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

Blacky · April 14, 2023, 11:44am

Try and expand your devices and use entities. It is always better if you can use entities. I find having “area” and “devices” is a quick way to find your entities.

The expand button is here

Mar1us · April 14, 2023, 12:03pm

I don´t think thats what i search for. Here a bit more in detail:

I have an automation that active a bulb at 8PM.
As soon the motion sensor is detecting motion the bulb should be active a scene.
After a period of time the bulb should go to the level of brightness from 1.
At 11pm the light will be off.
same behavior like 2.
After a period of time the bulb should go to the stat of off (4.)

So it would be great to store the state of the bulb before the activation and set this after the time after motion.

Blacky · April 14, 2023, 12:54pm

Hi @Mar1us

This is a custom automation but you still can do it with this blueprint and another one of my blueprint. It is simpler to André question above.

Below example is if your using the same light/s in everything.

First you will need to download another one of my blueprints called Turn Light, Switch or Scene On & Off with Trigger Conditions. This will be used for your (1) ON at 8pm and (4) OFF at 11pm. Set it up for this time. Then set up a scene for your ON (1) and put that in “Lights - Switches - Entities - Scenes”. We will call that scene “scene 1” for this example but you can name it anything you like. Then create an identical scene with everything OFF and put that into “Scenes To Turn OFF”

Once that is done Use this blueprint (sensor Light) for (2) and (3). So for (2) you would create a scene and set the brightness level you like and put that in “Lights - Switches - Scenes”. Then enter “Scene 1” used in the other automation and put that into “Scenes To Turn OFF”. Set the time under “Use The Time Options” to only run between 8pm and 11pm.

Now use this blueprint (sensor light) again and create another automation for (5) and (6) this time you can use a scene or not and set up the light to come ON and OFF as you like. Set the time under “Use The Time Options” to only run between 11pm and 8pm (note the reverse time).

With the 2 automations using the blueprint (sensor light) you can also set the other options if you like. Example “Use The Sun Option (Optional)”.

Hope this helps you.

Let us know how you go.

Blacky

NickM · April 14, 2023, 9:50pm

Very nice blueprint here! The only thing i’m missing here is to make the lamps go to there previous state. Or am i looking over this?

geox19 · April 14, 2023, 9:54pm

I think two post up explains how to achieve this. Didn’t read it real close yet but I’m thinking that’s what Blacky is explaining

Blacky:

Andre3000:

The goal is that for example if the sun goes down OR a specific lux value a light group should go on at 20%. With detected motion the lights should go to 100% and back again to 20% after few minutes without motion detected. As soon as the sun goes up or again specific lux value the lights should turn off.

Currently you can’t do what your asking in just this one blueprint, but there is a work around.

This is how you would do it. In this blueprint (sensor Light) create a scene with 100% lights and put it into “Lights - Switches - Scenes”, then create another scene with 20% lights an put it in “Scenes To Turn OFF”. Now set your option, sun goes down OR a specific lux value.

Now you will need to get another one of my blueprints called Turn Light, Switch or Scene On & Off with Trigger Conditions. This will turn it on and off on a trigger condition when the sun goes down OR a specific lux value. Once you got the other blueprint enter your scene of 20% in “Lights - Switches - Entities - Scenes” then create another scene that turns everything off and enter it in “Scenes To Turn OFF”. Now set your option, sun goes down OR a specific lux value.

The 2 blueprints will work together and give you what your asking

Hope this helps

Edit: Let us know how you go.

Blacky

Blacky · April 15, 2023, 9:39am

FAQ - The Settings & Best Practice Guidelines

Trigger Sensor - Binary Sensors

The trigger sensors are responsible for turning the lights, switches, scenes, or scripts ON and OFF. You can choose any Binary Sensor you prefer as triggers. Alternatively, if you prefer a time-based trigger, you can also add a schedule

For more information + Pro Tips Click Here

On how to set up a schedule helper and a pro tip to use it with a sun condition please click here.

NOTE: When adding multiple trigger sensors, in particular a sensor that can remain in an ON state for long periods of time, it is recommended to group these sensors together as the automation will function correctly. Sometimes depending on many factors, just having 2 or more trigger sensors prevents the automation from function correctly and grouping these sensors together helps. For more information on how to set up group sensors please click here. If you would like to know more about groups and why we use them then please click here. Example of these sensors are;

Presence sensor
mm wave sensor
Contact sensor
Door sensor
Window sensor
Garage door sensor
Motion sensors with long inbuilt delays

If you find your trigger is not triggering the automation then see below under “Lights - Switches – Scenes - Scripts”.

If you would like to create a template trigger sensor so you can use it in the blueprint click here for some examples. This is a realy good read, and I would strongly recommend you take a look at it. This shows how you can make this blueprint even better. The ‘Bee In The Hive’ sensor is the one I realy love , it will take your automatons to the next level.

Lights - Switches – Scenes - Scripts

The lights, switches, scenes, and scripts that will be activated by the trigger sensor/s.

More information on scenes and scripts please click here

The automation exclusively supports entities. To conveniently locate your entities, you have the option to also select areas, devices and labels, providing a quick and easy method. Simply click the expand button " < > " as shown below. This expands your area, device or labels, allowing for a swift identification of your entities. Ensure your final selection is all green, containing only lights, switches, scenes, or script entities.

Areas

Devices

Labels

Entities

Scenes & Scripts - Toggle Helper

Scenes and scripts lack a discernible state within Home Assistant, making it challenging for the automation to determine their activation status. To address this, it’s recommended to use a toggle helper alongside scenes or scripts. This enables the automation system to recognize when a scene or script has been activated, ensuring smooth operation. When entering scenes or scripts in “Lights - Switches - Scenes - Scripts” or “Night Light,” it’s advisable to create a dedicated toggle helper for each input.

If you would like to know how to create a toggle helper then please click here.

Scenes - Scripts To Turn OFF

If you have selected a scene or a script to be turned ON above in “Lights - Switches - Scenes - Scripts” or below in “Night Lights,” and you would like it to be turned OFF after the time delay, then you must create a scene or a script with everything OFF and enter it here. See below example.

More information on scenes and scripts please click here

Time Delay

The time delay setting dictates how long the lights, switches, scenes, and scripts will remain active after all triggers have returned to their inactive state, effectively initiating the countdown to turn them off. Additionally, the time delay also acts as a buffer zone between trigger events, preventing the lights, switches, scenes, and scripts from turning off immediately when the trigger is deactivated. If you find that your lights are turning off and then back on again too quickly, consider extending the time delay. In cases where multiple trigger sensors are used and adjustments to the time delay aren’t effective, grouping the trigger sensors may be necessary. Click here to learn more about grouping trigger sensors.

Light Control Options

This allows you to select what option you would like to control in your light entity.

Brightness – Your light must be able to support brightness control by being able to dim the light in Home Assistant.
Transition – If your lights support brightness or colour temperature then this is the time it will take to transition to the next state. A state change can be from OFF to ON, from ON to OFF, from normal lights to night lights and from night lights to normal lights.
RGB - Your light must be able to support RGB colour by being able to adjust the colour in Home Assistant. You can choose RGB, RGBW or RGBWW.
Colour Temperature - Your light must be able to support colour temperature by being able to adjust the colour temperature in Home Assistant. Some LED lights that can change colour may also support colour temperature.

For each option you select you also have the ability to adjust the setting. More information is next to each setting.

If you have selected an option and your light doesn’t support it then the light will simply just turn ON.

Dynamic Lighting

This option aims to make continual adjustments in your lighting setup by modulating brightness according to floating lux values or adapting colour temperature and brightness based on the sun’s changing elevation. Choose from nine preset options available in the dropdown menu.

1 - Lux Controlled Brightness
2 - Lux Controlled Brightness Inverted
3 - Sun Elevation Lighting - Colour Temp
4 - Sun Elevation Lighting - Brightness
5 - Sun Elevation Lighting - Brightness Inverted
6 - Sun Elevation Lighting - Colour Temp + Brightness
7 - Sun Elevation Lighting - Colour Temp + Brightness Inverted
8 - Sun Elevation Lighting - Colour Temp + Lux Controlled Brightness
9 - Sun Elevation Lighting - Colour Temp + Lux Controlled Brightness Inverted

If you would like more information on dynamic lighting then please click here.

By-pass

The Bypass Option allows you to manually control your automation and override its normal behaviour. By switching on the bypass, you disable the automation’s automatic actions and take full control over your lights. This feature is useful when you need to temporarily stop automations from running or want to override their settings based on specific needs.

You have three input options:

Turn Lights ON: This will turn your lights on, regardless of the automation’s current state.
Turn Lights OFF: This will turn your lights off, disabling the automation’s control over them.
Keep the Lights’ Current State (Pause): This option ensures that the lights remain in their current state (whether they are on or off) and the automation is paused.

You can have more than one bypass and choose any input option based on your preference. However, ensure that you DON’T use the same bypass entity in more than one option. Each option must have a separate entity.

By-pass 101 - For more information on the by-pass then please click here.

Global Conditions

All the conditions are global and can work alongside with the other conditions. You can select one or all of them but if enabled each condition must pass for the lights, switches or scenes to turn ON. Example: If you enable all of them and one of them has not been met, then the automation will not run.

Sun, ambient & time can also trigger your automation. This will only happen when the “trigger Sensor” is ON at the time the sensor crosses over it setting. Example: If your motion sensor is ON (motion detected) and you are using the sun as a condition, if the sun is above the “Sun Elevation” setting the light will be OFF. If the sun then crosses from above to below the “Sun Elevation” setting then the light will be turned ON. The same theory applies for ambient and time and also works for turning your lights ON and OFF.

Sun - Can trigger the automation if the main trigger is ON*
This option is used to add a condition that only allows the automation to run when it is dark or below the ‘Sun Elevation’ settings.

I initially considered using Sunset and Sunrise, with a time offset but Home Assistant recommends using sun elevation for more consistent performance throughout the year. Following their advice, I opted for sun elevation. This is because the actual light level differs when using a fixed time after sunset or sunrise during winter versus summer. By setting a sun elevation, you achieve consistent light levels throughout the year.

If you would like more information on this and how to set it up correctly then please click here.
Ambient - Can trigger the automation if the main trigger is ON*
This option is used to add a condition that only allows the automation to run when it is dark or below the ‘Ambient’ settings.

If you’re seeking more detailed information on the ambient settings, feel free to click here.

If you would like to use 2 or more ambient light sensors and would like to know how to set this up correctly then please click here.
Time - Can trigger the automation if the main trigger is ON*
This option is used to add a condition that only allows the automation to run between the start time and end time settings on the selected weekdays.

If you’re seeking more detailed information on the time settings then please click here.
Device Tracker
Home Assistant can track the location of your devices (such as mobile phones) within a designated zone via the mobile app device tracker.

To utilize this option, you need to set up a zone and configure your devices for tracking in Home Assistant. There are two enable options available; “Zone” tracks all devices within the zone, while “Zone + People” allows you to track individuals within a zone.

This feature can be particularly useful if you have pets triggering the sensor, turning your lights ON and OFF when no one is home.

Night Lights

Night lights allow you to set different lights, switches, scenes or scripts by using a entity state, time or sun condition to choose when these lights will be active.

While some settings are similar to those of normal lights, night lights offer additional options tailored to nighttime lighting control. For further information on night light settings that resemble those of normal lights, please review the details provided above. However, for the unique settings exclusive to night lights, please see below.

Night Lights - Use The Light Control Options
- If lights are ON, adjust the lights when crossing over
Selecting ‘If lights are ON, adjust the lights when crossing over’ option ensures that the light control settings will be applied to any lights that are already ON during the transition from normal lights to night lights and vice versa.

If the ‘If lights are ON, adjust the lights when crossing over’ option is not selected, lights that are already ON when transitioning from normal lights to night lights will remain in their current state. This allows for situations where you may want the lights to stay on later at night or during gatherings without transitioning to night mode immediately. However, once these lights are turned OFF, the night mode settings will be applied the next time they are turned ON. While this option may suit some areas, it may not be preferred everywhere, providing you the flexibility to choose your desired scenario by simply ticking a box.

Regardless of whether this option is selected or not, if any lights are OFF during the transition from normal lights to night lights and their settings differ, they will either turn ON to the specified light control settings or turn OFF, depending on the configuration.
- Yes - Manage OFF script when crossing over
Selecting ‘Yes - Manage OFF script when crossing over’ is beneficial for scripts containing if-then-else actions that toggle various functions on and off during the transition from normal lights to night lights and vice versa.

If you’re seeking more detailed information on scripts with a working example and would like to know how to set this up correctly then please click here.
Night Lights Conditions

If you choose to “Enable entity state option” the night lights will be active when the selected entity is ON. If you choose to “Enable time option” the night lights will be active during the set time period. If you choose to “Enable sun elevation option” the night lights will be active when the sun is below the “Sun Elevation” setting. You can enable both conditions if you like but they both must be met for the night lights to work.

Note: Night lights will still have to pass all the global conditions set for normal lights.

For more information on the entity state, then please click here.
For more information on the time settings, then please click here.
For more information on the sun settings, then please click here.

Night Glow

This feature activates a low-level light when no trigger is detected, creating a subtle ambient glow perfect for nighttime use. When a trigger, such as a motion sensor, is detected, the light gradually increases to the night light’s brightness level, providing enhanced visibility and functionality without abrupt changes in lighting. You can also customize the light’s colour temperature or RGB colour for added personalization.

Note: Night Glow is only active when using Night Lights.

Hope this helps to explain some of the settings

Enjoy

Blacky

Back to FAQ: Click Here

Blacky · April 15, 2023, 9:48am

@NickM

Hi Nick, firstly welcome to the community .

As @geox19 reply, the previous post explains how to achieve this. The basic principle is by using scenes and creating a scene of what you would like at the end and put it into “Scenes To Turn OFF”.

Blacky · April 15, 2023, 10:59am

New update 3.1

If you are upgrading from version 2.8 and below please read the release notes of version 2.9 before upgrading as you will need to clean up a bit of code in the YAML. Click Here to see version 2.9 release notes. If you are updating from version 2.9 and above you good to go.

New Features

Transitions will now work with scenes. Now it will transition a light entity with a brightness setting in a scene.

Bugs Fixes

Fixed light flicker when crossing over from normal lights to night lights and from night lights to normal lights in a time trigger. Note: For the crossover to work only entities can be selected. Currently areas and or devices are not supported.

EDIT: If you updated in the first 35 min of this release, please update again, something (a bug) snuck back into the code. Sorry

Enjoy

Blacky

barcomoon · April 15, 2023, 2:27pm

Thanks for the great blueprint! The new version seems to be working although I do get some warnings in the log:

2023-04-15 16:25:10.010 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'entity_id' when rendering '{% set a = light_switch.entity_id %} {% set b = night_lights.entity_id %} {% if a and b %}
  {{ b | reject('in', a) | list }}
{% else %}
  []
{% endif %}'
2023-04-15 16:25:10.603 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hue_play_1, light.hue_play_1_2, light.hue_play_2, light.hue_play_2_2, light.hue_play_4 or it is/they are currently not available
2023-04-15 16:25:10.611 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hue_play_1, light.hue_play_1_2, light.hue_play_2, light.hue_play_2_2, light.hue_play_4 or it is/they are currently not available

Seems to happen each time the automation is triggered.

Blacky · April 15, 2023, 2:34pm

Hi @barcomoon

Firstly welcome to the community.

Could you post your YAML code. In automation, top 3 dots, edit in YAML, copy code and use the “</>” in this forum when pasting your code.

barcomoon · April 15, 2023, 2:58pm

Thanks!

Sure, thanks for looking into this. To rule out other issues I made some changes to naming of lights but the message is the same:


2023-04-15 16:52:28.659 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'entity_id' when rendering '{% set a = light_switch.entity_id %} {% set b = night_lights.entity_id %} {% if a and b %}
  {{ a | reject('in', b) | list }}
{% else %}
  []
{% endif %}'
2023-04-15 16:52:28.662 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'entity_id' when rendering '{% set a = light_switch.entity_id %} {% set b = night_lights.entity_id %} {% if a and b %}
  {{ b | reject('in', a) | list }}
{% else %}
  []
{% endif %}'
2023-04-15 16:52:29.328 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hue_play_servieskast_links, light.hue_play_servieskast_rechts, light.hue_play_tv_links, light.hue_play_tv_midden, light.hue_play_tv_rechts or it is/they are currently not available
2023-04-15 16:52:29.329 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hue_play_servieskast_links, light.hue_play_servieskast_rechts, light.hue_play_tv_links, light.hue_play_tv_midden, light.hue_play_tv_rechts or it is/they are currently not available

This is my config for this particular automation:


alias: Verlichting - Woonkamer
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    light_brightness: 95
    time_delay: 4
    motion_trigger:
      - binary_sensor.woonkamer_light_trigger
    include_ambient: ambient_enabled
    ambient_light_options: ambient_light_option_enabled
    ambient_light_value: 80
    ambient_light_sensor: sensor.hue_motion_sensor_1_illuminance_5
    include_light_control:
      - use_brightness
      - use_transition
    light_transition_on: 2
    light_transition_off: 10
    light_switch:
      entity_id:
        - light.hue_play_tv_links
        - light.hue_play_tv_midden
        - light.hue_play_tv_rechts
        - light.hue_play_servieskast_links
        - light.hue_play_servieskast_rechts

The lights are all HUE lights. The light trigger is a helper with a few motion sensors.

The automation actually works but the warning messages are filing up the log.

Blacky · April 15, 2023, 3:03pm

Could you try and put any 2 lights used in “Lights - Switches - Scenes” into “Night Lights” but you dont have to “Enable the night lights options”.

Let us know how you go.

barcomoon · April 15, 2023, 3:09pm

Ok, that got rid of the first two warnings (template variable warning). The last two still persists (unable to find referenced entities):


2023-04-15 17:07:18.566 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hue_play_servieskast_links, light.hue_play_servieskast_rechts, light.hue_play_tv_links, light.hue_play_tv_midden, light.hue_play_tv_rechts or it is/they are currently not available
2023-04-15 17:07:18.570 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hue_play_servieskast_links, light.hue_play_servieskast_rechts, light.hue_play_tv_links, light.hue_play_tv_midden, light.hue_play_tv_rechts or it is/they are currently not available

Blacky · April 15, 2023, 3:28pm

I think it may have to do with the lights.

Blacky · April 15, 2023, 3:41pm

EDIT: When did you do the update… try updating again.

geox19 · April 15, 2023, 3:43pm

I’m getting errors like this I upgraded just few days ago from 1.29 I’m going to delete all my automations and install fresh with the updated blueprint

Blacky · April 15, 2023, 4:07pm

@barcomoon @geox19

I think I have found it. I will try and fix this in the next update. I believe the logs are only stored for 10 days and then cleared so it shouldn’t just keep building up you data base.

Edit: Fixed, will be in the next release.

geox19 · April 15, 2023, 4:24pm

Thanks Blacky, No worries I just need to keep my face out of the logs anyways. The great thing is, if you start fresh it’s really easy and fast to point and click your way to success with your blueprints.

PuceZhodosha · April 17, 2023, 7:45am

HI Blacky, nice BP thanks a lot.

Is there a possibility to add more bypass switches?

    include_bypass: bypass_enabled_stop
    motion_bypass: sensor.hue_wall_switch_module_1_battery_2

I have in the one room two different HUE wall switch modules which should be used to bypass this automation…

Blacky · April 17, 2023, 9:31am

@PuceZhodosha

Hi Puce, firstly welcome to the community

Currently you can only select one by-pass but that doesn’t mean you cant have more than 1. In a new feature that is on the road map, that I am sure everyone will love, may require to have a selection to add more than 1 by-pass. But for now it is best to set up a group helper as you can have it now.

To do this it is similar to one of our FAQ but you would select “sensor” rather than “Binary sensor group” and add that to your by-pass. To see the FAQ on how to do this click here.

Hope this helps.

Blacky