https://devzone.nordicsemi.com/f/nordic-q-a/117842/issues-in-scaling-bluetooth-mesh-network-with-nrf52840-provisionerHi all, I am developing my own provisioner with the nrf52840 chip. My idea is to be able to add at least 2000 nodes to a bluetooth mesh network with the provisioner but I am having several problems. When I add a node to the network and configure iten-USTelligent Community 13Thu, 09 Jan 2025 17:19:58 GMThttps://devzone.nordicsemi.com/thread/517779?ContentTypeID=1Thu, 09 Jan 2025 17:19:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a691b6e0-164c-47d3-af29-56e16a5bc182tesc<p>Hi,</p> <p>2000 might be a bit on the high side, but depending on the size of the application you could be able to find space on the nRF52840 for that number of nodes.</p> <p>Flash storage by the Bluetooth Mesh stack, most importantly the configuration database (CDB) and the replay protection list (RPL), uses the <a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/settings/index.html">Settings</a> subsystem of nRF Connect SDK. Assuming a single image build with standard configurations, including use of NVS as the flash backend for the settings subsystem, you should increase the size of the settings storage through <a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/kconfig/index.html#CONFIG_SETTINGS_NVS_SECTOR_COUNT">CONFIG_SETTINGS_NVS_SECTOR_COUNT</a>. The default configuration of 8 provides 8 * 4096 = 32 k of settings storage. Increasing this storage should provide room for storing larger CDB and RPL, in turn allowing for provisioning more devices.</p> <p>Please note that if you plan on doing BLE OTA DFU, then you need around double the amount of flash space for the application, since you need to keep the current application while you download the new version of the application to upgrade to.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>