<?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>When I change a node of mesh, devices stop communicate with new node till restart of device</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/63309/when-i-change-a-node-of-mesh-devices-stop-communicate-with-new-node-till-restart-of-device</link><description>I am using NRF52840 in Mesh (SDK 4.1.0), I am facing this strange issue, one of my node (have client+server both) is got damaged, I replaced this with new NRF52840, then I provisoned and give same node number as of damaged node. But After that this node</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Jul 2020 13:38:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/63309/when-i-change-a-node-of-mesh-devices-stop-communicate-with-new-node-till-restart-of-device" /><item><title>RE: When I change a node of mesh, devices stop communicate with new node till restart of device</title><link>https://devzone.nordicsemi.com/thread/258347?ContentTypeID=1</link><pubDate>Fri, 03 Jul 2020 13:38:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90b565df-8395-456c-838f-5e8f3230ca77</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Bivay,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Giving the replaced node with the same node address as the broken one might not be the best idea. I don&amp;#39;t think replacing a node is described in the Mesh spec that way. You can remove a node and add a new node into the network with the new address, not to re-use the previous address.&amp;nbsp;&lt;br /&gt;What went wrong here is that the new node may not have the same sequence number of IV index as other node when you provisioning it to the network. Packets with old sequence number will be ignored by the other nodes. And I think when you reset the node it will start accepting the new sequence number. So it&amp;#39;s better to use new address and avoid using unicast address in your network, use the group address instead.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>