And for what its worth, reconnecting the Sonoff dongle directly to the Raspberry pi 5 caused issues again. I needed to keep it connected to the unpowered usb hub. (I suspect powered / unpowered / extension doesn’t really matter, it just needs to be physically away from the raspberry pi 5 by some amount)
Regarding this issue, I submitted an issue to ZHA.
Same issues here but I got it working after I disabled Bluetooth on my RPI!
1 Like
same issue here!, no way to get it working, it failed since 2-3 weeks ago
Same issue, but different Hardware. I’m using a Mac Mini running VMWare ESXi and have been using an extension cable.
Currently using the Conbee2 for day to day Zigbee and forgot I’d left the Sonoff left plugged in after a previous migration plan stalled. I was prompted to look into it after recently seeing a detection of the device after a reboot.
Given that my system/network is currently working fine is there any benefit in pursuing this?
I was having the exact same problem after migrating my Zigbee network to the Sonoff 3.0 Plus (Skyconnect is using the extension cable it came with and the Sonoff was directly plugged into the Pi but it’s a 3B+ so it couldn’t have been intereference from USB 3.0).
Each time I rebooted it would come up with the “Add Sonoff Integration”, even after a (somewhat?) successful migration. Clicking Add I would get “Failed to probe the USB device”. I tried using the Skyconect’s extension cable, exact same thing. Thankfully I had an ancient unpowered USB hub laying around so I figured “what do I have to lose”? It actually asked me if I wanted to migrate this time (there was nothing anymore left to migrate) but I proceeded. Automatic migration failed (as it did the first time around), but doing an Advanced migration (of what? the Sonoff was already in charge of the Zigbee network and I’ve long since flashed Thread onto the Skyconnect, it was just the “Add Sonoff integration” that kept popping up every time even though it was working fine).
Long story short, it apparently successfully migrated itself using the unpowered usb hub and the message seems to have stopped appearing now (even after removing it from the usb hub and plugging it back in directly, no msg anymore even after a reboot).
I don’t have an actual “Sonoff” integration like I do for the Skyconnect (or ZHA-1), but it is (still) listed. Is this normal?
This is what it looks like.
I’ve been told my 3B+ is underpowered and that HA needs at least 2 gigs of ram to run properly (and I’m getting a ton of hci0: bluetooth errors - hopefully the 5 fixes this).
But yeah, I want to make sure everything is (now) fine with my HA installation and I can just use an upgrade. I keep getting the feeling something went wonky during the migration process (it didn’t rename the Skyconnect to Snoff for one, but that I can live with if everything else is as it should be).
Any input from the Sonoff owners? Do you have an actual Sonoff integration or is it just listed as a device under zha?
Hi everyone, I’m having the same issue and I’m fairly new to this.
Could those with more experience please advise on the most likely cause of the problem and the best solution?
I’ve read through the existing discussion and the accepted answer, but I’m still struggling to understand what actually solves the issue. In particular, the mention of an “official power supply” isn’t clearly explained, and I’m unsure how it applies to my setup.
Here is my exact configuration and what I’ve tried so far:
- Device: Zigbee USB Dongle, version E
Reference: https://www.amazon.fr/dp/B0B6P22YJC - Test 1: Connected directly to my mini-PC via USB
→ The dongle is detected, but it fails with the error:
“Failed to probe the USB device.” - Test 2: Connected via a NOVOO USB hub (unpowered)
Reference: https://www.amazon.fr/NOVOO-Aluminium-ChromeBook-Matebook-Tablette/dp/B075FGQ988
→ Same result: the device is detected, but it fails with
“Failed to probe the USB device.”
Also, I am using HA (homeassistant/home-assistant:2025.12) via docker.
The accepted answer mentions success after using a longer USB extension, an unpowered hub, and the “official power supply,” but it’s not clear which component actually made the difference or why (is it because it was unpowered ? because long ?..) .
At this point, buying additional equipment just to see if it works isn’t really an option for me. Is there a more systematic way to debug this (power issues, USB interference, logs to check, etc.) rather than relying on trial and error?
Any clarification or guidance would be greatly appreciated.
1 Like
I have the same issue
- standaard PC
- SONOFF Dongle Plus MG24 (latest firmware Zigbee 8.0.2)
- HA 2025.10.4 (Ubuntu snap)
Sorry, my problem was not a but bug. The snap installation had no rights to access the raw-usb.
martin@server1:~$ snap connections home-assistant-snap
Interface Plug Slot Notes
bluez home-assistant-snap:bluez - -
content - home-assistant-snap:components -
content - home-assistant-snap:configurations -
content - home-assistant-snap:vscs-content -
content home-assistant-snap:bin - -
desktop home-assistant-snap:desktop :desktop -
hardware-observe home-assistant-snap:hardware-observe :hardware-observe -
network home-assistant-snap:network :network -
network-bind home-assistant-snap:network-bind :network-bind -
network-control home-assistant-snap:network-control :network-control -
physical-memory-control home-assistant-snap:physical-memory-control - -
raw-usb home-assistant-snap:raw-usb :raw-usb manual
removable-media home-assistant-snap:removable-media - -
serial-port home-assistant-snap:serial-port - -
thanks to: