Hi,
Iāve successfully used the āstates_power:ā notation for the hvac_action attribute, however I realized that in my setup, my Ecobee thermostat controls both my HVAC furnace and thermopump.
So, in addition to hvac_action, there are other attributes that can be toggled by the thermostat. For instance, if outside temp drops below -10C, the thermostat switches from the thermopump to the furnace (aux_heat).
Would it be as simple as:
- platform: powercalc
entity_id: climate.my_ecobee
fixed:
states_power:
hvac_action|heating: 1810
hvac_action|cool: 1970
hvac_action|idle: 0
hvac_action|fan: 792
aux_heat|on: 17760
If I write it like this, will there be a conflict because we can have a situation where hvac_action = heating and aux_heat = on? Will hvac_action take precedence over the other because itās higher in the list?
Also, since part of the system uses a thermopump, the values I chose are the ārating conditionsā, however, the power consumed in heating and cooling are affected by the outside temperature. Is it possible to nest a linear mode within a fixed mode? Or create 2 powercalc sensors with the same climate entity, one for the thermopump (heating, cooling), and one for the furnace (aux_heat)?
Here are the attributes of the Ecobee:
hvac_modes: heat_cool, heat, cool, off
min_temp: 7
max_temp: 35
target_temp_step: 0.5
fan_modes: auto, on
preset_modes: Away, Sleep, Home, Off work
current_temperature: 21.7
temperature: 19.8
target_temp_high: null
target_temp_low: null
current_humidity: 62
fan_mode: auto
hvac_action: fan
preset_mode: away
aux_heat: off
fan: on
climate_mode: Home
equipment_running:
fan_min_on_time: 5
friendly_name: My ecobee
supported_features: 91
Thanks!