NCS Mesh: Precautions of Firmware update when Model Composition is changedhttps://devzone.nordicsemi.com/f/nordic-q-a/107640/ncs-mesh-precautions-of-firmware-update-when-model-composition-is-changedAs far as I know in Mesh 1.0 Model Composition is assumed to be not changed. Question is what happens if Model Composition is changed with an firmware update? I think we have potential issue when adding new model to the device which has some modelsen-USTelligent Community 13Tue, 23 Jan 2024 14:36:37 GMTRE: NCS Mesh: Precautions of Firmware update when Model Composition is changedhttps://devzone.nordicsemi.com/thread/465621?ContentTypeID=1Tue, 23 Jan 2024 14:36:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3473faf5-d6f8-4ad3-b1cb-3fd6f69247a0Hieu<p>Hello mesh777,</p> <p>Since you mentioned Bluetooth Mesh 1.0, I think you might have known Bluetooth Mesh 1.1&nbsp;was released with an official DFU solution specified, as well as the Node Composition Refresh procedure.</p> <p>However, I would like to check anyway. Is Mesh 1.1 an option for you, or do you need a way to make things work with Mesh 1.0?</p> <p>Hieu</p><div style="clear:both;"></div>