Supported Connectivity Modules
To enable a seamless connection and advanced Blynk’s functionality using the hardware of your choice, you need to add one of the supported connectivity modules below as a Network Co-Processor. We’ve prepared an example that includes firmware and will help you set up the communication between your hardware and Blynk with minimal effort.
Blynk.NCP is shipped as a combined firmware, so you only need to flash a single file (flash at address
0). Select the firmware file, corresponding to your module type.Connectivity module | Firmware file | Chipset | Connectivity | Provisioning | Interaction |
|---|---|---|---|---|---|
ESP32 | WiFi 2.4 | BLE | | ||
ESP32-C3 | WiFi 2.4 | BLE | | ||
ESP32-S3 | WiFi 2.4 | BLE | | ||
ESP32 | WiFi 2.4 | BLE | | ||
ESP32 | WiFi 2.4 | BLE | | ||
ESP32-S3 | WiFi 2.4 | BLE | | ||
ESP32 | WiFi 2.4 | BLE | RGB LED | ||
ESP32 | WiFi 2.4 | BLE | Green LED | ||
ESP32+LAN8720 | WiFi 2.4, Ethernet POE | BLE | | ||
ESP32+LAN8720 | WiFi 2.4, Ethernet | BLE | | ||
ESP8266 | WiFi 2.4 | WiFiAP | RGB LED, User Button | ||
ESP8266 | WiFi 2.4 | WiFiAP | User Button | ||
ESP-07S, ESP-12F | ESP8266 | WiFi 2.4 | WiFiAP | | |
ESP-01, ESP-01S | ESP8266 | WiFi 2.4 | WiFiAP | |
If you are using one of the following dual-MCU boards: UNO R4 WiFi, Portenta C33, Nano RP2040 Connect, Nano 33 IoT, MKR WiFi 1010, T-PicoC3, or RPi Pico + ESP8266, you can use this Blynk.NCP example to set up communication with the platform within minutes.