Error 35 RET_INVALID_STATE in Zigbee Light Bulb Example

[Peter K.]

Hi everyone,

I'm currently doing some experiments with the zigbee feature of NRF52840 and I'm working with an PCA10056 development board.

The light_bulb example however keeps on throwing an error and rebooting once I press button 4 in order to start identification:

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
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
LiI: Device started for the first time
I: Start network steering
I: Started network rejoin procedure.
ght Bulb example started
I: Network steering was not successful (status: -1)
I: Network steering was not successful (status: -1)
---> Button 4 gets pressed here
I: Enter identify mode
E: ERROR 35 [RET_INVALID_STATE] at ../src/main.c:205
--> NRF52840 reboots
I: nRF5 802154 radio initialized
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
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: ZBOSSI: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
 LI: Device started for the first time
I: Start network steering

This is the out-of-the box light build example that comes with nRF SDK 1.9.1 (built with default VS-Code setup, no modifications or configuration changes)

Do you have any hints for debugging that problem?

Regards,

Peter

[mytzyiay]

I think it is erroring out because the node has not yet joined a Zigbee network, therefore a finding-and-binding request would not be received by any other node?

The logic was recently changed here, so in the next rev of the SDK it should not be a fatal error: https://github.com/nrfconnect/sdk-nrf/commit/7bf39575ce9a72dc7f35879bdcb7f6535a259cda

[Peter K.]

Ahh, thank you for the hint!

I was too busy debugging the RET_INVALID_STATE (wasn't expecting the button press to cause the system to reboot) before actually noticing that my existing Zigbee network uses a channel different than the default channel 16

Thankk you!