Z-wave stopped working after pulling/plugging different USB device

Configuration Z-Wave
1

I’m using the Aeotec Z-wave stick (gen5) which has been working well for years.

I had to remove another USB stick (ConBee II), which I then reinserted and rebooted the computer. After this, the Z-wave network no longer starts. I get this in the OZW log:

2020-11-29 14:35:19.980 Always, OpenZwave Version 1.4.3469 Starting Up
2020-11-29 14:35:59.266 Info, Setting Up Provided Network Key for Secure Communications
2020-11-29 14:35:59.266 Info, mgr,     Added driver for controller /dev/serial/by-id/usb-0658_0200-if00
2020-11-29 14:35:59.266 Info,   Opening controller /dev/serial/by-id/usb-0658_0200-if00
2020-11-29 14:35:59.266 Info, Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1)
2020-11-29 14:35:59.269 Info, Serial port /dev/serial/by-id/usb-0658_0200-if00 opened (attempt 1)
2020-11-29 14:35:59.269 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-11-29 14:35:59.269 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-11-29 14:35:59.269 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-11-29 14:35:59.269 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-11-29 14:35:59.269 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-11-29 14:35:59.269 Detail,
2020-11-29 14:35:59.269 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-11-29 14:36:00.269 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-11-29 14:36:00.269 Detail, contrlr, Removing current message
2020-11-29 14:36:00.269 Detail, contrlr, Notification: Notification - TimeOut
2020-11-29 14:36:00.270 Detail,

I didn’t touch the Z-wave USB stick. I have rebooted before, though it’s been a while, with no issues (since I started using UUID instead of /dev/ttyACMx path). The only difference I can think of is that I removed the ZigBee stick, but I put it back, and have rebooted the computer, so not sure why that should matter?

The Zwave stick (and ZigBee stick) show up in CLI, and the ZigBee stick works fie with HASS again. Only the stick I didn’t touch gives problems…

Oh, and there’s nothing in HASS logs about this.

EDIT: The .storage/core.config_entries had "usb_path": "dev/ttyACM0" (which was wrong), but manually changing that to eith "usb_path": "dev/ttyACM0" (correct) or "usb_path": "/dev/serial/by-id/usb-0658_0200-if00" and restarting HASS didn’t help.

My zwave config is pretty basic, and not changed from when it last worked:

zwave:
    usb_path: !secret aeotec-z-wave-stick
    network_key: !secret secure_z_wave_key

where !secret aeotec-z-wave-stick is the /dev/serial/by-id/usb-0658_0200-if00

2

Have you re-inserted the Aeotec stick? Is it maybe in an inclusion mode if you hit the physical button? Is there any possibility some other process is using the stick? (Maybe experimented with the OZW Beta or Zwave2MQTT addons?)

3

I haven’t touched the Aeotec stick (or even accessed that side of the server, or any other cable/USB/anything) in over 6 months. I haven’t experimented with anything Z-wave (OZW, etc.), since it’s been running fairly smooth for >3 years now.

What finally did work was when I unplugged the ZigBee stick again (to add a long overdue USB extension). Once I restarted after having unplugged and re-plugged the ZigBee stick, the Z-wave network came up again. The ZigBee stick is at the front, the Z-wave stick at the back of the server, so I didn’t accidentally touch/push/move/wiggle the Z-wave stick while messing with the ZigBee stick.

Seriously odd. But at least I have a Z-wave network again.