ESP32 WiFi Troubleshooting

ESP32 WiFi Troubleshooting

WiFi is what makes the ESP32 valuable for IoT projects — and WiFi issues are what make ESP32 projects frustrating. Most problems have specific, solvable causes. This guide covers every common WiFi issue with the exact fix.

Problem 1: Cannot Connect to Access Point

Check SSID and password first. WiFi credentials in Arduino code are case-sensitive. A trailing space in the password string causes silent authentication failure.

2.4 GHz vs 5 GHz: The ESP32 only supports 2.4 GHz WiFi (802.11 b/g/n). If your router is set to 5 GHz only or to auto-band that the ESP32 cannot see, it will not connect. Enable 2.4 GHz on your router, or create a separate 2.4 GHz SSID.

WPA3 security: Some newer routers default to WPA3. The ESP32 Arduino SDK has limited WPA3 support (improved in newer versions). If connection fails on a new router, try switching to WPA2/WPA2-WPA3 mixed mode.

Hidden SSID: If your router uses a hidden network, specify the SSID explicitly in code and use WiFi.begin(ssid, password, channel, bssid, connect) with the BSSID set.

Problem 2: Connects But Keeps Dropping

Power supply: The most common cause. WiFi transmission draws up to 500 mA peak. A weak supply causes voltage sag, triggering brownout reset. Fix: use 5V/1A+ supply with short, thick cables. Add 100 µF decoupling capacitor on 3.3V rail near ESP32.

Auto light sleep: ESP32 enables WiFi modem sleep by default in Arduino SDK. This can cause connection drops when the modem sleeps between transmissions. Disable for always-connected applications:

WiFi.setSleep(false);

Router lease renewal: Some routers drop DHCP leases after a period. Set a static IP in code or on the router to avoid this.

Reconnect code: Add this to your loop():

if (WiFi.status() != WL_CONNECTED) {
  WiFi.disconnect();
  delay(1000);
  WiFi.begin(ssid, password);
  int attempts = 0;
  while (WiFi.status() != WL_CONNECTED && attempts < 20) {
    delay(500);
    attempts++;
  }
}

Problem 3: WiFi Connects but MQTT/HTTP Fails

WiFi connected (WL_CONNECTED) does not guarantee internet access or DNS resolution. Check:

• Is the router's internet connection working?
• Is DNS working? Test by connecting to a server by IP address instead of hostname.
• Is the server certificate valid? HTTPS requests from ESP32 require certificate verification. Use WiFiClientSecure with certificate fingerprint, or skip verification (less secure) for development.

Problem 4: Slow WiFi Connection Time

Setting a static IP eliminates the DHCP negotiation time (typically 2–5 seconds). Use static IP for deployed sensor nodes that connect on a schedule:

IPAddress ip(192, 168, 1, 100);
IPAddress gateway(192, 168, 1, 1);
IPAddress subnet(255, 255, 255, 0);
IPAddress dns(8, 8, 8, 8);
WiFi.config(ip, gateway, subnet, dns);
WiFi.begin(ssid, password);

Problem 5: Poor WiFi Range

The ESP32 DevKit PCB antenna (the meandering trace on the board edge) has limited range — typically 50–100 m in open space, 10–30 m through walls. For better range:

• Use ESP32-WROOM-32U variant with U.FL external antenna connector — attach a 2.4 GHz dipole antenna.
• Keep the antenna area clear of metal and circuit board copper planes.
• Orient the board so the antenna points toward the router — not parallel to a metal wall.

Useful Diagnostics

Serial.println(WiFi.RSSI()); // signal strength in dBm
// -50 dBm = excellent, -70 dBm = ok, -80 dBm = poor
Serial.println(WiFi.localIP()); // assigned IP address
Serial.println(WiFi.macAddress()); // MAC for router allow-lists

For projects with persistent WiFi issues, consider switching from client WiFi to ESP-NOW (peer-to-peer, no router needed) for the sensor mesh, with a single gateway ESP32 handling the WiFi uplink. Find ESP32 boards at Circuitkar.