💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

Blueprints Exchange
, , , ,
1601

Hi Blacky, can you see why this isn’t working again? For a post HASS restart?

different to yesterday. this is a light that has a scene enabled for the on and off commands.

image
image875×294 18.4 KB

image
image668×586 21 KB

image
image898×219 13.7 KB

Tested by also using the same automation in another room. The one that did work before. That still works and looks to be identical.

image
image933×724 41 KB

image
image906×359 14.9 KB

Another one for a light on a simple on/off also failed:

image
image932×386 18.7 KB

image
image933×382 15.2 KB

Cant figure out why some worked not others. All ad motion triggered shortly before the HASS restart. Only the Kitchen LED did work.

1 Like
1602

Hey, just another thank you for the blueprint. I just loaded it yesterday and am only working with one bulb so far. Many options! Great work! Works great, once I fixed my mistake of entity vs sensor. :laughing: I also just loaded your sensor light add-on. Both appear to meet and exceed my needs.

1603

Just responding to my own post to help anyone that may be trying to do the same thing.

1-2. No need for a helper if HA recognizes your TV. Just set it as the entity in the bypass.
3. No need for a new template binary sensor.
4. Create 2nd automation with lights as required. Use the new Turn Light, Switch or Scene On or Off automation.
5. Add the TV as the entity into the 2nd automation by-pass option 3.

Works perfectly. It’s like magic!

1604

@johnwang16

Okay, thanks John :+1:… I will have to add this to my list so I can test it. Currently I have completed the next release and working through final checks so I am not sure if I will get to this before then but I will look into it.

Stay turned.

Blacky :smiley:

1 Like
1605

@richsimpson

Yep I know what that is. Because you are using scenes only and the way scenes are handled in HA the automation can’t tell if it is ON or OFF. The good news is I have been working on this and it has been resolved. Stay turned for the next release that will be out soon. If you can’t wait for it then what you can do is just add one light entity used in the scene into “Lights - Switches - Scenes - Scripts” and “Night Lights”.

Blacky :smiley:

1606

@G2740

Hi Dave, it is realy nice to get this type of feedback every now and then without any questions. Glad you like it and thanks for yore kind words :smiling_face_with_three_hearts:

Stay tuned for the next release to be out soon.

Blacky :smiley:

1607

@kman42

Love it :+1:… looks like your are getting the hang of the blueprint… nice work and thanks for the update.

Blacky :smiley:

1608

FAQ: How to use the Ambient Options

What are Ambient Options?

The Ambient Options set conditions that restrict automation to run only when it is dark or below specific ambient light levels. These levels are typically measured in LUX, and such sensors may also be referred to as LUX sensors. These are global conditions and can work alongside other selected conditions if configured.

Ambient Light Sensor

Using a primary outdoor sensor to detect the actual outdoor LUX value can be beneficial, as it allows you to apply a consistent measurement across all lighting automation setups. Indoor sensors may be used when the outdoor LUX value is not relevant, such as when lights are used in enclosed spaces like a garage or when blinds are closed.

Ambient Light Sensor - Site Conditions

Sometimes, when lights turn on, they can affect the ambient light sensor, increasing its LUX value and causing the lights to turn off prematurely. To address this, select an option that best suits your installation.

NOTE: If you are using a buffer zone between the high and low lux values, select “NO” for this option.

Ambient Light - Low & High Lux Values

These settings allow you to create a buffer zone between two lux values to manage light activation and deactivation more effectively.

  • Ambient Light - Low Lux Value: Set this value to determine when the lights should turn ON. The light will activate when the lux level falls below this set value. This value should be equal to or lower than the “High Lux Value” below. A typical guide value is 20 lux (dusk).

  • Ambient Light - High Lux Value: Set this value to determine when the lights should turn OFF. The light will deactivate when the lux level rises above this set value. This value should be equal to or higher than the “Low Lux Value” above. Setting a higher value creates a buffer zone to prevent immediate light deactivation. A typical guide value is 80 lux (dawn).

Enjoy

Blacky :smiley:

Back to FAQ: Click Here

Back to “The Settings & Best Practice Guidelines” Click Here

1609

I will look out for it. though the last one is screenshot for Utility room failed and is also a simple light and motion sensor. no Night mode, just on and off.

1610

Just shifted all the ones with scenes to a simple light. Using the relevent colour and brightness levels.

They don’t survive a restart. Just stay permanently on.
Could it be that because the lights are on a zigbee2mqtt connection that the automation starts too soon, before the lights state is recognised as being on?

image
image885×767 31.5 KB

image
image881×387 18.9 KB

Perhaps a longer or configurable delay is needed to deal with how long it takes HASS to settle after a reboot?

1611

@richsimpson

That could be the case. In this next update maybe try and put in some toggle helpers into “Scenes & Scripts - Toggle Helper”.

Let me know if that works.

Blacky :smiley:

1612

New update 5.9

Your lighting experience, your way – take control and customize it to perfection! :bulb::sparkles:

New Feature :new:

Changes to Scenes & Scripts

We have added three new inputs.

  • Scenes & Scripts - Toggle Helper
  • Night Lights - Scenes & Scripts - Toggle Helper
  • Yes - Manage OFF script when crossing over

The purpose of adding these inputs is to ensure the proper functioning of automations when using scenes or scripts. The benefits of adding these inputs include:

  • You can now adjust the lights associated with your scenes and scripts after they have been activated, preventing them from resetting with each trigger.
  • With the addition of these inputs, you can create glow lights for night settings within a single automation, eliminating the need for multiple automations. A detailed guide on this process can be found Here.
  • When using scenes or scripts in conjunction with ambient options, selecting “Yes” for your site conditions will ensure that your lights remain on when the LUX value goes high.
  • There’s no longer a requirement to add just one entity in “Lights - Switches - Scenes - Scripts” or “Night Light”. Simply incorporate a toggle helper into the new “Scenes & Scripts - Toggle Helper” inputs.
  • By including “Yes - Manage OFF script when crossing over” in the night lights lighting control options, you can ensure that a script runs smoothly when transitioning between normal lights and night lights, even when the lights are off, allowing for different OFF settings to be applied.
  • Home Assistant (HA) restarts will now recognize whether your scenes or scripts lights are ON and perform the correct actions. This feature can also be helpful when using lights or switches on different platforms, as HA may take longer to recognize their ON status after a restart.

Maintenance :toolbox:

  • From your feedback to create a manual we have updated a lot of input descriptions to better help understand what they do and also provided more links directly to the blueprint FAQ’s. This will hopefully help you find what you are looking for when setting it up.
  • Code realignment.

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:

2 Likes
1613

Awesome @Blacky I do have a feature request for your add-on movie theater blueprint. Reed’s smart home on YouTube had a new video that does a similar thing to your blueprint, BUT he added the ability to have different lights/scenes based on the app on the Apple TV or Chomecast that is open. For example, for Spotify or Apple Music you could not dim the lights, but with Netflix, do a full movie dim. I think app specific conditions would be amazing.

1614

@DuckDuck25

Thanks for your suggestion. I will look into it :+1:

Blacky :smiley:

1615

FAQ - How To Create A Toggle Helper?

When using scenes and scripts, it is recommended that you create a toggle helper. Below, I’ll show you how to do this.

Go to Settings / Devices & Services / click on the “Helpers” tab at the top / create helper and select toggle.

27
27551×542 28.7 KB

Input the name you would like to call it, select an icon if you like and click create.

28

Enjoy

Blacky :grinning:

Back to FAQ: Click Here

Back to “The Settings & Best Practice Guidelines” Click Here

1616

FAQ - Setting Up a Schedule Helper with Sun Condition

You can use a schedule helper as the trigger. Below, I’ll show you how to do this.

Go to Settings / Devices & Services / click on the “Helpers” tab at the top / create helper and select schedule.

93
93549×542 27.2 KB

Input the name you would like to call it, select an icon if you like and click create.

94
94333×518 31.7 KB

If you would like to turn your your lights, switches, scenes, or scripts ON when the sun sets, then you would select a time well before the sunset and enable the sun condition. This ensures that the trigger is ON well before the sun sets but waits for the sun condition to turn your light ON. Then, the schedule will turn your lights OFF as per your schedule.

Example

This will activate your lights, switches, scenes, or scripts when the sun elevation is below -1.5 because the trigger schedule is active having an ON time 4pm. Conversely, it will deactivate them at the end of your schedule, well before the sun rises above -4.0.

95
95335×518 31.1 KB

96
961041×310 74.1 KB

Enjoy

Blacky :grinning:

Back to FAQ: Click Here

Back to The Settings & Best Practice Guidelines Click Here

1617

I have a timing problem that I need help with.
I would like the automation to be active between 5 am am 8 am, than again from 4 pm to 9 pm. The automation is off otherwise. How can I achieve this? Time settings only allow one time range. I need it to be triggered by the motion Detector, so a schedule helper doesn’t seem to be the answer.

1618

@rananna

You can use a schedule helper but your ON time will be the opposite to when you would like the automation to be active. Then you would put the schedule helper into the bypass option 2. Below is a example of the schedule. Then you wouldn’t use the time option :wink:

97
97337×520 35.2 KB

98
98335×516 30.9 KB

Blacky :smiley:

1619

This is just great. Just what I needed. Thank you so much for this. :partying_face:

Unfortunately I think I may have found a bug in Version 5.9 of this blueprint. This will prevent to turn ON lights using bypass ON.

To reproduce use blueprint with scripts to turn on, therefore a toggle helper and a bypass ON and bypass OFF helper.

  1. Turn lights on by enabling bypass ON.
  2. Turn lights off by enabling bypass OFF. (and disabling bypass ON)
  3. Turn lights on by enabling bypass ON.

Expected
The light turns on again.

best regards

Actual
The light stays off. I noticed, the toggle helper is still on. If I turn the toggle helper off manually, the lights turn on again.

1620

Thank you. That works great!