starred/WiFiManager

Fork 0

mirror of https://github.com/tzapu/WiFiManager.git synced 2026-04-27 00:55:52 +03:00

[GH-ISSUE #911] AP appears despite of entering client mode. #771

New issue

Closed

opened 2026-02-28 01:26:58 +03:00 by kerem · 8 comments

kerem commented

2026-02-28 01:26:58 +03:00

Owner

Originally created by @YogKar on GitHub (Jul 11, 2019).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/911

Basic Infos

Hardware

WiFimanager Branch/Release:

travis

Esp8266/Esp32:

ESP8266

**Hardware:

ESP12 E/F/S (nodemcu, wemos, feather)

Description

Using https://github.com/tzapu/WiFiManager/tree/travis

I need non blocking AP, and so i am using "https://github.com/tzapu/WiFiManager/tree/travis"
I was testing the basic Autoconnect .
When I configure , save New AP in portal, and restart ESP8266 module, The device gets configured in client mode and connects to the configured AP. But along with that it also Shows AP which is typically ESPxxx (starting with ESP). which ideally should have not been appearing.
to check further I tried to connect it. but could not get the config portal page. and this happens in blocking as well in non blocking mode.

what must be happening? How should this be resolved?

https://github.com/tzapu/WiFiManager/issues/457
The above issue looks similar . Is it resolved ?

Update:
https://github.com/tzapu/WiFiManager/tree/0.14
That problem is not with 0.14

Settings in IDE

Module: NodeMcu

Additional libraries:

Sketch


#include <Arduino.h>

void setup() {

}

void loop() {

}

Debug Messages

messages here

Originally created by @YogKar on GitHub (Jul 11, 2019). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/911 ### Basic Infos #### Hardware **WiFimanager Branch/Release:** - [ ] travis **Esp8266/Esp32:** - [ ] ESP8266 **Hardware: - [ ] ESP12 E/F/S (nodemcu, wemos, feather) ### Description Using https://github.com/tzapu/WiFiManager/tree/travis I need non blocking AP, and so i am using "https://github.com/tzapu/WiFiManager/tree/travis" I was testing the basic Autoconnect . When I configure , save New AP in portal, and restart ESP8266 module, The device gets configured in client mode and connects to the configured AP. But along with that it also Shows AP which is typically ESPxxx (starting with ESP). which ideally should have not been appearing. to check further I tried to connect it. but could not get the config portal page. and this happens in blocking as well in non blocking mode. what must be happening? How should this be resolved? https://github.com/tzapu/WiFiManager/issues/457 The above issue looks similar . Is it resolved ? Update: https://github.com/tzapu/WiFiManager/tree/0.14 That problem is not with 0.14 ### Settings in IDE Module: NodeMcu Additional libraries: ### Sketch ```cpp #include <Arduino.h> void setup() { } void loop() { } ``` ### Debug Messages ``` messages here ```

kerem closed this issue

2026-02-28 01:26:58 +03:00

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@tablatronix commented on GitHub (Jul 11, 2019):

WiFi.mode(WiFi_STA); // set mode explicitly
Esp does that by default

@tablatronix commented on GitHub (Jul 11, 2019): WiFi.mode(WiFi_STA); // set mode explicitly Esp does that by default

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@YogKar commented on GitHub (Jul 12, 2019):

It worked.
Thanks for working on nonblocking and sharing it. It's a huge effort saver.

@YogKar commented on GitHub (Jul 12, 2019): It worked. Thanks for working on nonblocking and sharing it. It's a huge effort saver.

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@tablatronix commented on GitHub (Jul 12, 2019):

I assume you meant you are using
https://github.com/tzapu/WiFiManager/tree/development

not travis. ?

@tablatronix commented on GitHub (Jul 12, 2019): I assume you meant you are using https://github.com/tzapu/WiFiManager/tree/development not travis. ?

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@YogKar commented on GitHub (Jul 13, 2019):

"https://github.com/tzapu/WiFiManager/tree/development" shows that the "build failing" for both ESP8266 and ESP32. So i thought it's somewhere incomplete or broken.

But after your reply I tested it. Its working flawless.

@YogKar commented on GitHub (Jul 13, 2019): "https://github.com/tzapu/WiFiManager/tree/development" shows that the "build failing" for both ESP8266 and ESP32. So i thought it's somewhere incomplete or broken. But after your reply I tested it. Its working flawless.

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@tablatronix commented on GitHub (Jul 13, 2019):

the script needs to be fixed, it broke when something changed in esp toolchain, I have not had time to look at it

@tablatronix commented on GitHub (Jul 13, 2019): the script needs to be fixed, it broke when something changed in esp toolchain, I have not had time to look at it

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@YogKar commented on GitHub (Jul 13, 2019):

I have to add few things so that other visitors here get some help and if I have done wrong you can correct me. This is based on my experience.

polling process() every 10ms gave me best results while using non-blocking mode..
I stopped polling when the device is configured in station mode (client).
Makes sense?

@YogKar commented on GitHub (Jul 13, 2019): I have to add few things so that other visitors here get some help and if I have done wrong you can correct me. This is based on my experience. 1) polling process() every 10ms gave me best results while using non-blocking mode.. 2) I stopped polling when the device is configured in station mode (client). Makes sense?

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@tablatronix commented on GitHub (Jul 14, 2019):

Yes you will have to process the web server constantly or it will not handle requests fast enough, and probably turn debugging off and serial prints.

You can process when ever you want the library will return if the webserver is not running, you can also run the webserver in sta mode without the ap or without the captive portal

@tablatronix commented on GitHub (Jul 14, 2019): Yes you will have to process the web server constantly or it will not handle requests fast enough, and probably turn debugging off and serial prints. You can process when ever you want the library will return if the webserver is not running, you can also run the webserver in sta mode without the ap or without the captive portal

kerem commented

2026-02-28 01:26:59 +03:00

Author

Owner

@YogKar commented on GitHub (Jul 16, 2019):

Sure.

@YogKar commented on GitHub (Jul 16, 2019): Sure.