Differences

This shows you the differences between two versions of the page.

--- amc:ss2025:group-yin:start [2025/08/08 17:38] – 24378_students.hsrw
+++ amc:ss2025:group-yin:start [2025/08/08 17:51] (current) – 24378_students.hsrw
@@ Line 1: / Line 1: @@
 ====== Smart Home Monitoring and Automation System ======
+''by 24378 - Yin Min Oo''
+====Abstract====
-Abstract
 This project implements a WiFi-based smart home system using an ESP32 microcontroller. The system integrates motion, temperature, humidity, and light sensors to automate a relay and servo mechanism and sends alerts via Pushover app when motion is detected in Away mode. A web interface allows toggling between Home and Away modes. The system prioritizes real-time motion detection using FreeRTOS task scheduling.
-. Introduction
+====1. Introduction====
 Smart home systems improve security and energy efficiency by automating device control and providing remote notifications. This work focuses on a compact implementation using ESP32 and commonly available sensors, emphasizing responsiveness and minimal false alerts.
-. System Architecture and Hardware
+====2. System Architecture and Hardware====
+===2.1 System Architecture===
-.1 System Architecture
 {{ :amc:ss2025:group-yin:system_architecture.png?direct&200 |}}
 Figure 1: System Architecture of the Home Automation System
@@ Line 20: / Line 17: @@
 The Application Logic Layer is where the main decision-making happens. It reads sensor data, checks if any values cross the set thresholds, and controls the devices based on that. Task scheduling is handled using FreeRTOS, where motion detection is the highest priority, temperature and humidity are in the middle, and light sensing is the lowest. At the base is the Hardware Layer, made up of the ESP32 microcontroller connected to various components: a PIR motion sensor (digital input), AHT20 temperature and humidity sensor (I2C), APDS9960 light sensor (I2C), a relay (digital output), and a servo motor (PWM). These are connected using standard protocols like GPIO and I2C.
-The diagram below shows how the main hardware components are connected.
+The diagram below shows how the main hardware components are connected.\\
 {{ :amc:ss2025:group-yin:hardware_assembly.png?direct&400 |}}
 Figure 2: Hardware Assembly of the System
-.1 Hardware Components
+===2.1 Hardware Components===
 .	ESP32: Central microcontroller with WiFi support.
 .	PIR Sensor: Detects human movement.
@@ Line 49: / Line 44: @@
 Figure 7: Servo Motor 3.3V
-.2 Software Components
+===2.2 Software Components===
 •	Arduino IDE with FreeRTOS
 •	ESPAsyncWebServer for web interface
@@ Line 55: / Line 50: @@
 •	Servo and sensor libraries (Adafruit, SparkFun)
-. Implementation
+====3. Implementation====
+===3.1 Sensor Integration===
-.1 Sensor Integration
 Other sensors except motion sensor is activated every 5 seconds. Motion sensor is activated every 5 milliseconds when in “Away” mode. Temperature and humidity activate the relay to switch the ventilator, light intensity controls curtain adjustment via a servo. Motion is processed via interrupt and high-priority task.
-.2 Network and Pushover Setup
+===3.2 Network and Pushover Setup===
 ESP32 connects to local WiFi and communicates with push notification with the Pushover APP. Messages are sent only when motion is detected, and the system is in Away mode.
 The system uses the Pushover service to send motion detection alerts to the user’s mobile device. A user account was created on the Pushover platform, and a new application was registered to obtain the required User Key and API Token. These credentials are used in the ESP32 firmware to authenticate with the Pushover API.
@@ Line 68: / Line 60: @@
 When motion is detected and the system is in “Away” mode as described in the table 1, the ESP32 sends an HTTPS POST request to the Pushover API endpoint with the alert message. This integration allows real-time push notifications, ensuring timely alerts directly to the user’s phone.
-.3 Web Server Interface
+===3.3 Web Server Interface===
 Users access a web page hosted on ESP32 to toggle between Home and Away mode. The page also displays current sensor values and relay state.
-.4 FreeRTOS Task Priority and Control Logic
+===3.4 FreeRTOS Task Priority and Control Logic===
 Table 1: Task Priorities of The Seosor Tasks (3 = Highest, 1 = Lowest)
 ^ Tasks            ^ Priority  ^ Interval    ^
@@ Line 80: / Line 70: @@
 | Light Sensor     | 1         | Every 5 s   |
-Table 2: Control Logic and Thresholds of Detected Environmental Values
+Table 2: Control Logic and Thresholds of Detected Environmental Values\\
 ^ Sensor Values      ^ Threshold                ^ Action                       ^
 | Motion detected    | No threshold (digital)   | Pushover Notification Alert  |
@@ Line 88: / Line 77: @@
 | Light Sensor       | T<25’C or humidity<60    | Servo is triggered           |
-. Results
+====4. Results====
+===4.1 System Behaviour===
-.1 System Behaviour
 The system connects to WiFi successfully and displays its local IP address for user access. Motion alerts are sent via Pushover only when the system is in Away mode and actual human motion is detected. The servo motor responds to ambient light levels by adjusting the blinds—closing when light is too strong and opening when it drops. The relay is activated when either the temperature exceeds a set threshold or humidity rises above the defined limit, helping manage indoor climate conditions effectively.
-. Demonstration
+====5. Demonstration====
 System boots, connects to WiFi, and hosts a web page. Home or away mode can be toggled on the page for the motion sensor detection. The interface also shows the status of light, temperature and humidity.
-{{ :amc:ss2025:group-yin:home_and_away_mode_in_web_interface.png?direct&400 |}}
+{{ :amc:ss2025:group-yin:home_and_away_mode_in_web_interface.png?direct&400 |}}\\
 Figure 8: “Home” and “Away” mode in web interface.
 Movement in Away mode triggers Pushover notification alert as shown in figure 8.
-{{ :amc:ss2025:group-yin:pushover_notification_in_away_mode.png?direct&400 |}}
+{{ :amc:ss2025:group-yin:pushover_notification_in_away_mode.png?direct&400 |}}\\
 Figure 9: Triggered pushover notification in "away" mode when motion is detected.
@@ Line 113: / Line 97: @@
 The video demonstrates the motion sensor detection when the system is set to away mode and how the push notification is triggered. It furthermore shows how the servo is activated when the light level is above or below the threshold and how the relay is activated based on the humidity level. However, the temperature sensor cannot be manipulated above the threshold and as it is dangerous. Nevertheless, it can be clearly seen in the code attached.
-. Limitations and Areas for Improvement
+====6. Limitations and Areas for Improvement====
 •	Sensitivity of Motion Detection: The motion sensor may sometimes fail to trigger alerts.
 •	Reliance on Stable WiFi Connection: The system requires a stable WiFi connection to function properly. Interruptions or changes in IP address may disrupt access to the web interface and push notifications. Implementing fixed IP addressing or network reconnection strategies could enhance reliability.
@@ Line 121: / Line 104: @@
 •	Servo Movement Optimization: The servo motor moves to preset positions based on light intensity without checking its current state, which may cause unnecessary movement. Adding state checks before actuation could improve efficiency and reduce wear.
-.  Conclusion
+====7.  Conclusion====
 This ESP32-based smart home system demonstrates motion-based alerting and light-driven automation. With FreeRTOS prioritization, the system ensures fast response to motion events. The future work includes improving motion detection, enhancing WiFi stability, adding manual test modes, supporting multi-user notifications, and optimizing servo movements based on state checks.
+<code>#include <WiFi.h>
+#include <WiFiClientSecure.h>
+#include <ESPAsyncWebServer.h>
+#include <Wire.h>
+#include <SparkFun_APDS9960.h>
+#include <Adafruit_AHTX0.h>
+#include <ESP32Servo.h>
+// WiFi credentials
+const char* ssid = "Vodafone-CA64";
+const char* password = "2Mm6mN7z6LFCYLNG";
+// Pushover credentials
+const char* pushoverUserKey = "uphxjot11p6kasrdgmjvkpm6v5hsod";
+const char* pushoverAppToken = "am7ebju1mdpp82axev8x9675qai6x3";
+// Pin definitions
+#define PIR_PIN 13
+#define RELAY_PIN 14
+#define SERVO_PIN 12
+// Hardware objects
+SparkFun_APDS9960 apds;
+Adafruit_AHTX0 aht;
+Servo myservo;
+AsyncWebServer server(80);
+WiFiClientSecure secureClient;
+// States
+volatile bool motionDetected = false;
+bool isHome = false;
+bool canSendAlert = true;
+float currentTemp = 0.0, currentHum = 0.0;
+uint16_t currentLight = 0;
+// Task handles
+TaskHandle_t motionTaskHandle;
+TaskHandle_t tempHumTaskHandle;
+TaskHandle_t lightTaskHandle;
+// Motion ISR
+void IRAM_ATTR motionISR() {
+  if (!isHome) {
+    motionDetected = true;
+    Serial.println("⚡ Interrupt: Motion flag set");
+  }
+}
+// Send pushover message
+void sendPushover(String message) {
+  if (WiFi.status() == WL_CONNECTED) {
+    secureClient.setInsecure();
+    String postData = "token=" + String(pushoverAppToken) +
+                      "&user=" + String(pushoverUserKey) +
+                      "&message=" + message;
+    if (!secureClient.connect("api.pushover.net", 443)) {
+      Serial.println("❌ Connection to Pushover failed");
+      return;
+    }
+    secureClient.println("POST /1/messages.json HTTP/1.1");
+    secureClient.println("Host: api.pushover.net");
+    secureClient.println("Content-Type: application/x-www-form-urlencoded");
+    secureClient.print("Content-Length: ");
+    secureClient.println(postData.length());
+    secureClient.println();
+    secureClient.print(postData);
+    // Read HTTP response headers
+    while (secureClient.connected()) {
+      String line = secureClient.readStringUntil('\n');
+      Serial.println(line);
+      if (line == "\r") break;
+    }
+    // Read HTTP body
+    String response = secureClient.readString();
+    Serial.println("🔄 Pushover Response Body:");
+    Serial.println(response);
+    Serial.println("📤 Message sent");
+  } else {
+    Serial.println("📡 WiFi not connected");
+  }
+}
+void setup() {
+  Serial.begin(115200);
+  pinMode(PIR_PIN, INPUT);
+  pinMode(RELAY_PIN, OUTPUT);
+  digitalWrite(RELAY_PIN, LOW);
+  myservo.attach(SERVO_PIN);
+  myservo.write(0);
+  Wire.begin(4, 5); // I2C pins
+  if (!apds.init()) Serial.println("❌ APDS9960 init failed");
+  else apds.enableLightSensor(false);
+  if (!aht.begin()) Serial.println("❌ AHT20 init failed");
+  attachInterrupt(digitalPinToInterrupt(PIR_PIN), motionISR, RISING);
+  WiFi.begin(ssid, password);
+  Serial.print("Connecting to WiFi");
+  while (WiFi.status() != WL_CONNECTED) {
+    delay(500);
+    Serial.print(".");
+  }
+  Serial.println("\n✅ Connected! IP: " + WiFi.localIP().toString());
+  // Web UI
+  server.on("/", HTTP_GET, [](AsyncWebServerRequest *request) {
+    String html = "<html><body><h2>ESP32 Home System</h2>";
+    html += "<p><b>Mode:</b> " + String(isHome ? "HOME" : "AWAY") + "</p>";
+    html += "<form action=\"/toggle\" method=\"POST\">";
+    html += "<input type=\"submit\" value=\"Toggle Home/Away\"></form><hr>";
+    html += "<p><b>Temp:</b> " + String(currentTemp, 1) + " °C</p>";
+    html += "<p><b>Humidity:</b> " + String(currentHum, 1) + " %</p>";
+    html += "<p><b>Light:</b> " + String(currentLight) + " lux</p>";
+    html += "<p><b>Relay:</b> " + String(digitalRead(RELAY_PIN) ? "ON" : "OFF") + "</p>";
+    html += "</body></html>";
+    request->send(200, "text/html", html);
+  });
+  server.on("/toggle", HTTP_POST, [](AsyncWebServerRequest *request) {
+    isHome = !isHome;
+    motionDetected = false;
+    canSendAlert = true;
+    request->redirect("/");
+  });
+  server.begin();
+  // FreeRTOS tasks
+  xTaskCreatePinnedToCore(motionTask, "MotionTask", 4096, NULL, 3, &motionTaskHandle, 0);
+  xTaskCreatePinnedToCore(tempHumTask, "TempHumTask", 4096, NULL, 2, &tempHumTaskHandle, 1);
+  xTaskCreatePinnedToCore(lightTask, "LightTask", 4096, NULL, 1, &lightTaskHandle, 1);
+}
+void loop() {
+  // RTOS handles everything
+}
+// Motion Task (priority 3)
+void motionTask(void *pvParameters) {
+  while (1) {
+    if (!isHome && motionDetected) {
+      motionDetected = false;
+      Serial.println("🚨 Motion Detected! Processing...");
+      if (canSendAlert) {
+        Serial.println("📢 Attempting to send push message...");
+        sendPushover("🚨 Motion detected at your home!");
+        canSendAlert = false;
+        // Re-enable alert after 5s
+        xTimerHandle alertTimer = xTimerCreate("alertTimer", pdMS_TO_TICKS(5000), pdFALSE, 0, [](TimerHandle_t xTimer) {
+          canSendAlert = true;
+          Serial.println("✅ Alert re-enabled");
+        });
+        xTimerStart(alertTimer, 0);
+      } else {
+        Serial.println("🔁 Alert temporarily blocked");
+      }
+    }
+    vTaskDelay(pdMS_TO_TICKS(5));
+  }
+}
+// Temp/Humidity Task (Priority 2)
+void tempHumTask(void *pvParameters) {
+  while (1) {
+    sensors_event_t humidity, temp;
+    aht.getEvent(&humidity, &temp);
+    currentTemp = temp.temperature;
+    currentHum = humidity.relative_humidity;
+    Serial.printf("🌡 Temp: %.1f°C, 💧 Hum: %.1f%%\n", currentTemp, currentHum);
+    if (currentTemp >= 25.0 || currentHum >= 70.0) {
+      digitalWrite(RELAY_PIN, HIGH);
+      Serial.println("✅ Relay turned ON");
+    } else {
+      digitalWrite(RELAY_PIN, LOW);
+      Serial.println("❌ Relay turned OFF");
+    }
+    vTaskDelay(pdMS_TO_TICKS(5000));
+  }
+}
+// Light Task (priority 1)
+void lightTask(void *pvParameters) {
+  bool blindsClosed = false; // Track servo state
+  while (1) {
+    if (apds.readAmbientLight(currentLight)) {
+      Serial.print("💡 Ambient Light: ");
+      Serial.println(currentLight);
+      if (currentLight >= 10000 && !blindsClosed) {
+        myservo.write(180);  // Close blinds
+        blindsClosed = true;
+        Serial.println("🪟 Blinds CLOSED");
+      }
+      else if (currentLight < 10000 && blindsClosed) {
+        myservo.write(0);    // Open blinds
+        blindsClosed = false;
+        Serial.println("🪟 Blinds OPENED");
+      }
+    }
+    vTaskDelay(pdMS_TO_TICKS(5000));
+  }
+}</code>