Maintenance 
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 
Hey @Blacky , thanks for pointing that out, Iāve been playing the 1000 possibilities up and down for a month now, but itās the switched on light that changes my lux value positively by a whole 13lux. My first technique was to set the heartbeat high, but then I just get a change far too late in changeable cloudy weather that it puts the whole technique offside. As my sensor is very fast, I decided to go to 0.25-0.5 heartbeat.
My dimming value of the lamp is at 0% - 40%
My maximum value is 42lux/40% and ends at 71lux/0%
This results in 71lux - 42lux = 29lux/40pp, as the light is also for 13lux as mentioned above, it starts immediately and then jumps through its own light like a madman, which is logical. Sure, I can now increase the range between 42lux - 71lux, but then I have to increase the % value again and the cat bites its tail (itās a German saying when youāre going round in circles 
).
If you could set the offet value of your lamp, it would somehow all make more sense. Now letās imagine that everything remains the same, the weather, the position of the sun, the external reflections, i.e. the lux value is 50 and the light switches on with the value it would take at a value of 50. The next moment, however, the light value is at 63lux and this is only due to the light being switched on, in which case it would immediately adjust again. The offset value must be included in the calculation, otherwise it would keep adjusting itself and the biggest adjustment comes from switching the light on.
sorry a lot of text, very unsorted and then also in bad english.
thank you for always caring, itās crazy how you always get it all through your head.
best regards
seger
Thanks for your detail explanation .
Because we can use the transition in the light control options try using this. The slider will only allow you to set 5 / 30 seconds but just type the number in and click save. You say your sensor is fast and that is great . Not sure how fast it is but if it is instant then try using 180 seconds = 3 min in both then play around with it and see what happens. You can also play around with the heartbeat and see what happens now the transition is slow. The heartbeat has to be faster than the transition or transition will do nothing. Set heartbeat to 0.25 and then adjust from there.
Blacky 
I have made some graphs for the new sun elevation feature used in Dynamic Lighting. Hopefully this will give you a better understanding of the settings. You can bring the start and end to be closer together or your can expand them out. You can also adjust the colour temps and brightness %. It is all up to you and what you would like to do. I think graphs just tell a thousand words. Hope this helps you to better understand sun elevation in Dynamic Lighting.
The setting in these graphs were.
Max Brightness Value = 100%
Min Brightness Value = 30%
Max Colour Temperature = 6500 k
Min Colour Temperature = 2000 k
Sun Elevation Rising - Start Point = 1.5 deg
Sun Elevation Rising - End Point = 35 deg
Sun Elevation Descending - Start Point = 35 deg
Sun Elevation Descending - End Point = 4.0 deg
The lowest you can go in elevation is -10.0 deg below this it will return your minimum settings.
This is how it looks in a sensor card
Edit: More information on Dynamic Lighting can be found here.
Hope this helps
Enjoy
Blacky
Hey @Blacky thank you as always!
I think one of my next problems is that all my newly installed lamps (ceiling lamps / 10 pieces) do not support transition 
At least here in the overview: AwoX 33955 control via MQTT | Zigbee2MQTT.
Not listed and when I had set it at the time, the lamps no longer switched off. So the switch-off command was executed and the lamp was still on at about 2%. But try it again.
I also set the min. lux value to = 20lux to reduce the range of the brightness value to be changed in relation to the individual lux counters. Itās probably really the missing transition that makes it seem strange to me.
Thank you very much, I wonāt give up yet.
Best regards
Seger
Hi @Blacky, thanks for building an awesome blueprint!
Iād like to request 2 enhancements if possible, please:
The scenario Iām trying to build is for the lights in my main kitchen and dining area.
Iād like the Motion Sensor to trigger the kitchen lighting scene between 30mins before Sunset and midnight.
This time is the main meal preparation and eating time, so the lights should remain on, even if thereās no movement detected.
Then, later in the evening the Nightlight schedule opens and the lights are allowed to switch on and off based on movement.
Then, the whole automation is off (conditioned) after midnight.
I know I can configure this with multiple automations, but it would be nice to have it contained into a single control.
Thanks in advance.
I understand that you can not use a physical connected switch as a by-pass.
However isnāt it possible to use a timed on/off/on/off sequence of such a switch to configure a state of a virtual on/off switch. the last one could be used as a condition for the by-pass.
In that case: to pauze the automation: turn light two times (within 10 sec) on and off. And to restart automation. do the same.
Or am I missing something?
Kind regards,
Victor
Hello @Blacky 
Thank you for this fabulous blueprint! 
I have two issues :
Did you have any tips to help me? What Iāve done wrong? I tried many configurationsā¦
Here is a snapshot of a yaml config that Iāve tried : https://pastes.io/itrr5axsc7
Thanks a lot!
Bertrand
Welcome to the community.
You can use a physical switch as long as it is not your light switch.
I have thought about it but best to have separate switch for this as it will upset the automationā¦ so then if you have a separate switch just use the by-passā¦ I have gone down a few rabbit holes and one day I will find that rabbit and it wont even be in the holeā¦ it will be directly in fount of me.
Blacky
Blacky
Welcome to the community.
I have looked at your yamlā¦ thanks. With your set up the automation will not run because you are using devices in āLights - Switches - Scenes - Scriptsā you need to expand down to entities. Click Here on the how to.
Looks like you would like to also use night lights. You will need to input your lights as entities in also in āNight Lightsā.
TIP: You can paste your yaml in the forum. use the </> button then paste it in there as it will keep its format.
Blacky
Thank you @Blacky !
But I have another issue. In fact, I was using an old automation inside Hue app. I have deleted it, and the room.
Now, I realize that the blueprint has never been executed. It is marked: last trigger / never. I donāt have any log.
Any clue to solve that? 
I have recapped your posts and it is on my mind alias: LumiĆØre entrĆ©e dynamique
description: ""
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.capteur_entree_mouvement
light_switch:
entity_id:
- light.hue_ambiance_lamp_2
- light.hue_ambiance_lamp_1
time_delay: 2
include_light_control:
- use_transition
- use_colour_temperature
include_dynamic_lighting: enable_sun_elevation_colour_brightness
dynamic_lighting_lux_sensor: sensor.capteur_entree_eclairement
night_time_delay: 3
include_night_light_control:
- use_brightness
- use_colour_temperature
- use_transition
- if_lights_are_on_adjust_when_crossing_over
include_night_lights: night_lights_enabled
night_lights:
entity_id:
- light.hue_ambiance_lamp_2
- light.hue_ambiance_lamp_1
night_light_transition_off: 5
light_transition_off: 3
night_lights_after_time: "23:00:00"
night_lights_conditions:
- time_enabled
night_lights_before_time: "07:00:00"
dynamic_lighting_max_colour_temp: 2500
dynamic_lighting_min_colour_temp: 2000
dynamic_lighting_min_brightness: 100
dynamic_lighting_max_brightness: 34
night_light_colour_temperature: 1
light_colour_temperature: 3000
motion_bypass_lights_on:
- input_boolean.forcer_lumiere_entree
- input_button.force_lumiere_entree
bypass_time_delay: 1.5
motion_bypass_lights_off: []
include_bypass:
- bypass_enabled_turn_on
include_bypass_auto_off:
- bypass_auto_off_enabled_on
light_brightness: 12
@blacky I can run the Sensor Light automation manualy but I canāt trigger it with my Hue Motion Sensor. This sensor is already used in another automation with success. I donāt understand why I canāt trigger your blueprint with it.
Yaml. automation reloaded after saving.
really the right motion sensor above
perhaps it has to be the other way round?
edit: just on the way, the other way round may also be wrong.
look at the sensor, hue always has 2 sensors, one does not change.
I donāt edit the config in YAML. Itās just for sharing.
I donāt understand 
Well spotted It was for testing purpose. I switched it!
I only have one binary sensor :
I finally managed to trigger the automation. Iāve unchecked the By-pass options!
I have to fix my by-pass entities. So right now the main blueprint is working! 
Sorry for my last posts!
Hi All,
i was wondering if you intend on adding the create scene option to this blue print (i believe one of your additional blue prints has this already, but is designed for media centre activation and so i cant see an obvious way of using it for a motion sensor light (with lux and time on options). (please shout if there is a motion sensor compatible option (i currently only use the lux and on time option of the blueprint using scenes.
the use case is as follows
i have a long WLED light strip over my porch and garage as part of permanent holiday lighting and when motion is triggered i light up a section as a security light. during most of the year this works great and i have defined two scenes porch light on and porch light off. however when the lights are in use in holiday mode (twinkling or some such) the blue print either goes from twinkle to porch to off (as blue print intended) or if i change the off scene to twinkle the twinkle mode stays on all night when in reality a create scene when motion detected would (i think work in both scenarios.
Holiday mode - scene capture - porch light on back to holiday mode
late at night when holiday mode off - off mode (scene capture) to porch light to off mode.
there may be some edge cases where timing is aginst it but in most cases this would work. with a separate automation simply turning holiday mode on at time x and off at time y.
Hopefully the above makes sense and if anyone can think of an alternate way of achieving this - happy to hear options too.
thanks for a great blue print and the extensive support provided in this thread
Looks like a script may serve you better and turn that script on. Then you can run a set of actions to your liking.
Blacky
Hi,
is it possible to use an input_boolean as an entity to switch?
I have a helper switch, which will turn on and off my infrarot Candles over a Broadlink IR Transmitter.
