Mesh Provisioner stuck at configuring node

[xianii]

Env:
nRF52832
Mesh SDK 3.2.0

When I reset a node after it's provisioned but not configured, the provisioner would keep trying to configure it, and would not be able to provision any other nodes.

Log:
<t:          0>, main.c,  830, ----- BLE Mesh Light Switch Provisioner Demo -----
<t:        543>, main.c,  576, Initializing and adding models
<t:        578>, main.c,  435, Restored: App data
<t:        580>, main.c,  632, Restored: Handles 
<t:        582>, provisioner_helper.c,  322, m_netkey_handle:0 m_appkey_handle:0 m_self_devkey_handle:1
<t:        587>, main.c,  866, <start> 
<t:        672>, main.c,  849, Starting application ...
<t:        675>, main.c,  851, Provisoned Nodes: 2, Configured Nodes: 1 Next Address: 0x0102
<t:        679>, main.c,  852, Dev key : 60BB50E165ACF79181EE9473CFB8D0E9
<t:        681>, main.c,  853, Net key : 873F6D8051A34438CE9AAC880BFB87E8
<t:        685>, main.c,  854, App key : 1B1F8AE1AAD2DA0A5050D797B8EF6A5F
<t:        687>, main.c,  855, Press Button 1 to start provisioning and configuration process. 
<t:      49746>, user_api.c,   67, Waiting for provisioned node to be configured ...
<t:      49749>, node_setup.c,  676, Configuring Node: 0x0101
<t:      49753>, node_setup.c,  566, Config client setup: devkey_handle:3 addr_handle:2
<t:      49756>, node_setup.c,  381, Getting composition data
<t:    2015846>, main.c,  366, Config client event
<t:    2015848>, node_setup.c,  614, Acknowledged message status not received 
<t:    2015851>, node_setup.c,  618, Retry ...
<t:    2015853>, node_setup.c,  381, Getting composition data
<t:    3981943>, main.c,  366, Config client event
<t:    3981945>, node_setup.c,  614, Acknowledged message status not received 
<t:    3981948>, node_setup.c,  618, Retry ...
<t:    3981950>, node_setup.c,  381, Getting composition data
<t:    5948040>, main.c,  366, Config client event
<t:    5948042>, node_setup.c,  614, Acknowledged message status not received 
<t:    5948045>, main.c,  298, Configuration of device 1 failed.
<t:    5948049>, user_api.c,   67, Waiting for provisioned node to be configured ...
<t:    5948052>, node_setup.c,  676, Configuring Node: 0x0101
<t:    5948055>, node_setup.c,  566, Config client setup: devkey_handle:3 addr_handle:2
<t:    5948058>, node_setup.c,  381, Getting composition data
<t:    7914148>, main.c,  366, Config client event
<t:    7914150>, node_setup.c,  614, Acknowledged message status not received 
<t:    7914153>, node_setup.c,  618, Retry ...
<t:    7914155>, node_setup.c,  381, Getting composition data
<t:    9880245>, main.c,  366, Config client event
<t:    9880247>, node_setup.c,  614, Acknowledged message status not received 
<t:    9880250>, node_setup.c,  618, Retry ...
<t:    9880252>, node_setup.c,  381, Getting composition data
<t:   11846342>, main.c,  366, Config client event
<t:   11846344>, node_setup.c,  614, Acknowledged message status not received 
<t:   11846347>, main.c,  298, Configuration of device 1 failed.
<t:   11846351>, user_api.c,   67, Waiting for provisioned node to be configured ...

And I want to know how to delete the invalid provision information, so I can make it back to the normal state in which could provision and configure new nodes.

[Mttrinh]

Hi,

Are you using the static provisioner from our SDK or the nRF Mesh app to provision the nodes?

[Mttrinh]

Could you also try with an unmodified version?

[xianii]

Tested on original light_switch\provisioner project in Mesh SDK v320.

I uses 1 provisioner and 2 client in the test.

Test process:

1. Power on provisioner then start provision
2. Power on client A
3. Power off client A right after provisioned but before configured
4. The provisioner will retry 3 times
5. Power on client B
6. Reset the provisioner
7. Mesh error occur on the provisioner

Log is here.

<t:          0>, main.c,  579, ----- BLE Mesh Light Switch Provisioner Demo -----
<t:        552>, main.c,  516, Initializing and adding models
<t:        563>, main.c,  163, Unable to add flash manager for app data
<t:        566>, main.c,  560, Setup defaults: Adding keys, addresses, and bindings 
<t:        718>, provisioner_helper.c,  354, netkey_handle: 0
<t:        728>, main.c,  608, <start> 
<t:       1099>, main.c,  109, Flash write complete
<t:       1165>, main.c,  596, Starting application ...
<t:       1168>, main.c,  598, Provisoned Nodes: 0, Configured Nodes: 0 Next Address: 0x0100
<t:       1171>, main.c,  599, Dev key : B741F1C2D482B36EC52E484D296EF35F
<t:       1174>, main.c,  600, Net key : D4EE131605230021F572BC3B37CA52E5
<t:       1177>, main.c,  601, App key : 7CEB994F805F94BDC2F60F0DB5864E9C
<t:       1180>, main.c,  602, Press Button 1 to start provisioning and configuration process. 
0<t:     269359>, main.c,  476, Button 1 pressed
<t:     269361>, main.c,  378, Waiting for Client node to be provisioned ...
<t:     269364>, provisioner_helper.c,  303, Scanning For Unprovisioned Devices
<t:     271194>, provisioner_helper.c,  138, UUID : 16F073B02CAB4C4C8DCF0947C3A919A9
<t:     271197>, provisioner_helper.c,  142, ^RSSI: -50
<t:     271199>, provisioner_helper.c,  147, ^URI Hash: BE915706
<t:     271204>, provisioner_helper.c,  153, URI hash matched. Provisioning ...
<t:     276354>, provisioner_helper.c,  274, Provisioning link established
<t:     289166>, provisioner_helper.c,  269, Static authentication data provided
<t:     300888>, provisioner_helper.c,  207, Provisioning completed received
<t:     300891>, provisioner_helper.c,  212, Adding device address, and device keys
<t:     300897>, provisioner_helper.c,  229, Addr: 0x0100 addr_handle: 0 netkey_handle: 0 devkey_handle: 2
<t:     304579>, provisioner_helper.c,  166, Local provisioning link closed: prov_state: 2  remaining retries: 2
<t:     304583>, main.c,  298, Provisioning successful
<t:     304586>, provisioner_helper.c,  196, Provisioning complete. Node addr: 0x0100 elements: 3
<t:     304590>, node_setup.c,  689, Configuring Node: 0x0100
<t:     304593>, node_setup.c,  582, Config client setup: devkey_handle:2 addr_handle:0
<t:     304597>, node_setup.c,  352, Getting composition data
<t:     304664>, main.c,  109, Flash write complete
<t:     304723>, main.c,  109, Flash write complete
<t:    2270687>, main.c,  350, Config client event
<t:    2270689>, node_setup.c,  630, Acknowledged message status not received 
<t:    2270692>, node_setup.c,  634, Retry ...
<t:    2270694>, node_setup.c,  352, Getting composition data
<t:    4236784>, main.c,  350, Config client event
<t:    4236786>, node_setup.c,  630, Acknowledged message status not received 
<t:    4236789>, node_setup.c,  634, Retry ...
<t:    4236791>, node_setup.c,  352, Getting composition data
<t:    6202881>, main.c,  350, Config client event
<t:    6202883>, node_setup.c,  630, Acknowledged message status not received 
<t:    6202887>, main.c,  291, Configuration of device 0 failed. Press Button 1 to retry.
3<t:    7964683>, main.c,  476, Button 4 pressed
<t:    7964685>, main.c,  490, ----- Node reset -----
<t:    7964691>, main.c,  496, ----- Press reset button or power cycle the device  -----
<t:    7964765>, main.c,  137, Flash remove complete
0<t:    8184175>, main.c,  476, Button 1 pressed
<t:    8184177>, main.c,  378, Waiting for Client node to be provisioned ...
<t:    8184180>, provisioner_helper.c,  303, Scanning For Unprovisioned Devices
<t:    8224643>, provisioner_helper.c,  138, UUID : 3364D96B0848C44AAE7A480A52070680
<t:    8224646>, provisioner_helper.c,  142, ^RSSI: -53
<t:    8224648>, provisioner_helper.c,  147, ^URI Hash: BE915706
<t:    8224653>, provisioner_helper.c,  153, URI hash matched. Provisioning ...
<t:    8229347>, app_error_weak.c,  119, Mesh error 11 at 0x00027379 (D:\_nrf5_SDK_Meshv320\examples\light_switch\provisioner\src\provisioner_helper.c:111)