We are using nordic SDK 16.0.0 and mesh SDK 4.2.0 with a nRF52840 chip.
Our products already have the provisioner/provisionee and config client/server implemented, based on the provisioner and light switch server examples.
We just learned what "composition data" is, a list of the models implemented by the device, that are sent to the config client so it knows what the features can be configured on the server device. The part where the node sends the composition data to the config client looks like it is implemented on my SDK version at least, but I could not find any parsing of this message on the config client side.
We are just using the node URI to choose the correct config scenario. This is very limited, as two firmware versions with the same URI but different models implemented don't benefit from the advantage of sending the composition data. Am I correct in my interpretation?
EDIT: Well, it looks like the handling of the composition data get message is done correctly on the config server side, since the nRF Mesh app on the smartphone can determine the model structure but commenting the NODE_SETUP_CONFIG_COMPOSITION_GET on CONFIG_SCENARIO_COMMON in config_scenarios.h and reprogramming the provisioner makes no difference as expected during the configuration phase. Has work started implementing something that parses the composition data on the config client side?
