Repository navigation
v1.13.0 — 53 models, HT support, datasheet COP curves
Daikin Cycle ML v1.13.0 — 53 models, HT support, real datasheet COP
Released: 2026-10-27 · Technical changelog
This is the biggest release we have ever shipped.
If you own a Daikin Altherma — low-temperature monobloc, split, high-temperature, heating-only or with DHW — this update almost certainly covers your model. And it finally uses your system's real datasheet values to judge your system's performance.
What's new at a glance
- 40 → 53 models — full Daikin Altherma catalogue with datasheet COP curves
- HT units are first-class — EKHBRD and ERRQ get their own behavioural profile
- Smarter COP alerts — measured against your model's datasheet curve, not a generic number
- Historical data recovered — one-time rebuild of missing thermal data from stored samples
- ESPAltherma in sync — adopts upstream ERRQ-ERSQ definition (40th def file)
- Easier model switching — change your model from the UI without uninstall/reinstall
🎉 All 53 supported models
Every model ships with its own COP curve built from official Daikin service-manual data — not interpolated, not guessed.
Low-temperature models
| Family | Type | Sizes | Max LWT |
|---|---|---|---|
| EPRA / ERLA | Monoblock LT | 04, 06, 08, 10, 11, 12, 14, 16 kW | 60 °C |
| ERGA | Split LT | 04, 06, 08 kW | 60 °C |
| EPGA | Split LT | 11, 14, 16 kW | 60 °C |
| EBLA | Monoblock LT | 04, 06, 08 kW | 60 °C |
| EDLA | Monoblock LT | 04, 06, 08, 11, 14, 16 kW | 60 °C |
| EDLQ | Monoblock LT | 04, 06, 08, 11, 14, 16 kW | 60 °C |
| EPSK | Monoblock LT | 04, 06, 08 kW | 60 °C |
| EBLQ (CV3) | Monoblock LT | 05, 07, 11, 14, 16 kW | 60 °C |
High-temperature models (NEW in v1.13.0)
| Family | Type | Sizes | Max LWT |
|---|---|---|---|
| EKHBRD + ERRQ | HT split | 011, 014, 016 | 80 °C |
| ERRQ + ERSQ | HT outdoor | 011, 014, 016 | 80 °C |
Datasheet curve coverage per model: 6 full 6–9 point curves (EPRA11/14/16, EPRA08/10/12), 12 two-point curves (A7/W35 + A7/W55), 6 HT three-point curves (A7/W35 + A7/W65 + A7/W80), 3 nominal-COP-only (EPRA14/16/18). Remaining smaller variants fall back to nominal COP — override any model with your own datasheet via the upload_datasheet service.
Full model matrix: docs/MODEL_COMPATIBILITY.md
🔥 High-temperature Altherma is finally first-class
Before this release, HT owners were tolerated. Now they are supported. HT systems get their own behavioural profile:
- 45-minute defrost interval (was 30) — matches HT hardware behaviour
- 300-minute cycle tolerance (was 240) — HT runs are legitimately long
- 10 K dT threshold (was 5) — HT systems produce bigger deltas
- 30-minute minimum run threshold (was 20)
- 3-point COP curves (W35 / W65 / W80) — real HT operating points
- 80 °C max LWT in the datasheet validator (was 70 — blocked HT)
Cycle detection no longer cuts HT runs short just because they look "too long" by low-temperature standards.
⚡ In sync with ESPAltherma
We track ESPAltherma's upstream attribute definitions. This release adopts their latest model definition (ERRQ-ERSQ outdoor unit, the 40th def file) so your Altherma keeps reading correctly after their updates. If your ESPAltherma version keeps working, we keep working.
📊 Alerts that know your system
- Low-COP alerts now compare your live COP against your model's datasheet curve, not a generic number.
- Bogus values are filtered. Values above 11.0 COP or 14.0 kW thermal are treated as measurement artifacts, not truth. No more "why does my heat pump claim 15 kW of heat when it's a 6 kW unit?"
- Sample count is preserved in diagnostics even when the value is gated, so you can always see what happened.
🗄️ Your historical data, recovered
Older cycles recorded with missing or zero thermal output are recomputed on first boot from the raw sensor samples you already have stored. This is a one-time, safe, idempotent migration:
- Runs on first startup after the update
- Uses only data already on your disk — nothing leaves your HA instance
- Sub-second on typical databases, up to ~30 seconds on very large ones
- Skips cleanly if already run (no risk of double-processing)
- Never overwrites existing valid values, only fills gaps
🔧 How to change your model
Originally picked a model during setup and now want to switch? Say you added a second outdoor unit, or you picked the wrong variant? Just change it from the UI — no uninstall, no data loss.
- Settings → Devices & Services → Daikin Cycle ML
- Click the gear icon (Configure) on the integration card
- Choose:
- "Source sensor and model only (quick)" — change the model, keep everything else
- "Full reconfigure" — review all settings step by step
- Pick your model from the 53-option list
- Confirm — the integration reloads itself automatically
Model is config-entry data, not an option. That's why you won't find it under "Configure → Options" — it lives under the "Configure" button on the integration card, per Home Assistant 2026+ guidelines.
Full guide: docs/MODEL_COMPATIBILITY.md § "Changing your model"
⬆️ How to upgrade
Via HACS (recommended)
- Open HACS in your sidebar
- Click Daikin Cycle ML
- Click the three dots → Redownload
- Select v1.13.0
- Restart Home Assistant
Verify the upgrade
- Settings → Devices & Services → Daikin Cycle ML should show v1.13.0
- Your entity list should be unchanged (no entities added or removed in this release)
- Check Settings → System → Logs for "Setup failed for custom integration" — should be none
- On first boot, you may see a brief log line about "v19 thermal_kw_avg rebuild" — that's the historical data recovery, expected and safe
The v19 data migration runs once, on the first boot after upgrade. It cannot touch files outside your HA instance.
⚠️ Known limitations (shipping anyway)
- HT COP-vs-datasheet % still uses W35 as reference, not nearest LWT point. If you run HT at W65 or W80, you may see a low-COP alert that is a false positive against the W35 curve. Fixed in v1.14.0 — we chose to ship 90% correct over waiting for 100%.
- v19 heating-cycle recompute is conservative. Heating cycles miss the return-water temperature sensor needed for a fully accurate thermal estimate, so some values come out NULL (safe) or biased low (from startup samples only). NULL is strictly better than wrong. Tracked as #184 for v1.14.0.
- Historical cycle duration can differ from (end − start) by 2–30 seconds. Cosmetic, no functional impact. Tracked as #183 for v1.14.0.
- Model not in the list? We support 53 models — if yours isn't there, your ESPAltherma attribute definition probably isn't upstream yet. See "Found a bug?" below.
🔗 Links
- Integration repo: https://github.com/elRadix/daikin_cycle_ml
- Full technical changelog: CHANGELOG.md
- Model compatibility matrix: docs/MODEL_COMPATIBILITY.md
- Database schema: docs/DATABASE.md
- Latest release: https://github.com/elRadix/daikin_cycle_ml/releases/latest
- Issues tracker: https://github.com/elRadix/daikin_cycle_ml/issues
🐛 Found a bug? Missing model?
If your model isn't in the list, or a value looks wrong, please file an issue with:
- Your model (e.g. EKHBRD016 + ERRQ016)
- Your ESPAltherma attribute definition (dump it if you can)
- A description of what looks wrong (screenshot from Diagnostics is ideal)
The reconfigure path means we can turn around new models in days, not releases.
💚 Thank you
The 40 → 53 expansion was shaped by community reports — ERGA08EAV3H owners, EBLA and EDLA owners, and HT users who told us their cycles were being cut. Every model request you filed, every "my COP is wrong" report, every attribute dump you sent: it added up to this.
If your model still isn't in the list, file an issue. We're listening.