Admin Operations

AutoGen Admin Manual

This guide is for AutoGen admins managing the full fleet, firmware policy, single-device overrides, dealer rollout support, and API token administration.

Fleet ScopeFull-fleet visibility and operations.
OverridesSingle-device control for controlled testing and recovery.
RolloutsDealer-scoped or global firmware policy.
TokensRead-only and control-enabled integration access.
Access

Admin Scope

Admins can view the full fleet, manage firmware policy globally, apply and clear single-device overrides, support dealer rollout actions, and administer API tokens across the permitted user base.

Monitoring

Fleet Console

Fleet Console is the fastest full-fleet operational screen. Use it to verify live or offline state, search across dealers and customers, confirm OTA version uptake, and jump into device-level management quickly.

Example Layout: Fleet Console Real fleet view used for full-fleet monitoring.
Admin Fleet Console
1Search and filters

Start here when you need to isolate one dealer, one user, one firmware version, or one problem device quickly.

2Firmware and live state

This is the first place to confirm whether an OTA actually landed and whether the device came back live afterward.

3Device rows

Rows are the operational units of the fleet console. Read across them rather than focusing on one column in isolation.

4Manage

Use Manage when a fleet-level question becomes a device-level action or investigation.

After any firmware change, confirm both live return and the final reported firmware version. Version confirmation matters as much as connectivity.
Control

Device Manage Page

The Manage page is the single-device action screen for targeted operational tasks. Use it for command validation, reboot actions, OTA forcing, and troubleshooting one device before widening a rollout.

Example Layout: Device Manage Page Real fleet view used for full-fleet monitoring.
Admin device Manage page
1Device identity

Always validate the exact target before running commands. Mistakes here turn into operational errors very quickly.

2Live state and telemetry

Use these values to decide whether the device is healthy, online, and in the right condition for a firmware or control action.

3Action controls

Keep single-device actions narrow and intentional. This page is where you prove a step before expanding scope.

4Policy context

OTA interpretation depends on knowing which policy layer currently applies to the device.

Policy

Firmware Policy Model

Firmware policy resolves in this order:

  1. single-device override
  2. dealer rollout
  3. global rollout

The most specific rule wins. Always validate the intended scope before assuming what a device will follow.

X Pro

X Pro Firmware Console

Admin X Pro firmware console
Single-device override

Use for controlled field testing, one-device recovery, or validating a release before broad rollout.

Rollout

Use my_fleet for dealer-scoped action or all_global for intentional global X Pro policy.

Unified

Unified Firmware Console

For Unified devices, always confirm the correct combination of:

  • Firmware Variant: GSM or WiFi
  • Engine: D100, D180, V100, or V5
  • Version
Admin Unified firmware console
Admin Unified device override engine selection
Admin Unified rollout engine selection
Transport mistakes are expensive. Never treat GSM and WiFi images as interchangeable.
Ultra

Ultra Firmware Console

For AutoGen Ultra devices, always confirm the correct combination of:

  • Firmware Variant: GSM or WiFi
  • Version
Admin Ultra firmware console
Single-device override

Use for controlled field testing, one-device recovery, or validating an Ultra release before broader rollout.

Rollout

Use my_fleet for dealer-scoped action or all_global for intentional global Ultra policy.

Ultra releases are isolated from Unified and X Pro. Use the dedicated Ultra console for overrides, dealer rollout, and global rollout. Use it only for Devices.Type = 8 Ultra controllers.
Release Discipline

Safe Release Procedure

  1. Bench test locally.
  2. Upload the bin to the correct EC2 firmware directory.
  3. Apply a single-device override to one test device.
  4. Trigger or wait for OTA and confirm the test device returns.
  5. Expand to dealer scope if stable.
  6. Expand globally only after validation.
For GSM and GPS devices, allow extra time after OTA before concluding failure. Return-to-cloud can be slower than WiFi.
Integrations

API Tokens

Use the API Tokens page to issue bearer tokens for dashboards, reporting, automation, and approved control workflows.

Admin API tokens page
Read-only

Preferred default for dashboards, reporting, and customer visibility.

Control-enabled

Use only when the integration must send commands or supported settings writes.

Workflow

Admin Workflow

Validate and release firmware

  1. Bench test locally.
  2. Upload bin to the correct directory.
  3. Apply one device override.
  4. Confirm update and live return.
  5. Expand scope only after proof.

Create integration access safely

  1. Choose the correct owning user.
  2. Decide read-only or control-enabled deliberately.
  3. Restrict devices if appropriate.
  4. Create the token and store ownership details internally.