starred/WiFiManager

Fork 0

mirror of https://github.com/tzapu/WiFiManager.git synced 2026-04-27 00:55:52 +03:00

[GH-ISSUE #542] ESP32 Testing doesn't get past WiFi.enableSTA(true) #455

New issue

Closed

opened 2026-02-28 01:25:23 +03:00 by kerem · 14 comments

kerem commented

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

Owner

Originally created by @renegadeandy on GitHub (Mar 1, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/542

I can't seem to get very far using the development branch.

Basic Infos

Using ESP32 dev board oooouuuu board.

Hardware

WiFimanager Branch/Release: Development

Hardware: ESP32

Core Version: 2.4.0, staging

Description

When I try to incorporate the dev WiFiManager into an old project which ran fine on esp8266, It seems to hang and crash directly after WiFi.enableSTA(true);

My call from main sketch is as follows:


 //Start WiFi Setup
  Serial.println("Setting up WiFi...");
  WiFiManager wifiManager;
  wifiManager.autoConnect("AP Setup", NULL);

The added Debug to autoconnect is as follows:


boolean WiFiManager::autoConnect(char const *apName, char const *apPassword) {
  DEBUG_WM(F("AutoConnect"));
 //digitalWrite(apLED,HIGH);
  // attempt to connect using saved settings, on fail fallback to AP config portal
    DEBUG_WM(F("2"));
  WiFi.enableSTA(true);
    DEBUG_WM(F("22"));
  _usermode = WIFI_STA;
  DEBUG_WM(F("222"));

Note my debug output is:

Setting up WiFi...
*WM: AutoConnect 
*WM: 2

As we can see, we never hit the *WM: 22 message, The sketch appears to simply hang. Is there some kind of setup I need to do? Do I need to declare I am on an ESP32 to the library somehow?

Settings in IDE

Module: ESP32 DEV BOARD

Originally created by @renegadeandy on GitHub (Mar 1, 2018). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/542 I can't seem to get very far using the development branch. ### Basic Infos Using ESP32 dev board oooouuuu board. #### Hardware WiFimanager Branch/Release: Development Hardware: ESP32 Core Version: 2.4.0, staging ### Description When I try to incorporate the dev WiFiManager into an old project which ran fine on esp8266, It seems to hang and crash directly after WiFi.enableSTA(true); My call from main sketch is as follows: ``` //Start WiFi Setup Serial.println("Setting up WiFi..."); WiFiManager wifiManager; wifiManager.autoConnect("AP Setup", NULL); ``` The added Debug to autoconnect is as follows: ``` boolean WiFiManager::autoConnect(char const *apName, char const *apPassword) { DEBUG_WM(F("AutoConnect")); //digitalWrite(apLED,HIGH); // attempt to connect using saved settings, on fail fallback to AP config portal DEBUG_WM(F("2")); WiFi.enableSTA(true); DEBUG_WM(F("22")); _usermode = WIFI_STA; DEBUG_WM(F("222")); ``` Note my debug output is: ``` Setting up WiFi... *WM: AutoConnect *WM: 2 ``` As we can see, we never hit the *WM: 22 message, The sketch appears to simply hang. Is there some kind of setup I need to do? Do I need to declare I am on an ESP32 to the library somehow? ### Settings in IDE Module: ESP32 DEV BOARD

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

Whats the debug from wifimanager???

@tablatronix commented on GitHub (Mar 1, 2018): Whats the debug from wifimanager???

kerem commented

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

Author

Owner

@renegadeandy commented on GitHub (Mar 1, 2018):

How do I turn that on? Not sure what you mean?

@renegadeandy commented on GitHub (Mar 1, 2018): How do I turn that on? Not sure what you mean?

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

It should be on, unless you are setting it to off in your code.
It outputs lots of info

@tablatronix commented on GitHub (Mar 1, 2018): It should be on, unless you are setting it to off in your code. It outputs lots of info

kerem commented

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

Author

Owner

@renegadeandy commented on GitHub (Mar 1, 2018):

I see no debug output at all in my code, apart from what i've shown to you above?

@renegadeandy commented on GitHub (Mar 1, 2018): I see no debug output at all in my code, apart from what i've shown to you above?

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

hmmm

@tablatronix commented on GitHub (Mar 1, 2018): hmmm

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

works for me

*WM: AutoConnect 
*WM: ESP32 event handler enabled 
*WM: Connecting as wifi client... 
*WM: wifi station disconnect 
*WM: Connecting to saved AP 
*WM: connectTimeout not set, ESP waitForConnectResult... 
WM: EVENT: WIFI_REASON: 201
*WM: Event: SYSTEM_EVENT_STA_DISCONNECTED, reconnecting
*WM: Connection result: WL_NO_SSID_AVAIL
*WM: lastconxresult: WL_NO_SSID_AVAIL
*WM: wifi station disconnect 
*WM: Disabling STA 
*WM: Enabling AP 
*WM: StartAP with SSID:  AutoConnectAP
*WM: AP has anonymous access! 
*WM: SoftAP Configuration 
*WM: -------------------- 
*WM: ssid:             AutoConnectAP
*WM: password:         
*WM: ssid_len:         13
*WM: channel:          1
*WM: authmode:        
*WM: ssid_hidden:     
*WM: max_connection:   4
*WM: beacon_interval:  100(ms)
*WM: -------------------- 
*WM: AP IP address: 192.168.4.1
*WM: setupConfigPortal 
*WM: Starting Web Portal 
*WM: HTTP server started 
*WM: Scan done 
*WM: Config Portal Running, blocking, waiting for clients...

@tablatronix commented on GitHub (Mar 1, 2018): works for me ``` *WM: AutoConnect *WM: ESP32 event handler enabled *WM: Connecting as wifi client... *WM: wifi station disconnect *WM: Connecting to saved AP *WM: connectTimeout not set, ESP waitForConnectResult... WM: EVENT: WIFI_REASON: 201 *WM: Event: SYSTEM_EVENT_STA_DISCONNECTED, reconnecting *WM: Connection result: WL_NO_SSID_AVAIL *WM: lastconxresult: WL_NO_SSID_AVAIL *WM: wifi station disconnect *WM: Disabling STA *WM: Enabling AP *WM: StartAP with SSID: AutoConnectAP *WM: AP has anonymous access! *WM: SoftAP Configuration *WM: -------------------- *WM: ssid: AutoConnectAP *WM: password: *WM: ssid_len: 13 *WM: channel: 1 *WM: authmode: *WM: ssid_hidden: *WM: max_connection: 4 *WM: beacon_interval: 100(ms) *WM: -------------------- *WM: AP IP address: 192.168.4.1 *WM: setupConfigPortal *WM: Starting Web Portal *WM: HTTP server started *WM: Scan done *WM: Config Portal Running, blocking, waiting for clients... ```

kerem commented

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

Author

Owner

@renegadeandy commented on GitHub (Mar 1, 2018):

Ahh, well you see you never get past WiFi.enableSTA(true); so the rest of the debug output never gets executed!

@renegadeandy commented on GitHub (Mar 1, 2018): Ahh, well you see you never get past WiFi.enableSTA(true); so the rest of the debug output never gets executed!

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

ohh, well that is not wifimanager then, there is nothing in that function to get stuck, is your module crashing?

you should have an exception or something

@tablatronix commented on GitHub (Mar 1, 2018): ohh, well that is not wifimanager then, there is nothing in that function to get stuck, is your module crashing? you should have an exception or something

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

enable esp debugging also maybe?

@tablatronix commented on GitHub (Mar 1, 2018): enable esp debugging also maybe?

kerem commented

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

Author

Owner

@renegadeandy commented on GitHub (Mar 1, 2018):

No, although I have made a couple of alterations, and now I see

Brownout detector was triggered....

Wondering if this is a USB power problem...

@renegadeandy commented on GitHub (Mar 1, 2018): No, although I have made a couple of alterations, and now I see Brownout detector was triggered.... Wondering if this is a USB power problem...

kerem commented

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

Author

Owner

@renegadeandy commented on GitHub (Mar 1, 2018):

Yes! This was the problem, a really rubbish USB Hub, time to put that one back into the garage, sorry tablatronix!

@renegadeandy commented on GitHub (Mar 1, 2018): Yes! This was the problem, a really rubbish USB Hub, time to put that one back into the garage, sorry tablatronix!

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):

Yeah power issue, below 300 ma or so, the wifi radio cannot turn on

@tablatronix commented on GitHub (Mar 1, 2018): Yeah power issue, below 300 ma or so, the wifi radio cannot turn on

kerem commented

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

Author

Owner

@tablatronix commented on GitHub (Mar 1, 2018):