Where in this blueprint can I define that my motion sensor triggers the light to be switch on? Am I overlooking something?
I was looking to turn a light On and Off in one automation and this blueprint works great! Thanks for your effort!
Has this stopped working for anyone? Since upgrading to 2020.4 it doesn’t seem to trigger for me for some reason.
All still working here. If you would like to provide your automation YAML I can look at it for you. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.
I would first try a reboot of your system first, not a restart but a reboot.
Blacky 
Hi, How can I use this blueprint so the automation work between sun rise and sunset?.
At the moment the moment the automation is working for me fine but from sunset to sunrise 
You could use time but that is not really what you would like. For a simple automation like this you can always do a simple custom automation. If you are unsure how to do this just let us know and I will help you out.
Blacky
Blacky
It had started working now on 2024.5, but is a bit flakey at the moment.
Here’s the yaml:
alias: Lights - Sunset Presence
description: Lights at Sunset based on Presence
use_blueprint:
path: Blackshome/entities-on-off-trigger-conditions.yaml
input:
entity_switch:
entity_id: light.room_lamp
include_light_control: use_brightness
global_conditions:
- condition: device
device_id: 98393bc4da40412851193f03a3bea28e
domain: device_tracker
entity_id: 0a111dbbe28c9c5332fb45df6563b3b3
type: is_home
include_sun: sun_enabled
include_entity_input: entity_disabled
sun_elevation: -1.5
Just wondering, could you implement some sort of transition effect like the Hue app? So, it gradually lights up using brightness between 0-100 during select intervals, instead of abruptly turning on?
Thanks
That would be great, thanks!
Also if it’s not too much to ask, maybe an option to set offset?
eg. Turn lights on or off {duration 5/10/15min} before Sunset/Sunrise. 
Thanks
Hi Community, I may be off topic or trying to use the wrong blueprint for my needs and if so, please help point me in the right direction. Otherwise, I am converting from HomeSeer and one native function that took some time getting just right in tht platform, I cannot seem to duplicate in HA. We have a number of interior and exterior lighting and device automations that are tied to specific date ranges that repeat each year. For example, Interior and Exterior Christmas Automations that run either during specific times or tied to sunset and sunrise but run conditionally based on Days and Months of any year. Another Automation example would be for the period of time after Christmas to when a Valentines Automation would run. Some automations would run daily at a specific time (say 12pm on the weekends and 4pm on weekdays) or tied to sunset/sunrise (with or without and offset). My initial thought was to create separate calendars for each automation with the calendar event being one of the triggers (or a condition as it was in HomeSeer). That method is not working, likely because the multi day event never changes state. Any thoughts or suggestions on how to incorporate specific date ranges into this or another blueprint/automation? Thank you
I have updated it just doing testing before I release it.
We use sun elevation rather than time and sunset/sunrise as it works better throughout the year and HA recommend it this way. I have changed it so you have a sun elevation falling and a sun elevation for rising so they can be different.I have posted a FAQ below on this now.
Blacky
FAQ - Sun Option & Sun Elevation
Why did you use it and how can I set it?
I thought about “Sunset” and “Sunrise” but HA recommend to use sun elevation as it works better throughout the year. So I took their advice and used the sun elevation.
It is really easy to set up. I would recommend checking your sun elevation degrees and adjusting it to your requirements. Every site is different. An easy way to choose your setting is to find or add the sun to your dashboard. When you click on it, a pop-up window will appear or you can just put the sun elevation entity in.
Then, one night, simply observe the sunset and note the elevation. Decide on the elevation you’d like to trigger the automation so the lights will turn on. Once you’ve determined your preference, adjust the sun elevation degrees in the blueprint for “Sun Elevation Falling”. Repeat the process for sunrise and enter your settings into “Sun Elevation Rising”
Then, monitor to ensure it’s working correctly and meets your preferences. If adjustments are needed, you can easily make changes as necessary.
Enjoy
Blacky 
Back to FAQ: Click Here
Firstly welcome to the community.
Looks like you would like a lot of different automatons. You can use this blueprint and also have another one called 
Sensor Light
You can also use 
Calendar Notifications & Actions that can do your Christmas automatons and I have a FAQ on how to set it all up that could help. You can also just use the calendar blueprint to toggle ON and OFF your automatons. So you would have a automation for x-mas lights and you toggle it ON and OFF using the start and end actions.
Hope this can help you.
Blacky
1 Like
Some work is required in this upgrade see below. Only entities are allowed now, don’t update if you would like to still use areas and devices or make a copy of the code to use in another custom blueprint file.
Upgrade Features 
-
Light Control:
- We have now added a option to set the colour temperature of a light.
- We have now added a option to set the transition of a light and scene.
-
Sun Option: You now have the option to set a rising and falling sun elevation.
Maintenance 
- Set blueprint to my new layout.
- Clean up some descriptions.
STEPS REQUIRED WHEN UPGRADING 
-
Just need to clean up some YAML. Once you update and you see nothing selected in light control as shown below then jump to step 2.
If you see brightness selected as shown below then you are all good and don’t need to do anything hear unless you use the sun option as a trigger then jump to step 5.
-
Click on the 3 dots and select edit in YAML.
-
We are looking for the line ‘include_light_control: dont_use_brightness’. If you don’t see it then you are all good nothing more to do if you see it go to step 4.
-
Delete the line ‘include_light_control: dont_use_brightness’, click save then the 3 dots and select ‘Edit in visual editor’. If you need to make any changes do so, if you use the sun option as a trigger then go to step 5.
-
Scroll down to the sun option. You will see you have 2 inputs now called ‘Sun Elevation Falling’ and ‘Sun Elevation Rising’. Adjust to your liking.
If you like this blueprint? Consider hitting the 
button in the top post 
If you like my blueprints, and would like to show your support or just say thank you? Click Here 
Enjoy
Blacky
I’m a newb to HA and trying use this blueprint to turn on and then off a light in my office. I don’t know what I’m doing wrong. The device I’m using is a TP-Link P135 wall plug with dimming.
alias: Office Light On & Off
description: Scheduled light on and off for workdays
use_blueprint:
path: Blackshome/entities-on-off-trigger-conditions.yaml
input:
light_colour_temperature: 2700
entity_switch:
entity_id: switch.office_light
light_transition_off: 15
light_transition_on: 0
after_time: "10:30:00"
before_time: "10:35:00"
weekday_options:
- mon
- tue
- wed
- thu
- fri
include_light_control:
- dont_use_brightness
include_time: time_enabled
include_weekdays: weekday_enabled
Welcome to the community.
Thanks for providing your YAML.
Everything looks good and I have tested this and it is working. I used version 1.8 but it should work on version 1.7. Note your ‘TP-Link P135 wall plug’ is a switch so the light control will not work on a switch. Maybe this is done internally within the ‘TP-Link P135 wall plug’.
Not sure if you have updated to the new version 1.8 or not but if you have then you can clean up some YAML by removing the code below.
include_light_control:
- dont_use_brightness
Here is your full YAML with the code cleaned up for you.
alias: Office Light On & Off
description: Scheduled light on and off for workdays
use_blueprint:
path: Blackshome/entities-on-off-trigger-conditions.yaml
input:
light_colour_temperature: 2700
entity_switch:
entity_id: switch.office_light
light_transition_off: 15
light_transition_on: 0
after_time: "10:30:00"
before_time: "10:35:00"
weekday_options:
- mon
- tue
- wed
- thu
- fri
include_time: time_enabled
include_weekdays: weekday_enabled
Blacky
Hello Blacky,
I think I found the issue. Using Edge I created Home Assistant webpage as an app so I could pin it to my taskbar and it opens like an app. I have noticed that when updating some items it doesn’t work in app mode. So I opened the HA webpage through the browser and did the update there and it worked. I also copied your version of yaml but don’t think that was the problem.
Thanks for your help and the blueprint.
Thanks for the help.
Nice one and thanks for letting the community know and for getting back to me
Your welcome
Enjoy
Blacky