-
Notifications
You must be signed in to change notification settings - Fork 1.3k
ESP32S2 WiFi connect() hard-resets and "Connection Error: Unknown failure" #3712
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
Comments
After doing tests with Metro ESP32-S2 with the Arduino IDE, the second part of this issue ( |
Small update: upon reboot of problematic AP (Apple Time Capsule w/ external DHCP), Metro ESP32-S2 connection results:
|
beta.0 is broken. Please use the a18 build until #3716 is merged into main. |
Helping with a connection issue on Discord (https://discord.com/channels/327254708534116352/537365702651150357/781234430520852491), I was able to connect to an Apple Airport Express set up as "Create a Wireless Network" in bridge mode (main router providing DHCP), with
|
@todbot Any update? Maybe we can close this. |
Hi @tannewt, I've not been able to reproduce this error on |
Tested on Metro ESP32-S2 and MagTag. This was also present in a debug firmware for MagTag provided by @tannewt on 17 Nov 2020.
On CircuitPython-6.1.0-beta.0, the
wifi
module will sometimes hard-reset onwifi.radio.connect()
, using a small connect script (*) This seems to only occur on Ctrl-D and save-on-reload restarts. When starting from hardware reset / power-on, the script works.Also on CP-6.1.0-beta.0, it seems the ESP32-S2 WiFi cannot connect to APs that are not DHCP servers (but instead use a DHCP server over LAN). I have two APs on my network: one is the router and DHCP server, another is secondary AP (with different SSID) on the same LAN as the DHCP server. The ESP32-S2 CP can connect to the primary AP that's the DHCP server, but will error out with
Connection Error: Unknown failure
on the secondary AP. This almost feels like the ESP32-S2 is timing out early for a DHCP response.*e.g. a script such as:
The text was updated successfully, but these errors were encountered: