<?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 unprovisioned device proxy</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/63089/mesh-unprovisioned-device-proxy</link><description>My company has a situation where we have 3+ devices. 
 
 A is the provisioner (also an embedded device) 
 B is a already provisioned device 
 C is a non-provisioned device. 
 
 If C is too far away from A, can B act as a go between for the provisioning</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 29 Jun 2020 11:00:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/63089/mesh-unprovisioned-device-proxy" /><item><title>RE: Mesh unprovisioned device proxy</title><link>https://devzone.nordicsemi.com/thread/257335?ContentTypeID=1</link><pubDate>Mon, 29 Jun 2020 11:00:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:619000fb-0fc1-4827-b7fb-67add32413c8</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Bluetooth mesh does not have remote provisioning in the specification, but we do have a proprietary solution for this in the nRF5 SDK for Mesh. See &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v4.1.0%2Fmd_doc_user_guide_modules_provisioning_pb_remote.html"&gt;Remote provisioning (PB-remote)&lt;/a&gt;.&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>