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

HVAC mode error in logs #97605

Closed
goedh452 opened this issue Aug 2, 2023 · 4 comments
Closed

HVAC mode error in logs #97605

goedh452 opened this issue Aug 2, 2023 · 4 comments

Comments

@goedh452
Copy link

goedh452 commented Aug 2, 2023

The problem

The logs show this error many times: Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported. I opened this issue but it was closed since there was no activity.

I took a look at the code and discovered that the zones seem to be the problem. At this line the state of a zone is set to auto when the location is set to off. Auto is not a valid HVAC-mode for a zone when looked a the possible states (see screenshot).

Scherm­afbeelding 2023-08-02 om 12 08 01

What version of Home Assistant Core has the issue?

2023.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

evohome

Link to integration documentation on our website

https://www.home-assistant.io/integrations/evohome/

Diagnostics information

2023-08-02 11:58:19.639 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.643 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.643 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.644 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.645 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.912 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.914 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.915 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.916 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported
2023-08-02 11:58:19.916 ERROR (MainThread) [homeassistant.components.homekit.type_thermostats] Cannot map hvac target mode: auto to homekit as only {0: <HVACMode.OFF: 'off'>, 1: <HVACMode.HEAT: 'heat'>} modes are supported

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Aug 2, 2023

Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration (evohome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of evohome can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign evohome Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


evohome documentation
evohome source
(message by IssueLinks)

@polter05
Copy link

polter05 commented Oct 5, 2023

Me too for homekit thermostat (netatmo)

#101244

@issue-triage-workflows
Copy link

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 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Feb 9, 2024
@zxdavb
Copy link
Contributor

zxdavb commented May 26, 2024

I took a look at the code and discovered that the zones seem to be the problem. ... the state of a zone is set to auto when the location is set to off. Auto is not a valid HVAC-mode for a zone when looked a the possible states (see screenshot).

Some confusion here is that you are referring to both:

  • a HA Climate entity (set to HvacMode.AUTO), and
  • an evohome zone (which would be FollowSchedule)

Nonetheless, I agree it is a bug.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants