Thatâs correct behavior: the trigger in you case is the motion sensor and not the lux sensor. so only when the motion sensor gets triggered the automation goes through the calculation again and sets the light to the changed value.
If you want it to work with the lux sensor only, you could try my other blueprint: đĄ Smart lux dimmer - Adjust light brightness depending on light sensor value
Thank you for that information
Am trying your other Blueprints
Hi @AntonH. I am a huge fan of your blueprint. I have one more suggested feature.
I use the blueprint to turn on the lights in a room, if thereâs motion detected in the room. I use the staircase option to countdown x minutes.
In my use case, I would like the lights in the room to turn on when I enter the room as they do now, but then only to turn off if there hanât been any motion in the room for x minutes.
For this, I would like the staicase countdown to restart if any of the triggers fire off again during the staircase timeframe.
Hope this makes sense.
Hi @AntonH
I just switched from one of your templates (controlling just the brightness) to this one, which helped me delete a few of my own automations (thanks for that 
). I have two question.
I have two motion sensors in my hall because it is build like an L. Therefore I have set two deactivation triggers (certain amount of time after one of the sensors does not detect movement anymore), which only work if none of the two detects movment, so that there are no unsure states. The deactivation trigger condition does somehow prevent the deactivation flow to be executed and Iâm not sure how to correct that. Without the condition the deactivation flow is executed but if there is continuous movement just one of the two sensors is detecting, the deactivation is still triggered.
I only want the automation to work between 7:00 - 22:00 but the deactivation triggers shall still work outside the given time plan. This does not seem to work so I have to set up an additional deactivation automation.
The Blueprintâs mode is set to ârestartâ, so what youâre describing should work by default. Each time itâs triggered the staircase timer resets.
Do take into account that motion sensors usually have a built-in cool down period during which they will not re-trigger.
This is normal. The mode of the blueprint is set to ârestartâ. This means that it will restart the automation when one of the sensors is triggered and reset the turn off triggers.
I donât understand what you mean by this. Could you clarify a little more?
This is normal. The mode of the blueprint is set to ârestartâ. This means that it will restart the automation when one of the sensors is triggered and reset the turn off triggers.
That does not seem to work for me. If sensor 1 starts the deactivation flow (because a switch to no movement was recognised) and I move within the area only sensor 2 is detecting, the deactivation flow will still be executed (because sensor 1 is not detecting movement) and deactivate the light for the whole area.
Imagine there is movement at 21:59 (continuously until e.g. 22:03) the deactivation flow will not run anymore or this happened for me at least.
From your explanations, I understand that you have a trigger of âno movement detectedâ to start the deactivation. I think this is whatâs causing your issue.
I would work with a staircase timer in your case. That would start counting down from the moment movement is detected and be reset every time motion is detected again.
Still, this will not do the trick. If there is a room with continious movement the staircase function will be triggered and executed (there will be no switch of the trigger, which will stay enabled). I would assume that triggering it with âno movement detectedâ would be better in addition to the condition that all sensors in this area do currently not detect any movement. I already created that flow as an additional automation (which works) but it would be cool if it could be enabled in your template as well 
Hi - I think this will be a daft question, but hopefully someone will take pity and help. I can get this automation to run once when a trigger is fired (motion or door open) but thatâs it. Itâs set to Dynamic so my expectation is that it will continue to run dynamically adjusting the lights until the Off trigger is fired. Instead it runs once then stops.
Any idea what Iâm doing wrong?
If your trigger doesnât re-activate then the automation will run only once.
If you want something that runs continuously you can look into my other blueprint: Smart lux dimmer - Adjust light brightness depending on light sensor value
Ah yes, already got that one (which works a treat). I was looking for one single blueprint with extended facilities to do the whole thing - motion, dynamic light based on lux, colour temperature that changes through the day, and then switches the lights to red on motion at nighttime. Iâll keep looking, but thanks very much for this one.
NEW RELEASE:
23/01/2024 - Version 2.6
Hello, something funny happens to me
When I click on the switch light will turn on and then off, then I click again it will light without no issue.
This also happens when it I turn it off, it will immediately turn off and then on, second time will work like a charm
alias: Interruptor baño
description: ââ
use_blueprint:
path: Twanne/the_everything_light.yaml
input:
triggers:
- trigger: state
entity_id:
- event.shellypro4pm_08f9e0e4c764_input_2
target_light:
entity_id: switch.shellypro4pm_08f9e0e4c764_switch_3
include_color_or_temp: include_temperature
light_temperature: 205
brightness: 100
include_turn_off:
- trigger
turn_off_triggers:
- trigger: state
entity_id:
- event.shellypro4pm_08f9e0e4c764_input_2
run_conditions:
turn_off_conditions:
- condition: state
entity_id: event.shellypro4pm_08f9e0e4c764_input_2
state: ââ
mode: toggle
Your have the same button set as the turn_on and turn_off triggers but havenât specified a specific state for each, so they will both be activated.
Try adding a condition for each:
NEW RELEASE
09/01/2025 - Version 2.7:
NEW RELEASE
09/01/2025 - Version 2.8
Hey @AntonH ! Thanks for this amazing blueprint. One question regarding entering brightness values using percentage values (instead of 0-255). The sliders in version 2.8 still show values between 0-255:
Thanks for noticing! Itâs fixed in version 2.9.
NEW RELEASE
16/01/2025 - Version 2.9
