Updates

Updates are yours to trigger. Luma checks quietly whether something new exists, tells you, and then does nothing until you say go.

How Luma learns about a release

• Checks happen when you look: opening the Updates card in the app’s Settings, visiting the device’s update page, or pressing Check. Luma does not phone out on a timer — see Privacy.
• When something newer exists, an Update available badge appears on the device dashboard, and the app shows the new version with its release notes.
• Check results are cached for a few minutes, so repeated looks don’t hammer anything.

Installing

Two buttons, two scopes:

• Update this device only — the device downloads the release, verifies it, installs, and restarts. The app shows live progress and reconnects afterwards.
• Update all devices — a coordinated rollout from the Main: satellites update first, the Main goes last, with per-device progress and a cancel button. Offline satellites are skipped with a warning rather than blocking the rest.

During any install: keep the devices powered. Each one restarts itself when done. If a download fails partway, the device simply stays on its current version — an update either completes and verifies, or nothing changes. A rollout also pins the exact release it resolved at the start, so every device lands on the same version rather than whatever was newest when its turn came.

The beta channel

If you like living slightly ahead, the app’s Updates card has an Update channelswitch: Stable or Beta. Beta offers pre-release firmware as soon as it’s published — with the app’s own warning that these builds may misbehave. A BETAbadge marks the device while it’s opted in.

• The choice is per-device and sticky — it survives restarts and updates until you switch it back.
• Switching back to Stable doesn’t downgrade anything: the device stays on its beta build until a stable release outranks it, then updates normally.

What protects you

• Downloads happen over pinned, encrypted connections, and every file is checked against its published fingerprint before it’s installed.
• Firmware installs to a spare slot first — the running system is only switched once the new one is fully written.
• The device’s web interface updates alongside the firmware; if that second step can’t complete after several tries, the device rolls back to the previous version rather than running a mismatched pair.

Manual installs

The update page keeps a manual lane for the rare day the release feed is unreachable: drag a firmware file onto the page and install it directly. And a device with no working firmware at all can always be restored over USB — see Recovery & reset or go straight to the USB installer.