Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v.0.2.16] new config parameter: show_action_type #118

Open
GrKoR opened this issue Jul 3, 2024 · 0 comments
Open

[v.0.2.16] new config parameter: show_action_type #118

GrKoR opened this issue Jul 3, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@GrKoR
Copy link
Owner

GrKoR commented Jul 3, 2024

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:

  1. 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.
  2. 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).

@GrKoR GrKoR added documentation Improvements or additions to documentation enhancement New feature or request labels Jul 3, 2024
@GrKoR GrKoR self-assigned this Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant