Screenshot of the button card with script service.
-
-## Related topics
-
-- [Card actions](/dashboards/actions/)
-- [Scripts](/docs/scripts/)
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/calendar.markdown b/source/_dashboards/calendar.markdown
index 3705e87e120..940a45c7fe6 100644
--- a/source/_dashboards/calendar.markdown
+++ b/source/_dashboards/calendar.markdown
@@ -3,6 +3,11 @@ type: card
title: "Calendar card"
sidebar_label: Calendar
description: "The calendar card displays your calendar entities in a month, day and list view"
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The calendar card displays your [calendar](/integrations/#calendar) {% term entities %} in a month, day, and list view (7 days).
@@ -52,8 +57,3 @@ entities:
- calendar.calendar_1
- calendar.calendar_2
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/conditional.markdown b/source/_dashboards/conditional.markdown
index 19b188730ba..ead8ea37a11 100644
--- a/source/_dashboards/conditional.markdown
+++ b/source/_dashboards/conditional.markdown
@@ -3,6 +3,9 @@ type: card
title: Conditional card
sidebar_label: Conditional
description: The Conditional card displays another card based on conditions.
+related:
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The conditional card displays another card based on conditions.
@@ -242,6 +245,3 @@ conditions:
{% endconfiguration %}
-## Related topics
-
-- [Dashboard cards](/dashboards/cards/)
diff --git a/source/_dashboards/energy.markdown b/source/_dashboards/energy.markdown
index f09f2a4fa3b..d0101d4d697 100644
--- a/source/_dashboards/energy.markdown
+++ b/source/_dashboards/energy.markdown
@@ -3,6 +3,11 @@ type: card
title: "Energy cards"
sidebar_label: Energy cards
description: "An overview of the energy cards that are available."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
This is a list of all the cards used in the energy dashboard. You can also place them anywhere you want in your dashboard.
@@ -229,8 +234,3 @@ The following example limits the number of shown devices to 5:
type: energy-devices-detail-graph
max_devices: 5
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/entities.markdown b/source/_dashboards/entities.markdown
index 9710311a591..98cc7056db5 100644
--- a/source/_dashboards/entities.markdown
+++ b/source/_dashboards/entities.markdown
@@ -3,6 +3,13 @@ type: card
title: "Entities card"
sidebar_label: Entities
description: "The entities card is the most common type of card. It groups items together into lists."
+related:
+ - docs: /dashboards/actions/
+ title: Card actions
+ - docs: /dashboards/header-footer/
+ title: Card header and footer
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The entities card is the most common type of card. It groups items together into lists. It can be used to display an entity's state or attribute, but also contain buttons, web links, etc.
@@ -456,9 +463,3 @@ entities:
text: Are you sure you want to restart?
service: script.libreelec_power_cycle
```
-
-## Related topics
-
-- [Card actions](/dashboards/actions/)
-- [Card header and footer](/dashboards/header-footer/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/entity.markdown b/source/_dashboards/entity.markdown
index 4fabc918093..12e77a61dac 100644
--- a/source/_dashboards/entity.markdown
+++ b/source/_dashboards/entity.markdown
@@ -3,6 +3,13 @@ type: card
title: "Entity card"
sidebar_label: Entity
description: "The entity card gives you a quick overview of your entity's state"
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/header-footer/
+ title: Card header and footer
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The entity card gives you a quick overview of your entity's state.
@@ -78,9 +85,3 @@ footer:
attribute: battery_level
unit: "%"
```
-
-## Related topics
-
-- [Card header and footer](/dashboards/header-footer/)
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/gauge.markdown b/source/_dashboards/gauge.markdown
index 6bacac009d5..8ede3f1de0a 100644
--- a/source/_dashboards/gauge.markdown
+++ b/source/_dashboards/gauge.markdown
@@ -3,6 +3,11 @@ type: card
title: "Gauge card"
sidebar_label: Gauge
description: "The gauge card is a basic card that allows visually seeing sensor data."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The gauge card is a basic card that allows visually seeing sensor data.
@@ -181,9 +186,3 @@ segments:
- from: 65
color: var(--error-color)
```
-
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/glance.markdown b/source/_dashboards/glance.markdown
index 10c5b911e7c..bdf2f0aa8c0 100644
--- a/source/_dashboards/glance.markdown
+++ b/source/_dashboards/glance.markdown
@@ -3,6 +3,13 @@ type: card
title: "Glance card"
sidebar_label: Glance
description: "The glance card is useful to group multiple sensors in a compact overview."
+related:
+ - docs: /dashboards/actions/
+ title: Card actions
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard 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.
@@ -157,9 +164,3 @@ entities:
tap_action:
action: toggle
```
-
-## Related topics
-
-- [Card actions](/dashboards/actions/)
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/grid.markdown b/source/_dashboards/grid.markdown
index b5a6229730b..706f93d0a13 100644
--- a/source/_dashboards/grid.markdown
+++ b/source/_dashboards/grid.markdown
@@ -3,6 +3,11 @@ type: card
title: "Grid card"
sidebar_label: Grid
description: "The grid card allows you to show multiple cards in a grid."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The grid card allows you to show multiple cards in a grid. It will first fill the columns, automatically adding new rows as needed.
@@ -80,8 +85,3 @@ cards:
entity: light.bed_light
image: /local/bed_2.png
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/history-graph.markdown b/source/_dashboards/history-graph.markdown
index df079a0d80b..1ab062ad138 100644
--- a/source/_dashboards/history-graph.markdown
+++ b/source/_dashboards/history-graph.markdown
@@ -3,6 +3,11 @@ type: card
title: "History graph card"
sidebar_label: History graph
description: "The history graph card allows you to display a graph for each of the entities listed."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The history graph card allows you to display a graph for each of up to eight entities.
@@ -107,8 +112,3 @@ entities:
- entity: sensor.attic_temperature
name: "Attic"
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/horizontal-stack.markdown b/source/_dashboards/horizontal-stack.markdown
index eddc32f69d2..ed211f7782d 100644
--- a/source/_dashboards/horizontal-stack.markdown
+++ b/source/_dashboards/horizontal-stack.markdown
@@ -3,6 +3,9 @@ type: card
title: "Horizontal stack card"
sidebar_label: Horizontal stack
description: "The horizontal stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column."
+related:
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The horizontal stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column.
@@ -46,7 +49,3 @@ cards:
Two picture cards in a horizontal stack card.
-
-## Related topics
-
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/humidifier.markdown b/source/_dashboards/humidifier.markdown
index 93b721febf9..759f74b357e 100644
--- a/source/_dashboards/humidifier.markdown
+++ b/source/_dashboards/humidifier.markdown
@@ -3,6 +3,11 @@ type: card
title: "Humidifier card"
sidebar_label: Humidifier
description: "The humidifier card gives control of your humidifier entity, allowing you to change the target humidity and mode of the entity."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The humidifier card lets you control and monitor humidifiers, dehumidifiers, and hygrostat devices.
@@ -57,7 +62,3 @@ entity: humidifier.bedroom
name: Bedroom Humidifier
```
-## Related topics
-
-- [Card features](/dashboards/features)
-- [Themes](/integrations/frontend/)
diff --git a/source/_dashboards/iframe.markdown b/source/_dashboards/iframe.markdown
index 1f70c3f70c2..b3d4df4d99d 100644
--- a/source/_dashboards/iframe.markdown
+++ b/source/_dashboards/iframe.markdown
@@ -3,10 +3,17 @@ type: card
title: "Webpage card"
sidebar_label: Webpage
description: "The webpage card allows you to embed your favorite webpage right into Home Assistant."
+related:
+ - docs: /dashboards/dashboards/#webpage-dashboard
+ title: Webpage dashboard
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The webpage card allows you to embed your favorite webpage right into Home Assistant. You can also embed files stored in your `
Windy weather radar as webpage.
@@ -16,6 +23,7 @@ The webpage card allows you to embed your favorite webpage right into Home Assis
All options for this card can be configured via the user interface.
+Note that not every webpage can be embedded due to security restrictions that some sites have in place. These restrictions are enforced by your browser and prevent embedding them into a Home Assistant dashboard.
Screenshot of the Light card names.
-
-## Related topics
-
-- [Card actions](/dashboards/actions/)
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/logbook.markdown b/source/_dashboards/logbook.markdown
index 2ae88343fac..8f86938ebd3 100644
--- a/source/_dashboards/logbook.markdown
+++ b/source/_dashboards/logbook.markdown
@@ -3,6 +3,11 @@ type: card
title: "Logbook card"
sidebar_label: Logbook
description: "The logbook card displays entries from the logbook for specific entities."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The logbook card displays entries from the logbook for specific entities.
@@ -65,8 +70,3 @@ entities:
- light.ceiling_lights
hours_to_show: 24
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/map.markdown b/source/_dashboards/map.markdown
index 3ee49dcb992..dbb024b2979 100644
--- a/source/_dashboards/map.markdown
+++ b/source/_dashboards/map.markdown
@@ -3,6 +3,13 @@ type: card
title: "Map card"
sidebar_label: Map
description: "The map card that allows you to display entities on a map"
+related:
+ - docs: /dashboards/dashboards/#map-dashboard
+ title: Map dashboard
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The map card that allows you to display entities on a map. This card is used on the [Map dashboard](/dashboards/dashboards/#map-dashboard), which is one of the default dashboards.
@@ -134,9 +141,3 @@ entities:
focus: false
hours_to_show: 48
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
-- [Map dashboard](/dashboards/dashboards/#map-dashboard)
\ No newline at end of file
diff --git a/source/_dashboards/markdown.markdown b/source/_dashboards/markdown.markdown
index bcac319e7c9..d6145a082b2 100644
--- a/source/_dashboards/markdown.markdown
+++ b/source/_dashboards/markdown.markdown
@@ -3,6 +3,11 @@ type: card
title: "Markdown card"
sidebar_label: Markdown
description: "The Markdown card is used to render Markdown"
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The Markdown card is used to render [Markdown](https://commonmark.org/help/).
@@ -140,8 +145,3 @@ content: |
button.
+5. To add a section, select the **Create section** button.
+6. To edit the section title, select the button.
- If you leave the section title empty, this line will be hidden.
-6. To delete a section, select the 
button.
+7. To delete a section, select the button.
## Rearranging sections and cards
@@ -68,12 +83,3 @@ type:
description: "`sections`"
type: string
{% endconfiguration %}
-
-## Related topics
-
-- [Masonry view](/dashboards/masonry/)
-- [Panel view](/dashboards/panel/)
-- [Sidebar view](/dashboards/sidebar/)
-- [Dashboard chapter 1 blog post](/blog/2024/03/04/dashboard-chapter-1/)
-- [Adding cards to a view](/dashboards/cards/#adding-cards-to-your-dashboard)
-- [Adding a new view](/dashboards/views/#adding-a-view-to-a-dashboard)
\ No newline at end of file
diff --git a/source/_dashboards/sensor.markdown b/source/_dashboards/sensor.markdown
index c4196828d7e..ae181701ce7 100644
--- a/source/_dashboards/sensor.markdown
+++ b/source/_dashboards/sensor.markdown
@@ -3,6 +3,11 @@ type: card
title: "Sensor card"
sidebar_label: Sensor
description: "The sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time.
@@ -83,8 +88,3 @@ type: sensor
entity: sensor.illumination
name: Illumination
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/shopping-list.markdown b/source/_dashboards/shopping-list.markdown
index b0a955f7a8c..fd4061f6838 100644
--- a/source/_dashboards/shopping-list.markdown
+++ b/source/_dashboards/shopping-list.markdown
@@ -1,6 +1,12 @@
---
title: "Shopping list card"
description: "The shopping list card allows you to add, edit, check-off, and clear items from your shopping list."
+description: "The panel view shows a single card in the full width of the screen."
+related:
+ - docs: /integrations/todo/
+ title: To-do list integration
+ - docs: /integrations/local_todo/
+ title: Local to-do integration
---
Note: the shopping list card is no longer available as a card to add from the user interface. Use the [to-do list card](/dashboards/todo-list/) instead.
@@ -45,8 +51,3 @@ Title example:
type: shopping-list
title: shopping list
```
-
-## Related topics
-
-- [To-do list integration](/integrations/todo)
-- [Local to-do integration](/integrations/local_todo/)
\ No newline at end of file
diff --git a/source/_dashboards/sidebar.markdown b/source/_dashboards/sidebar.markdown
index 3c55ccccd4a..47815a9e52d 100644
--- a/source/_dashboards/sidebar.markdown
+++ b/source/_dashboards/sidebar.markdown
@@ -3,6 +3,11 @@ type: view
title: Sidebar view
sidebar_label: Sidebar
description: "The sidebar view has 2 columns, a wide one and a smaller one on the right."
+related:
+ - docs: /dashboards/masonry/
+ title: Masonry view
+ - docs: /dashboards/panel/
+ title: Panel view
---
The sidebar view has 2 columns, a wide one and a smaller one on the right.
@@ -53,9 +58,4 @@ cards:
- media_player.lounge_room
view_layout:
position: sidebar
-```
-
-## Related topics
-
-- [Panel view](/dashboards/panel/)
-- [Masonry view](/dashboards/masonry/)
\ No newline at end of file
+```
\ No newline at end of file
diff --git a/source/_dashboards/statistic.markdown b/source/_dashboards/statistic.markdown
index e39895bae59..e7d03df5ebf 100644
--- a/source/_dashboards/statistic.markdown
+++ b/source/_dashboards/statistic.markdown
@@ -3,6 +3,11 @@ type: card
title: "Statistic card"
sidebar_label: Statistic
description: "The statistic card allows you to display a statistical value for an entity."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The statistic card allows you to display a statistical value for an entity.
@@ -172,8 +177,3 @@ period:
seconds: -10
stat_type: change
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/statistics-graph.markdown b/source/_dashboards/statistics-graph.markdown
index 940059e3a20..52a69b301be 100644
--- a/source/_dashboards/statistics-graph.markdown
+++ b/source/_dashboards/statistics-graph.markdown
@@ -3,6 +3,11 @@ type: card
title: "Statistics graph card"
sidebar_label: Statistics graph
description: "The statistics graph card allows you to display a graph with statistics data for each of the entities listed."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The statistics graph card allows you to display a graph of statistics data for each of the entities listed.
@@ -96,8 +101,3 @@ entities:
- entity: sensor.inside_temperature
name: Inside
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/thermostat.markdown b/source/_dashboards/thermostat.markdown
index 5ca865065d8..240a89bbc80 100644
--- a/source/_dashboards/thermostat.markdown
+++ b/source/_dashboards/thermostat.markdown
@@ -3,6 +3,11 @@ type: card
title: "Thermostat card"
sidebar_label: Thermostat
description: "The thermostat card gives control of your climate entity, allowing you to change the temperature and mode of the entity."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The thermostat card gives control of your [climate](/integrations/#climate) {% term entity %}, allowing you to change the temperature and mode of the {% term entity %}.
@@ -55,8 +60,3 @@ features:
type: thermostat
entity: climate.nest
```
-
-## Related topics
-
-- [Card features](/dashboards/features)
-- [Themes](/integrations/frontend/)
diff --git a/source/_dashboards/tile.markdown b/source/_dashboards/tile.markdown
index 514cfc14496..7dba42385ef 100644
--- a/source/_dashboards/tile.markdown
+++ b/source/_dashboards/tile.markdown
@@ -3,6 +3,13 @@ type: card
title: "Tile card"
sidebar_label: Tile
description: "The tile card gives you a quick overview of your entity. The card allows you to toggle the entity, show the more-info dialog, or custom actions."
+related:
+ - docs: /dashboards/actions/
+ title: Card actions
+ - docs: /dashboards/features
+ title: Card features
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The tile card gives you a quick overview of your {% term entity %}. The card allows you to toggle the {% term entity %} and show the more info dialog. A badge is shown for some {% term entities %} like the [climate](/integrations/climate) or [person](/integrations/person) {% term entities %}.
@@ -33,7 +40,7 @@ icon:
type: string
color:
required: false
- description: Set the color when the entity is active. By default, the color is based on `state`, `domain`, and `device_class` of your entity. It accepts [color token](/dashboards/tile/#available-color-tokens) or hex color code.
+ description: Set the color when the entity is active. By default, the color is based on `state`, `domain`, and `device_class` of your entity. It accepts [color token](/dashboards/tile/#available-colors) or hex color code.
type: string
default: state
show_entity_picture:
@@ -130,8 +137,3 @@ features:
You want to colorize the tile card? Choose one of the following colors: `primary`, `accent`, `disabled`, `red`, `pink`, `purple`, `deep-purple`, `indigo`, `blue`, `light-blue`, `cyan`, `teal`, `green`, `light-green`, `lime`, `yellow`, `amber`, `orange`, `deep-orange`, `brown`, `grey`, `blue-grey`, `black` and `white`.
-## Related topics
-
-- [Card actions](/dashboards/actions/)
-- [Card features](/dashboards/features)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/todo-list.markdown b/source/_dashboards/todo-list.markdown
index 51b358e1755..846d6cfd7f2 100644
--- a/source/_dashboards/todo-list.markdown
+++ b/source/_dashboards/todo-list.markdown
@@ -3,6 +3,19 @@ type: card
title: "To-do list card"
sidebar_label: To-do list
description: "The to-do list card allows you to add, edit, check-off, and clear items from your to-do list."
+related:
+ - docs: /dashboards/dashboards/
+ title: Dashboards
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
+ - docs: /integrations/todo
+ title: To-do list integration documentation
+ - docs: /integrations/#to-do-list
+ title: List of to-do list integrations
+ - docs: /integrations/local_todo/
+ title: Local to-do integration
---
The to-do list card allows you to add, edit, check-off, and clear items from your to-do list.
@@ -59,15 +72,3 @@ type: todo-list
entity: todo-list
title: todo list
```
-
-## Related topics
-
-- [To-do list integration documentation](/integrations/todo)
-- [List of to-do list integrations](/integrations/#to-do-list)
-- [Local to-do integration](/integrations/local_todo/)
-
-### Dashboards, cards, and themes
-
-- [Dashboards](/dashboards/dashboards/)
-- [Dashboard cards](/dashboards/cards/)
-- [Themes](/integrations/frontend/)
\ No newline at end of file
diff --git a/source/_dashboards/vertical-stack.markdown b/source/_dashboards/vertical-stack.markdown
index 08768af6955..56212aec535 100644
--- a/source/_dashboards/vertical-stack.markdown
+++ b/source/_dashboards/vertical-stack.markdown
@@ -3,6 +3,9 @@ type: card
title: "Vertical stack card"
sidebar_label: Vertical stack
description: "The vertical stack card allows you to group multiple cards so they always sit in the same column."
+related:
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The vertical stack card allows you to group multiple cards so they always sit in the same column.
@@ -72,6 +75,3 @@ cards:
Create a grid layout using vertical and horizontal stack.
-## Related topics
-
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_dashboards/weather-forecast.markdown b/source/_dashboards/weather-forecast.markdown
index 55c8fadd530..2ef07499650 100644
--- a/source/_dashboards/weather-forecast.markdown
+++ b/source/_dashboards/weather-forecast.markdown
@@ -3,6 +3,11 @@ type: card
title: "Weather forecast card"
sidebar_label: Weather forecast
description: "The weather forecast card displays the weather. Very useful to include on interfaces that people display on the wall."
+related:
+ - docs: /integrations/frontend/
+ title: Themes
+ - docs: /dashboards/cards/
+ title: Dashboard cards
---
The weather forecast card displays the weather. This card is particularly useful on wall-mounted displays.
@@ -153,8 +158,3 @@ Example theme configuration:
```yaml
--weather-icon-sunny: url("/local/sunny.png")
```
-
-## Related topics
-
-- [Themes](/integrations/frontend/)
-- [Dashboard cards](/dashboards/cards/)
\ No newline at end of file
diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml
index 445fe1e2893..4b0ed4611a5 100644
--- a/source/_data/glossary.yml
+++ b/source/_data/glossary.yml
@@ -3,20 +3,30 @@
# Format is a list of terms, each term is a dictionary with the following keys:
# - term: The term to define (required)
# - definition: The definition of the term (required)
-# - excerpt: Short excerpt of the definition, overrides definition for tooltips (optional)
+# - excerpt: Short excerpt of the definition, overrides definition for tooltips
+# (optional)
# - link: A URL to link to for more information (optional)
# - aliases: A list of aliases for the term (optional)
#
- term: Action
definition: |-
- Actions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*.
- Actions use service calls and/or scenes to interact with entities and cause these entities to do something. Actions can also include conditions and a delay. An action can call multiple services at the same time. For example, if your presence is detected in a room, an action may call one service to turn on a light and call another service to start playing music after a delay.
- Actions are also used on the dashboard, for example as tap or hold action on a UI element. When triggered, the action calls a service.
+ Actions are used in several places in Home Assistant. As part of a script or
+ automation, actions define what is going to happen once a trigger is
+ activated. In scripts, an action is called *sequence*. Actions use service
+ calls and/or scenes to interact with entities and cause these entities to do
+ something. Actions can also include conditions and a delay. An action can
+ call multiple services at the same time. For example, if your presence is
+ detected in a room, an action may call one service to turn on a light and
+ call another service to start playing music after a delay. Actions are also
+ used on the dashboard, for example as tap or hold action on a UI element.
+ When triggered, the action calls a service.
aliases:
- actions
link: /docs/automation/action/
excerpt: >
- Actions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*.
+ Actions are used in several places in Home Assistant. As part of a script or
+ automation, actions define what is going to happen once a trigger is
+ activated. In scripts, an action is called *sequence*.
- term: Add-on
definition: >-
Add-ons are additional standalone third-party software packages that can be
@@ -28,23 +38,29 @@
installed on Home Assistant OS.
- term: Area
definition: >-
- An area in Home Assistant is a logical grouping of devices and entities that are meant to match areas (or rooms) in the physical world: your home. For example, the `living room` area groups devices and entities in your living room. Areas allow you to target service calls at an entire group of devices. For example, turning off all the lights in the living room.
- Locations within your home such as living room, dance floor, etc.
- Areas can be assigned to floors.
- Areas can also be used for automatically
- generated cards, such as the [Area card](/dashboards/area/).
+ An area in Home Assistant is a logical grouping of devices and entities that
+ are meant to match areas (or rooms) in the physical world: your home. For
+ example, the `living room` area groups devices and entities in your living
+ room. Areas allow you to target service calls at an entire group of devices.
+ For example, turning off all the lights in the living room. Locations within
+ your home such as living room, dance floor, etc. Areas can be assigned to
+ floors. Areas can also be used for automatically generated cards, such as
+ the [Area card](/dashboards/area/).
excerpt: >-
- An area in Home Assistant is a logical grouping of devices and entities that are meant to match areas (or rooms) in the physical world: your home. For example, the `living room` area groups devices and entities in your living room.
+ An area in Home Assistant is a logical grouping of devices and entities that
+ are meant to match areas (or rooms) in the physical world: your home. For
+ example, the `living room` area groups devices and entities in your living
+ room.
aliases:
- areas
- term: Automation
definition: >-
- Automations connect one or more triggers to one or more actions in a
- 'when trigger then do action' fashion with additional optional conditions.
- For example, an automation might connect the trigger 'sunset' to the action
+ Automations connect one or more triggers to one or more actions in a 'when
+ trigger then do action' fashion with additional optional conditions. For
+ example, an automation might connect the trigger 'sunset' to the action
'turn the lights on' but only if the condition 'someone is home' is met.
- Pre-made automations for common use-cases are available via
- [the blueprints feature](/docs/automation/using_blueprints/).
+ Pre-made automations for common use-cases are available via [the blueprints
+ feature](/docs/automation/using_blueprints/).
excerpt: >-
Automations in Home Assistant allow you to automatically respond to things
that happen in and around your home.
@@ -53,14 +69,14 @@
- automations
- term: Backup
definition: >-
- Home Assistant has built-in functionality to create files containing a copy of
- your configuration. This can be used to restore your Home Assistant as well
- as migrate to a new system. The backup feature is available on some installation
- types.
+ Home Assistant has built-in functionality to create files containing a copy
+ of your configuration. This can be used to restore your Home Assistant as
+ well as migrate to a new system. The backup feature is available on some
+ installation types.
link: /integrations/backup/
excerpt: >-
- Home Assistant has built-in functionality to create files containing a copy of
- your configurations. This is available on certain installation types.
+ Home Assistant has built-in functionality to create files containing a copy
+ of your configurations. This is available on certain installation types.
aliases:
- backups
- term: Binary sensor
@@ -70,54 +86,85 @@
link: /integrations/binary_sensor
- term: Blueprint
definition: >-
- A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration-specific settings. Blueprints are shared by the community on the [blueprints exchange](https://community.home-assistant.io/c/blueprints-exchange/53) in the forum.
+ A blueprint is a script or automation configuration with certain parts
+ marked as configurable. This allows users to create multiple scripts or
+ automations based on the same blueprint, with each having its own
+ configuration-specific settings. Blueprints are shared by the community on
+ the [blueprints
+ exchange](https://community.home-assistant.io/c/blueprints-exchange/53) in
+ the forum.
link: /docs/blueprint/
excerpt: >-
- A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration-specific settings.
+ A blueprint is a script or automation configuration with certain parts
+ marked as configurable. This allows users to create multiple scripts or
+ automations based on the same blueprint, with each having its own
+ configuration-specific settings.
aliases:
- blueprints
- term: Category
definition: >-
- A category is an organization tool that allows grouping items in a table. Like labels, categories allow grouping irrespective of the items' physical location. For example, on the automations page, you can create the categories “Notifications” or “NFC tags” to view your automations grouped or filtered. Categories are unique for each table. The automations page can have different categories than the scene, scripts, or helpers settings page.
+ A category is an organization tool that allows grouping items in a table.
+ Like labels, categories allow grouping irrespective of the items' physical
+ location. For example, on the automations page, you can create the
+ categories “Notifications” or “NFC tags” to view your automations grouped or
+ filtered. Categories are unique for each table. The automations page can
+ have different categories than the scene, scripts, or helpers settings page.
aliases:
- categories
- term: Commissioning
definition: >-
- In the context of Matter devices, *commissioning* is the process of adding a device to a Matter controller. It is the equivalent of pairing a device in Zigbee or Z-Wave. Commissioning is done by scanning a QR code or entering a code manually. The code is printed on the device or its packaging. The code contains information about the device, such as its type, manufacturer, and serial number. The controller uses this information to identify the device and to download the required information to control the device. For example, the controller downloads the device's capabilities, such as the supported commands and the available attributes. The controller also downloads the device's configuration, such as the device's name and location.
+ In the context of Matter devices, *commissioning* is the process of adding a
+ device to a Matter controller. It is the equivalent of pairing a device in
+ Zigbee or Z-Wave. Commissioning is done by scanning a QR code or entering a
+ code manually. The code is printed on the device or its packaging. The code
+ contains information about the device, such as its type, manufacturer, and
+ serial number. The controller uses this information to identify the device
+ and to download the required information to control the device. For example,
+ the controller downloads the device's capabilities, such as the supported
+ commands and the available attributes. The controller also downloads the
+ device's configuration, such as the device's name and location.
link: /integrations/matter/
aliases:
- commission
excerpt: >
- In the context of Matter devices, *commissioning* is the process of adding a device to a Matter controller. It is the equivalent of pairing a device in Zigbee or Z-Wave.
+ In the context of Matter devices, *commissioning* is the process of adding a
+ device to a Matter controller. It is the equivalent of pairing a device in
+ Zigbee or Z-Wave.
- term: Component
definition: >-
Better known as: Integrations. Integrations used to be known as components.
- term: Condition
definition: >-
- Conditions are an optional part of an automation that will prevent an
- action from firing if they are not met.
+ Conditions are an optional part of an automation that will prevent an action
+ from firing if they are not met.
link: /docs/scripts/conditions/
aliases:
- conditions
- term: Cover
definition: >-
- Covers are devices such as blinds, garage doors, etc that can be opened
- and closed and optionally set to a specific position.
+ Covers are devices such as blinds, garage doors, etc that can be opened and
+ closed and optionally set to a specific position.
link: /integrations/cover
- term: Customize
definition: >-
- Customization allows you to overwrite the default parameters of your
- devices in the configuration.
+ Customization allows you to overwrite the default parameters of your devices
+ in the configuration.
- term: Device
definition: |-
- A device is a model representing a physical or logical unit that contains entities.
- **Example for a device as a physical unit**
- A smart plug named 'Coffee machine' which provides 2 entities: a `switch` entity to turn power on or off ('Coffee machine power switch') and a `sensor` entity for power monitoring ('Coffee machine power sensor').
- **Example for a device as a logical unit**
- An ecobee thermostat with 4 room sensors. This thermostat is seen as 5 devices in Home Assistant: 1 device for the thermostat with 4 sensors, and 1 device for each room sensor. Each device can be in a different area and may have more than one input or output within that area.
- Devices have properties such as ID, manufacturer, name, model, hardware version, firmware version, connections, etc.
+ A device is a model representing a physical or logical unit that contains
+ entities. **Example for a device as a physical unit** A smart plug named
+ 'Coffee machine' which provides 2 entities: a `switch` entity to turn power
+ on or off ('Coffee machine power switch') and a `sensor` entity for power
+ monitoring ('Coffee machine power sensor'). **Example for a device as a
+ logical unit** An ecobee thermostat with 4 room sensors. This thermostat is
+ seen as 5 devices in Home Assistant: 1 device for the thermostat with 4
+ sensors, and 1 device for each room sensor. Each device can be in a
+ different area and may have more than one input or output within that area.
+ Devices have properties such as ID, manufacturer, name, model, hardware
+ version, firmware version, connections, etc.
excerpt: >
- A device is a model representing a physical or logical unit that contains entities.
+ A device is a model representing a physical or logical unit that contains
+ entities.
aliases:
- devices
- term: Device tracker
@@ -130,35 +177,43 @@
they are discovered.
- term: Domain
definition: >-
- Each integration in Home Assistant has a unique identifier:
- a domain. All of the entities and services available in Home Assistant
- are provided by integrations and thus belong to such a domain. The first
- part of the entity or service, before the `.` shows the domain they belong
- to. For example `light.kitchen` is an entity in the `light` domain from
- the [light integration](/integrations/light), while `hue.activate_scene`
- is the `activate_scene` service for the `hue` domain which belongs to
- the [Hue integration](/integrations/hue).
+ Each integration in Home Assistant has a unique identifier: a domain. All of
+ the entities and services available in Home Assistant are provided by
+ integrations and thus belong to such a domain. The first part of the entity
+ or service, before the `.` shows the domain they belong to. For example
+ `light.kitchen` is an entity in the `light` domain from the [light
+ integration](/integrations/light), while `hue.activate_scene` is the
+ `activate_scene` service for the `hue` domain which belongs to the [Hue
+ integration](/integrations/hue).
excerpt: >
- Each integration in Home Assistant has a unique identifier: The domain.
- It is often shown as the first part (before the dot) of entity IDs.
+ Each integration in Home Assistant has a unique identifier: The domain. It
+ is often shown as the first part (before the dot) of entity IDs.
aliases:
- domains
- term: Entity
definition: |-
- An entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. Entities have states.
- **Example for entities as part of a device**
- A combined temperature and humidity sensor device provides two sensor entities. One for temperature (e.g. `sensor.temperature` with state `21.0` and unit `°C`) and one for humidity
- (e.g. `sensor.humidity` with state `65.4` and unit `%`).
- **Example for entities as part of a service**
- A weather service that provides 3 entities: wind speed, air pressure, and ozon level.
- **Example of an entity used for control**
- A fan that is turned on when the temperature exceeds 30 °C.
- There are standardized types of entities for common integrations such as light, switch, camera, sensor, fan, or vacuum.
- Some entities are not part of a device or service. Examples of standalone entities are automation, script, scene entities, and helper entities (e.g. input helpers).
- Most properties of entities are related to the state. Entities have optional attributes such as friendly name, unit of measurement, and an icon or picture that can be displayed in the frontend.
+ An entity represents a sensor, actor, or function in Home Assistant.
+ Entities are used to monitor physical properties or to control other
+ entities. An entity is usually part of a device or a service. Entities have
+ states. **Example for entities as part of a device** A combined temperature
+ and humidity sensor device provides two sensor entities. One for temperature
+ (e.g. `sensor.temperature` with state `21.0` and unit `°C`) and one for
+ humidity (e.g. `sensor.humidity` with state `65.4` and unit `%`). **Example
+ for entities as part of a service** A weather service that provides 3
+ entities: wind speed, air pressure, and ozon level. **Example of an entity
+ used for control** A fan that is turned on when the temperature exceeds
+ 30 °C. There are standardized types of entities for common integrations
+ such as light, switch, camera, sensor, fan, or vacuum. Some entities are not
+ part of a device or service. Examples of standalone entities are automation,
+ script, scene entities, and helper entities (e.g. input helpers). Most
+ properties of entities are related to the state. Entities have optional
+ attributes such as friendly name, unit of measurement, and an icon or
+ picture that can be displayed in the frontend.
link: /docs/configuration/state_object/
excerpt: >
- An entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service.
+ An entity represents a sensor, actor, or function in Home Assistant.
+ Entities are used to monitor physical properties or to control other
+ entities. An entity is usually part of a device or a service.
aliases:
- entities
- term: Event
@@ -169,16 +224,26 @@
- events
- term: Floor
definition: >-
- A floor in Home Assistant is a logical grouping of areas that are meant to match the physical floors in your home. Devices & entities are not assigned to floors but to areas. A floor has properties such as: Floor ID, name, aliases (for use in assistants), an icon, and a floor level. Some of these properties are optional. The level number can be negative to reflect floors below the basement.
- Floors can be used in automations and scripts as a target for actions. For example, to turn off all the lights on the downstairs floor when you go to bed.
+ A floor in Home Assistant is a logical grouping of areas that are meant to
+ match the physical floors in your home. Devices & entities are not assigned
+ to floors but to areas. A floor has properties such as: Floor ID, name,
+ aliases (for use in assistants), an icon, and a floor level. Some of these
+ properties are optional. The level number can be negative to reflect floors
+ below the basement. Floors can be used in automations and scripts as a
+ target for actions. For example, to turn off all the lights on the
+ downstairs floor when you go to bed.
excerpt: >-
- A floor in Home Assistant is a logical grouping of areas that are meant to match the physical floors in your home. Devices & entities are not assigned to floors but to areas. Floors can be used in automations and scripts as a target for actions. For example, to turn off all the lights on the downstairs floor when you go to bed.
+ A floor in Home Assistant is a logical grouping of areas that are meant to
+ match the physical floors in your home. Devices & entities are not assigned
+ to floors but to areas. Floors can be used in automations and scripts as a
+ target for actions. For example, to turn off all the lights on the
+ downstairs floor when you go to bed.
aliases:
- floors
- term: Frontend
definition: >-
- The frontend is a necessary component for the UI, it is also where you
- can define your themes.
+ The frontend is a necessary component for the UI, it is also where you can
+ define your themes.
link: /integrations/frontend/
- term: Group
definition: >-
@@ -188,29 +253,38 @@
- groups
- term: HASS
definition: >-
- HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for
- Home Assistant. It is also the command-line tool.
+ HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home
+ Assistant. It is also the command-line tool.
- term: HassOS
definition: >-
Another name for Home Assistant Operating System
link: /hassio/installation/
+- term: Home Assistant Container
+ definition: >-
+ Home Assistant Container is a standalone container-based installation of
+ Home Assistant Core. Any [OCI](https://opencontainers.org/) compatible
+ runtime can be used, but the documentation focus is on Docker.
+ link: /installation/#advanced-installation-methods
- term: Home Assistant Core
definition: >-
- Home Assistant Core is a Python program. It can be run on various operating
- systems and is the basis for Home Assistant. When people are talking about
- Home Assistant Core they usually refer to a standalone installation method
- that can be installed using a Virtual Environment or Docker. Home Assistant
- Core does not use the Home Assistant Supervisor.
+ Home Assistant Core is the Python program at the heart of Home Assistant. It
+ is part of all of the four installation types and can be run on various
+ operating systems. It can be installed standalone (without Home Assistant
+ Supervisor), using a Virtual Environment (typically referred to as Home
+ Assistant Core installation method) or as a container using Docker
+ (typically referred to as Home Assistant Container installation method).
link: /installation/#advanced-installation-methods
excerpt: >
- Home Assistant Core is the hart of Home Assistant itself. It is a Python
- program that powers every installation type, but can be installed standalone.
+ Home Assistant Core is the heart of Home Assistant itself. It is a Python
+ program that powers every installation type, but can be installed
+ standalone.
- term: Home Assistant Supervised
definition: >-
- Home Assistant Supervised is a full UI managed home automation ecosystem that
- runs Home Assistant, the Home Assistant Supervisor and add-ons. It comes
- pre-installed on Home Assistant OS, but can be installed on any Linux system.
- It leverages Docker, which is managed by the Home Assistant Supervisor.
+ Home Assistant Supervised is a full UI managed home automation ecosystem
+ that runs the Home Assistant Core program, the Home Assistant Supervisor and
+ add-ons. It comes pre-installed on Home Assistant OS, but can be installed
+ standalone on Debian Linux systems. It leverages Docker, which is managed by
+ the Home Assistant Supervisor.
excerpt: >
Home Assistant Supervised is the full Home Assistant ecosystem, without the
Home Assistant Operating System.
@@ -219,39 +293,50 @@
definition: >-
The Home Assistant Supervisor is a program that manages a Home Assistant
installation, taking care of installing and updating Home Assistant,
- add-ons, itself and, if used, updating the Home Assistant Operating System.
+ add-ons, itself, and, if used, updating the Home Assistant Operating System.
link: /installation/#advanced-installation-methods
- term: Home Assistant Operating System
definition: >-
Home Assistant OS, the Home Assistant Operating System, is an embedded,
minimalistic, operating system designed to run the Home Assistant ecosystem
- on single board computers (like the Raspberry Pi) or Virtual Machines.
- The Home Assistant Supervisor can keep it up to date, removing the need for
- you to manage an operating system. Home Assistant Operating System is the recommended installation method for most users.
+ on single board computers (like the Raspberry Pi) or Virtual Machines. It
+ includes Home Assistant Core, the Home Assistant Supervisor, and supports
+ add-ons. Home Assistant Supervisor keeps it up to date, removing the need
+ for you to manage an operating system. Home Assistant Operating System is
+ the recommended installation method for most users.
excerpt: >
Home Assistant OS, the Home Assistant Operating System, is an embedded,
- minimalistic, operating system designed to run the Home Assistant ecosystem. It is the recommended installation method for most users.
+ minimalistic, operating system designed to run the Home Assistant ecosystem.
+ It is the recommended installation method for most users.
link: /installation/#advanced-installation-methods
- term: Host
definition: >-
- A device that can communicate with other devices on a network. During setup and configuration,
- an input requesting a **Host** typically refers to a device's network address so that
- Home Assistant can attempt to connect to it. This may be in the form of a hostname, URL,
- IP address or some other type of network identifier. If you do not know the hostname or IP address of a device, you can find it in your router's webinterface. For example, if your device is connected wirelessly, somewhere there is a page listing all the devices that are connected to your network. It depends on your router, where exactly this page is. It could be under **Network** > **Wireless**.
+ A device that can communicate with other devices on a network. During setup
+ and configuration, an input requesting a **Host** typically refers to a
+ device's network address so that Home Assistant can attempt to connect to
+ it. This may be in the form of a hostname, URL, IP address or some other
+ type of network identifier. If you do not know the hostname or IP address of
+ a device, you can find it in your router's webinterface. For example, if
+ your device is connected wirelessly, somewhere there is a page listing all
+ the devices that are connected to your network. It depends on your router,
+ where exactly this page is. It could be under **Network** > **Wireless**.
excerpt: >-
- A device that participates in your network. If asked for the host, enter either the device's IP address or host name. If you don't know those, check the list of hosts in your router.
+ A device that participates in your network. If asked for the host, enter
+ either the device's IP address or host name. If you don't know those, check
+ the list of hosts in your router.
link: https://en.wikipedia.org/wiki/Host_(network)
aliases:
- hosts
- term: Integration
definition: >-
Integrations connect and integrate Home Assistant with devices, services,
- and more. They contain all the logic to handle
- vendor- and device-specific implementations, such as authentication or
- specific protocols. The integration brings such device-specific elements 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.
+ and more. They contain all the logic to handle vendor- and device-specific
+ implementations, such as authentication or specific protocols. The
+ integration brings such device-specific elements 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.
excerpt: >
Integrations connect and integrate Home Assistant with your devices,
services, and more.
@@ -260,24 +345,40 @@
- integrations
- term: Intent
definition: >-
- Intent is a term used with voice assistants. The intent is what Home Assistant thinks you want it to do when it extracts a command from your voice or text utterance. Currently, the following intents are supported out of the box: HassTurnOn, HassTurnOff, HassGetState, and HassLightSet.
- These intents allow you to turn things on or off, inquire about a state, or change the brightness or color of a light.
+ Intent is a term used with voice assistants. The intent is what Home
+ Assistant thinks you want it to do when it extracts a command from your
+ voice or text utterance. Currently, the following intents are supported out
+ of the box: HassTurnOn, HassTurnOff, HassGetState, and HassLightSet. These
+ intents allow you to turn things on or off, inquire about a state, or change
+ the brightness or color of a light.
excerpt: >
- Intent is a term used with voice assistants. The intent is what Home Assistant thinks you want it to do when it extracts a command from your voice or text utterance.
+ Intent is a term used with voice assistants. The intent is what Home
+ Assistant thinks you want it to do when it extracts a command from your
+ voice or text utterance.
link: https://developers.home-assistant.io/docs/intent_builtin
aliases:
- Intents
- term: Label
definition: >-
- Labels in Home Assistant allow grouping elements irrespective of their physical location or type. Labels can be assigned to areas, devices, entities, automations, scenes, scripts, and helpers. Labels can be used in automations and scripts as a target for actions and services. Labels can also be used to filter data. For example, you can filter the list of devices to show only devices with the label `heavy energy usage` or turn these devices off when there is not a lot of solar energy available.
+ Labels in Home Assistant allow grouping elements irrespective of their
+ physical location or type. Labels can be assigned to areas, devices,
+ entities, automations, scenes, scripts, and helpers. Labels can be used in
+ automations and scripts as a target for actions and services. Labels can
+ also be used to filter data. For example, you can filter the list of devices
+ to show only devices with the label `heavy energy usage` or turn these
+ devices off when there is not a lot of solar energy available.
excerpt: >-
- Labels in Home Assistant allow grouping elements irrespective of their physical location or type. Labels can be assigned to areas, devices, entities, automations, scenes, scripts, and helpers. Labels can be used in automations and scripts as a target for actions and services. Labels can also be used to filter data.
+ Labels in Home Assistant allow grouping elements irrespective of their
+ physical location or type. Labels can be assigned to areas, devices,
+ entities, automations, scenes, scripts, and helpers. Labels can be used in
+ automations and scripts as a target for actions and services. Labels can
+ also be used to filter data.
aliases:
- labels
- term: Lovelace
definition: >-
- Lovelace is the original code name of the UI that is now known as
- [Home Assistant dashboards](/dashboards).
+ Lovelace is the original code name of the UI that is now known as [Home
+ Assistant dashboards](/dashboards).
- term: Light
definition: >-
A light has a brightness you can control, and optionally color temperature
@@ -285,9 +386,17 @@
link: /integrations/light
- term: Matter
definition: >-
- Matter is an open-source standard that defines how to control smart home devices on a Wi-Fi or Thread network. The aim of the standard is to improve security and to make devices interoperable across vendors, replacing proprietary protocols for smart home ecosystems. Unlike other standards, Matter allows joining the same device to multiple controllers. For example, you can add a light to Google Home, Apple Home, and Home Assistant at the same time. A bridge device can be used to connect devices running on other smart home technologies such as Zigbee or Z-Wave.
+ Matter is an open-source standard that defines how to control smart home
+ devices on a Wi-Fi or Thread network. The aim of the standard is to improve
+ security and to make devices interoperable across vendors, replacing
+ proprietary protocols for smart home ecosystems. Unlike other standards,
+ Matter allows joining the same device to multiple controllers. For example,
+ you can add a light to Google Home, Apple Home, and Home Assistant at the
+ same time. A bridge device can be used to connect devices running on other
+ smart home technologies such as Zigbee or Z-Wave.
excerpt: >
- Matter is an open-source standard that defines how to control smart home devices on a Wi-Fi or Thread network.
+ Matter is an open-source standard that defines how to control smart home
+ devices on a Wi-Fi or Thread network.
link: /integrations/matter
- term: Notification
definition: >-
@@ -306,8 +415,8 @@
Platforms are building blocks provided by some integrations to be used by
other integrations. For example, the [Light](/integrations/light)
integration provides the `light platform` that is utilized by all
- integrations providing `light` entities such
- as e.g. [Hue](/integrations/hue).
+ integrations providing `light` entities such as e.g.
+ [Hue](/integrations/hue).
excerpt: >
Platforms are building blocks provided by some integrations to be used by
other integrations.
@@ -317,78 +426,97 @@
- term: Reload
definition: >-
Applies the changes made to the Home Assistant configuration files. Changes
- are normally automatically updated. However, changes made outside of the front
- end will not be reflected in Home Assistant and require a reload.
- To perform a manual reload, go to **Settings** > **System** >
- **Restart Home Assistant** (top right) > **Quick reload**. If you do not see the **Quick reload** option in the menu, you need to enable **Advanced mode** in your user settings. More granular
- reload options are available in *YAML configuration reloading* section
- in **Developer tools** > **YAML**.
+ are normally automatically updated. However, changes made outside of the
+ front end will not be reflected in Home Assistant and require a reload. To
+ perform a manual reload, go to **Settings** > **System** > **Restart Home
+ Assistant** (top right) > **Quick reload**. If you do not see the **Quick
+ reload** option in the menu, you need to enable **Advanced mode** in your
+ user settings. More granular reload options are available in *YAML
+ configuration reloading* section in **Developer tools** > **YAML**.
excerpt: >
- Applies the changes made to Home Assistant configuration files. Changes are normally
- automatically updated. However, changes made outside of the front
+ Applies the changes made to Home Assistant configuration files. Changes are
+ normally automatically updated. However, changes made outside of the front
end will not be reflected in Home Assistant and require a reload.
- term: Scene
definition: >-
- Scenes capture the states you want certain entities to be. For example,
- a scene can specify that light A should be turned on and light B should
- be bright red.
+ Scenes capture the states you want certain entities to be. For example, a
+ scene can specify that light A should be turned on and light B should be
+ bright red.
link: /integrations/scene/
aliases:
- scenes
- term: Script
definition: >
- Scripts are components that allow users to specify a sequence of actions
- to be executed by Home Assistant when turned on.
+ Scripts are components that allow users to specify a sequence of actions to
+ be executed by Home Assistant when turned on.
link: /docs/scripts/
aliases:
- scripts
- term: Sensor
definition: >-
- Sensors return information about a thing, for instance the level of water
- in a tank.
+ Sensors return information about a thing, for instance the level of water in
+ a tank.
link: /integrations/sensor/
aliases:
- sensors
- term: Selector
definition: >-
- Selectors are components for the user interface. Some selectors can,
- for example, show a toggle button to turn something on or off, while another
+ Selectors are components for the user interface. Some selectors can, for
+ example, show a toggle button to turn something on or off, while another
select can filter a list of devices to show only devices that have
motion-sensing capabilities.
excerpt: >
- Selectors are components for the user interface. Like toggle, dropdown,
- and more.
+ Selectors are components for the user interface. Like toggle, dropdown, and
+ more.
link: /docs/blueprint/selectors/
aliases:
- selectors
- term: Service
definition: |-
- The term service has 2 meanings in Home Assistant:
- **The information service**
- For example, the municipal waste management service that provides entities for organic, paper, and packaging waste. In terms of functionality, the information service is like a device. It is called *service* to avoid confusion, as it does not come with a piece of hardware.
- **The software function that interacts with targets to make something happen**
- A service carries out one specific task, for example: turning on the light in the living room or sending a notification to a mobile phone.
- A service has targets and data. Service targets are: areas, devices, and entities. Service data carries the information required to define the desired state change in the target. For example, the target, together with brightness 150 and RGB color `[255,0,0]`, or the message “Your coffee is ready”.
- Services can be used in, for example, automation, scripts, dashboards, or voice commands to control your home.
- Home Assistant provides a series of predefined services, such as `homeassistant.turn_on`, `homeassistant.toggle`, or `homeassistant.reload`.
+ The term service has 2 meanings in Home Assistant: **The information
+ service** For example, the municipal waste management service that provides
+ entities for organic, paper, and packaging waste. In terms of functionality,
+ the information service is like a device. It is called *service* to avoid
+ confusion, as it does not come with a piece of hardware. **The software
+ function that interacts with targets to make something happen** A service
+ carries out one specific task, for example: turning on the light in the
+ living room or sending a notification to a mobile phone. A service has
+ targets and data. Service targets are: areas, devices, and entities. Service
+ data carries the information required to define the desired state change in
+ the target. For example, the target, together with brightness 150 and RGB
+ color `[255,0,0]`, or the message “Your coffee is ready”. Services can be
+ used in, for example, automation, scripts, dashboards, or voice commands to
+ control your home. Home Assistant provides a series of predefined services,
+ such as `homeassistant.turn_on`, `homeassistant.toggle`, or
+ `homeassistant.reload`.
excerpt: >
- A service carries out one specific task, for example: turn on the light in the
- living room. A service has targets and data and can be called by actions, a
- dashboard, or via voice command.
+ A service carries out one specific task, for example: turn on the light in
+ the living room. A service has targets and data and can be called by
+ actions, a dashboard, or via voice command.
link: /docs/scripts/service-calls/
aliases:
- services
- term: State
definition: |-
- The state holds the information of interest of an entity. For example, if a light is on or off, the current temperature, or the amount of energy used. The data type of state is `string` (a textual value). Entities store 2 timestamps related to the state: `last_updated` and `last_changed`. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state. For example, the state of a light is _on_, and the related state attributes could be its current brightness and color values.
- State changes can be used as the source of triggers. The current state can be used in conditions.
-
+ The state holds the information of interest of an entity. For example, if a
+ light is on or off, the current temperature, or the amount of energy used.
+ The data type of state is `string` (a textual value). Entities store 2
+ timestamps related to the state: `last_updated` and `last_changed`. Each
+ entity has exactly one state and the state only holds one value at a time.
+ However, entities can store attributes related to that state. For example,
+ the state of a light is _on_, and the related state attributes could be its
+ current brightness and color values. State changes can be used as the source
+ of triggers. The current state can be used in conditions.
+
link: /docs/configuration/state_object/
aliases:
- states
excerpt: >
- The state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement.
+ The state holds the information of interest of an entity, for example, if a
+ light is on or off. Each entity has exactly one state and the state only
+ holds one value at a time. However, entities can store attributes related to
+ that state such as brightness, color, or a unit of measurement.
- term: Switch
definition: >-
Switches are things that have two states you can select between, such as
@@ -405,20 +533,37 @@
- term: Thread
definition: >-
- Thread is a low-power mesh networking standard that is specifically designed for smart home applications. It is a protocol that defines how devices communicate. *Mesh* topology means that the devices can communicate with each other directly, without going through a central controller first. Thread uses the same radio frequency (RF) technology as Zigbee, but provides IP connectivity similar to Wi-Fi. Unlike Zigbee, Thread does not specify how to control devices. How Thread-enabled devices are controlled is specified in a higher level protocol such as HomeKit or Matter.
+ Thread is a low-power mesh networking standard that is specifically designed
+ for smart home applications. It is a protocol that defines how devices
+ communicate. *Mesh* topology means that the devices can communicate with
+ each other directly, without going through a central controller first.
+ Thread uses the same radio frequency (RF) technology as Zigbee, but provides
+ IP connectivity similar to Wi-Fi. Unlike Zigbee, Thread does not specify how
+ to control devices. How Thread-enabled devices are controlled is specified
+ in a higher level protocol such as HomeKit or Matter.
link: /integrations/thread/
excerpt: >
- Thread is a low-power mesh networking standard that is specifically designed for smart home applications. It is a protocol that defines how devices communicate.
+ Thread is a low-power mesh networking standard that is specifically designed
+ for smart home applications. It is a protocol that defines how devices
+ communicate.
- term: Thread border router
definition: >-
- A Thread border router forwards data packets between your local network and the Thread network. This enables smart home devices within a Thread network to communicate with IPv6-capable devices in your local network. A Thread border router is connected to your network either via Wi-Fi or Ethernet and uses its radio frequency (RF) radio to communicate with the Thread mesh network. In case of Matter, the data that is forwarded is encrypted. Examples of Thread border routers are the Nest Hub (2nd gen), the HomePod mini, and the Home Assistant SkyConnect together with the OpenThread Border Router add-on.
+ A Thread border router forwards data packets between your local network and
+ the Thread network. This enables smart home devices within a Thread network
+ to communicate with IPv6-capable devices in your local network. A Thread
+ border router is connected to your network either via Wi-Fi or Ethernet and
+ uses its radio frequency (RF) radio to communicate with the Thread mesh
+ network. In case of Matter, the data that is forwarded is encrypted.
+ Examples of Thread border routers are the Nest Hub (2nd gen), the HomePod
+ mini, and the Home Assistant SkyConnect together with the OpenThread Border
+ Router add-on.
link: /integrations/thread/#about-thread-border-routers
aliases:
- Thread border routers
- term: Trigger
definition: >-
- A trigger is a set of values or conditions of a platform that are defined
- to cause an automation to run.
+ A trigger is a set of values or conditions of a platform that are defined to
+ cause an automation to run.
link: /docs/automation/trigger/
aliases:
- triggers
@@ -428,21 +573,21 @@
TTS (text-to-speech) allows Home Assistant to talk to you.
link: /integrations/tts/
-
- term: Valve
definition: >-
- Valves are devices to control the flow of liquids and gases. All valves in Home Assistant can be opened
- and closed. Some valves can also be set to a specific position.
+ Valves are devices to control the flow of liquids and gases. All valves in
+ Home Assistant can be opened and closed. Some valves can also be set to a
+ specific position.
link: /integrations/valve
- term: Variables
definition: >-
- Variables are used to store values in memory that can be processed
- for example, in a script.
+ Variables are used to store values in memory that can be processed for
+ example, in a script.
link: /docs/scripts/#variables
- term: Zone
definition: >-
Zones are areas that can be used for presence detection.
link: /integrations/zone/
aliases:
- - zones
\ No newline at end of file
+ - zones
diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown
index 6f6b6b63eaa..de84130966b 100644
--- a/source/_docs/authentication.markdown
+++ b/source/_docs/authentication.markdown
@@ -23,12 +23,12 @@ For the moment, other user accounts will have the same access as the owner accou
@@ -38,6 +38,7 @@ You can:
- Enable or disable [multi-factor authentication](/docs/authentication/multi-factor-auth/).
- Delete _Refresh Tokens_. These are created when you log in from a device. Delete them if you want to force the device to log out.
- Create [Long Lived Access Tokens](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) so scripts can securely interact with Home Assistant.
+- Define language and other locale settings.
- Log out of Home Assistant.
+ 
+ Screenshot showing the General settings page.
+
-
-## Related topics
-
-- [Areas](/docs/organzing/areas/)
-- [Floors](/docs/organzing/floors/)
-- [Labels](/docs/organzing/labels/)
-- [Categories](/docs/organzing/categories/)
diff --git a/source/_docs/organizing/areas.markdown b/source/_docs/organizing/areas.markdown
index a682c87d1a6..9b132256f52 100644
--- a/source/_docs/organizing/areas.markdown
+++ b/source/_docs/organizing/areas.markdown
@@ -1,6 +1,16 @@
---
title: "Areas"
description: "Group your devices and entities in areas and group areas in floors."
+related:
+ - docs: /docs/organizing/areas/
+ title: Areas
+ - docs: /docs/organizing/
+ - docs: /docs/organizing/labels/
+ title: Labels
+ - docs: /docs/organizing/categories/
+ title: Categories
+ - docs: /docs/configuration/templating/#areas
+ title: Using areas in template
---
An area in Home Assistant is a logical grouping of {% term devices %} and {% term entities %} that are meant to match areas (or rooms) in the physical world of your home. For example, the "Living room" area groups devices and entities in your living room. Areas allow you to target an entire group of devices with a service call. For example, turning off all the lights in the living room.
@@ -34,9 +44,3 @@ If an area has not yet been assigned to a floor, it is shown in the **Unassigned
1. Go to {% my areas title="**Settings** > **Areas, labels & zones**" %} and select **Create area**.
2. On the area card, select the pencil icon.
3. In the dialog, select the floor and add labels, if you like.
-
-## Related topics
-
-- [Floors](/docs/organzing/floors/)
-- [Labels](/docs/organzing/labels/)
-- [Using areas in templates](/docs/configuration/templating/#areas)
\ No newline at end of file
diff --git a/source/_docs/organizing/categories.markdown b/source/_docs/organizing/categories.markdown
index f85ae9ae758..bb3ff237946 100644
--- a/source/_docs/organizing/categories.markdown
+++ b/source/_docs/organizing/categories.markdown
@@ -1,6 +1,13 @@
---
title: "Categories"
description: "Use categories to group and filter your table items"
+related:
+ - docs: /docs/organizing/areas/
+ title: Areas
+ - docs: /docs/organizing/floors/
+ title: Floors
+ - docs: /docs/organizing/labels/
+ title: Labels
---
Categories let you group and filter items in a table. Like labels, categories allow grouping irrespective of the items physical location. For example, on the automations page, you can create the categories “Notifications” or “NFC tags” to view your automations grouped or filtered. These categories group automations on the automation page, but have no effect anywhere else. Categories are unique for each table. The automations page can have different categories than the scene, scripts, or helpers settings page.
@@ -31,10 +38,6 @@ Follow these steps to create a new category.
- In the top right corner, select **Move to category**.
- Then, select the category from the list.
4. Once categories are applied, the table items are grouped by those categories.
- - The example shows 2 categories: Coffee and housekeeping.
+ - The example shows 2 categories: Coffee and housekeeping.
-
-## Related topics
-
-- [Labels](/docs/organizing/labels/)
diff --git a/source/_docs/organizing/filtering.markdown b/source/_docs/organizing/filtering.markdown
new file mode 100644
index 00000000000..97aea10bfbf
--- /dev/null
+++ b/source/_docs/organizing/filtering.markdown
@@ -0,0 +1,56 @@
+---
+title: "Filtering your assets"
+description: "Filter for items in tables."
+related:
+ - docs: /docs/organizing/floors/
+ title: Floors
+ - docs: /docs/organizing/labels/
+ title: Labels
+ - docs: /docs/organizing/areas/
+ title: Areas
+ - docs: /docs/organizing/categories/
+ title: Categories
+ - docs: /docs/organizing/
+ title: Grouping your assets
+ - docs: /common-tasks/general/
+ title: Enabling or disabling entities and automations
+---
+
+When working with tables, you can select multiple elements to apply an action on multiple items at once. If you have [grouped](/docs/organizing/) your assets by assigning them to floors, areas, labels, or directories you can also filter your data accordingly.
+
+## Selecting multiple items in a table
+
+1. In your table, select the 
button.
+
+ 
+
+2. In the list, select the items of interest.
+
+ 
+
+3. You can now apply changes to all selected elements, such as [applying labels](/docs/organzing/labels/) or [enabling or disabling entities and automations](/common-tasks/general/).
+
+## Filtering items in a table
+
+You can filter a table so that only items matching certain criteria are shown.
+
+1. In the top left corner above the table, select the **Filters** button.
+
+ 
+
+2. In the filters panel, select your filter criteria.
+ - You can filter for [floors](/docs/organizing/floors/), [areas](/docs/organizing/areas/), [labels](/docs/organizing/labels/), and [categories](/docs/organizing/categories/) if you have previously defined them.
+
+ 
+
+## Grouping and sorting items in a table
+
+You can group items in a table according to certain criteria. The number of shown items stays the same. No items will be hidden.
+
+1. In the top right above the table, select the **Group by** button.
+2. The items will be grouped according to the criteria you chose.
+ - In the example, the items are grouped by manufacturer.
+
+ 
+
+3. To sort the items, select the **Sort by** button.
diff --git a/source/_docs/organizing/floors.markdown b/source/_docs/organizing/floors.markdown
index c9b9199d1b8..d4db0cb84cf 100644
--- a/source/_docs/organizing/floors.markdown
+++ b/source/_docs/organizing/floors.markdown
@@ -1,6 +1,16 @@
---
title: "Floors"
description: "Group your areas per floor"
+related:
+ - docs: /docs/organizing/areas/
+ title: Areas
+ - docs: /docs/organizing/
+ - docs: /docs/organizing/labels/
+ title: Labels
+ - docs: /docs/configuration/templating/#floors
+ title: Using floors in templates
+ - docs: /voice_control/aliases/
+ title: Using floor alias for voice assistants
---
A floor in Home Assistant is a logical grouping of areas meant to match your home's physical floors. Devices and entities
@@ -27,9 +37,3 @@ Follow these steps to create a new floor.
4. You can now [assign areas to that floor](/docs/organizing/areas/#assigning-areas-to-floors-and-add-labels).
-
-## Related topics
-
-- [Alias for voice assistants](/voice_control/aliases/)
-- [Areas](/docs/organizing/areas/)
-- [Using floors in templates](/docs/configuration/templating/#floors)
diff --git a/source/_docs/organizing/labels.markdown b/source/_docs/organizing/labels.markdown
index 23948927316..fddcb4659bf 100644
--- a/source/_docs/organizing/labels.markdown
+++ b/source/_docs/organizing/labels.markdown
@@ -1,6 +1,15 @@
---
title: "Labels"
description: "Label your areas, devices, entities, automations, scripts, and helpers. Then, filter by label or run an automation on all entities with that label."
+related:
+ - docs: /docs/organizing/areas/
+ title: Areas
+ - docs: /docs/organizing/floors/
+ title: Floors
+ - docs: /docs/organizing/categories/
+ title: Categories
+ - docs: /docs/configuration/templating/#labels
+ title: Using labels in templates
---
Labels in Home Assistant allow grouping elements irrespective of their physical location or type. Labels can be assigned to areas, devices, entities, automations, scenes, scripts, and helpers. Labels can be used in automations and scripts as a target for actions and services. Labels can also be used to filter data. For example, you can filter the list of devices to show only devices with the label `heavy energy usage` or turn these devices off when there is not a lot of solar energy available.
@@ -41,8 +50,3 @@ Follow these steps to apply a label
- Select the button.
- From the list, select all the items to which you want to apply a label.
- In the top right corner, select the three dots menu, then select **Add label**. Then, select the labels from the list.
-
-## Related topics
-
-- [Areas](/docs/organizing/areas/)
-- [Using labels in templates](/docs/configuration/templating/#labels)
diff --git a/source/_docs/tools/check_config.markdown b/source/_docs/tools/check_config.markdown
index 24592293913..4a805d672cd 100644
--- a/source/_docs/tools/check_config.markdown
+++ b/source/_docs/tools/check_config.markdown
@@ -1,9 +1,12 @@
---
title: "check_config"
description: "Script to perform a check of the current configuration"
+related:
+ - docs: /docs/configuration/#validating-the-configuration
+ title: Validating the configuration
---
-Test any changes to your `configuration.yaml` file before launching Home Assistant. This {% term script %} allows you to test changes without the need to restart Home Assistant.
+Test any changes to your `configuration.yaml` file before launching Home Assistant. This script allows you to test changes without the need to restart Home Assistant.
```bash
hass --script check_config
diff --git a/source/_docs/troubleshooting_general.markdown b/source/_docs/troubleshooting_general.markdown
index e50d69b8245..9180465edbd 100644
--- a/source/_docs/troubleshooting_general.markdown
+++ b/source/_docs/troubleshooting_general.markdown
@@ -1,6 +1,13 @@
---
title: "General troubleshooting"
description: "General troubleshooting information"
+related:
+ - docs: /docs/configuration/#editing-configurationyaml
+ title: Editing your configuration
+ - docs: /integrations/recovery_mode/
+ title: Recovery mode integration
+ - docs: /docs/locked_out/
+ title: Resetting your password
---
This page provides some information about more generic troubleshooting topics.
@@ -23,7 +30,7 @@ Recovery mode loads a minimum set of integrations to allow troubleshooting the c
You need to identify the issue in the configuration files and fix it there. The issue could be caused by something as simple as an invalid YAML file.
-- If you are running Home Assistant Operating System, you can install an add-on such as VS code to edit the configuration file if needed.
+- If you are running {% term "Home Assistant Operating System" %}, you can install an add-on such as VS code to edit the configuration file if needed.
- If you are still logged in, you can [edit your configuration](/docs/configuration/#editing-configurationyaml).
- In the Home Assistant user interface, open the add-on you usually use and edit the configuration file.
- Restart Home Assistant.
@@ -35,9 +42,3 @@ If your Home Assistant is acting up and you cannot identify a root cause, you ca
Safe mode loads Home Assistant Core, but no custom integrations, no custom cards, and no custom themes. If the issue does not persist in Safe mode, the issue is not with Home Assistant Core. Before reporting an issue, check if the issue persists in Safe mode.
To enable Safe mode, go to **Settings** > **System** > **Restart Home Assistant** (top right) > **Restart Home Assistant in safe mode**.
-
-## Related topics
-
-- [Editing your configuration](/docs/configuration/#editing-configurationyaml)
-- [Recovery mode integration](/integrations/recovery_mode/)
-- [Resetting your password](/docs/locked_out/)
\ No newline at end of file
diff --git a/source/_docs/z-wave/controllers.markdown b/source/_docs/z-wave/controllers.markdown
index 6f38d7184ba..b5f00710808 100644
--- a/source/_docs/z-wave/controllers.markdown
+++ b/source/_docs/z-wave/controllers.markdown
@@ -66,12 +66,7 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
### 800 Series Controllers
-Z-Wave JS and Z-Wave JS UI do not support the following features available on most 800 series controllers.
-
-Unsupported:
-
- - Long Range
- - NVM Backup/Restore
+Z-Wave JS does not support Z-Wave Long Range yet.
### Aeotec Z-Stick
@@ -89,8 +84,8 @@ On Raspberry Pi 3 and 4, you need to disable the on-board Bluetooth since the bo
For both processes below you will need to insert your SD card into your PC and open the configuration file with your favorite text editor.
-- If you are using Home Assistant Operating System, once you mounted the disk, you will see the `config.txt` directly in the root directory.
-- If you are using Home Assistant Supervised, the config file is stored in the boot folder: `/boot/config.txt`.
+- If you are using {% term "Home Assistant Operating System" %}, once you mounted the disk, you will see the `config.txt` directly in the root directory.
+- If you are using {% term "Home Assistant Supervised" %}, the config file is stored in the boot folder: `/boot/config.txt`.
#### Raspberry Pi 5 procedure
diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html
index 8e38fa42ea7..5e7aa5c9a9f 100644
--- a/source/_includes/asides/docs_navigation.html
+++ b/source/_includes/asides/docs_navigation.html
@@ -31,9 +31,10 @@
-
-
- {% active_link /docs/configuration/yaml/ YAML %} +
- {% active_link /docs/configuration/ Configuration.yaml %} +
- {% active_link /docs/configuration/yaml/ YAML syntax%}
- {% active_link /docs/configuration/basic/ Basic information %} @@ -186,4 +187,4 @@
Organizing
-
-
- {% active_link /docs/organizing/ Organizing your assets %} +
- {% active_link /docs/organizing/ Grouping your assets %} +
- {% active_link /docs/organizing/filtering Filtering your assets %}
- {% active_link /docs/organizing/areas/ Areas %} diff --git a/source/_includes/common-tasks/backups.md b/source/_includes/common-tasks/backups.md index d5d2c4b121a..1d8d64dcbf3 100644 --- a/source/_includes/common-tasks/backups.md +++ b/source/_includes/common-tasks/backups.md @@ -1,6 +1,8 @@ ## Backups -Backup of your Home Assistant and add-on data and configuration. They are stored in a compressed archive file (.tar). Backups are made from the backups panel under {% my supervisor_backups title="**Settings** > **System** > **Backups**" %}. There is also a service available that allows you to trigger the creation of a backup from an automation. By default, backups are stored locally in the `/backup` directory. +Backup of your Home Assistant, add-on data, and configuration. Backups are used to [restore](#restoring-a-backup) a system or parts of it if a rollback is needed or to migrate your Home Assistant to new hardware. It is good practice to create a backup before updating. + +Backups are made from the backups panel under {% my supervisor_backups title="**Settings** > **System** > **Backups**" %}. There is also a [service](/integrations/hassio/#service-hassiobackup_full) available that allows you to trigger the creation of a backup from an automation. Backups are stored in a compressed archive file (.tar) and by default, stored locally in the `/backup` directory. A full backup includes the following directories: @@ -26,7 +28,9 @@ A partial backup consists of any number of the above default directories and ins 1. Go to {% my supervisor_backups title="**Settings** > **System** > **Backups**" %} in the UI. 2. Select the **Create backup** button in the lower right. 3. Provide a name for the backup. -4. Choose full or partial. +4. Choose **Full backup** or **Partial backup**. + - If you choose **Partial backup**, make sure to select Home Assistant and all the folders and add-ons you want to backup or migrate. + - Note that the number of add-ons increases the size of the backup as well as the time it takes to restore from that backup. 5. Optionally, enable password protection. 6. Select **Create** to begin the backup. diff --git a/source/_includes/common-tasks/commandline.md b/source/_includes/common-tasks/commandline.md index 455bb86d9da..8505c66f962 100644 --- a/source/_includes/common-tasks/commandline.md +++ b/source/_includes/common-tasks/commandline.md @@ -1,10 +1,5 @@ ## Home Assistant via the command line -
-
-Home Assistant upgrade process from the SSH command line
-
+ 
+ Screenshot showing coordinates cannot be edited because they are defined in configuration.yaml file.
+
+ 
+ Screencast showing how to add a new Matter device to Home Assistant.
+
+ 
+ Screencast showing how to share a Matter device from Apple Home.
+
diff --git a/source/_integrations/switchbot.markdown b/source/_integrations/switchbot.markdown
index 35f23a9debb..4308417ac8b 100644
--- a/source/_integrations/switchbot.markdown
+++ b/source/_integrations/switchbot.markdown
@@ -62,7 +62,7 @@ Some SwitchBot devices need to be configured within the app before being control
- [Indoor/Outdoor Meter](https://switch-bot.com/pages/switchbot-indoor-outdoor-thermo-hygrometer) (WoIOSensorTH)
- [Motion Sensor (WoPresence)](https://switch-bot.com/pages/switchbot-motion-sensor)
- Plug Mini (WoPlug), both the original (model W1901400) and HomeKit-enabled (model W1901401)
-- [Lock (WoLock)](https://switch-bot.com/pages/switchbot-lock)
+- [Lock (WoLock)](https://switch-bot.com/pages/switchbot-lock) (currently the Pro model is not supported)
- [Blind Tilt (WoBlindTilt)](https://switch-bot.com/pages/switchbot-blind-tilt)
## SwitchBot Entity
diff --git a/source/_integrations/thread.markdown b/source/_integrations/thread.markdown
index 8b1b637c701..4793c54d4f2 100644
--- a/source/_integrations/thread.markdown
+++ b/source/_integrations/thread.markdown
@@ -12,6 +12,23 @@ ha_config_flow: true
ha_platforms:
- diagnostics
ha_zeroconf: true
+related:
+ - docs: /yellow/
+ title: Home Assistant Yellow - hub
+ - docs: /skyconnect/
+ title: Home Assistant SkyConnect - Zigbee/Thread USB stick
+ - docs: /integrations/matter/
+ title: Matter
+ - docs: /integrations/homekit_controller/
+ title: HomeKit
+ - docs: /integrations/matter/#adding-a-matter-device-to-home-assistant
+ title: Adding a Matter device to Home Assistant
+ - docs: /integrations/homekit_controller/#adding-a-homekit-device-through-thread
+ title: Adding an Apple HomeKit device through Thread
+ - url: https://skyconnect.home-assistant.io/procedures/enable-thread/
+ title: Enabling Thread on SkyConnect
+ - url: https://yellow.home-assistant.io/procedures/enable-thread/
+ title: Enabling Thread on Yellow
---
The Thread integration helps you track the different Thread networks in your home and store the Thread network credentials (similar to a Wi-Fi password). The Thread integration in Home Assistant is currently still a work in progress.
@@ -226,21 +243,3 @@ You can only set a Thread network as preferred if the credentials are known.
In the current implementation, having multiple TBRs from different vendors results in separate networks using different credentials. This prevents devices from roaming between the Thread networks. In theory, it would be better to join all Thread networks into a single network to increase the size of the mesh network. A dense mesh network should lead to better RF coverage and better link quality, which lowers transmission latencies, making communication faster.
-## Related topics
-
-### Related hardware
-
-- [Home Assistant Yellow](/yellow/) hub
-- [Home Assistant SkyConnect](/skyconnect/) Zigbee/Thread USB stick
-
-### Related integrations for smart home standards
-
-- [Matter](/integrations/matter/)
-- [HomeKit](/integrations/homekit_controller/)
-
-### Related guides
-
-- [Adding a Matter device to Home Assistant](/integrations/matter/#adding-a-matter-device-to-home-assistant)
-- [Adding an Apple HomeKit device through Thread](/integrations/homekit_controller/#adding-a-homekit-device-through-thread)
-- [Enabling Thread on SkyConnect](https://skyconnect.home-assistant.io/procedures/enable-thread/)
-- [Enabling Thread on Yellow](https://yellow.home-assistant.io/procedures/enable-thread/)
diff --git a/source/_integrations/todo.markdown b/source/_integrations/todo.markdown
index c07dc406748..8799cfc8e9a 100644
--- a/source/_integrations/todo.markdown
+++ b/source/_integrations/todo.markdown
@@ -9,6 +9,11 @@ ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
ha_integration_type: entity
+related:
+ - docs: /integrations/local_todo
+ title: Local to-do list integration documentation
+ - docs: /dashboards/todo-list/
+ title: To-do list card
---
The **To-do list** {% term integration %} provides to-do list {% term entities %}, allowing other integrations
@@ -46,9 +51,9 @@ services provided by some to-do list entities are described below or you can rea
Get to-do items from a to-do list. A to-do list `target` is selected with a [target selector](/docs/blueprint/selectors/#target-selector). The `data` payload supports the following fields:
-| Service data attribute | Optional | Description | Example |
-| ---------------------- | -------- | ----------- | --------|
-| `status` | yes | Only return to-do items with this status. | `needs_action`, `completed`
+| Service data attribute | Optional | Description | Example |
+| ---------------------- | -------- | ----------------------------------------- | --------------------------- |
+| `status` | yes | Only return to-do items with this status. | `needs_action`, `completed` |
This is a full example that returns all to-do items that have not been completed:
@@ -65,12 +70,12 @@ data:
Add a new to-do item. A to-do list `target` is selected with a [Target Selector](/docs/blueprint/selectors/#target-selector) and the `data` payload supports the following fields:
-| Service data attribute | Optional | Description | Example |
-| ---------------------- | -------- | ----------- | --------|
-| `item` | no | the name of the to-do Item. | Submit income tax return
-| `due_date` | yes | The date the to-do item is expected to be completed. | 2024-04-10
-| `due_datetime` | yes | The date and time the to-do item is expected to be completed. | 2024-04-10 23:00:00
-| `description` | yes | A more complete description than the one provided by the summary | Collect all necessary documents and submit the final return.
+| Service data attribute | Optional | Description | Example |
+| ---------------------- | -------- | ---------------------------------------------------------------- | ------------------------------------------------------------ |
+| `item` | no | the name of the to-do Item. | Submit income tax return |
+| `due_date` | yes | The date the to-do item is expected to be completed. | 2024-04-10 |
+| `due_datetime` | yes | The date and time the to-do item is expected to be completed. | 2024-04-10 23:00:00 |
+| `description` | yes | A more complete description than the one provided by the summary | Collect all necessary documents and submit the final return. |
Only one of `due_date` or `due_datetime` may be specified.
@@ -90,14 +95,14 @@ data:
Update a to-do item. A to-do list `target` is selected with a [Target Selector](/docs/blueprint/selectors/#target-selector) and the `data` payload supports the following fields:
-| Service data attribute | Optional | Description | Example |
-| ---------------------- | -------- | ----------- | --------|
-| `item` | no | The name of the to-do Item to update. | Submit income tax return
-| `rename` | yes | The new name of the to-do Item. | Something else
-| `status` | yes | The overall status of the To-do Item. | `needs_action` or `completed`
-| `due_date` | yes | The date the to-do item is expected to be completed. | 2024-04-10
-| `due_datetime` | yes | The date and time the to-do item is expected to be completed. | 2024-04-10 23:00:00
-| `description` | yes | A more complete description than the one provided by the summary. | Collect all necessary documents and submit the final return.
+| Service data attribute | Optional | Description | Example |
+| ---------------------- | -------- | ----------------------------------------------------------------- | ------------------------------------------------------------ |
+| `item` | no | The name of the to-do Item to update. | Submit income tax return |
+| `rename` | yes | The new name of the to-do Item. | Something else |
+| `status` | yes | The overall status of the To-do Item. | `needs_action` or `completed` |
+| `due_date` | yes | The date the to-do item is expected to be completed. | 2024-04-10 |
+| `due_datetime` | yes | The date and time the to-do item is expected to be completed. | 2024-04-10 23:00:00 |
+| `description` | yes | A more complete description than the one provided by the summary. | Collect all necessary documents and submit the final return. |
At least one of `rename` or `status` is required. Only one of `due_date` or `due_datetime` may be specified. This is a full example of a service call that updates the status and the name of a to-do item.
@@ -115,9 +120,9 @@ data:
Removing a to-do item. A to-do list `target` is selected with a [Target Selector](/docs/blueprint/selectors/#target-selector), and the `data` payload supports the following fields:
-| Service data attribute | Optional | Description | Example |
-| ---------------------- | -------- | ----------- | --------|
-| `item` | no | The name of the to-do item. | Submit income tax return
+| Service data attribute | Optional | Description | Example |
+| ---------------------- | -------- | --------------------------- | ------------------------ |
+| `item` | no | The name of the to-do item. | Submit income tax return |
This is a full example of a service call that deletes a to-do Item with the specified name.
@@ -140,8 +145,3 @@ service: todo.remove_completed_items
target:
entity_id: todo.personal_tasks
```
-
-## Related topics
-
-- [Local to-do integration](/integrations/local_todo/)
-- [To-do list card](/dashboards/todo-list/)
diff --git a/source/_integrations/todoist.markdown b/source/_integrations/todoist.markdown
index 654890c4a28..127d9401328 100644
--- a/source/_integrations/todoist.markdown
+++ b/source/_integrations/todoist.markdown
@@ -14,6 +14,19 @@ ha_platforms:
- todo
ha_integration_type: integration
ha_config_flow: true
+related:
+ - docs: /integrations/todo
+ title: To-do list integration documentation
+ - docs: /integrations/#to-do-list
+ title: List of to-do list integrations
+ - docs: /dashboards/todo-list/
+ title: To-do list card
+ - docs: /dashboards/dashboards/
+ title: Dashboards
+ - docs: /integrations/calendar/
+ title: Calendar
+ - url: https://todoist.com
+ title: Todoist projects
---
This platform allows you to connect to your [Todoist projects](https://todoist.com) as [todo](/integrations/todo/) or [calendar](/integrations/calendar/) entities. All tasks get updated roughly every 15 minutes.
@@ -194,15 +207,3 @@ Here are two example JSON payloads resulting in the same task:
Valid languages are: `en`, `da`, `pl`, `zh`, `ko`, `de`, `pt`, `ja`, `it`, `fr`, `sv`, `ru`, `es`, `nl`
- **reminder_date** (*Optional*): When should the user be reminded of this task, in either YYYY-MM-DD format or YYYY-MM-DD HH:MM format (in UTC timezone). Mutually exclusive with `reminder_date_string`.
-
-## Related topics
-
-- [Todoist projects](https://todoist.com)
-- [Calendar](/integrations/calendar/)
-
-## To-do list
-
-- [To-do list integration documentation](/integrations/todo)
-- [List of to-do list integrations](/integrations/#to-do-list)
-- [To-do list card](/dashboards/todo-list/)-
-- [Dashboards](/dashboards/dashboards/)
diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown
index 767e1e9f710..6ec871c023e 100644
--- a/source/_integrations/tplink.markdown
+++ b/source/_integrations/tplink.markdown
@@ -116,7 +116,8 @@ Devices not listed below may work but if you encounter issues submit a bug repor
- L510B
- L530E
-
+- TL135E
+
#### Light strips
- L900-5
diff --git a/source/_integrations/tts.markdown b/source/_integrations/tts.markdown
index c3f4e8bc000..6c4fc263f88 100644
--- a/source/_integrations/tts.markdown
+++ b/source/_integrations/tts.markdown
@@ -12,6 +12,17 @@ ha_quality_scale: internal
ha_platforms:
- notify
ha_integration_type: entity
+related:
+ - url: https://www.home-assistant.io/integrations/#text-to-speech
+ title: List of integrations using the TTS integration
+ - url: https://www.nabucasa.com/config/tts/
+ title: TTS with Home Assistant Cloud
+ - url: https://www.home-assistant.io/integrations/google_translate/
+ title: Google Translate TTS
+ - url: https://www.home-assistant.io/integrations/microsoft/
+ title: Microsoft TTS
+ - url: https://www.home-assistant.io/voice_control/
+ title: Home Assistant Assist
---
Text-to-speech (TTS) enables Home Assistant to speak to you.
@@ -143,11 +154,3 @@ The Google cast devices (Google Home, Chromecast, etc.) present the following pr
- They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). If you are _not_ using SSL then setting an internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname.
- If you are using SSL (e.g., `https://yourhost.example.org/...`) then you _must_ use the hostname in the certificate (e.g., `external_url: https://yourhost.example.org`). You cannot use an IP address since the certificate won't be valid for the IP address, and the cast device will refuse the connection.
-
-### Related topics
-
-- [List of integrations using the TTS integration](https://www.home-assistant.io/integrations/#text-to-speech)
-- [TTS with Home Assistant Cloud](https://www.nabucasa.com/config/tts/)
-- [Google Translate TTS](https://www.home-assistant.io/integrations/google_translate/)
-- [Microsoft TTS](https://www.home-assistant.io/integrations/microsoft/)
-- [Home Assistant Assist](https://www.home-assistant.io/voice_control/)
diff --git a/source/_integrations/twitch.markdown b/source/_integrations/twitch.markdown
index 2e07e18c2f4..f6dcd84459b 100644
--- a/source/_integrations/twitch.markdown
+++ b/source/_integrations/twitch.markdown
@@ -18,6 +18,10 @@ The Twitch integration will allow you to monitor [Twitch](https://www.twitch.tv/
## Get Twitch application credentials
-Create a new app at **Register Your Application** in the [Twitch developer portal](https://dev.twitch.tv/console/apps). Enter `https://my.home-assistant.io/redirect/oauth` in the **OAuth Redirect URL** field. Then, get the **Client ID** and **Client secret** from the new application.
+Create a new app at **Register Your Application** in the [Twitch developer portal](https://dev.twitch.tv/console/apps):
+
+- Enter a **Name** for your app. Note that it needs to be unique all over Twitch.
+- Enter `https://my.home-assistant.io/redirect/oauth` in the **OAuth Redirect URL** field.
+- Get the **Client ID** and **Client secret** from the new application, you need them to complete the integration setup in Home Assistant.
{% include integrations/config_flow.md %}
diff --git a/source/_integrations/universal.markdown b/source/_integrations/universal.markdown
index 5838f0199e3..b2fb1e6959d 100644
--- a/source/_integrations/universal.markdown
+++ b/source/_integrations/universal.markdown
@@ -327,6 +327,61 @@ media_player:
{% endraw %}
+### Denon AVR & HEOS
+
+This media player combines the media players provided by the [Denon AVR](/integrations/denonavr/) and [HEOS](/integrations/heos/) integrations.
+
+Features:
+- Volume control via Denon entity (might be more fine-granular than HEOS volume control)
+- ON/OFF button via Denon entity (not provided by HEOS media player)
+- Sound mode selector via Denon entity (not provided by HEOS media player)
+- Album art & Metadata via HEOS entity (not provided by Denon media player)
+
+The complete configuration is:
+
+{% raw %}
+
+```yaml
+media_player:
+ - platform: universal
+ name: Denon
+ unique_id: denon_universal_remote
+ device_class: receiver
+ children:
+ - media_player.denon_avr_x2700h # Denon AVR Integration entity
+ - media_player.denon_avr_x2700h_heos # Denon HEOS Integration entity
+ browse_media_entity: media_player.denon_avr_x2700h_heos
+ commands:
+ turn_off:
+ service: media_player.turn_off
+ data:
+ entity_id: media_player.denon_avr_x2700h
+ turn_on:
+ service: media_player.turn_on
+ data:
+ entity_id: media_player.denon_avr_x2700h
+ volume_up:
+ service: media_player.volume_up
+ data:
+ entity_id: media_player.denon_avr_x2700h
+ volume_down:
+ service: media_player.volume_down
+ data:
+ entity_id: media_player.denon_avr_x2700h
+ select_sound_mode:
+ service: media_player.select_sound_mode
+ target:
+ entity_id: media_player.denon_avr_x2700h
+ data:
+ sound_mode: "{{ sound_mode }}"
+ attributes:
+ sound_mode: media_player.denon_avr_x2700h|sound_mode
+ sound_mode_raw: media_player.denon_avr_x2700h|sound_mode_raw
+ sound_mode_list: media_player.denon_avr_x2700h|sound_mode_list
+```
+
+{% endraw %}
+
### Override active children
This example shows how you can use `active_child_template`:
diff --git a/source/_integrations/velux.markdown b/source/_integrations/velux.markdown
index 227140ccba9..430906870ca 100644
--- a/source/_integrations/velux.markdown
+++ b/source/_integrations/velux.markdown
@@ -30,6 +30,13 @@ There is currently support for the following device types within Home Assistant:
{% include integrations/config_flow.md %}
+During configuration, you will be asked for a hostname and password:
+
+- Hostname: enter the IP address of the KLF 200 gateway.
+- Password: enter the password of the gateway's wireless access point (printed on the underside - **not** the web login password).
+
+You must complete the configuration within 5 minutes of rebooting the KLF 200 gateway while the access point is still available.
+
## Services
### Service `velux.reboot_gateway`
diff --git a/source/_integrations/weather.template.markdown b/source/_integrations/weather.template.markdown
index 3787862b5f1..b5c8c7cb655 100644
--- a/source/_integrations/weather.template.markdown
+++ b/source/_integrations/weather.template.markdown
@@ -34,7 +34,7 @@ weather:
temperature_template: "{{ states('sensor.temperature') | float }}"
temperature_unit: "°C"
humidity_template: "{{ states('sensor.humidity') | float }}"
- forecast_daily_template: "{{ state_attr('weather.my_region', 'forecast') }}"
+ forecast_daily_template: "{{ state_attr('weather.my_region', 'forecast_data') }}"
```
{% endraw %}
@@ -116,10 +116,6 @@ visibility_unit:
description: Unit for visibility_template output. Valid options are km, mi, ft, m, cm, mm, in, yd.
required: false
type: string
-forecast_template:
- description: Forecast data.
- required: false
- type: template
forecast_daily_template:
description: Daily forecast data.
required: false
diff --git a/source/_integrations/whirlpool.markdown b/source/_integrations/whirlpool.markdown
index d634a034e3e..7ef99e50b5d 100644
--- a/source/_integrations/whirlpool.markdown
+++ b/source/_integrations/whirlpool.markdown
@@ -28,7 +28,7 @@ There is currently support for the following device types within Home Assistant:
## Supported hardware
-The following air conditioners are confirmed to be working, but other models that use the 6th Sense Live application may also work:
+The following appliances are confirmed to be working, but other models that use the 6th Sense Live application may also work:
Climate:
@@ -38,6 +38,7 @@ Climate:
Washer:
- WTW6120HW2
+- MHW8630HW0
Dryer:
diff --git a/source/_integrations/withings.markdown b/source/_integrations/withings.markdown
index 9fbc0ee4abe..2bbf743b617 100644
--- a/source/_integrations/withings.markdown
+++ b/source/_integrations/withings.markdown
@@ -57,6 +57,8 @@ Withings will validate (with HTTP HEAD) these requirements each time you save yo
{% enddetails %}
+Note: You will only need one developer account; the same account and credentials are used for each Withings configuration.
+
{% include integrations/config_flow.md %}
## Data updates
diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown
index 823b6081522..2a16e3f1761 100644
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@@ -106,6 +106,7 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
- [CC2652P/CC2652R/CC2652RB USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
- [CC1352P/CC1352R USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
- dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)
+ - [ConBee III (a.k.a. ConBee 3) USB adapter from dresden elektronik](https://phoscon.de/conbee3)
- [ConBee II (a.k.a. ConBee 2) USB adapter from dresden elektronik](https://phoscon.de/conbee2)
- [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee2)
diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index 9e8e9e6f046..307c8723d89 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -59,7 +59,7 @@ To run a Z-Wave network, you need the following elements:
### Setting up a Z-Wave JS server
-If you are running Home Assistant Operating System or Home Assistant Supervised, the easiest way to get started is by using the built-in Z-Wave JS add-on in Home Assistant.
+If you are running {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, the easiest way to get started is by using the built-in Z-Wave JS add-on in Home Assistant.
For other ways to setup a Z-Wave server, refer to the [advanced installation instructions](#advanced-installation-instructions).
@@ -726,13 +726,13 @@ The chart below illustrates Options 1 and 2, which are available for Home Assist
**Option 1: The official Z-Wave JS add-on, as described above**
-_This option is only available for Home Assistant OS (the recommended installation type) and Home Assistant Supervised installations._
+_This option is only available for {% term "Home Assistant Operating System" %} (the recommended installation type) and {% term "Home Assistant Supervised" %} installations._
This add-on can only be configured via the built-in Z-Wave control panel in Home Assistant. If you followed the standard [installation procedure](#setting-up-a-z-wave-js-server), this is how you are running the Z-Wave JS server.
**Option 2: The Z-Wave JS UI add-on installed from the community add-on store**
-_This option is only available for Home Assistant OS (the recommended installation type) and Home Assistant Supervised installations._
+_This option is only available for {% term "Home Assistant Operating System" %} (the recommended installation type) and {% term "Home Assistant Supervised" %} installations._
This add-on includes the Z-Wave JS Server as part of the Z-Wave JS UI application. The Z-Wave network can be configured via the built-in Z-Wave control panel in Home Assistant and alternatively via the Z-Wave control panel built into Z-Wave JS UI. It provides you with a full-fledged, attractive, and feature-complete UI to manage your Z-Wave nodes and settings, which may support more advanced use cases as development continues on the Z-Wave control panel.
diff --git a/source/_layouts/page.html b/source/_layouts/page.html
index 7d320b83a06..fb1122d4cff 100644
--- a/source/_layouts/page.html
+++ b/source/_layouts/page.html
@@ -35,5 +35,6 @@ layout: default
{% endif %}
{{ content }}
+ {% include related.html %}
{% include feedback.html %}
diff --git a/source/_posts/2024-04-03-release-20244.markdown b/source/_posts/2024-04-03-release-20244.markdown
index ae4f51ac8a2..64d6213de5b 100644
--- a/source/_posts/2024-04-03-release-20244.markdown
+++ b/source/_posts/2024-04-03-release-20244.markdown
@@ -56,6 +56,9 @@ Enjoy the release! 🌞
- [New integrations](#new-integrations)
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
- [Release 2024.4.1 - April 5](#release-202441---april-5)
+- [Release 2024.4.2 - April 8](#release-202442---april-8)
+- [Release 2024.4.3 - April 12](#release-202443---april-12)
+- [Release 2024.4.4 - April 23](#release-202444---april-23)
- [Need help? Join the community!](#need-help-join-the-community)
- [Backward-incompatible changes](#backward-incompatible-changes)
- [Farewell to the following](#farewell-to-the-following)
@@ -591,6 +594,209 @@ The following integrations are now available via the Home Assistant UI:
[@tronikos]: https://github.com/tronikos
[@xeniter]: https://github.com/xeniter
+## Release 2024.4.2 - April 8
+
+- Fix hang in SNMP device_tracker implementation ([@nmaggioni] - [#112815])
+- Fix missing if statement in homematic ([@bbr111] - [#114832])
+- Bump pylitterbot to 2023.4.11 ([@natekspencer] - [#114918])
+- Fix Snapcast Config flow ([@joostlek] - [#114952])
+- Bump axis to v61 ([@Kane610] - [#114964])
+- Filter out fuzzy translations from Lokalise ([@joostlek] - [#114968])
+- Upgrade to pynobo 1.8.1 ([@oyvindwe] - [#114982])
+- Fix dictionary changed size during iteration in prometheus ([@bdraco] - [#115005])
+- Bump `brother` to version 4.1.0 ([@bieniu] - [#115021])
+- Bump yolink-api to 0.4.2 ([@matrixd2] - [#115026])
+- Update xknxproject to 3.7.1 ([@farmio] - [#115053])
+- Fix synology_dsm availablity ([@bdraco] - [#115073])
+- Downgrade hass-nabucasa from 0.80.0 to 0.78.0 ([@ludeeus] - [#115078])
+- Bump velbus-aio to 2024.4.1 ([@Cereal2nd] - [#115109])
+- Terminate scripts with until and while conditions that execute more than 10000 times ([@bdraco] - [#115110])
+- improve handling of incorrect values in fyta integration ([@dontinelli] - [#115134])
+- Bump fyta_cli to 0.3.5 ([@dontinelli] - [#115143])
+- Fix fibaro sensor additional sensor lookup ([@rappenze] - [#115148])
+- Write timer entity state before firing events ([@bdraco] - [#115151])
+- Avoid checking for polling if an entity fails to add ([@bdraco] - [#115159])
+- Only reset requested utility meter with no tariff ([@gibwar] - [#115170])
+
+[#112815]: https://github.com/home-assistant/core/pull/112815
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114832]: https://github.com/home-assistant/core/pull/114832
+[#114918]: https://github.com/home-assistant/core/pull/114918
+[#114934]: https://github.com/home-assistant/core/pull/114934
+[#114952]: https://github.com/home-assistant/core/pull/114952
+[#114964]: https://github.com/home-assistant/core/pull/114964
+[#114968]: https://github.com/home-assistant/core/pull/114968
+[#114982]: https://github.com/home-assistant/core/pull/114982
+[#115005]: https://github.com/home-assistant/core/pull/115005
+[#115021]: https://github.com/home-assistant/core/pull/115021
+[#115026]: https://github.com/home-assistant/core/pull/115026
+[#115053]: https://github.com/home-assistant/core/pull/115053
+[#115073]: https://github.com/home-assistant/core/pull/115073
+[#115078]: https://github.com/home-assistant/core/pull/115078
+[#115109]: https://github.com/home-assistant/core/pull/115109
+[#115110]: https://github.com/home-assistant/core/pull/115110
+[#115134]: https://github.com/home-assistant/core/pull/115134
+[#115143]: https://github.com/home-assistant/core/pull/115143
+[#115148]: https://github.com/home-assistant/core/pull/115148
+[#115151]: https://github.com/home-assistant/core/pull/115151
+[#115159]: https://github.com/home-assistant/core/pull/115159
+[#115170]: https://github.com/home-assistant/core/pull/115170
+[@Cereal2nd]: https://github.com/Cereal2nd
+[@Kane610]: https://github.com/Kane610
+[@bbr111]: https://github.com/bbr111
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@dontinelli]: https://github.com/dontinelli
+[@farmio]: https://github.com/farmio
+[@frenck]: https://github.com/frenck
+[@gibwar]: https://github.com/gibwar
+[@joostlek]: https://github.com/joostlek
+[@ludeeus]: https://github.com/ludeeus
+[@matrixd2]: https://github.com/matrixd2
+[@natekspencer]: https://github.com/natekspencer
+[@nmaggioni]: https://github.com/nmaggioni
+[@oyvindwe]: https://github.com/oyvindwe
+[@rappenze]: https://github.com/rappenze
+
+## Release 2024.4.3 - April 12
+
+- Bump aiohttp to 3.9.4 ([@bdraco] - [#110730])
+- Add support for adopt data disk repair ([@mdegat01] - [#114891])
+- Improve Risco exception logging ([@OnFreund] - [#115232])
+- Configurable maximum concurrency in Risco local ([@OnFreund] - [#115226])
+- Fix misssing timeout in caldav ([@bdraco] - [#115247])
+- Fix Google Tasks parsing of remove responses ([@allenporter] - [#115258])
+- Bump forecast-solar lib to v3.1.0 ([@klaasnicolaas] - [#115272])
+- Support backup of add-ons with hyphens ([@agners] - [#115274])
+- Bump pymodbus v3.6.7 ([@janiversen] - [#115279])
+- Bump yt-dlp to 2024.04.09 ([@joostlek] - [#115295])
+- Fix Aranet failure when the Bluetooth proxy is not providing a device name ([@thecode] - [#115298])
+- Bump zha-quirks to 0.0.114 ([@TheJulianJES] - [#115299])
+- Ensure automations do not execute from a trigger if they are disabled ([@bdraco] - [#115305])
+- Bump bleak-retry-connector 3.5.0 ([@bdraco] - [#115328])
+- Secure against resetting a non active modbus ([@janiversen] - [#115364])
+- Solve modbus test problem ([@janiversen] - [#115376])
+- Fix deadlock in holidays dynamic loading ([@bdraco] - [#115385])
+- Bump whirlpool-sixth-sense to 0.18.8 ([@NodeJSmith] - [#115393])
+- Fix bug in rainbird switch when turning off a switch that is already off ([@allenporter] - [#115421])
+- Bump pybotvac to 0.0.25 ([@Santobert] - [#115435])
+- Update frontend to 20240404.2 ([@bramkragten] - [#115460])
+
+[#110730]: https://github.com/home-assistant/core/pull/110730
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114891]: https://github.com/home-assistant/core/pull/114891
+[#114934]: https://github.com/home-assistant/core/pull/114934
+[#115186]: https://github.com/home-assistant/core/pull/115186
+[#115226]: https://github.com/home-assistant/core/pull/115226
+[#115232]: https://github.com/home-assistant/core/pull/115232
+[#115247]: https://github.com/home-assistant/core/pull/115247
+[#115258]: https://github.com/home-assistant/core/pull/115258
+[#115272]: https://github.com/home-assistant/core/pull/115272
+[#115274]: https://github.com/home-assistant/core/pull/115274
+[#115279]: https://github.com/home-assistant/core/pull/115279
+[#115295]: https://github.com/home-assistant/core/pull/115295
+[#115298]: https://github.com/home-assistant/core/pull/115298
+[#115299]: https://github.com/home-assistant/core/pull/115299
+[#115305]: https://github.com/home-assistant/core/pull/115305
+[#115328]: https://github.com/home-assistant/core/pull/115328
+[#115364]: https://github.com/home-assistant/core/pull/115364
+[#115376]: https://github.com/home-assistant/core/pull/115376
+[#115385]: https://github.com/home-assistant/core/pull/115385
+[#115393]: https://github.com/home-assistant/core/pull/115393
+[#115421]: https://github.com/home-assistant/core/pull/115421
+[#115435]: https://github.com/home-assistant/core/pull/115435
+[#115460]: https://github.com/home-assistant/core/pull/115460
+[@NodeJSmith]: https://github.com/NodeJSmith
+[@OnFreund]: https://github.com/OnFreund
+[@Santobert]: https://github.com/Santobert
+[@TheJulianJES]: https://github.com/TheJulianJES
+[@agners]: https://github.com/agners
+[@allenporter]: https://github.com/allenporter
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@frenck]: https://github.com/frenck
+[@janiversen]: https://github.com/janiversen
+[@joostlek]: https://github.com/joostlek
+[@klaasnicolaas]: https://github.com/klaasnicolaas
+[@mdegat01]: https://github.com/mdegat01
+[@thecode]: https://github.com/thecode
+
+## Release 2024.4.4 - April 23
+
+- Bump slixmpp version to 1.8.5 ([@ravermeister] - [#114448])
+- Make Withings recoverable after internet outage ([@joostlek] - [#115124])
+- Fix Hyperion light not updating state ([@avee87] - [#115389])
+- Add scheduled mode to renault charge mode ([@slyoldfox] - [#115427])
+- Bump zeroconf to 0.132.1 ([@bdraco] - [#115501])
+- Bump zeroconf to 0.132.2 ([@bdraco] - [#115505])
+- Update pillow to 10.3.0 ([@cdce8p] - [#115524])
+- Fix race in TimestampDataUpdateCoordinator ([@bdraco] - [#115542])
+- Fix Teslemetry sensor values ([@Bre77] - [#115571])
+- Modbus: Bump pymodbus v3.6.8 ([@janiversen] - [#115574])
+- Fix sensor entity description in Teslemetry ([@Bre77] - [#115614])
+- Bump httpcore to 1.0.5 ([@bdraco] - [#115672])
+- Bump sqlparse to 0.5.0 ([@bdraco] - [#115681])
+- Bump aiohttp to 3.9.5 ([@bdraco] - [#115727])
+- Bump renault-api to 0.2.2 ([@epenet] - [#115738])
+- Fix homeworks import flow ([@emontnemery] - [#115761])
+- Allow [##:##:##] type keypad address in homeworks ([@emontnemery] - [#115762])
+- Add missing media_player features to Samsung TV ([@chemelli74] - [#115788])
+- Bump aiounifi to v75 ([@Kane610] - [#115819])
+- Ensure scripts with timeouts of zero timeout immediately ([@bdraco] - [#115830])
+- Fix KeyError error when fetching sensors (Airthings) ([@LaStrada] - [#115844])
+- Bump plexapi to 4.15.12 ([@jjlawren] - [#115872])
+- Bump ical to 8.0.0 ([@allenporter] - [#115907])
+- Fix geo location attributes of Tankerkoenig sensors ([@mib1185] - [#115914])
+- Use start helper in squeezebox for server discovery ([@rajlaud] - [#115978])
+
+[#114448]: https://github.com/home-assistant/core/pull/114448
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114934]: https://github.com/home-assistant/core/pull/114934
+[#115124]: https://github.com/home-assistant/core/pull/115124
+[#115186]: https://github.com/home-assistant/core/pull/115186
+[#115389]: https://github.com/home-assistant/core/pull/115389
+[#115427]: https://github.com/home-assistant/core/pull/115427
+[#115463]: https://github.com/home-assistant/core/pull/115463
+[#115501]: https://github.com/home-assistant/core/pull/115501
+[#115505]: https://github.com/home-assistant/core/pull/115505
+[#115524]: https://github.com/home-assistant/core/pull/115524
+[#115542]: https://github.com/home-assistant/core/pull/115542
+[#115571]: https://github.com/home-assistant/core/pull/115571
+[#115574]: https://github.com/home-assistant/core/pull/115574
+[#115614]: https://github.com/home-assistant/core/pull/115614
+[#115672]: https://github.com/home-assistant/core/pull/115672
+[#115681]: https://github.com/home-assistant/core/pull/115681
+[#115727]: https://github.com/home-assistant/core/pull/115727
+[#115738]: https://github.com/home-assistant/core/pull/115738
+[#115761]: https://github.com/home-assistant/core/pull/115761
+[#115762]: https://github.com/home-assistant/core/pull/115762
+[#115788]: https://github.com/home-assistant/core/pull/115788
+[#115819]: https://github.com/home-assistant/core/pull/115819
+[#115830]: https://github.com/home-assistant/core/pull/115830
+[#115844]: https://github.com/home-assistant/core/pull/115844
+[#115872]: https://github.com/home-assistant/core/pull/115872
+[#115907]: https://github.com/home-assistant/core/pull/115907
+[#115914]: https://github.com/home-assistant/core/pull/115914
+[#115978]: https://github.com/home-assistant/core/pull/115978
+[@Bre77]: https://github.com/Bre77
+[@Kane610]: https://github.com/Kane610
+[@LaStrada]: https://github.com/LaStrada
+[@allenporter]: https://github.com/allenporter
+[@avee87]: https://github.com/avee87
+[@bdraco]: https://github.com/bdraco
+[@cdce8p]: https://github.com/cdce8p
+[@chemelli74]: https://github.com/chemelli74
+[@emontnemery]: https://github.com/emontnemery
+[@epenet]: https://github.com/epenet
+[@frenck]: https://github.com/frenck
+[@janiversen]: https://github.com/janiversen
+[@jjlawren]: https://github.com/jjlawren
+[@joostlek]: https://github.com/joostlek
+[@mib1185]: https://github.com/mib1185
+[@rajlaud]: https://github.com/rajlaud
+[@ravermeister]: https://github.com/ravermeister
+[@slyoldfox]: https://github.com/slyoldfox
+
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
diff --git a/source/_redirects b/source/_redirects
index 60482f94b68..4bb068f835f 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -329,7 +329,6 @@ layout: null
/getting-started/automation-trigger /docs/automation/trigger
/getting-started/automation-templating /docs/automation/templating
/getting-started/basic /docs/configuration/basic
-/getting-started/browsers /docs/frontend/browsers
/getting-started/customizing-devices /docs/configuration/customizing-devices
/getting-started/installation /docs/installation
/getting-started/installation-docker /docs/installation/docker
@@ -357,6 +356,8 @@ layout: null
/topics/state_object /docs/configuration/state_object
/topics/templating /docs/configuration/templating
/common-tasks /common-tasks/os
+/common-tasks/os/#flashing-an-odroid-m1s /installation/odroid#flashing-an-odroid-m1s
+/common-tasks/os/#flashing-an-odroid-n2 /installation/odroid#flashing-an-odroid-n2
/docs/installation /installation
/docs/installation/docker /installation
/docs/installation/raspberry-pi /installation
@@ -560,6 +561,7 @@ layout: null
/integrations/opencv /more-info/removed-integration 301
/integrations/orangepi_gpio /more-info/removed-integration 301
/integrations/ozw /more-info/removed-integration 301
+/integrations/panel_iframe /more-info/removed-integration 301
/integrations/pcal9535a /more-info/removed-integration 301
/integrations/pi4ioe5v9xxxx /more-info/removed-integration 301
/integrations/piglow /more-info/removed-integration 301
diff --git a/source/changelogs/core-2024.4.markdown b/source/changelogs/core-2024.4.markdown
index 28da47b151b..a7d0caa5d98 100644
--- a/source/changelogs/core-2024.4.markdown
+++ b/source/changelogs/core-2024.4.markdown
@@ -1581,6 +1581,209 @@ For a summary in a more readable format:
[@tronikos]: https://github.com/tronikos
[@xeniter]: https://github.com/xeniter
+## Release 2024.4.2 - April 8
+
+- Fix hang in SNMP device_tracker implementation ([@nmaggioni] - [#112815])
+- Fix missing if statement in homematic ([@bbr111] - [#114832])
+- Bump pylitterbot to 2023.4.11 ([@natekspencer] - [#114918])
+- Fix Snapcast Config flow ([@joostlek] - [#114952])
+- Bump axis to v61 ([@Kane610] - [#114964])
+- Filter out fuzzy translations from Lokalise ([@joostlek] - [#114968])
+- Upgrade to pynobo 1.8.1 ([@oyvindwe] - [#114982])
+- Fix dictionary changed size during iteration in prometheus ([@bdraco] - [#115005])
+- Bump `brother` to version 4.1.0 ([@bieniu] - [#115021])
+- Bump yolink-api to 0.4.2 ([@matrixd2] - [#115026])
+- Update xknxproject to 3.7.1 ([@farmio] - [#115053])
+- Fix synology_dsm availablity ([@bdraco] - [#115073])
+- Downgrade hass-nabucasa from 0.80.0 to 0.78.0 ([@ludeeus] - [#115078])
+- Bump velbus-aio to 2024.4.1 ([@Cereal2nd] - [#115109])
+- Terminate scripts with until and while conditions that execute more than 10000 times ([@bdraco] - [#115110])
+- improve handling of incorrect values in fyta integration ([@dontinelli] - [#115134])
+- Bump fyta_cli to 0.3.5 ([@dontinelli] - [#115143])
+- Fix fibaro sensor additional sensor lookup ([@rappenze] - [#115148])
+- Write timer entity state before firing events ([@bdraco] - [#115151])
+- Avoid checking for polling if an entity fails to add ([@bdraco] - [#115159])
+- Only reset requested utility meter with no tariff ([@gibwar] - [#115170])
+
+[#112815]: https://github.com/home-assistant/core/pull/112815
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114832]: https://github.com/home-assistant/core/pull/114832
+[#114918]: https://github.com/home-assistant/core/pull/114918
+[#114934]: https://github.com/home-assistant/core/pull/114934
+[#114952]: https://github.com/home-assistant/core/pull/114952
+[#114964]: https://github.com/home-assistant/core/pull/114964
+[#114968]: https://github.com/home-assistant/core/pull/114968
+[#114982]: https://github.com/home-assistant/core/pull/114982
+[#115005]: https://github.com/home-assistant/core/pull/115005
+[#115021]: https://github.com/home-assistant/core/pull/115021
+[#115026]: https://github.com/home-assistant/core/pull/115026
+[#115053]: https://github.com/home-assistant/core/pull/115053
+[#115073]: https://github.com/home-assistant/core/pull/115073
+[#115078]: https://github.com/home-assistant/core/pull/115078
+[#115109]: https://github.com/home-assistant/core/pull/115109
+[#115110]: https://github.com/home-assistant/core/pull/115110
+[#115134]: https://github.com/home-assistant/core/pull/115134
+[#115143]: https://github.com/home-assistant/core/pull/115143
+[#115148]: https://github.com/home-assistant/core/pull/115148
+[#115151]: https://github.com/home-assistant/core/pull/115151
+[#115159]: https://github.com/home-assistant/core/pull/115159
+[#115170]: https://github.com/home-assistant/core/pull/115170
+[@Cereal2nd]: https://github.com/Cereal2nd
+[@Kane610]: https://github.com/Kane610
+[@bbr111]: https://github.com/bbr111
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@dontinelli]: https://github.com/dontinelli
+[@farmio]: https://github.com/farmio
+[@frenck]: https://github.com/frenck
+[@gibwar]: https://github.com/gibwar
+[@joostlek]: https://github.com/joostlek
+[@ludeeus]: https://github.com/ludeeus
+[@matrixd2]: https://github.com/matrixd2
+[@natekspencer]: https://github.com/natekspencer
+[@nmaggioni]: https://github.com/nmaggioni
+[@oyvindwe]: https://github.com/oyvindwe
+[@rappenze]: https://github.com/rappenze
+
+## Release 2024.4.3 - April 12
+
+- Bump aiohttp to 3.9.4 ([@bdraco] - [#110730])
+- Add support for adopt data disk repair ([@mdegat01] - [#114891])
+- Improve Risco exception logging ([@OnFreund] - [#115232])
+- Configurable maximum concurrency in Risco local ([@OnFreund] - [#115226])
+- Fix misssing timeout in caldav ([@bdraco] - [#115247])
+- Fix Google Tasks parsing of remove responses ([@allenporter] - [#115258])
+- Bump forecast-solar lib to v3.1.0 ([@klaasnicolaas] - [#115272])
+- Support backup of add-ons with hyphens ([@agners] - [#115274])
+- Bump pymodbus v3.6.7 ([@janiversen] - [#115279])
+- Bump yt-dlp to 2024.04.09 ([@joostlek] - [#115295])
+- Fix Aranet failure when the Bluetooth proxy is not providing a device name ([@thecode] - [#115298])
+- Bump zha-quirks to 0.0.114 ([@TheJulianJES] - [#115299])
+- Ensure automations do not execute from a trigger if they are disabled ([@bdraco] - [#115305])
+- Bump bleak-retry-connector 3.5.0 ([@bdraco] - [#115328])
+- Secure against resetting a non active modbus ([@janiversen] - [#115364])
+- Solve modbus test problem ([@janiversen] - [#115376])
+- Fix deadlock in holidays dynamic loading ([@bdraco] - [#115385])
+- Bump whirlpool-sixth-sense to 0.18.8 ([@NodeJSmith] - [#115393])
+- Fix bug in rainbird switch when turning off a switch that is already off ([@allenporter] - [#115421])
+- Bump pybotvac to 0.0.25 ([@Santobert] - [#115435])
+- Update frontend to 20240404.2 ([@bramkragten] - [#115460])
+
+[#110730]: https://github.com/home-assistant/core/pull/110730
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114891]: https://github.com/home-assistant/core/pull/114891
+[#114934]: https://github.com/home-assistant/core/pull/114934
+[#115186]: https://github.com/home-assistant/core/pull/115186
+[#115226]: https://github.com/home-assistant/core/pull/115226
+[#115232]: https://github.com/home-assistant/core/pull/115232
+[#115247]: https://github.com/home-assistant/core/pull/115247
+[#115258]: https://github.com/home-assistant/core/pull/115258
+[#115272]: https://github.com/home-assistant/core/pull/115272
+[#115274]: https://github.com/home-assistant/core/pull/115274
+[#115279]: https://github.com/home-assistant/core/pull/115279
+[#115295]: https://github.com/home-assistant/core/pull/115295
+[#115298]: https://github.com/home-assistant/core/pull/115298
+[#115299]: https://github.com/home-assistant/core/pull/115299
+[#115305]: https://github.com/home-assistant/core/pull/115305
+[#115328]: https://github.com/home-assistant/core/pull/115328
+[#115364]: https://github.com/home-assistant/core/pull/115364
+[#115376]: https://github.com/home-assistant/core/pull/115376
+[#115385]: https://github.com/home-assistant/core/pull/115385
+[#115393]: https://github.com/home-assistant/core/pull/115393
+[#115421]: https://github.com/home-assistant/core/pull/115421
+[#115435]: https://github.com/home-assistant/core/pull/115435
+[#115460]: https://github.com/home-assistant/core/pull/115460
+[@NodeJSmith]: https://github.com/NodeJSmith
+[@OnFreund]: https://github.com/OnFreund
+[@Santobert]: https://github.com/Santobert
+[@TheJulianJES]: https://github.com/TheJulianJES
+[@agners]: https://github.com/agners
+[@allenporter]: https://github.com/allenporter
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@frenck]: https://github.com/frenck
+[@janiversen]: https://github.com/janiversen
+[@joostlek]: https://github.com/joostlek
+[@klaasnicolaas]: https://github.com/klaasnicolaas
+[@mdegat01]: https://github.com/mdegat01
+[@thecode]: https://github.com/thecode
+
+## Release 2024.4.4 - April 23
+
+- Bump slixmpp version to 1.8.5 ([@ravermeister] - [#114448])
+- Make Withings recoverable after internet outage ([@joostlek] - [#115124])
+- Fix Hyperion light not updating state ([@avee87] - [#115389])
+- Add scheduled mode to renault charge mode ([@slyoldfox] - [#115427])
+- Bump zeroconf to 0.132.1 ([@bdraco] - [#115501])
+- Bump zeroconf to 0.132.2 ([@bdraco] - [#115505])
+- Update pillow to 10.3.0 ([@cdce8p] - [#115524])
+- Fix race in TimestampDataUpdateCoordinator ([@bdraco] - [#115542])
+- Fix Teslemetry sensor values ([@Bre77] - [#115571])
+- Modbus: Bump pymodbus v3.6.8 ([@janiversen] - [#115574])
+- Fix sensor entity description in Teslemetry ([@Bre77] - [#115614])
+- Bump httpcore to 1.0.5 ([@bdraco] - [#115672])
+- Bump sqlparse to 0.5.0 ([@bdraco] - [#115681])
+- Bump aiohttp to 3.9.5 ([@bdraco] - [#115727])
+- Bump renault-api to 0.2.2 ([@epenet] - [#115738])
+- Fix homeworks import flow ([@emontnemery] - [#115761])
+- Allow [##:##:##] type keypad address in homeworks ([@emontnemery] - [#115762])
+- Add missing media_player features to Samsung TV ([@chemelli74] - [#115788])
+- Bump aiounifi to v75 ([@Kane610] - [#115819])
+- Ensure scripts with timeouts of zero timeout immediately ([@bdraco] - [#115830])
+- Fix KeyError error when fetching sensors (Airthings) ([@LaStrada] - [#115844])
+- Bump plexapi to 4.15.12 ([@jjlawren] - [#115872])
+- Bump ical to 8.0.0 ([@allenporter] - [#115907])
+- Fix geo location attributes of Tankerkoenig sensors ([@mib1185] - [#115914])
+- Use start helper in squeezebox for server discovery ([@rajlaud] - [#115978])
+
+[#114448]: https://github.com/home-assistant/core/pull/114448
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114934]: https://github.com/home-assistant/core/pull/114934
+[#115124]: https://github.com/home-assistant/core/pull/115124
+[#115186]: https://github.com/home-assistant/core/pull/115186
+[#115389]: https://github.com/home-assistant/core/pull/115389
+[#115427]: https://github.com/home-assistant/core/pull/115427
+[#115463]: https://github.com/home-assistant/core/pull/115463
+[#115501]: https://github.com/home-assistant/core/pull/115501
+[#115505]: https://github.com/home-assistant/core/pull/115505
+[#115524]: https://github.com/home-assistant/core/pull/115524
+[#115542]: https://github.com/home-assistant/core/pull/115542
+[#115571]: https://github.com/home-assistant/core/pull/115571
+[#115574]: https://github.com/home-assistant/core/pull/115574
+[#115614]: https://github.com/home-assistant/core/pull/115614
+[#115672]: https://github.com/home-assistant/core/pull/115672
+[#115681]: https://github.com/home-assistant/core/pull/115681
+[#115727]: https://github.com/home-assistant/core/pull/115727
+[#115738]: https://github.com/home-assistant/core/pull/115738
+[#115761]: https://github.com/home-assistant/core/pull/115761
+[#115762]: https://github.com/home-assistant/core/pull/115762
+[#115788]: https://github.com/home-assistant/core/pull/115788
+[#115819]: https://github.com/home-assistant/core/pull/115819
+[#115830]: https://github.com/home-assistant/core/pull/115830
+[#115844]: https://github.com/home-assistant/core/pull/115844
+[#115872]: https://github.com/home-assistant/core/pull/115872
+[#115907]: https://github.com/home-assistant/core/pull/115907
+[#115914]: https://github.com/home-assistant/core/pull/115914
+[#115978]: https://github.com/home-assistant/core/pull/115978
+[@Bre77]: https://github.com/Bre77
+[@Kane610]: https://github.com/Kane610
+[@LaStrada]: https://github.com/LaStrada
+[@allenporter]: https://github.com/allenporter
+[@avee87]: https://github.com/avee87
+[@bdraco]: https://github.com/bdraco
+[@cdce8p]: https://github.com/cdce8p
+[@chemelli74]: https://github.com/chemelli74
+[@emontnemery]: https://github.com/emontnemery
+[@epenet]: https://github.com/epenet
+[@frenck]: https://github.com/frenck
+[@janiversen]: https://github.com/janiversen
+[@jjlawren]: https://github.com/jjlawren
+[@joostlek]: https://github.com/joostlek
+[@mib1185]: https://github.com/mib1185
+[@rajlaud]: https://github.com/rajlaud
+[@ravermeister]: https://github.com/ravermeister
+[@slyoldfox]: https://github.com/slyoldfox
+
[#100055]: https://github.com/home-assistant/core/pull/100055
[#102333]: https://github.com/home-assistant/core/pull/102333
[#102884]: https://github.com/home-assistant/core/pull/102884
diff --git a/source/common-tasks/container.markdown b/source/common-tasks/container.markdown
index 18464daa94c..bba727053b6 100644
--- a/source/common-tasks/container.markdown
+++ b/source/common-tasks/container.markdown
@@ -3,6 +3,9 @@ title: "Common tasks - Container"
description: "Common tasks for Home Assistant Container"
installation: container
---
+
+## Update
+
{% include common-tasks/update.md %}
{% include common-tasks/specific_version.md %}
{% include common-tasks/beta_version.md %}
diff --git a/source/common-tasks/core.markdown b/source/common-tasks/core.markdown
index 04066e649f2..60ea197ac7e 100644
--- a/source/common-tasks/core.markdown
+++ b/source/common-tasks/core.markdown
@@ -3,6 +3,9 @@ title: "Common tasks - Core"
description: "Common tasks for Home Assistant Core"
installation: core
---
+
+## Update
+
{% include common-tasks/update.md %}
{% include common-tasks/specific_version.md %}
{% include common-tasks/beta_version.md %}
diff --git a/source/common-tasks/os.markdown b/source/common-tasks/os.markdown
index f8303d89533..24ee35d502f 100644
--- a/source/common-tasks/os.markdown
+++ b/source/common-tasks/os.markdown
@@ -6,6 +6,71 @@ installation_name: "Operating System"
---
This section will provide guides to some common tasks and information which you will need in order to run, maintain, and edit your Home Assistant OS system. For further details on any particular subject, make sure to refer to the documentation for specific add-ons or topics listed here.
+## Updating Home Assistant
+
+If you have the {% term "Home Assistant Operating System" %} installed, you receive update notifications from different components:
+
+- {% term "Home Assistant Operating System" %}
+- {% term "Home Assistant Supervisor" %}
+- {% term "Home Assistant Core" %}
+- Add-ons, if you have any installed
+
+### Updating the Home Assistant Operating System
+
+Updates of the {% term "Home Assistant Operating System" %} are independent of other updates. They do not trigger repair issues and are usually backward-compatible.
+
+#### Prerequisites
+
+- [Backup](/common-tasks/os/#backups) your installation.
+ - Make sure the backup is downloaded and stored outside of the system.
+ - So that you can restore from that backup in case there is an issue with the system.
+
+#### To update the Home Assistant Operating System
+
+{% tabbed_block %}
+
+- title: Using the UI
+ content: |
+
+ 1. Open the **Settings** panel.
+ 2. On the top you will be presented with an update notification.
+
+ _If you do not see that notification, in the top right, select the three dots menu and select **Check for updates**"._
+
+- title: Using the CLI
+ content: |
+
+ ```bash
+ ha os update
+ ```
+
+ _This updates to the latest version. If you want to update to a specific version instead, use `ha os update --version 12.0`._
+
+{% endtabbed_block %}
+
+#### About boot slots used during the update
+
+The {% term "Home Assistant Operating System" %} uses two boot slots. On first installation, boot slot A is used. After that, on each Operating System update, the other boot slot is updated and reboot is triggered. On that reboot, the system boots from the other boot slot (A ➝ B ➝ A,...). When booting fails, the system automatically uses the previous boot slot, so that it boots from the last working operating system.
+
+#### Changing the boot slot used
+
+You can manually define that the previous boot slot is used. This can be useful in cases where the system boots but something still seems wrong. For example, when the device is no longer correctly detected or you see another issue that might be related to the latest update of the operating system.
+
+1. To check which boot slot is currently in use and what OS versions are installed in the individual slots, in the Home Assistant command line, enter the following command:
+
+ ```bash
+ ha os info
+ ```
+
+2. To change the boot slot, enter the following command:
+ - This will boot into the other (previous) OS version.
+
+ ```bash
+ ha os boot-slot other
+ ```
+
+### Updating Home Assistant Core
+
{% include common-tasks/update.md %}
{% include common-tasks/specific_version.md %}
{% include common-tasks/beta_version.md %}
@@ -18,7 +83,3 @@ This section will provide guides to some common tasks and information which you
{% include common-tasks/lost_password.md %}
{% include common-tasks/third-party-addons.md %}
{% include common-tasks/data_disk.md %}
-{% include common-tasks/flashing_n2_otg.md %}
-{% include common-tasks/flashing_m1s_otg.md %}
-{% include common-tasks/enable_i2c.md %}
-
diff --git a/source/common-tasks/supervised.markdown b/source/common-tasks/supervised.markdown
index 23adfe85603..d3dc28b5d61 100644
--- a/source/common-tasks/supervised.markdown
+++ b/source/common-tasks/supervised.markdown
@@ -4,6 +4,9 @@ description: "Common tasks for Home Assistant Supervised"
installation: supervised
installation_name: Supervised
---
+
+## Update
+
{% include common-tasks/update.md %}
{% include common-tasks/specific_version.md %}
{% include common-tasks/beta_version.md %}
diff --git a/source/dashboards/actions.markdown b/source/dashboards/actions.markdown
index 1010ea4f4a8..a22d473b038 100644
--- a/source/dashboards/actions.markdown
+++ b/source/dashboards/actions.markdown
@@ -1,6 +1,23 @@
---
title: "Actions"
description: "Define what an object does when interacted with."
+related:
+ - docs: /dashboards/button/
+ title: Button card
+ - docs: /dashboards/entities/
+ title: Entities card
+ - docs: /dashboards/glance/
+ title: Glance card
+ - docs: /dashboards/light/
+ title: Light card
+ - docs: /dashboards/picture/
+ title: Picture card
+ - docs: /dashboards/picture-elements/
+ title: Picture element card
+ - docs: /dashboards/picture-entity/
+ title: Picture entity card
+ - docs: /dashboards/picture-glance/
+ title: Picture glance card
---
Some cards have support for tap actions. These actions define what will happen when you tap or hold on an object within a card.
@@ -264,14 +281,3 @@ hold_action:
## Limitations
It is not possible to use templates for actions. But calling a [script](/docs/scripts/) is a good alternative.
-
-## Related topics
-
-- [Button card](/dashboards/button/)
-- [Entities card](/dashboards/entities/)
-- [Glance card](/dashboards/glance/)
-- [Light card](/dashboards/light/)
-- [Picture card](/dashboards/picture/)
-- [Picture element card](/dashboards/picture-elements/)
-- [Picture entity card](/dashboards/picture-entity/)
-- [Picture glance card](/dashboards/picture-glance/)
\ No newline at end of file
diff --git a/source/dashboards/cards.markdown b/source/dashboards/cards.markdown
index ac5e78b7dc5..8d707a46dbf 100644
--- a/source/dashboards/cards.markdown
+++ b/source/dashboards/cards.markdown
@@ -1,6 +1,19 @@
---
title: "Cards"
description: "Introduction to the role of cards on the dashboard and how to add a card."
+related:
+ - docs: /dashboards/actions/
+ title: Card tap actions
+ - docs: /dashboards/features/
+ title: Card features
+ - docs: /dashboards/header-footer/
+ title: Card header and footer widgets
+ - docs: /dashboards/views/
+ title: Views
+ - docs: /dashboards/
+ title: Introduction to dashboards
+ - docs: /dashboards/#get-started-with-your-own-dashboard/
+ title: Take control of the default dashboard
---
Each dashboard is made up of cards.
@@ -75,16 +88,3 @@ Another way to add entities to a dashboard is to use the **Device** page.
{% enddetails %}
-
-## Related topics
-
-- [Views](/dashboards/views/)
-- [Introduction to dashboards](/dashboards/)
-- [Take control of the default dashboard](/dashboards/#get-started-with-your-own-dashboard)
-
-### Cards
-
-- For a list of available card types and more detailed documentation, refer to the **Card types** section in the side navigation.
-- [Card tap actions](/dashboards/actions/)
-- [Card features](/dashboards/actions/)
-- [Card header and footer widgets](/dashboards/header-footer/)
diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown
index bbd9f892860..bb40bb191ab 100644
--- a/source/dashboards/dashboards.markdown
+++ b/source/dashboards/dashboards.markdown
@@ -1,6 +1,17 @@
---
title: "Multiple dashboards"
description: "Multiple powerful and configurable dashboards in Home Assistant."
+related:
+ - docs: /integrations/logbook/
+ title: Logbook integration
+ - docs: /integrations/history/
+ title: History integration
+ - docs: /integrations/todo/
+ title: To-do list integration
+ - docs: /dashboards/views/
+ title: Views
+ - docs: /dashboards/iframe/
+ title: Webpage card
---
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.
@@ -45,6 +56,24 @@ The predefined **History** dashboard is powered by the [History integration](/in
The predefined **To-do lists** dashboard is powered by the [To-do integration](/integrations/todo/). To learn how to use to-do and shopping lists, refer to the documentation of the to-do list integration.
+## Webpage dashboard
+
+Another available (but not default) dashboard is the webpage dashboard. The webpage dashboard allows you to add and embed a webpage to your dashboard.
+This could be a web page from the internet or a local web page from a local
+machine or device like your router or NAS. The webpage dashboard uses the [webpage card](/dashboards/iframe/).
+
+
+
+This dashboard replaces the old iFrame panel (`iframe_panel`). If you have
+existing panels configured in your YAML configuration, Home Assistant will
+automatically migrate them to the new webpage dashboard on upgrade.
+
+
+
+Note that not every webpage can be embedded due to security restrictions that
+some sites have in place. These restrictions are enforced by your browser and prevent
+embedding them into a Home Assistant dashboard.
+
## Creating a new dashboard
The default **Overview** dashboard updates itself when you add new devices, as long as you do not edit the default dashboard. If you want a customized dashboard, it is recommended not to change the **Overview** dashboard, but to create a new dashboard instead.
@@ -70,6 +99,15 @@ This will leave the default dashboard intact.
- To continue, in the dialog, select the three dots menu, then select **Take control**.
7. You can now [add a card](/dashboards/cards/#adding-cards-to-your-dashboard) or [add a view](/dashboards/views/#adding-a-view-to-a-dashboard).
+## Deleting a dashboard
+
+If you do not use one of the predefined dashboards, or created a dashboard you no longer need, you can delete that dashboard. It will then no longer show in the sidebar.
+
+1. Go to {% my lovelace_dashboards title="**Settings** > **Dashboards**" %}.
+2. From the list of dashboards, select the dashboard you want to delete.
+3. In the dialog, select **Delete**.
+ 
+
## Using YAML for the Overview dashboard
To change the **Overview** dashboard, create a new file `ui-lovelace.yaml` in your configuration directory and add the following section to your `configuration.yaml` and restart Home Assistant:
@@ -255,10 +293,3 @@ views:
content: >
Welcome to your **dashboard**.
```
-
-## Related topics
-
-- [Logbook integration](/integrations/logbook/)
-- [History integration](/integrations/history/)
-- [To-do list integration](/integrations/todo/)
-- [Views](/dashboards/views/)
\ No newline at end of file
diff --git a/source/dashboards/features.markdown b/source/dashboards/features.markdown
index cc62befc47a..b61bfcfbc83 100644
--- a/source/dashboards/features.markdown
+++ b/source/dashboards/features.markdown
@@ -1,6 +1,13 @@
---
title: "Features for dashboard cards"
description: "Decorate your dashboard cards with quick controls."
+related:
+ - docs: /dashboards/humidifier/
+ title: Humidifier card
+ - docs: /dashboards/thermostat/
+ title: Thermostat card
+ - docs: /dashboards/tile/
+ title: Tile card
---
Some dashboard cards have support for features. These widgets add quick controls to the card. Supported features depend on the card and entity capabilities. Multiple features can be added to a single card.
@@ -581,8 +588,3 @@ operation_modes:
type: list
{% endconfiguration %}
-## Related topics
-
-- [Humidifier card](/dashboards/humidifier/)
-- [Thermostat card](/dashboards/thermostat/)
-- [Tile card](/dashboards/tile/)
diff --git a/source/dashboards/header-footer.markdown b/source/dashboards/header-footer.markdown
index 10e7f607d7e..2b80e0720eb 100644
--- a/source/dashboards/header-footer.markdown
+++ b/source/dashboards/header-footer.markdown
@@ -1,6 +1,15 @@
---
title: "Headers & Footers for dashboard cards"
description: "Decorate your dashboard cards with header and footer widgets."
+related:
+ - docs: /integrations/entity/
+ title: Entity
+ - docs: /integrations/entities/
+ title: Entities
+ - docs: /integrations/statistics/
+ title: Statistics
+ - docs: /integrations/actions/
+ title: Card actions
---
Some dashboard cards have support for header and footer widgets. These widgets fill up the whole available space in a card.
@@ -146,10 +155,3 @@ hours_to_show:
type: integer
default: 24
{% endconfiguration %}
-
-## Related topics
-
-- [Entity](/dashboards/entity/)
-- [Entities](/dashboards/entities/)
-- [statistics](/dashboards/statistics/)
-- [Card actions](/dashboards/actions/)
diff --git a/source/dashboards/index.markdown b/source/dashboards/index.markdown
index ba52d11d050..b0248d37ab8 100644
--- a/source/dashboards/index.markdown
+++ b/source/dashboards/index.markdown
@@ -1,6 +1,19 @@
---
title: "Dashboards"
description: "Powerful and configurable dashboards for Home Assistant."
+related:
+ - docs: /integrations/entity/
+ title: Dashboard themes
+ - docs: /dashboards/dashboards/#creating-a-new-dashboard
+ title: Creating a new dashboard
+ - docs: /dashboards/cards/
+ title: About cards
+ - url: https://demo.home-assistant.io
+ title: Interactive dashboard demo
+ - url: https://home-assistant-cards.bessarabov.com/
+ title: Home Assistant cards
+ - url: https://github.com/custom-cards
+ title: Community custom cards
---
Home Assistant dashboards allow you to display information about your smart home. Dashboards are customizable and provide a powerful way to manage your home from your mobile or desktop.
@@ -29,16 +42,3 @@ To create your own dashboard, follow the steps on [creating a new dashboard](/da
- Suggestions are welcome in the [frontend repository](https://github.com/home-assistant/frontend/)
- For help with dashboards, join the `#frontend` channel on [our chat](/join-chat/) or [our forums](https://community.home-assistant.io/c/projects/frontend)
-
-## Related topics
-
-- [Dashboard themes](/integrations/frontend/#defining-themes)
-- [Interactive dashboard demo](https://demo.home-assistant.io)
-- [Creating a new dashboard](/dashboards/dashboards/#creating-a-new-dashboard)
-
-### Cards
-
-- [About cards](/dashboards/cards/)
-- [Community custom cards](https://github.com/custom-cards)
-- [Home Assistant cards](https://home-assistant-cards.bessarabov.com/)
-
diff --git a/source/dashboards/views.markdown b/source/dashboards/views.markdown
index 22d10a1badd..7ca8f3ef4e0 100644
--- a/source/dashboards/views.markdown
+++ b/source/dashboards/views.markdown
@@ -1,6 +1,19 @@
---
title: "Views"
description: "A view is a tab inside a dashboard."
+related:
+ - docs: /dashboards/masonry/
+ title: Masonry view
+ - docs: /dashboards/panel/
+ title: Panel view
+ - docs: /dashboards/sidebar/
+ title: Sidebar view
+ - docs: /dashboards/sections/
+ title: Sections view
+ - docs: /dashboards/
+ title: About dashboards
+ - docs: /dashboards/cards/#adding-cards-to-your-dashboard
+ title: Adding cards to a view
---
A view is a tab inside a dashboard. For example, the screenshot below shows a separate view for lights on the Overview dashboard.
@@ -267,12 +280,3 @@ Subview configuration:
entities:
- sensor.today_avg_price
```
-
-## Related topics
-
-- [Masonry view](/dashboards/masonry/)
-- [Panel view](/dashboards/panel/)
-- [Sidebar view](/dashboards/sidebar/)
-- [Sections view](/dashboards/sections/)
-- [About dashboards](/dashboards/)
-- [Adding cards to a view](/dashboards/cards/#adding-cards-to-your-dashboard)
\ No newline at end of file
diff --git a/source/images/dashboards/delete_dashboard.png b/source/images/dashboards/delete_dashboard.png
new file mode 100644
index 00000000000..9b05ffc4e2e
Binary files /dev/null and b/source/images/dashboards/delete_dashboard.png differ
diff --git a/source/images/docs/authentication/profile.png b/source/images/docs/authentication/profile.png
index a6b88e17cbc..deac23c20c7 100644
Binary files a/source/images/docs/authentication/profile.png and b/source/images/docs/authentication/profile.png differ
diff --git a/source/images/docs/configuration/coordinates-defined-in-yaml.png b/source/images/docs/configuration/coordinates-defined-in-yaml.png
new file mode 100644
index 00000000000..f0dbffe8a57
Binary files /dev/null and b/source/images/docs/configuration/coordinates-defined-in-yaml.png differ
diff --git a/source/images/docs/configuration/general-settings-stored-in-config-yaml.png b/source/images/docs/configuration/general-settings-stored-in-config-yaml.png
new file mode 100644
index 00000000000..f3c5eee1c51
Binary files /dev/null and b/source/images/docs/configuration/general-settings-stored-in-config-yaml.png differ
diff --git a/source/images/docs/configuration/general-settings.png b/source/images/docs/configuration/general-settings.png
new file mode 100644
index 00000000000..ed0a5fd75f4
Binary files /dev/null and b/source/images/docs/configuration/general-settings.png differ
diff --git a/source/images/docs/configuration/reloading_config.png b/source/images/docs/configuration/reloading_config.png
new file mode 100644
index 00000000000..11aba2afd90
Binary files /dev/null and b/source/images/docs/configuration/reloading_config.png differ
diff --git a/source/images/hassio/screenshots/ssh-upgrade.png b/source/images/hassio/screenshots/ssh-upgrade.png
deleted file mode 100644
index 64d80f9943b..00000000000
Binary files a/source/images/hassio/screenshots/ssh-upgrade.png and /dev/null differ
diff --git a/source/images/integrations/matter/matter_android_connect_new.webp b/source/images/integrations/matter/matter_android_connect_new.webp
new file mode 100644
index 00000000000..154d6d0e80f
Binary files /dev/null and b/source/images/integrations/matter/matter_android_connect_new.webp differ
diff --git a/source/images/integrations/matter/matter_share_from_apple.webp b/source/images/integrations/matter/matter_share_from_apple.webp
new file mode 100644
index 00000000000..3ddf4e29458
Binary files /dev/null and b/source/images/integrations/matter/matter_share_from_apple.webp differ
diff --git a/source/images/organizing/enable_disable.png b/source/images/organizing/enable_disable.png
new file mode 100644
index 00000000000..ed4ed655f54
Binary files /dev/null and b/source/images/organizing/enable_disable.png differ
diff --git a/source/images/organizing/filter-panel.png b/source/images/organizing/filter-panel.png
new file mode 100644
index 00000000000..67e69d67d94
Binary files /dev/null and b/source/images/organizing/filter-panel.png differ
diff --git a/source/images/organizing/multiselect_01.png b/source/images/organizing/multiselect_01.png
new file mode 100644
index 00000000000..415c83778f2
Binary files /dev/null and b/source/images/organizing/multiselect_01.png differ
diff --git a/source/images/organizing/table_group_01.png b/source/images/organizing/table_group_01.png
new file mode 100644
index 00000000000..616be9ccd41
Binary files /dev/null and b/source/images/organizing/table_group_01.png differ
diff --git a/source/installation/raspberrypi.markdown b/source/installation/raspberrypi.markdown
index acfdfa76f7d..1213f45d225 100644
--- a/source/installation/raspberrypi.markdown
+++ b/source/installation/raspberrypi.markdown
@@ -87,6 +87,7 @@ With the Home Assistant Operating System installed and accessible, you can now c
{% include getting-started/next_step.html step="Onboarding" link="/getting-started/onboarding/" %}
+
{% include installation/container.md %}
{% include installation/core.md %}
@@ -135,3 +136,4 @@ _Select and copy the URL or use the "copy" button that appear when you hover it.
We get commissions for purchases made through links in this post.
@@ -62,15 +81,3 @@ Use the [built-in sentences](/voice_control/builtin_sentences) to control entiti
Did Assist not understand your sentence? [Contribute them](https://developers.home-assistant.io/docs/voice/intent-recognition/).
_Assist was introduced in Home Assistant 2023.2._
-
-## Related topics
-
-- [Home Assistant Cloud](https://www.nabucasa.com/config/)
-- [Assist on Android](/voice_control/android)
-- [Assist on Wear OS](/voice_control/android/#assist-on-wear-os)
-- [Siri and Assist shortcuts](/voice_control/apple)
-- [Assist dashboard button](/voice_control/start_assist_from_dashboard/)
-- [Build a 13$ voice remote using an ESPHome device](/voice_control/thirteen-usd-voice-remote/)
-- [Enable a wake word](/voice_control/install_wake_word_add_on)
-- [Create your own wake words](/voice_control/create_wake_word/)
-- [Built-in sentences](/voice_control/builtin_sentences)
diff --git a/source/voice_control/s3-box-customize.markdown b/source/voice_control/s3-box-customize.markdown
index a800d3c266d..d873af398cb 100644
--- a/source/voice_control/s3-box-customize.markdown
+++ b/source/voice_control/s3-box-customize.markdown
@@ -2,6 +2,23 @@
title: "Customize the S3-BOX-3"
product_name: ESP32-S3-BOX-3
device_name_entry: ESP32-S3-BOX-3
+related:
+ - docs: /voice_control/voice_remote_cloud_assistant/
+ title: Home Assistant Cloud
+ - docs: /voice_control/voice_remote_local_assistant
+ title: Assist Pipeline
+ - docs: /voice_control/s3_box_voice_assistant/
+ title: ESP32-S3-BOX-3 voice assistant
+ - docs: /voice_control/troubleshooting/
+ title: General troubleshooting section for Assist
+ - docs: /voice_control/troubleshooting_the_s3_box/
+ title: Troubleshooting the ESP32-S3-BOX-3
+ - docs: /common-tasks/os/#configuring-access-to-files
+ title: Access to your configuration files
+ - url: https://github.com/jlpouffier/home-assistant-s3-box-community-illustrations/tree/main
+ title: Community image repository
+ - url: https://github.com/kahrendt/microWakeWord
+ title: microWakeWord
---
## Customize the S3-BOX-3 with your own illustrations
@@ -222,16 +239,5 @@ You can change the on-device wake word (microWakeWord) that is used on your S3-B
7. Now, speak a command to test the new setting. For example, *Hey Jarvis, turn on the light*.
-## Related topics
-
-- [Community image repository](https://github.com/jlpouffier/home-assistant-s3-box-community-illustrations/tree/main)
-- [Home Assistant Cloud](/voice_control/voice_remote_cloud_assistant/)
-- [Assist Pipeline](/voice_control/voice_remote_local_assistant)
-- [ESP32-S3-BOX-3 voice assistant](/voice_control/s3_box_voice_assistant/)
-- [General troubleshooting section for Assist](/voice_control/troubleshooting/)
-- [Troubleshooting the ESP32-S3-BOX-3](/voice_control/troubleshooting_the_s3_box/)
-- [Access to your configuration files](/common-tasks/os/#configuring-access-to-files)
-- [microWakeWord](https://github.com/kahrendt/microWakeWord)
-
[microWakeWord]: https://github.com/kahrendt/microWakeWord
[Kevin Ahrendt]: https://www.kevinahrendt.com/
\ No newline at end of file
diff --git a/source/voice_control/s3_box_voice_assistant.markdown b/source/voice_control/s3_box_voice_assistant.markdown
index 07865fb5930..9e76a272b29 100644
--- a/source/voice_control/s3_box_voice_assistant.markdown
+++ b/source/voice_control/s3_box_voice_assistant.markdown
@@ -3,6 +3,17 @@ title: "ESP32-S3-BOX voice assistant"
product_name: ESP32-S3-BOX
device_name_entry: ESP32-S3-BOX
config_link: /voice_control/s3_box_voice_assistant/#to-delete-the-configuration-from-esphome
+related:
+ - docs: /voice_control/troubleshooting/
+ title: General troubleshooting section for Assist
+ - docs: /voice_control/troubleshooting_the_s3_box/
+ title: Troubleshooting the ESP32-S3-BOX-3
+ - docs: /common-tasks/os/#configuring-access-to-files
+ title: Access to your configuration files
+ - docs: /voice_control/s3-box-customize/#customizing-on-device-wake-words-microwakeword
+ title: Customizing the S3-BOX with on-device wake words
+ - url: https://esphome.io/projects/index.html
+ title: ESPHome projects page
---
This tutorial will guide you to turn an ESP32-S3-BOX, ESP32-S3-BOX-3, or an ESP32-S3-BOX-Light into a Home Assistant voice assistant. Note, the term ESP32-S3-BOX is used to refer to any of the 3 product variants.
@@ -84,11 +95,3 @@ Before you can use this device with Home Assistant, you need to install a bit of
- Disable **LCD Backlight**.
-
-## Related topics
-
-- [General troubleshooting section for Assist](/voice_control/troubleshooting/)
-- [Troubleshooting the ESP32-S3-BOX-3](/voice_control/troubleshooting_the_s3_box/)
-- [ESPHome projects page](https://esphome.io/projects/index.html)
-- [Access to your configuration files](/common-tasks/os/#configuring-access-to-files)
-- [Customizing the S3-BOX with on-device wake words](/voice_control/s3-box-customize/#customizing-on-device-wake-words-microwakeword)
diff --git a/source/voice_control/start_assist_from_dashboard.markdown b/source/voice_control/start_assist_from_dashboard.markdown
index ec79fbe26f2..92db86f8442 100644
--- a/source/voice_control/start_assist_from_dashboard.markdown
+++ b/source/voice_control/start_assist_from_dashboard.markdown
@@ -1,5 +1,14 @@
---
title: "Starting Assist from your dashboard"
+related:
+ - docs: /voice_control/android/
+ title: Assist for Android
+ - docs: /voice_control/voice_remote_local_assistant/
+ title: Creating a local assistant
+ - docs: /voice_control/voice_remote_cloud_assistant/
+ title: Creating a Cloud assistant
+ - docs: /voice_control/voice_remote_expose_devices/
+ title: Exposing devices to Assist
---
If you are using Home Assistant in kiosk mode, for example if you have a tablet mounted on the wall, the Assist icon in the top right corner is not accessible. In this case, use a dashboard button to start Assist.
@@ -21,10 +30,3 @@ If you are using Home Assistant in kiosk mode, for example if you have a tablet
6. If you are using Assist with your voice, enable **Start listening**.
- If you don't want to use voice but just want to type, you do not need to enable listening.
7. **Save** your new button card.
-
-## Related topics
-
-- [Assist for Android](/voice_control/android/)
-- [Creating a local assistant](/voice_control/voice_remote_local_assistant/)
-- [Creating a Cloud assistant](/voice_control/voice_remote_cloud_assistant/)
-- [Exposing devices to Assist](/voice_control/voice_remote_expose_devices/)
diff --git a/source/voice_control/thirteen-usd-voice-remote.markdown b/source/voice_control/thirteen-usd-voice-remote.markdown
index 2d090c30a24..51dd0207719 100644
--- a/source/voice_control/thirteen-usd-voice-remote.markdown
+++ b/source/voice_control/thirteen-usd-voice-remote.markdown
@@ -3,6 +3,21 @@ title: "$13 voice assistant for Home Assistant"
product_name: ATOM Echo
device_name_entry: M5Stack Atom Echo a61920
config_link: /voice_control/thirteen-usd-voice-remote/#to-delete-the-atom-echo-configuration-from-esphome
+related:
+ - docs: /voice_control/install_wake_word_add_on/
+ title: Enable a wake word
+ - docs: /voice_control/create_wake_word/
+ title: Create your own wake words
+ - docs: /voice_control/voice_remote_cloud_assistant/
+ title: Creating a Cloud assistant
+ - docs: /voice_control/troubleshooting/
+ title: General troubleshooting section for Assist
+ - docs: /voice_control/voice_remote_local_assistant
+ title: Manually configured Assist pipeline
+ - docs: /voice_control/custom_sentences/
+ title: Using a sentence trigger
+ - docs: /common-tasks/os/#configuring-access-to-files
+ title: Access to your configuration files
---
This tutorial will guide you to turn an ATOM Echo into the
@@ -76,13 +91,3 @@ Before you can use this device with Home Assistant, you need to install a bit of
Are things not working as expected?
- Checkout the [general troubleshooting section for Assist](/voice_control/troubleshooting/).
-
-## Related topics
-
-- [Enable a wake word](/voice_control/install_wake_word_add_on/)
-- [Create your own wake words](/voice_control/create_wake_word/)
-- [General troubleshooting section for Assist](/voice_control/troubleshooting/)
-- [Access to your configuration files](/common-tasks/os/#configuring-access-to-files)
-- [Using a sentence trigger](/voice_control/custom_sentences/)
-- [Home Assistant Cloud](/voice_control/voice_remote_cloud_assistant/)
-- [Manually configured Assist pipeline](/voice_control/voice_remote_local_assistant)
diff --git a/source/voice_control/troubleshooting_the_s3_box.markdown b/source/voice_control/troubleshooting_the_s3_box.markdown
index 2c3b59e061f..470be2efe39 100644
--- a/source/voice_control/troubleshooting_the_s3_box.markdown
+++ b/source/voice_control/troubleshooting_the_s3_box.markdown
@@ -1,5 +1,10 @@
---
title: "Troubleshooting the ESP32-S3-BOX-3"
+related:
+ - docs: /voice_control/s3_box_voice_assistant/
+ title: Creating a ESP32-S3-BOX-3 voice assistant
+ - url: https://esphome.io/projects/index.html
+ title: ESPHome projects website
---
This section provides troubleshooting steps for the ESP32-S3-BOX-3 by Espressif.
@@ -77,8 +82,3 @@ This message indicates that the device could connect to the Wi-Fi, but is unable
- Go to your router, find the IP address or hostname of your device, and enter it.
-
-## Related topics
-
-- [Creating a ESP32-S3-BOX-3 voice assistant](/voice_control/s3_box_voice_assistant/)
-- [ESPHome projects website](https://esphome.io/projects/index.html)
\ No newline at end of file
diff --git a/source/voice_control/voice_remote_cloud_assistant.markdown b/source/voice_control/voice_remote_cloud_assistant.markdown
index 8b3691e29cf..0a5f4b76bf9 100644
--- a/source/voice_control/voice_remote_cloud_assistant.markdown
+++ b/source/voice_control/voice_remote_cloud_assistant.markdown
@@ -1,5 +1,14 @@
---
title: "Creating a cloud Assist pipeline"
+related:
+ - docs: /voice_control/install_wake_word_add_on/
+ title: Enabling a wake word
+ - docs: /voice_control/create_wake_word/
+ title: Create your own wake word
+ - docs: /voice_control/voice_remote_cloud_assistant/
+ title: Creating a Cloud assistant
+ - docs: /voice_control/voice_remote_expose_devices/
+ title: Exposing devices to Assist
---
In Home Assistant, the Assist pipelines are made up of various components that together form a voice assistant.
@@ -42,10 +51,3 @@ To have the fastest processing voice assistant experience, follow these steps:
6. That's it. You can now speak to your device, and the device can answer in the language you defined.
7. If you haven't done so yet, [expose your devices to Assist](/voice_control/voice_remote_expose_devices/#exposing-your-devices).
- Otherwise you won't be able to control them by voice.
-
-## Related topics
-
-- [Enable Home Assistant Cloud](https://www.nabucasa.com/config/)
-- [Enabling a wake word](/voice_control/install_wake_word_add_on/)
-- [Create your own wake word](/voice_control/create_wake_word/)
-- [Expose your devices to Assist](/voice_control/voice_remote_expose_devices/#exposing-your-devices)
diff --git a/source/voice_control/voice_remote_expose_devices.markdown b/source/voice_control/voice_remote_expose_devices.markdown
index 41c7db07351..30b9b3b38ff 100644
--- a/source/voice_control/voice_remote_expose_devices.markdown
+++ b/source/voice_control/voice_remote_expose_devices.markdown
@@ -1,5 +1,10 @@
---
title: "Exposing devices"
+related:
+ - docs: /voice_control/voice_remote_cloud_assistant/
+ title: Creating a Cloud assistant
+ - docs: /voice_control/voice_remote_local_assistant/
+ title: Creating a local assistant
---
To be able to control your devices over a voice command, you must expose your entities to Assist.
@@ -13,9 +18,3 @@ This is to avoid that sensitive devices, such as locks and garage doors, can ina
3. Select **Expose entities**.
1. Select all entities you want to be able to control by voice.
-
-
-## Related topics
-
-- [Local assistant pipeline](/voice_control/voice_remote_local_assistant/)
-- [Cloud assistant pipeline](/voice_control/voice_remote_cloud_assistant/)
\ No newline at end of file
diff --git a/source/voice_control/voice_remote_local_assistant.markdown b/source/voice_control/voice_remote_local_assistant.markdown
index caadd0f74a4..8112568c8b2 100644
--- a/source/voice_control/voice_remote_local_assistant.markdown
+++ b/source/voice_control/voice_remote_local_assistant.markdown
@@ -1,5 +1,14 @@
---
title: "Installing a local Assist pipeline"
+related:
+ - docs: /voice_control/voice_remote_expose_devices/#exposing-your-devices
+ title: Expose your devices to Assist
+ - docs: /voice_control/create_wake_word/
+ title: Create your own wake words
+ - url: https://github.com/openai/whisper
+ title: Whisper for speech-to-text
+ - url: https://github.com/rhasspy/piper
+ title: Piper for text-to-speech
---
In Home Assistant, the Assist pipelines are made up of various components that together form a voice assistant.
@@ -69,9 +78,3 @@ View some of the options in the video below. Explained by Mike Hansen, creator o
The options are also documented in the add-on itself. Go to the {% my supervisor_addon addon="core_whisper" title="**Whisper**" %} or the {% my supervisor_addon addon="core_piper" title="**Piper**" %} add-on and open the **Documentation** page.
-## Related topics
-
-- [Create your own wake word](/voice_control/create_wake_word/)
-- [Expose your devices to Assist](/voice_control/voice_remote_expose_devices/#exposing-your-devices)
-- [Whisper for speech-to-text](https://github.com/openai/whisper)
-- [Piper for text-to-speech](https://github.com/rhasspy/piper)
diff --git a/source/voice_control/worlds-most-private-voice-assistant.markdown b/source/voice_control/worlds-most-private-voice-assistant.markdown
index ac77ccc0b66..a98b79de126 100644
--- a/source/voice_control/worlds-most-private-voice-assistant.markdown
+++ b/source/voice_control/worlds-most-private-voice-assistant.markdown
@@ -1,5 +1,14 @@
---
title: "World's most private voice assistant"
+related:
+ - docs: /voice_control/voice_remote_cloud_assistant/
+ title: Creating a Cloud assistant
+ - docs: /voice_control/voice_remote_local_assistant/
+ title: Creating a local assistant
+ - url: https://amzn.to/40k7mRa
+ title: Grandstream HT801
+ - url: https://www.nabucasa.com
+ title: Home Assistant Cloud
---
This tutorial will guide you to turn your old landline phone into the
@@ -125,10 +134,3 @@ The phone shown in the video by TheFes is a *Heemaf type 1955*, which was used b
The phone used during creation of this tutorial is a 1953 [*Tischstation Mod.29 HF-TR* by Autophon AG](https://www.radiomuseum.org/r/autophon_tischstation_mod29_hf_tr.html).
-
-## Related topics
-
-- [Grandstream HT801](https://amzn.to/40k7mRa)
-- [Home Assistant Cloud](https://www.nabucasa.com)
-- [Cloud assistant pipeline](/voice_control/voice_remote_cloud_assistant/)
-- [Local assistant pipeline](/voice_control/voice_remote_local_assistant/)
\ No newline at end of file