home-assistant · c0ffeeca7 · Dec 13, 2025 · Dec 12, 2025 · Dec 12, 2025 · Dec 12, 2025
diff --git a/source/_integrations/alarm_control_panel.mqtt.markdown b/source/_integrations/alarm_control_panel.mqtt.markdown
@@ -11,7 +11,7 @@ related:
     title: Configuration file
 ---
 
-The `mqtt` alarm panel {% term integration %} enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
+The **MQTT Alarm control panel** {% term integration %} enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
 
 The {% term integration %} will accept the following states from your Alarm Panel (in lower case):
 

diff --git a/source/_integrations/binary_sensor.mqtt.markdown b/source/_integrations/binary_sensor.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` binary sensor platform uses an MQTT message received to set the binary sensor's state to `on`, `off` or `unknown`.
+The **MQTT binary sensor** {% term integration %} uses an MQTT message received to set the binary sensor's state to `on`, `off` or `unknown`.
 
 The state will be updated only after a new message is published on `state_topic` matching `payload_on`, `payload_off` or `None`. If these messages are published with the `retain` flag set,
 the binary sensor will receive an instant state update after subscription and Home Assistant will display the correct state on startup.

diff --git a/source/_integrations/blackbird.markdown b/source/_integrations/blackbird.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `blackbird` platform allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) (8x8) using a serial or IP connection, this integration does not support the 4x4 matrix switch.
+The **Monoprice Blackbird Matrix Switch** {% term integration %} allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) (8x8) using a serial or IP connection, this integration does not support the 4x4 matrix switch.
 
 To add a Blackbird 8x8 device to your installation, add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}

diff --git a/source/_integrations/button.mqtt.markdown b/source/_integrations/button.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` button platform lets you send an MQTT message when the button is pressed in the frontend or the button press action is called. This can be used to expose some service of a remote device, for example reboot.
+The **MQTT button** {% term integration %} lets you send an MQTT message when the button is pressed in the frontend or the button press action is called. This can be used to expose some service of a remote device, for example reboot.
 
 To use an MQTT button in your installation, [add a MQTT device as a subentry](/integrations/mqtt/#configuration), or add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}

diff --git a/source/_integrations/camera.mqtt.markdown b/source/_integrations/camera.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
+The **MQTT camera** {% term integration %} allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
 
 This can be used with an application or a service capable of sending images through MQTT.
 

diff --git a/source/_integrations/ccm15.markdown b/source/_integrations/ccm15.markdown
@@ -15,7 +15,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The CCM15 integration allows you to integrate [Midea CCM15](https://mbt.midea.com/hvac-goods/midea-products-category/vrfs/vrf-controller/central-controller-ccm-15) devices in Home Assistant.
+The **CCM15** {% term integration %} allows you to integrate [Midea CCM15](https://mbt.midea.com/hvac-goods/midea-products-category/vrfs/vrf-controller/central-controller-ccm-15) devices in Home Assistant.
 
 There is currently support for the following device types within Home Assistant:
 

diff --git a/source/_integrations/climate.mqtt.markdown b/source/_integrations/climate.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Local Polling
 ha_domain: mqtt
 ---
 
-The `mqtt` climate platform lets you control your MQTT enabled HVAC devices.
+The **MQTT climate** {% term integration %} lets you control your MQTT enabled HVAC devices.
 
 ## Configuration
 

diff --git a/source/_integrations/cover.mqtt.markdown b/source/_integrations/cover.mqtt.markdown
@@ -8,7 +8,7 @@ ha_release: 0.18
 ha_domain: mqtt
 ---
 
-The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a roller shutter or a garage door).
+The **MQTT cover** {% term integration %} allows you to control an MQTT cover (such as blinds, a roller shutter or a garage door).
 
 ## Configuration
 

diff --git a/source/_integrations/device_tracker.mqtt.markdown b/source/_integrations/device_tracker.mqtt.markdown
@@ -12,7 +12,7 @@ related:
 ---
 
 
-The `mqtt` device tracker {% term integration %} allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in {% term "`configuration.yaml`" %} and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
+The **MQTT device tracker** {% term integration %} allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in {% term "`configuration.yaml`" %} and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
 
 ## Configuration
 

diff --git a/source/_integrations/device_trigger.mqtt.markdown b/source/_integrations/device_trigger.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` device trigger platform uses an MQTT message payload to generate device trigger events.
+The **MQTT Device trigger** {% term integration %} uses an MQTT message payload to generate device trigger events.
 
 An MQTT device trigger is a better option than a [binary sensor](/integrations/binary_sensor.mqtt/) for buttons, remote controls etc.
 

diff --git a/source/_integrations/event.mqtt.markdown b/source/_integrations/event.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` event platform allows you to process event info from an MQTT message. Events are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. With the event some event attributes can be sent to become available as an attribute on the entity. MQTT events are stateless. For example, a doorbell does not have a state like being "on" or "off" but instead is momentarily pressed.
+The **MQTT Event** {% term integration %} allows you to process event info from an MQTT message. Events are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. With the event some event attributes can be sent to become available as an attribute on the entity. MQTT events are stateless. For example, a doorbell does not have a state like being "on" or "off" but instead is momentarily pressed.
 
 ## Configuration
 

diff --git a/source/_integrations/fan.mqtt.markdown b/source/_integrations/fan.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` fan platform lets you control your MQTT enabled fans.
+The **MQTT Fan** {% term integration %} lets you control your MQTT enabled fans.
 
 ## Configuration
 

diff --git a/source/_integrations/flux_led.markdown b/source/_integrations/flux_led.markdown
@@ -26,7 +26,7 @@ ha_dhcp: true
 ha_integration_type: integration
 ---
 
-The Magic Home {% term integration %} supports several brands of switches, bulbs, and controllers that use the same protocol. Chances are high that your bulb or controller (eg. WiFi LED CONTROLLER) will work with this integration if you can control the device with the Magic Home app or the Surp Life app.
+The **Magic Home** {% term integration %} supports several brands of switches, bulbs, and controllers that use the same protocol. Chances are high that your bulb or controller (eg. WiFi LED CONTROLLER) will work with this integration if you can control the device with the Magic Home app or the Surp Life app.
 
 This integration will provide local control over your LED lights/strips and can be configured to auto-scan your network for controllers or for you to manually configure individual lights by their IP address.
 

diff --git a/source/_integrations/humidifier.mqtt.markdown b/source/_integrations/humidifier.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` humidifier platform lets you control your MQTT enabled humidifiers.
+The **MQTT Humidifier** {% term integration %} lets you control your MQTT enabled humidifiers.
 
 ## Configuration
 

diff --git a/source/_integrations/image.mqtt.markdown b/source/_integrations/image.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` image platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as an image.
+The **MQTT Image** {% term integration %} allows you to integrate the content of an image file sent through MQTT into Home Assistant as an image.
 The `image` platform is a simplified version of the `camera` platform that only accepts images.
 Every time a message under the `image_topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `image_topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
 

diff --git a/source/_integrations/lawn_mower.mqtt.markdown b/source/_integrations/lawn_mower.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` `lawn_mower` platform allows controlling a lawn mower over MQTT.
+The **MQTT lawn mower** {% term integration %} allows controlling a lawn mower over MQTT.
 
 ## Configuration
 

diff --git a/source/_integrations/light.mqtt.markdown b/source/_integrations/light.mqtt.markdown
@@ -8,7 +8,7 @@ ha_release: 0.8
 ha_domain: mqtt
 ---
 
-The `mqtt` light platform lets you control your MQTT enabled lights through one of the supported message schemas, `default`, `json` or `template`.
+The **MQTT Light** {% term integration %} lets you control your MQTT enabled lights through one of the supported message schemas, `default`, `json` or `template`.
 
 ## Comparison of light MQTT schemas
 

diff --git a/source/_integrations/lock.mqtt.markdown b/source/_integrations/lock.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` lock platform lets you control your MQTT enabled locks.
+The **MQTT Lock** {% term integration %} lets you control your MQTT enabled locks.
 
 ## Configuration
 

diff --git a/source/_integrations/madvr.markdown b/source/_integrations/madvr.markdown
@@ -19,7 +19,7 @@ ha_platforms:
 ha_integration_type: device
 ---
 
-The madVR Envy allows for the automation and control of [madVR Envy devices](https://madvrenvy.com).
+The **madVR Envy** {% term integration %} allows for the automation and control of [madVR Envy devices](https://madvrenvy.com).
 
 ## Supported Devices
 

diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown
@@ -16,7 +16,7 @@ related:
     title: Configuration file
 ---
 
-The `manual` alarm control panel {% term integration %} enables you to create an alarm system in Home Assistant.
+The **Manual Alarm control panel** {% term integration %} enables you to create an alarm system in Home Assistant.
 
 ## Configuration
 

diff --git a/source/_integrations/manual_mqtt.markdown b/source/_integrations/manual_mqtt.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mqtt` {% term integration %} extends the [manual alarm](/integrations/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
+The **MQTT** {% term integration %} extends the [manual alarm](/integrations/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
 
 It's essentially the opposite of the [MQTT Alarm Panel](/integrations/alarm_control_panel.mqtt/) which allows Home Assistant to observe an existing, fully-featured alarm where all of the alarm logic is embedded in that physical device.
 

diff --git a/source/_integrations/marytts.markdown b/source/_integrations/marytts.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `marytts` text-to-speech {% term integration %} uses [MaryTTS](https://marytts.github.io/) text-to-speech engine to read a text with natural sounding voices.
+The **MaryTTS** {% term integration %} uses [MaryTTS](https://marytts.github.io/) text-to-speech engine to read a text with natural sounding voices.
 
 ## Configuration
 

@@ -19,7 +19,7 @@ ha_config_flow: true
 ha_quality_scale: bronze
 ---
 
-The `mastodon` platform uses [Mastodon](https://joinmastodon.org/) to post status updates and get account statistics.
+The **Mastodon** {% term integration %} uses [Mastodon](https://joinmastodon.org/) to post status updates and get account statistics.
 
 ### Setup
 

diff --git a/source/_integrations/matter.markdown b/source/_integrations/matter.markdown
@@ -55,7 +55,7 @@ related:
 ha_zeroconf: true
 ---
 
-The Matter {% term integration %} allows you to control Matter devices on your local Wi-Fi or {% term Thread %} network.
+The **Matter** {% term integration %} allows you to control Matter devices on your local Wi-Fi or {% term Thread %} network.
 
 For communicating with Matter devices, the Home Assistant integration runs its own "Matter controller" as add-on. This Matter Server add-on runs the controller software as a separate process and connects your Matter network (called Fabric in technical terms) and Home Assistant. The Home Assistant Matter integration connects to this server via a WebSocket connection.
 

@@ -16,7 +16,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Meater Smart Meat Thermometer {% term integration %} allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs.
+The **Meater** {% term integration %} allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs.
 
 {% include integrations/config_flow.md %}
 

@@ -16,7 +16,7 @@ related:
 ha_config_flow: true
 ---
 
-The Media extractor {% term integration %} gets a stream URL and sends it to a media player entity. This integration can extract entity specific streams if configured accordingly.
+The **Media extractor** {% term integration %} gets a stream URL and sends it to a media player entity. This integration can extract entity specific streams if configured accordingly.
 
 {% note %}
 Media extractor doesn't transcode streams, it just tries to find a stream that matches the requested query.

@@ -11,7 +11,7 @@ ha_quality_scale: internal
 ha_integration_type: system
 ---
 
-The Media source {% term integration %} platform allows integrations to expose media for
+The **Media source** {% term integration %} platform allows integrations to expose media for
 use inside Home Assistant through the Media Browser panel or through supported
 media players like Google Cast.
 

@@ -17,7 +17,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mediaroom` {% term integration %} allows you to control a [Mediaroom](https://en.wikipedia.org/wiki/Ericsson_Mediaroom) Set-Top Box (STB) from Home Assistant.
+The **Mediaroom** {% term integration %} allows you to control a [Mediaroom](https://en.wikipedia.org/wiki/Ericsson_Mediaroom) Set-Top Box (STB) from Home Assistant.
 
 To add a Mediaroom STB to your installation, add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}

@@ -17,7 +17,7 @@ ha_codeowners:
   - '@erwindouna'
 ---
 
-The `melcloud` integration integrates Mitsubishi Electric's [MELCloud](https://www.melcloud.com/) enabled devices into Home Assistant.
+The **MELCloud** {% term integration %} integrates Mitsubishi Electric's [MELCloud](https://www.melcloud.com/) enabled devices into Home Assistant.
 
 ## Device support
 

diff --git a/source/_integrations/melissa.markdown b/source/_integrations/melissa.markdown
@@ -18,7 +18,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `melissa` {% term integration %} is the main integration to connect to a [Melissa Climate](https://seemelissa.com/) A/C control.
+The **Melissa** {% term integration %} is the main integration to connect to a [Melissa Climate](https://seemelissa.com/) A/C control.
 
 There is currently support for the following device types within Home Assistant:
 

diff --git a/source/_integrations/melnor.markdown b/source/_integrations/melnor.markdown
@@ -19,7 +19,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Melnor Bluetooth integration allows you to control your Melnor Bluetooth watering valves.
+The **Melnor Bluetooth** {% term integration %} allows you to control your Melnor Bluetooth watering valves.
 The devices are set up through Bluetooth and don't need any additional bridge or gateway.
 
 1-zone, 2-zone, and 4-zone valves are supported.

diff --git a/source/_integrations/message_bird.markdown b/source/_integrations/message_bird.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `MessageBird` notification {% term integration %} sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone.
+The **MessageBird** {% term integration %} sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone.
 
 ## Setup
 

@@ -14,6 +14,6 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `met` platform uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
+The **Meteorologisk institutt (Met.no)** {% term integration %} uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
 
 {% include integrations/config_flow.md %}
diff --git a/source/_integrations/met_eireann.markdown b/source/_integrations/met_eireann.markdown
@@ -14,7 +14,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Met Éireann {% term integration %} uses the [Met Éireann](https://met.ie) (The Irish Meteorological Service) Public Weather Forecast API to provide current and forecasted weather data for a given location. This integration is in no way affiliated with or endorsed by Met Éireann.
+The **Met Éireann** {% term integration %} uses the [Met Éireann](https://met.ie) (The Irish Meteorological Service) Public Weather Forecast API to provide current and forecasted weather data for a given location. This integration is in no way affiliated with or endorsed by Met Éireann.
 
 {% note %}
 The Met Éireann API will only provide data for Ireland, the UK and a small part of northern France. For specific coverage, please see the Notes on API document available [here](https://data.gov.ie/dataset/met-eireann-forecast-api/resource/027da6d5-d819-48d1-9b16-331dba169bd1).

@@ -18,7 +18,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `meteo_france` integration uses the meteorological data from [Météo-France](http://www.meteofrance.com/) to provide weather forecast for any location in the world with a focus on France. One or more locations can be set via the front end or via the configuration file.
+The **Météo-France** {% term integration %} uses the meteorological data from [Météo-France](http://www.meteofrance.com/) to provide weather forecast for any location in the world with a focus on France. One or more locations can be set via the front end or via the configuration file.
 
 The integration support the following platforms within Home Assistant:
 

diff --git a/source/_integrations/meteoalarm.markdown b/source/_integrations/meteoalarm.markdown
@@ -14,7 +14,7 @@ ha_integration_type: integration
 ha_quality_scale: legacy
 ---
 
-The `MeteoAlarm` platform allows one to watch for weather alerts in Europe from [MeteoAlarm](https://www.meteoalarm.org) (EUMETNET). To use this binary sensor, you need the country and the province name from  [MeteoAlarm](https://feeds.meteoalarm.org). Please note that it is crucial to write the country name exactly as it appears in the URL starting with https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-, including any hyphens used in the name. Failure to do so may result in errors or incorrect data.
+The **MeteoAlarm** {% term integration %} allows one to watch for weather alerts in Europe from [MeteoAlarm](https://www.meteoalarm.org) (EUMETNET). To use this binary sensor, you need the country and the province name from  [MeteoAlarm](https://feeds.meteoalarm.org). Please note that it is crucial to write the country name exactly as it appears in the URL starting with https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-, including any hyphens used in the name. Failure to do so may result in errors or incorrect data.
 
 The name of the province can be found using the [MeteoAlarm EMMA_ID Region explorer tool](https://saratoga-weather.org/meteoalarm-map/)
-Original file line number
+Diff line change
@@ Expand Up / @@ -12,7 +12,7 @@ related: @@
     ---
-    The `mqtt` device tracker {% term integration %} allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in {% term "`configuration.yaml`" %} and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
+    The **MQTT device tracker** {% term integration %} allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in {% term "`configuration.yaml`" %} and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
     ## Configuration
@@ Expand Down @@