I am not sure how to implement it into the Blueprint because at the moment of creation the automation does not have a name.
For now it can be used e.g. as a template sensor and be used in a condition of an extra automation.
Feel free to share your automation code (pm) and maybe I get some extra inspiration out of it.
I definitely see that we need to implement that feature somehow!
Start a script
Another idea could be to start a script that handels all the stuff like delay and additional extra functionality if the window is closed. By using this method the automation is not occupied and can start directly if the window is opened again.
Hey guys, I’ve added this adapted blueprint for Tado thermostats and turns them off and on as expected as my windows open and close, but it also turns them on if they were previously off before the trigger. So basically opening the window and closing it in a room that wasn’t heated, starts the heating. Can you help me with perhaps adding a condition that skips thermostats that were set to off? Thanks much!
Actually, the Blueprint is designed to check if the thermostat is in any other state than off.
Maybe the tado setting need to be adjusted or tado has changed something. I do not know because I am not using tado. But maybe @WhimsySpoon can give you some advice how to set it up correctly. He uses this Bluprint for a long time (many thanks!)
I just tested this by setting a room/zone to “Off”, waited a few minutes, then opened a window. After a few minutes, I closed the window and the room/zone remained in the “Off” mode as expected.
I have the following set in my Tado integration configuration if it helps:
First of all, thank you for that. But for me, it’s not working perfectly because changes are recognized and also the waiting times but if the climate entity is set to off and I close the window again the temperature is set to the temperature of the room and not to what I have set it before.
I’m using Tado. So I had set the temperature to 21 degree for this Tado climate device and opened the window. The climate device was set to off. After I closed the door it was going back to heat but with a temperature of 16 degree which was the room temperature.
With auto mode you mean schedule? I have not set it always to this mode. More off and manual heating.
Off also works fine for me.
Ehm what?
I tested it right now again. My room temp is 20.1 degrees. I opened a window and the automation set it to off. After closing the window it was set to 19 degrees. I have no schedule that ever sets something to 19 degrees. Just off, 20.5 degrees and 22 degrees.
No, I have not deactivated it for all rooms. Just for the rooms where I have a sensor at my window. This means just the bathroom is still activated in the Tado app. Yeah, I got the Tado skill activated in Alexa.
Ehm frost protection settings? I don’t have something like this. I know that when it’s set to off it automatically activates when its less than 5 degree.
First, thanks for amazing blueprint. It works perfectly fine with window/door sensors as long as they are defined in HA as windows. I have some sensors declared as doors (ie balcony door). Is there a chance to extend blueprint to support entities marked as doors?
I’ve just stumbled upon this thread. Thanks for all the work you’ve done so far, @SmartLiving.Rocks.
I can see a lot of versions on the blueprint being posted here and I’m struggling to find which one is the “main” one which covers most use cases - I tried looking at the repo as well but it’s difficult to see that from first glance. Can you give any tips?
Something that would potentially simplify the implementation - have you considered using dynamic scenes? You can capture the state of the climate entity in a dynamic scene before turning it off and once the minimum_close_time expires, you can turn on the scene which will bring back the old state of the climate entity (including modes, temperature, fan speeds etc). This way you won’t have to create all those conditions for every (original) state of the climate entity
Yes, the blueprint initially had only a few lines of code and now it has 28 revisions since the introduction of blueprints to Home Assistant Due to the feedback and suggestions for improvements from the awesome users of this blueprint it grew over the time and fits to min. 96% of climate devices.
Actually the point with fan speed and heating/cooling mode is a good one. I have a fan coil thermostat that has a lot of features. Scenes - Home Assistant does not work because you need to hardcode a scene_id to the bp. Normally a user has several bp and the would all refere to the same scene_id and that would screw up the bp/ automation. Thanks for the idea!
Due to the feedback and suggestions for improvements from the awesome users of this blueprint it grew over the time and fits to min. 96% of climate devices.