zwave not responding

[junrt]

The problem

Zwave stick gen 5 is not responding. all nodes are not reachable

What version of Home Assistant Core has the issue?

core-2024.8.2

What was the last working version of Home Assistant Core?

core-2024.8.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

OS 13.1

Link to integration documentation on our website

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

Diagnostics information

Logger: homeassistant.components.websocket_api.http.connection Bron: components/websocket_api/commands.py:241 integratie: Home Assistant WebSocket API (documentatie, problemen) Eerst voorgekomen: 17:10:12 (1 gebeurtenissen) Laatst gelogd: 17:10:12

[547089682864] Unexpected exception Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 334, in _async_set_value return await self.info.node.async_set_value( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/zwave_js_server/model/node/init.py", line 564, in async_set_value result = await self.async_send_command( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/zwave_js_server/model/node/init.py", line 522, in async_send_command return result_task.result() ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/zwave_js_server/client.py", line 131, in async_send_command return await future ^^^^^^^^^^^^ zwave_js_server.exceptions.FailedZWaveCommand: zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202)

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2763, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2806, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 999, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1071, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/zwave_js/switch.py", line 86, in async_turn_on await self._async_set_value(self._target_value, True) File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 339, in _async_set_value raise HomeAssistantError from err homeassistant.exceptions.HomeAssistantError

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[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)}}

[DereckRadford]

Same issue here.. system is dead in water with z wave.

[qelanhari]

Same for me, did look at the logs, but I rolled back core version to 2024.8.2 to fix.

[DereckRadford]

I ended up reverted but still no dice.

[qelanhari]

Had to reboot the hole HA VM afterward

[DereckRadford]

Welp unfortunately restored, rebooted completely still dead in water it wants to reconfigure the entire zwave...

2024-08-28 18:20:17.391 INFO APP: GET /health/zwave 301 2.399 ms - 191 2024-08-28T23:20:17.784Z CNTRLR querying Serial API capabilities... 2024-08-28T23:20:18.807Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i n 100 ms. 2024-08-28T23:20:19.913Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i n 1100 ms. 2024-08-28T23:20:22.022Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts :5549:23) at ZWaveController.queryCapabilities (/opt/node_modules/zwave-js/src/lib/c ontroller/Controller.ts:1014:37) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib /driver/Driver.ts:1467:46) at Immediate. (/opt/node_modules/zwave-js/src/lib/driver/Driver .ts:1271:16)

[bagl3y]

Same here with core-2024.8.3, OS 13.1 and zwave-js-ui: 9.17.0 / zwave-js: 13.1.0

I'm trying a rollback to core-2024.8.1, will see

[DereckRadford]

Same here with core-2024.8.3, OS 13.1 and zwave-js-ui: 9.17.0 / zwave-js: 13.1.0

I'm trying a rollback to core-2024.8.1, will see

So I was able to roll back to an older version and I had to switch USB ports and reboot it and now it's working.