Zwave unknown nodes?

Tags: #<Tag:0x00007f616f96ea10>

lately I see different node ids in the log with the following warning.
those are always node ids that have never been on my network.
anything plausible where something like this comes from?
cheers

20:10:59.455 [WARN ] [rnal.protocol.ZWaveTransactionManager] - NODE 148: Not initialized (ie node unknown), ignoring message.
20:10:59.466 [WARN ] [rnal.protocol.ZWaveTransactionManager] - NODE 148: Not initialized (ie node unknown), ignoring message.
20:10:59.644 [WARN ] [rnal.protocol.ZWaveTransactionManager] - NODE 148: Not initialized (ie node unknown), ignoring message.
20:10:59.738 [WARN ] [rnal.protocol.ZWaveTransactionManager] - NODE 148: Not initialized (ie node unknown), ignoring message.
20:10:59.993 [WARN ] [rnal.protocol.ZWaveTransactionManager] - NODE 148: Not initialized (ie node unknown), ignoring message.

Maybe not with OH, but what zwave device are you using?

I do see this sometimes too, but did not dig deeper yet to find the cause … :sunglasses:

I see this too, using aeotec zstick gen5. Has 46 of these so far this month. Some of them come from node-numbers that actually were used earlier, some of the warnings come from completely unused node numbers, and a couple times this has come from node 0.

Not yet observed any issue except from the log warning.

I experience the exact same issue:

2019-07-30 13:11:15.996 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 6: Not initialized (ie node unknown), ignoring message.
2019-07-30 13:11:16.997 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 6: Not initialized (ie node unknown), ignoring message.
2019-07-30 13:11:25.997 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 6: Not initialized (ie node unknown), ignoring message.
2019-07-30 13:11:26.998 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 6: Not initialized (ie node unknown), ignoring message.

I can’t find any reference to this node 6. It is not in the inbox (i also checked the hidden items), it is not in any .thngs or .rules .items file.

Could it be a partially removed assocation? The node still sends messages to the controller and the controller does not have this Association anymore? And everytime the node sends a message to the controller. the controler throws this warning? It is just a guess, but if so, it would be cool if the binding would be more explicit in what is going on. “…ignoring message from NODE 6.”

Edit: using openHAB 2.5.0 Build #1641

This is already quite explicit. It means that there was a message received, from node 6, and that node 6 is not known in the system. The message is therefore ignored.

This normally happens when you have previously had a device in the network, and you have since reset the controller, but the device is still sending out periodically messages as it was never removed from the network.

The developer of the binding might find it explicit. For me (as end user) I was like what node? what message? It would be really helpfull if it was changed to:

NODE 6: Not initialized (ie node unknown to controller), ignoring message originating from this node.

This normally happens when you have previously had a device in the network, and you have since reset the controller, but the device is still sending out periodically messages as it was never removed from the network.

It was exactly that.

I personally don’t think this helps. It should be obvious that the node is not known to the binding (it is a binding logfile after all), and it should be reasonably obvious that it’s this message that is being ignored, since this is what is being logged about.

We can’t write a book in log messages, so I think you would still have asked the same question if we had added the extra 4 or so words here :wink:

Anyway, I hope my answer was helpful to you in understanding the issue.

Well your post helped, thanks! I’m sure that i could have come to the same conclusion if the error was more clear to me, but i allready made that point. :slight_smile:

thanks for the explanation, @chris - it explains well the messages of old nodes that were not removed.

But how can ist explain completely unexisting nodes? for example, my highest ever connected node is i the 80s, but I am getting spammed with messages from nodes that never existed:

ZW 14-Nov-2019 15:40:11 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 172: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 15:40:11 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 172: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 21:12:24 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 108: Not initialized (ie node unknown), ignoring message.

ZW 14-Nov-2019 22:22:29 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 67: Not initialized (ie node unknown), ignoring message.

ZW 15-Nov-2019 06:28:11 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 99: Not initialized (ie node unknown), ignoring message.

ZW 15-Nov-2019 06:28:12 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 99: Not initialized (ie node unknown), ignoring message.

ZW 15-Nov-2019 06:28:13 [WARN ] [ng.zwave.internal.protocol.ZWaveTransactionManager] NODE 99: Not initialized (ie node unknown), ignoring message.

I am on a Raspberry 4 on OH 2.5.0M4 and a Zwave.me Stick

@chris: is there a way to reinstate such a node back into openhab / the Controller without ging through factory reset and new inclusion? - I have one of those, a battery device that was originally very hard to include. I accidently removed it from the Controller and since then it continues to send messages but the Controller does not know the device anymore.

You have 2 options.

  1. Factory Reset the device
  2. Place the controller in Exclusion mode & exclude it. Any controller can exclude any Z-Wave device, even from a different network.

Unfortunately if you remove it from the controller, there’s no way back and you’ll need to re-include it again.

True, but the device needs to realize is has been excluded first, correct? A device will only be included into one network at a time

Yes, it will need resetting or excluding first otherwise you can’t include it.

1 Like