To improve the design, I cleaned up the breadboard layout and started planning a more stable setup using a donut board or PCB. These steps helped me get closer to a working and safe prototype.

Following my supervisor’s advice, I also surveyed and compared different DHT11 temperature sensor options. I looked into factors like accuracy, stability, and compatibility with the ESP32 board to ensure the sensor would perform reliably in real-world conditions.

In addition, I planned the logic for temperature-based alerts. This includes setting threshold values and delay timing to avoid false alarms, while still ensuring the system responds quickly to overheating risks. These improvements are part of my goal to make the SmartBaby Car Seat safer and more dependable.

Following the component survey from Week 7, I decided to purchase the DHT11 temperature sensor online. I chose this model based on its compatibility with the ESP32 and its ability to provide stable readings for my project needs.

While waiting for the sensor to arrive, I began preparing the wiring and coding plan to integrate the DHT11 into the system. This includes assigning the correct GPIO pins, planning the temperature threshold logic, and ensuring the buzzer activates only when necessary. These steps are part of my goal to enhance the safety features of the SmartBaby Car Seat system.

I also organized the layout on the breadboard to make it cleaner and easier to troubleshoot. As part of the next phase, I began planning the transition to a PCB for a more permanent and professional setup. This includes evaluating the current component arrangement and preparing for soldering once the design is finalized.

In preparation for the arrival of the DHT11 sensor I ordered online, I created a pin mapping and integration plan. This will help ensure smooth installation and coding once the component arrives, minimizing setup time and reducing errors.

After confirming the sensor’s performance, I updated the wiring layout to include the DHT11. I ensured proper connections for VCC, GND, and the data pin, and labeled each clearly to avoid confusion during future troubleshooting or documentation.

I also explored notification options using the Blynk app. The goal is to implement escalation logic that sends alerts when unsafe temperature levels are detected. This adds a remote monitoring feature to the system, making it more practical and responsive in real-world scenarios.

These steps mark a major milestone in integrating environmental sensing and alert logic into the project.

IoT connectivity was tested using the Blynk app, which consistently delivered real-time notifications to smartphones. Full system trials confirmed that all functions operated reliably, meeting the project’s safety objectives and validating the system’s readiness for deployment.

The system operated smoothly throughout the presentation, with alerts responding accurately to test conditions. This final showcase reflected the dedication invested in development, testing, and thorough documentation. A proud moment marking the completion of a safety-focused innovation.

Model Layout & Design – Features a protective outer frame, ergonomic seating area, and a side mounting bracket for secure installation, with a centrally positioned harness system for balanced restraint.

Model Labelling – Includes the “My Kingdom” branding with a crown symbol, with space for additional labels such as sensor zones, emergency indicators, and QR onboarding points.

Safety Features – Equipped with a 5‑point harness, rigid protective frame, and designated space for emergency stop mechanisms or sensor alerts to enhance child safety.

User‑Friendly – Designed for easy operation with visible buckles, adjustable straps, and smooth surfaces, allowing parents to secure and release the child quickly and comfortably.