Great blueprint, thanks a lot!
It seems like the blueprint/automation won’t turn off the HVAC for heating when the temperature is reached. Off If Above/Below Room Temperature is ticked, I don’t see anything in debug logs (I assume I can find those in Settings > System > Logs?). I’ve just installed the Uptime integration as I saw a warning about that.
Sensor of HVAC is an external sensor and it show 20.9 degrees while the HVAC keeps on running at 20 degrees
Any ideas?
Thanks for reporting. Just check out the latest version and try again. 
Thanks for the quick response.
I’ve re-imported the blueprint (version did not change btw) and edited current automation + saved. Assuming it’s now using the new blueprint.
I did not see any change in behaviour, maybe I should re-create the automation from the new blueprint?
Sry, I’ve forgot to increase version. Recreation isn’t needed. You can reload your automation by pressing C on your keyboard. Then you can type Automations → Reload Automations.
Done
HVAC sensor says 20.8 degrees. Automation keeps running while max temp should be 20 degrees (even after few minutes). Delay for thermostat is 2 sec. Box is ticked for Off when temp reached.
The logic compares your target temperature (comfort, eco, ect.) (not hvac) with the temperature of the external temperature sensor.
You can set the log level to warning, run the automation and share the trace log with me for some more analysis.
Yes, I said max temp. But I mean the comfort temp in the automation which is set to 20 degrees.
Oh, wait. You said hvac temperature. Atm the reference temperature is taken by an external temperature sensor not the temperature measured by the thermostat itself.
Usually the thermostats closes the valve automatically. That’s the point of a thermostat, right?
Oke, the HVAC has an external temp sensor as shown in the screenshot to avoid allot of cycling of the HVAC.
So would I need to set the temp sensor somewhere in the automation?
Yes, I think I have to sort some things in the configuration UI.
Just add your external sensor in the calibration section.
The sensor ID isn’t appearing in the list, though it behaves like a temperature sensor.
I have a Tado system for the gas central heating (CV), and I’d like to combine this with the HVAC. I might just use the Tado temperature sensor for both. The only challenge is that this sensor is within the line of sight of the HVAC, so it heats up faster. I can mitigate this by lowering the maximum temperature to compensate.
On a related note, combining the HVAC with the CV would be ideal for optimizing the floor heating. Would using the Tado temperature sensor make things easier in this case?
In the summer, I plan to use the HVAC’s external sensor with an additional automation based on your blueprint. Hopefully, by then, this sensor can be included in the calibration list. 
Yes, that’s the right way. If I open this selector for all sensors I will get a flood of support requests. xD
//EDIT: but you can navigate to line 627 in the blueprint or search for input_temperature_sensor (line 609) and delete following as a workaround. Don’t forget to reload your automations.
something for the sensor dev? active here as well on the forum
device_class:
- temperature
I will reach out to the HVAC sensor development team, as it seems we might be missing some classes, which could be limiting us in terms of available blueprints, automations, and selectors. There might be a valid reason for this, so I’ll confirm.
In the meantime, I’ll use the Tado temperature sensor. Do you have any thoughts on integrating a central heating system with HVAC? Using the same sensor for both systems seems more efficient. I’m currently considering whether to prioritize central heating to provide some warmth from the floor, then top up with HVAC, or vice versa. Any insights would be helpful.
More info here by another user: Smart heating: Floor heating and AC
Edit:
Putting in the Tado sensor (measuring 21.3 degrees now) as Calibration Temperature Sensor the HVAC turned off just fine
Depends on your configuration but triggers are:
But the entity values gets evaluated in template triggers and further more in the variable section. As a result the evaluation produces a set of changes. If there isn’t any change the automation gets blocked in condition section.
In the automations view the last triggered timestamp only gets updated if the action part of the automation gets executed. In reality the automation gets triggered more often but mostly there is nothing to change for your thermostats.
I was wondering. You added the option to select multiple TRV’s, but under calibration I can only select 1 temperature device. Would it not make sense to add also multiple temperature devices to control the different TRVs in the different rooms?
My only option now is to duplicate the blueprint, while i am actually very happy with the rest of it and did not have the need to do so.
Yes, this blueprint is designed for one room only. It’s to diffcult to add connections between thermostats, schedules, sensors ect. in a single automation/blueprint when every room has other conditions and requirements.
is it possible to solve this problem?
Logger: homeassistant.helpers.template
Quelle: helpers/template.py:2740
Erstmals aufgetreten: 09:41:00 (6 Vorkommnisse)
Zuletzt protokolliert: 09:57:00
Template variable warning: No first item, sequence was empty. when rendering '{% set selected_scheduler = none %} {% if input_schedulers | count == 0 %} {% set selected_scheduler = none %} {% elif input_schedulers | count == 1 or input_scheduler_selector == none %} {% set selected_scheduler = input_schedulers[0] %} {% elif input_schedulers | count > 1 %} {% set selected_scheduler = input_schedulers[0] %} {% set selector_value = states(input_scheduler_selector) %} {% if is_number(selector_value) %} {% set selector_value = iif(selector_value | int > (input_schedulers | count), input_schedulers | count, selector_value) %} {% set selector_value = iif(selector_value | int <= 0, 1, selector_value) %} {% set selected_scheduler = input_schedulers[(selector_value | int) - 1] %} {% elif selector_value in ['on','off'] %} {% set selected_scheduler = iif(selector_value == 'off', input_schedulers[0], input_schedulers[1]) %} {% else %} {% set selected_scheduler = input_schedulers | expand | selectattr('attributes.friendly_name', 'eq', selector_value) | map(attribute='entity_id') | first | default(none) %} {% if (selected_scheduler == none) %} {% set selected_scheduler = input_schedulers | expand | selectattr('attributes.friendly_name', 'search', '(?i)'+selector_value) | map(attribute='entity_id') | first %} {% endif %} {% endif %} {% endif %} {{ selected_scheduler }}'