Device Management

Devices accept secure parameter packs over HTTPS or MQTT. Supported settings include report rates, movement and sleep thresholds, digital inputs, ignition detection, and geofence lists. Conflicts are validated before apply. Failures queue for retry until confirmed.

Heartbeat packets provide battery voltage, RSSI, temperature, GNSS lock status, last GPS fix, and firmware build. Dashboards display trendlines and surface devices that cross defined limits. Data can be pulled on demand through the API.

Firmware files are signed and versioned. The platform stages the update, checks battery level and connection quality, and resumes safely after dropouts. Rollouts can be phased with canary groups and automatic rollback on failure.

The command engine batches jobs and respects rate limits per carrier and per device. You can filter targets by tag, model, firmware, or last-seen time. Progress and results are streamed in real time.

On first contact the device registers its identifiers, claims its profile, and binds to the correct tenant. SIM ICCID and APN are validated. Optional auto-naming and tagging rules speed deployment.

Rules evaluate telemetry at ingest and on device heartbeats. Supported actions include email, SMS, webhook post, and MQTT publish. All alerts are deduplicated to avoid noise.

RBAC separates tenants and restricts visibility by tag, group, or geography. Installers can add devices but cannot change billing or export data. Clients can see only their own fleets.

Every parameter change, command, firmware push, and login is timestamped with actor, target, and outcome. Logs are searchable and exportable for audits.