Comment on page
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)
- 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
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.
As 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: