For all the IoT makers and newbies, we very well know and understand the Blynk IoT Platform and how to use the Blynk 1.0 (Legacy version). But as Blynk has upgraded to Blynk 2.0 there were many changes made in the new documentation which are not yet noted or maybe missed out.

This article points to understanding and implementing not only the Dashboard usage of both Blynk 1.0 and 2.0 but also all the API endpoints that make its usage of it functional.

You get 10 good-quality PCBs manufactured and shipped to your doorstep for cheap. You will also get a discount on shipping on your first order. Upload your Gerber files onto PCBWAY to get them manufactured with good quality and quick turnaround time. PCBWay now could provide a complete product solution, from design to enclosure production. Check out their online Gerber viewer function. With reward points, you can get free stuff from their gift shop.

Before getting started, let us understand what is Blynk (For beginners)

Blynk is a full suite of software required to prototype, deploy, and remotely manage connected electronic devices at any scale: from personal IoT projects to millions of commercial connected products.

The above text is an official statement/description of what Blynk really is, and what it serves as a solution for the General Public as a tool.

Think about a Plug-and-Play IoT Platform for the IoT Developers, to build and develop IoT applications on-the-go. Blynk is exactly the same, with easy-to-make buttons, visualization charts, and many more from it.

The ability to use drag-and-drop widgets has made the IoT Platform grow even more. In only a matter of seconds, we can control our Wireless Board from the Web Dashboard, as well as Mobile App.

Back in 2016, when Blynk introduced multiple features like the ability to use the Library file and directly connect any WiFi-enabled board to the Blynk Cloud. Since then the Cloud was LIVE and had a pretty decent latency. Which caught the attention of many IoT developers or learners. It was this period of time when people started building many projects on this platform and the world of IoT became a thing for people.

Since then Blynk started documenting all the procedures, and steps required to use their platform. But recently with the upcoming Blynk 2.0 the documentation will soon be removed which is currently hosted on http://docs.blynk.cc. Even though not ACTIVE, the Blynk cloud for those API requests is still LIVE.

API Request - Send/Receive information to/from the Blynk Cloud, to/from the Device with Blynk Code.

To get started, it is required to first Download the Blynk App (LEGACY) (No more available on App store as per the information here)

After downloading, it is necessary to have a Facebook Account to be able to Sign In/ Login to the Blynk App.

From this App, with each new project, we are provided with an Auth Token which we can use to access the Blynk Cloud and its services. Either we can use the App to control/monitor our Wireless devices, or use the Auth Token to access the LIVE data using API requests.

1. Using Blynk App

Open App > New Project > Enter 'Project name' and Choose Device > click Create

Most likely, the Auth Token is sent to the Email ID associated automatically during the creation of a 'new project'. Check Mail if prompted, else Click on the Settings (gear icon on the top bar) and scroll down to Copy the Auth Token.

Now that we have the Auth Token, let us know about the Widgets available on this App. Tap and hold the Widget to drag it to the new position.

Each Widget has it’s own settings. Tap on the widget to get to them to view the settings

INPUT/OUTPUT - Select Digital pin only if you'll be using the specific pin at all times. Any changes in the code will require to be adjusted in the app as well. For ease of purpose, we use Virtual pin, since it gives the flexibility to choose the hardware pin from the code itself.

Rest of the settings depend on the widget we choose. For this project, we shall use 1 Button and 1 Value Display widget to showcase control and monitor
Let us add both the widgets to the Panel.

Provide below configurations accordingly,
Button -> OUTPUT - V0 (0-1), Mode - SWITCH
Slider -> OUTPUT - V1 (0-1023), Decimals-AUTO, SOR&SV-ON
Value Display -> Value - V2 (0-1023), Reading rate - PUSH

Great! Now RUN the Project

• In the code, WiFi.h, WiFiClient.h, Wire.h, SparkFunBME280.h and BlynkSimpleEsp32.h (download here) libraries have been used.
• Replace <wifi_name>, <password>, and auth_token under ssid, password, and auth with your WiFi and Blynk credentials. (Hint - Check the settings of the Project in App for Auth)

In the Arduino IDE, navigate to Sketch > Include Library > Add .ZIP Library. At the top of the drop down list, select the option to "Add .ZIP Library''. Then browse to the downloaded ZIP file of BlynkSimpleEsp32

I will be using BME280 sensor to send temperature data to the Blynk Cloud, I will share a commented code which can be used to share a dummy data as well.

#define BLYNK_PRINT Serial

long randNumber; float flrandNumber;

#include <WiFi.h>
#include <WiFiClient.h>
#include <BlynkSimpleEsp32.h>
#include <Wire.h>
#include "SparkFunBME280.h"
int freq = 2000;
int channel = 0;
int resolution = 8;
BlynkTimer timer;
BME280 bme;

String temperature;

char auth[] = "<auth_token>";       /* You should get Auth Token in the Blynk App. */
char ssid[] = "<wifi_name>";                    /* Your Wi-Fi Credentials */
char pass[] = "<password>";

void setup() {    pinMode(2, OUTPUT);    ledcSetup(channel, freq, resolution);    ledcAttachPin(4, channel);    Serial.begin(9600);    Serial.println("WiFi connected");    Blynk.begin(auth, ssid, pass);    Wire.begin();    if (bme.beginI2C() == false) /* Begin communication over I2C */    {        Serial.println("The sensor did not respond. Please check wiring.");        while(1); /* Freeze */    }    timer.setInterval(1000L, myTimerEvent);
}
BLYNK_WRITE(V0)
{  /* This function gets called each time something changes on the widget */    int value = param.asInt();  /* This gets the 'value' of the Widget as an integer */    digitalWrite(2,value);    Serial.print("Pin 2 - ");    Serial.println(value);
}
BLYNK_WRITE(V1)
{  /* This function gets called each time something changes on the widget */    int value2 = param.asInt();  /* This gets the 'value' of the Widget as an integer */    /*map(value2, 0, 255, 0, 255) */    ledcWrite(channel, value2);    Serial.print("Pin 4 - ");    Serial.println(value2);
}
void myTimerEvent()
{    Blynk.virtualWrite(V2, bme.readFloatHumidity());
    /*randNumber = random(600, 800);    flrandNumber = (float)randNumber / 100.00;    Blynk.virtualWrite(V2, flrandNumber); */

}
void loop(){    Blynk.run();    timer.run();
}

Now, let us use API to monitor and control the virtual pins.

Even though the API documentation of Blynk 1.0 is no longer managed, the servers are still functional so far. The server will be alive till December, 2022 as per the information here

HTTP Endpoint (Bangalore Server) - https://blr1.blynk.cloud/external/api
Parameters - token and pins

Sample UPDATE and GET requests

1. Control the Virtual Pins (Send data to Dev board)

https://blynk.cloud/external/api/update?token=&v1=100

2. View the Data on Dev board with Virtual Pin

https://blynk.cloud/external/api/get?token=&v0

In May 2021, Blynk released the latest generation of the Blynk IoT Platform called “Blynk IoT”. This guide is intended to assist someone currently using the legacy version of Blynk (“Blynk Legacy”) to migrate to the latest Blynk system.

Features of Blynk -

• Blynk.App: a unique, no-code mobile app builder for IoT
• Blynk.360: a web console to manage devices, users and data
• Templates: new device creation process designed for scale
• Blynk.Inject: a WI-FI manager built into the Blynk mobile app
• Blynk.Air: over-the-air firmware updates
• All kinds of Automations (think Eventor on steroids)
• Voice assistants and much much more

To get started, it is required to signup and log in to the Blynk Cloud.

Next, click on Templates from the left side panel, and create a New Template with below configurations.

After clicking on the created template, we should our Template ID and Device Name as our Firmware configurations. Make sure to note where to find them 😉

Next, we need to Add DataStreams which would work like a bucket where we can store data to the cloud for streaming across from the Device to/from the cloud.

Click on the Edit button on top-right section, click on Datastreams and create New DataStream > Virtual Pin. Then use below configurations -

Make changes accordingly, like using a double data type for decimal value, or selecting another virtual pin.

Similarly, create another datastream with MIN 0 and MAX 1.

Next on the Automations tab, Select the type of automation as sensor for min-max 0-155 and switch for 0-1.

Now, let us add widgets on the Web Dashboard to monitor and control the Datastreams.

Double click on Switch and Label Display from the Widget Box to add them to the Dashboard panel. Next, click on the gear button of each and select the appropriate Datastream you are using.

That's it on the Templates section! Click on Save and Apply and head to the Devices. Click on the Search icon on left-side panel to open the Device Dashboard seciton. Here, first Add New Device > from Templates > Choose the Template we just created.

We should see our Dashboard now -

Notice that all the device configuations are now ready to be copied for the Hardware device code.

In your Arduino IDE, go to Sketch > Include Library > Manage Libraries and search for 'Blynk'. Top-most result should be the library we require. To confirm, check if the latest version matches with one on Github.

Now, use the below code to get started and use the Blynk Cloud.

#define BLYNK_TEMPLATE_ID " "
#define BLYNK_DEVICE_NAME " "
#define BLYNK_AUTH_TOKEN " "
char ssid[] = " ";                    /* Your Wi-Fi Credentials */
char pass[] = " ";

#define BLYNK_FIRMWARE_VERSION        "1.1.0"
#define BLYNK_PRINT Serial

#define APP_DEBUG

#include <Wire.h>
#include "SparkFunBME280.h"
#include "BlynkSimpleEsp32.h"

int freq = 2000;
int channel = 0;
int resolution = 8;

long randNumber; float flrandNumber;
BlynkTimer timer;
BME280 bme;

#define BLYNK_PRINT Serial
//#define BLYNK_DEBUG
#define APP_DEBUG
#define USE_WROVER_BOARD

String temperature;

void myTimerEvent()
{  Blynk.virtualWrite(V0, bme.readFloatHumidity());
    /*randNumber = random(600, 800);    flrandNumber = (float)randNumber / 10.0;    Blynk.virtualWrite(V0, flrandNumber); */
}

BLYNK_WRITE(V1)
{  int pinValue = param.asInt(); /* assigning incoming value from pin V1 to a variable*/  digitalWrite(2,pinValue);    /*Serial.print("Pin 2 - ");  Serial.println(pinValue);*/
}


void setup()
{  Serial.begin(115200);  delay(100);
  pinMode(2, OUTPUT);    ledcSetup(channel, freq, resolution);    ledcAttachPin(4, channel);

   Blynk.begin(BLYNK_AUTH_TOKEN, ssid, pass);      Wire.begin();    if (bme.beginI2C() == false) /* Begin communication over I2C */    {        Serial.println("The sensor did not respond. Please check wiring.");        while(1); /* Freeze */    }  timer.setInterval(1000L, myTimerEvent);
}

void loop() {  Blynk.run();  timer.run();
}

After everything, Compile and Upload the code to the ESP32. Now, open the Serial monitor to check if there is any error. If not, the monitor shall look like this once connected to the Blynk Cloud with the Device created.

Below DashBoard is an Example of how it looks.

Now, let us use API to monitor and control the virtual pins.

The REST APIs of Blynk 2.0 is exactly the same to use as it was with the Legacy version. The Latest API documentation is available on HTTPs REST API for Blynk.Cloud. And below is only an example on how to implement it.

HTTP Endpoint - https://blynk.cloud/external/api
Parameters - token, pin, value, etc.

Sample UPDATE and GET requests

1. Control the Virtual Pins (Send data to Dev board)

https://blynk.cloud/external/api/update?token=&v1=100

2. View the Data on Dev board with Virtual Pin

https://blynk.cloud/external/api/get?token=&v0

With Blynk 2.0, which includes many features as listed. Another feature is also present, which allows for reduction in uploading code when change in network is observed frequently. Uploading a new code to the Board without having to reconnect to a PC, using the Edgent OTA feature.

It comes with the OTA feature, allowing us to update the code from the cloud itself. Let us see how to use this feature -

We can directly get started with the Example provided by them. In the Arduino IDE, navigate to Files > Examples > Blynk > Blynk.Edgent > Edgent_ESP32 - It will open default code.

Here, only make the changes in the Edgent_ESP32.h file, like adding Virtual Pins to be controlled or monitored, widget properties, timers, etc. Below is an example -

#define BLYNK_TEMPLATE_ID " "
#define BLYNK_DEVICE_NAME " "
#define BLYNK_AUTH_TOKEN " "

#define BLYNK_FIRMWARE_VERSION        "0.1.1"
#define BLYNK_PRINT Serial

#define APP_DEBUG

#include <Wire.h>
#include "SparkFunBME280.h" 
#include "BlynkEdgent.h"

int freq = 2000;
int channel = 0;
int resolution = 8;

long randNumber; float flrandNumber;
BME280 bme;

#define BLYNK_PRINT Serial
/* #define BLYNK_DEBUG */
#define APP_DEBUG
#define USE_WROVER_BOARD

String temperature;

void myTimerEvent()
{  Blynk.virtualWrite(V0, bme.readFloatHumidity());
    /* randNumber = random(600, 800);    flrandNumber = (float)randNumber / 100.00;    Blynk.virtualWrite(V2, flrandNumber); */
}

BLYNK_WRITE(V1)
{  int pinValue = param.asInt(); // assigning incoming value from pin V1 to a variable  digitalWrite(2,pinValue);
}

void setup()
{  Serial.begin(115200);  delay(100);
  pinMode(2, OUTPUT);   BlynkEdgent.begin();  Wire.begin();    if (bme.beginI2C() == false) /* Begin communication over I2C */    {        Serial.println("The sensor did not respond. Please check wiring.");        while(1); /* Freeze */    }  timer.setInterval(1000L, myTimerEvent);
}

void loop() {  BlynkEdgent.run();
}

Compile and Upload the code to ESP32 Dev Board and open the serial monitor.

Make sure the template, virtual pins, and datastream are linked for the template. Post that, we're good to go.

We shall now connect our Mobile to the Dev Board'swifi Hotspot.