About the provisioning beacon

RE: About the provisioning beacon

MichaelNordicUser — Mon, 30 Oct 2017 23:23:45 GMT

Is it possible for every device to be a provisioning device?

RE: About the provisioning beacon

mark — Tue, 10 Oct 2017 10:35:09 GMT

I also has this question, when device program the firmware of pb_remote_server and it has been add to the mesh network. This device receive packet that it's data_type is "AD_TYPE_BEACON", beacon_type is "BEACON_TYPE_UNPROV", it will happen an event of "unprov_evt.type = NRF_MESH_EVT_UNPROVISIONED_RECEIVED", this event will be handled by "mesh_evt_handler", and I find that when "case NRF_MESH_EVT_UNPROVISIONED_RECEIVED:" it does nothing but break. I don't know how the unprovisioned device add in the mesh network through this device?!

RE: About the provisioning beacon

bjorn-spockeli — Wed, 20 Sep 2017 08:59:29 GMT

Happy to help! I would appreciate if you could mark the answer as correct/accepted by clicking the check mark in the grey circle to the left of the answer.

RE: About the provisioning beacon

markson — Wed, 20 Sep 2017 08:55:19 GMT

OK，thanks : )

RE: About the provisioning beacon

bjorn-spockeli — Wed, 20 Sep 2017 08:29:21 GMT

No, this is a proprietary feature added by Nordic, i.e. its not a part of the Bluetooth Mesh Specification v1.0.

RE: About the provisioning beacon

markson — Wed, 20 Sep 2017 08:01:22 GMT

Yes, this is so cool, but this (PB-Remote) is the standard protocol define by SIG?

RE: About the provisioning beacon

bjorn-spockeli — Tue, 19 Sep 2017 13:54:49 GMT

Yes, our Bluetooth Mesh implementation supports Remote provisioning, see the quote from the Mesh Provisioning section of the nRF5 SDK for Bluetooth Mesh documentation, found here.

Remote provisioning (PB-Remote) allows a provisioner to provision devices outside its radio range. This is done by using mesh nodes to relay provisioning messages to a node within range of the device that is to be provisioned.