To create what your after it is best to use the Sensor Light blueprint. I think this is what your after.
Turn on when LUX below threshold
Turn off when LUX above threshold
Do not run this automation between 10pm and 6AM.
Download the sensor light blueprint. Then create a time of day sensor helper or a schedule helper. Time of day sensor helper is one time and easy and Schedule helper gives you more flexibility for each day and is also easy but it all depends on what you after.
Go to Settings > Devices & Services > Helpers.
Click “+ Create Helper” and choose the helper you would like to use being time of day sensor helper or a schedule helper.
Then the time you would select is from 6am to 10pm. The helper will be ON at these times and OFF between 10pm to 6am.
Use this helper in the sensor light blueprint (not this one) as the trigger.
In the meantime, I've solved my lighting control using "normal" automations
Going back to the blueprint wouldn't work for me right now, as I've incorporated a fairly complex logic regarding the motion detector, time, and button (single/double press).
I am trying to configure the automation with an push button (input_button) entity as trigger but the lights go on and directly off again? I checked both "Push Button ON" and "Push Button OFF" so it can toggle the lights. Am I doing this wrong?
Not necessary wrong but it's something your not noticing. I have tested it here again and it works perfectly. Make sure something (another automation) is not linked to the lights turning it OFF. Best way to find this is go into your automations and filter it as last triggered then trigger the automation using the button and see if something also ran at the same time. Failing that provide us the YAML of your automation settings and I will have a look at it.
I would like to use the Smart Light blueprint combined with my Enocean (friends of hue) switches in such a way that there is no extra helper for a switch (only a stateless push button). In that way I can by example still use the light entity to switch off the lights without anything runs out of sync.
Apologies if something like this has already been posted (625 replies is a lot to skim). In the winter, this blueprint works great for me - I have it set to use elevation to turn on the porch light at dusk and turn off around 8:30, which is the latest I'd expect a delivery or guest at my door. But, I'm in a particularly stupid time zone where civil twilight can be as late at 9:30pm in the summer, so the automation is turning on the porch light long after the kids are in bed and because it triggers after the "on" time, it leaves the light on all night if I don't catch it.
I can of course just use a regular automation for this one light, but I'm curious if there's an existing way to either not turn on the light if the "sun elevation on time" isn't reached until after a specific cutoff time?
This blueprint won't look at that condition. You could do your own regular automation but if you like to take full advantage of the other options and you like to use a blueprint of mine then I would recommend using the Sensor Light blueprint.
Your approach would be different though because of your time zone.
What you would do it to use the sensor light blueprint and then you can create a schedule helper or a times of day sensor helper. The time you would set is say 4pm to 8:30. 4pm being well before dusk, if not 3pm or whatever your time zone dictates. Use that helper as the trigger in the sensor light blueprint (not this blueprint). Then set up your lights and the Sun Elevation. this will stop the problem your describing as it can only run between 4pm to 8:30 if the sun condition is true as the sun elevation is now a condition and not the trigger.
If your unaware of helpers then you can find them in
Settings > Devices & Services > Then the Helpers tab at the top. Then just create the helper of you choice. The difference between the helpers are;
times of day sensor helper = one easy ON and OFF time everyday. schedule helper = Any ON and OFF time on any day as many as you like and can be different for Friday, Saturday and Sunday for extended time for guests.
Apologies if this has been asked before - there's a LOT to parse and find on page didn't come up with anything.
I'm trying to automate lights turning on at a specific time and ramping up brightness. This part is solved. What I want to add is a way to only have them trigger on work days and to skip holidays.
I have the Holdays integration configured, but can't figure out where to add that as a trigger.
Your after my Sensor Light blueprint. This allows you to set conditions. You may decide to use the state trigger so you can configure "only have them trigger on work days and to skip holidays". Then you just need to decide what will trigger it. Note you can use an input boolean and turn it ON so it is always active but the condition stops it.
I’m not sure if there is something in my setup but I’m still seeing this same behavior with 3.5 now I’ve got to the time of year where my fixed turn off (10pm) is occurring before the sun is low enough to turn on the lights so they turn on and nothing to turn them off.
Because this blueprint is trigger based you may find that my Sensor Light blueprint will work better. You can use a toggle helper as the trigger and then just turn ON the toggle helper so the blueprint is always active, then use the time and sun elevation settings and you may find this will always work in your time zone.
PS: to add a toggle helper you will need to add any trigger first then edit in YAML the automation and replace the trigger entity with your toggle helper entity.
Sensor Light blueprint. I think this is what your after.
