Version v1.0.9 to enhance Config Portal GUI

Releases v1.0.9

1. Enhance Config Portal GUI.

Version v1.0.8 to fix AP-staying-open bug

Releases v1.0.8

1. Fix AP-staying-open bug.
2. Add clearConfigData() to enable forcing into ConfigPortal Mode when necessary

Version v1.0.7 with Multi-WiFi APs and Multi-Blynk Servers

Releases v1.0.7

Why this version

1. Add checksum for more reliable data
2. Add Multi-WiFi feature to enable reconnect to the best / available WiFi AP.
3. Add Multi-Blynk feature to enable reconnect to the best / available Blynk Server

Version v1.0.6 with optimization, bug fix and more functions

New in Version v1.0.6

1. Optimize
2. Fix ESP32 EEPROM size to 2K from 4K to avoid NVS error
3. Shorten code size
4. Add functions
5. Use dynamically allocated Config Portal WebServer.

Version v1.0.5 enabling configurable static IP addresses.

Releases v1.0.5

Why this version

Normally, the default Portal IP (192.168.4.1), SSID and PW as well as the dynamically allocated board's IP address are good enough.
In special cases where there is conflict, if static IP is required or bad router's DNS settings, you can use the new features to force the configurable IP addresses. But please use with care to avoid potential issues.

New in this version

Add new features to enable :

1. configuring Portal Static IP address, Name and Password.
2. configuring Static IP address, Gateway, Subnet Mask and 2 DNS Servers IP addresses.

Version v1.0.4 with personalized RFC-952 DHCP hostname

Releases v1.0.4

Why this version

I'm really fed-up with the unfriendly, confusing and cryptic DHCP hostnames such as ESP_XXXXXX, espressif using ChipID. Thanks to an issue opened in library ESP_WiFiManager, I decided to add this option to have built-in, yet configurable DHCP hostname to these libraries.

Now you can easily specify and have the friendly, identifiable, RFC-952-conformed DHP hostnames associated with your boards, such as SmartFarm-1, Irrigation, Master-Controller, etc. You'll be happier to have a look at your WiFi Router DHCP list.

New in this version

1. Add configurable personalized RFC-952 DHCP hostname and setHostname()
2. Modify examples to use new feature

Version v1.0.3 to fix compiler errors for ESP8266 core pre-2.5.2

Releases v1.0.3

New in this version

1. Modify code to be compatible with ESP8266 core pre-2.5.2. But it's still advisable to update to the latest stable core, such as 2.6.3

2. Add examples

Version v1.0.2

This release of very-easy-to-use will help you to eliminate hardcoding your Wifi and Blynk credentials for ESP8266 and ESP32 (with / without SSL), and updating/reflashing every time when you need to change them.

Configuration data are stored in either SPIFFS or EEPROM.

When WiFi and/or Blynk connection is lost, the WM will try auto-reconnect.

New in this version

Fix bug
New in this version:

1. If the config data not entered completely (SSID, password, Server and Blynk token), entering config portal
2. Correct the operation of BUILTIN_LED

DONE:

Permit EEPROM size and location configurable to avoid conflict with others.
More flexible to configure reconnection timeout
For fresh config data, don't need to wait for connecting timeout before entering config portal.

v1.0.1

This release of very-easy-to-use will help you to eliminate hardcoding your Wifi and Blynk credentials for ESP8266 and ESP32 (with / without SSL), and updating/reflashing every time when you need to change them.

Configuration data are stored in either SPIFFS or EEPROM.

When WiFi and/or Blynk connection is lost, the WM will try auto-reconnect.

##DONE:

1. Permit EEPROM size and location configurable to avoid conflict with others.
2. More flexible to configure reconnection timeout
3. For fresh config data, don't need to wait for connecting timeout before entering config portal.

TO DO

1. Support other boards with WiFi
2. Better GUI

Preliminary Release v1.0.0

This first release of very-easy-to-use will help you to eliminate hardcoding your Wifi and Blynk credentials for ESP8266 and ESP32 (with / without SSL), and updating/reflashing every time when you need to change them.

Configuration data are stored in either SPIFFS or EEPROM.

When WiFi and/or Blynk connection is lost, the WM will try auto-reconnect.

TO DO:

1. Permit EEPROM size and location configurable to avoid conflict with others.
2. More flexible to configure reconnection timeout
3. For fresh config data, don't need to wait for connecting timeout before entering config portal.