-
I've done some searches across other issues and i'm coming up without an answer. I have a failed device which is no longer physically powered on (it died). zwavejs won't let me remove the failed node as it says INFO Z-WAVE: The node removal process could not be started due to the following reasons: The node has no deviceID or any data (0xXXXX 0xXXXX-0xXXXX) if I interview i see this 2024-10-11T17:38:48.324Z CNTRLR [Node 016] Interview attempt 1/5 failed, retrying in 5000 ms... but the node is still not marked as failed. How can I mark it as failed? running the latest versions of every component. zwave-js-ui: 9.21.1.e8667de Debug Info
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
Try pinging the node to see if it then marks it as failed. That usually works for me. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately not - i've tried this a bunch of times. |
Beta Was this translation helpful? Give feedback.
-
Hi - here is the log. It is Node 16 I did a ping - waited for that to come back as failed - then did a remove failed node |
Beta Was this translation helpful? Give feedback.
-
Your controller is becoming unresponsive. Do an OTW update of the firmware to the latest version (1.50), which can be found on https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/ You may want to wait until nothing is happening to avoid any interruptions. If the firmware update aborts, there is a setting called "bootloader only", which you can check to re-attempt the upgrade. |
Beta Was this translation helpful? Give feedback.
-
@AlCalzone That was it - after the FW update I was able to remove the node immediately. I had only updated to 1.4 a few weeks ago so wasn't expecting another FW so soon. Thank you! |
Beta Was this translation helpful? Give feedback.
Your controller is becoming unresponsive. Do an OTW update of the firmware to the latest version (1.50), which can be found on https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/
You may want to wait until nothing is happening to avoid any interruptions. If the firmware update aborts, there is a setting called "bootloader only", which you can check to re-attempt the upgrade.