Hi,
I am developing a feature to add remote provisioning support to a BLE Mesh-based network. In the network, a provisioner node receives, via a serial command, the UUID of the node to be provisioned into the network. Then the provisioner iterates over the nodes in its Configuration Database and requests them to start a remote provisioning scan (bt_mesh_rpr_scan_start). After receiving scan reports from remote provisioner servers that have seen the node to be added, the provisioner calls bt_mesh_provision_remote on the last node that reported seeing the node.
This process works fine most of the time, but sometimes bt_mesh_provision_remote is called; it returns no error, but the node_added callback on the provisioner is never triggered. Thus, I cannot proceed with configuring the node. The solution for this is to retry the procedure.
Aside from this, I occasionally get the following warnings
bt_mesh_transport: No free slots for new incoming segmented messages
bt_mesh_adv: AD malformed
Do you have any insights into why bt_mesh_provision_remote may return no error code, but the node_added callback is occasionally not triggered, as if the node was never remotely provisioned? What may cause the warnings shown above?
The following are the KConfigs related to segmented messages and ADV on the provisioner:
Current SDK Version: v2.8.0
Any help would be greatly appreciated
