Nordic has published an errata for the nRF Connect SDK for versions >1.8.0 where a Zigbee End Device can end up getting stuck if the parent device does not acknowledge the "Device Announcement packet". They have a suggested workaround to implement in the SDK, which has been adapted for the custom signal handler used here. This is an effort to solve issues where my parasites would occasionally drop off my network and require a reboot. After 24Hrs, I've not yet had a device disappear but it has taken >weeks before a device would fail. Unforunately it's hard to debug the board as the chips are in a low power state when this occurs. |
||
|---|---|---|
| .. | ||
| nrf-connect | ||
| .clang-format | ||