starred/WiFiManager
1
0
Fork 0
mirror of https://github.com/tzapu/WiFiManager.git synced 2026-04-28 01:25:49 +03:00
Code Issues 656 Projects Releases 8 Packages Wiki Activity

[GH-ISSUE #1103] calling setDebugOutput(false) causes autoconnect to fail and go straight to config (DEV BRANCH 2.0.3) #943

New issue
Closed
opened 2026-02-28 01:27:47 +03:00 by kerem · 6 comments
kerem commented 2026-02-28 01:27:47 +03:00
Owner
Copy link

Originally created by @tavdog on GitHub (Aug 2, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1103

Basic Infos

Using Adafruit featheresp32 target with platformio. Problem is not present on Adafruit huzzahesp8266

Hardware

WiFimanager Branch/Release:

  • Master
  • Development

Esp8266/Esp32:

  • ESP8266
  • ESP32

Hardware: ESP-12e, esp01, esp25

  • ESP01
  • ESP12 E/F/S (nodemcu, wemos, feather)
  • Other

ESP Core Version: 2.4.0, staging

  • 2.3.0
  • 2.4.0
  • staging (master/dev)

Description

With wifi already configured, if device is flashed with code that executes wm.setDebugOutput(false) autoconnect fails immiediatly (does not wait for connect timeout) and goes straight to config portal. The device connects file if calling wm.setDebugOutput(true) or line ommitted.

Settings in IDE

Module: featheresp32

Additional libraries:

Sketch

WiFiManagerParameter custom_brightness("brightness", "Brightness : High/Med/Low/Auto", config->brightness.c_str(), 5);
    WiFiManagerParameter custom_user("api_user", "Username : user@example.com", config->api_username.c_str(), 25);
    WiFiManagerParameter custom_password("api_password", "Password", config->api_password.c_str(), 32);

    //add all your parameters here
    wm.addParameter(&custom_brightness);
    wm.addParameter(&custom_user);
    wm.addParameter(&custom_password);

    // set the AP callback to display AP on display
    wm.setAPCallback(display_AP);

    //automatically connect using saved credentials if they exist
    //If connection fails it starts an access point with the specified name
    //here  "AutoConnectAP" if empty will auto generate basedcon chipid, if password is blank it will be anonymous
    //and goes into a blocking loop awaiting configuration
    wm.setConfigPortalTimeout(60);
    wm.setConnectTimeout(15);
    //wm.setDebugOutput(false);
    if (force_config) {
      wm.startConfigPortal(ap_name);
    } else {
      wm.autoConnect(ap_name);
    }

    Serial.println("connected");

Debug Messages

FAILURE OUTPUT :
MAC:2462ABDADC38
entering wifi_setup
*WM: [3] allocating params bytes: 20
*WM: [2] Added Parameter: brightness
*WM: [2] Added Parameter: api_user
*WM: [2] Added Parameter: api_password

SUCCESS OUTPUT:
entering wifi_setup
*WM: [3] allocating params bytes: 20
*WM: [2] Added Parameter: brightness
*WM: [2] Added Parameter: api_user
*WM: [2] Added Parameter: api_password
*WM: [1] Free heap:        309244
*WM: [1] ESP SDK version:  v3.2.3-14-gd3e562907
*WM: [1] AutoConnect 
*WM: [2] ESP32 event handler enabled 
*WM: [2] Connecting as wifi client... 
*WM: [3] STA static IP:
*WM: [2] setSTAConfig static ip not set, skipping 
*WM: [1] Connecting to SAVED AP: windytron
*WM: [3] Using Password: aaaaaaaa
*WM: [3] WiFi station enable 
*WM: [2] 15000 ms connectTimeout set
*WM: [2] 15000 ms timeout, waiting for connect...
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] . 
*WM: [2] Connection result: WL_CONNECTED
*WM: [3] lastconxresult: WL_CONNECTED
*WM: [1] AutoConnect: SUCCESS 
*WM: [1] STA IP Address: 192.168.43.31
Originally created by @tavdog on GitHub (Aug 2, 2020). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1103 # Basic Infos Using Adafruit featheresp32 target with platformio. Problem is not present on Adafruit huzzahesp8266 #### Hardware **WiFimanager Branch/Release:** - [ ] Master - [x] Development **Esp8266/Esp32:** - [ ] ESP8266 - [x] ESP32 **Hardware: ESP-12e, esp01, esp25** - [ ] ESP01 - [ ] ESP12 E/F/S (nodemcu, wemos, feather) - [x] Other **ESP Core Version: 2.4.0, staging** - [ ] 2.3.0 - [ ] 2.4.0 - [ ] staging (master/dev) ### Description With wifi already configured, if device is flashed with code that executes wm.setDebugOutput(false) autoconnect fails immiediatly (does not wait for connect timeout) and goes straight to config portal. The device connects file if calling wm.setDebugOutput(true) or line ommitted. ### Settings in IDE Module: featheresp32 Additional libraries: ### Sketch ```cpp WiFiManagerParameter custom_brightness("brightness", "Brightness : High/Med/Low/Auto", config->brightness.c_str(), 5); WiFiManagerParameter custom_user("api_user", "Username : user@example.com", config->api_username.c_str(), 25); WiFiManagerParameter custom_password("api_password", "Password", config->api_password.c_str(), 32); //add all your parameters here wm.addParameter(&custom_brightness); wm.addParameter(&custom_user); wm.addParameter(&custom_password); // set the AP callback to display AP on display wm.setAPCallback(display_AP); //automatically connect using saved credentials if they exist //If connection fails it starts an access point with the specified name //here "AutoConnectAP" if empty will auto generate basedcon chipid, if password is blank it will be anonymous //and goes into a blocking loop awaiting configuration wm.setConfigPortalTimeout(60); wm.setConnectTimeout(15); //wm.setDebugOutput(false); if (force_config) { wm.startConfigPortal(ap_name); } else { wm.autoConnect(ap_name); } Serial.println("connected"); ``` ### Debug Messages ``` FAILURE OUTPUT : MAC:2462ABDADC38 entering wifi_setup *WM: [3] allocating params bytes: 20 *WM: [2] Added Parameter: brightness *WM: [2] Added Parameter: api_user *WM: [2] Added Parameter: api_password SUCCESS OUTPUT: entering wifi_setup *WM: [3] allocating params bytes: 20 *WM: [2] Added Parameter: brightness *WM: [2] Added Parameter: api_user *WM: [2] Added Parameter: api_password *WM: [1] Free heap: 309244 *WM: [1] ESP SDK version: v3.2.3-14-gd3e562907 *WM: [1] AutoConnect *WM: [2] ESP32 event handler enabled *WM: [2] Connecting as wifi client... *WM: [3] STA static IP: *WM: [2] setSTAConfig static ip not set, skipping *WM: [1] Connecting to SAVED AP: windytron *WM: [3] Using Password: aaaaaaaa *WM: [3] WiFi station enable *WM: [2] 15000 ms connectTimeout set *WM: [2] 15000 ms timeout, waiting for connect... *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] . *WM: [2] Connection result: WL_CONNECTED *WM: [3] lastconxresult: WL_CONNECTED *WM: [1] AutoConnect: SUCCESS *WM: [1] STA IP Address: 192.168.43.31 ```
kerem 2026-02-28 01:27:47 +03:00
kerem commented 2026-02-28 01:27:48 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Aug 2, 2020):

I dont understand this says

*WM: [2] Connection result: WL_CONNECTED
*WM: [3] lastconxresult: WL_CONNECTED
*WM: [1] AutoConnect: SUCCESS 
*WM: [1] STA IP Address: 192.168.43.31

Which is not cp ...

<!-- gh-comment-id:667694011 --> @tablatronix commented on GitHub (Aug 2, 2020): I dont understand this says ``` *WM: [2] Connection result: WL_CONNECTED *WM: [3] lastconxresult: WL_CONNECTED *WM: [1] AutoConnect: SUCCESS *WM: [1] STA IP Address: 192.168.43.31 ``` Which is not cp ...
kerem commented 2026-02-28 01:27:48 +03:00
Author
Owner
Copy link

@tavdog commented on GitHub (Aug 2, 2020):

That is output when debugOutput is at default or set to true. The failure case is the first pasted block
FAILURE OUTPUT when debugOutput is set to false

MAC:2462ABDADC38
entering wifi_setup
*WM: [3] allocating params bytes: 20
*WM: [2] Added Parameter: brightness
*WM: [2] Added Parameter: api_user
*WM: [2] Added Parameter: api_password

Here output stops and it goes straight into configportal without connectiong.

<!-- gh-comment-id:667735348 --> @tavdog commented on GitHub (Aug 2, 2020): That is output when debugOutput is at default or set to true. The failure case is the first pasted block FAILURE OUTPUT when debugOutput is set to false ``` MAC:2462ABDADC38 entering wifi_setup *WM: [3] allocating params bytes: 20 *WM: [2] Added Parameter: brightness *WM: [2] Added Parameter: api_user *WM: [2] Added Parameter: api_password ``` Here output stops and it goes straight into configportal without connectiong.
kerem commented 2026-02-28 01:27:48 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Aug 2, 2020):

Hmm ill test it here and see if I can reproduce.

<!-- gh-comment-id:667741795 --> @tablatronix commented on GitHub (Aug 2, 2020): Hmm ill test it here and see if I can reproduce.
kerem commented 2026-02-28 01:27:48 +03:00
Author
Owner
Copy link

@tavdog commented on GitHub (Aug 3, 2020):

The logging stops because it is at that point that setDebugOutput(false) is called. My hunch is that it might just be a weird issue with esp32 and timing. Since it takes more cycles to print out the debugging info it gives the esp32 more time to connect in the background maybe ? I'll test by adding a delay and see if that helps.
Here is more of the preceding code that shows the parameters added then the debug call.

//add all your parameters here
    wm.addParameter(&custom_brightness);
    wm.addParameter(&custom_user);
    wm.addParameter(&custom_password);

    // set the AP callback to display AP on display
    wm.setAPCallback(display_AP);

    //automatically connect using saved credentials if they exist
    //If connection fails it starts an access point with the specified name
    //here  "AutoConnectAP" if empty will auto generate basedcon chipid, if password is blank it will be anonymous
    //and goes into a blocking loop awaiting configuration
    wm.setConfigPortalTimeout(60);
    wm.setConnectTimeout(15);
    wm.setDebugOutput(false);
    if (force_config) {
      wm.startConfigPortal(ap_name);
    } else {
      wm.autoConnect(ap_name);
    }

    Serial.println("connected");

...... nope. setting a 10sec delay did not help.

<!-- gh-comment-id:667749436 --> @tavdog commented on GitHub (Aug 3, 2020): The logging stops because it is at that point that setDebugOutput(false) is called. My hunch is that it might just be a weird issue with esp32 and timing. Since it takes more cycles to print out the debugging info it gives the esp32 more time to connect in the background maybe ? I'll test by adding a delay and see if that helps. Here is more of the preceding code that shows the parameters added then the debug call. ``` //add all your parameters here wm.addParameter(&custom_brightness); wm.addParameter(&custom_user); wm.addParameter(&custom_password); // set the AP callback to display AP on display wm.setAPCallback(display_AP); //automatically connect using saved credentials if they exist //If connection fails it starts an access point with the specified name //here "AutoConnectAP" if empty will auto generate basedcon chipid, if password is blank it will be anonymous //and goes into a blocking loop awaiting configuration wm.setConfigPortalTimeout(60); wm.setConnectTimeout(15); wm.setDebugOutput(false); if (force_config) { wm.startConfigPortal(ap_name); } else { wm.autoConnect(ap_name); } Serial.println("connected"); ``` ...... nope. setting a 10sec delay did not help.
kerem commented 2026-02-28 01:27:48 +03:00
Author
Owner
Copy link

@tavdog commented on GitHub (Aug 3, 2020):

Found it ! removing the line : wm.setConnectTimeout(15); fixed it. Also calling with a much larger number (15000) fixes it.
Hmm. Well, thanks for your time and a great library.

<!-- gh-comment-id:667751469 --> @tavdog commented on GitHub (Aug 3, 2020): Found it ! removing the line : wm.setConnectTimeout(15); fixed it. Also calling with a much larger number (15000) fixes it. Hmm. Well, thanks for your time and a great library.
kerem commented 2026-02-28 01:27:48 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Aug 3, 2020):

There is an ongoing ESP32 bug that several people with certain routers are having where connections take a very long time, if you remove the timeout it will use the default esp32 connect wait loop.

I think may be you experiencing this issue , where it always fails on first connection.

I find it odd that you thought debugoutput had something to do with it.. that is a bit odd if it was true.

#1067

<!-- gh-comment-id:668048894 --> @tablatronix commented on GitHub (Aug 3, 2020): There is an ongoing ESP32 bug that several people with certain routers are having where connections take a very long time, if you remove the timeout it will use the default esp32 connect wait loop. I think may be you experiencing this issue , where it always fails on first connection. I find it odd that you thought debugoutput had something to do with it.. that is a bit odd if it was true. #1067
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
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#943
No description provided.