Merge branch 'current' into next

_config.yml

@@ -63,7 +63,7 @@ titlecase: true # Converts page and post titles to titlecase
 # page_asides:
 
 collections:
-  components:
+  integrations:
     output: true
   cookbook:
     output: true

source/_addons/google_assistant.markdown

@@ -12,7 +12,7 @@ These instructions are outdated - the add-on has been updated and these are no l
 
 <div class='note'>
 
-If you want to integrate your Google Home or mobile phone running Google Assistant, with Home Assistant, then you want the [Google Assistant component](/components/google_assistant/).
+If you want to integrate your Google Home or mobile phone running Google Assistant, with Home Assistant, then you want the [Google Assistant component](/integrations/google_assistant/).
 
 </div>
 
@@ -84,7 +84,7 @@ Use the Home Assistant [DialogFlow component][comp] to integrate the add-on into
 [GoogleAssistant]: https://assistant.google.com/
 [GoogleActions]: https://actions.google.com/
 [Samba]: /addons/samba/
-[comp]: /components/dialogflow/
+[comp]: /integrations/dialogflow/
 [project]: https://console.cloud.google.com/project
 [API]: https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview
 [oauthclient]: https://console.developers.google.com/apis/credentials/oauthclient

source/_addons/snips.markdown

@@ -13,7 +13,7 @@ The Snips add-on depends on the Mosquitto add on to bridge to Home Assistant, so
 
 Home Assistant comes with certain Intents builtin to handle common tasks. A complete list of Intents can be found in this wiki [Hass Snips Bundle](https://github.com/tschmidty69/hass-snips-bundle-intents/wiki).
 
-The Snips add-on by default comes with an assistant that allows you to turn on lights or switches, open covers, or add and list items to a [Shopping List](/components/shopping_list/) if that integration is enabled.
+The Snips add-on by default comes with an assistant that allows you to turn on lights or switches, open covers, or add and list items to a [Shopping List](/integrations/shopping_list/) if that integration is enabled.
 
 If using a USB microphone and speakers plugged into the Raspberry Pi output, Snips will work without any change to the configuration. Trying saying things like:
 
@@ -65,7 +65,7 @@ tts_platform:
 
 ### Home Assistant configuration
 
-A simple configuration just requires this. Consult [Snips.ai integration](/components/snips/) for more options.
+A simple configuration just requires this. Consult [Snips.ai integration](/integrations/snips/) for more options.
 
 ```yaml
 snips:
@@ -79,7 +79,7 @@ There is an active [discord](https://discordapp.com/invite/3939Kqx) channel and
 
 So now you can turn lights on and off, let's check the weather. Log on to the [console](https://console.snips.ai/). If this is your first time, create a new assistant and add the Home Assistant skill, along with the Weather skill by snips. Download your assistant manually and copy it to the `/share` folder on your HassIO installation using the Samba add-on.
 
-Next create a weather sensor, e.g., one for [Dark Sky](/components/darksky/), and put the `api_key` in your `secrets.yaml` file. For this example to work you will need to have a valid API key from [Dark Sky](https://darksky.net/dev).
+Next create a weather sensor, e.g., one for [Dark Sky](/integrations/darksky/), and put the `api_key` in your `secrets.yaml` file. For this example to work you will need to have a valid API key from [Dark Sky](https://darksky.net/dev).
 
 ```yaml
 - platform: darksky

source/_addons/tellstick.markdown

@@ -19,7 +19,7 @@ tellstick:
     port: [50800, 50801]
 ```
 
-To add [lights](/components/tellstick#light), [sensors](/components/tellstick#sensor) and [switches](/components/tellstick#switch) you follow the guidelines for each type individually that is [described for Home Assistant](/components/tellstick/)
+To add [lights](/integrations/tellstick#light), [sensors](/integrations/tellstick#sensor) and [switches](/integrations/tellstick#switch) you follow the guidelines for each type individually that is [described for Home Assistant](/integrations/tellstick/)
 
 The add-on will also enable you to interact with the `tdtool` via a Home Assistant services call, see example below for self-learning device.
 

source/_components/demo.markdown

@@ -1,50 +0,0 @@
----
-title: "Demo platforms"
-description: "Instructions on how to use the Platform demos with Home Assistant."
-logo: home-assistant.png
-ha_category:
-  - Other
-ha_qa_scale: internal
-ha_release: 0.7
----
-
-
-The `demo` platform allows you to use integrations which are providing a demo of their implementation. The demo entities are dummies but show you how the actual platform looks like. This way you can run own demonstration instance like the online [Home Assistant demo](/demo/) or `hass --demo-mode` but combined with your own real/functional platforms.
-
-Available demo platforms:
-
-- [Air Quality](/components/air_quality/) (`air_quality`)
-- [Alarm control panel](/components/alarm_control_panel/) (`alarm_control_panel`)
-- [Binary sensor](/components/binary_sensor/) (`binary_sensor`)
-- [Camera](/components/camera/) (`camera`)
-- [Climate](/components/climate/) (`climate`)
-- [Cover](/components/cover/) (`cover`)
-- [Fan](/components/fan/) (`fan`)
-- [Geolocation](/components/geo_location/) (`geo_location`)
-- [Image Processing](/components/image_processing/) (`image_processing`)
-- [Light](/components/light/) (`light`)
-- [Lock](/components/lock/) (`lock`)
-- [Mailbox](/components/mailbox/) (`mailbox`)
-- [Media Player](/components/media_player/) (`media_player`)
-- [Notification](/components/notify/) (`notify`)
-- [Remote](/components/remote/) (`remote`)
-- [Sensor](/components/sensor/) (`sensor`)
-- [Switch](/components/switch/) (`switch`)
-- [Text-to-speech](/components/tts/) (`tts`)
-- [Weather](/components/weather/) (`weather`)
-
-
-To integrate a demo platform in Home Assistant, add the following section to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-[component]:
-  - platform: demo
-```
-
-{% configuration %}
-"[component]":
-  description: The name of the integration as stated in the listing above the configuration example.
-  required: true
-  type: string
-{% endconfiguration %}

source/_cookbook/automation_for_rainy_days.markdown

@@ -4,7 +4,7 @@ description: "Basic example how to use weather conditions to set states"
 ha_category: Automation Examples
 ---
 
-This requires a [Dark Sky](/components/darksky) sensor with the condition `precip_intensity` that tells if it's raining or not. You could also experiment with other attributes such as `cloud_cover`.
+This requires a [Dark Sky](/integrations/darksky) sensor with the condition `precip_intensity` that tells if it's raining or not. You could also experiment with other attributes such as `cloud_cover`.
 
 Turn on a light in the living room when it starts raining, someone is home, and it's afternoon or later.
 

source/_cookbook/automation_sun.markdown

@@ -40,7 +40,7 @@ automation:
 
 #### Send sun rise/sun set notifications
 
-Send notifications through [PushBullet](/components/pushbullet) when the sun state is changed.
+Send notifications through [PushBullet](/integrations/pushbullet) when the sun state is changed.
 
 ```yaml
 automation:

source/_cookbook/automation_telegram_presence_alert.markdown

@@ -4,9 +4,9 @@ description: "Examples sending notification depending of the presence"
 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/nmap_tracker) device tracker or a similar integration.
+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](/integrations/nmap_tracker) device tracker or a similar integration.
 
-This example uses [Telegram](/components/telegram) to send the notification.
+This example uses [Telegram](/integrations/telegram) to send the notification.
 
 ```yaml
 notify:

source/_cookbook/dim_and_brighten_lights.markdown

@@ -72,7 +72,7 @@ automation:
 
 There are 2 variables that control the speed of the change for the scripts below. The first is the `step`, small steps create a smooth transition. The second is the delay, larger delays will create a slower transition.
 
-To allow flexibility, an [Input Number](/components/input_number/) is used for the step (at the time of writing this, it's not possible to template the delay when the delay uses milliseconds). Two additional [Input Numbers](/components/input_number/) are used to set the minimum and maximum brightness, so that it's easy to tune that (or manage it through an automation).
+To allow flexibility, an [Input Number](/integrations/input_number/) is used for the step (at the time of writing this, it's not possible to template the delay when the delay uses milliseconds). Two additional [Input Numbers](/integrations/input_number/) are used to set the minimum and maximum brightness, so that it's easy to tune that (or manage it through an automation).
 
 ```yaml
 input_number:

source/_cookbook/dim_lights_when_playing_media.markdown

@@ -6,7 +6,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/) integration. 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](/integrations/media_player/), [lights](/integrations/light/) (transitions) and the [sun](/integrations/sun/) integration. We'll use actions to detect media player state changes and [scenes](/integrations/scene/) to control multiple lights and transition between scenes.
 
 #### Scenes
 One scene for normal light, one for when movies are on. A 2 second transition gives a nice 'feel' to the switch.

source/_cookbook/foscam_away_mode_PTZ.markdown

@@ -4,7 +4,7 @@ description: "Example of how to set Foscam to only have Motion Detection Recordi
 ha_category: Automation Examples
 ---
 
-This requires a [Foscam IP Camera](/components/foscam) camera with PTZ (Pan, Tilt, Zoom) and CGI functionality ([Source](http://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf)) 
+This requires a [Foscam IP Camera](/integrations/foscam) camera with PTZ (Pan, Tilt, Zoom) and CGI functionality ([Source](http://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf)) 
 
 Foscam Cameras can be controlled by Home Assistant through a number of CGI commands. 
 The following outlines examples of the switch, services, and scripts required to move between 2 preset destinations while controlling motion detection, but many other options of movement are provided in the Foscam CGI User Guide linked above.

source/_cookbook/google_maps_card.markdown

@@ -21,7 +21,7 @@ camera:
 ```
 
 <p class='img'>
-  <img src='/images/components/camera/generic-google-maps.png' alt='Screenshot showing Google Maps integration in Home Assistant front end.'>
+  <img src='/images/integrations/camera/generic-google-maps.png' alt='Screenshot showing Google Maps integration in Home Assistant front end.'>
 </p>
 
-[generic camera platform]: /components/generic
+[generic camera platform]: /integrations/generic

source/_cookbook/ifttt.manything.markdown

@@ -4,12 +4,12 @@ description: "Instructions on how to setup ManyThing support with IFTTT."
 logo: manything.png
 ha_category: Camera
 redirect_from:
-  /components/ifttt.manything/
+  /integrations/ifttt.manything/
 ---
 
 [Manything](https://manything.com) is a smart app that turns your Android device, iPhone, iPod, or iPad into a WiFi camera for monitoring your home, your pets, anything! Comes with live streaming, motion activated alerts, cloud video recording, and more.
 
-To get manything support, HA will use IFTTT's [Webhooks Service](https://ifttt.com/maker_webhooks) and the [ManyThing Service](https://ifttt.com/manything). Use the [IFTTT Setup instructions](/components/ifttt/) to activate the IFTTT Platform.
+To get manything support, HA will use IFTTT's [Webhooks Service](https://ifttt.com/maker_webhooks) and the [ManyThing Service](https://ifttt.com/manything). Use the [IFTTT Setup instructions](/integrations/ifttt/) to activate the IFTTT Platform.
 
 After setting up IFTTT, Maker Service and ManyThing Service, you can use the following examples to configure Home Assistant.
 
@@ -50,7 +50,7 @@ automation:
 ### Setting up a recipe
 
 <p class='img'>
-<img src='/images/components/ifttt/IFTTT_manything_trigger.png' />
+<img src='/images/integrations/ifttt/IFTTT_manything_trigger.png' />
 You need to setup a unique trigger for each event you sent to IFTTT.
 For ManyThing support, you need to set up an `on` and `off` event.
 </p>

source/_cookbook/notify.mqtt.markdown

@@ -5,10 +5,10 @@ logo: mqtt.png
 ha_category: Notifications
 ha_iot_class: Configurable
 redirect_from:
-  /components/notify.mqtt/
+  /integrations/notify.mqtt/
 ---
 
-The MQTT notification support is different than the other [notification](/components/notify/) platforms. It is a service. This means that you don't have to create a configuration entry but you need to provide more details when calling the service.
+The MQTT notification support is different than the other [notification](/integrations/notify/) platforms. It is a service. This means that you don't have to create a configuration entry but you need to provide more details when calling the service.
 
 **Call Service** section from the <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Developer Tools** allows you to send MQTT messages. Choose *mqtt.publish*  from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
 
@@ -43,7 +43,7 @@ $ curl -X POST \
 
 ### Automations
 
-Use as [`script`](/components/script/) in automations.
+Use as [`script`](/integrations/script/) in automations.
 
 {% raw %}
 ```yaml

source/_cookbook/notify_if__new_ha_release.markdown

@@ -27,7 +27,7 @@ automation:
           message: 'There is a new Home Assistant release available.'
 ```
 
-You can use [templates](/topics/templating/) to include the release number of Home Assistant if you prefer. The following example sends a notification via [Pushbullet](/components/pushbullet) with the Home Assistant version in the message.
+You can use [templates](/topics/templating/) to include the release number of Home Assistant if you prefer. The following example sends a notification via [Pushbullet](/integrations/pushbullet) with the Home Assistant version in the message.
 
 ```yaml
 notify:

source/_cookbook/perform_actions_based_on_input_select.markdown

@@ -4,7 +4,7 @@ description: "Example playing media to Chromecast based on input select element"
 ha_category: Automation Examples
 ---
 
-This example uses an [`input_select`](/components/input_select/) element to pick which mp3 file to play on a [Chromecast](/components/cast/).
+This example uses an [`input_select`](/integrations/input_select/) element to pick which mp3 file to play on a [Chromecast](/integrations/cast/).
 
 ```yaml
 # Define our dropdown list
@@ -69,7 +69,7 @@ automation:
       data:
         entity_id: media_player.nursery
 ```
-A little bit more complex example that uses [`input_select`](/components/input_select/) and template to decide what to play, and which [Chromecast](/components/cast/) to play on.
+A little bit more complex example that uses [`input_select`](/integrations/input_select/) and template to decide what to play, and which [Chromecast](/integrations/cast/) to play on.
 
 ```yaml
 input_select:

source/_cookbook/python_component_mqtt_basic.markdown

@@ -6,7 +6,7 @@ ha_category: Custom Python Component Examples
 
 <div class='note'>
 
-This example requires you to have the [MQTT integration](/components/mqtt/) up and running.
+This example requires you to have the [MQTT integration](/integrations/mqtt/) up and running.
 
 </div>
 

source/_cookbook/python_component_simple_alarm.markdown

@@ -4,9 +4,9 @@ description: "Detect intruders by checking if the light is turning on while no o
 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 integration](/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](/integrations/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.
+This integration depends on the integrations [device_tracker](/integrations/device_tracker/) and [light](/integrations/light/) being setup.
 
 To set it up, add the following lines to your `configuration.yaml` file:
 

source/_cookbook/restart_ha_if_wemo_switch_is_not_detected.markdown

@@ -6,7 +6,7 @@ ha_category: Automation Examples
 
 ### Restart Home Assistant
 
-This configuration example is restarting Home Assistant if a [WeMo](/components/wemo) switch is not detected. An additional MQTT switch is present for stopping Home Assistant and can be triggered by [IFTTT](/components/ifttt/). The running batch script will automatically restart Home Assistant if the process isn't found anymore.
+This configuration example is restarting Home Assistant if a [WeMo](/integrations/wemo) switch is not detected. An additional MQTT switch is present for stopping Home Assistant and can be triggered by [IFTTT](/integrations/ifttt/). The running batch script will automatically restart Home Assistant if the process isn't found anymore.
 
 ```yaml
 mqtt:

source/_cookbook/send_a_reminder.markdown

@@ -6,7 +6,7 @@ ha_category: Automation Examples
 
 Always forget to eat lunch? Let Home Assistant send you a reminder.
 
-Add a [notify platform](/components/notify/) of your choice.
+Add a [notify platform](/integrations/notify/) of your choice.
 
 ```yaml
 notify:

source/_cookbook/sonos_say.markdown

@@ -6,7 +6,7 @@ ha_category: Automation Examples
 
 #### Sonos say script to speak with text-to-speech
 
-This script allows you to use [TTS](/components/#text-to-speech) on Sonos.
+This script allows you to use [TTS](/integrations/#text-to-speech) on Sonos.
 
 ```yaml
 script:

source/_cookbook/track_battery_level.markdown

@@ -6,7 +6,7 @@ ha_category: Automation Examples
 
 ### iOS Devices
 
-If you have a device running iOS (iPhone, iPad, etc), The [iCloud](/components/icloud) integration is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/components/template). You can also use the `battery` [sensor device class](/components/sensor/#device-class) to dynamically change the icon with the battery level.
+If you have a device running iOS (iPhone, iPad, etc), The [iCloud](/integrations/icloud) integration is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/integrations/template). You can also use the `battery` [sensor device class](/integrations/sensor/#device-class) to dynamically change the icon with the battery level.
 
 {% raw %}
 ```yaml
@@ -27,7 +27,7 @@ sensor:
 {% endraw %}
 
 ### Android and iOS Devices
-While running the [Owntracks](/components/owntracks) device tracker you can retrieve the battery level. 
+While running the [Owntracks](/integrations/owntracks) device tracker you can retrieve the battery level. 
 How you achieve this depends on how you have configured your Owntracks instance. 
 
 #### MQTT

source/_data/glossary.yml

@@ -13,21 +13,21 @@
 - topic: Device
   description: "A device is usually a physical unit which can do or observe something."
 - topic: Discovery
-  description: "[Discovery](/components/discovery/) is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered."
+  description: "[Discovery](/integrations/discovery/) is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered."
 - topic: Entity
   description: "An [entity](/docs/configuration/platform_options/) is the representation of function a single device, unit, or web service. There may be multiple entities for a single device, unit, or web service, or there may be only one."
 - topic: Event
   description: "An [event](/docs/configuration/events/) is when something happens."
 - topic: Frontend
-  description: "The [frontend](/components/frontend/) is a necessary component for the UI, it is also where you can define your themes."
+  description: "The [frontend](/integrations/frontend/) is a necessary component for the UI, it is also where you can define your themes."
 - topic: Group
-  description: "[Groups](/components/group/) are a way to organize your entities into a single unit."
+  description: "[Groups](/integrations/group/) are a way to organize your entities into a single unit."
 - topic: hass
   description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is also the command-line tool."
 - topic: Hass.io
   description: "[Hass.io](/hassio/) is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration, and can easily be extended."
 - topic: Integration
-  description: "[Integrations](/components/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
+  description: "[Integrations](/integrations/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
 - topic: Lovelace
   description: "[Lovelace](/lovelace/) is the name of the current frontend."
 - topic: Packages
@@ -35,7 +35,7 @@
 - topic: Platform
   description: "[Platforms](/docs/configuration/platform_options/) make the connection to a specific software or hardware platform. For example, the `pushbullet` platform works with the service pushbullet.com to send notifications."
 - topic: Scene
-  description: "[Scenes](/components/scene/) capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red." 
+  description: "[Scenes](/integrations/scene/) capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red." 
 - topic: Script
   description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on."
 - topic: Service
@@ -45,4 +45,4 @@
 - topic: Trigger
   description: "A [trigger](/docs/automation/trigger/) is a set of values or conditions of a platform that are defined to cause an automation to run."
 - topic: Zone
-  description: "[Zones](/components/zone/) are areas that can be used for presence detection."
+  description: "[Zones](/integrations/zone/) are areas that can be used for presence detection."

source/_docs/asterisk_mbox.markdown

@@ -12,7 +12,7 @@ There are two components to the integration:
 
 Both parts are necessary for Asterisk voicemail integration.
 
-The server installation is documented below. The client is [integrated inside Home Assistant](/components/asterisk_mbox)
+The server installation is documented below. The client is [integrated inside Home Assistant](/integrations/asterisk_mbox)
 
 <div class='note'>
 Currently this module can only monitor a single Asterisk PBX mailbox.
@@ -74,7 +74,7 @@ Before beginning make sure that you have the following:
    sudo -u asterisk asterisk_mbox_server -v --cfg /etc/asterisk/asterisk_mbox.ini
    ```
 
-   Now complete the [Home Assistant configuration](/components/asterisk_mbox) and verify that Home Assistant can communicate with the server
+   Now complete the [Home Assistant configuration](/integrations/asterisk_mbox) and verify that Home Assistant can communicate with the server
 
    You can use `Ctrl-c` to terminate the server when done testing
 

source/_docs/authentication.markdown

@@ -2,7 +2,7 @@
 title: "Authentication"
 description: "Guide on authentication in Home Assistant."
 redirect_from:
-  - /components/auth/
+  - /integrations/auth/
 ---
 
 Our authentication system secures access to Home Assistant.
@@ -33,7 +33,7 @@ You can:
 
 * Change the language you prefer Home Assistant to use.
 * Change your password. 
-* Select the [theme](/components/frontend/#defining-themes) for the interface of Home Assistant.
+* Select the [theme](/integrations/frontend/#defining-themes) for the interface of Home Assistant.
 * Enable or disable [multi-factor authentication](/docs/authentication/multi-factor-auth/).
 * Delete _Refresh Tokens_. These are created when you log in from a device. Delete them if you want to force the device to log out.
 * Create [Long Lived Access Tokens](https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token) so scripts can securely interact with Home Assistant. 
@@ -54,7 +54,7 @@ Home Assistant provides several ways to authenticate. See the [Auth Providers](/
 
 ### Authentication failures from `127.0.0.1`
 
-If you're seeing authentication failures from `127.0.0.1` and you're using the `nmap` device tracker, you should [exclude the Home Assistant IP](/components/nmap_tracker#exclude) from being scanned.
+If you're seeing authentication failures from `127.0.0.1` and you're using the `nmap` device tracker, you should [exclude the Home Assistant IP](/integrations/nmap_tracker#exclude) from being scanned.
 
 ### Bearer token warnings
 
@@ -64,7 +64,7 @@ Under the new authentication system you'll see the following warning logged when
 WARNING (MainThread) [homeassistant.components.http.auth] You need to use a bearer token to access /blah/blah from 192.0.2.4
 ```
 
-If you see this, you need to add an [`api_password`](/components/http/#api_password) to your `http:` configuration.
+If you see this, you need to add an [`api_password`](/integrations/http/#api_password) to your `http:` configuration.
 
 ### Bearer token informational messages
 

source/_docs/authentication/multi-factor-auth.markdown

@@ -1,7 +1,7 @@
 ---
 title: "Multi-factor authentication"
 description: "Guide on configuring different multi-factor authentication modules."
-redirect_from: /components/auth/
+redirect_from: /integrations/auth/
 ---
 
 The Multi-factor Authentication (MFA) modules require you to solve a second challenge after you provide your password.
@@ -61,7 +61,7 @@ TOTP is _time based_ so it relies on your Home Assistant clock being accurate. I
 
 ### Notify multi-factor authentication module
 
-The Notify MFA module uses the [notify component](/components/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in.
+The Notify MFA module uses the [notify component](/integrations/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in.
 
 #### Setting up TOTP
 

source/_docs/authentication/providers.markdown

@@ -1,7 +1,7 @@
 ---
 title: "Authentication Providers"
 description: "Guide on configuring different auth providers."
-redirect_from: /components/auth/
+redirect_from: /integrations/auth/
 ---
 
 When you log in, an _auth provider_ checks your credentials to make sure you are an authorized user.

source/_docs/automation/action.markdown

@@ -6,7 +6,7 @@ redirect_from: /getting-started/automation-action/
 
 The action of an automation rule is what is being executed when a rule fires. The action part follows the [script syntax](/docs/scripts/) which can be used to interact with anything via services or events. For services you can specify the entity_id that it should apply to and optional service parameters (to specify for example the brightness).
 
-You can also call the service to activate [a scene](/components/scene/) which will allow you to define how you want your devices to be and have Home Assistant call the right services.
+You can also call the service to activate [a scene](/integrations/scene/) which will allow you to define how you want your devices to be and have Home Assistant call the right services.
 
 ```yaml
 automation:

source/_docs/automation/editor.markdown

@@ -5,7 +5,7 @@ description: "Instructions on how to use the automation editor."
 
 In Home Assistant 0.45 we introduced the first version of our automation editor. If you just created a new configuration with Home Assistant, then you're all set! Go to the UI and enjoy.
 
-From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor. Press the **+** sign in the lower right corner to get started. This example is based on the manual steps described in the [Getting started section](/getting-started/automation/) for a [`random` sensor](/components/sensor.random/).
+From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor. Press the **+** sign in the lower right corner to get started. This example is based on the manual steps described in the [Getting started section](/getting-started/automation/) for a [`random` sensor](/integrations/sensor.random/).
 
 Choose a meaningful name for your automation rules.
 
@@ -19,7 +19,7 @@ If the value of the sensor is greater than 10, then the automation rule should a
   <img src='{{site_root}}/images/docs/automation-editor/new-trigger.png' />
 </p>
 
-Firing a [persistent notification](/components/persistent_notification/) is the result.
+Firing a [persistent notification](/integrations/persistent_notification/) is the result.
 
 <p class='img'>
   <img src='{{site_root}}/images/docs/automation-editor/new-action.png' />

source/_docs/automation/trigger.markdown

@@ -337,7 +337,7 @@ You could test triggering the above automation by sending a POST HTTP request to
 
 ### Zone trigger
 
-Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/components/device_tracker.gpslogger/), the [OwnTracks platform](/components/device_tracker.owntracks/) and the [iCloud platform](/components/device_tracker.icloud/).
+Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/device_tracker.gpslogger/), the [OwnTracks platform](/integrations/device_tracker.owntracks/) and the [iCloud platform](/integrations/device_tracker.icloud/).
 
 ```yaml
 automation:
@@ -351,7 +351,7 @@ automation:
 
 ### Geolocation trigger
 
-Geolocation triggers can trigger when an entity is appearing in or disappearing from a zone. Entities that are created by a [Geolocation](/components/geo_location/) platform support reporting GPS coordinates.
+Geolocation triggers can trigger when an entity is appearing in or disappearing from a zone. Entities that are created by a [Geolocation](/integrations/geo_location/) platform support reporting GPS coordinates.
 Because entities are generated and removed by these platforms automatically, the entity id normally cannot be predicted. Instead, this trigger requires the definition of a `source` which is directly linked to one of the Geolocation platforms.
 
 ```yaml

source/_docs/automation/troubleshooting.markdown

@@ -4,7 +4,7 @@ description: "Tips on how to troubleshoot your automations."
 redirect_from: /getting-started/automation-troubleshooting/
 ---
 
-You can verify that your automation rules are being initialized correctly by watching both the realtime logs (`homeassistant.log` in the configuration directory) and also the [Logbook](/components/logbook/). The realtime logs will show the rules being initialized (once for each trigger), example:
+You can verify that your automation rules are being initialized correctly by watching both the realtime logs (`homeassistant.log` in the configuration directory) and also the [Logbook](/integrations/logbook/). The realtime logs will show the rules being initialized (once for each trigger), example:
 
 ```text
 INFO [homeassistant.components.automation] Initialized rule Rainy Day
@@ -15,7 +15,7 @@ INFO [homeassistant.components.automation] Initialized rule Rain is over
 
 The Logbook integration will show a line entry when an automation is triggered. You can look at the previous entry to determine which trigger in the rule triggered the event.
 
-![Logbook example](/images/components/automation/logbook.png)
+![Logbook example](/images/integrations/automation/logbook.png)
 
 [template]: /topics/templating/
 

source/_docs/backend/database.markdown

@@ -4,7 +4,7 @@ description: "Details about the database used by Home Assistant."
 redirect_from: /details/database/
 ---
 
-The default database used by Home Assistant is [SQLite](https://www.sqlite.org/), and the database file is stored in your [configuration directory](/getting-started/configuration/) (e.g., `<path to config dir>/.homeassistant/home-assistant_v2.db`). If you prefer to run a database server (e.g. PostgreSQL), use the [`recorder` component](/components/recorder/).
+The default database used by Home Assistant is [SQLite](https://www.sqlite.org/), and the database file is stored in your [configuration directory](/getting-started/configuration/) (e.g., `<path to config dir>/.homeassistant/home-assistant_v2.db`). If you prefer to run a database server (e.g. PostgreSQL), use the [`recorder` component](/integrations/recorder/).
 
 To work with the SQLite database manually from the command-line, you will need an [installation](http://www.sqlitetutorial.net/download-install-sqlite/) of `sqlite3`. Alternatively [DB Browser for SQLite](http://sqlitebrowser.org/) provides a viewer for exploring the database data and an editor for executing SQL commands.
 First load your database with `sqlite3`:

source/_docs/backend/updater.markdown

@@ -4,7 +4,7 @@ description: "Details what the updater integration is reporting about your Home
 redirect_from: /details/updater/
 ---
 
-Starting with 0.31 the [updater component](/components/updater/) sends an optional report about Home Assistant instance.
+Starting with 0.31 the [updater component](/integrations/updater/) sends an optional report about Home Assistant instance.
 
 If you want to opt-in to include integration information, add `include_used_components` to your config. This will allow the Home Assistant developers to focus development efforts on the most popular components.
 

source/_docs/configuration.markdown

@@ -32,7 +32,7 @@ If you run into trouble while configuring Home Assistant, have a look at the [co
 ## Reloading changes
 
 You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect.
-You can load changes to [automations](/docs/automation/), [core (customize)](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting.
+You can load changes to [automations](/docs/automation/), [core (customize)](/docs/configuration/customizing-devices/), [groups](/integrations/group/), and [scripts](/integrations/script/) without restarting.
 
 <div class='note warning'>
 

source/_docs/configuration/customizing-devices.markdown

@@ -49,7 +49,7 @@ homebridge_hidden:
   type: boolean
   default: false
 emulated_hue_hidden:
-  description: Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/components/emulated_hue)).
+  description: Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/integrations/emulated_hue)).
   required: false
   type: boolean
   default: false
@@ -86,9 +86,9 @@ initial_state:
 
 Device class is currently supported by the following components:
 
-* [Binary Sensor](/components/binary_sensor/)
+* [Binary Sensor](/integrations/binary_sensor/)
-* [Sensor](/components/sensor/)
+* [Sensor](/integrations/sensor/)
-* [Cover](/components/cover/)
+* [Cover](/integrations/cover/)
 
 ### Manual customization
 

source/_docs/configuration/devices.markdown

@@ -4,9 +4,9 @@ description: "Steps to help you get your devices in Home Assistant."
 redirect_from: /getting-started/devices/
 ---
 
-Home Assistant will be able to automatically discover many devices and services available on your network if you have [the discovery component](/components/discovery/) enabled (the default setting).
+Home Assistant will be able to automatically discover many devices and services available on your network if you have [the discovery component](/integrations/discovery/) enabled (the default setting).
 
-See the [components overview page](/components/) to find installation instructions for your devices and services. If you can't find support for your favorite device or service, [consider adding support](/developers/add_new_platform/).
+See the [components overview page](/integrations/) to find installation instructions for your devices and services. If you can't find support for your favorite device or service, [consider adding support](/developers/add_new_platform/).
 
 Classification for the available integrations:
 
@@ -76,4 +76,4 @@ group:
       - media_player.nexus_player
 ```
 
-For more details please check the [Group](/components/group/) page.
+For more details please check the [Group](/integrations/group/) page.

source/_docs/configuration/events.markdown

@@ -73,7 +73,7 @@ Field | Description
 
 ### Event `platform_discovered`
 
-Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/components/discovery/) component.
+Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/integrations/discovery/) component.
 
 Field | Description
 ----- | -----------

source/_docs/configuration/templating.markdown

@@ -11,8 +11,8 @@ This is an advanced feature of Home Assistant. You'll need a basic understanding
 
 Templating is a powerful feature that allows you to control information going into and out of the system. It is used for:
 
-- Formatting outgoing messages in, for example, the [notify](/components/notify/) platforms and [alexa](/components/alexa/) component.
+- Formatting outgoing messages in, for example, the [notify](/integrations/notify/) platforms and [alexa](/integrations/alexa/) component.
-- Process incoming data from sources that provide raw data, like [MQTT](/components/mqtt/), [`rest` sensor](/components/sensor.rest/) or the [`command_line` sensor](/components/sensor.command_line/).
+- Process incoming data from sources that provide raw data, like [MQTT](/integrations/mqtt/), [`rest` sensor](/integrations/sensor.rest/) or the [`command_line` sensor](/integrations/sensor.command_line/).
 - [Automation Templating](/docs/automation/templating/).
 
 ## Building templates
@@ -393,7 +393,7 @@ If your template uses an `entity_id` that begins with a number (example: `states
 
 ### Templates without entities using `now()`
 
-Note that templates that depend on time (`now()`) and do not use any entities will not be updated as it only happens on entity state changes. For more information and examples refer to [`template` sensor documentation](/components/sensor.template/#working-without-entities)
+Note that templates that depend on time (`now()`) and do not use any entities will not be updated as it only happens on entity state changes. For more information and examples refer to [`template` sensor documentation](/integrations/sensor.template/#working-without-entities)
 
 ### Priority of operators
 

source/_docs/configuration/troubleshooting.markdown

@@ -36,9 +36,9 @@ sensor:
     ...
 ```
 
-Another common problem is that a required configuration setting is missing. If this is the case, the integration will report this to `home-assistant.log`. You can have a look at [the various integration pages](/components/) for instructions on how to setup the components.
+Another common problem is that a required configuration setting is missing. If this is the case, the integration will report this to `home-assistant.log`. You can have a look at [the various integration pages](/integrations/) for instructions on how to setup the components.
 
-See the [logger](/components/logger/) integration for instructions on how to define the level of logging you require for specific modules.
+See the [logger](/integrations/logger/) integration for instructions on how to define the level of logging you require for specific modules.
 
 If you find any errors or want to expand the documentation, please [let us know](https://github.com/home-assistant/home-assistant.io/issues).
 

source/_docs/configuration/yaml.markdown

@@ -7,7 +7,7 @@ redirect_from: /getting-started/yaml/
 Home Assistant uses the [YAML](http://yaml.org/) syntax for configuration. YAML might take a while to get used to but is really powerful in allowing you to express complex configurations.
 
 For each integration that you want to use in Home Assistant, you add code in your `configuration.yaml` file to specify its settings.
-The following example entry specifies that you want to use the [notify component](/components/notify) with the [pushbullet platform](/components/notify.pushbullet).
+The following example entry specifies that you want to use the [notify component](/integrations/notify) with the [pushbullet platform](/integrations/notify.pushbullet).
 
 
 ```yaml
@@ -36,7 +36,7 @@ Please pay attention on not storing private data (passwords, API keys, etc.) dir
 
 Text following a `#` are comments and are ignored by the system.
 
-The next example shows an [input_select](/components/input_select) integration that uses a block collection for the options values.
+The next example shows an [input_select](/integrations/input_select) integration that uses a block collection for the options values.
 The other properties (like name) are specified using mappings. Note that the second line just has `threat:` with no value on the same line. Here threat is the name of the input_select and the values for it are everything nested below it.
 
 ```yaml

source/_docs/ecosystem/certificates.markdown

@@ -5,4 +5,4 @@ description: "Protect your communication with Home Assistant."
 
 If you plan to expose your Home Assistant to the internet or want an extra layer of protection in your local network, consider to use SSL/TLS. This way you can protect your communication. Especially sensitive data like usernames and  passwords are encrypted between the endpoints.
 
-Setting up usually requires creating the certificate and configure the [`http`](/components/http/) component.
+Setting up usually requires creating the certificate and configure the [`http`](/integrations/http/) component.

source/_docs/ecosystem/certificates/lets_encrypt.markdown

@@ -336,7 +336,7 @@ http:
   base_url: examplehome.duckdns.org
 ```
 
-You may wish to set up other options for the [http](/components/http/) integration at this point, these extra options are beyond the scope of this guide.
+You may wish to set up other options for the [http](/integrations/http/) integration at this point, these extra options are beyond the scope of this guide.
 
 Save the changes to configuration.yaml. Restart Home Assistant.
 
@@ -426,7 +426,7 @@ sensor:
 
 Save the configuration.yaml. Restart Home Assistant.
 
-On your default_view you should now see a sensor badge containing your number of days until expiry. If you've been following this guide from the start and have not taken any breaks in between, this should be 89 or 90. The sensor will update every 3 hours. You can place this reading on a card using groups, or hide it using customize. These topics are outside of the scope of this guide, but information can be found on their respective integrations pages: [Group](/components/group/) and [Customize](/docs/configuration/customizing-devices/)
+On your default_view you should now see a sensor badge containing your number of days until expiry. If you've been following this guide from the start and have not taken any breaks in between, this should be 89 or 90. The sensor will update every 3 hours. You can place this reading on a card using groups, or hide it using customize. These topics are outside of the scope of this guide, but information can be found on their respective integrations pages: [Group](/integrations/group/) and [Customize](/docs/configuration/customizing-devices/)
 
 Got your sensor up and running and where you want it? Top drawer! Nearly there, now move on to the final steps to ensure that you're never without a secure connection in the future.
 

source/_docs/ecosystem/certificates/tls_domain_certificate.markdown

@@ -53,7 +53,7 @@ address=/mydomain.com/<hass ip>
 
 ### Edit your Home Assistant configuration to use your certificates
 
-The [`http`](/components/http/) section must contain the full path to the needed files. 
+The [`http`](/integrations/http/) section must contain the full path to the needed files. 
 
 ```yaml
 http:

source/_docs/ecosystem/haproxy.markdown

@@ -89,7 +89,7 @@ Replace 443 with whatever port you chose to bind to in the config if different.
 
 ### Configure Home Assistant HTTP Component
 
-In your `configuration.yaml` file, edit the [http component](/components/http/).
+In your `configuration.yaml` file, edit the [http component](/integrations/http/).
 
 ```text
 http:

source/_docs/ecosystem/hass-configurator.markdown

@@ -86,7 +86,7 @@ The way this is implemented works in the following order:
   - No: Return error 420
 
 ### Embedding into Home Assistant
-Home Assistant has the [panel_iframe](/components/panel_iframe/) component. With this it is possible to embed the configurator directly into Home Assistant, allowing you to modify your configuration through the Home Assistant frontend.
+Home Assistant has the [panel_iframe](/integrations/panel_iframe/) component. With this it is possible to embed the configurator directly into Home Assistant, allowing you to modify your configuration through the Home Assistant frontend.
 An example configuration would look like this:
 
 ```yaml

source/_docs/ecosystem/ios.markdown

@@ -23,7 +23,7 @@ The app is available on the iOS App Store in every country that Apple supports.
 
 The `ios` integration is the companion integration for the Home Assistant iOS app. While not required, adding the `ios` integration to your setup will greatly enhance the iOS app with new notification, location and sensor functions not possible with a standalone app.
 
-Loading the `ios` integration will also load the [`device_tracker`](/components/device_tracker), [`zeroconf`](/components/zeroconf) and [`notify`](/components/notify) platforms.
+Loading the `ios` integration will also load the [`device_tracker`](/integrations/device_tracker), [`zeroconf`](/integrations/zeroconf) and [`notify`](/integrations/notify) platforms.
 
 The Home Assistant for iOS app supports the new authentication system introduced in Home Assistant 0.77.
 
@@ -33,7 +33,7 @@ The Home Assistant for iOS app supports the new authentication system introduced
 
 The `ios` integration will automatically be loaded under the following circumstances:
 
-1. The [`discovery`](/components/discovery) integration is enabled.
+1. The [`discovery`](/integrations/discovery) integration is enabled.
 2. You have just installed the app and are at the getting started screen.
 
 Automated discovery and integration loading only happens at first install of the app. You may need to wait a few minutes for the iOS integration to load as the `discovery` integration only scans the network every 5 minutes.

source/_docs/ecosystem/ios/notifications/basic.markdown

@@ -74,7 +74,7 @@ automation:
 
 
 ### Sending notifications to multiple phones
-To send notifications to multiple phones, create a [notification group](/components/notify.group/):
+To send notifications to multiple phones, create a [notification group](/integrations/notify.group/):
 ```yaml
 notify:
   - name: NOTIFIER_NAME

source/_docs/ecosystem/notebooks/graph.markdown

@@ -4,4 +4,4 @@ description: "Basic example how to create a graph with a Jupyter notebook."
 redirect_from: /ecosystem/notebooks/graph/
 ---
 
-For graphing this [Jupyter notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/graph-single-sensor.ipynb) should get you started.
+For graphing this [Jupyter notebook](https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/graph-single-sensor.ipynb) should get you started.

source/_docs/ecosystem/notebooks/stats.markdown

@@ -4,4 +4,4 @@ description: "Basic example how to create basic statistics with a Jupyter notebo
 redirect_from: /ecosystem/notebooks/stats/
 ---
 
-The [Statistics notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb) shows some basic statistical analysis on data in the Home Assistant database.
+The [Statistics notebook](https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/database-statistics.ipynb) shows some basic statistical analysis on data in the Home Assistant database.

source/_docs/installation/hassbian/customization.markdown

@@ -52,4 +52,4 @@ To upgrade any of them simply run `sudo hassbian-config upgrade SUITE`.
 For more information about this tool have a look at the [hassbian-scripts repository][hassbian-repo].
 
 [hassbian-repo]: https://github.com/home-assistant/hassbian-scripts
-[cec]: /components/hdmi_cec/
+[cec]: /integrations/hdmi_cec/

source/_docs/installation/hassbian/integrations.markdown

@@ -10,7 +10,7 @@ Some integrations that are specific for the Raspberry Pi can require some furthe
 
 The Bluetooth tracker will work on a Raspberry Pi 3 with the built-in Bluetooth module or with a USB Bluetooth device on any of the other Raspberry Pi's.
 
-Software needed for the tracker is pre-installed so just follow the [Bluetooth Tracker integration](/components/bluetooth_tracker/) and [Device Tracker page](/components/device_tracker/) pages.
+Software needed for the tracker is pre-installed so just follow the [Bluetooth Tracker integration](/integrations/bluetooth_tracker/) and [Device Tracker page](/integrations/device_tracker/) pages.
 
 ### Raspberry Pi GPIO
 
@@ -20,11 +20,11 @@ For more details about the GPIO layout, visit the [documentation](https://www.ra
 Permission have been given to the `homeassistant` user to use the GPIO pins and all of the following integrations should require no underlying changes to work.
 Just follow the integration pages for each on how to add them to your Home Assistant installation.
 
- - [DHT Sensor](/components/dht/)
+ - [DHT Sensor](/integrations/dht/)
- - [Raspberry Pi Cover](/components/rpi_gpio/#cover)
+ - [Raspberry Pi Cover](/integrations/rpi_gpio/#cover)
- - [Raspberry Pi GPIO Binary Sensor](/components/rpi_gpio/#binary-sensor)
+ - [Raspberry Pi GPIO Binary Sensor](/integrations/rpi_gpio/#binary-sensor)
- - [Raspberry Pi GPIO Switch](/components/rpi_gpio/#switch)
+ - [Raspberry Pi GPIO Switch](/integrations/rpi_gpio/#switch)
- - [Raspberry Pi RF Switch](/components/rpi_rf/)
+ - [Raspberry Pi RF Switch](/integrations/rpi_rf/)
 
 ### Raspberry Pi Camera
 
@@ -38,7 +38,7 @@ $ sudo raspi-config
 
 Go to `Interfacing Options`, select `Enable camera` choose `<Yes>` and hit `Enter`, then go to `Finish` and you'll be prompted to reboot.
 
-After this follow the [Raspberry Pi Camera integration](/components/rpi_camera/) page.
+After this follow the [Raspberry Pi Camera integration](/integrations/rpi_camera/) page.
 
 ### One wire Sensor
 
@@ -47,4 +47,4 @@ To enable One Wire support add the following line to the end of `/boot/config.tx
 ```yaml
 dtoverlay=w1-gpio
 ```
-After this follow the [One Wire Sensor integration](/components/onewire/) page.
+After this follow the [One Wire Sensor integration](/integrations/onewire/) page.

source/_docs/mqtt/broker.markdown

@@ -105,7 +105,7 @@ mqtt:
 
 ### CloudMQTT
 
-[CloudMQTT](https://www.cloudmqtt.com) is a hosted private MQTT instance that is free for up to 10 connected devices. This is enough to get started with for example [OwnTracks](/components/device_tracker.owntracks/) and give you a taste of what is possible.
+[CloudMQTT](https://www.cloudmqtt.com) is a hosted private MQTT instance that is free for up to 10 connected devices. This is enough to get started with for example [OwnTracks](/integrations/device_tracker.owntracks/) and give you a taste of what is possible.
 
 <div class='note'>
 Home Assistant is not affiliated with CloudMQTT nor will receive any kickbacks.

source/_docs/mqtt/discovery.markdown

@@ -4,21 +4,21 @@ description: "Instructions on how to setup MQTT Discovery within Home Assistant.
 logo: mqtt.png
 ---
 
-The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/components/binary_sensor.http/) and the [HTTP sensor](/components/sensor.http/). To prevent multiple identical entries if a device reconnects a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier and the remaining device configuration without the device type.
+The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/integrations/binary_sensor.http/) and the [HTTP sensor](/integrations/sensor.http/). To prevent multiple identical entries if a device reconnects a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier and the remaining device configuration without the device type.
 
 Supported by MQTT discovery:
 
-- [Alarm control panels](/components/alarm_control_panel.mqtt/)
+- [Alarm control panels](/integrations/alarm_control_panel.mqtt/)
-- [Binary sensors](/components/binary_sensor.mqtt/)
+- [Binary sensors](/integrations/binary_sensor.mqtt/)
-- [Cameras](/components/camera.mqtt/)
+- [Cameras](/integrations/camera.mqtt/)
-- [Covers](/components/cover.mqtt/)
+- [Covers](/integrations/cover.mqtt/)
-- [Fans](/components/fan.mqtt/)
+- [Fans](/integrations/fan.mqtt/)
-- [HVACs](/components/climate.mqtt/)
+- [HVACs](/integrations/climate.mqtt/)
-- [Lights](/components/light.mqtt/)
+- [Lights](/integrations/light.mqtt/)
-- [Locks](/components/lock.mqtt/)
+- [Locks](/integrations/lock.mqtt/)
-- [Sensors](/components/sensor.mqtt/)
+- [Sensors](/integrations/sensor.mqtt/)
-- [Switches](/components/switch.mqtt/)
+- [Switches](/integrations/switch.mqtt/)
-- [Vacuums](/components/vacuum.mqtt/)
+- [Vacuums](/integrations/vacuum.mqtt/)
 
 To enable MQTT discovery, add the following to your `configuration.yaml` file:
 
@@ -230,7 +230,7 @@ The following software has built-in support for MQTT discovery:
 
 ### Examples
 
-A motion detection device which can be represented by a [binary sensor](/components/binary_sensor.mqtt/) for your garden would send its configuration as JSON payload to the Configuration topic. After the first message to `config`, then the MQTT messages sent to the state topic will update the state in Home Assistant.
+A motion detection device which can be represented by a [binary sensor](/integrations/binary_sensor.mqtt/) for your garden would send its configuration as JSON payload to the Configuration topic. After the first message to `config`, then the MQTT messages sent to the state topic will update the state in Home Assistant.
 
 - Configuration topic: `homeassistant/binary_sensor/garden/config`
 - State topic: `homeassistant/binary_sensor/garden/state`
@@ -253,7 +253,7 @@ Delete the sensor by sending an empty message.
 $ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m ''
 ```
 
-Setting up a switch is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/components/switch.mqtt/).
+Setting up a switch is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/integrations/switch.mqtt/).
 
 - Configuration topic: `homeassistant/switch/irrigation/config`
 - State topic: `homeassistant/switch/irrigation/state`

source/_docs/mqtt/logging.markdown

@@ -4,7 +4,7 @@ description: "Instructions on how to setup MQTT Logging within Home Assistant."
 logo: mqtt.png
 ---
 
-The [logger](/components/logger/) integration allows the logging of received MQTT messages.
+The [logger](/integrations/logger/) integration allows the logging of received MQTT messages.
 
 ```yaml
 # Example configuration.yaml entry

source/_docs/mqtt/processing_json.markdown

@@ -4,7 +4,7 @@ description: "Instructions on how to process the MQTT payload."
 logo: mqtt.png
 ---
 
-The MQTT [switch](/components/switch.mqtt/) and [sensor](/components/sensor.mqtt/) platforms support processing JSON over MQTT messages and parsing them using JSONPath. JSONPath allows you to specify where in the JSON the value resides that you want to use. The following examples will always return the value `100`.
+The MQTT [switch](/integrations/switch.mqtt/) and [sensor](/integrations/sensor.mqtt/) platforms support processing JSON over MQTT messages and parsing them using JSONPath. JSONPath allows you to specify where in the JSON the value resides that you want to use. The following examples will always return the value `100`.
 
 | JSONPath query | JSON |
 | -------------- | ---- |

source/_docs/scripts.markdown

@@ -194,8 +194,8 @@ The following automation shows how to capture the custom event `event_light_stat
 ```
 {% endraw %}
 
-[Script component]: /components/script/
+[Script component]: /integrations/script/
 [automations]: /getting-started/automation-action/
-[Alexa/Amazon Echo]: /components/alexa/
+[Alexa/Amazon Echo]: /integrations/alexa/
 [service calls page]: /getting-started/scripts-service-calls/
 [conditions page]: /getting-started/scripts-conditions/

source/_docs/scripts/conditions.markdown

@@ -235,13 +235,13 @@ Time condition windows can span across the midnight threshold. In the example ab
 
 <div class='note tip'>
 
-A better weekday condition could be by using the [Workday Binary Sensor](/components/binary_sensor.workday/).
+A better weekday condition could be by using the [Workday Binary Sensor](/integrations/binary_sensor.workday/).
 
 </div>
 
 ### Zone condition
 
-Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/) and the [iCloud platform](/components/device_tracker.icloud/).
+Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the [OwnTracks platform](/integrations/device_tracker.owntracks/) and the [iCloud platform](/integrations/device_tracker.icloud/).
 
 ```yaml
 condition:

source/_docs/scripts/service-calls.markdown

@@ -35,7 +35,7 @@ data:
   rgb_color: [255, 0, 0]
 ```
 
-A full list of the parameters for a service can be found on the documentation page of each component, in the same way as it's done for the `light.turn_on` [service](/components/light/#service-lightturn_on).
+A full list of the parameters for a service can be found on the documentation page of each component, in the same way as it's done for the `light.turn_on` [service](/integrations/light/#service-lightturn_on).
 
 ### Use templates to decide which service to call
 
@@ -97,6 +97,6 @@ There are four `homeassistant` services that aren't tied to any single domain, t
 * `homeassistant.update_entity` - Request the update of an entity, rather than waiting for the next scheduled update, for example [google travel time] sensor, a [template sensor], or a [light]
 
 [templating]: /topics/templating/
-[google travel time]: /components/sensor.google_travel_time/
+[google travel time]: /integrations/sensor.google_travel_time/
-[template sensor]: /components/sensor.template/
+[template sensor]: /integrations/sensor.template/
-[light]: /components/light/
+[light]: /integrations/light/

source/_docs/security.markdown

@@ -15,13 +15,13 @@ Further [details about the fingerprint/server banner](/docs/security/webserver/)
 
 ## Porosity
 
-The default port of Home Assistant is 8123. This is the port where the [`frontend`](/components/frontend/) and the [`API`](/components/api/) is served. Both are depending on the [`http`](/components/http/) integration which contains the capability to adjust the settings like `server_host` or `server_port`.
+The default port of Home Assistant is 8123. This is the port where the [`frontend`](/integrations/frontend/) and the [`API`](/integrations/api/) is served. Both are depending on the [`http`](/integrations/http/) integration which contains the capability to adjust the settings like `server_host` or `server_port`.
 
 See the [open ports](/docs/security/porosity/) of a Hass.io instance with various add-ons.
 
 ## 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` integration](/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](/integrations/http/).
 
 ## SSH
 

source/_docs/security/webserver.markdown

@@ -6,7 +6,7 @@ redirect_from: /docs/frontend/webserver/
 
 It was only a matter of time until the first queries for tools like [https://www.shodan.io](https://www.shodan.io/search?query=Home+Assistant) to search for Home Assistant instances showed up.
 
-To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [Nmap device tracker](/components/device_tracker/). 
+To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [Nmap device tracker](/integrations/device_tracker/). 
 
 ```bash
 $ nmap -sV -p 8123 --script=http-title,http-headers 192.168.0.3

source/_docs/tools/dev-tools.markdown

@@ -89,7 +89,7 @@ For more information about jinja2, visit [jinja2 documentation](http://jinja.poc
 
 ## MQTT
 
-This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [mqtt](/components/mqtt/) component.
+This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [mqtt](/integrations/mqtt/) component.
 
 Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button.
 
@@ -101,4 +101,4 @@ This section displays `syslog` information, and the contents of `home-assistant.
 
 ## Info
 
-The Information tab simply provides information about the current installed version, [system health](/components/system_health/) (if enabled), additional links and credits.
+The Information tab simply provides information about the current installed version, [system health](/integrations/system_health/) (if enabled), additional links and credits.

source/_docs/z-wave.markdown

@@ -14,7 +14,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) integrations. 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](/integrations/mqtt_eventstream/) or [MQTT Statestream](/integrations/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.
 

source/_docs/z-wave/control-panel.markdown

@@ -6,7 +6,7 @@ redirect_from: /getting-started/z-wave-panel/
 
 <div class='note'>
 
-  If you don't see the **Configuration** menu on the menubar, where you'll find the Z-Wave menu, [see here](/components/config/).
+  If you don't see the **Configuration** menu on the menubar, where you'll find the Z-Wave menu, [see here](/integrations/config/).
 
 </div>
 

source/_docs/z-wave/controllers.markdown

@@ -31,10 +31,10 @@ We recommend that you purchase a [Z-Wave Plus](https://z-wavealliance.org/z-wave
 
 The alternative to a stick is a hub that supports Z-Wave. Home Assistant supports the following hubs with Z-Wave support:
 
- - [Vera](/components/vera/)
+ - [Vera](/integrations/vera/)
- - [Wink](/components/wink/)
+ - [Wink](/integrations/wink/)
- - [Fibaro](/components/fibaro/)
+ - [Fibaro](/integrations/fibaro/)
- - [SmartThings](/components/smartthings/)
+ - [SmartThings](/integrations/smartthings/)
 
 ## Controller Notes
 

source/_docs/z-wave/entities.markdown

@@ -147,7 +147,7 @@ The meaning of the `alarm_level` entity depends on the nature of the alarm senso
   - **254**: Deep sleep
   - **255**: Case open
 
-If your device has an `access_control` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](/components/binary_sensor.template/) to create one (here we've defined it as a door, but you can use [any relevant device class](/components/binary_sensor/#device-class):
+If your device has an `access_control` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](/integrations/binary_sensor.template/) to create one (here we've defined it as a door, but you can use [any relevant device class](/integrations/binary_sensor/#device-class):
 
 {% raw %}
 ```yaml
@@ -173,7 +173,7 @@ binary_sensor:
    - **254**: Deep sleep
    - **255**: Case open
 
-If your device has a `burglar` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](/components/binary_sensor.template/) to create one (here we've defined it as a motion sensor, but you can use [any relevant device class](/components/binary_sensor/#device-class):
+If your device has a `burglar` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](/integrations/binary_sensor.template/) to create one (here we've defined it as a motion sensor, but you can use [any relevant device class](/integrations/binary_sensor/#device-class):
 
 {% raw %}
 ```yaml

source/_includes/asides/component_navigation.html

@@ -10,7 +10,7 @@
 
   {%- assign file_parts = page.url | split: '/' | last | split: '.' -%}
   {%- assign imp_name = file_parts | first -%}
-  {%- assign imp_url = imp_name | prepend: '/components/' | append: '/' -%}
+  {%- assign imp_url = imp_name | prepend: '/integrations/' | append: '/' -%}
 
   <div class="section">
     <kb-alert-link integration="{{ imp_name }}"></kb-alert-link>
@@ -60,7 +60,7 @@
     <ul class='divided'>
     {%- for category in page.ha_category -%}
       <li>
-        <a href='/components/#{{ category | slugify }}'>{{ category }}</a>
+        <a href='/integrations/#{{ category | slugify }}'>{{ category }}</a>
       </li>
     {%- endfor -%}
     </ul>

source/_includes/custom/grid_item_left.html

@@ -2,49 +2,49 @@
 <hr>
 <p>Home Assistant will track the state of all the devices in your home, so you don't have to.</p>
 <div class='supported-brands clearfix'>
-  <a href='/components/ecobee/'>
+  <a href='/integrations/ecobee/'>
     <img src='/images/supported_brands/ecobee.png' alt="Ecobee" />
   </a>
-  <a href='/components/ifttt/'>
+  <a href='/integrations/ifttt/'>
     <img src='/images/supported_brands/ifttt.png' alt="IFTTT" />
   </a>
-  <a href='/components/light.hue/'>
+  <a href='/integrations/light.hue/'>
     <img src='/images/supported_brands/philips_hue.png' alt="Philips Hue" />
   </a>
-  <a href='/components/media_player.cast/'>
+  <a href='/integrations/media_player.cast/'>
     <img src='/images/supported_brands/google_cast.png' alt="Google Cast" />
   </a>
-  <a href='/components/mqtt/'>
+  <a href='/integrations/mqtt/'>
     <img src='/images/supported_brands/mqtt.png' alt="MQTT" />
   </a>
-  <a href='/components/switch.wemo/'>
+  <a href='/integrations/switch.wemo/'>
     <img src='/images/supported_brands/belkin_wemo.png' alt="Belkin WeMo" />
   </a>
-  <a href='/components/notify.pushbullet/'>
+  <a href='/integrations/notify.pushbullet/'>
     <img src='/images/supported_brands/pushbullet.png' alt="Pushbullet" />
   </a>
-  <a href='/components/media_player.kodi/'>
+  <a href='/integrations/media_player.kodi/'>
     <img src='/images/supported_brands/kodi.png' alt="Kodi" />
   </a>
-  <a href='/components/media_player.plex/'>
+  <a href='/integrations/media_player.plex/'>
     <img src='/images/supported_brands/plex.png' alt="Plex" />
   </a>
-  <a href='/components/tradfri/'>
+  <a href='/integrations/tradfri/'>
     <img src='/images/supported_brands/ikea.svg' width='165' alt="IKEA" />
   </a>
-  <a href='/components/vera/'>
+  <a href='/integrations/vera/'>
     <img src='/images/supported_brands/vera.png' alt="Vera" />
   </a>
-  <a href='/components/device_tracker.luci/'>
+  <a href='/integrations/device_tracker.luci/'>
     <img src='/images/supported_brands/openwrt.png' alt="OpenWRT" />
   </a>
-  <a href='/components/arduino/'>
+  <a href='/integrations/arduino/'>
     <img src='/images/supported_brands/arduino.png' alt="Arduino" />
   </a>
-  <!-- <a href='/components/wink/'>
+  <!-- <a href='/integrations/wink/'>
     <img src='/images/supported_brands/wink.png' alt="Wink" />
   </a> -->
 </div>
 
-<p class='pull-right'><a href='/components/'>Browse all &raquo;</a></p>
+<p class='pull-right'><a href='/integrations/'>Browse all &raquo;</a></p>
 

source/_includes/site/header.html

@@ -23,7 +23,7 @@
               </li>
             {% endcomment %}
             <li><a href="/getting-started/">Getting started</a></li>
-            <li><a href="/components/">Integrations</a></li>
+            <li><a href="/integrations/">Integrations</a></li>
             <li><a href="/docs/">Docs</a></li>
             <li><a href="/cookbook/">Examples</a></li>
             <li><a href="/blog/">Blog</a></li>

source/_integrations/abode.markdown

@@ -23,12 +23,12 @@ Please visit the [Abode website](https://goabode.com/) for further information a
 There is currently support for the following device types within Home Assistant:
 
 - **Alarm Control Panel**: Reports on the current alarm status and can be used to arm and disarm the system.
-- [**Binary Sensor**](/components/abode/#binary-sensor): Reports on `Quick Actions`, `Door Contacts`, `Connectivity` sensors (remotes, keypads, and status indicators), `Moisture` sensors, and `Motion` or `Occupancy` sensors.
+- [**Binary Sensor**](/integrations/abode/#binary-sensor): Reports on `Quick Actions`, `Door Contacts`, `Connectivity` sensors (remotes, keypads, and status indicators), `Moisture` sensors, and `Motion` or `Occupancy` sensors.
 - **Camera**: Reports on `Camera` devices and will download and show the latest captured still image.
 - **Cover**: Reports on `Secure Barriers` and can be used to open and close the cover.
 - **Lock**: Reports on `Door Locks` and can be used to lock and unlock the door.
-- [**Light**](/components/abode/#light): Reports on `Dimmer` lights and can be used to dim or turn the light on and off.
+- [**Light**](/integrations/abode/#light): Reports on `Dimmer` lights and can be used to dim or turn the light on and off.
-- [**Switch**](/components/abode/#switch): Reports on `Power Switch` devices and can be used to turn the power switch on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them.
+- [**Switch**](/integrations/abode/#switch): Reports on `Power Switch` devices and can be used to turn the power switch on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them.
 - **Sensor**: Reports on `Temperature`, `Humidity`, and `Light` sensors.
 
 ## Configuration
@@ -146,14 +146,14 @@ Trigger a quick action automation on your Abode system.
 
 This integration will add `Door Contacts`, `Connectivity` sensors (remotes, keypads, and status indicators), `Moisture` sensors, and `Motion` or `Occupancy` sensors.
 
-This integration will also list all Abode `Quick Actions` that are set up. You can trigger these quick actions by passing the `entity_id` of your quick action binary sensor to the [trigger_quick_action service](/components/abode/#trigger_quick_action).
+This integration will also list all Abode `Quick Actions` that are set up. You can trigger these quick actions by passing the `entity_id` of your quick action binary sensor to the [trigger_quick_action service](/integrations/abode/#trigger_quick_action).
 
 ### Light
 
-This integration will automatically add `Lights` configured in your Abode account. You can reclassify `Switches` to show up within Home Assistant as lights by listing the Abode device ID in your [configuration](/components/abode/#configuration).
+This integration will automatically add `Lights` configured in your Abode account. You can reclassify `Switches` to show up within Home Assistant as lights by listing the Abode device ID in your [configuration](/integrations/abode/#configuration).
 
 ### Switch
 
-This integration will automatically add `Power Switches` configured in your Abode account. You can reclassify switches to show up within Home Assistant as `Lights` by listing the Abode device ID in your [configuration](/components/abode/#configuration).
+This integration will automatically add `Power Switches` configured in your Abode account. You can reclassify switches to show up within Home Assistant as `Lights` by listing the Abode device ID in your [configuration](/integrations/abode/#configuration).
 
 This integration will also list all Abode `Automations` that are set up within the Abode system, allowing you to activate and deactivate the automations.

source/_integrations/actiontec.markdown

@@ -43,4 +43,4 @@ password:
   type: string
 {% endconfiguration %}
 
-See the [device tracker integration page](/components/device_tracker/) for instructions how to configure the people to be tracked.
+See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.

source/_integrations/ads.markdown

@@ -91,7 +91,7 @@ name:
   required: false
   type: string
 device_class:
-  description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
+  description: Sets the [class of the device](/integrations/binary_sensor/), changing the device state and icon that is displayed on the frontend.
   required: false
   type: string
 {% endconfiguration %}
@@ -239,6 +239,6 @@ name:
   type: string
 device_class:
   required: false
-  description: Sets the [class of the device](/components/cover/), changing the device state and icon that is displayed on the frontend.
+  description: Sets the [class of the device](/integrations/cover/), changing the device state and icon that is displayed on the frontend.
   type: device_class
 {% endconfiguration %}

source/_integrations/alarm_control_panel.ifttt.markdown

@@ -9,7 +9,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 integration. See the integrations documentation to set it up.
+This platform depends on the [IFTTT](/integrations/ifttt/) Home Assistant integration. See the integrations documentation to set it up.
 
 <div class='note'>
 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.

source/_integrations/alarm_control_panel.mqtt.markdown

@@ -114,11 +114,11 @@ payload_not_available:
   type: string
   default: offline
 json_attributes_topic:
-  description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in [MQTT sensor](/components/sensor.mqtt/#json-attributes-topic-configuration) documentation.
+  description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in [MQTT sensor](/integrations/sensor.mqtt/#json-attributes-topic-configuration) documentation.
   required: false
   type: string
 json_attributes_template:
-  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the JSON dictionary from messages received on the `json_attributes_topic`. Usage example can be found in [MQTT sensor](/components/sensor.mqtt/#json-attributes-template-configuration) documentation."
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the JSON dictionary from messages received on the `json_attributes_topic`. Usage example can be found in [MQTT sensor](/integrations/sensor.mqtt/#json-attributes-template-configuration) documentation."
   required: false
   type: template
 device:

source/_integrations/alarmdecoder.markdown

@@ -81,7 +81,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/alarmdecoder) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
+  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](/integrations/alarmdecoder) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
   required: false
   type: list
   keys:
@@ -90,7 +90,7 @@ zones:
       required: true
       type: string
     type:
-      description: "A type for the zone. Here you can find a list of [Device Classes](/components/binary_sensor/#device-class)."
+      description: "A type for the zone. Here you can find a list of [Device Classes](/integrations/binary_sensor/#device-class)."
       required: false
       default: opening
       type: string

source/_integrations/alexa.flash_briefings.markdown

@@ -19,7 +19,7 @@ Additionally, note that at the time of this writing, your Alexa skill endpoint *
 
   1. In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
   OR
-  2. Change your Home Assistant serving port to 443 this is done in the [`http`](/components/http/) section with the `server_port` entry in your `configuration.yaml` file
+  2. Change your Home Assistant serving port to 443 this is done in the [`http`](/integrations/http/) section with the `server_port` entry in your `configuration.yaml` file
 
 [blog-lets-encrypt]: /blog/2015/12/13/setup-encryption-using-lets-encrypt/
 
@@ -74,9 +74,9 @@ Please refer to the [Amazon documentation][flash-briefing-api-docs] for more inf
 [amazon-dev-console]: https://developer.amazon.com
 [flash-briefing-api]: https://developer.amazon.com/alexa-skills-kit/flash-briefing
 [flash-briefing-api-docs]: https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/flash-briefing-skill-api-feed-reference
-[large-icon]: /images/components/alexa/alexa-512x512.png
+[large-icon]: /images/integrations/alexa/alexa-512x512.png
-[small-icon]: /images/components/alexa/alexa-108x108.png
+[small-icon]: /images/integrations/alexa/alexa-108x108.png
 [templates]: /topics/templating/
 [zero-three-one]: /blog/2016/10/22/flash-briefing-updater-hacktoberfest/
 [alexa-settings-site]: http://alexa.amazon.com/
-[emulated-hue-component]: /components/emulated_hue/
+[emulated-hue-component]: /integrations/emulated_hue/

source/_integrations/alexa.intent.markdown

@@ -23,7 +23,7 @@ Additionally, note that at the time of this writing, your Alexa skill endpoint *
 
   1. In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
   OR
-  2. Change your Home Assistant serving port to 443 this is done in the [`http`](/components/http/) section with the `server_port` entry in your `configuration.yaml` file
+  2. Change your Home Assistant serving port to 443 this is done in the [`http`](/integrations/http/) section with the `server_port` entry in your `configuration.yaml` file
 
 [blog-lets-encrypt]: /blog/2015/12/13/setup-encryption-using-lets-encrypt/
 
@@ -83,7 +83,7 @@ This means that we can now ask Alexa things like:
 
 ## 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) integration.
+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`](/integrations/intent_script) integration.
 
 To enable Alexa, add the following entry to your `configuration.yaml` file:
 
@@ -113,7 +113,7 @@ First, we will configure Alexa. In the Amazon Interaction module add this to the
 Then create a custom slot type called `Scenes` listing every scene you want to control:
 
 <p class='img'>
-<img src='/images/components/alexa/scene_slot.png' />
+<img src='/images/integrations/alexa/scene_slot.png' />
 Custom slot type for scene support.
 </p>
 
@@ -122,7 +122,7 @@ The names must exactly match the scene names (minus underscores - Amazon discard
 In the new Alexa Skills Kit, you can also create synonyms for slot type values, which can be used in place of the base value in utterances. Synonyms will be replaced with their associated slot value in the intent request sent to the Alexa API endpoint, but only if there are not multiple synonym matches. Otherwise, the value of the synonym that was spoken will be used.
 
 <p class='img'>
-<img src='/images/components/alexa/scene_slot_synonyms.png' />
+<img src='/images/integrations/alexa/scene_slot_synonyms.png' />
 Custom slot values with synonyms.
 </p>
 
@@ -170,7 +170,7 @@ We can easily extend the above idea to work with scripts as well. As before, add
 Create a custom slot type called `Scripts` listing every script you want to run:
 
 <p class='img'>
-<img src='/images/components/alexa/script_slot.png' />
+<img src='/images/integrations/alexa/script_slot.png' />
 Custom slot type for script support.
 </p>
 
@@ -263,6 +263,6 @@ Alexa will now respond with a random phrase each time. You can use the include f
 
 
 [amazon-dev-console]: https://developer.amazon.com
-[large-icon]: /images/components/alexa/alexa-512x512.png
+[large-icon]: /images/integrations/alexa/alexa-512x512.png
-[small-icon]: /images/components/alexa/alexa-108x108.png
+[small-icon]: /images/integrations/alexa/alexa-108x108.png
 [templates]: /topics/templating/

source/_integrations/alexa.markdown

@@ -18,9 +18,9 @@ For Home Assistant Cloud Users, documentation can be found [here](https://www.na
 
 There are a few ways that you can use Amazon Alexa and Home Assistant together.
 
-- [Build custom commands to use](/components/alexa.intent/)
+- [Build custom commands to use](/integrations/alexa.intent/)
-- [Create a new Flash Briefing source](/components/alexa.flash_briefings/)
+- [Create a new Flash Briefing source](/integrations/alexa.flash_briefings/)
-- [Use the Smart Home API to control lights, etc](/components/alexa.smart_home/)
+- [Use the Smart Home API to control lights, etc](/integrations/alexa.smart_home/)
 - Alternative: use the [Emulated Hue integration][emulated-hue-component] to trick Alexa to thinking Home Assistant is a Philips Hue hub.
 
 ### Requirements
@@ -33,4 +33,4 @@ Manual setup the integration with Amazon Alexa needs several requirements
 - Smart Home API also needs your Home Assistant instance accessible from the Internet.
 
 [amazon-dev-console]: https://developer.amazon.com
-[emulated-hue-component]: /components/emulated_hue/
+[emulated-hue-component]: /integrations/emulated_hue/

source/_integrations/alexa.smart_home.markdown

@@ -18,7 +18,7 @@ limitations since everything looks like a light bulb.
 
 Amazon provides a Smart Home API for richer home automation control. It takes
 considerable effort to configure. The easy solution is to use
-[Home Assistant Cloud](/components/cloud/).
+[Home Assistant Cloud](/integrations/cloud/).
 
 However, config Amazon Alexa Smart Home Skill is not a easy job, you have to allow
 your Home Assistant accessible from Internet, and you need to create Amazon Developer
@@ -46,7 +46,7 @@ For Home Assistant Cloud Users, documentation can be found [here](https://www.na
 - Input `Skill name` as you like, select your skill's `Default language`.
 - Select `Smart Home` and `Provision your own`, then click `Create skill` button at top right corner.
 
-  <img src='/images/components/alexa/create_a_new_skill.png' alt='Screenshot: Create Smart Home skill'>
+  <img src='/images/integrations/alexa/create_a_new_skill.png' alt='Screenshot: Create Smart Home skill'>
 
 - In next screen, make sure *v3* is selected in `Payload version`.
 - Now, you have created a skeleton of Smart Home skill. Next step we will do some "real" developer work. You can keep Alex Developer Console opened, we need change the skill configuration later.
@@ -75,7 +75,7 @@ First thing you need to do after sing in [AWS console](https://console.aws.amazo
 - Click `Roles` in the left panel, then click `Create role`, select `AWS Service` -> `Lambda` in the first page of the wizard, then click `Next: Permissions`
 - Select `AWSLambdaBasicExecutionRole` policy, then click `Next: Tags`. (Tips: you can use the search box to filter the policy)
 
-  <img src='/images/components/alexa/create_iam_role_attach_permission.png' alt='Screenshot: Attach permission policy to IAM role'>
+  <img src='/images/integrations/alexa/create_iam_role_attach_permission.png' alt='Screenshot: Attach permission policy to IAM role'>
 
 - You can skip `Add tags` page, click `Next: Review`.
 - Give your new role a name, such as `AWSLambdaBasicExecutionRole-SmartHome`, then click `Create role` button. You should be able to find your new role in the roles list now.
@@ -103,7 +103,7 @@ Next you need create a Lambda function.
   * NOT_VERIFY_SSL *(optional)*: you can set it to *True* to ignore the SSL issue, if you don't have a valid SSL certificate or you are using self-signed certificate.
   * DEBUG *(optional)*: set to *True* to log the debug message
   * LONG_LIVED_ACCESS_TOKEN *(optional, not recommend)*: you will connect your Alexa Smart Home skill with your Home Assistant user account in the later steps, so that you don't need to use long-lived access token here. However, the access token you got from login flow is only valid for 30 minutes. It will be hard for you to test lambda function with the access token in test data. So for your convinces, you can remove the access token from the test data, [generate a long-lived access token][generate-long-lived-access-token] put here, then the function will fall back to read token from environment variables. (tips: You did not enable the security storage for your environment variables, so your token saved here is not that safe. You should only use it for debugging and testing purpose. You should remove and delete the long-lived access token after you finish the debugging.) 
-  <img src='/images/components/alexa/lambda_function_env_var.png' alt='Screenshot: Environment variables in Lambda function'>
+  <img src='/images/integrations/alexa/lambda_function_env_var.png' alt='Screenshot: Environment variables in Lambda function'>
 
 - Now scroll up to the top, click `Save` button.
 - You need copy the ARN displayed in the top of the page, which is the identify of this Lambda function. You will need this ARN to continue Alexa Smart Home skill configuration later.
@@ -178,7 +178,7 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom
   * `Scope`: input `smart_home`, Home Assistant is not using it yet, we may use it in the future when we allow more fine-grained access control.
 - You can leave `Domain List` and `Default Access Token Expiration Time` as empty.
 
-  <img src='/images/components/alexa/account_linking.png' alt='Screenshot: Account Linking'>
+  <img src='/images/integrations/alexa/account_linking.png' alt='Screenshot: Account Linking'>
 
 - Click `Save` button in the top right corner.
 - Next, you will use Alexa Mobile App or [Alexa web-based app](#alexa-web-based-app) to link your account.
@@ -236,5 +236,5 @@ The following is a list of regions and the corresponding URL for the web-based A
 * Spain: <https://alexa.amazon.es>
 
 [alexa-dev-console]: https://developer.amazon.com/alexa/console/ask
-[emulated-hue-component]: /components/emulated_hue/
+[emulated-hue-component]: /integrations/emulated_hue/
 [generate-long-lived-access-token]: https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token

source/_integrations/amcrest.markdown

@@ -162,7 +162,7 @@ your camera's configuration manager. If you defined the *stream_source* to
 Newer Amcrest firmware may not work, then **rtsp** is recommended instead.
 
 **Note:** If you set the `stream_source` option to `rtsp`,
-make sure to follow the steps mentioned at [FFMPEG](/components/ffmpeg/)
+make sure to follow the steps mentioned at [FFMPEG](/integrations/ffmpeg/)
 documentation to install the `ffmpeg`.
 
 ## Services

source/_integrations/android_ip_webcam.markdown

@@ -185,7 +185,7 @@ binary_sensor:
 
 ## Camera
 
-The `android_ip_webcam` integration adds a camera by default if you choose not to use the integration but still want to see the video feed then the [`mjpeg` camera](/components/mjpeg) platform can be used.
+The `android_ip_webcam` integration adds a camera by default if you choose not to use the integration but still want to see the video feed then the [`mjpeg` camera](/integrations/mjpeg) platform can be used.
 
 ## Configuration
 

source/_integrations/api.markdown

@@ -8,7 +8,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` integration](/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](/integrations/http/).
 
 <div class='note warning'>