Awsome thank you, itâs reassuring to know that itâs not me being stupid.
I will try your suggestions, but I have ordered the new Everything Presence Lite sensors and so will be using these instead with the blueprint. Thanks again 
1 Like
I want the garage lights to come on when 1) garage bay door open or 2) garage door into the house opens. This works fine (Iâve grouped them). However, how can I turn the light off (it was on) when a different door (letâs say âside doorâ) is opened? Is this a âbypassâ logic? I donât want bugs to be attracted to the lights so I want them to go off should that side door be opened.
Your lighting experience, your way â take control and customize it to perfection! 
New Feature 
-
Collapsible Sections - Added collapsible sections to the blueprint. This enhancement improves the blueprint user interface by making it cleaner and more organized, allowing sections to be collapsed.
This feature was introduced in Home Assistant 2024.6, so you must have this version or later for the blueprint to work.
Maintenance 
- Update deprecated code for light control in kelvin.
Code Clean Up 
- Cleaned up code for reliability that could cause a bug.
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 
5 Likes
Hello
The blueprint looks nice but it wil not trigger,
I have a aquara motion sensor as trigger and it wont start. when motion is detected.
alias: Vorraum 2 Licht
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.bs_vorraum_2_occupancy
light_switch:
entity_id:
- light.sl_vorraum_2_a
- switch.p_vorraum
- light.sl_vorraum_2_b
boolean_scenes_scripts: Vorraum 2 Licht
time_delay: 2
Looks like you edited your YAML manually as your âScenes & Scripts - Toggle Helperâ is wrong. This is not an input_boolean entity ID. You are only using lights and a switch so you donât need this input boolean. Please remove the bottom line and test it again.
boolean_scenes_scripts: Vorraum 2 Licht
Blacky 
Thank you for the tip. Now its working.
Amazing job 
Is it possible to configure the color of a RGB light with differents colors for differents range of time ?
Example red after the sunset (Night) and white after a certain time.
Hey, thank you for the great blueprint. I have a question.
I have a stair with 2 doors at the bottom and the top of the stair. Both doors have sensors and my goal is to turn on lights on the staircase the moment any of the doors open. Also my goal is to extend the time lights are on, each time any of the doors close and then open again.
You recommend to group multiple trigger sensors into a group sensor. But in this case as long as one of the doors is open, no matter how many times I open/close the 2nd door, binary group sensor says door is open once and then doesnât register future door opening/closing. Hence duration that light is on doesnât get extended with each opening and closeing of the 2nd door as long as 1st remains open.
Do I understan correctly that in this case I should not follow your advice and create a group binary sensor, but instead use each of the door sensors separately inside the blueprint settings? Would appreciate your advice here.
And if my assumption is correct and scenario legitimate perhaps its worth updating the documentation to differentiate your advice depending on the scenario?
@Blacky would you be so kind as to check here to see if it really is a bug? By way of background, I have updated to the latest version and also created the new helper for dynamic lighting. In my opinion, the automation is also running properly, but after I completely restarted the entire system, I discovered the following error message in the logs. It only affects one automation in the living room. When I restarted, I was also in the living room, the light stayed on and was also on after the restart, the helper was also on. Am I missing something or is it information I donât understand?
Thank you
Logger: homeassistant.components.automation.licht_wohnzimmer_automation
Quelle: helpers/script.py:2001
Integration: Automatisierung (Dokumentation, Probleme)
Erstmals aufgetreten: 18:46:13 (3 Vorkommnisse)
Zuletzt protokolliert: 18:46:13
licht_wohnzimmer_automation: Choose at step 1: default: Parallel actions for dynamic lighting and normal lights: parallel 1: Choose at step 3: 1 - Dynamic Lighting - Lux Controlled Brightness: Dynamic Lighting Control: Error executing script. Error rendering template for variables at pos 1: ZeroDivisionError: float division by zero
licht_wohnzimmer_automation: Choose at step 1: default: Parallel actions for dynamic lighting and normal lights: parallel 1: Choose at step 3: 1 - Dynamic Lighting - Lux Controlled Brightness: Error executing script. Error rendering template for repeat at pos 1: ZeroDivisionError: float division by zero
licht_wohnzimmer_automation: Choose at step 1: default: Parallel actions for dynamic lighting and normal lights: parallel 1: Error executing script. Error rendering template for choose at pos 3: ZeroDivisionError: float division by zero
alias: licht_wohnzimmer_automation
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.bewegungsmelder_wohnzimmer
light_switch:
entity_id: light.licht_gruppe_wz
end_scenes: []
time_delay: 2.5
include_light_control:
- use_colour_temperature
light_brightness: 50
light_colour_temperature: 2700
include_ambient: ambient_enabled
ambient_light_sensor: sensor.sensor_wohnzimmer_light_sensor_light_level
include_night_lights: night_lights_enabled
night_lights:
entity_id: light.licht_gruppe_wz
include_night_light_control:
- use_brightness
- use_colour_temperature
- if_lights_are_on_adjust_when_crossing_over
night_light_colour_temperature: 2750
night_lights_before_time: "06:00:00"
ambient_light_value: 80
night_time_delay: 2.5
night_lights_conditions:
- time_enabled
night_light_brightness: 1
night_light_transition_on: 1
night_light_transition_off: 1
include_sun: sun_disabled
ambient_light_options: ambient_light_option_enabled
include_bypass:
- bypass_enabled_stop
motion_bypass_lights_off:
- input_boolean.by_pass_kino
motion_bypass_lights_on:
- input_boolean.by_pass_kino
motion_bypass_lights_stop:
- input_boolean.by_pass_kino
night_lights_after_time: "23:30:00"
bypass_time_delay: 0
include_bypass_auto_off: []
dynamic_lighting_max_brightness: 45
dynamic_lighting_min_brightness: 0
dynamic_lighting_max_lux: 80
include_dynamic_lighting: enable_lux_controled_brightness
dynamic_lighting_lux_sensor: sensor.sensor_wohnzimmer_light_sensor_light_level
dynamic_lighting_min_lux: 0
dynamic_lighting_heartbeat: 0.25
dynamic_lighting_step_value: 3
dynamic_lighting_dead_zone: 5
ambient_light_high_value: 96
dynamic_lighting_boolean: input_boolean.helfer_dynamic_light_wohnzimmer
Hi Blacky,
What a super Bleuprint!
Is there a possibility to return to the previous state instead of just turning off?
For example; I have a light, it is manually turned on and dimmed to 25%. When the motion sensor triggers I want the brightness to 100% for a given amount of time and then return to 25% (the previous state). Is this possible?
Best regards, Bas.
I might be retarded but i cant find how to do the following.
I have some hue lights(always powered) in a room, motion sensor, door sensor, and a wireless button in the place of a traditional light switch.
all works good for turning the lights on and off by the timer. But when the light is on and i press the button the lights stay on.
How would i configure this so that the button is just a normal toggle
Your welcome.
Blacky
Thanks for your kind words.
Yes, you would need to use night lights. To get RGB you will need to create a scene and use the scene in night lights. Then when night light are active you will have red and when normal lights are active you will have white.
If you need more than 2 time frames then you would need to create a script that will set the RGB depending on the time of day. Example when motion is triggered it will run the script and then the script will set the lights to your liking depending on the time of day.
Blacky
Are you still getting this error? I ask because you say âIt only affects one automation in the living room.â and you may of resolved it before I dig into it.
Blacky
Welcome to the community.
Yes, you will need to use a script or a scene.
Example if you have a scene to set the light to 100% then add that into 'Lights - Switches - Scenes - Scripts '. Then you could have a scene to set the lights at 25% and then add that to âScenes - Scripts To Turn OFFâ. This will always have your lights at 25%.
Maybe if I had your use case I could better help you but take a look at this link click here and look under the heading Automation Example. It guides you how to set your lights to low brightness and then 100% and it just may be suited to your use case.
Blacky
Thanks for the info. Even you 1st edit⌠all good.
Because you have a wireless button we donât want that to turn the light ON / OFF. You probably have that set up. Push the button light turn ON / OFF before you used the BP. Now if you are using the BP you have to detach it from the light. The button must have an ON / OFF state.
There are a few ways to do this depending on what you are after. If you use it in the trigger when the button is ON the light will come ON. When it is pushed OFF the time delay starts and then turns the light OFF. You may have this setup already. When you turn it OFF you donât get that instant OFF because of the time delay.
so we can use the bypass option 1.
If you put your wireless button (must have an ON / OFF state) into bypass option 1 then when you turn it ON the light will come ON and stay ON and when your turn it OFF you have a separate time delay in the bypass. If you set it to 0 then it will go OFF instantly IF! all your triggers are OFF. If not then it will wait for your triggers to go OFF and then turn the light OFF. Good thing about the bypass you can also set an auto OFF time delay that will turn your button OFF if you forget to turn it OFF.
Hope this helps
Blacky
Iâm not sure if itâs possible, but is there a way to detect the entity supported attributes? Say for example, you have non-dimmable bulb, but you configure the brightness to adjust with the blueprint accidentally, which results in the automation to stop working all together.
If the blueprint is somehow was able to detect that this feature isnât support by said device, then it will notify the user or disable to option entirely. Think this will help with a lot of misconfiguration by users here (myself included).
Might be looking in to deep here. 
If you add a light that doesnât support the light control option you selected it just doesnât apply the data to that light because it canât. In light control you can also can decide what data you would like to provide to a light entity.
Are you having problems?
Blacky
There was an issue in the past where something like this happened, which resulted in the automation to break. It may have been the âcolour temperatureâ or dynamic lighting that broke it, rather than brightness control.
Issue couldâve been fix since then, as I hadnât tested it since then, but I did come across this.
1 Like