Manual SSH Update (Fallback)
Break-glass path for updating a device you can't reach from the dashboard — SSH in and run one script.
This is the fallback from the Update Model page: for a device the dashboard can't reach, you SSH into the Pi and run the update script directly, no cloud command in the loop.
Break-glass path only
Manual SSH updates bypass the dashboard rollout safeguards. Stay at the terminal until the script finishes, and confirm the service restarts cleanly before leaving the site.
Field tip
Only reach for this when OTA isn't an option — the device is offline from the dashboard's point of view, or OTA itself is unavailable. For every other case, use OTA from the Dashboard; that's the normal path.
SSH to the device
Connect to the Raspberry Pi over SSH using the credentials and host you'd normally use for this store.
Go to the install directory
cd ~/bytegate-edgeRun the update script
./scripts/update_system.shThe script is interactive — it backs things up, pulls the update, and restarts the service on its own, but it pauses for a Y/n confirmation at a few points (switching to the latest tagged release, restarting the service, continuing past a failed check). Stay at the terminal until it prints Update Complete!.
Confirm it landed
The script's own output tells you whether the service restarted cleanly. Once it's done, check the store's page in the Cloud Dashboard — the Edge Software version should show the new release within a heartbeat cycle or two.
Last updated on