openHAB 2.2 binding
-
@LastSamurai I can't say when I'm able to solve those issues.
According the ACK problem I need to enable ACK support in my network at home, which was something I already wanted to do a long time ago but haven't found the time yet.
The RGBW is a tough nut for me. I don't have a RGBW node to test with and the conversion HSB <=> RGBW is driving me crazy. The algorithm for the conversion can be found here: https://github.com/tobof/openhab2-addons/blob/MySensors_Binding/addons/binding/org.openhab.binding.mysensors/src/main/java/org/openhab/binding/mysensors/converter/MySensorsRGBWTypeConverter.java
@gonzalonal May I ask you to add an issue on github? This would allow me track those enhancement requests. Thank you!
-
Yes, sure. I'll do that to keep track.
By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?
-
Yes, sure. I'll do that to keep track.
By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?
@gonzalonal said in openHAB 2.2 binding:
Yes, sure. I'll do that to keep track.
By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?
You can find the issues here. Basically you (I ;)) can't set RGBW nodes to display pure white colors via openhab, dimming is not working (error confirmed by TimO) and most importantly ACK isn't working properly (for me at least). If you can help with any of this (especially the conversion HSB <=> RGBW) you are most welcome.
-
@gonzalonal said in openHAB 2.2 binding:
Yes, sure. I'll do that to keep track.
By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?
You can find the issues here. Basically you (I ;)) can't set RGBW nodes to display pure white colors via openhab, dimming is not working (error confirmed by TimO) and most importantly ACK isn't working properly (for me at least). If you can help with any of this (especially the conversion HSB <=> RGBW) you are most welcome.
Please kindly check my contribution in the git issue. Maybe it will help to clarify your issues.
@LastSamurai said in openHAB 2.2 binding:
@gonzalonal said in openHAB 2.2 binding:
Yes, sure. I'll do that to keep track.
By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?
You can find the issues here. Basically you (I ;)) can't set RGBW nodes to display pure white colors via openhab, dimming is not working (error confirmed by TimO) and most importantly ACK isn't working properly (for me at least). If you can help with any of this (especially the conversion HSB <=> RGBW) you are most welcome.
-
@gonzalonal I saw it earlier but did not understand it fully. I will take another look at it later.
@TimO I might have found the error... maybe. I reflashed the motion sensor (with cleared eeprom before) and removed the static id and signing. Now I see that the problem seems to be that the node is unable to get an ID. Any idea what's happening herer? Is there a setting concerning that somewhere?
Log from the node:
... 102477 TSM:FAIL:RE-INIT 102479 TSM:INIT 102488 TSM:INIT:TSP OK 102490 TSM:FPAR 102492 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 103426 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0 103432 TSF:MSG:FPAR OK,ID=0,D=1 104501 TSM:FPAR:OK 104503 TSM:ID 104503 TSM:ID:REQ 104507 TSF:MSG:SEND,255-255-0-0,s=55,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 106516 TSM:ID 106516 TSM:ID:REQ 106520 TSF:MSG:SEND,255-255-0-0,s=20,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 108529 TSM:ID 108529 TSM:ID:REQ 108533 TSF:MSG:SEND,255-255-0-0,s=241,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 110542 TSM:ID 110542 TSM:ID:REQ 110546 TSF:MSG:SEND,255-255-0-0,s=206,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 112556 !TSM:ID:FAIL 112558 TSM:FAIL:CNT=6 112560 TSM:FAIL:DIS 112562 TSF:TDI:TSL ...Log from the openhab server:
15:21:32.127 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;34;3;0;3; 15:21:34.135 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;0;3;0;3; 15:21:36.147 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;221;3;0;3; ...and lots more similar requests with different ids.
-
@gonzalonal I saw it earlier but did not understand it fully. I will take another look at it later.
@TimO I might have found the error... maybe. I reflashed the motion sensor (with cleared eeprom before) and removed the static id and signing. Now I see that the problem seems to be that the node is unable to get an ID. Any idea what's happening herer? Is there a setting concerning that somewhere?
Log from the node:
... 102477 TSM:FAIL:RE-INIT 102479 TSM:INIT 102488 TSM:INIT:TSP OK 102490 TSM:FPAR 102492 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 103426 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0 103432 TSF:MSG:FPAR OK,ID=0,D=1 104501 TSM:FPAR:OK 104503 TSM:ID 104503 TSM:ID:REQ 104507 TSF:MSG:SEND,255-255-0-0,s=55,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 106516 TSM:ID 106516 TSM:ID:REQ 106520 TSF:MSG:SEND,255-255-0-0,s=20,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 108529 TSM:ID 108529 TSM:ID:REQ 108533 TSF:MSG:SEND,255-255-0-0,s=241,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 110542 TSM:ID 110542 TSM:ID:REQ 110546 TSF:MSG:SEND,255-255-0-0,s=206,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK: 112556 !TSM:ID:FAIL 112558 TSM:FAIL:CNT=6 112560 TSM:FAIL:DIS 112562 TSF:TDI:TSL ...Log from the openhab server:
15:21:32.127 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;34;3;0;3; 15:21:34.135 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;0;3;0;3; 15:21:36.147 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;221;3;0;3; ...and lots more similar requests with different ids.
@LastSamurai Upgrade the binding. You're using the current beta of MySensors and the request for I'd has changed.
-
@LastSamurai Upgrade the binding. You're using the current beta of MySensors and the request for I'd has changed.
@TimO Ahh thank you! I am using version 2.2 linked in the first post of this thread though. Where do I get a newer version? Maybe I overlooked it but I am not seeing any newer releases.
-
@TimO Ahh thank you! I am using version 2.2 linked in the first post of this thread though. Where do I get a newer version? Maybe I overlooked it but I am not seeing any newer releases.
@LastSamurai just replace the jar from the link above. I'm doing small changes from time to time.
-
@LastSamurai just replace the jar from the link above. I'm doing small changes from time to time.
@TimO Thank you again for the help. Everything is now back up and running :+1: With the new jar my node could finally get a new id and after also enabling signing again everything worked as expected.
Can I see anywhere that you updated the jar file? I am using the current beta of mysensors mostly so I would also need to use an updated version of the openhab plugin. -
@TimO , is this binding supported via mysensors MQTT gateway?
In previous bending inormation you had some text indicating that you would implement it. But all that is gone.
So I'm thinking you either implemented it, or aborted that feature :) -
@TimO , is this binding supported via mysensors MQTT gateway?
In previous bending inormation you had some text indicating that you would implement it. But all that is gone.
So I'm thinking you either implemented it, or aborted that feature :)@Nicklas-Starkel It happens, that MQTT support is sadly still on the to do list. There were some changes in the Smarthome MQTT library and we need to adopt them now.
Here's the Issue: https://github.com/tobof/openhab2-addons/issues/98
-
@Nicklas-Starkel It happens, that MQTT support is sadly still on the to do list. There were some changes in the Smarthome MQTT library and we need to adopt them now.
Here's the Issue: https://github.com/tobof/openhab2-addons/issues/98
@TimO, cool that you are stil on it, even if it's on the "todo-list".
Kudos and keep up the great work :) -
Can we use this binding for MQTT once the PR is available in OpenHAB?
It is a separate mqtt generic binding in ESH for things discovery but I cannot make out if this will solve the dependency issue or not.
https://github.com/eclipse/smarthome/pull/3876 -
@TimO My sketches are sending the nodes remaining battery power to the controller via a V_VOLTAGE. Openhab 2 with your binding doesn't seem to be able to read these values. Is this an error (possibly on my side) or does the not yet support this?
-
@TimO My sketches are sending the nodes remaining battery power to the controller via a V_VOLTAGE. Openhab 2 with your binding doesn't seem to be able to read these values. Is this an error (possibly on my side) or does the not yet support this?
@LastSamurai Did you connect a channel / item for V_VOLTAGE? If the sensor is not represented by the sketch you need to connect it manually.
-
Can we use this binding for MQTT once the PR is available in OpenHAB?
It is a separate mqtt generic binding in ESH for things discovery but I cannot make out if this will solve the dependency issue or not.
https://github.com/eclipse/smarthome/pull/3876@gahlawathome I'm currently looking into the new MQTT implementation in smartphone. It should work without the PR above. The PR will bring us a new option to connect a MQTT binding with OpenHAB!
-
@LastSamurai Did you connect a channel / item for V_VOLTAGE? If the sensor is not represented by the sketch you need to connect it manually.
@TimO I am not sure what you mean.
My sketch sends a presentation:present(CHILD_ID_BATTERY, S_MULTIMETER);and in openhab I added these (tried both sensor kinds)
// things customSensor abc [nodeId=26, childId=1] multimeter def [nodeId=17, childId=1] // and items Number voltageSensorWZ ... { channel="mysensors:multimeter:gwSerial:def:volt" } //...Is there anything i am missing here?
-
@TimO I am not sure what you mean.
My sketch sends a presentation:present(CHILD_ID_BATTERY, S_MULTIMETER);and in openhab I added these (tried both sensor kinds)
// things customSensor abc [nodeId=26, childId=1] multimeter def [nodeId=17, childId=1] // and items Number voltageSensorWZ ... { channel="mysensors:multimeter:gwSerial:def:volt" } //...Is there anything i am missing here?
The channel is not correct:
channel="mysensors:multimeter:gwSerial:voltageSensorWZ:volt"It's confusing, but that's the way OpenHAB2 handles channels. :confused:
-
The channel is not correct:
channel="mysensors:multimeter:gwSerial:voltageSensorWZ:volt"It's confusing, but that's the way OpenHAB2 handles channels. :confused:
@TimO Thanks for your help though I am afraid you mixed something up there. The channel linking to the item itself doesn't really make sense ;)
Not 100% sure why it did not work earlier for me but I now got it to work like this:// thing multimeter voltTHWohnzimmer [nodeId=1, childId=2] // item Number voltageSensorWZ "Spannung [%3f mV]" <poweroutlet_eu> (grVolt, grWZ) { channel="mysensors:multimeter:gwSerial:voltTHWohnzimmer:volt" }My error in the code above seems to have been that I defined most as customSensor instead of multimeter.
