search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.81k stars 30.51k forks source link

Z-Wave JS won't add new devices, all "unknown" with no entities #49114

Closed rogersmj closed 3 years ago

rogersmj commented 3 years ago

The problem

I added 7 new Inovelli Red Dimmer switches to HA this morning, along with a Cooper/Eaton RFWC5AW. After nearly an hour of waiting and a restart, none of these nodes are "ready" according to Z-Wave JS, and all of them have zero entities attached. According to the device database, these devices are supported.

I do have many other Inovelli dimmers/switches (added months ago) that are working fine. It's only the ones I attempted to add this morning that are not working. The pairing process itself seemed to go mostly fine: I used Z-Wave JS to put the controller in pairing mode, and the switches flashed green when they were successfully added. The only oddity was that after inclusion, the typical success message that Z-Wave JS would display was not shown. It just went back to the "start inclusion" screen. I figured it was a UI bug.

I started to file this over at the Z-Wave JS project but since I'm using HA apparently I'm supposed to file here first.

What is version of Home Assistant Core has the issue?

2021.4.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

rogersmj commented 3 years ago

Update: Of course, right after I file this, the nodes are starting to become ready and display entities...after an hour.

Why is this taking so long? I'm on a pretty powerful machine by HA standards (a real server, not a Raspberry Pi), in the past it's never taken more than 30-60 seconds for a new node to become available.

probot-home-assistant[bot] commented 3 years ago

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration (zwave_js) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)

raman325 commented 3 years ago

Update: Of course, right after I file this, the nodes are starting to become ready and display entities...after an hour.

Why is this taking so long? I'm on a pretty powerful machine by HA standards (a real server, not a Raspberry Pi), in the past it's never taken more than 30-60 seconds for a new node to become available.

This has nothing to do with Home Assistant or your server power, we are dependent on zwave-js marking the nodes as ready. Given that these are switches (powered by mains I assume), I can't explain why it took so long for zwave-js to communicate with the nodes and process them. Perhaps it would have gone faster if you had done one at a time? In any case, this comment should be posted to the node-zwave-js repo for further troubleshooting