Skip to content

v1.15.0

Choose a tag to compare

@elRadix elRadix released this 30 Oct 13:15
· 183 commits to main since this release

🎉 Complete native support for Daikin Altherma R Hybrid

This release delivers the hybrid support first announced in v1.14.0. Owners of a Daikin Altherma R Hybrid (EVLQ) with an Intergas boiler now benefit from full integration understanding of both heat sources — the heat pump and the gas boiler — operating independently and in combination.

Additionally: the EBLA09DA3W1 datasheet, a critical alert-suppression fix, and database insert hardening against invalid sensor data.


📊 Featured dashboard — Daily Summary Tabbed

Overview
Overview
Quality
Quality

🔥 Hybrid support: how it works

A hybrid installation has two heat sources — the heat pump and the gas boiler — managed automatically by the Daikin control board. Without explicit handling, the integration would attribute boiler activity to the heat pump, corrupting COP calculations and generating spurious cycle alerts. This release resolves both issues.

Five new entities (available only on hybrid installations, unavailable otherwise):

  • binary_sensor.daikin_cycle_ml_boiler_operation_demand — boiler producing heat
  • binary_sensor.daikin_cycle_ml_boiler_dhw_demand — boiler producing DHW
  • sensor.daikin_cycle_ml_hybrid_mode — H/P only · Hybrid · Boiler only
  • sensor.daikin_cycle_ml_boiler_efficiency_cop — gas boiler efficiency
  • sensor.daikin_cycle_ml_boiler_contribution_today_pct — percentage of daily samples with boiler co-fire

COP reporting reflects pure heat pump operation. Boiler co-fire no longer contaminates the heat pump COP average. cop_today, heating-curve analysis, and hourly rollups use only pure HP samples. Boiler co-fire is tracked independently, so you can see how often the boiler assists.

Alert suppression prevents false positives. Short-cycle alerts (short_run, short_off, pendulum_*) are suppressed when the boiler is producing heat and the heat pump compressor is idle. dhw_pendulum is suppressed during boiler-DHW-only operation. Co-fire (both sources active) still triggers alerts — the heat pump is performing legitimate work.

Per-demand boiler contribution tracking. Each cycle records boiler_heat_samples and boiler_dhw_samples independently, and each COP sample records boiler_mode (heat / dhw / both / empty). This foundation enables future analysis of bivalent system efficiency.

Migrations v23 and v24 run automatically on the first coordinator tick after upgrade. Historical data is preserved in aggregate form; per-demand tracking begins from the upgrade moment.


🆕 New model

Daikin Altherma 3 M EBLA09DA3W1

  • 9.37 kW · 3-phase 3N~ 400V · R32 · 60 °C maximum LWT
  • Nominal COP: A-7/W35 = 2.81 · A2/W35 = 3.79 · A7/W35 = 4.91 · A7/W45 = 3.71
  • Full EN 14825 curves bundled (Average climate primary, Warmer climate Keymark reference)

Requested in #222. COP-vs-datasheet comparison works without any manual configuration.

Model counts: 54 technical + 1 commercial alias = 55 user-facing (was 54 in v1.14.0).


🐛 Bug fixes

  • Alert suppression was non-functional since v1.14.0 — the coordinator did not pass boiler state to the alert evaluator, so short-cycle suppression never triggered. Fixed at both call sites, with regression tests that lock the behavior. If you reported that short-cycle alerts continued to fire on your hybrid — this was the underlying defect.
  • Database schema drift — schema.sql and the runtime fallback contained divergent CREATE TABLE cop_samples statements. Both are now aligned, with a parser-based test that fails CI if they ever drift again.
  • Insert validation — LWT / R1T / R4T bounded to −30…100 °C, outdoor −45…55 °C, flow 0…150 L/min. NaN, Inf, and non-numeric values are stored as NULL. The −40.7 °C R5T sentinel is rejected. String "no" no longer coerces to 1.
  • hybrid_mode normalization — case-insensitive matching, whitespace stripped, common aliases (hp, h/p, boiler) accepted, unrecognized values resolve to unknown.
  • hybrid_hint None-safety — the setup warning now fires when boiler attributes are absent or present with a None value (as during the ESPAltherma startup window).
  • #217 — IDLE state forces RPS=0 / thermal=0 / COP=None rather than retaining stale values; ERG04/06/08 aliases added; heating curve requires 18+ samples before advising.

📚 Documentation

Complete documentation set updated for v1.15.0:


📦 Upgrade notes

  • Non-hybrid installations: no action required — boiler columns exist with DEFAULT 0, functionally no-ops.
  • Hybrid installations: no action required — migrations run automatically. If the hybrid_hint warning appears, enable ALTHERMA(HYBRID).h in ESPAltherma.
  • Breaking changes: none. No entity renames or reconfigurations.
  • Historical data: boiler_contribution_samples and boiler_active are preserved; new split columns backfill from the upgrade moment forward.
  • Downgrading: not supported — new columns remain but will not populate. Restore from pre-upgrade backup if needed.

⚠️ Known issues

  • EBLA09DA3W1 was briefly published in MODEL_COMPATIBILITY with EBLA08EV3 values due to a string-replace defect. Corrected before the tag was cut.
  • #218 remains open for field feedback from hybrid owners. Please comment there if your EVLQ behaves unexpectedly.
  • #221 tracks future analytics (gas meter integration, bivalent dashboards, co-fire pattern detection).

🙏 Acknowledgements

  • @raomin — ESPAltherma project, and the hybrid profile definitions that made EVLQ support possible
  • The hybrid testers from #217 and #218 who identified the alert-suppression defect
  • The EBLA09DA3W1 requester whose detailed specifications made the datasheet accurate
  • All users who filed issues and tested pre-release versions

Bug reports are welcome — please include your model, integration version, and a diagnostics dump.

Happy heat-pumping! 🔥❄️

Full changelog: CHANGELOG.md
Discussions: GitHub Discussions