diff --git a/source/_integrations/sabnzbd.markdown b/source/_integrations/sabnzbd.markdown index f0309f6101a..1cc6ba6c2cc 100644 --- a/source/_integrations/sabnzbd.markdown +++ b/source/_integrations/sabnzbd.markdown @@ -15,7 +15,7 @@ ha_platforms: ha_integration_type: integration --- -The `sabnzbd` integration will allow you to monitor and control your downloads with [SABnzbd](https://sabnzbd.org) from within Home Assistant and setup automations based on the information. +The SABnzbd integration will allow you to monitor and control your downloads with [SABnzbd](https://sabnzbd.org) from within Home Assistant and setup automations based on the information. ## Prerequisites @@ -29,7 +29,7 @@ You need to grab your API key from your SABnzbd instance in order to configure t ## Sensor -This component will create these sensors: +This integration will create these sensors: - `status`: The current status of SABnzbd. (Idle, Paused, etc.) - `speed`: The current download speed. diff --git a/source/_integrations/satel_integra.markdown b/source/_integrations/satel_integra.markdown index a3eb14af581..4935ea269f0 100644 --- a/source/_integrations/satel_integra.markdown +++ b/source/_integrations/satel_integra.markdown @@ -34,7 +34,7 @@ The library currently doesn't support encrypted connection to your alarm, so you A list of all partition, zone and output IDs can be acquired by running DloadX program and connecting to your alarm. -For the Binary Sensor check the [type/class](/integrations/binary_sensor/) list for a possible visualization of your zones. Note: If no zones or outputs are specified, Home Assistant will not load any binary_sensor components." +For the Binary Sensor, check the [type/class](/integrations/binary_sensor/) list for a possible visualization of your zones. Note: If no zones or outputs are specified, Home Assistant will not load any binary_sensor integrations." ## Configuration diff --git a/source/_integrations/scrape.markdown b/source/_integrations/scrape.markdown index e9569d0d073..1fc50d91491 100644 --- a/source/_integrations/scrape.markdown +++ b/source/_integrations/scrape.markdown @@ -181,7 +181,7 @@ scrape: ### Available implementations -Get the counter for all our implementations from the [Component overview](/integrations/) page. +Get the counter for all our implementations from the integrations page under {% my integrations title="**Settings** > **Devices & Services**" %}. {% raw %} diff --git a/source/_integrations/sensor.markdown b/source/_integrations/sensor.markdown index af4d721bd1f..637cde66f96 100644 --- a/source/_integrations/sensor.markdown +++ b/source/_integrations/sensor.markdown @@ -11,7 +11,7 @@ ha_codeowners: ha_integration_type: entity --- -Sensors are a basic platform component in Home Assistant. They monitor the states and conditions of a variety of entities. An entity can be many things. This can include a physical device like a motion sensor that reports the battery level, a web service that retrieves the weather temperature, a built-in function that calculates the sun's elevation relative to your GPS position, or even a custom sensor you may have created to report the free space on your laptop. These are all _things_ reporting different types of information. +Sensors are a basic integration in Home Assistant. They monitor the states and conditions of a variety of entities. An entity can be many things. This can include a physical device like a motion sensor that reports the battery level, a web service that retrieves the weather temperature, a built-in function that calculates the sun's elevation relative to your GPS position, or even a custom sensor you may have created to report the free space on your laptop. These are all _things_ reporting different types of information. Some of these sensors are built-in to Home Assistant, some are created automatically when you add an integration (see this [list](/integrations/#sensor)), and some can be created manually. The [Statistics](/integrations/statistics) and [Template](/integrations/template) sensors are two examples of the last case. diff --git a/source/_integrations/sentry.markdown b/source/_integrations/sentry.markdown index febe05e1878..c066e1e0d0e 100644 --- a/source/_integrations/sentry.markdown +++ b/source/_integrations/sentry.markdown @@ -15,11 +15,11 @@ ha_integration_type: service
- The free Sentry account allows 5000 events per month. Depending on the amount of events sent to Sentry you will either have to upgrade your Sentry account or have a period without data flowing from Home Assistant to Sentry. + The free Sentry account allows 5000 events per month. Depending on the amount of events sent to Sentry, you will either have to upgrade your Sentry account or have a period without data flowing from Home Assistant to Sentry.
-The `sentry` integration integrates with [Sentry](https://sentry.io/) to capture both logged errors as well as unhandled exceptions in Home Assistant. +The Sentry integration in Home Assistant integrates with [Sentry](https://sentry.io/) to capture both logged errors as well as unhandled exceptions in Home Assistant. ## Preparation @@ -27,11 +27,11 @@ Before configuring the Sentry integration, you'll need to get Sentry account and Follow these steps to get the DSN: -- Go to **Projects**. -- Click **Create project**. -- Fill out **Give your project a name** and **choose Assign a Team** fields and click Create project button. -- Click **Get your DSN** link in top of the page. -- Your DSN is now visible and looks like +1. Go to **Projects**. +1. Select **Create project**. +1. Fill out the **Give your project a name** and **choose Assign a Team** fields and select the **Create project** button. +1. Select the **Get your DSN** link in top of the page. + * Your DSN is now visible and looks like {% include integrations/config_flow.md %} @@ -42,10 +42,10 @@ The Sentry integration provides settings to: - Set an environment name for your instance. - Limit the event log level to trigger on, and the log level of the breadcrumbs. - Ability to send out error events that are handled. -- Ability to send out events caused by custom integrations (custom components). +- Ability to send out events caused by custom integrations. - Ability to send out events originating from third-party Python packages. - Enable performance tracing and tune the tracing sample rate used. -To change the settings go in **Settings** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**. +To change the settings, go to {% my integrations title="**Settings** > **Devices & Services**" %}. On the already installed **Sentry** integration, select the cogwheel and select **Options**. -After changing Sentry settings, you'll need to restart Home Assistant in order to make them effective. +After changing the Sentry settings, you'll need to restart Home Assistant in order to make them effective. diff --git a/source/_integrations/sighthound.markdown b/source/_integrations/sighthound.markdown index e41b84a3890..5b4a776870c 100644 --- a/source/_integrations/sighthound.markdown +++ b/source/_integrations/sighthound.markdown @@ -17,7 +17,7 @@ This integration adds an image processing entity where the state of the entity i If `save_file_folder` is configured, on each new detection of a person, an annotated image with the name `sighthound_{camera_name}_latest.jpg` is saved in the configured folder if it doesn't already exist, and overwritten if it does exist. The saved image shows the bounding box around detected people and can be displayed on the Home Assistant front end using a [Local File](/integrations/local_file/) camera, and used in notifications. If `save_timestamped_file` is configured as `true`, then the annotated image is saved with a file name that includes the time of detection. -**Note** that by default the component will not automatically scan images, but requires you to call the `image_processing.scan` service, e.g., using an automation triggered by motion. +**Note** that by default the integration will not automatically scan images, but requires you to call the `image_processing.scan` service, e.g., using an automation triggered by motion. ## Configuration