openzwave randomly "removes" devices

[akamming]

Hi,

I have an issue on OpenZWave

So my issue is: my battery powered nodes are failing every now and then. When i look in zwave config then the info is gone and i have to give the "refresh node info" command (and push the button on the sensor so it wakes up) and then it works again.

this happens randomly. I investigated the logs, and the 1st appearance was July 18th. I did not do any changes to the system at that moment in time (the last one was the upgrade to 2023.1 somewhere in april)

this is what i see in the log (although no node remove command given):

Code: Select all

domoticz.2023.07.18-06.25.02.txt:2023-07-17 10:02:23.456  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 87 (0x57)
domoticz.2023.07.18-06.25.02.txt:2023-07-17 10:02:54.611  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 87 (0x57)
domoticz.2023.07.18-06.25.02.txt:2023-07-17 20:18:03.028  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 87 (0x57)
domoticz.2023.07.18-06.25.02.txt:2023-07-17 20:24:04.397  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 87 (0x57)
domoticz.2023.07.18-06.25.02.txt:2023-07-17 22:35:36.551  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 72 (0x48)
domoticz.2023.07.18-06.25.02.txt:2023-07-17 23:30:06.071  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 91 (0x5b)
domoticz.2023.07.18-06.25.02.txt:2023-07-17 23:46:28.484  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 94 (0x5e)
domoticz.2023.07.18-06.25.02.txt:2023-07-18 00:50:31.399  Status: Zwave.me: Node Removed. HomeID: 3959520233, NodeID: 185 (0xb9)

The nodes are still in the Zwave controller.. very weird. Does anyone have a suggestion? (and pls don't give the advice to upgrade to zwave-js-ui. i know i have to, but tried that several times, but zwave-js-ui never finishes the initialization. Also don't have the time to that migration right now...)

[gizmocuz]

The only reason this can happen is that the controller is receiving a remove node request
Anyway, OpenZWave is deprecated, and removed in the latest beta.
Time to update

[akamming]

The only reason this can happen is that the controller is receiving a remove node request
Anyway, OpenZWave is deprecated, and removed in the latest beta.
Time to update

actually i know 2 "normal" reasons this message can occur. Indead a "remove node" request (which was not given). But also a "replace failed node" request (which does a remove and an add). I did not issue any of these commands.

I know I have to update. But as stated above: I already tried several times: zwave-js-ui never finishes initialization.. so is not (yet) usable for me. I will need to spend more time on this which i don't have know.

IF anyone in the meantime has suggestions on what i can do to troubleshoot the (nog longer supported) ozw for this case i would be very thankful..

[gizmocuz]

Probably you might have configured a invalid serial port, or if you mean finished initialisation the same as with OpenZWave, it could be necessary to wake up some battery nodes
I woud expect some devices being visible at this stage

[akamming]

Probably you might have configured a invalid serial port, or if you mean finished initialisation the same as with OpenZWave, it could be necessary to wake up some battery nodes
I woud expect some devices being visible at this stage

serial port is correct. The whole process starts but not all devices are initialized. I know i have to wake up battery powered nodes, but even not all nodes connected to mains are initialized so there's more going on.

So only way i can think of to fix is start all over by doing a factory reset on the controller and start including the devices one by one but that's a very time consuming process (1 have 80+ devices). Also if you take into account that i have to get all the names right (or adapt the scripts) to make everything work correctly again... WIll do it in the near future, but that does not solve my issue on the unsupported openzwave now...

For now i just updated to 2023.2 (last one with ozw support). Let's see if that has effect..

[akamming]

the update to 2023.2 did not resolve the issue...

i now enabled debugging on the OZW logging. If anyone has hints on how to solve i am very open to it..!

(And yes mr gizmocuz i even tried upgrading to zwave-js-ui this morning. but several devices do not finish inverviewing phase and are therfor unusable and i;m not only talking about battery powered nodes... so reverted back to OZW. if you have a way to fix that i'm open to it as well ofcourse...)

[gizmocuz]

regarding your not-finished-interviewing, please have a look on the zwavejs-ui forum, as this is not related to domoticz

[akamming]

regarding your not-finished-interviewing, please have a look on the zwavejs-ui forum, as this is not related to domoticz

i cannot find a zwavejs-ui forum. Do you have a link?

BTW: About the original problem: i narrowed it down to the automatic healing of the network everyday (i saw a pattern a pattern in the times on which it occurred. With this option switched off the issue is gone. When i switched it back on the issue was back)

[waltervl]

Zwave-JS-UI forum is here : https://github.com/zwave-js/zwave-js-ui/discussions

[akamming]

Zwave-JS-UI forum is here : https://github.com/zwave-js/zwave-js-ui/discussions

tx!!