Mathieu Moran
555af3694e
- All 10 FEATs now in strict numerical order under single Feature ideas section - Added summary table (ID, Status, Created, Title, Phase) for quick scanning - Created dates sourced from git history (ef3a951throughbc29a01) - Removed orphan Ideas that landed section (FEAT-06/07 merged into main flow)
187 lines
11 KiB
Markdown
187 lines
11 KiB
Markdown
# yaris-obd Feature Requests
|
|
|
|
Ideas and requests for **new features** (distinct from bugs, which belong in `BUGS.md`, and the
|
|
phase-by-phase implementation history in `PLAN.md`). Use this file to record anything that should
|
|
be built eventually but isn't an active roadmap phase yet. When a feature gets picked up, create a
|
|
dedicated PLAN.md phase (or fold it into the relevant existing work) and mark it here.
|
|
|
|
## How to use this file
|
|
|
|
- **One `## FEAT-XX` section per idea.** Keep numbering sequential.
|
|
- **Status field**: `IDEA` (brainstormed, not planned) → `PLANNED` (has an assigned phase) →
|
|
`IN PROGRESS` → `SHIPPED` (deployed + verified) or `WONTFIX`/`SUPERSEDED` as appropriate.
|
|
- **Relate to roadmap**: when a feature lands in a phase, note the phase here and drop a link back
|
|
here from PLAN.md so the two stay in sync.
|
|
- **Keep each entry small and one-idea-per-entry** so it's easy to pick up and scope.
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
| ID | Status | Created | Title | Phase |
|
|
|----|--------|---------|-------|-------|
|
|
| FEAT-01 | `IDEA` | 2026-08-10 | Parallel/concurrent chunked dashcam uploads | Phase 27 |
|
|
| FEAT-02 | `IDEA` | 2026-08-10 | QR / claim-code device pairing flow | Phase 27 |
|
|
| FEAT-03 | `SHIPPED` | 2026-08-10 | Manual start odometer fallback | Phase 27 |
|
|
| FEAT-04 | `IDEA` | 2026-08-11 | Replace SIM868 2G with 4G LTE modem | Phase 27 |
|
|
| FEAT-05 | `SHIPPED` | 2026-08-11 | DTC history synced to remote server | Phase 27 |
|
|
| FEAT-06 | `SHIPPED` | 2026-08-11 | Trip ID column in history table | Phase 26 |
|
|
| FEAT-07 | `SHIPPED` | 2026-08-11 | Phone-hotspot auto-connect docs | Phase 22 |
|
|
| FEAT-08 | `SHIPPED` | 2026-08-11 | Predictable IP on phone hotspot | Phase 22 |
|
|
| FEAT-09 | `WONTFIX` | 2026-08-11 | mDNS (yaris.local) on phone hotspot | — |
|
|
| FEAT-10 | `IDEA` | 2026-08-12 | Home Assistant integration | unassigned |
|
|
|
|
---
|
|
|
|
## Feature ideas
|
|
|
|
### FEAT-01 — Parallel/concurrent chunked dashcam uploads
|
|
- **Status**: `IDEA`
|
|
- **Area**: `modules/app_upload.py` (Pi upload client)
|
|
- **Phase**: Phase 27
|
|
- **Requested**: noted in Phase 10 of PLAN.md as a possible future optimization; not yet requested
|
|
explicitly by the owner.
|
|
- **Idea**: upload multiple dashcam chunks (and/or multiple files) concurrently instead of the
|
|
current strictly sequential one-chunk-then-one-file at a time. Would speed up the multi-hour
|
|
full-backlog drain of a large local dashcam archive, at the cost of more complexity (bounded
|
|
concurrency, per-file state, failure handling for the individual concurrent workers).
|
|
- **Outstanding considerations**: memory budget on the Pi (~900MB, no swap — must stay streaming),
|
|
and whether the sequential pace is actually annoying enough in practice to justify the added
|
|
complexity.
|
|
|
|
### FEAT-02 — QR / claim-code device pairing flow
|
|
- **Status**: `IDEA`
|
|
- **Area**: server device provisioning + Pi credential setup (Phase 25.5c)
|
|
- **Phase**: Phase 27
|
|
- **Requested**: discussed in Phase 25.5c as a possible follow-up to the manual copy/paste API-key
|
|
provisioning.
|
|
- **Idea**: zero-manual-copy provisioning of `YARIS_SERVER_URL` / `YARIS_DEVICE_NAME` /
|
|
`YARIS_API_KEY` onto the Pi — e.g. the portal shows a short-lived claim code / QR that the Pi
|
|
app (or owner) enters/scans once to adopt the device, instead of typing credentials by hand.
|
|
- **Outstanding considerations**: bigger scope than the current copy/paste flow; ship copy/paste
|
|
first, add pairing only if provisioning still feels annoying.
|
|
|
|
### FEAT-03 — Manual start odometer fallback when OBD odometer is unavailable
|
|
- **Status**: `SHIPPED` 2026-08-11
|
|
- **Area**: Settings page, Dashboard, `modules/app_settings.py`, `modules/app_sql.py`
|
|
- **Phase**: Phase 27
|
|
- **What**: Settings page now has an "Odometer baseline (km)" field. The app stores
|
|
this value and computes `odometer_km = baseline + cumulative trip distance`. Dashboard
|
|
shows "(manual)" label when using baseline. When baseline is 0, falls back to live
|
|
OBD reading (the original behavior). Also appears in `/api/stats` response.
|
|
|
|
### FEAT-04 — Replace SIM868 2G GSM hat with 4G LTE modem (Huawei E3372h-153)
|
|
- **Status**: `IDEA`
|
|
- **Area**: modems / uplink (Pi `modules/app_cellular.py`, `modules/app_gps.py`, uplink
|
|
switching) — replaces the current SIM868 GSM/GNSS HAT + cellular fallback path
|
|
- **Phase**: Phase 27
|
|
- **Requested**: owner — just purchased a Huawei **E3372h-153 4G LTE Modem**. The 2G/3G-only
|
|
SIM868 hat will not work in Canada (2G networks are decommissioned), so the plan is to make the
|
|
4G modem the working cellular uplink instead.
|
|
- **Idea**: integrate the Huawei E3372h-153 as the primary cellular data uplink, replacing reliance
|
|
on the SIM868's GSM (AT+HTTP) path. The E3372h-153 is a USB "stick" modem — likely supported via
|
|
Realtek / cdc_ether / usb-storage based drivers and exposes a dial-up or LTE dongle interface the
|
|
Pi can use for connectivity (e.g. via NetworkManager / ModemManager, or a static APN config).
|
|
- **Outstanding considerations**:
|
|
- Determine the E3372h-153's local mode vs stick/dial mode and the correct Linux driver/interface
|
|
(hierarchical USB mode switching may be needed; it's the "153" variant which may use the RNDIS /
|
|
ECM / CDC-NCM profile).
|
|
- Whether to run it as the *primary* uplink or just another option in the existing phone-hotspot /
|
|
home-wifi / local-AP priority chain.
|
|
- What happens to the SIM868 — keep it purely for its **GPS/GNSS** role (it's the PWRKEY-toggled
|
|
GNSS receiver on `/dev/serial0`) while dropping its **2G GSM** cellular path, vs removing it
|
|
entirely.
|
|
- The SIM868's `app_gps.py` GNSS positioning must keep working (it's the car's GPS source) even if
|
|
the 2G-modem half is retired — separate the two concerns.
|
|
- **Keep this feature as-is (2G/GSM fallback) for countries where 2G/3G still works** — don't
|
|
remove the existing cellular fallback code; gate it so the 2G path remains available there.
|
|
- LTE SIM plan/APN specifics for Canadian carriers (Rogers/Bell/Telus) and whether the modem can
|
|
run the Pi's hotspot/SSID the same way `app_network.py` currently does.
|
|
|
|
### FEAT-05 — DTC history synced to remote server with code descriptions
|
|
- **Status**: `SHIPPED` 2026-08-12
|
|
- **Area**: `modules/app_upload.py`, `server/sql/migrate_phase27_dtc.sql`, `server/modules/db.py`, `server/app.py`, `server/templates/dtc.html`
|
|
- **Phase**: Phase 27
|
|
- **What**: Pi pushes current DTC snapshot to server via `POST /api/v1/dtc/batch`.
|
|
Server diffs against stored state — new codes inserted, existing updated, missing
|
|
codes auto-cleared. Portal has a new `/dtc` page showing code, description, MIL
|
|
state, active/cleared status, first/last seen timestamps, and manual delete.
|
|
Upload skips when OBD disconnected (avoids clearing server DTCs on Pi reboot).
|
|
Snapshot is hash-compared to avoid redundant uploads.
|
|
|
|
### FEAT-06 — Trip ID column in history table
|
|
- **Status**: `SHIPPED` 2026-08-11
|
|
- **Area**: `static/js/history.js`, `templates/history.html`, `server/templates/history.html`
|
|
- **Phase**: Phase 26
|
|
- **What**: Narrow `#ID` column on server history (hidden on Pi via `data-show-id`).
|
|
Checkbox column and batch-delete restored on server only.
|
|
|
|
### FEAT-07 — Phone-hotspot auto-connect documentation
|
|
- **Status**: `SHIPPED` 2026-08-11 (already implemented in Phase 22, documented here)
|
|
- **Area**: `deploy/yaris_uplink.py`, Settings page, netwatch timer
|
|
- **What**: The Pi auto-connects to a saved phone hotspot on wlan1 within ~60s of it
|
|
appearing in range, and falls back to home-wifi when it disappears. The wlan0 AP
|
|
stays up regardless. Test flow: Settings → save hotspot name + password → "Wait for
|
|
hotspot" → enable phone hotspot → verify mode changes to "Phone hotspot".
|
|
|
|
### FEAT-08 — Predictable IP on phone hotspot (DHCP client-id)
|
|
- **Status**: `SHIPPED` 2026-08-11 (Phase 22)
|
|
- **Area**: `deploy/yaris_uplink.py`, phone-hotspot NM profile
|
|
- **What**: `dhcp-client-id=yaris-obd` in the NM keyfile gives the Pi a consistent DHCP
|
|
lease. The "Last phone IP" link on Settings shows the current address. Pixel testing
|
|
confirmed same IP across disconnects.
|
|
|
|
### FEAT-09 — mDNS (yaris.local) on phone hotspot
|
|
- **Status**: `WONTFIX` 2026-08-12 — hardware/OS limitation
|
|
- **Area**: Avahi, phone-hotspot NM profile
|
|
- **What**: Phone hotspot hosts (Android, iOS) don't relay multicast DNS. Avahi publishes
|
|
correctly on wlan0 AP and home WiFi. Settings "Last phone IP" link is the workaround.
|
|
Cannot be fixed in software — this is a phone-OS limitation.
|
|
|
|
### FEAT-10 — Home Assistant integration
|
|
- **Status**: `IDEA`
|
|
- **Area**: `modules/app_homeassistant.py` (new), `server/` (API endpoints), Pi-side MQTT/HTTP
|
|
- **Phase**: unassigned
|
|
- **Requested**: owner — wants the car's live telemetry and status visible in Home Assistant
|
|
dashboards alongside other smart-home devices.
|
|
- **Idea**: expose yaris-obd data (speed, RPM, coolant temp, fuel level, GPS position, DTC
|
|
alerts, ignition state, trip stats, cellular signal, etc.) as Home Assistant entities so
|
|
they appear automatically via MQTT discovery or a REST-based integration. The Pi already
|
|
collects all this data — the integration just needs to publish it in a format Home
|
|
Assistant can consume.
|
|
- **Possible approaches** (to scope later):
|
|
- **MQTT discovery**: Pi publishes to a local MQTT broker (e.g. Mosquitto on the same
|
|
network or on the HA host) with Home Assistant's auto-discovery topic schema
|
|
(`homeassistant/sensor/yaris/.../config`). HA picks up the entities automatically with
|
|
zero manual YAML. Works well on home WiFi; not available on phone hotspot or cellular.
|
|
- **REST API integration**: a custom Home Assistant integration (HACS or core) that polls
|
|
the Pi's `/api/stats` (or a new `/api/v1/ha/state` endpoint on the server) periodically.
|
|
Works from anywhere the server is reachable, including remotely via the self-hosted
|
|
server.
|
|
- **Hybrid**: MQTT when on home WiFi (real-time, low-latency), REST via server as a
|
|
fallback for remote/cellular visibility.
|
|
- **Entity ideas**:
|
|
- `sensor.yaris_speed` (km/h), `sensor.yaris_rpm`, `sensor.yaris_coolant_temp` (°C)
|
|
- `sensor.yaris_fuel_level` (%), `sensor.yaris_odometer` (km)
|
|
- `device_tracker.yaris_location` (lat/lon from GPS)
|
|
- `binary_sensor.yaris_ignition` (on/off), `binary_sensor.yaris_mil` (check engine light)
|
|
- `sensor.yaris_dtc_count`, `binary_sensor.yaris_dtc_active` (any active DTCs)
|
|
- `sensor.yaris_cellular_signal` (dBm or %), `sensor.yaris_uplink_mode` (home/phone/cell)
|
|
- `sensor.yaris_trip_distance`, `sensor.yaris_trip_duration` (current trip)
|
|
- `device_tracker.yaris_phone_hotspot` (when connected via phone hotspot — confirms car
|
|
is near the phone)
|
|
- **Outstanding considerations**:
|
|
- MQTT path only works when the Pi is on the same LAN as Home Assistant (home WiFi) — not
|
|
in the car on its own AP or cellular. This may be fine for "car is home" use cases
|
|
(charging status, maintenance reminders, trip summaries after returning).
|
|
- REST path via the self-hosted server works remotely but adds latency and depends on the
|
|
server being up.
|
|
- Decide whether to publish directly from the Pi or from the server (server already has
|
|
post-upload trip data; Pi has real-time data the server doesn't).
|
|
- Home Assistant OS vs container vs core install — MQTT discovery is universal, REST
|
|
would need a custom component or HACS add-on.
|
|
- Keep the integration opt-in and lightweight — don't add MQTT dependencies to the core
|
|
app.py startup unless the user explicitly configures it.
|
|
|
|
|