[ Final edit 2018/09/17 - I can no longer update this post as it is > 2 months old ]
Component, or Custom Component?
Until this component is fully integrated into HA (an initial PR has been sent), you’ll very likely want to use the custom_component version; for the latest instructions on how to install/configure it, please go to:
zxdavb/evohome
Home Assistant Custom Component for Honeywell Evotouch - zxdavb/evohome
I will edit the README.md there when I recommend switching over to the HA component version.
Please also report any issues there.
NOTE: You should ignore any installation instructions, below - they may well be hopelessly out-of-date.
[ Edited 2018/09/04 with two options to install ]
I know it’s Summer, but I am hoping to get this accepted into HA before next cold season.
This is for EU only as is uses: https://github.com/watchforstock/evohome-client … and so supports only installations available from: https://international.mytotalconnectcomfort.com
It has many improvements over the existing ‘honeywell’ compnent, and it definitely worth a look:
- slightly limited (i.e. no high-precision temperatures) support for accounts with multiple locations (you can specify which location)
- exposes the controller, allowing access to your location’s operating modes (e.g. Eco/Away/Off modes)
- exposes the DHW controller, if any (can read temperature & state, and set operating mode)
- and more!
**configuration.yaml**
I recommend the following configuration (only `username`, `password` is required). The old honeywell component should be 'runnable' can run side-by-side with this (new) evohome component:
evohome:
username: !secret evohome_username
password: !secret evohome_password
All following config parameters are presented with their default values:
scan_interval: 300 # seconds, you can probably get away with 60
high_precision: true # 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
use_schedules: false # this is for the adventurous person
away_temp: 15.0 # if you have a non-default Away temp
off_temp: 5.0 # if you have a non-default Heating Off temp
A lot of debug data can be had by turning on logging, and trying `cat home-assistant.log | grep evohome`:
logger:
default: warn
logs:
homeassistant.components.evohome: debug
homeassistant.components.climate.evohome: debug
evohomeclient2: debug
If you find a bug that persists after updating to the latest version of the component, please report it via github, _after_ checking:
https://github.com/zxdavb/home-assistant
Thanks to @matthewcky2k and @jarrah (who since chickened-out) for allowing me to use their DHW!
**Exceeding api limits, Unavailable devices, and HTTP 503s**
The component one of many that polls a web site for the status of a IoT device in your home. This causes issues with propagation delay, and relative unreliability of the Internet.
With this in mind, this component gracefully handles the following two issues:
a) exceeding api call limits (will throw a warning and 'back off')
b) installation/component unavailable for whatever reason (e.g. HTTP 503s), for example:
`2018-09-01 09:00:50 DEBUG (MainThread) [homeassistant.components.evohome] available(3449703) = False, self._status = {'zoneId': '3449703', 'temperatureStatus': {'isAvailable': False}, 'activeFaults': [{'faultType': 'TempZoneSensorCommunicationLost', 'since': '2018-08-30T22:13:59'}, {'faultType': 'TempZoneActuatorCommunicationLost', 'since': '2018-08-30T22:44:00'}], 'setpointStatus': {'targetHeatTemperature': 15.0, 'setpointMode': 'FollowSchedule'}, 'name': 'Bathroom', 'setpoint': 15.0}, self._timers = {'statusUpdated': datetime.datetime(2018, 9, 1, 9, 0, 49, 425578)}`
… the one “in the open”.
