mesh provisioner problem

RE: mesh provisioner problem

tesc — Wed, 22 May 2024 12:38:43 GMT

Hi,

In our experience, if the configuration manager (device with configuration client) is connected directly to the node being configured, then the configuration will be very fast.

A potential pitfall to the above solution, is if the configuration manager is connected to a GATT Proxy node different from the node being configured. In that case, packets are bridged over to the ADV bearer to reach the destination, and there is no speedup compared to configuring over ADV directly. If anything there might even be an added delay, since the traffic will always have to go over GATT in one end.

Regards,
Terje

RE: mesh provisioner problem

zero — Wed, 15 May 2024 10:07:22 GMT

Hi Terje，

Can the time be shortened by using PB_GATT to configure the network?

RE: mesh provisioner problem

tesc — Thu, 18 Apr 2024 13:37:12 GMT

Hi,

[quote user="zero"]What are asynchronous APIs? How to do?[/quote]

Most of the Configuration Client APIs can be run asynchronously by setting some of their parameters to NULL This is described in the documentation for each function, e.g. "This method can be used asynchronously by setting status as NULL."

Regards,
Terje

RE: mesh provisioner problem

zero — Fri, 12 Apr 2024 01:22:39 GMT

Hi Terje,

[quote userid="8164" url="~/f/nordic-q-a/110059/mesh-provisioner-problem/478295"]The provisioning phase must be sequential according to the Bluetooth Mesh specification, and therefore cannot be parallelized. However you can speed it up somewhat by enabling the kconfig option CONFIG_BT_MESH_PB_ADV_USE_RELAY_SETS.[/quote]

Okay, let me test if it works.

[quote userid="8164" url="~/f/nordic-q-a/110059/mesh-provisioner-problem/478295"]It should be possible to parallelize the configuration phase, using asynchronous APIs.[/quote]

What are asynchronous APIs? How to do?

BR,

Zero

RE: mesh provisioner problem

tesc — Thu, 11 Apr 2024 11:48:23 GMT

Hi,

The provisioning phase must be sequential according to the Bluetooth Mesh specification, and therefore cannot be parallelized. However you can speed it up somewhat by enabling the kconfig option CONFIG_BT_MESH_PB_ADV_USE_RELAY_SETS.

It should be possible to parallelize the configuration phase, using asynchronous APIs.

Regards,
Terje

RE: mesh provisioner problem

zero — Thu, 11 Apr 2024 01:32:57 GMT

Hi Terje,

If multiple devices cannot be provisioned at the same time, can the provisioning time be shortened? Because my test provisioning a device takes 8 seconds.

BR,

Zero

RE: mesh provisioner problem

tesc — Wed, 10 Apr 2024 15:42:17 GMT

Hi,

The provisioner in nRF Connect SDK provisions and configures one device at a time. If there are five unprovisioned devices within range of the provisioner, it can provision all five, not concurrently, but one after the other. For more on the provisioning process, see the Provisioning section of the Bluetooth Mesh stack documentation.

Please note that the configuration is not strictly part of provisioning, but the provisioner typically does some initial configuration right after provisioning. This is also true for the provisioning sample.

You can add new app keys to the configuration database (CDB) through use of cdb_app_key_set().

Regards,
Terje