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

[AntonH]

Hi Freddeh,

@freddeh

As a newbie to this blueprint it is a bit confusing to have first Tiggers and then Conditions in the top section and in DYNAMIC mode you have first Turn Off Conditions and then down below Turn Off Triggers… took me a few minutes to figure that out. Might be a minor improvement to just switch the order around in the bottom.

Thanks for this feedback.
Seems to be a fair observation, so I’ll modify this for the next release.

@freddeh

Edit: looks like the Turn Off Conditions are not checked at all in DYNAMIC mode when the trigger is reached, is that true?

Yes, the nature of dynamic mode is that you can set the maximum or minimum brightness to 0% (effectively turning it off). You can prevent this from happening by choosing other values or changing the values for ‘over max’ and ‘under min’. See screen capture below.

[AntonH]

NEW RELEASE:

09/01/2024 - Version 2.1

• Corrected a bug where the automation would not run unless an optional light sensor was selected.
• Removed the ‘don’t turn the lights off’ option since it was redundant and could cause an error.
• Changed the order of the turn off selectors to make them more user-friendly (Thanks @freddeh for the feedback).
• Modified selector descriptors to make the automation more user friendly.
• Modified the automation description for better legibility.
• Moved some default values around for better consistence in the code base.
• Slight modifications to templates for consistency and legibility.

[AntonH]

@freddeh

As a newbie to this blueprint it is a bit confusing to have first Tiggers and then Conditions in the top section and in DYNAMIC mode you have first Turn Off Conditions and then down below Turn Off Triggers… took me a few minutes to figure that out. Might be a minor improvement to just switch the order around in the bottom.

This has been modified in today’s release.

[Stqn (Stan)]

Might be a silly question – I’m just starting out with HA – but how do you toggle?
If I press the button, it turns on my lights. But I want a press to toggle. Do you seen what I mean?

Thanks for the work though! It looks amazing

[AntonH]

@Stqn

Might be a silly question – I’m just starting out with HA – but how do you toggle?
If I press the button, it turns on my lights. But I want a press to toggle. Do you seen what I mean?

It’s not a silly question at all:
Activate the turn off function ‘turn of with trigger’ and set your trigger to the same button.
Then add a condition that checks if the light is on.

See example below:

@Stqn

Thanks for the work though! It looks amazing

Thanks a lot!

[Stqn (Stan)]

@AntonH

It’s not a silly question at all:
Activate the turn off function ‘turn of with trigger’ and set your trigger to the same button.
Then add a condition that checks if the light is on.

Makes sense, I’m still lacking some reflexes like this mental puzzle
That being said, it works… but one light always re-turn ON right after. I’m trying to toggle a light group.

Even if I only target that one light, it blinks (toggle off and on immediately I’m assuming). I must have a conflict somewhere.

Thanks for the support!

[AntonH]

@Stqn

That being said, it works… but one light always re-turn ON right after. I’m trying to toggle a light group.

Even if I only target that one light, it blinks (toggle off and on immediately I’m assuming). I must have a conflict somewhere.

Thanks for the support!

Check the Traces (go to the Automation, you’ll see traces in the top right).
They will give you an overview of what happens in each step.
If there is any weirdness, just post it here or send me a message so I can have a look.

[Edvin89]

Hello and thanks for a great blueprint!
Have been using it for a while and it has worked very well and easy to set up, especially after the latest update (after feedback from another user).

But ran into a “problem” today when I was going to make an automation with a power outlet activate on motion and realized that this blueprint doesn’t support switches.

Would it be possible to add support for switches?

[Stqn (Stan)]

I can confirm there is something fishy.
I added some cards to see if it was a group trigger or something else, but through the card it works as expected, meaning I toggle on and off both lights

On screenshot, it’s the Hue ambiance lamp 1 at fault.

Any traces you’d like to see?

[Stqn (Stan)]

@AntonH Actually, managed to replicate the behaviour with another condition for toggling on: expecting that group is off.
Seems a bit overkill to have both, but it works as expected.

Thanks for your help!

[AntonH]

@Edvin89

Hello and thanks for a great blueprint!
Have been using it for a while and it has worked very well and easy to set up, especially after the latest update (after feedback from another user).

But ran into a “problem” today when I was going to make an automation with a power outlet activate on motion and realized that this blueprint doesn’t support switches.

Would it be possible to add support for switches?

Agreed, it’s possible to select switch entity types at this moment, but not yet to control them.
It’s not a big issue as switch entity type only turn on and off, so they only support the DEFAULT mode, however it’s something that needs to be address.

It’s on the list for a future release.

thanks for the feedback.

[AntonH]

NEW RELEASE:

10/01/2024 - Version 2.2

• Added support for switch entities (Only DEFAULT & TOGGLE modes are supported due to the nature of this entity type)
• Added a new TOGGLE mode, allowing users to toggle light and switch entities with a simple setup instead of using the turn off triggers.
• Adjusted and corrected descriptions to make the blueprint more user-friendly
• Correcting some spelling errors

[AntonH]

A new TOGGLE mode has been added to some this issue.

[AntonH]

@Edvin89

Hello and thanks for a great blueprint!
Have been using it for a while and it has worked very well and easy to set up, especially after the latest update (after feedback from another user).

But ran into a “problem” today when I was going to make an automation with a power outlet activate on motion and realized that this blueprint doesn’t support switches.

Would it be possible to add support for switches?

Support for switches has been added.
Due to the nature of how this entity type works, only default and toggle modes are supported though.

[Edvin89]

Thanks for the update, been running it for a while now and works great.

[Belei99]

Hi, thanks for your Bp, its works good for me, only the function Light Sensor does not find any Sensor. But i have 2 Homematic Sensors with Brighness. Under the Object is the Value available. But nothing in your Blueprint.

Someone any Ideas?

[tmudde (muddy)]

Hello, I’ve found the blueprint and it looks like a promising solution for me. Thanks for the good work! I have 2 things I can’t figure out and think they are flaws in the design.
The first one is related to the turn_off_conditions. As far as I can judge, this turn_off_condition is ignored completely during the execution of the automation.
The second point concerns the turn off function. The accompanying text states that there are multiple options possible, but that’s not the case, at least not simultaniously. For example, if I use the staircase function along with a ‘turn off with trigger’ option, the automation steps into the wait state of the staircase option, and during this wait state a turn-off trigger is no longer detected.
Hope this helps and can be resolved in a next version. Keep up the good work!

[AntonH]

@Edvin89

Thanks for the update, been running it for a while now and works great.

Thanks, it’s great to see the effort is appreciated!

[AntonH]

NEW RELEASE:

21/01/2024 - Version 2.3

• Fixed the turn off conditions. They are no longer ignored.
• Only 1 turn off option is possible while I’m working to fix interoperability of multiple options.

[AntonH]

@tmudde

Hello, I’ve found the blueprint and it looks like a promising solution for me. Thanks for the good work! I have 2 things I can’t figure out and think they are flaws in the design.
The first one is related to the turn_off_conditions. As far as I can judge, this turn_off_condition is ignored completely during the execution of the automation.

You’re right!
This was an oversight and has been addressed in the new release (2.3 and up)

@tmudde

The second point concerns the turn off function. The accompanying text states that there are multiple options possible, but that’s not the case, at least not simultaniously. For example, if I use the staircase function along with a ‘turn off with trigger’ option, the automation steps into the wait state of the staircase option, and during this wait state a turn-off trigger is no longer detected.

I’m working on this for the next release. For now, I’ve updated the BP so that only 1 option is selectable.