Z-Wave failed to initialize

Hi,

I’m sure this issue have been reported a million time before, but none of the solutions found seem to apply to my situation.

I’ve been into Domotica for over 20 years now. Started with X10 (or actually Eaton’s Xanura S10), ‘upgraded’ to Z-Wave, using HomeSeer 2, 3 and 4, OpenHAS, Domoticz and some software I’ve written myself, but gave up every time due to a poorly working system. I have recently decided to give Home Assistant a try and I’m running into this problem:

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.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1226:16) (ZW0100)

I’m using an Aeotec Z-Stick Gen5 on a freshly installed Home Assistant VirtualBox VM. The logging with log level ‘Silly’ looks like this:

2023-11-19 14:22:47.243 INFO Z-WAVE: Restarting client in 15 seconds, retry 82
2023-11-19 14:23:02.311 INFO GATEWAY: Driver is CLOSED
2023-11-19 14:23:02.314 INFO Z-WAVE-SERVER: Server closed
2023-11-19 14:23:02.315 INFO Z-WAVE: Client closed
2023-11-19 14:23:02.315 INFO GATEWAY: Driver is CLOSED
2023-11-19 14:23:02.318 INFO Z-WAVE: Connecting to /dev/ttyACM0
2023-11-19 14:23:02.318 INFO Z-WAVE: Setting user callbacks
2023-11-19T13:23:02.319Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2023-11-19T13:23:02.319Z DRIVER   version 12.3.0
2023-11-19T13:23:02.319Z DRIVER   
2023-11-19T13:23:03.358Z CONFIG   version 12.3.0
2023-11-19T13:23:03.923Z CNTRLR   querying Serial API capabilities...
2023-11-19T13:23:04.927Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-11-19T13:23:06.035Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2023-11-19T13:23:08.148Z 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.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
                                  .ts:1226:16)
2023-11-19 14:23:08.150 INFO Z-WAVE: Restarting client in 15 seconds, retry 83

This same Z-Stick Gen5 works perfectly well on the same computer, running HomeSeer 4, but perhaps HomeSeer isn’t doing anything fancy with it. Also, upgrading its firmware to make in a Gen5+ resulted into the familiar error of having to push its reset button, so it was under suspicion. Unfortunately, replacing it with a brand new Gen5+, restored to the contents of the Gen5, resulted in the exact same problem.

This same Gen5 stick worked - and still works - with Home Assistant on my Reterminal, but the Reterminal has other issues. Also a brand new Gen7 stick seems to work with the Home Assistant VM, but it is not associated with anything, and I’m really not looking forward to remove 50+ switches from the walls, just to press a freaking button.

Now the Home Assistant VM did briefly work with the Gen5 Z-Stick, but stopped working after it got halfway through interviewing all nodes. I never got it to work ever since. No amount of reinstalling images helped. And now even a new stick doesn’t help, I’m out of ideas.

Does anybody here know what’s going on, how to diagnose this situation and possibly even how to fix this?

+1 after last update

2023-12-06T21:41:20.946Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2023-12-06T21:41:20.947Z DRIVER   version 12.3.0
2023-12-06T21:41:20.948Z DRIVER   
2023-12-06T21:41:20.948Z DRIVER   starting driver...
2023-12-06T21:41:20.948Z DRIVER   opening serial port /dev/serial/by-id/usb-0658_0200-if00
2023-12-06T21:41:20.956Z DRIVER   serial port opened
2023-12-06T21:41:20.958Z SERIAL » 0x15                                                                 (1 bytes)
2023-12-07 00:41:20.960 INFO Z-WAVE: Zwavejs usage statistics ENABLED
2023-12-07 00:41:20.961 WARN Z-WAVE: Zwavejs driver is not ready yet, statistics will be enabled on driver initialization
2023-12-06T21:41:21.965Z DRIVER   loading configuration...
2023-12-06T21:41:21.973Z CONFIG   Using external configuration dir /data/db
2023-12-06T21:41:21.974Z CONFIG   version 12.3.0
2023-12-06T21:41:23.316Z DRIVER   beginning interview...
2023-12-06T21:41:23.317Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2023-12-06T21:41:23.318Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2023-12-06T21:41:23.319Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2023-12-06T21:41:23.320Z DRIVER   added request handler for SerialAPIStarted (0x0a)...
                                  1 registered
2023-12-06T21:41:23.321Z CNTRLR   querying Serial API capabilities...
2023-12-06T21:41:23.328Z SERIAL » 0x01030007fb                                                         (5 bytes)
2023-12-06T21:41:23.330Z DRIVER » [REQ] [GetSerialApiCapabilities]
2023-12-06T21:41:24.337Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try I
                                  n 100 ms.
2023-12-06T21:41:24.440Z DRIVER » [REQ] [GetSerialApiCapabilities]
2023-12-06T21:41:24.442Z SERIAL » 0x01030007fb                                                         (5 bytes)
2023-12-06T21:41:25.449Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try I
                                  n 1100 ms.
2023-12-06T21:41:26.552Z DRIVER » [REQ] [GetSerialApiCapabilities]
2023-12-06T21:41:26.554Z SERIAL » 0x01030007fb                                                         (5 bytes)
2023-12-06T21:41:27.564Z 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.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
                                  .ts:1226:16)
2023-12-07 00:41:27.567 INFO Z-WAVE: Restarting client in 8 seconds, retry 4
2023-12-06T21:41:27.569Z DRIVER   destroying driver instance...
2023-12-06T21:41:27.573Z DRIVER   all queues idle
2023-12-07 00:41:35.574 INFO GATEWAY: Driver is CLOSED
2023-12-07 00:41:35.576 INFO Z-WAVE-SERVER: Server closed
2023-12-07 00:41:39.535 INFO APP: GET /health/zwave 301 3.230 ms - 191

+1… I think after the 2023.12 update, but possibly unrelated and slightly after.

Hello to all… I have exactly the same error… has any of you found the solution?? :slight_smile:
Thanks in advance,
Christian

I’m up and running again. The exact steps that got me there are amongst many failed attempts so I’m not sure precisely. What is your installation? I’m running Container on a Synology NAS and I think that was integral to my particular issues.

Hello rossco555, I’m running HAos on a Raspberry Pi4
Here is the message I get

Blockquote
2023-12-29 12:17:31.887 INFO Z-WAVE: Connecting to /dev/ttyACM0
2023-12-29T11:17:31.889Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2023-12-29T11:17:31.890Z DRIVER version 12.3.0
2023-12-29T11:17:31.890Z DRIVER
2023-12-29 12:17:32.739 INFO APP: GET /health/zwave 301 0.879 ms - 191
2023-12-29T11:17:40.909Z DRIVER Failed to open the serial port: Error: No such file or directory, cannot open
/dev/ttyACM0
2023-12-29 12:17:40.910 INFO Z-WAVE: Restarting client in 15 seconds, retry 3168
2023-12-29 12:17:55.923 INFO GATEWAY: Driver is CLOSED
2023-12-29 12:17:55.923 INFO Z-WAVE: Client closed
2023-12-29 12:17:55.924 INFO GATEWAY: Driver is CLOSED
2023-12-29 12:17:55.932 INFO Z-WAVE: Connecting to /dev/ttyACM0

Power down, remove zwave stick, restart?

Thanks @PeteRage I had tried many thing, including disconnecting and reconnecting it… And this time, doing it just like youo said (power down, disconnecting, restarting, replugging it…)… Miracle, it worked!!!
Thanks a lot! :slight_smile:

Yeah I think I was in a similar boat if it makes you feel any better. On the 400th attempt, some subtle variation of the way I pulled the stick out and put it back in again must have somehow made the difference. Frustrating, as no doubt I’ll encounter it again at the least opportune time.