Next-level WiFi handling on ESP32 starts with the conversion from status-driven to event-driven structures.
Espressif themselves put 'events' right at the top of their API documentation. Background reconnections are driven by events.
In the end, there are only two events we care about - getting the connection and losing the connection.
But the logging of everything proves valuable information in the meantime.
And, ultimately, events are what we want to use to monitor our connection state.
For more on "All Things IoT" — 🔔 *Subscribe* (hardware, firmware, connectivity, cloud computing, and dev toolkit)
🛠️ *What You'll Learn In This Video:* - How to use events to signal the state of your WiFi connection - How to use events to log your connection status in detail
⏱️ *Chapters:* 0:00 - Intro & Today's Plan 3:15 - Set Up WiFi for Diagnostics 4:39 - Put it in a Library 9:57 - Log Status Codes 12:12 - Introduce and Log Events 16:16 - Introduce and Log Disconnect Reasons 19:01 - Set the Stage for More 21:44 - Wrap It Up