💡 The Everything Light - Trigger a light any way and turn it on in any way

[AntonH]

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.

[headless]

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

[iandogherty]

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?

[AntonH]

@iandogherty

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

[iandogherty]

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.

[AntonH]

NEW RELEASE:

23/01/2024 - Version 2.6

• General spelling corrections
• Amended syntax to new guidelines (HA 2024.8 & 2024.10 changes)

[DanielGG (Daniel)]

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

<sup>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</sup>

[AntonH]

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:

• When turning on: the light needs to be off
• when turning off: the light needs to be on

[AntonH]

NEW RELEASE

09/01/2025 - Version 2.7:

• Updated the deprecated ‘brightness_pct’ property to ‘brightness’

[AntonH]

NEW RELEASE

09/01/2025 - Version 2.8

• Updated the code so that users can use percentage values for the light’s brightness settings again, which is more intuitive than a 0-255 value.

[macaholman (David Waldmeier)]

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:

Wasn’t that supposed to change in version 2.8? Thanks!

[AntonH]

@macaholman

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:

Wasn’t that supposed to change in version 2.8? Thanks!

Thanks for noticing! It’s fixed in version 2.9.

[AntonH]

NEW RELEASE

16/01/2025 - Version 2.9

• Corrected the UI to reflect the brightness value input with percentage values.
• Code corrections for fixed brightness mode.

[AntonH]

NEW RELEASE

11/03/2025 - Version 2.10

• Updated the Color Temperature Selectors to use Kelvin instead of Mired values. (The usable range depends on what your lights support. Consult your manual.)

[baerakafubu]

Thx for the blueprint. Works reliably, but one thing I just can’t determine (or don’t understand it correctly): I use it to recognise movement so that a lamp is turned on with red color as warning for 3 minutes and then goes out after this time has passed. But if this lamp has been previously switched on as part of a scene with 4 other lamps, for example in warm white, then it’s not helpful if the lamp goes out and stays like that. How can I determine that the previous state (i.e. the warm white scene) is restored after the 3 minutes?

[AntonH]

At the moment that’s not possible.
Essentially the blueprint would need to create a scene and then call that scene when the light is turned off.
My other blueprint ‘Party Lights’ has a feature ‘SCENE THEN OFF’ which does exactly this. It could be a nice feature to add to this blueprint in the future.

Alternatively you could create a separate automation that sets the right color when the light goes out.

[baerakafubu]

Thank you!