Hey, thanks for the reply, however youāve missed the key part, I live in Norway, far north, like its summer right now, and the sun doesnāt start setting till 10pm, in winter thats more like 1pm
edit: To elaborate more on this, right now, sunset is at 10-11pm, and rise is at 1-2am
in winter thats more like, sunrise at 10-11am, and sunset at 1-2pmā¦ see the issue?
The variation there is too much. So the issue ISNT the start, but the second part, hence using the suns elevation to enable a binary trigger similar to an on/off functionality of the schedule triggerā¦
The issue is, even if i used your schedule helper like you suggested, the lights arenāt going off in the morning, just on at night.
So without digging into the yaml, iām curious did you set some kind of "wait for x hours " between the sun set, to the sunrise? because if so, that wont work here.
Then you can use the toggle helper and leave it ON 24/7. The sun elevation condition in the BP is what will actually turn it ON and OFF not the toggle helper.
That is what is used in the blueprint and why I did it that way. It uses sun elevation.
I just ran a live test and it worked perfectly and instantly as soon as the sun elevation changed, no delay. Lights turned OFF. I know the light turn ON because I use that everyday so I donāt need to test that.
Yep, because your worst case is sunset 1pm to sunrise 11am that only leaves 2 hours so just have it ON 24/7. Then use the sun elevation condition in the blueprint to turn the light ON and OFF.
thanks for your fast response and suggested solution.
I previously implemented the bypass option 2 as proposed. However, I encountered the following issue: When I deactivated the night-mode entity in the morning (which was set as a bypass), the lights reverted back to the brightness level selected before the night-mode entity has been activated the evening before, even if absence was detected in the zone. As a result, the light remained on indefinitely, as long as someone entered the zone again, starting the trigger of the blueprint. Is there any alternative solution?
Try not doing it this way. Try to just use the bypass option 2 rather than using night lights and setting the brightness to 0%. Your night-mode entityā¦ what is this? If it is something you turn ON then use it in the bypass. I use do not disturb on my phone. Some people I talked to have a toggle helper and they call in something like āSleep Modeā. or you can have a button near your bed that you push.
This could be because you are using scenes. I have toggle helpers for scenes now. The input is just under were you select your lights in normal lights and night lights. You need 2 toggle helpers, one for normal lights and one for night lights. This is because a scene has no state and the automation has no idea if it is ON or OFF. The toggle helper resolves this.
What I would do is probably something like thisā¦ but I could be totally off the mark of what you are trying to do, so please forgive me if I get it wrong.
No scene at all, have it trigger normal lights 100% brightness (or whatever you like).
When you trigger the bed area, use this as a state condition for night lights and set the brightness to 20% (??). Make sure you also select āIf lights are ON, adjust the lights when crossing overā in night light control.
Some type of entity used for sleep mode, whatever you like and put it into bypass option 2. Turn it ON when you go to bed, turn it OFF when you wake up. Some people use bed sensors, I use do not disturb on my phone, some people use a toggle helper what every you like.
Just a suggestion, add option for sunset and sunrise, with time settings. For example switch on light at sunset - 1h, an hour earlier that sunset, you get the idea. Would be more useful than elevation in my opinion, and easier to customise the timings!
Thanks for your suggestion, as @Nuwanda said you will find the link to the sun condition. I have also just updated it to reflect all the questions I have had in the last few post. You will find why I did it like this by clicking here.
A good example of why I used it is in this post recently click here
@Blacky Hi, not sure when this started happening, but when I turn on my main kitchen lights during the day, my cabinet and floor lights come on. I donāt want this to happen, this should happen only after sunset.
thanks for all your help, I really appreciate it!
I thought thereās no way around scenes if I donāt want to turn the lights off when the trigger is off. But using the night light option instead is an awesome idea. Iāll give it a try the next weeks. Thanks!
why does it turn on the scene ?. what I expect the bypass to do is NOT to activate the automation IF the lights are ON.
the scene is the for motion sensor to turn on cabinets and floor lights IF the main light are NOT on. and IF I turn on the main lights DO NOT activate the motion automation.
Hope that makes sense, I have 2nd automation to turn on the cabinet and floor lights, once sun set has arrived WHEN the main lights turn ON.
What you have is your light.kitchen_lights in bypass 1 - Enable the Bypass - Turn lights ON. When you turn your light ON it will trigger your scene scene.kitchen_motion_light_on. The name of that scene indicates to me that it will turn ON. This is what you are asking of the automation.
If you would like it to turn OFF your scene then try and put your light.kitchen_lights in bypass 2 - Enable the Bypass - Turn lights OFF.
Check this as it looks like you may have conflicts.
Apologies if this has been answered before. I have tried to search and read the docs, but I cannot find an answer to my question. I have scene operated livingroom lights, and that works well, with a physical bypass switch. But is a user clicks the scene in the HA dashboard, I also want the bypass to activate. If we enable āmovie-nightā scene, it is very irritating to get ānormalā activated mid-movie.
How do I orchestrate this? Any suggestions (other than physically using the light-switch!)?