Skip to content
Home Assistant TestFlight
Climate

ConnectLife

oyvindwe/connectlife-ha · vv0.53.2

HACSCloud polling

ConnectLife appliances from Hisense, Gorenje, ASKO and ATAG: air conditioners, heat pumps, dehumidifiers, washers, dryers, dishwashers, ovens, hobs, fridges

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
switchSwitch or outlet
climateThermostat
humidifierHumidifier or dehumidifier
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature, humidity, air quality…)
water_heaterWater heater (as a thermostat)
buttonButton (as a switch)
selectMode picker (as switches)

What people report

ConnectLife (Hisense/Gorenje/Asko) appliances work through the cloud with per-type mappings that the maintainer expands from user diagnostics; the API can only be polled about once a minute.

  • Works4
  • Partly works1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Asko W-DW50/60-22 dishwasher (015)Works CloudError flags exposed as problem sensors in 0.50.0
Saved copy
The `Error_f*` properties on 015 dishwashers read `1` when clear and `2` while the fault is active (verified in #665 by closing the water tap: only `Error_f12` went to 2). They showed as raw sensors stuck at `1`. - All 22 `Error_f*` flags become `problem` binary sensors (diagnostic). - The 14 with a known meaning are named and enabled by default: F10, F11, F12, F40, F41, F45, F52, F54, F56, F67 and F68 from the Asko 60 series manual (via #665), and F42 temperature sensor, F43 pressure sensor and F65 display board from the device's self-check list. - The other 8 (F44, F46, F61, F62, F69, F72, …

Excerpt saved from GitHub on 2026-10-23.

PR #713 · 2026-10
Hisense HD5026TLP dehumidifierWorks CloudMapping 007-499 added; Matter-bridged model
Saved copy
Adds a mapping for the Hisense HD5026TLP dehumidifier (`007-499`), a Matter-bridged model reported in #546. New properties hoisted into the default `007.yaml` mapping (ignored by variants that don't expose them): - `f_e_drive`, `f_e_eeprom`, fault flags (`binary_sensor`, `problem`) - `f_e_incom`, communication fault flag (`binary_sensor`, `problem`) - `f_matterOriginalProductId` / `VendorId` / `UniqueId`, Matter identifiers (diagnostic sensors) - `t_anion`, ioniser on/off (`switch`) `007-499.yaml` narrows the fan-speed and operating-mode option sets to what this model actually offers …

Excerpt saved from GitHub on 2026-10-23.

PR #568 · 2026-06
Induction hob 036 (hob-midi-gmi24-better)Works CloudDefault mapping for device type 036 added
Saved copy
Refs #667. Adds a default mapping for device type 036, from the diagnostics of a `036-hob-midi-gmi24-better` ("Mid induction with new UI") induction hob in #667. There was no 036 mapping, so all its properties were raw sensors. ## Changes - `036.yaml`: the hob uses the same property names as the 010 hobs, so the 81 properties both share are mapped the same way as in `010.yaml` (zone power levels, timers, pot detection, residual heat, device status, hood). The rest: - `SLn_Power_level` is unavailable when it reads 255, which the zones the hob doesn't have (SL5, SL6) report. - New sensors: …

Excerpt saved from GitHub on 2026-10-23.

PR #726 · 2026-10
WFSE1015-LVW001 washing machineWorks CloudWasher mapping expanded: program selects, start/pause/stop buttons
Saved copy
Device Information - Model: WFSE1015-LVW001 - Device Type Code: 27 - Device Feature Code: (unknown - need to check) - Device Nickname: (your device name in ConnectLife app) ## Issue Description I have a WFSE1015-LVW001 washing machine connected via ConnectLife integration. Currently, the device is recognized but all sensors show as "Hidden" with default values because there's no proper mapping file for this model. The current file `/data_dictionaries/027-washing-machine-wm22.yaml` only contains: [code] ## Similar Models I noticed that the WFSE1214-MVW002 model (also device type 27) was added …

Excerpt saved from GitHub on 2026-10-23.

Issue #351 · 2026-02
Hisense 009-104 air conditionersPartly works CloudCJK market model names fall back to generic device type name
Saved copy
… splitting out the model-name fallback as discussed there. ## Problem Some ConnectLife markets report the marketing model name in Chinese/Japanese. Our 009-104 air conditioners report: 104冷暖节能无功率 which ends up verbatim as the Home Assistant device model. ## What this does - Adds `_contains_cjk()` in `entity.py`: a true CJK test over the Unicode blocks that occur in Chinese/Japanese market names (radicals supplement, CJK symbols/punctuation, kana, unified ideographs + Ext. A, compatibility ideographs, fullwidth forms), instead of an `isascii()` check, which also rewrote legitimate non-ASCII …

Excerpt saved from GitHub on 2026-10-23.

PR #781 · 2026-10

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Cloud polling

Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.

Details

Installs (analytics)2,900 (0.41%)
GitHub stars306
Latest versionv0.53.2 (2026-10-23)
Set up in the UIYes
Maintainers@oyvindwe
LicenseGPL-3.0

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.