[GH-ISSUE #1589] wifiManager.setConfigPortalTimeout should only time out if no client connected to AP #1354

New issue

Closed

opened 2026-02-28 01:29:44 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 01:29:44 +03:00

Owner

Originally created by @probonopd on GitHub (Apr 16, 2023).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1589

E.g., when we set a 180 seconds timeout like this: wifiManager.setConfigPortalTimeout(180);

The 180 seconds timeout should be t for the user to connect to the access point and open the configuration portal. Once the user has connected to the access point and opened the configuration portal, the user should be able to take as much time as they need to enter the WiFi credentials and save them (not just 180 seconds).

Or is that already the case?

Originally created by @probonopd on GitHub (Apr 16, 2023). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1589 E.g., when we set a 180 seconds timeout like this: `wifiManager.setConfigPortalTimeout(180);` The 180 seconds timeout should be t for the user to connect to the access point and open the configuration portal. Once the user has connected to the access point and opened the configuration portal, the user should be able to take as much time as they need to enter the WiFi credentials and save them (not just 180 seconds). Or is that already the case?

kerem

2026-02-28 01:29:44 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-28 01:29:44 +03:00

Author

Owner

@Catta1997 commented on GitHub (Apr 20, 2023):

I think that it wait, since the description say "Check for connection and if it's still not established do whatever is needed" but im not 100% sure. You can also use setConfigPortalBlocking(boolean shouldBlock) , but as description say user is responsible for closing configportal.

@Catta1997 commented on GitHub (Apr 20, 2023): I think that it wait, since the description say "Check for connection and if it's still not established do whatever is needed" but im not 100% sure. You can also use `setConfigPortalBlocking(boolean shouldBlock)` , but as description say user is responsible for closing configportal.

kerem commented

2026-02-28 01:29:44 +03:00

Author

Owner

@tablatronix commented on GitHub (Apr 23, 2023):

The timer is reset everytime an http connection is made, but I agree you could timeout on that page filling out params..

boolean       _apClientCheck          = false; // keep cp alive if ap have station
boolean       _webClientCheck         = true;  // keep cp alive if web have client

I guess we could add some background XHR keepalive, or you can use the apclientcheck , but sometimes it stays showing a client so is not enabled.

@tablatronix commented on GitHub (Apr 23, 2023): The timer is reset everytime an http connection is made, but I agree you could timeout on that page filling out params.. boolean _apClientCheck = false; // keep cp alive if ap have station boolean _webClientCheck = true; // keep cp alive if web have client I guess we could add some background XHR keepalive, or you can use the apclientcheck , but sometimes it stays showing a client so is not enabled.