<?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>Tutorial request - Proxy Service and BLE service merging</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/45878/tutorial-request---proxy-service-and-ble-service-merging</link><description>Hi all, 
 I have a hard time to merge Mesh Proxy Service and Nordic UART service. I am working with mesh SDK v. 3.1.0 and nRF5 SDK v. 15.2, coexistence example ble_app_uart_coexist. I have read all the posts here in the DevZone about this problematic</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Apr 2019 08:40:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/45878/tutorial-request---proxy-service-and-ble-service-merging" /><item><title>RE: Tutorial request - Proxy Service and BLE service merging</title><link>https://devzone.nordicsemi.com/thread/180951?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 08:40:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb620343-db66-415a-8386-023fa18f269d</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I can understand that it is not straight forward to do what you request, but currently we don&amp;#39;t have a tutorial doing exactly this, but unfortunately, it would be difficult to create and maintain all possible combinations of BLE services with Mesh.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The uart coexistence example in the mesh SDK does pretty much what you describe. You can use the provisioner from the mesh SDK to provision this. You can also connect using the uart part of nRF Toolbox.&lt;/p&gt;
&lt;p&gt;You can&amp;nbsp;&lt;strong&gt;not&lt;/strong&gt; provision the uart coexistence example using the nRF Mesh app, because it is looking for a specific advertisement UUID (the provisioning/proxy UUID) when it is scanning. If you add the proxy service, and change the advertising UUID to use the proxy UUID (like the light_switch client does), then you could connect to it using the nRF Mesh app. However, the UART module in nRF Toolbox is looking for the Nordic UART Service (NUS) in the advertisements, and filtering out everything else. But you can still connect with the nRF Connect for mobile app.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;So you can either provision with the provisioner from the light_switch\provisioner example, or change the coexistence project to use the proxy advertisement UUID to provision it via the nRF Mesh app. Note that once it is provisioned, this data is stored in flash, so it will not be removed until you erase the entire chip.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>