<?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>nrf52 mesh max node question</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69020/nrf52-mesh-max-node-question</link><description>In our mesh application, we are trying to give all our devices the same network key. As we are planning to have in excess of 100,000 devices, the 2-byte unicast address is insufficient. I have been examining the mesh SDK to determine the feasibility of</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 06 Dec 2020 23:02:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69020/nrf52-mesh-max-node-question" /><item><title>RE: nrf52 mesh max node question</title><link>https://devzone.nordicsemi.com/thread/283436?ContentTypeID=1</link><pubDate>Sun, 06 Dec 2020 23:02:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4da90f8f-c1bb-4ad1-94b2-a5b9c3e084dd</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;Doing this will cause your devies and network to break the Mesh specification. Thus, you won&amp;#39;t be able to qualify as a BLE Mesh device.&lt;/p&gt;
&lt;p&gt;Other than that I can&amp;#39;t say which issues you might run into, as we haven&amp;#39;t tested this (cause it breaks spec.). &lt;br /&gt;But on top of my head I can&amp;#39;t see that it should be any specific issues with implementing this yourself.&lt;/p&gt;
&lt;p&gt;Br, &lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>