-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After upgrade to higher than 3.17 - Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) #736
Comments
I have a nearly identical setup and have experienced the exact same problems. Attempting to upgrade to 3.17 or 3.18 results in inability to connect to RPI with USB stick running Ser2net (same error as mentioned "Timeout while waiting for an ACK from the controller"). Ended up having to roll back to 3.16.1 to restore connectivity. Unable to upgrade HA core due to version dependency requirements. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Has someone looked at this issue? |
I upgraded to new version 3.19.0, exactly same issue remains. 2025-01-22T11:22:04.301Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ |
Problem/Motivation
The Z-Wave integration cannot be configured because the Z-Wave JS UI Add-on cannot start the server.
I met this problem first when I tried to upgrade Z-Wave JS UI to 3.17. After upgrade the Z-Wave JS UI cannot start any more. I restored back to 3.16.1, everything works just fine.
Today I tried to upgrade to 3.18.0, then I got same problem.
Expected behavior
Z-Wave integration works.
Actual behavior
2024-12-08T15:20:52.556Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-12-08T15:20:52.557Z DRIVER version 14.3.7
2024-12-08T15:20:52.557Z DRIVER
2024-12-08T15:20:53.563Z CONFIG version 14.3.7
2024-12-08T15:20:53.975Z CNTRLR querying Serial API capabilities...
2024-12-08T15:20:54.978Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-12-08T15:20:56.082Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-12-08T15:20:58.187Z 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
:6059:23)
at ZWaveController2.queryCapabilities (/opt/node_modules/zwave-js/src/lib/
controller/Controller.ts:1144:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib
/driver/Driver.ts:1665:46)
at Immediate. (/opt/node_modules/zwave-js/src/lib/driver/Driver
.ts:1466:16)
2024-12-08 16:20:58.189 INFO Z-WAVE: Restarting client in 15 seconds, retry 381
2024-12-08 16:21:00.935 INFO APP: GET /health/zwave 301 0.452 ms - 162
2024-12-08 16:21:13.200 INFO Z-WAVE-SERVER: Server closed
2024-12-08 16:21:13.202 INFO Z-WAVE: Client closed
Steps to reproduce
My Setup is Home Assistant OS running on VirtualBox VM. Official Z-Wave JS UI Add-on installed.
The Z-Wave Gen5 Aerotek USB stick is plugged on another raspberry pi 4 and connected to Z-Wave JS via Ser2net through cabled ethernet.
After upgrade to 3.17 or 3.18, the problem showed up immediately. When restore back to 3.16.1, it works fine again.
I tried on raspberry pi:
I had successfully let the server started once by above operations. But after a restart of the Home Assistant. Z-Wave JS UI stopped again.
Proposed changes
The text was updated successfully, but these errors were encountered: