ecoNET-300 v1.3.0 🎉

A stable release that consolidates all of the 1.3.0 beta fixes. No manual configuration migration is required — your existing setup keeps working.

✨ What's New

• 📅 Schedules as Calendar entities — heating, mixer, and hot-water schedules are now real Home Assistant Calendar entities (instead of text sensors). Easier to view and to use in automations.
• ⚙️ Configurable settings — from the integration Options you can now:
  • set separate polling intervals per endpoint,
  • choose device grouping: split (separate devices, default) or single (one merged device).
• 🩺 Health diagnostics — new entities: Data age, Consecutive failures, Last successful update, and a Live polling connectivity sensor. You can see the integration's health even when the boiler isn't responding.
• 🔥 More heat-pump (Phoenix) sensors and an editParams catalog of editable parameters.
• 🧹 Cleaner entity list — removed duplicate boiler-output sensors (kept the "running now" states), and moved registration/configuration values into Diagnostics.

⬆️ Upgrading from 1.2.x — important

Home Assistant does not delete old entities on upgrade, so a few will become Unavailable and should be removed manually:

1. Update via HACS and restart Home Assistant.
2. Go to Settings → Devices & Services → ecoNET300 → Entities.
3. Filter by Unavailable.
4. Delete the old sensor.*_schedule (schedule) sensors and any leftover Unavailable boiler sensors.

Deleting is safe — it only removes the stale registry entry. If your automations used the old schedule sensors, switch them to the new Calendar entities.

📖 Full details: CHANGELOG · Migration guide