Skip to main content
Version: 1.3

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 stream your system follows controls which releases reach it.

For most users, the Stable track is the right choice and is the ONLY stream we support for consumers with a support plan.

On a Nomad Appliance you can see your stream at any time. Open Settings, then System, and read the Update channel row under Software updates.

Moving a system between streams is something Sensa does, not something you do. Beta and Edge are invitation-only, and a system on either needs to be one we know about, so ask support rather than looking for a setting. On an Enthusiast or DIY install you manage your own stream in Home Assistant in the usual way.

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 Sensa staff and a very select number of customers. They may include incomplete work, regressions, unexpected behaviour, 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.

For most installations:

  1. start on Stable
  2. move to Beta only if you want to help validate newer releases
  3. 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

Changing stream does not update your system there and then, and the two directions behave differently.

Moving up a stream, towards newer software, happens at your next update: when you press Update now, or when your maintenance window comes round. Until then your system keeps running what it has, and an update shows as waiting. That is expected, not a fault.

Moving down a stream never arrives on its own. The build on the lower stream is older than the one you are running, so nothing ever shows as waiting and your system correctly reports that it is already on the latest version. It carries on running what it has until Sensa installs the lower stream's build for you, which is a deliberate step somebody takes rather than something that turns up overnight. If you have asked to be moved down, ask support to finish the job rather than waiting for it. Your own Update now only ever moves forward: see Rollback.

Last updated on