Zigbee CLI

[nanbuwks]

Hello!

I use Zigbee CLI example and multi_sensor example on nRF52840.
(examples/zigbee/experimental/cli/cli_agent_router and examples/zigbee/experimental/multi_sensor)

I modify these programs as:

#define ERASE_PERSISTENT_CONFIG ZB_TRUE

When both device same time start, multi_sensor join to network well.

CLI:

> bdb role zc
Coordinator set
Done
> bdb start
Started coordinator
Done
>

multi_sensor:

<info> app: Production configuration is not present or invalid (status: -1)
<info> app: Zigbee stack initialized
<info> app: Device started for the first time
<info> app: Start network steering
<info> app: Joined network successfully (Extended PAN ID: f4ce363f1c7ea7d6, PAN ID: 0xC086)

But, case of multi_sensor start after CLI start about 3 minutes, multi_sensor has fail to Join to network.

<info> app: Production configuration is not present or invalid (status: -1)
<info> app: Zigbee stack initialized
<info> app: Device started for the first time
<info> app: Start network steering
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
<error> app: Failed to join network (status: -1)
.
.
.

So, When this happens, how do I re-accept network steering in the CLI?

Thanks.

[Edvin]

Hello,

It should just be a matter of using the command "bdb start" on the CLI coordinator again. A short test on my desk showed that this worked. 

FYI, the bdb start command ultimately calls

bdb_start_top_level_commissioning(ZB_BDB_NETWORK_STEERING);

Which is the same as the light_coordinator example does when you press button 1 (if you want to add more bulbs/switches after 3 minutes).

BR,

Edvin