Unwanted "Leave" command from coordinator

[abe]

Hello, I developed for my customer, a ZigBee coordinator in last 2019, using nRF5 SDK for Thread and Zigbee v3.2.0.
Now my customer has this issue:
- End Node connected via router, if router deads, the coordinator rejoin it but after few time send "leave" command to end node
Here attached WireShark log file of ZigBee radio communication
Some details:
- end node has NW address E3DF
- router has NW address D01B
- at line 14631 and following, the router deads
- at line 14680 starting end node routing search
- at line 14747 and followings rejon procedure
- at line 14850 Coordinator sends LEAVE command to end node E3DF

What is happened? Why Coordinator sends "Leave" command?
How can we avoid this unwanted behaviour?

Many thanks for your help!

Abele

[abe]

Hello Marte,

Marte Myrvold said:

Changing only ZBOSS libs should be only with the rest of the SDK - there were some major changes between SDK v3.2 and v4.X.

Yes, of course, I see there are some function that must be adapted/changed, but this could be resolved, I think

Marte Myrvold said:

I pretty sure that even attempt to change ZBOSS libs will require factory reset of the device.

This is not a issue, all custom data/configurations stored on FDS will be restored via BLE

For the issue, I haven't said that it can be reproduced with CLI sample, I said that ii needs to be tested.
I said that Link Status timing are same of CLI example

To try to reproduce the issue, you must have a Battery powered end node (button or door sensor) and a Bulb or other mains powered end node that act also as Router
If you see my WireShark log, you can see that the all end nodes regullary report some attribute, in addition, the Door Sensor is configured also to send IAS zone status info to Coordinator and it send these information via router.
If you power down the router, and for example open / close the door sensor, it try to send via router, but it is not reachable; then it ask to find a route, the coordinator rejoins it and accept data, but after some seconds sends "leave" to just rejoined end node.
Unfortunatly this happens "randomly" not every time you make this sequence

Abele

PS We are using Heiman end nodes (bulbs, door sensor , ...)

[abe]

Hi Marte
Have you still tried to reproduce the issue? (using my suggests...)
Have further news?
On my side, I hope to try with Zboss log enabled during this week ...

Abele

[abe]

Hi Marte,

this is the Zboss Log as expected?
If yes, i will try to reproduce the issue and send you the log
Let me know as soon

Thanks

Abele

[abe]

Hi Marte
here attached zip file with Zboss log and related WireShark files for two cases of "Unwanted Leave"
Inside the Zboss log you can find also some "app" info: the message "<info> app: Device IEE UUID address 5C0272FFFEE7B24F leave network" is coming from Zboss callback function zboss_signal_handler(zb_uint8_t param) on main.c, processing switch case ZB_ZDO_SIGNAL_LEAVE_INDICATION.

Please help me as soon, let me know your comments to the logs
Many thanks!

Abele

Unwanted_Leave_ZbossLogs.zip

[Marte Myrvold]

Hi Abele,

Thank you for uploading the logs. I have forwarded it to the development team for decoding.

abe said:

Have you still tried to reproduce the issue? (using my suggests...)
Have further news?

I have not heard back from the development team yet, so I do not know if they have been able to reproduce the issue or not. Due to summer vacation response times might be slower than usual, so I apologize for that. Hopefully I will get a response as soon as possible, and I will update you when I hear something.

Best regards,

Marte