[GH-ISSUE #115] AP connect failures when stored client fails. #89

New issue

Open

opened 2026-02-28 01:23:21 +03:00 by kerem · 30 comments

kerem commented 2026-02-28 01:23:21 +03:00

Owner

Copy link

Originally created by @tablatronix on GitHub (Feb 29, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/115

So this is a pretty normal thing. You move your board from one network to another ( I do this everyday for development )

And I noticed if there is a stored config, and it fails to connect or find the SSID, then soft AP mode does 2 things.

1. connection failures on some devices, method unknown
2. web responses are very slow or fail entirely.

I am tracking this issue as similar
https://github.com/esp8266/Arduino/issues/1094

also see my notes on it.

I added an explicit disconnect to
startConfigPortal() and it seems to have stabilized my setup. ( IOS always fails to connect to AP )

I am not sure why changing mode doesn't handle this alone, but it seems some channel scan or something keeps running in the background ( no debugging revealed what it was ), maybe some interrupt problem or memory problem or by design.

fyi ESP.eraseConfig() and reboot also fixes the issue, but not ideal solution obviously.

Originally created by @tablatronix on GitHub (Feb 29, 2016). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/115 So this is a pretty normal thing. You move your board from one network to another ( I do this everyday for development ) And I noticed if there is a stored config, and it fails to connect or find the SSID, then soft AP mode does 2 things. 1. connection failures on some devices, method unknown 2. web responses are very slow or fail entirely. I am tracking this issue as similar https://github.com/esp8266/Arduino/issues/1094 also see my notes on it. I added an explicit disconnect to `startConfigPortal()` and it seems to have stabilized my setup. ( IOS always fails to connect to AP ) I am not sure why changing mode doesn't handle this alone, but it seems some channel scan or something keeps running in the background ( no debugging revealed what it was ), maybe some interrupt problem or memory problem or by design. fyi `ESP.eraseConfig()` and reboot also fixes the issue, but not ideal solution obviously.

kerem added the

bug

label 2026-02-28 01:23:21 +03:00

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

nice investigative work:
just adding disconnect() in start config portal would have 2 very important side effects.
disconnect() erases the config, so esps that would be started and enter config due to temporarily missing router for instance, will never connect again. also people already starting config mode while connected to something, would loose connection (don t know if this is not happening already)
there may be a few things to try here, maybe you can help me with since you are getting the issue ( i am not getting it on any modules currently...)

1. add ESP.eraseConfig() at the beginning of your sketch, before anything else. does it help?
2. instead of disconnect to startConfigPortal, try this

WiFi.persistent(false);
WiFi.disconnect(true);
WiFi.persistent(true);

and maybe it won t erase the settings. this should be tested as well, that if you reboot, instead of reconfigure after starting the portal, it would still remember the old settings. i think this is very important
3. try the ap + sta mode instead of ap? maybe that s more...compatible? although in the past there s been lots of issues with that

thanks

<!-- gh-comment-id:190567548 --> @tzapu commented on GitHub (Mar 1, 2016): nice investigative work: just adding disconnect() in start config portal would have 2 very important side effects. disconnect() erases the config, so esps that would be started and enter config due to temporarily missing router for instance, will never connect again. also people already starting config mode while connected to something, would loose connection (don t know if this is not happening already) there may be a few things to try here, maybe you can help me with since you are getting the issue ( i am not getting it on any modules currently...) 1. add ESP.eraseConfig() at the beginning of your sketch, before anything else. does it help? 2. instead of disconnect to startConfigPortal, try this ``` WiFi.persistent(false); WiFi.disconnect(true); WiFi.persistent(true); ``` and maybe it won t erase the settings. this should be tested as well, that if you reboot, instead of reconfigure after starting the portal, it would still remember the old settings. i think this is very important 3. try the ap + sta mode instead of ap? maybe that s more...compatible? although in the past there s been lots of issues with that thanks

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

Eraseconfig requires a reboot but yeah the problem goes away cause theres nothing to connect to.

Disconnect should not erase config it should turn off radio. Maybe i read wrong cause that makes no sense.

<!-- gh-comment-id:190714587 --> @tablatronix commented on GitHub (Mar 1, 2016): Eraseconfig requires a reboot but yeah the problem goes away cause theres nothing to connect to. Disconnect should not erase config it should turn off radio. Maybe i read wrong cause that makes no sense.

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

if persistent is true, disconnect will also erase config. that s what i used in resetSettings, seems very effective

erase config deletes calibration data, so if it s done before connecting to anything, should it not help? ( i haven t look in what it actually does, i just saw the recommandation at some point by igrr to put it in front of everything, before connecting, etc...i think...if i remember correctly)

<!-- gh-comment-id:190716683 --> @tzapu commented on GitHub (Mar 1, 2016): if persistent is true, disconnect will also erase config. that s what i used in resetSettings, seems very effective erase config deletes calibration data, so if it s done before connecting to anything, should it not help? ( i haven t look in what it actually does, i just saw the recommandation at some point by igrr to put it in front of everything, before connecting, etc...i think...if i remember correctly)

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

Erase config wipes your config file so it requires a reboot to take effect and like you said you lose config which could be bad if you make mistake or cancel config

<!-- gh-comment-id:190717715 --> @tablatronix commented on GitHub (Mar 1, 2016): Erase config wipes your config file so it requires a reboot to take effect and like you said you lose config which could be bad if you make mistake or cancel config

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

i tried it without reset so that s why i didn t see the erase of ssid pass as well
https://github.com/esp8266/Arduino/issues/1494

<!-- gh-comment-id:190719569 --> @tzapu commented on GitHub (Mar 1, 2016): i tried it without reset so that s why i didn t see the erase of ssid pass as well https://github.com/esp8266/Arduino/issues/1494

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

so yes, 1 doesn t seem to be a go...

<!-- gh-comment-id:190719837 --> @tzapu commented on GitHub (Mar 1, 2016): so yes, 1 doesn t seem to be a go...

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

Yeah its probably async I always manually restart never tried automating it.

<!-- gh-comment-id:190719937 --> @tablatronix commented on GitHub (Mar 1, 2016): Yeah its probably async I always manually restart never tried automating it.

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

well, i looked at it, it actually wipes the flash sectors cotaning the data, so it matters when that data is read, to see if it needs a reset or not

<!-- gh-comment-id:190720645 --> @tzapu commented on GitHub (Mar 1, 2016): well, i looked at it, it actually wipes the flash sectors cotaning the data, so it matters when that data is read, to see if it needs a reset or not

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

I can't even find the definition for WiFi.disconnect in the source, Did you see it even documented somewhere?

<!-- gh-comment-id:190739097 --> @tablatronix commented on GitHub (Mar 1, 2016): I can't even find the definition for WiFi.disconnect in the source, Did you see it even documented somewhere?

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

here
github.com/esp8266/Arduino@bbaed29b7e/libraries/ESP8266WiFi/src/ESP8266WiFiSTA.cpp (L243)

<!-- gh-comment-id:190749812 --> @tzapu commented on GitHub (Mar 1, 2016): here https://github.com/esp8266/Arduino/blob/bbaed29b7e55f15d61eeedbf4d91e0473672222d/libraries/ESP8266WiFi/src/ESP8266WiFiSTA.cpp#L243

kerem commented 2026-02-28 01:23:21 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

yeah not sure how I was missing it.

So I cannot reproduce this outside of wifimanager. I am trying to replicate as close as possible, but no luck. Strange.

/* based on wifiaccess example */
/* Create a WiFi access point and provide a web server on it. */

#include <ESP8266WiFi.h>
#include <WiFiClient.h> 
#include <ESP8266WebServer.h>

/* Set these to your desired credentials. */
const char *ssid = "ESPap";
const char *password;

ESP8266WebServer server(80);

/* Just a little test message.  Go to http://192.168.4.1 in a web browser
 * connected to this access point to see it.
 */
void handleRoot() {
    server.send(200, "text/html", "<h1>You are connected</h1>");
}

void setup() {
    delay(1000);
  Serial.begin(115200);
  Serial.setDebugOutput(true); 

  // WiFi.begin("nonexisting","password"); // store
  WiFi.begin(); // restore

  delay(300);
  WiFi.printDiag(Serial);

  Serial.println((String)WiFi.waitForConnectResult());

  WiFi.mode(WIFI_AP);
  delay(300);
  WiFi.printDiag(Serial);

    Serial.println();
    Serial.print("Configuring access point...");
    /* You can remove the password parameter if you want the AP to be open. */
    WiFi.softAP(ssid, password);
  delay(300);
  WiFi.printDiag(Serial);

    IPAddress myIP = WiFi.softAPIP();
    Serial.print("AP IP address: ");
    Serial.println(myIP);
    server.on("/", handleRoot);
    server.begin();
    Serial.println("HTTP server started");
}

void loop() {
    server.handleClient();
}

I am not doing the dns and webserver stuff... I wonder.

<!-- gh-comment-id:190790006 --> @tablatronix commented on GitHub (Mar 1, 2016): yeah not sure how I was missing it. So I cannot reproduce this outside of wifimanager. I am trying to replicate as close as possible, but no luck. Strange. ``` /* based on wifiaccess example */ /* Create a WiFi access point and provide a web server on it. */ #include <ESP8266WiFi.h> #include <WiFiClient.h> #include <ESP8266WebServer.h> /* Set these to your desired credentials. */ const char *ssid = "ESPap"; const char *password; ESP8266WebServer server(80); /* Just a little test message. Go to http://192.168.4.1 in a web browser * connected to this access point to see it. */ void handleRoot() { server.send(200, "text/html", "<h1>You are connected</h1>"); } void setup() { delay(1000); Serial.begin(115200); Serial.setDebugOutput(true); // WiFi.begin("nonexisting","password"); // store WiFi.begin(); // restore delay(300); WiFi.printDiag(Serial); Serial.println((String)WiFi.waitForConnectResult()); WiFi.mode(WIFI_AP); delay(300); WiFi.printDiag(Serial); Serial.println(); Serial.print("Configuring access point..."); /* You can remove the password parameter if you want the AP to be open. */ WiFi.softAP(ssid, password); delay(300); WiFi.printDiag(Serial); IPAddress myIP = WiFi.softAPIP(); Serial.print("AP IP address: "); Serial.println(myIP); server.on("/", handleRoot); server.begin(); Serial.println("HTTP server started"); } void loop() { server.handleClient(); } ``` I am not doing the dns and webserver stuff... I wonder.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 1, 2016):

i ve been trying the same with no luck, but did not get to webserver level like you
i suggest adding the store part to the handleRoot, and a connect after that?

that should simulate the client being connected as well

<!-- gh-comment-id:190803192 --> @tzapu commented on GitHub (Mar 1, 2016): i ve been trying the same with no luck, but did not get to webserver level like you i suggest adding the store part to the handleRoot, and a connect after that? that should simulate the client being connected as well

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

retracted, i missed something so simple

<!-- gh-comment-id:190818343 --> @tablatronix commented on GitHub (Mar 1, 2016): retracted, i missed something so simple

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 1, 2016):

It is
WiFi.waitForConnectResult()

If you add a delay of 1-2s after it, or remove it, its works fine.

no clue why, done for today.

<!-- gh-comment-id:190820350 --> @tablatronix commented on GitHub (Mar 1, 2016): It is `WiFi.waitForConnectResult()` If you add a delay of 1-2s after it, or remove it, its works fine. no clue why, done for today.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 5, 2016):

hi, i ve noticed another scenario that seems to be leading to a deadlock in WiFi.waitForConnectResult()
it seems to be related to the auto connection(of the esp) mechanism and WiFi.begin();
you could try disabling the auto connect of the sdk on boot, i know there s a flag for it somewhere

i ran into it and added a possible fix to wifi manager, but that only works when you try with a good user and password

<!-- gh-comment-id:192676549 --> @tzapu commented on GitHub (Mar 5, 2016): hi, i ve noticed another scenario that seems to be leading to a deadlock in WiFi.waitForConnectResult() it seems to be related to the auto connection(of the esp) mechanism and WiFi.begin(); you could try disabling the auto connect of the sdk on boot, i know there s a flag for it somewhere i ran into it and added a possible fix to wifi manager, but that only works when you try with a good user and password

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 5, 2016):

Yeah its a odd thing I never did figure it out, but its a timing issue of where in an ap autoconnect failure scan process you try to start the softap, I am thinking it is something to do with a reset state or which channel the scan is on or landed on (it ends at 14, which is not supported by some hardware) so maybe that is why my IOS has issues. But I gave up for a while until I can get more advanced debugging and find out where that code is and how it works.

<!-- gh-comment-id:192677961 --> @tablatronix commented on GitHub (Mar 5, 2016): Yeah its a odd thing I never did figure it out, but its a timing issue of where in an ap autoconnect failure scan process you try to start the softap, I am thinking it is something to do with a reset state or which channel the scan is on or landed on (it ends at 14, which is not supported by some hardware) so maybe that is why my IOS has issues. But I gave up for a while until I can get more advanced debugging and find out where that code is and how it works.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 5, 2016):

the issue in waitForConnectResult i found, seems realted to the fact that the SDK starts connecting on boot, even before we call any functions in wifimanager
need to find those fucntions to disable that

<!-- gh-comment-id:192680004 --> @tzapu commented on GitHub (Mar 5, 2016): the issue in waitForConnectResult i found, seems realted to the fact that the SDK starts connecting on boot, even before we call any functions in wifimanager need to find those fucntions to disable that

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 5, 2016):

I find that if you can do your stuff before it even has a chance then you are usually ok.
But if you wait or there is a delay (which waitforconnect does ) then you have to wait even more or change mode and then wait for it to stabilize, so adding a delay of about 2000 after either of those seemed to fix my problems but that could just be random timing issues also.

Either way autoconnect = false should theoretically resolve, but i guess it saves and then you need to restart for it to take effect also.

wificonnect() is probably in the sdk and out of the libraries control, that I could see.

<!-- gh-comment-id:192680722 --> @tablatronix commented on GitHub (Mar 5, 2016): I find that if you can do your stuff before it even has a chance then you are usually ok. But if you wait or there is a delay (which waitforconnect does ) then you have to wait even more or change mode and then wait for it to stabilize, so adding a delay of about 2000 after either of those seemed to fix my problems but that could just be random timing issues also. Either way autoconnect = false should theoretically resolve, but i guess it saves and then you need to restart for it to take effect also. wificonnect() is probably in the sdk and out of the libraries control, that I could see.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 8, 2016):

hi, finally i was able to reproduce this outside wifi manager
could you tell me what WiFi.status() returns for you in the example above, immediatelly before the locking waitForConnectResult() ?

<!-- gh-comment-id:193591630 --> @tzapu commented on GitHub (Mar 8, 2016): hi, finally i was able to reproduce this outside wifi manager could you tell me what WiFi.status() returns for you in the example above, immediatelly before the locking waitForConnectResult() ?

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 8, 2016):

hi, i ve just made another commit to this, could you please try the github version of WiFiManager and see if anything changed for you?

<!-- gh-comment-id:193618806 --> @tzapu commented on GitHub (Mar 8, 2016): hi, i ve just made another commit to this, could you please try the github version of WiFiManager and see if anything changed for you?

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 9, 2016):

paste the commit hashes ?

It does seem more stable now.

<!-- gh-comment-id:194531476 --> @tablatronix commented on GitHub (Mar 9, 2016): paste the commit hashes ? It does seem more stable now.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tzapu commented on GitHub (Mar 10, 2016):

fixes in these 2 hashes
b99487785d
566bcbe063

that is great news

<!-- gh-comment-id:194659778 --> @tzapu commented on GitHub (Mar 10, 2016): fixes in these 2 hashes b99487785d2c8319df1223b204e1bba2b321f3f3 566bcbe0632c2c501995a7a9d6c3490bb0d33e5b that is great news

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 10, 2016):

ahh, interesting fixes.

<!-- gh-comment-id:194850443 --> @tablatronix commented on GitHub (Mar 10, 2016): ahh, interesting fixes.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@sej7278 commented on GitHub (Jul 10, 2016):

did anyone figure out how to do this yet, i "persisted" an accesspoint i've never even connected to and now it won't even try other AP's.

<!-- gh-comment-id:231588496 --> @sej7278 commented on GitHub (Jul 10, 2016): did anyone figure out how to do this yet, i "persisted" an accesspoint i've never even connected to and now it won't even try other AP's.

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jul 10, 2016):

Do you have alot of AP in the area ?

You have 2 options as this thread notes.

add WiFi.disconnect(true); before your ap connect in your sketch.

erase_config using esptool

<!-- gh-comment-id:231592687 --> @tablatronix commented on GitHub (Jul 10, 2016): Do you have alot of AP in the area ? You have 2 options as this thread notes. add WiFi.disconnect(true); before your ap connect in your sketch. erase_config using esptool

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@sej7278 commented on GitHub (Jul 10, 2016):

this does absolutely nothing, doesn't even blink the serial led i don't think:

https://github.com/igrr/esptool-ck/#erase-flash-on-a-nodemcu-board

running this a few times seems to do it randomly:

WiFi.persistent(false);
WiFi.disconnect(true);
WiFi.persistent(true);

<!-- gh-comment-id:231596261 --> @sej7278 commented on GitHub (Jul 10, 2016): this does absolutely nothing, doesn't even blink the serial led i don't think: https://github.com/igrr/esptool-ck/#erase-flash-on-a-nodemcu-board running this a few times seems to do it randomly: ``` WiFi.persistent(false); WiFi.disconnect(true); WiFi.persistent(true); ```

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jul 10, 2016):

I never could get esptool.exe to erase flash, i had to use esptool.py

<!-- gh-comment-id:231598920 --> @tablatronix commented on GitHub (Jul 10, 2016): I never could get esptool.exe to erase flash, i had to use esptool.py

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@kentaylor commented on GitHub (Jul 11, 2016):

For a low effort flash erasure, there is an Arduino sketch at https://github.com/kentaylor/EraseEsp8266Flash

<!-- gh-comment-id:231629220 --> @kentaylor commented on GitHub (Jul 11, 2016): For a low effort flash erasure, there is an Arduino sketch at https://github.com/kentaylor/EraseEsp8266Flash

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@sej7278 commented on GitHub (Jul 11, 2016):

nicely documented too @kentaylor

<!-- gh-comment-id:231677875 --> @sej7278 commented on GitHub (Jul 11, 2016): nicely documented too @kentaylor

kerem commented 2026-02-28 01:23:22 +03:00

Author

Owner

Copy link

@e1red commented on GitHub (Aug 10, 2016):

Hey guys,

Figured something out! Turns out the host definition in both the WiFiClientBasic and WifiClient example scripts was wrong.

Change this:
const char * host = "192.168.4.1"; // ip or dns
To this:
const IPAddress host = IPAddress(192,168,4,1);

Something about the way the libraries define whether we are asking for a IP or a DNS. Especially working with teeny dumb boards (I am on a NodeMCU 0.9). And I could connect to google via my home wifi but then couldn't seem to connect to 192.168.4.1 on my second NodeBoard

And wow that's like 10 hours of my life I won't get back. Also the WifiClientBasic script doesn't have a GET command so doesn't ever print out the webpage, but at least the WifiClient example script does.

Things that didn't help
WiFi.setPhyMode(WIFI_PHY_MODE_11G);
WiFi.disconnect();
WiFi.mode(WIFI_STA);
the erase script by KenTaylor (thanks but I guess not relevant right now)

For seeing the IPaddress thingo in action look up the ChatServer example

<!-- gh-comment-id:238871842 --> @e1red commented on GitHub (Aug 10, 2016): Hey guys, Figured something out! Turns out the host definition in both the WiFiClientBasic and WifiClient example scripts was wrong. Change this: `const char * host = "192.168.4.1"; // ip or dns` To this: `const IPAddress host = IPAddress(192,168,4,1);` Something about the way the libraries define whether we are asking for a IP or a DNS. Especially working with teeny dumb boards (I am on a NodeMCU 0.9). And I could connect to google via my home wifi but then couldn't seem to connect to 192.168.4.1 on my second NodeBoard And wow that's like 10 hours of my life I won't get back. Also the WifiClientBasic script doesn't have a GET command so doesn't ever print out the webpage, but at least the WifiClient example script does. Things that didn't help WiFi.setPhyMode(WIFI_PHY_MODE_11G); WiFi.disconnect(); WiFi.mode(WIFI_STA); the erase script by KenTaylor (thanks but I guess not relevant right now) For seeing the IPaddress thingo in action look up the ChatServer example

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

revert-1849-master

feature_fastconnect

feature_auth

feature_slimable

PEAP

feature_statichtmlparams

feature_asyncwebserver

feature_pagestringsref

parameter-smart-ptr

gh-pages

Legacy_v1

hotfixes

autochannelselect_feature

travis

smartconfig

v2.0.17

v2.0.16-rc.2

v2.0.15-rc.1

v2.0.0-rc.1

v2.0.14-beta

v2.0.13-beta

v2.0.12-beta

v2.0.11-beta

v2.0.10-beta

v2.0.9-beta

v2.0.8-beta

2.0.7-beta

2.0.6-beta

2.0.5-beta

2.0.4-beta

0.16.0

2.0.3-alpha

0.15.0

0.14

0.13

0.12

0.11

0.10

0.9

0.8

0.7

0.6

0.5

v0.4

v0.3

v0.2

v0.1

Labels

Clear labels   

📶 WiFi

  

🕸️ HTTP

  

Branch

  

DEV Help Wanted

  

Discussion

  

Documentation

  

ESP32

  

Example

  

Good First Issue

  

Hotfix

  

In Progress

  

Incomplete

  

Needs Feeback

  

Priority

  

QA

  

Question

  

Task

  

Upstream/Dependancy

  

bug

  

duplicate

  

enhancement

  

invalid

  

pull-request

Mirrored from GitHub Pull Request

  

wontfix

No labels

📶 WiFi

🕸️ HTTP

Branch

DEV Help Wanted

Discussion

Documentation

ESP32

Example

Good First Issue

Hotfix

In Progress

Incomplete

Needs Feeback

Priority

QA

Question

Task

Upstream/Dependancy

bug

duplicate

enhancement

invalid

pull-request

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/WiFiManager#89

No description provided.