It seems that the Sun Elevation setting is not working. I have a schedule for the trigger to turn on a lamp but it shouldnât turn on until Sun Elevation is -1.5 degrees. Sun elevation is way above that currently, but still the lamp is turning on.
I definitely did. Good catch! However, the sun elevation was at around 15 degrees when I posted this. It seems it still shouldnât have triggered, but I may be understanding the settings incorrectly?
Try rebooting your HA sometimes things get messed up. Take note of the sun elevation before and after a reboot. I tested it here again and it is working perfectly.
Hi
Thanks for the quick reply, Iâve removed the other code from my original post.
I have the timer set at 5 minutes using the blueprint. The issue I seem to have is that the lights turn off after 5 minutes - regardless of whether motion is detected or not within those 5 minutes. The other blueprint I had the code from has a reset that resets the timer/script if movement is detected within the 5 minute timer period.
The effect of this is, the lights turn off after 5 minutes regardless of movement detection during the 5 minute timer. My wife or I have to move or wave a hand at the motion sensor to re-trigger the automation for another 5 minutes.
With the reset in place, the light doesnât go out after 5 minutes if motion is detected during the 5 minute timer period as it gets reset and starts over.
Thanks for sharing your YAML and removing the code. I see the issue: you are using a device in your Lights - Switches - Scenes - Scripts section. Devices are not supported here; you need to select the specific light entities instead. Also, since youâre using light control, make sure your entity is a light, not a switch.
Additionally, note that the automation should not have run when you selected a device. Ensure that no other automation is triggering it. If so, you may need to remove or disable that automation.
To resolve this, you can expand your device to select the light entities. Hereâs a helpful guide on how to do that: Click Here
Hi, just wanna give you a hand and say what a fine blueprint with so many options. I have 1 question, dunno if you can help me achieve it @Blacky.
Iâm trying this blueprint with my Aqara fp2, i have multiple zones, 1 zone i want that the lights go on if the zone(motion) is occupied for like 10 seconds, so the condition is that the motion trigger needs to be at least 10seconds active before the automation can proceed to execute. You have any idea how i can achieve this with you blueprint?
You will have to create a template sensor with a delay on for your motion sensor. Then use it in the trigger. The template example is for a camera but it works the same to what your are trying to do. Click Here
FWIW: I actually still have the same problem with night light scenes not activating from the automation even though using scripts that activate the exact same scene does work. This is only in the night light flow, although I donât seem to use scenes in most other places anyway (just scripts). Certainly not a showstopper by any means. Iâm just adding this to the thread in case it appears that the original report was considered dead. Iâm fine with using the script.
I am using your dynamic lighting to adjust the light levels in the room based on the lux value between a certain timeframe. However, once the automation ends, I want to keep the lights at its current state.
The bypass is not useful as it would pause the automation which is not something I would desire.
I could also see this option useful in saying chaining multiple of your blueprints for more complex lighting situation.
PS. Sorry if the option is already there and I may have missed it.
When the automation ends it turns the lights OFF unless you pause the automation but thatâs something you donât want to do. So you will have to turn the light ON manually when the automation ends. If you are using a time frame then you can use the smart light BP to turn it on at the same end time.
Hi @Blacky , still loving your automations. Using four of them on a regular basis and cannot think of how life has been before
Quick question if this is feasible before I order any more contact sensors: when using the toilet, sometimes the light goes off because I do not move soon enough for the motion sensor to keep the automation running (I know - bad habit to take your phone to the restroom with you ). I do notvwantbto change delays or anything as the settings work very well in general when I use the bathroom.
Now, to keep the lights on while using the toilet, I thought about adding contact sensors to the lid of the toilet and somehow add the sensors state (via a helper) to the automation to keep the lights from going off.
However, I am not quite sure if I can just use the âBypass Switch - Turn Lights ONâ? I also use a helper for bedtime as âBypass Switch - Turn Lights OFFâ which prevents the lights from turning on when this helper is active.
I akso looked to use your blueprint âCloset, Pantry, and Cupboard Lightingâ but there is no illumination option for a motion sensor which would mean every time I open the lid, the lights would turn on, meaning also when it is bright enough in the first place (except for when the bedtime helper is active of course).
So long story short: How can I keep the lights on while using the toilet without compromising the comfort of my current setting?
Is it possible to have the time delay stored in a input_number? I tried using time_delay: {{ states('input_number.bevegelse_timer_gang') }} with and without casting it to float.