Issues related to Matter over Thread product interfaces for reporting brightness changes to the APP

We are developing a light product that features a built-in button. A single click of this button toggles the light on/off, while a long press adjusts the brightness level.

If we manually adjust the brightness and then report the new brightness level via the Clusters::LevelControl::Attributes::CurrentLevel::Set() interface, this action triggers the MatterPostAttributeChangeCallback() command to set the brightness (which involves receiving commands for the transition from the current value to the target value).

Since our intent is solely to report the new brightness to the app without triggering a control command, this creates a conflict.

Is there an interface that allows us to only report the brightness state without subsequently receiving a dimming/setting command?

Parents
  • Hi,

    The MatterPostAttributeChangeCallback() function is always called when an attribute value is changed, and since the Set() function changes the CurrentLevel attribute, MatterPostAttributeChangeCallback() will be called.

    Can you clarify what you mean by MatterPostAttributeChangeCallback() triggering a control command? How have you implemented this function?

    Best regards,
    Marte

Reply
  • Hi,

    The MatterPostAttributeChangeCallback() function is always called when an attribute value is changed, and since the Set() function changes the CurrentLevel attribute, MatterPostAttributeChangeCallback() will be called.

    Can you clarify what you mean by MatterPostAttributeChangeCallback() triggering a control command? How have you implemented this function?

    Best regards,
    Marte

Children
Related