Beta releases — what they are and when to install one

This integration ships two kinds of releases:

• Stable — vX.Y.Z (e.g. v2.21.5). What HACS installs by default. Recommended for everyone.
• Beta — vX.Y.Z-beta.N (e.g. v2.22.0-beta.3). Pre-release builds used to validate fixes and refactors before they roll up into the next stable.

Should I install a beta?

The default answer is no. Stable is the right choice for almost everyone.

Install a beta only if one of these applies:

• You are hitting a bug on the current stable, a beta is out that claims to fix it, and you are willing to confirm whether the fix works for you.
• A beta's release notes call out something you specifically want to test, and you are comfortable rolling back if it misbehaves.
• You are a developer or contributor helping validate a refactor.

If none of those apply, stay on stable. Betas exist to catch regressions before they reach everyone — they are not an early-access channel for new features. Each beta's release notes include a version-specific "Should I install this?" section at the top.

How to install a beta (or roll back to stable)

The wiki has the exact HACS steps — including how to toggle Show beta versions and how to revert to the latest stable:

➡️ Installation → Beta releases

Where to find all available releases

Every tag — stable and beta — is listed on the Releases page, with the full release notes for each.

Found a problem on a beta?

Open an issue with the beta version number in the title and a diagnostics download attached. That is the fastest path to a fix.