Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Mon, 17 Mar 2025 14:57:30 GMT

I will create a new private ticket with my project attached. The information concerning the 0x0000 network join could be useful to others I think

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Mon, 17 Mar 2025 14:40:15 GMT

Hi Pieter-Jan,

Apologies for the delay, I was out of office on a business trip last week.

I can either convert this case to private instead if you wish to upload the project here or you can create a new private ticket if you wish to do that instead.

Let me know which of these you prefer and we'll pick up from there!

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Tue, 11 Mar 2025 15:37:40 GMT

Hi Andreas,

Reporting is enabled by default with off-the-shelve sensors like temperature/humidity sensors. You don't need to configure reporting using the coordinator, the only necessary thing is doing the correct bindings for the relevant clusters. I want to replicate this same behaviour. This worked on SDK version <= 2.5.3 but I am just not able to get this working on later versions. I have tried the examples you have provided but sadly without any luck.
One thing I have to mention though is that I am using custom clusters. Can I perhaps send my project in a private message or in a new private ticket to see if you can get any luck with it?

Thanks,

Best Regards,

Pieter-Jan Buntinx

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Thu, 06 Mar 2025 11:27:38 GMT

Hi Pieter-Jan,

Unfortunately we don't have any examples that shows this out of the box within NCS, but here's a few pointers from a colleague of mine's unofficial samples

Set up reporting in code

Set up reporting over shell, you can follow this sample:

https://github.com/martelmy/NCS_examples/tree/main/zigbee/multi_sensor

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Tue, 25 Feb 2025 13:57:27 GMT

Hi Andreas,

Regarding the OTA, it is not different between SDK versions only between projects. The example light switch receives an update much faster than my project. You can see that the packages are send out more quickly on the coordinator for light switch project. Could this have something to do with the amount of RAM memory that is left?

For the reporting, do you have an example on how I can configure this? I have posted some code before on how I have tried enabling reporting but that does not work on any 2.6.x+ SDK version.
Currently, the behavior on SDK version 2.5.3 is as follows: from the moment I bind to the clusters of my NRF device, the device starts reporting with the configured intervals.

This is the code I am using to configure reporting on 2.5.3:

zb_zcl_reporting_info_t rep_info = {0};

    rep_info.direction                    = ZB_ZCL_CONFIGURE_REPORTING_SEND_REPORT;
    rep_info.ep                           = endpoint;
    rep_info.cluster_id                   = ZB_ZCL_CLUSTER_ID_WILMS_VENT_MONITORING;
    rep_info.cluster_role                 = ZB_ZCL_CLUSTER_SERVER_ROLE;
    rep_info.dst.profile_id               = ZB_AF_HA_PROFILE_ID;
    rep_info.u.send_info.def_min_interval = DEFAULT_MIN_REPORTING;
    rep_info.u.send_info.def_max_interval = DEFAULT_MAX_REPORTING;
    rep_info.dst.short_addr               = REPORTING_SHORT_ADDR;
    rep_info.dst.endpoint                 = REPORTING_ENDPOINT;

    for (int i = 0; i <= ZB_ZCL_ATTR_WILMS_VENT_MONITORING_NETA_ID; i++) {
        rep_info.attr_id = i;

        switch (i) {
        case ZB_ZCL_ATTR_WILMS_VENT_MONITORING_TA_ID:
        case ZB_ZCL_ATTR_WILMS_VENT_MONITORING_TB_ID:
        case ZB_ZCL_ATTR_WILMS_VENT_MONITORING_TC1_ID:
        case ZB_ZCL_ATTR_WILMS_VENT_MONITORING_TC2_ID:
        case ZB_ZCL_ATTR_WILMS_VENT_MONITORING_TD_ID:
            rep_info.u.send_info.delta.s16 = 50;
            break;
        default:
            rep_info.u.send_info.delta.u16 = 10;
            break;
        }
        zb_zcl_put_reporting_info(&rep_info, ZB_TRUE);
    }

Thanks,

Best Regards,
PIeter-Jan

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Fri, 14 Feb 2025 08:45:22 GMT

Hi Pieter-Jan

Apologies for the wait.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/zboss/CHANGELOG.html has some items regarding attribute reporting in 2.6.0 and newer. This might affect your implementation.

[quote user="pjbuntinx"]I do have one more question, if I try to do a Zigbee FOTA on the light switch example, it is reasonably fast. It takes maybe 15 minutes. When I do the FOTA on my build, it takes about 3-4 times as long. On both instances I am transferring the same OTA image, so the same amount of data. What could be the cause of this? I have compared both prj.conf's and all settings concerning FOTA seems to be the same.[/quote]

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-2.7.0.html#zigbee Seems to be related to the OTA, but I can't say what the root cause is, and a sniffer trace where you have a look at the traffic will be required to make any speculations and conclusions.

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Mon, 10 Feb 2025 16:22:33 GMT

Hi AHaug

Do you have any updates on this issue?

I do have one more question, if I try to do a Zigbee FOTA on the light switch example, it is reasonably fast. It takes maybe 15 minutes. When I do the FOTA on my build, it takes about 3-4 times as long. On both instances I am transferring the same OTA image, so the same amount of data. What could be the cause of this? I have compared both prj.conf's and all settings concerning FOTA seems to be the same.

Thanks!

Kind regards,
Pieter-Jan

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Thu, 23 Jan 2025 15:10:43 GMT

Noted, thank you for verifying. I will open a discussion with the Zigbee team w.r.t this

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Thu, 23 Jan 2025 14:11:52 GMT

In 2.6.1 this issue is also present.

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Wed, 22 Jan 2025 14:06:39 GMT

Great news indeed!

From what I can see there shouldn't be any changes to attribute reporting other than this from 2.6.0:

I'm not quite sure what this fix is about, but you're able to verify that it is present in 2.6.1 this might be the root cause. I will discuss it with the zigbee team in the meanwhile

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Tue, 21 Jan 2025 09:00:35 GMT

Hi,

Thanks for the update.
I have now tried the official release of 2.9.0 and I have not managed to reproduce the problem. So that is great news!

The reason I am so late in responding is because reporting attributes does not work the same anymore as with v2.5.2. I am not able to let my device automatically report the attributes it has. Is there something changed in this regard compared to v2.5.2? In 2.7.0 I have the same problem.

I have tried the code below to enable reporting in the new version, in 2.5.2 this worked by default and I could change the intervals using zb_zcl_put_reporting_info.

 zb_zcl_reporting_info_t rep_info = {0};

    rep_info.direction                    = ZB_ZCL_CONFIGURE_REPORTING_SEND_REPORT;
    rep_info.ep                           = endpoint;
    rep_info.cluster_id                   = ZB_ZCL_CLUSTER_ID_WILMS_VENT_OPERATION;
    rep_info.cluster_role                 = ZB_ZCL_CLUSTER_SERVER_ROLE;
    rep_info.u.send_info.def_min_interval = DEFAULT_MIN_REPORTING;
    rep_info.u.send_info.def_max_interval = DEFAULT_MAX_REPORTING;
    rep_info.u.send_info.delta.u16        = 1;
    rep_info.dst.short_addr               = 0xFFFF;
    rep_info.dst.endpoint                 = 0xFF;
    rep_info.dst.profile_id               = ZB_AF_HA_PROFILE_ID;

    for (int i = 0; i <= ZB_ZCL_ATTR_WILMS_VENT_OPERATION_ACTUAL_STATUS_ID; i++) {
        rep_info.attr_id = i;
        int put          = zb_zcl_put_reporting_info(&rep_info, ZB_TRUE);

        int start = zb_zcl_start_attr_reporting(endpoint, ZB_ZCL_CLUSTER_ID_WILMS_VENT_OPERATION, ZB_ZCL_CLUSTER_SERVER_ROLE, i);

        int check = zcl_is_attr_reported(endpoint, ZB_ZCL_CLUSTER_ID_WILMS_VENT_OPERATION, ZB_ZCL_CLUSTER_SERVER_ROLE, i);
        printf("reporting attr %i: put %i, start %i, check %i\n", i, put, start, check);
    }

Kind regards,

Pieter-Jan Buntinx

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Thu, 12 Dec 2024 10:00:46 GMT

Hi again,

Another update here. The team verifies that the fix will target NCS 2.9.0. You should already be able to see it in v2.9.0-rc1, if I am not mistaken.

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Thu, 28 Nov 2024 09:13:41 GMT

Good to hear! Thank you for the update :)

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Thu, 28 Nov 2024 08:25:48 GMT

Hi again,

The team verifies that the issue is reproducible and they are working on testing a suggested fix and to integrate it. If the test passes it will be targeted for NCS 2.9.0, which should be estimated release some time in Q1 2025.

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Wed, 27 Nov 2024 14:05:00 GMT

Hi Pieter-Jan,

The latest update I received from the Zigbee team is they are working with testing and recreating the behaviour reported. I will try to update you before the weekend with any results and/or follow up questions from the team.

Thank you for your patience and kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Wed, 27 Nov 2024 09:40:01 GMT

Hi AHaug

Do you perhaps have any update on this?

Kind regards,
Pieter-Jan

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Fri, 15 Nov 2024 09:05:17 GMT

Thank you for providing this.

Based on your description and reproduction in multiple SDKs this seems to be a bug. I've created an internal ticket to investigate this further and I'm currently waiting for some feedback from the Zigbee team for this case.

I'll update you as soon as I know something

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Thu, 14 Nov 2024 12:00:37 GMT

I have now used the Zigbee light_bulb example in NRF SDK v2.7.0. What I did was just flash the example to an NRF52840 DK board without any changes in the kconfig. To get it to join this 0x0000 network I had to factory reset the board multiple times (long pressing button 4). This in combination with resetting the board let me reproduce the problem. On Wireshark there does not seem to be happening anything special. There are only beacon requests.

It does seem it is more difficult to reproduces the problem on SDK v2.7.0. On v2.5.2, it seems to happen most of the time after just 1 factory reset (right after a fresh "erase and flash to board")

Below you can find the log.

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting ZBOSS Light Bulb example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: Set level value: 255
I: ZBOSS Light Bulb example started
I: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
I: Device started for the first time
I: Start network steering
I: Started network rejoin procedure.
I: Network steering was not successful (status: -1)
I: nRF5 802154 radio initialized
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting ZBOSS Light Bulb example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: Set level value: 255
I: ZBOSS I: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
I: Device started for the first time
I: Start network steering
I: Started network rejoin procedure.
Light Bulb example started
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: Network left (leave type: 0)
W: Device not in a network - cannot enter identify mode
W: Device not in a network - cannot enter identify mode
I: Network left (leave type: 0)
W: Device not in a network - cannot enter identify mode
W: Device not in a network - cannot enter identify mode
W: Device not in a network - cannot enter identify mode
I: nRF5 802154 radio initialized
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting ZBOSS Light Bulb example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: Set level value: 255
I: ZBOSS I: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
I: Device started for the first time
I: Start network steering
I: Started network rejoin procedure.
Light Bulb example started
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: Network left (leave type: 0)
I: Network steering was not successful (status: -1)
W: Device not in a network - cannot enter identify mode
I: Network steering was not successful (status: -1)
I: Network left (leave type: 0)
I: Network steering was not successful (status: -1)
I: Network left (leave type: 0)
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: nRF5 802154 radio initialized
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting ZBOSS Light Bulb example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: Set level value: 255
I: ZBOSS I: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
I: Device started for the first time
I: Start network steering
I: Started network rejoin procedure.
Light Bulb example started
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
I: Network left (leave type: 0)
I: Joined network successfully (Extended PAN ID: 0000000000000000, PAN ID: 0xffff)
I: Network rejoin procedure stopped.

And here is the wireshark capture:
devzone.nordicsemi.com/.../capture-light-bulb-example.pcapng

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Tue, 12 Nov 2024 13:50:24 GMT

My initial thought as well is that this should not be possible without a coordinator and/or Trust Center

Could you provide a sniffer trace lapsing over the time span of the procedure?

Could you provide a minimal sample and descriptions for how to reproduce this?

Kind regards,
Andreas

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

pjbuntinx — Tue, 12 Nov 2024 11:41:39 GMT

This happens with or without a coordinator in the proximity. When it is, It does not matter whether the coordinator is allowing new devices or not. The network the device joins is not one that should be existing.
This is not applicable to the light bulb example, but for my own device's code, I am using install_codes. So, it should normally not be possible to join another network without having the correct install code added to the coordinator.

RE: Zigbee Router device sometimes joins to 0x0000000000000000 network after factory reset

AHaug — Fri, 08 Nov 2024 14:47:20 GMT

[quote user=""]Sometimes, after I factory reset my Zigbee router device, it will immediately join a network [/quote]

Could you clarify the following when you say "a network":

Do you have multiple networks up, i.e is it a random network it joins? Is it establishing a new network that the router joins?

Do you have a sniffer trace for the device throughout the procedure you describe?

The log also says I: Network rejoin procedure stopped. Indicating that the rejoin procedure stops

Kind regards,
Andreas