Rectronx Circuits
Back to Catalog
IoT & EmbeddedAdvancedFYP / Projek Akhir Tahun Ready

IoT-Based Smart Curtain Control with Light Sensor

IoT-Based Smart Curtain Control with Light Sensor is an iot monitoring and automation prototype that can be demonstrated with BH1750 or paired LDR light sensors. A realistic FYP outcome is a working prototype with this processing path: Reads sensors, applies control logic and provides WiFi/Bluetooth when required; Converts readings into a documented state, threshold or event. The result is delivered through WiFi router/hotspot and dashboard service, Opto-isolated relay module, Servo motor. The important proof is repeatable Time-stamped database or data logger, not just a device that powers on.

Project Snapshot

CategoryIoT & Embedded
DifficultyAdvanced
Time Required8-12 weeks including component testing, integration, calibration and demo preparation
CostNo fixed price. Cost depends on selected controller, sensors, communication modules, casing, dashboard/app features and documentation scope.
Suitable forDiploma, Degree, FYP, Projek Akhir Tahun
ComponentsESP32 development board, BH1750 or paired LDR light sensors, WiFi router/hotspot and dashboard service, Time-stamped database or data logger
Expected outputWiFi router/hotspot and dashboard service, Opto-isolated relay module, Servo motor

Quick Summary

IoT-Based Smart Curtain Control with Light Sensor is a iot monitoring and automation prototype idea for students who need a working demo with BH1750 or paired LDR light sensors. A good version focuses on WiFi router/hotspot and dashboard service, Opto-isolated relay module, Servo motor using ESP32 development board, BH1750 or paired LDR light sensors, WiFi router/hotspot and dashboard service, with testing evidence for input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour.

Difficulty

Advanced

Time Required

8-12 weeks including component testing, integration, calibration and demo preparation

Cost

No fixed price. Cost depends on selected controller, sensors, communication modules, casing, dashboard/app features and documentation scope.

Engineering profile

IoT monitoring and automation prototype

Function Flow

1

Power and initialise

The regulated 5 v supply with common ground starts the ESP32 development board and connected modules within their voltage and current requirements.

2

Acquire the input

BH1750 or paired LDR light sensors supplies the project measurement, identity or trigger.

3

Validate the signal

Firmware rejects missing or implausible samples and applies calibration, debounce or averaging appropriate to the module.

4

Make the decision

The controller compares the validated value with the documented threshold, authorisation rule or operating state.

5

Act and communicate

Opto-isolated relay module + Servo motor presents the local result, while the communication link sends the corresponding event or reading.

6

Record and recover

The logger stores the input, decision, output and timestamp. On a fault, the system enters a defined safe state instead of silently continuing.

System Block Diagram

Functional signal and data path for the recommended prototype scope. Final pin assignments and electrical wiring must follow the exact module datasheets.

input

BH1750 or paired LDR light sensors

Measures ambient or differential light level after calibration

process

ESP32 development board

Reads sensors, applies control logic and provides WiFi/Bluetooth when required

process

Filtering and decision logic

Converts readings into a documented state, threshold or event

output

Opto-isolated relay module + Servo motor

Switches the selected demonstration load; Moves the small mechanical actuator to a commanded position

communication

WiFi router/hotspot and dashboard service

Transfers readings and events to the selected application service

data

Time-stamped database or data logger

Stores readings, events and output states for report evidence

BH1750 or paired LDR light sensorsmeasured signalESP32 development board
ESP32 development boardcalibrated value/eventFiltering and decision logic
Filtering and decision logicstatus/control commandOpto-isolated relay module + Servo motor
Filtering and decision logicalert/telemetryWiFi router/hotspot and dashboard service
WiFi router/hotspot and dashboard servicetimestamped recordTime-stamped database or data logger

Recommended Components & Platform

ESP32 development board

controller

Reads sensors, applies control logic and provides WiFi/Bluetooth when required

View component guide

BH1750 or paired LDR light sensors

input

Measures ambient or differential light level after calibration

View component guide

WiFi router/hotspot and dashboard service

communication

Transfers readings and events to the selected application service

Time-stamped database or data logger

data

Stores readings, events and output states for report evidence

Opto-isolated relay module

output

Switches the selected demonstration load

View component guide

Servo motor

output

Moves the small mechanical actuator to a commanded position

View component guide

Regulated 5 V supply with common ground

power

Provides stable power while keeping higher-current loads on suitable drivers

Engineering Validation Notes

Verify every module voltage, logic level, current draw and driver requirement against the exact purchased board datasheet before wiring.

Calibrate or baseline the input with known test conditions and report repeatability, response time and observed limitations.

Learning Resources

Build Scope Options

Basic prototype

Core demo using ESP32 development board, BH1750 or paired LDR light sensors, WiFi router/hotspot and dashboard service, Time-stamped database or data logger with visible input and output response.

Intermediate prototype

Adds dashboard/database logging, alerts, calibration notes, and cleaner wiring for reliable demonstration.

Advanced prototype

Adds casing, mobile/cloud features, multi-node setup, image processing, maps, or reporting depending on scope.

Expected Demo Outcome

  • Shows WiFi router/hotspot and dashboard service, Opto-isolated relay module, Servo motor from real or realistic BH1750 or paired LDR light sensors.
  • Stores or displays Time-stamped database or data logger as report evidence.
  • Demonstrates the main iot monitoring and automation prototype workflow end to end.
  • Includes a clear test scenario for input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour.

Accuracy & Limitations

This is realistic for FYP when the scope stays controlled: Validate the input-to-controller-to-output path with safe bench tests before adding cloud features, casing, or extra modules.

Prototype reliability depends on correct wiring, stable power supply, and proper module selection.

Sensor readings can vary with placement, calibration, environment, and demo conditions.

Validation & Testing Plan

Run repeated tests under controlled demo conditions and record readings or status changes.

Verify input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour before adding extra features.

Capture photos, dashboard screenshots, serial logs, or database entries as testing evidence.

Document sensor/module limits honestly so the report does not overclaim industrial accuracy.

Troubleshooting

If readings are unstable, test the sensor separately before connecting the dashboard or app.

If the module resets, check power supply, common ground, loose jumper wires, and current requirements.

If alerts or cloud updates fail, test WiFi, hotspot, SIM balance, API token, and internet connection early.

If the demo is hard to explain, focus on one repeatable workflow for WiFi router/hotspot and dashboard service, Opto-isolated relay module, Servo motor.

Common Mistakes

  • Choosing a scope that is too large for the available FYP timeline.
  • Validate the input-to-controller-to-output path with safe bench tests before adding cloud features, casing, or extra modules.
  • Writing objectives that do not match the actual prototype or software demo.
  • Preparing no backup demo flow for viva day.
  • Using weak power supply, loose jumper wires, or unprotected sensors during demonstration.
  • Skipping calibration or test readings before presenting results.

Suggested Report Sections

Problem statement and project background

Objectives focused on iot monitoring and automation prototype and achievable prototype scope

System block diagram showing BH1750 or paired LDR light sensors -> processing -> WiFi router/hotspot and dashboard service, Opto-isolated relay module, Servo motor

Methodology using ESP32 development board, BH1750 or paired LDR light sensors, WiFi router/hotspot and dashboard service, Time-stamped database or data logger with data flow and user/prototype workflow

Testing results for input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour

Limitations, discussion, and future improvements

Alternatives

Mobile app or Blynk dashboardFirebase or cloud databaseTelegram, WhatsApp, or SMS alertingCustom enclosure and cleaner wiring

Related Projects

FAQ

Is "IoT-Based Smart Curtain Control with Light Sensor" suitable for FYP?

Yes. This title can be suitable for FYP or Projek Akhir Tahun when the scope is controlled. The recommended scope is validate the input-to-controller-to-output path with safe bench tests before adding cloud features, casing, or extra modules.

What difficulty level is this project?

The suggested difficulty is Advanced. The actual difficulty depends on whether you choose a basic, intermediate, or advanced prototype scope.

What platform can this project use?

This project can be planned using ESP32 development board, BH1750 or paired LDR light sensors, WiFi router/hotspot and dashboard service, Time-stamped database or data logger. The final platform can be adjusted based on supervisor requirements and the chosen scope; common alternatives include Arduino, ESP32, Raspberry Pi, or another controller depending on the required features.

Is there a fixed project price?

No fixed price is published because the final quotation depends on project scope, features, timeline, hardware, software, and documentation requirements.

Can Rectronx help with documentation and demo preparation?

Yes. Rectronx can help with project planning, prototype development, coding explanation, report structure, testing evidence, and demo preparation.