🔥 Advanced Heating Control

Blueprints Exchange
, ,
1831

@panhans i get this error in v5. do you need a trace or you know the problem?

image

1832

Just a warning (see FAQ in the first post). Its for calibrating Tado thermostats and without the integration spook gives a warning. You can simply ignor this.

1833

ah okay, thats bad, so i have always many “bad” a spook message after a reboot :frowning:

1834

Could you update to the latest dev version and check if the warning still exists for you?

1 Like
1835

im still on 5.0.rc1_g, and it looks like the spook messages are away, dont know why the messages comes before always after a reboot, so i cant check your new version, but i update to it (but the changes in the code looks right :slight_smile: )

1836

Regarding the spook documentation spook won’t throw warnings about templates. So I’d just put the action into a template. A test with a simple automation worked for me.

1 Like
1838

Hi,
I tried to test the DEV version and re-entered the data from one room.
But it seems that the window/door detection doesn’t turn the TRVs to off after the reaction time.
As far as I can see the scene is created but the TRVs remains at the comfort temperature.
In case needed please find the trace: https://controlc.com/6bce5721

The other way round seems to work, as if I set the TRV manual to off and close the window, the created scene is applied and the TRV goes back to heat state.

As an additional note, the missing uptime integration mentioned in the trace log has since been added, but the behaviour remains the same.

1 Like
1839

Thanks for testing and reporting! Issue is fixed now. :slight_smile:

1 Like
1840

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
1841

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

1842

Which protocol???

1843

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.

1844

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
1845

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.

1846

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.

1847

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

1848

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.

1849

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

1850

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

1851

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?