Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

[DavidAbreu99]

Hello,

I'm currently starting to develop with the Nordic nRF5340dk and trying to build a mesh network but i'm having some trouble on the examples to understand and buld my own. I see in the instructions that the UUID is generated by the board itself but i was wondering if there was some way to use a partial custom UUID to provision the devices.

UUID = n custom static bits + m auto generated bits.

This would function to differentiate the devices on the unprovisioned state like in 10 devices available only the ones that had the static bits is showed to the user to provision on the network.

I know this is possible on ESP32 but i can't seem to figure it out on Nordic, or if i can separate the devices on any way.

Any help is appreciated.

[Hung Bui]

Hi David, 
I assume you have looked in to the bt_mesh_dk_prov_init() in dk_prov.c. 

There is some requirement on the UUID:

 Where the 4 most significant bits of time_hi_and_version shall be
	 * 0b0010 and the 2 most significant bits of clk_seq_hi_res shall be
	 * 0b10. The remaining fields have no required values

So you are free to choose the value of the UUID except for the time_hi_and_version and clk_seq_hi_res 's bits. You are free to mix between static value and the auto generated bit or the hardware device ID

Note that after being provisioned the device will no longer advertise as unprovisioned beacon. 

[DavidAbreu99]

Thank you for the response, is there any example that i can use to see this procedure?

[Hung Bui]

Hi David,
I'm not sure what you mean. Have you looked into bt_mesh_dk_prov_init() ? You can modify the dev_uuid[] array to add your own static bits. Just avoid byte 6 and byte 8. 

[DavidAbreu99]

Hello, yes i have looked into bt_mesh_dk_prov_init() and i modified the dev_uuid[] however the uuid doesn't seem to change. Can you give me an example on how to do this?

Thank you.

[Hung Bui]

I did this: 

And I can see the UUID changed with 0xAAAA: