ESP BLE MESH node self provisioning (IDFGH-11861)

[Murtaza7745]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Hello,
I am developing firmware using the esp32 wroom-32e n16 module, its goal is to have a BLE MESH network, with multiple nodes (approx: 50) and a mobile app working as the client node in the mesh network for transmitting and receiving data.

I am stuck in a scenario where I don't have the liberty to provision even a single device from the app, considering the esp32 has static unicast addr, unique uuid, netkey and appkey. I want the unprovisioned esp32 to set its status to get self-provisioned, and I will upload the same data to the mobile app to communicate with the device.

How do I do that, I am very much in need of some assistance here.

[ankit-thealchemist]

@Murtaza7745 I think better way to do is to have each device provisioned in the factory by using the same appkey and net key. Just use the same net key and appkey the app like nrf mesh to communicate with the device.
App key you can decide any.
For net key use the function esp_ble_mesh_provisioner_get_local_net_key(uint16_t net_idx);. wheree net_idx = 0, ie esp primay index.

Now you have both appkey and net key. Now go to the nrf mesh and click settings. Provide the net key and appkey. This should solve the problem