And how about a light sensor?
In the sensor light blueprint use Ambient, enter in your sensor and adjust your settings.
Blacky 
This is it! It works. I knew you are a genius 
Hi,
Thanks for putting these together; Iām using your fan blueprint already and it works great.
I looked at this and your other lighting blueprints and Iām not sure if it works with my use case: I want to have some lights turn on when I open my garage door to the yard - but only if itās dark - otherwise pointless to have those lights come on.
I looked at the night light option but itās not clear to me if that would be the conditional.
Any thoughts?
Thanks.
You will need to use my 
Sensor Light blueprint. Set up the trigger, your lights and use the Ambient condition, enter in your sensor and adjust your settings. No need for night light.
Tip: If you like to take it to the next level your could set up a template sensor that has auto OFF so when you open / close the door the light will be ON for X amount of time and then turn OFF so the light isnāt always ON when the door is open, then you also use a motion sensor in the garage that will turn the light back ON or keep it ON if you are in the garage. You then use the template sensor and your motion sensor in a sensor group in the trigger. Link to the Ho To for the template sensor click here.
Blacky
Hello Blacky,
Iām using the Smart Light blueprint to turn the outdoor lights on and off based on the sun position, with brightness set to 25%.
The same lights should also be triggered by a motion sensor. When motion is detected, brightness should go up to 75% for a duration of 2 minutes. For this, Iām using the Sensor Light blueprint.
After that, the lights should return to 25% brightness.
Each blueprint works individually, but when I activate both, the lights turn off completely after 2 minutes.
I need some help with this. Thanks in advance!
Welcome to the community.
This is something on my list to do in the sensor light blueprint.
Until then because you already have 2 automations set up, in the sensor light blueprint automation create a scene with your lights at 25%ā¦ then add that scene into Scenes - Scripts To Turn OFF. Try that and and see if that works. If you see a light flicker when it goes from 100% to 25% then you may need to create another scene with your lights at 100% and add it into Lights - Switches - Scenes - Scripts (no light entities only the scene). If you do that then create a toggle helper and add it into Scenes & Scripts - Toggle Helper.
To create a scene go to settings > automation & scenes > scenes tab at top, then and add scene. Add your light entities in, then click on them and set them how you would like them and save the scene.
Let us know if that works for you as I havenāt tested it.
Blacky
FAQ - Smart Light Blueprint V Sensor Light Blueprint
1. What are the primary differences between the Sensor Light and Smart Light Blueprints?
-
Sensor Light Blueprint is specifically designed for dynamic triggers like binary sensors (e.g., motion sensors, presence sensors, etc.). It includes a wide range of conditions such as sun elevation, ambient light, time-based options, and device tracking to control when the automation will activate. This makes it ideal for areas where lighting should respond to real-time, unpredictable triggers, such as motion or presence sensors that can change state at any moment.
-
Smart Light Blueprint is built for fixed triggers such as entity states, sun elevation, ambient light, and time-based options to turn lights on or off. Apart from the entity state trigger, all other triggers in this blueprint are based on fixed schedules instead of dynamic conditions. This means they activate lights based on predictable, scheduled events like sunrise/sunset, ambient light thresholds, or specific times. Itās best suited for scheduled, consistent lighting needs and is not designed for use with motion sensors or other dynamic triggers.
2. Trigger Type:
-
Sensor Light Blueprint is designed for dynamic triggers, which are typically binary sensors like motion sensors or presence sensors. These sensors can change state at any moment, making the lighting responsive to real-time events.
-
Smart Light Blueprint is intended for fixed triggers, such as entity states (on/off), sun elevation, ambient light levels, and specific times. These triggers are usually more predictable and occur on a fixed schedule.
3. Which blueprint is better for motion-sensor-based lighting?
- Sensor Light Blueprint is optimized for motion sensors and other binary triggers, allowing detailed control over activation, time delays, and continuous lighting when sensors are re-triggered.
4. What are the different condition options available in each blueprint?
-
Sensor Light Blueprint offers a variety of conditions to control when the automation is allowed to run, including:
- Sun Elevation: Based on the sunās position in the sky.
- Ambient Light: Based on light levels in the environment.
- Time-Based Options: Allows you to define specific time periods on given days for activation.
- Device Tracking: Uses presence detection to ensure automation only runs when someone is home.
-
Smart Light Blueprint, on the other hand, only has Weekdays as a condition to control when the automation is allowed to run, allowing you to specify the day of the week. As you can see, the conditions in the Sensor Light Blueprint (such as sun elevation, ambient light, and time) are essentially used as triggers in the Smart Light Blueprint.
5. How does each blueprint handle dynamic lighting?
-
Both blueprints support Dynamic Lighting, where brightness and color temperature can be automatically adjusted based on lux levels or sun position.
-
The Sensor Light Blueprint also allows fine-tuning of Dynamic Lighting based on sun elevation and lux, as these are added conditions that can further control how lighting behaves.
6. What is the difference in the manual override or bypass options?
- Both blueprints have manual override/bypass options that work the same way. They allow you to manually control the lights and prevent automatic activation when needed. In both blueprints, you can bypass the automation rules and gain full control over the lights, ensuring they donāt automatically turn on or off based on the triggers or conditions set in the blueprint.
7. How do the blueprints handle Night Lights?
- Both blueprints include a Night Lights Mode, which can be automatically enabled based on entity state, a given time period, or sun elevation. This ensures that the lighting behaves appropriately for nighttime use, offering a softer and more comfortable lighting experience.
In Closing:
-
The Sensor Light Blueprint is best suited for environments where lighting needs to react to real-time, dynamic changes, such as motion or presence detection. Itās ideal for scenarios where you need flexibility and immediate response to unpredictable events.
Example: Walk into a room and the light turns ON. When you leave, the light will turn OFF with a delay. Open a door and the light turns ON, with the light turning OFF with a delay when the door is closed.
-
The Smart Light Blueprint, on the other hand, is designed for more predictable, scheduled lighting setups. Itās perfect for automations based on fixed events like specific times of the day, sun elevation, or ambient light levels, without the need for dynamic triggers. This blueprint offers a more consistent, scheduled lighting experience, where triggers occur based on fixed schedules rather than changing conditions.
Example: Turn the light ON when the sun sets and turn it OFF at a set time, such as 11pm. Open a door and the light turns ON, close the door and the light turns OFF (no delay).
Enjoy
Blacky 
Back to FAQ: Click Here
2 Likes
Hello Blacky, Is there a way to delay the night lights from going back to normal lighting effects right after for example the motion sensor clears motion or door closes. Iām using a helper atm with an automation timer. Maybe Iām missing something. In sensor light we can set a delay to turn the lights off.
I can see that would be a good option when crossing over from night lights to normal lights. I will put it on the list to do.
Also have a look at the sensor light blueprint as it now has a night glow.
Blacky
1 Like
Thanks Blacky
Dear all,
I am trying this blueprint in order to switch on some lights depending on the value of an illumination sensor. But the trigger doesnāt seem to fire. I tried to debug it by using trace, but canāt see any reason why it doesnāt.
I also was under the impression that when you run the automation and it is dark (sensor reporting 0 lux) it should switch the light on, shouldnāt it?
I by the way also use the CCA blueprint which works when it comes to timing, but doesnāt when it comes for illumination sensor; maybe the same issue.
Find here the yaml code for the blueprint parameters:
id: '1733137666873'
alias: Smart Light Stern Arbeitszimmer
description: ''
use_blueprint:
path: Blackshome/smart-light.yaml
input:
include_ambient:
- ambient_low
- ambient_high
ambient_light_sensor: sensor.hm_sen_li_o_peq1447533_lux
include_time: []
light_switch:
entity_id: switch.sw_02_none
ambient_light_value: 40
ambient_light_value_off: 50
include_weekdays: weekday_disabled
weekday_options: []
include_bypass: []
bypass_lights_on: []
bypass_lights_off: []
Thanks for any hint, even if it is only a hint how to debug that stuff. The trace visual editor is not really my preferred choice :-).
BR,
Carsten.
Thanks for your YAML. I tested it here with your settings and it worked perfectly.
This is how I tested it.
- Lux sensor is high above 40. Make the lux sensor go below 40, light turns ON.
- Lux sensor is now below 40 then make it go above 50 and light turns OFF.
You canāt use the run in the automation to test it. The sensor must go from high to low and then from low to high. All your setting are good.
Blacky
Good Morning Blacky,
first of all: thanks for your wonderful blueprints and for testing my YAML. In fact most of the automations also worked in my home this morning as a nice surprise!
I started already to understand what went wrong when I went to bed after 4 hours of testing yesterday. You know I am coming from FHEM with what is called a DOIF. It will permanently check whether the values of e.g. the light sensor are fitting the requirements or we are still in a certain time range.
I now know that HA is working different here: it will need the eventās transition to fire. Running the automation will not check that the light sensor is still underneath the value.
Hence it worked, as it did for my shutter control blueprint. I am very happy now!
Best Regards,
Carsten.
Your welcome Carsten, glad you got it working and thanks for letting us know.
Enjoy
Blacky
could you add the option to make the lights work only when someone is home? like in the other blueprints
Thanks
First let me say how much your work has made my life easier! I was ready to pull my hair out until i found your automations
One issue im having, my lights arent transitioning colors/brightness on a new time.
Example
Lights on 4pm - white 100%
Lights on 9pm - blue 50%
At 9pm they are staying white 100% and not switching. Pretty much if the lights are on, they wont transition at all.
Edit this is for a couple govee bulbs and a hue strip
Hopefully ive added what you need. This is day 5 of me learning HA lol.
alias: Test
description: āā
use_blueprint:
path: Blackshome/smart-light.yaml
input:
include_time:
- time_on
after_time: ā15:00:00ā
light_switch:
entity_id:
- light.living_room_lamp
- light.kitchen_under_cabinet
include_light_control:
- use_brightness
- use_transition
include_weekdays: weekday_enabled
include_light_colour_control: use_rgb_colour
light_rgb_colour:
- 255
- 0
- 0
I am assuming you are going to turn the lights OFF manually.
This will turn your lights ON at 4pm white at 100% and then at 9pm they will switch to blue at 50%. At 8am they will go back to white at 100% if you donāt turn them OFF. Notice how I have used night lights, we only need to use weekday if you only what it to run a a few days but if it is everyday then we donāt need to enable this option.
Copy the code below and paste it into your automation. TIP: When you paste code into this forum if you use the </> in the editor and then paste your code into there it will keep the format it should be, like below.
alias: Test
description: ""
use_blueprint:
path: Blackshome/smart-light.yaml
input:
include_time:
- time_on
after_time: "16:00:00"
light_switch:
entity_id:
- light.living_room_lamp
- light.kitchen_under_cabinet
include_light_control:
- use_brightness
- use_transition
include_night_lights: night_lights_enabled
night_lights_conditions:
- time_enabled
night_lights_after_time: "21:00:00"
night_lights_before_time: "08:00:00"
night_lights:
entity_id:
- light.living_room_lamp
- light.kitchen_under_cabinet
include_night_light_control:
- use_brightness
- use_transition
- if_lights_are_on_adjust_when_crossing_over
night_light_brightness: 50
include_light_colour_control: use_rgb_colour
include_night_light_colour_control: use_rgb_colour
night_light_rgb_colour:
- 0
- 0
- 255
Let us know how you go.
Blacky