starred/WiFiManager
1
0
Fork 0
mirror of https://github.com/tzapu/WiFiManager.git synced 2026-04-27 09:05:56 +03:00
Code Issues 656 Projects Releases 8 Packages Wiki Activity

[GH-ISSUE #1326] Hundreds of "*wm:[2] [EVENT] WIFI_REASON: 8" logs when I disconnect() #1140

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

Originally created by @robjordan on GitHub (Dec 22, 2021).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1326

Basic Infos

Hardware

WiFimanager Branch/Release: Master
2.0.5-beta+sha.8452df7

Esp32:

Hardware: m5stickc+ (ESP32-PICO-D4 based)

Core Version: 3.4.0

Description

On ESP32 Arduino, my app is a BLE scanner. I have read that WiFi activity can interfere with BLE detection, so I keep WiFi disabled most of the time, but re-enable once a minute to log data to a web server. The way I do that is:

        if (wifiManager.autoConnect()) {
          log_value("sos-battery", batteryLevel);
          log_value("sos-rssi", (avgRSSI==0) ? -100 : avgRSSI);
          log_value("sos-freeheap", ESP.getFreeHeap());
          wifiManager.disconnect();
        } else {
          Serial.println("Failed to connect WiFi.");
        }

After every disconnect(), I see a log message as per the Issue subject, but it is repeated many times, seemingly one additional log message each time I disconnect. Now after running for around 12 hours, there are more than 600 repeated messages.

Settings in IDE

Module: NodeMcu, Wemos D1

Additional libraries:

Sketch

#BEGIN
#include <Arduino.h>

void setup() {
  esp_get_idf_version();
  m5_init();
  wifi_init();  // connect to Wifi, use it, then disconnect.
  config_init(cfgFile, cfg);
  ble_scan_init();
}

void loop() {
  static time_t lastPing = 0;
  static time_t silentTime = 0;
  static time_t lastFeed = now();
  const char *timeUnit[] = {"sec(s)", "min(s)", "hour(s)", "day(s)"};
  unsigned timeUnitIndex = 0;


  char buf[80];

  // If an error occurs that stops the scan, it will be restarted here.
  if(pBLEScan->isScanning() == false) {
      // Start scan with: duration = 5s, no scan end callback, not a continuation of a previous scan.
      pBLEScan->start(5, nullptr, false);
      M5.Lcd.fillScreen(0);
      M5.Lcd.setCursor(0,10);
      print_date_time();
      Serial.print("Scan exited, ping count: ");
      Serial.print(pingCount);

      if (pingCount == 0) {
        // it might be a temporary silence, but track it in case it's a sign
        // of technical failure, beacon turned off, etc.
        silentTime = now() - lastPing;
        if (silentTime > silenceThreshold) {
          M5.Lcd.println("\nALERT: NO BEACON");
          alert(&alerts[silenceAlertIndex]);
        }
        if (silentTime < 60) {
          timeUnitIndex = 0;
        } else if (silentTime < 60*60) {
          silentTime = silentTime / 60;
          timeUnitIndex = 1;
        } else if (silentTime < 24*60*60) {
          silentTime = silentTime / (60*60);
          timeUnitIndex = 2;
        } else {
          silentTime = silentTime / 24*60*60;
          timeUnitIndex = 3;
        }

      } else {
        // we have detected pings - not sure how many yet
        lastPing = now();
        silentTime = 0;
        if (batteryLevel < batteryThreshold) {
          M5.Lcd.println("\nALERT: LOW BATTERY");
          alert(&alerts[batteryAlertIndex]);
        }
        if (pingCount >= pingAlertThreshold) {
          // it's an SOS call, raise the alarm
          M5.Lcd.println("\nALERT: BUTTON PRESS");
          alert(&alerts[sosAlertIndex]);
        } else {
          // it's the normal case of ~1 ping per sample interval
        }
      }

      // Calculate average RSSI, avoiding divide by zero error
      avgRSSI = (pingCount>0) ? (sumRSSI / pingCount) : 0;

      sprintf(buf, 
            "\npings: %d, RSSI: %d\nbattery: %d%%\nsilent: %lu %s", 
            pingCount, 
            avgRSSI,
            batteryLevel,
            silentTime,
            timeUnit[timeUnitIndex]);

      M5.Lcd.println(buf);
      Serial.println(buf);
      if ((now() - lastFeed) > feedInterval) {
        // Log data to MQTT
        if (wifiManager.autoConnect()) {
          log_value("sos-battery", batteryLevel);
          log_value("sos-rssi", (avgRSSI==0) ? -100 : avgRSSI);
          log_value("sos-freeheap", ESP.getFreeHeap());
          wifiManager.disconnect();
        } else {
          Serial.println("Failed to connect WiFi.");
        }
        lastFeed = now();
      }
      pingCount = 0;
      sumRSSI = 0;
  }
}
#END

Debug Messages

*wm:[1] AutoConnect 
*wm:[2] ESP32 event handler enabled 
*wm:[2] Connecting as wifi client... 
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: JM07
*wm:[1] connectTimeout not set, ESP waitForConnectResult... 
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS 
*wm:[1] STA IP Address: 192.168.1.132
About to post: {"value": 100}
[HTTPS] POST...
[HTTPS] POST... code: 200
{"id":"0EXBBRQ1MWYN84Y86TF96P2PQA","value":"100","feed_id":1772252,"feed_key":"sos-battery","created_at":"2021-12-22T13:35:38Z","created_epoch":1640180138,"expiration":"2022-01-21T13:35:38Z"}
About to post: {"value": -67}
[HTTPS] POST...
[HTTPS] POST... code: 200
{"id":"0EXBBRQM5CKF8C7VEMZVFKKTH9","value":"-67","feed_id":1772254,"feed_key":"sos-rssi","created_at":"2021-12-22T13:35:40Z","created_epoch":1640180140,"expiration":"2022-01-21T13:35:40Z"}
About to post: {"value": 113928}
[HTTPS] POST...
[HTTPS] POST... code: 200
{"id":"0EXBBRRDRM2HF7SE53X232V9AG","value":"113928","feed_id":1772435,"feed_key":"sos-freeheap","created_at":"2021-12-22T13:35:42Z","created_epoch":1640180142,"expiration":"2022-01-21T13:35:42Z"}
*wm:[1] Disconnecting 
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
<hundreds more like this>
Originally created by @robjordan on GitHub (Dec 22, 2021). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1326 ### Basic Infos #### Hardware WiFimanager Branch/Release: Master 2.0.5-beta+sha.8452df7 Esp32: Hardware: m5stickc+ (ESP32-PICO-D4 based) Core Version: 3.4.0 ### Description On ESP32 Arduino, my app is a BLE scanner. I have read that WiFi activity can interfere with BLE detection, so I keep WiFi disabled most of the time, but re-enable once a minute to log data to a web server. The way I do that is: ```cpp if (wifiManager.autoConnect()) { log_value("sos-battery", batteryLevel); log_value("sos-rssi", (avgRSSI==0) ? -100 : avgRSSI); log_value("sos-freeheap", ESP.getFreeHeap()); wifiManager.disconnect(); } else { Serial.println("Failed to connect WiFi."); } ``` After every disconnect(), I see a log message as per the Issue subject, but it is repeated many times, seemingly one additional log message each time I disconnect. *Now after running for around 12 hours, there are more than 600 repeated messages*. ### Settings in IDE Module: NodeMcu, Wemos D1 Additional libraries: ### Sketch ```cpp #BEGIN #include <Arduino.h> void setup() { esp_get_idf_version(); m5_init(); wifi_init(); // connect to Wifi, use it, then disconnect. config_init(cfgFile, cfg); ble_scan_init(); } void loop() { static time_t lastPing = 0; static time_t silentTime = 0; static time_t lastFeed = now(); const char *timeUnit[] = {"sec(s)", "min(s)", "hour(s)", "day(s)"}; unsigned timeUnitIndex = 0; char buf[80]; // If an error occurs that stops the scan, it will be restarted here. if(pBLEScan->isScanning() == false) { // Start scan with: duration = 5s, no scan end callback, not a continuation of a previous scan. pBLEScan->start(5, nullptr, false); M5.Lcd.fillScreen(0); M5.Lcd.setCursor(0,10); print_date_time(); Serial.print("Scan exited, ping count: "); Serial.print(pingCount); if (pingCount == 0) { // it might be a temporary silence, but track it in case it's a sign // of technical failure, beacon turned off, etc. silentTime = now() - lastPing; if (silentTime > silenceThreshold) { M5.Lcd.println("\nALERT: NO BEACON"); alert(&alerts[silenceAlertIndex]); } if (silentTime < 60) { timeUnitIndex = 0; } else if (silentTime < 60*60) { silentTime = silentTime / 60; timeUnitIndex = 1; } else if (silentTime < 24*60*60) { silentTime = silentTime / (60*60); timeUnitIndex = 2; } else { silentTime = silentTime / 24*60*60; timeUnitIndex = 3; } } else { // we have detected pings - not sure how many yet lastPing = now(); silentTime = 0; if (batteryLevel < batteryThreshold) { M5.Lcd.println("\nALERT: LOW BATTERY"); alert(&alerts[batteryAlertIndex]); } if (pingCount >= pingAlertThreshold) { // it's an SOS call, raise the alarm M5.Lcd.println("\nALERT: BUTTON PRESS"); alert(&alerts[sosAlertIndex]); } else { // it's the normal case of ~1 ping per sample interval } } // Calculate average RSSI, avoiding divide by zero error avgRSSI = (pingCount>0) ? (sumRSSI / pingCount) : 0; sprintf(buf, "\npings: %d, RSSI: %d\nbattery: %d%%\nsilent: %lu %s", pingCount, avgRSSI, batteryLevel, silentTime, timeUnit[timeUnitIndex]); M5.Lcd.println(buf); Serial.println(buf); if ((now() - lastFeed) > feedInterval) { // Log data to MQTT if (wifiManager.autoConnect()) { log_value("sos-battery", batteryLevel); log_value("sos-rssi", (avgRSSI==0) ? -100 : avgRSSI); log_value("sos-freeheap", ESP.getFreeHeap()); wifiManager.disconnect(); } else { Serial.println("Failed to connect WiFi."); } lastFeed = now(); } pingCount = 0; sumRSSI = 0; } } #END ``` ### Debug Messages ``` *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: JM07 *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] Connection result: WL_CONNECTED *wm:[1] AutoConnect: SUCCESS *wm:[1] STA IP Address: 192.168.1.132 About to post: {"value": 100} [HTTPS] POST... [HTTPS] POST... code: 200 {"id":"0EXBBRQ1MWYN84Y86TF96P2PQA","value":"100","feed_id":1772252,"feed_key":"sos-battery","created_at":"2021-12-22T13:35:38Z","created_epoch":1640180138,"expiration":"2022-01-21T13:35:38Z"} About to post: {"value": -67} [HTTPS] POST... [HTTPS] POST... code: 200 {"id":"0EXBBRQM5CKF8C7VEMZVFKKTH9","value":"-67","feed_id":1772254,"feed_key":"sos-rssi","created_at":"2021-12-22T13:35:40Z","created_epoch":1640180140,"expiration":"2022-01-21T13:35:40Z"} About to post: {"value": 113928} [HTTPS] POST... [HTTPS] POST... code: 200 {"id":"0EXBBRRDRM2HF7SE53X232V9AG","value":"113928","feed_id":1772435,"feed_key":"sos-freeheap","created_at":"2021-12-22T13:35:42Z","created_epoch":1640180142,"expiration":"2022-01-21T13:35:42Z"} *wm:[1] Disconnecting *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 <hundreds more like this> ```
kerem 2026-02-28 01:28:41 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Dec 22, 2021):

Thanks, I may have left some debugging on the wrong level when testing S2

<!-- gh-comment-id:999947162 --> @tablatronix commented on GitHub (Dec 22, 2021): Thanks, I may have left some debugging on the wrong level when testing S2
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (Dec 24, 2021):

Thanks, I appreciate you paying attention to this. I'm not sure I was clear though: it isn't just there is an unwanted debug output. I fear there might be something wrong in the code path, based on the increasing number of these WIFI_REASON messages, i.e. it appears 1x on the first wifiManager.disconnect();, 2x on the second, 3x on the third, Nx on the Nth. And N can be a very large number as I connect and disconnect once every minute. I had it appear literally 600 times in succession after running for a few hours.

<!-- gh-comment-id:1000933775 --> @robjordan commented on GitHub (Dec 24, 2021): Thanks, I appreciate you paying attention to this. I'm not sure I was clear though: it isn't just there is an unwanted debug output. I fear there might be something wrong in the code path, based on the increasing number of these WIFI_REASON messages, i.e. it appears 1x on the first wifiManager.disconnect();, 2x on the second, 3x on the third, Nx on the Nth. And N can be a very large number as I connect and disconnect once every minute. I had it appear literally 600 times in succession after running for a few hours.
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Dec 25, 2021):

Interesting let me see if I can reproduce what version on esp lib you on?

<!-- gh-comment-id:1000955908 --> @tablatronix commented on GitHub (Dec 25, 2021): Interesting let me see if I can reproduce what version on esp lib you on?
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Dec 25, 2021):

Oh nm I see you added all the info above

<!-- gh-comment-id:1000955938 --> @tablatronix commented on GitHub (Dec 25, 2021): Oh nm I see you added all the info above
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Dec 25, 2021):

WIFI_REASON_ASSOC_LEAVE = 8,

Are you perhaps creating new objects over and over again accidentally? That would make sense if creating more and more event listeners.

Can you share how you are reconnecting over and over? Or reduce your sketch to a simpler one, where is your wm object?

<!-- gh-comment-id:1000965285 --> @tablatronix commented on GitHub (Dec 25, 2021): WIFI_REASON_ASSOC_LEAVE = 8, Are you perhaps creating new objects over and over again accidentally? That would make sense if creating more and more event listeners. Can you share how you are reconnecting over and over? Or reduce your sketch to a simpler one, where is your wm object?
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (Dec 26, 2021):

Hi. Not knowingly creating multiple objects. wifiManager is created in global scope. HTTP clients are created on the stack in local variables each time I do an HTTP post. The main loop is basically:
// ... block for 5 seconds checking for BLE advertisements
// ... check whether 1 minute has elapsed since we last logged, if so ...
if (wifiManager.autoConnect("SSID", "PW")) {
log_json(); // which makes an HTTP POST
wifiManager.disconnect();
}

I'll aim to create a simpler test case to reproduce. Maybe in a couple of days though. Thanks for help.

<!-- gh-comment-id:1001089915 --> @robjordan commented on GitHub (Dec 26, 2021): Hi. Not knowingly creating multiple objects. wifiManager is created in global scope. HTTP clients are created on the stack in local variables each time I do an HTTP post. The main loop is basically: // ... block for 5 seconds checking for BLE advertisements // ... check whether 1 minute has elapsed since we last logged, if so ... if (wifiManager.autoConnect("SSID", "PW")) { log_json(); // which makes an HTTP POST wifiManager.disconnect(); } I'll aim to create a simpler test case to reproduce. Maybe in a couple of days though. Thanks for help.
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (Dec 27, 2021):

This test case (based on the WiFiManager basic example) demonstrates.

#include <Arduino.h>
#include <WiFi.h>
#include <WiFiManager.h> // https://github.com/tzapu/WiFiManager
#include <HTTPClient.h>

WiFiManager wm;

void setup() {
    WiFi.mode(WIFI_STA); // explicitly set mode, esp defaults to STA+AP
    Serial.begin(115200);
    bool res;

    res = wm.autoConnect("AutoConnectAP","password"); // password protected ap

    if(!res) {
        Serial.println("Failed to connect");
        // ESP.restart();
    } 
    else {
        //if you get here you have connected to the WiFi    
        Serial.println("connected...yeey :)");
        Serial.println("now disconnecting");
        wm.disconnect();
    }

}

void loop() {
    HTTPClient http;
    const char *postUrl="https://ptsv2.com/t/b8a9b-1640614358/post";
    String httpRequestData = "Hello world";
    int httpCode; 

    // put your main code here, to run repeatedly:  
    if (wm.autoConnect()) {
        if (http.begin(postUrl)) {
            httpCode = http.POST(httpRequestData);
            wm.disconnect();
        }
    }
    delay(2000);
}
<!-- gh-comment-id:1001778482 --> @robjordan commented on GitHub (Dec 27, 2021): This test case (based on the WiFiManager basic example) demonstrates. ``` #include <Arduino.h> #include <WiFi.h> #include <WiFiManager.h> // https://github.com/tzapu/WiFiManager #include <HTTPClient.h> WiFiManager wm; void setup() { WiFi.mode(WIFI_STA); // explicitly set mode, esp defaults to STA+AP Serial.begin(115200); bool res; res = wm.autoConnect("AutoConnectAP","password"); // password protected ap if(!res) { Serial.println("Failed to connect"); // ESP.restart(); } else { //if you get here you have connected to the WiFi Serial.println("connected...yeey :)"); Serial.println("now disconnecting"); wm.disconnect(); } } void loop() { HTTPClient http; const char *postUrl="https://ptsv2.com/t/b8a9b-1640614358/post"; String httpRequestData = "Hello world"; int httpCode; // put your main code here, to run repeatedly: if (wm.autoConnect()) { if (http.begin(postUrl)) { httpCode = http.POST(httpRequestData); wm.disconnect(); } } delay(2000); } ```
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (Dec 27, 2021):

Debug output:

*wm:[1] AutoConnect 
*wm:[2] ESP32 event handler enabled 
*wm:[2] Connecting as wifi client... 
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: PLUSNET-X8T5
*wm:[1] connectTimeout not set, ESP waitForConnectResult... 
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS 
*wm:[1] STA IP Address: 192.168.1.102
connected...yeey :)
now disconnecting
*wm:[1] Disconnecting 
*wm:[1] AutoConnect 
*wm:[2] ESP32 event handler enabled*wm:[2] [EVENT] WIFI_REASON:  8
 
*wm:[2] Connecting as wifi client... 
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: PLUSNET-X8T5
*wm:[1] connectTimeout not set, ESP waitForConnectResult... 
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS 
*wm:[1] STA IP Address: 192.168.1.102
*wm:[1] Disconnecting 
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8                                                                                                     
*wm:[1] AutoConnect                                                                                                                 
*wm:[2] ESP32 event handler enabled                                                                                                 
*wm:[2] Connecting as wifi client...                                                                                                
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: PLUSNET-X8T5
*wm:[1] connectTimeout not set, ESP waitForConnectResult... 
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS 
*wm:[1] STA IP Address: 192.168.1.102
*wm:[1] Disconnecting 
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[1] AutoConnect 
*wm:[2] ESP32 event handler enabled 
*wm:[2] Connecting as wifi client... 
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: PLUSNET-X8T5
*wm:[1] connectTimeout not set, ESP waitForConnectResult... 
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS 
*wm:[1] STA IP Address: 192.168.1.102
*wm:[1] Disconnecting 
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[1] AutoConnect 
*wm:[2] ESP32 event handler enabled 
*wm:[2] Connecting as wifi client... 
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: PLUSNET-X8T5
*wm:[1] connectTimeout not set, ESP waitForConnectResult... 
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS 
*wm:[1] STA IP Address: 192.168.1.102
*wm:[1] Disconnecting 
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[2] [EVENT] WIFI_REASON:  8
*wm:[1] AutoConnect 
*wm:[2] ESP32 event handler enabled 
*wm:[2] Connecting as wifi client... 
*wm:[2] setSTAConfig static ip not set, skipping 
*wm:[1] Connecting to SAVED AP: PLUSNET-X8T5
*wm:[1] connectTimeout not set, ESP waitForConnectResult...
<!-- gh-comment-id:1001779531 --> @robjordan commented on GitHub (Dec 27, 2021): Debug output: ``` *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: PLUSNET-X8T5 *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] Connection result: WL_CONNECTED *wm:[1] AutoConnect: SUCCESS *wm:[1] STA IP Address: 192.168.1.102 connected...yeey :) now disconnecting *wm:[1] Disconnecting *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled*wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: PLUSNET-X8T5 *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] Connection result: WL_CONNECTED *wm:[1] AutoConnect: SUCCESS *wm:[1] STA IP Address: 192.168.1.102 *wm:[1] Disconnecting *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: PLUSNET-X8T5 *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] Connection result: WL_CONNECTED *wm:[1] AutoConnect: SUCCESS *wm:[1] STA IP Address: 192.168.1.102 *wm:[1] Disconnecting *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: PLUSNET-X8T5 *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] Connection result: WL_CONNECTED *wm:[1] AutoConnect: SUCCESS *wm:[1] STA IP Address: 192.168.1.102 *wm:[1] Disconnecting *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: PLUSNET-X8T5 *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] Connection result: WL_CONNECTED *wm:[1] AutoConnect: SUCCESS *wm:[1] STA IP Address: 192.168.1.102 *wm:[1] Disconnecting *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[2] [EVENT] WIFI_REASON: 8 *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: PLUSNET-X8T5 *wm:[1] connectTimeout not set, ESP waitForConnectResult... ```
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Feb 3, 2022):

Ever figure this out?

<!-- gh-comment-id:1028543640 --> @tablatronix commented on GitHub (Feb 3, 2022): Ever figure this out?
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (Feb 3, 2022):

To be fair, I haven't updated the library since I reported it. It's not a
critical problem in my application because I reboot the esp32 every 24
hours. But as far as I know the problem still exists. Did you try the small
sample programme I posted?

On Thu, 3 Feb 2022, 02:25 Shawn A, @.***> wrote:

Ever figure this out?

—
Reply to this email directly, view it on GitHub
https://github.com/tzapu/WiFiManager/issues/1326#issuecomment-1028543640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC65F2A75G75HLRU3N5VSTUZHRS3ANCNFSM5KSXPQKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1029401784 --> @robjordan commented on GitHub (Feb 3, 2022): To be fair, I haven't updated the library since I reported it. It's not a critical problem in my application because I reboot the esp32 every 24 hours. But as far as I know the problem still exists. Did you try the small sample programme I posted? On Thu, 3 Feb 2022, 02:25 Shawn A, ***@***.***> wrote: > Ever figure this out? > > — > Reply to this email directly, view it on GitHub > <https://github.com/tzapu/WiFiManager/issues/1326#issuecomment-1028543640>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAC65F2A75G75HLRU3N5VSTUZHRS3ANCNFSM5KSXPQKQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Feb 3, 2022):

I have to see which event that is
WIFI_REASON_ASSOC_LEAVE OR
8 SYSTEM_EVENT_STA_LOST_IP < ESP32 station lost IP and the IP is reset to 0

Something with your router I doubt its reproducible elsewhere

i can try it though

<!-- gh-comment-id:1029440767 --> @tablatronix commented on GitHub (Feb 3, 2022): I have to see which event that is WIFI_REASON_ASSOC_LEAVE OR 8 SYSTEM_EVENT_STA_LOST_IP < ESP32 station lost IP and the IP is reset to 0 Something with your router I doubt its reproducible elsewhere i can try it though
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (Feb 3, 2022):

Works fine for me

<!-- gh-comment-id:1029451573 --> @tablatronix commented on GitHub (Feb 3, 2022): Works fine for me
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (Feb 4, 2022):

Ok, if not reproducible, it's not worth pursuing. Thanks for looking.

On Thu, 3 Feb 2022, 22:14 Shawn A, @.***> wrote:

Works fine for me

—
Reply to this email directly, view it on GitHub
https://github.com/tzapu/WiFiManager/issues/1326#issuecomment-1029451573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC65F6OP6WA3D3SXGNLHTDUZL457ANCNFSM5KSXPQKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1029815581 --> @robjordan commented on GitHub (Feb 4, 2022): Ok, if not reproducible, it's not worth pursuing. Thanks for looking. On Thu, 3 Feb 2022, 22:14 Shawn A, ***@***.***> wrote: > Works fine for me > > — > Reply to this email directly, view it on GitHub > <https://github.com/tzapu/WiFiManager/issues/1326#issuecomment-1029451573>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAC65F6OP6WA3D3SXGNLHTDUZL457ANCNFSM5KSXPQKQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@OekoSolveMG commented on GitHub (May 19, 2022):

I am assuming you use autoConnect() to reconnect to the wifi while your application is running. Because if you do then this issue is probably because of the same reason as #1383. Hope this helps and is actually causing your problem, because if it does simply integrating the easy fix or using a different way to reconnect fixes that.

<!-- gh-comment-id:1131697945 --> @OekoSolveMG commented on GitHub (May 19, 2022): I am assuming you use ```autoConnect()``` to reconnect to the wifi while your application is running. Because if you do then this issue is probably because of the same reason as #1383. Hope this helps and is actually causing your problem, because if it does simply integrating the easy fix or using a different way to reconnect fixes that.
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@robjordan commented on GitHub (May 19, 2022):

I am assuming you use autoConnect() to reconnect to the wifi while your application is running. Because if you do then this issue is probably because of the same reason as #1383. Hope this helps and is actually causing your problem, because if it does simply integrating the easy fix or using a different way to reconnect fixes that.

I am assuming you use autoConnect() to reconnect to the wifi while your application is running. Because if you do then this issue is probably because of the same reason as #1383. Hope this helps and is actually causing your problem, because if it does simply integrating the easy fix or using a different way to reconnect fixes that.

Thanks, yes I do call autoconnect() repeatedly. I read the issue you mentioned and it's very useful info.

<!-- gh-comment-id:1132223214 --> @robjordan commented on GitHub (May 19, 2022): > I am assuming you use `autoConnect()` to reconnect to the wifi while your application is running. Because if you do then this issue is probably because of the same reason as #1383. Hope this helps and is actually causing your problem, because if it does simply integrating the easy fix or using a different way to reconnect fixes that. > I am assuming you use `autoConnect()` to reconnect to the wifi while your application is running. Because if you do then this issue is probably because of the same reason as #1383. Hope this helps and is actually causing your problem, because if it does simply integrating the easy fix or using a different way to reconnect fixes that. Thanks, yes I do call autoconnect() repeatedly. I read the issue you mentioned and it's very useful info.
kerem commented 2026-02-28 01:28:42 +03:00
Author
Owner
Copy link

@tablatronix commented on GitHub (May 19, 2022):

This should be solved now

<!-- gh-comment-id:1132224004 --> @tablatronix commented on GitHub (May 19, 2022): This should be solved now
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#1140
No description provided.