Did you make sure you only have Entities listed in the ‘Lights - Switches - Scenes - Scripts *’ section? If you have Areas or Devices listed there, you need to expand them out to the actual Entities.
1 Like
Yes. I even tried one at a time. It only turns them off.
A lot of work has gone into the next release. Final testing is being done. I hope you like it.
Blacky 
2 Likes
Hi Dennis,
If it is not turning them ON it will not turn them OFF trough the normal trigger. Check your logbook to see what is turning them OFF as something could be going on here.
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.
Blacky
Will do when I make it home. Two things to mention though. The bulb and the helper group I’m trying to use are Hues connected via the hue integration. I tried with a Zigbee plug connected via ZHA and it works. 
Thanks!
This blueprint seems to offer everything what I am looking for but haven’t found a solution for one of the cases.
I have:
- Hue fixture with ability to dim / change color
- Zigbee doorswitch
I would like:
- Light goes full on when door is opened during the day
- Light goes on in a dimmed state when door is opened after sunset/night
- Light goes off after x minutes
- Light goes off immediately when door is closed
All cases work flawless except the last one. If the timeout is set at 0; the light switches ON and OFF when the door is opened/closed. I would like to use the timeout only when opening the door and ignoring it when closing the door.
Is this scenario possible with this blueprint?
alias: TEST Sensor Light Blue Print
description: Living Room Lights and Presence Sensor
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.living_room_occupancy_presence
light_switch:
entity_id: light.living_room_lights_group
time_delay: 3
include_dynamic_lighting: enable_sun_elevation_colour_brightness
dynamic_lighting_min_colour_temp: 2000
include_time: time_enabled
after_time: "15:00:00"
before_time: "07:00:00"
dynamic_lighting_max_colour_temp: 6500
include_night_lights: night_lights_enabled
night_lights:
entity_id: light.living_room_lights_group
night_lights_conditions:
- time_enabled
night_lights_after_time: "22:00:00"
night_lights_before_time: "06:00:00"
light_transition_on: 1.5
light_transition_off: 2
include_light_control: []
Yes put you will have to do a script. New update is coming out soon as well.
Blacky
Hi Dennis, please adjust your min brightness as it is set to 0 = light OFF. So if you set it on say 10% the light will come ON.
Blacky
1 Like
IT IS A BIG ONE
Embarking on this journey, countless hours of dedication have been poured into our latest release, and I am thrilled to share it with you all. 
The top post has already garnered an incredible 201 likes – thank you for your overwhelming support! If you haven’t already, please take a moment to hit the like button and show some love to the blueprint. 
For those who resonate with my work and want to contribute further, there’s an opportunity to make a positive impact. A donation link is available to support ongoing projects. A heartfelt THANK YOU to those who have already generously contributed! 
If you’re yet to make a donation and would like to be a part of this journey, consider clicking the Donation Link. Your small contribution goes a long way, and I genuinely appreciate your support! 
Attention: Dynamic Lighting Enthusiasts!
Exciting news for users of dynamic lighting options 1 or 2! We’ve introduced some game-changing inputs that will enhance the functionality and take your experience to the next level.
If you’re keen on maintaining your current setup, it’s a breeze! Simply follow these steps: Set the “Step Value” to 100 and adjust the “Dead Zone” to 0. This guarantees that your original preferences will stay intact, ensuring a seamless continuation of your preferred settings. 
Your lighting experience, your way – take control and customize it to perfection! 
New Feature 
Dynamic lighting
I have updated LUX brightness from all your feedback and my own experiences. No longer will the brightness jump up and down to then when it gets close just change ever so slightly… that can be annoying. You now can take back control of your lighting transition to a more suitable setting and let dynamic lighting do the rest. If your lights only support brightness then that is no longer a problem, you can now slow it down using the step value. The “Dead Zone” is a ± value that realy helps. Think of it like this; Say the dynamic lighting would like to set your lights at 88%, if your dead zone is 7% then if your actual light brightness is in the range (“Dead Zone”) of 81% to 95% then your lights will not change the brightness value. 7% seams high but I have found when testing it is only realy less than 7% of what it should be and is not noticeable. The defaults have been set but you will need to adjust them to your liking.
Below is what been added to dynamic lighting.
- Step Value - With every heartbeat, the system evaluates the lux value, light brightness, and the targeted brightness. If the targeted brightness surpasses the predefined step value, the system applies the set step value to gracefully moderate the rate of changes, facilitating a smoother transition in light brightness.
- Dead Zone - With every heartbeat, the system evaluates the current light brightness and the targeted brightness. If the targeted brightness falls within the defined dead zone, the system maintains the current light brightness. This prevents minor fluctuations in light intensity that could be bothersome to the eye.
- Option 6 - Sun Elevation Lighting - Colour Temp + Lux Controlled Brightness. New option added for you light control.
Scripts
- You are able to run a script at the end like we already do with scenes. All you have to do is put your script in “Scenes - Scripts To Turn OFF” and when the automation turns OFF it will run the end script.
Maintenance 
- General code clean up - Just doing some housekeeping.
Bugs Fixed 
- By-pass auto OFF – When all three by-passes were ON, option 3 would not turn OFF due to an automation timing issue.
- Auto OFF Enabled – When two or three were ON and one was turned OFF manually the by-pass auto off would not work.
- HA Restart - By-pass options.
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 
4 Likes
Great; I have updated immediately !
I assume I still would need to make a script to switch off the lights when using a doorswitch?
Awesome, really happy with the bypass fixes. Now I can restart my HA again without my spouse getting annoyed!
Hm, too soon. I am using a template (occupancy) sensor helper that detects if my TV is on and configured this as a bypass in “By-pass Switch - Turn lights ON”. But after a restart it takes a little while before the helper becomes available and “occupied” again. The automation doesn’t handle this so the lights will turn off after the timeout (and won’t turn on again on motion because of the bypass).
Okay, thanks for the feedback. We will fix it in the next release. How long does it take for it to become available?
Blacky
1 Like
Thanks. I’m not sure how long it takes, I think a couple of seconds. Not sure how I can specify this, the unavailable state is not logged.
No problem, I will look at my system, the only thing is my system is realy fast so maybe on a RPi it could be slower. I will work it out.
Blacky
1 Like
Hi Blacky,
First of all, thanks for the update and great support for this blueprint.
As the functionality is increasing with each update, also the complexity increases and more and more questions will be raised. You have created many FAQ’s and tips&tricks in this thread, but these are spread over multiple posts.
Is it possible to have alle the FAQ’s etc centralized on the GitHub so it will be easier to find the answers to all our questions.
1 Like
+100. I LOVE Blacky’s Blueprints, and his devotion to answering every question. But I think he’d be doing himself (and us) a huge favor with a centralized FAQ/how-to instructions on Github. The Blueprints are very complex and having detailed help/FAQ/upgrade instructions in one spot would be a god send.
2 Likes
Thank you for the reply. I’ve set it for option 2-turn lights off and put the auto-off to 0. When I press the switch, the lights turn off and then immediately turn back on. Here’s my code. Maybe that will help someone spot my problem.
alias: Family Room Table Lights Toggle and Nightlight
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.presence_fp2_family_room
light_switch:
entity_id:
- light.family_room_left_table_bulb
- light.family_room_right_table_bulb
time_delay: 8
include_light_control:
- use_colour_temperature
include_night_lights: night_lights_enabled
night_lights:
entity_id:
- light.family_room_left_table_bulb
- light.family_room_right_table_bulb
night_time_delay: 1.5
include_night_light_control:
- use_brightness
- use_colour_temperature
night_light_brightness: 10
night_lights_conditions:
- time_enabled
night_lights_after_time: "21:00:00"
night_lights_before_time: "04:00:00"
light_brightness: 50
include_dynamic_lighting: enable_lux_controled_brightness
dynamic_lighting_lux_sensor: sensor.family_room_light_sensor
light_colour_temperature: 3000
dynamic_lighting_max_colour_temp: 3000
night_light_colour_temperature: 3000
include_bypass:
- bypass_enabled_turn_off
include_bypass_auto_off:
- bypass_auto_off_enabled_off
motion_bypass_lights_on: []
motion_bypass_lights_off:
- light.family_room_lamp_switch
motion_bypass_lights_stop: []
bypass_auto_off_delay: 60
bypass_time_delay: 0
Thanks, Blacky!