ESP32 WiFi reason 200: BEACON_TIMEOUT
A connected ESP32 listens for its access point's beacons. When it misses them for too long and the access point does not answer five probe requests either, it disconnects with reason 200.
WIFI_REASON_BEACON_TIMEOUT (200). Espressif's description: Beacon timeout.
The usual causes
- A weak or noisy signal: distance, walls, metal enclosures, the device moved. Watch the RSSI over time; a slow drop before each disconnect points here.
- The access point restarted or changed channel.
- The antenna: a module with a PCB antenna placed against metal or a ground plane, or a board with an external antenna connector and no antenna on it.
Handle it
Reason 200 is normal now and then. What matters is that the firmware reconnects: call esp_wifi_connect() on WIFI_EVENT_STA_DISCONNECTED, as Espressif recommends, with a growing delay between tries. The time it waits for beacons can be changed with esp_wifi_set_inactive_time().
Where you see the number
In ESP-IDF, the WIFI_EVENT_STA_DISCONNECTED event carries it: ((wifi_event_sta_disconnected_t *) event_data)->reason. In Arduino, the ARDUINO_EVENT_WIFI_STA_DISCONNECTED event has it in info.wifi_sta_disconnected.reason, and WiFi.disconnectReasonName() turns it into a name. Log it every time: the reason is what separates a wrong password from a weak signal.
When it happens at a customer's site
On your desk you see the reason in the log. On a device behind someone else's router you only hear that it "goes offline sometimes". Pinscope keeps the device's logs and its WiFi signal over time, so you can see which reason it disconnected with and whether the signal was dropping before it did. Free for three devices. Remote logging.
Related errors: WiFi reason 8: ASSOC_LEAVE · WiFi reason 2: AUTH_EXPIRE · WiFi reason 15 / 204: handshake timeout · WiFi disconnect reasons. All ESP32 errors: the list. Reason codes and their meaning from Espressif's Wi-Fi Driver guide and esp_wifi_types.h.
More
- Remote access to an ESP32 without TLS: what it measured and what it costs
- Reaching an ESP32 web server from outside its network
- Updating ESP32 firmware over the internet, with rollback
- Guru Meditation Error: decoding the backtrace, and crashes from the field
- Remote logging: ESP_LOG without a serial cable
- Heap and stack monitoring in the field
- An ESP32 behind CGNAT, 4G or Starlink
- TLS memory usage on the ESP32, and how to reduce it
- Sharing an ESP32 sensor page with anyone, without port forwarding
- ArduinoOTA over the internet, with a rollback
- ESP32 remote access compared: port forwarding, ngrok, Cloudflare Tunnel, Tailscale
- esp_http_server slow? The 250 ms delay and the fix
- Before the first ESP32 ships: a field support checklist
- ESP32 exception decoder: a Guru Meditation backtrace to lines, in the browser