[REQUEST] LCD display support about nl.joolee.homey.espeasy HOT 10 CLOSED

I think I'll be able to make that work:
https://www.letscontrolit.com/wiki/index.php?title=OLEDDisplay

Can you test if you can use these commands?

[<taskname>].OLED,<row>,<col>,<text> 
[<taskname>].OLEDCMD,<value>

I want to be able to target a specific OLED display that is connected, otherwise, I will be sending commands to all of them... Also, can you find out whether sending text like {D} to get a degree sign actually works? And what happens when you send a degree sign without translating it to {D}? I can include the translation table in the app but It's nice to know it works and it actually is necessary.

Homey will be sending commands with a HTTP GET request like so:
http://192.168.xxx.xxx/control?cmd=mydisplay.OLED,1,1,test%20text
Can you test your commands that way?

from nl.joolee.homey.espeasy.

I currently don't own such a display yet. Want to make sure it's supported before ordering.
I was indeed looking into the commands, and since I receive an 'OK' from the webserver, I feel that at least that should be working.
Is there a way to see the values (virtually) that I shared over cmd?

from nl.joolee.homey.espeasy.

You might be able to see them in the log if you set logging to high. I don't know for sure though.

from nl.joolee.homey.espeasy.

It gave me this:
15254991: HTTP: OLED,1,1,TestTextOnDisplay
15254994: Command: OLED

So not really the outcome I was looking for.
I obviously can order a display at Ali, but it might take some time to get shipped.

from nl.joolee.homey.espeasy.

It looks good though. Worst case, you can use it by triggering custom rules or commands (which is on my to-do list #2) with Homey.

I can't make the <taskname> version give me an OK though, that's a bit weird.

from nl.joolee.homey.espeasy.

I have fixed issue #2 so in the next version, you can run custom commands on the unit.

I want to see the commands below working before I add the plugin as a device. I don't want a user to accidentally control multiple OLED displays, that would get confusing.

[<taskname>].OLED,<row>,<col>,<text> 
[<taskname>].OLEDCMD,<value>

I'll look into this a bit more some time but if you can confirm you got the commands above working, I'll make the plugin. Shouldn't be too much work now that I have action cards implemented.

from nl.joolee.homey.espeasy.

Great news!
I've received the displays and did some testing.

In fact, there seems to be a difference between OLED and OLED FRAMED and in my scenario, OLED FRAMED worked best so far.

By triggering the following URL, I get to change text on my display:
http://<IP>/control?cmd=OLEDFRAMEDCMD,<ROW>,<Text>

from nl.joolee.homey.espeasy.

Is there also a way to specifically control a single oled panel? Otherwise, I'll have to restrict the oled devices to a single one per unit.

from nl.joolee.homey.espeasy.

Beat me to it, but I don't believe you can connect more than one display.
https://espeasy.readthedocs.io/en/latest/Plugin/P036.html

from nl.joolee.homey.espeasy.

Decided not to implement this for now. It's a lot of work to implement the most used display plugins and they can all be controlled by just sending commands to the unit with the available action flowcard.

from nl.joolee.homey.espeasy.