<?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 self provisioning or factory preconfigured</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39424/ble-mesh-self-provisioning-or-factory-preconfigured</link><description>Hi, 
 we want to made the device which should working in the mesh network without provisiong procedure by user. 
 Typical application - network with 500 nodes, every node placed in disabled mode (no power provided), we power them all simultaneously (turn</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 Oct 2018 08:54:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39424/ble-mesh-self-provisioning-or-factory-preconfigured" /><item><title>RE: BLE mesh self provisioning or factory preconfigured</title><link>https://devzone.nordicsemi.com/thread/152997?ContentTypeID=1</link><pubDate>Tue, 16 Oct 2018 08:54:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46708b0a-d6df-4053-bc4b-ddd9d9b689df</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;I would not recommend using factory hardcoded device/network key like that. &lt;br /&gt;When using a hardcoded network key, it increases the risk that someone may hack that master key and being able to access any of the company&amp;#39;s networks.&lt;br /&gt;If you do go for a hardcoded network and device key, it is hard for the unicast address. &lt;br /&gt;Without knowing which product is going to which application/customer, how would they assign the address?&lt;/p&gt;
&lt;p&gt;You could still be able to acheive &amp;quot;No customer intervention&amp;quot; when using our provisioner. &lt;br /&gt;The provisioner could run in the background to assign network keys/address.&lt;/p&gt;
&lt;p&gt;I suggest that you take a look at the Remote provisioning example in our nRF5 SDK for Mesh.&lt;/p&gt;
&lt;p&gt;Best regards, &lt;br /&gt;Joakim&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>