diff --git a/source/_components/climate.evohome.markdown b/source/_components/climate.evohome.markdown deleted file mode 100644 index 4656d3a1683..00000000000 --- a/source/_components/climate.evohome.markdown +++ /dev/null @@ -1,52 +0,0 @@ ---- -layout: page -title: "Honeywell evohome/TCC Climate devices" -description: "Instructions on how to utilize a Honeywell evohome/TCC system within Home Assistant." -date: 2018-09-25 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: honeywell.png -ha_category: Climate -ha_release: 0.80 -ha_iot_class: Cloud Polling ---- - -The `evohome` climate platform integrates your _non-US_ [Honeywell Total Connect Comfort (TCC)](https://international.mytotalconnectcomfort.com/Account/Login) system into Home Assistant. It has been tested with the Honeywell evohome multi-zone CH/DHW system, but other systems may also work. - -It is distinct from - but related to - the [`honeywell`](/components/climate.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: -```json -{ - '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: -{% raw %} -``` -value_template: "{{ state_attr('climate.main_room', 'status').setpointStatus.setpointMode }}" -``` -{% endraw %} - -

-Full configuration details can be found on the main [evohome component](/components/evohome/) page. -

diff --git a/source/_components/evohome.markdown b/source/_components/evohome.markdown index 7ac73150974..b8ea759a062 100644 --- a/source/_components/evohome.markdown +++ b/source/_components/evohome.markdown @@ -8,16 +8,24 @@ comments: false sharing: true footer: true logo: honeywell.png -ha_category: Hub +ha_category: + - Hub + - Climate ha_release: 0.80 ha_iot_class: Cloud Polling +redirect_from: + - /components/climate.evohome/ --- -The `evohome` component is the main component to set up and integrate all _non-US_ [Honeywell Total Connect Comfort (TCC)](https://international.mytotalconnectcomfort.com/Account/Login) CH/DHW systems, primarily the Honeywell evohome multi-zone CH/DHW system. It does not support the home security functionality of TCC. +The `evohome` component is the main component to set up and integrate all _non-US_ [Honeywell Total Connect Comfort (TCC)](https://international.mytotalconnectcomfort.com/Account/Login) 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](https://github.com/watchforstock/evohome-client) client library and so will let you control (only) EU/international systems. It _does not_ leverage the [somecomfort](https://github.com/kk7ds/somecomfort) client library as used by US-based systems; for those, you may find what you need at the [honeywell climate platform](/components/climate.honeywell/). -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](/components/climate.evohome/) page. +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](#climate) page. + +There is currently support for the following device types within Home Assistant: + +- [Climate](#climate) ## {% linkable_title Configuration %} @@ -53,3 +61,36 @@ scan_interval: 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. +## {% linkable_title Climate %} + +It is distinct from - but related to - the [`honeywell`](/components/climate.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: +```json +{ + '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: +{% raw %} +``` +value_template: "{{ state_attr('climate.main_room', 'status').setpointStatus.setpointMode }}" +``` +{% endraw %} \ No newline at end of file