ncs provisioner question

[William.wei]

hi support team,

customer needs provisioner program to program device without app,

i find it in ncs: zephyr\samples\bluetooth\mesh_provisioner and i tested it,here is a question with this code:

this demo can only provision device with app key, as logs shows:

however, compared to nrf5 sdk, our provisoner demo in nrf5 sdk can provision device, also we can set up publication and subscribe, as below:

here is my questions:

1. do we have reference code or demo as same as in nrf5 sdk, so proisioner can set up the group for publish and subscribe?

2 .is it possible to use provisioner to update the light, in case models in light are changed?

here is my other questions:

1. after i copy net key and app key to mobile device, the mobile phone can connect to the device after the device is provisioned by provisioner, for example light demo in mesh folder, but it could not show up in our app, how to fix this if possible ?

2.how can export those provisioning data(from provisioner) to our mobile phone, so mobile phone can use it for backup?

[Roshan Rajaratnam]

HI looking at the video I see your problem, copying the network key and the application key is not enough here. You are correct that you can connect to the network but the app on your phone does not know the setup of your network.

Once a network is created and a node is provisioned, you may export these configuration using the mesh configuration database. This is a predefined JSON format. Following steps should allow you to back up your settings.

1. Setup Network
2. Go to Settings
3. Click on overflow icon on the top right hand corner and select export
4. Here you have the option to choose either a partial export or a full export. A partial export would allow you to select the items you want to export and a full export would allow you to export all the network data.
5. Import the json file on a phone,
6. create a new provisioner with a new address.

Note: The sequence numbers are not exported in the JSON file so every phone should have its own provisioner with its unique address assigned to it.

Following are the answers to your initial questions

1. do we have reference code or demo as same as in nrf5 sdk, so proisioner can set up the group for publish and subscribe?

If you are referring to implement this on the app side, You can check out our source code on Github

https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library

Also our latest mesh library written in Kotlin github.com/.../Kotlin-Mesh-Library

2. is it possible to use provisioner to update the light, in case models in light are changed?

If you are referring to doing a DFU, yes this is supported on our iOS Mesh Library and this feature will be added to our Kotlin mesh library in the future.

[William.wei]

Thanks Roshan,

for this, i think it is clear.

Roshan Rajaratnam said:

HI looking at the video I see your problem, copying the network key and the application key is not enough here. You are correct that you can connect to the network but the app on your phone does not know the setup of your networ

for this i mean, the code in 54l15 here in ncs: zephyr\samples\bluetooth\mesh_provisioner.

Roshan Rajaratnam said:

1. do we have reference code or demo as same as in nrf5 sdk, so proisioner can set up the group for publish and subscribe?

i wish we can provide provisionerI（54l15） demo can set up the group for publish and subscribe after provision those device，as we did in nrf5 sdk: nrf5_SDK_for_Mesh_v4.2.0_src\examples\provisioner.

Regards,

William.

[tesc]

Hi,

I see that most of your questions seems to be for provisioner on the nRF, and not on smartphone.

Please note that the provisioner in nRF Connect SDK is in the Zephyr part of the SDK, and has limited functionality. There may be differences between the Bluetooth Mesh samples in the Zephyr part of the SDK and the ones in the nrf part. For Bluetooth Mesh we recommend following the style of the nrf samples, not the Zephyr samples.

1. do we have reference code or demo as same as in nrf5 sdk, so proisioner can set up the group for publish and subscribe?

The provisioner example in nRF5 SDK had functionality for setting up nodes from basically all of the other Bluetooth Mesh examples. The (Zephyr) provisioner sample of nRF Connect SDK does not come with this functionality out-of-the-box, and so must be implemented using the available APIs. We don't currently have reference code or demo for this, no.

2 .is it possible to use provisioner to update the light, in case models in light are changed?

Please elaborate on what you mean here. Unless there are recent additions to the spec, such changes to the node would require a re-provision, no?

2.how can export those provisioning data(from provisioner) to our mobile phone, so mobile phone can use it for backup?

The required information is stored in the configuration database (CDB). While there is an API for the CDB for getting information out of it, there is no single export functionality for dumping the whole CDB.

Regards,
Terje

[William.wei]

thanks tesc,

tesc said:

see that most of your questions seems to be for provisioner on the nRF, and not on smartphone.

yes, my question focus on privisioner on the ncs, and not on smartphone.

which means, the only way for customer to provision the device is using nrf mesh app, right?

Regards,

William.

[tesc]

Hi,

William.wei said:

which means, the only way for customer to provision the device is using nrf mesh app, right?

For doing both provisioning and configuration, that will not work out-of-the-box with the provisioner sample in the nRF Connect SDK, that is correct. For that they would have to modify the sample, adding the required functionality for model configuration. Or they can use the smartphone app nRF Connect for Android/iOS.

Regards, Terje