<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[📡 IoT & Connectivity]]></title><description><![CDATA[<h2>What is IoT &amp; Connectivity?</h2>
<p dir="auto">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.</p>
<p dir="auto">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.</p>
<hr />
<h3>What you'll be able to do after this</h3>
<ul>
<li>Read a Wireshark capture of an MQTT session and know exactly what's happening at every step</li>
<li>Design a topic schema that works for a single device today and a fleet of thousands tomorrow</li>
<li>Write WiFi + MQTT reconnection logic that actually handles every failure case</li>
<li>Implement TLS mutual auth and store credentials correctly on the device</li>
<li>Get data out of a Modbus RTU sensor and route it to the cloud</li>
<li>Build firmware that buffers data locally during outages and syncs when connectivity returns</li>
</ul>
<hr />
<h3>What's covered</h3>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f310.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--globe_with_meridians" style="height:23px;width:auto;vertical-align:middle" title="🌐" alt="🌐" /> 3.1 Networking</strong><br />
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.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-1-1" rel="nofollow ugc">3.1 Networking sessions</a></p>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f4e1.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--satellite_antenna" style="height:23px;width:auto;vertical-align:middle" title="📡" alt="📡" /> 3.2 MQTT Deep Dive</strong><br />
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.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-2-1" rel="nofollow ugc">3.2 MQTT sessions</a></p>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f501.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--repeat" style="height:23px;width:auto;vertical-align:middle" title="🔁" alt="🔁" /> 3.3 Communication Patterns</strong><br />
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.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-3-1" rel="nofollow ugc">3.3 Communication Pattern sessions</a></p>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f510.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--closed_lock_with_key" style="height:23px;width:auto;vertical-align:middle" title="🔐" alt="🔐" /> 3.4 Security</strong><br />
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.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-1" rel="nofollow ugc">3.4 Security sessions</a></p>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f50c.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--electric_plug" style="height:23px;width:auto;vertical-align:middle" title="🔌" alt="🔌" /> 3.5 Protocols Beyond MQTT</strong><br />
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.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-5-1" rel="nofollow ugc">3.5 Protocols sessions</a></p>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f3c1.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--checkered_flag" style="height:23px;width:auto;vertical-align:middle" title="🏁" alt="🏁" /> Capstone</strong><br />
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.<br />
→ <a href="https://forum.grapesiot.com/category/9/block-3-iot-connectivity">Block 3 Labs — submit here</a></p>
<hr />
<p dir="auto"><em>Start at <a href="https://embiq.grapesiot.com/embedded-iot/block3/" rel="nofollow ugc">embiq.grapesiot.com/embedded-iot/block3</a> — each section links to its sessions from there. Post questions in this category and tag with the section number (e.g. <code>3.2</code>) so the right people see it.</em></p>
]]></description><link>https://forum.grapesiot.com/topic/68/iot-connectivity</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 13:02:49 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/68.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 11:29:34 GMT</pubDate><ttl>60</ttl></channel></rss>