Dashboard Cards

Dashboard cards

Cards built from what the integration exposes, using Home Assistant's own card types. Paste them into a dashboard's raw configuration or add them card by card through Edit dashboard -> Add card -> Manual.

Entities used on this page

Placeholder	sunspec_key	Meaning
sensor.inverter_ac_power	W	AC output, W
sensor.inverter_dc_power	DCW	DC input, W
sensor.inverter_module_0_dc_power, ..._1_...	module:N:DCW	Per string, block 160
sensor.inverter_lifetime_energy_produced	WH	Lifetime counter
sensor.solar_energy_daily		Utility meter, see Energy dashboard and statistics
sensor.inverter_operating_state	St	Operating state
sensor.inverter_events	Evt1	Event flags
sensor.inverter_cabinet_temperature	TmpCab
sensor.inverter_ac_frequency	Hz
sensor.battery_state_of_charge	802 SoC
number.inverter_export_limit, switch.inverter_export_limit_enabled		Write beta

The top row

Three tiles: power now, energy today, battery.

type: grid
columns: 3
square: false
cards:
  - type: tile
    entity: sensor.inverter_ac_power
    name: Solar
    icon: mdi:solar-power
  - type: tile
    entity: sensor.solar_energy_daily
    name: Today
    icon: mdi:solar-panel
  - type: tile
    entity: sensor.battery_state_of_charge
    name: Battery

Power as a gauge

Set max to your inverter's rating. The segments turn the needle yellow at half power and green near the top.

type: gauge
entity: sensor.inverter_ac_power
name: Solar power
unit: W
min: 0
max: 8000
needle: true
segments:
  - from: 0
    color: "#9e9e9e"
  - from: 500
    color: "#ffc107"
  - from: 4000
    color: "#4caf50"

The last 24 hours, per string

type: history-graph
title: DC power per string
hours_to_show: 24
entities:
  - entity: sensor.inverter_module_0_dc_power
    name: East
  - entity: sensor.inverter_module_1_dc_power
    name: West

Two strings that used to track each other and stopped doing so is the earliest sign of a failing panel or a dirty section of the roof.

Monthly production as bars

The statistics graph reads long-term statistics, so it works across years without keeping the raw history.

type: statistics-graph
title: Production per month
entities:
  - sensor.inverter_lifetime_energy_produced
period: month
stat_types:
  - change
chart_type: bar
days_to_show: 365

State and flags in one line

A markdown card that reads like a status line and stays empty when nothing is wrong:

type: markdown
content: >
  {% set flags = state_attr('sensor.inverter_events', 'active_flags') or [] %}
  **{{ states('sensor.inverter_operating_state') }}**
  {% if flags %} · {{ flags | join(', ') }}{% endif %}
  · {{ states('sensor.inverter_cabinet_temperature') }} °C
  · {{ states('sensor.inverter_ac_frequency') }} Hz

  Updated {{ relative_time(states.sensor.inverter_ac_power.last_updated) }} ago

The diagnostics group

Everything the device page tags as diagnostic, in one collapsible place:

type: entities
title: Inverter details
state_color: true
entities:
  - entity: sensor.inverter_operating_state
  - entity: sensor.inverter_events
  - entity: sensor.inverter_cabinet_temperature
  - entity: sensor.inverter_ac_frequency
  - entity: sensor.inverter_dc_power
  - type: attribute
    entity: sensor.inverter_events
    attribute: raw
    name: Event bitfield

Export limit controls, only when they exist

The write entities appear once the beta is on. A conditional card keeps the dashboard clean on installations without them, and a second one shows the limit prominently while it is active:

type: conditional
conditions:
  - condition: state
    entity: switch.inverter_export_limit_enabled
    state_not: unavailable
card:
  type: entities
  title: Export limit
  entities:
    - entity: switch.inverter_export_limit_enabled
    - entity: number.inverter_export_limit
    - entity: number.inverter_export_limit_revert_time

type: conditional
conditions:
  - condition: state
    entity: switch.inverter_export_limit_enabled
    state: "on"
card:
  type: markdown
  content: >
    ⚠️ Export limited to **{{ states('number.inverter_export_limit') }} %**

Power flow cards

The community power flow cards from HACS (Power Flow Card Plus, Tesla Style Solar Power Card and relatives) want one power entity per node. The mapping is:

Node	Entity
Solar	sensor.inverter_ac_power, or the block 160 string powers summed if you want DC
Grid	The meter's W, with the sign convention the card expects; most take positive as import
Battery	Block 802 W
Home	The card computes it, or use the House consumption template from Energy dashboard and statistics