Hum. Iām not familiar enough with blueprints to know if thatās solvable.
amazing, i will look at it next month
Itās not, when you change inputs it breaks the blueprint, then anyone using this option has to fix it. DL started with just a brightness option and grew from there. Itās also a bit complex to help reduce how much it work the blueprint does under the hood and how it links to other option in the blueprint making it work correctly.
Itās easier to add 3 new selections.
Blacky 
1 Like
Wondering if anyone has ever come across this error when activating a sensor light add-on automation?
Canāt figure out whatās causing it at all but the error only ever occurs when the add-on automation is run.
Effect is the add-on lights routine runs but then after a few seconds the lights return to the normal automation state. Issue has only started happening in the last week or so, canāt pinpoint a change that could have caused itā¦
Logger: homeassistant
Source: helpers/script.py:974
First occurred: March 28, 2026 at 9:56:07 PM (12 occurrences)
Last logged: 8:10:13 PM
Error doing job: _StopScript exception in shielded future (task: None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 467, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 533, in _async_step
self._handle_exception(
~~~~~~~~~~~~~~~~~~~~~~^
ex, continue_on_error, self._log_exceptions or log_exceptions
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 563, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 531, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/trace.py", line 283, in async_wrapper
await func(*args)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 675, in _async_step_parallel
raise result
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 667, in async_run_with_trace
await self._async_run_script(script, parallel=True)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 643, in _async_run_script
result = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 631, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1865, in async_run
return await asyncio.shield(create_eager_task(run.async_run()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 467, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 533, in _async_step
self._handle_exception(
~~~~~~~~~~~~~~~~~~~~~~^
ex, continue_on_error, self._log_exceptions or log_exceptions
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 563, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 531, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 734, in _async_step_choose
await self._async_run_script(script)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 643, in _async_run_script
result = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 631, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1865, in async_run
return await asyncio.shield(create_eager_task(run.async_run()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 467, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 533, in _async_step
self._handle_exception(
~~~~~~~~~~~~~~~~~~~~~~^
ex, continue_on_error, self._log_exceptions or log_exceptions
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 563, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 531, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 787, in _async_step_if
await self._async_run_script(if_data["if_else"])
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 643, in _async_run_script
result = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 631, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1865, in async_run
return await asyncio.shield(create_eager_task(run.async_run()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 467, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 533, in _async_step
self._handle_exception(
~~~~~~~~~~~~~~~~~~~~~~^
ex, continue_on_error, self._log_exceptions or log_exceptions
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 563, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 531, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 974, in _async_step_stop
raise _StopScript(stop, response)
homeassistant.helpers.script._StopScript: Stop the automation
Look at the bottom line. The automation was stopped. This is okay, just monitor it and maybe an update of HA will fix it.
Blacky
Iād like the lights to not turn off during Night Light hours, because i manually turn off anyway and might want them to stay on low for a while, my pir sensor canāt see the whole room and i might not trigger it in bed either.
I figured i could group the pir and a toggle, but not sure how
Ive been a long time user of this blueprint but have struggled with a recurring issue in my bathroom. When the automation kicks off during night time, it turns on the lights at 100% and then dims them a few seconds later. The net result is it blinds you temporarily instead of just turning on dimmed. Thoughts?
Hi Blacky. Iām having some problem with a new purchase of some new Apollo automation combined 2412 - 2450 sensors. They detect quickly with your blueprint. I also have some SCreek 2410ās as part of the system but they donāt seem to show this issue. Nor do PIR sensors.
Very often, in some locations, I trip the binary helper (combination of Apolloās 2412 and 2450 motion energy, still energy and movement) and the lights go on. I exist the hall, lights still on, they go off according to a combination of the ESP Apollo timer and Home Assistant automation, letās say 1 minute total, and then I walk back into the zone 10 seconds later and they donāt come on.
In the Apollo ESP Home settings, there is only 1 timer setting for the 2412 and one for the 2450 in the settings. and it just labels them 2450 timeout or 2412 timeout. Not sure what tthat means, what time is it referring to?
A claude search of this same post gave me this answer. Of course Claude is always trying to keep me happy.
## The Core Issue: State Lockout After Timeout
When your lights turn off after the timeout, the automation is likely in a brief "cooldown" or the binary sensor is stuck in a state that prevents re-triggering. Here are the most probable culprits:
1. **The Blueprint's "Blocking" Logic**
Most popular lighting blueprints (like the widely-used ones by Blacky or others) use a **blocking helper** ā an `input_boolean` or similar ā that gets set when the lights turn off. If you return within a short window, that blocker hasn't reset yet and suppresses the trigger. Check your blueprint for any "blocking" or "cooldown" input helpers.
Do you have any insight into this?
Hi and Thanks @Blacky for this awesome Blueprint!
edit: Sometimes I am a fool. I forgot to set up the off script. With an off script itās working. 
But maybe itās possible to integrate Scene Presets by default? 
I have been changed for some months ago to this blueprint and itās working like a charm!
But sometimes I want to have more colourful lights In my own automations I used a mix of fixed light temperature and ambient lights and Scene Presets (Scene Presets: Hue-like scenes for generic light entities).
Scene Presets would be active for some reasons like ānot dark enough for all lights but some colourful highlights would nice hahaā or something else. I tried to combine your Blueprint with a script which has been set up as light, which should start Scene Presets for a light. The script work (nothing special) if I start it standalone:
sequence:
- data:
preset_id: 6550c445-3ed7-46b3-9d06-76f7e9ef7c4e
targets:
entity_id: light.stofflampe
brightness: 138
shuffle: false
smart_shuffle: false
action: scene_presets.apply_preset
alias: Sensor Light Script Ambientesteuerung Wohnzimmer
description: Wendet eine Ambiente-Szene auf einen Raum an
mode: restart
fields: {}
but the script doesnāt start as script in your Blueprint.
Two questions:
- Do I something wrong? Is something else necessary to start a script?
- Maybe it would be possible to add a function in your Blueprint to get a ācolourfulā ambient light? Maybe in combination with Scene Presets as direct integration or may as add-on (like Movie Lights?)
This would be very nice! 
Bests
Montgomery
Hi All
I love this blueprint and i use it everywhere i have light !!!
for the life of me i canāt find how can we use input_boolean as the āLights - Switches - Scenes - Scripts *ā is yhis not possible ?
I canāt believe I am the only one that would need this feature ? I search the foreum but canāt find anything on this.
thanks for any help
Trying out the Sensor Light blueprint and so far been liking it.
Currently testing the āBypass Switch - Keep the Lights Current Stateā option for one of rooms that is controlled by a Lutron Caseta light switch. So I have a dedicated Zigbee button Sonoff SNZB-01 integrated via Zigbee2MQTT. Iām trying to choose the entity on the remote button but it doesnāt show the action (press single/double/long/etc). Z2M deprecated the legacy option for actions that is why actions entity is now missing in HA.
Is it possible to use a dedicated zigbee button to trigger bypass of the light switch?
Is there any particular reason for the crossover variables to check that āexclusionā set is non empty? If we calculate entities that are in a and not in b, b can be empty.
For example, during the night time crossover, it calculates which lights should be turned off, however, it only does so if both day and night lights are non-empty, whereas in my opinion if none of the night lights are defined - then it should turn off all the day lights (well minus the āglowā lights but these are accounted for in a separate variable that does suffer from the same problem though)
Current behavior is that none of the ādayā lights are being turned off, but if I add a āfakeā light to the night lights, everthing works as I expect.
Iām not sure of course Iām using it right, because what is the purpose of the night mode if you donāt have any night lights, but in my case the purpose is to effectively disable presence trigger.
Lastly both these lines [1 and 2] contain likely a typo ({} instead of [])
Is it possible to add these fixes to the next version?