Light Switch Example, nRF5 SDK Mesh

[Maxime]

Hello,

I am testing the Light Switch example and I observed a problem:

- I noticed that it was possible to reset the "server nodes" by pressing their "button 4" to leave the Mesh. There no problem there it seems to have worked very well.

- I also noticed that it was normally possible to reset the "provisioner node" by pressing its "button 4" so that it leaves the Mesh too. Unfortunately, as soon as I press it, it is impossible to add the nodes back into the network. I am always forced to delete the nRF52 and re-upload the codes so that it works again.

Have you ever observed this problem? Maybe I'm doing something wrong in my tests?

Thank you in advance for your help.

Best regards,

Maxime

[Mttrinh]

Hi,

Do you get any error codes? Can you provide me a step-by-step procedure to reproduce this?

Also, which Mesh SDK are you using? Have you made any modification to the example?

[Maxime]

Hi, Thanks for the help.

I use Mesh version 3.1.0 (with SDK version 15.3)

Here is the procedure:

- I uploaded the "provisioner", "client" and "server"  codes on 3 different nRF52840 DK.
- I pressed button 1 of the provisioner to start provisioning.
- The server and client have been provisioned.
- The system is functional, I can turn on the server leds thanks to the client.
- I can also remove the server from the mesh (with button 4).
- I can then put the server back into the mesh by performing a new provisinning.

AGAINST:

- If I reset the provisioning with button 4, I can no longer do any more provisioning for the server or client after that.

[Mttrinh]

I talked to one of our developers and it is intended behavior. 

Provisioner: First always provisions the light switch client and only then provisions servers. It can be Node-reset by pressing button 4.
Client: Cannot be Node-reset by pressing buttons. It must be re-flashed.
Servers: Can be Node-reset by pressing button 4.

If you Node-reset the Provisioner, you must also re-flash the client, otherwise, provisioner will never move forward to provision servers. If you see the RTT logs of the provisioner carefully, you will see that, provisioner waits for the unprovisioned node beacon of the Client when it has to provision the very first device in the network.