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:
What do you think about this ?
I was planning on flashing it, but I don’t have a screwdriver small enough to open the screws 
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
Yes. Recommended.
I re-read your issue. The cable will help for EMI. I don’t believe that is your issue. EMI causes issues with zigbee, not with the pi not working.
What is the rating of your power supply? The official supply is rated at 5.1V 3A (15.3 W).
You may want to creat an issue on GitHub and post your logs so one of the developers maybe able to help.
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:
https://www.facebook.com/SONOFF.official/posts/2927251720919807
Even the discovery through the integration does not seem to work. Will update with results tomorrow.
This might be it. I have a feeling the USB is not going in. the 2 middle pins on the dongle don’t seem to be full length
I think it’s normal.
Here is a screenshot of the video that’s update the dongle.
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.
https://itead.cc/product/1-5m-usb-male-to-female-extension-cable/
Also follow general tips in https://github.com/home-assistant/home-assistant.io/pull/18864 and https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties as all Zigbee Coordinator adapters is very sensitive to EMI/RFI interference (e.g. a noisy radio frequency environment will jam the signal and prevent it from receiving all Zigbee messages to it without errors).
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.
2 Likes
While you are at it, follow the general tips in https://github.com/home-assistant/home-assistant.io/pull/18864 and https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties as all Zigbee Coordinator adapters is very sensitive to EMI/RFI interference (e.g. a noisy radio frequency environment will jam the signal and prevent it from receiving all Zigbee messages to it without errors).
PS: If it help give a thumbs up in https://github.com/home-assistant/home-assistant.io/pull/18864
It’s work for me too without extension cable for the moment.
I just stop my Raspberry, plug the dongle and start my Raspberry and it’s ok…
Before I tried without stop the raspberry, I think that was the problem.
I had the same issue: only SSD works fine, inserting sonoff dongle resulted in the error message “Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby” in the zigbee2mqtt log files.
Checking the link in the log file (Zigbee2MQTT fails to start | Zigbee2MQTT) this would refer to a power issue with the advice to use an external powered hub for the SSD.
I tried the extension cable for the sonoff dongle as opt-ed by several people, and I can confirm this solved the issue for me.
1 Like
Can also confirm this worked. I used a USB hub with powered by another powerbrick (because I didn’t have a usb cable extension)
that was my problem too. The screws are so tight. I cracked them with sheer willpower.
Supposedly there is a way to put it in bootloader mode with a linux program without pushing the button.
Def update the firmware to the 1217 version.