I migrated all of my Zigbee Devices to Zigbee2MQTT and it had been working fine. Recently it started to become unstable and it appears I’m having issues with my HASS.IO VM losing connection to the USB Port. I need help badly to get it all operating.
I’m running to current patch of hassio on a VM running on an ESXI 6.7 host. I’ve had USB passthrough working fine before, so I don’t think that’s the issue (I hope not anyway). On the cole, I’m getting a message pop up … cdc_acm 2-2.1:1.0: failed to sdet dtr/rts …seemingly each time I lose connection to the USB port.
I’m not really much of a Linux person, so I’m not entirely sure what that message means. It was working fine for a while. I think I can attribute the instability to losing connection to the zigbee2MTTT controller, but I can’t be sure. I really don’t want to go back to using SmartThings. Can someone help?
I’m having the same issue. Using a CC2531 controller and HassOS in a VM on Windows 10.
The Windows 10 device manager states that the USB “device descriptor request failed”.
Initially this seemed to be related to USB power management. Disabling various USB sleep options seemed to work for a short time but now it’s back to being incredibly unstable and only lasts for a few minutes before getting that error again.
I’m going to try a fresh VM and I’ve also ordered a different controller so I can test.
I know this is an old thread, but this is also happening to me. It happened yesterday, and a few months earlier.
My setup uses an intel nuc, proxmox and haos 15.2.
Yesterday, even a full system reboot wouldn’t resolve. It impacts an aeotec 7 usb z-wave controller, sonoff zigbee controller and a video processor.
I was ready to reinstall ha on a new ssd yesterday, taken a backup of my setup, had stripped down the nuc, taken out the ssd to replace with a larger one, and installed the new drive. Only because of my automations missing from the backup, I went back to my original disc. Lo and behold, the usb devices were back! They’ve been fine over night, but who knows when they’ll go again. We have a couple of areas in the house, where it is critical that they are handled in a resilient manner, so these have now moved to Wi-Fi devices, as these seem more stable.
Has anyone found the root cause for these usb devices disappearing? I don’t think it’s got anything to do with proxmox, as I’ve had the same happen with a baremetal ha install, and also on a raspberry pi. Would love to get this resolved once and all.
I guess it’s too late to ask if the devices were detected inside proxmox. If they weren’t, this would point to a hardware issue.
More likely, though, is that what you’re describing sounds suspiciously like the device path changed. The below is from the ZHA docs, but applies to any USB to serial device:
Most devices need at the very least the serial device path, like /dev/ttyUSB0,
but it is recommended to use device path from /dev/serial/by-id folder, e.g., /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F003D3-if01-port0
A list of available device paths can be found in Settings > System > Hardware > dot menu > All Hardware.
The Z-wave page also contains an identical warning:
A device path like /dev/ttyUSB0 is subject to change. Essentially your usb devices will be fighting to grab the first path available after a restart or update. In your case, you seem to have been lucky that they landed back in their original slots when you put the NUC back together.
Using /dev/serial/by-id mitigates this issue, because it searches for the device address instead of its path. I suggest you use that to avoid future headaches.
I don’t use proxmox, (but I use Libvirt/QEMU/KVM), so maybe a question of how proxmox handles a USB device that gets reset as its USB port number will change after a reset and proxmox may or may not know whether it needs to be passed through or not.
For Aeotec, one thing you could also try is go into ZWaveJS-UI (if you use this) and settings and disable the ZWave “Soft Reset”. ZWaveJS has some kind of detection mechanism when it thinks the ZStick is possibly not working properly, it will do a soft reset. I think this is more for the 500 series ZStick’s and so it may not apply in your case, but may be worth a try.
