What is IoT & Connectivity?
A device that only blinks an LED is not an IoT device. IoT starts the moment your firmware opens a socket, sends data somewhere, and receives a command back. That sounds simple. In practice it means dealing with unstable WiFi, broker authentication, encrypted connections, dropped packets, industrial sensors that speak 30-year-old protocols, and devices that must keep working even when the internet doesn't.
Block 3 is about building firmware that connects to the real world — reliably, securely, and in a way that doesn't fall apart the moment something goes wrong in the field.
What you'll be able to do after this
Read a Wireshark capture of an MQTT session and know exactly what's happening at every step
Design a topic schema that works for a single device today and a fleet of thousands tomorrow
Write WiFi + MQTT reconnection logic that actually handles every failure case
Implement TLS mutual auth and store credentials correctly on the device
Get data out of a Modbus RTU sensor and route it to the cloud
Build firmware that buffers data locally during outages and syncs when connectivity returns
What's covered
3.1 Networking
The foundation everything else builds on. Most firmware engineers treat the network stack as a black box and then can't debug it when it misbehaves. This section fixes that — TCP/IP mechanics, how WiFi events actually fire on ESP32, and what TLS is doing before your first MQTT packet is sent.
→ 3.1 Networking sessions
3.2 MQTT Deep Dive
MQTT looks simple until you hit production. This goes inside the protocol — packet structure, what QoS actually guarantees, topic schema design that scales, retained messages and LWT for device presence, connecting to EMQX and GrapesIoT, and a systematic debugging method for when things break.
→ 3.2 MQTT sessions
3.3 Communication Patterns
Knowing the protocol isn't enough — you need to know how to use it well. Pub-sub vs request-response, command-acknowledge patterns, the difference between a telemetry reading and an alarm, and how to buffer data in a ring buffer so a WiFi outage doesn't lose sensor history.
→ 3.3 Communication Pattern sessions
3.4 Security
Real IoT devices have been used to take down the internet (Mirai botnet) and physically destroy industrial equipment. Security here is not theoretical — real attack case studies, secure boot, certificate-based auth, correct credential storage in NVS, and signed OTA updates. This is the section that separates hobbyist firmware from production firmware.
→ 3.4 Security sessions
3.5 Protocols Beyond MQTT
MQTT isn't the answer to everything. HTTP/REST for on-device APIs, WebSocket for local dashboards, Modbus RTU for industrial sensors on RS-485 (which isn't going away), and BLE provisioning so users can configure WiFi credentials without hardcoding them.
→ 3.5 Protocols sessions
Capstone
A fully connected, secure IoT device — TLS-authenticated MQTT connection to GrapesIoT, proper topic schema, LWT-based presence detection, and offline buffering that survives a broker outage. Submitted to the lab forum and reviewed against a checklist.
→ Block 3 Labs — submit here
Start at embiq.grapesiot.com/embedded-iot/block3 — each section links to its sessions from there. Post questions in this category and tag with the section number (e.g. 3.2) so the right people see it.