Hey Blacky,
thanks for all your help, I really appreciate it!
I thought thereâs no way around scenes if I donât want to turn the lights off when the trigger is off. But using the night light option instead is an awesome idea. Iâll give it a try the next weeks. Thanks!
Have a great day.
Lukas
why does it turn on the scene ?. what I expect the bypass to do is NOT to activate the automation IF the lights are ON.
the scene is the for motion sensor to turn on cabinets and floor lights IF the main light are NOT on. and IF I turn on the main lights DO NOT activate the motion automation.
Hope that makes sense, I have 2nd automation to turn on the cabinet and floor lights, once sun set has arrived WHEN the main lights turn ON.
What you have is your light.kitchen_lights in bypass 1 - Enable the Bypass - Turn lights ON. When you turn your light ON it will trigger your scene scene.kitchen_motion_light_on. The name of that scene indicates to me that it will turn ON. This is what you are asking of the automation.
If you would like it to turn OFF your scene then try and put your light.kitchen_lights in bypass 2 - Enable the Bypass - Turn lights OFF.
Check this as it looks like you may have conflicts.
Blacky 
Apologies if this has been answered before. I have tried to search and read the docs, but I cannot find an answer to my question. I have scene operated livingroom lights, and that works well, with a physical bypass switch. But is a user clicks the scene in the HA dashboard, I also want the bypass to activate. If we enable âmovie-nightâ scene, it is very irritating to get ânormalâ activated mid-movie.
How do I orchestrate this? Any suggestions (other than physically using the light-switch!)?
let me clarify what I am after. Iâll start with just motion light what Iâm after.
when I walk into the Kitchen (when the main kitchen lights are OFF). after sunset I want the scene scene.kitchen_motion_light_on to turn on, and continue to stay on if there is motion.
Now IF I turn ON the main Kitchen Light.
If I walk into the Kitchen, and turn on the Main Kitchen Lights, I want a bypass to disable the scene to turn ON scene.kitchen_motion_light_off, as If I am cooking at the hob, as there is limited movement the 1.5 timeout is not enough and can turn off the Cabinet and floor LEDâs.
so what I was doing is to have a separate automation the turn ON scene.kitchen_motion_light_on when the main lights tured turned ON (ONLY after sunset), and turn on scene scene.kitchen_motion_light_off when the main lights are turned OFF.
EDIT:
after testing I have the folllwing,
include_bypass:
- bypass_enabled_turn_on
turns on the scene scene.kitchen_motion_light_on when main lights turn on (removes the need for 2nd automation, which is good)
and
include_bypass:
- bypass_enabled_stop
stops the scene scene.kitchen_motion_light_off from being tuned on, if NO motion. this is what I want it to do.
What I am after is to allow BOTH options to be allowed. ATM IF I enable BOTH options, it only recognises the last option bypass_enabled_stop
ie.
include_bypass:
- bypass_enabled_turn_on
- bypass_enabled_stop
Hope this makes more sense.
Have you looked at this blueprint? 
Sensor Light Add On - Media & Movie Lights - House Alarm Lights - Smoke Alarm Lights & Exhaust Fans + More
Blacky
Regards to the bypass. If you turn one on and it is turn ON then the light turn ON. If you then turn the bypass for turn OFF then the lights turn OFF, if you then turn the bypass for turn ON then the light turn back ON etc, it reacts to the last one you did. If you have 2 ON then all af them have to be OFF for the automation to run again.
Can you explain in a easy step guide on what you are trying to achieve. Then provide your yaml with all the entites in there so I can edit it. Also make 2 helpers for your scenes, put one in Scenes & Scripts - Toggle Helper and one in Night Lights - Scenes & Scripts - Toggle Helper
Blacky
ok, Iâll try to explain.
light.kitchen_lightsscene.kitchen_motion_light_on which includes light.kitchen_cabinets, light.kitchen_floor_led this TURNS ON the lightsscene.kitchen_motion_light_off which includes light.kitchen_cabinets, light.kitchen_floor_led this TURNS OFF the lightsbinary_sensor.kitchen_motion_sensor_occupancythere are 2 scenarios Before Sun Set and After Sun Set
1: Before Sun Set
light.kitchen_lights nothing else happens.light.kitchen_lights nothing else happens.In this Scenario the motion sensor has NO effect at all.
2A After Sun Set
NO LIGHTS ON, NO MOTION IN ROOM
TURN ON light.kitchen_lights and I want the scene scene.kitchen_motion_light_on to ACTIVATE (so it TURNS ON light.kitchen_cabinets, light.kitchen_floor_led). and have the motion sensor IGNORED while light.kitchen_lights are ON, so ALL lights stay ON.
TURN OFF light.kitchen_lights and I want the scene scene.kitchen_motion_light_off to ACTIVATE (so it TURNS OFF light.kitchen_cabinets, light.kitchen_floor_led).
2B After Sun Set
NO LIGHTS ON, NEW MOTION DETECTED IN ROOM
scene.kitchen_motion_light_on to activate (so it TURNS ON light.kitchen_cabinets, light.kitchen_floor_led). and have a 1.5 minute timeout, so if after 1.5 mins of NO MOTION I want the scene scene.kitchen_motion_light_off to ACTIVATE, so it TURNS OFF light.kitchen_cabinets, light.kitchen_floor_led2C After Sun Set
MOTION ALREADY DETECTED IN ROOM (scene.kitchen_motion_light_on ALREADY ACTIVATED)
TURN ON light.kitchen_lights, I want the motion timeout IGNORED, so ALL lights stay ON.
TURN OFF light.kitchen_lights I want the scene scene.kitchen_motion_light_off to ACTIVATE, so it TURNS OFF light.kitchen_cabinets, light.kitchen_floor_led
alias: Kitchen Motion Light
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.kitchen_motion_sensor_occupancy
include_sun: sun_enabled
time_delay: 1.5
end_scenes:
- scene.kitchen_motion_light_off
include_night_lights: night_lights_disabled
light_switch:
entity_id: scene.kitchen_motion_light_on
sun_elevation: 0
light_transition_on: 0.5
motion_bypass_lights_off: []
motion_bypass_lights_on:
- light.kitchen_lights
include_bypass:
- bypass_enabled_stop
motion_bypass_lights_stop:
- light.kitchen_lights
this allows 1: Before Sun Set, 2B After Sun Set and 2C After Sun Set seem to be working fine, it is just 2A After Sun Set that does not work.
IF I use:
include_bypass:
- bypass_enabled_turn_on
then 2A After Sun Set, 2B After Sun Set and 2C After Sun Set works, but 1 Before Sun Set does not work correctly as it ACTIVATES scene.kitchen_motion_light_on BEFORE SUN SET. and it does not allow you to use
include_bypass:
- bypass_enabled_turn_on
- bypass_enabled_stop
as only the first option is activated upon
Hi guys, I have a door and a motion sensor on my kitchen. The door is usually open, so the off trigger will count at the moment the sensor is closed?
Hello Community. And big thanks for this amazing BluePrint!
I have already dived into this project a little and implemented basic light control in one room. It is a pity that I had to redefine the standard behavior to make it match my color_temp with âmiredâ units. Because current slider support only kelvin. Anyway is okay.
I have two scenarios that cannot be implemented using this project:
The only thing that comes to mind without major changes to the project is implementation via a bypass. But with the addition of a separate timer only for turning on:
Any other ideas or suggestion?
I have a similar scenario to you, where some lights are ordinarily controlled via a motion sensor however on occasion there is a manual switch that can be used to turn on the lights. The way I did it was to use blackys Manual Off blueprint along with this one.
Please understand this is hard to do and get my head around it⌠but I think this is what you are after.
Setup:
Scenarios:
2A: No Lights On, No Motion Detected:
2B: No Lights On, Motion Detected: (This is normal Lights)
2C: Motion Already Detected (scene.kitchen_motion_light_on already active):
Option 1:
This is your YAML but NOTE you donât have a toggle helper enter it into Scenes & Scripts - Toggle Helper
alias: Kitchen Motion Light
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.kitchen_motion_sensor_occupancy
include_sun: sun_enabled
time_delay: 1.5
end_scenes:
- scene.kitchen_motion_light_off
light_switch:
entity_id: scene.kitchen_motion_light_on
sun_elevation: 0
light_transition_on: 0.5
motion_bypass_lights_on:
- light.kitchen_lights
include_bypass:
- bypass_enabled_turn_on
Option 2:
Or try it using just the entities only, no senes (see YAML code below). You will have to set up light control for your light.kitchen_cabinets and light.kitchen_floor_led lights. If this works and you still would like to use the scenes then in the autoamtion YAML above you will need to create a toggle helper and enter it into Scenes & Scripts - Toggle Helper
alias: Kitchen Motion Light
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.kitchen_motion_sensor_occupancy
include_sun: sun_enabled
time_delay: 1.5
light_switch:
entity_id:
- light.kitchen_cabinets
- light.kitchen_floor_led
sun_elevation: 0
light_transition_on: 0.5
motion_bypass_lights_on:
- light.kitchen_lights
include_bypass:
- bypass_enabled_turn_on
The problem I see if you turn ON light.kitchen_lights before sunset. You may have to do a script for this automation.
One More Option - Option 3
The other thing that I can also think of is I have another blueprint in beta that will turn your light.kitchen_lights into a toggle helper and you can enter it into Night Lights - Entity State then enter in your light.kitchen_lights, light.kitchen_cabinets and light.kitchen_floor_led lights into Night Lights. If the above not working I can set you up to try the beta blueprint. This may work a lot better I think but I have not tested this theory as it is just in my head so I could be wrong.
Hope this works for you 
Blacky
thanks for taking the time to look at this, Iâll just stick with using
include_bypass:
- bypass_enabled_stop
and use a secondary automation to sync cabinet / floor ledâs with main kitchen lights, it just a shame that
include_bypass:
- bypass_enabled_turn_on
can not be set too adhere to sun settings swell, that way the motion scene could be only be controlled after sunset for both motion and bypass on, which I thought would be what it should be doing if sunset option is used. I do not understand why you would want bypass controlled when the motion trigger is not being used at that time.
ie you say this:
- By-pass Switch - Turn lights ON.
Select the switches that will turn your lights ON, bypass the trigger sensor, and allow your lights to function as normal. Please note that the entity cannot be included in the âLights - Switches - Scenes - Scriptsâ or âNight Lightsâ selections.
and my trigger is
motion_trigger:
- binary_sensor.kitchen_motion_sensor_occupancy
include_sun: sun_enabled
time_delay: 1.5
so why do you not let the bypass on trigger
include_bypass:
- bypass_enabled_turn_on
motion_bypass_lights_on:
- light.kitchen_lights
adhere to sun aswell, as the motion trigger is NOT active until AFTER sunset.
A bypass will bypass all the settings and do what is asked to do.
Blacky
I had been having trouble with my automation after upgrading from V2 top V7. I do not use bypass, but after much debugging, I found that the bypass list was populated with bypass_disabled. It looked like this:
I removed it and made the list empty by editing the yaml:
include_bypass: []
This solved the issue. This may be too much of an edge case to matter, and I guess I could have remade the automation easily enough, since its a blueprint, but thought it would be good to let you know. It could probably be solved with an additional check in the bypass enabled check.
This is the trace where I found it. I can share the whole trace if it is helpful
@Blacky - are there any current problems known?
I have the most simplest of setups for testing purposes but it doesnât work. I tested it with a manual automation and it works fine. Light works, sensor gets occupied.
The YAML looks as follows:
alias: Test
description: ""
action: []
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.motion_sensor_hall_occupancy
light_switch:
entity_id:
- light.hall_ceiling
time_delay: 2
include_light_control: []
light_brightness: 1
Iâm not fully understanding the capabilities of this blueprint 
Can somebody please let me know if it would be possible to use this using a grouped âoutdoor lightsâ and grouped âaverage outside luxâ sensors as well as a outdoor motion sensor to do the following:
Ideally the Lux value should be after its been above/below for 15 minutes, But I can live without that.
Or is this (turn on dimmed at âduskâ, full brightness on motion and off at dawn) out of the scope for this blueprint and I should just write my own basic boring automation for it.
Going from V2 to V7 there are many thing you had to do along the way. You can see them in the FAQ down the bottom. Best to just create a new automation fresh. Disable your existing one. Then create a new one. You can reference the old one as you to it. Then once your happy just delete the old automation.
Let us know how you go.
Blacky
Something happen to your YAML and looks like you moved things. Below is a clean YAML for you. Copy and replace your YAML.
alias: Test
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.motion_sensor_hall_occupancy
light_switch:
entity_id:
- light.hall_ceiling
time_delay: 2
Blacky
Your in luck I just updated another blueprint. Looks like you are doing outdoor lights. The blueprint below can work with lux but you may want to consider sun elevation as then it will only turn ON at night. Have a look at the trigger FAQ in the below blueprint for a stairwell as it is the same for what you are doing. If you need a delay then sometimes your motion sensor has a setting for it or you can create a template sensor that has a delay OFF for you motion sensor and then use that template sensor in your night lights state trigger rather than your motion sensor.
If you need help for the template sensor then just let us know but if you using the other blueprint post the question there.
Smart Light - Entity - Sun Elevation - Ambient & Time Triggers
Blacky