<?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>nRF Mesh self provision on client</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64187/nrf-mesh-self-provision-on-client</link><description>Dear all, I try to self provision device by it self following steps below: Step 1 : Bind key Step 2 : Subscribe to topic 
 Step3 : Set publication topic 
 
 
 Step 4 The main code to config device 
 
 The problem is, after self provisioned and reboot</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 28 Jul 2020 08:13:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64187/nrf-mesh-self-provision-on-client" /><item><title>RE: nRF Mesh self provision on client</title><link>https://devzone.nordicsemi.com/thread/261898?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2020 08:13:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:517d86c0-89ce-4882-91c3-409e0fd14e1f</guid><dc:creator>huybk213</dc:creator><description>&lt;p&gt;Dear Simon,&lt;br /&gt;&lt;br /&gt;I use nRF Mesh SDK 4.2 and BLE SDK 16&lt;/p&gt;
&lt;p&gt;I will take a look at documents.&lt;br /&gt;&lt;br /&gt;Thank you,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Mesh self provision on client</title><link>https://devzone.nordicsemi.com/thread/261886?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2020 07:02:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bebb4564-d07b-435b-a6d1-725b30adb98d</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Which Mesh SDK and device are you using here? The provisioning data should be stored in Flash for the device to automatically join the network when powering up. The NRF_ERROR_NOT_FOUND point towards that the data can&amp;#39;t be found, so it seems like it isn&amp;#39;t stored properly.&lt;/p&gt;
&lt;p&gt;I suggest you give the provisioning section of the Mesh specification a read to get a better understanding of how the self-provisioning process is working.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Mesh self provision on client</title><link>https://devzone.nordicsemi.com/thread/261715?ContentTypeID=1</link><pubDate>Mon, 27 Jul 2020 07:29:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:589c048d-0c5e-48cd-9437-c826ee456b2c</guid><dc:creator>huybk213</dc:creator><description>&lt;p&gt;Hi all,&lt;br /&gt;The call stack is&amp;nbsp;access_model_publish -&amp;gt;&amp;nbsp;&amp;nbsp;packet_alloc_and_tx-&amp;gt;packet_tx-&amp;gt;dsm_tx_secmat_get-&amp;gt;app_tx_secmat_get-&amp;gt; NRF_ERROR_NOT_FOUND&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>