Skip to content

Mixergy v2.1.0

Choose a tag to compare

@CaputoDavide93 CaputoDavide93 released this 12 Aug 12:48
· 4 commits to main since this release
f205adc

Six user-visible fixes, five of them found by an adversarial review of the codebase.

Fixed

  • Holiday mode hid heating that was really happening. Frost protection, the anti-legionella cycle and the pre-return reheat all reported as not-heating while away, so the power sensor read zero and the energy and cost totals stopped for the whole holiday.
  • Service calls without a target no longer report success while doing nothing. boost_charge and friends succeeded silently whenever no tank was loaded.
  • A Mixergy server error no longer looks like a wrong password. Any non-success response from the login endpoint was reported as an authentication failure, which stopped polling and raised a re-authenticate prompt during outages nothing could be done about.
  • A missing default heat source no longer prevents the integration loading. On a first start it meant setup never completed.
  • Tank readings are parsed correctly in both response formats. One of the two shapes the cloud returns was silently discarded, leaving target charge, heat source, heating status and holiday mode all reporting defaults.
  • Authentication could get permanently stuck after a malformed token lifetime, reusing a dead token until Home Assistant restarted.
  • German, French and Italian were each missing 29 strings, so parts of setup, reconfigure, options, the device triggers and service fields fell back to English mid-dialog.
  • Cloud responses are size-capped before parsing.

Changed

The default poll interval is now 60 seconds (was 30). The tank reports to the Mixergy cloud roughly once a minute, so polling twice that fast could not surface fresher data — it only tripled the request count, since each cycle fetches measurement, settings and schedule. Boosts and control changes refresh immediately as before; only background polling slows.

This affects existing installs that never chose an interval. To keep 30 seconds, set it under Settings → Devices & Services → Mixergy → Configure. The 30–300 second range is unchanged.

Quality

46 of the 47 applicable Home Assistant Integration Quality Scale rules are now met, recorded per-rule in quality_scale.yaml. No tier is claimed: the scale applies to core integrations only, and one Bronze rule (brands) cannot be satisfied by any custom integration. Test coverage is 98% with every module above 95%, and ruff plus strict mypy run in CI against both the minimum and current Home Assistant.

Note on the HACS icon: it shows as a grey placeholder. Nothing is wrong with your install — the icon is correct everywhere inside Home Assistant. It is a known HACS limitation affecting every custom integration published after February 2026 (hacs/integration#5171).