[GH-ISSUE #1721] If anyone wants to change the name (SSID) of the Access Point (AP) that appears (with the IP address 192.168.4.1) #1460

New issue

Closed

opened 2026-02-28 01:30:09 +03:00 by kerem · 12 comments

kerem commented 2026-02-28 01:30:09 +03:00

Owner

Copy link

Originally created by @rtek1000 on GitHub (Mar 15, 2024).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1721

If anyone wants to change the name (SSID) of the Access Point (AP) that appears (with the IP address 192.168.4.1), go to line 685. There seems to be a lack of alternatives in this part.

boolean WiFiManager::startConfigPortal() {
  String ssid = getDefaultAPName(); // <----------- SSID here: ESP32_XXXX
  return startConfigPortal(ssid.c_str(), NULL);
}

Example:

boolean WiFiManager::startConfigPortal() {
  String ssid = "My_AP"; //getDefaultAPName(); // <----------- SSID here: My_AP
  return startConfigPortal(ssid.c_str(), NULL);
}

github.com/tzapu/WiFiManager@d82d0a1b9f/WiFiManager.cpp (L686)

---

On line 538 something about HostName seems to be implemented, but I don't know if this should also appear when you press the button, for on-demand mode.

  // set ap hostname
  #ifdef ESP32
    if(ret && _hostname != ""){
      bool res =  WiFi.softAPsetHostname(_hostname.c_str());
      #ifdef WM_DEBUG_LEVEL
      DEBUG_WM(WM_DEBUG_VERBOSE,F("setting softAP Hostname:"),_hostname);
      if(!res)DEBUG_WM(WM_DEBUG_ERROR,F("[ERROR] hostname: AP set failed!"));
      DEBUG_WM(WM_DEBUG_DEV,F("hostname: AP: "),WiFi.softAPgetHostname());
      #endif
   }

github.com/tzapu/WiFiManager@d82d0a1b9f/WiFiManager.cpp (L538)

Originally created by @rtek1000 on GitHub (Mar 15, 2024). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1721 If anyone wants to change the name (SSID) of the Access Point (AP) that appears (with the IP address 192.168.4.1), go to line 685. There seems to be a lack of alternatives in this part. ```C++ boolean WiFiManager::startConfigPortal() { String ssid = getDefaultAPName(); // <----------- SSID here: ESP32_XXXX return startConfigPortal(ssid.c_str(), NULL); } ``` Example: ```C++ boolean WiFiManager::startConfigPortal() { String ssid = "My_AP"; //getDefaultAPName(); // <----------- SSID here: My_AP return startConfigPortal(ssid.c_str(), NULL); } ``` https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.cpp#L686 ---- On line 538 something about HostName seems to be implemented, but I don't know if this should also appear when you press the button, for on-demand mode. ```C++ // set ap hostname #ifdef ESP32 if(ret && _hostname != ""){ bool res = WiFi.softAPsetHostname(_hostname.c_str()); #ifdef WM_DEBUG_LEVEL DEBUG_WM(WM_DEBUG_VERBOSE,F("setting softAP Hostname:"),_hostname); if(!res)DEBUG_WM(WM_DEBUG_ERROR,F("[ERROR] hostname: AP set failed!")); DEBUG_WM(WM_DEBUG_DEV,F("hostname: AP: "),WiFi.softAPgetHostname()); #endif } ``` https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.cpp#L538

kerem 2026-02-28 01:30:09 +03:00

• closed this issue
• added the
  Question
  label

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 15, 2024):

Its the first argument in the function.. what do you mean?

startConfigPortal(ssid,..

<!-- gh-comment-id:1999290875 --> @tablatronix commented on GitHub (Mar 15, 2024): Its the first argument in the function.. what do you mean? startConfigPortal(ssid,..

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

The initial post about the 686 line was with ESP32.

It also occurs with the ESP8266, in the line 388

  // not connected start configportal
  bool res = startConfigPortal(apName, apPassword);

At the beginning of Main there is wm.setHostname("MDNSEXAMPLE"), line 37, onDemandNonBlocking.ino.

Shouldn't the library have used this same "MDNSEXAMPLE" as the SSID?

<!-- gh-comment-id:1999741628 --> @rtek1000 commented on GitHub (Mar 15, 2024): The initial post about the 686 line was with ESP32. It also occurs with the ESP8266, in the line [388](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.cpp#L388) ```C++ // not connected start configportal bool res = startConfigPortal(apName, apPassword); ``` At the beginning of Main there is wm.setHostname("MDNSEXAMPLE"), [line 37, onDemandNonBlocking.ino](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L37). Shouldn't the library have used this same "MDNSEXAMPLE" as the SSID?

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

It appears there is a way to read the SSID, but there is no way to Set it

/**
 * get config portal AP SSID
 * @since 0.0.1
 * @access public
 * @return String the configportal ap name
 */
String WiFiManager::getConfigPortalSSID() {
  return _apName;
}

<!-- gh-comment-id:1999759609 --> @rtek1000 commented on GitHub (Mar 15, 2024): It appears there is a way to [read the SSID](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.cpp#L3226), but there is no way to Set it ```C++ /** * get config portal AP SSID * @since 0.0.1 * @access public * @return String the configportal ap name */ String WiFiManager::getConfigPortalSSID() { return _apName; } ```

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

I managed to solve it, I was missing using:

autoConnect(apName, apPassword)

startConfigPortal(apName, apPassword)

char const * portal_SSID = {"DEVICE1"};
char const * portal_PASSWORD = {"12345678"}; // Need >= 8 chars

wm.autoConnect(portal_SSID, portal_PASSWORD);
wm.startConfigPortal(portal_SSID, portal_PASSWORD);

wm.autoConnect(portal_SSID, portal_PASSWORD);

wm.startConfigPortal(portal_SSID, portal_PASSWORD);

Maybe it would be easier if there was a function to set this, instead of the user declaring the SSID and password on each line they use when the portal starts.

Thank you.

<!-- gh-comment-id:1999890733 --> @rtek1000 commented on GitHub (Mar 15, 2024): I managed to solve it, I was missing using: [autoConnect](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.h#L257C5-L257C81)(apName, apPassword) [startConfigPortal](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.h#L261C1-L261C13)(apName, apPassword) ```C++ char const * portal_SSID = {"DEVICE1"}; char const * portal_PASSWORD = {"12345678"}; // Need >= 8 chars wm.autoConnect(portal_SSID, portal_PASSWORD); wm.startConfigPortal(portal_SSID, portal_PASSWORD); ``` wm.[autoConnect](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L40)(portal_SSID, portal_PASSWORD); wm.[startConfigPortal](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L74)(portal_SSID, portal_PASSWORD); Maybe it would be easier if there was a function to set this, instead of the user declaring the SSID and password on each line they use when the portal starts. Thank you.

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 15, 2024):

Are you confusing mdns hostname and ssid, they are not the same thing.

I suppose there could be a global for setting apname, shrug seems trivial

<!-- gh-comment-id:1999903179 --> @tablatronix commented on GitHub (Mar 15, 2024): Are you confusing mdns hostname and ssid, they are not the same thing. I suppose there could be a global for setting apname, shrug seems trivial

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

Should the onDemandNonBlocking.ino example always be non-blocking?

If the ESP is not connected, how long will the portal wait to go to the loop() routine?

When I comment out the wm.autoConnect() line, then the led blinks, but if I leave the line, the portal is activated and remains active indefinitely.

I used wm.setConfigPortalTimeout(timeout), but it still takes the timeout time to go to loop().

<!-- gh-comment-id:1999936837 --> @rtek1000 commented on GitHub (Mar 15, 2024): Should the [onDemandNonBlocking.ino](https://github.com/tzapu/WiFiManager/blob/master/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino) example always be non-blocking? If the ESP is not connected, how long will the portal wait to go to the loop() routine? When I comment out the wm.autoConnect() [line](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L40), then the led blinks, but if I leave the line, the portal is activated and remains active indefinitely. I used wm.[setConfigPortalTimeout](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.h#L333)(timeout), but it still takes the timeout time to go to loop().

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

Should the onDemandNonBlocking.ino example always be non-blocking?

If the ESP is not connected, how long will the portal wait to go to the loop() routine?

When I comment out the wm.autoConnect() line, then the led blinks, but if I leave the line, the portal is activated and remains active indefinitely.

I used wm.setConfigPortalTimeout(timeout), but it still takes the timeout time to go to loop().

The line needed to be uncommented:

// wm.setConfigPortalBlocking(false);

<!-- gh-comment-id:1999945217 --> @rtek1000 commented on GitHub (Mar 15, 2024): > Should the [onDemandNonBlocking.ino](https://github.com/tzapu/WiFiManager/blob/master/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino) example always be non-blocking? > > If the ESP is not connected, how long will the portal wait to go to the loop() routine? > > When I comment out the wm.autoConnect() [line](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L40), then the led blinks, but if I leave the line, the portal is activated and remains active indefinitely. > > I used wm.[setConfigPortalTimeout](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.h#L333)(timeout), but it still takes the timeout time to go to loop(). The [line](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L39) needed to be uncommented: `// wm.setConfigPortalBlocking(false);`

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

Should the onDemandNonBlocking.ino example always be non-blocking?
If the ESP is not connected, how long will the portal wait to go to the loop() routine?
When I comment out the wm.autoConnect() line, then the led blinks, but if I leave the line, the portal is activated and remains active indefinitely.
I used wm.setConfigPortalTimeout(timeout), but it still takes the timeout time to go to loop().

The line needed to be uncommented:

// wm.setConfigPortalBlocking(false);

If I use the portal Timeout, how can I know if the portal has already been stopped?

Note: On line 599, a form of time control that is not recommended appears to be being implemented, in the case of recycling the variable returned to millis().

    // handle timed out
    if(millis() > _configPortalStart + _configPortalTimeout){
      #ifdef WM_DEBUG_LEVEL
      DEBUG_WM(F("config portal has timed out"));
      #endif
      return true; // timeout bail, else do debug logging
    } 

But on line 607, A recommended form of time control is being implemented

      // log timeout time remaining every 30s
      if((millis() - timer) > logintvl){
        timer = millis();
        #ifdef WM_DEBUG_LEVEL
        DEBUG_WM(WM_DEBUG_VERBOSE,F("Portal Timeout In"),(String)((_configPortalStart + _configPortalTimeout-millis())/1000) + (String)F(" seconds"));
        #endif
      }

<!-- gh-comment-id:1999983299 --> @rtek1000 commented on GitHub (Mar 15, 2024): > > Should the [onDemandNonBlocking.ino](https://github.com/tzapu/WiFiManager/blob/master/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino) example always be non-blocking? > > If the ESP is not connected, how long will the portal wait to go to the loop() routine? > > When I comment out the wm.autoConnect() [line](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L40), then the led blinks, but if I leave the line, the portal is activated and remains active indefinitely. > > I used wm.[setConfigPortalTimeout](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.h#L333)(timeout), but it still takes the timeout time to go to loop(). > > The [line](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/examples/NonBlocking/OnDemandNonBlocking/onDemandNonBlocking.ino#L39) needed to be uncommented: > > `// wm.setConfigPortalBlocking(false);` If I use the portal Timeout, how can I know if the portal has already been stopped? Note: On line [599](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.cpp#L599), a form of time control that is not recommended appears to be being implemented, in the case of recycling the variable returned to millis(). ```C++ // handle timed out if(millis() > _configPortalStart + _configPortalTimeout){ #ifdef WM_DEBUG_LEVEL DEBUG_WM(F("config portal has timed out")); #endif return true; // timeout bail, else do debug logging } ``` But on line [607](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.cpp#L607), A recommended form of time control is being implemented ```C++ // log timeout time remaining every 30s if((millis() - timer) > logintvl){ timer = millis(); #ifdef WM_DEBUG_LEVEL DEBUG_WM(WM_DEBUG_VERBOSE,F("Portal Timeout In"),(String)((_configPortalStart + _configPortalTimeout-millis())/1000) + (String)F(" seconds")); #endif } ```

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 15, 2024):

If I use the portal Timeout, how can I know if the portal has already been stopped?

I found this: getConfigPortalActive()

My sketch now (ESP8266):

• It works like a WiFi router, the user have to press the button for 15 seconds
• • The settings are reset.
• • Wait for user to release button.
• • LED goes out (on NodeMCU off: HIGH)
• The portal is only active for the timeout period, to avoid unnecessary exposure of the portal.
• The LED flashes differently when the portal is active

Sketch:

#include <Arduino.h>

/**
 * OnDemandNonBlocking.ino
 * example of running the webportal or configportal manually and non blocking
 * trigger pin will start a webportal for 120 seconds then turn it off.
 * startAP = true will start both the configportal AP and webportal
 */
#include <WiFiManager.h> // https://github.com/tzapu/WiFiManager

// include MDNS
#ifdef ESP8266
#include <ESP8266mDNS.h>
#elif defined(ESP32)
#include <ESPmDNS.h>
#endif

// select which pin will trigger the configuration portal when set to LOW
#define TRIGGER_PIN 0 // ESP8266 GPIO0 (NodeMCU D3)

#define LED_BUILTIN_D4 2 // ESP8266 GPIO2 (NodeMCU D4)

char const *portal_SSID = {"DEVICE1"};
char const *portal_PASSWORD = {"12345678"}; // Need >= 8 chars

WiFiManager wm;

unsigned int timeout = 120; // seconds to run for
unsigned int startTime = millis();
//bool portalRunning = false;
bool startAP = true; // start AP and webserver if true, else start only webserver

uint32_t millis1 = 0;
uint32_t millis2 = 0;

void doWiFiManager();

void setup()
{
  WiFi.mode(WIFI_STA); // explicitly set mode, esp defaults to STA+AP
  // put your setup code here, to run once
  Serial.begin(115200);
  Serial.setDebugOutput(true);
  delay(1000);
  Serial.println("\n Starting");

  pinMode(TRIGGER_PIN, INPUT_PULLUP);
  pinMode(LED_BUILTIN_D4, OUTPUT);
  digitalWrite(LED_BUILTIN_D4, HIGH);

  wm.setConfigPortalTimeout(timeout);

  // wm.resetSettings();
  wm.setHostname("MDNSEXAMPLE");
  // wm.setEnableConfigPortal(false);
  wm.setConfigPortalBlocking(false);
  // wm.autoConnect();

  wm.autoConnect(portal_SSID, portal_PASSWORD);
}

void loop()
{
#ifdef ESP8266
  MDNS.update();
#endif
  doWiFiManager();
  // put your main code here, to run repeatedly:

  if (wm.getConfigPortalActive() == true)
  {
    if ((millis() - millis2) > 500)
    {
      millis2 = millis();

      digitalWrite(LED_BUILTIN_D4, !digitalRead(LED_BUILTIN_D4));
    }
  } else {
    if ((millis() - millis2) > 5000)
    {
      millis2 = millis();
    }

    if (((millis() - millis2) < 500))
    {
      digitalWrite(LED_BUILTIN_D4, LOW);
    } else if (((millis() - millis2) > 500) && ((millis() - millis2) < 1000))
    {
      digitalWrite(LED_BUILTIN_D4, HIGH);
    }
  }
}

void doWiFiManager()
{
  // is auto timeout portal running
  if (wm.getConfigPortalActive()) //portalRunning
  {
    wm.process(); // do processing

    // check for timeout
    if ((millis() - startTime) > (timeout * 1000))
    {
      Serial.println("portaltimeout");
      //portalRunning = false;
      if (startAP)
      {
        wm.stopConfigPortal();
      }
      else
      {
        wm.stopWebPortal();
      }
    }
  }

  // is configuration portal requested?
  if (digitalRead(TRIGGER_PIN) == LOW && (!wm.getConfigPortalActive())) // !portalRunning
  {
    // Minimum button press time to activate the portal
    if ((millis() - millis1) > 15000)
    {
      digitalWrite(LED_BUILTIN_D4, HIGH);

      // Wait for user to release button
      while(digitalRead(TRIGGER_PIN) == LOW) {
        yield();
      }

      if (startAP)
      {
        Serial.println("Button Pressed, Starting Config Portal");
        wm.resetSettings();
        wm.setConfigPortalBlocking(false);
        wm.startConfigPortal(portal_SSID, portal_PASSWORD);
      }
      else
      {
        Serial.println("Button Pressed, Starting Web Portal");
        wm.startWebPortal();
      }
      //portalRunning = true;
      startTime = millis();
    }
    else
    {
      digitalWrite(LED_BUILTIN_D4, LOW);
    }
  }
  else
  {
    millis1 = millis();
  }
}

(Now I think I can go to the part "auto update via email")

Thank you.

<!-- gh-comment-id:2000106643 --> @rtek1000 commented on GitHub (Mar 15, 2024): > If I use the portal Timeout, how can I know if the portal has already been stopped? I found this: [getConfigPortalActive()](https://github.com/tzapu/WiFiManager/blob/d82d0a1b9fca741b9ec44accdf553606a6576dda/WiFiManager.h#L489) My sketch now (ESP8266): - It works like a WiFi router, the user have to press the button for 15 seconds - - The settings are reset. - - Wait for user to release button. - - LED goes out (on NodeMCU off: HIGH) - The portal is only active for the timeout period, to avoid unnecessary exposure of the portal. - The LED flashes differently when the portal is active Sketch: ```C++ #include <Arduino.h> /** * OnDemandNonBlocking.ino * example of running the webportal or configportal manually and non blocking * trigger pin will start a webportal for 120 seconds then turn it off. * startAP = true will start both the configportal AP and webportal */ #include <WiFiManager.h> // https://github.com/tzapu/WiFiManager // include MDNS #ifdef ESP8266 #include <ESP8266mDNS.h> #elif defined(ESP32) #include <ESPmDNS.h> #endif // select which pin will trigger the configuration portal when set to LOW #define TRIGGER_PIN 0 // ESP8266 GPIO0 (NodeMCU D3) #define LED_BUILTIN_D4 2 // ESP8266 GPIO2 (NodeMCU D4) char const *portal_SSID = {"DEVICE1"}; char const *portal_PASSWORD = {"12345678"}; // Need >= 8 chars WiFiManager wm; unsigned int timeout = 120; // seconds to run for unsigned int startTime = millis(); //bool portalRunning = false; bool startAP = true; // start AP and webserver if true, else start only webserver uint32_t millis1 = 0; uint32_t millis2 = 0; void doWiFiManager(); void setup() { WiFi.mode(WIFI_STA); // explicitly set mode, esp defaults to STA+AP // put your setup code here, to run once Serial.begin(115200); Serial.setDebugOutput(true); delay(1000); Serial.println("\n Starting"); pinMode(TRIGGER_PIN, INPUT_PULLUP); pinMode(LED_BUILTIN_D4, OUTPUT); digitalWrite(LED_BUILTIN_D4, HIGH); wm.setConfigPortalTimeout(timeout); // wm.resetSettings(); wm.setHostname("MDNSEXAMPLE"); // wm.setEnableConfigPortal(false); wm.setConfigPortalBlocking(false); // wm.autoConnect(); wm.autoConnect(portal_SSID, portal_PASSWORD); } void loop() { #ifdef ESP8266 MDNS.update(); #endif doWiFiManager(); // put your main code here, to run repeatedly: if (wm.getConfigPortalActive() == true) { if ((millis() - millis2) > 500) { millis2 = millis(); digitalWrite(LED_BUILTIN_D4, !digitalRead(LED_BUILTIN_D4)); } } else { if ((millis() - millis2) > 5000) { millis2 = millis(); } if (((millis() - millis2) < 500)) { digitalWrite(LED_BUILTIN_D4, LOW); } else if (((millis() - millis2) > 500) && ((millis() - millis2) < 1000)) { digitalWrite(LED_BUILTIN_D4, HIGH); } } } void doWiFiManager() { // is auto timeout portal running if (wm.getConfigPortalActive()) //portalRunning { wm.process(); // do processing // check for timeout if ((millis() - startTime) > (timeout * 1000)) { Serial.println("portaltimeout"); //portalRunning = false; if (startAP) { wm.stopConfigPortal(); } else { wm.stopWebPortal(); } } } // is configuration portal requested? if (digitalRead(TRIGGER_PIN) == LOW && (!wm.getConfigPortalActive())) // !portalRunning { // Minimum button press time to activate the portal if ((millis() - millis1) > 15000) { digitalWrite(LED_BUILTIN_D4, HIGH); // Wait for user to release button while(digitalRead(TRIGGER_PIN) == LOW) { yield(); } if (startAP) { Serial.println("Button Pressed, Starting Config Portal"); wm.resetSettings(); wm.setConfigPortalBlocking(false); wm.startConfigPortal(portal_SSID, portal_PASSWORD); } else { Serial.println("Button Pressed, Starting Web Portal"); wm.startWebPortal(); } //portalRunning = true; startTime = millis(); } else { digitalWrite(LED_BUILTIN_D4, LOW); } } else { millis1 = millis(); } } ``` (Now I think I can go to the part ["auto update via email"](https://github.com/mobizt/ESP-Mail-Client/blob/5c6e231e181ff863a325bba38eb692e88c087abb/examples/IMAP/Firmware_Update_Attachment/Firmware_Update_Attachment.ino)) Thank you.

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 16, 2024):

The ondemand part is non blocking but not autoconnect is not in that example, // wm.setConfigPortalBlocking(false);

I see the millis rollover issue, thanks

Looks like you figured the rest out. I suggest you read the .h file the super example and the wiki https://github.com/tzapu/WiFiManager/wiki/Methods

The actual readme still needs work as do general docs

<!-- gh-comment-id:2001489518 --> @tablatronix commented on GitHub (Mar 16, 2024): The ondemand part is non blocking but not autoconnect is not in that example, // wm.setConfigPortalBlocking(false); I see the millis rollover issue, thanks Looks like you figured the rest out. I suggest you read the .h file the super example and the wiki https://github.com/tzapu/WiFiManager/wiki/Methods The actual readme still needs work as do general docs

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@rtek1000 commented on GitHub (Mar 18, 2024):

Hello, I would like to suggest that an example be made available (if possible) with a login to access the portal, it is the standard for almost all routers I have seen, I found a project that has this, perhaps it could serve as an example of how to implement it :

https://github.com/rtek1000/esp32-asyncwebserver-fileupload-example/tree/master/example-02

Login to access the portal:

Additional page that a commercial router shows if the user is unable to log in:

info.zip

<!-- gh-comment-id:2002787248 --> @rtek1000 commented on GitHub (Mar 18, 2024): Hello, I would like to suggest that an example be made available (if possible) with a login to access the portal, it is the standard for almost all routers I have seen, I found a project that has this, perhaps it could serve as an example of how to implement it : https://github.com/rtek1000/esp32-asyncwebserver-fileupload-example/tree/master/example-02 Login to access the portal:  Additional page that a commercial router shows if the user is unable to log in:  [info.zip](https://github.com/tzapu/WiFiManager/files/14630384/info.zip)

kerem commented 2026-02-28 01:30:10 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Mar 19, 2024):

#1669

<!-- gh-comment-id:2005566026 --> @tablatronix commented on GitHub (Mar 19, 2024): #1669

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#1460

No description provided.