Closed spattinson closed 4 years ago
This is correct behavior per HA design. I still can't believe they decided to name "Heat / Cool", this "mode" instead of "Auto", which is how many devices call this mode. I hadn't realized that your heat only, or cool only device goes to "Heat / Cool" mode when the device only supports one mode, this is just.... And of course is confusing lots of people for sure. If you want to learn more you'll have to search for this issue at HA issue tracker or forums. I'm closing this as you say it is just a display usability issue only.
I have another climate integration using vaillant component. That has heat/off/auto.see these two screenshots of vaillant component "idle" and "heating" home assistant does not know when esphome is heating or idle. In the second screenshot i set a manual setpoint, the climate has changed from auto to heat and the state has changed from idle to heating, heat, manual. I have a feeling that having high/low setpoints implies heat/cool capability in home assistant even if there is no cool_action. my vailant component has only one setpoint not high/low and handles hysteresis itself by modulating boiler. I get it that bang bang works like this. I will live with it though, wait for someone else who can define the issue more precisely. Thanks
I understand your frustration, I even feel it myself.
You'll find the tip of this iceberg here: https://github.com/home-assistant/architecture/issues/260
All you say is expected behavior: The Vaillant when in auto mode is not accepting a Target temperature (set point) while ESPHome accepts a Target temperature in Heat / Cool. Two point target temperature is unrelated. Climate action (heating, cooling) should be informed by ESPHome to HA, see https://github.com/esphome/esphome/pull/720, if not open an issue.
Remember this is open source software and not everyone is going to review your issue, you are supposed to investigate and contribute, there is lots of information about this in HA community. I'm reopening this issue so "someone else who can define the issue more precisely" sees this, but I encourage you to close it.
Thanks. my understanding is improved. I think I will set a schedule of temperatures rather than use away mode at night. By doing that I am able to emulate auto mode, and I can alter a setpoint with the full knowledge that it will return to 'auto' mode at the next scheduled change. Thanks I do appreciate all the hard work put into this project. Its awesome. I should improve my programming skills so that I can contribute too. Closing.
Operating environment/Installation (Hass.io/Docker/pip/etc.):
Home Assistant 0.100.3 esphome 1.14.2, hassbian
NOdeMCU esp8266 Affected component:
https://esphome.io/components/climate/bang_bang.html
Description of problem: I have no cool_action defined in my esphome config yet in the HA frontend I have options Heat, Off, Heat/Cool. I believe that I should have Auto instead of Heat/Cool.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
In .storage the configuration file that esphome generated contains:
I Believe the supported modes should be 0, 1 and 2 so that Auto appears in the front end instead of Heat/Cool. From the Logs esphome thinks it is in Auto mode.
Additional information and things you've tried:
Its working fine as Heat/Cool, its a display usability issue only.
One other thing I noticed is that the graph that is displayed in frontend is not coloured to show when heating is active like it was when I had it configured as a generic_thermostat in HA. The graph IS coloured when it is set to Heat though, I thought Heat = Automatic for a heater when presented with a choice of Off, Heat, and Heat/Cool.