Demo-grade code connects once in setup() and works until the first router reboot. Production devices must detect drops, back off politely and recover automatically, for months. The difference is about twenty lines of pattern.
At a glance: 7 minute guide · part 3 of 10 in the complete IoT and ESP32 guide track · includes a worked example and a quick-reference table.
Detect and report state
Here is the working theory in one pass. WiFi. status() tells you the truth: WL_CONNECTED, WL_IDLE_STATUS, WL_DISCONNECTED. Log transitions with millis() timestamps intermittent issues become readable history instead of vibes. An LED or MQTT LWT topic reports health without SSH.
| F | a | i | l | u | r | e | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| S | y | m | p | t | o | m | ||||
| F | i | x | p | a | t | t | e | r | n | |
| Router reboot | WL_DISCONNECTED loop | Timed retry with backoff | ||||||||
| Dead spot | Weak RSSI, drops | RSSI logging + antenna/site change | ||||||||
| Sleep wake | No auto re-associate | Explicit reconnect after wake | ||||||||
| Radio stall | status stuck | WiFi.disconnect + restart radio | ||||||||
| Credential change | Auth fail | Fallback config portal |
Reconnect with backoff
Attempt reconnection every few seconds, then stretch the interval (5 s → 15 s → 60 s) so a dead network is not hammered. Reset the backoff on success. WiFi. reconnect() is gentler than begin() from scratch and preserves credentials flow.
Survive the edge cases
After deep sleep, re-associate explicitly before using sockets. On brownout recovery, validate that the radio actually re-initialised. And design the application layer to queue data during outages reconnection is useless if sensor history is lost while offline.
How to apply this in your build
Work through the sequence below each step assumes the previous one passed. For numbers that need calculating, the linked tools at the end of this guide do the arithmetic instantly.
- Track status changes with timestamps in a ring buffer
- Retry on a backoff schedule, resetting after success
- Reconnect explicitly after every deep-sleep wake
- Queue telemetry while offline and flush on reconnect
Worked example
A garage sensor dropped for hours because reconnect hammered every 200 ms and the router throttled it. Backoff to 60 s reconnected in one cycle after the router rebooted and stopped the lockout entirely. Run the numbers yourself with the Battery Life Calculator and the result should agree to within rounding.
Practical note from the bench. Every Procirel IoT sketch ships with the same skeleton: status ring-buffer, backoff reconnect, offline queue. Copy it between projects verbatim.
Pitfalls that cost real hardware
- Calling begin() in a tight loop credential re-read hammers flash
- Blocking loop() while disconnected, freezing local logic
- Ignoring WiFi events (SYSTEM_EVENT_STA_DISCONNECTED) that make state machines clean
Key takeaways
- Detect and report state the foundation of this guide; revisit it if any measurement here surprises you.
- Reconnect with backoff the foundation of this guide; revisit it if any measurement here surprises you.
- Survive the edge cases the foundation of this guide; revisit it if any measurement here surprises you.
Who this guide is for
Beginners get a single focused topic instead of a whole textbook chapter. It works as an early stop in the complete IoT and ESP32 guide path. Intermediate readers use it as a reference the table, the worked example and the mistake list answer the questions that come up mid-build. If you teach, the structure (theory, application, example, failure modes) maps cleanly onto a lab session.
What you need before starting
Nothing exotic: the parts or tools named in the guide, a multimeter. The Battery Life Calculator open in a tab. Track status changes with timestamps in a ring buffer before you begin the guide assumes it and keep the quick-reference table above within sight while you work through the steps.
Quick reference card
| Aspect | Where to find it in this guide |
|---|---|
| Core theory | Detect and report state |
| Application steps | How to apply this in your build |
| Worked numbers | Worked example |
| Failure modes | Pitfalls that cost real hardware |
How this fits the complete IoT and ESP32 guide track
This guide is one stop in the structured learning path. Start from the complete IoT and ESP32 guide complete guide for the full map, or continue with MQTT protocol basics and Home Assistant MQTT integration. For the arithmetic, open the Battery Life Calculator.
Frequently asked questions
How do I know reconnection works before deployment? Pull the router power mid-run: the log should show drop, backoff attempts, and recovery repeat ten times.
What is MQTT LWT? Last Will and Testament the broker publishes an "offline" message when the device drops, giving observers instant status.
Is there a calculator for this? Yes the Battery Life Calculator tool runs the formulas from this guide instantly, client-side, with no signup.
Related guides and tools
- The complete iot, sensors & esp32 guide: IoT, Sensors & ESP32 complete guide
- Read next: lorawan for beginners: long-range iot without wifi
- Also in this track: antenna basics for iot: wavelength, gain and matching
- Continue with: biomedical sensors: how wearables measure the body
- Calculate as you go: battery life estimator · LM317 regulator designer · wire gauge checker
- From here, the natural continuation is the next guide in the track index. It assumes exactly the vocabulary this page built and adds the next layer of practice.
Verification routine
The fastest way to internalise this topic is to change one variable deliberately and predict the result before measuring. Wrong predictions are the curriculum, they show exactly which mental model needs revisiting, and the bench grades honestly.
Component substitution is a legitimate experiment as long as it is deliberate. Swap one part, predict the effect, measure, and record. That single habit converts a parts bin into a teaching lab and makes every future guide in this track faster to absorb.
Formulas and checks from this guide
Verification checklist for this track: watch RSSI before blaming code, measure supply current during radio bursts. Confirm MQTT topics against the broker log. Wireless bugs are usually power or signal problems wearing a software disguise.
Bookmark this page against your next build in the track. The checklist above is the same one used across 23 guides in this series.
Notes from the bench
Location, then device, then measurement. Document the tree before flashing the first device.
Measure current during transmit bursts. Sags under load are power problems, no firmware fixes those.
Extended Application Notes
This section expands the practical application of esp32 wifi that never dies: reconnection strategies beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.
Failure Analysis in Depth
The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. Calling begin() in a tight loop credential re-read hammers flash Blocking loop() while disconnected, freezing local logic Ignoring WiFi events (SYSTEM_EVENT_STA_DISCONNECTED) that make state machines clean. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.
Pre-Build Checklist
Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.
What Comes Next
Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.
Theory in Practice, Extended
The theory section of esp32 wifi that never dies: reconnection strategies deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.
Component Sourcing and Substitution Notes
Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.
Instrumentation for This Design
Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.
Documentation Template for This Build
Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.
Last updated 23 August 2026