Inspiration
The market for electric vehicles is one of the fastest growing global market segments, with commercial and personal viability of using them growing rapidly. However, despite significant investments in infrastructure and improving technologies underpinning electric vehicles, drivers both new and old remain hesitant adopt this new drivetrain full-time due to some looming questions whenever they hit the road. Some of these questions include: Where should I stop and charge to reach my destination in the least time possible? Will I have enough range to reach a charger based on how I’m currently driving? Will the charger(s) be working when I get to it? Are there enough free charging handles at the charger / are the chargers full? If the chargers are full and there is a line, how many people are in front of me? Is it worthwhile to leave? Is my vehicle ready to accept a charge at its maximum speed? Is the battery below a certain threshold to maximize charging efficiency? Is the battery temperature between 70f and 80f? Is the charger’s rated speed above the rated speed of the vehicle?
What it does
Our project is a browser-based web application that captures vehicle diagnostic data from commonly available hardware devices. We track key metrics about the vehicle and display this information in a seamless frontend while tracking the vehicles efficiency and how much CO2 it saves among other useful data points. Most significantly, we also predict the optimal route for a vehicle to take from one destination to another to ensure it finds chargers at the optimal times.
How we built it
We used React for the frontend and Flask for the backend.
Challenges we ran into
We had issues working with APIs to integrate the data. The geopy library was very slow. Endpoints were also quite messy to work with. As our software is composed of multiple intricate parts it was challenging to do integrations in a production environment.
Accomplishments that we're proud of
We are proud of building a fully integrated app starting from the hardware to the frontend. We managed to successfully work as a team despite having very different backgrounds.
What we learned
We learned about many new technologies (Daisy UI, Tailwind, tsx) that we had not used before. Also getting a group of people to work consistently was interesting to learn.
What's next for EVEE
We plan on working more directly with the hardware used. We also plan to integrate to integrate advanced and quality of life features that we were not able to get to within this hackathon.
Log in or sign up for Devpost to join the conversation.