Adding nRF52 DK to gitHub mesh demo for thingys

[Michael_K]

Hello everyone, 

I`ve 4 thingys and ran the https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo. That works well. 

Now I`m trying to add the nRF52 DK as a Node to the bluetooth mesh network in order for it to receive the periodic messages sent by the sensor nodes. 

As a first step, I was trying to program the light_switch_example_server_nrf52832_xxAA_s132_3_1_0 from the nRF5 SDK for Mesh v1.0.1 onto the Chip (using SEGGER Embedded Studio) to see whether it is being provisioned by the bridge. Unfortunately it is not. 

My question is: Why doesn`t the nRF5 DK get provisioned by the bridge? And what do I have to change to add it to the mesh and to receive the messages of the thingys? 

Best regards, 

Michael

[Michael_K]

I`m using the light_switch_server-project from the examples of the mesh sdk v1.0.1. 

While configuring the mesh node using nrf_mesh_node_config() the provisionee-model is initialized using setup_provisionee(). In this process, public and private keys for the provisioning cryptography are generated, the provisionee is initialized with a so called provisioning context, which contains important information for setting up the provisionee. One of these characteristics is the bearer type, which I believe has to be similar to the one of the bridge. And right now it apparently is not, which might be the reason why the bridge doesn`t recognize the dk. 

Regards Michael

[Jui-Chou (Rick) Chung]

Hello Michael,

Since you are using the example based on the mesh SDK 1.0.1. I would like to suggest you check this thread. In the example workspace in mesh SDK v1.0.1, the default bearer access address is not the one defined in the specification, And that may be the reason why the bridge cannot scan the beacon from your unprovisioned server device. 

Hope this can do help :)

[Michael_K]

That was it! 

Thank you, Rick. It works now. 

Now the DK gets provisioned by the Bridge