đ Adaptive Lighting: Enhance Your Home's Atmosphere with Smart, Sun-Synchronized Lighting đ
Adaptive Lighting is a custom component for Home Assistant that intelligently adjusts the brightness and color of your lights
Download and install directly through HACS (Home Assistant Community Store)
By automatically adapting the settings of your lights throughout the day, Adaptive Lighting helps maintain your natural circadian rhythm
In addition to its regular mode, Adaptive Lighting also offers a "sleep mode"
[ToC]
đĄ Features
Adaptive Lighting provides four switches (using "living_room" as an example component name):
switch.adaptive_lighting_living_room
: Turn Adaptive Lighting on or off and view current light settings through its attributes.switch.adaptive_lighting_sleep_mode_living_room
: Activate "sleep mode"đ´ and set custom sleep_brightness and sleep_color_temp.switch.adaptive_lighting_adapt_brightness_living_room
: Enable or disable brightness adaptationđ for supported lights.switch.adaptive_lighting_adapt_color_living_room
: Enable or disable color adaptationđ for supported lights.
đī¸ Regain Manual Control
Adaptive Lighting is designed to automatically detect when you or another source (e.g., automation) manually changes light settings adaptive_lighting.set_manual_control
service call.
This feature is available when take_over_control
is enabled.
Additionally, enabling detect_non_ha_changes allows Adaptive Lighting to detect all state changes, including those made outside of Home Assistant, by comparing the light's state to its previously used settings.
The adaptive_lighting.manual_control
event is fired when a light is marked as "manually controlled," allowing for integration with automations
đ Table of Contents
âī¸ Configurationđ¤ Automation examples- Additional Information
đ Troubleshootingđ Graphs!đ See alsođĨ Contributors
âī¸ Configuration
Adaptive Lighting supports configuration through both YAML and the frontend (Configuration -> Integrations -> Adaptive Lighting, Adaptive Lighting -> Options), with identical option names in both methods.
# Example configuration.yaml entry
adaptive_lighting:
lights:
- light.living_room_lights
Transform your home's atmosphere with Adaptive Lighting
đ Options
All of the configuration options are listed below, along with their default values. The YAML and frontend configuration methods support all of the options listed below.
Variable name | Description | Default | Type |
---|---|---|---|
lights |
List of light entity_ids to be controlled (may be empty). |
[] |
list of entity_id s |
prefer_rgb_color |
Whether to prefer RGB color adjustment over light color temperature when possible. |
False |
bool |
include_config_in_attributes |
Show all options as attributes on the switch in Home Assistant when set to true . |
False |
bool |
initial_transition |
Duration of the first transition when lights turn from off to on in seconds. |
1 |
float 0-6553 |
sleep_transition |
Duration of transition when "sleep mode" is toggled in seconds. |
1 |
float 0-6553 |
transition |
Duration of transition when lights change, in seconds. |
45 |
float 0-6553 |
transition_until_sleep |
When enabled, Adaptive Lighting will treat sleep settings as the minimum, transitioning to these values after sunset. |
False |
bool |
interval |
Frequency to adapt the lights, in seconds. |
90 |
int > 0 |
min_brightness |
Minimum brightness percentage. |
1 |
int 1-100 |
max_brightness |
Maximum brightness percentage. |
100 |
int 1-100 |
min_color_temp |
Warmest color temperature in Kelvin. |
2000 |
int 1000-10000 |
max_color_temp |
Coldest color temperature in Kelvin. |
5500 |
int 1000-10000 |
sleep_brightness |
Brightness percentage of lights in sleep mode. |
1 |
int 1-100 |
sleep_rgb_or_color_temp |
Use either "rgb_color" or "color_temp" in sleep mode. |
color_temp |
one of ['color_temp', 'rgb_color'] |
sleep_color_temp |
Color temperature in sleep mode (used when sleep_rgb_or_color_temp is color_temp ) in Kelvin. |
1000 |
int 1000-10000 |
sleep_rgb_color |
RGB color in sleep mode (used when sleep_rgb_or_color_temp is "rgb_color"). |
[255, 56, 0] |
RGB color |
sunrise_time |
Set a fixed time (HH:MM:SS) for sunrise. |
None |
str |
max_sunrise_time |
Set the latest virtual sunrise time (HH:MM:SS), allowing for earlier real sunrises. |
None |
str |
sunrise_offset |
Adjust sunrise time with a positive or negative offset in seconds. |
0 |
int |
sunset_time |
Set a fixed time (HH:MM:SS) for sunset. |
None |
str |
min_sunset_time |
Set the earliest virtual sunset time (HH:MM:SS), allowing for later real sunsets. |
None |
str |
sunset_offset |
Adjust sunset time with a positive or negative offset in seconds. |
0 |
int |
only_once |
Adapt lights only when they are turned on (true ) or keep adapting them (false ). |
False |
bool |
take_over_control |
Disable Adaptive Lighting if another source calls light.turn_on while lights are on and being adapted. Note that this calls homeassistant.update_entity every interval ! |
True |
bool |
detect_non_ha_changes |
Detect non-light.turn_on state changes and stop adapting lights. Requires take_over_control . |
False |
bool |
separate_turn_on_commands |
Use separate light.turn_on calls for color and brightness, needed for some light types. |
False |
bool |
send_split_delay |
Delay (ms) between separate_turn_on_commands for lights that don't support simultaneous brightness and color setting. |
0 |
int 0-10000 |
adapt_delay |
Wait time (seconds) between light turn on and Adaptive Lighting applying changes. Might help to avoid flickering. |
0 |
float > 0 |
autoreset_control_seconds |
Automatically reset the manual control after a number of seconds. Set to 0 to disable. |
0 |
int 0-31536000 |
skip_redundant_commands |
Skip sending adaptation commands whose target state already equals the light's known state. Minimizes network traffic and improves the adaptation responsivity in some situations. Disable if physical light states get out of sync with HA's recorded state. | False |
bool |
Full example:
# Example configuration.yaml entry
adaptive_lighting:
- name: "default"
lights: []
prefer_rgb_color: false
transition: 45
initial_transition: 1
interval: 90
min_brightness: 1
max_brightness: 100
min_color_temp: 2000
max_color_temp: 5500
sleep_brightness: 1
sleep_color_temp: 1000
sunrise_time: "08:00:00" # override the sunrise time
sunrise_offset:
sunset_time:
sunset_offset: 1800 # in seconds or '00:15:00'
take_over_control: true
detect_non_ha_changes: false
only_once: false
đ ī¸ Services
adaptive_lighting.apply
adaptive_lighting.apply
applies Adaptive Lighting settings to lights on demand.
Service data attribute | Description | Required | Type |
---|---|---|---|
entity_id |
The entity_id of the switch with the settings to apply. |
list of entity_id s |
|
lights |
A light (or list of lights) to apply the settings to. |
list of entity_id s |
|
transition |
Duration of transition when lights change, in seconds. |
float 0-6553 |
|
adapt_brightness |
Whether to adapt the brightness of the light. |
bool | |
adapt_color |
Whether to adapt the color on supporting lights. |
bool | |
prefer_rgb_color |
Whether to prefer RGB color adjustment over light color temperature when possible. |
bool | |
turn_on_lights |
Whether to turn on lights that are currently off. |
bool |
adaptive_lighting.set_manual_control
adaptive_lighting.set_manual_control
can mark (or unmark) whether a light is "manually controlled", meaning that when a light has manual_control
, the light is not adapted.
Service data attribute | Description | Required | Type |
---|---|---|---|
entity_id |
The entity_id of the switch in which to (un)mark the light as being manually controlled . |
list of entity_id s |
|
lights |
entity_id(s) of lights, if not specified, all lights in the switch are selected. |
list of entity_id s |
|
manual_control |
Whether to add ("true") or remove ("false") the light from the "manual_control" list. |
bool |
adaptive_lighting.change_switch_settings
adaptive_lighting.change_switch_settings
(new in 1.7.0) Change any of the above configuration options of Adaptive Lighting (such as sunrise_time
or prefer_rgb_color
) with a service call directly from your script/automation.
Service data attribute | Required | Description |
---|---|---|
use_defaults |
(default: current for current settings) Choose from factory , configuration , or current to reset variables not being set with this service call. current leaves them as they are, configuration resets to initial startup values, factory resets to default values listed in the documentation. |
|
all other keys (except the ones in the table below |
See the table below for disallowed keys. |
The following keys are disallowed:
DISALLOWED service data | Description |
---|---|
entity_id |
You cannot change the switch's entity_id , as it has already been registered. |
lights |
You may call adaptive_lighting.apply with your lights or create a new config instead. |
name |
You can rename your switch's display name in Home Assistant's UI. |
interval |
The interval is used only once when the config loads. A config change and restart are required. |
đ¤ Automation examples
Reset the manual_control
status of a light after an hour.
- alias: "Adaptive lighting: reset manual_control after 1 hour"
mode: parallel
trigger:
platform: event
event_type: adaptive_lighting.manual_control
variables:
light: "{{ trigger.event.data.entity_id }}"
switch: "{{ trigger.event.data.switch }}"
action:
- delay: "01:00:00"
- condition: template
value_template: "{{ light in state_attr(switch, 'manual_control') }}"
- service: adaptive_lighting.set_manual_control
data:
entity_id: "{{ switch }}"
lights: "{{ light }}"
manual_control: false
Toggle multiple Adaptive Lighting switches to "sleep mode" using an input_boolean.sleep_mode
.
- alias: "Adaptive lighting: toggle 'sleep mode'"
trigger:
- platform: state
entity_id: input_boolean.sleep_mode
- platform: homeassistant
event: start # in case the states aren't properly restored
variables:
sleep_mode: "{{ states('input_boolean.sleep_mode') }}"
action:
service: "switch.turn_{{ sleep_mode }}"
entity_id:
- switch.adaptive_lighting_sleep_mode_living_room
- switch.adaptive_lighting_sleep_mode_bedroom
Set your sunrise and sunset time based on your alarm. The below script sets sunset_time exactly 12 hours after the custom sunrise time.
iphone_carly_wakeup:
alias: iPhone Carly Wakeup
sequence:
- condition: state
entity_id: input_boolean.carly_iphone_wakeup
state: "off"
- service: input_datetime.set_datetime
target:
entity_id: input_datetime.carly_iphone_wakeup
data:
time: '{{ now().strftime("%H:%M:%S") }}'
- service: input_boolean.turn_on
target:
entity_id: input_boolean.carly_iphone_wakeup
- repeat:
count: >
{{ (states.switch
| map(attribute="entity_id")
| select(">","switch.adaptive_lighting_al_")
| select("<", "switch.adaptive_lighting_al_z")
| join(",")
).split(",") | length }}
sequence:
- service: adaptive_lighting.change_switch_settings
data:
entity_id: switch.adaptive_lighting_al_den_ceilingfan_lights
sunrise_time: '{{ now().strftime("%H:%M:%S") }}'
sunset_time: >
{{ (as_timestamp(now()) + 12*60*60) | timestamp_custom("%H:%M:%S") }}
- service: script.turn_on
target:
entity_id: script.run_wakeup_routine
- service: input_boolean.turn_off
target:
entity_id:
- input_boolean.carly_iphone_winddown
- input_boolean.carly_iphone_bedtime
- service: input_datetime.set_datetime
target:
entity_id: input_datetime.wakeup_time
data:
time: '{{ now().strftime("%H:%M:%S") }}'
- service: script.adaptive_lighting_disable_sleep_mode
mode: queued
icon: mdi:weather-sunset
max: 10
Additional Information
For more details on adding the integration and setting options, refer to the documentation of the PR and this video tutorial on Reddit.
Adaptive Lighting was initially inspired by @claytonjn's hass-circadian_lighting, but has since been entirely rewritten and expanded with new features.
đ Troubleshooting
Encountering issues? Enable debug logging in your configuration.yaml
:
logger:
default: warning
logs:
custom_components.adaptive_lighting: debug
After the issue occurs, create a new issue report with the log (/config/home-assistant.log
).
â Common Problems & Solutions
đĄ Lights Not Responding or Turning On by Themselves
Adaptive Lighting sends more commands to lights than a typical human user would. If your light control network is unhealthy, you may experience:
- Laggy manual commands (e.g., turning lights on or off).
- Unresponsive lights.
- Home Assistant reporting incorrect light states, causing Adaptive Lighting to inadvertently turn lights back on.
Most issues that appear to be caused by Adaptive Lighting are actually due to unrelated problems. Addressing these issues will significantly improve your Home Assistant experience.
đļ WiFi Networks
Ensure your light bulbs have a strong WiFi connection. If the signal strength is less than -70dBm, the connection may be weak and prone to dropping messages.
đ¸ī¸ Zigbee, Z-Wave, and Other Mesh Networks
Mesh networks typically require powered devices to act as routers, relaying messages back to the central coordinator (the radio connected to Home Assistant). Philips lights usually function as routers, while Ikea, Sengled, and generic Tuya bulbs often do not. If devices become unresponsive or fail to respond to commands, Adaptive Lighting can exacerbate the issue. Use network maps (available in ZHA, zigbee2mqtt, deCONZ, and ZWaveJS UI) to evaluate your network health. Smart plugs can be an affordable way to add more routers to your network.
For most Zigbee networks, using groups is essential for optimal performance. For example, if you want to use Adaptive Lighting in a hallway with six bulbs, adding each bulb individually to the Adaptive Lighting configuration could overwhelm the network with commands. Instead, create a group in your Zigbee software (not a regular Home Assistant group) and add that single group to the Adaptive Lighting configuration. This sends a single broadcast command to adjust all bulbs, improving response times and keeping the bulbs in sync.
As a rule of thumb, if you always control lights together (e.g., bulbs in a ceiling fixture), they should be in a Zigbee group. Expose only the group (not individual bulbs) in Home Assistant Dashboards and external systems like Google Home or Apple HomeKit.
đ Light Colors Not Matching
Bulbs from different manufacturers or models may have varying color temperature specifications. For instance, if you have two Adaptive Lighting configurationsâone with only Philips Hue White Ambiance bulbs and another with a mix of Philips Hue White Ambiance and Sengled bulbsâthe Philips Hue bulbs may appear to have different color temperatures despite having identical settings.
To resolve this:
- Include only bulbs of the same make and model in a single Adaptive Lighting configuration.
- Rearrange bulbs so that different color temperatures are not visible simultaneously.
đĄ Bulb-Specific Issues
These lights are known to exhibit disadvantageous behaviour due to firmware bugs, insufficient functionality, or hardware limitations:
- Sengled Z01-A19NAE26
- Unexpected turn-ons: If Adaptive Lighting sends a long transition time (like the default 45 seconds), and the bulb is turned off during that time, it may turn back on after approximately 10 seconds to continue the transition command. Since the bulb is turning itself on, there will be no obvious trigger in Home Assistant or other logs indicating the cause of the light turning on. To fix this, set a much shorter
transition
time, such as 1 second. - Heat sensitivity: Additionally, these bulbs may perform poorly in enclosed "dome" style ceiling lights, particularly when hot. While most LEDs (even non-smart ones) state in the fine print that they do not support working in enclosed fixtures, in practice, more expensive bulbs like Philips Hue generally perform better. To resolve this issue, move the problematic bulbs to open-air fixtures.
- Unexpected turn-ons: If Adaptive Lighting sends a long transition time (like the default 45 seconds), and the bulb is turned off during that time, it may turn back on after approximately 10 seconds to continue the transition command. Since the bulb is turning itself on, there will be no obvious trigger in Home Assistant or other logs indicating the cause of the light turning on. To fix this, set a much shorter
- Ikea Tradfri bulbs/drivers (and related Ikea smart light products)
- Unsupported simultaneous transition of brightness and color: When receiving such a command, they switch the brightness instantly and only transition the color. To get smooth transitions of both brightness and color, enable
separate_turn_on_commands
. - Unresponsiveness during color transitions: No other commands are processed during an ongoing color transition, e.g., turn-off commands are ignored and lights stay on despite being reported as off to Home Assistant. The default config with long transitions thus results in long periods of unresponsiveness. To work around this, disable transitions by setting
transition
to0
, and increase the adaptation frequency by settinginterval
to a short time, e.g.,15
seconds, to retain the impression of smooth continuous adaptations. Keeping theinitial_transition
is recommended for a smooth fade-in (lights are usually not turned off momentarily after being turned on, in which case a short period of unresponsiveness is tolerable).
- Unsupported simultaneous transition of brightness and color: When receiving such a command, they switch the brightness instantly and only transition the color. To get smooth transitions of both brightness and color, enable
đ Graphs!
These graphs were generated using the values calculated by the Adaptive Lighting sensor/switch(es).
âī¸ Sun Position
đĄī¸ Color Temperature
đ Brightness
transition_until_sleep: true
While using
đ See also
- Sleep better with Adaptive Lighting in Home Assistant by Florian Wartner on 2023-02-23 (blog post
đ ) - Automatic smart light brightness and color based on the sun by Home Automation Guy on 2022-08-31 (YouTube video
đē ) - Adaptive Lighting Blew My Mind in Home Assistant - How to set it up by Smart Home Junkie on 2022-06-26 (YouTube video
đē )