Mathieu MoranandCopilot
0b729adb28
Reordered/renumbered the roadmap based on dependency analysis: - Phase 12 (remove relay) stays first - pure cleanup, no deps. - New Phase 13: power-loss resilience + hardware watchdog - OS-level, independent, should land before the Pi lives in the car full-time (cars cut power abruptly at every key-off, a real SD-corruption risk nothing in the project currently addresses). - New Phase 14: UI design-system foundation - pulls forward a small slice of the old end-of-roadmap redesign (shared layout + reusable list/table component) so the dashcam/video browsers, trip history, and settings pages are all built on it once instead of being built in the old template and then rebuilt during the redesign later. - Phases 15/16 (dashcam + local video browsers) now explicitly build on Phase 14's foundation. Folded two more QOL ideas directly into Phase 16: ffmpeg thumbnails per video, and an optional upload-confirmed local retention/auto-cleanup policy. - Phase 17 (OBD hardening) explicitly marked independent/parallel- frins to other phases - backend-only work, no UI dependency. - New Phase 18: trip history + map replay (trips table + GPS-gap boundary detection + list/replay UI reusing the offline Leaflet map). - New Phase 19: Pi health monitoring card (CPU temp/disk/uptime/RAM). - New Phase 20: alerts/notifications via a simple outbound webhook (ntfy.sh/Telegram) for DTC-on, storage full, backlog growing, overheating, lost GPS fix. - New Phase 21: consolidated Settings page (upload toggle, cellular APN, retention policy, alert config) - reduces routine SSH-editing. - Phase 22: renamed 'Finish web UI redesign' - now scoped as the remaining cleanup after Phase 14's foundation + all functional phases land, rather than one big redesign at the very end. - Phase 23: native Android app, unchanged content, still last/low priority per explicit user instruction. Updated the session's todo tracking table to match the new phase IDs/order and added todo_deps reflecting the same dependency chain. Co-authored-by: Copilot <[email protected]>
yaris-obd 🚗📡
A Raspberry Pi 3-based OBD-II + GPS tracker for my 2013 Toyota Yaris — reads live vehicle data over USB, tracks position with a SIM868 GNSS/GSM HAT, and serves it all from a local web UI you can pull up on your phone by connecting to the car's own WiFi hotspot. Fully usable offline: no internet needed in the car, offline map tiles included. Also handles pulling dashcam footage off a USB dashcam for local/remote backup.
|
rené lévesque bangers i have a dream |
Screenshot
Features
- 📊 Live OBD-II data (speed, RPM, DTC codes) over a cheap USB ELM327-compatible adapter
- 🛰️ Real GPS tracking via a Waveshare SIM868 GNSS/GSM/Bluetooth HAT, plotted live on an offline Leaflet map (pre-cached map tiles — no internet needed in the car)
- 📶 Self-hosted WiFi hotspot so you can load the web UI on your phone from inside the car,
with automatic fallback to your home WiFi when in range (
http://yaris.local— no port number) - 🎥 Dashcam file retrieval — detects a USB dashcam automatically (any brand/folder layout, no hardcoded device path), copies its footage locally, verified against real hardware
- ☁️ Remote upload — a self-hosted server (Flask + Postgres,
server/) receives trip/GPS logs and dashcam footage over the internet (via Cloudflare Tunnel or a plain port-forward). Dashcam videos upload in resumable 40MB chunks (works around tunnel body-size limits and keeps the Pi's memory footprint flat regardless of file size); a UI toggle can pause dashcam uploads independently while trip logs keep syncing - 📱 Phone-relay upload — if the Pi's own WiFi is slow/congested, open
/dashon your phone to download pending dashcam files locally and re-upload them straight to the remote server using the phone's own network instead, automatically pausing the Pi's own upload meanwhile - 🗄️ Local SQLite trip logging, retried/synced to the remote server with automatic backoff
- 🔌 Runs fully headless as a
systemdservice, autostarting on boot
Hardware
| Part | Notes |
|---|---|
| Raspberry Pi 3 Model B | Web UI host + hotspot |
| Waveshare SIM868 HAT | GNSS (GPS) + GSM/GPRS, unused Bluetooth |
| USB OBD-II adapter | PL2303-based, ELM327-compatible (originally Bluetooth, switched to USB) |
| USB dashcam | Any brand — detected as generic USB mass storage |
| 2013 Toyota Yaris | The patient |
See PLAN.md for full hardware bring-up notes (SIM868 jumper/UART setup, antenna gotchas, etc.) and the detailed project history.
Getting started
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
python3 app.py
The app serves on http://<host>:5000. On the Pi it also runs as a systemd service
(see deploy/) and is reachable with no port number at http://yaris.local once the
mDNS + port-redirect setup described in PLAN.md is installed.
For the remote server (receives trip logs + dashcam uploads), see server/README.md.
Project status
This project was revived after a couple of years on the shelf. All 11 planned phases are done and the full pipeline — OBD/GPS logging, offline web UI, WiFi hotspot, dashcam retrieval, remote upload, and phone-relay upload — has been verified against real hardware end-to-end, including a full real dashcam import and upload run. Only the SIM868 cellular fallback (for uploading while out of WiFi range) and the phone-relay feature's real-phone/live-network test remain untested. Full phase-by-phase history in PLAN.md.