Supported Hardware
List of hardware and development boards that work with Blynk.
There are five 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.
Try Quickstart flow and make sure to explore Blynk Library documentation afterwards.
Blynk.Edgent
Blynk.Edgent is a packaged solution that allows you to easily connect devices to Blynk and take advantage of all its advanced features, including:
Blynk.Library API
Blynk.Inject (dynamic device credentials provisioning)
Blynk.Air (firmware OTA updates)
If your hardware supports Blynk.Edgent, we recommend using this flow at all times.
Blynk.NCP
Blynk provides a versatile software stack for Network Co-Processors (NCPs), which are dedicated connectivity chips or modules.
NCP handles Blynk.Cloud connectivity (WiFi, Ethernet, Cellular), offloading this task from the main device's MCU. The main MCU operates with a lightweight client library, communicating with the NCP via UART or SPI. This setup offers rapid and high-quality integration, making it ideal for retrofitting scenarios.
To get started, check our firmware examples to connect a dual-MCU board or design your own device by incorporating an NCP module.
HTTP(s) API
This is a standard communication protocol suitable for any internet-connected device.
It allows the device to connect to the cloud periodically to transfer data. Additionally, it supports sending timestamped data in batches, a feature especially beneficial for cellular devices.
You can find more guidance in HTTP(s) API documentation.
MQTT API
A secure, industry standard two-way communication protocol.
Supports authentication, updating data streams, widget properties, events, metadata, timezone/location information, OTA firmware updates and more.
Ideal for projects utilizing MQTT libraries, Node-RED and similar, or SDKs with MQTT support.
Works for integrating off-the-shelf MQTT-enabled gateways and other hardware directly into the Blynk environment.
Hardware supported by Blynk.Edgent
Blynk.EdgentAs part of Blynk.Edgent the following features are fully supported: Dynamic Tokens (WiFi provisioning). Read more about WiFi provisioning here:
WiFi provisioningBlynk.Air (OTA). Read about it here:
OTA: Firmware Over-The-Air updatesESP32
✅
✅
✅
ESP8266
✅
✅
✅
Seeed Wio Terminal
✅
✅
✅
TI CC3220
✅
✅
✅
Dual-MCU Boards supported by Blynk.NCP
Blynk.NCPConnectivity Modules supported by Blynk.NCP
Blynk.NCPHardware that works with Blynk library or HTTPs API (using Static Tokens)
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:
Static TokenIf 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
…
Arduino connection types
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.
Made by Community
Node-RED (can be used as bridge to HTTP, TCP, UDP, MQTT, XMPP, IRC, OSC…)
Troubleshooting
Here is a list of known library issues.
Need support for any other hardware?
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.
Last updated