v0.4.8

📦 DKNCloud-HASS v0.4.8

✅ Stable release for the 0.4.x line.
Focus: release packaging + coordinator resilience — HACS-friendly ZIP builds, documented/deterministic climate supported_features, and safer multi-installation refresh behavior that avoids sensitive metadata in logs.

---

🚀 Highlights (since 0.4.7)

• 🧰 HACS-ready release ZIPs

  • Enabled HACS zip_release packaging and added validated release ZIP workflows producing airzoneclouddaikin.zip.

• 🧭 Documented + tested dynamic climate supported_features

  • Documented the dynamic supported_features contract (DRY/FAN_ONLY/OFF rationale).
  • Locked the mode → feature matrix with regression tests to prevent accidental behavior drift.

• 🔁 Coordinator refreshes: faster, safer, and more resilient

  • Parallelized per-installation device fetches for better refresh latency.
  • Retains partial results when non-auth installation requests fail, while preserving cancellation semantics.
  • Treats the initial partial refresh as an update failure (so platforms don’t bootstrap off incomplete snapshots), and keeps the last known-good per-installation snapshot on later transient errors.
  • Scopes removed-device notification cleanup during partial refreshes to only the installations that refreshed successfully.
  • Prunes cached per-installation device maps when installations disappear from backend relations.

• 🕵️ Cleaner logs, less sensitive metadata

  • Avoids logging installation identifiers during per-installation fetch errors.

• 🧹 More robust cleanup & options behavior

  • Removes orphaned PII sensor entities by unique-id suffix during opt-out cleanup even when coordinator snapshots are empty.
  • Recomputes HEAT_COOL capability in the options flow when the cached support flag is None and coordinator data later becomes available.

---

🧾 Detailed changes – 0.4.8 (2026-03-03)

Changed

• Enable HACS zip_release packaging and add validated release ZIP workflows for airzoneclouddaikin.zip.
• Document dynamic climate supported_features behavior (DRY/FAN_ONLY/OFF contract rationale) and lock the mode-feature matrix with regression tests.

Fixed

• Remove orphaned PII sensor entities by unique-id suffix during opt-out cleanup, even when coordinator device snapshots are empty.
• Recompute HEAT_COOL capability in the options flow when the cached support flag is unknown (None) and coordinator data later becomes available.
• Parallelize per-installation device fetches during coordinator updates and keep partial results when non-auth installation requests fail.
• Preserve cancellation semantics during parallel device fetches by propagating cancelled installation requests immediately.
• Avoid logging installation identifiers during per-installation fetch errors to keep coordinator logs free of sensitive metadata.
• Treat initial partial installation refreshes as update failures and retain the last successful per-installation snapshot on later transient errors.
• Scope removed-device notification cleanup during partial refreshes so only installations refreshed successfully are considered for removal handling.
• Prune cached per-installation device maps when installations disappear from the backend relations snapshot.

---

Full Changelog: v0.4.7...v0.4.8