⚙ Turn Light, Switch, Entity or Scene On & Off with Trigger Conditions

Hello, thanks for the script and the continued support!

I have played around with both the time for it to be active and the sun position, but it appears the light will turn on regardless of the time of day, instead of only when i am trying to define it. unless i am drastically misinterpreting it

which from an earlier post: The automation was developed as a lot of people just wanted a simple ON / OFF for a light with time. I added extra options to choose from when developing it if time was not your thing, like LUX, sun & binary sensor. You can choose weekday as a global setting so it could be used in a office environment were Monday to Friday you need the lights ON and OFF. Example: If using time option set the time to turn the lights ON at 8 am and OFF at 6 pm Monday to Friday.

It looks like it might not do what i was hoping (basically when a event in frigate is logged to turn on a light) I only want to turn on a light if a person is seen, not the millions of bugs in florida :slight_smile:


Hi Michael, firstly welcome to the community.

This blueprint works with the actual trigger points (crosses over your setting). Example

You mentioned time and sun.

When the sun drops below the sun elevation or the “ON time” it will turn the light ON. If you enabled the option.

When the sun rises above the sun elevation or the “Off Time” it will turn the light OFF at that point. It is not a condition to only work when the sun is below the sun elevation.

It is the same for “Binary Sensor” and “Ambient Light Sensor”.

So the sun could turn the light ON when it goes below the sun elevation and then the time can turn it off. Example if you let the sun turn it ON and then you would like it off at 11:30pm you would set the sun elevation at say -1.5 and the light would come ON when it passes over this setting. Then if you would like it OFF at 11:30pm you would use the time and set the ON time to 11:29pm (the light is already ON so nothing changes) and the off time to 11:30pm. Light turns OFF. When the sun goes above the sun elevation it will turn it OFF but it is already OFF so nothing happens.

What I think your after is for the light to only come ON when it is dark or below the sun elevation. For this you would need to use my other blueprint called :bulb: Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time.

This is tricky… but if you have a CCTV camera that can detect humans and then send triggers for this and not the millions of bugs you have in florida it should work with my other blueprint.

Hope the helps you.

Blacky :smiley:

1 Like

It is actually working pretty much as I want now. :+1:

I would like to see a timer option for switching off lights. Now it needs two?? automations that might interfere as I see it but please correct me if I am wrong.
I want to use it with a ‘presence sensor group’ switch light groups on but when no occupancy it should switch of after X time.

Hi Stevie, that is good news :+1:


I think you may be after my other blueprint. Have a look at this one.

:bulb: Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time

Can it be made to accept any sensor?
I.E. Use a battery sensor to toggle a the smart plug where the charger is when the battery is below X%.
And disable when battery above Y% percent?


Hi Tiago, have a look at another one of my blueprints called :snowflake: Temperature Control Exhaust Fan - Inverted. I think this is what you are after.

I’ll try it, it does seem to be able to accomplish my idea. But the name kinda threw me away xD.

Yea the name will throw you, but when saving it you will have the option to rename it.

Good luck and hope this helps you.

Blacky :smiley:

1 Like

Good point. I’ll do that.

Much appreciated for your work in these fine blueprints.
I use Sensor Light as well.

1 Like

New update 1.5

:warning: BLUEPRINT CODE UPDATE :exclamation:

Just a heads up if your still on a old HA version before you update.

From time to time Home Assistant update their code structure and the old code will become “DEPRECATED” stopping / breaking automations from working. It effected this blueprint about 4 to 6 months ago. I wanted to wait some time so everyone had a chance to update their HA version before updating the code as older HA versions can not run the new code. This blueprint has now been updated so it will still operate once HA remove the “DEPRECATED” code from their system. :wink: :+1:

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:


Blacky :grinning:


Is there a way of adding conditions to the trigger ? For example, I have an alarm system which is integrated to HA, so I want to trigger the lights based on

  1. The Alarm systems “sunset flag”
  2. The alarm systems mode (ie, dont trigger if set to night mode).


Hi @Wexfordman

I would have to add this option in. Give us a few days so I can have a look at it and I will get back to you.

Blacky :smiley:

I have done this, before I update it could you confirm your “sunset flag” domain. If you are unsure what this is could you please copy paste the entity ID in here.

EDIT: Don’t worry I am going to change this so you can have any domain you like.

New update 1.6

:warning: Some work is required in this upgrade. Please see below on the steps required when upgrading. It is easy and not a breaking change.

Upgrade Features :new:

  • Binary Sensor: “Use The Binary Sensor Option (Optional)”, as been upgraded to “Use The Entity State Option (Optional)”. This now allows you to enter in any entity you like and not just a binary sensor. The entity still must have an ON / OFF state. Because of this update you will need to update your YAML as shown below.

New Features :new:

  • Global Condition: You can now add in any global condition you like.

:warning: :stethoscope: STEPS REQUIRED WHEN UPGRADING :white_check_mark:

If you have never selected to use a “Binary Sensor” then most likely you won’t need to do anything but you may want to check just encase you have selected “Binary Sensor” in the past.

1 - Upgrade your blueprint.
2 - Go into your automation (the ones using this blueprint). Click on the 3 dots top right and edit in YAML.

3 - We are looking for the words… “include_binary_sensor…” & “binary_sensor…”. If you don’t see them then you are all good, nothing to do. If you see them then read on.

4 - We need to delete the 2 lines, click save then the 3 dots and edit in virtual editor.

5 - Then you will need to enable the entity state option and enter in your binary sensor again into input entity.

6 - Click save, you’re done. Now just do the same in your other automations using this blueprint.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:


Blacky :grinning:

1 Like

Thanks blacky, will give it a go over the weekend

1 Like

Awesome… Thanks, @Blacky for your blueprints. I think I use all of them now :slight_smile:

Anyway… maybe a silly question. I have enabled the ambient light option, set to trigger at 3 lux. But when will the blueprint actually trigger? (1) When the illuminance sensor is 3 (or below) for the first time, or (2) every time when the illuminance sensor reports 3 lux or lower?

I want to use this blueprint to manage my livingroom lights. But when I go to bed, I turn the light off, and then should remain off (obviously). In case of (2) the light will go on again as soon as the illuminance sensors sends an update.

Can you add the option that the illuminance sensor is influenced by the light? Just like you have in the other blueprint?


No it will not work that way.

Looks like you are only needing it at night time. If this is the case then try using the sun condition as it will then work for you. The sun elevation can be very close to a lux value. If this is not the case then let me know.

Blacky :smiley:

No, not really. For example:
Today is a really rainy day. It’s over 30 minutes until sunset, but the light is already really low (below 7 lux in my room) This causes the light to go on/off every couple of minutes. Just because the lights raise the lux again above the threshold…