Inspiration

Many people with deaf and hearing disabilities face challenges in perceiving critical environmental sounds such as alarms, doorbells, and other important sounds. This gap in awareness can impact safety and independence. This is inspired by the need for accessible needs around the world. We want to create a wearable device that detects important sounds and translates them into LED visuals.

What it does

Our project is a wearable device and web-based dashboard designed to assist deaf and hard-of-hearing individuals by detecting critical sounds such as fire alarms and door knocks. The device captures sound frequencies using a sensor and translates them into LED visual alerts and vibrations, ensuring the user is immediately aware of important auditory cues. Simultaneously, the alerts are sent to a real-time dashboard built with Streamlit and Flask, allowing family members to monitor emergency events remotely. The system also maintains an event history log, tracking past alerts for safety insights. Designed for affordability, accessibility, and ease of use, this project bridges the communication gap between the hearing and non-hearing world, empowering individuals with greater independence and security.

How we built it

We decided to use the streamlit.io framework, which makes website building so much easier in Python, we focused on the UI and some backend utilities where we would read updated status from a json file. We also needed an end-point to receive requests of emergencies / fires / knocks from the arduino. We used C++ to setup the arduino, we used the Adafruit_SSD1306 library for our display whose role was to print whether there is an emergency or not to the screen. We also utilized a sound & vibrator to let the user of the watch know the type of emergency occurring, in this case either a knock, fire or a default state (no emergencies).

Challenges we ran into

Throughout the development of our accessibility device, we encountered numerous technical and logistical challenges. Initially, we planned to 3D print components for the device, but die to high demand, we were unable to secure a printer in time. This forced us to rethink our approach and find alternative ways to construct the physical casing. On the hardware side, we constantly had to adjust our choice of components, as some parts were unavailable or incompatible. Wiring issues on the breadboard caused repeated setbacks. Our LED and buzzer failed to work at one point, and we spent significant time troubleshooting faulty connections. Additionally, we encountered several defective components, which led to further delays and the need for quick improvisation, especially when we lacked essential wires and cables. Beyond technical issues, we also faced challenges in teamwork. One of our team members abandoned the project within less than an hour, leaving the rest of us to pick up the slack. Despite these difficulties, we adapted, problem solved on the spot, and pushed forward to complete the project. These obstacles ultimately strengthened our ability to work under pressure and develop creative solutions in real time.

Accomplishments that we're proud of

We're proud of the fact that even tho we came across MANY challenges (for example a significant member leaving the group without notifying us), we were able to recover, take upon new skills such as learning streamlit, the use of arduino with other hardware components and much more, which displays the resilience of our team members and passion to get this done the right way.

What we learned

Through this project, we learned the importance of adaptability and problem-solving when working with hardware and team dynamics. When our 3D printing plans fell through, we had to quickly pivot and find alternative solutions. Troubleshooting the breadboard issues and dealing with faculty components taught us patience and the importance of systematically diagnosing problems rather than rushing to replace parts. Furthermore, we also realized how crucial it is to work with available resources. The lac of wires forces us to be creative and find workarounds, proving that constraints can drive innovation. Additionally, experiencing a teammate abandoning the project underscored the importance of accountability and teamwork. It reminded us that strong collaboration is just as vital as technical skills in completing a project successfully. Most importantly, we gained a deeper appreciation for accessibility-focused design. Seeing firsthand the challenges of developing a reliable, cost-effective solution reinforces our commitment to creating technology that truly benefits those who need it.

What's next for Hear-O Squad

Moving forward, we plan to refine and improve our accessibility device to make it ore reliable, efficient, and user-friendly. Our next steps include the following: Optimizing hardware & design Since we face issues with faulty components and wiring, we will work on sourcing higher-quality, tested components and refining the circuit design for better durability and efficiency. Additionally, we will revisit out 3D printing plans to create a more polished, wearable prototype Enhancing Functionality We aim to improve sound detection accuracy by experimenting with different sensors and refining the algorithm to differentiate between various important sounds more effectively Usability Testing Conducting real-world testing with potential users, including individuals with hearing impairments, will help us gather valuable feedback to ensure the device meets their needs Seeking Funding & Collaboration To bring this project to a wider audience, we place to explore potential grans, sponsorships or partnerships with organizations focused on accessibility and assistive technology By focusing on these areas, we hope to take our prototype from a proof-of-concept to a fully functional, affordable device that can make a real difference in people's lives.

Built With

Share this project:

Updates