Continuous leave request with rejoin from Zigbee coordinator

RE: Continuous leave request with rejoin from Zigbee coordinator

Laura M — Fri, 08 Mar 2024 10:23:43 GMT

Hi Marte,

Thank you for your replies.

As you said the coordinator is probably sending this leave request because the device is doing something that is not according to the specification. We've chosen a completely different implementation to address the issue, now ZBOSS is not processing any more packets from this device.

Best,

Laura

RE: Continuous leave request with rejoin from Zigbee coordinator

Marte Myrvold — Mon, 19 Feb 2024 14:54:56 GMT

Hi Laura,

I have been looking into this, but I have not figured out the issue yet.

Do you have application logs from the coordinator as well?

I also see a lot of communication from other devices in the sniffer log. Do you see the same behavior if you test in a less noisy environment?

Best regards,
Marte

RE: Continuous leave request with rejoin from Zigbee coordinator

Laura M — Tue, 13 Feb 2024 15:20:31 GMT

Hello Marte,

sorry for the late reply.

While trying to replicate the issue I realized that it may be related to orphan join procedure. The issue is easily reproducible if the device uses this procedure.

This device has 2 ways to join the network. The first one starts with a beacon request but unfortunately doesn't work in all Zigbee channel. The second one starts with an "Orphan notification" (IEEE 802.15.4 spec) whose reply is a "Coordinator realignment", packet number 115 in following logs.
devzone.nordicsemi.com/.../Leave-req-_2D00_-orphan-join-_2800_pkt-115_2900_.pcapng
I erased memory before collecting them.

Is there a way to notify the stack that this is a new device and it shouldn't be remove?

I tried with zb_address_update but it didn't help.

Best regards,

Laura

RE: Continuous leave request with rejoin from Zigbee coordinator

Marte Myrvold — Mon, 18 Dec 2023 12:39:35 GMT

Hi Laura,

[quote user=""]Is there a way to avoid this situation? Any parameter I can set? [/quote]

This is difficult to answer without knowing why the coordinator sends the leave request.

[quote user=""]If not, is there a way to limit the number of retries for this packet? Any workaround?[/quote]

Based on the sequence numbers of the packets none of them seem to be retries, but instead individual packets. Regarding workaround this is also difficult to answer without knowing what the underlying issue is or what is causing the coordinator to send the leave requests.

Please get a sniffer log of the end device being commissioned to the network. Make sure that the end device is factory restored or at least does not have any network data stored so it is commissioned to the network and not rejoining. Please also get application logs from the coordinator.

[quote user=""]This request is sent continuously every time that a data request is received and I don't know what triggers this behavior (device aging?).[/quote]

Data requests are the keep-alive packets of Zigbee end devices, so the device should not timeout as a result of sending data requests.

Please note that devices that are not compliant with the Zigbee specification may lead to unexpected behavior such as you are seeing. It could be that the coordinator is sending the leave request because the device is doing something that is not according to the specification.

Best regards,
Marte