zwave_js adds three nodes instead of one

[austinmroczek]

The problem

I ran into a weird issue today after installing a device using Smart Start.

I’m running the latest HA via HAOS and using Z-wavejsUI as an add-on.

• Core 2023.11.1
• Supervisor 2023.10.1
• Operating System 11.1
• zwave-js-ui: 9.3.1
• zwave-js: 12.2.3

I have a Zooz ZST39 LR controller stick.

I installed a Zooz Zen52 LR dual relay (and nothing else).

In Smart Start I provisioned the DSK (manually typed) in Z-wavejsUI and called it “Front Patio”. I set it for S2 Authenticated only.

Then I energized the circuit. After a while Node 073 (pretty sure this was the next available node number) was found. The interview completed. Everything looked good, except it was showing as “no security”. Then less than a minute later the node was marked as dead. Then there are a handful of “Secure inclusion started” then failed then stopped.

Then node 077 is found and interviewed. It’s the same device. Also showing as “no security.” Then it is marked as dead almost immediately.

I then went on to do other things for a few hours. I came back and now there is a new node 090, showing S2 Authentication.

What version of Home Assistant Core has the issue?

2023.11.1

What was the last working version of Home Assistant Core?

unsure

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zwave_js

Link to integration documentation on our website

No response

Diagnostics information

config_entry-zwave_js-564fc8effdabfd5359b34b4a5b16215c.json.txt

Example YAML snippet

n/a

Anything in the logs that might be useful for us?

No response

Additional information

z-ui_2023-11-04.log

zwavejs_2023-11-04.log

[home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[raman325]

You'll have to post this in zwave-js/node-zwave-js. We don't have anything to do with the actual provisioning, the driver handles all of that logic. If you can, set the driver log level to debug, remove all three devices, and then let it get provisioned again. If the same thing happens you'll have some logs that can be used to figure out what happened. If it doesnt happen again, you should still file the report, there will just be less information to work off of.

I'll leave this open in case you have questions but please close this when you open the new issue

[kpine]

Driver v12.3.0 might already have a fix for this.

Auto-remove failed SmartStart nodes when bootstrapping times out (zwave-js/node-zwave-js#6483)

[austinmroczek]

You'll have to post this in zwave-js/node-zwave-js. We don't have anything to do with the actual provisioning, the driver handles all of that logic. If you can, set the driver log level to debug, remove all three devices, and then let it get provisioned again. If the same thing happens you'll have some logs that can be used to figure out what happened. If it doesnt happen again, you should still file the report, there will just be less information to work off of.

I'll leave this open in case you have questions but please close this when you open the new issue

Posted as zwave-js/node-zwave-js#6495. Thanks!