ESPHome component for AUX based air conditioners. Direct wifi control of HVAC by ESPHome and Home Assistant. HVAC status and command feedback are available.
Other
177
stars
42
forks
source link
[v.0.2.16] new config parameter: show_action_type #118
Folks are often asking about non-obvious behavior of the component:
Why the mode is cool, but it shows fan (previously it showed cool)
Sometimes the component shows "drying" when the mode is "cool". It's confusing.
This behavior is the correct workflow. There is a difference between mode and current action. The current action is what AC is actually doing right now in this mode.
Some examples:
If the current mode is COOL, then the current action may be FAN, because when AC reaches the target temperature, it can't cool further and should mix air in the room until the ambient temperature becomes too high.
If the current mode is AUTO, the current action may be FAN, COOLING or HEATING, depending on the current conditions in the room.
The current version of the component (v.0.2.15 and below) doesn't use current mode in the current action calculations. The current action for these versions of the component is a result of the target temperature, room temperature, inbound AC temperature, etc. This calculation method is totally correct and based on physics (isobaric processes). But it confuses some users.
Thus, I'm thinking of implementing a new component's config parameter (show_action_type) with two options: "physical" and "reasonable".
The physical option gives us the old-fashioned result (based on isobaric processes).
The reasonable option will consider the current mode in the calculations and will exclude "strange" actions from the output (i.e. it will never give action DRYING for COOL mode).
Folks are often asking about non-obvious behavior of the component:
Sometimes the component shows "drying" when the mode is "cool". It's confusing.
This behavior is the correct workflow. There is a difference between mode and current action. The current action is what AC is actually doing right now in this mode.
Some examples:
The current version of the component (v.0.2.15 and below) doesn't use current mode in the current action calculations. The current action for these versions of the component is a result of the target temperature, room temperature, inbound AC temperature, etc. This calculation method is totally correct and based on physics (isobaric processes). But it confuses some users.
Thus, I'm thinking of implementing a new component's config parameter (show_action_type) with two options: "physical" and "reasonable". The physical option gives us the old-fashioned result (based on isobaric processes). The reasonable option will consider the current mode in the calculations and will exclude "strange" actions from the output (i.e. it will never give action DRYING for COOL mode).