Merge branch 'current' into rc

Gemfile.lock

@@ -84,7 +84,7 @@ GEM
     prism (0.24.0)
     public_suffix (5.0.4)
     racc (1.7.3)
-    rack (3.0.9)
+    rack (3.0.9.1)
     rack-protection (4.0.0)
       base64 (>= 0.1.0)
       rack (>= 3.0.0, < 4)

_config.yml

@@ -110,8 +110,8 @@ social:
 # Home Assistant release details
 current_major_version: 2024
 current_minor_version: 2
-current_patch_version: 2
-date_released: 2024-02-16
+current_patch_version: 5
+date_released: 2024-02-27
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
@@ -216,6 +216,8 @@ installation:
       board: Raspberry Pi
       installation_media: "SD card"
       variants:
+        - name: "Raspberry Pi 5"
+          key: "rpi5-64"
         - name: "Raspberry Pi 4"
           key: "rpi4-64"
         - name: "Raspberry Pi 3"

source/_dashboards/masonry.markdown

@@ -6,7 +6,13 @@ description: "The default panel layout uses a masonry algorithme."
 ---
 
 The masonry view is the default view type.
-It sorts cards in columns based on their `card size`. If you want to group some cards you have to use `stack` or `grid` cards.
+
+<p class='img'>
+<img src='/images/getting-started/lovelace.png' alt='Screenshot of the masonry view'>
+Screenshot of the masonry view.
+</p>
+
+It sorts cards in columns based on their `card size`. If you want to group some cards you have to use [horizontal stack](/dashboards/horizontal-stack/), [vertical stack](/dashboards/vertical-stack/), or [grid](/dashboards/grid/) cards.
 
 {% configuration %}
 type:
@@ -14,3 +20,8 @@ type:
   description: "`masonry`"
   type: string
 {% endconfiguration %}
+
+## Related topics
+
+- [Panel view](/dashboards/panel/)
+- [Sidebar view](/dashboards/sidebar/)

source/_dashboards/panel.markdown

@@ -5,11 +5,16 @@ sidebar_label: Panel
 description: "The panel view shows a single card in the full width of the screen."
 ---
 
-The view must have exactly one card. This card is rendered full-width.
+The panel view must have exactly one card. This card is rendered full-width.
+
+<p class='img'>
+<img src='/images/dashboards/panel_view.png' alt='Screenshot of the panel view'>
+Screenshot of the panel view.
+</p>
 
 This view doesn't have support for badges.
 
-This view is good when using cards like `map`, `stack` or `picture-elements`.
+This view is good when using cards like [map](/dashboards/map/), [horizontal stack](/dashboards/horizontal-stack/), [vertical stack](/dashboards/vertical-stack/), [picture elements](/dashboards/picture-elements/), or [picture glance](/dashboards/picture-glance/).
 
 {% configuration %}
 type:
@@ -17,3 +22,8 @@ type:
   description: "`panel`"
   type: string
 {% endconfiguration %}
+
+## Related topics
+
+- [Masonry view](/dashboards/masonry/)
+- [Sidebar view](/dashboards/sidebar/)

source/_dashboards/sidebar.markdown

@@ -7,14 +7,21 @@ description: "The sidebar view has 2 columns, a wide one and a smaller one on th
 
 The sidebar view has 2 columns, a wide one and a smaller one on the right.
 
+<p class='img'>
+<img src='/images/dashboards/sidebar_view.png' alt='Screenshot of the sidebar view'>
+Screenshot of the sidebar view used for the energy dashboard.
+</p>
+
 This view doesn't have support for badges.
 
-To change a view to edit mode, or to change the location of a card, enable edit mode:
-Click the menu (three dots at the top right of the screen) and then **Edit Dashboard**.
+You can set if a card should be placed in the main (left) column of the sidebar column (right), by selecting the arrow right or left arrow in the bar underneath the card.
 
-You can set if a card should be placed in the main (left) column of the sidebar column (right), by pressing the arrow right or left arrow in the bar underneath the card.
+<p class='img'>
+<img src='/images/dashboards/sidebar_view_move_card.png' alt='Screenshot showing how to move a card between sidebar and main view'>
+Screenshot showing how to move a card between sidebar and main view.
+</p>
 
-On mobile all cards are rendered in 1 column and kept in the order of the cards in the config.
+On mobile, all cards are rendered in 1 column and kept in the order of the cards in the config.
 
 ## View config:
 
@@ -47,3 +54,8 @@ cards:
     view_layout:
       position: sidebar
 ```
+
+## Related topics
+
+- [Panel view](/dashboards/panel/)
+- [Masonry view](/dashboards/masonry/)

source/_docs/automation/trigger.markdown

@@ -946,6 +946,10 @@ The sentences matched by this trigger will be:
 
 Punctuation and casing are ignored, so "It's PARTY TIME!!!" will also match.
 
+### Related topic
+
+- [Adding a custom sentence to trigger an automation](/voice_control/custom_sentences/#adding-a-custom-sentence-to-trigger-an-automation)
+
 ### Sentence wildcards
 
 Adding one or more `{lists}` to your trigger sentences will capture any text at that point in the sentence. A `slots` object will be [available in the trigger data](/docs/automation/templating#sentence).

source/_docs/troubleshooting_general.markdown

@@ -0,0 +1,43 @@
+---
+title: "General troubleshooting"
+description: "General troubleshooting information"
+---
+
+This page provides some information about more generic troubleshooting topics.
+
+## Home Assistant went into recovery mode
+
+### Symptom: Home Assistant is in recovery mode
+
+On top of the page you see a red banner. On the **Overview** page, you see a **Recovery mode** notification.
+
+![image](/images/docs/troubleshooting/recovery_mode_active.png)
+
+### Description
+
+When Home Assistant is in recovery mode, there was an issue with the configuration.
+
+Recovery mode loads a minimum set of integrations to allow troubleshooting the configuration. Recovery mode will use the parts of the configuration that was used the last time Home Assistant started successfully. You can still see the user interface, the settings, and add-ons.
+
+### Resolution
+
+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 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.
+- If you are locked out because you forgot your password, you cannot edit the configuration file from the user interface. Follow the steps to [reset your password](/docs/locked_out/).
+
+## Restarting Home Assistant in safe mode
+
+If your Home Assistant is acting up and you cannot identify a root cause, you can use **Safe mode** to narrow down the number of possible causes.
+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/)

source/_docs/z-wave/controllers.markdown

@@ -85,9 +85,20 @@ It's totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blu
 
 ### Razberry Board
 
-You need to disable the on-board Bluetooth since the board requires the use of the hardware UART (and there's only one on the Pi3). You do this by adding the following to the end of `/boot/config.txt`:
+On Raspberry Pi 3 and 4, you need to disable the on-board Bluetooth since the board requires the use of the hardware UART (whose pins are shared with the Bluetooth). You do this by adjusting the `/boot/config.txt`.
 
-For both processes below you will need to insert your SD card into your PC and open the `/boot/config.txt` file with your favorite text editor.
+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`.
+
+#### Raspberry Pi 5 procedure
+
+Add the following parameters to the bottom of the `config.txt` file.
+
+```text
+dtoverlay=uart0
+```
 
 #### Raspberry Pi 4 procedure
 

source/_includes/asides/docs_navigation.html

@@ -8,14 +8,19 @@
         <b>{% active_link /docs/glossary/ Glossary %}</b>
       </li>
       <li>
-        <b>{% active_link /getting-started Getting started %}</b>
+        <b>Getting started</b>
         <ul>
           <li>{% active_link /installation Installation %}</li>
+          <li>{% active_link /getting-started Getting started & onboarding %}</li>
+          <li>{% active_link /dashboards Dashboards & views %}</li>
           <li>{% active_link /common-tasks/os/ Common tasks %}</li>
           <li>
             {% active_link /docs/troubleshooting/ Troubleshooting installation
             %}
           </li>
+          <li>
+            {% active_link /docs/troubleshooting_general/ General troubleshooting %}
+          </li>
         </ul>
       </li>
       <li>

source/_includes/common-tasks/backups.md

@@ -44,7 +44,8 @@ You might need a backup in case your system has crashed. If you only store them
 
 There are multiple ways to store the backup on another device:
 
-- **Option 1**: Under {% my supervisor_backups title="**Settings** > **System** > **Backups**" %}, select the backup from the list.
+- **Option 1**: Under {% my supervisor_backups title="**Settings** > **System** > **Backups**" %}, on the list, single-click or tap the backup of interest.
+  - **Result**: The backup dialog opens.
   - In the dialog, select the three dots menu and select **Download backup**.
   - **Result**: The selected backup is stored in the **Downloads** folder of your computer.
 - **Option 2**: If you haven't already done so, [configure access to files on Home Assistant](/common-tasks/{{page.installation}}/#configuring-access-to-files), using one of the methods listed there.

source/_includes/dashboard/edit_dashboard.md

@@ -3,6 +3,10 @@
 {% capture title %}{{ include.title | default: page.title }}{% endcapture %}
 
 To add the {{ title | downcase }} to your user interface:
-1. In the top right of the screen, select the three dots menu and then select **Edit dashboard**.
-   - By editing the dashboard, you are taking over control of this dashboard. This means that it is no longer automatically updated when new dashboard elements become available. To continue, in the dialog, select **Take control**.
-2. In the bottom right corner, select the **Add card** button  and select from the card picker.
+
+1. In the top right of the screen, select the pencil icon.
+   - If this is your first time editing a dashboard, the **Edit dashboard** dialog appears.
+     - By editing the dashboard, you are taking over control of this dashboard.
+     - This means that it is no longer automatically updated when new dashboard elements become available.
+     - To continue, in the dialog, select the three dots menu, then select **Take control**.
+2. In the bottom right corner, select the **Add card** button and select from the card picker.

source/_integrations/analytics_insights.markdown

@@ -18,6 +18,6 @@ The **Analytics Insights** {% term integration %} allows you to get integration
 The data comes from [Home Assistant Analytics](https://analytics.home-assistant.io/).
 For more information about the component that collects analytics, checkout [Analytics](/integrations/analytics).
 
-Only integrations with one or more active installations will be displayed. This means it will take some time before newly released integrations are visible.
+For a custom integration to show up, it should have its [brands](https://github.com/home-assistant/brands) merged.
 
 {% include integrations/config_flow.md %}

source/_integrations/braviatv.markdown

@@ -32,26 +32,84 @@ Almost all [Sony Bravia TV 2013 and newer](https://info.tvsideview.sony.net/en_w
 The Bravia TV integration supports two types of authentication:
 
 - **PSK (Pre-Shared-Key)** is a user-defined secret key used for access control. This authentication method is recommended as more reliable and stable. To set up and enable PSK on your TV, go to: **Settings -> Network -> Home Network Setup -> IP Control**.
-- **PIN Code** authentication is easier and does not require additional settings.
+- **PIN Code** authentication is easier and does not require additional settings. [See this guide](#tv-does-not-generate-new-pin) if your TV does not show the PIN code.
 
 For more information, see [IP Control Authentication](https://pro-bravia.sony.net/develop/integrate/ip-control/index.html#ip-control-authentication).
 
-## Common issues
-
-### TV does not generate new pin
-
-If you have previously set up your TV with any Home Assistant instances via PIN code, you must remove Home Assistant from your TV in order for your TV to generate a new pin. To do this, you must do **one** of the following:
-
-- On your TV, go to: **Settings** > **Network** > **Remote device settings** > **Deregister remote device**. Disable and re-enable the **Control remotely** after. Menu titles may differ slightly between models. If needed, refer to your specific model's [manual](https://www.sony.com/electronics/support/manuals) for additional guidance.
-- Reset your TV to factory condition.
-
 ## Media browser
 
-Using the media browser, you can view a list of all installed applications and TV channels and launch them.
+Using the media browser, you can view a list of all installed applications and TV channels and launch them. You can access the media browser from the **Media** section in the Home Assistant side menu or by selecting the **Browse media** button on the media player card.
+
+## Using with Google Cast
+
+The Bravia TV {% term integration %} provides information about the power status of the device, current source, and volume. It gives you the ability to control playback, run applications, and send remote control commands. Unfortunately, due to limitations of the Bravia REST API, it does not provide information about the currently playing content in applications (app name, media title, duration, play/pause state, etc.). In turn, the [Google Cast](/integrations/cast/) integration does not provide reliable information about the power status of the device (for example on Home Screen) and does not allow you to control playback in Android apps without [MediaSession](https://developer.android.com/reference/android/media/session/MediaSession) support. However, it can display full information about the content being played in supported apps. If your TV runs on Android or Google TV, you can use the Google Cast integration together with the Bravia TV integration. For convenience, you can combine two media players into one using [Universal Media Player](/integrations/universal/). Universal Media Player will automatically select the appropriate active media player entity.
+
+{% details "Example YAML configuration" %}
+
+Replace `media_player.sony_tv_native` with your Bravia TV integration media player {% term entity %} ID. Replace `media_player.sony_tv_cast` with your Google Cast integration media player {% term entity %} ID.
+
+{% raw %}
+
+```yaml
+media_player:
+  - platform: universal
+    name: Sony TV
+    unique_id: sony_tv_combined
+    device_class: tv
+    children:
+      - media_player.sony_tv_native
+      - media_player.sony_tv_cast
+    active_child_template: >
+      {% if state_attr('media_player.sony_tv_native', 'media_content_id') %}
+         media_player.sony_tv_native
+      {% endif %}
+    attributes:
+      source: media_player.sony_tv_native|source
+      source_list: media_player.sony_tv_native|source_list
+    browse_media_entity: media_player.sony_tv_native
+    commands:
+      turn_off:
+        service: media_player.turn_off
+        data:
+          entity_id: media_player.sony_tv_native
+      turn_on:
+        service: media_player.turn_on
+        data:
+          entity_id: media_player.sony_tv_native
+      select_source:
+        service: media_player.select_source
+        data:
+          entity_id: media_player.sony_tv_native
+          source: "{{ source }}"
+      media_play:
+        service: media_player.media_play
+        target:
+          entity_id: media_player.sony_tv_native
+      media_pause:
+        service: media_player.media_pause
+        target:
+          entity_id: media_player.sony_tv_native
+      media_play_pause:
+        service: media_player.media_play_pause
+        target:
+          entity_id: media_player.sony_tv_native
+      media_previous_track:
+        service: media_player.media_previous_track
+        target:
+          entity_id: media_player.sony_tv_native
+      media_next_track:
+        service: media_player.media_next_track
+        target:
+          entity_id: media_player.sony_tv_native
+```
+
+{% endraw %}
+
+{% enddetails %}
 
 ## Play media service
 
-The `play_media` {% term service %} can be used in an automation or script to switch to a specified application or TV channel. It selects the best matching application or channel according to the `media_content_id`:
+The `play_media` {% term service %} can be used in an {% term automation %} or {% term script %} to switch to a specified application or TV channel. It selects the best matching application or channel according to the `media_content_id`:
 
  1. Channel number *(i.e., '1' or '6')*
  2. Exact app or channel name *(i.e., 'Google Play' or 'CNN')*
@@ -93,9 +151,19 @@ data:
 
 ## Remote
 
-The integration supports `remote` platform. The remote allows you to send key commands to your TV with the `remote.send_command` service.
+The {% term integration %} supports `remote` {% term platform %}. It allows you to send remote control commands to your TV with the `remote.send_command` service.
 
-The commands that can be sent to the TV depends on the model of your TV. To display a list of supported commands for your TV, call the service `remote.send_command` with non-valid command (e.g. `Test`). A list of available commands will be displayed in [Home Assistant System Logs](https://my.home-assistant.io/redirect/logs).
+The commands that can be sent to the TV depend on the model of your TV. To display a list of supported commands for your TV, call the {% term service %} `remote.send_command` with non-valid command (e.g. `Test`). A list of available commands will be displayed in [Home Assistant System Logs](https://my.home-assistant.io/redirect/logs).
+
+**Example to send `Down` key command:**
+
+```yaml
+service: remote.send_command
+target:
+  entity_id: remote.bravia_tv
+data:
+  command: "Down"
+```
 
 {% details "Some commonly used commands" %}
 
@@ -124,20 +192,34 @@ The commands that can be sent to the TV depends on the model of your TV. To disp
 
 {% enddetails %}
 
-**Example to send `Down` key command:**
-
-```yaml
-service: remote.send_command
-target:
-  entity_id: remote.bravia_tv
-data:
-  command: "Down"
-```
-
 ## Buttons
 
-The integration supports `button` platform and allows you to reboot the device or terminate all running applications.
+The {% term integration %} supports `button` {% term platform %} and allows you to reboot the device or terminate all running applications.
 
-## For TVs older than 2013
+## Limitations and known issues
+
+### TV does not generate new PIN
+
+If you have previously set up your TV with any Home Assistant instances via PIN code, you must remove Home Assistant from your TV in order for your TV to generate a new PIN. On your TV, go to: **Settings** > **Network** > **Remote device settings** > **Deregister remote device**. Menu titles may differ slightly between models. If needed, refer to your specific model's [manual](https://www.sony.com/electronics/support/manuals) for additional guidance.
+
+### Sometimes, the integration displays an error in the logs and does not respond to commands
+
+Unfortunately, the system service application (WebApiCore) on the TV that provides Sony Bravia REST API does not work very well and has many problems. The service may begin to reboot spontaneously or freeze, especially when the TV has not been rebooted for a long time or a heavy application is running. Perhaps sometimes the process is killed by Android TV itself due to lack of memory. When the service is being rebooted (about 30 seconds), the API will be unavailable, and any interaction with the {% term integration %} may result in an error in the logs.
+
+If you encounter this, you must completely reboot your TV. To do this, hold down the **Power** button on the remote control and select **Restart**. In addition, we recommend periodically completely restarting your TV. You can also create an {% term automation %} that will automatically restart the TV (for example, every night if the TV is turned off).
+
+If this happens very often, you can try to reset **WebApiCore** service. On your TV, go to: **Settings** > **Apps** > **See all aps** > Find **WebApiCore** > Press **Clear data**.
+
+### Integration shows 'Smart TV' instead of the name of the running application
+
+See [Using with Google Cast](#using-with-google-cast) section for more details.
+
+### Power consumption ~15 W when the TV in standby mode while integration is enabled
+
+The Bravia TV is [local pulling integration](https://www.home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/#polling-the-local-device). Even if the TV is turned off, its status is constantly polled to determine the current state, so the TV's network interface remains enabled. This is normal behavior. If you are concerned about this, you can disable polling for updates in the integration **System options** menu, but the TV status will no longer update automatically and you will have to force the {% term entity %} update by calling `homeassistant.update_entity` {% term service %} manually.
+
+Please note that this behavior can be caused not only by the integration, but also by some applications installed on the TV.
+
+### For TVs older than 2013
 
 Users of TVs older than 2013 can control their devices using [HDMI-CEC](/integrations/hdmi_cec/), [Broadlink](/integrations/broadlink/) or [Kodi](/integrations/kodi/) integrations.

source/_integrations/ecovacs.markdown

@@ -34,7 +34,7 @@ The `ecovacs` {% term integration %} is the main integration to integrate [Ecova
 
 Additional note: There are some issues during the password encoding. Using some special characters (e.g., `-`) in your password does not work.
 
-With `advanced_mode` enabled, users can use their self-hosted instance over the cloud servers. Self-hosting comes with some requirements and limitations. More information can be found in the [Bumper's documentation](https://bumper.readthedocs.io).
+With `advanced_mode` enabled, users can use their self-hosted instance over the cloud servers. Self-hosting comes with some requirements and limitations. See [Self-hosted configuration](#self-hosted-configuration) for additional details.
 
 ## Provided entities
 
@@ -131,3 +131,16 @@ Alternatively, you can use the `ecovacs_error` event to watch for errors. This e
 ```
 
 Finally, if a vacuum becomes unavailable (usually due to being idle and off its charger long enough for it to completely power off,) the vacuum's `status` attribute will change to `offline` until it is turned back on.
+
+## Self-hosted configuration
+
+Depending on your setup of the self-hosted instance, you can connect to the server using the following settings:
+- `Username`: Enter the e-mail address configured in your instance. If authentication is disabled, you can enter any valid e-mail address.
+- `Password`: Enter the password configured in your instance. If authentication is disabled, you can enter any string (series of characters).
+- `REST URL`: http://`SELF_HOSTED_INSTANCE`:8007
+- `MQTT URL`: mqtts://`SELF_HOSTED_INSTANCE`:8883
+- `Verify MQTT SSL certificate`: disabled
+
+Replace `SELF_HOSTED_INSTANCE` with either the IP address or the hostname of your instance.
+
+The above configuration is based on the information from [Bumper's documentation](https://bumper.readthedocs.io). 

source/_integrations/fan.mqtt.markdown

@@ -328,7 +328,6 @@ mqtt:
       command_topic: "bedroom_fan/on/set"
       direction_state_topic: "bedroom_fan/direction/state"
       direction_command_topic: "bedroom_fan/direction/set"
-      oscillation_command_topic: "bedroom_fan/oscillation/set"
       oscillation_state_topic: "bedroom_fan/oscillation/state"
       oscillation_command_topic: "bedroom_fan/oscillation/set"
       percentage_state_topic: "bedroom_fan/speed/percentage_state"

source/_integrations/powerwall.markdown

@@ -47,42 +47,41 @@ The following binary sensors are added for each Backup Gateway:
 The following sensors are added for each Backup Gateway aggregated across all Powerwalls:
 
 - Powerwall Backup Reserve - Reserve energy for grid outages in %
-- Powerwall Battery Now - Usage in kW
+- Powerwall Battery Now - Power in kW (negative for charging)
 - Powerwall Charge - Percent charge remaining in %
-- Powerwall Generator Now - Usage in kW (if applicable)
-- Powerwall Load Now - Load usage in kW
-- Powerwall Solar Now - Solar usage in kW (if applicable)
-- Powerwall Site Now - Site usage in kW
+- Powerwall Generator Now - Power in kW (if applicable)
+- Powerwall Load Now - Power in kW
+- Powerwall Solar Now - Power in kW (if applicable)
+- Powerwall Site Now - Power in kW (negative for grid export)
 - Powerwall Backup Reserve - Percentage of battery which will be reserved for a grid outage
-- Frequency/ Average Current/ Average Voltage Now
+- Frequency/ Average Current/ Average Voltage Now - in Hertz, Amps and Volts
 
-The following sensors show the direction of energy in aggregate:
+The following sensors measure lifetime energy flow:
 
 - Powerwall Solar Export - Solar energy exported in kWh
-- Powerwall Solar Import - Solar energy imported in kWh
+- Powerwall Solar Import - Solar energy imported in kWh (generally near zero)
 - Powerwall Site Export - Site energy exported in kWh
 - Powerwall Site Import - Site energy imported in kWh
 - Powerwall Battery Export - Battery energy exported in kWh
 - Powerwall Battery Import - Battery energy imported in kWh
-- Powerwall Load Export - Load energy exported in kWh
+- Powerwall Load Export - Load energy exported in kWh (generally zero)
 - Powerwall Load Import - Load energy imported in kWh
-- Powerwall Generator Export - Generator energy exported in kWh
+- Powerwall Generator Export - Generator energy exported in kWh 
 - Powerwall Generator Import - Generator energy imported in kWh
 
-The following sensors are added for each Powerwall:
-- Powerwall Battery Capacity - Capacity in kWh
-- Powerwall Battery Remaining - Remaining capacity in kWh
-- Frequency/ Average Current/ Average Voltage Now
-- Powerwall Load Now - Load usage in kW
+A Powerwall battery device for each battery, connected to the Powerwall Gateway, with the following sensors:
+- Powerwall Battery Capacity - Energy in kWh
+- Powerwall Battery Remaining - Remaining energy in kWh
+- Frequency/ Average Current/ Average Voltage Now in Hertz, Amps and Volts
+- Powerwall Battery Power - Battery power in kW (negative for charging)
 - Powerwall Battery Export - Battery energy exported in kWh
 - Powerwall Battery Import - Battery energy imported in kWh
-- Powerwall Charge - Percent charge remaining in %
-- Powerwall Grid State - State of grid power
+- Powerwall Grid State - Battery grid compliance
 
 
 ### Switch
 
-The following switches are added for each Powerwall Backup Gateway:
+The following switch is added for the Powerwall Backup Gateway:
 
 - Off-Grid operation - Take your Powerwall off-grid (simulate a grid outage)
 

source/_integrations/recovery_mode.markdown

@@ -10,19 +10,23 @@ ha_quality_scale: internal
 ha_integration_type: system
 ---
 
-The `recovery_mode` integration is an internally used integration by the
+The **Recovery mode** integration is an internal integration used by the
 Home Assistant Core.
 
-You don't have to configure it in any way since it is automatically always
+You don't have to configure it since it is automatically always
 available when Home Assistant needs it.
 
 If, during startup, Home Assistant has problems reading your configuration,
-it will still continue to start using bits and pieces from the configuration
-of the last time it did start.
+it will still continue to start using parts of the configuration
+from the last time Home Assistant did start.
 
-When this happens, Home Assistant will start in "Recovery mode" using this
-integration. In this mode, nothing is loaded, but it does give you access to
+When this happens, Home Assistant will start in **Recovery mode** using this
+integration. In this mode, no user configured integrations are loaded, but it does give you access to
 the Home Assistant frontend, settings and add-ons.
 
 This gives you the possibility to correct the issue and restart Home Assistant
 to re-try.
+
+## Related topics
+
+- [General troubleshooting](/docs/troubleshooting_general/)

source/_integrations/reolink.markdown

@@ -38,9 +38,20 @@ Protocol:
   description: Switch between RTSP, RTMP or FLV streaming protocol.
 {% endconfiguration_basic %}
 
+## Asterisk (*) next to entities listed in this documentation
+
+If an entity listed below has an asterisk (*) next to its name, it means it is disabled by default. To use such an entity, you must [enable the entity](/common-tasks/general/#enabling-entities) first.
+
 ## Camera streams
 
-This integration creates a few camera entities, one for each stream type with different resolutions: Clear, Fluent, Balanced, Snapshots Clear, and Snapshots Fluent.
+This integration creates a few camera entities, one for each stream type with different resolutions:
+
+- Fluent (Low resolution)
+- Balanced* (Mid resolution)
+- Clear* (High resolution, resource intensive)
+- Snapshots Fluent* (Low resolution)
+- Snapshots Clear* (High resolution)
+
 The Fluent stream camera entity is enabled by default; the other streams are disabled by default.
 The Snapshots stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate; this can be used when the RTMP/RTSP/FLV video stream has too much lag.
 Dual lens cameras provide additional streams for the second lens.
@@ -64,10 +75,6 @@ Not all camera models generate ONVIF push events for all event types, some binar
 For list of Reolink products that support ONVIF see the [Reolink Support Site](https://support.reolink.com/hc/en-us/articles/900000617826).
 To ensure you have the best latency possible, refer to the [Reducing latency of motion events](#reducing-latency-of-motion-events) section.
 
-## Asterisk (*) next to entities listed in this documentation
-
-If an entity listed below has an asterisk (*) next to its name, it means it is disabled by default. To use such an entity, you must [enable the entity](/common-tasks/general/#enabling-entities) first.
-
 ## Number entities
 
 Depending on the supported features of the camera, number entities are added for:

source/_integrations/screenlogic.markdown

@@ -60,8 +60,8 @@ Begins super chlorination, running for the specified period or 24 hours if none
 
 Stops super chlorination.
 
-| Service data attribute | Optional | Description                                                                          |
-| ---------------------- | -------- | ------------------------------------------------------------------------------------ |
+| Service data attribute | Optional | Description                                                                              |
+| ---------------------- | -------- | ---------------------------------------------------------------------------------------- |
 | `config_entry`         | no       | Integration entry_id of the ScreenLogic instance you wish to stop super chlorination on. |
 
 ## Reference

source/_integrations/simplisafe.markdown

@@ -42,7 +42,7 @@ There is currently support for the following device types within Home Assistant:
 
 ## SimpliSafe Plans
 
-SimpliSafe offers several [monitoring plans](https://support.simplisafe.com/articles/alarm-events-monitoring/what-are-the-service-plan-options/6344794a013ba90af0bce6a4). Currently, only the Standard and Fast Protect are known to work with this integration; if you find otherwise, please consider updating this documentation.
+SimpliSafe offers several [monitoring plans](https://support.simplisafe.com/articles/alarm-events-monitoring/what-are-the-service-plan-options/6344794a013ba90af0bce6a4). All plans (including the free plan) should work with this integration.  
 
 {% include integrations/config_flow.md %}
 

source/_integrations/sms.markdown

@@ -185,6 +185,8 @@ Re-plug the USB stick, reboot the device, run `lsusb` again.
 The resulting product id now should be different and the brand id should be the same.
 And `ls -l /dev/*USB*` should now report your device.
 
+Note: if you have multiple USB devices, USB number order can change on boot. For this reason, it's preferable to use your device ID and look in `/dev/serial/by-id/*`. For example,  `/dev/serial/by-id/usb-HUAWEI_MOBILE_HUAWEI_MOBILE-if00-port0`.
+
 If the device is still not recognized, remove the parameter -X from the usb_modeswitch command and reboot again.
 
 ## More details:

source/_integrations/sql.markdown

@@ -122,7 +122,7 @@ See [supported engines](/integrations/recorder/#custom-database-engines) for whi
 
 The SQL integration will connect to the Home Assistant Recorder database if "Database URL" has not been specified.
 
-There is no explicit configuration required for attributes. The integration will set all additional columns returned by the query as attributes. 
+There is no explicit configuration required for attributes. The integration will set all columns returned by the query as attributes.
 
 Note that in all cases only the first row returned will be used.
 

source/_integrations/template.markdown

@@ -55,15 +55,15 @@ Button, image, number, and select template entities are defined in your YAML con
 
 _For old sensor/binary sensor configuration format, [see below](#legacy-binary-sensor-configuration-format)._
 
-# UI configuration
+## UI configuration
 
 Sensor template and binary sensor template can be configured using the user interface at **{% my helpers title="Settings > Devices & Services > Helpers" %}**. Select the **+ Add helper** button and then select the **{% my config_flow_start domain=page.ha_domain title=page.title %}** helper.
 
 To be able to add **{% my helpers title="Helpers" %}** via the user interface, you should have `default_config:` in your `configuration.yaml`. It should already be there by default unless you removed it.
 
-# YAML configuration
+## YAML configuration
 
-## State-based template binary sensors, buttons, images, numbers, selects and sensors
+### State-based template binary sensors, buttons, images, numbers, selects and sensors
 
 Template entities will by default update as soon as any of the referenced data in the template updates.
 
@@ -86,7 +86,7 @@ template:
 {% endraw %}
 
 
-## Trigger-based template binary sensors, buttons, images, numbers, selects and sensors
+### Trigger-based template binary sensors, buttons, images, numbers, selects and sensors
 
 If you want more control over when an entity updates, you can define a trigger. Triggers follow the same format and work exactly the same as [triggers in automations][trigger-doc]. This feature is a great way to create entities based on webhook data ([example](#trigger-based-sensor-and-binary-sensor-storing-webhook-information)), or update entities based on a schedule.
 
@@ -405,16 +405,16 @@ template:
 
 [trigger-doc]: /docs/automation/trigger
 
-### Video tutorial
+#### Video tutorial
 This video tutorial explains how to set up a Trigger based template that makes use of an action to retrieve the weather forecast (precipitation).
 
 <lite-youtube videoid="zrWqDjaRBf0" videotitle="How to create Action Template Sensors in Home Assistant" posterquality="maxresdefault"></lite-youtube>
 
-## Template and action variables
+### Template and action variables
 
 State-based and trigger-based template entities have the special template variable `this` available in their templates and actions. The `this` variable is the [state object](/docs/configuration/state_object) of the entity and aids [self-referencing](#self-referencing) of an entity's state and attribute in templates and actions. Trigger-based entities also provide [the trigger data](/docs/automation/templating/). 
 
-## Rate limiting updates
+### Rate limiting updates
 
 When there are entities present in the template and no triggers are defined, the template will be re-rendered when one of the entities changes states. To avoid this taking up too many resources in Home Assistant, rate limiting will be automatically applied if too many states are observed.
 
@@ -455,9 +455,9 @@ template:
 
 If the template accesses every state on the system, a rate limit of one update per minute is applied. If the template accesses all states under a specific domain, a rate limit of one update per second is applied. If the template only accesses specific states, receives update events for specifically referenced entities, or the `homeassistant.update_entity` service is used, no rate limit is applied.
 
-## Considerations
+### Considerations
 
-### Startup
+#### Startup
 
 If you are using the state of a platform that might not be available during startup, the Template Sensor may get an `unknown` state. To avoid this, use the `states()` function in your template. For example, you should replace {% raw %}`{{ states.sensor.moon.state }}`{% endraw %} with this equivalent that returns the state and never results in `unknown`: {% raw %}`{{ states('sensor.moon') }}` {% endraw %}. 
 

source/_integrations/tractive.markdown

@@ -30,6 +30,10 @@ To use the integration you must be a premium tractive client.
 
 {% include integrations/config_flow.md %}
 
+<div class="note">
+Due to Tractive API limitations, trackers (pets) that are shared from another account to your account are not visible in Home Assistant. You need to configure all Tractive accounts from which trackers (pets) come from with Home Assistant.
+</div>
+
 ## Integration entities
 
 The Tractive integration adds one device tracker and several sensors and switches per registered pet:

source/_integrations/verisure.markdown

@@ -82,3 +82,12 @@ automation:
 | code | Lock was unlocked by exterior code |
 | auto | Lock was locked/unlocked automatically by Verisure rule |
 | remote | Lock was locked/unlocked automatically by Verisure App |
+
+## Limitations and known issues
+
+Some users have reported that this integration currently doesn't work in the following countries:
+
+- France
+- Ireland
+- Italy 
+- Sweden

source/_integrations/weatherflow.markdown

@@ -37,8 +37,8 @@ This {% term integration %} will expose the following sensors:
 - Irradiance
 - Lightning average distance
 - Lightning count
-- Precipitation
-- Precipitation amount
+- Precipitation (accumulated over the previous minute)
+- Precipitation intensity ([extrapolated](https://weatherflow.github.io/Tempest/api/derived-metric-formulas.html#rain-rate) from the accumulation over the previous minute)
 - Precipitation type
 - Temperature
 - UV index

source/_integrations/yolink.markdown

@@ -55,67 +55,48 @@ Service data attribute | Optional | Description
 
 The integration is tested and verified for the following devices from YoLink:
 
-- YS1604 (SpeakerHub)
-- YS3604 (FlexFob)
+- YS1603-UC (Hub)
+- YS1604-UC (SpeakerHub)
 - YS3604-UC (YoLink KeyFob)
 - YS3605-UC (YoLink On/OffFob)
 - YS3606-UC (YoLink DimmerFob)
 - YS3607-UC (YoLink SirenFob)
 - YS4002-UC (YoLink Thermostat)
-- YS4002/3 (Thermostat)
 - YS4003-UC (YoLink Thermostat Heatpump)
 - YS4906-UC + YS7706-UC (Garage Door Kit 1)
-- YS4906/8 (Garage Door Sensor/ Garage Door Controller)
-- YS4908 (Finger)
 - YS4908-UC + YS7706-UC (Garage Door Kit 2 (Finger))
-- YS4909 YS5001 (valve controller)
 - YS4909-UC (Water Valve Controller)
 - YS5001-UC (X3 Water Valve Controller)
 - YS5002-UC (YoLink Motorized Ball Valve)
 - YS5003-UC (Water Valve Controller 2)
 - YS5705-UC (In-Wall Switch)
-- YS5705/6 (switch)
 - YS5706-UC (YoLink Relay)
-- YS5707 (Dimmer)
 - YS5707-UC (Dimmer Switch)
 - YS5708-UC (In-Wall Switch 2)
 - YS6602-UC (YoLink Energy Plug)
-- YS6602/4 YS6704 (outlet | plug)
 - YS6604-UC (YoLink Plug Mini)
 - YS6704-UC (In-wall Outlet)
 - YS6801-UC (Smart Power Strip)
-- YS6801/2 (MultiOutlet)
 - YS6802-UC (Smart Outdoor Power Strip)
 - YS7103-UC (Siren Alarm)
-- YS7103/4/5 (siren)
 - YS7104-UC (Outdoor Alarm Controller)
 - YS7105-UC (X3 Outdoor Alarm Controller)
-- YS7106 (PowerFailureAlar)
 - YS7106-UC (Power Fail Alarm)
 - YS7107-UC (Outdoor Alarm Controller 2)
-- YS7201 (vibration sensor)
 - YS7201-UC (Vibration Sensor)
 - YS7606-UC (YoLink Smart Lock M1)
-- YS7606/7 (lock)
 - YS7607-UC (YoLink Smart Lock M2)
 - YS7704-UC (Door Sensor)
-- YS7704/7705/7706 (door sensor)
 - YS7706-UC (Garage Door Sensor)
-- YS7707 (Contact Sensor)
 - YS7707-UC (Contact Sensor)
 - YS7804-UC (Motion Sensor)
-- YS7804/5 (motion sensor)
-- YS7805 (Outdoor Motion Detector Sensor)
 - YS7805-UC (Outdoor Motion Sensor)
 - YS7903-UC (Water Leak Sensor)
-- YS7903/4 (leak sensor)
 - YS7904-UC (Water Leak Sensor 2)
 - YS7906-UC (Water Leak Sensor 4)
 - YS7916-UC (Water Leak Sensor 4 MoveAlert)
 - YS7A01-UC (Smart Smoke/CO Alarm)
-- YS7A01/2 (CO & Smoke Sensor)
 - YS8003-UC (Temperature Humidity Sensor)
-- YS8003/4/5/6 (temperature/humidity sensor)
 - YS8004-UC (Weatherproof Temperature Sensor)
 - YS8005-UC (Weatherproof Temperature & Humidity Sensor)
 - YS8006-UC (X3 Temperature & Humidity Sensor)

source/_posts/2024-02-07-release-20242.markdown

@@ -60,6 +60,9 @@ _Oh! And don't forget Valentine's Day is coming up!_ 😘
 - [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
 - [Release 2024.2.1 - February 9](#release-202421---february-9)
 - [Release 2024.2.2 - February 16](#release-202422---february-16)
+- [Release 2024.2.3 - February 22](#release-202423---february-22)
+- [Release 2024.2.4 - February 25](#release-202424---february-25)
+- [Release 2024.2.5 - February 27](#release-202425---february-27)
 - [Need help? Join the community!](#need-help-join-the-community)
 - [Backward-incompatible changes](#backward-incompatible-changes)
 - [Farewell to the following](#farewell-to-the-following)
@@ -279,7 +282,7 @@ noteworthy changes this release:
 
 - [@edenhaus] improved how we handle errors in our form fields. We no longer
   show the technical coding gibberish that often showed up in the past. Nice!
-- When you [change the type of a switch entity] to, for example, a garage door 
+- When you [change the type of a switch entity] to, for example, a garage door
   entity, you will now have the option to invert its behavior.
   Thanks, [@emontnemery]!
 - The [Ecovacs] integration received lots of love from [@edenhaus] and now
@@ -367,7 +370,7 @@ We welcome the following new integrations in this release:
 - **[Tedee]**, added by [@zweckj]<br />
   Use your Tedee smart locks in Home Assistant.
 - **[Teslemetry]**, added by [@Bre77]<br />
-  Pull in live telemetry data from your Tesla vehicle via the Tesla Fleet API. 
+  Pull in live telemetry data from your Tesla vehicle via the Tesla Fleet API.
 - **[TechnoVE]**, added by [@Moustachauve]<br />
   Control of TechnoVE Smart Charging Station using a local API.
 - **[Traccar server]**, added by [@ludeeus]<br />
@@ -610,6 +613,141 @@ The following integrations are now available via the Home Assistant UI:
 [@wilburCforce]: https://github.com/wilburCforce
 [@zxdavb]: https://github.com/zxdavb
 
+## Release 2024.2.3 - February 22
+
+- Fix reauth in Overkiz for config entries created prior to 2022.12 ([@iMicknl] - [#106251])
+- Handle deep standby and poweroffs of enigma2 devices gracefully ([@autinerd] - [#107462])
+- Add wake up timeout to Teslemetry ([@Bre77] - [#109037])
+- Fix set_temperature in Tessie climate platform ([@Bre77] - [#110445])
+- Fix uuid issue in Lutron ([@wilburCforce] - [#110524])
+- Update rokuecp to 0.19.1 ([@ctalkington] - [#110670])
+- Fix scene activation with climate entities with `None` attribute values ([@mib1185] - [#110684])
+- Remove matplotlib pinning due to Python 3.12 incompatibility ([@sbyx] - [#110706])
+- Bump roombapy to 1.6.12 ([@mib1185] - [#110762])
+- Ensure Tile timestamps are reported as UTC ([@bachya] - [#110773])
+- Detect reached API rate limit in Tankerkoenig ([@mib1185] - [#110432])
+- Bump aiotankerkoenig to 0.4.1 ([@jpbede] - [#110840])
+- Update govee-local-api library to 1.4.4 ([@Galorhallen] - [#110854])
+- Allow loading of more then 1 defined Apprise URL ([@caronc] - [#110868])
+- Reolink continue setup when internet blocked ([@starkillerOG] - [#110888])
+- Bump deluge-client to 1.10.0 ([@tkdrob] - [#110663])
+- Bump deluge-client to 1.10.2 ([@dsander] - [#110905])
+- Bump reolink-aio to 0.8.8 ([@starkillerOG] - [#110959])
+- Reset error state when Ecovacs bot is operational again ([@mib1185] - [#110962])
+- Bump motionblinds to 0.6.21 ([@starkillerOG] - [#110970])
+- Bump holidays to 0.43 ([@gjohansson-ST] - [#111039])
+- Fixes UniFi Protect light state check ([@AngellusMortis] - [#111058])
+- Bump pywebpush to 1.14.1 ([@thecode] - [#111082])
+- Bump aioairzone to v0.7.4 ([@Noltari] - [#111105])
+- Bump deebot-client to 5.2.2 ([@edenhaus] - [#111112])
+- Ignore cloudhook already removed in mobile app ([@joostlek] - [#111122])
+
+[#106251]: https://github.com/home-assistant/core/pull/106251
+[#107462]: https://github.com/home-assistant/core/pull/107462
+[#109037]: https://github.com/home-assistant/core/pull/109037
+[#109883]: https://github.com/home-assistant/core/pull/109883
+[#110078]: https://github.com/home-assistant/core/pull/110078
+[#110432]: https://github.com/home-assistant/core/pull/110432
+[#110445]: https://github.com/home-assistant/core/pull/110445
+[#110524]: https://github.com/home-assistant/core/pull/110524
+[#110663]: https://github.com/home-assistant/core/pull/110663
+[#110670]: https://github.com/home-assistant/core/pull/110670
+[#110684]: https://github.com/home-assistant/core/pull/110684
+[#110706]: https://github.com/home-assistant/core/pull/110706
+[#110720]: https://github.com/home-assistant/core/pull/110720
+[#110762]: https://github.com/home-assistant/core/pull/110762
+[#110773]: https://github.com/home-assistant/core/pull/110773
+[#110840]: https://github.com/home-assistant/core/pull/110840
+[#110854]: https://github.com/home-assistant/core/pull/110854
+[#110868]: https://github.com/home-assistant/core/pull/110868
+[#110888]: https://github.com/home-assistant/core/pull/110888
+[#110905]: https://github.com/home-assistant/core/pull/110905
+[#110959]: https://github.com/home-assistant/core/pull/110959
+[#110962]: https://github.com/home-assistant/core/pull/110962
+[#110970]: https://github.com/home-assistant/core/pull/110970
+[#111035]: https://github.com/home-assistant/core/pull/111035
+[#111039]: https://github.com/home-assistant/core/pull/111039
+[#111058]: https://github.com/home-assistant/core/pull/111058
+[#111082]: https://github.com/home-assistant/core/pull/111082
+[#111105]: https://github.com/home-assistant/core/pull/111105
+[#111112]: https://github.com/home-assistant/core/pull/111112
+[#111122]: https://github.com/home-assistant/core/pull/111122
+[@AngellusMortis]: https://github.com/AngellusMortis
+[@Bre77]: https://github.com/Bre77
+[@Galorhallen]: https://github.com/Galorhallen
+[@Noltari]: https://github.com/Noltari
+[@autinerd]: https://github.com/autinerd
+[@bachya]: https://github.com/bachya
+[@caronc]: https://github.com/caronc
+[@ctalkington]: https://github.com/ctalkington
+[@dsander]: https://github.com/dsander
+[@edenhaus]: https://github.com/edenhaus
+[@frenck]: https://github.com/frenck
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@iMicknl]: https://github.com/iMicknl
+[@joostlek]: https://github.com/joostlek
+[@jpbede]: https://github.com/jpbede
+[@mib1185]: https://github.com/mib1185
+[@sbyx]: https://github.com/sbyx
+[@starkillerOG]: https://github.com/starkillerOG
+[@thecode]: https://github.com/thecode
+[@tkdrob]: https://github.com/tkdrob
+[@wilburCforce]: https://github.com/wilburCforce
+
+## Release 2024.2.4 - February 25
+
+- Return group unit of measurement when device_class is None ([@PoppyPop] - [#110973]) ([group docs])
+- Bump roombapy to 1.6.13 ([@Orhideous] - [#111187]) ([roomba docs])
+- Bump orjson to 3.9.15 ([@bdraco] - [#111233])
+- Set Lutron switch to device name ([@joostlek] - [#111293]) ([lutron docs])
+- Bump opower to 0.3.0 ([@swartzd] - [#109248]) ([opower docs])
+- Bump opower to 0.3.1 ([@benhoff] - [#111307])
+- Fix another name missing in wyoming getLogger ([@llluis] - [#111390]) ([wyoming docs])
+- Update caldav to 1.3.9 ([@cdce8p] - [#111429]) ([caldav docs])
+- Update guppy3 to 3.1.4.post1 ([@cdce8p] - [#111430]) ([profiler docs])
+- Bump openwebifpy to 4.2.4 ([@autinerd] - [#110676]) ([enigma2 docs])
+
+[@autinerd]: https://github.com/autinerd
+[enigma2 docs]: /integrations/enigma2/
+[#110676]: https://github.com/home-assistant/core/pull/110676
+[#109248]: https://github.com/home-assistant/core/pull/109248
+[#109883]: https://github.com/home-assistant/core/pull/109883
+[#110078]: https://github.com/home-assistant/core/pull/110078
+[#110720]: https://github.com/home-assistant/core/pull/110720
+[#110973]: https://github.com/home-assistant/core/pull/110973
+[#111133]: https://github.com/home-assistant/core/pull/111133
+[#111187]: https://github.com/home-assistant/core/pull/111187
+[#111233]: https://github.com/home-assistant/core/pull/111233
+[#111293]: https://github.com/home-assistant/core/pull/111293
+[#111307]: https://github.com/home-assistant/core/pull/111307
+[#111390]: https://github.com/home-assistant/core/pull/111390
+[#111429]: https://github.com/home-assistant/core/pull/111429
+[#111430]: https://github.com/home-assistant/core/pull/111430
+[@Orhideous]: https://github.com/Orhideous
+[@PoppyPop]: https://github.com/PoppyPop
+[@bdraco]: https://github.com/bdraco
+[@benhoff]: https://github.com/benhoff
+[@cdce8p]: https://github.com/cdce8p
+[@frenck]: https://github.com/frenck
+[@joostlek]: https://github.com/joostlek
+[@llluis]: https://github.com/llluis
+[@swartzd]: https://github.com/swartzd
+[abode docs]: /integrations/abode/
+[caldav docs]: /integrations/caldav/
+[group docs]: /integrations/group/
+[lutron docs]: /integrations/lutron/
+[opower docs]: /integrations/opower/
+[profiler docs]: /integrations/profiler/
+[roomba docs]: /integrations/roomba/
+[wyoming docs]: /integrations/wyoming/
+
+## Release 2024.2.5 - February 27
+
+- Add title to reauthenticate integration issue ([@timmo001] - [#111275])
+
+[#111275]: https://github.com/home-assistant/core/pull/111275
+[@timmo001]: https://github.com/timmo001
+
 ## Need help? Join the community!
 
 Home Assistant has a great community of users who are all more than willing
@@ -1149,11 +1287,11 @@ The following integrations are also no longer available as of this release:
   ([@reedy] - [#107005])
 - **Legrand Home+ Control** has been removed as their API shut down in December.
   Use [the Netatmo integration](/integrations/netatmo/) as an alternative to
-  integrate your Legrand Home+ Control devices.  
+  integrate your Legrand Home+ Control devices.
   ([@jpbede] - [#107587])
 - **Life360** has been removed. They are now actively blocking third-party
   access, including Home Assistant. The [Home Assistant Companion app](https://companion.home-assistant.io/)
-  is a good and (above all) privacy-friendly alternative.  
+  is a good and (above all) privacy-friendly alternative.
   ([@pnbruckner] - [#107805])
 
 [@jpbede]: https://github.com/jpbede

source/_posts/2024-02-21-voice-chapter-6.markdown

@@ -0,0 +1,145 @@
+---
+layout: post
+title: "On device wake word on ESP32-S3 is here - Voice: Chapter 6"
+description: "This chapter brings on-device wake word detection (microWakeWord), customization for sentence triggers, additional intents for controlling devices, and better error messages."
+date: 2024-02-21 00:00:00
+date_formatted: "February 21, 2024"
+author: Michael Hansen
+comments: true
+categories: Assist
+og_image: /images/blog/2024-02-21-voice-chapter-6/social.jpg
+---
+
+**TL;DR:** We have added on-device wake word detection (microWakeWord)! It's faster and more scalable than processing the wake word in Home Assistant. We will keep supporting wake word processing in Home Assistant. Also new is more customization for sentence triggers, additional intents for controlling more devices, and better error messages and debugging tools.
+
+<p class='img'>
+<lite-youtube videoid="NQIv3nsu7dE" videotitle="Voice - Chapter 6 Livestream"></lite-youtube>
+Watch the full Voice chapter 6 livestream
+</p>
+
+2023's [Year of the Voice] built a solid foundation for letting users control Home Assistant by speaking in their own language.
+
+We continue with improvements to [Assist], including:
+
+- More customization options for [sentence triggers]
+- Better error messages and [debugging tools]
+- Additional [intents] for controlling valves, vacuums, and media players
+
+Oh, and "one more thing": **on-device, open source wake word detection in ESPHome!** 🥳🥳🥳
+
+Check out this video of the new [microWakeWord] system running on an [ESP32-S3-BOX-3] alongside one doing wake word detection inside Home Assistant:
+
+<p class='img'>
+<lite-youtube videoid="oSKBWtBJyDE" videotitle="On-device wake word is here! Demonstrating microWakeWord on the ESP32-S3-BOX-3 in Home Assistant."></lite-youtube>
+On-device vs. streaming wake word
+</p>
+
+<!--more-->
+
+## microWakeWord
+
+Thanks to the incredible [microWakeWord] created by [Kevin Ahrendt], ESPHome can now perform wake word detection on devices like the [ESP32-S3-BOX-3].
+You can [install it on your S3-BOX-3 today][s3-box-tutorial] to try it out.
+
+Back in [Chapter 4], we added wake word detection using [openWakeWord]. Unfortunately, openWakeWord was too large to run on low power devices like S3-BOX-3.
+So we chose to run wake word detection inside Home Assistant instead.
+
+<p><img src='/images/blog/2024-02-21-voice-chapter-6/challenge.png' class='no-shadow' /></p>
+
+Doing wake word detection in HA allows tiny devices like the [M5 ATOM Echo Development Kit][m5-tutorial] to simply stream audio and let all of the processing happen elsewhere. This is great, as it allows low-powered devices using a simple ESP32 chip to be transformed into a voice assistant even if they do not pack the necessary power to detect wake words.
+The downside is that adding more voice assistants requires more CPU usage in HA as well as more network traffic.
+
+Enter microWakeWord. After listening to an interview with Paulus Schoutsen (founder of Home Assistant) on the [Self Hosted](https://selfhosted.show/) podcast, Kevin Ahrendt created a model based on [Google's Inception neural network](https://towardsdatascience.com/a-simple-guide-to-the-versions-of-the-inception-network-7fc52b863202). As an existing contributor to [ESPHome], Kevin was able to get this new model running on the ESP32-S3 chip inside the S3-BOX-3! _(It also works on the, now discontinued, S3-BOX and S3-BOX-Lite)_
+
+Kevin has trained [three models](https://github.com/esphome/micro-wake-word-models/tree/main/models) for the launch of microWakeWord:
+
+* "okay nabu"
+* "hey jarvis"
+* "alexa"
+
+You can try these out yourself now by following the [ESP32-S3-BOX tutorial][s3-box-tutorial]. Changing the default "okay nabu" wake word will require adjusting your [ESPHome configuration](https://beta.esphome.io/components/micro_wake_word.html) and recompiling the firmware, which may take a long time and requires a machine with more than 2GB of RAM.
+
+We're grateful to Kevin for developing microWakeWord, and making it a part of the open home!
+
+## Sentence trigger responses
+
+Adding custom sentences to Assist is as easy as adding a [sentence trigger][sentence triggers] to an automation. This allows you to trigger any action in Home Assistant with whatever sentences you want.
+
+Now with the new [conversation response] action in HA 2024.2, you can also customize the response spoken or printed back to you. Using [templating](/docs/automation/templating/#sentence), your response can refer to the current state of your home.
+
+<p><img src='/images/blog/2024-02-21-voice-chapter-6/assist-custom-response-editor.png' class='no-shadow' /></p>
+
+You can also refer to [wildcards](/docs/automation/trigger/#sentence-wildcards) in your sentence trigger. For example, the sentence trigger:
+
+```
+play {album} by {artist}
+```
+
+could have the response:
+
+{% raw %}
+```
+Playing {{ trigger.slots.album }} by {{ trigger.slots.artist }}
+```
+{% endraw %}
+
+in addition to calling a media service.
+
+You can experiment now with sentence triggers, and custom conversation responses in our automation editor by clicking here:
+[![Open your Home Assistant instance and show your automations.](https://my.home-assistant.io/badges/automations.svg)](https://my.home-assistant.io/redirect/automations/)
+
+## Improved errors and debugging
+
+Assist users know the phrase "Sorry, I couldn't understand that" all too well. This generic error message was given for a variety of reasons, such as:
+
+* The sentence didn't match any known [intent](https://github.com/home-assistant/intents)
+* The device/area names didn't match
+* There weren't any devices of a specific type in an area (lights, windows, etc.)
+
+Starting in HA 2024.2, Assist provides different error messages for each of these cases.
+
+<img class="no-shadow" src='/images/blog/2024-02/assist-errors.png' alt='Screenshot showing the new errors Assist will return in case the intention is understood, but something else is missing.'>
+
+Now if you encounter errors, you will know where to start looking! The first thing to check is that your device is [exposed to Assist](/voice_control/voice_remote_expose_devices/). Some types of devices, such as lights, are exposed by default. Other, like locks, are not and must be manually exposed.
+
+Once your devices are exposed, make sure you've added an appropriate [alias](/voice_control/aliases) so Assist will know exactly how you'll be referring to them. Devices and areas can have multiple aliases, even in multiple languages, so everyone's preference can be accommodated.
+
+If you are still having problems, the [Assist debug tool][debugging tools] has also been improved. Using the tool, you see how Assist is interpreting a sentence, including any missing pieces.
+
+<p><img src='/images/blog/2024-02-21-voice-chapter-6/debug_tool.png' class='no-shadow' /></p>
+
+[![Open your Home Assistant instance and show your Assist developer tools.](https://my.home-assistant.io/badges/developer_assist.svg)](https://my.home-assistant.io/redirect/developer_assist/)
+
+Our community [language leaders](https://developers.home-assistant.io/docs/voice/language-leaders) are hard at work translating sentences for Assist. If you have suggestions for new sentences to be added, please create an issue on [the intents repository](https://github.com/home-assistant/intents) or drop us a line at voice@nabucasa.com
+
+
+## Thank you
+
+Thank you to the Home Assistant community for subscribing to [Home Assistant Cloud][nabucasa] to support voice and development of Home Assistant, ESPHome and other projects in general.
+
+Thanks to our language leaders for extending the sentence support to all the various languages.
+
+<p class='img'>
+<img src='/images/blog/2024-02-21-voice-chapter-6/ha-support.png' alt="Thank you for supporting the Home Assistant project">
+</p>
+
+[Year of the Voice]: /blog/2022/12/20/year-of-voice/
+[Assist]: /voice_control/
+[exposed]: /voice_control/voice_remote_expose_devices/
+[alias]: /voice_control/aliases
+[wyoming]: https://github.com/rhasspy/wyoming
+[openWakeWord]: https://github.com/dscripka/openWakeWord
+[Piper]: https://github.com/rhasspy/piper/
+[wyoming-satellite]: https://github.com/rhasspy/wyoming-satellite
+[s3-box-tutorial]: /voice_control/s3_box_voice_assistant/
+[ESP32-S3-BOX-3]: https://www.espressif.com/en/news/ESP32-S3-BOX-3
+[ESPHome]: https://esphome.io
+[nabucasa]: https://www.nabucasa.com
+[sentence triggers]: /docs/automation/trigger/#sentence-trigger
+[conversation response]: /docs/scripts/#respond-to-a-conversation
+[microWakeWord]: https://github.com/kahrendt/microWakeWord
+[Kevin Ahrendt]: https://www.kevinahrendt.com/
+[debugging tools]: /voice_control/troubleshooting/#test-a-sentence-per-language-without-voice-without-executing-commands
+[intents]: https://developers.home-assistant.io/docs/intent_builtin
+[Chapter 4]: /blog/2023/10/20/year-of-the-voice-chapter-4/
+[m5-tutorial]: /voice_control/thirteen-usd-voice-remote/

source/_posts/2024-02-22-what-about-grace-live-stream.markdown

@@ -0,0 +1,19 @@
+---
+layout: post
+title: "What about Grace? Tune in to our special livestream next week!"
+description: "Why is Grace important to us? Well, we have a habit of naming our projects after influential women in tech. And we have been working on a little something special and can’t wait to show you!"
+date: 2024-02-22 00:00:01
+date_formatted: "February 22, 2024"
+author: Madelena Mak
+comments: true
+categories: Announcements
+og_image: /images/blog/2024-02-grace-chapter-1/banner.png
+---
+
+Who is Grace? Grace Hopper was a computer scientist, mathematician, and US Navy admiral who had made significant contributions to the field of computer programming and technology, from her pioneering work on and contributions to the Harvard Mark I computer, COBOL, and UNIVAC I.
+
+<lite-youtube videoid="XyBy0ckkiDU" videotitle="What about Grace? - Chapter 1"></lite-youtube>
+
+Why is she important to us? Well, we have a habit of naming some of our projects after influential women in tech. And we have been working on a little something nice for the past year that we can’t wait to show you!
+
+For those who are interested in making your smart home easier to control and monitor for everyone in your home, tune in next week on the leap year day, February 29, 2024, at 20:00 GMT / 21:00 CET / 3:00 PM ET / 12:00 PM PT, for a [special livestream](https://www.youtube.com/live/XyBy0ckkiDU). We will walk you through the past, present, and future of this special project.

source/_posts/2024-02-26-home-assistant-os-12-support-for-raspberry-pi-5.markdown

@@ -0,0 +1,49 @@
+---
+layout: post
+title: "Raspberry Pi 5 support and more in Home Assistant OS release 12 & Supervisor update"
+description: "HAOS 12 adds support for Raspberry Pi 5 and ODROID-M1S boards, with the Linux kernel updated to 6.6. Additionally, backups have become faster, and add-ons can now signal when they should not be auto-updated."
+date: 2024-02-26 00:00:00
+date_formatted: "February 26, 2024"
+author: Stefan Agner
+comments: true
+categories: HAOS
+og_image: /images/blog/2024-02-haos12/haos12.png
+---
+
+**TL;DR:** Home Assistant OS 12 adds support for Raspberry Pi 5 and ODROID-M1S boards, with the Linux kernel updated to 6.6. Additionally, backups have become faster, and add-ons can now signal when they should not be auto-updated.
+
+<p><img src='/images/blog/2024-02-haos12/haos12.png' class='no-shadow' /></p>
+
+## Raspberry Pi 5
+
+With the release of Home Assistant OS 12, we officially announce Raspberry Pi 5 support! Many Home Assistant OS users have extensively tested the preview releases during the last few months, and after some initial hiccups with the Raspberry Pi 5-specific update mechanism, things are stable and solid today. As a third of all Home Assistant users currently use a Raspberry Pi board as their dedicated Home Assistant system, we are sure this support will make many users very happy!
+
+Compared to other Raspberry Pi boards, HAOS does not use U-Boot as an extra bootloader. Instead, the Raspberry Pi's built-in “tryboot” functionality is used to automatically fall back to a previous release in case of an update failure. This new update mechanism integration required us to have a longer testing phase.
+
+In our testing, the higher CPU clock of the Raspberry Pi 5 (up to 2.4GHz) makes Home Assistant feel noticeably snappier compared to previous Raspberry Pi boards. Additionally, a Raspberry Pi HAT that provides NVMe SSD support allows you to extend your Raspberry Pi with fast, reliable, and cost-effective storage. We do recommend using an SD card as the boot medium and using the [data disk feature](/common-tasks/os/#using-external-data-disk) to move most of the Home Assistant installation onto the NVMe. This is easy to set up and guarantees a reliable boot.
+
+## ODROID-M1S
+
+The Raspberry Pi 5 is not the only new board that is supported with this release. We are happy to announce that the family of supported ODROID devices from the Korean manufacturer Hardkernel has become bigger thanks to a community contribution from Tim Lunn (darkxst), who implemented board support for the ODROID-M1S. The ODROID-M1S is the newest single-board computer from Hardkernel, which is similar to the already supported ODROID-M1, which was added in Home Assistant OS 10. This new board offers a slimmer form factor, 4 or 8 GB of RAM on board, and an embedded 64 GB eMMC storage. Home Assistant OS can be booted either from an SD card or the system can be flashed to the eMMC card using the procedure described in the [documentation](https://github.com/home-assistant/operating-system/blob/dev/Documentation/boards/hardkernel/odroid-m1s.md). While the board also has an NVMe slot for a solid-state drive, it is not supported as a boot device. However, just like on the Raspberry Pi 5, it can still be used as the data disk.
+
+Just like its larger brother, the ODROID-M1S is powered by a quad-core ARM Cortex-A55, but while ODROID-M1 has (very slightly) beefier Rockchip RK3568 SoC, this board sports the RK3566. Some of our more curious readers may notice this is the same processor that is found on our Home Assistant Green! While there are some similarities between those two boards, Home Assistant Green can offer you a seamless out-of-box experience, allowing you to set up your smart home in a matter of minutes. But Home Assistant is also about the freedom of choice, so if you are looking for a more DIY approach, ODROID-M1S might be the right choice for you.
+
+## Linux 6.6
+
+Home Assistant OS 12 now comes with Linux kernel 6.6! This is good news for those who want to run their Home Assistant on newer hardware that lacked support in the previous 6.1 kernel. This version update also allows us to extend the list of supported Wi-Fi and Bluetooth cards, including ones you may find in new mini-PCs, a popular platform for Home Assistant OS. Those who run their installations on a Raspberry Pi (including the CM4 in Home Assistant Yellow) may notice their kernel version still starts with 6.1. This is because we are not using the upstream kernel but the downstream one maintained by the Raspberry Pi developers. But this kernel was also updated to the latest stable version, which we hope will resolve some sporadic bugs.
+
+Home Assistant OS sticks to the LTS (long-term support) kernels, which are usually released once per year - just like Buildroot, the base system we use for Home Assistant OS. This time, we are slightly ahead of schedule, because usually the kernel update is done alongside the bump of the Buildroot version. But don't worry, the Buildroot update is coming soon as well, and we expect to include its update in one of the next minor Home Assistant OS releases coming in the following weeks. This will conclude this year's spring cleaning of Home Assistant OS, and we will be ready to focus on new features and improvements again!
+
+## Faster Backups
+
+Home Assistant Supervisor and Core’s built-in backup functionality has become much faster. Thanks to contributions from bdraco, the backup feature gained faster compression speeds due to a library named isal, which provides optimized low-level functions for compression and decompression. More importantly, the backup feature now avoids intermediate copies, making it faster on slower storage media especially. If you used uncompressed backups before because the backup used to be too slow for you, now is the time to give compressed backups a try again! 😀
+
+<p><img src='/images/blog/2024-02-haos12/supervisor-backup-speed-improvements.png' class='no-shadow' alt='Comparison of the speed of a 100MB backup on a Home Assistant Yellow, between Supervisor 2023.12.1 and 2024.02.0.' /></p>
+
+Home Assistant OS users’ backup functionality is part of Supervisor. You’ll have received the improvements incrementally over the releases of the past few weeks. At the time of writing, your installation should run on Home Assistant Supervisor 2024.02.0 with all these improvements built in.
+
+## Safer add-on auto-updates
+
+Last, but not least, the Supervisor features an auto-update flag for add-ons. However, depending on the nature of an update to the add-on, the new version might need user intervention or have breaking changes. Add-on developers now have the option to prevent auto-updates to such versions. Users of the auto-update feature might see an update notification despite auto-updates being enabled. This means that the author of the add-on decided that this particular update should not be auto-updated and instead be manually approved by the user.
+
+Note: We generally don’t recommend auto-updates for add-ons, as even safe updates might interfere with regular operation. For example, during the automatic update of an add-on like Z-Wave JS, your Z-Wave devices would unexpectedly become unavailable for a short time. The better approach for such add-ons is to plan some time to maintain your Home Assistant system every once in a while and update your add-ons in a batch.

source/changelogs/core-2024.2.markdown

@@ -1482,6 +1482,87 @@ For a summary in a more readable format:
 [@wilburCforce]: https://github.com/wilburCforce
 [@zxdavb]: https://github.com/zxdavb
 
+## Release 2024.2.3 - February 22
+
+- Fix reauth in Overkiz for config entries created prior to 2022.12 ([@iMicknl] - [#106251])
+- Handle deep standby and poweroffs of enigma2 devices gracefully ([@autinerd] - [#107462])
+- Add wake up timeout to Teslemetry ([@Bre77] - [#109037])
+- Fix set_temperature in Tessie climate platform ([@Bre77] - [#110445])
+- Fix uuid issue in Lutron ([@wilburCforce] - [#110524])
+- Update rokuecp to 0.19.1 ([@ctalkington] - [#110670])
+- Fix scene activation with climate entities with `None` attribute values ([@mib1185] - [#110684])
+- Remove matplotlib pinning due to Python 3.12 incompatibility ([@sbyx] - [#110706])
+- Bump roombapy to 1.6.12 ([@mib1185] - [#110762])
+- Ensure Tile timestamps are reported as UTC ([@bachya] - [#110773])
+- Detect reached API rate limit in Tankerkoenig ([@mib1185] - [#110432])
+- Bump aiotankerkoenig to 0.4.1 ([@jpbede] - [#110840])
+- Update govee-local-api library to 1.4.4 ([@Galorhallen] - [#110854])
+- Allow loading of more then 1 defined Apprise URL ([@caronc] - [#110868])
+- Reolink continue setup when internet blocked ([@starkillerOG] - [#110888])
+- Bump deluge-client to 1.10.0 ([@tkdrob] - [#110663])
+- Bump deluge-client to 1.10.2 ([@dsander] - [#110905])
+- Bump reolink-aio to 0.8.8 ([@starkillerOG] - [#110959])
+- Reset error state when Ecovacs bot is operational again ([@mib1185] - [#110962])
+- Bump motionblinds to 0.6.21 ([@starkillerOG] - [#110970])
+- Bump holidays to 0.43 ([@gjohansson-ST] - [#111039])
+- Fixes UniFi Protect light state check ([@AngellusMortis] - [#111058])
+- Bump pywebpush to 1.14.1 ([@thecode] - [#111082])
+- Bump aioairzone to v0.7.4 ([@Noltari] - [#111105])
+- Bump deebot-client to 5.2.2 ([@edenhaus] - [#111112])
+- Ignore cloudhook already removed in mobile app ([@joostlek] - [#111122])
+
+[#106251]: https://github.com/home-assistant/core/pull/106251
+[#107462]: https://github.com/home-assistant/core/pull/107462
+[#109037]: https://github.com/home-assistant/core/pull/109037
+[#109883]: https://github.com/home-assistant/core/pull/109883
+[#110078]: https://github.com/home-assistant/core/pull/110078
+[#110432]: https://github.com/home-assistant/core/pull/110432
+[#110445]: https://github.com/home-assistant/core/pull/110445
+[#110524]: https://github.com/home-assistant/core/pull/110524
+[#110663]: https://github.com/home-assistant/core/pull/110663
+[#110670]: https://github.com/home-assistant/core/pull/110670
+[#110684]: https://github.com/home-assistant/core/pull/110684
+[#110706]: https://github.com/home-assistant/core/pull/110706
+[#110720]: https://github.com/home-assistant/core/pull/110720
+[#110762]: https://github.com/home-assistant/core/pull/110762
+[#110773]: https://github.com/home-assistant/core/pull/110773
+[#110840]: https://github.com/home-assistant/core/pull/110840
+[#110854]: https://github.com/home-assistant/core/pull/110854
+[#110868]: https://github.com/home-assistant/core/pull/110868
+[#110888]: https://github.com/home-assistant/core/pull/110888
+[#110905]: https://github.com/home-assistant/core/pull/110905
+[#110959]: https://github.com/home-assistant/core/pull/110959
+[#110962]: https://github.com/home-assistant/core/pull/110962
+[#110970]: https://github.com/home-assistant/core/pull/110970
+[#111035]: https://github.com/home-assistant/core/pull/111035
+[#111039]: https://github.com/home-assistant/core/pull/111039
+[#111058]: https://github.com/home-assistant/core/pull/111058
+[#111082]: https://github.com/home-assistant/core/pull/111082
+[#111105]: https://github.com/home-assistant/core/pull/111105
+[#111112]: https://github.com/home-assistant/core/pull/111112
+[#111122]: https://github.com/home-assistant/core/pull/111122
+[@AngellusMortis]: https://github.com/AngellusMortis
+[@Bre77]: https://github.com/Bre77
+[@Galorhallen]: https://github.com/Galorhallen
+[@Noltari]: https://github.com/Noltari
+[@autinerd]: https://github.com/autinerd
+[@bachya]: https://github.com/bachya
+[@caronc]: https://github.com/caronc
+[@ctalkington]: https://github.com/ctalkington
+[@dsander]: https://github.com/dsander
+[@edenhaus]: https://github.com/edenhaus
+[@frenck]: https://github.com/frenck
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@iMicknl]: https://github.com/iMicknl
+[@joostlek]: https://github.com/joostlek
+[@jpbede]: https://github.com/jpbede
+[@mib1185]: https://github.com/mib1185
+[@sbyx]: https://github.com/sbyx
+[@starkillerOG]: https://github.com/starkillerOG
+[@thecode]: https://github.com/thecode
+[@tkdrob]: https://github.com/tkdrob
+[@wilburCforce]: https://github.com/wilburCforce
+
 [#100684]: https://github.com/home-assistant/core/pull/100684
 [#100806]: https://github.com/home-assistant/core/pull/100806
 [#101497]: https://github.com/home-assistant/core/pull/101497

source/getting-started/index.markdown

@@ -1,5 +1,5 @@
 ---
-title: "Getting Started"
+title: "Getting started"
 description: "Getting started with Home Assistant"
 body_id: getting_started
 show_title: true

source/getting-started/onboarding_dashboard.markdown

@@ -5,7 +5,7 @@ description: "Instructions on editing the dashboard for the first time"
 
 ## First contact with the Overview dashboard
 
-The **Overview** dashboard is the first page you see after the [onboarding process](/getting-started/onboarding). Dashboards are customizable pages to display information in Home Assistant. 
+The **Overview** [dashboard](/dashboards/) is the first page you see after the [onboarding process](/getting-started/onboarding). Dashboards are customizable pages to display information in Home Assistant.
 
 By default, there are two dashboards: **Overview** and **Energy**. The image below shows a customized example of the **Overview** dashboard. If you just onboarded, your dashboard will be nearly empty.
 
@@ -32,7 +32,7 @@ The procedure below is optional. The idea is to learn some basics on changing th
     - Once you are done, select **Update**.
    ![Weather details](/images/getting-started/onboarding_card_settings_01.png)
 
-4. To change the type of dashboard card, in the top right corner, select the three-dots, then, in the **Edit dashboard** dialog, select the three dots again and select **Take control**.
+4. To change the type of dashboard card, in the top right corner, select the pencil icon, then, in the **Edit dashboard** dialog, select the three dots and select **Take control**.
    ![Take control of the dashboard](/images/getting-started/dashboard-take-control.png)
    - Read and accept this before continuing.
    - On the dashboard, select the weather card, select the three dots, then **Device info**.
@@ -46,7 +46,7 @@ The procedure below is optional. The idea is to learn some basics on changing th
    - You now see the forecast card on the dashboard.
 
 7. Now let's delete the other weather card.
-   - In the top right corner, select the three-dot menu, then select **Edit dashboard**.
+   - In the top right corner, select the pencil.
    ![Dashboard - edit the dashboard](/images/getting-started/onboarding_edit_dashboard_01.png)
    - On the card, select the three-dot menu and select **Delete**.
    ![Dashboard - delete card](/images/getting-started/onboarding_dashboard_delete_card.png)
@@ -56,4 +56,11 @@ The procedure below is optional. The idea is to learn some basics on changing th
    - When you are done, in the top right corner, select **Done**.
 9. Congratulations! You have completed your first dashboard customization.
 
-{% include getting-started/next_step.html step="Integrations" link="/getting-started/integration/" %}
+To continue with this tutorial, select the button below to learn about {% term integrations %}.
+
+{% include getting-started/next_step.html step="Integrations" link="/getting-started/integration/" %}
+
+## Related topics
+
+- [Dashboards](/dashboards/)
+- [Views](/dashboards/views/)

source/installation/raspberrypi.markdown

@@ -4,7 +4,7 @@ description: "Install Home Assistant on a Raspberry Pi"
 installation_type: raspberrypi
 ---
 {% comment %}
-Included sections for this page is located under source/_includes/installation
+Included section for this page is located under source/_includes/installation
 {% endcomment %}
 
 {% assign board = "Raspberry Pi" %}
@@ -23,6 +23,7 @@ Before installing Home Assistant, you might want to <a href="/installation#compa
 
 We will need a few things to get started with installing Home Assistant. Links below lead to Amazon US. If you’re not in the US, you should be able to find these items in web stores in your country.
 
+- [Raspberry Pi 5](https://amzn.to/3UH6TcD)
 - [Raspberry Pi 4](https://amzn.to/2S0Gcl1) (Raspberry Pi 3 Model B is ok too, but the Model A does not have enough RAM). Raspberry Pi are currently hard to come by, use [RPilocator](https://rpilocator.com/?cat=PI4) to find official distributors with stock.
 - [Power Supply for Raspberry Pi 4](https://amzn.to/2ReZ2Vq) or [Power Supply for Raspberry Pi 3](https://amzn.to/2R8yG7h)
 - [Micro SD Card](https://amzn.to/2X0Z2di). Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html) as they handle small I/O much more consistently than cards not optimized to host applications. A 32&nbsp;GB or bigger card is recommended.
@@ -37,15 +38,15 @@ If Raspberry Pi Imager is not supported by your platform, you can use [Balena Et
 
 ### Write the image to your SD card
 
-1. Download and install the Raspberry Pi Imager on your computer as described under [https://www.raspberrypi.com/software/](https://www.raspberrypi.com/software/). 
+1. Download and install the Raspberry Pi Imager on your computer as described under [https://www.raspberrypi.com/software/](https://www.raspberrypi.com/software/).
    ![Install Raspberry Pi Imager](/images/installation/rpi_imager.png)
 2. Open the Raspberry Pi Imager and select your Raspberry Pi device.
     ![Open Raspberry Pi Imager](/images/installation/rpi_imager_start.png)
 3. Choose the operating system:
    1. Select **Choose OS**.
    2. Select **Other specific-purpose OS** > **Home assistants and home automation** > **Home Assistant**.
-   3. Choose the Home Assistant OS that matches your hardware (RPi&nbsp;3 or RPi&nbsp;4).
-    ![Choose the operating system](/images/installation/rpi-ha.gif)
+   3. Choose the Home Assistant OS that matches your hardware (RPi&nbsp;3, RPi&nbsp;4, or RPi&nbsp;5).
+    ![Choose the operating system](/images/installation/rpi-ha.webp)
 4. Choose the storage:
    1. Insert the SD card into the computer. Note: the contents of the card will be overwritten.
    2. Select your SD card.
@@ -72,8 +73,8 @@ Within a few minutes after connecting the Raspberry Pi, you will be able to reac
     If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at <a href="http://homeassistant:8123" target="_blank">homeassistant:8123</a> or `http://X.X.X.X:8123` (replace X.X.X.X with your Raspberry Pi’s IP address).
     </div>
 
-- The time it takes for this page to become available depends on your hardware. On a Raspberry Pi 4, this page should be available within a minute.
-  - If it does not show up after 5 minutes on a Pi 4, maybe the image was not written properly.
+- The time it takes for this page to become available depends on your hardware. On a Raspberry Pi 4 or 5, this page should be available within a minute.
+  - If it does not show up after 5 minutes on a Pi 4 or 5, maybe the image was not written properly.
     - Try to flash the SD card again, possibly even try a different SD card.
   - If this did not help, view the console output on the Raspberry Pi.
     - To do this, connect a monitor via HDMI.

source/voice_control/custom_sentences.markdown

@@ -14,6 +14,7 @@ If you have not set up voice control yet, set up the hardware first. For instruc
 
 - [World's most private voice assistant](/voice_control/worlds-most-private-voice-assistant/): Using a classic landline phone
 - [$13 voice assistant for Home Assistant](/voice_control/thirteen-usd-voice-remote/): Using a button with speaker and mic
+- [S3-BOX-3 voice assistant](/voice_control/s3_box_voice_assistant/): Using a small device with speaker, mic, and display
 - [Assist for Apple](/voice_control/apple/): Using your iPhone, Mac, or Apple watch
 - [Assist for Android](/voice_control/android/): Using your Android phone, tablet, or a Wear OS watch
 
@@ -29,7 +30,27 @@ If you have not set up voice control yet, set up the hardware first. For instruc
    - Then, select **Set conversation response**.
      ![Set conversation response](/images/assist/assist_set-conversation-response.png)
 5. In the text field, enter the response you want to hear from Assist and select **Save**.
-   ![Enter the response text](/images/assist/assist_set-conversation-response_02.png)
+
+   ![Enter the response text](/images/assist/assist_set-conversation-response_02.png)  
+
+   - You can also use [wildcards](/docs/automation/trigger/#sentence-wildcards). For example, the trigger:
+
+      ```yaml
+      play {album} by {artist}
+      ```
+
+      could have the response:
+
+      {% raw %}
+
+      ```yaml
+      Playing {{ trigger.slots.album }} by {{ trigger.slots.artist }}
+      ```
+
+      {% endraw %}
+
+   - For more details, refer to [conversation response script action](/docs/scripts/#respond-to-a-conversation).
+ 
 6. To test the automation, go to **Overview** and in the top right corner, open Assist.
    - Enter one of the sentences.
 7. If it did not work out, checkout the [troubleshooting](/voice_control/troubleshooting/) section.
@@ -144,11 +165,17 @@ responses:
 
 {% endraw %}
 
-
 ## Related topics
 
 - [View existing intents](https://developers.home-assistant.io/docs/intent_builtin/)
 - [Create aliases](/voice_control/aliases/)
+- [Conversation response script action](/docs/scripts/#respond-to-a-conversation)
+- [Sentence triggers](/docs/automation/trigger/#sentence-trigger)
+- [Sentence wildcards](/docs/automation/trigger/#sentence-wildcards)
+
+### Related devices and installation tutorials
+
 - [$13 voice assistant for Home Assistant](/voice_control/thirteen-usd-voice-remote/)
+- [S3-BOX-3 voice assistant](/voice_control/s3_box_voice_assistant/)
 - [Assist for Apple](/voice_control/apple/)
 - [Assist for Android](/voice_control/android/)

source/voice_control/s3-box-customize.markdown

@@ -180,20 +180,21 @@ If your images have transparency, you can define the background color in the con
 
 ## Customizing on-device wake words (microWakeWord)
 
-If you are running the latest version of ESPHome on your device, you can already process your wake word on your S3-BOX (instead of running it on the Home Assistant server). This is done using the [microWakeWord](https://github.com/kahrendt/microWakeWord) model. By default, the wake word then is *Okay Nabu*. If you want to change the on-device wake word to *Hey Jarvis* or *Alexa*, follow these steps.
+You can change the on-device wake word (microWakeWord) that is used on your S3-BOX-3.
 
 ### Prerequisites
 
 - Home Assistant 2024.2, installed with the Home Assistant Operating System. If you do not have Home Assistant installed yet, refer to the [installation page](/installation/) for instructions.
 - Successfully [installed ESPHome on the S3-BOX-3](/voice_control/s3_box_voice_assistant/)
 - ESPHome 2024.2 or later
-- Home Assistant server with at least 2 GB of RAM
-  - The firmware needs to be compiled on the server before it is installed on the S3-BOX-*.
+- Home Assistant server with at least 2 GB of RAM free
+  - The firmware needs to be compiled on the server before it is installed on the S3-BOX-3.
   - Compiling requires a bit of RAM.
+- [On-device wake word installed](#installing-on-device-wake-words-microwakeword) on your S3-BOX-3.
 
-(It also works on the, now discontinued, S3-BOX and S3-BOX-Lite)_
+*(It also works on the (now discontinued) S3-BOX and S3-BOX-Lite)*
 
-### To customize the S3-BOX-* with on-device wake words
+### To customize the S3-BOX-3 with on-device wake words
 
 1. If you haven't done so already, [adopt the device in the ESPHome add-on](#adopting-the-device-in-the-esphome-add-on).
 2. In Home Assistant, go to [**Settings** > **Add-ons** > **ESPHome**](https://my.home-assistant.io/redirect/supervisor_addon/?addon=5c53de3b_esphome), and **Open Web UI**.
@@ -207,13 +208,19 @@ If you are running the latest version of ESPHome on your device, you can already
      ```yaml
      substitutions:
        ...
-       micro_wake_word_model: okay_nabu
+       micro_wake_word_model: hey_jarvis
      ```
 
 5. Save the changes and in the top right corner, select **Install**.
-   - Depending on your environment, the installation process can take a while. (On Home Assistant Green, for example, it takes about 45 minutes.)
-   - On Home Assistant Green, for example, it takes about 45 minutes.86. Once the installation is complete, you can see the new image on the S3-BOX-3.
-6.  - Now, speak a command to test the new setting. For example, *OK Nabu, turn on the light*.
+   - Depending on your environment, the installation process can take a while.
+   - On Home Assistant Green, for example, it takes about 45 minutes.
+6. Select the **ESPHome** integration. Under **Devices**, you should see the **ESP32-S3-BOX** listed.
+    - On the ESP32-S3-BOX-3 entry, select **Device** to open the device page.
+    - Under **Wake word engine location**, select **On device**.
+
+      ![ESP32-S3-BOX-3 on device wake word processing](/images/assist/wake_word_engine_location.png)
+
+7. Now, speak a command to test the new setting. For example, *Hey Jarvis, turn on the light*.
 
 ## Related topics
 

source/voice_control/s3_box_voice_assistant.markdown

@@ -31,12 +31,12 @@ Before you can use this device with Home Assistant, you need to install a bit of
    - If your browser does not support web serial, you will see a warning message indicating this instead of a button.
 
       <script type="module" src="https://unpkg.com/esp-web-tools@10/dist/web/install-button.js?module"></script>
-      <esp-web-install-button manifest="https://firmware.esphome.io/voice-assistant/esp32-s3-box-3/manifest.json"></esp-web-install-button>
+      <esp-web-install-button manifest="https://firmware.esphome.io/wake-word-voice-assistant/esp32-s3-box-3/manifest.json"></esp-web-install-button>
 
 
    - If you have an ESP32-S3-BOX or ESP32-S3-BOX-Lite, open the [ESPHome projects](https://esphome.io/projects/index.html?type=voice) page, select your variant and follow the installation instructions.
    - **For advanced users**: The configuration files are available on GitHub:
-     - [ESP32-S3-BOX-3](https://github.com/esphome/firmware/blob/main/voice-assistant/esp32-s3-box-3.yaml)
+     - [ESP32-S3-BOX-3](https://github.com/esphome/firmware/blob/main/wake-word-voice-assistant/esp32-s3-box-3.yaml)
 
 {% include voice_assistant/install_esp_firmware.md %}