I’ve been using your blueprints for a while now annd love them thank you! I cannot for the life of me get the nightlight mode to trigger on from my motion sensor. It works perfectly during the day time hours I have configured, however at night it will never trigger.
If I run the automation manually during the night it will turn on the lights correctly.
Hi Blacky, this is an amazing blueprint! One small request, is it possible to add an option to specify brightness of bypass? I’m using this to control a zigbee bulb that I typically want at 70%, then 5% for night light mode, but would like it to be at 100% if I activate the bypass switch.
I jumped into the yaml config and it is much more complex than the automation I have ben playing with so far
@Blacky
Hi. Can you add an function for an brightness sensor? So I can simulate the funtion of the hue app for brightness and motion sensor.
So I can choose as input that the motion sensor ist enabled and teh brightness ist above oder under a limit.
Hi Blacky,
Great automation. I love the brightness adjustment based on lux option. I understand we can set night lighting conditions when a boolean switch is turned on. Is there a way to set lighting for other modes (other than night)? The only way I see is to use the bypass feature and have another automation activate a scene. Is this correct or am I missing something?
Louis
@Blacky
Many thanks for your comprehensive and handy blueprints, and for all the support throughout the year.
Merry Christmas and all the best for the New Year!
I need to implement a second state for my lights. They should dim to 50% before they go off. But this only should happed if the turned on by the sensor.
Because you are wanting the automation to run 24/7 you don’t need to enable the main time condition so I have disabled that and cleaned up your YAML as I see there were some old code in there. Also in Night Light Control I enabled If lights are ON, adjust the lights when crossing over so if the lights are ON they will transition to the correct brightness. Up to you if you don’t want that then just disable it. Also consider using the Transition if required. Below is you code fixed up.
Note: If you were not running 24/7 then your main time condition must include the night light time. Example main time from 5pm to 5am and night light time from 10:30pm to 5am. You can see the night light time is included in the main time.
Yeah there is a lot of logic in the code. You could have a custom automation that when you turn the bypass ON it sets your light to 100% but I can see when testing this I need to fix a bit of logic in this blueprint so when you turn the bypass OFF it resets you lights to the correct % value. I will have to update the blueprint for this to work.
When you turn ON a bypass, it executes the action associated with that bypass. If you activate another bypass, the system will perform the action for the newly activated bypass.
Examples:
Turning ON Bypass Option 1 turns the lights ON.
Turning ON Bypass Option 2 turns the lights OFF.
Once all bypasses are turned OFF (cleared), the system evaluates site conditions and reacts based on your trigger settings.
Scenarios:
If the lights are ON and you turn OFF the bypass, they may not turn OFF immediately because:
The trigger is still active.
The Bypass - Time Delay is still in effect.
If the lights are OFF and you turn OFF the bypass while the trigger is active, the lights may turn ON depending on the conditions you’ve set.
Currently there are only 2 modes that I call normal lights and night lights. If you would like more different modes then you could use a script and say if X is on then = ABC lights @ 30% green if XY is ON then = ABC lights @ 60% blue etc. You can make as many as you like…
You would use a scene or script to turn the light ON in Lights - Switches - Scenes - Scripts and then in your Scenes - Scripts To Turn OFF you would use a script to turn your lights first to 50%, delay and then turn OFF.
This is a great blueprint, thankyou. I have a few improvements mainly allow multiple ambient light sensors.
I think I have found a bug or oversight, if I have night glow enabled and dont have all of the “night light entities” selected in the “night glow” entities then the night light entities never end up turning off.
I have a hallway with a few bathrooms that I have 4 of the Third Reality night lights that have a motion, illumination and color bulb. I have 2 of them in them in a hallway and another 2 in bathrooms connected to the hallway. Ideally Id like the lights in the hallway to enable night glow and then have the 2 lights in the bathroom only act as a night light and turn off after no motion. As it is now the lights in the bathroom dont seem to get the off signal.
I have tested it here and it is working… please look at Night Lights - Time Delay as this is the time it will take to transition back to night glow once your motion sensor is clear.
I am working on this blueprint now so if you could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.
Merry Christmas to all and all the best for the New Year!
Your lighting experience, your way – take control and customize it to perfection!
Bugs Fixed
Fixed a bug in the bypass function where, when the bypass was turned ON, changes in site conditions from normal lights to night lights or glow lights were not evaluated correctly when the bypass was turned OFF. This bug has now been resolved.
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
Trying to see if this would work for me. My biggest problem is my cat that keeps me from just using mmWave.
Is it a correct use of the bypass to use the PIR for triggering and mmWave for Keep current state bypass?
I want to trigger with PIR but keep on if mmWave is detecting something.
Ideally I’d like to trigger with PIR, keep on if mmWave is detecting but no longer than 30 minutes (unless PIR is high again).
I would try and look at the problem (The Cat). So there are a few ways.
You could use the Device Tracker so the automation will only run then you are home. If you are away the cat wont / can’t trigger the automation.
Maybe manually turning ON the light but then have the PIR or the mmWave keep the light ON and turn it OFF for you. Take a look at this blueprint Manual light control with auto OFF
Have a look at the Aqara FP2. I don’t have one but I understand that they may ignore cats and only look for humans. You will have to research this.