Merge branch 'current' into next

CODEOWNERS

@@ -95,6 +95,7 @@ source/_integrations/azure_data_explorer.markdown @kaareseras
 source/_integrations/azure_devops.markdown @timmo001
 source/_integrations/azure_event_hub.markdown @eavanvalkenburg
 source/_integrations/azure_service_bus.markdown @hfurubotten
+source/_integrations/azure_storage.markdown @zweckj
 source/_integrations/backup.markdown @home-assistant/core
 source/_integrations/baf.markdown @bdraco @jfroy
 source/_integrations/balboa.markdown @garbled1 @natekspencer
@@ -133,6 +134,7 @@ source/_integrations/bthome.markdown @Ernst79 @thecode
 source/_integrations/bticino.markdown @cgtobi
 source/_integrations/bubendorff.markdown @cgtobi
 source/_integrations/buienradar.markdown @mjj4791 @ties @Robbie1221
+source/_integrations/burbank_water_and_power.markdown @tronikos
 source/_integrations/button.markdown @home-assistant/core
 source/_integrations/calendar.markdown @home-assistant/core
 source/_integrations/cambridge_audio.markdown @noahhusby
@@ -348,6 +350,7 @@ source/_integrations/hassio.markdown @home-assistant/supervisor
 source/_integrations/havana_shade.markdown @starkillerOG
 source/_integrations/hdmi_cec.markdown @inytar
 source/_integrations/heatmiser.markdown @andylockran
+source/_integrations/heicko.markdown @starkillerOG
 source/_integrations/heiwa.markdown @cmroche
 source/_integrations/heos.markdown @andrewsayre
 source/_integrations/here_travel_time.markdown @eifinger
@@ -361,7 +364,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 @Diegorro98
+source/_integrations/home_connect.markdown @DavidMStraub @Diegorro98 @MartinHjelmare
 source/_integrations/home_plus_control.markdown @cgtobi
 source/_integrations/homeassistant.markdown @home-assistant/core
 source/_integrations/homeassistant_alerts.markdown @home-assistant/core
@@ -418,6 +421,7 @@ source/_integrations/insteon.markdown @teharris1
 source/_integrations/integration.markdown @dgomes
 source/_integrations/intellifire.markdown @jeeftor
 source/_integrations/intesishome.markdown @jnimmo
+source/_integrations/iometer.markdown @MaestroOnICe
 source/_integrations/ios.markdown @robbiet480
 source/_integrations/iotawatt.markdown @gtdiehl @jyavenard
 source/_integrations/iotty.markdown @shapournemati-iotty
@@ -436,7 +440,7 @@ source/_integrations/ista_ecotrend.markdown @tr4nt0r
 source/_integrations/isy994.markdown @bdraco @shbatm
 source/_integrations/ituran.markdown @shmuelzon
 source/_integrations/izone.markdown @Swamp-Ig
-source/_integrations/jellyfin.markdown @j-stienstra @ctalkington
+source/_integrations/jellyfin.markdown @RunC0deRun @ctalkington
 source/_integrations/jewish_calendar.markdown @tsvi
 source/_integrations/juicenet.markdown @jesserockz
 source/_integrations/justnimbus.markdown @kvanzuijlen
@@ -485,6 +489,7 @@ source/_integrations/light.template.markdown @home-assistant/core
 source/_integrations/linak.markdown @abmantis
 source/_integrations/linear_garage_door.markdown @IceBotYT
 source/_integrations/linux_battery.markdown @fabaff
+source/_integrations/linx.markdown @starkillerOG
 source/_integrations/litejet.markdown @joncar
 source/_integrations/litterrobot.markdown @natekspencer @tkdrob
 source/_integrations/livisi.markdown @StefanIacobLivisi @planbnet
@@ -598,7 +603,7 @@ source/_integrations/nuheat.markdown @tstabrawa
 source/_integrations/nuki.markdown @pschmitt @pvizeli @pree
 source/_integrations/numato.markdown @clssn
 source/_integrations/number.markdown @home-assistant/core @Shulyaka
-source/_integrations/nut.markdown @bdraco @ollo69 @pestevez
+source/_integrations/nut.markdown @bdraco @ollo69 @pestevez @tdfountain
 source/_integrations/nutrichef.markdown @bdraco
 source/_integrations/nws.markdown @MatthewFlamm @kamiyo
 source/_integrations/nyt_games.markdown @joostlek
@@ -649,9 +654,10 @@ source/_integrations/pepco.markdown @tronikos
 source/_integrations/permobil.markdown @IsakNyberg
 source/_integrations/persistent_notification.markdown @home-assistant/core
 source/_integrations/pge.markdown @tronikos
+source/_integrations/pglab.markdown @pglab-electronics
 source/_integrations/philips_js.markdown @elupus
 source/_integrations/pi_hole.markdown @shenxn
-source/_integrations/picnic.markdown @corneyl
+source/_integrations/picnic.markdown @corneyl @codesalatdev
 source/_integrations/pinecil.markdown @tr4nt0r
 source/_integrations/ping.markdown @jpbede
 source/_integrations/piper.markdown @balloob @synesthesiam
@@ -800,6 +806,7 @@ source/_integrations/smappee.markdown @bsmappee
 source/_integrations/smart_blinds.markdown @starkillerOG
 source/_integrations/smart_home.markdown @starkillerOG
 source/_integrations/smart_meter_texas.markdown @grahamwetzler
+source/_integrations/smart_rollos.markdown @starkillerOG
 source/_integrations/smarther.markdown @cgtobi
 source/_integrations/smarttub.markdown @mdz
 source/_integrations/smarty.markdown @z0mbieprocess
@@ -809,6 +816,7 @@ source/_integrations/sms.markdown @ocalvo
 source/_integrations/smud.markdown @tronikos
 source/_integrations/snapcast.markdown @luar123
 source/_integrations/snmp.markdown @nmaggioni
+source/_integrations/snoo.markdown @Lash-L
 source/_integrations/snooz.markdown @AustinBrunkhorst
 source/_integrations/solaredge.markdown @frenck @bdraco
 source/_integrations/solaredge_local.markdown @drobtravels @scheric
@@ -915,6 +923,7 @@ source/_integrations/twentemilieu.markdown @frenck
 source/_integrations/twinkly.markdown @dr1rrb @Robbie1221 @Olen
 source/_integrations/twitch.markdown @joostlek
 source/_integrations/ubiwizz.markdown @imicknl
+source/_integrations/ublockout.markdown @starkillerOG
 source/_integrations/ukraine_alarm.markdown @PaulAnnekov
 source/_integrations/unifi.markdown @Kane610
 source/_integrations/unifi_direct.markdown @tofuSCHNITZEL
@@ -968,6 +977,7 @@ source/_integrations/weather.template.markdown @home-assistant/core
 source/_integrations/weatherflow.markdown @natekspencer @jeeftor
 source/_integrations/weatherflow_cloud.markdown @jeeftor
 source/_integrations/weatherkit.markdown @tjhorner
+source/_integrations/webdav.markdown @jpbede
 source/_integrations/webhook.markdown @home-assistant/core
 source/_integrations/webmin.markdown @autinerd
 source/_integrations/webostv.markdown @thecode

Gemfile

@@ -11,7 +11,7 @@ group :development do
   # > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
   gem 'sassc', '2.1.0'
   gem 'sass-embedded', '1.85.1'
-  gem 'rubocop', '1.72.2'
+  gem 'rubocop', '1.73.2'
   gem 'ruby-lsp', '0.23.11'
   gem 'rackup', '2.2.1'
 end

Gemfile.lock

@@ -30,10 +30,10 @@ GEM
     ffi (1.17.1-arm64-darwin)
     ffi (1.17.1-x86_64-linux-gnu)
     forwardable-extended (2.6.0)
-    google-protobuf (4.29.3-arm64-darwin)
+    google-protobuf (4.30.0-arm64-darwin)
       bigdecimal
       rake (>= 13)
-    google-protobuf (4.29.3-x86_64-linux)
+    google-protobuf (4.30.0-x86_64-linux)
       bigdecimal
       rake (>= 13)
     http_parser.rb (0.8.0)
@@ -99,7 +99,7 @@ GEM
     prism (1.3.0)
     public_suffix (6.0.1)
     racc (1.8.1)
-    rack (3.1.10)
+    rack (3.1.11)
     rack-protection (4.1.1)
       base64 (>= 0.1.0)
       logger (>= 1.6.0)
@@ -119,7 +119,7 @@ GEM
     regexp_parser (2.10.0)
     rexml (3.4.1)
     rouge (4.5.1)
-    rubocop (1.72.2)
+    rubocop (1.73.2)
       json (~> 2.3)
       language_server-protocol (~> 3.17.0.2)
       lint_roller (~> 1.1.0)
@@ -141,10 +141,9 @@ GEM
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
     sass (3.4.25)
-    sass-embedded (1.85.1-arm64-darwin)
-      google-protobuf (~> 4.29)
-    sass-embedded (1.85.1-x86_64-linux-gnu)
+    sass-embedded (1.85.1)
       google-protobuf (~> 4.29)
+      rake (>= 13)
     sass-globbing (1.1.5)
       sass (>= 3.1)
     sassc (2.1.0)
@@ -158,7 +157,7 @@ GEM
       rack-protection (= 4.1.1)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11862)
+    sorbet-runtime (0.5.11899)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
@@ -184,7 +183,7 @@ DEPENDENCIES
   nokogiri (= 1.18.3)
   rackup (= 2.2.1)
   rake (= 13.2.1)
-  rubocop (= 1.72.2)
+  rubocop (= 1.73.2)
   ruby-lsp (= 0.23.11)
   sass-embedded (= 1.85.1)
   sass-globbing (= 1.1.5)

_config.yml

@@ -107,9 +107,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2025
-current_minor_version: 2
-current_patch_version: 5
-date_released: 2025-02-21
+current_minor_version: 3
+current_patch_version: 0
+date_released: 2025-03-05
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_dashboards/energy.markdown

@@ -235,6 +235,28 @@ type: energy-devices-detail-graph
 max_devices: 5
 ```
 
+## Sankey energy graph
+
+<p class='img'>
+  <img src='/images/dashboards/energy/sankey.png' alt='Screenshot of the sankey energy graph card'>
+  Screenshot of the sankey energy graph card.
+</p>
+
+The sankey energy graph shows the flow of energy in your home. It starts with sources and flows into the various consumers. Devices are grouped into floors and areas if these are configured.
+
+### Examples
+
+```yaml
+type: energy-sankey
+```
+
+The following example orients the flow from top to bottom:
+
+```yaml
+type: energy-sankey
+layout: vertical
+```
+
 ## Using Multiple Collections
 
 By default, all energy cards are linked to any `energy-date-selection` card on the view, and all `energy-date-selection` cards are linked to the same period. To enable multiple different date selections on the same view, it is necessary to link them to different collections. This is done by adding the variable `collection_key` to the card YAML, and giving this a value of any custom string that begins with `energy_`. (strings that do not start with `energy_` will generate an error).

source/_dashboards/tile.markdown

@@ -12,11 +12,12 @@ related:
     title: Dashboard cards
 ---
 
-The tile card gives you a quick overview of your {% term entity %}. The card allows you to toggle the {% term entity %} and show the more info dialog. A badge is shown for some {% term entities %} like the [climate](/integrations/climate) or [person](/integrations/person) {% term entities %}.
+The tile card gives you a quick overview of your {% term entity %}. The card allows you to add tap actions, and features to control the entity. You can also select the {% term entity %} to open the more info dialog. A badge is shown for some {% term entities %} like the [climate](/integrations/climate) or [person](/integrations/person) {% term entities %}.
 
 <p class='img'>
-  <img src='/images/dashboards/tile_card.png' alt='Screenshot of tile cards'>
-  Screenshot of tile cards.
+  <img src='/images/dashboards/tile_card_tap_action.webp' alt='Screenshot of tile cards'>
+  The circular background behind an icon indicates that there is a tap action.   
+  The "Downstairs" and "Upstairs" climate entities have a badge and a feature that is bottom-aligned.
 </p>
 
 {% include dashboard/edit_dashboard.md %}

source/_data/glossary.yml

@@ -532,7 +532,6 @@
     entities for organic, paper, and packaging waste. In terms of functionality,
     the information service is like a device. It is called *service* to avoid
     confusion, as it does not come with a piece of hardware.
-  link: /docs/scripts/perform-actions/
   aliases:
     - services
 - term: State

source/_data/people.yml

@@ -92,4 +92,8 @@ Missy Quarry:
 
 Annika Schulz:
   name: Annika Schulz
-  github: anakinsbrna
+  github: anakinsbrna
+
+Miranda Bishop:
+  name: Miranda Bishop
+  github: miranda-gb

source/_data/products.yml

@@ -17,6 +17,11 @@ green:
       ship_to: America
       url: https://cloudfree.shop/product/home-assistant-green/
       logo: /images/distributors/cloudfree.webp
+    - name: Seeed Studio
+      ship_from: US
+      ship_to: America
+      url: https://www.seeedstudio.com/Home-Assistant-Green-p-5792.html
+      logo: /images/distributors/seeed-studio.webp
       # Asia
     - name: Seeed Studio
       ship_from: China

source/_docs/blueprint.markdown

@@ -18,7 +18,7 @@ This section gives a high-level introduction to blueprints. To view a descriptio
 
 ## What is a blueprint?
 
-A blueprint is a {% term script %}, {% term automation %} or [template entity](/docs/integrations/template/) configuration with certain parts marked as configurable. This allows you to create different scripts, automations or template entities based on the same blueprint.
+A blueprint is a {% term script %}, {% term automation %} or [template entity](/integrations/template/) configuration with certain parts marked as configurable. This allows you to create different scripts, automations or template entities based on the same blueprint.
 
 Imagine you want to control lights based on motion. A blueprint provides the generic {% term automation %} framework, while letting you select one specific motion sensor as a {% term trigger %}, and the exact light to control. This blueprint makes it possible to create two automations. Each automation has their own configuration and act completely independently. Yet, they share some basic automation configuration so that you do not have to set this up every time.
 

source/_docs/glossary.html

@@ -1,31 +0,0 @@
----
-title: "Glossary"
-description: "Home Assistant's Glossary."
----
-
-{% assign entries = site.data.glossary | sort: 'term' %}
-
-The glossary covers terms which are used around Home Assistant.
-
-<div class="config-vars basic">
-
-{% for entry in entries %}
-
-<div class="config-vars-item">
-  <div class="config-vars-label">
-    <a name="{{ entry.term | slugify }}" class="title-link" href="#{{ entry.term | slugify }}"></a>
-    <span class="config-vars-label-name">{{ entry.term }}</span>
-  </div>
-  <div class="config-vars-description-and-children">
-    <span class="config-vars-description">
-      {{ entry.definition | markdownify | newline_to_br }}
-      {%- if entry.link -%}
-      <a href="{{ entry.link }}">Read more about: {{ entry.term }}</a>
-      {%- endif -%}
-    </span>
-  </div>
-</div>
-
-{% endfor %}
-
-</div>

source/_docs/glossary.markdown

@@ -0,0 +1,33 @@
+---
+title: "Glossary"
+description: "Home Assistant's Glossary."
+---
+
+The glossary covers terms which are used around Home Assistant.
+
+{% assign entries = site.data.glossary | sort: 'term' %}
+{% assign current_letter = '' %}
+
+{% for entry in entries %}
+
+{% assign first_letter = entry.term | slice: 0 %}
+{% if first_letter != current_letter %}
+{% assign current_letter = first_letter | upcase %}
+
+## {{ current_letter }}
+
+---
+
+{% endif %}
+
+### {{ entry.term }}
+
+{{ entry.definition | markdownify }}
+
+{%- if entry.link -%}
+
+{{ "[Read more about " | append: "_" | append: entry.term | append: "_](" | append: entry.link | append: ")" | markdownify }}
+
+{%- endif -%}
+
+{% endfor %}

source/_docs/tools/dev-tools.markdown

@@ -149,7 +149,7 @@ Another use of the {% my developer_statistics title="statistics developer tool"
 <svg width="24" height="24" viewBox="0 0 24 24"><path d="M22,13V22H2V19L22,13M21.68,7.06L16.86,4.46L17.7,7.24L7.58,10.24C6.63,8.95 4.82,8.67 3.53,9.62C2.24,10.57 1.96,12.38 2.91,13.67C3.85,14.97 5.67,15.24 6.96,14.29C7.67,13.78 8.1,12.97 8.14,12.09L18.26,9.09L19.1,11.87L21.68,7.06Z" /></svg>
 icon. Use date & time to search for the incorrect data point and adjust the value.
 
-![Screenshot showing adjusting the long-term statistic history value](/images/blog/2022-04/adjust-statistics.png)
+![Screenshot showing adjusting the long-term statistic history value](/images/docs/developer-tools/adjust-statistics.png)
 
 ## Assist tab
 

source/_includes/asides/component_navigation.html

@@ -3,7 +3,7 @@
 {% assign percentage = 100.0 | times: active_installations | divided_by: site.data.analytics_data.reports_integrations | round: 1 %}
 <section class="aside-module grid__item one-whole lap-one-half">
   <div class='brand-logo-container section'>
-      <img src='https://brands.home-assistant.io/{% if page.ha_brand %}brands{% else %}_{% endif %}/{{ domain }}/logo.png' srcset='https://brands.home-assistant.io/{% if page.ha_brand %}brands{% else %}_{% endif %}/{{ page.ha_domain }}/logo@2x.png 2x' />
+      <img src='https://brands.home-assistant.io/{% if page.ha_brand %}brands{% else %}_{% endif %}/{{ page.ha_domain }}//logo.png' srcset='https://brands.home-assistant.io/{% if page.ha_brand %}brands{% else %}_{% endif %}/{{ page.ha_domain }}/logo@2x.png 2x' />
 
     {%- if page.ha_config_flow and domain -%}
       {% my config_flow_start badge domain=domain %}

source/_integrations/_integration_docs_template.markdown

@@ -0,0 +1,208 @@
+---
+title: My integration
+description: Example document structure and text blocks for integration documentation.
+ha_release: 2025.3
+ha_iot_class: Local Push
+ha_codeowners:
+  - '@home-assistant/core'
+ha_domain: my_integration
+ha_integration_type: integration
+related:
+  - url: https://developers.home-assistant.io/docs/documenting/standards
+    title: Documentation standard
+  - url: https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/
+    title: Integration Quality Scale - Rules
+  - docs: /docs/glossary/
+    title: Glossary
+  - docs: /docs/tools/quick-bar/#my-links
+    title: My link
+---
+
+<!--- The integration documentation template provides a documentation structure as well as some example content per section. The example content is meant for inspiration, it may not apply for your integration or will at least have to be adapted. -->
+
+<!--- Use this template together with the developer documentation, under [Documentation standard](https://developers.home-assistant.io/docs/documenting/standards) and the documentation rules of the [Integration Quality Scale](https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/). -->
+
+The **My integration** {% term integration %} is used to integrate with the devices of [MyCompany](https://www.mycompany.com). MyCompany creates various smart home appliances and devices and are known for their MyProduct.
+Use case: When you combine it with their other device you can do x.
+
+## Supported devices
+
+The following devices are known to be supported by the integration:
+
+- Device 1
+- Device 2
+- Every appliance that runs MyOS
+
+## Unsupported devices
+
+The following devices are not supported by the integration:
+
+- Device 3
+- Appliances built before 2010
+
+## Prerequisites
+
+1. Open the app store and install the **MyProduct** app.
+2. Create an account.
+3. Add a device to the app.
+4. Open the app and go to the **Settings** page.
+5. Select **Expose API**.
+
+{% include integrations/config_flow.md %}
+
+<!--- The next section is about documenting configuration variables. For details, refer to the [documentation standard on configuration variables](/docs/documenting/standards#configuration-variables). -->
+
+<!--- In case your integration is used via a config flow: -->
+
+{% configuration_basic %}
+Host:
+    description: "The IP address of your bridge. You can find it in your router or in the Integration app under **Bridge Settings** > **Local API**."
+Local access token:
+    description: "The local access token for your bridge. You can find it in the Integration app under **Bridge Settings** > **Local API**."
+{% endconfiguration_basic %}
+
+<!--- In case an integration is set up via YAML in the {% term "`configuration.yaml`" %}: -->
+
+{% configuration %}
+Host:
+    description: "The IP address of your bridge. You can find it in your router or in the Integration app under **Bridge Settings** > **Local API**."
+    required: false
+    type: string
+Local access token:
+    description: "The local access token for your bridge. You can find it in the Integration app under **Bridge Settings** > **Local API**."
+    required: false
+    type: string
+{% endconfiguration %}
+
+## Configuration options
+
+The integration provides the following configuration options:
+
+{% configuration_basic %}
+Country code:
+  description: You can specify the country code (NL or BE) of the country to display on the camera.
+Timeframe:
+  description: Minutes to look ahead for precipitation forecast sensors (minimum 5, maximum 120).
+{% endconfiguration_basic %}
+
+## Supported functionality
+
+### Entities
+
+The **My integration** integration provides the following entities.
+
+#### Buttons
+
+- **Start backflush**
+  - **Description**: Starts the backflush process on your machine. You got 15 seconds to turn the paddle after activation.
+  - **Available for machines**: all
+
+#### Numbers
+
+- **Dose**
+  - **Description**: Dosage (in ticks) for each key
+  - **Available for machines**: GS3 AV, Linea Mini.
+  - **Remarks**: GS3 has this multiple times, one for each physical key (1-4), and the entities are disabled by default.
+
+#### Sensors
+
+- **Current coffee temperature**
+  - **Description**: Current temperature of the coffee boiler.
+  - **Available for machines**: all
+  - **Remarks**: When the machine reaches temperature, this will be approximately 3 degrees higher than the `Coffee target temperature`, due to different measurement points.
+
+- **Current steam temperature**
+  - **Description**: Current temperature of the steam boiler.
+  - **Available for machines**: Linea Micra, GS3 AV, GS3 MP.
+  - **Remarks**: -
+
+#### Selects
+
+- **Prebrew/-infusion mode**
+  - **Description**: Whether to use prebrew, preinfusion, or neither.
+  - **Options**: Disabled, Prebrew, Preinfusion
+  - **Available for machines**: Linea Micra, Linea Mini, GS3 AV
+
+- **Steam level**
+  - **Description**: The level your steam boiler should run at.
+  - **Options**: 1, 2, 3
+  - **Available for machines**: Linea Micra
+
+#### Updates
+
+- **Gateway firmware**
+  - **Description**: Firmware status of the gateway.
+  - **Available for machines**: all
+
+## Actions
+
+The integration provides the following actions.
+
+### Action: Get schedule
+
+The `my_integration.get_schedule` action is used to fetch a schedule from the integration.
+
+- **Data attribute**: `config_entry_id`
+  - **Description**: The ID of the config entry to get the schedule from.
+  - **Optional**: No
+
+## Examples
+
+### Turning off the LEDs during the night
+
+The status LEDs on the device can be quite bright.
+To tackle this, you can use this blueprint to easily automate the LEDs turning off when the sun goes down.
+
+link to the blueprint on the [blueprints
+    exchange](https://community.home-assistant.io/c/blueprints-exchange/53)
+
+## Data updates
+
+The **My integration** integration fetches data from the device every 5 minutes by default.
+Newer devices (the ones running MyOS) have the possibility to push data.
+In this case, pushing data is enabled when the integration is started. If enabling data push fails, the integration uses data {% term polling %}.
+
+## Known limitations
+
+The integration does not provide the ability to reboot, which can instead be done via the manufacturer's app.
+
+## Troubleshooting
+
+### Can’t set up the device
+
+#### Symptom: “This device can’t be reached”
+
+When trying to set up the integration, the form shows the message “This device can’t be reached”.
+
+##### Description
+
+This means the settings on the device are incorrect, since the device needs to be enabled for local communication.
+
+##### Resolution
+
+To resolve this issue, try the following steps:
+
+1. Make sure your device is powered up (LEDs are on).
+2. Make sure your device is connected to the internet:
+   - Make sure the app of the manufacturer can see the device.
+3. Make sure the device has the local communication enabled:
+   - Check the device’s settings.
+   - Check the device’s manual.
+...
+
+### I can't see my devices
+
+Make sure the devices are visible and controllable via the manufacturer's app.
+If they are not, check the device's power and network connection.
+
+### The device goes unavailable after a day
+
+Make sure you turned off the device's power-saving mode.
+
+## Removing the integration
+
+This integration follows standard integration removal.
+
+{% include integrations/remove_device_service.md %}
+
+After deleting the integration, go to the app of the manufacturer and remove the Home Assistant integration from there as well.

source/_integrations/azure_storage.markdown

@@ -10,6 +10,7 @@ ha_domain: azure_storage
 ha_codeowners:
   - '@zweckj'
 ha_integration_type: service
+ha_quality_scale: bronze
 ---
 
 This integration allows you to use [Azure storage accounts](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview) for use with Home Assistant Backups.

source/_integrations/bring.markdown

@@ -13,9 +13,9 @@ ha_domain: bring
 ha_integration_type: service
 ha_platforms:
   - diagnostics
+  - event
   - sensor
   - todo
-  - event
 related:
   - docs: /integrations/todo
     title: To-do list integration documentation
@@ -25,6 +25,7 @@ related:
     title: To-do list card
   - url: https://www.getbring.com/
     title: Bring!
+ha_quality_scale: platinum
 ---
 
 The **Bring!** integration allows you to sync your [Bring!](https://www.getbring.com/) shopping lists with Home Assistant.

source/_integrations/burbank_water_and_power.markdown

@@ -4,7 +4,7 @@ description: Get energy usage from Burbank Water and Power (BWP) using the Opowe
 ha_category:
   - Energy
   - Sensor
-ha_release: 2025.3
+ha_release: 2023.8
 ha_domain: burbank_water_and_power
 ha_integration_type: virtual
 ha_supporting_domain: opower

source/_integrations/device_tracker.markdown

@@ -55,6 +55,7 @@ device_tracker:
   - platform: netgear
     host: IP_ADDRESS
     username: YOUR_USERNAME
+    password: YOUR_PASSWORD
     interval_seconds: 10
     consider_home: 180
     new_device_defaults:

source/_integrations/electric_kiwi.markdown

@@ -13,6 +13,7 @@ ha_platforms:
   - select
   - sensor
 ha_integration_type: hub
+ha_quality_scale: bronze
 ---
 
 [Electric Kiwi](https://www.electrickiwi.co.nz/) is an independent power and broadband company in New Zealand, offering variable rates for peak, shoulder, and off-peak pricing with a selectable hour of free power. 

source/_integrations/enphase_envoy.markdown

@@ -142,8 +142,8 @@ House consumption data requires an Envoy Metered equipped and configured with at
 
 - **Envoy <abbr title="Envoy serial number">SN</abbr> Current power consumption**: Current power consumption in W.
 - **Envoy <abbr title="Envoy serial number">SN</abbr> Lifetime energy consumption**: Lifetime energy consumption in Wh, default display scaled to MWh.
-- **Envoy <abbr title="Envoy serial number">SN</abbr> Energy production last seven days**: Energy consumption in previous 7 days, not including today's, in Wh, display scaled to kWh. This entity is not logged in statistics.
-- **Envoy <abbr title="Envoy serial number">SN</abbr> Energy consumption today**: Energy consumption since midnight in Wh, default display scaled to kWh.
+- **Envoy <abbr title="Envoy serial number">SN</abbr> Energy consumption last seven days**: Energy consumption in previous 7 days, not including today's, in Wh, display scaled to kWh. (See known limitations [Energy Incorrect](#energy-incorrect)) This entity is not logged in statistics.
+- **Envoy <abbr title="Envoy serial number">SN</abbr> Energy consumption today**: Energy consumption since midnight in Wh, default display scaled to kWh. (See known limitations [Energy Incorrect](#energy-incorrect))
 
 <figure>
   <img src="/images/integrations/enphase_envoy/enphase_envoy_consumption.png" alt="consumption entities">
@@ -683,8 +683,22 @@ When using Envoy Metered with <abbr title="current transformers">CT</abbr>, not
 
 When using Envoy Metered with <abbr title="current transformers">CT</abbr>
 
-- not all firmware versions report `Energy production today` correctly. Zero data and unexpected spikes have been reported. In this case, best use a utility meter with the `Lifetime energy production` entity for daily reporting.
-- not all firmware versions report `Energy production last seven days` correctly. Zero and unexpected values have been reported.
+- not all firmware versions report `Energy production today` and/or `Energy consumption today` correctly. Zero data and unexpected spikes have been reported. In this case, best use a utility meter with the `Lifetime energy production` or `Lifetime energy consumption` entity for daily reporting.
+- not all firmware versions report `Energy production last seven days` and/or `Energy consumption last seven days` correctly. Zero and unexpected values have been reported.
+- `Energy production today` has been reported not to reset to zero at the start of the day. Instead, it resets to a non-zero value that gradually increases over time. This issue has also been reported as starting suddenly overnight. For daily reporting, it is recommended to use a utility meter with the `Lifetime energy production` entity.
+
+{% details "History examples for Today's energy production value not resetting to zero" %}
+
+<figure>
+  <img src="/images/integrations/enphase_envoy/enphase_envoy_production_non_zero_reset.png" alt="envoy today non zero reset">
+  <figcaption>Envoy Today's energy production value exhibits a daily reset to an ever increasing non-zero value.</figcaption>
+</figure>
+
+<figure>
+  <img src="/images/integrations/enphase_envoy/enphase_envoy_production_non_zero_reset_step_change.png" alt="envoy today step change">
+  <figcaption>Envoy Today's energy production value exhibits a sudden onset of non-zero resets.</figcaption>
+</figure>
+{% enddetails %}
 
 ### Lifetime reset
 

source/_integrations/esera_onewire.markdown

@@ -19,6 +19,7 @@ ha_platforms:
   - sensor
   - switch
 ha_iot_class: Local Polling
+ha_zeroconf: true
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/group.markdown

@@ -118,10 +118,12 @@ In short, when any group member entity is `unlocked`, the group will also be `un
 - The group state is `unavailable` if all group members are `unavailable`.
 - Otherwise, the group state is `unknown` if all group members are `unknown` or `unavailable`.
 - Otherwise, the group state is `jammed` if at least one group member is `jammed`.
+- Otherwise, the group state is `opening` if at least one group member is `opening`.
 - Otherwise, the group state is `locking` if at least one group member is `locking`.
+- Otherwise, the group state is `open` if at least one group member is `open`.
 - Otherwise, the group state is `unlocking` if at least one group member is `unlocking`.
-- Otherwise, the group state is `unlocked` if at least one group member is `unlocked`.
-- Otherwise, the group state is `locked`.
+- Otherwise, the group state is `locked` if all group members are `locked`.
+- Otherwise, the group state is `unlocked`.
 
 ### Notify entity groups
 

source/_integrations/habitica.markdown

@@ -31,6 +31,7 @@ related:
     title: To-do list card
   - url: https://habitica.com/
     title: Habitica
+ha_quality_scale: platinum
 ---
 
 The Habitica {% term integration %} enables you to monitor your adventurer's progress and stats from [Habitica](https://habitica.com/) in Home Assistant and seamlessly integrates your to-do's, daily tasks, and many more things.

source/_integrations/heicko.markdown

@@ -7,7 +7,7 @@ ha_domain: heicko
 ha_integration_type: virtual
 ha_supporting_domain: motion_blinds
 ha_supporting_integration: Motionblinds
-ha_release: 2025.3
+ha_release: 2020.12
 ha_codeowners:
   - '@starkillerOG'
 ha_config_flow: true

source/_integrations/heos.markdown

@@ -218,6 +218,11 @@ data:
 | `entity_id`            | yes      | Remove this media player from any player groups. |
 
 
+{% note %}
+
+Actions may fail if they cannot be processed by the HEOS device. For example, attempting to call `media_player.clear_playlist` when the queue is empty will result in an error. To prevent this from halting a script or automation, set [`continue_on_error: true`](/docs/scripts/#continuing-on-error) in the action call.
+{% endnote %}
+
 ## Supported devices
 
 Denon and Marantz do not currently publish an inventory of HEOS-enabled devices, however, many receiver and hi-fi products began including HEOS since 2013. Consult your product model to confirm support:

source/_integrations/here_travel_time.markdown

@@ -20,7 +20,9 @@ The `here_travel_time` sensor provides travel time from the [HERE Routing API](h
 
 You need to register for an API key by following the instructions in the [API Developer Guide](https://www.here.com/docs/bundle/routing-api-developer-guide-v8/page/topics/send-request.html).
 
-HERE offers a Limited Plan which includes 1000 free transactions per day. If you are not [updating sensors on demand](#updating-sensors-on-demand-using-automation), you can track 3 routes without exceeding the limit. You can provide payment details to increase this to 5000 free transactions per day. More information can be found [on the pricing page](https://www.here.com/get-started/pricing)
+HERE offers a Limited Plan which includes 1000 free transactions per day. If you are not [updating sensors on demand](#updating-sensors-on-demand-using-automation), you can track 3 routes without exceeding the limit.
+
+You can provide payment details if you want to pay for unlimited transactions. Be aware that the amount of transactions included for free in the paid plan might be _less_ than the 1000 transactions per day in the free plan. More information can be found [on the pricing page](https://www.here.com/get-started/pricing)
 
 {% include integrations/config_flow.md %}
 

source/_integrations/home_connect.markdown

@@ -17,6 +17,7 @@ ha_domain: home_connect
 ha_codeowners:
   - '@DavidMStraub'
   - '@Diegorro98'
+  - '@MartinHjelmare'
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
@@ -41,31 +42,10 @@ The Home Connect integration allows users to integrate their home appliances sup
 - Control the light of your appliances.
 - Adjust the appliance settings.
 
-The integration will add one Home Assistant device for each connected home appliance which will have the following entities:
-
-- A power switch
-- If the device has programs:
-  - Two select entities that will allow you to select and start a program between the available ones.
-  - A timestamp sensor for remaining time and a numeric sensor for the progress percentage.
-- Light:
-  - Hoods:
-    - Functional light: on/off and brightness
-    - Ambient light: on/off, brightness, HSV and RGB
-  - Dishwasher: on/off, brightness, HS and RGB
-  - Cooling appliances: Both, external and internal lights, on/off and brightness
-- Numbers that set the temperature of cooling appliances.
-- Time for alarm clock for cooktops and ovens.
-- Multiple sensors that report the different states and events reported by the appliance.
-- Binary sensors that show binary states of the appliance.
-
 {% note %}
 Note that it depends on the appliance and on API permissions which of the features are supported.
 {% endnote %}
 
-{% note %}
-Some devices only have the state `on` and turn off is not supported by the appliance, check [power state availability at Home Connect API documentation](https://api-docs.home-connect.com/settings/#power-state) for more information.
-{% endnote %}
-
 ## Supported devices
 
 You can find information about supported devices on the [Home Connect website](https://www.home-connect.com/global/smart-home-appliances).
@@ -110,14 +90,6 @@ Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://hom
 
 The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details.
 
-## Removing the integration
-
-This integration follows standard integration removal. No extra steps are required.
-
-{% include integrations/remove_device_service.md %}
-
-After deleting the integration, go to [your applications at the Home Connect Developer portal](https://developer.home-connect.com/applications), find the application that you were using for Home Assistant, click on details and click on "Delete Application".
-
 ## Supported functionality
 
 {% note %}
@@ -1002,7 +974,6 @@ Changes a setting.
 | `key` | no | Key of the setting. |
 | `value` | no | Value of the setting. |
 
-
 ## Automation examples
 
 Get started with these automation examples
@@ -1077,6 +1048,12 @@ actions:
 This integration uses server-sent events from the Home Connect API to receive live updates from the appliances.
 When the configuration entry is loaded or after a streaming error (for example after disconnection), the integration will request all data (such as appliance info, available commands, programs, settings, and status) for all appliances.
 If a new appliance is added to the account, the integration will request data for the new appliance and expose the related entities automatically.
+
+## Known limitations
+
+- The Home Connect API does not fully match the Home Connect app. Some programs, options, or settings available in the app may not be accessible or usable via the API.
+- This integration supports only one integration entry, as the Home Connect API does not allow for the unique identification of an account.
+
 ## Troubleshooting
 
 ### I could not configure the Home Connect integration
@@ -1143,8 +1120,10 @@ To try to solve the above issues, follow these steps:
    - [Home Connect service and contact](https://www.home-connect.com/us/en/support/contact-and-service)
    - [Home Connect developer Help & Support](https://developer.home-connect.com/support)
 
-## Known limitations
+## Removing the integration
 
-- The Home Connect API does not fully match the Home Connect app. Some programs, options, or settings available in the app may not be accessible or usable via the API.
-- This integration supports only one integration entry, as the Home Connect API does not allow for the unique identification of an account.
+This integration follows standard integration removal. No extra steps are required.
 
+{% include integrations/remove_device_service.md %}
+
+After deleting the integration, go to [your applications at the Home Connect Developer portal](https://developer.home-connect.com/applications), find the application that you were using for Home Assistant, click on details and click on "Delete Application".

source/_integrations/iometer.markdown

@@ -3,17 +3,18 @@ title: IOmeter
 description: Instructions on how to integrate IOmeter within Home Assistant.
 ha_release: 2025.3
 ha_category:
-  - Sensor
   - Energy
+  - Sensor
 ha_codeowners:
   - '@MaestroOnICe'
-  - '@iometer-gmbh'
 ha_quality_scale: bronze
 ha_domain: iometer
-ha_integration_type: integration
+ha_integration_type: device
 ha_iot_class: Local Polling
 ha_config_flow: true
 ha_zeroconf: true
+ha_platforms:
+  - sensor
 ---
 
 The **IOmeter** {% term integration %} fetches data from your [IOmeter](https://iometer.de/produkt/) device, by using the local HTTP API.

source/_integrations/islamic_prayer_times.markdown

@@ -58,7 +58,7 @@ Default: Islamic Society of North America
 
 A prayer times calculation method. Methods identify various schools of thought about how to compute the timings. If not specified, it defaults to Islamic Society of North America.
 
-### Latatude Adjustment Method
+### Latitude Adjustment Method
 
 Default: Middle of the night 
 

source/_integrations/jellyfin.markdown

@@ -9,7 +9,7 @@ ha_category:
 ha_release: '2021.12'
 ha_iot_class: Local Polling
 ha_codeowners:
-  - '@j-stienstra'
+  - '@RunC0deRun'
   - '@ctalkington'
 ha_config_flow: true
 ha_domain: jellyfin

source/_integrations/lg_thinq.markdown

@@ -127,29 +127,30 @@ The properties for controlling both the temperature and wind strength of the app
 
 | Device | Property |
 | ------ | -------- |
-| Air Conditioner | Current temperature<br>Fan mode<br>HVAC mode<br>Preset mode<br>Temperature<br>Temperature cool<br>Temperature heat<br>Unit |
+| Air Conditioner | Current temperature<br>Fan mode<br>Swing mode<br>Swing horizontal mode<br>HVAC mode<br>Preset mode<br>Temperature<br>Temperature cool<br>Temperature heat<br>Unit |
 | 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.
+A notification message pushed from the server is represented as an event platform. The **Notification codes** shows the full support range, and you can check the range of your device through the developer tools.
 
-| Device | Property |
-| ------ | -------- |
-| Air Conditioner | Notification |
-| Air Purifier| Notification |
-| Air Purifier Fan | Notification |
-| Dehumidifier | Notification |
-| Dish Washer | Error<br>Notification |
-| Humidifier | Notification |
-| Kimchi Refrigerator | Notification |
-| Microwave Oven | Notification |
-| Oven | Notification |
-| Refrigerator | Notification |
-| Robot Cleaner | Error<br>Notification |
-| Stick Cleaner | Notification |
-| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Error<br>Notification |
-| Wine Cellar | Notification |
+| Device | Property | Notification codes |
+| ------ | -------- | ---------- |
+| Air Conditioner | Notification | water_is_full |
+| Air Purifier| Notification | lack_of_water, time_to_clean_filter, pollution_is_high, time_to_change_filter |
+| Air Purifier Fan | Notification | time_to_change_filter |
+| Dehumidifier | Notification | water_is_full |
+| Dish Washer | Error<br>Notification | cleaning_is_complete, error_during_cleaning, water_leak_has_occurred, rinse_is_not_enough, salt_refill_is_needed |
+| Humidifier | Notification | time_to_change_filter, lack_of_water |
+| Kimchi Refrigerator | Notification | door_is_open |
+| Microwave Oven | Notification | none |
+| Oven | Notification | preheating_is_complete, cooking_is_complete, time_to_clean, error_has_occurred |
+| Refrigerator | Notification | time_to_change_filter, time_to_change_water_filter, frozen_is_complete, door_is_open |
+| Robot Cleaner | Error<br>Notification | - |
+| Stick Cleaner | Notification | charging_is_complete, time_to_clean_filter |
+| Washer<br>Dryer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Error<br>Notification | washing_is_complete, error_during_washing, drying_is_complete, drying_failed |
+| Styler | Error<br>Notification | styling_is_complete, error_has_occurred |
+| Wine Cellar | Notification | door_is_open |
 
 ### Fan
 
@@ -172,7 +173,7 @@ A read-write property which has a numeric value is represented as a number platf
 | Microwave Oven | Fan<br>Light |
 | Oven | Temperature |
 | Refrigerator | Temperature |
-| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Delay ends in |
+| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Delayed start/end |
 | Water Heater | Temperature |
 | Wine Cellar | Light<br>Temperature |
 
@@ -200,13 +201,13 @@ A read-write property which has only two states that can be toggled is represent
 
 | Device | Property |
 | ------ | -------- |
-| Air Conditioner | Energy saving |
+| Air Conditioner | Power<br>Lighting<br>Energy saving |
 | Air Purifier | Power |
 | Air Purifier Fan | Heating<br>Power<br>UVnano |
 | Dehumidifier | Power |
 | Humidifier | Auto mode<br>Heating<br>Mood light<br>Power<br>Sleep mode |
-| Refrigerator | Ice plus<br>Quick freeze |
-| System Boiler | Hot water |
+| Refrigerator | Express mode<br>Express cool<br>Quick freeze |
+| System Boiler | Power<br>Hot water |
 | Wine Cellar | Ventilation |
 
 ### Vacuum
@@ -217,6 +218,14 @@ The properties for controlling the clean operations of the appliance are represe
 | ------ | -------- |
 | Robot Cleaner | Battery<br>Current status<br>Operation |
 
+### Water heater
+
+The properties for controlling the operating mode and temperature are represented as a water_heater platform.
+
+| Device | Property |
+| ------ | -------- |
+| Water heater | Mode<br>Current temperature<br>Temperature |
+
 ### Sensor
 
 A read-only property which has states is represented as a sensor platform.
@@ -228,8 +237,8 @@ A read-only property which has states is represented as a sensor platform.
 | 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<br>Schedule turn-off<br>Schedule turn-on |
 | Cooktop | Current status<br>Power level |
 | Dehumidifier | Humidity<br>Operating mode |
-| Dish Washer | Current cycle<br>Current status<br>Rinse aid dispenser level<br>Softening level<br>Delay in<br>Remaining time<br>Total time |
-| Home Brew| Brewing duration<br>Brewing period<br>Current status<br>Flavor<br>Homebrew recipe<br>Hops<br>Recipe progress<br>Wort<br>Yeast |
+| Dish Washer | Current cycle<br>Current status<br>Rinse aid dispenser level<br>Softening level<br>Delayed start<br>Remaining time<br>Total time |
+| Home Brew| Brewing duration<br>Brewing period<br>Current status<br>First flavor<br>Second flavor<br>Homebrew recipe<br>First hop<br>Second hop<br>Recipe progress<br>Wort<br>Yeast |
 | 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 | Fresh air filter<br>Temperature |
 | Microwave Oven | Current status |
@@ -238,16 +247,16 @@ A read-only property which has states is represented as a sensor platform.
 | Refrigerator | Fresh air filter<br>Water filter used |
 | Robot Cleaner | Current status<br>Operating mode<br>Running time |
 | Stick Cleaner | Battery<br>Current status<br>Operating mode |
-| Water Heater | Temperature |
+| System Boiler | Indoor temperature<br>Inlet temperature<br>Outlet temperature |
 | Water Purifier | High-temp sterilization<br>Type<br>UVnano|
-| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Current status<br>Delay in<br>Remaining time<br>Total time |
+| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Current status<br>Delayed start/end<br>Remaining time<br>Total time<br>Cycles |
 
-### Custom card configuration
+## User guide
+### 1. Custom card configuration (HACS)
 
-#### Timer Bar Card
-
-- Supported devices: Washer, Dryer, Styler, Dish washer
-- Entities: sensor.washer_current_status, sensor.washer_remaining_time, sensor.washer_total_time
+**- Timer Bar Card**
+> - Supported devices: Washer, Dryer, Styler, Dish washer
+> - Used entities: sensor.washer_**current_status**, sensor.washer_**remaining_time**, sensor.washer_**total_time**
 
 ```yaml
 type: custom:timer-bar-card
@@ -274,6 +283,29 @@ entities:
     invert: true
 ```
 
+### 2. Automation
+**- Notification, Error event**
+> - Guide: [Automating on event](https://www.home-assistant.io/integrations/event/#automating-on-a-button-press)
+> - Important: guide's step 3, 4
+> - You can select the state change you want to act as trigger in step 4
+```yaml
+alias: lack of water example
+description: Toggle switch when air purifier's lack_of_water
+triggers:
+  - trigger: state
+    entity_id:
+      - event.purifier_notification
+actions:
+  - condition: state
+    entity_id: event.purifier_notification
+    attribute: event_type
+    state: lack_of_water
+  - type: toggle
+    device_id: xxxxxxxx
+    entity_id: xxxxxxxx
+    domain: switch
+```
+
 ## Troubleshooting
 
 ### Setup
@@ -293,5 +325,9 @@ The LG ThinQ integration will work properly after some time.
 
 ## Debugging / Issue report
 The LG ThinQ integration will show additional information by enabling log configuration.
-1. Enable debug logging in /config/integrations/integration/lg_thinq,
-2. Please report your device info (screenshot including name, device type, entities) and logs.
+1. [Enable debug logging](/docs/configuration/troubleshooting/#enabling-debug-logging).
+   - If you change **Enable** to **Disable**, the log will be saved to the download folder.
+2. When reporting an issue:
+   - Provide screenshots of your device configuration (including device name, type, and entities).
+   - Include the debug logs.
+   - Describe the expected behavior and what's not working.

source/_integrations/linak.markdown

@@ -1,22 +1,22 @@
 ---
 title: LINAK
-description: Connect and control your LINAK motorized desks the IKEA Idåsen Desk integration
+description: Connect and control your LINAK devices using the IKEA Idasen Desk integration
 ha_category:
   - Cover
 ha_domain: linak
-ha_iot_class: Local Push
 ha_integration_type: virtual
 ha_supporting_domain: idasen_desk
 ha_supporting_integration: IKEA Idåsen Desk
-ha_release: '2025.3'
+ha_release: '2023.10'
 ha_codeowners:
   - '@abmantis'
 ha_config_flow: true
-ha_quality_scale: bronze
 ha_platforms:
   - button
   - cover
   - sensor
+ha_iot_class: Local Push
+ha_bluetooth: true
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/linx.markdown

@@ -7,7 +7,7 @@ ha_domain: linx
 ha_integration_type: virtual
 ha_supporting_domain: motion_blinds
 ha_supporting_integration: Motionblinds
-ha_release: 2025.2
+ha_release: 2020.12
 ha_codeowners:
   - '@starkillerOG'
 ha_config_flow: true

source/_integrations/lock.markdown

@@ -27,6 +27,7 @@ A lock entity can have the following states:
 - **Opening**: Indication of whether the lock is currently opening.
 - **Locked**: The lock is currently locked.
 - **Locking**: The lock is in the process of being locked.
+- **Unlocked**: The lock is currently unlocked.
 - **Unlocking**: The lock is in the process of being unlocked.
 - **Unavailable**: The entity is currently unavailable.
 - **Unknown**: The state is not yet known.

source/_integrations/mastodon.markdown

@@ -12,6 +12,7 @@ ha_domain: mastodon
 ha_iot_class: Cloud Polling
 ha_platforms:
   - diagnostics
+  - notify
   - sensor
 ha_integration_type: service
 ha_config_flow: true

source/_integrations/microsoft.markdown

@@ -65,7 +65,7 @@ pitch:
   type: string
   default: "`default`"
 contour:
-  description: "Change the contour of the output in percentages. This overrides the pitch setting. See the [W3 SSML specification](https://www.w3.org/TR/speech-synthesis/#pitch_contour) for what it does. Example value: `(0,0) (100,100)`."
+  description: "Change the contour of the output in percentages. This overrides the pitch setting. See the [W3 SSML specification](https://www.w3.org/TR/speech-synthesis/#pitch_contour) for what it does. Example value: `(0%, -1st) (100%, +10st)`."
   required: false
   type: string
 region:
@@ -100,6 +100,6 @@ tts:
     rate: 20
     volume: -50
     pitch: high
-    contour: (0, 0) (100, 100)
+    contour: (0%, -1st) (100%, +10st)
     region: eastus
 ```

source/_integrations/minecraft_server.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - diagnostics
   - sensor
 ha_integration_type: integration
+ha_quality_scale: silver
 ---
 
 [Minecraft](https://www.minecraft.net/en-us) is a sandbox video game developed by Mojang Studios. Minecraft servers allow players to play the game online or via a local area network with other players. The **Minecraft Server** integration lets you retrieve information from a Minecraft server within Home Assistant. Both **Java Edition** and **Bedrock Edition** servers are supported.

source/_integrations/nut.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
   - '@bdraco'
   - '@ollo69'
   - '@pestevez'
+  - '@tdfountain'
 ha_zeroconf: true
 ha_platforms:
   - diagnostics

source/_integrations/onedrive.markdown

@@ -1,5 +1,5 @@
 ---
-title: Microsoft OneDrive
+title: OneDrive
 description: Instructions on how to setup OneDrive to be used with backups.
 ha_release: 2025.2
 ha_category:
@@ -13,7 +13,9 @@ ha_integration_type: service
 related:
   - docs: /common-tasks/general/#backups
     title: Backups
-ha_quality_scale: bronze
+ha_quality_scale: platinum
+ha_platforms:
+  - sensor
 ---
 
 This integration allows you to use [Microsoft OneDrive](https://www.microsoft.com/en-us/microsoft-365/onedrive/online-cloud-storage) for [Home Assistant Backups](/common-tasks/general/#backups).

source/_integrations/opower.markdown

@@ -142,3 +142,16 @@ Your **Configure gas consumption** should now look like this:
 With the above changes your (**{% my config_energy title="Settings > Dashboards > Energy" %}**) page should now look like this:
 
 ![Screenshot Energy Configuration](/images/integrations/opower/energy_config.png)
+
+## Known limitations
+
+- There is a delay, often for up to a few days, for sensors and statistics to have up-to-date data.
+- For some utilities, there are no sensors added by this integration.
+- For some utilities, the sensors might disappear or become unavailable at the beginning of your bill period.
+- Sensors for typical monthly usage and cost are not populated for accounts younger than a year.
+- Many utilities provide granular usage (for example, daily or hourly) but not cost. They only provide cost for billing periods (for example, month). This results in showing 0 for cost.
+
+## Troubleshooting
+
+- Before opening an issue, ensure you can access the energy usage section/dashboard on your utility website and verify that the data is up-to-date there.
+- In your energy dashboard in Home Assistant, make sure you use the statistics and not the sensors.

source/_integrations/pglab.markdown

@@ -4,16 +4,17 @@ description: Instructions on how to integrate PG LAB Electronics with Home Assis
 ha_category:
   - Switch
   - Sensor
-ha_release: "2025.3"
+ha_release: '2025.3'
 ha_iot_class: Local Push
 ha_config_flow: true
 ha_codeowners:
-  - "@pglab-electronics"
+  - '@pglab-electronics'
 ha_domain: pglab
 ha_platforms:
   - switch
   - sensor
 ha_integration_type: integration
+ha_quality_scale: bronze
 ---
 
 The **PG LAB Electronics** {% term integrations %} allows you to control [PG LAB Electronics](https://www.pglab.dev/) devices in Home Assistant.

source/_integrations/picnic.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
   - '@corneyl'
+  - '@codesalatdev'
 ha_domain: picnic
 ha_platforms:
   - sensor

source/_integrations/qbus.markdown

@@ -4,6 +4,7 @@ description: Instructions on how to integrate your Qbus installation with Home A
 ha_category:
   - Switch
 ha_platforms:
+  - light
   - switch
 ha_iot_class: Local Push
 ha_codeowners:

source/_integrations/roborock.markdown

@@ -24,6 +24,7 @@ ha_platforms:
   - diagnostics
   - image
   - number
+  - scene
   - select
   - sensor
   - switch

source/_integrations/smart_rollos.markdown

@@ -7,7 +7,7 @@ ha_domain: smart_rollos
 ha_integration_type: virtual
 ha_supporting_domain: motion_blinds
 ha_supporting_integration: Motionblinds
-ha_release: 2025.3
+ha_release: 2020.12
 ha_codeowners:
   - '@starkillerOG'
 ha_config_flow: true

source/_integrations/snoo.markdown

@@ -1,5 +1,5 @@
 ---
-title: Snoo
+title: Happiest Baby Snoo
 description: Instructions on how to integrate Snoo into Home Assistant
 ha_category:
   - Sensor
@@ -12,6 +12,7 @@ ha_domain: snoo
 ha_platforms:
   - sensor
 ha_integration_type: integration
+ha_quality_scale: bronze
 ---
 
 The [Snoo](https://www.happiestbaby.com/products/snoo-smart-bassinet) is a smart bassinet made by [Happiest Baby](https://www.happiestbaby.com/) that helps get your baby to sleep and helps keep them asleep.

source/_integrations/steam_online.markdown

@@ -32,7 +32,12 @@ Go to your profile, select "Edit Profile", "Privacy Settings".
 
 You need a [free API key](https://steamcommunity.com/dev/apikey) to use the platform.
 
-To find an account's 64-bit SteamID on profiles without a custom URL you can check the URL of the profile page, the long string of numbers at the end is the 64-bit SteamID. If the profile has a custom URL you will have to copy the URL into [STEAMID I/O](https://steamid.io/) to find the 64-bit SteamID.
+To find an account's 64-bit SteamID:
+
+1. Open Steam.
+2. Open the dropdown menu labeled with your username.
+3. Select **Account details**.
+   - Your **Steam ID** is displayed just below the label **Your-Account-Name Account**.
 
 ## Examples
 

source/_integrations/tado.markdown

@@ -7,13 +7,12 @@ ha_category:
   - Hub
   - Presence detection
   - Sensor
+  - Switch
   - Water heater
   - Weather
-  - Switch
 ha_release: 0.41
 ha_iot_class: Cloud Polling
 ha_codeowners:
-  - '@chiefdragon'
   - '@erwindouna'
 ha_domain: tado
 ha_config_flow: true
@@ -23,6 +22,7 @@ ha_platforms:
   - climate
   - device_tracker
   - sensor
+  - switch
   - water_heater
 ha_dhcp: true
 ha_integration_type: integration

source/_integrations/thermopro.markdown

@@ -12,6 +12,7 @@ ha_codeowners:
 ha_domain: thermopro
 ha_config_flow: true
 ha_platforms:
+  - button
   - sensor
 ha_integration_type: integration
 ---

source/_integrations/tplink.markdown

@@ -204,6 +204,7 @@ If required, you can manually trigger an update via **Developer tools** > **Acti
 - Ensure you have enabled **Tapo Lab** > **Third-Party Compatibility** in the Tapo app. You may need to factory reset and re-add to the Tapo app after this step.
 - Disable or remove any custom integrations that interact with TPLink devices supported by this integration.
 - Ensure stable network connectivity between Home Assistant and the device.
+- Unplug existing TP-Link/Tapo devices on your network before onboarding a new device. The TP-Link Simple Setup (TSS) protocol, which shares credentials from existing devices, can break authentication. If issues persist, factory reset the new device and re-add it without other TP-Link devices active.
 - Check the [reported connection solutions](#reported-connection-solutions) section below.
 - Check the [supported device list](#supported-devices) to see if the device is tested to work with the integration. 
 - Try running the [kasa tool](https://github.com/python-kasa/python-kasa) to connect to the device. An easy way to do this is to [install uv](https://docs.astral.sh/uv/getting-started/installation/) and run `uvx --from python-kasa kasa --username <tplink cloud username> --password <tplink cloud password>`

source/_integrations/ublockout.markdown

@@ -7,7 +7,7 @@ ha_domain: ublockout
 ha_integration_type: virtual
 ha_supporting_domain: motion_blinds
 ha_supporting_integration: Motionblinds
-ha_release: 2025.3
+ha_release: 2020.12
 ha_codeowners:
   - '@starkillerOG'
 ha_config_flow: true

source/_integrations/velbus.markdown

@@ -27,6 +27,7 @@ ha_platforms:
   - sensor
   - switch
 ha_integration_type: hub
+ha_quality_scale: bronze
 ---
 
 The **Velbus** {% term integration %} is used to control [Velbus](https://www.velbus.eu/?lang=en) modules. It supports the Velbus USB, Velbus serial and a TCP/IP gateway.

source/_integrations/vesync.markdown

@@ -23,6 +23,7 @@ ha_platforms:
   - humidifier
   - light
   - number
+  - select
   - sensor
   - switch
 ha_integration_type: integration

source/_integrations/weatherflow_cloud.markdown

@@ -1,5 +1,5 @@
 ---
-title: WeatherFlow Cloud
+title: WeatherflowCloud
 description: Instructions on the Cloud based WeatherFlow integration
 ha_release: 2024.3
 ha_category:
@@ -84,4 +84,3 @@ There is not a straight 1-1 mapping between the Home Assistant supported weather
 | snow | snowy |
 | thunderstorm | lightning |
 | windy | windy |
-

source/_posts/2025-02-27-apollo-joins-wwha.markdown

@@ -0,0 +1,50 @@
+---
+layout: post
+title: "Apollo joins the Works With Home Assistant Program"
+description: "Adding three devices, including their community favorite presence and air quality multisensors."
+date: 2025-02-27 00:00:01
+date_formatted: "February 27, 2025"
+author: Miranda Bishop
+comments: true
+categories: Announcements
+og_image: /images/blog/2025-02-apollo/art.jpg
+---
+
+<img src='/images/blog/2025-02-apollo/art.jpg' style='border: 0;box-shadow: none;' alt="Apollo wwha logo">
+
+[Apollo Automation](https://apolloautomation.com/) has joined the [Works with Home Assistant](https://partner.home-assistant.io/) program. Certifying three of their newest devices, including their community favorite presence and air quality multisensors, giving users the best possible experience when using these devices with Home Assistant.
+
+Notably, these are the first [ESPHome](https://esphome.io/index.html)-based devices to receive Works with Home Assistant certification. Apollo is one of the first movers in an important trend that we're very excited about: Home Assistant community members turning their open projects into viable businesses that support a thriving Open Home ecosystem.
+
+<!--more-->
+
+## Background
+
+Apollo Automation is a growing family-run business rooted in the Home Assistant and ESPHome communities. And yes, they're named after their German Shepherd, Apollo 🐕.
+
+<div class="alert">
+    <p>Apollo Automation is built by and for the Home Assistant community. We believe in open smart home technology that gives users control, privacy, and flexibility. Joining the Works With Home Assistant program is a natural step for us, ensuring our devices integrate seamlessly while supporting the ecosystem we love. Home Assistant allows users to create powerful smart homes, and we are excited to contribute by making high-quality, reliable hardware that enhances the experience for everyone.</p>
+    <em style="text-align: right; display: block;">- Justin Bunton, Co-Founder, Apollo Automation</em>
+</div>
+
+Two years ago, they started sharing their designs for a new impressively small ESPHome-powered multisensor with the community. Getting feedback, sharing iterations, and working collaboratively, they turned that sensor into a full-fledged product, which was built to work with Home Assistant. They have continued this open, community-first approach and have now built several even more refined multisensors.
+
+<p class='img'><img src='/images/blog/2025-02-apollo/multisensor.jpg' style='border: 0;box-shadow: none;' alt="Apollo MSR-2 multisensor">
+A multisensor for ants? 🐜</p>
+
+Home Assistant is the [only true smart home platform](https://newsletter.openhomefoundation.org/true-platforms-let-you-create/) because it gives everyone full control to build and create. [ESPHome](/integrations/esphome/) is the ultimate smart device platform, and it is fostering an entirely new ecosystem of Open Home projects. ESPHome works fully locally, and it's a modder's paradise, allowing users to build DIY smart home devices (check out the [getting started with ESPHome guide](https://esphome.io/guides/getting_started_hassio.html)).
+
+Creators can also use it to build pre-built, plug-and-play products that give users a really seamless experience. With devices being discovered and easily added to your Wi-Fi network and Home Assistant, along with a one-click update within Home Assistant.
+
+ESPHome and Home Assistant allows anyone to turn their passion for building cool things into a career, and the things they build help support a more vibrant Open Home. Apollo is an exciting new partner for the Works with Home Assistant program and should serve as an inspiration to all aspiring makers in our community.
+
+## Devices
+Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box. Any company joining also commits to providing long-term support and firmware updates, while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the [Open Home Foundation](https://www.openhomefoundation.org/), and it is the support of [Home Assistant Cloud](/cloud/) subscribers that funds this work.
+
+Apollo has chosen first to certify three products, which include:
+
+- [MTR-1 Multi-Target Radar Multisensor For Home Assistant (LD2450)](https://apolloautomation.com/products/mtr-1) - A tiny, but powerful radar-based (mmWave) presence sensor that can pack in many other sensors.
+- [MSR-2 mmWave Multisensor For Home Assistant (LD2410B)](https://apolloautomation.com/products/msr-2) - An even smaller multisensor that is the successor of the initial community feedback-driven design.
+- [AIR-1 Air Quality Sensor For Home Assistant](https://apolloautomation.com/products/air-1) - A small air quality multisensor that can be extended to incorporate a huge variety of sensors.
+
+We anticipate that Apollo will bring more of their lineup into the program, and we are excited to see their new innovations going forward! This is just the start of a year of many new Works with Home Assistant announcements, so please stay tuned!

source/_posts/2025-03-05-music-assistants-next-big-hit.markdown

@@ -0,0 +1,95 @@
+---
+layout: post
+title: "Music Assistant's next big hit"
+description: "Spotify Connect, Assist streaming, podcasts, audiobooks, Apple Music, a full EQ, and more!"
+date: 2025-03-05 00:00:01
+date_formatted: "March 5, 2025"
+author: Marcel van der Veldt
+comments: true
+categories: Music-Assistant
+og_image: /images/blog/2025-03-music-assistant/art.jpg
+---
+
+<p><img src='/images/blog/2025-03-music-assistant/art.jpg' alt="Music Assistants next big hit" class='no-shadow' /></p>
+
+Over the past several months, [Music Assistant](https://www.music-assistant.io/) has been hitting all the right notes with new features, greater stability, and a crescendo of contributors who keep pushing the project forward. If you're [unfamiliar with Music Assistant](/blog/2024/05/09/music-assistant-2/#what-is-music-assistant), it allows you to merge your libraries from leading audio streaming providers and local files, letting you play them on the most popular smart speakers. Since our [last update](/blog/2024/05/09/music-assistant-2/), Music Assistant has had a couple of big releases, but our most recent might just be our platinum record 💿, with a lot of new functionality coming in version 2.4. In case you've missed the last few updates, here are the biggest additions.
+
+**Table of contents**
+- [Optimized for Assist](#say-my-name)
+- [External audio & Spotify Connect](#across-the-universe)
+- [Podcasts & Audiobooks](#radio-ga-ga)
+- [More players and providers](#new-sensation)
+- [Equalizer control & features](#all-about-that-bass)
+- [Home Assistant improvements](#master-of-puppets)
+- [More stable streaming](#d-d-dont-dont-stop-the-beat)
+- [Get Music Assistant 2.4 today!](#drop-it-like-its-hot)
+
+<!--more-->
+
+### "Say My Name"
+<h4 style="margin-top: -1em; opacity: .67;">Optimized for Assist</h4>
+<p class="img"><img src='/images/blog/2025-03-music-assistant/voice_ma.jpg' alt="audiobooks page"/>We should have called it Hi-Fi edition</p>
+
+The most recent release has some great advancements for [Assist](/voice_control/) devices, like the [Home Assistant Voice Preview Edition](/voice-pe/). We've been working closely with the [ESPHome](https://esphome.io/) team to ensure the most optimal audio streaming experience, which has helped make Assist devices into very capable media players. The community has even added some great functionality to fully [control your media player with your voice](https://github.com/music-assistant/voice-support), including choosing songs, artists, and more. Voice Preview Edition has a high-quality DAC that provides very clean audio playback from its 3.5mm jack, allowing you to stream lossless audio to connected speakers (this $59 device puts some of my expensive Hi-Fi gear to shame!).
+
+### "Across the Universe"
+<h4 style="margin-top: -1em; opacity: .67;">External audio & Spotify Connect</h4>
+<p class="img"><img src='/images/blog/2025-03-music-assistant/spotify_connect.jpg' alt="Spotify Connect on a Voice PE"/>Spotify Connect on Voice Preview Edition</p>
+
+Another feature in the latest release is support for "external audio sources", which can be provided either by players themselves (source control) or with plugins. The first plugin to deliver this functionality is Spotify Connect. It's the easiest way to use Spotify with Music Assistant, and can be enabled on any player. This makes any Music Assistant supported device a Spotify Connect supported device (can confirm, Voice Preview Edition is great for this). [To get started](https://www.music-assistant.io/plugins/spotify-connect/) go to Music Assistant's settings, add the Spotify Connect Plugin, choose the devices you would like it to use, and within Spotify you will see the device as a player. Just note, Spotify Connect requires a Premium account to work.
+
+We've got our sights set on adding even more plugins like this down the line (AirPlay, anyone?). We're also hard at work making the whole setup process super simple, particularly for those using the Voice Preview Edition who might not need every single Music Assistant feature, but still want this simple casting capability.
+
+### "Radio Ga Ga"
+<h4 style="margin-top: -1em; opacity: .67;">Podcasts & Audiobooks</h4>
+
+<p class="img"><img src='/images/blog/2025-03-music-assistant/audiobooks.png' alt="audiobooks page"/>The full book's progress is tracked, and chapters are clearly shown</p>
+
+Your library just got a whole lot bigger! Music Assistant now has native support for podcasts and audiobooks. For podcasts, several providers have been added, including [Subsonic](https://www.music-assistant.io/music-providers/subsonic/), [YouTube](https://www.music-assistant.io/music-providers/youtube-music/), and [RSS feeds](https://www.music-assistant.io/music-providers/podcastfeed/). Audiobooks can be added via two brand new providers: [Audible](https://www.music-assistant.io/music-providers/audible/) and [Audiobookshelf](https://www.music-assistant.io/music-providers/audiobookshelf/), or imported directly from your local files. Audiobook playback presents the entire book as a single bar with dots showing each chapter (even if the book is separated into multiple files), allowing you to really track your progress. The entire core has been adjusted to keep better track of your progress through any media, so you will always resume where you left off.
+
+<p class="img"><img src='/images/blog/2025-03-music-assistant/continue.png' alt="Continue listening section"/>The "Continue listening" section on the home page takes you back to where you left off</p>
+
+### "New Sensation"
+<h4 style="margin-top: -1em; opacity: .67;">More players and providers</h4>
+
+Shortly after our last blog post, we added support for [Apple Music](https://www.music-assistant.io/music-providers/apple-music/) which was one of the most requested additions in the comments. A couple of other new providers were added, including [iBroadcast](https://www.music-assistant.io/music-providers/ibroadcast/) and [SiriusXM](https://www.music-assistant.io/music-providers/siriusxm/). For new hardware support we've added support for [Bluesound](https://www.music-assistant.io/player-support/bluesound/) players. If you have a provider or player you love and want to see it in Music Assistant, [request it](https://github.com/orgs/music-assistant/discussions?discussions_q=sort%3Atop)---but better yet [join us in developing it](https://github.com/music-assistant/server)!
+
+### "All About That Bass"
+<h4 style="margin-top: -1em; opacity: .67;">Equalizer control & features</h4>
+
+<p class="img"><img src='/images/blog/2025-03-music-assistant/eq.png' alt="PEQ page"/>Make your own EQ settings or import pre-made settings for your speaker</p>
+
+When we released 2.0 there were basic bass and treble controls for devices, but with our new [configurable DSP](https://www.music-assistant.io/audiopipeline/) (Digital Signal Processor) you can now fine-tune your audio like never before. This includes input and output gain, along with a powerful [parametric equalizer](https://www.music-assistant.io/dsp/parametriceq/) that can be applied per player 📈. You can conveniently view the entire audio pipeline by clicking the quality indicator icon.
+
+<p><img src='/images/blog/2025-03-music-assistant/audio_path.png' alt="Music Assistants next big hit" class='no-shadow' /></p>
+
+Another useful feature added was a "[Don't stop the music](https://www.music-assistant.io/usage/#:~:text=Don%27t%20Stop%20The%20Music%20(DSTM))" mode that keeps music playing even once your queue finishes, playing similar songs from your library. Another way to keep the music playing is through lock screens and widget controls built into many popular operating systems, which can now control Music Assistant.
+
+### "Master of Puppets"
+<h4 style="margin-top: -1em; opacity: .67;">Home Assistant improvements</h4>
+
+Home Assistant was always designed to work seamlessly with Music Assistant, and it's only getting better. In the [Home Assistant 2024.12 release](/blog/2024/12/04/release-202412/#new-integrations), we gave the community a Christmas present--Music Assistant moved from HACS to being a native integration ([please migrate if you haven't yet](https://www.music-assistant.io/integration/migrate/)).
+
+Many people now add all their players to Music Assistant first and then integrate Music Assistant with Home Assistant, eliminating the need to add each device separately. The most recent release added the ability to outsource any player control, including volume or turning it on/off, to a Home Assistant entity. There are other benefits to using them together, like Music Assistant [resuming audio playback](https://www.music-assistant.io/integration/announcements/) after an announcement or using Assist to find and play a song ([with or without LLMs](https://github.com/music-assistant/voice-support)).
+
+### "D-D-Don't Don't Stop the Beat"
+<h4 style="margin-top: -1em; opacity: .67;">More stable streaming</h4>
+
+One of the biggest goals for every release is to improve streaming stability across all providers and players. With every release, we've been improving stability, and since our last post, we've had a big influx of users who have been finding and helping squash bugs. There have been nice improvements to almost every provider helping with stability, speed, and quality. Just in the next patch release 2.4.3, we've improved streaming performance on slower network connections. The goal is that the music never stops.
+
+## "Praise You" - 🙏
+
+A huge thank you to everyone who contributed to this release---whether through code, testing, or feedback. Your support keeps Music Assistant evolving into the ultimate tool for managing your music, on your players.
+
+## "Drop It Like It's Hot"
+<h3 style="margin-top: -1em; opacity: .67;">Get Music Assistant 2.4 today!</h3>
+
+If you haven't updated yet, now's the time! And if you haven't used it yet, you can install Music Assistant as a Home Assistant Add-on,
+
+[<img src='https://my.home-assistant.io/badges/supervisor_addon.svg' style='border: 0;box-shadow: none;' alt="!Open your Home Assistant instance and show the dashboard of an add-on.">](https://my.home-assistant.io/redirect/supervisor_addon/?addon=d5369777_music_assistant)
+
+For more on getting started with Music Assistant, [read the documentation](https://www.music-assistant.io/installation/).
+
+Have feedback or want to contribute? Join our growing community on GitHub and Discord!
+
+Happy listening!

source/_posts/2025-03-05-release-20253.markdown

@@ -0,0 +1,619 @@
+---
+layout: post
+title: "2025.3: View those headers!"
+description: "Beautiful dashboard view headers, tons of tile card improvements and new features, better map clustering, Assist now streams responses, and integrating with SmartThings is now better than ever!"
+date: 2025-03-05 00:01:00
+date_formatted: "March 5, 2025"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2025-03/social.jpg
+---
+
+<lite-youtube videoid="TrNpNsZyGFw" videotitle="Home Assistant 2025.3 Release Party"></lite-youtube>
+
+Home Assistant 2025.3! 🎉
+
+But! Before I dive into the release, let me quickly catch you up on things you
+might have missed. There is a lot of cool stuff happening lately!
+
+We had a live stream about Assist: [**Voice chapter 9**](https://www.youtube.com/watch?v=k6VvzDSI8RU)!
+Here we announced [**Speech-to-Phrase**](/blog/2025/02/13/voice-chapter-9-speech-to-phrase/#voice-for-the-masses),
+a voice recognition technology that is blazing fast and super accurate, even
+on a Raspberry Pi! 🚀
+
+I'm also super stoked [about the announcement](/blog/2025/02/27/apollo-joins-wwha/)
+that [**Apollo Automation**](https://apolloautomation.com/) has joined the
+[**Works with Home Assistant**](https://partner.home-assistant.io) program 🥰
+
+And our friends at [**Music Assistant**](https://www.music-assistant.io/) have
+[**shipped their next big hit**](/blog/2025/03/05/music-assistants-next-big-hit/)!
+With awesome new features like Spotify Connect, Assist optimization,
+an equalizer, and podcast & audiobook support. 🎶
+
+Great stuff, right? But this release today is also packed with amazing things!
+
+After a few releases [focusing on backups](/blog/2025/02/05/release-20252/),
+we are back with a release **packed** with new features and improvements,
+mostly **focusing on dashboards**! 🤩
+
+The new abilities, the tile card's fine-tuning, and the dashboard view's new
+headers are really cool; I can’t wait to see screenshots of your dashboards
+with these new features! 📸
+
+Enjoy the release!
+
+../Frenck
+
+<!--more-->
+
+- [Dashboard view headers](#dashboard-view-headers)
+- [Tile cards](#tile-cards)
+  - [Making tile card interactions clearer](#making-tile-card-interactions-clearer)
+  - [Position tile card features](#position-tile-card-features)
+  - [New tile card features](#new-tile-card-features)
+    - [Switch toggle](#switch-toggle)
+    - [Counter actions](#counter-actions)
+  - [Tiny interaction improvements](#tiny-interaction-improvements)
+  - [Editor improvements](#editor-improvements)
+- [Assist chat now has streaming responses](#assist-chat-now-has-streaming-responses)
+- [Integrations](#integrations)
+  - [New integrations](#new-integrations)
+  - [Noteworthy improvements to existing integrations](#noteworthy-improvements-to-existing-integrations)
+  - [SmartThings](#smartthings)
+- [Other noteworthy changes](#other-noteworthy-changes)
+- [Iterating on the legends of graphs](#iterating-on-the-legends-of-graphs)
+- [Grouping/clustering of trackables on the maps](#groupingclustering-of-trackables-on-the-maps)
+- [Need help? Join the community!](#need-help-join-the-community)
+- [Backward-incompatible changes](#backward-incompatible-changes)
+- [All changes](#all-changes)
+
+## Dashboard view headers
+
+This release brings a whole new look with the ability to add headers to your
+dashboards. This allows you to add a title and welcoming text to your dashboards
+using Markdown and even templates. Additionally, this gives you a lot of space
+for badges next to the header.
+
+As always, we’ve baked in a lot of customization, with the ability to align the
+header in multiple different ways. It comes with a responsive layout by default,
+but you can also set it to always be left-aligned or center-aligned.
+
+<img class="no-shadow" src="/images/blog/2025-03/dashboard-view-header.png" alt="Screenshot showing the new header feature in the dashboard view." />
+
+The badges can also be positioned below the text (default) or above the text. A
+great visual menu makes it easy to choose how you want to organize your header.
+
+## Tile cards
+
+This release has made many improvements and fine touches to the tile card. It
+is one of the most versatile cards in Home Assistant,
+and we have made it even better!
+
+### Making tile card interactions clearer
+
+There is no doubt the tile card can do a lot, but ever since its creation,
+it has had a little flaw that you might have run into yourself…
+
+How would you know if tapping the icon on the tile card would trigger
+an action or whether it would just display more information? We have addressed
+this with some subtle visual language in this release!
+
+<img class="no-shadow" src="/images/blog/2025-03/tile-card-clear-interactions.png" alt="Screenshot showing tile cards with and without direct actions on their icons. The ones that do have a direct action have a circular background, others don't." />
+
+When tapping the icon on the tile card directly performs an action,
+like for example, turning on a light, the icon will have a circular background
+around it. In all other cases, the little circle will not be displayed.
+
+Now you know! 👍
+
+### Position tile card features
+
+Since [we added support for resizing cards](/blog/2024/07/03/release-20247/#resize-the-cards-on-your-dashboard),
+we gained the ability to make very wide tile cards. These cards have a lot of
+empty space surrounding them, which can be helpful at times.
+
+But what if you could do something useful with that space? Now you can!
+All features of a tile card can now be positioned inline in the tile card!
+
+<img class="no-shadow" src="/images/blog/2025-03/tile-card-inline-features.png" alt="Screenshot showcasing the new inline tile card features (versus the existing bottom feature" />
+
+This brings a completely new look and feel, which we are sure you will love!
+From the settings, you can add a feature, like a brightness slider, and position
+it either below (bottom) or to the right side of the icon (inline).
+
+{% note %}
+Only the first feature can be positioned inline; the rest will not be displayed.
+{% endnote %}
+
+### New tile card features
+
+This release also ships with two new tile card features that can be
+added to your entities to provide new controls. [@jpbede] contributed these,
+so a big shout out to him!
+
+[@jpbede]: https://github.com/jpbede
+
+#### Switch toggle
+
+The first addition is one that is just surprising we didn't have it before:
+A switch toggle! This allows you to toggle a switch entity directly from the
+tile card.
+
+<img class="no-shadow" src="/images/blog/2025-03/tile-card-switch-toggle.png" alt="Screenshot showing the new tile card feature for switch entities." />
+
+#### Counter actions
+
+The second addition is a counter toggle. This allows you to add a button to
+increase, decrease, or reset a counter entity directly from the tile card.
+
+<img class=" no-shadow" src="/images/blog/2025-03/tile-card-counter-actions.png" alt="Screenshot showing the new tile card feature for counter helper entities."/>
+
+### Tiny interaction improvements
+
+More tweaks to the tile card have been made to improve their interaction
+experience. For example, we now have nice little animations when you hover over
+the tile card, making it more apparent that it is interactive. Still, when you
+tap the tile card, it will show a little animation to indicate that the
+tap was registered.
+
+<center>
+<img class="no-shadow" src="/images/blog/2025-03/tile-card-interactions.gif" alt="Screenrecording showing the new tiny micro interactions added to the tile card and a small demo of using keyboard navigation" />
+</center>
+
+Another nice addition is that the tile card can now interact with your keyboard!
+Tab and shift + tab your way across the screen like the keyboard warrior you are.
+
+### Editor improvements
+
+Not just the tile card itself has been improved, but also the editor for
+the tile card has been improved. It is now clearer and easier to use.
+
+The new control gives you a better overview of what the option will do for
+the tile card.
+
+<img class="no-shadow" src="/images/blog/2025-03/card-editor-improvements.png" alt="Screenshot showing the brand new visual card editor that make it more visually clear what options do." />
+
+## Assist chat now has streaming responses
+
+If you have hooked up an LLM, like ChatGPT, to your Assist as
+a conversation agent, it will now livestream the responses to you when
+you are text chatting with it!
+
+When experimenting with larger models, or on slower hardware, LLM’s can feel
+sluggish. They only respond once the entire reply is generated, which can take
+frustratingly long for lengthy responses (you’ll be waiting a while if you ask
+it to tell you an epic fairy tale).
+
+We've added support for LLMs to stream their response to the text chat, allowing you
+to start reading while the response is being generated. A bonus side effect is
+that commands are now also faster: they will be executed as soon as they come
+in, without waiting for the rest of the message to be complete.
+
+<lite-youtube videoid="k6VvzDSI8RU" videoStartAt="3239" videotitle="Voice - Chapter 9"></lite-youtube>
+
+There was quite a lot more to tell around Assist and the new voice features;
+in case you missed it, you can read all about it in this blog post:
+
+📰 [Speech-to-Phrase brings voice home - Voice chapter 9](/blog/2025/02/13/voice-chapter-9-speech-to-phrase/)
+
+## 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:
+
+- **[Azure Storage]**, added by [@zweckj]  
+  Use Azure Storage as a target location for your backups.
+- **[IOmeter]**, added by [@MaestroOnICe]  
+  Read out your [IOmeter device] data locally.
+- **[PG LAB Electronics]**, added by [@pglab-electronics]  
+  Control your [PG LAB Electronics devices] from Home Assistant.
+- **[SensorPush Cloud]**, added by [@sstallion]  
+  Integrate your [SensorPush devices] with Home Assistant, using their
+  cloud service.
+- **[SNOO]**, added by [@Lash-L]  
+  Get the state of your [SNOO Smart Sleeper Bassinet] into Home Assistant.
+- **[WebDAV]**, added by [@jpbede]  
+  Use any WebDAV compatible service as a target location for your backups.
+
+[@jpbede]: https://github.com/jpbede
+[@Lash-L]: https://github.com/Lash-L
+[@MaestroOnICe]: https://github.com/MaestroOnICe
+[@pglab-electronics]: https://githb.com/pglab-electronics
+[@sstallion]: https://github.com/sstallion
+[@zweckj]: https://github.com/zweckj
+[Azure Storage]: /integrations/azure_storage
+[IOmeter device]: https://iometer.de/produkt/
+[IOmeter]: /integrations/iometer
+[PG LAB Electronics devices]: https://www.pglab.dev/
+[PG LAB Electronics]: /integrations/pglab
+[SensorPush Cloud]: /integrations/sensorpush_cloud
+[SensorPush devices]: https://www.sensorpush.com/
+[SNOO Smart Sleeper Bassinet]: https://www.happiestbaby.com/
+[SNOO]: /integrations/snoo
+[WebDAV]: /integrations/webdav
+
+This release also has new virtual integrations. Virtual integrations
+are stubs that are handled by other (existing) integrations to help with
+findability. These ones are new:
+
+- **[Burbank Water and Power (BWP)]**, provided by [Opower], added by [@tronikos]
+- **[Heicko]**, provided by [Motionblinds], added by [@starkillerOG]
+- **[LINAK]**, provided by [Idasen Desk], added by [@abmantis]
+- **[Linx]**, provided by [Motionblinds], added by [@starkillerOG]
+- **[Smart Rollos]**, provided by [Motionblinds], added by [@starkillerOG]
+- **[Ublockout]**, provided by [Motionblinds], added by [@starkillerOG]
+
+[@abmantis]: https://github.com/abmantis
+[@starkillerOG]: https://github.com/starkillerOG
+[@tronikos]: https://github.com/tronikos
+[Burbank Water and Power (BWP)]: /integrations/burbank_water_and_power
+[Heicko]: /integrations/heicko
+[Idasen Desk]: /integrations/idasen_desk
+[LINAK]: /integrations/linak
+[Linx]: /integrations/linx
+[Motionblinds]: /integrations/motionblinds
+[Opower]: /integrations/opower
+[Smart Rollos]: /integrations/smart_rollos
+[Ublockout]: /integrations/ublockout
+
+### 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:
+
+- [@MartinHjelmare] and [@Diegorro98] have been putting in a lot of effort to bring
+  the [Home Connect integration] to the next level. Nice!
+- Got an [ESPHome] device that is acting up? [@bdraco] has added a new option
+  to the integration to let Home Assistant shadowlog the device logs.
+  Helpful!
+- The [OpenAI conversation integration] now supports the `o1`, `o1-preview`,
+  `o1-mini`, and `o3-mini` reasoning models. Thanks, [@Shulyaka]!
+- The [Shelly integration] now supports the 4th generation of the Shelly Flood
+  sensors and added support for Shelly script events entities.
+  Thanks, [@chemelli74] and [@wjtje]!
+- Support for the [Switchbot Remote] has been added to the
+  [Switchbot integration]. Thanks, [@awahlig]!
+- UniFi version 9 introduced zone-based rules. These are now supported by
+  [Unifi integration]. Thanks, [@Samywamy10]!
+- [@Galorhallen] has added support for effects in [Govee lights]. Nice!
+
+[@awahlig]: https://github.com/awahlig
+[@bdraco]: https://github.com/bdraco
+[@chemelli74]: https://github.com/chemelli74
+[@Diegorro98]: https://github.com/Diegorro98
+[@Galorhallen]: https://github.com/Galorhallen
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@Samywamy10]: https://github.com/Samywamy10
+[@Shulyaka]: https://github.com/Shulyaka
+[@wjtje]: https://github.com/wjtje
+[ESPhome]: /integrations/esphome
+[Govee lights]: /integrations/govee_light_local
+[Home Connect integration]: /integrations/home_connect
+[OpenAI conversation integration]: /integrations/openai_conversation
+[Switchbot integration]: /integrations/switchbot
+[Switchbot Remote]: https://eu.switch-bot.com/products/switchbot-Remote
+[UniFi integration]: /integrations/unifi
+[Shelly integration]: /integrations/shelly
+
+### SmartThings
+
+The [SmartThings] integration has been completely rewritten! 🎉 In December,
+SmartThings shut down the old authentication method, but thanks to
+SmartThings' hard work and close collaboration with us, [@joostlek] was able to
+bring back the integration is back—better than ever.
+
+No more setting up routing, exposing ports, or creating developer accounts with
+access tokens—**just log in with your Samsung account**, and you’re good to go!
+
+And there’s more! Push updates now work without exposing your instance to the
+internet, making the experience faster, seamless, and more secure! 🚀
+
+A huge shoutout to our amazing community, who played a key role in this effort!
+💙 When [@joostlek] shared a guide on gathering test data, the community
+stepped up—sending in valuable test data that helped fine-tune the integration.
+This collaboration truly made a difference!
+
+[@joostlek]: https://github.com/joostlek
+[SmartThings]: /integrations/smartthings
+
+## Other noteworthy changes
+
+There are many more improvements in this release; here are some of the other
+noteworthy changes this release:
+
+- Ever upgraded Home Assistant and needed to do a hard refresh in your
+  browser to make it work again? We have been able to reduce the cases in
+  which this happens! Thanks, [@bramkragten]!
+- [@balloob] made a small change with a big impact. When you set up a new
+  integration for a new device, Home Assistant will now redirect you to the
+  device page after setting it up. Nice!
+- There is now an option to add an extra margin to the top of a section view.
+  Thanks, [@piitaya]!
+- The add/edit area dialog has been improved and compacted. They are
+  much more pleasant to use now. Thanks, [@jpbede]!
+- We now have a device class for the wind direction sensors! Thanks, [@edenhaus]!
+- [@jschlyter] has added the energy distance device class for sensors,
+  which supports the following units: `kWh/100mi`, `kWh/100km`, and `mi/kWh`,
+  including conversion between them. Awesome!
+- Media player entities that support browsing media now have a new action
+  available to [browse media as an action with a response]. Thanks, [@PeteRager]!
+- [@rikroe] has added an action to [retrieve the configuration of a schedule
+  helper]. Thanks!
+
+[@balloob]: https://github.com/balloob
+[@bramkragten]: https://github.com/bramkragten
+[@edenhaus]: https://github.com/edenhaus
+[@jpbede]: https://github.com/jpbede
+[@jschlyter]: https://github.com/jschlyter
+[@PeteRager]: https:/github.com/PeteRager
+[@piitaya]: https://github.com/piitaya
+[@rikroe]: https://github.com/rikroe
+[browse media as an action with a response]: /integrations/media_player#action-media_playerbrowse_media
+[retrieve the configuration of a schedule helper]: /integrations/schedule#action-scheduleget_schedule
+
+## Iterating on the legends of graphs
+
+Last release, we made [quite a big change to the charts](/blog/2025/02/05/release-20252/#preparing-our-graphs-for-the-future)
+by replacing the software we use to make these graphs in Home Assistant. Things
+changed behind the scenes, but our aim to start was to make it look
+and feel similar.
+
+However, we received a lot of feedback from the community that the legends shown
+on the new graphs were suboptimal. Our UX and frontend teams have been working
+hard to improve this situation and make the new graph legends more similar
+to the old ones.
+
+<center>
+<img class="no-shadow" alt="A screen recording showing expanding and collapsing the legend" src="/images/blog/2025-03/graph-legend.gif"/>
+</center>
+
+By default, we show the legend below the graph and show as many data points
+as possible. If there are too many, they will be displayed on demand using the
+little ellipsis button.
+
+When using these cards on your dashboard, if you want to always show the full
+legend, a new option will allow you to keep it fully visible.
+
+You can now also zoom in and out, by double clicking on a graph. If you want
+more control over the range you want to view in your graph, you can press the
+ctrl/cmd key and then select the range on the graph you want to zoom in on.
+
+## Grouping/clustering of trackables on the maps
+
+The map card is perfect for visualizing your entities’ locations, but when too
+many cluster together in the same spot, it can get a bit cluttered.
+
+To tackle this, we’ve introduced marker clustering, which groups nearby entities
+together, making it easier to see them at a glance. When zooming in, the markers
+‘spider’ out, showing individual entity locations with a connecting line to
+their original positions. You can temporarily disable clustering with a
+simple toggle.
+
+Thanks [@jpbede] and [@marcinbauer85] for this awesome improvement!
+
+<center>
+<img class="no-shadow" alt="The map now nicely clusters the items on the same location. This animation shows the ability to expand the cluster of items." src="/images/blog/2025-03/map-marker-clustering.gif"/>
+</center>
+
+[@jpbede]: https://github.com/jpbede
+[@marcinbauer85]: https://github.com/marcinbauer85
+
+## 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 "Automations & scripts" %}
+
+The `wait` variable and variables defined by a `response_variable` set in an
+inner scope of a script or automation now propagate to outer scopes also if
+a `variables` action is present in the inner scope.
+
+Furthermore, variables defined by a `response_variable` now also propagate
+out from `parallel` sequences. Scripts and automations which relied on the
+older (buggy) behavior might need to be adjusted.
+
+([@arturpragacz] - [#138883])
+
+[@arturpragacz]: https://github.com/jrieger
+[#138883]: https://github.com/home-assistant/core/pull/138883
+
+{% enddetails %}
+
+{% details "GPSD" %}
+
+All state attributes of the main sensor were replaced with a dedicated sensor
+Home Assistant in 2024.9. The deprecated attributes have now been removed.
+
+([@jrieger] - [#137600]) ([documentation](/integrations/gpsd))
+
+[@jrieger]: https://github.com/jrieger
+[#137600]: https://github.com/home-assistant/core/pull/137600
+
+{% enddetails %}
+
+{% details "Home Connect" %}
+
+Some programs and program switches (which are being deprecated) and program
+select entities may not be exposed anymore by the integration as they are
+missing an `aiohomeconnect` program key enumeration ([file](https://github.com/MartinHjelmare/aiohomeconnect/blob/ccfbf802884aa781eef481da92e6bccd2e6de733/src/aiohomeconnect/model/program.py#L213C1-L507C6)).
+You can get the diagnostics from the configuration entry or the device and open
+an issue or submit a PR with the generated diagnostics file on the
+[`aiohomeconnect` repository](https://github.com/MartinHjelmare/aiohomeconnect)
+to suggest the missing program(s).
+
+([@Diegorro98] - [#136116]) ([documentation](/integrations/home_connect))
+
+[@Diegorro98]: https://github.com/Diegorro98
+[#136116]: https://github.com/home-assistant/core/pull/136116
+
+---
+
+Using program and option keys that aren't in the API documentation in Home
+Connect actions will no longer work. To be able to use undocumented program or
+option keys, open an issue or submit a pull request with the required keys at
+[MartinHjelmare/aiohomeconnect](https://github.com/MartinHjelmare/aiohomeconnect).
+
+([@Diegorro98] - [#137027]) ([documentation](/integrations/home_connect))
+
+[@Diegorro98]: https://github.com/Diegorro98
+[#137027]: https://github.com/home-assistant/core/pull/137027
+
+---
+
+Multiple Home Connect config entries will not be allowed to be configured. For
+regular users where all appliances in the home are connected to the same Home
+Connect account, there should not be any reason to have more than one config
+entry since all appliances in the home will be connected to the same account
+and config entry.
+
+([@Diegorro98] - [#137088]) ([documentation](/integrations/home_connect))
+
+[@Diegorro98]: https://github.com/Diegorro98
+[#137088]: https://github.com/home-assistant/core/pull/137088
+
+{% enddetails %}
+
+{% details "MQTT" %}
+
+ Legacy `color_mode` support for MQTT JSON lights has been removed. The support
+ was deprecated in HA Core 2024.4.
+
+Users with a YAML setup have been instructed to update their configuration in
+`configuration.yaml` via repair issue flow. Deprecation issues with MQTT JSON
+lights set up through discovery were communicated via warnings in the logs.
+Using the removed parameters in discovery will not break the configuration but
+will still log a warning.
+
+([@jbouwh] - [#136996]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#136996]: https://github.com/home-assistant/core/pull/136996
+
+{% enddetails %}
+
+{% details "Proximity" %}
+
+The distance is now measured to the edge of the monitored zones (it takes the
+radius into account), instead of to the center of the zone as before. This leads
+to slightly different expected distance values, which you may have to adjust
+accordingly in your existing automations.
+
+([@Spcemarine] - [#138819]) ([documentation](/integrations/proximity))
+
+[@Spcemarine]: https://github.com/Spcemarine
+[#138819]: https://github.com/home-assistant/core/pull/138819
+
+{% enddetails %}
+
+{% details "SmartThings" %}
+
+The energy and power sensors have been removed for every device that has a
+switch. They rarely worked because there were no energy or power
+capabilities available to get data from. If you do have the capabilities,
+it will still work for you.
+
+([@joostlek] - [#138313]) ([documentation](/integrations/smartthings))
+
+---
+
+There are a lot of states that have been renamed; this might need an update in
+your automations or other configurations.
+
+- Set options for dishwasher job state sensor in SmartThings ([#139349])
+- Add translatable states to SmartThings media source input ([#139353])
+- Add translatable states to SmartThings media playback ([#139354])
+- Add translatable states to oven mode in SmartThings ([#139356])
+- Add translatable states to oven job state in SmartThings ([#139361])
+- Add translatable states to robot cleaner movement in SmartThings ([#139363])
+- Add translatable states to robot cleaner turbo mode in SmartThings ([#139364])
+- Add translatable states to washer job state in SmartThings ([#139368])
+- Add translatable states to dryer job state in SmartThings ([#139370])
+
+
+[@joostlek]: https://github.com/joostlek
+[#138313]: https://github.com/home-assistant/core/pull/138313
+[#139349]: https://github.com/home-assistant/core/pull/139349
+[#139353]: https://github.com/home-assistant/core/pull/139353
+[#139354]: https://github.com/home-assistant/core/pull/139354
+[#139356]: https://github.com/home-assistant/core/pull/139356
+[#139361]: https://github.com/home-assistant/core/pull/139361
+[#139363]: https://github.com/home-assistant/core/pull/139363
+[#139364]: https://github.com/home-assistant/core/pull/139364
+[#139368]: https://github.com/home-assistant/core/pull/139368
+[#139370]: https://github.com/home-assistant/core/pull/139370
+
+{% enddetails %}
+
+{% details "Synology DSM" %}
+
+The scan interval option has been removed, and the default of 15 minutes is
+used. If needed, there is an integration-independent and
+[common way](/common-tasks/general/#defining-a-custom-polling-interval)
+to set a custom polling interval.
+
+([@mib1185] - [#138490]) ([documentation](/integrations/synology_dsm))
+
+[@mib1185]: https://github.com/mib1185
+[#138490]: https://github.com/home-assistant/core/pull/138490
+
+{% enddetails %}
+
+{% details "TechnoVE" %}
+
+The status sensor state `high_charge_period` was renamed to `high_tariff_period`.
+
+([@Moustachauve] - [#139314]) ([documentation](/integrations/technove))
+
+[@Moustachauve]: https://github.com/Moustachauve
+[#139314]: https://github.com/home-assistant/core/pull/139314
+
+{% 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 changes are the most notable for this release:
+
+- [Backup agents](https://developers.home-assistant.io/blog/2025/02/17/backup-agents)
+- [Changed config entry state transitions](https://developers.home-assistant.io/blog/2025/02/19/new-config-entry-states)
+- [Changes to the BackupAgent API](https://developers.home-assistant.io/blog/2025/03/04/backup-agent-api-changes)
+- [Energy by distance units](https://developers.home-assistant.io/blog/2025/01/31/energy-distance-units)
+- [New checks for config flow unique ID](https://developers.home-assistant.io/blog/2025/03/01/config-flow-unique-id/)
+- [Relocate dhcp/ssdp/usb/zeroconf ServiceInfo models](https://developers.home-assistant.io/blog/2025/01/15/service-info)
+- [Support for config subentries](https://developers.home-assistant.io/blog/2025/02/16/config-subentries)
+
+[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 2025.3](/changelogs/core-2025.3)

source/dashboards/features.markdown

@@ -164,7 +164,7 @@ preset_modes:
 
 ## Counter actions
 
-Widget that displays buttons to increment, decrement and reset a [counter](/integrations/counter).
+Widget that displays buttons to increment, decrement, and reset a [counter](/integrations/counter).
 
 <p class='img'>
   <img src='/images/dashboards/features/counter_actions.png' alt='Screenshot of the tile card with counter actions feature'>

source/getting-started/onboarding.markdown

@@ -21,7 +21,7 @@ After Home Assistant has been [installed](/installation/) on your device, there
         ![Home Assistant preparation](/images/getting-started/onboarding_preparing_02.png)
      - Enter a name, username, and password.
        - Make sure the username is lowercase and contains no whitespace.
-       - {% icon "mdi:info" %} **Info**: The **Name** is the name of the person the is shown in the UI. The username is used for login.
+       - {% icon "mdi:info" %} **Info**: The **Name** is the name of the person that is shown in the UI. The username is used for login.
 
         ![Set your username and password.](/images/getting-started/onboarding_username.png)
      - Store the name, username, and password somewhere safe. There is no way to recover the owner credentials.