Devices stuck at ProtocolInfo for what seems indefinately

Configuration Z-Wave
1

Controller: Zooz 700 S2 USB Stick
Home Assistant 2023.7.3
Supervisor 2023.07.1
Operating System 10.3
Frontend 20230705.1
Z-Wave JS UI version: 1.15.1

I am running into an issue after trying to add a couple of different devices to my Home Assistant installation where they end up stuck at the ProtocolInfo step. I am unable to make them complete the setup nor am I able to remove them using the remove failed nodes option under the Advanced menu on the individual device (presumably because HA doesn’t consider them as failed yet?).

One of them is the Bali MCZ1 remote and the other was a Zooz 4-in-1 Motion sensor.

To make things even weirder, I was eventually able to add the Zooz motion sensor while one of the previous attempts to add it is still stuck at the ProtocolInfo step.

Trying to run an exclusion on the devices does not remove them from the list either. It’s just stuck there spinning at that ProtoclInfo initial step.

Any assistance with tips on how to get these removed would be greatly appreciated.

Screenshot 2023-07-24 080127
Screenshot 2023-07-24 0801272229×288 39.6 KB

2

Looks like some kind of interference.
What is your background RSSI? Should be < -80db:

grafik
grafik1598×716 273 KB

3

This is what I have for my controller, not sure if that’s at all helpful. I will say, as I mentioned in my original post, I was able to eventually add the 4-in-1 motion sensor even though my first attempt of adding it is still stuck at the ProtocolInfo attempt and I am not sure how to stop and remove it from the UI.

image
image2204×1073 476 KB

4

You cannot currently remove failed battery devices due to a bug in Z-Wave JS.

5

Well at least I now know the reason and can stop banging my head against the wall trying to figure this out.

Is there a spot currently where I can follow along and know when this bug is fixed?

6
7

A way to get rid of spinning tasks is to restart zwavejs-ui.

8

Appreciate it!

9

Already tried this actually. Nothing really stopped the tasks from spinning. I’ve tried unplugging the USB controller, restarting the Home Assistant VM, restarting just zwavejs-ui. The devices just kept on spinning and at this point I’ve been successful in actually adding the Devices to Home Assistant. It’s just that my previous attempts are still spinning and I am unable to remove them.

10

I would factory reset the controller and the devices and then try again to include the devices. In your case I would try to include them near to the conroller. And do not forget to wake up your devices(could be needed several times).

11

Thanks for the suggestion. I’ll do that if the bug doesn’t get resolved. Not looking forward to adding all the devices back in as we’ve got around 20.

Appreciate the suggestion though.

12

It’s already fixed.

Hard resetting the controller for this problem would be fine if you have just one or two devices. If you have 20, waste of time.

13

Right but it hasn’t been pushed to production yet, correct? The current version running inside of HA doesn’t have this applied yet as far as I can tell.

14

Correct, it takes time to propagate. I was just responding to the comment “I’ll do that if the bug doesn’t get resolved.” It’s resolved.

I just don’t understand why you would want to start over from scratch over this issue.

15

What I meant to say “I’ll start over once this is updated in my instance of HA and I am still having troubles with it.”

16

Gotcha, thanks.

17

This is a dumb question but is there a way to easily check what version of node-zwave-js is being used in the current release of Home Assistant?

18

There is no relationship between the HA version and node-zwave-js version, except an implicit minimum version of the zwave-js-server.

The node-zwave-js version depends on how you have installed Z-Wave JS, via add-on, docker, standalone, etc.

You can try this link for the common install options, I think it’s automatically kept up-to-date. Z-Wave JS - Which version?

19

Appreciate the link.

My particular instance is the Home Assistant OS running on a VM and Z-Wave JS UI is installed from the Home Assistant Community Add-on Store.

I’ll just keep an eye on the change log for Z-Wave JS UI updates, I am sure it’ll be mentioned there when it’s included.

20

Happy to report that with Z-Wave JS UI 1.15.2 the bug is fixed and I was able to remove to devices properly. Huzzah!

Thanks for everyone’s help!