ESP32 Common Problems & Solutions: Complete Troubleshooting FAQ

Solution:

1. Check the USB cable – Many cables are charge-only! Use a data cable.
2. Install drivers – CP210x or CH340 drivers depending on your board:
   • CP210x: Download from Silicon Labs
   • CH340: CH340 drivers
3. Try a different USB port – Avoid USB hubs.
4. Restart your computer – After driver installation.
5. Check Device Manager (Windows) – Look for "Unknown Device" or under "Ports (COM & LPT)".
6. Try another ESP32 board – Your board might be faulty.

Solution:

1. Hold the BOOT button while uploading (then release after upload starts)
2. Check your USB cable – Use a high-quality shielded cable
3. Reduce upload speed – In Arduino IDE: Tools → Upload Speed → 115200 instead of 921600
4. Try a different USB port – Direct to computer, not through hub
5. Check power supply – ESP32 needs stable 5V with 500mA minimum

Solution:

1. Press and hold the BOOT button on your ESP32
2. While holding BOOT, click Upload in Arduino IDE
3. When you see "Connecting..." in the console, release the BOOT button
4. If that doesn't work, try: Hold BOOT → Press EN/RESET → Release EN → Release BOOT

Solution:

1. Check baud rate – Make sure Serial Monitor matches your code's Serial.begin(115200)
2. Try different baud rates – 9600, 115200, 230400, 460800
3. Check power supply – Low power can cause serial corruption
4. Check grounding – ESP32 and computer must share common ground

Solution:

1. Select the correct board: Tools → Board → ESP32 Dev Module
2. Select correct COM port
3. Try different USB cable
4. Press BOOT button during upload (see above)
5. Lower upload speed to 115200

Solution:

1. Optimize your code – Remove unused libraries, combine variables
2. Use PROGMEM – Store large strings in flash instead of RAM
3. Choose a board with more flash – Some ESP32 boards have 16MB flash
4. Enable optimization – Tools → Optimization → "Smallest Code"
5. Use Partition Scheme – Tools → Partition Scheme → "Huge App (3MB No OTA)"

Solution:

1. Install ESP32 board support: File → Preferences → Additional Boards Manager URLs
2. Add URL: https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json
3. Tools → Board → Boards Manager → Search "ESP32" → Install
4. Select Tools → Board → ESP32 Arduino → ESP32 Dev Module
5. Restart Arduino IDE

Solution:

1. Check which library is being used in the console output
2. Delete duplicate libraries from your Arduino/libraries folder
3. Keep only the most recent or most compatible version
4. For OceanRemote, ensure you have the correct library version

Solution:

1. Check SSID and password – Case-sensitive!
2. Check WiFi frequency – ESP32 only supports 2.4GHz, not 5GHz
3. Move ESP32 closer to router – Weak signal causes connection failures
4. Check special characters – Avoid spaces or symbols in SSID/password
5. Restart router – Sometimes the router's DHCP table is full
6. Try static IP – Some routers have DHCP issues
7. Check antenna connection – If using external antenna, ensure it's connected

Solution:

1. Check power supply – WiFi draws bursts of 300-400mA!
2. Add delay between reconnection attempts – Don't hammer the router
3. Enable WiFi auto-reconnect: WiFi.setAutoReconnect(true);
4. Check for interference – Microwaves, baby monitors, neighbors' WiFi
5. Update ESP32 board package – Newer versions have better WiFi stability
6. Try a different WiFi channel – In router settings (channels 1, 6, 11 are best)

Solution:

1. Restart your router – DHCP table might be full
2. Assign a static IP – Bypasses DHCP entirely
3. Check MAC address filtering – Your router might be blocking the ESP32
4. Reduce number of connected devices – Some routers limit to 10-15 devices

// Static IP example
IPAddress local_IP(192, 168, 1, 200);
IPAddress gateway(192, 168, 1, 1);
IPAddress subnet(255, 255, 255, 0);
WiFi.config(local_IP, gateway, subnet);

Solution:

1. Avoid input-only pins – GPIO 34-39 are input-only (no output)
2. Avoid strapping pins at boot – GPIO 0, 2, 5, 12, 15 affect boot mode
3. Check if pin is used internally – Some boards use GPIO 16/17 for PSRAM
4. Test with simple blink code – Isolate the problem
5. Check voltage levels – ESP32 is 3.3V, not 5V tolerant on most pins

Solution:

1. Avoid pulling GPIO 0 LOW at boot – GPIO 0 LOW = download mode
2. Avoid pulling GPIO 2 LOW at boot – Affects boot behavior
3. Avoid pulling GPIO 15 HIGH at boot – Affects boot output
4. Add pull-up/down resistors correctly – 10kΩ recommended
5. Remove any components on GPIO 0, 2, 5, 12, 15 during boot

Solution:

1. Use ADC attenuation – analogReadResolution(11); analogSetAttenuation(ADC_11db);
2. Add a capacitor – 0.1µF between ADC pin and GND reduces noise
3. Average multiple readings – Take 10-50 samples and average them
4. Use ADC2 pins carefully – ADC2 is shared with WiFi (use ADC1 for WiFi projects)
5. Calibrate your ADC – Measure known voltages to create a calibration curve

Solution:

1. Use a better power supply – ESP32 needs 5V with 500mA minimum, 1A recommended
2. Use a USB power bank – Computer USB ports often provide only 500mA
3. Add a large capacitor – 470-1000µF between 5V and GND
4. Check your wiring – Thin wires cause voltage drop
5. Power sensors separately – Don't draw power for sensors from ESP32's 3.3V pin
6. Disable brownout detector – (Not recommended, but possible in code)

Solution:

1. Check power supply – Most common cause of random resets
2. Check for watchdog timer – Add delay() or yield() in long loops
3. Check for stack overflow – Reduce recursive functions or large local arrays
4. Check for NULL pointer dereference – Always check pointers before using
5. Add ESP32 exception decoder – Use esp_exception_decoder library

Solution:

1. Check battery voltage – ESP32 needs 3.0V-3.6V (or 5V via USB)
2. Use a voltage regulator – 3.7V Li-ion needs regulator to 3.3V
3. Check battery capacity – ESP32 draws 80-240mA, small batteries won't last
4. Use deep sleep – Reduce power consumption dramatically
5. Check for voltage drop – Thin wires cause voltage drop under load

Solution:

1. Add 10kΩ pull-up resistor – Between DATA and VCC (3.3V)
2. Check wiring – VCC to 3.3V, DATA to GPIO, GND to GND
3. Wait 2 seconds between readings – DHT22 needs 2 seconds minimum
4. Check library version – Use Adafruit DHT sensor library
5. Test with example code – Isolate the sensor from your main code
6. Replace sensor – DHT22 can be damaged by moisture or voltage spikes

Solution:

1. Add 4.7kΩ pull-up resistor – Between VCC and DATA (critical!)
2. Check wiring – Red=VCC, Yellow=DATA, Black=GND
3. Check OneWire address – Use scanner sketch to find address
4. Check cable length – Long cables (>10m) need stronger pull-up
5. Check if sensor is connected to correct pin – Verify in code

Solution:

1. Check power supply – Sensor needs stable voltage
2. Add decoupling capacitor – 0.1µF between VCC and GND near sensor
3. Check for electrical noise – Keep sensor wires away from high-current lines
4. Calibrate the sensor – Compare with known reference
5. Check for self-heating – Power sensor only when reading (for some sensors)
6. Average multiple readings – Take 5-10 readings, discard outliers, average

Solution:

1. Remove unused libraries – Each library adds memory overhead
2. Use F() macro for strings – Serial.println(F("Long string")); stores in flash
3. Use PROGMEM for constants – Store lookup tables in flash
4. Reduce global variables – Move to local scope when possible
5. Choose larger partition scheme – Tools → Partition Scheme → "Huge App"
6. Switch to ESP32 with PSRAM – Some boards have 4-8MB extra RAM

Solution:

1. Check for long delays – Use millis() instead of delay() for timing
2. Check CPU frequency – Tools → CPU Frequency → 240MHz (not 80MHz)
3. Use both cores – Run WiFi on core 0, sensors on core 1
4. Reduce Serial.print() statements – Serial communication is slow
5. Optimize loops – Move calculations outside loops

Solution:

1. Check board compatibility – ESP32-S2 has no Bluetooth! Only original ESP32, S3, C3
2. Add Bluetooth name – esp_bt_dev_set_device_name("MyESP32");
3. Check Bluetooth stack initialization – Must be before WiFi if using both
4. Try different Bluetooth library – ESP32 BLE Arduino vs classic Bluetooth
5. Check distance – Bluetooth range is ~10 meters

Solution:

1. Use different antenna – Both WiFi and Bluetooth share same antenna
2. Use dual-core properly – Run WiFi on core 0, Bluetooth on core 1
3. Reduce WiFi power – WiFi.setTxPower(WIFI_POWER_8_5dBm);
4. Use BLE instead of Classic Bluetooth – BLE interferes less with WiFi
5. Time-slice between WiFi and Bluetooth – Alternate operations