Mine works with no issue.
As @fenty17 mentioned you may need an extension cable. EMI is a real with USB3 and other devices plugged into other ports. You could have a power issue? Not sure what powered supply you have?
I have my SSD on a powered hub on an extension cable plugged into a usb3 port. My sonoff dongle is on another extension cable plugged in to a USB2 port.
I’ve just ordered for an extension, let’s see if it helps. I’m using the raspberry pi power supply and have an ssd (Crucial bx 500) that is powered through usb by the raspberry pi.
I am able to detect the dongle on my windows pc so it’s not really a dongle issue i think. I’ll update once i try with the extension cable.
No, no other devices. Just the ethernet cable and the ssd through the usb 3.0 port. Its not super hot or anything.
Its very weird, once i plug it in, most of the Home Assistant pages don’t load or give errors. I cant reboot it from the web page as well, have to manually diconnect power and reconnect. I though it might be a boot order issue but that doesn’t make sense as even when I plug it in after booting, it causes an issue.
Hello
I have exactly the same problem with the same errors with the USB3 port and this dongle.
I have not tried yet to plug it on the USB2 port.
I think I will flash and update the dongle with this video:
Are you guys plugging it into the USB3 port? EMI issues with both devices so close. Most people are having issues without an extension cable. Intel published a white paper on EMI caused by the USB3 switching. It interferes at the 2.4 GHz that the Zigbee uses.
my sonoff is plugged into usb2 which is adjacent to usb 3.0 used for my hdd. I’ll wait till my extension arrives and update if it works. I’m in australia so deliveries take a lot of time
There is another good reason for needing a USB extension cable and that is the USB plug on the dongle is very short so could be that if have an Raspberry Pi enclosure that is hindering the USB plug part of the dongle to be properly inserted all the way in the Raspberry Pi will not detect it since it is not actually fully plugged in. Using a USB extension cable with a longer USB plug part should help that issue.
Se alternative upgrade method here which does not require removing any screws or opening the case:
However, I do not believe that updated firmware will help with the symptoms described as it sounds like the issue is that the Raspberry Pi is not physically detecting the dongle for whatever reason.
He said that " can’t access integrations and … everything starts failing. This is not a zigbee issue unless the dongle is drawing more power than his supply can handle. I can’t tell from his comments if the dongle is inserted properly. This should not be an issue with “most” cases.
FYI, automatic USB discovery for ZHA will not work on early shipped batches of ITead Sonoff Zigbee Dongle Plus adapters unless you write missing custom product description in its CP2102N USB chip:
Again, use a long USB extension cable with a thin port so that the thickness of the computer enclosure casing does not prevent dongle from being plugged in all the way into the port on the computer board.
It is as well very strongly recommended to use a long USB extension cable to avoid EMF interference.
Using a longer USB extension cable to connect any radio adapters using the 2.4GHz frequency range to a USB 2.0 port (or a USB 2.0 hub) is step #1 and step #2 to try to avoid EMF/EMI/RMI interference.
Take note that the dongle is every big/wide and some computer enclosures are thick and do not have a lot of room around the USB ports, and if so then you need a USB extension cable which port is thinner.
Such computer enclosure casings will put the USB port a little bit recessed which can cause issues.
One such known example is the Home Assistant Blue enclosure which has issues with its thick casing:
This was perfect. It’s working now - my case was blocking the dongle from being inserted properly. I’m such a goose, but hope this helps someone out with a similar problem.