This just started happening after updating Home Asistant and Home Assistant OS a couple days ago. It was woirking fine before this.
Home Assistant OS is running in a VirtualBox VM. The z-wave controller is an Aotec Z-stick 7. Yes, the USB pass through is working. Home Assistant sees it just fine as /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_3a2ea055c0e5ea11ae1084d5994a5d01-if00-port0 and it is selectable in the z-wave js configuration. The following is the error I see:
2021-12-19T15:56:43.726Z DRIVER
2021-12-19T15:56:50.480Z CONFIG version 8.8.3
2021-12-19T15:56:54.627Z CNTRLR querying controller IDs...
2021-12-19T15:56:55.768Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-12-19T15:56:56.872Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-12-19T15:56:58.989Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive
r.ts:3261:23)
at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro
ller/Controller.ts:668:33)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
/lib/driver/Driver.ts:938:26)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
iver.ts:818:16)
Shutting down
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3261:23)
at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:668:33)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:938:26)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:818:16) (ZW0100)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:835:6) {
code: 100,
context: undefined,
transactionSource: undefined
}
And system info:
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
user: root
virtualenv: false
python_version: 3.9.7
os_name: Linux
os_version: 5.10.83
arch: x86_64
I can tell you I just experienced something similar and it was absolutely the Aeotec stick. Same basic error messages, constant Z-Wave issues for the past month or two and I went through everything to try to fix it:
Replace powered USB hub the stick plugs into
Upgrade from SD to SSD to see if maybe a failing SD was the root
Replacing the rPi power supply
Replacing the rPi entirely
I did those things knowing that the stick was probably at fault, but since Amazon told me it was 2+ months to get a new stick I had little choice. By some remote miracle, I got the stick yesterday and today I woke up and my old z-stick failed entirely. I was able to fiddle it back into be recognized on my Mac so I could use the Aeotec Backup to back it up and restore it to a new one. Now there are no errors and it runs significantly faster. I’m going to go ahead and call this a Christmas Miracle!
Now my stick was the first release of Gen5, and that was upgraded from the Gen3, so it was probably 5+ years old, but in the end the stick was absolutely my problem. Perhaps it is yours as well?
I really hope that isn’t the case. This entire setup is only a few months old and the stick wasn’t even one of the first things I ordered or setup for it. It would be really disappointing if it failed so soon.
I am having the same issue. I unplugged, re-plugged, rebooted HA. No luck.
zwave-js-ui: 9.3.2
zwave-js: 12.3.0
home id: undefined
home hex: undefined
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:5240:23) at ZWaveController.identify (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:897:37) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1432:26) at Immediate. (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1226:16) (ZW0100)
Error: 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:5240:23) at ZWaveController.identify (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:897:37) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1432:26) at Immediate. (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1226:16) (ZW0100)
Any advice on how to resolve?
I am also seeing the following:
Logger: homeassistant.setup
Source: setup.py:221
First occurred: 4:11:07 PM (1 occurrences)
Last logged: 4:11:07 PM
Setup failed for ‘zwave’: Integration not found.
If I attempt to install the integration, it fails.
Updated add-on today and see the same / similar error messages:
2024-01-17T02:36:33.150Z CONFIG version 12.4.1
2024-01-17T02:36:34.838Z CNTRLR querying Serial API capabilities...
2024-01-17T02:36:35.861Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-01-17T02:36:36.975Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-01-17T02:36:39.094Z 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
:5256:23)
at ZWaveController.identify (/opt/node_modules/zwave-js/src/lib/controller
/Controller.ts:897:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib
/driver/Driver.ts:1432:26)
at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
.ts:1226:16)
Same here since yesterday…
Didn’t update anything in between turning on my coffee machine and when wanting it to turn off Zwave was completely unavailable.
Using a Zwave.me usb stick
Downgraded everything, upgraded everything.
rebooted 200 times
plugged usb in different port
plugged it back
tried everything?
It seems to work fine on my laptop. So I tried updating bootload & firmware. Update did well, but no luck getting it working on my HA Yellow.
It’s detected on my proxmox box, so I manage to get it detected on HA Hardware by using USB over IP. It’s working fine for now, but I purchased a new dongle just in case.
It was all working fine until I rebooted the entire yellow box. It was not during an update of any king (I deactivated the auto-update of ZWave-JS). I really wonder what went wrong here.
Somehow got it working again.
Removed all usb’s (zigbee/P1/Zwave) and rebooted.
Then plugged in all usb’s again - in different ports then they were before. Rebooted again.
Everything works like a charm again.
Came here to say I just had this as well. Started right after the HA OS update.
Noticed my ZigBee/sky connect was also having issues. Since the sky connect was a recent addition, I flipped the devices USB ports and rebooted. It seems HA was trying to connect to the serial port (ttyUSB0 If I remember correctly) of the wrong device which was rectified by simply changing the USB port so it would see them in physical (USB port) order of when they were installed.
May this update show others a possible conflict of serial devices to rectify their issues.
Just experienced this as well but not immediately after any particular update. I’m running Home Assistant in a docker container with Z-Wave JS in a separate container. I updated HA and Z-Wave JS to the latest version yesterday and everything was fine, but randomly at some point today all of my Z-Wave devices stopped responding and I saw this error message in Z-Wave JS. Tried restarting both HA and Z-Wave JS but no change, but after unplugging and re-plugging in my Zooz 700-series Z-Wave USB dongle, everything started working again.
A little late, but I also have the ZAC93 and started getting this yesterday after an update. The fix that worked for me was similar to those above – basically, disconnect, do a power cycle, and then reconnect the controller.
2024-06-04 21:27:19.700 INFO Z-WAVE: Connecting to /dev/ttyAMA0
2024-06-04 21:27:19.701 INFO Z-WAVE: Setting user callbacks
2024-06-05T01:27:19.702Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-06-05T01:27:19.703Z DRIVER version 12.9.1
2024-06-05T01:27:19.703Z DRIVER
2024-06-05T01:27:19.704Z DRIVER starting driver...
2024-06-05T01:27:19.704Z DRIVER opening serial port /dev/ttyAMA0
2024-06-05T01:27:19.710Z DRIVER serial port opened
2024-06-04 21:27:19.998 INFO APP: GET /health/zwave 301 1.429 ms - 191
2024-06-05T01:27:20.715Z DRIVER loading configuration...
2024-06-05T01:27:20.719Z CONFIG version 12.9.1
2024-06-05T01:27:21.881Z DRIVER beginning interview...
2024-06-05T01:27:21.882Z DRIVER added request handler for AddNodeToNetwork (0x4a)...
1 registered
2024-06-05T01:27:21.883Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2024-06-05T01:27:21.883Z DRIVER added request handler for ReplaceFailedNode (0x63)...
1 registered
2024-06-05T01:27:21.884Z DRIVER added request handler for SerialAPIStarted (0x0a)...
1 registered
2024-06-05T01:27:21.885Z CNTRLR querying Serial API capabilities...
2024-06-05T01:27:21.889Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-06-05T01:27:22.893Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-06-05T01:27:22.995Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-06-05T01:27:24.001Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-06-05T01:27:25.104Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-06-05T01:27:26.108Z 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
:5349:23)
at ZWaveController.queryCapabilities (/opt/node_modules/zwave-js/src/lib/c
ontroller/Controller.ts:970:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib
/driver/Driver.ts:1458:46)
at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
.ts:1259:16)
2024-06-04 21:27:26.110 INFO Z-WAVE: Restarting client in 15 seconds, retry 8
2024-06-05T01:27:26.112Z DRIVER destroying driver instance...
2024-06-05T01:27:26.114Z DRIVER driver instance destroyed
2024-06-04 21:27:41.115 INFO Z-WAVE-SERVER: Server closed
2024-06-04 21:27:41.116 INFO Z-WAVE: Client closed
What fixed it:
Shut down the HASS device.
Disconnect the physical Z-Wave controller (disconnect the ZAC93 GPIO module, in my case).
Turn on the HASS device. Wait for it to fully start up.
Shut down the HASS device again.
Reconnect the physical Z-Wave controller.
Turn on the HASS device. Confirm Z-Wave JS is able to reach the controller again.
Unfortunately I run into the same problem and error. But this trick does not work out. The malfunction of the z-wave network started after the recent updates of HA core and zwave-JS.
Any other suggestions to help me with this issue?
Thanks