nRF Mesh example with provisioner board

[Flips]

Hey, I want to create a Bluetooth Mesh Network with the nRF52DK from Nordic. One board should be the provisioner and two more boards should be my nodes.

For my first test, I used the Zephyr examples "Mesh Provisioner" and "Mesh" on the nRF Connect 2.4.1 SDK and the 2.4.0 Connect Toolchain.

So I have flashed the "Mesh Provisioner" on one board and the "Mesh" example on two more boards.

I can add both nodes with the provisioner, and it seems that this part works too. (because when I added one node, I can't see his advertising anymore)

But when I click on the Botton1 of one of the Nodes, there should be a broadcast call and turn on the other LED, but I always get the Message "The Generic OnOff Client must be bound to a key before sending."

Normally, should the provisioner give the node this Key, so I'm not sure what I'm doing wrong.

This is the output of the Provisioner:

*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Device 544d4f0f3c300a690000000000000000 detected, press button 1 to provision.
Provisioning 544d4f0f3c300a690000000000000000
Waiting for node to be added...
Added node 0x0002
Configuring node 0x0002...
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Device 544d4f0f3c300a690000000000000000 detected, press button 1 to provision.
Provisioning 544d4f0f3c300a690000000000000000
Waiting for node to be added...
Added node 0x0002
Configuring node 0x0002...
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Waiting for unprovisioned beacon...

[Edvin]

Hello,

From your logs, are you resetting the provisioner device on purpose? Do you press the reset button? Or does it reset automatically?

I have never tried out Zephyr's mesh samples. Only the ones found in NCS\nrf\samples\bluetooth\mesh. As a provisioner you can test the nRF Mesh application for iOS/Android. I suggest you test this either way, so that you know that the peripherals work correctly. 

Alternatively, you can use only the samples from NCS\nrf\samples\bluetooth\mesh. You can start off with the light and light switch examples, and see if you can get that up and running as described in the documentation of these samples. It also describes how to use the nRF Mesh app as the provisioner.

Best regards,

Edvin

[Flips]

Thank you, for your prompt response.

Edvin said:

Do you press the reset button?

No, it resets automatically. This was also my first thought, whether this is the error.

I already tested the light and light switch example with the Android App as provisioner, it works both fine.

But I wanted to test now an nRF chip as provisioner. The documentation of the mesh_provisioner said it would work with the "mesh" example.

Best regards,

Philipp