Hi @Blacky great blueprint, and as an HA beginner I am overwhelmed by all the options. Just a quick question: I would love to use the night light option to have the lights not so bright during nighttime. I have to enter the Night Light start time and end time during creating the automation. But I would prefer to use sunset and sunrise time, not the fixed time values. There is already a “sun” option in the blueprint, but it does not seem to be related to the Night Light feature? Is it possible to have a flexible (sunset and sunrise) time set for the Night Light option?
Edit: found in this thread it is on your roadmap already… hope to see it implemented soon
Blacky, does it make sense to have more than one light-turn-off duration setting if we have more than one entity or device turned on by the trigger? For instance, once my motion sensor in the bathroom is triggered the lights turn on and so does the fan. It’ll be nice to set the lights to turn off 30 seconds after the last motion but the fan to turn off maybe 5 minutes later to exhaust the humid air.
It is not the smiley face that the logs show it is the;
This was introduce in Home Assistant 2023.3. I think I may have jumped the gun on this one and included it to fast. I have now removed it from all my blueprints and you should be good to go. Next time I should wait 1 year before doing this type of thing again
Again thanks for letting me know, and you should be all good now.
this is one thing I was afraid of, but I do use this blueprint and every feature in my HA everyday. Once you get to know it hopefully you will to. A good starting point is to read “The Settings & Best Practice Guidelines” Click Here.
Your correct in what you are saying. Another feature . This is on the road map and I have developed already 3 different ways to make this work. I am just trying to decide on the best way to implement it so new users dont become overwhelmed by all the options and it works with ease. So this is something you may see sooner than latter. For now use time and stay tuned.
Thanks for reaching out and your suggestion / question.
Hi Harry, if you are in the bathroom and you are removing humidity could I suggest you have a look at my Bathroom Humidity Exhaust Fan. Once you set it up correctly you will wonder how you lived without it. You then will have 2 automations in your bathroom and they work perfectly together. You will then achieve what you are trying to do.
Great! I would prefer a checkbox for “Night Light Sun Option” and for “Night Light fixed time”. And then simply take the Sun / Elevation configuration from the upper sun option. But of course, just a wish, you may have other factors to consider.
In terms of the bypass, this did confuse me a bit at the beginning. But I am finding my family/guests are confused.
When they walk in the room it is clear, the light is on so they ignore everything. But when they leave their habit is to turn off the light, they I see them pressing the button and cannot figure out what is happening whilst the off timer is going.
I am wondering if there should be an option in which the switch will just cut the light (automation) immediately?
So then they will “feel” they did something even though it doesnt matter.
Hi thanks for the reply, I don’t want to make them a group as I don’t want the mmWave presence sensor to trigger the automation as it can sometimes be too sensitive but would like it to be used to keep the lights on and then turn them off once no presence is detected.
This is what we need to look at (your mmWave presence sensor). You have a few options and because I don’t know what mmWave presence sensor you have I will provide some general information.
If your mmWave presence sensor is done with ESPHome then you can put a delay ON. The forum is very active there and you should get some help if you ask a the question on how to do this.
You could go into the settings of the mmWave presence sensor and adjust the sensitivity.
You could create a template sensor that has a delay ON. Below is the code that you will need to put into your configuration.yaml file and restart Home Assistant.
This is the code to create a template sensor. with this code your mmWave presence sensor must be ON for 1 minute for it to change its state to ON thus no longer too sensitive. Once you create this sensor you can adjust the “delay_on” time to suit you as you will be the only one that will know what works. Every time you change it you must restart HA.
In the code below to suit you;
Change the name of your “kitchen_mmwave_presence_sensor”
Change the friendly name “Kitchen mmWave Sensor”
Enter your mmWave presence sensor into here “binary_sensor.your_mmWave_presence_sensor_here”
No, without getting to technical if you have multiple sensors for the trigger it is best to group them. Then they will act like one sensor and the automation will work perfectly. In saying that I do have multiple sensors (3 off them) down my hallway and I have added them individually, but they are ON for about 2 seconds and by the time I get to the 3rd one the first one is OFF. So in this type of situation it works but most of the time if you have a room with multiple sensors then it is best to group them.
For more information on how to set up group sensors please Click Here.
I could use scripts to build an automation that sets a group of lights to 100% brightness when movement is detected and then after the time delay sets it back down to a given value from an input helper on the dashboard.
I’m currently doing this with your blueprint using scenes, but without the option to adjust the lower brightness value from an input helper