šŸ’” Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

I love this blueprint and currently have it set up in two rooms. I’m planning to roll it out to the whole house but it’s a lot of work to duplicate it and set up all the multiple sensors and switches etc. Is there an easier way to reduce the amount of config by perhaps having one blueprint that allows you to keep the same settings but define multiple rooms?

Confirmed the issue. This happens since I updated my HA to 2026.1. The input_boolean seems to be mandatory even when I’m not using scene or script at all. Unlike before, it’s only optional and you don’t need to create any toggle switch to make it work.

1 Like

Thank you.
I’m glad to know that I’m not losing my mind with this.
So this causes no functionality loss to the program, just a slight mind-set inconvenience.
Good to know and thank you for responding positively. I figured it would be at least after the weekend for a response.

JRS

1 Like

@Blacky Thanks! I had initially used entities but it didn’t work, so I tried using the area to debug. Anyway, I switched back to entities as you suggested and it is working fine now :clap: :pray:

1 Like

I’m totally lost on this one, I am only using light entities, triggered by a binary sensor of grouped doors, turning on lights only after sunset and then turning them off after 90s. The lights turn on fine but don’t turn off, even though all doors in the group are closed. Am I supposed to be doing something with the input toggle? Mine also broke after the recent update.

Im new to this blurprint and seeking some advice on how to set up illumination/lux based motion light automation. I just cant seem to figure it out from the docs and everything i tried seems to be working not the way i thought (i think maybe my understanding is incorrect here).

What i have:

  • Living room lights
  • Living room presence/occupancy
  • Living room illumination (lux)

What i want to happen:

  • When living room presence turns on, turn on the lights if LUX is below 50 (if above 50, do nothing).
  • When presence is off, turn off lights.
  • When LUX goes above 50 (and presence is on and lights are OFF), turn off lights
  • When LUX goes below 50 (and presence is on, lights are OFF), turn ON the lights

I can very easily get the presence to turn on/off lights, but i cant seem to correctly have the LUX level immediatly affect the lights. For example, i want the living room lights to turn on when i walk in, but when i open up the window in day time (lux value goes up above the limit), then the lights should turn off, and when i close the window (lux goes down) the lights should turn on again immediately.

Can someone give me some hints on how i should configure this?

Same problem, here:
See: 2026.1: Home is where the dashboard is šŸ„‚ - #258 by Herr.Vorragend

1 Like

Hey @Blacky
First off all nice automations! - I love them! Keep on this great work!

Now for my problem… - I use your automation for like every room in my house now :smiley:

In my living room I have a chandelier with 8 bulbs. - all of them are smart bulbs via zigbee2mqtt and I use different zigbee groups for daytime and nighttime.
So at daytime I have a zigbee group with all 8 bulbs on - and for the nighttime I have a zigbee group only with 4 bulbs on.
I use your automation to simply control the light with a presence sensor - and some different color temperatures.
nothing else really… because in my living room I want to have light as soon as I’m here - no other feature.

My presence detector stays ā€œdetectedā€ for 60 seconds, so I set the ā€œturn off timerā€ in your automation to 4 minutes, so I have like a round 5 minutes before the light will turn off.
This works very well, like most of the time! (not 100%, but well enough I guess :smiley: )

My Problem is the switch between daytime and nighttime. I’m not really sure if the problem exists with the other rooms, but let me explain.

When I am sitting in my living room, the presence detector is like detected the whole time. so the daylight will stay on - now it’s getting to 10pm, where my nighttime light should turn on.
But instead your automation just will turn off the daylight - and I’m sitting in the dark… I can move, I can dance… but the light will stay off.

I think it has to do with the presence detector is not triggering again?.. because it will stay on detected the whole time? - I don’t really know and I hope you can help me.
Is the light not intended to just switch to the nightlight, when presence is detected before the time change? - or at least stay on…

If you need further information, please let me know! - I will give you what’s possible :slight_smile:

Much greetings
Wilhelm

Looks like the right blueprint for my purpose, but I cannot wrap my head around it. What I would like to do is:

  • Turn my outdoor lights on around sunset (i.e. sun elevation dependent) to a certain scene (Hue lamps) and turn them off at a fixed time (e.g. midnight).
  • I want to switch the same lights to a different scene between ~sunset and ~sunrise depending on a motion sensor trigger.

So, between sunset and midnight the lights should return to the first scene after the motion triggered scene, while between midnight and sunrise the light should turn off after the motion triggered scene.

I’m probably missing a small detail but I cannot get the automation to behave like I want.

Can somebody explain how to configure? Thanks!

(Btw, I have this scheme working by using partly an automation in the Hue app, but the automations in that app are not very reliable.)

Just to know…Any way in light control reduce minimum turn off delay under 30 sec.? I’ll try to explain.There are two small rooms, one leading to another, larger room. These rooms are crossed in 10 seconds, so there’s a 30-second delay plus the sensor’s fade time, and the light stays on for 1 minute each time the room is crossed. In these situations, a 10-second delay allows the light to stay on for 20 to 30 seconds, more than enough to avoid being left in the dark.

@s1rT0by

You can but then you will be doing a script and using the script in the Lights - Switches - Scenes - Scripts. If you use a script then you can’t use dynamic lighting.

Blacky :grinning:

@AndyMUK

You can duplicate an automation by clicking on the 3 dots on the right hand side of the automation and selecting duplicate. You then just need to swap out your lights and motion sensors etc.

Blacky :grinning:

@ToadInTheBox

Welcome to the community.

I can’t see your settings but if your just using a group of doors so when one or more are open the lights will come on and when it all of them are closes then you will have the 90s time delay to then turn your lights OFF. If your just using light entities then you don’t need the toggle helper. The toggle helper in Scenes & Scripts - Toggle Helper is only required when you are using Scenes or Scripts. As for the update I am yet to update to the latest Home assistant as I always wait until .3 or more depending on the feedback in the release blog.

Blacky :grinning:

@syrys

Yes it should work like this. In ambient make sure your slected NO - My Ambient Light Sensor is not affected by the Lights and maybe for Ambient Light - High Lux Value set a slightly hire value and maybe use the Ambient Light - High Lux Time Delay

If you would like me to look at it 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.

Blacky :grinning:

Hope HA fixes it.

Blacky :grinning:

@Temnotchort

It will do this and change to your night light settings. There are a few settings that you will need to select. 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.

Blacky :grinning:

@Rodocop

You may need 2 automations.

Try my :high_brightness: Smart Light - Entity - Sun Elevation - Ambient & Time Triggers Blueprint for this. Just set the OFF Time for 23:59:59. So use the sun elevation Sun Elevation Falling - ON to turn the lights ON and then the OFF Time to turn them OFF at 23:59:59. Enable night lights and use the Enable entity state option and then use your motion sensor for the Night Lights - Entity State. In night light control select If lights are ON, adjust the lights when crossing over & Use cross over time delay from night lights to normal lights and set your Cross Over - Time Delay.

Now between sun set and 23:59:59 your light will come ON, when your motion sensor is detected it will apply the night light settings. Then when motion is cleared and after your Cross Over - Time Delay your light will go back to normal lights.

This automation will cover between sunset and midnight.

Now for this part… use this blueprint. Set up sun elevation and time but now the time is set to 12 am to a time past sunrise like 10am. Because both the sun elevation and time must be true for this blueprint to work it will only be active between 12am and your sunrise setting. Then just use your motion sensor as the trigger with the lights you would like ON. Once motion clears it will turn them OFF.

This automation will cover between midnight and sunrise.

Blacky :grinning:

@gggizmo

Yes.

Equation for the Time Delay will be 10 divided by 60 = 0.16. Just type 0.16 value in and click save.

Blacky :grinning:

I have created the following ticket for this.

Thanks for the info… when I update I will look at it.

Blacky :grinning: