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

Blacky · January 16, 2025, 10:37am

Thank you for your detailed post and thorough testing… it was incredibly helpful in identifying the issue quickly. I truly appreciate your effort!

The problem stemmed from a bug in the condition logic that caused an unintended loop.

This has now been fixed, and the updated blueprint should resolve the issue. Please update the blueprint, test it, and let us know if the problem is resolved.

Once again, thank you for reporting this bug and helping improve the blueprint!

I have also updated your YAML but I am not sure if this is what you are after as some of your setting may be from testing.

Because in dynamic lighting your brightness is from 100% to 99% and you are using option 13 I changed it to option 10 and your 100 % brightness will be handled in light control.
Removed your toggle helper as it is not needed.
In dynamic lighting changed the Dynamic Lighting - Time Evening - End Point to be 11pm so you will finally reach your Dynamic Lighting - Min Colour Temperature.
In Night Light Control I selected If lights are ON, adjust the lights when crossing over. This way they will change when the time crosses over from normal light to night lights and vice versa.

Click to expand

alias: A Sensor Light - Forum
description: ""
use_blueprint:
  path: craig/new-option-sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.flur_bewegungsmelder_bewegung
    light_switch:
      entity_id:
        - light.flur_licht_leuchte
    time_delay: 1
    include_light_control:
      - use_transition
      - use_colour_temperature
      - use_brightness
    light_transition_off: 5
    light_transition_on: 0.5
    light_colour_temperature: 3400
    include_night_lights: night_lights_enabled
    night_lights:
      entity_id:
        - light.flur_licht_leuchte
    night_time_delay: 0
    include_night_light_control:
      - use_brightness
      - use_colour_temperature
      - use_transition
      - if_lights_are_on_adjust_when_crossing_over
    night_light_colour_temperature: 1900
    night_light_brightness: 1
    night_light_transition_off: 10
    night_lights_conditions:
      - time_enabled
    night_lights_before_time: "05:30:00"
    include_light_colour_control: use_colour_temperature
    include_night_light_colour_control: use_colour_temperature
    include_dynamic_lighting: enable_time_controled_colour
    dynamic_lighting_max_colour_temp: 3400
    dynamic_lighting_min_colour_temp: 2500
    dynamic_lighting_time_start_morning: "05:30:00"
    dynamic_lighting_time_end_morning: "06:30:00"
    dynamic_lighting_time_end_evening: "23:00:00"
    dynamic_lighting_heartbeat: 5
    dynamic_lighting_time_start_evening: "19:00:00"
    night_lights_after_time: "23:00:00"
    dynamic_lighting_min_brightness: 99

Blacky

herbert1910 · January 16, 2025, 10:55am

But then the entire automation is deactivated.
I actually meant that the light should come on when the LUX value of a sensor goes below a certain value. so use the LUX sensor as a TRIGGER.

Blacky · January 16, 2025, 11:08am

@herbert1910

When you turn ON the toggle helper the automation will be active. It will then trigger on the lux sensor but it has to cross over.

If you are having problems could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.

Make sure you add your helper in so I can edit your YAML.

Blacky

Blacky · January 16, 2025, 11:16am

New update 7.7

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

Bug Fixes

Dynamic Lighting - A bug affecting dynamic lighting options 10, 11, 12, and 13 has been fixed. Previously, re-triggering the automation caused a loop that consumed excessive RAM and issued a critical log. This issue was caused by a single condition leading to an unintended loop.

The updated blueprint resolves this problem. Please update your blueprint promptly to apply the fix.

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

Enjoy

Blacky

ajd_ht · January 16, 2025, 11:42am

@Blacky : 1.000 Thanks.

Will Blueprint-Updates be automated in future?
☀️ Cover Control Automation (CCA) - a comprehensive and highly configurable roller blind blueprint offers a possibiliy for additional actions.

image1038×736 48 KB

Do you have plans to implement that in future?

Blacky · January 16, 2025, 11:56am

@ajd_ht

Point 1. This is up to HA and what they would like to do. Maybe they will allow this to happen.

Point 2. This Blueprint is very complex in the logic. You could have another automation to do something when the light turn ON or OFF. Adding it may just make it more confusing.

Your welcome

Blacky

ajd_ht · January 16, 2025, 12:10pm

Just the option to have a follow up action would be great.

Vinkoy · January 17, 2025, 12:31pm

Hi @Blacky! First and foremost, a huge thank you for all the incredible effort you’ve put into creating this amazing blueprint!

I’m trying to customize the Dynamic Lighting: Time Controlled Feature for my needs. I’m using the 11 - Time Controlled - Brightness option.

I’d like the light to gradually dim from 100% to 3% over three hours, specifically between 10:00 PM and 1:00 AM.
Additionally, I want the night_time_delay to be set to 3 minutes during the night.

Here’s my YAML configuration:

alias: light test
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.ms_room_occupancy
    light_switch:
      entity_id: light.room
    time_delay: 10
    include_dynamic_lighting: enable_time_controled_brightness
    dynamic_lighting_max_brightness: 100
    dynamic_lighting_min_brightness: 3
    dynamic_lighting_time_start_evening: "22:00:00"
    dynamic_lighting_time_end_evening: "01:00:00"
    include_night_lights: night_lights_enabled
    night_lights_conditions:
      - time_enabled
    night_lights_after_time: "23:00:00"
    night_lights_before_time: "05:00:00"
    night_lights:
      entity_id: light.room
    night_time_delay: 3

Automation Results:

9:59 PM - Brightness 100% - OK
10:00 PM - Brightness 3% (expected 100%). If I change dynamic_lighting_time_end_evening to "23:59:00", the brightness is 100%.
10:30 PM - Brightness 3% (expected 83%). If I change dynamic_lighting_time_end_evening to "23:59:00", the brightness is 83%.
11:00 PM - Brightness 100% (expected 67%). The night lights mode is enabled, and Dynamic Lighting does not seem to work.
11:30 PM - Brightness 100% (expected 50%). The night lights mode is enabled, and Dynamic Lighting does not seem to work.

Questions:

Based on items 2 and 3, it seems that I cannot achieve dynamic brightness adjustment across midnight (10:00 PM to 1:00 AM). Is this by design?
From points 4 and 5, should Dynamic Lighting work when the night_lights mode is active?

Blacky · January 17, 2025, 2:39pm

@Vinkoy

Thank you, and your welcome.

Answers:

Currently NO. I developed it to mimic the sun not to do it over a day. That said I should be able to achieve this easily but I will need time to test it live through a whole day. Keep an eye out for a new release.
Dynamic lighting only works for normal lights not night lights.

Blacky

Rhidus · January 17, 2025, 11:13pm

@Blacky , thanks so much for your quick reply and fix! I will try it once I have a bit of time and respond whether the issue was fixed for me.

Also thanks for the suggestions on the automation settings!

Blacky · January 18, 2025, 6:29am

@Rhidus

No problem, there is another update coming with a fix if you using it over a day and a new feature so keep an eye out for it.

Blacky

Rhidus · January 18, 2025, 9:47am

@Blacky And here comes the update: After updating the blueprint and enabling the automation, RAM usage is stable now when motion senosr is triggered (even without the toggle helper)! Thanks for your support

Vinkoy · January 18, 2025, 5:05pm

Thank you for your response!

Great news! I’ll keep an eye out for updates.
Got it, that’s not an issue at all. I’ve solved this on my end by creating an additional automation based on your blueprint and using mutually exclusive bypasses. This way, one automation runs until 10:00 PM, and another takes over after 10:00 PM. In the second automation, I set the time delay to 3 minutes (as I wanted during the late evening hours), ensuring Dynamic Lighting works properly during the late evening and night hours.

KeKeSeB · January 18, 2025, 9:25pm

Thanks for this fantastic blueprint.
I’ve been playing with it and if my lights are already on, they are not triggered/adjusted to the values configured on trigger, but they are turned off at the end of the “Time Delay”. Is there a way to prevent that?

Blacky · January 19, 2025, 7:06am

@KeKeSeB

Welcome to the community.

This is how the blueprint is designed. This allows you to make changes to your light when they are turned ON by the automation. It also helps to reduce network traffic.

If you would like it to change then you will need to create a scene or a script and input it into Lights - Switches - Scenes - Scripts and don’t use the Scenes & Scripts - Toggle Helper, leave this input empty.

Blacky

Blacky · January 19, 2025, 1:48pm

New update 7.8

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

New Feature

Dynamic Lighting - State Control Option
You now have an option to enable or disable dynamic lighting based on the state of a specified entity. When the entity is in the selected activation state, dynamic lighting will function as configured. When the entity is not in the activation state, dynamic lighting will be disabled. This allows you to toggle between normal lighting and dynamic lighting based on the entity’s state.
Dynamic Lighting - Next Day
With options 10, 11, 12, and 13, you can now set the time for transitioning to a new day.

Bug Fixes

Dynamic Lighting
- Resolved an issue with options 10, 11, 12, and 13 that could cause excessive RAM usage and generate a critical log, depending on your settings.
- Fixed a bug where turning OFF the bypass might not reset your lights correctly.

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

Enjoy

Blacky

jrullo8 · January 20, 2025, 3:19am

Cannot save any automation. I have HA detecting presence of Aqara FP2. HA does detect presence for binary sensor binary_sensor.kitchen_occupied on the dashboards.

When I select that sensor as a trigger for this blueprint, the automation cannot be saved.
Get error: Message malformed: extra keys not allowed @ data[‘triggers’]

I chose just one entity in the subsequent dropdown. Not an area, not a device, just one light entity: light.big_kitchen_light.

kitchen_occupied is a type group in helpers with 2 entities in the group. One entity is the In Kitchen and the other is Any Area Detect. These entities show just fine on a dashboard and are working.

I do not understand why this cannot be used as a trigger.

Blacky · January 20, 2025, 9:15am

@jrullo8

Welcome to the community.

Sorry your having troubles… You will need to update your HA if you can as I have updated the code to follow HA road map. This way you will be able to use the blueprint how HA would like it to be. Once you done that everything will work perfectly.

Blacky

Herr.Vorragend · January 20, 2025, 6:04pm

For some time now my Sensor-Light Automation has been behaving strangely.

I use the bypass function and activate the following boolean helpers via a wall switch:

Bypass Switch - Turn lights ON (here: bypass_bwm_diele_on)

Bypass Switch - Keep The Lights Current State (here: bypass_bwm_diele_keep)

action_left_bottom_short:
  - action: light.turn_on
    target:
      entity_id:
        - light.dekoleuchten_haustuer
    data: {}
  - action: input_boolean.turn_on
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_on
        - input_boolean.bypass_bwm_diele_keep
    data: {}

At night, I switch the light off again using another wall switch and also deactivate the two booleans.

action_top_short:
  - action: light.turn_off
    target:
      entity_id:
        - light.dekoleuchten_haustuer
    data: {}
  - action: input_boolean.turn_off
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_on
        - input_boolean.bypass_bwm_diele_keep
    data: {}

For a few weeks now, the light has been switched off, but a motion sensor that is still active switches the light back on again immediately. I just walk through the motion sensor when I have to go to the switch.

If I then don’t switch the light off again, the light stays on for as long as configured in ‘Time Delay’.

My configuration:

alias: Bewegungsmelder Diele / Dekoleuchten
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.bwm_diele_motion
      - binary_sensor.tuerkontakt_haustuer_opening
    light_switch:
      entity_id: light.dekoleuchten_haustuer
    time_delay: 3
    motion_bypass_lights_on:
      - input_boolean.bypass_bwm_diele_on
    motion_bypass_lights_off:
      - input_boolean.bypass_bwm_diele_off
    motion_bypass_lights_stop:
      - input_boolean.bypass_bwm_diele_keep
    include_sun: sun_disabled
    sun_elevation: 0
    ambient_light_sensor: sensor.lichtsensoren
    ambient_light_value: 1300
    include_bypass:
      - bypass_enabled_turn_on
      - bypass_enabled_stop
      - bypass_enabled_turn_off
    ambient_light_options: ambient_light_option_disabled
    ambient_light_high_value: 1400
    include_ambient: ambient_enabled

Can you help me find out what I’ve done wrong here? Or has something been changed here? Thank you.

Or to put it another way: automation is somehow re-triggered.

Do you need a trace?

Blacky · January 21, 2025, 9:43am

@Herr.Vorragend

Thanks for all the information… it makes it easy to understand.

When the bypass is turned OFF (any bypass, as long as all are OFF), the automation enters auto mode. If the motion sensor (any trigger) is ON, the automation will keep the lights ON as expected. In auto mode, the lights should remain ON if a trigger is active.

If the lights turn OFF and then back ON instantly, this is likely caused by your switch action turning the light OFF, followed by this automation turning it back ON. You can allow the automation to manage this seamlessly. Refer to the YAML adjustment example below.

Your YAML click here

action_top_short:
  - action: input_boolean.turn_off
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_on
        - input_boolean.bypass_bwm_diele_keep
    data: {}

If you want the light to turn OFF and remain OFF, even if the motion sensor is active, you can use Bypass Option 2 with the Bypass Auto OFF Option. This setup ensures the motion sensor has time to clear before the bypass turns OFF automatically. If the motion sensor is clear when the bypass turns OFF, the lights will remain OFF. Below is the YAML configuration for this setup.

Your YAML click here

alias: Bewegungsmelder Diele / Dekoleuchten
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.bwm_diele_motion
      - binary_sensor.tuerkontakt_haustuer_opening
    light_switch:
      entity_id: light.dekoleuchten_haustuer
    time_delay: 3
    motion_bypass_lights_on:
      - input_boolean.bypass_bwm_diele_on
    motion_bypass_lights_off:
      - input_boolean.bypass_bwm_diele_off
    motion_bypass_lights_stop:
      - input_boolean.bypass_bwm_diele_keep
    include_sun: sun_disabled
    sun_elevation: 0
    ambient_light_sensor: sensor.lichtsensoren
    ambient_light_value: 1300
    include_bypass:
      - bypass_enabled_turn_on
      - bypass_enabled_stop
      - bypass_enabled_turn_off
    ambient_light_options: ambient_light_option_disabled
    ambient_light_high_value: 1400
    include_ambient: ambient_enabled
    bypass_time_delay: 0.25
    include_bypass_auto_off:
      - bypass_auto_off_enabled_off
    bypass_auto_off_delay: 1

And your OFF switch would look like this

Your YAML click here

action_top_short:
  - action: input_boolean.turn_on
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_off
  - action: input_boolean.turn_off
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_on
        - input_boolean.bypass_bwm_diele_keep
    data: {}

So this is how I would do the whole setup but I am not sure why your turning 2 bypasses ON and then turning 2 OFF at the same time.

First I would group the 2 triggers, then;

action_left_bottom_short:
  - action: input_boolean.turn_on
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_on
    data: {}

action_top_short:
  - action: input_boolean.turn_on
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_off
  - action: input_boolean.turn_off
    target:
      entity_id:
        - input_boolean.bypass_bwm_diele_on
    data: {}

I have set the Bypass Auto OFF Option to 1 minute, but you may need to adjust this duration to match the time it takes for your motion sensor to clear. If the timing is too short, the bypass may turn OFF before the motion sensor clears, causing the light to turn back ON.

alias: Bewegungsmelder Diele / Dekoleuchten
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.bwm_diele_motion
      - binary_sensor.tuerkontakt_haustuer_opening
    light_switch:
      entity_id: light.dekoleuchten_haustuer
    time_delay: 3
    motion_bypass_lights_on:
      - input_boolean.bypass_bwm_diele_on
    motion_bypass_lights_off:
      - input_boolean.bypass_bwm_diele_off
    motion_bypass_lights_stop:
      - input_boolean.bypass_bwm_diele_keep
    include_sun: sun_disabled
    sun_elevation: 0
    ambient_light_sensor: sensor.lichtsensoren
    ambient_light_value: 1300
    include_bypass:
      - bypass_enabled_turn_on
      - bypass_enabled_stop
      - bypass_enabled_turn_off
    ambient_light_options: ambient_light_option_disabled
    ambient_light_high_value: 1400
    include_ambient: ambient_enabled
    include_bypass_auto_off:
      - bypass_auto_off_enabled_off
    bypass_auto_off_delay: 1

Hope this helps you.

Blacky