Zwave stops responding after upgrade to 2024.9.0

[homeautomator2]

The problem

I have a large Zwave install. Everything was working normally this am. I upgraded to 2024.9.0 and suddenly, none of my zwave devices were responding. There were no entries in the logbook that I could find.

I was/am concerned this might be the dreaded issue with the Zwave firmware bug. First, i tried restarting HA. no good. Then reboot. no good. finally shut the system down, and removed power. Waited 1 min, then powered back up. Got 1 device to respond, then none others.

I subsequently backed out of the upgrade, going back to 2024.8.3 and after a shut down/power cycle, the system came back up and is working normally.

What version of Home Assistant Core has the issue?

2024.9.0

What was the last working version of Home Assistant Core?

2024.8.3

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

not that i can find so far

Additional information

System Information version | core-2024.8.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.46-haos arch | aarch64 timezone | America/Phoenix config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.1 Stage | running Available Repositories | 1460 Downloaded Repositories | 13

Home Assistant Cloud

logged_in | true -- | -- subscription_expiration | November 8, 2024 at 5:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | us-east-1-8.ui.nabu.casa certificate_status | ready instance_id | 75abc7a77f2d450fb00c5d11205b5162 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.08.0 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 1833.7 GB disk_used | 59.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | odroid-n2 supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), Spotify Connect (0.13.0), Terminal & SSH (9.14.0), Mosquitto broker (6.4.1), Z-Wave JS UI (3.10.0), ESPHome (2024.8.3), Rclone Backup (3.3.1), Studio Code Server (5.15.0)

Dashboards

dashboards | 6 -- | -- resources | 4 views | 15 mode | storage

Recorder

oldest_recorder_run | August 26, 2024 at 3:22 AM -- | -- current_recorder_run | September 4, 2024 at 11:56 AM estimated_db_size | 189.92 MiB database_engine | sqlite database_version | 3.45.3

Spotify

api_endpoint_reachable | ok -- | --

[home-assistant[bot]]

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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[forrestjr]

My Zwave has stopped working as well...and I have other issues too. Not sure what is going on, but something is funky and my HA will just stop working after several hours of clean operation.

[TomJensen6678]

Problem solved, had to stop -JS and pull the USB unit out, incert it again and start -JS.

All my light switches has stopped working, but sensors is wotking, -jS i started and now errors. Have about 20 switches that stopped working and 10 that works, but no lights are working. What ever I do nothing happens with the light switches, restarted HA, done reload on -JS and so on. This is what the log say: [Node 014] failed to refresh values for Multilevel Sensor CC: Failed to send the command after 3 attempts. Transmission queue full (ZW0202)

[raman325]

My Zwave has stopped working as well...and I have other issues too. Not sure what is going on, but something is funky and my HA will just stop working after several hours of clean operation.

it sounds like you have a bigger problem than the z-wave integration which you need to fix first before you can figure out whether there is a legitimate issue