ZWave Controller Issue

Configuration Z-Wave
1

Hello,
I’m running HA version on Raspberry Pi 5.

  • Core: 2024.8.1
  • Supervisor: 2024.08.0
  • Operating System: 13.0
  • Interface utilisateur: 20240809.0
    For zwave I’m using an Aeotec Gen 5 Zwave stick and Fibaro devices.
    I’m using the add-on Z-Wave JS (Current version: 0.6.2) and the Zwave integration.
    At one point it stopped working and I could not reach my devices at all.
    I’ve tried:
  • to restart HA.
  • To unplung and replug the Aeotec stick
  • To restart Z-Wave JS.
  • To reinstall Z-Wave JS.
  • To also reinstall the integration.
  • To reload the Zwave Network.
  • To Rebuild Network route.
  • To Re-Configure the server.
  • I also reinstalled HA from scratch.
    I’d like to avoid to restet the Aeoted stick and to have to add again all the device.
    Please find below what I have in the logs:
    2024-08-14T13:41:48.758Z CNTRLR [Node 007] The node did not respond after 1 attempts, it is presumed dead
    2024-08-14T13:41:48.759Z CNTRLR [Node 007] The node is dead.
    2024-08-14T13:41:48.762Z CNTRLR [Node 007] ping failed: The node did not acknowledge the command (ZW0204)
    2024-08-14T13:41:48.762Z CNTRLR » [Node 007] querying node info…
    2024-08-14T13:42:18.780Z CNTRLR The controller is unresponsive
    2024-08-14T13:42:18.781Z DRIVER Controller missed Send Data callback. Attempting to recover…
    2024-08-14T13:42:18.782Z CNTRLR Performing soft reset…
    2024-08-14T13:42:19.787Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
    n 100 ms.
    2024-08-14T13:42:20.890Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
    n 1100 ms.
    2024-08-14T13:42:22.995Z CNTRLR Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
    0)
    2024-08-14T13:42:22.996Z DRIVER Automatic controller recovery failed. Returning to normal operation and hoping
    for the best.
    2024-08-14T13:42:22.997Z CNTRLR The controller is no longer unresponsive
    2024-08-14T13:42:22.998Z CNTRLR [Node 018] ping failed: Timeout while waiting for a callback from the controll
    er (ZW0200)
    2024-08-14T13:42:22.998Z CNTRLR » [Node 018] querying node info…
    2024-08-14T13:42:24.003Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
    n 100 ms.
    2024-08-14T13:42:25.107Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
    n 1100 ms.
    2024-08-14T13:42:27.211Z CNTRLR The controller is unresponsive
    2024-08-14T13:42:27.211Z DRIVER Attempting to recover unresponsive controller by restarting it…
    2024-08-14T13:42:27.212Z CNTRLR Performing soft reset…
    2024-08-14T13:42:28.217Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
    n 100 ms.
    2024-08-14T13:42:29.321Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
    n 1100 ms.
    2024-08-14T13:42:31.424Z CNTRLR Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
    0)
    2024-08-14T13:42:31.425Z DRIVER Attempting to recover unresponsive controller by reopening the serial port…
    2024-08-14T13:42:31.426Z CNTRLR [Node 031] ping failed: Timeout while waiting for an ACK from the controller (
    ZW0200)
    2024-08-14T13:42:31.426Z CNTRLR » [Node 031] querying node info…

When I restart the add-on:
2024-08-14T14:47:13.841Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-08-14T14:47:13.843Z DRIVER version 12.11.2
2024-08-14T14:47:13.844Z DRIVER
2024-08-14T14:47:14.870Z CONFIG version 12.11.1
2024-08-14T14:47:15.378Z CNTRLR querying Serial API capabilities…
2024-08-14T14:47:16.544Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-08-14T14:47:17.647Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-08-14T14:47:19.756Z 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:5450:23)
at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/l
ib/controller/Controller.ts:1007:37)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
/lib/driver/Driver.ts:1475:46)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
iver.ts:1276:16)
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:5450:23)
at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:1007:37)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1475:46)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1276:16) (ZW0100)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1296:6) {
code: 100,
context: undefined,
transactionSource: undefined
}
Shutting down
[14:47:25] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Could you please help me to solve this issue.
Thank you very much in advance for your help.

2

First thing I’d check is to make sure you’re referencing the USB stick with it’s persistent name, sometimes called ‘serial-by-id’. If you’re referencing it with something like ‘/dev/ttyUSB#’ or ‘/dev/ttyACM#’, the number at the end may or may not point to the same USB device between restarts/reboots.

For example, I reference my USB stick as ‘/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_813009F7-if00-port0’.

4

Are you sure you are not running both zwavejs and the zwavejsui add on at the same time?

Try to check that device path from the console. Is it actually at that path?

Try a different USB port

The gen5 stick has problems with some USB ports, I run mine on a usb 2.0 hub. Are you running it on a hub with an extender?

5

Thanks for your answer.

I only have Zwavejs, zwawejsui is not even installed.

I checked that the device path in the add on is the same as the one listed in the hardware tab.

To plug the gens stick I do not use any hub or extender,I plug it directly on the RPI 5.

I tried the 4 USB ports, each time reinstalling the Zwave integration and the add on but I still have the same issue.

I do not have any automation so far which could overload the network, I even tried to downgrade the HA OS and the core version but it did not changed anything.

Any other idea to fix this issue.

7

Thanks for your answer.
I’m using the ID: /dev/serial/by-id/usb-0658_0200-if00

8

I’ve just tried running it with a USB extender cable , I’ve also rebuilt network route after adding the extender but I still have the same issue. Any other ideas?

9

I too am seeing these errors in the last few weeks - it works fine for a few hours/days and then i start to see the errors and devices not responding.

I also use a Aeotech Gen5 Zstick
Config is
/dev/serial/by-id/usb-0658_0200-if00

Its connected to small form factor PC , no usb extention leads. I’ve tried changing USB ports but this doesnt appear to have helped. I will try using a USB2 hub and see what happens.

After ~20hrs still not working reliably: here is some content from my log:

2024-08-29T22:14:46.663Z CNTRLR » [Node 016] pinging the node...
2024-08-29T22:14:47.519Z CNTRLR   [Node 031] failed to refresh values for Meter CC: Failed to send  [Endpoint 2]
                                  the message after 3 attempts (ZW0202)
2024-08-29T22:14:47.524Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-08-29T22:14:47.626Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2024-08-29T22:14:48.731Z CNTRLR   [Node 016] ping failed: Failed to send the message after 3 attempts (ZW0202)
2024-08-29T22:14:50.772Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-08-29T22:14:50.878Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
Z-Wave error ZWaveError: Failed to send the message after 3 attempts (ZW0202)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5450:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5648:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5758:29)
    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)
    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1182:39)
    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:19:43)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:92)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:134:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:66:45) {
  code: 202,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5450:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5648:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5758:29)\n' +
    '    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)\n' +
    '    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1182:39)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:19:43)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:92)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:134:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:66:45)'
}