tobof / openhab-addons

The next-generation open Home Automation Bus (openHAB)
Eclipse Public License 2.0
39 stars 30 forks source link

Some childs of a node don't get updated after changing their Configuration in Openhab #129

Open Jantleing opened 5 years ago

Jantleing commented 5 years ago

After changing configuration for a child of MySensor-Nodes in Paper-UI/Configuration/Things, all other childs don't get updated anymore. For example in the following log I have changed the name for child 2.

before change all childs got found and updated:

18:58:36.095 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 1;10;1;0;47;48 0 0
18:58:36.124 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Node 1 found in gateway
18:58:36.151 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Child 10 found in node 1
18:58:36.178 [DEBUG] [sensors.handler.MySensorsThingHandler] - Updating channel: text(V_TEXT) value to: 48 0 0
18:58:36.220 [DEBUG] [sensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/10 to 2018-12-01T18:58:36.000+0100
18:58:36.221 [INFO ] [smarthome.event.ItemStateChangedEvent] - mysensors_text_8b48534b_text_1_10_text changed from 46 0 0 to 48 0 0
18:58:36.295 [INFO ] [smarthome.event.ItemStateChangedEvent] - mysensors_text_8b48534b_text_1_10_lastupdate changed from 2018-12-01T18:58:25.000+0100 to 2018-12-01T18:58:36.000+0100
then I changed the name for for the second child, which caused this log entries:
18:58:40.759 [DEBUG] [sensors.handler.MySensorsThingHandler] - Configuration: MySensorsSensorConfiguration{nodeId=1, childId=2, requestAck=false, revertState=true, smartSleep=false, childUpdateTimeout=-1, nodeUpdateTimeout=-1, requestHeartbeatResponse=false, usePureWhiteLightInRGBW=false}
18:58:40.843 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Adding device MySensorsNode [nodeId=1, childNumber=1, chidldList={2=MySensorsChild [childId=2, nodeValue={V_VAR4=MySensorsVariableVVar4 [value=null], V_VAR5=MySensorsVariableVVar5 [value=null], V_VAR2=MySensorsVariableVVar2 [value=null], V_VAR1=MySensorsVariableVVar1 [value=null], V_HUM=MySensorsVariableVHum [value=null], V_VAR3=MySensorsVariableVVar3 [value=null]}]}]
18:58:40.967 [DEBUG] [sensors.handler.MySensorsThingHandler] - Event listener for node 1-2 not registered yet, registering...
18:58:41.073 [INFO ] [smarthome.event.ThingUpdatedEvent    ] - Thing 'mysensors:humidity:8b48534b:humidity_1_2' has been updated.
after this only child 2 gets updated with new information, other childs seem not to be found anymore:
18:58:46.370 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 1;1;1;0;0;21.5
18:58:46.399 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Node 1 found in gateway
18:58:46.426 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Child 1 not present in node 1
18:58:46.740 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 1;2;1;0;1;56.6
18:58:46.810 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Node 1 found in gateway
18:58:46.863 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Child 2 found in node 1
18:58:46.891 [DEBUG] [sensors.handler.MySensorsThingHandler] - Updating channel: hum(V_HUM) value to: 56.6
18:58:46.936 [DEBUG] [sensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/2 to 2018-12-01T18:58:46.000+0100
18:58:46.940 [INFO ] [smarthome.event.ItemStateChangedEvent] - mysensors_humidity_8b48534b_humidity_1_2_hum changed from 57.2 to 56.6
18:58:47.010 [INFO ] [smarthome.event.ItemStateChangedEvent] - mysensors_humidity_8b48534b_humidity_1_2_lastupdate changed from 2018-12-01T18:58:35.000+0100 to 2018-12-01T18:58:46.000+0100
18:58:47.103 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 1;10;1;0;47;51 0 0
18:58:47.132 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Node 1 found in gateway
18:58:47.159 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Child 10 not present in node 1
[...]
I am using Openhab 2.3 with the binding "org.openhab.binding.mysensors-2.3.0-SNAPSHOT.jar" (btw: thanks very much for this binding, makes things so much easier!) I think this is not a to bad issue because a solution is to reset the node, then it gets updated again.. but for someone who doesn't know it could be pretty annoying