custom:sv-dashboard-dual-energy-overview-card is the wide native SV Dashboard card for vehicles that expose both electric and fuel data, especially PHEV/Hybrid vehicles.
It is also available from Home Assistant's normal Add card picker as the localized SV vehicle overview – Dual Energy entry. The compact universal vehicle overview remains a separate public card.
The Dual-Energy Hero is deliberately reusable in two different contexts:
- Standalone/start-page Hero — add the card to any ordinary Home Assistant dashboard to show the most important vehicle information without opening the complete SV Dashboard first. This is a supported product use case, not only a beta test scaffold.
- Generated SV Dashboard Hero — the generated dashboard can use the same Dual-Energy presentation for vehicles that expose both electric and fuel capabilities. Pure-electric and other non-dual vehicles keep the compact/universal Hero.
The current beta still uses the compact/universal card in the generated LIVE view. Capability-driven automatic selection of the Dual-Energy Hero for Hybrid/PHEV vehicles is the next integration step after external DS4 validation.
type: custom:sv-dashboard-dual-energy-overview-cardWith more than one SV Dashboard config entry, select the vehicle in the card editor or bind the card to the corresponding entry_id.
The card keeps the two energy domains deliberately separate:
| Vehicle state | Battery side | Fuel side |
|---|---|---|
| Parked / idle | battery SOC and electric range | fuel level and fuel range |
| Driving | battery SOC and current trip energy used in kWh | fuel level and fresh instantaneous fuel consumption when the upstream entity is trustworthy |
| Charging | battery SOC and current charge power | fuel level / range remains available |
Important rules:
current_trip_energyis an absolute kWh value, not kWh/100 km.- Fuel consumption is shown only when the mapped upstream value is numeric, belongs to the current drive and is sufficiently fresh. A stale value is not presented as live consumption.
- Unknown or unsupported values stay neutral (
—); the card does not invent Hybrid/EV values. - Package-derived charging power and energy can be battery-side SOC/time estimates. They are not EVSE/grid meter readings and do not include charging losses.
The production Hero uses native card interactions rather than nested custom:button-card instances:
- click the vehicle image → generated SV vehicle dashboard (
/<dashboard_url_path>/vehicleunlessnavigation_pathoverrides it); - click vehicle temperature → Home Assistant native More Info / recorded history;
- click Battery or Fuel percentage → native More Info for the mapped entity;
- click the current battery/fuel detail → native More Info for the metric currently being displayed.
The vehicle-picture navigation is especially important for the standalone/start-page use case: the card acts as the compact entry point into the full generated vehicle dashboard. The whole card is not a navigation target; the vehicle picture is.
The native implementation replaced the temporary YAML/button-card interaction playground used during beta development.
The small Hero climate control is intentionally treated primarily as a one-shot preconditioning start action, not as the main start/stop control surface.
Citroën describes remote temperature preconditioning as a vehicle-managed cycle to a fixed target around 21 °C. Exact timing differs by model and by immediate versus scheduled use, and Stellantis state feedback can arrive with noticeable delay. For that reason the overview Hero must not encourage rapid repeated clicks that depend on an immediately updated remote state.
Design contract:
- the Hero control starts the available mapped preconditioning action;
- the visual state may follow the upstream preconditioning entity when that state becomes available;
- a delayed state transition does not mean the first command failed;
- explicit Start climate / Stop climate actions remain available in the generated SV Dashboard Quick Actions area for users who intentionally want to stop a running cycle;
- the Hero should not send duplicate start commands merely because remote state feedback is still pending.
The card and its editor use the shared SV Dashboard frontend localisation layer and follow the Home Assistant UI language automatically. An explicit card language override uses the same resolution path.
SV Dashboard currently ships the public frontend contract in 18 languages:
de, en, fr, it, es, pt, nl, da, nb, sv, fi, pl, cs, sk, hu, ro, sl, hr.
DE / EN / FR runtime switching was visually checked during beta.9 owner QA, including the longer French Hybrid labels.
The SVGs below are documentation renderings based on the owner beta.9 runtime screenshots and the approved post-beta.9 wording. They demonstrate layout and localisation without publishing private vehicle/location data.
The SV Dashboard card is not the only way to present the data. The mapped Stellantis entities and the package-owned SV entities are normal Home Assistant data sources, so an advanced user can build a different Lovelace/YAML presentation for the same vehicle data.
A useful prototype contribution contains:
- the YAML/custom-card configuration;
- one or more screenshots;
- which vehicle/powertrain state is being shown (parked, driving, charging, Hybrid fuel use, etc.);
- the intended interaction or information hierarchy;
- no VIN, exact location, account data or other private identifiers.
A well-defined custom prototype can be used as design input for a future package-owned feature. Sharing a prototype does not mean that every third-party card or layout will become a built-in dependency.