Hi, any chance you could add a by-pass/test for deferring the switch-off event rather than just by-passing the main execution? My use case is having the light persistently switch on while I’m working from home. I have a magic button I click to set a WFH toggle sensor to ‘on’ with a 6 hr delay before it sets the WFH toggle back to off. It also does some other things to do with heating in the room.
In some scenarios I will manually turn off the light out of habit when I go down for lunch, but using your blueprint, the toggle sensor will by-pass/block the reactivation of the light in all scenarios including when the motion sensor detects me coming back into the room within the 6 hrs. I don’t want to reset the 6 hrs on that event, just trigger the light turning back on and blocking/deferring it turning off (even if I’m sitting really still).
There’s probably already a way to do this, but it would be neat if embedded within your blueprint.
A reliable occupancy sensor would do the trick also!
Hi @mjsblume It is probably just me but I am not full understanding what is happening but I will try to answer your post.
you have a magic button that you switch ON and then a time delay of 6 hours starts before it turns itself OFF.
If that magic button is also set in the blueprint it should disable any triggers you have and your lights should work as normal. If you go to lunch and you would like the light OFF you will have to turn it OFF manually. When you get back you will have to turn it back on manually. It will work like this until the magic button 6 hour time delay goes to OFF. If the light is turned ON and then the time delay goes to OFF the light will stay ON until a trigger happens and the blueprint automation runs.
If them magic button is not connected to the by-pass in the blueprint then it should work as normal. The light may turn ON and OFF if you sit still but that is a motion sensor.
If the magic button disables the motion sensor some how…then… not sure what is going on.
If the magic button is connected to the by-pass option in the blueprint and it is ON then this is how it should work. You will have to turn the light on manually.
I think you just need to manually turn the light back ON. If you don’t want to do that then a presence detectors is the go. I haven’t got mine yet as it all sold out but I will be getting one if he makes more.
Then enter a name, in this example we put “Sensor Light - Front Door - Group”. Then select your “Members” or entities (all of them that will be in the blueprint automation). Keep “Hide Members” and “All Entities” toggles OFF as shown below.
Then go back into the automation and in the “Trigger Sensor - Binary Sensors" selection search for the name (Group) you just created in this case “Sensor Light - Front Door - Group” and select it. Now only have one item selected here. If you would like to add more or remove some entities you will have to go back into the helper and edit it (see below)
Now just go through the blueprint and click save. Hopefully you should have resolved your problems.
If you need to edit the Helper. Go back to Settings / Devices & Services / click on the “Helpers” tab / click the helper you would like to edit, in this case “Sensor Light - Front Door - Group”. Click on the cogged wheel.
Before upgrading from Version 1.7 and below please see below upgrade options. If you are installing from new then you don’t need to do anything just install the blueprint.
More user friendly selection for enabling and disabling options.
Bug fix. Fixed a issue where light would not turn ON when option was made. Example: Using the new presence sensors, door sensor, contact sensor that hold their state to ON for long periods and one of the options being sun, LUX or time would pass through its condition and the light would remain OFF until you walk out of the room and entered again resetting the sensor or you would have to close the door and open it again because the trigger is in the ON state. Anyway it is fixed and is worth the upgrade.
Delete the automation, upgrade and set up again.
Follow the steps below.
Go into your automation and click on the three dots. Select “Edit in YAML”
It is really easy to set up.I would recommend you check your sun elevation degrees and set it to your requirements. Every site is different. A easy way to choose your setting is to find or add the sun to your dashboard. When you click on it, a pop up window will appear.
Then one night just watch the sunset and your elevation. Determine what elevation you would like to set so when the trigger is triggered and the sun is below your set point (elevation degrees) the light will come ON. Once you know your preference just change the sun elevation degrees in the blueprint for “Sun Elevation Falling”. You will then do the same for sunrise and enter your setting into “Sun Elevation Rising”
Then just monitor if it is working correctly and to your liking. Change if necessary.
You also have a sun condition in night lights. This is totally separate to the global sun condition. Normally you would choose to use one or the other (Normal lights or night lights). If you are choosing to use both sun conditions in normal light and night lights, it is recommended that you use a lower value for night lights.
I just stumbled accross your blueprint and i think it is great thank you for the hard work and sharing with the community.
I tried the blueprint on a basic light with a motion and a lux sensor and it works great !
However i fail to see why it doesn’t work all the time with multiple binary sensors as trigger. My case is that i have more then 15 lights that rely on motion (sometimes 2 of them), door, and lux sensors. I understand creating helpers … will… help but i’d like to use the blueprint as it was designed so i can change stuff quickly and see all info in one place.
I have automations that rely on multiple triggers and they work just fine.
A example: Motion detected, trigger received automation runs, motion is in the ON state, before it goes to the OFF state the door opened and goes to ON state, LUX goes to ON state and then motion goes to OFF state. Because motion has now gone to the OFF state it is ready to receive the next trigger. The door and the LUX will not send a trigger to the automation until the door is closed and opened again or the LUX go high and low again so the automation waits. The problem happens more when we have sensors that can be in a ON state for a long time like door, LUX, etc.
If you have 3 motion sensors apart from each other it can work well because they normal are only on for short time and keep sending triggers. But in saying that it is possible to have issues.
If you group the motion, door and the LUX sensor together it acts as one trigger. So you trigger motion and it goes to the ON state, then you open the door and it goes to ON state, then your LUX goes to the ON state, your door closes and then is OFF, motion then goes OFF but the LUX is still ON so the group or the trigger is still in a ON state waiting until all sensors go to the OFF state. Once that happens the time delay starts. Hope that make sense.
I try and name the helper group to the automation so I can find it easy. But normally we set it up and forget about it.
HA do a good job with groups so even though I do understand it is nice to have it all in one place as I to would like that, sometimes it is better to use what HA have perfected and maintain well like helper groups.
Here is the link on how to set up helper group if you need it. Click Here
Currently I have a script with a template for the lamp that retrieves the values from the adaptive lighting and adjusts accordingly.
If I let the lamp just turn on, I have partly a short flickering or have to wait a bit until the integration adjusts the lamp.
My script looks like this:
Thank you, I will look into that and update the blueprint.
Mine worked the first time with 2 motions sensors, but looked at the traces showed it stopped (what the). Then I changed it and the traces looked good and it worked. Then I removed it and it didn’t work. Put it back and it works.
I will update the Blueprint with your fix, thanks again.
Now i’m thinking of how to include some other check to keep lights on if standing still. For example check for TV power and if above 100W then do not turn lights off.
I like the idea of having an override switch like it is implemented but i’m the type that always forget to press some button. So an automated check for some entity property would be great.