- Why do we need this WiFiWebServer library
- Changelog
- Prerequisites
- Installation
- Packages' Patches
- 1. For Adafruit nRF52840 and nRF52832 boards
- 2. For Teensy boards
- 3. For Arduino SAM DUE boards
- 4. For Arduino SAMD boards
- 5. For Adafruit SAMD boards
- 6. For Seeeduino SAMD boards
- 7. For STM32 boards
- 8. For RP2040-based boards using Earle Philhower arduino-pico core
- 9. For Portenta_H7 boards using Arduino IDE in Linux
- 10. For RTL8720DN boards using AmebaD core
- 11. For SAMD21 and SAMD51 boards using ArduinoCore-fab-sam core
- 12. For Seeeduino RP2040 boards
- 13. For Seeeduino nRF52840 boards
- How to configure to use different WiFi Libraries
- Usage
- Examples
- Original Examples
- 1. AdvancedWebServer
- 2. AP_SimpleWebServer
- 3. HelloServer
- 4. HelloServer2
- 5. HttpBasicAuth
- 6. MQTTClient_Auth
- 7. MQTTClient_Basic
- 8. MQTT_ThingStream
- 9. PostServer
- 10. ScanNetworks
- 11. SimpleAuthentication
- 12. UdpNTPClient
- 13. UdpSendReceive
- 14. WebClient
- 15. WebClientRepeating
- 16. WebServer
- 17. WiFiUdpNtpClient
- 18. multiFileProject New
- HTTP and WebSocket Client New Examples
- WiFiMulti Examples New
- Original Examples
- Example AdvancedWebServer
- Debug Terminal Output Samples
- 1. AdvancedWebServer on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 2. SimpleWebSocket on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 3. SimpleHTTPExample on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 4. DweetPost on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 5. DweetGet on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 6. MQTTClient_Auth on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 7. MQTT_ThingStream on Arduino SAMD_NANO_33_IOT using WiFiNINA_Generic Library
- 8. WebClientRepeating on RASPBERRY_PI_PICO with Custom WiFi using Custom WiFi Library
- 9. AdvancedWebServer on Arduino Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
- 10. SimpleHTTPExample on ESP32_DEV
- 11. AdvancedWebServer on PORTENTA_H7_M7 with Portenta_H7 WiFi
- 12. MQTTClient_Auth on ESP32_DEV
- 13. WebClientRepeating on ESP32_DEV
- 14. AdvancedWebServer on ESP32C3_DEV with ESP WiFi
- 15. AdvancedWebServer on ESP32S3_DEV with ESP WiFi
- 16. AdvancedWebServer_WiFiMulti on Nano RP2040 Connect with WiFiNINA
- 17. MQTTClient_Auth_WiFiMulti on Nano RP2040 Connect with WiFiNINA
- 18. WiFiUdpNTPClient_WiFiMulti on Nano RP2040 Connect with WiFiNINA
- 19. AdvancedWebServer_WiFiMulti on RASPBERRY_PI_PICO_W
- Debug
- Troubleshooting
- Issues
- TO DO
- DONE
- Contributions and Thanks
- Contributing
- License
- Copyright
Why do we need this WiFiWebServer library
This WiFiWebServer library is a simple yet complete WebServer library for AVR, Portenta_H7, Teensy, SAM DUE, Arduino SAMD21, Adafruit SAMD21/SAMD51, Adafruit nRF52, ESP32/ESP8266, STM32F/L/H/G/WB/MP1, etc. boards, using WiFi modules/shields (WiFiNINA, WiFi101, U-Blox W101, W102, ESP8266/ESP32-AT, etc.).
The functions are similar and compatible to those of ESP32 WebServer and ESP8266WebServer libraries to make life much easier to port sketches from ESP8266/ESP32.
This WiFiWebServer library, from v1.1.0, also provides high-level HTTP and WebSocket Client with the functions are similar and compatible to those of ArduinoHttpClient Library
The library provides supports to:
- WiFi Client, STA and AP mode
- TCP Server and Client
- UDP Server and Client
- HTTP Server and Client
- HTTP GET and POST requests, provides argument parsing, handles one client at a time.
- High-level HTTP (GET, POST, PUT, PATCH, DELETE) and WebSocket Client. From v1.1.0.
It is based on and modified from:
The WiFiWebServer class found in WiFiWebServer.h header, is a simple web server that knows how to handle HTTP requests such as GET and POST and can only support one client at a time.
The newly-created WiFiMulti-related examples in WiFiMulti demonstrate how to use the new WiFiMulti_Generic library to connect to the best of multi-WiFi APs, with auto-checking / auto-reconnecting features when WiFi connection is lost.
This WiFiWebServer library currently supports these following boards:
-
SAM DUE
-
SAMD21
- Arduino: ZERO, MKR, 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 M44 Express, Trellis M4, Metro M4 AirLift lite, MONSTER M4SK Express, Hallowing EM4 xpress, etc.
- Seeeduino: Wio Terminal, Grove UI Wireless
-
Teensy (4.1, 4.0, 3.6, 3.5, 3,2, 3.1, 3.0, LC)
-
All STM32F/L/H/G/WB/MP1 with more than 32KB flash memory.
-
AVR Mega1280, 2560, ADK, 32U4, 16U4, etc. using Arduino, Adafruit or Sparkfun core. To use patch for
ArduinoSTLlibrary. -
RP2040-based boards, such as Nano RP2040 Connect, or RASPBERRY_PI_PICO_W with CYW43439 WiFi, using Arduino-mbed RP2040 core or Earle Philhower's arduino-pico core
-
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.
-
ESP32
- ESP32 boards, such as
ESP32_DEV, etc. - ESP32S2-based boards, such as
ESP32S2_DEV,ESP32_S2 Saola, etc. - ESP32C3-based boards, such as
ESP32C3_DEV, etc. New - ESP32_S3 (ESP32S3_DEV, ESP32_S3_BOX, UM TINYS3, UM PROS3, UM FEATHERS3, etc.) New
-
ESP8266
-
Portenta_H7
-
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.
-
Arduino
megaAVRboards using Arduino core
- UNO WiFi Rev2 :
WiFi101New - Nano Every :
WiFiEspATNew
- CO2 Ampel
- SAMD :
WiFi101New
-
STM32 using
STM32duino Maplecore. New -
Sparkfun SAMD
- SAMD21, SAMD51 :
WiFiEspATNew
- Industruino SAMD
- D21G : WiFiEspAT New
- Tlera Corp STM32WB boards
- Firefly-WB55RG, Nucleo-WB55RG, etc. :
WiFiEspATNew
- Maixduino boards
- Sipeed Maixduino, etc. :
WiFiEspATNew
-
RTL8720DNusing RealtekAmebaDcore New -
Arduino, Sparkfun, Adafruit, etc. AVR boards (Mega, 32U4, etc.). To use patch for
ArduinoSTLlibrary New
- Arduino Uno / Mega / Duemilanove / Diecimila / LilyPad / Mini / Fio / Nano, etc.
- Arduino ATMega 16U4, 32U4 such as AVR Leonardo, Leonardo ETH, YUN, Esplora, LILYPAD_USB, AVR_ROBOT_CONTROL, AVR_ROBOT_MOTOR, AVR_INDUSTRIAL101, etc.
- Adafruit ATMega 32U4 such as AVR_FLORA8, AVR_FEATHER32U4, AVR_CIRCUITPLAY, AVR_ITSYBITSY32U4_5V, AVR_ITSYBITSY32U4_3V, AVR_BLUEFRUITMICRO, AVR_ADAFRUIT32U4, etc.
- Adafruit ATMega 328(P) such as AVR_METRO, AVR_FEATHER328P, AVR_PROTRINKET5, AVR_PROTRINKET3, AVR_PROTRINKET5FTDI, AVR_PROTRINKET3FTDI, etc.
- Generic or Sparkfun AVR ATmega_32U4 such as AVR_MAKEYMAKEY, AVR_PROMICRO, etc.
- Generic or Sparkfun AVR ATmega_328(P) such as ARDUINO_REDBOT, ARDUINO_AVR_DIGITAL_SANDBOX, etc.
- Generic or Sparkfun AVR ATmega128RFA1 such as ATMEGA128RFA1_DEV_BOARD, etc.
- WiFiNINA using
WiFiNINA_Generic library - WiFi101 using
WiFi101_Generic libraryNew - u-blox W101, W102 using
WiFiNINA_Generic library - ESP8266-AT command using
WiFiEspAT library - ESP8266/ESP32-AT command using
ESP_AT_Lib library - Built-in WiFi of ESP32, ESP8266
- Built-in WiFi of Portenta_H7
- Built-in CYW43439 WiFi of RASPBERRY_PI_PICO_W New
-
ESP32 Core 2.0.5+for ESP32-based boards. -
ESP8266 Core 3.0.2+for ESP8266-based boards..
-
Arduino AVR core 1.8.6+for Arduino (Use Arduino Board Manager) for AVR boards. -
Teensy core v1.57+for Teensy (4.1, 4.0, 3.6, 3.5, 3,2, 3.1, 3.0) boards. -
Arduino SAM DUE core v1.6.12+for SAM DUE ARM Cortex-M3 boards. -
Arduino SAMD core 1.8.13+for SAMD ARM Cortex-M0+ boards. -
Adafruit SAMD core 1.7.11+for SAMD ARM Cortex-M0+ and M4 boards (Nano 33 IoT, etc.). -
Seeeduino SAMD core 1.8.3+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. -
Arduino Core for STM32 v2.3.0+for STM32F/L/H/G/WB/MP1 boards. -
Earle Philhower's arduino-pico core v2.6.3+for RP2040-based boards such as RASPBERRY_PI_PICO, RASPBERRY_PI_PICO_W, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, etc. -
ArduinoCore-mbed mbed_rp2040, mbed_nano, mbed_portenta core 3.4.1+for Arduino (Use Arduino Board Manager) Portenta_H7, RP2040-based boards, such as Nano_RP2040_Connect, RASPBERRY_PI_PICO. -
Arduino megaAVR core 1.8.7+for Arduino megaAVR boards such as UNO_WIFI_REV2, NANO_EVERY -
Functional-Vlpp library v1.0.2+to use server's lambda function. To install, check -
WiFiNINA_Generic library v1.8.15-1+if using WiFiNINA. To install, check.
-
ESP_AT_Lib library v1.4.1+if using ESP8288/ESP32-AT shields. To install, check.
-
WiFi101_Generic library v1.0.0+to use SAMD MKR1000, etc. boards with WiFi101 for sending larger data. To install, check.
-
WiFiEspAT library v1.4.1+if using ESP8288/ESP32-AT shields. -
WiFiMulti_Generic library v1.2.2+to use WiFiMulti function. To install, check. New
The best and easiest way is to use Arduino Library Manager. Search for WiFiWebServer, then select / install the latest version.
You can also use this link
- Navigate to WiFiWebServer page.
- Download the latest release
WiFiWebServer-master.zip. - Extract the zip file to
WiFiWebServer-masterdirectory - Copy the whole
WiFiWebServer-masterfolder to Arduino libraries' directory such as~/Arduino/libraries/.
- Install VS Code
- Install PlatformIO
- Install WiFiWebServer library by using Library Manager. Search for WiFiWebServer 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
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.3.0).
Supposing the Adafruit nRF52 version is 1.3.0. These files must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.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
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.19/hardware/teensy/avr/boards.txt).
Supposing the Arduino version is 1.8.19. These files must be copied into the directory:
./arduino-1.8.19/hardware/teensy/avr/boards.txt./arduino-1.8.19/hardware/teensy/avr/cores/teensy/Stream.h./arduino-1.8.19/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-1.8.19/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
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
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.13).
Supposing the Arduino SAMD version is 1.8.13. Now only one file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/1.8.13/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
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.
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.11).
Supposing the Adafruit SAMD core version is 1.7.11. These files must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/samd/1.7.11/platform.txt~/.arduino15/packages/adafruit/hardware/samd/1.7.11/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/1.7.11/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 These files 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
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.3).
Supposing the Seeeduino SAMD core version is 1.8.3. These files must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/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 These files 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
For Generic STM32F4 series boards, such as STM32F407VE, using LAN8720, please use STM32 core v2.2.0 as breaking core v2.3.0 creates the compile error.
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.2.0/system) to overwrite the old files.
Supposing the STM32 stm32 core version is 2.2.0. These files must be copied into the directory:
~/.arduino15/packages/STM32/hardware/stm32/2.2.0/system/STM32F4xx/stm32f4xx_hal_conf_default.hfor STM32F4.~/.arduino15/packages/STM32/hardware/stm32/2.2.0/system/STM32F7xx/stm32f7xx_hal_conf_default.hfor 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, these 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
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.3.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.3.0. These files must be copied into the directory:
~/.arduino15/packages/STM32/hardware/stm32/2.3.0/variants/STM32F7xx/F765Z(G-I)T_F767Z(G-I)T_F777ZIT/NUCLEO_F767ZI/variant.hfor Nucleo-144 NUCLEO_F767ZI.~/.arduino15/packages/STM32/hardware/stm32/2.3.0/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.hfor 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, these 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. For RP2040-based boards using Earle Philhower arduino-pico core
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.
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.
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/3.4.1/portenta_post_install.sh).
Then run the following command using sudo
$ cd ~/.arduino15/packages/arduino/hardware/mbed_portenta/3.4.1
$ 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 3.4.1. Now only one file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/mbed_portenta/3.4.1/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
To avoid compile error relating to PROGMEM, you have to copy the file Realtek AmebaD core pgmspace.h into Realtek AmebaD directory (~/.arduino15/packages/realtek/hardware/AmebaD/3.1.4/cores/ambd/avr/pgmspace.h).
Supposing the Realtek AmebaD core version is 3.1.4. This file must be copied into the directory:
~/.arduino15/packages/realtek/hardware/AmebaD/3.1.4/cores/ambd/avr/pgmspace.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 into the directory:
~/.arduino15/packages/realtek/hardware/AmebaD/x.yy.zz/cores/ambd/avr/pgmspace.h
To avoid compile error relating to SAMD21/SAMD51, you have to copy the file ArduinoCore-fab-sam core pgmspace.h into ArduinoCore-fab-sam samd directory (~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/1.9.0/boards.txt).
Supposing the ArduinoCore-fab-sam samd core version is 1.9.0. This file must be copied into the directory:
~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/1.9.0/boards.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/Fab_SAM_Arduino/hardware/samd/x.yy.zz/boards.txt
To be able to compile, run and automatically detect and display BOARD_NAME on Seeeduino RP2040 (XIAO RP2040, Wio RP2040 Mini) boards, you have to copy the whole Seeeduino RP2040 Packages_Patches directory into Seeeduino samd directory (~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2).
Supposing the Seeeduino RP2040 core version is 2.7.2. These files must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2/boards.txt~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2/variants/Seeed_XIAO_RP2040/pins_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 These files must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/boards.txt~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/variants/Seeed_XIAO_RP2040/pins_arduino.h
To be able to compile and run on Xiao nRF52840 boards, you have to copy the whole nRF52 1.0.0 directory into Seeeduino nRF52 directory (~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0).
Supposing the Seeeduino nRF52 version is 1.0.0. These files must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/platform.txt~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/cores/nRF5/Print.h~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/cores/nRF5/Print.cpp~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.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/Seeeduino/hardware/nrf52/x.yy.z/platform.txt~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/cores/nRF5/Print.h~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/cores/nRF5/Print.cpp~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h
Please change the pin-to-pin connection in ~/Arduino/libraries/src/WiFiNINA_Pinout_Generic.h to match actual connection if using WiFiNINA with WiFiNINA_Generic library.
For example
#elif ( 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) )
#warning You have to modify pin usage according to actual connection for NRF528XX
// To define pin out for WiFiNINA here
//#define PINS_COUNT (60u)
//NINA
#define NINA_GPIO0 (26u) //26
#define NINA_RESETN (27u)
#define NINA_ACK (28u)
#define SPIWIFI_SS 24 //PIN_SPI1_SS //24
#define SPIWIFI_ACK 28 //NINA_ACK //28
#define SPIWIFI_RESET 27 //NINA_RESETN //27- To use W102-based WiFiNINA, define in the sketch:
#define USE_WIFI_NINA true- To use built-in WiFi101 or shield:
#define USE_WIFI_NINA false
#define USE_WIFI101 true- To use MKR1000 with built-in WiFi101:
// Don't care false or true
#define USE_WIFI_NINA false- For boards other than MKR1000, to use another WiFi library with the standard WiFi.h, such as
WiFiEspAT librarylibrary
#define USE_WIFI_NINA false- To use another WiFi library without the standard WiFi.h
For example, WiFi_XYZ library uses WiFi_XYZ.h
#define USE_WIFI_NINA false
#define USE_WIFI_CUSTOM true
...
//Must be placed before #include <WiFiWebServer.h>
#include <WiFi_XYZ.h>
#include <WiFiWebServer.h>- The WiFiEsp, WiFi_Link libraries are not supported. Don't use unless you know how to modify those libraries.
- Requests to support for any custom WiFi library will be ignored. Use at your own risk.
WiFiWebServer server(80);Creates the WiFiWebServer class object.
Parameters:
host port number: int port (default is the standard HTTP port 80)
Starting the server
void begin();Handling incoming client requests
void handleClient();Disabling the server
void close();
void stop();Both methods function the same
Client request handlers
void on();
void addHandler();
void onNotFound();
void onFileUpload(); Example:
server.on("/", handlerFunction);
server.onNotFound(handlerFunction); // called when handler is not assigned
server.onFileUpload(handlerFunction); // handle file uploadsSending responses to the client
void send();
void send_P();Parameters:
code - HTTP response code, can be 200 or 404, etc.
content_type - HTTP content type, like "text/plain" or "image/png", etc.
content - actual content body
Getting information about request arguments
const String & arg();
const String & argName();
int args();
bool hasArg();Function usage:
arg - get request argument value, use arg("plain") to get POST body
argName - get request argument name
args - get arguments count
hasArg - check if argument exist
Getting information about request headers
const String & header();
const String & headerName();
const String & hostHeader();
int headers();
bool hasHeader();Function usage:
header - get request header value
headerName - get request header name
hostHeader - get request host header if available, else empty string
headers - get header count
hasHeader - check if header exist
Authentication
bool authenticate();
void requestAuthentication();Function usage:
authenticate - server authentication, returns true if client is authenticated else false
requestAuthentication - sends authentication failure response to the client
Example Usage:
if(!server.authenticate(username, password))
{
server.requestAuthentication();
} const String& uri(); // get the current uri
HTTPMethod method(); // get the current method
WiFiClient client(); // get the current client
HTTPUpload& upload(); // get the current upload
void setContentLength(); // set content length
void sendHeader(); // send HTTP header
void sendContent(); // send content
void sendContent_P();
void collectHeaders(); // set the request headers to collect
void serveStatic();
size_t streamFile();- AdvancedWebServer
- AP_SimpleWebServer
- HelloServer
- HelloServer2
- HttpBasicAuth
- MQTTClient_Auth
- MQTTClient_Basic
- MQTT_ThingStream
- PostServer
- ScanNetworks
- SimpleAuthentication
- UdpNTPClient
- UdpSendReceive
- WebClient
- WebClientRepeating
- WebServer
- WiFiUdpNtpClient
- multiFileProject New
- BasicAuthGet
- CustomHeader
- DweetGet
- DweetPost
- HueBlink
- node_test_server
- PostWithHeaders
- SimpleDelete
- SimpleGet
- SimpleHTTPExample
- SimplePost
- SimplePut
- SimpleWebSocket
- AdvancedWebServer_WiFiMulti
- MQTTClient_Auth_WiFiMulti
- MQTTClient_Basic_WiFiMulti
- MQTT_ThingStream_WiFiMulti
- WiFiUdpNtpClient_WiFiMulti
- WebClient_WiFiMulti
- WebClientRepeating_WiFiMulti
- WebServer_WiFiMulti
Example AdvancedWebServer
1. File AdvancedWebServer.ino
WiFiWebServer/examples/AdvancedWebServer/AdvancedWebServer.ino
Lines 40 to 327 in 9094e54
2. File defines.h
WiFiWebServer/examples/AdvancedWebServer/defines.h
Lines 12 to 409 in 9094e54
The following are debug terminal output and screen shot when running example AdvancedWebServer on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
Starting AdvancedServer on SAMD_NANO_33_IOT
WiFiWebServer v1.10.1
[NN] ===============================
[NN]
Used/default SPI pinout:
[NN] MOSI: 11
[NN] MISO: 12
[NN] SCK: 13
[NN] SS: 10
[NN] ===============================
[NN]
Used/default NINA pinout:
[NN] NINA_GPIO0: 26
[NN] NINA_RESETN/SPIWIFI_RESET: 27
[NN] NINA_ACK: 28
[NN] SS: 10
[NN] ===============================
[NN]
Actual final pinout to used:
[NN] SPIWIFI_SS: 24
[NN] SLAVESELECT/SPIWIFI_SS: 24
[NN] SLAVEREADY/SPIWIFI_ACK/NINA_ACK: 28
[NN] SLAVERESET/SPIWIFI_RESET/NINA_RESETN: 27
[NN] ===============================
Connecting to WPA SSID: HueNet1
HTTP server started @ 192.168.2.118
H[WIFI] String Len = 0, extend to 2048
WiFiWebServer::handleClient: New Client
method: GET
url: /
search:
headerName: Host
headerValue: 192.168.2.118
headerName: Connection
headerValue: keep-alive
headerName: Cache-Control
headerValue: max-age=0
headerName: DNT
headerValue: 1
headerName: Upgrade-Insecure-Requests
headerValue: 1
headerName: User-Agent
headerValue: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36
headerName: Accept
headerValue: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
headerName: Accept-Encoding
headerValue: gzip, deflate
headerName: Accept-Language
headerValue: en-GB,en-US;q=0.9,en;q=0.8
headerName: Cookie
headerValue: NINASESSIONID=0
args:
args count: 0
args:
args count: 0
Request: /
Arguments:
Final list of key/value pairs:
WiFiWebServer::_handleRequest handle
WiFiWebServer::send1: len = 330
content = <html><head><meta http-equiv='refresh' content='5'/><title>WiFiNINA SAMD_NANO_33_IOT</title><style>body { background-color: #cccccc; font-family: Arial, Helvetica, Sans-Serif; Color: #000088; }</style></head><body><h1>Hello from WiFiNINA</h1><h2>on SAMD_NANO_33_IOT</h2><p>Uptime: 00:00:20</p><img src="/test.svg" /></body></html>
WiFiWebServer::_prepareHeader sendHeader Conn close
WiFiWebServer::send1: write header = HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 330
Connection: close
WiFiWebServer::sendContent: Client.write content: <html><head><meta http-equiv='refresh' content='5'/><title>WiFiNINA SAMD_NANO_33_IOT</title><style>body { background-color: #cccccc; font-family: Arial, Helvetica, Sans-Serif; Color: #000088; }</style></head><body><h1>Hello from WiFiNINA</h1><h2>on SAMD_NANO_33_IOT</h2><p>Uptime: 00:00:20</p><img src="/test.svg" /></body></html>
WiFiWebServer::_handleRequest OK
WiFiWebServer::handleClient: Client disconnected
WiFiWebServer::handleClient: Don't keepCurrentClient
WiFiWebServer::handleClient: Client disconnected
WiFiWebServer::handleClient: New Client
method: GET
url: /test.svg
search:
headerName: Host
headerValue: 192.168.2.118
headerName: Connection
headerValue: keep-alive
headerName: User-Agent
headerValue: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36
headerName: DNT
headerValue: 1
headerName: Accept
headerValue: image/webp,image/apng,image/*,*/*;q=0.8
headerName: Referer
headerValue: http://192.168.2.118/
headerName: Accept-Encoding
headerValue: gzip, deflate
headerName: Accept-Language
headerValue: en-GB,en-US;q=0.9,en;q=0.8
headerName: Cookie
headerValue: NINASESSIONID=0
args:
args count: 0
args:
args count: 0
Request: /test.svg
Arguments:
Final list of key/value pairs:
WiFiWebServer::_handleRequest handle
WiFiWebServer::send1: len = 1946
content = <svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="310" height="150">
<rect width="310" height="150" fill="rgb(250, 230, 210)" stroke-width="1" stroke="rgb(0, 0, 0)" />
<g stroke="black">
<line x1="10" y1="77" x2="20" y2="67" stroke-width="1" />
<line x1="20" y1="67" x2="30" y2="98" stroke-width="1" />
<line x1="30" y1="98" x2="40" y2="111" stroke-width="1" />
<line x1="40" y1="111" x2="50" y2="90" stroke-width="1" />
<line x1="50" y1="90" x2="60" y2="22" stroke-width="1" />
<line x1="60" y1="22" x2="70" y2="98" stroke-width="1" />
<line x1="70" y1="98" x2="80" y2="64" stroke-width="1" />
<line x1="80" y1="64" x2="90" y2="104" stroke-width="1" />
<line x1="90" y1="104" x2="100" y2="31" stroke-width="1" />
<line x1="100" y1="31" x2="110" y2="59" stroke-width="1" />
<line x1="110" y1="59" x2="120" y2="139" stroke-width="1" />
<line x1="120" y1="139" x2="130" y2="117" stroke-width="1" />
<line x1="130" y1="117" x2="140" y2="75" stroke-width="1" />
<line x1="140" y1="75" x2="150" y2="72" stroke-width="1" />
<line x1="150" y1="72" x2="160" y2="137" stroke-width="1" />
<line x1="160" y1="137" x2="170" y2="20" stroke-width="1" />
<line x1="170" y1="20" x2="180" y2="94" stroke-width="1" />
<line x1="180" y1="94" x2="190" y2="81" stroke-width="1" />
<line x1="190" y1="81" x2="200" y2="38" stroke-width="1" />
<line x1="200" y1="38" x2="210" y2="33" stroke-width="1" />
<line x1="210" y1="33" x2="220" y2="53" stroke-width="1" />
<line x1="220" y1="53" x2="230" y2="88" stroke-width="1" />
<line x1="230" y1="88" x2="240" y2="32" stroke-width="1" />
<line x1="240" y1="32" x2="250" y2="110" stroke-width="1" />
<line x1="250" y1="110" x2="260" y2="87" stroke-width="1" />
<line x1="260" y1="87" x2="270" y2="11" stroke-width="1" />
<line x1="270" y1="11" x2="280" y2="98" stroke-width="1" />
<line x1="280" y1="98" x2="290" y2="76" stroke-width="1" />
<line x1="290" y1="76" x2="300" y2="121" stroke-width="1" />
</g>
</svg>
WiFiWebServer::_prepareHeader sendHeader Conn close
WiFiWebServer::send1: write header = HTTP/1.1 200 OK
Content-Type: image/svg+xml
Content-Length: 1946
Connection: closeThe terminal output of SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library running SimpleWebSocket example to demonstrate newly-added WebSocket Client feature.
Starting SimpleWebSocket on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.98
SSID: HueNet1, Signal strength (RSSI):-24 dBm
starting WebSocket client
Sending Hello 0
Sending Hello 1
Received a message:
0 => Hello from SimpleWebSocket on SAMD_NANO_33_IOT, millis = 6642
Sending Hello 2
Received a message:
1 => Hello from SimpleWebSocket on SAMD_NANO_33_IOT, millis = 11648
Sending Hello 3
Received a message:
2 => Hello from SimpleWebSocket on SAMD_NANO_33_IOT, millis = 16655
Sending Hello 4
Received a message:
3 => Hello from SimpleWebSocket on SAMD_NANO_33_IOT, millis = 21661
Sending Hello 5
Received a message:
4 => Hello from SimpleWebSocket on SAMD_NANO_33_IOT, millis = 26668
Sending Hello 6
Received a message:
5 => Hello from SimpleWebSocket on SAMD_NANO_33_IOT, millis = 31675The terminal output of SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library running SimpleHTTPExample example to demonstrate newly-added HTTP Client feature.
Starting SimpleHTTPExample on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.98
SSID: HueNet1, Signal strength (RSSI):-21 dBm
startedRequest ok
Got status code: 200
Content length is: 2263
Body returned follows:
`:;;;,` .:;;:.
.;;;;;;;;;;;` :;;;;;;;;;;: TM
`;;;;;;;;;;;;;;;` :;;;;;;;;;;;;;;;
:;;;;;;;;;;;;;;;;;; `;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;; .;;;;;;;;;;;;;;;;;;;;
;;;;;;;;:` `;;;;;;;;; ,;;;;;;;;.` .;;;;;;;;
.;;;;;;, :;;;;;;; .;;;;;;; ;;;;;;;
;;;;;; ;;;;;;; ;;;;;;, ;;;;;;.
,;;;;; ;;;;;;.;;;;;;` ;;;;;;
;;;;;. ;;;;;;;;;;;` ``` ;;;;;`
;;;;; ;;;;;;;;;, ;;; .;;;;;
`;;;;: `;;;;;;;; ;;; ;;;;;
,;;;;` `,,,,,,,, ;;;;;;; .,,;;;,,, ;;;;;
:;;;;` .;;;;;;;; ;;;;;, :;;;;;;;; ;;;;;
:;;;;` .;;;;;;;; `;;;;;; :;;;;;;;; ;;;;;
.;;;;. ;;;;;;;. ;;; ;;;;;
;;;;; ;;;;;;;;; ;;; ;;;;;
;;;;; .;;;;;;;;;; ;;; ;;;;;,
;;;;;; `;;;;;;;;;;;; ;;;;;
`;;;;;, .;;;;;; ;;;;;;; ;;;;;;
;;;;;;: :;;;;;;. ;;;;;;; ;;;;;;
;;;;;;;` .;;;;;;;, ;;;;;;;; ;;;;;;;:
;;;;;;;;;:,:;;;;;;;;;: ;;;;;;;;;;:,;;;;;;;;;;
`;;;;;;;;;;;;;;;;;;;. ;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;; :;;;;;;;;;;;;;;;;:
,;;;;;;;;;;;;;, ;;;;;;;;;;;;;;
.;;;;;;;;;` ,;;;;;;;;:
;;; ;;;;;` ;;;;: .;; ;; ,;;;;;, ;;. `;, ;;;;
;;; ;;:;;; ;;;;;; .;; ;; ,;;;;;: ;;; `;, ;;;:;;
,;:; ;; ;; ;; ;; .;; ;; ,;, ;;;,`;, ;; ;;
;; ;: ;; ;; ;; ;; .;; ;; ,;, ;;;;`;, ;; ;;.
;: ;; ;;;;;: ;; ;; .;; ;; ,;, ;;`;;;, ;; ;;`
,;;;;; ;;`;; ;; ;; .;; ;; ,;, ;; ;;;, ;; ;;
;; ,;, ;; .;; ;;;;;: ;;;;;: ,;;;;;: ;; ;;, ;;;;;;
;; ;; ;; ;;` ;;;;. `;;;: ,;;;;;, ;; ;;, ;;;;
The terminal output of SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library running DweetPost example to demonstrate newly-added HTTP Client feature.
Starting DweetPost on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.98
SSID: HueNet1, Signal strength (RSSI):-22 dBm
making POST request
Status code: 200
Response: {"this":"succeeded","by":"dweeting","the":"dweet","with":{"thing":"Hello-from-SAMD_NANO_33_IOT","created":"2020-11-17T19:55:37.378Z","content":{"sensorValue":581},"transaction":"f968ee5f-35b5-4984-ac3d-34d93fdaddbe"}}
Wait ten seconds
making POST request
Status code: 200
Response: {"this":"succeeded","by":"dweeting","the":"dweet","with":{"thing":"Hello-from-SAMD_NANO_33_IOT","created":"2020-11-17T19:55:48.925Z","content":{"sensorValue":570},"transaction":"68ee52e0-22a3-4af2-96cd-aaa53587b314"}}
Wait ten secondsThe terminal output of SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library running DweetGet example to demonstrate newly-added HTTP Client feature.
Starting DweetGet on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.98
SSID: HueNet1, Signal strength (RSSI):-25 dBm
Making GET request
Status code: 200
Response: {"this":"succeeded","by":"getting","the":"dweets","with":[{"thing":"Hello-from-SAMD_NANO_33_IOT","created":"2020-11-17T20:06:18.905Z","content":{"sensorValue":567}}]}
"sensorValue":567
Value string: 567
Actual value: 567
Wait ten seconds
Making GET request
Status code: 200
Response: {"this":"succeeded","by":"getting","the":"dweets","with":[{"thing":"Hello-from-SAMD_NANO_33_IOT","created":"2020-11-17T20:06:18.905Z","content":{"sensorValue":567}}]}
"sensorValue":567
Value string: 567
Actual value: 567
Wait ten secondsThe terminal output of SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library running MQTTClient_Auth example to demonstrate newly-added MQTT Client feature.
Starting MQTTClient_Auth on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Please upgrade the firmware
Connecting to WPA SSID: HueNet1
Connected! IP address: 192.168.2.98
Attempting MQTT connection to broker.emqx.io...connected
Message Send : MQTT_Pub => Hello from MQTTClient_Auth on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
Message arrived [MQTT_Pub] Hello from MQTTClient_Auth on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
Message Send : MQTT_Pub => Hello from MQTTClient_Auth on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
Message arrived [MQTT_Pub] Hello from MQTTClient_Auth on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic LibraryThe terminal output of SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library running MQTT_ThingStream example to demonstrate newly-added MQTT Client feature.
Start MQTT_ThingStream on SAMD_NANO_33_IOT
Starting MQTTClient_Auth on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Please upgrade the firmware
Connecting to WPA SSID: HueNet1
Connected! IP address: 192.168.2.98
***************************************
STM32_Pub
***************************************
Attempting MQTT connection to broker.emqx.io
...connected
Published connection message successfully!
Subscribed to: STM32_Sub
MQTT Message Send : STM32_Pub => Hello from MQTT_ThingStream on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
MQTT Message receive [STM32_Pub] Hello from MQTT_ThingStream on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
MQTT Message Send : STM32_Pub => Hello from MQTT_ThingStream on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
MQTT Message receive [STM32_Pub] Hello from MQTT_ThingStream on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
MQTT Message Send : STM32_Pub => Hello from MQTT_ThingStream on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
MQTT Message receive [STM32_Pub] Hello from MQTT_ThingStream on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
The terminal output of RASPBERRY_PI_PICO with Custom WiFi (ESP8266-AT) using Custom WiFi (WiFiEspAT) Library running WebClientRepeating example to demonstrate new RP2040-based board using Earle Philhower's arduino-pico core
Starting WebClientRepeating on RASPBERRY_PI_PICO with Custom WiFi using Custom WiFi Library
WiFiWebServer v1.10.1
WiFi shield init done
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.76
SSID: HueNet1, Signal strength (RSSI):-29 dBm
Connecting...
HTTP/1.1 200 OK
Server: nginx/1.4.2
Date: Wed, 26 May 2021 03:56:08 GMT
Content-Type: text/plain
Content-Length: 2263
Last-Modified: Wed, 02 Oct 2013 13:46:47 GMT
Connection: close
Vary: Accept-Encoding
ETag: "524c23c7-8d7"
Accept-Ranges: bytes
`:;;;,` .:;;:.
.;;;;;;;;;;;` :;;;;;;;;;;: TM
`;;;;;;;;;;;;;;;` :;;;;;;;;;;;;;;;
:;;;;;;;;;;;;;;;;;; `;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;; .;;;;;;;;;;;;;;;;;;;;
;;;;;;;;:` `;;;;;;;;; ,;;;;;;;;.` .;;;;;;;;
.;;;;;;, :;;;;;;; .;;;;;;; ;;;;;;;
;;;;;; ;;;;;;; ;;;;;;, ;;;;;;.
,;;;;; ;;;;;;.;;;;;;` ;;;;;;
;;;;;. ;;;;;;;;;;;` ``` ;;;;;`
;;;;; ;;;;;;;;;, ;;; .;;;;;
`;;;;: `;;;;;;;; ;;; ;;;;;
,;;;;` `,,,,,,,, ;;;;;;; .,,;;;,,, ;;;;;
:;;;;` .;;;;;;;; ;;;;;, :;;;;;;;; ;;;;;
:;;;;` .;;;;;;;; `;;;;;; :;;;;;;;; ;;;;;
.;;;;. ;;;;;;;. ;;; ;;;;;
;;;;; ;;;;;;;;; ;;; ;;;;;
;;;;; .;;;;;;;;;; ;;; ;;;;;,
;;;;;; `;;;;;;;;;;;; ;;;;;
`;;;;;, .;;;;;; ;;;;;;; ;;;;;;
;;;;;;: :;;;;;;. ;;;;;;; ;;;;;;
;;;;;;;` .;;;;;;;, ;;;;;;;; ;;;;;;;:
;;;;;;;;;:,:;;;;;;;;;: ;;;;;;;;;;:,;;;;;;;;;;
`;;;;;;;;;;;;;;;;;;;. ;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;; :;;;;;;;;;;;;;;;;:
,;;;;;;;;;;;;;, ;;;;;;;;;;;;;;
.;;;;;;;;;` ,;;;;;;;;:
;;; ;;;;;` ;;;;: .;; ;; ,;;;;;, ;;. `;, ;;;;
;;; ;;:;;; ;;;;;; .;; ;; ,;;;;;: ;;; `;, ;;;:;;
,;:; ;; ;; ;; ;; .;; ;; ,;, ;;;,`;, ;; ;;
;; ;: ;; ;; ;; ;; .;; ;; ,;, ;;;;`;, ;; ;;.
;: ;; ;;;;;: ;; ;; .;; ;; ,;, ;;`;;;, ;; ;;`
,;;;;; ;;`;; ;; ;; .;; ;; ,;, ;; ;;;, ;; ;;
;; ,;, ;; .;; ;;;;;: ;;;;;: ,;;;;;: ;; ;;, ;;;;;;
;; ;; ;; ;;` ;;;;. `;;;: ,;;;;;, ;; ;;, ;;;; The following are debug terminal output and screen shot when running example AdvancedWebServer on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
Starting AdvancedServer on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
WiFiWebServer v1.10.1
Connecting to WPA SSID: HueNet1
HTTP server started @ 192.168.2.130
H[WIFI] handleClient: New Client
[WIFI] method: GET
[WIFI] url: /
[WIFI] search:
[WIFI] headerName: Host
[WIFI] headerValue: 192.168.2.130
[WIFI] headerName: Connection
[WIFI] headerValue: keep-alive
[WIFI] headerName: Cache-Control
[WIFI] headerValue: max-age=0
[WIFI] headerName: Upgrade-Insecure-Requests
[WIFI] headerValue: 1
[WIFI] headerName: DNT
[WIFI] headerValue: 1
[WIFI] headerName: User-Agent
[WIFI] headerValue: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36
[WIFI] headerName: Accept
[WIFI] headerValue: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
[WIFI] headerName: Referer
[WIFI] headerValue: http://192.168.2.130/
[WIFI] headerName: Accept-Encoding
[WIFI] headerValue: gzip, deflate
[WIFI] headerName: Accept-Language
[WIFI] headerValue: en-GB,en-US;q=0.9,en;q=0.8,vi;q=0.7
[WIFI] args:
[WIFI] args count: 0
[WIFI] args:
[WIFI] args count: 0
[WIFI] Request: /
[WIFI] Arguments:
[WIFI] Final list of key/value pairs:
[WIFI] _handleRequest handle
[WIFI] send1: len = 392
[WIFI] content = <html><head><meta http-equiv='refresh' content='5'/><title>Nano RP2040 Connect</title><style>body { background-color: #cccccc; font-family: Arial, Helvetica, Sans-Serif; Color: #000088; }</style></head><body><h1>Hello from Nano RP2040 Connect</h1><h3>running WiFiWebServer</h3><h3>on WiFiNINA using WiFiNINA_Generic Library</h3><p>Uptime: 0 d 00:00:12</p><img src="/test.svg" /></body></html>
[WIFI] _prepareHeader sendHeader Conn close
[WIFI] send1: write header = HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 392
Connection: close
[WIFI] sendContent: Client.write content: <html><head><meta http-equiv='refresh' content='5'/><title>Nano RP2040 Connect</title><style>body { background-color: #cccccc; font-family: Arial, Helvetica, Sans-Serif; Color: #000088; }</style></head><body><h1>Hello from Nano RP2040 Connect</h1><h3>running WiFiWebServer</h3><h3>on WiFiNINA using WiFiNINA_Generic Library</h3><p>Uptime: 0 d 00:00:12</p><img src="/test.svg" /></body></html>
[WIFI] _handleRequest OK
[WIFI] handleClient: Client disconnected
[WIFI] handleClient: Don't keepCurrentClient
[WIFI] handleClient: Client disconnected
[WIFI] handleClient: New Client
[WIFI] method: GET
[WIFI] url: /test.svg
[WIFI] search:
[WIFI] headerName: Host
[WIFI] headerValue: 192.168.2.130
[WIFI] headerName: Connection
[WIFI] headerValue: keep-alive
[WIFI] headerName: User-Agent
[WIFI] headerValue: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36
[WIFI] headerName: DNT
[WIFI] headerValue: 1
[WIFI] headerName: Accept
[WIFI] headerValue: image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
[WIFI] headerName: Referer
[WIFI] headerValue: http://192.168.2.130/
[WIFI] headerName: Accept-Encoding
[WIFI] headerValue: gzip, deflate
[WIFI] headerName: Accept-Language
[WIFI] headerValue: en-GB,en-US;q=0.9,en;q=0.8,vi;q=0.7
[WIFI] args:
[WIFI] args count: 0
[WIFI] args:
[WIFI] args count: 0
[WIFI] Request: /test.svg
[WIFI] Arguments:
[WIFI] Final list of key/value pairs:
[WIFI] _handleRequest handle
[WIFI] send1: len = 1954
[WIFI] content = <svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="310" height="150">
<rect width="310" height="150" fill="rgb(250, 230, 210)" stroke-width="3" stroke="rgb(0, 0, 0)" />
<g stroke="blue">
<line x1="10" y1="77" x2="20" y2="92" stroke-width="2" />
<line x1="20" y1="92" x2="30" y2="123" stroke-width="2" />
<line x1="30" y1="123" x2="40" y2="136" stroke-width="2" />
<line x1="40" y1="136" x2="50" y2="115" stroke-width="2" />
<line x1="50" y1="115" x2="60" y2="47" stroke-width="2" />
<line x1="60" y1="47" x2="70" y2="123" stroke-width="2" />
<line x1="70" y1="123" x2="80" y2="89" stroke-width="2" />
<line x1="80" y1="89" x2="90" y2="129" stroke-width="2" />
<line x1="90" y1="129" x2="100" y2="56" stroke-width="2" />
<line x1="100" y1="56" x2="110" y2="83" stroke-width="2" />
<line x1="110" y1="83" x2="120" y2="33" stroke-width="2" />
<line x1="120" y1="33" x2="130" y2="11" stroke-width="2" />
<line x1="130" y1="11" x2="140" y2="99" stroke-width="2" />
<line x1="140" y1="99" x2="150" y2="96" stroke-width="2" />
<line x1="150" y1="96" x2="160" y2="31" stroke-width="2" />
<line x1="160" y1="31" x2="170" y2="44" stroke-width="2" />
<line x1="170" y1="44" x2="180" y2="118" stroke-width="2" />
<line x1="180" y1="118" x2="190" y2="105" stroke-width="2" />
<line x1="190" y1="105" x2="200" y2="62" stroke-width="2" />
<line x1="200" y1="62" x2="210" y2="57" stroke-width="2" />
<line x1="210" y1="57" x2="220" y2="77" stroke-width="2" />
<line x1="220" y1="77" x2="230" y2="111" stroke-width="2" />
<line x1="230" y1="111" x2="240" y2="55" stroke-width="2" />
<line x1="240" y1="55" x2="250" y2="133" stroke-width="2" />
<line x1="250" y1="133" x2="260" y2="110" stroke-width="2" />
<line x1="260" y1="110" x2="270" y2="34" stroke-width="2" />
<line x1="270" y1="34" x2="280" y2="121" stroke-width="2" />
<line x1="280" y1="121" x2="290" y2="99" stroke-width="2" />
<line x1="290" y1="99" x2="300" y2="14" stroke-width="2" />
</g>
</svg>
[WIFI] _prepareHeader sendHeader Conn close
[WIFI] send1: write header = HTTP/1.1 200 OK
Content-Type: image/svg+xml
Content-Length: 1954
Connection: close
The terminal output of ESP32_DEV running SimpleHTTPExample example to demonstrate newly-added HTTP Client feature.
Starting SimpleHTTPExample on ESP32_DEV with ESP WiFi using WiFi Library
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.80
SSID: HueNet1, Signal strength (RSSI):-23 dBm
startedRequest ok
Got status code: 200
Content length is: 2263
Body returned follows:
`:;;;,` .:;;:.
.;;;;;;;;;;;` :;;;;;;;;;;: TM
`;;;;;;;;;;;;;;;` :;;;;;;;;;;;;;;;
:;;;;;;;;;;;;;;;;;; `;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;; .;;;;;;;;;;;;;;;;;;;;
;;;;;;;;:` `;;;;;;;;; ,;;;;;;;;.` .;;;;;;;;
.;;;;;;, :;;;;;;; .;;;;;;; ;;;;;;;
;;;;;; ;;;;;;; ;;;;;;, ;;;;;;.
,;;;;; ;;;;;;.;;;;;;` ;;;;;;
;;;;;. ;;;;;;;;;;;` ``` ;;;;;`
;;;;; ;;;;;;;;;, ;;; .;;;;;
`;;;;: `;;;;;;;; ;;; ;;;;;
,;;;;` `,,,,,,,, ;;;;;;; .,,;;;,,, ;;;;;
:;;;;` .;;;;;;;; ;;;;;, :;;;;;;;; ;;;;;
:;;;;` .;;;;;;;; `;;;;;; :;;;;;;;; ;;;;;
.;;;;. ;;;;;;;. ;;; ;;;;;
;;;;; ;;;;;;;;; ;;; ;;;;;
;;;;; .;;;;;;;;;; ;;; ;;;;;,
;;;;;; `;;;;;;;;;;;; ;;;;;
`;;;;;, .;;;;;; ;;;;;;; ;;;;;;
;;;;;;: :;;;;;;. ;;;;;;; ;;;;;;
;;;;;;;` .;;;;;;;, ;;;;;;;; ;;;;;;;:
;;;;;;;;;:,:;;;;;;;;;: ;;;;;;;;;;:,;;;;;;;;;;
`;;;;;;;;;;;;;;;;;;;. ;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;; :;;;;;;;;;;;;;;;;:
,;;;;;;;;;;;;;, ;;;;;;;;;;;;;;
.;;;;;;;;;` ,;;;;;;;;:
;;; ;;;;;` ;;;;: .;; ;; ,;;;;;, ;;. `;, ;;;;
;;; ;;:;;; ;;;;;; .;; ;; ,;;;;;: ;;; `;, ;;;:;;
,;:; ;; ;; ;; ;; .;; ;; ,;, ;;;,`;, ;; ;;
;; ;: ;; ;; ;; ;; .;; ;; ,;, ;;;;`;, ;; ;;.
;: ;; ;;;;;: ;; ;; .;; ;; ,;, ;;`;;;, ;; ;;`
,;;;;; ;;`;; ;; ;; .;; ;; ,;, ;; ;;;, ;; ;;
;; ,;, ;; .;; ;;;;;: ;;;;;: ,;;;;;: ;; ;;, ;;;;;;
;; ;; ;; ;;` ;;;;. `;;;: ,;;;;;, ;; ;;, ;;;;
Got status code: 200
Content length is: 2263 The following are debug terminal output and screen shot when running example AdvancedWebServer on PORTENTA_H7_M7 with Portenta_H7 WiFi
Starting AdvancedServer on PORTENTA_H7_M7 with Portenta_H7 WiFi
WiFiWebServer v1.10.1
Connecting to WPA SSID: HueNet1
HTTP server started @ 192.168.2.138
H[WIFI] String Len = 0, extend to 2048
HHHHHHHHH HHHHHHHThe terminal output of PORTENTA_H7_M7 with Portenta_H7 WiFi running MQTTClient_Auth example to demonstrate MQTT Client feature.
Starting MQTTClient_Auth on PORTENTA_H7_M7 with Portenta_H7 WiFi
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
Connected! IP address: 192.168.2.130
Attempting MQTT connection to broker.emqx.io...connected
Message Send : MQTT_Pub => Hello from MQTTClient_Auth on PORTENTA_H7_M7 with Portenta_H7 WiFi
Message arrived [MQTT_Pub] Hello from MQTTClient_Auth on PORTENTA_H7_M7 with Portenta_H7 WiFi
Message Send : MQTT_Pub => Hello from MQTTClient_Auth on PORTENTA_H7_M7 with Portenta_H7 WiFi
Message arrived [MQTT_Pub] Hello from MQTTClient_Auth on PORTENTA_H7_M7 with Portenta_H7 WiFiThe terminal output of PORTENTA_H7_M7 with Portenta_H7 WiFi running WebClientRepeating example.
Starting WebClientRepeating on PORTENTA_H7_M7 with Portenta_H7 WiFi
WiFiWebServer v1.10.1
Connecting to SSID: HueNet1
You're connected to the network, IP = 192.168.2.130
SSID: HueNet1, Signal strength (RSSI):-33 dBm
Connecting...
HTTP/1.1 200 OK
Server: nginx/1.4.2
Date: Wed, 08 Sep 2021 01:29:41 GMT
Content-Type: text/plain
Content-Length: 2263
Last-Modified: Wed, 02 Oct 2013 13:46:47 GMT
Connection: close
Vary: Accept-Encoding
ETag: "524c23c7-8d7"
Accept-Ranges: bytes
`:;;;,` .:;;:.
.;;;;;;;;;;;` :;;;;;;;;;;: TM
`;;;;;;;;;;;;;;;` :;;;;;;;;;;;;;;;
:;;;;;;;;;;;;;;;;;; `;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;; .;;;;;;;;;;;;;;;;;;;;
;;;;;;;;:` `;;;;;;;;; ,;;;;;;;;.` .;;;;;;;;
.;;;;;;, :;;;;;;; .;;;;;;; ;;;;;;;
;;;;;; ;;;;;;; ;;;;;;, ;;;;;;.
,;;;;; ;;;;;;.;;;;;;` ;;;;;;
;;;;;. ;;;;;;;;;;;` ``` ;;;;;`
;;;;; ;;;;;;;;;, ;;; .;;;;;
`;;;;: `;;;;;;;; ;;; ;;;;;
,;;;;` `,,,,,,,, ;;;;;;; .,,;;;,,, ;;;;;
:;;;;` .;;;;;;;; ;;;;;, :;;;;;;;; ;;;;;
:;;;;` .;;;;;;;; `;;;;;; :;;;;;;;; ;;;;;
.;;;;. ;;;;;;;. ;;; ;;;;;
;;;;; ;;;;;;;;; ;;; ;;;;;
;;;;; .;;;;;;;;;; ;;; ;;;;;,
;;;;;; `;;;;;;;;;;;; ;;;;;
`;;;;;, .;;;;;; ;;;;;;; ;;;;;;
;;;;;;: :;;;;;;. ;;;;;;; ;;;;;;
;;;;;;;` .;;;;;;;, ;;;;;;;; ;;;;;;;:
;;;;;;;;;:,:;;;;;;;;;: ;;;;;;;;;;:,;;;;;;;;;;
`;;;;;;;;;;;;;;;;;;;. ;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;; :;;;;;;;;;;;;;;;;:
,;;;;;;;;;;;;;, ;;;;;;;;;;;;;;
.;;;;;;;;;` ,;;;;;;;;:
;;; ;;;;;` ;;;;: .;; ;; ,;;;;;, ;;. `;, ;;;;
;;; ;;:;;; ;;;;;; .;; ;; ,;;;;;: ;;; `;, ;;;:;;
,;:; ;; ;; ;; ;; .;; ;; ,;, ;;;,`;, ;; ;;
;; ;: ;; ;; ;; ;; .;; ;; ,;, ;;;;`;, ;; ;;.
;: ;; ;;;;;: ;; ;; .;; ;; ,;, ;;`;;;, ;; ;;`
,;;;;; ;;`;; ;; ;; .;; ;; ,;, ;; ;;;, ;; ;;
;; ,;, ;; .;; ;;;;;: ;;;;;: ,;;;;;: ;; ;;, ;;;;;;
;; ;; ;; ;;` ;;;;. `;;;: ,;;;;;, ;; ;;, ;;;; The following are debug terminal output and screen shot when running example AdvancedWebServer on PORTENTA_H7_M7 with Portenta_H7 WiFi
Starting AdvancedWebServer on ESP32C3_DEV with ESP WiFi using WiFi Library
WiFiWebServer v1.10.1
Connecting to WPA SSID: HueNet1
HTTP server started @ 192.168.2.86
HHThe following are debug terminal output and screen shot when running example AdvancedWebServer on PORTENTA_H7_M7 with Portenta_H7 WiFi
Starting AdvancedWebServer on ESP32S3_DEV with ESP WiFi using WiFi Library
WiFiWebServer v1.10.1
Connecting to WPA SSID: HueNet1
HTTP server started @ 192.168.2.86
HHThe following are debug terminal output and screen shot when running example AdvancedWebServer_WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
Starting AdvancedWebServer_WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
WiFiMulti_Generic v1.2.2
WiFiWebServer v1.10.1
Connecting WiFi...
WiFi connected, IP address: 192.168.2.113
You're connected to the network, IP = 192.168.2.113
SSID: HueNet1, Signal strength (RSSI):-20 dBm
HTTP server started @ 192.168.2.113
HThe following are debug terminal output and screen shot when running example MQTTClient_Auth_WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
Starting MQTTClient_Auth_WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
WiFiMulti_Generic v1.2.2
WiFiWebServer v1.10.1
Connecting WiFi...
WiFi connected, IP address: 192.168.2.113
You're connected to the network, IP = 192.168.2.113
SSID: HueNet1, Signal strength (RSSI):-18 dBm
Attempting MQTT connection to broker.emqx.io...connected
Published connection message successfully!
Subscribed to: Nano RP2040 ConnectSub
H
MQTT Message Send : Nano RP2040 ConnectPub => Hello from MQTTClient_Auth__WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
Message arrived [Nano RP2040 ConnectPub] Hello from MQTTClient_Auth__WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
HH
MQTT Message Send : Nano RP2040 ConnectPub => Hello from MQTTClient_Auth__WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
H
Message arrived [Nano RP2040 ConnectPub] Hello from MQTTClient_Auth__WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
HH
MQTT Message Send : Nano RP2040 ConnectPub => Hello from MQTTClient_Auth__WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
H
Message arrived [Nano RP2040 ConnectPub] Hello from MQTTClient_Auth__WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic LibraryThe following are debug terminal output and screen shot when running example WiFiUdpNTPClient_WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
Starting WiFiUdpNTPClient_WiFiMulti on Nano RP2040 Connect with WiFiNINA using WiFiNINA_Generic Library
WiFiMulti_Generic v1.2.2
WiFiWebServer v1.10.1
Connecting WiFi...
WiFi connected, IP address: 192.168.2.113
You're connected to the network, IP = 192.168.2.113
SSID: HueNet1, Signal strength (RSSI):-17 dBm
Starting connection to server...
Listening on port 2390
HHH
Packet received
Seconds since Jan 1 1900 = 3869665072
Unix time = 1660676272
The UTC time is 18:57:52
HH
Packet received
Seconds since Jan 1 1900 = 3869665132
Unix time = 1660676332
The UTC time is 18:58:52
HHThe following are debug terminal output and screen shot when running example AdvancedWebServer_WiFiMulti on RASPBERRY_PI_PICO_W with CYW43439 WiFi
Starting AdvancedWebServer_WiFiMulti on RASPBERRY_PI_PICO_W with RP2040W CYW43439 WiFi
WiFiMulti_Generic v1.2.2
WiFiWebServer v1.10.1
Connecting WiFi...
WiFi connected, IP address: 192.168.2.180
You're connected to the network, IP = 192.168.2.180
SSID: HueNet1, Signal strength (RSSI):0 dBm
HTTP server started @ 192.168.2.180
HHDebug is enabled by default on Serial. Debug Level from 0 to 4. To disable, change the WIFI_LOGLEVEL and WIFININA_LOGLEVEL to 0
// Use this to output debug msgs to Serial
#define DEBUG_WIFI_WEBSERVER_PORT Serial
// Debug Level from 0 to 4
#define _WIFI_LOGLEVEL_ 1
#define _WIFININA_LOGLEVEL_ 1If you get compilation errors, more often than not, you may need to install a newer version of the board's core, applying Libraries' Patches, Packages' Patches or this library latest version.
Submit issues to: WiFiWebServer issues
- Bug Searching and Killing
- Add SSL/TLS Client and Server support
- Support more types of boards using WiFiNINA and other WiFi shields.
- Add support to megaAVR boards using MegaCoreX core
- Add support to Arduino SAMD21, Adafruit SAMD21/SAMD51, Seeeduino SAMD21/SAMD51.
- Add support to nRF52.
- Add support to SAM DUE.
- Add support to all STM32F/L/H/G/WB/MP1.
- Add support to WiFiNINA using WiFiNINA_Generic library.
- Add support to ESP_AT_Lib library.
- Add support to
WiFi101 library. - Add support to
WiFiEspAT library. - Add support to PROGMEM-related commands, such as sendContent_P() and send_P()
- Add High-level HTTP (GET, POST, PUT, PATCH, DELETE) and WebSocket Client
- Add support to Arduino Nano RP2040 Connect using Arduino mbed OS for Nano boards.
- Add support to RP2040-based boards, such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, using Earle Philhower's arduino-pico core.
- Add support to RP2040-based boards, such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, using Arduino-mbed mbed_rp2040 core.
- Add support to Portenta_H7 boards, using Arduino-mbed mbed_portenta core.
- Reduce usage of Arduino String with std::string
- Optimize library code and examples by using reference-passing instead of value-passing.
- Add support to new ESP32-S3 and ESP32_C3
- Add support to megaAVR boards (UNO_WIFI_REV2, NANO_EVERY) using Arduino megaAVR core
- Rewrite library and add example multiFileProject to demo for multiple-file project to fix
multiple-definitionslinker error - Add WiFiMulti_Generic library support
- Add many WiFiMulti-related examples in WiFiMulti
- Add support to RASPBERRY_PI_PICO_W using CYW4343 WiFi with Earle Philhower's arduino-pico core v2.4.0+
- Better workaround for RP2040W
WiFi.status()bug usingping()to local gateway - Add new features, such as
CORS - Use
allman astyleand addutils - Using new
WiFi101_Generic libraryfor sending larger data
- Based on and modified from Ivan Grokhotkov's ESP8266WebServer
- Thanks to good work of Miguel Alexandre Wisintainer for initiating, inspriring, working with, developing, debugging and testing. Without that, support to nRF52, especially U-Blox B302 running as nRF52840 and U-Blox B112 running as nRF52832, has never been started and finished. See u-blox nina b
- Adrian McEwen for HttpClient Library on which the ArduinoHttpClient Library and this EthernetWebServer library are relied.
- RQnet to report issue Decoding Error. two times called urlDecode in Parsing-impl.h. #17 leading to version v1.6.3 to fix the decoding error bug when using special
&in data fields.
 ⭐️⭐️ Ivan Grokhotkov |
 ⭐️ Adrian McEwen |
 ⭐️ Miguel Wisintainer |
 RQnet |
If you want to contribute to this project:
- Report bugs and errors
- Ask for enhancements
- Create issues and pull requests
- Tell other people about this library
- The library is licensed under MIT
Copyright (c) 2020- Khoi Hoang
