Bluetooth Mesh SDK 1.1.0 - evt_mesh_prov_config_status - Status code documentation
01/04/2018 | 04:23 PM
Occasionally I see status codes of 254 when receiving an `evt_mesh_prov_config_status` event on a node trying to provision another node. Where can I find documentation for these status codes? It's not clear to me where this lines up with any docs from the Bluetooth SIG.
Blue Gecko Bluetooth Low Energy SoCs
Bluetooth Low Energy
Discussion Forums
Answered
Answered
To follow-up, the summary of status codes in section 4.3.5 of the Mesh Profile specification v1.0 lists 0xFE (254) as reserved for future use. Any idea what may be causing this to come out of a provisioning node? It specifically happens during vendor model binding. I also haven't found a way to reliably reproduce this issue.
0
Value 0xFE is used to indicate "timeout". It's not part of the Mesh specification but an additional status code used by our mesh stack.
If you get a `evt_mesh_prov_config_status` event with status 0xFE you should simply send the last command again (e.g. call cmd_mesh_prov_model_app_bind() again)
Bluetooth Mesh SDK 1.1.0 - evt_mesh_prov_config_status - Status code documentation
Occasionally I see status codes of 254 when receiving an `evt_mesh_prov_config_status` event on a node trying to provision another node. Where can I find documentation for these status codes? It's not clear to me where this lines up with any docs from the Bluetooth SIG.
Value 0xFE is used to indicate "timeout". It's not part of the Mesh specification but an additional status code used by our mesh stack.
If you get a `evt_mesh_prov_config_status` event with status 0xFE you should simply send the last command again (e.g. call cmd_mesh_prov_model_app_bind() again)