I do have some troubles with the the aeotec zwave stick 7.
I do have 2 of those sticks, one normaly used, another one as backup in case the first one breaks down.
I made a nvm backup with the Simplicity Studio tool.
After that I restored that backup on the second zwave stick with that tool.
I asumed that it now would make no difference which one of the two sticks I use, but only the original one is working in HA.
When I place the copied one the connection with zwave js ui is lost.
No matter what to try: restart HA from tools inside HA, shut down on VM Virtual box and restart, restart windows10 machine: all the same result.
When I look at zwave js ui/settings/zwave, I can see that the backup stick is connected (the informtion about serial port did change to new information).
Anyone a clue what might be wrong?
Config:
ZWave js ui 3.4.1 (3.6.0 gave a load of jammed errors, but behaves on this issue the same)
VM Virtual box on windows 10 machine
|Versie |core-2024.5.3|
|Type installatie |Home Assistant OS|
|Ontwikkeling |false|
|Supervisor |true|
|Docker |true|
The log when I take out the working z-stick and bring in the restored one.
The last lines were when I brought in the original stick again:
ZWave integration is still looking for the old stick (ending on …9a97352-if00-port0). So I guess I have to tell Zwave integration somehow that there is another stick to work with. But how to do?
2024-05-17 09:03:17.182 INFO Z-WAVE: Controller status: Driver: Serial port errored: The serial port closed unexpectedly! (ZW0100)
2024-05-17 09:03:17.183 INFO Z-WAVE: Restarting client in 1 seconds, retry 1
ZWaveError: The controller is not yet ready! (ZW0103)
at Driver.get controller [as controller] (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:752:10)
at Timeout._onTimeout (/opt/server/lib/ZwaveClient.js:2831:30)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
2024-05-17 09:03:54.912 INFO Z-WAVE: Setting user callbacks
2024-05-17T07:04:01.190Z DRIVER Failed to open the serial port: Error: No such file or directory, cannot open
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f2
8a86f25ed11b80270c2f9a97352-if00-port0
2024-05-17 09:04:01.192 INFO Z-WAVE: Controller status: Driver: Failed to open the serial port: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f28a86f25ed11b80270c2f9a97352-if00-port0 (ZW0100)
2024-05-17 09:04:01.192 INFO Z-WAVE: Restarting client in 1 seconds, retry 1
2024-05-17 09:04:02.194 INFO GATEWAY: Driver is CLOSED
2024-05-17 09:04:02.195 INFO Z-WAVE: Client closed
2024-05-17 09:04:02.196 INFO GATEWAY: Driver is CLOSED
2024-05-17 09:04:02.206 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f28a86f25ed11b80270c2f9a97352-if00-port0
2024-05-17 09:04:02.209 INFO Z-WAVE: Setting user callbacks
2024-05-17T07:04:02.211Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-05-17T07:04:02.212Z DRIVER version 12.4.4
2024-05-17T07:04:02.214Z DRIVER
2024-05-17T07:04:11.244Z DRIVER Failed to open the serial port: Error: No such file or directory, cannot open
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f2
8a86f25ed11b80270c2f9a97352-if00-port0
2024-05-17 09:04:11.245 INFO Z-WAVE: Restarting client in 2 seconds, retry 2
2024-05-17 09:04:13.249 INFO GATEWAY: Driver is CLOSED
2024-05-17 09:04:13.249 INFO Z-WAVE: Client closed
2024-05-17 09:04:13.249 INFO GATEWAY: Driver is CLOSED
2024-05-17 09:04:13.255 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f28a86f25ed11b80270c2f9a97352-if00-port0
2024-05-17 09:04:13.257 INFO Z-WAVE: Setting user callbacks
2024-05-17T07:04:13.258Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-05-17T07:04:13.259Z DRIVER version 12.4.4
2024-05-17T07:04:13.259Z DRIVER
2024-05-17 09:04:19.245 INFO APP: GET /health/zwave 301 4.308 ms - 191
2024-05-17T07:04:22.289Z DRIVER Failed to open the serial port: Error: No such file or directory, cannot open
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f2
8a86f25ed11b80270c2f9a97352-if00-port0
2024-05-17 09:04:22.292 INFO Z-WAVE: Restarting client in 4 seconds, retry 3
2024-05-17 09:04:26.294 INFO GATEWAY: Driver is CLOSED
2024-05-17 09:04:26.295 INFO Z-WAVE: Client closed
2024-05-17 09:04:26.296 INFO GATEWAY: Driver is CLOSED
2024-05-17 09:04:26.310 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_141f28a86f25ed11b80270c2f9a97352-if00-port0
2024-05-17 09:04:26.315 INFO Z-WAVE: Setting user callbacks
2024-05-17T07:04:26.322Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-05-17T07:04:26.325Z DRIVER version 12.4.4
2024-05-17T07:04:26.329Z DRIVER
2024-05-17T07:04:28.432Z DRIVER no handlers registered!
2024-05-17T07:04:29.436Z CONFIG version 12.4.4
2024-05-17T07:04:30.083Z DRIVER Dropping message because the driver is not ready to handle it yet.
2024-05-17T07:04:30.561Z CNTRLR querying Serial API capabilities...
2024-05-17T07:04:30.811Z CNTRLR received API capabilities:
firmware version: 7.20
manufacturer ID: 0x00
product type: 0x04
product ID: 0x04
When I restart HA the same error shows up.
On the settings/zwave site the new stick is seen, but it cannot connect:
Yes, removed controllers several times, shutdoen HA and restart, shutdown windows PC and restart. Tried it all, nothing helped.
I don’t guess it’s the same firmware. The one that works now is recently updated to 7.20.2. The other one not yet. But the problem was there also before the update to 7.20 and at that time I guess they had the same firmware.
Simplicity Studio does not translate config between different version, Zwavejs does. Try backing up the good stick from zwavejs and restore to the other stick.
Feels somehow as a kind of problematic.
I guess I can make a nvm backup in HA (have to figure out how, but that should be not too difficult), but how do I restore it on a stick that is not seen in HA?
