RPI 5 failed to probe the USB device via ZHA to add ZBDongle-P

[Ash-xiao]

The problem

After installing HAOS 15.2 on Raspberry Pi 5, unable to add the SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P) via ZHA. Tried all USB ports on Raspberry Pi 5, and even with a USB extension cable—none worked. On RPI 4 with HAOS 15.2, ZHA works correctly and can successfully add the same ZBDongle-P device.

Installation Methods Tried:

• Flashing HAOS 15.2 directly to TF card using Raspberry Pi Imager, ZHA error when adding Dongle: "Failed to probe the USB device."

• Installing HAOS 15.2 via Docker on Raspbian Same ZHA error: "Failed to probe the USB device."

On RPI 4:

What version of Home Assistant Core has the issue?

2025.5.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zigbee Home Automation

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

USB Logs：
mike@raspi5:~ $ ls -l /dev/zigbee
lrwxrwxrwx 1 root root 7 Apr 26 20:37 /dev/zigbee -> ttyUSB0
mike@raspi5:~ $ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ZHA Logs:
dmesg | grep cp210x
[ 4.946784] usbcore: registered new interface driver cp210x
[ 4.946813] usbserial: USB Serial support registered for cp210x
[ 4.947491] cp210x 1-2:1.0: cp210x converter detected
[ 5.036867] usb 1-2: cp210x converter now attached to ttyUSB0
[ 60.023483] cp210x ttyUSB0: failed set request 0x12 status: -110
[ 70.267876] cp210x ttyUSB0: failed set request 0x12 status: -110
[ 78.166725] cp210x ttyUSB0: failed set request 0x12 status: -110
[ 85.070018] cp210x ttyUSB0: failed set request 0x12 status: -110

RPI 5 information:
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

Some users online have reported the same issue, with the earliest problematic versions likely being:
Home Assistant Core: 2025.4.1
OS Version: Home Assistant OS 15.1

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[Ash-xiao]

Update: On the same system of RPI 5, the zigbee2mqtt addon can be started successfully. However, after stopping Zigbee2MQTT, it doesn't work when adding from ZHA.

logs：

[09:42:38] INFO: Preparing to start...
[09:42:38] INFO: Socat not enabled
[09:42:38] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-05-16 09:42:39] info: 	z2m: Logging to console, file (filename: log.log)
[2025-05-16 09:42:39] info: 	z2m: Starting Zigbee2MQTT version 2.3.0 (commit #unknown)
[2025-05-16 09:42:39] info: 	z2m: Starting zigbee-herdsman (4.0.0)
[2025-05-16 09:42:39] info: 	zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"60a1147bea6aef11ab349badc169b110","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_60a1147bea6aef11ab349badc169b110-if00-port0","vendorId":"10c4","productId":"ea60"} => zstack: 4
[2025-05-16 09:42:39] info: 	zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2025-05-16 09:42:40] info: 	zh:zstack:znp: Serialport opened
[2025-05-16 09:43:12] info: 	z2m: zigbee-herdsman started (restored)
[2025-05-16 09:43:12] info: 	z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2},"type":"ZStack3x0"}'
[2025-05-16 09:43:12] info: 	z2m: Currently 0 devices are joined.
[2025-05-16 09:43:12] info: 	z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883
[2025-05-16 09:43:13] info: 	z2m: Connected to MQTT server
[2025-05-16 09:43:13] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2025-05-16 09:43:13] info: 	z2m: Started frontend on port 8099
[2025-05-16 09:43:13] info: 	z2m: Zigbee2MQTT started!

[puddly]

Can you enable debug logging for ZHA (https://www.home-assistant.io/integrations/zha/#debug-logging), try adding it again, and post a log of it failing to connect on the CM5?

[Ash-xiao]

@puddly Yes. Here are the logs. Is this a problem with the CM5?

home-assistant_2025-05-16T02-34-29.220Z.log

[puddly]

Hmm. It looks like closing the serial port takes longer than expected on the CM5 for some reason and the probing timeout of 5s is hit even though probing was successful: https://github.com/zigpy/zigpy-znp/blob/856f6324907fb11a2daf171ba9256fcd50b88e5a/zigpy_znp/zigbee/application.py#L42.

[Ash-xiao]

Hmm... From what I remember, the CM5 didn't have this issue when running Home Assistant OS with core versions earlier than 2025.4.1.
However, I'm happy to assist with any testing you might need.

[WinniAT]

is there any update on this - i am also running into the same issue.
What can i do - i actually wanna go with the ZHA and not the MQTT

[puddly]

I've just migrated to a CM5 for testing and will try to get the fix for this into next week's release.

[WinniAT]

Awesome - thx!

Is there something I Can do in the meanwhile? Test / Send Logs ?