2025.7: Sync codebase

source/_integrations/alexa_devices.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
 ha_iot_class: Cloud Polling
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - notify
   - sensor
   - switch

source/_integrations/altruist.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - sensor
 ha_integration_type: device
 ha_zeroconf: true
+ha_quality_scale: bronze
 ---
 
 The **Altruist** {% term integration %} connects Home Assistant to [Air Quality Sensor “Altruist“](https://robonomics.network/devices/altruist/) — a device designed for decentralized environmental monitoring. It captures noise, dust, and temperature data from the sensor over HTTP, making it available as locally usable entities within Home Assistant.

source/_integrations/assist_satellite.markdown

@@ -239,4 +239,3 @@ actions:
 ```
 
 {% endraw %}
-

source/_integrations/balay.markdown

@@ -31,6 +31,7 @@ ha_platforms:
   - switch
   - time
 ha_iot_class: Cloud Push
+ha_dhcp: true
 ha_zeroconf: true
 ---
 

source/_integrations/bosch_alarm.markdown

@@ -20,7 +20,7 @@ ha_platforms:
   - sensor
   - switch
 ha_integration_type: device
-ha_quality_scale: bronze
+ha_quality_scale: platinum
 ha_dhcp: true
 ---
 

source/_integrations/constructa.markdown

@@ -31,6 +31,7 @@ ha_platforms:
   - switch
   - time
 ha_iot_class: Cloud Push
+ha_dhcp: true
 ha_zeroconf: true
 ---
 

source/_integrations/derivative.markdown

@@ -11,6 +11,7 @@ ha_iot_class: Calculated
 ha_qa_scale: internal
 ha_codeowners:
   - '@afaucogney'
+  - '@karwosts'
 ha_domain: derivative
 ha_config_flow: true
 ha_platforms:

source/_integrations/eastron.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - button
   - diagnostics
   - number
+  - select
   - sensor
   - switch
 ha_iot_class: Local Polling

source/_integrations/gaggenau.markdown

@@ -31,6 +31,7 @@ ha_platforms:
   - switch
   - time
 ha_iot_class: Cloud Push
+ha_dhcp: true
 ha_zeroconf: true
 ---
 

source/_integrations/google_gemini.markdown

@@ -2,6 +2,7 @@
 title: Google Gemini
 description: Instructions on how to integrate Google Gemini as a conversation agent
 ha_category:
+  - Text-to-speech
   - Voice
 ha_release: 2023.6
 ha_domain: google_gemini
@@ -15,6 +16,7 @@ ha_config_flow: true
 ha_platforms:
   - conversation
   - diagnostics
+  - tts
 ha_iot_class: Cloud Polling
 ---
 

source/_integrations/google_generative_ai_conversation.markdown

@@ -2,8 +2,8 @@
 title: Google Generative AI
 description: Instructions on how to integrate Google Generative AI as a conversation agent
 ha_category:
-  - Voice
   - Text-to-speech
+  - Voice
 ha_release: 2023.6
 ha_iot_class: Cloud Polling
 ha_config_flow: true

source/_integrations/ipp.markdown

@@ -1,18 +1,23 @@
----
+---
-title: Internet Printing Protocol (IPP)
+title: Internet Printing Protocol (IPP)
-description: Instructions on how to integrate printers that support the Internet Printing Protocol (IPP) into Home Assistant.
+description: Instructions on how to integrate printers that support the Internet Printing Protocol (IPP) into Home Assistant.
-ha_category:
+ha_category:
-  - System monitor
+  - System monitor
-ha_release: 0.108
+ha_release: 0.108
-ha_iot_class: Local Polling
+ha_iot_class: Local Polling
-ha_config_flow: true
+ha_config_flow: true
-ha_codeowners:
+ha_codeowners:
-  - '@ctalkington'
+  - '@ctalkington'
-ha_domain: ipp
+ha_domain: ipp
----
+ha_platforms:
-
+  - diagnostics
-The `Internet Printing Protocol (IPP)` integration allows you to read current data from your networked printer that supports the [Internet Printing Protocol](https://www.pwg.org/ipp/everywhere.html).
+  - sensor
-
+ha_zeroconf: true
-It provides information about the printer's state and remaining ink levels.
+ha_integration_type: device
-
+---
-{% include integrations/config_flow.md %}
+
+The `Internet Printing Protocol (IPP)` integration allows you to read current data from your networked printer that supports the [Internet Printing Protocol](https://www.pwg.org/ipp/everywhere.html).
+
+It provides information about the printer's state and remaining ink levels.
+
+{% include integrations/config_flow.md %}

source/_integrations/ista_ecotrend.markdown

@@ -13,6 +13,7 @@ ha_platforms:
   - sensor
 ha_config_flow: true
 ha_integration_type: integration
+ha_quality_scale: gold
 ---
 
 The **ista EcoTrend** {% term integration %} for Home Assistant allows you to import your monthly meter readings from the [ista EcoTrend](https://ecotrend.ista.de) service.

source/_integrations/knx.markdown

@@ -48,6 +48,7 @@ ha_platforms:
   - weather
 ha_config_flow: true
 ha_integration_type: hub
+ha_quality_scale: silver
 ---
 
 The [KNX](https://www.knx.org) integration connects Home Assistant to your KNX installation, allowing you to control KNX devices, act on telegrams and forward state changes from other integrations entities to your KNX bus.

source/_integrations/lcn.markdown

@@ -25,6 +25,7 @@ ha_platforms:
   - switch
 ha_config_flow: true
 ha_integration_type: integration
+ha_quality_scale: bronze
 ---
 
 The **LCN** {% term integration %} for Home Assistant allows you to connect to [LCN](https://www.lcn.eu/) hardware devices.

source/_integrations/lg_thinq.markdown

@@ -23,6 +23,7 @@ ha_platforms:
 ha_integration_type: integration
 ha_codeowners:
   - '@LG-ThinQ-Integration'
+ha_dhcp: true
 ---
 
 The **LG ThinQ** integration allows you to connect LG ThinQ devices to Home Assistant. The features of this integration include:

source/_integrations/linak.markdown

@@ -6,8 +6,9 @@ ha_category:
 ha_domain: linak
 ha_integration_type: virtual
 ha_supporting_domain: idasen_desk
-ha_supporting_integration: IKEA Idåsen Desk
+ha_supporting_integration: IKEA Idasen Desk
 ha_release: '2023.10'
+ha_bluetooth: true
 ha_codeowners:
   - '@abmantis'
 ha_config_flow: true
@@ -16,7 +17,6 @@ ha_platforms:
   - cover
   - sensor
 ha_iot_class: Local Push
-ha_bluetooth: true
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/linkplay.markdown

@@ -1,54 +1,55 @@
----
+---
-title: LinkPlay
+title: LinkPlay
-description: Connect and control your LinkPlay media players using the LinkPlay integration
+description: Connect and control your LinkPlay media players using the LinkPlay integration
-ha_category:
+ha_category:
-  - Media player
+  - Media player
-ha_domain: linkplay
+ha_domain: linkplay
-ha_zeroconf: true
+ha_zeroconf: true
-ha_integration_type: integration
+ha_integration_type: hub
-ha_release: 2024.8
+ha_release: 2024.8
-ha_codeowners:
+ha_codeowners:
-  - '@Velleman'
+  - '@Velleman'
-ha_config_flow: true
+ha_config_flow: true
-ha_platforms:
+ha_platforms:
-  - media_player
+  - button
-  - button
+  - diagnostics
-ha_iot_class: Local Polling
+  - media_player
----
+ha_iot_class: Local Polling
-
+---
-The LinkPlay {% term integrations %} for Home Assistant allows you to control various media players based on the LinkPlay protocol. The integration supports auto-discovery on your local network through [Zeroconf](/integrations/zeroconf).
+
-
+The LinkPlay {% term integrations %} for Home Assistant allows you to control various media players based on the LinkPlay protocol. The integration supports auto-discovery on your local network through [Zeroconf](/integrations/zeroconf).
-{% include integrations/config_flow.md %}
+
-
+{% include integrations/config_flow.md %}
-## Features
+
-
+## Features
-### Media Player 
+
-
+### Media Player 
-The media player entity offers robust controls and playback features from the media player integration and provides additionally:
+
-
+The media player entity offers robust controls and playback features from the media player integration and provides additionally:
-- **Preset playback**: Play LinkPlay presets configured on the device using the action `linkplay.play_preset`. 
+
-- **Multiroom**: Combine multiple LinkPlay devices in a multiroom. Use the actions `media_player.join` and `media_player.unjoin`. 
+- **Preset playback**: Play LinkPlay presets configured on the device using the action `linkplay.play_preset`. 
-
+- **Multiroom**: Combine multiple LinkPlay devices in a multiroom. Use the actions `media_player.join` and `media_player.unjoin`. 
-### Buttons
+
-
+### Buttons
-The button entities provide some additional LinkPlay features available on the device:
+
-
+The button entities provide some additional LinkPlay features available on the device:
-- **Time Sync**: Synchronize the device's internal clock with the current time in Home Assistant. 
+
-- **Restart Device**: Reboot the device, allowing for convenient troubleshooting and maintenance.
+- **Time Sync**: Synchronize the device's internal clock with the current time in Home Assistant. 
-
+- **Restart Device**: Reboot the device, allowing for convenient troubleshooting and maintenance.
-## Actions
+
-
+## Actions
-The LinkPlay integration makes various custom actions available in addition to the [standard media player actions](/integrations/media_player/#actions).
+
-
+The LinkPlay integration makes various custom actions available in addition to the [standard media player actions](/integrations/media_player/#actions).
-### Action `linkplay.play_preset`
+
-
+### Action `linkplay.play_preset`
-Play a preset on a LinkPlay media player. 
+
-
+Play a preset on a LinkPlay media player. 
-{% note %}
+
-Companion apps, such as 4stream, allow to save music presets (for example, Spotify playlists). This action can be used to start playing these presets. 
+{% note %}
-{% endnote %}
+Companion apps, such as 4stream, allow to save music presets (for example, Spotify playlists). This action can be used to start playing these presets. 
-
+{% endnote %}
-| Data attribute | Optional | Description |
+
-| ---------------------- | -------- | ----------- |
+| Data attribute | Optional | Description |
-| `entity_id` | no | The speakers to target. To target all LinkPlay devices, use `all`.
+| ---------------------- | -------- | ----------- |
-| `preset_number` | no | The number of the preset to play.
+| `entity_id` | no | The speakers to target. To target all LinkPlay devices, use `all`.
+| `preset_number` | no | The number of the preset to play.

source/_integrations/locative.markdown

@@ -1,23 +1,27 @@
----
+---
-title: "Locative"
+title: Locative
-description: "Instructions on how to use Locative to track devices in Home Assistant."
+description: Instructions on how to use Locative to track devices in Home Assistant.
-ha_category:
+ha_category:
-  - Presence detection
+  - Presence detection
-ha_release: 0.86
+ha_release: 0.86
-ha_iot_class: Cloud Push
+ha_iot_class: Local Push
-ha_domain: locative
+ha_domain: locative
----
+ha_platforms:
-
+  - device_tracker
-This platform allows you to detect presence using [Locative](https://www.locative.app/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
+ha_config_flow: true
-
+ha_integration_type: integration
-Install on your smartphone:
+---
-
+
-- [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4)
+This platform allows you to detect presence using [Locative](https://www.locative.app/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
-
+
-To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on its first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
+Install on your smartphone:
-
+
-<p class='img'>
+- [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4)
-  <img src='/images/screenshots/locative.png'/>
+
-</p>
+To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on its first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
-
+
-When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
+<p class='img'>
+  <img src='/images/screenshots/locative.png'/>
+</p>
+
+When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".

source/_integrations/meater.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
   - '@emontnemery'
 ha_domain: meater
 ha_platforms:
+  - diagnostics
   - sensor
 ha_integration_type: integration
 ---

source/_integrations/motionmount.markdown

@@ -1,115 +1,116 @@
----
+---
-title: Vogel's MotionMount
+title: Vogel's MotionMount
-description: Instructions on how to integrate Vogel's MotionMount into Home Assistant.
+description: Instructions on how to integrate Vogel's MotionMount into Home Assistant.
-ha_category:
+ha_category:
-  - Number
+  - Binary sensor
-  - Select
+  - Number
-  - Binary sensor
+  - Select
-  - Sensor
+  - Sensor
-ha_release: 2024.1
+ha_release: 2024.1
-ha_iot_class: Local Push
+ha_iot_class: Local Push
-ha_config_flow: true
+ha_config_flow: true
-ha_platforms:
+ha_platforms:
-  - number
+  - binary_sensor
-  - select
+  - number
-  - binary_sensor
+  - select
-  - sensor
+  - sensor
-ha_codeowners:
+ha_codeowners:
-  - '@RJPoelstra'
+  - '@laiho-vogels'
-ha_domain: motionmount
+ha_domain: motionmount
-ha_zeroconf: true
+ha_zeroconf: true
----
+ha_quality_scale: bronze
-
+ha_integration_type: device
-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.
+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.
-
+
-It provides information about the current position of the mount and allows setting a new position.
+This integration uses the Ethernet (IP) connection of your MotionMount. It's not possible to connect using the RS-232 connection.
-
+
-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.
+It provides information about the current position of the mount and allows setting a new position.
-
+
-{% include integrations/config_flow.md %}
+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.
-
+
-{% configuration_basic %}
+{% include integrations/config_flow.md %}
-Host:
+
-  description: Hostname or IP address of the device, for example:`192.168.1.2`.
+{% configuration_basic %}
-Port:
+Host:
-  description: The TCP port of the device. Defaults to 23. Only change this when you're absolutely certain that it shouldn't be 23.
+  description: Hostname or IP address of the device, for example:`192.168.1.2`.
-PIN:
+Port:
-  description: The user level pincode, if configured on the device.
+  description: The TCP port of the device. Defaults to 23. Only change this when you're absolutely certain that it shouldn't be 23.
-{% endconfiguration_basic %}
+PIN:
-
+  description: The user level pincode, if configured on the device.
-## Removing the integration
+{% endconfiguration_basic %}
-
+
-This integration follows standard integration removal. No extra steps are required.
+## Removing the integration
-
+
-{% include integrations/remove_device_service.md %}
+This integration follows standard integration removal. No extra steps are required.
-
+
-## Data updates
+{% include integrations/remove_device_service.md %}
-
+
-The MotionMount pushes new data to the integration.
+## Data updates
-The only exception is the presets. Changes to the presets are {% term polling polled %}, by default every 60 seconds.
+
-
+The MotionMount pushes new data to the integration.
-## Known limitations
+The only exception is the presets. Changes to the presets are {% term polling polled %}, by default every 60 seconds.
-
+
-The integration does not provide the ability to configure the MotionMount.
+## Known limitations
-All settings, including configuring presets, should be done via the MotionMount app.
+
-
+The integration does not provide the ability to configure the MotionMount.
-Only IP connections are supported. Connection via RS-232 or Bluetooth Low Energy is not supported.
+All settings, including configuring presets, should be done via the MotionMount app.
-
+
-## Supported devices
+Only IP connections are supported. Connection via RS-232 or Bluetooth Low Energy is not supported.
-
+
-The following devices are supported:
+## Supported devices
-
+
-- TVM 7675 Pro (SIGNATURE MotionMount with Pro extension)
+The following devices are supported:
-
+
-## Unsupported devices
+- TVM 7675 Pro (SIGNATURE MotionMount with Pro extension)
-
+
-The following devices are *not* supported:
+## Unsupported devices
-
+
-- TVM 7675 (SIGNATURE MotionMount without Pro extension)
+The following devices are *not* supported:
-- TVM 7355 (NEXT MotionMount)
+
-
+- TVM 7675 (SIGNATURE MotionMount without Pro extension)
-## Supported functionality
+- TVM 7355 (NEXT MotionMount)
-
+
-### Entities
+## Supported functionality
-
+
-#### Sensors
+### Entities
-
+
-- **Moving**
+#### Sensors
-  - **Description**: Indicates whether the MotionMount is moving.
+
-
+- **Moving**
-- **Error Status**
+  - **Description**: Indicates whether the MotionMount is moving.
-  - **Description**: The error status of the MotionMount.
+
-    - None: There is no error.
+- **Error Status**
-    - Motor: There is a problem communicating with the motor.
+  - **Description**: The error status of the MotionMount.
-    - HDMI CEC: There is a problem communicating with the TV. Check the HDMI cable.
+    - None: There is no error.
-    - Obstruction: The MotionMount detected an obstacle and stopped moving.
+    - Motor: There is a problem communicating with the motor.
-    - TV Width Constraint: The MotionMount detected that the TV moved too close to the wall and stopped moving.
+    - HDMI CEC: There is a problem communicating with the TV. Check the HDMI cable.
-    - Internal: There is an internal error. Refer to the MotionMount app for support.
+    - Obstruction: The MotionMount detected an obstacle and stopped moving.
-
+    - TV Width Constraint: The MotionMount detected that the TV moved too close to the wall and stopped moving.
-#### Numbers
+    - Internal: There is an internal error. Refer to the MotionMount app for support.
-
+
-- **Extension**
+#### Numbers
-  - **Description**: The current extension of the MotionMount from the wall.
+
-
+- **Extension**
-- **Turn**
+  - **Description**: The current extension of the MotionMount from the wall.
-  - **Description**: The current rotation of the MotionMount.
+
-
+- **Turn**
-#### Selects
+  - **Description**: The current rotation of the MotionMount.
-
+
-- **Presets**
+#### Selects
-  - **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.
+- **Presets**
-
+  - **Description**: If the MotionMount is at a preset location, this shows the corresponding preset.
-## Troubleshooting
+        Any preset can be selected to move the MotionMount to this preset position.
-
+
-### Can't connect to device
+## Troubleshooting
-
+
-1. Make sure the device is powered on.
+### Can't connect to device
-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.
+1. Make sure the device is powered on.
-    - In case of doubt, perform a network reset by holding the reset button for approx. 5 seconds.
+2. Make sure the device is connected to the same network as Home Assistant.
-      - **Result**: The LED will start to blink slowly. This indicates that the network configuration is being reset to use DHCP.
+3. Make sure the IP address of the MotionMount is configured correctly.
-      - **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.
+    - 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/music_assistant.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@music-assistant'
 ha_domain: music_assistant
 ha_platforms:
+  - button
   - media_player
 ha_zeroconf: true
 ha_integration_type: integration

source/_integrations/ntfy.markdown

@@ -13,6 +13,7 @@ ha_integration_type: integration
 ha_platforms:
   - diagnostics
   - notify
+  - sensor
 ha_quality_scale: bronze
 ---
 

source/_integrations/paperless_ngx.markdown

@@ -18,6 +18,7 @@ related:
 ha_platforms:
   - diagnostics
   - sensor
+  - update
 ---
 
 The **Paperless-ngx** {% term integration %} allows you to connect your [Paperless-ngx](https://docs.paperless-ngx.com/) instance to Home Assistant and monitor its status and activity.

source/_integrations/playstation_network.markdown

@@ -7,15 +7,19 @@ ha_release: 2025.7
 ha_iot_class: Cloud Polling
 ha_domain: playstation_network
 ha_platforms:
+  - diagnostics
   - media_player
+  - sensor
 ha_codeowners:
   - '@jackjpowell'
+  - '@tr4nt0r'
 ha_config_flow: true
 ha_quality_scale: bronze
-ha_integration_type: integration
+ha_integration_type: service
 related:
   - url: https://playstation.com/
     title: Playstation
+ha_dhcp: true
 ---
 
 The **PlayStation Network** {% term integration %} enables you to seamlessly integrate information from your currently playing game in Home Assistant.

source/_integrations/qbus.markdown

@@ -8,6 +8,7 @@ ha_category:
   - Switch
 ha_platforms:
   - climate
+  - cover
   - light
   - scene
   - switch

source/_integrations/remote_calendar.markdown

@@ -12,6 +12,7 @@ ha_platforms:
   - diagnostics
 ha_codeowners:
   - '@Thomas55555'
+  - '@allenporter'
 ha_integration_type: service
 ha_quality_scale: silver
 ---

source/_integrations/samsungtv.markdown

@@ -19,6 +19,7 @@ ha_platforms:
 ha_zeroconf: true
 ha_dhcp: true
 ha_integration_type: device
+ha_quality_scale: bronze
 ---
 
 The `samsungtv` platform allows you to control a [Samsung Smart TV](https://www.samsung.com/uk/tvs/all-tvs/).

source/_integrations/spotify.markdown

@@ -10,7 +10,6 @@ ha_codeowners:
   - '@frenck'
   - '@joostlek'
 ha_domain: spotify
-ha_zeroconf: true
 ha_platforms:
   - diagnostics
   - media_player

source/_integrations/telegram_bot.markdown

@@ -8,7 +8,9 @@ ha_iot_class: Cloud Push
 ha_config_flow: true
 ha_domain: telegram_bot
 ha_integration_type: integration
-ha_quality_scale: legacy
+ha_quality_scale: bronze
+ha_codeowners:
+  - '@hanwg'
 ---
 
 Use Telegram on your mobile or desktop device to send and receive messages or commands to/from your Home Assistant.

source/_integrations/tilt_pi.markdown

@@ -5,16 +5,17 @@ ha_category:
   - Sensor
 ha_release: '2025.7'
 ha_iot_class: Local Polling
-ha_quality_scale: Bronze
+ha_quality_scale: bronze
 ha_config_flow: true
 ha_codeowners:
   - '@michaelheyman'
 ha_domain: tilt_pi
 ha_platforms:
-   - sensor
+  - sensor
 related:
   - url: https://tilthydrometer.com/collections/tilt-pi
     title: Tilt Pi product page
+ha_integration_type: integration
 ---
 
 The **Tilt Pi** {% term integration %} allows you to connect a Tilt Pi to Home Assistant to

source/_integrations/tts.markdown

@@ -198,4 +198,4 @@ The recommended way to overcome these obstacles is to not manually configure a l
 
 Some media players could reproduce only partial, corrupted or no audio at all when the audio format is not fully supported. In such cases it is required to experiment with different combinations of audio formats, channels, sample rates and bits using [preferred audio settings](#preferred-audio-settings) options.
 
-For example, some Google Cast devices skip initial audio part when the audio is sampled at 22050Hz, and to fix the problem it is required to set the `preferred_sample_rate` setting in the `options` option to `44100`. 
+For example, some Google Cast devices skip initial audio part when the audio is sampled at 22050Hz, and to fix the problem it is required to set the `preferred_sample_rate` setting in the `options` option to `44100`.

source/_integrations/zerproc.markdown

@@ -19,4 +19,3 @@ This {% term integration %} discovers nearby Zerproc lights and adds them to Hom
 {% include integrations/config_flow.md %}
 
 The {% term integration %} will scan for nearby devices, and is completed if any are found. No additional configuration is required. The integration will perform a BLE scan every 60 seconds to search for new devices.
-