<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Path of the message in the mesh</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/43724/path-of-the-message-in-the-mesh</link><description>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 -&amp;gt; C -&amp;gt; D -&amp;gt; Q and A -&amp;gt; R</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Feb 2019 00:51:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/43724/path-of-the-message-in-the-mesh" /><item><title>RE: Path of the message in the mesh</title><link>https://devzone.nordicsemi.com/thread/172205?ContentTypeID=1</link><pubDate>Thu, 21 Feb 2019 00:51:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5f4fd5b-b35a-48eb-a521-4ef4f65fa4b0</guid><dc:creator>Andy</dc:creator><description>&lt;p&gt;Thank you.&amp;nbsp; Definitely will look at the health model.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Path of the message in the mesh</title><link>https://devzone.nordicsemi.com/thread/172083?ContentTypeID=1</link><pubDate>Wed, 20 Feb 2019 11:13:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df1c36fd-a1eb-4b0c-93a5-a5fb3785e2e6</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Yes, you should be able to configure this. I made a mistake. I was supposed to refer to the health model &amp;amp; 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 &amp;amp; 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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Path of the message in the mesh</title><link>https://devzone.nordicsemi.com/thread/171493?ContentTypeID=1</link><pubDate>Sat, 16 Feb 2019 00:53:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:792e4451-b7f9-4e82-a6b6-8133333ba1de</guid><dc:creator>Andy</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi Bj&amp;oslash;rn, quick question.&amp;nbsp; I am using sdk v3, would a client be able to listen to the heart beats?&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Path of the message in the mesh</title><link>https://devzone.nordicsemi.com/thread/171443?ContentTypeID=1</link><pubDate>Fri, 15 Feb 2019 15:22:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d09097d-522f-4103-ad20-3d0d3260f3ea</guid><dc:creator>Andy</dc:creator><description>&lt;p&gt;Thank you&amp;nbsp;Bj&amp;oslash;rn , definitely will look at the heart beat functionality.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Path of the message in the mesh</title><link>https://devzone.nordicsemi.com/thread/171437?ContentTypeID=1</link><pubDate>Fri, 15 Feb 2019 14:59:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a0b41c4-bc32-40a9-83ce-e704662caf63</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Yes, it should be possible. I would take a close look at the &lt;a href="https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-glossary#heartbeat"&gt;heartbeat functionality&lt;/a&gt;. You can use the heartbeat functionality to optimize the time to live between nodes.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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 &amp;amp; server examples, you&amp;nbsp;can take a look at the&amp;nbsp;app_health_event_cb() in main.c of the provisioner example. There, the RSSI between nodes &amp;amp; the provisioner is given (take a look at the Reliability Questions section &lt;a href="https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-faq"&gt;here&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;I would also take a closer look at the mesh spec &amp;amp; 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 &amp;amp; then you will constantly receive the RSSI information from all mesh nodes. That way, you could then optimize the node placement that way.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>