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
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.
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.
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.
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?
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.
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
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
The Alarm systems âsunset flagâ
The alarm systems mode (ie, dont trigger if set to night mode).
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.
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
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
Global Condition: You can now add in any global condition you like.
STEPS REQUIRED WHEN UPGRADING
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.
Awesome⌠Thanks, @Blacky for your blueprints. I think I use all of them now
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.
Edit:
Can you add the option that the illuminance sensor is influenced by the light? Just like you have in the other blueprint?
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.
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âŚ
BLUEPRINT CODE UPDATE 
button in the top post 
STEPS REQUIRED WHEN UPGRADING 
