Hey,
i just got a raspberry pi 5 and flashed the HA image. I added a Zigbee dongle i ordered (https://www.amazon.de/dp/B09KXTCMSC?ref=ppx_yo2ov_dt_b_fed_asin_title) and tried to add it. After a while i get the message “Failed to probe the USB device”.
I was under the assumption, that i only need to plug it in and it should be installable.
I read a few times, that the dongle might have problems when it is directly added to the usb port, so i also tried a 0.5m USB 2.0 extension.
The Logs (Settings->System->Logs) where empty. I looked again after you said that and saw that you can see “raw logs”, so i restarted HA and tried it again. All i got in the logs was this
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
[17:19:57] INFO: Home Assistant Core finish process exit code 0
[17:19:57] INFO: Home Assistant Core service shutdown
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
Hi
I’m experiencing the same issue on a fresh install of HA ( HAOS 15.1 on a RPI5.
When connecting the Sonoff Dongle P model dmesg shows
[145135.448720] usb 1-2: new full-speed USB device number 3 using xhci-hcd
[145135.620878] usb 1-2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[145135.620884] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[145135.620887] usb 1-2: Product: Sonoff Zigbee 3.0 USB Dongle Plus
[145135.620890] usb 1-2: Manufacturer: ITead
[145135.620892] usb 1-2: SerialNumber:
[145135.623015] cp210x 1-2:1.0: cp210x converter detected
[145135.642439] usb 1-2: cp210x converter now attached to ttyUSB0
[145169.556798] usb 1-2: USB disconnect, device number 3
[145169.557004] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[145169.557530] cp210x 1-2:1.0: device disconnected
[145189.921111] usb 1-2: new full-speed USB device number 4 using xhci-hcd
[145190.093828] usb 1-2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[145190.093834] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[145190.093837] usb 1-2: Product: Sonoff Zigbee 3.0 USB Dongle Plus
[145190.093840] usb 1-2: Manufacturer: ITead
[145190.093842] usb 1-2: SerialNumber:
[145190.095983] cp210x 1-2:1.0: cp210x converter detected
[145190.115127] usb 1-2: cp210x converter now attached to ttyUSB0
➜ ~
Then when adding the device as ZHA in the devices menu the
Sonoff Zigbee 3.0 USB Dongle Plus
Zigbee Home Automation
after a while the message Failed to probe the USB device appears.
Dmesg
[145336.614258] cp210x ttyUSB0: failed set request 0x12 status: -110
[145346.854330] cp210x ttyUSB0: failed set request 0x12 status: -110
[145354.534381] cp210x ttyUSB0: failed set request 0x12 status: -110
[145361.446435] cp210x ttyUSB0: failed set request 0x12 status: -110
This may be a tough one to figure out. If it works on RPi4, and even on RPi5 it comes up OK, but not until it is probed does it break, then hard to tell. My recommendation would be to try to plug it into a powered USB hub to see if that makes any difference.
I don’t have a powered USB hub, so i couldn’t test this.
I did try earlier versions (10.5, 14.2, 14.1). None of them worked.
Since @hub88 said it worked with 14.2 on the pi 4, it seems, that this is more an issue between the pi and the dongle.
Can anyone name a different zigbee dongle that does work with the pi 5?
Could you please upgrade HA Core to the latest version (2025.4.2) and test again?
I’ve tested on Raspberry Pi 5 without finding any issues - my HA Core version is 2025.4.2.
Based on feedback from other users, I believe the core issue stems from electromagnetic interference (EMI) generated by the Raspberry Pi 5 itself, requiring the use of a USB extension cable (minimum 0.5m recommended) to sufficiently distance the dongle from the device.
If you’re adding USB drives or other USB devices, please note that the maximum current the Raspberry Pi USB ports (either combined or a single USB port) can pass through is 1.2A.
To clarify, you cannot draw 1.2A from all four ports at the same time. You can draw this from one port only, or 1.2A across all 4 ports combined.
That is why you should try with a powered USB hub.
I do not have a powered usb hub. As i already mentioned before ; on rpi4 i have no problem at all. The dongle is recognized and configured immediately. Zigbee devices work as expected.
I spent half a day trying to add the Sonoff Zigbee 3.0 USB Dongle Plus to Home Assistant on Raspberry Pi 5. After a clean installation of HA, I was getting the error “cp210x ttyUSB0: failed set request 0x12 status: -110”. I tried updating and rolling back both the Dongle firmware and HA, but it didn’t help.
In the end, I connected the Dongle to a USB hub (without additional power), and it successfully added to the system. Then I removed the hub and connected the Dongle directly to the Raspberry Pi, and it started working. It seems the issue was with the initial device addition procedure via Raspberry Pi’s built-in USB hub.
Thank you for your feedback. Based on available reports, all related issues exclusively occur on Raspberry Pi 5. However, I haven’t determined whether the root cause stems from EMF interference or the Pi 5’s USB ports.
Could anyone share a purchase link for an affected Raspberry Pi 5 unit? I’d like to acquire one for testing purposes.
Following Deon’s advice I performed a new test with an old non powererd usb hub between dongle and rpi5 and now everything worked as expected.
dmesg output
[ 592.062034] usb 3-2: new high-speed USB device number 3 using xhci-hcd
[ 592.211734] usb 3-2: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 592.211742] usb 3-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 592.211745] usb 3-2: Product: USB 2.0 Hub
[ 592.275955] hub 3-2:1.0: USB hub found
[ 592.276239] hub 3-2:1.0: 4 ports detected
[ 619.266246] usb 3-2.1: new full-speed USB device number 4 using xhci-hcd
[ 619.493446] usb 3-2.1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 619.493453] usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 619.493456] usb 3-2.1: Product: Sonoff Zigbee 3.0 USB Dongle Plus
[ 619.493459] usb 3-2.1: Manufacturer: ITead
[ 619.493461] usb 3-2.1: SerialNumber: 1…0
[ 619.494788] cp210x 3-2.1:1.0: cp210x converter detected
[ 619.500024] usb 3-2.1: cp210x converter now attached to ttyUSB0
[ 889.438279] cp210x ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Thx for the suggestion Deon.
I bought my RPI5 from Amazon.