diff --git a/source/_integrations/bbox.markdown b/source/_integrations/bbox.markdown index 8d82bde2674..667f43a3aef 100644 --- a/source/_integrations/bbox.markdown +++ b/source/_integrations/bbox.markdown @@ -17,7 +17,7 @@ related: title: Configuration file --- -The `bbox` platform uses the [Bbox Modem Router](https://www.bouyguestelecom.fr/offres-internet/bbox-fit) from the French Internet provider Bouygues Telecom. Sensors are mainly bandwidth measures. +The `bbox` {% term integration %} uses the [Bbox Modem Router](https://www.bouyguestelecom.fr/offres-internet/bbox-fit) from the French Internet provider Bouygues Telecom. Sensors are mainly bandwidth measures. There is currently support for the following device types within Home Assistant: @@ -30,9 +30,9 @@ Due to third party limitation, the sensors will only be available if Home Assist ## Presence detection -The `bbox` platform offers presence detection by looking at connected devices to a [Bbox](https://www.bouyguestelecom.fr/offres-internet/bbox-fit) based router from [Bouygues](https://www.bouyguestelecom.fr/), which is one of the main Internet provider in France. +The `bbox` {% term integration %} offers presence detection by looking at connected devices to a [Bbox](https://www.bouyguestelecom.fr/offres-internet/bbox-fit) based router from [Bouygues](https://www.bouyguestelecom.fr/), which is one of the main Internet provider in France. -Bbox is a generic name for different hardware routers. The platform has been tested with the following devices: +Bbox is a generic name for different hardware routers. The {% term integration %} has been tested with the following devices: - Sagem F@st 5330b @@ -63,7 +63,8 @@ See the [device tracker integration page](/integrations/device_tracker/) for ins ## Sensor -To add Bbox sensors to your installation, add the following to your `configuration.yaml` file: +To add Bbox sensors to your installation, add the following to your {% term "`configuration.yaml`" %} file. +{% include integrations/restart_ha_after_config_inclusion.md %} ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/binary_sensor.mqtt.markdown b/source/_integrations/binary_sensor.mqtt.markdown index a3bbb1fd63e..5b64bd29f9b 100644 --- a/source/_integrations/binary_sensor.mqtt.markdown +++ b/source/_integrations/binary_sensor.mqtt.markdown @@ -21,7 +21,7 @@ Stateless devices such as buttons, remote controls etc are better represented by The `mqtt` binary sensor platform optionally supports a list of `availability` topics to receive online and offline messages (birth and LWT messages) from the MQTT device. During normal operation, if the MQTT sensor device goes offline (i.e., publishes `payload_not_available` to an `availability` topic), Home Assistant will display the binary sensor as `unavailable`. If these messages are published with the `retain` flag set, the binary sensor will receive an instant update after subscription and Home Assistant will display the correct availability state of the binary sensor when Home Assistant starts up. If the `retain` flag is not set, Home Assistant will display the binary sensor as `unavailable` when Home Assistant starts up. If no `availability` topic is defined, Home Assistant will consider the MQTT device to be `available` and will display its state. To use an MQTT binary sensor in your installation, -add the following to your `configuration.yaml` file: +add the following to your {% term "`configuration.yaml`" %} file: ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/binary_sensor.rest.markdown b/source/_integrations/binary_sensor.rest.markdown index 10e9f358dd3..dbf2c7e9cc2 100644 --- a/source/_integrations/binary_sensor.rest.markdown +++ b/source/_integrations/binary_sensor.rest.markdown @@ -33,7 +33,7 @@ The JSON messages can contain different values like `1`, `"1"`, ## Configuration To enable this sensor, -add the following lines to your `configuration.yaml` file for a GET request: +add the following lines to your {% term "`configuration.yaml`" %} file for a GET request: ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/blink.markdown b/source/_integrations/blink.markdown index 2963880d50a..55eba3838d2 100644 --- a/source/_integrations/blink.markdown +++ b/source/_integrations/blink.markdown @@ -68,11 +68,11 @@ Trigger a camera to take a new still image. ### `blink.save_video` -Save the last recorded video of a camera to a local file. Note that in most cases, Home Assistant will need to know that the directory is writable via the `allowlist_external_dirs` in your `configuration.yaml` file (see example below). +Save the last recorded video of a camera to a local file. Note that in most cases, Home Assistant will need to know that the directory is writable via the `allowlist_external_dirs` in your {% term "`configuration.yaml`" %} file (see example below). -| Service Data Attribute | Optional | Description | -| ---------------------- | -------- | ---------------------------------------- | -| `filename` | no | Location of save file. | +| Service Data Attribute | Optional | Description | +| ---------------------- | -------- | ---------------------- | +| `filename` | no | Location of save file. | ```yaml homeassistant: @@ -82,11 +82,11 @@ homeassistant: ``` ### `blink.save_recent_clips` -Save the recent video clips of a camera to a local file in the pattern `%Y%m%d_%H%M%S_{name}.mp4`. Note that in most cases, Home Assistant will need to know that the directory is writable via the `allowlist_external_dirs` in your `configuration.yaml` file. +Save the recent video clips of a camera to a local file in the pattern `%Y%m%d_%H%M%S_{name}.mp4`. Note that in most cases, Home Assistant will need to know that the directory is writable via the `allowlist_external_dirs` in your {% term "`configuration.yaml`" %} file. -| Service Data Attribute | Optional | Description | -| ---------------------- | -------- | ---------------------------------------- | -| `file_path` | no | Location of save files. | +| Service Data Attribute | Optional | Description | +| ---------------------- | -------- | ----------------------- | +| `file_path` | no | Location of save files. | ### `blink.send_pin` diff --git a/source/_integrations/bloomsky.markdown b/source/_integrations/bloomsky.markdown index c881df51f85..eb729df7cd9 100644 --- a/source/_integrations/bloomsky.markdown +++ b/source/_integrations/bloomsky.markdown @@ -58,7 +58,7 @@ To get your BloomSky binary sensors working with Home Assistant, follow the inst ### Configuration -To use your BloomSky binary sensor in your installation, add the following to your `configuration.yaml` file: +To use your BloomSky binary sensor in your installation, add the following to your {% term "`configuration.yaml`" %} file. ```yaml # Example configuration.yaml entry @@ -87,7 +87,7 @@ The `bloomsky` camera integration allows you to view the current photo created b ### Configuration -To enable this camera in your installation, set up the BloomSky integration with your API key and add the following to your `configuration.yaml` file: +To enable this camera in your installation, set up the BloomSky integration with your API key and add the following to your {% term "`configuration.yaml`" %} file. ```yaml # Example configuration.yaml entry @@ -101,7 +101,7 @@ The `bloomsky` sensor integration allows you to view the measurements made by se ### Configuration -To enable these sensors in your installation, set up the BloomSky integration with your API key add the following to your `configuration.yaml` file: +To enable these sensors in your installation, set up the BloomSky integration with your API key add the following to your {% term "`configuration.yaml`" %} file. ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/bluetooth.markdown b/source/_integrations/bluetooth.markdown index 56c5a0cdd4b..c30e1914fe0 100644 --- a/source/_integrations/bluetooth.markdown +++ b/source/_integrations/bluetooth.markdown @@ -286,7 +286,7 @@ The connection time and performance vary greatly based on the Bluetooth adapter While newer integrations can share the Bluetooth Adapter, some legacy integrations require exclusive use of the adapter. Enabling this integration may prevent an integration that has not been updated to use newer methods from functioning. -Deleting the config entry for this integration will release control of the adapter and allow another integration to gain exclusive use of the Bluetooth adapter. If you have manually added `bluetooth:` to your `configuration.yaml`, you must also remove it to prevent the configuration from being recreated. Consider adding a second Bluetooth adapter on Linux systems if you need to continue using legacy integrations, as more integrations will move to use the Bluetooth integration in the future. +Deleting the config entry for this integration will release control of the adapter and allow another integration to gain exclusive use of the Bluetooth adapter. If you have manually added `bluetooth:` to your {% term "`configuration.yaml`" %}, you must also remove it to prevent the configuration from being recreated. Consider adding a second Bluetooth adapter on Linux systems if you need to continue using legacy integrations, as more integrations will move to use the Bluetooth integration in the future. ### Bluetooth interference with other devices diff --git a/source/_integrations/broadlink.markdown b/source/_integrations/broadlink.markdown index 85c0a56afea..ffd66c4926f 100644 --- a/source/_integrations/broadlink.markdown +++ b/source/_integrations/broadlink.markdown @@ -353,7 +353,7 @@ You can also define custom IR/RF switches to be controlled with universal remote ### Setting up custom IR/RF switches -The first step is to configure the device normally via the configuration flow. Then add these lines to your `configuration.yaml`: +The first step is to configure the device normally via the configuration flow. Then add these lines to your {% term "`configuration.yaml`" %} file: ```yaml # Example configuration.yaml entry @@ -506,7 +506,7 @@ First get or learn all the remotes you want to add to Home Assistant in e-Contro [+] Dumping codes to TV.txt ``` -6. Now there should be a file with the name of the remote you chose in the same directory ending in `.txt`. Open that up and it will contain the Base64 code required for Home Assistant. To ensure these codes work correctly you may need to add `==` to the end of the code in your `configuration.yaml` file (or wherever you have your switches). +6. Now there should be a file with the name of the remote you chose in the same directory ending in `.txt`. Open that up and it will contain the Base64 code required for Home Assistant. To ensure these codes work correctly you may need to add `==` to the end of the code in your {% term "`configuration.yaml`" %} file (or wherever you have your switches). ### Using Windows to obtain codes with Broadlink Manager diff --git a/source/_integrations/brother.markdown b/source/_integrations/brother.markdown index 90406109240..c33622be83c 100644 --- a/source/_integrations/brother.markdown +++ b/source/_integrations/brother.markdown @@ -40,7 +40,7 @@ For some Brother devices, `SNMPv3 read-write access and v1/v2c read-only access` ## Sensor example -You can configure Home Assistant to alert you when the printer jams or runs out of paper as follows. First, add the following to `configuration.yaml` under the `template:` section (Note: replace `sensor.hl_l2340d_status` with the actual name of your sensor): +You can configure Home Assistant to alert you when the printer jams or runs out of paper as follows. First, add the following to {% term "`configuration.yaml`" %} under the `template:` section (Note: replace `sensor.hl_l2340d_status` with the actual name of your sensor): {% raw %}