Dealer Operations

AutoGen Dealer Manual

This guide is for dealers managing their own fleet, firmware rollout tasks, customer access, and API tokens inside dealer scope.

Fleet ScopeDealer-owned devices only.
FirmwareDeploy, pause, or clear dealer fleet rollouts.
TokensCreate customer or dealer-scoped API access safely.
ControlUse single-device manage tools for day-to-day operations.
Access

Dealer Scope

Dealers can
  • view dealer fleet devices
  • use Fleet Console and Fleet Map
  • manage eligible devices
  • deploy `my_fleet` rollouts
  • issue tokens within dealer scope
Dealers cannot
  • push global firmware
  • manage devices outside dealer scope
  • issue tokens outside dealer scope
  • use admin-only override actions
Monitoring

Fleet Console

Fleet Console is the main daily operations page. Use it to search by device ID, customer email, or device name, confirm connection state, review firmware version, and open the single-device Manage page.

After any OTA, confirm both that the device is live again and that the reported firmware version changed to the expected release.
Dealer Fleet Console
  1. Use search to filter by device ID, customer email, or device name.
  2. Use the Manage button to open the selected device.
  3. Confirm firmware versions after OTA or staged rollout.
  4. Check live and offline state before taking action.
Location

Fleet Map

Fleet Map is intended for GPS-enabled devices. Use it to inspect recent position or last known location for dealer-scoped field units.

Dealer Fleet Map
  1. Use the map to understand geographic distribution of your fleet.
  2. Red markers highlight units that need attention or lost contact.
  3. Green markers highlight units that are reporting normally.
Control

Device Manage Page

The Manage page gives you single-device actions such as Start, Stop, Reboot, FW Update, and Force OTA. Use it for targeted actions and for post-rollout validation on one device.

  • FW Update: normal remote update action
  • Force OTA: immediate OTA attempt when needed
  • Reboot: use carefully on remote units
Dealer device Manage page
  1. Status fields confirm you are acting on the correct device.
  2. Start and Stop send live commands to the selected unit.
  3. Firmware actions are grouped for update checks and recovery.
Releases

Firmware Rollouts

Dealers use rollout sections only, not admin override sections. For X Pro, use the X Pro firmware console. For D100, D180, V100, and V5, use the Unified firmware console. For AutoGen Ultra, use the dedicated Ultra firmware console and confirm the correct GSM or WiFi variant before deployment.

Dealer X Pro firmware console
Dealer Unified firmware console
Dealer Ultra firmware console
X Pro

Use rollout actions for dealer fleet X Pro devices.

Unified

Choose the correct engine and transport variant before deploying.

Ultra

Choose the correct transport variant and use the Ultra-only console so Ultra releases do not share policy with Unified engines.

Procedure

Safe OTA Procedure

  1. Validate the firmware on a test device first.
  2. Select the correct console, engine, and variant.
  3. Deploy to my_fleet.
  4. Monitor Fleet Console until devices return online.
  5. Confirm reported firmware versions changed correctly.
GSM and GPS devices can take longer than WiFi units to return after OTA. Do not assume failure too quickly.
Integrations

API Tokens

Use the API Tokens page to issue read-only or control-enabled bearer tokens within dealer scope. Restrict tokens to specific devices when running demos, pilots, or narrow integrations.

Dealer API tokens page
  • Read-only: dashboards, reporting, monitoring
  • Control-enabled: only when the integration must send commands or supported settings writes
Workflow

Dealer Workflow

Roll out a tested firmware

  1. Validate on one device first.
  2. Open the correct firmware console.
  3. Choose correct engine and variant.
  4. Deploy to my_fleet.
  5. Monitor versions and online return in Fleet Console.

Issue customer API access

  1. Choose the correct user account.
  2. Decide read-only or control-enabled deliberately.
  3. Restrict devices if needed.
  4. Create the token and hand it off securely.