This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thingy52 provisioning OOB blinking public key

Hello.

I have question about output OOB and public key.

I create my Android app for Thingy Bluetooth mesh purposes. I would like to start output OOB process (then Thingy blinks couple of times).

Shoud I generate before this blinking process, a public key on my Provisioner and send this key to the device and after that Thingy will be blinking?

I have read  chapter 5 form Mesh Profile document, but still do not understand how it works.

Can someone help me please?

Parents
  • Hi,

    We have documented the Provisioning process and API in the nRF5 SDK for Mesh documentation on Infocenter. The message sequence chart shows the provisioning process for both nodes, while separate sections below describe the full provisioning sequence for provisioner and for provisionee. In particular, what you ask for is the provisionee Step 5: Authenticating the provisioning procedure.

    Private and public keys are generated on both devices, and provided when initializing a provisioning context structure with nrf_mesh_prov_init(). This is needed both for provisioner and for provisionee, and the keys are used (in each end) together with the OOB data, as part of the provisioning process. The details are then handled by our mesh stack when you use the provisioning API as described in the "Provisioning process and API" documentation mentioned in the above paragraph.

    Regards,
    Terje

Reply
  • Hi,

    We have documented the Provisioning process and API in the nRF5 SDK for Mesh documentation on Infocenter. The message sequence chart shows the provisioning process for both nodes, while separate sections below describe the full provisioning sequence for provisioner and for provisionee. In particular, what you ask for is the provisionee Step 5: Authenticating the provisioning procedure.

    Private and public keys are generated on both devices, and provided when initializing a provisioning context structure with nrf_mesh_prov_init(). This is needed both for provisioner and for provisionee, and the keys are used (in each end) together with the OOB data, as part of the provisioning process. The details are then handled by our mesh stack when you use the provisioning API as described in the "Provisioning process and API" documentation mentioned in the above paragraph.

    Regards,
    Terje

Children
No Data
Related