SMART ENVIRONMENTAL MONITORING SYSTEM FOR LIVING ROOM USING IoT Submitted by AKKUDALAI SUJEETH [RA211 1003011628] i A PROJECT REPORT BONGU DURGA PRASAD [RA21 11003011935] Under the Guidance of | Dr. R. Thilagavathy (Associate Professor, Department of Computing Technologies) 9 BACHELOR OF TECHNOLOGY ] in partial fulfillment of the requirementsfor the degree In COMPUTER SCIENCE ENGINEERING ; : | @SRM ] INSTITUTE OF SCIENCE & TECHNOLOGY wo Unley a of | DEPARTMENT OF COMPUTING TECHNOLOGIES | COLLEGE OF ENGINEERING AND TECHNOLOGY | SRM INSTITUTE OF SCIENCE AND TECHNOLOGY KATTANKULATHUR- 603 203 NOVEMBER 2024| Department of Computing Technologies a@SRM SRM Institute of Science & Technology 2 (Own Work* Declaration Form This sheet must be filled in (each box ticked to show that the condition has been met). ft must be signed and dated along with your student registration number and included with all assignments you submit - work will not be marked unless this is done To be completed by th e student for all assessments Degree/ Course : B, Tech in Computer Science Engineering Student Name : AKKUDALAI SUJEETH, BON! DURGA PRASAD. Registration Number + RA2111003011628, RA2111003011935. Title of Work SMART ENVIRONMENTAL MONITORING SYSTEM USING IoT We hereby certify that this assessment compiles with the University’s Rules and Regulations relating to Academic misconduct and plagiarism**, as listed in the University Website, Regulations, and the Education Committee guidelines. We confirm that all the work contained in this assessment is our own except where indicated. and that We have met the following conditions: Clearly referenced / listed all soure appropriate # Referenced and put in inverted commas all quoted text (from books, web. etc) © Given the sources of all pictures, data etc. that are not my own © Not made any use of the report(s) or essay(s) of any other student(s) either past or present «Acknowledged in appropriate places any help that I have received from others (e.g fellow students, technicians, statisticians, external sources) «Compiled with any other plagiarism criteria specified in the Course handbook University website We understand that any false claim for this work will be penalized in accordance with the University policies and regulations. DEGUARATION ee ee iu et SR Oe a We are aware of and understand the University’s policy on Academie misconduct and plagiarism and We cea het hac assessment is our own work, except where indicated by referring, and that We have tices noted above, the good academic AKKUDALAT SUJEETH [RA211 1003011628] DSi BONGU DURGA PRASAD {RA2L 11003011935) je om, If you are working in @ group, please write your re every student in your group. mbers and sign with the date for@SRM SRM INSTITUTE OF SCIENCE AND TECHNOLOGY KATTANKULATHUR - 603 203 BONAFIDE CERTIFICATE Certified that 18CSP107L - Minor Project report titled “SMART ENVIRONMENTAL, MONITORING SYSTEM FOR LIVING ROOM USING IoT” is the bonafide work of “AKKUDALAI SUJEETH [RA2111003011628], BONGU DURGA PRASAD {RA2111003011935]” who carried out the project work under my supervision. Certified further, that to the best of my knowledge the work reported herein docs not form any other project report or dissertation on the basis of which a degree or award was conferred on an earlier occasion on this or any other candidate. xe SIGNATURE SIGNATURE SUPERVISOR Dr. G. NIRANJANA, Dr. R. THILAGAVATHY PROFESSOR & HEAD ASSISTANT PROFESSOR Department of Computing Technologies Department of Computing TechnologiesACKNOWLEDGEMENT We express our humble gratitude to Dr. C. Muthamizhchelvan, Vice-Chancellor, SRM Institute of Science and Technology, for the facilities extended for the project work and his continued support We extend our sincere thanks to Dr. T. V. Gopal, Dean- T, SRM Institute of Sci and Technology, for his invaluable support. We wish to thank Dr. Revathi Venkataraman, Professor and Chairperson, School of Computing, SRM Institute of Science and Technology, for her support throughout the project work We encompass our sincere thanks to, Dr. M. Pushpalatha, Professor and Associate Chairperson, School of Computing and Dr. C. Lakshmi, Professor and Associate Chairperson, School of Computing, SRM Institute of Science and Technology, for their invaluable support We are incredibly grateful to our Head of the Department, Dr. G iranjana, Professor, Department of Computing Technologies, SRM Institute of Science and Technology, for her suggestions and encouragement at all the stages of the project work. We want to convey our thanks to our Project Coordinators, Dr.R. Dr. Gnanavel § and Panel Members, Dr.R.Thilagavathy Computing Technologies, SRM Institute of Science and Technology, for their inputs during the hya . Panel Head, and Dr. D. Viji. Department of project reviews and support. We register our immeasurable thanks to our Faculty Advisor, Dr. J. Jaya Pradha, Department of Computing Technologies, SRM Institute of Science and Technology. for leading and helping us to complete our course Our inexpressible respect and thanks to our guide, Dr.R.Thilagavathy, Department of Computational Intelligence, SRM Institute of Science and Technology. for providing us with an opportunity to pursue our project under her mentorship. She provided us with the freedom and support to explore the research topics of our interest. Her passion for solving problems and making a difference in the world has always been inspiring. School of We sincerely thank all the staff and students of Computing Technolog! Computing, S.R.M Institute of Science and Technology, for their help during our project. Finally, family members, and friends for their unconditional love, We would like to thank our parent Constant support and encouragement AKKUDALAT SUIEETH{RA21 1003011628} BONGU DURGA PRASAD[RA21L 1003011935]ABSTRACT Indoor air quality is a growing concem because of the direct impacts on human health, comfort, and productivity. Increased levels of carbon dioxide are an indoor air pollutant common indoors and cause complaints of headaches, fatigue, and reduced cognition. This is more so in enclosed spaces where there is little ventilation, and COs levels can easily reach dangerous limits. The system uses the MQ-135 gas sensor, ESP8266 microcontroller, Blynk application, and relatively simple actuation mechanisms through a fan and buzzer to detect the concentration levels of CO» and perform preventive action by allowing ventilation when the concentration becomes higher than a set point. Blynk platform also provides real-time data visualization. Hardware setup: It connects the MQ-135 sensor with the ESP8266 microcontroller, processes sensor information, calculates CO. values, and transmits sensor data to the Blynk platform using Wi-Fi, This automation negates health risks and de-sensitizes the indoor environment to users. That aside, inthis paper, we discuss the system's design, implementation, and testing to throw more light on its effectiveness when applied to residential and small commercial spaces in IAQ management. This work justifies testing results on a system with efficiency in observing CO: levels and timely response for a viable IAQ challenge solution. Automated ventilation can be seen here a the project represents the next major step in developing smart home technology, hence, bringing 1oT-based application concepts to practical use for improvements in air quality and hence human health and comfort. While this is @ critical issue of health, it ereates further attention to the importance of awareness of [AQ and what value smart connected environmental control can do.TABLE OF CONTE ABSTRACT TABLE OF CONTENTS LIST OF FIGURES LIST OF TABLES ABBREVIATIONS 1 INTRODUCTION 1.1 General (Introduction to Project) 1.2 Motivation 1.3 Sustainable Development Goal of the Project 1.4 Product Vision Statement 1.5 Product Goal 1.6 Product Backlog (Key User Stories with Desired Outcomes) 1.7 Product Release Plan 2. SPRINT PLANNING AND EXECUTION 2.1 Sprint 1 2.1.1 Sprint Goal with User Stories of Sprint | 2.1.2 Funetional Document 2.1.3 Architecture Document 2.1.4 Ul Design 2.1.5 Funetional Test Cases 2.1.6 Daily Call Progress 2.1.7 Committed vs Completed User Stories 2.1.8 Sprint Retrospective iv vii viii2.2 Sprint 2 2.2.1 Sprint Goal with User Stories of Sprint 2 2.2.2 Functional Document 2.2.3 Architecture Document 2.2.4 UI Design 2.2.5 Functional Test Cases 2.2.6 Daily Call Progress 2.2.7 Committed vs Completed User Stories 2.2.8 Sprint Retrospective 2.3 Sprint 3 2.3.1 Sprint Goal with User Stories of Sprint 3 2.3.2 Functional Document 2.3.3 Architecture Document 2.3.4 UI Design 2.3.5 Functional Test Cases 2.3.6 Daily Call Progress 2.3.7 Committed vs Completed User Stories 2.3.8 Sprint Retrospective 3. RESULTS AND DISCUSSIONS 3.1 Project Outcomes (Justification of outcomes and how they align with the goals) 3.2 Committed vs Completed User Stories 4 CONCLUSIONS & FUTURE ENHANCEMENT APPENDIX A, PATENT DISCLOSURE FORM B, SAMPLE CODING C. PLAGIARISM REPORT 2 2 23 26 28 29 30 31 32 33 33 34 37 39. 40 4) 43 44 44 4s 46LIST OF FIGURES FIGURE NO. TITLE PAGE NO. Ll CO? Real time monitoring system in Blynk 7 platform 12 Hardware setup using loT 7 2.0 System Architecture 14 21 Indication of CO: levels in Blynk platform 17 22 Hardware set up for CO2 Monitoring Using loT 28 23 Real Time Monitoring of CO3 levels 39 3.1 Bar graph showing Committed vs Completed of cach 45 User Stories viiTABLE NO Ll 2.1 21.1 2.1.2 2.1.3 2.1.4 2.2 2.2.2 2.2.3 2.2.4 2.3 2.3.2 2.3.3 2.3.4 LIST OF TABLES TITLE User Stories of CO? monitoring and alert system setup Detailed User Stories of Sprint | Access level Authorization Matrix of Sprint | Functional Test Cases of Sprint 1 Committed Vs Completed User Stories of Sprint 1 Sprint Retrospective for the Sprint | Detailed User Stories of Sprint 2 Access level Authorization Matrix of Sprint 2 Functional Test Cases of Sprint 2 Committed Vs Completed User Stories of Sprint 2 Sprint Retrospective for the Sprint 2 Detailed User Stories of Sprint 3 ‘Access level Authorization Matrix of Sprint 3 Functional Test Cases of Sprint 3 Committed Vs Completed User Stories of Sprint 3 Sprint Retrospective for the Sprint 3 vill PAGE NO. 6 18 20 21 22 25 29 31 32 33 36 40 42 43CO: 1AQ tol ESP8266 MQ Blynk APL UAT UL AL. API REST HVAC SLA S3 WiFi NLP SDG UAT RAM ABBREVIATIONS Carbon Dioxide Indoor Air Quality Intemet of Things Wi Fi Microcontroller Module used in lo projects 135 Gas Sensor Model (commonly used for CO2 and air quality monitoring) loT Platform for mobile and web-based monitoring and control Application Programming Interface User Acceptance Testing User Interface Antificial Intelligence Application Programming Interface Representational State Transfer (AP! communication protocol) Heating, Ventilat n, and Air Conditioning Servi Level Agreement Simple Storage Service (AWS Cloud Storage) Wireless Fidelity (for wireless network connection) Natural Language Processing (potential for chatbot integration) Sustainable Development Goal (related to environmental objectives) User Acceptance Testing Random Ace Memory (important in embedded systems)CHAPTER 1 INTRODUCTION .L Introduction to CO2 Monitoring and Alert System: The quality of indoor air plays an essential role in determining the overall health and well-being of individuals occupying a space. In recent years, awareness of indoor air pollutants. particularly carbon dioxide (CO), has grown as studies link poor air quality to numerous adverse health effects. Indoor spaces, especially those with limited ventilation, can accumulate CO: levels that lead to symptoms ranging from mild discomfort to more severe conditions like headaches, dizziness, and cognitive decline. Prolonged exposure to elevated CO: levels can | impair decision-making and reduce productivity, making air quality a crucial factor in environments like homes, offices, and schools. With the advent of Intemet of Things (IoT) technology, it has become possible to create low-cost, smart systems that provide real-time data on environmental factors and take corrective action automatically. loT-based solutions enable users to monitor and control their environment remotely, providing insights and actionable data that traditional systems lack. By integrating sensors, microcontrollers, and wireless communication, ToT devices can detect pollutants like COs and initiate ventilation or air purification to maintain optimal air quality. Such systems not only enhance comfort but also safeguard health, making loT applications a viable solution to IAQ issues. ‘The goal of this project is to design, develop, and test a cost-effective, user-friendly IoT-based COs monitoring and control system. By using the MQ-135 gas sensor, the ESP8266 microcontroller, and the Blynk application, this system offers continuous CO: level monitoring and automates ventilation when thresholds are exceeded. This approach addresses both the health and technological aspects of air quality management, creating a functional solution that could be deployed in a variety of indoor settings.12 Motivation ‘The motivation to do this project comes about because of the growing need to recogni7e indoor air pollution and its implications on the welfare of human beings. As the world focuses extensively on outdoor pollution, that of indoor air quality is disregarded. Modem lifestyles jead to a person spending their most significant amount of time indoors, thus requiring 2" conditions to be healthy. Poor ventilation, high occupancy, cooking, and utilisation of heating appliances increase COs levels toa fatal point Most people will not be aware that concentration and energy. and cognitive functionality can be dramatically reduced from concentrations of more than 1,000 parts of COz inthe ambient air. Long-term exposures to higher: ‘concentrations of CO: can result in giddiness and respiratory ailment, IoT-based proactive intervention is possible through instant monitoring of COs sending alerts and automatic corrective actions within the system. This will integrate smart monitoring and controlling functionalities to make living areas safer and comfortable. The Blynk project is the product of advancements in oT technologies and allows for easy integration of hardware with cloud-based services. This project can be developed using low- cost components and open-source platforms that make it an accessible, scalable, and efficient solution for smart home solutions. ‘Another strong side of this project isthe energy efficiency that this system has provided. its design would allow the fan and buzzer to be ON only while in use to save more energy and lessen the bill, This can be used as a basic framework that can be scalable and modified for future expansions, such as the integration of sensors for different air quality pollutants like PM2.5 or humidity and voice-controlled settings with smart assistants like Amazon Alexa or Google Home. These further develop functionality and give an even more holistic approach to indoor air quality management.13 Sustainable Development Goal of the Project ‘he primary Sustainable Development Goal the project is associated with #s SPC 7 Affordable and Clean Energy. This is ensuring universal access to affordable, reliable. castainable, and modem energy for all. The points highlighted include improving encrBy efficiency, developing renewable forms of energy, and reducing energy-related wastes Although the target is placed more on the macrolevel of energy systems and policies, projects uch as COz monitoring and control prove significant at the household level or micro-level. for example, promoting better ways of using energy, improvement of sustainsbIlty, and most of all responsible energy practice in everyday life. House energy consumption has inereased to a significant level, and present houses contain many electronic appliances. The ar ventilation units or HVAC are kept running mostly. regardless of the quality of air, and use a lot of energy. So, inthis projec the fan can be controlled smartly. The fan is on only when the CO: levels exceed a pre-set threshold and cuts ost when they become normal. This will help reduce the time taken forthe fan to unnecessarily run, thus cutting down electricity consumption while ensuring best quality air. “The architecture used in the project for its cloud-based system supports SIG 7 berause +t allows for remote monitoring and contro, meaning there js minimal need for physical intervention. This also increases convenience but at the same time, it helps in energy savings since it provides realtime insights to users regarding the consumption of energy. The Blynk platform helps users monitor the eves of CO: using ther smartphones and makes sure thatthe fan works only when required. This has shown that the future homes are smart and energy conscious, highlighting how loT can be applied to achieve the SDG 7 objectives a individual and community levels1.4 Product Vision Statement 1.4.1 Audience -Primary Audience: The CO2 Detection and Absorption system includes homeowners and individuals concerned about indoor air quality and its impact on health and well-being. facility administrators, and Secondary Audience: comprises property manage taining safe and healthy indoor environmental health professionals responsible for m environments. 1.4.2. Needs: Primary Needs “Real-Time CO2 Monitoring -Alert System. -CO2 Absorption Feature. Secondary Needs: -Data Analytics and Reporting, -Integration with Smart Home Systems. 1.4.3. Products: Core Product: CO2 Detection and Absorption System: A comprehensive system that continuously monitors indoor CO2 levels, provides real-time data visualization. and activates the absorption feature when necessary to maintain a healthy indoor environment, Additional Features: -Integration with Smart Home Devices. -Al-Driven Air Quality Management -Customizable Alerts and Notifications. -Energy Efficiency. 1.44, Values: Core values: users health by ensuring that indoor air quality remains -Health and Safety: Prot within safe parameters. users to take a proaeti Proactive Air Quality Management: Empowers indoor air quality. Differentiators: -Customization and Flexibility -Al-Driven Insight15 product Goal ‘The primary goal of the product is the optimization of CO: in living environment, making ihe indoor environment healthy and safe. The system monitors the COs concentration continually and provides corrective action, including the automatic triggering of a fan or buzzer whenever needed. The goal will be the design of a safer, healthier indoors through an automatic gystem. This will allow for maximized air quality levels through controlling COz level and thus iden and jynamically responding to alterations. Indeed, indoor air pollution is perhaps the hid serious danger of modem living in a city. It solves the problem by giving a real-time solution {for monitoring and managing indoor levels of COs. So, the users will be given an assurance about air quality without constant attention. It used the MQ-135 sensor with reliable measurement of concentration CO, which provided live data to the ESP8266 microcontroller for later transfer to the Blynk platform. This can show air quality inside via real-time monitoring using a smartphone. This makes it quite convenient and easy because a user does not need constant monitoring: changes in concentration COs can be detected from anywhere. So, the integration by Blynk connects the user to the system wherein he can interact with the data and take proactive measures for indoor air quality. One of the salient characteristics of this product is an auto-response mechanism. Anytime the COs sensor has determined that the levels become too high above a certain threshold defined by the user, the system will automatically drive the fan and enforce the buzzer while reducing CO: by ventilating the room while the buzzer triggers an alert to the inhabitants. This ving because it only comes on in cases where automation ventilation control is very eneney" this is necessary while preserving Sa fe conditions indoors.1.6 product Backlog a new user, I would use it-it should conti | and inform you on how to achieve good indoor air quality: ‘O:2 levels | As auser, T would like to have the system notify me every time t | exceed the safety limits so that I can act accordingly. TAs a user, I would require that the fan auto-on when the levels of CO: are high to #US 3 | give good ventilation. st be employed to ‘As a house owner, the historical values of CO2 concentrations mu: derive trends and adjust ventilation levels. ‘As a developer, it would be modular and easy to extend so | could integrate it with other home automation solutions. ‘Asa property manager, I want to monitor CO> levels in a room or across rooms! buildings from one interface in order to manage air quality effectively across | different spaces. T would like to receive a mobile notification when the CO: level exceeds Asa user, the safe threshold so that I can be alerted even if I am not in the room. ‘Asa user, | want the ability to adjust the CO» threshold limit manually so that | can | fine-tune the system to be more sensitive according to my preferences. Asa parent, that is the Kind of education I would want; how to maintain good air | quality especially in the presence of children, o ensure the family is healthy, ‘As auser, | have to monitor the amount of energy used by the fan and the system over time for appropriate choice-making. Table 1.1 User Stories of COz monitoring and alert system setup 6the product backlog of Co2 monitoring system wag configured using the Blynk platfurra whiclt jg represented in the following Figure 1.1. The Product Backlog consists of the complete COz Real time monitoring system Fach user story consist of necessary parameters like Functional and non-functional parameters, detailed acceptance criteria with linked tasks, Figure 1.2: Hardware setup using loT Figure 1.1: €O2 monitoring system in blynk platform4.7 Product Release Plan Release 1: Basic Monitor and Alert System (Weeks 1-4) sonnect the following hardware to the ESP8266, MQ-135, fan, and buzzer. he code is to monitor levels of CO: and alert through the buzzer. paseline COs levels and threshold calibration at system testing. Release 2: Blynk Platform Integrate (Week 3-5) Set up Blynk to view the program live on your smartphone. resent the COs levels in gauges or charts right on the application interface. ‘st the system using Blynk and verify proper reception of data. lease 3: Automatic fan control (Week 5-8) ~ Automatic switching of a fan on using relay control. ‘Activate the fan only during high CO» events for maximum energy savings. performed test for serving validated automation. Release 4: Testing and Documentation (Week 7-10) Perform stress tests to know how the system will behave under various conditions. Document the hardware configuration, code, and installation. "Include user guides on system maintenance and troubleshooting. Release $: Further Development (Week 10-12) - Others can include sensor integration, such as temperature or humidity. Enable cloud storage " for historical CO: data and analytics. Make voice control with smart assistants like Alexa or Google Home.CHAPTER 2 SPRINT PLANNING AND EXECUTION 2.1 Sprint 1 _ 2,1. Sprint Goal with User Stories of Sprint 1 The Goal of the first sprint is to construct the user landing page and to enable the search functionalities such as skills and courses. Detailed User Stories | US #1 | As anew user, I would use it-it should continuously measure how much COs exists all inform you on how to achieve good indoor air quality. USA | Asa user, I would like to have the system notify me every time the CO: levels exceed the safety limits so that I can act accordingly. U5 | Asa user, | would require that the fan auto-on when the levels of CO: are high to give good ventilation. Table 2.1 Detailed User Stories of sprint 121.2 Functional Document 22d Introduction ntains More Increased level of health concern over quality of air indoors. Indoor air cot te ventilation is lacking. Amongst jeels of pollutants than outdoor at, especially when adequal «, concentration of CO2 is particularly an indicative critical parameter of IAQ aS Tra these pollutant since its concentration directly affects human comfort and cognitive function. High levels of ally cause 1 of © C02 concentration (> rm health risks. There should thus be continuous 1m 1000 ppm) lead to headaches and dizziness and may potent long-ter onitoring and real-time contro ventilation especially in confined indoor environments 2.1.2.2. Product Goal ‘Oz Monitoring and Control IoT Project is to develop a user-centric “The primary goal of the C' door air quality through real-time mont and efficient system that ensures healthy in joring and automated control. The application aims to: Empower users to monitor COs levels in thet living spaces using an intuitive mobile application connected to LoT devices. + Provide real-time alerts and notifications when CO: levels exceed safe thresholds, ensuring prompt action to maintain a healthy environment + Facilitate automated control of ventilation systems, such as fans, to optimize air quality without unnecessary energy consumption. :s of the importance of maintaining optimal CO> levels for health and «Promote awarenes: ers to adopt sustainable practices in their homes. well-being, encouraging U 2.1.2.3. Demography (Users, Location) Users: + Target users: Homeowners: & Renters Health-conscious individuals. Environment enthusiasts and Technology savvy Users: aking to improve their indoor air quality and reduce health + User characteristics: Users s risks associated with high CO: levelsan Target Location: Global ‘pphcation, with a particul ar emphasis on urban areas where indoor air pollution is a Significant concer, "1.24. Business Processes ~The key business processes include: ser Registration and Authentication: + COs evel Monitoring: Real-Time Data Capture: Continuous monitoring of CO: levels using the MQ-135 sensor connected to the ESP8266 microcontroller. + User Aler'System: Threshold Setting: Users can define accepable COs through the Blynk app settings, level thresholds. Automated Control: Energy Management: The system monitors operational time to optimize energy consumption, ensuring the fan runs only when necessary. 2.1.2.5. Features This project focuses on implementing the following key features: Feature I: Real-Time CO: Monitoring 1. Description: : + Development of a Sensor System: Integration of the MQ-135 CO: sensor for continuous monitoring of indoor air quality. 2. User Story: + User-Friendly Interface: A mobile app interface (using Blynk) that displays real- time COs levels, ensuring easy accessibility for user. Feature 2: Automated Air Quality Control 1. Description: + Fan Control Mechanism: Automatic activation of the fan based on COs levels, ensuring optimal air quality while minimizing energy consumption 2. User Story:+ As auser, ike would like to have the system notify me every time the CO» levels exceed the safety limits ‘0 that I can act accordingly. eature 3: User Notifications and Insights 1, Description: + Customizable Notifications: Users can set preferences for alert thresholds and notification types (¢.g., mobile notifications, in-app alerts). 2. User Story: + Asauser, | would require that the fan auto-on when the levels of CO2 are high to give good ventilation. 2.1.2.6. Authorization Matrix Role Access Level Can manage all aspects of the system, including user accounts, device Administrator management, system settings, and data analytics Can access system data, analyse CO: readings, and generate reports but cannot Data Analyst modify system settings or configurations, Can monitor real-time COs levels, receive alerts, and manage their personal settings through the Blynk app, but cannot access system-wide settings or other User users’ data. Can access user accounts for troubleshooting and provide limited updates or Support Staff support documentation but cannot modify system settings. | Matrix “Table 2.1.1 Access level Authoriz: 2.1.2.7. Assumptions «User Accessibility: Users will have aecess to smartphones or devices that support the Biynk app, enabling them to monitor COs levels and receive alerts in real-time + User Engagement: Users will actively engage with the system, adhering to the recommended threshold settings for CO: levels and responding to alerts when notifiedWiFi Connectivity: A stable and reliable Wi-Fi connection will be available for the SP8266 microcontroller to communicate effectively with the Blynk platform and deliver real-time data to users. User Training and Suppor: Users will have access to adequate training resources and technical support to help them understand how to use the system effectively and troubleshoot any issues.313 Architecture Document +11 Application ; Mieroservices Jhitecture to the C2 Monitoring and Control loT system is designed with a microservices are! ems, Each aiiow modularity, scalability, and ease of integration with other smart home syst “service encapsulates a distinct functionality to manage the system’s core operations Key services include + Authentication Service: Manages user login two-factor authentication, and account recovery. 1-135 CO + COz Monitoring Service: This service continuously reads data from the M holds. It sensor, processes the COs levels, and determines if they exceed safe thres! transmits real-time CO: readings to the Blynk platform for user monitoring, «Alert and Notification Service: Responsible for sending real-time alerts to users via the Blynk app when CO: levels cross the defined threshold. The service also controls the buzzer activation as a local alert mechanism within the environment. «Control Automation Service: Manages automated responses, such as activating the fan when COz levels are too high. This service controls the relay module connected to the fan and works in conjunction with the monitoring service to maintain optimal air quality. 2.1.3.2 System Architecture- rao a @1 \ ; © 6 & + fan ysenet Vacate See Figure 2.0 System Architecturepata Exchange Contract: sey of Data Exchanges: ct) yee es are structured to ensure pat exchanges nsure real-time monitoring fr critical functions and periodic sor background proces syste for background processes, optimizing performance and reliability Time Exchan 7 eal-Time Exchanges: Real-time data exchanges are essential for operations like sponitoring CO: levels, sending notifications, and controlling the fan and buzzer Data is transmitted instantly between the sensors, microcontroller, and the Blynk platform to ensure immediate action and feedback. periodic Syncs: Data such as historical COs levels and user activity logs are synchronized periodically. This data syne enables efficient storage and retrieval for analytics without impacting real-time system performance. pata Sets? The system processes and exchanges multiple types of data sets. each with specific sequrements and frequency based on functionality. CO: Sensor Data: Captures real-time CO> levels from the MQ-135 sensor. This data is exchanged continuously between the sensor, the ESP8266 microcontroller. and the Bilynk platform to keep users updated on indoor air quality. «User Preferences Data: Contains user-configured settings, such as CO: threshold levels. notification types, and fan activation preferences. This data is exchanged when a user updates their settings in the Blyak app. «Device Comtrol Data: Includes control commands for the fan and buzzer activation Data is exchanged between the control automation service and the hardware components whenever the CO: threshold is exceeded «Historical Air Quality Data: Logs past CO: levels and system activity over time, This data is periodically synchronized with the cloud and is used for data analysis and visualization on the Blynk app. Mode of Exchanges (API, File, Queue, et) ods are employed across the To facilitate efficient and reliable communication. various metho Platform for data exchange+ API (RESTful): Real-time data exchanges, including sensor data and user preference updates, are handled through RESTful APIs. The Blynk platform's API is used to relay real-time CO: levels and user-configured settings between the front-end (mobile apP) and the back-end (IoT system). _ » Message Queues: For asynchronous tasks such as managing notifications and controlling the fan or buzzer based on CO: levels, a message queue (¢-8-> MQTT or RabbitMQ) is employed. This ensures that alerts and actions are processed reliably, even during high loads. Cloud Storage (File-Based): For bulk data transfers, such as uploading historical COs data logs for analysis, file-based exchanges are used. Data is stored on cloud services like AWS $3, enabling long-term storage and retrieval for analytics.EE ii -—__:z—z————<—_ 114 UI DESIGN Se YR) Figure 2-1: Indication of CO: levels in Blynk platformesture cont uo¥s Monto uoifeaton tortigh ©: Automation 5F unctional Test Cases Steps to Execute Test Test Case Case venty 1. Power on continuous the system CO; 2.Open the montonng —_Blynk app. 3. Observe CO; levels displayed continuously verity 1. Set CO, notification threshold to.2 ‘ssent when lovrvalue. COsexcesds 2. Expose safety limits sensor to COs 3. Check for notifeation smartphone. Verity fon 1. Set COs auto-on threshold to 2 when CO; 1 lowvalve. hen 2. expose sensor to COr 3, Observe if fan turns on automatically Table 2.1 Expected Output CO; levels are continuously displayed on the Blynk app. Notification is sentto smartphone when CO> exceeds Fits. Fanturns on automatically when COs levels are high. Actual output COs levels displayed continuously ‘on the Blynk opp. Notification recened on smariphone when CO: exceeded Fits. Fan turned on automatically when COs levels were gh 2 Functional Test Cases of Sprint | status Pass Pass Pass More Information Ensure phone i connected to Blynk ape adjust threshold 35 needed for testing1.6 Daily Call Progress eck 1: Continuous COs Measurement and Monitoring ‘Goal: Implement continuous CO2 measurement and provide users with information on achieving good indoor air quality «Day (1-3): Set up the development environment and configure the MQ-135 CO» sensor. «Day (4-6): Develop basic functionality for continuous COs measurement. Week 2: Notification System for High CO: Levels Goal: Implement a notification system that alerts users when COs levels exceed safety limits. + Day (1-3): Configure threshold settings for high CO: levels. + Day (4-6): Develop the notification functionality to alert users when CO: exceeds safe limits. Week 3: Automated Fan Control for High CO: Levels Goal: Implement automated fan control to provide ventilation when COs levels are high: + Day (1-2): Configure the relay module for fan control «Day (5:6): Test the automated fan control system for efficiency and responsiveness.1.7 Committed Vs Completed User Stories Us #1 Asa new user, I | would use it-it should continuously measure how much CO> exists and inform you on how to achieve good indoor air quality like to have the system notify me every time the CO: levels exceed the safety limits so that I can act accordingly. HUS 2 Asauser, I would | FUS 3 Asa user, I would require that the fan auto-on when the levels of CO2 are high to give good ventilation. Committed | Completed YES YES | YES INES a YES YES | Completed Table 2.1.3 Com mitted Vs Completed User Stories of Sprint 118 Sprint Retrospective ited lamed Lacked Longed for smoothintegration of Improved understanding More time for tefining Additional testing realtime CO2 Of Sensor calibration and fan automation environment for User monitoring with Blynk data accuracy, response. simulation. app ser feedback was: Leamed best practices for intial setup challenges More tools to test postive on notifications setting appropriate alert with accurate CO, notfcation reabilty. and alert clarity thresholds, readings, Successful end-to-end Gained insights into Lack of advanced Alarger team for testing ensured system balancing alert frequency documentation on Bink faster feature stability with usability integrations. deployment. Table 2.1.4 Sprint Retrospective for the Sprint I 21SPRINT 2 1 Sprint Goal with User Stories of Sprint 2 The goal of the second sprint is to enable advanced functionalities, such as historical tracking, integration with other home automation solutions, and centralized monitorinss <6 multiple spaces. These features are essential for enhancing the usability, modularity Detailed User Stories ‘As a house owner, the historical values of COs concentrations must be employed to derive trends and adjust ventilation levels. ‘Asa developer, it would be modular and easy to extend so I could integrate it with other home automation solutions. ‘As a property manager, I want to monitor CO: levels in a room or across rooms/buildings from one interface in order to manage air quality effectively across | eitfront spaces, led User Stories of sprint 22.2 Functional Document 2.2.1. Introduction As air quality concems grow, itis essential to provide users with detailed insights and Jjexibility in system integration, Monitoring historical CO2 data can help users make informed cisions about ventilation patterns, while a modular system architecture supports integration ith other smart home solutions. Centralized monitoring enables property managers to oversee i. quality across multiple spaces from a single interface, Product Goal The primary goal of Sprint 2 is to enhance the CO: Monitoring and Control 1oT Project by miplementing historical data tracking, modular architecture for easy integration, and centralized multi-room monitoring. The application aims to: «Empower users to track and analyse CO: trends over time to improve indoor air quality ‘management. «Provide developers with a modular system architecture, allowing integration with other home automation devices and system. + Facilitate centralized monitoring for property managers, enabling effective air quality control across different rooms and buildings. 2.23. Demography (Users, Location) /sers + Target users: Homeowners, Developers, and Property Managers. © User characteristics: Users who are interested in advanced control, data analysis, and mart home integration to manage and improve air quality across various settings cation: «Target Location: Global application, with paula elevance in urban and commercial areas where air quality control is critical. 2.2.2.4, Business Processes The key business processes include:ey User Registration and Authentication + Data Logging and Trend Analysis: Continuous logging of CO; levels to help uset analyse trends an nd make data-driven decisions about indoor air quality + APL and Interfi i face Integration: Providing APIs and modular system components for easy integration with other smart home solutions. + Central Dashboard: A single interface displaying CO: levels across multiple rooms/buildings for property managers to oversee and control air quality ¢fficiently 2.2.2.5. Features ‘This sprint focuses on implementing the following key features: Feature 1: Historical Data Logging and Analysis, 3. Description: + Data Logging and Visualization: The system continuously logs CO: data storing it for historical analysis and trend visualization on the Blynk app 4. User Story’ + Asa house owner, | want historical CO: data to help identify trends and make ventilation adjustments to optimize air quality. Feature 2: Automated Air Quality Control 3, Description: + API for Integration: Providing APIs to allow seamless integration with other [oT and smart home systems for a connected experience 4. User Story: «Asa developer, I want the system to be modular and easy to extend, enabling integration with other home automation solutions Feature 3: User Notifications and Insights 3. Description: uMlevels + Multi z Multi-Room Dashboard: A centralized dashboard displaying CO» across multiple spaces, making it easy for property managers to monitor and control air quality in different rooms or buildings. 4, User Story: + As a property manager, 1 want to monitor COs levels in multiple rooms/buildings from a single interface for effective air quality management » 2.6. Authorization Matrix ole. «Access Level F sens | Can manage all aspects of the system, including user accounts, device, dministrator management, system settings, and data analytics. | Can access the modular system architecture, APIs, and integration tools to ‘JDeveloper extend and customize functionalities. Can monitor real-time and historical COs levels, receive alerts, and manage | ser personal settings through the Blynk app | | Tpropery Can access centralized dashboard for monitoring COs levels across multiple anager tooms/buildings but cannot modify system configurations Table 2.2.1 Access level Authorization Matrix 2.1.2.7. Assumptions + Data Accessibility users for trend analysis and system optimization + Modularity: The system is designed with a modular architecture tallow future 'y: Historical data will be stored securely on the cloud, accessible to expansion and integration with other home automation systems. «Centralized Monitoring: Property managers will have access to a centralized dashboard, providing a holistic view of COs levels across multple rooms or buildings. + User Training and Support: Property managers and developers will have access to technical support and training resources to understand and utilize multi-room ‘monitoring and integration capabilities effectively 252.2.3 Architecture Document 22.4.1. Application Microservices: The system's architecture in Sprint 2 continues to follow a microserviees approach 10 supper modularity, scalability, and integration. Key services added in this sprint include. + Historical Data Service: Logs historical CO: levels and allows trend visualization 1" the Blynk app. This data helps users understand long-term air quality trends. + Integration API Service: Provides APIs to allow other smart home devices or systems to connect and interact with the COs Monitoring and Control system for an integrated experience. + Multi-Room Monitoring Service: Aggregates data from multiple COz sensors across different rooms or buildings and displays it on a centralized dashboard for property manager, 2.2.3.2 System Architecture ‘The system architecture of the CO: Monitoring and Control foT project is designed to and ease of integration. As the system evolves. especially with (0 handle modular support flexibility, scalability, features introduced in Sprint 2, the architecture becomes more sophisticated t integration, real-time data processing, and centralized monitoring across multiple spaces. A s into independent ased architecture is employed to isolate functionaliti microservices- services, each responsible for a specific task, which enhances scalability, fault tolerance, and ease of development ‘Overview of Key Components “The architecture is structured into several core components that work together to deliver a cohesive CO: monitoring and control experience. These components include the sensor network, microcontroller and control logic, cloud-based services, mobile app interface (Blynk), and a centralized dashboard for multi-room or multi-building monitoring 262.2.3.3. Data Exchange Contract Frequency of Data exchanges Data exchanges are str nf uctured to ensure real-time monitoring for critical functions and periodic updates for background processes, optimizing performance and reliability. + Real-Time Exchanges: Critical operations, such as CO: monitoring, notifications, and ventilation control, are handled in real-time + Periodic Syncs: Historical data and multi-room data syne periodically with the cloud for trend analysis and centralized monitoring Data Sets: The system processes and exchanges multiple types of data sets, each with specific requirements and frequency based on functionality: + Historical CO: Data: Logs CO: levels over time for trend analysis and user insights This data synes periodically with the cloud. + Multi-Room Data: Aggregates CO: levels from various sensors in multiple rooms/buildings for centralized monitoring + Integration Data: Enables API-based exchanges to support integration with other smart home devices. Mode of Exchanges (API, File, Queue, etc.) To facilitate efficient and reliable communication, various methods are employed across the platform for data exchange: «API (RESTful): Provides real-time data exchanges and supports system integration through RESTful APIs, allowing developers to connect other home automation solutions. «Message Queues: For managing multi-room notifications, centralized data aggregation, and trend analysis tasks. tored in cloud services like AWS S3, © Cloud Storage (File-Based): Historical data is s enabling access to long-term data for trend analysis and multi-room monitoring.Figure 2.2: Hardware set up for CO: Monitoring Using loT2.2.5 Functional Test Cases Feature Historical Data Logging MultiRoom Monitoring Modularity Test Test Case Verify CO, data logging Verify multi- oom monitoring functionality Verify system extensibility Steps to Execute Test Case 1.Run system for 24 hours. 2.Check Blynk app for historical data trends, 1,Set up sensors in multiple rooms. 2. Access Blynk app and monitor all rooms. 1. Add new sensor. 2. Configure in app. 3, Monitor for seamless integration. Expected Output Historical CO; data is accessible on the app, CO, levels displayed for each room in Blynk app. New sensor integrated and data displayed on app. Actual Output Status Historical CO, Pass data successfully displayed on app COzlevels for — Pass each room accurately displayed. New sensor Pass data displayed ‘without any issues. Table 2.2.2 Functional Test Cases of Sprint 2 20 More Information Useful for trend analysis Ensure each room sensor thas unique 1D Test with multiple extensions2,2.6 Daily Call Progress Week 4: Set Up and Initial Development al: Establish the foundations Goal: F the foundational components for historical data logging and multi-room monitoring.” + Day (1-3): Set up development environment and configure cloud storage for historical CO: data logging. + Day (4-6): Develop basic functionality for COs data logging. Week 5: Modular Integration and System Extensibility Goal: Enhance system modularity to support future integrations with other smart home devices. + Day (1-3): Refactor code to create a modular architecture, making each component (sensor, fan, buzzer) a standalone module. + Day (4-6): Implement test cases for modular integration. Week 6: Multi-Room Monitoring and Interface Development Goal: Implement multi-room monitoring and enable centralized data display for property managers. + Day (1-3): Set up multiple CO» sensors in different rooms aad configure each sensor to transmit data to the cloud. + Day (4-6): Develop a centralized multi-room monitoring interface on the Blynk app. Week 7: User Feedback, Testing, and Final Adjustments Goal: Conduct comprehensive testing, gather user feedback, and refine the system for deployment. + Day (1-3): Refine the Blynk app interface and notification settings based on user feedback + Day (4-6): Finalize the system and prepare for deployment. 302.2.7 COMMITTED Vs COMPLETED USER STORIES er Story, the historical values of COz concentrations must be employed to derive trends and adjust ventilation levels #US4 Asa house owner, | | YES | Committed [Completed [Status YES #US 5 As a developer, it would be modular and easy to extend so I could integrate it with other home automation solutions YES YES. Completed #US 6 As a property manager, I want to monitor CO: levels ina room or across rooms/ buildings from one interface in order to manage air quality effectively across different spaces YES YES Completed Table 2.2.3 COMMITTED Vs COMPLETED USER STORIES of Sprint 22.2.8 Sprint Retrospective Smooth integration of historical data logaing. User feedback on real-time CO; notifications was positive. Successful modular design made adding features easier. Learned lacked Longed for Gained insights into Better access to test data More automation in Optimizing data forsimulating high CO, _testing multt-toom synchronization. levels. configurations. Learned new techniques Detailed documentation Additional time to refine for handling message on integrating with Blynk the user interface for queues. APL. multi-room monitoring. Understood best Lacked a dedicated More resources to explore practices for testing environment for rmicroservices in loT. large-scale simulations. _with the system. Table 2.2.4 Sprint Retrospective of Sprint 23 sprint 3 yl sprint Goal with User Stories of Sprint 2 ‘The goal of the third sprint is to enhance user interaction by adding notification jantionality customizable threshold settings, and educational content. These features will iporease User engagement, allow personalization, and promote awareness an indoor ait quit for families fine-tune the system to be more sensitive according to my preferences. ‘Asa parent, I want educational information on how to maintain good air quality, especially in the presence of children, to ensure the family is healthy. “Table 2.3 Detailed user stories of Sprint 3 332.3.2 Functional Document 2.3.2.1, Introduction Indoor air quality significantly affects health, especially for vulnerable groups like children. This sprint focuses on adding features that improve user engagement and customization. Mobile notifications for high CO: levels ensure users are promptly alerted, even when away, Adjustable COs thresholds allow users to tailor the system to their needs, and educational content promotes awareness on maintaining healthy indoor air quality. 2.3.2.2. Product Goal The primary goals of this sprint are: + Enable Mobile Notifications: Alert users when CO: levels exceed safe thresholds, ensuring they can take action even if they're not present. + Allow CO2 Threshold Customization: Let users manually adjust the COs threshold limit to better suit their preferences and environmental needs. + Provide Educational Information: Educate users on maintaining indoor air quality. emphasizing family health and well-being 2.3.2.3, Demography (Users, Location) Users: + Target users: Homeowners, parents, and individuals who are health-conscious or environmentally aware, «User characteristics: Users who prioritize family health and seek real-time information on indoor air quality, with a desire for system customization, Location: + Target Location: Global, particularly in urban and suburban areas where indoor air pollution and environmental awareness are significant. 2.3.2.4. Business Processes The key business processes include User Registration and Authentication:Real-Time Alert System: Implement mobile notifications that alert users when CO» _ levels exceed the safety threshold + Customizable Threshold Settings: Provide users with the option to adjust CO: thresholds based on their comfort level + Educational Content Display: Offer tips and information on the Blynk app to help users maintain optimal air quality for family health 2.3.2.8. Features This sprint focuses on implementing the following key features: Feature 1: Mobile CO: Notification 5. Description: * Sends mobile notifications to users when CO: levels exceed the safety threshold, even if the user is not actively monitoring the app. 6. User Story: + Asa user, | would like to receive a mobile notification when the CO: level exceeds the safe threshold so that I can be alerted even if | am not in the room. Feature 2: Customizable CO2 Threshold 5. Deseripti + Allows users to adjust the CO: safety threshold manually to match their personal or environmental preferences. 6. User Story: + Asauser, | want the ability to adjust the CO» threshold limit manually so that 1 can fine-tune the system to be more sensitive according to my preferences. Feature 3: Educational Content on Air Quality 5. Description: + Provides educational information within the Blynk app on maintaining indoor ir quality, especially for family health, 6. User Story:Asa parent, I want educational information on how to maintain good aur quality, especially in the presence of children, to ensure the family is health. | 2.3.2.6. Authorization Matrix Role Access Level Can manage all aspects of the system, including user accounts, device | | management, system settings, and data analytics, as well as access to) |Administrator educational content. | | Can access system data, analyse CO: readings, generate reports, and view Developer educational content but cannot modify system settings or configurations. Can monitor real-time CO: levels, receive alerts, adjust personal settings (including threshold limits), and access educational resources through the User Blynk app. | Can access user accounts for troubleshooting and provide limited updates or support documentation but cannot modify system settings or view educational Support Staff content Table 2.3.1 Access level Authorization Matrix 2.3.2.7. Assumptions «User Accessibility: Users will have access to smartphones or devices that support the Blynk app, allowing them to receive real-time notifications. + User Engagement: Users will adjust CO: threshold settings based on individual preferences and will actively use educational resources provided © Wi-Fi Connectivity: A stable Wi-Fi connection is required for the ESP8266 microcontroller to send notifications and display real-time CO2 data on the Blynk platform. «Educational Content Relevance: Users, particularly parents, will find the educational content valuable for maintaining good indoor air quality and will engage with the tips provided 362.3.3 Architecture Document 2.3.3.1. Application Micioservices: D2 Monit va . The CO: Monitoring and Control loT system uses a microservices architecture for scalability and modularity. Key services include: + Notification Service: Sends real-time alerts via push notifications to users’ mobile devices when CO. levels exceed the threshold, ensuring timely awareness. + Threshold Adjustment Service: Manages user-configured CO: threshold setting: allowing customization for each user's preferences. + Educational Content Service: Displays educational resources on air quality maintenance, with a focus on health and family safety, especially for children. 2.3.3.2 System Architecture The system architecture of the COz Monitoring and Control loT project is designed to support flexibility, scalability, and ease of integration. As the system evolves, especially with features introduced in Sprint 3, System architecture include the sensor network, microcontroller and control logic, cloud-based services, mobile app interface (Blynk), and a centralized dashboard for multi-room or multi-building monitoring. The architecture is structured into several core components that work together to deliver a cohesive COs monitoring and control experience. These components include Notification Service, Threshold Adjustment Service, and Educational Content Service, integrated with the Blynk platform and the 1oT hardware components. 2.3.3.3. Data Exchange Contract: Frequency of Data Exchanges: Data exchanges are structured to ensure real-time monitoring for critical functions and periodic updates for background processes, optimizing performance and reliability. «Real-Time Exchanges: For notifications and COs threshold adjustments, data is exchanged in real-time between the ESP8266, Blynk platform, and user devices. 37+ Pertodic Synes: Educational content and user activity logs are synced penodieally 10 optimize storage, Data Sets: The system processes and exchanges multiple types of data sets, each with specific requirements and frequency based on functionality: + CO2§ ensor Data: Continuously captured from the MQ-135 sensor, transmitted to Blynk for monitoring and triggering alerts. ‘+ User Preferences Data: Stores user-defined CO» threshold limits, retrieved and updated as needed, + Educational Content Data: Provides tips and guidelines on air quality maintenance, accessed periodically through the Blynk app. Mode of Exchanges (API, File, Queue, etc.): To facilitate efficient and reliable communication, various methods are employed across the platform for data exchange: * API(RESTful): Real-time data exchanges for sensor data, user preference updates, and educational content are handled via RESTful APIs with Blynk. «Message Queues: Notifications are managed asynchronously through message queues to ensure timely alerts. «= Cloud Storage (File-Based): Stores user activity logs and educational resources, enabling easy access and retrieval. awtdefine MQ135_PIN Ae © FAN_BUZZER_PIN DS const int CO2_THRESHOLD void setup() { serial. begin(115200); Serial Monitor x Figure 2.3: Real Time Monitoring of CO> levels 392.3.5 Functional Test Cases Feature CO: Notifcation syste Mana! Threstog Adjustment Educaticrs! Information Disp ay Test Case Verity mobie notification for high CO: evels Verity user cer manualy adjust COs threshold Verity dspiay of ecucationa’ rfoon air quaity Steps to Execute Test Case 1.Set CO: threshoid toa low vaue, 2. Expose sensor to CO; source. 3.Verity notification on mobie device. 1.Open Byrne aop. 2. Navigate to thresholg settings. 3.Charge thresho'd value, 4. Obsene system betavion 1.Oper Bynk: 200. 2.Navigate to educational irfo section. 3, Review dspiayes tips on air quality maintenance. Expected Output Mobile notification 'ssent wher COs exceeds safe threshold. System adjusts CO: threshold based on user input. Educational information 'so'splayed swith tips or air quality ‘Actual Output Notification received on mobile as expected. system responds accurately to updated thresho'd settings. Eoucationa content showm clearly ‘with relevant formation. Table 2.3.2 Functional Testcases of Sprint 3 40 Status Pass Pass Pass More Information Ensure phone has intemet connection Test different thresno'd values sure content '5 clear and concise2.3.6 Daily Call Progress Week 4: Notification and Threshold Customization Goal: Implement the mobile notification system for high COs levels and provide users with the ability to manually adjust CO; threshold settings to suit personal preferences. + Day (1-3): Developed and tested the notification functionality for COz thresholds. + Day (4-6): Developed and tested manual CO2 threshold adjustment feature. Week 5: Educational Content Integration Goal: Integrate educational content on air quality to promote awareness and provide guidance on maintaining safe CO: levels, especially for family health ‘© Day (1-3): Designed and integrated educational content in the Blynk app. + Day (4-6): Refined educational content and completed testing. ‘Week 6: Final Testing and User Feedback Goal: Conduct comprehensive testing of all features, gather user feedback, and make final adjustments in preparation for deployment. Day (1-3): Conducted end-to-end testing for all new features (notifications, threshold customization, and educational content). + Day (4-6): Gathered user feedback and made final adjustments. Week 7: Deployment Preparation and Final Documentation. Goal: Finalize deployment preparations, create comprehensive user documentation, and ensure that the system is ready for launch with all features working seamlessly\. + Day (1-3): Finalize system deployment and prepare user documentation. + Day (4-6): Conducted final user acceptance testing (UAT) and refined documentation based on feedback. 412.3.7 COMMITTED Vs COMPLETED USER STORIES er Story to receive a mobile notification when the CO: evel exceeds the safe threshold so that I can be alerted even if | am not in the room THUS 8 As a user, I want the ability to adjust the CO» threshold limit manually so that | can fine-tune the system to be more sensitive according to my preferene: s the [AUS 9 Asa parent, that kind of education | would ant: how to maintain good air quality especia'ly in the presence of children, to | ensure the family is healthy. “| Committed | Completed | Status #US 7 Asa user, I would like Completed “TYES—YES.~—s—~*~*~*«ompicted ‘YES _—+*| YES Completed Table 2.3.3 COMMITTED Vs COMPLETED USER STORIES of Sprint 32.3.8 Sprint Retrospective (Tikes Notifications worked smoothly and provided timely alerts. Customizable thresholds improved user satisfaction Positive user feedback on educational content for families, Learned Learned more about adjusting notification frequency to avoid alert fatigue. Gained insights into user engagement through customization options. Learned the importance of adding value through educational information. Table 2.3.4 Sp a lacked More documentation on best practices for real-time notifications. A dedicated U! designer for enhancing app experience. Lacked sufficient test data for real world air quality variations. Retrospective of Sprint 3 Longed for Additional user feedback on the educational content, More tools to gather live user feedback during testing Additional sensors for more comprehensive testingCHAPTER 3 RESULTS AND DISCUSSION 3.1 Project Outcomes The objective of the COz Monitoring and Control foT Project is to create a user-friendly and efficient system that enables users to maintain ‘optimal indoor air quality. This system will provide real-time monitoring, automated ventilation control, and educational insights to promote a healthy indoor environment, Here are the key outcomes expected from this project User-Friendly Interface for Non-Technical Users The platform will prioritize simplicity and intuitiveness, ensuring accessibility for users with minimal technical skills. The interface, accessible through the Blynk app, will feature easy navigation, clear instructions, and intuitive options to monitor CO: levels, receive alerts, and customize settings. This design will enable a wide range of users, from health-conscious individuals to technology enthusiasts, to interact with the system seamlessly without requiring technical support. By keeping the design user-focused, the CO Monitoring and Control [oT System aims to make indoor air quality management accessible, encouraging widespread use and promoting health-conscious habits. me CO: Monitoring and Notification Support Continuous monitoring of indoor COs levels is at the core of this project. The system will provide real-time data through the Blynk app, displaying up-to-date CO: levels in an easy- to-tead format. When CO: levels exceed user-defined safe thresholds, immediate mobile notifications will alert users, enabling them to take timely action to maintain a healthy environment, This real-time monitoring and alert functionality will provide a proactive approach to indoor air quality management. Users will be promptly informed when indoor CO: /Jevels reach unsafe levels, allowing them to make quick adjustments to prevent adverse health effects, Automated Ventilation Control for Optimal Air Quality The COs Monitoring and Control system will feature an automated veutiation function, which activates a connected fan when CO: levels surpass set thresholds, This automation will ensure optimal air quality without requiring manual imerventons helping users maintain a sate 44vironment efficiently. The automated fun control will save energy by only activating when ecessary, making it both eco-friendly and cost-effective, This outcome ensures that the system es immediate action to improve air quality in real time, especially when users may be ecupied or unable to respond to high CO2 levels manually. This feature is particularly wneficial in enclosed spaces, where poor ventilation can fead to rapid COp accumulation. .2 Committed Vs Completed User stories Committed Vs Completed User Stories By... Committed vs Completed User Stories by Sprint status US #1 US #2 US #3. US#4 US#5 US#6 US#7 US #8 US #9 User Stories Figure 3.1 Bar Graph Showing Committed Vs Completed of each User stories 45CHAPTER 4 CONCLUSION & FUTURE ENHANCEMENTS The COs Monitoring and Control lot. Project successfully delivers a comprehensive jor enhancing yuon for enhancing indoor ted controls solt ANF quality. Through real-time monitoring, automa and user-friendly notifications, the system ensures that users are informed about CO» levels and can take immediate action to maintain a healthy environment. The integration with the Biynk app allows seamless interaction, providing users with insights, notifications, and control over threshold settings, making the system adaptable to individual needs. Educational content on ait quality adds an essential value, promoting awareness and sustainable practices among users, especially those with children or health concerns, By leveraging a microservices architecture, the system is both modular and scalable, enabling future integration with other smart home solutions. Throughout the project, the focus on modular design has allowed for flexible system components, which simplifies maintenance and enhances scalability. Each sprint aimed to address different aspects of user experience, functionality, and system performance, result ina robust system that meets the initial project goals. Comprehensive testing of the notification system, threshold adjustment, and educational content ensured reliability, usability, and clarity ineach feature. The project’s success highlights the importance of data-driven decision-making in home automation and exemplifies how LoT can play a crucial role in enhancing indoor environmental quality for both comfort and well-being, The project opens the door for various future enhancements that could further extend its functionality, usability, and appeal to a broader range of users. The CO Monitoring and Control loT Project, while meeting its primary objectives, presents exciting opportunities for ‘uture enhancements such as these would increase the growth and continued development. project's scope. impact, and value, making it a versatile tool for users invested in creating a healthier, more sustainable living environment, As indoor air quality continues to be a global concer, the evolution of this project could contribute significantly to health-focused mart and pr home solutions, establishing a new standard for environmental awareness otive ty uality management. 46APPENDIX A.PATENT DISCLOSURE FORM 0. ofall Inventors 4fc2 of invention 47lonftoring System is an innovative loT-based , the fan is trigacied 10 enhance ‘entiation, reducing CO? level in| hou oe | ann’ This fystem iomorats an audible buzzer that v3 "COR evels wre high, providing an immediate and noticeabie | let osen eve they ar ot atively monilviog he system.” ' CosteEttective and) Low-Power: Unlike commercial-grade sir quality “monitors whieh eanbe expensive end powcr-ntensie this sup s “Us seisor end ESPS266microcontlir, Keeping éba low while mataning sulle accuracy, : 4 Stand: “hee 4“4 Garand Amvediate Alert Mechanism: Ths ‘Assue of relying solely oi milised. The bore : beyondiherafeiange 5. Simple Installation and Maintenance: iisadiges ‘pesilisis,enabling deployment n'a wide ae of omes, classrooms, a offices, | Those fearurs collectively make our CO2 monitoring stem an inpovnve tion | that is accesdibley effective, and responsive fo air quality needs, aes sont | eve conosco exupotcomfira6dpevestoh of toc sci Con oats eR. | reside, cogmve © | venation sant, 30OF SCIENCE AND TECHNOLOGY | "ANKULATHUR ~ 603203 oe ich, dravings, plot and her eialy tial hel ee ilerstatin as you invention been ised expesimental!? Z ‘Yes, the CO2 wontring systems has undergone pelinary isin: validate the eftecsivenes fits components in detect feted COR levels 31Acie. Akad i Sujecth Deparment CSE SRST Kade compas 8 32B. SAMPLE CODING _ {Q135_PIN AO // Analog pin for MQ-135 sensor AN_BUZZER_PIN DS // Digital pin for fan and buzzer control ¢ hold value for CO: level (set based on calibration) C02_THRESHOLD = 200; // Adjust this value based on testing ‘WMnitialize serial communication for debugging Serial.begin( 115200); 1/ Configure pin modes pinMode(MQ135_PIN, INPUT); pinMode(FAN_BUZZER_PIN, OUTPUT); __// Start with fan and buzzer off “digital Write(FAN_ BUZZER_PIN, LOW); Dt 4d CO> level from the MQ-135 sensor avel'= analogRead(MQ135_PIN);k if COs level exceeds the threshold evel > CO2_THRESHOLD) { 1 on fan and buzzer sitalWrite(FAN_BUZZER_PIN, HIGH); Serial.printin("COz level high! Fan and buzzer activated."); yelse { i Tam off fan and buzzer digitalWrite(FAN_BUZZER_PIN, LOW); Serial.printIn("CO> level normal. Fan and buzzer deactivated."); 3 // Wait a short time before next reading delay(1000); // 1-second delay between readings 49C. PLAGIARISM REPORT Thilagavathy R SAMPLE PROJECT REPORT PRODUCT BASED (1).docx @ ravers B panel SAM ns Lute of scence & Techno.ogy Document Details sasre0o710 emai 3071640368 submision De Now, 2024, 409M GMTHS:30 Dowmose D2:¢ oe 9, 2024, 1210 GMTS:30 te Name SAMPLE PROJECT REPORT. PRODUCT BASED. docx lesa woke Alturnitin roesess men orn 4% Overall Similarity Filtered from the Report pty quae ts Match Groups © e vercnedor austen 13r words 44012 characters Top Sources he raeeetsouces om Ml nt By Suber worhs Studer Popes) 50