Registering the "not found" handler is a different way than ESP8266WebServer. The onNotFound of ESP8266WebServer does not work with AutoConnect. AutoConnect overrides ESP8266WebServer::onNotFound to handle a captive portal. To register "not found" handler, use AutoConnect::onNotFound.
Registering the "not found" handler is a different way than ESP8266WebServer/WebServer. The onNotFound of ESP8266WebServer/WebServer does not work with AutoConnect. AutoConnect overrides ESP8266WebServer::onNotFound/WebServer::onNotFound to handle a captive portal. To register "not found" handler, use AutoConnect::onNotFound.
When the captive portal is started, SoftAP starts and the STA is disconnected. The current SSID setting memorized in ESP8266 will be lost. +
When the captive portal is started, SoftAP starts and the STA is disconnected. The current SSID setting memorized in ESP8266 will be lost but then the reconnect behavior of ESP32 is somewhat different from this. +The WiFiSTAClass::disconnect function implemented in the arduino-esp32 has extended parameters than the ESP8266's arduino-core. The second parameter of WiFi.disconnect on the arduino-esp32 core that does not exist in the ESP8266WiFiSTAClass has the effect of deleting the currently connected WiFi configuration and its default value is "false". On the ESP32 platform, even if WiFi.disconnect is executed, WiFi.begin() without the parameters in the next turn will try to connect to that AP. That is, automatic reconnection is implemented in arduino-esp32 already. Although this behavior appears seemingly competent, it is rather a disadvantage in scenes where you want to change the access point each time. When explicitly disconnecting WiFi from the Disconnect menu, AutoConnect will erase the AP connection settings saved by arduino-esp32 core. AutoConnect's automatic reconnection is a mechanism independent from the automatic reconnection of the arduino-esp32 core. If the autoReconnect option of the AutoConnectConfig class is enabled, it automatically attempts to reconnect to the disconnected past access point. When the autoReconnect option is specified, AutoConnect will not start SoftAP immediately if the first WiFi.begin fails. It will scan WiFi signal and the same connection information as the detected BSSID is stored in EEPROM as AutoConnect's credentials, explicitly apply it with WiFi.begin and rerun.
AutoConnect Portal; AutoConnectConfig Config; @@ -745,6 +746,10 @@ If the autoReconnect< Portal.begin();
In ESP32, the credentials for AutoConnect are not in NVS
The credentials used by AutoConnect are not saved in NVS on ESP32 module. ESP-IDF saves the WiFi connection configuration to NVS, but AutoConnect stores it on the eeprom partition. You can find the partition table for default as default.csv
The captive portal will only be activated if the first WiFi::begin fails. Sketch can detect with the AutoConnect::onDetect function that the captive portal has started. For example, the sketch can be written like as follows that turns on the LED at the start captive portal.
AutoConnect Portal; @@ -823,10 +828,10 @@ If the autoReconnect< EEPROM library uses one sector of flash located just after the SPIFFS. -So in the default state, the credential storage area used by AutoConnect conflicts with data owned by the user sketch. It will be destroyed together saved data in EEPROM by user sketch and AutoConnect each other. But you can move the storage area to avoid this. +Also, the placement of the EEPROM area of ESP32 is described in the partition table. So in the default state, the credential storage area used by AutoConnect conflicts with data owned by the user sketch. It will be destroyed together saved data in EEPROM by user sketch and AutoConnect each other. But you can move the storage area to avoid this. The boundaryOffset in AutoConnectConfig specifies the start offset of the credentials storage area. The default value is 0. - Refers the hosted ESP8266WebServer¶ -Constructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer inside the AutoConnect. This object variable could be referred by AutoConnect::host() function to access ESP8266WebServer instance as like below. + Refers the hosted ESP8266WebServer/WebServer¶ +Constructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer/WebServer inside the AutoConnect. This object variable could be referred by AutoConnect::host() function to access ESP8266WebServer/WebServer instance as like below. AutoConnect Portal; Portal.begin(); @@ -838,8 +843,8 @@ If the autoReconnect< When host() is valid The host() can be referred at after AutoConnect::begin. - Usage for automatically instantiated ESP8266WebServer¶ -The sketch can handle URL requests using ESP8266WebServer that AutoConnect started internally. ESP8266WebServer instantiated dynamically by AutoConnect can be referred to by AutoConnect::host function. The sketch can use the 'on' function, 'send' function, 'client' function and others by ESP8266WebServer reference of its return value. + Usage for automatically instantiated ESP8266WebServer/WebServer¶ +The sketch can handle URL requests using ESP8266WebServer or WebServer that AutoConnect started internally. ESP8266WebServer/WebServer instantiated dynamically by AutoConnect can be referred to by AutoConnect::host function. The sketch can use the 'on' function, 'send' function, 'client' function and others by ESP8266WebServer/WebServer reference of its return value. #include <ESP8266WiFi.h> #include <ESP8266WebServer.h> #include <AutoConnect.h> @@ -875,12 +880,12 @@ If the autoReconnect< -ESP8266WebServer function should be called after AutoConnect::begin -The sketch cannot refer to an instance of ESP8266WebServer until AutoConnect::begin completes successfully. +ESP8266WebServer/WebServer function should be called after AutoConnect::begin +The sketch cannot refer to an instance of ESP8266WebServer/WebServer until AutoConnect::begin completes successfully. -Do not use with ESP8266WebServer::begin -ESP8266WebServer is already running inside the AutoConnect. +Do not use with ESP8266WebServer::begin or WebServer::begin +ESP8266WebServer/WebServer is already running inside the AutoConnect. Use with the PageBuilder library¶ In ordinary, the URL handler will respond the request by sending some HTML. PageBuilder library is HTML assembly aid. it can handle predefined HTML as like a template and simplify an HTML string assemble logic, and also the generated HTML send automatically. @@ -917,8 +922,8 @@ If the autoReconnect<
EEPROM library uses one sector of flash located just after the SPIFFS.
So in the default state, the credential storage area used by AutoConnect conflicts with data owned by the user sketch. It will be destroyed together saved data in EEPROM by user sketch and AutoConnect each other. But you can move the storage area to avoid this.
Also, the placement of the EEPROM area of ESP32 is described in the partition table. So in the default state, the credential storage area used by AutoConnect conflicts with data owned by the user sketch. It will be destroyed together saved data in EEPROM by user sketch and AutoConnect each other. But you can move the storage area to avoid this.
The boundaryOffset in AutoConnectConfig specifies the start offset of the credentials storage area. The default value is 0.
Constructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer inside the AutoConnect. This object variable could be referred by AutoConnect::host() function to access ESP8266WebServer instance as like below.
Constructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer/WebServer inside the AutoConnect. This object variable could be referred by AutoConnect::host() function to access ESP8266WebServer/WebServer instance as like below.
AutoConnect Portal; Portal.begin(); @@ -838,8 +843,8 @@ If the autoReconnect< When host() is valid The host() can be referred at after AutoConnect::begin.
When host() is valid
The host() can be referred at after AutoConnect::begin.
The sketch can handle URL requests using ESP8266WebServer that AutoConnect started internally. ESP8266WebServer instantiated dynamically by AutoConnect can be referred to by AutoConnect::host function. The sketch can use the 'on' function, 'send' function, 'client' function and others by ESP8266WebServer reference of its return value.
The sketch can handle URL requests using ESP8266WebServer or WebServer that AutoConnect started internally. ESP8266WebServer/WebServer instantiated dynamically by AutoConnect can be referred to by AutoConnect::host function. The sketch can use the 'on' function, 'send' function, 'client' function and others by ESP8266WebServer/WebServer reference of its return value.
#include <ESP8266WiFi.h> #include <ESP8266WebServer.h> #include <AutoConnect.h> @@ -875,12 +880,12 @@ If the autoReconnect<
ESP8266WebServer function should be called after AutoConnect::begin
The sketch cannot refer to an instance of ESP8266WebServer until AutoConnect::begin completes successfully.
ESP8266WebServer/WebServer function should be called after AutoConnect::begin
The sketch cannot refer to an instance of ESP8266WebServer/WebServer until AutoConnect::begin completes successfully.
Do not use with ESP8266WebServer::begin
ESP8266WebServer is already running inside the AutoConnect.
Do not use with ESP8266WebServer::begin or WebServer::begin
ESP8266WebServer/WebServer is already running inside the AutoConnect.
In ordinary, the URL handler will respond the request by sending some HTML. PageBuilder library is HTML assembly aid. it can handle predefined HTML as like a template and simplify an HTML string assemble logic, and also the generated HTML send automatically.
It is also possible to assign static IP Address to ESP8266 in STA mode. By default DHCP is enabled and it becomes the IP address assigned by the DHCP server with WiFi.begin.
To assign a static IP to ESP8266 with WIFI_MODE_STA, the following parameters are required:
It is also possible to assign static IP Address to ESP8266/ESP32 in STA mode. By default DHCP is enabled and it becomes the IP address assigned by the DHCP server with WiFi.begin.
To assign a static IP to ESP8266/ESP32 with WIFI_MODE_STA, the following parameters are required:
#include <AutoConnect.h>
#define AC_DEBUG // Monitor message output activation #define AC_DEBUG_PORT Serial // Default message output device #define AUTOCONNECT_AP_IP 0x01F4A8C0 // Default SoftAP IP @@ -1142,15 +1142,24 @@
AutoConnect default constructor. This entry internally allocates the ESP8266WebServer and is activated internally.
AutoConnect default constructor. This entry internally allocates the ESP8266WebServer for ESP8266 or WebServer for ESP32 and is activated internally.
AutoConnect(ESP8266WebServer& webServer)
Run the AutoConnect site using the externally ensured ESP8266WebServer.
The handleClient function of AutoConnect can include the response of the URI handler added by the user using the "on" function of ESP8266WebServer. If ESP8266WebServer is assigned internally by AutoConnect, the sketch can obtain that reference with the host function. +
AutoConnect(WebServer& webServer) +
Run the AutoConnect site using the externally ensured ESP8266WebServer for ESP8266 or WebServer for ESP32.
The handleClient function of AutoConnect can include the response of the URI handler added by the user using the "on" function of ESP8266WebServer/WebServer. If ESP8266WebServer/WebServer is assigned internally by AutoConnect, the sketch can obtain that reference with the host function.
bool begin(const char* ssid, const char* passphraase)
bool begin(const char* ssid, const char* passphraase, unsinged long timeout) +bool begin(const char* ssid, const char* passphraase, unsigned long timeout) Starts establishing the WiFi connection. -AutoConnect first invokes WiFi.begin. If the case of SSID and Password missing, its WiFi.begin has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer will be started immediately after the first WiFi.beign regardless of the result. +AutoConnect first invokes WiFi.begin. If the case of SSID and Password missing, its WiFi.begin has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer/WebServer will be started immediately after the first WiFi.begin regardless of the result. The captive portal will not be started if the connection has been established with first WiFi.begin. If the connection cannot establish, switch to WIFI_AP_STA mode and activate SoftAP. Then DNS server starts.
bool begin(const char* ssid, const char* passphraase, unsigned long timeout)
Starts establishing the WiFi connection. -AutoConnect first invokes WiFi.begin. If the case of SSID and Password missing, its WiFi.begin has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer will be started immediately after the first WiFi.beign regardless of the result.
The captive portal will not be started if the connection has been established with first WiFi.begin. If the connection cannot establish, switch to WIFI_AP_STA mode and activate SoftAP. Then DNS server starts.
void end()
Stops AutoConnect captive portal service. Release ESP8266WebServer and DNSServer.
Stops AutoConnect captive portal service. Release ESP8266WebServer/WebServer and DNSServer.
Attention to end
The end function releases the instance of ESP8266WebServer and DNSServer. It can not process them after the end function.
The end function releases the instance of ESP8266WebServer/WebServer and DNSServer. It can not process them after the end function.
void handleClient()
Process the AutoConnect menu interface. It will be processed the client request too contained in the user sketch handler by calling from inside of AutoConnect to the hosted ESP8266WebServer::handleClient.
Process the AutoConnect menu interface. The handleClient() function of the ESP8266WebServer/WebServer hosted by AutoConnect is also called from within AutoConnect and client requests contained in the user sketch handler are also handled.
void handleRequest()
Handling for the AutoConnect menu request.
About used in combination with handleClient
The handleRequest function is not supposed to use with AutoConnect::handleClient. It should be used with ESP8266::handleClient.
The handleRequest function is not supposed to use with AutoConnect::handleClient. It should be used with ESP8266WebServer::handleClient or WebServer::handleClient.
void home(String uri) @@ -1220,12 +1229,21 @@ AutoConnect first invokes WiFi.begin. If the case of SSID and Password
Returns the reference of the ESP8266WebServer which is allocated in AutoConnect automatically.
ESP8266WebServer& host() +Returns the reference of the ESP8266WebServer/WebServer which is allocated in AutoConnect automatically. +
Returns the reference of the ESP8266WebServer/WebServer which is allocated in AutoConnect automatically.
ESP8266WebServer& host() +
WebServer& host()
&reference is not a pointer
void onNotFound(ESP8266WebServer::THandlerFunction fn) +
void onNotFound(WebServer::THandlerFunction fn)
Automatically reconnect to past established access point (BSSID) when the current configured SSID in ESP8266 could not be connected. By enabling this option, AutoConnect::begin() function will attempt to reconnect to a known access point using credentials stored in the EEPROM, even if the connection failed by current SSID. +
Automatically will try to reconnect with the past established access point (BSSID) when the current configured SSID in ESP8266/ESP32 could not be connected. By enabling this option, AutoConnect::begin() function will attempt to reconnect to a known access point using credentials stored in the EEPROM, even if the connection failed by current SSID. If the connection fails, starts the captive portal in SoftAP + STA mode.
How embed the AutoConnect to the sketches you have. Most simple approach to applying AutoConnect for the existing sketches, follow the below steps.
How embed the AutoConnect to the sketches you have. Most simple approach to applying AutoConnect for the existing sketches, follow the below steps. The below sketch is for ESP8266. For ESP32, replace ESP8266WebServer with WebServer and ESP8266WiFi.h with WiFi.h respectively.
ESP8266WebServer
WebServer
ESP8266WiFi.h
WiFi.h
#include <ESP8266WebServer.h>
ESP8266WebServer.h
AutoConnect.h
WebServer.h
ESP8266WebServer::on
WebServer::on
AutoConnect::begin()
AutoConnect::handleClient()
ESP8266WebServer::handleClient()
AutoConnect::handleRequest()
WebServer::handleClient
Two options are available for AutoConnect constructor.
AutoConnect VARIABLE(&ESP8266WebServer); +AutoConnect VARIABLE(&ESP8266WebServer); // For ESP8266 +AutoConnect VARIABLE(&WebServer); // For ESP32 or AutoConnect VARIABLE; @@ -705,44 +706,44 @@ or -The parameter with an ESP8266WebServer variable: An ESP8266WebServer object variable must be declared. AutoConnect uses its variable to handles the AutoConnect menu. +The parameter with an ESP8266WebServer/WebServer variable: An ESP8266WebServer/WebServer object variable must be declared. AutoConnect uses its variable to handles the AutoConnect menu. -With no parameter: The sketch does not declare ESP8266WebServer object. In this case, AutoConnect allocates an instance of the ESP8266WebServer internally. The logic sequence of the sketch is somewhat different as the above. To register a URL handler function by ESP8266WebServer::on should be performed after AutoConnect::begin. +With no parameter: The sketch does not declare ESP8266WebServer/WebServer object. In this case, AutoConnect allocates an instance of the ESP8266WebServer/WebServer internally. The logic sequence of the sketch is somewhat different as the above. To register a URL handler function by ESP8266WebServer::on or WebServer::on should be performed after AutoConnect::begin. 3. No need WiFI.begin(...)¶ AutoConnect internally performs WiFi.begin to establish a WiFi connection. There is no need for a general process to establish a connection using WiFi.begin with a sketch code. -4. Alternate ESP8266WebServer::begin()¶ -AutoConnect::begin executes ESP8266WebServer::begin internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call ESP8266WebServer::begin with the sketch. +4. Alternate ESP8266WebServer::begin() and WebServer::begin()¶ +AutoConnect::begin executes ESP8266WebServer::begin/WebServer::begin internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call ESP8266WebServer::begin/WebServer::begin with the sketch. Why DNS Server starts AutoConnect traps the detection of the captive portal and achieves a connection with the WLAN interactively by the AutoConnect menu. It responds SoftAP address to all DNS queries temporarily to trap. When the WLAN connection establishes, then stops DNS server. 5. AutoConnect::begin with SSID and Password¶ -SSID and Password can also specify by AutoConnect::begin. ESP8266 uses provided SSID and Password explicitly. If the connection false with specified SSID with Password then a captive portal is activated. SSID and Password are not present, ESP8266 SDK will attempt to connect using the still effectual SSID and password. Usually, it succeeds. -6. Use ESP8266WebServer::on to handle URL¶ -AutoConnect is designed to coexist with the process for handling the web pages by user sketches. The page processing function which will send an HTML to the client invoked by the "on::ESP8266WebServer" function is the same as when using ESP8266WebServer natively. -7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()¶ -Both classes member function name is the same: handleClient, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient has limitations. Refer to the below section for details. - ESP8266WebServer hosted or parasitic¶ -The interoperable process with an ESP8266WebServer depends on the parameters of the AutoConnect constructor. +SSID and Password can also specify by AutoConnect::begin. ESP8266/ESP32 uses provided SSID and Password explicitly. If the connection false with specified SSID with Password then a captive portal is activated. SSID and Password are not present, ESP8266 SDK will attempt to connect using the still effectual SSID and password. Usually, it succeeds. +6. Use ESP8266WebServer::on and WebServer::on to handle URL¶ +AutoConnect is designed to coexist with the process for handling the web pages by user sketches. The page processing function which will send an HTML to the client invoked by the "on::ESP8266WebServer" or the "on::WebServer" function is the same as when using ESP8266WebServer/WebServer natively. +7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()¶ +Both classes member function name is the same: handleClient, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient/WebServer::handleClient has limitations. Refer to the below section for details. + ESP8266WebServer/WebServer hosted or parasitic¶ +The interoperable process with an ESP8266WebServer/WebServer depends on the parameters of the AutoConnect constructor. Declaration parameter for the constructor -Use ESP8266WebServer::handleClient only +Use ESP8266WebServer::handleClient or WebServer::handleClient only Use AutoConnect::handleClient None -AutoConnect menu not available.To use AutoConnect menu, need AutoConnect::handleRequest().also to use ESP8266WebServer natively, need AutoConnect::host(). +AutoConnect menu not available.To use AutoConnect menu, need AutoConnect::handleRequest().also to use ESP8266WebServer/WebServer natively, need AutoConnect::host(). AutoConnect menu available.To use ESP8266WebServer natively, need AutoConnect::host(). -Reference to ESP8266WebServer +Reference to ESP8266WebServer/WebServer AutoConnect menu not available.To use AutoConnect menu, need AutoConnect::handleRequest(). AutoConnect menu available. @@ -750,22 +751,22 @@ or -By declaration for the AutoConnect variable with no parameter: The ESP8266WebServer instance is hosted by AutoConnect automatically then the sketches use AutoConnect::host as API to get it after AutoConnect::begin performed. +By declaration for the AutoConnect variable with no parameter: The ESP8266WebServer/WebServer instance is hosted by AutoConnect automatically then the sketches use AutoConnect::host as API to get it after AutoConnect::begin performed. -By declaration for the AutoConnect variable with the reference of ESP8266WebServer: AutoConnect will use it. The sketch can use it is too. +By declaration for the AutoConnect variable with the reference of ESP8266WebServer/WebServer: AutoConnect will use it. The sketch can use it is too. -In use ESP8266WebServer::handleClient(): AutoConnect menu can be dispatched but not works normally. It is necessary to call AutoConnect::handleRequest after ESP8255WebServer::handleClient invoking. +In use ESP8266WebServer::handleClient()/WebServer::handleClient(): AutoConnect menu can be dispatched but not works normally. It is necessary to call AutoConnect::handleRequest after ESP8255WebServer::handleClient/WebServer::handleClient invoking. In use AutoConnect::handleClient(): The handleClient() process and the AutoConnect menu is available without calling ESP8266WebServer::handleClient. -Why AutoConnect::handleRequest is needed when using ESP8266::handleClient -The AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside ESP8266WebServer::handleClient. -AutoConnect::handleClient is equivalent ESP8266WebServer::handleClient included AutoConnect::handleRequest. +Why AutoConnect::handleRequest is needed when using ESP8266WebServer::handleClient/WebServer::handleClient +The AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside ESP8266WebServer::handleClient and WebServer::handleClient. +AutoConnect::handleClient is equivalent ESP8266WebServer::handleClient and WEbServer::handleClient included AutoConnect::handleRequest. diff --git a/docs/changelog/index.html b/docs/changelog/index.html index 6a12ab7..479de94 100644 --- a/docs/changelog/index.html +++ b/docs/changelog/index.html @@ -10,7 +10,7 @@ - + @@ -42,7 +42,7 @@ - Change log - AutoConnect for ESP8266 + Change log - AutoConnect for ESP8266/ESP32 @@ -101,7 +101,7 @@ - + Skip to content @@ -110,7 +110,7 @@ - + @@ -124,7 +124,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 Change log @@ -249,7 +249,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 @@ -400,6 +400,13 @@ Table of contents + + + [0.9.5] Aug.27, 2018. + + + + [0.9.4] May 5, 2018. @@ -469,6 +476,13 @@ Table of contents + + + [0.9.5] Aug.27, 2018. + + + + [0.9.4] May 5, 2018. @@ -516,7 +530,12 @@ Change log - [0.9.4] May 5, 2018.¶ + [0.9.5] Aug.27, 2018.¶ + +Supports ESP32. +Fixed that crash may occur if the number of stored credentials in the EEPROM is smaller than the number of found WiFi networks. + +[0.9.4] May 5, 2018.¶ Automatically focus passphrase after selecting SSID with Configure New AP. Supports AutoConnectConfig::autoReconnect option, it will scan the WLAN when it can not connect to the default SSID, apply the applicable credentials if it is saved, and try reconnecting. diff --git a/docs/examples/index.html b/docs/examples/index.html index f3b9c66..d7d359d 100644 --- a/docs/examples/index.html +++ b/docs/examples/index.html @@ -10,7 +10,7 @@ - + @@ -42,7 +42,7 @@ - Examples - AutoConnect for ESP8266 + Examples - AutoConnect for ESP8266/ESP32 @@ -110,7 +110,7 @@ - + @@ -124,7 +124,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 Examples @@ -249,7 +249,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 diff --git a/docs/faq/index.html b/docs/faq/index.html index 33c3769..096379d 100644 --- a/docs/faq/index.html +++ b/docs/faq/index.html @@ -10,7 +10,7 @@ - + @@ -42,7 +42,7 @@ - FAQ - AutoConnect for ESP8266 + FAQ - AutoConnect for ESP8266/ESP32 @@ -110,7 +110,7 @@ - + @@ -124,7 +124,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 FAQ @@ -249,7 +249,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 diff --git a/docs/gettingstarted/index.html b/docs/gettingstarted/index.html index 7de93c9..3b52b15 100644 --- a/docs/gettingstarted/index.html +++ b/docs/gettingstarted/index.html @@ -10,7 +10,7 @@ - + @@ -42,7 +42,7 @@ - Getting started - AutoConnect for ESP8266 + Getting started - AutoConnect for ESP8266/ESP32 @@ -110,7 +110,7 @@ - + @@ -124,7 +124,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 Getting started @@ -249,7 +249,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 @@ -544,11 +544,11 @@ Let's do the most simple sketch¶ Open the Arduino IDE, write the following sketch and upload it. The feature of this sketch is that the SSID and Password are not coded. -#include <ESP8266WiFi.h> -#include <ESP8266WebServer.h> +#include <ESP8266WiFi.h> // Replace with WiFi.h for ESP32 +#include <ESP8266WebServer.h> // Replace with WebServer.h for ESP32 #include <AutoConnect.h> -ESP8266WebServer Server; +ESP8266WebServer Server; // Replace with WebServer for ESP32 AutoConnect Portal(Server); void rootPage() { @@ -572,8 +572,11 @@ } + +The above code can be applied to ESP8266. To apply to ESP32, replace ESP8266WebServer class with WebServer and include WiFi.h and WebServer.h appropriately. + Run at first¶ -After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open Wi-Fi settings from the Settings Apps. You can see the esp8266ap in the list of "CHOOSE A NETWORK...". Then tap the esp8266ap and enter password 12345678, a something screen pops up automatically as shown below. +After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open Wi-Fi settings from the Settings Apps. You can see the esp8266ap 1 in the list of "CHOOSE A NETWORK...". Then tap the esp8266ap and enter password 12345678, a something screen pops up automatically as shown below. This is the AutoConnect statistics screen. This screen displays the current status of the established connection, WiFi mode, IP address, free memory size, and etc. Also, the hamburger icon is the control menu of AutoConnect seems at the upper right. By tap the hamburger icon, the control menu appears as the below. Join to the new access point¶ @@ -592,6 +595,15 @@ Or, "RESET" can be selected. The ESP8266 resets and reboots. Af Gifffer(); } + + + + + +When applied to ESP32, esp32ap ↩ + + + diff --git a/docs/index.html b/docs/index.html index a33fbfd..f713f07 100644 --- a/docs/index.html +++ b/docs/index.html @@ -10,7 +10,7 @@ - + @@ -42,7 +42,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 @@ -101,7 +101,7 @@ - + Skip to content @@ -110,7 +110,7 @@ - + @@ -124,7 +124,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 Overview @@ -249,7 +249,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 @@ -654,22 +654,22 @@ - AutoConnect for ESP8266¶ -An Arduino library for ESP8266 WLAN configuration at run time with web interface. + AutoConnect for ESP8266/ESP32¶ +An Arduino library for ESP8266/ESP32 WLAN configuration at run time with web interface. Overview¶ -To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with ESP8266WebServer class. -Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi connection. With this library to make a sketch easily which connects from ESP8266 to the access point at runtime by the web interface without hard-coded SSID and password. +To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with ESP8266WebServer class for ESP8266 or WebServer class for ESP32. +Easy implementing the Web interface constituting the WLAN for ESP8266/ESP32 WiFi connection. With this library to make a sketch easily which connects from ESP8266/ESP32 to the access point at runtime by the web interface without hard-coded SSID and password. No need pre-coded SSID & password¶ -It is no needed hard-coding in advance the SSID and Password into the sketch to connect between ESP8266 and WLAN. You can input SSID & Password from a smartphone via the web interface at runtime. +It is no needed hard-coding in advance the SSID and Password into the sketch to connect between ESP8266/ESP32 and WLAN. You can input SSID & Password from a smartphone via the web interface at runtime. Simple usage¶ AutoConnect control screen will be displayed automatically for establishing new connections. It aids by the captive portal when vested the connection cannot be detected.By using the AutoConnect menu, to manage the connections convenient. Store the established connection¶ -The connection authentication data as credentials are saved automatically in EEPROM of ESP8266 and You can select the past SSID from the AutoConnect menu. +The connection authentication data as credentials are saved automatically in EEPROM of ESP8266/ESP32 and You can select the past SSID from the AutoConnect menu. Easy to embed in¶ AutoConnect can be placed easily in your sketch. It's "begin" and "handleClient" only. Lives with the your sketches¶ -The sketches which provide the web page using ESP8266WebServer there is, AutoConnect will not disturb it. AutoConnect can use an already instantiated ESP8266WebServer object, or itself can assign it. +The sketches which provide the web page using ESP8266WebServer there is, AutoConnect will not disturb it. AutoConnect can use an already instantiated ESP8266WebServer object, or itself can assign it.This efficacy can also be applied to ESP32. The corresponding class for ESP32 will be the WebServer. Installation¶ Requirements¶ Supported hardware¶ @@ -682,6 +682,13 @@ Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi conne Olimex MOD-WIFI-ESP8266 SparkFun Thing SweetPea ESP-210 + ESP32Dev Board (applying the Espressif's arduino-esp32 core) + SparkFun ESP32 Thing + WEMOS LOLIN D32 + Ai-Thinker NodeMCU-32S + Heltec WiFi Kit 32 + M5Stack + And other ESP8266/ESP32 modules supported by the Additional Board Manager URLs of the Arduino-IDE. About flash size on the module @@ -694,15 +701,13 @@ Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi conne ESP8266 Arduino core AutoConnect targets sketches made on the assumption of ESP8266 Community's Arduino core. The latest release is recommended. Install third-party platform using the Boards Manager of Arduino IDE. Package URL is http://arduino.esp8266.com/stable/package_esp8266com_index.json + ESP32 Arduino core +Also, to apply AutoConnect to ESP32, the arduino-esp32 core provided by Espressif is needed. The latest release is recommended. +Install third-party platform using the Boards Manager of Arduino IDE. You can add multiple URLs into Additional Board Manager URLs field, separating them with commas. Package URL is https://dl.espressif.com/dl/package_esp32_index.json Additional necessary library The PageBuilder library to build HTML for ESP8266WebServer is needed. -To install the PageBuilder library into your Arduino IDE, you can use the Library Manager. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword 'PageBuilder' with the topic 'Communication', then you can see the PageBuilder. The latest version or 1.0.0 later is required. +To install the PageBuilder library into your Arduino IDE, you can use the Library Manager. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword 'PageBuilder' with the topic 'Communication', then you can see the PageBuilder. The latest version is required 1.1.0 later for ESP32. - -Library Manager of Arduino IDE -The version of PageBuilder may not have been updated yet. If the library manager shows only version 0.93.0, please install the latest PageBuilder version than 1.0.0 from the Github repository. The PageBuilder release of the Github repository is the latest version. The PlatformIO library has the latest version of 1.0.0. -In 0.93.0, the PageBuilder class has a compile error about without the 'cancel' method. - Install the AutoConnect¶ Clone or download from the AutoConnect GitHub repository. @@ -710,7 +715,7 @@ In 0.93.0, the PageBuilder class has a compile error about without the 'cancel' Supported by Library manager. -AutoConnect was added to the Arduino IDE library manager as of March 17, 2018. It can be used with the PlatformIO library also. +AutoConnect was added to the Arduino IDE library manager. It can be used with the PlatformIO library also.
AutoConnect VARIABLE(&ESP8266WebServer); // For ESP8266 +AutoConnect VARIABLE(&WebServer); // For ESP32
AutoConnect VARIABLE; @@ -705,44 +706,44 @@ or
The parameter with an ESP8266WebServer variable: An ESP8266WebServer object variable must be declared. AutoConnect uses its variable to handles the AutoConnect menu.
The parameter with an ESP8266WebServer/WebServer variable: An ESP8266WebServer/WebServer object variable must be declared. AutoConnect uses its variable to handles the AutoConnect menu.
With no parameter: The sketch does not declare ESP8266WebServer object. In this case, AutoConnect allocates an instance of the ESP8266WebServer internally. The logic sequence of the sketch is somewhat different as the above. To register a URL handler function by ESP8266WebServer::on should be performed after AutoConnect::begin.
With no parameter: The sketch does not declare ESP8266WebServer/WebServer object. In this case, AutoConnect allocates an instance of the ESP8266WebServer/WebServer internally. The logic sequence of the sketch is somewhat different as the above. To register a URL handler function by ESP8266WebServer::on or WebServer::on should be performed after AutoConnect::begin.
AutoConnect internally performs WiFi.begin to establish a WiFi connection. There is no need for a general process to establish a connection using WiFi.begin with a sketch code.
AutoConnect::begin executes ESP8266WebServer::begin internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call ESP8266WebServer::begin with the sketch.
AutoConnect::begin executes ESP8266WebServer::begin/WebServer::begin internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call ESP8266WebServer::begin/WebServer::begin with the sketch.
Why DNS Server starts
AutoConnect traps the detection of the captive portal and achieves a connection with the WLAN interactively by the AutoConnect menu. It responds SoftAP address to all DNS queries temporarily to trap. When the WLAN connection establishes, then stops DNS server.
SSID and Password can also specify by AutoConnect::begin. ESP8266 uses provided SSID and Password explicitly. If the connection false with specified SSID with Password then a captive portal is activated. SSID and Password are not present, ESP8266 SDK will attempt to connect using the still effectual SSID and password. Usually, it succeeds.
AutoConnect is designed to coexist with the process for handling the web pages by user sketches. The page processing function which will send an HTML to the client invoked by the "on::ESP8266WebServer" function is the same as when using ESP8266WebServer natively.
Both classes member function name is the same: handleClient, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient has limitations. Refer to the below section for details.
The interoperable process with an ESP8266WebServer depends on the parameters of the AutoConnect constructor.
SSID and Password can also specify by AutoConnect::begin. ESP8266/ESP32 uses provided SSID and Password explicitly. If the connection false with specified SSID with Password then a captive portal is activated. SSID and Password are not present, ESP8266 SDK will attempt to connect using the still effectual SSID and password. Usually, it succeeds.
AutoConnect is designed to coexist with the process for handling the web pages by user sketches. The page processing function which will send an HTML to the client invoked by the "on::ESP8266WebServer" or the "on::WebServer" function is the same as when using ESP8266WebServer/WebServer natively.
Both classes member function name is the same: handleClient, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient/WebServer::handleClient has limitations. Refer to the below section for details.
The interoperable process with an ESP8266WebServer/WebServer depends on the parameters of the AutoConnect constructor.
By declaration for the AutoConnect variable with no parameter: The ESP8266WebServer instance is hosted by AutoConnect automatically then the sketches use AutoConnect::host as API to get it after AutoConnect::begin performed.
By declaration for the AutoConnect variable with no parameter: The ESP8266WebServer/WebServer instance is hosted by AutoConnect automatically then the sketches use AutoConnect::host as API to get it after AutoConnect::begin performed.
By declaration for the AutoConnect variable with the reference of ESP8266WebServer: AutoConnect will use it. The sketch can use it is too.
By declaration for the AutoConnect variable with the reference of ESP8266WebServer/WebServer: AutoConnect will use it. The sketch can use it is too.
In use ESP8266WebServer::handleClient(): AutoConnect menu can be dispatched but not works normally. It is necessary to call AutoConnect::handleRequest after ESP8255WebServer::handleClient invoking.
In use ESP8266WebServer::handleClient()/WebServer::handleClient(): AutoConnect menu can be dispatched but not works normally. It is necessary to call AutoConnect::handleRequest after ESP8255WebServer::handleClient/WebServer::handleClient invoking.
In use AutoConnect::handleClient(): The handleClient() process and the AutoConnect menu is available without calling ESP8266WebServer::handleClient.
Why AutoConnect::handleRequest is needed when using ESP8266::handleClient
The AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside ESP8266WebServer::handleClient. -AutoConnect::handleClient is equivalent ESP8266WebServer::handleClient included AutoConnect::handleRequest.
Why AutoConnect::handleRequest is needed when using ESP8266WebServer::handleClient/WebServer::handleClient
The AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside ESP8266WebServer::handleClient and WebServer::handleClient. +AutoConnect::handleClient is equivalent ESP8266WebServer::handleClient and WEbServer::handleClient included AutoConnect::handleRequest.
Open the Arduino IDE, write the following sketch and upload it. The feature of this sketch is that the SSID and Password are not coded.
#include <ESP8266WiFi.h> -#include <ESP8266WebServer.h> +#include <ESP8266WiFi.h> // Replace with WiFi.h for ESP32 +#include <ESP8266WebServer.h> // Replace with WebServer.h for ESP32 #include <AutoConnect.h> -ESP8266WebServer Server; +ESP8266WebServer Server; // Replace with WebServer for ESP32 AutoConnect Portal(Server); void rootPage() { @@ -572,8 +572,11 @@ } + +The above code can be applied to ESP8266. To apply to ESP32, replace ESP8266WebServer class with WebServer and include WiFi.h and WebServer.h appropriately. + Run at first¶ -After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open Wi-Fi settings from the Settings Apps. You can see the esp8266ap in the list of "CHOOSE A NETWORK...". Then tap the esp8266ap and enter password 12345678, a something screen pops up automatically as shown below. +After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open Wi-Fi settings from the Settings Apps. You can see the esp8266ap 1 in the list of "CHOOSE A NETWORK...". Then tap the esp8266ap and enter password 12345678, a something screen pops up automatically as shown below. This is the AutoConnect statistics screen. This screen displays the current status of the established connection, WiFi mode, IP address, free memory size, and etc. Also, the hamburger icon is the control menu of AutoConnect seems at the upper right. By tap the hamburger icon, the control menu appears as the below. Join to the new access point¶ @@ -592,6 +595,15 @@ Or, "RESET" can be selected. The ESP8266 resets and reboots. Af Gifffer(); } + + + + + +When applied to ESP32, esp32ap ↩ + + + diff --git a/docs/index.html b/docs/index.html index a33fbfd..f713f07 100644 --- a/docs/index.html +++ b/docs/index.html @@ -10,7 +10,7 @@ - + @@ -42,7 +42,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 @@ -101,7 +101,7 @@ - + Skip to content @@ -110,7 +110,7 @@ - + @@ -124,7 +124,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 Overview @@ -249,7 +249,7 @@ - AutoConnect for ESP8266 + AutoConnect for ESP8266/ESP32 @@ -654,22 +654,22 @@ - AutoConnect for ESP8266¶ -An Arduino library for ESP8266 WLAN configuration at run time with web interface. + AutoConnect for ESP8266/ESP32¶ +An Arduino library for ESP8266/ESP32 WLAN configuration at run time with web interface. Overview¶ -To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with ESP8266WebServer class. -Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi connection. With this library to make a sketch easily which connects from ESP8266 to the access point at runtime by the web interface without hard-coded SSID and password. +To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with ESP8266WebServer class for ESP8266 or WebServer class for ESP32. +Easy implementing the Web interface constituting the WLAN for ESP8266/ESP32 WiFi connection. With this library to make a sketch easily which connects from ESP8266/ESP32 to the access point at runtime by the web interface without hard-coded SSID and password. No need pre-coded SSID & password¶ -It is no needed hard-coding in advance the SSID and Password into the sketch to connect between ESP8266 and WLAN. You can input SSID & Password from a smartphone via the web interface at runtime. +It is no needed hard-coding in advance the SSID and Password into the sketch to connect between ESP8266/ESP32 and WLAN. You can input SSID & Password from a smartphone via the web interface at runtime. Simple usage¶ AutoConnect control screen will be displayed automatically for establishing new connections. It aids by the captive portal when vested the connection cannot be detected.By using the AutoConnect menu, to manage the connections convenient. Store the established connection¶ -The connection authentication data as credentials are saved automatically in EEPROM of ESP8266 and You can select the past SSID from the AutoConnect menu. +The connection authentication data as credentials are saved automatically in EEPROM of ESP8266/ESP32 and You can select the past SSID from the AutoConnect menu. Easy to embed in¶ AutoConnect can be placed easily in your sketch. It's "begin" and "handleClient" only. Lives with the your sketches¶ -The sketches which provide the web page using ESP8266WebServer there is, AutoConnect will not disturb it. AutoConnect can use an already instantiated ESP8266WebServer object, or itself can assign it. +The sketches which provide the web page using ESP8266WebServer there is, AutoConnect will not disturb it. AutoConnect can use an already instantiated ESP8266WebServer object, or itself can assign it.This efficacy can also be applied to ESP32. The corresponding class for ESP32 will be the WebServer. Installation¶ Requirements¶ Supported hardware¶ @@ -682,6 +682,13 @@ Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi conne Olimex MOD-WIFI-ESP8266 SparkFun Thing SweetPea ESP-210 + ESP32Dev Board (applying the Espressif's arduino-esp32 core) + SparkFun ESP32 Thing + WEMOS LOLIN D32 + Ai-Thinker NodeMCU-32S + Heltec WiFi Kit 32 + M5Stack + And other ESP8266/ESP32 modules supported by the Additional Board Manager URLs of the Arduino-IDE. About flash size on the module @@ -694,15 +701,13 @@ Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi conne ESP8266 Arduino core AutoConnect targets sketches made on the assumption of ESP8266 Community's Arduino core. The latest release is recommended. Install third-party platform using the Boards Manager of Arduino IDE. Package URL is http://arduino.esp8266.com/stable/package_esp8266com_index.json + ESP32 Arduino core +Also, to apply AutoConnect to ESP32, the arduino-esp32 core provided by Espressif is needed. The latest release is recommended. +Install third-party platform using the Boards Manager of Arduino IDE. You can add multiple URLs into Additional Board Manager URLs field, separating them with commas. Package URL is https://dl.espressif.com/dl/package_esp32_index.json Additional necessary library The PageBuilder library to build HTML for ESP8266WebServer is needed. -To install the PageBuilder library into your Arduino IDE, you can use the Library Manager. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword 'PageBuilder' with the topic 'Communication', then you can see the PageBuilder. The latest version or 1.0.0 later is required. +To install the PageBuilder library into your Arduino IDE, you can use the Library Manager. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword 'PageBuilder' with the topic 'Communication', then you can see the PageBuilder. The latest version is required 1.1.0 later for ESP32. - -Library Manager of Arduino IDE -The version of PageBuilder may not have been updated yet. If the library manager shows only version 0.93.0, please install the latest PageBuilder version than 1.0.0 from the Github repository. The PageBuilder release of the Github repository is the latest version. The PlatformIO library has the latest version of 1.0.0. -In 0.93.0, the PageBuilder class has a compile error about without the 'cancel' method. - Install the AutoConnect¶ Clone or download from the AutoConnect GitHub repository. @@ -710,7 +715,7 @@ In 0.93.0, the PageBuilder class has a compile error about without the 'cancel' Supported by Library manager. -AutoConnect was added to the Arduino IDE library manager as of March 17, 2018. It can be used with the PlatformIO library also. +AutoConnect was added to the Arduino IDE library manager. It can be used with the PlatformIO library also.
#include <ESP8266WiFi.h> // Replace with WiFi.h for ESP32 +#include <ESP8266WebServer.h> // Replace with WebServer.h for ESP32 #include <AutoConnect.h> -ESP8266WebServer Server; +ESP8266WebServer Server; // Replace with WebServer for ESP32 AutoConnect Portal(Server); void rootPage() { @@ -572,8 +572,11 @@ }
The above code can be applied to ESP8266. To apply to ESP32, replace ESP8266WebServer class with WebServer and include WiFi.h and WebServer.h appropriately.
After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open Wi-Fi settings from the Settings Apps. You can see the esp8266ap in the list of "CHOOSE A NETWORK...". Then tap the esp8266ap and enter password 12345678, a something screen pops up automatically as shown below.
After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open Wi-Fi settings from the Settings Apps. You can see the esp8266ap 1 in the list of "CHOOSE A NETWORK...". Then tap the esp8266ap and enter password 12345678, a something screen pops up automatically as shown below.
This is the AutoConnect statistics screen. This screen displays the current status of the established connection, WiFi mode, IP address, free memory size, and etc. Also, the hamburger icon is the control menu of AutoConnect seems at the upper right. By tap the hamburger icon, the control menu appears as the below.
When applied to ESP32, esp32ap ↩
An Arduino library for ESP8266 WLAN configuration at run time with web interface.
An Arduino library for ESP8266/ESP32 WLAN configuration at run time with web interface.
To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with ESP8266WebServer class. -Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi connection. With this library to make a sketch easily which connects from ESP8266 to the access point at runtime by the web interface without hard-coded SSID and password.
To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with ESP8266WebServer class for ESP8266 or WebServer class for ESP32. +Easy implementing the Web interface constituting the WLAN for ESP8266/ESP32 WiFi connection. With this library to make a sketch easily which connects from ESP8266/ESP32 to the access point at runtime by the web interface without hard-coded SSID and password.
It is no needed hard-coding in advance the SSID and Password into the sketch to connect between ESP8266 and WLAN. You can input SSID & Password from a smartphone via the web interface at runtime.
It is no needed hard-coding in advance the SSID and Password into the sketch to connect between ESP8266/ESP32 and WLAN. You can input SSID & Password from a smartphone via the web interface at runtime.
AutoConnect control screen will be displayed automatically for establishing new connections. It aids by the captive portal when vested the connection cannot be detected.By using the AutoConnect menu, to manage the connections convenient.
The connection authentication data as credentials are saved automatically in EEPROM of ESP8266 and You can select the past SSID from the AutoConnect menu.
The connection authentication data as credentials are saved automatically in EEPROM of ESP8266/ESP32 and You can select the past SSID from the AutoConnect menu.
AutoConnect can be placed easily in your sketch. It's "begin" and "handleClient" only.
The sketches which provide the web page using ESP8266WebServer there is, AutoConnect will not disturb it. AutoConnect can use an already instantiated ESP8266WebServer object, or itself can assign it.
The sketches which provide the web page using ESP8266WebServer there is, AutoConnect will not disturb it. AutoConnect can use an already instantiated ESP8266WebServer object, or itself can assign it.This efficacy can also be applied to ESP32. The corresponding class for ESP32 will be the WebServer.
About flash size on the module
ESP8266 Arduino core
AutoConnect targets sketches made on the assumption of ESP8266 Community's Arduino core. The latest release is recommended. Install third-party platform using the Boards Manager of Arduino IDE. Package URL is http://arduino.esp8266.com/stable/package_esp8266com_index.json
ESP32 Arduino core
Also, to apply AutoConnect to ESP32, the arduino-esp32 core provided by Espressif is needed. The latest release is recommended. +Install third-party platform using the Boards Manager of Arduino IDE. You can add multiple URLs into Additional Board Manager URLs field, separating them with commas. Package URL is https://dl.espressif.com/dl/package_esp32_index.json
Additional necessary library
The PageBuilder library to build HTML for ESP8266WebServer is needed. -To install the PageBuilder library into your Arduino IDE, you can use the Library Manager. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword 'PageBuilder' with the topic 'Communication', then you can see the PageBuilder. The latest version or 1.0.0 later is required.
Library Manager of Arduino IDE
The version of PageBuilder may not have been updated yet. If the library manager shows only version 0.93.0, please install the latest PageBuilder version than 1.0.0 from the Github repository. The PageBuilder release of the Github repository is the latest version. The PlatformIO library has the latest version of 1.0.0. -In 0.93.0, the PageBuilder class has a compile error about without the 'cancel' method.
Clone or download from the AutoConnect GitHub repository.
Supported by Library manager.
AutoConnect was added to the Arduino IDE library manager as of March 17, 2018. It can be used with the PlatformIO library also.
AutoConnect was added to the Arduino IDE library manager. It can be used with the PlatformIO library also.