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

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