<?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>How to access mesh proxy packets</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125688/how-to-access-mesh-proxy-packets</link><description>Hi, 
 We&amp;#39;ve had a mesh sensor network all working for a long time using SDK17.0.2 + Mesh SDK 4.1.0 
 The data is accessed by a mobile app through a mesh node acting as a proxy. We can send data back and forth from the mobile app through the mesh proxy</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 21 Nov 2025 14:28:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125688/how-to-access-mesh-proxy-packets" /><item><title>RE: How to access mesh proxy packets</title><link>https://devzone.nordicsemi.com/thread/555068?ContentTypeID=1</link><pubDate>Fri, 21 Nov 2025 14:28:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2f89546-eeaa-42e0-8a33-d275dfbee34e</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Unfortunately, there is no such function in SDK 17.0.2 + Mesh SDK 4.1.0 that meets your requirement.&lt;span&gt;&amp;nbsp;You have to implement by yourself.&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to access mesh proxy packets</title><link>https://devzone.nordicsemi.com/thread/554946?ContentTypeID=1</link><pubDate>Thu, 20 Nov 2025 16:17:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ee780a4-3820-4967-9cd3-2f3c4227784b</guid><dc:creator>ftjandra</dc:creator><description>&lt;p&gt;Hi Amanda,&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t have those functions or&amp;nbsp;&lt;span&gt;proxy_msg.c. I am using SDK17.0.2 + Mesh SDK 4.1.0 (modified light switch server).&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to access mesh proxy packets</title><link>https://devzone.nordicsemi.com/thread/554943?ContentTypeID=1</link><pubDate>Thu, 20 Nov 2025 15:57:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:185f1190-99ed-43e5-a687-05658c4b95cf</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you want to print logs on the embedded side, there is no&amp;nbsp;&lt;span&gt;dedicated&lt;/span&gt;&amp;nbsp;interface or debug prints &lt;span&gt;to get access to proxy packets&lt;/span&gt;. You can add your own logging at the following places and print the raw packets:&lt;/p&gt;
&lt;p&gt;For packets being received by the embedded device via proxy: add logging &lt;a title="https://github.com/zephyrproject-rtos/zephyr/blob/cb89816c0dd67b9833d78bd55a04ff24a8edcc67/subsys/bluetooth/mesh/proxy_msg.c#l110" href="https://github.com/zephyrproject-rtos/zephyr/blob/cb89816c0dd67b9833d78bd55a04ff24a8edcc67/subsys/bluetooth/mesh/proxy_msg.c#L110" rel="noopener noreferrer" target="_blank"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For packets being sent by the embedded device to the proxy: add logging &lt;a title="https://github.com/zephyrproject-rtos/zephyr/blob/cb89816c0dd67b9833d78bd55a04ff24a8edcc67/subsys/bluetooth/mesh/proxy_msg.c#l174" href="https://github.com/zephyrproject-rtos/zephyr/blob/cb89816c0dd67b9833d78bd55a04ff24a8edcc67/subsys/bluetooth/mesh/proxy_msg.c#L174" rel="noopener noreferrer" target="_blank"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Ensure that you analyze the code and add appropriate logging or make the proper modifications. Because the function calls, especially within bt_mesh_proxy_msg_send(), might return errors, which means the message was not sent (or processed). You should consider these return codes of underlying functions and then decide whether to print a particular packet in the log or not. Be careful not to break functional logic there.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>