<?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>RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97827/rssi-value-of-packet-in-mesh</link><description>Hi, 
 
 We need to read a RSSI value of received packet from nRF Mesh layer, have traced the RSSI of recieved packet in bt_mesh_msg_ctx structure -&amp;gt; recv_rssi ; 
 checked in debug mode, verified in access layer when i debug the ctx of recieved packet</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Apr 2023 07:08:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97827/rssi-value-of-packet-in-mesh" /><item><title>RE: RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/thread/419529?ContentTypeID=1</link><pubDate>Tue, 11 Apr 2023 07:08:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11c7a1b0-b067-489f-805f-433a5e910d19</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry about the long delay in response.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The controller doesn&amp;#39;t provide such information for rx functions of gatt characteristics. Mesh doesn&amp;#39;t have any sources to pick up this information. Proxy srv/cli always set rx rssi value to 0.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As a solution you can register your own connection callback (BT_CONN_CB_DEFINE) to get the connection handle. Then you can call HCI command to read out RSSI value whenever you want to.&amp;nbsp;&lt;br /&gt;You can take a look at this sample on how this can be done:&amp;nbsp;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/bluetooth/hci_pwr_ctrl/src/main.c"&gt;https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/bluetooth/hci_pwr_ctrl/src/main.c&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also, you need to check the role in the connected callback (BT_CONN_ROLE_PERIPHERAL) and identity (BT_ID_DEFAULT) like we do here:&amp;nbsp;&lt;br /&gt;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/blob/0e6c306dcec991311b11b4090430ade43d04777e/subsys/bluetooth/mesh/pb_gatt_srv.c#L102-L106"&gt;https://github.com/zephyrproject-rtos/zephyr/blob/0e6c306dcec991311b11b4090430ade43d04777e/subsys/bluetooth/mesh/pb_gatt_srv.c#L102-L106&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve talked to our developers, and currently there is no plans to add reading RSSI value in proxy messages. But this might change in the future.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Br,&amp;nbsp;&lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/thread/418946?ContentTypeID=1</link><pubDate>Tue, 04 Apr 2023 07:15:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d624c72-369c-4bbc-a809-5273ca09a9fb</guid><dc:creator>hiteshk014</dc:creator><description>&lt;p&gt;Hi&lt;span&gt; JoaKim&lt;/span&gt;,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Can you please expedite the solution for this problem&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Hitesh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/thread/417566?ContentTypeID=1</link><pubDate>Mon, 27 Mar 2023 06:11:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4eb78293-2557-4247-8aed-bbb12c2578ae</guid><dc:creator>hiteshk014</dc:creator><description>&lt;p&gt;Hi JoaKim,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Can you please expedite the solution for this problem&lt;/p&gt;
&lt;p&gt;we&amp;#39;re not able to get rssi value in ctx of recieved packet when it is sent out from mobile phone&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Hitesh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/thread/416774?ContentTypeID=1</link><pubDate>Wed, 22 Mar 2023 11:54:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:447ba0be-2a22-437d-ab22-b3ce4d8b0dce</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t have an Android phone to reproduce at the moment, but I&amp;#39;ll ask our developers about it.&lt;/p&gt;
&lt;p&gt;Br,&lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/thread/416469?ContentTypeID=1</link><pubDate>Tue, 21 Mar 2023 09:35:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c6c6c1b-5938-4b07-b3b9-bf68248f2213</guid><dc:creator>hiteshk014</dc:creator><description>&lt;p&gt;Hi Joakin,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve observed these observations in nRF Mesh app downloaded from Play store, Android&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Hitesh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI value of Packet in Mesh</title><link>https://devzone.nordicsemi.com/thread/416397?ContentTypeID=1</link><pubDate>Mon, 20 Mar 2023 22:41:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fefc548a-7a9a-4c7d-8934-b31fab360f41</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;Thank you for your question.&lt;/p&gt;
&lt;p&gt;Might be due to a limitation on the phone side, but I&amp;#39;ll investigate. Could you also share which OS you are using on your phone?&lt;/p&gt;
&lt;p&gt;Br, &lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>