IoT Air Quality Monitoring FYP for Classrooms in Malaysia

Quick Summary

The system monitors temperature, humidity and air quality indicators, displays status, and logs trend data for a classroom or small lab. For a Malaysia final year project, the strongest version is not only a working circuit. It should also show a clear problem, a clean data flow, useful alerts, repeatable testing and honest limitations.

This supports searches like classroom air quality IoT FYP, ESP32 air quality project Malaysia and MQ135 final year project. The goal is to help students choose a topic that can be built, explained and defended during viva without overclaiming.

Why This Topic Works for Malaysia FYP

Classrooms and labs make the project relatable because students can explain comfort, ventilation and air quality trends. It also gives the student enough engineering content: sensor selection, ESP32 wiring, power planning, threshold logic, dashboard design and result validation.

A good proposal can use this structure:

Problem: what user or environment issue is being monitored.
Input: what the sensor reads and how often it updates.
Processing: how the ESP32 filters data and decides the status.
Output: buzzer, relay, display, dashboard, Telegram or WhatsApp-style alert.
Evidence: screenshots, log tables and repeated test cases.

Recommended System Flow

Use this flow for the report and presentation:

Sensor reads the physical condition.
ESP32 checks the reading against calibrated thresholds.
Local display shows the latest value and status.
Dashboard stores readings with timestamp.
Alert is sent only when the status is warning or danger.
The system returns to normal when the reading is stable again.

This makes the project easier to explain than a simple sensor demo because every block has a purpose.

Core Components

ESP32 DevKit
BME280 or DHT22
SCD41 or SCD30 for CO2 claims
MQ135 only for relative gas trend experiments
OLED display
Dashboard

Check component details in the Rectronx Components Database. If your project uses ESP32, plan safe pins using the ESP32 Pinout Tool before wiring sensors, relays and displays.

Suggested Features

Live sensor reading with clear unit or status.
Normal, warning and danger states.
Dashboard table with timestamp.
Simple graph for trend analysis.
Local output such as buzzer, LED or display.
Manual reset or override where suitable.
Short error message when sensor data is missing.

For more title ideas, browse the 500+ project catalog. For implementation help, use the contact page and explain your required deadline, board and preferred dashboard.

Testing Plan

Test normal room air and controlled changes such as ventilation.
Separate CO2 measurement from general gas trend readings.
Warm up MQ sensors before recording values.
Log readings over time.
Explain sensor limitations clearly.

Testing is where many FYP projects become stronger. Instead of saying “the system works,” show a small table with test condition, expected result, actual result and screenshot evidence.

Common Mistakes

Calling MQ135 a precise CO2 sensor.
No warm-up time for gas sensors.
No calibration discussion.
Ignoring airflow and sensor placement.
Using ppm claims without reference measurement.

Avoid fixed cost promises in your report. Component prices in Malaysia change by supplier, stock, shipping and module quality, so it is safer to describe the bill of materials and explain what is optional.

What to Show During Viva

Prepare a short demo path:

Show the wiring and explain the main sensor.
Open the dashboard before triggering the test.
Trigger normal, warning and danger conditions.
Show the timestamped log.
Explain one limitation honestly.
Mention one future upgrade such as casing, battery backup, LoRa, better calibration or mobile app.

This gives the panel a complete story: problem, prototype, data, result and improvement.

Related Rectronx Pages

FAQ

Is this IoT project suitable for beginners?

Yes, if the first version uses one sensor, one ESP32 and one dashboard. Add extra sensors only after the basic flow is stable.

Do I need a mobile app for this FYP?

Not always. A web dashboard, Firebase page, Blynk screen or Telegram alert can be enough if the data flow and testing are clear.

Can I claim high accuracy?

Only if you calibrate and compare against a suitable reference. For most student prototypes, it is better to say the system monitors trends and alerts based on project-defined thresholds.