core: Zooz ZST10 Z-Wave USB no longer seen by Z-Wave.js after upgrade to current HomeAssistant OS

There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

I had a similar problem after updating to 2023.3.1. My setup uses two dongles, one for Z-Wave and another for Zigbee, communicating with a serial port like /dev/ACM0 and /dev/ACM1 respectivelly. After a reboot serial ports mixed up and services were communicating with the wrong devices…

Restarting HA and pluging dongles in the right order fixes the issue… until the next unplaned restart.

HA doesn’t seem to use udev which means to keep serial port names persistant after reboot, one needs an unique device path like /dev/serial/by-id/usb-1324-5678-WHATEVER-THE-DRIVER-SAYS

For Z-wave instead of:

I use:

And ZHA already uses a persistant path (found in core.config_entries). Updating my naive setup seems to fix the issue with both services.

Gave it another try tuesday. Went from OS9.0 -> OS9.3 and core to 10.5 I only received errors at startup. I reconnected the usb-stick a few minutes after start-up. After that zwave-js started normally. Today still without problems. To me this looks like some inrush problem with zwave. Maybe the number of devices, integrations or addons of the install has something to do with this zwave strangeness.

If you power-cycle the entire device (i.e. without unplugging, waiting, and plugging things back in), does it work or you have to unplug, wait, and plug back in every time the host hardware is rebooted?

I used hassio.host_shutdown, completely powered off and on again. Everything came on-line and worked. No errors in the log. NB i have a different z-wave stick than the one you have.

I had this issue, and the instructions that @gbrandsma noted didn’t work for me. However when I went to addons -> Z-wave JS -> configuration, none of the “device” radio buttons were selected. I selected the one as per this:

Device
[ ] /dev/ttyAMA0
[ ] /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2293321-if00
[X] /dev/serial/by-id/usb-0658_0200-if00

then clicked save. It said it needed to restart addon to apply, so I said yes, then the logs looked like success.

Best guess is that device ID changed between the upgrade, and the config had the old one… ?

Good luck!

Full exact list of what I did:

1. Followed instructions as per post by @gbrandsma
2. Saw addon was stopped, so attempted to start, each time got error similar (but I don’t think identical) to what @gbrandsma had
3. Disabled Z-wave JS integration
4. Went to addon config and selected the conbee stick (yep that was dumb selecting my zigbee stick), and starting it didn’t work
5. Went back to addon config and selected the option as per above, upon saving it asked to restart, and I clicked yes
6. Looked at logs and saw everything saying success
7. Went back and re-enabled the Z-wave JS integration
8. Saw all my Z-wave devices were back

Can you try downgrading the OS to see it’s indeed the OS? In the Terminal:

ha os update --version 9.0

I’m still experiencing this issue. After fixing it will work for some time but fails again. Have restarted this 4 times today.

The interesting part in my Z-WaveJS log:

2022-10-12T15:45:41.808Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-10-12T15:45:41.924Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2022-10-12T15:45:43.037Z CNTRLR   [Node 019] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-10-12T15:45:43.470Z DRIVER   Dropping message with invalid payload
2022-10-12T15:45:43.552Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-10-12T15:45:43.661Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
Z-Wave error ZWaveError: Failed to send the command after 3 attempts. Transmission queue full (ZW0202)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4181:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4296:15)
    at Proxy.get (/usr/src/node_modules/@zwave-js/cc/src/cc/ManufacturerSpecificCC.ts:106:24)
    at ZWaveController.getAvailableFirmwareUpdates (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:4523:5)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:204:54)
    at Object.controller (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:103)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:105:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:49:45)
    at WebSocket.emit (node:events:513:28) {
  code: 202,
  context: SendDataResponse {
    host: [Driver],
    type: 1,
    functionType: 19,
    payload: <Buffer 00>,
    wasSent: false
  },
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4181:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4296:15)\n' +
    '    at Proxy.get (/usr/src/node_modules/@zwave-js/cc/src/cc/ManufacturerSpecificCC.ts:106:24)\n' +
    '    at ZWaveController.getAvailableFirmwareUpdates (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:4523:5)\n' +
    '    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:204:54)\n' +
    '    at Object.controller (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:103)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:105:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:49:45)\n' +
    '    at WebSocket.emit (node:events:513:28)'
}