Update roadmap networking and dashboard architecture

2026-06-04 12:46:35 -06:00
parent d8f756ee53
commit e3efdc581f
3 changed files with 355 additions and 0 deletions
@@ -251,3 +251,156 @@ Potential future features:
 - Bluetooth sensor support
 - Mobile web dashboard
 - Plugin-style integrations
+
+---
+
+## Networking Roadmap
+
+### Current
+
+The ESP32 currently operates as a local access point.
+
+Default local access:
+
+    http://192.168.4.1
+
+This provides a reliable recovery/setup path even when no other WiFi network is available.
+
+### Planned: AP + STA Mode
+
+The ESP32 should support AP and STA mode at the same time.
+
+Access Point mode:
+
+    Overland-Controller
+    192.168.4.1
+
+Station mode:
+
+    Connects to a configured WiFi network such as Starlink, home WiFi, or shop WiFi.
+
+The AP should remain enabled even when STA mode is connected.
+
+Reason:
+
+- Always available recovery path
+- Easier setup
+- Less risk of locking yourself out
+- Useful when Starlink/home WiFi is unavailable
+
+### Planned: Multiple Saved WiFi Networks
+
+The controller should eventually support multiple saved WiFi profiles.
+
+Example priority order:
+
+    1. Starlink
+    2. Home WiFi
+    3. Shop WiFi
+
+Expected boot behavior:
+
+    Start AP
+    Try Starlink
+    If Starlink fails, try Home WiFi
+    If Home WiFi fails, try Shop WiFi
+    If all fail, remain AP-only
+
+The ESP32 only connects to one STA network at a time, but it can remember and try multiple networks.
+
+### Planned WiFi Configuration
+
+Future configuration should include:
+
+    ap_enabled
+    sta_enabled
+    hostname
+    saved networks
+    priority order
+
+Future setup options:
+
+- Serial console
+- HTTP API
+- Pico dashboard UI
+- Embedded web dashboard
+
+### Planned mDNS
+
+The controller should eventually support mDNS.
+
+Example:
+
+    http://overland-controller.local
+
+This would avoid needing to look up the controller IP when connected through Starlink or home WiFi.
+
+---
+
+## Embedded Web Dashboard
+
+### Current Direction
+
+The ESP32 should serve a lightweight mobile-friendly dashboard.
+
+Purpose:
+
+- Check battery status from a phone
+- Check fridge/temp status from camp
+- Toggle relays if needed
+- View alarms
+- Provide fallback UI without the Pico display
+
+Design limits:
+
+- No React
+- No external libraries
+- No images
+- Small inline HTML/CSS/JS
+- Poll /status every few seconds
+- Use existing relay endpoints
+
+This dashboard is not intended to replace the physical Pico dashboard.
+
+---
+
+## Optional Future Pi Zero Module
+
+The base system should not require a Pi Zero.
+
+Base system:
+
+    ESP32 controller
+    Pico 2 W dashboard
+
+Optional future advanced module:
+
+    Pi Zero 2 W
+
+Possible Pi Zero functions:
+
+- Rich web dashboard
+- Historical logging
+- Graphs
+- SQLite database
+- MQTT bridge
+- Home Assistant bridge
+- Advanced configuration UI
+
+The core controller should remain functional without the Pi Zero.
+
+---
+
+## Configuration Backup and Restore
+
+Planned future feature.
+
+Goals:
+
+- Export configuration JSON
+- Import configuration JSON
+- Backup install-specific setup
+- Restore after factory reset
+- Make support easier for future users
+
+This is important if the project becomes shareable or sellable.