After an update of both Unraid and HomeAssistant my Aeotec Z-Stick Gen5 will no longer stay connected to the HA VM running on Unraid.
If I boot up the VM without any USB devices connected, and then select the Z-Stick in Unraid, HomeAssistant shows the following logs:
Jan 17 19:24:47 homeassistant kernel: usb 2-1: new full-speed USB device number 7 using uhci_hcd
Jan 17 19:24:47 homeassistant kernel: usb 2-1: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Jan 17 19:24:47 homeassistant kernel: usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 17 19:24:47 homeassistant kernel: cdc_acm 2-1:1.0: ttyACM0: USB ACM device
Jan 17 19:24:50 homeassistant kernel: usb 2-1: USB disconnect, device number 7
As you can see the USB device is initially recognized as ttyACM0, but disconnects after 3 seconds every time. During those 3 seconds it can also be seen in the āAll Hardwareā list with the serial path /dev/serial/by-id/usb-0658_0200-if00
.
In comparison, this is what the logs look like for my working SONOFF ZigBee Dongle:
Jan 17 19:25:39 homeassistant kernel: usb 3-1: new full-speed USB device number 2 using uhci_hcd
Jan 17 19:25:39 homeassistant kernel: usb 3-1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Jan 17 19:25:39 homeassistant kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 17 19:25:39 homeassistant kernel: usb 3-1: Product: Sonoff Zigbee 3.0 USB Dongle Plus
Jan 17 19:25:39 homeassistant kernel: usb 3-1: Manufacturer: ITead
Jan 17 19:25:39 homeassistant kernel: usb 3-1: SerialNumber: 261cbfcf63c9eb118ea98d4f1d69213e
Jan 17 19:25:39 homeassistant kernel: usbcore: registered new interface driver cp210x
Jan 17 19:25:39 homeassistant kernel: usbserial: USB Serial support registered for cp210x
Jan 17 19:25:39 homeassistant kernel: cp210x 3-1:1.0: cp210x converter detected
Jan 17 19:25:39 homeassistant kernel: usb 3-1: cp210x converter now attached to ttyUSB0
I also tried passing the Z-Stick through to another random Ubuntu VM I had lying around, and it stayed connected even after 30+ seconds, with the logs looking like this:
Jan 17 20:30:58 randomvm kernel: [ 2691.512901] usb 2-2: new full-speed USB device number 2 using uhci_hcd
Jan 17 20:30:58 randomvm kernel: [ 2691.684024] usb 2-2: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Jan 17 20:30:58 randomvm kernel: [ 2691.684030] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 17 20:30:58 randomvm kernel: [ 2691.699414] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
Jan 17 20:30:58 randomvm kernel: [ 2691.699432] usbcore: registered new interface driver cdc_acm
Jan 17 20:30:58 randomvm kernel: [ 2691.699433] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
So I donāt think itās a problem with my Unraid setup, as the stick can obviously stay connected to other VMs.
Other things Iāve tried that made no difference:
- Using a direct USB port instead of an extension cable
- Using both a 2.0 and 3.0 port
- Passing the USB port through to the VM before boot and while itās already running.
- Restarting the physical Unraid server
- Factory Resetting the Z-Stick
Thing I havenāt tried yet (cause theyād be really annoying lol)
- Setting up a completely new HA VM
- Installing a dedicated PCI USB card
- Buying a new Z-Stick
Relevant versions:
HA Core: 2024.1.3
HA Supervisor: 2023.12.1
HA Operating System: 11.4
Unraid: 6.12.6