Repository navigation
SV Dashboard for Stellantis Vehicles – EV/PHEV dashboard, history & more testers wanted #525
Replies: 1 comment 9 replies
|
This integration looks fine and I am very interested specially by the charging history and trips history. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
SV Dashboard for Stellantis Vehicles – EV/PHEV dashboard, history & more testers wanted
A larger update to the dashboard project that originally started here around the Citroën ë-C3.
The project has since evolved into a generic Home Assistant companion integration for Stellantis Vehicles:
SV Dashboard
https://github.com/CaneTLOTW/sv_dashboard
It deliberately builds on top of
homeassistant-stellantis-vehiclesinstead of duplicating vehicle communication, OAuth or session handling. The UI is now capability-driven rather than model-specific, so EV, PHEV/Hybrid and combustion vehicles can expose different cards, history and controls depending on the data actually available from the upstream integration.Current validation
We currently have real-world validation from:
The DS4 test has been especially useful because it showed that even closely related Stellantis vehicles and model years can expose different data and update behaviour. SV Dashboard therefore tracks actual capabilities and real-vehicle evidence instead of assuming that one model represents the whole platform.
The current developer candidate is
0.6.0-beta.15.For this exact candidate:
5d93cba038ea6954bd409e1564cb9b4aa78fdb09Owner runtime validation of that exact candidate is the next gate before promotion.
Dual-Energy / PHEV support
Hybrid/PHEV vehicles can use a native Dual-Energy Hero that keeps battery and fuel information visible at the same time.
The UI does not invent unavailable data. For example:
What SV Dashboard currently provides
Among other things:
Historical and derived data is quality-gated. Missing or implausible API values are kept distinguishable from measured/authoritative vehicle data.
Trip history
Trip history uses Stellantis server trips where available and keeps source timestamps/provenance. Reconstructed values are intentionally limited to cases where the underlying evidence is strong enough.
Charging history
Charging sessions can be reconstructed from observed charging state/SOC history, with guards against bad samples such as transient SOC drops.
Looking for a few more real vehicles
The largest remaining gap is now vehicle diversity, not another ë-C3-only test.
It would be especially useful to get real-world feedback from:
Even a short test is valuable. We are especially interested in which entities are actually populated and how they behave in real use, including:
If you already have another Stellantis vehicle working with
homeassistant-stellantis-vehicles, replying with just brand / model / model year / powertrain is enough to get started.Current external test thread
The active DS4 Hybrid / French beta test is here:
CaneTLOTW/sv_dashboard#2
That thread also contains the consolidated tester-feedback matrix and the implementation status for the current beta.
Small upstream PR for native trip-history transport
There is also a deliberately small upstream PR:
#616
It adds only a native authenticated transport method for historical
/tripsdata:History aggregation, persistence and dashboard behaviour remain outside the upstream integration. The goal is simply to avoid downstream consumers depending on private request/session internals.
Thanks again to everyone who has already shared vehicle data, translations and test feedback. The project is now at the point where a few additional real Stellantis vehicles would be much more useful than adding more model assumptions in code.
All reactions