docs: audit stale dashboard references and clarify DS18B20 support
This commit is contained in:
@@ -250,3 +250,16 @@ Selected dashboard hardware:
|
||||
This replaces the earlier Pico dashboard concept as the active dashboard architecture.
|
||||
|
||||
The Dashboard ESP32-S3 communicates with the Cargo ESP32 over WiFi/HTTP REST for v1. CAN/OBD-II support remains a future dashboard-side vehicle-visualization feature and is not part of the Cargo ESP32 role.
|
||||
|
||||
## Existing DS18B20 Temperature Support
|
||||
|
||||
DS18B20 temperature sensor support is already part of the Cargo ESP architecture.
|
||||
|
||||
Current responsibility split:
|
||||
|
||||
- Cargo ESP32 owns DS18B20 sensor reading.
|
||||
- Cargo ESP32 exposes temperature state through the WebUI/API path.
|
||||
- Dashboard ESP32-S3 should consume temperature data from the Cargo ESP API.
|
||||
- Dashboard ESP32-S3 should not wire directly to cargo-area DS18B20 sensors for v1.
|
||||
|
||||
This means future dashboard work should display existing Cargo ESP temperature telemetry rather than reimplementing temperature sensing on the dashboard.
|
||||
|
||||
Reference in New Issue
Block a user