About deleting node, then configuring node failed

[caca1989]

nordic team，

sdk：mesh2.11+sdk15.1

Follow the steps below：

Configuring Node(adress = 0x100) ->delete node(adress = 0x100) 

Repeat the above action，I found a problem

1.Every time you configure node, it is longer than the last time.

2.Repeat more than ten times, the configuration will fail

3.I don't understand why the previous configuration can be successfully configured, and then it will fail after multiple configurations.

The last few configuration logs are as follows：

<t:   15989889>, node_setup.c,  713, Configuring Node: 0x0100
<t:   15989894>, node_setup.c,  627, Config client setup: addr_handle:1 devkey_handle:2 
<t:   15989899>, node_setup.c,  383, Getting composition data
<t:     195737>, mesh_main.c,  488, Config client event
<t:     195742>, node_setup.c,  646, Acknowledged message status not received 
<t:     195747>, node_setup.c,  650, Retry ...
<t:     195751>, node_setup.c,  383, Getting composition data
<t:     559880>, mesh_main.c, 1580, scan device UUID: : F3185691
<t:     559884>, mesh_main.c, 1583, Provisoned Nodes: 1, Configured Nodes: 0 Now Address: 0x0100, Next Address: 0x0101
 <t:     559891>, mesh_main.c, 1585, Waiting for Server node to be provisioned ...
<t:     559897>, provisioner_helper.c,  315, Scanning For Unprovisioned Devices
<t:    1178805>, mesh_main.c,  488, Config client event
<t:    1178810>, node_setup.c,  646, Acknowledged message status not received 
<t:    1178815>, node_setup.c,  650, Retry ...
<t:    1178819>, node_setup.c,  383, Getting composition data
<t:    1305265>, mesh_main.c,  488, Config client event
<t:    1305270>, node_setup.c,  393, Adding appkey
<t:    1312836>, mesh_main.c,  488, Config client event
<t:    1312840>, node_setup.c,  251, Unexpected opcode: exp 0x8003  rx 0x0002
<t:    1389149>, mesh_main.c,  488, Config client event
<t:    1389153>, node_setup.c,  289, opcode status field: 0 
<t:    1389159>, node_setup.c,  404, App key bind: Health server
<t:    1390006>, mesh_main.c,  488, Config client event
<t:    1390010>, node_setup.c,  289, opcode status field: 0 
<t:    1390015>, node_setup.c,  419, App key bind: Simple On/Off server
<t:    1390962>, mesh_main.c,  488, Config client event
<t:    1390966>, node_setup.c,  289, opcode status field: 0 
<t:    1390971>, node_setup.c,  472, Setting publication address for the health server to 0x0001
<t:    1394605>, mesh_main.c,  488, Config client event
<t:    1394610>, node_setup.c,  289, opcode status field: 0 
<t:    1394615>, node_setup.c,  510, Adding subscription
<t:    1396575>, mesh_main.c,  488, Config client event
<t:    1396579>, node_setup.c,  289, opcode status field: 0 
<t:    1396584>, mesh_main.c,  304, Configuration of device 0 successful
<t

<t:    2299625>, node_setup.c,  713, Configuring Node: 0x0100
<t:    2299631>, node_setup.c,  627, Config client setup: addr_handle:1 devkey_handle:2 
<t:    2299636>, node_setup.c,  383, Getting composition data
<t:    3282690>, mesh_main.c,  488, Config client event
<t:    3282695>, node_setup.c,  646, Acknowledged message status not received 
<t:    3282700>, node_setup.c,  650, Retry ...
<t:    3282704>, node_setup.c,  383, Getting composition data
<t:    4265758>, mesh_main.c,  488, Config client event
<t:    4265763>, node_setup.c,  646, Acknowledged message status not received 
<t:    4265768>, node_setup.c,  650, Retry ...
<t:    4265772>, node_setup.c,  383, Getting composition data
<t:    4494093>, mesh_main.c,  488, Config client event
<t:    4494097>, node_setup.c,  393, Adding appkey
<t:    4496973>, mesh_main.c,  488, Config client event
<t:    4496978>, node_setup.c,  289, opcode status field: 0 
<t:    4496982>, node_setup.c,  404, App key bind: Health server
<t:    4498510>, mesh_main.c,  488, Config client event
<t:    4498515>, node_setup.c,  289, opcode status field: 0 
<t:    4498519>, node_setup.c,  419, App key bind: Simple On/Off server
<t:    4499292>, mesh_main.c,  488, Config client event
<t:    4499297>, node_setup.c,  289, opcode status field: 0 
<t:    4499302>, node_setup.c,  472, Setting publication address for the health server to 0x0001
<t:    4524602>, mesh_main.c,  488, Config client event
<t:    4524606>, node_setup.c,  289, opcode status field: 0 
<t:    4524611>, node_setup.c,  510, Adding subscription
<t:    4526255>, mesh_main.c,  488, Config client event
<t:    4526260>, node_setup.c,  289, opcode status field: 0 
<t:    4526264>, mesh_main.c,  304, Configuration of device 0 successful



<t:    8125810>, node_setup.c,  713, Configuring Node: 0x0100
<t:    8125815>, node_setup.c,  627, Config client setup: addr_handle:1 devkey_handle:2 
<t:    8125821>, node_setup.c,  383, Getting composition data
<t:    9108878>, mesh_main.c,  488, Config client event
<t:    9108883>, node_setup.c,  646, Acknowledged message status not received 
<t:    9108888>, node_setup.c,  650, Retry ...
<t:    9108892>, node_setup.c,  383, Getting composition data
<t:   10091946>, mesh_main.c,  488, Config client event
<t:   10091951>, node_setup.c,  646, Acknowledged message status not received 
<t:   10091956>, node_setup.c,  650, Retry ...
<t:   10091960>, node_setup.c,  383, Getting composition data
<t:   10790693>, mesh_main.c,  488, Config client event
<t:   10790697>, node_setup.c,  393, Adding appkey
<t:   10793730>, mesh_main.c,  488, Config client event
<t:   10793735>, node_setup.c,  289, opcode status field: 0 
<t:   10793740>, node_setup.c,  404, App key bind: Health server
<t:   10795293>, mesh_main.c,  488, Config client event
<t:   10795298>, node_setup.c,  289, opcode status field: 0 
<t:   10795302>, node_setup.c,  419, App key bind: Simple On/Off server
<t:   10796226>, mesh_main.c,  488, Config client event
<t:   10796231>, node_setup.c,  289, opcode status field: 0 
<t:   10796236>, node_setup.c,  472, Setting publication address for the health server to 0x0001
<t:   10821536>, mesh_main.c,  488, Config client event
<t:   10821540>, node_setup.c,  289, opcode status field: 0 
<t:   10821545>, node_setup.c,  510, Adding subscription
<t:   10823009>, mesh_main.c,  488, Config client event
<t:   10823013>, node_setup.c,  289, opcode status field: 0 
<t:   10823018>, mesh_main.c,  304, Configuration of device 0 successful


<t:   13200901>, node_setup.c,  713, Configuring Node: 0x0100
<t:   13200907>, node_setup.c,  627, Config client setup: addr_handle:1 devkey_handle:2 
<t:   13200912>, node_setup.c,  383, Getting composition data
<t:   14183966>, mesh_main.c,  488, Config client event
<t:   14183971>, node_setup.c,  646, Acknowledged message status not received 
<t:   14183976>, node_setup.c,  650, Retry ...
<t:   14183980>, node_setup.c,  383, Getting composition data
<t:   15167034>, mesh_main.c,  488, Config client event
<t:   15167039>, node_setup.c,  646, Acknowledged message status not received 
<t:   15167044>, node_setup.c,  650, Retry ...
<t:   15167048>, node_setup.c,  383, Getting composition data
<t:   16150102>, mesh_main.c,  488, Config client event
<t:   16150107>, node_setup.c,  646, Acknowledged message status not received 
<t:   16150112>, mesh_main.c,  367, Configuration of device 0 failed. Press Button 1 to retry.
<t:   16150118>, provisioner_helper.c,  321, stop For Unprovisioned Devices

client delete serve code：

    ERROR_CHECK(dsm_devkey_delete(deviceInfo[index].devkey_handle));

Server side：

  node_reset();

I suspect that deleting the server node is not complete, causing such a problem.

So, can you give me some help, thank you！

[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,

This is a really old thread, I suggest you create a new ticket for this issue and we will handle it there.

[JeffZ]

Hi Mttrinh, thanks for advising. I created a new ticket.