<?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>Sequence number validation</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/106000/sequence-number-validation</link><description>Hello, 
 We are facing some issue on Sequence number, as if we export and import json file from the nrf mesh application to another nrf mesh application then controlling wont happen due to Sequence no. error. 
 I wanted to know where we are validating</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Nov 2023 14:37:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/106000/sequence-number-validation" /><item><title>RE: Sequence number validation</title><link>https://devzone.nordicsemi.com/thread/457202?ContentTypeID=1</link><pubDate>Thu, 23 Nov 2023 14:37:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bbc9ba3a-fa9a-4b86-a2de-ceb74c64bfb9</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sequence numbers are checked by the Bluetooth Mesh stack, which should not be changed. (Changing the stack in any way breaks the qualification, so any changed stack must be requalified. Changing it in the way you suggests will change the behavior in such a way that the modified stack cannot pass qualification.)&lt;/p&gt;
&lt;p&gt;If at any one point you end up with two devices where both device uses the same unicast address, then you will see issues with sequence numbers.&lt;/p&gt;
&lt;p&gt;If you want two smartphones controlling the network, then you should first add a new provisioner under Provisioners in the Settings tab, and assign the new provisioner a different unicast address. When you export, uncheck the &amp;quot;export everything&amp;quot; selection, and pick which provisioner to export (the new one). Then when you import, the new device will use that new unicast address of the new provisioner, instead of sharing unicast address with the old one.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>