Move /lovelace -> /dashboards, and renames resulting from that (#22036)
@ -75,7 +75,7 @@ collections:
|
||||
output: true
|
||||
faq:
|
||||
output: true
|
||||
lovelace:
|
||||
dashboards:
|
||||
output: true
|
||||
|
||||
# ----------------------- #
|
||||
|
@ -20,6 +20,6 @@
|
||||
"scripts": {
|
||||
"markdown:lint": "remark --quiet --frail .",
|
||||
"textlint:all": "textlint source",
|
||||
"textlint": "textlint source/_examples source/_docs source/_faq source/_integrations source/_lovelace source/cloud source/getting-started source/hassio source/lovelace"
|
||||
"textlint": "textlint source/_examples source/_docs source/_faq source/_integrations source/_dashboards source/cloud source/getting-started source/hassio source/dashboards"
|
||||
}
|
||||
}
|
||||
|
@ -8,7 +8,7 @@ description: "The Alarm Panel card allows you to arm and disarm your alarm contr
|
||||
The Alarm Panel card allows you to arm and disarm your [alarm control panel](/integrations/#alarm) integrations.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_alarm_panel_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
<img src='/images/dashboards/lovelace_alarm_panel_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
Screenshot of the Alarm Panel card.
|
||||
</p>
|
||||
|
||||
@ -66,7 +66,7 @@ Title example:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_alarm_panel_title_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
<img src='/images/dashboards/lovelace_alarm_panel_title_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
Screenshot of the Alarm Panel card.
|
||||
</p>
|
||||
|
@ -35,7 +35,7 @@ show_camera:
|
||||
default: false
|
||||
navigation_path:
|
||||
required: false
|
||||
description: link to view. For more information about views, see the [view documentation](/lovelace/views/)
|
||||
description: link to view. For more information about views, see the [view documentation](/dashboards/views/)
|
||||
type: string
|
||||
theme:
|
||||
required: false
|
@ -8,7 +8,7 @@ description: "The Button card allows you to add buttons to perform tasks."
|
||||
The Button card allows you to add buttons to perform tasks.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_button_card.png' alt='Screenshot of three Button Cards'>
|
||||
<img src='/images/dashboards/lovelace_entity_button_card.png' alt='Screenshot of three Button Cards'>
|
||||
Screenshot of three Button Cards.
|
||||
</p>
|
||||
|
||||
@ -32,9 +32,9 @@ Icon Height:
|
||||
Theme:
|
||||
description: Name of any loaded theme to be used for this card. For more information about themes, see the [frontend documentation](/integrations/frontend/).
|
||||
Tap Action:
|
||||
description: The action taken on card tap. For more information, see the [action documentation](/lovelace/actions/#tap-action).
|
||||
description: The action taken on card tap. For more information, see the [action documentation](/dashboards/actions/#tap-action).
|
||||
Hold Action:
|
||||
description: The action taken on card tap and hold. For more information, see the [action documentation](/lovelace/actions/#hold-action).
|
||||
description: The action taken on card tap and hold. For more information, see the [action documentation](/dashboards/actions/#hold-action).
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
### YAML
|
||||
@ -87,15 +87,15 @@ state_color:
|
||||
default: true
|
||||
tap_action:
|
||||
required: false
|
||||
description: The action taken on card tap. For more information, see the [action documentation](/lovelace/actions/#tap-action).
|
||||
description: The action taken on card tap. For more information, see the [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: The action taken on card tap and hold. For more information, see the [action documentation](/lovelace/actions/#hold-action).
|
||||
description: The action taken on card tap and hold. For more information, see the [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: The action taken on card double-tap. For more information, see the [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: The action taken on card double-tap. For more information, see the [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
theme:
|
||||
required: false
|
||||
@ -135,6 +135,6 @@ tap_action:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_button_complex_card.png' alt='Screenshot of the Button card with Script Service'>
|
||||
<img src='/images/dashboards/lovelace_entity_button_complex_card.png' alt='Screenshot of the Button card with Script Service'>
|
||||
Screenshot of the Button card with Script Service.
|
||||
</p>
|
@ -8,7 +8,8 @@ description: "The calendar card displays your calendar entities in a month, day
|
||||
The Calendar card displays your [calendar](/integrations/#calendar) entities in a month, day and list view.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_calendar_card.png' alt='Screenshot of the calendar card'>
|
||||
<img src='/images/dashboards/lovelace_calendar_card.png' alt='Screenshot of the
|
||||
calendar card'>
|
||||
Screenshot of the Calendar card.
|
||||
</p>
|
||||
|
@ -12,7 +12,7 @@ At the moment there are no configuration options available for these cards, you
|
||||
## Energy date picker
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/date-selection.png' alt='Screenshot of the energy date selection card'>
|
||||
<img src='/images/dashboards/energy/date-selection.png' alt='Screenshot of the energy date selection card'>
|
||||
Screenshot of the Energy date selection card.
|
||||
</p>
|
||||
|
||||
@ -26,7 +26,7 @@ type: energy-date-selection
|
||||
## Energy usage graph
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/usage-graph.png' alt='Screenshot of the energy usage graph card'>
|
||||
<img src='/images/dashboards/energy/usage-graph.png' alt='Screenshot of the energy usage graph card'>
|
||||
Screenshot of the Energy usage graph card.
|
||||
</p>
|
||||
|
||||
@ -41,7 +41,7 @@ type: energy-usage-graph
|
||||
## Solar production graph
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/solar-graph.png' alt='Screenshot of the solar graph card'>
|
||||
<img src='/images/dashboards/energy/solar-graph.png' alt='Screenshot of the solar graph card'>
|
||||
Screenshot of the Solar production graph card.
|
||||
</p>
|
||||
|
||||
@ -55,7 +55,7 @@ type: energy-solar-graph
|
||||
## Gas consumption graph
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/gas-graph.png' alt='Screenshot of the gas consumption graph card'>
|
||||
<img src='/images/dashboards/energy/gas-graph.png' alt='Screenshot of the gas consumption graph card'>
|
||||
Screenshot of the gas consumption graph card.
|
||||
</p>
|
||||
|
||||
@ -70,7 +70,7 @@ type: energy-gas-graph
|
||||
## Energy distribution
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/distribution.png' alt='Screenshot of the energy distribution card'>
|
||||
<img src='/images/dashboards/energy/distribution.png' alt='Screenshot of the energy distribution card'>
|
||||
Screenshot of the Energy distribution card.
|
||||
</p>
|
||||
|
||||
@ -89,7 +89,7 @@ link_dashboard: true
|
||||
## Energy sources table
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/sources-table.png' alt='Screenshot of the energy sources table card'>
|
||||
<img src='/images/dashboards/energy/sources-table.png' alt='Screenshot of the energy sources table card'>
|
||||
Screenshot of the Energy sources table card.
|
||||
</p>
|
||||
|
||||
@ -104,7 +104,7 @@ type: energy-sources-table
|
||||
## Grid neutrality gauge
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/grid-neutrality-gauge.png' alt='Screenshot of the grid neutrality gauge card'>
|
||||
<img src='/images/dashboards/energy/grid-neutrality-gauge.png' alt='Screenshot of the grid neutrality gauge card'>
|
||||
Screenshot of the Grid neutrality gauge card.
|
||||
</p>
|
||||
|
||||
@ -118,7 +118,7 @@ type: energy-grid-neutrality-gauge
|
||||
## Solar consumed gauge
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/solar-consumed-gauge.png' alt='Screenshot of the solar consumed gauge card'>
|
||||
<img src='/images/dashboards/energy/solar-consumed-gauge.png' alt='Screenshot of the solar consumed gauge card'>
|
||||
Screenshot of the Solar consumed gauge card.
|
||||
</p>
|
||||
|
||||
@ -132,7 +132,7 @@ type: energy-solar-consumed-gauge
|
||||
## Carbon consumed gauge
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/carbon-consumed-gauge.png' alt='Screenshot of the carbon consumed gauge card'>
|
||||
<img src='/images/dashboards/energy/carbon-consumed-gauge.png' alt='Screenshot of the carbon consumed gauge card'>
|
||||
Screenshot of the Carbon consumed gauge card.
|
||||
</p>
|
||||
|
||||
@ -146,7 +146,7 @@ type: energy-carbon-consumed-gauge
|
||||
## Devices energy graph
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/energy/devices-graph.png' alt='Screenshot of the devices energy graph card'>
|
||||
<img src='/images/dashboards/energy/devices-graph.png' alt='Screenshot of the devices energy graph card'>
|
||||
Screenshot of the devices energy graph card.
|
||||
</p>
|
||||
|
@ -42,11 +42,11 @@ state_color:
|
||||
default: false
|
||||
header:
|
||||
required: false
|
||||
description: Header widget to render. See [header documentation](/lovelace/header-footer/).
|
||||
description: Header widget to render. See [header documentation](/dashboards/header-footer/).
|
||||
type: map
|
||||
footer:
|
||||
required: false
|
||||
description: Footer widget to render. See [footer documentation](/lovelace/header-footer/).
|
||||
description: Footer widget to render. See [footer documentation](/dashboards/header-footer/).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -94,15 +94,15 @@ state_color:
|
||||
default: false
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on row tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on row tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on row tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on row tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on row double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on row double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -176,15 +176,15 @@ action_name:
|
||||
default: "`Run`"
|
||||
tap_action:
|
||||
required: true
|
||||
description: Action taken on button tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on button tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on button tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on button tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on button double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on button double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -231,15 +231,15 @@ entities:
|
||||
default: "true"
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on button tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on button tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on button tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on button tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on button double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on button double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -382,7 +382,7 @@ type: entities
|
||||
title: Entities card sample
|
||||
show_header_toggle: true
|
||||
header:
|
||||
image: "https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png"
|
||||
image: "https://www.home-assistant.io/images/dashboards/header-footer/balloons-header.png"
|
||||
type: picture
|
||||
entities:
|
||||
- entity: alarm_control_panel.alarm
|
||||
@ -398,7 +398,7 @@ entities:
|
||||
Above the divider are regular entity rows, below one of type `buttons`. Note that regular entity rows automatically show the entity name, whereas for buttons you have to explicitly specify a label / name.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_row_buttons.jpg' alt='Screenshot of buttons row'>
|
||||
<img src='/images/dashboards/lovelace_entity_row_buttons.jpg' alt='Screenshot of buttons row'>
|
||||
Screenshot of buttons row.
|
||||
</p>
|
||||
|
||||
@ -419,7 +419,7 @@ entities:
|
||||
### Other special rows
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_row_special.jpg' alt='Screenshot of other special rows'>
|
||||
<img src='/images/dashboards/lovelace_entity_row_special.jpg' alt='Screenshot of other special rows'>
|
||||
Screenshot of other special rows.
|
||||
</p>
|
||||
|
@ -7,10 +7,10 @@ description: "The Entity Filter card allows you to define a list of entities tha
|
||||
|
||||
The Entity Filter card allows you to define a list of entities that you want to track only when in a certain state. Very useful for showing lights that you forgot to turn off or show a list of people only when they're at home.
|
||||
|
||||
This type of card can also be used together with rest of cards that allow multiple entities, allowing you to use [glance](/lovelace/glance/) or [picture-glance](/lovelace/picture-glance/). By default it uses [entities](/lovelace/entities/) card model.
|
||||
This type of card can also be used together with rest of cards that allow multiple entities, allowing you to use [glance](/dashboards/glance/) or [picture-glance](/dashboards/picture-glance/). By default it uses [entities](/dashboards/entities/) card model.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_filter.png' alt='Screenshot of the Entity Filter card'>
|
||||
<img src='/images/dashboards/lovelace_entity_filter.png' alt='Screenshot of the Entity Filter card'>
|
||||
Screenshot of the Entity Filter card.
|
||||
</p>
|
||||
|
||||
@ -108,7 +108,7 @@ state_filter:
|
||||
- "on"
|
||||
```
|
||||
|
||||
Show only people that are at home using [glance](/lovelace/glance/):
|
||||
Show only people that are at home using [glance](/dashboards/glance/):
|
||||
|
||||
```yaml
|
||||
type: entity-filter
|
||||
@ -124,7 +124,7 @@ card:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_filter_glance.png' alt='Entity filter combined with glance card'>
|
||||
<img src='/images/dashboards/lovelace_entity_filter_glance.png' alt='Entity filter combined with glance card'>
|
||||
Entity filter combined with glance card.
|
||||
</p>
|
||||
|
@ -8,7 +8,7 @@ description: "The Entity card gives you a quick overview of your entity's state"
|
||||
The Entity card gives you a quick overview of your entity's state.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_card.png' alt='Screenshot of the entity card'>
|
||||
<img src='/images/dashboards/lovelace_entity_card.png' alt='Screenshot of the entity card'>
|
||||
Screenshot of the Entity card.
|
||||
</p>
|
||||
|
||||
@ -52,7 +52,7 @@ theme:
|
||||
type: string
|
||||
footer:
|
||||
required: false
|
||||
description: Footer widget to render. See [footer documentation](/lovelace/header-footer/).
|
||||
description: Footer widget to render. See [footer documentation](/dashboards/header-footer/).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
@ -8,12 +8,12 @@ description: "The Gauge card is a basic card that allows visually seeing sensor
|
||||
The Gauge card is a basic card that allows visually seeing sensor data.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_gauge_card.gif' alt='Screenshot of the Gauge card'>
|
||||
<img src='/images/dashboards/lovelace_gauge_card.gif' alt='Screenshot of the Gauge card'>
|
||||
Screenshot of the Gauge card.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_gauge_needle_card.png' alt='Screenshot of the Gauge card in needle mode'>
|
||||
<img src='/images/dashboards/lovelace_gauge_needle_card.png' alt='Screenshot of the Gauge card in needle mode'>
|
||||
Screenshot of the Gauge card in needle mode.
|
||||
</p>
|
||||
|
||||
@ -95,7 +95,7 @@ entity: sensor.cpu_usage
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_gauge_card.gif' alt='Screenshot of the gauge card with custom title and unit of measurement'>
|
||||
<img src='/images/dashboards/lovelace_gauge_card.gif' alt='Screenshot of the gauge card with custom title and unit of measurement'>
|
||||
Screenshot of the gauge card with custom title and unit of measurement.
|
||||
</p>
|
||||
|
@ -5,10 +5,10 @@ sidebar_label: Glance
|
||||
description: "The Glance card is useful to group multiple sensors in a compact overview."
|
||||
---
|
||||
|
||||
The Glance card is useful to group multiple sensors in a compact overview. Keep in mind that this can be used together with [entity-filter](/lovelace/entity-filter/) cards to create dynamic cards.
|
||||
The Glance card is useful to group multiple sensors in a compact overview. Keep in mind that this can be used together with [entity-filter](/dashboards/entity-filter/) cards to create dynamic cards.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_glance_card.png' alt='Screenshot of the glance card'>
|
||||
<img src='/images/dashboards/lovelace_glance_card.png' alt='Screenshot of the glance card'>
|
||||
Screenshot of the Glance card.
|
||||
</p>
|
||||
|
||||
@ -90,15 +90,15 @@ show_state:
|
||||
default: true
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -129,7 +129,7 @@ entities:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_glance_card.png' alt='Screenshot of the glance card with custom title'>
|
||||
<img src='/images/dashboards/lovelace_glance_card.png' alt='Screenshot of the glance card with custom title'>
|
||||
Screenshot of the glance card with custom title.
|
||||
</p>
|
||||
|
@ -8,7 +8,7 @@ description: "The Grid card allows you to show multiple cards in a grid."
|
||||
The Grid card allows you to show multiple cards in a grid. It will first fill the columns, automatically adding new rows as needed.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_grid.png' alt='Screenshot of the grid card'>
|
||||
<img src='/images/dashboards/lovelace_grid.png' alt='Screenshot of the grid card'>
|
||||
Screenshot of the Grid card.
|
||||
</p>
|
||||
|
@ -8,12 +8,12 @@ description: "The History Graph card allows you to display a graph for each of t
|
||||
The History Graph card allows you to display a graph for each of the entities listed.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_history_graph.png' alt='Screenshot of the history graph card for entities without a unit_of_measurement'>
|
||||
<img src='/images/dashboards/lovelace_history_graph.png' alt='Screenshot of the history graph card for entities without a unit_of_measurement'>
|
||||
Screenshot of the History Graph card, when the sensor has no `unit_of_measurement` defined.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_history_graph_lines.png' alt='Screenshot of the history graph card for entities with a unit_of_measurement'>
|
||||
<img src='/images/dashboards/lovelace_history_graph_lines.png' alt='Screenshot of the history graph card for entities with a unit_of_measurement'>
|
||||
Screenshot of the History Graph card, when the sensor has a `unit_of_measurement` defined.
|
||||
</p>
|
||||
|
@ -39,6 +39,6 @@ cards:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_horizontal_stack.PNG' alt='Two picture cards in a horizontal stack card'>
|
||||
<img src='/images/dashboards/lovelace_horizontal_stack.PNG' alt='Two picture cards in a horizontal stack card'>
|
||||
Two Picture cards in a Horizontal Stack card.
|
||||
</p>
|
@ -8,7 +8,7 @@ description: "The Humidifier card gives control of your humidifier entity, allow
|
||||
The Humidifier card lets you control and monitor humidifiers, dehumidifiers, and hygrostat devices.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_humidifier_card.png' alt='Screenshot of the humidifier card'>
|
||||
<img src='/images/dashboards/lovelace_humidifier_card.png' alt='Screenshot of the humidifier card'>
|
||||
Screenshot of the humidifier card.
|
||||
</p>
|
||||
|
@ -12,7 +12,7 @@ You can't embed sites using HTTP if you are using HTTPS for your Home Assistant.
|
||||
</div>
|
||||
|
||||
<p class='img'>
|
||||
<img width="500" src='/images/lovelace/lovelace_iframe.png' alt='Windy weather radar as Webpage'>
|
||||
<img width="500" src='/images/dashboards/lovelace_iframe.png' alt='Windy weather radar as Webpage'>
|
||||
Windy weather radar as Webpage.
|
||||
</p>
|
||||
|
@ -8,7 +8,7 @@ description: "The Light card allows you to change the brightness of the light."
|
||||
The Light card allows you to change the brightness of the light.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_light_card.png' alt='Screenshot of the Light card'>
|
||||
<img src='/images/dashboards/lovelace_light_card.png' alt='Screenshot of the Light card'>
|
||||
Screenshot of the Light card.
|
||||
</p>
|
||||
|
||||
@ -46,11 +46,11 @@ theme:
|
||||
type: string
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -71,6 +71,6 @@ name: My Office
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_light_complex_card.png' alt='Screenshot of the Light card'>
|
||||
<img src='/images/dashboards/lovelace_light_complex_card.png' alt='Screenshot of the Light card'>
|
||||
Screenshot of the Light card names.
|
||||
</p>
|
@ -8,7 +8,7 @@ description: "The Logbook card displays entries from the logbook for specific en
|
||||
The Logbook card displays entries from the logbook for specific entities.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_logbook.png' alt='Screenshot of the logbook card'>
|
||||
<img src='/images/dashboards/lovelace_logbook.png' alt='Screenshot of the logbook card'>
|
||||
Screenshot of the Logbook card.
|
||||
</p>
|
||||
|
@ -8,7 +8,7 @@ description: "The Map card that allows you to display entities on a map"
|
||||
The Map card that allows you to display entities on a map
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_map_card.png' alt='Screenshot of the map card'>
|
||||
<img src='/images/dashboards/lovelace_map_card.png' alt='Screenshot of the map card'>
|
||||
Screenshot of the map card.
|
||||
</p>
|
||||
|
@ -10,7 +10,7 @@ The Markdown card is used to render [Markdown](https://commonmark.org/help/).
|
||||
The renderer uses [Marked.js](https://marked.js.org), which supports [several specifications of Markdown](https://marked.js.org/#specifications), including CommonMark, GitHub Flavored Markdown (GFM) and `markdown.pl`.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_markdown.png' alt='Screenshot of the markdown card'>
|
||||
<img src='/images/dashboards/lovelace_markdown.png' alt='Screenshot of the markdown card'>
|
||||
Screenshot of the Markdown card.
|
||||
</p>
|
||||
|
||||
@ -53,7 +53,7 @@ The card can also be configured using YAML, some examples below:
|
||||
```yaml
|
||||
type: markdown
|
||||
content: >
|
||||
## Lovelace
|
||||
## Dashboards
|
||||
|
||||
Starting with Home Assistant 0.72, we're experimenting with a new way of defining your interface.
|
||||
```
|
@ -8,7 +8,7 @@ description: "The Media Control card is used to display media player entities on
|
||||
The Media Control card is used to display [Media Player](/integrations/#media-player) entities on an interface with easy to use controls.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_mediaplayer.png' alt='Screenshot of the media player control card'>
|
||||
<img src='/images/dashboards/lovelace_mediaplayer.png' alt='Screenshot of the media player control card'>
|
||||
Screenshot of the Media Control card.
|
||||
</p>
|
||||
|
@ -7,10 +7,10 @@ description: "The Picture Elements card is one of the most versatile types of ca
|
||||
|
||||
The Picture Elements card is one of the most versatile types of cards.
|
||||
|
||||
The cards allow you to position icons or text and even services on an image based on coordinates. Imagine floor plan, imagine [picture-glance](/lovelace/picture-glance/) with no restrictions!
|
||||
The cards allow you to position icons or text and even services on an image based on coordinates. Imagine floor plan, imagine [picture-glance](/dashboards/picture-glance/) with no restrictions!
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_picture_elements.gif' alt='A functional floorplan powered by picture elements'>
|
||||
<img src='/images/dashboards/lovelace_picture_elements.gif' alt='A functional floorplan powered by picture elements'>
|
||||
A functional floorplan powered by picture elements.
|
||||
</p>
|
||||
|
||||
@ -97,15 +97,15 @@ title:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -172,15 +172,15 @@ tap_action:
|
||||
default: "false"
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
style:
|
||||
required: true
|
||||
@ -220,15 +220,15 @@ title:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
style:
|
||||
required: true
|
||||
@ -288,15 +288,15 @@ entity:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
style:
|
||||
required: true
|
||||
@ -324,15 +324,15 @@ title:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
image:
|
||||
required: false
|
@ -8,7 +8,7 @@ description: The Picture Entity card displays an entity in the form of an image.
|
||||
The Picture Entity card displays an entity in the form of an image. Instead of images from URL, it can also show the picture of `camera` entities.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_picture_entity.gif' alt='Picture entity card'>
|
||||
<img src='/images/dashboards/lovelace_picture_entity.gif' alt='Picture entity card'>
|
||||
Background changes according to the entity state.
|
||||
</p>
|
||||
|
||||
@ -66,15 +66,15 @@ theme:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
@ -8,7 +8,7 @@ description: "The Picture Glance card shows an image and corresponding entity st
|
||||
The Picture Glance card shows an image and corresponding entity states as an icon. The entities on the right side allow toggle actions, others show the more information dialog.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_picture_glance.gif' alt='Picture glance card for a living room'>
|
||||
<img src='/images/dashboards/lovelace_picture_glance.gif' alt='Picture glance card for a living room'>
|
||||
Picture glance card for a living room.
|
||||
</p>
|
||||
|
||||
@ -70,15 +70,15 @@ theme:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -114,15 +114,15 @@ show_state:
|
||||
default: true
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
@ -8,7 +8,7 @@ description: "The Picture card allows you to set an image to use for navigation
|
||||
The Picture card allows you to set an image to use for navigation to various paths in your interface or to call a service.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_picture.png' alt='Screenshot of the picture card'>
|
||||
<img src='/images/dashboards/lovelace_picture.png' alt='Screenshot of the picture card'>
|
||||
Screenshot of the picture card.
|
||||
</p>
|
||||
|
||||
@ -27,15 +27,15 @@ theme:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action taken on card tap and hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action taken on card double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -60,7 +60,7 @@ tap_action:
|
||||
navigation_path: /lovelace/home
|
||||
```
|
||||
|
||||
Check the [views](/lovelace/views/) setup on how to setup custom IDs.
|
||||
Check the [views](/dashboards/views/) setup on how to setup custom IDs.
|
||||
|
||||
Toggle entity using a service:
|
||||
|
@ -8,7 +8,7 @@ description: "The Plant Status card is for all the lovely botanists out there."
|
||||
The Plant Status card is for all the lovely botanists out there.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_plant_card.png' alt='Screenshot of the plant status card'>
|
||||
<img src='/images/dashboards/lovelace_plant_card.png' alt='Screenshot of the plant status card'>
|
||||
Screenshot of the plant status card.
|
||||
</p>
|
||||
|
@ -8,7 +8,7 @@ description: "The Sensor card gives you a quick overview of your sensors state w
|
||||
The Sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_sensor.png' alt='Screenshot of the sensor card'>
|
||||
<img src='/images/dashboards/lovelace_sensor.png' alt='Screenshot of the sensor card'>
|
||||
Screenshot of the sensor card.
|
||||
</p>
|
||||
|
@ -10,7 +10,7 @@ The Shopping List card allows you to add, edit, check-off, and clear items from
|
||||
Setup of the [Shopping List integration](/integrations/shopping_list/) is required.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_shopping_list_card.gif' alt='Screenshot of the shopping list card'>
|
||||
<img src='/images/dashboards/lovelace_shopping_list_card.gif' alt='Screenshot of the shopping list card'>
|
||||
Screenshot of the Shopping List card.
|
||||
</p>
|
||||
|
@ -12,12 +12,12 @@ Statistics are gathered every hour for sensors that support it. It will either k
|
||||
If your sensor doesn't work with statistics, check [this](/more-info/statistics/).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_statistics_graph_line.png' alt='Screenshot of the statistics graph card for power entities'>
|
||||
<img src='/images/dashboards/lovelace_statistics_graph_line.png' alt='Screenshot of the statistics graph card for power entities'>
|
||||
Screenshot of the Statistics Graph card with none metered entities and `chart_type` `line`.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_statistics_graph_bar.png' alt='Screenshot of the statistics graph card for energy entities'>
|
||||
<img src='/images/dashboards/lovelace_statistics_graph_bar.png' alt='Screenshot of the statistics graph card for energy entities'>
|
||||
Screenshot of the Statistics Graph card with a metered entity and `chart_type` `bar`.
|
||||
</p>
|
||||
|
@ -8,7 +8,7 @@ description: "The Thermostat card gives control of your climate entity, allowing
|
||||
The Thermostat card gives control of your [climate](/integrations/#climate) entity, allowing you to change the temperature and mode of the entity.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_thermostat_card.gif' alt='Screenshot of the thermostat card'>
|
||||
<img src='/images/dashboards/lovelace_thermostat_card.gif' alt='Screenshot of the thermostat card'>
|
||||
Screenshot of the Thermostat card.
|
||||
</p>
|
||||
|
@ -43,7 +43,7 @@ cards:
|
||||
```
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/lovelace/lovelace_vertical-stack.png" alt="Picture- and entities-card in a stack">
|
||||
<img src="/images/dashboards/lovelace_vertical-stack.png" alt="Picture- and entities-card in a stack">
|
||||
Picture and entities-card in a stack.
|
||||
</p>
|
||||
|
||||
@ -66,6 +66,6 @@ cards:
|
||||
```
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/lovelace/lovelace_vertical-horizontal-stack.png" alt="Create a grid layout using vertical and horizontal stack">
|
||||
<img src="/images/dashboards/lovelace_vertical-horizontal-stack.png" alt="Create a grid layout using vertical and horizontal stack">
|
||||
Create a grid layout using vertical and horizontal stack.
|
||||
</p>
|
@ -8,7 +8,7 @@ description: "The Weather Forecast card displays the weather. Very useful to inc
|
||||
The Weather Forecast card displays the weather. Very useful to include on interfaces that people display on the wall.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_weather.png' alt='Screenshot of the weather card'>
|
||||
<img src='/images/dashboards/lovelace_weather.png' alt='Screenshot of the weather card'>
|
||||
Screenshot of the Weather card.
|
||||
</p>
|
||||
|
||||
@ -71,15 +71,15 @@ theme:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: The action taken on card tap. For more information, see the [action documentation](/lovelace/actions/#tap-action).
|
||||
description: The action taken on card tap. For more information, see the [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: The action taken on card tap and hold. For more information, see the [action documentation](/lovelace/actions/#hold-action).
|
||||
description: The action taken on card tap and hold. For more information, see the [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: The action taken on card double-tap. For more information, see the [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: The action taken on card double-tap. For more information, see the [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
@ -45,7 +45,7 @@
|
||||
- topic: Integration
|
||||
description: "[Integrations](/integrations/) connect and integrates Home Assistant with devices, services, and more. Such an integration contains all the logic that takes care of vendor- and device-specific implementations such as authentication or special protocols and brings those into Home Assistant in a standardized way. For example, the [Hue](/integrations/hue) integration integrates the Philips Hue bridge and its connected bulbs into Home Assistant, making them available as Home Assistant light entities you can control."
|
||||
- topic: Lovelace
|
||||
description: "[Lovelace](/lovelace/) is the name of the current frontend."
|
||||
description: "Lovelace is the original code name of the UI that is now known as [Home Assistant dashboards](/dashboards)."
|
||||
- topic: Light
|
||||
description: "A [light](/integrations/light) has a brightness you can control, and optionally color temperature or RGB color control."
|
||||
- topic: Notification
|
||||
|
@ -3,7 +3,7 @@ title: "Service Calls"
|
||||
description: "Instructions on how to call services in Home Assistant."
|
||||
---
|
||||
|
||||
Various integrations allow calling services when a certain event occurs. The most common one is calling a service when an automation trigger happens. But a service can also be called from a script, a Lovelace dashboard or via voice command devices such as Amazon Echo.
|
||||
Various integrations allow calling services when a certain event occurs. The most common one is calling a service when an automation trigger happens. But a service can also be called from a script, a dashboard or via voice command devices such as Amazon Echo.
|
||||
|
||||
The configuration options to call a configuration are the same between all integrations and are described on this page.
|
||||
|
||||
|
@ -1,21 +1,21 @@
|
||||
<section class="aside-module grid__item one-whole lap-one-half">
|
||||
{% assign elements = site.lovelace | sort_natural: 'title' %}
|
||||
{% assign elements = site.dashboards | sort_natural: 'title' %}
|
||||
|
||||
<div class="section">
|
||||
<h1 class="title delta">Lovelace UI</h1>
|
||||
<h1 class="title delta">Dashboards</h1>
|
||||
<ul class="divided sidebar-menu">
|
||||
<li>{% active_link /lovelace/ Introduction %}</li>
|
||||
<li>{% active_link /dashboards/ Introduction %}</li>
|
||||
<li>
|
||||
{% active_link /lovelace/dashboards/ Dashboards %}
|
||||
{% active_link /dashboards/dashboards/ Multiple Dashboards %}
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /lovelace/views/ Views %}
|
||||
{% active_link /dashboards/views/ Views %}
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /lovelace/cards/ Cards %}
|
||||
{% active_link /dashboards/cards/ Cards %}
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /lovelace/badges/ Badges %}
|
||||
{% active_link /dashboards/badges/ Badges %}
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
@ -45,8 +45,8 @@
|
||||
<div class="section">
|
||||
<h1 class="title delta">Advanced</h1>
|
||||
<ul class="divided sidebar-menu">
|
||||
<li>{% active_link /lovelace/header-footer/ Headers & Footers %}</li>
|
||||
<li>{% active_link /lovelace/actions/ Actions %}</li>
|
||||
<li>{% active_link /dashboards/header-footer/ Headers & Footers %}</li>
|
||||
<li>{% active_link /dashboards/actions/ Actions %}</li>
|
||||
<li>
|
||||
<a
|
||||
href="https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card.html"
|
@ -125,7 +125,7 @@
|
||||
{% active_link /docs/frontend/browsers/ Browser Compatibility List
|
||||
%}
|
||||
</li>
|
||||
<li>{% active_link /lovelace Lovelace UI %}</li>
|
||||
<li>{% active_link /dashboards Dashboards %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
|
@ -39,7 +39,7 @@
|
||||
<a href="/docs/scripts/">Scripting</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="/lovelace/">User Interface</a>
|
||||
<a href="/dashboards/">Dashboards</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
@ -7,8 +7,8 @@
|
||||
{% include asides/installation_navigation.html %}
|
||||
{% elsif root == 'common-tasks' %}
|
||||
{% include asides/common_tasks_navigation.html %}
|
||||
{% elsif root == 'lovelace' %}
|
||||
{% include asides/lovelace_navigation.html %}
|
||||
{% elsif root == 'dashboards' %}
|
||||
{% include asides/dashboards_navigation.html %}
|
||||
{% elsif root == 'developers' or root == 'help' %}
|
||||
{% include asides/help_navigation.html %}
|
||||
{% elsif root == 'getting-started' %}
|
||||
|
@ -12,7 +12,7 @@ ha_codeowners:
|
||||
ha_domain: almond
|
||||
---
|
||||
|
||||
[Almond](https://almond.stanford.edu/) is an open, privacy-preserving virtual assistant by [Stanford Open Virtual Assistant Lab](https://oval.cs.stanford.edu/). It allows you, among other things, to control Home Assistant using natural language. Once installed, it will be available on Lovelace via the microphone icon in the top right.
|
||||
[Almond](https://almond.stanford.edu/) is an open, privacy-preserving virtual assistant by [Stanford Open Virtual Assistant Lab](https://oval.cs.stanford.edu/). It allows you, among other things, to control Home Assistant using natural language. Once installed, it will be available in the user interface via the microphone icon in the top right.
|
||||
|
||||
Almond consists of three parts:
|
||||
|
||||
|
@ -27,7 +27,7 @@ or using an [input boolean helper](/integrations/input_boolean),
|
||||
### Device Class
|
||||
|
||||
Knowing a sensor is binary impacts how the sensor's current state may be
|
||||
represented in Home Assistant's UI (see [Lovelace](/lovelace/)). Opposing states
|
||||
represented in Home Assistant's UI (see [Dashboards](/dashboards/)). Opposing states
|
||||
may be given different icons, colors, and value labels to highlight a particular
|
||||
state over the other. This is set by the binary sensor's device class.
|
||||
|
||||
|
@ -32,7 +32,7 @@ Ignore CEC:
|
||||
|
||||
## Home Assistant Cast
|
||||
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url`, typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/dashboards/entities/#cast) to your dashboards, or by calling the `cast.show_lovelace_view` service. The service takes the path of a dashboard view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your dashboard's YAML for each view, as outlined in the [views documentation](/dashboards/views/#path). The `dashboard_path` is the part of the dashboard URL that follows the defined `base_url`, typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
|
||||
```yaml
|
||||
cast_downstairs_on_kitchen:
|
||||
|
@ -73,6 +73,6 @@ sensor:
|
||||
number_of_departures: 20
|
||||
```
|
||||
|
||||
## Custom Lovelace card
|
||||
## Custom dashboard card
|
||||
|
||||
Works best with the following custom Lovelace card: <https://github.com/bollewolle/delijn-card>
|
||||
Works best with the following custom dashboard card: <https://github.com/bollewolle/delijn-card>
|
||||
|
@ -16,7 +16,7 @@ ha_platforms:
|
||||
|
||||
The `filter` platform enables sensors that process the states of other entities.
|
||||
|
||||
`filter` applies a signal processing algorithm to a sensor, previous and current states, and generates a `new state` given the chosen algorithm. The next image depicts an original sensor and the filter sensor of that same sensor using the [History Graph](/lovelace/history-graph/) component.
|
||||
`filter` applies a signal processing algorithm to a sensor, previous and current states, and generates a `new state` given the chosen algorithm. The next image depicts an original sensor and the filter sensor of that same sensor using the [History Graph](/dashboards/history-graph/) component.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/filter-sensor.png' />
|
||||
|
@ -164,7 +164,7 @@ automation:
|
||||
```
|
||||
|
||||
|
||||
### Example Lovelace Dashboard
|
||||
### Example Dashboard
|
||||
|
||||
```yaml
|
||||
panel: true
|
||||
|
@ -52,7 +52,7 @@ state:
|
||||
required: true
|
||||
type: [list, string]
|
||||
name:
|
||||
description: Name displayed on the frontend. Note that it is used by Home Assistant to generate sensor's `object_id` so it is advisable to choose a unique one and change name for frontend using [customization](/docs/configuration/customizing-devices/#friendly_name) or via [Lovelace](/lovelace/entities/#name).
|
||||
description: Name displayed on the frontend. Note that it is used by Home Assistant to generate sensor's `object_id` so it is advisable to choose a unique one and change name for frontend using [customization](/docs/configuration/customizing-devices/#friendly_name) or via [Dashboards](/dashboards/entities/#name).
|
||||
required: false
|
||||
default: unnamed statistics
|
||||
type: string
|
||||
|
@ -21,6 +21,6 @@ Devices that are currently at home won't show on the map.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/lovelace/map/).
|
||||
This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/dashboards/map/).
|
||||
|
||||
</div>
|
||||
|
@ -31,7 +31,7 @@ It displays the current weather along with a 5 days forecast and create sensors,
|
||||
|
||||
## Weather platform
|
||||
|
||||
To be used with the weather Lovelace card to access current condition, today and next four days forecast.
|
||||
To be used with the weather dashboard card to access current condition, today and next four days forecast.
|
||||
|
||||
The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
|
||||
|
||||
|
@ -296,9 +296,9 @@ of the "overlapping" cameras are queried. Use different root directories (in mot
|
||||
`File Storage -> Root Directory`) to ensure motionEye (and thus this integration) will
|
||||
correctly associate media with the camera from which that media was captured.
|
||||
|
||||
## Example Lovelace Card
|
||||
## Example Dashboard Card
|
||||
|
||||
A Lovelace card with icons that will call the `action` service to send action commands to motionEye.
|
||||
A dashboard card with icons that will call the `action` service to send action commands to motionEye.
|
||||
|
||||
```yaml
|
||||
- type: picture-glance
|
||||
|
@ -303,7 +303,7 @@ Additional Nest Temperature Sensors are not supported by the SDM API.
|
||||
Home Assistant supports all SDM API features. However, every Camera or Doorbell device has a different set of built-in capabilities. A Camera device has one of the following live stream types:
|
||||
|
||||
- **RTSP**: These devices have an HLS stream served by the Home Assistant Core. These cameras support server-side `camera` services like stream recording or image preview. See [Low Latency HLS](/integrations/stream#ll-hls) as a great option to enable to reduce stream latency.
|
||||
- **WebRTC**: These devices support direct browser to camera communication and a super low latency stream. A [Picture Glance Card](/lovelace/picture-glance/) can show the live stream in the grid with the *Camera View* set to `live` (not recommended for battery-powered cameras). `camera` services like stream recording are *not supported*.
|
||||
- **WebRTC**: These devices support direct browser to camera communication and a super low latency stream. A [Picture Glance Card](/dashboards/picture-glance/) can show the live stream in the grid with the *Camera View* set to `live` (not recommended for battery-powered cameras). `camera` services like stream recording are *not supported*.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
@ -66,6 +66,6 @@ panel_iframe:
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Do **not** create one that is named `lovelace` it will overwrite Lovelace causing it to never load.
|
||||
Do **not** create one that is named `lovelace` it will overwrite existing Dashboards, causing it to never load.
|
||||
|
||||
</div>
|
||||
|
@ -53,7 +53,7 @@ show_delivered:
|
||||
|
||||
## Examples
|
||||
|
||||
### Lovelace summary card
|
||||
### Dashboard summary card
|
||||
|
||||
Use the following templated Markdown card to list all packages in transit along with their status:
|
||||
|
||||
|
@ -12,7 +12,7 @@ ha_domain: shopping_list
|
||||
|
||||
The `shopping_list` integration allows you to keep track of shopping list items.
|
||||
|
||||
Your shopping list will be accessible from the sidebar, and you can optionally add the [Shopping List card](/lovelace/shopping-list/) to your Lovelace dashboard. With the [Conversation integration](/integrations/conversation/) you can add items to your shopping list using voice commands like "Add eggs to my shopping list."
|
||||
Your shopping list will be accessible from the sidebar, and you can optionally add the [Shopping List card](/dashboards/shopping-list/) to your dashboard. With the [Conversation integration](/integrations/conversation/) you can add items to your shopping list using voice commands like "Add eggs to my shopping list."
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
@ -19,4 +19,4 @@ system_health:
|
||||
|
||||
System Health integration data can be viewed at **Configuration** -> **Info**.
|
||||
|
||||
Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of Lovelace [Dashboards](/lovelace/dashboards/) and [Views](/lovelace/views/) you have, and more.
|
||||
Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Dashboards](/dashboards/dashboards/) and [Views](/dashboards/views/) you have, and more.
|
||||
|
@ -120,7 +120,7 @@ Stops a torrent.
|
||||
|
||||
### Attribute `torrent_info`
|
||||
|
||||
All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a [Markdown card](/lovelace/markdown/) to Lovelace with the following code:
|
||||
All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a [Markdown card](/dashboards/markdown/) to a dashboard with the following code:
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
@ -122,7 +122,7 @@ geo_location:
|
||||
```
|
||||
## Card Example
|
||||
|
||||
Assuming you configure this service using `feed_type: past_week_all_earthquakes`, you can create a corresponding map card in the Lovelace UI with the following card:
|
||||
Assuming you configure this service using `feed_type: past_week_all_earthquakes`, you can create a corresponding map card in a dashboard with the following card:
|
||||
```yaml
|
||||
type: map
|
||||
geo_location_sources:
|
||||
|
@ -104,5 +104,5 @@ In this example we are using the entity ID of a zone as the origin and the frien
|
||||
## Using the live map in an iFrame
|
||||
|
||||
If you plan to use [Waze's live map](https://developers.google.com/waze/iframe/)
|
||||
in Lovelace [iframe](/lovelace/iframe/) then use
|
||||
in a dashboard [iframe](/dashboards/iframe/) then use
|
||||
[https://embed.waze.com/iframe](https://embed.waze.com/iframe) and not the live map URL itself.
|
||||
|
@ -100,11 +100,11 @@ delay_sec: 0.1
|
||||
|
||||
### Picture Elements Card
|
||||
|
||||
Below is a picture elements card that can be added to Lovelace to provide an Xbox controller interface in your frontend. It utilizes the services detailed above. Replace `remote.xboxone_remote` and `media_player.xboxone` with the names of your entities and enjoy! Courtesy of [@SeanPM5](https://github.com/SeanPM5) and [@hunterjm](https://github.com/hunterjm).
|
||||
Below is a picture elements card that can be added to a dashboard to provide an Xbox controller interface in your frontend. It utilizes the services detailed above. Replace `remote.xboxone_remote` and `media_player.xboxone` with the names of your entities and enjoy! Courtesy of [@SeanPM5](https://github.com/SeanPM5) and [@hunterjm](https://github.com/hunterjm).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/integrations/xbox/xbox_picture_entity.png' alt='Screenshot showing Xbox Controller in Lovelace.'>
|
||||
Screenshot showing Xbox Controller in Lovelace.
|
||||
<img src='/images/integrations/xbox/xbox_picture_entity.png' alt='Screenshot showing Xbox Controller in a dashboard.'>
|
||||
Screenshot showing Xbox Controller in a dashboard.
|
||||
</p>
|
||||
|
||||
```yaml
|
||||
|
@ -1103,7 +1103,7 @@ remote:
|
||||
- pronto:pronto_hex:[optional_repeat]
|
||||
```
|
||||
|
||||
### Add command as entity button in Lovelace UI
|
||||
### Add command as entity button to a dashboard
|
||||
|
||||
```yaml
|
||||
type: entity-button
|
||||
|
@ -72,7 +72,7 @@ sensor:
|
||||
|
||||
## Options For Entities
|
||||
|
||||
You can configure view information about the next bus using Lovelace card.
|
||||
You can configure view information about the next bus using dashboard card.
|
||||
To enable displaying the relative time in your `default_view` add the following lines:
|
||||
|
||||
```yaml
|
||||
|
@ -17,7 +17,7 @@ In the meanwhile, we're also working hard on the new authentication system. A pr
|
||||
|
||||
This release also includes a TON of love for the new Lovelace UI. Yes, it's still experimental but daaang, it's already so awesome that you should probably just go ahead and try it out. Thanks to all the devs who have jumped on this: [@c727], [@ciotlosm] and [@jeradM].
|
||||
|
||||
We don't have time to go through all the changes in this release, but [@ciotlosm] has been keeping [a very detailed changelog](/lovelace/changelog/). I'll just leave this screenshot by [@arsaboo] of the new picture-elements card and [the Lovelace configuration](https://github.com/arsaboo/homeassistant-config/blob/master/ui-lovelace.yaml#L15-L158):
|
||||
We don't have time to go through all the changes in this release, but [@ciotlosm] has been keeping a very detailed changelog. I'll just leave this screenshot by [@arsaboo] of the new picture-elements card and [the Lovelace configuration](https://github.com/arsaboo/homeassistant-config/blob/master/ui-lovelace.yaml#L15-L158):
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2018-07-0.73/lovelace-elements.png' alt='Screenshot of a floorplan with sensor info and light/camera controls overlayed.'>
|
||||
|
@ -32,7 +32,7 @@ To try it out today, [read these instructions](https://developers.home-assistant
|
||||
|
||||
We keep seeing [great examples](https://twitter.com/home_assistant/status/1019579208622845953) of UIs built with Lovelace. Follow us on social media ([FB](https://www.facebook.com/homeassistantio/?ref=bookmarks), [Twitter](https://twitter.com/home_assistant)) where we will keep sharing great examples.
|
||||
|
||||
For the Lovelace changes in this release, check out the [changelog](/lovelace/changelog/). To help our development and design teams, we've also introduced a [Lovelace card gallery](https://www.awesome-ha.com/).
|
||||
To help our development and design teams, we've also introduced a [Lovelace card gallery](https://www.awesome-ha.com/).
|
||||
|
||||
Thanks to [@c727], [@jeradM] and [@ciotlosm] for leading this effort ❤️
|
||||
|
||||
|
@ -15,8 +15,8 @@ October 12, 2018. 12 days into Hacktoberfest and it's been busier than ever on t
|
||||
|
||||
Alright, new release, we got some cool stuff! Let's start with our [Lovelace UI](/lovelace). We have integrated into Lovelace UI some of the custom cards that our amazing community have built, making them easily accessible to all users. The cards are [Gauge][ll-gauge] and [Sensor][ll-sensor]:
|
||||
|
||||
[ll-gauge]: /lovelace/gauge/
|
||||
[ll-sensor]: /lovelace/sensor/
|
||||
[ll-gauge]: /dashboards/gauge/
|
||||
[ll-sensor]: /dashboards/sensor/
|
||||
|
||||
<img src='/images/blog/2018-10-release-80/lovelace-glance-sensor.png' alt='Screenshot of new Gauge and Sensor cards' style='border: 0;box-shadow: none;'>
|
||||
|
||||
|
@ -18,7 +18,7 @@ To go with the configuration entry support, MQTT also now also integrates with t
|
||||
Lovelace has another three new cards, the alarm panel, the button card, and the thermostat card:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_thermostat_card.gif' alt='Screenshot of the thermostat card'>
|
||||
<img src='/images/dashboards/lovelace_thermostat_card.gif' alt='Screenshot of the thermostat card'>
|
||||
Screenshot of the thermostat card.
|
||||
</p>
|
||||
|
||||
|
@ -45,9 +45,9 @@ If you are currently testing Lovelace, please read the notes thoroughly as a lot
|
||||
|
||||
So if you were using Lovelace before 0.84, you now have two options. Option one is to use the new storage mode and import your existing file. You can do this by opening the Lovelace UI and click on Configure UI, this will prompt you to change to storage mode. This will unlock a new option in the menu called "raw config editor". Open this and paste the content of your `ui-lovelace.yaml` file into it and click save. Note that YAML comments are not persisted and `!include`/`!secret` are not supported if in storage mode.
|
||||
|
||||
If you want to continue managing a YAML file, [check here how to enable the YAML mode](/lovelace/yaml-mode/). The file `ui-lovelace.yaml` will now follow the same options as `configuration.yaml`. This means that the Lovelace YAML config is now parsed with YAML 1.1 instead of YAML 1.2. Major change is that you need to make sure that you wrap `on` and `off` with quotes in your configs!
|
||||
If you want to continue managing a YAML file, [check here how to enable the YAML mode](/dashboards/yaml-mode/). The file `ui-lovelace.yaml` will now follow the same options as `configuration.yaml`. This means that the Lovelace YAML config is now parsed with YAML 1.1 instead of YAML 1.2. Major change is that you need to make sure that you wrap `on` and `off` with quotes in your configs!
|
||||
|
||||
We have also aligned the configuration of all the cards, causing breaking changes. Changes are especially focused around how we define actions for short and long presses. See [the docs](/lovelace/changelog/) for more info.
|
||||
We have also aligned the configuration of all the cards, causing breaking changes. Changes are especially focused around how we define actions for short and long presses. See [the docs](/dashboards/changelog/) for more info.
|
||||
|
||||
Editor UI is now further processed. You can manage your Lovelace UI without leaving your browser! It is possible to add, edit and delete views. It is possible to add, edit, move and delete cards, including custom cards!
|
||||
|
||||
|
@ -13,7 +13,7 @@ og_image: /images/blog/2019-01-lovelace/demo.png
|
||||
|
||||
Today we're happy to announce that our new Lovelace UI, which has been in beta for the last 8 months, is becoming the new default interface of [Home Assistant 0.86](/blog/2019/01/23/release-86/). With Lovelace we're taking a new approach to building user interfaces for Home Assistant. We're no longer storing the look and feel of your UI in your configuration.yaml, requiring restarts for changes. With Lovelace we're keeping the UI concerns in the UI<sup>1</sup>, unlocking a whole new set of features:
|
||||
|
||||
- [24 cards](/lovelace/alarm-panel/) to place and configure as you like.
|
||||
- [24 cards](/dashboards/alarm-panel/) to place and configure as you like.
|
||||
- UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards.
|
||||
- Fast. Using a static config allows us to build up the UI once.
|
||||
- Customizable.
|
||||
@ -30,9 +30,9 @@ In case you're reading this and want to give it a try right now: we've updated [
|
||||
|
||||
For a deep dive into all the new features, check out the [latest episode of the Home Assistant podcast](https://hasspodcast.io/ha042/), featuring an interview with [Zack Arnett][@zsarnett] from the Lovelace team.
|
||||
|
||||
For an overview of all the different features, check out the [Lovelace documentation](/lovelace/).
|
||||
For an overview of all the different features, check out the [Lovelace documentation](/dashboards/).
|
||||
|
||||
<sup>1</sup>: If you prefer to write your Lovelace config in YAML, Lovelace also includes an optional [YAML mode](/lovelace/yaml-mode/).
|
||||
<sup>1</sup>: If you prefer to write your Dashboard config in YAML, Home Assistant also includes an optional [YAML mode](/dashboards/yaml-mode/).
|
||||
|
||||
## Migrating to Lovelace
|
||||
|
||||
|
@ -45,7 +45,7 @@ Home Assistant Cast opens a whole new world of possibilities for using Lovelace,
|
||||
|
||||
This release contains a couple of notable UI changes:
|
||||
|
||||
- [New Cast row available](/lovelace/entities/#cast) in the Lovelace entities card to start Home Assistant Cast.
|
||||
- [New Cast row available](/dashboards/entities/#cast) in the Lovelace entities card to start Home Assistant Cast.
|
||||
- Improved accessibility for visually impaired users. This is an [ongoing effort](https://github.com/home-assistant/home-assistant-polymer/issues/3267) on making the frontend accessible.
|
||||
- Split out `configuration.yaml` actions from the core configuration into a new server control config panel. Thanks [@IcyPalm]
|
||||
- Markdown card now has a size + 1, if it has a header defined. Some layouts might be moved around due to this.
|
||||
|
@ -141,7 +141,7 @@ So if you have a light named "Living room lights" that is in the area "Living ro
|
||||
- We added many accessibility features to Lovelace; you can navigate almost everything with the tab key.
|
||||
We will continue to work on this so that people with disabilities can also enjoy Home Assistant.
|
||||
|
||||
For a full list of changes, see the [Lovelace changelog](/lovelace/changelog/).
|
||||
For a full list of changes, see the Lovelace changelog.
|
||||
|
||||
Even more frontend improvements:
|
||||
|
||||
|
@ -69,7 +69,7 @@ admin users only.
|
||||
|
||||
An unlimited amount of dashboards can be created right from the UI in the new
|
||||
Lovelace configuration panel, and YAML dashboards can be set up in
|
||||
`configuration.yaml`, see [the documentation](/lovelace/yaml-mode/).
|
||||
`configuration.yaml`, see [the documentation](/dashboards/yaml-mode/).
|
||||
|
||||
This awesome new feature comes with a deprecation if you use Lovelace in
|
||||
manual YAML mode: You need to move the `resources` section from
|
||||
@ -176,14 +176,14 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
|
||||
- **Input Number** - Adds an entity ID to input_number warning. Passing an out of range value to `input_number.set_value` will now raise a validation error. Incrementing/decrementing an `input_number` will no longer cause warnings. - ([@balloob] - [#32012]) ([input_number docs])
|
||||
|
||||
- **History Graph** - The `history_graph` integration has been deprecated in Home Assistant 0.105 and is now removed. This integration was used for the old states UI, which is no longer available. A Lovelace an equivalent is available: [The Lovelace History Graph](/lovelace/history-graph/). ([@frenck] - [#32028])
|
||||
- **History Graph** - The `history_graph` integration has been deprecated in Home Assistant 0.105 and is now removed. This integration was used for the old states UI, which is no longer available. A Lovelace an equivalent is available: [The Lovelace History Graph](/dashboards/history-graph/). ([@frenck] - [#32028])
|
||||
|
||||
- **Weblink** - The `weblink` integration is was deprecated in 0.105.0 and now removed. This integration only works with the old states UI, which is no longer available. ([@frenck] - [#32024])
|
||||
|
||||
With Lovelace, the same can be achieved using:
|
||||
|
||||
- [The Lovelace Markdown card](/lovelace/markdown/)
|
||||
- [The Lovelace Entities card](/lovelace/entities/#weblink)
|
||||
- [The Lovelace Markdown card](/dashboards/markdown/)
|
||||
- [The Lovelace Entities card](/dashboards/entities/#weblink)
|
||||
|
||||
- **Environment Canada** - This integration was previously using web scraping for weather alert details. The details attribute has been removed to make it compliant. (ADR-0004) - ([@michaeldavie] - [#32077]) ([environment_canada docs])
|
||||
|
||||
|
@ -148,7 +148,7 @@ You can also set the attribute you want to show as the secondary information.
|
||||
Screenshot of the updated weather card.
|
||||
</p>
|
||||
|
||||
Check the [documentation](/lovelace/weather-forecast/) for more information.
|
||||
Check the [documentation](/dashboards/weather-forecast/) for more information.
|
||||
|
||||
## Internal & External URLs
|
||||
|
||||
|
@ -93,7 +93,7 @@ We have also been hard at working making improvements in other areas of the app:
|
||||
|
||||
* There are now 2 [widgets](https://companion.home-assistant.io/docs/integrations/android-widgets) that you can set up, with Entity State being the latest addition. The Entity State widget will display the state and any attribute of the selected entity. It will update once every 30 minutes or when tapped. The Service Call widget was also enhanced to allow you to select from a list of valid and available services along with the ability to add additional data fields that the service may require.
|
||||
* In App Configuration the Home Network WiFi SSID option now allows the user to select multiple SSIDs.
|
||||
* A Cookie Manager was added to our WebView that will allow you to save cookies from sites that you may use in the [webpage card](/lovelace/iframe/).
|
||||
* A Cookie Manager was added to our WebView that will allow you to save cookies from sites that you may use in the [webpage card](/dashboards/iframe/).
|
||||
* More descriptive SSL error messages were added to help users resolve local issues they may encounter while setting up the app.
|
||||
* Device ID is now sent with the event data for actionable notifications.
|
||||
|
||||
|
@ -37,7 +37,7 @@ Screenshot of Sensor Search & Filter.
|
||||
|
||||
## Shortcuts
|
||||
|
||||
Sometimes when you open the app you may already know exactly where you want to go. You may find yourself on the same view often to see your cameras or give the nursery a quick look to make sure things are ok. You may even want to quickly see the history of an entity like when the door was last opened. In this release, we have introduced [Android Shortcuts](https://developer.android.com/guide/topics/ui/shortcuts) which will let you get to anywhere in the Home Assistant frontend quickly, directly from your home screen. Shortcuts will look like a separate app on the home screen allowing you to make them easily accessible and even place them into a folder for better organization. You can navigate to any Lovelace [view or dashboard](/lovelace/dashboards-and-views/) including other pages like the [Shopping List](/integrations/shopping_list/). You can also navigate to any entity directly to get more information like the history or see the graph.
|
||||
Sometimes when you open the app you may already know exactly where you want to go. You may find yourself on the same view often to see your cameras or give the nursery a quick look to make sure things are ok. You may even want to quickly see the history of an entity like when the door was last opened. In this release, we have introduced [Android Shortcuts](https://developer.android.com/guide/topics/ui/shortcuts) which will let you get to anywhere in the Home Assistant frontend quickly, directly from your home screen. Shortcuts will look like a separate app on the home screen allowing you to make them easily accessible and even place them into a folder for better organization. You can navigate to any Lovelace [view or dashboard](/dashboards/dashboards-and-views/) including other pages like the [Shopping List](/integrations/shopping_list/). You can also navigate to any entity directly to get more information like the history or see the graph.
|
||||
|
||||
There are a few different shortcut types and in the nature of Home Assistant, we have opted not to add static shortcuts because they are static! We support dynamic shortcuts which will show up under the app long-press menu. Once you create a shortcut, you will be able to drag it onto your home screen. There is also support for pinned shortcuts that can be added automatically to your home screen without needing to drag the icon, given your device and launcher support pinned shortcuts. Check out the [documentation](https://companion.home-assistant.io/docs/integrations/android-shortcuts) for more details including known limitations.
|
||||
|
||||
|
@ -110,9 +110,9 @@ If you're interested in helping out, don't hesitate to stop by the new #devs_ene
|
||||
|
||||
### New possibilities for advanced users
|
||||
|
||||
Every home is different and so are the needs of individual users. The energy management feature in Home Assistant is created with existing Home Assistant building blocks: Lovelace & Data storage. This means that our advanced users can choose to build up their own dashboards and use [the pieces from the energy dashboard](/lovelace/energy/) that they like.
|
||||
Every home is different and so are the needs of individual users. The energy management feature in Home Assistant is created with existing Home Assistant building blocks: Lovelace & Data storage. This means that our advanced users can choose to build up their own dashboards and use [the pieces from the energy dashboard](/dashboards/energy/) that they like.
|
||||
|
||||
On top of that, advanced users will have access to the new [long-term statistics](/lovelace/statistics-graph/) that have been added to Home Assistant. This data allows you to easily monitor most sensor data over long periods of time, not just energy data.
|
||||
On top of that, advanced users will have access to the new [long-term statistics](/dashboards/statistics-graph/) that have been added to Home Assistant. This data allows you to easily monitor most sensor data over long periods of time, not just energy data.
|
||||
|
||||
### Thank you community
|
||||
|
||||
|
@ -121,7 +121,7 @@ Every hour, we calculate things like mean, min/max values, or the difference
|
||||
created that hour and store just that result in our long-term statistics.
|
||||
|
||||
These statistics is what partly powers the new Energy dashboard, however,
|
||||
they can be used for anything else: Introducing the Lovelace [statistics graph card](/lovelace/statistics-graph/).
|
||||
they can be used for anything else: Introducing the Lovelace [statistics graph card](/dashboards/statistics-graph/).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-08/statistics-graph.png' alt='Screenshot of the new Lovelace statistics graph card'>
|
||||
@ -170,7 +170,7 @@ Screenshot of the Gauge card in needle mode with severity configured.
|
||||
</p>
|
||||
|
||||
These settings are available straight from the Lovelace UI editor; More
|
||||
information and examples can be found in the [Gauge card documentation](/lovelace/gauge/).
|
||||
information and examples can be found in the [Gauge card documentation](/dashboards/gauge/).
|
||||
|
||||
## Currency core setting
|
||||
|
||||
|
@ -205,7 +205,7 @@ Click the My button below to test it out on your Home Assistant instance:
|
||||
{% my developer_template badge %}
|
||||
|
||||
[@kubawolanin]: https://github.com/kubawolanin
|
||||
[Lovelace cards]: /lovelace/cards
|
||||
[Lovelace cards]: /dashboards/cards
|
||||
[Tim Cowell]: https://github.com/tgcowell
|
||||
[Waves]: https://github.com/tgcowell/waves
|
||||
|
||||
|
@ -1060,7 +1060,7 @@
|
||||
/integrations/cover.modbus /integrations/modbus
|
||||
/integrations/fan.xiaomi_miio /integrations/xiaomi_miio
|
||||
/integrations/light.xiaomi_miio /integrations/xiaomi_miio
|
||||
/integrations/lovelace /lovelace
|
||||
/integrations/lovelace /dashboards
|
||||
/integrations/remote.xiaomi_miio /integrations/xiaomi_miio
|
||||
/integrations/sensor.websocket_api /integrations/websocket_api
|
||||
/integrations/sensor.modbus /integrations/modbus
|
||||
@ -2182,11 +2182,14 @@
|
||||
/tag/* /tag 200
|
||||
|
||||
# Lovelace documentation
|
||||
/lovelace/entity-button /lovelace/button
|
||||
/lovelace/views /lovelace/dashboards-and-views
|
||||
/lovelace/yaml-mode /lovelace/dashboards-and-views
|
||||
/lovelace/calendar-card /lovelace/calendar
|
||||
/integrations/lovelace /lovelace
|
||||
/lovelace/entity-button /dashboards/button
|
||||
/lovelace/views /dashboards/dashboards-and-views
|
||||
/lovelace/yaml-mode /dashboards/dashboards-and-views
|
||||
/lovelace/calendar-card /dashboards/calendar
|
||||
/integrations/lovelace /dashboards
|
||||
/lovelace/* /dashboards/:splat
|
||||
/images/lovelace/* /images/dashboards/:splat
|
||||
|
||||
|
||||
# Removed documentation
|
||||
/docs/installation /getting-started
|
||||
|
@ -7,14 +7,14 @@ Some cards have support for tap actions. These actions define what will happen w
|
||||
|
||||
Actions can be enabled on:
|
||||
|
||||
- [Button](/lovelace/button/)
|
||||
- [Entities](/lovelace/entities/)
|
||||
- [Glance](/lovelace/glance/)
|
||||
- [Light](/lovelace/light/)
|
||||
- [Picture](/lovelace/picture/)
|
||||
- [Picture Element](/lovelace/picture-elements/)
|
||||
- [Picture Entity](/lovelace/picture-entity/)
|
||||
- [Picture Glance](/lovelace/picture-glance/)
|
||||
- [Button](/dashboards/button/)
|
||||
- [Entities](/dashboards/entities/)
|
||||
- [Glance](/dashboards/glance/)
|
||||
- [Light](/dashboards/light/)
|
||||
- [Picture](/dashboards/picture/)
|
||||
- [Picture Element](/dashboards/picture-elements/)
|
||||
- [Picture Entity](/dashboards/picture-entity/)
|
||||
- [Picture Glance](/dashboards/picture-glance/)
|
||||
|
||||
## Tap-Action
|
||||
|
@ -7,7 +7,7 @@ Badges are widgets that sit at the top of a panel, above all the cards.
|
||||
|
||||
## State Label Badge
|
||||
|
||||
The State Label badge allows you to display a state badge. This badge supports [actions](/lovelace/actions/).
|
||||
The State Label badge allows you to display a state badge. This badge supports [actions](/dashboards/actions/).
|
||||
|
||||
```yaml
|
||||
type: state-label
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Dashboards"
|
||||
description: "A powerful and configurable interface for Home Assistant."
|
||||
title: "Multiple Dashboards"
|
||||
description: "Multiple powerful and configurable dashboards in Home Assistant."
|
||||
---
|
||||
|
||||
You can define multiple dashboards in Home Assistant. Each dashboard can be added to the sidebar. This makes it possible to create separate control dashboards for each individual part of your house.
|
||||
@ -70,10 +70,10 @@ lovelace:
|
||||
title: YAML
|
||||
icon: mdi:script
|
||||
show_in_sidebar: true
|
||||
filename: lovelace.yaml
|
||||
filename: dashboards.yaml
|
||||
```
|
||||
|
||||
{% configuration Lovelace %}
|
||||
{% configuration dashboards %}
|
||||
mode:
|
||||
required: true
|
||||
description: "In what mode should the main dashboard be, `yaml` or `storage` (UI managed)."
|
@ -5,7 +5,7 @@ description: "Decorate your dashboard cards with header and footer widgets."
|
||||
|
||||
Some dashboard cards have support for header and footer widgets. These widgets fill up the whole available space in a card.
|
||||
|
||||
<p class='img'><img src='/images/lovelace/header-footer/screenshot-picture-buttons.png' alt="Screenshot of an entities card with a picture header.">
|
||||
<p class='img'><img src='/images/dashboards/header-footer/screenshot-picture-buttons.png' alt="Screenshot of an entities card with a picture header.">
|
||||
Screenshot of an entities card with a picture header and buttons footer.
|
||||
</p>
|
||||
|
||||
@ -16,7 +16,7 @@ Widget to show a picture as a header or a footer. A picture can have touch actio
|
||||
```yaml
|
||||
header:
|
||||
type: picture
|
||||
image: "https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png"
|
||||
image: "https://www.home-assistant.io/images/dashboards/header-footer/balloons-header.png"
|
||||
```
|
||||
|
||||
{% configuration header-footer %}
|
||||
@ -30,15 +30,15 @@ image:
|
||||
type: string
|
||||
tap_action:
|
||||
required: false
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: Action to take on tap-and-hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
description: Action to take on tap-and-hold. See [action documentation](/dashboards/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action to take on double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action to take on double tap. See [action documentation](/dashboards/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -85,7 +85,7 @@ entities:
|
||||
|
||||
Widget to show an entity in the sensor domain as a graph in the header or footer.
|
||||
|
||||
<p class='img'><img src='/images/lovelace/header-footer/graph.png' alt="Screenshot of an entities card with a graph footer.">
|
||||
<p class='img'><img src='/images/dashboards/header-footer/graph.png' alt="Screenshot of an entities card with a graph footer.">
|
||||
Screenshot of an entities card with a graph footer.
|
||||
</p>
|
||||
|
@ -1,9 +1,9 @@
|
||||
---
|
||||
title: "Dashboard"
|
||||
description: "A powerful and configurable dashboard for Home Assistant."
|
||||
title: "Dashboards"
|
||||
description: "Powerful and configurable dashboards for Home Assistant."
|
||||
---
|
||||
|
||||
The Home Assistant dashboard is a fast, customizable and powerful way for users to manage their home using their mobiles and desktops.
|
||||
Home Assistant dashboards are a fast, customizable and powerful way for users to manage their home using their mobiles and desktops.
|
||||
|
||||
- 29 different cards to place and configure as you like.
|
||||
- Dashboard Editor: Allows you to manage your dashboard by including a live preview when editing cards.
|
@ -10,7 +10,7 @@ You can add a view to your user interface, by clicking the menu (three dots at t
|
||||
Click the `+` button in the top menu bar.
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/lovelace/lovelace_views.png" alt="Views toolbar">
|
||||
<img src="/images/dashboards/lovelace_views.png" alt="Views toolbar">
|
||||
Use titles and icons to describe the content of views.
|
||||
</p>
|
||||
|
||||
@ -86,7 +86,7 @@ user:
|
||||
|
||||
## Type
|
||||
|
||||
You can change the layout of a view by using a different view type. The default is [`masonry`](/lovelace/masonry).
|
||||
You can change the layout of a view by using a different view type. The default is [`masonry`](/dashboards/masonry).
|
||||
|
||||
#### Example
|
||||
|
@ -25,11 +25,11 @@ The documentation covers beginner to advanced topics around the installation, se
|
||||
</div>
|
||||
<div class='title'>MQTT</div>
|
||||
</a>
|
||||
<a class='option-card' href='/lovelace/'>
|
||||
<a class='option-card' href='/dashboards/'>
|
||||
<div class='img-container'>
|
||||
<img src='/images/supported_brands/view-dashboard.png' />
|
||||
</div>
|
||||
<div class='title'>User Interface</div>
|
||||
<div class='title'>Dashboards</div>
|
||||
</a>
|
||||
<a class='option-card' href='https://companion.home-assistant.io/'>
|
||||
<div class='img-container'>
|
||||
|
Before Width: | Height: | Size: 4.4 KiB After Width: | Height: | Size: 4.4 KiB |
Before Width: | Height: | Size: 1.4 KiB After Width: | Height: | Size: 1.4 KiB |
Before Width: | Height: | Size: 8.0 KiB After Width: | Height: | Size: 8.0 KiB |
Before Width: | Height: | Size: 8.1 KiB After Width: | Height: | Size: 8.1 KiB |
Before Width: | Height: | Size: 132 KiB After Width: | Height: | Size: 132 KiB |
Before Width: | Height: | Size: 4.1 KiB After Width: | Height: | Size: 4.1 KiB |
Before Width: | Height: | Size: 3.9 KiB After Width: | Height: | Size: 3.9 KiB |
Before Width: | Height: | Size: 7.0 KiB After Width: | Height: | Size: 7.0 KiB |
Before Width: | Height: | Size: 8.5 KiB After Width: | Height: | Size: 8.5 KiB |
Before Width: | Height: | Size: 6.9 KiB After Width: | Height: | Size: 6.9 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 5.7 KiB After Width: | Height: | Size: 5.7 KiB |