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?

[jfpastrana]

Hello Mttrinh,

I need to develop a network like the picture below, this is a simplified version, in the future will be more devices as DEVICE A. Every device is physically accessible by CORE device, I do not need a remote provisioner.

Therefore, if I understand well the roles in BLE Mesh, I will need:

CORE: Control role (Client / server). Also, with Proxy and ANT+ capabilities.

DEVICE A: Server role

DEVICE B: Control (Client / server)

If there is a better role approach, please tell me how I can do it.

Thank you in advanced,

Javier