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

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

lshaiou — Fri, 11 Jun 2021 08:39:24 GMT

OK。Thanks！~

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

jfpastrana — Fri, 11 Jun 2021 08:35:57 GMT

Hello @Ishaiou,

The provisioner example given in BLE Mesh examples has a Configuration client role. If you are starting with BLE Mesh I recommend reading the Nordic documentatation: Bluetooth mesh concepts

Here is also a good tutorial that it was a good starting point for me: The Ultimate Bluetooth Mesh Tutorial

Regards,

Javier

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

lshaiou — Fri, 11 Jun 2021 08:22:05 GMT

Hi jfpastrana,

I have the same use case as you.The CORE device could implement provisioner and configuration client roles .And I don‘t know how to do,because I am a newer on mesh .Have you finished the test?And could you be kind to give me some advice? Thanks.

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

jfpastrana — Tue, 01 Jun 2021 15:36:21 GMT

Hello Mttrinh,

Thanks for your answer and thanks again for reviewing the network architecture, it is true. It should be a server, not a client.

I will keep the CORE node as provisioner node.

Thanks for the example, I will test it.

Best regards,

Javier

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

Mttrinh — Fri, 28 May 2021 16:52:15 GMT

Hi,

Provisioner as a role is always a separate device as by spec you must use one of the specified provisioner bearers (ADV or GATT) in order to provision a device. However, by reading the spec, nothing prevents the node that implements Provisioner and Configuration Client to have other models (like it was with generic onoff client). But generally, yes, provisioner and configuration client is a smartphone or some other device that can add devices to a mesh network. Regarding the static provisioner, we see it as an example that can provision and configure all our samples, not just generic onoff client.

Regarding your case, if you won't have a smartphone or any other separate device, then the CORE device could implement provisioner and configuration client roles together with generic onoff client.

I have attached a patch that adds Generic OnOff Client from light switch client example to static provisioner example for nRF5 SDK for Mesh v5.0. Actually, the static provisioner can be any other device as well as CORE device. But since CORE device should subscribe to button status, it should have Generic OnOff Server instance, not the client one. Or use Device A as a provisioner. Then the rest devices could be Light Switch server examples. The important thing is that one and only one device must have provisioner and configuration client roles on it.

devzone.nordicsemi.com/.../6787.onoff_5F00_client_5F00_in_5F00_static_5F00_provisioner.diff

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

jfpastrana — Thu, 27 May 2021 07:25:02 GMT

Hello Mttrinh,

Any suggestions? Or I just remove the clients from provisioner node?

Regards,

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

jfpastrana — Sat, 22 May 2021 09:07:28 GMT

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

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

Mttrinh — Fri, 21 May 2021 16:16:57 GMT

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.

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

jfpastrana — Fri, 21 May 2021 12:48:06 GMT

Hello Mttrinh,

Could you give some idea? or tell me if it is not a good approach of the given network?

Basicaly, i took the static provisioner example and i included the clien initialization of genereic OnOff client. it means, put the initialization at the end of the models_init_cb() function. (As it is done in the Mesh1.0 example)

    for (uint32_t i = 0; i < CLIENT_MODEL_INSTANCE_COUNT; ++i)
    {
      /* TODO Configure the client locally, if we have more clients, do it in an array */
      m_client_on_off[i].settings.p_callbacks = &client_cbs;
      m_client_on_off[i].settings.timeout = 0;
      m_client_on_off[i].settings.force_segmented = APP_FORCE_SEGMENTATION;
      m_client_on_off[i].settings.transmic_size = APP_MIC_SIZE;
      __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Client\n");
      ERROR_CHECK(generic_onoff_client_init(&m_client_on_off[i], i + 1));
    }

However, when the program goes to the first generic_onoff_client_init() it breaks. i do not know why, maybe is the order initialization, not sure. I am comparing it with the Mesh 1.0 example but it is quiet difficult to follow, due to the changes between Mesh 1.0 and 5.0.

Could you give any clue?

You can find attached my main.c if it helps.

Best regards,

Javier

devzone.nordicsemi.com/.../6808182.main.c

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

jfpastrana — Thu, 20 May 2021 07:48:36 GMT

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

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

Mttrinh — Wed, 19 May 2021 16:00:31 GMT

Hi,

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