Changing ZigBee Max Children Between Firmware Versions

[WestCoastDaz]

Is there an issue with releasing application firmware, say v1.0 with 

zb_set_max_children(10);

 and then in a following release via DFU, say v1.1 with 

zb_set_max_children(15)

.

I'm trying to understand if a network has been formed and devices have joined if the increased number of children in v1.1 will mean the change in device count will mean the devices need to be removed and re-joined?

Thanks,

[Edvin]

Hello,

Do you experience any issues when updating the zb_set_max_children() from 10 to 15 after joining the network? I don't think you need to perform an actual DFU to check this. If it has joined a network, updating the FW without erasing the persistent storage area of the flash should behave the same as a DFU in this case, since the bootloader is on top, and the persistent storage is below that. 

Best regards,

Edvin

[WestCoastDaz]

Edvin

I haven't experienced any issues.  I wanted to ensure that there were no ZBOSS NVRAM allocation issues with updating this between versions.  

[Edvin]

Hello,

I ran this by our Zigbee team, and received the reply:

"I cannot find place of NVRAM code that may be corrupted by making this change, so I would say that this is safe to be changed between firmware upgrades."

So it should be fine to expand the number of child nodes via a DFU.

BR,

Edvin

[WestCoastDaz]

Edvin Thank you for checking with the ZigBee team!