Installation

Installation

HACS (Recommended)

In HACS, search for Adaptive Cover Pro, download, and restart Home Assistant. Then add the integration from Settings → Devices & Services → Add Integration.

Already installed via custom repository? Follow Migrating from Custom Repository to switch to the default-store listing without losing any configuration.

Manual

Download the adaptive_cover_pro folder from this github. Add the folder to config/custom_components/.

Restart Home-Assistant and add the integration.

Release cadence

Adaptive Cover Pro uses CalVer versioning (Year.Month.Patch, like Home Assistant itself — e.g. 2026.7.0). A stable release ships on the first Tuesday of each month, with in-month patch releases as needed for bug fixes. New features land in the following month's release.

Beta releases

Pre-release builds are tagged vYYYY.M.PATCH-beta.N and published alongside stable releases. They exist to validate fixes and refactors before they roll up into the next stable. Most users should stay on stable — see the pinned Beta releases discussion for when to install one.

Install a beta in HACS:

1. Open Adaptive Cover Pro in HACS.
2. Click the ⋮ menu in the top-right and pick Redownload.
3. Toggle Show beta versions on.
4. Select the beta tag you want from the version dropdown and click Download.
5. Restart Home Assistant.

Roll back to stable: repeat the same flow, but leave Show beta versions off and pick the most recent vX.Y.Z stable tag.

Browse every available build: the Releases page lists every tag — stable, beta, and dev — with its release notes. Each beta's notes include a version-specific "Should I install this?" section.

Develop builds

Every push to the develop branch triggers a pre-release build from that new tip, tagged vYYYY.M.PATCH-alpha.<timestamp> (e.g. v2026.8.1-alpha.202607081432). The full test suite must pass before the build is published, so a develop build appears within minutes of anything merging to develop. The seven most recent develop builds are kept; older ones are pruned automatically.

A develop build carries everything merged to develop — including work that hasn't been bundled into a beta yet. That makes it the least-validated build available: handy for confirming a fix the moment it merges, but not something to leave a production blind sitting on. If you're not chasing a specific change, stay on a beta or stable.

Develop builds appear in the same place as betas. With Show beta versions toggled on in HACS Redownload, pick the -alpha. tag from the version dropdown. The -alpha version deliberately sorts below stable and beta, so HACS never surfaces a develop build as an available update — you have to select the exact -alpha. tag yourself. Roll back the same way you would from a beta — toggle Show beta versions off and reselect the latest vX.Y.Z stable.

Builds before 2026-07-29 used a .dev<timestamp> suffix instead (v2026.8.0.dev202607291440). Those sorted correctly in HACS but wrongly on GitHub's tag list, where they outranked the beta they were supposed to sit under. Nothing changes about how you install or roll back — only the tag spelling.