Ble Mesh : being a provisioner and say light switch server

RE: Ble Mesh : being a provisioner and say light switch server

Hung Bui — Thu, 26 Oct 2017 14:00:30 GMT

No, I don't have any date for that. I guess you would need to talk to our Sales.

RE: Ble Mesh : being a provisioner and say light switch server

Mahendra Tailor — Wed, 25 Oct 2017 10:45:23 GMT

Thank you for confirming what I suspected would be the case. The Nordic Mesh is evolving and I appreciate Nordic allowing us early access to the SDKs. Is there a timeline for releases. For example, for a production ready Mesh SDK, which quarter should I be planning for?

Although just like Nordic, we at Laird plan to do something similar and release engineering firmware releases that mirror the functionality in your SDK, but exposed in an easy to use interpreted programming language.

RE: Ble Mesh : being a provisioner and say light switch server

Hung Bui — Wed, 25 Oct 2017 10:38:28 GMT

Hi Mahendra,

If you are going to use the server on the provisioner, I don't see any problem adding an extra element and a server model on it. As you might already see, we configure the clients manually inside access_init(). Subscription/publication address and application key is binded to the clients model manually in the function.

You can do the same to the server.

But if you want to add another element on the server, you may have a trouble because the provisioner on the light switch example doesn't support provisioning multiple element on one device. Have a look here.

You will have to think of creating a generic provisioner that can do more flexible provisioning and can can be dynamically customized by the end user.