📖 What You'll Learn in This Tutorial:

✓ Common WiFi connection issues and their solutions
✓ Understanding the 2.4GHz vs 5GHz limitation (critical!)
✓ How to check WiFi signal strength and improve it
✓ Router settings that affect ESP8266/ESP32/Pico W
✓ Using Serial Monitor to debug WiFi connection problems
✓ Fixing DHCP, IP address, and DNS issues
✓ Step-by-step recovery when your device won't connect

The #1 Mistake: 5GHz WiFi

⚠️ CRITICAL: ESP8266, ESP32, and Pico W ONLY support 2.4GHz WiFi!

This is the most common reason devices won't connect. Modern routers broadcast both 2.4GHz and 5GHz networks, often with the SAME name (band steering). Your microcontroller cannot see 5GHz networks.

How to Fix 5GHz Issues:

Solution	Steps
Separate SSIDs (Best)	Rename 2.4GHz network to "MyWiFi-2.4" and 5GHz to "MyWiFi-5" in router settings
Create IoT Network (Better)	Enable guest network on 2.4GHz only for IoT devices
Use Phone Hotspot (Testing)	Create 2.4GHz hotspot on your phone to test if device works

How to check if your router has band steering:

1. Log into your router (usually 192.168.1.1 or 192.168.0.1)
2. Look for "WiFi Settings" or "Wireless Settings"
3. Check if 2.4GHz and 5GHz have the same network name (SSID)
4. If they are the same, band steering is enabled
5. Change the 2.4GHz network name to something unique (e.g., "HomeWiFi-2G")

Most routers allow separate names. Google your router model + "separate 2.4 and 5GHz".

Understanding Device Status Colors

OceanRemote dashboard shows device status with colored indicators:

Status	Color	Meaning	What To Do
ONLINE	🟢 Green	Device communicated within last 10 seconds	Nothing - it's working!
AWAY	🟡 Yellow	Device hasn't communicated for 10-300 seconds	Check WiFi signal, device may be sleeping or have intermittent connection
OFFLINE	🔴 Red	No communication for over 5 minutes	Device is disconnected - follow troubleshooting steps below

🔧 How Status Works:

Your device polls OceanRemote server every 5 seconds. The server tracks the last poll time:

Last poll < 10 seconds ago → ONLINE (green)
Last poll 10-300 seconds ago → AWAY (yellow)
Last poll > 300 seconds ago → OFFLINE (red)

A yellow "AWAY" status often indicates WiFi interference or distance issues, not complete disconnection.

Using Serial Monitor for Debugging

The Serial Monitor is your best friend for debugging WiFi issues. It shows exactly what your device is doing.

How to Open Serial Monitor:

Open Arduino IDE
Select the correct port (Tools → Port)
Click Tools → Serial Monitor (or Ctrl+Shift+M)
Set baud rate to 115200 (bottom right corner)

What a Successful Connection Looks Like:

########################################
# OceanicRemote v4.4 - ESP8266 D1 Mini #
########################################
[SYSTEM] Device ID: ESP_AABBCCDDEEFF
[WiFi] Connecting to 'MyWiFi'...
[WiFi] Connected! IP: 192.168.1.100
[REG] Registering with server...
[REG] ✓ Registered successfully!
[SESSION] Got session ID: a1b2c3d4e5f6
[SENSOR] DHT22 - Temp: 23.5°C, Hum: 45.2%
....
.... (dots indicate polling every 5 seconds)
....

What a Failed Connection Looks Like:

########################################
# OceanicRemote v4.4 - ESP8266 D1 Mini #
########################################
[SYSTEM] Device ID: ESP_AABBCCDDEEFF
[WiFi] Connecting to 'MyWiFi'...
[WiFi] Failed to connect! (Timeout)
[WiFi] Retrying in 10 seconds...
[WiFi] Connecting to 'MyWiFi'...
[WiFi] Failed to connect! (Timeout)
... (repeats forever)

Common WiFi Problems and Solutions

Problem 1: Device Won't Connect at All (Timeout)

Cause	Solution
Wrong SSID or password	Double-check credentials in generated firmware. WiFi is case-sensitive!
5GHz network (band steering)	Separate 2.4GHz and 5GHz SSIDs in router settings
Hidden SSID	ESP8266/ESP32 have trouble with hidden networks. Make SSID visible.
Special characters in password	Avoid $, !, @, #, % in WiFi passwords. Use letters and numbers only.
MAC address filtering	Add device MAC address to router's allowed list, or disable MAC filtering
Out of range	Move device closer to router (within 5-10 meters / 15-30 feet)

Problem 2: Device Connects but Drops Frequently (AWAY status)

Cause	Solution
Weak WiFi signal	Check RSSI (see below). Move device or add WiFi extender.
Interference (microwave, cordless phone)	Change WiFi channel in router settings (1, 6, or 11 are best)
Too many devices on network	Upgrade router or reduce connected devices
Power supply issues	WiFi draws power spikes. Use a stronger power supply (2A+).
ESP8266 power saving	OceanRemote firmware keeps WiFi active. Check if you modified code.

Problem 3: Device Connects but Won't Register

Serial Monitor shows:
[WiFi] Connected! IP: 192.168.1.100
[REG] Registering...
[REG] Registration failed! (Invalid token)
[REG] Retrying...

Cause	Solution
Token expired (24 hour limit)	Generate new firmware from dashboard (pending devices expire after 24 hours)
Wrong token in firmware	Don't modify the token in generated code. Generate fresh firmware.
Device already claimed by another account	Delete device from old account or generate new firmware with fresh token
Server connectivity issue	Check if your network blocks oceanremote.net (corporate/ school networks)

Problem 4: DNS Resolution Fails

Serial Monitor shows:
[WiFi] Connected! IP: 192.168.1.100
[REG] DNS lookup failed for www.oceanremote.net

Cause: Your router's DNS server isn't responding properly
Solution 1: Reboot your router
Solution 2: Change router DNS to Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1)
Solution 3: Check if your network requires a login page (hotel, airport) - OceanRemote doesn't support captive portals

Checking WiFi Signal Strength (RSSI)

RSSI (Received Signal Strength Indicator) is measured in dBm (decibel-milliwatts). Higher (less negative) is better.

RSSI Value	Signal Quality	Expected Performance
-30 dBm to -50 dBm	Excellent	Perfect connection, no issues
-50 dBm to -60 dBm	Good	Reliable, occasional minor delays
-60 dBm to -70 dBm	Fair	May see AWAY status occasionally
-70 dBm to -80 dBm	Poor	Frequent disconnections, unreliable
Below -80 dBm	Unusable	Device will rarely connect

How to Check RSSI:

Method 1: Add this to your firmware (temporary):
Serial.print("RSSI: ");
Serial.println(WiFi.RSSI());

Method 2: Use a WiFi analyzer app on your phone:
- Android: WiFi Analyzer (farproc)
- iOS: AirPort Utility (Apple)

Method 3: Check your router's connected devices page
- Many routers show signal strength for each client

💡 Improving WiFi Signal:

Move device closer to router (within 5-10 meters / 15-30 feet)
Elevate the device (WiFi signals travel better from higher positions)
Reduce obstacles (walls, metal, water pipes, mirrors block WiFi)
Add a WiFi extender or mesh node
Change router channel to 1, 6, or 11 (least interference)
For ESP32, use external antenna if your board has a U.FL connector

Router Settings to Check

1. WiFi Channel

Overcrowded channels cause interference. Use channels 1, 6, or 11 for 2.4GHz.

How to change WiFi channel:
1. Log into router (192.168.1.1 or 192.168.0.1)
2. Find Wireless Settings or WiFi Settings
3. Look for "Channel" (usually set to Auto)
4. Manually select 1, 6, or 11
5. Save and reboot router

2. Bandwidth (20MHz vs 40MHz)

20MHz is more reliable for IoT devices. 40MHz can cause interference.

Recommended: Set 2.4GHz bandwidth to 20MHz (not 40MHz or Auto)

3. WPA2/WPA3 Compatibility

ESP8266 and older ESP32 may have issues with WPA3. Use WPA2-Personal (AES) for best compatibility.

Recommended: WPA2-Personal (AES)
Not recommended: WPA3, WPA/WPA2 mixed, WEP, Open network

4. DHCP vs Static IP

OceanRemote firmware uses DHCP by default. If you need static IP, you can modify the firmware.

5. Client Isolation

Some routers have "Client Isolation" or "AP Isolation" enabled on guest networks. This prevents devices from talking to each other. Disable it.

Testing with Phone Hotspot

If your device won't connect to your home WiFi, test with a phone hotspot to isolate the problem.

Step-by-Step:

On your phone, enable Personal Hotspot / Mobile Hotspot
Important: Go to hotspot settings and enable "Maximize Compatibility" (forces 2.4GHz)
Note the hotspot name (SSID) and password
Generate new firmware with your hotspot credentials (or edit existing firmware)
Flash and test

Test Results Interpretation:

✅ Device connects to phone hotspot → Problem is your home router/WiFi
❌ Device doesn't connect to phone hotspot → Problem is your device/hardware

🔧 If Phone Hotspot Works:

Your device is fine. The problem is your home WiFi. Check:

2.4GHz vs 5GHz (rename networks separately)
WiFi channel (use 1, 6, or 11)
Bandwidth (set to 20MHz)
Security type (use WPA2-Personal AES)
Signal strength (move device closer)

Power Supply Issues Affecting WiFi

WiFi transmission draws significant current spikes (200-300mA). A weak power supply can cause the device to brown out and reset.

Symptoms of Power-Related WiFi Issues:

Device connects but resets when sending data
WiFi works for a few minutes then stops
Device reboots when relay activates AND WiFi is active
Serial Monitor shows "Brownout detector was triggered" (ESP32)

Solutions:

Use a better USB cable: Many cables are charge-only or have thin wires. Use a quality data cable.
Use a stronger power supply: 5V 2A minimum for ESP32 + relays
Add a capacitor: Place 470-1000μF capacitor across 5V and GND near the board
Separate relay power: Power relays from a separate 5V supply (connect grounds together)

Adding a capacitor to stabilize power:

    ┌─────────────┐
    │   5V from   │
    │   USB       ├──────┬──────► Board 5V
    │             │      │
    │             │     ┌┴┐
    │             │     │ │ 470-1000μF
    │             │     │ │ Electrolytic
    │             │     │ │ Capacitor
    │             │     └┬┘
    │             │      │
    │   GND       ├──────┴──────► Board GND
    └─────────────┘

The capacitor acts as a small battery, providing current during WiFi spikes.

ESP8266/ESP32/Pico W WiFi Recovery Steps

If your device is completely offline and won't reconnect, follow these steps in order:

Step 1: Power Cycle

Unplug the device for 10 seconds
Plug it back in
Wait 1 minute for reconnection
Check dashboard

Step 2: Check Serial Monitor

Connect device to computer via USB
Open Serial Monitor (115200 baud)
Watch the output - it tells you exactly what's wrong

Step 3: Re-flash Firmware

Generate fresh firmware from dashboard
Verify WiFi credentials are correct
Re-flash the device
Test again

Step 4: Test with Different WiFi

Use phone hotspot to isolate the problem
If hotspot works, problem is your home router

Step 5: Factory Reset (ESP8266/ESP32)

In Arduino IDE: Tools → Erase Flash → All Flash Contents
Re-flash OceanRemote firmware

💡 Quick Recovery Sequence:

Power cycle (unplug 10 sec)
Check router (reboot it)
Move device closer to router
Check Serial Monitor for errors
Re-flash firmware with fresh credentials
Test with phone hotspot

Router-Specific Issues

Mesh WiFi Systems (Eero, Google WiFi, Orbi)

Mesh systems often use band steering and may hide 2.4GHz network. Solutions:

Temporarily disable 5GHz during setup (many mesh apps have this option)
Move device very close to main router node
Check if mesh system has an "IoT compatibility mode"
Use a separate 2.4GHz-only access point for IoT devices

Xfinity/Comcast Routers

Xfinity routers have "Band Steering" enabled by default. Fix:

Log into router (10.0.0.1)
Go to Gateway → Connection → WiFi
Edit 2.4GHz and 5GHz settings separately
Give them different names (e.g., "MyWiFi-2.4" and "MyWiFi-5")

Eero

Eero doesn't allow separating SSIDs. Workaround:

Enable "Troubleshooting" → "My device won't connect" in Eero app
This temporarily disables 5GHz for 10 minutes
Connect your device during this window

Google/Nest WiFi

Google WiFi also uses band steering. Workaround:

Open Google Home app
Go to WiFi → Settings → Preferred Activities
Set to "Gaming" (this prioritizes 2.4GHz stability)
Or use a phone hotspot for initial setup

Serial Monitor Error Messages Reference

Error Message	Meaning	Solution
[WiFi] Failed to connect! (Timeout)	Wrong credentials or network not found	Check SSID/password, ensure 2.4GHz network
[REG] Registration failed! (Invalid token)	Token expired or wrong	Generate fresh firmware from dashboard
Brownout detector was triggered	Power supply voltage dropped	Use stronger power supply (5V 2A), better USB cable
ets Jan 8 2013,rst cause:2, boot mode:(3,7)	ESP8266 boot loop	Check GPIO0 and GPIO2 (must be HIGH at boot)
Guru Meditation Error: Core 0 panic'ed	ESP32 crash	Check power supply, re-flash firmware

Prevention: Best Practices for Stable WiFi

Use separate 2.4GHz SSID: Name it something like "HomeWiFi-IoT" to ensure devices connect to correct band
Set static IP in router: Assign fixed IP addresses to your devices (by MAC address) for easier management
Position router centrally: Place router in central location, elevated, away from metal objects
Reduce interference: Keep router away from cordless phones, microwaves, baby monitors, and Bluetooth devices
Update router firmware: Router manufacturers release stability updates regularly
Use quality power supply: 5V 2A minimum for ESP32 + relays, 5V 1A for ESP8266 alone
Add WiFi extender: For devices far from router, use a 2.4GHz WiFi extender
Monitor RSSI: Keep signal strength above -60 dBm for reliable operation

🔧 Network Requirements Summary:

✅ 2.4GHz WiFi (NOT 5GHz)
✅ WPA2-Personal (AES) security (NOT WPA3)
✅ Visible SSID (not hidden)
✅ DHCP enabled (or static IP configured)
✅ Internet access (can reach www.oceanremote.net)
✅ No captive portal (hotel/airport WiFi won't work)

Next Steps

Now that you've learned WiFi troubleshooting, continue with:

Tutorial 30: FAQ and Best Practices
Return to Dashboard: Monitor your devices
Review Tutorial 15: Flashing Firmware to Your Device

🎯 Summary:

The most common WiFi issues are: using 5GHz instead of 2.4GHz (band steering), weak signal strength, and incorrect credentials. Use Serial Monitor to debug, test with phone hotspot to isolate problems, and ensure your power supply is adequate (5V 2A for ESP32 + relays). If your device shows AWAY (yellow) status, check signal strength. If OFFLINE (red), power cycle and re-flash firmware.

Tutorial 29: WiFi Connection Troubleshooting