Window open, climate off

Have you ever managed to get it working? I am asking because we had a simmilar case with Tado yesterday. We used the service climate.set_hvac_mode instead of climate.turn_on. Your thermostat shows the same hvac_modes: as mentioned in your post:

hvac_modes:
  - auto
  - heat
  - 'off'

You could also try this blueprint and tell us if it also works for you and your HM-CC-RT-DN Thermostats. Thanks in advance!

2 Likes

Thank you for the template for Tado, it works wonderfully!

What do I have to do if I want to switch off or switch on all rooms at once? One reason Heating period ended

If it should be automatic (outside temperature, date, etc.) with an automation. For manual activation, I recommend a script that deactivates all climat entities. In your case (Tado) via the service climate.set_hvac_mode

This blueprint only works if the clumat entity is not turned off.

1 Like

@ SmartLiving.Rocks

Thank you for your answer. It should be switched off manually
How do I do this with the script on/off?

One script for on. Second script for off.

1 Like

Hi @SmartLiving.Rocks I have adapted parts of your Blueprint to work with HomematicIP here: https://community.home-assistant.io/t/homematic-reduce-room-temperature-when-a-window-or-door-is-opened/341053

This uses a service call homematic.set_device_value to set the WINDOW_STATE parameter directly, so it emulates the operation of HomematicIP door/window sensor.

It’s been in use for several months now, and it works fine.

@ SmartLiving.Rocks

Ok, I don’t know how yet but I’ll find something.

Hello! Nice, I was assuming that the Homematic climate devices are different. I did not know that homematic has its own service calls. But I think there is still a difference in 1. Homematic and 2. HomematicIP, right? Do you know the differneces? I am asking if your blueprint can handle all Homematic users (so that I can inform them in my initial post and make a link to your post).

It is really fascinating to me that an easy function can have so much corner cases even in Home Assistant. At the same time it is a proof that a single “smarthome” company will never be capable of managing all the functions a smarthome end-user wants to use!

1 Like

Hi @SmartLiving.Rocks. I just installed this blueprint for my Tado-based home. After creating a few template binary sesnors for the rooms with more than one window, creating the automations was easy and I was done inside of ten minutes. After initial testing, I can see it works perfectly. Thank you for all of your hard work and continued effort in this.

If you were to consider a https://www.buymeacoffee.com/ or similar, I’d gladly contribute!

I’m afraid that all my Homematic devices are IP types, so I can’t say for definite that it won’t work. However, I think it’s quite likley that it will, as the non-IP TRVs and thermostats do have the same functionality to use window sensors to control them.
Totally agree with your comment, no one manufacturer can cover every use case, which is why I love Home Assistant. Being able to link the sensors from my alarm system to control the heating system is a perfect example of this.

Alright, thanks! So all HomematicIP users can visit your link in this post. Very cool! Thanks

1 Like

:relaxed: Wow thank you very much! That is really great to hear/ read! Actually it was not so much work and it is more scientific experiment. That is one of the functions the market promised at the beginning of the smart home journey. But it was actually really complicated (tried it with fibaro HomeCenter2) and other Z-Wave controllers. Even a company like tado that only concentrates on heating is not able to handle it. Interesting, isn’t it.

No, I do not have a buymeacoffee account. I assume that they keep a little percentage. You can use my PayPal account and send money using friends.

Thanks in advance and have a nice day!

1 Like

Tado do have their own open window detection, but I think it’s based on sudden temp/humidity changes. I did try using it, but it wasn’t very accurate. Using actual door/window sensors makes it fool proof.

I’ve had this automation running for a few days now and it’s brilliant. It’s probably going to drain the batteries in my TRVs a lot faster, but they are rechargable and the cost savings compared to the gas heating make it a no-brainer.

Your PayPal link didn’t work. Looking at the HTML, it looks like it’s just plain text in an anchor tag.

The build in window detection does not work at all - I have experienced it with Danfoss Thermostats and other brands as well. Regarding the batteries, I am also looking for alternatives. There is a device with EnOcean technology that does create its energy by transforming the heat. But I do not have any experience yet.

What window sensors are you using? I have updated the link.

1 Like

How could I add multiple sensor in the blueprint. For 1 zone I have 2 Windows = 2 window sensor. If one of both is open, shutoff the hvac.

We have discussed it here. You need to make a Binary Template Sensor. Example in the following post:

2 Likes

Thank you for this blueprint.
I do have one question though. i do not want to use the open state from my radiator valve, but from a aqara window sensor as this seems to be more accurate. I cannot select these in the blueprint. Any easy way to fix this?

I assume the device class of your sensor is not “window”. We have discussed it here:

1 Like

You are correct. I did change this and all is working fine now.
Thank you !

1 Like

@SmartLiving.Rocks

The HA description states that this should no longer be used. What would be the more modern variant?

template:
  - binary_sensor:
    sensors:
      window_group:
        friendly_name: Windows_Heating_Julia
        value_template: >-
          {{ is_state('binary_sensor.openclose_28', 'on')
             or is_state('binary_sensor.openclose_29', 'on')
            }}
        device_class: window 

Thought would be this, but this does not work so :roll_eyes: