Ugenz Academy/IoT Tutorial

Firebase Blynk And Thingspeak

9 min read1,788 words

Reading progress

Keep learning

Firebase, Blynk and ThingSpeak with ESP32

Now we move from MQTT concepts to actual IoT cloud platforms.

These platforms make it easier to connect your ESP32 to the Internet, store sensor data, create dashboards, and control devices remotely.

INTERNET │ ESP32 │ ┌────────────┼────────────┐ ▼ ▼ ▼ Firebase Blynk ThingSpeak │ │ │ Database Dashboard Charts/Data │ │ │ ▼ ▼ ▼ Web/App Mobile App Analytics

1. Why Do We Need IoT Cloud Platforms?

Suppose your ESP32 measures:

Temperature = 29°C Humidity = 65%

If you only use Serial Monitor:

ESP32 → USB → Computer

you can see the data only locally.

With cloud IoT:

ESP32 │ │ Internet ▼ Cloud │ ├── Phone ├── Laptop └── Web Dashboard

You can potentially monitor the device remotely.

For example:

ESP32 is installed in your farm in Nepal, and you check the temperature from your phone while you're somewhere else.


2. Firebase

Firebase is a Google platform providing backend services for applications.

For ESP32 projects, the most relevant Firebase services include:

  • Realtime Database
  • Cloud Firestore
  • Authentication
  • Cloud Functions
  • Hosting
  • Storage

For beginner IoT projects, Realtime Database is particularly useful.


3. Firebase Realtime Database

Think of it as an online JSON-like database.

Example:

home ├── temperature: 29.5 ├── humidity: 62 ├── light: "ON" ├── fan: "OFF" └── door: "CLOSED"

Your ESP32 can write data:

ESP32 │ │ temperature = 29.5 ▼ Firebase

Your website can read it:

Firebase │ ▼ Next.js Dashboard │ ▼ Temperature: 29.5°C

4. Firebase for Smart Home

For your smart-home project, you could structure the database like:

smartHome │ ├── sensors │ ├── temperature │ ├── humidity │ ├── motion │ └── lightLevel │ ├── devices │ ├── light │ ├── fan │ └── door │ └── security └── armed

Then:

ESP32 → Firebase → Web Dashboard

and:

Web Dashboard → Firebase → ESP32

This gives you two-way control.


5. Example

Suppose the web dashboard changes:

devices/light = "ON"

ESP32 reads the value:

Firebase │ │ ON ▼ ESP32 │ ▼ Relay │ ▼ Light ON

Similarly, ESP32 can update:

sensors/temperature = 30.2

and your website displays:

🌡 Temperature 30.2°C

6. Firebase + React/Next.js

This is especially useful with your web-development stack.

You can have:

Firebase / \ / \ ESP32 Next.js │ │ ▼ ▼ Sensors Dashboard

Your Next.js dashboard could show:

┌─────────────────────────────┐ │ SMART HOME │ ├─────────────────────────────┤ │ Temperature 29.4 °C │ │ Humidity 61 % │ │ Motion Detected │ │ │ │ Light 🟢 ON │ │ Fan ⚪ OFF │ │ Door 🔒 Locked │ └─────────────────────────────┘

7. Firebase Authentication

If you're creating a real dashboard, don't simply allow anyone to control your ESP32.

You can use authentication:

User │ ▼ Login │ ▼ Firebase Authentication │ ▼ Dashboard │ ▼ IoT Device

Possible authentication methods include:

  • Email/password
  • Google sign-in
  • Other supported providers

This is important for smart-home security.


8. Firebase Security Rules

Another important concept is security rules.

You don't want:

Anyone on Internet │ ▼ Firebase │ ▼ Your Door

Instead:

Authenticated User │ ▼ Firebase Rules │ ▼ Allowed Data

For example, a user may be allowed to read:

home/temperature

but only authorized users should control:

home/door

9. Blynk

Blynk is designed specifically for IoT devices and provides dashboards and device controls.

It can significantly reduce the amount of frontend code you need to write.

Architecture:

ESP32 │ │ Internet ▼ Blynk Cloud │ ▼ Blynk App / Dashboard

10. Why Blynk is Popular for ESP32

Suppose you want:

Temperature Humidity Light button Fan button Door button

With a custom system, you'd normally build:

ESP32 + Backend + Database + Authentication + Frontend + Mobile UI

Blynk provides many IoT-specific components so you can build a dashboard much faster.


11. Blynk Dashboard

A dashboard could look conceptually like:

┌─────────────────────────────┐ │ MY SMART HOME │ ├─────────────────────────────┤ │ 🌡 Temperature 29.5°C │ │ 💧 Humidity 62% │ │ │ │ 💡 LIGHT [ ON ] │ │ 🌀 FAN [ OFF ] │ │ 🚪 DOOR [ OPEN ] │ │ │ │ 🔐 SECURITY [ ARM ] │ └─────────────────────────────┘

This matches your ESP32 smart-home project very well.


12. Blynk Virtual Pins

Blynk commonly uses virtual datastreams/pins to exchange values between your ESP32 and dashboard.

Conceptually:

V0 → Temperature V1 → Humidity V2 → Light V3 → Fan V4 → Door

For example:

V0 = 29.5

could represent temperature.

A button could send:

V2 = 1

meaning:

Light ON

13. Blynk Two-Way Control

The communication becomes:

Blynk Cloud / \ / \ ESP32 Phone │ │ │ │ Sensor Button │ │ └───────┬───────┘ │ Internet

Phone:

LIGHT → ON

Blynk sends the command to ESP32.

ESP32:

Relay → ON

14. ThingSpeak

ThingSpeak is particularly useful for collecting, visualizing, and analyzing sensor data.

Think:

ESP32 │ │ Sensor data ▼ ThingSpeak │ ├── Charts ├── History └── Analysis

It's excellent when your main goal is:

"I want to record my sensor data and see graphs."


15. ThingSpeak Example

Suppose your ESP32 measures:

Temperature Humidity Soil Moisture

You could send:

Field 1 → Temperature Field 2 → Humidity Field 3 → Soil Moisture

ThingSpeak can then visualize the values over time.

Example:

Temperature 32°C ┤ ╭─╮ 30°C ┤ ╭──╯ ╰──╮ 28°C ┤───────╯ ╰── └──────────────────── 10 12 14 16 18 Time

16. ThingSpeak for Agriculture

This is especially useful for an IoT farming project.

FARM │ ┌────┴─────┐ │ │ DHT22 Soil Sensor │ │ └────┬─────┘ ▼ ESP32 │ Internet │ ▼ ThingSpeak │ ┌────┼────┐ ▼ ▼ ▼ Temp Humidity Soil

You can analyze changes over hours, days, or longer periods.


17. Firebase vs Blynk vs ThingSpeak

FeatureFirebaseBlynkThingSpeak
IoT dashboard⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Database⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Mobile control⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Custom website⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Data charts⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Authentication⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Quick ESP32 project⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Custom backend⭐⭐⭐⭐⭐⭐⭐⭐⭐
Sensor analytics⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐

18. Which One Should You Choose?

Choose Firebase if:

You want to build:

ESP32 + Custom Website + Login + Database + Dashboard

For example:

Next.js + Firebase + ESP32

is a powerful combination.


Choose Blynk if:

You want:

ESP32 ↓ Ready-made IoT dashboard ↓ Phone

and don't want to spend a lot of time building the frontend.


Choose ThingSpeak if:

Your main goal is:

Sensors ↓ Data Collection ↓ Charts ↓ Analysis

19. Firebase vs MQTT

These are not necessarily competitors.

You can use both.

ESP32 │ │ MQTT ▼ MQTT Broker │ ▼ Backend │ ▼ Firebase │ ▼ Web Dashboard

For a larger architecture:

Sensors ↓ ESP32 ↓ MQTT ↓ Broker ↓ Backend ↓ Firebase ↓ Next.js

MQTT handles device messaging.

Firebase handles application data/backend services.


20. Blynk vs MQTT

Blynk can provide a higher-level IoT experience.

Instead of designing your own:

MQTT Broker Backend Database Dashboard Mobile App

you can use Blynk's platform and focus more on the ESP32/device side.


21. ThingSpeak + MQTT

ThingSpeak can also fit into MQTT-based architectures.

Conceptually:

ESP32 │ │ MQTT ▼ Cloud Service │ ▼ ThingSpeak │ ▼ Charts

The exact integration depends on the service configuration.


22. Your Smart Home Architecture

For your IoT wall project, a practical architecture could be:

INTERNET │ ▼ ┌────────────┐ │ Cloud │ └─────┬──────┘ │ ┌─────────┼─────────┐ ▼ ▼ ▼ Firebase Blynk ThingSpeak │ ▼ Web Dashboard │ ▼ ESP32 │ ┌────────┼─────────┐ │ │ │ DHT22 PIR LDR │ │ │ └────────┼─────────┘ │ ┌────────┼─────────┐ ▼ ▼ ▼ Relay Servo Display │ │ Light Door

23. Example Smart Home Data

Your Firebase database could contain:

{ "sensors": { "temperature": 29.5, "humidity": 62, "motion": true, "lightLevel": 740 }, "devices": { "light": true, "fan": false, "door": false }, "security": { "armed": true } }

Now your web application can read this data and display it.


24. IoT Data Flow

Let's follow one sensor value.

Step 1

DHT22 measures:

29.5°C

Step 2

ESP32 reads it:

ESP32 = 29.5

Step 3

ESP32 sends it to cloud:

ESP32 → Firebase

Step 4

Firebase stores:

temperature: 29.5

Step 5

Dashboard reads:

29.5°C

Complete:

DHT22 ↓ ESP32 ↓ Internet ↓ Firebase ↓ Next.js ↓ Browser

25. IoT Command Flow

Now reverse the direction.

User clicks:

FAN → ON

Then:

Browser ↓ Firebase ↓ ESP32 ↓ Relay ↓ Fan

This is the basic principle behind remote IoT control.


26. Important Security Rules

Never put sensitive credentials directly into a public GitHub repository.

Avoid:

const char* password = "MY_REAL_PASSWORD";

in code that you upload publicly.

Also protect:

  • Firebase database
  • API keys where applicable
  • MQTT credentials
  • Device tokens
  • Cloud credentials
  • OTA credentials

And don't make a smart-home door/relay endpoint publicly accessible without authentication and authorization.


27. Which Platform for Which Project?

Project Best starting choice Smart Home Dashboard Firebase / Blynk Mobile IoT Control Blynk Custom React/Next.js IoT Firebase Temperature Monitoring ThingSpeak Agriculture Data Analysis ThingSpeak Large IoT Messaging System MQTT ESP32 + Custom Backend MQTT + Firebase Quick College Project Blynk

🧠 Quick Summary

Remember these three ideas:

Firebase

Database + Backend + Authentication + Custom App

Blynk

IoT Device + Ready Dashboard + Mobile Control

ThingSpeak

Sensor Data + Charts + Analytics

And they can all work with ESP32:

ESP32 │ ┌───────────┼───────────┐ ▼ ▼ ▼ Firebase Blynk ThingSpeak │ │ │ Web/App IoT UI Charts

Keep learning. Keep building. Keep growing.

© 2026 Ugenz Academy