Not not atm. Sounds to me like a new feature request.
Must the thermostats valves stay open in order to keep the 6 rooms warm?
As @hindseb said. Leave everything blank and just provide an input_boolean for guest mode or presence sensor.
Let me check this. But you just want to go presence based in combination of a presence sensor and a presence scheduler that allows the time when presence should be detected, right?
You can find this in the tweak section. When enabled you are able to set the temperature on your thermostat or by a thermostat card. After a change all thermostats will be synced with this new target temperature. (doesn’t work with aggressive mode or generic calibration)
You want to block the complete action call with a custom condition?
yes, is my case is it only for climate (air conditioner), for example outside temp is lower than inside, so i dont want that the cliamte stops, when i have a custom action call i can stop the trigger to stop the climate, so i have 2 options a outside threshold next inside threshold or this custom action call to stop the trigger
Thanks! Yes that’s the idea. The rooms that have presence detectors should only heat if presence is detected at the scheduled times. I guess I could do away with the scheduler and stick to just presence detection if I have to, but would like to get the schedule working.
Hi panhans, thanks for your efford. I like the idear of your blueprint, but having a problem to integrate my Tado.
I want use HVAC=auto, so that my themostats follow the timetable from tado. It works when i create my own automation from scratch. But
when your blueprint-autmation is started, it gets instantly overwritten by the static eco temperature and is apparently in HVAC=heat mode. Except the static eco temperatur is set to the exact temperatur like in the tado timetable. In this case it keeps HVAC=auto.
Do you have any idear how to fix it ?
Hi panhans, could it be, that there is something wrong with the calibration!?
i have some external tuya sensor i wanted to use for the calibration.
But if i set them in the calibration and check the generic calibration, nothing happens.
In one room the temp at the tuya Sensor is about 20,1.
Temp at the TRV is 20,5.
Comfort Temp is set to 21,5.
So the Target Temp at the TRV should be 22,5 right?
But its still at 21,5!!
The other rooms are similar to that one, the target temp is everywhere the comfort temp!
if i check the “fully rounded value” the target temp goes to 22 but not to 22,5!
Any ideas?
Could you check this
the trv’s dont have to stay open, the radiators will give enough heat while warm. Also not all rooms are used, and want to heat only the rooms where people are (livingroom and office for example).
Wasn’t possible for now. Just update to the latest version. If you don’t provide scheduler, person or presence sensor. Your thermostat won’t get a change except for open window detection and party mode. Feel free to test and give some feedback.
Depends on your calibration delta. The difference between your sensor and the trvs temperature is only 0.4°. The default delta is 0.5°. Correction only comes in place if the difference is greater than 0.5°C. So the target temperature is correct. If you want to have it more granular decrease the delta but be sure your thermostat accept values lower steps than 0.5. Maybe your looking for aggressive mode when your thermostat reacts too sluggish.
Just provide the presence scheduler and the presence sensor and leave the scheuler section blank.
I’ve added a custom condition section. But keep in mind this also blocks party or window open detection except you evaluate the corresponding variables in your condition. (state_mode_party, state_window)
I have 11 automations all running this Blueprint. I’ve just recently noticed this error in the logs for one of them:
Logger: homeassistant.components.automation.upstairs_heating
Source: helpers/script.py:2026
integration: Automation (documentation, issues)
First occurred: 10:17:18 (1 occurrences)
Last logged: 10:17:18
Upstairs Heating: Choose at step 6: default: Repeat at step 9: If at step 5: Error rendering Upstairs Heating: Choose at step 6: default: Repeat at step 9: If at step 5 delay template: expected float for dictionary value @ data['hours']
The error only occurs in this one automation. Here’s the automation trace:
@panhans i know thats not the best way, the only other way is when you add a second temp threshold like the existing only for inside. what do you prefer? (i think this would be better and the other features are still working)
Some selectors changed time ago. Just go to your automations and check the Action Call Delay in the Tweak section. It’s a duration selector now. The default is 2 seconds but your custom value is 4. If you want to keep this simply set it to 4 seconds.
I have two thermostats (two floors). What’s the right way for me to have 2 schedules, two eco and comfort set points? I searched in comments for multi-zone setups but what I read didn’t make sense to me.
I’m new to blueprints. This is my first one. I think the idea is I’m supposed to create two automations from this blueprint and in that way I can use the same blueprint “twice”.
My AC supports ‘auto’ and ‘heat_cool’. With a single static eco temperature and static comfort temperature how does this blueprint handle auto and heat_cool?
The two workarounds I thought of are:
Have two automations for my AC and use heat for one and cool for the other and just only have them be mutually exclusive to enable.
Have one automation and keep adjusting it? I don’t like this option, but it’s an idea.
