<?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>Problems changing Network-Key</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/32760/problems-changing-network-key</link><description>In the light switch example, I try to change the network-key and then get some new unprovisioned servers provisioned. 
 The servers seem to get provisioned, but the client logs &amp;quot; Configuration of device 1 failed&amp;quot; and there is no communication. 
 I use</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 May 2019 07:53:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/32760/problems-changing-network-key" /><item><title>RE: Problems changing Network-Key</title><link>https://devzone.nordicsemi.com/thread/185844?ContentTypeID=1</link><pubDate>Wed, 08 May 2019 07:53:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:511b701a-5ada-4b77-9568-d97c52b4e378</guid><dc:creator>Emile Albert</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Could you provide the location of the hardcoded network key in simple_coap_server example ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks in advance !&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problems changing Network-Key</title><link>https://devzone.nordicsemi.com/thread/127566?ContentTypeID=1</link><pubDate>Tue, 10 Apr 2018 09:11:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32ce09d3-0747-42db-91ed-b287585ed737</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Seger,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It most likely was because we hard coded the Network Key in our provisioner in the light switch example. In&amp;nbsp;start_provisioning() you can find that we use&amp;nbsp;NETKEY which is the original one.&amp;nbsp;You would need to edit the code and pass your new netkey to the provisioner.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Key refresh is supported from SDK v1.0.x. The way you call&amp;nbsp;dsm_subnet_update_* () to do key refresh seems to be correct.&lt;/p&gt;
&lt;p&gt;But if you want to do key refresh for already provisioned nodes, you would need to use configuration client to talk to all configuration servers on all node and update the new key to them before you&amp;nbsp;call&amp;nbsp;dsm_subnet_update_swap_keys() on the provisioner to start swapping keys.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>