## After connected, AutoConnect menu performs but no happens. If you can access the **AutoConnect root path** as http://ESP8266IPADDRESS/_ac from browser, probably the sketch uses *ESP8266WebServer::handleClient()* without [*AutoConnect::handleRequest()*](api.md#handlerequest). For AutoConnect menus to work properly, call [*AutoConnect::handleRequest()*](api.md#handlerequest) after *ESP8266WebServer::handleClient()* invoked, or use [*AutoConnect::handleClient()*](api.md#handleclient). [*AutoConnect::handleClient()*](api.md#handleclient) is equivalent *ESP8266WebServer::handleClient* combined [*AutoConnect::handleRequest()*](api.md#handlerequest). See also the explanation [here](basicusage.md#esp8266webserver-hosted-or-parasitic). ## An esp8266ap as SoftAP was connected but Captive portal does not start. Captive portal detection could not be trapped. It is necessary to disconnect and reset ESP8266 to clear memorized connection data in ESP8266. Also, It may be displayed on the smartphone if the connection information of esp8266ap is wrong. In that case, delete the connection information of esp8266ap memorized by the smartphone once. ## Connection refused with the captive portal after established. This is a known issue with ESP32 and may occur when the following conditions are satisfied at the same time: - SoftAP channel on ESP32 and the connecting AP channel you specified are different. - Never connected to the AP in the past, or NVS had erased by erase_flash causes the connection data lost. - There are receivable multiple WiFi signals which are the same SSID with different channels using the WiFi repeater etc. (This condition is loose, it may occur even if there is no WiFi repeater.) To avoid this problem, try [changing the channel](#1-change-wifi-channel). ESP32 hardware equips only one channel for WiFi signal to carry. At the AP_STA mode, if ESP32 as an AP will connect to another AP on another channel while maintaining the connection with the station, the channel switching will occur and the station may be disconnected. But it may not be just a matter of channel switching causes ESP8266 has the same constraints too. It may be a problem with AutoConnect or the arduino core or SDK issue. Unfortunately, I have not found a solution yet. However, I am continuing trial and error to solve this problem and will resolve in due course. ## Does not appear esp8266ap in smartphone. Maybe it is successfully connected at the **first WiFi.begin**. ESP8266 remembers the last SSID successfully connected and will use at the next. It means SoftAP will only start up when the first *WiFi.begin()* fails. The saved SSID would be cleared by *WiFi.disconnect()* with WIFI_STA mode. If you do not want automatic reconnection, you can erase the memorized SSID with the following simple sketch. ```cpp #include void setup() { delay(1000); Serial.begin(115200); WiFi.mode(WIFI_STA); delay(100); WiFi.begin(); if (WiFi.waitForConnectResult() == WL_CONNECTED) { WiFi.disconnect(); while (WiFi.status() == WL_CONNECTED) delay(100); } Serial.println("WiFi disconnected."); } void loop() { delay(1000); } ``` ??? hint "You can interactively check the WiFi state of ESP8266." Please try [**ESPShaker**](https://github.com/Hieromon/ESPShaker). It is ESP8266 interactive serial command processor. ## Does not response from /\_ac. Probably **WiFi.begin** failed with the specified SSID. Activating the [debug printing](advancedusage.md#debug-print) will help you to track down the cause. ## How change esp8266ap for SSID name in Captive portal? An **esp8266ap** is default SSID name for SoftAP of captive portal and password is **12345678**. You can change both by using [AutoConnectConfig](api.md#autoconnectconfig-api). ## How change HTTP port? HTTP port number is defined as a macro in [AutoConnect.h](https://github.com/Hieromon/AutoConnect/blob/77d5cb5dc6d50651fd15f74b47859105c71fc317/src/AutoConnect.h#L89) header file. You can change it directly with several editors and must re-compile. ```cpp #define AUTOCONNECT_HTTPPORT 80 ``` ## Hang up after Reset? If ESP8266 hang up after reset by AutoConnect menu, perhaps manual reset is not yet. Especially if it is not manual reset yet after uploading the sketch, the boot mode will stay 'Uart Download'. There is some discussion about this on the Github's ESP8266 core: https://github.com/esp8266/Arduino/issues/1017 If you received the following message, the boot mode is still sketch uploaded. It needs to the manual reset once. ``` ets Jan 8 2013,rst cause:2, boot mode:(1,6) or (1,7) ets Jan 8 2013,rst cause:4, boot mode:(1,6) or (1,7) wdt reset ``` The correct boot mode for starting the sketch is **(3, x)**. !!! info "ESP8266 Boot Messages" It is described by [ESP8266 Non-OS SDK API Reference](view-source:https://www.espressif.com/en/products/hardware/esp8266ex/resources), section A.5. | Messages | Description | |----------|-------------| | rst cause | 1: power on
2: external reset
4: hardware watchdog reset | | boot mode
(the first parameter) | 1: ESP8266 is in UART-down mode (and downloads firmware into flash).
3: ESP8266 is in Flash-boot mode (and boots up from flash). | ## How erase the credentials saved in EEPROM? Make some sketches for erasing the EEPROM area, or some erasing utility is needed. You can prepare the sketch to erase the saved credential with *AutoConnectCredential*. The *AutoConnectCrendential* class provides the access method to the saved credential in EEPROM and library source file is including it. A class description of AutoConnectCredential is follows. ### Include header ```cpp #include ``` ### Constructor ```cpp AutoConnectCredential(); ``` AutoConnectCredential default constructor. The default offset value is 0. If the offset value is 0, the credential storage area starts from the top of the EEPROM. AutoConnect sometimes overwrites data when using this area with user sketch. ```cpp AutoConnectCredential(uint16_t offset); ``` Specify offset from the top of the EEPROM for the credential storage area together. The offset value is from 0 to the flash sector size. ### Public member functions - uint8_t **entries()** Returns number of entries as contained credentials. - int8_t **load(const char\* _ssid_, struct station_config\* _config_)** Load a credential entry specified *ssid* to *config*. Returns -1 as unsuccessfully loaded. - bool **load(int8_t _entry_, struct station_config\* _config_)** Load a credential entry to *config*. The *entry* parameter specify to index of the entry. - bool **save(const struct station_config\* _config_)** Save a credential entry stored in *config* to EEPROM. Returns the true as succeeded. - bool **del(const char\* _ssid_)** Delete a credential entry specified *ssid*. Returns the true as successfully deleted. ### Data structures - station_config A structure is included in the ESP8266 SDK. You can use it in the sketch like as follows. ```cpp extern "C" { #include } ``` ```cpp struct station_config { uint8 ssid[32]; uint8 password[64]; uint8 bssid_set; uint8 bssid[6]; }; ``` - EEPROM data structure A data structure of the credential saving area in EEPROM as the below. [^1] [^1]: There may be 0xff as an invalid data in the credential saving area. The 0xff area would be reused. | Byte offset | Length | Value | |-------------|----------|---------------------------------------------------------------------| | 0 | 8 | AC_CREDT | | 8 | 1 | Number of contained entries (uint8_t) | | 9 | 2 | Container size, excluding size of AC_CREDT and size of the number of entries(width for uint16_t type). | | 11 | variable | SSID terminated by 0x00. Max length is 32 bytes. | | variable | variable | Password plain text terminated by 0x00. Max length is 64 bytes. | | variable | 6 | BSSID | | variable | | Contained the next entries. (Continuation SSID+Password+BSSID) | | variable | 1 | 0x00. End of container. | !!! hint With the [**ESPShaker**](https://github.com/Hieromon/ESPShaker), you can access EEPROM interactively from the serial monitor, and of course you can erase saved credentials. ## How locate the link button to the AutoConnect menu? Link button to AutoConnect menu can be embedded into Sketch's web page. The root path of the menu is **/_ac** by default and embed the following `````` tag in the generating HTML. ```html MENU ``` ## How much memory does AutoConnect consume? ### Sketch size It increases about 53K bytes compared to the case without AutoConnect. A sketch size of the most simple example introduced in the Getting started is about 330K bytes. (270K byte without AutoConnect) ### Heap size It consumes about 2K bytes in the static and about 12K bytes are consumed at the moment when menu executed. ## I cannot complete to Wi-Fi login from smartphone. Because AutoConnect does not send a login success response to the captive portal requests from the smartphone. The login success response varies iOS, Android and Windows. By analyzing the request URL of different login success inquiries for each OS, the correct behavior can be implemented, but not yet. Please resets ESP8266 from the AutoConnect menu. ## I cannot see the custom Web page. If the sketch is correct, a JSON syntax error may have occurred. In this case, activate the [AC_DEBUG](faq.md#3-turn-on-the-debug-log-options) and rerun. If you take the message of JSON syntax error, the [Json Assistant](https://arduinojson.org/v5/assistant/) helps syntax checking. This online tool is provided by the author of ArduinoJson and is most consistent for the AutoConnect. ## AutoConnect behaves not stable with my sketch yet. If AutoConnect behavior is not stable with your sketch, you can try the following measures. ### 1. Change WiFi channel Both ESP8266 and ESP32 can only work on one channel at any given moment. This will cause your station to lose connectivity on the channel hosting the captive portal. If the channel of the AP which you want to connect is different from the SoftAP channel, the operation of the captive portal will not respond with the screen of the AutoConnect connection attempt remains displayed. In such a case, please try the [AutoConnectConfig](apiconfig.md#autoconnectconfig) to match the [channel](apiconfig.md#channel) to the access point. ### 2. Change arduino core version I recommend change installed an arduino core version to the upstream when your sketch is not stable with AutoConnect on each board. #### with ESP8266 arduino core To stabilize the behavior, You can select the [lwIP](http://lwip.wikia.com/wiki/LwIP_Wiki) variant to contribute. Lower memory option of Arduino IDE for core version 2.4.2 is based on the lwIP-v2. On the other hand, the core version 2.5.0 upstream is based on the lwIP-2.1.2 stable release. You can select the option from Arduino IDE as **Tool** menu, if you are using ESP8266 core 2.5.0. It can be select `lwIP v2 Lower Memory` option. (not `lwIP v2 Lower Memory (no features)`) It is expected to improve response performance and stability. #### with ESP32 arduino core The [arduino-esp32](https://github.com/espressif/arduino-esp32) is still under development even if it is a stable release. It is necessary to judge whether the cause of the problem is the core or AutoConnect. Trace the log with the esp32 core and the AutoConnect debug option enabled for problem diagnosis and please you check the [issue of arduino-esp32](https://github.com/espressif/arduino-esp32/issues). The problem that your sketch possesses may already have been solved. ### 3. Turn on the debug log options To fully enable for the AutoConnect debug logging options, change the following two files. AutoConnectDefs.h ```cpp #define AC_DEBUG ``` PageBuilder.h [^2] ```cpp #define PB_DEBUG ``` [^2]: `PageBuilder.h` file exists in the `libraries/PageBuilder/src` directory under your sketch folder. ### 4. Reports the issue to AutoConnect repository on Github If you can not solve AutoConnect problems please report to [Issues](https://github.com/Hieromon/AutoConnect/issues). And please make your question comprehensively, not a statement. Include all relevant information to start the problem diagnostics as follows: * [x] Hardware module * [x] Arduino core version (Including the upstream tag ID.) * [x] Operating System which you use * [x] lwIP variant * [x] Problem description * [x] If you have a STACK DUMP decoded result with formatted by the code block tag * [x] The sketch code with formatted by the code block tag (Reduce to the reproducible minimum code for the problem) * [x] Debug messages output