Configuration
Configuration Options
This Strategy has a sensible default configuration, which is the one i myself use!
You can start without configuring anything. If you want to change something take a look at the Configuration Documentation.
Click for Configuration Options
option | description | type | required | default | example |
---|---|---|---|---|---|
platforms | Platforms (= integrations) for which the strategy should generate rows
| Array | yes | Zigbee, Switchbot, Other (always present everything that is not defined in platforms!) | platforms: - platform: hacs title: HACS - platform: MQTT title: Everything MQTT |
minColumnWidth | Minimal Column Width in the Grid = The Minimal Width of the Cards. | number | yes | set for area-dashboard-strategy set for all other strategies | minColumnWidth: 300 |
replaceCards | You can set a card to be used for a specific entity. Overwrites default card config | Object | no | - | replaceCards: button.test: type: entity entities: - $entity |
So valid YAML for this could look like this:
---
strategy:
type: custom:battery-view-strategy
config:
platforms:
- platform: hacs
title: HACS
- platform: MQTT
title: Everything MQTT
minColumnWidth: 300
replaceCards:
button.test:
type: entity
entities:
- "$entity"
icon: mdi:test
path: test
title: Test
I used all available options in this example. You don`t need to do this! Take a look at the required fields for what you need!
Default Config explained
The default config is written as yaml. This should make it easy to make your own changes because it is written exactly as you would in your dashboard.
You can find it here.
Additionally for this View Strategy the platforms options is hard-coded so it is not defined in yaml but can be overwritten!
There are Rows for:
- Zigbee
- Switchbot
- Other (always present everything that is not defined in platforms!)