Chapters
How IoTClass Works · 6 of 8

Books

How IoTClass Works · 6 of 8

Three resource types, three different jobs: videos for watching a process happen, hands-on labs for building it yourself, and code references for the moment you're actually writing firmware.

Sammy, your guide

Sammy your guide, not a professor

“I used to treat a finished video as the same thing as understanding. It isn't — the lab afterward is where I actually found out what I'd missed.”

Videos

Short clips — more than 25 lecture highlights and walkthroughs across five categories: architecture, data analytics, security, networking, and sensing — embed directly inside the chapters they support, so you meet them in context instead of hunting a separate gallery. Coverage varies by module: some topics have several clips, others have none yet. Watch with a question already in mind, pause when something changes state, and validate what you saw with the chapter's own quiz afterward.

Hands-On Labs

A lab is only worth the time if it produces evidence — a packet trace, a serial log, a working dashboard — not just a finished screen. Guided labs live inside the modules that teach them: the MQTT module carries full ESP32 publisher, dashboard, and TLS labs, and the Energy & Power module has its own hands-on lab on power budgeting. Run one lab at a time, stop at each checkpoint to verify the actual output before moving on, and keep a short notebook of commands, versions, and anything that didn't work as expected.

Sammy

Sammy says: a lab that "worked" on the first try without a single confusing step is the one worth double-checking. Usually it means a checkpoint got skipped, not that everything actually lined up.

Code Snippets & Quick Reference

Runnable patterns — sensor reads, MQTT publish/subscribe, deep sleep, and the rest — now live as inline code inside the chapters that teach them, the same way the labs do, rather than in one giant standalone library. If you're mid-project and just need a fast lookup — a port number, a pin assignment, a formula — the relevant chapter is the right place to look; there's no separate catalog to keep in sync with it.

Find help

3 reviewed answers.

Where should I start in a module?

Open the module page from the sidebar to see its chapters in order. Use the module map to return to a topic you need.

Modules and paths

Reviewed

What can I try when a project does not work?

Check the symptom, then work through the diagnostic steps. Keep the error message and the smallest example that reproduces it.

When you are stuck

Reviewed

How do interactive examples work?

Use the interactive guide to check how examples and simulations work before changing your project.

Interactive examples guide

Reviewed