Zara’s Status Report for 04/12/2025

This week I first worked with Jana on making the greenhouse water-resistant as we sprayed water-resistant sealant over it and put the components back in. We have tidied up the system and secured the lights and the water pump. I also got the 7-in-1 soil sensor working fully and is incorporated into the main function. There were a few issues in getting it working at the same time as the temperature sensor, however, I managed to resolve them by using different packages for the code. I have now incorporated all sensor data to be sent on the webapp and they are running constantly now to collect data. For the RPI camera, I have also laser-cut a mount for it so it can be stuck on the greenhouse and the angle of the camera may be adjustable depending on the plant inserted.

My progress is mostly on track, I will need to resolve the finalissues with the heater thisweek. I have also received the final water pump for the nutrients so I will set it up in the upcoming week. In terms of actuator code control, I will need to record the water flow rate so I can set up automated water pumping and nutrient pumping.

Zara’s Status Report for 03/29/2025

This week I made progress on getting the water pump actuator to work through the RPi, as well as the soil moisture sensor (HW080) to collect plant data. The actuator code for the heater works as well, though it overheats the wires and smokes so it becomes unsafe. Thus I have decided to not demo that and wait to retry with thicker wires for more safety in the future. I have researched more into the soil moisture, pH, and nutrients sensors, however, due to lack of documentation am still struggling to make it work so will be using the HW080 for the demo instead. We have also instilled all the current working components into our greenhouse so that it is together, and I have added an extra Arduino to the system to reduce the stress on the Raspberry Pi.

By next week, I hope to get the soil moisture, nutrients, pH sensor working as well as the heater without safety issues so that full data can be collected. I also want to start the control code with a pid so that the system will respond to ideal conditions.

Team Status Report for 03/29/2025

This week, our biggest effort went towards sufficiently preparing for the interim demos on Monday and Wednesday. We aimed to have 2-3 working sensors, at least one working actuator, a working camera stream, and plant identification, all communicating with the webapp somewhat. We came across many risks during the process, firstly for the amount of plant data we send there may not be enough space on the database to hold it, so we decided to reduce the frequency of data sent. Additionally, when trying to set up the heater, we found that when running the code, it tends to overheat and occasionally smoke, proving to be a fire hazard, so we aim in the future to try thicker wires better for this. Additionally, we aimed to have the soil moisture, pH, and nutrients sensor ready for the interim demo and ML data collection, however, due to lack of documentation, it has been difficult to set in time, so an easier sensor (HW080) is being used instead initially to just collect soil moisture data for now whilst the other one is being setup.

 

For the overall design, we have run into overheating issues in the Raspberry Pi, so we have decided to move the light sensor as well as the soil moisture sensor (HW080) to an Arduino to collect data and send that to the Raspberry Pi. As the LEDs we initially bought may not have been appropriate for rewiring through a relay, we have also decided to purchase a new one to prepare for it. 

 

Progress:

  • Working soil moisture, temperature, and humidity sensor data sent to webapp
  • Working water pump control through webapp
  • Working camera stream to the webapp
  • Mostly working plant identification 
  • Working plant health identification through webapp
  • Display temperature and humidity sensor data on webapp with charts
  • Some working code for mister actuator

 

Next Steps:

  • Get the heater actuator working
  • Get plant identification more accurate
  • Start training on collected sensor data
  • Get soil moisture, pH, and nutrient sensors working
  • Get mister working through actuator
  • Get LED strips working through actuator

 

Zara’s Status Report for 03/22/2025

This week, I made significant progress on the project by completing most of the web scraping for plant data. I successfully gathered essential information such as scientific name, light requirements, watering needs, temperature, and humidity levels. The only remaining task for this aspect is to obtain pH levels and more precise water level data from additional sources. Alongside this, I worked with Yuna to implement the transmission of temperature and humidity sensor data from the Raspberry Pi to the web application. I also tested and verified the functionality of the light sensor code, ensuring it is correctly reading and processing data.

The Raspberry Pi is now deployed on campus, where I noticed that it tends to overheat when multiple sensor inputs are running simultaneously. To address this issue, I have ordered a cooling fan to help maintain optimal performance. In terms of overall logic, I also finalized the control flow payloads that will be sent back and forth from the RPi to the Web app with Jana and Yuna.

My progress is mostly on schedule, though I have fallen a bit behind on starting actuators, as I wanted to prioritize the integration of webapp for sensor data before implementing turning on and off the heater. By next week I hope to complete the code for the soil pH and nutrients sensor as well as having pH levels scraped online. I want to finalize sending all sensor data to the webapp integration in time for the upcoming demo and also get started on actuator code for the heater.

Zara’s Status Report for 03/15/2025

This week, I worked on the ethics assignment to evaluate the ethical considerations related to our project. On the technical side, I continued developing the API code and discovered that the initial API we intended to use was no longer actively maintained, though some calls were still functional. Upon further investigation, I found the API’s database but determined that it lacked the necessary data for our project.

To address this, I implemented an alternative API to retrieve the required information. However, certain critical details, such as plant watering and lighting schedules, were locked behind a paywall. As a workaround, I explored web scraping as a potential solution and identified several websites with relevant plant data, though they cover a limited selection of houseplants.

My progress remains on schedule, and I am now shifting my focus to setting up the heater. By next week, I aim to finalize the heater’s control code and complete the web scraping implementation to gather the necessary plant data.

Team Status Report for 03/08/2025

No major changes were made to our system though we have decided to add a pid control system to our environment to control the actuators based on sensor data. 

Challenges & Mitigation:

  • Potential faulty sensors: If the sensors we have received are faulty we need to order backups which will increase our costs. We have managed to decrease costs in other areas to have more budget for potential backups. 
  • Not enough training data: An ongoing issue remains that we may not be able to collect enough plant data to sufficiently train the ML model, to combat this we have ordered the plants to start training. 

Progress:

  • Collected all the plants for training and testing, and started setting them up in different conditions for ML training
  • Finished setting up the temperature and humidity sensor, and started setting up the light sensor
  • Created a rough web application with all base pages
  • Labeled online datasets consistently for ML models

Next Steps:

  • Finish setting light and soil moisture, pH, and, nutrients sensor
  • Establish a training framework for the ML model
  • Implement web UI, and django channels with WebSockets
  • Integrate RaspberryPi with web app

A was written by Zara, B was written by Jana, C was written by Yuna. 

Part A: Our product addresses global factors by recognizing that plant care is a universal activity, with people worldwide facing different challenges in managing plants due to varying levels of expertise, time, and environmental conditions. This product bridges the gap for individuals who lack the time or knowledge to care for plants, offering a solution for growing herbs, fruits, vegetables, and flowers at home, regardless of experience. It is particularly valuable in remote areas or regions with limited access to plant care resources, providing an educational tool for users at all skill levels. Additionally, its remote monitoring capabilities support plant care in diverse global settings, making it a versatile solution for anyone looking to grow plants efficiently, no matter where they are located.

Part B: In many cultures, plants hold symbolic and spiritual significance. Our system offers personalized plant care recommendations that meet the specific needs of plants that hold cultural significance, such as herbs, flowers, and medicinal plants. The system is designed to adapt to a wide range of growing conditions, ensuring that users from diverse cultural backgrounds, regardless of level of expertise or traditions, can effectively use the technology. By providing a simple and intuitive way to manage plant health, users can stay connected to the plants that are important to them, while also benefiting from automation and helpful insights that make plant care easier.

Part C: Our product solution addresses environmental challenges by allowing optimization of resource consumption for plant cultivation in home settings. The greenhouse system reduces energy use and water waste through precise irrigation that only delivers the water and nutrient amount that is needed for the plant. The system detects the plant conditions and water the appropriate amount rather than merely watering based on the typical watering schedules – this is particularly valuable in regions that are facing water scarcity. This plant condition detection also helps prevent overfertilization that can lead to soil degradation. Furthermore, our product solution allows easy plant cultivation in limited spaces, which improves air quality and reduces the carbon emissions caused by transporting commercial produce.

Zara’s Status Report for 03/08/2025

This week, I helped work on the design status report, which has helped further solidify our project plans. I focused on reworking the system architecture, specifically the flow chart diagram, to incorporate the new decision to use a PID controller for managing the system’s environment. Additionally, I updated the system implementation plan, bill of materials, and prepared a summary to align our project’s direction moving forward. On the sensor front, I conducted tests on various temperature and humidity sensors to identify the most accurate one, replacing the initially tested model. I also began implementing the light sensor into our system. For the plant API call, I am still in the process of finalizing the code to ensure smooth integration and functionality.

In terms of schedule, I am mostly on track; however, I have encountered a delay in implementing the heater. This is due to shipping issues, as the heater has yet to arrive, which is preventing me from progressing as planned

Looking ahead, my deliverables for next week include completing the implementation of the soil nutrients, pH, and moisture sensors, as well as finalizing the light sensor integration. If the heater arrives as expected, I aim to complete its implementation as well.

Zara’s Status Report for 02/22/2025

This week, I focused on setting up the Raspberry Pi at home and configuring it for our project. I successfully set up a Git repository for the team so we can track our code and collaborate efficiently. I also wrote initial code to collect temperature and humidity sensor data. The temperature readings appeared accurate, but the humidity values seemed off. To investigate further, I plan to rerun tests and, if the issue persists, compare results with backup sensors to determine whether the problem is with the sensor itself or the way the data is being processed. In addition to working on the sensor data, I also started implementing the Plant API data retrieval code, though I haven’t finished it yet. Here is an image of the sensor output data:

As a team, we received most of our components and assembled the greenhouse, ensuring that all parts fit together correctly. We also finished ordering the remaining components, including the plants, so we can begin testing as soon as they arrive with the sensors and start collecting training data for the ML models. My progress is currently on schedule since I have been able to start testing the sensors, though I still need to complete the Plant API integration this week.

Next week, I plan to set up and test the remaining sensors to ensure they are providing accurate readings. I also need to configure the Raspberry Pi to connect to the school’s Wi-Fi so that I can work on it remotely while on campus. Additionally, I aim to complete the integration of the Plant API so we can start using the data in our system.

Zara’s Status Report for 02/15/2025

This week, I focused on ordering all the necessary parts for our project and ensuring that the components we selected are fully compatible with our Raspberry Pi 5. I spent time carefully planning how the sensors and actuators will connect to the Raspberry Pi on the pinout, including how they will be powered and controlled. Additionally, I researched various water pump systems to determine the best way to integrate one into our design.

With the upcoming design presentation, I also worked closely with my team to refine our slides. I finalized the block diagram to visually present how the system components will connect and interact. To address previous confusion about the role of our machine learning model, I created a detailed flow diagram to clearly outline its function and integration within our system. My goal was to ensure that our audience would fully understand how our data inputs contribute to plant health classification.

Currently, we are on schedule, and our progress aligns with our planned timeline. However, I am slightly concerned that some of our ordered components may take longer than expected to arrive, which could delay the integration of certain parts. Fortunately, none of these delays seem significant enough to disrupt our overall schedule. Another potential issue is the soil nutrient and pH sensor we selected, as it has limited reviews and its reliability is uncertain. Due to budget constraints, we opted for a more affordable sensor, but if testing reveals any issues, we will order an alternative model as soon as possible.

By next week, I hope to have the temperature and humidity sensor set up and fully integrated with the RPi 5 to establish a working model for collecting environmental data. Additionally, I plan to begin testing other hardware components as they arrive to ensure a smooth transition into the next phase of our project.

Team Status Report for 02/08/2025

One of the most significant risks to our project is ensuring that we have enough time to train a machine learning model on sensor input data. If we do not set up our data collection system early, we may not have sufficient training data, which could result in an underdeveloped model that does not perform as expected. To mitigate this risk, our approach is to prioritize setting up the fundamental hardware and software components as soon as possible. This includes setting up the Raspberry Pi 5 with an initial sensor and the camera module, establishing a data collection and storage system to begin logging sensor and camera input, and implementing the initial machine learning pipeline so we can start training models early in the development process. By doing this, we ensure that data collection and ML training can happen concurrently with other parts of the project, minimizing delays.

There were no major changes to the design of the system. However, we made one key adjustment by switching from the Raspberry Pi 4B to the Raspberry Pi 5. This decision was made because the Raspberry Pi 5 offers better performance, which will help with machine learning training and real-time processing. Additionally, we were able to secure one for free from the ECE inventory, reducing project costs. This change does not introduce additional expenses but improves our system’s capability and allows us to work with newer hardware.

At this point, there are no major schedule updates. Our current focus is on ordering components and beginning initial setup. Once our parts arrive, we will start hardware integration and software development.

So far, we have finalized our project proposal and user case requirements, researched communication protocols for sensor and camera data transfer, ordered our first Raspberry Pi 5 unit, and finalized the initial list of parts to order next week. Our next steps include ordering all remaining parts and beginning hardware setup, setting up the Raspberry Pi 5 with essential sensors and the camera, and establishing the data collection and machine learning training pipeline. We will include photos of our hardware setup in future updates as we begin assembling components.