Z-wave JS Conroller showing "Initialising network" z-wave node showing "Node not ready" #268
-
|
Just trying to add another node to my z-wave network, but the inclusion seems to have messed up one of my existing nodes... :( The node seems now to be asleep (it should been awake) and when clicking on the node I get "Node not ready": Anything I can do to fix it again? Or is exclude and include again by best option? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
HI @widert You can try waking up the node - if it can sleep, most devices have a wake routine, it should be documented in its manual. If for what ever reason, the node is not waking up, you can shift + click the node - and this will reveal options, one of which is a "remove failed node" option - once removed, you will need to re-add it, but I would first try the wake up routine, before having to forcibly remove and re-add it |
Beta Was this translation helpful? Give feedback.
-
|
See here for shift + click https://github.com/zwave-js/node-red-contrib-zwave-js/wiki/User-Interface |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Marcus, the node was an "old" one that reappeared, removed it with Shift-Click I also used the opportunity to upgrade to the newest version, looks great, congratulation with good work! Regards, |
Beta Was this translation helpful? Give feedback.
HI @widert
You can try waking up the node - if it can sleep, most devices have a wake routine, it should be documented in its manual.
Once the driver receives a wake up command from it - it will re-interview the node, and put it back to an operating state.
If for what ever reason, the node is not waking up, you can shift + click the node - and this will reveal options, one of which is a "remove failed node" option - once removed, you will need to re-add it, but I would first try the wake up routine, before having to forcibly remove and re-add it