rule "open garage gate by Status_Entrance"
when
Item Status_Entrance_Top received command or
Item Status_Entrance_Top_s received command or
Item Status_Entrance_Top_l received command
then
logInfo("Status_Entrance", "triggering garage gate")
//Switch_Garage_Gate.sendCommand(ON)
if (Gate_Garage.state == OPEN)
Status_Entrance_Line1.sendCommand("schließt")
else
Status_Entrance_Line1.sendCommand("öffnet")
Status_Entrance_Submit.sendCommand(ON)
end
Sending and receiving text lines work (but there is no reaction to my rule, neither logging nor text lines), so in general the setup is ok. Any suggestions?
When pressing long, I get the error “Unknown value ‘CONT’ for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed”, is this related?
Ok, I will give it a try, thank you. This is probably not to be discussed in this thread, but are the addon releases bound to the main OH version number? There should be maintenance releases of addons inbetween two OH releases. At least, I was hoping to get bugfixes easier and continuously by switching to the package distribution of OH. I don’t mean to be rude (my comment is rather general than specific to the homematic addon), but manually installing snapshot versions was pretty much what I was hoping to avoid. I will try it nonetheless.
maybe this was not such a good idea after all. Now updated all to 2.3.0.20180314… and nothing is working anymore. Karaf is not starting many bundles, among them core, ui, the bindings, transformations etc… I know what I’ll do for the rest of the evening…
Hmmm, I have tried 2.3 Build 1221 and no problems with a clean installation (on Windows). But I did not test it with production environment on the raspi.
So good luck …
Some feedback from my testing…
Button presses work when reacting on “changed to ON” events, not “received command”.
Text transmission only works for lines 2 and 3. The button descriptions cannot be changed, and also the 3rd line in the middle (presumably line 4) cannot be set. The EP-Thing has only 3 lines, not 5.
Did someone manage to change the button text or the 3 middle line?
It is definitly not possible to change the button texts via the binding, but the three lines in the middle can be set (at least with binding version 2.1). I am not at home, so I can’t post my rule code, but I can check it this weekend and post the rule code here.
I created a slightly modified version of my rule that is running on OH 2.1:
rule "Info-Anzeige"
when
Item Fenster_Arbeitszimmer changed or
Item Fenster_Bad changed or
Item Fenster_Schlafzimmer changed or
Item Tuer_Wohnzimmer changed or
Item Balkon_Temperatur changed
then
val temp = "Line 1"
sendCommand(DT_L1, temp)
sendCommand(DT_Icon1, "OK")
var fensterIcon = "OK";
sendCommand(DT_Icon2, fensterIcon)
sendCommand(DT_L2, "Line 2")
sendCommand(DT_L3, "Line 3")
sendCommand(DT_Icon3, "ON")
sendCommand(DT_Submit, ON) // always execute at the end
end
Item DT_L1 ist connected with channel DISPLAY_LINE_1, DT_L2 with channel DISPLAY_LINE_2, …
Thanks a lot for the good feedback! Well, my lines are off by 1, so when I write to line 2, it appears where you have line 1. Text written to line 1 does not appear anywhere…
I assume it is related to this update, where @Thomas_G mentioned that the lines have been shifted? I think it made things worse for the EP device. Could you make that last change only for the OLED version and revert for EP?
@gerrieg Yes, they are really “interesting” devices :-).
Strictly speaking, the EP device has got 5 lines. But via the binding only the 3 lines in the middle can be set (see my picture above). In version 2.1 of the binding there were 3 channels for the text and 3 channels for the icons:
DISPLAY_LINE_1 to DISPLAY_LINE_3 and DISPLAY_ICON_1 to DISPLAY_ICON_3.
In the next days I can find some time for testing (and probably migrating my production environment to 2.3).
The OLED HM-DIS-WM55 device has 6 lines. Your changes made the device completely usable. (One more line and shifting the content one line up).
For the EP device you must revert the shifting-change. But only for EP, not for “my” device.
I think that is the only “To-Do”.
That’s what I interpret here.
Hi @gerrieg, did you have time to fix this issue? Would help me a lot because right now, I cannot use the device properly. When you make the changes in a snapshot I can test it right away.
