wirtz
/
AutoConnect
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
28 Commits
3 Branches
19 Tags
22 MiB
 
 
 
 
 
Tag: Branch: Tree: 7eb7d2bd61
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7eb7d2bd61'
${ noResults }
AutoConnect/mkdocs/basicusage.md

7.6 KiB
Raw Blame History

Simple usage

Embed to the sketches

How embed the AutoConnect to the sketches you have. Most simple approach to applying AutoConnect for the existing sketches, follow the below steps.

  • Insert #include <AutoConnect.h> to behind of #include <ESP8266WebServer.h>.
  • Insert AutoConnect PORTAL(WEBSERVER); to behind of ESP8266WebServer WEBSERVER; declaration.1
  • Remove WiFi.begin(SSID,PSK) and the subsequent logic for the connection status check.
  • Replace WEBSERVER.begin() to PORTAL.begin().2
  • Replace WEBSERVER.handleClient() to PORTAL.handleClient().3
  • If the connection checks logic is needed, you can check the return value according to PORTAL.begin() with true or false.

Each VARIABLE conforms to the actual declaration in the sketches.

WiFi SSID and Password can be specified AutoConnect::begin() too.

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.

Basic usage

Basic logic sequence for the user sketches

1. A typical logic sequence

!!! note "" 1. Include headers, ESP8266WebServer.h and AutoConnect.h
2. Declare ESP8266WebServer variable.
3. Declare AutoConnect variable.
4. Implements the URL handler function().
5. setup()
5.1 Sets URL handler function() to ESP8266WebServer byESP8266WebServer::on.
5.2 Starts AutoConnect::begin().
5.3 Check connection status.
6. loop()
6.1 Invokes AutoConnect::handleClient(),
or invokes ESP8266WebServer::handleClient() then AutoConnect::handleRequest().
6.2 Do the process for actual sketch.

2. Declare AutoConnect object

Two options are available for AutoConnect constructor.

AutoConnect VARIABLE(&ESP8266WebServer);

or

AutoConnect VARIABLE;

  • Parameter with ESP8266WebServer variable: An ESP8266WebServer object variable must be declared in the sketch. AutoConnect uses its variable for handling the AutoConnect menu.

  • With no parameter: The sketch does not declare ESP8266WebServer object. In this case, AutoConnect allocates an instance of the ESP8266WebServer internally and 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.

3. No need WiFI.begin(...)

AutoConnect performs WiFi.begin for establishing a connection with WLAN internally. There is no need for a general process to establish a connection with WiFi.begin in a sketch.

4. Alternate ESP8266WebServer::begin()

AutoConnect::begin internally executes ESP8266WebServer::begin too and it starts DNS server to behave as a captive portal. So the sketch does not need to call ESP8266WebServer::begin.

!!! info "Why DNS Server Starts" AutoConnect traps the detection of captive portals and directs them to the AutoConnect menu to achieve a connection with the WLAN interactively. In order to trap, it temporarily responds SoftAP address to all DNS queries. When the connection with the WLAN is successfully established, the DNS server will stop.

5. AutoConnect::begin with SSID and Password

SSID and Password can also specify by AutoConnect::begin. ESP8266 uses provided SSID and Password explicitly. If the connection false with specified SSID with Password then a captive portal is activated. SSID and Password are not present, ESP8266 SDK will attempt to connect using the still effectual SSID and password. Usually, it succeeds.

6. Use ESP8266WebServer::on to handle URL

AutoConnect is designed to coexist with the process for handling the web pages by user sketches. The page processing function which will send an HTML to the client invoked by the "on::ESP8266WebServer" function is the same as when using ESP8266WebServer natively.

7. Use either ESP8266WebServer::handleClient() or AutoConnect::handleClient()

Both classes member function name is the same: handleClient, but behavior is different. Using the AutoConnect embedded along with ESP8266WebServer::handleClient has limitations. Refer to the below section for details.

ESP8266WebServer hosted or parasitic

The interoperable process with an ESP8266WebServer depends on the parameters of the AutoConnect constructor.

Declaration parameter Use ESP8266WebServer::handleClient Use AutoConnect::handleClient
None AutoConnect menu not available.
host() is needed.		 AutoConnect menu available.
host() is needed.
Reference to ESP8266WebServer AutoConnect menu not available.
host() not necessary.		 AutoConnect menu available.
host() not necessary.

  • 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.

!!! info "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.