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

πŸ“‘ IoT Β· State Machine

IoT Device Lifecycle

Every state an IoT device goes through, from manufacture to decommissioning, including updates, faults and replacement.

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

  • Devices are registered at manufacture and claimed by customers
  • Firmware updates are a state with rollback on failure
  • Decommissioned devices have their certificates revoked

Prompt used

State machine for an IoT device: Manufactured, Registered with identity, Shipped, Claimed by the customer, Provisioned, Active. From Active it can go to Updating (firmware) then back to Active or Rollback on failure, to Offline when it stops reporting, to Faulty and then Replaced, or to Decommissioned with its certificate revoked.

Mermaid code
stateDiagram-v2
  [*] --> Manufactured
  Manufactured --> Registered: Identity burned in
  Registered --> Shipped
  Shipped --> Claimed: Customer scans code
  Claimed --> Provisioned: Certificate issued
  Provisioned --> Active
  Active --> Updating: Firmware update
  Updating --> Active: Success
  Updating --> Rollback: Failed
  Rollback --> Active
  Active --> Offline: No heartbeat 10 min
  Offline --> Active: Reconnects
  Active --> Faulty: Self-test fails
  Faulty --> Replaced
  Active --> Decommissioned: Certificate revoked
  Replaced --> [*]
  Decommissioned --> [*]

Inside this diagram

A state diagram with 12 states and 14 transitions.

States

  • Manufactured
  • Registered
  • Shipped
  • Claimed
  • Provisioned
  • Active
  • Updating
  • Rollback
  • Offline
  • Faulty
  • Replaced
  • Decommissioned

Starts in

  • Manufactured

Ends in

  • Replaced
  • Decommissioned

Transitions

  • Manufactured β†’ Registered when Identity burned in
  • Registered β†’ Shipped
  • Shipped β†’ Claimed when Customer scans code
  • Claimed β†’ Provisioned when Certificate issued
  • Provisioned β†’ Active
  • Active β†’ Updating when Firmware update
  • Updating β†’ Active when Success
  • Updating β†’ Rollback when Failed
  • Rollback β†’ Active
  • Active β†’ Offline when No heartbeat 10 min
  • Offline β†’ Active when Reconnects
  • Active β†’ Faulty when Self-test fails
  • Faulty β†’ Replaced
  • Active β†’ Decommissioned when Certificate revoked

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

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.