-
Notifications
You must be signed in to change notification settings - Fork 13.3k
ESP hang by Core 2.3.0 #2594
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
I too have sketches that reliably connect with the 2.1.0 core and fail to connect. or only connect a few times, with the 2.3.0 core. When a failure occurs, it happens in this loop: WiFi.begin(ssid, password); // connect to the network If I reset my router, it proceeds from the hangup, and I am able to connect a few times. (Not sure what that points to.) EDIT: Maybe I have the problem described in Issue 2186. I will try the workarounds. |
I had a similar problem and 'fixed' it by going back to V2.2.0 core |
Fixed my problem with the workaround described in Issue 2186. i.e. |
Unfortunately the above solution doesn't resolve my case. |
Fixed my problem too !!! if (WiFi.status() != WL_CONNECTED) { // FIX FOR USING 2.3.0 CORE (only .begin if not connected) Bajajar, , try it with a ssid-name, without special characters |
Fixed by rework coding with PubSubClient. Nothing wrong with ESP8266WiFi. Thanks you guys. |
Basic Infos
Hardware
Hardware: ESP-12E
Core Version: 2.3.0
Description
I flashed a sketch with PubSubClient version 2.6.0 and Core version 2.3.0. The problem occurred right after ESP connected to MQTT broker. The ESP hang about 30 seconds, then it could send and receive messages. Not only version 2.3.0 but also version 2.2.0 has the same problem too. However, the problem won't happen with Core version 2.1.0.
Settings in IDE
Module: Generic ESP8266 Module
Flash Size: 4MB/3MB
CPU Frequency: 80Mhz
Flash Mode: dio
Flash Frequency: 40Mhz
Upload Using: SERIAL
Reset Method: ck
The text was updated successfully, but these errors were encountered: