Could you please advice me with mesh network ?

Hi,

Can you give more informations about the trouble concerning the provisioner node ?

What is your project ?

How many STM32wb boards are in your mesh network ?

What are the MESH configuration of each Node to provision ?

Best regards.

Hi,

Embedded provisioning idea is to use a nucleo board as provisioner instead of a smartphone or other mobile computing device.

The board used as provisioner does not need to be provisioned as it creates itself the network parameters.

The board will then be able to scan all unprovisioned devices around and provision them.

First you have to open the project in an appropriate IDE and check the features enabled in mesh_cfg_usr.h:

Manually configured provisioner

Refer to the sample code below:

#define EANBLE_RELAY_FEATURE

#define EANBLE_PROXY_FEATURE

#define EANBLE_FRIEND_FEATURE

//#define EANBLE_PROVISIONER_FEATURE

#define DYNAMIC_PROVISIONER

If the DYNAMIC_PROVISIONER is selected, the provisioner configuration will have to be done manually following

the steps below:

• Build and flash the project into your provisioner board
• The following welcome message is displayed on the board serial terminal :

Next NVM Address 080c7000

Unprovisioned device

[…]

BLE-Mesh Lighting Demo v1.12.008

BLE-Mesh Library v01.12.008

BLE Stack v1.6.0 Branch=0 Type=3

FUS v1.0.2

BD_MAC Address = [c0]:[e1]:[26]:[07]:[f3]:[90]

UUID Address = [f8] [1d] [4f] [ae] [7d] [ec] [4b] [53] [a1] [54] [90] [f3] [07] [26] [e1] [c0]

• Write the following instruction in the serial terminal to define one node as the ROOT node for networkcreation:

ATEP ROOT (case insensitive).

This performs the model binding and configuration.

• Write the following instruction in serial terminal to scan unprovisioned devices in range:

ATEP SCAN (case insensitive).

The log on terminal will indicate unprovisioned devices with their corresponding UUIDs:

Device-0 -> F81D4FAE7DEC4B53A15490F30726E1C0

Device-1 -> F81D4FAE7DEC4B53A1542B350826E1C0

Test command executed successfully

Here two devices (device-0 and device-1) are unprovisioned in the network

• Write the following instruction to start provisioning of device-0:

ATEP PRVN-0 (case insensitive)

The log will appear on terminal indicating the device-0 has been provisioned by the provisioner by making

the PB-ADV connection link:

Test command executed successfully

PB-ADV Link opened successfully

Device Key: 46 82 e9 3e 20 […]

App Key: e6 bd d2 95 2d 81 85 7c a4 2e […]

Device is provisioned by provisioner

The log in the provisioned node terminal indicates that the node is provisioned by the provisioner.

• Finally the PB-ADV connection link is closed and device-0 is configured and models bound.

Best regards.

Hi @EMECH​ ;

Thank you for your advice. I have done on provisioner. I would like to know more if I set below.

#define EANBLE_RELAY_FEATURE
#define EANBLE_PROXY_FEATURE
#define EANBLE_FRIEND_FEATURE
#define EANBLE_PROVISIONER_FEATURE
//#define DYNAMIC_PROVISIONER

My devices will sync mesh network(FN, RN, PRN), right? . How do I send parameter temperature and humdity to FN-->RN-->PRN? Could you please advice me?

Best regards.

Hi,

The Provisioner is autmotically self provisioned and configured at the initialisation (no ATEP ROOT command).

Dynamic Provisioner after initialisation is seen as unprovisioned device that can be provision by a smartphone, a provisioner or byself.

As you can seen in the mesh_cfg_usr.h file of each project (Low Power Node, Proxy Relay Friend Node or Provisioner Node) the Node contains the following Models and elements enabled :

• #define ENABLE_GENERIC_MODEL_SERVER_ONOFF                  (1)

Means that the first element of the Node is set with Generic OnOff Server model.

• #define ENABLE_LIGHT_MODEL_SERVER_LIGHTNESS                 (1)

Means that the first element of the Node is set with Light Lightness Server model.

• #define APPLICATION_NUMBER_OF_ELEMENTS                     1

Means that the Node have only one element

• #define USER_SIG_MODELS_MAX_COUNT                       4

Means that the Node can have up to 4 Bluetooth SIG models per element

• #define USER_VENDOR_MODELS_MAX_COUNT                      1

Means that the Node can have up to 1 Vendor model per element

In the case of your application you only need Sensor models.

Depending of the use case, it could be a Sensor Model with 2 sensors or 2 Sensor Models with one sensor embedded in 1 or 2 Nodes.

For a Node with a Sensor Model you have to uncomment the mesh_cf_usr.h following lines:

• //#define ENABLE_SENSOR_MODEL_SERVER                      (1)
• //#define NUMBER_OF_SENSOR                            1

And modify if necessary the number of sensor.

Configuration of your sensor is defined in the file sensor_cfg_usr.h.

Please have a look to the Bluetooth SIG Mesh Model specification version 1.0.1 for more details on the sensor model.

Actually we are under implementation of a project demo involving sensor model and other models.

We will go back to you when this demo will be finalized.

Best regards.

Hi @EMECH​ ;

Thank you for your advice. How do I config provisioner on the same network ? ( I don't would like to use mobile to adjust provisioner. In use case with endnode more than 500 devices )

Best regards.

Since the ST provisioner is using PB-ADV the provisioner needs to be in radio range of the all the 500 nodes that are being provisioned, or you need to walk around provisioning the end nodes with the provisioner board. The provisioner is like a god node, the god node has all the encryption keys (per device key, application key and network key), the addresses that were assigned to the end node etc.

After you provision the network you will need to set up the publishers and subscribers for the 500 end nodes, this is called the configuration stage.

The mobile app will usually help you do both the provisioning and configuring. Typically you either go for the provisioner running on an embedded board or a mobile app.

It is possible for the provisioner board to also do configuration but that is likely to be sub optimal for an actual production situation. You can can do the configuration if publisher role and subscriber roles are well defined , but it is a bit of work.

Additionally if you want to reconfigure the mesh network and the provisioner board was accidentally destroyed or lost, you lose the keys to the entire network, this means you will need to backup the provisioning info and the configuration info to be able to re-create the provisioner node again.

It is indeed possible to do the able, but just be prepared for a lot of additional code for the embedded provisioner.

Hi @DEdwi.1​ ;

Thank you for your advice. I get it now.

Best regards.

If you really don't want the phone to do the provisioning, the only real solution would be to wait for the ST implementation of remote provisioning, this will enable you to provision the entire 500 nodes from a single stationary provisioner.

As @EMECH​ says, the spec is not ready but early implementations are already available and you should press your ST contact for this release. This stationary provisioner can be the gateway node for the mesh, I would however prepare for this eventual remote provisioning solution by provsioning the nodes by phone and work on managing the JSON file describing the mesh network so you are ready when ST releases the remote provisioning solution.

Hi,

As you know ST Microelectronics is an Associate member of the Bluetooth SIG, all our Bluetooth products must be qualified by the Bluetooth SIG and then we cannot give any "early implementations" before any Bluetooth SIG specification release and Bluetooth SIG qualification.

Best regards.

As @EMECH (ST Employee)​ says, this is correct.

The remote provisioning specification should first be agreed at the SIG and then an IOP (IOPs more likely) done to verify that this works according to specification, then the specification is released. Typically most BT associate companies will try to release their implementation(typically with enough tests to provide evidence of qualification) at the time of the specification release.

Companies that are already associate or have good relationships can negotiate for early releases typically under NDA, however for most of the customer base we have to wait for a public release, so we have to wait.