How is CONFIG_OPCODE_COMPOSITION_DATA_GET handled by a Bluetooth mesh server?

[SørenHN]

I am writing a bluetooth mesh application with a server and client. Provisioning is working, but the configuration of the server is giving me problems.

I have based my application on the Light Switch example from the Mesh SDK v0.10 and can't seem to figurer out how the configuring is handled on the server.

When calling config_client_composition_data_get() from the client, the configuration times out.

How does the server handle the CONFIG_OPCODE_COMPOSITION_DATA_GET message? Is it handled by one the deeper layers or should the application handle the answering? And what could course this error?

Edit 1: After some testing, it seems like the provisioner might be the cause of the problem. Are there anything I should be aware of before calling config_client_composition_data_get() from the provisioner? Like any variables that should absolutely be set before the function call?

Edit 2: After some further testing I am now very sure it is the provisioner who is not sending the message. How do i test what goes wrong in the provisioner? And again, what could the problem be?

[SørenHN]

Have you made sure the publication address of the client when you call config_client_composition_data_get() matches with the unicast address of the server ?

Thank you for this question. I tried to use address 0x0001.

In the light switch example a UNPROV_START_ADDRESS of 0x0100 is used instead as the first address. After changing to 0x0100 it seems work.

@Hung Bui, can you give a short description of why 0x0001 cannot be used as an unicast address? I can't seem to find any information on this topic.