multiple server on one client - light switch demo

[vnagy]

Hellou. I'm developing application, which is modifiaction of light switch demo. I need use 128 servers and one client. But when I redefine in SERVER_COUNT to 128 in client application, it is no posible connect to servers (servers are not promisioned). I was read somewhere its needed change ACCESS_FLASH_PAGE_COUNT and DSM_FLASH_PAGE_COUNT . But I didn't find how many pages are needed for example 128 servers. My question is how many bytes are needed for writing data to ACCESS_FLASH and how many bytes are needed for writing data to DSM_FLASH by promisioning for 1 server. When i know how many bytes ist needed for 1 bytes, its enoght multiple by SERVER _COUNT(exactly 128) and from this calculate hoe many pages is needed for ACCESS_FLASH_PAGE_COUNT and  DSM_FLASH_PAGE_COUNT. 

Thank you for answer. 

[vnagy]

OK, i understand this. I our projects is gateway also provisioneer, so it need store data about nodes. How many nodes its posible connect on gateway, which is also provisioneer? 

[Hung Bui]

Ok, so the minimum data need to be stored on the provisioner about a node is: unicast address, number of elements, device key, network key index 

We currently don't store those information on flash on the provisioner. You are free to choose how you want to store them. They are just a dozens of byte per node, so it's not the flash size would be the limit. A few hundred nodes shouldn't be problem. But you will need to think of how you organize , and search for a node when you want to reconfigure them. 

Also on the provisioner, if you want to do black listing, using key refresh, you would need to update the database about black listed node. 

Here is some information about the flash usage on a node (but not about the provisioning database):

http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v2.0.1/md_doc_getting_started_how_to_nordicSDK.html?cp=4_1_0_3_6

And

https://raw.githubusercontent.com/NordicSemiconductor/nRF5-SDK-for-Mesh/master/doc/introduction/mesh_hw_resources.md

 

[Armin]

I think there is an error in the last paragraph of your answer. You mention the same function access_model_publish_address_set() for both setting the app key and the publication address. I guess the first is not the one you actually had in mind. Could you please correct that? Is it always necessary to set an app key if there was already assigned an address and now is only changed to another one?

[Thierry]

I would guess he meant 
access_model_application_bind()