Skip to content

Dashboard cards ​

State of charge, power, solar, and operating mode are ordinary Home Assistant sensors. You can put them on any dashboard with the built-in cards. This page is a copy-paste layout for a live view, plus the same cards added in the visual editor.

The Battery health cards are a different view. They show usable capacity and an estimated state of health. They do not replace the live cards below.

Find your entity ids ​

Every example uses <battery> as a stand-in for the start of the entity id. Home Assistant builds that from the device name.

Device name Home Assistant usesReplace <battery> with
Venus E (3.0)venus_e_3_0
Venus Avenus_a
Venus Dvenus_d

A second battery with the same name gets _2 on the end of the prefix (venus_a_2). If you renamed the device, the prefix follows the new name.

To copy yours:

  1. Go to Settings > Devices & services > Marstek and open the battery.
  2. Select Battery level.
  3. Read the entity id, for example sensor.venus_e_3_0_battery_level.
  4. The prefix is the part between sensor. and _battery_level.

Developer tools > States, filtered on battery_level, shows the same id.

The examples use the English names. Home Assistant creates the id from the name in the language you were using when the battery was added, and it does not rename the id if you switch language later. On a Dutch Home Assistant, Battery level was created as Batterijniveau, so the id ends in _batterijniveau instead of _battery_level. If a card says the entity is missing, copy the id from the device page.

A rename or an area change can give one entity a different prefix from the others. The single <battery> placeholder fits when Battery level, Battery power, and Operating mode still share it. When they do not, paste each entity id on its own.

The id you paste into a card is not the unique id. The unique id is the battery's BLE MAC plus an internal key, such as battery_soc for Battery level, and it stays put when you rename the entity. Leave it alone. The table lists both, so a diagnostics download is easy to match to a card.

What you see (English)Paste thisUnique id ends with
Battery levelsensor.<battery>_battery_levelbattery_soc
Battery powersensor.<battery>_battery_powerbattery_power
Battery statussensor.<battery>_battery_statusbattery_status
Operating modeselect.<battery>_operating_modeoperating_mode
On-grid powersensor.<battery>_on_grid_powerongrid_power
Off-grid powersensor.<battery>_off_grid_poweroffgrid_power
PV powersensor.<battery>_pv_powerpv_power
PV1 powersensor.<battery>_pv1_powerpv1_power
Battery state of healthsensor.<battery>_battery_state_of_healthbattery_state_of_health
Battery temperaturesensor.<battery>_battery_temperaturebat_temp
WiFi signal strengthsensor.<battery>_wifi_signal_strengthwifi_rssi

PV power and PV1 power exist on Venus A and Venus D only. Positive Battery power is discharging. Negative Battery power is charging.

What the local API does not send ​

Battery state of health is an estimate from long charge and discharge runs. It stays unknown until a few of those runs are finished. The local API does not send a state of health, a cycle count, or cell voltages, and it has only one temperature.

The Energy tab on the Battery health card shows equivalent full cycles: energy the battery has delivered, divided by its nameplate. That is not a cycle counter from the battery. Cell-by-cell screens in other Marstek projects come from Modbus, which is a different connection.

Build it with the visual editor ​

No YAML is required. On a dashboard, choose Edit dashboard, then Add card.

  1. Search for Gauge. Choose Battery level. Set the minimum to 0 and the maximum to 100.
  2. Add a Tile. Choose Battery power. Open Features and add Trend graph.
  3. Add a Tile. Choose Operating mode. Selecting the card opens the mode list.
  4. On Venus A or Venus D, add another Tile and choose PV power. Skip this on Venus E, Venus C, and Venus E mini. Those models have no solar entities, and the card would stay empty.
  5. Add an Entities card. Add Battery status, On-grid power, Off-grid power, and Battery state of health.
  6. Add a History graph. Add Battery power, and PV power when the battery has solar. Set Hours to show to 12.
  7. Add a card, search for Marstek, and pick Marstek battery health. Choose the battery. The editor can also set a title and which tab opens first. Details are in Battery health.
Gauge card configuration in the visual editor. Battery level is selected, the name is Battery level, the minimum is 0, the maximum is 100, and a live preview shows the gauge.

The name fields in the examples are optional. A short name keeps the label readable on a phone. Without one, every card repeats the device name, such as Venus E (3.0) Battery level, and that gets cut off. Leave name out when you want the full entity name in your Home Assistant language. A name you type stays in that language.

Temperature and Wi-Fi are not in the steps above because those sensors start disabled. Turn them on first, then add them to the entities card. See Temperature and Wi-Fi.

A sections view stacks cards into one column on a phone. Add the cards to one section and stop there if that layout is enough.

Venus E layout ​

Venus E has no PV sensors. This stack is one card: a gauge beside battery power, then mode beside status, then the detail list and 12 hours of power history. Two columns stay readable on a phone. A third column gets cramped, so this layout stops at two.

Paste it from the dashboard menu under Raw configuration editor, or add the same cards one by one with the visual editor.

yaml
type: vertical-stack
cards:
  - type: grid
    columns: 2
    square: false
    cards:
      - type: gauge
        entity: sensor.<battery>_battery_level
        name: Battery level
        min: 0
        max: 100
      - type: tile
        entity: sensor.<battery>_battery_power
        name: Power
        features:
          - type: trend-graph
            hours_to_show: 12
  - type: grid
    columns: 2
    square: false
    cards:
      - type: tile
        entity: select.<battery>_operating_mode
        name: Mode
      - type: tile
        entity: sensor.<battery>_battery_status
        name: Status
  - type: entities
    title: Battery
    entities:
      - entity: sensor.<battery>_on_grid_power
        name: On-grid
      - entity: sensor.<battery>_off_grid_power
        name: Off-grid
      - entity: sensor.<battery>_battery_state_of_health
        name: State of health
      # Enable these on the device page first, then uncomment.
      # - entity: sensor.<battery>_battery_temperature
      # - entity: sensor.<battery>_wifi_signal_strength
  - type: history-graph
    title: Power
    hours_to_show: 12
    entities:
      - entity: sensor.<battery>_battery_power
        name: Power
      - entity: sensor.<battery>_on_grid_power
        name: On-grid
Venus E layout with short names. The gauge, power, mode, and status cards no longer repeat the device name. The history graph shows 12 hours of charge and discharge.

State of health on the list is the estimate. A battery that has not finished a long charge run and a long discharge run stays Unknown. The picture shows a pack that already has an estimate.

The gauge, tile, entities, and history cards are the built-in ones: gauge, tile, entities, and history graph.

Venus A and Venus D layout ​

Use the same stack, and put PV power in the second row instead of Battery status. Battery status stays in the entities list. PV1 power is there when you want the first solar input on its own. Venus D can show PV2, PV3, and PV4 the same way (sensor.<battery>_pv2_power, and so on). The full list is in Entities.

yaml
type: vertical-stack
cards:
  - type: grid
    columns: 2
    square: false
    cards:
      - type: gauge
        entity: sensor.<battery>_battery_level
        name: Battery level
        min: 0
        max: 100
      - type: tile
        entity: sensor.<battery>_battery_power
        name: Power
        features:
          - type: trend-graph
            hours_to_show: 12
  - type: grid
    columns: 2
    square: false
    cards:
      - type: tile
        entity: sensor.<battery>_pv_power
        name: PV
      - type: tile
        entity: select.<battery>_operating_mode
        name: Mode
  - type: entities
    title: Battery
    entities:
      - entity: sensor.<battery>_battery_status
        name: Status
      - entity: sensor.<battery>_pv1_power
        name: PV1
      - entity: sensor.<battery>_on_grid_power
        name: On-grid
      - entity: sensor.<battery>_off_grid_power
        name: Off-grid
      - entity: sensor.<battery>_battery_state_of_health
        name: State of health
      # Enable these on the device page first, then uncomment.
      # - entity: sensor.<battery>_battery_temperature
      # - entity: sensor.<battery>_wifi_signal_strength
  - type: history-graph
    title: Power
    hours_to_show: 12
    entities:
      - entity: sensor.<battery>_battery_power
        name: Power
      - entity: sensor.<battery>_pv_power
        name: PV
      - entity: sensor.<battery>_on_grid_power
        name: On-grid
Venus A and Venus D layout on a Venus D, with short names. PV power sits beside mode, and the history graph includes solar over 12 hours.

Temperature and Wi-Fi ​

Battery temperature and the Wi-Fi sensors are diagnostic and start disabled. A card that points at one of them shows a missing entity until you enable it.

  1. Open the battery's device page.
  2. Select Battery temperature or WiFi signal strength. Disabled entities are listed on that page.
  3. Select the gear icon, switch Enabled on, and select Update.

Enabling Battery temperature, Battery remaining capacity, Battery rated capacity, Charge permission, or Discharge permission makes Home Assistant ask the battery for battery details on the slow poll, every 5 minutes by default. Enabling any Wi-Fi sensor (signal, IP address, gateway, subnet mask, or DNS) starts the Wi-Fi request on that same slow poll. While every one of those entities is off, the integration does not send the request. The interval is Configure > Polling Intervals > Slow. See Options and Entities.

On Venus A, D, and E 3.0 below firmware 150, the temperature entities are not created. That request has been linked to the battery resetting itself. Firmware 150 and newer, including a Venus A on 151, can enable them. After a firmware update they come back, still disabled.

Energy dashboard ​

Lifetime energy belongs on Home Assistant's Energy dashboard, not on this live card. Total grid input energy and Total grid output energy are the battery's own charge and discharge totals. On Venus A and Venus D, Total solar energy is the solar total. Adding solar and the battery totals together can count the same solar twice. Energy dashboard shows which row each sensor belongs on.

Battery health card ​

The health card is already registered. Search for Marstek in Add card and pick Marstek battery health for one battery, or Marstek battery fleet when you want every battery on one scale.

If you edit YAML, add the card in the visual editor first and then open the code editor. Home Assistant fills in device_id. That value is the device registry id, not the MAC and not the entity id.

yaml
type: custom:marstek-battery-health-card
device_id: YOUR_DEVICE_ID
show_tabs: true
default_tab: capacity

default_tab is one of capacity, runs, energy, restarts, or corrections. The fleet card is custom:marstek-battery-fleet-card and needs no device id.

A sections view on a phone ​

Paste this as a view in the raw configuration editor when the dashboard uses sections. On a narrow screen the section becomes one column. On a wide screen the gauge and the power tile sit side by side.

yaml
type: sections
max_columns: 2
sections:
  - type: grid
    cards:
      - type: gauge
        entity: sensor.<battery>_battery_level
        name: Battery level
        min: 0
        max: 100
      - type: tile
        entity: sensor.<battery>_battery_power
        name: Power
        features:
          - type: trend-graph
            hours_to_show: 12
      - type: tile
        entity: select.<battery>_operating_mode
        name: Mode
  - type: grid
    cards:
      - type: entities
        title: Battery
        entities:
          - entity: sensor.<battery>_battery_status
            name: Status
          - entity: sensor.<battery>_on_grid_power
            name: On-grid
          - entity: sensor.<battery>_off_grid_power
            name: Off-grid
          - entity: sensor.<battery>_battery_state_of_health
            name: State of health
      - type: history-graph
        title: Power
        hours_to_show: 12
        entities:
          - entity: sensor.<battery>_battery_power
            name: Power
          - entity: sensor.<battery>_on_grid_power
            name: On-grid

On Venus A or Venus D, add a tile for sensor.<battery>_pv_power in the first section and add that same entity to the history graph.

The Venus E sections view at phone width, about 390 pixels. Short names keep Power, Mode, and State of health on one line.