Honeywell evohome/TCC systems

The evohome component is the main component to set up and integrate all non-US Honeywell Total Connect Comfort (TCC) CH/DHW systems, primarily the Honeywell evohome multi-zone CH/DHW system. It does not support the home security functionality of TCC.

It uses v2 of the evohome-client client library and so will let you control (only) EU/international systems. It does not leverage the somecomfort client library as used by US-based systems; for those, you may find what you need at the honeywell climate platform.

Currently, only Controllers and Heating zones are supported; support for DHW controllers will be added at a later time. More information is available on the evohome climate platform page.

There is currently support for the following device types within Home Assistant:


To use this component in your installation, add the following to your configuration.yaml file:

# Example configuration.yaml entry
  username: YOUR_USERNAME
  password: YOUR_PASSWORD

Configuration Variables


(string)(Required)The username (email address) that has access to Honeywell TCC web site.


(string)(Required)The password corresponding to the above username.


(int)(Optional)Used to select which location to use, if your login has access to more than one location. Multiple locations at one time are not supported.

Default value: 0


(int)(Optional)How often updates are retreived from Honeywell’s web servers. The minimum value is 180 seconds, rounded up to the nearest minute.

Default value: 300

This is an IoT cloud-polling device, and the recommended minimum scan_interval is 300 seconds. Testing has indicated that this is a safe interval that - by itself - shouldn’t cause you to be rate-limited by Honeywell.


It is distinct from - but related to - the honeywell climate platform, which also allows (limited) integration with Honeywell Connected thermostats; these two components may well be usable side-by-side, but YMMV.

The evohome evotouch Controller supports seven distict operating modes: Auto, AutoWithEco, Away, DayOff, HeatingOff, and Custom; AutoWithReset is a 7th, hidden, mode.

Currently, only the standard HA operating modes are supported; the evohome modes are mapped thus: ‘Eco’ (AutoWithEco), ‘Off’ (HeatingOff), and ‘Auto’ (all other evohome modes). ‘Away’ mode is supported separately, in the HA fashion.

The evohome Heating zones support only three operating modes: FollowSchedule, TemporaryOverride, and PermanentOverride. If the zone is in FollowSchedule mode, it inherits its operating_mode from the controller; the other modes are mapped to ‘Manual’ or ‘Off’.

A device’s actual operating mode can be tracked via its device_state_attributes, which includes a JSON data structure for current state called status. For example:

	'zoneId': '999999',
	'temperatureStatus': {
		'temperature': 21.5,
		'isAvailable': true
	'activeFaults': [],
	'setpointStatus': {
		'targetHeatTemperature': 17.5,
		'setpointMode': 'FollowSchedule'
	'name': 'Main Room'

This data can be accessed in automations, etc., via a value template:

value_template: "{{ state_attr('climate.main_room', 'status').setpointStatus.setpointMode }}"