#Z-Wave JS UI node stuck in "protocolinfo" - can't remove node

1 messages · Page 1 of 1 (latest)

grim falcon
#

Z-Wave JS UI 3.21.0
Zooz - ZST39 LR (800 Series Long Range USB Controller) - FW v1.50 , SDK v7.22.1
Home Assistant OS running on a Raspberry Pi 4 8gb (HASS Core 2025.2.5, HASS OS 14.2)

I'm having issues trying to pair a Schlage Connect (Z-Wave) touchscreen deadbolt with HASS through Z-Wave JS UI. It looks like it did not pair correctly the first times that I tried, and it created 2 nodes (Node 53 & Node 54) that are currently stuck in the Z-Wave JS UI.

I've tried removing each dead node through the "Remove Failed Nodes" action, replacing the nodes, re-interviewing them, restarting the add-on, restarting the system, etc. I get different errors in the logs:

[Node 054] The node did not respond after 1 attempts, it is presumed dead
[Node 054] ping failed: The node did not acknowledge the command (ZW0204)
...
The node replace process could not be started due to the following reasons:
· The node replace process is currently busy (ZW0362) replaceFailedNode undefined

How can I remove the nodes that are stuck? I've tried re-pairing my Schlage Connect device but its not working. From the logs it looks like it attempts to communicate with the device but immediately times out after starting to communicate with it, even when I just started inclusion mode in Z-Wave JS UI.

young zealot
plush grove
#

The last error message sounds like you are a bit too quick. Might have to do with the missing extension cable though

grim falcon
#

So I manage to add the Schlage device by doing the "replace" on node 54, and now its paired perfectly. But Im not able to get rid of the node 53 which is stuck in "protocolinfo"

#

btw, im not using an extension cord, but one of those flexible ~12 inch usb extensions

young zealot
#

not really sure what the difference is

#

some locks need to be included close to the controller and then moved back to the install location and healed (rebuild routes)

grim falcon