I’ve noticed that “Additional Close Actions” occur as soon as the window sensor triggers, not after any set delay time. I’d like to see the close action occur at the end of the delay cycle. What are your thoughts? Should the action occur at the time the sensor changes or should it occur after the set time delay? Perhaps an option for either?
I see this being useful in cases such as blinds being set to automatically close once a window is closed. Without a delay, the person closing the window may be in way of the closing blinds.
Really helpful blueprint which saves a lot of time. Thank you for it.
I have a quite large living room with 4 windows and 2 radiators. For the window sensors I created a group, but the helper doesn’t support a climate group. I did it with the old syntax in the yaml configuration, but this wouldn’t be recognized by your blueprint.
Of course I can use 2 automations, one for each radiator, but is there maybe a more elegant solution for this?
Yes, grouping climate devices is not possible because of the different states a climate device has. It is a bit more complex as e.g. a binary sensor (open/close).
I have added a second thermostat that acts as a slave. So if it has Home Assistant different state than the master, it will be overwritten.
Here is a version with two thermostats:
Let me know if it is working for you! Furthermore, would also like to know what thermostats you are using (vendor and model). Thanks and have a nice day!
After suffering through trial & error with my own automations (to get “back to previous state” to work) I stumbled upon your blueprint & must say a huge thanks!
First off, thanks so much for this. I was able to get multiple window switches operating on multiple thermostats exactly as I needed with very little trouble, amazing.
Just one quick question, would it be hard to make it also work with the ‘generic_hygrostat’ integration? I’ve been looking at using that to control a dehumidifier and would like to shut that off if the windows are open too.
Hi and thank you for your time creating this amazing blueprint.
It works great for the most part. I recently set my system to Heat_Cool then tested the automation and for some reason it failed to set Heat_Cool so it set the system to Heat instead. I’ll attach the pertinent trace below.
I would also like to create a delay to resume system operation after a door/window has closed to help prevent ‘short cycling’ if possible.
Hi, can you make a screenshot of the trace? I have just tested it with my heat_cool climate.entity device, and it is working as expected. The information you shared is the not offcondition of the blueprint ( so it fires at any on state) and is correct.
Hey I love your Blueprint int realy is exactly what I was looking for. Is there any way to trigger more than one climat device? (I have multiple windows and two heaters in my livingroom and would love to have it in one automation)
I am realy confused right now. I tested the blueprint in the bedroom and it worked nicely (aquara window/door sensors with homematic Ip thermostats). So I thought lets go for the rest of the house (kitchen one more room and the livingroom with 2 heaters) so I did and for the livingroom I used the 2 Heater option. Everything setup exactly the same but for some ODD reason ALL the other rooms switch to BOOST mode when the windows are open instead of turning them off. (wich is basicly the opposit of what I want). Has someone got a clue why this is happening or what i did wrong? I need help i love this blueprint.
Ah ok i didnt now that. I am still wondering why it worked in the bedroom though since its exactly the same thermostat. Well now I need to finde a way to adapt this somehow. ty
Edit: It works but it does not turn it compleatly of like the other one and I have the problem now again that I have two heaters in the livingroom. Well thats life I guess
