Time for configuring node increases after deleting from mesh network

[JeffZ]

Hi guys,

I have the same issue as coca1989 had 2 years ago. Did anybody found a solution?

I am using health model and simple message model. Client and Provisioner are running on one device (demoboard). I can provision and configure upto 5 server nodes (dongles). I get health events from each connected server (all 10 seconds) and I can send and receive small messages on all server nodes.

Now, I would like to remove nodes from the mesh network and reconnect them (reprovisioning and reconfiguration). This are the steps that I am doing:

1. config_client_server_bind() and config_client_server_set() to the server node I would like to remove from network
2. config_client_node_reset()
3. the server gets the node reset event (CONFIG_SERVER_EVT_NODE_RESET) from client and performs node_reset() with:  mesh_stack_config_clear() and mesh_stack_device_reset()
4. the server responds to the client with CONFIG_CLIENT_EVENT_TYPE_CANCELLED and I do dsm_devkey_delete()

After removing the server node, I can reprovision and reconfigure the node successfully (getting health events and send/receive messages). But the configuration takes longer then the first time. Repeating this process (removing node and reconnecting) increases the configuration time each time.

Here is a time table:

First configuration: 2-3 seconds
Second configuration (after removing node from mesh): 10-11 seconds
Third configuration (after removing node from mesh):20-30 seconds
Fourth configuration (after removing node from mesh): 45 -50 seconds
Fifth configuration (after removing node from mesh): >80 seconds

This is reproduceable. Rebooting the client/provisioner device after removing a server node reduces the configuration time back to 2-3 seconds, but I do not get health events and no messages.

During reconfiguration (after removing the server from network) I am getting SAR mesh events on the server node. At the first configuration (fresh device) I dont have this SAR events.

I guess I have to delete more on client side? Maybe the simple message or health is still active on the last address handles?

[Mttrinh]

Hi,

What is your setup? Which Mesh SDK are you using? Which device are you using?

Have you tried this with the latest Mesh SDK v4.2?

[JeffZ]

Hi Mttrinh, thank you for replying.

SDKs
Mesh v3.1.0
nrf5 v15.2.0_9412b96 with SoftDevice140.

Hardware
1x nordic demoboard (PCA10056, nrf52840)
3x nordic dongles (PCA10059,nrf52840)

Setup
On the Demoboard: Provisioner, Config Client, Health Client, Simple Message Client
On the 3 Dongles: Provisionee, Health Server, Simple Message Server

Mttrinh said:

Have you tried this with the latest Mesh SDK v4.2?

No, till this moment 3.1.0 was running perfectly for me.

Thx, Jeff

[JeffZ]

Mttrinh Sorry I forgot to mention that I have also running pb_remote_server on the dongles and pb_remote_client on the demoboard. Remote provisioning runs, but with the same issue (increasing time for configuration process after re-provisioning/-configuration).