All good… thanks for getting back to us.
Your welcome.
Blacky 
Hi Yuri
Is your Aqara motion sensor battery operated?
What would be interesting is the logbook of your Aqara motion sensor when this happens. It would be good to see all the actions (state changes) from the trigger ON to when it will not turn OFF the light.
Blacky
@Blacky
Thank you for your prompt response, I will try to explain myself a little better.
My intention with the 60 Min was to be able to define a maximum Light ON time even with the By-pass ON and that after this time both the By-Pass and the light would turn off. ( If during this time no one is detected ).
Which indicates that you forgot that you activated the By-Pass and the light will stay on until you deactivate it. " Children are unpredictable " 
This is to solve when you press and activate the By-Pass but forget to press again to turn off the light and By-Pass.
Let’s say that the light would always turn off if after this time the By-Pass has not been deactivated and there is no movement during that time (Which indicates that no one is there). You would have to turn off the Light and the By-Pass and finish the automation to be ready for the next time.
Hi Blacky,
No, there is no any additional state changes. Just “detected” and “cleared” in about 90 sec. Note, it is more that timeout that was set. Could that be triggering some unexpected execution path?
Thanks,
Yuri
So the by-pass stops the automation from working. The option you have are, ON, OFF or keep the current state when it turns ON, yes you can set an auto OFF for 60min and after that time the by-pass turns OFF and evaluated the automation. It will ether keep the light ON if motion is detected or turn the light OFF after the “By-pass - Time Delay” if no motion is detected.
Yes this is why we have auto OFF. It can also act as a timer.
You dont need to turn OFF the light to activate the automation, you can but it will not activate the automation. To activate the automation when the by-pass is ON is turn OFF the by-pass.
Q: By-pass 101 - Every thing to know about the by-pass and how to use the “Trigger Sensor By-pass” without having a physical switch?
A: Please Click Here
I am not sure if there are any question or if it is not working. Did it work once you selected the correct settings as suggested?
Blacky
1 Like
No
lets look at the logs for your lights and automation. To find your automation in logbook start to type “automation” and then find the automation. Include logs before and after this event in you screen shot.
Blacky
hello Blacky
i Still use two automatisation for one light: morning/day eventing/night. (without sun conditions)
sometimes, whene the time from first automatisation ends and the other automatisation starts, the light turns off and cant turn on with motion (for some time?). (in my example at 07:00 am, wife stands in the dark kitchen “angry” and has to turn on the light with pysical button)
I will PM you.
Thank you so much,
I have changed what you have indicated and I am going to try it.
This is how it turned out, should I now do what I expect?.
alias: Auto Light Comedor v4
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.multi_comedor_home_security_motion_detection
light_switch:
entity_id: light.dimmer_comedor
time_delay: 1
include_dynamic_lighting:
- enable_dynamic_lighting_brightness
dynamic_lighting_lux_sensor: sensor.multi_comedor_illuminance
dynamic_lighting_max_lux: 80
dynamic_lighting_max_brightness: 90
dynamic_lighting_min_brightness: 0
include_bypass:
- bypass_enabled_turn_on
motion_bypass_lights_on:
- input_boolean.estado_auto_luces_comedor
bypass_time_delay: 10
include_bypass_auto_off:
- bypass_auto_off_enabled_off
include_ambient: ambient_disabled
include_night_lights: night_lights_enabled
night_lights:
entity_id: light.dimmer_comedor
night_time_delay: 1
include_night_light_control:
- use_brightness
night_light_brightness: 10
night_lights_conditions:
- time_enabled
night_lights_after_time: "23:00:00"
night_lights_before_time: "07:00:00"
motion_bypass_lights_stop: []
bypass_auto_off_delay: 60
ambient_light_high_value: 80
dynamic_lighting_min_lux: 20
motion_bypass_lights_off: []
ambient_light_sensor: sensor.multi_comedor_illuminance
So your automation never received the clear from the motion sensor. This helps thanks.
One last question. This automation works most of the time but sometimes it leaves the light ON… correct?
Blacky
Hi @Blacky
Just had the same problem with another light:
id: '1699012879992'
alias: Main Entry Closet
description: ''
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.main_entry_closet_occupancy
light_switch:
entity_id: light.main_entry_closet_light
This one is using Tuya sensor.
It there any way to send traces to you or they are not useful?
Thanks,
Yuri
I will PM
Blacky
@Blacky
Thanks, I’ve already changed it. I’ll let you know when I get home how it goes.
Thanks again.
Hello Everyone.
I’m using this blueprint for almost all my lights.
But I have a problem managing the 6 hue ambiance scenes for the living space:
Full Brightness - Normal - Relax - Reading - Dimmed - Movie and Nightlights
With this blueprint, I manage Normal and Nightlights and Movie mode disable the blueprint and sets the lightning (trough the KODI plugin)
For the others, I have to switch to manual mode then fix a mode.
But then I loose the movement detection automation…
What suggestion do you have to manage this ?
Thanks !
I am not sure of what you are trying to do exactly so it this is a bit of a hit and miss… “Dimmed state managed with a schedule” so there is a automation that turns the lights ON to a set brightness and then OFF again (automation 1). Amusing this is at 7pm (ON @ 30% brightness) to 11pm (OFF).
Now we would like to turn the lights on to a higher brightness when motion is detected between 7pm to 11pm and back to 30% brightness.
We will need to create another automation for this (automation 2). Automation 2 uses time from 7:01 pm to 10:49 pm. Note if your delay time is 5 min then set the 10:49 to 10:44. Set the light to 100% brightness or what every you like then create a scene with your lights at 30% brightness and put that scene in “Scenes to turn OFF” Now you lights will go to 100% when triggered and then back to 30% when OFF.
Hi @Blacky , i want the same as @fitz247 and i tried your suggestion but it does not work completely as expected. But i do think the blueprint must be able to.
here is what i did with your blueprint implementation:
front light is on at 20%,
a motion triggers,
ceiling light and front light turn on at 100%,
after time T (5 min) the ceiling light turns off,
in the blue print i call a turn off scene: dim front light at 20%,
result: ceiling light is off and front light is also turned off. Not good! and not expected.
The strange part is: if i start with front light off, it does work. It ends with light ceiling off and front light at 20%. So it seems that is doesn’t work if the light is already on before the blueprint starts??
Is this normal behaviour or am i doing something wrong? ( i have the latest blueprint.)
I do have one other question: why is it not possible to call another automation and why does it have to be a scene?
best regards,
jacco
I was wondering if it would make sense whenever a light is turned off (by inactivity of the trigger) to turn off “related lights” as well.
For example, it is night time and only night lights are on after motion. Light is not enough for the task I’m doing so I explicitly turn on the day lights. When motion is gone and the automation turns off lights, it would turn off Day and Night lights, and not only the one that was turned on by the automation.
wdyt @Blacky ?
Edit: nevermind I believe this can be achieved with scenes