Coordinator ZBOSS stack hangs when router leaves network

[dimi]

Dear Nordic team,

in our multiprotocol (BLE, ZB) application (nRF5 SDK v4.1.0 )we are facing following severe issue relating to the ZBOSS stack: When a router leaves its ZB network using the workaround described in issue zigbee stack reset coordinator - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com), the ZBOSS stack sometimes hangs on the coordinator side (zb_assert, after executing either zb_address_unlock or zb_address_reset).

Here the call stack on the coordinator side, after trying to remove a router device from its network (in 2 different cases):

Result is, that the app scheduler we use, returns a NRF_ERROR_NO_MEM error, since its queue is not processed and the application fails. Could you please advise us on how to deal with these ZBOSS errors (via workaround or ZBOSS update)? The problem is really hard to track, since it doesn't occur systematically. 

Since we are already in production, we would appreciate a prompt response.

Many thanks in advance!

[Charlie]

Hi Dimitris,

Sorry, I cannot bring a "ZBOSS expert" for you, the ZBOSS stack has its own maintenance team. The issue can be hardly solved through a workaround outside of the ZBOSS stack, and there is already a fix on the new ZBOSS release. The only issue is that we need time to integrate and test it for nRF5 SDK, and getting Zigbee certification for the new nRF5 SDK for Thread and Zigbee release is also time-consuming. The above solution for this issue is the best effort we can provide now.

Updates:

NCS 1.9.0 (not NCS1.8.0) and nRF5 SDK for T&Z 4.2 will have the same final ZBOSS (coming from December 2021), target release time is February 2022 with production quality and certification be ready.

Best regards,

Charlie