https://devzone.nordicsemi.com/f/nordic-q-a/81408/mesh_sdk-unable-to-update-mesh-device-group-after-a-new-device-provisionedHi, I have setup a provisioner using the provisioner example of the mesh sdk. I have also setup 10 nodes using the on_off example of the mesh sdk. I have provision all my node with the provisioner and no problem. After that I have add all theen-USTelligent Community 13Wed, 10 Nov 2021 14:01:21 GMThttps://devzone.nordicsemi.com/thread/338393?ContentTypeID=1Wed, 10 Nov 2021 14:01:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3a633410-b93a-4eed-9b93-fd9f525f9d31Amanda Hsieh<p>Hi,&nbsp;</p> <p>Sorry for the delay.</p> <p>The provisioner example always configures a node right after provisioning it. But before configuring a node, it initializes its Configuration Client so that it knows where to send messages. You can find this code here:&nbsp;<a title="https://github.com/nordicsemiconductor/nrf5-sdk-for-mesh/blob/master/examples/provisioner/src/node_setup.c#l659" href="https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/master/examples/provisioner/src/node_setup.c#L659" rel="noopener noreferrer" target="_blank">https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/master/examples/provisioner/src/node_setup.c#L659</a><span>&nbsp;Not sure if you initialize Configuration Client before trying to remove the subscription for the already configured nodes, but seems like it doesn&#39;t because the error code that it mentioned means invalid address. Most likely Configuration Client sends the message to a wrong destination, probably to the newly provisioned device.</span></p> <p><span>Regards,<br />Amanda</span></p><div style="clear:both;"></div>