<?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>BLE Mesh provision and configuration by a codeword</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41771/ble-mesh-provision-and-configuration-by-a-codeword</link><description>Hello Nordic community, 
 is it possible to configure the network key, application key, node address with the help of a byte array? The keys, adresses and all the peripheral configuration shall be included in this array. I have tried some lines of code</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 21 Dec 2018 08:27:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41771/ble-mesh-provision-and-configuration-by-a-codeword" /><item><title>RE: BLE Mesh provision and configuration by a codeword</title><link>https://devzone.nordicsemi.com/thread/162788?ContentTypeID=1</link><pubDate>Fri, 21 Dec 2018 08:27:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:55cd40fa-17a1-4c82-a329-86250340257e</guid><dc:creator>Patrick_</dc:creator><description>&lt;p&gt;Thanks for the hint. &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh provision and configuration by a codeword</title><link>https://devzone.nordicsemi.com/thread/162778?ContentTypeID=1</link><pubDate>Fri, 21 Dec 2018 07:17:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bbe3bd07-6ae4-45a8-84c9-0c3b3362cafc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Thanks, now it makes sense.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a good idea to send data via NFC&amp;nbsp;as an alternative to&amp;nbsp;the standard provisioning process. I assume you aware that&amp;nbsp;this is proprietary and won&amp;#39;t support by other vendors. In addition, if you want to change configuration or do key refresh, you still need to do it the traditional way.&amp;nbsp;You may need to have a way to avoid the risk that the attacker can also use NFC to get the bait device provisioned and get the network key , appkey transferred.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;To do this you would need to write your own code to read data from NFC and write to flash the provisioning data.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I would suggest to have a look at how the provisioning data being stored in our example and follow that (mesh_stack_provisioning_data_store () )&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh provision and configuration by a codeword</title><link>https://devzone.nordicsemi.com/thread/162660?ContentTypeID=1</link><pubDate>Thu, 20 Dec 2018 13:05:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c7559a2-be9f-4b3f-b25a-1b1709bc678b</guid><dc:creator>Patrick_</dc:creator><description>&lt;p&gt;Hi, I would like to implemant the possibility to configure the node via NFC. So I can perform the provisioning process via provisioner node and NFC data. So the node should do self provisioniing in case of a valid incoming NFC configuration command + configuration parameters. In addition I would like to configure also the peripheral which is attached to the nRF microcontroller via NFC data string. &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh provision and configuration by a codeword</title><link>https://devzone.nordicsemi.com/thread/162606?ContentTypeID=1</link><pubDate>Thu, 20 Dec 2018 08:05:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fa94902-b249-448c-9332-3c3c295f9631</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Patrick,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;What exactly do you want to do ? Could you describe what would be the workflow you want to do provisioning + configuration ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Bluetooth Mesh is an open standard, you would need to follow what describe in the spec in order to pass the qualification and to allow interoperability.&lt;/p&gt;
&lt;p&gt;Of course you can define your own &amp;quot;hard-coded provisioning&amp;quot; but then your device would be out to the market as &amp;quot;preprovisioned&amp;quot;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you want to know more about the provisioning please have a look at the light switch\ provisioning example and the documentation &lt;a href="https://www.nordicsemi.com/en/DocLib/Content/SDK_Doc/Mesh_SDK/v3-0-0/md_doc_getting_started_provisioning"&gt;here&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>