Window open, climate off

Blueprints Exchange
,
144

Hello, thanks for your feedback. Interesting use case. Let us see how many people would like to have a longer time period. I have asked in the past and there was only one vote:

Let us see how the demand is:

  • What time range do you need before the blueprint triggers?
  • 1 sec to 3 Minutes?
  • 5 sec to 12 Minutes?
  • 1 minute to 30 Minutes?
  • more
0 voters

Anyway, you can make your suggested modifications to your blueprint. It will not update automatically. So you can start using it right away :smiley:

145

That is the right way to do it!

As Groups just have been modified by the creators of Home Assistant, it is possible to create a grouped sensor for this blueprint right from the UI now. Here also the device class can be set.

:information_source: I have also been working on a version that can be used with more than on binary sensor and different device classes in order to make it even more comfortable for the users. But there are some limitations:

  1. The wait for trigger does not accept conditions. An and condition would be needed in order to set the previous set havc mode to its previous state.
  2. Another Syntax would need additional helper (that need to be created by the user manually) - that is too much for an easy Blueprint.

If there is anybody out there who can give me a hint how to improve my automation sintax feel free to contact me or share the code directly here!

Here is a modified version for your need as described above. This version can be used with any binary sensor and has minutes instead of seconds for the minimum open time trigger. You can just copy the url and import it directly into Home Assistant

146

@SmartLiving.Rocks , thank you for making these changes. Appreciate very much.

148

hey. great blueprint.
but could you please add roller shutters to this?
so if the roller shutters are down; open it for XX% and close, if the window is closed again?

thank you

149

Interesting use case. So you want the blueprint to turn of the climate device and open a blind? If the window is closed again turn the heating back to its previous state as well as the blinds?

I thing we would need an additional helper to save the blind position in order to make it work.

150

yes, exactly.
i didn’t thought about saving the state though.
Just open to a user given value (like 10%) and back off. Just for opening the blinds to let a little bit more air through. because most of the time, opening a window is about ventilation, right? :slight_smile:
i don’t know of a scenario where it’s needed to turn the blinds back to the state before.
even for a window-door with blinds, i guess it’s okay to turn it to 100% (e.g. for entering a terrace) without saving the state.
i guess even checking day/night times is not necessary, because even in day times, opening a window with closed blinds seems pointless.

so maybe like this:

window example:

  • blind-entity: XY (window)
    – approach target value below: XY (10%)
    – target value: XY (15%)
    – close back after window is closed: Y/N (Yes)

terrace door example:

  • blind-entity: XY (terrace-door)
    – approach target value below: XY (100%)
    – target value: XY (100%)
    – close back after window is closed: Y/N (No) (because it would lock you out)

thank you

151

:face_with_raised_eyebrow: I am seeing too much corner cases and a lot of additional helpers that would be required.

But there have also been some feature requests regarding notifications:

:partying_face: Now we finally can do what ever we want!

@snikay As you are mentioning also to control the blinds, suddenly the feature introduced by Loxone came to my mind. Bugs, especially mosquitos, cannot see if there is red light. With the updated version of the blueprint, you have the freedom to also control the lights.

Here is a version that has additional action features. You have to import it manually from GitHub because I do not know if it is 100% stable. Please feel free to give it a try and let me know how it is working.

1 Like
152

Thanks @SmartLiving.Rocks. I’ve installed the blueprint. Will report any problems.

1 Like
153

altough i like the feature of addional actions for all sorts of things, i still think blinds will be the most used one. also blinds are very special, because it needs to check whether the blinds are closed or not, which needs again choosing the “do-if” action and makes the usage of a blueprint a little obsolete^^ otherwise the blinds would close if already open.
same for closing-action (checking for after sunset to close).
maybe you can add blinds on top? :slight_smile:

1 Like
154

Thanks for the feedback. I totally agree that there is a need for a functionality like this. Actually, I have tried to get it working, so that the position is stored to a variable if the window is opened. So I added a part in the Blueprint.

variables:
  cover_previous_position: {{ states.cover.living_room_window.attributes.current_position }}

and in the action part:

  - service: cover.set_cover_position
    data_template:
      position: '{{ states(cover_previous_position) }}'

:warning: But it is not possible :warning:

The variable is set correctly but cannot be restored:

Error: Error rendering data template: AttributeError: 'NoneType' object has no attribute 'lower'

Workaround

As I already have tried to explain here - an additional input numbers helper is needed to store the current value of the blind_position Open your Home Assistant instance and show your helper entities.

Create Helper

I named mine input_number.test_2

Use additional actions of the Blueprint to control the cover

:warning: Make sure you have imported the right version from GitHub :warning:
You can directly import the Blueprint directly here:
Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

I have used in my Example cover.living_room_window

Additional Open Action

  1. In order to set the current position of the blind to the input number use a Call Service action:
service: input_number.set_value
target:
  entity_id: input_number.test_2
data_template:
  value: '{{ state_attr(''cover.living_room_window'', ''current_position'') | int  }}'
  1. Open the Blind

Additional Close Action

  1. Set the cover to the saved position of the input number value use a Call Service action:
service: cover.set_cover_position
data:
  position: '{{ states(''input_number.test_2'') | int  }}'
target:
  entity_id: cover.living_room_window

:partying_face: You are done!

At least for the moment. Additional features like the mentioned sunset, close back after window is closed: Y/N (Yes) and stuff like that are still not part of a KISS climate blueprint (POV)!

ezgif-4-960674f87d

Additional information

Bildschirmfoto 2022-08-12 um 10.48.19
Bildschirmfoto 2022-08-12 um 10.48.19666×1296 77.5 KB

Here is the blueprint in YAML

alias: '😎 Window based climate-entity control with cover control'
description: ''
use_blueprint:
  path: SmartLiving-Rocks/window open climate off with optional actions.yaml
  input:
    open_action:
      - service: input_number.set_value
        target:
          entity_id: input_number.test_2
        data_template:
          value: >-
            {{ state_attr('cover.living_room_window', 'current_position') | int 
            }}
      - service: cover.open_cover
        data: {}
        target:
          entity_id: cover.living_room_window
    window_entity: binary_sensor.door_window_sensor_x
    minimum_open_time: 1
    climate_target: climate.hvac
    close_action:
      - service: cover.set_cover_position
        data:
          position: '{{ states(''input_number.test_2'') | int  }}'
        target:
          entity_id: cover.living_room_window
155

thank you again.

i see storing the value of the blinds before opening the window is making things complex. but i don’t think it’s actually necessary. at least not for me. just check for like “is blind closed?” if yes, open to XY%. if already opened to some percent, for me, it could stay that way. because i want to open it to only 20% anyway.
so would that latest version only work with that helper? or does it also work without? like choosing between “stupid” and “smart” ? ^^

156

Is it possible to add a delay before the climate returns to the state from before the window sensor was activated?
I have 5 TRV’s and I prefer if they all turns off, when a window is opened, but then I would prefer if there could be a delay for like 5 minutes before the TRV’s returns to heating mode after all windows are closed.

157

there is a minimum open time, but i too thought about a minimum closing time - would be great especially if one’s closing the tilted window just for a second to open it completely.

158

Sure! Here you go:

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

You can have a look at the code on GitHub.

159

You haven’t made your self familiar with the “Choose” or the “If-then” options for the additional action part, have you? If yes, please share the code with us and tell us what is not working

Sure it is! And it is even more complex to build because a lot of people have Venetian blinds nowadays. That means also to save the tilt position and results in two helpers for each blind entity. Yes it is more complex, but it also should fit all situations and not only an individual one.

160

Wonderful addition! Thank you.

1 Like
161

Hi Amon

Really a great blueprint, it works off the shelf while sticking to the supported HAVC modes :slight_smile:
The only trouble I had: My AC was in hvac-mode “cool” which is not supported by your blueprint. Took me a while until I noticed. It would be great if you could include this mode as well :slight_smile:

Best regards
Tom

162

Actually, it is already included as you can see here:

Please have a closer look at the trace of your AC automation and share the result with us. Thanks!

163

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.

164

Thanks for your feedback and testing the automation. That is very helpful. I agree that the additional close action should be after the delay.

So I have changed the code accordingly - give it a try and tell us what you think!

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Maybe there are also use cases that require Additional Close Action (Optional)

  1. At the time of closing
  2. After the delay of Miniumum close time

Maybe someone can give us an example for each case - that would be helpful