Honeywell thermostat shows heat setpoint when in 'auto' mode

[garyckoch]

Home Assistant release with the issue:
0.71.0

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):
Virtual Environment on Linux (Archlinux ARM)

Component/platform:
https://www.home-assistant.io/components/climate.honeywell/

Description of problem:
honeywell.py is hard coded to show the heat setpoint if mode is not 'cool'

    @property
    def target_temperature(self):
        """Return the temperature we try to reach."""
        if self._device.system_mode == 'cool':
            return self._device.setpoint_cool
return self._device.setpoint_heat

This results in odd setpoint output when in 'auto' instead of 'heat' or 'cool' mode. Given that target_temperature is a single setpoint, I don't know what would be the best way to determine which setpoint to return in 'auto' mode. Perhaps the one that is closest to the current temperature?

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

climate:
  - platform: honeywell
    username: <removed>
    password: <removed>
    scan_interval: 600
    region: us

Traceback (if applicable):

n/a

Additional information:

[tylerakraft]

It would be amazing if it would show the heat AND cool set points when the thermostat is set to auto mode. I live in a place where there are days when I get 35+ degree temp swings within hours and being able to leave the thermostat on auto and adjust both set points would be tremendous.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[cdkonecny]

This is still an issue in 0.81.2

The code remains as above with no provision for how to handle setpoints when the operation mode is in 'auto'. This causes a return of the heat setpoint if the stat is in any mode other than cool.

[garyckoch]

I was still seeing this issue until my Honeywell gateway died so I don’t consider it resolved.

[Varjo1]

This issue definitely still persists.

[asjmcguire]

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

[cdkonecny]

Yes, it still shows heating setpoint when in auto in 90.1

Haven't looked at updated somecomfort, but last version it was because it only checked if in cooling mode and then defaulted to heat if it wasn't. I don't have the chops to update that to deal with the complexity of auto

[stmrocket]

This issue still exists in the current version (0.91.4).

[zxdavb]

I have addressed this issue in #24257 (which will be part of the new climate schema), but really the config parameters need to be changed to F, not C.

During the migration refactor, so your issue may have been fixed too - if anyone is willing to give me access to their system (i.e. I will need access via TCC), I can confirm this.

[EDIT] - I have changed the following code, see below.

@property
def target_temperature(self) -> Optional[float]:
    """Return the temperature we try to reach."""
    if self.hvac_mode == HVAC_MODE_COOL:
        return self._device.setpoint_cool

    elif self.hvac_mode != HVAC_MODE_HEAT:
        return self._device.setpoint_heat

    elif self.hvac_mode != HVAC_MODE_AUTO:
        if self.hvac_action == CURRENT_HVAC_HEAT:
            return self._device.setpoint_heat

        elif self.hvac_action == CURRENT_HVAC_COOL:
            return self._device.setpoint_cool

    return None

[Adminiuga]

I'd assume in auto mode component should return target_temperature_low and target_temperature_high properties and target_temperature being None in this case? Similar toset_target_temperature service call?

[zxdavb]

I think you're right - but with the new climate-1.0 is it HVAC_MODE_AUTO, or HVAC_MODE_HEAT_COOL - i am sorry, i have written a few climate components, but never one of these...

...and with climate-1.0, you can's see a UI at the moment.

[Adminiuga]

I'm reading it as HVAC_MODE_HEAT_COOL per https://github.com/home-assistant/home-assistant/blob/f7c2997fd5a05cfa592ce8dbd8968eacc8824bd9/homeassistant/components/climate/const.py#L13

My interpretation of HVAC_MODE_AUTO is when climate is on auto pilot. There's no target temperature per se? since user cannot set it, does it imply that target_temperature property should be None

[zxdavb]

OK, I have refactored this bit, and replaced HVAC_MODE_AUTO with HVAC_MODE_HEAT_COOL.

It is now:
https://github.com/home-assistant/home-assistant/blob/9de11a8fd1b046dd01a3b4f12e8128a338e0f313/homeassistant/components/honeywell/climate.py#L286-L300

...and this:
https://github.com/home-assistant/home-assistant/blob/9de11a8fd1b046dd01a3b4f12e8128a338e0f313/homeassistant/components/honeywell/climate.py#L155-L160

[zxdavb]

This is an issue that existed before climate-1.0, and the integration has been extensively reworked since then. Thus, closing this issue.

Please open a new issue if this remains a problem