this is the output on the serial after the restart
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[I][wifi:286]: WiFi Connecting to 'Sweet_Spot_IoT'...
[W][wifi_esp32:458]: Event: Disconnected ssid='Sweet_Spot_IoT' bssid=88:B1:E1:2D:12:F2 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[I][wifi:286]: WiFi Connecting to 'Sweet_Spot_IoT'...
[W][wifi_esp32:458]: Event: Disconnected ssid='Sweet_Spot_IoT' bssid=88:B1:E1:2D:12:F2 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[I][wifi:286]: WiFi Connecting to 'Sweet_Spot_IoT'...
[W][wifi_esp32:458]: Event: Disconnected ssid='Sweet_Spot_IoT' bssid=88:B1:E1:2D:12:F2 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[I][wifi:286]: WiFi Connecting to 'Sweet_Spot_IoT'...
I also have the ability to scan the ring buffer on my APs for the client itself and any probes its making, and the MAC that is showing when I erase the chip using esptool is either not the mac it uses in the airspace, or my APs arenβt hearing a packet come out of it. This is looking like a driver issue or something at a much lower level than configuration.
I even tried an ancient (2006) Netgear 802.11g AP. Single SSID basic WPA2 PSK all the same error, and I canβt see anything coming out of the chip in airspace at all. no probes or anything. Something is broken in this things 802.11 it seems. I have also powered it using my benchtop power supply at 3.45v with 10a available on the 3.3v pins. So power is not the issue.
[I][wifi:500]: - 'I'm a rogue 2' (00:14:6C:C6:BE:F1) ββββ
[D][wifi:501]: Channel: 11
[D][wifi:502]: RSSI: -79 dB
[D][wifi:505]: - 'Sweet_Spot_IoT' (88:B1:E1:29:EB:61) ββββ
[D][wifi:505]: - 'Sweet Spot' (30:86:2D:B0:70:90) ββββ
[D][wifi:505]: - 'Sweet_Spot_IoT' (30:86:2D:B0:70:91) ββββ
[D][wifi:505]: - 'Sweet Spot' (88:B1:E1:29:EB:60) ββββ
[D][wifi:505]: - 'Sweet_Spot_IoT' (88:B1:E1:2D:12:F2) ββββ
[D][wifi:505]: - 'Rogue AP' (00:14:6C:C6:BE:F0) ββββ
[D][wifi:505]: - 'Rogue'n around' (00:14:6C:C6:BE:F2) ββββ
[I][wifi:286]: WiFi Connecting to 'I'm a rogue 2'...
[W][wifi_esp32:458]: Event: Disconnected ssid='I'm a rogue 2' bssid=00:14:6C:C6:BE:F1 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[I][wifi:286]: WiFi Connecting to 'I'm a rogue 2'...
[W][wifi_esp32:458]: Event: Disconnected ssid='I'm a rogue 2' bssid=00:14:6C:C6:BE:F1 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[D][wifi:441]: Starting scan...
[D][wifi:456]: Found networks:
[I][wifi:500]: - 'I'm a rogue 2' (00:14:6C:C6:BE:F1) ββββ
[D][wifi:501]: Channel: 11
[D][wifi:502]: RSSI: -78 dB
[D][wifi:505]: - 'Sweet Spot' (88:B1:E1:29:EB:60) ββββ
[D][wifi:505]: - 'Sweet_Spot_IoT' (88:B1:E1:29:EB:61) ββββ
[D][wifi:505]: - 'Sweet Spot' (30:86:2D:B0:70:90) ββββ
[D][wifi:505]: - 'Sweet_Spot_IoT' (30:86:2D:B0:70:91) ββββ
[D][wifi:505]: - 'Sweet_Spot_IoT' (88:B1:E1:2D:12:F2) ββββ
[D][wifi:505]: - 'Rogue AP' (00:14:6C:C6:BE:F0) ββββ
[D][wifi:505]: - 'Rogue'n around' (00:14:6C:C6:BE:F2) ββββ
[I][wifi:286]: WiFi Connecting to 'I'm a rogue 2'...
[W][wifi_esp32:458]: Event: Disconnected ssid='I'm a rogue 2' bssid=00:14:6C:C6:BE:F1 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
[I][wifi:286]: WiFi Connecting to 'I'm a rogue 2'...
[W][wifi_esp32:458]: Event: Disconnected ssid='I'm a rogue 2' bssid=00:14:6C:C6:BE:F1 reason='Auth Expired'
[W][wifi:604]: Error while connecting to network.
[W][wifi:640]: Restarting WiFi adapter...
Having 2 similar D1 mini ESP32s here. One works like a charm (less ble_tracker issues), the other cannot connect to wifi. Same config uploaded via USB.
Extra 1000uF on the 3.3V did not help. Nothing attached.
with software: ESPHome-Flasher-1.4.0-Windows-x64.exe i flashed BOTH with the SAME firmare one of this i have problem with connection to wifi with
reason=βAuth Expiredβ
So i think that this is an hardware problem (one modem only the same distance to the modem with both ESP32).
Now i try to contact the manufacturer
I found this thread looking for the same kind of βauth expiredβ problem.
I had two ESP32 devices (listed on Ali as βESP32 TYPE-C USB CH340C CP2102 WiFi+Bluetooth Ultra-Low Power Dual Core ESP32-DevKitC-32 ESP-WROOM-32 Expansion Boardβ).
Neither worked with my config, so I suspected Iβd made a mistake.
I switched to a different type of ESP (micro USB instead of USB-C if that matters), and it worked fine.
I then installed WLED on the two non-working ESPs and it installed but could not connect to my network.
I will now contact the seller for a refund on my devices that seem like duds.
Hi, did you get this working?
I have the same situation where after programming using the esphome run xyz.yaml tool (DEBUG on) Wifi connects instantly and everything works fine. Then breaking that link and linking using cutecom it just sits and βAuth Expiredβ the whole time.
What is weird is going back to using esphome logs xyz.yaml and pressing the modules reset button, Wifi works again.
None of the settings in this thread worked sofar.
Tried that, and it did not resolve my ESP32 connection issues. Tried switching from WPA2-Personal to WPA2/WPA3-Personal (it appears to be a newer option) but itβs not helping. Last option is to disable the logger: section as noted above. No, that did not resolve it, either. Quite aggravating.
The blame for the aggravation rests solely with the module/board/ESP32 manufacturer. Two of three ESP32-S3-WROOM-1 boards in a single purchase were BAD. The first would not register correctly with USB, failing to provide a valid Device Descriptor. The second would not connect via WiFi no matter what was attempted. Only the third would actually load and connect.
After struggling with this for a week I finally solved my issue. I popped the shield off the esp module and it looked awful. The solder paste didnβt look like it had melted all the way and components were askew. I reflowed the board, put the shield back on and I get a fast and reliable connection now.
I had a similar problem with an ESP32-CAM board. The issue turned out to be the power regulation on the ESP32-CAM-MB. When I directly connected the ESP board the issue went away.