ZigBee End Devices Leaving nRF52840 Coordinator

RE: ZigBee End Devices Leaving nRF52840 Coordinator

Simonr — Mon, 31 May 2021 06:05:31 GMT

The nRF 802.15.4 sniffer firmware is only supported by the nRF52840 DK and Dongle, so making it work on an RPi is likely not very straight forward. Do you not have an nRF528440 DK available at all?

I'm afraid I don't have any suggestions to helpful ZBOSS stack stats at the moment.

Best regards,

Simon

RE: ZigBee End Devices Leaving nRF52840 Coordinator

WestCoastDaz — Fri, 28 May 2021 16:26:30 GMT

Simonr

Yes, I have zb_bdb_set_legacy_device_support(1) enabled in the ZB_BEB_SIGNAL_STEERING handler. Unfortunately I haven't been able to get a trace yet. I have tried to get the NRF 802.15.4 sniffer to work on a rPI for long duration traces but the interface doesn't seem to show up in Wireshark.

Any other thoughts or tests? Is there any error stats that the ZBOSS stack collects that would be helpful to review?

RE: ZigBee End Devices Leaving nRF52840 Coordinator

Simonr — Fri, 28 May 2021 06:46:19 GMT

Hi again

Marte is right, the rejoining should be enabled by default. As this is occurring on your customer's devices, I understand that this might not be doable, but is it possible to get a traffic dump (.pcap) file so we can take a look at what's going on over the air. A suggestion by one of our Zigbee developers: Have you tried enabling the legacy device support on the coordinator (adding zb_bdb_set_legacy_device_support(1) in the ZB_BDB_SIGNAL_STEERING signal handler)?

Best regards,

Simon

RE: ZigBee End Devices Leaving nRF52840 Coordinator

WestCoastDaz — Thu, 27 May 2021 16:13:01 GMT

Simonr

I asked about this call in this post https://devzone.nordicsemi.com/f/nordic-q-a/68410/how-to-use-the-zboss-zb_secur_set_tc_rejoin_enabled-api-call and was told it was enabled by default. Is this not the case?

Thanks,

RE: ZigBee End Devices Leaving nRF52840 Coordinator

Simonr — Thu, 27 May 2021 06:31:56 GMT

Hi Darren

I have forwarded some of your questions to our Zigbee devs, as I'm not aware of a way to determine why sensors have left a network specifically, and what the correct methods to handle rejoining are. Hopefully I'll hear back from them by tomorrow.

In the meantime, is this specific to a specific set of Zigbee 3.0 sensors, or does any kinds of end nodes leave the network? One lmitation to the Zigbee SDK (v4.0.0) is that time-critical processes (like leaving and rejoining can occur at the same time as migration processes, but this should only occur if mass NVRAM operations are in intersection with mass radio operations. (like if a parent device is joining 20+ devices one-by-one without delays. Likelihood of happening is low though.

Have you enabled the zb_secur_set_tc_rejoin_enabled in your coordinator application to allow TC rejoin?

Best regards,

Simon