🏁 Capstone: Finish and Demo Your BLE Gadget

You have built the pieces. The GATT service exists, notifications stream sensor data, control commands arrive from the phone, and you know how to recover from a dropped connection. Now we assemble everything into one final firmware and show it working.

This is a project lesson, so there is no new theory to memorize. Your job is to build, test, and present.

[!NOTE] Quick review from the last lesson. Three recovery rules carry into the capstone: the ESP32 does not resume advertising after a disconnect unless you restart it, your BLE callbacks must stay short, and every notification needs a connection, an active subscription, and reasonable pacing. Keep these in your mind while you finish the firmware.

Project Brief

The goal: ship a finished ESP32 gadget that a phone can connect to, that sends live sensor data to the phone, and that obeys a control command from the phone, all demonstrated in a short live demo.

Why it matters: building each feature separately teaches you the parts. Delivering a complete, working device teaches you what shipping actually feels like: fixed firmware, a repeatable test, and a story you can tell to someone else. That is exactly what a hobby project, a portfolio entry, or a job interview demo needs.

What you deliver:

  1. A single PlatformIO project that holds the full firmware, not a set of scattered test sketches.
  2. A phone test that exercises the whole loop, sensor to notification, and phone to command.
  3. A two to three minute live demo with a short spoken explanation.

Requirements and Spec

Your finished gadget must meet this specification:

This lesson is part of the paid section. Sign in and purchase the course to view the full content. Sign in