🔆 Smart Light - Entity - Sun Elevation - Ambient & Time Triggers

Blueprints Exchange
, , , ,
18

It is actually working pretty much as I want now. :+1:

19

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.

20

Hi Stevie, that is good news :+1:

21

@zebrahosting

I think you may be after my other blueprint. Have a look at this one.

:bulb: Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time

22

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?

23

@beloso

Hi Tiago, have a look at another one of my blueprints called :snowflake: Temperature Control Exhaust Fan - Inverted. I think this is what you are after.

24

I’ll try it, it does seem to be able to accomplish my idea. But the name kinda threw me away xD.

25

Yea the name will throw you, but when saving it you will have the option to rename it.

Good luck and hope this helps you.

Blacky :smiley:

1 Like
26

Good point. I’ll do that.

Much appreciated for your work in these fine blueprints.
I use Sensor Light as well.

1 Like
27

New update 1.5

:warning: BLUEPRINT CODE UPDATE :exclamation:

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. :wink: :+1:

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning:

28

Hi

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

  1. The Alarm systems “sunset flag”
  2. The alarm systems mode (ie, dont trigger if set to night mode).

Thanks,
Eamon

29

Hi @Wexfordman

I would have to add this option in. Give us a few days so I can have a look at it and I will get back to you.

Blacky :smiley:

30

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.

31

New update 1.6

:warning: 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 :new:

  • 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 :new:

  • Global Condition: You can now add in any global condition you like.

:warning: :stethoscope: STEPS REQUIRED WHEN UPGRADING :white_check_mark:

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
31643×578 113 KB

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.

4
41663×379 74.7 KB

4 - We need to delete the 2 lines, click save then the 3 dots and edit in virtual editor.

5
51669×887 93.3 KB

5 - Then you will need to enable the entity state option and enter in your binary sensor again into input entity.

7
71041×220 43.3 KB

6 - Click save, you’re done. Now just do the same in your other automations using this blueprint.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning:

1 Like
32

Thanks blacky, will give it a go over the weekend

1 Like
33

Awesome… Thanks, @Blacky for your blueprints. I think I use all of them now :slight_smile:

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?

34

@beurdy

No it will not work that way.

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.

Blacky :smiley:

35

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…

36

@beurdy

O okay, let look at a few things then

EDIT: Update to then new version 1.7 and set a dead ban between ON lux value and OFF lux value. Could you please provide some feedback here if it now works.

With the problem of the light coming back ON try and use the global conditions and set the sun as a condition. This should disable it 1 hour after sunset and it should be dark and enable it at sunrise to start the day again. So during the day it will work, once it gets dark the condition stops it so when you turn your light ON / OFF at night it will just be manual control. The light will still turn ON at when it gets dark at night (1 hour offset) but you will have to turn it OFF manually when you go to bed.

1

Blacky :smiley:

37

New update 1.7

:warning: Some work is required in this upgrade see below.

Upgrade Features :new:

  • Ambient Light Sensor: We have now added a LUX value for ON and OFF. You can now set a dead ban so you light doesn’t turn ON and OFF to fast on a cloudy day.

    :white_check_mark: Below shows the OFF value higher than the ON value. This will work :+1:

    6
    61041×398 71.1 KB

    :white_check_mark: Below shows the ON and OFF values equal. This will work :+1:

    5
    51040×396 68.1 KB

    :x: Below shows the OFF value lower than the ON value. This will not work :-1:

    4
    41043×400 67.7 KB

:warning: :stethoscope: STEPS REQUIRED WHEN UPGRADING :white_check_mark:

If using Ambient Light Sensor then you will need to set your OFF value. Below shows a dead ban of 80 lux.

2
21041×398 69.4 KB

If you would like to keep it the same before this update then set the OFF vale the same as the ON value. Below show the setting the same as before the update.

3
31038×396 68.6 KB

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning: