🔥 Advanced Heating Control

Thanks for the quick fix.
I can confirm that it is now working as expected. I will continue to test one room and provide feedback if I find anything else. :slight_smile:

1 Like

I just updated the dev version again since there was a major bug that had prevented the calibration.

Which protocol???

Just have a look in the initial post of this thread. Everything is described there what to do if you encounter a problem.

Be sure your thermostats are working, trigger the automation and share the trace log of the run where your thermostats ran into an error.

i currently setup the dev version and i have two questions:

  • what should i select if my TRV supports heat and auto in Operation / HVAC Mode?
  • for Calibration Entity Key Word my TRV have two entities one for number.bad_thermostat_remote_temperature what is the room temperature and number.bad_thermostat_local_temperature_calibration what is the delta between the TRV and the room thermostat

The manual mode. For my thermostats it’s heat. For others heat is the boost mode and they have to run in auto mode.

Depends on the manufacturer. If it’s Popp, Hive, Danfoss go with the remote temperature. But in this case the temperature gets converted from e.g. 20.5° → 2050. That means the input number must comsume integers instead of floats multiplicated with 100.
Fore everything else chose the delta / offset.

The issue, is that if a keep my larger zone, the person entities are “away” of my larger zone when I am at home (that is inside the larger zone).
Persons at home (and in the larger zone): they appear as being in the home zone, but NOT in the larger zone. To summ up:

  1. Persons inside the larger zone (but not at home): they appear as being in the larger zone but not at home.
  2. Persons outside
  3. Persons outside the larger zone: they appear away of both zones.

I guess it works like that because Home Assistant when there are overlapping zones, prioritizes, at least in this case, home. It seems that the same person cannot be in more than one zone at the same time.

Yes, but what if you add the person entities in the person section and the proximity sensor. This should work.

Hi,

I’ve been trying to get this working with my Tuya floor heating, but haven’t had any luck.

For testing I’ve just configured it that when the motion sensor is triggered it should set the temperature to the desired temp, but that doesn’t seem to happen.

Here’s the trace: https://controlc.com/09fb5e70

I’ve created my own basic automation for testing:

alias: Test Heating Automation
description: ""
triggers:
  - type: motion
    device_id: 050c620f24bd6c7bf56f912498d40af7
    entity_id: 5b2058205aec2ae919554ff4119acf39
    domain: binary_sensor
    trigger: device
    for:
      hours: 0
      minutes: 0
      seconds: 10
conditions: []
actions:
  - action: climate.set_temperature
    metadata: {}
    data:
      temperature: 27
    target:
      area_id: bathroom
mode: single

And this works
(I’ve disabled it, so it doesn’t interfere with Advanced Heating Control)

I suspect that Advanced Heating Control isn’t setting the climate.set_temperature for some reason, but can’t figure out why.

Hi, have you also fixed this in the new version?

The persons are already included in the Persons section of the blueprint. In the Proximity integration I have included both zones (Home and Home larger zone), but in the proximity section of the blueprint, as I only can include one item of the proximity integration, I need to choose: if I include Home, the heater turns off after being away home and inside the Home larger zone); if I include Home larger zone, the heaters turns off when at home, so it is not working

sounds fine so i can as keyword : “local_temperature_calibration”?
Is there a way use the remote temp. entity? So the TRV get the temp. from the room thermostat?

Thanks a lot. I think I got it now.

@panhans can you tell my why here the temp is 21C? (it should be lower in my oppinion)

me was away, the eco is 18C the comfort 21C, away= -1C
https://controlc.com/9192034c

edit:
same here:

comfort is 21C, Inside and thermostat are also 21C, so why the temp is higher than the comfort temp
https://controlc.com/2c5e0af8

edit2:
i think this is something on the calibration, because the same temperture are in the kitchen too, and there is 21C

Edit3: can you check also the away feature, me was away before and the temp was still on the comfort temp 21C, normaly the away -1C should put the temp to 20C (5.0.rc1_2410310859)

I will have a look into this.

//EDIT: Did the automation trigger after one minute (the duration you set)? Maybe you chose a lower duration for testing purpose like in you example automation. Could you also share the history graph of your presence sensor when the automation should be triggered?

I think so. xD

Could you disable your automation and have a test with ne latest dev version? You can add it without damaging your “old” automation.

The person away trigger had a bug. The latest version should fix that problem.

1 Like

Is it possible that the external sensor calibration is broken with the latest dev version? Seems not to trigger for me anymore.
Also am I supposed to change the keyword to ‘external’ for the Aqara TRV? Or does it check all the keywords in addition to the custom one? The description is a bit unclear in that regard.

1 Like

Thanks for the reply and helping, I’ve changed the trigger trigger the LaundryRoomDoor sensor being open or closed for 10 seconds.

I can see in automations that the trigger fires, but the new temperature doesn’t get stet.

Here are the new logs https://controlc.com/1ae5cd4a

@Rapha0000
It only check the keyword in the text edit box. Just have a look into your device page of your thermostat, find out the calibration entity, check the entity_id and set the keyword that matches it. Be sure no other number entity of your thermostat has this keyword in its entity_id.

For me it’s calibration. local_temperature_calibration would also work for me.

Bildschirmfoto 2024-11-01 um 16.38.01

@NoBadDays739
Your window or door is open. That prevents any change:

“state_window”: true

Ah, I misunderstood that setting, I’ve removed the window settings and just trying to trigger it via the Motion sensor now.

Here’s the graph (I can see the automation getting triggered in the automation screen)

Here’s the new trace: https://controlc.com/7ec44ecb

I’ve noticed something strange about my climate control, the state stays in off, even when it’s on.
I’m not sure if that might be related to the problem, the temp doesn’t seem to be set when the automation is triggered.

Away Mode Bug is Not fixed