<?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>Is it possible to implement Configuration Client on non-provisioner?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46844/is-it-possible-to-implement-configuration-client-on-non-provisioner</link><description>I&amp;#39;m trying to extend the light_switch client example (from mesh SDK 3.1.0) to a gateway. The gateway will consists of nRF52832 and a WiFi module connected via serial interface. Purpose of this is to display the status of the lights on a IoT dashboard</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 May 2019 10:42:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46844/is-it-possible-to-implement-configuration-client-on-non-provisioner" /><item><title>RE: Is it possible to implement Configuration Client on non-provisioner?</title><link>https://devzone.nordicsemi.com/thread/185139?ContentTypeID=1</link><pubDate>Fri, 03 May 2019 10:42:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a735482d-e339-475b-b071-e552a32bd7e6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Yes, you can use that.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is it possible to implement Configuration Client on non-provisioner?</title><link>https://devzone.nordicsemi.com/thread/185018?ContentTypeID=1</link><pubDate>Fri, 03 May 2019 01:20:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3df1db81-da3b-47b5-b83f-34701cfc729d</guid><dc:creator>Leipo</dc:creator><description>&lt;p&gt;Thank you Hung Bui for the answer. In that case, it might be easier to integrate the simple message model to pass the address information and control messages.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is it possible to implement Configuration Client on non-provisioner?</title><link>https://devzone.nordicsemi.com/thread/184932?ContentTypeID=1</link><pubDate>Thu, 02 May 2019 13:50:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5c94a6a-a02c-4676-ac31-57a0a735a0a7</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Leipo,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You are correct about this part:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;nbsp;In order for Configuration Client to be bound to Configuration Server, the device key of the light server need to be known. The device key is only known to the light server node and the provisioner, i.e. the phone.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Your task is to send the device key(s) from the phone to the light switch client (which has the configuration client). I don&amp;#39;t think it should be very difficult to this. But it&amp;#39;s not defined in the spec on how to do this. You can think of using proprietary command/protocol or using BLE to send the keys. It should be properly encrypted.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>