Skip to content
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

Per light color temperature settings #29

Open
julianrinaldi opened this issue Jun 17, 2019 · 6 comments
Open

Per light color temperature settings #29

julianrinaldi opened this issue Jun 17, 2019 · 6 comments

Comments

@julianrinaldi
Copy link

Being able to set a min/max color temperature per light would be very useful. While working in my office I like to have my lights at 5500K max. While I would only want my kitchen lights to get up to ~3500K.

@claytonjn
Copy link
Owner

This has been requested a few times (most recently in January, starting here), but I'm very hesitant to implement it. The whole point of Circadian Lighting is to help your body maintain a constant and natural circadian rhythm. Having lights at different temperatures in different rooms of the house would completely eliminate any benefit of adjusting the color temperature based on the sun's position.

I'm not going to close the issue because I have no problem making the change if someone can provide a compelling reason to do so.

@Djelibeybi
Copy link

Different smart bulbs (even from the same manufacturer) have different min/max kelvin values, which may be a somewhat compelling reason for adding this functionality.

For example, the LIFX colour bulbs generally have a range from 2500K to 9000K while the Day/Dusk (i.e. temperature change only) can do 1500K to 4000K.

Having this option would mean you're not restricted to the lowest common denominator temperature range of the least capable bulb. :)

@Joshfindit
Copy link

Joshfindit commented Sep 24, 2019

Would it be possible to change the lights with a homeassistant automation or a custom sensor that does the math you’re looking for?

That way the circadian addon would not have to be modified to do what you want.

@avdz
Copy link

avdz commented Nov 14, 2019

Different smart bulbs (even from the same manufacturer) have different min/max kelvin values, which may be a somewhat compelling reason for adding this functionality.

For example, the LIFX colour bulbs generally have a range from 2500K to 9000K while the Day/Dusk (i.e. temperature change only) can do 1500K to 4000K.

Having this option would mean you're not restricted to the lowest common denominator temperature range of the least capable bulb. :)

+1 for this reason.
Personally I have the same issue with the brightness. My LED strip in my sleeping room is not as powerful as in the living. This means that the brightness in my sleeping room is usually just too low.

@mouth4war
Copy link
Contributor

mouth4war commented Dec 24, 2019

@claytonjn for the love of logic, if you have min/max brightness per switch then why not color temp? Both are used for delivering circadian lighting and either both should be tweakable per switch or neither :)

Edit: We already have sleep_colortemp per switch as well, why not min and max too?

How about we retain the min and max colortemp on main component level for calculations (and min can be set to the lowest possible color temp across all lights). Then, each switch can have its own range. When adjusting, if the desired color temp falls out of the switch's range, just bind to the switch's min and max values.

So, the lights that can go low (say 1700K) will go that low and the rest will stop at 2700K or 3000K.

@mouth4war
Copy link
Contributor

mouth4war commented Dec 27, 2019

https://github.com/claytonjn/hass-circadian_lighting/blob/5f9cb61ed0844fb8725957036514821ad747c4fb/custom_components/circadian_lighting/switch.py needs testing @julianrinaldi @Djelibeybi @avdz

min_colortemp and max_colortemp are available per switch (and initial_transition as well).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants