💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

thanks for the suggestion :slight_smile:

I’m trying to stay away from helpers and the likes as with more then 200 automation devices in the house i lose track of all the helpers / template sensors and all. So trying to keep as much stuff related to an automation in the automation itself.

Hi @Momo

Sorry I have just been away for the last few days.

Regards to your points.

1/ “Dimmable lights”… Not 100% sure here. Some people have PM me and they are using Adaptive Lighting. Not sure if this is what you are looking for.
2/ Regards to “Multiple ambient Light Sensors” Yes this can be done and if you like I can PM you and show you how to set this up. Just let us know. Not sure if I would add this into the blueprint as it could cause issues but hay it is HA so if you would like it in your automation then why not.
3/ “reduce traffic” … if we have to check it then lets just send a command… same, same or maybe I am not understanding zwave/zigbee networks.

Q: how does the bypass works?

A: It just checks if it is ON or OFF… no time period. Maybe you can explain it more with your “binary motion sensor as bypass” and we can get this to work for you.

Hi Blacky :slight_smile:


  1. I know about the Adaptive Lightning, but that is way complicated and complex for some simple dimmers. I’m just looking for a slider to control a dimmer.
  2. yes pls show how to add multiple light sensors.
  3. entities imported into HA from other Zwave / Zigbee networks/hubs - i’m talking about reducing radio traffic over those networks, because when the network is big (100+ devices) extra network traffic can create lag. At this point the automation is sending On or Off everytime it is trigered , which is quite ofter if you keep moving in front of the motion sensor. What i am asking is if it is possible to check the state of the light first as this has 0 traffic in zwave/zigbee network - it checks against HA state, then sends the actual command if it is not in the required state.


Hi Momo

  1. So the easy way to achieve this is to use a scene and set the brightness there. I will look more into this.
  2. I will PM you.
  3. The automation needs to restart to reset the time delay. One way you could achieve this is if you have multiple triggers and they stay ON for a long time. Like in your home office and your computers power binary sensor and put it in a group. That way it will sit there waiting for it to go into a OFF state. The other thing I can think of is if your motion sensor as a inbuilt delay and adjust that so it stays ON for a longer time. I think you were looking into that.

Hello @Blacky thanks for your effort on this Blueprint, I’m very interested on use the “Sun” condition, but I’m not quite sure if I can achieve that using the sun elevation, so maybe you can enlighten me.

The thing is, that I want to replace HomeKit automations, and on mostly of them I have a time before sunset an a time after sunrise for trigger, like this:

That is something that I can manage with the sun elevation degrees ?

Thanks in advance !!

Hi @garanda21

Have a read of our FAQ in regards to sun. Below is the link. Once you have done that let us know what you think.

Click Here

Sun elevation and time after sunset / before sunrise can get quite a different result specially if you are way north on south in the planet.
If you are above the polar circle the sunset not even happens for some days during the year and closer to those days you still having light over all night long, as the angle is not gonna be too low regardless how many hours after the sunset.
In the other hands, during winter, you cannot have a sunrise for days, but in some days could be quite clear, as the Sun gets quite close to the horizon.
The closer you are to those extremes the easier to see the difference, but that is valid everywhere (to certain level).

1 Like

Also remember this time is not a trigger but a condition for the trigger. In saying that it will trigger on time if the trigger sensor is in the ON state and it passes through the start time, sun elevation or LUX value. It will then turn the lights ON.

1 Like
  1. Brightness is done something like here Motion-activated Light-brightness. Scenes are really not the best way to do it.

  2. thanks

  3. I think a condition can be introduced right before the action ?! If state is on then skip, else turn on or something along those lines.

  1. I quickly did the brightness before but when testing it, if a light didn’t have the ability to adjust the brightness then the light didn’t turn ON. If all the light can be adjusted to a brightness then it worked and it set them all to the same brightness.

  2. no problem

  3. If you have a condition just before the action then it will never turn the light OFF. Maybe give us a example of the condition you are thinking of.

It is not a special condition, just a check if the light is on or off. It should not impact the OFF function or anything else. So just before sending the off comand, check the state of the light. If it’s off already then do nothing, if it’s on call service turn_off.

Why do you think it will never turn off? I could be missing something obvious :innocent:

Thanks for your response and advices, totally understood. I’m going to take a look into it.

1 Like

Scenes are used by 99.6% of the active installations. With scenes you can change the brightness, colour and effect of each individual light. It is maintained by HA, so it is a really good way of doing it. If you would like to change the brightness according to the time of day / sun position then Adaptive Lightning is really not that complicated. I have also explained the simple slider for brightness, hope this make sense and is why scenes just work and it is simple.

If we check if the light is ON before we turn it OFF knowing that we just turned it ON is not going to reduce traffic it will increase traffic and code. If we put a condition in before we turn it ON say “if OFF then turn ON” to reduce traffic then the first motion detected will turn the light ON but because the automation is a “restart” then if motion is detected again it should stop and not turn the light OFF.

The “ON / OFF every time it is triggered” looks to be your motion sensor not the automation. This is why I suggested a group or your inbuilt motion sensor delay. When a trigger is received it will only send a ON, wait until motion is not detected then the time delay has to pass and then turn light OFF. If you stop it with a condition then it will never send a OFF and the light will stay ON.

Hope this helps and makes sense.

Thank you for the patience and very detailed info :smiley: Things are clearer now. But i still do not like scenes :rofl:

Hi Blacky,

great Blueprint you created - thx for sharing.
As i found your blueprint i thought all my wishes comes true …but :wink:

There is a little issue in the end for me.
My problem is, that the motion sensor is the same as the brightness sensor.
So after the first trigger ( Motion on, brightness under 20 ) light goes on.
I move in front of the motion sensor and he should retrigger the automation as long as i´m in the room.
But that do not happen , because the condition “brightness under 20” is no more true because the light is on :frowning: . So the automation waits definded time (120s) and the light switch off -
Is there a way to check the automation is trigger the second time and so the condition “brightness under 20” will switch off or a simlilar logic ??

I hope you understand my issue …

I have many motion sensors with integrated LUX, so i know what you mean :smiley: The only solution i found for this was to tweak the LUX value, so those 20 in your case to a number which is higher then when the light is on.

I thought on something like check the retrigger index (starting with 0, if the automtions starts the first time after switch off) in the conditions togther with the brightness check.
→ condition sample: "… if the brightness is under 20 or the retrigger counter is not 0 … "
Don´t know how to implement this in detail, but i will go reading and check if this could be a way to solve this…

Hi @EsserA

Is it possible to use the sun condition rather than the LUX?

This can be done just trying to understand the use case and if other people would like it too. This way if I add it to the blueprint we get it right.

1 Like

Hi Blacky
This is amazing!! It worked to solve my biggest marriage conflict so thank you for that :laughing: . I didn’t create the helper switch and it just works fine without but bypass only works when I turn on the light manually on home assistant but it doesn’t work when I use the physical switch thats on my wall. Is there anyway around it?
I’m thinking it may work if I put a few seconds delay: when the lights turn off then motion is detected again wait a few seconds before turning on the light again and before the motion sensor triggers the light I will use the physical switch to turn the light on, I have no clue of why I think it may work.

Cheers :beer:

love it :+1:

If you have a physical by-pass it must have a “ON” & a “OFF” state (not ON/OFF). It should work perfectly if you manually turn a light ON or OFF from either HA or the physical switch on the wall.

So if the by-pass is in the “ON” state you should be able to turn the light/s ON & OFF manually with a physical switch on the wall or in HA and they should stay ON or OFF depending on what you have selected (No delay time OFF). When you turn the by-pass OFF you will then have to manually turn OFF the lights unless all the options are true, and the trigger is triggered… it will then start the automation and turn OFF the lights.

I tested it again here and it worked. If you can check yours again and let me know it would be appreciated. :slightly_smiling_face:

Delays and that kind of stuff can break the blueprint. I would like the blueprint to just work an you shouldn’t have to do anything. Plug and play. If you would be so kind and check again and let us know.