[GH-ISSUE #92] setTimeout not work properly #69

New issue

Closed

opened 2026-02-28 01:23:13 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 01:23:13 +03:00

Owner

Originally created by @chuxuanhy on GitHub (Feb 4, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/92

Hello,

I am using ESP12E with version 2.1. rc2 and wifimanager 0.9.
I set timeout to 180 seconds. Correct uid and password was saved. Wifi signal was also pretty good (above 80%). The ESP12E gave up quickly to try to connect to the Internet (about 3-4 seconds not as long as the timeout was set) at power on, then the config portal displayed in the wifi list. It was also randomly to make successful or fail connection at the time of powering on. I used AutoConnect, please check this!

Originally created by @chuxuanhy on GitHub (Feb 4, 2016). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/92 Hello, I am using ESP12E with version 2.1. rc2 and wifimanager 0.9. I set timeout to 180 seconds. Correct uid and password was saved. Wifi signal was also pretty good (above 80%). The ESP12E gave up quickly to try to connect to the Internet (about 3-4 seconds not as long as the timeout was set) at power on, then the config portal displayed in the wifi list. It was also randomly to make successful or fail connection at the time of powering on. I used AutoConnect, please check this!

kerem closed this issue

2026-02-28 01:23:13 +03:00

kerem commented

2026-02-28 01:23:14 +03:00

Author

Owner

@tzapu commented on GitHub (Feb 5, 2016):

hi, as it is, the timeout is from the moment wifimanager is intialised, so it would be 180 seconds from the moment you booted pretty much.

i am reconsidering this
cheers

@tzapu commented on GitHub (Feb 5, 2016): hi, as it is, the timeout is from the moment wifimanager is intialised, so it would be 180 seconds from the moment you booted pretty much. i am reconsidering this cheers

kerem commented

2026-02-28 01:23:14 +03:00

Author

Owner

@chuxuanhy commented on GitHub (Feb 6, 2016):

There must be an issue, I also tried increasing the timeout (to hour) but it helped nothing. ESP12E did not try to reconnect to the internet. It just gave up and started the config portal.

I ran the OnDemandConfigPortal example, gave corrent credentials, had good wifi signal, but could not connect to the Internet. Please recheck the sketch!

@chuxuanhy commented on GitHub (Feb 6, 2016): There must be an issue, I also tried increasing the timeout (to hour) but it helped nothing. ESP12E did not try to reconnect to the internet. It just gave up and started the config portal. I ran the OnDemandConfigPortal example, gave corrent credentials, had good wifi signal, but could not connect to the Internet. Please recheck the sketch!

kerem commented

2026-02-28 01:23:14 +03:00

Author

Owner

@tzapu commented on GitHub (Feb 7, 2016):

hi, you may be misunderstanding the timeout parameter.
what it is is a time it waits in the config portal, not how long it tries to connect.
when timeout is reached, WiFiManager terminates itself and returns control to your sketch.

@tzapu commented on GitHub (Feb 7, 2016): hi, you may be misunderstanding the timeout parameter. what it is is a time it waits in the config portal, not how long it tries to connect. when timeout is reached, WiFiManager terminates itself and returns control to your sketch.

kerem commented

2026-02-28 01:23:14 +03:00

Author

Owner

@chuxuanhy commented on GitHub (Feb 7, 2016):

Oh, I misunderstood the timeout parameter completely! May you help me to modify the sketch to make it try to reconnect in an interval of time? The issue is that it randomly failed to connect to the internet at the time of powering on. Please help me!

@chuxuanhy commented on GitHub (Feb 7, 2016): Oh, I misunderstood the timeout parameter completely! May you help me to modify the sketch to make it try to reconnect in an interval of time? The issue is that it randomly failed to connect to the internet at the time of powering on. Please help me!

kerem commented

2026-02-28 01:23:14 +03:00

Author

Owner

@tzapu commented on GitHub (Feb 8, 2016):

hi, try the example AutoConnectWithTimeout.
If it doesn t manage to connect in 3 minutes, it will reset the module and try again.
Will that do it for you?

@tzapu commented on GitHub (Feb 8, 2016): hi, try the example AutoConnectWithTimeout. If it doesn t manage to connect in 3 minutes, it will reset the module and try again. Will that do it for you?