Device service auto-update

Every edge device runs a set of built-in device services — for example browse, debug, hardware key, and licensing — alongside your runtime. These services update themselves from the cloud whenever a newer version is published, so devices in the field stay current without an engineer having to log in to each one.

How it works

1. The edge periodically checks the cloud for newer device-service versions. The check interval is configurable per device (DeviceServiceVersionCheckIntervalMs in the edge settings) and defaults to 60 seconds.
2. When a newer version is available, the edge runs the update flow for that service: stop the process, uninstall the old version, download and install the new version, update its local version record, and start it again.
3. The full sequence is reported step-by-step in the device’s activity log.

Auto-update is enabled by default for every device service. Install and uninstall are idempotent — if an update is interrupted, the next cycle resumes safely.

Watching an update in the portal

1. Open the Devices page and select the device.
2. Open the Activity log.
3. Follow the update sequence as it progresses. The activity entries read, for each affected service: stopping process for update, uninstalling version <old>, downloading version <new>, installing version <new>, then starting process.
4. Confirm the new version is reflected in the Device services area once the sequence completes.

Recovering from a failed update

1. Open the Activity log and locate the failing step (typically install or restart).
2. Verify the device has enough free storage and a working connection to the cloud.
3. Trigger Reinstall on the affected service from the device services area.
4. If the failure repeats, capture the activity log entry and contact support.

Device services should never be installed or uninstalled by hand on the device filesystem. Always drive install and uninstall through the portal so the activity log and cloud state remain in sync.