Allow disabling CT and brightness adjustment individually
See original GitHub issueCurrently, if a CL switch is configured to adjust both color temperature and brightness, the CL toggle switch and the disable_state
disables all adjustment (both color temperature and brightness). It would be nice to be able to dynamically enable/disable just color temperature or brightness - for example, you may want the option to turn brightness up for certain tasks while still maintaining the proper color temperature.
This can technically be accomplished already by configuring a “color temperature” CL switch (with disable_brightness_adjust
set to true) and a “brightness” CL switch (with lights included under lights_brightness
). While this works, it doubles the amount of service calls when both are on.
The ideal solution should be to create a new type of entity (i.e. cl_group
) with two toggles (color temperature and brightness), if both are configured. This would also mean creating a custom entity-row for Lovelace.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:9 (3 by maintainers)
Top GitHub Comments
Oh, gotcha - you mean you need to know what the proper brightness for the end of the ramp-up time would be.
I use Sleep as Android as an alarm clock and it directly pairs to my Hue bridge to brighten my nightstand lamp with my alarm. It also ties in with Tasker which I have connected to Home Assistant. So basically; when the house is in “sleep” mode I turn off Circadian Lighting for the bedroom lights, when the alarm clock goes off it slowly brightens my nightstand lamp, when I dismiss my alarm Home Assistant leaves “sleep” mode and Circadian Lighting is turned on for the bedroom lights, adjusting them to the proper settings.
+1