HA Custom Component for Honeywell evohome

This is a Home Assistant custom_component that supports Honeywell evohome multi-zone heating systems (EU-only).

It supports a single Honeywell evohome installation: one controller, multiple heating zones and (optionally) a DHW controller. It will not work with US-based systems (it is written to utilize the EU-based API only, see: https://github.com/watchforstock/evohome-client).

Other Versions of this Component

This is the custom_component version of HA's official evohome component (see: https://home-assistant.io/components/evohome). It includes much functionality that is not yet - or will never be - supported by HA. There are good reasons why you may choose to run this concurrently with the official version (see below for more detail).

You could even run it alongside HA's older honeywell component (see: https://home-assistant.io/components/climate.honeywell), although I believe there is little reason for doing so.

There is support for multiple locations/logins. Use can choose which location with location_idx:, and you can even have multiple concurrent locations/logins with the following work-around: zxdavb/ramses_rf#10

Installation instructions

You must be running HA v0.84.0 or later (it has an updated evohomeclient). Make the following changes to your existing installation of HA:

1. Download this git into the custom_components folder (which is under the folder containing configuration.yaml) by executing something like: git clone https://github.com/zxdavb/evohome.git custom_components
2. Edit configuration.yaml as below. I recommend 300 seconds, and high_precision: true (both are defaults). YMMV with heuristics/schedules.
3. If/when required, update the git by executing something like: git pull

You will need to do 1) & 2) only once if you use git. You will need to redo 3) as often as the git is updated.

Post-Installation checklist

TBD

Troubleshooting

Execute this command: cat home-assistant.log | grep WARNING | grep evohome, and you should expect to see the following warning, You are using a custom component for evohome_cc:

2018-11-06 16:30:33 WARNING (MainThread) [homeassistant.loader] You are using a custom component for evohome_cc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

If you don't see this, then something is wrong with your custom_components folder, or your configuration.yaml.

Regardless of that you can also try the following: cat home-assistant.log | grep evohome | grep ERROR, and/or cat home-assistant.log | grep evohome | grep WARN, and/or cat home-assistant.log | grep evohome | grep Found

Configuration file

The configuration.yaml is as below (NB: it is evohome_cc: rather than evohome:)

evohome_cc:
  username: !secret evohome_username
  password: !secret evohome_password

# These config parameters are presented with their default values...
# scan_interval: 300     # seconds, you might get away with 120
# high_precision: true   # temperature in tenths instead of halves
# location_idx: 0        # if you have more than 1 location, use this

# These config parameters are YMMV...
# use_heuristics: false  # this is for the highly adventurous person, YMMV
# use_schedules: false   # this is for the slightly adventurous person
# away_temp: 15.0        # °C, if you have a non-default Away temp
# off_temp: 5.0          # °C, if you have a non-default Heating Off temp

If required, you can add logging as below (make sure you don't end up with two logger: directives).

# These are for debug logging...
logger:
  logs:
    custom_components.evohome_cc: debug
    custom_components.climate.evohome_cc: debug
    custom_components.water_heater.evohome_cc: debug
#   evohomeclient2: warn

Notes about scan_interval and high_precision

The scan_interval parameter defaults to 300 secs, but could be as low as 120 secs. This should be OK as this component polls Honeywell servers with only 1 API call per scan interval, with a maximum 30 per hour (plus a few more once hourly for authentication/authorization).

However, Note that high_precision temps use 3 API calls per scan interval for a maximum of 90 per hour.

I understand that up to 250 polls per hour is considered OK, but YMMV (if anyone has any official info on this, I'd like to know).

List of future features

Replace AutoWithEco: mode that allows a delta of +/-0.5, +/-1.0, +/-1.5, etc.

Improve heuristics: detect TRV Off, and OpenWindow