<?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>Mesh Gatt Peripheral Role</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/65375/mesh-gatt-peripheral-role</link><description>Device nrf52832, nrf5_SDK_for_Mesh_v3.2.0_src with nRF5_SDK_15.3.0_59ac345 
 Hello. 
 I want to transmit and receive some data between smartphone app and mesh sensor.(almost similar function as light_switch server model) 
 I made the mesh server has a</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Sep 2020 09:04:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/65375/mesh-gatt-peripheral-role" /><item><title>RE: Mesh Gatt Peripheral Role</title><link>https://devzone.nordicsemi.com/thread/267401?ContentTypeID=1</link><pubDate>Tue, 01 Sep 2020 09:04:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5da45308-7439-486a-8a14-fe53fe461deb</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Good to hear that it works, I do not see any reason why this should affect mesh function no.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Gatt Peripheral Role</title><link>https://devzone.nordicsemi.com/thread/267374?ContentTypeID=1</link><pubDate>Tue, 01 Sep 2020 08:01:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d160618-879a-4d16-a3ae-e2e19d02f417</guid><dc:creator>Charlie Choi</dc:creator><description>&lt;p&gt;Hello Kenneth,&lt;/p&gt;
&lt;p&gt;Thank you for your advice. I tested per your suggestion and got a good result. i.e. Device name and advertisement type seems stable.&lt;/p&gt;
&lt;p&gt;Could you confirm that&amp;nbsp;this alteration of gap address doesn&amp;#39;t affect the mesh function?&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;
&lt;p&gt;Charlie.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Gatt Peripheral Role</title><link>https://devzone.nordicsemi.com/thread/267197?ContentTypeID=1</link><pubDate>Mon, 31 Aug 2020 11:28:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4e23cf7-1a9a-42b0-9223-f6b17eac021f</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;I was thinking the problem could be related to the same gap address is used for connectable and non-connectable here. This may prevent the mobile to connect to the device, so maybe change the gap address&amp;nbsp;before starting connectable advertisement? Something like:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    ble_gap_addr_t gap_addr;
    err_code = sd_ble_gap_addr_get(&amp;amp;gap_addr);
    APP_ERROR_CHECK(err_code);    
    gap_addr.addr[3] = ~gap_addr.addr[3]; // flip the bits when connectable
    err_code = sd_ble_gap_addr_set(&amp;amp;gap_addr);
    APP_ERROR_CHECK(err_code);  &lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>