MELCloud Home
andrew-blake/melcloudhome · vv2.6.1
MELCloudHome - Home Assistant Integration
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.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
climate | Thermostat | |
fan | Fan | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
water_heater | Water heater (as a thermostat) |
1 report below say how a device from this integration behaves in the Home app.
What people report
MELCloud Home supports Mitsubishi Electric air conditioners and Ecodan heat pumps via cloud, with a HomeKit guide for fan and climate.
- Works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Mitsubishi Electric Ecodan heat pump (FTC) | Works Cloud | Zone 1/2 heating, DHW, telemetry and energy supportedSaved copySupported devices: Status: Production-ready (tested on real hardware); Supported systems: Mitsubishi Electric Ecodan heat pumps with FTC controllers; Core features: Zone 1 & Zone 2 heating, DHW control, 3-way valve systems, telemetry sensors, energy monitoring*; Optional features: Cooling mode (capability-based), energy monitoring (capability-based). Excerpt saved from the README on 2026-10-23. | README | |
| Mitsubishi Electric MELCloud Home ATA/ATW units | Works Cloud | Works in Home HomeKit guide covers fan tile, climate and device triggers | Error code exposed on error_state binary sensorsSaved copySummary The UserContext API already returns an `ErrorCode` setting for both ATA and ATW units, but the integration never surfaced it: the ATW model parsed it without exposing it, and the ATA model dropped it entirely. This PR parses `ErrorCode` on ATA units and exposes it as an `error_code` attribute on the existing `error_state` binary sensors for both device types, so users can see *which* error occurred (and build notifications on it, e.g. "Heat pump error E4") without opening the MELCloud Home app. No additional API calls, the data is already present in every UserContext poll. ## Changes … Excerpt saved from GitHub on 2026-10-23. | PR #172 · 2026-07 |
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) | 698 (0.1%) |
|---|---|
| GitHub stars | 142 |
| Latest version | v2.6.1 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @andrew-blake |
| License | MIT |
Devices listed in its README
- Status: Production-ready (tested on real hardware)
- Supported systems: Mitsubishi Electric Ecodan heat pumps with FTC controllers
- Core features: Zone 1 & Zone 2 heating, DHW control, 3-way valve systems, telemetry sensors, energy monitoring*
- Optional features: Cooling mode (capability-based), energy monitoring (capability-based)
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.
Sources
- Documentation: https://github.com/andrew-blake/melcloudhome
- Source code: https://github.com/andrew-blake/melcloudhome
- Issues: https://github.com/andrew-blake/melcloudhome/issues
- HACS: https://hacs.xyz