<?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>Bluetooth mesh node with radio mostly turned off</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38251/bluetooth-mesh-node-with-radio-mostly-turned-off</link><description>Hi! 
 
 I may have asked about this earlier in a lengthy question: 
 https://devzone.nordicsemi.com/f/nordic-q-a/35576/low-power-remote-control 
 But I&amp;#39;d like to be sure about how often a node needs to be present on a Bluetooth mesh network. The spec</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Sep 2018 08:13:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38251/bluetooth-mesh-node-with-radio-mostly-turned-off" /><item><title>RE: Bluetooth mesh node with radio mostly turned off</title><link>https://devzone.nordicsemi.com/thread/147944?ContentTypeID=1</link><pubDate>Mon, 10 Sep 2018 08:13:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e3ba8db-cf8e-4f3e-878d-4649e8260f35</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;div&gt;Yes, you should be able to keep the radio turned off for 48 weeks without the device having to be reprovisioned. You might want to turn the device back on after 47 weeks for example, as clock drift could lead the device to believe it is turning on after 48 weeks, but it might actually be turning on after 48 weeks. In this case, the remote may need to be reprovisioned.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;You have two options: either you can turn on the device every 96 hours to be able to listen for when the IV Index is incremented &amp;amp; update its IV Index. This way, the remote will be able to communicate with the mesh network all of the time.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;The second option: turn off the device for 47 weeks or so, turn the device back on &amp;amp; listen for the secure network beacon. The Secure Network beacon contains info about any key refresh being done &amp;amp; the current IV Index. The low power device will need to be on for around five seconds to listen for this beacon.&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth mesh node with radio mostly turned off</title><link>https://devzone.nordicsemi.com/thread/147550?ContentTypeID=1</link><pubDate>Thu, 06 Sep 2018 10:23:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:338e7c56-d901-4c0c-8036-38d0b22472c3</guid><dc:creator>TYRI</dc:creator><description>&lt;p&gt;...and just to clarify. A more specific scenario would be to have a certain number of lamps which are all turned on simultaneously, including their radio, hence keeping the network &amp;quot;active&amp;quot; (although they may all be turned off when not used).&lt;/p&gt;
&lt;p&gt;The node which &amp;quot;mostly keeps its radio turned off&amp;quot; is a remote control that is used to control the lamps. For instance, we&amp;#39;d like to keep the radio on only for a short period when the user presses a button.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>