BLE Mesh Custom Model Appkey Index not updating during self-provisioning process, always equals 0xFFFF

RE: BLE Mesh Custom Model Appkey Index not updating during self-provisioning process, always equals 0xFFFF

Hieu — Thu, 27 Mar 2025 13:46:07 GMT

Hi Cam,

The status of whether an app key is added, and which models it is bound to is stored in NVM. During initialization, you can simply check the status and then proceed depends on what the current state is.

It has been a long time, and I don't know if I had tried this then, but instead of a reset to split apart the sequence, you can also try adding a delay.

RE: BLE Mesh Custom Model Appkey Index not updating during self-provisioning process, always equals 0xFFFF

Cam Martell — Wed, 26 Mar 2025 12:09:21 GMT

Hi Hieu,

Thank you for your reply. Are you referring to these steps you outlined:

On initialization when the device is not yet provision, add the app key to the node. The model features won't work yet in this boot.
On initialization where the device has been provisioned, run the key binding. From this point on, the features should work normally.
Thus, to get things run, after flashing the device and let it run for the first time, simply reset it and things should then work.

If so, I am a bit unsure what this would look like in the source code. Are you suggesting that I try adding the app key first on boot, then provisioning the device second, followed by binding the app key? Or is there some other order of operations. I don't understand how the multiple boot ups would work in this case.

Would I need to add some conditional to check if the app key has already been added? If it hasn't, add the app key and reboot, if it has, provision and do the key binding? Or is this different than your crude workaround?

RE: BLE Mesh Custom Model Appkey Index not updating during self-provisioning process, always equals 0xFFFF

Hieu — Tue, 25 Mar 2025 22:11:52 GMT

Hello Cam,

I found some issues about the order the operations in a similar setup in my last reply in this DevZone case:

Bluetooth: Mesh Demo example automatic provisioning

Could you enable more logging and see if that is what is happening here?

In that same DevZone case, I also wrote about why the self-provisioning setup is recommended against for production.

Hieu