evohome: unknown/invalid zone type (ghost zones)

[antald]

The problem

I have added the evohome variables to my configuration.yaml and restarted but getting the below error. Though I can access my honeywell system via the web.

Can you fix this error?

Logger: homeassistant.components.evohome.climate
Source: components/evohome/climate.py:114
Integration: Honeywell Total Connect Comfort (Europe) (documentation, issues)
First occurred: 00:49:31 (1 occurrences)
Last logged: 00:49:31

Ignoring: Unknown (Unknown), id=xxxxxxxx, name=: unknown/invalid zone type, report as an issue if you feel this zone type should be supported

What version of Home Assistant Core has the issue?

2023.9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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)}}

[zxdavb]

Hello, thanks for submitting this issue - I am hoping I can help.

Please describe what your TCC kit is - is it evohome, or something else?

Please look at this wiki: https://github.com/zxdavb/evohome-async/wiki/Hass:-Evohome-Debug-Logs

... and post the DEBUG info here.

You may want to redact some of the information (e.g. your home address may be in there), or you can PM me the data.

[antald]

My setup; Evohome controller ATC928G3000 2 x HCE 80 zone controller HRA80 antenna T87RF round thermostat R8810A opentherm controller HR92 radiator controller

Found the logs;

{'zoneId': '7820586', 'modelType': 'Unknown', 'setpointCapabilities': {'maxHeatSetpoint': 30.0, 'minHeatSetpoint': 5.0, 'valueResolution': 0.5, 'canControlHeat': True, 'canControlCool': False, 'allowedSetpointModes': ['PermanentOverride', 'FollowSchedule', 'TemporaryOverride'], 'maxDuration': '1.00:00:00', 'timingResolution': '00:10:00'}, 'scheduleCapabilities': {'maxSwitchpointsPerDay': 6, 'minSwitchpointsPerDay': 1, 'timingResolution': '00:10:00', 'setpointValueResolution': 0.5}, 'name': '', 'zoneType': 'Unknown'}], 'allowedSystemModes': [{'systemMode': 'Auto', 'canBePermanent': True, 'canBeTemporary': False}, {'systemMode': 'AutoWithEco', 'canBePermanent': True, 'canBeTemporary': True, 'maxDuration': '1.00:00:00', 'timingResolution': '01:00:00', 'timingMode': 'Duration'}, {'systemMode': 'AutoWithReset', 'canBePermanent': True, 'canBeTemporary': False}, {'systemMode': 'Away', 'canBePermanent': True, 'canBeTemporary': True, 'maxDuration': '99.00:00:00', 'timingResolution': '1.00:00:00', 'timingMode': 'Period'}, {'systemMode': 'DayOff', 'canBePermanent': True, 'canBeTemporary': True, 'maxDuration': '99.00:00:00', 'timingResolution': '1.00:00:00', 'timingMode': 'Period'}, {'systemMode': 'HeatingOff', 'canBePermanent': True, 'canBeTemporary': False}, {'systemMode': 'Custom', 'canBePermanent': True, 'canBeTemporary': True, 'maxDuration': '99.00:00:00', 'timingResolution': '1.00:00:00', 'timingMode': 'Period'}]}]}]}

DEBUG (MainThread) [homeassistant.components.evohome] Temperatures = {'7820586': 128.0, '7866229': 20.54, '7833055': 21.65, '7833056': 21.35, '7833057': 21.73, '7785131': 22.02, '7786128': 21.55, '7834320': 21.7, '7866233': 21.81}

{'zoneId': '7820586', 'temperatureStatus': {'isAvailable': False}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 62.0, 'setpointMode': 'PermanentOverride'}, 'name': ''}], 'activeFaults': [], 'systemModeStatus': {'mode': 'Auto', 'isPermanent': True}}], 'activeFaults': []}]}

{'zoneId': '7820586', 'temperatureStatus': {'isAvailable': False}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 62.0, 'setpointMode': 'PermanentOverride'}, 'name': ''}], 'activeFaults': [], 'systemModeStatus': {'mode': 'Auto', 'isPermanent': True}}], 'activeFaults': []}]}

{'zoneId': '7820586', 'temperatureStatus': {'isAvailable': False}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 62.0, 'setpointMode': 'PermanentOverride'}, 'name': ''}], 'activeFaults': [], 'systemModeStatus': {'mode': 'Auto', 'isPermanent': True}}], 'activeFaults': []}]}

[antald]

My best guess this is the Opentherm module (controlling the heating with Opentherm protocol) which is connected to our boiler. In the Honeywell Home app it displays a device with 62 degrees which I can't configure and also isn't assigned to any location/zone. This must be the boiler water temperature.

[zxdavb]

My best guess this is

For clarity, this guess is wrong - it appears to be a ghost zone.

---

It appears you have removed chunks of JSON, except for the zone in question. I am sorry, that is not what I meant by redaction - I usually need all the JSON before I can help.

That is, from Config = { all the way to the corresponding }, and the same for Status.

I do not mind if you change some values (e.g. your address may be in the Config JSON, so just replace it with 'REDACTED').

In any case, I am thinking you have exactly 8 zone in evohome? The JSON has 9, including zone 7820586.

It might be the case that the first zone is a 'ghost zone'.

[zxdavb]

See issue https://github.com/home-assistant/core/issues/30945 for a solution.

Please do submit a comment if the proposed solution does not resolve your issue.

[zxdavb]

I am going to reopen this issue - I am re-factoring the integration, and I believe it should provide a more useful error message for this somewhat common scenario (ghost zones).

[zxdavb]

This is addressed in https://github.com/zxdavb/evohome-async/commit/1bb2572625aaf15b742efdac34fc824afbb227e4 and will be in version 0.40.16.