Zigbee end-device (NRF52840) leaving the coordinator (also NRF52840)

[Fernando Fontes]

I've been working with the NRF52840 for a while now. My setup is based on the CLI coordinator code and a bunch of end devices running the multisensor freertos based program.

Recently something weird started to happen. After being paired with the coordinator for like days, some end devices disconnect from the network and never re-join again. Also, the connection status LED turns off and never turns on again unless I manually reboot the power of the end device. What could be the issue here?

What can I do to prevent this? Should I make kind of a watchdog to the connection status?

Best regards,

Fernando

[Simonr]

Hi

I assume you're referring to the timeout for when a device should leave after a set amount of inactivity? If not, please specify what timeout you mean.

What SDK are you using for development? The nRF5 SDK for Zigbee and Thread or the nRFConnect SDK? Depending on which one you use, setting this timeout length will be somewhat different.

Best regards,

Simon

[Fernando Fontes]

Hi, 
So if I understood correctly there is a timeout for the device to leave the network in case the coordinator being off for too long? What is this value? Where can I get this configuration info? Is this also applicable for the router mode? 

I was talking about a different issue. That is, when I first power the end device, he enters in commissioning but stops after a certain timeout. I want to stop this behavior and have the device always in commissioning until reaching a coordinator. 

Best regards,

Fernando

[Fernando Fontes]

Oh sorry, I forgot to mention but I'm using the nRF5 SDK for Zigbee and Thread.