[nRF52840 + zigbee] What the mean "network is open" ?

[embedholic]

I get answer from  msromero  that If zigbee network is open, then new zed can join this network.

What means that nework is open ?

I want zigbee netork is silently joinable and lent new zed can join(register) to this network in controlled method.

I mean "controlled method" that zed cannot join this network if ZC permit the zed.

Currently zed is restared with zigbee_erase_persistent_storage(ZB_FALSE), and any zed can join this network.(ZC doest not pervent a new zed from joining).

I don't use the feather install codes. I tried that but it is complicated and not work in some situation nicely.

Or

Is there any API which close network (commisioning window) with zigbee_erase_persistent_storage(ZB_FALSE)  for not admit any more ZEDs?

Thanks.

[Marjeris Romero]

Hi,

Take a look at "Section 8 Commissioning" in the Zigbee Base Device Behaviour Specification.

In our Zigbee stack you start the commissioning process by using function bdb_start_top_level_commissioning and the network will be open (new devices can join, both zr and zed) for 3 minutes. This is the default value specified in the BDB specification.

If you want to close it earlier or open it for a shorter period you can take a look at permit join request in the BDB specification and function zb_zdo_mgmt_permit_joining_req.

Best regards,

Marjeris

[embedholic]

If zigbee_erase_persistent_storage is ZB_TRUE , then the ZC behaves as you explain(Within 3 minutes, zed can join and after that time, join fails).

But i am wondering that

if zigbee_erase_persistent_storage is ZB_FALSE, New zed/zr can join all the time.

[Marjeris Romero]

Hi embedholic,

This is strange. I have verified this at my end I am also experiencing the same, but only when I use SDK v3.2.0, not SDK v.3.1.0, is this the same for you? Anyways I have reported it as a bug to our developers and I am waiting for their feedback.

[Marjeris Romero]

Mmm, have you tried to do an eraseall before flashing the program? This fixed the issue for me just now.

[embedholic]

Hi~

a) eraseall from SES IDE tool

b) flashing program with zigbee_erase_persistent_storage(ZB_FALSE)

You mean this sequence will be ok?

I tried with ZB_TRUE because new network formation is needed in some situation.

Is there any API corresponding "eraseall" ?

I want to keep program is not erased.

Thanks.

[Marjeris Romero]

Hi  embedholic,

Sorry for the late reply. Yes, make sure you always erase the flash completely (use "eraseall") before you flash a new program on the chip. Most likely this error occured because of wrong data being stored in flash, I haven't been able to reproduce the problem since.

You can erase the chip either using the "eraseall" command from the SES IDE tool or running "nrfjprog --eraseall".

NB: I did experienced the same when I first tested but quickly realized I didn't do an eraseall before flashing. Sorry for the confusion.