Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

RE: Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

Hung Bui — Mon, 19 Jul 2021 15:41:27 GMT

I did this:

And I can see the UUID changed with 0xAAAA:

RE: Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

DavidAbreu99 — Mon, 19 Jul 2021 10:14:30 GMT

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.

RE: Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

Hung Bui — Mon, 19 Jul 2021 08:59:20 GMT

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.

RE: Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

DavidAbreu99 — Fri, 16 Jul 2021 15:13:22 GMT

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

RE: Differentiate devices on a BLE Mesh unprovisioned status - NRF5340DK

Hung Bui — Fri, 16 Jul 2021 14:55:03 GMT

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.