Hi, thank you so much for your awesome support!
It seems to be working correctly with the test version. Here are the same screenshots as before.
Thanks again!
This is actually already possible, but requires some setup.
In the app settings, you can disable color temperature and brightness control separately per light, just open the light’s settings by tapping on the name. So for your living room lights, you could simply disable the brightness control while keeping the color temperature adjustment active. And in a recent update I added flow cards that let you do this per zone in one go.
Thanks for the kind words, and glad you’re enjoying the app! 
Ahh, ok, die einstellung hab ich übersehen, damit ist mein problem gelöst, super, danke
Hm, you are right, I’m even not sure how to get this implemented in universal way and yep, I was thinking it’s probably the Yeelights capability only ;-(
Actually let me see how it would work even with Night mode enabled. Night mode is basically a mode, where “you should only see where you walk”, but you will not wake up anyone by this strong light 
update so no go, for some reason it always resets the Night mode, so will pass unfortunately, even though I like the app and it’s functionalities and setup.
Perhaps I don’t understand how this app is supposed to work. I’m trying to run it on a single Govee COB Light Strip with an advertised color temperature range of 2700-6500K.
I set the range of color in the Adaptive Lighting app to go from 2700K to 3000K just to see an extra warm version of light in a test. I built a flow that simply turns on the light strip, then Resumes Color and Brightness control in the Adaptive Lighting app.
When the control resumes, the Adaptive Lighting app cranks the Light Strip’s color temperature to the coolest possible setting in the Homey Pro color temperature wheel, despite me having set a max color temperature of 3000K. It also shows a color temperature override in the Adaptive Lighting app settings which I thought was meant to show that the color temperature was overridden by manual control in the app. But it wasn’t because I had started with the Light Strip manually configured to display the warmest possible color available in the Homey Pro color temperature wheel. The only thing overriding that is the Adaptive Lighting app which is overriding the color temperature to the highest possible setting…far beyond the limits I set in it’s configuration page. What’s going on here?
Hi there,
Thanks for the detailed description, I think there’s indeed a misunderstanding of what the per-device Kelvin range setting does.
The per-device min/max Kelvin is not an operating range limiter. It tells the app what color temperatures your physical hardware actually supports, so that Homey’s internal 0-1 scale can be correctly mapped across all your lights. A light with a 2700-6500K range and one with a 2200-4000K range will both display the same “3000K” because each has its own mapping.
When you entered 2700-3000K there, you told the app “this light’s hardware only spans 2700-3000K.” So when the circadian algorithm outputs anything above 3000K during the day, it clamps to 3000K and maps that to 0.0 on your declared scale - which is the cool/max end of what you said the device supports. That’s why it jumps to the coolest setting.
To limit the temperature range the app actually uses, change the global min/max Kelvin in the system settings, and not the per-device range. For a very warm look, try something like global max 3000K. Keep your Govee’s per-device range set to its actual advertised hardware range of 2700–6500K.
I do acknowledge this is confusing, and I’ll be adding clearer hints and descriptions to the settings in an upcoming version of the app to make the distinction more obvious.
Hi there,
first of all, thank you for the great app! 
I’m using Hue bulbs and, like the previous user, I was also confused at first and didn’t understand the setting correctly. I think this is also a UX issue:
When I change the global min/max Kelvin values, the same values are also shown in the min/max fields of the individual lamps. This makes it look like both settings are the same thing, or that the global setting simply overwrites the per-device setting. As a user, that strongly suggests that the per-device fields are meant to limit the usable range as well.
Now I understand that the per-device Kelvin range should describe the actual hardware capabilities of the light, while the global min/max Kelvin settings define the range the app should actually use. But the current UI makes this distinction quite hard to understand.
And sorry — I also didn’t read the manual.
One question remains for me: what would be the correct way to handle different desired limits for different lamps?
For example:
- Lamp A should never go above 3000K
- Lamp B should be allowed to go up to 4000K
Is this possible in the current version, or is per-lamp “usable range limiting” not supported yet?
Thanks again!
Thanks for your message, I hope to find the time in the near future to improve the app and make it clearer.
One question remains for me: what would be the correct way to handle different desired limits for different lamps?
Currently this is not possible, as this is not really the idea behind the app. It’s meant to make sure all lamps are approximately the same colour temperature throughout the house and day.
I’m not entirely sure if or when I’ll add that functionality. If you do want to achieve this, the other circadian lighting app might be a better fit, as you can create multiple circadian zones. So also one for just a particular light.
Hi there,
thank you for your reply!
And just to make that clear: I already find the app very useful, especially because it basically works without having to create flows for everything. That’s really nice.
I noticed one more thing this evening and I’m not sure whether I’m misunderstanding something again.
For example, for my dining table light I entered the min/max values correctly according to the actual hardware range of the lamp. At that moment, the target value shown by the app was 3200K. However, the actual value of the lamp was 2600K.
Then I moved the offset slider. The target value stayed at 3200K, which makes sense to me if the original value before the cut-off was still above 3200K. But the actual value of the lamp changed when I moved the offset.
Can you explain why that happens?
Thanks again!
Hi again,
I hope I’m not getting annoying yet.
I noticed one more thing: when I change the global min/max temperature values, it does not seem to have any effect on the color temperature of my lamp. The lamp always ends up with the same color temperature.
Only when I change the min/max values directly in the individual lamp settings do I get a different color temperature.
So to me it looks as if the global min/max values are not being taken into account for the actual output calculation.
In the “Current target values” display and in the curve, everything seems to be calculated and shown correctly. But the global min/max settings do not change the actual output value of the lamp.
Thanks for detailed testing, not annoying at all.
after some setting changes, app did not immediately resync managed lights and instead waited for next sync cycle. That made changes like global min/max Kelvin look like they were not affecting light output.
This is now fixed in new test release, so these settings changes should update lights right away.
The app tries to back off when it notices that a light has been updated by something other than itself, for example, when a flow or a user interacts with the light directly. This is done so that the adaptive lighting system won’t fight other automations or user behaviour. This pause will be reset when the light is turned off.
So you’ve most likely have another flow, that changes the temperature of the lights. In the general section of the app settings, you can find the logs of the app, which could help you identify when the temperature control is paused.
Love the app and have it implemented for about 20 lights right now. I have a question and an idea for a feature:
First the question: If I set a minimum dim value does that impact the rate of change of the dimming? So does it take the minimum value as the new bottom of the curve or does it just dim along the original curve and remain constant until the intensity raises above the minimum again?
The feature request: When I turn on my lights I want them do slowly fade in to the current (adaptive) setting. Homey can’t do transitions by default by you can do them via an app like Transitions, but that app doesn’t take the adaptive bit into account. Would be cool to be able to combine the functions.
