WiFiManager: Configuration Portal does not load
Hardware
WiFimanager Branch/Release:
- Master
- Development
Esp8266/Esp32:
- ESP32
**Hardware: ESP32 Dev Module
ESP Core Version: 2.4.0, staging
- 2.3.0
- 2.4.0
- staging (master/dev)
Description
I’m trying to check the WifiManager on my ESP32 card. I loaded an example, but the configuration portal does not want to run. In the list of Wifi networks, I also do not see my fee.
Sketch
#include "soc/soc.h" // Lib For Brownout Detector (Low Power Mode Fix)
#include "soc/rtc_cntl_reg.h" // Lib For Brownout Detector (Low Power Mode Fix)
#include <WiFiManager.h> //https://github.com/tzapu/WiFiManager
void setup() {
// put your setup code here, to run once:
WRITE_PERI_REG (RTC_CNTL_BROWN_OUT_REG, 0);
Serial.begin(115200);
//WiFiManager
//Local intialization. Once its business is done, there is no need to keep it around
WiFiManager wifiManager;
//reset saved settings
//wifiManager.resetSettings();
//set custom ip for portal
//wifiManager.setAPStaticIPConfig(IPAddress(10,0,1,1), IPAddress(10,0,1,1), IPAddress(255,255,255,0));
//fetches ssid and pass from eeprom and tries to connect
//if it does not connect it starts an access point with the specified name
//here "AutoConnectAP"
//and goes into a blocking loop awaiting configuration
wifiManager.autoConnect("AutoConnectAP");
//or use this for auto generated name ESP + ChipID
//wifiManager.autoConnect();
//if you get here you have connected to the WiFi
Serial.println("connected...yeey :)");
}
void loop() {}
Debug Messages
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:952
load:0x40078000,len:6084
load:0x40080000,len:7936
entry 0x40080310
*WM: [1] AutoConnect
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15
very odd, I would have expected some kind of crash or reboot in serial log. Glad you got it fixed, can it be closed?
@tablatronix Happened! The problem is solved by thoroughly cleaning the flash with esptool.py.