-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
WIFI STA and AP Connection Issue (SDK 5.3.2) (IDFGH-14297) #15088
Comments
hi @varram-bdh could you share your router setting page? I want to confirm th settings, and could you tell me you specific router brand? |
hi @Xiehanxin The router currently causing the issue is provided by SK Telecom in Korea. I will update the page soon. |
As an additional update, I found that the event handler is generating an ID of 43. This is not documented anywhere. |
@Xiehanxin |
@Xiehanxin hi. |
@varram-bdh 32-wifi-lib.zip |
@varram-bdh Any update regarding #15088 (comment) |
Answers checklist.
IDF version.
V5.3.2
Espressif SoC revision.
ESP32-WROOM-32
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
ESP32-WROOM-32
Power Supply used.
External 3.3V
What is the expected behavior?
There is an issue with connecting in STATION mode to a specific AP.
Currently, there are no problems with other APs except for this particular one. While the AP itself might be suspected, all other devices I own, except for the ESP32, connect to the AP without any issues.
I don't think there is an issue with the AP itself.
Additionally, there are no problems when using programs developed with ESP32 SDK 3.x. However, the issue occurs with SDK 4.x and SDK 5.x.
The security protocol is WPA2-PSK with AES encryption.
What is the actual behavior?
Even when using the STA example program provided in SDK 5.3.2, the same issue occurs.
Path: v5.3.2\esp-idf\examples\wifi\getting_started\station
Additionally, the connection issue persists even when using the AT COMMAND method.
Steps to reproduce.
...
Debug Logs.
More Information.
I also think it might be a timing issue. Occasionally, the connection succeeds during repeated attempts. This occurs when the log level is set to DEBUG.
The text was updated successfully, but these errors were encountered: