[GH-ISSUE #431] On Demand Configuration or AutoConnect; but not both? #362

New issue

Closed

opened 2026-02-28 01:24:56 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 01:24:56 +03:00

Owner

Originally created by @JSCSJSCS on GitHub (Sep 29, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/431

In the Documentation it says:

On Demand Configuration Portal

If you would rather start the configuration portal on demand rather than automatically on a failed connection attempt, then this is for you.

Instead of calling autoConnect() which does all the connecting and failover configuration portal setup for you, you need to use startConfigPortal(). Do not use BOTH.

I have a project where the ESP8266 has to be given a distance input (how far away an object is). Because the sensor is not very accurate, it can be a trial and error to set it correctly. I was going to use this On Demand Configuration Portal to have the user press a button to enter AP configuration mode were they could re-enter the distance input (like changing MQTT server, topics, etc.), but it looks like the ESP8266 will lose it's "automatic" capabilities if I do this? Either it works automatically or you have to push a button, but not both? Is this how it works? Maybe this is not the best approach in my use case. Any suggestions?

Originally created by @JSCSJSCS on GitHub (Sep 29, 2017). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/431 In the Documentation it says: > On Demand Configuration Portal > > If you would rather start the configuration portal on demand rather than automatically on a failed connection attempt, then this is for you. > > Instead of calling autoConnect() which does all the connecting and failover configuration portal setup for you, you need to use startConfigPortal(). **Do not use BOTH**. I have a project where the ESP8266 has to be given a distance input (how far away an object is). Because the sensor is not very accurate, it can be a trial and error to set it correctly. I was going to use this On Demand Configuration Portal to have the user press a button to enter AP configuration mode were they could re-enter the distance input (like changing MQTT server, topics, etc.), but it looks like the ESP8266 will lose it's "automatic" capabilities if I do this? Either it works automatically or you have to push a button, but not both? Is this how it works? Maybe this is not the best approach in my use case. Any suggestions?

kerem closed this issue

2026-02-28 01:24:57 +03:00

kerem commented

2026-02-28 01:24:57 +03:00

Author

Owner

@tablatronix commented on GitHub (Sep 29, 2017):

That means do not use both together in normal use, you can still combine them.

@tablatronix commented on GitHub (Sep 29, 2017): That means do not use both together in normal use, you can still combine them.

kerem commented

2026-02-28 01:24:57 +03:00

Author

Owner

@JSCSJSCS commented on GitHub (Sep 29, 2017):

@tablatronix Thanks. Can't wait to try it.

@JSCSJSCS commented on GitHub (Sep 29, 2017): @tablatronix Thanks. Can't wait to try it.

kerem commented

2026-02-28 01:24:57 +03:00

Author

Owner

@skx commented on GitHub (Jan 8, 2018):