Hardware ability report after provisioning in Mesh demo

[WHui]

Hello Nordic Tech Support,

I am currently testing Thingy Mesh Demo v0.1. It is a great demo as I could manage the group of nodes or configure the sensor data using macros of communication protocols. Thingy Bridge serves as the bridge which communicate in both BLE (to Android phone) and Mesh (to Thingy Nodes).

I wish to have that every new Thingy Node report to Thingy Bridge which hardware ability it is equipped once after it is provisioned, e.g. "I have humidity and acceleration sensors". I have found that "Thingy drivers" folder contains the driver API for all the sensors driver API that a Thingy Node needs to operate and send sensors data.

My question is, how could we pass the Infos (what the hardware is capable of) to the bridge? For example, in the method provisioner_prov_complete_cb, p_prov_data (pointer to nrf_mesh_prov_evt_complete_t) contains address and p_context. Meanwhile there are also p_meta_data for health client event and composition data for config messages. Could I pass the infos as a string, or as hex data to the aforementioned data packet, and define which hex data meant for which hardware sensors?

Any helps and tips are much appreciated!

Many thanks,

WHui

[Hung Bui]

Hi WHui, 

The Thingy Mesh demo based on very old Mesh SDK v1.0.1. I would suggest you to have a look at our latest SDK v3.2.0 if you want to develop a new application. 

I don't think you can send some vendor specific data via the composition data. What you can do is to implement different models representing different hardware features of the device. For example if there is a Temperature model on the device meaning the device is capable of getting temperature. 

If you want to send some arbitrary vendor specific data as text , I would suggest to implement a specific model for it. So on each of the node there will be a server. And the client is located on the bridge. 

[WHui]

Hi Hung Bui,

Thank you for your reply!

If I understand correctly, do u mean that I should implement, let's say Hardware Infos Server Model (my vendor specific model) for each Thingy Nodes. This is just a model to send hardware Infos to Hardware Infos Client Model on my single Thingy Bridge. Right? 

[Hung Bui]

Yes, you are correct. 

[WHui]

Thanks a lot Hung Bui! I have found the guide for creating new model. If I have more question regarding creating vendor model I may open another ticket.