-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32-C3 can not connect to WiFi AP (AUTH_EXPIRE) #6767
Comments
Full output from serial monitor: Connecting to [my SSID] [...] |
@PilnyTomas, PTAL - Thanks! |
Hi @XFer012, could you please get the signal strength of the AP you are trying to connect to? |
Sure, here it's the output from WiFiScan: scan done |
@PilnyTomas @XFer012 We have only troubles with the Lolin C3-Mini and Tasmota. Every! other C3 board does work well. After we modified the HF part of the board we got it going more or less good. There is "somewhere" a bug in the HF board design. |
You mean all Lolin-C3 you tested scan OK, correctly detect RSSI, but cannot connect with an "AUTH_EXPIRE" error? |
@XFer012 Either this or some even did not found a AP. |
@Jason2866 is right, there is a flaw in the design. You need to set the transmit power to -8.5db right after wifi.begin then it will connect. If using the softAP, you need to set it after starting also.
|
The antenna matching is not correct. So the HF signal gets reflected. A really bad workaround is to reduce transmit power so the reflecting is reduced and does not eliminate the (weak) signal completly. A real fix needs changes in the HF matching network. |
Yes, it's a bad workaround and although it eliminates the AUTH_EXPIRE response it's deceiving because the board's RX'd signal will be much greater than the TX range. I bought a bunch of these boards when they first came out and have used many successfully but only within ~10 meters of the AP, after that RX strength is still pretty good but too many dropped packets on the TX end. I only use them now with SoftAP as it only needs to transmit to a mobile phone which is usually within a few meters of the device. Hoping they improve the design and release an updated version of the board. |
Thank you, I will try this workaround. Better than nothing! |
Confirmed working. Thanks! |
Closing as solved, if needed, you can reopen the issue. |
Hi. |
That workaround also worked for me! |
Thank you! it worked perfectly :) |
Had the same problem and after trying MULTIPLE HW changes like adding capacitors, diodes to boost 3.3v to 3.4v, and modifying the smd wifi antenna I decided to try all esp32c3 super mini boards from a batch of 10 I bought and found out that 4 out of 10 where unable to connect to wifi reporting error AUTH_EXPIRE. Exactly the same sketch (wifi tx power 8.5db) for all of them. My conclusion is the manufacturer doesnt chack for defectives and sells all of them. Dont know what other issues can arise. Hope this helps (to discard the broken ones). |
@totial You are right. There are bad designed (defective) C3 out there and sold. |
This solved my issue! I was going at it for hours and could not for the life of me figure out why it wasn't connecting! |
From espressif/arduino-esp32#6767 (comment) to ensure the board can connect to WiFi
Thank you so much, this solved a weeks worth of useless messing around in code! Confirmed working on ESP32-S3 Devkit with ESP32-S3-WROOM-1 |
@DansDesigns First time i hear about issues with S3 in "classic" devkit form factor. |
Board
Lolin C3-Mini
Device Description
Lolin C3-Mini alone, nothing connected
Hardware Configuration
Nothing
Version
v2.0.3
IDE Name
Arduino IDE 1.8.19
Operating System
Windows 10 Pro 64 bit
Flash frequency
80 MHz
PSRAM enabled
no
Upload speed
921600
Description
ESP32-C3 can not connect to my AccessPoint, while ESP32 "stock" (ESP32 Devkit board) connects without issues
C3 reports continously "[W][WiFiGeneric.cpp:873] _eventCallback(): Reason: 2 - AUTH_EXPIRE"
Sketch
Debug Message
Other Steps to Reproduce
I also tried ESP32 Devkit board, same AP, same parameters, same position; works without issues
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: