Xathros Posted July 15, 2016 Posted July 15, 2016 I have a Schlage FE-599 that died due to water entering through a damaged keypad. Since it's dead, I'm unable to exclude it from my network. I have tried to use "Remove failed zwave node" with the following result: What now? I'm on 5.0.4. -Xathros
stusviews Posted July 15, 2016 Posted July 15, 2016 You may just want to delete the device and heal the Z-Wave network. In any case, the id (ZW 006) is not vacated, that is, a new device will never use that id. But that's true even if you exclude a functioning device.
Xathros Posted July 15, 2016 Author Posted July 15, 2016 Tried that but it comes back with a "Synchronize new and deleted". I'd really like to to just be gone. I don't care (at this point) if #6 never gets reused.
Michel Kohanim Posted July 17, 2016 Posted July 17, 2016 Hi Xathros, Right mouse click | Z-Wave | Remove failed node. With kind regards, Michel
Xathros Posted July 18, 2016 Author Posted July 18, 2016 Hi Xathros, Right mouse click | Z-Wave | Remove failed node. With kind regards, Michel Hi Michel, Please see post #1 of this thread. Thats exactly what I did and what failed. -Xathros'
Michel Kohanim Posted July 19, 2016 Posted July 19, 2016 Hi Xathros, 1. Delete from ISY 2. Synchronize 3. It will show up as uninitialized or not responsive 4. Remove Failed Device With kind regards, Michel
Xathros Posted July 19, 2016 Author Posted July 19, 2016 Hi Michel, Thanks. I'll give this a shot. I did have to restart my ISY yesterday for a new nodeserver profile installation. This may have some bearing on the situation. I will report back tonight. -Xathros
Xathros Posted July 21, 2016 Author Posted July 21, 2016 UPDATE: It looks as though the restart resolved my problem. After having restarted the ISY for a node server install, I was able to right click and remove the failed node successfully. -Xathros
Michel Kohanim Posted July 21, 2016 Posted July 21, 2016 Hi Xathros, Thanks so very much for the update. With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.