Open OliverHi opened 7 years ago
I still have the same problem and it happens a lot more than I though earlier. About 40-50% of the time. This time I saw the log output below. As I have the log level set to debug for mysensors it normally shows all the (signing) messages. In this case it seems to have found the node but not send any actual messages.
22:09:18.990 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'LichtKuecheObenOn' received command OFF
22:09:19.030 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 3 found in gateway
22:09:19.061 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 3
22:09:19.083 [INFO ] [rsAbstractConnection$MySensorsWriter] - ACK received for message: 3;1;1;1;2;0
22:09:19.145 [INFO ] [marthome.event.ItemStateChangedEvent] - LichtKuecheObenOn changed from ON to OFF
If there is any way I can help finding the error just tell me. It is kind of annoying when trying to use openhab + mysensors ;)
1) This only happens on RGBW nodes?
2) If you disble the request for ACK does the error remain?
3) The second log shows that a ACK was received from the node, indicating that the node has received the message OFF. Did LichtKuecheObenOn
(the hardware) changed to off? Or was there no reaction at all?
[rsAbstractConnection$MySensorsReader] - Message from gateway received: ...
messages, in the error cases there are none at all. Only the MySensorsWriter
message from the above log and an ItemStateChangedEvent
I am running openhab 2.1.0 and the version 2.2.0.201707241115 of the MySensors binding on a raspberry pi.
When trying to change values of my RGBW node the updates don't always get send to the node. I have enabled debug logging for the mysensors Binding so normal output looks something like this:
I have activated signing for the nodes and
requestAck=true
for the openhab thing.Sometimes when I change some settings for the node all I get in the openhab log is
no indication in either the openhab or the nodes log that any messages actually get send. I don't see any pattern about when this is happening but it seems to mostly occur when I change the state of the node more quickly.