SpecsModelExplore
Overview
Actors
External Systems
Edge DevicesObject StorageNotification Provider
IoT Platform
Edge Devices
Connection shape
Failure handling
Lifecycle workflows
SpecsModelExplore
Edge Devices
OverviewGuideLinks and Communications

Edge Devices

Edge Devices are the physical fleet in the field — sensors, controllers and embedded gateways. They are external to the platform: we control the contract (how they connect and what they send), not the firmware runtime itself.

Integration contract

Devices connect over MQTT secured with TLS client certificates. They publish telemetry upstream and subscribe to commands and desired-state downstream — a bidirectional, long-lived session.

Connection shape

  • Transport: MQTT over TLS (mutual auth).
  • Identity: per-device X.509 client certificate.
  • Keepalive: periodic PINGREQ; missed windows mark the device stale.

Failure handling

  • A device with an expired or revoked certificate is refused at the broker.
  • Lost sessions reconnect with backoff; presence is tracked separately by the Connection State Tracker.
  • Telemetry buffered on-device during an outage is replayed on reconnect.

Lifecycle workflows

A device first comes under management through provisioning:

Once connected, its telemetry feeds the alert pipeline: