There is a secure process to remove a node from a mesh network, where necessary key refreshments and database changes has to be done.
If anyone intentionally do factory reset to one of the node in the network then provisioner will not be knowing about it at the time of reset. But during the next key refresh procedure, provisioner will know about the unreachable(reset node) node when it does not receive new keys. And this node will be blacklisted by config client and will be notified about it to the user.
You can use below APIs to configure heartbeat publication and subscription.
1 of 1 people found this helpful
You can get the description of these APIs from wiced_bt_mesh_provision.h. Please go through it.
Also you can refer mesh_provision_client app where these APIs have been used to GET/SET the heartbeat messages.
When mesh core receives the heartbeat messages, it will set the parameters accordingly and give responses. Please check the clientcontrol logs for the sent and received messages.