The server can be provisioner?

RE: The server can be provisioner?

rcosta — Wed, 10 Jan 2018 12:47:44 GMT

Dear Hung Bui Thank you very much for the help. Before my post I was already studying the Mesh SDK´s getting started guide. I will study the suggested resources, If a have any question i will create a devzone case. Thank you very much.

Best Regards, Rafael Costa

RE: The server can be provisioner?

Hung Bui — Tue, 09 Jan 2018 12:28:07 GMT

The resource that I would suggest you to have a look are:

Bluetooth Mesh spec (Mesh Profile) www.bluetooth.com/.../mesh-specifications
Mesh SDK's getting started guide (starts with the provisioning part) infocenter.nordicsemi.com/.../md_doc_getting_started_getting_started.html
Lightswitch example source code.

RE: The server can be provisioner?

rcosta — Mon, 08 Jan 2018 17:06:46 GMT

Dear Hung Bei,

I am starting on Bluetooth for mesh. The final goal is to create a mesh network, composed by one gateway and many nodes, the gateway should be the provisioner.

To be able to create my application first i need to learn some basic concepts and study the SDK. I am studying the light switch example included on the nrf52 SDK for mesh, i already executed this example. On the example i not understand some functions calls and data structures. After some time analyzing the example, i conclude that there is a lot of things that are necessary to do before two nodes can communicate. Please can you tell the best approach for somebody that is starting on Bluetooth for mesh? Please can you provide me some resources?

Any help will be very appreciated.

Best regards, Rafael Costa

RE: The server can be provisioner?

Hung Bui — Fri, 05 Jan 2018 14:32:40 GMT

Are you sure you want to use Mesh to create a star network ?

In the SDK light switch example, we have one device acts as client(s) and several servers, it is just an example. Actually there are several elements on the client, each element control one server.

You don't need to follow that, you can use one single client to control different server or you don't really need to use server - client model at all, if it's better for your application. To send a packet from one device to another device, you just need to match publication address with the subscription address or the unicast address of the other device.

The provisioner can be on any device, doesn't need to be client. But for now we don't support multiple provisioners.