Provisioner and client (provisionee) roles in the same application Mesh 5.0

[jfpastrana]

Provisioner and client (provisionee) roles in the same application.

 

Hello everyone,

First, I am using SDK 17.02 and BLE Mesh 5.0.

By the moment, I want to integrate a static provisioner and a generic OnOff client in the same application. I have this post in which is provided an Example using Mesh 1.0. I use this example as a reference.

Also I have followed this tutorial about how to migrate Mesh examples into SDK examples. I did it with the static provisioner example.

Now I want to include a generic On Off client in the same project (In the future I will have more) but I do not know which the order is to initialize each component. Also, I do not know if I am doing it well.

 In the provisioner example is given this order:

1. ble_stack_init();
2. mesh_init();
   • models_init
     • config_client_init()
     • health_client_init()
   • mesh_stack_init()
     • config_server_init()
     • health_server_init()
     • mesh_config_load()
     • dsm_load_config_apply()
     • access_load_config_apply()
     • mesh_stack_is_device_provisioned()
   • prov_helper_init
   • node_setup_cb_set
3. node_setup_uri_check();
4. mesh_stack_start());

I image that I should include the initial configuration of genericOnOff inside of point 2.1 and then make the fix configuration for self-provisioning below 2.2.3 point. But It does not work… Which is the best way to include more clients?

Moreover, giving the static provisioning example it makes me more questions. Is it necessary to include a config and health clients? On client examples I only see config and health servers.

Best regards,

Javier

[Mttrinh]

Hi,

Is there a reason for you to have both in the same application? Could you tell me more about your use-case?

[Mttrinh]

Hi,

I still don't quite understand why you need the provisioner and provisionee to be on the same node.Your core don't need to be a provisioner, or am I wrong here? Could you elaborate? In almost all cases you want your provisioner to be a seperate device, often a smartphone or other device connected to the outside world for backup of the provisioning database.

[jfpastrana]

Hello,

Ok, I am going to explain you my use of case with an example, for a better understanding.

Imagine that you have a virtual assistant like Alexa, which is the core of the network. Then you have other nodes, like a smart blind, smart lights, speakers, … basically devices which need to send its status and have actuators.

Now the keys of my use of case:

• The virtual assistant will be always at the same home.
• You do not want to force to the user to use its smartphone for configuring/pairing.
• You want to add new devices automatically, when the virtual assistant detects a new node, they will be paired automatically.
• I insist again, you want a self-managed network, you cannot force the user for configuring the network.

If it Is not the nature of the provisioner, I do not understand why Nordic has published an example like this.

I hope it would be explained better.

Best regards,

Javier