Python library for ConnectLife API
Used by devices from Hisense, Gorenje, ASKO & ATAG and ETNA Connect.
The goal of this library is to support a native Home Assistant integration for devices that uses the ConnectLife API.
The code is based on Connectlife API proxy / MQTT Home Assistant integration (MIT license).
Software is provided as is - use at your own risk. There is probably no way to harm your physical devices, but there is no guarantee that you don't experience other problems, for instance locking your ConnectLife account.
Licensed under GPLv3.
To test out the library (users in Russia/CIS may need to pass the --trir option):
pip install connectlife
python -m connectlife.dump --username <username> [--password '<password>'] [--trir]
Omit password to be prompted for it instead. Make sure to always use single quotes around passwords with special characters.
This will log in to the ConnectLife API using the provided username and password, and write a JSON
file with all returned fields for each appliance that is registered with the account. Pass
--format dd to instead write a mapping file YAML skeleton to be used with
connectlife-ha.
Note: the property set a device reports is not authoritative. A device may report properties it does not actually support (and may omit ones its feature code defines), so two units with the same device type/feature code can report different properties. Treat dumps as a starting point for a mapping, not ground truth — cross-check controls against the device or the ConnectLife app.
To instead dump each appliance's energy statistics (both the air_duct_energy and
energyConsumptionCurve endpoints), use --query energy:
python -m connectlife.dump --username <username> --query energy
To dump each appliance's per-device static data (the query_static_data endpoint, keyed by puid),
use --query static:
python -m connectlife.dump --username <username> --query static
Because it's keyed by the device's puid, the response can differ between two physical models that
report the same device type/feature code. The response echoes the puid, so the dump redacts the
puid, wifi_id and device_id — but the schema is gateway-defined and may contain other identifiers,
so review each file before sharing. (For the per-feature-code property list, use
--query property-list below.)
To fetch the property list for a specific device type and feature code (any code, not just ones on
your account), use --query property-list:
python -m connectlife.dump --username <username> \
--query property-list --device-type-code <type-code> --device-feature-code <feature-code>
OAuth (browser sign-in)
OAuthConnectLifeApi uses tokens from the browser sign-in on oauth.hijuconn.com, which also
supports Google, Apple, Facebook and Microsoft accounts and accepting updated terms. The caller
runs the authorization code flow and refreshes the tokens (in Home Assistant, the OAuth2 config
flow), and passes a callback returning a valid access token:
from connectlife.oauth import (
OAUTH2_AUTHORIZE_URL,
OAUTH2_CLIENT_ID,
OAUTH2_CLIENT_SECRET,
OAUTH2_TOKEN_URL,
OAuthConnectLifeApi,
generate_source_id,
)
api = OAuthConnectLifeApi(get_access_token, source_id=stored_source_id)
appliances = await api.get_appliances()
The client ID and secret are Hisense's client for Home Assistant. Requests go to Hisense's
third-party API (juapi-3rd.hijuconn.com), except energy statistics, which it doesn't have; those
go to the app gateway with the same token. If the API rejects the token twice,
LifeConnectAuthError is raised and the sign-in should be repeated. Persist the source_id.
The Home Assistant integration is currently in discovery phase. Please contribute your device dumps to help the development.
Test server
To use the test server to support developing the Home Assistant integration, clone this repo and see DEVELOPMENT.md:
1 maintainer
Metadata
1 maintainer
Release files for connectlife 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| connectlife-0.12.0.tar.gz | 175.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| connectlife-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 233.4 kB
Release files / connectlife-0.12.0.tar.gz
| Download URL | connectlife-0.12.0.tar.gz |
|---|---|
| Size | 175.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ce865b9aaf741a6f18e08817e4e8a946a82e1f5600c53c272fad934b026f4f1
|
|
BLAKE2b-256 checksum How to use checksums |
d1fb3f4041931e9d89589bb89f567a965380b9e93f2bafae74ae660b3332fc80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.8.23
|
Release files / connectlife-0.12.0-py3-none-any.whl
| Download URL | connectlife-0.12.0-py3-none-any.whl |
|---|---|
| Size | 58.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c30f7a7ba7dd84b52bdf100a05d0de02500b2d17c58c177b1288a0ea8dd0b658
|
|
BLAKE2b-256 checksum How to use checksums |
4ceb738199c5bb9a6975a5c1299521a1a71e3042c63bf5d51648bcae6c45c751
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.8.23
|
Security for connectlife 0.12.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
