This is really strange but I've had it happen at least three times. It's happen enough that I'm wondering if I have a corrupted data base. It this keeps up I'm worries that my system will never be stable.
So what will happen is a hardwired device will stop responding. I've had it happen on old Evolve switches and now on a ZOOZ REN15 switch.
In the case of the ZOOZ I pool them for several of their readings and for the current watts let them send the data when it changes. I just had my ZOOZ on node 64 stop responding to polls stating that it was sleeping. That's a problem since these devices never sleep. I went to the Z-Wave tab so check the device and it did respond to a test for contacted but fails both Rescan and Audit this Node. Here is the Audit this node information.
It was then I noticed under Options that the node ID showed No Node ID. As I said this has happen before on some of my Evolve devices, they just loose the Node ID and you can reset it since the node id is not in the list to select.
How can a device just suddenly loose its Node ID and that ID disappear from the node list?
I am running HS3 beta but the first time this happen I don't think I was on a beta. I could go back to the last official release and its backup but all of my new stuff would be history if the current backups won't load on the last official release.
So what will happen is a hardwired device will stop responding. I've had it happen on old Evolve switches and now on a ZOOZ REN15 switch.
In the case of the ZOOZ I pool them for several of their readings and for the current watts let them send the data when it changes. I just had my ZOOZ on node 64 stop responding to polls stating that it was sleeping. That's a problem since these devices never sleep. I went to the Z-Wave tab so check the device and it did respond to a test for contacted but fails both Rescan and Audit this Node. Here is the Audit this node information.
Auditing node 64 (Root_Status Garage Door Opener Root Status) ...
HomeSeer was able to send a frame to the node.
HomeSeer cannot test two-way communication with the node because it is a non-listening node.
HomeSeer was able to send a frame to the node.
HomeSeer cannot test two-way communication with the node because it is a non-listening node.
How can a device just suddenly loose its Node ID and that ID disappear from the node list?
I am running HS3 beta but the first time this happen I don't think I was on a beta. I could go back to the last official release and its backup but all of my new stuff would be history if the current backups won't load on the last official release.
Comment