Nerivec

It's a little strange this behavior. Not sure what's going on behind the scene there... 👀 --- You can use USB or TCP (just point to it like you have...

To get an address conflict on zero, technically you'd need a device that reported as "coordinator" (the only device supposed to have address zero in a ZigBee network). _Granted, there...

@stavros-k I assume you didn't rename the file before flashing? If so, you didn't pick the "max" version as Koenkk intended. https://github.com/Nerivec/silabs-firmware-builder/actions/runs/10512841278/artifacts/1843552001 Can you try that one and report back?

@YoungRus Seems some networks are having troubles with message volume/rate. Try the firmware mentioned above, it increases the capabilities of the adapter, and so far has been able to fix...

Crash on multiple OTAs is not really surprising; it's entirely dependent on the stability of the underlaying network (quality of the routers, number of hops, etc.). Can you list the...

@alexborro Does your network map also look similar to the one above (many devices directly on the coordinator)?

@stavros-k Could you try with [7.4.4](https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/), see if you can make it crash like you did before? _I don't see anything in the release notes from silabs that would explain...

Thanks for the detailed feedback! Looks like something in 7.4.4 is making your OTAs happier... too bad silabs release notes don't really point to something in that regard...

> 7.4.4 with increased buffers You mean custom firmware? If yes, what increased values exactly? Note: That error is not necessarily a firmware issue, but could just be generic network...

Strange indeed, crash after only a couple requests in the queue. It should handle 80+ queue without issue with default concurrency (tested on Dongle-E with a generic Tuya RGB strip)....