From b1ef4996eb83735a9bf444494ecd0f6a4c839ff2 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Wed, 3 Jul 2019 13:48:38 +0200 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20The=20great=20integration?= =?UTF-8?q?=20migration=20-=20part=202=20(#9760)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * :pencil2: The great integration migration - part 2 * :pencil2: Tweak --- source/_addons/snips.markdown | 4 ++-- source/_components/air_quality.markdown | 3 ++- source/_components/alarm_control_panel.ifttt.markdown | 2 +- source/_components/alarmdecoder.markdown | 2 +- source/_components/alert.markdown | 4 ++-- source/_components/alexa.intent.markdown | 2 +- source/_components/alexa.markdown | 2 +- source/_components/alexa.smart_home.markdown | 2 +- source/_components/api.markdown | 2 +- source/_components/asterisk_cdr.markdown | 2 +- source/_components/binary_sensor.knx.markdown | 2 +- source/_components/binary_sensor.markdown | 2 +- source/_components/binary_sensor.xiaomi_aqara.markdown | 2 +- source/_components/blink.markdown | 2 +- source/_components/bme680.markdown | 2 +- source/_components/camera.ffmpeg.markdown | 2 +- source/_components/canary.markdown | 8 ++++---- source/_components/cast.markdown | 6 +++--- source/_components/climate.knx.markdown | 2 +- source/_components/configurator.markdown | 4 ++-- source/_components/conversation.markdown | 2 +- source/_components/cover.knx.markdown | 2 +- source/_components/daikin.markdown | 2 +- source/_components/deconz.markdown | 4 ++-- source/_components/device_sun_light_trigger.markdown | 2 +- source/_components/dialogflow.markdown | 5 +++-- source/_components/directv.markdown | 2 +- source/_components/dlib_face_detect.markdown | 2 +- source/_components/dlib_face_identify.markdown | 2 +- .../_cookbook/automation_telegram_presence_alert.markdown | 2 +- source/_cookbook/dim_lights_when_playing_media.markdown | 2 +- source/_cookbook/python_component_mqtt_basic.markdown | 4 ++-- source/_cookbook/python_component_simple_alarm.markdown | 2 +- source/_docs/authentication.markdown | 3 ++- source/_docs/security.markdown | 2 +- source/_docs/z-wave.markdown | 4 ++-- source/_lovelace/alarm-panel.markdown | 4 ++-- source/cloud/alexa.markdown | 3 ++- source/hassio/installation.markdown | 2 +- source/help/reporting_issues.markdown | 6 +++--- source/help/trivia.markdown | 2 +- source/lovelace/index.markdown | 3 ++- 42 files changed, 62 insertions(+), 57 deletions(-) diff --git a/source/_addons/snips.markdown b/source/_addons/snips.markdown index 90ae974b03c..919e842cdbd 100644 --- a/source/_addons/snips.markdown +++ b/source/_addons/snips.markdown @@ -68,7 +68,7 @@ tts_platform: ### {% linkable_title Home Assistant configuration %} -A simple configuration just requires this. Consult [Snips.ai component](/components/snips/) for more options. +A simple configuration just requires this. Consult [Snips.ai integration](/components/snips/) for more options. ```yaml snips: @@ -98,7 +98,7 @@ Next create a weather sensor, e.g., one for (Dark Sky)[/components/sensor.darksk - temperature_min ``` -Next add this to your `configuration.yaml` file to reference a new `intent_script` component. This is a good practice to [split your configuration files](/docs/configuration/splitting_configuration/) up. +Next add this to your `configuration.yaml` file to reference a new `intent_script` integration. This is a good practice to [split your configuration files](/docs/configuration/splitting_configuration/) up. ```yaml intent_script: !include intent_script.yaml diff --git a/source/_components/air_quality.markdown b/source/_components/air_quality.markdown index 26318e9d27b..3ff556c6f07 100644 --- a/source/_components/air_quality.markdown +++ b/source/_components/air_quality.markdown @@ -7,7 +7,8 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /components/air_pollutants/ +redirect_from: + - /components/air_pollutants/ ha_release: 0.85 --- diff --git a/source/_components/alarm_control_panel.ifttt.markdown b/source/_components/alarm_control_panel.ifttt.markdown index 1cb7ebd51d6..3e7d4ebf81f 100644 --- a/source/_components/alarm_control_panel.ifttt.markdown +++ b/source/_components/alarm_control_panel.ifttt.markdown @@ -15,7 +15,7 @@ ha_release: 0.66 The `ifttt` platform allows you to integrate security systems that have no open API but can be controlled through [IFTTT](https://ifttt.com/discover). -This platform depends on the [IFTTT](/components/ifttt/) Home Assistant component. See the component's documentation to set it up. +This platform depends on the [IFTTT](/components/ifttt/) Home Assistant integration. See the integrations documentation to set it up.

It is important to note that this platform fully relies on IFTTT to receive updates when the security system's state changes. Therefore, this platform shows an assumed state. diff --git a/source/_components/alarmdecoder.markdown b/source/_components/alarmdecoder.markdown index 0bde582eaa7..d9ed822f076 100644 --- a/source/_components/alarmdecoder.markdown +++ b/source/_components/alarmdecoder.markdown @@ -91,7 +91,7 @@ panel_display: default: false type: boolean zones: - description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*" + description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*" required: false type: list keys: diff --git a/source/_components/alert.markdown b/source/_components/alert.markdown index a881dfaa487..6b7eb22d442 100644 --- a/source/_components/alert.markdown +++ b/source/_components/alert.markdown @@ -25,8 +25,8 @@ This entity allows you to silence an alert until it is resolved. ### {% linkable_title Basic Example %} -The `alert` integration makes use of any of the `notifications` components. To -setup the `alert` component, first, you must setup a `notification` component. +The `alert` integration makes use of any of the `notifications` integrations. To +setup the `alert` integration, first, you must setup a `notification` integration. Then, add the following to your configuration file: ```yaml diff --git a/source/_components/alexa.intent.markdown b/source/_components/alexa.intent.markdown index 7c2c9552c4e..925d33f8f53 100644 --- a/source/_components/alexa.intent.markdown +++ b/source/_components/alexa.intent.markdown @@ -90,7 +90,7 @@ This means that we can now ask Alexa things like: ## {% linkable_title Configuring Home Assistant %} -When activated, the Alexa integration will have Home Assistant's native intent support handle the incoming intents. If you want to run actions based on intents, use the [`intent_script`](/components/intent_script) component. +When activated, the Alexa integration will have Home Assistant's native intent support handle the incoming intents. If you want to run actions based on intents, use the [`intent_script`](/components/intent_script) integration. To enable Alexa, add the following entry to your `configuration.yaml` file: diff --git a/source/_components/alexa.markdown b/source/_components/alexa.markdown index f9bf1a3ba92..7a7df1f7a9c 100644 --- a/source/_components/alexa.markdown +++ b/source/_components/alexa.markdown @@ -27,7 +27,7 @@ There are a few ways that you can use Amazon Alexa and Home Assistant together. - [Build custom commands to use](/components/alexa.intent/) - [Create a new Flash Briefing source](/components/alexa.flash_briefings/) - [Use the Smart Home API to control lights, etc](/components/alexa.smart_home/) -- Alternative: use the [Emulated Hue component][emulated-hue-component] to trick Alexa to thinking Home Assistant is a Philips Hue hub. +- Alternative: use the [Emulated Hue integration][emulated-hue-component] to trick Alexa to thinking Home Assistant is a Philips Hue hub. ### {% linkable_title Requirements %} diff --git a/source/_components/alexa.smart_home.markdown b/source/_components/alexa.smart_home.markdown index 6aa184a6010..d5f3e819b07 100644 --- a/source/_components/alexa.smart_home.markdown +++ b/source/_components/alexa.smart_home.markdown @@ -19,7 +19,7 @@ ha_release: "0.54" While the Skills API described above allows for arbitrary intents, all utterances must begin with "Alexa, tell $invocation_name ..." -The [Emulated Hue component][emulated-hue-component] provides a simpler +The [Emulated Hue integration][emulated-hue-component] provides a simpler interface such as, "Alexa, turn on the kitchen light". However, it has some limitations since everything looks like a light bulb. diff --git a/source/_components/api.markdown b/source/_components/api.markdown index 8f6415bbe0b..151530947b7 100644 --- a/source/_components/api.markdown +++ b/source/_components/api.markdown @@ -14,7 +14,7 @@ ha_qa_scale: internal ha_release: 0.7 --- -The `api` integration exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This integration depends on the [`http` component](/components/http/). +The `api` integration exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This integration depends on the [`http` integration](/components/http/).

It is HIGHLY recommended that you set the `api_password`, especially if you are planning to expose your installation to the internet. diff --git a/source/_components/asterisk_cdr.markdown b/source/_components/asterisk_cdr.markdown index 59c27d946dd..4cc68d5d505 100644 --- a/source/_components/asterisk_cdr.markdown +++ b/source/_components/asterisk_cdr.markdown @@ -15,4 +15,4 @@ redirect_from: - /components/mailbox.asterisk_cdr/ --- -The Asterisk Call Data Recorder provides access to Asterisk call logs on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail component](/components/asterisk_mbox/) configuration if the `asterisk_mbox_server` is configured to provide CDR data. More information on configuring the server can be found in the [Asterisk PBX configuration guide](/docs/asterisk_mbox/). +The Asterisk Call Data Recorder provides access to Asterisk call logs on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail integration](/components/asterisk_mbox/) configuration if the `asterisk_mbox_server` is configured to provide CDR data. More information on configuring the server can be found in the [Asterisk PBX configuration guide](/docs/asterisk_mbox/). diff --git a/source/_components/binary_sensor.knx.markdown b/source/_components/binary_sensor.knx.markdown index 6e5f40cde95..b89ee64f261 100644 --- a/source/_components/binary_sensor.knx.markdown +++ b/source/_components/binary_sensor.knx.markdown @@ -18,7 +18,7 @@ The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) binary ## {% linkable_title Configuration %} -The `knx` integration must be configured correctly, see [KNX Component](/components/knx). +The `knx` integration must be configured correctly, see [KNX Integration](/components/knx). ```yaml # Example configuration.yaml entry diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown index 2d83527eed8..7b93b7dc757 100644 --- a/source/_components/binary_sensor.markdown +++ b/source/_components/binary_sensor.markdown @@ -45,7 +45,7 @@ The way these sensors are displayed in the frontend can be modified in the [cust - **vibration**: `On` means vibration detected, `Off` means no vibration (clear) - **window**: `On` means open, `Off` means closed -For analog sensors please check the [component overview](/components/#sensor). +For analog sensors please check the [integration overview](/components/#sensor).

diff --git a/source/_components/binary_sensor.xiaomi_aqara.markdown b/source/_components/binary_sensor.xiaomi_aqara.markdown index e6a955d4004..4aae23f5a9c 100644 --- a/source/_components/binary_sensor.xiaomi_aqara.markdown +++ b/source/_components/binary_sensor.xiaomi_aqara.markdown @@ -16,7 +16,7 @@ ha_iot_class: Local Push The `xiaomi aqara` binary sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) binary sensors. -The requirement is that you have setup the [`xiaomi aqara` component](/components/xiaomi_aqara/). +The requirement is that you have setup the [`xiaomi aqara` integration](/components/xiaomi_aqara/). ### {% linkable_title Type of sensors supported %} diff --git a/source/_components/blink.markdown b/source/_components/blink.markdown index 72f1dc651ab..aa87420e647 100644 --- a/source/_components/blink.markdown +++ b/source/_components/blink.markdown @@ -160,7 +160,7 @@ The following are some examples showing how to correctly make service calls usin ### {% linkable_title Snap Picture and Save Locally %} -This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in home-assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera component](https://www.home-assistant.io/components/camera#service-snapshot) +This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in home-assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera integration](https://www.home-assistant.io/components/camera#service-snapshot) ```yaml alias: Blink Snap Picture diff --git a/source/_components/bme680.markdown b/source/_components/bme680.markdown index ada45594307..a2cd6ce52a1 100644 --- a/source/_components/bme680.markdown +++ b/source/_components/bme680.markdown @@ -114,7 +114,7 @@ aq_humidity_bias: default: 25 type: integer temp_offset: - description: "The temperature for the sensor will always be too high as it pulls heat from the components around it. Consider adding a negative offset to ensure the sensor returns an accurate temperature. Note: This value is in celsius." + description: "The temperature for the sensor will always be too high as it pulls heat from the components around it. Consider adding a negative offset to ensure the sensor returns an accurate temperature. Note: This value is in celsius." required: false default: 0 type: float diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index f47dcef0de6..57e93d7d9f3 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -18,7 +18,7 @@ The `ffmpeg` platform allows you to use any video feed as a camera in Home Assis ## {% linkable_title Configuration %} -To enable your FFmpeg feed in your installation you must first configure the [ffmpeg component](/components/ffmpeg/), then add the following to your `configuration.yaml` file: +To enable your FFmpeg feed in your installation you must first configure the [ffmpeg integration](/components/ffmpeg/), then add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_components/canary.markdown b/source/_components/canary.markdown index 2ead4902559..c115703c1e5 100644 --- a/source/_components/canary.markdown +++ b/source/_components/canary.markdown @@ -57,7 +57,7 @@ timeout: default: 10 {% endconfiguration %} -Once loaded, your front end will have the following components: +Once loaded, your front end will have the following integrations: - A camera image triggered by motion for each camera. - An alarm control panel for each location. @@ -67,9 +67,9 @@ Once loaded, your front end will have the following components: ## {% linkable_title Camera %} -The `canary` camera platform allows you to watch the live stream of your [Canary](https://canary.is) camera in Home Assistant. This requires the [`ffmpeg` component](/components/ffmpeg/) to be already configured. +The `canary` camera platform allows you to watch the live stream of your [Canary](https://canary.is) camera in Home Assistant. This requires the [`ffmpeg` integration](/components/ffmpeg/) to be already configured. -Once you have [Canary component](/components/canary/) setup, your [Canary](https://canary.is) camera(s) should show up automatically. +Once you have [Canary integration](/components/canary/) setup, your [Canary](https://canary.is) camera(s) should show up automatically. ## {% linkable_title Configuration %} @@ -82,7 +82,7 @@ camera: {% configuration %} ffmpeg_arguments: - description: Extra options to pass to `ffmpeg`, e.g., image quality or video filter options. More details in [FFmpeg component](/components/ffmpeg). + description: Extra options to pass to `ffmpeg`, e.g., image quality or video filter options. More details in [FFmpeg integration](/components/ffmpeg). required: false type: string {% endconfiguration %} diff --git a/source/_components/cast.markdown b/source/_components/cast.markdown index 8fac5fb601c..09529e9567b 100644 --- a/source/_components/cast.markdown +++ b/source/_components/cast.markdown @@ -17,15 +17,15 @@ redirect_from: /components/media_player.cast/ --- Google Cast devices like Android TVs and Chromecasts will be automatically -discovered if you enable [the discovery component](/components/discovery/). If +discovered if you enable [the discovery integration(/components/discovery/). If you don't have the discovery integration enabled, you can enable the Cast -component by going to the Integrations page inside the config panel. +integration by going to the Integrations page inside the config panel. ## {% linkable_title Advanced use %} The Cast integration has some extra configuration options available for advanced users. You will still need to create a config entry to initialize the Cast -component. +integration. For example, Cast devices can only be discovered if they are on the same subnet as Home Assistant. If this is not the case, diff --git a/source/_components/climate.knx.markdown b/source/_components/climate.knx.markdown index f7f7ba2063d..b37c5ab075c 100644 --- a/source/_components/climate.knx.markdown +++ b/source/_components/climate.knx.markdown @@ -16,7 +16,7 @@ ha_iot_class: Local Polling The `knx` climate platform is used as in interface with KNX thermostats. -The `knx` integration must be configured correctly, see [KNX Component](/components/knx). +The `knx` integration must be configured correctly, see [KNX Integration](/components/knx). To use your KNX thermostats in your installation, add the following lines to your `configuration.yaml` file: diff --git a/source/_components/configurator.markdown b/source/_components/configurator.markdown index cba5fe0f76f..296c74560e6 100644 --- a/source/_components/configurator.markdown +++ b/source/_components/configurator.markdown @@ -24,6 +24,6 @@ The configurator integration allows integrations to request information from the - Input fields can be defined with a description, and optional type - It will trigger a callback when the button is pressed -The Hue integration in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo component](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/demo) for a simple example. +The Hue integration in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo integration](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/demo) for a simple example. -See [the source](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/configurator) for more details on how to use the configurator component. +See [the source](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/configurator) for more details on how to use the configurator integration. diff --git a/source/_components/conversation.markdown b/source/_components/conversation.markdown index 48817f6d338..4aae2f49683 100644 --- a/source/_components/conversation.markdown +++ b/source/_components/conversation.markdown @@ -40,7 +40,7 @@ intents: ## {% linkable_title Adding custom sentences %} -By default, it will support turning devices on and off. You can say things like "turn on kitchen lights" or "turn the living room lights off". You can also configure your own sentences to be processed. This works by mapping sentences to intents and then configure the [intent script component](/components/intent_script/) to handle these intents. +By default, it will support turning devices on and off. You can say things like "turn on kitchen lights" or "turn the living room lights off". You can also configure your own sentences to be processed. This works by mapping sentences to intents and then configure the [intent script integration](/components/intent_script/) to handle these intents. Here is a simple example to be able to ask what the temperature in the living room is. diff --git a/source/_components/cover.knx.markdown b/source/_components/cover.knx.markdown index 0c93ae37070..606845df77c 100644 --- a/source/_components/cover.knx.markdown +++ b/source/_components/cover.knx.markdown @@ -17,7 +17,7 @@ ha_iot_class: Local Polling The `knx` cover platform is used as in interface with KNX covers. -The `knx` integration must be configured correctly, see [KNX Component](/components/knx). +The `knx` integration must be configured correctly, see [KNX Integration](/components/knx). To use your KNX covers in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/daikin.markdown b/source/_components/daikin.markdown index 4da14c4ff84..110c245418f 100644 --- a/source/_components/daikin.markdown +++ b/source/_components/daikin.markdown @@ -38,7 +38,7 @@ There is currently support for the following device types within Home Assistant: The Daikin integration can be configured in three ways. -- Automatically via the [discovery]({{site_root}}/components/discovery/) component. +- Automatically via the [discovery]({{site_root}}/components/discovery/) integration. - Via the Home Assistant user interface where it will let you enter the IP-address of your Daikin AC. - Or via the `configuration.yaml` file by adding the following: diff --git a/source/_components/deconz.markdown b/source/_components/deconz.markdown index e03c60279e6..faa9093bc22 100644 --- a/source/_components/deconz.markdown +++ b/source/_components/deconz.markdown @@ -329,7 +329,7 @@ The `entity_id` name will be `binary_sensor.device_name`, where `device_name` is ## {% linkable_title Climate %} -See the [deCONZ main component](/components/deconz/) for configuration instructions. +See the [deCONZ main integration](/components/deconz/) for configuration instructions. Climate currently represent thermostats. @@ -386,7 +386,7 @@ The following sensor types are supported: - Switches - Temperature sensor -The `entity_id` name will be `sensor.device_name`, where `device_name` is defined in deCONZ. Switches aren't exposed as ordinary entities, see the [deCONZ main component](/components/deconz/) for more details. +The `entity_id` name will be `sensor.device_name`, where `device_name` is defined in deCONZ. Switches aren't exposed as ordinary entities, see the [deCONZ main integration](/components/deconz/) for more details. ### {% linkable_title Verified to be supported sensors %} diff --git a/source/_components/device_sun_light_trigger.markdown b/source/_components/device_sun_light_trigger.markdown index d2e4a7724a7..9c4c011aab1 100644 --- a/source/_components/device_sun_light_trigger.markdown +++ b/source/_components/device_sun_light_trigger.markdown @@ -22,7 +22,7 @@ Home Assistant has a built-in integration called `device_sun_light_trigger` to h This integration requires the integrations [sun](/components/sun/), [device_tracker](/components/device_tracker/) and [light](/components/light/) to be enabled. -To enable this component, add the following lines to your `configuration.yaml` file: +To enable this integration, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_components/dialogflow.markdown b/source/_components/dialogflow.markdown index 658f2002e9c..1126bd5d99f 100644 --- a/source/_components/dialogflow.markdown +++ b/source/_components/dialogflow.markdown @@ -11,7 +11,8 @@ logo: dialogflow.png ha_category: - Voice ha_release: 0.56 -redirect_from: /components/apiai/ +redirect_from: + - /components/apiai/ --- The `dialogflow` integration is designed to be used with the [webhook](https://dialogflow.com/docs/fulfillment#webhook) integration of [Dialogflow](https://dialogflow.com/). When a conversation ends with a user, Dialogflow sends an action and parameters to the webhook. @@ -62,7 +63,7 @@ Take a look to "Integrations", in the left menu, to configure third parties. ### {% linkable_title Configuring Home Assistant %} -When activated, the [`alexa` component](/components/alexa/) will have Home Assistant's native intent support handle the incoming intents. If you want to run actions based on intents, use the [`intent_script`](/components/intent_script) component. +When activated, the [`alexa` integration](/components/alexa/) will have Home Assistant's native intent support handle the incoming intents. If you want to run actions based on intents, use the [`intent_script`](/components/intent_script) integration. ## {% linkable_title Examples %} diff --git a/source/_components/directv.markdown b/source/_components/directv.markdown index 97d6cc9b61c..a13e1adadc7 100644 --- a/source/_components/directv.markdown +++ b/source/_components/directv.markdown @@ -16,7 +16,7 @@ redirect_from: - /components/media_player.directv/ --- -Master [DirecTV](http://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery component](/components/discovery/) and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery. +Master [DirecTV](http://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery integration](/components/discovery/) and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery. To ensure that your DirecTV boxes are always found and configured, they should be added into your `configuration.yaml`. diff --git a/source/_components/dlib_face_detect.markdown b/source/_components/dlib_face_detect.markdown index 5ba7c2ca0d9..273bd3240f1 100644 --- a/source/_components/dlib_face_detect.markdown +++ b/source/_components/dlib_face_detect.markdown @@ -17,7 +17,7 @@ redirect_from: The `dlib_face_detect` image processing platform allows you to use the [Dlib](http://www.dlib.net/) through Home Assistant. This platform enables face detection from cameras, and can fire events with attributes. -This can be used to trigger an automation rule. Further info is on the [component](/components/image_processing/) page. +This can be used to trigger an automation rule. Further info is on the [integration](/components/image_processing/) page. ### {% linkable_title Configuration Home Assistant %} diff --git a/source/_components/dlib_face_identify.markdown b/source/_components/dlib_face_identify.markdown index 3efb0ac8179..186b9f81242 100644 --- a/source/_components/dlib_face_identify.markdown +++ b/source/_components/dlib_face_identify.markdown @@ -17,7 +17,7 @@ redirect_from: The `dlib_face_identify` image processing platform allows you to use the [Dlib](http://www.dlib.net/) through Home Assistant. This platform allow you to identify persons on camera and fire an event with identify persons. -For using the result inside an automation rule, take a look at the [component](/components/image_processing/) page. +For using the result inside an automation rule, take a look at the [integration](/components/image_processing/) page. ### {% linkable_title Configuration Home Assistant %} diff --git a/source/_cookbook/automation_telegram_presence_alert.markdown b/source/_cookbook/automation_telegram_presence_alert.markdown index d701f0cdc4f..0dcb5aacdbf 100644 --- a/source/_cookbook/automation_telegram_presence_alert.markdown +++ b/source/_cookbook/automation_telegram_presence_alert.markdown @@ -10,7 +10,7 @@ footer: true ha_category: Automation Examples --- -This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [Nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar component. +This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [Nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar integration. This example uses [Telegram](/components/notify.telegram/) to send the notification. diff --git a/source/_cookbook/dim_lights_when_playing_media.markdown b/source/_cookbook/dim_lights_when_playing_media.markdown index a53c90d9f0a..e5e6b883524 100644 --- a/source/_cookbook/dim_lights_when_playing_media.markdown +++ b/source/_cookbook/dim_lights_when_playing_media.markdown @@ -12,7 +12,7 @@ ha_category: Automation Examples Like it how the lights dim up/down at the movies? Do it at home as well! -This example uses the [media player](/components/media_player/), [lights](/components/light/) (transitions) and the [sun](/components/sun/) component. We'll use actions to detect media player state changes and [scenes](/components/scene/) to control multiple lights and transition between scenes. +This example uses the [media player](/components/media_player/), [lights](/components/light/) (transitions) and the [sun](/components/sun/) integration. We'll use actions to detect media player state changes and [scenes](/components/scene/) to control multiple lights and transition between scenes. #### {% linkable_title Scenes %} One scene for normal light, one for when movies are on. A 2 second transition gives a nice 'feel' to the switch. diff --git a/source/_cookbook/python_component_mqtt_basic.markdown b/source/_cookbook/python_component_mqtt_basic.markdown index c7e09c8ee25..a5508d129d8 100644 --- a/source/_cookbook/python_component_mqtt_basic.markdown +++ b/source/_cookbook/python_component_mqtt_basic.markdown @@ -11,10 +11,10 @@ ha_category: Custom Python Component Examples ---

-This example requires you to have the [MQTT component](/components/mqtt/) up and running. +This example requires you to have the [MQTT integration](/components/mqtt/) up and running.

-This is a simple hello world example to show the basics of using MQTT in a custom component. To use this example, create the file `/custom_components/hello_mqtt.py` and copy the below example code. +This is a simple hello world example to show the basics of using MQTT in a custom integration. To use this example, create the file `/custom_components/hello_mqtt.py` and copy the below example code. This example follows a topic on MQTT and updates the state of an entity to the last message received on that topic. It will also register a service 'set_state' that will publish a message to the MQTT topic that we're listening to. diff --git a/source/_cookbook/python_component_simple_alarm.markdown b/source/_cookbook/python_component_simple_alarm.markdown index 80ae163161b..63c5bdf05d8 100644 --- a/source/_cookbook/python_component_simple_alarm.markdown +++ b/source/_cookbook/python_component_simple_alarm.markdown @@ -10,7 +10,7 @@ footer: true ha_category: Automation in Python Examples --- -This example integration will detect intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via [the notify component](/components/notify/). It will also flash a specific light when a known person comes home. +This example integration will detect intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via [the notify integration](/components/notify/). It will also flash a specific light when a known person comes home. This integration depends on the integrations [device_tracker](/components/device_tracker/) and [light](/components/light/) being setup. diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index 084846798c5..8de0f3e1dc3 100644 --- a/source/_docs/authentication.markdown +++ b/source/_docs/authentication.markdown @@ -3,7 +3,8 @@ layout: page title: "Authentication" description: "Guide on authentication in Home Assistant." date: 2018-08-23 09:40 -redirect_from: /components/auth/ +redirect_from: + - /components/auth/ sidebar: true comments: false sharing: true diff --git a/source/_docs/security.markdown b/source/_docs/security.markdown index db321bb51fb..132f3435443 100644 --- a/source/_docs/security.markdown +++ b/source/_docs/security.markdown @@ -27,7 +27,7 @@ See the [open ports](/docs/security/porosity/) of a Hass.io instance with variou ## {% linkable_title HTTP SSL/TLS %} -Home Assistant is following the [Mozilla's Operations Security team recommendations](https://wiki.mozilla.org/Security/Server_Side_TLS) for Server side SSL/TLS settings. Home Assistant uses **Modern compatibility** by default. If an user wishes to use **Intermediate compatibilty**, this is configurable in the [`http` component](/components/http/). +Home Assistant is following the [Mozilla's Operations Security team recommendations](https://wiki.mozilla.org/Security/Server_Side_TLS) for Server side SSL/TLS settings. Home Assistant uses **Modern compatibility** by default. If an user wishes to use **Intermediate compatibilty**, this is configurable in the [`http` integration](/components/http/). ## {% linkable_title SSH %} diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown index caf4e3ad221..ebc7948e510 100644 --- a/source/_docs/z-wave.markdown +++ b/source/_docs/z-wave.markdown @@ -20,7 +20,7 @@ Before configuring the Z-Wave setup, please take a moment and read [this article Z-Wave is a wireless communication protocol designed for home automation. It uses a low power, and low bandwidth, mesh network that allows devices that aren't within direct range of each other to communicate indirectly, via other nodes. Any device that's permanently powered (not battery powered) will help build the mesh, if you don't have enough powered devices, or you locate these poorly, your mesh will be unreliable. You can [view the state](https://community.home-assistant.io/t/graph-your-z-wave-mesh-python-auto-update/40549) of your mesh [by graphing it](https://community.home-assistant.io/t/z-wave-graph-without-the-python/64275). -There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components. There is also a limit of 4 hops for Z-Wave, so placing the controller as centrally as you can is important. +There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) integrations. There is also a limit of 4 hops for Z-Wave, so placing the controller as centrally as you can is important. The Z-Wave standard was improved with Z-Wave Plus, and if you only use Z-Wave plus devices then you will gain the full benefits. @@ -34,7 +34,7 @@ There are 12 different regions for Z-Wave devices, which relates to the frequenc ## {% linkable_title Getting started %} -You'll now need to connect your [controller](/docs/z-wave/controllers/), [configure](/docs/z-wave/installation) the Z-Wave component, then [add some devices](/docs/z-wave/adding) using the [control panel](/docs/z-wave/control-panel). [This explains](/docs/z-wave/devices/) about devices, and how [entities are named](/docs/z-wave/entities). +You'll now need to connect your [controller](/docs/z-wave/controllers/), [configure](/docs/z-wave/installation) the Z-Wave integration, then [add some devices](/docs/z-wave/adding) using the [control panel](/docs/z-wave/control-panel). [This explains](/docs/z-wave/devices/) about devices, and how [entities are named](/docs/z-wave/entities). You can get more information on the [available services](/docs/z-wave/services/) and [events](/docs/z-wave/events/), what the [query stages](/docs/z-wave/query-stage) of battery powered devices are, as well as details on configuring [specific devices](/docs/z-wave/device-specific/). diff --git a/source/_lovelace/alarm-panel.markdown b/source/_lovelace/alarm-panel.markdown index 103df57a77a..f3d9f8de0d7 100644 --- a/source/_lovelace/alarm-panel.markdown +++ b/source/_lovelace/alarm-panel.markdown @@ -2,7 +2,7 @@ layout: page title: "Alarm Panel Card" sidebar_label: Alarm Panel -description: "The Alarm Panel allows you to Arm and Disarm your Alarm Control Panel Components" +description: "The Alarm Panel allows you to Arm and Disarm your Alarm Control Panel Integrations" date: 2018-10-15 10:28 +00:00 sidebar: true comments: false @@ -10,7 +10,7 @@ sharing: true footer: true --- -The Alarm Panel allows you to Arm and Disarm your Alarm Control Panel Components. +The Alarm Panel allows you to Arm and Disarm your Alarm Control Panel Integrations.

Screenshot of the alarm panel card diff --git a/source/cloud/alexa.markdown b/source/cloud/alexa.markdown index 148e8cfe2d0..f09fe535993 100644 --- a/source/cloud/alexa.markdown +++ b/source/cloud/alexa.markdown @@ -7,7 +7,8 @@ sidebar: false comments: false sharing: true footer: true -redirect_from: /components/cloud.alexa/ +redirect_from: + - /components/cloud.alexa/ --- Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [the Nabu Casa website](https://www.nabucasa.com/config/amazon_alexa/) for help with the Amazon Alexa integration via Home Assistant Cloud. diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 8c90ce1f509..c1b92029b25 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -116,7 +116,7 @@ The packages you need to have available on your system that will run Hass.io may - software-properties-common

- The `modemmanager` package will interfere with any Z-Wave or Zigbee stick and should be removed or disabled. Failure to do so will result in random failures of those components. For example you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager` + The `modemmanager` package will interfere with any Z-Wave or Zigbee stick and should be removed or disabled. Failure to do so will result in random failures of those integrations. For example you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager`

### {% linkable_title Arch Linux %} diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown index 25a3b321f3b..6ea2cf377fd 100644 --- a/source/help/reporting_issues.markdown +++ b/source/help/reporting_issues.markdown @@ -33,12 +33,12 @@ If possible, provide the latest release of which you know that the integration o There are many different ways to run Home Assistant. In this section please mention which you are using, e.g., manual installation, [Hass.io](/hassio/), Hasbian or as container (Docker). It can help if you mention which operating system you are using because not all are supported on the same level. -### {% linkable_title Component/platform %} +### {% linkable_title Integration/platform %} -Please add the link to the documention of the component/platform in question. E.g., +Please add the link to the documention of the integration/platform in question. E.g., - issue with the `random` sensor: [/components/sensor.random/](/components/sensor.random/) -- issue with the `hue` component: [/components/hue/](/components/hue/) +- issue with the `hue` integration: [/components/hue/](/components/hue/) ### {% linkable_title Description of problem %} diff --git a/source/help/trivia.markdown b/source/help/trivia.markdown index f4a91f4a664..4ecf61372c5 100644 --- a/source/help/trivia.markdown +++ b/source/help/trivia.markdown @@ -17,7 +17,7 @@ Isn't it obvious? Home Assistant is the good soul that is assisting you in your ### {% linkable_title Website %} -The website [https://www.home-assistant.io](/) was launched on December 18, 2014 and contains documentation about the setup process, the platforms and components, and for the developers. +The website [https://www.home-assistant.io](/) was launched on December 18, 2014 and contains documentation about the setup process, the platforms and integrations, and for the developers. ### {% linkable_title Logo %} diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index 20364d518e3..acc9240c39b 100644 --- a/source/lovelace/index.markdown +++ b/source/lovelace/index.markdown @@ -7,7 +7,8 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /components/lovelace/ +redirect_from: + - /components/lovelace/ --- Lovelace is the name of the Home Assistant user interface. It is a fast, customizable and powerful way for users to manage their homes, working both on mobile and desktop.