Autoconnect problem after network loss - need some help

FilipDem commented 4 years ago

Basic Infos

Hardware

WiFimanager Branch/Release: WifiManager 2.0.3-alpha from the Arduino Library Manager

Esp8266/Esp32: ESP8266 Hardware: ESP-12F ESP Core Version: 2.7.4

Description

I am using the WifiManager... Now it happens that the network is interrupted. I see then that the AP is activated (from LED behavior and network scan). The network comes up again (because my PC has again a WIFI connection. Afterwards the AP is quit (probably after timeout), however there is no network access. After reboot all comes back OK.

Is it correct that the StartConfigPortal is started if a network disconnection is detected? Don't understand where in the code this happens, seen I don't do sth special in the loop(). Who could help me to the behavior of the WifiManager to detect that the network is interrupted and up again? Or somebody has some ideas what could be the problem, always welcome.

Concept Sketch

void setup() {
...
        WiFiManager wifiManager;
        wifiManager.setDebugOutput(DEBUG_WIFIMANAGER);
        wifiManager.setShowStaticFields(true);
        static const char* menu[] PROGMEM = {"wifi", "wifinoscan", "restart", "exit"};
        wifiManager.setMenu(menu, 4);
        wifiManager.setAPCallback(APconfigModeCallback);
        wifiManager.setAPStaticIPConfig(AP_IP_ADDRESS, AP_GATEWAY, AP_SUBNET_MASK);
        wifiManager.setConfigPortalTimeout(TIMEOUT_AP_PORTAL);

        // Connect to network or active AP if no connection can be made
        if (wifiManager.autoConnect(APname, APpassword)) {
            // Send the IP address of the ESP8266 to the computer
            DEBUG(Serial.print(F("\nConnected to: "));Serial.println(WiFi.SSID());Serial.print(F("IP address: "));Serial.println(WiFi.localIP());)

            // Update status of the connection
            LastConnectionStatus = true;
            LastConnectionDateTime = CurrentDateTime;

            // Led on
            ticker.detach();
            digitalWrite(LED, LOW);

            return true;
        }
        // Active AP has quit after timeout; no network connection
        else {
            DEBUG(Serial.print(F("\nNo network connection!"));)

            // Led slowly blinking if no network
            ticker.attach(1, toggle_led);

            return false;
        }

    }
...

}

void loop() {

...
        if (WiFi.status() == WL_CONNECTED) {
            // Connection is just restored
            if (LastConnectionStatus == false) {
                // Toggle status
                LastConnectionStatus = true;
                LastConnectionDateTime = CurrentDateTime;
                // Led on
                ticker.detach();
                digitalWrite(LED, LOW);
                DEBUG(Serial.println(F("WIFI connected again!"));)
            }
            return true;
        }
        // Not connected to network
        else {
            // Connection is just lost
            if (LastConnectionStatus == true) {
                // Toggle status and count disconnections
                LastConnectionStatus = false;
                NbrDeconnections++;
                DEBUG(Serial.println(F("WIFI disconnected!"));)
                // Led slowly blinking if no network
                ticker.attach(1, toggle_led);
            }
            // Connection stay lost: reboot after a certain time
            else {
                if ( CurrentDateTime-LastConnectionDateTime > MAX_TIME_WITHOUT_INTERNET ) {
                    ESP.restart();
                }
            }
            return false;
        }
...

}

tablatronix commented 4 years ago

autoconnect autostarts configportal on fail, it should only start on reboot, unless you disable that (its optional)

esp should auto reconnect, so why it is not is the question.

It sounds like your esp is having a problem reconnecting, it could be another bug or unrelated to wm.

You need to enable debugging and see what its doing.

Also make sure you set wifi.mode properly in your code, sta only if you do not want ap running

ddweber456 commented 4 years ago

I have had the same issue with a power outages. Router takes 30 - 40 sec to connect to the web, mean time the ESP wifiManager.autoConnect is already in AP mode waiting for SSID/Password.

I fixed the problem with wifiManager.setTimeout and a ESP.restart.

wifiManager.setTimeout(120);
wifiManager.setConfigPortalTimeout(120);

if(!wifiManager.autoConnect("APSetup WIFI", "password")) { Serial.println("failed to connect 1st time after BOOT and hit timeout"); delay(100); ESP.restart();

I also added the following in Setup:

WiFi.persistent(true);
WiFi.setAutoConnect(true);
WiFi.setAutoReconnect(true);

tablatronix commented 4 years ago

Yeah I would just add a little loop and deal with it in your own code.

tablatronix commented 4 years ago

if you wifiManager.setTimeout(120); then it should keep checking before starting the cp, but maybe there is something else going on. There are documented issues of connects failing first time, I would reproduce and get some logs to see why the 120S is not enough