基于Arduino+Blynk+ESP8266设计的WiFi遥控小车（皆可应用在毕设/课设/大作业/实训/竞赛/项目开发）

## Current development going on here :arrow_right: [Development Branch](https://github.com/tzapu/WiFiManager/tree/development) # WiFiManager ESP8266 WiFi Connection manager with fallback web configuration portal [](https://travis-ci.org/tzapu/WiFiManager) The configuration portal is of the captive variety, so on various devices it will present the configuration dialogue as soon as you connect to the created access point. First attempt at a library. Lots more changes and fixes to do. Contributions are welcome. #### This works with the ESP8266 Arduino platform with a recent stable release(2.0.0 or newer) https://github.com/esp8266/Arduino ## Contents - [How it works](#how-it-works) - [Wishlist](#wishlist) - [Quick start](#quick-start) - Installing - [Through Library Manager](#install-through-library-manager) - [From Github](#checkout-from-github) - [Using](#using) - [Documentation](#documentation) - [Access Point Password](#password-protect-the-configuration-access-point) - [Callbacks](#callbacks) - [Configuration Portal Timeout](#configuration-portal-timeout) - [On Demand Configuration](#on-demand-configuration-portal) - [Custom Parameters](#custom-parameters) - [Custom IP Configuration](#custom-ip-configuration) - [Filter Low Quality Networks](#filter-networks) - [Debug Output](#debug) - [Troubleshooting](#troubleshooting) - [Releases](#releases) - [Contributors](#contributions-and-thanks) ## How It Works - when your ESP starts up, it sets it up in Station mode and tries to connect to a previously saved Access Point - if this is unsuccessful (or no previous network saved) it moves the ESP into Access Point mode and spins up a DNS and WebServer (default ip 192.168.4.1) - using any wifi enabled device with a browser (computer, phone, tablet) connect to the newly created Access Point - because of the Captive Portal and the DNS server you will either get a 'Join to network' type of popup or get any domain you try to access redirected to the configuration portal - choose one of the access points scanned, enter password, click save - ESP will try to connect. If successful, it relinquishes control back to your app. If not, reconnect to AP and reconfigure. ## How It Looks   ## Wishlist - [x] remove dependency on EEPROM library - [x] move HTML Strings to PROGMEM - [x] cleanup and streamline code (although this is ongoing) - [x] if timeout is set, extend it when a page is fetched in AP mode - [x] add ability to configure more parameters than ssid/password - [x] maybe allow setting ip of ESP after reboot - [x] add to Arduino Library Manager - [x] add to PlatformIO - [ ] add multiple sets of network credentials - [x] allow users to customize CSS - [ ] ESP32 support or instructions - [ ] rewrite documentation for simplicity, based on scenarios/goals - [ ] rely on the SDK's built in auto connect more than forcing a connect ## Quick Start ### Installing You can either install through the Arduino Library Manager or checkout the latest changes or a release from github #### Install through Library Manager __Currently version 0.8+ works with release 2.0.0 or newer of the [ESP8266 core for Arduino](https://github.com/esp8266/Arduino)__ - in Arduino IDE got to Sketch/Include Library/Manage Libraries  - search for WiFiManager  - click Install and start [using it](#using) #### Checkout from github __Github version works with release 2.0.0 or newer of the [ESP8266 core for Arduino](https://github.com/esp8266/Arduino)__ - Checkout library to your Arduino libraries folder ### Using - Include in your sketch ```cpp #include <ESP8266WiFi.h> //ESP8266 Core WiFi Library (you most likely already have this in your sketch) #include <DNSServer.h> //Local DNS Server used for redirecting all requests to the configuration portal #include <ESP8266WebServer.h> //Local WebServer used to serve the configuration portal #include <WiFiManager.h> //https://github.com/tzapu/WiFiManager WiFi Configuration Magic ``` - Initialize library, in your setup function add ```cpp WiFiManager wifiManager; ``` - Also in the setup function add ```cpp //first parameter is name of access point, second is the password wifiManager.autoConnect("AP-NAME", "AP-PASSWORD"); ``` if you just want an unsecured access point ```cpp wifiManager.autoConnect("AP-NAME"); ``` or if you want to use and auto generated name from 'ESP' and the esp's Chip ID use ```cpp wifiManager.autoConnect(); ``` After you write your sketch and start the ESP, it will try to connect to WiFi. If it fails it starts in Access Point mode. While in AP mode, connect to it then open a browser to the gateway IP, default 192.168.4.1, configure wifi, save and it should reboot and connect. Also see [examples](https://github.com/tzapu/WiFiManager/tree/master/examples). ## Documentation #### Password protect the configuration Access Point You can and should password protect the configuration access point. Simply add the password as a second parameter to `autoConnect`. A short password seems to have unpredictable results so use one that's around 8 characters or more in length. The guidelines are that a wifi password must consist of 8 to 63 ASCII-encoded characters in the range of 32 to 126 (decimal) ```cpp wifiManager.autoConnect("AutoConnectAP", "password") ``` #### Callbacks ##### Enter Config mode Use this if you need to do something when your device enters configuration mode on failed WiFi connection attempt. Before `autoConnect()` ```cpp wifiManager.setAPCallback(configModeCallback); ``` `configModeCallback` declaration and example ```cpp void configModeCallback (WiFiManager *myWiFiManager) { Serial.println("Entered config mode"); Serial.println(WiFi.softAPIP()); Serial.println(myWiFiManager->getConfigPortalSSID()); } ``` ##### Save settings This gets called when custom parameters have been set **AND** a connection has been established. Use it to set a flag, so when all the configuration finishes, you can save the extra parameters somewhere. See [AutoConnectWithFSParameters Example](https://github.com/tzapu/WiFiManager/tree/master/examples/AutoConnectWithFSParameters). ```cpp wifiManager.setSaveConfigCallback(saveConfigCallback); ``` `saveConfigCallback` declaration and example ```cpp //flag for saving data bool shouldSaveConfig = false; //callback notifying us of the need to save config void saveConfigCallback () { Serial.println("Should save config"); shouldSaveConfig = true; } ``` #### Configuration Portal Timeout If you need to set a timeout so the ESP doesn't hang waiting to be configured, for instance after a power failure, you can add ```cpp wifiManager.setConfigPortalTimeout(180); ``` which will wait 3 minutes (180 seconds). When the time passes, the autoConnect function will return, no matter the outcome. Check for connection and if it's still not established do whatever is needed (on some modules I restart them to retry, on others I enter deep sleep) #### On Demand Configuration Portal If you would rather start the configuration portal on demand rather than automatically on a failed connection attempt, then this is for you. Instead of calling `autoConnect()` which does all the connecting and failover configuration portal setup for you, you need to use `startConfigPortal()`. __Do not use BOTH.__ Example usage ```cpp void loop() { // is configuration portal requested? if ( digitalRead(TRIGGER_PIN) == LOW ) { WiFiManager wifiManager; wifiManager.startConfigPortal("OnDemandAP"); Serial.println("connected...yeey :)"); } } ``` See example for a more complex version. [OnDemandConfigPo