Mathieu Moran
47993a876f
fix: diagnose.sh DB checks — wrong path, column, and tool
...
- DB lives under db/sql/<account>_<car>.db, not the repo root (was -maxdepth 1)
- Pick the most recently modified DB (active account) instead of the first
found, which was the stale TestUser_SubaruWRX.db
- Query UPLOADED=0 instead of sent=0 (column was renamed long ago)
- Use the venv Python's sqlite3 for queries — the sqlite3 CLI isn't installed
on the Pi, so integrity/row-count checks were silently failing
2026-08-15 14:22:35 -04:00
Mathieu Moran
5170dbce62
chore: update diagnose.sh for dual-T3U WiFi and Android app
...
- Network section now checks wlan1 (in-car AP, 10.42.0.1), wlan2 (uplink),
and reports wlan0 as retired fallback (was: first-wlan guess)
- Header + manual commands reflect current layout: Android companion app,
remote server at yaris.ceaf.dev, AP/uplink nmcli profiles
2026-08-15 14:16:10 -04:00
Mathieu Moran and Copilot
437434b972
feat: add scripts/diagnose.sh — system diagnostic & recovery tool
...
Read-only health check (no args) or auto-fix mode (--fix):
- Service: active state, crash loop detection, recent log
- Hardware: OBD USB adapter (/dev/ttyUSBx), SIM868 UART (/dev/serial0),
dashcam USB mount, permissions
- Network: hotspot IP, web UI reachability, internet, upload server
- Storage: disk usage, SQLite integrity check, row counts, upload backlog,
log file size
- OBD status: parsed from log (last connect/disconnect/speed/errors)
- Python env: venv present, key packages importable
- Pi health: throttling flags decoded, CPU temp, free memory
- Manual recovery command cheatsheet printed at the end
Exit code = number of critical issues found (0 = healthy).
Co-authored-by: Copilot <[email protected] >
2026-08-10 05:31:03 -04:00