ESP32 WiFi reason 15 and 204: handshake timeout

The ESP32 found the network and started the WPA handshake, but it did not complete. Espressif names two causes: a wrong password, and a signal too weak.

WIFI_REASON_4WAY_HANDSHAKE_TIMEOUT (15), WIFI_REASON_HANDSHAKE_TIMEOUT (204). Espressif's description: 4-way handshake timeout. Handshake timeout.

The two are the same failure: ESP-IDF reports 4-way handshake timeouts as 204 for legacy reasons, and passes 15 on when the access point sends it.

The usual causes

Tell them apart

If it fails every time right after boot, start with the password. If it connects most of the time and fails at the edge of coverage, it is the signal. A device that connected for weeks and starts failing after a router change usually has a password or security mode that no longer matches.

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 201: NO_AP_FOUND · WiFi reason 202: AUTH_FAIL · WiFi reason 200: BEACON_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