2024.11: Beta release notes (#35429)

2025-07-15 21:36:52 +00:00 · 2024-10-30 18:37:21 +01:00 · 2024-10-30 18:37:21 +01:00 · fb7c39b7e3
commit fb7c39b7e3
parent 828a66bd80 ae7212e209
50 changed files with 4140 additions and 219 deletions
--- a/9
+++ b/9
@ -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
@ -706,7 +706,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
@ -795,11 +795,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
@ -812,7 +811,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
--- a/2
+++ b/2
@ -10,6 +10,8 @@ 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.4'
  gem 'rubocop', '1.67.0'
  gem 'ruby-lsp', '0.20.1'
  gem 'rackup', '2.1.0'
--- a/Gemfile.lock
+++ b/Gemfile.lock
@ -66,7 +66,7 @@ GEM
      nokogiri (~> 1.12)
    jekyll-watch (2.2.1)
      listen (~> 3.0)
-    json (2.7.3)
+    json (2.7.4)
    kramdown (2.4.0)
      rexml
    kramdown-parser-gfm (1.1.0)
@ -123,7 +123,7 @@ 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.33.0)
      parser (>= 3.3.1.0)
    ruby-lsp (0.20.1)
      language_server-protocol (~> 3.17.0)
@ -134,9 +134,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.5-arm64-darwin)
      google-protobuf (~> 4.28)
-    sass-embedded (1.80.4-x86_64-linux-gnu)
+    sass-embedded (1.80.5-x86_64-linux-gnu)
      google-protobuf (~> 4.28)
    sass-globbing (1.1.5)
      sass (>= 3.1)
@ -150,7 +150,7 @@ GEM
      rack-protection (= 4.0.0)
      rack-session (>= 2.0.0, < 3)
      tilt (~> 2.0)
-    sorbet-runtime (0.5.11615)
+    sorbet-runtime (0.5.11625)
    stringex (2.8.6)
    terminal-table (3.0.2)
      unicode-display_width (>= 1.1.1, < 3)
@ -178,6 +178,7 @@ DEPENDENCIES
  rake (= 13.2.1)
  rubocop (= 1.67.0)
  ruby-lsp (= 0.20.1)
+  sass-embedded (= 1.80.4)
  sass-globbing (= 1.1.5)
  sassc (= 2.1.0)
  sinatra (= 4.0.0)
--- a/_config.yml
+++ b/_config.yml
@ -107,9 +107,9 @@ social:

 # Home Assistant release details
 current_major_version: 2024
-current_minor_version: 10
-current_patch_version: 4
-date_released: 2024-10-25
+current_minor_version: 11
+current_patch_version: 0
+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.
--- a/sass/homeassistant/_overrides.scss
+++ b/sass/homeassistant/_overrides.scss
@ -888,6 +888,35 @@ dt:hover a.title-link {
  }
 }

+.hero-github-badge .desktop {
+  display: none;
+  max-width: 658px;
+  width: 100%;
+}
+
+.hero-github-badge .mobile {
+  display: block;
+  max-width: 420px;
+  width: 100%;
+  margin-bottom: 2rem;
+}
+
+// after 768px, show desktop, hide mobile
+@media only screen and (min-width: 1025px) {
+  .hero-github-badge .mobile {
+    display: none;
+    max-width: 385px;
+  }
+
+  .hero-github-badge .desktop {
+    display: block;
+  }
+}
+
+.hero-buttons {
+  margin-bottom: 0;
+}
+
 .hero-buttons a {
  margin: 0 30px 10px 0;

@ -896,7 +925,6 @@ dt:hover a.title-link {
  }
 }

-
 // Article formatting

 article.post,
@ -1362,13 +1390,13 @@ a.my {
 // Prevent headings from disappearing behind the site header when linked to
 h1, h2, h3, h4, h5, h6 {
  position: relative;
+  word-wrap: break-word;
 }

-:target {
-  display: block;
-  position: absolute;
-  top: -100px;
-  visibility: hidden;
+:target, .title-link {
+  display: inline-block;
+  position: relative;
+  scroll-margin-top: 140px;
 }

 .site-header {
--- a/sass/homeassistant/homepage/_hero_unit.scss
+++ b/sass/homeassistant/homepage/_hero_unit.scss
@ -14,7 +14,7 @@
  max-height: 1080px;
  height: 100vh;
  align-content: center;
-  min-height: 720px;
+  min-height: 840px;
  // scroll-snap-align: start;
  color: $white;

@ -86,11 +86,11 @@
    // animation-iteration-count: infinite;
    // animation-direction: alternate;

-    @media only screen and (max-height: 720px) {
+    @media only screen and (max-height: 840px) {
      border-bottom: 0;
      margin-bottom: -8px;
      border-radius: 48px 48px 0 0;
-      height: 640px;
+      height: 750px;

    }

@ -126,6 +126,7 @@

@media only screen and (max-width: 760px) {
  .hero {
+    min-height: 940px;
    .flex {
      flex-direction: column;
    }
--- a/source/_dashboards/entities.markdown
+++ b/source/_dashboards/entities.markdown
@ -115,6 +115,10 @@ double_tap_action:
  required: false
  description: Action taken on row double tap. See [action documentation](/dashboards/actions/#double-tap-action).
  type: map
+confirmation:
+  required: false
+  description: For entities that display a button element in the row (for example, button, lock, script), this option adds a confirmation dialog to the press of the button. See [options for confirmation](/dashboards/actions/#options-for-confirmation) for configuration options.
+  type: map
 {% endconfiguration %}

 ## Special row elements
--- a/source/_dashboards/map.markdown
+++ b/source/_dashboards/map.markdown
@ -58,11 +58,11 @@ type:
  type: string
 entities:
  required: true
-  description: List of entity IDs or `entity` objects (see below). Either this or the `geo_location_sources` configuration option is required.
+  description: List of entity IDs or `entity` objects (see [below](#options-for-entities)). Either this or the `geo_location_sources` configuration option is required.
  type: list
 geo_location_sources:
  required: true
-  description: List of geolocation sources. All current entities with that source will be displayed on the map. See [Geolocation](/integrations/geo_location/) platform for valid sources. Set to `all` to use all available sources. Either this or the `entities` configuration option is required.
+  description: List of geolocation sources or `source` objects (see [below](#options-for-geolocation-sources)). All current entities with that source will be displayed on the map. See [Geolocation](/integrations/geo_location/) platform for valid sources. Set to `all` to use all available sources. Either this or the `entities` configuration option is required.
  type: list
 auto_fit:
  required: false
@ -134,6 +134,22 @@ focus:
  type: boolean
 {% endconfiguration %}

+## Options for geolocation sources:
+
+If you define geolocation sources as objects instead of strings (by adding `source:` before the ID), you can add more customization and configuration.
+
+{% configuration %}
+source:
+  required: true
+  description: Name of a geolocation source, or `all`.
+  type: string
+focus:
+  required: false
+  default: true
+  description: When set to `false`, the entities of this source will not be considered for determining the default zoom or fit of the map.
+  type: boolean
+{% endconfiguration %}
+
 ## Examples

 ```yaml
@ -150,6 +166,8 @@ entities:
 type: map
 geo_location_sources:
  - nsw_rural_fire_service_feed
+  - source: gdacs
+    focus: false
 entities:
  - zone.home
 ```
--- a/source/_includes/asides/docs_sitemap.html
+++ b/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>
--- a/source/_includes/common-tasks/remove_device_service.md
+++ b/source/_includes/common-tasks/remove_device_service.md
@ -0,0 +1,13 @@
+## Removing an integration instance
+
+If you no longer want to use a device or service in Home Assistant, you can remove the integration instance including the device or service with all its entities.
+
+The following steps describe the general steps needed to remove an integration instance. Depending on the integration, additional steps can be needed, such as resetting the device or to delete credentials. Refer to the integration documentation to see if additional steps are needed.
+
+### To remove an integration instance from Home Assistant
+
+1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the integration card.
+2. From the list of devices, select the integration instance you want to remove.
+3. Next to the entry, select the three-dot menu. Then, select **Delete**.
+
+   ![Screenshot showing how to remove an integration instance](/images/organizing/integration_instance_delete.png)
--- a/source/_includes/custom/welcome.html
+++ b/source/_includes/custom/welcome.html
@ -19,3 +19,15 @@
  <a href='https://demo.home-assistant.io' target='_blank'>View live demos</a>
  <a href='/integrations/'>Browse {{ tot | minus: 1 | divided_by: 100 | round | times: 100 }}+ integrations</a>
 </p>
+<a href="https://github.blog/news-insights/octoverse/octoverse-2024/#the-state-of-open-source" target="_blank" class="hero-github-badge">
+  <img
+    src="/images/github-top-project-2024-mobile.png"
+    class="mobile"
+    alt="GitHub's top open source project by contributors in 2024"
+    >
+  <img
+    src="/images/github-top-project-2024-desktop.png"
+    class="desktop"
+    alt="GitHub's top open source project by contributors in 2024"
+    >
+</a>
--- a/source/_integrations/airgradient.markdown
+++ b/source/_integrations/airgradient.markdown
@ -14,6 +14,7 @@ ha_codeowners:
 ha_domain: airgradient
 ha_platforms:
  - button
+  - diagnostics
  - number
  - select
  - sensor
--- a/source/_integrations/blebox.markdown
+++ b/source/_integrations/blebox.markdown
@ -397,6 +397,14 @@ This integration adds the Blebox device as a sensor entity to Home Assistant.

 - Periodic read of current wind speed

+### luxSensor
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of illuminance (unit: lx)
+
 ------

 ## "BleBox inside" controllers
--- a/source/_integrations/cambridge_audio.markdown
+++ b/source/_integrations/cambridge_audio.markdown
@ -11,6 +11,7 @@ ha_platforms:
  - diagnostics
  - media_player
  - select
+  - switch
 ha_codeowners:
  - '@noahhusby'
 ha_config_flow: true
@ -56,7 +57,8 @@ The integration provides a few entities to configure the device settings. The fo

 - Display brightness
 - Pre-Amp
- Early Update
+- Early update
+- Audio output (Speaker select)

 ## Playing media

--- a/source/_integrations/comelit.markdown
+++ b/source/_integrations/comelit.markdown
@ -20,6 +20,7 @@ ha_platforms:
  - binary_sensor
  - climate
  - cover
+  - diagnostics
  - humidifier
  - light
  - sensor
--- a/source/_integrations/dsmr_reader.markdown
+++ b/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>`.
--- a/source/_integrations/govee_light_local.markdown
+++ b/source/_integrations/govee_light_local.markdown
@ -44,6 +44,8 @@ H6087,
 H6088,
 H608A,
 H608B,
+H608D,
+H60A1,
 H610A,
 H610B,
 H6110,
@ -79,6 +81,7 @@ H61A8,
 H61B2,
 H61B5,
 H61BA,
+H61BC,
 H61BE,
 H61C3,
 H61C5,
@ -86,6 +89,7 @@ H61D3,
 H61D5,
 H61E0,
 H61E1,
+H61F5,
 H7012,
 H7013,
 H7020,
@ -104,14 +108,19 @@ H7055,
 H705A,
 H705B,
 H705C,
+H705E,
 H7060,
 H7061,
 H7062,
 H7063,
 H7065,
 H7066,
+H706A,
+H706B,
+H706C,
 H7075,
 H70A1,
 H70B1,
 H70C1,
-H70C2
+H70C2
+H70C2
--- a/source/_integrations/habitica.markdown
+++ b/source/_integrations/habitica.markdown
@ -4,6 +4,7 @@ description: Instructions on enabling Habitica support for your Home Assistant
 ha_category:
  - To-do list
  - Sensor
+  - Calendar
 ha_release: 0.78
 ha_iot_class: Cloud Polling
 ha_domain: habitica
@ -12,6 +13,7 @@ ha_platforms:
  - sensor
  - switch
  - todo
+  - calendar
 ha_codeowners:
  - '@ASMfreaK'
  - '@leikoilja'
@ -64,6 +66,11 @@ The following Habitica tasks are available as to-do lists in Home Assistant. You
 - **To-Do's:** Displays a comprehensive list of active and completed to-dos. Each to-do includes its due date if applicable, allowing you to check them off, edit them, delete them, and create new to-dos seamlessly.
 - **Dailies:** Shows the daily tasks that need to be completed today or in the future. Tasks completed yesterday can still be marked off as "yesterdailies" until a new day starts.

+## Calendars
+
+- **To-Do calendar:** Lists the due dates for all active to-do tasks. Each event on this calendar represents a to-do item that has a set due date, making it easy to track upcoming deadlines and plan accordingly.
+- **Dailies calendar:** Displays all daily tasks that are scheduled for today and are still active. It also shows all tasks scheduled for future dates, helping you stay organized and track upcoming routines. The calendar sensor will be active if there are unfinished tasks for today and display the next due daily (based on sort order if there are multiple tasks due for that day).
+
 ## Button controls

 - **Start my day:** Initiates daily routine actions in Habitica, including resetting your dailies, deal damage from unfinished dailies and quest bosses, habits adjustment, buff expiration, and mana regeneration based on completed dailies.
--- a/source/_integrations/husqvarna_automower_ble.markdown
+++ b/source/_integrations/husqvarna_automower_ble.markdown
@ -0,0 +1,33 @@
+---
+title: Husqvarna Automower BLE
+description: Instructions on how to integrate Husqvarna Automower BLE lawn mowers into Home Assistant.
+ha_category:
+  - Lawn Mower
+ha_release: 2024.11
+ha_iot_class: Local Polling
+ha_config_flow: true
+ha_codeowners:
+  - '@alistair23'
+ha_platforms:
+  - lawn_mower
+ha_integration_type: integration
+ha_domain: husqvarna_automower_ble
+---
+
+The Husqvarna Automower BLE integration provides connectivity with Husqvarna Automowers lawn mowers via a local Bluetooth connection. This allows connecting and controlling an Automower without any accounts, cloud, or network connection.
+
+The integration is based on [AutoMower-BLE](https://github.com/alistair23/AutoMower-BLE), an unofficial reverse engineered Husqvarna Automower Connect BLE library.
+
+There is currently support for the following device types within Home Assistant:
+
+- Lawn Mower
+
+### Prerequisites
+
+1. Setup a [Bluetooth controller](https://www.home-assistant.io/integrations/bluetooth/). An ESPHome Bluetooth proxy works well and allows locating a device close to the mower.
+2. Enter the pairing mode on the mower. Different models will do this in different ways. For the 305, for example, the mower will enter pairing mode for the first 3 minutes after powering on. Ensure the mower is in pairing mode when adding the integration. This only needs to be done once per BLE controller (so changing the ESPHome device will require a repair).
+3. When adding the integration to Home Assistant, you will need to enter the mower BLE Mac address. You can find this in the ESPHome logs, on an Android phone, or by some other means.
+
+Pairing can take a few goes. Even when using the official Android application, it can be tricky to get the first pair to succeed. If you are having issues, reboot the mower and try again.
+
+{% include integrations/config_flow.md %}
--- a/source/_integrations/lamarzocco.markdown
+++ b/source/_integrations/lamarzocco.markdown
@ -76,6 +76,7 @@ Host:
 | Prebrew on time | Time prebrew wets the puck | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
 | Prebrew off time | Time prebrew waits before turning on the pump | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
 | Preinfusion time | Duration of preinfusion | Linea Micra, Linea Mini, GS3 AV | GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default |
+| Smart standby time | Time until the machine will automatically stand by (if enabled) | all | - |


 ## Switches
@ -84,6 +85,7 @@ Host:
 |-------------|-------------| ---------------------- |
 | Main        | Allows to turn machines on-/off | all |
 | Steam boiler | Allows to enable/disable the steam boiler | all |
+| Smart standby enabled | Whether smart standby is on (machine will automatically stand by after given time) | all |

 ## Binary sensors

@ -116,6 +118,7 @@ Host:
 |-------------|-------------| ------------------------| ---------------------- |
 | Prebrew/-infusion mode | Whether to use prebrew, preinfusion, or neither | Disabled, Prebrew, Preinfusion | Linea Micra, Linea Mini, GS3 AV |
 | Steam level | The level your steam boiler should run at | 1,2,3 | Linea Micra |
+| Smart standby mode | The smart standby mode, that decides from which events the timer to standby will run. | Last brewing, Power on | all |

 ## Supported devices

--- a/source/_integrations/lcn.markdown
+++ b/source/_integrations/lcn.markdown
@ -31,7 +31,7 @@ The **LCN** {% term integration %} for Home Assistant allows you to connect to [

 ## Prerequisites

- The integration requires one unused license of the coupling software LCN-PCHK (version >2.8) and an LCN hardware coupler. 
+- The integration requires one unused license of the coupling software LCN-PCHK (version >2.8) and an LCN hardware coupler.
 - Alternatively, an LCN-VISU or LCN-PKE coupler can be used which offers at least two PCHK licenses.
 With this setup, sending and receiving commands to and from LCN modules is possible.

@ -75,8 +75,6 @@ The detailed documentation for the LCN frontend panel can be found [here](https:
 The `lcn` binary sensor platform allows the monitoring of the following [LCN](https://www.lcn.eu/) binary data sources:

 - Binary hardware sensors
- Lock state of regulator setpoints
- Lock state of keys

 The binary sensor can be used in automation scripts or in conjunction with `template` platforms.

@ -141,6 +139,8 @@ The `lcn` switch platform allows the control of the following [LCN](https://www.

 - Output ports
 - Relays
+- Lock state of regulators
+- Lock state of keys

 ## Additional features

--- a/source/_integrations/lektrico.markdown
+++ b/source/_integrations/lektrico.markdown
@ -15,6 +15,7 @@ ha_platforms:
  - number
  - select
  - sensor
+  - switch
 ha_integration_type: device
 ---

--- a/source/_integrations/lg_thinq.markdown
+++ b/source/_integrations/lg_thinq.markdown
@ -0,0 +1,285 @@
+---
+title: LG ThinQ
+description: Setup for LG ThinQ Integration.
+ha_category:
+  - Hub
+ha_release: "2024.11"
+ha_iot_class: Cloud Push
+ha_code_owners:
+  - '@LG-ThinQ-Integration'
+ha_config_flow: true
+ha_domain: lg_thinq
+ha_platforms:
+  - switch
+  - binary_sensor
+  - climate
+  - event
+  - fan
+  - number
+  - sensor
+  - select
+  - vacuum
+ha_integration_type: integration
+---
+
+The **LG ThinQ** integration allows you to connect LG ThinQ devices to Home Assistant. The features of this integration include:
+
+- Control LG appliances as Home Assistant entities through the [LG ThinQ Connect API](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/overview/).
+
+## Prerequisites
+
+- This feature works via LG ThinQ cloud. Therefore, an internet connection is required.
+- A [personal access token](https://connect-pat.lgthinq.com) to use the [LG ThinQ Connect API](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/overview/).
+
+### Personal Access Token (PAT)
+
+1. Access the **[personal access token](https://connect-pat.lgthinq.com)** page (requires an LG ThinQ account).
+2. Select **ADD NEW TOKEN**.
+3. Enter a new token name and select the following authorized scopes:
+    - **Permission to view all devices**
+    - **Permission to view all device statuses**
+    - **All device control rights**
+    - **All device event subscription rights**
+    - **All device push notification permissions**
+4. Select **CREATE TOKEN**.
+5. Once all the steps are completed, you will see that a **PAT** has been generated.
+
+{% include integrations/config_flow.md %}
+
+1. Enter the information to use LG ThinQ Connect API:
+   - The **Token Value** obtained through the PAT issuance process. (Required)
+   - The entry name.
+2. Choose the region (country).
+
+## Supported Devices
+
+### Appliance
+
+Support LG Appliances as follows:
+
+- [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/)
+- [Air Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-purifier/)
+- [Air Purifier Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Air-Purifier-Fan/)
+- [Ceiling Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/ceiling-fan/)
+- [Cooktop](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/cooktop/)
+- [Dehumidifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dehumidifier/)
+- [Dishwasher](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dish-washer/)
+- [Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dryer/)
+- [Home Brew](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/home-brew/)
+- [Hood](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/hood/)
+- [Humidifier](https://thinq.developer.lge.com/ko/cloud/docs/thinq-connect/device-profile/humidifier/)
+- [Kimchi Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/kimchi-refrigerator/)
+- [Microwave Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/microwave-oven/)
+- [Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/oven/)
+- [Plant Cultivator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/plant-cultivator/)
+- [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/)
+- [Robot Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/robot-cleaner/)
+- [Stick Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Stick-Cleaner/)
+- [Styler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/styler/)
+- [System Boiler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/system-boiler/)
+- [Washcombo Main](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)
+- [Washcombo Mini](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)
+- [Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)
+- [Washtower](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Single-Unit/)
+- [Washtower Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Dryer/)
+- [Washtower Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Washer/)
+- [Water Heater](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/water-heater/)
+- [Water Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/water-purifier/)
+- [Wine Cellar](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/wine-cellar/)
+
+## Platforms
+
+LG ThinQ represents devices as a set of [profiles](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/). And these are mapped to entities in Home Assistant.
+
+A list of all Entity Platforms provided by LG ThinQ Integration:
+
+- [Binary sensor](#binary-sensor)
+- [Climate](#climate)
+- [Event](#event)
+- [Fan](#fan)
+- [Number](#number)
+- [Select](#select)
+- [Sensor](#sensor)
+- [Switch](#switch)
+- [Vacuum](#vacuum)
+
+### Binary sensor
+
+A read-only property which has only two states that can be toggled is represented as a binary sensor platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Cooktop](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Cooktop/)<br> | Remote start |
+| [Dish Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dish-washer/) | Chime sound<br>Clean indicator light<br>Door<br>Machine clean reminder<br>Remote start<br>Rinse refill needed |
+| [Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Dryer/)<br> | Remote start |
+| [Hood](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Hood/) | Power |
+| [Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Oven/) | Remote start |
+| [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/) | Door<br>Eco friendly<br>Power saving mode<br>Sabbath |
+| [Kimchi Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Kimchi-Refrigerator/) | Fresh air filter |
+| [Styler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/styler/) | Remote start |
+| [Washcombo Main](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washcombo Mini](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/) | Remote start |
+| [Washtower](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Single-Unit/)<br>[Washtower Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Dryer/)<br>[Washtower Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Washer/) | Remote start |
+| [Water Heater](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Water-Heater/) | Power |
+| [Wine Cellar](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Wine-Cellar/) | Sabbath |
+
+### Climate
+
+The properties for controlling both the temperature and wind strength of the appliance are represented as a climate platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/) | Current temperature<br>Fan mode<br>HVAC mode<br>Preset mode<br>Temperature<br>Temperature cool<br>Temperature heat<br>Unit |
+| [System Boiler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/System-Boiler/) | Current temperature<br>HVAC mode<br>Temperature<br>Temperature cool<br>Temperature heat<br>Unit |
+
+### Event
+
+A notification message pushed from the server is represented as an event platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/) | Notification |
+| [Air Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-purifier/) | Notification |
+| [Air Purifier Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Air-Purifier-Fan/) | Notification |
+| [Dehumidifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dehumidifier/) | Notification |
+| [Dish Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dish-washer/) | Error<br>Notification |
+| [Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Dryer/) | Error<br>Notification |
+| [Humidifier](https://thinq.developer.lge.com/ko/cloud/docs/thinq-connect/device-profile/humidifier/) | Notification |
+| [Kimchi Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Kimchi-Refrigerator/) | Notification |
+| [Microwave Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Microwave-Oven/) | Notification |
+| [Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Oven/) | Notification |
+| [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/) | Notification |
+| [Robot Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/robot-cleaner/) | Error<br>Notification |
+| [Stick Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Stick-Cleaner/) | Notification |
+| [Styler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/styler/) | Error<br>Notification |
+| [Washcombo Main](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washcombo Mini](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/) | Error<br>Notification |
+| [Washtower](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Single-Unit/)<br>[Washtower Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Dryer/)<br>[Washtower Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Washer/) | Error<br>Notification |
+| [Wine Cellar](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Wine-Cellar/) | Notification |
+
+### Fan
+
+The properties for controlling the wind strength of the appliance are represented as a fan platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Ceiling Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/ceiling-fan/) | Power<br>Speed |
+
+### Number
+
+A read-write property which has numeric value is represented as a number platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/) | Schedule turn-off<br>Schedule turn-on<br>Sleep timer |
+| [Air Purifier Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Air-Purifier-Fan/) | Sleep timer<br>Wind temperature |
+| [Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Dryer/) | Delay ends in<br>Delay starts in |
+| [Hood](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Hood/) | Fan<br>Light |
+| [Humidifier](https://thinq.developer.lge.com/ko/cloud/docs/thinq-connect/device-profile/humidifier/) | Sleep timer<br>Target humidity |
+| [Microwave Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Microwave-Oven/) | Fan<br>Light |
+| [Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Oven/) | Temperature |
+| [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/) | Temperature |
+| [Styler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/styler/) | Delay ends in |
+| [Washcombo Main](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washcombo Mini](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/) | Delay ends in<br>Delay starts in |
+| [Washtower](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Single-Unit/)<br>[Washtower Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Dryer/)<br>[Washtower Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Washer/) | Delay ends in<br>Delay starts in |
+| [Water Heater](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Water-Heater/) | Temperature |
+| [Wine Cellar](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Wine-Cellar/) | Light<br>Temperature |
+
+### Select
+
+A writable property which has a list of selectable values is represented as a select platform.
+
+| Device |Property |
+| ------ |-------- |
+| [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/) | Air purify<br>Air quality sensor |
+| [Air Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-purifier/) | Operating mode<br>Speed |
+| [Air Purifier Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Air-Purifier-Fan/) | Display brightness<br>Operating mode<br>Rotation<br>Speed |
+| [Dehumidifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dehumidifier/) | Speed |
+| [Dish Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dish-washer/) | Operation |
+| [Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Dryer/) | Operation |
+| [Humidifier](https://thinq.developer.lge.com/ko/cloud/docs/thinq-connect/device-profile/humidifier/) | Display brightness<br>Drying mode<br>Operating mode<br>Speed |
+| [Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Oven/) | Cook mode<br>Operation<br> |
+| [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/) | Fresh air filter |
+| [Styler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/styler/) | Operation |
+| [Washcombo Main](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washcombo Mini](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/) | Operation |
+| [Washtower](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Single-Unit/)<br>[Washtower Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Dryer/)<br>[Washtower Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Washer/) | Operation |
+| [Water Heater](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Water-Heater/) | Operating mode |
+| [Wine Cellar](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Wine-Cellar/) | Light<br>Operating mode |
+
+### Sensor
+
+A read-only property which has states is represented as a sensor platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/) | Filter remaining<br>Humidity<br>Odor<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Schedule turn-off<br>Schedule turn-on<br>Sleep timer |
+| [Air Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-purifier/) | Air quality sensor<br>Humidity<br>Odor<br>Operating mode<br>Overall air quality<br>Personal mode<br>PM1<br>PM10<br>PM2.5 |
+| [Air Purifier Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Air-Purifier-Fan/) | Air quality sensor<br>Humidity<br>Odor<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Sleep timer<br>Temperature |
+| [Cooktop](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Cooktop/) | Current status<br>Power level<br>Remaining time |
+| [Dehumidifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dehumidifier/) | Humidity<br>Operating mode |
+| [Dish Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dish-washer/) | Current cycle<br>Current status<br>Delay starts in<br>Remaining time<br>Rinse aid dispenser level<br>Softening level<br>Total time |
+| [Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Dryer/) | Current status<br>Delay ends in<br>Delay starts in<br>Remaining time<br>Total time |
+| [Home Brew](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Home-Brew/)| Brewing duration<br>Brewing period<br>Current status<br>Flavor<br>Homebrew recipe<br>Hops<br>Recipe progress<br>Wort<br>Yeast |
+| [Humidifier](https://thinq.developer.lge.com/ko/cloud/docs/thinq-connect/device-profile/humidifier/) | Air quality sensor<br>Humidity<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Schedule turn-off<br>Schedule turn-on<br>Sleep timer<br>Temperature |
+| [Kimchi Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Kimchi-Refrigerator/) | Fresh air filter<br>Temperature |
+| [Microwave Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Microwave-Oven/) | Current status<br>Remaining time |
+| [Oven](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Oven/) | Cook time<br>Current status<br>Remaining time<br>Temperature |
+| [Plant Cultivator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Plant-Cultivator/) | Current status<br>Day growth temperature<br>Lighting duration<br>Lighting intensity<br>Lights on time<br>Mode<br>Night growth temperature<br>Temperature<br>Wind speed |
+| [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/) | Fresh air filter<br>Water filter used |
+| [Robot Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/robot-cleaner/) | Current status<br>Operating mode<br>Running time |
+| [Stick Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Stick-Cleaner/) | Battery<br>Current status<br>Operating mode |
+| [Styler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/styler/) | Current status<br>Delay ends in<br>Delay starts in<br>Remaining time<br>Total time |
+| [Washcombo Main](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washcombo Mini](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/)<br>[Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/washer/) | Current status<br>Delay ends in<br>Delay starts in<br>Remaining time<br>Total time |
+| [Washtower](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Single-Unit/)<br>[Washtower Dryer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Dryer/)<br>[Washtower Washer](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/WashTower-Washer/) | Current status<br>Delay ends in<br>Delay starts in<br>Remaining time<br>Total time |
+| [Water Heater](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Water-Heater/) | Temperature |
+| [Water Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/water-purifier/) | High-temp sterilization<br>Type<br>UVnano|
+
+### Switch
+
+A read-write property which has only two states that can be toggled is represented as a switch platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Air Conditioner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-conditioner/) | Energy saving |
+| [Air Purifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/air-purifier/) | Power |
+| [Air Purifier Fan](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Air-Purifier-Fan/) | Heating<br>Power<br>UVnano |
+| [Dehumidifier](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/dehumidifier/) | Power |
+| [Humidifier](https://thinq.developer.lge.com/ko/cloud/docs/thinq-connect/device-profile/humidifier/) | Auto mode<br>Heating<br>Mood light<br>Power<br>Sleep mode |
+| [Refrigerator](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/) | Ice plus<br>Quick freeze |
+| [System Boiler](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/System-Boiler/) | Hot water |
+| [Wine Cellar](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/Wine-Cellar/) | Ventilation |
+
+### Vacuum
+
+The properties for controlling the clean operations of the appliance are represented as a vacuum platform.
+
+| Device | Property |
+| ------ | -------- |
+| [Robot Cleaner](https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/robot-cleaner/) | Battery<br>Current status<br>Operation |
+
+## Troubleshooting
+
+### Setup
+
+#### Aborted: The token is not valid
+
+This error occurs when the Personal Access Token (PAT) is invalid or entered incorrectly. Please visit the [Personal Access Token Page](https://connect-pat.lgthinq.com) page to check if your token is valid.
+
+#### Aborted: The country is not supported
+
+Check your PAT's valid country in the **Choose the region / Country** section.
+
+#### Error: The number of API calls has been exceeded
+
+This error occurs when there's an abnormal number of API calls made using the PAT.
+The LG ThinQ integration will work properly after some time.
+
+## Debugging
+
+The LG ThinQ integration will show additional information by enabling log configuration. Add the line to your {% term "`configuration.yaml`" %}:
+Don't forget to remove the line again once you are done debugging.
+
+```yaml
+logger:
+  default: info
+  logs:
+    homeassistant.components.lg_thinq: debug
+```
--- a/source/_integrations/local_file.markdown
+++ b/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
--- a/source/_integrations/matter.markdown
+++ b/source/_integrations/matter.markdown
@ -14,6 +14,7 @@ ha_category:
  - Sensor
  - Switch
  - Update
+  - Vacuum
  - Valve
 ha_release: '2022.12'
 ha_iot_class: Local Push
@ -36,6 +37,7 @@ ha_platforms:
  - sensor
  - switch
  - update
+  - vacuum
  - valve
 ha_integration_type: integration
 related:
--- a/source/_integrations/music_assistant.markdown
+++ b/source/_integrations/music_assistant.markdown
@ -0,0 +1,38 @@
+---
+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.
--- a/source/_integrations/onkyo.markdown
+++ b/source/_integrations/onkyo.markdown
@ -3,93 +3,51 @@ title: Onkyo
 description: Instructions on how to integrate Onkyo and some Pioneer receivers into Home Assistant.
 ha_category:
  - Media player
-ha_release: 0.17
-ha_iot_class: Local Push
+ha_codeowners:
+  - '@arturpragacz'
+ha_config_flow: true
 ha_domain: onkyo
+ha_integration_type: integration
+ha_iot_class: Local Push
 ha_platforms:
  - media_player
-ha_integration_type: integration
+ha_release: 0.17
 related:
  - docs: /docs/configuration/
    title: Configuration file
-ha_codeowners:
-  - '@arturpragacz'
 ---

 The `onkyo` {% term integration %} allows you to control a [Onkyo](https://www.onkyo.com), [Integra](http://www.integrahometheater.com)
 and some recent [Pioneer](https://www.pioneerelectronics.com) receivers from Home Assistant.
 Please be aware that you need to enable "Network Standby" for this integration to work in your Hardware.

-## Configuration
+{% include integrations/config_flow.md %}

-To add an Onkyo or Pioneer receiver to your installation, add the following to your {% term "`configuration.yaml`" %} file.
-{% include integrations/restart_ha_after_config_inclusion.md %}
+If your receiver has second or third zone available, they are displayed as additional media players with the same functionality as the main zone.

-```yaml
-# Example configuration.yaml entry
-media_player:
-  - platform: onkyo
-    host: 192.168.1.2
-    name: receiver
-    sources:
-      pc: "HTPC"
-```
-
- If your receiver has second or third zone’s available, they are displayed as additional media players with the same functionality as the main zone.
-
-{% configuration %}
-host:
-  description: IP address of the device. Example:`192.168.1.2`. If not specified, the platform will load any discovered receivers.
-  required: false
+{% configuration_basic %}
+Host:
+  description: Hostname or IP address of the device, for example:`192.168.1.2`.
  type: string
-name:
-  description: Name of the device. (*Required if host is specified*)
-  required: false
-  type: string
-max_volume:
-  description: Maximum volume as a percentage. Often the maximum volume of the receiver is far too loud. Setting this will set Home Assistant's 100% volume to be this setting on the amp. i.e., if you set this to 50% when you set Home Assistant to be 100% then your receiver will be set to 50% of its maximum volume.
-  required: false
+Volume Resolution:
+  description: Number of steps it takes for the receiver to go from the lowest to the highest possible volume. Possible values are 50, 80, 100, 200. For older Onkyo receivers, this typically is 80; newer Onkyo receivers use 200.
+  type: integer
+Input sources:
+  description: List of input sources supported by the receiver.
+  type: list
+{% endconfiguration_basic %}
+
+{% include integrations/option_flow.md %}
+
+{% configuration_basic %}
+Max Volume:
+  description: Maximum volume limit as a percentage. Often the maximum volume of the receiver is far too loud. Setting this will set Home Assistant's 100% volume to be this setting on the amp, i.e., if you set this to 50%, when you set Home Assistant to be 100%, then your receiver will be set to 50% of its maximum volume.
  default: 100
  type: integer
-receiver_max_volume:
-  description: The number of steps it takes for the receiver to go from the lowest to the highest possible volume. Possible values are 50, 80, 100, 200. For older Onkyo receivers, this typically is 80; newer Onkyo receivers use 200.
-  required: false
-  default: 80
-  type: integer
-sources:
-  description: A list of mappings from source to source name. Valid sources can be found below. A default list will be used if no source mapping is specified.
-  required: false
+Input sources:
+  description: Mappings of input sources to their names.
  type: list
-{% endconfiguration %}
-
-List of source names:
-
- `video1`
- `video2`
- `video3`
- `video4`
- `video5`
- `video6`
- `video7`
- `dvd`
- `bd-dvd`
- `tape1`
- `tv-tape`
- `tape2`
- `phono`
- `cd`
- `tv-cd`
- `fm`
- `am`
- `tuner`
- `dlna`
- `internet-radio`
- `usb`
- `network`
- `universal-port`
- `multi-ch`
- `xm`
- `sirius`
+{% endconfiguration_basic %}

 ### Action `onkyo_select_hdmi_output`

@ -105,6 +63,21 @@ Accepted values are:
 which one to use seems to vary depending on model so you will have to try them out.
 ( For model TX-NR676E it seems to be 'out' for main, 'out-sub' for sub, and 'sub' for both )

+### Example `onkyo_select_hdmi_output` script
+
+```yaml
+# Example onkyo_select_hdmi_output script
+#
+script:
+  hdmi_sub:
+    alias: "Hdmi out projector"
+    sequence:
+      - action: media_player.onkyo_select_hdmi_output
+        data:
+          entity_id: media_player.onkyo
+          hdmi_output: out-sub
+```
+
 ### Example `play_media` script

 The `play_media` function can be used in script to play radio station by preset number.
@ -114,7 +87,7 @@ Not working for NET radio.
 # Example play_media script
 #
 script:
- radio1:
+  radio1:
    alias: "Radio 1"
    sequence:
      - action: media_player.turn_on
@ -127,18 +100,3 @@ script:
          media_content_type: "radio"
          media_content_id: "1"
 ```
-
-### Example `onkyo_select_hdmi_output` script
-
-```yaml
-# Example onkyo_select_hdmi_output script
-#
-script:
- hdmi_sub:
-    alias: "Hdmi out projector"
-    sequence:
-      - action: media_player.onkyo_select_hdmi_output
-        data:
-          entity_id: media_player.onkyo
-          hdmi_output: out-sub
-```
--- a/source/_integrations/pegel_online.markdown
+++ b/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'
--- a/source/_integrations/pinecil.markdown
+++ b/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
 ---

--- a/source/_integrations/prometheus.markdown
+++ b/source/_integrations/prometheus.markdown
@ -189,22 +189,27 @@ When looking into the metrics on the Prometheus side, there will be:

 - All Home Assistant domains, which can be easily found through the common **namespace** prefix, if defined.
 - The [client library](https://github.com/prometheus/client_python) provided metrics, which are a bunch of **process_\*** and also a single pseudo-metric **python_info** which contains (not as value but as labels) information about the Python version of the client, i.e., the Home Assistant Python interpreter.
-  
+
 Typically, you will only be interested in the first set of metrics.

 ## Metrics in unavailable or unknown states

-When the Prometheus exporter starts (typically when Home Assistant starts), all non-excluded entities in an unavailable or unknown state are not be exported until they are available again. If the entity goes into state unavailable or unknown again, the value exported will always be the latest known one.
+When the Prometheus exporter starts (typically when Home Assistant starts), all non-excluded entities in an unavailable or unknown state are not exported until they are available and known.

-While an entity is in those states, the `entity_available` corresponding metric is set to 0. This metric can be used to filter out values while the entity is unavailable or in an unknown state thanks to a [recording rule](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/).
+If an available entity goes into state unavailable or unknown, then it will automatically be unexported and return again automatically when available and known.

-For example:
+{% note %}
+
+To filter out these stale values, `entity_available` could be used in a query or recording rule. For example:

 ```yaml
 - record: "known_temperature_c"
  expr: "temperature_c unless entity_available == 0"
 ```

+This use of `unless` (which can be slow to compute) is no longer necessary, but will continue to work.
+{% endnote %}
+
 ## Supported metrics

 Metrics are exported only for the following domains:
--- a/source/_integrations/pushover.markdown
+++ b/source/_integrations/pushover.markdown
@ -38,7 +38,7 @@ Example Automation:

 Integration-specific values in the nested `data` section are optional.

-Image attachments can be added using the `attachment` parameter, which can either be a local file reference (ex: `/tmp/image.png`).
+Image attachments can be added using the `attachment` parameter, which must be a local file reference (ex: `/tmp/image.png`).

 To use a specific Pushover device, set it using `target`. If one of the entered devices doesn't exist or is disabled in your Pushover account it will send a message to all you devices. To send to all devices, just skip the target attribute.

--- a/source/_integrations/reolink.markdown
+++ b/source/_integrations/reolink.markdown
@ -76,11 +76,9 @@ Depending on the supported features of the camera, binary sensors are added for:
 - AI package detection+
 - Sleep status

-\+ These sensors receive events using 3 methods in order: ONVIF push, ONVIF long polling or fast polling (every 5 seconds).
-The latency for receiving the events is the best for ONVIF push and the worst for fast polling, the fastest available method that is detected to work will be used, and slower methods will not be used.
+\+ These sensors receive events using the following 4 methods (in order): TCP push, ONVIF push, ONVIF long polling or fast polling (every 5 seconds).
+The latency for receiving the events is the best for TCP push and the worst for fast polling, the fastest available method that is detected to work will be used, and slower methods will not be used.
 For redundancy, these sensors are polled every 60 seconds together with the update of all other entities.
-Not all camera models generate ONVIF push events for all event types, some binary sensors might, therefore, only be polled.
-For list of Reolink products that support ONVIF see the [Reolink Support Site](https://support.reolink.com/hc/en-us/articles/900000617826).
 To ensure you have the best latency possible, refer to the [Reducing latency of motion events](#reducing-latency-of-motion-events) section.

 ## Number entities
@ -400,11 +398,11 @@ Set up the Reolink integration in Home Assistant using the credentials you set i

 ### Reducing latency of motion events

-ONVIF push will result in slightly faster state changes of the binary motion/AI event sensors than ONVIF long polling.
-Moreover, ONVIF push is less demanding for the camera than ONVIF long polling or fast polling, resulting in potentially less connection issues.
-However, ONVIF push has some additional network configuration requirements:
+TCP push and ONVIF push will result in slightly faster state changes of the binary motion/AI event sensors than ONVIF long polling.
+Moreover, TCP push and ONVIF push are less demanding for the camera than ONVIF long polling or fast polling, resulting in potentially less connection issues.
+TCP push does not have any particular requirements. However, ONVIF push has some additional network configuration requirements:

- Reolink products can not push motion events to an HTTPS address (SSL).
+- Reolink products can not push ONVIF motion events to an HTTPS address (SSL).
 Therefore, make sure a (local) HTTP address at which HA is reachable is configured under **Home Assistant URL** in the {% my network title="network settings" %}.
 A valid address could, for example, be `http://192.168.1.10:8123` where `192.168.1.10` is the IP of the Home Assistant device.

@ -412,4 +410,4 @@ A valid address could, for example, be `http://192.168.1.10:8123` where `192.168
 Therefore, ensure no Global SSL certificate is configured in the [`configuration.yaml` under HTTP](/integrations/http/#ssl_certificate).
 An SSL certificate can still be enforced for external connections, by, for instance, using the [NGINX add-on](https://github.com/home-assistant/addons/tree/master/nginx_proxy) or [NGINX Proxy Manager add-on](https://github.com/hassio-addons/addon-nginx-proxy-manager) instead of a globally enforced SSL certificate.

-To see if a Reolink integration is currently using `ONVIF push`, `ONVIF long polling` or `Fast polling`, [download the diagnostics text file](/docs/configuration/troubleshooting/#download-diagnostics) and find the `"event connection": "ONVIF push"\"ONVIF long polling"\"Fast polling"` in the txt file.
+To see if a Reolink integration is currently using `TCP push`, `ONVIF push`, `ONVIF long polling` or `Fast polling`, [download the diagnostics text file](/docs/configuration/troubleshooting/#download-diagnostics) and find the `"event connection": "TCP push"\"ONVIF push"\"ONVIF long polling"\"Fast polling"` in the txt file.
--- a/source/_integrations/roomba.markdown
+++ b/source/_integrations/roomba.markdown
@ -10,7 +10,6 @@ ha_codeowners:
  - '@pschmitt'
  - '@cyr-ius'
  - '@shenxn'
-  - '@Xitee1'
  - '@Orhideous'
 ha_domain: roomba
 ha_config_flow: true
--- a/source/_integrations/schlage.markdown
+++ b/source/_integrations/schlage.markdown
@ -14,6 +14,7 @@ ha_platforms:
  - binary_sensor
  - diagnostics
  - lock
+  - select
  - sensor
  - switch
 ha_integration_type: integration
--- a/source/_integrations/spotify.markdown
+++ b/source/_integrations/spotify.markdown
@ -13,7 +13,9 @@ ha_codeowners:
 ha_domain: spotify
 ha_zeroconf: true
 ha_platforms:
+  - diagnostics
  - media_player
+  - sensor
 ha_integration_type: service
 ---

@ -152,3 +154,19 @@ The `media_content_id` value can be obtained from the Spotify desktop app by cli
 ## Unsupported devices

 - **Sonos**: Although Sonos is a Spotify Connect device, it is not supported by the official Spotify API.
+
+## Sensors
+
+Spotify provides sensors that display information about the song that is currently being played. The following sensors are available:
+
+- **Song acousticness**: Indicates how much the sound is free from electronic modification. 100% indicates it not electronically modified.
+- **Song danceability**. In percent. Describes how suitable a track is for dancing based on a combination of musical elements including tempo, rhythm stability, beat strength, and overall regularity. The higher the value, the more danceable.
+- **Song energy**. In percent.  A measure of intensity and activity. Typically, energetic tracks feel fast, loud, and noisy. For example, death metal has high energy, while a Bach prelude scores low on the scale. Perceptual features contributing to this attribute include dynamic range, perceived loudness, timbre, onset rate, and general entropy. A higher number means more energetic.
+- **Song instrumentalness**: In percent. Describes whether a track contains no vocals. “Ooh” and “aah” sounds are treated as instrumental in this context. Rap or spoken word tracks are clearly “vocal”. The higher the value the more instrumental the song is. 
+- **Song key**: The estimated overall key of the track. If no key was detected, the value is unknown. For example, C sharp or E flat.
+- **Song liveness**: In percent.  Describes the presence of an audience in the recording. Higher liveness values represent an increased probability that the track was performed live.
+- **Song mode**: The modality (major or minor) of a song.
+- **Song speechiness**: In percent. Describes the presence of spoken words in a song. The more exclusively speech-like the recording (for example, talk show, audio book, poetry), the higher the value.
+- **Song tempo**: The speed of the piece of music that is currently playing, in beats per minute (bpm).
+- **Song time signature**: The time signature (meter) is a notational convention to specify how many beats are in each bar (or measure). For example: 4/4, 6/8.
+- **Song valence**. In percent. Tracks with high valence sound more positive (happy, cheerful, euphoric), while tracks with low valence sound more negative (sad, depressed, angry).
--- a/source/_integrations/squeezebox.markdown
+++ b/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:
--- a/source/_integrations/statistics.markdown
+++ b/source/_integrations/statistics.markdown
@ -20,14 +20,19 @@ 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 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.
+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.

 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 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).
+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).
 {% 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)
@ -61,8 +66,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 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: 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_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_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_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. |
--- a/source/_integrations/suez_water.markdown
+++ b/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
--- a/source/_integrations/switchbot_cloud.markdown
+++ b/source/_integrations/switchbot_cloud.markdown
@ -6,6 +6,7 @@ ha_category:
  - Plug
  - Remote
  - Sensor
+  - Lock
  - Switch
  - Vacuum
 ha_release: '2023.10'
@ -17,6 +18,7 @@ ha_codeowners:
 ha_domain: switchbot_cloud
 ha_platforms:
  - climate
+  - lock
  - sensor
  - switch
  - vacuum
@ -41,6 +43,7 @@ Please note, device names configured in the SwitchBot app are transferred into H
 - IR appliances exposed through the different hubs:
  - ON/OFF for all appliance types excepted "Others"
  - Air Conditioner
+- Lock
 - Meter
 - MeterPlus
 - Outdoor Meter
--- a/source/_integrations/switcher_kis.markdown
+++ b/source/_integrations/switcher_kis.markdown
@ -17,6 +17,7 @@ ha_platforms:
  - climate
  - cover
  - diagnostics
+  - light
  - sensor
  - switch
 ha_config_flow: true
@ -33,6 +34,7 @@ Supported devices:
 - Switcher V2 (Espressif chipset - from firmware 3.21)
 - Switcher V2 (Qualcomm chipset - from firmware 72.32)
 - Switcher V4
+- Switcher Mini
 - Switcher Breeze
 - Switcher Runner
 - Switcher Runner S11
--- a/source/_integrations/vodafone_station.markdown
+++ b/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
--- a/source/_integrations/wyoming.markdown
+++ b/source/_integrations/wyoming.markdown
@ -12,6 +12,7 @@ ha_domain: wyoming
 ha_integration_type: service
 ha_platforms:
  - binary_sensor
+  - conversation
  - number
  - select
  - stt
--- a/source/_posts/2024-11-06-release-202411.markdown
+++ b/source/_posts/2024-11-06-release-202411.markdown
@ -0,0 +1,358 @@
+---
+layout: post
+title: "2024.11: Beta release notes"
+description: "Beta release notes for Home Assistant 2024.11"
+date: 2024-10-30 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.png
+---
+
+<lite-youtube videoid="x" videotitle="Home Assistant 2024.11 Release Party"></lite-youtube>
+
+{% note %}
+
+**Welcome to the beta release notes for Home Assistant 2024.11** 🎉
+
+<br />
+
+Please note that these release notes are a work in progress. 👷‍♀️ We will be
+completing them over the next couple of days. Not all features might be final
+yet, and some features _**may not** make it into the final release_.
+
+<br />
+
+**Want to help test the beta?** Awesome! ❤️ We have documented how you
+[can join our beta channel and install the beta here](/common-tasks/os/#running-a-beta-version).
+
+<br />
+
+While running the beta, we highly recommend joining our _#beta_ channel on
+the [Home Assistant Discord chat](/join-chat)! 💬 Most developers and beta
+testers are in this channel during the beta period to share experiences, ideas,
+and iterate over new features, fine-tuning them before the final release.
+It's a really fun place to hang out. 😎
+
+<br />
+
+**Reporting issues**: As this is a beta test, you might encounter unexpected
+behavior or issues. 🐞 We use the GitHub issue tracker to track beta issues.
+You can find our issue trackers and the reported issues during beta here:
+
+<br />
+
+- [Report(ed) beta **dashboards/UI/frontend** issues](https://github.com/home-assistant/frontend/milestone/125)
+- [Report(ed) beta **integrations/automations/backend/core** issues](https://github.com/home-assistant/core/milestone/699)
+- [Report(ed) beta **documentation** issues](https://github.com/home-assistant/home-assistant.io/milestone/132)
+
+🙏 When reporting issues, **make sure to mention the exact beta version you are
+running** in the issue description. This will help us identify and track the
+issue correctly. Read more about [reporting issues here](/help/reporting_issues/).
+
+<br />
+
+Issues introduced in the beta are processed with priority. 🔝
+
+{% endnote %}
+
+{% tip %}
+
+Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=_X2-encNyrA)
+6 November 2024, at 20:00 GMT / 12:00 PT / 21:00 CET!
+
+{% endtip %}
+
+Home Assistant 2024.11! 🎉
+
+Enjoy the (beta) release!
+
+../Frenck
+
+<!--more-->
+
+- [Sections dashboard now generally available](#sections-dashboard-now-generally-available)
+- [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)
+- [Other noteworthy changes](#other-noteworthy-changes)
+  - [Live logs](#live-logs)
+- [Need help? Join the community!](#need-help-join-the-community)
+- [Backward-incompatible changes](#backward-incompatible-changes)
+- [All changes](#all-changes)
+
+## Sections dashboard now generally available
+
+Exciting news on the dashboarding front; the new sections type dashboards are
+now marked as stable! 
+
+This means that, as of this release, when you create a new dashboard, you
+will get our awesome drag and drop experience!
+
+### Convert your old dashboards to sections dashboards
+
+This release also includes a conversion from the old masonry type to the new sections type dashboards. If you change the type of a view to sections you get a button to convert the view. All the cards of the old view are then placed in an imported cards section, and you can drag them into sections as you please!
+
+### Precise sizing mode
+
+You now have even more control over the size of cards. In the layout options of a card you can now enable "Precise mode", this will give you 3 time more options for width and height as before!
+
+## Low latency cameras using WebRTC
+
+Camera stream will now try to use WebRTC when possible. This is a peer-to-peer connection making for lower latency streams.
+It will try to use the fastest and most direct path. Sometimes a direct connection between the client and camera is not possible, for those situations the stream needs to be relayed by an external server. Home Assistant Cloud by Nabu Casa provides this relay server for all Home Assistant Cloud subscribers! So no matter where you are, you should always be able to stream your camera with low latency.
+
+If WebRTC is not available it will fallback to using the old method of streaming.
+
+## 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:
+
+- **[Husqvarna Automower BLE]**, added by [@alistair23]  
+  Integrate your Husqvarna lawnmower using Bluetooth
+
+[@alistair23]: https://github.com/alistair23
+[Husqvarna Automower BLE]: /integrations/husqvarna_automower_ble
+
+- Add go2rtc and extend camera integration for better WebRTC support ([@edenhaus] - [#124410]) ([camera docs]) ([rtsp_to_webrtc docs]) (new-integration)
+- Allow SSL security_protocol configuration property in apache_kafka component ([@jkaflik] - [#128651]) ([apache_kafka docs]) (new-integration)
+- Palazzetti integration ([@dotvav] - [#128259]) ([palazzetti docs]) (new-integration)
+- Add LG ThinQ integration ([@LG-ThinQ-Integration] - [#129299]) ([lg_thinq docs]) (new-integration)
+- Add musicassistant integration ([@jozefKruszynski] - [#128919]) ([mass docs]) (new-integration)
+
+### 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:
+
+- Add Light support for Switcher Runner S11 ([@YogevBokobza] - [#126402]) ([switcher_kis docs]) (new-platform)
+- Add power sensor detection in fibaro integration ([@rappenze] - [#126964]) ([fibaro docs])
+- Add support for room sensors in ViCare integration ([@CFenner] - [#125243]) ([vicare docs])
+- Add hotwater storage sensors to ViCare integration ([@CFenner] - [#126570]) ([vicare docs])
+- Add sensor for total installations and integrations to Analytics Insights ([@starkillerOG] - [#127248]) ([analytics_insights docs])
+- Add sensors for gems and mystic hourglasses to Habitica integration ([@tr4nt0r] - [#127651]) ([habitica docs])
+- Add work area sensors to Husqvarna Automower ([@Thomas55555] - [#126931]) ([husqvarna_automower docs])
+- Add sensors to Omada ([@MarkGodwin] - [#127767]) ([tplink_omada docs]) (new-platform)
+- Add audio feature sensors to Spotify ([@joostlek] - [#128785]) ([spotify docs]) (new-platform)
+- Add Airzone Cloud main zone mode select ([@Noltari] - [#125918]) ([airzone_cloud docs])
+- Add Airzone Cloud switch entities to zones ([@Noltari] - [#125917]) ([airzone_cloud docs]) (new-platform)
+- Add 'select' to configure Schlage locks "Auto Lock Time" ([@mxr] - [#123758]) ([schlage docs])
+- Add Meter Pro support to SwitchBot ([@bdraco] - [#128991]) ([switchbot docs]) (noteworthy)
+- Add lock to switchbot_cloud ([@miterion] - [#115128]) ([switchbot_cloud docs]) (new-platform)
+- LinkPlay multiroom support ([@silamon] - [#127862]) ([linkplay docs])
+- Add more spotify sensors ([@joostlek] - [#129215]) ([spotify docs]) (noteworthy)
+
+{% details "Potential changes to process" icon="mdi:scale-balance" %}
+
+Processed up to _#129297.
+
+{% enddetails %}
+
+### 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 this release:
+
+- Add snapshot service to image entity ([@NickM-27] - [#110057]) ([image docs])
+- Blueprints for template entities ([@tetele] - [#126971]) ([template docs]) (noteworthy)
+- Add limited template to at field for time triggers ([@Petro31] - [#126584]) ([homeassistant docs])
+- Add `nmi` (nautical miles) as valid distance unit ([@mib1185] - [#124723]) (noteworthy)
+
+### Live logs
+
+A bit technical maybe, but if you need to view the Home Assistant supervisor logs, you
+can now view those live! No need to press refresh buttons anymore, and you can scroll back in time to see previous log items.
+
+_**Insert recording of it streaming**_
+
+## 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 "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 a linked doorbell sensor. Linked doorbell sensors can continue
+to 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 use 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` has 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 "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 "all" %}
+
+- Remove the Google Domains integration ([@emontnemery] - [#127278]) ([google_domains docs]) (breaking-change)
+- Add protocol upload / download sensors to Deluge ([@mgrandi] - [#119203]) ([deluge docs]) (breaking-change)
+- Remove Spider integration ([@joostlek] - [#127346]) ([spider docs]) (breaking-change)
+- Remove enigma2 yaml import ([@autinerd] - [#127597]) ([enigma2 docs]) (breaking-change)
+- Remove automatic linkage of doorbells to HomeKit accessories via device class occupancy ([@bdraco] - [#127668]) ([homekit docs]) (breaking-change)
+- Update A. O. Smith integration to reflect upstream API changes ([@bdr99] - [#127678]) ([aosmith docs]) (breaking-change)
+- Remove deprecated yaml import from Habitica ([@tr4nt0r] - [#127946]) ([habitica docs]) (breaking-change)
+- End deprecation for config entry import for folder watcher ([@gjohansson-ST] - [#128056]) ([folder_watcher docs]) (breaking-change)
+- Remove deprecated restart service in modbus ([@gjohansson-ST] - [#128059]) ([modbus docs]) (breaking-change)
+- Remove deprecated speed limit lock entity from tessie ([@jpbede] - [#128043]) ([tessie docs]) (breaking-change)
+- Remove config entry import from lg_netcast ([@gjohansson-ST] - [#128179]) ([lg_netcast docs]) (breaking-change)
+- Remove deprecated notify service in ecobee ([@gjohansson-ST] - [#128177]) ([ecobee docs]) (breaking-change)
+- Remove legacy knx notify service ([@gjohansson-ST] - [#128185]) ([knx docs]) (breaking-change)
+- Remove legacy notify service from ecobee ([@jpbede] - [#128115]) ([ecobee docs]) (breaking-change)
+- Remove deprecated yaml support from lg_netcast ([@jpbede] - [#128114]) ([lg_netcast docs]) (breaking-change)
+- Fix state for litterrobot ([@gjohansson-ST] - [#128297]) ([litterrobot docs]) (breaking-change)
+- Remove deprecated map integration ([@jpbede] - [#128529]) ([map docs]) (breaking-change)
+- Remove deprecated panel_iframe integration ([@jpbede] - [#128532]) ([panel_iframe docs]) (breaking-change)
+- Add translations for Netatmo thermostat preset modes ([@piitaya] - [#128890]) ([netatmo docs]) (breaking-change)
+- Add update_percentage state attribute to update entity ([@emontnemery] - [#128877]) ([update docs]) (breaking-change)
+- Remove bloomsky integration ([@epenet] - [#129073]) ([bloomsky docs]) (breaking-change)
+- Add config flow to Onkyo ([@Nebula83] - [#117319]) ([onkyo docs]) (breaking-change)
+- Remove deprecated `retries` and `lazy_error_count` yaml option ([@jpbede] - [#128932]) ([modbus docs]) (breaking-change)
+- Omit declined Google Calendar events ([@joelhawksley] - [#128900]) ([google docs]) (breaking-change)
+- Fix visualization by inverting open/closed state of patio awnings ([@mback2k] - [#128079]) ([wmspro docs]) (breaking-change)
+- Change Tibber get_prices action to return datetimes as str ([@functionpointer] - [#123901]) ([tibber docs]) (breaking-change)
+
+{% 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)
+- [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)
+
+[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)
--- a/source/changelogs/core-2024.11.markdown
+++ b/source/changelogs/core-2024.11.markdown
--- a/source/common-tasks/general.markdown
+++ b/source/common-tasks/general.markdown
@ -22,4 +22,6 @@ Creating an automation for polling gives you more flexibility on when to poll:
 1. Not all integrations have a configurable polling interval. The homeassistant.update_entity service, on the other hand, works with most of the integrations; no code changes are required.
 2. An automation allows you to poll whenever you want. For example, if you have a rate-limited solar panel provider with a maximum number of requests per day, you may want to lower/stop the polling at night but poll more frequently during the day.

-{% include common-tasks/define_custom_polling.md %}
+{% include common-tasks/define_custom_polling.md %}
+
+{% include common-tasks/remove_device_service.md %}
--- a/source/images/docs/configuration/integration_instance_delete.png
+++ b/source/images/docs/configuration/integration_instance_delete.png
--- a/source/images/github-top-project-2024-desktop.png
+++ b/source/images/github-top-project-2024-desktop.png
--- a/source/images/github-top-project-2024-mobile.png
+++ b/source/images/github-top-project-2024-mobile.png
--- a/source/voice_control/builtin_sentences.markdown
+++ b/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**
-    - *"turn on the living room light"*
-    - *"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”*
+- The entities you want to control with Assist must be [exposed to Assist](/voice_control/voice_remote_expose_devices/).
+- 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/).

-  <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**
-    - *"Nevermind"*: If you triggered the wake word by mistake and want to stop Home Assistant from listening
+- *Turn off the lights in the living room in 5 minutes*
+- *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"*
- *"open windows in the kitchen"*
- *"change office brightness to 50%"*
- *"set bedroom lights to green"*
+- *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?*

-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. Take a look at the test sentences:
+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:
    - 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 [response definition](https://github.com/home-assistant/intents/tree/main/responses)
+4. View the [sentence definition](https://github.com/home-assistant/intents/tree/main/sentences) for your language.
+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.
--- a/source/voice_control/index.markdown
+++ b/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
 ---