Mesh Provisioning Lifecycle Considerations

RE: Mesh Provisioning Lifecycle Considerations

Justin Reina — Tue, 15 Sep 2020 18:03:11 GMT

let us know of the "A"/"B" question, when available

RE: Mesh Provisioning Lifecycle Considerations

Justin Reina — Sat, 12 Sep 2020 16:12:15 GMT

If the elements change, will the device still remain on the network? If the device has elements "A" & "B" with an update to "A", will "B" still work before reprovisioning?

RE: Mesh Provisioning Lifecycle Considerations

Justin Reina — Sat, 12 Sep 2020 16:02:51 GMT

Interesting, thank you! We are addressing mesh integration for a distributed utilities service in remote locations, your 48 weeks notice is appreciated

RE: Mesh Provisioning Lifecycle Considerations

Mttrinh — Thu, 10 Sep 2020 10:43:04 GMT

Hi,

A Bluetooth Mesh device should, in theory, only need to be provisioned once. There are some cases you need to reprovision the device(from the spec):

- If the number and structure of elements changes, for example due to a firmware update, the node must be reprovisioned.

- A node that is away from a network for longer than 48 weeks must be reprovisioned.