Python client to asynchronously access the Total Connect Comfort RESTful API.

It provides support for Resideo TCC-based systems, such as Evohome, Round Thermostat, VisionPro and others:

• it supports only EU/EMEA-based systems, please use (e.g.) somecomfort for US-based systems
• it provides Evohome support for Home Assistant and other automation platforms

NOTE: the TCC API used by the library does not currently support cooling.

This client requires the aiohttp library. If you prefer a non-async client, evohome-client uses requests instead.

If you download the git repo you can use a basic CLI for backup/restore of schedules (incl. DHW, if any), for example:

python client.py -u username@gmail.com -p password get-schedules --loc-idx 2 > schedules.json

... and to restore:

python client.py -u username@gmail.com -p password set-schedules --loc-idx 2 -f schedules.json

To avoid exceeding the vendor's API rate limit, it will restore the access token cache, unless you use the the --no-tokens switch.

NOTE: the client may save your access tokens to .evo-cache.tmp: this presents a small security concern.

websession = aiohttp.ClientSession()
token_manager = TokenManager(username, password, websession, cache_file=CACHE_FILE_PATH)
await token_manager.load_access_token()

evo = EvohomeClient(token_manager)
await evo.update()

...

await token_manager.save_access_token()
await websession.close()

It is loosely based upon https://github.com/watchforstock/evohome-client, but async-aware.

The difference between the evohome-async and evohome-client libraries are significant, but it should be relatively straightforward to port your code over to this async library should you wish.

For example, entity ID attrs are .id and no longer .dhwId, zoneId, etc.

Other differences include:

• namespace is different (simpler) and is snake_case and not camelCase
• exceptions are parochial (e.g. AuthenticationFailedError) rather than generic (TypeError)
• exposes a TokenManager class (for authentication) and uses an Auth class (for authorization)
• is fully typed, including TypedDicts and py.typed
• additional functionality (e.g. logs a warning for any active faults)
• better error messages when things do go wrong
• extended compatibility beyond pure evohome systems (e.g. VisionPro)
• more extensive testing via pytest
• uses best of class linting/typing via ruff/mypy
• can import schedule JSON by name as well as by zone/dhw id

TIP: the non-async documentation (from evohome-client) is available at http://evohome-client.readthedocs.org/en/latest/