Nerivec
Nerivec
`MQTT Publish` lines are far too verbose for `info`, especially for larger networks, or people with high-update-rate devices (like power monitoring). But a new level just for that line would...
@Loic691 Can you generate a network map and identify the path from the coordinator to the device in question (just push irrelevant devices to the side or something) and send...
Can you provide some `debug`-level logs of when this happens?
The Zigbee spec prevents more than 8 broadcasts over a 9-second period. [Silabs docs](https://community.silabs.com/s/article/how-are-different-tables-managed-in-emberznet-x?language=en_US) (see paragraph "Broadcast Table"). Filtered logs ```logs [2024-05-10 14:04:11] [34mdebug[39m: zh:ember:ezsp: ~~~> [SENT type=MULTICAST apsSequence=0 messageTag=8...
@diegocjorge That would not be the same problem. Yours are failing because it looks like the network isn't very stable, and it can't reach devices properly all the time. Try...
1. It gets problematic if you then see `NETWORK_BUSY` returned for messages. The broadcast table can hold 15 messages (standard size), you need to reach over that limit before it...
`ezsp` is not making use of these network/route issues reported by the adapter (hidden away). `ember` is, since they can be useful. Check the [Help section here](https://nerivec.github.io/z2m-ember-helper/#help) for more details...
@thewan056 Can you open a new issue for that device with missing power monitoring and provide a `debug` log of the pairing procedure?
@rinne Do you have the complete log file for those ~24h? I'll take a look, see if I can spot something.
Just to be clear: Network/route errors are not necessarily a "problem". They happened with `ezsp` too, you just didn't see them because `ezsp` doesn't make use of them. `ember` does...