Supported Hardware
Last updated
Last updated
There are different ways to get your devices connected to the Blynk Cloud:
Blynk library An easy to use and portable C++ library, pre-configured to work with hundreds of development boards. The library implements a streaming connection protocol (i.e. the device stays always connected to the cloud), that allows for a low latency, bi-directional communication. For an easy start use Quickstart flow and make sure to explore Blynk Library documentation afterwards.
Blynk.Edgent Blynk.Edgent is a packaged solution that allows developers to easily connect their devices to the platform and take advantage of all its advanced features without the need for extensive coding. It includes:
Blynk library API
Blynk.Inject (dynamic device credentials provisioning)
Blynk.Air (firmware OTA updates)
A simple UX/interaction example:
Device state indication using an RGB LED
Device configuration reset using a button
If your hardware supports Blynk.Edgent, we recommend using this flow at all times.
Blynk.NCP
Blynk offers a software stack for a variety of Network Co-Processors. NCP is a dedicated connectivity chip/module that off-loads the Blynk.Cloud connectivity (WiFi, Ethernet, Cellular) from the main device MCU. The main MCU runs a lightweight client library that communicates to the NCP over UART or SPI. It enables blazing fast and high quality integration, and is perfect for retrofitting scenarios. If you're interested in using Blynk.NCP for commercial applications, please contact Blynk.
HTTP(s) API A standard communication protocol that can be used by any Internet-connected device. The device connects to the cloud occasionally to transfer the data. Sending timestamped data in batches is also possible, which is particularly useful for Cellular devices. You can find more guidance in HTTP(s) API documentation.
Blynk.EdgentAs part of Blynk.Edgent the following features are fully supported: Dynamic Tokens (WiFi provisioning). Read more about WiFi provisioning here:
Blynk.Air (OTA). Read about it here:
ESP32
✅
✅
✅
ESP8266
✅
✅
✅
Seeed Wio Terminal
✅
✅
✅
TI CC3220
✅
✅
✅
Blynk.NCP⏳ RA4M1
✅ ESP32s3
WiFi 2.4
✅ BLE
4.25 MB
⏳ RA6M5
✅ ESP32c3
WiFi 2.4
✅ BLE
512 KB
✅ RP2040
❌ NINA_W102
WiFi 2.4
✅ BLE
384 KB
✅ SAMD21
❌ NINA_W102
WiFi 2.4
✅ BLE
384 KB
✅ SAMD21
❌ NINA_W102
WiFi 2.4
✅ BLE
384 KB
✅ RP2040
✅ ESP32c3
WiFi 2.4
✅ BLE
512 KB
✅ RP2040
✅ ESP8266
WiFi 2.4
✅ WiFiAP
1000 KB
Blynk.NCPESP32
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
This is the easiest way to migrate from legacy Blynk projects. Just add BLYNK_TEMPLATE_ID and BLYNK_TEMPLATE_NAME at the top of your firmware (prior to any includes), update your auth token and that's it. Read more about project migration.
Read about static tokens here:
If your board is not listed below, you may still be able to use it with Blynk library. Check out the generic Arduino Client examples.
Arduino (https://github.com/blynkkk/blynk-library)
Arduino MKR WiFi 1010
Arduino MKR GSM 1400
Arduino MKR NB 1500
Arduino Uno, Duemilanove
Arduino Nano, Mini, Pro Mini, Pro Micro, Due, Mega
Arduino MKR1000
Arduino Zero
Arduino Yún (onboard WiFi and Ethernet, via Bridge)
Arduino.org UNO WiFi
Arduino MKR VIDOR 4000 (use the example for MKR WiFi 1010)
Arduino UNO WiFi Rev.2 (use the example for MKR WiFi 1010)
Arduino-like
Blynk Board
ESP8266 (Generic, NodeMCU, Witty Cloud, Huzzah, WeMos D1, Seeed Wio Link, etc.)
ESP32
Teensy
Blue Pill (STM32F103C)
Realtek RTL8710 / Ameba via RTLduino
Feather M0 WiFi
TinyCircuits TinyDuino (CC3000)
Microduino/mCookie Core, Core+, CoreUSB
Wicked WildFire V2, V3, V4
chipKIT Uno32
Alorium XLR8 (FPGA)
LinkIt ONE
Particle https://github.com/vshymanskyy/blynk-library-spark)
Core
Photon
Electron
Argon
Photon 2
JavaScript (Node.js, Espruino, Browsers) (https://www.npmjs.com/package/blynk-library)
Regular PC with Linux / Windows / OS X
Raspberry Pi (Banana Pi, Orange Pi, …)
BeagleBone Black
Onion Omega 2
VoCore, VoCore2 (OpenWRT + Espruino package)
Espruino Pico
…
Python (https://github.com/vshymanskyy/blynk-library-python)
Regular PC with Linux / Windows / OS X
Raspberry Pi (Banana Pi, Orange Pi, …)
BeagleBone Black
Onion Omega 2
MicroPython
…
USB (Serial), connected to your laptop or desktop
Ethernet
Arduino MKR ETH
Arduino Ethernet Shield (W5100)
Arduino Ethernet Shield 2 (W5500)
ENC28J60-based modules
WiFi
ESP8266 as WiFi modem (running original AT firmware)
Arduino WiFi 101 Shield
Arduino WiFi Shield
WIZnet WizFi310
Cellular (GSM/3G/LTE)
SIMCom SIM800 series (SIM800A, SIM800C, SIM800L, SIM800H, SIM808, SIM868)
SIMCom SIM7600 series
BG96
GPRSbee
Adafruit FONA (Mini Cellular GSM Breakout)
Traffic optimization is usually required for cellular connections. Using realtime streaming protocols like Blynk or MQTT has benefits of interactive device updates, but it also requires device to stay "always connected", which significantly increases the traffic. Blynk recommends using HTTPS (batch) API for reporting telemetry and fetching DataStream values periodically in such scenarios. It will also help saving the battery.
Node-RED (can be used as bridge to HTTP, TCP, UDP, MQTT, XMPP, IRC, OSC…)
Here is a list of known library issues.
If you are looking for commercial use of Blynk with hardware from Nordic Semiconductor, Silicon Labs, NXP Semiconductors or other manufacturers, let's talk about integration options.
+
(no PSRAM)