Device Offline in Dashboard

Your OceanRemote device shows as OFFLINE in the dashboard. The device is not communicating with the server. This guide covers WiFi connection issues, power problems, token expiry, server connectivity, and hardware failures.

Last updated: April 22, 2026 | 12 min read

Symptoms

• Dashboard shows OFFLINE status for device
• Device LED is on but not responding to commands
• Serial Monitor shows no output or connection errors
• Device worked before but suddenly went offline
• Other devices work fine, only specific device offline
• Device appears in "Pending Devices" but never goes online
• Device reconnects briefly then goes offline again

Common Causes

1. No Power to Device Device not powered, loose USB cable, or dead battery
2. WiFi Disconnected Router issue, wrong credentials, or 5GHz network
3. Registration Token Expired Token older than 24 hours, never used
4. Token Already Used Same firmware flashed to multiple devices
5. Server Connection Blocked Firewall or network blocking HTTPS to www.oceanremote.net
6. Device ID Mismatch MAC address changed or EEPROM corrupted
7. Hardware Failure Damaged ESP32/ESP8266 or voltage regulator

Device Connection Flow

1. Device powers on
         
         
2. Connects to WiFi 
         
          WiFi fails  Check credentials, signal, 2.4GHz band
         
         
3. Loads permanent token from EEPROM
         
          Token missing  Go to registration flow
         
         
4. Requests session from /api/device/state/
         
          401/410  Token invalid, re-register
          200 OK  Session created
         
         
5. Device appears ONLINE in dashboard
         
         
6. Polls every 3 seconds to stay online

Step-by-Step Fixes

1. Check Device Power

No power = no connection:

• Check if LED on device is lit
• Try different USB cable
• Try different USB port or power source
• If using battery, check charge level
• Measure voltage at 5V and 3.3V pins with multimeter
• For ESP8266/ESP32, 3.3V should be stable between 3.0V-3.3V

2. Open Serial Monitor

See what the device is actually doing:

• Connect device via USB
• Open Arduino IDE Serial Monitor
• Press RESET button on device
• Watch for error messages:

//  GOOD - Device connecting normally:
// [WiFi] Connecting... Connected!
// [WiFi] IP Address: 192.168.1.100
// [SESSION] Got session ID: a1b2c3d4
// [INFO] Device ONLINE

//  WiFi FAILURE - Check credentials, 2.4GHz:
// [WiFi] Connecting... Failed!
// [WiFi] Connection lost! Status: 0

//  TOKEN FAILURE - Generate new firmware:
// [REG] HTTP Response: 401
// [REG] Token already used or expired

//  NO OUTPUT - Check power, USB cable, or device may be dead

3. Check WiFi Credentials

Wrong credentials = no connection:

• Verify SSID and password in firmware
• Ensure network is 2.4GHz
• Check for spaces at beginning or end of SSID/password
• Test with mobile hotspot to isolate router issues
• If using special characters, try simpler password temporarily

4. Generate Fresh Firmware

Expired or used token is common:

• Go to OceanRemote dashboard "Your Device" page
• Click "Generate New Code"
• Copy the new firmware code
• Flash to device within 24 hours
• Device should register and appear online

5. Clear EEPROM and Re-flash

Corrupted token in EEPROM prevents connection:

// Upload this temporary code to clear EEPROM
#include <EEPROM.h>

void setup() {
  Serial.begin;
  EEPROM.begin;
  
  // Clear all EEPROM
  for  {
    EEPROM.write;
  }
  EEPROM.commit();
  
  Serial.println;
}

void loop() {}

// After running:
// 1. Remove this code from Arduino IDE
// 2. Generate fresh firmware from OceanRemote
// 3. Flash normal firmware
// 4. Device should register as new device

6. Check Router and Network

Network issues can block connection:

• Restart router
• Check if other devices can connect to same WiFi
• Ensure router has available DHCP leases
• Check if router firewall is blocking outbound HTTPS
• Try connecting device to mobile hotspot to isolate router issue

7. Check Device Hardware

Hardware failure may be the cause:

• Try uploading a simple Blink sketch to verify hardware works
• If Blink fails to upload, USB-serial chip may be damaged
• Check for burnt components or swollen capacitors
• Try different ESP32/ESP8266 board if available
• If device was working and suddenly died, power surge may have damaged it

Serial Monitor Error Messages Reference

Message	Meaning	Solution
[WiFi] Connecting... Failed!	WiFi credentials wrong or network not found	Check SSID/password, ensure 2.4GHz
[WiFi] Connection lost! Status: 0	WiFi disconnected	Move closer to router, check power supply
[REG] HTTP Response: 401	Token expired or invalid	Generate fresh firmware within 24 hours
[REG] HTTP Response: 410	Token already used	Generate new firmware
[SESSION] Token invalid - will re-register	Permanent token corrupted or revoked	Clear EEPROM, generate fresh firmware
Brownout detector was triggered	Power supply voltage dropped	Add 470-1000F capacitor, upgrade power supply
wdt reset ()	Watchdog timeout, code blocked	Add yield() in loops, reduce delay()

Prevention Tips

• Always flash firmware within 24 hours of generation
• Use quality 5V 2A power supply with 470-1000F capacitor
• Ensure 2.4GHz WiFi network
• Keep device within range of router
• Save generated firmware code in text file for backup
• Monitor Serial Monitor after flash to verify registration
• Add WiFi auto-reconnect logic

Related Issues

• Device Away Status Explained
• Firmware Flash Success But No Connection
• Token Invalid or Expired
• ESP32 Not Connecting to WiFi

Frequently Asked Questions

Still having offline issues? Contact Support or return to the Troubleshooting Hub.