Merge branch 'current' into patch-824360

Hedda · web-flow · commit 716dbe9cb68d · 2025-10-20T11:06:26.000+02:00
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -30,10 +30,10 @@ GEM
     ffi (1.17.2-arm64-darwin)
     ffi (1.17.2-x86_64-linux-gnu)
     forwardable-extended (2.6.0)
-    google-protobuf (4.32.1-arm64-darwin)
+    google-protobuf (4.33.0-arm64-darwin)
       bigdecimal
       rake (>= 13)
-    google-protobuf (4.32.1-x86_64-linux-gnu)
+    google-protobuf (4.33.0-x86_64-linux-gnu)
       bigdecimal
       rake (>= 13)
     http_parser.rb (0.8.0)
@@ -96,7 +96,7 @@ GEM
       racc
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    prism (1.5.2)
+    prism (1.6.0)
     public_suffix (6.0.2)
     racc (1.8.1)
     rack (3.2.3)
diff --git a/_config.yml b/_config.yml
@@ -108,8 +108,8 @@ social:
 # Home Assistant release details
 current_major_version: 2025
 current_minor_version: 10
-current_patch_version: 2
-date_released: 2025-10-10
+current_patch_version: 3
+date_released: 2025-10-17
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
diff --git a/source/_data/people.yml b/source/_data/people.yml
@@ -105,3 +105,7 @@ Timothy Nibeaudeau:
 Keith Burzinski:
   name: Keith Burzinski
   github: kbx81
+
+Carl Albertsson:
+  name: Carl Albertsson
+  github: mellowism
diff --git a/source/_integrations/aosmith.markdown b/source/_integrations/aosmith.markdown
@@ -29,6 +29,7 @@ Before using this integration, your water heater must be connected to a Wi-Fi ne
 - EE12-50R55DVF
 - EE12-50H55DVF
 - EE12-55H55DVF
+- HETF-50-100
 - HPA10-40H45DV
 - HPA10-50H45DV
 - HPA10-66H45DV
diff --git a/source/_integrations/apcupsd.markdown b/source/_integrations/apcupsd.markdown
@@ -179,7 +179,7 @@ Some sensors are disabled by default, since they provide information that is onl
 - **Transfer to Battery**
   - **Description**: Time and date of last transfer to batteries.
   - **Available for machines**: all
-  - **Remarks**: This entity only becomes available after a tranfer to battery event happens.
+  - **Remarks**: This entity only becomes available after a transfer to battery event happens.
 
 - **Battery Status**
   - **Description**: The status of the batteries.
diff --git a/source/_integrations/azure_data_explorer.markdown b/source/_integrations/azure_data_explorer.markdown
@@ -62,10 +62,10 @@ There are a few differences between the **PAYG** and **Free** versions:
 3. Write and perform the following statements one by one, replacing the placeholder content between the <> with the copied values (including the brackets).
 
 ```KQL
-// Give the Service Pricipal write access to the database
+// Give the Service Principal write access to the database
 .add database ['<databasename>'] ingestors ('aadapp=<ApplicationID>;<DirectoryID>');
 
-// Give the Service Pricipal read access to database (used for connectivity checks) 
+// Give the Service Principal read access to the database (used for connectivity checks)
 .add database ['<databasename>'] viewers ('aadapp=<ApplicationID>;<DirectoryID>');
 
 // Create a table for the data to be ingested into (replace the name and copy inserted *name* for later use)
diff --git a/source/_integrations/azure_storage.markdown b/source/_integrations/azure_storage.markdown
@@ -45,3 +45,15 @@ This integration follows standard integration removal. No extra steps are requir
 Check that your storage account allows [`Shared Key` access](https://learn.microsoft.com/en-us/azure/storage/common/shared-key-authorization-prevent?tabs=portal#remediate-authorization-via-shared-key).
 
 {% enddetails %}
+
+{% details "DNS Error" %}
+
+You may encounter a `aiodns.error.DNSError: (4, 'Domain name not found')` error. 
+
+To resolve this:
+
+1. Navigate to **Settings → System → Network → DNS Servers** in Home Assistant
+2. Manually set fallback DNS servers to `1.1.1.1` (Cloudflare) and `8.8.8.8` (Google) (or any other that you prefer). This allows Home Assistant to resolve Azure domain names successfully.
+3. Restart Home Assistant to propagate the new settings.
+
+{% enddetails %}
diff --git a/source/_integrations/default_config.markdown b/source/_integrations/default_config.markdown
@@ -16,6 +16,7 @@ This {% term integration %} is a meta-component and configures a default set of
 - [Assist pipeline](/integrations/assist_pipeline/) (`assist_pipeline`)
 - [Backup](/integrations/backup/) (`backup`)
 - [Bluetooth](/integrations/bluetooth/) (`bluetooth`)
+- [Cloud](/integrations/cloud/) (`cloud`)
 - [Configuration](/integrations/config/) (`config`)
 - [Conversation](/integrations/conversation/) (`conversation`)
 - [DHCP discovery](/integrations/dhcp/) (`dhcp`)
diff --git a/source/_integrations/ecobee.markdown b/source/_integrations/ecobee.markdown
@@ -260,7 +260,7 @@ Enable/disable Smart Home/Away and Follow Me modes.
 
 ### Service `ecobee.set_sensors_in_climate`
 
-Set which sensors are active on a termostat for a specific climate program.
+Set which sensors are active on a thermostat for a specific climate program.
 
 | Service data attribute | Optional | Description                                                                                                                                         |
 | ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/source/_integrations/foscam.markdown b/source/_integrations/foscam.markdown
@@ -224,4 +224,4 @@ elements:
 
 ### Extra CGI Commands
 
-Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](https://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf)).
+Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](https://community.jeedom.com/uploads/short-url/2A5aSBcCyoVZOdpiFC8HRDAOxqG.pdf)).
diff --git a/source/_integrations/freedompro.markdown b/source/_integrations/freedompro.markdown
@@ -42,7 +42,7 @@ You will need to obtain an API key from Freedompro's app to use this integration
 2. Register and create your first home.
 3. Make sure you have at least one accessory paired with the Freedompro Cloud before starting integration.
 4. Switch to the **Profile** tab (bottom right corner).
-5. Scroll down to the **Developper tools** and tap **Api Key**.
+5. Scroll down to the **Developer tools** and tap **Api Key**.
 6. Generate an API key.
 
 {% include integrations/config_flow.md %}
diff --git a/source/_integrations/hassio.markdown b/source/_integrations/hassio.markdown
@@ -73,7 +73,7 @@ For Home Assistant Host, the following sensors are available:
 
 For each installed add-on Supervisor provides following binary sensors:
 
-(These entities are disabled by default and must be reenabled to appear)
+(These entities are disabled by default and must be re-enabled to appear)
 
 | Sensor | Enabled by default | Description |
 | ------- | ------------------ | ----------- |
diff --git a/source/_integrations/imeon_inverter.markdown b/source/_integrations/imeon_inverter.markdown
@@ -27,7 +27,7 @@ The Imeon Energy Inverter {% term integrations %} will poll an [Imeon](https://i
 
 - The Imeon inverter must be connected to the local network.
 - [OS One](https://imeon-energy.com/os-one/) version must be **1.8.1.4** or higher.
-- *ModuleAPI* application must be activated on the OS One pannel of your Imeon inverter.
+- *ModuleAPI* application must be activated on the OS One panel of your Imeon inverter.
    - To do so, connect to **OS One** > **Applications** and by hovering over *ModuleAPI*, select **Activate**.
 
 {% include integrations/config_flow.md %}
diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown
@@ -602,7 +602,7 @@ knx:
     # time and date exposures
     - type: time
       address: "0/0/1"
-    # entitiy exposures
+    # entity exposures
     - type: temperature
       entity_id: sensor.owm_temperature
       address: "0/0/2"
diff --git a/source/_integrations/lcn.markdown b/source/_integrations/lcn.markdown
@@ -80,7 +80,7 @@ They are ideal to be used in automation scripts or for the `template` platforms.
 {% endnote %}
 
 
-## Setting up devices and entites
+## Setting up devices and entities
 
 The `lcn` hardware modules and groups are represented by Home Assistant *devices*. The periphery of each `lcn` module is represented by Home Assistant *entities*. Peripheries are, for example, the output ports, relays, and variables of a module. Refer to the description of each [platform](#platforms) to learn about which entity should be used for which periphery.
 
diff --git a/source/_integrations/lightwave.markdown b/source/_integrations/lightwave.markdown
@@ -116,7 +116,7 @@ The first use of a light or switch will try to register with your Lightwave WiFi
 Lightwave Thermostatic Radiator Values (TRV) are supported.
 
 Earlier integrations required a proxy - See [LWProxy](https://github.com/ColinRobbins/Homeassistant-Lightwave-TRV).
-This capabilty is still supported, but no longer required.
+This capability is still supported, but no longer required.
 
 ```yaml
 # Example TRV configuration.yaml for TRVs
diff --git a/source/_integrations/livisi.markdown b/source/_integrations/livisi.markdown
@@ -30,7 +30,7 @@ The following devices are currently supported by this integration:
 - Wall Switches (ISS, ISS2)
 - Window-Door Sensor (WDS)
  
-## Prequisites
+## Prerequisites
  
 This integration communicates with the local version of LIVISI SmartHome only. 
  
diff --git a/source/_integrations/modbus.markdown b/source/_integrations/modbus.markdown
@@ -378,7 +378,7 @@ device_address:
 unique_id:
   description: "ID that uniquely identifies this entity.
   Slaves will be given a unique_id of <<unique_id>>_<<slave_index>>.
-  If two enities have the same unique ID, Home Assistant will raise an exception."
+  If two entities have the same unique ID, Home Assistant will raise an exception."
   required: false
   type: string
 
@@ -1461,7 +1461,7 @@ sensors:
       required: false
       type: integer
     virtual_count:
-      description: "Generates x+1 sensors (master + slaves), allowing read of multiple registers with a single read messsage."
+      description: "Generates x+1 sensors (master + slaves), allowing read of multiple registers with a single read message."
       required: false
       type: integer
     state_class:
diff --git a/source/_integrations/mysensors.markdown b/source/_integrations/mysensors.markdown
@@ -785,7 +785,7 @@ void receive(const MyMessage &message)
       last_dim=100;
     }
 
-    //Update constroller status
+    // Update controller status
     send_status_message();
 
   } else if ( message.type == V_PERCENTAGE ) {
@@ -794,14 +794,14 @@ void receive(const MyMessage &message)
     if ( dim_value == 0 ) {
       last_state = LIGHT_OFF;
 
-      //Update constroller with dimmer value & status
+      // Update controller with dimmer value & status
       send_dimmer_message();
       send_status_message();
     } else {
       last_state = LIGHT_ON;
       last_dim = dim_value;
 
-      //Update constroller with dimmer value
+      // Update controller with dimmer value
       send_dimmer_message();
     }
 
diff --git a/source/_integrations/onewire.markdown b/source/_integrations/onewire.markdown
@@ -105,6 +105,21 @@ The 1-Wire bus can be connected with a remote 1-wire host over a network connect
 
 {% include integrations/config_flow.md %}
 
+{% configuration_basic %}
+Host:
+  description: The hostname or IP address of your OWServer instance.
+Port:
+  description: The port of your OWServer instance.
+  default: 4304
+{% endconfiguration_basic %}
+
+{% include integrations/option_flow.md %}
+
+{% configuration_basic %}
+Device selection:
+  description: The precision of the `DS18B20` temperature sensors can be configured for individual devices. The lower the precision, the faster the sensor will respond, but with less accuracy. The selected precision is reflected in the `device_path` attribute of the sensor entities.
+{% endconfiguration_basic %}
+
 ### Entities and attributes
 
 Upon startup of the platform, the 1-wire bus is searched for available 1-wire devices. On Bridge devices, the `aux` and `main` branches are recursively searched. For each device that this platform handles (see list of supported devices above), the platform adds one sensor for each physical quantity it measures. The name of the sensor is the device ID with the physical quantity it measures appended. Unsupported sensors are noted with a warning message in the log.
@@ -122,29 +137,29 @@ unit_of_measurement: °C
 friendly_name: 28.FF5C68521604 Temperature
 ```
 
-### Units with multiple sensors
-
-This platform works with devices with multiple sensors, which will cause a discontinuity in recorded values. Existing devices will receive a new ID and therefore show up as new devices.
-If you wish to maintain continuity, it can be resolved in the database by renaming the old devices to the new names.
+## Removing the integration
 
-Connect to your database using the instructions from [Database section](/docs/backend/database/). Check the names of sensors:
+This integration follows standard integration removal. No extra steps are required.
 
-```sql
-SELECT entity_id, COUNT(*) as count FROM states GROUP BY entity_id ORDER BY count DESC LIMIT 10;
-```
+{% include integrations/remove_device_service.md %}
 
-Alter the names of sensors using the following examples:
+## Troubleshooting
 
-```sql
-UPDATE states SET entity_id='sensor.<sensor_name>_temperature' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%\u00b0C%';
-UPDATE states SET entity_id='sensor.<sensor_name>_pressure' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%mb%';
-UPDATE states SET entity_id='sensor.<sensor_name>_humidity' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%%%' ESCAPE '';
-```
+### Temperature reported as 85°C
 
-Remember to replace `<sensor_name>` with the actual name of the sensor, as seen in the `SELECT` query.
+A reading of 85°C on a `DS18B20` may indicate a valid value, or it may indicate a wiring issue or a loss of power.
 
-## Removing the integration
+> 85°C is the power-on reset value of the `DS18B20`. It can report such a value when its tiny internal capacitor that acts as its power supply is depleted.
 
-This integration follows standard integration removal. No extra steps are required.
+There is currently no way to distinguish between a valid and an invalid 85°C value. If such values are reported incorrectly, the first step is to check the wiring (possibly ensuring that the temperature sensors are powered, and not using parasitic power).
 
-{% include integrations/remove_device_service.md %}
+If all else fails, then a template can be used to filter out the incorrect values:
+{% raw %}
+```jinja
+{% if states('sensor.28_a05966040000_temperature') | float != 85 %}
+  {{ states('sensor.28_a05966040000_temperature') }}
+{% else %}
+  None
+{% endif %}
+```
+{% endraw %}
diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown
@@ -34,8 +34,6 @@ The default, and recommended, database engine is [SQLite](https://www.sqlite.org
 Changing database used by the recorder may result in losing your existing history. Migrating data is not supported.
 {% endcaution %}
 
-To change the defaults for the `recorder` integration in your installation, add the following to your {% term "`configuration.yaml`" %} file:
-
 ## Disk space requirements
 
 A bare minimum requirement is to have at least as much free temporary space available as the size of your database at all times. A table rebuild, repair, or repack may happen at any time, which can result in a copy of the data on disk during the operation. Meeting the bare minimum requirement is essential during a version upgrade, where the schema may change, as this operation almost always requires making a temporary copy of part of the database.
@@ -44,6 +42,8 @@ For example, if your database is 1.5&nbsp;GiB on disk, you must always have at l
 
 ## Advanced configuration
 
+To change the defaults for the `recorder` integration in your installation, add the following to your {% term "`configuration.yaml`" %} file:
+
 ```yaml
 # Example configuration.yaml entry
 recorder:
diff --git a/source/_integrations/tuya.markdown b/source/_integrations/tuya.markdown
@@ -95,7 +95,7 @@ Tuya supports scenes in their app. These allow triggering some of the more compl
 
 ## Troubleshooting
 
-### Unsupported device or missing device functionnality
+### Unsupported device or missing device functionality
 
 This integration relies on the official [Python SDK provided by Tuya](https://github.com/tuya/tuya-device-sharing-sdk), which does not expose all functionality available in SmartLife.
 
diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown
@@ -292,7 +292,7 @@ utility_meter:
 
 Additionally, you can add template sensors to compute daily and monthly total usage. Important note, in these examples,
 we use the `is_number()` [function](/docs/configuration/templating/#numeric-functions-and-filters) to verify the values
-returned from the sensors are numeric. If this evalutes to false, `None` is returned.
+returned from the sensors are numeric. If this evaluates to false, `None` is returned.
 
 {% raw %}
 
diff --git a/source/_integrations/velux.markdown b/source/_integrations/velux.markdown
@@ -35,14 +35,28 @@ There is currently support for the following device types within Home Assistant:
 
 Rain sensors of supported windows do not report automatically and must be polled every 5 minutes. For this reason, they are disabled by default, because polling uses more radio bandwidth and battery power than simply reporting changed window positions.
 
+## Prerequisites
+
+1. Make sure you have the password for your gateway's wireless access point.
+    - You'll find it printed on the underside of your KLF 200 device.
+    - It is not the web login password.
+2. Reboot or power cycle the KLF 200 device.
+    - You must complete the configuration within 5 minutes of rebooting the device while its Wi-Fi access point is still visible.
+3. During configuration, keep your Home Assistant connected to your regular network.
+    - Don't connect to the device's wireless access point.
+
 {% include integrations/config_flow.md %}
 
 During configuration, you will be asked for a hostname and password:
 
-- Hostname: enter the IP address of the KLF 200 gateway.
-- Password: enter the password of the gateway's wireless access point (printed on the underside - **not** the web login password).
+{% configuration_basic %}
+Hostname:
+    description: "The IP address or hostname of the KLF 200 gateway. You can find it in your router."
+Password:
+    description: "The password of the gateway's wireless access point. You can find it printed on the underside of the device. It is not the web login password."
+{% endconfiguration_basic %}
 
-You must complete the configuration within 5 minutes of rebooting the KLF 200 gateway while the access point is still available.
+Remember: You must complete the configuration within 5 minutes of rebooting the KLF 200 gateway. If you can't complete in time and setup fails, power cycle the device and try again.
 
 ## Actions
 
@@ -52,6 +66,12 @@ Reboots the configured KLF 200 gateway.
 
 In Home Assistant versions up to 2024.12.x, it was recommended to create an automation to reboot the KLF 200 gateway before shutting down or restarting Home Assistant. This automated reboot is now built into the integration, so you no longer need to create a separate automation.
 
+## Removing the integration
+
+This integration follows standard integration removal. No extra steps are required.
+
+{% include integrations/remove_device_service.md %}
+
 ## Velux Active (KIX 300)
 
 The Velux Active (KIX 300) set is not supported by this {% term integration %}. To integrate Velux Active (KIX 300) with Home Assistant, you can use the [HomeKit Controller](/integrations/homekit_controller) {% term integration %} and get full control over your windows, curtains, covers, the air quality sensor KLA 300, etc.
diff --git a/source/_posts/2025-09-17-home-assistant-turns-12.markdown b/source/_posts/2025-09-17-home-assistant-turns-12.markdown
@@ -42,7 +42,7 @@ In my opinion, the best thing about Home Assistant is its flexibility - you can
 
 - Inspired by [PowerDisplayESPHome](https://github.com/johannyren/PowerDisplayESPHome/tree/main), JannickBlmndl [made an LED matrix](https://gitlab.com/JannickBlmndl/ESPHome-Dynamic-Prices-LEDMatrix) that helps their household be more sustainable by being energy flexible. It displays the live energy prices from their energy provider. 📊
 
-- [Tano Spirits](https://www.youtube.com/@TanoSpirits) in Melbourne, Australia, uses Home Assistant to automate their Japanese Shochu distillery, inspired by the brewing automations at [Little Island Brewing Co](https://libc.co/brewing-process/) in Singapore. 🍻
+- [Tano Spirits](https://www.youtube.com/@TanoSpirits) in Melbourne, Australia, uses Home Assistant to automate their Japanese Shochu distillery, inspired by a small brewing company in Singapore. 🍻
 
 - Several years ago, HillPhantom found that Home Assistant wasn’t quite ready for him. Over the past year, though, he’s now got Ollama set up with his Home Assistant Voice Preview Edition and has been building guides on how to make your own [mmWave radar sensors in Home Assistant](https://www.youtube.com/watch?v=Gb-4l93st8A). 👋🏻
 
diff --git a/source/_posts/2025-10-01-release-202510.markdown b/source/_posts/2025-10-01-release-202510.markdown
diff --git a/source/_posts/2025-10-15-yellow-end-of-life.markdown b/source/_posts/2025-10-15-yellow-end-of-life.markdown
diff --git a/source/_redirects b/source/_redirects
diff --git a/source/blueprints/blog/2023-07/notify_agent_agenda.yaml b/source/blueprints/blog/2023-07/notify_agent_agenda.yaml
diff --git a/source/changelogs/core-2025.10.markdown b/source/changelogs/core-2025.10.markdown
diff --git a/source/images/blog/2025-10-yellow-eol/art.webp b/source/images/blog/2025-10-yellow-eol/art.webp
diff --git a/source/images/blog/2025-10-yellow-eol/yellow.webp b/source/images/blog/2025-10-yellow-eol/yellow.webp
diff --git a/source/more-info/unsupported/docker_configuration.markdown b/source/more-info/unsupported/docker_configuration.markdown
diff --git a/source/voice_control/aliases.markdown b/source/voice_control/aliases.markdown

Original file line number	Diff line number	Diff line change
`@@ -224,4 +224,4 @@ elements:`
`224`	`224`
`225`	`225`	`### Extra CGI Commands`
`226`	`226`
`227`		`-Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](https://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf)).`
	`227`	`+Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](https://community.jeedom.com/uploads/short-url/2A5aSBcCyoVZOdpiFC8HRDAOxqG.pdf)).`