Blynk_Esp8266AT_WM
Table of Contents
Features
This is a Blynk and WiFiManager Library for configuring/auto(re)connecting ESP8266/ESP32-AT-command shields/modules to the available MultiWiFi APs at runtime. Connection is without SSL. Configuration data to be saved in either EEPROM, nRF52/RP2040 LittleFS, SAMD EEPROM-emulated FlashStorage, SAM-DUE DueFlashStorage or STM32 emulated EEPROM. Default Credentials as well as Dynamic custom parameters can be added and modified easily without coding knowledge. DoubleResetDetector is used to force Config Portal opening even if the Credentials are still valid.
This library is designed to help you to eliminate hardcoding your Wifi and Blynk credentials for boards using ESP8266/ESP32-AT-command shields, and updating/reflashing every time you need to change them via Config Portalor or sketch.
The RP2040-based boards, such as RASPBERRY_PI_PICO, are currently supported using Earle Philhower’s arduino-pico core v1.4.0+ with Blynk/WiFiManager features thanks to LittleFS support.
The support to Arduino-mbed RP2040 core with Blynk/WiFiManager features will be added in the future using simulated-EEPROM or LittleFS if ready then. Now you can use this core without Blynk/WiFiManager features.
New recent features:
- MultiWiFi feature for configuring/auto(re)connecting ESP8266/ESP32-AT shields to the available MultiWiFi APs at runtime.
- DoubleDetectDetector feature to force Config Portal when double reset is detected within predetermined time, default 10s.
- Configurable Config Portal Title to be either BoardName or default undistinguishable names.
- Examples are redesigned to separate Credentials / Defines / Dynamic Params / Code so that you can change Credentials / Dynamic Params quickly for each device
- Add functions to control Config Portal from software or Virtual Switches.
Currently Supported Boards
- SAMD21
- Arduino SAMD21: ZERO, MKRs, NANO_33_IOT, etc.
- Adafruit SAMD21 (M0): ItsyBitsy M0, Feather M0, Feather M0 Express, Metro M0 Express, Circuit Playground Express, Trinket M0, PIRkey, Hallowing M0, Crickit M0, etc.
- Seeeduino: LoRaWAN, Zero, Femto M0, XIAO M0, Wio GPS Board, etc.
- SAMD51
- Adafruit SAMD51 (M4): Metro M4, Grand Central M4, ItsyBitsy M4, Feather M4 Express, Trellis M4, Metro M4 AirLift Lite, MONSTER M4SK Express, Hallowing M4, etc.
- Seeeduino: Wio Terminal, Grove UI Wireless
-
nRF52 boards, such as AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, NINA_B302_ublox, NINA_B112_ublox, etc.
-
SAM DUE
-
STM32F/L/H/G/WB/MP1
-
Teensy (4.1, 4.0, 3.6, 3.5, 3,2, 3.1, 3.0) using Teensy core 1.51
-
AVR Mega1280, 2560, ADK.
-
RP2040-based boards, such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, using Arduino-mbed RP2040 core or Earle Philhower’s arduino-pico core v1.3.1+.
Currently Supported AT-command shields
- ESP8266-AT-command shield
- ESP32-AT-command shield
- W600 and WIS600-01S AT-command shield
Prerequisites
Arduino IDE 1.8.19+ for Arduino. 
Arduino AVR core 1.8.3+ for Arduino (Use Arduino Board Manager) for AVR boards. 
Arduino Core for STM32 v2.2.0+ for STM32F/L/H/G/WB/MP1 boards (Nucleo-144 NUCLEO_F767ZI, Nucleo-64 NUCLEO_L053R8, etc.). 
Teensy core 1.56 for Teensy (4.1, 4.0, 3.6, 3.5, 3,2, 3.1, 3.0, LC) boards. Use Teensy core v1.51, if the Config Portal can’t run.Arduino SAM DUE core v1.6.12+ for SAM DUE ARM Cortex-M3 boards.Arduino SAMD core 1.8.12+ for SAMD ARM Cortex-M0+ boards. 
Adafruit SAMD core 1.7.9+ for SAMD ARM Cortex-M0+ and M4 boards (Nano 33 IoT, etc.). 
Seeeduino SAMD core 1.8.1+ for SAMD21/SAMD51 boards (XIAO M0, Wio Terminal, etc.). 
Adafruit nRF52 v1.3.0+ for nRF52 boards such as Adafruit NRF52840_FEATHER, NRF52832_FEATHER, NRF52840_FEATHER_SENSE, NRF52840_ITSYBITSY, NRF52840_CIRCUITPLAY, NRF52840_CLUE, NRF52840_METRO, NRF52840_PCA10056, PARTICLE_XENON, NINA_B302_ublox, etc. 
Earle Philhower's arduino-pico core v1.10.0+ for RP2040-based boards such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, etc. 
Arduino mbed_rp2040 core 2.7.2+ for Arduino (Use Arduino Board Manager) RP2040-based boards, such as RASPBERRY_PI_PICO. 
ESP_AT_Lib v1.4.1+ for ESP8266/ESP32-AT shields. To install, check 
.ESP8266_AT_WebServer v1.5.3+. To install, check 
.FlashStorage_SAMD library v1.3.2+ for SAMD21 and SAMD51 boards (ZERO, MKR, NANO_33_IOT, M0, M0 Pro, AdaFruit Itsy-Bitsy M4, etc.). 
FlashStorage_STM32 v1.2.0+ for STM32F/L/H/G/WB/MP1 boards. To install, check 
.DueFlashStorage library v1.0.0+ for SAM DUE. To install, check 
DoubleResetDetector_Generic v1.8.0+. To install. check 
.Ai-Thinker AT Firmware v1.5.4 or AT Firmware v1.7.4.0 for ESP8266-AT shields.AT version_2.1.0.0_dev for ESP32-AT shields.Adafruit's LittleFS/InternalFS for nRF52
Important Notes about AT Firmwares
1. Tested OK with ESP8266-AT shields
-
Ai-Thinker AT Firmware v1.5.4
AT version:1.1.0.0(May 11 2016 18:09:56)
SDK version:1.5.4(baaeaebb)
Ai-Thinker Technology Co. Ltd.
Jun 13 2016 11:29:20
-
AT Firmware v1.7.4.0
AT version:1.7.4.0(May 11 2020 19:13:04)
SDK version:3.0.4(9532ceb)
compile time:May 27 2020 10:12:17
Bin version(Wroom 02):1.7.4
-
WIS600-01S and W600 using either ESP8266 or ESP32-AT commands and stock firmware
AT version:1.1.4(Dec 05 2018 11:06:45)
SDK version:3.0.0
Dec 05 2018 11:06:45
2. Tested OK with ESP32-AT shields
3. Where to upload AT-Firmware
Upload AT Firmware v1.7.4.0 bin files to correct locations as follows:
# BOOT MODE
### Flash size 8Mbit: 512KB+512KB
boot_v1.2+.bin 0x00000
user1.1024.new.2.bin 0x01000
esp_init_data_default.bin 0xfc000
blank.bin 0x7e000 & 0xfe000
### Flash size 16Mbit-C1: 1024KB+1024KB
boot_v1.2+.bin 0x00000
user1.2048.new.5.bin 0x01000
esp_init_data_default.bin 0x1fc000
blank.bin 0xfe000 & 0x1fe000
4. Important Notes
-
Test before using different AT-Firmware Version at your own risks. Just use any simple example to verify if the AT-firmware is OK.
-
Compatible AT-Firmare version will be updated. Check for all supported AT Firmwares and download them from AT_Firmwares.
-
Support to ESP32-AT-command shields has been added to permit using new library ESP_AT_Lib to replace Blynk’s BlynkESP8266_Lib. The same ESP_AT_Lib can also be use for ESP8266-AT shields.
Installation
Use Arduino Library Manager
The best and easiest way is to use Arduino Library Manager. Search for Blynk_Esp8266AT_WM, then select / install the latest version.
You can also use this link for more detailed instructions.
Then copy BlynkDetectDevice.h to folder ~/Arduino/libraries/Blynk/src/Blynk to overwrite the original file BlynkDetectDevice.h.
Manual Install
Another way to install is to:
- Navigate to Blynk_Esp8266AT_WM page.
- Download the latest release
Blynk_Esp8266AT_WM-master.zip.
- Extract the zip file to
Blynk_Esp8266AT_WM-master directory
- Copy whole
Blynk_Esp8266AT_WM-master/src folder to Arduino libraries’ directory such as ~/Arduino/libraries/.
Then copy BlynkDetectDevice.h to folder ~/Arduino/libraries/Blynk/src/Blynk to overwrite the original file BlynkDetectDevice.h. By doing this, the correct board type can be displayed correctly along with Blynk logo as follows:
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ \/ '_/
/____/_/\_, /_//_/_/\_\
/___/ v0.6.1 on NRF52840_ITSYBITSY_EXPRESS
not just unknown Arduino board type:
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ \/ '_/
/____/_/\_, /_//_/_/\_\
/___/ v0.6.1 on Arduino
- Install VS Code
- Install PlatformIO
- Install Blynk_Esp8266AT_WM library by using Library Manager. Search for Blynk_Esp8266AT_WM in Platform.io Author’s Libraries
- Use included platformio.ini file from examples to ensure that all dependent libraries will installed automatically. Please visit documentation for the other options and examples at Project Configuration File
Packages’ Patches
1. For Adafruit nRF52840 and nRF52832 boards
To be able to compile, run and automatically detect and display BOARD_NAME on nRF52840/nRF52832 boards, you have to copy the whole nRF52 Packages_Patches directory into Adafruit nRF52 directory (~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0).
Supposing the Adafruit nRF52 version is 1.1.0. These files must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.1.0/cores/nRF5/Udp.h
Whenever a new version is installed, remember to copy these files into the new version directory. For example, new version is x.yy.z
These files must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h
2. For Teensy boards
To be able to compile and run on Teensy boards, you have to copy the files in Packages_Patches for Teensy directory into Teensy hardware directory (./arduino-1.8.15/hardware/teensy/avr/boards.txt).
Supposing the Arduino version is 1.8.15. These files must be copied into the directory:
./arduino-1.8.15/hardware/teensy/avr/boards.txt./arduino-1.8.15/hardware/teensy/avr/cores/teensy/Stream.h./arduino-1.8.15/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-1.8.15/hardware/teensy/avr/cores/teensy4/Stream.h
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz
These files must be copied into the directory:
./arduino-x.yy.zz/hardware/teensy/avr/boards.txt./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy/Stream.h./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy4/Stream.h
3. For Arduino SAM DUE boards
To be able to compile and run on SAM DUE boards, you have to copy the whole SAM DUE directory into Arduino sam directory (~/.arduino15/packages/arduino/hardware/sam/1.6.12).
Supposing the Arduino SAM core version is 1.6.12. This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/sam/1.6.12/platform.txt
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/sam/x.yy.zz/platform.txt
4. For Arduino SAMD boards
To be able to compile, run and automatically detect and display BOARD_NAME on Arduino SAMD (Nano-33-IoT, etc) boards, you have to copy the whole Arduino SAMD Packages_Patches directory into Arduino SAMD directory (~/.arduino15/packages/arduino/hardware/samd/1.8.11).
For core version v1.8.10+
Supposing the Arduino SAMD version is 1.8.11. Now only one file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/1.8.11/platform.txt
Whenever a new version is installed, remember to copy this files into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/x.yy.zz/platform.txt
For core version v1.8.9-
Supposing the Arduino SAMD version is 1.8.9. These files must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/1.8.9/platform.txt~/.arduino15/packages/arduino/hardware/samd/1.8.9/cores/arduino/Arduino.h
Whenever a new version is installed, remember to copy these files into the new version directory. For example, new version is x.yy.z
These files must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/x.yy.z/platform.txt~/.arduino15/packages/arduino/hardware/samd/x.yy.z/cores/arduino/Arduino.h
This is mandatory to fix the notorious Arduino SAMD compiler error. See Improve Arduino compatibility with the STL (min and max macro)
...\arm-none-eabi\include\c++\7.2.1\bits\stl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2
min(const _Tp& __a, const _Tp& __b, _Compare __comp)
Whenever the above-mentioned compiler error issue is fixed with the new Arduino SAMD release, you don’t need to copy the Arduino.h file anymore.
5. For Adafruit SAMD boards
To be able to compile, run and automatically detect and display BOARD_NAME on Adafruit SAMD (Itsy-Bitsy M4, etc) boards, you have to copy the whole Adafruit SAMD Packages_Patches directory into Adafruit samd directory (~/.arduino15/packages/adafruit/hardware/samd/1.7.5).
Supposing the Adafruit SAMD core version is 1.7.5. This file must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/samd/1.7.5/platform.txt~/.arduino15/packages/adafruit/hardware/samd/1.7.5/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/1.7.5/cores/arduino/Print.cpp
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/platform.txt~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/cores/arduino/Print.cpp
6. For Seeeduino SAMD boards
To be able to compile, run and automatically detect and display BOARD_NAME on Seeeduino SAMD (XIAO M0, Wio Terminal, etc) boards, you have to copy the whole Seeeduino SAMD Packages_Patches directory into Seeeduino samd directory (~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2).
Supposing the Seeeduino SAMD core version is 1.8.2. This file must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/cores/arduino/Print.cpp
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Print.cpp
7. For STM32 boards
7.1 For STM32 boards to use LAN8720
To use LAN8720 on some STM32 boards
- Nucleo-144 (F429ZI, NUCLEO_F746NG, NUCLEO_F746ZG, NUCLEO_F756ZG)
- Discovery (DISCO_F746NG)
- STM32F4 boards (BLACK_F407VE, BLACK_F407VG, BLACK_F407ZE, BLACK_F407ZG, BLACK_F407VE_Mini, DIYMORE_F407VGT, FK407M1)
you have to copy the files stm32f4xx_hal_conf_default.h and stm32f7xx_hal_conf_default.h into STM32 stm32 directory (~/.arduino15/packages/STM32/hardware/stm32/2.1.0/system) to overwrite the old files.
Supposing the STM32 stm32 core version is 2.1.0. These files must be copied into the directory:
~/.arduino15/packages/STM32/hardware/stm32/2.1.0/system/STM32F4xx/stm32f4xx_hal_conf_default.h for STM32F4.~/.arduino15/packages/STM32/hardware/stm32/2.1.0/system/STM32F7xx/stm32f7xx_hal_conf_default.h for Nucleo-144 STM32F7.
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz,
theses files must be copied into the corresponding directory:
~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/system/STM32F4xx/stm32f4xx_hal_conf_default.h- `~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/system/STM32F7xx/stm32f7xx_hal_conf_default.h
7.2 For STM32 boards to use Serial1
To use Serial1 on some STM32 boards without Serial1 definition (Nucleo-144 NUCLEO_F767ZI, Nucleo-64 NUCLEO_L053R8, etc.) boards, you have to copy the files STM32 variant.h into STM32 stm32 directory (~/.arduino15/packages/STM32/hardware/stm32/2.1.0). You have to modify the files corresponding to your boards, this is just an illustration how to do.
Supposing the STM32 stm32 core version is 2.1.0. These files must be copied into the directory:
~/.arduino15/packages/STM32/hardware/stm32/2.1.0/variants/STM32F7xx/F765Z(G-I)T_F767Z(G-I)T_F777ZIT/NUCLEO_F767ZI/variant.h for Nucleo-144 NUCLEO_F767ZI.~/.arduino15/packages/STM32/hardware/stm32/2.1.0/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.h for Nucleo-64 NUCLEO_L053R8.
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz,
theses files must be copied into the corresponding directory:
~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/variants/STM32F7xx/F765Z(G-I)T_F767Z(G-I)T_F777ZIT/NUCLEO_F767ZI/variant.h~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.h
8.1 To use BOARD_NAME
To be able to automatically detect and display BOARD_NAME on RP2040-based boards (RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040, GENERIC_RP2040, etc) boards, you have to copy the file RP2040 platform.txt into rp2040 directory (~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0).
Supposing the rp2040 core version is 1.4.0. This file must be copied into the directory:
~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0/platform.txt
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/rp2040/hardware/rp2040/x.yy.zz/platform.txt
With core after v1.5.0, this step is not necessary anymore thanks to the PR Add -DBOARD_NAME=“{build.board}” #136.
8.2 To avoid compile error relating to microsecondsToClockCycles
Some libraries, such as Adafruit DHT-sensor-library, require the definition of microsecondsToClockCycles(). To be able to compile and run on RP2040-based boards, you have to copy the files in RP2040 Arduino.h into rp2040 directory (~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0).
Supposing the rp2040 core version is 1.4.0. This file must be copied to replace:
~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0/cores/rp2040/Arduino.h
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz
This file must be copied to replace:
~/.arduino15/packages/rp2040/hardware/rp2040/x.yy.zz/cores/rp2040/Arduino.h
With core after v1.5.0, this step is not necessary anymore thanks to the PR Add defs for compatibility #142.
9. For Portenta_H7 boards using Arduino IDE in Linux
To be able to upload firmware to Portenta_H7 using Arduino IDE in Linux (Ubuntu, etc.), you have to copy the file portenta_post_install.sh into mbed_portenta directory (~/.arduino15/packages/arduino/hardware/mbed_portenta/2.5.2/portenta_post_install.sh).
Then run the following command using sudo
$ cd ~/.arduino15/packages/arduino/hardware/mbed_portenta/2.5.2
$ chmod 755 portenta_post_install.sh
$ sudo ./portenta_post_install.sh
This will create the file /etc/udev/rules.d/49-portenta_h7.rules as follows:
# Portenta H7 bootloader mode UDEV rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2341", ATTRS{idProduct}=="035b", GROUP="plugdev", MODE="0666"
Supposing the ArduinoCore-mbed core version is 2.5.2. Now only one file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/mbed_portenta/2.5.2/portenta_post_install.sh
Whenever a new version is installed, remember to copy this files into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/mbed_portenta/x.yy.zz/portenta_post_install.sh
How to use
In your code, to use WiFiManager Blynk features, replace
BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_WM.h for Mega boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_nRF52_WM.h for nRF52 boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_SAMD_WM.h for SAMD boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_DUE_WM.h for SAM DUE boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_STM32_WM.h for STM32 boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_Teensy_WM.h for Teensy boards using multiWiFi APs.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_Teensy_WM_Single.h for Teensy boards using single WiFi AP.
to use Blynk only, with hardcoded Credentials, replace
BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_nRF52.h for nRF52 boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_SAMD.h for SAMD boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_DUE.h for SAMD boards.BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_STM32.h for STM32 boards.- Keep the same
BlynkSimpleShieldEsp8266.h for Mega boards
BlynkSimpleShieldEsp8266.h with BlynkSimpleShieldEsp8266_Teensy.h for Teensy boards.
- For Mega, Config Data is stored in EEPROM ( 184 bytes for Mega from address EEPROM_START ) to save your configuration data. EEPROM_SIZE can be specified from 512 to 4096 bytes.
- For STM32 boards, Config Data is stored in emulated-EEPROM ( 280 bytes for STM32 boards from address EEPROM_START ) to save your configuration data. EEPROM_SIZE can be up to 16K bytes. The STM32 Arduino core provides a buffered access API to the emulated-EEPROM.
- For nRF52 boards, Config Data is stored in LittleFS.
- For SAMD boards, Config Data is stored in FlashStorage using 256-byte block.
- For SAM DUE boards, Config Data is stored in DueFlashStorage.
To use personalized Config Portal AP SSID and Password, as well as IP Address, channel e.g. call :
ESP8266 wifi(&EspSerial);
// initialize serial for ESP module
EspSerial.begin(ESP8266_BAUD);
...
// Optional to change default AP IP(192.168.4.1) and channel(10)
//Blynk.setConfigPortalIP(IPAddress(192, 168, 132, 1));
// Personalized portal_ssid and password
Blynk.setConfigPortal(portal_ssid, portal_password);
//Blynk.setConfigPortal("STM32_WM", "MySTM32_PW");
Blynk.setConfigPortalChannel(0);
Blynk.begin(wifi);
Then replace Blynk.begin(...) with Blynk.begin(wifi);
in your code. Keep Blynk.run() intact.
That’s it.
HOWTO Use default Credentials and have them pre-loaded onto Config Portal
See this example and modify as necessary
bool LOAD_DEFAULT_CONFIG_DATA = true;
2. To use system default to load “blank” when there is no valid Credentials
bool LOAD_DEFAULT_CONFIG_DATA = false;
#ifndef Credentials_h
#define Credentials_h
#include "defines.h"
/// Start Default Config Data //////////////////
/*
#define SSID_MAX_LEN 32
//From v1.0.3, WPA2 passwords can be up to 63 characters long.
#define PASS_MAX_LEN 64
typedef struct
{
char wifi_ssid[SSID_MAX_LEN];
char wifi_pw [PASS_MAX_LEN];
} WiFi_Credentials;
#define NUM_WIFI_CREDENTIALS 2
// Configurable items besides fixed Header
#define NUM_CONFIGURABLE_ITEMS ( ( 2 * NUM_WIFI_CREDENTIALS ) + 4 )
////////////////
typedef struct Configuration
{
char header [16];
WiFi_Credentials WiFi_Creds [NUM_WIFI_CREDENTIALS];
char blynk_server [32];
char blynk_token [36];
int checkSum;
} Blynk_WF_Configuration;
*/
#define TO_LOAD_DEFAULT_CONFIG_DATA false //true
#if TO_LOAD_DEFAULT_CONFIG_DATA
// Use LOAD_DEFAULT_CONFIG_DATA = true in development stage to avoid repeatedly input config data
// Default Config Data will override Data input from Config Portal (CP)
// Use LOAD_DEFAULT_CONFIG_DATA = false in normal operation, and use dummy value here
// Data input from Config Portal (CP) will override Default Config Data
bool LOAD_DEFAULT_CONFIG_DATA = false;
Blynk_WF_Configuration defaultConfig =
{
//char header[16], dummy, not used
"STM32_ESP_AT",
// WiFi_Credentials WiFi_Creds [NUM_WIFI_CREDENTIALS];
// WiFi_Credentials.wifi_ssid and WiFi_Credentials.wifi_pw
#if 1
"realSSID", "realPass",
"realSSID1", "realPass1",
// Blynk_Creds : blynk_server and blynk_token
"realServer.duckdns.org", "realToken",
#else
"SSID1", "password1",
"SSID2", "password2",
// Blynk_Creds : blynk_server and blynk_token
"account.ddns.net", "token",
#endif
// terminate the list
//int checkSum, dummy, not used
0
/////////// End Default Config Data /////////////
};
#else
bool LOAD_DEFAULT_CONFIG_DATA = false;
Blynk_WF_Configuration defaultConfig;
#endif // TO_LOAD_DEFAULT_CONFIG_DATA
/////////// End Default Config Data /////////////
#endif //Credentials_h
4. How to add dynamic parameters from sketch
- To add custom parameters, just modify the example below
4.1 In defines.h
#define USE_DYNAMIC_PARAMETERS true
4.2 In dynamicParams.h
#ifndef dynamicParams_h
#define dynamicParams_h
#if USE_BLYNK_WM
// USE_DYNAMIC_PARAMETERS defined in defined.h
/////////////// Start dynamic Credentials ///////////////
//Defined in <BlynkSimpleShieldEsp8266_STM32_WM.h>
/**************************************
#define MAX_ID_LEN 5
#define MAX_DISPLAY_NAME_LEN 16
typedef struct
{
char id [MAX_ID_LEN + 1];
char displayName [MAX_DISPLAY_NAME_LEN + 1];
char *pdata;
uint8_t maxlen;
} MenuItem;
**************************************/
#if USE_DYNAMIC_PARAMETERS
#define MAX_MQTT_SERVER_LEN 34
char MQTT_Server [MAX_MQTT_SERVER_LEN + 1] = "default-mqtt-server";
#define MAX_MQTT_PORT_LEN 6
char MQTT_Port [MAX_MQTT_PORT_LEN + 1] = "1883";
MenuItem myMenuItems [] =
{
{ "mqtt", "MQTT Server", MQTT_Server, MAX_MQTT_SERVER_LEN },
{ "mqpt", "Port", MQTT_Port, MAX_MQTT_PORT_LEN },
};
// Due to notorious 2K buffer limitation of ESO8266-AT shield, the NUM_MENU_ITEMS is limited to max 3
// to avoid WebServer not working due to HTML data larger than 2K can't be sent successfully
// The items with index larger than 3 will be ignored
uint16_t NUM_MENU_ITEMS = sizeof(myMenuItems) / sizeof(MenuItem); //MenuItemSize;
#else
MenuItem myMenuItems [] = {};
uint16_t NUM_MENU_ITEMS = 0;
#endif //USE_DYNAMIC_PARAMETERS
/////// // End dynamic Credentials ///////////
#endif //USE_BLYNK_WM
#endif //dynamicParams_h
5. If you don’t need to add dynamic parameters
Use the following code snippet in sketch
#define USE_DYNAMIC_PARAMETERS false
or
/////////////// Start dynamic Credentials ///////////////
MenuItem myMenuItems [] = {};
uint16_t NUM_MENU_ITEMS = 0;
/////// // End dynamic Credentials ///////////
Important Notes for using Dynamic Parameters’ ids
- These ids (such as “mqtt” in example) must be unique.
Please be noted that the following reserved names are already used in library:
"id" for WiFi SSID
"pw" for WiFi PW
"id1" for WiFi1 SSID
"pw1" for WiFi1 PW
"sv" for Blynk Server
"tk" for Blynk Token
Important notes
- Now you can use special chars such as ~, !, @, #, $, %, ^, &, _, -, space,etc. thanks to brondolin to provide the amazing fix in v1.0.10 to permit input special chars such as % and # into data fields. See Issue 3.
- The SSIDs, Passwords, BlynkServers and Tokens must be input (or to make them different from nothing). Otherwise, the Config Portal will re-open until those fields have been changed. If you don’t need any field, just input anything or use duplicated data from similar field.
- WiFi password max length now is 63 chars according to WPA2 standard.
- Sometimes, it’s hard or not possible to connect to Config Portal WiFi AP, the majority cases are caused by WiFi channel conflict if there are too many WiFi APs running around. Please use random ConfigPortal WiFi AP channel in sketch (see code snippet below) and reset the board so that another channel is used. Repeat until connection is OK
// Set config portal channel, default = 1. Use 0 => random channel from 1-13 to avoid conflict
Blynk.setConfigPortalChannel(0);
Why using this Blynk_Esp8266AT_WM with MultiWiFi feature
You can see that the system automatically detects and connects to the avaiable WiFi APs, whenever interruption happens. This feature is very useful for systems requiring high degree of reliability.
Moreover, this Blynk.begin() is not a blocking call, so you can use it for critical functions requiring in loop().
Anyway, this is better for projects using Blynk just for GUI (graphical user interface).
In operation, if WiFi or Blynk connection is lost, Blynk.run() will try reconnecting automatically. Therefore, Blynk.run() must be called in the loop() function. Don’t use:
void loop()
{
if (Blynk.connected())
Blynk.run();
...
}
just
void loop()
{
Blynk.run();
...
}
Examples
- Mega_ESP8266Shield
- nRF52_ESP8266Shield
- SAMD_ESP8266Shield
- SAM_DUE_ESP8266Shield
- STM32_ESP8266Shield
- Teensy40_ESP8266Shield.
- Teensy40_ESP8266Shield_Single.
- RP2040_ESP8266Shield. New
So, how it works?
If it cannot connect to the Blynk server in 30 seconds, it will switch to Configuration Mode. You will see your built-in LED turned ON. In Configuration Mode, it starts a configurable access point, default called nRF52_XXXXXX, SAMD_XXXXXX, DUE_XXXXXX,Mega_XXXXXX or STM32_XXXXXX. Connect to it using password MynRF52_XXXXXX, MySAMD_XXXXXX, MyDUE_XXXXXX, MyMega_XXXXXX or MySTM32_XXXXXX.
After you connected, please, go to http://192.168.4.1 or the AP IP you specified.
Enter your credentials : WiFi SSID/Password, Blynk Server, Port and Token, Board Name.
Then click Save. After you restarted, you will see your built-in LED turned OFF. That means, it connected to your Blynk server successfully.
/****************************************************************************************************************************
Important notes:
1) Tested OK with SAMD, Mega, nRF52, SAM DUE
a) ESP8266-AT version:1.1.0.0(May 11 2016 18:09:56)
SDK version:1.5.4(baaeaebb)
Ai-Thinker Technology Co. Ltd.
Jun 13 2016 11:29:20
b) ESP8266-AT version:1.7.4.0(May 11 2020 19:13:04)
SDK version:3.0.4(9532ceb)
compile time:May 27 2020 10:12:22
Bin version(Wroom 02):1.7.4
2) These versions don't work on SAMD, but work on Mega (hanging when connect to Blynk, WiFi OK)
To find bug and fix in Blynk ESP8266_Lib or Blynk library
*****************************************************************************************************************************/
#include "defines.h"
#if USE_BLYNK_WM
#include "Credentials.h"
#include "dynamicParams.h"
#define BLYNK_PIN_FORCED_CONFIG V10
#define BLYNK_PIN_FORCED_PERS_CONFIG V20
// Use button V10 (BLYNK_PIN_FORCED_CONFIG) to forced Config Portal
BLYNK_WRITE(BLYNK_PIN_FORCED_CONFIG)
{
if (param.asInt())
{
Serial.println( F("\nCP Button Hit. Rebooting") );
// This will keep CP once, clear after reset, even you didn't enter CP at all.
Blynk.resetAndEnterConfigPortal();
}
}
// Use button V20 (BLYNK_PIN_FORCED_PERS_CONFIG) to forced Persistent Config Portal
BLYNK_WRITE(BLYNK_PIN_FORCED_PERS_CONFIG)
{
if (param.asInt())
{
Serial.println( F("\nPersistent CP Button Hit. Rebooting") );
// This will keep CP forever, until you successfully enter CP, and Save data to clear the flag.
Blynk.resetAndEnterConfigPortalPersistent();
}
}
#endif
ESP8266 wifi(&EspSerial);
void heartBeatPrint()
{
static int num = 1;
if (Blynk.connected())
{
Serial.print(F("B"));
}
else
{
Serial.print(F("F"));
}
if (num == 80)
{
Serial.println();
num = 1;
}
else if (num++ % 10 == 0)
{
Serial.print(F(" "));
}
}
void check_status()
{
static unsigned long checkstatus_timeout = 0;
#define STATUS_CHECK_INTERVAL 15000L
// Send status report every STATUS_REPORT_INTERVAL (60) seconds: we don't need to send updates frequently if there is no status change.
if ((millis() > checkstatus_timeout) || (checkstatus_timeout == 0))
{
// report status to Blynk
heartBeatPrint();
checkstatus_timeout = millis() + STATUS_CHECK_INTERVAL;
}
}
void setup()
{
// Debug console
Serial.begin(115200);
while (!Serial);
delay(200);
Serial.print(F("\nStart nRF52_ESP8266Shield on ")); Serial.println(BOARD_NAME);
Serial.println(BLYNK_ESP8266AT_WM_VERSION);
Serial.println(ESP_AT_LIB_VERSION);
// initialize serial for ESP module
EspSerial.begin(ESP8266_BAUD);
#if USE_BLYNK_WM
Serial.println(DOUBLERESETDETECTOR_GENERIC_VERSION);
Serial.println(F("Start Blynk_ESP8266AT_WM"));
// Optional to change default AP IP(192.168.4.1) and channel(10)
//Blynk.setConfigPortalIP(IPAddress(192, 168, 152, 1));
// Personalized portal_ssid and password
Blynk.setConfigPortal(portal_ssid, portal_password);
//Blynk.setConfigPortal("nRF52_WM", "MynRF52_PW");
Blynk.setConfigPortalChannel(0);
Blynk.begin(wifi);
#else
Serial.print(F("Start Blynk no WM with BlynkServer = "));
Serial.print(BlynkServer);
Serial.print(F(" and Token = "));
Serial.println(auth);
Blynk.begin(auth, wifi, ssid, pass, BlynkServer.c_str(), BLYNK_SERVER_HARDWARE_PORT);
#endif
}
#if (USE_BLYNK_WM && USE_DYNAMIC_PARAMETERS)
void displayCredentials()
{
Serial.println("\nYour stored Credentials :");
for (uint8_t i = 0; i < NUM_MENU_ITEMS; i++)
{
Serial.println(String(myMenuItems[i].displayName) + " = " + myMenuItems[i].pdata);
}
}
void displayCredentialsInLoop()
{
static bool displayedCredentials = false;
if (!displayedCredentials)
{
for (uint8_t i = 0; i < NUM_MENU_ITEMS; i++)
{
if (!strlen(myMenuItems[i].pdata))
{
break;
}
if ( i == (NUM_MENU_ITEMS - 1) )
{
displayedCredentials = true;
displayCredentials();
}
}
}
}
#endif
void loop()
{
Blynk.run();
check_status();
#if (USE_BLYNK_WM && USE_DYNAMIC_PARAMETERS)
displayCredentialsInLoop();
#endif
}
#ifndef defines_h
#define defines_h
/* Comment this out to disable prints and save space */
#define BLYNK_PRINT Serial
// Debug level, 0-3
#define BLYNK_WM_DEBUG 3
#define USE_NEW_WEBSERVER_VERSION true //false
#define _ESP_AT_LOGLEVEL_ 0
#define _ESP_AT_LIB_LOGLEVEL_ 0
/* Comment this out to disable prints and save space */
#define DRD_GENERIC_DEBUG true
/* Comment this out to disable prints and save space */
#define ESP_AT_DEBUG_OUTPUT Serial
//#define ESP_AT_LIB_DEBUG_OUTPUT Serial
#define ESP_AT_DEBUG true
#define ESP_AT_LIB_DEBUG true
// Uncomment to use ESP32-AT commands
//#define USE_ESP32_AT true
// USE_ESP_AT_LIB == true to use new ESP_AT_Lib, instead of ESP8266_Lib
// For ESP32-AT, must use ESP_AT_Lib
#if (defined(USE_ESP32_AT) && USE_ESP32_AT )
#define USE_ESP_AT_LIB true
#else
#define USE_ESP_AT_LIB true
//#define USE_ESP_AT_LIB false
#endif
#if ( defined(NRF52840_FEATHER) || defined(NRF52832_FEATHER) || defined(NRF52_SERIES) || defined(ARDUINO_NRF52_ADAFRUIT) || \
defined(NRF52840_FEATHER_SENSE) || defined(NRF52840_ITSYBITSY) || defined(NRF52840_CIRCUITPLAY) || defined(NRF52840_CLUE) || \
defined(NRF52840_METRO) || defined(NRF52840_PCA10056) || defined(PARTICLE_XENON) || defined(NINA_B302_ublox) || defined(NINA_B112_ublox) )
#if defined(ESP8266_AT_USE_NRF528XX)
#undef ESP8266_AT_USE_NRF528XX
#endif
#define ESP8266_AT_USE_NRF528XX true
#else
#error This code is intended to run only on the nRF52 boards ! Please check your Tools->Board setting.
#endif
#if (ESP8266_AT_USE_NRF528XX)
#if defined(NRF52840_FEATHER)
#define BOARD_TYPE "NRF52840_FEATHER_EXPRESS"
#elif defined(NRF52832_FEATHER)
#define BOARD_TYPE "NRF52832_FEATHER"
#elif defined(NRF52840_FEATHER_SENSE)
#define BOARD_TYPE "NRF52840_FEATHER_SENSE"
#elif defined(NRF52840_ITSYBITSY)
#define BOARD_TYPE "NRF52840_ITSYBITSY_EXPRESS"
#elif defined(NRF52840_CIRCUITPLAY)
#define BOARD_TYPE "NRF52840_CIRCUIT_PLAYGROUND"
#elif defined(NRF52840_CLUE)
#define BOARD_TYPE "NRF52840_CLUE"
#elif defined(NRF52840_METRO)
#define BOARD_TYPE "NRF52840_METRO_EXPRESS"
#elif defined(NRF52840_PCA10056)
#define BOARD_TYPE "NORDIC_NRF52840DK"
#elif defined(NINA_B302_ublox)
#define BOARD_TYPE "NINA_B302_ublox"
#elif defined(NINA_B112_ublox)
#define BOARD_TYPE "NINA_B112_ublox"
#elif defined(PARTICLE_XENON)
#define BOARD_TYPE "PARTICLE_XENON"
#elif defined(MDBT50Q_RX)
#define BOARD_TYPE "RAYTAC_MDBT50Q_RX"
#elif defined(ARDUINO_NRF52_ADAFRUIT)
#define BOARD_TYPE "ARDUINO_NRF52_ADAFRUIT"
#else
#define BOARD_TYPE "nRF52 Unknown"
#endif
#define EspSerial Serial1
#endif //ESP8266_AT_USE_NRF528XX
#ifndef BOARD_NAME
#define BOARD_NAME BOARD_TYPE
#endif
#define USE_BLYNK_WM true
//#define USE_BLYNK_WM false
#if USE_BLYNK_WM
#define USE_DYNAMIC_PARAMETERS true
#include <BlynkSimpleShieldEsp8266_nRF52_WM.h>
#else
#include <BlynkSimpleShieldEsp8266_nRF52.h>
#if defined(BLYNK_INFO_DEVICE)
#undef BLYNK_INFO_DEVICE
#endif
#define BLYNK_INFO_DEVICE BOARD_TYPE
#define USE_LOCAL_SERVER true
#if USE_LOCAL_SERVER
char auth[] = "****";
String BlynkServer = "account.duckdns.org";
//String BlynkServer = "192.168.2.112";
#else
char auth[] = "****";
String BlynkServer = "blynk-cloud.com";
#endif
#define BLYNK_SERVER_HARDWARE_PORT 8080
// Your WiFi credentials.
char ssid[] = "****";
char pass[] = "****";
#endif
#define HOST_NAME "nRF52_ESP_AT"
// SSID and PW for Config Portal
String portal_ssid = "CfgPrtl-SSID";
String portal_password = "CfgPrtl-PW";
// Your nRF52 <-> ESP8266 baud rate:
#define ESP8266_BAUD 115200
#endif //defines_h
#ifndef Credentials_h
#define Credentials_h
#include "defines.h"
/// Start Default Config Data //////////////////
/*
#define SSID_MAX_LEN 32
//From v1.0.3, WPA2 passwords can be up to 63 characters long.
#define PASS_MAX_LEN 64
typedef struct
{
char wifi_ssid[SSID_MAX_LEN];
char wifi_pw [PASS_MAX_LEN];
} WiFi_Credentials;
#define NUM_WIFI_CREDENTIALS 2
// Configurable items besides fixed Header
#define NUM_CONFIGURABLE_ITEMS ( ( 2 * NUM_WIFI_CREDENTIALS ) + 4 )
////////////////
typedef struct Configuration
{
char header [16];
WiFi_Credentials WiFi_Creds [NUM_WIFI_CREDENTIALS];
char blynk_server [32];
char blynk_token [36];
int checkSum;
} Blynk_WF_Configuration;
*/
#define TO_LOAD_DEFAULT_CONFIG_DATA true
#if TO_LOAD_DEFAULT_CONFIG_DATA
// Use LOAD_DEFAULT_CONFIG_DATA = true in development stage to avoid repeatedly input config data
// Default Config Data will override Data input from Config Portal (CP)
// Use LOAD_DEFAULT_CONFIG_DATA = false in normal operation, and use dummy value here
// Data input from Config Portal (CP) will override Default Config Data
bool LOAD_DEFAULT_CONFIG_DATA = false; //true;
Blynk_WF_Configuration defaultConfig =
{
//char header[16], dummy, not used
"nRF52_ESP_AT",
// WiFi_Credentials WiFi_Creds [NUM_WIFI_CREDENTIALS];
// WiFi_Credentials.wifi_ssid and WiFi_Credentials.wifi_pw
#if 1
"realSSID", "realPass",
"realSSID1", "realPass1",
// Blynk_Creds : blynk_server and blynk_token
"realServer.duckdns.org", "realToken",
#else
"SSID1", "password1",
"SSID2", "password2",
// Blynk_Creds : blynk_server and blynk_token
"account.ddns.net", "token",
#endif
// terminate the list
//int checkSum, dummy, not used
0
/////////// End Default Config Data /////////////
};
#else
bool LOAD_DEFAULT_CONFIG_DATA = false;
Blynk_WF_Configuration defaultConfig;
#endif // TO_LOAD_DEFAULT_CONFIG_DATA
/////////// End Default Config Data /////////////
#endif //Credentials_h
#ifndef dynamicParams_h
#define dynamicParams_h
#if USE_BLYNK_WM
// USE_DYNAMIC_PARAMETERS defined in defined.h
/////////////// Start dynamic Credentials ///////////////
//Defined in <BlynkSimpleShieldEsp8266_nRF52_WM.h>
/**************************************
#define MAX_ID_LEN 5
#define MAX_DISPLAY_NAME_LEN 16
typedef struct
{
char id [MAX_ID_LEN + 1];
char displayName [MAX_DISPLAY_NAME_LEN + 1];
char *pdata;
uint8_t maxlen;
} MenuItem;
**************************************/
#if USE_DYNAMIC_PARAMETERS
#define MAX_MQTT_SERVER_LEN 34
char MQTT_Server [MAX_MQTT_SERVER_LEN + 1] = "mqtt-server";
#define MAX_MQTT_PORT_LEN 6
char MQTT_Port [MAX_MQTT_PORT_LEN + 1] = "1883";
MenuItem myMenuItems [] =
{
{ "mqtt", "MQTT Server", MQTT_Server, MAX_MQTT_SERVER_LEN },
{ "mqpt", "Port", MQTT_Port, MAX_MQTT_PORT_LEN },
};
// Due to notorious 2K buffer limitation of ESO8266-AT shield, the NUM_MENU_ITEMS is limited to max 3
// to avoid WebServer not working due to HTML data larger than 2K can't be sent successfully
// The items with index larger than 3 will be ignored
uint16_t NUM_MENU_ITEMS = sizeof(myMenuItems) / sizeof(MenuItem); //MenuItemSize;
#else
MenuItem myMenuItems [] = {};
uint16_t NUM_MENU_ITEMS = 0;
#endif //USE_DYNAMIC_PARAMETERS
/////// // End dynamic Credentials ///////////
#endif //USE_BLYNK_WM
#endif //dynamicParams_h
Debug Terminal Output Samples
1. nRF52_ESP8266Shield using LittleFS on NRF52840_ITSYBITSY_EXPRESS with ESP8266-AT shield
1.1. No ConfigDat or Forced Config Portal => Config Portal
Start nRF52_ESP8266Shield on NRF52840_ITSYBITSY
Blynk_Esp8266AT_WM v1.3.1
ESP_AT_Lib v1.2.0
DoubleResetDetector_Generic v1.7.2
Start Blynk_ESP8266AT_WM
[7691] AT version:1.7.4.0(May 11 2020 19:13:04)
SDK version:3.0.4(9532ceb)
compile time:May 27 2020 10:12:17
Bin version(Wroom 02):1.7.4
OK
LittleFS Flag read = 0xd0d04321
Flag read = 0xd0d04321
No doubleResetDetected
Saving DOUBLERESETDETECTOR_FLAG to DRD file : 0xd0d01234
Saving DRD file OK
SetFlag write = 0xd0d01234
[8354] LoadCfgFile
[8355] OK
[8356] CCSum=0x1fed,RCSum=0x1fed
[8358] LoadCredFile
[8358] OK
t-server,len=34
[8359] ChkCrR:pdata=1883,len=6
[8359] CrCCsum=0x55e,CrRCsum=0x55e
[8359] Buffer freed
[8362] LoadCredFile
[8362] OK
[8362] CrR:pdata=mqtt-serRCsum=0x55e
[8362] Valid Stored Dynamic Data
[8362] ======= Stet1,PW=12345678
[8363] SSID1=HueNet2,PW1=12345678
[8363] Svr=account.duckdns.org,Prt=8080,Tok=token
[8363] i=0,id=mqtt,data=mqtt-server
[8363] i=1,id=mqpt,data=1883
[8363] Check if isForcedCP
[8367] LoadCPFile
[8367] OK
[8367] bg: isForcedConfigPortal = true
[8367] bg:Stay forever in CP:Forced-Persistent
[ESP_AT] Use ES8266-AT Command
[16807] stConf:SSID=CfgPrtl-SSID,PW=CfgPrtl-PW,IP=192.168.4.1
[16807] SSID=CfgPrtl-SSID,PW=CfgPrtl-PW
[16807] IP=192.168.4.1,CH=11
Stop doubleResetDetecting
Saving to DRD file : 0xd0d04321
Saving DRD file OK
LittleFS Flag read = 0xd0d04321
ClearFlag write = 0xd0d04321
F
Your stored Credentials :
MQTT Server = mqtt-server
Port = 1883
FFFFFFF
1.2. Enter Config Portal and Save Config Data => Connect to Blynk
[245736] h:repl
[245744] h1:myMenuItems[0]=mqtt-server
[245745] h1:myMenuItems[1]=1883
[245745] h:HTML page size:1724
[258383] h:repl id
[258383] h:items updated =1
[258383] h:key =id, value =HueNet1
[258457] h:repl pw
[258457] h:items updated =2
[258457] h:key =pw, value =12345678
[258528] h:repl id1
[258528] h:items updated =3
[258528] h:key =id1, value =HueNet2
[258609] h:repl pw1
[258609] h:items updated =4
[258609] h:key =pw1, value =12345678
[258691] h:repl sv
[258691] h:items updated =5
[258691] h:key =sv, value =account.duckdns.org
[258777] h:repl tk
[258777] h:items updated =6
[258777] h:key =tk, value =token
[258859] h:mqtt=mqtt-server
[258859] h:items updated =7
[258859] h:key =mqtt, value =mqtt-server
[258943] h:mqpt=1883
[258943] h:items updated =8
[258943] h:key =mqpt, value =1883
[258964] h:UpdLittleFS
[258965] SaveCfgFile
[258965] WCSum=0x1fed
[259096] OK
[259096] SaveBkUpCfgFile
[259483] OK
[259485] SaveCredFile
[259485] CW1:pdata=mqtt-server,len=34
[259486] CW1:pdata=1883,len=6
[259746] OK
[259746] CrWCSum=0x55e
[259749] SaveBkUpCredFile
[259749] CW2:pdata=mqtt-server,len=34
[259750] CW2:pdata=1883,len=6
[260008] OK
[260008] clearForcedCP
[260011] SaveCPFile
[260267] OK
[260270] SaveBkUpCPFile
[260526] OK
[260526] h:Rst
Start nRF52_ESP8266Shield on NRF52840_ITSYBITSY
Blynk_Esp8266AT_WM v1.3.1
ESP_AT_Lib v1.2.0
DoubleResetDetector_Generic v1.7.2
Start Blynk_ESP8266AT_WM
[7919] AT version:1.7.4.0(May 11 2020 19:13:04)
SDK version:3.0.4(9532ceb)
compile time:May 27 2020 10:12:17
Bin version(Wroom 02):1.7.4
OK
LittleFS Flag read = 0xd0d04321
Flag read = 0xd0d04321
No doubleResetDetected
Saving DOUBLERESETDETECTOR_FLAG to DRD file : 0xd0d01234
Saving DRD file OK
SetFlag write = 0xd0d01234
[8583] LoadCfgFile
[8583] OK
[8583] CCSum=0x1fed,RCSum=0x1fed
[8585] LoadCredFile
[8585] OK
[8585] ChkCrR: Buffer allocated, Sz=35
[8585] ChkCrR:pdata=mqtt-server,len=34
[8586] ChkCrR:pdata=1883,len=6
[8586] CrCCsum=0x55e,CrRCsum=0x55e
[8586] Buffer freed
en=34
[8588] CrR:pdata=1883,len=6
[8588] CrCCsum=0x55e,CrRCsum=0x55e
[8588] Valid Stored Dynamic Data
[8588] ======= Start Stored Config Data =======
[8588] Hdr=SHD_ESP8266,SSID=HueNet1,PW=12345678
[8589] SSID1=HueNet2,PW1=12345678
[8589] Svr=account.duckdns.orgtt,data=mqtt-server
[8589] i=1,id=mqpt,data=1883
[8589] Check if isForcedCP
[8591] LoadCPFile
[8592] OK
[8592] bg: noConfigPortal = true
[8592]
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ \/ '_/
/____/_/\_, /_//_/_/\_\
/___/ v0.6.1 on NRF52840_ITSYBITSY
[8592] ConMultiWifi
[8592] con2WF:SSID=HueNet1,PW=12345678
[8592] Remaining retry_time=3
[8592] Con2:HueNet1
[15159] AT version:1.7.4.0(May 11 2020 19:13:04)
SDK version:3.0.4(9532ceb)
compile time:May 27 2020 10:12:17
Bin version(Wroom 02):1.7.4
OK
[15697] Mac=5c:cf:7f:66:05:d2
[21714] IP=192.168.2.106
[21731] WOK
[21732] WOK, lastConnectedIndex=0
[21732] con2WF:OK
[21732] IP=192.168.2.106
[21749] b:WOK.TryB
[32008] Ready (ping: 13ms).
[32355] b:WBOK
Stop doubleResetDetecting
Saving to DRD file : 0xd0d04321
Saving DRD file OK
LittleFS Flag read = 0xd0d04321
ClearFlag write = 0xd0d04321
B
Your stored Credentials :
MQTT Server = mqtt-server
Port = 1883
BBBBBBBBB BBBBBBBBBB BBBBBBBBBB BBBBBBBBBB BBBBBBBBBB BBBBBBBBBB BBBBBBBBBB BBBBBBBBBB
CP Button Hit. Rebooting
[175725] setForcedCP non-Persistent
[175727] SaveCPFile
[175856] OK
[175858] SaveBkUpCPFile
[175987] OK
Start nRF52_ESP8266Shield on NRF52840_ITSYBITSY
Blynk_Esp8266AT_WM v1.3.1
ESP_AT_Lib v1.2.0
DoubleResetDetector_Generic v1.7.2
Start Blynk_ESP8266AT_WM
[7466] AT version:1.7.4.0(May 11 2020 19:13:04)
SDK version:3.0.4(9532ceb)
compile time:May 27 2020 10:12:17
Bin version(Wroom 02):1.7.4
OK
LittleFS Flag read = 0xd0d04321
Flag read = 0xd0d04321
No doubleResetDetected
Saving DOUBLERESETDETECTOR_FLAG to DRD file : 0xd0d01234
Saving DRD file OK
SetFlag write = 0xd0d01234
[8129] LoadCfgFile
[8130] OK
[8130] CCSum=0x1fed,RCSum=0x1fed
[8132] LoadCredFile
[8132] OK
[8132] ChkCrR: Buffer allocated, Sz=35
[8132] ChkCrR:pdata=mqtt-server,len=34
[8133] ChkCrR:pdata=1883,len=6
[8133] CrCCsum=0x55e,CrRCsum=0x5 CrR:pdata=mqtt-server,len=34
[8135] CrR:pdata=1883,len=6
[813
[8135] ======= Start Stored Config Data =======
[8135] Hdr=SHD_ESP8266,SSID=HueNet1,PW=12345678
[8136] SSID1=HueNet2,PW1=12345678
[8136] Svr=account.duckdns.org,Prt=8080,Tok=token
[8136] Check if isForcedCP
[8138] LoadCPFile
[8138] OK
[8138] bg: isForcedConfigPortal = true
[8139] bg:Stay forever in CP:Forced-non-Persistent
[8139] clearForcedCP
[8141] SaveCPFile
[8270] OK
[8272] SaveBkUpCPFile
[8400] OK
[ESP_AT] Use ES8266-AT Command
[16842] stConf:SSID=CfgPrtl-SSID,PW=CfgPrtl-PW,IP=192.168.4.1
[16842] SSID=CfgPrtl-SSID,PW=CfgPrtl-PW
[16842] IP=192.168.4.1,CH=2
Stop doubleResetDetecting
Saving to DRD file : 0xd0d04321
Saving DRD file OK
LittleFS Flag read = 0xd0d04321
ClearFlag write = 0xd0d04321
F
Your stored Credentials :
MQTT Server = mqtt-server
Port = 1883
FFFF
Persistent CP Button Hit. Rebooting
[43170] setForcedCP Persistent
[43172] SaveCPFile
[43301] OK
[43303] SaveBkUpCPFile
[43432] OK
Start nRF52_ESP8266Shield on NRF52840_ITSYBITSY
Blynk_Esp8266AT_WM v1.3.1
ESP_AT
> README 内容过长，已截取部分内容。完整内容请前往 GitHub 仓库查看。
评论