This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Mesh Provisioner stuck at configuring node

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.

Parents Reply Children
No Data
Related