Push a new release to your balenaCloud fleet with balena push <fleet_name>; note the release ID or commit hash from the output
Pin the fleet to a specific release in the balenaCloud console (Fleet > Releases > Pin to release) or via the balena CLI: balena release finalize <release_id> followed by balena fleet pin <fleet_name> <release_id>
Override a single device to track a different release by pinning at the device level from the device's Actions menu, which takes precedence over the fleet pin
From within a running container, access the Supervisor API (available at the address in BALENA_SUPERVISOR_ADDRESS using BALENA_SUPERVISOR_API_KEY); restart a specific service: POST /v2/applications/<app_id>/restart-service with body {"serviceName": "<service>"}
Check device update status via the cloud API: GET https://api.balena-cloud.com/v6/device with a filter on uuid and inspect the is_on__release field
Unpin the fleet to resume tracking the latest release: balena fleet track-latest <fleet_name>
Known gotchas
Pinning a device overrides the fleet pin; if both are set, the device-level pin wins — audit individual device pins when debugging why a device is not on the expected release
The Supervisor API key (BALENA_SUPERVISOR_API_KEY) is available only to containers with the io.balena.features.supervisor-api label in the docker-compose.yml; add it only to services that genuinely need it
Restarting a service via the Supervisor API is non-destructive but may briefly interrupt network-dependent services; plan maintenance windows for production fleets
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp