The annoying thing is that the switch is still working as far as I can see. It can be excluded and included from the network, and when it is freshly included, it will respond to commands sent to it up to the point when the Zstick reports that it's dead. Then, of course, the Zstick refuses to send any commands to it because it claims it is dead - when I'm pretty sure it is not.
Code: Select all
2017-01-01 11:02:39.821 OpenZWave: using config in: C:\Program Files (x86)\Domoticz\Config/
2017-01-01 11:02:40.006 OpenZWave: Driver Ready
...
2017-01-01 11:02:40.487 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 27 (0x1b)
...
2017-01-01 11:03:35.668 OpenZWave: Received Node Dead notification from HomeID: 3550212702, NodeID: 27 (0x1b)
...
2017-01-01 11:11:21.384 OpenZWave: Closed
...
...
2017-01-01 11:16:05.162 OpenZWave: Node Removed. HomeID: 3550212702, NodeID: 27 (0x1b)
2017-01-01 11:16:05.227 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 28 (0x1c)
...
2017-01-01 11:17:14.786 OpenZWave: Received Node Dead notification from HomeID: 3550212702, NodeID: 28 (0x1c)
...
017-01-01 11:18:37.199 OpenZWave: Awake Nodes queriedEdit: I found this page about dealing with dead nodes in the OpenZwave knowledge base. I've tried all the steps except resetting the USB controller without success. So it looks as though the nuclear option of resetting the controller and starting all over again to build up the entire network may be necessary. Sigh.
I note this passage in the text, which I find a bit worrisome:
From the OpenZWave side of things, once a Node ends up on the Failed Node List in the controller, the controller will reject any attempt to communicate with it. There may be a command that be issued to the controller to clear the failed node list, or retry communications with failed nodes, but we are not aware of it.