Thanks! The sensors device class has to be specified correctly otherwise the blueprint does not find matching entitys. Your workaround shows all sensors - what in a lot of cases can become overwhelming.
As @Blade1337 reccomended you can use a “Template Binary Sensor” in order to make a (window) sensor group. Here you can also define a “device_class” so that my blueprint will recognize it as a window sensor.
You can put as many sensors as you want - the following example consists of two sensors.
binary_sensor:
- platform: template
sensors:
window_group:
friendly_name: Window Sensor with several Sensors
value_template: >-
{{ is_state('binary_sensor.training_fenster_936', 'on')
or is_state('binary_sensor.training_philio_4_1_window_940', 'on')
}}
device_class: window
Unfortunately it is not yet possible to do it directly in the Blueprint.
Nice topic! I am looking for a blueprint using a temperature drop for detection of an open window. Then a window sensor is not needed. A rapid measured temperature drop of the thermostat or valve (Adam Plugwise) could be used to switch off the heating for 15-20 minutes.
Who can write such a blueprint? Thanks, Dirk.
Hi,
please define “A rapid measured temperature drop” in time and delta temperature. Please take in consideration that there are different environmental conditions during summer, winter as well as spring and autumn that will have an effect on the delta temperature.
Furthermore, I would like to know what happens after the 15-20 min countdown if the blueprint has been triggered and the window/door is still open?
This is great! It would be great if we could define the time it should be open before the heating is killed. For example, if I open my window for just a second, it shouldn’t kill the heating.
Fritz Dect open window detection is a nice source for inspiration: open window based on temperature drop. Fritz!dect open window
There are also suggestions of settings.
Sorry, I am not convinced, and I highly doubt the efficiency as well as the stability of the automation. The failure rate is way too high (see also diverse AVM User/Experience groups/forums). Sorry, I am not the right guy for your requirement. Maybe you can develop a blueprint with these guys: Use rapid temperature delta to trigger automation? Thanks!
Notifications, alerts and other information is a complete different chapter in the Book of Home Automation! I see the need as I have TTS saying over my media player entity during daytime: “I have switched off the heater. The temperature is yx and the humidity is zx.” You have to set an input boolean helper to set notification ON/OFF as well as input sliders to define a time range. Then you use it also for other things like the “Garage/Entrance/ door is still open!”, “Person xy at the Entrance”, “Unknown car detected at the driveway!” etc. The notification is also able to select a device to send the Notification to (Media Player, Smartphone, TV, Telegram, E-Mail, LeMetric) based on different conditions (time, location, TV-on, sleepmode-on etc.)
For this basic automation it is too much.
Hello,
I grab your Creation and implemented a Condition. the condition is that if the Climate unit is actually turned off, this automation will not start the climate.
In this particular case for MELCLOUD systems. This is important because each climate unit has its own state names. if you want to find out about yours just go to DEveloper Tools and write the name of the entity. this will show you the state atributes.
blueprint:
name: Window open, climate off after a defined time4
description: An automation that turns off your climate device for exmple a heater
or an air conditioning if a window sensor is open for a specific time. It waits
until the window is closed again in order to turn the climate entity on again.
domain: automation
input:
window_entity:
name: Window Sensor
description: The window sensor that controls the climate entity.
selector:
entity:
domain: binary_sensor
device_class: door
minimum_open_time:
name: Miniumum time the window is open
description: Time in seconds to wait until the automation is triggered
default: 12
selector:
number:
min: 0.0
max: 120.0
unit_of_measurement: seconds
step: 1.0
mode: slider
climate_target:
name: Climate Device
description: The climate entity that is controlled by the window sensor.
selector:
entity:
domain: climate
condition_target:
name: Climate Device
description: I Unit has a State by melcloud operate.
selector:
entity:
domain: climate
source_url: https://community.home-assistant.io/t/window-open-climate-off/257293
trigger:
- platform: state
entity_id: !input 'window_entity'
to: 'on'
for: !input 'minimum_open_time'
condition:
- condition: state
entity_id: !input 'condition_target'
state:
- 'heat'
- 'dry'
- 'cool'
- 'fan_only'
- 'heat_cool'
action:
- service: climate.turn_off
entity_id: !input 'climate_target'
- wait_for_trigger:
- platform: state
entity_id: !input 'window_entity'
to: 'off'
continue_on_timeout: false
- service: climate.turn_on
entity_id: !input 'climate_target'
Hi, I do not get your point at the moment. Is it some “Melcloud” specific behavior, and it is working for you now?
Do I have to choose the same climate (device) in your modified version of the blueprint?
Why are you not using the “!input climate_target” as it is literally the same climate device as condition-target?
What is meant by “I unit” - what is the difference between the normal “state” of a climate device versus the state of a “melcloud” climate entity?
Why have you changed the device class to door instead of window?
Ahh, yes, about the device Class. For me to find the Z-wave Window and Door Sensor I had to change that device Class. Or I would not find it. I could also leave it in blank and it would show me all entities. I can change it back to yours or to all entities if you wish. But i am sure you can do it as well, since you created this one.
About the MELCLOUD, this is only for the Condition Part. I am still new to this, so this was the best way I could find for my CONDITION to work. As explained before, your Automation for me didnt work, because here in Portugal we dont need Climate always on, because we have times of the year that the temperature is just right, so if if the AC unit was off at the moment that I would open the Window , once I would close the window, it would start the climate, and we dont want that.
So for me to be able to use your automation and only triger if the actual climate unit was ON, I had to create a condition that would say, only trigger if you see these states
state:
‘heat’
‘dry’
‘cool’
‘fan_only’
‘heat_cool’
These are all the states that my Climate unit works with. I stated this because maybe your units have other diferent states.
So if the state of the Climate unit was OFF, then the automation would not start.
For this contition to work, yes you must use the same unit. because thats the unit that you want to control or not.
the condition sees if the targeted unit is on or not.
Hi! Yes, now it makes perfectly sense! The automation/blueprint should only run if the climate device is running. I have added a condition that checks if the entity is not off (so any climate state is accepted)! Check “condition” documentation here. That feature should have been included right from the beginning. Thank you for giving me the hint for the real life corner case! I was travelling to Spain (Andalucia) for the last 7 years and a lot of people have this kind of climate device! Greetings to Portugal and the sea!!!
p.s.: If you change the device class of your door/window sensor to window it shows up in the blueprint
Good Day,
first of all thanks for all the work done so far, really appreciate it!!
I am trying to use this Blueprint with my Homematic Door/Window Sensor and it does not work. What information can I provide for debugging?
First notice I can not select the sensor from the list I have to enter it manual.
Thanks for the quick response.
I did take the blueprint with the binary sensor and for some reason it does not trigger. Any ideas what to check? I can see that the sensor is reacting.
