-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Net connection broken in ESP8266WiFi library Version 2.5.0 or later #6138
New issue
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No 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? No Sign in to your account
Comments
watching this: I have a (possibly) similar problem |
Which problem? That ESP8266WiFi library Version 2.5.0 or later will not connect to WiFi? |
I've the same problem, did you solve the lost of connections ? |
Please try version 2.5.2, and use the tool menu option "Erase All Flash". |
I'm not sure to whom you are directing the request, but here is my test sketch:
I installed esp8266 Version 2.5.2, flashed (selecting "all flash contents"). This is what I get:
Reinstalled Version 2.4.2, flashed as above, and this is what I get:
|
I have the similar problem with my Feather Huzzah. It will successfully connect via the HTTPSRequest example when using the 2.4.2 library but not with 2.5.1 or 2.5.2. I tried the Erase Flash option 'All Flash Contents' initially and switched to 'Only Sketch' afterwards. It will connect to my WiFi network but not to api.github.com ("connection failed"). Does the erase 'All Flash Contents' constitute a reflash of the firmware for an upgrade to the library? |
I believe this problem is caused by ignoring RF settings area on flash. The AT firmware reference has:
The location of RF parameters area depends on the size of the flash. The application must be flashed with the right flash size for SDK to find the RF parameters area. The esp8266 uses the values in esp_init_data_default.bin as start values for RF calibration. Sometimes It can calibrate starting with wrong values, sometimes not. Different SDK versions may have different default values. |
Jandrassy- perhaps I wasn't clear. I have tried the experiment on several Wemos D1 Mini's and some NodeMCU boards. I've tried Erase Flash: "Only Sketch", "Sketch + WiFi Settings" and "All Flash Contents". Something has changed in the library. |
the esp8266 core uses Espressif SDK. 2.4.2 has a different SDK version then 2.5.0. generic.menu.sdk.nonosdk221=nonos-sdk 2.2.1 (legacy) default for other boards is build.sdk=NONOSDK221 |
And, that fixes the problem, how? |
did you try 2.5.2? |
Yes, and I posted my test sketch and the results above. #6138 (comment) |
did you try without |
Didn't fix it. And I did use "Erase Flash: All Flash Content". Tried it on two different boards (a NodeMCU and a Wemos D1 Mini). |
can you try WPA authentication? |
This is a home router- there is no username or password. Or am I not understanding WPA? I couldn't find any examples using Professor Google. |
WEP has a passphrase, WPA has password. both are set the same way, as second parameter in WiFi.begin. you could try a smartphone as WiFi hotspot |
Yes. Version 2.5.2 does connect to my phone as a hot spot. But not to my home network. Does this give a clue what is happening? I went to my router to see if there was a setting for WPA, and it was hidden under four different pages on the router. I turned on WPA, which turned off WEP automatically. To maintain some compatibility, I gave it an ascii password that was the same as the WEP passphrase. So, yes, not V2.5.2 does connect to my network. But that created all new problems. I have 65 devices on my IP scan, and after turning on WPA, only 20 of them would reconnect over WPA. Fixing that would be a full-day job in itself because many of these devices are inside wall-boxes, inside of appliances and generally inconvenient to get to the flash pins. Then I would have to find the sketches for each device that aren't running Tasmota. So, in summary, you are saying that V2.5.X of ESP8266WIFI.h does not support WEP? |
it should support WEP. how long is your paraphrase? 64 characters? or shorter? |
Thanks for working with me in this issue. When I tried setting up WPA on the router I used the same hex characters as an ASCII password. I really, really want to avoid reprogramming all of the devices on my network. |
None of these suggestions fix the problem of 2.5.2 (or anything higher than 2.4.2) preventing my feather huzzah from connecting to a known website, through either my phone hotspot or my home network (using WPA). I've tried the Generic ESP8266 profile as well as the Adafruit Feather Huzzah profile that corresponds to my device. Any other suggestions out there? Could this be related to the manufacture date/version of my device? |
2.4.2 works and 2.5.2 does not? |
Yes, 2.4.2 works for http, on my phone hot spot & home router. I'd like to upgrade to 2.5.2 because I'm unable to connect to some secure sites via HTTPS, and I'm hoping the newer libraries resolve some of these related issues. |
DHPC is where 2.5.2 gets stuck for me. The AP broadcast by the ESP shows on my laptop, but I can't connect to it. 2.4.2 works fine. |
@SteveRMann
before |
calling Thanks for pointing me to this new member of the class. I did a quick browse of the docs and don't see this anywhere. |
----------------------------- Delete below -----------------------------
----------------------------- Delete above -----------------------------
Basic Infos
Platform
Settings in IDE
Problem Description
I spent two days chasing this down, but you get the workaround in 2 minutes. I suspect that this problem may be unique to my environment, but here is what I found.
I have a few Wemos D1 Mini boards and NodeMCU boards that were working on the local WiFi yesterday, yet today none of them will connect after compiling and uploading to the Wemos or NodeMCU. More puzzling is that I can flash Tasmota on them and they all connect to the WiFi, but none with this code that was working yesterday. I recalled after a day of troubleshooting that I did a libraries upgrade.
I modified an example sketch (below) that just tries to connect to my local network, and instead of the marching dots, I show the WiFi.status().
I have determined that if I use ESP8266WiFi library Version 2.5.0 or later, this is what the sketch below returns:
(6=WL_DISCONNECTED, and 1=WL_NO_SSID_AVAIL)
By reverting to ESP8266WiFi library Version 2.4.2, I can get a connection:
(3=WL_CONNECTED)
Debug Messages
None
Additional information:
My router is an Actiontec MI424WR on Verizon Wireless.
I don't know if it's related, but I have had a connection problem from Raspberry Pi's which was resolved by removing the quotes from the wpa_supplicant.conf file:
The text was updated successfully, but these errors were encountered: