Merge branch 'current' into next

CODEOWNERS

@@ -354,7 +354,7 @@ source/_integrations/hive.markdown @Rendili @KJonline
 source/_integrations/hko.markdown @MisterCommand
 source/_integrations/hlk_sw16.markdown @jameshilliard
 source/_integrations/holiday.markdown @jrieger @gjohansson-ST
-source/_integrations/home_connect.markdown @DavidMStraub
+source/_integrations/home_connect.markdown @DavidMStraub @Diegorro98
 source/_integrations/home_plus_control.markdown @cgtobi
 source/_integrations/homeassistant.markdown @home-assistant/core
 source/_integrations/homeassistant_alerts.markdown @home-assistant/core
@@ -707,7 +707,7 @@ source/_integrations/rmvtransport.markdown @cgtobi
 source/_integrations/roborock.markdown @Lash-L
 source/_integrations/roku.markdown @ctalkington
 source/_integrations/romy.markdown @xeniter
-source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn @Xitee1 @Orhideous
+source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn @Orhideous
 source/_integrations/roon.markdown @pavoni
 source/_integrations/rpi_power.markdown @shenxn @swetoast
 source/_integrations/rss_feed_template.markdown @home-assistant/core
@@ -796,11 +796,10 @@ source/_integrations/sonos.markdown @jjlawren @peterager
 source/_integrations/soundtouch.markdown @kroimon
 source/_integrations/spaceapi.markdown @fabaff
 source/_integrations/speedtestdotnet.markdown @rohankapoorcom @engrbm87
-source/_integrations/spider.markdown @peternijssen
 source/_integrations/splunk.markdown @Bre77
 source/_integrations/spotify.markdown @frenck @joostlek
 source/_integrations/sql.markdown @gjohansson-ST @dougiteixeira
-source/_integrations/squeezebox.markdown @rajlaud
+source/_integrations/squeezebox.markdown @rajlaud @pssc @peteS-UK
 source/_integrations/srp_energy.markdown @briglx
 source/_integrations/starline.markdown @anonym-tsk
 source/_integrations/starlink.markdown @boswelja
@@ -813,7 +812,7 @@ source/_integrations/stookwijzer.markdown @fwestenberg
 source/_integrations/stream.markdown @hunterjm @uvjustin @allenporter
 source/_integrations/stt.markdown @home-assistant/core
 source/_integrations/subaru.markdown @G-Two
-source/_integrations/suez_water.markdown @ooii
+source/_integrations/suez_water.markdown @ooii @jb101010-2
 source/_integrations/sun.markdown @Swamp-Ig
 source/_integrations/sunweg.markdown @rokam
 source/_integrations/supla.markdown @mwegrzynek

Gemfile

@@ -10,11 +10,10 @@ group :development do
   gem 'stringex', '2.8.6'
   # > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
   gem 'sassc', '2.1.0'
-  # 1.80.5 breaks the build
+  gem 'sass-embedded', '1.80.6'
-  gem 'sass-embedded', '1.80.4'
+  gem 'rubocop', '1.68.0'
-  gem 'rubocop', '1.67.0'
+  gem 'ruby-lsp', '0.21.3'
-  gem 'ruby-lsp', '0.20.1'
+  gem 'rackup', '2.2.0'
-  gem 'rackup', '2.1.0'
 end
 
 group :jekyll_plugins do

Gemfile.lock

@@ -66,7 +66,7 @@ GEM
       nokogiri (~> 1.12)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    json (2.7.4)
+    json (2.8.1)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -86,7 +86,7 @@ GEM
     nokogiri (1.16.7-x86_64-linux)
       racc (~> 1.4)
     parallel (1.26.3)
-    parser (3.3.5.0)
+    parser (3.3.6.0)
       ast (~> 2.4.1)
       racc
     pathutil (0.16.2)
@@ -100,9 +100,8 @@ GEM
       rack (>= 3.0.0, < 4)
     rack-session (2.0.0)
       rack (>= 3.0.0)
-    rackup (2.1.0)
+    rackup (2.2.0)
       rack (>= 3)
-      webrick (~> 1.8)
     rainbow (3.1.1)
     rake (13.2.1)
     rb-fsevent (0.11.2)
@@ -113,7 +112,7 @@ GEM
     regexp_parser (2.9.2)
     rexml (3.3.9)
     rouge (4.4.0)
-    rubocop (1.67.0)
+    rubocop (1.68.0)
       json (~> 2.3)
       language_server-protocol (>= 3.17.0)
       parallel (~> 1.10)
@@ -123,9 +122,9 @@ GEM
       rubocop-ast (>= 1.32.2, < 2.0)
       ruby-progressbar (~> 1.7)
       unicode-display_width (>= 2.4.0, < 3.0)
-    rubocop-ast (1.32.3)
+    rubocop-ast (1.34.0)
       parser (>= 3.3.1.0)
-    ruby-lsp (0.20.1)
+    ruby-lsp (0.21.3)
       language_server-protocol (~> 3.17.0)
       prism (>= 1.2, < 2.0)
       rbs (>= 3, < 4)
@@ -134,9 +133,9 @@ GEM
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
     sass (3.4.25)
-    sass-embedded (1.80.4-arm64-darwin)
+    sass-embedded (1.80.6-arm64-darwin)
       google-protobuf (~> 4.28)
-    sass-embedded (1.80.4-x86_64-linux-gnu)
+    sass-embedded (1.80.6-x86_64-linux-gnu)
       google-protobuf (~> 4.28)
     sass-globbing (1.1.5)
       sass (>= 3.1)
@@ -150,7 +149,7 @@ GEM
       rack-protection (= 4.0.0)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11620)
+    sorbet-runtime (0.5.11641)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
@@ -160,7 +159,7 @@ GEM
     tzinfo-data (1.2024.2)
       tzinfo (>= 1.0.0)
     unicode-display_width (2.6.0)
-    webrick (1.8.2)
+    webrick (1.9.0)
 
 PLATFORMS
   arm64-darwin-23
@@ -174,11 +173,11 @@ DEPENDENCIES
   jekyll-sitemap (= 1.4.0)
   jekyll-toc (= 0.19.0)
   nokogiri (= 1.16.7)
-  rackup (= 2.1.0)
+  rackup (= 2.2.0)
   rake (= 13.2.1)
-  rubocop (= 1.67.0)
+  rubocop (= 1.68.0)
-  ruby-lsp (= 0.20.1)
+  ruby-lsp (= 0.21.3)
-  sass-embedded (= 1.80.4)
+  sass-embedded (= 1.80.6)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)
   sinatra (= 4.0.0)

_config.yml

@@ -107,9 +107,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2024
-current_minor_version: 10
+current_minor_version: 11
-current_patch_version: 4
+current_patch_version: 0
-date_released: 2024-10-25
+date_released: 2024-11-06
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

sass/homeassistant/_overrides.scss

@@ -1393,12 +1393,10 @@ h1, h2, h3, h4, h5, h6 {
   word-wrap: break-word;
 }
 
-:target {
+:target, .title-link {
-  display: block;
+  display: inline-block;
   position: relative;
-  top: -100px;
+  scroll-margin-top: 140px;
-  visibility: hidden;
-  scroll-margin-top: 80px;
 }
 
 .site-header {

sass/homeassistant/base/_global.scss

@@ -64,6 +64,11 @@ table {
   }
 }
 
+.text-input,
+textarea {
+  cursor: text;
+}
+
 .gist {
   font-size: 0.75em;
 }

source/_dashboards/glance.markdown

@@ -115,15 +115,6 @@ double_tap_action:
   type: map
 {% endconfiguration %}
 
-### Options for exemptions
-
-{% configuration badges %}
-user:
-  required: true
-  description: User ID that can see the view tab.
-  type: string
-{% endconfiguration %}
-
 ### Examples
 
 Basic example:

source/_dashboards/picture-elements.markdown

@@ -407,15 +407,6 @@ style:
   default: "position: absolute, transform: translate(-50%, -50%)"
 {% endconfiguration %}
 
-## Options for exemptions
-
-{% configuration badges %}
-user:
-  required: true
-  description: User ID that can see the view tab.
-  type: string
-{% endconfiguration %}
-
 ## Notes on element attributes
 
 ### How to use the style object

source/_dashboards/picture-glance.markdown

@@ -143,15 +143,6 @@ double_tap_action:
   type: map
 {% endconfiguration %}
 
-### Options for exemptions
-
-{% configuration badges %}
-user:
-  required: true
-  description: User ID that can see the view tab.
-  type: string
-{% endconfiguration %}
-
 ### How to use state_filter
 
 Specify different [CSS filters](https://developer.mozilla.org/en-US/docs/Web/CSS/filter)

source/_dashboards/todo-list.markdown

@@ -74,6 +74,6 @@ Title example:
 
 ```yaml
 type: todo-list
-entity: todo-list
+entity: todo.todo_list
-title: todo list
+title: Todo List
 ```

source/_data/glossary.yml

@@ -205,6 +205,11 @@
   definition: >-
     Device trackers are used to track the presence, or location, of a device.
   link: /integrations/device_tracker
+- term: Diagnostics
+  definition: >-
+    The diagnostics integration provides a way to download diagnostic data from a device or integration for sharing in issue reports. Sharing diagnostics data when reporting an issue allows developers to diagnose and
+    fix your reported problem quicker.
+  link: /integrations/diagnostics
 - term: Discovery
   definition: >
     Discovery is the automatic setup of zeroconf/mDNS and uPnP devices after
@@ -361,6 +366,12 @@
   link: https://en.wikipedia.org/wiki/Host_(network)
   aliases:
     - hosts
+- term: Image
+  definition: >-
+    The Image integration allows other integrations to display a static image.
+  link: /integrations/image
+  aliases:
+    - images
 - term: Integration
   definition: >-
     Integrations connect and integrate Home Assistant with devices, services,
@@ -548,6 +559,8 @@
     Switches are things that have two states you can select between, such as
     turning on or off a socket.
   link: /integrations/switch/
+  aliases:
+    - switches
 - term: Template
   definition: >-
     A template is an automation definition that can include variables for the
@@ -599,6 +612,18 @@
     TTS (text-to-speech) allows Home Assistant to talk to you.
   link: /integrations/tts/
 
+- term: Update
+  definition: >-
+    An update entity is an entity that indicates if an update is available for a
+    device or service. This can be any update, be it a firmware update
+    for a device like a light bulb or router, or a software update for an add-on or a container.
+  excerpt: >
+    An update entity is an entity that indicates if an update is available for a
+    device or service.
+  link: /integrations/update
+  aliases:
+    - updates
+
 - term: Valve
   definition: >-
     Valves are devices to control the flow of liquids and gases. All valves in

source/_docs/authentication.markdown

@@ -7,7 +7,7 @@ The authentication system secures access to Home Assistant.
 
 ## Login screen
 
-You are greeted with a log in screen, asking you for user name and password.
+You are greeted with a log in screen, asking you for username and password.
 
 <img src='/images/docs/authentication/login-outside-local-network.png' alt='Screenshot of the login screen, when logging in from within the local network' style='border: 0;box-shadow: none;'>
 
@@ -55,9 +55,9 @@ As an extra level of security, you can turn on [multi-factor authentication](/do
 
 If you have administrator rights, you can [add a person to Home Assistant](/integrations/person/#adding-a-person-to-home-assistant) and create them a user account.
 
-## Changing display or user name
+## Changing display or username
 
-To learn how to change a display or user name, refer to [setting up basic information](/docs/configuration/basic/).
+To learn how to change a display or username, refer to [setting up basic information](/docs/configuration/basic/).
 
 ## Other authentication techniques
 

source/_docs/authentication/providers.markdown

@@ -123,11 +123,16 @@ homeassistant:
           - group: system-users
 ```
 
-First note, for `trusted_users` configuration you need to use `user id`, which you can find through {% my users title="Settings -> People" %} -> View User Detail. The `trusted_users` configuration will not validate the existence of the user, so please make sure you have put in the correct user id by yourself.
+First note, for `trusted_users` configuration you need to use `user id`.
 
-Second note, a trusted user with an IPv6 address must put the IPv6 address in quotes as shown.
+1. To find the user ID, in your browser, make sure the URL of your Home Assistant ends in `config/users/`.
+   - For example: `homeassistant:8123/config/users`.
+2. Select the user from the list, and copy the ID.
+   - For example: `acbbff56461748718f3650fb914b88c9`.
+3. The `trusted_users` configuration will not validate the existence of the user, so please make sure you have put in the correct user id.
+4. A trusted user with an IPv6 address must put the IPv6 address in quotes as shown.
 
-In above example, if user try to access Home Assistant from 192.168.0.1, they will have only one user available to choose. They will have two users available if access from 192.168.0.38 (from 192.168.0.0/24 network). If they access from 192.168.10.0/24 network, they can choose from all available users (non-system and active users).
+In the above example, if user try to access Home Assistant from 192.168.0.1, they will have only one user available to choose. They will have two users available if access from 192.168.0.38 (from 192.168.0.0/24 network). If they access from 192.168.10.0/24 network, they can choose from all available users (non-system and active users).
 
 Specially, you can use `group: GROUP_ID` to assign all users in certain `user group` to be available to choose. Group and users can be mix and match.
 

source/_docs/automation/templating.markdown

@@ -102,6 +102,7 @@ These are the properties available for a [Sentence trigger](/docs/automation/tri
 | `trigger.sentence` | Text of the sentence that was matched
 | `trigger.slots`    | Object with matched slot values
 | `trigger.details` | Object with matched slot details by name, such as [wildcards](/docs/automation/trigger/#sentence-wildcards). Each detail contains: <ul><li>`name` - name of the slot</li><li>`text` - matched text</li><li>`value` - output value (see [lists](https://developers.home-assistant.io/docs/voice/intent-recognition/template-sentence-syntax/#lists))</li></ul>
+| `trigger.device_id` | The device ID that captured the command, if any.
 
 ### State
 

source/_docs/configuration/basic.markdown

@@ -39,7 +39,7 @@ To change the general settings that were defined during onboarding, follow these
 
 ## Changing a person's display name
 
-The display name is the name that is shown in Home Assistant. It can differ from the user name, which is the name used to log in.
+The display name is the name that is shown in Home Assistant. It can differ from the username, which is the name used to log in.
 
 ### Prerequisites
 
@@ -50,18 +50,19 @@ The display name is the name that is shown in Home Assistant. It can differ from
 1. To edit the display name of a person using Home Assistant, go to {% my people title="**Settings** > **People**" %} and select the person for which you want to change the display name.
 2. Change the display name and select **Update** to save the change.
 
-## Changing a user name
+## Changing a username
 
-The user name is the name that is used to log in. It can differ from the display name.
+The username is the name that is used to log in. It can differ from the display name.
 
 ### Prerequisites
 
-- You need owner rights to change a user name.
+- You need owner rights to change a username.
 
 ### To change a username
 
 1. To edit the username of a person using Home Assistant, go to {% my people title="**Settings** > **People**" %} and select the person for which you want to change the display name.
 2. Change the username and select **Update** to save the change.
+   - It must be lowercase and contain no spaces.
    - The log in is case-sensitive.
 
 ## Changing authentication settings

source/_includes/asides/docs_sitemap.html

@@ -126,7 +126,7 @@
         <li>{% active_link /voice_control/voice_remote_expose_devices/ Exposing devices to voice assistant %}</li>
         <li>{% active_link /voice_control/install_wake_word_add_on/ Enabling a wake word %}</li>
         <li>{% active_link /voice_control/about_wake_word/ About wake words %}</li>
-        <li>{% active_link /voice_control/builtin_sentences/ Built-in sentences %}</li>
+        <li>{% active_link /voice_control/builtin_sentences/ Sentences starter kit %}</li>
         <li>{% active_link /voice_control/custom_sentences/ Custom sentences %}</li>
         <li>{% active_link /voice_control/aliases/ Using aliases %}</li>
         <li>{% active_link /voice_control/using_tts_in_automation/ Using Piper TTS in automations %}</li>

source/_includes/common-tasks/network_storage.md

@@ -1,6 +1,6 @@
 ## Network storage
 
-You can configure both Network File Share (NFS) and Windows samba (CIFS) targets to be used within Home Assistant and add-ons.
+You can configure both Network File System (NFS) and Samba/Windows (CIFS) targets to be used within Home Assistant and add-ons.
 To list all your currently connected network storages, go to **{% my storage title="Settings > System > Storage" %}** in the UI.
 
 {% if page.installation == "os" %}

source/_includes/installation/container/alternative.md

@@ -1,7 +1,6 @@
 ### Synology NAS
 
-Synology with DSM now supports Docker, allowing you to install Home Assistant using Docker without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see <https://www.synology.com/en-us/dsm/packages/Docker>
+Synology with DSM now supports container management through the Container Manager package, allowing you to install Home Assistant without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see <https://www.synology.com/en-us/dsm/packages/ContainerManager>
-
 The steps would be:
 
 - Install Docker "Container Manager" package on your Synology NAS

source/_integrations/aftership.markdown

@@ -12,7 +12,7 @@ ha_integration_type: integration
 ha_config_flow: true
 ---
 
-The `aftership` platform allows one to track deliveries by [AfterShip](https://www.aftership.com), a service that supports 490+ couriers worldwide. To use the tracking API functionality, the Essentials plan is required. This plan includes 100 shipments per month. There are various paid-for tiers after that.
+The `aftership` platform allows one to track deliveries by [AfterShip](https://www.aftership.com), a service that supports 490+ couriers worldwide. To use the tracking API functionality, the Pro plan is required. 
 
 The sensor value shows the number of packages that are not in `Delivered` state. As attributes are the number of packages per status.
 

source/_integrations/airgradient.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
 ha_domain: airgradient
 ha_platforms:
   - button
+  - diagnostics
   - number
   - select
   - sensor

source/_integrations/alexa.smart_home.markdown

@@ -231,17 +231,17 @@ Now remove the long-lived access token (if you want), copy the ARN of your Lambd
 
 ## Account linking
 
-Alexa needs to link your Amazon account to your Home Assistant account. Therefore Home Assistant can make sure only authenticated Alexa requests are able to access your home's devices. In order to link the account, you have to make sure your Home Assistant can be accessed from Internet at port 443.
+Alexa needs to link your Amazon account to your Home Assistant account. Therefore Home Assistant can make sure only authenticated Alexa requests are able to access your home's devices. In order to link the account, you have to make sure your Home Assistant can be accessed from Internet.
 
 - Return to the [Alexa Developer Console][alexa-dev-console], go to `Alexa Skills` page if you are not.
 - Find the skill you just created, click `Edit` link in the `Actions` column.
 - Click `ACCOUNT LINKING` in the left navigation bar of build page
 - Do not turn on the "Allow users to link their account to your skill from within your application or website" switch. This will require a Redirect URI, which won't work.
-- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`. For Alexa account linking, by default, the standard port 443 is used. Use your firewall to forward this, if needed:
+- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL][:PORT]`, where `PORT` is the TCP port. The port can be omitted if it is `443`. For Alexa account linking, by default, the standard port 443 is used by default. Use your firewall to forward this, if needed:
-  - `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]/auth/authorize`
+  - `Authorization URI`: `https://[YOUR HOME ASSISTANT URL][:PORT]/auth/authorize`
-  - `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]/auth/token`
+  - `Access Token URI`: `https://[YOUR HOME ASSISTANT URL][:PORT]/auth/token`
 
-    Although it is possible to assign a different port, Alexa requires you use port 443, so make sure your firewall/proxy is forwarding via port 443.
+    Although it is possible to assign a different port, it is preferable to use port 443, so in that case make sure your firewall/proxy is forwarding via port 443.
 
     Read [more from the Alexa developer documentation](https://developer.amazon.com/en-US/docs/alexa/account-linking/requirements-account-linking.html) about requirements for account linking.
 

source/_integrations/calendar.markdown

@@ -177,7 +177,7 @@ Add a new calendar event. A calendar `target` is selected with a [Target Selecto
 You either use `start_date_time` and `end_date_time`, or `start_date` and `end_date`, or `in`.
 {% endnote %}
 
-This is a full example of a {% term service %} call in YAML:
+This is a full example of an {% term action %} in YAML:
 
 ```yaml
 action: calendar.create_event

source/_integrations/cambridge_audio.markdown

@@ -11,6 +11,7 @@ ha_platforms:
   - diagnostics
   - media_player
   - select
+  - switch
 ha_codeowners:
   - '@noahhusby'
 ha_config_flow: true

source/_integrations/comelit.markdown

@@ -20,6 +20,7 @@ ha_platforms:
   - binary_sensor
   - climate
   - cover
+  - diagnostics
   - humidifier
   - light
   - sensor

source/_integrations/diagnostics.markdown

@@ -11,10 +11,7 @@ ha_codeowners:
 ha_integration_type: system
 ---
 
-The diagnostics {% term integration %} provides a way to download diagnostic data from
+The **Diagnostics** {% term integration %} provides a way to download diagnostic data from a {% term device %} or {% term integration %} for sharing in issue reports. Sharing diagnostics data when reporting an issue allows developers to diagnose and fix your reported problem quicker.
-a {% term device %} or {% term integration %}, that can be shared in issue reports. Sharing
-diagnostics data when reporting an issue allows developers to diagnose 
-and fix your reported problem quicker.
 
 <p class='img'>
 <img class="no-shadow" src='/images/blog/2022-02/diagnostics.png' alt='Screenshot showing the Download Diagnostics button on a Sonos device page'>

source/_integrations/dsmr_reader.markdown

@@ -17,6 +17,7 @@ ha_platforms:
   - diagnostics
   - sensor
 ha_integration_type: integration
+ha_quality_scale: gold
 ---
 
 The `dsmr_reader` sensor integration allows you to easily add all sensors that [DSMR Reader](https://dsmr-reader.readthedocs.io/en/latest/) (Dutch Smart Meter Requirements Reader) exposes to MQTT. It adds a separate sensor for every field in the MQTT topics which is named `sensor_dsmr_<mqtt_topic>`.

source/_integrations/epson.markdown

@@ -39,6 +39,7 @@ When you want to add a device for the first time, turn it on before following th
 - Epson EH-TW7000
 - Epson EH-TW9400W (shares platform with 7400/8400/9400(w))
 - Epson EH-TW3200
+- Epson Powerlite W39
 
 ## Configuration
 

source/_integrations/fritz.markdown

@@ -1,6 +1,6 @@
 ---
 title: AVM FRITZ!Box Tools
-description: Instructions on how to integrate AVM FRITZ!Box based routers into Home Assistant.
+description: Instructions on how to integrate AVM FRITZ!Box routers into Home Assistant.
 ha_category:
   - Binary sensor
   - Image
@@ -11,7 +11,6 @@ ha_release: '0.10'
 ha_domain: fritz
 ha_config_flow: true
 ha_codeowners:
-  - '@mammuth'
   - '@AaronDavidSchneider'
   - '@chemelli74'
   - '@mib1185'
@@ -29,26 +28,31 @@ ha_ssdp: true
 ha_integration_type: integration
 ---
 
-The AVM FRITZ!Box Tools integration allows you to control your [AVM FRITZ!Box](https://en.avm.de/products/fritzbox/) based router.
+The AVM FRITZ!Box Tools integration allows you to control your [AVM FRITZ!Box](https://en.avm.de/products/fritzbox/) router and have presence detection for connected network devices.
 
 There is support for the following platform types within Home Assistant:
 
-- **Device tracker** - presence detection by looking at connected devices.
+- **{% term "Device tracker" %}** - presence detection by looking at connected devices.
-- **Binary sensor** - connectivity status.
+- **{% term "Binary sensor" %}** - connectivity status.
-- **Image** - QR code for Guest Wi-Fi.
+- **{% term Image %}** - QR code for Guest Wi-Fi.
-- **Button** - reboot, reconnect, firmware_update.
+- **{% term Button %}** - reboot, reconnect, firmware update.
-- **Sensor** - external IP address, uptime and network monitors.
+- **{% term Sensor %}** - external IP address, uptime and network monitors.
-- **Switch** - call deflection, port forward, parental control and Wi-Fi networks.
+- **{% term Switch %}** - call deflection, port forward, parental control and Wi-Fi networks.
-- **Update** - firmware status of the device.
+- **{% term Update %}** - firmware status of the device.
+
 {% include integrations/config_flow.md %}
 
 {% important %}
-Both TR-064 and UPnP need to be enabled in the FRITZ!Box ( Home Network -> Network -> Network settings -> Access Settings in the Home Network ) for Home Assistant to login and read device info.
+Both the TR-064 (_Permit access for apps_) and UPnP (_Transmit status information over UPnP_) protocol needs to be enabled in the FRITZ!Box under **Home Network** > **Network** > **Network settings** > **Access Settings in the Home Network** for Home Assistant to login and read device info.
 {% endimportant %}
 
 ## Username
 
-The configuration in the UI asks for a username. Starting from FRITZ!OS 7.24 the FRITZ!Box creates a random username for the admin user if you didn't set one yourself. This can be found after logging into the FRITZ!Box and visiting System -> FRITZ!Box Users -> Users. The username starts with `fritz` followed by four random numbers. Under properties on the right it says `created automatically`. Prior to FRITZ!OS 7.24 the default username was `admin`.
+It is recommended to create a separate user to connect Home Assistant to your FRITZ!Box. To create a user, in the FRITZ!Box go to **System** > **FRITZ!Box Users** > **Users** > **Add User**. Make sure the user has the **FRITZ!Box Settings** permission.
+
+{% note %}
+If you still want to use the predefined user, please note that as of FRITZ!OS 7.24, the FRITZ!Box creates a random username for the admin user if you didn't set one yourself. This can be found after logging into the FRITZ!Box and visiting **System** > **FRITZ!Box Users** > **Users**. The username starts with `fritz` followed by four random numbers. Under properties on the right it says `created automatically`. Prior to FRITZ!OS 7.24, the default username was `admin`.
+{% endnote %}
 
 ## Actions
 
@@ -56,50 +60,50 @@ Available {% term actions %}: `set_guest_wifi_password`
 
 ### Action `set_guest_wifi_password`
 
-Set a new password for the guest wifi.
+Set a new password for the guest wifi. The password Length must be between 8 and 63 characters long.
-The password must be between 8 and 63 characters long.
-If no password is given, it will be auto-generated.
 
-| Data attribute | Optional | Description                                                                                                    |
+| Data attribute | Required | Description |
-| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------- |
+| --- | --- | --- |
-| `device_id`            | no       | Only act on a specific  router                                                                                 |
+| `device_id` | yes | Only act on a specific router |
-| `password`             | yes      | New password for the guest wifi                                                                                |
+| `password` | no | New password for the guest wifi (_will be auto-generated if not defined_) |
-| `length`               | yes      | Length of the auto-generated password. (_default 12_)                        |
+| `length` | no | Length of the auto-generated password. (_default 12_) |
 
 ## Integration options
 
 It is possible to change some behaviors through the integration options.
 To change the settings, go to {% my integrations title="**Settings** > **Devices & services**" %}. Select the **AVM FRITZ!Box Tools** integration, then select **Configure**.
 
-- **Consider home**: Number of seconds that must elapse before considering a disconnected device "not at home".
+### Consider home
-- **Enable old discovery method**: Needed on some scenarios like no mesh support (fw <= 6.x), mixed brands network devices or LAN switches.
 
-## Additional info
+Number of seconds that must elapse before considering a disconnected device "not at home".
 
-### Parental control
+### Enable old discovery method
 
-Parental control switches can be used to enable and disable internet access of individual devices. If a device has internet access it will be enabled, otherwise it will be disabled. You can also find the current blocking state of the individual devices in the UI of the FRITZ!Box under `Internet` -> `Filters` -> `Parental Controls` -> `Device Block`
+Needed on some scenarios like no mesh support (_FritzOS <= 6.x_) or mixed brands network devices or LAN switches.
 
-Parental control switches are designed for advanced users, thus they are disabled by default. You need to enable the wanted entities manually.
+## Additional information
+
+### Parental control switches
+
+Parental control {% term switches %} can be used to enable and disable internet access of individual devices. You can also find the current blocking state of the individual devices in the UI of the FRITZ!Box under **Internet** > **Filters** > **Parental Controls** > **Device Block**.
 
 ### Device tracker
 
-**Note**: If you don't want to automatically track newly detected devices, disable the integration system option `Enable new added entities`.
+**Note**: If you don't want to automatically track newly detected devices, disable the {% term integration %} system option `Enable new added entities`.
 
-### Port forward
+### Port forward switches
 
-Due to security reasons, AVM implemented the ability to enable/disable a port forward rule only from the host involved in the rule.
+Due to security reasons, AVM implemented the ability to enable/disable a port forward rule only from the host involved in the rule. As a result, this integration will create entities only for rules that have your Home Assistant host as a destination.
-As a result, this integration will create entities only for rules that have your Home Assistant host as a destination.
 
-**Note 1**: On your FRITZ!Box, enable the setting `Permit independent port sharing for this device` for the device which runs HA (`Internet` -> `Permit Access` -> `<Name of HA device>`)
+**Note 1**: On your FRITZ!Box under **Internet** > **Permit Access**, enable the setting `Permit independent port sharing for this device` for the device which runs HA.
 
-**Note 2**: Only works if you have a dedicated IPv4 address (it won't work with DS-Lite)
+**Note 2**: Only works if you have a dedicated IPv4 address (_it won't work with DS-Lite_)
 
 ## Example Automations and Scripts
 
 ### Script: Reconnect / get new IP
 
-The following script can be used to easily add a reconnect button to your UI. If you want to reboot your FRITZ!Box, you can use `fritz.reboot` instead.
+The following {% term script %} can be used to easily add a reconnect button to your UI. If you want to reboot your FRITZ!Box, you can use `fritz.reboot` instead.
 
 ```yaml
 fritz_box_reconnect:
@@ -142,3 +146,16 @@ automation:
           message: "Password: ..."
 
 ```
+
+## Troubleshooting
+
+In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue re-occurs stop the debug logging again (_download of debug log file will start automatically_). Further _if still possible_, please also download the {% term diagnostics %} data. If you have collected the debug log and the diagnostics data, provide them with the issue report.
+
+### Device presence detection is not working as expected
+
+Check if one of the following cases applies:
+
+- You see a device as still present, even if it is offline or disconnected for more than the configured [consider home](#consider-home) seconds.
+- You're using additional network equipment like a network switch or Wi-Fi access point other than an AVM Fritz!Repeater or other AVM components, but not configured as a [mesh](https://en.avm.de/service/knowledge-base/dok/FRITZ-Box-7590/3329_Mesh-with-FRITZ/) in your home network.
+
+If one of the above cases applies to your setup, try [enabling the old discovery method](#enable-old-discovery-method) in the [integration options](#integration-options). This might resolve the issue.

source/_integrations/history_stats.markdown

@@ -121,7 +121,11 @@ Depending on the sensor type you choose, the `history_stats` integration can sho
 
 - **time**: The default value, which is the tracked time, in hours
 - **ratio**: The tracked time divided by the length of your period, as a percentage
-- **count**: How many times the tracked entity matched the configured state during the time period
+- **count**: How many times the tracked entity matched the configured state during the time period. This will count states (for example, how many times a light was in the `on` state during the time period), as opposed to counting state transitions (for example, how many times a light was *turned* `on`). The difference is if the entity was already in the desired state at the start of the time period, that scenario will be counted with this sensor type.
+
+{% note %}
+For a count sensor that uses a time period that does not slide (such as one that resets upon each hour, as opposed to one which considers the trailing 60 minutes), consider using [customization](/docs/configuration/customizing-devices/#customizing-an-entity-in-yaml) to change the `state_class` to `total_increasing` to generate statistics that track the `sum`. This is useful when emulating the behavior of a `utility_meter` helper that has a defined reset cycle. Without intervention, the `state_class` of any `history_stats` sensor will be `measurement` and will therefore generate `average`, `min`, and `max` statistics.
+{% endnote %}
 
 ## Time periods
 
@@ -158,6 +162,10 @@ duration:
 If the duration exceeds the number of days of history stored by the `recorder` integration (`purge_keep_days`), the history statistics sensor will not have all the information it needs to look at the entire duration. For example, if `purge_keep_days` is set to 7, a history statistics sensor with a duration of 30 days will only report a value based on the last 7 days of history.
 {% endnote %}
 
+{% note %}
+The history stats sensor will be updated when the source entity changes or once per minute if there is no source change. Keep this in mind when using fixed durations that aren't evenly divisible by one minute.
+{% endnote %}
+
 ### Video tutorial
 This video tutorial explains how you can use history stats. It also shows how you can create a daily bar chart graph to visualize things such as occupancy, or how long the lights are on in a particular room.
 

source/_integrations/homeassistant.markdown

@@ -296,8 +296,8 @@ homeassistant:
     ice_servers:
     # Add an entry for each STUN or TURN server
     - url:
-      - "stun:stun.l.google.com:19302"
+      - "stun:stun.example.com:19302"
-      - "stun:stun1.l.google.com:3478"
+      - "stun:stun2.example.com:12345"
     - url: "turn:turn.domain.com"
       username: "username"
       credential: "abc123"

source/_integrations/http.markdown

@@ -73,7 +73,7 @@ ip_ban_enabled:
   description: Flag indicating whether additional IP filtering is enabled.
   required: false
   type: boolean
-  default: false
+  default: true
 login_attempts_threshold:
   description: "Number of failed login attempt from single IP after which it will be automatically banned if `ip_ban_enabled` is `true`. When set to -1 no new automatic bans will be added."
   required: false

source/_integrations/intent_script.markdown

@@ -46,7 +46,7 @@ intent:
       description: List of domains that the entity supports.
       required: false
       type: list
-    actions:
+    action:
       description: Defines an action to run to intents.
       required: false
       type: action
@@ -109,7 +109,7 @@ conversation:
 
 intent_script:
   EventCountToday:
-    actions:
+    action:
       - action: calendar.get_events
         target:
           entity_id: calendar.my_calendar

source/_integrations/jewish_calendar.markdown

@@ -100,35 +100,35 @@ The following is the list of holidays the sensor knows about with their selected
 | yom_kippur           | Yom Kippur                 | יום הכפורים           | YOM_TOV                   | 1       |
 | erev_sukkot          | Erev Sukkot                | ערב סוכות             | EREV_YOM_TOV              | 2       |
 | sukkot               | Sukkot                     | סוכות                 | YOM_TOV                   | 1       |
+| sukkot_ii            | Sukkot II                  | שני של סוכות          | YOM_TOV                   | 1       |
 | hol_hamoed_sukkot    | Hol hamoed Sukkot          | חול המועד סוכות       | HOL_HAMOED                | 3       |
 | hoshana_raba         | Hoshana Raba               | הושענא רבה            | EREV_YOM_TOV              | 2       |
+| shmini_atzeret       | Shmini Atzeret             | שמיני עצרת            | YOM_TOV                   | 1       |
 | simchat_torah        | Simchat Torah              | שמחת תורה             | YOM_TOV                   | 1       |
 | chanukah             | Chanukah                   | חנוכה                 | MELACHA_PERMITTED_HOLIDAY | 4       |
+| rabin_memorial_day   | Yitzhak Rabin memorial day | יום הזכרון ליצחק רבין | MEMORIAL_DAY              | 8       |
 | asara_btevet         | Asara B'Tevet              | צום עשרה בטבת         | FAST_DAY                  | 5       |
 | tu_bshvat            | Tu B'Shvat                 | ט"ו בשבט              | MINOR_HOLIDAY             | 7       |
+| family_day           | Family Day                 | יום המשפחה            | ISRAEL_NATIONAL_HOLIDAY   | 9       |
+| memorial_day_unknown | Memorial day for fallen whose place of burial is unknown | יום הזיכרון לחללי מערכות ישראל שמקום קבורתם לא נודע | MEMORIAL_DAY | 8      |
 | taanit_esther        | Ta'anit Esther             | תענית אסתר            | FAST_DAY                  | 5       |
 | purim                | Purim                      | פורים                 | MELACHA_PERMITTED_HOLIDAY | 4       |
 | shushan_purim        | Shushan Purim              | שושן פורים            | MELACHA_PERMITTED_HOLIDAY | 4       |
 | erev_pesach          | Erev Pesach                | ערב פסח               | EREV_YOM_TOV              | 2       |
 | pesach               | Pesach                     | פסח                   | YOM_TOV                   | 1       |
+| pesach_ii            | Pesach II                  | שני של פסח            | YOM_TOV                   | 1       |
 | hol_hamoed_pesach    | Hol hamoed Pesach          | חול המועד פסח         | HOL_HAMOED                | 3       |
 | pesach_vii           | Pesach VII                 | שביעי פסח             | YOM_TOV                   | 1       |
-| yom_haatzmaut        | Yom HaAtzma'ut             | יום העצמאות           | MODERN_HOLIDAY            | 6       |
+| pesach_viii          | Pesach VIII                | אחרון של פסח          | YOM_TOV                   | 1       |
-| lag_bomer            | Lag B'Omer                 | ל"ג בעומר             | MINOR_HOLIDAY             | 7       |
-| erev_shavuot         | Erev Shavuot               | ערב שבועות            | EREV_YOM_TOV              | 2       |
-| shavuot              | Shavuot                    | שבועות                | YOM_TOV                   | 1       |
-| tzom_tammuz          | Tzom Tammuz                | צום שבעה עשר בתמוז    | FAST_DAY                  | 5       |
-| tisha_bav            | Tish'a B'Av                | תשעה באב              | FAST_DAY                  | 5       |
-| tu_bav               | Tu B'Av                    | ט"ו באב               | MINOR_HOLIDAY             | 7       |
 | yom_hashoah          | Yom HaShoah                | יום השואה             | MEMORIAL_DAY              | 8       |
 | yom_hazikaron        | Yom HaZikaron              | יום הזכרון            | MEMORIAL_DAY              | 8       |
+| yom_haatzmaut        | Yom HaAtzma'ut             | יום העצמאות           | MODERN_HOLIDAY            | 6       |
+| lag_bomer            | Lag B'Omer                 | ל"ג בעומר             | MINOR_HOLIDAY             | 7       |
 | yom_yerushalayim     | Yom Yerushalayim           | יום ירושלים           | MODERN_HOLIDAY            | 6       |
-| shmini_atzeret       | Shmini Atzeret             | שמיני עצרת            | YOM_TOV                   | 1       |
+| erev_shavuot         | Erev Shavuot               | ערב שבועות            | EREV_YOM_TOV              | 2       |
-| pesach_viii          | Pesach VIII                | אחרון של פסח          | YOM_TOV                   | 1       |
+| shavuot              | Shavuot                    | שבועות                | YOM_TOV                   | 1       |
 | shavuot_ii           | Shavuot II                 | שני של שבועות         | YOM_TOV                   | 1       |
-| sukkot_ii            | Sukkot II                  | שני של סוכות          | YOM_TOV                   | 1       |
+| tzom_tammuz          | Tzom Tammuz                | צום שבעה עשר בתמוז    | FAST_DAY                  | 5       |
-| pesach_ii            | Pesach II                  | שני של פסח            | YOM_TOV                   | 1       |
-| family_day           | Family Day                 | יום המשפחה            | ISRAEL_NATIONAL_HOLIDAY   | 9       |
-| memorial_day_unknown | Memorial day for fallen whose place of burial is unknown | יום הזיכרון לחללי מערכות ישראל שמקום קבורתם לא נודע | MEMORIAL_DAY | 8      |
-| rabin_memorial_day   | Yitzhak Rabin memorial day | יום הזכרון ליצחק רבין | MEMORIAL_DAY              | 8       |
 | zeev_zhabotinsky_day | Zeev Zhabotinsky day       | יום זאב ז'בוטינסקי    | MEMORIAL_DAY              | 8       |
+| tisha_bav            | Tish'a B'Av                | תשעה באב              | FAST_DAY                  | 5       |
+| tu_bav               | Tu B'Av                    | ט"ו באב               | MINOR_HOLIDAY             | 7       |

source/_integrations/knocki.markdown

@@ -16,12 +16,30 @@ ha_platforms:
 ha_integration_type: hub
 ---
 
-The **Knocki** {% term integration %} can receive events for the triggers set up from your [Knocki devices](https://knocki.com/).
+The **Knocki** {% term integration %} allows you to trigger your favorite automations simply by tapping custom patterns (such as triple taps) on ordinary surfaces.
 
 ## Prerequisites
 
-To use the Knocki integration, you need a Knocki account.
+- You must have a [Knocki device](http://knocki.com).
 
-Once you set a trigger in the app, it will show up in Home Assistant to use.
+- Completed the setup process in the **Knocki** mobile app, as described in steps 1-7 below.
+
+1. Open the Knocki Mobile App. It’s a free download on [iOS](https://apps.apple.com/us/app/knocki/id1238395440) and [Android](https://play.google.com/store/apps/details?id=com.knocki.mobileapp).
+2. Using the app, log-in or create a new Knocki account.
+3. From the app’s home screen, select a Knocki or [add a Knocki](https://support.knocki.com/hc/en-us/articles/12769368448659-How-Do-Add-a-Knocki-to-My-Account).
+4. On the app’s device screen, select a gesture or [add a gesture](https://support.knocki.com/hc/en-us/articles/360013333634-Creating-a-Gesture).
+5. Next, select the [add a task](https://support.knocki.com/hc/en-us/articles/12920956118291-How-do-I-Add-Tasks-to-a-Knocki) option.
+6. Scroll down the task menu and select Home Assistant.
+7. Follow the in-app instructions to add the Home Assistant task.
 
 {% include integrations/config_flow.md %}
+
+## Automation example
+
+1. Go to {% my automations title="**Settings** > **Automations & scenes**" %} and in the lower right corner, select  **Create Automation**.
+2. Select **Create new automation**.
+3. Select **Add Trigger**, select **Entity** as the trigger type.
+   - Search for the name of the task (as you named it in the Knocki app). Select the entity with that name appended to it.
+   - Select **State** as the type of entity change.
+4. Select **Add action** and choose whatever action(s) you’d like the automation to trigger.
+5. Finally, test the action by tapping the associated gesture pattern.

source/_integrations/lektrico.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - number
   - select
   - sensor
+  - switch
 ha_integration_type: device
 ---
 

source/_integrations/local_file.markdown

@@ -6,7 +6,6 @@ ha_category:
 ha_iot_class: Local Polling
 ha_release: 0.22
 ha_domain: local_file
-ha_config_flow: true
 ha_platforms:
   - camera
 ha_integration_type: integration

source/_integrations/mqtt.markdown

@@ -454,13 +454,7 @@ To allow a smooth migration from single component discovery to device-based disc
 2. Move the `object_id` inside the discovery payload, if that is available, or use a unique ID or the component.
 3. Consider using the previous `node_id` as the new `object_id` of the device discovery topic.
 4. Ensure the `unique_id` matches and the `device` context has the correct identifiers.
-5. Send the following payload to all existing single component discovery topics:
+5. Send the following payload to all existing single component discovery topics: `{"migrate_discovery": true }`. This will unload the discovered item, but its settings will be retained.
-
-```json
-{"migrate_discovery": true }
-```
-
-This will unload the discovered item, but its settings will be retained.
 6. Switch the discovery topic to the device-based discovery topic and include all the component configurations.
 7. Clean up the single component discovery messages with an empty payload.
 
@@ -1317,6 +1311,7 @@ The following software has built-in support for MQTT discovery:
 - [Nuki Hub](https://github.com/technyon/nuki_hub)
 - [Nuki Smart Lock 3.0 Pro](https://support.nuki.io/hc/articles/12947926779409-MQTT-support), [more info](https://developer.nuki.io/t/mqtt-api-specification-v1-3/17626)
 - [OpenMQTTGateway](https://github.com/1technophile/OpenMQTTGateway)
+- [OTGateway](https://github.com/Laxilef/OTGateway)
 - [room-assistant](https://github.com/mKeRix/room-assistant) (starting with 1.1.0)
 - [SmartHome](https://github.com/roncoa/SmartHome)
 - [SpeedTest-CLI MQTT](https://github.com/adorobis/speedtest-CLI2mqtt)
@@ -1330,7 +1325,6 @@ The following software has built-in support for MQTT discovery:
 - [Xiaomi DaFang Hacks](https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks)
 - [Zehnder Comfoair RS232 MQTT](https://github.com/adorobis/hacomfoairmqtt)
 - [Zigbee2MQTT](https://github.com/koenkk/zigbee2mqtt)
-- [OTGateway](https://github.com/Laxilef/OTGateway)
 
 ## Manual configured MQTT items
 

source/_integrations/music_assistant.markdown

@@ -1,38 +0,0 @@
----
-title: Music Assistant
-description: Instructions on how to integrate Music Assistant into Home Assistant.
-ha_category:
-  - Media player
-ha_release: 2024.11
-ha_iot_class: Local Push
-ha_config_flow: true
-ha_codeowners:
-  - '@music_assistant'
-ha_domain: music_assistant
-ha_platforms:
-  - media_player
-ha_zeroconf: true
-ha_integration_type: integration
----
-
-The **Music Assistant**(MA) {% term integrations %} allows you to connect Home Assistant to a [Music Assistant Server](https://music-assistant.io/). Once configured, all [MA Players](https://music-assistant.io/player-support/) show up as Home Assistant [media player entities](/integrations/media_player/).  Media players will allow you to control media playback and see the currently playing item.
-
-There is currently support for the following Home Assistant Platforms:
-
-- [Media player](#media-player)
-
-All of the Home Assistant [Media Player Control Actions](https://www.home-assistant.io/integrations/media_player/#media-control-actions) are supported.
-
-{% include integrations/config_flow.md %}
-
-### Manual configuration
-
-Under normal circumstances, Home Assistant automatically discovers your running Music Assistant Server. If something special about the HA or MA setup (for example, the MA server is running as a remote Docker container) or discovery is not working, you can manually specify the URL to your Music Assistant server. 
-
-## Media player
-
-The Music Assistant media player creates media player entities for all players available in MA including those imported from Home Assistant. This is needed to provide the full functionality Music Assistant has to offer. These entities will display media information, playback progress, and playback controls.
-
-## Notes
-
-- Any Home Assistant players added to Music Assistant will appear duplicated as the MA version of the player is created. The original HA player can be hidden if desired.

source/_integrations/pegel_online.markdown

@@ -9,6 +9,7 @@ ha_config_flow: true
 ha_iot_class: Cloud Polling
 ha_domain: pegel_online
 ha_platforms:
+  - diagnostics
   - sensor
 ha_codeowners:
   - '@mib1185'

source/_integrations/person.markdown

@@ -44,7 +44,8 @@ If you have administrator rights, you can add other persons to Home Assistant an
    - They cannot have their own dashboard, for example.
    - But they can still be used for device tracking and show up on a map and be used in automations.
 5. If they are able to log in, fill in the user information.
-   - Check if the user name is correct. A suggestion is made based on the person name. But they do not have to be identical.
+   - Check if the username is correct. A suggestion is made based on the person name. But they do not have to be identical.
+     - The username must be lowercase and contain no spaces.
      - The username is required to log in.
      - The person name is the name displayed in the UI.
    - Enter a password and store it in a safe location.

source/_integrations/pinecil.markdown

@@ -4,6 +4,7 @@ description: Connect and control your Pinecil devices using the IronOS integrati
 ha_category:
   - Number
   - Sensor
+  - Update
 ha_release: 2024.8
 ha_domain: pinecil
 ha_integration_type: virtual
@@ -15,6 +16,7 @@ ha_config_flow: true
 ha_platforms:
   - number
   - sensor
+  - update
 ha_iot_class: Local Polling
 ---
 

source/_integrations/remote_rpi_gpio.markdown

@@ -19,7 +19,7 @@ related:
 
 The `remote_rpi_gpio` {% term integration %} is the base for all related GPIO platforms in Home Assistant. For the platform configurations, please check their corresponding sections.
 
-The remote Raspberry Pi, and the control computer where Home Assistant is running must be configured to be able to run `remote_rpi_gpio`, see [Configuring Remote GPIO](https://gpiozero.readthedocs.io/en/stable/remote_gpio.html) for more details.
+The remote Raspberry Pi, and the control computer where Home Assistant is running must be configured to be able to run `remote_rpi_gpio`, see [Configuring Remote GPIO](https://gpiozero.readthedocs.io/en/stable/remote_gpio.html) for more details. Unfortunately, this setup is not currently possible with remote, Raspberry Pi 5 hosts, [due to a lack of support in pigiod](https://github.com/joan2937/pigpio/issues/586).
 
 Note that for virtual environments, you may need to set an environment variable when starting the environment to set the pin factory, for example:
 

source/_integrations/roomba.markdown

@@ -10,7 +10,6 @@ ha_codeowners:
   - '@pschmitt'
   - '@cyr-ius'
   - '@shenxn'
-  - '@Xitee1'
   - '@Orhideous'
 ha_domain: roomba
 ha_config_flow: true

source/_integrations/schedule.markdown

@@ -171,10 +171,10 @@ triggers:
         - schedule.light_schedule
       to: "on"
   actions:
-    - service: light.turn_on
+    - action: light.turn_on
       target:
-        entity_id: climate.thermostat
+        entity_id: light.kitchen
-      data_template:
+      data:
         brightness_pct: "{{ state_attr('schedule.light_schedule', 'brightness') }}"
         kelvin: "{{ state_attr('schedule.light_schedule, 'temperature') }}"
 ```

source/_integrations/schlage.markdown

@@ -14,6 +14,7 @@ ha_platforms:
   - binary_sensor
   - diagnostics
   - lock
+  - select
   - sensor
   - switch
 ha_integration_type: integration

source/_integrations/spotify.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
 ha_domain: spotify
 ha_zeroconf: true
 ha_platforms:
+  - diagnostics
   - media_player
   - sensor
 ha_integration_type: service

source/_integrations/squeezebox.markdown

@@ -8,6 +8,8 @@ ha_iot_class: Local Polling
 ha_domain: squeezebox
 ha_codeowners:
   - '@rajlaud'
+  - '@pssc'
+  - '@peteS-UK'
 ha_config_flow: true
 ha_dhcp: true
 ha_platforms:

source/_integrations/statistics.markdown

@@ -20,19 +20,14 @@ ha_config_flow: true
 
 The `statistics` integration observes the state of a source sensor and provides aggregated statistical characteristics about its recent past. This integration can be useful in automation, for example, to trigger an action when the air humidity in the bathroom settles after a hot shower or when the number of brewed coffees over a day gets too high.
 
-The `statistics` sensor can use either the numeric `sensor` or `binary_sensor` as it's input. The time period and/or number of recent state changes, which should be considered, must be given in configuration. Check the configuration section below for details.
+The statistics sensor updates with every update of the source sensor, for which the numeric `sensor` and `binary_sensor` are supported. The time period and/or number of recent state changes, which should be considered, must be given in configuration. Check the configuration section below for details.
 
 Assuming the [`recorder`](/integrations/recorder/) integration is running, historical sensor data is read from the database on startup and is available immediately after a restart of the platform. If the [`recorder`](/integrations/recorder/) integration is *not* running, it can take some time for the sensor to start reporting data because some characteristics calculations require more than one source sensor value.
 
 {% tip %}
-The `statistics` integration is not the same as the [Long-term Statistics](https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics). More details on the differences can be found in the [2021.8.0 release notes](/blog/2021/08/04/release-20218/#long-term-statistics).
+The `statistics` integration is different to [Long-term Statistics](https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics). More details on the differences can be found in the [2021.8.0 release notes](/blog/2021/08/04/release-20218/#long-term-statistics).
 {% endtip %}
 
-The `statistics` sensor has an internal buffer that stores the values it needs for the computation of the various functions (for example, `average_step`). The sensor is updated whenever new values are added to the buffer or when elements are removed. This is triggered either by a change of the source sensor (which may or may not change its actual value) or by values expiring (in cases where `max_age` was specified). This means that the buffer can hold a sequence of identical values in cases where values are not changing over time.
-
-When using a time-based buffer (by providing a `max_age`), it is recommended to ensure that the buffer contains at least a decent number of values spanning the full range of time. For sensors that don't change much, this can be achieved by using a template sensor with a time-based trigger as input. If the input values don't cover most of the time range, the computed output values could lead to unexpected results.
-Example: To find out whether a switch was used in the last 5 minutes, `count_on` could be used. However, if there are no frequent readings a single "Off" (maybe only a second ago) in the buffer would produce 0 even though the sensor was "On" for most of the last five minutes.
-
 {% include integrations/config_flow.md %}
 
 Further information about these configuration options can be found under the [YAML configuration](#yaml-configuration)
@@ -66,8 +61,8 @@ The following are supported for `sensor` source sensors `state_characteristic`:
 
 | State Characteristic | Description |
 | -------------------- | ----------- |
-| `average_linear` | The average value of stored measurements under consideration of the time distances between them. A linear interpolation is applied per measurement pair. Suited to observe a source sensor with frequent, non-periodic sensor updates and when continuous behavior is represented by the measurements (e.g. your electricity consumption). WARNING: This doesn't compute the exact average over the full interval defined by `max_age`. It will only consider the interval between the first and the last value in the buffer. |
+| `average_linear` | The average value of stored measurements under consideration of the time distances between them. A linear interpolation is applied per measurement pair. Suited to observe a source sensor with frequent, non-periodic sensor updates and when continuous behavior is represented by the measurements (e.g. your electricity consumption). WARNING: This type of average may show unexpected behavior in cases where values remain stable (e.g. an equally spaced sequence of t1:0 -> t2:0 -> t3:0 -> t4:0 -> t5:10 would produce an average of 5 instead of 1,25 because the non-changing zeros in the middle (t2 to t4) are being filtered out by Home Assistant and so the actually computed curve already starts rising at t1 instead of staying flat until t4). Accordingly, this function is only making sense in the context of noisy sensors that keep changing constantly. |
-| `average_step` | The average value of stored measurements under consideration of the time distances between them. LOCF (last observation carried forward weighting) is applied, meaning, that the old value is assumed between two measurements. This is a better fit to how Home Assistant deals with constant values (compared to the linear function) and it is also better fitting to sensors that are switching between stable phases (e.g. a heating level set to either 1, 2 or 3). WARNING: This doesn't compute the exact average over the full interval defined by `max_age`. It will only consider the interval between the first and the last value in the buffer. |
+| `average_step` | The average value of stored measurements under consideration of the time distances between them. LOCF (last observation carried forward weighting) is applied, meaning, that the old value is assumed between two measurements. This is a better fit to how Home Assistant deals with constant values (compared to the linear function) and it is also better fitting to sensors that are switching between stable phases (e.g. a heating level set to either 1, 2 or 3). WARNING: Even when a time interval is specified by the max age parameter, the average is not necessarily matching the average over that whole interval (e.g. when values were removed due to the sampling size limit). |
 | `average_timeless` | The average value of stored measurements. This method assumes that all measurements are equally spaced and, therefore, time is ignored and a simple average of values is computed. Equal to `mean`. |
 | `change_sample` | The average change per sample. The difference between the newest and the oldest measurement is divided by the number of in-between measurements (n-1). |
 | `change_second` | The average change per second. The difference between the newest and the oldest measurement is divided by seconds between them. |

source/_integrations/suez_water.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
   - '@ooii'
+  - '@jb101010-2'
 ha_domain: suez_water
 ha_platforms:
   - sensor

source/_integrations/switcher_kis.markdown

@@ -17,6 +17,7 @@ ha_platforms:
   - climate
   - cover
   - diagnostics
+  - light
   - sensor
   - switch
 ha_config_flow: true

source/_integrations/tado.markdown

@@ -38,6 +38,10 @@ There is currently support for the following device types within Home Assistant:
 - Sensor - for some additional information of the zones.
 - Weather - for information about the current weather at the location of your Tado home.
 
+## Unsupported device types
+
+New Tado X devices are not supported by this integration, they have to be used through the [Matter integration](/integrations/matter).
+
 {% include integrations/config_flow.md %}
 
 The Tado thermostats are internet connected thermostats. There exists an unofficial API at [my.tado.com](https://my.tado.com/), which is used by their website and now by this component.

source/_integrations/verisure.markdown

@@ -96,6 +96,7 @@ Some users have reported that this integration currently doesn't work in the fol
 - France
 - Ireland
 - Italy
+- Spain
 - Sweden
 
 ## Troubleshooting

source/_integrations/vodafone_station.markdown

@@ -15,6 +15,7 @@ ha_iot_class: Local Polling
 ha_platforms:
   - button
   - device_tracker
+  - diagnostics
   - sensor
 ha_integration_type: hub
 ha_quality_scale: silver

source/_integrations/wyoming.markdown

@@ -12,6 +12,7 @@ ha_domain: wyoming
 ha_integration_type: service
 ha_platforms:
   - binary_sensor
+  - conversation
   - number
   - select
   - stt

source/_posts/2024-11-06-release-202411.markdown

@@ -0,0 +1,559 @@
+---
+layout: post
+title: "2024.11: Slick dashboards and speedy cameras"
+description: "Our new sections dashboards are now out of experimental and have become the default, low-latency camera streams using WebRTC, live streaming logs, Home Assistant Voice updates, and much more!"
+date: 2024-11-06 00:00:00
+date_formatted: "November 6, 2024"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2024-11/social.jpg
+---
+
+<lite-youtube videoid="rmV4ijEaRtI" videotitle="Home Assistant 2024.11 Release Party"></lite-youtube>
+
+Home Assistant 2024.11! 🎉
+
+It is November already, and we are closing in on the end of the year, but we are
+not slowing down!
+
+Before we dive into what this release has to offer, I want to take a moment to
+thank everyone who has contributed to the Home Assistant project. You might
+have heard this already, but going to share it again:
+
+_**We are number one!** 🥇_
+
+GitHub published its annual [Octoverse report], highlighting the platform's
+biggest trends and projects. It named Home Assistant 2024's largest open-source
+project, with over 21,000 contributors over the year. **That includes you! ❤️**
+
+Continuing the festivities, this release is a big one! The new dashboarding
+system we have been working on all year is now out of its experimental phase
+and generally available! 🥳 Exciting, **everyone** can now create beautiful
+dashboards with ease!
+
+To top it off, this release also supports faster and lower-latency camera
+streams using WebRTC, supported by the [Open Home Foundation].
+This is a huge improvement! 🎉
+
+Enjoy the release!
+
+../Frenck
+
+[Open Home Foundation]: https://www.openhomefoundation.org/
+[Octoverse report]: https://github.blog/news-insights/octoverse/octoverse-2024/
+
+<!--more-->
+
+- [Sections dashboard no longer experimental!](#sections-dashboard-no-longer-experimental)
+  - [Convert your old dashboards to sections view layout](#convert-your-old-dashboards-to-sections-view-layout)
+  - [Precise mode for card sizes](#precise-mode-for-card-sizes)
+- [Low latency cameras using WebRTC](#low-latency-cameras-using-webrtc)
+- [Integrations](#integrations)
+  - [New integrations](#new-integrations)
+  - [Noteworthy improvements to existing integrations](#noteworthy-improvements-to-existing-integrations)
+  - [Now available to set up from the UI](#now-available-to-set-up-from-the-ui)
+  - [Farewell to the following](#farewell-to-the-following)
+- [Other noteworthy changes](#other-noteworthy-changes)
+  - [Live logs](#live-logs)
+- [Voice](#voice)
+  - [Home Assistant intents improvements](#home-assistant-intents-improvements)
+  - [Join the Wake Word Collective](#join-the-wake-word-collective)
+- [Need help? Join the community!](#need-help-join-the-community)
+- [Backward-incompatible changes](#backward-incompatible-changes)
+- [All changes](#all-changes)
+
+## Sections dashboard no longer experimental!
+
+This release marks a big milestone in our pursuit of making dashboards easier to
+customize and use for everyone, aka [Project Grace]! The sections view layout,
+together with its drag-and-drop 🐲 capabilities and responsive design,
+is now **out of its experimental phase**, and ready for primetime! This means
+that, as of this release, you will get our awesome feature-rich and easy-to-use
+dashboard editing experience when you create a new dashboard. 🎉
+
+Over the past few months, we have worked hard to iterate and listen to your
+feedback to ensure that our new dashboard is easy to customize for both
+beginners and advanced users alike. We have added new capabilities such as
+[resizing cards], [visibility options], [wider sections], [new badges],
+and, most recently, adding [the new heading card].
+
+To finish this journey, we are adding two more features to this release.
+
+[new badges]: /blog/2024/08/07/release-20248/
+[Project Grace]: /blog/2024/03/04/dashboard-chapter-1/
+[resizing cards]: /blog/2024/07/03/release-20247/
+[the new heading card]: /blog/2024/10/02/release-202410/
+[visibility options]: /blog/2024/06/05/release-20246/
+[wider sections]: /blog/2024/09/04/release-20249/
+
+### Convert your old dashboards to sections view layout
+
+<p class='img no-shadow'><img class="no-shadow" alt="Screenshots showing the conversion of a view in masonry into sections" src="/images/blog/2024-11/dashboard-conversion.png"/>Screenshots showing the conversion of a view in masonry into sections</p>
+
+This release includes a way to convert individual dashboard views from the old
+masonry view layout to the new sections view layout. When you change the view
+type to sections, you get a button to convert the view. All the cards of the
+old view are then copied and placed in an imported cards section in the new
+view, and you can then easily drag-and-drop them into the right sections.
+
+Please note that cards placed within the imported cards section are only visible
+to users once moved to a section above the fold. This ensures that
+cards do not get accidentally shown in the wrong sections while you are still
+working on the dashboard.
+
+<p class='img no-shadow'><img class="no-shadow" alt="Screenshot of the imported cards section" src="/images/blog/2024-11/imported-cards.png"/>Screenshot of the imported cards section</p>
+
+If you are not ready for the new layout yet, no worries! Your old dashboard view
+is kept when a new dashboard is created, giving an excellent way for masonry
+view veterans to try out sections while keeping all the hard work they have put
+into customizing their cards.
+
+Alternatively, you can move each card one-by-one from another view. All moved
+cards will also be temporarily placed in the imported cards section.
+
+### Precise mode for card sizes
+
+<p class='img no-shadow'><img class="no-shadow" alt="Examples of cards using precise mode" src="/images/blog/2024-11/precise-mode-example.png" style="width: 60%;"/>Examples of cards using precise mode</p>
+
+If you love tinkering with your dashboards and fine-tuning card sizes with more
+precision, you now have even more control over the size of cards. In the layout
+options of a card you can now enable “Precise mode”, which will give you three
+times more options for the card widths!
+
+Precise mode is applied on a card-by-card level. While a normal section is
+divided into 4 columns, precise modes gives you 12 columns, which allows you
+to align 2, 3, 4, or 6 buttons side-by-side.
+
+## Low latency cameras using WebRTC
+
+Lots of effort has gone into this new and amazing feature for this release:
+**WebRTC**! 🎉
+
+<center><p class='no-shadow'><img class="no-shadow" alt="Logo of WebRTC" src="/images/blog/2024-11/webrtc-logo-horiz-retro.png" /></p></center>
+
+Not sure [what WebRTC is]? No worries! Let us try to explain. If you are
+watching a camera in Home Assistant, you might have noticed it is sometimes
+a bit slow and delayed. WebRTC support is going to change that!
+
+Camera streams will now try to use WebRTC whenever possible.
+[WebRTC is a standard] that makes a peer-to-peer connection for lower-latency
+audio and video streaming. You are probably using this technology a lot already,
+for example, when having an online video call. When you’re away from home,
+it will try to find the fastest and most direct path between your Home Assistant
+instance and the camera you are trying to view.
+
+[The Open Home Foundation] will host the negotiating network infrastructure
+([STUN servers]) **for free for all Home Assistant users** and enable the
+capability to use WebRTC for peer-to-peer connections whenever possible. If you are using Home Assistant OS or our containers, after you update this will automatically work out of the box.
+
+<center><p class='no-shadow'><img class="no-shadow" alt="Logo of the Open Home Foundation" src="https://www.openhomefoundation.org/assets/images/logo/open-home-foundation.svg" style="width: 90%" /></p></center>
+
+Sometimes, a direct connection between the client (like your browser
+or mobile app) and the camera is not possible; in those situations, the camera
+stream needs to be relayed by an external server. [Home Assistant Cloud] now
+provides this relay server ([TURN server]), and it's **included as one of the many benefits**
+available to all subscribers!
+
+So, no matter where you are, you should always be able to watch your cameras
+via this low-latency technology. If, for whatever reason, WebRTC is not
+available, it will fall back to using the old method of streaming to ensure
+you can always see your camera feeds.
+
+So, after reading all of this, what changed? Well, camera feeds will do everything they did before, but will be faster, more responsive, and less delayed! 🎉
+
+[Home Assistant Cloud]: /cloud/
+[STUN servers]: https://en.wikipedia.org/wiki/STUN
+[TURN server]: https://en.wikipedia.org/wiki/Traversal_Using_Relays_around_NAT
+[The Open Home Foundation]: https://www.openhomefoundation.org/
+[WebRTC is a standard]: https://webrtc.org/
+[what WebRTC is]: https://en.wikipedia.org/wiki/WebRTC
+
+## Integrations
+
+Thanks to our community for keeping pace with the new {% term integrations %}
+and improvements to existing ones! You’re all awesome 🥰
+
+### New integrations
+
+We welcome the following new integrations in this release:
+
+- **[LG ThinQ]**, added by [@LG-ThinQ-Integration]  
+  Integrate your LG ThinQ devices, such as air conditioners, refrigerators,
+  and washing machines. LG built and provided this integration! It's super nice
+  to see a manufacturer providing an integration for Home Assistant.
+- **[Husqvarna Automower BLE]**, added by [@alistair23]  
+  Integrate your Husqvarna lawnmower using Bluetooth.
+- **[Palazzetti]**, added by [@dotvav]  
+  Integrate your [Palazzetti pellet stove]; control the stove, fan speeds and get the current temperature.
+
+[@alistair23]: https://github.com/alistair23
+[@dotvav]: https://github.com/dotvav
+[@LG-ThinQ-Integration]: https://github.com/LG-ThinQ-Integration
+[Husqvarna Automower BLE]: /integrations/husqvarna_automower_ble
+[LG ThinQ]: /integrations/lg_thinq
+[Palazzetti pellet stove]: https://palazzettigroup.com/
+[Palazzetti]: /integrations/palazzetti
+
+### Noteworthy improvements to existing integrations
+
+It is not just new {% term integrations %} that have been added; existing
+integrations are also being constantly improved. Here are some of the noteworthy
+changes to existing integrations:
+
+- [@joostlek] has extended the [Spotify integration] with a whole bunch of new
+  sensors for the current song playing. You can now, for example, automate
+  putting your house into party mode 🎉 when the song playing is danceable
+  enough 😎 Awesome job!
+- The [LinkPlay integration] now has multiroom support! Group and ungroup your
+  devices to play music in sync or individually straight from Home Assistant.
+  Thanks [@silamon]!
+- Staying in the audio department, [@mj23000] added shuffle and repeat controls
+  to the [Bang & Olufsen integration]. Nice!
+- The [ViCare integration] now supports room sensors and hot water storage
+  sensors. Thanks for that [@CFenner]!
+- [@starkillerOG] added sensors to track the total number of installations and
+  integrations to the [Analytics Insights integration]. Nice!
+- The [Habitica integration] now supports sensors for gems, mystic hourglasses,
+  and calendars for to-dos and daily tasks. Thanks [@tr4nt0r]!
+- [@YogevBokobza] added support for the [Switcher Runner S12] to the
+  [Switcher integration]. Thanks for that!
+- The [Husqvarna Automower integration] keeps receiving love from [@Thomas55555].
+  This release adds work area and progress sensors. Nice!
+- [@bdraco] added support for the [SwitchBot Meter Pro] to the
+  [SwitchBot integration]. Thanks!
+- The [SwitchBot Cloud integration] now supports locks! Thanks [@miterion]!
+- A little more technical, but [@jbouwh] added support for
+  [MQTT device-based auto discovery]. This allows MQTT devices to be set up
+  and discovered once instead of separately for each entity; which is much
+  more efficient. Nice improvement!
+
+[@bdraco]: https://github.com/bdraco
+[@CFenner]: https://github.com/CFenner
+[@jbouwh]: https://github.com/jbouwh
+[@joostlek]: https://github.com/joostlek
+[@miterion]: https://github.com/miterion
+[@mj23000]: https://github.com/mj23000
+[@silamon]: https://github.com/silamon
+[@starkillerOG]: https://github.com/starkillerOG
+[@Thomas55555]: https://github.com/Thomas55555
+[@tr4nt0r]: https://github.com/tr4nt0r
+[@YogevBokobza]: https://github.com/YoavGivati
+[Analytics Insights integration]: /integrations/analytics_insights
+[Bang & Olufsen integration]: /integrations/bang_olufsen
+[Habitica integration]: /integrations/habitica
+[Husqvarna Automower integration]: /integrations/husqvarna_automower
+[LinkPlay integration]: /integrations/linkplay
+[MQTT device-based auto discovery]: /integrations/mqtt/#device-discovery-payload
+[Spotify integration]: /integrations/spotify
+[SwitchBot Cloud integration]: /integrations/switchbot_cloud
+[SwitchBot integration]: /integrations/switchbot
+[SwitchBot Meter Pro]: https://www.switch-bot.com/products/switchbot-meter-pro
+[Switcher integration]: /integrations/switcher_kis
+[Switcher Runner S12]: https://switcher.co.il/%D7%9E%D7%95%D7%A6%D7%A8/runner-lights-s12/
+[ViCare integration]: /integrations/vicare
+
+### Now available to set up from the UI
+
+While most {% term integrations %} can be set up directly from the Home Assistant
+user interface, some were only available using YAML configuration. We keep moving
+more integrations to the UI, making them more accessible for everyone
+to set up and use.
+
+The following integrations are now available via the Home Assistant UI:
+
+- **[Local file]**, done by [@gjohansson-ST]
+- **[Onkyo]**, done by [@Nebula83]
+- **[Smarty]**, done by [@joostlek]
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@joostlek]: https://github.com/joostlek
+[@Nebula83]: https://github.com/Nebula83
+[Local file]: /integrations/local_file
+[Onkyo]: /integrations/onkyo
+[Smarty]: /integrations/smarty
+
+### Farewell to the following
+
+The following {% term integrations %} are also no longer available as
+of this release:
+
+- **Bloomsky**. Their service shut down.
+- **Google Domains**. The domain registration service by Google has been
+  shut down.
+- **Spider**. The service is no longer available.
+
+## Other noteworthy changes
+
+There are many more improvements in this release; here are some of the other
+noteworthy changes:
+
+- [Image entities] now have a snapshot action, allowing you to save the current
+  image in the entity to a file. Nice [@NickM-27]!
+- [@Petro31] added [(limited) template] support to the "at" field of [time triggers].
+  This allows you to template the time of that trigger in, for example,
+  a blueprint automation.
+- [Nautical miles] (`nmi`) is now a valid distance unit. This means you can now
+  use this as a unit for your distance sensors. Thanks [@mib1185]!
+- [@tetele] added [blueprints for template entities]! This allows for easier
+  re-use and sharing of common blueprints for sets of templated entities.
+  This is an advanced feature and is only available using manual YAML
+  configuration.
+- [@MindFreeze] and [@matthiasdebaat] have improved the network settings user
+  interface. It is now easier to manage and configure your network settings,
+  including nicer handling of IP addresses, improved Wi-Fi configuration,
+  and better visibility on the URLs Home Assistant is using for your instance.
+- We now indicate if a custom integration is overriding a built-in integration.
+  This makes it easier to spot if a custom integration is taking over a
+  built-in integration while you are wondering why you didn't get the latest
+  features Home Assistant releases bring. Thanks, [@MindFreeze]!
+
+[(limited) template]: /docs/configuration/templating/#limited-templates
+[@matthiasdebaat]: https://github.com/matthiasdebaat
+[@mib1185]: https://github.com/mib1185
+[@MindFreeze]: https://github.com/MindFreeze
+[@NickM-27]: https://github.com/NickM-27
+[@Petro31]: https://github.com/Petro31
+[@tetele]: https://github.com/tetele
+[blueprints for template entities]: /integrations/template/#using-blueprints
+[Image entities]: /integrations/image
+[Nautical miles]: https://en.wikipedia.org/wiki/Nautical_mile
+[time triggers]: /docs/automation/trigger/#time-trigger
+
+### Live logs
+
+Sometimes, if something does not work as expected, you might resort to a more technical
+tool for finding out what is going on: The logs.
+
+Previously, if you looked at the logs of, for example, an add-on or the Home
+Assistant Supervisor, you would only see the last 100 log lines. You would
+have had to refresh the page to see new log entries.
+
+Well, no more! As of this release, the logs are now **streaming live**! 🎉
+
+<p class='img no-shadow'><img class="no-shadow" alt="Screenshot of the imported cards section" src="/images/blog/2024-11/streaming-live-logs.gif"/>Screen recording demonstrating logs showing up as they happen.</p>
+
+And not just that, you can scroll back in time to see previous log items.
+That's a pretty cool improvement. 😎
+
+## Voice
+
+Last year, 2023, was the [Year of the Voice] for Home Assistant. And while this
+year isn't specifically dedicated to voice, everyone is still working hard
+towards the goal of letting users control their homes with their voice in
+their own language.
+
+As you might have heard through many community channels 🕵️‍♀️, we are working to
+make this a reality for everyone. We are hard at work getting our Home Assistant
+voice satellite hardware ready and available for selling and shipping! 🤗
+
+Stay tuned for more information on that soon!
+
+[Year of the Voice]: /blog/2022/12/20/year-of-voice/
+
+### Home Assistant intents improvements
+
+One of the things we are working on is the Home Assistant intents. This is a
+way for a voice assistant to understand the intention behind your spoken
+sentences. This is a very crucial part of a local voice assistant.
+
+In this release, we decided to align and combine Canadian French and French languages for the time being. Though we understand it is a unique dialect, this is about giving Canadian French users a lot more voice features.
+
+![Screenshot showing a few commands in Canadian French before and after this release](/images/blog/2024-11/canadian-french-on-assist.png)
+
+These intents are built and maintained by the community, and we are very
+grateful for their work. For example, [@piitaya] and [@jlpouffier] have made a
+great effort to lead the French language intents mentioned above.
+
+Nevertheless, we want to ensure everyone can use Home Assistant in their
+own language, **so we need your help**! Help the community by contributing to
+the intents for your language. You can find more information on how to do that
+in our [developer documentation].
+
+[@jlpouffier]: https://github.com/jlpouffier
+[@piitaya]: https://github.com/piitaya
+[developer documentation]: https://developers.home-assistant.io/docs/voice/intent-recognition/contributing
+
+### Join the Wake Word Collective
+
+Another essential part of voice is the Wake Word! And this is where **everyone**,
+no matter your skill level, can help out with just a minute of your time!
+
+Wake words are the words you say to wake up your voice assistant. For example,
+_"Hey Google"_ or _"Alexa"_. As we are building our own voice assistant with
+our own wake words, we need to train our models to recognize these words,
+regardless of your accent, language, gender, or age.
+
+So, get your whole home involved 🏠! Take a minute to help us out by recording your voice
+saying the wake word. It is super easy, and you can do it right from your
+browser or mobile, no need to install anything!
+
+[**Help us improve our wake words today! ❤️**](https://ohf-voice.github.io/wake-word-collective/)
+
+You can read more about the Wake Word Collective in our
+[dedicated blog post](/blog/2024/10/24/wake-word-collective/).
+
+## Need help? Join the community!
+
+Home Assistant has a great community of users who are all more than willing
+to help each other out. So, join us!
+
+Our very active [Discord chat server](/join-chat) is an excellent place to be
+at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
+
+Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
+to get it fixed! Or, check [our help page](/help) for guidance for more
+places you can go.
+
+Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
+to get the latest news about features, things happening in our community and
+other news about building an Open Home; straight into your inbox.
+
+## Backward-incompatible changes
+
+We do our best to avoid making changes to existing functionality that might
+unexpectedly impact your Home Assistant installation. Unfortunately, sometimes,
+it is inevitable.
+
+We always make sure to document these changes to make the transition as easy as
+possible for you. This release has the following backward-incompatible changes:
+
+{% details "A. O. Smith" %}
+
+A. O. Smith now provides the hot water status as a percentage rather than low,
+medium, or high. The hot water status entity has been updated accordingly.
+
+([@bdr99] - [#127678]) ([documentation](/integrations/aosmith))
+
+[@bdr99]: https://github.com/bdr99
+[#127678]: https://github.com/home-assistant/core/pull/127678
+
+{% enddetails %}
+
+{% details "Google Calendar" %}
+
+Google Calendar events that are declined are now omitted from the calendar.
+
+([@joelhawksley] - [#128900]) ([documentation](/integrations/google))
+
+[@joelhawksley]: https://github.com/joelhawksley
+[#128900]: https://github.com/home-assistant/core/pull/128900
+
+{% enddetails %}
+
+{% details "HomeKit" %}
+
+Historically, many integrations implemented doorbells as binary sensors with a
+device class of occupancy. This design was replaced with the new event entities,
+which use a purpose-built device class of doorbell.
+
+HomeKit will no longer automatically link binary sensors with device class
+occupancy as linked doorbell sensors. However, linked doorbell sensors can
+still be configured manually via YAML.
+
+([@bdraco] - [#127668]) ([documentation](/integrations/homekit))
+
+[@bdraco]: https://github.com/bdraco
+[#127668]: https://github.com/home-assistant/core/pull/127668
+
+{% enddetails %}
+
+{% details "Litter-Robot" %}
+
+Previously, Litter-Robot could have an off state. This has now changed to
+`docked`, as `off` isn’t a valid state for vacuum entities.
+
+([@gjohansson-ST] - [#128297]) ([documentation](/integrations/litterrobot))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#128297]: https://github.com/home-assistant/core/pull/128297
+
+{% enddetails %}
+
+{% details "Netatmo" %}
+
+The preset modes of the thermostat have been renamed in order to support
+translations `Schedule`, `Frost guard`, and `Manual` have been renamed to
+`schedule`, `frost_guard`, and `manual`.
+
+([@piitaya] - [#128890]) ([documentation](/integrations/netatmo))
+
+[@piitaya]: https://github.com/piitaya
+[#128890]: https://github.com/home-assistant/core/pull/128890
+
+{% enddetails %}
+
+{% details "Tibber" %}
+
+The `tibber.get_prices` action has been adjusted to return datetimes as strings
+instead of raw datetime objects.
+
+Automations or template sensors using this may need to be modified with an
+`as_datetime` filter. See our [templating documentation](/docs/configuration/templating/#time)
+for more information on using these filters.
+
+([@functionpointer] - [#123901]) ([documentation](/integrations/tibber))
+
+[@functionpointer]: https://github.com/functionpointer
+[#123901]: https://github.com/home-assistant/core/pull/123901
+
+{% enddetails %}
+
+{% details "Updates" %}
+
+State attributes of update entities have been changed:
+
+- The `in_progress` state attribute is now always a `bool`, never an integer.
+- A new state attribute `update_percentage` has been added. The
+  `update_percentage` is a number between 0-100 if an update is in progress
+  and the entity supports reporting progress, or `None` if an update is not
+  in progress or an update is in progress but the entity does not support
+  reporting progress.
+
+Scripts, automations, custom frontend components, etc., which consume the
+`in_progress` state attribute of update entities, need to be updated accordingly.
+
+([@emontnemery] - [#128877]) ([documentation](/integrations/update))
+
+[@emontnemery]: https://github.com/emontnemery
+[#128877]: https://github.com/home-assistant/core/pull/128877
+
+{% enddetails %}
+
+{% details "WMS WebControl pro" %}
+
+The open/closed state of awnings will be inverted so that the UI visualization
+and positioning match reality. This means open (100%) now refers to the awning
+being completely retracted, and closed (0%) now means the awning is fully
+expanded. This is not in line with industry terminology, but Home Assistant
+does not yet natively support awnings of type patio.
+
+([@mback2k] - [#128079]) ([documentation](/integrations/wmspro))
+
+[@mback2k]: https://github.com/mback2k
+[#128079]: https://github.com/home-assistant/core/pull/128079
+
+{% enddetails %}
+
+If you are a custom integration developer and want to learn about changes and
+new features available for your integration: Be sure to follow our
+[developer blog][devblog]. The following are the most notable for this release:
+
+- [Changes to the UnitOfConductivity enum](https://developers.home-assistant.io/blog/2024/10/08/unit-of-conductivity-changes)
+- [Changes to the update entity](https://developers.home-assistant.io/blog/2024/10/31/update-entity-changes)
+- [Deprecating state constants for cover](https://developers.home-assistant.io/blog/2024/10/08/state-constants-cover-deprecation)
+- [Extend deprecation period of hass.helpers](https://developers.home-assistant.io/blog/2024/10/09/extend-deprecation-hass-helpers)
+- [New alarm control panel state property and state enum](https://developers.home-assistant.io/blog/2024/10/22/new-alarm-state-property)
+- [New helpers and best practises for reauth and reconfigure flows](https://developers.home-assistant.io/blog/2024/10/21/reauth-reconfigure-helpers)
+- [Reauth and reconfigure flows need to be linked to a config entry](https://developers.home-assistant.io/blog/2024/11/04/reauth-reconfigure-entry-id/)
+- [The core config class has been moved](https://developers.home-assistant.io/blog/2024/10/31/core-config-moved)
+
+[devblog]: https://developers.home-assistant.io/blog/
+
+## All changes
+
+Of course, there is a lot more in this release. You can find a list of
+all changes made here: [Full changelog for Home Assistant Core 2024.11](/changelogs/core-2024.11)

source/connectzbt1/index.html

@@ -601,7 +601,7 @@ frontpage_image: /images/connectzbt1/connectzbt1-cover.jpg
           </a>
 
           <a
-            href="https://smarterhome.sk/en/zwave-pc-adapters/home-assistant-skyconnect-zigbee-and-thread-usb-controller-1403.html"
+            href="https://smarterhome.sk/sk/zwave-pc-adaptery/home-assistant-connect-zbt-1-zigbee-a-thread-usb-adapter-1646.html"
             target="_blank"
           >
             <div class="distributor">

source/green/index.html

@@ -2490,6 +2490,24 @@ dark_header: true
             </div>
           </a>
           
+          <a
+            href="https://dinamotech.it/products/home-assistant-green"
+            target="_blank"
+          >
+            <div class="distributor">
+              <div>
+                <div>🇮🇹</div>
+                <div>Dinamotech</div>
+                <div>Shipping from Italy</div>
+              </div>
+              <svg width="24" height="24" viewBox="0 0 24 24">
+                <path
+                  d="M8.59,16.58L13.17,12L8.59,7.41L10,6L16,12L10,18L8.59,16.58Z"
+                />
+              </svg>
+            </div>
+          </a>
+
           <a
             href="https://www.domadoo.fr/fr/box-domotique/7046-nabu-casa-box-domotique-home-assistant-green-0794677011758.html"
             target="_blank"
@@ -2707,7 +2725,7 @@ dark_header: true
           </a>
 
           <a
-            href="https://smarterhome.sk/controllers/home-assistant-green-smart-home-hub-1490.html"
+            href="https://smarterhome.sk/sk/centralne-jednotky/home-assistant-green-smart-home-hub-1490.html"
             target="_blank"
           >
             <div class="distributor">

source/integrations/index.html

@@ -120,7 +120,7 @@ regenerate: false
   <div class="grid__item four-fifths lap-one-whole palm-one-whole">
     <div class="component-search">
       <form onsubmit="event.preventDefault(); return false">
-        <input type="text" name="search" id="search" class="search" placeholder="Search integrations..." autofocus />
+        <input type="text" name="search" id="search" class="search text-input" placeholder="Search integrations..." autofocus />
       </form>
     </div>
     <div class="hass-option-cards" id="componentContainer"> </div>

source/more-info/statistics.markdown

@@ -3,6 +3,10 @@ title: "Expected data source not listed"
 description: "More information on if your expected data source is not listed."
 ---
 
-You're configuring a statistic but you couldn't find your source in the dropdown? That's caused by a bug in the integration providing the entity. Integrations need to configure their entities correctly so Home Assistant knows that we need to track statistics for it and how.
+You're configuring a statistic but you couldn't find your source in the dropdown?
+
+Check that it hasn't been excluded in the [Recorder](https://www.home-assistant.io/integrations/recorder/) configuration.
+
+Otherwise, It's caused by a bug in the integration providing the entity. Integrations need to configure their entities correctly so Home Assistant knows that we need to track statistics for it and how.
 
 Open an issue with the author of the integration and link them to https://developers.home-assistant.io/docs/core/entity/sensor#long-term-statistics.

source/privacy/index.markdown

@@ -48,7 +48,7 @@ Ads appearing on any of our websites may be delivered to users by advertising pa
 
 ## Companion Applications
 
-All information collected by the applications is sent directly to your hosted instance of Home Assistant. This includes, but is not limited to, sensor data and location data, which at times is sent while the application is in the background. At no point is this data logged or given to a 3rd party.
+All information collected by the applications is sent directly to your hosted instance of Home Assistant. This includes, but is not limited to, sensor, health, and location data, which at times is sent while the application is in the background. At no point is this data logged or given to a 3rd party.
 
 ## Privacy Policy Changes
 
@@ -58,6 +58,7 @@ Although most changes are likely to be minor, Home Assistant may change its Priv
 
 - October 19, 2017: Initial version
 - October 19, 2020: Add information about Companion Applications
+- October 30, 2024: Add health data to Companion Applications
 
 _This privacy policy has been adapted from the [Automattic privacy policy][Home Assistant] and is licensed [Creative Commons ShareAlike][cc]._
 

source/voice_control/android.markdown

@@ -11,17 +11,25 @@ related:
 
 ## Assist on Android phones
 
-Assist is available on Android phones and tablets using the [Home Assistant Companion App](https://companion.home-assistant.io/docs/getting_started/) for Android.
+Assist can be used on Android phones and tablets using the [Home Assistant Companion App](https://companion.home-assistant.io/docs/getting_started/).
 
 ### Prerequisites
 
+- [Home Assistant Companion App](https://companion.home-assistant.io/docs/getting_started/) installed
+- Have an Assistant set up: either [cloud](/voice_control/voice_remote_cloud_assistant/) (recommended, more performant) or [local](/voice_control/voice_remote_local_assistant/).
 - The devices you want to control with Assist are [exposed to Assist](/voice_control/voice_remote_expose_devices/)
 
-### Setting up Home Assistant Assist as default assistant app on an Android phone
+### Starting Assist in Home Assistant
+
+1. On your phone, open Home Assistant.
+2. In the top-right corner, select the three-dots menu and select **Assist**.
+3. [Give a command](/voice_control/custom_sentences/).
+
+### Setting up Home Assistant Assist as default assistant app
 
 This section was written using an Android 13. Depending on your flavor of Android, the exact steps may vary.
 
-To define Home Assistant Assist as default assistant app, follow these steps:
+To define Home Assistant Assist as default assistant app on your Android phone, follow these steps:
 
 1. On the Android phone, go to **Settings** > **Apps** > **Default apps**.
 2. Under **Digital assistant app**, select **Default digital assistant app**.
@@ -76,9 +84,11 @@ Assist is available on Wear OS using the [Home Assistant Companion App](https://
 
 The way how Assist can be set up on your phone may differ depending on your version of Wear OS.
 
-1. After [installing the companion app](https://companion.home-assistant.io/docs/getting_started/) and connecting it to your Home Assistant, Assist might appear automatically on the **Apps screen**.
+1. After [installing the companion app](https://companion.home-assistant.io/docs/getting_started/) on your watch and connecting it to your Home Assistant, Assist appears automatically on the **Apps screen**.
-2. If it does not, visit your watch companion app or the Wear OS app and select **Add tile** inside the **Tiles** area.
+    
-3. Tap the **Assist** tile to add it to your watch:
+    ![Assist app](/images/assist/wearos_assist_app.png)
+
+2. To add an Assist tile, in the Wear OS app, go to the **Tiles** area, select **Add tile** > **Assist**.
     
     ![Conversation tile](/images/assist/android_tile.png)
 
@@ -94,10 +104,10 @@ The way how Assist can be set up on your phone may differ depending on your vers
    
      ![Assist complication](/images/assist/android_watch_5.png)
 
-
 ### Using Assist on Wear OS
 
-1. On your watch, swipe left until the **Assist** button is visible.
+1. On your watch, open Assist. 
+   - For example, swipe left until the **Assist** button is visible.
    
     ![Assist button](/images/assist/android_watch_1.png)
 
@@ -114,10 +124,9 @@ The way how Assist can be set up on your phone may differ depending on your vers
     
    ![List of assistants](/images/assist/android_watch_6.png)
 
-
 ### Setting up Home Assistant Assist as default assistant app on a Wear OS watch
 
-This procedure was written using Wear OS version 3.5. The exact steps may vary depending on the watch and software version.
+This procedure was written using Wear OS version 4.0. The exact steps may vary depending on the watch and software version.
 
 To define Home Assistant Assist as default assistant app, follow these steps:
 

source/voice_control/builtin_sentences.markdown

@@ -1,5 +1,5 @@
 ---
-title: "Assist - default sentences"
+title: Assist - sentences starter kit
 related:
   - docs: /voice_control/aliases/
     title: Create aliases
@@ -19,99 +19,161 @@ related:
 
 Home Assistant comes with [built-in sentences](https://github.com/home-assistant/intents/tree/main/sentences) contributed by the community for [dozens of languages](https://developers.home-assistant.io/docs/voice/intent-recognition/supported-languages).
 
-These sentences allow you, for example, to:
+## Prerequisites
 
-- **Turn entities on and off**
+- The entities you want to control with Assist must be [exposed to Assist](/voice_control/voice_remote_expose_devices/).
-    - *"turn on the living room light"*
+- When using the names of entities or areas, make sure to use them exactly as they are defined in Home Assistant, or, [create an alias](/voice_control/aliases/).
-    - *"turn off ceiling fan"*
-    - *"turn on the TV"*
-    - *"lock all the doors"*
-    - *"open the main door"*
-- **Open, close covers, or ask about their state**
-    - *"Close the garage door"*
-    - *"Open kitchen window"*
-    - *"Which curtains are closed"*
-    - *"Set bedroom curtain to 50%"*
-- **Set the brightness and color of lights**
-    - *"Change kitchen lights brightness to 50%"*
-    - *"Set bed light to green"*
-- **Ask about the weather**
-    - *"What is the weather"*
-    - Struggling with this one? Check the [troubleshooting section](/voice_control/troubleshooting/).
-- **Add items to a list**
-    - *"Add bread to my shopping list"*
-    - *"Add decorating christmas tree to my december chores list"*
-- **Get information about a state**
-  - *"What is the amount of energy from solar production?"*
-  - *"what is the heat pump co2 sensor's co2 level?"*
-  - *"what is the battery level of my phone?"*
-- **Run a script**
-    - *"Run stealth mode script"*
-- **Activate a scene**
-    - *"Activate dinner scene"*
-    - *"Turn kitchen dinner scene on"*
-- **Inquire about people (that have device tracking activated in Home Assistant)**
-    - *"How many people are in the kitchen"*
-    - *"Who is in the garage"*
-    - *"Where is Anne"*
-- **Control the media player**
-    - *"next item on TV"*
-    - *"skip song on the TV"*
-    - *"skip track on the TV"*
-    - *"skip to the next song on the TV"*
-    - *"pause TV"*
-    - *"TV pause"*
-    - *"unpause TV"*
-    - *"TV unpause"*
-    - *"resume TV"*
-    - *"set TV volume to 90 percent"*
-    - *"change the TV volume to 90"*
-    - *"turn TV volume down to 90 percent"*
-- **Control the vacuum**
-    - *"return rover to base"*
-    - *"start rover"*
-- **Use timers**
-  - *“Create a timer for 5 minutes”*
-  - *“Create a 15-minute timer for pizza”*
-  - *“Cancel my timer”*
-  - *“Pause my timer”*
-  - *“Resume my timer”*
-  - *“Add 2 minutes to my 5-minute timer”*
-  - *“Remove 3 minutes from my pizza timer”*
 
-  <p class='img'><lite-youtube videoid="v3mNdTsX4J0" videotitle="Voice timers with countdown text and loading bar"></lite-youtube>Timers running on an S3-Box-3B, with countdown text and a loading bar!</p>
+## Device control
+
+### Turning entities on and off
+
+- *turn on the living room light*
+- *turn off ceiling fan*
+- *turn on the TV*
+- *lock all the doors*
+- *open the main door*
+
+### Lights
+
+- *Change kitchen lights brightness to 50%*
+- *Set bed light to green*
+- *set bed light brightness to 50%*
+- *set living room brightness to 50%*
+- *set brightness to 50%*
+  - Uses area of voice satellite
+- *set kitchen lights to red*
+- *set lights to red*
+  - Uses area of voice satellite
+- *turn on the lights in the living room*
+
+### Covers
+
+- *Close the garage door*
+- *Open kitchen window*
+- *Which curtains are closed*
+- *Set bedroom curtain to 50%*
+
+### Scenes and scripts
+
+- *Run stealth mode script*
+- *Activate dinner scene*
+- *Turn kitchen dinner scene on*
+
+### Media player
+
+- *next item on TV*
+- *next track*
+- *next track in office*
+- *previous track*
+- *previous track in office*
+- *skip song on the TV*
+- *skip track on the TV*
+- *skip to the next song on the TV*
+- *pause|resume*
+  - pauses or resumes music on voice satellite or in current area
+- *pause|resume "area" music*
+  - pauses or resumes music in area
+- *pause|resume "entity"*
+  - pauses or resumes music on media player
+- *unpause TV*
+- *TV unpause*
+- *set TV volume to 90 percent*
+- *change the TV volume to 90*
+- *turn TV volume down to 90 percent*
+
+### Vacuum
+
+- *return rover to base*
+- *start rover*
+
+### Lists
+
+- *Add bread to my shopping list*
+- *Add decorating christmas tree to my december chores list*
+  - needs a todo list name "december chores"
+- *add clean out garage to weekend list*
+  - needs a todo list named "Weekend"
+
+## Date and time
+
+- *what time is it?*
+- *what's the date?*
+
+## Timers
+
+### Starting
+
+- *set a timer for 5 minutes*
+- *5 minute timer*
+- *set a 20 minute timer for pizza*
+
+### Cancelling
+
+- *cancel timer*
+  - can't cancel multiple timers yet
+- *cancel 5 minute timer*
+- *cancel pizza timer*
+- *cancel kitchen timer*
+  - Must have been set by a voice satellite in the kitchen
+
+### Adding/Removing Time
+
+- *add 5 minutes to pizza timer*
+- *add 5 minutes to kitchen timer*
+- *remove 1 minute from timer*
+- *remove 1 minute from 5 minute timer*
+
+### Status
+
+- *timer status*
+- *how much time is left on pizza timer?*
+- *how much time is left on kitchen timer?*
+- *how much time is left on 5 minute timer?*
+
+<p class='img'><lite-youtube videoid="v3mNdTsX4J0" videotitle="Voice timers with countdown text and loading bar"></lite-youtube>Timers running on an S3-Box-3B, with countdown text and a loading bar!</p>
 
 To learn how to set this up, refer to the [ESP32-S3-Box-3B tutorial](/voice_control/s3_box_voice_assistant/).
 
-- **Combine timers and device control to add a delay**
+### Combining timers and device control to add a delay
+
 Unlike regular voice timers, delayed commands cannot be canceled or modified.
-  - *“Turn off the lights in the living room in 5 minutes”*
-  - *“Pause TV in 10 minutes”*
-  - *“Open the blinds in 5 minutes”*
 
-- **Abort wake word**
+- *Turn off the lights in the living room in 5 minutes*
-    - *"Nevermind"*: If you triggered the wake word by mistake and want to stop Home Assistant from listening
+- *Pause TV in 10 minutes*
+- *Open the blinds in 5 minutes*
 
-The sentences only work, if the {% term entities %} are available and are named exactly the way you call them. Check the [troubleshooting section](/voice_control/troubleshooting/) to see common errors when asking for the weather forecast.
+## Questions
 
-In addition to individual {% term entities %}, commands can target **areas**:
+### Get information about a state
 
-- *"turn on all lights in the living room"*
+- *What is the amount of energy from solar production?*
-- *"open windows in the kitchen"*
+- *what is the heat pump co2 sensor's co2 level?*
-- *"change office brightness to 50%"*
+- *what is the battery level of my phone?*
-- *"set bedroom lights to green"*
 
-Entity [aliases](/voice_control/aliases) are also matched so that multiple names can be used, even in different languages.
+### Ask about the weather
 
-You can extend the [built-in sentences](https://github.com/home-assistant/intents/tree/main/sentences) or [add your own](/voice_control/custom_sentences) to trigger any action in Home Assistant.
+- *What is the weather*
+- Struggling with this one? Check the [troubleshooting section](/voice_control/troubleshooting/).
 
-## View existing sentences
+### Ask about people
+
+(that have device tracking activated in Home Assistant)
+
+- *How many people are in the kitchen*
+- *Who is in the garage*
+- *Where is Anne*
+
+## Aborting
+
+- *Nevermind*: If you triggered the wake word by mistake and want to stop Home Assistant from listening
+
+## Troubleshooting
 
 The list of supported sentences is constantly being updated for each language. There are so many possible sentences that they cannot be all listed here. To find out what works in your language, follow these steps.
 
-**Note**: If the voice assistant doesn't understand you, you may need to rephrase your sentence a bit. Or check if the {% term entity %} or {% term area %} name is correct for your environment.
+1. If the voice assistant doesn't understand you, you may need to rephrase your sentence a bit. Or check if the {% term entity %} or {% term area %} name is correct for your environment.
-
+2. Take a look at the test sentences:
-1. Take a look at the test sentences:
     - On GitHub, in the [tests](https://github.com/home-assistant/intents/tree/main/tests) folder, open the subfolder for your language.
     - Look through the test files to see the example sentences that have been tested.
     - The second part of the file name shows the {% term intent %}, the first part shows the {% term domain %}. For some {% term domains %}, such as covers, fans, and light, there are specific sentences.
@@ -124,7 +186,7 @@ The list of supported sentences is constantly being updated for each language. T
 
         ![Example of a set of test sentences](/images/assist/assist-test-file-light-turn-on.png)
 
-2. View the sentence definition for the tests:
+3. View the sentence definition for the tests:
     - On GitHub, in the [sentences](https://github.com/home-assistant/intents/tree/main/sentences) folder, open the subfolder for your language.
     - Open the file of interest.
 
@@ -132,8 +194,12 @@ The list of supported sentences is constantly being updated for each language. T
 
         - () mean alternative elements.
         - [] mean optional elements.
-        - <> mean an expansion rule. To view these rules, search for `expansion_rules` in the [_common.yaml](https://github.com/home-assistant/intents/blob/main/sentences/en/_common.yaml) file.
+        - &lt;&gt; mean an expansion rule. To view these rules, search for `expansion_rules` in the [_common.yaml](https://github.com/home-assistant/intents/blob/main/sentences/en/_common.yaml) file.
         - The syntax is explained in detail in the [template sentence syntax documentation](https://developers.home-assistant.io/docs/voice/intent-recognition/template-sentence-syntax/).
-3. View the [sentence definition](https://github.com/home-assistant/intents/tree/main/sentences) for your language.
+4. View the [sentence definition](https://github.com/home-assistant/intents/tree/main/sentences) for your language.
-4. View the [response definition](https://github.com/home-assistant/intents/tree/main/responses)
+5. View the [response definition](https://github.com/home-assistant/intents/tree/main/responses)
+6. If there are issues when asking for the weather forecast, check the [troubleshooting section](/voice_control/troubleshooting/) to see common errors.
 
+## More sentences
+
+You can extend the [built-in sentences](https://github.com/home-assistant/intents/tree/main/sentences) or [add your own](/voice_control/custom_sentences) to trigger any action in Home Assistant.

source/voice_control/custom_sentences.markdown

@@ -148,7 +148,7 @@ As mentioned above, you can then use the `intent_script` integration to implemen
 # Example configuration.yaml
 intent_script:
   SetVolume:
-    actions:
+    action:
       service: "media_player.volume_set"
       data:
         entity_id: "{{ media_player }}"

source/voice_control/index.markdown

@@ -16,7 +16,7 @@ related:
   - docs: /voice_control/create_wake_word/
     title: Create your own wake words
   - docs: /voice_control/builtin_sentences
-    title: Built-in sentences
+    title: Sentences starter kit
   - url: https://www.nabucasa.com/config/
     title: Home Assistant Cloud
 ---