CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/IoT

πŸ“‘ IoT Β· Sequence

Firmware OTA Update Sequence

How a device fleet gets a firmware update safely: staged rollout, signed images, verification, reboot and automatic rollback.

More IoT templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Updates go to a small percentage of devices first
  • Devices verify the image signature before installing
  • A failed boot rolls back to the previous firmware

Prompt used

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.

Mermaid code
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%

Inside this diagram

A sequence diagram with 3 participants and 12 messages, in the order they happen.

People

  • Engineer

Systems

  • OTA Service
  • Device

Steps in order

  • 1. Engineer β†’ OTA Service: Upload signed firmware v2.4
  • 2. Engineer β†’ OTA Service: Campaign: 5% of fleet
  • 3. OTA Service β†’ Device: Update available
  • 4. Device β†’ OTA Service: Download image (HTTPS)
  • 5. Device β†’ Device: Verify signature and checksum
  • 6. Device β†’ Device: Write to inactive partition
  • 7. Device β†’ Device: Reboot into v2.4
  • 8. Device β†’ OTA Service: Success
  • 9. Device β†’ Device: Boot previous firmware
  • 10. Device β†’ OTA Service: Rolled back
  • 11. OTA Service β†’ OTA Service: 99% success in batch
  • 12. OTA Service β†’ Engineer: Expand to 100% (reply)

Conditions and loops

  • If: Health check passes
  • Otherwise: Health check fails

Make your own diagram like this

Describe your own system in plain English and the AI sequence diagram generator draws it in seconds, in the same style as this template.

Related templates

Data FlowIoT

IoT Telemetry Data Pipeline

How sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.

SequenceIoT

IoT Device Provisioning Sequence

How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.

C4 ArchitectureProIoT

IoT Platform Reference Architecture

A general-purpose IoT platform: device connectivity, device management, data processing, rules and the apps built on top.

DeploymentProIoT

IoT Edge Computing Deployment

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.

FlowchartIoT

Smart Home Automation Flow

How a smart home reacts to events: motion, door and temperature triggers run rules for lights, locks, AC and alerts.

SequenceIoT

MQTT Publish/Subscribe Messaging

How MQTT messaging works between devices, a broker and applications: connect, subscribe, publish with QoS, retained messages and last will.