zigbee: similar issue as KRKNWK-12017

[Cheb]

Hi,

SDK: nRF5 SDK for Thread and Zigbee v4.2.0

Chip: nRF52840

We're experiencing a very rare behavior on an end device implementation.

We haven't able to reproduce with logs due to the rare occurrence of the issue but we have some live instrumentation that allows us to get the history of ZBOSS signals.

When the issue happens we get a ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE and the device doesn't try to rejoin the coordinator anymore.

It looks very similar to the KRKNWK-12017 issue bu there is no broken rejoin procedure happening before the ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE event.

Here is the historic of ZBOSS signals for a device which was up for several days and then stops interaction with the coordinator:

1. ZB_ZDO_SIGNAL_PRODUCTION_CONFIG_READY
   
2. ZB_ZDO_SIGNAL_SKIP_STARTUP
   
3. ZB_BDB_SIGNAL_DEVICE_REBOOT
   
4. ZB_NLME_STATUS_INDICATION  => ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE
   

Could you recommend a procedure to fix this ? Maybe trigger a rejoin when the ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE occurs ?
FYI, resetting the device makes the device rejoin the network immediately

Thanks,

Sebastien

[Cheb]

Marte Myrvold said:

Do you only get ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE once or do you get this signal multiple times when it fails? The best option is to have a failure counter that checks how many times the device has received ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE, and then have a threshold for when it should reset.

When it fails ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE happens once and there are no more signals received from the zboss signal handler.

Regards,

Sebastien

[Marte Myrvold]

Hi Sebastien,

In that case, you can reset the device on the first ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE. Please be aware that this will make the device reset in situations where it might have been able to find the parent again or rejoin under a new parent, but it should be able to rejoin successfully on restart.

Best regards,
Marte

[Cheb]

Marte Myrvold said:

In that case, you can reset the device on the first ZB_NWK_COMMAND_STATUS_PARENT_LINK_FAILURE. Please be aware that this will make the device reset in situations where it might have been able to find the parent again or rejoin under a new parent, but it should be able to rejoin successfully on restart.

Thanks we have this logic under test.

[Rogger]

Have you been able to solve the issue with a device reset after parent link failure?