You mean it shouldn’t look like this?
Fenster Sensor PC Raum Tür should be removed so your group Alle Fenster Offen /Durchlüften is the only one. Except you also want the TRVs to turn off if the Fenster Seneor PC Raum Tür is open and not just the group.
That’s the way it should be. If I only ventilate the room, only this heating should go off. But if I open at least 3 of my windows, all the heaters should be switched off.
That’s the problem. If this group is included, everyone goes down even though there is only one window
Ah now I understand. You should setup one automation per room. The blueprint is designed for rooms. Especially every room has its own windows, thermostats, presence sensors, persons who live in and a sensor for calibrating.
Just duplicate your automation and set it up for every specific room and select only the entities that are existent in this specific room.
Okay. The problem is that not every room has a window sensor. So I wanted to use the existing sensors when I ventilate to tell the heating system that I’m ventilating now and switch off all the heaters.
Yes I have a similar setup. I think you have to set your group in every automation and also the single windows for the corresponding room. So the TRVs turn off when all windows are open or just the windows in the corresponding room.
I tried to heat a room to comfort temperature
- during a schedule (08-12pm)
AND - when a binary sensor is ON
The binary sensor is controlled by Apple Home and turns ON when somebody is at home. I need to go with this solution, as not all residents want to have the home assistant app. So I can’t use the people feature.
I tried to archieve this with
a) schedule and set the binary sensor as guest in people tab.
=> It sets always the comfort temperature, when the binary sensor is ON (which is expected) but it also sets it when the binary sensor is OFF. (not expected); it seems that schedule overules the guest
b) schedule and Presence Sensor; no people specified. Same behaviour then a)
Is this use case covered?
Thanks for your feedback. Could you share a trace log - described in the init post - when the schedule is on and your input boolean is off?
If you try solution b you have to set the schedule as presence schedule.
Can I just confirm that if I’m using people and presence with scheduler, and have set
input_away_presence_ignor_people: true
(That’s not a typo by the way. Ignore is missing the ‘e’ on the end)
when nobody is home the target temp will drop to Eco and not min?
It’s not a problem as such, I just wondered, if this is the case, is there any way of turning the heating to min temp when there is nobody home?
I can always toggle the winter input_boolean to off when we go out if not.
Thanks.
solution b works when the presence schedule is set, thanks for the hint.
solution a works when a person entity is set (see test person in screenshot)
without setting a person, it don’t work.
Thanks I will check this. A trace log is always helpful for those issues.
@P6Dave
Never had this use case. Did you try to enable following tweaks?
Ah righto. I have “Min instead of Off” set, so if I also set “Off instead of Eco” will those two work together to set the heating to Min when nobody is home?
Except that won’t work either, because we’re out just now and temps are set to Away not Eco because my presense schedule is On 
.
Haha… that’s the question. It should: Off instead of Eco sets the global mode for all TRVs and Min instead of Off gets evaluated when generating temperatures individually for each TRV.
@tux1337
I could recreate the issue with the guest mode. It’s fixed in the lates version.
Good evening,
I have implemented the template throughout the entire house, and everything is running great, except for the window detection.
We have window handle sensors that can have three states: closed, tilted, and open. These window states are not being detected.
Additionally, I also have simple door contacts with the states: closed and open. These are being detected correctly.
Could this possibly be the issue?
1 Like
Ok, you’re the first here with those window sensors. Could you share a screenshot of the attributes of the state overview in your developer tools section?
Update the blueprint please and have another try.
To use the automation, shall I create a climate entity if I have a wire pilot module ?
German windows 
I updated the blueprint, and it works now. Thank you!
1 Like
“Lüften” is holly here 
1 Like
Hi there! First of all, I really like the blueprint. It’s feature-rich and keeps things simple at the same time.
However, I am running into some strange behaviour which I can’t resolve by myself. I’ve configured a thermostat through my Fritzbox. It worked as desired for some time, but yesterday, the thermostat started having peaks in the temperature it should heat up to. It sets the target temperature to 30° C every hour at 15 minutes past and keeps it for 1 minute. At 16 minutes past the target temperatue is reset to the temperate I was expecting. You can see this in the following graph:
I’m completely lost and can’t find out what triggers the temperature change, especially because it is set to a temperature which I am not using in my configuration at all. (As a new user, I can’t post more images at the moment, happy to share more infos)
Any help with resolving this would be highly appreciated.
Thanks for your feedback. Could you tell me the version you’re using and could you share your automation configuration in yaml, please?