#179414·core

Evohome: fails with an unrecognized `model_type`: 'Saratoga'

Author: webbtechaustCreated Aug 17, 2026Updated Sep 29, 2026
Labelsneeds-more-informationintegration: evohome

The problem

Since the 2026.8.0 update (evohome-async bumped to v2.0.1, #174335), the evohome integration hard-fails setup entirely if any temperature_control_systems[].model_type isn't in the library's accepted list. My controller reports model_type: 'Saratoga', which isn't recognized. Prior to 2026.8.0 this same controller worked fine — the older evohome-async was more permissive about unrecognized model types.

What version of Home Assistant Core has the issue?

core-2026.8.2

What was the last working version of Home Assistant Core?

core-2026.7.x (last known-good before the 2026.8.0 bump)

What type of installation are you running?

Home Assistant OS

Integration causing the issue

evohome

Link to integration documentation on our website

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

Diagnostics information

N/A — evohome is a YAML-configured integration (no config entry), so there's no diagnostics download available for it.

Example YAML snippet

yaml
evohome:
  username: !secret honeywell_username
  password: !secret honeywell_password

Anything in the logs that might be useful for us?

Setup failed for 'evohome': Integration failed to initialize.
Failed to fetch initial data: GET location/installationInfo?userId=REDACTED&includeTemperatureControlSystems=True: response failed validation: not a valid value for dictionary value @ data[0]['gateways'][0]['temperature_control_systems'][0]['model_type']

Additional information

Still reproducing identically on 2026.8.0, 2026.8.1, and 2026.8.2 — confirmed via live log check on each. Happy to enable debug logging and provide the raw upstream API payload if useful.