Unwanted "Leave" command from coordinator

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Mon, 05 Sep 2022 11:04:21 GMT

Hi Abele,

[quote user="Marte.M"] But if that is the case, you should double the NVRAM memory capacity.[/quote]

If you plan on connecting 100 devices then you should double the NVRAM memory capacity.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Thu, 01 Sep 2022 12:27:36 GMT

Hi Marte,

[quote userid="92402" url="~/f/nordic-q-a/89723/unwanted-leave-command-from-coordinator/384332"]This depends on the application, the network configuration and how often the data needs to be stored in the flash memory. If the configuration of the network is to be changed often, it would be smart to increase the flash memory allocated for the ZBOSS NVRAM.[/quote]

I'm not sure to good understand this answer ... when a End Node is joined by the coordinator there are some parameters stored into Zboss Nvram. If I have 100 different nodes in the network, this NVRAM amount is enough?

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Thu, 01 Sep 2022 12:11:27 GMT

Hi Abele,

[quote user="Abele"]The question about the needed amount of NVRAM for 100 end node,[/quote]

This depends on the application, the network configuration and how often the data needs to be stored in the flash memory. If the configuration of the network is to be changed often, it would be smart to increase the flash memory allocated for the ZBOSS NVRAM.

The default value should be sufficient unless you actually plant to connect so many devices to the network. But if that is the case, you should double the NVRAM memory capacity.

[quote user="Abele"]how can I contact you if I need help during the migration to new SDK 4.2.0?[/quote]

Remember that factory reset is required when the device is upgraded from SDK v3 to v4, so do not forget about this.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Thu, 01 Sep 2022 11:49:34 GMT

Hi Abele,

[quote user="Abele"]The question about the needed amount of NVRAM for 100 end node, for the previous Zboss version iI received excel file whit compute of space. You can see on this thread what I means devzone.nordicsemi.com/.../zigbee-maximum-device-number[/quote]

I will ask the development team and get back to you.

[quote user="Abele"]Last question, how can I contact you if I need help during the migration to new SDK 4.2.0?[/quote]

Create tickets on DevZone about your specific issues.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Thu, 01 Sep 2022 08:18:20 GMT

Thanks for answers, Marte.
For BLE and DFU integration (that I have already done in actual release) I follow same steps I have already done on SDK 3.2.0, and so also for device annonce and update, and to start network formation.

The question about the needed amount of NVRAM for 100 end node, for the previous Zboss version iI received excel file whit compute of space. You can see on this thread what I means devzone.nordicsemi.com/.../zigbee-maximum-device-number

Last question, how can I contact you if I need help during the migration to new SDK 4.2.0?

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Wed, 31 Aug 2022 11:34:16 GMT

Hi Abele,

I am sorry for the delay.

[quote user="Abele"]- adding BLE gatt/services and DFU bootloader integration[/quote]

We do have some nRF5 SDK Bluetooth guides on Devzone here: Bluetooth low energy , such as this guide for services: Bluetooth low energy Services, a beginner's tutorial . As for DFU there is a guide for getting started with the secure DFU bootloader here: Getting started with Nordic's Secure DFU bootloader, a step by step guide . You should also be able to find information in our documentation on infocenter. If you have more problems with this part, please create a new ticket.

[quote user="Abele"]Handler when NEW devices will accepted on network (we need to read from device some info and store on BLE GATT)[/quote]

You can use the ZB_ZDO_SIGNAL_DEVICE_ANNCE or ZB_ZDO_SIGNAL_DEVICE_UPDATE signals in zboss_signal_handler() to handle when a device is updated/joins the network. See components/zigbee/common/zigbee_helpers.c for how these signals are used there.

[quote user="Abele"]- Zboss method to handle end-node steering and net formation (user must manually activate devices network joining process)[/quote]

Do you mean that the user must be able to open the network on the coordinator? Because if so, then you can look at the light coordinator example. There the network is reopened if button 1 is pressed:

case BSP_EVENT_KEY_0:
    UNUSED_RETURN_VALUE(ZB_SCHEDULE_APP_ALARM_CANCEL(steering_finished, ZB_ALARM_ANY_PARAM));

    comm_status = bdb_start_top_level_commissioning(ZB_BDB_NETWORK_STEERING);

[quote user="Abele"]Computing of needed NVRAM for 100 Zigbee nodes, and how to handle it[/quote]

We have some information about NVRAM in our documentation here: https://infocenter.nordicsemi.com/topic/sdk_tz_v4.2.0/group__zboss__nvram.html

I hope this answers some of the questions. If you have specific questions about any of this, please create a new ticket for the questions, as they are no longer directly related to the original issue in this ticket. Thank you!

Best regards,

MArte

RE: Unwanted "Leave" command from coordinator

abe — Mon, 22 Aug 2022 08:52:23 GMT

Hi Marte,
I'm evaluating to use Segger Embedded Studio to migrate my project to SDK 4.2.0.
It's very probably that I will need help for several things, here a starting list:
- adding BLE gatt/services and DFU bootloader integration
- Handler when NEW devices will accepted on network (we need to read from device some info and store on BLE GATT)
- Zboss method to handle end-node steering and net formation (user must manually activate devices network joining process)
- Computing of needed NVRAM for 100 Zigbee nodes, and how to handle it
- using and handle of FDS storage for store some data used by custom application (without issues with Zboss NVRAM)
This is main list, but I think that we could need other help during the development.
I will inform you that our product is a Zigbee Coordinator, and the previous development (from SDK3.2) was made integrating DFU bootloader and CLI agent configured as coordinator into Multiprotocol Ble-Zigbee template
Let me know for these helps.
Many thanks in advance.
Abele

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Fri, 05 Aug 2022 06:58:48 GMT

Hi Abele,

Thanks for letting me know. For some reason DevZone changed the link to try to link to something on DevZone instead. I have updated the link, but it is also here: https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/zigbee_r22_migration.html.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Thu, 04 Aug 2022 15:11:57 GMT

Hi Marte,
I will inform my customer for your answers.
Nordic help in migration to 4.1 would be very appreciated, I'll keep you updated in next weeks when I can start this work

Regards

Abele

PS the link you paste seems not working ...

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Thu, 04 Aug 2022 14:49:33 GMT

Hi Abele,

As stated in my previous reply, you will not be able to certify Zigbee products that are using R21 of the Zigbee specification anymore. This is not a limitation on our side, but by CSA. Even if the leave problem is fixed you will not be able to certify a new product developed in v3.2 of the SDK.

Support for R22 of the specification was added in v4.0.0 and has been supported in our SDKs for more than 2,5 years already. I would really recommend migrating to v4.2 if possible, as this version supports ZCL8 as well and there was a lot of fixes between this version and the previous one, but if that is absolutely not possible then you should at least migrate to v4.1. There are still a lot of changes between v3.2 and v4.1, but it will not be as many as with v4.2, and there is still support for IAR. As mentioned by Kenneth previously we have a migration guide available in our documentation: https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/zigbee_r22_migration.html.

If you experience any issues with v4.1 I will try to help, but if these are bugs that have been fixed in later versions of the stack I unfortunately cannot help.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Thu, 04 Aug 2022 11:31:57 GMT

I'm very disappointed for this answer, when I developed the application the SDK 3.x was the new available, and now after few year Nordic don't support it anymore.
I hoped a best help to issues, expecially when the alternative solution porposed has high impact on already developed project: migrating to the latest SDK practically forces to redo the project, with all difficulty related.
In addition, the new SDK don't support IAR EWARM (the 3.2 yes, I have developed my project with IAR EWARM)
Last, peraphs you can ask to development team if there is a possibility to "disable" the leave command on ZigBee SDK 3.2 ?
This could be a "patch" that has minor impact the project.
Please, let me know as soon

Best regards,
Abele

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Thu, 04 Aug 2022 11:01:25 GMT

Hi Abele,

I got a response from the development team today. They are not able to prioritize resources for debugging logs from a product based on an old stack. The nRF5 SDK for Thread and Zigbee v3.2 has a Zigbee stack supporting specification version R21 – which is not certifiable anymore by CSA. To officially introduce new product into the field (including firmware update), after even minimal change in firmware, it must go throughout product certification. Thus switching to newer platform using R22 is essential.

Additionally, there is a good chance that this bug is fixed in newer versions of the stack and that the issue will resolve itself when migrating to the latest SDK.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Tue, 02 Aug 2022 11:30:30 GMT

Ok, thanks
Please, follow any update and let me know as soon any further news

Abele

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Tue, 02 Aug 2022 11:06:37 GMT

Hi Abele,

I do not have any news yet, but I have asked the development team for an update.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Mon, 01 Aug 2022 06:51:45 GMT

Hi Marte,

have any news?
Keep me updated, we nee to solve the issue
Many thanks

Abele

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Tue, 26 Jul 2022 10:56:06 GMT

Hi Abele,

Yes, the format is as expected of ZBOSS trace logs.

Unfortunately we are short on staff due to summer vacations, so you must expect some wait time before the development team are done decoding and looking through the logs. I apologize for the inconvenience.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Tue, 26 Jul 2022 07:30:19 GMT

many thanks Marte!
Then the format of log output is as expected, right?
Keep me updated. My customer is worried ... it ask me often if we have identified the issue.

Abele

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Tue, 26 Jul 2022 07:20:27 GMT

Hi Abele,

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

[quote user="Abele"]Have you still tried to reproduce the issue? (using my suggests...)
Have further news?[/quote]

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

RE: Unwanted "Leave" command from coordinator

abe — Mon, 25 Jul 2022 13:35:32 GMT

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

devzone.nordicsemi.com/.../Unwanted_5F00_Leave_5F00_ZbossLogs.zip

RE: Unwanted "Leave" command from coordinator

abe — Mon, 25 Jul 2022 12:39:31 GMT

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

RE: Unwanted "Leave" command from coordinator

abe — Mon, 25 Jul 2022 08:08:56 GMT

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

RE: Unwanted "Leave" command from coordinator

abe — Tue, 19 Jul 2022 09:55:26 GMT

Hello Marte,

[quote userid="92402" url="~/f/nordic-q-a/89723/unwanted-leave-command-from-coordinator/377561"]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.[/quote]

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

[quote userid="92402" url="~/f/nordic-q-a/89723/unwanted-leave-command-from-coordinator/377561"]I pretty sure that even attempt to change ZBOSS libs will require factory reset of the device.[/quote]

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 , ...)

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Tue, 19 Jul 2022 09:17:51 GMT

Hi Abele,

I have an update from the developers as well:

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.
I pretty sure that even attempt to change ZBOSS libs will require factory reset of the device.
ZBOSS logs could also be configured to be printed over RTT so maybe the additional connector for serial is not required.
Customer claims that the Link Status issue could be reproduced with the original CLI example.
Could you ask them to how can it be reproduced? I have tried a bit but wasn't able to reproduce it.

Best regards,

Marte

RE: Unwanted "Leave" command from coordinator

abe — Tue, 19 Jul 2022 09:05:48 GMT

Thanks Marte
I next days (or next week) I will arrange the needed modify to have Zboss Log Out and I will try to reproduce the issue (but it is not easy, the issue is randomly)
As I have news I will send you the results
Abele

RE: Unwanted "Leave" command from coordinator

Marte Myrvold — Tue, 19 Jul 2022 08:34:20 GMT

Hi Abele,

Thank you for providing the additional information!

[quote user="Abele"]then it is not possible to update only Zboss Stack? I have already done it from 3.0.0 to 3.1,0[/quote]

It is possible to do so, but the SDK might not be compatible with a different version of ZBOSS than it was made for. Additionally, platform certification points out one particular version of ZBOSS, so you will not be able to use platform certification if you use a different version of the ZBOSS stack than the SDK was certified with.

[quote user="Abele"]Zboss log need to be enabled (how we can do it?)[/quote]

This is described in the documentation here: Debugging, but what you need to do is to:

Replace the libzboss libraries in your project with the files located in <InstallFolder>/external/zboss/lib/debug
Configure the following in sdk_config.h:

Configuration option	Value for nRF52840	Value for nRF52833*
NRF_LOG_DEFAULT_LEVEL	4	4
NRF_LOG_BUFSIZE	65536	32768
NRF_LOG_MSGPOOL_ELEMENT_COUNT	32	32
NRF_LOG_MSGPOOL_ELEMENT_SIZE	40	40
NRF_LOG_BACKEND_RTT_TX_RETRY_CNT	100	100
SEGGER_RTT_CONFIG_BUFFER_SIZE_UP	32768	512

Then change these in main():

ZB_SET_TRACE_LEVEL(ZIGBEE_TRACE_LEVEL);
ZB_SET_TRACE_MASK(ZIGBEE_TRACE_MASK);
to
ZB_SET_TRACE_LEVEL(4);
ZB_SET_TRACE_MASK(TRACE_SUBSYSTEM_ZCL | TRACE_SUBSYSTEM_ZDO | TRACE_SUBSYSTEM_NWK | TRACE_SUBSYSTEM_SECUR);

The UART log from nRF Should output some character strings. Please save this log and upload it here so I can forward it to the developers for decoding.

Best regards,

Marte