How to re-provision a node to same address with nRF52840 DK board in mesh

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Mon, 05 Aug 2019 05:18:39 GMT

i have deleted devkey with this function while the provision complete, it has worked.Thank you

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Fri, 02 Aug 2019 14:23:14 GMT

So what happened when you call dsm_devkey_delete() for that handle ? Have you stepped into the code ?

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Fri, 02 Aug 2019 09:46:58 GMT

devkey for first provisioned node is not deleted if i use dsm_devkey_delete().

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Wed, 31 Jul 2019 14:34:58 GMT

Yes, correct.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Wed, 31 Jul 2019 13:09:15 GMT

ok i understand about dsm_clear() now, should i call dsm_devkey_delete() next to config_client_node_rest() in provisioner main.c

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Wed, 31 Jul 2019 13:05:54 GMT

I'm not sure why you mention dsm_clear() here ?

dsm_clear() is to be called on the provisionee (the node to be removed) not the provisioner.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Wed, 31 Jul 2019 11:19:42 GMT

ok, what you saying is, i have to call sdm_devkey_delete() after config_client_code_reset() in provisioner main.c but the dsm_devkey)delete() contains handle parameter. dsm_clear() will not delete this devkey?

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Wed, 31 Jul 2019 08:50:28 GMT

When you remove the node (calling config_client_node_reset() ) you can delete the device key in the dsm list on the provisioner by calling dsm_devkey_delete()

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Tue, 30 Jul 2019 15:30:32 GMT

where should i need to call this dsm_devkey_delete()

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Tue, 30 Jul 2019 14:16:16 GMT

Call this dsm_devkey_delete()

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Tue, 30 Jul 2019 12:59:07 GMT

when provision first time the devkey is 9D F7 CC 2D C8 E8 B4 AA 66 C7 DC 41 40 9D AD 4E 00 and p_devkey address is 0x200036E0. After re-provision with same node address the devkey becomes AA 36 22 75 76 7D 55 34 4A 75 33 13 42 A8 1A 8E 00 and p_devkey address is 0x200036E0. how to remove the address from device key list.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Tue, 30 Jul 2019 12:56:14 GMT

I saw in the log you post ealier, there is some log about node reset on the provisioner for example:

<t: 532066>, main.c, 702, Button 4 pressed
<t: 532068>, main.c, 716, ----- Node reset -----
<t: 532078>, main.c, 721, ----- Press reset button or power cycle the device -----
<t: 532081>, main.c, 728, Setup start after reset
<t: 532083>, main.c, 731, Waiting for node to be provisioned ...
<t: 532086>, provisioner_helper.c, 287, Scanning For Unprovisioned Devices

Please explain this.

Regarding devkey_handle, please debug the call to dsm_devkey_add() inside NRF_MESH_PROV_EVT_COMPLETE event handler in prov_evt_handler(). And check if the p_devkey in that call, would be exactly the same at the p_devkey when you first provision the device. Also please check if dsm_devkey_add () return NRF_SUCCESS or it actually return NRF_ERROR_FORBIDDEN

What I can see in the code of dsm_devkey_add is that if the address is already inside the list of device keys, then the call dev_key_handle_get() will return the handle and it will trigger NRF_ERROR_FORBIDDEN.

You would need to make sure the address is removed from the device key list.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Tue, 30 Jul 2019 12:25:29 GMT

i'm resetting provisionee node (unprovision from network) by calling config_client_node_reset().I have successfully unprovisioned the node, I facing the issue, when i start provision to same address it provision to (address: 0x0100) same address but devkey_handle becomes 0 instead of 2.Can you please clarify why the devkey_handle becomes 0 when i re-provision the node with same address.

Please describe what exactly your code doing.

I'm simply reset a node using config_client_node_reset() from provisioner and trying to re-provision it to same address.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Tue, 30 Jul 2019 11:43:08 GMT

I'm not sure I understand what you are doing. Are you saying you resetting the provisioner node ? Why would you reset the provisioner node ?

My understanding is that you want to reset the provisionee node, a normal node in the network. To reset a normal node (reset means remove/unprovision it from the network) you call config_client_node_reset() inside the config client.

This (command with CONFIG_OPCODE_NODE_RESET opcode) will be handled by the config server on the node to be reset.

Please describe what exactly your code doing.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Mon, 29 Jul 2019 15:31:04 GMT

i have added the code which was in check_network_state function for provisioned_device =0, after reset a node by pressing button 4 from main.c. If i do like this i got error for devkey_handle.can you just help me to solve this devkey_handle issue?

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Mon, 29 Jul 2019 13:03:34 GMT

This is something out of spec so you will be on your own if you want to do this. We unfortunately don't have the resource to provide you the detailed instruction on how to do it. You would need to look into the provisioner code and find where we assign the address of the new node. Look for next_device_address in the provisioner example.

I'm not sure your logging is about, why you have Flash remove complete ?

What you need to test first is to remove a node and add the node back as a new node with incremental address. After you can do that, you can start to modify to add the new node with the original address.

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Sash — Mon, 29 Jul 2019 12:31:27 GMT

<t: 461821>, provisioner_helper.c, 287, Scanning For Unprovisioned Devices
<t: 461857>, main.c, 118, Flash write complete
<t: 532066>, main.c, 702, Button 4 pressed
<t: 532068>, main.c, 716, ----- Node reset -----
<t: 532078>, main.c, 721, ----- Press reset button or power cycle the device -----
<t: 532081>, main.c, 728, Setup start after reset
<t: 532083>, main.c, 731, Waiting for node to be provisioned ...
<t: 532086>, provisioner_helper.c, 287, Scanning For Unprovisioned Devices
<t: 534849>, main.c, 146, Flash remove complete
<t: 535156>, main.c, 460, Config client event
<t: 613530>, provisioner_helper.c, 144, UUID seen: 0059000000000000975B2B98BE9A8FF2
<t: 613533>, provisioner_helper.c, 95, UUID filter matched
<t: 614293>, provisioner_helper.c, 264, Provisioning link established
<t: 693378>, provisioner_helper.c, 259, Static authentication data provided
<t: 704892>, provisioner_helper.c, 192, Provisioning completed received
<t: 704895>, provisioner_helper.c, 197, Adding device address, and device keys
<t: 704898>, provisioner_helper.c, 200, Address: 0x0100
<t: 704900>, provisioner_helper.c, 203, devkey_handle:0
<t: 627593>, app_error_weak.c, 103, Mesh error 15 at 0x00027FF1

(Error in line:\provisioner\src\provisioner_helper.c:203)

It seems device key handle gets 0 if i reset the node and re-provision it.How to solve this problem

RE: How to re-provision a node to same address with nRF52840 DK board in mesh

Hung Bui — Fri, 26 Jul 2019 13:44:45 GMT

Hi,

Mesh spec has no guide regarding this. By the spec, the address of a newly provisioned node should be the increment of the last provisioned node.

But it should be possible to provision with the previous address. You need to modify the provisioner code to store the database and when you re-provision the unprovisioned node you use the same address.