https://devzone.nordicsemi.com/f/nordic-q-a/28487/mesh-configuration---sending-composition-data-failsI have asked about this before . But after working more on the project, it seems the solution i found before actually didn&#39;t solve the problem. Hence I am asking again. After provisioning a mesh server and calling config_client_composition_data_geten-USTelligent Community 13Tue, 14 Nov 2017 16:51:02 GMThttps://devzone.nordicsemi.com/thread/112686?ContentTypeID=1Tue, 14 Nov 2017 16:51:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a3e8f8ef-4baa-434b-bbcf-1bc10ccf9c71S&#248;renHN<p>Hi Hung Bui.</p> <p>Thank you for the answer. The problem has somehow been resolved, and i am not sure how... maybe magic? I haven&#39;t made any significant changes to the code but. I flashed another program to the chip before trying again and it seems to have fixed the error.</p> <p>But thank you for the help anyway.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/112685?ContentTypeID=1Tue, 14 Nov 2017 12:06:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:43fc2c48-b9ba-43d9-b3d2-af1ce851f5d9Hung Bui<p>Hi Søren,</p> <p>When you are handling handle_composition_data_get() on the server, what was the source address and destination address inside access_message_rx_t * p_message ? When you reply and then end up in the packet_tx I don&#39;t think it would be a problem if non_virtual_address_handle_get() returns DSM_HANDLE_INVALID . The reason is that, that address is not the dsm address list. So it&#39;s normal to get DSM_HANDLE_INVALID. But I don&#39;t think it would be a problem when sending packet. The mesh stack will just simply send the packet using the src address in the rx message data. Have you checked all the way until nrf_mesh_packet_send() inside packet_tx() ?</p><div style="clear:both;"></div>