Zigbee disconnect

RE: Zigbee disconnect

AHaug — Wed, 24 Jan 2024 13:55:10 GMT

Hi,

I have a conclusive update from the Zigbee team and from DSR: Unfortunately it is not possible to disable Zigbee on a device so that it still remembers the nwk data stored on it in our Zigbee stack and there does not exist a general way to do this in any other versions of DSRs Zigbee stacks.

Kind regards,
Andreas

RE: Zigbee disconnect

AHaug — Tue, 23 Jan 2024 13:26:11 GMT

Hi,

Apologies for the week long wait. I've been out of office.

It looks like we've misunderstood your original query, which stated "disconnect" and not "disable". I've created a query if it is possible to disable Zigbee so that it still remembers the nwk details, and I'll get back to you when I hear more from the Zigbee team.

[quote user="Gaston"]Is the another way of shutting down Zigbee? It's strange that it's not possible to easily shut it down, like with bluetooth it's just a matter of stopping advertising.[/quote]

This seems to be correct, but I will verify when I hear back from the Zigbee teams investigation. One way that we briefly discussed that might be an alternative is to use a combination of determining a long timeout for when a router should delete an end device if it does not receive a keep-alive from the end device through zb_set_ed_timeout() (should be ~256 minutes in nRF5 and ~64 minutes in NCS by default), and zb_set_keepalive_timeout() that determines how often you send keep alive. This period is 3 seconds by default, but you should be able to get away with just sending 3 keep-alives during the span of the timeout period.

This is not a perfect way, but it could be worth investigating while waiting

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Mon, 15 Jan 2024 13:21:08 GMT

Hi,

This works, but now it leaves the whole zigbee network and can't rejoin without deleting the device from the coordinator and rejoin it manually. My purpose is not leaving the zigbee network itself, because it can't recover automatically from that. My purpose is to "shut down" zigbee when the battery is almost depleted.

I believe this code is almost the same as zb_bdb_reset_via_local_action(0U); but like I said, that's not what I want to do.

In a previous answer you posted this:

[quote userid="107683" url="~/f/nordic-q-a/106090/zigbee-disconnect/458058"]For Mgmt_leave_req:
You can call zdo_mgmt_leave_req(). If the device sets is adresse as device_adresse then it will send the leave request to itself. Make sure that you also set the rejoin flag to false so it does not try to rejoine until you've met the conditions you want it to have before rejoining. To my understanding that would be when the battery levels are sufficient in your case. There are some examplecode in the link.[/quote]

Which is why I set the device address to 0.

Is the another way of shutting down Zigbee? It's strange that it's not possible to easily shut it down, like with bluetooth it's just a matter of stopping advertising.

RE: Zigbee disconnect

AHaug — Mon, 15 Jan 2024 08:37:27 GMT

Hi,

Here's some feedback from the Zigbee team:

---

I tested their code, and this line caused the ZBOSS fatal error:

ZB_MEMSET(req->device_address, 0, sizeof(zb_ieee_addr_t));

They can just remove it. Setting the long address to 0000000000000000 will make the device send the leave request to itself, but so will omitting this field completely.

They were also doing some other questionable things, so I cleaned up their code. I’ll explain what and why, the full code is at the end.

1. The function zb_buf_get_out_delayed() will allocate an output buffer, and this output buffer will be a parameter of the function called as callback with zb_buf_get_out_delayed(). E.g:

zb_buf_get_out_delayed(my_function);

void my_function(zb_bufid_t bufid)
{
  // Here I can use bufid as the output buffer
}

So they do not need to create the param variable and can just use this buffer instead.

2. They should use the correct short addr for the device, not just set it to 1. They have to use the long address to find the short address, but it’s just a few lines of code. So I added code for getting the long address and short address, and changed dst_addr to this short_addr instead of 1.

3. They should free the output buffer with zb_buf_free(). If the command is not successful they should free it in zb_leave(). If it is successful, they should handle it in the callback by checking if the buffer exists and, if so, freeing it.

Cleaned up code:

void leave_callback(zb_uint8_t param)
{
    // Handle callback here as you want
    if (param) {
        zb_buf_free(param);
    }
}

void leave_zb(zb_bufid_t buf) {
    zb_zdo_mgmt_leave_param_t *req = NULL;
    zb_uint8_t tsn;

    // Getting short address of the device
    zb_uint16_t short_addr;
	zb_ieee_addr_t addr;
    zb_get_long_address(addr);
    short_addr = zb_address_short_by_ieee(addr);
 
    req = ZB_BUF_GET_PARAM(buf, zb_zdo_mgmt_leave_param_t);
    
    req->remove_children = ZB_FALSE;
    req->rejoin = ZB_FALSE;
    req->dst_addr = short_addr;
    tsn = zdo_mgmt_leave_req(buf, leave_callback);

    if (tsn == ZB_ZDO_INVALID_TSN){
        zb_buf_free(buf);
    }
}

...

zb_buf_get_out_delayed(leave_zb);

---

Let me know if this resolves the issue

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Wed, 10 Jan 2024 13:33:57 GMT

Hi,

I indeed called leave_zb directly, I didn't know I had to call it via the scheduler.

However, this didn't solve the issue. I still get this error log

00> <info> app: Joined network successfully on reboot signal (Extended PAN ID: 9820273807686906, PAN ID: 0x4EBC)
00> <error> app: ZBOSS assertion in file: 24, line: 1024
00> <error> app: ZBOSS assertion occurred

I indeed also think that it crashed before the leave request, hence the assert. Which file is File 24?

The leave request call is:

void leave_callback(zb_uint8_t param)
{
 //zb_zdo_mgmt_leave_res_t *resp = (zb_zdo_mgmt_leave_res_t *)zb_buf_begin(param);
 //TRACE_MSG(TRACE_ERROR, "LEAVE CALLBACK status %hd", (FMT__H, resp->status));
}

void leave_zb() {
    uint8_t param = 0;
    zb_bufid_t buf = param;
    zb_zdo_mgmt_leave_param_t *req = NULL;
    zb_ret_t ret = RET_OK;
    zb_uint8_t tsn;

    //TRACE_MSG(TRACE_ERROR, "zb_leave_req", (FMT__0));

    req = ZB_BUF_GET_PARAM(buf, zb_zdo_mgmt_leave_param_t);

    ZB_MEMSET(req->device_address, 0, sizeof(zb_ieee_addr_t));
    req->remove_children = ZB_FALSE;
    req->rejoin = ZB_FALSE;
    req->dst_addr = 1;
    tsn = zdo_mgmt_leave_req(param, leave_callback);
}

And leave_zb is called with:

zb_buf_get_out_delayed(leave_zb);

RE: Zigbee disconnect

AHaug — Wed, 10 Jan 2024 13:16:45 GMT

Hi,

After inspecting the pcap we believe that your device is not sending the leave request before crashing. Could you post the complete leave request call with parameters that you used in this trace?

The Zigbee teams suspicion is that you are calling leave_zb() incorrectly and outside of the ZBOSS scheduler. Could you try calling it using zb_buf_get_out_delayed()?

zb_buf_get_out_delayed(leave_zb);

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Tue, 09 Jan 2024 14:32:06 GMT

Hi,

The zigbee assert log I get is:

00> <error> app: ZBOSS assertion in file: 24, line: 1024
00> <error> app: ZBOSS assertion occurred

I'm not so sure if the wireshark sniff log is so usefull, as I can't see anything happening there (probably because it asserts before doing anything).

Anyway, I attached it. The network key is 83:26:c3:f1:02:82:6b:d1:13:fa:db:a7:47:36:db:dddevzone.nordicsemi.com/.../Zigbee_5F00_assert2.pcapng

RE: Zigbee disconnect

AHaug — Tue, 09 Jan 2024 07:46:28 GMT

Hi,

Could you provide us with a device log (without trace such as the one you have provided) and a separate wireshark sniff (.pcap)? See https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_sniffer_802154%2FUG%2Fsniffer_802154%2Fintro_802154.html for how to set up wireshark for sniffing Zigbee

Kind regards,
Andreas

RE: Zigbee disconnect

AHaug — Mon, 08 Jan 2024 09:34:10 GMT

Hi,

I've queried the team once more. December has been busy and there has been some organizational changes in the Zigbee team

Hopefully this will pick up speed, but unfortunately there will be some more wait.

Apologies for the inconvenience

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Mon, 08 Jan 2024 08:11:44 GMT

Hi, any updates on this? It's been more then a month ago.

RE: Zigbee disconnect

AHaug — Thu, 07 Dec 2023 15:20:49 GMT

Hi,

This is just an update that I will relay this to the Zigbee team for some input and I'll get back to you when I know some more or if they have any questions to you.

Hopefully that won't take to long, and I'll check back in with you next week regarding the status

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Tue, 05 Dec 2023 13:03:50 GMT

Hi,

See the zigbee trace (including traffic) attached.

When I call zdo_mgmt_leave_req with param 0, then I get a softreset. When I call it with 1, then it won't reset, but it won't leave the network. The attached trace file is with param 1.

devzone.nordicsemi.com/.../zigbee_5F00_trace.txt

RE: Zigbee disconnect

AHaug — Tue, 05 Dec 2023 09:41:09 GMT

You're right, my bad.

Could you provide me with a application log and sniffer trace?

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Mon, 04 Dec 2023 11:18:40 GMT

Yes it does. On line number 1 till 5 of the code that I posted you can see that callback.

RE: Zigbee disconnect

AHaug — Mon, 04 Dec 2023 09:13:09 GMT

Hi,

The example code also contains this callback

While the sample code you posted does not.

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Fri, 01 Dec 2023 14:37:04 GMT

Hi,

I'm not sure what you mean with include leave_callback? This callback is called via the zdo_mgmt_leave_req function, where should I include it?

RE: Zigbee disconnect

AHaug — Fri, 01 Dec 2023 13:42:37 GMT

Hi,

Do you also include the leave_callback? I assume you do, but just to be safe

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Wed, 29 Nov 2023 14:36:25 GMT

Hi,

Thanks.for the reply. So I should leave the network, that makes sense.

However, I can't get zdo_mgmt_leave_req() to leave the network.

I use the following code from the sample:

void leave_callback(zb_uint8_t param)
{
 zb_zdo_mgmt_leave_res_t *resp = (zb_zdo_mgmt_leave_res_t *)zb_buf_begin(param);
 TRACE_MSG(TRACE_ERROR, "LEAVE CALLBACK status %hd", (FMT__H, resp->status));
}

void leave_zb(uint8_t param) {
    zb_bufid_t buf = param;
    zb_zdo_mgmt_leave_param_t *req = NULL;
    zb_ret_t ret = RET_OK;
    zb_uint8_t tsn;

    TRACE_MSG(TRACE_ERROR, "zb_leave_req", (FMT__0));

    req = ZB_BUF_GET_PARAM(buf, zb_zdo_mgmt_leave_param_t);

    ZB_MEMSET(req->device_address, 0, sizeof(zb_ieee_addr_t));
    req->remove_children = ZB_FALSE;
    req->rejoin = ZB_FALSE;
    req->dst_addr = 1;
    tsn = zdo_mgmt_leave_req(param, leave_callback);
}

I call leave_zb with parameter 0.

When I call it, I get a device reset because the zigbee stack crashed.

What should I change in the code?

RE: Zigbee disconnect

AHaug — Wed, 29 Nov 2023 11:34:01 GMT

Hi,

I've asked around some and here's an alternative to what you can do:

For Mgmt_leave_req:
You can call zdo_mgmt_leave_req(). If the device sets is adresse as device_adresse then it will send the leave request to itself. Make sure that you also set the rejoin flag to false so it does not try to rejoine until you've met the conditions you want it to have before rejoining. To my understanding that would be when the battery levels are sufficient in your case. There are some examplecode in the link.

Factory reset

For factory reset you can call zb_bdb_reset_via_local_action(). This will make the device run a NLME leave and remove all Zigbee persistent data except the outgoing NWK frame counter and the aplication dataset (if there are any present)

Let me know if this answers your question!

Kind regards,
Andreas

RE: Zigbee disconnect

AHaug — Tue, 28 Nov 2023 14:53:10 GMT

Allright, thank you for verifying

I would say that this should be possible to do as long as you handle the reconnection procedure correct

I will have ask around a bit if someone knows if there are an existing API, but in the meanwhile you can have a look in the API reference for Zigbee in https://infocenter.nordicsemi.com/topic/sdk_tz_v4.2.0/modules.html

Kind regards,
Andreas

RE: Zigbee disconnect

Gueston — Tue, 28 Nov 2023 14:06:03 GMT

Hi,

nRF5 SDK for Thread and Zigbee v4.2.0

Yes I still want to use other features of the device, so I don't want a powerdown. With bluetooth I simply stop the advertising with low battery, so I'm looking like a similar feature to 'disconnect' from the zigbee router.

RE: Zigbee disconnect

AHaug — Tue, 28 Nov 2023 13:53:59 GMT

Hi,

I see that you've listed the nRF52833. Could you also state which SDK and version of said SDK you're using?

Could you verify if you still want to use other features of the device, such as the BLE features and/or other items, or do you simply want to power down the device and let it sleep as long as possible?

Kind regards,
Andreas