jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-21 16:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update evohome.markdown (#7487)

Browse Source 
* Update evohome.markdown

Added info about Zones now being supported. Also a little tidy-up.

* 🔥 Removed optional parameter from initial example

* ✏️ Tweaks
This commit is contained in:
zxdavb 2018-11-15 21:16:30 +00:00 committed by Franck Nijhof
parent 29861c483b
commit 94d4440fc9
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
source/_components/evohome.markdown
View File

@ -13,14 +13,11 @@ ha_release: 0.80
ha_iot_class: "Cloud Polling"
---
The `evohome` platform is the main component to set up and integrate all supported evohome devices.
The `evohome` platform is the main component to set up and integrate all supported evohome Climate devices.
It uses the [evohomeclient](https://pypi.org/project/evohomeclient/) client library and so will let you control (only) _EU-based_ [Honeywell Connect Comfort](https://international.mytotalconnectcomfort.com/Account/Login) systems.
Currently, only Controllers are supported; support for Heating zones and DHW controllers will be added at a later time.
It is related to the [honeywell](/components/climate.honeywell/) climate component, which allows limited integration with evohome Heating zones. These two components should be usuable side-by-side, but YMMV.
Currently, only Controllers and Zones are supported; support for DHW controllers will be added at a later time. More information is available [evohome climate component](/components/climate.honeywell/) page.
## {% linkable_title Configuration %}
@ -31,9 +28,9 @@ To use this component in your installation, add the following to your `configura
evohome:
username: YOUR_USERNAME
password: YOUR_PASSWORD
location_idx: 0
```
This is a IoT cloud-polling device, and the `scan_interval` is currently fixed at 3 minutes. Testing has indicated that this is a safe interval that - by itself - shouldn't cause you to be rate-limited by Honeywell.
This is an IoT cloud-polling device, and the `scan_interval` is currently fixed at 5 minutes. Testing has indicated that this is a safe interval that - by itself - shouldn't cause you to be rate-limited by Honeywell.
{% configuration %}
username: