overland-controller/docs/roadmap.md

Roadmap

Phase 1: Solid Local Cargo Controller

• Reliable relay control
• Reliable DS18B20 temps
• Reliable JBD/Xiaoxiang BMS BLE
• WPA2 AP mode
• Stable WebUI
• Stable HTTP API
• Clear status/config/control model

Phase 2: Waveshare ESP32-S3 Dashboard

• LVGL project scaffold
• WiFi client to Cargo ESP32 AP
• Poll /status
• Display battery, relays, temps, and alarms
• Send relay commands
• Handle offline/stale/failed-command states

UI direction:

• Dark theme
• Large readable text
• Circular SOC gauge
• Card-based layout
• Smooth subtle animations
• No stock LVGL demo look

Phase 3: Vehicle Data

• Connect Waveshare CAN to OBD-II CAN-H/CAN-L
• Keep CAN termination disabled
• Read coolant temp via PID 0105
• Read RPM via PID 010C
• Read vehicle speed via PID 010D

Phase 4: Transmission Temperature

• Install dedicated sender
• Read through exposed ADC or ADS1115 over I2C
• Convert resistance to temp with lookup interpolation
• Add alert thresholds

Phase 5: Future Home Server

• Cargo ESP32 outbound connection
• Remote read-only dashboard first
• Optional commands later
• HTTPS reverse proxy/PWA
• Possible MQTT/WebSocket bridge
• Optional Grafana/Home Assistant/InflDB

Phase 6: Optional Enhancements

• microSD logging
• GPS
• OTA updates
• Dashboard alert sounds
• More vehicle PIDs
• Historical charts

AP Security, OLED Setup, and Dashboard Pairing

Phase 1 — Cargo AP security

• Require WPA2 on the Cargo ESP32 AP.
• Generate a unique AP password on first boot.
• Store AP SSID/password in Preferences.
• Add /api/v1/config/ap for AP configuration.
• Add AP auth/SSID metadata to status responses.
• Do not expose AP password in API responses.

Phase 2 — Cargo OLED setup display

• Add 128x64 SSD1306 OLED support on the Cargo ESP32.
• Show AP SSID/password/IP during first boot and setup mode.
• Show critical operational state during normal operation:
  • SOC
  • voltage/current
  • relay state
  • WiFi/IP
  • alarms
• Add setup/status button:
  • short press cycles pages
  • long press shows AP credentials
  • extended hold enters recovery/reset mode

Phase 3 — Dashboard credential migration

• Dashboard ESP32-S3 connects as a client to the Cargo ESP AP.
• Cargo ESP remains the network/configuration authority.
• When AP credentials are changed from the phone WebUI, Cargo stages the new credentials.
• Dashboard fetches and saves pending credentials before Cargo restarts AP.
• Cargo applies the new AP settings.
• Dashboard reconnects automatically.
• Temporary dashboard setup AP is fallback/recovery only.

Phase 4 — User-friendly setup polish

• Add QR code display for joining Cargo AP.
• Add dashboard settings UI.
• Add LVGL on-screen keyboard only after core dashboard functionality is stable.