Behavior of the Bluetooth Mesh network provisioner/configurator

RE: Behavior of the Bluetooth Mesh network provisioner/configurator

Edvin — Tue, 15 May 2018 06:14:36 GMT

Hello,

Sorry, you are correct. Provisioning is happening before configuration. The keys are exchanged during provisioning, which are then used in configuration.

BR,

Edvin

RE: Behavior of the Bluetooth Mesh network provisioner/configurator

gsegment — Mon, 14 May 2018 14:16:36 GMT

Thanks for response,

For the last answer, do you mean after the provisioning (not before)? Because I thought that configuration can be done only when provisoning process is complete.

RE: Behavior of the Bluetooth Mesh network provisioner/configurator

Edvin — Mon, 14 May 2018 13:51:26 GMT

Hello,

1. Yes. You are correct. You the network can be operative after the nodes are provisioned, even if the provisioner is no longer turned on.

2. This is not done automatically in the Mesh network, but you can use e.g. the Health server (found here). In the Light switch example the servers are sending their health status as an I'm-Alive message.

3. This is not Mesh specific. In SDK for mesh v2, there are some json files that is storing the data. The mesh specification says that you can have several provisioners, but it is up to the application how to share the information between them.

4. The configuration happens before the provisioning, so actually, yes. The node that configured the network can be a provisioner.

Best regards,

Edvin