<?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>Number of hops BT Mesh</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41235/number-of-hops-bt-mesh</link><description>Hello, 
 
 To determine the current network topology I hoped I could use the heartbeats to determine the RSSI and the number of hops. The RSSI of the last node is in the example (health client), but I can&amp;#39;t find the number of hops. Is that accessible</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Jan 2019 07:53:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41235/number-of-hops-bt-mesh" /><item><title>RE: Number of hops BT Mesh</title><link>https://devzone.nordicsemi.com/thread/164426?ContentTypeID=1</link><pubDate>Tue, 08 Jan 2019 07:53:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:296e059f-ee2c-425e-a819-5b7e5a8a5f17</guid><dc:creator>Milogic</dc:creator><description>&lt;p&gt;OK Clear. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Number of hops BT Mesh</title><link>https://devzone.nordicsemi.com/thread/161159?ContentTypeID=1</link><pubDate>Tue, 11 Dec 2018 10:24:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52564d61-20fd-4b88-bc95-6b7db149b56a</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Number of hops is available in the NRF_MESH_EVT_HB_MESSAGE_RECEIVED event, in the field evt.params.hb_message.hops. See the &lt;a href="https://www.nordicsemi.com/DocLib/Content/SDK_Doc/Mesh_SDK/v3-0-0/structnrf__mesh__evt__hb__message__t"&gt;nrf_mesh_evt_hb_message_t Struct Reference&lt;/a&gt; for descriptions of all fields.&lt;/p&gt;
&lt;p&gt;There is no method provided through the Bluetooth mesh specification for finding the full path of the packet, so in that case you will have to build something for that yourself. You would need to in every node to figure out what nodes they receive messages from, and communicate that information out from the nodes. Please note however that this quickly becomes very statistical/probabilistic, as not every packet will make the same &amp;quot;path&amp;quot; through the network. (Bluetooth mesh is a flooding network, and so every packet will &amp;quot;spread&amp;quot; or &amp;quot;flood&amp;quot; out from the point of origin through the network. It is not a point-to-point routed network.)&lt;/p&gt;
&lt;p&gt;I also found a DevZone thread named &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/37227/mesh-monitor-with-heartbeat-messages"&gt;Mesh Monitor with Heartbeat Messages&lt;/a&gt; which may be of some interest to you.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>