Update the Suta agent

The Suta agent is the small program on each device that talks to Suta. You can update it on one device, or on many devices in stages with a rollout.

What happens on each device

1. The device downloads the new agent and checks its signature and checksum.
2. It installs the new agent and restarts it.
3. It checks that the new agent is healthy.
4. If that check fails, it puts the previous agent back automatically.

The device keeps its identity and network settings throughout.

Update one device

1. Open the device. The Suta agent row on the Overview tab shows the installed version.

2. If a newer version is available, select Update agent.

3. Watch the progress. If the device is offline, the update starts when it next connects.

Up to date means the device runs the latest published version. Devices with a newer version available show an Update label in the device list.

Update many devices with a rollout

A rollout updates a small canary group first, then the rest in batches. It pauses when devices fail, so a bad update reaches as few devices as possible.

1. Go to Deployments and select Update agents.

2. Under Devices, choose All devices or one tag.

3. Under Start with, choose how many canary devices update first, such as 1 canary device. Under Then update, choose a batch size.

4. Under If a device fails, choose Pause immediately or allow a few failures before the rollout pauses.

5. Check the preview. It shows how many devices will update and which ones are skipped and why, for example Already up to date or Agent too old for remote updates.

6. Select Start rollout.

The rollout panel shows each stage’s progress and every device’s state. A batch starts only when every device in the previous one has updated.

• Devices that are offline when their batch starts are skipped.
• A device that fails, rolls back, or doesn’t finish within 30 minutes counts as a failure. Once failures exceed what you allowed, the rollout pauses with the reason.
• Resume continues with the remaining devices. Failures you’ve already seen don’t pause it again; new ones do.
• Retry failed queues failed devices and devices that were offline again, including after the rollout has completed.
• Pause stops it at any time. Cancel stops it for good; devices already updating finish on their own.

The devices and the version are fixed when the rollout starts, so tagging a device afterwards doesn’t add it. You can run one rollout at a time, and each step is recorded in Activity. You need the Update the Suta agent permission. You can also run rollouts from the CLI, from CI with an API token, or through an AI agent.

What this updates

This updates only the Suta agent. It doesn’t update your applications or the operating system. To update all Suta software on a device, including the remote access and monitoring helpers, run the installer again.

If an update fails

A failed update shows its reason on the device page and can open an alert. The previous agent keeps running. Devices with an agent older than 0.3.0 can’t update remotely; reflash them or run the installer again.