Path of the message in the mesh

[Andy]

Hi all, I got the requirement to actually know the path of a message from a client to server(s). Is it possible to add a few bytes of data until the message reaches the server(s)?  This way I will know if a message goes from A -> C -> D -> Q and A -> R -> S -> Q.  This is for the optimization of node placements and maintenance.

Thank you in advance!

[Bjørn Kvaale]

Yes, it should be possible. I would take a close look at the heartbeat functionality. You can use the heartbeat functionality to optimize the time to live between nodes. 

In addition, the heartbeat model should allow you to see the RSSI to a central node. If you run the mesh sdk v3 with the light switch privisioner, client & server examples, you can take a look at the app_health_event_cb() in main.c of the provisioner example. There, the RSSI between nodes & the provisioner is given (take a look at the Reliability Questions section here).

I would also take a closer look at the mesh spec & read up more on heartbeat functionality there. I believe it should be possible to figure out the RSSI between different nodes via the health model to optimize the node placement. You could for example move your provisioner around the mesh network & then you will constantly receive the RSSI information from all mesh nodes. That way, you could then optimize the node placement that way.

[Andy]

Hi Bjørn, quick question.  I am using sdk v3, would a client be able to listen to the heart beats?  

[Bjørn Kvaale]

Yes, you should be able to configure this. I made a mistake. I was supposed to refer to the health model & not the heartbeat model. I would take a good look at the health client model in Section 4.4.4 of the Mesh Profile Spec. Then, see how the health client is initialized in the provisioner & do the same steps in the client example. It should be very similar to how the generic on off client is initialized in the client example.

[Andy]

Thank you.  Definitely will look at the health model.