Oh wow should it really be that easy… I will try.
May I ask another question - shall I add a new coordinator thing or just overwrite the old one?
May I ask what problem you stumbled upon? Replacing the ZBDongle-E with an ELU013 looks like a downgrade to me hardware-wise (80 MHz → 40 MHz, 1.024 kB → 512 kB flash memory, 96 kB → 64 kB RAM).
I’m not sure whether you can re-use the old Ember Coordinator Thing. Both chipsets are made by Silabs, but as mentioned above, there are differences between EFR32MG21 and EFR32MG13P - maybe @chris can provide an authoritative answer?
Well the ZBDongle-E does not support hardware flow control.
The main issue is that the startup takes round about 45 min before the last device is online. I was hoping the Elelabs solves the issue.
But maybe you have a better suggestion for a new coordinator.
May I ask what coordinator you use?
ZigBee - Bindings | openHAB and https://itead.cc/product/zigbee-3-0-usb-dongle/ contradict each other re HW flow control.
Any proof (log files etc.) that communication problems are the root cause? Any battery operated Zigbee devices involved?
My setup (two separate Zigbee networks bridged by openHAB):
- openHAB Zigbee Binding and Hacking the Lidl Silvercrest ZigBee Gateway: A Step-by-Step Tutorial
- Zigbee2MQTT/openHAB MQTT Binding and ZBDongle-E (30+ devices - no idea how long it’ll take to restart the Zigbee network)
I found quite many posts that say it is not possible to use hardware flow with this stick and many post that say it has some design flaws:
https://community.openhab.org/t/zigbee-coordinator-for-new-setup/124015/9?u=anpro
While startup I receive the following error: Error 0xffff setting client binding
I have 19 battery operated Sonoff Mini Motion Sensors
3 battery operated Wallswitches
And the following non battery powered:
22 Light bulbs
8 Sonor Mini Switches
But I no battery operated device is away more than 5 meters from the next „normal“ device.
Any proof (log files etc.) that communication problems are the root cause? Any battery operated Zigbee devices involved?
What do I have to look for - for me log files look normal after start - and every device works flawlessly.
The only point is the long startup phase.
Edit: just read what you did with the Lidl gateway- cool - I guess the benefits are:
- stable network because of the better antenna
- more options to place it because connected via Ethernet
- when you restart openhab you do not have to restart the gateway and all the devices are back online
Is it possible to use the netbackup with the haked Lidl gateway?
Seeing is believing. Which flaws? Proof? Are we talking about ZBDongle-E or ZBDongle-P or https://itead.cc/product/cc2531-usb-dongle/?
Battery operated devices are sleeping most of the time. AFAIK they cannot be ‘contacted’ by a Zigbee router (unlike FLiRS devices in Z-Wave networks), they must wake up and find a Zigbee router (or the coordinator) on their own. So I’m not surprised that it takes some time to get your specific Zigbee network up and running as a whole. Whether another Zigbee coordinator would take less time to get your Zigbee network up and running would remain to be seen. Radio interferences might be a problem. Use a USB extension cable between your USB host and your dongle. Why not buy a dongle of your choice, set up an additional Zigbee network with some battery operated devices and check the network convergence time?
Yes, it is - but I wouldn’t recommend it for new projects, the EFR32MG1B is quite outdated (40 MHz, 256 kB flash memory, 32 kB RAM).
For now I can only answer a few questions because I am not at my mac.
We are talking about the E-Dongle:
Even on the Website it only says software flow.
And whenever I activated it in the think no device came back online.
It shouldn’t matter - the software is generally the same (by which I mean the interface API to the host is the same). What does matter is the version of EZSP - if it’s using a very recent version then it might not be compatible at the moment (although I’ll likely update this soon).
Re convergence time:
There may be weak radio links between your devices. Use the Zigbee2MQTT network map to identify weak links and add Zigbee routers where necessary.
Some additional hints to take into account: Improve network range and stability | Zigbee2MQTT
Ok? What are the consequences for me?
Can you also give me a second advice which usb stick you would choose?
But that would mean a lot of effort to move my whole network from the zigbee binding to Zigbee2MQTT.
Is there a way in the Zigbee binding itself?
openhab> zigbee neighbors 0
Total neighbors: 1
Extended PAN ID Extended Address Network Address Device Type RX On When Idle Relationship Permit Joining Depth LQI
87E9CAF6XXXXXXXX A4C138XXXXXXXXXX 61889 END_DEVICE RX_OFF CHILD DISABLED 1 0
LQI is the parameter to watch for.
Ok so I just have to type in „zigbee neighbors“ and then I get an overview over the network including LQI - and it better be over 200 as far as I understood.
Well I have a strange behavior here:
openhab> zigbee neighbours
Error: Could not find command: neighbours
zigbee --help gives:
Usage: openhab:zigbee - neighbors NODEID - Lists the neighbors of a node.
Which means you have to provide a NODEID like Ap15e did.
Use American English. 
Thanks that worked - but why does it only show 16 devices?
Total neighbors: 16
Extended PAN ID Extended Address Network Address Device Type RX On When Idle Relationship Permit Joining Depth LQI
056043E0668F7F18 385B44FFFE1B24CC 57084 ROUTER RX_ON SIBLING UNKNOWN 15 111
056043E0668F7F18 385B44FFFE1B2982 28220 ROUTER RX_ON SIBLING UNKNOWN 15 84
056043E0668F7F18 0C4314FFFE5B5EBA 36639 ROUTER RX_ON SIBLING UNKNOWN 15 44
056043E0668F7F18 385B44FFFE1B267C 15115 ROUTER RX_ON SIBLING UNKNOWN 15 37
056043E0668F7F18 0000000000000000 49082 ROUTER RX_ON SIBLING UNKNOWN 15 104
056043E0668F7F18 DC8E95FFFE1E3154 51733 ROUTER RX_ON SIBLING UNKNOWN 15 55
056043E0668F7F18 385B44FFFE1F5F26 50000 ROUTER RX_ON SIBLING UNKNOWN 15 196
056043E0668F7F18 B4E3F9FFFE08F783 13460 ROUTER RX_ON SIBLING UNKNOWN 15 51
056043E0668F7F18 0C4314FFFE57C066 22830 ROUTER RX_ON SIBLING UNKNOWN 15 211
056043E0668F7F18 847127FFFE90EC19 61357 ROUTER RX_ON SIBLING UNKNOWN 15 135
056043E0668F7F18 60A423FFFEB02B7B 43217 ROUTER RX_ON SIBLING UNKNOWN 15 164
056043E0668F7F18 847127FFFE8F7F94 62502 ROUTER RX_ON SIBLING UNKNOWN 15 136
056043E0668F7F18 B4E3F9FFFEA764C7 26143 ROUTER RX_ON SIBLING UNKNOWN 15 118
056043E0668F7F18 B4E3F9FFFEC0AB18 52604 ROUTER RX_ON SIBLING UNKNOWN 15 144
056043E0668F7F18 0000000000000000 11213 ROUTER RX_ON SIBLING UNKNOWN 15 64
056043E0668F7F18 0C4314FFFE600162 28708 ROUTER RX_ON SIBLING UNKNOWN 15 151
How to find out about the rest?
Btw. today came a shielded usb extension now the dongle is 5 meters away from my network rack, now it took only 15 minutes until the last devices cam online.
I’m not sure what the device is that you requested the neighbour table from but typically there is a limitation of 16 neighbours stored in any single device.
I requested it from node 0 but I did not find a way to identify any other nodes.
I used zigbee —help but could not find the correct command!
You can query the neighbors in your list returned from node 0. That is:
zigbee neighbors 57084