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

[Jui-Chou (Rick) Chung]

Hello Michael,

Great to hear that the Thingy mesh demo works well.

The reason why the nRF52-DK with "light switch server" cannot work with "Thingy bridge" correctly is that:

1. The "Thingy bridge" will do provision for the unprovisioned device and then do the configuration
2. During the configuration, Thingy bridge will try to bind the AppKey to the "simple Thingy server model" (the code is in here)
3. However, the "light switch server" is using the "simple on off server", which is different
4. So the configuration will fail

Basically, if you want your nRF52-DK works with "Thingy mesh demo", you have to add the "simple Thingy server model" into your project which running on nRF52-DK.

Also, since "Thingy mesh demo" is quite old (using nRF5 Mesh SDK v1.0.1), I would like to suggest you try the project "Thingy mesh provisioning demo"  which made by Hung :)

Best regards,

Rick

[Michael_K]

Thank you very much for your fast response, Rick!

I`m not sure what adding simple thingy server model in detail means. I added simple_thingy_server.c and ...server.h to the light_switch_project and additionally added the include directories for the preprocessor, which means building the project works fine now. 

Furthermore I have initialized the simple_thingy_server and bound it to an element. What else do I have to do to get my nRF52 DK provisioned?

[Jui-Chou (Rick) Chung]

Hello Michael,

If you have done the server initialization like here correctly, then your nRF52-DK should possible been provisioned and configured. Since "Thingy bridge" will provision the nearby unprovisioned device and configure it. You can add log in the provisioner.c in "Thingy bridge" to tracking the provisioning and configuration process.

Or you can modify the "Thingy bridge" project with removing all the "Thingy" hardware related code (like I2C I/O expander, LED driver and so on) for fitting the nRF52-DK.

Since your goal is trying to collect the sensor information from Thingys, and in the Thingy mesh demo, the "Thingy bridge" is not only a provisioner, but also all the sensor information will send to "simple Thingy client" in the "Thingy bridge".

[wangshuai]

Hello Michael,

I also encountered the same problem with you now. If you have time, you can send your configured demo to my reference learning? Thank you very much.

[Michael_K]

Hello 

Jui-Chou (Rick) Chung: Thank you for your advice. I`m still working on the initialization. Unfortunately the link you were referring to doesn`t work. Would you mind sending it again?

wangshuai I`m trying to add the initialization of the simple_thingy_server-model to nrf_mesh_node_config.c. Unfortunately I also have some exams coming up but I will post my results asap. 

[Jui-Chou (Rick) Chung]

Hello Michael,

Would you please check the link again? Since the link should work now

And please let me to add some comments:

In the "Thingy mesh demo" project, there are ten "simple Thingy client" in the "Thingy bridge"., and each one has been configured to publish the message to the corresponded "simple Thingy server" in those ten Thingy node. Once if one of the Thiny node got the "read sensor back" command, it will send the sensor information to the corresponded "simpleThingy client" in the "Thingy server", and the callback function will send the sensor data to through Nordic UART Service to the mobile device (this is the old design).
According to the upon information, it would be better to turn your DK as a Thingy bridge

But I would like to suggest you to use our latest Mesh SDK, and check here to create the model for your application. 

Hope the upon information can do help.