Nerivec

Looks like [some of the firmware versions might have quirks](https://github.com/Koenkk/zigbee2mqtt/issues/19916#issuecomment-2204561938). Can someone with one of these devices see what's going on in the airwaves when OTA is requested? https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html

It must be something specific to Hue that is causing trouble. I had a report, not too long ago, of almost 20 Inovelli devices being updated (sequentially of course 😁)...

No on the contrary, it confirms this is a more "generic" issue. The first `dataSize` should be `maximumDataSize` (the value received), the second one is the value determined/used by Z2M....

From the comments in code, it seems the 50 was chosen because higher values often result in instabilities. Also have to consider deeply nested routes and the cost involved. The...

@mundschenk-at Any chance you can run custom code to test an OTA refactor? If yes, find me on zigbee2mqtt Discord.

I know @mundschenk-at had some pretty good results with the new [OTA refactoring](https://github.com/Koenkk/zigbee-herdsman-converters/pull/7585). Had some good feedback on large `ember` networks too. So I'm going to tag this. @Ricc68 not...

@Ricc68 Looks like your issue lies elsewhere (not OTA). Try bringing the device in question close to the coordinator, and re-pair the device to it directly. Then see if the...

Closing this as no longer relevant to the issue. If you have trouble starting Z2M: - make sure you are using the proper firmware, proper baudrate, and corresponding baudrate in...

Are these devices with "message too long" farther away from the coordinator? It could happen if the devices are nested too deeply (as in "device > router > router >...

For multicast/broadcast, addresses are special, since they target the whole network, not just a single device. They mean the following: ``` 0xFFFB = Low power routers only 0xFFFC = All...