Project Title: Smart Guest Comfort Management System

Name	GitHub
Mostafa Gaafar	900214463
Omar Saqr	900223343
Farida Bey	900212071

Github Repo: https://github.com/mostafa21314/Guest-Comfort-Management-System

1. The Proposal

Abstract / Elevator Pitch:

Walking into a poorly lit, stuffy, cold, or hot home is a common experience, especially if we forgot to open the windows or adjust the thermometer. Adjusting lights, temperature, and air quality manually can be inconvenient and it takes time to come into effect. Despite the rise of smart homes, many solutions either require constant manual control or are overly complex and expensive for simple everyday needs.

We propose a Presence-Aware Guest Comfort Management System, which aims to solve this problem by creating a smart, responsive environment that automatically adapts to human presence. As soon as someone enters the apartment, the system welcomes them, turns on the lights, improves air freshness, and adjusts the room temperature to create an inviting atmosphere. When the space is no longer occupied, the system intelligently powers down devices to conserve energy and maintain efficiency.

In addition to automation, the system provides users with remote control capabilities through a mobile connection, allowing them to prepare their home environment before arrival. By combining comfort, convenience, and energy efficiency into one integrated solution, this project demonstrates a practical and user-friendly approach to smart living.

Project Objectives & Scope:

Minimum Viable Product (MVP):

• Detect human presence using sensors
• Automatically turn on lights when someone enters
• Play a welcome message/music through a speaker
• Activate an air freshener system upon entry
• Start a fan (cooling system) when presence is detected
• Count the number of people entering and leaving the room
• Automatically turn off lights, fan, and air freshener when the room is empty
• Remote control via Bluetooth or Wi-Fi to allow users to set the environment before arriving.

Stretch Goals:

• Optional mobile app interface for user-friendly control
• Use humidity sensing to regulate mist output and prevent overuse
• Temperature-based fan speed control, fan intensity scales with how hot the room is rather than simple on/off
• Multi-room extension by replicating the sensor/actuator setup across more than one room simultaneously

2. System Architecture

2.1 High-Level Block Diagram:

A visual representation of the entire system (inputs, processing, outputs, and power supply).

Subsystem Breakdown:

The system is built around five interconnected subsystems that work together to create an automated guest comfort experience.

The sensing subsystem consists of a PIR/IR break-beam sensor at the entrance to monitor guest entry and exit, a temperature sensor, a humidity sensor, and a light sensor. These sensors continuously sample the environment and forward their readings to the MCU for processing.

The processing subsystem is the MCU, which acts as the brain of the entire system. Upon receiving sensor data, it runs several layers of logic: an occupancy counter that tracks the number of guests entering and leaving the room, threshold-based control that compares sensor readings against predefined values to determine which actuators need to be triggered, event-based triggers that fire specific actions such as a welcome greeting when the first guest arrives or a goodbye message when the last guest leaves, and a continuous feedback loop that keeps re-reading sensors after actuators fire to ensure the environment stays within the desired comfort range.

The actuation subsystem consists of four actuators: a fan or AC unit for temperature regulation, an air atomizer for humidity control, LED lights for ambient lighting, and a speaker for audio greetings. Each actuator is driven by the MCU and activated only when its corresponding condition is met.

The wireless communication subsystem is a WiFi/Bluetooth module that connects bidirectionally to the MCU, allowing a remote application to send manual override commands such as pre-cooling the room before guests arrive, while simultaneously receiving live system status updates.

Finally, the power subsystem provides a regulated 3.3V supply to the MCU, which in turn distributes power to all other components in the system.

3. Hardware Design

Component Selection:

Schematics & Wiring:

Circuit diagrams, pinout tables, and breadboard layouts.

Bill of Materials (BOM):

A table listing component names, part numbers, quantities, costs, and links to datasheets.

Power Budget:

Calculations ensuring your power supply can handle the peak current draw of all components combined.

4. Software Implementation

4.1 Software Architecture:

Description of the firmware design (e.g., Bare-metal Superloop, Interrupt-driven, or RTOS).

4.2 Flowcharts & State Machines:

Visual diagrams mapping out the core logic, state transitions, and interrupt service routines (ISRs).

4.3 Key Algorithms:

Explanations of any complex logic used (e.g., PID control loops, digital filtering, sensor fusion).

4.4 Development Environment:

Compilers, IDEs, and toolchains used (e.g., Keil, PlatformIO, STM32CubeIDE).

5. Testing, Validation & Debugging

5.1 Unit Testing:

How individual hardware components and software functions were tested in isolation.

5.2 Integration Testing:

How the system was tested as a whole.

5.3 Challenges & Solutions:

A log of major bugs, hardware failures, or design flaws you encountered, and the engineering steps you took to solve them.

6. Results & Demonstration

6.1 Final Prototype:

High-quality photos of the completed build.

6.2 Video Demonstration:

A link to a short video showing the system working in real-time under various conditions.

6.3 Performance Metrics:

Data showing how well the project met its initial objectives (e.g., "Response time was measured at 12ms, well within our 50ms goal").

7. Project Management

7.1 Division of Labor:

Name	Contribution
Mostafa Gaafar	Project Proposal, Sensors and Actuators needed, Timeline
Omar Saqr	System Architecture, Timeline
Farida Bey	System Architcture, Project Proposal

7.2 Timeline:

Milestones

April 14 (Milestone 1 — Team Formation)

• Formed team of three: Mostafa Gaafar, Omar Saqr, and Farida
• Decided on project idea: Presence-Aware Guest Comfort Management System
• Submitted team formation through the wiki page

April 15 (Milestone 2 — Proposal Presentation)

• Deliver in-class proposal presentation
• Prepare hardware/software block diagram
• Refine the proposal according to comments and feedback

April 20 (Checkpoint A)

• Finalize problem statement and proposed solution
• Prepare component list
• Define functional and non-functional requirements

April 29 (Milestone 3)

• Implement guest presence detection
• Implement ultrasonic mist maker for air freshening
• Implement LED lighting control
• Implement temperature regulation using sensors and fan

May 6 (Checkpoint B)

• Add humidity sensing to regulate mist maker output
• Implement speaker for guest greeting
• Implement people counter with entry/exit logic

May 13 (Milestone 4)

• Add Bluetooth remote control
• Allow users to remotely adjust environment before arrival
• Develop a simple mobile app interface for remote control

8. Appendices & References

8.1 Source Code Repository:

Link to your GitHub/GitLab repo.

8.2 References:

Links to datasheets, tutorials, academic papers, and course materials used during development.