Extend PB Remote functionalities

RE: Extend PB Remote functionalities

bjorn-spockeli — Tue, 26 Jun 2018 16:04:22 GMT

I've been discussing this some more with the mesh developers and they were curious as to why you would like to run multiple remote provisioning clients on a single mesh node as provisioning is performed once during the lifetime of the devices. They argued that running multiple remote provisioning clients will slow down the provisioning links as the traffic to the node is increased. With running only one remote provisioning client you shouldnt see the provisioning of each device taking more than ~1.5-2.0 seconds.

They argued that a better approach would be to have multiple provisioning devices if the speed of the provisioning process is a key performance criteriea, but again this is only done once.

That said, it should theoretically be possible to run multiple remote provisioning clients on one node. You should only need the handle of the newly provisoned devices, which is returned with the NRF_MESH_PROV_EVT_COMPLETE event, then use this to set the remote server for the respective rempte PB clients.

As to the question regarding if one can perform regular provisioning at the same time as remote provisioning, the answer was yes, this should be possible.

Since you're adding both the provisioning bearer and the remote provisioning bearer in provisioner_start() in the pb_remote_client project, i.e.

ERROR_CHECK(nrf_mesh_prov_bearer_add(&m_prov_ctx, nrf_mesh_prov_bearer_adv_interface_get(&m_prov_bearer_adv)));
ERROR_CHECK(nrf_mesh_prov_bearer_add(&m_prov_ctx, pb_remote_client_bearer_interface_get(&m_remote_client)));

then any packet received over the respective bearers should be treated accordingly, i.e. by their respective handlers prov_evt_handler and remote_client_event_cb. Which error are you getting?

RE: Extend PB Remote functionalities

Damien Berger — Mon, 25 Jun 2018 10:16:35 GMT

Yes i know that remote provisioning servers just relays packet to the provisioner, but is it possible to have several remote provisioning servers running concurrently ?

I am able to do remote provisioning on all my servers but only one at a time. I do not know how to make them running concurrently. If i keep using one remote client, it only can communicates with one server, and if i create one remote client for each server, i do not know how to specify the remote address of the client since the configuration of the remote server is done locally.

By the way, is there a way to run classic provisioning at the same time of remote provisioning ? I always get an error when a Remote UUID and a non-remote UUID are detected at the same time.

RE: Extend PB Remote functionalities

bjorn-spockeli — Mon, 25 Jun 2018 08:21:00 GMT

Hi Damien,

I apologize for the late reply.

I've been in contact with the Mesh team and according to them there are no restrictions to the number of remote, i.e. you can have as many remote provisioning servers as you want.However, they pointed out that the remote provisioning servers does not perform the actual provisioning, they just relay the PB-ADV packets back to the remote provisioning client (i.e. the provisioner in the mesh).

Could you post the log output from the provisioner node? Do you get the "Remote scanning started on node %u and model handle %04X\n at @%u" log output for all the 5 server nodes?

Best regards
Bjørn

RE: Extend PB Remote functionalities

Damien Berger — Mon, 25 Jun 2018 06:38:00 GMT

Could you contact the Mesh team ?

RE: Extend PB Remote functionalities

Damien Berger — Tue, 19 Jun 2018 06:17:47 GMT

Hi, do you have any news ?

RE: Extend PB Remote functionalities

bjorn-spockeli — Fri, 15 Jun 2018 14:02:25 GMT

HI Damien,

I am not sure if remote provisioning and regular provisioning are mutually exclusive or not OR if you can have multiple remote scanners active at the same time. I will contact the Mesh team and inquire if there are any limitations.

Best regards

Bjørn