Hello,
I’m working with the Matter Light Bulb sample in nRF Connect SDK v3.0.0, and I’ve run into build issues when enabling certain optional commands in standard clusters using the ZAP GUI—that is, commands not marked as required in the GUI.
For instance, when I enable the MoveToClosestFrequency command in the LevelControl cluster, the build fails with the following error:
undefined reference to `emberAfLevelControlClusterMoveToClosestFrequencyCallback(...)`
I traced the error and found that this command is not defined in level-control.cpp, even though other LevelControl commands (like MoveToLevel, Step, etc.) are defined there. I’ve verified that this issue isn’t limited to just one cluster—I've encountered similar errors when enabling other optional commands across different standard clusters.
I'd appreciate clarification on the following:
- Is it expected behavior that enabling optional (non-required) commands in ZAP requires manually defining their callbacks?
- Is there a recommended approach or template for adding these missing callback implementation.
Thanks,
Suhas