
📡 IoT · Sequence
How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.
Drawing diagram…
Sequence for provisioning a new IoT device: the owner scans the claim code in the mobile app, the provisioning service links the device to the owner's account in the device registry. When the device first boots it sends a certificate signing request, gets an X.509 certificate from the certificate authority, connects to the MQTT broker with mutual TLS and publishes its first status message.
sequenceDiagram actor Owner participant App as Mobile App participant Prov as Provisioning Service participant Reg as Device Registry participant CA as Certificate Authority participant D as Device participant MQ as MQTT Broker Owner->>App: Scan claim code App->>Prov: Claim device Prov->>Reg: Link device to account Reg-->>Prov: Linked D->>Prov: First boot, send CSR Prov->>CA: Sign certificate CA-->>Prov: X.509 certificate Prov-->>D: Certificate and broker URL D->>MQ: Connect with mutual TLS MQ-->>D: Connected D->>MQ: Publish status: online
How sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.
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.
Every state an IoT device goes through, from manufacture to decommissioning, including updates, faults and replacement.