Hi Blacky! Once again - thank you for all your work on the blueprints. As you can tell Iām working my way through all of them and replacing my multiple convoluted automations with your simple and structured blueprints
Iām considering replacing my 3 automations with what I think can be done with this single blueprint, which does the following:
At sunset, turn ON 4-specific lights, if there is anyone at home
At sunset, if no one is at home, turn ON only 2-specific lights (for the dogs )
If we leave the house after sunset, turn OFF all lights leaving just 2-specific lights ON
When returning home after sunset, turn ON 4-specific lights (similar to case 1)
Scenarios 1 & 2 seem like they can be done fairly straightforward through the sun elevation trigger and appropriate global condition of zone.home.
Scenarios 3 & 4 - am I right in assuming I have to use the entity state option (I have a āpersonsAtHomeā group which reports āhomeā and ānot_homeā I can tie to a ON/OFF toggle helper) to trigger these? Am I on the right track here? Hopefully this isnāt too confusing!
Best to use the sensor light blueprint with probably a schedule for the trigger and sun condition and device tracker. The 2 lights to leave ON without device tracker.
TIP If you use a schedule helper then you can set the time before sunset and OFF later in the night or after sunrise. Then when you select the sun condition it will trigger the light ON / OFF if someone is home. Device tracker will turn the lights ON / OFF when you arrive or leave home if the trigger is ON and it meets your sun condition.
I guess this is best asked in the other blueprint discussion, but just for continuity -
After a bit of playing around, the 2 lights ON without device tracker and scheduled trigger works perfectly.
The other 4 however partially works. When people at home during sunset it works fine. When everyone is away and someone enters home zone after sunset, it doesnāt trigger. Iāve set up the automation as follows: scheduled trigger (well before sunset and just before sunrise), sun elevation enabled, device tracker enabled (tested both zone and zone+people). Am I missing something? Another trigger perhaps?
Iāll provide two examples: one for stairwell lighting and another for family room lamps. These examples will illustrate how you can use the new blueprint to create customized lighting solutions for different areas of your home.
Stairwell Lighting
Imagine your stairwell lights automatically glowing as the sun sets, and smoothly transitioning to OFF when the sun rises. Hereās how it works:
ON: The lights turn on at sunset with a soft 10% brightness.
Motion Detection: When motion is detected, the brightness ramps up to 50%, brightening your path.
Motion Cleared: Once motion is cleared, the brightness dims back down to a gentle 10% glow.
OFF: The lights automatically turn off when the sun rises.
This setup ensures your stairwell is always appropriately lit while saving energy when not in use!
Below is how you set it up:
First, we set up our sun triggers for both ON and OFF.
Finally set your light control options to use brightness, transition and If lights are ON, adjust the lights when crossing over. If desired, you can also adjust the colour settings here.
That night, make sure to test everything to ensure itās working correctly. Then, sit back, relax, and let the automation handle your family room lighting!
Get ready for a game-changing update! Weāve rebranded and revamped everything, so much so that the old blueprint has officially retired. Introducing the all-new Smart Light blueprint!
This is not just an upgrade; itās a complete transformation. Weāve taken all the fantastic features from our sensor light blueprint and supercharged them with even more exciting trigger options. Imagine having the flexibility to mix and match triggers to perfectly suit your needs!
For example, you can set your lights to turn ON based on the sunās elevation and OFF based on time. The possibilities are endless, and the control is all yours!
Dive in and discover how this new blueprint can be tailored to your unique lighting needs. You wonāt want to miss out on this incredible upgrade!
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
Great update Blacky! Quick question - my use case is for our outdoor lights. Turn on at sunset and then off at a specific time depending on the day (weekday or weekend). However I do want to use a device tracker condition so that these lights donāt turn on when no oneās home. I guess in this case its best to stick to the Sensor blueprint with the schedule trigger? Or is there a way I can use a device tracker group helper as the entity here? Thanks!
PS. thereās a typo in trigger-time section (NO time instead of ON time).
This blueprint is very different to the sensor light blueprint. I think if the sensor light blueprint is working well then maybe leave it alone but if you got an itch and would like to test it using the same bypass we talked about in the sensor light blueprint then try it out and let us know how you go. The conditions for this was a bit tricky and it may just work. I havenāt tested that scenario but it would be nice to know.
Thanks for letting us know I realty appreciate it, my bad It has been fixed if you push the update PB again
Hey there, so I just got this blueprint installed, and Iām having a little confusion. Weāre trying to use this to control lights for tropical plants and want to keep it on a dawn/dusk cycle (or sunrise/sunset, but from my understanding it seems thatās not recommended for whatever reason).
If Iām following the coding for the sun elevation script itās actually being used to turn the lights -on- at night and off in the day (which makes sense from an outside night light scenario) Am I reading this right or am I off base?
If Iām reading right, what would be the best way to address this so it triggers in the opposite direction?
Here is my current YAML to help with troubleshooting:
At the moment I worked around it by making a input toggle to match the sun state and used the entity setting as a workaround, but I suspect this can work as desired
The sun trigger only turns the light ON at sunset and OFF at sunrise. The way you did it is a good workaround if you would like it to turn ON at sunrise and OFF at sunset.
first of all and as always: @Blacky thanks a million for your blueprints!
and secondly a question (of course )
my requirements:
my outdoor balcony lights should turn on when the ambient brightness in the living room is below 10 lux and turn of when itās getting brighter again (above 15 lux). This should only happen between 6:30 in the morning and 22:30 in the evening (letās call it daytime)
How to achieve this?
I think the Trigger-Time is only appropriate to switch the lights off at 22:30. But it could not enable the automation at 6:30. Am I right here to state that this wouldnāt work
I am considering using Night-Time and setting the brightness to 0. which would mean I need to set the brightness at daytime to e.g. 100%.
That would work as long no one changes the brightness during daytime to eā¦g 50%, then the ambient settings turn the lights off and on again, in this case brightness would be set again to 100%, but not to 50% as they were before.
How could I implement my requirements? Is there anything I could do within the blueprint based automation?
or do I need a scheduler that switches off the lights at the start of nighttime (22:30) and deactivates the automation, and another scheduler to activate the automation at the start of daytime (6:30)?
Well I do have dynamic lighting that works of the sun elevation during the day so it make sense to also include this as a trigger option. Yea I will put it on the list to add in.
Even though this PB looks like the sensor light PB it is very different. This one works of your chosen triggerā¦ example I use it to turn on my family room, kitchen lamps when the sun sets and then turn OFF at 11:00pm. Time is not a condition in this PB but a trigger and the only condition is weekday.
The best way to achieve what you are truing to do is use the sensor light BP (not this one). In your trigger use a schedule or time of day helper for 6:30 to 22:30. Then set up the ambient to your liking. That BP will turn ON and OFF everything perfectly for you.
Awesome! I was at my sisterās tonight where I first used your script and when it hit dusk I kind of freaked as all the plant lights turned off, then was like āoh yeah, I guess that means the patch is working as intendedā
Currently not a selection option.You could use the bypass to turn your lights OFF for winter, just need to create a template sensor for itā¦ Can I ask why? what is it for?
I have a switch that keeps on every night, but I only need that in the summer. (and tbh if thereās a way to automate it it would be amazing.- if not itās not that big of a problem)