đŸ”„ Advanced Heating Control

Blueprints Exchange
, ,
1556

Just create a 2nd schedule for your daughter. And a binary template sensor.

{{ is_state('person.YOUR_DAUGHTER','home') }}

Add the 2nd schedule to your automation and the sensor entity as schedule selector.

1 Like
1557

Hi community,

first of all a big THANKS for this amazing Blueprint! I startet to move frome Homematic to Home Assistant in february and as the winter is comming i was searching for some help instead of automate everything for my heating on my own. And BAM: found this Blueprint :wink:

My question: I would like to establish two different schedulers for a scheduled heating (work or holiday) wich works fine with the scheduler-section and the scheduler-selector.
BUT: I would like to change the radiator to eco-temperature when leaving the house and switch on the alarmo-integration.

So i understood the Blueprint-config that i could additionally configure a boolean-helper in the “Presence Sensor / On/Off-Entity” - section. I would expect that setting this helper to “on” while the scheduler is also “on” would force the radiator to the “comfort”-temperature.
If the helper is “off” and the scheduler is “on” the radiator would use the eco-temperature.
If the scheduler would be “off” the radiator would use the eco-temperature regardles wihc state the “Presence Sensor / On/Off-Entity”-helper has got.

But what i recognize is, that if the scheduler is “on” my helper has no impact on the radiator-temperature. Only if the scheduler is “off” i can force it to the comfort-temperature by setting the helper to “on”.

What configuration should i choose to reach my idea? (btw.: I do not want to use the “person” entities due to WAF
 ;-))

Would be great to get a hint from anyone. Thanks!

1 Like
1558

Remove your scheduler from the schedule section and place it to the presence section as presence schedule.

1 Like
1559

I have set a schedule for workdays from 6 am to 10 pm. Heating is to take place during this time. There are also two people entered who use the switch-on and switch-off times.
However, I would now like the heating to be set to comfort temperature at 1 pm on workdays, even if no one is at home. What is the best way to achieve this? An additional automation and thus set the “Comfort temperature optional” parameter? Or is there a better solution? Thanks

1560

May you can simply force the eco temperature at 1pm to a higher value with help of the schedule adjustments. Don’t forget an entry to reset the eco in the evening.

1 Like
1561

"Hey there, it’s me again :smiley:

I’m having some trouble with my thermostats and/or the automation. I tried to activate the “physical temperature change” option, which, of course, didn’t work. When I set the desired temperature manually, it jumps back to the temperature set by Eco Static or Comfort Static. After digging around a bit, I found out that due to an unsolved HA bug, it only works if I create an input boolean, which I did, and it’s working as expected. That’s the good news. The bad news is that if the temperature is manually changed while eco mode is active, and then comfort mode kicks in, the temperature doesn’t reset, even “reset temperature” option is set, to the static eco temperature when comfort mode is deactivated. Instead, it goes back to the last manually changed temperature.

Hope that makes sense so far.

Here’s my question: Is it possible to prioritize the static eco and comfort temperatures, depending on what was active before or after the change, instead of using the last manually changed temperature? For example, let’s say eco static was active at 17°C, then I manually changed the temperature to 19°C. When comfort mode kicks in and then goes off, can the temperature fall back to 17°C instead of 19°C? Not sure if I’m explaining this clearly, but that’s what I’m after.
Here my configuration:

alias: Heizung Wohnzimmer
description: ''
use_blueprint:
  path: panhans/heating_control.yaml
  input:
    input_trvs:
      - climate.wohnhzimmer_int0000005
    input_hvac_mode: auto
    input_temperature_minimum_static: 17
    input_persons:
      - person.XXX
      - person.XXX
    input_presence_sensor: binary_sensor.presence_wz_denon
    input_scheduler_presence: schedule.wz_presence_schedule
    input_presence_reaction_on_time:
      hours: 0
      minutes: 0
      seconds: 0
    input_presence_reaction_off_time:
      hours: 0
      minutes: 0
      seconds: 0
    input_windows:
      - binary_sensor.wohnzimmerfenster
    input_windows_reaction_time_open:
      hours: 0
      minutes: 0
      seconds: 5
    input_window_open_temperature: 5
    input_mode_winter: input_boolean.wintermode
    input_mode_outside_temperature: sensor.aussentemperatur
    input_tweaks:
      - not_off_but_min
      - reset_temperature
      - physical_temperature_change
    input_calibration_delta: 0
    input_schedulers: []
    input_temperature_comfort_static: 19
    input_temperature_sensor: sensor.environment_sensor_temperature_sensor
    input_windows_reaction_time_close:
      hours: 0
      minutes: 0
      seconds: 10
    input_frost_protection_duration:
      hours: 0
      minutes: 0
      seconds: 0
      days: 1
    input_frost_protection_temp: 16
    input_custom_condition: []
    input_temperature_minimum: input_number.manuelle_temperatur
    input_temperature_comfort: input_number.wz_manuelle_temperatur_comfort

I’m using TRV’s from HomeaticIP if this information is necessary.
So any help, ideas or hint’s to solve it would be appriciated.
Thanks in advance

1562

I can’t confirm this. The comfort mode is totally independent of the temperature settings. I’ve testet physical change feature in my test and productive environment without any issue.
When I changed the temperature on the device the eco/comfort input number gets set to the new target temperature. Depending on the state of the heating at the moment of temperature change.

  • Comfort Mode → Temperature Change → Comfort Input Number gets changed
  • Eco Mode → Temperature Change → Eco Input Number gets changed

Comfort mode depends on the state of scheduler, person, proximity or presence. You can setup a sensor (described in the first post) for your automation. If comfort is on the sensor is also on. You also can share a trace log after the moment comfort kicks in order to figure out what cause comfort mode.

Resetting the temperature works for the comfort temperature but not for eco temperature. I will fix this.

1563

I guess there is a missleading. The same behavior is what I got also and it seems as expected.
I refering about , if the Comfort Mode changed back to the Eco Mode (e.g no presence detectet or schedule time is reached) the Temperature will not set back to the static Eco Mode temperature if someone before changed the temperature manually via the input number (or physically on the Thermostat itself). But as you said that the reset doesen’t work for the Eco Mode and you will fix it, is maybe the solution for my problem :wink:
Please notify me if you was able to fix it to give it a try :slight_smile:
Thank you in advance

1564

I’d renew the logic for temperature reset. But maybe the reason for you issues is a timing problem.

Lets say eco is enabled. You enter the room and change the temp. Eco temp will by synced. Then the presence sensor kicks in and comfort will set but to the temp of the comfort input number. But you’ve changed the eco before not the comfort temperature.

1565

To keep it simple, the goal is that the temperature goes back to the value which is set in the static comfort or static eco mode is set. The resaon is, if the eco mode is activated and before, for some reason the temperature was changed manually, that it doesn’t heat overnight with the last manually changed temperature in eco or comfort mode. So the static value is always set and ignore the manually set temperature if the mode change because of timing or presence. Not sure if it is clear wht i would like to say.

1566

I was asking for calendar integration just some days before 
 then I read your post:

Oh! I did miss the section “helpful snippets” totally.
Can I ask if there will be a “real” calendar integration for AHC in the near future or is the calendar based sensor the way to go?

1567

Hello everyone.

Big thanks for this amazing blueprint ! Started using it couple of days ago (I do have only Tado TRVs around the house).

What I am trying to figure out are the following:

  1. Can I still control my schedules throuhg the tado app if I do not input anything in the “scheduling” part of the automation? I do have specific schedules on the tado app and when I need to lower the tempratures in a specifc part of the house (3 rooms) I do it manually through tado but after a while manually a temperature is set (19 C) which is not part of any of my schedules. Is that the comfort temperature?

  2. Frost protection. I have set specific times for the windows/doors to be open so this can be enabled - which seems to work fine - but based on my timings for windows/doors to be closed so that the TRVs can resume again nothing seems to happen. As an example , I have set fot a door to be closed for 5 mins in order for the schedule to resume, now 11 minutes have passed and I can still see “frost protection” on.

  3. Yesterday I was away of my house for a couple of hours and have set the “away temp” in the Tado App - this seems to work for the TRVs not included in the Blueprint but for the other 3 controlled by the blueprint that Tado away mode does not seem to work. Is that normal?

Thanks in advance for your help on those. Seems like a lot of amazing work has been done and I am looking forward to use this in its full extent.

1568

I have also one additioanl question:

I don’t (can’t) use person integration. Instead i have some automation/logic that sets an input boolean to on if someone is home. Is there the possibility to have geofencing with a input boolean?
As a workaround I suppose I could use presence sensor. But this leaves the scheduler not working :grimacing:any idea on how to go about this?

1569

If you don’t provide anything (scheduler, presence sensor ect.) you can go with your internal schedule. Window open detection and calibration should work.

This shouldn’t happen if you don’t use any schedule logic in this blueprint. Do you use the latest version?

Frost protection only works if you define some people but then the AHC scheudle is enabled. Frost protection is mainly for thermostat that don’t support this. Tado has frost protection build in.

Maybe you share your automation configuration in yaml for better understanding what you’d configured.

Add you input_boolean as guest mode entity. Maybe I should put this into the person or scheduling section. Atm you can find this under modes.

Yes, this is the feature I want to implement next. :wink:

1 Like
1570

@panhans Thanks a lot for the fix, now it works like charme. :smiley:

1 Like
1571

Hi I have a suggestion to the activation part. In homeassistant there is a Season - Home Assistant integration. It’d make life easier to newcomers as it is easier to set it than custome input boolean.

1 Like
1572

Yes, the presence sensor activates comfort temperature. But yes, the evaluation of the reaction time in the logic is missing. Atm. it will only be evaluated in the trigger logic. I will fix this soon.

1573

Will it be possible in a future version to add optional a boolean as an presence detection, instead of only a Person. Then we can use other presence detection Solutions.

1574

You can: Modes → Guest Mode

You can also add any boolean entity as a presence sensor.

1 Like
1575

Oh, it’s possible now to add attributes to schedules like:

schedule:
  heating_schedule:
    name: "heating schedule"
    wednesday:
      - from: "17:00:00"
        to: "21:00:00"
        data:
          eco: 17
          comfort: 22

But atm. this only works if you define your schedules in yaml. The UI editor doesn’t support this feature atm. But this could be a little game changer and makes the heating adjustments obsolete. Will focus on this when it’s possible to add these attributes over the UI.