🔥 Advanced Heating Control

As I can see Lilli passed the 8000m at 20:27. State towards was already set. So you have set a duration of 2 min. So comfort heating should be set at 20.29 and 20:34 she was at home. All in all comfort heating should started only 5 min before she arrived at home.

Regarding the graph you could set the distance to 15.000 m or also include the location in the radius. (20.000 m)

EDIT: If you setup an AHC sensor for you automation you could display the state of this sensor together with distance and direction in the history.

Did test again today, and it looks like there might be blocking on “person not home”, but thats a guess. i had a lift home today, and was able to track the states in HA, and it looks like that I must “home” for it to trigger

EDIT: If you setup an AHC sensor for you automation you could display the state of this sensor together with distance and direction in the history.

Not sure how to

Just tested a setup with proximity and person. Proximity works fine even if nobody is at home.

There is a description in the initial post if you want to setup a AHC sensor (Helpful snippets)

Will try the sensor… :slight_smile:

Here is my ahc setup for 1 room

alias: 🔥 AHC 1. Sal - Stuen
description: ""
use_blueprint:
  path: panhans/heating_control.yaml
  input:
    input_trvs:
      - climate.stue_mod_haven
      - climate.stue_mod_vejen
    input_proximity_distance: 8000
    input_proximity: 20e7c2fe1fb7244485543e0e8d3b9555
    input_mode_winter: input_boolean.varme_1_sal_auto_manuel
    input_schedulers:
      - schedule.ahc_1_sal_normal_tid
    input_persons:
      - person.michael_dahl
      - person.lilli
    input_people_leaving_home_duration:
      hours: 0
      minutes: 5
      seconds: 2
    input_windows:
      - binary_sensor.vindue_i_stuen_contact
      - binary_sensor.doren_ud_til_haven_contact
    input_windows_reaction_time_open:
      hours: 0
      minutes: 3
      seconds: 0
    input_windows_reaction_time_close:
      hours: 0
      minutes: 10
      seconds: 0
    input_window_open_temperature: 5
    input_mode_outside_temperature_threshold: 5
    input_temperature_sensor: sensor.netatmo_skovkrogen_3_livingroom_temperature
    input_calibration_timeout:
      hours: 0
      minutes: 30
      seconds: 0
    input_calibration_delta: 0.1
    input_presence_sensor: binary_sensor.all_motion
    input_scheduler_presence: schedule.ahc_tilstedevaerelses_tid
    input_presence_reaction_on_time:
      hours: 0
      minutes: 5
      seconds: 0
    input_presence_reaction_off_time:
      hours: 0
      minutes: 10
      seconds: 0
    input_temperature_minimum_static: 18
    input_temperature_comfort_static: 19
    input_temperature_minimum: input_number.varme_1_sal_eco
    input_temperature_comfort: input_number.varme_1_sal_normal
    input_proximity_duration:
      hours: 0
      minutes: 2
      seconds: 0
    input_log_level: warning

Do I understand correctly that I have to create the automation for each thermostat? I can’t build them all into one automation?

Yes you do

No, you can add as many thermostats in a automation as you want. But it makes only sense if all thermostats has the same heating schedule. If not just create one automation per room where you add only the thermostats that are physically in that specific room.

Hi, this doesn’t seem to be working or is my configuration wrong? At 1pm the Eco temperature is not raised.

Another small question, is there a big difference between generic calibration and offset calibration via the thermostat (if it can do that, in my case Sonoff)? Which should I use better?

Could you share your configuration in yaml? I also use that feature for my bathroom to set the eco temperature to another value.

If your Sonoff provides calibration just go with the native calibration. The generic calibration manipulates the target temperature so your thermostat never shows the correct target temperature except the calibration offset is 0°.

ok, that’s the background. Yes, the Sonoff can offset calibration.

Here is my config:

alias: AHC Wohnung OG
description: ""
use_blueprint:
  path: panhans/heating_control.yaml
  input:
    input_trvs:
      - climate.sonoff_thermo_esszimmer
      - climate.sonoff_thermo_wohnzimmer
    input_temperature_minimum_static: 21
    input_schedulers:
      - schedule.wohnung_og_zeitplan
    input_away_options:
      - scheduler
    input_persons:
      - person.frank
      - person.tanja
    input_windows:
      - binary_sensor.alle_fenster_og
    input_temperature_sensor: sensor.raumthermostat_og_temperatur
    input_away_offset: 1
    input_time_based_temperature_change_valve_target:
      - time: "13:00"
        days:
          - Mon
          - Tue
          - Wed
          - Thu
          - Fri
        eco: "22"
      - time: "14:30"
        days:
          - Mon
          - Tue
          - Wed
          - Thu
          - Fri
        eco: "21"
    input_calibration_options:
      - generic_calibration

Then I would have to create these over 12 times?

How did you know that the eco set doesn’t work for you? Did you check the history of your external temperature sensor? The target temperature of your thermostat was manipulated because of the generic calibration.

If you have 12 room, 12 thermostats, 12 different requirements, then yes. If not you can group them and you’re good to go with only one automation per group.

If each room has its own thermometer, don’t I have to do the same?

Yes, just setup one automation for one room, clone it and edit the temperature sensor.

What about the Static Comfort Temperature? Does this have to be changed in the automation or does it take this from the thermostat card?

The absence detection function only works if a heating schedule has been set. Does this mean that it does not turn down when nobody is at home?

Edit:
I have just tested it. The Static Comfort Temperature is always taken over. Regardless of whether I have set something else in the card.

I always get a notification when the target temperature changes and it doesn’t do that at 1 pm when nobody is at home. When I get home at 2:15 p.m., I immediately get a notification that the target temperature has been raised to Comfort 22 degrees

Just wondering, can this be a blocker for the proximity


do I need that at 0 ?

Hi,

it looked like it was working for all rooms, but since one of the latest versions, it looks like something is broken.

E.g. when I run the automation for the kitchen, the temperature is put to 5 degrees while it should go to the ECO temp (16 degrees), the same in another time window when it should be set to Comfort (19 degrees).

Checked with other rooms, disabled the Legacy Restore, Window detection, etc. All doesn’t make a difference.

I wanted to add a trace to this, but only can find the option to upload pictures…

Any ideas?

In the forst post is described how to share a trace log. Did you configure frost protection?

No frost protection configured. Uploaded a trace for the sleeping room, which should be set to 16 degrees when running, but stays on 5 degrees:

https://controlc.com/01e18716

Hope you know the issue :-).

Thanks in advance!