WiFi.status() always not connected.

[fabiosoft]

Basic Infos

Hardware

Hardware: ESP-01
Core Version: 2.3.0

Description

WiFi.status() always not connected. WL_CONNECTED is never set with version 2.3.0, instead with version 2.0.0 everything works ok.

It outputs a not connected state ...while surfing web!! How is it possible?

Settings in IDE

Module: Generic ESP8266 Module
Flash Size: 512k
CPU Frequency: 80Mhz
Flash Mode: dio
Flash Frequency: 40Mhz
Upload Using: SERIAL
Reset Method: ck

Sketch

#include <Arduino.h>

#include <ESP8266WiFi.h>

int status = WL_IDLE_STATUS;                     // the Wifi radio's status

void setup() {
  Serial.begin(57600);


  // attempt to connect to Wifi network:
  while ( status != WL_CONNECTED) { //<---- never changed! status never changes
    Serial.println("Attempting to connect to...");
    status = WiFi.begin("xxxx", "xxxx");

    // wait 10 seconds for connection:
    delay(1000);
  }

  // once you are connected :
  Serial.print("You're connected to the network");
}

void loop() {
  // check the network status connection once every 10 seconds:
  delay(1000);
  Serial.println(WiFi.status()); // <--- always NOT_CONNECTED status.
}

[WereCatf]

No idea what's wrong, it works just fine on my ESPs.

[gilbertobueno]

Please, see issue 2186. Maybe it can help you. https://github.com/esp8266/Arduino/issues/2186

[KingModest]

Hi, am still having this issue, with AT commands module connects, but if I want to do this, status != WL_CONNECTED - the statement always return true

[savankoradia]

Same issue here. WiFi.status() returns 255. But still able to connect using AT command.

[mitsuhito]

I have same issue. my hardware is esp-wroom-02.
https://international.switch-science.com/catalog/2500/

[max5555]

A workaround is to replace
while ( status != WL_CONNECTED) {
with
while (WiFi.localIP().toString() == "0.0.0.0") {

[devyte]

@fabiosoft is this issue still valid with latest git?

[briskt]

I just tested with the latest, and it still does the same for me. Sometimes (~30%) works, but usually returns WL_DISCONNECTED indefinitely.

[muthu29]

Did anyone find the solution. I have the same problem always Wifi.status() is not connected and when I tried to print the Wifi.status() it returns value 0 for five times and a 6 once. I am wondering how this will by any chance give a String value of WL_CONNECTED :(

[briskt]

@muthu29 the workaround by @max5555 is good. To answer your question about return value, WL_CONNECTED is an enum value that equates to 3. It's defined in wl_definitions.h:

typedef enum { WL_NO_SHIELD = 255, // for compatibility with WiFi Shield library WL_IDLE_STATUS = 0, WL_NO_SSID_AVAIL = 1, WL_SCAN_COMPLETED = 2, WL_CONNECTED = 3, WL_CONNECT_FAILED = 4, WL_CONNECTION_LOST = 5, WL_DISCONNECTED = 6 } wl_status_t;

[devyte]

This should be addressed in latest master.
@fabianoms @Fly4TheKing @muthu29 @KingModest could someone please retest?

[muthu29]

For me it was a Typo in the SSID Password. It is working when I corrected it.

[devyte]

Closing due to recent lwip glue fixes and WiFi::status() testing.

[slow-down]

How can it be, that it's still not fixed, even with 2.4.2 ... It's been more than 3 years. I had to use the workaround to fix it..

[ScientificNerd]

I tried the workaround, and it failed. So, I printed "WiFi.localIP().toString()" to the console, and to my amazement, it did not contain "0.0.0.0", but "(IP unset)", so I replaced the "0.0.0.0" with "(IP unset)" in the while statement, and it still didn't connect. Then I decided to check the router connections, and found that the IP had been issued, and the ESP was connected to the router.

At that point, I thought maybe the router was taking a bit longer to get everything done before the "while" timeout, so I added 15 seconds, and also decided to change the "while" statement to:

while (WiFi.localIP().toString() != IP) {
WiFi.begin(ssid, password) ;
// failed, retry
Serial.print(".");
delay(20000);
}
or
while (WiFi.localIP().toString() == "(IP unset)") {
WiFi.begin(ssid, password) ;
// failed, retry
Serial.print(".");
delay(20000);

Where "IP" was set as a global char* constant, as I had set the IP address for the ESP MAC in the router. Both were tested, and work.

I am using a Netgear WNDR3000-2, which takes its sweet time connecting. Since I need my ESP addresses to be fixed, I used the router to save the addresses rather than try to get the ESP's to request a fixed IP.

Now that this stumbling block is passed, I can finally move on to productive parts of my project.

[d-a-v]

Please try and replace

while (WiFi.localIP().toString() == "(IP unset)") {

by

while (!WiFi.localIP().isSet()) {

Checking against a string is always worse when there are other means.

[ScientificNerd]

That works very well, Thanks! You are quite right about checking against strings, as it takes more program memory, as well as more time than checking for bool.

[ebrahimkarimi]

for me, none of the above worked!!!
after digging deep i was able to debug it and find a solution that may work for everyone.
i just enabled debugging in Arduino IDE and used Serial to connect the esp8266-12e to my phone and debug it using USB Serial Terminal.
i found out there was messages like evt : <number> after a searched i realized there is WiFi events. so i found this. i realized connect event triggers after WiFi.begin(ssid,pwd) but StationGotIP event wont get triggered correctly:

you can see that after connection established, event 0 triggered (event docs) but event 3 (EVENT_STAMODE_GOT_IP) didn't.
so i think the best and safe solution would be registering a EVENT_STAMODE_CONNECTED event.

some usable links:
Arduino ESP8266 - wifi evt: 3 and wifi evt: 7 meaning?

[Bighoneypot]

Please, try with another SSID and Password, could be a problem with your router. Use Hotspot in your smartphone and try.
Leave the hotspot screen open and watch if your esp is connected on your hotspot.

[mazorvanunu]

come delete my comments "contributor" or maybe tell me to check up on my power cord. that will surely make a huge difference, i feel engulfed with your support. <3

[d-a-v]

@mazorvanunu
This is a closed issue. Please open a new one with your data, don't forget to fill the issue template and provide an MCVE.
I deleted offending comments.