Design and build a connected product of your own on the ESP32-C3, milestone by milestone: the brief, the data contract, firmware, a dashboard, failure handling, a security review and a demo.
0 of 7 done
7 lessons in 4 chapters, about 8 hours on a simulated ESP32-C3-DevKitM-1. Free, in your browser, every step checked by the simulator.
Design the message before the code: a versioned JSON reading with units in its field names, a round trip through echo.mokxi to prove it parses, and a config pulled from api.mokxi that is checked before it is trusted.
Open it in the simulatorThe node serves its own dashboard and a JSON endpoint from a WebServer, with one setLimit() behind both the form and the Serial Monitor, and the status LED following whatever either one sets.
Open it in the simulatorReview the node like an attacker: a token printed to the log, a limit that trusts any text, a name that could inject HTML into the dashboard, and a short threat model of who can reach what.
Open it in the simulatorEach lesson opens when the one before it is done, and each chapter ends in a project.
Pick a product, write requirements with numbers, and design the data before the code.
The brief for a connected product of your own, and FridgeWatch, the reference build: a shared-fridge monitor that has to do its one job before it ever touches a network.
0 of 6 steps
Design the message before the code: a versioned JSON reading with units in its field names, a round trip through echo.mokxi to prove it parses, and a config pulled from api.mokxi that is checked before it is trusted.
0 of 7 steps
Firmware that never waits, and a dashboard served by the board itself.
The node as one loop that never waits: each job checks its own millis() clock and returns, so the LED keeps blinking while reports go out, and a serial console answers at any moment.
0 of 6 steps
The node serves its own dashboard and a JSON endpoint from a WebServer, with one setLimit() behind both the form and the Serial Monitor, and the status LED following whatever either one sets.
0 of 6 steps
Survive a bad network and a curious attacker.
Make it expect trouble: WiFi as a state machine that names each failure and backs off, a weak-signal warning, a config fetch that survives errors and bad JSON, and readings buffered through an outage and sent when it ends.
0 of 7 steps
Review the node like an attacker: a token printed to the log, a limit that trusts any text, a name that could inject HTML into the dashboard, and a short threat model of who can reach what.
0 of 6 steps
A 60 second demo, a release, a README and a link to share.
The finished build in a 60 second demo: it reports, it warns, it survives an outage. Then tag the release, write the README and share the project.
0 of 7 steps
All 7 lessons, in order, each with what it covers. Any of them opens in the editor right away.
Every lesson runs in the simulator with nothing to buy. When you want the real thing, these kits have the parts.
Pick the starter kit you own and run every lesson in its manual with the same parts on the same pins.
See every kitYes. All 7 lessons of IoT capstone: your own connected product are free and run in your browser, with nothing to install and no parts to buy before you start.
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.
About 8 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.
Each chapter ends in a project that puts it together: Data and API design, Dashboard and Security review.
With "Pick a product", and each lesson builds on the one before it. New to circuits? Electronics basics is the course that starts from zero.