I’m trying to create a scenario where either door or window in room 1 have to be closed and window in room 2 has to be closed for my Tado to be running.
I’ve set up one group for window and door of room 1 with “all entities” unchecked, which seems to work. I’ve then added a second group that includes the group for room 1 and the window for room 2 with “all entities” checked. But that one fails.
Is my second group resolving individual entites of my first group for its “all entities” check instead of just taking group 1’s status plus room 2 into consideration?
Actually, I do not understand under what condition the Blueprint should stop the heating process and on what condition it should start it again.
Anyway - I advise you to take a look on template sensor. You can define exactly under what circumstances the sensor shows open or closed.
After you have created the template sensor (with device class window) , you can use it in this blueprint.
Hello, I need a meaningful solution to the following problem with this Blueprint:
If the window is opened again within the set waiting time after closing, the heating will still be off, so the automation will always fail from now on, as the “OFF”-status is checked first.
How can this situation be saved? I would prefer not to reduce the waiting time to zero so that the room can acclimate a bit before the heating turns on.
Thank you for your help!
Sorry for the late reply!
This is exactly how I have currently solved it. However, I will integrate the whole thing directly into your script as follows: 1. Set a helper to “ON” for every heating status except “OFF”, and set it back to “OFF” after the waiting time has elapsed. 2. At the beginning of the automation, check if the helper is set to “ON”. If so, the automation was restarted before the waiting time expired (for example, because the window was opened again (heating is “OFF”, helper is still “ON”)). For simplicity’s sake, it then jumps directly to the “AUTO” section (so I save myself different helpers for each heating mode) and processes the automation normally.
I am still unsure whether I should do it this way or through a separate automation, as with this solution, I would have to laboriously adapt every new version of your script… Thank you very much for your help!!!
I’ve been trying to get it to work for a few hours now. Unfortunately the automation doesn’t trigger. I have an Aqara window sensor and Tado thermostats. Unfortunately the Aqara sensor does not trigger. When I test with the following helper it works:
Do you have any idea what I’m doing wrong or how I can get the blueprint to work?
I would be very happy about your help and wish you a nice evening.
EDIT: Sorry for my post. I found the problem. My sensors were not of the window type but of the opening type. I had selected the Tado window sensor the whole time (window open detection).
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?
