[GH-ISSUE #1072] do not disable internal ap when device connected to external ap #914

New issue

Open

opened 2026-02-28 01:27:39 +03:00 by kerem · 4 comments

kerem commented

2026-02-28 01:27:39 +03:00

Owner

Originally created by @alirezaimi on GitHub (Jun 5, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1072

Hi
Is there any option exist in this library that after my board connected to external access point, do not disable internal ap of board ?
I'm asking this because i want both ap and sta mode active simultaneously in my esp8266 board for when external ap or internet connection is dead, i can connect to board with internal ap of board .

Originally created by @alirezaimi on GitHub (Jun 5, 2020). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1072 Hi Is there any option exist in this library that after my board connected to external access point, do not disable internal ap of board ? I'm asking this because i want both ap and sta mode active simultaneously in my esp8266 board for when external ap or internet connection is dead, i can connect to board with internal ap of board .

kerem commented

2026-02-28 01:27:40 +03:00

Author

Owner

@alirezaimi commented on GitHub (Apr 22, 2022):

Hi
in esp8266 board the ability of using both AP and sta in same time is exist and I want to use it, but in this library after connecting to AP, the internal sta disabled by default . I want to choose it optionally , how ???

@alirezaimi commented on GitHub (Apr 22, 2022): Hi in esp8266 board the ability of using both AP and sta in same time is exist and I want to use it, but in this library after connecting to AP, the internal sta disabled by default . I want to choose it optionally , how ???

kerem commented

2026-02-28 01:27:40 +03:00

Author

Owner

@tablatronix commented on GitHub (Apr 22, 2022):

just turn it on like usual WiFi.softAp()

@tablatronix commented on GitHub (Apr 22, 2022): just turn it on like usual WiFi.softAp()

kerem commented

2026-02-28 01:27:40 +03:00

Author

Owner

@alirezaimi commented on GitHub (Apr 25, 2022):

Hi @tablatronix
When should i do this ?
I mean in setup I got these lines :

// -- Initializing the configuration.
iotWebConf.init();

// -- Set up required URL handlers on the web server.
server.on("/", handleRoot);
server.on("/config", []{ iotWebConf.handleConfig(); });
server.onNotFound([](){ iotWebConf.handleNotFound(); });

and everything is handled by library itself, when i turn on softap again after the library disable it ?

@alirezaimi commented on GitHub (Apr 25, 2022): Hi @tablatronix When should i do this ? I mean in setup I got these lines : // -- Initializing the configuration. iotWebConf.init(); // -- Set up required URL handlers on the web server. server.on("/", handleRoot); server.on("/config", []{ iotWebConf.handleConfig(); }); server.onNotFound([](){ iotWebConf.handleNotFound(); }); and everything is handled by library itself, when i turn on softap again after the library disable it ?

kerem commented

2026-02-28 01:27:40 +03:00

Author

Owner

@tablatronix commented on GitHub (Apr 25, 2022):

hmm you mentioned ap mode not a webserver..
you can use the wm.server()

someone else just asked this in another issue, let me check

@tablatronix commented on GitHub (Apr 25, 2022): hmm you mentioned ap mode not a webserver.. you can use the wm.server() someone else just asked this in another issue, let me check