that was the mistake - sorry and thank you
💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights
Could you confirm what version you are on. If you are not on Version 3.6 or above could you please update and let us know.
Q: How do you update the blueprint and not delete / recreate existing automations?
A Please follow these steps Click Here.
EDIT: I have just checked it here with your settings and I have no bugs. I am on Version 3.7 that will be releases soon but Version 3.6 should stop these bugs as I spent allot of time fixing them in the last release
You can now select a by-pass option to turn the lights ON when you turn the by-pass ON. This will now allow you to use the by-pass like a normal physical switch.
It is only when you turn the by-pass OFF that it will check the trigger, and if the trigger is ON it will leave or turn the lights ON. If the trigger is OFF it will turn the lights OFF. Remember when the automation turn your lights OFF you have an extra setting “By-pass Time Delay” so if you would like it to instantly turn your lights OFF you would set this to “0”. This is the same function no matter what enable option you choose.
We have also update the by-pass enable options description in the hope it will be clearer when selecting one of the three enable option.
Awesome as usual @Blacky, you work at the speed of light!
P.S. Btw - couldn’t donate to you from my country, do you happen to have other donation platforms you use?
I couldn’t find the donation option. Please link.
Thanks @samuelthng glad you like it
I will PM you.
Hi again @Blacky
I’ve been keeping an eye on this thread and keeping track of all the latest versions and features. I’m wondering if this latest release, if my understanding is correct, now allows for the scenario I asked about in April?
It sounds like it might, and allow the motion sensor, door sensor and smart switch override/bypass to combine to allow for occupancy automation with temporary bypass via smart switch?
If so, I’ll disable my current automation and give this blueprint a try Keep up the great work!
Done. I would encourage everyone here too click that link. Blacky does great work on this and other blueprints. This should really become part of stock homeassistant
First just want to say thanks for this awesome blueprint, now, would it be possible when using a scene to run on activate, instead of choosing another scene scene to return to ie ‘scene off’, could you add the ability to use “call service - create scene” and chose the entities to that we could watch and return too, this would be so much better than a scene that could have changed since we created it (ie the colour / brightness could be controlled via another automation)
like in the screenshot you would create a scene named something ie.
before, then for the return part (like you do now) you would just activate this scene
I would get errors like this a lot especially after a reboot. Version 3.6 has seemed to fix all the errors I was getting. Although errors were showing up in the log none of my automations ever failed to run properly, that I’m aware of.
Yeah I’m using this exact use case, but do take note, the blueprint does not modify your bypass. So if you need the bypass to turn off, you have to turn it off manually or via another automation.
For Aqara Wireless Switch, if it doesn’t hold the state, you might need an input helper. (Setup instructions can be found in FAQs - third Q&A)
Hi Scott, thanks for keeping an eye on this thread. I haven’t forgotten your suggestion as I have a 2 page word document of all my thoughts and notes on the code and the how to but there are some hurdles to get over.
Stay tuned. For now I have a Entity - Run ON Timer blueprint that will turn your by-pass off in a set time period.
Thanks for your support, it realy helps me a lot and is much appreciated.
Hi Andy, thanks for your suggestion. I sort of recall that when developing this option back in Version 1.6, I had a few hurdles and If I renumber correctly. I think they were;
- scene.create, believe it can’t survive a restart.
- scene.create, something to do with automation mode restart, and will it keep creating scenes of the new lights on every trigger once they have been turned ON thus never turning OFF.
- The complex nature of targets
There were a few more and I wish I did notes on the day but I didn’t
However I do like it and maybe I should revisit it again.
yeah i can imagine the complexity of it all.
Next time if you have something like this, it is best to PM me.
Not sure why you have chosen to use “persons” rather than “device tracker”. I have been looking at this and it is on my list but not with persons rather device tracker. I will have a look at it.
Hi - This Blueprint would be the perfect one for me to use (thank you so much) but I cannot get it to work. My lights can be controlled by home asssitant only through REST API calls to an external system. Specifically, I have a service in home assistant that does this (for example: “rest_command.light23on”).
Is there any way I can make this “service” show up as an action / light / entity, which can be controlled by this blueprint / automation?`
I was hoping that this might be possible thourgh a “helper” but was so far unable to figure it out.
Thank you for any hints.
To use Rest services in the template light you could use the Rest Command integration. Seems you already have this part.
After all these gymnastics goes well, you probably can use the template you created as a light and with this blueprint!
I would also spend some time to check online if anyone has made a custom component on HACs for your light, to reduce the number of loops.