v2026.03.15

Highlights

• Publish the stable PR2 release with dedicated read-only sensors and the pressure-switch binary sensor (#87).
• Keep the temporary compatibility window for legacy climate attributes while encouraging the new dedicated entities (#87).
• Preserve upgrade coverage from pre-PR1 installs, including the migration smoke path for legacy/YAML-origin setups (#87).

Fixes since v2026.03.11

• Fix the climate entity-registry migration regression that could break ConfigFlow-only installs on restart with:
  ValueError: Unique id '...:climate' is already in use by ...
• Keep the valid legacy/YAML migration path intact while skipping the incorrect rewrite on already-stable ConfigFlow entities.
• Align the Docker/dev environment with the optional HA 2026.x dependencies needed by current core service validation.
• Group climate, sensor, and binary sensor entities under the same Home Assistant device and mark the dedicated read-only entities as diagnostic.
• Keep migration smoke working cleanly on forks as well as on the upstream repository.

Upgrade notes

• Users affected by the startup regression in v2026.03.11 should be able to upgrade directly to this release.
• In local validation, the path “broken on v2026.03.11, then switch to the fixed build” recovered cleanly without requiring an intermediate release.
• If you were testing v2026.03.14-beta2, this stable release is the same validated code, now published as a normal release.

Tracking

• PR2: #87
• Regression report: #89
• Roadmap: #68
• PR organization discussion: #77

Contributors

Thanks to @jmcollin78 for the testing, review feedback, and migration bug report that helped catch and narrow the restart regression.

Thanks to @Basfoppele and @thomasvanhorde for the real-world reports, rollback/retry testing, and logs on issue #89.

Thanks to @aceindy for project stewardship, hardware-side context, and release coordination.