-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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 not reconnecting after connection lost in lwip 2 #4101
Comments
I've got a similar behavior. The ESP does reconnect to the WiFi network - I can successful ping the device, after the AP has gone and came back again. But the state of WiFi.status() isn't getting to WL_CONNECTED again, so that my HTTP GET Requests always fail. |
@EricMc1289 @jp112sdl Please test the referenced PR. |
@devyte For everyone else with this issue. The solution above works so far, so I will close this issue. I will test this software the next couple of days and report any problems in this thread |
Thanks for testing |
related to esp8266#4101 esp8266#4078 esp8266#4060 esp8266#4028 and maybe others
related to esp8266#4101 esp8266#4078 esp8266#4060 esp8266#4028 and maybe others
Basic Infos
Hello everyone. I have a very strange problem since 2.4.0.
Hardware
Hardware: Esp8266 12f and Esp8266 -01
Description
If the ESP looses the connection to the router (just disable your network for 30 seconds and reenable again at the router) the ESP won't connect to the wifi again.
It is a very strange behaviour, because the function wifi_station_get_connect_status() return only 0 then when the WiFi.begin was called 1 and after sometime 0 again. And now it gets even more funny when the ESP stucks at 1 my Router a Fritzbox 7490 lists the device as connected and you can access the httpserver on the ESP but only until it goes back to 0 again. It never gets the state 3 which should be triggered once. Under 2.3.0 everything works fine and as expected.
After an reboot it connects again...
Settings in IDE
lwip v2 prebuilt MSS=536
Sketch
The text was updated successfully, but these errors were encountered: