**Overarching Objective: **
Two heat sources - mini split heat pumps and an oil furnace. Heat pumps are primary heat source unless an outside air temperature threshold is crossed then they shut down and the oil furnace becomes the primary heat source. While the heat pumps are primary the oil furnace set point is below the heat pump to establish the primary/secondary relationship. As I am working with Mini Splits, the automation also needs to control for cooling.
Temperatures are controlled thru a number of helpers:
Climate - Heating Temperature
Climate - Heating Setback Temperature
Climate - Cooling Interior Target
Objective:
I attempting to set up a thermometer setback during sleeping hours. In doing this I want to establish a single value to pass to the devices as the “Climate - Target Temperature”.
Steps to date
I have a working automation that effectively manages the heat pump mode and furnace interaction based on exterior temperature.
Challange of the moment
I have created “Climate - Target Temperature” as a helper and am attempting to set its value in an automation without success using input.set.value from templated value from one of the other helpers (Climate - Heating Temperature or Climate - Heating Setback Temperature for heating and Climate - Cooling Interior Target for cooling).
The automation below runs but does not update “Climate - Target Temperature”.
It’s completely unnecessary to convert your service calls to this format:
- service:
data_template:
entity_id:
value:
In fact, the data_template option was deprecated, many versions ago, in favor of data. Your automation was failing not because you used the new format:
- service:
target:
entity_id:
data:
value:
It was failing because you didn’t supplied the value option with correct information.
What corrects the problem is simply providing value with the state of the input_number (changing the service call to an outdated format isn’t part of the solution).