Release Streams
The Release Stream governs when you receive updates to your system. Some users want the most stable experience possible. Others want access to newer changes sooner, even if that means a higher chance of issues. The release stream you choose controls which stream of releases your system follows.
For most users, the Stable track is the right choice and is the ONLY stream we support for consumers with a support plan.
Why release tracks exist
Not every update is suitable for every user at the same time.
Release tracks make it possible to:
- provide a well-tested option for everyday use
- make upcoming changes available to testers earlier
- validate new features and fixes before they reach wider use
- reduce the risk of unstable changes reaching production installs
Available release tracks
Stable
The Stable track is the recommended choice for most users. Our customer Support Policy is ONLY for the Stable stream.
Stable releases are intended for normal day-to-day use and should be the best choice for production installs. They are the releases most users should run in a campervan or other live environment.
Choose Stable if you want:
- the lowest risk
- the most predictable update experience
- releases intended for regular use
- the recommended path for production installs
Beta
The Beta track is for users who want access to newer changes before they reach Stable. You should only be using Beta if you have been invited to test a a new release.
Beta releases are usually more mature than Edge, but they may still contain issues, incomplete changes, or behaviour that is still being validated in real-world use.
Choose Beta if you:
- are comfortable testing newer releases
- want earlier access to changes and fixes
- are willing to report issues
- understand that problems may still occur
- have been invited to this stream
Beta is NOT to be used for production use.
Edge
The Edge track provides the newest changes first. This will be a rocky road and has the latest software with potentially all the newest problems.
Edge releases are intended for development, evaluation, and early testing by BlackPaw staff and a very select number of customers. They may include incomplete work, regressions, unexpected behavior, or changes that are later revised before reaching Beta or Stable.
Choose Edge only if you:
- you have been invited to the Edge stream
Edge is not recommended for production installs.
Choosing the right release track
A simple rule of thumb is:
- choose Stable for normal day-to-day use
- choose Beta if you have been invited to help test our newer releases
- choose Edge if you have been invited for the rocky road
If you are unsure, ALWAYS choose Stable.
Home Assistant add-on and device firmware
Release tracks may apply to:
- the Home Assistant add-on
- device firmware
- both, depending on the product and release process
In many cases, device firmware may be shared across editions, while some releases may apply only to a specific edition or device. Always check the release notes and compatibility information before changing release track.
Important considerations
Before moving away from Stable, make sure you understand:
- the level of risk you are accepting
- whether the release applies to your edition or device
- whether any manual action is required
- whether rollback or recovery steps are available if something goes wrong
This is especially important in live vehicle installations where reliability matters.
Recommended approach
For most installations:
- start on Stable
- move to Beta only if you want to help validate newer releases
- use Edge only for active testing or development work
Before changing release track
Before switching release track, review:
- the latest release notes
- any breaking changes
- the compatibility matrix
- the upgrade and rollback guidance