No, when night lights is active then night glow can be active so night glow is active between 9pm to 6am.
Blacky 
Ok, strange, i have added the auto off as a back up and resolved it (added a timer per light) so that separate automation survives a HASS restart. This blueprint should survive restart on its own though, is that right. I read the info right? Certainly wasnt happening for me.Latest HA and latest version.
For Dynamic Lighting or any other Lux field, is there really not a way to set a lower Lux value than 10?
Im not sure if something is off with my Hue sensor but most of the time the Lux value in my hallway is <10lux, closer to 1-4lux range.
I have 3 motion sensors in different parts of the hallway, 2 Ikea and 1 Hue that i want to use Lux for. If it’s below a certain value like 6lux, is when I want to trigger my lights so that even if it’s the middle of the day but just very dark outside, i want the hallway lights on.
Bypass Problem
Hi Blacky,
first of all: thanks for the great work 
!
I do have a problem with “bypass”: All I want is Sensor Light to NOT DO ANYTHING at all if a certain condition matches. To do so, I assigned a binary sensor as bypass:
alias: sensorlight.bonnieflur
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.occupancy_group_bonnieflur
light_switch:
entity_id:
- light.e27_hue_bonnieflur
- scene.snapshot_lights_all_attributes_mittelflur
ambient_light_sensor: sensor.sens_zb_light01_illuminance
ambient_light_value: 5000
ambient_light_high_value: 0
include_ambient: ambient_enabled
dim_before_off_time_delay: 20
time_delay: 0
light_transition_on: 0.1
light_transition_off: 0.1
include_light_control:
- use_transition
include_bypass:
- bypass_enabled_stop
motion_bypass_lights_stop:
- binary_sensor.con_badtuer_inverted
However, when doing so, the sensor defined in motion_bypass_lights_stop actually triggers the script itself, resulting in Sensor Light turning off my light. So it actually does something.
As I understand, I can define multiple triggers but they are all “OR” logic, right?
Question: Is there a way to really, completely bypass the script based on external conditions?
Great blueprint! However, I’m seeing triggers when home assistant restarts that I don’t understand.
I have 3 identical door sensors and used 3 automations each configured in the same way: Door open, turn some lights on. I thought I fixed unwanted trigger at restart by setting the condition that door sensor has to be off first. But, with the recent core update, a restart triggered one, but not the others!
Is there a best practice to prevent triggers at restart? Ideally, I’d like to trip an alarm if the door opens when it’s not supposed to, but don’t want that happening everytime I have to restart!
Thanks for any help.
and this
Hi: I have a question regarding the time option.
The automation is triggered at end time to turn off lights, not sure it’s the expected behaviour? My understanding is that end time is only for enable/disable the automation and it shouldn’t turn on/off lights.
Edit: also noticed when “Dim Before OFF” is enabled, when automation triggers to turn on the lights, it turn on the lights with brightness 100%. This raises issue for adaptive lighting which I have configured to ignore turn_on command with brightness info. I have double checked “Use Brightness” under light control is disabled.
Been using your blueprint for about a year or so and just wanted to say thanks for the great work and providing this to the community!
Is there a way of using beside a binary sensor an event? I want to activate lights based on events from a finger print sensor of our door.
Sorry for the late response. Have set it and will test it. (if I don’t repsond in the futher it means it worked). And thank you for the help!!!