Sonoff USB problem - dont see in lsusb in Debian 12

I run HASS in a VM on Debian 12. I plugged in the Sonoff USB Dongle but when I type lsusb I don’t see it. I need to know the device 0000x0000 to pass it through to the VM

Any ideas? A Google search AI summary said it shouldn’t need special drivers for debian.

(fyi, I plugged it into a Windows PC and it detected in Device Manager as Sonoff USB 3.0 zigbee. On my debian server, I tried multiple USB ports, both usb2 and 3 and with and without the short extension cable)

If its not showing in lsusb on the host, you aren’t going to be able to pass it through to the VM.

Could this be a power issue ? Are you running this on a pi ?

Perhaps trying through a powered hub ?

This might also help:-

not a pi, it’s a full PC basically, in a rack case being run on Debian 12

interesting link. will try to see if that helps thanks

edit: checked, the file is co210x.ko as he suggests it should be

Hmm… if its not even being detected with lsusb I wonder if its a compatibility issue then.

Also Try:-

https://www.reddit.com/r/linuxquestions/comments/uk4a1d/lsusb_not_showing_usb_device/

That does show the info when I plugged it in. I see the idVendor # and the idProduct (which may be enough to pass through to my KVM via virtManager)

Product: Sonoff Zigbee 3.0 USB Dongle Plus V2
Manufacturer: Itead

SN listed

cp210x converter detected
cp210x converter now attached to ttyUSB0

(edit: opened another terminal. still doesn’t show in lsusb though)

Ok, so maybe a driver issue then ?

seeing something about apparmor=“DENIED” so maybe there’s a conflict or something. This at least gets me started thanks

Perhaps

Looks like it is showing up, but just not as Sonoff USB Dongle, instead as Silicon Labs CP210x UART Bridge

so, not the product name i expected

Yeah a lot of USB vendors don’t bother changing the IDs and so they simply end up with the internal cp210x chip’s IDs. Be aware that because of this, you may have multiple USB devices plugged in with these same IDs so passing through to the VM based on IDs may be insufficient in these situations.

Thanks.

Just to update for any future readers, it appears the pass through worked

now i just gotta figure out what to do next haha