Version 2 - Roadmap Vote

[RubenKelevra]

I like to give myself, @basnijholt and everyone interested in the project an overview of what's planned for the next major release.

Given that development time is usually sparse, we like to get an idea on the usefulness for you. Completing all of these goals in our free time will take quite a while, so we like to not waste resources on the wrong end.

Please take your time and read every of the goals below and upvote them with ⬆️, if you would use/enjoy the feature and like us to focus on it (multiple choice!).

Feel free to leave us feedback on each of them, if you have specific needs or have some details and thoughts on what would be required to make the feature useful for you.

Thank you!

[RubenKelevra]

Simplify the user interaction as much as possible

The following issues have been closed because of this goal:

• Input Boolean for State of Adaptive Lighting #137

[th3w1zard1]

While this would make user interaction a bit easier, it would also create even more unnecessary entities.

Any end user can already do this themselves by creating their own template switch that calls adaptive_lighting.set_manual_control

[RubenKelevra]

Make it possible to override and adjust the automation without turning it off

The following issues have been closed because of this goal:

• Input Boolean for State of Adaptive Lighting #137
• rgb/xy color for min and max colour + sleep color. #150
• Add ability to switch to manual mode for only brightness #166
• Set light level before the light turns on #391

[RubenKelevra]

The idea is to make delta-sliders to allow raising or lower the current target brightness, shift the color temperature etc. for a room, while keeping the automation in place and adapting with the new delta value.

The delta can be reset by default on toggle or by default after an idle period slowly shift back to zero.

Similar goals (partly overlapping or dependent):

• Target brightness is covered here.
• Service calls to move the sunset back is covered here

[10bn]

Sry I'm not sure if I understood everything right thats planed for v2.
Question: I'm using homekit to interact with my smarthome.
Scenario: A light is off and I use homekit to turn it on and the command sent to HA is not just on/off eg. it includes a colortone and a specific brightness. With v2 will there be a way to override the usually applied color and brightness adjustments by adaptive lighting without turning al off?

[djurny]

Hi there,
As I understand and see it work, is that the "manual_control" will be set whenever brightness or color is changed within a certain amount.
A seperate manual_control (or defeat/override) for brightness and color would be great; this way one can dim the lights and still enjoy the color (temperature) changes throughout the day.
Groetjes,

[RubenKelevra]

If lights are turned on, they should start with the right color/brightness and not adjust afterwards (and avoid that they turn on after you turned them off ;)

Update: This is now implemented (in 1.19.0b2), light.turn_on calls are intercepted and immediately adjusted. Additionally, enable adapt_only_on_bare_turn_on: true to prevent adapting when manually turning on a light with brightness and color 🎉

The following issues have been closed because of this goal:

• Lights still change by A.L. #2
• Manual Control Not Being Declared For Various 'light.turn_on' Calls from Google Assistant and for Scenes #82
• Input Boolean for State of Adaptive Lighting #137
• Stuck brightness or color temperature #142
• Multiple errors in log #145
• Scenes do not trigger manual control anymore? #147
• adaptive lighting and motion sensors #167
• initial_transition and transition aren't working #168
• add delay before changing lights after turning on #174
• Remove transition when it is 0 (botches running transitions), or add possibility to remove it. #200
• Cannot turn off lights with long transition #201
• Manual Control Triggered by Adaptive Lighting  #209
• Sleep Transition #217
• Take over not working #224
• Lights turn on by themself #246
• Restore previous state of light when adaptive lighting is turned off #347
• Ignore lights being turned on with a specific color value and effects. #416

[daFreeMan]

So long as this doesn't eliminate the flexibility of having the lights fade on over time. When I get up in the winter and it's dark outside, I don't want the lights coming on at full blast, I want them to fade up over 30 or 60 seconds so my eyes have a chance to adjust. During the day, of course, coming on at the full, appropriate brightness makes sense.

Having AL be able to tell the difference (based on light sensors in the room or simply based on its own internal calculation of what the light setting should be), would be fantastic.

[th3w1zard1]

I tried implementing this myself but ran into a snag. Can anyone check #416 (comment) and recommend a solution?

[th3w1zard1]

I believe I've implemented this feature request correctly here: #528

If someone could test, that'd be great :)

You need to enable the config option ignore_turnon_with_custom_data to use it.

[basnijholt]

In the latest beta you can set adapt_only_on_bare_turn_on: true to instantly activate manual_control when calling light.turn_on with color or brightness.

Then since 1.19.0b0 lights will instantly turn to the right color and brightness when turning them on 🎉

[djurny]

Hi there,
With the intercepting of light.turn_on:

• Some bulbs, the off-to-on action will only result in a transition of brightness - as many would expect. (e.g. WiZ and LiFX bulbs/fixtures start from color_temp setpoint and only transitions brightness from 0 to setpoint.)
• Many Zigbee based bulbs (Philips Hue and Ikea TRADFRI), the off-to-on will result in both brightness and color_temp transition - as many would not expect. (e.g. the last set color_temp will be starting point of off-to-on transition.)

Request would be to also add a 'priming' of the color_temp for lights that support doing so. Currently with zigbee2mqtt the execute_if_off option and sending a color_temp with transition of 0 before the bulb is on, will make the off-to-on transition start from the color_temp setpoint, effectively resulting in no transition for color_temp.

This will give the same effect as intercepting the light.turn_on has on non-Zigbee bulbs on most (if not all) Ikea TRADFRI and Philips Hue bulbs.

This can also be achieved with dedicated scripts and dedicated buttons in home assistant, but I do not think this is a solution for most users.

Groetjes,

[RubenKelevra]

Switch from a brightness-percentage-goal to a target-brightness-in-lux-goal

The following issues have been closed because of this goal:

• rgb/xy color for min and max colour + sleep color. #150

[RubenKelevra]

Incorporate ambient brightness sensors per room as feedback method to adjust for uncontrolled light sources and natural light

The following issues have been closed because of this goal:

• rgb/xy color for min and max colour + sleep color. #150
• Adaptive lighting based on sensor instead of sun #412
• Enable dynamic offset for max brightness #352

[RubenKelevra]

So I created the idea (without room profiles) in HA automations natively, just to give an idea how this would look like.

This is the output of the PID-Controller, which gets it setpoint from an ambient light sensor outside, which provides a realtime brightness reading.

The target over the day is somewhat around 100 lx, but the ceiling light isn't capable of doing this on its own. So its ambient light mixed with artificial light to get to the 100 lx:

The output brightness setting of the PID-Controller:

And the brightness picked up by the sensor in the room:

As you can see it drops down at the evening, that's just because the light on it's own isn't strong enough to reach 100 lx in the corner where the light sensor is positioned.

If you're curious the room is around 20 qm and there are three lights in the ceiling fixture with 4.9 W (470 lm). The sensor used is a Xiaomi GZCGQ01LM.

[patrickcollins12]

Hey Ruben, thanks for this. Seems like an interesting proposal.

I'm not sure your proposal quite meets my needs. I might be an audience of 1, so I'm conscious that my needs might be different from others. Let me unpack it.

100 lux at night is very differen to 100 lux during the day. For a couple reasons. during the day I'm often trying to keep a minimal level of light if it gets very cloudy, but not waste energy when it is sunny. During the night I have different needs... I don't necessarily want the lights to be based on lux, I want them more based on mood or room. For instance, my Kitchen I always want bright, my Living Areas I deliberately want warm and dim except when the kids are doing homework and I'll manually crank up the brightness.

So for me, I like the current behaviour of Adaptive Lighting at night time. It works nicely. I create different AL integration for different groups of lights. They don't use the Lux sensor at night. My lux sensor is only used during the day to handle clouds.

So for me I would want the ability to change "modes" during a period of time. For instance "target a lux" during the day. Then follow a mood curve during night time irregardless of room lux. Transitioning between these modes is also critically important to prevent lights Jumping brightness.

[th3w1zard1]

This can currently be done by utilizing adaptive_lighting.change_switch_settings to update the min/max ct/rgb config options in an automation. If anybody needs help please reach out here.

[jcastro]

Just discovered this integration and I'm loving it already! Thanks everyone for the great work!

I was just thinking that would be nice to have support to take into consideration ambient light sensors that could work together with the sun elevation. This way we can get the right brightness if it's sunny outside but all your blinds are down, for example.

[tinnetju]

Hey @th3w1zard1 , I just saw your post here after creating in issue, but I have some trouble applying the changes using the adaptive_lighting.change_switch_settings service. Would you be able to have a look over at #785 ? Maybe this automation can be mixed and matched and included in the Readme as I can imagine more people will want a similar solution

[RubenKelevra]

Implement a method to calibrate lights for better matching colors and brightnesses

The following issues have been closed because of this goal:

• Use RGB mode only in sleep mode only #135
• RGB mode color tweaks / offset #226
• RGBW lights seem to be assumed to be cold white #169

[NateEaton]

A question about this one... I use AL for pretty much every light under automated control and for some, it works fine to have the max brightness at 100 or it's a light that is usually only on in the evening so have a max brightness at a lower percent works fine.

However, one of the lights is an under-cabinet Hue lightstrip in the kitchen. It comes up with motion activation any time we come into the kitchen, day or night. In daytime, it often provides enough extra light that we don't need the ceiling lamp on and having it on at night works great as a nightlight when ever midnight munchies strike. Anyway, for this light, I have max brightness set to 60% because any brighter is just too bright. But that means that the light curve is one that goes to minimum in middle of the night, ramps up through and beyond sunrise, then "maxes out" about mid-morning and that is the brightness any time it is on till mid-evening. The issue is that means in morning when we get up or at night before bed time (and before "sleep mode" gets turned on when we leave the front of the house), it is actually a bit brighter than I want. I could lower the max brightness to resolve that but then it wouldn't get as bright as I want it mid-day.

So the idea I came here to propose - one that I think this V2 idea may address - is to be able to set a max brightness (whether percentage or lux) and have AL smoothly ramp between min and max brightness instead of having a "flat top" to the light curve during the time the light is at max brightness.

Somewhere else on this git I saw a graph that showed the light curve cycling up and down and in the case where a max brightness below 100% is set, the top of each curve is chopped off. My proposal is that we have an option (which is why the idea of doing this with a "calibration" seems appealing) such that max meant what the max possible brightness the light can achieve but that in calculating the light curve AL would treat that max set for the device as 100% for the light switch.

Does that make sense?

Thanks,
Nate

[daFreeMan]

@NateEaton That makes perfect sense to me and I'd vote to support that idea if I could!

[RubenKelevra]

Make it possible to control binary lights and lights with fixed white points

[diamant-x]

This would be interesting. Not sure if already possible. Something like I declare my binary lights to be 'equivalent' to certain brightness % and colour Temperature. Then, if adaptivelight were to set the group above those values, then those lights are to be turned on. If adaptivelight should set it to lower brightness or color temp (hotter), then turn them off.

I have a mix of adjustable and fixed in my living room, and would love to be able to set them all together so the house knows when to turn off the binary lights in the room and leave only the adaptable one.

[RubenKelevra]

Dynamically switch between RGB/XY and White-Temperature mode to allow very cold and very warm tones outside the range of the White-Mode of lights

The following issues have been closed because of this goal:

• RGB mode color tweaks / offset #226
• rgb/xy color for min and max colour + sleep color. #150
• RGBWW support #289
• Proper support for WLED WWA (Cool White, Warm White, Amber) LED-strip #252

[I3lackshirts]

Not sure if this needs its own issue but having support for RGBW LEDS would also be great too. One of the use cases I could see is being able to define what W led type you have (Cool/Amber/Warm) and have the RGB LEDs generate a color opposite of the white and work in tandem to generate the correct temperature of lights.

Right now I don't use the color adjustment on my RGBW strips because the RGB control does not have a great temperature range. I get better results if I put the RGB in a "Warm White" mode (255,197,143) and adjust my white LEDS alone. (like around 130) EX RGBW(255,197,143,130) for a lower temp setting. Would be awesome if there was a way for AL to adjust the temperature overtime using a method like this.

[RubenKelevra]

Dynamically switch lights on and off to reach the desired brightness (to allow for very low brightness values, even if some lights cannot dim that low)

[RubenKelevra]

Allow for scenes with grouping of lights to allow for general purpose lights, area lights and accent / ambient lights and seamless switching between them

The following issues have been closed because of this goal:

• rgb/xy color for min and max colour + sleep color. #150
• Add ability to switch to manual mode for only brightness #166

[RubenKelevra]

Integrate a simple triggers to turn on/off lights based on binary inputs, like motion sensors and device usage like TVs

The following issues have been closed because of this goal:

• adaptive lighting and motion sensors #167

[RubenKelevra]

Allow dynamic input via a sensor of RGB values or White-Temperatures + Brightness for mirroring the natural light conditions outside (for example for rooms without or low natural light)

The following issues have been closed because of this goal:

• Add a more natural light curve as an option #133
• Sunrise and sunset times #182

[dekiesel]

This looks very cool @RubenKelevra!

Do you have some kind of writeup somewhere so that I can give this a try?

[RubenKelevra]

@dekiesel wrote:

This looks very cool @RubenKelevra!

Do you have some kind of writeup somewhere so that I can give this a try?

Nope, but I'm happy to share the automations as soon as I'm home.

But you gonna need this or a similar sensor :)

[dekiesel]

Thanks! I was eyeing one of those anyway :)

[RubenKelevra]

So there are multiple types of automations:

Input automations store the data in helper variables:

• Calculate Brightness from Ambience.yaml.txt
• Save Light Temperature from Ambience.yaml.txt

(1800 K is the minimum, 6500K the maximum my lights support - so I cut the values off there)

Switch between RGB and temperature mode (via setting an input_select helper)

• Switch from RGB to Temperature and back based on brightness.yaml.txt

Main Light Automations (these are the ones shown in the dashboard as toggles)

• Adapt Light Brightness from Ambient.yaml.txt
• Adapt Light RGB color from Ambient.yaml.txt
• Adapt Light Temperature from Ambient.yaml.txt

Helpers:

• adapted_ambience_illumination (type: number, min: 4, max: 255, step: 1, unit of measurement: points)
• adapted_ambience_light_temperature (type: number, min: 1800, max: 6500, step: 1, unit of measurement: K)
• adaption mode (type: dropdown, options: 'rgb, temperature, off')

Dashboard:

  - theme: Backend-selected
    title: Light Adaption to Ambient
    path: light-adaption-to-ambient
    badges: []
    cards:
      - type: horizontal-stack
        cards:
          - type: entity
            entity: light.ambient_light_sensor_white_led
            name: Sensor Bulb
            state_color: true
          - type: gauge
            entity: sensor.ambient_light_sensor_illuminance
            max: 1000
            needle: true
          - type: gauge
            entity: sensor.ambient_light_sensor_color_temperature
            max: 8100
            min: 1500
            needle: true
            segments:
              - from: 1450
                color: '#FF6C00'
              - from: 1550
                color: '#FF7300'
              - from: 1650
                color: '#FF7900'
              - from: 1750
                color: '#FF7E00'
              - from: 1850
                color: '#FF8400'
              - from: 1950
                color: '#FF890E'
              - from: 2050
                color: '#FF8E1B'
              - from: 2150
                color: '#FF9227'
              - from: 2250
                color: '#FF9732'
              - from: 2350
                color: '#FF9B3D'
              - from: 2450
                color: '#FF9F46'
              - from: 2550
                color: '#FFA34F'
              - from: 2650
                color: '#FFA757'
              - from: 2750
                color: '#FFAA5F'
              - from: 2850
                color: '#FFAE67'
              - from: 2950
                color: '#FFB16E'
              - from: 3050
                color: '#FFB475'
              - from: 3150
                color: '#FFB87B'
              - from: 3250
                color: '#FFBB81'
              - from: 3350
                color: '#FFBE87'
              - from: 3450
                color: '#FFC18D'
              - from: 3550
                color: '#FFC392'
              - from: 3650
                color: '#FFC697'
              - from: 3750
                color: '#FFC99D'
              - from: 3850
                color: '#FFCBA1'
              - from: 3950
                color: '#FFCEA6'
              - from: 4050
                color: '#FFD0AB'
              - from: 4150
                color: '#FFD3AF'
              - from: 4250
                color: '#FFD5B3'
              - from: 4350
                color: '#FFD7B7'
              - from: 4450
                color: '#FFDABB'
              - from: 4550
                color: '#FFDCBF'
              - from: 4650
                color: '#FFDEC3'
              - from: 4750
                color: '#FFE0C7'
              - from: 4850
                color: '#FFE2CA'
              - from: 4950
                color: '#FFE4CE'
              - from: 5050
                color: '#FFE6D1'
              - from: 5150
                color: '#FFE8D5'
              - from: 5250
                color: '#FFEAD8'
              - from: 5350
                color: '#FFECDB'
              - from: 5450
                color: '#FFEDDE'
              - from: 5550
                color: '#FFEFE1'
              - from: 5650
                color: '#FFF1E4'
              - from: 5750
                color: '#FFF3E7'
              - from: 5850
                color: '#FFF4EA'
              - from: 5950
                color: '#FFF6ED'
              - from: 6050
                color: '#FFF8F0'
              - from: 6150
                color: '#FFF9F2'
              - from: 6250
                color: '#FFFBF5'
              - from: 6350
                color: '#FFFDF8'
              - from: 6450
                color: '#FFFEFA'
              - from: 6550
                color: '#FFFFFF'
              - from: 6650
                color: '#FEF9FF'
              - from: 6750
                color: '#FAF6FF'
              - from: 6850
                color: '#F6F4FF'
              - from: 6950
                color: '#F3F2FF'
              - from: 7050
                color: '#F0F0FF'
              - from: 7150
                color: '#EDEFFF'
              - from: 7250
                color: '#EAEDFF'
              - from: 7350
                color: '#E8ECFF'
              - from: 7450
                color: '#E6EBFF'
              - from: 7550
                color: '#E4EAFF'
              - from: 7650
                color: '#E2E9FF'
              - from: 7750
                color: '#E0E8FF'
              - from: 7850
                color: '#DFE7FF'
              - from: 7950
                color: '#DDE6FF'
              - from: 8050
                color: '#DCE5FF'
          - type: gauge
            entity: input_number.adapted_ambience_illumination
            max: 255
            min: 1
            unit: ' '
            needle: true
            name: brightness
      - type: horizontal-stack
        cards:
          - show_name: true
            show_icon: true
            type: button
            tap_action:
              action: toggle
            entity: automation.adapt_light_temperature_from_ambient
            icon: mdi:sun-thermometer
            icon_height: 60px
            name: Adapt Temperature
          - show_name: true
            show_icon: true
            type: button
            tap_action:
              action: toggle
            entity: automation.adapt_light_rgb_color_from_ambient
            icon: mdi:format-color-fill
            icon_height: 60px
            name: Adapt RGB
          - show_name: true
            show_icon: true
            type: button
            tap_action:
              action: call-service
              service: input_select.select_next
              data: {}
              target:
                entity_id: input_select.adaption_mode
            entity: input_select.adaption_mode
            show_state: true
            icon: mdi:vector-difference
            icon_height: 60px
          - show_name: true
            show_icon: true
            type: button
            tap_action:
              action: toggle
            entity: automation.adapt_light_brightness_from_ambient
            name: Adapt Brightness
            icon_height: 60px
      - type: horizontal-stack
        cards:
          - type: gauge
            entity: sensor.ambient_light_sensor_red_channel_relative
            name: Red
            needle: true
            severity:
              green: 300
              yellow: 200
              red: -2
            min: 1
            max: 100
          - type: gauge
            entity: sensor.ambient_light_sensor_green_channel_relative
            name: Green
            needle: true
            severity:
              green: 1
              yellow: 200
              red: 300
            min: 1
            max: 100
          - type: gauge
            entity: sensor.ambient_light_sensor_blue_channel_relative
            needle: true
            name: Blue
            min: 1
            max: 100
          - type: gauge
            entity: sensor.ambient_light_sensor_clear_channel
            name: Light

LMK if something is missing.

[RubenKelevra]

With the newly released version of ESPHome the sensor should now auto-change the integration time and gain and receive better accuracies!

Thanks @swifty99 for this! :)

esphome/esphome#3258 (comment)

[RubenKelevra]

Create dynamic "movie"-like scenes with different frames of color, brightness, temperature to simulate sunset / sunrise events (and similar)

The following issues have been closed because of this goal:

• Ability to set sunrise latest time rather than fixed or offset #225
• Sleep mode not working after recent HACS update #134
• rgb/xy color for min and max colour + sleep color. #150
• Sunrise and sunset times #182

[RubenKelevra]

New icon

A friend is designing a new icon for this project which will be 42 pixels square and meant to be pixel art in higher resolutions.

The general idea is to make a light bulb that shows the different states of color temperature over the day in one half plus a sun. And for the night the different color temperatures as well (blue hour etc) and stars + moon.

Hope you like the idea @basnijholt

The following issues have been closed because of this goal:

• New Icon #243

[RubenKelevra]

Move "config" switches and variables to the new config section in HA

The following issues have been closed because of this goal:

• Set entity_category for generated switches to 'config' #241

[th3w1zard1]

@stefanroelofs can you explain this feature again? I'm not exactly sure why classifying it as an entity_category is necessary or useful.

[stefanroelofs]

I'm sorry, but please read my original issue (#241).
I don't think I can explain it any further.
Thanks for your time anyway!

[gravityrebel]

To expand on this, would it be possible to add has_entity_name? The category is useful to me to programmatically pull off the main switch entity. But as it is the integration makes it hard to determine programmatically which switch entity is associated with what purpose. A goal would be to get more information exposed at the device level.

[RubenKelevra]

[ DONE! ] Allow simple overwrites of sunrise/sunset with fixed times or deltas with service calls and instant "sunrise/sunset" events

The idea is to simplify the integration of sleep tracking alarm clocks etc. with morning wakeups as well as automate the "sunset" to fit the sleep rhythm dictated by the alarm clock.

The following issues have been closed because of this goal:

• Ability to set sunrise latest time rather than fixed or offset #225

[10bn]

What about variables for these values which can change dynamically by users' other automations? Could that be an option too?

[RubenKelevra]

Not sure what the difference would be. I mean if you want to change the next sunrise, you call the service and overrides it.

If you don't override it the default will be used.

What would be the benefit of a variable? 🤔

[10bn]

I was thinking of the helpers HA provides and an option to add them from the GUI like you can in some blueprints...

[josh-hemphill]

When trying to add controls to dashboards to control the sunrise or sunset times across areas, I have to set up intermediate helpers and automations just to try and sync them, having a variable would be very nice.

[zebrahosting]

Is there a way (and if not than consider it a request) to trigger an update to all lights?
I am having hardware switched connected to Shelly 4 PM's everywhere so updates can only apply when switched on. Now it takes a long time for some lights to correct. I I could trigger with a Shelly.click event it could adapt the lights on startup. (plus the time they take to connect to HA)

[th3w1zard1]

You can do this with an automation inside of HASS I believe.