Merge branch 'current' into next

CODEOWNERS

@@ -117,7 +117,7 @@ source/_integrations/bluetooth_adapters.markdown @bdraco
 source/_integrations/bmw_connected_drive.markdown @gerard33 @rikroe
 source/_integrations/bond.markdown @bdraco @prystupa @joshs85 @marciogranzotto
 source/_integrations/bosch_shc.markdown @tschamm
-source/_integrations/brandt.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/brandt.markdown @imicknl
 source/_integrations/braviatv.markdown @bieniu @Drafteed
 source/_integrations/brel_home.markdown @starkillerOG
 source/_integrations/bring.markdown @miaucl @tr4nt0r
@@ -166,7 +166,7 @@ source/_integrations/coolmaster.markdown @OnFreund
 source/_integrations/counter.markdown @fabaff
 source/_integrations/cover.markdown @home-assistant/core
 source/_integrations/cover.template.markdown @home-assistant/core
-source/_integrations/cozytouch.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/cozytouch.markdown @imicknl
 source/_integrations/cpuspeed.markdown @fabaff
 source/_integrations/cribl.markdown @Bre77
 source/_integrations/crownstone.markdown @Crownstone @RicArch97
@@ -178,6 +178,7 @@ source/_integrations/datetime.markdown @home-assistant/core
 source/_integrations/deako.markdown @sebirdman @balake @deakolights
 source/_integrations/debugpy.markdown @frenck
 source/_integrations/deconz.markdown @Kane610
+source/_integrations/decorquip.markdown @starkillerOG
 source/_integrations/default_config.markdown @home-assistant/core
 source/_integrations/delijn.markdown @bollewolle @Emilv2
 source/_integrations/delmarva.markdown @tronikos
@@ -279,7 +280,7 @@ source/_integrations/fitbit.markdown @allenporter
 source/_integrations/fivem.markdown @Sander0542
 source/_integrations/fjaraskupan.markdown @elupus
 source/_integrations/flexit_bacnet.markdown @lellky @piotrbulinski
-source/_integrations/flexom.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/flexom.markdown @imicknl
 source/_integrations/flick_electric.markdown @ZephireNZ
 source/_integrations/flipr.markdown @cnico
 source/_integrations/flo.markdown @dmulcahey
@@ -325,6 +326,7 @@ source/_integrations/google.markdown @allenporter
 source/_integrations/google_assistant.markdown @home-assistant/cloud
 source/_integrations/google_assistant_sdk.markdown @tronikos
 source/_integrations/google_cloud.markdown @lufton @tronikos
+source/_integrations/google_drive.markdown @tronikos
 source/_integrations/google_generative_ai_conversation.markdown @tronikos
 source/_integrations/google_mail.markdown @tkdrob
 source/_integrations/google_photos.markdown @allenporter
@@ -341,6 +343,7 @@ source/_integrations/guardian.markdown @bachya
 source/_integrations/habitica.markdown @tr4nt0r
 source/_integrations/hardware.markdown @home-assistant/core
 source/_integrations/harmony.markdown @ehendrix23 @bdraco @mkeesey @Aohzan
+source/_integrations/harvey.markdown @Jordi1990
 source/_integrations/hassio.markdown @home-assistant/supervisor
 source/_integrations/havana_shade.markdown @starkillerOG
 source/_integrations/hdmi_cec.markdown @inytar
@@ -348,8 +351,8 @@ source/_integrations/heatmiser.markdown @andylockran
 source/_integrations/heiwa.markdown @cmroche
 source/_integrations/heos.markdown @andrewsayre
 source/_integrations/here_travel_time.markdown @eifinger
-source/_integrations/hexaom.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
-source/_integrations/hi_kumo.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/hexaom.markdown @imicknl
+source/_integrations/hi_kumo.markdown @imicknl
 source/_integrations/hikvision.markdown @mezz64
 source/_integrations/hikvisioncam.markdown @fbradyirl
 source/_integrations/hisense_aehw4a1.markdown @bannhead
@@ -366,6 +369,7 @@ source/_integrations/homeassistant_green.markdown @home-assistant/core
 source/_integrations/homeassistant_hardware.markdown @home-assistant/core
 source/_integrations/homeassistant_sky_connect.markdown @home-assistant/core
 source/_integrations/homeassistant_yellow.markdown @home-assistant/core
+source/_integrations/homee.markdown @Taraman17
 source/_integrations/homekit.markdown @bdraco
 source/_integrations/homekit_controller.markdown @Jc2k @bdraco
 source/_integrations/homematic.markdown @pvizeli
@@ -389,9 +393,9 @@ source/_integrations/hyperion.markdown @dermotduffy
 source/_integrations/ialarm.markdown @RyuzakiKK
 source/_integrations/iammeter.markdown @lewei50
 source/_integrations/iaqualink.markdown @flz
-source/_integrations/ibeacon.markdown @bdraco
 source/_integrations/icloud.markdown @Quentame @nzapponi
 source/_integrations/idasen_desk.markdown @abmantis
+source/_integrations/igloohome.markdown @keithle888
 source/_integrations/ign_sismologia.markdown @exxamalte
 source/_integrations/image.markdown @home-assistant/core
 source/_integrations/image_processing.markdown @home-assistant/core
@@ -470,6 +474,7 @@ source/_integrations/leaone.markdown @bdraco
 source/_integrations/led_ble.markdown @bdraco
 source/_integrations/legrand.markdown @cgtobi
 source/_integrations/lektrico.markdown @lektrico
+source/_integrations/letpot.markdown @jpelgrom
 source/_integrations/leviton_z_wave.markdown @home-assistant/z-wave
 source/_integrations/lg_netcast.markdown @Drafteed @splinter98
 source/_integrations/lg_thinq.markdown @LG-ThinQ-Integration
@@ -506,6 +511,8 @@ source/_integrations/martec.markdown @starkillerOG
 source/_integrations/mastodon.markdown @fabaff @andrew-codechimp
 source/_integrations/matrix.markdown @PaarthShah
 source/_integrations/matter.markdown @home-assistant/matter
+source/_integrations/mcp.markdown @allenporter
+source/_integrations/mcp_server.markdown @allenporter
 source/_integrations/mealie.markdown @joostlek @andrew-codechimp
 source/_integrations/meater.markdown @Sotolotl @emontnemery
 source/_integrations/medcom_ble.markdown @elafargue
@@ -566,7 +573,7 @@ source/_integrations/netgear.markdown @hacf-fr @Quentame @starkillerOG
 source/_integrations/netgear_lte.markdown @tkdrob
 source/_integrations/network.markdown @home-assistant/core
 source/_integrations/nexia.markdown @bdraco
-source/_integrations/nexity.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/nexity.markdown @imicknl
 source/_integrations/nextbus.markdown @vividboarder
 source/_integrations/nextcloud.markdown @mib1185
 source/_integrations/nextdns.markdown @bieniu
@@ -578,7 +585,6 @@ source/_integrations/niko_home_control.markdown @VandeurenGlenn
 source/_integrations/nilu.markdown @hfurubotten
 source/_integrations/nina.markdown @DeerMaximum
 source/_integrations/nissan_leaf.markdown @filcole
-source/_integrations/nmbs.markdown @thibmaek
 source/_integrations/noaa_tides.markdown @jdelaney72
 source/_integrations/nobo_hub.markdown @echoromeo @oyvindwe
 source/_integrations/nordpool.markdown @gjohansson-ST
@@ -605,9 +611,10 @@ source/_integrations/ombi.markdown @larssont
 source/_integrations/onboarding.markdown @home-assistant/core
 source/_integrations/oncue.markdown @bdraco @peterager
 source/_integrations/ondilo_ico.markdown @JeromeHXP
+source/_integrations/onedrive.markdown @zweckj
 source/_integrations/onewire.markdown @garbled1 @epenet
 source/_integrations/onkyo.markdown @arturpragacz @eclair4151
-source/_integrations/onvif.markdown @hunterjm
+source/_integrations/onvif.markdown @hunterjm @jterrace
 source/_integrations/open_meteo.markdown @frenck
 source/_integrations/openai_conversation.markdown @balloob
 source/_integrations/openerz.markdown @misialq
@@ -626,7 +633,8 @@ source/_integrations/oru_opower.markdown @tronikos
 source/_integrations/osoenergy.markdown @osohotwateriot
 source/_integrations/otbr.markdown @home-assistant/core
 source/_integrations/ourgroceries.markdown @OnFreund
-source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/overkiz.markdown @imicknl
+source/_integrations/overseerr.markdown @joostlek
 source/_integrations/ovo_energy.markdown @timmo001
 source/_integrations/p1_monitor.markdown @klaasnicolaas
 source/_integrations/palazzetti.markdown @dotvav
@@ -648,7 +656,7 @@ source/_integrations/ping.markdown @jpbede
 source/_integrations/piper.markdown @balloob @synesthesiam
 source/_integrations/plaato.markdown @JohNan
 source/_integrations/plex.markdown @jjlawren
-source/_integrations/plugwise.markdown @CoMPaTech @bouwew @frenck
+source/_integrations/plugwise.markdown @CoMPaTech @bouwew
 source/_integrations/plum_lightpad.markdown @ColinHarrington @prystupa
 source/_integrations/point.markdown @fredrike
 source/_integrations/poolsense.markdown @haemishkyd
@@ -709,7 +717,7 @@ source/_integrations/reolink.markdown @starkillerOG
 source/_integrations/repairs.markdown @home-assistant/core
 source/_integrations/repetier.markdown @ShadowBr0ther
 source/_integrations/rest_command.markdown @jpbede
-source/_integrations/rexel.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/rexel.markdown @imicknl
 source/_integrations/rflink.markdown @javicalle
 source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
 source/_integrations/rhasspy.markdown @balloob @synesthesiam
@@ -718,7 +726,7 @@ source/_integrations/ring.markdown @sdb9696
 source/_integrations/risco.markdown @OnFreund
 source/_integrations/rituals_perfume_genie.markdown @milanmeu @frenck
 source/_integrations/rmvtransport.markdown @cgtobi
-source/_integrations/roborock.markdown @Lash-L
+source/_integrations/roborock.markdown @Lash-L @allenporter
 source/_integrations/roku.markdown @ctalkington
 source/_integrations/romy.markdown @xeniter
 source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn @Orhideous
@@ -727,6 +735,7 @@ source/_integrations/rpi_power.markdown @shenxn @swetoast
 source/_integrations/rss_feed_template.markdown @home-assistant/core
 source/_integrations/ruckus_unleashed.markdown @lanrat @ms264556 @gabe565
 source/_integrations/russound_rio.markdown @noahhusby
+source/_integrations/russound_rnet.markdown @noahhusby
 source/_integrations/ruuvi_gateway.markdown @akx
 source/_integrations/ruuvitag_ble.markdown @akx
 source/_integrations/rympro.markdown @OnFreund @elad-bar @maorcc
@@ -772,7 +781,7 @@ source/_integrations/simplefin.markdown @scottg489 @jeeftor
 source/_integrations/simplepush.markdown @engrbm87
 source/_integrations/simplisafe.markdown @bachya
 source/_integrations/simply_automated.markdown @gwww
-source/_integrations/simu.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/simu.markdown @imicknl
 source/_integrations/sinch.markdown @bendikrb
 source/_integrations/siren.markdown @home-assistant/core @raman325
 source/_integrations/sisyphus.markdown @jkeljo
@@ -784,7 +793,7 @@ source/_integrations/sleepiq.markdown @mfugate1 @kbickar
 source/_integrations/slide.markdown @ualex73
 source/_integrations/slide_local.markdown @dontinelli
 source/_integrations/slimproto.markdown @marcelveldt
-source/_integrations/sma.markdown @kellerza @rklomp
+source/_integrations/sma.markdown @kellerza @rklomp @erwindouna
 source/_integrations/smappee.markdown @bsmappee
 source/_integrations/smart_blinds.markdown @starkillerOG
 source/_integrations/smart_home.markdown @starkillerOG
@@ -802,9 +811,9 @@ source/_integrations/snooz.markdown @AustinBrunkhorst
 source/_integrations/solaredge.markdown @frenck @bdraco
 source/_integrations/solaredge_local.markdown @drobtravels @scheric
 source/_integrations/solarlog.markdown @Ernst79 @dontinelli
-source/_integrations/solax.markdown @squishykid
+source/_integrations/solax.markdown @squishykid @Darsstar
 source/_integrations/soma.markdown @ratsept @sebfortier2288
-source/_integrations/somfy.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/somfy.markdown @imicknl
 source/_integrations/sonarr.markdown @ctalkington
 source/_integrations/songpal.markdown @rytilahti @shenxn
 source/_integrations/sonos.markdown @jjlawren @peterager
@@ -849,7 +858,7 @@ source/_integrations/synology_dsm.markdown @hacf-fr @Quentame @mib1185
 source/_integrations/synology_srm.markdown @aerialls
 source/_integrations/system_bridge.markdown @timmo001
 source/_integrations/systemmonitor.markdown @gjohansson-ST
-source/_integrations/tado.markdown @chiefdragon @erwindouna
+source/_integrations/tado.markdown @erwindouna
 source/_integrations/tag.markdown @balloob @dmulcahey
 source/_integrations/tailscale.markdown @frenck
 source/_integrations/tailwind.markdown @frenck
@@ -899,11 +908,11 @@ source/_integrations/transmission.markdown @engrbm87 @JPHutchins
 source/_integrations/trend.markdown @jpbede
 source/_integrations/triggercmd.markdown @rvmey
 source/_integrations/tts.markdown @home-assistant/core
-source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck
+source/_integrations/tuya.markdown @Tuya @zlinoliver
 source/_integrations/twentemilieu.markdown @frenck
 source/_integrations/twinkly.markdown @dr1rrb @Robbie1221 @Olen
 source/_integrations/twitch.markdown @joostlek
-source/_integrations/ubiwizz.markdown @imicknl @vlebourl @tetienne @nyroDev @tronix117 @alexfp14
+source/_integrations/ubiwizz.markdown @imicknl
 source/_integrations/ukraine_alarm.markdown @PaulAnnekov
 source/_integrations/unifi.markdown @Kane610
 source/_integrations/unifi_direct.markdown @tofuSCHNITZEL
@@ -926,12 +935,12 @@ source/_integrations/vacuum.template.markdown @home-assistant/core
 source/_integrations/vallox.markdown @andre-richter @slovdahl @viiru- @yozik04
 source/_integrations/valve.markdown @home-assistant/core
 source/_integrations/velbus.markdown @Cereal2nd @brefra
-source/_integrations/velux.markdown @Julius2342 @DeerMaximum
+source/_integrations/velux.markdown @Julius2342 @DeerMaximum @pawlizio
 source/_integrations/venstar.markdown @garbled1 @jhollowe
 source/_integrations/vermont_castings.markdown @jeeftor
 source/_integrations/versasense.markdown @imstevenxyz
 source/_integrations/version.markdown @ludeeus
-source/_integrations/vesync.markdown @markperdue @webdjoe @thegardenmonkey @cdnninja
+source/_integrations/vesync.markdown @markperdue @webdjoe @thegardenmonkey @cdnninja @iprak
 source/_integrations/vicare.markdown @CFenner
 source/_integrations/vilfo.markdown @ManneW
 source/_integrations/vivotek.markdown @HarlemSquirrel

Gemfile

@@ -4,15 +4,15 @@ ruby '> 2.5.0'
 
 group :development do
   gem 'rake', '13.2.1'
-  gem 'jekyll', '4.4.0'
+  gem 'jekyll', '4.4.1'
   gem 'compass', '1.0.3'
   gem 'sass-globbing', '1.1.5'
   gem 'stringex', '2.8.6'
   # > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
   gem 'sassc', '2.1.0'
   gem 'sass-embedded', '1.83.4'
-  gem 'rubocop', '1.71.0'
-  gem 'ruby-lsp', '0.23.7'
+  gem 'rubocop', '1.71.2'
+  gem 'ruby-lsp', '0.23.8'
   gem 'rackup', '2.2.1'
 end
 

Gemfile.lock

@@ -39,7 +39,7 @@ GEM
     http_parser.rb (0.8.0)
     i18n (1.14.7)
       concurrent-ruby (~> 1.0)
-    jekyll (4.4.0)
+    jekyll (4.4.1)
       addressable (~> 2.4)
       base64 (~> 0.2)
       colorator (~> 1.0)
@@ -61,8 +61,8 @@ GEM
     jekyll-commonmark (1.4.0)
       commonmarker (~> 0.22)
     jekyll-paginate (1.1.0)
-    jekyll-sass-converter (3.0.0)
-      sass-embedded (~> 1.54)
+    jekyll-sass-converter (3.1.0)
+      sass-embedded (~> 1.75)
     jekyll-sitemap (1.4.0)
       jekyll (>= 3.7, < 5.0)
     jekyll-toc (0.19.0)
@@ -98,7 +98,7 @@ GEM
     prism (1.3.0)
     public_suffix (6.0.1)
     racc (1.8.1)
-    rack (3.1.8)
+    rack (3.1.9)
     rack-protection (4.1.1)
       base64 (>= 0.1.0)
       logger (>= 1.6.0)
@@ -118,19 +118,19 @@ GEM
     regexp_parser (2.10.0)
     rexml (3.4.0)
     rouge (4.5.1)
-    rubocop (1.71.0)
+    rubocop (1.71.2)
       json (~> 2.3)
       language_server-protocol (>= 3.17.0)
       parallel (~> 1.10)
       parser (>= 3.3.0.2)
       rainbow (>= 2.2.2, < 4.0)
       regexp_parser (>= 2.9.3, < 3.0)
-      rubocop-ast (>= 1.36.2, < 2.0)
+      rubocop-ast (>= 1.38.0, < 2.0)
       ruby-progressbar (~> 1.7)
       unicode-display_width (>= 2.4.0, < 4.0)
     rubocop-ast (1.38.0)
       parser (>= 3.3.1.0)
-    ruby-lsp (0.23.7)
+    ruby-lsp (0.23.8)
       language_server-protocol (~> 3.17.0)
       prism (>= 1.2, < 2.0)
       rbs (>= 3, < 4)
@@ -156,7 +156,7 @@ GEM
       rack-protection (= 4.1.1)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11787)
+    sorbet-runtime (0.5.11801)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
@@ -174,7 +174,7 @@ PLATFORMS
 
 DEPENDENCIES
   compass (= 1.0.3)
-  jekyll (= 4.4.0)
+  jekyll (= 4.4.1)
   jekyll-commonmark (= 1.4.0)
   jekyll-paginate (= 1.1.0)
   jekyll-sitemap (= 1.4.0)
@@ -182,8 +182,8 @@ DEPENDENCIES
   nokogiri (= 1.18.2)
   rackup (= 2.2.1)
   rake (= 13.2.1)
-  rubocop (= 1.71.0)
-  ruby-lsp (= 0.23.7)
+  rubocop (= 1.71.2)
+  ruby-lsp (= 0.23.8)
   sass-embedded (= 1.83.4)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)

_config.yml

@@ -107,9 +107,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2025
-current_minor_version: 1
-current_patch_version: 4
-date_released: 2025-01-24
+current_minor_version: 2
+current_patch_version: 0
+date_released: 2025-02-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.

sass/homeassistant/aside/_buy_dialog.scss

@@ -195,7 +195,6 @@
                     font-size: 10px;
                     height: 14px;
                     line-height: 1;
-                    overflow: hidden;
                     white-space: nowrap;
                 }
 
@@ -216,4 +215,4 @@
             }
         }
     }
-}
+}

source/_data/products.yml

@@ -1,5 +1,3 @@
-# Flags rendered via https://flagpedia.net/
-# ship_from accepts ISO 3166 country code
 green:
   name: "<strong>Home Assistant Green</strong>"
   distributors:
@@ -446,4 +444,9 @@ voice-pe:
       ship_from: UK
       ship_to: Europe
       url: https://shop.everythingsmart.io/products/home-assistant-voice-preview-edition
-      logo: /images/distributors/est.webp
+      logo: /images/distributors/est.webp
+    - name: Pimoroni
+      ship_from: UK
+      ship_to: Europe
+      url: https://shop.pimoroni.com/products/home-assistant-voice
+      logo: /images/distributors/pimoroni.webp

source/_docs/tools/hass.markdown

@@ -5,8 +5,9 @@ description: "Description of hass."
 
 The command-line part of Home Assistant is `hass`.
 
+This tool is only available to users of the Home Assistant Core installation method. It is started from the command line on the computer running Home Assistant Core (accessed perhaps via SSH).
 
-```bash
+```text
 $ hass -h
 usage: hass [-h] [--version] [-c path_to_config_dir] [--safe-mode]
             [--debug] [--open-ui] [--skip-pip] [-v] [--log-rotate-days LOG_ROTATE_DAYS] 

source/_integrations/airthings.markdown

@@ -30,7 +30,7 @@ Airthings API setup (needed to acquire the required ID and Secret for the Home A
 1. Login [here](https://dashboard.airthings.com/integrations/api-integration) to find your credentials.
 2. Select [Integrations](https://dashboard.airthings.com/integrations/api-integration) from the left side-bar.
 3. Click on "Request API Client" in order to set up an API connection.
-4. Name your API connection ie. "Home Assistant Integration".
+4. Name your API connection (e.g., "Home Assistant"). Note: The name field has a character limit and longer names will be truncated.
 5. Give the connection an accurate description.
 6. Select a Resource Scope.
 7. Select an access Type, i.e., Confidential.

source/_integrations/airthings_ble.markdown

@@ -40,6 +40,7 @@ This integration uses the last 6 digits of the serial number.
 - Wave Radon
 - Wave Mini
 - Wave Plus
+- Wave Enhance
 
 ## Sensors
 

source/_integrations/balboa.markdown

@@ -21,6 +21,7 @@ ha_codeowners:
   - '@natekspencer'
 ha_config_flow: true
 ha_integration_type: integration
+ha_dhcp: true
 ---
 
 The **Balboa Spa Client** {% term integration %} adds support for [Balboa](https://www.balboawatergroup.com/) Spa WiFi Modules to be used within Home Assistant.

source/_integrations/bang_olufsen.markdown

@@ -2,16 +2,16 @@
 title: Bang & Olufsen
 description: Instructions on how to integrate Bang & Olufsen devices into Home Assistant.
 ha_category:
+  - Event
   - Media Player
   - Multimedia
-  - Event
 ha_release: 2024.2
 ha_iot_class: Local Push
 ha_domain: bang_olufsen
 ha_platforms:
   - diagnostics
-  - media_player
   - event
+  - media_player
 ha_codeowners:
   - '@mj23000'
 ha_config_flow: true

source/_integrations/bluetooth.markdown

@@ -293,7 +293,13 @@ Bluetooth advertisement bundling reduces traffic between Home Assistant and the
 
 ### Improving connection times
 
-The connection time and performance vary greatly based on the Bluetooth adapter and interference. The below adapters are listed from best-performing to worst-performing:
+Connection time and performance vary greatly depending on the Bluetooth adapter and interference. 
+
+{% warning %}
+When switching to an adapter with better performance, disable the old, less performant adapters. The best signal and available connection slots are considered when making connections, and performance will be limited to the worst-performing adapter with the best signal to reach the remote device.
+{% endwarning %}
+
+The below adapters are listed from best-performing to worst-performing:
 
 - [Ethernet-connected Bluetooth proxies](#remote-adapters-bluetooth-proxies) running ESPHome 2023.6.0 or later with [passive scanning](https://esphome.io/components/esp32_ble_tracker.html#configuration-variables)
 - [USB High performance adapter](#known-working-high-performance-adapters) with [passive scanning](#passive-scanning)

source/_integrations/brandt.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/bticino.markdown

@@ -3,6 +3,7 @@ title: BTicino
 description: Connect and control your BTicino devices using the Netatmo integration
 ha_category:
   - Binary sensor
+  - Button
   - Camera
   - Climate
   - Cover
@@ -24,6 +25,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
   - camera
   - climate
   - cover

source/_integrations/bubendorff.markdown

@@ -3,6 +3,7 @@ title: Bubendorff
 description: Connect and control your Bubendorff devices using the Netatmo integration
 ha_category:
   - Binary sensor
+  - Button
   - Camera
   - Climate
   - Cover
@@ -24,6 +25,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
   - camera
   - climate
   - cover

source/_integrations/cloud.markdown

@@ -3,6 +3,8 @@ title: Home Assistant Cloud
 description: Enable the Home Assistant Cloud integration.
 ha_release: '0.60'
 ha_category:
+  - Backup
+  - Speech-to-text
   - Text-to-speech
   - Voice
 ha_iot_class: Cloud Push
@@ -16,7 +18,7 @@ ha_platforms:
 ha_integration_type: system
 ---
 
-The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. [Learn more.](/cloud)
+The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. It also enables a secure remote connection, speech-to-text, text-to-speech, an offsite backup location, Webhooks support, and better WebRTC. [Learn more.](/cloud)
 
 ## Configuration
 
@@ -29,7 +31,7 @@ cloud:
 
 Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/)
 
-Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your {% term "`configuration.yaml`" %} file.
+Once activated, go to the configuration panel in Home Assistant, create an account, and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your {% term "`configuration.yaml`" %} file.
 
 ```yaml
 config:

source/_integrations/command_line.markdown

@@ -22,6 +22,7 @@ ha_codeowners:
 related:
   - docs: /docs/configuration/
     title: Configuration file
+ha_quality_scale: legacy
 ---
 
 The **Command line** {% term integration %} offers functionality that issues specific commands to get data or to control a device.

source/_integrations/cookidoo.markdown

@@ -11,6 +11,9 @@ ha_codeowners:
 ha_domain: cookidoo
 ha_integration_type: service
 ha_platforms:
+  - button
+  - diagnostics
+  - sensor
   - todo
 related:
   - docs: /integrations/todo

source/_integrations/cozytouch.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/decorquip.markdown

@@ -7,7 +7,7 @@ ha_domain: decorquip
 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/discovergy.markdown

@@ -14,6 +14,7 @@ ha_platforms:
   - diagnostics
   - sensor
 ha_integration_type: service
+ha_quality_scale: silver
 ---
 
 The **inexogy** {% term integration %} allows users to integrate their [inexogy](https://inexogy.com/) smart meters into Home Assistant.

source/_integrations/esera_onewire.markdown

@@ -15,6 +15,7 @@ ha_config_flow: true
 ha_platforms:
   - binary_sensor
   - diagnostics
+  - select
   - sensor
   - switch
 ha_iot_class: Local Polling

source/_integrations/flexom.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/fujitsu_fglair.markdown

@@ -46,4 +46,3 @@ This integration supports the following functionalities (if the devices support
 ## Outside temperature
 
 On units that support it, this integration will expose a temperature sensor that reports the outside temperature that the unit is sensing.
-

source/_integrations/fyta.markdown

@@ -13,6 +13,7 @@ ha_domain: fyta
 ha_platforms:
   - binary_sensor
   - diagnostics
+  - image
   - sensor
 ha_integration_type: hub
 ha_quality_scale: platinum

source/_integrations/google_generative_ai_conversation.markdown

@@ -41,7 +41,7 @@ The Google Generative AI API key is used to authenticate requests to the Google
 - Visit the [API Keys page](https://aistudio.google.com/app/apikey) to retrieve the API key you'll use to configure the integration.
 
 On the same page, you can see your plan: *free of charge* if the associated Google Cloud project doesn't have billing, or *pay-as-you-go* if the associated Google Cloud project has billing enabled.
-Comparison of the plans is available [at this pricing page](https://ai.google.dev/pricing). The major differences include: the free of charge plan is rate limited, free prompts/responses are used for product improvement, and the free plan is not available in all [regions](https://ai.google.dev/gemini-api/docs/available-regions).
+Comparison of the plans is available [at this pricing page](https://ai.google.dev/pricing). The major differences include: the free of charge plan is rate limited, and free prompts/responses are used for product improvement.
 
 {% include integrations/option_flow.md %}
 
@@ -73,7 +73,7 @@ Safety settings:
 
 ## Talking to Super Mario
 
-You can use an OpenAI Conversation integration to [talk to Super Mario and, if you want, have him control devices in your home](/voice_control/assist_create_open_ai_personality/).
+You can use this integration to [talk to Super Mario and, if you want, have him control devices in your home](/voice_control/assist_create_open_ai_personality/).
 
 The tutorial is using OpenAI, but this could also be done with the Google Generative AI integration.
 

source/_integrations/habitica.markdown

@@ -3,9 +3,9 @@ title: Habitica
 description: Instructions on enabling Habitica support for your Home Assistant
 ha_category:
   - Calendar
+  - Image
   - Sensor
   - To-do list
-  - Image
 ha_release: 0.78
 ha_iot_class: Cloud Polling
 ha_domain: habitica
@@ -14,10 +14,10 @@ ha_platforms:
   - button
   - calendar
   - diagnostics
+  - image
   - sensor
   - switch
   - todo
-  - image
 ha_codeowners:
   - '@tr4nt0r'
 ha_config_flow: true

source/_integrations/harvey.markdown

@@ -4,7 +4,7 @@ description: Integrate Harvey water softeners with Home Assistant using the Aqua
 ha_category:
   - Sensor
 ha_domain: harvey
-ha_release: 2025.1
+ha_release: 2024.7
 ha_integration_type: virtual
 ha_supporting_domain: aquacell
 ha_supporting_integration: AquaCell

source/_integrations/heos.markdown

@@ -13,7 +13,7 @@ ha_ssdp: true
 ha_platforms:
   - diagnostics
   - media_player
-ha_integration_type: integration
+ha_integration_type: hub
 ha_quality_scale: silver
 ---
 

source/_integrations/hexaom.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/hi_kumo.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/home_plus_control.markdown

@@ -3,6 +3,7 @@ title: Legrand Home+ Control
 description: Connect and control your Legrand Home+ Control devices using the Netatmo integration
 ha_category:
   - Binary sensor
+  - Button
   - Camera
   - Climate
   - Cover
@@ -24,6 +25,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
   - camera
   - climate
   - cover

source/_integrations/homee.markdown

@@ -13,6 +13,7 @@ ha_platforms:
   - cover
   - sensor
 ha_integration_type: hub
+ha_quality_scale: bronze
 ---
 
 [Homee](https://hom.ee) is a smart home system, able to integrate various protocols such as Z-Wave, Zigbee, EnOcean, and more. The Homee {% term integration %} will let you use the {% term devices %} from your Homee in Home Assistant.

source/_integrations/homematicip_cloud.markdown

@@ -22,6 +22,7 @@ ha_platforms:
   - button
   - climate
   - cover
+  - event
   - light
   - lock
   - sensor

source/_integrations/ibeacon.markdown

@@ -14,8 +14,6 @@ ha_platforms:
 ha_bluetooth: true
 ha_config_flow: true
 ha_integration_type: integration
-ha_codeowners:
-  - '@bdraco'
 ---
 
 {% include integrations/config_flow.md %}

source/_integrations/idasen_desk.markdown

@@ -15,6 +15,7 @@ ha_platforms:
 ha_integration_type: device
 ha_codeowners:
   - '@abmantis'
+ha_quality_scale: bronze
 ---
 
 The IKEA IDÅSEN {% term integration %} allows you to connect your [IKEA Idåsen](https://www.ikea.com/us/en/cat/idasen-system-47424/) motorized desk to Home Assistant, making it possible to control the desk height and also monitor height changes from the physical controller.

source/_integrations/igloohome.markdown

@@ -11,7 +11,8 @@ ha_codeowners:
 ha_domain: igloohome
 ha_platforms:
   - sensor
-ha_integration_type: device
+ha_integration_type: integration
+ha_quality_scale: bronze
 ---
 
 The **igloohome** {% term integration %} grants Home Assistant access to paired [smart access device\(s\)](https://www.igloohome.co/#products). The features of this integration includes:
@@ -74,4 +75,4 @@ Some generic troubleshooting steps:
 ### Authentication problems
 
 - Verify that your [API credentials](https://access.igloocompany.co/api-access) are correctly filled in.
-- Ensure your API credentials have not expired or been revoked.
+- Ensure your API credentials have not expired or been revoked.

source/_integrations/incomfort.markdown

@@ -14,6 +14,7 @@ ha_domain: incomfort
 ha_platforms:
   - binary_sensor
   - climate
+  - diagnostics
   - sensor
   - water_heater
 ha_integration_type: integration

source/_integrations/iron_os.markdown

@@ -19,6 +19,7 @@ ha_integration_type: integration
 ha_platforms:
   - binary_sensor
   - button
+  - diagnostics
   - number
   - select
   - sensor

source/_integrations/ituran.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - device_tracker
   - sensor
 ha_integration_type: hub
+ha_quality_scale: silver
 ---
 
 The **Ituran** {% term integration %} allows you to retrieve information from your Ituran-equipped vehicle using the [Ituran APP service](https://www.ituran.co.il/ituranfront/comfort-services-2/ituran-app-comfort). It pulls information from the Ituran web service regarding the vehicle's location.

source/_integrations/juicenet.markdown

@@ -22,8 +22,13 @@ ha_integration_type: integration
 
 The `juicenet` platform pulls data from a [JuiceNet](https://evcharging.enelx.com/products/juicebox) charging station equipped with a Wi-Fi connection. It will access and make available all of the devices attached to your account. It also exposes a switch allowing you to charge your car now instead of waiting for the pre-set schedule.
 
+{% important %}
+This integration can no longer be set up as the required API token cannot be obtained. However, if you have it working, it may remain functional.
+{% endimportant %}
+
 {% include integrations/config_flow.md %}
 
+
 ## Sensor
 
 The `juicenet` sensor platform allows you to get data from your [JuiceNet](https://evcharging.enelx.com/products/juicebox) charger.

source/_integrations/lametric.markdown

@@ -278,4 +278,4 @@ Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://hom
 ### The brightness doesn't go to 100%
 
 When the LaMetric is powered by a USB port on a computer, the brightness is limited.
-To get the full brightness, use a proper USB charger.
+To get the full brightness, use a proper USB charger.

source/_integrations/legrand.markdown

@@ -3,6 +3,7 @@ title: Legrand
 description: Connect and control your Legrand devices using the Netatmo integration
 ha_category:
   - Binary sensor
+  - Button
   - Camera
   - Climate
   - Cover
@@ -24,6 +25,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
   - camera
   - climate
   - cover

source/_integrations/letpot.markdown

@@ -10,10 +10,11 @@ ha_config_flow: true
 ha_codeowners:
   - '@jpelgrom'
 ha_domain: letpot
-ha_integration_type: integration
+ha_integration_type: hub
 ha_platforms:
   - switch
   - time
+ha_quality_scale: bronze
 ---
 
 The **LetPot** {% term integration %} allows you to integrate your [LetPot](https://letpot.com/) hydroponic gardens/systems into Home Assistant.

source/_integrations/litterrobot.markdown

@@ -26,6 +26,7 @@ ha_platforms:
   - update
   - vacuum
 ha_integration_type: hub
+ha_quality_scale: bronze
 ---
 
 The Litter-Robot integration allows you to monitor and control your Wi-Fi-enabled, automatic, self-cleaning litter box and pet feeders. If you have pet profiles set up, you can also track your pet's weight.

source/_integrations/mcp.markdown

@@ -7,12 +7,13 @@ ha_release: 2025.2
 ha_iot_class: Local Polling
 ha_config_flow: true
 ha_codeowners:
-  - 'allenporter'
+  - '@allenporter'
 ha_domain: mcp
 ha_integration_type: integration
 related:
   - docs: /integrations/conversation/
     title: Conversation
+ha_quality_scale: silver
 ---
 
 The [Model Context Protocol](https://modelcontextprotocol.io) is an open protocol that

source/_integrations/mcp_server.markdown

@@ -7,12 +7,13 @@ ha_release: 2025.2
 ha_iot_class: Local Push
 ha_config_flow: true
 ha_codeowners:
-  - 'allenporter'
+  - '@allenporter'
 ha_domain: mcp_server
-ha_integration_type: integration
+ha_integration_type: service
 related:
   - docs: /integrations/conversation/
     title: Conversation
+ha_quality_scale: silver
 ---
 
 The [Model Context Protocol](https://modelcontextprotocol.io) is an open protocol that standardizes how applications provide context to <abbr title="Large Language Models">LLMs</abbr>. The **Model Context Protocol Server** (MCP) integration enables using Home Assistant to provide context for <abbr title="Model Context Protocol">MCP</abbr> LLM Client Applications. For example, you can expose your Google Tasks To-do list as a tool for Claude Desktop.

source/_integrations/mill.markdown

@@ -11,8 +11,8 @@ ha_domain: mill
 ha_config_flow: true
 ha_platforms:
   - climate
-  - sensor
   - number
+  - sensor
 ha_integration_type: integration
 ---
 

source/_integrations/minecraft_server.markdown

@@ -19,9 +19,10 @@ ha_integration_type: integration
 
 [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.
 
-{% important %}
-Minecraft Java Edition servers must be version 1.7 or newer, since older versions don't expose any information.
-{% endimportant %}
+## Prerequisites
+
+- Minecraft Java Edition servers must be version 1.7 or newer, since older versions don't expose any information.
+- The `enable-status` and `enable-query` must be set to `true` in the Minecraft `server.properties`.
 
 {% include integrations/config_flow.md %}
 

source/_integrations/monzo.markdown

@@ -2,8 +2,8 @@
 title: Monzo
 description: Instructions on how to integrate Monzo integration into Home Assistant.
 ha_category:
-  - Sensor
   - Finance
+  - Sensor
 ha_release: 2024.6
 ha_iot_class: Cloud Polling
 ha_codeowners:

source/_integrations/motionmount.md

@@ -17,12 +17,96 @@ ha_platforms:
 ha_codeowners:
   - '@RJPoelstra'
 ha_domain: motionmount
+ha_zeroconf: true
 ---
 
-The Vogel's MotionMount integration allows you to control the position of your [TVM 7675 Pro](https://www.vogels.com/p/tvm-7675-pro-motorized-tv-wall-mount-black) Signature MotionMount.
+The `motionmount` {% term integration %} allows you to control the position of your [TVM 7675 Pro](https://www.vogels.com/p/tvm-7675-pro-motorized-tv-wall-mount-black) SIGNATURE MotionMount from Vogel's.
 
 This integration uses the Ethernet (IP) connection of your MotionMount. It's not possible to connect using the RS-232 connection.
 
 It provides information about the current position of the mount and allows setting a new position.
 
+A use case would be to position the TV based on whether anyone is actively watching. The MotionMount provides an HDMI connection to monitor whether the TV is turned on and in response move it to a preset position or the last known position. However, if you also use the TV for background music, you probably don't want the MotionMount to extend. By using a presence sensor to check whether anyone is actually in front of the TV, you can ensure the MotionMount only extends when the TV is actively being watched.
+
 {% include integrations/config_flow.md %}
+
+{% configuration_basic %}
+Host:
+  description: Hostname or IP address of the device, for example:`192.168.1.2`.
+Port:
+  description: The TCP port of the device. Defaults to 23. Only change this when you're absolutely certain that it shouldn't be 23.
+PIN:
+  description: The user level pincode, if configured on the device.
+{% endconfiguration_basic %}
+
+## Removing the integration
+
+This integration follows standard integration removal. No extra steps are required.
+
+{% include integrations/remove_device_service.md %}
+
+## Data updates
+
+The MotionMount pushes new data to the integration.
+The only exception is the presets. Changes to the presets are {% term polling polled %}, by default every 60 seconds.
+
+## Known limitations
+
+The integration does not provide the ability to configure the MotionMount.
+All settings, including configuring presets, should be done via the MotionMount app.
+
+Only IP connections are supported. Connection via RS-232 or Bluetooth Low Energy is not supported.
+
+## Supported devices
+
+The following devices are supported:
+
+- TVM 7675 Pro (SIGNATURE MotionMount with Pro extension)
+
+## Unsupported devices
+
+The following devices are *not* supported:
+
+- TVM 7675 (SIGNATURE MotionMount without Pro extension)
+- TVM 7355 (NEXT MotionMount)
+
+## Supported functionality
+
+### Entities
+
+#### Sensors
+
+- **Moving**
+  - **Description**: Indicates whether the MotionMount is moving.
+
+- **Error Status**
+  - **Description**: The error status of the MotionMount.
+    - None: There is no error.
+    - Motor: There is a problem communicating with the motor.
+    - Internal: There is an internal error. Refer to the MotionMount app for support.
+
+#### Numbers
+
+- **Extension**
+  - **Description**: The current extension of the MotionMount from the wall.
+
+- **Turn**
+  - **Description**: The current rotation of the MotionMount.
+
+#### Selects
+
+- **Presets**
+  - **Description**: If the MotionMount is at a preset location, this shows the corresponding preset.
+        Any preset can be selected to move the MotionMount to this preset position.
+
+## Troubleshooting
+
+### Can't connect to device
+
+1. Make sure the device is powered on.
+2. Make sure the device is connected to the same network as Home Assistant.
+3. Make sure the IP address of the MotionMount is configured correctly.
+    - In case of doubt, perform a network reset by holding the reset button for approx. 5 seconds.
+      - **Result**: The LED will start to blink slowly. This indicates that the network configuration is being reset to use DHCP.
+      - **Important**: Don't hold the reset button for too long (approx. 10 s). Holding the button for 10 s or longer starts a factory reset. A factory reset is indicated by the LED blinking fast.
+

source/_integrations/mqtt.markdown

@@ -44,6 +44,7 @@ ha_platforms:
   - valve
   - water_heater
 ha_integration_type: integration
+ha_quality_scale: platinum
 ---
 
 MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.
@@ -793,7 +794,7 @@ support_url:
     'osc_cmd_tpl':         'oscillation_command_template',
     'osc_stat_t':          'oscillation_state_topic',
     'osc_val_tpl':         'oscillation_value_template',
-    'platform':            'p',
+    'p':                   'platform',
     'pct_cmd_t':           'percentage_command_topic',
     'pct_cmd_tpl':         'percentage_command_template',
     'pct_stat_t':          'percentage_state_topic',

source/_integrations/nexity.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/nmbs.markdown

@@ -6,8 +6,6 @@ ha_category:
 ha_config_flow: true
 ha_iot_class: Cloud Polling
 ha_release: 0.85
-ha_codeowners:
-  - '@thibmaek'
 ha_domain: nmbs
 ha_platforms:
   - sensor

source/_integrations/onedrive.markdown

@@ -13,6 +13,7 @@ ha_integration_type: service
 related:
   - docs: /common-tasks/general/#backups
     title: Backups
+ha_quality_scale: bronze
 ---
 
 This integration allows you to use [OneDrive](https://www.microsoft.com/en-us/microsoft-365/onedrive/online-cloud-storage) for [Home Assistant Backups](/common-tasks/general/#backups).

source/_integrations/onewire.markdown

@@ -17,6 +17,7 @@ ha_platforms:
   - sensor
   - switch
 ha_integration_type: hub
+ha_zeroconf: true
 ---
 
 The Onewire integration supports sensors that use the 1-wire bus for communication.

source/_integrations/onvif.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Local Push
 ha_domain: onvif
 ha_codeowners:
   - '@hunterjm'
+  - '@jterrace'
 ha_config_flow: true
 ha_platforms:
   - binary_sensor

source/_integrations/overkiz.markdown

@@ -22,11 +22,6 @@ ha_config_flow: true
 ha_iot_class: Local Polling
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_domain: overkiz
 ha_dhcp: true
 ha_zeroconf: true
@@ -169,4 +164,4 @@ Please note that only a [limited set of devices is supported via HomeKit](https:
 
 This integration follows standard integration removal. No extra steps are required.
 
-{% include integrations/remove_device_service.md %}
+{% include integrations/remove_device_service.md %}

source/_integrations/overseerr.markdown

@@ -13,8 +13,10 @@ ha_codeowners:
 ha_domain: overseerr
 ha_integration_type: service
 ha_platforms:
+  - diagnostics
   - event
   - sensor
+ha_quality_scale: platinum
 ---
 
 Overseerr is a service that allows you to manage media requests and to integrate these media requests with Plex, Radarr, and Sonarr. The **Overseerr** {% term integration %} allows you to integrate your [Overseerr](https://overseerr.dev/) instance.

source/_integrations/palazzetti.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@dotvav'
 ha_domain: palazzetti
 ha_platforms:
+  - button
   - climate
   - diagnostics
   - number

source/_integrations/pinecil.markdown

@@ -3,9 +3,11 @@ title: Pinecil
 description: Connect and control your Pinecil devices using the IronOS integration
 ha_category:
   - Binary sensor
+  - Button
   - Number
   - Select
   - Sensor
+  - Switch
   - Update
 ha_release: 2024.8
 ha_domain: pinecil
@@ -17,9 +19,12 @@ ha_codeowners:
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
+  - diagnostics
   - number
   - select
   - sensor
+  - switch
   - update
 ha_iot_class: Local Polling
 ---

source/_integrations/piper.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
   - '@synesthesiam'
 ha_config_flow: true
 ha_platforms:
+  - assist_satellite
   - binary_sensor
   - conversation
   - number

source/_integrations/qbus.markdown

@@ -11,8 +11,9 @@ ha_codeowners:
   - '@thomasddn'
 ha_release: 2025.2
 ha_domain: qbus
-ha_integration_type: device
+ha_integration_type: hub
 ha_config_flow: true
+ha_quality_scale: bronze
 ---
 
 The **Qbus** {% term integration %} allows you to integrate your [Qbus Control](https://www.qbus.be) into Home Assistant. **Qbus** is a Belgian manufacturer of Home Automation systems.

source/_integrations/refoss.markdown

@@ -81,4 +81,4 @@ If the Refoss device isn't discovered by Home Assistant automatically, follow th
 4. Check the logs for messages containing "Discovered devices"
 5. If no devices are found, verify:
    - Network connectivity
-   - Device firmware version matches the supported versions listed above
+   - Device firmware version matches the supported versions listed above

source/_integrations/reolink.markdown

@@ -591,7 +591,7 @@ Prerequisites:
 ![Choose entity button](/images/integrations/reolink/rich_notification__chose_entity.png)
 ![Select Fluent camera](/images/integrations/reolink/rich_notification__select_fluent_camera.png)
 
-  Under **Filename**, fill in `/config/www/reolink_snapshot/last_snapshot_doorbell.jpg`. The first part `/config/www/` is absolutely necessary to allow your phone to access the saved image when it receives the notification. The reset of the folder and filename can be changed at will as long as you fill in the same filename under step 6.
+  Under **Filename**, fill in `/media/reolink_snapshot/last_snapshot_doorbell.jpg`. The first part `/media/` is absolutely necessary to allow your phone to access the saved image when it receives the notification. The reset of the folder and filename can be changed at will as long as you fill in the same filename under step 6.
 
 <p class='img'>
   <img src='/images/integrations/reolink/rich_notification__screenshot_take_snapshot.png' alt='Screenshot: take snapshot'>
@@ -605,7 +605,7 @@ Prerequisites:
 
   Under **message**, type the text you want to receive in the notification. For instance, “Someone rang the doorbell”.
   If you want to give the notification a title, select the **title** option. For instance, if you have multiple cameras that send you notifications, select the camera name: `Doorbell`.
-  Select the **data** option and fill in `image: /local/reolink_snapshot/last_snapshot_doorbell.jpg`. Note that `/config/www/` of the filename of step 5 now needs to be changed to `/local/`. The rest of the filename needs to be the same as in step 5.
+  Select the **data** option and fill in `image: /media/local/reolink_snapshot/last_snapshot_doorbell.jpg`. Note that `/media/` of the filename of step 5 now needs to be changed to `/media/local/`. The rest of the filename needs to be the same as in step 5.
 
 <p class='img'>
   <img src='/images/integrations/reolink/rich_notification__send_to_mobile.png' alt='Screenshot: send notification'>
@@ -625,6 +625,81 @@ Prerequisites:
 
 - Turn on (outdoor) lights near the camera to improve image clarity at night once the camera detects a person, vehicle, or animal.
 - Turn off notifications and recording when you get home (based on, e.g., geofencing) and turn it back on when you leave home.
+- Auto-pause rich notifications for x time
+
+{% details "Auto-pause rich notifications tutorial" icon="mdi:cursor-hand" %}
+
+**Goal**: At the end of this tutorial, you will have a drop-down on your dashboard with different time choices to pause your notifications. When the time is up, the notifications will become active again. It will look like this:
+
+![Overview of end result](/images/integrations/reolink/auto_pause__overview.png)
+
+1. First, create the dropdown from **Settings** > **Devices & services** > **Helpers** > **+ Create Helper** > **Dropdown**. 
+   - Decide how many time delay choices you want. 
+   - Add them all to the dropdown like below. 
+   - Your first entry needs to be "Notifications active" (or simular phrasing) for when the notifications are turned on. 
+   - You can define as many time options as you want. And you can define any time interval you like, for example, 22 minutes, 2 hours.
+
+    ![Dropdown](/images/integrations/reolink/auto_pause__dropdown.png)
+
+2. Next, also from the **Helpers** menu create a **Timer**. 
+   - Leave the time duration all zeros. Select the **Restore state and time** box.
+
+     ![Timer](/images/integrations/reolink/auto_pause__timer.png)
+
+3. Now you will create a new automation script. 
+   - For the **When** select **+ Add Trigger** > **Entity** > **State** and choose your dropdown box for the entity and in the **From** choose your "Notifications active" or whatever you chose for the top item.
+
+   ![Automation When dropdown](/images/integrations/reolink/auto_pause__automation_when.png)
+
+4. Add another trigger using **+ Add Trigger** > **Entity** > **State** and choose your timer for the entity and in the **To** choose "Idle". 
+   - Now select the three dots {% icon "mdi:dots-vertical" %} menu of this trigger and press **Edit ID**. In the **Trigger ID** type "TIMER DONE".
+
+    ![Automation When timer](/images/integrations/reolink/auto_pause__automation_when_timer.png)
+
+5. There is nothing in the **And if** section. For the **Then do** section choose **add building block** and use **Choose**. 
+   - You will have as many options as you have times in your dropdown box plus one to reset the dropdown box. 
+   - First, we make the option to reset the dropdown box. This needs to be the first option. 
+   - Under **Option 1**, select **+ Add Condition** > **Other conditions** > **Triggered by**. 
+   - Now check the box in front of "TIMER DONE".
+
+    ![Automation Triggered by](/images/integrations/reolink/auto_pause__automation_triggered_by.png)
+
+6. Add an action under this **Option 1**, choose **Select** as your action and then choose **First**. 
+   - Then enter your dropdown box as the entity. 
+   - This will change your dropdown box back to the first item when the timer is done. 
+   - This will allow your notification automation to run again.
+
+    ![Automation Select first](/images/integrations/reolink/auto_pause__automation_select_first.png)
+
+7. Let’s code the first option to pause the notifications now. 
+   - Under **Option 2**, select **+ Add Condition** > **Entity** > **State**. 
+   - Your dropdown box goes in the **Entity** and for **State** choose your first time delay.
+
+   ![Automation Choose](/images/integrations/reolink/auto_pause__automation_choose.png)
+
+8. For **+ Add Action**, choose **Helpers** > **Timer** > **Start** and enter your timer entity. 
+   - Check the duration box and enter the time delay you used for your first time delay. Format is HH:MM:SS
+
+    ![Automation Start timer](/images/integrations/reolink/auto_pause__automation_start_timer.png)
+
+9. The only thing left here is to duplicate Option 2 as many items as you have in your dropdown box. 
+   - The only changes you will need to make for each new option is to choose the correct state (time amount) for the dropdown box and then change the amount of time in the timer. 
+   - You can easliy duplicate by clicking the three dots {% icon "mdi:dots-vertical" %} menu at the far right of the option.
+
+10. Lastly, you need to apply this new feature. 
+    - Go into your rich notifications automation, or for that matter any automation that you would like to have pause control over, and add a condition. 
+    - Below is an example. In the **And if** press **+ Add condition** > **Entity** > **State** add select the dropdown box as the entity and "Notifications Active", the first item, as the state.
+
+    ![Condition](/images/integrations/reolink/auto_pause__condition.png)
+
+11. Add the dropdown box and the timer onto your dashboard and you are all set. 
+    - Here is what it looks like when it is running (holding notifications). 
+    - You can end it early by just selecting the timer, then selecting finish. That ends the timer, it goes to idle, and the automation resets the dropdown box to active.
+
+    ![Result when running](/images/integrations/reolink/auto_pause__result_when_running.png)
+
+{% enddetails %}
+
 - When someone presses the doorbell, play ringtones on speakers (Echo Dot/Google Home/smart hubs) throughout the house.
 - Pause a TV and show a notification badge on the TV when the doorbell is pressed (only when the TV is already on).
 - Play the quick replay messages of a Reolink doorbell only when not home (geofencing)

source/_integrations/rexel.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/roborock.markdown

@@ -16,6 +16,7 @@ ha_release: 2023.5
 ha_config_flow: true
 ha_codeowners:
   - '@Lash-L'
+  - '@allenporter'
 ha_domain: roborock
 ha_platforms:
   - binary_sensor

source/_integrations/russound_rio.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_integration_type: integration
 ha_quality_scale: silver
+ha_zeroconf: true
 ---
 
 The Russound RIO {% term integration %} allows you to control Russound devices that make use of the RIO protocol.

source/_integrations/russound_rnet.markdown

@@ -13,6 +13,8 @@ related:
   - docs: /docs/configuration/
     title: Configuration file
 ha_quality_scale: legacy
+ha_codeowners:
+  - '@noahhusby'
 ---
 
 The `russound_rnet` {% term integration %} allows you to control Russound devices that make use of the RNET protocol.

source/_integrations/simu.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/sma.markdown

@@ -9,8 +9,10 @@ ha_release: 0.36
 ha_codeowners:
   - '@kellerza'
   - '@rklomp'
+  - '@erwindouna'
 ha_domain: sma
 ha_platforms:
+  - diagnostics
   - sensor
 ha_integration_type: integration
 ---

source/_integrations/smarther.markdown

@@ -3,6 +3,7 @@ title: Smarther
 description: Connect and control your Smarther devices using the Netatmo integration
 ha_category:
   - Binary sensor
+  - Button
   - Camera
   - Climate
   - Cover
@@ -24,6 +25,7 @@ ha_codeowners:
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
   - camera
   - climate
   - cover

source/_integrations/smlight.markdown

@@ -22,6 +22,7 @@ ha_platforms:
 ha_codeowners:
   - '@tl-sl'
 ha_integration_type: device
+ha_dhcp: true
 ---
 
 The [SMLIGHT](https://smlight.tech) SLZB-06x Ethernet Zigbee coordinators

source/_integrations/solax.markdown

@@ -8,6 +8,7 @@ ha_release: 0.94
 ha_iot_class: Local Polling
 ha_codeowners:
   - '@squishykid'
+  - '@Darsstar'
 ha_domain: solax
 ha_platforms:
   - sensor

source/_integrations/somfy.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/template.markdown

@@ -156,7 +156,7 @@ variables:
 sensor:
   description: List of sensors
   required: true
-  type: map
+  type: list
   keys:
     state:
       description: "Defines a template to get the state of the sensor. If the sensor is numeric, i.e. it has a `state_class` or a `unit_of_measurement`, the state template must render to a number or to `none`. The state template must not render to a string, including `unknown` or `unavailable`. An `availability` template may be defined to suppress rendering of the state template."
@@ -180,7 +180,7 @@ sensor:
 binary_sensor:
   description: List of binary sensors
   required: true
-  type: map
+  type: list
   keys:
     state:
       description: The sensor is `on` if the template evaluates as `True`, `yes`, `on`, `enable` or a positive number. Any other value will render it as `off`. The actual appearance in the frontend (`Open`/`Closed`, `Detected`/`Clear` etc) depends on the sensor’s device_class value

source/_integrations/tesla_fleet.markdown

@@ -361,4 +361,3 @@ which then can be used within the energy dashboard.
 
 - **Integration shows `a condition has not been met to process the request`**
   1. Confirm that you've run all the steps from both the **Hosting a Public/Private Key Pair** and **Register your application as a Fleet API partner** sections above.
-  

source/_integrations/teslemetry.markdown

@@ -238,10 +238,6 @@ These are the entities available in the Teslemetry integration. Not all entities
 |Sensor|State|Yes|
 |Sensor|Vehicle|Yes|
 
-## Vehicle sleep
-
-Constant API polling will prevent most Model S and Model X vehicles manufactured before 2021 from sleeping, so the Teslemetry integration will stop polling these vehicles for 15 minutes, after 15 minutes of inactivity. You can call the `homeassistant.update_entity` action to force polling the API, which will reset the timer.
-
 ## Actions
 
 Teslemetry provides various custom actions to interact with the Tesla Fleet API directly.

source/_integrations/tplink_tapo.markdown

@@ -14,6 +14,7 @@ ha_category:
   - Sensor
   - Siren
   - Switch
+  - Vacuum
 ha_domain: tplink_tapo
 ha_release: 0.89
 ha_integration_type: virtual
@@ -37,6 +38,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - vacuum
 ha_iot_class: Local Polling
 ha_dhcp: true
 ---

source/_integrations/tradfri.markdown

@@ -36,7 +36,7 @@ If you see an "Unable to connect" message, restart the gateway and try again. Do
 {% note %}
 There is currently no dedicated core integration for the Dirigera hub released in October 2022.
 
-The Dirigera hub can, however, be integrated directly via the [HomeKit device](/integrations/homekit_controller/) integration. This configuration even provides events for motion sensors and buttons, which the original integration lacks.
+The Dirigera hub can, however, be integrated directly via the [HomeKit device](/integrations/homekit_controller/) integration or the [Matter](/integrations/matter/#using-a-matter-bridge) integration. As of Hub version 2.615.8 (September 2024), there is support for the following device types via Matter Bridge: lights (including drivers), smart plugs/outlets, connected blinds, remotes, motion sensors, open/close sensors, air purifiers, and air quality sensors.
 {% endnote %}
 
 

source/_integrations/trafikverket_weatherstation.markdown

@@ -10,6 +10,7 @@ ha_domain: trafikverket_weatherstation
 ha_codeowners:
   - '@gjohansson-ST'
 ha_platforms:
+  - diagnostics
   - sensor
 ha_integration_type: integration
 ---

source/_integrations/tuya.markdown

@@ -23,7 +23,6 @@ ha_domain: tuya
 ha_codeowners:
   - '@Tuya'
   - '@zlinoliver'
-  - '@frenck'
 ha_platforms:
   - alarm_control_panel
   - binary_sensor

source/_integrations/twinkly.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
 ha_platforms:
   - diagnostics
   - light
+  - select
 ha_dhcp: true
 ha_integration_type: integration
 ---

source/_integrations/ubiwizz.markdown

@@ -24,11 +24,6 @@ ha_supporting_integration: Overkiz
 ha_release: 2022.2
 ha_codeowners:
   - '@imicknl'
-  - '@vlebourl'
-  - '@tetienne'
-  - '@nyroDev'
-  - '@tronix117'
-  - '@alexfp14'
 ha_config_flow: true
 ha_platforms:
   - alarm_control_panel

source/_integrations/ubus.markdown

@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-This is a presence detection scanner for [OpenWrt](https://openwrt.org/) using [ubus](https://wiki.openwrt.org/doc/techref/ubus). It scans for changes in `hostapd.*`, which will detect and report changes in devices connected to the access point on the router.
+This is a presence detection scanner for [OpenWrt](https://openwrt.org/) using [ubus](https://openwrt.org/docs/techref/ubus). It scans for changes in `hostapd.*`, which will detect and report changes in devices connected to the access point on the router.
 
 Before this scanner can be used, you have to install the ubus RPC packages on OpenWrt (versions older than 18.06.x do not require the `uhttpd-mod-ubus` package):
 

source/_integrations/velbus.markdown

@@ -187,4 +187,3 @@ The Velbus integration and its entities can be removed by following these steps:
 {% include integrations/remove_device_service.md %}
 
 Note: Removing the integration will delete all Velbus devices and their history from Home Assistant.
-

source/_integrations/velux.markdown

@@ -10,12 +10,14 @@ ha_iot_class: Local Polling
 ha_codeowners:
   - '@Julius2342'
   - '@DeerMaximum'
+  - '@pawlizio'
 ha_domain: velux
 ha_platforms:
   - cover
   - light
   - scene
 ha_integration_type: integration
+ha_dhcp: true
 ---
 
 [Velux](https://www.velux.com/) {% term integration %} for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200.

source/_integrations/vesync.markdown

@@ -14,8 +14,10 @@ ha_codeowners:
   - '@webdjoe'
   - '@thegardenmonkey'
   - '@cdnninja'
+  - '@iprak'
 ha_domain: vesync
 ha_platforms:
+  - binary_sensor
   - diagnostics
   - fan
   - humidifier

source/_integrations/whisper.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
   - '@synesthesiam'
 ha_config_flow: true
 ha_platforms:
+  - assist_satellite
   - binary_sensor
   - conversation
   - number

source/_posts/2025-02-05-release-20252.markdown

@@ -0,0 +1,631 @@
+---
+layout: post
+title: "2025.2: Iterating on backups"
+description: "Lot of backup features including using Google Drive and Microsoft OneDrive as backup locations! Voice can now broadcast messages and control your thermostat. And much more!"
+date: 2025-02-05 00:00:00
+date_formatted: "February 5, 2025"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2025-02/social.jpg
+---
+
+<lite-youtube videoid="rflpsHsEE5s" videotitle="Home Assistant 2025.2 Release Party"></lite-youtube>
+
+Home Assistant 2025.2! ❤️
+
+In the previous release, we [overhauled our backup system](/blog/2025/01/03/release-20251/#overhaul-of-the-backup-system),
+and the response was overwhelming! Tons of suggestions and feature requests
+came in, so this release is—once again—focused on backups. Based on this
+community feedback, we’ve added loads of improvements, including the first
+integrations to store your backups in **Google Drive**
+and **Microsoft OneDrive**!
+
+This release also brings exciting new features to **Voice**! Home Assistant can
+now call your **analog phone**, and when dinner is ready, you can **broadcast**
+that message to all voice assistants in your home! But wait… there’s more!
+
+On **February 12, 2025**, we’re streaming live on YouTube all about Voice:
+[**Voice - Chapter 9**](https://www.youtube.com/live/k6VvzDSI8RU)! 🎙
+Be sure to subscribe and hit the bell so you don’t miss it. 🛎
+
+Before diving into the release notes, I also want to give a shoutout to our
+friends at [**ESPHome**](https://esphome.io/) powering so much of the Home
+Assistant ecosystem, including Home Assistant Voice PE! And
+on **February 19th**, they’ll be hosting a
+[**live release party for ESPHome 2025.2**](https://www.youtube.com/live/HtG3fjAO96c)! 🎉
+
+Enjoy the release!
+
+../Frenck
+
+_PS: It is almost Valentine's day, did you set up some romantic scenes yet? 🌹_
+
+<!--more-->
+
+- [Iterating on backups](#iterating-on-backups)
+  - [Unencrypted backups](#unencrypted-backups)
+    - [Ability to turn off encryption for specific locations](#ability-to-turn-off-encryption-for-specific-locations)
+    - [Downloading backups unencrypted](#downloading-backups-unencrypted)
+  - [Customize the time of your backups](#customize-the-time-of-your-backups)
+  - [Taking backups on an advanced schedule](#taking-backups-on-an-advanced-schedule)
+  - [Re-introduction of the backup toggle on update](#re-introduction-of-the-backup-toggle-on-update)
+    - [Backup on updating Home Assistant](#backup-on-updating-home-assistant)
+    - [Backup on updating add-ons](#backup-on-updating-add-ons)
+  - [Improved filenames for backups](#improved-filenames-for-backups)
+  - [New locations](#new-locations)
+- [Voice](#voice)
+  - [Home Assistant will be able to call your analog phone to tell you a message](#home-assistant-will-be-able-to-call-your-analog-phone-to-tell-you-a-message)
+  - [New Broadcast intent](#new-broadcast-intent)
+  - [Setting Temperature on Thermostat](#setting-temperature-on-thermostat)
+  - [LLMs meet calendars](#llms-meet-calendars)
+  - [Shared history between the default conversation agent and its LLM-based fallback](#shared-history-between-the-default-conversation-agent-and-its-llm-based-fallback)
+  - [Model Context Protocol](#model-context-protocol)
+- [Integrations](#integrations)
+  - [New integrations](#new-integrations)
+  - [Noteworthy improvements to existing integrations](#noteworthy-improvements-to-existing-integrations)
+  - [Now available to set up from the UI](#now-available-to-set-up-from-the-ui)
+- [Other noteworthy changes](#other-noteworthy-changes)
+- [Bluetooth config panel](#bluetooth-config-panel)
+- [Preparing our graphs for the future](#preparing-our-graphs-for-the-future)
+- [Need help? Join the community!](#need-help-join-the-community)
+- [Backward-incompatible changes](#backward-incompatible-changes)
+- [All changes](#all-changes)
+
+## Iterating on backups
+
+In the previous release, we [fully revamped the entire backup experience](/blog/2025/01/03/release-20251/#overhaul-of-the-backup-system)
+and added many new features to make it easier to use. That release set the
+stage for the next iterations and opened up the ability for integrations to
+provide locations to store backups.
+
+We've received **a lot** of feedback on the new backup system, which is awesome! ❤️
+All the feedback helped us prioritize the most requested features, and other
+improvements to the backup system.
+
+This release includes a lot of the most requested improvements and abilities.
+
+### Unencrypted backups
+
+The new backup system came with a lot of security improvements, including
+encryption of backups. However, as it turns out, many users use these backups
+to extract and restore single files or configurations, a use case in which
+encryption made things more difficult. In this release we made two changes
+to the backup system to address this.
+
+#### Ability to turn off encryption for specific locations
+
+While our default recommendation remains to encrypt backups, as of this
+release, you can turn off encryption on a per location basis. This allows you
+to store backups on you local NAS, for example, in an unencrypted format.
+
+<img class="no-shadow" alt="Screenshot showing the option to turn off encryption for a specific backup location." src="/images/blog/2025-02/backups-turn-off-encryption.png" />
+
+<img class="no-shadow" alt="Screenshot showing the backup locations, one location indicates that encryption has been turned off." src="/images/blog/2025-02/backups-encryption-turned-off.png" />
+
+There is one exception to this, which is [Home Assistant Cloud](/cloud). Backups
+stored in Home Assistant Cloud will always be encrypted, and encryption cannot
+be turned off. At Nabu Casa, we take your privacy and security very seriously,
+and we never ever want to be able to access your data.
+
+#### Downloading backups unencrypted
+
+When downloading backups from the Home Assistant interface, you will now always
+download the backup in an unencrypted format that can be extracted using your
+favorite archive tool.
+
+This works for all backups, regardless of the encryption settings of the
+location in which they are stored. For instance, if you download an encrypted
+backup from Home Assistant Cloud through the Home Assistant interface,
+it will decrypt the backup on the fly while you download it.
+
+### Customize the time of your backups
+
+The initial iteration of the backup system scheduled backups to run at 4:45 AM,
+but this time wasn't ideal for everyone. Some, for example, turned off their
+network storage during the night, meaning the backup would fail.
+
+This release, we added the ability to customize the time of your backups to your
+liking. Additionally, if you choose to make weekly backups, you can now select
+the days of the week you want the backup to run.
+
+<img class="no-shadow" alt="Screenshot showing the backup configuration options, you can now set your own time and select which days to backup." src="/images/blog/2025-02/backups-customize-backups-change.png" />
+
+### Taking backups on an advanced schedule
+
+The above backup time changes not flexible enough for you? Well, you are in luck! In this
+release, we added an action (`backup.create_automatic`) that you can use
+to trigger a backup, with your preferred settings, in an automation.
+
+<img class="no-shadow" alt="Screenshot showing an automation in the automation editor that is using the new action to create an automated backup." src="/images/blog/2025-02/backups-action.png" />
+
+This allows you to create automated backups on any schedule you like, or even
+add conditions and actions around it. For example, you could make an automation
+that triggers on a calendar, wakes up your network storage, waits till it is
+online, and then starts a backup.
+
+### Re-introduction of the backup toggle on update
+
+If you run Home Assistant OS, you get updates for Home Assistant along with
+all your add-ons. The update dialog used to have a toggle to create a backup
+before updating, which was removed in the previous release.
+
+This change was made because this feature was considered redundant when running
+regular automated backups. However, we’ve received a lot of feedback that many
+people relied on these backups to ensure they had the latest data, for instance,
+if they needed to roll back to a previous version of an add-on. We are
+re-introducing this backup on update toggle in this release, but in a smarter
+way. 🤓
+
+#### Backup on updating Home Assistant
+
+When updating Home Assistant, the toggle is now turned off by default and
+shows the last time you made a backup. This allows you to decide whether to make
+a new backup before updating.
+
+<img class="no-shadow" alt="Screenshot showing an Home Assistant Core update dialog, giving the option to make a backup before update." src="/images/blog/2025-02/backups-before-update-core.png" />
+
+If you turn the switch on, a full automated backup is created and synced to
+your configured locations, before the update is started.
+
+This full sync is done to ensure you have the most recent backup available in
+case the update causes issues and you need to restore your system. In the rare
+case a Home Assistant update fatally fails and you can’t access the backup page,
+if you’ve configured a second backup location, you’ll be able to download it
+from there.
+
+#### Backup on updating add-ons
+
+Things are slightly different when updating add-ons. The toggle exists here too,
+and is disabled by default. However, when you enable it, only a backup of your
+add-on and its data is created. That way you can keep around the previous
+version of the add-on, so you can always roll back to it if needed.
+
+<img class="no-shadow" alt="Screenshot showing an Home Assistant add-on update dialog, giving the option to make a backup before update." src="/images/blog/2025-02/backups-addons-before-update.png" />
+
+To prevent your system from filling up with old add-on backups, we only retain
+one backup per add-on, automatically deleting the previous backup whenever
+a new one is created. Add-on backups you created manually, of course,
+remain untouched and will not be deleted automatically.
+
+### Improved filenames for backups
+
+One piece of feedback we’ve seen a lot, is that the filenames created by backups
+can be a bit cryptic and hard to understand for humans.
+
+This feedback was fair, as the filename was a hash and originally not designed
+to be human-readable. This method was not newly introduced in the last release,
+but it was made more apparent with the new backup system and locations.
+
+So, in this release, we've improved the filenames of the backups stored on your
+backup locations. The filename now includes the date and time the backup was
+created, making it easier to understand and identify the backup you are looking
+for, even outside of Home Assistant.
+
+### New locations
+
+This release also introduces new locations to store your backups. There are new
+integrations for [Google Drive](/integrations/google_drive/) and
+[Microsoft OneDrive](/integrations/onedrive/), and backup support was added to
+the [Synology DSM](/integrations/synology_dsm) integration.
+
+<img class="no-shadow" alt="Screenshot showing the backup configuration panel, with all possible backup integrations set up!" src="/images/blog/2025-02/backups-new-locations.png" />
+
+## Voice
+
+Assist, our [private voice assistant](/voice_control/), is getting a few new
+features in this release. If you don't have Assist set up yet, check out our
+[Home Assistant Voice: Preview Edition](/voice-pe/) to get started.
+
+### Home Assistant will be able to call your analog phone to tell you a message
+
+Remember our tutorial on turning an analog phone into the
+[world's most private voice assistant](/voice_control/worlds-most-private-voice-assistant/)?
+Thanks to [Jamin](https://github.com/jaminh), we now have a way to call
+your analog phone from Home Assistant!
+
+You can use [`assist_satellite.announce`](/integrations/assist_satellite#action-assist_satelliteannounce)
+to have Home Assistant call your phone and play a message when someone picks up
+the phone.
+
+If you use an LLM as the brains for your voice assistant, you can take this one
+step further with the new [`assist_satellite.start_conversation`](/integrations/assist_satellite#action-assist_satellitestart_conversation)
+action. Instead of playing an announcement, it starts a conversation between
+Home Assistant and the user, with Home Assistant saying the first message.
+Left the garage door open for 30 minutes? No problem, let Home Assistant call
+and ask if they want to close it.
+
+_(Starting a conversation with the default conversation agent is a bit more work
+and did not make it this release)._
+
+### New Broadcast intent
+
+You can now broadcast messages to every other voice assistant in your home.
+Try it by saying _"Broadcast it is time for dinner"_.
+As always with new intents, support may vary
+[depending on your language](https://home-assistant.github.io/intents/),
+but our language leaders are working hard on making sure it will be supported
+soon in your language!
+
+### Setting Temperature on Thermostat
+
+A few releases ago we introduced an intent to get the current temperature from
+a climate device. As of this release, you can also set the target temperature
+of your thermostat by voice.
+
+By saying _"Set the temperature to 19 degrees"_ this will smartly target the
+area you are in (if you have a thermostat per area, such as thermostatic valves
+on your radiators) or the floor you are in (if you only have a central unit).
+You can also target specific devices by name if you prefer.
+
+### LLMs meet calendars
+
+Without complex custom tooling, LLM-based conversation agents previously could
+not fetch events from your calendar. This release changes that. Out of the box,
+LLM-based agents can now retrieve today’s and this week’s events from any of
+your calendars. Don’t forget to
+[expose your calendar entities](/voice_control/voice_remote_expose_devices/)
+to enable this functionality.
+
+### Shared history between the default conversation agent and its LLM-based fallback
+
+In [2024.12](/blog/2024/12/04/release-202412/) we introduced a lovely feature
+that allowed you to use our fast and local default conversation agent for most
+queries while still being able to fall back to a much more powerful LLM-based
+agent for more complex queries.
+
+This introduced some interesting behaviors. From a user perspective, it looked
+like you were talking to the same assistant, whereas, in reality, nothing was
+shared between the two agents. This led to some less-than-optimal scenarios,
+such as this one:
+
+<img class="no-shadow" alt="Screenshot of missing history in the conversation" src="/images/blog/2025-02/conversation-history-before.png" />
+
+The first command is processed locally by our default agent, but the follow-up
+request is processed by the LLM-based agent. Since no memory is shared, it does
+not understand what device you want to turn off.
+
+Starting with this release, both agents now share the same command history,
+helping address this issue.
+
+<img class="no-shadow" alt="Screenshot of the new improved behavior" src="/images/blog/2025-02/conversation-history-after.png" />
+
+### Model Context Protocol
+
+This release adds the [Model Context Protocol](https://modelcontextprotocol.io/introduction)
+to Home Assistant thanks to [Allen][@allenporter]. Home Assistant can both be an
+[MCP server](/integrations/mcp_server/) and an
+[MCP client](/integrations/mcp/). From the MCP website:
+
+> MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools.
+
+To give it a try yourself, [check out this client demo](https://gist.github.com/allenporter/b0e9946feb2ab60901c4f467ac1ba6f9).
+
+## 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:
+
+- **[Google Drive]**, added by [@tronikos]<br>
+  Add your Google Drive as a location to store your Home Assistant backups.
+- **[Homee]**, added by [@Taraman17]<br>
+  Integrate your [Homee smart home system] into Home Assistant.
+- **[igloohome]**, added by [@keithle888]<br>
+  Monitor the battery levels of your [igloo smart access device(s)].
+- **[LetPot]**, added by [@jpelgrom]<br>
+  Monitor and control your [LetPot indoor garden].
+- **[OneDrive]**, added by [@zweckj]<br>
+  Allows you to store your Home Assistant backups in your Microsoft OneDrive.
+- **[Overseerr]**, added by [@joostlek]<br>
+  Interact with your [Overseerr media requests] directly from Home Assistant.
+- **[Model Context Protocol Server]**, added by [@allenporter]<br>
+  Enables using Home Assistant to provide context for MCP LLM Client
+  Applications. For example, you can expose your Google Tasks to-do list as a
+  tool for [Claude Desktop].
+- **[Model Context Protocol]**, added by [@allenporter]<br>
+  Enables using [MCP Servers] in Home Assistant to provide additional tools to
+  use with a conversation agent.
+- **[Qbus]**, added by [@thomasddn]<br>
+  Allows you to integrate your [Qbus Control] into Home Assistant.
+
+This release also has a new virtual integration. Virtual integrations are stubs
+that are handled by other (existing) integrations to help with findability.
+The following virtual integration have been added:
+
+- **[Decorquip Dream]**, provided by [Motionblinds] added by [@starkillerOG]
+
+[@allenporter]: https://github.com/allenporter
+[@joostlek]: https://github.com/joostlek
+[@jpelgrom]: https://github.com/jpelgrom
+[@keithle888]: https://github.com/keithle888
+[@starkillerOG]: https://github.com/starkillerOG
+[@Taraman17]: https://github.com/Taraman17
+[@thomasddn]: https://github.com/thomasddn
+[@tronikos]: https://github.com/tronikos
+[@zweckj]: https://github.com/zweckj
+[Claude Desktop]: https://claude.ai/download
+[Decorquip Dream]: /integrations/decorquip/
+[Google Drive]: /integrations/google_drive
+[Homee smart home system]: https://hom.ee/
+[Homee]: /integrations/homee
+[igloo smart access device(s)]: https://www.igloohome.co/#products
+[igloohome]: /integrations/igloohome
+[LetPot indoor garden]: https://letpot.com/
+[LetPot]: /integrations/letpot
+[MCP Servers]: https://modelcontextprotocol.io/
+[Model Context Protocol Server]: /integrations/mcp_server
+[Model Context Protocol]: /integrations/mcp
+[Motionblinds]: /integrations/motion_blinds
+[OneDrive]: /integrations/onedrive
+[Overseerr media requests]: https://overseerr.dev/
+[Overseerr]: /integrations/overseerr
+[Qbus Control]: https://www.qbus.be/
+[Qbus]: /integrations/qbus/
+
+### 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:
+
+- A big shoutout to [@NoRi2909]! He has been reviewing and improving every single
+  piece of text we show anywhere in Home Assistant. Thank you for your hard work!
+- Also, [@lboue]! This hero keeps extending the device support for the [Matter]
+  integration by adding support for more and more devices. Home Assistant is
+  close to reaching full Matter 1.4 device support!
+- [@chemelli74] added support for the [Shelly BLU TRV] to the [Shelly]
+  integration. Nice!
+- The [HomeWizard Energy] integration now supports the
+  [HomeWizard Plug-In Battery]. Awesome work [@DCSBL]!
+- Thanks to [@iprak], the [Vesync] integration now supports humidifiers!
+- [@rytilahti] added vacuum support to the [TP-Link Smart Home] integration. Sweet!
+- The [Reolink] integration keeps evolving, [@starkillerOG] added support for baby crying detection as a sensor. Nice!
+- The [Bang & Olufsen] integration now provides entities allowing you to react
+  to physical button presses on all Bang & Olufsen devices. Thanks [@mj23000]!
+
+[@chemelli74]: https://github.com/chemelli74
+[@DCSBL]: https://github.com/DCSBL
+[@iprak]: https://github.com/iprak
+[@lboue]: https://github.com/lboue
+[@mj23000]: https://github.com/mj23000
+[@NoRi2909]: https://github.com/NoRi2909
+[@rytilahti]: https://github.com/rytilahti
+[@starkillerOG]: https://github.com/starkillerOG
+[Bang & Olufsen]: /integrations/bang_olufsen
+[HomeWizard Energy]: /integrations/homewizard
+[HomeWizard Plug-In Battery]: https://www.homewizard.com/nl/plug-in-battery/
+[Matter]: /integrations/matter
+[Reolink]: /integrations/reolink
+[Shelly BLU TRV]: https://www.shelly.com/products/shelly-blu-trv-single-pack
+[Shelly]: /integrations/shelly
+[TP-Link Smart Home]: /integrations/tplink
+[Vesync]: /integrations/vesync
+
+### Now available to set up from the UI
+
+While most {% term integrations %} can be set up directly from the Home Assistant
+user interface, some were only available using YAML configuration. We keep moving
+more integrations to the UI, making them more accessible for everyone
+to set up and use.
+
+The following integration is now available via the Home Assistant UI:
+
+- **[NMBS]**, done by [@silamon]
+- **[Filter]**, done by [@gjohansson-ST]
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@silamon]: https://github.com/silamon
+[Filter]: /integrations/filter
+[NMBS]: /integrations/nmbs
+
+## Other noteworthy changes
+
+- When using the [Generic thermostat], setting a temperature that matches
+  one of the presets will automatically select that preset as active.
+  Thanks [@domingues]!
+- [Time triggers] in automations can now be offset when using datetime input
+  helpers. Thanks [@Petro31]!
+
+[@domingues]: https://github.com/domingues
+[@Petro31]: https://github.com/Petro31
+[Generic thermostat]: /integrations/generic_thermostat
+[Time triggers]: /docs/automation/trigger/#time-trigger
+
+## Bluetooth config panel
+
+The [Bluetooth integration] now has its own configuration panel! 💙
+
+The panel is accessible by going to **Settings** > **Device & services**. Find
+and select the **Bluetooth** integration, and next select **Configure**.
+
+This new panel gives you access to the Bluetooth integration options and
+insights into the connection slot allocations. More importantly,
+it has an advertisement monitor!
+
+Selecting **Advertisement monitor** will open a new panel, where you can see
+information about your Bluetooth devices, including the raw advertisement data
+and how they are connected to your Home Assistant instance. This includes
+which [Bluetooth proxy] it connects through!
+
+<img class="no-shadow" alt="Screenshot of the new advertisement panel" src="/images/blog/2025-02/bluetooth-panel.png" />
+
+[Bluetooth integration]: /integrations/bluetooth
+[Bluetooth proxy]: /integrations/bluetooth/#remote-adapters-bluetooth-proxies
+
+## Preparing our graphs for the future
+
+This release includes a major overhaul of every graph we display and show in
+Home Assistant. We have entirely replaced the software library that renders
+these graphs in the frontend.
+
+You can most definitely tell things have changed, but everything still looks
+very similar. The latter was our goal for now, as we wanted the existing
+experience to be familiar.
+
+However, this change is a preparation for the future. We have many plans and
+ideas for our graphs, and this change was a necessary step to make those plans
+possible.
+
+## 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 "Ecovacs" %}
+
+The attributes on the vacuum entity for the lifespan of the main brush, side
+brush, and filter have been deprecated and are now removed. These attributes
+are superseded by dedicated sensor entities.
+
+([@gjohansson-ST] - [#134492]) ([documentation](/integrations/ecovacs))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#134492]: https://github.com/home-assistant/core/pull/134492
+
+{% enddetails %}
+
+{% details "Home Connect" %}
+
+Some appliances might lose their power entity as the API does not report the
+power setting.
+
+([@Diegorro98] - [#135930]) ([documentation](/integrations/home_connect))
+
+[@Diegorro98]: https://github.com/Diegorro98
+[#135930]: https://github.com/home-assistant/core/pull/135930
+
+{% enddetails %}
+
+{% details "IMGW-PIB" %}
+
+Some hydrology data is no longer available to Home Assistant users via IMGW-PIB
+API and for this reason, the following entities are removed:
+
+- `flood alarm` binary sensor
+- `flood alarm level` sensor
+- `flood warning` binary sensor
+- `flood warning level` sensor
+
+([@bieniu] - [#134668]) ([documentation](/integrations/imgw_pib))
+
+[@bieniu]: https://github.com/bieniu
+[#134668]: https://github.com/home-assistant/core/pull/134668
+
+{% enddetails %}
+
+{% details "KNX" %}
+
+The "State Updater" option in the integration settings now works as intended.
+Previously, the option wasn’t applied correctly.
+
+- When disabled: KNX will only read a `state_address` once when the connection
+  is established.
+- When enabled: KNX will also read any `state_address` if no value has been
+  received for one hour.
+
+Please review your integration settings to ensure this option is configured
+according to your preferences.
+
+([@farmio] - [#135611]) ([documentation](/integrations/knx))
+
+[@farmio]: https://github.com/farmio
+[#135611]: https://github.com/home-assistant/core/pull/135611
+
+{% enddetails %}
+
+{% details "Litter-Robot" %}
+
+Remove extra_state_attributes from Litter-Robot vacuum entities.
+These were previously migrated to sensors.
+
+([@natekspencer] - [#136196]) ([documentation](/integrations/litterrobot))
+
+[@natekspencer]: https://github.com/natekspencer
+[#136196]: https://github.com/home-assistant/core/pull/136196
+
+{% enddetails %}
+
+{% details "MQTT" %}
+
+To change the MQTT broker settings, you need to start a reconfiguration.
+When `CONFIGURE` is selected, MQTT shows a "MQTT settings" page with subscribe
+and publish tools. The `Re-configure MQTT` button will be replaced with
+an `MQTT options` page.
+
+The reconfiguration option will only be available from the MQTT integration
+entry context menu.
+
+([@jbouwh] - [#133342]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#133342]: https://github.com/home-assistant/core/pull/133342
+
+{% enddetails %}
+
+{% details "Pentair ScreenLogic" %}
+
+Raw states derived from ScreenLogic enums are now lowercase instead of Title
+Case. This change impacts:
+
+- pH/ORP dosing state sensor entities:
+  - `Dosing` -> `dosing`
+  - `Mixing` -> `mixing`
+  - `Monitoring` -> `monitoring`
+- The `preset_mode` state attribute for ScreenLogic climate entities, where
+  raw states have also been underscored-spaced and had any punctuation removed.
+  - `Solar` -> `solar`
+  - `Solar Preferred` -> `solar_preferred`
+  - `Heater` -> `heater`
+  - `Don't Change` -> `dont_change`
+
+These changes support the addition of translation keys for text-based entity
+states. You should update any references to the above states/preset_modes to
+the new, lowercase versions.
+
+([@dieselrabbit] - [#133866]) ([documentation](/integrations/screenlogic))
+
+[@dieselrabbit]: https://github.com/dieselrabbit
+[#133866]: https://github.com/home-assistant/core/pull/133866
+
+{% enddetails %}
+
+If you are a custom integration developer and want to learn about changes and
+new features available for your integration: Be sure to follow our
+[developer blog][devblog]. The following are the most notable for this release:
+
+- [Energy by distance units](https://developers.home-assistant.io/blog/2025/01/31/energy-distance-units/)
+- [Relocate dhcp/ssdp/usb/zeroconf ServiceInfo models](https://developers.home-assistant.io/blog/2025/01/15/service-info)
+
+[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.2](/changelogs/core-2025.2)

source/green/index.html

@@ -1010,7 +1010,6 @@ dark_header: true
           </h3>
           <p>
             You can add Home Assistant Connect ZBT-1 to control Zigbee and Thread* devices, set up Home Assistant Cloud for voice assistants, and integrate third-party USB accessories to support other smart standards, such as Z-Wave or Bluetooth.
-            <br>*Thread support is currently under development.
           </p>
           <a
             href="/connectzbt1"