All paths

Device to cloud: telemetry that survives

Telemetry that reaches the server once, in order, through outages: sequence numbers, ArduinoJson payloads, batching, backoff with jitter, an offline queue on SD, device identity and idempotent uploads, on an ESP32-C3.

ESP32-C3-DevKitM-1Free7 lessons7 h4 chapters3,152 XPEmbedded engineering · Advanced+250 XP

0 of 7 done

What you will build

3 projects, built step by step

7 lessons in 4 chapters, about 7 hours on a simulated ESP32-C3-DevKitM-1. Free, in your browser, every step checked by the simulator.

Chapter 1 project

JSON payloads

Build payloads with ArduinoJson: nested objects and arrays, exact decimals with serialized(), the size before sending, short keys, and a server reply parsed with every failure checked.

Open it in the simulator
Chapter 2 project

Backoff

When the cloud fails: exponential backoff to a cap, full jitter so a thousand nodes do not retry in step, a reset on success, and never retrying a request the server called wrong.

Open it in the simulator
Chapter 3 project

Device identity

Who is this node? An id from a config file on the card or from the chip’s MAC, an API key that never lives in the code, an Idempotency-Key that makes a retried upload safe, and what to do when the key is refused.

Open it in the simulator
The map

Chapter by chapter

Each lesson opens when the one before it is done, and each chapter ends in a project.

Chapter 1

Messages

What a reading carries, and JSON that says it.

  1. Open265 XP

    Telemetry design

    What a reading must carry to survive the trip: who sent it, a sequence number that is never reused, when it was measured on the device’s own clock, and units in every name. And what a day of it costs.

    0 of 6 steps

  2. ProjectLocked728 XP

    JSON payloads

    Build payloads with ArduinoJson: nested objects and arrays, exact decimals with serialized(), the size before sending, short keys, and a server reply parsed with every failure checked.

    0 of 8 steps

4 questions, graded as you go.
Chapter 2

Sending well

Batching, and backing off when the cloud fails.

  1. Locked265 XP

    Batching

    One request for many readings: a JSON array with a sequence number in each entry, sent a batch at a time, kept whole when the post fails, and the trade between requests and delay.

    0 of 6 steps

  2. ProjectLocked606 XP

    Backoff

    When the cloud fails: exponential backoff to a cap, full jitter so a thousand nodes do not retry in step, a reset on success, and never retrying a request the server called wrong.

    0 of 7 steps

4 questions, graded as you go.
Chapter 3

Surviving

An offline queue on SD, and an identity the cloud trusts.

  1. Locked341 XP

    An offline queue

    Readings on the SD card first, uploads second: a JSON Lines queue file, a marker of how much is sent, the oldest first, nothing marked sent before a 2xx, and a sequence number that survives a reboot.

    0 of 8 steps

  2. ProjectLocked606 XP

    Device identity

    Who is this node? An id from a config file on the card or from the chip’s MAC, an API key that never lives in the code, an Idempotency-Key that makes a retried upload safe, and what to do when the key is refused.

    0 of 7 steps

4 questions, graded as you go.
Chapter 4

Boss project

A reliable telemetry node.

  1. Locked341 XP

    Boss: a reliable telemetry node

    Every idea at once: readings queued on SD with a persistent sequence number, idempotent batches with the node’s identity, backoff with jitter through an outage, a reboot in the middle, and a stop on a refused key.

    0 of 8 steps

3 questions, graded as you go.
Syllabus

Every lesson in the course

All 7 lessons, in order, each with what it covers. Any of them opens in the editor right away.

Chapter 1

Messages

  1. Telemetry designWhat a reading must carry to survive the trip: who sent it, a sequence number that is never reused, when it was measured on the device’s own clock, and units in every name. And what a day of it costs.
  2. JSON payloadsBuild payloads with ArduinoJson: nested objects and arrays, exact decimals with serialized(), the size before sending, short keys, and a server reply parsed with every failure checked.
Chapter 2

Sending well

  1. BatchingOne request for many readings: a JSON array with a sequence number in each entry, sent a batch at a time, kept whole when the post fails, and the trade between requests and delay.
  2. BackoffWhen the cloud fails: exponential backoff to a cap, full jitter so a thousand nodes do not retry in step, a reset on success, and never retrying a request the server called wrong.
Chapter 3

Surviving

  1. An offline queueReadings on the SD card first, uploads second: a JSON Lines queue file, a marker of how much is sent, the oldest first, nothing marked sent before a 2xx, and a sequence number that survives a reboot.
  2. Device identityWho is this node? An id from a config file on the card or from the chip’s MAC, an API key that never lives in the code, an Idempotency-Key that makes a retried upload safe, and what to do when the key is refused.
Chapter 4

Boss project

  1. Boss: a reliable telemetry nodeEvery idea at once: readings queued on SD with a persistent sequence number, idempotent batches with the node’s identity, backoff with jitter through an outage, a reboot in the middle, and a stop on a refused key.
Kits

Build it on your bench too

Every lesson runs in the simulator with nothing to buy. When you want the real thing, these kits have the parts.

Have a kit already?

Find your kit

Pick the starter kit you own and run every lesson in its manual with the same parts on the same pins.

See every kit
Questions

About Device to cloud: telemetry that survives

Is Device to cloud: telemetry that survives free?

Yes. All 7 lessons of Device to cloud: telemetry that survives are free and run in your browser, with nothing to install and no parts to buy before you start.

Do I need a real ESP32-C3-DevKitM-1?

No. Every lesson runs on a simulated ESP32-C3-DevKitM-1 with its parts on the canvas, and the simulator checks each step as you go. When you want to build it for real, the same wiring and code work on a real board.

How long does Device to cloud: telemetry that survives take?

About 7 hours: 7 lessons in 4 chapters, each one a few short steps. Your progress is kept, so you can stop after any lesson and pick up where you left off.

What will I build?

Each chapter ends in a project that puts it together: JSON payloads, Backoff and Device identity.

Where do I start?

With "Telemetry design", and each lesson builds on the one before it. New to circuits? Electronics basics is the course that starts from zero.