ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)

[greyltc]

Describe the issue

Hi, I'm having trouble with https://github.com/zwave-js/node-zwave-js/blob/master/packages/flash/README.md

Do I first have to put the stick in bootloader mode or something for this to work?

$ npx @zwave-js/flash@latest /dev/ttyACM0 ZST39_SDK_7.22.0_US-LR_V01R40.gbl --verbose
Starting driver...
12:49:35.423 DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                      ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                        ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                       ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                      ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                      ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
12:49:35.425 DRIVER   version 13.2.0
12:49:35.425 DRIVER   
12:49:35.425 DRIVER   starting driver...
12:49:35.425 DRIVER   opening serial port /dev/ttyACM0
12:49:35.434 DRIVER   serial port opened
12:49:35.435 SERIAL » 0x15                                                                 (1 bytes)
12:49:36.437 DRIVER   beginning interview...
12:49:36.438 DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                      1 registered
12:49:36.439 DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                      1 registered
12:49:36.439 DRIVER   added request handler for ReplaceFailedNode (0x63)...
                      1 registered
12:49:36.440 CNTRLR   querying Serial API capabilities...
12:49:36.527 SERIAL » 0x01030007fb                                                         (5 bytes)
12:49:36.528 DRIVER » [REQ] [GetSerialApiCapabilities]
12:49:37.532 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:49:37.633 DRIVER » [REQ] [GetSerialApiCapabilities]
12:49:37.633 SERIAL » 0x01030007fb                                                         (5 bytes)
12:49:38.636 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
12:49:39.738 DRIVER » [REQ] [GetSerialApiCapabilities]
12:49:39.738 SERIAL » 0x01030007fb                                                         (5 bytes)
12:49:40.743 DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                      from the controller (ZW0200)
                          at Driver.sendMessage (~/.npm/_npx/7690b5c31200d08c/node_modules/
                      zwave-js/src/lib/driver/Driver.ts:5549:23)
                          at ZWaveController.queryCapabilities (~/.npm/_npx/7690b5c31200d08
                      c/node_modules/zwave-js/src/lib/controller/Controller.ts:1014:37)
                          at Driver.initializeControllerAndNodes (~/.npm/_npx/7690b5c31200d
                      08c/node_modules/zwave-js/src/lib/driver/Driver.ts:1467:46)
                          at Immediate.<anonymous> (~/.npm/_npx/7690b5c31200d08c/node_modul
                      es/zwave-js/src/lib/driver/Driver.ts:1271:16)

Software versions

version 13.2.0
(that's what npx @zwave-js/flash@latest pulls on August 14th, 2024)

Device information

Manufacturer: Zooz
Model name: 800 Z-Wave Stick (ZST39 LR)
USB vendor id = 0x1A86
USB product id = 0x55D4

Journal prints when I plug in the stick:

Aug 14 12:42:55 box kernel: usb 1-13: USB disconnect, device number 5
Aug 14 12:42:57 box kernel: usb 1-13: new full-speed USB device number 6 using xhci_hcd
Aug 14 12:42:57 box kernel: usb 1-13: New USB device found, idVendor=1a86, idProduct=55d4, bcdDevice= 4.43
Aug 14 12:42:57 box kernel: usb 1-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 14 12:42:57 box kernel: usb 1-13: Product: 800 Z-Wave Stick
Aug 14 12:42:57 box kernel: usb 1-13: Manufacturer: Zooz
Aug 14 12:42:57 box kernel: usb 1-13: SerialNumber: REDACTED
Aug 14 12:42:57 box kernel: cdc_acm 1-13:1.0: ttyACM0: USB ACM device

[zwave-js-bot]

👋 Hey @greyltc!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[AlCalzone]

I believe you've gotten further with some assistance on Discord? Do we need this issue?

[greyltc]

This issue shows what zwave-js does when it tries to talk to a bricked stick (serial API not running on the stick's microcontroller). In this case my stick was "bricked" when I downgraded a Zooz ZST39 800 LR stick from

Firmware 1.40 (based on SDK 7.22.0)
https://www.getzooz.com/firmware/ZST39_SDK_7.22.0_US-LR_V01R40.zip

to

Firmware 1.30 (based on SDK 7.21.3)
https://www.getzooz.com/firmware/ZST39_SDK_7.21.3_US-LR_V01R30.zip

Here I was trying to re-upgrade the firmware in an attempt to unbrick it, but this same issue happens no matter what zwave-js tries to do with a stick in such a state.

The bricking turns out to not really be a zwave-js bug per se, except that maybe you could refuse to actually do such a downgrade or something.

[AlCalzone]

The bootloader should be the one preventing the downgrade, as it should know better what's compatible and what isn't. In this case the default downgrade prevention was disabled in the firmware.