Updating

Updating

Once ShellyElevate is on the device there are three ways to move it to a newer version. Which ones you can use comes down to how it was installed.

Your settings are safe through all of them. They live in the app's private storage, and none of these touch it.

Reinstall over ADB

The one that always works. Grab a newer APK and install it over the top:

adb install -r shellyelevatev2.apk

-r reinstalls without wiping data. You need a cable or ADB over Wi-Fi, and the new APK has to be signed with the same key as the one already installed — that's Android's rule for any app update, not ours.

From inside the app

If ShellyElevate is running as a system app, it can update itself. Open settings, find the update section, hit Check for updates. It asks GitHub for the latest release; if that's newer than what's running it downloads the APK, checks the signature against the installed app, copies it into /system/priv-app, and offers to reboot.

Two catches:

• It only works when the app is a system app. A normal install can't write to /system, so there's nothing for the button to do — promote it first (see Installation).
• The signature check is why the install-as-system-app step nags about signing keys. An update whose signature doesn't match the running app gets rejected, so a locally-built copy won't self-update to official releases, and the other way around.

The WebView (Stargate only)

The original Stargate shipped with an old Android System WebView — old enough that newer Home Assistant dashboards can look broken. ShellyElevate can fetch the official WebView update, stage it, and reboot so the recovery applies it, which is the same thing the stock Shelly app does. The option only shows up on the Stargate, and only when the installed WebView is actually old enough to be a problem.

This updates the system WebView, not ShellyElevate, so it's a one-off rather than something you'll do every release.

Watching for new versions

Releases show up on the Releases page. There's no push notification — the in-app check is manual. If you want to automate it, the / endpoint of the HTTP API reports the running version, so you can diff it against the latest release tag yourself.