🔥 Advanced Heating Control

[stephanschleichstr13]

Im not 100% sure with the “Calibration Entity Key Word” feature.
What is the right “Calibration Entity”? my thermostat or my external sensor?
the external sensor is already the “Room Temperature Sensor” so i need to add again this one?

Edit: aah the “Room Temperature Sensor” is for “Enable Room Temperature Threshold”

[hainfelder]

as far as I understand it:
Calibration Entity is the entity of the thermostat, where calibration can be changed.

AHC looks for an entitiy that includes the keyword.
(Seems to be a clever workaround to adapt to many different thermostats)

In one case the calibration entity was named “externer” (external in german) … by setting the “Calibration Entity Key Word” we can tell AHC what to look for.

(this was the logic before already - only now we can change the keyword in the UI.)

[stephanschleichstr13]

alright thanks.

[tco95ttocs (Mario)]

so normaly there is no need to change the given keyword?

[panhans]

Yes, not needed. There are some users who localize the IDs. Thats why the default entity_ids doesn’t match the algorithm anymore. In this case the key word must be changed to make calibration work again.

[say1897]

@panhans

The uptime integration provides a sensor with the timestamp of the last start of home assistant.
Home Assistant updates every entity with every restart so the last_changed attribute is at least the ha start timestamp.
Without knowing the actual ha uptime timestamp the automation waits after every restart until the durations ran out.
Let’s say you set the duration for presence activation to 5 min. Before restarting ha the presence detection is already on. After a restart the automation waits again for 5 min until the target temp will be set to comfort temp. With the uptime sensor the automation checks wether home assistant just started at kicks in heating without waiting the additional minutes.

There is no need to setup this integration. It’s just a recommendation.

Thank you for your detailed response. With this explanation, I can work well. It seems like this is generally a very useful thing! THANK YOU!

[Ohana_Means_family]

@panhans

Könnten Sie das Trace-Protokoll hochladen und teilen, in dem Sie die Warnung/den Fehler erhalten?

Which protocol? Where is it?

[miguelpineiroo]

Great blueprint!! Congrats. I have set it up last week and I am very happy. I am using the proximity integration to track my Home zone. The only issue I am having is when I go out from home for a short period of time, let’s say 1 h, and the heater turns off. I prefer to maintain it on. To try to fix it, I have created another zone that is centered in my home but with a larger radius, let’s call it “home wide” zone. The idea is that if I am both at “home” or at “home wide” zones, the heater is on. If I set in the blueprint proximity filed the “wide zone”, it is not working when I am at home, as I am detected at home, but not at home wide. Maybe it is an issue with two overlapping zones, that selects the smaller. To make it work, it would require that the proximity section of the blueprint allows to track two zones, not only home. Is it possible to do that, or do you see an alternative? Thanks in advance.

[panhans]

If you only go with proximity you can keep your larger zone and add person entities.

[tco95ttocs (Mario)]

hi guys, i have a quaestion about the sheduling. At the moment i have several schedules, for example “normal” and “holiday”. At the moment i have to change them with the schedule selector. Would it be possible to integrate the workday integration to this blueprint, so that it will automaticaly switch between “normal” and “holiday” or weekend?

[panhans]

If I am right the workday sensor is just a binary sensor, correct? On holiday it is off and on a regular workday on.

Add your schedules in the correct order:

1. Holiday Schedule
2. Workday Schedule

Then just set your workday sensor as your scheduler selector.

[tco95ttocs (Mario)]

yep its a binary sensor…ohh…thats a good idea, i will try that

[stephanschleichstr13]

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

[panhans]

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.

[stephanschleichstr13]

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

[panhans]

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

[stephanschleichstr13]

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 )

[panhans]

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.

[kauthmbt (Thalion)]

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.

[panhans]

Thanks for testing and reporting! Issue is fixed now.