Dashboard Setup
PowerSync includes an auto-generated Lovelace dashboard that adapts to your configuration. The dashboard uses a strategy pattern — it checks which entities exist at render time and only builds cards for features you have set up.
Install these via HACS > Frontend:
-
button-card— Compact chips for controls -
card-mod— Custom card styling -
power-flow-card-plus— Real-time energy flow visualization -
apexcharts-card— Advanced charting for price/energy history
For a premium power flow visualization, install tesla-style-solar-power-card via HACS. When installed, PowerSync automatically uses it instead of power-flow-card-plus, with full entity mapping including:
- Core sensors (solar, grid, battery, home load)
- EV charging power (when EV is configured)
- Individual PV arrays (when available)
- Weather entity for dynamic backgrounds
- Sun entity for day/night theming
If the tesla-style card is not installed, the dashboard falls back to power-flow-card-plus.
The dashboard is auto-created when PowerSync loads. It appears in your sidebar as PowerSync.
No manual YAML configuration is required. The dashboard strategy JS is registered automatically and builds all cards dynamically based on your configured entities.
If you don't see it:
- Ensure the required HACS cards above are installed
- Restart Home Assistant
- Check Settings > Dashboards — "PowerSync" should appear
The dashboard includes up to 16 sections, each shown only when the relevant entities exist:
| Section | Gate Entity / Condition |
|---|---|
| Price Gauges | Price sensors exist |
| Battery Controls | Battery system configured |
| Smart Optimizer | Optimizer enabled |
| Power Flow | Core power sensors |
| Price Chart | Dynamic pricing provider |
| TOU Schedule | TOU tariff synced |
| LP Forecast Summary | LP optimizer active |
| LP Solar/Load Chart | Forecast sensors exist |
| LP Price Chart | Price forecast sensors exist |
| Solar Curtailment | Curtailment configured |
| AC Inverter Controls | AC inverter configured |
| FoxESS Sensors | FoxESS battery system |
| Battery Health | Health sensor available |
| Energy Charts | Daily energy sensors |
| Demand Charge | Demand tracking enabled |
| AEMO Spike | Spike detection configured |
The Force Charge and Force Discharge duration selectors (select.power_sync_force_charge_duration and select.power_sync_force_discharge_duration) are created automatically by the integration. No manual helper setup is required.
The Battery Health sensor (sensor.power_sync_battery_health) shows your battery's state of health as a percentage. How it gets populated depends on your battery system:
- Sungrow, Sigenergy, GoodWe — SOH is read automatically from the inverter. No setup required, it just works.
- Tesla — Use either the mobile app TEDAPI scan or the capacity sensor blueprint below.
- FoxESS — No SOH register is available, so the sensor shows "Unknown".
See Sensors for full details.
If your battery system exposes a capacity sensor (e.g. Tesla Powerwall), you can use this blueprint to sync battery health data into PowerSync. It reads the current capacity, calculates degradation against the manufacturer spec, and calls power_sync.sync_battery_health every 6 hours.
Note: Sungrow, Sigenergy, and GoodWe users don't need this blueprint — SOH is read directly from the inverter.
Import:
Or manually: Settings > Automations & Scenes > Blueprints > Import Blueprint and paste:
https://github.com/bolagnaise/PowerSync/blob/main/blueprints/battery_health_from_powerwall_capacity_sensor.yaml
Configuration:
| Setting | Description | Example |
|---|---|---|
| Capacity sensor | Sensor reporting current battery capacity | sensor.powerwall_capacity |
| Capacity sensor unit | Whether the sensor reports in kWh or Wh | kwh |
| Original capacity (Wh) | Manufacturer spec total capacity |
13500 (1x Powerwall), 27000 (2x) |
| Battery count | Number of batteries (reporting only) | 1 |