
📡 IoT · Sequence
How a device fleet gets a firmware update safely: staged rollout, signed images, verification, reboot and automatic rollback.
Drawing diagram…
Firmware over-the-air sequence: the engineer uploads a signed firmware image and creates a campaign for 5% of devices, the OTA service notifies each device in the batch, the device downloads the image over HTTPS, verifies the signature and checksum, writes it to the inactive partition, reboots, runs a health check and reports success; on failure it boots the previous partition and reports rollback. If the batch success rate is above 98%, the campaign expands to all devices.
sequenceDiagram
actor E as Engineer
participant OTA as OTA Service
participant D as Device
E->>OTA: Upload signed firmware v2.4
E->>OTA: Campaign: 5% of fleet
OTA->>D: Update available
D->>OTA: Download image (HTTPS)
D->>D: Verify signature and checksum
D->>D: Write to inactive partition
D->>D: Reboot into v2.4
alt Health check passes
D->>OTA: Success
else Health check fails
D->>D: Boot previous firmware
D->>OTA: Rolled back
end
OTA->>OTA: 99% success in batch
OTA-->>E: Expand to 100%How sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.
How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.
A general-purpose IoT platform: device connectivity, device management, data processing, rules and the apps built on top.
Where processing happens in an edge IoT setup: devices, an on-site edge server running containers, and the cloud for fleet management and long-term storage.
How a smart home reacts to events: motion, door and temperature triggers run rules for lights, locks, AC and alerts.
How MQTT messaging works between devices, a broker and applications: connect, subscribe, publish with QoS, retained messages and last will.