From 8cb41a65bc64d238507db9514422882d2e40df74 Mon Sep 17 00:00:00 2001
From: Hieromon Ikasamo <hieromon@gmail.com>
Date: Fri, 14 Sep 2018 17:10:04 +0900
Subject: [PATCH] Supports ESP32

---
 docs/404.html                  |  10 +--
 docs/advancedusage/index.html  |  57 +++++++-------
 docs/api/index.html            |  81 +++++++++++++-------
 docs/basicusage/index.html     |  93 +++++++++++------------
 docs/changelog/index.html      |  33 ++++++--
 docs/examples/index.html       |  10 +--
 docs/faq/index.html            |  10 +--
 docs/gettingstarted/index.html |  30 +++++---
 docs/index.html                |  45 ++++++-----
 docs/license/index.html        |  10 +--
 docs/menu/index.html           |  24 +++---
 docs/search/search_index.json  | 133 +++++++++++++++++----------------
 docs/sitemap.xml               |  20 ++---
 examples/mqttRSSI/mqttRSSI.ino |  13 +++-
 mkdocs/api.md                  |  56 ++++++++++----
 mkdocs/changelog.md            |   5 ++
 16 files changed, 372 insertions(+), 258 deletions(-)

diff --git a/docs/404.html b/docs/404.html
index 9a5cc25..054d12f 100644
--- a/docs/404.html
+++ b/docs/404.html
@@ -10,7 +10,7 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
       
@@ -40,7 +40,7 @@
     
     
       
-        <title>AutoConnect for ESP8266</title>
+        <title>AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -104,7 +104,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="/AutoConnect/images/arduino-logo.svg" width="24" height="24">
           
@@ -118,7 +118,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 
@@ -243,7 +243,7 @@
         <img src="/AutoConnect/images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
diff --git a/docs/advancedusage/index.html b/docs/advancedusage/index.html
index a01c634..976d43d 100644
--- a/docs/advancedusage/index.html
+++ b/docs/advancedusage/index.html
@@ -10,7 +10,7 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/advancedusage/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>Advanced usage - AutoConnect for ESP8266</title>
+        <title>Advanced usage - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Advanced usage
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -417,15 +417,15 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#refers-the-hosted-esp8266webserver" title=" Refers the hosted ESP8266WebServer" class="md-nav__link">
-     Refers the hosted ESP8266WebServer
+  <a href="#refers-the-hosted-esp8266webserverwebserver" title=" Refers the hosted ESP8266WebServer/WebServer" class="md-nav__link">
+     Refers the hosted ESP8266WebServer/WebServer
   </a>
   
 </li>
         
           <li class="md-nav__item">
-  <a href="#usage-for-automatically-instantiated-esp8266webserver" title=" Usage for automatically instantiated ESP8266WebServer" class="md-nav__link">
-     Usage for automatically instantiated ESP8266WebServer
+  <a href="#usage-for-automatically-instantiated-esp8266webserverwebserver" title=" Usage for automatically instantiated ESP8266WebServer/WebServer" class="md-nav__link">
+     Usage for automatically instantiated ESP8266WebServer/WebServer
   </a>
   
 </li>
@@ -637,15 +637,15 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#refers-the-hosted-esp8266webserver" title=" Refers the hosted ESP8266WebServer" class="md-nav__link">
-     Refers the hosted ESP8266WebServer
+  <a href="#refers-the-hosted-esp8266webserverwebserver" title=" Refers the hosted ESP8266WebServer/WebServer" class="md-nav__link">
+     Refers the hosted ESP8266WebServer/WebServer
   </a>
   
 </li>
         
           <li class="md-nav__item">
-  <a href="#usage-for-automatically-instantiated-esp8266webserver" title=" Usage for automatically instantiated ESP8266WebServer" class="md-nav__link">
-     Usage for automatically instantiated ESP8266WebServer
+  <a href="#usage-for-automatically-instantiated-esp8266webserverwebserver" title=" Usage for automatically instantiated ESP8266WebServer/WebServer" class="md-nav__link">
+     Usage for automatically instantiated ESP8266WebServer/WebServer
   </a>
   
 </li>
@@ -724,9 +724,10 @@
                 
                 <h2 id="advanced-usage">Advanced usage<a class="headerlink" href="#advanced-usage" title="Permanent link">&para;</a></h2>
 <h3 id="404-handler"><i class="fa fa-caret-right"></i> 404 handler<a class="headerlink" href="#404-handler" title="Permanent link">&para;</a></h3>
-<p>Registering the "not found" handler is a different way than ESP8266WebServer. The <em>onNotFound</em> of ESP8266WebServer does not work with AutoConnect. AutoConnect overrides <em>ESP8266WebServer::onNotFound</em> to handle a captive portal. To register "not found" handler, use <a href="../api/index.html#onnotfound"><em>AutoConnect::onNotFound</em></a>.</p>
+<p>Registering the "not found" handler is a different way than ESP8266WebServer/WebServer. The <em>onNotFound</em> of ESP8266WebServer/WebServer does not work with AutoConnect. AutoConnect overrides <em>ESP8266WebServer::onNotFound</em>/<em>WebServer::onNotFound</em> to handle a captive portal. To register "not found" handler, use <a href="../api/index.html#onnotfound"><em>AutoConnect::onNotFound</em></a>.</p>
 <h3 id="automatic-reconnect"><i class="fa fa-caret-right"></i> Automatic reconnect<a class="headerlink" href="#automatic-reconnect" title="Permanent link">&para;</a></h3>
-<p>When the captive portal is started, SoftAP starts and the STA is disconnected. The current SSID setting memorized in ESP8266 will be lost.<br />
+<p>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.<br />
+The <a href="https://github.com/espressif/arduino-esp32/blob/a0f0bd930cfd2d607bf3d3288f46e2d265dd2e11/libraries/WiFi/src/WiFiSTA.h#L46">WiFiSTAClass::disconnect</a> 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 <a href="https://github.com/esp8266/Arduino/blob/7e1bdb225da8ab337373517e6a86a99432921a86/libraries/ESP8266WiFi/src/ESP8266WiFiSTA.cpp#L296">ESP8266WiFiSTAClass</a> 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.<br />
 If the <a href="../api/index.html#autoreconnect"><strong>autoReconnect</strong></a> option of the <a href="../api/index.html#autoconnectconfig-api"><strong>AutoConnectConfig</strong></a> 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.</p>
 <div class="codehilite"><pre><span></span><span class="n">AutoConnect</span>       <span class="n">Portal</span><span class="p">;</span>
 <span class="n">AutoConnectConfig</span> <span class="n">Config</span><span class="p">;</span>
@@ -745,6 +746,10 @@ If the <a href="../api/index.html#autoreconnect"><strong>autoReconnect</strong><
 <span class="n">Portal</span><span class="p">.</span><span class="nf">begin</span><span class="p">();</span>
 </pre></div>
 
+<div class="admonition note">
+<p class="admonition-title">In ESP32, the credentials for AutoConnect are not in NVS</p>
+<p>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 <a href="https://github.com/espressif/arduino-esp32/blob/master/tools/partitions/default.csv">default.csv</a></p>
+</div>
 <h3 id="captive-portal-start-detection"><i class="fa fa-caret-right"></i> Captive portal start detection<a class="headerlink" href="#captive-portal-start-detection" title="Permanent link">&para;</a></h3>
 <p>The captive portal will only be activated if the first <em>WiFi::begin</em> fails. Sketch can detect with the <a href="../api/index.html#ondetect"><em>AutoConnect::onDetect</em></a> 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.</p>
 <div class="codehilite"><pre><span></span><span class="n">AutoConnect</span> <span class="n">Portal</span><span class="p">;</span>
@@ -823,10 +828,10 @@ If the <a href="../api/index.html#autoreconnect"><strong>autoReconnect</strong><
 <blockquote>
 <p>EEPROM library uses one sector of flash located <a href="http://arduino-esp8266.readthedocs.io/en/latest/libraries.html?highlight=SPIFFS#eeprom">just after the SPIFFS</a>.</p>
 </blockquote>
-<p>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.</p>
+<p>Also, the placement of the EEPROM area of ESP32 is described in the <a href="https://github.com/espressif/arduino-esp32/blob/master/tools/partitions/default.csv">partition table</a>. 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.</p>
 <p>The <a href="../api/index.html#boundaryoffset"><strong>boundaryOffset</strong></a> in <a href="../api/index.html#autoconnectconfig-api"><strong>AutoConnectConfig</strong></a> specifies the start offset of the credentials storage area. The default value is 0.</p>
-<h3 id="refers-the-hosted-esp8266webserver"><i class="fa fa-caret-right"></i> Refers the hosted ESP8266WebServer<a class="headerlink" href="#refers-the-hosted-esp8266webserver" title="Permanent link">&para;</a></h3>
-<p>Constructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer inside the AutoConnect. This object variable could be referred by <a href="../api/index.html#host"><em>AutoConnect::host()</em></a> function to access ESP8266WebServer instance as like below.</p>
+<h3 id="refers-the-hosted-esp8266webserverwebserver"><i class="fa fa-caret-right"></i> Refers the hosted ESP8266WebServer/WebServer<a class="headerlink" href="#refers-the-hosted-esp8266webserverwebserver" title="Permanent link">&para;</a></h3>
+<p>Constructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer/WebServer inside the AutoConnect. This object variable could be referred by <a href="../api/index.html#host"><em>AutoConnect::host()</em></a> function to access ESP8266WebServer/WebServer instance as like below.</p>
 <div class="codehilite"><pre><span></span><span class="n">AutoConnect</span> <span class="n">Portal</span><span class="p">;</span>
 
 <span class="n">Portal</span><span class="p">.</span><span class="nf">begin</span><span class="p">();</span>
@@ -838,8 +843,8 @@ If the <a href="../api/index.html#autoreconnect"><strong>autoReconnect</strong><
 <p class="admonition-title">When host() is valid</p>
 <p>The host() can be referred at after <em>AutoConnect::begin</em>.</p>
 </div>
-<h3 id="usage-for-automatically-instantiated-esp8266webserver"><i class="fa fa-caret-right"></i> Usage for automatically instantiated ESP8266WebServer<a class="headerlink" href="#usage-for-automatically-instantiated-esp8266webserver" title="Permanent link">&para;</a></h3>
-<p>The sketch can handle URL requests using ESP8266WebServer that AutoConnect started internally. ESP8266WebServer instantiated dynamically by AutoConnect can be referred to by <a href="../api/index.html#host"><em>AutoConnect::host</em></a> function. The sketch can use the '<strong>on</strong>' function, '<strong>send</strong>' function, '<strong>client</strong>' function and others by ESP8266WebServer reference of its return value.</p>
+<h3 id="usage-for-automatically-instantiated-esp8266webserverwebserver"><i class="fa fa-caret-right"></i> Usage for automatically instantiated ESP8266WebServer/WebServer<a class="headerlink" href="#usage-for-automatically-instantiated-esp8266webserverwebserver" title="Permanent link">&para;</a></h3>
+<p>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 <a href="../api/index.html#host"><em>AutoConnect::host</em></a> function. The sketch can use the '<strong>on</strong>' function, '<strong>send</strong>' function, '<strong>client</strong>' function and others by ESP8266WebServer/WebServer reference of its return value.</p>
 <div class="codehilite"><pre><span></span><span class="cp">#include</span> <span class="cpf">&lt;ESP8266WiFi.h&gt;</span><span class="cp"></span>
 <span class="cp">#include</span> <span class="cpf">&lt;ESP8266WebServer.h&gt;</span><span class="cp"></span>
 <span class="cp">#include</span> <span class="cpf">&lt;AutoConnect.h&gt;</span><span class="cp"></span>
@@ -875,12 +880,12 @@ If the <a href="../api/index.html#autoreconnect"><strong>autoReconnect</strong><
 </pre></div>
 
 <div class="admonition note">
-<p class="admonition-title">ESP8266WebServer function should be called after AutoConnect::begin</p>
-<p>The sketch cannot refer to an instance of ESP8266WebServer until AutoConnect::begin completes successfully.</p>
+<p class="admonition-title">ESP8266WebServer/WebServer function should be called after AutoConnect::begin</p>
+<p>The sketch cannot refer to an instance of ESP8266WebServer/WebServer until AutoConnect::begin completes successfully.</p>
 </div>
 <div class="admonition warning">
-<p class="admonition-title">Do not use with ESP8266WebServer::begin</p>
-<p>ESP8266WebServer is already running inside the AutoConnect.</p>
+<p class="admonition-title">Do not use with ESP8266WebServer::begin or WebServer::begin</p>
+<p>ESP8266WebServer/WebServer is already running inside the AutoConnect.</p>
 </div>
 <h3 id="use-with-the-pagebuilder-library"><i class="fa fa-caret-right"></i> Use with the <a href="https://github.com/Hieromon/PageBuilder">PageBuilder</a> library<a class="headerlink" href="#use-with-the-pagebuilder-library" title="Permanent link">&para;</a></h3>
 <p>In ordinary, the URL handler will respond the request by sending some HTML. <a href="https://github.com/Hieromon/PageBuilder">PageBuilder</a> 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.</p>
@@ -917,8 +922,8 @@ If the <a href="../api/index.html#autoreconnect"><strong>autoReconnect</strong><
 </pre></div>
 
 <h3 id="static-ip-assignment-1"><i class="fa fa-caret-right"></i> Static IP assignment <sup id="fnref:1"><a class="footnote-ref" href="#fn:1" rel="footnote">1</a></sup><a class="headerlink" href="#static-ip-assignment-1" title="Permanent link">&para;</a></h3>
-<p>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 <em>WiFi.begin</em>.</p>
-<p>To assign a static IP to ESP8266 with WIFI_MODE_STA, the following parameters are required:</p>
+<p>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 <em>WiFi.begin</em>.</p>
+<p>To assign a static IP to ESP8266/ESP32 with WIFI_MODE_STA, the following parameters are required:</p>
 <ul>
 <li>IP address.</li>
 <li>Gateway address.</li>
diff --git a/docs/api/index.html b/docs/api/index.html
index d803df1..2585bc2 100644
--- a/docs/api/index.html
+++ b/docs/api/index.html
@@ -10,7 +10,7 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/api/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>Library APIs - AutoConnect for ESP8266</title>
+        <title>Library APIs - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Library APIs
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -381,8 +381,8 @@
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
-  <a href="#define-macros" title="Define macros" class="md-nav__link">
-    Define macros
+  <a href="#defined-macros" title="Defined macros" class="md-nav__link">
+    Defined macros
   </a>
   
 </li>
@@ -786,8 +786,8 @@
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
-  <a href="#define-macros" title="Define macros" class="md-nav__link">
-    Define macros
+  <a href="#defined-macros" title="Defined macros" class="md-nav__link">
+    Defined macros
   </a>
   
 </li>
@@ -1121,7 +1121,7 @@
 <div class="codehilite"><pre><span></span><span class="cp">#include</span> <span class="cpf">&lt;AutoConnect.h&gt;</span><span class="cp"></span>
 </pre></div>
 
-<h4 id="define-macros">Define macros<a class="headerlink" href="#define-macros" title="Permanent link">&para;</a></h4>
+<h4 id="defined-macros">Defined macros<a class="headerlink" href="#defined-macros" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span></span><span class="cp">#define AC_DEBUG                                </span><span class="c1">// Monitor message output activation</span>
 <span class="cp">#define AC_DEBUG_PORT           Serial          </span><span class="c1">// Default message output device</span>
 <span class="cp">#define AUTOCONNECT_AP_IP       0x01F4A8C0      </span><span class="c1">// Default SoftAP IP</span>
@@ -1142,15 +1142,24 @@
 </pre></div>
 
 <p><a id="withparameter"></a></p>
-<p>AutoConnect default constructor. This entry internally allocates the ESP8266WebServer and is activated internally.</p>
+<p>AutoConnect default constructor. This entry internally allocates the ESP8266WebServer for ESP8266 or WebServer for ESP32 and is activated internally.</p>
+<ul>
+<li>For ESP8266</li>
+</ul>
 <div class="codehilite"><pre><span></span><span class="n">AutoConnect</span><span class="p">(</span><span class="n">ESP8266WebServer</span><span class="o">&amp;</span> <span class="n">webServer</span><span class="p">)</span>
 </pre></div>
 
-<p>Run the AutoConnect site using the externally ensured ESP8266WebServer.</p>
-<p>The <a href="index.html#handleclient"><strong>handleClient</strong></a> function of AutoConnect can include the response of the URI handler added by the user using the "<em>on</em>" function of ESP8266WebServer. If ESP8266WebServer is assigned internally by AutoConnect, the sketch can obtain that reference with the <a href="../api.me#host"><strong>host</strong></a> function.
+<ul>
+<li>For ESP32</li>
+</ul>
+<div class="codehilite"><pre><span></span><span class="n">AutoConnect</span><span class="p">(</span><span class="n">WebServer</span><span class="o">&amp;</span> <span class="n">webServer</span><span class="p">)</span>
+</pre></div>
+
+<p>Run the AutoConnect site using the externally ensured ESP8266WebServer for ESP8266 or WebServer for ESP32.</p>
+<p>The <a href="index.html#handleclient"><strong>handleClient</strong></a> function of AutoConnect can include the response of the URI handler added by the user using the "<em>on</em>" function of ESP8266WebServer/WebServer. If ESP8266WebServer/WebServer is assigned internally by AutoConnect, the sketch can obtain that reference with the <a href="../api.me#host"><strong>host</strong></a> function.
 <dl class="apidl">
     <dt><strong>Parameters</strong></dt>
-    <dd><span class="apidef">webServer</span>A reference of ESP8266WebServer instance.</dd>
+    <dd><span class="apidef">webServer</span>A reference of ESP8266WebServer or WebServer instance.</dd>
 </dl></p>
 <h3 id="public-member-functions"><i class="fa fa-code"></i> Public member functions<a class="headerlink" href="#public-member-functions" title="Permanent link">&para;</a></h3>
 <h4 id="begin">begin<a class="headerlink" href="#begin" title="Permanent link">&para;</a></h4>
@@ -1158,10 +1167,10 @@
 </pre></div>
 <div class="codehilite"><pre><span></span><span class="kt">bool</span> <span class="n">begin</span><span class="p">(</span><span class="k">const</span> <span class="kt">char</span><span class="o">*</span> <span class="n">ssid</span><span class="p">,</span> <span class="k">const</span> <span class="kt">char</span><span class="o">*</span> <span class="n">passphraase</span><span class="p">)</span>
 </pre></div>
-<div class="codehilite"><pre><span></span><span class="kt">bool</span> <span class="n">begin</span><span class="p">(</span><span class="k">const</span> <span class="kt">char</span><span class="o">*</span> <span class="n">ssid</span><span class="p">,</span> <span class="k">const</span> <span class="kt">char</span><span class="o">*</span> <span class="n">passphraase</span><span class="p">,</span> <span class="n">unsinged</span> <span class="kt">long</span> <span class="n">timeout</span><span class="p">)</span>
+<div class="codehilite"><pre><span></span><span class="kt">bool</span> <span class="n">begin</span><span class="p">(</span><span class="k">const</span> <span class="kt">char</span><span class="o">*</span> <span class="n">ssid</span><span class="p">,</span> <span class="k">const</span> <span class="kt">char</span><span class="o">*</span> <span class="n">passphraase</span><span class="p">,</span> <span class="kt">unsigned</span> <span class="kt">long</span> <span class="n">timeout</span><span class="p">)</span>
 </pre></div></p>
 <p>Starts establishing the WiFi connection.<br />
-AutoConnect first invokes <em>WiFi.begin</em>. If the case of SSID and Password missing, its <em>WiFi.begin</em> has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer will be started immediately after the first <em>WiFi.beign</em> regardless of the result.</p>
+AutoConnect first invokes <em>WiFi.begin</em>. If the case of SSID and Password missing, its <em>WiFi.begin</em> has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer/WebServer will be started immediately after the first <em>WiFi.begin</em> regardless of the result.</p>
 <p>The captive portal will not be started if the connection has been established with first <em>WiFi.begin</em>. If the connection cannot establish, switch to WIFI_AP_STA mode and activate SoftAP. Then DNS server starts.
 <dl class="apidl">
     <dt><strong>Parameters</strong></dt>
@@ -1181,7 +1190,7 @@ AutoConnect first invokes <em>WiFi.begin</em>. If the case of SSID and Password
 <dl class="apidl">
     <dt><strong>Parameters</strong></dt>
     <dd><span class="apidef">config</span>Reference to <a href="index.html#autoconnectconfig"><strong>AutoConnectConfig</strong></a> containing SoftAP's parameters and static IP parameters.</dd>
-    <dd><span class="apidef">ap</span>SSID for SoftAP. The default value is <strong>esp8266ap</strong>.</dd>
+    <dd><span class="apidef">ap</span>SSID for SoftAP. The default value is <strong>esp8266ap</strong> for ESP8266, <strong>esp32ap</strong> for ESP32.</dd>
     <dd><span class="apidef">password</span>Password for SodtAP. The default value is <strong>12345678</strong>.</dd>
     <dt><strong>Return value</strong></dt>
     <dd><span class="apidef">true</span>Successfully configured.</dd>
@@ -1191,16 +1200,16 @@ AutoConnect first invokes <em>WiFi.begin</em>. If the case of SSID and Password
 <div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">end</span><span class="p">()</span>
 </pre></div>
 
-<p>Stops AutoConnect captive portal service. Release ESP8266WebServer and DNSServer. </p>
+<p>Stops AutoConnect captive portal service. Release ESP8266WebServer/WebServer and DNSServer. </p>
 <div class="admonition warning">
 <p class="admonition-title">Attention to end</p>
-<p>The end function releases the instance of ESP8266WebServer and DNSServer. It can not process them after the end function.</p>
+<p>The end function releases the instance of ESP8266WebServer/WebServer and DNSServer. It can not process them after the end function.</p>
 </div>
 <h4 id="handleclient">handleClient<a class="headerlink" href="#handleclient" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">handleClient</span><span class="p">()</span>
 </pre></div>
 
-<p>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 <em>ESP8266WebServer::handleClient</em>.</p>
+<p>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.</p>
 <h4 id="handlerequest">handleRequest<a class="headerlink" href="#handlerequest" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">handleRequest</span><span class="p">()</span>
 </pre></div>
@@ -1208,7 +1217,7 @@ AutoConnect first invokes <em>WiFi.begin</em>. If the case of SSID and Password
 <p>Handling for the AutoConnect menu request.</p>
 <div class="admonition warning">
 <p class="admonition-title">About used in combination with handleClient</p>
-<p>The handleRequest function is not supposed to use with AutoConnect::handleClient. It should be used with ESP8266::handleClient.</p>
+<p>The handleRequest function is not supposed to use with AutoConnect::handleClient. It should be used with ESP8266WebServer::handleClient or WebServer::handleClient.</p>
 </div>
 <h4 id="home">home<a class="headerlink" href="#home" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">home</span><span class="p">(</span><span class="n">String</span> <span class="n">uri</span><span class="p">)</span>
@@ -1220,12 +1229,21 @@ AutoConnect first invokes <em>WiFi.begin</em>. If the case of SSID and Password
     <dd><span class="apidef">uri</span> A URI string of user site's home path.</dd>
 </dl></p>
 <h4 id="host">host<a class="headerlink" href="#host" title="Permanent link">&para;</a></h4>
-<p>Returns the reference of the ESP8266WebServer which is allocated in AutoConnect automatically.</p>
-<p><div class="codehilite"><pre><span></span><span class="n">ESP8266WebServer</span><span class="o">&amp;</span> <span class="n">host</span><span class="p">()</span>
+<p>Returns the reference of the ESP8266WebServer/WebServer which is allocated in AutoConnect automatically.</p>
+<ul>
+<li>For ESP8266</li>
+</ul>
+<div class="codehilite"><pre><span></span><span class="n">ESP8266WebServer</span><span class="o">&amp;</span> <span class="n">host</span><span class="p">()</span>
+</pre></div>
+
+<ul>
+<li>For ESP32</li>
+</ul>
+<p><div class="codehilite"><pre><span></span><span class="n">WebServer</span><span class="o">&amp;</span> <span class="n">host</span><span class="p">()</span>
 </pre></div>
 <dl class="apidl">
     <dt><strong>Return value</strong></dt>
-    <dd>A reference of the ESP8266WebServer.</dd>
+    <dd>A reference of the ESP8266WebServer/WebServer.</dd>
 </dl></p>
 <div class="admonition note">
 <p class="admonition-title">&amp;reference is not a pointer</p>
@@ -1257,7 +1275,16 @@ Register the function which will call from AutoConnect at the start of the capti
     <dd><span class="apidef">false</span>Cancel the captive portal. AutoConnect::begin function will return with a false.</dd>
 </dl></p>
 <h4 id="onnotfound">onNotFound<a class="headerlink" href="#onnotfound" title="Permanent link">&para;</a></h4>
-<p><div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">onNotFound</span><span class="p">(</span><span class="n">ESP8266WebServer</span><span class="o">::</span><span class="n">THandlerFunction</span> <span class="n">fn</span><span class="p">)</span>
+<ul>
+<li>For ESP8266</li>
+</ul>
+<div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">onNotFound</span><span class="p">(</span><span class="n">ESP8266WebServer</span><span class="o">::</span><span class="n">THandlerFunction</span> <span class="n">fn</span><span class="p">)</span>
+</pre></div>
+
+<ul>
+<li>For ESP32</li>
+</ul>
+<p><div class="codehilite"><pre><span></span><span class="kt">void</span> <span class="n">onNotFound</span><span class="p">(</span><span class="n">WebServer</span><span class="o">::</span><span class="n">THandlerFunction</span> <span class="n">fn</span><span class="p">)</span>
 </pre></div>
 Register the handler function for undefined URL request detected.
 <dl class="apidl">
@@ -1273,7 +1300,7 @@ Register the handler function for undefined URL request detected.
 </pre></div>
 <dl class="apidl">
     <dt><strong>Parameters</strong></dt>
-    <dd><span class="apidef">ap</span>SSID for SoftAP. The length should be up to 31. The default value is <strong>esp8266ap</strong>.</dd>
+    <dd><span class="apidef">ap</span>SSID for SoftAP. The length should be up to 31. The default value is <strong>esp8266ap</strong> for ESP8266, <strong>esp32ap</strong> for ESP32.</dd>
     <dd><span class="apidef">password</span>Password for SodtAP. The length should be from 8 to up to 63. The default value is <strong>12345678</strong>.</dd>
 </dl></p>
 <h3 id="public-member-variables"><i class="fa fa-code"></i> Public member variables<a class="headerlink" href="#public-member-variables" title="Permanent link">&para;</a></h3>
@@ -1290,7 +1317,7 @@ Register the handler function for undefined URL request detected.
     <dd><span class="apidef" style="width:230px;">IPAddress</span>The default value is <strong>192.168.244.1</strong></dd>
 </dl></p>
 <h4 id="autoreconnect">autoReconnect<a class="headerlink" href="#autoreconnect" title="Permanent link">&para;</a></h4>
-<p>Automatically reconnect to past established access point (BSSID) when the current configured SSID in ESP8266 could not be connected. By enabling this option, <em>AutoConnect::begin()</em> function will attempt to reconnect to a known access point using credentials stored in the EEPROM, even if the connection failed by current SSID.<br />
+<p>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, <em>AutoConnect::begin()</em> function will attempt to reconnect to a known access point using credentials stored in the EEPROM, even if the connection failed by current SSID.<br />
 If the connection fails, starts the captive portal in SoftAP + STA mode.<br />
 <dl class="apidl">
     <dt><strong>Type</strong></dt>
diff --git a/docs/basicusage/index.html b/docs/basicusage/index.html
index fcc62b7..01dc8d9 100644
--- a/docs/basicusage/index.html
+++ b/docs/basicusage/index.html
@@ -10,7 +10,7 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/basicusage/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>Basic usage - AutoConnect for ESP8266</title>
+        <title>Basic usage - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Basic usage
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -398,8 +398,8 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#4-alternate-esp8266webserverbegin" title="4. Alternate ESP8266WebServer::begin()" class="md-nav__link">
-    4. Alternate ESP8266WebServer::begin()
+  <a href="#4-alternate-esp8266webserverbegin-and-webserverbegin" title="4. Alternate ESP8266WebServer::begin() and WebServer::begin()" class="md-nav__link">
+    4. Alternate ESP8266WebServer::begin() and WebServer::begin()
   </a>
   
 </li>
@@ -412,15 +412,15 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#6-use-esp8266webserveron-to-handle-url" title="6. Use ESP8266WebServer::on to handle URL" class="md-nav__link">
-    6. Use ESP8266WebServer::on to handle URL
+  <a href="#6-use-esp8266webserveron-and-webserveron-to-handle-url" title="6. Use ESP8266WebServer::on and WebServer::on to handle URL" class="md-nav__link">
+    6. Use ESP8266WebServer::on and WebServer::on to handle URL
   </a>
   
 </li>
         
           <li class="md-nav__item">
-  <a href="#7-use-either-esp8266webserverhandleclient-or-autoconnecthandleclient" title="7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()" class="md-nav__link">
-    7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()
+  <a href="#7-use-either-esp8266webserverhandleclientwebserverhandleclient-or-autoconnecthandleclient" title="7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()" class="md-nav__link">
+    7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()
   </a>
   
 </li>
@@ -431,8 +431,8 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#esp8266webserver-hosted-or-parasitic" title=" ESP8266WebServer hosted or parasitic" class="md-nav__link">
-     ESP8266WebServer hosted or parasitic
+  <a href="#esp8266webserverwebserver-hosted-or-parasitic" title=" ESP8266WebServer/WebServer hosted or parasitic" class="md-nav__link">
+     ESP8266WebServer/WebServer hosted or parasitic
   </a>
   
 </li>
@@ -601,8 +601,8 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#4-alternate-esp8266webserverbegin" title="4. Alternate ESP8266WebServer::begin()" class="md-nav__link">
-    4. Alternate ESP8266WebServer::begin()
+  <a href="#4-alternate-esp8266webserverbegin-and-webserverbegin" title="4. Alternate ESP8266WebServer::begin() and WebServer::begin()" class="md-nav__link">
+    4. Alternate ESP8266WebServer::begin() and WebServer::begin()
   </a>
   
 </li>
@@ -615,15 +615,15 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#6-use-esp8266webserveron-to-handle-url" title="6. Use ESP8266WebServer::on to handle URL" class="md-nav__link">
-    6. Use ESP8266WebServer::on to handle URL
+  <a href="#6-use-esp8266webserveron-and-webserveron-to-handle-url" title="6. Use ESP8266WebServer::on and WebServer::on to handle URL" class="md-nav__link">
+    6. Use ESP8266WebServer::on and WebServer::on to handle URL
   </a>
   
 </li>
         
           <li class="md-nav__item">
-  <a href="#7-use-either-esp8266webserverhandleclient-or-autoconnecthandleclient" title="7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()" class="md-nav__link">
-    7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()
+  <a href="#7-use-either-esp8266webserverhandleclientwebserverhandleclient-or-autoconnecthandleclient" title="7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()" class="md-nav__link">
+    7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()
   </a>
   
 </li>
@@ -634,8 +634,8 @@
 </li>
         
           <li class="md-nav__item">
-  <a href="#esp8266webserver-hosted-or-parasitic" title=" ESP8266WebServer hosted or parasitic" class="md-nav__link">
-     ESP8266WebServer hosted or parasitic
+  <a href="#esp8266webserverwebserver-hosted-or-parasitic" title=" ESP8266WebServer/WebServer hosted or parasitic" class="md-nav__link">
+     ESP8266WebServer/WebServer hosted or parasitic
   </a>
   
 </li>
@@ -666,7 +666,7 @@
                 
                 <h2 id="simple-usage">Simple usage<a class="headerlink" href="#simple-usage" title="Permanent link">&para;</a></h2>
 <h3 id="embed-to-the-sketches"><i class="fa fa-edit"></i> Embed to the sketches<a class="headerlink" href="#embed-to-the-sketches" title="Permanent link">&para;</a></h3>
-<p>How embed the AutoConnect to the sketches you have. Most simple approach to applying AutoConnect for the existing sketches, follow the below steps.</p>
+<p>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 <code class="codehilite">ESP8266WebServer</code> with <code class="codehilite">WebServer</code> and <code class="codehilite">ESP8266WiFi.h</code> with <code class="codehilite">WiFi.h</code> respectively.</p>
 <p><img src="../images/BeforeAfter.svg" /></p>
 <ul class="ulsty-edit" style="list-style:none;">
   <li>Insert <code class="codehilite"><span class="cp">#include</span> <span class="cpf">&lt;AutoConnect.h&gt;</span></code> to behind of <code class="codehilite"><span class="cp">#include</span> <span class="cpf">&lt;ESP8266WebServer.h&gt;</span></code>.</li>
@@ -682,22 +682,23 @@
 <h4 id="1-a-typical-logic-sequence">1. A typical logic sequence<a class="headerlink" href="#1-a-typical-logic-sequence" title="Permanent link">&para;</a></h4>
 <div class="admonition note">
 <ol>
-<li><strong>Include headers,</strong> <code class="codehilite">ESP8266WebServer.h</code> and <code class="codehilite">AutoConnect.h</code>  </li>
+<li><strong>Include headers,</strong> <code class="codehilite">ESP8266WebServer.h</code>/<code class="codehilite">WebServer.h</code> and <code class="codehilite">AutoConnect.h</code>  </li>
 <li><strong>Declare ESP8266WebServer variable.</strong>  </li>
 <li><strong>Declare AutoConnect variable.</strong>  </li>
 <li><strong>Implements the URL handler with the <em>function()</em>.</strong>  </li>
 <li><strong>setup()</strong><br />
-   5.1 <strong>Sets URL handler <em>function()</em> to ESP8266WebServer by</strong><code class="codehilite">ESP8266WebServer::on</code><strong>.</strong><br />
+   5.1 <strong>Sets URL handler <em>function()</em> to ESP8266WebServer/WebServer by</strong><code class="codehilite">ESP8266WebServer::on</code><strong>/</strong><code class="codehilite">WebServer::on</code><strong>.</strong><br />
    5.2 <strong>Starts </strong><code class="codehilite">AutoConnect::begin()</code><strong>.</strong><br />
    5.3 <strong>Check WiFi connection status.</strong>  </li>
 <li><strong>loop()</strong><br />
-   6.1 <strong>Invokes </strong><code class="codehilite">AutoConnect::handleClient()</code><strong>, or invokes </strong><code class="codehilite">ESP8266WebServer::handleClient()</code><strong> then </strong><code class="codehilite">AutoConnect::handleRequest()</code><strong>.</strong><br />
+   6.1 <strong>Invokes </strong><code class="codehilite">AutoConnect::handleClient()</code><strong>, or invokes </strong><code class="codehilite">ESP8266WebServer::handleClient()</code><strong>/</strong><code class="codehilite">WebServer::handleClient</code><strong> then </strong><code class="codehilite">AutoConnect::handleRequest()</code><strong>.</strong><br />
    6.2 <strong>Do the process for actual sketch.</strong>  </li>
 </ol>
 </div>
 <h4 id="2-declare-autoconnect-object">2. Declare AutoConnect object<a class="headerlink" href="#2-declare-autoconnect-object" title="Permanent link">&para;</a></h4>
 <p><a href="#esp8266webserver-hosted-or-parasitic">Two options</a> are available for <a href="../api/index.html#constructors">AutoConnect constructor</a>.</p>
-<p><div class="codehilite"><pre><span></span><span class="n">AutoConnect</span> <span class="nf">VARIABLE</span><span class="p">(</span><span class="o">&amp;</span><span class="n">ESP8266WebServer</span><span class="p">);</span>
+<p><div class="codehilite"><pre><span></span><span class="n">AutoConnect</span> <span class="nf">VARIABLE</span><span class="p">(</span><span class="o">&amp;</span><span class="n">ESP8266WebServer</span><span class="p">);</span>  <span class="c1">// For ESP8266</span>
+<span class="n">AutoConnect</span> <span class="nf">VARIABLE</span><span class="p">(</span><span class="o">&amp;</span><span class="n">WebServer</span><span class="p">);</span>         <span class="c1">// For ESP32</span>
 </pre></div>
 or</p>
 <div class="codehilite"><pre><span></span><span class="n">AutoConnect</span> <span class="n">VARIABLE</span><span class="p">;</span>
@@ -705,44 +706,44 @@ or</p>
 
 <ul>
 <li>
-<p><strong>The parameter with an ESP8266WebServer variable:</strong> An ESP8266WebServer object variable must be declared. AutoConnect uses its variable to handles the <a href="../menu/index.html">AutoConnect menu</a>.</p>
+<p><strong>The parameter with an ESP8266WebServer/WebServer variable:</strong> An ESP8266WebServer/WebServer object variable must be declared. AutoConnect uses its variable to handles the <a href="../menu/index.html">AutoConnect menu</a>.</p>
 </li>
 <li>
-<p><strong>With no parameter:</strong> 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 <em>ESP8266WebServer::on</em> should be performed after <a href="../api/index.html#begin"><em>AutoConnect::begin</em></a>.</p>
+<p><strong>With no parameter:</strong> 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 <em>ESP8266WebServer::on</em> or <em>WebServer::on</em> should be performed after <a href="../api/index.html#begin"><em>AutoConnect::begin</em></a>.</p>
 </li>
 </ul>
 <h4 id="3-no-need-wifibegin">3. No need WiFI.begin(...)<a class="headerlink" href="#3-no-need-wifibegin" title="Permanent link">&para;</a></h4>
 <p>AutoConnect internally performs <em>WiFi.begin</em> to establish a WiFi connection. There is no need for a general process to establish a connection using <em>WiFi.begin</em> with a sketch code.</p>
-<h4 id="4-alternate-esp8266webserverbegin">4. Alternate ESP8266WebServer::begin()<a class="headerlink" href="#4-alternate-esp8266webserverbegin" title="Permanent link">&para;</a></h4>
-<p><a href="../api/index.html#begin"><em>AutoConnect::begin</em></a> executes <em>ESP8266WebServer::begin</em> internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call <em>ESP8266WebServer::begin</em> with the sketch.</p>
+<h4 id="4-alternate-esp8266webserverbegin-and-webserverbegin">4. Alternate ESP8266WebServer::begin() and WebServer::begin()<a class="headerlink" href="#4-alternate-esp8266webserverbegin-and-webserverbegin" title="Permanent link">&para;</a></h4>
+<p><a href="../api/index.html#begin"><em>AutoConnect::begin</em></a> executes <em>ESP8266WebServer::begin</em>/<em>WebServer::begin</em> internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call <em>ESP8266WebServer::begin</em>/<em>WebServer::begin</em> with the sketch.</p>
 <div class="admonition info">
 <p class="admonition-title">Why DNS Server starts</p>
 <p>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.</p>
 </div>
 <h4 id="5-autoconnectbegin-with-ssid-and-password">5. AutoConnect::begin with SSID and Password<a class="headerlink" href="#5-autoconnectbegin-with-ssid-and-password" title="Permanent link">&para;</a></h4>
-<p>SSID and Password can also specify by <a href="../api.me#begin"><em>AutoConnect::begin</em></a>. 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.</p>
-<h4 id="6-use-esp8266webserveron-to-handle-url">6. Use ESP8266WebServer::on to handle URL<a class="headerlink" href="#6-use-esp8266webserveron-to-handle-url" title="Permanent link">&para;</a></h4>
-<p>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 "<em>on::ESP8266WebServer</em>" function is the same as when using ESP8266WebServer natively.</p>
-<h4 id="7-use-either-esp8266webserverhandleclient-or-autoconnecthandleclient">7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()<a class="headerlink" href="#7-use-either-esp8266webserverhandleclient-or-autoconnecthandleclient" title="Permanent link">&para;</a></h4>
-<p>Both classes member function name is the same: <em>handleClient</em>, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient has limitations. Refer to the below section for details. </p>
-<h3 id="esp8266webserver-hosted-or-parasitic"><i class="fa fa-caret-right"></i> ESP8266WebServer hosted or parasitic<a class="headerlink" href="#esp8266webserver-hosted-or-parasitic" title="Permanent link">&para;</a></h3>
-<p>The interoperable process with an ESP8266WebServer depends on the parameters of the <a href="../api/index.html#constructors">AutoConnect constructor</a>.</p>
+<p>SSID and Password can also specify by <a href="../api.me#begin"><em>AutoConnect::begin</em></a>. 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.</p>
+<h4 id="6-use-esp8266webserveron-and-webserveron-to-handle-url">6. Use ESP8266WebServer::on and WebServer::on to handle URL<a class="headerlink" href="#6-use-esp8266webserveron-and-webserveron-to-handle-url" title="Permanent link">&para;</a></h4>
+<p>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 "<em>on::ESP8266WebServer</em>" or the "<em>on::WebServer</em>" function is the same as when using ESP8266WebServer/WebServer natively.</p>
+<h4 id="7-use-either-esp8266webserverhandleclientwebserverhandleclient-or-autoconnecthandleclient">7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()<a class="headerlink" href="#7-use-either-esp8266webserverhandleclientwebserverhandleclient-or-autoconnecthandleclient" title="Permanent link">&para;</a></h4>
+<p>Both classes member function name is the same: <em>handleClient</em>, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient/WebServer::handleClient has limitations. Refer to the below section for details. </p>
+<h3 id="esp8266webserverwebserver-hosted-or-parasitic"><i class="fa fa-caret-right"></i> ESP8266WebServer/WebServer hosted or parasitic<a class="headerlink" href="#esp8266webserverwebserver-hosted-or-parasitic" title="Permanent link">&para;</a></h3>
+<p>The interoperable process with an ESP8266WebServer/WebServer depends on the parameters of the <a href="../api/index.html#constructors">AutoConnect constructor</a>.</p>
 <table>
 <thead>
 <tr>
 <th>Declaration parameter for the constructor</th>
-<th>Use ESP8266WebServer::handleClient only</th>
+<th>Use ESP8266WebServer::handleClient or WebServer::handleClient only</th>
 <th>Use AutoConnect::handleClient</th>
 </tr>
 </thead>
 <tbody>
 <tr>
 <td><a href="../api/index.html#constructors">None</a></td>
-<td>AutoConnect menu not available.<br>To use AutoConnect menu, need <a href="../api/index.html#handlerequest">AutoConnect::handleRequest()</a>.<br>also to use ESP8266WebServer natively, need <a href="../api/index.html#host">AutoConnect::host()</a>.</td>
+<td>AutoConnect menu not available.<br>To use AutoConnect menu, need <a href="../api/index.html#handlerequest">AutoConnect::handleRequest()</a>.<br>also to use ESP8266WebServer/WebServer natively, need <a href="../api/index.html#host">AutoConnect::host()</a>.</td>
 <td>AutoConnect menu available.<br>To use ESP8266WebServer natively, need <a href="../api/index.html#host">AutoConnect::host()</a>.</td>
 </tr>
 <tr>
-<td><a href="../api/index.html#withparameter">Reference to ESP8266WebServer</a></td>
+<td><a href="../api/index.html#withparameter">Reference to ESP8266WebServer/WebServer</a></td>
 <td>AutoConnect menu not available.<br>To use AutoConnect menu, need <a href="../api/index.html#handlerequest">AutoConnect::handleRequest()</a>.</td>
 <td>AutoConnect menu available.</td>
 </tr>
@@ -750,22 +751,22 @@ or</p>
 </table>
 <ul>
 <li>
-<p><strong>By declaration for the AutoConnect variable with no parameter</strong>: The ESP8266WebServer instance is hosted by AutoConnect automatically then the sketches use <a href="../api/index.html#host"><em>AutoConnect::host</em></a> as API to get it after <a href="../api/index.html#begin"><em>AutoConnect::begin</em></a> performed.</p>
+<p><strong>By declaration for the AutoConnect variable with no parameter</strong>: The ESP8266WebServer/WebServer instance is hosted by AutoConnect automatically then the sketches use <a href="../api/index.html#host"><em>AutoConnect::host</em></a> as API to get it after <a href="../api/index.html#begin"><em>AutoConnect::begin</em></a> performed.</p>
 </li>
 <li>
-<p><strong>By declaration for the AutoConnect variable with the reference of ESP8266WebServer</strong>: AutoConnect will use it. The sketch can use it is too.</p>
+<p><strong>By declaration for the AutoConnect variable with the reference of ESP8266WebServer/WebServer</strong>: AutoConnect will use it. The sketch can use it is too.</p>
 </li>
 <li>
-<p><strong>In use ESP8266WebServer::handleClient()</strong>: AutoConnect menu can be dispatched but not works normally. It is necessary to call <a href="../api/index.html#void-handlerequest"><em>AutoConnect::handleRequest</em></a> after <em>ESP8255WebServer::handleClient</em> invoking.</p>
+<p><strong>In use ESP8266WebServer::handleClient()/WebServer::handleClient()</strong>: AutoConnect menu can be dispatched but not works normally. It is necessary to call <a href="../api/index.html#void-handlerequest"><em>AutoConnect::handleRequest</em></a> after <em>ESP8255WebServer::handleClient</em>/<em>WebServer::handleClient</em> invoking.</p>
 </li>
 <li>
 <p><strong>In use <a href="../api/index.html#void-handleclient">AutoConnect::handleClient()</a></strong>: The handleClient() process and the AutoConnect menu is available without calling <em>ESP8266WebServer::handleClient</em>.</p>
 </li>
 </ul>
 <div class="admonition info">
-<p class="admonition-title">Why AutoConnect::handleRequest is needed when using ESP8266::handleClient</p>
-<p>The AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside <em>ESP8266WebServer::handleClient</em>.<br />
-<a href="../api/index.html#void-handleclient"><em>AutoConnect::handleClient</em></a> is equivalent <em>ESP8266WebServer::handleClient</em> included <a href="../api/index.html#void-handlerequest"><em>AutoConnect::handleRequest</em></a>.</p>
+<p class="admonition-title">Why AutoConnect::handleRequest is needed when using ESP8266WebServer::handleClient/WebServer::handleClient</p>
+<p>The AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside <em>ESP8266WebServer::handleClient</em> and <em>WebServer::handleClient</em>.<br />
+<a href="../api/index.html#void-handleclient"><em>AutoConnect::handleClient</em></a> is equivalent <em>ESP8266WebServer::handleClient</em> and <em>WEbServer::handleClient</em> included <a href="../api/index.html#void-handlerequest"><em>AutoConnect::handleRequest</em></a>.</p>
 </div>
 <div class="footnote">
 <hr />
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 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/changelog/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>Change log - AutoConnect for ESP8266</title>
+        <title>Change log - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -101,7 +101,7 @@
     <input class="md-toggle" data-md-toggle="search" type="checkbox" id="search">
     <label class="md-overlay" data-md-component="overlay" for="drawer"></label>
     
-      <a href="#094-may-5-2018" tabindex="1" class="md-skip">
+      <a href="#095-aug27-2018" tabindex="1" class="md-skip">
         Skip to content
       </a>
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Change log
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -400,6 +400,13 @@
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
       
+        <li class="md-nav__item">
+  <a href="#095-aug27-2018" title="[0.9.5] Aug.27, 2018." class="md-nav__link">
+    [0.9.5] Aug.27, 2018.
+  </a>
+  
+</li>
+      
         <li class="md-nav__item">
   <a href="#094-may-5-2018" title="[0.9.4] May 5, 2018." class="md-nav__link">
     [0.9.4] May 5, 2018.
@@ -469,6 +476,13 @@
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
       
+        <li class="md-nav__item">
+  <a href="#095-aug27-2018" title="[0.9.5] Aug.27, 2018." class="md-nav__link">
+    [0.9.5] Aug.27, 2018.
+  </a>
+  
+</li>
+      
         <li class="md-nav__item">
   <a href="#094-may-5-2018" title="[0.9.4] May 5, 2018." class="md-nav__link">
     [0.9.4] May 5, 2018.
@@ -516,7 +530,12 @@
                 
                   <h1>Change log</h1>
                 
-                <h4 id="094-may-5-2018">[0.9.4] May 5, 2018.<a class="headerlink" href="#094-may-5-2018" title="Permanent link">&para;</a></h4>
+                <h4 id="095-aug27-2018">[0.9.5] Aug.27, 2018.<a class="headerlink" href="#095-aug27-2018" title="Permanent link">&para;</a></h4>
+<ul>
+<li>Supports ESP32.</li>
+<li>Fixed that crash may occur if the number of stored credentials in the EEPROM is smaller than the number of found WiFi networks.</li>
+</ul>
+<h4 id="094-may-5-2018">[0.9.4] May 5, 2018.<a class="headerlink" href="#094-may-5-2018" title="Permanent link">&para;</a></h4>
 <ul>
 <li>Automatically focus passphrase after selecting SSID with Configure New AP.</li>
 <li>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.</li>
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 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/examples/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>Examples - AutoConnect for ESP8266</title>
+        <title>Examples - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Examples
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
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 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/faq/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>FAQ - AutoConnect for ESP8266</title>
+        <title>FAQ - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 FAQ
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
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 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/gettingstarted/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>Getting started - AutoConnect for ESP8266</title>
+        <title>Getting started - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Getting started
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -544,11 +544,11 @@
                 
                 <h2 id="lets-do-the-most-simple-sketch">Let's do the most simple sketch<a class="headerlink" href="#lets-do-the-most-simple-sketch" title="Permanent link">&para;</a></h2>
 <p>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.</p>
-<div class="codehilite"><pre><span></span><span class="cp">#include</span> <span class="cpf">&lt;ESP8266WiFi.h&gt;</span><span class="cp"></span>
-<span class="cp">#include</span> <span class="cpf">&lt;ESP8266WebServer.h&gt;</span><span class="cp"></span>
+<div class="codehilite"><pre><span></span><span class="cp">#include</span> <span class="cpf">&lt;ESP8266WiFi.h&gt;          // Replace with WiFi.h for ESP32</span><span class="cp"></span>
+<span class="cp">#include</span> <span class="cpf">&lt;ESP8266WebServer.h&gt;     // Replace with WebServer.h for ESP32</span><span class="cp"></span>
 <span class="cp">#include</span> <span class="cpf">&lt;AutoConnect.h&gt;</span><span class="cp"></span>
 
-<span class="n">ESP8266WebServer</span> <span class="nf">Server</span><span class="p">;</span>
+<span class="n">ESP8266WebServer</span> <span class="nf">Server</span><span class="p">;</span>          <span class="c1">// Replace with WebServer for ESP32</span>
 <span class="n">AutoConnect</span>      <span class="nf">Portal</span><span class="p">(</span><span class="nf">Server</span><span class="p">);</span>
 
 <span class="kr">void</span> <span class="nf">rootPage</span><span class="p">()</span> <span class="p">{</span>
@@ -572,8 +572,11 @@
 <span class="p">}</span>
 </pre></div>
 
+<div class="admonition note">
+<p>The above code can be applied to ESP8266. To apply to ESP32, replace <code class="codehilite">ESP8266WebServer</code> class with <code class="codehilite">WebServer</code> and include <code class="codehilite">WiFi.h</code> and <code class="codehilite">WebServer.h</code> appropriately.</p>
+</div>
 <h3 id="run-at-first"><i class="fa fa-play-circle"></i> Run at first<a class="headerlink" href="#run-at-first" title="Permanent link">&para;</a></h3>
-<p>After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open <em>Wi-Fi settings</em> from the <em>Settings</em> Apps. You can see the <strong>esp8266ap</strong> in the list of <em>"CHOOSE A NETWORK..."</em>. Then tap the esp8266ap and enter password <strong>12345678</strong>, a something screen pops up automatically as shown below.</p>
+<p>After about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open <em>Wi-Fi settings</em> from the <em>Settings</em> Apps. You can see the <strong>esp8266ap</strong> <sup id="fnref:1"><a class="footnote-ref" href="#fn:1" rel="footnote">1</a></sup> in the list of <em>"CHOOSE A NETWORK..."</em>. Then tap the esp8266ap and enter password <strong>12345678</strong>, a something screen pops up automatically as shown below.</p>
 <p><span style="display:inline-block;width:282px;height:501px;border:1px solid lightgrey;"><img data-gifffer="../images/login_ani.gif" data-gifffer-width="280" style="width:280px;" /></span><img src="../images/arrow_right.svg" style="vertical-align:top;padding-top:120px;width:48px;margin-left:30px;margin-right:30px;" /><img src="../images/stat.png" style="border:1px solid lightgrey;width:280px;" /></span></p>
 <p>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 <strong>hamburger icon</strong> is the control menu of AutoConnect seems at the upper right. By tap the hamburger icon, the control menu appears as the below.</p>
 <h3 id="join-to-the-new-access-point"><i class="fa fa-cog"></i> Join to the new access point<a class="headerlink" href="#join-to-the-new-access-point" title="Permanent link">&para;</a></h3>
@@ -592,6 +595,15 @@ Or, "<strong>RESET</strong>" can be selected. The ESP8266 resets and reboots. Af
     Gifffer();
   }
 </script>
+
+<div class="footnote">
+<hr />
+<ol>
+<li id="fn:1">
+<p>When applied to ESP32, <strong>esp32ap</strong>&#160;<a class="footnote-backref" href="#fnref:1" rev="footnote" title="Jump back to footnote 1 in the text">&#8617;</a></p>
+</li>
+</ol>
+</div>
                 
                   
                 
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 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>AutoConnect for ESP8266</title>
+        <title>AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -101,7 +101,7 @@
     <input class="md-toggle" data-md-toggle="search" type="checkbox" id="search">
     <label class="md-overlay" data-md-component="overlay" for="drawer"></label>
     
-      <a href="#autoconnect-for-esp8266" tabindex="1" class="md-skip">
+      <a href="#autoconnect-for-esp8266esp32" tabindex="1" class="md-skip">
         Skip to content
       </a>
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="./images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 Overview
@@ -249,7 +249,7 @@
         <img src="./images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -654,22 +654,22 @@
               
                 
                 
-                <h1 id="autoconnect-for-esp8266">AutoConnect <small>for ESP8266</small><a class="headerlink" href="#autoconnect-for-esp8266" title="Permanent link">&para;</a></h1>
-<p>An Arduino library for ESP8266 WLAN configuration at run time with web interface.</p>
+                <h1 id="autoconnect-for-esp8266esp32">AutoConnect <small>for ESP8266/ESP32</small><a class="headerlink" href="#autoconnect-for-esp8266esp32" title="Permanent link">&para;</a></h1>
+<p>An Arduino library for ESP8266/ESP32 WLAN configuration at run time with web interface.</p>
 <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
-<p>To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with <em>ESP8266WebServer</em> 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.</p>
+<p>To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with <em>ESP8266WebServer</em> class for ESP8266 or <em>WebServer</em> 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.</p>
 <p><img style="display:inline-block;width:460px;margin-right:30px;" src="./images/ov.png" /><span style="display:inline-block;width:182px;height:322px;border:solid 1px lightgrey;"><img data-gifffer="./images/ov.gif" data-gifffer-width="180" style="width:180px;" /></span></p>
 <h3 id="no-need-pre-coded-ssid-password"><i class="fa fa-arrow-circle-right" aria-hidden="true"></i> No need pre-coded SSID &amp; password<a class="headerlink" href="#no-need-pre-coded-ssid-password" title="Permanent link">&para;</a></h3>
-<p><span class="lead">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 &amp; Password from a smartphone via the web interface at runtime.</span></p>
+<p><span class="lead">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 &amp; Password from a smartphone via the web interface at runtime.</span></p>
 <h3 id="simple-usage"><i class="fa fa-arrow-circle-right" aria-hidden="true"></i> Simple usage<a class="headerlink" href="#simple-usage" title="Permanent link">&para;</a></h3>
 <p><span class="lead">AutoConnect control screen will be displayed automatically for establishing new connections. It aids by the <a href="https://en.wikipedia.org/wiki/Captive_portal">captive portal</a> when vested the connection cannot be detected.<br>By using the <a href="menu/index.html">AutoConnect menu</a>, to manage the connections convenient.</span></p>
 <h3 id="store-the-established-connection"><i class="fa fa-arrow-circle-right" aria-hidden="true"></i> Store the established connection<a class="headerlink" href="#store-the-established-connection" title="Permanent link">&para;</a></h3>
-<p><span class="lead">The connection authentication data as credentials are saved automatically in EEPROM of ESP8266 and You can select the past SSID from the <a href="menu/index.html">AutoConnect menu</a>.</span></p>
+<p><span class="lead">The connection authentication data as credentials are saved automatically in EEPROM of ESP8266/ESP32 and You can select the past SSID from the <a href="menu/index.html">AutoConnect menu</a>.</span></p>
 <h3 id="easy-to-embed-in"><i class="fa fa-arrow-circle-right" aria-hidden="true"></i> Easy to embed in<a class="headerlink" href="#easy-to-embed-in" title="Permanent link">&para;</a></h3>
 <p><span class="lead">AutoConnect can be placed easily in your sketch. It's "<strong>begin</strong>" and "<strong>handleClient</strong>" only.</span></p>
 <h3 id="lives-with-the-your-sketches"><i class="fa fa-arrow-circle-right" aria-hidden="true"></i> Lives with the your sketches<a class="headerlink" href="#lives-with-the-your-sketches" title="Permanent link">&para;</a></h3>
-<p><span class="lead">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.</span></p>
+<p><span class="lead">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.<br>This efficacy can also be applied to ESP32. The corresponding class for ESP32 will be the WebServer.</span></p>
 <h2 id="installation">Installation<a class="headerlink" href="#installation" title="Permanent link">&para;</a></h2>
 <h3 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">&para;</a></h3>
 <h4 id="supported-hardware">Supported hardware<a class="headerlink" href="#supported-hardware" title="Permanent link">&para;</a></h4>
@@ -682,6 +682,13 @@ Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi conne
 <li class="task-list-item"><input type="checkbox" disabled checked/> Olimex MOD-WIFI-ESP8266</li>
 <li class="task-list-item"><input type="checkbox" disabled checked/> SparkFun Thing</li>
 <li class="task-list-item"><input type="checkbox" disabled checked/> SweetPea ESP-210</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> ESP32Dev Board (applying the Espressif's arduino-esp32 core)</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> SparkFun ESP32 Thing</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> WEMOS LOLIN D32</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> Ai-Thinker NodeMCU-32S</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> Heltec WiFi Kit 32</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> M5Stack</li>
+<li class="task-list-item"><input type="checkbox" disabled checked/> And other ESP8266/ESP32 modules supported by the Additional Board Manager URLs of the Arduino-IDE.</li>
 </ul>
 <div class="admonition info">
 <p class="admonition-title">About flash size on the module</p>
@@ -694,15 +701,13 @@ Easy implementing the Web interface constituting the WLAN for ESP8266 WiFi conne
 <p><i class="fa fa-download"></i> <strong>ESP8266 Arduino core</strong></p>
 <p>AutoConnect targets sketches made on the assumption of <a href="https://github.com/esp8266/Arduino">ESP8266 Community's Arduino core</a>. The <a href="https://github.com/esp8266/Arduino/releases/latest">latest release</a> is recommended.<br />
 Install third-party platform using the <em>Boards Manager</em> of Arduino IDE. Package URL is <a href="http://arduino.esp8266.com/stable/package_esp8266com_index.json">http://arduino.esp8266.com/stable/package_esp8266com_index.json</a></p>
+<p><i class="fa fa-download"></i> <strong>ESP32 Arduino core</strong></p>
+<p>Also, to apply AutoConnect to ESP32, the <a href="https://github.com/espressif/arduino-esp32">arduino-esp32 core</a> provided by Espressif is needed. The <a href="https://github.com/espressif/arduino-esp32/releases/latest">latest release</a> is recommended.<br />
+Install third-party platform using the <em>Boards Manager</em> of Arduino IDE. You can add multiple URLs into <em>Additional Board Manager URLs</em> field, separating them with commas. Package URL is <a href="https://dl.espressif.com/dl/package_esp32_index.json">https://dl.espressif.com/dl/package_esp32_index.json</a></p>
 <p><i class="fa fa-download"></i> <strong>Additional necessary library</strong></p>
 <p>The <a href="https://github.com/Hieromon/PageBuilder">PageBuilder</a> library to build HTML for ESP8266WebServer is needed.<br />
-To install the PageBuilder library into your Arduino IDE, you can use the <em>Library Manager</em>. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword '<strong>PageBuilder</strong>' with the topic '<strong>Communication</strong>', then you can see the <em>PageBuilder</em>. The latest version or 1.0.0 later is required.</p>
+To install the PageBuilder library into your Arduino IDE, you can use the <em>Library Manager</em>. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword '<strong>PageBuilder</strong>' with the topic '<strong>Communication</strong>', then you can see the <em>PageBuilder</em>. The latest version is required 1.1.0 later for ESP32.</p>
 <p><img src="./images/lm.png" width="640"/></p>
-<div class="admonition warning">
-<p class="admonition-title">Library Manager of Arduino IDE</p>
-<p>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. <a href="https://github.com/Hieromon/PageBuilder/releases/latest">The PageBuilder release</a> of the Github repository is the latest version. The <a href="https://platformio.org/lib/show/2010/PageBuilder">PlatformIO library</a> has the latest version of 1.0.0.<br />
-In 0.93.0, the PageBuilder class has a compile error about without the 'cancel' method.</p>
-</div>
 <h3 id="install-the-autoconnect">Install the AutoConnect<a class="headerlink" href="#install-the-autoconnect" title="Permanent link">&para;</a></h3>
 <p>Clone or download from the <a href="https://github.com/Hieromon/AutoConnect">AutoConnect GitHub repository</a>.</p>
 <p><img src="./images/gitrepo.png" width="640"/></p>
@@ -710,7 +715,7 @@ In 0.93.0, the PageBuilder class has a compile error about without the 'cancel'
 <p><img src="./images/ins_lib.png" /></p>
 <div class="admonition info">
 <p class="admonition-title">Supported by Library manager.</p>
-<p>AutoConnect was added to the Arduino IDE library manager as of March 17, 2018. It can be used with the PlatformIO library also.</p>
+<p>AutoConnect was added to the Arduino IDE library manager. It can be used with the PlatformIO library also.</p>
 </div>
 <script>
   window.onload = function() {
diff --git a/docs/license/index.html b/docs/license/index.html
index c1b1f7c..cef84c1 100644
--- a/docs/license/index.html
+++ b/docs/license/index.html
@@ -10,7 +10,7 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/license/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>License - AutoConnect for ESP8266</title>
+        <title>License - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -106,7 +106,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -120,7 +120,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 License
@@ -245,7 +245,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
diff --git a/docs/menu/index.html b/docs/menu/index.html
index 44189c6..b9c2de0 100644
--- a/docs/menu/index.html
+++ b/docs/menu/index.html
@@ -10,7 +10,7 @@
       <meta name="viewport" content="width=device-width,initial-scale=1">
       <meta http-equiv="x-ua-compatible" content="ie=edge">
       
-        <meta name="description" content="ESP8266 WLAN configuration at run time with web interface">
+        <meta name="description" content="ESP8266/ESP32 WLAN configuration at run time with web interface">
       
       
         <link rel="canonical" href="https://Hieromon.github.io/AutoConnect/menu/index.html">
@@ -42,7 +42,7 @@
     
     
       
-        <title>AutoConnect menu - AutoConnect for ESP8266</title>
+        <title>AutoConnect menu - AutoConnect for ESP8266/ESP32</title>
       
     
     
@@ -110,7 +110,7 @@
   <nav class="md-header-nav md-grid">
     <div class="md-flex">
       <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266" class="md-header-nav__button md-logo">
+        <a href="https://Hieromon.github.io/AutoConnect/" title="AutoConnect for ESP8266/ESP32" class="md-header-nav__button md-logo">
           
             <img src="../images/arduino-logo.svg" width="24" height="24">
           
@@ -124,7 +124,7 @@
           
             
               <span class="md-header-nav__topic">
-                AutoConnect for ESP8266
+                AutoConnect for ESP8266/ESP32
               </span>
               <span class="md-header-nav__topic">
                 AutoConnect menu
@@ -249,7 +249,7 @@
         <img src="../images/arduino-logo.svg" width="48" height="48">
       
     </span>
-    AutoConnect for ESP8266
+    AutoConnect for ESP8266/ESP32
   </label>
   
     <div class="md-nav__source">
@@ -549,7 +549,7 @@
 <p>The AutoConnect menu is developed using the <a href="https://github.com/balzss/luxbar">LuxBar</a> which is licensed under the MIT License. See the <a href="../license/index.html">License</a>.</p>
 </div>
 <h2 id="where-the-from"><i class="fa fa-external-link"></i> Where the from<a class="headerlink" href="#where-the-from" title="Permanent link">&para;</a></h2>
-<p>The AutoConnect menu appears when you access the <strong>AutoConnect root path</strong>. It is assigned "<strong>/_ac</strong>" located on ESP8266 <em>local IP address</em> by default. This location can be changed in the sketch. The following screen will appear at access to <code class="codehilite">http://{localIP}/_ac</code> as the root path. This is the statistics of the current WiFi connection. You can access the menu from the here, to invoke it tap <i class="fa fa-bars"></i> at right on top. (e.g. <code class="codehilite">http://192.168.244.1/_ac</code> for SoftAP mode.)</p>
+<p>The AutoConnect menu appears when you access the <strong>AutoConnect root path</strong>. It is assigned "<strong>/_ac</strong>" located on ESP8266/ESP32 <em>local IP address</em> by default. This location can be changed in the sketch. The following screen will appear at access to <code class="codehilite">http://{localIP}/_ac</code> as the root path. This is the statistics of the current WiFi connection. You can access the menu from the here, to invoke it tap <i class="fa fa-bars"></i> at right on top. (e.g. <code class="codehilite">http://192.168.244.1/_ac</code> for SoftAP mode.)</p>
 <p><img src="../images/ac.png" style="border-style:solid;border-width:1px;border-color:lightgrey;width:280px;" /></p>
 <div class="admonition note">
 <p class="admonition-title">What's local IP?</p>
@@ -561,7 +561,7 @@
 <li><strong>Configure new AP</strong>: Configure SSID and Password for new access point.</li>
 <li><strong>Open SSIDs</strong>: Opens the past SSID which has been established connection from EEPROM.</li>
 <li><strong>Disconnect</strong>: Disconnects current connection.</li>
-<li><strong>Reset...</strong>: Rest the ESP8266 module.</li>
+<li><strong>Reset...</strong>: Rest the ESP8266/ESP32 module.</li>
 <li><strong>HOME</strong>: Return to user home page.</li>
 </ul>
 <p><img src="../images/menu.png" style="width:280px;" /></p>
@@ -570,17 +570,17 @@
 Enter SSID and Passphrase and tap "<strong>apply</strong>" to starts a connection. </p>
 <p><img src="../images/newap.png" style="border-style:solid;border-width:1px;border-color:lightgrey;width:280px;" /></p>
 <h2 id="open-ssids"><i class="fa fa-bars"></i> Open SSIDs<a class="headerlink" href="#open-ssids" title="Permanent link">&para;</a></h2>
-<p>Once it was established connection, its SSID and Password will be stored to the EEPROM of ESP8266 automatically. The <strong>Open SSIDs</strong> menu reads the saved SSID credentials from the EEPROM. The stored credential data are listed by the SSID as shown below. Its label is a clickable button. Tap the SSID button, starts connection it.</p>
+<p>Once it was established connection, its SSID and Password will be stored to the EEPROM of ESP8266/ESP32 automatically. The <strong>Open SSIDs</strong> menu reads the saved SSID credentials from the EEPROM. The stored credential data are listed by the SSID as shown below. Its label is a clickable button. Tap the SSID button, starts connection it.</p>
 <p><img src="../images/open.png" style="border-style:solid;border-width:1px;border-color:lightgrey;width:280px;" /></p>
 <h2 id="disconnect"><i class="fa fa-bars"></i> Disconnect<a class="headerlink" href="#disconnect" title="Permanent link">&para;</a></h2>
-<p>Disconnect ESP8266 from the current connection. It can also reset the ESP8266 automatically after disconnection by instructing with using <a href="../api/index.html#autoreset">API</a> in the sketch.</p>
+<p>Disconnect ESP8266/ESP32 from the current connection. It can also reset the ESP8266/ESP32 automatically after disconnection by instructing with using <a href="../api/index.html#autoreset">API</a> in the sketch.</p>
 <p>After tapping "Disconnect", you will not be able to reach the AutoConnect menu. Once disconnected, you will need to set the SSID again for connecting the WLAN. </p>
 <h2 id="reset"><i class="fa fa-bars"></i> Reset...<a class="headerlink" href="#reset" title="Permanent link">&para;</a></h2>
-<p>Reset the ESP8266, it will start rebooting. After rebooting complete, the ESP8266 begins establishing the previous connection with WIFI_STA mode, and <em>esp8266ap</em> of an access point will disappear from WLAN.</p>
+<p>Reset the ESP8266/ESP32, it will start rebooting. After rebooting complete, the ESP8266/ESP32 module begins establishing the previous connection with WIFI_STA mode, and <em>esp8266ap</em> or <em>esp32ap</em> of an access point will disappear from WLAN.</p>
 <p><img src="../images/resetting.png" style="width:280px;" /></p>
 <div class="admonition warning">
-<p class="admonition-title">Not every module will be rebooted normally</p>
-<p>The Reset menu is using the <strong>ESP.reset()</strong> function. This is an almost hardware reset. In order to resume the sketch normally, the <a href="https://github.com/esp8266/esp8266-wiki/wiki/Boot-Process#esp-boot-modes">state of GPIO0</a> is important. Since this depends on the circuit implementation for each module, not every module will be rebooted normally. See also <a href="../faq/index.html#hang-up-after-reset">FAQ</a>.</p>
+<p class="admonition-title">Not every ESP8266 module will be rebooted normally</p>
+<p>The Reset menu is using the <strong>ESP.reset()</strong> function for ESP8266. This is an almost hardware reset. In order to resume the sketch normally, the <a href="https://github.com/esp8266/esp8266-wiki/wiki/Boot-Process#esp-boot-modes">state of GPIO0</a> is important. Since this depends on the circuit implementation for each module, not every module will be rebooted normally. See also <a href="../faq/index.html#hang-up-after-reset">FAQ</a>.</p>
 </div>
                 
                   
diff --git a/docs/search/search_index.json b/docs/search/search_index.json
index a655b72..a3ee598 100644
--- a/docs/search/search_index.json
+++ b/docs/search/search_index.json
@@ -2,22 +2,22 @@
     "docs": [
         {
             "location": "/index.html",
-            "text": "AutoConnect \nfor ESP8266\n\u00b6\n\n\nAn Arduino library for ESP8266 WLAN configuration at run time with web interface.\n\n\nOverview\n\u00b6\n\n\nTo the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with \nESP8266WebServer\n class.\nEasy 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.\n\n\n\n\n No need pre-coded SSID & password\n\u00b6\n\n\nIt 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.\n\n\n Simple usage\n\u00b6\n\n\nAutoConnect control screen will be displayed automatically for establishing new connections. It aids by the \ncaptive portal\n when vested the connection cannot be detected.\nBy using the \nAutoConnect menu\n, to manage the connections convenient.\n\n\n Store the established connection\n\u00b6\n\n\nThe connection authentication data as credentials are saved automatically in EEPROM of ESP8266 and You can select the past SSID from the \nAutoConnect menu\n.\n\n\n Easy to embed in\n\u00b6\n\n\nAutoConnect can be placed easily in your sketch. It's \"\nbegin\n\" and \"\nhandleClient\n\" only.\n\n\n Lives with the your sketches\n\u00b6\n\n\nThe 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.\n\n\nInstallation\n\u00b6\n\n\nRequirements\n\u00b6\n\n\nSupported hardware\n\u00b6\n\n\n\n\n Generic ESP8266 modules (applying the ESP8266 Community's Arduino core)\n\n\n Adafruit HUZZAH ESP8266 (ESP-12)\n\n\n ESP-WROOM-02\n\n\n Heltec WiFi Kit 8\n\n\n NodeMCU 0.9 (ESP-12) / NodeMCU 1.0 (ESP-12E)\n\n\n Olimex MOD-WIFI-ESP8266\n\n\n SparkFun Thing\n\n\n SweetPea ESP-210\n\n\n\n\n\n\nAbout flash size on the module\n\n\nThe AutoConnect sketch size is relatively large. Large flash capacity is necessary. 512Kbyte (4Mbits) flash inclusion module such as ESP-01 is not recommended.\n\n\n\n\nRequired libraries\n\u00b6\n\n\nAutoConnect requires the following environment and libraries.\n\n\n \nArduino IDE\n\n\nThe current upstream at the 1.8 level or later is needed. Please install from the \nofficial Arduino IDE download page\n. This step is not required if you already have a modern version.\n\n\n \nESP8266 Arduino core\n\n\nAutoConnect targets sketches made on the assumption of \nESP8266 Community's Arduino core\n. The \nlatest release\n is recommended.\n\nInstall third-party platform using the \nBoards Manager\n of Arduino IDE. Package URL is \nhttp://arduino.esp8266.com/stable/package_esp8266com_index.json\n\n\n \nAdditional necessary library\n\n\nThe \nPageBuilder\n library to build HTML for ESP8266WebServer is needed.\n\nTo install the PageBuilder library into your Arduino IDE, you can use the \nLibrary Manager\n. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword '\nPageBuilder\n' with the topic '\nCommunication\n', then you can see the \nPageBuilder\n. The latest version or 1.0.0 later is required.\n\n\n\n\n\n\nLibrary Manager of Arduino IDE\n\n\nThe 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. \nThe PageBuilder release\n of the Github repository is the latest version. The \nPlatformIO library\n has the latest version of 1.0.0.\n\nIn 0.93.0, the PageBuilder class has a compile error about without the 'cancel' method.\n\n\n\n\nInstall the AutoConnect\n\u00b6\n\n\nClone or download from the \nAutoConnect GitHub repository\n.\n\n\n\n\nWhen you select Download, you can import it to Arduino IDE immediately. After downloaded, the AutoConnect-master.zip file will be saved in your download folder. Then in the Arduino IDE, navigate to \n\"Sketch > Include Library\"\n. At the top of the drop down list, select the option to \n\"Add .ZIP Library...\"\n. Details for \nArduino official page\n.\n\n\n\n\n\n\nSupported by Library manager.\n\n\nAutoConnect was added to the Arduino IDE library manager as of March 17, 2018. It can be used with the PlatformIO library also.\n\n\n\n\n\n  window.onload = function() {\n    Gifffer();\n  }",
+            "text": "AutoConnect \nfor ESP8266/ESP32\n\u00b6\n\n\nAn Arduino library for ESP8266/ESP32 WLAN configuration at run time with web interface.\n\n\nOverview\n\u00b6\n\n\nTo the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with \nESP8266WebServer\n class for ESP8266 or \nWebServer\n class for ESP32.\nEasy 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.\n\n\n\n\n No need pre-coded SSID & password\n\u00b6\n\n\nIt 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.\n\n\n Simple usage\n\u00b6\n\n\nAutoConnect control screen will be displayed automatically for establishing new connections. It aids by the \ncaptive portal\n when vested the connection cannot be detected.\nBy using the \nAutoConnect menu\n, to manage the connections convenient.\n\n\n Store the established connection\n\u00b6\n\n\nThe connection authentication data as credentials are saved automatically in EEPROM of ESP8266/ESP32 and You can select the past SSID from the \nAutoConnect menu\n.\n\n\n Easy to embed in\n\u00b6\n\n\nAutoConnect can be placed easily in your sketch. It's \"\nbegin\n\" and \"\nhandleClient\n\" only.\n\n\n Lives with the your sketches\n\u00b6\n\n\nThe 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.\nThis efficacy can also be applied to ESP32. The corresponding class for ESP32 will be the WebServer.\n\n\nInstallation\n\u00b6\n\n\nRequirements\n\u00b6\n\n\nSupported hardware\n\u00b6\n\n\n\n\n Generic ESP8266 modules (applying the ESP8266 Community's Arduino core)\n\n\n Adafruit HUZZAH ESP8266 (ESP-12)\n\n\n ESP-WROOM-02\n\n\n Heltec WiFi Kit 8\n\n\n NodeMCU 0.9 (ESP-12) / NodeMCU 1.0 (ESP-12E)\n\n\n Olimex MOD-WIFI-ESP8266\n\n\n SparkFun Thing\n\n\n SweetPea ESP-210\n\n\n ESP32Dev Board (applying the Espressif's arduino-esp32 core)\n\n\n SparkFun ESP32 Thing\n\n\n WEMOS LOLIN D32\n\n\n Ai-Thinker NodeMCU-32S\n\n\n Heltec WiFi Kit 32\n\n\n M5Stack\n\n\n And other ESP8266/ESP32 modules supported by the Additional Board Manager URLs of the Arduino-IDE.\n\n\n\n\n\n\nAbout flash size on the module\n\n\nThe AutoConnect sketch size is relatively large. Large flash capacity is necessary. 512Kbyte (4Mbits) flash inclusion module such as ESP-01 is not recommended.\n\n\n\n\nRequired libraries\n\u00b6\n\n\nAutoConnect requires the following environment and libraries.\n\n\n \nArduino IDE\n\n\nThe current upstream at the 1.8 level or later is needed. Please install from the \nofficial Arduino IDE download page\n. This step is not required if you already have a modern version.\n\n\n \nESP8266 Arduino core\n\n\nAutoConnect targets sketches made on the assumption of \nESP8266 Community's Arduino core\n. The \nlatest release\n is recommended.\n\nInstall third-party platform using the \nBoards Manager\n of Arduino IDE. Package URL is \nhttp://arduino.esp8266.com/stable/package_esp8266com_index.json\n\n\n \nESP32 Arduino core\n\n\nAlso, to apply AutoConnect to ESP32, the \narduino-esp32 core\n provided by Espressif is needed. The \nlatest release\n is recommended.\n\nInstall third-party platform using the \nBoards Manager\n of Arduino IDE. You can add multiple URLs into \nAdditional Board Manager URLs\n field, separating them with commas. Package URL is \nhttps://dl.espressif.com/dl/package_esp32_index.json\n\n\n \nAdditional necessary library\n\n\nThe \nPageBuilder\n library to build HTML for ESP8266WebServer is needed.\n\nTo install the PageBuilder library into your Arduino IDE, you can use the \nLibrary Manager\n. Select the board of ESP8266 series in the Arduino IDE, open the library manager and search keyword '\nPageBuilder\n' with the topic '\nCommunication\n', then you can see the \nPageBuilder\n. The latest version is required 1.1.0 later for ESP32.\n\n\n\n\nInstall the AutoConnect\n\u00b6\n\n\nClone or download from the \nAutoConnect GitHub repository\n.\n\n\n\n\nWhen you select Download, you can import it to Arduino IDE immediately. After downloaded, the AutoConnect-master.zip file will be saved in your download folder. Then in the Arduino IDE, navigate to \n\"Sketch > Include Library\"\n. At the top of the drop down list, select the option to \n\"Add .ZIP Library...\"\n. Details for \nArduino official page\n.\n\n\n\n\n\n\nSupported by Library manager.\n\n\nAutoConnect was added to the Arduino IDE library manager. It can be used with the PlatformIO library also.\n\n\n\n\n\n  window.onload = function() {\n    Gifffer();\n  }",
             "title": "Overview"
         },
         {
-            "location": "/index.html#autoconnect-for-esp8266",
-            "text": "An Arduino library for ESP8266 WLAN configuration at run time with web interface.",
-            "title": "AutoConnect for ESP8266"
+            "location": "/index.html#autoconnect-for-esp8266esp32",
+            "text": "An Arduino library for ESP8266/ESP32 WLAN configuration at run time with web interface.",
+            "title": "AutoConnect for ESP8266/ESP32"
         },
         {
             "location": "/index.html#overview",
-            "text": "To the dynamic configuration for joining to WLAN with SSID and PSK accordingly. It an Arduino library united with  ESP8266WebServer  class.\nEasy 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.",
+            "text": "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.\nEasy 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.",
             "title": "Overview"
         },
         {
             "location": "/index.html#no-need-pre-coded-ssid-password",
-            "text": "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.",
+            "text": "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.",
             "title": " No need pre-coded SSID &amp; password"
         },
         {
@@ -27,7 +27,7 @@
         },
         {
             "location": "/index.html#store-the-established-connection",
-            "text": "The connection authentication data as credentials are saved automatically in EEPROM of ESP8266 and You can select the past SSID from the  AutoConnect menu .",
+            "text": "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 .",
             "title": " Store the established connection"
         },
         {
@@ -37,7 +37,7 @@
         },
         {
             "location": "/index.html#lives-with-the-your-sketches",
-            "text": "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.",
+            "text": "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.",
             "title": " Lives with the your sketches"
         },
         {
@@ -52,32 +52,32 @@
         },
         {
             "location": "/index.html#supported-hardware",
-            "text": "Generic ESP8266 modules (applying the ESP8266 Community's Arduino core)   Adafruit HUZZAH ESP8266 (ESP-12)   ESP-WROOM-02   Heltec WiFi Kit 8   NodeMCU 0.9 (ESP-12) / NodeMCU 1.0 (ESP-12E)   Olimex MOD-WIFI-ESP8266   SparkFun Thing   SweetPea ESP-210    About flash size on the module  The AutoConnect sketch size is relatively large. Large flash capacity is necessary. 512Kbyte (4Mbits) flash inclusion module such as ESP-01 is not recommended.",
+            "text": "Generic ESP8266 modules (applying the ESP8266 Community's Arduino core)   Adafruit HUZZAH ESP8266 (ESP-12)   ESP-WROOM-02   Heltec WiFi Kit 8   NodeMCU 0.9 (ESP-12) / NodeMCU 1.0 (ESP-12E)   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  The AutoConnect sketch size is relatively large. Large flash capacity is necessary. 512Kbyte (4Mbits) flash inclusion module such as ESP-01 is not recommended.",
             "title": "Supported hardware"
         },
         {
             "location": "/index.html#required-libraries",
-            "text": "AutoConnect requires the following environment and libraries.    Arduino IDE  The current upstream at the 1.8 level or later is needed. Please install from the  official Arduino IDE download page . This step is not required if you already have a modern version.    ESP8266 Arduino core  AutoConnect targets sketches made on the assumption of  ESP8266 Community's Arduino core . The  latest release  is recommended. \nInstall third-party platform using the  Boards Manager  of Arduino IDE. Package URL is  http://arduino.esp8266.com/stable/package_esp8266com_index.json    Additional necessary library  The  PageBuilder  library to build HTML for ESP8266WebServer is needed. \nTo 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. \nIn 0.93.0, the PageBuilder class has a compile error about without the 'cancel' method.",
+            "text": "AutoConnect requires the following environment and libraries.    Arduino IDE  The current upstream at the 1.8 level or later is needed. Please install from the  official Arduino IDE download page . This step is not required if you already have a modern version.    ESP8266 Arduino core  AutoConnect targets sketches made on the assumption of  ESP8266 Community's Arduino core . The  latest release  is recommended. \nInstall 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. \nInstall 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. \nTo 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.",
             "title": "Required libraries"
         },
         {
             "location": "/index.html#install-the-autoconnect",
-            "text": "Clone or download from the  AutoConnect GitHub repository .   When you select Download, you can import it to Arduino IDE immediately. After downloaded, the AutoConnect-master.zip file will be saved in your download folder. Then in the Arduino IDE, navigate to  \"Sketch > Include Library\" . At the top of the drop down list, select the option to  \"Add .ZIP Library...\" . Details for  Arduino official page .    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.   \n  window.onload = function() {\n    Gifffer();\n  }",
+            "text": "Clone or download from the  AutoConnect GitHub repository .   When you select Download, you can import it to Arduino IDE immediately. After downloaded, the AutoConnect-master.zip file will be saved in your download folder. Then in the Arduino IDE, navigate to  \"Sketch > Include Library\" . At the top of the drop down list, select the option to  \"Add .ZIP Library...\" . Details for  Arduino official page .    Supported by Library manager.  AutoConnect was added to the Arduino IDE library manager. It can be used with the PlatformIO library also.   \n  window.onload = function() {\n    Gifffer();\n  }",
             "title": "Install the AutoConnect"
         },
         {
             "location": "/gettingstarted/index.html",
-            "text": "Let's do the most simple sketch\n\u00b6\n\n\nOpen the Arduino IDE, write the following sketch and upload it. The feature of this sketch is that the SSID and Password are not coded.\n\n\n#include\n \n<ESP8266WiFi.h>\n\n\n#include\n \n<ESP8266WebServer.h>\n\n\n#include\n \n<AutoConnect.h>\n\n\n\nESP8266WebServer\n \nServer\n;\n\n\nAutoConnect\n      \nPortal\n(\nServer\n);\n\n\n\nvoid\n \nrootPage\n()\n \n{\n\n  \nchar\n \ncontent\n[]\n \n=\n \n\"Hello, world\"\n;\n\n  \nServer\n.\nsend\n(\n200\n,\n \n\"text/plain\"\n,\n \ncontent\n);\n\n\n}\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \ndelay\n(\n1000\n);\n\n  \nSerial\n.\nbegin\n(\n115200\n);\n\n  \nSerial\n.\nprintln\n();\n\n\n  \nServer\n.\non\n(\n\"/\"\n,\n \nrootPage\n);\n\n  \nif\n \n(\nPortal\n.\nbegin\n())\n \n{\n\n    \nSerial\n.\nprintln\n(\n\"WiFi connected: \"\n \n+\n \nWiFi\n.\nlocalIP\n().\ntoString\n());\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n    \nPortal\n.\nhandleClient\n();\n\n\n}\n\n\n\n\n\n Run at first\n\u00b6\n\n\nAfter about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open \nWi-Fi settings\n from the \nSettings\n Apps. You can see the \nesp8266ap\n in the list of \n\"CHOOSE A NETWORK...\"\n. Then tap the esp8266ap and enter password \n12345678\n, a something screen pops up automatically as shown below.\n\n\n\n\nThis 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 \nhamburger icon\n is the control menu of AutoConnect seems at the upper right. By tap the hamburger icon, the control menu appears as the below.\n\n\n Join to the new access point\n\u00b6\n\n\nHere, tap \n\"Configure new AP\"\n to connect the new access point then the SSID configuration screen would be shown. Enter the \nSSID\n and \nPassphrase\n and tap \napply\n to start connecting the access point.\n\n\n\n\n Connection establishment\n\u00b6\n\n\nAfter connection established, the current status screen will appear. It is already connected to WLAN with WiFi mode as WIFI_AP_STA and the IP connection status is displayed there including the SSID. Then at this screen, you have two options for the next step.\n\n\nFor one, continues execution of the sketch while keeping this connection. You can access ESP8266 via browser through the established IP address after cancel to \"\nLog in\n\" by upper right on the screen.\n\nOr, \"\nRESET\n\" can be selected. The ESP8266 resets and reboots. After that, immediately before the connection will be restored automatically with WIFI_STA mode.\n\n\n\n\n Run for usually\n\u00b6\n\n\nThe IP address of ESP8266 would be displayed on the serial monitor after connection restored. Please access its address from the browser. The \"Hello, world\" page will respond. It's the page that was handled by in the sketch with \"\non\n\" function of \nESP8266WebServer\n.\n\n\n\n\n\n  window.onload = function() {\n    Gifffer();\n  }",
+            "text": "Let's do the most simple sketch\n\u00b6\n\n\nOpen the Arduino IDE, write the following sketch and upload it. The feature of this sketch is that the SSID and Password are not coded.\n\n\n#include\n \n<ESP8266WiFi.h>          // Replace with WiFi.h for ESP32\n\n\n#include\n \n<ESP8266WebServer.h>     // Replace with WebServer.h for ESP32\n\n\n#include\n \n<AutoConnect.h>\n\n\n\nESP8266WebServer\n \nServer\n;\n          \n// Replace with WebServer for ESP32\n\n\nAutoConnect\n      \nPortal\n(\nServer\n);\n\n\n\nvoid\n \nrootPage\n()\n \n{\n\n  \nchar\n \ncontent\n[]\n \n=\n \n\"Hello, world\"\n;\n\n  \nServer\n.\nsend\n(\n200\n,\n \n\"text/plain\"\n,\n \ncontent\n);\n\n\n}\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \ndelay\n(\n1000\n);\n\n  \nSerial\n.\nbegin\n(\n115200\n);\n\n  \nSerial\n.\nprintln\n();\n\n\n  \nServer\n.\non\n(\n\"/\"\n,\n \nrootPage\n);\n\n  \nif\n \n(\nPortal\n.\nbegin\n())\n \n{\n\n    \nSerial\n.\nprintln\n(\n\"WiFi connected: \"\n \n+\n \nWiFi\n.\nlocalIP\n().\ntoString\n());\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n    \nPortal\n.\nhandleClient\n();\n\n\n}\n\n\n\n\n\n\n\nThe above code can be applied to ESP8266. To apply to ESP32, replace \nESP8266WebServer\n class with \nWebServer\n and include \nWiFi.h\n and \nWebServer.h\n appropriately.\n\n\n\n\n Run at first\n\u00b6\n\n\nAfter about 30 seconds, if the ESP8266 cannot connect to nearby Wi-Fi spot, you pull out your smartphone and open \nWi-Fi settings\n from the \nSettings\n Apps. You can see the \nesp8266ap\n \n1\n in the list of \n\"CHOOSE A NETWORK...\"\n. Then tap the esp8266ap and enter password \n12345678\n, a something screen pops up automatically as shown below.\n\n\n\n\nThis 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 \nhamburger icon\n is the control menu of AutoConnect seems at the upper right. By tap the hamburger icon, the control menu appears as the below.\n\n\n Join to the new access point\n\u00b6\n\n\nHere, tap \n\"Configure new AP\"\n to connect the new access point then the SSID configuration screen would be shown. Enter the \nSSID\n and \nPassphrase\n and tap \napply\n to start connecting the access point.\n\n\n\n\n Connection establishment\n\u00b6\n\n\nAfter connection established, the current status screen will appear. It is already connected to WLAN with WiFi mode as WIFI_AP_STA and the IP connection status is displayed there including the SSID. Then at this screen, you have two options for the next step.\n\n\nFor one, continues execution of the sketch while keeping this connection. You can access ESP8266 via browser through the established IP address after cancel to \"\nLog in\n\" by upper right on the screen.\n\nOr, \"\nRESET\n\" can be selected. The ESP8266 resets and reboots. After that, immediately before the connection will be restored automatically with WIFI_STA mode.\n\n\n\n\n Run for usually\n\u00b6\n\n\nThe IP address of ESP8266 would be displayed on the serial monitor after connection restored. Please access its address from the browser. The \"Hello, world\" page will respond. It's the page that was handled by in the sketch with \"\non\n\" function of \nESP8266WebServer\n.\n\n\n\n\n\n  window.onload = function() {\n    Gifffer();\n  }\n\n\n\n\n\n\n\n\n\n\n\n\nWhen applied to ESP32, \nesp32ap\n\u00a0\n\u21a9",
             "title": "Getting started"
         },
         {
             "location": "/gettingstarted/index.html#lets-do-the-most-simple-sketch",
-            "text": "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   <AutoConnect.h>  ESP8266WebServer   Server ;  AutoConnect        Portal ( Server );  void   rootPage ()   { \n   char   content []   =   \"Hello, world\" ; \n   Server . send ( 200 ,   \"text/plain\" ,   content );  }  void   setup ()   { \n   delay ( 1000 ); \n   Serial . begin ( 115200 ); \n   Serial . println (); \n\n   Server . on ( \"/\" ,   rootPage ); \n   if   ( Portal . begin ())   { \n     Serial . println ( \"WiFi connected: \"   +   WiFi . localIP (). toString ()); \n   }  }  void   loop ()   { \n     Portal . handleClient ();  }",
+            "text": "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>          // Replace with WiFi.h for ESP32  #include   <ESP8266WebServer.h>     // Replace with WebServer.h for ESP32  #include   <AutoConnect.h>  ESP8266WebServer   Server ;            // Replace with WebServer for ESP32  AutoConnect        Portal ( Server );  void   rootPage ()   { \n   char   content []   =   \"Hello, world\" ; \n   Server . send ( 200 ,   \"text/plain\" ,   content );  }  void   setup ()   { \n   delay ( 1000 ); \n   Serial . begin ( 115200 ); \n   Serial . println (); \n\n   Server . on ( \"/\" ,   rootPage ); \n   if   ( Portal . begin ())   { \n     Serial . println ( \"WiFi connected: \"   +   WiFi . localIP (). toString ()); \n   }  }  void   loop ()   { \n     Portal . handleClient ();  }    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.",
             "title": "Let's do the most simple sketch"
         },
         {
             "location": "/gettingstarted/index.html#run-at-first",
-            "text": "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.   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.",
+            "text": "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.",
             "title": " Run at first"
         },
         {
@@ -92,22 +92,22 @@
         },
         {
             "location": "/gettingstarted/index.html#run-for-usually",
-            "text": "The IP address of ESP8266 would be displayed on the serial monitor after connection restored. Please access its address from the browser. The \"Hello, world\" page will respond. It's the page that was handled by in the sketch with \" on \" function of  ESP8266WebServer .   \n  window.onload = function() {\n    Gifffer();\n  }",
+            "text": "The IP address of ESP8266 would be displayed on the serial monitor after connection restored. Please access its address from the browser. The \"Hello, world\" page will respond. It's the page that was handled by in the sketch with \" on \" function of  ESP8266WebServer .   \n  window.onload = function() {\n    Gifffer();\n  }      When applied to ESP32,  esp32ap \u00a0 \u21a9",
             "title": " Run for usually"
         },
         {
             "location": "/menu/index.html",
-            "text": "Luxbar\n\n\nThe AutoConnect menu is developed using the \nLuxBar\n which is licensed under the MIT License. See the \nLicense\n.\n\n\n\n\n Where the from\n\u00b6\n\n\nThe AutoConnect menu appears when you access the \nAutoConnect root path\n. It is assigned \"\n/_ac\n\" located on ESP8266 \nlocal IP address\n by default. This location can be changed in the sketch. The following screen will appear at access to \nhttp://{localIP}/_ac\n as the root path. This is the statistics of the current WiFi connection. You can access the menu from the here, to invoke it tap \n at right on top. (e.g. \nhttp://192.168.244.1/_ac\n for SoftAP mode.)\n\n\n\n\n\n\nWhat's local IP?\n\n\nA local IP means Local IP at connection established or SoftAP's IP.\n\n\n\n\n Right on top\n\u00b6\n\n\nCurrently, AutoConnect supports four menus. Undermost menu as \"HOME\" returns to the home path of its sketch.\n\n\n\n\nConfigure new AP\n: Configure SSID and Password for new access point.\n\n\nOpen SSIDs\n: Opens the past SSID which has been established connection from EEPROM.\n\n\nDisconnect\n: Disconnects current connection.\n\n\nReset...\n: Rest the ESP8266 module.\n\n\nHOME\n: Return to user home page.\n\n\n\n\n\n\n Configure new AP\n\u00b6\n\n\nScan all available access point and display it. Strength and security of the detected AP are marked. The \n is indicated for the SSID that needs a security key. \"\nHidden:\n\" means the number of hidden SSIDs discovered.\n\nEnter SSID and Passphrase and tap \"\napply\n\" to starts a connection. \n\n\n\n\n Open SSIDs\n\u00b6\n\n\nOnce it was established connection, its SSID and Password will be stored to the EEPROM of ESP8266 automatically. The \nOpen SSIDs\n menu reads the saved SSID credentials from the EEPROM. The stored credential data are listed by the SSID as shown below. Its label is a clickable button. Tap the SSID button, starts connection it.\n\n\n\n\n Disconnect\n\u00b6\n\n\nDisconnect ESP8266 from the current connection. It can also reset the ESP8266 automatically after disconnection by instructing with using \nAPI\n in the sketch.\n\n\nAfter tapping \"Disconnect\", you will not be able to reach the AutoConnect menu. Once disconnected, you will need to set the SSID again for connecting the WLAN. \n\n\n Reset...\n\u00b6\n\n\nReset the ESP8266, it will start rebooting. After rebooting complete, the ESP8266 begins establishing the previous connection with WIFI_STA mode, and \nesp8266ap\n of an access point will disappear from WLAN.\n\n\n\n\n\n\nNot every module will be rebooted normally\n\n\nThe Reset menu is using the \nESP.reset()\n function. This is an almost hardware reset. In order to resume the sketch normally, the \nstate of GPIO0\n is important. Since this depends on the circuit implementation for each module, not every module will be rebooted normally. See also \nFAQ\n.",
+            "text": "Luxbar\n\n\nThe AutoConnect menu is developed using the \nLuxBar\n which is licensed under the MIT License. See the \nLicense\n.\n\n\n\n\n Where the from\n\u00b6\n\n\nThe AutoConnect menu appears when you access the \nAutoConnect root path\n. It is assigned \"\n/_ac\n\" located on ESP8266/ESP32 \nlocal IP address\n by default. This location can be changed in the sketch. The following screen will appear at access to \nhttp://{localIP}/_ac\n as the root path. This is the statistics of the current WiFi connection. You can access the menu from the here, to invoke it tap \n at right on top. (e.g. \nhttp://192.168.244.1/_ac\n for SoftAP mode.)\n\n\n\n\n\n\nWhat's local IP?\n\n\nA local IP means Local IP at connection established or SoftAP's IP.\n\n\n\n\n Right on top\n\u00b6\n\n\nCurrently, AutoConnect supports four menus. Undermost menu as \"HOME\" returns to the home path of its sketch.\n\n\n\n\nConfigure new AP\n: Configure SSID and Password for new access point.\n\n\nOpen SSIDs\n: Opens the past SSID which has been established connection from EEPROM.\n\n\nDisconnect\n: Disconnects current connection.\n\n\nReset...\n: Rest the ESP8266/ESP32 module.\n\n\nHOME\n: Return to user home page.\n\n\n\n\n\n\n Configure new AP\n\u00b6\n\n\nScan all available access point and display it. Strength and security of the detected AP are marked. The \n is indicated for the SSID that needs a security key. \"\nHidden:\n\" means the number of hidden SSIDs discovered.\n\nEnter SSID and Passphrase and tap \"\napply\n\" to starts a connection. \n\n\n\n\n Open SSIDs\n\u00b6\n\n\nOnce it was established connection, its SSID and Password will be stored to the EEPROM of ESP8266/ESP32 automatically. The \nOpen SSIDs\n menu reads the saved SSID credentials from the EEPROM. The stored credential data are listed by the SSID as shown below. Its label is a clickable button. Tap the SSID button, starts connection it.\n\n\n\n\n Disconnect\n\u00b6\n\n\nDisconnect ESP8266/ESP32 from the current connection. It can also reset the ESP8266/ESP32 automatically after disconnection by instructing with using \nAPI\n in the sketch.\n\n\nAfter tapping \"Disconnect\", you will not be able to reach the AutoConnect menu. Once disconnected, you will need to set the SSID again for connecting the WLAN. \n\n\n Reset...\n\u00b6\n\n\nReset the ESP8266/ESP32, it will start rebooting. After rebooting complete, the ESP8266/ESP32 module begins establishing the previous connection with WIFI_STA mode, and \nesp8266ap\n or \nesp32ap\n of an access point will disappear from WLAN.\n\n\n\n\n\n\nNot every ESP8266 module will be rebooted normally\n\n\nThe Reset menu is using the \nESP.reset()\n function for ESP8266. This is an almost hardware reset. In order to resume the sketch normally, the \nstate of GPIO0\n is important. Since this depends on the circuit implementation for each module, not every module will be rebooted normally. See also \nFAQ\n.",
             "title": "AutoConnect menu"
         },
         {
             "location": "/menu/index.html#where-the-from",
-            "text": "The AutoConnect menu appears when you access the  AutoConnect root path . It is assigned \" /_ac \" located on ESP8266  local IP address  by default. This location can be changed in the sketch. The following screen will appear at access to  http://{localIP}/_ac  as the root path. This is the statistics of the current WiFi connection. You can access the menu from the here, to invoke it tap   at right on top. (e.g.  http://192.168.244.1/_ac  for SoftAP mode.)    What's local IP?  A local IP means Local IP at connection established or SoftAP's IP.",
+            "text": "The AutoConnect menu appears when you access the  AutoConnect root path . It is assigned \" /_ac \" located on ESP8266/ESP32  local IP address  by default. This location can be changed in the sketch. The following screen will appear at access to  http://{localIP}/_ac  as the root path. This is the statistics of the current WiFi connection. You can access the menu from the here, to invoke it tap   at right on top. (e.g.  http://192.168.244.1/_ac  for SoftAP mode.)    What's local IP?  A local IP means Local IP at connection established or SoftAP's IP.",
             "title": " Where the from"
         },
         {
             "location": "/menu/index.html#right-on-top",
-            "text": "Currently, AutoConnect supports four menus. Undermost menu as \"HOME\" returns to the home path of its sketch.   Configure new AP : Configure SSID and Password for new access point.  Open SSIDs : Opens the past SSID which has been established connection from EEPROM.  Disconnect : Disconnects current connection.  Reset... : Rest the ESP8266 module.  HOME : Return to user home page.",
+            "text": "Currently, AutoConnect supports four menus. Undermost menu as \"HOME\" returns to the home path of its sketch.   Configure new AP : Configure SSID and Password for new access point.  Open SSIDs : Opens the past SSID which has been established connection from EEPROM.  Disconnect : Disconnects current connection.  Reset... : Rest the ESP8266/ESP32 module.  HOME : Return to user home page.",
             "title": " Right on top"
         },
         {
@@ -117,22 +117,22 @@
         },
         {
             "location": "/menu/index.html#open-ssids",
-            "text": "Once it was established connection, its SSID and Password will be stored to the EEPROM of ESP8266 automatically. The  Open SSIDs  menu reads the saved SSID credentials from the EEPROM. The stored credential data are listed by the SSID as shown below. Its label is a clickable button. Tap the SSID button, starts connection it.",
+            "text": "Once it was established connection, its SSID and Password will be stored to the EEPROM of ESP8266/ESP32 automatically. The  Open SSIDs  menu reads the saved SSID credentials from the EEPROM. The stored credential data are listed by the SSID as shown below. Its label is a clickable button. Tap the SSID button, starts connection it.",
             "title": " Open SSIDs"
         },
         {
             "location": "/menu/index.html#disconnect",
-            "text": "Disconnect ESP8266 from the current connection. It can also reset the ESP8266 automatically after disconnection by instructing with using  API  in the sketch.  After tapping \"Disconnect\", you will not be able to reach the AutoConnect menu. Once disconnected, you will need to set the SSID again for connecting the WLAN.",
+            "text": "Disconnect ESP8266/ESP32 from the current connection. It can also reset the ESP8266/ESP32 automatically after disconnection by instructing with using  API  in the sketch.  After tapping \"Disconnect\", you will not be able to reach the AutoConnect menu. Once disconnected, you will need to set the SSID again for connecting the WLAN.",
             "title": " Disconnect"
         },
         {
             "location": "/menu/index.html#reset",
-            "text": "Reset the ESP8266, it will start rebooting. After rebooting complete, the ESP8266 begins establishing the previous connection with WIFI_STA mode, and  esp8266ap  of an access point will disappear from WLAN.    Not every module will be rebooted normally  The Reset menu is using the  ESP.reset()  function. This is an almost hardware reset. In order to resume the sketch normally, the  state of GPIO0  is important. Since this depends on the circuit implementation for each module, not every module will be rebooted normally. See also  FAQ .",
+            "text": "Reset the ESP8266/ESP32, it will start rebooting. After rebooting complete, the ESP8266/ESP32 module begins establishing the previous connection with WIFI_STA mode, and  esp8266ap  or  esp32ap  of an access point will disappear from WLAN.    Not every ESP8266 module will be rebooted normally  The Reset menu is using the  ESP.reset()  function for ESP8266. This is an almost hardware reset. In order to resume the sketch normally, the  state of GPIO0  is important. Since this depends on the circuit implementation for each module, not every module will be rebooted normally. See also  FAQ .",
             "title": " Reset..."
         },
         {
             "location": "/basicusage/index.html",
-            "text": "Simple usage\n\u00b6\n\n\n Embed to the sketches\n\u00b6\n\n\nHow embed the AutoConnect to the sketches you have. Most simple approach to applying AutoConnect for the existing sketches, follow the below steps.\n\n\n\n\n\n  \nInsert \n#include\n \n<AutoConnect.h>\n to behind of \n#include\n \n<ESP8266WebServer.h>\n.\n\n  \nInsert \nAutoConnect\n \nPORTAL(WEBSERVER);\n to behind of \nESP8266WebServer\n \nWEBSERVER;\n declaration.\n1\n\n  \nRemove \nWiFi.\nbegin\n(\nSSID\n,\nPSK\n)\n and the subsequent logic for the connection status check.\n\n  \nReplace \nWEBSERVER\n.\nbegin\n()\n to \nPORTAL\n.\nbegin\n()\n.\n2\n\n  \nReplace \nWEBSERVER\n.\nhandleClient\n()\n to \nPORTAL\n.\nhandleClient\n()\n.\n3\n\n  \nIf the connection checks logic is needed, you can check the return value according to \nPORTAL\n.\nbegin\n()\n with \ntrue\n or \nfalse\n.\n\n\n\n\n\nBasic usage\n\u00b6\n\n\n Basic logic sequence for the user sketches\n\u00b6\n\n\n1. A typical logic sequence\n\u00b6\n\n\n\n\n\n\nInclude headers,\n \nESP8266WebServer.h\n and \nAutoConnect.h\n  \n\n\nDeclare ESP8266WebServer variable.\n  \n\n\nDeclare AutoConnect variable.\n  \n\n\nImplements the URL handler with the \nfunction()\n.\n  \n\n\nsetup()\n\n   5.1 \nSets URL handler \nfunction()\n to ESP8266WebServer by\nESP8266WebServer::on\n.\n\n   5.2 \nStarts \nAutoConnect::begin()\n.\n\n   5.3 \nCheck WiFi connection status.\n  \n\n\nloop()\n\n   6.1 \nInvokes \nAutoConnect::handleClient()\n, or invokes \nESP8266WebServer::handleClient()\n then \nAutoConnect::handleRequest()\n.\n\n   6.2 \nDo the process for actual sketch.\n  \n\n\n\n\n\n\n2. Declare AutoConnect object\n\u00b6\n\n\nTwo options\n are available for \nAutoConnect constructor\n.\n\n\nAutoConnect\n \nVARIABLE\n(\n&\nESP8266WebServer\n);\n\n\n\nor\n\n\nAutoConnect\n \nVARIABLE\n;\n\n\n\n\n\n\n\n\n\nThe parameter with an ESP8266WebServer variable:\n An ESP8266WebServer object variable must be declared. AutoConnect uses its variable to handles the \nAutoConnect menu\n.\n\n\n\n\n\n\nWith no parameter:\n 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 \nESP8266WebServer::on\n should be performed after \nAutoConnect::begin\n.\n\n\n\n\n\n\n3. No need WiFI.begin(...)\n\u00b6\n\n\nAutoConnect internally performs \nWiFi.begin\n to establish a WiFi connection. There is no need for a general process to establish a connection using \nWiFi.begin\n with a sketch code.\n\n\n4. Alternate ESP8266WebServer::begin()\n\u00b6\n\n\nAutoConnect::begin\n executes \nESP8266WebServer::begin\n internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call \nESP8266WebServer::begin\n with the sketch.\n\n\n\n\nWhy DNS Server starts\n\n\nAutoConnect 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.\n\n\n\n\n5. AutoConnect::begin with SSID and Password\n\u00b6\n\n\nSSID and Password can also specify by \nAutoConnect::begin\n. 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.\n\n\n6. Use ESP8266WebServer::on to handle URL\n\u00b6\n\n\nAutoConnect 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 \"\non::ESP8266WebServer\n\" function is the same as when using ESP8266WebServer natively.\n\n\n7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()\n\u00b6\n\n\nBoth classes member function name is the same: \nhandleClient\n, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient has limitations. Refer to the below section for details. \n\n\n ESP8266WebServer hosted or parasitic\n\u00b6\n\n\nThe interoperable process with an ESP8266WebServer depends on the parameters of the \nAutoConnect constructor\n.\n\n\n\n\n\n\n\n\nDeclaration parameter for the constructor\n\n\nUse ESP8266WebServer::handleClient only\n\n\nUse AutoConnect::handleClient\n\n\n\n\n\n\n\n\n\n\nNone\n\n\nAutoConnect menu not available.\nTo use AutoConnect menu, need \nAutoConnect::handleRequest()\n.\nalso to use ESP8266WebServer natively, need \nAutoConnect::host()\n.\n\n\nAutoConnect menu available.\nTo use ESP8266WebServer natively, need \nAutoConnect::host()\n.\n\n\n\n\n\n\nReference to ESP8266WebServer\n\n\nAutoConnect menu not available.\nTo use AutoConnect menu, need \nAutoConnect::handleRequest()\n.\n\n\nAutoConnect menu available.\n\n\n\n\n\n\n\n\n\n\n\n\nBy declaration for the AutoConnect variable with no parameter\n: The ESP8266WebServer instance is hosted by AutoConnect automatically then the sketches use \nAutoConnect::host\n as API to get it after \nAutoConnect::begin\n performed.\n\n\n\n\n\n\nBy declaration for the AutoConnect variable with the reference of ESP8266WebServer\n: AutoConnect will use it. The sketch can use it is too.\n\n\n\n\n\n\nIn use ESP8266WebServer::handleClient()\n: AutoConnect menu can be dispatched but not works normally. It is necessary to call \nAutoConnect::handleRequest\n after \nESP8255WebServer::handleClient\n invoking.\n\n\n\n\n\n\nIn use \nAutoConnect::handleClient()\n: The handleClient() process and the AutoConnect menu is available without calling \nESP8266WebServer::handleClient\n.\n\n\n\n\n\n\n\n\nWhy AutoConnect::handleRequest is needed when using ESP8266::handleClient\n\n\nThe AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside \nESP8266WebServer::handleClient\n.\n\n\nAutoConnect::handleClient\n is equivalent \nESP8266WebServer::handleClient\n included \nAutoConnect::handleRequest\n.\n\n\n\n\n\n\n\n\n\n\n\n\nEach \nVARIABLE\n conforms to the actual declaration in the sketches.\u00a0\n\u21a9\n\n\n\n\n\n\nWiFi SSID and Password can be specified AutoConnect::begin() too.\u00a0\n\u21a9\n\n\n\n\n\n\nReplacement the \nhandleClient\n method is not indispensable. AutoConnect can still connect with the captive portal as it is ESP8266WebServer::handleClient. But it can \nnot valid AutoConnect menu\n.\u00a0\n\u21a9",
+            "text": "Simple usage\n\u00b6\n\n\n Embed to the sketches\n\u00b6\n\n\nHow 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 \nESP8266WebServer\n with \nWebServer\n and \nESP8266WiFi.h\n with \nWiFi.h\n respectively.\n\n\n\n\n\n  \nInsert \n#include\n \n<AutoConnect.h>\n to behind of \n#include\n \n<ESP8266WebServer.h>\n.\n\n  \nInsert \nAutoConnect\n \nPORTAL(WEBSERVER);\n to behind of \nESP8266WebServer\n \nWEBSERVER;\n declaration.\n1\n\n  \nRemove \nWiFi.\nbegin\n(\nSSID\n,\nPSK\n)\n and the subsequent logic for the connection status check.\n\n  \nReplace \nWEBSERVER\n.\nbegin\n()\n to \nPORTAL\n.\nbegin\n()\n.\n2\n\n  \nReplace \nWEBSERVER\n.\nhandleClient\n()\n to \nPORTAL\n.\nhandleClient\n()\n.\n3\n\n  \nIf the connection checks logic is needed, you can check the return value according to \nPORTAL\n.\nbegin\n()\n with \ntrue\n or \nfalse\n.\n\n\n\n\n\nBasic usage\n\u00b6\n\n\n Basic logic sequence for the user sketches\n\u00b6\n\n\n1. A typical logic sequence\n\u00b6\n\n\n\n\n\n\nInclude headers,\n \nESP8266WebServer.h\n/\nWebServer.h\n and \nAutoConnect.h\n  \n\n\nDeclare ESP8266WebServer variable.\n  \n\n\nDeclare AutoConnect variable.\n  \n\n\nImplements the URL handler with the \nfunction()\n.\n  \n\n\nsetup()\n\n   5.1 \nSets URL handler \nfunction()\n to ESP8266WebServer/WebServer by\nESP8266WebServer::on\n/\nWebServer::on\n.\n\n   5.2 \nStarts \nAutoConnect::begin()\n.\n\n   5.3 \nCheck WiFi connection status.\n  \n\n\nloop()\n\n   6.1 \nInvokes \nAutoConnect::handleClient()\n, or invokes \nESP8266WebServer::handleClient()\n/\nWebServer::handleClient\n then \nAutoConnect::handleRequest()\n.\n\n   6.2 \nDo the process for actual sketch.\n  \n\n\n\n\n\n\n2. Declare AutoConnect object\n\u00b6\n\n\nTwo options\n are available for \nAutoConnect constructor\n.\n\n\nAutoConnect\n \nVARIABLE\n(\n&\nESP8266WebServer\n);\n  \n// For ESP8266\n\n\nAutoConnect\n \nVARIABLE\n(\n&\nWebServer\n);\n         \n// For ESP32\n\n\n\nor\n\n\nAutoConnect\n \nVARIABLE\n;\n\n\n\n\n\n\n\n\n\nThe parameter with an ESP8266WebServer/WebServer variable:\n An ESP8266WebServer/WebServer object variable must be declared. AutoConnect uses its variable to handles the \nAutoConnect menu\n.\n\n\n\n\n\n\nWith no parameter:\n 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 \nESP8266WebServer::on\n or \nWebServer::on\n should be performed after \nAutoConnect::begin\n.\n\n\n\n\n\n\n3. No need WiFI.begin(...)\n\u00b6\n\n\nAutoConnect internally performs \nWiFi.begin\n to establish a WiFi connection. There is no need for a general process to establish a connection using \nWiFi.begin\n with a sketch code.\n\n\n4. Alternate ESP8266WebServer::begin() and WebServer::begin()\n\u00b6\n\n\nAutoConnect::begin\n executes \nESP8266WebServer::begin\n/\nWebServer::begin\n internally too and it starts the DNS server to behave as a Captive portal. So it is not needed to call \nESP8266WebServer::begin\n/\nWebServer::begin\n with the sketch.\n\n\n\n\nWhy DNS Server starts\n\n\nAutoConnect 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.\n\n\n\n\n5. AutoConnect::begin with SSID and Password\n\u00b6\n\n\nSSID and Password can also specify by \nAutoConnect::begin\n. 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.\n\n\n6. Use ESP8266WebServer::on and WebServer::on to handle URL\n\u00b6\n\n\nAutoConnect 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 \"\non::ESP8266WebServer\n\" or the \"\non::WebServer\n\" function is the same as when using ESP8266WebServer/WebServer natively.\n\n\n7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()\n\u00b6\n\n\nBoth classes member function name is the same: \nhandleClient\n, but the behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient/WebServer::handleClient has limitations. Refer to the below section for details. \n\n\n ESP8266WebServer/WebServer hosted or parasitic\n\u00b6\n\n\nThe interoperable process with an ESP8266WebServer/WebServer depends on the parameters of the \nAutoConnect constructor\n.\n\n\n\n\n\n\n\n\nDeclaration parameter for the constructor\n\n\nUse ESP8266WebServer::handleClient or WebServer::handleClient only\n\n\nUse AutoConnect::handleClient\n\n\n\n\n\n\n\n\n\n\nNone\n\n\nAutoConnect menu not available.\nTo use AutoConnect menu, need \nAutoConnect::handleRequest()\n.\nalso to use ESP8266WebServer/WebServer natively, need \nAutoConnect::host()\n.\n\n\nAutoConnect menu available.\nTo use ESP8266WebServer natively, need \nAutoConnect::host()\n.\n\n\n\n\n\n\nReference to ESP8266WebServer/WebServer\n\n\nAutoConnect menu not available.\nTo use AutoConnect menu, need \nAutoConnect::handleRequest()\n.\n\n\nAutoConnect menu available.\n\n\n\n\n\n\n\n\n\n\n\n\nBy declaration for the AutoConnect variable with no parameter\n: The ESP8266WebServer/WebServer instance is hosted by AutoConnect automatically then the sketches use \nAutoConnect::host\n as API to get it after \nAutoConnect::begin\n performed.\n\n\n\n\n\n\nBy declaration for the AutoConnect variable with the reference of ESP8266WebServer/WebServer\n: AutoConnect will use it. The sketch can use it is too.\n\n\n\n\n\n\nIn use ESP8266WebServer::handleClient()/WebServer::handleClient()\n: AutoConnect menu can be dispatched but not works normally. It is necessary to call \nAutoConnect::handleRequest\n after \nESP8255WebServer::handleClient\n/\nWebServer::handleClient\n invoking.\n\n\n\n\n\n\nIn use \nAutoConnect::handleClient()\n: The handleClient() process and the AutoConnect menu is available without calling \nESP8266WebServer::handleClient\n.\n\n\n\n\n\n\n\n\nWhy AutoConnect::handleRequest is needed when using ESP8266WebServer::handleClient/WebServer::handleClient\n\n\nThe AutoConnect menu function may affect WiFi connection state. It follows that the menu process must execute outside \nESP8266WebServer::handleClient\n and \nWebServer::handleClient\n.\n\n\nAutoConnect::handleClient\n is equivalent \nESP8266WebServer::handleClient\n and \nWEbServer::handleClient\n included \nAutoConnect::handleRequest\n.\n\n\n\n\n\n\n\n\n\n\n\n\nEach \nVARIABLE\n conforms to the actual declaration in the sketches.\u00a0\n\u21a9\n\n\n\n\n\n\nWiFi SSID and Password can be specified AutoConnect::begin() too.\u00a0\n\u21a9\n\n\n\n\n\n\nReplacement the \nhandleClient\n method is not indispensable. AutoConnect can still connect with the captive portal as it is ESP8266WebServer::handleClient. But it can \nnot valid AutoConnect menu\n.\u00a0\n\u21a9",
             "title": "Basic usage"
         },
         {
@@ -142,7 +142,7 @@
         },
         {
             "location": "/basicusage/index.html#embed-to-the-sketches",
-            "text": "How embed the AutoConnect to the sketches you have. Most simple approach to applying AutoConnect for the existing sketches, follow the below steps.   \n   Insert  #include   <AutoConnect.h>  to behind of  #include   <ESP8266WebServer.h> . \n   Insert  AutoConnect   PORTAL(WEBSERVER);  to behind of  ESP8266WebServer   WEBSERVER;  declaration. 1 \n   Remove  WiFi. begin ( SSID , PSK )  and the subsequent logic for the connection status check. \n   Replace  WEBSERVER . begin ()  to  PORTAL . begin () . 2 \n   Replace  WEBSERVER . handleClient ()  to  PORTAL . handleClient () . 3 \n   If the connection checks logic is needed, you can check the return value according to  PORTAL . begin ()  with  true  or  false .",
+            "text": "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.   \n   Insert  #include   <AutoConnect.h>  to behind of  #include   <ESP8266WebServer.h> . \n   Insert  AutoConnect   PORTAL(WEBSERVER);  to behind of  ESP8266WebServer   WEBSERVER;  declaration. 1 \n   Remove  WiFi. begin ( SSID , PSK )  and the subsequent logic for the connection status check. \n   Replace  WEBSERVER . begin ()  to  PORTAL . begin () . 2 \n   Replace  WEBSERVER . handleClient ()  to  PORTAL . handleClient () . 3 \n   If the connection checks logic is needed, you can check the return value according to  PORTAL . begin ()  with  true  or  false .",
             "title": " Embed to the sketches"
         },
         {
@@ -157,12 +157,12 @@
         },
         {
             "location": "/basicusage/index.html#1-a-typical-logic-sequence",
-            "text": "Include headers,   ESP8266WebServer.h  and  AutoConnect.h     Declare ESP8266WebServer variable.     Declare AutoConnect variable.     Implements the URL handler with the  function() .     setup() \n   5.1  Sets URL handler  function()  to ESP8266WebServer by ESP8266WebServer::on . \n   5.2  Starts  AutoConnect::begin() . \n   5.3  Check WiFi connection status.     loop() \n   6.1  Invokes  AutoConnect::handleClient() , or invokes  ESP8266WebServer::handleClient()  then  AutoConnect::handleRequest() . \n   6.2  Do the process for actual sketch.",
+            "text": "Include headers,   ESP8266WebServer.h / WebServer.h  and  AutoConnect.h     Declare ESP8266WebServer variable.     Declare AutoConnect variable.     Implements the URL handler with the  function() .     setup() \n   5.1  Sets URL handler  function()  to ESP8266WebServer/WebServer by ESP8266WebServer::on / WebServer::on . \n   5.2  Starts  AutoConnect::begin() . \n   5.3  Check WiFi connection status.     loop() \n   6.1  Invokes  AutoConnect::handleClient() , or invokes  ESP8266WebServer::handleClient() / WebServer::handleClient  then  AutoConnect::handleRequest() . \n   6.2  Do the process for actual sketch.",
             "title": "1. A typical logic sequence"
         },
         {
             "location": "/basicusage/index.html#2-declare-autoconnect-object",
-            "text": "Two options  are available for  AutoConnect constructor .  AutoConnect   VARIABLE ( & ESP8266WebServer );  \nor  AutoConnect   VARIABLE ;     The parameter with an ESP8266WebServer variable:  An ESP8266WebServer 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 .",
+            "text": "Two options  are available for  AutoConnect constructor .  AutoConnect   VARIABLE ( & ESP8266WebServer );    // For ESP8266  AutoConnect   VARIABLE ( & WebServer );           // For ESP32  \nor  AutoConnect   VARIABLE ;     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/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 .",
             "title": "2. Declare AutoConnect object"
         },
         {
@@ -171,33 +171,33 @@
             "title": "3. No need WiFI.begin(...)"
         },
         {
-            "location": "/basicusage/index.html#4-alternate-esp8266webserverbegin",
-            "text": "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.   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.",
-            "title": "4. Alternate ESP8266WebServer::begin()"
+            "location": "/basicusage/index.html#4-alternate-esp8266webserverbegin-and-webserverbegin",
+            "text": "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.",
+            "title": "4. Alternate ESP8266WebServer::begin() and WebServer::begin()"
         },
         {
             "location": "/basicusage/index.html#5-autoconnectbegin-with-ssid-and-password",
-            "text": "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.",
+            "text": "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.",
             "title": "5. AutoConnect::begin with SSID and Password"
         },
         {
-            "location": "/basicusage/index.html#6-use-esp8266webserveron-to-handle-url",
-            "text": "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.",
-            "title": "6. Use ESP8266WebServer::on to handle URL"
+            "location": "/basicusage/index.html#6-use-esp8266webserveron-and-webserveron-to-handle-url",
+            "text": "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.",
+            "title": "6. Use ESP8266WebServer::on and WebServer::on to handle URL"
         },
         {
-            "location": "/basicusage/index.html#7-use-either-esp8266webserverhandleclient-or-autoconnecthandleclient",
-            "text": "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.",
-            "title": "7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()"
+            "location": "/basicusage/index.html#7-use-either-esp8266webserverhandleclientwebserverhandleclient-or-autoconnecthandleclient",
+            "text": "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.",
+            "title": "7. Use either ESP8266WebServer::handleClient()/WebServer::handleClient() or AutoConnect::handleClient()"
         },
         {
-            "location": "/basicusage/index.html#esp8266webserver-hosted-or-parasitic",
-            "text": "The interoperable process with an ESP8266WebServer depends on the parameters of the  AutoConnect constructor .     Declaration parameter for the constructor  Use ESP8266WebServer::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 available. To use ESP8266WebServer natively, need  AutoConnect::host() .    Reference to ESP8266WebServer  AutoConnect menu not available. To use AutoConnect menu, need  AutoConnect::handleRequest() .  AutoConnect menu available.       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 the reference of ESP8266WebServer : 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  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 .       Each  VARIABLE  conforms to the actual declaration in the sketches.\u00a0 \u21a9    WiFi SSID and Password can be specified AutoConnect::begin() too.\u00a0 \u21a9    Replacement the  handleClient  method is not indispensable. AutoConnect can still connect with the captive portal as it is ESP8266WebServer::handleClient. But it can  not valid AutoConnect menu .\u00a0 \u21a9",
-            "title": " ESP8266WebServer hosted or parasitic"
+            "location": "/basicusage/index.html#esp8266webserverwebserver-hosted-or-parasitic",
+            "text": "The interoperable process with an ESP8266WebServer/WebServer depends on the parameters of the  AutoConnect constructor .     Declaration parameter for the constructor  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/WebServer natively, need  AutoConnect::host() .  AutoConnect menu available. To use ESP8266WebServer natively, need  AutoConnect::host() .    Reference to ESP8266WebServer/WebServer  AutoConnect menu not available. To use AutoConnect menu, need  AutoConnect::handleRequest() .  AutoConnect menu available.       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/WebServer : AutoConnect will use it. The sketch can use it is too.    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 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 .       Each  VARIABLE  conforms to the actual declaration in the sketches.\u00a0 \u21a9    WiFi SSID and Password can be specified AutoConnect::begin() too.\u00a0 \u21a9    Replacement the  handleClient  method is not indispensable. AutoConnect can still connect with the captive portal as it is ESP8266WebServer::handleClient. But it can  not valid AutoConnect menu .\u00a0 \u21a9",
+            "title": " ESP8266WebServer/WebServer hosted or parasitic"
         },
         {
             "location": "/advancedusage/index.html",
-            "text": "Advanced usage\n\u00b6\n\n\n 404 handler\n\u00b6\n\n\nRegistering the \"not found\" handler is a different way than ESP8266WebServer. The \nonNotFound\n of ESP8266WebServer does not work with AutoConnect. AutoConnect overrides \nESP8266WebServer::onNotFound\n to handle a captive portal. To register \"not found\" handler, use \nAutoConnect::onNotFound\n.\n\n\n Automatic reconnect\n\u00b6\n\n\nWhen the captive portal is started, SoftAP starts and the STA is disconnected. The current SSID setting memorized in ESP8266 will be lost.\n\nIf the \nautoReconnect\n option of the \nAutoConnectConfig\n 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.\n\n\nAutoConnect\n       \nPortal\n;\n\n\nAutoConnectConfig\n \nConfig\n;\n\n\nConfig\n.\nautoReconnect\n \n=\n \ntrue\n;\n\n\nPortal\n.\nconfig\n(\nConfig\n);\n\n\nPortal\n.\nbegin\n();\n\n\n\n\n\nAn autoReconnect option is available to \nAutoConnect::begin\n without SSID and pass passphrase.\n\n\n Auto save Credential\n\u00b6\n\n\nBy default, AutoConnect saves the credentials of the established connection in EEPROM. You can disable it with the \nautoSave\n parameter specified by \nAutoConnectConfig\n.\n\n\nAutoConnect\n       \nPortal\n;\n\n\nAutoConnectConfig\n \nConfig\n;\n\n\nConfig\n.\nautoSave\n \n=\n \nAC_SAVECREDENTIAL_NEVER\n;\n\n\nPortal\n.\nconfig\n(\nConfig\n);\n\n\nPortal\n.\nbegin\n();\n\n\n\n\n\n Captive portal start detection\n\u00b6\n\n\nThe captive portal will only be activated if the first \nWiFi::begin\n fails. Sketch can detect with the \nAutoConnect::onDetect\n 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.\n\n\nAutoConnect\n \nPortal\n;\n\n\n\nbool\n \nstartCP\n(\nIPAddress\n \nip\n)\n \n{\n\n\n  \ndigitalWrite\n(\nBUILTIN_LED\n,\n \nHIGH\n);\n\n  \nSerial\n.\nprintln\n(\n\"C.P. started, IP:\"\n \n+\n \nWiFi\n.\nlocalIP\n().\ntoString\n());\n\n  \nreturn\n \ntrue\n;\n\n\n}\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \nSerial\n.\nbegin\n(\n115200\n);\n\n  \npinMode\n(\nBUILTIN_LED\n,\n \nOUTPUT\n);\n\n  \ndigitalWrite\n(\nBUILTIN_LED\n,\n \nLOW\n);\n\n\n  \nPortal\n.\nonDetect\n(\nstartCP\n);\n\n\n  \nif\n \n(\nPortal\n.\nbegin\n())\n \n{\n\n    \ndigitalWrite\n(\nBUILTIN_LED\n,\n \nLOW\n);\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n  \nPortal\n.\nhandleClient\n();\n\n\n}\n\n\n\n\n\n Combination with mDNS\n\u00b6\n\n\nWith \nmDNS library\n, you can access to ESP8266 by name instead of IP address after connection. The sketch can start the MDNS responder after \nAutoConnect::begin\n.\n\n\n#include\n \n<ESP8266WiFi.h>\n\n\n#include\n \n<ESP8266mDNS.h>\n\n\n#include\n \n<ESP8266WebServer.h>\n\n\nAutoConnect\n \nPortal\n;\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \nif\n \n(\nPortal\n.\nbegin\n())\n \n{\n\n\n    \nif\n \n(\nMDNS\n.\nbegin\n(\n\"esp8266\"\n))\n \n{\n\n\n      \nMDNS\n.\naddService\n(\n\"http\"\n,\n \n\"tcp\"\n,\n \n80\n);\n\n\n    \n}\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n  \nPortal\n.\nhandleClient\n();\n\n\n}\n\n\n\n\n\n Debug print\n\u00b6\n\n\nYou can output AutoConnect monitor messages to the \nSerial\n. A monitor message activation switch is in an include header file \nAutoConnect.h\n of library source. Define \nAC_DEBUG\n macro to output the monitor messages.\n\n\n#define AC_DEBUG\n\n\n\n\n\n Disable the captive portal\n\u00b6\n\n\nIt can also prevent the captive portal from starting even if the connection at the first \nWiFi.begin\n fails. In this case, \nAutoConnect::begin\n behaves same as \nWiFi.begin\n.\n\n\nFor disabling the captive portal, \nautoRise\n sets to false with \nAutoConnectConfig\n.\n\n\nAutoConnect\n       \nportal\n;\n\n\nAutoConnectConfig\n \nacConfig\n;\n\n\n\nacConfig\n.\nautoRaise\n \n=\n \nfalse\n;\n\n\nportal\n.\nconfig\n(\nacConfig\n);\n\n\nportal\n.\nbegin\n();\n\n\n\n\n\n Move the saving area of EEPROM for the credentials\n\u00b6\n\n\nBy default, the credentials saving area is occupied from the beginning of EEPROM area. \nESP8266 Arduino core document\n says that:\n\n\n\n\nThe following diagram illustrates flash layout used in Arduino environment:\n\n\n\n\n\n\n\n  \n|--------------|-------|---------------|--|--|--|--|--|\n\n  \n^\n              \n^\n       \n^\n               \n^\n     \n^\n\n  \nSketch\n    \nOTA\n \nupdate\n   \nFile\n \nsystem\n   \nEEPROM\n  \nWiFi\n \nconfig\n \n(\nSDK\n)\n\n\n\n\n\n\n\nand\n\n\n\n\nEEPROM library uses one sector of flash located \njust after the SPIFFS\n.\n\n\n\n\nSo 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.\n\n\nThe \nboundaryOffset\n in \nAutoConnectConfig\n specifies the start offset of the credentials storage area. The default value is 0.\n\n\n Refers the hosted ESP8266WebServer\n\u00b6\n\n\nConstructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer inside the AutoConnect. This object variable could be referred by \nAutoConnect::host()\n function to access ESP8266WebServer instance as like below.\n\n\nAutoConnect\n \nPortal\n;\n\n\n\nPortal\n.\nbegin\n();\n\n\nESP8266WebServer\n&\n \nserver\n \n=\n \nPortal\n.\nhost\n();\n\n\nserver\n.\nsend\n(\n200\n,\n \n\"text/plain\"\n,\n \n\"Hello, world\"\n);\n\n\n\n\n\n\n\nWhen host() is valid\n\n\nThe host() can be referred at after \nAutoConnect::begin\n.\n\n\n\n\n Usage for automatically instantiated ESP8266WebServer\n\u00b6\n\n\nThe sketch can handle URL requests using ESP8266WebServer that AutoConnect started internally. ESP8266WebServer instantiated dynamically by AutoConnect can be referred to by \nAutoConnect::host\n function. The sketch can use the '\non\n' function, '\nsend\n' function, '\nclient\n' function and others by ESP8266WebServer reference of its return value.\n\n\n#include\n \n<ESP8266WiFi.h>\n\n\n#include\n \n<ESP8266WebServer.h>\n\n\n#include\n \n<AutoConnect.h>\n\n\n\nAutoConnect\n       \nPortal\n;\n\n\n\nvoid\n \nhandleRoot\n()\n \n{\n\n\n  \nESP8266WebServer\n&\n \nIntServer\n \n=\n \nPortal\n.\nhost\n();\n\n\n  \nIntServer\n.\nsend\n(\n200\n,\n \n\"text/html\"\n,\n \n\"Hello, world\"\n);\n\n\n}\n\n\n\nvoid\n \nhandleNotFound\n()\n \n{\n\n\n  \nESP8266WebServer\n&\n \nIntServer\n \n=\n \nPortal\n.\nhost\n();\n\n\n  \nIntServer\n.\nsend\n(\n404\n,\n \n\"text/html\"\n,\n \n\"Unknown.\"\n);\n\n\n}\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \nbool\n \nr\n \n=\n \nPortal\n.\nbegin\n();\n\n  \nif\n \n(\nr\n)\n \n{\n\n\n    \nESP8266WebServer\n&\n \nIntServer\n \n=\n \nPortal\n.\nhost\n();\n\n\n    \nIntServer\n.\non\n(\n\"/\"\n,\n \nhandleRoot\n);\n\n\n    \nPortal\n.\nonNotFound\n(\nhandleNotFound\n);\n    \n// For only onNotFound.\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n\n  \nPortal\n.\nhost\n().\nhandleClient\n();\n\n\n  \nPortal\n.\nhandleRequest\n();\n\n  \n/* or following one line code is equ.\n\n\n  Portal.handleClient();\n\n\n  */\n\n\n}\n\n\n\n\n\n\n\nESP8266WebServer function should be called after AutoConnect::begin\n\n\nThe sketch cannot refer to an instance of ESP8266WebServer until AutoConnect::begin completes successfully.\n\n\n\n\n\n\nDo not use with ESP8266WebServer::begin\n\n\nESP8266WebServer is already running inside the AutoConnect.\n\n\n\n\n Use with the \nPageBuilder\n library\n\u00b6\n\n\nIn ordinary, the URL handler will respond the request by sending some HTML. \nPageBuilder\n 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.\n\n\nAn example sketch used with the PageBuilder as follows and it explains how it aids for the HTML generating. Details for \nGithub repository\n.\n\n\n\n\nConfiguration functions\n\u00b6\n\n\n Configuration for Soft AP\n\u00b6\n\n\nAutoConnect will activate SoftAP at failed the first \nWiFi.begin\n. It SoftAP settings are stored in \nAutoConnectConfig\n as the following parameters. The sketch could be configured SoftAP using these parameters, refer the \nAutoConnectConfig API\n for details.\n\n\n\n\nIP address of SoftAP activated.\n\n\nGateway IP address.\n\n\nSubnet mask.\n\n\nSSID for SoftAP.\n\n\nPassword for SoftAP.\n\n\nChannel.\n\n\nHidden attribute.\n\n\nAuto save credential.\n\n\nOffset address of the credentials storage area in EEPROM.\n\n\nLength of start up time after reset.\n\n\nAutomatic starting the captive portal.\n\n\nAuto reset after connection establishment.\n\n\nHome URL of the user sketch application.\n\n\n\n\n\n\nAutoConnect::config before AutoConnect::begin\n\n\nAutoConnect::config\n must be executed before \nAutoConnect::begin\n.\n\n\n\n\n Assign user sketch's home path\n\u00b6\n\n\n\"\nHOME\n\" for returning to the user's sketch homepage is displayed at the bottom of the AutoConnect menu. It could be set using the \nAutoConnect::home\n function.\n\n\n\n\n Relocate the AutoConnect home path\n\u00b6\n\n\nA home path of AutoConnect is \n/_ac\n by default. You can access from the browser with http://IPADDRESS/_ac. You can change the home path by revising \nAUTOCONNECT_URI\n macro in the include header file as \nAutoConnect.h\n.\n\n\n#define AUTOCONNECT_URI         \"/_ac\"\n\n\n\n\n\n Static IP assignment \n1\n\u00b6\n\n\nIt 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 \nWiFi.begin\n.\n\n\nTo assign a static IP to ESP8266 with WIFI_MODE_STA, the following parameters are required:\n\n\n\n\nIP address.\n\n\nGateway address.\n\n\nSubnet mask.\n\n\nPrimary DNS server.\n\n\nSecondary DNS server. (optional)\n\n\n\n\nThe above parameters must be executed before \nAutoConnect::begin\n as \narguments of AutoConnectConfig\n.\n\n\nAutoConnect\n        \nportal\n;\n\n\nAutoConnectConfig\n  \nConfig\n;\n\n\nConfig\n.\nstaip\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n1\n,\n10\n);\n\n\nConfig\n.\nstaGateway\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n1\n,\n1\n);\n\n\nConfig\n.\nstaNetmask\n \n=\n \nIPAddress\n(\n255\n,\n255\n,\n255\n,\n0\n);\n\n\nConfig\n.\ndns1\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n1\n,\n1\n);\n\n\nportal\n.\nconfig\n(\nConfig\n);\n\n\nportal\n.\nbegin\n();\n\n\n\n\n\n\n\n\n\n\n\n\n\nStatic IP address assignment is available from version 0.9.3.\u00a0\n\u21a9",
+            "text": "Advanced usage\n\u00b6\n\n\n 404 handler\n\u00b6\n\n\nRegistering the \"not found\" handler is a different way than ESP8266WebServer/WebServer. The \nonNotFound\n of ESP8266WebServer/WebServer does not work with AutoConnect. AutoConnect overrides \nESP8266WebServer::onNotFound\n/\nWebServer::onNotFound\n to handle a captive portal. To register \"not found\" handler, use \nAutoConnect::onNotFound\n.\n\n\n Automatic reconnect\n\u00b6\n\n\nWhen 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.\n\nThe \nWiFiSTAClass::disconnect\n 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 \nESP8266WiFiSTAClass\n 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.\n\nIf the \nautoReconnect\n option of the \nAutoConnectConfig\n 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.\n\n\nAutoConnect\n       \nPortal\n;\n\n\nAutoConnectConfig\n \nConfig\n;\n\n\nConfig\n.\nautoReconnect\n \n=\n \ntrue\n;\n\n\nPortal\n.\nconfig\n(\nConfig\n);\n\n\nPortal\n.\nbegin\n();\n\n\n\n\n\nAn autoReconnect option is available to \nAutoConnect::begin\n without SSID and pass passphrase.\n\n\n Auto save Credential\n\u00b6\n\n\nBy default, AutoConnect saves the credentials of the established connection in EEPROM. You can disable it with the \nautoSave\n parameter specified by \nAutoConnectConfig\n.\n\n\nAutoConnect\n       \nPortal\n;\n\n\nAutoConnectConfig\n \nConfig\n;\n\n\nConfig\n.\nautoSave\n \n=\n \nAC_SAVECREDENTIAL_NEVER\n;\n\n\nPortal\n.\nconfig\n(\nConfig\n);\n\n\nPortal\n.\nbegin\n();\n\n\n\n\n\n\n\nIn ESP32, the credentials for AutoConnect are not in NVS\n\n\nThe 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 \ndefault.csv\n\n\n\n\n Captive portal start detection\n\u00b6\n\n\nThe captive portal will only be activated if the first \nWiFi::begin\n fails. Sketch can detect with the \nAutoConnect::onDetect\n 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.\n\n\nAutoConnect\n \nPortal\n;\n\n\n\nbool\n \nstartCP\n(\nIPAddress\n \nip\n)\n \n{\n\n\n  \ndigitalWrite\n(\nBUILTIN_LED\n,\n \nHIGH\n);\n\n  \nSerial\n.\nprintln\n(\n\"C.P. started, IP:\"\n \n+\n \nWiFi\n.\nlocalIP\n().\ntoString\n());\n\n  \nreturn\n \ntrue\n;\n\n\n}\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \nSerial\n.\nbegin\n(\n115200\n);\n\n  \npinMode\n(\nBUILTIN_LED\n,\n \nOUTPUT\n);\n\n  \ndigitalWrite\n(\nBUILTIN_LED\n,\n \nLOW\n);\n\n\n  \nPortal\n.\nonDetect\n(\nstartCP\n);\n\n\n  \nif\n \n(\nPortal\n.\nbegin\n())\n \n{\n\n    \ndigitalWrite\n(\nBUILTIN_LED\n,\n \nLOW\n);\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n  \nPortal\n.\nhandleClient\n();\n\n\n}\n\n\n\n\n\n Combination with mDNS\n\u00b6\n\n\nWith \nmDNS library\n, you can access to ESP8266 by name instead of IP address after connection. The sketch can start the MDNS responder after \nAutoConnect::begin\n.\n\n\n#include\n \n<ESP8266WiFi.h>\n\n\n#include\n \n<ESP8266mDNS.h>\n\n\n#include\n \n<ESP8266WebServer.h>\n\n\nAutoConnect\n \nPortal\n;\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \nif\n \n(\nPortal\n.\nbegin\n())\n \n{\n\n\n    \nif\n \n(\nMDNS\n.\nbegin\n(\n\"esp8266\"\n))\n \n{\n\n\n      \nMDNS\n.\naddService\n(\n\"http\"\n,\n \n\"tcp\"\n,\n \n80\n);\n\n\n    \n}\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n  \nPortal\n.\nhandleClient\n();\n\n\n}\n\n\n\n\n\n Debug print\n\u00b6\n\n\nYou can output AutoConnect monitor messages to the \nSerial\n. A monitor message activation switch is in an include header file \nAutoConnect.h\n of library source. Define \nAC_DEBUG\n macro to output the monitor messages.\n\n\n#define AC_DEBUG\n\n\n\n\n\n Disable the captive portal\n\u00b6\n\n\nIt can also prevent the captive portal from starting even if the connection at the first \nWiFi.begin\n fails. In this case, \nAutoConnect::begin\n behaves same as \nWiFi.begin\n.\n\n\nFor disabling the captive portal, \nautoRise\n sets to false with \nAutoConnectConfig\n.\n\n\nAutoConnect\n       \nportal\n;\n\n\nAutoConnectConfig\n \nacConfig\n;\n\n\n\nacConfig\n.\nautoRaise\n \n=\n \nfalse\n;\n\n\nportal\n.\nconfig\n(\nacConfig\n);\n\n\nportal\n.\nbegin\n();\n\n\n\n\n\n Move the saving area of EEPROM for the credentials\n\u00b6\n\n\nBy default, the credentials saving area is occupied from the beginning of EEPROM area. \nESP8266 Arduino core document\n says that:\n\n\n\n\nThe following diagram illustrates flash layout used in Arduino environment:\n\n\n\n\n\n\n\n  \n|--------------|-------|---------------|--|--|--|--|--|\n\n  \n^\n              \n^\n       \n^\n               \n^\n     \n^\n\n  \nSketch\n    \nOTA\n \nupdate\n   \nFile\n \nsystem\n   \nEEPROM\n  \nWiFi\n \nconfig\n \n(\nSDK\n)\n\n\n\n\n\n\n\nand\n\n\n\n\nEEPROM library uses one sector of flash located \njust after the SPIFFS\n.\n\n\n\n\nAlso, the placement of the EEPROM area of ESP32 is described in the \npartition table\n. 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.\n\n\nThe \nboundaryOffset\n in \nAutoConnectConfig\n specifies the start offset of the credentials storage area. The default value is 0.\n\n\n Refers the hosted ESP8266WebServer/WebServer\n\u00b6\n\n\nConstructing an AutoConnect object variable without parameters then creates and starts an ESP8266WebServer/WebServer inside the AutoConnect. This object variable could be referred by \nAutoConnect::host()\n function to access ESP8266WebServer/WebServer instance as like below.\n\n\nAutoConnect\n \nPortal\n;\n\n\n\nPortal\n.\nbegin\n();\n\n\nESP8266WebServer\n&\n \nserver\n \n=\n \nPortal\n.\nhost\n();\n\n\nserver\n.\nsend\n(\n200\n,\n \n\"text/plain\"\n,\n \n\"Hello, world\"\n);\n\n\n\n\n\n\n\nWhen host() is valid\n\n\nThe host() can be referred at after \nAutoConnect::begin\n.\n\n\n\n\n Usage for automatically instantiated ESP8266WebServer/WebServer\n\u00b6\n\n\nThe sketch can handle URL requests using ESP8266WebServer or WebServer that AutoConnect started internally. ESP8266WebServer/WebServer instantiated dynamically by AutoConnect can be referred to by \nAutoConnect::host\n function. The sketch can use the '\non\n' function, '\nsend\n' function, '\nclient\n' function and others by ESP8266WebServer/WebServer reference of its return value.\n\n\n#include\n \n<ESP8266WiFi.h>\n\n\n#include\n \n<ESP8266WebServer.h>\n\n\n#include\n \n<AutoConnect.h>\n\n\n\nAutoConnect\n       \nPortal\n;\n\n\n\nvoid\n \nhandleRoot\n()\n \n{\n\n\n  \nESP8266WebServer\n&\n \nIntServer\n \n=\n \nPortal\n.\nhost\n();\n\n\n  \nIntServer\n.\nsend\n(\n200\n,\n \n\"text/html\"\n,\n \n\"Hello, world\"\n);\n\n\n}\n\n\n\nvoid\n \nhandleNotFound\n()\n \n{\n\n\n  \nESP8266WebServer\n&\n \nIntServer\n \n=\n \nPortal\n.\nhost\n();\n\n\n  \nIntServer\n.\nsend\n(\n404\n,\n \n\"text/html\"\n,\n \n\"Unknown.\"\n);\n\n\n}\n\n\n\nvoid\n \nsetup\n()\n \n{\n\n  \nbool\n \nr\n \n=\n \nPortal\n.\nbegin\n();\n\n  \nif\n \n(\nr\n)\n \n{\n\n\n    \nESP8266WebServer\n&\n \nIntServer\n \n=\n \nPortal\n.\nhost\n();\n\n\n    \nIntServer\n.\non\n(\n\"/\"\n,\n \nhandleRoot\n);\n\n\n    \nPortal\n.\nonNotFound\n(\nhandleNotFound\n);\n    \n// For only onNotFound.\n\n  \n}\n\n\n}\n\n\n\nvoid\n \nloop\n()\n \n{\n\n\n  \nPortal\n.\nhost\n().\nhandleClient\n();\n\n\n  \nPortal\n.\nhandleRequest\n();\n\n  \n/* or following one line code is equ.\n\n\n  Portal.handleClient();\n\n\n  */\n\n\n}\n\n\n\n\n\n\n\nESP8266WebServer/WebServer function should be called after AutoConnect::begin\n\n\nThe sketch cannot refer to an instance of ESP8266WebServer/WebServer until AutoConnect::begin completes successfully.\n\n\n\n\n\n\nDo not use with ESP8266WebServer::begin or WebServer::begin\n\n\nESP8266WebServer/WebServer is already running inside the AutoConnect.\n\n\n\n\n Use with the \nPageBuilder\n library\n\u00b6\n\n\nIn ordinary, the URL handler will respond the request by sending some HTML. \nPageBuilder\n 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.\n\n\nAn example sketch used with the PageBuilder as follows and it explains how it aids for the HTML generating. Details for \nGithub repository\n.\n\n\n\n\nConfiguration functions\n\u00b6\n\n\n Configuration for Soft AP\n\u00b6\n\n\nAutoConnect will activate SoftAP at failed the first \nWiFi.begin\n. It SoftAP settings are stored in \nAutoConnectConfig\n as the following parameters. The sketch could be configured SoftAP using these parameters, refer the \nAutoConnectConfig API\n for details.\n\n\n\n\nIP address of SoftAP activated.\n\n\nGateway IP address.\n\n\nSubnet mask.\n\n\nSSID for SoftAP.\n\n\nPassword for SoftAP.\n\n\nChannel.\n\n\nHidden attribute.\n\n\nAuto save credential.\n\n\nOffset address of the credentials storage area in EEPROM.\n\n\nLength of start up time after reset.\n\n\nAutomatic starting the captive portal.\n\n\nAuto reset after connection establishment.\n\n\nHome URL of the user sketch application.\n\n\n\n\n\n\nAutoConnect::config before AutoConnect::begin\n\n\nAutoConnect::config\n must be executed before \nAutoConnect::begin\n.\n\n\n\n\n Assign user sketch's home path\n\u00b6\n\n\n\"\nHOME\n\" for returning to the user's sketch homepage is displayed at the bottom of the AutoConnect menu. It could be set using the \nAutoConnect::home\n function.\n\n\n\n\n Relocate the AutoConnect home path\n\u00b6\n\n\nA home path of AutoConnect is \n/_ac\n by default. You can access from the browser with http://IPADDRESS/_ac. You can change the home path by revising \nAUTOCONNECT_URI\n macro in the include header file as \nAutoConnect.h\n.\n\n\n#define AUTOCONNECT_URI         \"/_ac\"\n\n\n\n\n\n Static IP assignment \n1\n\u00b6\n\n\nIt 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 \nWiFi.begin\n.\n\n\nTo assign a static IP to ESP8266/ESP32 with WIFI_MODE_STA, the following parameters are required:\n\n\n\n\nIP address.\n\n\nGateway address.\n\n\nSubnet mask.\n\n\nPrimary DNS server.\n\n\nSecondary DNS server. (optional)\n\n\n\n\nThe above parameters must be executed before \nAutoConnect::begin\n as \narguments of AutoConnectConfig\n.\n\n\nAutoConnect\n        \nportal\n;\n\n\nAutoConnectConfig\n  \nConfig\n;\n\n\nConfig\n.\nstaip\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n1\n,\n10\n);\n\n\nConfig\n.\nstaGateway\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n1\n,\n1\n);\n\n\nConfig\n.\nstaNetmask\n \n=\n \nIPAddress\n(\n255\n,\n255\n,\n255\n,\n0\n);\n\n\nConfig\n.\ndns1\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n1\n,\n1\n);\n\n\nportal\n.\nconfig\n(\nConfig\n);\n\n\nportal\n.\nbegin\n();\n\n\n\n\n\n\n\n\n\n\n\n\n\nStatic IP address assignment is available from version 0.9.3.\u00a0\n\u21a9",
             "title": "Advanced usage"
         },
         {
@@ -207,17 +207,17 @@
         },
         {
             "location": "/advancedusage/index.html#404-handler",
-            "text": "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 .",
+            "text": "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 .",
             "title": " 404 handler"
         },
         {
             "location": "/advancedusage/index.html#automatic-reconnect",
-            "text": "When the captive portal is started, SoftAP starts and the STA is disconnected. The current SSID setting memorized in ESP8266 will be lost. \nIf 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 ;  Config . autoReconnect   =   true ;  Portal . config ( Config );  Portal . begin ();   An autoReconnect option is available to  AutoConnect::begin  without SSID and pass passphrase.",
+            "text": "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. \nThe  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. \nIf 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 ;  Config . autoReconnect   =   true ;  Portal . config ( Config );  Portal . begin ();   An autoReconnect option is available to  AutoConnect::begin  without SSID and pass passphrase.",
             "title": " Automatic reconnect"
         },
         {
             "location": "/advancedusage/index.html#auto-save-credential",
-            "text": "By default, AutoConnect saves the credentials of the established connection in EEPROM. You can disable it with the  autoSave  parameter specified by  AutoConnectConfig .  AutoConnect         Portal ;  AutoConnectConfig   Config ;  Config . autoSave   =   AC_SAVECREDENTIAL_NEVER ;  Portal . config ( Config );  Portal . begin ();",
+            "text": "By default, AutoConnect saves the credentials of the established connection in EEPROM. You can disable it with the  autoSave  parameter specified by  AutoConnectConfig .  AutoConnect         Portal ;  AutoConnectConfig   Config ;  Config . autoSave   =   AC_SAVECREDENTIAL_NEVER ;  Portal . config ( Config );  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",
             "title": " Auto save Credential"
         },
         {
@@ -242,18 +242,18 @@
         },
         {
             "location": "/advancedusage/index.html#move-the-saving-area-of-eeprom-for-the-credentials",
-            "text": "By default, the credentials saving area is occupied from the beginning of EEPROM area.  ESP8266 Arduino core document  says that:   The following diagram illustrates flash layout used in Arduino environment:    \n   |--------------|-------|---------------|--|--|--|--|--| \n   ^                ^         ^                 ^       ^ \n   Sketch      OTA   update     File   system     EEPROM    WiFi   config   ( SDK )    and   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.  The  boundaryOffset  in  AutoConnectConfig  specifies the start offset of the credentials storage area. The default value is 0.",
+            "text": "By default, the credentials saving area is occupied from the beginning of EEPROM area.  ESP8266 Arduino core document  says that:   The following diagram illustrates flash layout used in Arduino environment:    \n   |--------------|-------|---------------|--|--|--|--|--| \n   ^                ^         ^                 ^       ^ \n   Sketch      OTA   update     File   system     EEPROM    WiFi   config   ( SDK )    and   EEPROM library uses one sector of flash located  just after the SPIFFS .   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.",
             "title": " Move the saving area of EEPROM for the credentials"
         },
         {
-            "location": "/advancedusage/index.html#refers-the-hosted-esp8266webserver",
-            "text": "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.  AutoConnect   Portal ;  Portal . begin ();  ESP8266WebServer &   server   =   Portal . host ();  server . send ( 200 ,   \"text/plain\" ,   \"Hello, world\" );    When host() is valid  The host() can be referred at after  AutoConnect::begin .",
-            "title": " Refers the hosted ESP8266WebServer"
+            "location": "/advancedusage/index.html#refers-the-hosted-esp8266webserverwebserver",
+            "text": "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 ();  ESP8266WebServer &   server   =   Portal . host ();  server . send ( 200 ,   \"text/plain\" ,   \"Hello, world\" );    When host() is valid  The host() can be referred at after  AutoConnect::begin .",
+            "title": " Refers the hosted ESP8266WebServer/WebServer"
         },
         {
-            "location": "/advancedusage/index.html#usage-for-automatically-instantiated-esp8266webserver",
-            "text": "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.  #include   <ESP8266WiFi.h>  #include   <ESP8266WebServer.h>  #include   <AutoConnect.h>  AutoConnect         Portal ;  void   handleRoot ()   {     ESP8266WebServer &   IntServer   =   Portal . host ();     IntServer . send ( 200 ,   \"text/html\" ,   \"Hello, world\" );  }  void   handleNotFound ()   {     ESP8266WebServer &   IntServer   =   Portal . host ();     IntServer . send ( 404 ,   \"text/html\" ,   \"Unknown.\" );  }  void   setup ()   { \n   bool   r   =   Portal . begin (); \n   if   ( r )   {       ESP8266WebServer &   IntServer   =   Portal . host ();       IntServer . on ( \"/\" ,   handleRoot );       Portal . onNotFound ( handleNotFound );      // For only onNotFound. \n   }  }  void   loop ()   {     Portal . host (). handleClient ();     Portal . handleRequest (); \n   /* or following one line code is equ.    Portal.handleClient();    */  }    ESP8266WebServer function should be called after AutoConnect::begin  The sketch cannot refer to an instance of ESP8266WebServer until AutoConnect::begin completes successfully.    Do not use with ESP8266WebServer::begin  ESP8266WebServer is already running inside the AutoConnect.",
-            "title": " Usage for automatically instantiated ESP8266WebServer"
+            "location": "/advancedusage/index.html#usage-for-automatically-instantiated-esp8266webserverwebserver",
+            "text": "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>  AutoConnect         Portal ;  void   handleRoot ()   {     ESP8266WebServer &   IntServer   =   Portal . host ();     IntServer . send ( 200 ,   \"text/html\" ,   \"Hello, world\" );  }  void   handleNotFound ()   {     ESP8266WebServer &   IntServer   =   Portal . host ();     IntServer . send ( 404 ,   \"text/html\" ,   \"Unknown.\" );  }  void   setup ()   { \n   bool   r   =   Portal . begin (); \n   if   ( r )   {       ESP8266WebServer &   IntServer   =   Portal . host ();       IntServer . on ( \"/\" ,   handleRoot );       Portal . onNotFound ( handleNotFound );      // For only onNotFound. \n   }  }  void   loop ()   {     Portal . host (). handleClient ();     Portal . handleRequest (); \n   /* or following one line code is equ.    Portal.handleClient();    */  }    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 or WebServer::begin  ESP8266WebServer/WebServer is already running inside the AutoConnect.",
+            "title": " Usage for automatically instantiated ESP8266WebServer/WebServer"
         },
         {
             "location": "/advancedusage/index.html#use-with-the-pagebuilder-library",
@@ -282,12 +282,12 @@
         },
         {
             "location": "/advancedusage/index.html#static-ip-assignment-1",
-            "text": "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:   IP address.  Gateway address.  Subnet mask.  Primary DNS server.  Secondary DNS server. (optional)   The above parameters must be executed before  AutoConnect::begin  as  arguments of AutoConnectConfig .  AutoConnect          portal ;  AutoConnectConfig    Config ;  Config . staip   =   IPAddress ( 192 , 168 , 1 , 10 );  Config . staGateway   =   IPAddress ( 192 , 168 , 1 , 1 );  Config . staNetmask   =   IPAddress ( 255 , 255 , 255 , 0 );  Config . dns1   =   IPAddress ( 192 , 168 , 1 , 1 );  portal . config ( Config );  portal . begin ();       Static IP address assignment is available from version 0.9.3.\u00a0 \u21a9",
+            "text": "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:   IP address.  Gateway address.  Subnet mask.  Primary DNS server.  Secondary DNS server. (optional)   The above parameters must be executed before  AutoConnect::begin  as  arguments of AutoConnectConfig .  AutoConnect          portal ;  AutoConnectConfig    Config ;  Config . staip   =   IPAddress ( 192 , 168 , 1 , 10 );  Config . staGateway   =   IPAddress ( 192 , 168 , 1 , 1 );  Config . staNetmask   =   IPAddress ( 255 , 255 , 255 , 0 );  Config . dns1   =   IPAddress ( 192 , 168 , 1 , 1 );  portal . config ( Config );  portal . begin ();       Static IP address assignment is available from version 0.9.3.\u00a0 \u21a9",
             "title": " Static IP assignment 1"
         },
         {
             "location": "/api/index.html",
-            "text": "Include headers\n\u00b6\n\n\n AutoConnect.h\n\u00b6\n\n\n#include\n \n<AutoConnect.h>\n\n\n\n\n\nDefine macros\n\u00b6\n\n\n#define AC_DEBUG                                \n// Monitor message output activation\n\n\n#define AC_DEBUG_PORT           Serial          \n// Default message output device\n\n\n#define AUTOCONNECT_AP_IP       0x01F4A8C0      \n// Default SoftAP IP\n\n\n#define AUTOCONNECT_AP_GW       0x01F4A8C0      \n// Default SoftAP Gateway IP\n\n\n#define AUTOCONNECT_AP_NM       0x00FFFFFF      \n// Default subnet mask\n\n\n#define AUTOCONNECT_DNSPORT     53              \n// Default DNS port at captive portal\n\n\n#define AUTOCONNECT_HTTPPORT    80              \n// Default HTTP\n\n\n#define AUTOCONNECT_MENU_TITLE  \"AutoConnect\"   \n// Default AutoConnect menu title\n\n\n#define AUTOCONNECT_STARTUPTIME 10              \n// Default waiting time[s] for after reset\n\n\n#define AUTOCONNECT_URI         \"/_ac\"          \n// Default AutoConnect root path\n\n\n#define AUTOCONNECT_TIMEOUT     30000           \n// Default connection timeout[ms]\n\n\n\n\n\nAutoConnect API\n\u00b6\n\n\n Constructors\n\u00b6\n\n\nAutoConnect\n\u00b6\n\n\nAutoConnect\n()\n\n\n\n\n\n\n\nAutoConnect default constructor. This entry internally allocates the ESP8266WebServer and is activated internally.\n\n\nAutoConnect\n(\nESP8266WebServer\n&\n \nwebServer\n)\n\n\n\n\n\nRun the AutoConnect site using the externally ensured ESP8266WebServer.\n\n\nThe \nhandleClient\n function of AutoConnect can include the response of the URI handler added by the user using the \"\non\n\" function of ESP8266WebServer. If ESP8266WebServer is assigned internally by AutoConnect, the sketch can obtain that reference with the \nhost\n function.\n\n\n    \nParameters\n\n    \nwebServer\nA reference of ESP8266WebServer instance.\n\n\n\n\n Public member functions\n\u00b6\n\n\nbegin\n\u00b6\n\n\nbool\n \nbegin\n()\n\n\n\n\nbool\n \nbegin\n(\nconst\n \nchar\n*\n \nssid\n,\n \nconst\n \nchar\n*\n \npassphraase\n)\n\n\n\n\nbool\n \nbegin\n(\nconst\n \nchar\n*\n \nssid\n,\n \nconst\n \nchar\n*\n \npassphraase\n,\n \nunsinged\n \nlong\n \ntimeout\n)\n\n\n\n\nStarts establishing the WiFi connection.\n\nAutoConnect first invokes \nWiFi.begin\n. If the case of SSID and Password missing, its \nWiFi.begin\n has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer will be started immediately after the first \nWiFi.beign\n regardless of the result.\n\n\nThe captive portal will not be started if the connection has been established with first \nWiFi.begin\n. If the connection cannot establish, switch to WIFI_AP_STA mode and activate SoftAP. Then DNS server starts.\n\n\n    \nParameters\n\n    \nssid\nSSID to be connected.\n\n    \npassphrase\nPassword for connection.\n\n    \ntimeout\nA time out value in milliseconds for waiting connection.\n\n    \nReturn value\n\n    \ntrue\nConnection established, AutoConnect service started with WIFI_STA mode.\n\n    \nfalse\nCould not connected, Captive portal started with WIFI_AP_STA mode.\n\n\n\n\nconfig\n\u00b6\n\n\nbool\n \nconfig\n(\nAutoConnectConfig\n&\n \nconfig\n)\n\n\n\n\nbool\n \nconfig\n(\nconst\n \nchar\n*\n \nap\n,\n \nconst\n \nchar\n*\n \npassword\n \n=\n \nnullptr\n)\n\n\n\n\nSet SoftAP's WiFi configuration and static IP configuration. \n\n\n    \nParameters\n\n    \nconfig\nReference to \nAutoConnectConfig\n containing SoftAP's parameters and static IP parameters.\n\n    \nap\nSSID for SoftAP. The default value is \nesp8266ap\n.\n\n    \npassword\nPassword for SodtAP. The default value is \n12345678\n.\n\n    \nReturn value\n\n    \ntrue\nSuccessfully configured.\n\n    \nfalse\nConfiguration parameter is invalid, some values out of range.\n\n\n\n\nend\n\u00b6\n\n\nvoid\n \nend\n()\n\n\n\n\n\nStops AutoConnect captive portal service. Release ESP8266WebServer and DNSServer. \n\n\n\n\nAttention to end\n\n\nThe end function releases the instance of ESP8266WebServer and DNSServer. It can not process them after the end function.\n\n\n\n\nhandleClient\n\u00b6\n\n\nvoid\n \nhandleClient\n()\n\n\n\n\n\nProcess 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 \nESP8266WebServer::handleClient\n.\n\n\nhandleRequest\n\u00b6\n\n\nvoid\n \nhandleRequest\n()\n\n\n\n\n\nHandling for the AutoConnect menu request.\n\n\n\n\nAbout used in combination with handleClient\n\n\nThe handleRequest function is not supposed to use with AutoConnect::handleClient. It should be used with ESP8266::handleClient.\n\n\n\n\nhome\n\u00b6\n\n\nvoid\n \nhome\n(\nString\n \nuri\n)\n\n\n\n\n\nPut a user site's home URI. The URI specified by home is linked from \"HOME\" in the AutoConnect menu.\n\n\n    \nParameters\n\n    \nuri\n A URI string of user site's home path.\n\n\n\n\nhost\n\u00b6\n\n\nReturns the reference of the ESP8266WebServer which is allocated in AutoConnect automatically.\n\n\nESP8266WebServer\n&\n \nhost\n()\n\n\n\n\n\n    \nReturn value\n\n    \nA reference of the ESP8266WebServer.\n\n\n\n\n\n\n&reference is not a pointer\n\n\nA reference cannot be re-assigned, and must be assigned at initialization. It's like as bind as alias.    \n\n\nESP8266WebServer\n&\n \nserver\n \n=\n \nportal\n.\nhost\n();\n\n\nserver\n.\nhandleClient\n();\n\n\n\nor\n\n\nportal\n.\nhost\n().\nhandleClient\n();\n\n\n\n\n\n\nonDetect\n\u00b6\n\n\nvoid\n \nonDetect\n(\nDetectExit_ft\n \nfn\n)\n\n\n\nRegister the function which will call from AutoConnect at the start of the captive portal.\n\n\n    \nParameters\n\n    \nfn\nFunction called at the captive portal start.\n\n\n\n\n\nAn \nfn\n specifies the function called when the captive portal starts. Its prototype declaration is defined as \"\nDetectExit_ft\n\".\n\n\ntypedef\n \nstd\n::\nfunction\n<\nbool\n(\nIPAddress\n \nsoftapIP\n)\n>\n  \nDetectExit_ft\n\n\n\n\n\n    \nParameters\n\n    \nsoftapIP\nAn IP address of SoftAP for the captive portal.\n\n    \nRetuen value\n\n    \ntrue\nContinues captive portal handling.\n\n    \nfalse\nCancel the captive portal. AutoConnect::begin function will return with a false.\n\n\n\n\nonNotFound\n\u00b6\n\n\nvoid\n \nonNotFound\n(\nESP8266WebServer\n::\nTHandlerFunction\n \nfn\n)\n\n\n\nRegister the handler function for undefined URL request detected.\n\n\n    \nParameters\n\n    \nfn\nA function of the \"not found\" handler.\n\n\n\n\nAutoConnectConfig API\n\u00b6\n\n\n Constructor\n\u00b6\n\n\nAutoConnectConfig\n\u00b6\n\n\nAutoConnectConfig\n();\n\n\n\n\nAutoConnectConfig\n(\nconst\n \nchar\n*\n \nap\n,\n \nconst\n \nchar\n*\n \npassword\n);\n\n\n\n\n\n    \nParameters\n\n    \nap\nSSID for SoftAP. The length should be up to 31. The default value is \nesp8266ap\n.\n\n    \npassword\nPassword for SodtAP. The length should be from 8 to up to 63. The default value is \n12345678\n.\n\n\n\n\n Public member variables\n\u00b6\n\n\napid\n\u00b6\n\n\nSoftAP's SSID.\n\n\n    \nType\n\n    \nString\n\n\n\n\napip\n\u00b6\n\n\nSets IP address for Soft AP in captive portal. When AutoConnect fails the initial WiFi.begin, it starts the captive portal with the IP address specified this.\n\n\n    \nType\n\n    \nIPAddress\nThe default value is \n192.168.244.1\n\n\n\n\nautoReconnect\n\u00b6\n\n\nAutomatically reconnect to past established access point (BSSID) when the current configured SSID in ESP8266 could not be connected. By enabling this option, \nAutoConnect::begin()\n function will attempt to reconnect to a known access point using credentials stored in the EEPROM, even if the connection failed by current SSID.\n\nIf the connection fails, starts the captive portal in SoftAP + STA mode.\n\n\n\n    \nType\n\n    \nbool\n\n    \nValue\n\n    \ntrue\nReconnect automatically.\n\n    \nfalse\nStarts Captive Portal in SoftAP + STA mode without trying to reconnect. This is the default.\n\n\n\n\nWhen the autoReconnect option is enabled, an automatic connection will behave if the following conditions are satisfied.\n\n\n\n\nInvokes \nAutoConnect::begin\n without user name and password parameter as \nbegin()\n.\n\n\nIf one of the saved BSSIDs (not the SSID) of the credentials matches the BSSID detected by the network scan.\n\n\n\n\nautoReset\n\u00b6\n\n\nReset ESP8266 module automatically after WLAN disconnected.\n\n\n    \nType\n\n    \nbool\n\n    \nValue\n\n    \ntrue\nReset after WiFi disconnected automatically.\n\n    \nfalse\nNo reset.\n\n\n\n\nautoRise\n\u00b6\n\n\nCaptive portal activation switch. False for disabling the captive portal. It prevents starting the captive portal even if the connection at the first \nWiFi.begin\n fails.\n\n\n    \nType\n\n    \nbool\n\n    \nValue\n\n    \ntrue\nEnable the captive portal. This is the default.\n\n    \nfalse\nDisable the captive portal.\n\n\n\n\nautoSave\n\u00b6\n\n\nThe credential saved automatically at the connection establishment.\n\n\n    \nType\n\n    \nAC_SAVECREDENTIAL_t\n\n    \nValue\n\n    \nAC_SAVECREDENTIAL_AUTO\nThe credential saved automatically. This is the default.\n\n    \nAC_SAVECREDENTIAL_NEVER\nThe credential no saved.\n\n\n\n\nboundaryOffset\n\u00b6\n\n\nSets the offset address of the credential storage area for EEPROM. This value must be between greater than 4 and less than flash sector size. (4096 by SDK)\n\nThe default value is 0.\n\n\n    \nType\n\n    \nuint16_t\n\n\n\n\n\n\nIt will conflict with user data.\n\n\nIf the sketch leaves this offset at zero, it will conflict the storage area of credentials with the user sketch owned data. It needs to use the behind of credential area.\n\n\n\n\nchannel\n\u00b6\n\n\nThe channel number of WIFi when SoftAP starts.\n\n\n    \nType\n\n    \nuint8_t\n\n    \nValue\n\n    \n1 ~ 14. The default value is 1.\n\n\n\n\n\n\nHow do I choose Channel\n\n\nEspressif Systems had announced the \napplication note\n about Wi-Fi channel selection.\n\n\n\n\ndns1\n\u00b6\n\n\nSet primary DNS server address when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\ndns2\n\u00b6\n\n\nSet secondary DNS server address when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\ngateway\n\u00b6\n\n\nSets gateway address for Soft AP in captive portal. When AutoConnect fails the initial WiFi.begin, it starts the captive portal with the IP address specified this.\n\n\n    \nType\n\n    \nIPAddress\nThe default value is \n192.168.244.1\n\n\n\n\nhidden\n\u00b6\n\n\nSets SoftAP to hidden SSID.\n\n\n    \nType\n\n    \nuint8_t\n\n    \nValue\n\n    \n0\nSSID will be appeared. This is the default.\n\n    \n1\nSSID will be hidden.\n\n\n\n\nhomeUri\n\u00b6\n\n\nSets the home path of user sketch. This path would be linked from 'HOME' in the AutoConnect menu.\n\n\n    \nType\n\n    \nString\n\n\n\n\nnetmask\n\u00b6\n\n\nSets subnet mask for Soft AP in captive portal. When AutoConnect fails the initial WiFi.begin, it starts the captive portal with the IP address specified this.\n\n\n    \nType\n\n    \nIPAddress\nThe default value is \n255.255.255.0\n\n\n\n\npsk\n\u00b6\n\n\nSets password for SoftAP. The length should be from 8 to up to 63. The default value is \n12345678\n.\n\n\n    \nType\n\n    \nString\n\n\n\n\nstaip\n\u00b6\n\n\nSet a static IP address. The IP will behave with STA mode.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\nstaGateway\n\u00b6\n\n\nSet the gateway address when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\nstaNetmask\n\u00b6\n\n\nSet the subnetmask when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\n AutoConnectConfig example\n\u00b6\n\n\nAutoConenct\n        \nPortal\n;\n\n\nAutoConenctConfig\n  \nConfig\n(\n\"\"\n,\n \n\"passpass\"\n);\n    \n// SoftAp name is determined at runtime\n\n\nConfig\n.\napid\n \n=\n \nESP\n.\nhostname\n();\n                 \n// Retrieve host name to SotAp identification\n\n\nConfig\n.\napip\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n101\n);\n      \n// Sets SoftAP IP address\n\n\nConfig\n.\ngateway\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n1\n);\n     \n// Sets WLAN router IP address\n\n\nConfig\n.\nnetmask\n \n=\n \nIPAddress\n(\n255\n,\n255\n,\n255\n,\n0\n);\n    \n// Sets WLAN scope\n\n\nConfig\n.\nautoReconnect\n \n=\n \ntrue\n;\n                  \n// Enable auto-reconnect\n\n\nConfig\n.\nautoSave\n \n=\n \nAC_SAVECREDENTIAL_NEVER\n;\n    \n// No save credential\n\n\nCOnfig\n.\nboundaryOffet\n \n=\n \n64\n;\n                    \n// Reserve 64 bytes for the user data in EEPROM. \n\n\nConfig\n.\nhomeUri\n \n=\n \n\"/index.html\"\n                \n// Sets home path of the sketch application\n\n\nConfig\n.\nstaip\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n10\n);\n      \n// Sets static IP\n\n\nConfig\n.\nstaGateway\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n1\n);\n  \n// Sets WiFi router address\n\n\nConfig\n.\nstaNetmask\n \n=\n \nIPAddress\n(\n255\n,\n255\n,\n255\n,\n0\n);\n \n// Sets WLAN scope\n\n\nConfig\n.\ndns1\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n1\n);\n        \n// Sets primary DNS address\n\n\nPortal\n.\nconfig\n(\nConfig\n);\n                        \n// Configure AutoConnect\n\n\nPortal\n.\nbegin\n();\n                               \n// Starts and behaves captive portal\n\n\n\n\n\n Something extra\n\u00b6\n\n\nThe library presents two PNG icons which can be used to embed a hyperlink to the AutoConnect menu.\n\n\n\n\nBar type \n\n\nCog type \n\n\n\n\nTo reference the icon, use the \nAUTOCONNECT_LINK\n macro in the sketch. It expands into the string literal as an HTML \n<a></a>\n tag with PNG embedded of the AutoConnect menu hyperlinks. Icon type is specified by the parameter of the macro.\n\n\n\n    \nBAR_24\nBars icon, 24x24.\n\n    \nBAR_32\nBars icon, 32x32.\n\n    \nBAR_48\nBars icon, 48x48.\n\n    \nCOG_24\nCog icon, 24x24.\n\n    \nCOG_32\nCog icon, 32x32.\n\n\n\n\n\n\n\nUsage\n\n\nString\n \nhtml\n \n=\n \n\"<html>\"\n;\n\n\nhtml\n \n+=\n \nAUTOCONNECT_LINK\n(\nBAR_32\n);\n\n\nhtml\n \n+=\n \n\"</html>\"\n;\n\n\nserver\n.\nsend\n(\n200\n,\n \n\"text/html\"\n,\n \nhtml\n);",
+            "text": "Include headers\n\u00b6\n\n\n AutoConnect.h\n\u00b6\n\n\n#include\n \n<AutoConnect.h>\n\n\n\n\n\nDefined macros\n\u00b6\n\n\n#define AC_DEBUG                                \n// Monitor message output activation\n\n\n#define AC_DEBUG_PORT           Serial          \n// Default message output device\n\n\n#define AUTOCONNECT_AP_IP       0x01F4A8C0      \n// Default SoftAP IP\n\n\n#define AUTOCONNECT_AP_GW       0x01F4A8C0      \n// Default SoftAP Gateway IP\n\n\n#define AUTOCONNECT_AP_NM       0x00FFFFFF      \n// Default subnet mask\n\n\n#define AUTOCONNECT_DNSPORT     53              \n// Default DNS port at captive portal\n\n\n#define AUTOCONNECT_HTTPPORT    80              \n// Default HTTP\n\n\n#define AUTOCONNECT_MENU_TITLE  \"AutoConnect\"   \n// Default AutoConnect menu title\n\n\n#define AUTOCONNECT_STARTUPTIME 10              \n// Default waiting time[s] for after reset\n\n\n#define AUTOCONNECT_URI         \"/_ac\"          \n// Default AutoConnect root path\n\n\n#define AUTOCONNECT_TIMEOUT     30000           \n// Default connection timeout[ms]\n\n\n\n\n\nAutoConnect API\n\u00b6\n\n\n Constructors\n\u00b6\n\n\nAutoConnect\n\u00b6\n\n\nAutoConnect\n()\n\n\n\n\n\n\n\nAutoConnect default constructor. This entry internally allocates the ESP8266WebServer for ESP8266 or WebServer for ESP32 and is activated internally.\n\n\n\n\nFor ESP8266\n\n\n\n\nAutoConnect\n(\nESP8266WebServer\n&\n \nwebServer\n)\n\n\n\n\n\n\n\nFor ESP32\n\n\n\n\nAutoConnect\n(\nWebServer\n&\n \nwebServer\n)\n\n\n\n\n\nRun the AutoConnect site using the externally ensured ESP8266WebServer for ESP8266 or WebServer for ESP32.\n\n\nThe \nhandleClient\n function of AutoConnect can include the response of the URI handler added by the user using the \"\non\n\" function of ESP8266WebServer/WebServer. If ESP8266WebServer/WebServer is assigned internally by AutoConnect, the sketch can obtain that reference with the \nhost\n function.\n\n\n    \nParameters\n\n    \nwebServer\nA reference of ESP8266WebServer or WebServer instance.\n\n\n\n\n Public member functions\n\u00b6\n\n\nbegin\n\u00b6\n\n\nbool\n \nbegin\n()\n\n\n\n\nbool\n \nbegin\n(\nconst\n \nchar\n*\n \nssid\n,\n \nconst\n \nchar\n*\n \npassphraase\n)\n\n\n\n\nbool\n \nbegin\n(\nconst\n \nchar\n*\n \nssid\n,\n \nconst\n \nchar\n*\n \npassphraase\n,\n \nunsigned\n \nlong\n \ntimeout\n)\n\n\n\n\nStarts establishing the WiFi connection.\n\nAutoConnect first invokes \nWiFi.begin\n. If the case of SSID and Password missing, its \nWiFi.begin\n has no SSID and Password. The WiFi mode at this time is WIFI_STA. Then ESP8266WebServer/WebServer will be started immediately after the first \nWiFi.begin\n regardless of the result.\n\n\nThe captive portal will not be started if the connection has been established with first \nWiFi.begin\n. If the connection cannot establish, switch to WIFI_AP_STA mode and activate SoftAP. Then DNS server starts.\n\n\n    \nParameters\n\n    \nssid\nSSID to be connected.\n\n    \npassphrase\nPassword for connection.\n\n    \ntimeout\nA time out value in milliseconds for waiting connection.\n\n    \nReturn value\n\n    \ntrue\nConnection established, AutoConnect service started with WIFI_STA mode.\n\n    \nfalse\nCould not connected, Captive portal started with WIFI_AP_STA mode.\n\n\n\n\nconfig\n\u00b6\n\n\nbool\n \nconfig\n(\nAutoConnectConfig\n&\n \nconfig\n)\n\n\n\n\nbool\n \nconfig\n(\nconst\n \nchar\n*\n \nap\n,\n \nconst\n \nchar\n*\n \npassword\n \n=\n \nnullptr\n)\n\n\n\n\nSet SoftAP's WiFi configuration and static IP configuration. \n\n\n    \nParameters\n\n    \nconfig\nReference to \nAutoConnectConfig\n containing SoftAP's parameters and static IP parameters.\n\n    \nap\nSSID for SoftAP. The default value is \nesp8266ap\n for ESP8266, \nesp32ap\n for ESP32.\n\n    \npassword\nPassword for SodtAP. The default value is \n12345678\n.\n\n    \nReturn value\n\n    \ntrue\nSuccessfully configured.\n\n    \nfalse\nConfiguration parameter is invalid, some values out of range.\n\n\n\n\nend\n\u00b6\n\n\nvoid\n \nend\n()\n\n\n\n\n\nStops AutoConnect captive portal service. Release ESP8266WebServer/WebServer and DNSServer. \n\n\n\n\nAttention to end\n\n\nThe end function releases the instance of ESP8266WebServer/WebServer and DNSServer. It can not process them after the end function.\n\n\n\n\nhandleClient\n\u00b6\n\n\nvoid\n \nhandleClient\n()\n\n\n\n\n\nProcess 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.\n\n\nhandleRequest\n\u00b6\n\n\nvoid\n \nhandleRequest\n()\n\n\n\n\n\nHandling for the AutoConnect menu request.\n\n\n\n\nAbout used in combination with handleClient\n\n\nThe handleRequest function is not supposed to use with AutoConnect::handleClient. It should be used with ESP8266WebServer::handleClient or WebServer::handleClient.\n\n\n\n\nhome\n\u00b6\n\n\nvoid\n \nhome\n(\nString\n \nuri\n)\n\n\n\n\n\nPut a user site's home URI. The URI specified by home is linked from \"HOME\" in the AutoConnect menu.\n\n\n    \nParameters\n\n    \nuri\n A URI string of user site's home path.\n\n\n\n\nhost\n\u00b6\n\n\nReturns the reference of the ESP8266WebServer/WebServer which is allocated in AutoConnect automatically.\n\n\n\n\nFor ESP8266\n\n\n\n\nESP8266WebServer\n&\n \nhost\n()\n\n\n\n\n\n\n\nFor ESP32\n\n\n\n\nWebServer\n&\n \nhost\n()\n\n\n\n\n\n    \nReturn value\n\n    \nA reference of the ESP8266WebServer/WebServer.\n\n\n\n\n\n\n&reference is not a pointer\n\n\nA reference cannot be re-assigned, and must be assigned at initialization. It's like as bind as alias.    \n\n\nESP8266WebServer\n&\n \nserver\n \n=\n \nportal\n.\nhost\n();\n\n\nserver\n.\nhandleClient\n();\n\n\n\nor\n\n\nportal\n.\nhost\n().\nhandleClient\n();\n\n\n\n\n\n\nonDetect\n\u00b6\n\n\nvoid\n \nonDetect\n(\nDetectExit_ft\n \nfn\n)\n\n\n\nRegister the function which will call from AutoConnect at the start of the captive portal.\n\n\n    \nParameters\n\n    \nfn\nFunction called at the captive portal start.\n\n\n\n\n\nAn \nfn\n specifies the function called when the captive portal starts. Its prototype declaration is defined as \"\nDetectExit_ft\n\".\n\n\ntypedef\n \nstd\n::\nfunction\n<\nbool\n(\nIPAddress\n \nsoftapIP\n)\n>\n  \nDetectExit_ft\n\n\n\n\n\n    \nParameters\n\n    \nsoftapIP\nAn IP address of SoftAP for the captive portal.\n\n    \nRetuen value\n\n    \ntrue\nContinues captive portal handling.\n\n    \nfalse\nCancel the captive portal. AutoConnect::begin function will return with a false.\n\n\n\n\nonNotFound\n\u00b6\n\n\n\n\nFor ESP8266\n\n\n\n\nvoid\n \nonNotFound\n(\nESP8266WebServer\n::\nTHandlerFunction\n \nfn\n)\n\n\n\n\n\n\n\nFor ESP32\n\n\n\n\nvoid\n \nonNotFound\n(\nWebServer\n::\nTHandlerFunction\n \nfn\n)\n\n\n\nRegister the handler function for undefined URL request detected.\n\n\n    \nParameters\n\n    \nfn\nA function of the \"not found\" handler.\n\n\n\n\nAutoConnectConfig API\n\u00b6\n\n\n Constructor\n\u00b6\n\n\nAutoConnectConfig\n\u00b6\n\n\nAutoConnectConfig\n();\n\n\n\n\nAutoConnectConfig\n(\nconst\n \nchar\n*\n \nap\n,\n \nconst\n \nchar\n*\n \npassword\n);\n\n\n\n\n\n    \nParameters\n\n    \nap\nSSID for SoftAP. The length should be up to 31. The default value is \nesp8266ap\n for ESP8266, \nesp32ap\n for ESP32.\n\n    \npassword\nPassword for SodtAP. The length should be from 8 to up to 63. The default value is \n12345678\n.\n\n\n\n\n Public member variables\n\u00b6\n\n\napid\n\u00b6\n\n\nSoftAP's SSID.\n\n\n    \nType\n\n    \nString\n\n\n\n\napip\n\u00b6\n\n\nSets IP address for Soft AP in captive portal. When AutoConnect fails the initial WiFi.begin, it starts the captive portal with the IP address specified this.\n\n\n    \nType\n\n    \nIPAddress\nThe default value is \n192.168.244.1\n\n\n\n\nautoReconnect\n\u00b6\n\n\nAutomatically 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, \nAutoConnect::begin()\n function will attempt to reconnect to a known access point using credentials stored in the EEPROM, even if the connection failed by current SSID.\n\nIf the connection fails, starts the captive portal in SoftAP + STA mode.\n\n\n\n    \nType\n\n    \nbool\n\n    \nValue\n\n    \ntrue\nReconnect automatically.\n\n    \nfalse\nStarts Captive Portal in SoftAP + STA mode without trying to reconnect. This is the default.\n\n\n\n\nWhen the autoReconnect option is enabled, an automatic connection will behave if the following conditions are satisfied.\n\n\n\n\nInvokes \nAutoConnect::begin\n without user name and password parameter as \nbegin()\n.\n\n\nIf one of the saved BSSIDs (not the SSID) of the credentials matches the BSSID detected by the network scan.\n\n\n\n\nautoReset\n\u00b6\n\n\nReset ESP8266 module automatically after WLAN disconnected.\n\n\n    \nType\n\n    \nbool\n\n    \nValue\n\n    \ntrue\nReset after WiFi disconnected automatically.\n\n    \nfalse\nNo reset.\n\n\n\n\nautoRise\n\u00b6\n\n\nCaptive portal activation switch. False for disabling the captive portal. It prevents starting the captive portal even if the connection at the first \nWiFi.begin\n fails.\n\n\n    \nType\n\n    \nbool\n\n    \nValue\n\n    \ntrue\nEnable the captive portal. This is the default.\n\n    \nfalse\nDisable the captive portal.\n\n\n\n\nautoSave\n\u00b6\n\n\nThe credential saved automatically at the connection establishment.\n\n\n    \nType\n\n    \nAC_SAVECREDENTIAL_t\n\n    \nValue\n\n    \nAC_SAVECREDENTIAL_AUTO\nThe credential saved automatically. This is the default.\n\n    \nAC_SAVECREDENTIAL_NEVER\nThe credential no saved.\n\n\n\n\nboundaryOffset\n\u00b6\n\n\nSets the offset address of the credential storage area for EEPROM. This value must be between greater than 4 and less than flash sector size. (4096 by SDK)\n\nThe default value is 0.\n\n\n    \nType\n\n    \nuint16_t\n\n\n\n\n\n\nIt will conflict with user data.\n\n\nIf the sketch leaves this offset at zero, it will conflict the storage area of credentials with the user sketch owned data. It needs to use the behind of credential area.\n\n\n\n\nchannel\n\u00b6\n\n\nThe channel number of WIFi when SoftAP starts.\n\n\n    \nType\n\n    \nuint8_t\n\n    \nValue\n\n    \n1 ~ 14. The default value is 1.\n\n\n\n\n\n\nHow do I choose Channel\n\n\nEspressif Systems had announced the \napplication note\n about Wi-Fi channel selection.\n\n\n\n\ndns1\n\u00b6\n\n\nSet primary DNS server address when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\ndns2\n\u00b6\n\n\nSet secondary DNS server address when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\ngateway\n\u00b6\n\n\nSets gateway address for Soft AP in captive portal. When AutoConnect fails the initial WiFi.begin, it starts the captive portal with the IP address specified this.\n\n\n    \nType\n\n    \nIPAddress\nThe default value is \n192.168.244.1\n\n\n\n\nhidden\n\u00b6\n\n\nSets SoftAP to hidden SSID.\n\n\n    \nType\n\n    \nuint8_t\n\n    \nValue\n\n    \n0\nSSID will be appeared. This is the default.\n\n    \n1\nSSID will be hidden.\n\n\n\n\nhomeUri\n\u00b6\n\n\nSets the home path of user sketch. This path would be linked from 'HOME' in the AutoConnect menu.\n\n\n    \nType\n\n    \nString\n\n\n\n\nnetmask\n\u00b6\n\n\nSets subnet mask for Soft AP in captive portal. When AutoConnect fails the initial WiFi.begin, it starts the captive portal with the IP address specified this.\n\n\n    \nType\n\n    \nIPAddress\nThe default value is \n255.255.255.0\n\n\n\n\npsk\n\u00b6\n\n\nSets password for SoftAP. The length should be from 8 to up to 63. The default value is \n12345678\n.\n\n\n    \nType\n\n    \nString\n\n\n\n\nstaip\n\u00b6\n\n\nSet a static IP address. The IP will behave with STA mode.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\nstaGateway\n\u00b6\n\n\nSet the gateway address when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\nstaNetmask\n\u00b6\n\n\nSet the subnetmask when using static IP address.\n\n\n    \nType\n\n    \nIPAddress\n\n\n\n\n AutoConnectConfig example\n\u00b6\n\n\nAutoConenct\n        \nPortal\n;\n\n\nAutoConenctConfig\n  \nConfig\n(\n\"\"\n,\n \n\"passpass\"\n);\n    \n// SoftAp name is determined at runtime\n\n\nConfig\n.\napid\n \n=\n \nESP\n.\nhostname\n();\n                 \n// Retrieve host name to SotAp identification\n\n\nConfig\n.\napip\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n101\n);\n      \n// Sets SoftAP IP address\n\n\nConfig\n.\ngateway\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n1\n);\n     \n// Sets WLAN router IP address\n\n\nConfig\n.\nnetmask\n \n=\n \nIPAddress\n(\n255\n,\n255\n,\n255\n,\n0\n);\n    \n// Sets WLAN scope\n\n\nConfig\n.\nautoReconnect\n \n=\n \ntrue\n;\n                  \n// Enable auto-reconnect\n\n\nConfig\n.\nautoSave\n \n=\n \nAC_SAVECREDENTIAL_NEVER\n;\n    \n// No save credential\n\n\nCOnfig\n.\nboundaryOffet\n \n=\n \n64\n;\n                    \n// Reserve 64 bytes for the user data in EEPROM. \n\n\nConfig\n.\nhomeUri\n \n=\n \n\"/index.html\"\n                \n// Sets home path of the sketch application\n\n\nConfig\n.\nstaip\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n10\n);\n      \n// Sets static IP\n\n\nConfig\n.\nstaGateway\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n1\n);\n  \n// Sets WiFi router address\n\n\nConfig\n.\nstaNetmask\n \n=\n \nIPAddress\n(\n255\n,\n255\n,\n255\n,\n0\n);\n \n// Sets WLAN scope\n\n\nConfig\n.\ndns1\n \n=\n \nIPAddress\n(\n192\n,\n168\n,\n10\n,\n1\n);\n        \n// Sets primary DNS address\n\n\nPortal\n.\nconfig\n(\nConfig\n);\n                        \n// Configure AutoConnect\n\n\nPortal\n.\nbegin\n();\n                               \n// Starts and behaves captive portal\n\n\n\n\n\n Something extra\n\u00b6\n\n\nThe library presents two PNG icons which can be used to embed a hyperlink to the AutoConnect menu.\n\n\n\n\nBar type \n\n\nCog type \n\n\n\n\nTo reference the icon, use the \nAUTOCONNECT_LINK\n macro in the sketch. It expands into the string literal as an HTML \n<a></a>\n tag with PNG embedded of the AutoConnect menu hyperlinks. Icon type is specified by the parameter of the macro.\n\n\n\n    \nBAR_24\nBars icon, 24x24.\n\n    \nBAR_32\nBars icon, 32x32.\n\n    \nBAR_48\nBars icon, 48x48.\n\n    \nCOG_24\nCog icon, 24x24.\n\n    \nCOG_32\nCog icon, 32x32.\n\n\n\n\n\n\n\nUsage\n\n\nString\n \nhtml\n \n=\n \n\"<html>\"\n;\n\n\nhtml\n \n+=\n \nAUTOCONNECT_LINK\n(\nBAR_32\n);\n\n\nhtml\n \n+=\n \n\"</html>\"\n;\n\n\nserver\n.\nsend\n(\n200\n,\n \n\"text/html\"\n,\n \nhtml\n);",
             "title": "Library APIs"
         },
         {
@@ -301,9 +301,9 @@
             "title": " AutoConnect.h"
         },
         {
-            "location": "/api/index.html#define-macros",
+            "location": "/api/index.html#defined-macros",
             "text": "#define AC_DEBUG                                 // Monitor message output activation  #define AC_DEBUG_PORT           Serial           // Default message output device  #define AUTOCONNECT_AP_IP       0x01F4A8C0       // Default SoftAP IP  #define AUTOCONNECT_AP_GW       0x01F4A8C0       // Default SoftAP Gateway IP  #define AUTOCONNECT_AP_NM       0x00FFFFFF       // Default subnet mask  #define AUTOCONNECT_DNSPORT     53               // Default DNS port at captive portal  #define AUTOCONNECT_HTTPPORT    80               // Default HTTP  #define AUTOCONNECT_MENU_TITLE  \"AutoConnect\"    // Default AutoConnect menu title  #define AUTOCONNECT_STARTUPTIME 10               // Default waiting time[s] for after reset  #define AUTOCONNECT_URI         \"/_ac\"           // Default AutoConnect root path  #define AUTOCONNECT_TIMEOUT     30000            // Default connection timeout[ms]",
-            "title": "Define macros"
+            "title": "Defined macros"
         },
         {
             "location": "/api/index.html#autoconnect-api",
@@ -317,7 +317,7 @@
         },
         {
             "location": "/api/index.html#autoconnect",
-            "text": "AutoConnect ()    AutoConnect default constructor. This entry internally allocates the ESP8266WebServer 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. \n     Parameters \n     webServer A reference of ESP8266WebServer instance.",
+            "text": "AutoConnect ()    AutoConnect default constructor. This entry internally allocates the ESP8266WebServer for ESP8266 or WebServer for ESP32 and is activated internally.   For ESP8266   AutoConnect ( ESP8266WebServer &   webServer )    For ESP32   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. \n     Parameters \n     webServer A reference of ESP8266WebServer or WebServer instance.",
             "title": "AutoConnect"
         },
         {
@@ -327,27 +327,27 @@
         },
         {
             "location": "/api/index.html#begin",
-            "text": "bool   begin ()   bool   begin ( const   char *   ssid ,   const   char *   passphraase )   bool   begin ( const   char *   ssid ,   const   char *   passphraase ,   unsinged   long   timeout )   Starts establishing the WiFi connection. \nAutoConnect 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. \n     Parameters \n     ssid SSID to be connected. \n     passphrase Password for connection. \n     timeout A time out value in milliseconds for waiting connection. \n     Return value \n     true Connection established, AutoConnect service started with WIFI_STA mode. \n     false Could not connected, Captive portal started with WIFI_AP_STA mode.",
+            "text": "bool   begin ()   bool   begin ( const   char *   ssid ,   const   char *   passphraase )   bool   begin ( const   char *   ssid ,   const   char *   passphraase ,   unsigned   long   timeout )   Starts establishing the WiFi connection. \nAutoConnect 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. \n     Parameters \n     ssid SSID to be connected. \n     passphrase Password for connection. \n     timeout A time out value in milliseconds for waiting connection. \n     Return value \n     true Connection established, AutoConnect service started with WIFI_STA mode. \n     false Could not connected, Captive portal started with WIFI_AP_STA mode.",
             "title": "begin"
         },
         {
             "location": "/api/index.html#config",
-            "text": "bool   config ( AutoConnectConfig &   config )   bool   config ( const   char *   ap ,   const   char *   password   =   nullptr )   Set SoftAP's WiFi configuration and static IP configuration.  \n     Parameters \n     config Reference to  AutoConnectConfig  containing SoftAP's parameters and static IP parameters. \n     ap SSID for SoftAP. The default value is  esp8266ap . \n     password Password for SodtAP. The default value is  12345678 . \n     Return value \n     true Successfully configured. \n     false Configuration parameter is invalid, some values out of range.",
+            "text": "bool   config ( AutoConnectConfig &   config )   bool   config ( const   char *   ap ,   const   char *   password   =   nullptr )   Set SoftAP's WiFi configuration and static IP configuration.  \n     Parameters \n     config Reference to  AutoConnectConfig  containing SoftAP's parameters and static IP parameters. \n     ap SSID for SoftAP. The default value is  esp8266ap  for ESP8266,  esp32ap  for ESP32. \n     password Password for SodtAP. The default value is  12345678 . \n     Return value \n     true Successfully configured. \n     false Configuration parameter is invalid, some values out of range.",
             "title": "config"
         },
         {
             "location": "/api/index.html#end",
-            "text": "void   end ()   Stops AutoConnect captive portal service. Release ESP8266WebServer and DNSServer.    Attention to end  The end function releases the instance of ESP8266WebServer and DNSServer. It can not process them after the end function.",
+            "text": "void   end ()   Stops AutoConnect captive portal service. Release ESP8266WebServer/WebServer and DNSServer.    Attention to end  The end function releases the instance of ESP8266WebServer/WebServer and DNSServer. It can not process them after the end function.",
             "title": "end"
         },
         {
             "location": "/api/index.html#handleclient",
-            "text": "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 .",
+            "text": "void   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.",
             "title": "handleClient"
         },
         {
             "location": "/api/index.html#handlerequest",
-            "text": "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.",
+            "text": "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 ESP8266WebServer::handleClient or WebServer::handleClient.",
             "title": "handleRequest"
         },
         {
@@ -357,7 +357,7 @@
         },
         {
             "location": "/api/index.html#host",
-            "text": "Returns the reference of the ESP8266WebServer which is allocated in AutoConnect automatically.  ESP8266WebServer &   host ()   \n     Return value \n     A reference of the ESP8266WebServer.    &reference is not a pointer  A reference cannot be re-assigned, and must be assigned at initialization. It's like as bind as alias.      ESP8266WebServer &   server   =   portal . host ();  server . handleClient ();  \nor  portal . host (). handleClient ();",
+            "text": "Returns the reference of the ESP8266WebServer/WebServer which is allocated in AutoConnect automatically.   For ESP8266   ESP8266WebServer &   host ()    For ESP32   WebServer &   host ()   \n     Return value \n     A reference of the ESP8266WebServer/WebServer.    &reference is not a pointer  A reference cannot be re-assigned, and must be assigned at initialization. It's like as bind as alias.      ESP8266WebServer &   server   =   portal . host ();  server . handleClient ();  \nor  portal . host (). handleClient ();",
             "title": "host"
         },
         {
@@ -367,7 +367,7 @@
         },
         {
             "location": "/api/index.html#onnotfound",
-            "text": "void   onNotFound ( ESP8266WebServer :: THandlerFunction   fn )  \nRegister the handler function for undefined URL request detected. \n     Parameters \n     fn A function of the \"not found\" handler.",
+            "text": "For ESP8266   void   onNotFound ( ESP8266WebServer :: THandlerFunction   fn )    For ESP32   void   onNotFound ( WebServer :: THandlerFunction   fn )  \nRegister the handler function for undefined URL request detected. \n     Parameters \n     fn A function of the \"not found\" handler.",
             "title": "onNotFound"
         },
         {
@@ -382,7 +382,7 @@
         },
         {
             "location": "/api/index.html#autoconnectconfig",
-            "text": "AutoConnectConfig ();   AutoConnectConfig ( const   char *   ap ,   const   char *   password );   \n     Parameters \n     ap SSID for SoftAP. The length should be up to 31. The default value is  esp8266ap . \n     password Password for SodtAP. The length should be from 8 to up to 63. The default value is  12345678 .",
+            "text": "AutoConnectConfig ();   AutoConnectConfig ( const   char *   ap ,   const   char *   password );   \n     Parameters \n     ap SSID for SoftAP. The length should be up to 31. The default value is  esp8266ap  for ESP8266,  esp32ap  for ESP32. \n     password Password for SodtAP. The length should be from 8 to up to 63. The default value is  12345678 .",
             "title": "AutoConnectConfig"
         },
         {
@@ -402,7 +402,7 @@
         },
         {
             "location": "/api/index.html#autoreconnect",
-            "text": "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. \nIf the connection fails, starts the captive portal in SoftAP + STA mode.  \n     Type \n     bool \n     Value \n     true Reconnect automatically. \n     false Starts Captive Portal in SoftAP + STA mode without trying to reconnect. This is the default.   When the autoReconnect option is enabled, an automatic connection will behave if the following conditions are satisfied.   Invokes  AutoConnect::begin  without user name and password parameter as  begin() .  If one of the saved BSSIDs (not the SSID) of the credentials matches the BSSID detected by the network scan.",
+            "text": "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. \nIf the connection fails, starts the captive portal in SoftAP + STA mode.  \n     Type \n     bool \n     Value \n     true Reconnect automatically. \n     false Starts Captive Portal in SoftAP + STA mode without trying to reconnect. This is the default.   When the autoReconnect option is enabled, an automatic connection will behave if the following conditions are satisfied.   Invokes  AutoConnect::begin  without user name and password parameter as  begin() .  If one of the saved BSSIDs (not the SSID) of the credentials matches the BSSID detected by the network scan.",
             "title": "autoReconnect"
         },
         {
@@ -647,9 +647,14 @@
         },
         {
             "location": "/changelog/index.html",
-            "text": "[0.9.4] May 5, 2018.\n\u00b6\n\n\n\n\nAutomatically focus passphrase after selecting SSID with Configure New AP.\n\n\nSupports 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.\n\n\n\n\n[0.9.3] March 23, 2018.\n\u00b6\n\n\n\n\nSupports a static IP address assignment.\n\n\n\n\n[0.9.2] March 19, 2018.\n\u00b6\n\n\n\n\nImprovement of string literal declaration with the examples, no library change.\n\n\n\n\n[0.9.1] March 13, 2018.\n\u00b6\n\n\n\n\nA release of the stable.",
+            "text": "[0.9.5] Aug.27, 2018.\n\u00b6\n\n\n\n\nSupports ESP32.\n\n\nFixed that crash may occur if the number of stored credentials in the EEPROM is smaller than the number of found WiFi networks.\n\n\n\n\n[0.9.4] May 5, 2018.\n\u00b6\n\n\n\n\nAutomatically focus passphrase after selecting SSID with Configure New AP.\n\n\nSupports 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.\n\n\n\n\n[0.9.3] March 23, 2018.\n\u00b6\n\n\n\n\nSupports a static IP address assignment.\n\n\n\n\n[0.9.2] March 19, 2018.\n\u00b6\n\n\n\n\nImprovement of string literal declaration with the examples, no library change.\n\n\n\n\n[0.9.1] March 13, 2018.\n\u00b6\n\n\n\n\nA release of the stable.",
             "title": "Change log"
         },
+        {
+            "location": "/changelog/index.html#095-aug27-2018",
+            "text": "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.",
+            "title": "[0.9.5] Aug.27, 2018."
+        },
         {
             "location": "/changelog/index.html#094-may-5-2018",
             "text": "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/sitemap.xml b/docs/sitemap.xml
index c3e0291..2a6ed8c 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -4,7 +4,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -12,7 +12,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//gettingstarted/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -20,7 +20,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//menu/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -28,7 +28,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//basicusage/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -36,7 +36,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//advancedusage/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -44,7 +44,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//api/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -52,7 +52,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//examples/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -60,7 +60,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//faq/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -68,7 +68,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//changelog/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -76,7 +76,7 @@
     
     <url>
      <loc>https://Hieromon.github.io/AutoConnect//license/index.html</loc>
-     <lastmod>2018-05-06</lastmod>
+     <lastmod>2018-09-14</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
diff --git a/examples/mqttRSSI/mqttRSSI.ino b/examples/mqttRSSI/mqttRSSI.ino
index 052347a..5bf7eba 100644
--- a/examples/mqttRSSI/mqttRSSI.ino
+++ b/examples/mqttRSSI/mqttRSSI.ino
@@ -74,6 +74,17 @@ void mqttPublish(String msg) {
   mqttClient.publish(topic, payload);
 }
 
+int getStrength(uint8_t points) {
+  uint8_t sc = points;
+  long    rssi = 0;
+
+  while (sc--) {
+    rssi += WiFi.RSSI();
+    delay(20);
+  }
+  return points ? (int)(rssi / points) : 0;
+}
+
 unsigned long   lastPub = 0;
 
 void setup() {
@@ -100,7 +111,7 @@ void loop() {
     if (!mqttClient.connected()) {
       mqttConnect();
     }
-    String item = String("field1=") + String(WiFi.RSSI());
+    String item = String("field1=") + String(getStrength(7));
     mqttPublish(item);
     mqttClient.loop();
     lastPub = millis();
diff --git a/mkdocs/api.md b/mkdocs/api.md
index c812493..1284533 100644
--- a/mkdocs/api.md
+++ b/mkdocs/api.md
@@ -6,7 +6,7 @@
 #include <AutoConnect.h>
 ```
 
-#### Define macros
+#### Defined macros
 
 ```cpp
 #define AC_DEBUG                                // Monitor message output activation
@@ -34,18 +34,26 @@ AutoConnect()
 
 <a id="withparameter"></a>
 
-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.
+
+- For ESP8266
 
 ```cpp
 AutoConnect(ESP8266WebServer& webServer)
 ```
 
-Run the AutoConnect site using the externally ensured ESP8266WebServer.
+- For ESP32
+
+```cpp
+AutoConnect(WebServer& webServer)
+```
+
+Run the AutoConnect site using the externally ensured ESP8266WebServer for ESP8266 or WebServer for ESP32.
 
-The [**handleClient**](api.md#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**](api.me#host) function.
+The [**handleClient**](api.md#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**](api.me#host) function.
 <dl class="apidl">
     <dt>**Parameters**</dt>
-    <dd><span class="apidef">webServer</span>A reference of ESP8266WebServer instance.</dd>
+    <dd><span class="apidef">webServer</span>A reference of ESP8266WebServer or WebServer instance.</dd>
 </dl>
 
 ### <i class="fa fa-code"></i> Public member functions
@@ -59,11 +67,11 @@ bool begin()
 bool begin(const char* ssid, const char* passphraase)
 ```  
 ```cpp
-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.
 <dl class="apidl">
@@ -89,7 +97,7 @@ Set SoftAP's WiFi configuration and static IP configuration.
 <dl class="apidl">
     <dt>**Parameters**</dt>
     <dd><span class="apidef">config</span>Reference to [**AutoConnectConfig**](api.md#autoconnectconfig) containing SoftAP's parameters and static IP parameters.</dd>
-    <dd><span class="apidef">ap</span>SSID for SoftAP. The default value is **esp8266ap**.</dd>
+    <dd><span class="apidef">ap</span>SSID for SoftAP. The default value is **esp8266ap** for ESP8266, **esp32ap** for ESP32.</dd>
     <dd><span class="apidef">password</span>Password for SodtAP. The default value is **12345678**.</dd>
     <dt>**Return value**</dt>
     <dd><span class="apidef">true</span>Successfully configured.</dd>
@@ -102,10 +110,10 @@ Set SoftAP's WiFi configuration and static IP configuration.
 void end()
 ```
 
-Stops AutoConnect captive portal service. Release ESP8266WebServer and DNSServer. 
+Stops AutoConnect captive portal service. Release ESP8266WebServer/WebServer and DNSServer. 
 
 !!! warning "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.
 
 #### handleClient
 
@@ -113,7 +121,7 @@ Stops AutoConnect captive portal service. Release ESP8266WebServer and DNSServer
 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.
 
 #### handleRequest
 
@@ -124,7 +132,7 @@ void handleRequest()
 Handling for the AutoConnect menu request.
 
 !!! warning "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.
 
 #### home
 
@@ -140,14 +148,22 @@ Put a user site's home URI. The URI specified by home is linked from "HOME" in t
 
 #### host
 
-Returns the reference of the ESP8266WebServer which is allocated in AutoConnect automatically.
+Returns the reference of the ESP8266WebServer/WebServer which is allocated in AutoConnect automatically.
+
+- For ESP8266
 
 ```cpp
 ESP8266WebServer& host()
 ```
+
+- For ESP32
+
+```cpp
+WebServer& host()
+```
 <dl class="apidl">
     <dt>**Return value**</dt>
-    <dd>A reference of the ESP8266WebServer.</dd>
+    <dd>A reference of the ESP8266WebServer/WebServer.</dd>
 </dl>
 
 !!! note "&reference is not a pointer"
@@ -188,9 +204,17 @@ typedef std::function<bool(IPAddress softapIP)>  DetectExit_ft
 
 #### onNotFound
 
+- For ESP8266
+
 ```cpp
 void onNotFound(ESP8266WebServer::THandlerFunction fn)
 ```
+
+- For ESP32
+
+```cpp
+void onNotFound(WebServer::THandlerFunction fn)
+```
 Register the handler function for undefined URL request detected.
 <dl class="apidl">
     <dt>**Parameters**</dt>
@@ -211,7 +235,7 @@ AutoConnectConfig(const char* ap, const char* password);
 ```
 <dl class="apidl">
     <dt>**Parameters**</dt>
-    <dd><span class="apidef">ap</span>SSID for SoftAP. The length should be up to 31. The default value is **esp8266ap**.</dd>
+    <dd><span class="apidef">ap</span>SSID for SoftAP. The length should be up to 31. The default value is **esp8266ap** for ESP8266, **esp32ap** for ESP32.</dd>
     <dd><span class="apidef">password</span>Password for SodtAP. The length should be from 8 to up to 63. The default value is **12345678**.</dd>
 </dl>
 
@@ -234,7 +258,7 @@ Sets IP address for Soft AP in captive portal. When AutoConnect fails the initia
 
 #### autoReconnect
 
-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.  
 <dl class="apidl">
     <dt>**Type**</dt>
diff --git a/mkdocs/changelog.md b/mkdocs/changelog.md
index bde1c6d..6369f35 100644
--- a/mkdocs/changelog.md
+++ b/mkdocs/changelog.md
@@ -1,3 +1,8 @@
+#### [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.