-
-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Matter light control behavior #106190
Comments
Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) matter documentation |
Thanks for reporting and your investigation for the solution. I'll do my best to fix it as soon as possible. |
Sorry, did not yet have a chance to look at this due to the holiday season. I will pick it up next week. |
The problem
Action: Selecting a color for a matter light bulb when light bulb is off
Observed behavior: Light turns on, but does not change to selected color. To change colors, a second command is required
Expected behavior: Light turns on with the selected color without requiring a second command, which would be more inline with the existing brightness command behavior (moving to a brightness when the bulb is off results in the bulb turning on at a specific brightness without the need for two commands).
Additional context: The current matter implementation uses
MoveToLevelWithOnOff
which results in the expected brightness behavior when the light bulb is off (the light bulb turns on to the specified brightness). While theLevelControl
cluster offers bothMoveToLevel
(which would turn on the bulb and ignore the brightness -- similar to the existing issue with the color command) andMoveToLevelWithOnOff
, theColorControl
cluster does not offer "withOnOff" commands. Instead, anoptionsMask
andoptionsOverride
can be supplied, corresponding to the bit forExecuteIfOff
which fixes this behavior:This enables corresponds to the
ExecuteIfOff
bit in theOptionsBitmap
.Proposed action: Add
optionsMask=1
andoptionsOverride=1
toColorControl
commands.What version of Home Assistant Core has the issue?
2023.12.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Matter
Link to integration documentation on our website
https://www.home-assistant.io/integrations/matter/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: