Used my previous flashed ZBDongle-P to pair it into ZHA. Devise is visible in the Visualization but not connected to the coordinator. Has no end devises connected as well. WTH?
edit: updated wrong screenshot / added OS platform
FYI, many if not most Zigbee End Device products will not automatically change their connection to a closer Zigbee Router if you added that Zigbee Router after you added the Zigbee End Device products, so in those cases, you might just have to remove its battery/power for a while in order to it to make a new connection when put battery/power back or sometimes manually re-pair/re-join the Zigbee End Device in ZHA.
Those Zigbee End Device products that do automatically change their connection to a closer Zigbee Router usually only do so in intervals of once every 24 hours or more after it has evaluated its strongest neighbours.
Most other Zigbee Router products will however automatically change their connection once every 24 hours or more after it has evaluated its strongest neighbours.
Thank you Hedda for your elaboration. I was assuming that the SONOFF DONGLE-E_R used as router would make faster pairing possible than my BlitzWolf SHP-13 Energy Sockets/Meters.The SONOFF DONGLE-E_R has now paired itself into the mesh - 15 hours later - and has already made some connections.
Still not sure about the LQI / RSSI (not showing) for the majority of devices in my mesh. For now I’ll let the ZHA mesh do its thing and check it everyday or so.
Next time I pair a device I’ll have more patience.
@Arc8dium ,
did you able to recover from firmware 7.X.X?
also try to downgrade to 6.10.3,
but after firmware flush the device stop to respond,
try again to flush with the bootloader mode,
but nothing help.
with the ezsp utility getting this messege:
python3 Elelabs_EzspFwUtility.py probe -p /dev/ttyACM1
2022/10/27 10:39:26 Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode
After that push enter then you will see a text in the console.
Enter 1 then click “File transfer” at the top → Xmodem → send
It is important that you push 1 and then you will see: CCCCCCC
While you see this you have to start the file transfer.
After that extraputty uploads the firmware and after finishing you have to push 2 → it goes to paring mode.
Hi all,
I’m trying to flash my two e dongles with the router firmware. I tried with SecureCRT and also ExtraPutty with parameters you told:
Serial: COM10 (for this example) and 115.200 bauds. Data bits to 8, parity None, stops bits 1 and flow control XON/XOFF
I can connect but I cannot send the firmware. SecureCRT says that receiver never responded to the start of transfer request.
I also tried booting the dongle pushing the boot button and also the reset one. Nothing worked.
For now they work equally great with Home Assistant’s ZHA integration today, however, you could maybe speculate that support for Silicon Labs based adapters like the ZBDongle-E might perhaps indirectly become better integrated in the future if prioritized by Nabu Casa’s own developers only because it uses the same Silicon Labs EFR32MG21 SoC chip as the upcoming official Home Assistant SkyConnect USB Stick
Also note that if you are using the ZHA integration today then it is now very easy to migrate back and forth between ZBDongle-E and ZBDongle-P (via ZHA integration’s built-in backup, restore, and migration features).
In addition, remember that you can always convert ZBDongle-E and ZBDongle-P adapters into dedicated Zigbee Router devices that can work as stand-alone Zigbee signal repeaters and range extenders if used in USB charger for power to achieve better coverage in large homes.
One of THE best elaborations about the two Sonoff Zigbee 3.0 ZBDongles P/E! Thank you for that Hedda.
E.g. I have one ZBDongle-P flashed as Coordinator running in ZHA and one ZBDongle-E as Router in the same ZHA. Still fine tuning my Zigbee mesh network, but happy with both Sonoff ZBDongles.
Do anyone know the current status of zigbee2mqtt for the ZBDongle-E? I see that it is still in the experimental section, but would it be safe to take it in use now? I cannot seem to able to get hold of the “P” version any more.
Hopefully, stability will improve as more people in the Zigbee2MQTT community start to use it and help with development or as testers to actively contribute with proper and constructive bug reports.
I believe that is due to the still ongoing global chip shortage and global supply chain crisis
Note that everyone here can also help the developers make this dongle more stable in Zigbee2MQTT.
If you stumble into issues that seem related to this or other Silicon Labs EFR32 based Zigbee dongles then try to help the developer of the ezsp adapter for Zigbee2MQTT’s zigbee-herdsman code by providing detailed descriptions of your problem and logs needed for troubleshooting and debugging. See → https://github.com/Koenkk/zigbee-herdsman/issues/319
Note! If feeling brave then also consider upgrading to the latest unofficial 7.1.x community firmware builds on the ZBDongle-E to help them with testing the updated EZSP v9 interface with Zigbee2MQTT.
Community resources with newer unofficial firmware builds:
I’ve upgraded to this firmware on my dongle and it resolved the issues I was (ironically) having with pairing SONOFF contact and movement sensors. After the upgrade, they finally paired and finished the interview process. The older firmware would just fail to finish the interview.
Edited to add that I’m using the xsp1989 firmware and used the Elelabs Python script.