[BUG] Incorrect handling of MoveColorTemperature and StepColorTemperature when ColorTemperatureMaximum is 0 · Issue #33903 · project-chip/connectedhomeip · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have found the issue regarding MoveColorTemperature and StepColorTemperature. If the light receives the above command and ColorTemperatureMaximum is 0, the light will not take any action. The light should adjust its color temperature value according to the spec description.
ColorTemperatureMinimumMireds Field
If the ColorTemperatureMinimumMireds field is set to 0, ColorTempPhysicalMinMireds SHALL
be used as the lower bound for the ColorTemperatureMireds attribute.
ColorTemperatureMaximumMireds Field
If the ColorTemperatureMaximum Mireds field is set to 0, ColorTempPhysicalMaxMireds
SHALL be used as the upper bound for the ColorTemperatureMireds attribute.
Reproduction steps
We have found the issue regarding MoveColorTemperature and StepColorTemperature. If the light receives the above command and ColorTemperatureMaximum is 0, the light will not take any action. The light should adjust its color temperature value according to the spec description.
But the SDK currently does not handle ColorTemperatureMaximum is 0.
https://github.com/project-chip/connectedhomeip/blob/master/src/app/clusters/color-control-server/color-control-server.cpp#L2700
https://github.com/project-chip/connectedhomeip/blob/master/src/app/clusters/color-control-server/color-control-server.cpp#L2811
Bug prevalence
100%
GitHub hash of the SDK that was being used
d83caf7
Platform
core
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: