After mega-20180426-normal sending TEXT tro OLED don't work

[M*I*B]

... any news maybe about the changed parameter?

[M*I*B]

PUSH

[budman1758]

I too would li8ke to know what the commands to write to the display have changed to. If it has changed it would be nice to know the differences are.

[M*I*B]

... looks as if no more sow cares, just like to the matter with the BME280 (viewtopic.php?p=28956#p28956) ...
That's a pity. I think the system is pretty good, but of course with this way of "support" you get the best OpenSouce software broken down quite quickly.

There is nothing left to do but switch to another system where support isn't a unknown word ...

[grovkillen]

... looks as if no more sow cares, just like to the matter with the BME280 (viewtopic.php?p=28956#p28956) ...
That's a pity. I think the system is pretty good, but of course with this way of "support" you get the best OpenSouce software broken down quite quickly.

There is nothing left to do but switch to another system where support isn't a unknown word ...

We're doing our best to get it stable and thus some issues are taking more time than anticipated. I'm sorry you're thinking our support is not good. I will improve.

Did you open an issue on GitHub?

[M*I*B]

... I have not say it's not good. I have say that the support not exist ...

It's month ago not only I ask for the new implemented parameter. Normaly if someone implement new parameter or attributes there is a changelist where the (what the name say) changes are documented... But here is nothing... Just changed and leave all alone with that. That's the same i.e. I cut a single cable in your home but don't tell you whith one and who ...

[grovkillen]

... I have not say it's not good. I have say that the support not exist ...

It's month ago not only I ask for the new implemented parameter. Normaly if someone implement new parameter or attributes there is a changelist where the (what the name say) changes are documented... But here is nothing... Just changed and leave all alone with that. That's the same i.e. I cut a single cable in your home but don't tell you whith one and who ...

I totally understand you. We will get better in the change log, at least for stable releases, maybe not much better for nightly. But have you opened one or more issues on GitHub? We have very little time to parse through the forum on search of issues.

[M*I*B]

... no ... Some time ago I have tell you that I don't know what GitHub is and how to handle ... I'm not a programmer/coder... I'm just a simple user with much scills in hardware and do my best to report faults and/or achievements and also ever be there to test some new things. But if I have'nt any things to test or have'nt any docs/changelist to read I can't check and test anything. And I believe that most of the users here also just users and don't know to handle GitHub but are able to describe problems and wishes in a forum like this ...

[grovkillen]

... no ... Some time ago I have tell you that I don't know what GitHub is and how to handle ... I'm not a programmer/coder... I'm just a simple user with much scills in hardware and do my best to report faults and/or achievements and also ever be there to test some new things. But if I have'nt any things to test or have'nt any docs/changelist to read I can't check and test anything. And I believe that most of the users here also just users and don't know to handle GitHub but are able to describe problems and wishes in a forum like this ...

Ok, then it's a bit hard for us to take care of those issues. We prefer you to use the GitHub issue tracker since it'll keep you updated with current status. We're not (yet) a big company so it's essentially me and TD-er taking care of everything around here. Once we get a chance to release a first stable we'll get more up to date with the documentation. I hope you understand our side of the story, we're doing our best and will get better doing it. Please bear with us.

[M*I*B]

... I understand you and your point of view ... That's not the problem. But I think you also have to take care of this user that can't handle GitHub; I believe that are the most.
If I have to wait 6 month or more without result for a thing I'm watching out for an other way to do it. In my matter it is the BME280 (it goes cold again and I have no way to mount this on the roof before next springtime) and the O-LED that meanwhile is the 4rd one due nobody knows about the dimmimg-attributes that are important for the livetime of this type of display... And meanwhile my stock of this displays are near empty due I have to replace it all 2-3 month... Gradually to destroy hardware and not to move forward is not really useful and not my goal ...

Maybe it's time to think about an other way where you not spend more time while pharsing the forum for issues but give the user without GitHub experience a way to incorporate the problems into the development. I'm sure that there is a viable solution that meets all sides, which does not leave the pure user in the rain and thus makes the project itself more manageable and thus more popular in the medium term...

[TD-er]

The Framed Oled plugin has support for dimming (not the normal OLED plugin)
I did add an issue about it: https://github.com/letscontrolit/ESPEasy/issues/1506

But I've simply been too busy fixing other stuff, that it kinda slipped my mind.

[TD-er]

I have re-read the topic and am now looking at the source code of the plugin.

It looks like it is looking for "," (a comma) as parameter separator.

For example:

Code: Select all

oled 4 1 Some Text here

Becomes:

Code: Select all

oled,4,1,"Some Text here"

And about the 'support'.
We're spending a hell of a lot of time in making it a better product, and maybe the time isn't spent as optimal as possible.
I do most of the coding (like 90+%) and thus visit the Github page the most.
I try to visit the forum also on a regular basis, but when I do, it takes about half of my evening reading through all the new replies and helping out where I can.
Also on the reported issues at Github, a lot of time is lost in trying to gather enough info to get an idea on what is really happening.

It is all done in our free time.
This is not meant as an excuse on why your question was missed a number of times, just some view on what is going on here.
We're simply short on time and manpower and there is too much which has to be done.
For me, the last few months have been mainly about getting stuff stable and making sure a lot of code duplication was taken out.
A lot of code was <cut><paste><paste><paste><paste> and then altered in just a few lines to match its use.
The problem with that kind of development is that when you fix something in the first few "paste" occurrences, it is still broken in the others.
That's probably also what happened to this OLED command, that it got broken by changing something else.