Not used it myself, as of yet, but the adaptive_lighting.apply service looks to be what you're after.

This is what I do to avoid that transition and prime the light with the right colour temp and brightness when turning the lights on using motion sensors. I get no jump in temp or brightness as a result.

service: light.turn_on
data_template:
entity_id: light.corridor_lights
kelvin: >-
{{ state_attr('switch.adaptive_lighting_corridor', 'color_temp_kelvin') |
int }}
brightness_pct: >-
{{ state_attr('switch.adaptive_lighting_corridor', 'brightness_pct') | int
}}

The adaptive light switch needs to be on for the variables colour temp and brightness to be populated.

Not used it myself, as of yet, but the adaptive_lighting.apply service looks to be what you're after.

I'll have to test this out. My initial reading of it was that it would operate just like the component normally does (e.g. turn on light, then adapt), but on demand.

This is what I do to avoid that transition and prime the light with the right colour temp and brightness when turning the lights on using motion sensors. I get no jump in temp or brightness as a result.

service: light.turn_on
data_template:
entity_id: light.corridor_lights
kelvin: >-
{{ state_attr('switch.adaptive_lighting_corridor', 'color_temp_kelvin') |
int }}
brightness_pct: >-
{{ state_attr('switch.adaptive_lighting_corridor', 'brightness_pct') | int
}}

The adaptive light switch needs to be on for the variables colour temp and brightness to be populated.

I always keep AL on so this should work. Thanks! I'll give it a go!

I'll have to test this out. My initial reading of it was that it would operate just like the component normally does (e.g. turn on light, then adapt), but on demand.

Sorry, should have highlighted the turn_on_lights attribute of the service.

turn_on_lights	Whether to turn on lights that are currently off.

Behaviour of lights (in general) does seem to vary per brand/model, though. It's good to have finer control in those situations—igiannakas' use of a data template looks perfect for such.

You might also look towards a Template Light, for complete handling of functionality. A little overkill for what I'm doing ... sidesteps much of the convenience afforded by automation and the Adaptive Lighting integration; though—if you've an exact requirement of how entities should behave—it's probably a good fit.

turn_on_lights isn't the perfect solution. My IKEA Tradfri bulbs need separate commands for brightness and color.

When I trigger the adaptive_lighting.apply the two transitions of the service and the two transitions of the initial_transition start and if a transition start while another transition is still ongoing the ongoing transition gets cancelled. And if the timing is bad they cancel each other in a way that bulb does not reach it's final color/brightness.

Is there an easy way to suppress the the initial_transition?

For testing purposes I removed the following call in line 917 in switch.py

await self._update_attrs_and_maybe_adapt_lights(
    lights=[entity_id],
    transition=self._initial_transition,
    force=True,
    context=self.create_context("light_event"),
)

Without this the adaptive_lighting.apply with turn_on_lights works like a charm and just the two service calls for brightness and color are issued.

Does this function call do anything else than the initial_transition? If it's only for the initial_transition than a checkbox in the UI could be added and the function could be called depending on the checkbox.

I am also this issue, had a hope zigbee2mqtt will speed things up (compared to Tradfri and Hue), but it's not that much.

It would be great to have a service that preloads light.turn_on with appropriate settings!

I'm currently in the process of doing version 2. This will be added/fixed.

Keep this ticket open until you can verify that it's properly working in the upcoming version 2.

This is currently done/waiting-for-review. I wanted this too so I spent a half hour making it :)

The problem described by @Slinky-Wrangle-Punch here #86 (comment) is no longer present.

Right now AL will wait for transitions that have been set (thanks to @th3w1zard1! 🎉)

Therefore, I think the request has an existing solution (use adaptive_lighting.apply with turn_on_lights and desired transition). Then just use the normal light.turn_off.