<?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 program Bluetooth Mesh server on provisioning device?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27665/how-to-program-bluetooth-mesh-server-on-provisioning-device</link><description>The Bluetooth Mesh Light Switch example provides an example of how to program a Bluetooth Mesh application where the client model is on the provisioner device and the server models are on other devices. 
 I am having problems figuring out how to program</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 30 Nov 2017 12:36:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27665/how-to-program-bluetooth-mesh-server-on-provisioning-device" /><item><title>RE: How to program Bluetooth Mesh server on provisioning device?</title><link>https://devzone.nordicsemi.com/thread/109213?ContentTypeID=1</link><pubDate>Thu, 30 Nov 2017 12:36:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9e6552d-6f60-4f01-bfe8-c76234938f2c</guid><dc:creator>ketil</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;These functions are the same functions that are called on the server peripherals during configuration. The provisioner also needs to be configured and therefore calls these functions directly. So the reason is, as you suggest, that it is because the device is the provisioner.&lt;/p&gt;
&lt;p&gt;Ketil&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>