RE: Comsumption of the SIG mesh LPN; Change a new Provisioner.

jhc — Fri, 10 Jul 2020 08:34:32 GMT

Great, thank you!

RE: Comsumption of the SIG mesh LPN; Change a new Provisioner.

tesc — Wed, 08 Jul 2020 12:35:31 GMT

Hi,

[quote user=""]2. does the provisioner need to keep some parameters of its mesh network, like the unicasting address of the elements?[/quote]

Provisioner basically needs to store everything about addresses and keys for the network, in order to be able to configure the other nodes and for provisioning new nodes into the network.

[quote user=""]3. if the provisioner is lost or damaged, how to replace it with a new one?[/quote]

If you have backup of the provisioning database, it is doable to just use a new provisioner, load the database into that one, and use that one. If you do not have backup of the provisioning database (with current state of the mesh network), you basically need to set up a new network using a new provisioner.

[quote user=""]4. is it possible to have multiple provisioners in a mesh network?[/quote]

Yes, this is possible according to the Bluetooth mesh specification, although there is not any specified way to share the provisioning data between the multiple provisioners. (The specification only states that such data sharing must happen.)

[quote user=""]5. Is it possible to upgrade BLE node to a mesh node via OTA?[/quote]

That should be possible, yes, although if you want to upgrade into a mesh node which has DFU capability, you may need some modifications to the DFU process (I do not have full overview of what would be required for that.) If you experience any issues with such upgrades, please create a new ticket for that specific use case.

Regards,
Terje