But now I get the following error:
2023-03-06 18:15:45.919 [ERROR] [tsystems.zigbee.ZigBeeNetworkManager] - Cannot add extension ZigBeeDiscoveryExtension when network state is ONLINE
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.
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).
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.
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.
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.