RE: Provisioning and Configuring light bulbs using nrf52832 without mobile app

tesc — Tue, 29 Sep 2020 12:08:15 GMT

Hi,

We use an URI included in the beacons of the SDK examples in order to simplify the provisioner example. We have not always done it this way, for instance the provisioner was part of the light switch example in nRF5 SDK for Mesh v3, and the provisioner and client was on the same device in nRF5 SDK for Mesh v1. The reason why we moved the provisioner to a separate node, is that in a real life scenario it is probably not a good idea to combine provisioner with clent or server.

It is possible to automatically configure the device on other criteria, yes, for instance by recognizing what models are present on the device and use that to decide how to configure it. For configuring the node you use the configuration client API, which is the API already used by the provisioner example.

For provisioning, all nodes in the network need to be provisioned by the same provisioner. (Actually, it can be multiple provisioners, but then the provisioners must exchange information about the network beforehand, such as network key, already provisioned nodes, app keys, etc. The protocols for such exchange is not specified by the Bluetooth mesh specification, so it will be implementation specific.) In other words, a node cannot provision itself into the network. The only exception would be if it is the first node of the network, and acts as provisioner for provisioning more devices into the network.

Regards,
Terje