+`interface` options are for resinos based installation. On other system you can set it to `""`, for listen on every interface. +
+ ```json { "defaults": ["8.8.8.8", "8.8.4.4"], @@ -19,7 +23,8 @@ Setup and manage a [Dnsmasq](http://thekelleys.org.uk/dnsmasq/doc.html) DNS serv ], "hosts": [ {"host": "home.mydomain.io", "ip": "192.168.1.10"} - ] + ], + "interface": "eth1" } ``` @@ -28,3 +33,4 @@ Configuration variables: - **defaults** (*Required*): A list of DNS servers to forward default requests to. - **forwards** (*Optional*): A list of domains that will forward to a specific server. - **hosts** (*Optional*): A list of hosts to resolve statically. +- **interface** (*Optional*): If an interface is set, it listens only on this interface. Needs to be set for ResinOS. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection. diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown index 123e975e97..297cbb8fd9 100644 --- a/source/_addons/duckdns.markdown +++ b/source/_addons/duckdns.markdown @@ -10,14 +10,12 @@ footer: true featured: true --- -[Duck DNS](https://www.duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. This add-on includes support for Let's Encrypt and will automatically create and renew your certificates. +[Duck DNS](https://duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. This add-on includes support for Let's Encrypt and will automatically create and renew your certificates. ```json { "lets_encrypt": { - "accept_terms": true, - "certfile": "fullchain.pem", - "keyfile": "privkey.pem" + "accept_terms": true }, "token": "sdfj-2131023-dslfjsd-12321", "domains": ["my-domain.duckdns.org"] @@ -26,10 +24,10 @@ featured: true Configuration variables: -- **lets_encrypt.accept_terms** (*Optional*): If you accept the [Let's Encrypt Subscriber Agreement][le], it will generate and update Let's Encrypt certificates for your DuckDNS domain. - **token** (*Required*): Your Duck DNS API key. - **domains** (*Required*): A list of domains to update DNS. -- **seconds** (*Required*): Seconds between updates to Duck DNS. +- **seconds** (*Optional*): Seconds between updates to Duck DNS. +- **lets_encrypt.accept_terms** (*Optional*): If you accept the [Let's Encrypt Subscriber Agreement][le], it will generate & update Let's Enrypt certificates for your DuckDNS domain. [le]: https://letsencrypt.org/repository/ @@ -51,5 +49,3 @@ If you use a port other than `8123` or an SSL proxy, change the port number acco You'll need to forward the port you listed in your configuration (8123 in the example above) on your router to your Home Assistant system. You can find guides on how to do this on [Port Forward](https://portforward.com/) - noting that you'll only need to forward the TCP port. Ensure that you allocate the Home Assistant system a fixed IP on your network before you configure port forwarding. You can do this either on the computer itself (see the [install guide](/hassio/installation/) or via a static lease on your router. - -Restart Home Assistant for the configured changes to take effect. When you access the Home Assistant frontend you will now need to use `https`, even when accessing local instances, for example at `https://192.168.0.1:8123`. diff --git a/source/_addons/google_assistant.markdown b/source/_addons/google_assistant.markdown index f48415638e..ac0765bc51 100644 --- a/source/_addons/google_assistant.markdown +++ b/source/_addons/google_assistant.markdown @@ -11,7 +11,7 @@ featured: true ---- 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](https://home-assistant.io/components/google_assistant/).
[Google Assistant][GoogleAssistant] is an AI-powered voice assistant that runs on the Raspberry Pi and x86 platforms and interact via the [DialogFlow][comp] integration with Home-Assistant. You can also use [Google Actions][GoogleActions] to extend its functionality. @@ -66,7 +66,7 @@ Configuration example that uses the USB microphone and the built-in headset audi Configuration variables: -- **mic**: This is the hardware address of your microphone. Look at the add-on output +- **mic**: This is the hardware address of your microphone. Look at the add-on output - **speaker**: This is the hardware address of your speakers. Look at the add-on output ### {% linkable_title Home Assistant configuration %} diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown index 6a92bbff81..8cf3c3b9b3 100644 --- a/source/_addons/homematic.markdown +++ b/source/_addons/homematic.markdown @@ -57,7 +57,7 @@ Use the following configuration in Home Assistant to use it: ```yaml homematic: interfaces: - rf: + BidCoS-RF: host: core-homematic port: 2001 ``` diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown index 0ac8d01994..fe3894e6f8 100644 --- a/source/_addons/lets_encrypt.markdown +++ b/source/_addons/lets_encrypt.markdown @@ -2,7 +2,7 @@ layout: page title: "Let's Encrypt" description: "Automatically manage your SSL certificate using Let's Encrypt." -date: 2018-04-18 10:55 +date: 2017-04-30 13:28 sidebar: true comments: false sharing: true @@ -14,7 +14,7 @@ featured: false You should not use this if you are also using the [DuckDNS add-on]. The DuckDNS add-on has integrated Let's Encrypt support. -Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This addon will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration. This add-on uses port 80 to verify the certificate request. You will need to stop all other add-ons that also use this port. +Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This addon will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration. ```json { @@ -41,24 +41,4 @@ http: If you use another port such as `8123` or an SSL proxy, change the port number. -## {% linkable_title Enabling auto-renewals %} - -Out of the box, the add-on will not automatically renew your certificate. In fact, it only starts, tries to get/renew your certificte, and then stops. It's up to you to manually start it again whenever your certificate comes close to expiry. - -However, you can automate this process using Home Assistant. - -Use this in your `automations.yaml` to attempt certificate renewal each day at midnight: - -```yaml -- id: letsencrypt-renewal - alias: "Let's Encrypt Renewal" - trigger: - - platform: time - at: '00:00:00' - action: - - service: hassio.addon_restart - data: - addon: core_letsencrypt -``` - [DuckDNS add-on]: /addons/duckdns/ diff --git a/source/_addons/mariadb.markdown b/source/_addons/mariadb.markdown index 66df1440c6..673857de06 100644 --- a/source/_addons/mariadb.markdown +++ b/source/_addons/mariadb.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -Set up a [mariadb](https://mariadb.org/) SQL server. It supports multiple databases, users, and permission settings. If you want to only connect from inside Home Assistant use `core-mariadb` as the host address. +Set up a [mariadb](https://mariadb.org/) SQL server. It supports multiple databases, users, and permission settings. If you want to only connect from inside home assistant use `core-mariadb` as the host address. ```json { diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown index f143d9ac34..de3df29894 100644 --- a/source/_addons/mosquitto.markdown +++ b/source/_addons/mosquitto.markdown @@ -43,7 +43,7 @@ Configuration variables: ### {% linkable_title Home Assistant configuration %} -To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), add the following entry to the `configuration.yaml` file. +To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own) add the following entry to the `configuration.yaml` file. ```yaml # Example configuration.yaml entry @@ -59,20 +59,3 @@ mqtt: username: YOUR_USERNAME password: YOUR_PASSWORD ``` - -### {% linkable_title Listening simultaneously on SSL/TLS (8883) and insecure (1883) ports %} - -1. Configure SSL/TLS as normal. -2. Set `customize` flag to `true` in your configuration. -3. Create a file in `/share/mosquitto` named `insecure.conf` with the following contents: - -```text -listener 1883 -protocol mqtt -``` - -4. Restart MQTT - --It's recommened that you only open your firewall to the SSL/TLS port (8883) and only use the insecure port (1883) for local devices. -
diff --git a/source/_addons/nginx_proxy.markdown b/source/_addons/nginx_proxy.markdown index e1d8a5f01c..8fd22956e7 100644 --- a/source/_addons/nginx_proxy.markdown +++ b/source/_addons/nginx_proxy.markdown @@ -11,29 +11,17 @@ footer: true Setup an SSL proxy with NGINX and redirect port 80 to 443. Make sure you have generated a certificate before you start this add-on. -In the `http` section of the `configuration.yaml` file remove `ssl_certificate` and `ssl_key` and don't enter the port in the `base_url` to avoid an HTTP 502 error. +In the `http` section of the `configuration.yaml` file remove `ssl_certificate` and `ssl_key` and don't enter the port in the `base_url` to avoid a HTTP 502 error. ```json { - "domain": "home.example.com", - "certfile": "fullchain.pem", - "keyfile": "privkey.pem", - "hsts": "max-age=31536000; includeSubDomains", - "customize": { - "active": false, - "default": "nginx_proxy_default*.conf", - "servers": "nginx_proxy/*.conf" - } + "domain": "home.example.com" } ``` Configuration variables: - **domain** (*Required*): Domain they will proxy run with it. -- **certfile** (*Required*): Certificate file to use in the /ssl dir. -- **keyfile** (*Required*): Private key file to use in the /ssl dir. -- **hsts** (*Optional*): Value for the [`Strict-Transport-Security`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) HTTP header to send. If empty or `null`, the header is not sent. -- **customize** (*Optional*): If true, additional NGINX configuration files for the default server and additional servers are read from files in the /share dir specified by the `default` and `servers` variables.
It is possible to deactivate port 80 if you need this for things like `emulate_hue`. Remove the host port from Network option of this add-on.
diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown
index 9d0f18923f..33e573ec37 100644
--- a/source/_addons/samba.markdown
+++ b/source/_addons/samba.markdown
@@ -22,7 +22,7 @@ This addon allows you to set up a [Samba](https://samba.org/) server to access h
"addons": true,
"share": true,
"backup": true,
- "ssl": false
+ "ssl": false,
},
"username": "",
"password": "",
@@ -32,10 +32,10 @@ This addon allows you to set up a [Samba](https://samba.org/) server to access h
Configuration variables:
-- **name** (*Optional*): Set netbios name of Hass.io device. Default is `hassio`.
-- **workgroup** (*Optional*): Set network workgroup name. Default is `WORKGROUP`.
-- **guest** (*Optional*): Allow login without a username or password. Default is `true`.
-- **map** (*Optional*): Control which folders will be exposed. `config` shares the Home Assistant configuration folder. `addons` shares the local custom repository. `share` shares a folder that can be accessed by add-ons and Home Assistant. `backup` shares access to snapshot files. `ssl` shares certificate storage. Be careful with the `ssl` option! Defaults are all set to `true`, except for `ssl`.
-- **username** (*Optional*): Username for logging in if guest login is not used.
+- **name** (*Optional*): default `hassio`. Set NetBIOS name of hassio device.
+- **workgroup** (*Optional*): default `WORKGROUP`. Set network workgroup.
+- **guest** (*Optional*): Allow login without a username or password. Defaults to `true`.
+- **map** (*Optional*): Control which folder will be exposed. `config` is for Home Assistant configuration folder. `addons` for a local custom repository. `share` is a folder that can access from add-ons and Home Assistant too. `backup` for access to snapshot files. `ssl` for certificate storage, be careful with this option! Defaults all to `true`, except for `ssl`.
+- **username** (*Optional*): The username for logging in if guest login is not used.
- **password** (*Optional*): Password for `username`. An empty password is not supported.
-- **interface** (*Optional*): Interface that will start the share. Normally this is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
+- **interface** (*Optional*): Interface on that will start the share. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
diff --git a/source/_addons/snips.markdown b/source/_addons/snips.markdown
index 851afd8e7d..954d04d613 100644
--- a/source/_addons/snips.markdown
+++ b/source/_addons/snips.markdown
@@ -2,39 +2,51 @@
layout: page
title: "Snips.ai"
description: "Enhance your Hass.io installation with a local voice assistant."
-date: 2018-05-02 13:28
+date: 2017-04-30 13:28
sidebar: true
comments: false
sharing: true
footer: true
---
-[Snips.ai](https://snips.ai/) is an AI-powered voice assistant that runs on the Raspberry Pi 3 and x86 platforms. It runs on-device and is Private by Design.
+[Snips.ai] is an AI-powered voice assistant that runs on the Raspberry Pi 3 and x86 platforms. It runs on-device and is Private by Design.
-The Snips add-on depends on the Mosquitto add on to bridge to Home Assistant, so make sure that is installed.
+To get started, follow [their tutorial] to create an assistant and download the training data.
-HomeAssistant 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).
+Now install and activate the [Samba] add-on so you can upload your training data. Connect to the "share" Samba share and copy your training data over. Name the file `assistant.zip`.
-The Snips addon 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 if that component is enabled.
+Now it's time to start Snips for the first time. When the Snips add-on starts, it will output your audio devices:
-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:
-
-```
-Turn on kitchen light
-Open garage door
-What is on my shopping list
+```text
+**** List of PLAYBACK Hardware Devices ****
+card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
+ Subdevices: 8/8
+ Subdevice #0: subdevice #0
+ Subdevice #1: subdevice #1
+ Subdevice #2: subdevice #2
+ Subdevice #3: subdevice #3
+ Subdevice #4: subdevice #4
+ Subdevice #5: subdevice #5
+ Subdevice #6: subdevice #6
+ Subdevice #7: subdevice #7
+card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
+ Subdevices: 1/1
+ Subdevice #0: subdevice #0
```
-To get started creating your own configuration, follow [their tutorial](https://snips.gitbook.io/documentation/console) to create an assistant and download the training data. You can also add the HomeAssistant Skill to your assistant to enable the built-in intents, and add or create your own intents to do more complex tasks.
+You need to use this information to point the add-on at the right speakers and microphone. The information describes different cards and devices. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port. In the example above, the USB microphone showed up as card 1 - device 0.
-Now install and activate the [Samba](/addons/samba/) add-on so you can upload your training data. Connect to the "share" Samba share and copy your assistant over. Name the file `assistant.zip` or whatever you have configured in the configuration options.
+Find the microphone and speakers that you want to use and note down their device and card number. We will need that to configure the add-on options `mic` (microphone to use) and `speaker` (speaker to use). The format for these options is `
-`alarm_arm_custom_bypass` and `alarm_trigger`, while available in the services list in Home Assistant, are not currently implemented in the Alarm Decoder platform.
-
-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.
-
-It is strongly discouraged to use this platform when you don't use encryption; otherwise, your API password will be send unprotected through the IFTTT Webhooks. It is adviced to [setup encryption using Let's Encrypt](https://home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/).
-
Currently, you must have Home Sharing enabled for this to work. Support for pairing Home Assistant with your device will be supported in a later release.
@@ -92,7 +92,7 @@ then device authentication is required. Press the icon in the upper left corner
A word of caution: The Arduino boards are not storing states. This means that with every initialization the pins are set to off/low.
diff --git a/source/_components/arlo.markdown b/source/_components/arlo.markdown
index e82ade68d1..479a771329 100644
--- a/source/_components/arlo.markdown
+++ b/source/_components/arlo.markdown
@@ -15,27 +15,19 @@ ha_iot_class: "Cloud Polling"
The `arlo` implementation allows you to integrate your [Arlo](https://arlo.netgear.com/) devices in Home Assistant.
-## {% linkable_title Configuration %}
-
To enable device linked in your [Arlo](https://arlo.netgear.com/) account, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
arlo:
- username: YOUR_USERNAME
- password: YOUR_PASSWORD
+ username: you@example.com
+ password: secret
```
-{% configuration %}
-username:
- description: The username for accessing your Arlo account.
- required: true
- type: string
-password:
- description: The password for accessing your Arlo account.
- required: true
- type: string
-{% endconfiguration %}
+Configuration variables:
+
+- **username** (*Required*): The username for accessing your Arlo account.
+- **password** (*Required*): The password for accessing your Arlo account.
It is recommended to create a dedicated user on Arlo website to be used within Home Assistant and then share your Arlo cameras.
diff --git a/source/_components/asterisk_mbox.markdown b/source/_components/asterisk_mbox.markdown
index 2361dfe0c9..d0d7ba72fe 100644
--- a/source/_components/asterisk_mbox.markdown
+++ b/source/_components/asterisk_mbox.markdown
@@ -1,32 +1,31 @@
---
layout: page
title: "Asterisk Voicemail"
-description: "Instructions on how to integrate your existing Asterisk voicemail within Home Assistant."
+description: "Instructions how to integrate your existing Asterisk voicemail within Home Assistant."
date: 2017-06-30 18:30
sidebar: true
comments: false
sharing: true
footer: true
-logo: asterisk.png
ha_category: Other
ha_version: 0.51
ha_iot_class: "Local Push"
---
-The `asterisk_mbox `Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
+The Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
To enable the component, a configuration is required in both Home Assistant as well as on the Asterisk server.
-First follow the [Asterisk PBX configuration guide](/docs/asterisk_mbox/) to setup the necessary server on the Asterisk PBX server (this is needed even if Asterisk and Home Assistant are running on the same server)
+First follow the [Asterisk PBX configuration guide](/docs/asterisk_mbox) to setup the necessary server on the Asterisk PBX server (this is needed even if Asterisk and Home Assistant are running on the same server)
Once that is complete, add the following entry `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
asterisk_mbox:
- password: ASTERISK_PBX_PASSWORD
- host: ASTERISK_PBX_SERVER_IP_ADDRESS
- port: ASTERISK_PBX_SERVER_PORT
+ password: ASTERISK_PBX_PASSWORD
+ host: ASTERISK_PBX_SERVER_IP_ADDRESS
+ port: ASTERISK_PBX_SERVER_PORT
```
This will add a new 'Mailbox' side-panel, as well as a sensor to indicate # of messages available.
diff --git a/source/_components/august.markdown b/source/_components/august.markdown
deleted file mode 100644
index 818002e14c..0000000000
--- a/source/_components/august.markdown
+++ /dev/null
@@ -1,56 +0,0 @@
----
-layout: page
-title: "August"
-description: "Instructions on how to integrate your August devices into Home Assistant."
-date: 2018-02-17 22:00
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: august.png
-ha_category: Hub
-ha_release: "0.64"
-ha_iot_class: "Cloud Polling"
----
-
-The `august` component allows you to integrate your [August](http://august.com) devices in Home Assistant. Currently this component supports August Lock and Doorbell.
-
-
-August Lock 2nd Gen will need either August Connect or Doorbell to connect to Home Assistant.
-
-Select `apple_tv` as domain, `apple_tv_authenticate` as service and enter `{"entity_id": "XXX"}` into "Service Data", but replace XXX with the entity id of your device (e.g., `media_player.apple_tv`). Press the button and hopefully you are presented with an input dialog asking for a pin code:
+Select `apple_tv` as domain, `apple_tv_authenticate` as service and enter `{"entity_id": "XXX"}` into "Service Data", but replace XXX with the entity id of your device (e.g. `media_player.apple_tv`). Press the button and hopefully you are presented with an input dialog asking for a pin code:
@@ -143,3 +143,4 @@ To play media on an Apple TV with device authentication enabled (e.g., ATV4 with
### {% linkable_title Service `apple_tv_scan` %}
Scans the local network for Apple TVs. All found devices are presented as a persistent notification.
+
diff --git a/source/_components/arduino.markdown b/source/_components/arduino.markdown
index ca16dd32b7..5105f19c4c 100644
--- a/source/_components/arduino.markdown
+++ b/source/_components/arduino.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Arduino"
-description: "Instructions on how to setup an Arduino boards within Home Assistant."
+description: "Instructions how to setup an Arduino boards within Home Assistant."
date: 2015-06-27 10:28
sidebar: true
comments: false
@@ -43,7 +43,7 @@ The exact number can be determined with the command shown below.
$ ls /dev/ttyACM*
```
-If that's not working, check your `dmesg` or `journalctl -f` output. Keep in mind that Arduino clones are often using a different name for the port (e.g., `/dev/ttyUSB*`).
+If that's not working, check your `dmesg` or `journalctl -f` output. Keep in mind that Arduino clones are often using a different name for the port (e.g. `/dev/ttyUSB*`).
-In order for the sensors to work the hikvision user must have the 'Remote: Notify Surveillance Center/Trigger Alarm Output' permission which can be enabled from the user management section of the web interface. Also the 'WEB Authentication' needs to be set to 'digest/basic' in the security/authentication section. -
+The platform will automatically add all sensors to Home Assistant that are configured within the camera/nvr interface to "Notify the surveillance center" as a trigger. If you would like to hide a sensor type you can do so by either unchecking "Notify the surveillance center" in the camera configuration or by using the "ignored" customize option detailed below. For example, if you configure a camera with the name "Front Porch" that has motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant: -```text +``` binary_sensor.front_porch_motion binary_sensor.front_port_line_crossing ``` -When used with a NVR device the sensors will be appended with the channel number they represent. For example, if you configure an NVR with the name "Home" that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant: +When used with a NVR device the sensors will be appended with the channel number they represent. For example, if you configure an NVR with the name "Home" that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant: -```text +``` binary_sensor.home_motion_1 binary_sensor.home_motion_2 binary_sensor.home_line_crossing_1 @@ -38,37 +34,35 @@ binary_sensor.home_line_crossing_2 ``` This platform should work with all Hikvision cameras and nvrs, and has been confirmed to work with the following models: - - DS-2CD3132-I - DS-2CD2232-I5 - DS-2CD2032-I - DS-2CD2042WD-I - DS-2CD2142FWD-I -To enable this sensor, the following lines are required in your `configuration.yaml` file: +To enable this sensor, the following lines are required in your `configuration.yaml`: ```yaml binary_sensor: - - platform: hikvision - host: IP_ADDRESS - username: user - password: pass + platform: hikvision + host: IP_ADDRESS + username: user + password: pass ``` Configuration options for a Hikvision Sensor: -- **host** (*Required*): The IP address of the camera you would like to connect to. -- **username** (*Required*): The username to authenticate with. -- **password** (*Required*): The password to authenticate with. - **name** (*Optional*): The name you'd like to give the camera in Home Assistant, defaults to name defined in the camera. +- **host** (*Required*): The IP address of the camera you would like to connect to. - **port** (*Optional*): The port to connect to the camera on, defaults to 80. - **ssl** (*Optional*): True if you want to connect with https. Be sure to set the port also. +- **username** (*Required*): The username to authenticate with. +- **password** (*Required*): The password to authenticate with. - **customize** (*Optional*): This attribute contains sensor-specific override values. Only sensor name needs defined: - **ignored** (*Optional*): Ignore this sensor completely. It won't be shown in the Web Interface and no events are generated for it. - **delay** (*Optional*): Specify the delay to wait after a sensor event ends before notifying Home Assistant. This is useful to catch multiple quick trips in one window without the state toggling on and off. The default delay is 5 seconds. Supported sensor/event types are: - - Motion - Line Crossing - Field Detection @@ -86,36 +80,37 @@ Supported sensor/event types are: - Face Detection - Scene Change Detection + Example of a configuration in your `configuration.yaml` that utilizes the customize options for a camera: ```yaml binary_sensor: - - platform: hikvision - host: 192.168.X.X - port: 80 - ssl: False - username: user - password: pass - customize: - motion: - delay: 30 - line_crossing: - ignored: True + platform: hikvision + host: 192.168.X.X + port: 80 + ssl: False + username: user + password: pass + customize: + motion: + delay: 30 + line_crossing: + ignored: True ``` Example of a configuration in your `configuration.yaml` that utilizes the customize options for a nvr: ```yaml binary_sensor: - - platform: hikvision - host: 192.168.X.X - port: 80 - ssl: False - username: user - password: pass - customize: - motion_1: - delay: 30 - field_detection_2: - ignored: True + platform: hikvision + host: 192.168.X.X + port: 80 + ssl: False + username: user + password: pass + customize: + motion_1: + delay: 30 + field_detection_2: + ignored: True ``` diff --git a/source/_components/binary_sensor.hive.markdown b/source/_components/binary_sensor.hive.markdown index 49486d62d7..ef695f4601 100644 --- a/source/_components/binary_sensor.hive.markdown +++ b/source/_components/binary_sensor.hive.markdown @@ -14,12 +14,11 @@ ha_iot_class: "Cloud Polling" --- -The `hive` binary sensor component integrates your Hive sensors into Home Assistant. +The 'hive' binary sensor component integrates your Hive sensors into Home Assistant. -The platform supports the following Hive products: - -- Hive Window or Door Sensor -- Hive Motion Sensor +The Hive sensor component supports the following Hive products: +- **Hive Window or Door Sensor** +- **Hive Motion Sensor**diff --git a/source/_components/binary_sensor.homematic.markdown b/source/_components/binary_sensor.homematic.markdown index 5155aedeea..37140c8433 100644 --- a/source/_components/binary_sensor.homematic.markdown +++ b/source/_components/binary_sensor.homematic.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Homematic Binary Sensor" -description: "Instructions on how to integrate binary Homematic sensors within Home Assistant." +description: "Instructions how to integrate binary Homematic sensors within Home Assistant." date: 2016-06-28 08:30 sidebar: true comments: false diff --git a/source/_components/binary_sensor.http.markdown b/source/_components/binary_sensor.http.markdown index c2442aa881..aaddf8a725 100644 --- a/source/_components/binary_sensor.http.markdown +++ b/source/_components/binary_sensor.http.markdown @@ -1,7 +1,7 @@ --- layout: page title: "HTTP Binary Sensor" -description: "Instructions on how to integrate HTTP binary sensors within Home Assistant." +description: "Instructions how to integrate HTTP binary sensors within Home Assistant." date: 2016-02-05 12:15 sidebar: true comments: false diff --git a/source/_components/binary_sensor.ihc.markdown b/source/_components/binary_sensor.ihc.markdown index da5aac7615..5a3d7769de 100644 --- a/source/_components/binary_sensor.ihc.markdown +++ b/source/_components/binary_sensor.ihc.markdown @@ -1,7 +1,7 @@ --- layout: page title: "IHC Binary Sensor" -description: "Instructions on how to integrate IHC Binary Sensors within Home Assistant." +description: "Instructions how to integrate IHC Binary Sensors within Home Assistant." date: 2017-11-27 13:35 sidebar: true comments: false diff --git a/source/_components/binary_sensor.insteon_plm.markdown b/source/_components/binary_sensor.insteon_plm.markdown index d06c324a44..bd685df7c2 100644 --- a/source/_components/binary_sensor.insteon_plm.markdown +++ b/source/_components/binary_sensor.insteon_plm.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon PLM Binary Sensor" -description: "Instructions on how to setup the Insteon PLM binary sensors locally within Home Assistant." +description: "Instructions how to setup the Insteon PLM switches locally within Home Assistant." date: 2017-02-19 17:00 sidebar: true comments: false diff --git a/source/_components/binary_sensor.isy994.markdown b/source/_components/binary_sensor.isy994.markdown index 2cb7345d0e..1318ef67d1 100644 --- a/source/_components/binary_sensor.isy994.markdown +++ b/source/_components/binary_sensor.isy994.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ISY994 Binary Sensor" -description: "Instructions on how to integrate ISY994 binary sensors into Home Assistant." +description: "Instructions how to integrate ISY994 binary sensors into Home Assistant." date: 2016-09-03 23:00 sidebar: true comments: false diff --git a/source/_components/binary_sensor.knx.markdown b/source/_components/binary_sensor.knx.markdown index d51c9effbb..73c747601a 100644 --- a/source/_components/binary_sensor.knx.markdown +++ b/source/_components/binary_sensor.knx.markdown @@ -1,7 +1,7 @@ --- layout: page title: "KNX Binary Sensor" -description: "Instructions on how to setup the KNX binary sensors within Home Assistant." +description: "Instructions how to setup the KNX binary sensors within Home Assistant." date: 2016-07-13 07:00 sidebar: true comments: false @@ -25,16 +25,14 @@ binary_sensor: address: '6/0/2' device_class: 'motion' #significant_bit: 2 - #reset_after: 100 ``` Configuration variables: - **name** (*Optional*): A name for this device used within Home Assistant. - **address**: KNX group address of the binary sensor. -- **device_class** (Optional): HASS device class e.g., "motion". +- **device_class** (Optional): HASS device class e.g. "motion". - **significant_bit** (Optional): Specify which significant bit of the KNX value should be used. Default is 1. -- **reset_after** (Optional): Reset back to OFF state after specified milliseconds. You can also attach actions to binary sensors (e.g., to switch on a light when a switch was pressed). In this example, one light is switched on when the button was pressed once and two others when the button was pressed a second time. diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown index fe8f4a5107..781f4f4557 100644 --- a/source/_components/binary_sensor.markdown +++ b/source/_components/binary_sensor.markdown @@ -11,8 +11,6 @@ footer: true Binary sensors gather information about the state of devices which have a "digital" return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: **0/off/low/closed/false** and **1/on/high/open/true**. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality. -### {% linkable_title Device Class %} - The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors: - **None**: Generic on/off. This is the default and doesn't need to be set. @@ -24,7 +22,6 @@ The way these sensors are displayed in the frontend can be modified in the [cust - **gas**: `On` means gas detected, `Off` means no gas (clear) - **heat**: `On` means hot, `Off` means normal - **light**: `On` means light detected, `Off` means no light -- **lock**: `On` means open (unlocked), `Off` means closed (locked) - **moisture**: `On` means moisture detected (wet), `Off` means no moisture (dry) - **motion**: `On` means motion detected, `Off` means no motion (clear) - **moving**: `On` means moving, `Off` means not moving (stopped) @@ -40,9 +37,4 @@ The way these sensors are displayed in the frontend can be modified in the [cust - **vibration**: `On` means vibration detected, `Off` means no vibration (clear) - **window**: `On` means open, `Off` means closed -For analog sensors please check the [component overview](/components/#sensor). - -
-
-Example of various device classes icons in `On` and `Off` state.
-
-If you use a `#` sign for `search` then wrap the whole search term in quotes. Otherwise everything following the hash sign would be considered a YAML comment. -
+**Note**: If you use a `#` sign for `search` then wrap the whole search term in quotes. Otherwise everything following the hash sign would be considered a YAML comment. + ### {% linkable_title Sensor attributes %} - **offset_reached**: If set in the event title and parsed out will be `on`/`off` once the offset in the title in minutes is reached. So the title `Very important meeting #Important !!-10` would trigger this attribute to be `on` 10 minutes before the event starts. + - **all_day**: `True`/`False` if this is an all day event. Will be `False` if there is no event found. + - **message**: The event title with the `search` and `offset` values extracted. So in the above example for **offset_reached** the **message** would be set to `Very important meeting` + - **description**: The event description. + - **location**: The event Location. + - **start_time**: Start time of event. + - **end_time**: End time of event. diff --git a/source/_components/calendar.markdown b/source/_components/calendar.markdown index 4b69b5e6fe..f18e94902c 100644 --- a/source/_components/calendar.markdown +++ b/source/_components/calendar.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Calendar" -description: "Instructions on how to integrate calendars within Home Assistant." +description: "Instructions how to integrate calendars within Home Assistant." date: 2016-11-19 08:36 sidebar: true comments: false diff --git a/source/_components/calendar.todoist.markdown b/source/_components/calendar.todoist.markdown index c416ddb50d..00bdca07f7 100644 --- a/source/_components/calendar.todoist.markdown +++ b/source/_components/calendar.todoist.markdown @@ -63,7 +63,7 @@ calendar: - Calculus II ``` -(See [here](/docs/configuration/secrets/) for more details about what that `!secret` does -- it's not exclusive to Todoist, and can help keep your API keys and passwords a little safer!) +(See [here](https://home-assistant.io/docs/configuration/secrets/) for more details about what that `!secret` does -- it's not exclusive to Todoist, and can help keep your API keys and passwords a little safer!) As you can see, there are 4 custom projects here: @@ -111,7 +111,7 @@ Home Assistant does its best to determine what task in each project is "most" im Todoist also comes with access to a service, `calendar.todoist_new_task`. This service can be used to create a new Todoist task. You can specify labels and a project, or you can leave them blank, and the task will go to your "Inbox" project. -Here are two example JSON payloads resulting in the same task: +Here's an example JSON payload: ```json { @@ -123,17 +123,6 @@ Here are two example JSON payloads resulting in the same task: } ``` -```json -{ - "content": "Pick up the mail", - "project": "Errands", - "labels":"Homework,School", - "priority":3, - "due_date_string":"tomorrow at 14:00", - "due_date_lang":"en" -} -``` - - **content** (*Required*): The name of the task you want to create. - **project** (*Optional*): The project to put the task in. @@ -142,11 +131,6 @@ Here are two example JSON payloads resulting in the same task: - **priority** (*Optional*): The priority of the task, from 1-4. Again, 1 means least important, and 4 means most important. -- **due_date_string** (*Optional*): When the task should be due, in [natural language](https://support.todoist.com/hc/en-us/articles/205325931-Dates-and-Times). Mutually exclusive with `due_date` - -- **due_date_lang** (*Optional*): When `due_date_string` is set, it is posisble to set the language. - Valid languages are: `en`, `da`, `pl`, `zh`, `ko`, `de`, `pt`, `ja`, `it`, `fr`, `sv`, `ru`, `es`, `nl` - -- **due_date** (*Optional*): When the task should be due, in either YYYY-MM-DD format or YYYY-MM-DD HH:MM format. Mutually exclusive with `due_date_string`. +- **due_date** (*Optional*): When the task should be due, in either YYYY-MM-DD format or YYYY-MM-DD HH:MM format. Note that there's (currently) no way to mark tasks as done through Home Assistant; task names do not necessarily have to be unique, so you could find yourself in a situation where you close the wrong task. diff --git a/source/_components/camera.abode.markdown b/source/_components/camera.abode.markdown index 2aa3da2313..a95b6d2fcf 100644 --- a/source/_components/camera.abode.markdown +++ b/source/_components/camera.abode.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Abode Camera" -description: "Instructions on how to integrate Abode cameras into Home Assistant." +description: "Instructions how to integrate Abode cameras into Home Assistant." date: 2017-08-26 13:28 sidebar: true comments: false diff --git a/source/_components/camera.amcrest.markdown b/source/_components/camera.amcrest.markdown index 73a6ca444f..2c1a042c87 100644 --- a/source/_components/camera.amcrest.markdown +++ b/source/_components/camera.amcrest.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Amcrest IP Camera" -description: "Instructions on how to integrate Amcrest IP cameras within Home Assistant." +description: "Instructions how to integrate Amcrest IP cameras within Home Assistant." date: 2016-11-24 10:00 sidebar: true comments: false diff --git a/source/_components/camera.android_ip_webcam.markdown b/source/_components/camera.android_ip_webcam.markdown index 8aa3455faa..04c6e41d8e 100644 --- a/source/_components/camera.android_ip_webcam.markdown +++ b/source/_components/camera.android_ip_webcam.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Android IP Webcam Camera" -description: "Instructions on how to integrate Android IP Webcam cameras within Home Assistant." +description: "Instructions how to integrate Android IP Webcam cameras within Home Assistant." date: 2015-07-11 0:36 sidebar: true comments: false diff --git a/source/_components/camera.arlo.markdown b/source/_components/camera.arlo.markdown index a634e8d8d9..1d66a90bbf 100644 --- a/source/_components/camera.arlo.markdown +++ b/source/_components/camera.arlo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Arlo Camera" -description: "Instructions on how to integrate your Netgear Arlo cameras within Home Assistant." +description: "Instructions how to integrate your Netgear Arlo cameras within Home Assistant." date: 2016-05-30 10:00 sidebar: true comments: false @@ -30,4 +30,4 @@ Configuration variables: - **ffmpeg_arguments**: (*Optional*): Extra options to pass to ffmpeg, e.g., image quality or video filter options. -**Note:** To be able to playback the last capture, it is required to install the `ffmpeg` component. Make sure to follow the steps mentioned at [FFMPEG](/components/ffmpeg/) documentation. +**Note:** To be able to playback the last capture, it is required to install the `ffmpeg` component. Make sure to follow the steps mentioned at [FFMPEG](https://home-assistant.io/components/ffmpeg/) documentation. diff --git a/source/_components/camera.august.markdown b/source/_components/camera.august.markdown deleted file mode 100644 index 660a9504c5..0000000000 --- a/source/_components/camera.august.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "August Camera" -description: "Instructions on how to integrate your August devices into Home Assistant." -date: 2018-02-17 22:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: august.png -ha_category: Camera -ha_release: "0.64" -ha_iot_class: "Cloud Polling" ---- - -The `august` camera platform allows you to view the latest camera image (triggered by motion) by your [August](http://august.com) device in Home Assistant. - -To add `august` camera to your installation, follow instructions in [August component](/components/august/). diff --git a/source/_components/camera.axis.markdown b/source/_components/camera.axis.markdown index ec725b06ec..23695c7905 100644 --- a/source/_components/camera.axis.markdown +++ b/source/_components/camera.axis.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Axis Camera" -description: "Instructions on how to setup Axis cameras within Home Assistant." +description: "Instructions how to setup Axis cameras within Home Assistant." date: 2017-05-01 19:09 sidebar: true comments: false diff --git a/source/_components/camera.bloomsky.markdown b/source/_components/camera.bloomsky.markdown index bd6f8a58b9..8661690eb6 100644 --- a/source/_components/camera.bloomsky.markdown +++ b/source/_components/camera.bloomsky.markdown @@ -1,7 +1,7 @@ --- layout: page title: "BloomSky Camera" -description: "Instructions on how to integrate the BloomSky camera within Home Assistant." +description: "Instructions how to integrate the BloomSky camera within Home Assistant." date: 2016-02-03 20:00 sidebar: true comments: false diff --git a/source/_components/camera.canary.markdown b/source/_components/camera.canary.markdown index 8e5f07f461..bf7c029bc7 100644 --- a/source/_components/camera.canary.markdown +++ b/source/_components/camera.canary.markdown @@ -13,20 +13,6 @@ ha_release: "0.60" ha_iot_class: "Cloud Polling" --- -The `canary` camera platform allows you to watch the live stream of your [Canary](https://canary.is) camera in Home Assistant. This requires the [`ffmpeg` component](/components/ffmpeg/) to be already configured. +The `canary` camera platform allows you to view the latest camera image (triggered by motion) by your [Canary](https://canary.is) device in Home Assistant. -To add `canary` camera to your installation, follow instructions in [Canary component](/components/canary/). Once you have [Canary component](/components/canary/) setup, your [Canary](https://canary.is) camera(s) should show up automatically. - -You can add the following to your `configuration.yaml` file to configure `canary` camera with optional settings: - -```yaml -camera: - - platform: canary -``` - -{% configuration %} - ffmpeg_arguments: - description: Extra options to pass to `ffmpeg`, e.g., image quality or video filter options. More details in [FFmpeg component](/components/ffmpeg). - required: false - type: string -{% endconfiguration %} +To add `canary` camera to your installation, follow instructions in [Canary component](/components/canary/). diff --git a/source/_components/camera.dispatcher.markdown b/source/_components/camera.dispatcher.markdown index 26eb74febc..2672c6c48e 100644 --- a/source/_components/camera.dispatcher.markdown +++ b/source/_components/camera.dispatcher.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Dispatcher IP Camera" -description: "Instructions on how to integrate internal dispatcher cameras within Home Assistant." +description: "Instructions how to integrate internal dispatcher cameras within Home Assistant." date: 2017-03-08 00:00 sidebar: true comments: false diff --git a/source/_components/camera.doorbird.markdown b/source/_components/camera.doorbird.markdown index ce23d94672..d96a1ebe9b 100644 --- a/source/_components/camera.doorbird.markdown +++ b/source/_components/camera.doorbird.markdown @@ -1,7 +1,7 @@ --- layout: page title: "DoorBird Camera" -description: "Instructions on how to integrate DoorBird video doorbell images into Home Assistant." +description: "Instructions how to integrate DoorBird video doorbell images into Home Assistant." date: 2017-08-06 11:30 sidebar: true comments: false diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 481c835a15..86e6355c8d 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -29,7 +29,7 @@ Configuration variables: - **input** (*Required*): An FFmpeg-compatible input file, stream, or feed. - **name** (*Optional*): Override the name of your camera. -- **extra_arguments** (*Optional*): Extra options to pass to `ffmpeg`, e.g., image quality or video filter options. +- **extra_arguments** (*Optional*): Extra options to pass to `ffmpeg`, e.g. image quality or video filter options. ### {% linkable_title Image quality %} diff --git a/source/_components/camera.foscam.markdown b/source/_components/camera.foscam.markdown index c9d1aabd50..ea90a82984 100644 --- a/source/_components/camera.foscam.markdown +++ b/source/_components/camera.foscam.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Foscam IP Camera" -description: "Instructions on how to integrate Foscam IP cameras within Home Assistant." +description: "Instructions how to integrate Foscam IP cameras within Home Assistant." date: 2015-09-17 08:01 sidebar: true comments: false @@ -15,8 +15,6 @@ ha_iot_class: "Local Polling" The `foscam` platform allows you to watch the live stream of your [Foscam](http://www.foscam.com/) IP camera in Home Assistant. -## {% linkable_title Configuration %} - To enable your Foscam IP camera in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -24,8 +22,8 @@ To enable your Foscam IP camera in your installation, add the following to your camera: - platform: foscam ip: IP_ADDRESS - username: YOUR_USERNAME - password: YOUR_PASSWORD + username: USERNAME + password: PASSWORD ``` Configuration variables: @@ -41,5 +39,4 @@ There seems to be some issues within Foscam with lengthy passwords and passwords ### {% linkable_title Control Foscam PTZ (Pan/Tilt/Zoom) - Home/Away %} - Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](http://www.ipcamcontrol.net/files/Foscam%20IPCamera%20CGI%20User%20Guide-V1.0.4.pdf)). For an example of how this can be done, see the [Foscam IP Camera Pan, Tilt, Zoom Control](/cookbook/foscam_away_mode_PTZ/) Cookbook entry. diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown index bec1ec5ffe..71a16ba40e 100644 --- a/source/_components/camera.generic.markdown +++ b/source/_components/camera.generic.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Generic IP Camera" -description: "Instructions on how to integrate IP cameras within Home Assistant." +description: "Instructions how to integrate IP cameras within Home Assistant." date: 2015-07-11 0:36 sidebar: true comments: false diff --git a/source/_components/camera.local_file.markdown b/source/_components/camera.local_file.markdown index b2b953041d..6dade4b4c5 100644 --- a/source/_components/camera.local_file.markdown +++ b/source/_components/camera.local_file.markdown @@ -13,9 +13,9 @@ ha_iot_class: "Local Polling" ha_release: 0.22 --- -The `local_file` camera platform allows you to integrate an image file from disk into Home Assistant as a camera. If the image is updated on the file system the image displayed in Home Assistant will also be updated. The service `local_file_update_file_path` can be used to update the image using an automation. +The `local_file` camera platform allows you to integrate any readable image file from disk into Home Assistant as a camera. If the image is updated on the file system the image displayed in Home Assistant will also be updated. -The `local_file` camera can for example be used with various camera platforms that save a temporary images locally. It can also be used to display a graph that you render periodically and will then be displayed in Home Assistant. +This can for example be used with various camera platforms that save a temporary images locally. It can also be used to display a graph that you render periodically and will then be displayed in Home Assistant. To enable this camera in your installation, add the following to your `configuration.yaml` file: @@ -31,11 +31,7 @@ Configuration variables: - **file_path** (*Required*): File to serve as the camera. - **name** (*Optional*): Name of the camera -### {% linkable_title Service `camera.local_file_update_file_path` %} ++The given `file_path` must be an existing file because the camera platform setup make a readable check on it. +
-Use this service to change the file displayed by the camera. - -| Service data attribute | Description | -| -----------------------| ----------- | -| `entity_id` | String of the `entity_id` of the camera to update. | -| `file_path` | The full path to the new image file to be displayed. | diff --git a/source/_components/camera.markdown b/source/_components/camera.markdown index 8d3c12c7e6..2d92253993 100644 --- a/source/_components/camera.markdown +++ b/source/_components/camera.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Camera" -description: "Instructions on how to integrate cameras within Home Assistant." +description: "Instructions how to integrate cameras within Home Assistant." date: 2015-11-09 08:36 sidebar: true comments: false diff --git a/source/_components/camera.mjpeg.markdown b/source/_components/camera.mjpeg.markdown index de03528200..6a01c70872 100644 --- a/source/_components/camera.mjpeg.markdown +++ b/source/_components/camera.mjpeg.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Generic MJPEG IP Camera" -description: "Instructions on how to integrate IP cameras within Home Assistant." +description: "Instructions how to integrate IP cameras within Home Assistant." date: 2015-11-09 08:36 sidebar: true comments: false diff --git a/source/_components/camera.mqtt.markdown b/source/_components/camera.mqtt.markdown index f0e903a37a..852140ddf9 100644 --- a/source/_components/camera.mqtt.markdown +++ b/source/_components/camera.mqtt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MQTT Camera" -description: "Instructions on how to use an MQTT image message as a Camera within Home Assistant." +description: "Instructions how to use an MQTT image message as a Camera within Home Assistant." date: 2017-04-14 00:45 sidebar: true comments: false diff --git a/source/_components/camera.neato.markdown b/source/_components/camera.neato.markdown index 3b959c0bc3..4fccb0b413 100644 --- a/source/_components/camera.neato.markdown +++ b/source/_components/camera.neato.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Neato Camera" -description: "Instructions on how to setup the Neato cleaning maps within Home Assistant." +description: "Instructions how to setup the Neato cleaning maps within Home Assistant." date: 2017-04-05 13:10 sidebar: true comments: false diff --git a/source/_components/camera.nest.markdown b/source/_components/camera.nest.markdown index 607a88c516..e597fcb19d 100644 --- a/source/_components/camera.nest.markdown +++ b/source/_components/camera.nest.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Nest Camera" -description: "Instructions on how to integrate Nest cameras into Home Assistant." +description: "Instructions how to integrate Nest cameras into Home Assistant." date: 2016-12-03 08:10 sidebar: true comments: false diff --git a/source/_components/camera.netatmo.markdown b/source/_components/camera.netatmo.markdown index e452d26b41..5ad8ebe38e 100644 --- a/source/_components/camera.netatmo.markdown +++ b/source/_components/camera.netatmo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Netatmo Camera" -description: "Instructions on how to integrate Netatmo cameras into Home Assistant." +description: "Instructions how to integrate Netatmo cameras into Home Assistant." date: 2016-06-02 08:10 sidebar: true comments: false diff --git a/source/_components/camera.onvif.markdown b/source/_components/camera.onvif.markdown index ed01e31d37..0cfa7cf453 100644 --- a/source/_components/camera.onvif.markdown +++ b/source/_components/camera.onvif.markdown @@ -30,21 +30,7 @@ Configuration variables: - **name** (*Optional*): Override the name of your camera. - **username** (*Optional*): The username for the camera. - **password** (*Optional*): The password for the camera. -- **port** (*Optional*): The port for the camera. This defaults to 5000. -- **profile** (*Optional*): Video profile that will be used to obtain the stream. This defaults to 0. More details below. -- **extra_arguments** (*Optional*): Extra options to pass to `ffmpeg`, e.g., image quality or video filter options. More details in [FFmpeg component](/components/ffmpeg). - -Most of the Onvif cameras support more than one audio/video Profile. Each profile provides different image quality. Usually, the first profile has the highest quality, and it is the profile used by default. However, you may want to use a lower quality image. One of the reasons may be that your hardware isn't able to render the highest quality image in real-time - especially when running on Raspberry Pi. Therefore you can choose which profile do you want to use by setting in config `profile` variable. - -### {% linkable_title Service `camera.onvif_ptz` %} - -If your ONVIF camera supports PTZ, you will be able to pan, tilt or zoom your camera. - -| Service data attribute | Description | -| -----------------------| ----------- | -| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Else targets all. -| `tilt` | Tilt direction. Allowed values: `UP`, `DOWN` -| `pan` | Pan direction. Allowed values: `RIGHT`, `LEFT` -| `zoom` | Zoom. Allowed values: `ZOOM_IN`, `ZOOM_OUT` +- **port** (*Optional*): The port for the camera. This defaults to 5000 +- **extra_arguments** (*Optional*): Extra options to pass to `ffmpeg`, e.g. image quality or video filter options. More details in [FFmpeg component](/components/ffmpeg). If you are running into trouble with this sensor, please refer to the [Troubleshooting section](/components/ffmpeg/#troubleshooting). diff --git a/source/_components/camera.proxy.markdown b/source/_components/camera.proxy.markdown deleted file mode 100644 index e8a38d4b23..0000000000 --- a/source/_components/camera.proxy.markdown +++ /dev/null @@ -1,90 +0,0 @@ ---- -layout: page -title: "Camera Proxy" -description: "Instructions on how to integrate a camera proxy within Home Assistant." -date: 2018-03-08 19:00 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Camera -ha_release: 0.65 ---- - - -The `proxy` camera platform allows you to pass another camera's output through post-processing routines and generate a new camera with the post-processed output. - -The current post-processing supports resizing the image/MJPEG as well as limiting the maximum refresh rate. - -The current proxy capabilities are intended to reduce the camera bandwidth for slower internet connections. - -To enable this camera in your installation, you must first have an existing working camera configured in Home Assistant. Next, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -camera: - - platform: proxy - entity_id: camera.-Hassbian users: don't forget to install ffmpeg support on your platform, otherwise, you'll not see video. -
-Some alternative Yi firmwares enable an experimental RTSP server, which will allow you to connect to your camera via other Home Assistant camera platforms. However, this RTSP server disables the ability to use the supremely-useful Yi Home app. In order to maintain both Home Assistant compatibility _and_ the native app, this platform retrieves videos via FTP.
@@ -72,7 +68,7 @@ Configuration variables: - **password** (*Required*): The password to the FTP server on the camera (from above). - **path** (*Optional*): The path to the raw MP4 files. Defaults to `/tmp/sd/record`. - **username** (*Optional*): The user that can access the FTP server. Defaults to `root`. -- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g., image quality or video filter options). +- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g. image quality or video filter options). ## {% linkable_title Image quality %} diff --git a/source/_components/canary.markdown b/source/_components/canary.markdown index 186d704e17..425055f48a 100644 --- a/source/_components/canary.markdown +++ b/source/_components/canary.markdown @@ -15,8 +15,6 @@ ha_iot_class: "Cloud Polling" The `canary` component allows you to integrate your [Canary](https://canary.is) devices in Home Assistant. -## {% linkable_title Configuration %} - You will need your Canary login information (username, usually your email address, and password) to use this module. To set it up, add the following to your `configuration.yaml` file: @@ -24,8 +22,8 @@ To set it up, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry canary: - username: YOUR_USERNAME - password: YOUR_PASSWORD + username: you@example.com + password: secret ``` {% configuration %} @@ -44,6 +42,8 @@ canary: default: 10 {% endconfiguration %} + + Once loaded, your front end will have the following components: * A camera image triggered by motion for each camera. diff --git a/source/_components/climate.ecobee.markdown b/source/_components/climate.ecobee.markdown index b92b001f37..e8711168e7 100644 --- a/source/_components/climate.ecobee.markdown +++ b/source/_components/climate.ecobee.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Ecobee Thermostat" -description: "Instructions on how to setup the Ecobee thermostats within Home Assistant." +description: "Instructions how to setup the Ecobee thermostats within Home Assistant." date: 2016-08-26 18:00 sidebar: true comments: false diff --git a/source/_components/climate.econet.markdown b/source/_components/climate.econet.markdown index 704c6ebf0e..3feb4aa643 100644 --- a/source/_components/climate.econet.markdown +++ b/source/_components/climate.econet.markdown @@ -1,7 +1,7 @@ --- layout: page title: "EcoNet water heater" -description: "Instructions on how to integrate Rheem EcoNet water heaters into Home Assistant." +description: "Instructions how to integrate Rheem EcoNet water heaters into Home Assistant." date: 2017-12-28 14:51 sidebar: true comments: false diff --git a/source/_components/climate.eq3btsmart.markdown b/source/_components/climate.eq3btsmart.markdown index ce833566ff..5cfa52ae40 100644 --- a/source/_components/climate.eq3btsmart.markdown +++ b/source/_components/climate.eq3btsmart.markdown @@ -1,7 +1,7 @@ --- layout: page title: "EQ3 Bluetooth Smart Thermostats" -description: "Instructions on how to integrate EQ3 Bluetooth Smart Thermostats into Home Assistant." +description: "Instructions how to integrate EQ3 Bluetooth Smart Thermostats into Home Assistant." date: 2016-04-18 22:00 sidebar: true comments: false diff --git a/source/_components/climate.flexit.markdown b/source/_components/climate.flexit.markdown index 0281b50756..078b840985 100644 --- a/source/_components/climate.flexit.markdown +++ b/source/_components/climate.flexit.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Flexit A/C controller" -description: "Instructions on how to integrate Flexit A/C unit into Home Assistant." +description: "Instructions how to integrate Flexit A/C unit into Home Assistant." date: 2017-06-02 16:30 +0200 sidebar: true comments: false diff --git a/source/_components/climate.fritzbox.markdown b/source/_components/climate.fritzbox.markdown deleted file mode 100644 index 65975ca77c..0000000000 --- a/source/_components/climate.fritzbox.markdown +++ /dev/null @@ -1,28 +0,0 @@ ---- -layout: page -title: "Fritzbox Thermostat" -description: "Instructions on how to integrate the AVM Fritzbox thermostat." -date: 2017-11-12 17:10 -sidebar: true -comments: false -sharing: true -footer: true -logo: avm.png -ha_category: Climate -ha_release: 0.68 -ha_iot_class: "Local Polling" ---- - --To get AVM fritzbox thermostat follow the instructions for the general [Fritzbox](/components/fritzbox/). -
- -### {% linkable_title Attributes %} - -The are several attributes that can be useful for automations and templates. - -| Attribute | Description | -| --------- | ----------- | -| `device_locked` | The state of the key lock at the device. -| `locked` | The state of the lock for configuring the device via the app or the Fritzbox web interface. -| `low_battery` | The low battery state indication. diff --git a/source/_components/climate.heatmiser.markdown b/source/_components/climate.heatmiser.markdown index b1478034e9..b772e9923b 100644 --- a/source/_components/climate.heatmiser.markdown +++ b/source/_components/climate.heatmiser.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Heatmiser Thermostat" -description: "Instructions on how to integrate Heatmiser thermostats within Home Assistant." +description: "Instructions how to integrate Heatmiser thermostats within Home Assistant." date: 2015-12-11 12:35 sidebar: true comments: false diff --git a/source/_components/climate.hive.markdown b/source/_components/climate.hive.markdown index 12f4688553..dd3fd41ca5 100644 --- a/source/_components/climate.hive.markdown +++ b/source/_components/climate.hive.markdown @@ -14,15 +14,13 @@ ha_iot_class: "Cloud Polling" --- -The `hive` climate platform integrates your Hive thermostat and hot water into Home Assistant, enabling control of setting the **mode** and setting the **target temperature**. - +The 'hive' climate component integrates your Hive thermostat and hot water into Home Assistant, enabling control of setting the **mode** and setting the **target temperature**. A short boost for Hive Heating or Hive Hot water can be set by using the **Aux Heat** function, this will turn on the boost feature for Hive Heating or Hive Hot water for 30 minutes at 0.5 degrees higher than the current temperature. -The platform supports the following Hive products: - -- Hive Active Heating -- Hive Multizone -- Hot water control +The Hive climate component supports the following Hive products: +- **Hive Active Heating** +- **Hive Multizone** +- **Hot water control**diff --git a/source/_components/climate.homematic.markdown b/source/_components/climate.homematic.markdown index 86e38fdb49..ac5458d592 100644 --- a/source/_components/climate.homematic.markdown +++ b/source/_components/climate.homematic.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Homematic Thermostats" -description: "Instructions on how to integrate Homematic thermostats within Home Assistant." +description: "Instructions how to integrate Homematic thermostats within Home Assistant." date: 2016-06-28 08:30 sidebar: true comments: false diff --git a/source/_components/climate.honeywell.markdown b/source/_components/climate.honeywell.markdown index 855d009cda..8104a6a77f 100644 --- a/source/_components/climate.honeywell.markdown +++ b/source/_components/climate.honeywell.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Honeywell Thermostat" -description: "Instructions on how to integrate Honeywell thermostats within Home Assistant." +description: "Instructions how to integrate Honeywell thermostats within Home Assistant." date: 2016-02-07 22:01 sidebar: true comments: false diff --git a/source/_components/climate.markdown b/source/_components/climate.markdown index fd41b437cd..53cfc08013 100644 --- a/source/_components/climate.markdown +++ b/source/_components/climate.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Climate" -description: "Instructions on how to setup climate control devices within Home Assistant." +description: "Instructions how to setup climate control devices within Home Assistant." date: 2016-08-26 19:00 sidebar: true comments: false diff --git a/source/_components/climate.melissa.markdown b/source/_components/climate.melissa.markdown deleted file mode 100644 index 9d648a83b5..0000000000 --- a/source/_components/climate.melissa.markdown +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: page -title: "Melissa Climate" -description: "Instructions on how to integrate Melissa climate system (HVAC) into Home Assistant." -date: 2018-01-08 20:21 -sidebar: true -comments: false -sharing: true -footer: true -logo: mclimate.png -ha_category: Climate -ha_iot_class: "Cloud Polling" -ha_release: 0.63 ---- - -The `Melissa` climate platform allows you to control your [Melissa Climate](http://seemelissa.com/) from within Home Assistant. - -The climate platform will be automatically configured if Melissa component is configured. - -For more configuration information see the [Melissa component](/components/melissa/) documentation. diff --git a/source/_components/climate.modbus.markdown b/source/_components/climate.modbus.markdown deleted file mode 100644 index eeb376ef8e..0000000000 --- a/source/_components/climate.modbus.markdown +++ /dev/null @@ -1,71 +0,0 @@ ---- -layout: page -title: "Modbus" -description: "Instructions how to integrate a Modbus thermostat within Home Assistant." -date: 2018-01-29 9:35 -sidebar: true -comments: false -sharing: true -footer: true -logo: modbus.png -ha_category: Thermostat -ha_release: 0.68 -ha_iot_class: "Local Polling" ---- - - -The `modbus` thermostat allows you to use a sensor value (current temperature) and target value (target temperature) from [Modbus](http://www.modbus.org/) registers. - -## {% linkable_title Configuration %} - -To use your Modbus thermostat in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -climate: - - platform: modbus - name: Watlow F4T - slave: 1 - target_temp_register: 2782 - current_temp_register: 27586 -``` - -{% configuration %} -name: - description: Name of the device - required: true - type: string -slave: - description: The number of the slave (Optional for tcp and upd Modbus, use 1). - required: true - type: int -target_temp_register: - description: Register number for target temperature (Setpoint). - required: true - type: int -current_temp_register: - description: Register number for current temperature (Process value). - required: true - type: int -data_type: - description: Response representation (int, uint, float, custom). If float selected, value will converted to IEEE 754 floating point format. - required: false - type: string - default: float -count: - description: Number of registers to read. - required: false - type: int -precision: - description: Number of valid decimals. - required: false - type: int - default: 0 -{% endconfiguration %} - - -### {% linkable_title Services %} - -| Service | Description | -| ------- | ----------- | -| set_temperature | Set Temperature. Requires `value` to be passed in, which is the desired target temperature. `value` should be in the same type as `data_type` | diff --git a/source/_components/climate.mqtt.markdown b/source/_components/climate.mqtt.markdown index 958974869a..504610dea4 100644 --- a/source/_components/climate.mqtt.markdown +++ b/source/_components/climate.mqtt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MQTT HVAC" -description: "Instructions on how to integrate MQTT HVAC into Home Assistant." +description: "Instructions how to integrate MQTT HVAC into Home Assistant." date: 2017-07-31 19:59 sidebar: true comments: false @@ -178,11 +178,11 @@ aux_state_template: #### {% linkable_title Optimistic mode %} -If a property works in *optimistic mode* (when the corresponding state topic is not set), Home Assistant will assume that any state changes published to the command topics did work and change the internal state of the entity immediately after publishing to the command topic. If it does not work in optimistic mode, the internal state of the entity is only updated when the requested update is confirmed by the device through the state topic. +If a property works in *optimistic mode* (when the corresponding state topic is not set), home assistant will assume that any state changes published to the command topics did work and change the internal state of the entity immediately after publishing to the command topic. If it does not work in optimistic mode, the internal state of the entity is only updated when the requested update is confirmed by the device through the state topic. #### {% linkable_title Using Templates %} -For all `*_state_topic`s, a template can be specified that will be used to render the incoming payloads on these topics. Also, a default template that applies to all state topis can be specified as `value_template`. This can be useful if you received payloads are e.g., in JSON format. Since in JSON, a quoted string (e.g., `"foo"`) is just a string, this can also be used for unquoting. +For all `*_state_topic`s, a template can be specified that will be used to render the incoming payloads on these topics. Also, a default template that applies to all state topis can be specified as `value_template`. This can be useful if you received payloads are e.g. in JSON format. Since in JSON, a quoted string (e.g. `"foo"`) is just a string, this can also be used for unquoting. Say you receive the operation mode `"auto"` via your `mode_state_topic`, but the mode is actually called just `auto`, here's what you could do: diff --git a/source/_components/climate.mysensors.markdown b/source/_components/climate.mysensors.markdown index 6f5379449b..a61fae33f9 100644 --- a/source/_components/climate.mysensors.markdown +++ b/source/_components/climate.mysensors.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MySensors HVAC" -description: "Instructions on how to integrate MySensors climate into Home Assistant." +description: "Instructions how to integrate MySensors climate into Home Assistant." date: 2016-10-01 15:00 +0200 sidebar: true comments: false diff --git a/source/_components/climate.nest.markdown b/source/_components/climate.nest.markdown index 4d99423734..be9adf6d41 100644 --- a/source/_components/climate.nest.markdown +++ b/source/_components/climate.nest.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Nest Thermostat" -description: "Instructions on how to integrate Nest thermostats within Home Assistant." +description: "Instructions how to integrate Nest thermostats within Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false diff --git a/source/_components/climate.netatmo.markdown b/source/_components/climate.netatmo.markdown index a90a1f4353..72c4f0de00 100644 --- a/source/_components/climate.netatmo.markdown +++ b/source/_components/climate.netatmo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Netatmo Thermostat" -description: "Instructions on how to integrate Netatmo thermostat into Home Assistant." +description: "Instructions how to integrate Netatmo thermostat into Home Assistant." date: 2016-10-11 08:10 sidebar: true comments: false diff --git a/source/_components/climate.nuheat.markdown b/source/_components/climate.nuheat.markdown index 46a8e84c5a..51ffd6fee4 100644 --- a/source/_components/climate.nuheat.markdown +++ b/source/_components/climate.nuheat.markdown @@ -1,7 +1,7 @@ --- layout: page title: "NuHeat Thermostat" -description: "Instructions on how to integrate your NuHeat Signature thermostats within Home Assistant." +description: "Instructions how to integrate your NuHeat Signature thermostats within Home Assistant." date: 2017-11-11 18:00 sidebar: true comments: false diff --git a/source/_components/climate.oem.markdown b/source/_components/climate.oem.markdown index 2b7b401229..be9b8cda21 100644 --- a/source/_components/climate.oem.markdown +++ b/source/_components/climate.oem.markdown @@ -1,7 +1,7 @@ --- layout: page title: "OpenEnergyMonitor WiFi Thermostat" -description: "Instructions on how to integrate an OpenEnergyMonitor thermostat with Home Assistant." +description: "Instructions how to integrate an OpenEnergyMonitor thermostat with Home Assistant." date: 2017-01-27 11:15 sidebar: true comments: false diff --git a/source/_components/climate.proliphix.markdown b/source/_components/climate.proliphix.markdown index b089ef586d..74227c0a98 100644 --- a/source/_components/climate.proliphix.markdown +++ b/source/_components/climate.proliphix.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Proliphix Thermostat" -description: "Instructions on how to integrate Proliphix thermostats within Home Assistant." +description: "Instructions how to integrate Proliphix thermostats within Home Assistant." date: 2016-01-15 08:00 sidebar: true comments: false diff --git a/source/_components/climate.radiotherm.markdown b/source/_components/climate.radiotherm.markdown index f4d08db107..f3cf3bd919 100644 --- a/source/_components/climate.radiotherm.markdown +++ b/source/_components/climate.radiotherm.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Radio Thermostat (3M Filtrete) Thermostat" -description: "Instructions on how to integrate Radio Thermostat (3M Filtrete) thermostats within Home Assistant." +description: "Instructions how to integrate Radio Thermostat (3M Filtrete) thermostats within Home Assistant." date: 2015-10-18 17:15 sidebar: true comments: false diff --git a/source/_components/climate.sensibo.markdown b/source/_components/climate.sensibo.markdown index 02003d4aa6..9b9771bc42 100644 --- a/source/_components/climate.sensibo.markdown +++ b/source/_components/climate.sensibo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Sensibo A/C controller" -description: "Instructions on how to integrate Sensibo A/C controller into Home Assistant." +description: "Instructions how to integrate Sensibo A/C controller into Home Assistant." date: 2017-04-01 15:00 +0200 sidebar: true comments: false diff --git a/source/_components/climate.toon.markdown b/source/_components/climate.toon.markdown index 61e4258847..57d8708aa3 100644 --- a/source/_components/climate.toon.markdown +++ b/source/_components/climate.toon.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Toon Thermostat" -description: "Instructions on how to integrate Toon thermostats within Home Assistant." +description: "Instructions how to integrate Toon thermostats within Home Assistant." date: 2017-10-22 12:00 sidebar: true comments: false diff --git a/source/_components/climate.touchline.markdown b/source/_components/climate.touchline.markdown index 0f7f271946..ebc48a9df8 100644 --- a/source/_components/climate.touchline.markdown +++ b/source/_components/climate.touchline.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Roth Touchline" -description: "Instructions on how to integrate Roth Touchline within Home Assistant." +description: "Instructions how to integrate Roth Touchline within Home Assistant." date: 2018-01-03 12:35 sidebar: true comments: false diff --git a/source/_components/climate.vera.markdown b/source/_components/climate.vera.markdown index c46b8fdff9..bc8a9fdc58 100644 --- a/source/_components/climate.vera.markdown +++ b/source/_components/climate.vera.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Vera Thermostat" -description: "Instructions on how to integrate Vera thermostats into Home Assistant." +description: "Instructions how to integrate Vera thermostats into Home Assistant." date: 2016-09-19 21:00 sidebar: true comments: false diff --git a/source/_components/climate.wink.markdown b/source/_components/climate.wink.markdown index be8623cb08..3a41d2c81d 100644 --- a/source/_components/climate.wink.markdown +++ b/source/_components/climate.wink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Wink Climate" -description: "Instructions on how to setup the Wink climate devices within Home Assistant." +description: "Instructions how to setup the Wink climate devices within Home Assistant." date: 2016-11-01 22:36 sidebar: true comments: false diff --git a/source/_components/climate.zwave.markdown b/source/_components/climate.zwave.markdown index e1b20babc6..3c5f96f724 100644 --- a/source/_components/climate.zwave.markdown +++ b/source/_components/climate.zwave.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Z-Wave Climate" -description: "Instructions on how to setup the Z-Wave thermostat or HVAC within Home Assistant." +description: "Instructions how to setup the Z-Wave thermostat or HVAC within Home Assistant." date: 2016-04-03 9:52 sidebar: true comments: false @@ -46,12 +46,12 @@ automation: at: "20:00:00" action: - service: climate.set_operation_mode + entity_id: climate.remotec_zxt120_heating_1_id data: - entity_id: climate.remotec_zxt120_heating_1_id operation_mode: Heat - service: climate.set_temperature + entity_id: climate.remotec_zxt120_heating_1_39 data: - entity_id: climate.remotec_zxt120_heating_1_39 temperature: 24 ``` @@ -65,8 +65,8 @@ automation: at: "21:00:00" action: - service: climate.set_operation_mode + entity_id: climate.remotec_zxt120_heating_1_id data: - entity_id: climate.remotec_zxt120_heating_1_id operation_mode: 'Off' ``` diff --git a/source/cloud/alexa.markdown b/source/_components/cloud.alexa.markdown similarity index 94% rename from source/cloud/alexa.markdown rename to source/_components/cloud.alexa.markdown index 7e140825af..5f30f112a1 100644 --- a/source/cloud/alexa.markdown +++ b/source/_components/cloud.alexa.markdown @@ -7,7 +7,10 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /components/cloud.alexa/ +logo: home-assistant.png +ha_release: "0.60" +ha_category: Cloud +ha_iot_class: "Cloud Push" --- The Alexa integration allows users to control the entities via the [Home Assistant Smart Home skill for Alexa][alexa skill]. This means that you can say things like "Alexa, turn on the kitchen light" to control your local Home Assistant. @@ -18,6 +21,8 @@ To use this integration, you need to have: - An Alexa enabled device like the Amazon Echo - Activated the [Home Assistant Smart Home skill for Alexa][alexa skill] +
Only Amazon US is currently supported. Other regions are being certified.
+ You can use `configuration.yaml` to configure the entities that are being shown to Alexa and how they are exposed. ```yaml @@ -40,7 +45,7 @@ cloud: display_categories: LIGHT ``` -{% configuration cloud %} +{% configuration %} alexa: description: Configuration options for the Amazon Alexa integration. required: false diff --git a/source/cloud/google_assistant.markdown b/source/_components/cloud.google_assistant.markdown similarity index 86% rename from source/cloud/google_assistant.markdown rename to source/_components/cloud.google_assistant.markdown index 070f03040b..3dc3dde7cf 100644 --- a/source/cloud/google_assistant.markdown +++ b/source/_components/cloud.google_assistant.markdown @@ -7,20 +7,20 @@ sidebar: true comments: false sharing: true footer: true +logo: home-assistant.png +ha_release: 0.61 +ha_category: Cloud +ha_iot_class: "Cloud Push" +published: false --- - --The minimum supported version of Home Assistant is 0.65.6. -
- The Google Assistant integration allows users to control the entities via the Home Assistant Smart Home skill for Google Assistant. This means that you can say things like "Ok Google, turn on the kitchen light" to control your local Home Assistant. To use this integration, you need to have: - The cloud component set up. [Learn more](/components/cloud/) - A Google Assistant enabled device like the Google Home - - Activated the [Home Assistant Smart Home skill for Google Assistant](https://assistant.google.com/services/a/uid/00000091fd5fb875) + - Activated the Home Assistant Smart Home skill for Google Assistant You can use `configuration.yaml` to configure the entities that are being shown to Google Assistant and how they are exposed. @@ -42,10 +42,10 @@ cloud: aliases: - bright lights - entry lights - room: living room + type: 'action.devices.types.LIGHT' ``` -{% configuration cloud %} +{% configuration %} google_actions: description: Configuration options for the Google Assistant integration. required: false @@ -90,8 +90,9 @@ google_actions: description: Aliases that can also be used to refer to this entity required: false type: list - room: - description: Hint for Google Assistant in which room this entity is. + type: + description: Override the type of the entity in Google Assistant. [List of available types](https://developers.google.com/actions/smarthome/guides/) required: false type: string {% endconfiguration %} + diff --git a/source/_components/cloud.markdown b/source/_components/cloud.markdown index 3008a52cac..d45e9aa15f 100644 --- a/source/_components/cloud.markdown +++ b/source/_components/cloud.markdown @@ -13,7 +13,27 @@ ha_category: Voice ha_iot_class: "Cloud Push" --- -The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa. [Learn more.](/cloud) +The Home Assistant Cloud is currently in open beta and will become part of the upcoming Community Support Package. [Learn more](/blog/2017/12/17/introducing-home-assistant-cloud/)
+ +The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa. + +The following integrations are currently available: + + - [Amazon Alexa (Amazon Echo)](/components/cloud.alexa/) + + + +### {% linkable_title How does it work? %} + +The Home Assistant Cloud has been designed with security in mind. When you activate the Cloud component, your instance will create a secure connection to the Home Assistant Cloud. There is no need for any further configuration or to expose your instance to the internet. + +Integrations like Alexa will deliver messages to our cloud which we will forward to your local instance for processing. We just forward the response back to Alexa. This means that we do not have to store the state of your house in our cloud, we’re just the messenger! + +You can find a list of frequently asked questions (and their answers) in [this blog post](/blog/2017/12/17/introducing-home-assistant-cloud/#faq). + +### {% linkable_title Enabling the cloud %} + +The Home Assistant Cloud is enabled by default. If not, add this to your configuration: ```yaml # Example configuration.yaml entry to enable the cloud component diff --git a/source/_components/comfoconnect.markdown b/source/_components/comfoconnect.markdown index 7394042b84..fcce2b619f 100644 --- a/source/_components/comfoconnect.markdown +++ b/source/_components/comfoconnect.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Zehnder ComfoAir Q Ventilation" -description: "Instructions on how to integrate Zehnder ComfoAir Q350/450/600 ventilation systems into Home Assistant." +description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 ventilation systems into Home Assistant." date: 2017-06-28 18:00 sidebar: true comments: false diff --git a/source/_components/config.markdown b/source/_components/config.markdown index 29aa9ce2ae..514840e7f7 100644 --- a/source/_components/config.markdown +++ b/source/_components/config.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Config" -description: "Instructions on how to setup the configuration panel for Home Assistant." +description: "Instructions how to setup the configuration panel for Home Assistant." date: 2017-02-24 20:00 sidebar: true comments: false diff --git a/source/_components/configurator.markdown b/source/_components/configurator.markdown index 9cabdccbb3..3d9661d50b 100644 --- a/source/_components/configurator.markdown +++ b/source/_components/configurator.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Configurator" -description: "Instructions on how to integrate the configurator in your components." +description: "Instructions how to integrate the configurator in your components." date: 2015-03-15 00:51 sidebar: true comments: false diff --git a/source/_components/conversation.markdown b/source/_components/conversation.markdown index e9bb86aaab..55b9fbb19a 100644 --- a/source/_components/conversation.markdown +++ b/source/_components/conversation.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Conversation" -description: "Instructions on how to have conversations with your Home Assistant." +description: "Instructions how to have conversations with your Home Assistant." date: 2015-03-15 00:39 sidebar: true comments: false @@ -11,85 +11,46 @@ logo: home-assistant.png ha_category: "Voice" --- -The conversation component allows you to converse with Home Assistant. You can either converse by pressing the microphone in the frontend (supported browsers only (no iOS)) or by calling the `conversation/process` service with the transcribed text. -
- 
- Screenshot of the conversation interface in Home Assistant.
-
+
+
+ Apple iPhones do not support this feature in any browser. +
diff --git a/source/_components/counter.markdown b/source/_components/counter.markdown index f181d4755a..76a11fbb89 100644 --- a/source/_components/counter.markdown +++ b/source/_components/counter.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Counter" -description: "Instructions on how to integrate counters into Home Assistant." +description: "Instructions how to integrate counters into Home Assistant." date: 2017-08-26 06:00 sidebar: true comments: false @@ -19,7 +19,7 @@ To add a counter to your installation, add the following to your `configuration. ```yaml # Example configuration.yaml entry counter: - my_custom_counter: + counter: initial: 30 step: 1 ``` diff --git a/source/_components/cover.abode.markdown b/source/_components/cover.abode.markdown index a80303a756..e67998bf0b 100644 --- a/source/_components/cover.abode.markdown +++ b/source/_components/cover.abode.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Abode Cover" -description: "Instructions on how to integrate Abode covers into Home Assistant." +description: "Instructions how to integrate Abode covers into Home Assistant." date: 2017-08-26 13:28 sidebar: true comments: false diff --git a/source/_components/cover.garadget.markdown b/source/_components/cover.garadget.markdown index 0a3b5de358..6ae25d44e8 100644 --- a/source/_components/cover.garadget.markdown +++ b/source/_components/cover.garadget.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Garadget Cover" -description: "Instructions on how to integrate Garadget covers within Home Assistant." +description: "Instructions how to integrate Garadget covers within Home Assistant." date: 2016-10-24 14:25 sidebar: true comments: false @@ -16,8 +16,6 @@ ha_iot_class: "Cloud Polling" The `garadget` cover platform lets you control [Garadget](http://www.garadget.com/) garage door futurizers through Home Assistant. -## {% linkable_title Configuration %} - To enable Garadget Covers in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -26,8 +24,8 @@ cover: - platform: garadget covers: 190028001947343412342341: - username: YOUR_USERNAME - password: YOUR_PASSWORD + username: UseYourLogin@garadget.com + password: abc123 4c003f001151353432134214: access_token: df4cc785ff818f2b01396c44142342fccdef ``` @@ -46,13 +44,12 @@ Configuration variables: If provided, the **access_token** will be used, otherwise the **username** and **password** will be used to automatically generate an access token at start time. -## {% linkable_title Example %} +**Example with more detail:**
The above devices are confirmed to work, but others may work as well.
+ diff --git a/source/_components/cover.xiaomi_aqara.markdown b/source/_components/cover.xiaomi_aqara.markdown index 6f5353b9c8..d2bbdf5fa9 100644 --- a/source/_components/cover.xiaomi_aqara.markdown +++ b/source/_components/cover.xiaomi_aqara.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Xiaomi Cover" -description: "Instructions on how to setup the Xiaomi cover within Home Assistant." +description: "Instructions how to setup the Xiaomi cover within Home Assistant." date: 2017-07-21 16:34 sidebar: true comments: false diff --git a/source/_components/cover.zwave.markdown b/source/_components/cover.zwave.markdown index 53477e1e00..90547584ce 100644 --- a/source/_components/cover.zwave.markdown +++ b/source/_components/cover.zwave.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Z-Wave Cover" -description: "Instructions on how to setup the Z-Wave covers within Home Assistant." +description: "Instructions how to setup the Z-Wave covers within Home Assistant." date: 2016-12-18 19:41 sidebar: true comments: false diff --git a/source/_components/datadog.markdown b/source/_components/datadog.markdown index 7a3ec052c7..511d51608a 100644 --- a/source/_components/datadog.markdown +++ b/source/_components/datadog.markdown @@ -35,7 +35,7 @@ datadog: Configuration variables: -- **host** (*Optional*): The IP address or hostname of your Datadog host, e.g., 192.168.1.23. Defaults to `localhost`. +- **host** (*Optional*): The IP address or hostname of your Datadog host, e.g. 192.168.1.23. Defaults to `localhost`. - **port** (*Optional*): Port to use. Defaults to 8125. - **prefix** (*Optional*): Prefix to use. Defaults to `hass`. - **rate** (*Optional*): The sample rate of UDP packets sent to Datadog. Defaults to 1. diff --git a/source/_components/deconz.markdown b/source/_components/deconz.markdown index d1fde01521..6b65b08664 100644 --- a/source/_components/deconz.markdown +++ b/source/_components/deconz.markdown @@ -17,33 +17,29 @@ ha_iot_class: "Local Push" [deCONZ REST API](http://dresden-elektronik.github.io/deconz-rest-doc/). -### {% linkable_title Supported device types %} - -- [Zigbee Lights](/components/light.deconz/) -- [Consumption Sensors](/components/sensor.deconz/) -- [Humidity Sensors](/components/sensor.deconz/) -- [Light Level Sensors](/components/sensor.deconz/) -- [OpenClose Detectors](/components/binary_sensor.deconz/) -- [Power Sensors](/components/sensor.deconz/) -- [Presence Detectors](/components/binary_sensor.deconz/) -- [Pressure Sensors](/components/sensor.deconz/) -- [Switches (Remote Controls)](/components/sensor.deconz/) -- [Temperature Sensors](/components/sensor.deconz/) - -## {% linkable_title Configuration %} - Home Assistant will automatically discover deCONZ presence on your network, if `discovery:` is present in your `configuration.yaml` file. -If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to **Menu** -> **Settings** -> **Unlock Gateway** in deCONZ and then use the deCONZ configurator in Home Assistant frontend to create an API key. When you've generated the API key from Home Assistant, the API key will be stored in `.config_entries.json` inside the `.homeassistant` folder. +If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to Menu->Settings->Unlock Gateway in deCONZ and then use the deCONZ configurator in Home Assistant GUI to create an API key. When you've generated the API key from Home Assistant, the API key will be stored in deconz.conf inside the home-assistant folder. You can add the following to your configuration.yaml file if you are not using the `discovery:` component: ```yaml # Example configuration.yaml entry deconz: - host: IP_ADDRESS + host: IP ADDRESS ``` +#### {% linkable_title Supported Device types %} + +- [Zigbee Lights](/components/light.deconz/) +- [Humidity Sensors](/components/sensor.deconz/) +- [Light Level Sensors](/components/sensor.deconz/) +- [OpenClose Detectors](/components/binary_sensor.deconz/) +- [Presence Detectors](/components/binary_sensor.deconz/) +- [Pressure Sensors](/components/sensor.deconz/) +- [Switches (Remote Controls)](/components/sensor.deconz/) +- [Temperature Sensors](/components/sensor.deconz/) + {% configuration %} host: description: The IP address of your deCONZ web server. @@ -70,41 +66,22 @@ deconz: port: 80 ``` -## {% linkable_title Debugging component %} - -If you have problems with deCONZ or the component you can add debug prints to the log. - -```yaml -logger: - default: info - logs: - pydeconz: debug - homeassistant.components.deconz: debug -``` - ## {% linkable_title Device services %} - Available services: `configure`. -#### {% linkable_title Service `deconz.configure` %} - +#### {% linkable_title Service `deconz/configure` %} Set attribute of device in Deconz using [Rest API](http://dresden-elektronik.github.io/deconz-rest-doc/rest/). | Service data attribute | Optional | Description | |-----------|----------|-------------| | `field` | No | String representing a specific device in deCONZ. | -| `entity` | No | String representing a specific HASS entity of a device in deCONZ. | | `data` | No | Data is a JSON object with what data you want to alter. | -Field and entity are exclusive, i.e you can only use one in a request. - { "field": "/lights/1", "data": {"name": "light2"} } -{ "entity": "light.light1", "data": {"name": "light2"} } - { "field": "/config", "data": {"permitjoin": 60} } -## {% linkable_title Remote control devices %} +## {% linkable_title Remote control devices%} Remote controls (ZHASwitch category) will be not be exposed as a regular entity, but as events named 'deconz_event' with a payload of 'id' and 'event'. Id will be the device name from deCONZ and Event will be the momentary state of the switch. However, a sensor entity will be created that shows the battery level of the switch as reported by deCONZ, named sensor.device_name_battery_level. @@ -119,13 +96,10 @@ Typical values for switches, the event codes are 4 numbers where the first and l Where for example on a Philips Hue Dimmer, 2001 would be holding the dim up button. -For the IKEA Tradfri remote, 1 is the middle button, 2 is up, 3 is down, 4 is left, and 5 is right. - ## {% linkable_title Examples %} ### {% linkable_title Step up and step down input number with wireless dimmer %} -{% raw %} ```yaml automation: - alias: 'Toggle lamp from dimmer' @@ -152,9 +126,9 @@ automation: - service: light.turn_on data_template: entity_id: light.lamp - brightness: > + brightness: {% raw %}> {% set bri = states.light.lamp.attributes.brightness | int %} - {{ [bri+30, 249] | min }} + {{ [bri+30, 249] | min }}{% endraw %} - alias: 'Decrease brightness of lamp from dimmer' initial_state: 'on' @@ -168,8 +142,7 @@ automation: - service: light.turn_on data_template: entity_id: light.lamp - brightness: > + brightness: {% raw %}> {% set bri = states.light.lamp.attributes.brightness | int %} - {{ [bri-30, 0] | max }} + {{ [bri-30, 0] | max }}{% endraw %} ``` -{% endraw %} diff --git a/source/_components/demo.markdown b/source/_components/demo.markdown index f1c2573720..b399c9485c 100644 --- a/source/_components/demo.markdown +++ b/source/_components/demo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Demo platforms" -description: "Instructions on how to use the Platform demos with Home Assistant." +description: "Instructions how to use the Platform demos with Home Assistant." date: 2016-02-24 07:00 sidebar: true comments: false @@ -12,7 +12,7 @@ ha_category: Other --- -The `demo` platform allows you to use components 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. +The `demo` platform allows you to use components 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](https://home-assistant.io/demo/) or `hass --demo-mode` but combined with your own real/functional platforms. Available demo platforms: diff --git a/source/_components/device_sun_light_trigger.markdown b/source/_components/device_sun_light_trigger.markdown index d49c4e1565..e0a75a093c 100644 --- a/source/_components/device_sun_light_trigger.markdown +++ b/source/_components/device_sun_light_trigger.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Presence based lights" -description: "Instructions on how to automate your lights with Home Assistant." +description: "Instructions how to automate your lights with Home Assistant." date: 2015-01-20 22:36 sidebar: true comments: false diff --git a/source/_components/device_tracker.actiontec.markdown b/source/_components/device_tracker.actiontec.markdown index fbf2119650..b292353585 100644 --- a/source/_components/device_tracker.actiontec.markdown +++ b/source/_components/device_tracker.actiontec.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Actiontec" -description: "Instructions on how to integrate Actiontec routers into Home Assistant." +description: "Instructions how to integrate Actiontec routers into Home Assistant." date: 2015-08-30 19:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.aruba.markdown b/source/_components/device_tracker.aruba.markdown index e84c37954b..0dd6102555 100644 --- a/source/_components/device_tracker.aruba.markdown +++ b/source/_components/device_tracker.aruba.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Aruba" -description: "Instructions on how to integrate Aruba routers into Home Assistant." +description: "Instructions how to integrate Aruba routers into Home Assistant." date: 2015-08-31 08:45 sidebar: true comments: false @@ -36,7 +36,7 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., `192.168.1.1`. +- **host** (*Required*): The IP address of your router, e.g. `192.168.1.1`. - **username** (*Required*): The username of an user with administrative privileges, usually `admin`. - **password** (*Required*): The password for your given admin account. diff --git a/source/_components/device_tracker.asuswrt.markdown b/source/_components/device_tracker.asuswrt.markdown index 7889253ce9..a49a066309 100644 --- a/source/_components/device_tracker.asuswrt.markdown +++ b/source/_components/device_tracker.asuswrt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ASUSWRT" -description: "Instructions on how to integrate ASUSWRT based routers into Home Assistant." +description: "Instructions how to integrate ASUSWRT based routers into Home Assistant." date: 2015-08-06 19:00 sidebar: true comments: false @@ -19,8 +19,6 @@ The `asuswrt` platform offers presence detection by looking at connected devices This platform is **NOT** available for [Microsoft Windows installations](http://pexpect.readthedocs.io/en/stable/overview.html#pexpect-on-windows). -### {% linkable_title Configuration %} - To use an ASUSWRT router in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -31,44 +29,15 @@ device_tracker: username: YOUR_ADMIN_USERNAME ``` -{% configuration %} -host: - description: "The IP address of your router, eg. `192.168.1.1`." - required: true - type: string -username: - description: "The username of an user with administrative privileges, usually `admin`." - required: true - type: string -password: - description: "The password for your given admin account (use this if no SSH key is given)." - required: false - type: string -protocol: - description: "The protocol (`ssh` or `telnet`) to use." - required: false - type: string - default: ssh -port: - description: SSH port to use. - required: false - type: int - default: 22 -mode: - description: "The operating mode of the router (`router` or `ap`)." - required: false - type: string - default: router -ssh_key: - description: The path to your SSH private key file associated with your given admin account (instead of password). - required: false - type: string -require_ip: - description: If the router is in access point mode. - required: false - type: boolean - default: true -{% endconfiguration %} +Configuration variables: + +- **host** (*Required*): The IP address of your router, eg. `192.168.1.1`. +- **username** (*Required*: The username of an user with administrative privileges, usually `admin`. +- **password** (*Optional*): The password for your given admin account (use this if no SSH key is given). +- **protocol** (*Optional*): The protocol (`ssh` or `telnet`) to use. Defaults to `ssh`. +- **port** (*Optional*): SSH port to use. Defaults to `22`. +- **mode** (*Optional*): The operating mode of the router (`router` or `ap`). Defaults to `router`. +- **ssh_key** (*Optional*): The path to your SSH private key file associated with your given admin account (instead of password).You need to [enable telnet](https://www.asus.com/support/faq/1005449/) on your router if you choose to use `protocol: telnet`. diff --git a/source/_components/device_tracker.bbox.markdown b/source/_components/device_tracker.bbox.markdown index 35bae013f0..7a5cc91649 100644 --- a/source/_components/device_tracker.bbox.markdown +++ b/source/_components/device_tracker.bbox.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Bbox" -description: "Instructions on how to integrate Bouygues Bbox routers into Home Assistant." +description: "Instructions how to integrate Bouygues Bbox routers into Home Assistant." date: 2016-10-13 23:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.bluetooth_le_tracker.markdown b/source/_components/device_tracker.bluetooth_le_tracker.markdown index ce1dab5000..03b844f667 100644 --- a/source/_components/device_tracker.bluetooth_le_tracker.markdown +++ b/source/_components/device_tracker.bluetooth_le_tracker.markdown @@ -48,7 +48,7 @@ Configuration variables: - **interval_seconds** (*Optional*): Seconds between each scan for new devices. Defaults to `12` seconds. As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times. -Some BTLE devices (e.g., fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won't see this device. +Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won't see this device. ## {% linkable_title Rootless Setup %} diff --git a/source/_components/device_tracker.bluetooth_tracker.markdown b/source/_components/device_tracker.bluetooth_tracker.markdown index 45bd09eae3..0a2a2d0632 100644 --- a/source/_components/device_tracker.bluetooth_tracker.markdown +++ b/source/_components/device_tracker.bluetooth_tracker.markdown @@ -27,14 +27,6 @@ device_tracker: - platform: bluetooth_tracker ``` -{% configuration %} -request_rssi: - description: Performs a request for the "Received signal strength indication" (RSSI) of each tracked device - required: false - type: boolean - default: False -{% endconfiguration %} - In some cases it can be that your device is not discovered. In that case let your phone scan for Bluetooth devices while you restart Home Assistant. Just hit `Scan` on your phone all the time until Home Assistant is fully restarted and the device should appear in `known_devices.yaml`. For additional configuration variables check the [Device tracker page](/components/device_tracker/). diff --git a/source/_components/device_tracker.bmw_connected_drive.markdown b/source/_components/device_tracker.bmw_connected_drive.markdown deleted file mode 100644 index 4f390c5fa3..0000000000 --- a/source/_components/device_tracker.bmw_connected_drive.markdown +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: page -title: "BMW Connected Drive Device Tracker" -description: "Instructions on how to setup your BMW Connected Drive account with Home Assistant." -date: 2018-01-10 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: bmw.png -ha_category: Presence Detection -ha_release: 0.64 ---- - - -The `bmw_connected_drive` platform allows you to import data on your BMW into Home Assistant. - -The device tracker platform will be automatically configured if the `bmw_connected_drive` component is configured. - -For more configuration information see the [`bmw_connected_drive` component](/components/bmw_connected_drive/) documentation. diff --git a/source/_components/device_tracker.bt_home_hub_5.markdown b/source/_components/device_tracker.bt_home_hub_5.markdown index 106ba06083..9fd185eadd 100644 --- a/source/_components/device_tracker.bt_home_hub_5.markdown +++ b/source/_components/device_tracker.bt_home_hub_5.markdown @@ -1,7 +1,7 @@ --- layout: page title: "BT Home Hub 5" -description: "Instructions on how to integrate BT Home Hub 5 router into Home Assistant." +description: "Instructions how to integrate BT Home Hub 5 router into Home Assistant." date: 2016-06-13 13:00 sidebar: true comments: false @@ -25,6 +25,6 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., 192.168.1.254. +- **host** (*Required*): The IP address of your router, e.g. 192.168.1.254. See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.cisco_ios.markdown b/source/_components/device_tracker.cisco_ios.markdown index 589241b8eb..1402e84064 100644 --- a/source/_components/device_tracker.cisco_ios.markdown +++ b/source/_components/device_tracker.cisco_ios.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Cisco IOS" -description: "Instructions on how to integrate Cisco IOS routers into Home Assistant." +description: "Instructions how to integrate Cisco IOS routers into Home Assistant." date: 2016-11-07 19:59 sidebar: true comments: false @@ -59,7 +59,7 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., 192.168.1.1. +- **host** (*Required*): The IP address of your router, e.g. 192.168.1.1. - **username** (*Required*): The username of an user with administrative privileges. - **password** (*Required*): The password for your given admin account. diff --git a/source/_components/device_tracker.ddwrt.markdown b/source/_components/device_tracker.ddwrt.markdown index 826046d029..4fa4fe0af4 100644 --- a/source/_components/device_tracker.ddwrt.markdown +++ b/source/_components/device_tracker.ddwrt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "DD-WRT" -description: "Instructions on how to integrate DD-WRT based routers into Home Assistant." +description: "Instructions how to integrate DD-WRT based routers into Home Assistant." date: 2015-05-11 09:00 sidebar: true comments: false @@ -27,7 +27,7 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., `192.168.1.1`. +- **host** (*Required*): The IP address of your router, e.g. `192.168.1.1`. - **username** (*Required*: The username of an user with administrative privileges, usually `admin`. - **password** (*Required*): The password for your given admin account. diff --git a/source/_components/device_tracker.fritz.markdown b/source/_components/device_tracker.fritz.markdown index 3e4a745d99..40d7bfa985 100644 --- a/source/_components/device_tracker.fritz.markdown +++ b/source/_components/device_tracker.fritz.markdown @@ -1,7 +1,7 @@ --- layout: page title: "FRITZ!Box" -description: "Instructions on how to integrate AVM FRITZ!Box based routers into Home Assistant." +description: "Instructions how to integrate AVM FRITZ!Box based routers into Home Assistant." date: 2015-12-13 19:00 sidebar: true comments: false @@ -15,8 +15,6 @@ ha_release: "0.10" The `fritz` platform offers presence detection by looking at connected devices to a [AVM Fritz!Box](http://avm.de/produkte/fritzbox/) based router. -## {% linkable_title Configuration %} -
It might be necessary to install additional packages: $ sudo apt-get install libxslt-dev libxml2-dev python3-lxml
If you are working with the All-in-One installation, you may also need to execute also within your virtual environment the command pip install lxml; be patient this will take a while.
-Since this platform is using an unofficial API with the help of [locationsharinglib](https://github.com/costastf/locationsharinglib), Google seems to block access to your data the first time you've logged in with this component. -This issue can be fixed by logging in with your new account and approving your login on the [Device Activity](https://myaccount.google.com/device-activity) page. -
- -To integrate Google Maps Location Sharing in Home Assistant, add the following section to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -device_tracker: - - platform: google_maps - username: YOUR_USERNAME - password: YOUR_PASSWORD -``` - -{% configuration %} -username: - description: The email address for the Google account that has access to your shared location. - required: true - type: string -password: - description: The password for your given username. - required: true - type: string -{% endconfiguration %} diff --git a/source/_components/device_tracker.gpslogger.markdown b/source/_components/device_tracker.gpslogger.markdown index 4c2889a94b..34465aec4f 100644 --- a/source/_components/device_tracker.gpslogger.markdown +++ b/source/_components/device_tracker.gpslogger.markdown @@ -1,7 +1,7 @@ --- layout: page title: "GPSLogger" -description: "Instructions on how to use GPSLogger to track devices in Home Assistant." +description: "Instructions how to use GPSLogger to track devices in Home Assistant." date: 2016-11-25 15:00 sidebar: true comments: false @@ -39,7 +39,7 @@ After the launch, go to **General Options**. Enable **Start on bootup** and **St GPSLogger Settings -Go to **Logging details** and disable **Log to GPX**, **Log to KML** and **Log to NMEA**. Enable **Log to custom URL**. +Go to **Logging details** and disable **Log to GPX**. **Log to KML**, and **Log to NMEA**. Enable **Log to custom URL**.
@@ -56,7 +56,7 @@ Right after enabling, the app will take you to the **Log to custom URL** setting
The relevant endpoint is: `/api/gpslogger`
```text
-https://[IP address Home Assistant]:[Port]/api/gpslogger?
+http://[IP address Home Assistant]:[Port]/api/gpslogger?
latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC
&battery=%BATT&speed=%SPD&direction=%DIR
&altitude=%ALT&provider=%PROV&activity=%ACT
@@ -65,8 +65,8 @@ https://[IP address Home Assistant]:[Port]/api/gpslogger?
Add the above URL after you modified it with your settings into the **URL** field. Remove the line breaks as they are only there to make the URL readable here.
- It's HIGHLY recommended to use SSL/TLS.
-- Use the domain that Home Assistant is available on the internet or the public IP address. This can be a local IP address if you are using an always on VPN from your mobile device to your home network.
-- Only remove `[Port]` if your Home Assistant instance is using port 443. Otherwise set it to the port you're using.
+- Use the domain that Home Assistant is available on the internet or the public IP address. Can be a local IP address if you are using a VPN setup.
+- Only remove `[Port]` if your Home Assistant instance is using port 80. Otherwise set it to 8123.
- For Home Assistant only the above URL, as written, will work - do not add or remove any parameters.
- Make sure to include your [API password](/components/http/) if you have configured a password. Add `&api_password=[Your password]` to the end of the URL.
- You can change the name of your device name by replacing `&device=%SER` with `&device=[Devicename]`.
diff --git a/source/_components/device_tracker.huawei_router.markdown b/source/_components/device_tracker.huawei_router.markdown
index 92ee5c62d4..6c9647ac3c 100644
--- a/source/_components/device_tracker.huawei_router.markdown
+++ b/source/_components/device_tracker.huawei_router.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Huawei Router"
-description: "Instructions on how to integrate Huawei Routers into Home Assistant."
+description: "Instructions how to integrate Huawei Routers into Home Assistant."
date: 2017-07-16 01:40
sidebar: true
comments: false
@@ -12,12 +12,9 @@ ha_category: Presence Detection
ha_release: 0.51
---
-The `huawei` device trakcer platform offers presence detection by looking at connected devices to a [Huawei router](http://m.huawei.com/enmobile/enterprise/products/network/access/pon-one/hw-371813.htm).
-
+This component offers presence detection by looking at connected devices to a [Huawei router](http://m.huawei.com/enmobile/enterprise/products/network/access/pon-one/hw-371813.htm).
Currently, this was only tested with the Huawei HG8247H and HG8247Q Smart Router (used by Vodafone Portugal).
-## {% linkable_title Configuration %}
-
To use a Huawei router in your installation, add the following to your `configuration.yaml` file:
```yaml
@@ -25,23 +22,15 @@ To use a Huawei router in your installation, add the following to your `configur
device_tracker:
- platform: huawei_router
host: 192.168.1.1
- username: YOUR_USERNAME
- password: YOUR_PASSWORD
+ username: user
+ password: pass
```
-{% configuration %}
-host:
- description: The IP address of your router, e.g., 192.168.1.1.
- required: true
- type: string
-username:
- description: The username to login into the router (the same used trough the router's web interface).
- required: true
- type: string
-password:
- description: The password for the specified username.
- required: true
- type: string
-{% endconfiguration %}
+Configuration variables:
+
+- **host** (*Required*): The IP address of your router, e.g. 192.168.1.1.
+- **username** (*Required*): The username to login into the router (the same used trough the router's web interface).
+- **password** (*Required*): The password for the specified username.
+
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.icloud.markdown b/source/_components/device_tracker.icloud.markdown
index a57ba44d4b..74f22f02f6 100644
--- a/source/_components/device_tracker.icloud.markdown
+++ b/source/_components/device_tracker.icloud.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "iCloud"
-description: "Instructions on how to use iCloud to track devices in Home Assistant."
+description: "Instructions how to use iCloud to track devices in Home Assistant."
date: 2015-12-15 1000
sidebar: true
comments: false
@@ -33,11 +33,9 @@ Configuration variables:
- **username** (*Required*): The username for the iCloud account.
- **password** (*Required*): The password for your given username.
- **account_name** (*Optional*): The friendly name for the account_name. If this isn't given, it will use the account_name of the username (so the part before the `@` in the email address).
-- **max_interval** (*Optional*): Maximum interval in minutes between subsequent location upates. This tracker uses dynamic intervals for requesting location updates. When iphone is stationary, interval will eventually be set to `max_interval` to save battery. When iphone starts moving again interval will be dynamically updated to 1 min. Note that updating interval to 1 min might be delayed by maximum `max_interval` minutes. Default is 30 min. Minimum value is 1 min.
-- **gps_accuracy_threshold** (*Optional*): iCloud location updates come with some gps_accuracy varying from 10 to 5000 meters. This setting defines the accuracy threshold in meters for a location update. Less accurate updates will be discarded by this tracker. This allows more precise location monitoring and fewer false positive zone changes. Default is 1000 meters.
-Low `max_interval` may cause battery drainage as it wakes up your device to get the current location. +This may cause battery drainage as it wakes up your device to get the current location.
@@ -50,7 +48,7 @@ To disable the drainage of the battery, a dynamic interval is being used for eac 2 Factor Authentication is the improved version of 2 Steps Authentication, this is still not supported by the pyicloud library. Therefore it's not possible to use it with the device_tracker yet. 4 services are available for this component: -- **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iphone location. Can be used in automations when manual location update is needed, e.g. to check if anyone is home when door's been opened. +- **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. - **icloud_lost_iphone**: This service will play the Lost iPhone sound on a certain iDevice. The `account_name` and `device_name` are optional. - **icloud_set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level. - **icloud_reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are being found by the component or if you have added a new iDevice to your account. The `account_name` is optional. diff --git a/source/_components/device_tracker.keenetic_ndms2.markdown b/source/_components/device_tracker.keenetic_ndms2.markdown index aec5ac8a52..3dbd197b77 100644 --- a/source/_components/device_tracker.keenetic_ndms2.markdown +++ b/source/_components/device_tracker.keenetic_ndms2.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Keenetic NDMS2 Routers" -description: "Instructions on how to integrate Keenetic NDMS2 Routers into Home Assistant." +description: "Instructions how to integrate Keenetic NDMS2 Routers into Home Assistant." date: 2017-09-15 15:40 sidebar: true comments: false @@ -28,7 +28,7 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., 192.168.1.1. +- **host** (*Required*): The IP address of your router, e.g. 192.168.1.1. - **username** (*Required*): The username to login into the router (user should have read access to web interface of the router). - **password** (*Required*): The password for the specified username. - **interface** (*Optional*): Ihe internal name of the interface to get devices connected to. Default is 'Home'. For expert users only. diff --git a/source/_components/device_tracker.linksys_ap.markdown b/source/_components/device_tracker.linksys_ap.markdown index 6cdc3984b2..b9821eb522 100644 --- a/source/_components/device_tracker.linksys_ap.markdown +++ b/source/_components/device_tracker.linksys_ap.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Linksys Access Points" -description: "Instructions on how to integrate Linksys Access Points into Home Assistant." +description: "Instructions how to integrate Linksys Access Points into Home Assistant." date: 2016-12-16 01:40 sidebar: true comments: false diff --git a/source/_components/device_tracker.linksys_smart.markdown b/source/_components/device_tracker.linksys_smart.markdown index 4cf0ca7e5a..0e1827c680 100644 --- a/source/_components/device_tracker.linksys_smart.markdown +++ b/source/_components/device_tracker.linksys_smart.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Linksys Smart Wifi Router" -description: "Instructions on how to integrate Linksys Smart Wifi Router into Home Assistant." +description: "Instructions how to integrate Linksys Smart Wifi Router into Home Assistant." date: 2017-06-22 01:40 sidebar: true comments: false diff --git a/source/_components/device_tracker.locative.markdown b/source/_components/device_tracker.locative.markdown index 02d932a7a4..2a185c924e 100644 --- a/source/_components/device_tracker.locative.markdown +++ b/source/_components/device_tracker.locative.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Locative" -description: "Instructions on how to use Locative to track devices in Home Assistant." +description: "Instructions how to use Locative to track devices in Home Assistant." date: 2015-10-13 19:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.luci.markdown b/source/_components/device_tracker.luci.markdown index 621f70a905..32d0cde87b 100644 --- a/source/_components/device_tracker.luci.markdown +++ b/source/_components/device_tracker.luci.markdown @@ -1,7 +1,7 @@ --- layout: page title: "OpenWRT (luci)" -description: "Instructions on how to integrate OpenWRT routers into Home Assistant." +description: "Instructions how to integrate OpenWRT routers into Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -39,7 +39,7 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., `192.168.1.1`. +- **host** (*Required*): The IP address of your router, e.g. `192.168.1.1`. - **username** (*Required*): The username of an user with administrative privileges, usually `admin`. - **password** (*Required*): The password for your given admin account. diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown index b595407d13..25e2961498 100644 --- a/source/_components/device_tracker.markdown +++ b/source/_components/device_tracker.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Device Tracker" -description: "Instructions on how to setup device tracking within Home Assistant." +description: "Instructions how to setup device tracking within Home Assistant." date: 2015-01-20 22:36 sidebar: true comments: false @@ -13,7 +13,7 @@ Home Assistant can get information from your wireless router or third party serv There are also trackers available which use different technologies like [MQTT](/components/mqtt/) or [Nmap](/components/device_tracker.nmap_tracker/) to scan the network for devices. -An [event](/getting-started/automation-trigger/#event-trigger) (`device_tracker_new_device`) will be fired when a device is discovered for the first time. +An [event](/getting-started/automation-trigger/#event-trigger) (`device_tracker_new_device`) will be fired when a device is discovered for the first time. ## {% linkable_title Configuring a `device_tracker` platform %} @@ -37,13 +37,9 @@ The following optional parameters can be used with any platform. However device | Parameter | Default | Description | |----------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `interval_seconds` | 12 | Seconds between each scan for new devices | -| `consider_home` | 180 | Seconds to wait till marking someone as not home after not being seen. This parameter is most useful for households with Apple iOS devices that go into sleep mode while still at home to conserve battery life. iPhones will occasionally drop off the network and then re-appear. `consider_home` helps prevent false alarms in presence detection when using IP scanners such as Nmap. `consider_home` accepts various time representations, (e.g., the following all represents 3 minutes: `180`, `0:03`, `0:03:00`) | +| `consider_home` | 180 | Seconds to wait till marking someone as not home after not being seen. This parameter is most useful for households with Apple iOS devices that go into sleep mode while still at home to conserve battery life. iPhones will occasionally drop off the network and then re-appear. `consider_home` helps prevent false alarms in presence detection when using IP scanners such as Nmap. `consider_home` accepts various time representations, (E.g. the following all represents 3 minutes: `180`, `0:03`, `0:03:00`) | | `new_device_defaults`| | Default values for new discovered devices. Available options `track_new_devices` (default: `True`), `hide_if_away` (default: `False`) | -
- Note that setting `track_new_devices: False` will still result in new devices being recorded in `known_devices.yaml`, but they won't be tracked (`track: no`). -
- The extended example from above would look like the following sample: ```yaml @@ -69,7 +65,7 @@ Here's an example configuration for a single device: devicename: name: Friendly Name mac: EA:AA:55:E7:C6:94 - picture: https://www.home-assistant.io/images/favicon-192x192.png + picture: https://home-assistant.io/images/favicon-192x192.png track: yes hide_if_away: no ``` diff --git a/source/_components/device_tracker.meraki.markdown b/source/_components/device_tracker.meraki.markdown index cbe481d39e..a88aa1d713 100644 --- a/source/_components/device_tracker.meraki.markdown +++ b/source/_components/device_tracker.meraki.markdown @@ -11,21 +11,8 @@ logo: meraki.png ha_category: Presence Detection ha_release: "0.60" --- - -Use your Meraki AP as device tracker. Note that Meraki will see all devices, not only connected to the network. - -### {% linkable_title Prerequisites %} - -1. Go to Network-wide/General page, and find the Location and scanning section. -1. Make sure analytics and Scanning API are both enabled. -1. Make note of the Validator string, which will be used in the `device_tracker` configuration. -1. Click **Add a Post URL**: - 1. Set the Post URL to `https://YOUR_HOSTNAME/api/meraki?api_password=YOUR_HASS_PASSWORD` - 1. Set the Secret to a randomly generated string, and make note of it for the `device_tracker` configuration. - 1. Make sure the API Version is set to `2.0`. - 1. Hit **Save** in the bottom right of the page. - -## {% linkable_title Configuration %} +Use your `Meraki AP` as device tracker. Note that Meraki will see all devices, not only connected to the network. +Follow instructions [here](https://meraki.cisco.com/technologies/location-analytics-api) how to enable Location Analytics. After you configure access to the Meraki CMX API, add the following to your `configuration.yaml` file: @@ -37,13 +24,14 @@ device_tracker: validator: meraki_validator ``` + {% configuration %} secret: - description: Secret code added in Meraki. + description: Secret code added in Meraki required: true type: string validator: - description: Validation string from Meraki. + description: Validation string from Meraki required: true type: string {% endconfiguration %} diff --git a/source/_components/device_tracker.mercedesme.markdown b/source/_components/device_tracker.mercedesme.markdown deleted file mode 100644 index ad59c95e0d..0000000000 --- a/source/_components/device_tracker.mercedesme.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Mercedes me" -description: "Instructions on for how to integrate Mercedes me into Home Assistant." -date: 2018-01-27 10:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: mercedesme.png -ha_category: Presence Detection -ha_release: 0.63 ---- - -The `Mercedes me` platform allows you to get data about the location of your [Mercedes me connected car](https://www.mercedes-benz.com/en/mercedes-me/) car within Home Assistant. - -The device tracker platform will be automatically configured if Mercedes me component is configured. - -For more configuration information see the [Mercedes me component](/components/mercedesme/) documentation. diff --git a/source/_components/device_tracker.mikrotik.markdown b/source/_components/device_tracker.mikrotik.markdown index da1dceee4d..e3e49c4846 100644 --- a/source/_components/device_tracker.mikrotik.markdown +++ b/source/_components/device_tracker.mikrotik.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Mikrotik" -description: "Instructions on how to integrate Mikrotik/Routerboard based routers into Home Assistant." +description: "Instructions how to integrate Mikrotik/Routerboard based routers into Home Assistant." date: 2017-04-28 16:03 sidebar: true comments: false diff --git a/source/_components/device_tracker.mqtt.markdown b/source/_components/device_tracker.mqtt.markdown index 3640b8ad5a..d60b895c50 100644 --- a/source/_components/device_tracker.mqtt.markdown +++ b/source/_components/device_tracker.mqtt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MQTT Device Tracker" -description: "Instructions on how to use MQTT to track devices in Home Assistant." +description: "Instructions how to use MQTT to track devices in Home Assistant." date: 2015-09-19 20:41 sidebar: true comments: false @@ -32,7 +32,7 @@ Configuration variables: - **qos** (*Optional*): The QoS level of the topic. -Example JSON you can publish to the topic (e.g., via mqtt.publish service): +Example JSON you can publish to the topic (e.g. via mqtt.publish service): ```json { diff --git a/source/_components/device_tracker.mqtt_json.markdown b/source/_components/device_tracker.mqtt_json.markdown index a6cbc50b87..d7a515588c 100644 --- a/source/_components/device_tracker.mqtt_json.markdown +++ b/source/_components/device_tracker.mqtt_json.markdown @@ -1,7 +1,7 @@ --- layout: page title: "JSON MQTT Device Tracker" -description: "Instructions on how to use JSON MQTT to track devices in Home Assistant." +description: "Instructions how to use JSON MQTT to track devices in Home Assistant." date: 2017-04-12 20:41 sidebar: true comments: false diff --git a/source/_components/device_tracker.mysensors.markdown b/source/_components/device_tracker.mysensors.markdown index 5366c68ea7..14db68931a 100644 --- a/source/_components/device_tracker.mysensors.markdown +++ b/source/_components/device_tracker.mysensors.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MySensors Device Tracker" -description: "Instructions on how to use MySensors to track devices in Home Assistant." +description: "Instructions how to use MySensors to track devices in Home Assistant." date: 2017-02-06 15:00 +0100 sidebar: true comments: false diff --git a/source/_components/device_tracker.netgear.markdown b/source/_components/device_tracker.netgear.markdown index 8bdcacc8cd..70dbbce102 100644 --- a/source/_components/device_tracker.netgear.markdown +++ b/source/_components/device_tracker.netgear.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Netgear" -description: "Instructions on how to integrate Netgear routers into Home Assistant." +description: "Instructions how to integrate Netgear routers into Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -13,6 +13,7 @@ ha_iot_class: "Local Polling" ha_release: pre 0.7 --- + This platform allows you to detect presence by looking at connected devices to a [Netgear](http://www.netgear.com/) device. To use this device tracker in your installation, add the following to your `configuration.yaml` file: @@ -28,18 +29,10 @@ device_tracker: Configuration variables: -- **url** (*Optional*): The base URL, e.g., `http://routerlogin.com:5000` for example. If not provided `host` and `port` are used. If none provided autodetection of the URL will be used. -- **host** (*Optional*): The IP address of your router, e.g., `192.168.1.1`. -- **port** (*Optional*): The port your router communicates with. -- **username** (*Optional*): The username of a user with administrative privileges. If not provided `admin` will be used. +- **host** (*Optional*): The IP address of your router, e.g. `192.168.1.1`. If not provided `routerlogin.net` will be used. +- **username** (*Optional*): The username of an user with administrative privileges. If not provided `admin` will be used. +- **port** (*Optional*): The port your router communicates with (defaults to `5000`, but `80` is also known to be used on some models). - **password** (*Required*): The password for your given admin account. -- **devices** (*Optional*): If provided only specified devices will be reported. Can be MAC address or the device name as reported in the Netgear UI. -- **exclude** (*Optional*): Devices to exclude from the scan. -- **accesspoints** (*Optional*): Also track devices on the specified APs. Only supports MAC address. - -When `accesspoints` is specified an extra device will be reported for each device connected to the APs specified here, as `MY-LAPTOP on RBS40`. `Router` will be reported as AP name for the main AP. Only tested with Orbi. - -The use of `devices` or `exclude` is recommended when using `accesspoints` to avoid having a lot of entries. List of models that are known to use port 80: - Nighthawk X4S - AC2600 (R7800) diff --git a/source/_components/device_tracker.nmap_tracker.markdown b/source/_components/device_tracker.nmap_tracker.markdown index 74ace37e23..0ce79dfc3a 100644 --- a/source/_components/device_tracker.nmap_tracker.markdown +++ b/source/_components/device_tracker.nmap_tracker.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Nmap" -description: "Instructions on how to integrate Nmap into Home Assistant." +description: "Instructions how to integrate Nmap into Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false diff --git a/source/_components/device_tracker.owntracks.markdown b/source/_components/device_tracker.owntracks.markdown index a852ff2e50..631d8dc669 100644 --- a/source/_components/device_tracker.owntracks.markdown +++ b/source/_components/device_tracker.owntracks.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Owntracks" -description: "Instructions on how to use Owntracks to track devices in Home Assistant." +description: "Instructions how to use Owntracks to track devices in Home Assistant." date: 2015-09-22 07:00 sidebar: true comments: false @@ -13,8 +13,13 @@ featured: false ha_release: 0.7.4 --- + This platform allows you to detect presence using [Owntracks](http://owntracks.org/). OwnTracks allows users to track their location on iOS phones and publish it to an MQTT broker. This platform will connect to the broker and monitor for new locations. ++The Android app for OwnTracks is no longer developed or supported, Zanzito is a drop in replacement for OwnTracks MQTT. +
+ This component requires [the MQTT component](/components/mqtt/) to be set up and works very well together with [the zone component](/components/zone/). To integrate Owntracks in Home Assistant, add the following section to your `configuration.yaml` file: @@ -29,7 +34,7 @@ Configuration variables: - **max_gps_accuracy** (*Optional*): Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account. - **waypoints** (*Optional*): Owntracks users can define [waypoints](http://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `True`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to `True`. -- **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. This would be the `username` portion of the Base Topic Name, (e.g., owntracks/**username**/iPhone). Defaults to all users who are connected to Home Assistant via Owntracks. +- **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. This would be the `username` portion of the Base Topic Name, (e.g. owntracks/**username**/iPhone). Defaults to all users who are connected to Home Assistant via Owntracks. - **secret** (*Optional*): [Payload encryption key](http://owntracks.org/booklet/features/encrypt/). This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the `libsodium` library to be present. - **mqtt_topic** (*Optional*): The topic to subscribe for Owntracks updates on your MQTT instance (defaults to `owntracks/#`). - **events_only** (*Optional*): Home Assistant will ignore all location updates and rely solely on geofence enter/leave events. @@ -54,7 +59,6 @@ device_tracker: ``` ### {% linkable_title Using Owntracks with other device trackers %} - Owntracks can also be used with other device trackers, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/). To do this, fill in the `mac` field to the Owntracks entry in `known_devices.yaml` with the MAC address of the device you want to track. This way the state of the device will be determined by the source that reported last. The naming convention for known device list is `+The Android app for OwnTracks is no longer developed or supported. Consider [GPS Logger](/components/device_tracker.gpslogger/) as an alternative. +
+ To integrate Owntracks tracking via HTTP in Home Assistant, add the following section to your `configuration.yaml` file: ```yaml @@ -32,21 +36,5 @@ Open OwnTracks and go to Connection preferences: - Mode: Select **Private HTTP** - Host: [Home Assistant URL]:[port]/api/owntracks/[your name]/[device name] - Identification: Turn **Authentication** on, username `homeassistant` and password is your API password that you use to login to Home Assistant. - + Host example: If I host my Home Assistant at `https://example.duckdns.org`, my name is Paulus and my phone is a Pixel I would set the host to be `https://example.duckdns.org/api/owntracks/paulus/pixel`. This will result in an entity with an ID of `device_tracker.paulus_pixel`. You can pick any name for the user and the device. - -Since the battery data is available as an attribute of the device tracker entity, it can be tracked with a [`template` sensor](/components/sensor.template/). - -{% raw %} -```yaml -# Example configuration.yaml entry -sensor: - - platform: template - sensors: - pixel_battery: - friendly_name: Pixel of Paulus - unit_of_measurement: "%" - value_template: '{{ states.device_tracker.paulus_pixel.attributes.battery|int }}' - device_class: battery -``` -{% endraw %} diff --git a/source/_components/device_tracker.ping.markdown b/source/_components/device_tracker.ping.markdown index 1f34368012..7979881198 100644 --- a/source/_components/device_tracker.ping.markdown +++ b/source/_components/device_tracker.ping.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Ping (ICMP)" -description: "Instructions on how to integrate Ping (ICMP)-based presence detection into Home Assistant." +description: "Instructions how to integrate Ping (ICMP)-based presence detection into Home Assistant." date: 2017-01-06 08:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.sky_hub.markdown b/source/_components/device_tracker.sky_hub.markdown index 792aece8a8..e5a1271894 100644 --- a/source/_components/device_tracker.sky_hub.markdown +++ b/source/_components/device_tracker.sky_hub.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Sky Hub" -description: "Instructions on how to integrate Sky Hub routers into Home Assistant." +description: "Instructions how to integrate Sky Hub routers into Home Assistant." date: 2017-01-28 09:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown index 8193abfee8..60c14a1f87 100644 --- a/source/_components/device_tracker.snmp.markdown +++ b/source/_components/device_tracker.snmp.markdown @@ -1,7 +1,7 @@ --- layout: page title: "SNMP" -description: "Instructions on how to integrate SNMP into Home Assistant." +description: "Instructions how to integrate SNMP into Home Assistant." date: 2015-10-08 12:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.swisscom.markdown b/source/_components/device_tracker.swisscom.markdown index 49c4f72ba9..bee21be205 100644 --- a/source/_components/device_tracker.swisscom.markdown +++ b/source/_components/device_tracker.swisscom.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Swisscom Internet-Box" -description: "Instructions on how to integrate Swisscom Internet-Box into Home Assistant." +description: "Instructions how to integrate Swisscom Internet-Box into Home Assistant." date: 2016-10-29 23:30 sidebar: true comments: false diff --git a/source/_components/device_tracker.tado.markdown b/source/_components/device_tracker.tado.markdown index 70f130c7e0..bc1d91b37b 100644 --- a/source/_components/device_tracker.tado.markdown +++ b/source/_components/device_tracker.tado.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Tado" -description: "Instructions on how to integrate Tado into Home Assistant." +description: "Instructions how to integrate Tado into Home Assistant." date: 2017-01-17 12:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.thomson.markdown b/source/_components/device_tracker.thomson.markdown index 810d586d27..f9d39eb6d7 100644 --- a/source/_components/device_tracker.thomson.markdown +++ b/source/_components/device_tracker.thomson.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Thomson" -description: "Instructions on how to integrate Thomson routers into Home Assistant." +description: "Instructions how to integrate Thomson routers into Home Assistant." date: 2015-08-30 19:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.tile.markdown b/source/_components/device_tracker.tile.markdown index 8abb07a676..63ba3d693c 100644 --- a/source/_components/device_tracker.tile.markdown +++ b/source/_components/device_tracker.tile.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Tile" -description: "Instructions on how to use Tile to track devices in Home Assistant." +description: "Instructions how to use Tile to track devices in Home Assistant." date: 2017-11-08 20:40:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.tomato.markdown b/source/_components/device_tracker.tomato.markdown index 279cd63b68..3c5eca66ca 100644 --- a/source/_components/device_tracker.tomato.markdown +++ b/source/_components/device_tracker.tomato.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Tomato" -description: "Instructions on how to integrate Tomato routers into Home Assistant." +description: "Instructions how to integrate Tomato routers into Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -31,11 +31,11 @@ device_tracker: {% configuration %} host: - description: "The IP address or hostname of your router, e.g., `192.168.1.1` or `rt-ac68u`." + description: "The IP address or hostname of your router, e.g. `192.168.1.1` or `rt-ac68u`." required: false type: string port: - description: "The port number of your router, e.g., `443`." + description: "The port number of your router, e.g. `443`." required: false type: int default: 80/443 (automatically detected) @@ -45,7 +45,7 @@ ssl: type: bool default: false verify_ssl: - description: "If SSL verification for https resources needs to be turned off (for self-signed certs, etc.) this can take on boolean values `False` or `True` or you can pass a location on the device where a certificate can be used for verification e.g., `/mnt/NAS/router_cert.pem`." + description: "If SSL verification for https resources needs to be turned off (for self-signed certs, etc.) this can take on boolean values `False` or `True` or you can pass a location on the device where a certificate can be used for verification e.g. `/mnt/NAS/router_cert.pem`." required: false type: [string, bool] default: true diff --git a/source/_components/device_tracker.tplink.markdown b/source/_components/device_tracker.tplink.markdown index 29b70a143a..89897bb1e0 100644 --- a/source/_components/device_tracker.tplink.markdown +++ b/source/_components/device_tracker.tplink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "TP-Link" -description: "Instructions on how to integrate TP-Link routers into Home Assistant." +description: "Instructions how to integrate TP-Link routers into Home Assistant." date: 2015-06-22 10:30 sidebar: true comments: false @@ -31,7 +31,7 @@ device_tracker: Configuration variables: -- **host** (*Required*): The IP address of your router, e.g., 192.168.1.1. +- **host** (*Required*): The IP address of your router, e.g. 192.168.1.1. - **username** (*Required*: The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. @@ -41,7 +41,7 @@ For Archer C9 models running firmware version 150811 or later please use the enc 2. Type in the password you use to login into the password field. 3. Click somewhere else on the page so that the password field is not selected anymore. 4. Open the JavaScript console of your browser (usually by pressing F12 and then clicking on "Console"). -5. Type `document.getElementById("login-password").value;` or `document.getElementById("pcPassword").value;`, depending on your firmware version. +5. Type ```document.getElementById("login-password").value;```. 6. Copy the returned value to your Home Assistant configuration as password. See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.trackr.markdown b/source/_components/device_tracker.trackr.markdown index 962300ed1e..6337b8f787 100644 --- a/source/_components/device_tracker.trackr.markdown +++ b/source/_components/device_tracker.trackr.markdown @@ -1,7 +1,7 @@ --- layout: page title: "TrackR" -description: "Instructions on how to use TrackR to track devices in Home Assistant." +description: "Instructions how to use TrackR to track devices in Home Assistant." date: 2016-12-22 1000 sidebar: true comments: false @@ -24,18 +24,11 @@ To integrate TrackR in Home Assistant, add the following section to your `config # Example configuration.yaml entry device_tracker: platform: trackr - username: YOUR_USERNAME - password: YOUR_PASSWORD + username: USERNAME + password: PASSWORD ``` -{% configuration %} -username: - description: The email address for the TrackR account. - required: true - type: string -password: - description: The password for your given username. - required: true - type: string -{% endconfiguration %} +Configuration variables: +- **username** (*Required*): The email address for the TrackR account. +- **password** (*Required*): The password for your given username. diff --git a/source/_components/device_tracker.ubus.markdown b/source/_components/device_tracker.ubus.markdown index 3df045db24..d408fec544 100644 --- a/source/_components/device_tracker.ubus.markdown +++ b/source/_components/device_tracker.ubus.markdown @@ -1,7 +1,7 @@ --- layout: page title: "OpenWRT (ubus)" -description: "Instructions on how to integrate OpenWRT routers into Home Assistant." +description: "Instructions how to integrate OpenWRT routers into Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -68,7 +68,7 @@ Configuration variables: - **host** (*Required*): The IP address of your router, eg. 192.168.1.1. - **username** (*Required*): The username of an user with administrative privileges, usually *root*. - **password** (*Required*): The password for your given account. -- **dhcp_software** (*Optional*): The DHCP software used in your router: `dnsmasq`, `dhcpd`, or `none`. Defaults to `dnsmasq`. +- **dhcp_software** (*Optional*): The DHCP software used in your router: `dnsmasq` or `dhcpd`. Defaults to `dnsmasq`. See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.unifi.markdown b/source/_components/device_tracker.unifi.markdown index e941066770..a71db05655 100644 --- a/source/_components/device_tracker.unifi.markdown +++ b/source/_components/device_tracker.unifi.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Ubiquiti Unifi WAP" -description: "Instructions on how to use a Unifi WAP controller as a device tracker module." +description: "Instructions how to use a Unifi WAP controller as a device tracker module." date: 2016-02-19 20:59 sidebar: true comments: false @@ -20,12 +20,8 @@ To use this device tracker in your installation, add the following to your `conf # Example configuration.yaml entry device_tracker: - platform: unifi - host: unifi - username: username - password: password - ssid_filter: - - 'HomeSSID' - - 'IoTSSID' + username: USERNAME + password: PASSWORD ``` {% configuration %} @@ -60,14 +56,8 @@ verify_ssl: detection_time: description: How long since the last seen time before the device is marked away, specified in seconds. type: int - required: false + required: optional default: 300 -ssid_filter: - description: Filter the SSIDs that tracking will occur on. - type: list of strings - required: false - default: None - {% endconfiguration %} See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. @@ -80,7 +70,7 @@ The Unifi controller allows you to create multiple users on it besides the main The Unifi controller can either be a dedicated hardware device (Unifi's cloud key), or as software any Linux system. If you run the the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well. -It is recommended that you run the Unifi controller in a dedicated virtual machine to avoid that situation. +It is recommended that you run the Unifi controller in a dedicate virtual machine to avoid that situation. ### {% linkable_title Troubleshooting and Time Synchronization %} diff --git a/source/_components/device_tracker.unifi_direct.markdown b/source/_components/device_tracker.unifi_direct.markdown index 4816832b8e..8c0bda46b8 100644 --- a/source/_components/device_tracker.unifi_direct.markdown +++ b/source/_components/device_tracker.unifi_direct.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Ubiquiti Unifi direct AP" -description: "Instructions on how to use a Unifi WAP as a device tracker." +description: "Instructions how to use a Unifi WAP as a device tracker." date: 2017-11-17 14:59 sidebar: true comments: false @@ -13,7 +13,7 @@ ha_release: 0.59 --- -This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ubnt.com/products/#unifi). This device tracker differs form [Ubiquiti Unifi WAP](/components/device_tracker.unifi/) because it doesn't require the Unifi controller software. +This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ubnt.com/products/#unifi). This device tracker differs form [Ubiquiti Unifi WAP](https://home-assistant.io/components/device_tracker.unifi/) because it doesn't require the Unifi controller software. To use this device tracker in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/device_tracker.upc_connect.markdown b/source/_components/device_tracker.upc_connect.markdown index 1f77bc8d86..ca0a7e57b2 100644 --- a/source/_components/device_tracker.upc_connect.markdown +++ b/source/_components/device_tracker.upc_connect.markdown @@ -1,7 +1,7 @@ --- layout: page title: "UPC ConnectBox" -description: "Instructions on how to integrate UPC ConnectBox into Home Assistant." +description: "Instructions how to integrate UPC ConnectBox into Home Assistant." date: 2016-12-30 00:00 sidebar: true comments: false diff --git a/source/_components/device_tracker.xiaomi.markdown b/source/_components/device_tracker.xiaomi.markdown index d38571007c..9a8f6a43fd 100644 --- a/source/_components/device_tracker.xiaomi.markdown +++ b/source/_components/device_tracker.xiaomi.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Xiaomi Router" -description: "Instructions on how to integrate Xiaomi routers into Home Assistant." +description: "Instructions how to integrate Xiaomi routers into Home Assistant." date: 2017-01-12 12:04 sidebar: true comments: false diff --git a/source/_components/device_tracker.xiaomi_miio.markdown b/source/_components/device_tracker.xiaomi_miio.markdown deleted file mode 100644 index ae60404393..0000000000 --- a/source/_components/device_tracker.xiaomi_miio.markdown +++ /dev/null @@ -1,38 +0,0 @@ ---- -layout: page -title: "Xiaomi Mi WiFi Repeater 2" -description: "Instructions how to integrate your Xiaomi Mi WiFi Repeater 2 within Home Assistant." -date: 2018-04-01 21:06 -sidebar: true -comments: false -sharing: true -footer: true -logo: xiaomi.png -ha_category: Presence Detection -ha_version: 0.67 -ha_iot_class: "Local Polling" ---- - -The `xiaomi_miio` device tracker platform is observing your Xiaomi Mi WiFi Repeater 2 and reporting all associated WiFi clients. - -Please follow the instructions on [Retrieving the Access Token](/components/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token. - -To add a Xiaomi Mi Air Quality Monitor to your installation, add the following to your `configuration.yaml` file: - -```yaml -device_tracker: - - platform: xiaomi_miio - host: 192.168.130.73 - token: YOUR_TOKEN -``` - -{% configuration %} -host: - description: The IP address of your miio device. - required: true - type: string -token: - description: The API token of your miio device. - required: true - type: string -{% endconfiguration %} diff --git a/source/_components/dialogflow.markdown b/source/_components/dialogflow.markdown index bf2cc4b4e6..a034f72e28 100644 --- a/source/_components/dialogflow.markdown +++ b/source/_components/dialogflow.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Dialogflow" -description: "Instructions on how integrate Dialogflow with Home Assistant." +description: "Instructions how integrate Dialogflow with Home Assistant." date: 2017-01-27 11:28 sidebar: true comments: false @@ -47,10 +47,10 @@ To use this integration, you should define a conversation (intent) in Dialogflow - Select name, language (if you are planning to use Google Actions check their [supported languages](https://support.google.com/assistant/answer/7108196?hl=en)) and time zone - Click "Save" - Go to "Fulfillment" (in the left menu) -- Enable Webhook and set your Home Assistant URL with the Dialogflow endpoint, e.g., `https://myhome.duckdns.org/api/dialogflow?api_password=HA_PASSWORD` +- Enable Webhook and set your Home Assistant URL with the Dialogflow endpoint, e.g. `https://myhome.duckdns.org/api/dialogflow?api_password=HA_PASSWORD` - Click "Save" - Create a new intent -- Below "User says" write one phrase that you, the user, will tell Dialogflow, e.g., `What is the temperature at home?` +- Below "User says" write one phrase that you, the user, will tell Dialogflow, e.g. `What is the temperature at home?` - In "Action" set some key (this will be the bind with Home Assistant configuration), eg.: GetTemperature - In "Response" set "Cannot connect to Home Assistant or it is taking to long" (fall back response) - At the end of the page, click on "Fulfillment" and check "Use webhook" diff --git a/source/_components/digital_ocean.markdown b/source/_components/digital_ocean.markdown index 4554819ee2..c2e26b9aa3 100644 --- a/source/_components/digital_ocean.markdown +++ b/source/_components/digital_ocean.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Digital Ocean" -description: "Instructions on how to integrate the Digital Ocean within Home Assistant." +description: "Instructions how to integrate the Digital Ocean within Home Assistant." date: 2016-09-24 20:00 sidebar: true comments: false diff --git a/source/_components/discoverable.markdown b/source/_components/discoverable.markdown index 12c170a1ee..19c16ce0ac 100644 --- a/source/_components/discoverable.markdown +++ b/source/_components/discoverable.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Discoverable" -description: "Instructions on how to setup the discoverable component with Home Assistant." +description: "Instructions how to setup the discoverable component with Home Assistant." date: 2016-03-01 07:00 sidebar: true comments: false @@ -23,7 +23,7 @@ for state in hass.states(): To enable `discovery` in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry discoverable: expose_password: yes ``` diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index f369ce67c1..f6629e3159 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Discovery" -description: "Instructions on how to setup Home Assistant to discover new devices." +description: "Instructions how to setup Home Assistant to discover new devices." date: 2015-01-24 14:39 sidebar: true comments: false @@ -14,32 +14,31 @@ ha_category: Other Home Assistant can discover and automatically configure [zeroconf](https://en.wikipedia.org/wiki/Zero-configuration_networking)/[mDNS](https://en.wikipedia.org/wiki/Multicast_DNS) and [uPnP](https://en.wikipedia.org/wiki/Universal_Plug_and_Play) devices on your network. Currently the `discovery` component can detect: - * [Apple TV](/components/apple_tv/) - * [Axis Communications security devices](/components/axis/) - * [Belkin WeMo switches](/components/wemo/) - * [Bluesound speakers](/components/media_player.bluesound/) - * [Bose Soundtouch speakers](/components/media_player.soundtouch/) - * [Denon network receivers](/components/media_player.denonavr/) - * [DirecTV receivers](/components/media_player.directv/) - * [Frontier Silicon internet radios](/components/media_player.frontier_silicon/) - * [Google Cast](/components/media_player.cast/) - * [HomeKit](/components/homekit_controller/) - * [IKEA Trådfri (Tradfri)](/components/tradfri/) - * [Linn / Openhome](/components/media_player.openhome/) - * [Logitech Harmony Hub](/components/remote.harmony/) - * [Logitech media server (Squeezebox)](/components/media_player.squeezebox/) - * [Netgear routers](/components/device_tracker.netgear/) - * [Panasonic Viera](/components/media_player.panasonic_viera/) - * [Philips Hue](/components/light.hue/) - * [Plex media server](/components/media_player.plex/) - * [Roku media player](/components/media_player.roku/) - * [SABnzbd downloader](/components/sensor.sabnzbd/) - * [Samsung TVs](/components/media_player.samsungtv/) - * [Sonos speakers](/components/media_player.sonos/) - * [Telldus Live](/components/tellduslive/) - * [Wink](/components/wink/) - * [Yamaha media player](/components/media_player.yamaha/) - * [Yeelight Sunflower bulb](/components/light.yeelightsunflower/) + * [Apple TV](https://home-assistant.io/components/apple_tv/) + * [Axis Communications security devices](https://home-assistant.io/components/axis/) + * [Belkin WeMo switches](https://home-assistant.io/components/wemo/) + * [Bluesound speakers](https://home-assistant.io/components/media_player.bluesound/) + * [Bose Soundtouch speakers](https://home-assistant.io/components/media_player.soundtouch/) + * [Denon network receivers](https://home-assistant.io/components/media_player.denonavr/) + * [DirecTV receivers](https://home-assistant.io/components/media_player.directv/) + * [Frontier Silicon internet radios](https://home-assistant.io/components/media_player.frontier_silicon/) + * [Google Cast](https://home-assistant.io/components/media_player.cast/) + * [IKEA Trådfri (Tradfri)](https://home-assistant.io/components/tradfri/) + * [Linn / Openhome](https://home-assistant.io/components/media_player.openhome/) + * [Logitech Harmony Hub](https://home-assistant.io/components/remote.harmony/) + * [Logitech media server (Squeezebox)](https://home-assistant.io/components/media_player.squeezebox/) + * [Netgear routers](https://home-assistant.io/components/device_tracker.netgear/) + * [Panasonic Viera](https://home-assistant.io/components/media_player.panasonic_viera/) + * [Philips Hue](https://home-assistant.io/components/light.hue/) + * [Plex media server](https://home-assistant.io/components/media_player.plex/) + * [Roku media player](https://home-assistant.io/components/media_player.roku/) + * [SABnzbd downloader](https://home-assistant.io/components/sensor.sabnzbd/) + * [Samsung TVs](https://home-assistant.io/components/media_player.samsungtv/) + * [Sonos speakers](https://home-assistant.io/components/media_player.sonos/) + * [Telldus Live](https://home-assistant.io/components/tellduslive/) + * [Wink](https://home-assistant.io/components/wink/) + * [Yamaha media player](https://home-assistant.io/components/media_player.yamaha/) + * [Yeelight Sunflower bulb](https://home-assistant.io/components/light.yeelightsunflower/) It will be able to add Google Chromecasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user. @@ -51,8 +50,6 @@ discovery: ignore: - sonos - samsung_tv - enable: - - homekit ``` Configuration variables: @@ -82,18 +79,11 @@ Valid values for ignore are: * `sabnzbd`: SABnzbd downloader * `samsung_tv`: Samsung TVs * `sonos`: Sonos speakers - * `songpal` : Songpal * `tellduslive`: Telldus Live * `wink`: Wink Hub * `yamaha`: Yamaha media player * `yeelight`: Yeelight Sunflower bulb -- **enable** (*Optional*): A list of platforms not enabled by default that `discovery` should discover. - -Valid values for enable are: - - * `homekit`: HomeKit accessories -Home Assistant must be on the same network as the devices for uPnP discovery to work. If running Home Assistant in a [Docker container](/docs/installation/docker/) use switch `--net=host` to put it on the host's network. @@ -109,7 +99,7 @@ If you are on Windows and you're using Python 3.5, download the [Netifaces](http
If you see `Not initializing discovery because could not install dependency netdisco==0.6.1` in the logs, you will need to install the `python3-dev` or `python3-devel` package on your system manually (eg. `sudo apt-get install python3-dev` or `sudo dnf -y install python3-devel`). On the next restart of Home Assistant, the discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system. - + For DSM/Synology, install via debian-chroot [see this forum post](https://community.home-assistant.io/t/error-starting-home-assistant-on-synology-for-first-time/917/15).
diff --git a/source/_components/dominos.markdown b/source/_components/dominos.markdown index d6849d738f..062c0fbfea 100644 --- a/source/_components/dominos.markdown +++ b/source/_components/dominos.markdown @@ -10,15 +10,12 @@ footer: true logo: dominos.png ha_category: Other ha_version: 0.59 -ha_iot_class: "Cloud Polling" --- -The `dominos` component allows you to order Dominos Pizza from within your Home Assistant scripts and automations. +The `Dominos` component allows you to order Dominos Pizza from within your Home Assistant scripts and automations. At present, this component only supports ordering within Canada and the US. -## {% linkable_title Configuration %} - To enable the component, you need to set up your customer information and define some orders. Orders are a group of product codes. You can get these product codes by inspecting an order request from the Dominos web app, or you can [add this custom panel by following this readme](https://github.com/wardcraigj/hass-dominos-panel) to see the available product codes in a separate panel in your install. diff --git a/source/_components/doorbird.markdown b/source/_components/doorbird.markdown index 9db3c71d86..4ce686ec64 100644 --- a/source/_components/doorbird.markdown +++ b/source/_components/doorbird.markdown @@ -20,10 +20,9 @@ To connect your device, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry doorbird: - host: DOORBIRD_IP_OR_HOSTNAME - username: YOUR_USERNAME - password: YOUR_PASSWORD - hass_url_override: HASS_IP + host: IP_OR_HOSTNAME + username: abcdef0001 + password: xxxxxxxxxx ``` Configuration variables: @@ -32,77 +31,7 @@ Configuration variables: - **username** (*Required*): The username of a non-administrator user account on the device. - **password** (*Required*): The password for the user specified. - **doorbell_events** (*Optional*): Setting this to `true` this will register a callback URL with the device so that events can be published to the event bus when the doorbell rings. -- **hass_url_override** (*Optional*): If your DoorBird cannot connect to the machine running Home Assistant because you are using dynamic DNS or some other HTTP configuration (such as HTTPS), specify the LAN IP of the machine here to force a LAN connection.Enabling `doorbell_events` will delete all other registered push notification services with the device every time Home Assistant starts. This will not affect notifications delivered by the DoorBird mobile app.
- -### Doorbell Sound Examples - -You can create an automation that triggers on event `doorbird_doorbell` to play a doorbell sound when the Doorbird button is pressed. This should work with any media player. - -#### Example using SONOS - -[`SONOS`](http://www.sonos.com) players have features allowing for "snapshotting" the current state of some or all players so those state(s) can be "restored" at a later time. This feature is perfect for implementing a doorbell sound (from Doorbird or any other Doorbell setup for that matter). The [`media_player.sonos`](/components/media_player.sonos/) platform includes the [`SONOS_SNAPSHOT`](/components/media_player.sonos/#service-sonos_snapshot) and [`SONOS_RESTORE`](/components/media_player.sonos/#service-sonos_restore) features. The result of not using these features is any currently playing songs or media will not continue playing after the doorbell sound has played and you will be left with the doorbell sound queued as the last played song. This setup allows for seamless ringing of the doorbell and all SONOS devices continuing nicely on as if nothing had happened. - -The example script below takes a snapshot of three SONOS players that are not currently grouped together, joins the three players in a group (so the sound plays at the same time on all players), plays the doorbell MP3 sound, unjoins the players from the group and finally restores the players to their original state. When the players are grouped they are controlled by refering to the `master`. - -Automation file: - -```yaml -- alias: Doorbird ring - trigger: - platform: event - event_type: doorbird_doorbell - action: - service: script.turn_on - entity_id: script.doorbell -``` - -Script file: - -```yaml -doorbell: - alias: Ring Doorbell - sequence: - - service: media_player.sonos_snapshot - data: - entity_id: - - media_player.kitchen - - media_player.master_bedroom - - media_player.study - - service: media_player.sonos_join - data: - master: media_player.study - entity_id: - - media_player.kitchen - - media_player.master_bedroom - - media_player.study - - service: media_player.play_media - data: - entity_id: media_player.study # the group master - media_content_id: http://10.1.1.10/sounds/doorbell.mp3 # this is on a NAS but could be HASS local - media_content_type: music - - service: media_player.volume_set - data: - entity_id: # can still control the volume of grouped players indivdually - - media_player.study - - media_player.kitchen - - media_player.master_bedrom - volume_level: 0.50 - - delay: - seconds: 4 # wait while the sound plays - - service: media_player.sonos_unjoin - data: - entity_id: - - media_player.kitchen - - media_player.master_bedroom - - media_player.study - - service: media_player.sonos_restore - data: - entity_id: - - media_player.kitchen - - media_player.master_bedroom - - media_player.study -``` diff --git a/source/_components/downloader.markdown b/source/_components/downloader.markdown index beec226876..53063587d6 100644 --- a/source/_components/downloader.markdown +++ b/source/_components/downloader.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Downloader" -description: "Instructions on how to setup the downloader component with Home Assistant." +description: "Instructions how to setup the downloader component with Home Assistant." date: 2015-01-24 14:39 sidebar: true comments: false @@ -42,29 +42,3 @@ This will download the file from the given URL. | `subdir` | yes | Download into subdirectory of **download_dir** | | `filename` | yes | Determine the filename. | | `overwrite` | yes | Whether to overwrite the file or not, defaults to `false`. | - -### {% linkable_title Download Status Events %} - -When a download finished successfully, Home Assistant will emit a 'downloader_download_completed' event to the event bus which you can use to write automations against. -In case download failed another event 'downloader_download_failed' is emitted to indicate that the download did not complete successfully. - -Along with the event the following payload parameters are available: - -| Parameter | Description | -|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `url` | The `url` that was requested.| -| `filename` | The `name` of the file that was being downloaded.| - -#### Example Automation: - -```yaml -- alias: Download Failed Notification - trigger: - platform: event - event_type: downloader_download_failed - action: - service: persistent_notification.create - data_template: - message: "{{trigger.event.data.filename}} download failed" - title: "Download Failed" - ``` diff --git a/source/_components/dyson.markdown b/source/_components/dyson.markdown index 7c0e1ca2f3..a3d015001c 100644 --- a/source/_components/dyson.markdown +++ b/source/_components/dyson.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Dyson" -description: "Instructions on how to integrate Dyson into Home Assistant." +description: "Instructions how to integrate Dyson into Home Assistant." date: 2017-05-27 10:00 sidebar: true comments: false @@ -15,31 +15,29 @@ ha_release: 0.47 The `dyson` component is the main component to integrate all [Dyson](https://dyson.com) related platforms: [Fans](/components/fan/dyson/) and [Robot vacuum](/components/vacuum/dyson/). -## {% linkable_title Configuration %} - To enable this component, add the following lines to your `configuration.yaml`: ```yaml -# Example configuration.yaml entry dyson: - username: YOUR_DYSON_USERNAME - password: YOUR_DYSON_PASSWORD - language: YOUR_DYSON_ACCOUNT_LANGUGAGE + username:-Be aware that `emulated_hue` doesn't work for new **Google Home** users. If you're a new user of Google Home, use the [Google Assistant component](/components/google_assistant/). +Be aware that `emulated_hue` doesn't work for new **Google Home** users. If you're a new user of Google Home, use the [Google Assistant component](https://home-assistant.io/components/google_assistant/).
-The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, which allows services that work with the Hue API to interact with Home Assistant -entities. The driving use case behind for functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no setup cost outside of configuration changes. -The virtual bridge can turn entities on/off or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness. +The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant +entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no set up cost outside of configuration changes. +The virtual bridge has the ability to turn entities on or off, or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness.A physical Hue Bridge is required for Philips Hue lights to function - this virtual bridge will not replace a physical bridge. Instead, it allows Home Assistant to represent non-Philips Hue devices to Amazon Echo as Philips Hue devices, which Amazon Echo can control with built-in support. @@ -29,10 +29,6 @@ A physical Hue Bridge is required for Philips Hue lights to function - this virt It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresses, and if the IP changes, the Echo won't be able to control it. This is easiest done from your router, see your router's manual for details.
--Both Google Home and Alexa use the device they were initially set up with for communication with emulated_hue. In other words: if you remove/replace this device you will also break emulated_hue. -
- ### {% linkable_title Configuration %} To enable the emulated Hue bridge, add one of the following configs to your `configuration.yaml` file: @@ -51,14 +47,14 @@ emulated_hue: Configuration variables: -- **type** (*Optional*): The type of assistant which we are emulating. Either `alexa` or `google_home`, defaults to `google_home`. **This configuration option is deprecated and will be removed in a future release. It is no longer necessary to define type.** +- **type** (*Optional*): The type of assistant who we are emulated for. Either `alexa` or `google_home`, defaults to `google_home`. **This configuration option is deprecated and will be removed in a future release. It is no longer necessary to define type.** - **host_ip** (*Optional*): The IP address that your Home Assistant installation is running on. If you do not specify this option, the component will attempt to determine the IP address on its own. - **listen_port** (*Optional*): The port the Hue bridge API web server will run on. If not specified, this defaults to 8300. This can be any free port on your system. -- **advertise_ip** (*Optional*): If you need to override the IP address used for UPnP discovery. (For example, using network isolation in Docker) -- **advertise_port** (*Optional*): If you need to specifically override the advertised UPnP port. +- **advertise_ip** (*Optional*): If you need to override the IP address used for UPNP discovery. (For example, using network isolation in Docker) +- **advertise_port** (*Optional*): If you need to specifically override the advertised UPNP port. -- **upnp_bind_multicast** (*Optional*): Whether or not to bind the UPnP (SSDP) listener to the multicast address (239.255.255.250) or instead to the (unicast) host_ip address specified above (or automatically determined). The default is true, which will work for most situations. In special circumstances, like running in a FreeBSD or FreeNAS jail, you may need to disable this. +- **upnp_bind_multicast** (*Optional*): Whether or not to bind the UPNP (SSDP) listener to the multicast address (239.255.255.250) or instead to the (unicast) host_ip address specified above (or automatically determined). The default is true, which will work for most situations. In special circumstances, like running in a FreeBSD or FreeNAS jail, you may need to disable this. - **off_maps_to_on_domains** (*Optional*): The domains that maps an "off" command to an "on" command. @@ -79,8 +75,6 @@ Configuration variables: - `media_player` - `fan` -- **entities** (*Optional*): Customization for entities. - A full configuration sample looks like the one below. ```yaml @@ -96,21 +90,26 @@ emulated_hue: expose_by_default: true exposed_domains: - light - entities: - light.bedroom_light: - name: "Bedside Lamp" - light.ceiling_lights: - hidden: true ``` -The following are attributes that can be applied in the `entities` section: +With additional customization you will be able to specify the behavior of the existing entities. -- **name** (*Optional*): The name that the emulated Hue will use. The default for this is the entity's friendly name. -- **hidden** (*Optional*): Whether or not the emulated Hue bridge should expose the entity. Adding `hidden: false` will expose the entity to Alexa. The default value for this attribute is controlled by the `expose_by_default` option. +```yaml +# Example customization +homeassistant: + customize: + light.bedroom_light: + # Don't allow light.bedroom_light to be controlled by the emulated Hue bridge + emulated_hue_hidden: true + light.office_light: + # Address light.office_light as "back office light" + emulated_hue_name: "back office light" +``` --These attributes used to be found under the `customize` section of `homeassistant`, however, they have now been moved to `entities`. Emulated Hue configuration under `homeassistant.customize` will be deprecated in the near future. -
+The following are attributes that can be applied in the `customize` section: + +- **emulated_hue_hidden** (*Optional*): Whether or not the entity should be exposed by the emulated Hue bridge. Adding `emulated_hue_hidden: false` will expose the entity to Alexa. The default value for this attribute is controlled by the `expose_by_default` option. +- **emulated_hue_name** (*Optional*): The name that the emulated Hue will use. The default for this is the entity's friendly name. ### {% linkable_title Troubleshooting %} @@ -119,14 +118,14 @@ You can verify that the `emulated_hue` component has been loaded and is respondi - `http://
diff --git a/source/_components/gc100.markdown b/source/_components/gc100.markdown
index 43d74d72b7..063dddcab0 100644
--- a/source/_components/gc100.markdown
+++ b/source/_components/gc100.markdown
@@ -14,7 +14,7 @@ ha_release: 0.57
The Global Caché [GC-100](https://www.globalcache.com/products/gc-100/) can be integrated into Home Assistant. GC-100 is a TCP-controllable
hardware device which has an array of relays, RS232 serial ports, and flexible ports which can be programmed to be either digital inputs or IR blaster outputs. There are a variety of submodels of the GC-100 which have different amounts of each I/O type.
-Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the iTach remote platform (/components/remote.itach/), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché.
+Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the iTach remote platform (https://home-assistant.io/components/remote.itach/), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché.
To enable this device, add the following lines to your `configuration.yaml`:
diff --git a/source/_components/goalfeed.markdown b/source/_components/goalfeed.markdown
deleted file mode 100644
index 5632a8847d..0000000000
--- a/source/_components/goalfeed.markdown
+++ /dev/null
@@ -1,54 +0,0 @@
----
-layout: page
-title: "Goalfeed"
-description: "Instructions on how to setup Goalfeed events within Home Assistant."
-date: 2017-12-13 17:30
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: goalfeed.png
-ha_category: Other
-ha_version: 0.63
----
-
-The `goalfeed` component lets you use your Goalfeed account to trigger events in Home Assistant whenever a NHL or MLB team scores.
-
-To use this component, enter your email address and password from your goalfeed.ca account in your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-goalfeed:
- username: YOUR_E_MAIL_ADDRESS
- password: YOUR_PASSWORD
-```
-
-{% configuration %}
-username:
- required: true
- description: The email address on your goalfeed.ca account.
- type: string
-password:
- required: true
- description: The password on your goalfeed.ca account.
- type: string
-{% endconfiguration %}
-
-Now you can use the goal event type in your automations:
-
-```yaml
-- alias: 'Jets Goal'
- trigger:
- platform: event
- event_type: goal
- event_data:
- team_name: "Winnipeg Jets"
-```
-
-Goal events have the following event data:
-
-- **team**: Three letter code representing the team. This is unique within the leagues, but not unique across the leagues (i.e. 'WPG' or 'TOR').
-- **team_name**: The team that scored (i.e. 'Winnipeg Jets' or 'Toronto Blue Jays').
-- **team_hash**: A unique hash for the team (you can find these values on https://goalfeed.ca/get-teams).
-- **league_id**: A unique number for the league.
-- **league_name**: A the short name of the league (i.e. 'NHL' or 'MLB').
diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown
index edd0b8ebb1..95ef0fff19 100644
--- a/source/_components/google_assistant.markdown
+++ b/source/_components/google_assistant.markdown
@@ -13,10 +13,6 @@ featured: true
ha_release: 0.56
---
-
- Use [Home Assistant Cloud](/cloud/) to integrate with Google Assistant without any effort. -
- The `google_assistant` component allows you to control things via Google Assistant (on your mobile or tablet) or a Google Home device. The Google Assistant component requires a bit more setup than most due to the way Google requires Assistant Apps to be set up. @@ -25,8 +21,6 @@ The Google Assistant component requires a bit more setup than most due to the wa To use Google Assistant, your Home Assistant configuration has to be externally accessible with a hostname and SSL certificate. If you haven't already configured that, you should do so before continuing. -## {% linkable_title Configuration %} - To enable this, add the following lines to your `configuration.yaml` file: ```yaml @@ -47,9 +41,9 @@ google_assistant: aliases: - bright lights - entry lights + type: light light.living_room: expose: false - room: living room ``` Configuration variables: @@ -69,15 +63,15 @@ access_token: required: true type: string agent_user_id: - description: A string to identify the user, e.g., email address. If not provided, the component will generate one. + description: A string to identify the user, e.g. email address. If not provided, the component will generate one. required: false type: string api_key: - description: An API Key generated for the project from [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see step 9 below). If not provided then the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have setup this component you will need to call this service (or command) each time you add a new device that you wish to control via the Google Assistant integration. + description: An API Key generated for the project from [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see setup below). If not provided then the request_sync service is not exposed. required: false type: string expose_by_default: - description: Expose devices in all supported domains by default. If set to false, you need to either expose domains or add the expose configuration option to each entity in entity_config and set it to true. + description: Expose devices in all supported domains by default. required: false default: True type: boolean @@ -107,8 +101,8 @@ entity_config: description: Aliases that can also be used to refer to this entity required: false type: list - room: - description: Allows for associating this device to a Room in Google Assistant. + type: + description: Override how Google Assistant interprets the domain of the entity. For example, set to `light` for a switch entity to have it be handled as a light. required: false type: string {% endconfiguration %} @@ -116,16 +110,15 @@ entity_config: ### {% linkable_title Available domains %} Currently, the following domains are available to be used with Google Assistant, listed with their default types: -- group (on/off) -- input boolean (on/off) -- scene (on) -- script (on) -- switch (on/off) -- fan (on/off) -- light (on/off/brightness/rgb color/color temp) -- cover (on/off/set position (via set brightness)) -- media_player (on/off/set volume (via set brightness)) -- climate (temperature setting) +- group = switch (on/off) +- scene = scene (on) +- script = scene (on) +- switch = switch (on/off) +- fan = switch (on/off) +- light = light (on/off/brightness/rgb color/color temp) +- cover = switch (on/off/set position (brightness) ) +- media_player = switch (on/off/set volume (brightness) ) +- climate = thermostat (temperature setting) It's very important that you use very long strings for `client_id` and `access_token`. Those are essentially the credentials to your Home Assistant instance. You can generate them with the following command: @@ -137,32 +130,58 @@ If you're not using Linux, you can use sites such as [this one](https://www.brow ### {% linkable_title Setup %} -1. Create a new project in the [developer console](https://console.actions.google.com/). +1. Download the [gactions CLI](https://developers.google.com/actions/tools/gactions-cli) to be used later. You can download and run this anywhere and on any machine. Just remember where you put it for later and don't forget to run `chmod +x gactions` to make it executable on Mac or Linux. +2. Create a new file named `project.json` (in the same directory you downloaded `gactions` to) and replace the `[YOUR HOME ASSISTANT URL]` below with the URL you use to access Home Assistant. + Note: This must be an HTTPS URL to work. + +```json +{ + "actions": [{ + "name": "actions.devices", + "deviceControl": { + }, + "fulfillment": { + "conversationName": "automation" + } + }], + "conversations": { + "automation": + { + "name": "automation", + "url": "https://[YOUR HOME ASSISTANT URL]/api/google_assistant" + } + } +} +``` + +3. Create a new project in the [developer console](https://console.actions.google.com/). a. Add/Import project - b. Click on `BUILD` on the `Smart home` card - c. Type in your home assistant url: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / ip address and the port under which your Home Assistant is reachable. - d. Click `Done`. Then click on `Overview`, which will lead you to the app details screen. -2. You'll need to fill out most of the information on that page, but none of it really matters since you won't be addressing the App directly, only through the Smart Home functionality built into Google Assistant. -3. The final item on that page `Account linking` is required for your app to interact with Home Assistant. - a. Grant type: `Implicit` - b. Client ID: The `client_id` from your Home Assistant configuration above - c. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth`. If you have set `api_password:` add this password to the URL `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth?api_password=[YOUR API PASSWORD]`) - d. Configure your client. Add scopes for `email` and `name`. - e. Testing instructions: Enter anything. It doesn't matter since you won't submit this app. -4. Back on the main app draft page. Click `Test Draft`. That will take you to the simulator (which won't work so just close that window). -5. If you haven't already added the component configuration to `configuration.yaml` and restarted Home Assistant, you'll be unable to continue until you have. -6. Open the Google Assistant app and go into `Settings > Home Control` -7. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead you the screen where you can set rooms for your devices or nicknames for your devices. -8. If you want to allow other household users to control the devices: - a. Go to the settings for the project you created in point 1 in the developer console. - b. Under the gear icon, click `Permissions` - c. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role - d. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 4 -9. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project: - a. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) - b. Select your project and click Enable Homegraph API - c. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials - d. Note down the generated API Key and use this in the configuration + b. Go to Build under the Actions SDK box + c. Copy the command that looks like: + + `gactions update --action_package PACKAGE_NAME --project doctest-2d0b8` +4. Replace `PACKAGE_NAME` with `project.json` and run that command in a console from the same directory you saved `project.json` in (you'll need to put `./` before `gactions` so that it reads `./gactions` if you're running it on Linux or Windows). It should output a URL like `https://console.actions.google.com/project/doctest-2d0b8/overview` - go there. +5. You'll need to fill out most of the information on that page, but none of it really matters since you won't be addressing the App directly, only through the Smart Home functionality built into Google Assistant. +6. The final item on that page `Account linking` is required for your app to interact with Home Assistant. + 1. Grant type: `Implicit` + 2. Client ID: The `client_id` from your Home Assistant configuration above + 3. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth`. If you have set `api_password:` add this password to the URL `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth?api_password=[YOUR API PASSWORD]`) + 4. Configure your client. Add scopes for `email` and `name`. + 5. Testing instructions: Enter anything. It doesn't matter since you won't submit this app. +7. Back on the main app draft page. Click `Test Draft`. That will take you to the simulator (which won't work so just close that window). +8. If you haven't already added the component configuration to `configuration.yaml` and restarted Home Assistant, you'll be unable to continue until you have. +8. Open the Google Assistant app and go into `Settings > Home Control` +9. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead to you the screen where you can set rooms for your devices or nicknames for your devices. +10. If you want to allow other household users to control the devices: + 1. Go to the developer console using the address from point 4. + 2. Under the gear icon, click `Permissions` + 3. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role + 4. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 7. +11. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project: + 1. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) + 2. Select your project and click Enable Homegraph API + 3. Go to Credentials and select API Key from Create Credentials + 4. Note down the generated API Key and use this in the configuration ### {% linkable_title Troubleshooting the request_sync service %} @@ -171,7 +190,7 @@ The request_sync service requires that the initial sync from Google includes the The request_sync service may fail with a 404 if the project_id of the Homegraph API differs from the project_id of the Actions SDK found in the preferences of your project on [developer console](https://console.actions.google.com). Resolve this by: 1. Removing your project from the [developer console](https://console.actions.google.com). - 2. Add a new project to the [cloud console](https://console.cloud.google.com). Here you get a new `project_id`. + 2. Add a new project to the [cloud console](https://console.cloud.google.com). Here you get a new project_id. 3. Enable Homegraph API to the new project. 4. Generate a new API key. - 5. Again, create a new project in the [developer console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`. + 5. Again, create a new project in the [developer console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same project_id. diff --git a/source/_components/group.markdown b/source/_components/group.markdown index 924c55e24a..8f781722d2 100644 --- a/source/_components/group.markdown +++ b/source/_components/group.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Group" -description: "Instructions on how to setup groups within Home Assistant." +description: "Instructions how to setup groups within Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false diff --git a/source/_components/hdmi_cec.markdown b/source/_components/hdmi_cec.markdown index ceafd717c6..758f8d468e 100644 --- a/source/_components/hdmi_cec.markdown +++ b/source/_components/hdmi_cec.markdown @@ -1,7 +1,7 @@ --- layout: page title: "HDMI CEC" -description: "Instructions on how to interact with HDMI CEC via Home Assistant." +description: "Instructions how to interact with HDMI CEC via Home Assistant." date: 2016-06-24 19:59 sidebar: true comments: false @@ -31,24 +31,32 @@ If you are using [Hass.io](/hassio/) then just move forward to the configuration #### {% linkable_title Symlinking into virtual environment %} -Create a symlink to the `cec` installation including the _cec.so file. Keep in mind different installation methods will result in different locations of cec. +Create a symlink to the `cec` installation. Keep in mind different installation methods will result in different locations of cec. ```bash -$ ln -s /path/to/your/installation/of/cec /path/to/your/venv/lib/python*/site-packages -$ ln -s /path/to/your/installation/of/_cec.so /path/to/your/venv/lib/python*/site-packages - +$ ln -s /path/to/your/installation/of/cec /path/to/your/venv/lib/python3.4/site-packages ``` - ##### {% linkable_title Symlinking examples: %} For the default virtual environment of a [HASSbian Image for Raspberry Pi](/getting-started/installation-raspberry-pi-image/) the command would be as follows. ```bash -$ ln -s /usr/local/lib/python*/dist-packages/cec /srv/homeassistant/lib/python*/site-packages -$ ln -s /usr/local/lib/python*/dist-packages/_cec.so /srv/homeassistant/lib/python*/site-packages - +$ ln -s /usr/local/lib/python3.4/dist-packages/cec /srv/homeassistant/lib/python3.4/site-packages ``` +For the default virtual environment of a [Raspberry Pi All-In-One installation](/getting-started/installation-raspberry-pi-all-in-one/) the command would be as follows. + +```bash +$ ln -s /usr/local/lib/python3.4/site-packages/cec /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages +``` + +For the default virtual environment of a [Manual installation](/getting-started/installation-raspberry-pi/) the command would be as follows. + +```bash +$ ln -s /usr/local/lib/python3.4/site-packages/cec /srv/hass/hass_venv/lib/python3.4/site-packages +``` + +If after symlinking and adding `hdmi_cec:` to your configuration you are getting the following error in your logs,
`* failed to open vchiq instance` you will also need to add the user account Home Assistant runs under, to the `video` group. To add the Home Assistant user account to the `video` group, run the following command. `$ usermod -a -G video
- It might be necessary to install an additional package: - `$ sudo apt-get install libavahi-compat-libdnssd-dev` -
- -- If you are upgrading Home Assistant from `0.65.x` and have used the HomeKit component, some accessories may not respond or may behave unusually. To fix these problems, you will need to remove the Home Assistant Bridge from your Home, stop Home Assistant and delete the `.homekit.state` file in your configuration folder and follow the Homekit [setup](#setup) steps again. -
- -{% configuration %} - homekit: - description: HomeKit configuration. - required: true - type: map - keys: - auto_start: - description: Flag if the HomeKit Server should start automatically after the Home Assistant Core Setup is done. ([Disable Auto Start](#disable-auto-start)) - required: false - type: boolean - default: true - port: - description: Port for the HomeKit extension. - required: false - type: int - default: 51827 - ip_address: - description: The local network IP address. Only necessary if the default from Home Assistant does not work. - required: false - type: string - filter: - description: Filter entities to available in the `Home` app. ([Configure Filter](#configure-filter)) - required: false - type: map - keys: - include_domains: - description: Domains to be included. - required: false - type: list - include_entities: - description: Entities to be included. - required: false - type: list - exclude_domains: - description: Domains to be excluded. - required: false - type: list - exclude_entities: - description: Entities to be excluded. - required: false - type: list - entity_config: - description: Configuration for specific entities. All subordinate keys are the corresponding entity ids to the domains, e.g. `alarm_control_panel.alarm`. - required: false - type: map - keys: - alarm_control_panel: - description: Additional options for `alarm_control_panel` entities. - required: false - type: map - keys: - code: - description: Code to arm or disarm the alarm in the frontend. - required: false - type: string - default: '' -{% endconfiguration %} - -- If you use Z-Wave, or `discovery:` you'll need to disable auto-start, see the [section below](#disable-auto-start) for details on how to do this. You'll then need to start the HomeKit component once Z-Wave is ready, or an appropriate delay to allow your entities to be discovered. -
- -## {% linkable_title Setup %} - -To enable the `HomeKit` component in Home Assistant, add the following to your configuration file: - -```yaml -# Example for HomeKit setup -homekit: -``` - -After Home Assistant has started, the entities specified by the filter are exposed to `HomeKit` if they are [supported](#supported-components). To add them: -1. Open the Home Assistant frontend. A new card will display the `pin code`. -1. Open the `Home` app. -2. Choose `Add Accessory`, than select `Don't Have a Code or Can't Scan?` and enter the `pin code`. -4. Confirm the you are adding an `Uncertified Accessory` by clicking on `Add Anyway`. -5. Follow the setup be clicking on `Next` and lastly `Done` in the top right hand corner. -6. The `Home Assistant` Bridge and the Accessories should now be listed in the `Home` app. - -After the setup is completed you should be able to control your Home Assistant components through `Home` and `Siri`. - - -## {% linkable_title Considerations %} - - -### {% linkable_title Accessory ID %} - -Currently this component uses the `entity_id` to generate a unique `accessory id (aid)` for `HomeKit`. The `aid` is used to identify a device and save all configurations made for it. This however means that if you decide to change an `entity_id` all configurations for this accessory made in the `Home` app will be lost. - -### {% linkable_title Persistence Storage %} - -Unfortunately `HomeKit` doesn't support any kind of persistent storage - only the configuration for accessories that are added to the `Home Assistant Bridge` are kept. To avoid problems it is recommended to use an automation to always start `HomeKit` with at least the same entities setup. If for some reason some entities are not setup, their config will be deleted. (State unknown or similar will not cause any issues.) - -A common situation might be if you decide to disable parts of the configuration for testing. Please make sure to disable `auto start` and `turn off` the `Start HomeKit` automation (if you have one). - - -## {% linkable_title Disable Auto Start %} - -Depending on your individual setup, it might be necessary to disable `Auto Start` for all accessories to be available for `HomeKit`. Only those entities that are fully setup when the `HomeKit` component is started, can be added. To start `HomeKit` when `auto_start: False`, you can call the service `homekit.start`. - -If you have Z-Wave entities you want exposed to HomeKit then you'll need to disable auto start and then start it after the Z-Wave mesh is ready. This is because the Z-Wave entities won't be fully set up until then. This can be automated using an automation: - -{% raw %} -```yaml -# Example for Z-Wave -homekit: - auto_start: False - -automation: - - alias: 'Start HomeKit' - trigger: - - platform: event - event_type: zwave.network_ready - action: - - service: homekit.start -``` -{% endraw %} - -For a general delay where your component doesn't generate an event, you can also do: - -{% raw %} -```yaml -# Example using a delay after start of Home Assistant -homekit: - auto_start: False - -automation: - - alias: 'Start HomeKit' - trigger: - - platform: homeassistant - event: start - action: - - delay: 00:05 # Waits 5 minutes - - service: homekit.start -``` -{% endraw %} - - -## {% linkable_title Configure Filter %} - -By default no entity will be excluded. To limit which entities are being exposed to `HomeKit`, you can use the `filter` parameter. Keep in mind only [supported components](#supported-components) can be added. - -{% raw %} -```yaml -# Example filter to include specified domains and exclude specified entities -homekit: - filter: - include_domains: - - alarm_control_panel - - light - exclude_entities: - - light.kitchen_light -``` -{% endraw %} - -Filters are applied as follows: - -1. No includes or excludes - pass all entities -2. Includes, no excludes - only include specified entities -3. Excludes, no includes - only exclude specified entities -4. Both includes and excludes: - * Include domain specified - - if domain is included, and entity not excluded, pass - - if domain is not included, and entity not included, fail - * Exclude domain specified - - if domain is excluded, and entity not included, fail - - if domain is not excluded, and entity not excluded, pass - - if both include and exclude domains specified, the exclude domains are ignored - * Neither include or exclude domain specified - - if entity is included, pass (as #2 above) - - if entity include and exclude, the entity exclude is ignored - - -## {% linkable_title Supported Components %} - -The following components are currently supported: - -| Component | Type Name | Description | -| --------- | --------- | ----------- | -| alarm_control_panel | SecuritySystem | All security systems. | -| binary_sensor | Sensor | Support for `co2`, `door`, `garage_door`, `gas`, `moisture`, `motion`, `occupancy`, `opening`, `smoke` and `window` device classes. Defaults to the `occupancy` device class for everything else. | -| climate | Thermostat | All climate devices. | -| cover | GarageDoorOpener | All covers that support `open` and `close` and have `garage` as their `device_class`. | -| cover | WindowCovering | All covers that support `set_cover_position`. | -| cover | WindowCovering | All covers that support `open_cover` and `close_cover` through value mapping. (`open` -> `>=50`; `close` -> `<50`) | -| cover | WindowCovering | All covers that support `open_cover`, `stop_cover` and `close_cover` through value mapping. (`open` -> `>70`; `close` -> `<30`; `stop` -> every value in between) | -| device_tracker | Sensor | Support for `occupancy` device class. | -| light | Light | Support for `on / off`, `brightness` and `rgb_color`. | -| lock | DoorLock | Support for `lock / unlock`. | -| sensor | TemperatureSensor | All sensors that have `Celsius` or `Fahrenheit` as their `unit_of_measurement` or `temperature` as their `device_class`. | -| sensor | HumiditySensor | All sensors that have `%` as their `unit_of_measurement` and `humidity` as their `device_class`. | -| sensor | AirQualitySensor | All sensors that have `pm25` as part of their `entity_id` or `pm25` as their `device_class` | -| sensor | CarbonDioxideSensor | All sensors that have `co2` as part of their `entity_id` or `co2` as their `device_class` | -| sensor | LightSensor | All sensors that have `lm` or `lx` as their `unit_of_measurement` or `illuminance` as their `device_class` | -| switch / remote / input_boolean / script | Switch | All represented as switches. | - - -## {% linkable_title Error reporting %} - -If you encounter any issues or bug and want to report them on `GitHub`, please follow these steps to make it easier for others to help and get your issue solved. - -1. Enable debugging mode: -```yaml -logger: - default: warning - logs: - homeassistant.components.homekit: debug - pyhap: debug -``` -2. Reproduce the bug / problem you have encountered. -3. Stop Home Assistant and copy the log from the log file. That is necessary since some errors only get logged, when Home Assistant is being shutdown. -4. Follow this link: [home-assistant/issues/new](https://github.com/home-assistant/home-assistant/issues/new?labels=component: homekit) and open a new issue. -5. Fill out all fields and especially include the following information: - - The configuration entries for `homekit` and the `component` that is causing the issue. - - The log / traceback you have generated before. - - Screenshots of the failing entity in the `states` panel. diff --git a/source/_components/homekit_controller.markdown b/source/_components/homekit_controller.markdown deleted file mode 100644 index 910c07e036..0000000000 --- a/source/_components/homekit_controller.markdown +++ /dev/null @@ -1,36 +0,0 @@ ---- -layout: page -title: "HomeKit controller support" -description: "Instructions how to integrate your HomeKit devices within Home Assistant." -date: 2018-03-19 21:04 -sidebar: true -comments: false -sharing: true -footer: true -logo: apple-homekit.png -ha_category: Hub -ha_release: 0.68 -ha_iot_class: "Local Polling" ---- - -[HomeKit](https://developer.apple.com/homekit/) controller integration for Home Assistant allows you to connect HomeKit accessories to Home Assistant. This component should not be confused with the [HomeKit](/components/homekit/) component, which allows you to control Home Assistant devices via HomeKit. - -- You may need additional packages to support the HomeKit Python module: - `$ sudo apt-get install libgmp-dev libmpfr-dev libmpc-dev` -
- -There is currently support for the following device types within Home Assistant: - -- [Light](/components/light.homekit_controller/) -- [Switch](/components/switch.homekit_controller/) - -The component will be automatically configured if the [`discovery:`](/components/discovery/) component is enabled and an enable entry added for HomeKit: - -```yaml -discovery: - enable: - - homekit -``` - -For each detected HomeKit accessory, a configuration prompt will appear in the web front end. Use this to provide the HomeKit PIN. Note that HomeKit accessories can only be paired to one device at once. If your device is currently paired with Siri, you will need to reset it in order to pair it with Home Assistant. Once Home Assistant is configured to work with the device, you can export it back to Siri with the [`HomeKit`](/components/homekit/) component. diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index 5deaa8311a..73287f7420 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -2,7 +2,7 @@ layout: page title: "Homematic" description: "Instructions for integrating Homematic into Home Assistant." -date: 2018-02-13 19:10 +date: 2016-11-27 21:38 sidebar: true comments: false sharing: true @@ -13,15 +13,16 @@ ha_iot_class: "Local Push" featured: false --- -The [Homematic](http://www.homematic.com/) component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit. + +The [Homematic](http://www.homematic.com/) component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit. If you are using Homegear with paired [Intertechno](http://intertechno.at/) devices, uni-directional communication is possible as well. Device support is available for most of the wired and wireless devices, as well as a few IP devices. If you have a setup with mixed protocols, you have to configure additional hosts with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`. -If you want to see if a specific device you have is supported, head over to the [pyhomematic](https://github.com/danielperna84/pyhomematic/tree/master/pyhomematic/devicetypes) repository and browse through the source code. A dictionary with the device identifiers (e.g., HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute. +If you want to see if a specific device you have is supported, head over to the [pyhomematic](https://github.com/danielperna84/pyhomematic/tree/master/pyhomematic/devicetypes) repository and browse through the source code. A dictionary with the device identifiers (e.g. HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute. We automatically detect all devices we currently support and try to generate useful names. If you enable name-resolving, we try to fetch names from Metadata (Homegear), via JSON-RPC or the XML-API you may have installed on your CCU. Since this may fail this is disabled by default. -You can manually rename the created entities by using Home Assistant's [Customizing](/docs/configuration/customizing-devices/) feature. With it you are also able to hide entities you don't want to see in the UI. +You can manually rename the created entities by using Home Assistants [Customizing](https://home-assistant.io/getting-started/customizing-devices/) feature. With it you are also able to hide entities you don't want to see in the UI. To set up the component, add the following information to your `configuration.yaml` file: @@ -89,7 +90,7 @@ homematic: host: 127.0.0.1 username: Admin password: secret - + ``` ### {% linkable_title The `resolvenames` option %} @@ -110,7 +111,7 @@ This does *not* affect the entities in Home Assistant. They all use their own co ### {% linkable_title Reading attributes of entities %} -Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the [template sensor](/components/sensor.template/) component. Here's an example of a template sensor that exposes the valve state of a thermostat. +Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the [template sensor](https://home-assistant.io/components/sensor.template/) component. Here's an example of a template sensor that exposes the valve state of a thermostat. ```yaml sensor: @@ -125,7 +126,7 @@ sensor: ### {% linkable_title Variables %} It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables. -The states of the variables are available through the attributes of your hub entity (e.g., `homematic.ccu2`). Use templates (as mentioned above) to make your variables available to automations or as entities. +The states of the variables are available through the attributes of your hub entity (e.g. `homematic.ccu2`). Use templates (as mentioned above) to make your variables available to automations or as entities. The values of variables are polled from the CCU/Homegear in an interval of 30 seconds. Setting the value of a variable happens instantly and is directly pushed. ### {% linkable_title Events %} @@ -137,7 +138,7 @@ When HomeMatic devices change their state or some other internal value, the CCU/ #### {% linkable_title Devices with buttons %} -Devices with buttons (e.g., HM-Sen-MDIR-WM55, remote controls) may not be fully visible in the UI. This is intended, as buttons don't serve any value here and all they do is trigger events. +Devices with buttons (e.g. HM-Sen-MDIR-WM55, remote controls) may not be fully visible in the UI. This is intended, as buttons don't serve any value here and all they do is trigger events. As an example: The HM-Sen-MDIR-WM55 motion detector will be displayed as 2 entities. A motion sensor and a brightness sensor. On top of that we have 2 sets (one set per button) of 4 events: PRESS_SHORT, PRESS_LONG, PRESS_CONT, PRESS_LONG_RELEASE. Be aware, that there are devices which don't provide all of these events. But in general: if you can press it, it usually at least has PRESS_SHORT. @@ -158,17 +159,7 @@ automation: ``` The channel parameter is equal to the channel of the button you are configuring the automation for. You can view the available channels in the UI you use to pair your devices. -The name depends on if you chose to resolve names or not. If not, it will be the device ID (e.g., LEQ1234657). If you chose to resolve names (and that is successful), it will be the name you have set in your CCU or in the metadata (e.g., "Kitchen Switch"). - -You can test whether your button works within Home Assistant if you look at the terminal output. When pressing a button, lines similar to those should appear: - -```bash -2018-01-27 11:51:32 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=MEQ1234567:6, interface_id=homeassistant-CCU2, key=PRESS_SHORT, value=True -2018-01-27 11:51:32 INFO (MainThread) [homeassistant.core] Bus:Handling-Please note, that sources from `trusted_networks` won't be banned automatically. -
- -## {% linkable_title Hosting files %} - -If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config` on Hass.io, `.homeassistant` elsewhere). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`. - -- If you've had to create the `www/` folder for the first time, you'll need to restart Home Assistant. +Please note, that sources from `trusted_networks` won't be banned automatically.
diff --git a/source/_components/hue.markdown b/source/_components/hue.markdown index f172c6b0ff..fb73a05824 100644 --- a/source/_components/hue.markdown +++ b/source/_components/hue.markdown @@ -33,20 +33,12 @@ hue: Configuration variables: -- **host**: IP address of the device, eg. 192.168.1.10. Required if not using the `discovery` component to discover Hue bridges. +- **host** (*Optional*): IP address of the device, eg. 192.168.1.10. Required if not using the `discovery` component to discover Hue bridges. - **allow_unreachable** (*Optional*): (true/false) This will allow unreachable bulbs to report their state correctly. - **filename** (*Optional*): Make this unique if specifying multiple Hue hubs. +- **allow_in_emulated_hue** (*Optional*): (true/false) Enable this to block all Hue entities from being added to the `emulated_hue` component. - **allow_hue_groups** (*Optional*): (true/false) Enable this to stop Home Assistant from importing the groups defined on the Hue bridge. -```yaml -# Example configuration.yaml entry specifying optional parameters -hue: - bridges: - - host: DEVICE_IP_ADDRESS - allow_unreachable: true - allow_hue_groups: true -``` - ### {% linkable_title Migrating from older configuration %} In previous versions of the Hue component the configuration looked different: diff --git a/source/_components/ifttt.manything.markdown b/source/_components/ifttt.manything.markdown index 84d0228bc1..7288afb90b 100644 --- a/source/_components/ifttt.manything.markdown +++ b/source/_components/ifttt.manything.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ManyThing" -description: "Instructions on how to setup ManyThing support with IFTTT." +description: "Instructions how to setup ManyThing support with IFTTT." date: 2015-09-07 18:00 sidebar: true comments: false diff --git a/source/_components/ifttt.markdown b/source/_components/ifttt.markdown index 9f48303946..764138d272 100644 --- a/source/_components/ifttt.markdown +++ b/source/_components/ifttt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "IFTTT" -description: "Instructions on how to setup IFTTT within Home Assistant." +description: "Instructions how to setup IFTTT within Home Assistant." date: 2015-09-07 18:00 sidebar: true comments: false @@ -21,7 +21,7 @@ ifttt: key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ``` -`key` is your API key which can be obtained by viewing the **Settings** of the [Webhooks applet](https://ifttt.com/services/maker_webhooks/settings). It's the last part of the URL (e.g., https://maker.ifttt.com/use/MYAPIKEY) you will find under **My Applets** > **Webhooks** > **Settings**. +`key` is your API key which can be obtained by viewing the **Settings** of the [Webhooks applet](https://ifttt.com/services/maker_webhooks/settings). It's the last part of the URL (e.g. https://maker.ifttt.com/use/MYAPIKEY) you will find under **My Applets** > **Webhooks** > **Settings**.diff --git a/source/_components/image_processing.dlib_face_detect.markdown b/source/_components/image_processing.dlib_face_detect.markdown index f427590256..6673146847 100644 --- a/source/_components/image_processing.dlib_face_detect.markdown +++ b/source/_components/image_processing.dlib_face_detect.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Dlib Face Detect" -description: "Instructions on how to integrate Dlib Face Detect into Home Assistant." +description: "Instructions how to integrate Dlib Face Detect into Home Assistant." date: 2017-05-05 00:00 sidebar: true comments: false diff --git a/source/_components/image_processing.dlib_face_identify.markdown b/source/_components/image_processing.dlib_face_identify.markdown index 34690d6b8f..1e47bf13e4 100644 --- a/source/_components/image_processing.dlib_face_identify.markdown +++ b/source/_components/image_processing.dlib_face_identify.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Dlib Face Identify" -description: "Instructions on how to integrate Dlib Face Identify into Home Assistant." +description: "Instructions how to integrate Dlib Face Identify into Home Assistant." date: 2017-01-25 00:00 sidebar: true comments: false @@ -13,7 +13,7 @@ featured: false ha_release: 0.44 --- -The `dlib_face_identify` image processing platform allows you to use the [Dlib](http://www.dlib.net/) through Home Assistant. This platform allow you to identify persons on camera and fire an event with identify persons. +The `dlib_face_identify` image processing platform allows you to use the [Dlib](http://www.dlib.net/) through Home Assistant. This platform allow you to identify persons on camera and fire a event with identify persons. For using the result inside an automation rule, take a look at the [component](/components/image_processing/) page. @@ -36,7 +36,3 @@ Configuration variables: - **entity_id** (*Required*): A camera entity id to get picture from. - **name** (*Optional*): This parameter allows you to override the name of your `image_processing` entity. - **faces** array (*Required*): List of faces sources. - -
-If the platform fails to load because it could not install its requirement, install cmake: `sudo apt-get install cmake`. -
diff --git a/source/_components/image_processing.markdown b/source/_components/image_processing.markdown index 1f1507bf28..6f010ebad2 100644 --- a/source/_components/image_processing.markdown +++ b/source/_components/image_processing.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Image Processing" -description: "Instructions on how to setup image processing with Home Assistant." +description: "Instructions how to setup image processing with Home Assistant." date: 2017-01-09 00:00 sidebar: true comments: false diff --git a/source/_components/image_processing.microsoft_face_detect.markdown b/source/_components/image_processing.microsoft_face_detect.markdown index 06cca72d26..39aecb1534 100644 --- a/source/_components/image_processing.microsoft_face_detect.markdown +++ b/source/_components/image_processing.microsoft_face_detect.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Microsoft Face Detect" -description: "Instructions on how to integrate Microsoft Face Detect into Home Assistant." +description: "Instructions how to integrate Microsoft Face Detect into Home Assistant." date: 2017-01-25 00:00 sidebar: true comments: false diff --git a/source/_components/image_processing.microsoft_face_identify.markdown b/source/_components/image_processing.microsoft_face_identify.markdown index eb6d0a110f..76fb2ad1be 100644 --- a/source/_components/image_processing.microsoft_face_identify.markdown +++ b/source/_components/image_processing.microsoft_face_identify.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Microsoft Face Identify" -description: "Instructions on how to integrate Microsoft Face Identify into Home Assistant." +description: "Instructions how to integrate Microsoft Face Identify into Home Assistant." date: 2017-01-25 00:00 sidebar: true comments: false diff --git a/source/_components/image_processing.openalpr_cloud.markdown b/source/_components/image_processing.openalpr_cloud.markdown index 96e180a705..3a13097c87 100644 --- a/source/_components/image_processing.openalpr_cloud.markdown +++ b/source/_components/image_processing.openalpr_cloud.markdown @@ -1,7 +1,7 @@ --- layout: page title: "OpenALPR Cloud" -description: "Instructions on how to integrate licences plates with OpenALPR cloud into Home Assistant." +description: "Instructions how to integrate licences plates with OpenALPR cloud into Home Assistant." date: 2017-01-09 00:00 sidebar: true comments: false @@ -13,7 +13,7 @@ featured: false ha_release: 0.36 --- -[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](/components/automation/). +[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](https://home-assistant.io/components/automation/). For using the result inside an automation rule, take a look at the [component](/components/image_processing/) page. diff --git a/source/_components/image_processing.openalpr_local.markdown b/source/_components/image_processing.openalpr_local.markdown index d5da4bab3e..593a921261 100644 --- a/source/_components/image_processing.openalpr_local.markdown +++ b/source/_components/image_processing.openalpr_local.markdown @@ -1,7 +1,7 @@ --- layout: page title: "OpenALPR Local" -description: "Instructions on how to integrate licences plates with OpenALPR local into Home Assistant." +description: "Instructions how to integrate licences plates with OpenALPR local into Home Assistant." date: 2017-01-09 00:00 sidebar: true comments: false @@ -14,7 +14,7 @@ ha_release: 0.36 redirect_from: /components/openalpr/ --- -[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](/components/automation/). +[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](https://home-assistant.io/components/automation/). For using inside automation look on [component](/components/image_processing) page. diff --git a/source/_components/image_processing.opencv.markdown b/source/_components/image_processing.opencv.markdown index 9e485ec6c3..db6bfd2d5c 100644 --- a/source/_components/image_processing.opencv.markdown +++ b/source/_components/image_processing.opencv.markdown @@ -1,7 +1,7 @@ --- layout: page title: "OpenCV" -description: "Instructions on how to integrate OpenCV image processing into Home Assistant." +description: "Instructions how to integrate OpenCV image processing into Home Assistant." date: 2017-01-25 00:00 sidebar: true comments: false diff --git a/source/_components/image_processing.seven_segments.markdown b/source/_components/image_processing.seven_segments.markdown index a5944d821b..13249bc52b 100644 --- a/source/_components/image_processing.seven_segments.markdown +++ b/source/_components/image_processing.seven_segments.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Seven segments display" -description: "Instructions on how to use OCR for seven segments displays into Home Assistant." +description: "Instructions how to use OCR for seven segments displays into Home Assistant." date: 2017-05-18 08:00 sidebar: true comments: false diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown index 9df07711f8..4252068c03 100644 --- a/source/_components/influxdb.markdown +++ b/source/_components/influxdb.markdown @@ -23,11 +23,11 @@ The default InfluxDB configuration doesn't enforce authentication. If you have i influxdb: ``` -You will still need to create a database named `home_assistant` via InfluxDB's command line interface. For instructions on how to create a database check the [InfluxDB documentation](https://docs.influxdata.com/influxdb/latest/introduction/getting_started/#creating-a-database) relevant to the version you have installed. +You will still need to create a database named `home_assistant` via InfluxDB's web interface or command line. For instructions how to create a database check the [InfluxDB documentation](https://docs.influxdata.com/influxdb/latest/introduction/getting_started/#creating-a-database) relevant to the version you have installed. Configuration variables: -- **host** (*Optional*): IP address of your database host, e.g., 192.168.1.10. Defaults to `localhost`. +- **host** (*Optional*): IP address of your database host, e.g. 192.168.1.10. Defaults to `localhost`. - **port** (*Optional*): Port to use. Defaults to 8086. - **username** (*Optional*): The username of the database user. The user needs read/write privileges on the database. - **password** (*Optional*): The password for the database user account. @@ -35,9 +35,10 @@ Configuration variables: - **ssl** (*Optional*): Use https instead of http to connect. Defaults to false. - **verify_ssl** (*Optional*): Verify SSL certificate for https request. Defaults to false. - **max_retries** (*Optional*): Allow the component to retry if there was a network error when transmitting data +- **retry_queue_limit** (*Optional*): If retry enabled, specify how much calls are allowed to be queued for retry. - **default_measurement** (*Optional*): Measurement name to use when an entity doesn't have a unit. Defaults to entity id. - **override_measurement** (*Optional*): Measurement name to use instead of unit or default measurement. This will store all data points in a single measurement. -- **component_config**, **component_config_domain**, **component_config_glob** (*Optional*): These attributes contains component-specific override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. +- **component_config**, **component_config_domain**, **component_config_glob** (*Optional*): These attributes contains component-specific override values. See [Customizing devices and services](https://home-assistant.io/getting-started/customizing-devices/) for format. - **override_measurement** (*Optional*): Measurement name to use for this component, takes precedence over the global 'override_measurement' and component-specific 'unit_of_measurement' attribute. - **exclude** (*Optional*): Configure which components should be excluded from recording to InfluxDB. - **entities** (*Optional*): The list of entity ids to be excluded from recording to InfluxDB. diff --git a/source/_components/input_boolean.markdown b/source/_components/input_boolean.markdown index b2b23aeeff..ff2aa46ca8 100644 --- a/source/_components/input_boolean.markdown +++ b/source/_components/input_boolean.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Input Boolean" -description: "Instructions on how to integrate the Input Boolean component into Home Assistant." +description: "Instructions how to integrate the Input Boolean component into Home Assistant." date: 2016-01-17 16:58 sidebar: true comments: false diff --git a/source/_components/input_datetime.markdown b/source/_components/input_datetime.markdown index 462b309e7e..7337114357 100644 --- a/source/_components/input_datetime.markdown +++ b/source/_components/input_datetime.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Input Datetime" -description: "Instructions on how to integrate the Input Datetime component into Home Assistant." +description: "Instructions how to integrate the Input Datetime component into Home Assistant." date: 2017-09-14 16:01 sidebar: true comments: false @@ -65,7 +65,7 @@ input_datetime: A datetime input entity's state exports several attributes that can be useful in automations and templates. | Attribute | Description | -| ----- | ----- | +| --------- | ----------- | | `has_time` | `true` if this entity has a time. | `has_date` | `true` if this entity has a date. | `year`-Before version 0.55 this component was known as `input_slider` and did not have the `mode` configuration option. Also, service `select_value` is now `set_value`. +Before version 0.55 this component was known as `input_slider` and did not have the `mode` configuration option.
The `input_number` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well. @@ -39,6 +39,7 @@ input_number: mode: box ``` + {% configuration %} input_number: description: Alias for the input. Multiple entries are allowed. diff --git a/source/_components/input_select.markdown b/source/_components/input_select.markdown index 8e59002ccf..bf25b89d5f 100644 --- a/source/_components/input_select.markdown +++ b/source/_components/input_select.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Input Select" -description: "Instructions on how to integrate the Input Select component into Home Assistant." +description: "Instructions how to integrate the Input Select component into Home Assistant." date: 2016-02-02 17:00 sidebar: true comments: false diff --git a/source/_components/input_text.markdown b/source/_components/input_text.markdown index 284ab5ea36..2fa07711af 100644 --- a/source/_components/input_text.markdown +++ b/source/_components/input_text.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Input Text" -description: "Instructions on how to integrate the Input Text component into Home Assistant." +description: "Instructions how to integrate the Input Text component into Home Assistant." date: 2016-03-15 06:00 sidebar: true comments: false @@ -12,7 +12,7 @@ ha_category: Automation ha_release: 0.53 --- -The `input_text` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. It can also be configured in password mode (obscured text). +The `input_text` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. ```yaml # Example configuration.yaml entries @@ -27,9 +27,6 @@ input_text: text3: name: Text 3 pattern: '[a-fA-F0-9]*' - text4: - name: Text 4 - mode: password ``` {% configuration %} @@ -62,11 +59,6 @@ input_text: required: false type: String default: empty - mode: - description: Can specify `text` or `password`. Elements of type "password" provide a way for the user to securely enter a value. - required: false - type: String - default: text {% endconfiguration %} ### {% linkable_title Restore State %} diff --git a/source/_components/insteon_hub.markdown b/source/_components/insteon_hub.markdown index 5c9813bc5c..03bf4b8a6e 100644 --- a/source/_components/insteon_hub.markdown +++ b/source/_components/insteon_hub.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon Hub" -description: "Instructions on how to setup the Insteon Hub within Home Assistant." +description: "Instructions how to setup the Insteon Hub within Home Assistant." date: 2016-01-27 08:00 sidebar: true comments: false @@ -32,6 +32,6 @@ insteon_hub: Configuration variables: -- **username** (*Required*): The username used to access the Insteon interface (e.g., the [connect.insteon.com](http://connect.insteon.com/) site). +- **username** (*Required*): The username used to access the Insteon interface (e.g. the [connect.insteon.com](http://connect.insteon.com/) site). - **password** (*Required*): The password used to access the Insteon interface. - **api_key** (*Required*): The Insteon REST API key emailed to you once you are approved in the Insteon Developer program. diff --git a/source/_components/insteon_local.markdown b/source/_components/insteon_local.markdown index 40ed93c1d5..fba1087171 100644 --- a/source/_components/insteon_local.markdown +++ b/source/_components/insteon_local.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon (local)" -description: "Instructions on how to setup the Insteon Hub locally within Home Assistant." +description: "Instructions how to setup the Insteon Hub locally within Home Assistant." date: 2016-12-18 08:00 sidebar: true comments: false diff --git a/source/_components/insteon_plm.markdown b/source/_components/insteon_plm.markdown index 9e15bb0f7d..f28db9b74c 100644 --- a/source/_components/insteon_plm.markdown +++ b/source/_components/insteon_plm.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon PLM" -description: "Instructions on how to setup an Insteon USB PLM locally within Home Assistant." +description: "Instructions how to setup an Insteon USB PLM locally within Home Assistant." date: 2017-02-19 16:00 sidebar: true comments: false @@ -16,15 +16,13 @@ ha_version: 0.39 This component adds "local push" support for INSTEON PowerLinc Modems allowing linked INSTEON devices to be used within Home Assistant as lights, switches, and binary sensors. Device support is provided by the underlying [insteonplm] -package. It is known to work with the [2413U] USB and [2412S] RS242 flavors -of PLM and the [2448A7] USB stick. This component does not work with the -IP-based hub products. For that, you'll want the "Insteon (Local)" component -instead. +package. It is known to work with both the [2413U] USB and [2412S] +RS242 flavors of PLM. This component does not work with the IP-based hub +products. For that, you'll want the "Insteon (Local)" component instead. [insteonplm]: https://github.com/nugget/python-insteonplm [2413U]: https://www.insteon.com/powerlinc-modem-usb [2412S]: https://www.insteon.com/powerlinc-modem-serial -[2448A7]: https://www.smarthome.com/insteon-2448a7-portable-usb-adapter.html ```yaml @@ -32,83 +30,23 @@ instead. insteon_plm: port: SERIAL_PORT device_override: - - address: ADDRESS - cat: CATEGORY - subcat: SUBCATEGORY - firmware: FIRMWARE - product_key: PRODUCT_KEY + - address: INSTEON_ADDRESS + platform: DEVICE_PLATFORM ``` + Configuration variables: -- **port** (*Required*): The port for your device, e.g., `/dev/ttyUSB0` -- **device_override** (*Optional*): Override the default device definition - - *ADDRESS* is found on the device itself in the form 1A.2B.3C or 1a2b3c - - *CATEGORY* is found in the back of the device's User Guide in the form of - 0x00 - 0xff - - *SUBCATEGORY* is found in the back of the device's User Guide in the form - of 0x00 - 0xff - - *FIRMWARE* and *PRODUCT_KEY* are more advanced options and will typically - not be used. - -### {% linkable_title Autodiscovery %} - -The first time autodiscovery runs, the duration may require up to 20 seconds -per device. Subsequent startups will occur much quicker using cached device -information. If a device is not recognized during autodiscovery, you can add -the device to the **device_override** configuration. - -In order for a device to be discovered it must be linked to the PLM as either -a responder or a controller. - -### {% linkable_title Linking Devices to the PLM %} - -In order for any two Insteon devices to talk with one another, they must be -linked. For an overview of device linking please read the Insteon page on -[understanding linking]. The Insteon PLM module supports All-Linking through -[Development Tools] service calls. The following services are available: - -In order for any two Insteon devices to talk with one another, they must be -linked. For an overview of device linking, please read the Insteon page on -[understanding linking]. The Insteon PLM module supports All-Linking through -[Development Tools] service calls. The following services are available: -- **insteon_plm.add_all_link**: Tells the Insteon Modem (IM) start All-Linking -mode. Once the IM is in All-Linking mode, press the link button on the device -to complete All-Linking. -- **insteon_plm.delete_all_link**: Tells the Insteon Modem (IM) to remove an -All-Link record from the All-Link Database of the IM and a device. Once the IM -is set to delete the link, press the link button on the corresponding device -to complete the process. -- **insteon_plm.load_all_link_database**: Load the All-Link Database for a -device. WARNING - Loading a device All-Link database is very time consuming -and inconsistent. This may take a LONG time and may need to be repeated to -obtain all records. -- **insteon_plm.print_all_link_database**: Print the All-Link Database for a -device. Requires that the All-Link Database is loaded into memory. -- **insteon_plm.print_im_all_link_database**: Print the All-Link Database for -the INSTEON Modem (IM). - -If you are looking for more advanced options, you can use the -[insteonplm_interactive] command line tool that is distributed with the -[insteonplm] Python module. Please see the documentation on the [insteonplm] -GitHub site. Alternatively, you can download [HouseLinc] which runs on any -Windows PC, or you can use [Insteon Terminal] which is open source and runs -on most platforms. SmartHome no longer supports HouseLinc, but it still -works. Insteon Terminal is a very useful tool but please read the disclaimers -carefully, they are important. - -[understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking -[Development Tools]: https://www.home-assistant.io/docs/tools/dev-tools/ -[HouseLinc]: https://www.smarthome.com/houselinc.html -[Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal -[insteonplm_interactive]: https://github.com/nugget/python-insteonplm#command-line-interface +- **port** (*Required*): The port for your device, e.g. `/dev/ttyUSB0` +- **device_override** (*Optional*): Override the default device platform + ### {% linkable_title Customization %} -The only configuration item that is absolutely necessary is the port so that -Home Assistant can connect to the PLM. This will expose all the supported -INSTEON devices which exist in the modem’s ALL-Link database. However, devices -will only be shown by their INSTEON hex address (e.g., “1A.2B.3C”) which can -be a bit unwieldy. As you link and unlink devices using the ‘Set’ buttons, -they’ll be added and removed from Home Assistant automatically. +The only configuration item that is absolutely necessary is the port so that +Home Assistant can connect to the PLM. This will expose all the supported INSTEON +devices which exist in the modem's ALL-Link database. However, devices will +only be shown by their INSTEON hex address (e.g. "1A.2B.3C") which can be a bit +unwieldy. As you link and unlink devices using the 'Set' buttons, they'll be +added and removed from Home Assistant automatically. You can use the normal Home Assistant [device customization] section of your configuration to assign friendly names and special icons to your devices. This @@ -120,14 +58,14 @@ devices. ### {% linkable_title Device Overrides %} INSTEON devices are added to Home Assistant using the platform(s) that make the -most sense given the model and features of the hardware. The features of the -INSTEON device are built into the Home Assistant platform. Changing the -platform is not recommended. There are two primary uses for the -**device_override** feature. -- Devices that do not respond during autodiscovery. This is common for battery - operated devices. -- Devices that have not been fully developed. This allows an unknown device to - be mapped to a device that operates similarly to another device. +most sense given the model and features of the hardware. In most cases this is +unambiguous, but sometimes the component will not be able to guess the actual +usage of the device. For example, there might be a table lamp plugged into an +INSTEON appliance relay module. By default, this will show as a 'switch' +device in Home Assistant, but it really should be a 'light' device. For +exceptions like this, the component supports a device platform override. You +can set any device (by address) to explicitly use a specific platform if the +default is not correct. ### {% linkable_title Example Configuration with Options%} @@ -145,20 +83,7 @@ homeassistant: insteon_plm: port: /dev/ttyUSB0 device_override: - - address: a1b2c3 # Hidden Door Sensor [2845-222] - cat: 0x10 - subcat: 0x11 + - address: a1b2c3 # Icon Appliance Module for bedside lamp + platform: light # make it a light instead of a switch ``` -### {% linkable_title What NOT to do %} - -Insteon PLM is a top level component and device discovery will identify -the Home Assistant platform the device belongs in. As such, do not -declare Insteon devices in other platforms. For example, this configuration -will NOT work: - -```yaml -light: - - platform: insteon_plm - address: 1a2b3c -``` diff --git a/source/_components/ios.markdown b/source/_components/ios.markdown deleted file mode 100644 index 44ac2fa88e..0000000000 --- a/source/_components/ios.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "iOS" -description: "Instructions on how to use the iOS companion app with Home Assistant." -date: 2018-04-06 08:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: apple.png -ha_category: Hub -featured: false -ha_release: 0.31 -ha_iot_class: depends ---- - -The `ios` component is the Home Assistant part for using the iOS companion app. For further details please check the [iOS section](/docs/ecosystem/ios/) in the documentation for further details. diff --git a/source/_components/isy994.markdown b/source/_components/isy994.markdown index 211917fe56..558765a764 100644 --- a/source/_components/isy994.markdown +++ b/source/_components/isy994.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ISY994 Controller" -description: "Instructions on how to setup the ISY994 controller within Home Assistant." +description: "Instructions how to setup the ISY994 controller within Home Assistant." date: 2015-01-20 22:36 sidebar: true comments: false @@ -45,7 +45,7 @@ Once the ISY controller is configured, it will automatically import any binary s An Insteon door/window sensor will show up as a single Binary Sensor rather than two discrete devices like it does in the ISY994 admin panel. Note that when in "Two Nodes" mode, the sensor will have an UNKNOWN state until the sensor changes for the first time since the last Home Assistant reboot. If you do not use Insteon scenes that are controlled directly from the door sensor, you may prefer to set the sensor to "One Node" mode using the ISY Admin Panel. -Each Insteon leak sensor will also show up as a single Binary Sensor as opposed to the two nodes seen in the ISY994. The name of the device will be based on what the parent node is named in the ISY994, which is typically the one with "-Dry" at the end of the name. This may be confusing, because "On" means wet in Home Assistant. You can rename this node either in the ISY994 Admin Panel (which will change the entity_id in Home Assistant) or assign a `friendly_name` in the [Customization section](/docs/configuration/customizing-devices/) of your configuration. +Each Insteon leak sensor will also show up as a single Binary Sensor as opposed to the two nodes seen in the ISY994. The name of the device will be based on what the parent node is named in the ISY994, which is typically the one with "-Dry" at the end of the name. This may be confusing, because "On" means wet in Home Assistant. You can rename this node either in the ISY994 Admin Panel (which will change the entity_id in Home Assistant) or assign a `friendly_name` in the [Customization section](https://home-assistant.io/docs/configuration/customizing-devices/) of your configuration. If your leak or door/window sensor supports heartbeats, a new binary_sensor device will be added to Home Assistant to represent the battery state. The sensor will stay "Off" so long as the daily heartbeats occur. If a heartbeat is missed, the sensor will flip to "On". The name of this device will be based on the heartbeat node in the ISY. @@ -125,7 +125,7 @@ My Programs ``` A device is created by creating a directory, with the name for the device, under any of the following root directories: - * *HA.binary_sensor* will create a binary sensor (see [Customizing Devices](/getting-started/customizing-devices/) to set the sensor class) + * *HA.binary_sensor* will create a binary sensor (see [Customizing Devices](https://home-assistant.io/getting-started/customizing-devices/) to set the sensor class) * *HA.cover* will create a cover * *HA.fan* will create a fan * *HA.lock* will create a lock diff --git a/source/_components/juicenet.markdown b/source/_components/juicenet.markdown index 74cc2fdb89..5015022c55 100644 --- a/source/_components/juicenet.markdown +++ b/source/_components/juicenet.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Juicenet" -description: "Instructions on how to setup WiFi-equipped Juicenet charging stations with Home Assistant." +description: "Instructions how to setup WiFi-equipped Juicenet charging stations with Home Assistant." date: 2017-05-20 22:00 sidebar: true comments: false @@ -15,12 +15,10 @@ ha_release: 0.47 The `juicenet` sensor platform pulls data from a [JuiceNet](https://emotorwerks.com/products/juicenet/) charging station equipped with a wifi connection. It will access and make available all of the devices attached to your account. -## {% linkable_title Configuration %} - To enable the platform in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry juicenet: access_token: ACCESS_TOKEN ``` diff --git a/source/_components/keyboard.markdown b/source/_components/keyboard.markdown index 00dad71931..07b3e2db26 100644 --- a/source/_components/keyboard.markdown +++ b/source/_components/keyboard.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Keyboard" -description: "Instructions on how to simulate key presses with Home Assistant." +description: "Instructions how to simulate key presses with Home Assistant." date: 2015-01-24 14:39 sidebar: true comments: false diff --git a/source/_components/keyboard_remote.markdown b/source/_components/keyboard_remote.markdown index aeefd01e63..f1d80bfa97 100644 --- a/source/_components/keyboard_remote.markdown +++ b/source/_components/keyboard_remote.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Keyboard Remote" -description: "Instructions on how to use a keyboard to remote control Home Assistant." +description: "Instructions how to use a keyboard to remote control Home Assistant." date: 2016-09-28 14:39 sidebar: true comments: false diff --git a/source/_components/kira.markdown b/source/_components/kira.markdown index b32ae95eac..d2c2594834 100644 --- a/source/_components/kira.markdown +++ b/source/_components/kira.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Kira" -description: "Instructions on how to integrate Keene Electronics IR over IP modules (Kira) into Home Assistant." +description: "Instructions how to integrate Keene Electronics IR over IP modules (Kira) into Home Assistant." date: 2017-05-07 00:00 sidebar: true comments: false @@ -76,7 +76,7 @@ Configuration variables: - **type** (*Optional*): The type of this code. If this field is omitted, the type will be autodetected if possible. - **repeat** (*Optional*): The number of times to repeat this code (on transmit). Default is 1. -Some manufacturers (e.g., Samsung) require an IR code to be sent a number of times in a row in rapid succession (usually 3). This doesn't apply to the vast majority of devices, but it can be helpful if needed. +Some manufacturers (e.g. Samsung) require an IR code to be sent a number of times in a row in rapid succession (usually 3). This doesn't apply to the vast majority of devices, but it can be helpful if needed. ### {% linkable_title Code Types %} diff --git a/source/_components/knx.markdown b/source/_components/knx.markdown index 7acfae7676..4fd471efeb 100644 --- a/source/_components/knx.markdown +++ b/source/_components/knx.markdown @@ -31,7 +31,6 @@ There is currently support for the following device types within Home Assistant: - [Light](/components/light.knx) - [Thermostat](/components/climate.knx) - [Notify](/components/notify.knx) -- [Scene](/components/scene.knx) ### {% linkable_title Configuration %} @@ -84,6 +83,7 @@ knx: - **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus - **fire_event_filter** (*Optional*): If `fire_event` is set `fire_event_filter` has to be specified. `fire_event_filter` defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme Assistant event bus. - **state_updater** (*Optional*): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behavior. +- **time_address** (*Optional*): Broadcast current local time to KNX bus with configured group address. ### {% linkable_title Services %} @@ -98,27 +98,6 @@ Service Data: {"address": "1/0/15", "payload": 0} * **address**: KNX group address * **payload**: Payload, either an integer or an array of integers -### {% linkable_title Exposing sensor values or time to knx bus %} - -KNX component is able to expose time or sensor values to KNX bus. The component will broadcast any change of the exposed value to the KNX bus and answer read requests to the specified group address: - -```yaml -# Example configuration.yaml entry -knx: - expose:: - - type: 'temperature' - entity_id: 'sensor.owm_temperature' - address: '0/0/2' - - type: 'time' - address: '0/0/1' - - type: 'datetime' - address: '0/0/23' -``` - -* **type**: Type of the exposed value. Either time or datetime or any supported type of [KNX Sensor](/components/sensor.knx/) (e.g., "temperature" or "humidity"). -* **entity_id**: Entity id of the HASS component to be exposed. Not necessary for types time and datetime. -* **address**: KNX group address. - ### {% linkable_title Known issues %} diff --git a/source/_components/light.abode.markdown b/source/_components/light.abode.markdown index f362107791..bb6d597dee 100644 --- a/source/_components/light.abode.markdown +++ b/source/_components/light.abode.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Abode Light" -description: "Instructions on how to integrate Abode lights into Home Assistant." +description: "Instructions how to integrate Abode lights into Home Assistant." date: 2017-08-26 13:28 sidebar: true comments: false diff --git a/source/_components/light.ads.markdown b/source/_components/light.ads.markdown index aaedc1c12f..b5188cf33e 100644 --- a/source/_components/light.ads.markdown +++ b/source/_components/light.ads.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ADS Light" -description: Instructions on how to set up ADS lights within Home Assistant +description: Instructions how to set up ADS lights within Home Assistant date: 2017-10-25 10:00 sidebar: true comments: false diff --git a/source/_components/light.avion.markdown b/source/_components/light.avion.markdown index 68c40b1aac..74260e9395 100644 --- a/source/_components/light.avion.markdown +++ b/source/_components/light.avion.markdown @@ -21,6 +21,8 @@ To enable these lights, add the following lines to your `configuration.yaml` fil # Example configuration.yaml entry light: - platform: avion + username: testuser@fakedomain.com + password: foobar ``` Configuration variables: diff --git a/source/_components/light.blinksticklight.markdown b/source/_components/light.blinksticklight.markdown index c11da280ac..9deab2be84 100644 --- a/source/_components/light.blinksticklight.markdown +++ b/source/_components/light.blinksticklight.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Blinkstick" -description: "Instructions on how to setup Blinkstick lights within Home Assistant." +description: "Instructions how to setup Blinkstick lights within Home Assistant." date: 2015-10-08 10:00 sidebar: true comments: false diff --git a/source/_components/light.blinkt.markdown b/source/_components/light.blinkt.markdown index ad2d6200f8..617e81cac2 100644 --- a/source/_components/light.blinkt.markdown +++ b/source/_components/light.blinkt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Blinkt!" -description: "Instructions on how to setup Blinkt! RGB LED lights within Home Assistant." +description: "Instructions how to setup Blinkt! RGB LED lights within Home Assistant." date: 2017-04-30 9:00 sidebar: true comments: false diff --git a/source/_components/light.decora_wifi.markdown b/source/_components/light.decora_wifi.markdown index 7fc68d0dcf..48ce82aa3a 100644 --- a/source/_components/light.decora_wifi.markdown +++ b/source/_components/light.decora_wifi.markdown @@ -8,12 +8,12 @@ comments: false sharing: true footer: true ha_category: Light -ha_iot_class: "Cloud Polling" +ha_iot_class: "Local Polling" logo: leviton.png ha_release: 0.51 --- -Support for [Leviton Decora Wi-Fi](http://www.leviton.com/en/products/lighting-controls/decora-smart-with-wifi) dimmers/switches via the MyLeviton API. +Support for [Leviton Decora Wi-Fi](http://www.leviton.com/en/products/lighting-controls/decora-smart-with-wifi) dimmers/switches. Supported devices (tested): @@ -26,18 +26,13 @@ To enable these lights, add the following lines to your `configuration.yaml` fil # Example configuration.yaml entry light: - platform: decora_wifi - username: YOUR_USERNAME - password: YOUR_PASSWORD + username: my_leviton_user_email@email.com + password: my_leviton_password ``` -{% configuration %} -username: - description: Your "My Leviton" app email address/user name. - required: true - type: string -password: - description: Your "My Leviton" app password. - required: true - type: string -{% endconfiguration %} +Configuration variables: + +- **username** (*Required*): Your "My Leviton" app email address/user name. +- **password** (*Required*): Your "My Leviton" app password. + diff --git a/source/_components/light.eufy.markdown b/source/_components/light.eufy.markdown deleted file mode 100644 index d8596c0048..0000000000 --- a/source/_components/light.eufy.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Eufy Lights" -description: "Instructions on how to integrate Eufy LED lights into Home Assistant." -date: 2018-04-09 19:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: eufy.png -ha_category: Light -ha_iot_class: "Local Polling" -ha_release: 0.68 ---- - -The `eufy` platform allows you to control your [Eufy](http://www.eufylife.com) lights from within Home Assistant. - -They will be automatically discovered if the [Eufy](/components/eufy/) component is enabled. - diff --git a/source/_components/light.flux_led.markdown b/source/_components/light.flux_led.markdown index 871ba222e2..e74e6942d9 100644 --- a/source/_components/light.flux_led.markdown +++ b/source/_components/light.flux_led.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Flux Led/MagicLight" -description: "Instructions on how to setup Flux led/MagicLight within Home Assistant." +description: "Instructions how to setup Flux led/MagicLight within Home Assistant." date: 2015-07-17 20:09 sidebar: true comments: false diff --git a/source/_components/light.greenwave.markdown b/source/_components/light.greenwave.markdown index 16f8e16099..a0cba942d4 100644 --- a/source/_components/light.greenwave.markdown +++ b/source/_components/light.greenwave.markdown @@ -27,7 +27,7 @@ light: host: XXX.XXX.XXX.XXX version: 3 ``` -The version option is the major revision of your firmware, which should be 2 or 3. If you are running Version 2, there are no extra steps. If you are running Version 3, you must press the Sync button on the gateway prior to the first launch of Home Assistant, so a token can be grabbed. Once Home Assistant has started, you can either press the Sync button again or wait for it to time out manually. +The version option is the major revision of your firmware, which should be 2 or 3. If you are running Version 2, there are no extra steps. If you are running Version 3, you must press the Sync button on the gateway prior to the first launch of Home Assistant, so a token can be grabbed. Once home assistant has started, you can either press the Sync button again or wait for it to time out manually. {% configuration %} host: diff --git a/source/_components/light.group.markdown b/source/_components/light.group.markdown deleted file mode 100644 index 4ec8262463..0000000000 --- a/source/_components/light.group.markdown +++ /dev/null @@ -1,63 +0,0 @@ ---- -layout: page -title: "Light Group" -description: "Instructions for how to setup light groups within Home Assistant." -date: 2018-02-23 11:41 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Light -ha_release: 0.65 -ha_iot_class: "Local Push" -logo: home-assistant.png ---- - -The group light platform lets you combine multiple lights into one entity. All child lights of a light group can still be used as usual, but controlling the state of the grouped light will forward the command to each child light. - -To enable this platform in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -light: - - platform: group - name: Kitchen Lights - entities: - - light.kitchen_ceiling_lights - - light.kitchen_under_cabinet_lights - - light.kitchen_spot_lights - - light.pendant_lights -``` - -{% configuration %} - name: - description: The name of the light group. Defaults to "Light Group". - required: false - type: string - entities: - description: A list of entities to be included in the light group. - required: true - type: string list -{% endconfiguration %} - -
-
-Example of the light group "Kitchen Lights".
-
diff --git a/source/_components/light.homekit_controller.markdown b/source/_components/light.homekit_controller.markdown deleted file mode 100644 index f3f7243a10..0000000000 --- a/source/_components/light.homekit_controller.markdown +++ /dev/null @@ -1,16 +0,0 @@ ---- -layout: page -title: "HomeKit Light" -description: "Instructions how to setup HomeKit lights within Home Assistant." -date: 2017-03-19 21:08 -sidebar: true -comments: false -sharing: true -footer: true -logo: apple-homekit.png -ha_category: Light -ha_iot_class: "Local Polling" -ha_release: 0.68 ---- - -To get your HomeKit lights working with Home Assistant, follow the instructions for the general [HomeKit controller component](/components/homekit_controller/). diff --git a/source/_components/light.homematic.markdown b/source/_components/light.homematic.markdown index 86249ce98e..b2223ae9e4 100644 --- a/source/_components/light.homematic.markdown +++ b/source/_components/light.homematic.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Homematic Light" -description: "Instructions on how to integrate Homematic lights within Home Assistant." +description: "Instructions how to integrate Homematic lights within Home Assistant." date: 2016-06-28 08:30 sidebar: true comments: false diff --git a/source/_components/light.hue.markdown b/source/_components/light.hue.markdown index 59e8b8e970..8cd9aad47e 100644 --- a/source/_components/light.hue.markdown +++ b/source/_components/light.hue.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Philips Hue Light" -description: "Instructions on how to integrate Philips Hue lights into Home Assistant." +description: "Instructions how to integrate Philips Hue lights into Home Assistant." date: 2015-03-23 20:09 sidebar: true comments: false diff --git a/source/_components/light.hyperion.markdown b/source/_components/light.hyperion.markdown index 7cba5e18f4..7f3b23ad6c 100644 --- a/source/_components/light.hyperion.markdown +++ b/source/_components/light.hyperion.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Hyperion" -description: "Instructions on how to integrate Hyperion into Home Assistant." +description: "Instructions how to integrate Hyperion into Home Assistant." date: 2015-10-25 22:43 sidebar: true comments: false diff --git a/source/_components/light.ihc.markdown b/source/_components/light.ihc.markdown index 214f19564b..741d2168cd 100644 --- a/source/_components/light.ihc.markdown +++ b/source/_components/light.ihc.markdown @@ -1,7 +1,7 @@ --- layout: page title: "IHC Light" -description: "Instructions on how to integrate IHC lights within Home Assistant." +description: "Instructions how to integrate IHC lights within Home Assistant." date: 2017-11-27 13:35 sidebar: true comments: false diff --git a/source/_components/light.insteon_hub.markdown b/source/_components/light.insteon_hub.markdown index f581706b92..82c4df9aa5 100644 --- a/source/_components/light.insteon_hub.markdown +++ b/source/_components/light.insteon_hub.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon Hub Light" -description: "Instructions on how to setup the Insteon Hub Lights within Home Assistant." +description: "Instructions how to setup the Insteon Hub Lights within Home Assistant." date: 2016-09-10 08:00 sidebar: true comments: false diff --git a/source/_components/light.insteon_local.markdown b/source/_components/light.insteon_local.markdown index b9aacb3250..06af902dfd 100644 --- a/source/_components/light.insteon_local.markdown +++ b/source/_components/light.insteon_local.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon (Local) Light" -description: "Instructions on how to setup the Insteon Hub Lights locally within Home Assistant." +description: "Instructions how to setup the Insteon Hub Lights locally within Home Assistant." date: 2016-12-18 08:00 sidebar: true comments: false diff --git a/source/_components/light.insteon_plm.markdown b/source/_components/light.insteon_plm.markdown index 65026cf576..7c95d8dfe4 100644 --- a/source/_components/light.insteon_plm.markdown +++ b/source/_components/light.insteon_plm.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Insteon PLM Light" -description: "Instructions on how to setup Insteon PLM lights locally within Home Assistant." +description: "Instructions how to setup Insteon PLM lights locally within Home Assistant." date: 2017-02-19 17:00 sidebar: true comments: false @@ -13,5 +13,5 @@ ha_iot_class: "Local Push" ha_version: 0.39 --- -The `insteon_plm` light platform lets you control your dimmable light switches through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on an USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component. +The `insteon_plm` light platform lets you control your sensors through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on an USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component. diff --git a/source/_components/light.isy994.markdown b/source/_components/light.isy994.markdown index 6c03413c8b..8ae450edfc 100644 --- a/source/_components/light.isy994.markdown +++ b/source/_components/light.isy994.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ISY994 Light" -description: "Instructions on how to integrate ISY994 lights into Home Assistant." +description: "Instructions how to integrate ISY994 lights into Home Assistant." date: 2016-09-03 23:00 sidebar: true comments: false diff --git a/source/_components/light.lifx.markdown b/source/_components/light.lifx.markdown index 04f444540f..805cb67e68 100644 --- a/source/_components/light.lifx.markdown +++ b/source/_components/light.lifx.markdown @@ -1,7 +1,7 @@ --- layout: page title: "LIFX" -description: "Instructions on how to integrate LIFX into Home Assistant." +description: "Instructions how to integrate LIFX into Home Assistant." date: 2016-01-27 08:00 sidebar: true comments: false diff --git a/source/_components/light.limitlessled.markdown b/source/_components/light.limitlessled.markdown index 2dcf4d9c7a..bc0849cbca 100644 --- a/source/_components/light.limitlessled.markdown +++ b/source/_components/light.limitlessled.markdown @@ -18,7 +18,7 @@ ha_release: pre 0.7 ### {% linkable_title Setup %} -Before configuring Home Assistant, make sure you can control your bulbs or LEDs with the MiLight mobile application. Discover your bridge(s) IP address. You can do this via your router or a mobile application like Fing ([android](https://play.google.com/store/apps/details?id=com.overlook.android.fing&hl=en) or [iTunes](https://itunes.apple.com/us/app/fing-network-scanner/id430921107?mt=8)). Keep in mind that LimitlessLED bulbs are controlled via groups. You can not control an individual bulb via the bridge, unless it is in a group by itself. Note that you can assign an `rgbw`, `rgbww`, `white` and `dimmer` group to the same group number, effectively allowing 16 groups (4 `rgbww`, 4 `rgbw`, 4 `white` and 4 `dimmer`) per bridge. +Before configuring Home Assistant, make sure you can control your bulbs or LEDs with the MiLight mobile application. Discover your bridge(s) IP address. You can do this via your router or a mobile application like Fing ([android](https://play.google.com/store/apps/details?id=com.overlook.android.fing&hl=en) or [iTunes](https://itunes.apple.com/us/app/fing-network-scanner/id430921107?mt=8)). Keep in mind that LimitlessLED bulbs are controlled via groups. You can not control an individual bulb via the bridge, unless it is in a group by itself. Note that you can assign an `rgbw`, `rgbww` and `white` group to the same group number, effectively allowing 12 groups (4 `rgbww`, 4 `rgbw` and 4 `white`) per bridge. To add `limitlessled` to your installation, add the following to your `configuration.yaml` file: @@ -38,9 +38,6 @@ light: type: rgbw name: Kitchen fade: on - - number: 4 - type: dimmer - name: Livingroom - host: 192.168.1.11 groups: - number: 1 @@ -59,7 +56,7 @@ Configuration variables: - **groups** array (*Required*): The list of available groups. - **number** (*Required*): Group number (`1`-`4`). Corresponds to the group number on the remote. These numbers may overlap only if the type is different. - **name** (*Required*): Any name you'd like. Must be unique among all configured groups. - - **type** (*Optional*): Type of group. Choose either `rgbww`, `rgbw`, `white`, `bridge-led` or `dimmer`. `rgbw` is the default if you don't specify this entry. Use `bridge-led` to control the built-in LED of newer WiFi bridges. + - **type** (*Optional*): Type of group. Choose either `rgbww`, `rgbw`, `white`, or `bridge-led`. `rgbw` is the default if you don't specify this entry. Use `bridge-led` to control the built-in LED of newer WiFi bridges. - **fade** (*Optional*): Fade behavior. Defaults to `off`. If turned on, the group is faded out before being turned off. This makes for a more pleasing transition at the expense of wall switch usability, since the light will turn back on at the lowest brightness if it is power cycled. ### {% linkable_title Properties %} @@ -77,29 +74,9 @@ Refer to the [light]({{site_root}}/components/light/) documentation for general - When using a legacy WiFi bridge (before v6), you can observe on the MiLight mobile application, you can not select a specific brightness or temperature - you can only step each property up or down. There is no indication of which step you are on. This restriction, combined with the unreliable nature of LimitlessLED transmissions, means that setting white bulb properties is done on a best-effort basis. The only very reliable settings are the minimum and maximum of each property. - *Temperature*: Wifi bridge v6 supports 101 temperature steps; older versions only 10. - *Brightness*: Wifi bridge v6 supports 101 brightness steps; older versions only 10. -- **Dimmer** (Only supported on v6 bridges) - - This type is for a single color LED dimmer like the 1CH MiLight dimmer module or similar. This type is only supported by the version 6 Wifi bridges. - - *Brightness*: Wifi bridge v6 supports 101 brightness steps. - **Transitions** - If a transition time is set, the group will transition between the current settings and the target settings for the duration specified. Transitions from or to white are not possible - the color will change immediately. ### {% linkable_title Initialization & Synchronization %} -When starting Home Assistant, the last recorded state will be shown. This might no longer match the actual state of the bulbs. - -If you control your LimitlessLED lights via the MiLight mobile application or other means while Home Assistant is running, Home Assistant can not track those changes and you may observe obsolete information. - -This lack of synchronization is due to a LimitlessLED limitation. - -
-
-
configuration.yaml
Turns one light on or multiple lights on using [groups]({{site_root}}/components/group/).
-Most lights do not support all attributes. You can check the platform documentation of your particular light for hints, but in general, you will have to try things out and see what works.
+Most lights do not support all attributes. You can check the platform documentation of your particular light for hints but in general you will have to try things out and see what works.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all.
| `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state.
-| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten.
-| `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100.
-| `xy_color` | yes | A list containing two floats representing the xy color you want the light to be. Two comma-separated floats that represent the color in XY. You can find a great chart here: [Hue Color Chart](https://developers.meethue.com/documentation/core-concepts#color_gets_more_complicated).
-| `rgb_color` | yes | A list containing three integers between 0 and 255 representing the RGB color you want the light to be. Three comma-separated integers that represent the color in RGB. Note that the specified RGB value will not change the light brightness, only the color.
+| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define a xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten.
+| `xy_color` | yes | A list containing two floats representing the xy color you want the light to be. Two comma separated floats that represent the color in XY.
+| `rgb_color` | yes | A list containing three integers representing the rgb color you want the light to be. Three comma separated integers that represent the color in RGB. You can find a great chart here: [Hue Color Chart](http://www.developers.meethue.com/documentation/hue-xy-values)
| `white_value` | yes | Integer between 0 and 255 for how bright a dedicated white LED should be.
| `color_temp` | yes | An integer in mireds representing the color temperature you want the light to be.
| `kelvin` | yes | Alternatively, you can specify the color temperature in Kelvin.
-| `color_name` | yes | A human-readable string of a color name, such as `blue` or `goldenrod`. All [CSS3 color names](https://www.w3.org/TR/css-color-3/#svg-color) are supported.
+| `color_name` | yes | A human readable string of a color name, such as `blue` or `goldenrod`. All [CSS3 color names](https://www.w3.org/TR/2010/PR-css3-color-20101028/#svg-color) are supported.
| `brightness` | yes | Integer between 0 and 255 for how bright the color should be.
| `brightness_pct`| yes | Alternatively, you can specify brightness in percent (a number between 0 and 100).
| `flash` | yes | Tell light to flash, can be either value `short` or `long`.
| `effect`| yes | Applies an effect such as `colorloop` or `random`.
-In order to apply attributes to an entity, you will need to add `data:` to the configuration. See example below +In order to apply attributes to an entity you will need to add `data:` to the configuration. See example below
```yaml diff --git a/source/_components/light.mochad.markdown b/source/_components/light.mochad.markdown index 9721e9d6c9..2902cb71be 100644 --- a/source/_components/light.mochad.markdown +++ b/source/_components/light.mochad.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Mochad Light" -description: "Instructions on how to integrate X10 Mochad lights into Home Assistant." +description: "Instructions how to integrate X10 Mochad lights into Home Assistant." date: 2017-07-14 11:29 sidebar: true comments: false @@ -11,14 +11,13 @@ ha_category: Light ha_release: 0.51 --- -The `mochad` light platform lets you control an X10 enabled dimmer/light device. - - +The `mochad` light platform lets you control an X10 enabled dimmer/light +device. To enable this sensor, you first have to set up the [mochad component](/components/mochad/) and then add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry light: - platform: mochad devices: diff --git a/source/_components/light.mqtt.markdown b/source/_components/light.mqtt.markdown index e92f859fb7..33f76eb5cc 100644 --- a/source/_components/light.mqtt.markdown +++ b/source/_components/light.mqtt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MQTT Light" -description: "Instructions on how to setup MQTT lights within Home Assistant." +description: "Instructions how to setup MQTT lights within Home Assistant." date: 2015-11-13 08:30 sidebar: true comments: false @@ -14,8 +14,6 @@ ha_iot_class: depends The `mqtt` light platform lets you control your MQTT enabled lights. It supports setting brightness, color temperature, effects, flashing, on/off, RGB colors, transitions, XY colors and white values. -## {% linkable_title Configuration %} - In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with a `RETAIN` flag, the MQTT light will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state of the switch will be `false` / `off`. When a state topic is not available, the light will work in optimistic mode. In this mode, the light will immediately change state after every command. Otherwise, the light will wait for state confirmation from the device (message from `state_topic`). @@ -23,7 +21,7 @@ When a state topic is not available, the light will work in optimistic mode. In Optimistic mode can be forced, even if the `state_topic` is available. Try to enable it, if experiencing incorrect light operation. ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry light: - platform: mqtt command_topic: "office/rgb1/light/switch" @@ -57,7 +55,7 @@ brightness_value_template: required: false type: string color_temp_command_topic: - description: The MQTT topic to publish commands to change the light’s color temperature state. The color temperature command slider has a range of 153 to 500 mireds (micro reciprocal degrees). + description: The MQTT topic to publish commands to change the light’s color temperature state. The color temperature command slider has a range of 157 to 500 mireds (micro reciprocal degrees). required: false type: string color_temp_state_topic: @@ -97,12 +95,12 @@ payload_on: description: The payload that represents enabled state. required: false type: string - default: "ON" + default: ON payload_off: description: The payload that represents disabled state. required: false type: string - default: "OFF" + default: OFF qos: description: The maximum QoS level of the state topic. required: false @@ -122,7 +120,7 @@ rgb_command_topic: required: false type: string rgb_state_topic: - description: The MQTT topic subscribed to receive RGB state updates. The expected payload is the RGB values separated by commas, for example `255,0,127`. + description: The MQTT topic subscribed to receive RGB state updates. required: false type: string rgb_value_template: @@ -145,7 +143,7 @@ white_value_state_topic: description: The MQTT topic subscribed to receive white value updates. required: false type: string -white_value_template: +white_value_value_template: description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the white value." required: false type: string @@ -187,7 +185,7 @@ payload_not_available: ## {% linkable_title Comparison of light MQTT platforms %} -| Function | [`mqtt`](/components/light.mqtt/) | [`mqtt_json`](/components/light.mqtt_json/) | [`mqtt_template`](/components/light.mqtt_template/) | +| Function | [`mqtt`](https://home-assistant.io/components/light.mqtt/) | [`mqtt_json`](https://home-assistant.io/components/light.mqtt_json/) | [`mqtt_template`](https://home-assistant.io/components/light.mqtt_template/) | |-------------------|------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------| | Brightness | ✔ | ✔ | ✔ | | Color temperature | ✔ | ✔ | ✔ | @@ -196,7 +194,6 @@ payload_not_available: | RGB Color | ✔ | ✔ | ✔ | | Transitions | ✘ | ✔ | ✔ | | XY Color | ✔ | ✔ | ✘ | -| HS Color | ✘ | ✔ | ✘ | | White Value | ✔ | ✔ | ✔ | ## {% linkable_title Examples %} @@ -207,9 +204,8 @@ In this section you will find some real life examples of how to use this sensor. To enable a light with brightness and RGB support in your installation, add the following to your `configuration.yaml` file: -{% raw %} ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry light: - platform: mqtt name: "Office Light RGB" @@ -219,29 +215,28 @@ light: brightness_command_topic: "office/rgb1/brightness/set" rgb_state_topic: "office/rgb1/rgb/status" rgb_command_topic: "office/rgb1/rgb/set" - state_value_template: "{{ value_json.state }}" - brightness_value_template: "{{ value_json.brightness }}" - rgb_value_template: "{{ value_json.rgb | join(',') }}" + state_value_template: "{% raw %}{{ value_json.state }}{% endraw %}" + brightness_value_template: "{% raw %}{{ value_json.brightness }}{% endraw %}" + rgb_value_template: "{% raw %}{{ value_json.rgb | join(',') }}{% endraw %}" qos: 0 payload_on: "ON" payload_off: "OFF" optimistic: false ``` -{% endraw %} ### {% linkable_title Brightness and no RGB support %} To enable a light with brightness (no RGB version) in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry light: - platform: mqtt name: "Office light" - state_topic: "office/light/status" - command_topic: "office/light/switch" - brightness_state_topic: 'office/light/brightness' - brightness_command_topic: 'office/light/brightness/set' + state_topic: "office/rgb1/light/status" + command_topic: "office/rgb1/light/switch" + brightness_state_topic: 'office/rgb1/light/brightness' + brightness_command_topic: 'office/rgb1/light/brightness/set' qos: 0 payload_on: "ON" payload_off: "OFF" @@ -253,18 +248,19 @@ light: To enable a light that sends only brightness topics to turn it on, add the following to your `configuration.yaml` file. The `command_topic` is only used to send an off command in this case: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry light: - platform: mqtt name: "Brightness light" state_topic: "office/light/status" command_topic: "office/light/switch" payload_off: "OFF" - brightness_state_topic: 'office/light/brightness' - brightness_command_topic: 'office/light/brightness/set' + brightness_state_topic: 'office/rgb1/light/brightness' + brightness_command_topic: 'office/rgb1/light/brightness/set' on_command_type: 'brightness' ``` + ### {% linkable_title Implementations %} - A [basic example](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_light) using a nodeMCU board (ESP8266) to control its built-in LED (on/off). diff --git a/source/_components/light.mqtt_json.markdown b/source/_components/light.mqtt_json.markdown index 6e70c8be89..bdcfaaab11 100644 --- a/source/_components/light.mqtt_json.markdown +++ b/source/_components/light.mqtt_json.markdown @@ -23,12 +23,10 @@ This platform supports on/off, brightness, RGB colors, XY colors, color temperat "color_temp": 155, "color": { "r": 255, - "g": 180, - "b": 200, - "x": 0.406, - "y": 0.301, - "h": 344.0, - "s": 29.412 + "g": 255, + "b": 255, + "x": 0.123, + "y": 0.123 }, "effect": "colorloop", "state": "ON", @@ -128,11 +126,6 @@ xy: required: false type: boolean default: false -hs: - description: Flag that defines if the light supports HS colors. - required: false - type: boolean - default: false availability_topic: description: The MQTT topic subscribed to receive availability (online/offline) updates. required: false @@ -154,12 +147,12 @@ payload_not_available:- RGB, XY and HSV can not be used at the same time in `state_topic` messages. Make sure that only one of the color models is in the "color" section of the state MQTT payload. + XY and RGB can not be used at the same time. If both are provided, XY overrides RGB.
## {% linkable_title Comparison of light MQTT platforms %} -| Function | [`mqtt`](/components/light.mqtt/) | [`mqtt_json`](/components/light.mqtt_json/) | [`mqtt_template`](/components/light.mqtt_template/) | +| Function | [`mqtt`](https://home-assistant.io/components/light.mqtt/) | [`mqtt_json`](https://home-assistant.io/components/light.mqtt_json/) | [`mqtt_template`](https://home-assistant.io/components/light.mqtt_template/) | |-------------------|------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------| | Brightness | ✔ | ✔ | ✔ | | Color temperature | ✔ | ✔ | ✔ | @@ -168,7 +161,6 @@ payload_not_available: | RGB Color | ✔ | ✔ | ✔ | | Transitions | ✘ | ✔ | ✔ | | XY Color | ✔ | ✔ | ✘ | -| HS Color | ✘ | ✔ | ✘ | | White Value | ✔ | ✔ | ✔ | ## {% linkable_title Examples %} @@ -223,32 +215,7 @@ Home Assistant will then convert its 8bit value in the message to and from the d ```json { "brightness": 4095, - "state": "ON" -} -``` - -### {% linkable_title HS Color %} - -To use a light with hue+saturation as the color model, set `hs` to `true` in the platform configuration: - -```yaml -light: - - platform: mqtt_json - name: mqtt_json_hs_light - state_topic: "home/light" - command_topic: "home/light/set" - hs: True -``` - -Home Assistant expects the hue values to be in the range 0 to 360 and the saturation values to be scaled from 0 to 100. For example, the following is a blue color shade: - -```json -{ "state": "ON", - "color": { - "h": 24.0, - "s": 100.0 - } } ``` @@ -260,6 +227,4 @@ Home Assistant expects the hue values to be in the range 0 to 360 and the satura - [MQTT JSON Light](https://github.com/mertenats/Open-Home-Automation/tree/master/ha_mqtt_rgbw_light_with_discovery) is another implementation for ESP8266 including [MQTT discovery](/docs/mqtt/discovery/). -- [esphomelib](https://github.com/OttoWinter/esphomelib) is a library for ESP8266 and ESP32 boards that has many of Home Assistant's MQTT features (like [discovery](/docs/mqtt/discovery/)) pre-implemented and provides high-level abstractions for components such as lights or sensors. - -- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/components/light.mqtt_json/) platform and supports ON/OFF, RGBW colours, brightness, colour temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well. \ No newline at end of file +- [esphomelib](https://github.com/OttoWinter/esphomelib) is a library for ESP32-based boards that has many of Home Assistant's MQTT features (like [discovery](/docs/mqtt/discovery/)) pre-implemented and provides high-level abstractions for components such as lights or sensors. diff --git a/source/_components/light.mqtt_template.markdown b/source/_components/light.mqtt_template.markdown index 11b4372672..5a13ea9dfb 100644 --- a/source/_components/light.mqtt_template.markdown +++ b/source/_components/light.mqtt_template.markdown @@ -123,7 +123,7 @@ payload_not_available: ## {% linkable_title Comparison of light MQTT platforms %} -| Function | [`mqtt`](/components/light.mqtt/) | [`mqtt_json`](/components/light.mqtt_json/) | [`mqtt_template`](/components/light.mqtt_template/) | +| Function | [`mqtt`](https://home-assistant.io/components/light.mqtt/) | [`mqtt_json`](https://home-assistant.io/components/light.mqtt_json/) | [`mqtt_template`](https://home-assistant.io/components/light.mqtt_template/) | |-------------------|------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------| | Brightness | ✔ | ✔ | ✔ | | Color temperature | ✔ | ✔ | ✔ | @@ -132,7 +132,6 @@ payload_not_available: | RGB Color | ✔ | ✔ | ✔ | | Transitions | ✘ | ✔ | ✔ | | XY Color | ✔ | ✔ | ✘ | -| HS Color | ✘ | ✔ | ✘ | | White Value | ✔ | ✔ | ✔ | ## {% linkable_title Examples %} @@ -141,7 +140,7 @@ In this section you find some real life examples of how to use this light. ### {% linkable_title Simple string payload %} -For a simple string payload with the format `state,brightness,r-g-b` (e.g., `on,255,255-255-255`), add the following to your `configuration.yaml` file: +For a simple string payload with the format `state,brightness,r-g-b` (e.g. `on,255,255-255-255`), add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_components/light.mysensors.markdown b/source/_components/light.mysensors.markdown index 5f91aa43fe..4bf9a9d28a 100644 --- a/source/_components/light.mysensors.markdown +++ b/source/_components/light.mysensors.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MySensors Light" -description: "Instructions on how to integrate MySensors lights into Home Assistant." +description: "Instructions how to integrate MySensors lights into Home Assistant." date: 2016-10-01 15:00 +0200 sidebar: true comments: false diff --git a/source/_components/light.mystrom.markdown b/source/_components/light.mystrom.markdown index 9cc2555fb1..f9ceacdb22 100644 --- a/source/_components/light.mystrom.markdown +++ b/source/_components/light.mystrom.markdown @@ -1,7 +1,7 @@ --- layout: page title: "myStrom WiFi Bulb" -description: "Instructions on how to integrate myStrom WiFi Bulbs into Home Assistant." +description: "Instructions how to integrate myStrom WiFi Bulbs into Home Assistant." date: 2017-04-18 06:00 sidebar: true comments: false diff --git a/source/_components/light.nanoleaf_aurora.markdown b/source/_components/light.nanoleaf_aurora.markdown deleted file mode 100644 index 4f066dc7b2..0000000000 --- a/source/_components/light.nanoleaf_aurora.markdown +++ /dev/null @@ -1,52 +0,0 @@ ---- -layout: page -title: "Nanoleaf Aurora Light Panel" -description: "Instructions how to integrate Nanoleaf Aurora Light Panels into Home Assistant." -date: 2018-01-04 20:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: nanoleaf_aurora_light.png -ha_category: Light -ha_iot_class: "Local Polling" -featured: false -ha_release: 0.67 ---- - -### {% linkable_title Configuration Sample %} - -To enable the Aurora lights, add the following lines to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -light: - - platform: nanoleaf_aurora - host: 192.168.1.10 - token: xxxxxxxxxxxxxxxxxxxxx -``` - -{% configuration %} -host: - description: IP address or host-name of the device, e.g., 192.168.1.10. - required: true - type: string -token: - description: The *auth* token that you get via *POST* to */api/v1/new* - required: true - type: string -name: - description: Name of the component, make this unique if you have multiple Light Panels - required: false - type: string - default: Aurora -{% endconfiguration %} - -### {% linkable_title Getting The Auth Token %} - -1. Make sure that your Nanoleaf Aurora Panel is fully patched (as of the time of writing the latest version was 2.2.0) -2. Hold down the *ON* button on the Panel for 5 seconds; the LED will start flashing -3. Issue a *POST* request to the API endpoint, e.g., via `$ curl -i -X POST http://192.168.1.155:16021/api/v1/new` -4. The output should include the auth token like *{"auth_token":"xxxxxxxxxxxxxxxxxxxxx"}*, copy the resulting token into your configuration - -If you get a 403 Forbidden message, you probably did not press the *ON* button long enough. The time-frame to get a valid token is only 30 seconds, so you have to be quick to issue the curl request. diff --git a/source/_components/light.osramlightify.markdown b/source/_components/light.osramlightify.markdown index df1abeece9..86fa342c9b 100644 --- a/source/_components/light.osramlightify.markdown +++ b/source/_components/light.osramlightify.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Osram Lightify" -description: "Instructions on how to integrate Osram Lightify into Home Assistant." +description: "Instructions how to integrate Osram Lightify into Home Assistant." date: 2016-05-29 08:00 sidebar: true comments: false diff --git a/source/_components/light.piglow.markdown b/source/_components/light.piglow.markdown index c2664af84c..d261a81648 100644 --- a/source/_components/light.piglow.markdown +++ b/source/_components/light.piglow.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Piglow" -description: "Instructions on how to setup Piglow LED's within Home Assistant." +description: "Instructions how to setup Piglow LED's within Home Assistant." date: 2017-01-13 18:00 sidebar: true comments: false diff --git a/source/_components/light.qwikswitch.markdown b/source/_components/light.qwikswitch.markdown index 13f61413f6..e1f600c98f 100644 --- a/source/_components/light.qwikswitch.markdown +++ b/source/_components/light.qwikswitch.markdown @@ -1,7 +1,7 @@ --- layout: page title: "QwikSwitch Light" -description: "Instructions on how to integrate Qwikswitch dimmers and relays as lights into Home Assistant." +description: "Instructions how to integrate Qwikswitch dimmers and relays as lights into Home Assistant." date: 2016-05-04 00:00 sidebar: true comments: false diff --git a/source/_components/light.rflink.markdown b/source/_components/light.rflink.markdown index cc56e6de3e..ebba128f88 100644 --- a/source/_components/light.rflink.markdown +++ b/source/_components/light.rflink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "RFLink Light" -description: "Instructions on how to integrate RFLink lights into Home Assistant." +description: "Instructions how to integrate RFLink lights into Home Assistant." date: 2016-01-04 sidebar: true comments: false diff --git a/source/_components/light.rfxtrx.markdown b/source/_components/light.rfxtrx.markdown index b6a1b707cf..ee5c513fe8 100644 --- a/source/_components/light.rfxtrx.markdown +++ b/source/_components/light.rfxtrx.markdown @@ -1,7 +1,7 @@ --- layout: page title: "RFXtrx Light" -description: "Instructions on how to integrate RFXtrx lights into Home Assistant." +description: "Instructions how to integrate RFXtrx lights into Home Assistant." date: 2015-10-08 10:15 sidebar: true comments: false diff --git a/source/_components/light.scsgate.markdown b/source/_components/light.scsgate.markdown index 07df0ca0f7..5625b43cfb 100644 --- a/source/_components/light.scsgate.markdown +++ b/source/_components/light.scsgate.markdown @@ -1,7 +1,7 @@ --- layout: page title: "SCSGate Light" -description: "Instructions on how to integrate SCSGate lights into Home Assistant." +description: "Instructions how to integrate SCSGate lights into Home Assistant." date: 2016-01-31 19:30 sidebar: true comments: false diff --git a/source/_components/light.sensehat.markdown b/source/_components/light.sensehat.markdown index 55e09b1219..b2bb9dbce5 100644 --- a/source/_components/light.sensehat.markdown +++ b/source/_components/light.sensehat.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Sense HAT Light" -description: "Instructions on how to setup Sense HAT LED lights within Home Assistant." +description: "Instructions how to setup Sense HAT LED lights within Home Assistant." date: 2017-04-29 16:00 sidebar: true comments: false diff --git a/source/_components/light.tellstick.markdown b/source/_components/light.tellstick.markdown index 9c66e121ec..a81d238464 100644 --- a/source/_components/light.tellstick.markdown +++ b/source/_components/light.tellstick.markdown @@ -1,7 +1,7 @@ --- layout: page title: "TellStick Light" -description: "Instructions on how to integrate TellStick lights into Home Assistant." +description: "Instructions how to integrate TellStick lights into Home Assistant." date: 2015-08-06 19:00 sidebar: true comments: false @@ -15,7 +15,7 @@ ha_iot_class: "Assumed State" This `tellstick` light platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) dimmers. -To use your TellStick device, you first have to set up your [Tellstick hub](/components/tellstick/) and then add the following to your `configuration.yaml` file: +To use your TellStick device, you first have to set up your [Tellstick hub](https://home-assistant.io/components/tellstick/) and then add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_components/light.template.markdown b/source/_components/light.template.markdown index 9d1315b310..58648b4735 100755 --- a/source/_components/light.template.markdown +++ b/source/_components/light.template.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Template Light" -description: "Instructions on how to integrate Template Lights into Home Assistant." +description: "Instructions how to integrate Template Lights into Home Assistant." date: 2016-05-18 20:32 sidebar: true comments: false @@ -51,10 +51,6 @@ light: description: Name to use in the frontend. required: false type: string - entity_id: - description: A list of entity IDs so the light only reacts to state changes of these entities. This can be used if the automatic analysis fails to find all relevant entities. - required: false - type: [string, list] value_template: description: Defines a template to get the state of the light. required: false diff --git a/source/_components/light.tplink.markdown b/source/_components/light.tplink.markdown index 158504bcae..71fc4e9717 100644 --- a/source/_components/light.tplink.markdown +++ b/source/_components/light.tplink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "TP-Link Bulb" -description: "Instructions on how to integrate TP-Link bulbs into Home Assistant." +description: "Instructions how to integrate TP-Link bulbs into Home Assistant." date: 2017-07-25 08:00 sidebar: true comments: false diff --git a/source/_components/light.vera.markdown b/source/_components/light.vera.markdown index dba42ffcaf..da0fc42fff 100644 --- a/source/_components/light.vera.markdown +++ b/source/_components/light.vera.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Vera Light" -description: "Instructions on how to integrate Vera lights into Home Assistant." +description: "Instructions how to integrate Vera lights into Home Assistant." date: 2015-10-20 21:00 sidebar: true comments: false diff --git a/source/_components/light.wemo.markdown b/source/_components/light.wemo.markdown index 1ae147ef86..df44818d04 100644 --- a/source/_components/light.wemo.markdown +++ b/source/_components/light.wemo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Belkin WeMo Lights" -description: "Instructions on how to integrate Belkin WeMo LED lights and WeMo Dimmer Switch into Home Assistant." +description: "Instructions how to integrate Belkin WeMo LED lights and WeMo Dimmer Switch into Home Assistant." date: 2016-02-20 00:45 sidebar: true comments: false diff --git a/source/_components/light.wink.markdown b/source/_components/light.wink.markdown index e537c11601..5e7b74771e 100644 --- a/source/_components/light.wink.markdown +++ b/source/_components/light.wink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Wink Light" -description: "Instructions on how to setup the Wink lights within Home Assistant." +description: "Instructions how to setup the Wink lights within Home Assistant." date: 2015-01-20 22:36 sidebar: true comments: false diff --git a/source/_components/light.x10.markdown b/source/_components/light.x10.markdown index 45df065a49..b79a881441 100644 --- a/source/_components/light.x10.markdown +++ b/source/_components/light.x10.markdown @@ -1,7 +1,7 @@ --- layout: page title: "X10" -description: "Instructions on how to setup X10 devices within Home Assistant." +description: "Instructions how to setup X10 devices within Home Assistant." date: 2016-07-27 sidebar: true comments: false diff --git a/source/_components/light.xiaomi_aqara.markdown b/source/_components/light.xiaomi_aqara.markdown index 48bf4fb135..25e01ba22c 100644 --- a/source/_components/light.xiaomi_aqara.markdown +++ b/source/_components/light.xiaomi_aqara.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Xiaomi Light" -description: "Instructions on how to setup the Xiaomi light within Home Assistant." +description: "Instructions how to setup the Xiaomi light within Home Assistant." date: 2017-07-21 16:34 sidebar: true comments: false diff --git a/source/_components/light.xiaomi_miio.markdown b/source/_components/light.xiaomi_miio.markdown index 991ff8c97f..90e5d1359b 100644 --- a/source/_components/light.xiaomi_miio.markdown +++ b/source/_components/light.xiaomi_miio.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Xiaomi Philips Light" -description: "Instructions on how to integrate your Xiaomi Philips Lights within Home Assistant." +description: "Instructions how to integrate your Xiaomi Philips Lights within Home Assistant." date: 2017-08-26 08:45 sidebar: true comments: false @@ -13,54 +13,9 @@ ha_version: 0.53 ha_iot_class: "Local Polling" --- -The `xiaomi_miio` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp, Xiaomi Philips Zhirui LED Bulb E14 Candle Lamp, Xiaomi Philips LED Ceiling Lamp and Xiaomi Philips Eyecare Lamp 2. +The `xiaomi_miio` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp and Xiaomi Philips LED Ceiling Lamp. -## Features - -### Philips LED Ball Lamp and Philips Zhirui LED Candle Lamp - -* Power (on, off) -* Brightness -* Color temperature (175...333 mireds) -* Scene (1, 2, 3, 4) -* Delayed turn off (Resolution in seconds) -* Attributes - - model - - scene - - delayed_turn_off - -### Philips LED Ceiling Lamp - -* Power (on, off) -* Brightness -* Color temperature (175...370 mireds) -* Scene (1, 2, 3, 4) -* Night light mode (on, off) -* Delayed turn off (Resolution in seconds) -* Attributes - - model - - scene - - delayed_turn_off - - night_light_mode - - automatic_color_temperature - -### Philips Eyecare Smart Lamp 2 - -* Eyecare light (on, off) -* Ambient light (on, off) -* Brightness (of each light) -* Scene (1, 2, 3, 4) -* Night light mode (on, off) -* Delayed turn off (Resolution in seconds) -* Eye fatigue reminder / notification (on, off) -* Eyecare mode (on, off) -* Attributes - - model - - scene - - delayed_turn_off - - night_light_mode - - reminder - - eyecare_mode +Currently, the supported features are `on`, `off`, `set_cct` (colortemp) , `set_bright` (brightness). Please follow the instructions on [Retrieving the Access Token](/components/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file. @@ -73,99 +28,20 @@ light: name: Xiaomi Philips Smart LED Ball host: 192.168.130.67 token: YOUR_TOKEN - model: philips.light.bulb ``` Configuration variables: - **host** (*Required*): The IP of your light. - **token** (*Required*): The API token of your light. - **name** (*Optional*): The name of your light. -- **model** (*Optional*): The model of your light. Valid values are `philips.light.bulb`, `philips.light.candle2`, `philips.light.sread1`, `philips.light.ceiling` and `philips.light.zyceiling`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available. - -{% configuration %} -host: - description: The IP address of your device. - required: true - type: string -token: - description: The API token of your device. - required: true - type: string -name: - description: The name of your device. - required: false - type: string - default: Xiaomi Philips Light -model: - description: The model of your device. - required: false - type: string -{% endconfiguration %} ## {% linkable_title Platform Services %} -### {% linkable_title Service `light.xiaomi_miio_set_scene` %} +### Service fan/xiaomi_miio_set_scene Set one of the 4 available fixed scenes. | Service data attribute | Optional | Description | |---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | +| `entity_id` | yes | Only act on specific light. Else targets all. | | `scene` | no | Scene, between 1 and 4. | - -### {% linkable_title Service `light.xiaomi_miio_set_delayed_turn_off` %} - -Delayed turn off. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | -| `time_period` | no | Time period for the delayed turn off. | - -### {% linkable_title Service `light.xiaomi_miio_reminder_on` %} (Eyecare Smart Lamp 2 only) - -Enable the eye fatigue reminder/notification. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | - -### {% linkable_title Service `light.xiaomi_miio_reminder_off` %} (Eyecare Smart Lamp 2 only) - -Disable the eye fatigue reminder/notification. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | - -### {% linkable_title Service `light.xiaomi_miio_night_light_mode_on` %} (Eyecare Smart Lamp 2 only) - -Turn the smart night light mode on. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | - -### {% linkable_title Service `light.xiaomi_miio_night_light_mode_off` %} (Eyecare Smart Lamp 2 only) - -Turn the smart night light mode off. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | - -### {% linkable_title Service `light.xiaomi_miio_eyecare_mode_on` %} (Eyecare Smart Lamp 2 only) - -Turn the eyecare mode on. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | - -### {% linkable_title Service `light.xiaomi_miio_eyecare_mode_off` %} (Eyecare Smart Lamp 2 only) - -Turn the eyecare mode off. - -| Service data attribute | Optional | Description | -|---------------------------|----------|-------------------------------------------------------| -| `entity_id` | yes | Only act on a specific light. Else targets all. | diff --git a/source/_components/light.yeelight.markdown b/source/_components/light.yeelight.markdown index 8ee047b47f..b098d007d5 100644 --- a/source/_components/light.yeelight.markdown +++ b/source/_components/light.yeelight.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Yeelight Wifi Bulb" -description: "Instructions on how to setup Yeelight Wifi devices within Home Assistant." +description: "Instructions how to setup Yeelight Wifi devices within Home Assistant." date: 2016-10-29 sidebar: true comments: false @@ -35,7 +35,7 @@ light: Configuration variables: -- **ip** (*Required*): IP(s) of your Wifi bulbs +- **ip** (*Required*): IP(s) of your wifi bulbs - **name** (*Optional*): A friendly name for the device. - **transition** (*Optional*, default 350): Smooth transitions over time (in ms). - **use_music_mode** (*Optional*, default False): Enable music mode. @@ -62,18 +62,6 @@ This component is tested to work with the following models. If you have a differ - **YLDD01YL**: Lightstrip (Color) - **YLDD02YL**: Lightstrip (Color) - **MJCTD01YL**: Xiaomi Mijia Bedside Lamp - WIFI Version! -- **MJTD01YL**: Xiaomi Mijia Smart LED Desk Lamp (autodiscovery isn't possible because the device doesn't support mDNS due to the small amount of RAM) -- **YLXD02YL**: Yeelight Ceiling Light 4 (Jiaoyue 650) -- **YLXD01YL**: Yeelight Smart LED Ceiling Light - Youth Version -## {% linkable_title Platform Services %} -### {% linkable_title Service `light.yeelight_set_mode` %} - -Set a operation mode. - -| Service data attribute | Optional | Description | -|---------------------------|----------|---------------------------------------------------------------------------------------------| -| `entity_id` | yes | Only act on a specific yeelight. Else targets all. | -| `mode` | no | Operation mode. Valid values are 'last', 'normal', 'rgb', 'hsv', 'color_flow', 'moonlight'. | diff --git a/source/_components/light.yeelightsunflower.markdown b/source/_components/light.yeelightsunflower.markdown index 0583084626..1b0e441970 100644 --- a/source/_components/light.yeelightsunflower.markdown +++ b/source/_components/light.yeelightsunflower.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Yeelight Sunflower Bulb" -description: "Instructions on how to setup Yeelight Sunflower hub and bulbs within Home Assistant." +description: "Instructions how to setup Yeelight Sunflower hub and bulbs within Home Assistant." date: 2017-02-11 sidebar: true comments: false diff --git a/source/_components/light.zengge.markdown b/source/_components/light.zengge.markdown index b2f46b065d..ed15a92752 100644 --- a/source/_components/light.zengge.markdown +++ b/source/_components/light.zengge.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Zengge" -description: "Instructions on how to integrate Zengge Bluetooth bulbs into Home Assistant." +description: "Instructions how to integrate Zengge Bluetooth bulbs into Home Assistant." date: 2017-01-14 08:00 sidebar: true comments: false diff --git a/source/_components/light.zha.markdown b/source/_components/light.zha.markdown index 904c1e59de..c3b0cc2d8b 100644 --- a/source/_components/light.zha.markdown +++ b/source/_components/light.zha.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ZigBee Home Automation Light" -description: "Instructions on how to setup ZigBee Home Automation lights within Home Assistant." +description: "Instructions how to setup ZigBee Home Automation lights within Home Assistant." date: 2017-02-22 00:00 sidebar: true comments: false diff --git a/source/_components/light.zwave.markdown b/source/_components/light.zwave.markdown index 891f63e886..4053e61f1d 100644 --- a/source/_components/light.zwave.markdown +++ b/source/_components/light.zwave.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Z-Wave Light" -description: "Instructions on how to setup the Z-Wave lights within Home Assistant." +description: "Instructions how to setup the Z-Wave lights within Home Assistant." date: 2015-11-11 13:00 sidebar: true comments: false diff --git a/source/_components/lirc.markdown b/source/_components/lirc.markdown index 1c6dc56be3..6d379e04ca 100644 --- a/source/_components/lirc.markdown +++ b/source/_components/lirc.markdown @@ -1,7 +1,7 @@ --- layout: page title: "LIRC" -description: "Instructions on how to integrate IR remotes with LIRC into Home Assistant." +description: "Instructions how to integrate IR remotes with LIRC into Home Assistant." date: 2016-05-22 19:59 sidebar: true comments: false @@ -14,9 +14,9 @@ ha_release: 0.21 ha_iot_class: "Local Push" --- -[LIRC](http://www.lirc.org/) integration for Home Assistant allows you to receive signals from an infrared remote control and control actions based on the buttons you press. You can use them to set scenes or trigger any other [automation](/components/automation/). +[LIRC](http://www.lirc.org/) integration for Home Assistant allows you to receive signals from an infrared remote control and control actions based on the buttons you press. You can use them to set scenes or trigger any other [automation](https://home-assistant.io/components/automation/). -Sending IR commands is not supported in this component (yet), but can be accomplished using the [shell_command component](/components/shell_command/) in conjunction with the `irsend` command. +Sending IR commands is not supported in this component (yet), but can be accomplished using the [shell_command component](https://home-assistant.io/components/shell_command/) in conjunction with the `irsend` command. ### {% linkable_title Installation %} @@ -32,14 +32,14 @@ The configuration is slightly different : - The `hardware.conf` file is not supported, obsoleted by a new `lirc_options.conf` file and systemd unit definitions. - The former single `lirc` service is replaced with the three systemd services `lircd.service`, `lircmd.service` and `irexec.service`. There is no counterpart to the 0.9.0 `lirc` service which covered all of these. Using a separate transmitter device requires yet another service. - - 0.9.4 defaults to using systemd for controlling the services. This is not just start/stop functionality, systemd is used to implement new features and to address shortcomings in 0.9.0. However, traditional systemV scripts are also installed and could be used although this is less tested and not really documented. - + - 0.9.4 defaults to using systemd for controlling the services. This is not just start/stop functionality, systemd is used to implement new features and to address shortcomings in 0.9.0. However, traditional systemV scripts are also installed and could be used although this is less tested and not really documented. + For more information have a look at `/usr/share/doc/lirc/README.Debian.gz` where the update process is explained when you have updated from jessie to stretch. ### {% linkable_title Configuring LIRC %} -Now teach LIRC about your particular remote control by preparing a lircd configuration file (`/etc/lirc/lircd.conf`). Search the [LIRC remote database](http://lirc.sourceforge.net/remotes/) for your model. If you can't find it, then you can always use the `irrecord` program to learn your remote. This will create a valid configuration file. Add as many remotes as you want by pasting them into the file. If `irrecord` doesn't work (e.g., for some air conditioner remotes), then the `mode2` program is capable of reading the codes in raw mode, followed by `irrecord -a` to extract hex codes. +Now teach LIRC about your particular remote control by preparing a lircd configuration file (`/etc/lirc/lircd.conf`). Search the [LIRC remote database](http://lirc.sourceforge.net/remotes/) for your model. If you can't find it, then you can always use the `irrecord` program to learn your remote. This will create a valid configuration file. Add as many remotes as you want by pasting them into the file. If `irrecord` doesn't work (e.g. for some air conditioner remotes), then the `mode2` program is capable of reading the codes in raw mode, followed by `irrecord -a` to extract hex codes. Next, you have to make a `~/.lircrc` file that maps keypresses to system actions. [The configuration](http://www.lirc.org/html/configure.html) is a bit tedious but it must be done. Use the `prog = home-assistant` for all keys you want to be recognized by Home Assistant. The values you set for `button` must be the same as in the `lircd.conf` file and the values you put for `config` entry will be the sensor value in Home Assistant when you press the button. An example may look like this: @@ -98,4 +98,4 @@ automation: entity_id: group.a_lights ``` -The `button_name` data values (e.g., `KEY_0`) are set by you in the `.lircrc` file. +The `button_name` data values (e.g. `KEY_0`) are set by you in the `.lircrc` file. diff --git a/source/_components/litejet.markdown b/source/_components/litejet.markdown index fb33408953..3770bb024b 100644 --- a/source/_components/litejet.markdown +++ b/source/_components/litejet.markdown @@ -1,7 +1,7 @@ --- layout: page title: "LiteJet" -description: "Instructions on how to setup the LiteJet hub within Home Assistant." +description: "Instructions how to setup the LiteJet hub within Home Assistant." date: 2015-10-26 09:37 sidebar: true comments: false diff --git a/source/_components/lock.abode.markdown b/source/_components/lock.abode.markdown index 9dcc3cff90..c1e2860370 100644 --- a/source/_components/lock.abode.markdown +++ b/source/_components/lock.abode.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Abode Lock" -description: "Instructions on how to integrate Abode locks into Home Assistant." +description: "Instructions how to integrate Abode locks into Home Assistant." date: 2017-08-26 13:28 sidebar: true comments: false diff --git a/source/_components/lock.august.markdown b/source/_components/lock.august.markdown deleted file mode 100644 index eda4f37d06..0000000000 --- a/source/_components/lock.august.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "August Lock" -description: "Instructions on how to integrate your August devices into Home Assistant." -date: 2018-02-17 22:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: august.png -ha_category: Lock -ha_release: "0.64" -ha_iot_class: "Cloud Polling" ---- - -The `august` lock platform allows you to control your [August](http://august.com) lock from within Home Assistant. - -To add `august` lock to your installation, follow instructions in [August component](/components/august/). diff --git a/source/_components/lock.bmw_connected_drive.markdown b/source/_components/lock.bmw_connected_drive.markdown deleted file mode 100755 index 4c6c7a2edc..0000000000 --- a/source/_components/lock.bmw_connected_drive.markdown +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: page -title: "BMW Connected Drive Lock" -description: "Instructions on how to setup your BMW Connected Drive account with Home Assistant." -date: 2018-02-22 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: bmw.png -ha_category: Lock -ha_release: 0.66 ---- - - -The `bmw_connected_drive` platform allows you to import data on your BMW into Home Assistant. - -The lock will be automatically configured if `bmw_connected_drive` component is configured. - -For more configuration information see the [`bmw_connected_drive` component](/components/bmw_connected_drive/) documentation. diff --git a/source/_components/lock.homematic.markdown b/source/_components/lock.homematic.markdown deleted file mode 100644 index d536312e2e..0000000000 --- a/source/_components/lock.homematic.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "Homematic Lock (KeyMatic)" -description: "Instructions how to integrate Homematic locks (KeyMatic) within Home Assistant." -date: 2018-01-28 03:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: homematic.png -ha_category: Lock -ha_release: 0.66 -ha_iot_class: "Local Push" ---- - -The `homematic` lock platform lets you observe and control the state of the HomeMatic [Homematic](http://www.homematic.com/) KeyMatic lock through Home Assistant. - -Devices will be configured automatically. Please refer to the [component](/components/homematic/) configuration on how to setup Homematic. diff --git a/source/_components/lock.isy994.markdown b/source/_components/lock.isy994.markdown index b019662a68..04109b9cd6 100644 --- a/source/_components/lock.isy994.markdown +++ b/source/_components/lock.isy994.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ISY994 Lock" -description: "Instructions on how to integrate ISY994 locks into Home Assistant." +description: "Instructions how to integrate ISY994 locks into Home Assistant." date: 2016-09-03 23:00 sidebar: true comments: false diff --git a/source/_components/lock.lockitron.markdown b/source/_components/lock.lockitron.markdown index 6b320e7108..418881c169 100644 --- a/source/_components/lock.lockitron.markdown +++ b/source/_components/lock.lockitron.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Lockitron Lock" -description: "Instructions on how to integrate Lockitron locks into Home Assistant." +description: "Instructions how to integrate Lockitron locks into Home Assistant." date: 2017-03-24 00:00 sidebar: true comments: false diff --git a/source/_components/lock.markdown b/source/_components/lock.markdown index 67d5b6509a..c2c3cc5530 100644 --- a/source/_components/lock.markdown +++ b/source/_components/lock.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Locks" -description: "Instructions on how to setup your locks with Home Assistant." +description: "Instructions how to setup your locks with Home Assistant." date: 2015-11-21 08:10 sidebar: true comments: false diff --git a/source/_components/lock.mqtt.markdown b/source/_components/lock.mqtt.markdown index ff8eb05170..8ed47ccf4a 100644 --- a/source/_components/lock.mqtt.markdown +++ b/source/_components/lock.mqtt.markdown @@ -1,7 +1,7 @@ --- layout: page title: "MQTT Lock" -description: "Instructions on how to integrate MQTT locks into Home Assistant." +description: "Instructions how to integrate MQTT locks into Home Assistant." date: 2016-02-28 15:00 sidebar: true comments: false @@ -24,7 +24,7 @@ Optimistic mode can be forced, even if state topic is available. Try to enable i To enable MQTT locks in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry lock: - platform: mqtt command_topic: "home/frontdoor/set" diff --git a/source/_components/lock.nello.markdown b/source/_components/lock.nello.markdown index 558f9098b9..53f2e26e79 100644 --- a/source/_components/lock.nello.markdown +++ b/source/_components/lock.nello.markdown @@ -16,7 +16,6 @@ ha_iot_class: "Cloud Polling" --- The `nello` platform allows you to control [Nello](https://nello.io) intercoms. - To get started you need to create a secondary Nello account and authorize it to access your lock(s).
@@ -25,26 +24,18 @@ Be aware that if you use your main account for Home Assistant you may not be abl
## {% linkable_title Configuration %}
-To add your Nello locks to your installation, add the following to your `configuration.yaml` file:
-
```yaml
# Example configuration.yaml entry
lock:
- platform: nello
- username: YOUR_USERNAME
- password: YOUR_PASSWORD
+ username: mail@example.com
+ password: mySecretPassword
```
-{% configuration %}
-username:
- description: The username of your Nello account.
- required: true
- type: string
-password:
- description: The password of your Nello account.
- required: true
- type: string
-{% endconfiguration %}
+Configuration variables:
+
+- **username** (*Required*): The username of your Nello account.
+- **password** (*Required*): The password of your Nello account.
## {% linkable_title Events %}
diff --git a/source/_components/lock.sesame.markdown b/source/_components/lock.sesame.markdown
index affd029f63..01d9910fda 100644
--- a/source/_components/lock.sesame.markdown
+++ b/source/_components/lock.sesame.markdown
@@ -15,28 +15,18 @@ ha_release: "0.47"
The `sesame` platform allows you to control your [Sesame](https://candyhouse.co/) smart locks made by CANDY HOUSE, Inc.
-## {% linkable_title Configuration %}
-
Your Sesame needs to be paired with a mobile device running the app in *virtual station* mode, or a standalone [Wi-Fi Access Point](https://candyhouse.co/collections/frontpage/products/wi-fi-access-point).
Once you have remote access enabled using one of the above AND the Integration - cloud option enabled on the Sesame app for that lock settings, add the following to your `configuration.yaml` file:
-
```yaml
# Example configuration.yaml entry
lock:
- platform: sesame
- email: YOUR_E_MAIL_ADDRESS
- password: YOUR_PASSWORD
+ email: abc@i-lovecandyhouse.co
+ password: super-strong-password
```
-{% configuration %}
-email:
- description: The email address for your Sesame account.
- required: true
- type: string
-password:
- description: The password for your Sesame account.
- required: true
- type: string
-{% endconfiguration %}
+Configuration variables:
+- **email** (*Required*): The email address for your Sesame account.
+- **password** (*Required*): The password for your Sesame account.
diff --git a/source/_components/lock.vera.markdown b/source/_components/lock.vera.markdown
index a305038987..8baf864dfd 100644
--- a/source/_components/lock.vera.markdown
+++ b/source/_components/lock.vera.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Vera Lock"
-description: "Instructions on how to integrate Vera locks into Home Assistant."
+description: "Instructions how to integrate Vera locks into Home Assistant."
date: 2016-06-29 15:00
sidebar: true
comments: false
diff --git a/source/_components/lock.verisure.markdown b/source/_components/lock.verisure.markdown
index e3c2d31e85..2e72677179 100644
--- a/source/_components/lock.verisure.markdown
+++ b/source/_components/lock.verisure.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Verisure Lock"
-description: "Instructions on how to setup the Verisure locks within Home Assistant."
+description: "Instructions how to setup the Verisure locks within Home Assistant."
date: 2016-02-12 06:00
sidebar: true
comments: false
diff --git a/source/_components/lock.wink.markdown b/source/_components/lock.wink.markdown
index a792e130a8..1f51751b3f 100644
--- a/source/_components/lock.wink.markdown
+++ b/source/_components/lock.wink.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Wink Lock"
-description: "Instructions on how to setup the Wink locks within Home Assistant."
+description: "Instructions how to setup the Wink locks within Home Assistant."
date: 2015-11-20 12:00
sidebar: true
comments: false
diff --git a/source/_components/lock.zwave.markdown b/source/_components/lock.zwave.markdown
index ba25eacd6c..e1d6fd7b33 100644
--- a/source/_components/lock.zwave.markdown
+++ b/source/_components/lock.zwave.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Z-Wave Lock"
-description: "Instructions on how to setup the Z-Wave Locks within Home Assistant."
+description: "Instructions how to setup the Z-Wave Locks within Home Assistant."
date: 2016-05-07 08:00
sidebar: true
comments: false
diff --git a/source/_components/logbook.markdown b/source/_components/logbook.markdown
index 438e747430..adabef99d1 100644
--- a/source/_components/logbook.markdown
+++ b/source/_components/logbook.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Logbook"
-description: "Instructions on how to enable the logbook component for Home Assistant."
+description: "Instructions how to enable the logbook component for Home Assistant."
date: 2015-04-25 9:23
sidebar: true
comments: false
@@ -11,7 +11,7 @@ logo: logbook.png
ha_category: "History"
---
-
-When starting or restarting Home Assistant make sure your TV is off. This is a flaw in the TV itself.
-
-The platform will never turn your TV off. Instead, it will be put to sleep and woken up. This can be useful, because the selected source of the TV will remain the same. It will essentially turn your TV into a dumb TV.
-
- The component was removed. The vendor disabled the API endpoint and a new API is not available currently.
-
-The minimal setup uses the embedded MQTT broker, however a separate broker is advised for more stability.
-
-After the update to firmware 4.0 (which adds cleaning maps) there is also support for displaying the maps of the Botvac D3 Connected and Botvac D5 Connected robots. The start/stop functionality does not work. More information on how to update can be found [here](https://support.neatorobotics.com/hc/en-us/articles/115004320694-Software-Update-4-0-for-Neato-Botvac-Connected-D3-D5-).
+After the update to firmware 4.0 (which adds cleaning maps) there is also support for displaying the maps of the Botvac D3 Connected and Botvac D5 Connected robots. The start/stop functionality does not work. More information on how to update here: https://support.neatorobotics.com/hc/en-us/articles/115004320694-Software-Update-4-0-for-Neato-Botvac-Connected-D3-D5-
If you are accessing home Assistant over HTTPS using SSL, you cannot access HTTP sites through an iframe panel.
- `/local/` in this context refers to the `.homeassistant/www/` folder.
-
The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. [See the demo for a live example](/demo/). It depends on the `recorder` component for storing the data. This means that if the [`recorder`](/components/recorder/) component is set up to use e.g., MySQL or PostgreSQL as data store, the `logbook` component does not use the default SQLite database to store data.
+ The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. [See the demo for a live example](/demo/). It depends on the `recorder` component for storing the data. This means that if the [`recorder`](/components/recorder/) component is set up to use e.g. MySQL or PostgreSQL as data store, the `logbook` component does not use the default SQLite database to store data.
To enable the logbook in your installation, add the following to your `configuration.yaml` file:
@@ -26,8 +26,8 @@ Configuration variables:
- **entities** (*Optional*): The list of entity ids to be excluded from creating logbook entries.
- **domains** (*Optional*): The list of domains to be excluded from creating logbook entries.
- **include** (*Optional*): Configure which components should create logbook entries.
- - **entities** (*Optional*): The list of entity ids to be included in creating logbook entries.
- - **domains** (*Optional*): The list of domains to be included in creating logbook entries.
+ - **entities** (*Optional*): The list of entity ids to be included from creating logbook entries.
+ - **domains** (*Optional*): The list of domains to be included from creating logbook entries.
If you want to exclude messages of some entities or domains from the logbook just add the `exclude` parameter like:
diff --git a/source/_components/logger.markdown b/source/_components/logger.markdown
index 2f89e09096..70168cf440 100644
--- a/source/_components/logger.markdown
+++ b/source/_components/logger.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Logger"
-description: "Instructions on how to enable the logger component for Home Assistant."
+description: "Instructions how to enable the logger component for Home Assistant."
date: 2015-11-12 17:00
sidebar: true
comments: false
diff --git a/source/_components/lutron.markdown b/source/_components/lutron.markdown
index 6799e1feb5..c946160db1 100644
--- a/source/_components/lutron.markdown
+++ b/source/_components/lutron.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Lutron"
-description: "Instructions on how to use Lutron devices with Home Assistant."
+description: "Instructions how to use Lutron devices with Home Assistant."
date: 2017-01-28 13:00
sidebar: true
comments: false
@@ -18,8 +18,6 @@ ha_iot_class: "Local Polling"
Presently, there's only support for communicating with the [RadioRA 2](http://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RadioRA2/Overview.aspx) Main Repeater and only handle light switches and dimmers.
-## {% linkable_title Configuration %}
-
When configured, the `lutron` component will automatically discover the rooms and their associated switches/dimmers as configured by the RadioRA 2 software from Lutron. Each room will be treated as a separate group.
To use Lutron RadioRA 2 devices in your installation, add the following to your `configuration.yaml` file using the IP address of your RadioRA 2 main repeater:
diff --git a/source/_components/lutron_caseta.markdown b/source/_components/lutron_caseta.markdown
index 9783766c89..912bd82dc4 100644
--- a/source/_components/lutron_caseta.markdown
+++ b/source/_components/lutron_caseta.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Lutron Caseta"
-description: "Instructions on how to use Lutron Caseta devices with Home Assistant."
+description: "Instructions how to use Lutron Caseta devices with Home Assistant."
date: 2017-01-28 13:00
sidebar: true
comments: false
@@ -25,7 +25,7 @@ The currently supported Caseta devices are:
- Scenes as Home Assistant [scenes](/components/scene.lutron_caseta/)
- Lutron shades as Home Assistant [covers](/components/cover.lutron_caseta/)
-When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Bedroom Lamp' becomes `light.bedroom_lamp` in Home Assistant.
+When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g. a dimmer called 'Bedroom Lamp' becomes `light.bedroom_lamp` in Home Assistant.
To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [this script](/assets/get_lutron_cert.zip), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
diff --git a/source/_components/mailbox.asterisk_mbox.markdown b/source/_components/mailbox.asterisk_mbox.markdown
index 15d5ec455f..25a0859aa9 100644
--- a/source/_components/mailbox.asterisk_mbox.markdown
+++ b/source/_components/mailbox.asterisk_mbox.markdown
@@ -1,16 +1,15 @@
---
layout: page
title: "Asterisk Voicemail Mailbox"
-description: "Instructions on how to integrate an Asterisk Voicemail within Home Assistant."
+description: "Instructions how to integrate an Asterisk Voicemail within Home Assistant."
date: 2017-06-30 18:30
sidebar: true
comments: false
sharing: true
footer: true
-logo: asterisk.png
ha_category: Mailbox
ha_version: 0.51
---
-The Asterisk Voicemail Mailbox provides visual and audio access to voicemail on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail component](/components/asterisk_mbox/) configuration.
+The Asterisk Voicemail Mailbox provides visual and audio access to voicemail on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail component](/components/asterisk_mbox) configuration.
diff --git a/source/_components/mailbox.markdown b/source/_components/mailbox.markdown
index 16bfa603b8..28f4d77f43 100644
--- a/source/_components/mailbox.markdown
+++ b/source/_components/mailbox.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Mailbox"
-description: "Instructions on how to setup your mailboxes with Home Assistant."
+description: "Instructions how to setup your mailboxes with Home Assistant."
date: 2017-06-30 18:30
sidebar: true
comments: false
diff --git a/source/_components/mailgun.markdown b/source/_components/mailgun.markdown
index 2f13d2c062..78764d7507 100644
--- a/source/_components/mailgun.markdown
+++ b/source/_components/mailgun.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Mailgun"
-description: "Instructions on how to add Mailgun mail notifications to Home Assistant."
+description: "Instructions how to add Mailgun mail notifications to Home Assistant."
date: 2017-02-06 16:52
sidebar: true
comments: false
diff --git a/source/_components/matrix.markdown b/source/_components/matrix.markdown
deleted file mode 100644
index 1047d54053..0000000000
--- a/source/_components/matrix.markdown
+++ /dev/null
@@ -1,136 +0,0 @@
----
-layout: page
-title: "Matrix"
-description: "Matrix chatbot support"
-date: 2018-03-25 18:50
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: matrix.png
-ha_category: Hub
-ha_version: 0.69
----
-
-This component allows you to send messages to matrix rooms, as well as to react to messages in matrix rooms. Reacting to commands is accomplished by firing an event when one of the configured commands is triggered.
-
-```yaml
-# Example configuration.yaml entry
-matrix:
- homeserver: https://matrix.org
- username: "@my_matrix_user:matrix.org"
- password: supersecurepassword
- rooms:
- - "#hasstest:matrix.org"
- commands:
- - word: my_command
- name: my_command
-```
-
-Configuration variables:
-
-{% configuration %}
-username:
- description: "The matrix username that home assistant should use to log in. *Note*: You must specify a full matrix ID here, including the homeserver domain, e.g. '@my_matrix_bot:matrix.org'. Please note also that the '@' character has a special meaning in YAML, so this must always be given in quotes."
- required: true
- type: string
-password:
- description: The password for your Matrix account.
- required: true
- type: string
-homeserver:
- description: "The full URL for your homeserver. If you use the defauls matrix.org homeserver, this is 'https://matrix.org'."
- required: true
- type: string
-verify_ssl:
- description: Verify the homeservers certificate.
- required: false
- type: string
- default: true
-rooms:
- description: "The list of rooms that the bot should join and listen for commands (see below) in. While you can limit the list of rooms that a certain command applies to on a per-command basis (see below), you must still list all rooms here that commands should be received in. Rooms can be given either by their internal ID (e.g., '!cURbafjkfsMDVwdRDQ:matrix.org') or any of their aliases (e.g., '#matrix:matrix.org')."
- required: false
- type: [string]
- default: empty
-commands:
- description: "A list of commands that the bot should listen for. If a command is triggered (via its *word* or *expression*, see below), an event is fired that you can handle using automations. Every command consists of these possible configuration options:"
- required: false
- type: map
- default: empty
- keys:
- word:
- description: "Specifies a word that the bot should listen for. If you specify 'my_command' here, the bot will react to any message starting with '!my_command'."
- required: false
- type: string
- expression:
- description: "Specifies a regular expression (in python regexp syntax) that the bot should listen to. The bot will react to any message that matches the regular expression."
- required: false
- type: string
- name:
- description: "The name of the command. This will be an attribute of the event that is fired when this command triggers."
- required: true
- type: string
- rooms:
- description: "A list of rooms that the bot should listen for this command in. If this is not given, the *rooms* list from the main config is used. Please note that every room in this list must also be in the main *room* config."
- required: false
- type: [string]
- default: empty
-{% endconfiguration %}
-
-### {% linkable_title Event Data %}
-
-If a command is triggered, a `matrix_command` event is fired. The event contains the name of the command in the `name` field. If the command is a word command that has no name set, the `name` field contains the word instead.
-
-If the command is a word command, the `data` field contains a list of the command's arguments, i.e., everything that stood behind the word, split at spaces. If the command is an expression command, the `data` field contains the [group dictionary](https://docs.python.org/3.6/library/re.html?highlight=re#re.match.groupdict) of the regular expression that matched the message.
-
-### {% linkable_title Comprehensive Configuration Example %}
-
-This example also uses the [matrix `notify` platform](/components/notify.matrix/).
-
-```yaml
-# The Matrix component
-matrix:
- homeserver: https://matrix.org
- username: "@my_matrix_user:matrix.org"
- password: supersecurepassword
- rooms:
- - "#hasstest:matrix.org"
- - "#someothertest:matrix.org"
- commands:
- - word: testword
- rooms:
- - "#someothertest:matrix.org"
- - expression: "My name is (?P
diff --git a/source/_components/media_player.philips_js.markdown b/source/_components/media_player.philips_js.markdown
index e776db61a3..d7e663e8e5 100644
--- a/source/_components/media_player.philips_js.markdown
+++ b/source/_components/media_player.philips_js.markdown
@@ -29,5 +29,3 @@ Configuration variables:
- **host** (*Required*): IP address of TV.
- **name** (*Optional*): The name you would like to give to the Philips TV.
-- **turn_on_action** (*Optional*): A script that will be executed to turn on the TV (can be used with wol).
-- **api_version** (*Optional*): The JointSpace API version of your Philips TV, defaults to `1`. This is an experimental option and not all the functionalities are guaranteed to work with API versions different from `1`.
diff --git a/source/_components/media_player.pioneer.markdown b/source/_components/media_player.pioneer.markdown
index 6bc6d1a5b0..66086c5ded 100644
--- a/source/_components/media_player.pioneer.markdown
+++ b/source/_components/media_player.pioneer.markdown
@@ -29,7 +29,7 @@ Configuration variables:
- **host** (*Required*): The IP of the Pioneer device, eg. `192.168.0.10`
- **name** (*Optional*): The name you would like to give to the receiver.
-- **port** (*Optional*): The port on which the Pioneer device listens, e.g., `23` (default) or `8102`
+- **port** (*Optional*): The port on which the Pioneer device listens, e.g. `23` (default) or `8102`
- **timeout** (*Optional*): Number of seconds (float) to wait for blocking operations like connect, write, and read.
Notes:
diff --git a/source/_components/media_player.plex.markdown b/source/_components/media_player.plex.markdown
index e17068d221..ddaf3a611b 100644
--- a/source/_components/media_player.plex.markdown
+++ b/source/_components/media_player.plex.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Plex"
-description: "Instructions on how to integrate Plex into Home Assistant."
+description: "Instructions how to integrate Plex into Home Assistant."
date: 2015-10-05 21:21
sidebar: true
comments: false
@@ -69,8 +69,6 @@ media_player:
show_all_controls: false
use_custom_entity_ids: true
use_episode_art: true
- remove_unavailable_clients: true
- client_remove_interval: 600
```
- **entity_namespace** (*Optional*): Prefix for entity ID's. Defaults to `null`. Useful when using overlapping components (ex. Apple TV and Plex components when you have Apple TV's you use as Plex clients). Go from _media_player.playroom2_ to _media_player.plex_playroom_
- **include_non_clients** (*Optional*): Display non-recontrollable clients (ex. remote clients, PlexConnect Apple TV's). Defaults to `false`.
@@ -78,8 +76,6 @@ media_player:
- **show_all_controls** (*Optional*): Forces all controls to display. Defaults to `false`. Ignores dynamic controls (ex. show volume controls for client A but not for client B) based on detected client capabilities. This option allows you to override this detection if you suspect it to be incorrect.
- **use_custom_entity_ids** (*Optional*): Name Entity ID's by client ID's instead of friendly names. Defaults to `false`. HA assigns entity ID's on a first come first serve basis. When you have identically named devices connecting (ex. media_player.plex_web_safari, media_player.plex_web_safari2), you can't reliably distinguish and or predict which device is which. This option avoids this issue by using unique client ID's (ex. media_player.dy4hdna2drhn).
- **use_episode_art** (*Optional*): Display TV episode art instead of TV show art. Defaults to `false`.
-- **remove_unavailable_clients** (*Optional*): Remove stale plex clients from UI after interval. Defaults to `true`.
-- **client_remove_interval** (*Optional*): How long a client is to be unavailable for before it is cleaned up. Defaults to `600 seconds (10min)`.
### {% linkable_title Service `play_media` %}
diff --git a/source/_components/media_player.roku.markdown b/source/_components/media_player.roku.markdown
index c7771e0f40..5c889727de 100644
--- a/source/_components/media_player.roku.markdown
+++ b/source/_components/media_player.roku.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Roku"
-description: "Instructions on how to integrate Roku into Home Assistant."
+description: "Instructions how to integrate Roku into Home Assistant."
date: 2016-05-16 20:0+0000
sidebar: true
comments: false
diff --git a/source/_components/media_player.samsungtv.markdown b/source/_components/media_player.samsungtv.markdown
index d944b2b3a7..744488bebe 100644
--- a/source/_components/media_player.samsungtv.markdown
+++ b/source/_components/media_player.samsungtv.markdown
@@ -50,15 +50,12 @@ Currently known supported models:
- EH5600
- F6400AF
- F6400
-- F8000BF
- D6505
- D6300SF
- U6000 (port must be set to 8001)
- U6300 (port must be set to 8001, and `pip3 install websocket-client` must be executed)
-- K5579 (port must be set to 8001, On/Off, Forward/Backward, Volume control, but no Play button)
- K6500AF (port must be set to 8001)
- KS8005 (port must be set to 8001, and `pip3 install websocket-client` must be executed)
-- KU6020 (port must be set to 8001, and `pip3 install websocket-client` must be executed)
- KU6290 (port must be set to 8001)
- KU7000 (port must be set to 8001)
- MU6170UXZG (port must be set to 8001, and `pip3 install websocket-client` must be executed)
@@ -77,10 +74,10 @@ Currently tested but not working models:
- JS9500 - State is always "on" and unable to control (but port 8001 *is* open)
- MU6300 - Port set to 8001, `pip3 install websocket-client` must be executed, turning on works, status not working reliably, turning off is not permanent (it comes back on)
-None of the 2014 (H) and 2015 (J) model series (e.g., J5200) will work, since Samsung have used a different (encrypted) type of interface for these.
+None of the 2014 (H) and 2015 (J) model series (e.g. J5200) will work, since Samsung have used a different (encrypted) type of interface for these.
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.samsungtv.markdown).
-The first letter (U, P, L, H & K) represent the screen type, e.g., LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size.
+The first letter (U, P, L, H & K) represent the screen type, e.g. LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size.
If you add your model remember to remove these before adding them to the list.
Currently the ability to select a source is not implemented.
diff --git a/source/_components/media_player.songpal.markdown b/source/_components/media_player.songpal.markdown
deleted file mode 100644
index 0fd9a73f72..0000000000
--- a/source/_components/media_player.songpal.markdown
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: "Sony SongPal compatible devices"
-description: "Instructions on how to integrate Sony Songpal devices into Home Assistant."
-date: 2018-02-03 09:00
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: sony.png
-ha_category: Media Player
-ha_iot_class: "Local Polling"
-ha_release: 0.65
----
-
-The `songpal` platform allows you to control Sony's Songpal ("[Audio Control API](https://developer.sony.com/develop/audio-control-api/)") compatible devices such as soundbars, AV receivers and wireless speakers from Home Assistant.
-
-Even when the API officially supports only a few devices (HT-ST5000, HT-MT500, HT-CT800, SRS-ZR5 and STR-DN1080), it has also been confirmed to work on others. [The list of supported devices](http://vssupport.sony.net/en_ww/device.html) from Sony's Songpal website lists devices which are likely to be compatible with this platform.
-
-If the platform works with your non-listed device, or you encounter bugs, please feel free to [report them upstream](https://github.com/rytilahti/python-songpal).
-
-A few notes:
-
-- The quick start-up mode has to be enabled in order to turn the device on.
-- Supports currently only one output terminal, i.e. the volume control works only on the first volume controller as reported by the backend library.
-- Some devices, e.g., HT-XT3, do not support decreasing the volume step-by-step correctly.
-- Feel free to improve the available services!
-
-## {% linkable_title Configuration %}
-
-The platform will be loaded automatically by discovery component. If you want to manually configure it, add the following to your `configuration.yaml` file:
-
-```yaml
-media_player:
- - platform: songpal
- name: my soundbar
- endpoint: http://IP_ADDRESS:10000/sony
-```
-
-{% configuration %}
-name:
- description: The name to display for this device.
- required: false
- type: string
-endpoint:
- description: API endpoint of the device.
- required: true
- type: string
-{% endconfiguration %}
-
-See [python-songpal's documentation](https://github.com/rytilahti/python-songpal#locating-the-endpoint) how to get your API endpoint.
-
-## {% linkable_title Services %}
-
-In addition to the general [media player services](/components/media_player/#services), the following services are provided:
-
-### {% linkable_title Service `media_player/songpal_set_sound_setting` %}
-
-For a list of available settings and their values use [`songpal sound`](https://github.com/rytilahti/python-songpal#sound-settings) command.
-
-| Service data attribute | Optional | Description |
-|------------------------|----------|--------------------------------------------------|
-| `entity_id` | yes | Target entity, leave unset for all devices |
-| `name` | no | Configuration variable, e.g., `nightmode` |
-| `value` | no | New configuration value, e.g., `on` |
-
-
-
diff --git a/source/_components/media_player.sonos.markdown b/source/_components/media_player.sonos.markdown
index 862cd822f8..3afe420ff4 100644
--- a/source/_components/media_player.sonos.markdown
+++ b/source/_components/media_player.sonos.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Sonos"
-description: "Instructions on how to integrate Sonos devices into Home Assistant."
+description: "Instructions how to integrate Sonos devices into Home Assistant."
date: 2015-09-12 13:00
sidebar: true
comments: false
diff --git a/source/_components/media_player.soundtouch.markdown b/source/_components/media_player.soundtouch.markdown
index 463914f236..fa2a550b02 100644
--- a/source/_components/media_player.soundtouch.markdown
+++ b/source/_components/media_player.soundtouch.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Soundtouch"
-description: "Instructions on how to integrate Bose Soundtouch devices into Home Assistant."
+description: "Instructions how to integrate Bose Soundtouch devices into Home Assistant."
date: 2016-11-06 13:00
sidebar: true
comments: false
diff --git a/source/_components/media_player.spotify.markdown b/source/_components/media_player.spotify.markdown
index 7097e06e20..ec34749834 100644
--- a/source/_components/media_player.spotify.markdown
+++ b/source/_components/media_player.spotify.markdown
@@ -29,7 +29,7 @@ To create the required Spotify Application:
- Login to [Spotify Developer](https://developer.spotify.com)
- Visit the [My Applications](https://developer.spotify.com/my-applications/#!/applications) page
-- Select **Create An App**. Enter any name and description. Once your application is created, view it and copy your **Client ID** and **Client Secret**, which are used in the Home Assistant configuration file.
+- Select **Create An App**. Enter any name and description. Once your application is created, view it and copy your **Client ID** and **Client Secret**, which are used in the Home Assistant configuration file.
- Add a **Redirect URI** in the following forms:
No SSL: `http://
-
**Services** from the **Developer Tools** to call the `persistent_notification` service. Select `persistent_notification/create` from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
@@ -87,3 +67,5 @@ Choose
-If you use MariaDB 10 you need to add port 3307 to the SERVER_IP, e.g., `mysql://user:password@SERVER_IP:3307/DB_NAME?charset=utf8`.
-
-+If you are running a database server instance on the same server as Home Assistant then you must ensure that this service starts before Home Assistant. For a Linux instance running Systemd (Raspberry Pi, Debian, Ubuntu and others) then you should edit the service file.
-
-```bash
-$ sudo nano /etc/systemd/system/home-assistant@homeassistant.service
-```
-
-and add the service for PostgreSQL:
-
-```
-[Unit]
-Description=Home Assistant
-After=network.target postgresql.service
-```
-
-Save the file then reload `systemctl`:
-
-```bash
-$ sudo systemctl daemon-reload
-```
-
Due to different logic levels, a voltage level shifter is required between the 3.3V NodeMCU and 5V Arduino MEGA 2560 pins. The BSS138 bidirectional logic level converter has been tested for serial pins and the [link](https://www.aliexpress.com/item/8CH-IIC-I2C-Logic-Level-Converter-Bi-Directional-Module-DC-DC-5V-to-3-3V-Setp/32238089139.html) is recommended for the CC2500 transceiver (used for Ikea Ansluta and Philips Living Colors) @@ -136,7 +136,7 @@ If you find a device is recognized differently, with different protocols or the ### {% linkable_title Technical Overview %} - The`rflink` Python module is an asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway. -- This component uses this callback to distribute 'rflink packet events' over [Home Assistant's event bus](/docs/configuration/events/) which can be subscribed to by entities/platform implementations. +- This component uses this callback to distribute 'rflink packet events' over [Home Assistant's event bus](https://home-assistant.io/docs/configuration/events/) which can be subscribed to by entities/platform implementations. - The platform implementation takes care of creating new devices (if enabled) for unseen incoming packet ID's. - Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entity logic is maintained in this main component. diff --git a/source/_components/rfxtrx.markdown b/source/_components/rfxtrx.markdown index 046e27ac02..64c0e1dee4 100644 --- a/source/_components/rfxtrx.markdown +++ b/source/_components/rfxtrx.markdown @@ -1,7 +1,7 @@ --- layout: page title: "RFXtrx" -description: "Instructions on how to integrate RFXtrx into Home Assistant." +description: "Instructions how to integrate RFXtrx into Home Assistant." date: 2015-10-08 10:15 sidebar: true comments: false @@ -24,7 +24,7 @@ rfxtrx: Configuration variables: -- **device** (*Required*): The path to your device, e.g., `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0` +- **device** (*Required*): The path to your device, e.g. `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0` - **debug** (*Optional*): If you want to receive debug output. - **dummy** (*Optional*): Then you have need a connected drive to test your settings. Can be useful for debugging and testing. diff --git a/source/_components/ring.markdown b/source/_components/ring.markdown index 4daf012653..762810d6a7 100644 --- a/source/_components/ring.markdown +++ b/source/_components/ring.markdown @@ -21,19 +21,13 @@ To enable device linked in your [Ring.com](https://ring.com/) account, add the f ```yaml # Example configuration.yaml entry ring: - username: YOUR_USERNAME - password: YOUR_PASSWORD + username: you@example.com + password: secret ``` -{% configuration %} -username: - description: The username for accessing your Ring account. - required: true - type: string -password: - description: The password for accessing your Ring account. - required: true - type: string -{% endconfiguration %} +Configuration variables: + +- **username** (*Required*): The username for accessing your Ring account. +- **password** (*Required*): The password for accessing your Ring account. Finish its configuration by visiting the [Ring binary sensor](/components/binary_sensor.ring/) or [Ring sensor](/components/sensor.ring/) documentation. diff --git a/source/_components/rpi_gpio.markdown b/source/_components/rpi_gpio.markdown index 31a1befde2..642804ffff 100644 --- a/source/_components/rpi_gpio.markdown +++ b/source/_components/rpi_gpio.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Raspberry Pi GPIO" -description: "Instructions on how to integrate the GPIO capability of a Raspberry Pi into Home Assistant." +description: "Instructions how to integrate the GPIO capability of a Raspberry Pi into Home Assistant." date: 2016-08-30 19:00 sidebar: true comments: false diff --git a/source/_components/rpi_pfio.markdown b/source/_components/rpi_pfio.markdown index 1b3c4785e5..51feb22b70 100644 --- a/source/_components/rpi_pfio.markdown +++ b/source/_components/rpi_pfio.markdown @@ -1,7 +1,7 @@ --- layout: page title: "PiFace Digital I/O" -description: "Instructions on how to integrate the PiFace Digital I/O module into Home Assistant." +description: "Instructions how to integrate the PiFace Digital I/O module into Home Assistant." date: 2016-05-08 15:00 sidebar: true comments: false diff --git a/source/_components/scene.hunterdouglas_powerview.markdown b/source/_components/scene.hunterdouglas_powerview.markdown index 2ef810a113..5598971724 100644 --- a/source/_components/scene.hunterdouglas_powerview.markdown +++ b/source/_components/scene.hunterdouglas_powerview.markdown @@ -1,14 +1,14 @@ --- layout: page title: "PowerView Scenes" -description: "Instructions on how to setup Hunter Douglas PowerView scenes within Home Assistant." +description: "Instructions how to setup Hunter Douglas PowerView scenes within Home Assistant." date: 2016-03-11 16:00 sidebar: true comments: false sharing: true footer: true logo: hunter-douglas-powerview.png -ha_category: Scene +ha_category: Cover ha_release: 0.15 --- diff --git a/source/_components/scene.knx.markdown b/source/_components/scene.knx.markdown deleted file mode 100644 index e77b657181..0000000000 --- a/source/_components/scene.knx.markdown +++ /dev/null @@ -1,34 +0,0 @@ ---- -layout: page -title: "KNX Scene" -description: "Instructions on how to integrate KNX Scenes into Home Assistant." -date: 2018-02-03 20:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: knx.png -ha_category: Scene -ha_release: "0.63" ---- - -The `knx` scenes platform allows you to trigger [KNX](http://www.knx.org) scenes. - -The `knx` component must be configured correctly, see [KNX Component](/components/knx). - -```yaml -# Example configuration.yaml entry -scene: - - name: Romantic - platform: knx - address: 8/8/8 - scene_number: 23 -``` - -Configuration variables: - -- **name** (*Optional*): A name for this device used within Home Assistant. -- **address**: KNX group address of the binary sensor. -- **scene_number** KNX scene number to be activated. - - diff --git a/source/_components/scene.lifx_cloud.markdown b/source/_components/scene.lifx_cloud.markdown index 7b6ac7a279..cddb7cafd2 100644 --- a/source/_components/scene.lifx_cloud.markdown +++ b/source/_components/scene.lifx_cloud.markdown @@ -17,8 +17,8 @@ The `lifx_cloud` scene platform allows you to activate the scenes that LIFX smar ```yaml # Example configuration.yaml entry scene: - - platform: lifx_cloud - token: YOUR_LIFX_TOKEN + platform: lifx_cloud + token: YOUR_LIFX_TOKEN ``` Configuration variables: diff --git a/source/_components/scene.litejet.markdown b/source/_components/scene.litejet.markdown index 511c1cb6fa..fca7954e1b 100644 --- a/source/_components/scene.litejet.markdown +++ b/source/_components/scene.litejet.markdown @@ -1,7 +1,7 @@ --- layout: page title: "LiteJet Scenes" -description: "Instructions on how to setup LiteJet scenes within Home Assistant." +description: "Instructions how to setup LiteJet scenes within Home Assistant." date: 2016-10-26 16:00 sidebar: true comments: false diff --git a/source/_components/scene.lutron_caseta.markdown b/source/_components/scene.lutron_caseta.markdown index 7e07ed485e..2d10556edf 100644 --- a/source/_components/scene.lutron_caseta.markdown +++ b/source/_components/scene.lutron_caseta.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Lutron Caseta Scene" -description: "Instructions on how to setup Lutron Caseta Scenes within Home Assistant." +description: "Instructions how to setup Lutron Caseta Scenes within Home Assistant." date: 2017-07-28 16:00 sidebar: true comments: false diff --git a/source/_components/scene.markdown b/source/_components/scene.markdown index 4bf9f168f7..74e8dd09b4 100644 --- a/source/_components/scene.markdown +++ b/source/_components/scene.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Scenes" -description: "Instructions on how to setup scenes within Home Assistant." +description: "Instructions how to setup scenes within Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -11,7 +11,7 @@ logo: home-assistant.png ha_category: Organization --- -You can create scenes that 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. +You can create scenes that 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. ```yaml # Example configuration.yaml entry @@ -38,13 +38,6 @@ Configuration variables: - **name** (*Required*): Friendly name of scene. - **entities** (*Required*): Entities to control. -As you can see, there are two ways to define the states of each `entity_id`: - -- Define the `state` directly with the entity. -- Define a complex state with its attributes. - -The mapping from states to services is done with the [state helper](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/state.py#L74). So, please have a look there for available states for your scenes. - Scenes can be activated using the service `scene.turn_on` (there is no 'scene.turn_off' service). ```yaml @@ -62,5 +55,5 @@ automation: ```
-Please note that the scene component currently only supports one service call per entity to achieve the state. Due to this limitation, you cannot set states belonging to different services. A workaround for this limitation is to write a script, which you then turn on in your scene. +Please note that the scene component currently only supports one service call per entity to achieve the state. Due to this limitation you cannot set states belonging to different services.
diff --git a/source/_components/scene.tahoma.markdown b/source/_components/scene.tahoma.markdown deleted file mode 100644 index b5cd1c4294..0000000000 --- a/source/_components/scene.tahoma.markdown +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: page -title: "Tahoma Scene" -description: "Instructions on how to integrate Tahoma scenes into Home Assistant." -date: 2018-02-18 12:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: tahoma.png -ha_category: Scene -ha_release: 0.64 ---- - -The `tahoma` scene platform lets you trigger scenes added to your Tahoma Box in Home Assistant. - -Scenes will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma. diff --git a/source/_components/scene.wink.markdown b/source/_components/scene.wink.markdown index cf8e79cf4c..50ef56848f 100644 --- a/source/_components/scene.wink.markdown +++ b/source/_components/scene.wink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Wink Scene" -description: "Instructions on how to setup the Wink scenes(shortcuts) within Home Assistant." +description: "Instructions how to setup the Wink scenes(shortcuts) within Home Assistant." date: 2017-04-01 16:45 sidebar: true comments: false diff --git a/source/_components/script.markdown b/source/_components/script.markdown index 856b758aab..52dd111053 100644 --- a/source/_components/script.markdown +++ b/source/_components/script.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Scripts" -description: "Instructions on how to setup scripts within Home Assistant." +description: "Instructions how to setup scripts within Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -26,7 +26,7 @@ script: message: Current temperature is {% raw %}{{ states.sensor.temperature.state }}{% endraw %} ```-Script names (e.g., `message_temperature` in the example above) are not allowed to contain dash (minus) characters, i.e. `-`. +Script names (e.g. `message_temperature` in the example above) are not allowed to contain dash (minus) characters, i.e. `-`. The preferred way to separate words for better readability is to use underscore (`_`) characters.
diff --git a/source/_components/scsgate.markdown b/source/_components/scsgate.markdown index 30fa3c975f..c70238554c 100644 --- a/source/_components/scsgate.markdown +++ b/source/_components/scsgate.markdown @@ -1,7 +1,7 @@ --- layout: page title: "SCSGate" -description: "Instructions on how to integrate SCSGate into Home Assistant." +description: "Instructions how to integrate SCSGate into Home Assistant." date: 2016-01-31 19:20 sidebar: true comments: false @@ -25,7 +25,7 @@ scsgate: Configuration variables: -- **device** (*Required*): The path to your device, e.g., `/dev/ttyACM0` +- **device** (*Required*): The path to your device, e.g. `/dev/ttyACM0` ### {% linkable_title How to find the scs_id for your devices %} diff --git a/source/_components/sensor.abode.markdown b/source/_components/sensor.abode.markdown index f2076b85f9..b886d385ab 100644 --- a/source/_components/sensor.abode.markdown +++ b/source/_components/sensor.abode.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Abode Sensor" -description: "Instructions on how to integrate Abode sensors into Home Assistant." +description: "Instructions how to integrate Abode sensors into Home Assistant." date: 2017-10-05 14:00 sidebar: true comments: false diff --git a/source/_components/sensor.ads.markdown b/source/_components/sensor.ads.markdown index 2360ac70c3..0e65a67bb6 100644 --- a/source/_components/sensor.ads.markdown +++ b/source/_components/sensor.ads.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ADS Sensor" -description: "Instructions on how to integrate ADS numeric values into Home Assistant." +description: "Instructions how to integrate ADS numeric values into Home Assistant." date: 2017-10-25 10:00 sidebar: true comments: false diff --git a/source/_components/sensor.alarmdecoder.markdown b/source/_components/sensor.alarmdecoder.markdown index 770e94f1b7..d7b0483f9a 100644 --- a/source/_components/sensor.alarmdecoder.markdown +++ b/source/_components/sensor.alarmdecoder.markdown @@ -1,7 +1,7 @@ --- layout: page title: "AlarmDecoder Sensor" -description: "Instructions on how to integrate AlarmDecoder sensors into Home Assistant." +description: "Instructions how to integrate AlarmDecoder sensors into Home Assistant." date: 2017-04-02 13:28 sidebar: true comments: false diff --git a/source/_components/sensor.alpha_vantage.markdown b/source/_components/sensor.alpha_vantage.markdown index 25714dd5cc..29712a8d0c 100644 --- a/source/_components/sensor.alpha_vantage.markdown +++ b/source/_components/sensor.alpha_vantage.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Alpha Vantage" -description: "Instructions on how to setup Alpha Vantage within Home Assistant." +description: "Instructions how to setup Alpha Vantage within Home Assistant." date: 2017-12-02 12:00 sidebar: true comments: false @@ -14,7 +14,7 @@ featured: false ha_release: "0.60" --- -The `alpha_vantage` sensor platform uses [Alpha Vantage](https://www.alphavantage.co) to monitor the stock market. This platform also provides detail about exchange rates. +The `alpha_vantage` sensor platform uses [Alpha Vantage](https://www.alphavantage.co) to monitor the stock market. To enable the `alpha_vantage` platform, add the following lines to your `configuration.yaml` file: @@ -23,17 +23,8 @@ To enable the `alpha_vantage` platform, add the following lines to your `configu sensor: - platform: alpha_vantage api_key: YOUR_API_KEY - symbols: - - symbol: GOOGL - name: Google - foreign_exchange: - - name: USD_EUR - from: USD - to: EUR ``` -Either a symbol or a foreign exchange must be configured, otherwise you will not get any data. - {% configuration %} api_key: description: "The API Key from [Alpha Vantage](https://www.alphavantage.co)." @@ -42,6 +33,7 @@ api_key: symbols: description: List of stock market symbols for given companies. required: false + default: GOOGL type: map keys: name: diff --git a/source/_components/sensor.amcrest.markdown b/source/_components/sensor.amcrest.markdown index 127021a1e2..538369de5a 100644 --- a/source/_components/sensor.amcrest.markdown +++ b/source/_components/sensor.amcrest.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Amcrest IP Camera" -description: "Instructions on how to integrate Amcrest IP cameras sensors within Home Assistant." +description: "Instructions how to integrate Amcrest IP cameras sensors within Home Assistant." date: 2017-01-13 10:00 sidebar: true comments: false diff --git a/source/_components/sensor.android_ip_webcam.markdown b/source/_components/sensor.android_ip_webcam.markdown index 35d4eefb7a..87f6f0d783 100644 --- a/source/_components/sensor.android_ip_webcam.markdown +++ b/source/_components/sensor.android_ip_webcam.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Android IP Webcam Sensor" -description: "Instructions on how to integrate sensors for Android IP webcam within Home Assistant." +description: "Instructions how to integrate sensors for Android IP webcam within Home Assistant." date: 2017-03-10 00:00 sidebar: true comments: false diff --git a/source/_components/sensor.api_stream.markdown b/source/_components/sensor.api_stream.markdown index c363e88533..4b2c2a26ec 100644 --- a/source/_components/sensor.api_stream.markdown +++ b/source/_components/sensor.api_stream.markdown @@ -1,7 +1,7 @@ --- layout: page title: "API Stream Sensor" -description: "Instructions on how to count clients using the API stream within Home Assistant." +description: "Instructions how to count clients using the API stream within Home Assistant." date: 2016-11-19 10:00 sidebar: true comments: false diff --git a/source/_components/sensor.arduino.markdown b/source/_components/sensor.arduino.markdown index f7f686370a..b7e4c1c6d7 100644 --- a/source/_components/sensor.arduino.markdown +++ b/source/_components/sensor.arduino.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Arduino Sensor" -description: "Instructions on how to integrate Arduino boards pins as sensors within Home Assistant." +description: "Instructions how to integrate Arduino boards pins as sensors within Home Assistant." date: 2015-09-14 18:28 sidebar: true comments: false diff --git a/source/_components/sensor.arest.markdown b/source/_components/sensor.arest.markdown index 4f7c68732f..bf5c31651c 100644 --- a/source/_components/sensor.arest.markdown +++ b/source/_components/sensor.arest.markdown @@ -1,7 +1,7 @@ --- layout: page title: "aREST Sensor" -description: "Instructions on how to integrate aREST sensors within Home Assistant." +description: "Instructions how to integrate aREST sensors within Home Assistant." date: 2015-09-07 18:15 sidebar: true comments: false @@ -33,7 +33,7 @@ sensor: Configuration variables: -- **resource** (*Required*): IP address and schema of the device that is exposing an aREST API, e.g., http://192.168.1.10. +- **resource** (*Required*): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10. - **name** (*Optional*): Let you overwrite the name of the device. By default *name* from the device is used. - **monitored_variables** array (*Optional*): List of exposed variables. - **[variable]** (*Required*): Name of the variable to monitor. diff --git a/source/_components/sensor.arlo.markdown b/source/_components/sensor.arlo.markdown index e5184d2ed0..309795f795 100644 --- a/source/_components/sensor.arlo.markdown +++ b/source/_components/sensor.arlo.markdown @@ -15,10 +15,6 @@ ha_iot_class: "Cloud Polling" To get your [Arlo](https://arlo.netgear.com/) sensors working within Home Assistant, please follow the instructions for the general [Arlo component](/components/arlo). -This platform does not support Arlo Q. - -## {% linkable_title Configuration %} - Once you have enabled the [Arlo component](/components/arlo), add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/sensor.arwn.markdown b/source/_components/sensor.arwn.markdown index 8a9eea544a..fb66cc50bd 100644 --- a/source/_components/sensor.arwn.markdown +++ b/source/_components/sensor.arwn.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ARWN Sensor" -description: "Instructions on how to integrate ARWN within Home Assistant." +description: "Instructions how to integrate ARWN within Home Assistant." date: 2016-10-20 15:15 sidebar: true comments: false diff --git a/source/_components/sensor.bh1750.markdown b/source/_components/sensor.bh1750.markdown index 4910cdfba0..8b07a84482 100644 --- a/source/_components/sensor.bh1750.markdown +++ b/source/_components/sensor.bh1750.markdown @@ -1,7 +1,7 @@ --- layout: page title: "BH1750 Light sensor" -description: "Instructions on how to integrate a BH1750 light sensor into Home Assistant." +description: "Instructions how to integrate a BH1750 light sensor into Home Assistant." date: 2017-06-10 00:00 sidebar: true comments: false diff --git a/source/_components/sensor.bitcoin.markdown b/source/_components/sensor.bitcoin.markdown index ba47bf8d9e..85173adc72 100644 --- a/source/_components/sensor.bitcoin.markdown +++ b/source/_components/sensor.bitcoin.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Bitcoin" -description: "Instructions on how to integrate Bitcoin data within Home Assistant." +description: "Instructions how to integrate Bitcoin data within Home Assistant." date: 2015-05-08 17:15 sidebar: true comments: false diff --git a/source/_components/sensor.blockchain.markdown b/source/_components/sensor.blockchain.markdown index 8c441ff88b..21da288337 100644 --- a/source/_components/sensor.blockchain.markdown +++ b/source/_components/sensor.blockchain.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Blockchain.info" -description: "Instructions on how to integrate Blockchain.info data within Home Assistant." +description: "Instructions how to integrate Blockchain.info data within Home Assistant." date: 2017-06-01 16:20 sidebar: true comments: false diff --git a/source/_components/sensor.bloomsky.markdown b/source/_components/sensor.bloomsky.markdown index 61b850de1e..a975a0300c 100644 --- a/source/_components/sensor.bloomsky.markdown +++ b/source/_components/sensor.bloomsky.markdown @@ -1,7 +1,7 @@ --- layout: page title: "BloomSky Sensor" -description: "Instructions on how to integrate the BloomSky sensors within Home Assistant." +description: "Instructions how to integrate the BloomSky sensors within Home Assistant." date: 2016-02-03 20:00 sidebar: true comments: false diff --git a/source/_components/sensor.bme280.markdown b/source/_components/sensor.bme280.markdown index 7dd524405a..8da831b067 100644 --- a/source/_components/sensor.bme280.markdown +++ b/source/_components/sensor.bme280.markdown @@ -1,7 +1,7 @@ --- layout: page title: "BME280 Sensor" -description: "Instructions on how to integrate a BME280 sensor into Home Assistant." +description: "Instructions how to integrate a BME280 sensor into Home Assistant." date: 2017-06-10 00:00 sidebar: true comments: false diff --git a/source/_components/sensor.bme680.markdown b/source/_components/sensor.bme680.markdown index 05d42769c1..e6978a3f0f 100644 --- a/source/_components/sensor.bme680.markdown +++ b/source/_components/sensor.bme680.markdown @@ -105,7 +105,7 @@ aq_humidity_baseline: default: 40 type: int aq_humidity_bias: - description: The bias for humidity to the gas resistance measurement in the air quality calculations expressed as a percentage of the total calculation e.g., 25% hudidtity to 75% gas. + description: The bias for humidity to the gas resistance measurement in the air quality calculations expressed as a percentage of the total calculation e.g. 25% hudidtity to 75% gas. required: false default: 25 type: int diff --git a/source/_components/sensor.bmw_connected_drive.markdown b/source/_components/sensor.bmw_connected_drive.markdown deleted file mode 100644 index 083e5124a6..0000000000 --- a/source/_components/sensor.bmw_connected_drive.markdown +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: page -title: "BMW Connected Drive Sensor" -description: "Instructions on how to setup your BMW Connected Drive account with Home Assistant." -date: 2018-01-10 23:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: bmw.png -ha_category: Sensor -ha_release: 0.64 ---- - - -The `bmw_connected_drive` platform allows you to import data on your BMW into Home Assistant. - -The sensors will be automatically configured if the `bmw_connected_drive` component is configured. - -For more configuration information see the [`bmw_connected_drive` component](/components/bmw_connected_drive/) documentation. diff --git a/source/_components/sensor.broadlink.markdown b/source/_components/sensor.broadlink.markdown index 4688cf2aa0..70e82936ad 100644 --- a/source/_components/sensor.broadlink.markdown +++ b/source/_components/sensor.broadlink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Broadlink RM2 and A1 sensor" -description: "Instructions on how to integrate Broadlink RM2 and/or A1 E-air sensors within Home Assistant." +description: "Instructions how to integrate Broadlink RM2 and/or A1 E-air sensors within Home Assistant." date: 2016-12-03 21:59 sidebar: true comments: false @@ -78,7 +78,7 @@ sensor: The pycrypto library needs to be available on your platform. On a typical windows sysytem `pip install pycrypto` will fail, as a compiler needs to be installed first. -The quickest way around this is to use a pre-built binary, e.g., from [https://github.com/sfbahr/PyCrypto-Wheels](https://github.com/sfbahr/PyCrypto-Wheels) +The quickest way around this is to use a pre-built binary, e.g. from [https://github.com/sfbahr/PyCrypto-Wheels](https://github.com/sfbahr/PyCrypto-Wheels) Be sure to get the correct 64 or 32-bit binary for your system, the full command line will look something like the sample below for a 64-bit system: diff --git a/source/_components/sensor.buienradar.markdown b/source/_components/sensor.buienradar.markdown index 63e1f88b46..cb1cd65660 100644 --- a/source/_components/sensor.buienradar.markdown +++ b/source/_components/sensor.buienradar.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "Buienradar Sensor" -description: "Instructions on how to integrate buienradar.nl sensor within Home Assistant." +title: "Buienradar" +description: "Instructions how to integrate buienradar.nl sensor within Home Assistant." date: 2017-05-15 14:00 sidebar: true comments: false diff --git a/source/_components/sensor.coinbase.markdown b/source/_components/sensor.coinbase.markdown index c506d82341..89c06fc6f3 100644 --- a/source/_components/sensor.coinbase.markdown +++ b/source/_components/sensor.coinbase.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Coinbase Sensor" -description: "Instructions on how to setup Coinbase sensors within Home Assistant." +description: "Instructions how to setup Coinbase sensors within Home Assistant." date: 2017-12-08 18:00 sidebar: true comments: false diff --git a/source/_components/sensor.coinmarketcap.markdown b/source/_components/sensor.coinmarketcap.markdown index 1fc1300ab5..63fde6b5ea 100644 --- a/source/_components/sensor.coinmarketcap.markdown +++ b/source/_components/sensor.coinmarketcap.markdown @@ -1,7 +1,7 @@ --- layout: page title: "CoinMarketCap" -description: "Instructions on how to integrate CoinMarketCap data within Home Assistant." +description: "Instructions how to integrate CoinMarketCap data within Home Assistant." date: 2016-08-31 08:15 sidebar: true comments: false diff --git a/source/_components/sensor.comed_hourly_pricing.markdown b/source/_components/sensor.comed_hourly_pricing.markdown index b371c8c197..d278c8a713 100644 --- a/source/_components/sensor.comed_hourly_pricing.markdown +++ b/source/_components/sensor.comed_hourly_pricing.markdown @@ -1,7 +1,7 @@ --- layout: page title: "ComEd Hourly Pricing" -description: "Instructions on how to set up the ComEd Hourly Pricing sensor in Home Assistant." +description: "Instructions how to set up the ComEd Hourly Pricing sensor in Home Assistant." date: 2017-03-02 0:15 sidebar: true comments: false diff --git a/source/_components/sensor.comfoconnect.markdown b/source/_components/sensor.comfoconnect.markdown index 0d9400f5ce..78d22454b9 100644 --- a/source/_components/sensor.comfoconnect.markdown +++ b/source/_components/sensor.comfoconnect.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Zehnder ComfoAir Q Ventilation sensors" -description: "Instructions on how to integrate Zehnder ComfoAir Q350/450/600 sensors into Home Assistant." +description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 sensors into Home Assistant." date: 2017-06-28 18:00 sidebar: true comments: false diff --git a/source/_components/sensor.command_line.markdown b/source/_components/sensor.command_line.markdown index 5cc0b4d9ea..e27656e9a5 100644 --- a/source/_components/sensor.command_line.markdown +++ b/source/_components/sensor.command_line.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Command line Sensor" -description: "Instructions on how to integrate command line sensors into Home Assistant." +description: "Instructions how to integrate command line sensors into Home Assistant." date: 2015-09-13 10:10 sidebar: true comments: false @@ -31,7 +31,7 @@ Configuration variables: - **name** (*Optional*): Name of the command sensor. - **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any. - **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload. -- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds). +- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds). ## {% linkable_title Examples %} @@ -61,7 +61,6 @@ sensor: Thanks to the [`proc`](https://en.wikipedia.org/wiki/Procfs) file system, various details about a system can be retrieved. Here the CPU temperature is of interest. Add something similar to your `configuration.yaml` file: -{% raw %} ```yaml # Example configuration.yaml entry sensor: @@ -70,9 +69,8 @@ sensor: command: "cat /sys/class/thermal/thermal_zone0/temp" # If errors occur, remove degree symbol below unit_of_measurement: "°C" - value_template: '{{ value | multiply(0.001) | round(1) }}' + value_template: '{% raw %}{{ value | multiply(0.001) }}{% endraw %}' ``` -{% endraw %} ### {% linkable_title Monitoring failed login attempts on Home Assistant %} @@ -86,7 +84,7 @@ sensor: command: "grep -c 'Login attempt' /home/hass/.homeassistant/home-assistant.log" ``` -Make sure to configure the [logger component](/components/logger) to monitor the [http component](/components/http/) at least the `warning` level. +Make sure to configure the [logger component](/components/logger) to monitor the [http component](https://home-assistant.io/components/http/) at least the `warning` level. ```yaml # Example working logger settings that works @@ -151,13 +149,11 @@ sensor: [Templates](/docs/configuration/templating/) are supported in the `command:` configuration variable. This could be used if you want to include the state of a specific sensor as an argument to your external script. -{% raw %} ```yaml # Example configuration.yaml entry sensor: - platform: command_line name: wind direction - command: 'sh /home/pi/.homeassistant/scripts/wind_direction.sh {{ states.sensor.wind_direction.state }}' + command: 'sh /home/pi/.homeassistant/scripts/wind_direction.sh {% raw %}{{ states.sensor.wind_direction.state }}{% endraw %}' unit_of_measurement: "Direction" ``` -{% endraw %} diff --git a/source/_components/sensor.cpuspeed.markdown b/source/_components/sensor.cpuspeed.markdown index f69f014967..c997ae5a2f 100644 --- a/source/_components/sensor.cpuspeed.markdown +++ b/source/_components/sensor.cpuspeed.markdown @@ -1,7 +1,7 @@ --- layout: page title: "CPU speed" -description: "Instructions on how to integrate CPU speed within Home Assistant." +description: "Instructions how to integrate CPU speed within Home Assistant." date: 2015-10-15 11:00 sidebar: true comments: false diff --git a/source/_components/sensor.cups.markdown b/source/_components/sensor.cups.markdown index 2e32f5aa0f..eb9f43e9dd 100644 --- a/source/_components/sensor.cups.markdown +++ b/source/_components/sensor.cups.markdown @@ -1,7 +1,7 @@ --- layout: page title: "CUPS Sensor" -description: "Instructions on how to integrate CUPS sensors into Home Assistant." +description: "Instructions how to integrate CUPS sensors into Home Assistant." date: 2016-10-30 12:10 sidebar: true comments: false diff --git a/source/_components/sensor.darksky.markdown b/source/_components/sensor.darksky.markdown index 6b110a6c72..11edb0c1ce 100644 --- a/source/_components/sensor.darksky.markdown +++ b/source/_components/sensor.darksky.markdown @@ -9,7 +9,7 @@ sharing: true footer: true logo: dark_sky.png ha_category: Weather -featured: false +featured: true ha_release: "0.30" redirect_from: /components/sensor.forecast/ ha_iot_class: "Cloud Polling" @@ -41,46 +41,6 @@ Configuration variables: - **api_key** (*Required*): Your API key. - **name** (*Optional*): Additional name for the sensors. Default to platform name. - **forecast** array (*Optional*): List of days in the 7 day forecast you would like to receive data on, starting with tomorrow as day 1. Any `monitored_condition` with a daily forecast by DarkSky will generate a sensor tagged with `_Your system must have `fail2ban` installed and correctly configured for this sensor to work. In addition, Home Assistant must be able to read the `fail2ban` log file. @@ -72,7 +72,7 @@ logger: #### {% linkable_title Edit the `jail.local` file %} -Next, we need to edit the `jail.local` file that is included with the Let's Encrypt docker linked above. Note, for this tutorial, we'll only be implementing the `[hass-iptables]` jail from the [previously linked tutorial](/cookbook/fail2ban/). +Next, we need to edit the `jail.local` file that is included with the Let's Encrypt docker linked above. Note, for this tutorial, we'll only be implementing the `[hass-iptables]` jail from the [previously linked tutorial](https://home-assistant.io/cookbook/fail2ban/). Edit `/mnt/user/appdata/letsencrypt/fail2ban/jail.local` and append the following to the end of the file: @@ -123,7 +123,7 @@ Now do the same for the Home Assistant docker, but this time we'll be mapping th By default, the IP address that Home Assistant sees will be that of the container (something like `172.17.0.16`). What this means is that for any failed login attempt, assuming you have correctly configured `fail2ban`, the Docker IP will be logged as banned, but the originating IP is still allowed to make attempts. We need `fail2ban` to recognize the originating IP to properly ban it. -First, we have to add the following to the nginx configuration file located in `/mnt/user/appdata/letsencrypt/nginx/site-confs/default`. +First, we have to add the following to the nginx configuration file located in `/mnt/user/appdata/letsencrypt/nginx/site-confs/default`. ```bash proxy_set_header X-Real-IP $remote_addr; @@ -136,7 +136,7 @@ This snippet should be added within your Home Assistant server config, so you ha server { ... location / { - proxy_pass http://192.168.0.100:8123; + proxy_pass http://192.168.0.100:8123; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; @@ -153,7 +153,7 @@ server { proxy_set_header Connection "upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; - } + } ... } ``` diff --git a/source/_components/sensor.fido.markdown b/source/_components/sensor.fido.markdown index edb59195a3..165f52bbf0 100644 --- a/source/_components/sensor.fido.markdown +++ b/source/_components/sensor.fido.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Fido" -description: "Instructions on how to integrate Fido data usage within Home Assistant." +description: "Instructions how to integrate Fido data usage within Home Assistant." date: 2017-01-01 17:17 sidebar: true comments: false diff --git a/source/_components/sensor.file.markdown b/source/_components/sensor.file.markdown index 8ae7216a7d..741d297c41 100644 --- a/source/_components/sensor.file.markdown +++ b/source/_components/sensor.file.markdown @@ -1,7 +1,7 @@ --- layout: page title: "File Sensor" -description: "Instructions on how to integrate sensors which read from files into Home Assistant." +description: "Instructions how to integrate sensors which read from files into Home Assistant." date: 2017-05-13 12:10 sidebar: true comments: false @@ -14,7 +14,7 @@ ha_release: 0.45 --- -The `file` sensor platform reads the entries from a plain-text file and shows the found value. Only the last line of the file is used. This is similar to do `$ tail -n 1 sensor.txt` on the command-line. Note that file paths must be added to [whitelist_external_dirs](/docs/configuration/basic/). +The `file` sensor platform reads the entries from a plain-text file and shows the found value. Only the last line of the file is used. This is similar to do `$ tail -n 1 sensor.txt` on the command-line. To enable the `file` sensor, add the following lines to your `configuration.yaml`: diff --git a/source/_components/sensor.filesize.markdown b/source/_components/sensor.filesize.markdown deleted file mode 100644 index 3178fa6e3c..0000000000 --- a/source/_components/sensor.filesize.markdown +++ /dev/null @@ -1,31 +0,0 @@ ---- -layout: page -title: "File size sensor" -description: "Component for monitoring the size of a file." -date: 2018-02-06 14:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: file.png -ha_category: Sensor -ha_iot_class: "Local Polling" -ha_release: 0.64 ---- - -Component for displaying the size in MB of a file. Note that paths must be added to [whitelist_external_dirs](/docs/configuration/basic/). -Add to your config: - -```yaml -sensor: - - platform: filesize - file_paths: - - /config/home-assistant_v2.db - ``` - -{% configuration %} -file_paths: - description: The absolute path to the file. - required: true - type: list of strings -{% endconfiguration %} diff --git a/source/_components/sensor.filter.markdown b/source/_components/sensor.filter.markdown deleted file mode 100644 index 30661e8d1f..0000000000 --- a/source/_components/sensor.filter.markdown +++ /dev/null @@ -1,146 +0,0 @@ ---- -layout: page -title: "Filter Sensor" -description: "Instructions on how to integrate Data Filter Sensors into Home Assistant." -date: 2018-02-20 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Sensor -ha_release: 0.65 -ha_iot_class: "Local Push" -logo: home-assistant.png ---- - -The `filter` platform enables sensors that process the states of other entities. - -`filter` applies a signal processing algorithm to a sensor, previous and current states, and generates a `new state` given the chosen algorithm. The next image depicts an original sensor and the filter sensor of that same sensor using the [History Graph]({{site_roor}}/components/history_graph/) component. - -
- 
-
Full configuration details can be found on the main [Hive component](/components/hive/) page.
diff --git a/source/_components/sensor.homematic.markdown b/source/_components/sensor.homematic.markdown
index 005011cea6..aea1b6d5ef 100644
--- a/source/_components/sensor.homematic.markdown
+++ b/source/_components/sensor.homematic.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Homematic Sensor"
-description: "Instructions on how to integrate Homematic sensors within Home Assistant."
+description: "Instructions how to integrate Homematic sensors within Home Assistant."
date: 2016-06-28 08:30
sidebar: true
comments: false
diff --git a/source/_components/sensor.homematicip_cloud.markdown b/source/_components/sensor.homematicip_cloud.markdown
deleted file mode 100644
index bfb8449890..0000000000
--- a/source/_components/sensor.homematicip_cloud.markdown
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: page
-title: "HomematicIP Cloud Sensor"
-description: "Instructions on how to integrate HomematIP sensors within Home Assistant."
-date: 2018-04-02 13:40
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: homematic.png
-ha_category: Sensor
-ha_release: 0.66
-ha_iot_class: "Local Push"
----
-
-The `homematicip_cloud` sensor platform allows you to control
-[HomematicIP](http://www.homematicip.de) sensors through Home Assistant.
-
-Devices will be configured automatically. Please refer to the
-[component](/components/homematicip_cloud/) configuration on how to setup
-HomematicIP Cloud.
diff --git a/source/_components/sensor.hp_ilo.markdown b/source/_components/sensor.hp_ilo.markdown
index f242584b9d..1f51f2052c 100644
--- a/source/_components/sensor.hp_ilo.markdown
+++ b/source/_components/sensor.hp_ilo.markdown
@@ -15,7 +15,7 @@ ha_iot_class: "Local Polling"
The `hp_ilo` platform allows you to do an API call to the HP ILO (Integrated Lights-Out) sensor of your server, and use this data in Home Assistant sensors.
-If the ILO or specified jsonpath query returns only a single value (e.g., a temperature or state), it will be put in the state field. If a data structure is returned, it will be placed in the `ilo_data` attribute.
+If the ILO or specified jsonpath query returns only a single value (e.g. a temperature or state), it will be put in the state field. If a data structure is returned, it will be placed in the `ilo_data` attribute.
Some more details about what can be retrieved from these sensors is available in the [python-hpilo documentation](http://pythonhosted.org/python-hpilo/).
@@ -23,7 +23,6 @@ Some more details about what can be retrieved from these sensors is available in
-If you set `show_on_map` to `True` then the location attributes are named `latitude` and `longitude`. The default name of the location attributes is `lat` and `long` to avoid showing them on the map. -
- Not all sensors provide all conditions. Also, it's possible that the sensor values are not available all the time. To check what a sensor is publishing use `curl`: ```bash diff --git a/source/_components/sensor.markdown b/source/_components/sensor.markdown index 647f0e7ab0..9f446e5266 100644 --- a/source/_components/sensor.markdown +++ b/source/_components/sensor.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Sensor" -description: "Instructions on how to setup your sensors with Home Assistant." +description: "Instructions how to setup your sensors with Home Assistant." date: 2015-01-24 14:39 sidebar: true comments: false @@ -9,21 +9,8 @@ sharing: true footer: true --- -Sensors are gathering information about states and conditions. +Sensors are gathering information about states and conditions. -Home Assistant currently supports a wide range of sensors. They are able to display information which are provides by Home Assistant directly, are gathered from web services, and, of course, physical devices. Please check the sidebar for a full list of supported sensor platforms. +Home Assistant currently supports a wide range of sensors. They are able to display information which are provides by Home assistant directly, are gathered from web services, and, of course, physical devices. Please check the sidebar for a full list of supported sensor platforms. -### {% linkable_title Device Class %} -The way these sensors are displayed in the frontend can be modified in the [customize section](/docs/configuration/customizing-devices/). The following device classes are supported for sensors: - -- **None**: Generic sensor. This is the default and doesn't need to be set. -- **battery**: Percentage of battery that is left. -- **humidity**: Percentage of humidity in the air. -- **illuminance**: The current light level in lx or lm. -- **temperature**: Temperature in °C or °F. - -
-
-Example of various device class icons for sensors.
-
-It is vital that your system clock is correct both on your Home Assistant server and on your OTP generator device (e.g., your phone). If not, the generated codes will not match! Make sure NTP is running and syncing your time correctly before creating an issue. +It is vital that your system clock is correct both on your Home Assistant server and on your OTP generator device (e.g. your phone). If not, the generated codes will not match! Make sure NTP is running and syncing your time correctly before creating an issue.
diff --git a/source/_components/sensor.pi_hole.markdown b/source/_components/sensor.pi_hole.markdown index f0b5dedbdb..809cee76ca 100644 --- a/source/_components/sensor.pi_hole.markdown +++ b/source/_components/sensor.pi_hole.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Pi-Hole Sensor" -description: "Instructions on how to integrate REST sensors into Home Assistant." +description: "Instructions how to integrate REST sensors into Home Assistant." date: 2016-09-03 16:30 sidebar: true comments: false diff --git a/source/_components/sensor.pilight.markdown b/source/_components/sensor.pilight.markdown index 2a33cc2a1d..276586c98c 100644 --- a/source/_components/sensor.pilight.markdown +++ b/source/_components/sensor.pilight.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Pilight Sensor" -description: "Instructions on how to integrate pilight sensors within Home Assistant." +description: "Instructions how to integrate pilight sensors within Home Assistant." date: 2016-10-08 23:21 sidebar: true comments: false @@ -14,14 +14,12 @@ ha_iot_class: depends --- -This `pilight` sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g., _uuid_) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up. - -## {% linkable_title Configuration %} +This `pilight` sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. _uuid_) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up. To use your sensor via pilight, make sure it is [supported](https://wiki.pilight.org/doku.php/protocols) and add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry sensor: - platform: pilight variable: temperature diff --git a/source/_components/sensor.pollen.markdown b/source/_components/sensor.pollen.markdown deleted file mode 100644 index 8c61388224..0000000000 --- a/source/_components/sensor.pollen.markdown +++ /dev/null @@ -1,86 +0,0 @@ ---- -layout: page -title: "Pollen.com" -description: "Instructions on how to use Pollen.com data within Home Assistant" -date: 2018-01-10 19:20:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: pollen.jpg -ha_category: Health -ha_release: 0.63 -ha_iot_class: "Cloud Polling" ---- - -The `pollen` sensor platform collects and displays allergy and disease -information (based on a U.S. ZIP code) from [Pollen.com](https://www.pollen.com/). Data measured includes: - -* Indicies for allergies and cold/flu measurements -* Trends -* Current outlook -* more! - -## {% linkable_title Configuring the Platform %} - -To integrate `pollen` into Home Assistant, add the following section to your -`configuration.yaml` file (adjusting the `monitored_conditions` list to your -liking): - -```yaml -sensor: - platform: pollen - zip_code: "00544" - monitored_conditions: - - allergy_average_forecasted - - allergy_average_historical - - allergy_index_today - - allergy_index_tomorrow - - allergy_index_yesterday - - disease_average_forecasted -``` - -{% configuration %} - zip_code: - description: the U.S. ZIP code to gather data for (as a quoted string) - required: true - type: string - monitored_conditions: - description: the metric types to monitor; valid values are specified below - required: true - type: list -{% endconfiguration %} - --It is important to ensure the ZIP code is quoted if it starts with a 0. Unquoted -ZIP codes that start with 0 will cause errors. -
- -## {% linkable_title Available Metrics %} - -The following metrics can be monitored: - -* Allergy Index: Forecasted Average (`allergy_average_forecasted`): the average -forecasted allergy index over the next 5 days -* Allergy Index: Historical Average (`allergy_average_historical`): the average -historical allergy index over the past 30 days -* Allergy Index: Today (`allergy_index_today`): the allergy index for today -* Allergy Index: Tomorrow (`allergy_index_tomorrow`): the allergy index for -tomorrow -* Allergy Index: Yesterday (`allergy_index_yesterday`): the allergy index for -yesterday -* Cold & Flu: Forecasted Average (`disease_average_forecasted`): the average -forecasted cold/flu index over the next 5 days - -## {% linkable_title Understanding the Indices %} - -Any index-related sensor will have a value between 0.0 and 12.0. The values -map to the following human-friendly ratings: - -Range | Rating ---------- | ----------- -0.0 - 2.4 | Low -2.5 - 4.8 | Low/Medium -4.9 - 7.2 | Medium -7.3 - 9.6 | Medium/High -9.7 - 12.0 | High diff --git a/source/_components/sensor.postnl.markdown b/source/_components/sensor.postnl.markdown deleted file mode 100644 index 3087ce4b01..0000000000 --- a/source/_components/sensor.postnl.markdown +++ /dev/null @@ -1,47 +0,0 @@ ---- -layout: page -title: PostNL Sensor -description: "Instructions on how to set up PostNL sensors within Home Assistant." -date: 2017-04-22 08:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: postnl.png -ha_category: Sensor -ha_release: 0.69 -ha_iot_class: "Cloud Polling" ---- - -The `postnl` platform allows one to track deliveries by [PostNL](https://www.postnl.nl) (Dutch Postal Services). To use this sensor, you need a [PostNL Account](https://jouw.postnl.nl). It is possible to add multiple accounts to your Home Assistant configuration. - -## {% linkable_title Configuration %} - -To enable this sensor, add the following lines to your `configuration.yaml`: - -```yaml -sensors: - - platform: postnl - username: POSTNL_USERNAME - password: POSTNL_PASSWORD -``` - -{% configuration %} -name: - description: Sensor name - required: false - default: "postnl" - type: string -username: - description: Account username of jouw.postnl.nl - required: true - type: string -password: - description: Account password of jouw.postnl.nl - required: true - type: string -{% endconfiguration %} - --This component is not affiliated with PostNL and retrieves date from the endpoints of the mobile application. Use at your own risk. -
diff --git a/source/_components/sensor.pushbullet.markdown b/source/_components/sensor.pushbullet.markdown index bd8ee0eda5..df04990f68 100644 --- a/source/_components/sensor.pushbullet.markdown +++ b/source/_components/sensor.pushbullet.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Pushbullet Mirrors" -description: "Instructions on how to read user pushes in Home Assistant" +description: "Instructions how to read user pushes in Home Assistant" date: 2017-04-20 16:44 sidebar: true comments: false diff --git a/source/_components/sensor.pvoutput.markdown b/source/_components/sensor.pvoutput.markdown index a61f661459..b36ded0c28 100644 --- a/source/_components/sensor.pvoutput.markdown +++ b/source/_components/sensor.pvoutput.markdown @@ -1,7 +1,7 @@ --- layout: page title: "PVOutput Sensor" -description: "Instructions on how to use PVOutput within Home Assistant." +description: "Instructions how to use PVOutput within Home Assistant." date: 2016-11-06 10:00 sidebar: true comments: false diff --git a/source/_components/sensor.pyload.markdown b/source/_components/sensor.pyload.markdown index 0c5886b637..c4d7611edb 100644 --- a/source/_components/sensor.pyload.markdown +++ b/source/_components/sensor.pyload.markdown @@ -1,7 +1,7 @@ --- layout: page title: "pyLoad Sensor" -description: "Instructions on how to integrate pyLoad download sensor within Home Assistant." +description: "Instructions how to integrate pyLoad download sensor within Home Assistant." date: 2017-10-23 09:00 sidebar: true comments: false diff --git a/source/_components/sensor.qnap.markdown b/source/_components/sensor.qnap.markdown index 3814f37bd0..38dd16ca98 100644 --- a/source/_components/sensor.qnap.markdown +++ b/source/_components/sensor.qnap.markdown @@ -1,7 +1,7 @@ --- layout: page title: "QNAP Sensor" -description: "Instructions on how to integrate the QNAP sensor within Home Assistant." +description: "Instructions how to integrate the QNAP sensor within Home Assistant." date: 2017-02-02 06:39 sidebar: true comments: false @@ -16,12 +16,10 @@ ha_iot_class: "Local Polling" This `qnap` sensor allows getting various statistics from your [QNAP NAS](https://www.qnap.com/en-us/). -## {% linkable_title Configuration %} - To use the `qnap` sensor in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry sensor: - platform: qnap host: IP_ADDRESS_OF_QNAP_NAS diff --git a/source/_components/sensor.qwikswitch.markdown b/source/_components/sensor.qwikswitch.markdown deleted file mode 100644 index afc4fc6cb4..0000000000 --- a/source/_components/sensor.qwikswitch.markdown +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: page -title: "QwikSwitch Sensor" -description: "Instructions on how to integrate Qwikswitch dimmers and relays as sensors into Home Assistant." -date: 2016-05-04 00:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: qwikswitch.png -ha_category: Sensor -ha_iot_class: "Local Push" -ha_release: "0.67" ---- - -The `qwikswitch` sensor platform allows you to use your [QwikSwitch](http://www.qwikswitch.co.za/) sensors in Home Assistant. - -The platform is configured through the [QwikSwitch component](/components/qwikswitch/). diff --git a/source/_components/sensor.radarr.markdown b/source/_components/sensor.radarr.markdown index 94a4665548..78ca33d041 100644 --- a/source/_components/sensor.radarr.markdown +++ b/source/_components/sensor.radarr.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Radarr Sensor" -description: "Instructions on how to integrate Radarr sensors with Home Assistant" +description: "Instructions how to integrate Radarr sensors with Home Assistant" date: 2017-05-04 00:00 sidebar: true comments: false @@ -15,12 +15,10 @@ ha_release: 0.47 This `radarr` sensor platform pulls data from a given [Radarr](https://radarr.video/) instance. -## {% linkable_title Configuration %} - To use your Radarr sensor in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry sensor: - platform: radarr api_key: YOUR_API_KEY diff --git a/source/_components/sensor.random.markdown b/source/_components/sensor.random.markdown index cbe6049cf3..d550d4b88d 100644 --- a/source/_components/sensor.random.markdown +++ b/source/_components/sensor.random.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Random Sensor" -description: "Instructions on how to integrate random number sensors into Home Assistant." +description: "Instructions how to integrate random number sensors into Home Assistant." date: 2016-10-30 12:10 sidebar: true comments: false @@ -14,9 +14,7 @@ ha_release: 0.32 --- -The `random` sensor platform is creating random sensor values (integers) out of a given range. Returned values form a [discrete uniform distribution](https://en.wikipedia.org/wiki/Discrete_uniform_distribution), meaning that each integer value in the range configured is equally likely to be drawn. This can be useful if you want to test automation rules. It generates a new value every time it is polled. - -## {% linkable_title Configuration %} +The `random` sensor platform is creating random sensor values (integers) out of a given range. This can be useful if you want to test automation rules. It generates a new value every time it is polled. To enable the random sensor, add the following lines to your `configuration.yaml`: @@ -50,4 +48,4 @@ unit_of_measurement: See the [entity component options][entity-docs] to control how often the main component polls the random sensor. The default is 30 seconds. -[entity-docs]: /docs/configuration/platform_options/ +[entity-docs]: https://home-assistant.io/docs/configuration/platform_options/ diff --git a/source/_components/sensor.rest.markdown b/source/_components/sensor.rest.markdown index 0c0cc9a7ab..7d8c751313 100644 --- a/source/_components/sensor.rest.markdown +++ b/source/_components/sensor.rest.markdown @@ -1,7 +1,7 @@ --- layout: page title: "RESTful Sensor" -description: "Instructions on how to integrate REST sensors into Home Assistant." +description: "Instructions how to integrate REST sensors into Home Assistant." date: 2015-09-14 19:10 sidebar: true comments: false @@ -151,7 +151,7 @@ sensor: unit_of_measurement: "°C" ``` -### {% linkable_title Accessing an HTTP authentication protected endpoint %} +### {% linkable_title Accessing a HTTP authentication protected endpoint %} The REST sensor supports HTTP authentication and customized headers. diff --git a/source/_components/sensor.rflink.markdown b/source/_components/sensor.rflink.markdown index 7efee12d68..38b529af80 100644 --- a/source/_components/sensor.rflink.markdown +++ b/source/_components/sensor.rflink.markdown @@ -1,7 +1,7 @@ --- layout: page title: "RFLink Sensor" -description: "Instructions on how to integrate RFLink sensors into Home Assistant." +description: "Instructions how to integrate RFLink sensors into Home Assistant." date: 2016-01-04 sidebar: true comments: false diff --git a/source/_components/sensor.rfxtrx.markdown b/source/_components/sensor.rfxtrx.markdown index 91a2dd5cf1..9df49ee684 100644 --- a/source/_components/sensor.rfxtrx.markdown +++ b/source/_components/sensor.rfxtrx.markdown @@ -1,7 +1,7 @@ --- layout: page title: "RFXtrx Sensor" -description: "Instructions on how to integrate RFXtrx sensors into Home Assistant." +description: "Instructions how to integrate RFXtrx sensors into Home Assistant." date: 2015-08-06 17:15 sidebar: true comments: false diff --git a/source/_components/sensor.ripple.markdown b/source/_components/sensor.ripple.markdown index 2eda541505..ad960c30e5 100644 --- a/source/_components/sensor.ripple.markdown +++ b/source/_components/sensor.ripple.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Ripple" -description: "Instructions on how to integrate ripple.com data within Home Assistant." +description: "Instructions how to integrate ripple.com data within Home Assistant." date: 2017-06-06 16:20 sidebar: true comments: false diff --git a/source/_components/sensor.sabnzbd.markdown b/source/_components/sensor.sabnzbd.markdown index 27766435fd..47680c4e1a 100644 --- a/source/_components/sensor.sabnzbd.markdown +++ b/source/_components/sensor.sabnzbd.markdown @@ -1,7 +1,7 @@ --- layout: page title: "SABnzbd" -description: "Instructions on how to integrate SABnzbd within Home Assistant." +description: "Instructions how to integrate SABnzbd within Home Assistant." date: 2015-03-23 19:59 sidebar: true comments: false @@ -68,7 +68,7 @@ Note that this will create the following sensors: - sensor.sabnzbd_left - sensor.sabnzbd_disk - sensor.sabnzbd_disk_free - - sensor.sabnzbd_queue_count + - sensor.sabnzdb_queue_count ``` As always, you can determine the names of sensors by looking at the dev-state page `< >` in the web interface. diff --git a/source/_components/sensor.scrape.markdown b/source/_components/sensor.scrape.markdown index 047dd0e956..06d1cd8042 100644 --- a/source/_components/sensor.scrape.markdown +++ b/source/_components/sensor.scrape.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Scrape Sensor" -description: "Instructions on how to integrate Web scrape sensors into Home Assistant." +description: "Instructions how to integrate Web scrape sensors into Home Assistant." date: 2016-10-12 09:10 sidebar: true comments: false @@ -22,7 +22,7 @@ To enable this sensor, add the following lines to your `configuration.yaml` file # Example configuration.yaml entry sensor: - platform: scrape - resource: https://www.home-assistant.io + resource: https://home-assistant.io select: ".current-version h1" ``` @@ -43,14 +43,14 @@ In this section you find some real life examples of how to use this sensor. Ther ### {% linkable_title Home Assistant %} -The current release Home Assistant is published on [https://www.home-assistant.io/](/) +The current release Home Assistant is published on [https://home-assistant.io/](https://home-assistant.io/) {% raw %} ```yaml sensor: # Example configuration.yaml entry - platform: scrape - resource: https://www.home-assistant.io + resource: https://home-assistant.io name: Release select: ".current-version h1" value_template: '{{ value.split(":")[1] }}' @@ -66,7 +66,7 @@ Get the counter for all our implementations from the [Component overview](/compo # Example configuration.yaml entry sensor: - platform: scrape - resource: https://www.home-assistant.io/components/ + resource: https://home-assistant.io/components/ name: Home Assistant impl. select: 'a[href="#all"]' value_template: '{{ value.split("(")[1].split(")")[0] }}' @@ -126,7 +126,7 @@ sensor: resource: https://elen.nu/timpriser-pa-el-for-elomrade-se3-stockholm/ name: Electricity price select: ".elspot-content" - value_template: '{{ ((value.split(" ")[0]) | replace (",", ".")) }}' + value_template: '{{ value.split(" ")[0] }}' unit_of_measurement: "öre/kWh" ``` {% endraw %} diff --git a/source/_components/sensor.season.markdown b/source/_components/sensor.season.markdown index 875636fb7c..6297420cd1 100644 --- a/source/_components/sensor.season.markdown +++ b/source/_components/sensor.season.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Season Sensor" -description: "Instructions on how to add season sensors into Home Assistant." +description: "Instructions how to add season sensors into Home Assistant." date: 2017-07-04 07:00:00 sidebar: true comments: false diff --git a/source/_components/sensor.sense.markdown b/source/_components/sensor.sense.markdown deleted file mode 100644 index e13e45dd93..0000000000 --- a/source/_components/sensor.sense.markdown +++ /dev/null @@ -1,74 +0,0 @@ ---- -layout: page -title: Sense -description: "Instructions on how to integrate Sense within Home Assistant." -date: 2018-01-11 13:50 -sidebar: true -comments: false -sharing: true -footer: true -logo: sense.png -ha_category: Energy -ha_iot_class: "Cloud Polling" -ha_release: 0.65 ---- - - -Integrate your [Sense](https://sense.com) meter information into Home Assistant. -To enable this sensor in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -sensor: - platform: sense - email: CLIENT_ID - password: CLIENT_SECRET - monitored_conditions: - - active_usage - - active_production - - daily_usage - - daily_production -``` - -Two types of sensors can be monitored and will be created with the following names: -- **Active Usage/Production**: Current active power usage/production in Watts. Updated every 30 seconds. -- **Daily Usage/Production**: Daily power usage/production in kWh. Updated every 5 minutes. -- ... - -Weekly, Monthly and Yearly variants are also available. - -{% configuration %} -email: - description: The email associated with your Sense account/application. - required: true - type: string -password: - description: The password for your Sense account/application. - required: true - type: string -monitored_conditions: - description: List of sensors to display in the front end. - required: true - type: list - keys: - active_usage: - description: The current power usage in W - active_production: - description: The current solar production in W - daily_usage: - description: Total power used for current day in kWh - daily_production: - description: Total power produced for current day in kWh - weekly_usage: - description: Total power used for current week in kWh - weekly_production: - description: Total power produced for current week in kWh - monthly_usage: - description: Total power used for current month in kWh - monthly_production: - description: Total power produced for current month in kWh - yearly_usage: - description: Total power used for current year in kWh - yearly_production: - description: Total power produced for current year in kWh -{% endconfiguration %} diff --git a/source/_components/sensor.sensehat.markdown b/source/_components/sensor.sensehat.markdown index fb3447acd5..ae270f052f 100644 --- a/source/_components/sensor.sensehat.markdown +++ b/source/_components/sensor.sensehat.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Sense HAT" -description: "Instructions on how to integrate Sense HAT within Home Assistant." +description: "Instructions how to integrate Sense HAT within Home Assistant." date: 2017-06-03 04:00 sidebar: true comments: false @@ -35,7 +35,7 @@ Configuration variables: - 'humidity' - 'pressure' is_hat_attached (Optional): True|False boolean; Default value is True declaring that the SenseHAT _is_ physically on the Raspberry Pi - + #### Customizing the Sense HAT data @@ -145,10 +145,10 @@ These issues have been discussed in the repository issue (#5093)[https://github. This fix has been tested with a clean install of: -* [Raspbian Jessie - version January 2017](https://downloads.raspberrypi.org/raspbian/images/raspbian-2017-01-10/) - +* [Raspbian Jessie - version January 2017](https://downloads.raspberrypi.org/raspbian/images/raspbian-2017-01-10/) + and - -* [Home-Assistant 0.37.1](/getting-started/installation-raspberry-pi-all-in-one/) + +* [Home-Assistant 0.37.1](https://home-assistant.io/getting-started/installation-raspberry-pi-all-in-one/) For setting up the Sense HAT's RGB LED matrix as lights within Home Assistant, please see the [Sense HAT light component](/components/light.sensehat/). diff --git a/source/_components/sensor.serial.markdown b/source/_components/sensor.serial.markdown index 356ced350f..ea1ad91a0b 100644 --- a/source/_components/sensor.serial.markdown +++ b/source/_components/sensor.serial.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Serial Sensor" -description: "Instructions on how to integrate data from serial connected sensors into Home Assistant." +description: "Instructions how to integrate data from serial connected sensors into Home Assistant." date: 2017-10-13 07:00 sidebar: true comments: false diff --git a/source/_components/sensor.shodan.markdown b/source/_components/sensor.shodan.markdown index 6a98ad3042..e4ca7947a2 100644 --- a/source/_components/sensor.shodan.markdown +++ b/source/_components/sensor.shodan.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Shodan Sensor" -description: "Instructions on how to integrate Shodan sensors into Home Assistant." +description: "Instructions how to integrate Shodan sensors into Home Assistant." date: 2017-08-09 10:30 sidebar: true comments: false diff --git a/source/_components/sensor.sht31.markdown b/source/_components/sensor.sht31.markdown deleted file mode 100644 index 7adbfc2cee..0000000000 --- a/source/_components/sensor.sht31.markdown +++ /dev/null @@ -1,54 +0,0 @@ ---- -layout: page -title: "Sensirion SHT31 Sensor" -description: "Instructions on how to integrate SHT31 sensors within Home Assistant." -date: 2018-03-06 19:15 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: DIY -ha_release: 0.68 -logo: sensirion.png -ha_iot_class: "Local Polling" ---- - -The `sht31` sensor platform allows you to get the current temperature and humidity from a Sensirion SHT31 device. - -## {% linkable_title Configuration %} - -To use your SHT31 sensor in your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -sensor: - platform: sht31 - name: Bedroom - i2c_address: 0x44 - monitored_conditions: - - temperature - - humidity -``` - -{% configuration %} - name: - description: The name of the sensor. Temperature and Humidity will be added to the name for the sensor name. - required: false - default: SHT31 - type: string - i2c_address: - description: I2C address of the sensor. - required: false - default: "`0x44`" - type: int - monitored_conditions: - description: Conditions to monitor. - required: false - default: All conditions - type: list - keys: - temperature: - description: The current temperature of the SHT31. - humidity: - description: The current humidity of the SHT31. -{% endconfiguration %} diff --git a/source/_components/sensor.sigfox.markdown b/source/_components/sensor.sigfox.markdown deleted file mode 100644 index f3f0bbb0ea..0000000000 --- a/source/_components/sensor.sigfox.markdown +++ /dev/null @@ -1,47 +0,0 @@ ---- -layout: page -title: "Sigfox Sensor" -description: "Display messages from Sigfox devices in Home Assistant." -date: 2018-04-07 12:10 -sidebar: true -comments: false -sharing: true -footer: true -logo: sigfox.png -ha_category: Sensor -ha_iot_class: "Local Polling" -ha_release: 0.68 ---- - -[SigFox](https://www.sigfox.com/en) component adding a sensor for each Sigfox device registered with your account. The default name of sensors is `sigfox_{DEVICE_ID}` where `DEVICE_ID` is the devices Sigfox ID. The state of an added Sigfox sensor is the payload of the last message published by that device. Additionally, there are attributes for the latitude and longitude coordinates of the device, as well as the signal-to-noise ratio ( [snr](https://en.wikipedia.org/wiki/Signal-to-noise_ratio)). - -```yaml -# Example configuration.yaml entry -sensor: - - platform: sigfox - api_login: your_api_login - api_password: your_api_password -``` - -{% configuration %} -api_login: - description: Your Sigfox API login. - required: true - type: string -api_password: - description: Your Sigfox API password. - required: true - type: string -name: - description: The name to prepend to the device ID. - required: false - default: "sigfox" - type: string -{% endconfiguration %} - -Note that `your_api_login` and `your_api_password` are your **API access credentials** which can be accessed by following: - -1. Log into [Sigfox backend](https://backend.sigfox.com) -1. Select `GROUP` -1. Select `API ACCESS` -1. Click on `new` and create new access entry diff --git a/source/_components/sensor.simulated.markdown b/source/_components/sensor.simulated.markdown deleted file mode 100644 index 4667b9ff39..0000000000 --- a/source/_components/sensor.simulated.markdown +++ /dev/null @@ -1,94 +0,0 @@ ---- -layout: page -title: "Simulated sensor" -description: "Component for simulating a numerical sensor." -date: 2018-02-20 08:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: home-assistant.png -ha_category: Sensor -ha_iot_class: "Local Polling" -ha_release: 0.65 ---- - -This component provides a simulated sensor that generates a time-varying signal ```V(t)``` given by the [function](https://en.wikipedia.org/wiki/Sine_wave): - - ``` - V(t) = M + A sin((2 pi (t - t_0) / w) + P) + N(s) - ``` - -where: - -- **M** = the [mean](https://en.wikipedia.org/wiki/Mean) value of the sensor -- **A** = the [amplitude](https://en.wikipedia.org/wiki/Amplitude) of the periodic contribution -- **t** = the time when a value is generated -- **t_0** = the time when the sensor is started -- **w** = the time [period](https://en.wikipedia.org/wiki/Periodic_function) in seconds for a single complete cycle of the periodic contribution -- **P** = the [phase](https://en.wikipedia.org/wiki/Phase_(waves)) offset to add to the periodic contribution, in units of degrees -- **N(s)** = the random [Gaussian noise](https://en.wikipedia.org/wiki/Gaussian_noise) with spread **s** - -A simulated sensor with default values can be added to home-assistant using the following config: - -```yaml -sensor: - - platform: simulated -``` - -To give an example of simulating real world data, a simulated relative humidity sensor (in %) can be added using the following config: - -```yaml -sensor: - - platform: simulated - name: 'simulated relative humidity' - unit: '%' - amplitude: 0 # Turns off the periodic contribution - mean: 50 - spread: 10 - seed: 999 -``` - -Configuration variables: -{% configuration %} -name: - description: The name of the sensor - required: false - default: Defaults to 'simulated' - type: string -unit: - description: The unit to apply - required: false - default: Defaults to 'value' - type: string -amplitude: - description: The amplitude of periodic contribution - required: false - default: 1 - type: float -mean: - description: The mean level of the sensor - required: false - default: 0 - type: float -period: - description: The time in seconds for one complete oscillation of the periodic contribution - required: false - default: 0 - type: seconds -phase: - description: The phase offset (in degrees) to apply to the periodic component - required: false - default: 0 - type: float -seed: - description: The [seed](https://docs.python.org/3.6/library/random.html#random.seed) value for the random noise component - required: false - default: 999 - type: int -spread: - description: The spread is the range of the randomly distributed values about their mean. This is sometimes referred to as the Full Width at Half Maximum ([FWHM](https://en.wikipedia.org/wiki/Full_width_at_half_maximum)) of the random distribution - required: false - default: None - type: float -{% endconfiguration %} diff --git a/source/_components/sensor.sma.markdown b/source/_components/sensor.sma.markdown index f3eb166564..b2c9bfdcd1 100644 --- a/source/_components/sensor.sma.markdown +++ b/source/_components/sensor.sma.markdown @@ -16,16 +16,14 @@ ha_release: 0.36 The `sma` sensor will poll a [SMA](http://www.sma-solar.com/) [(US)](http://www.sma-america.com/) solar inverter and present the values as sensors (or attributes of sensors) in Home Assistant. -## {% linkable_title Configuration %} - To enable this sensor, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry sensor sma: - platform: sma - host: IP_ADDRESS_OF_DEVICE - password: YOUR_SMA_PASSWORD + host: 192.168.88.199 + password: !secret sma_password sensors: current_consumption: [total_consumption] current_power: diff --git a/source/_components/sensor.smappee.markdown b/source/_components/sensor.smappee.markdown deleted file mode 100644 index 2886f2b434..0000000000 --- a/source/_components/sensor.smappee.markdown +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: page -title: "Smappee Sensor" -description: "Instructions on how to integrate Smappee energy monitor into Home Assistant." -date: 2018-02-26 08:37 -sidebar: true -comments: false -sharing: true -footer: true -logo: smappee.png -ha_release: "0.64" -ha_category: Sensor ---- - -[Smappee](https://www.smappee.com/) controller for energy monitoring and Comport plug switches. - -Energy monitor measurements will be automatically added when you connect to the Smappee controller. - -For more configuration information see the [Smappee component](/components/smappee/) documentation. diff --git a/source/_components/sensor.snmp.markdown b/source/_components/sensor.snmp.markdown index f492d5ef3a..95429545db 100644 --- a/source/_components/sensor.snmp.markdown +++ b/source/_components/sensor.snmp.markdown @@ -1,7 +1,7 @@ --- layout: page title: "SNMP" -description: "Instructions on how to integrate SNMP sensors within Home Assistant." +description: "Instructions how to integrate SNMP sensors within Home Assistant." date: 2016-06-05 20:00 sidebar: true comments: false diff --git a/source/_components/sensor.sochain.markdown b/source/_components/sensor.sochain.markdown index 26ff8d5fd1..77bf1c7836 100644 --- a/source/_components/sensor.sochain.markdown +++ b/source/_components/sensor.sochain.markdown @@ -1,7 +1,7 @@ --- layout: page title: "SoChain" -description: "Instructions on how to integrate chain.so data within Home Assistant." +description: "Instructions how to integrate chain.so data within Home Assistant." date: 2017-06-01 16:20 sidebar: true comments: false diff --git a/source/_components/sensor.socialblade.markdown b/source/_components/sensor.socialblade.markdown deleted file mode 100644 index cf106c9133..0000000000 --- a/source/_components/sensor.socialblade.markdown +++ /dev/null @@ -1,37 +0,0 @@ ---- -layout: page -title: Social Blade Sensor -description: "Instructions on how to set up Social Blade Sensor within Home Assistant." -date: 2018-04-23 08:00 -sidebar: false -comments: false -sharing: true -footer: true -logo: socialblade.png -ha_category: Sensor -ha_release: 0.69 -ha_iot_class: "Cloud Polling" ---- - -The `socialblade` sensor component allows you get updates on a youtube channel using your social blade channel id. The sensor gets the subscribers and total views count from [Social Blade Website]( https://socialblade.com/) - -to get the channel id you can go to [Social Blade Website]( https://socialblade.com/) and search for youtube channel by username, then select the channel and grab the id from the url. -The channel id will be the last part of the url : -https://socialblade.com/youtube/channel/{channel_id} - -## Example for `configuration.yaml` : - -```yaml -sensor: - - platform: socialblade - channel_id: YOUR_CHANNEL_NUMBER -``` - -{% configuration %} -channel_id: - description: channel id number optained from the URL when you access Social Blade web client. - required: true - type: string -{% endconfiguration %} - -All the data will be fetch from [Social Blade]( https://socialblade.com/). diff --git a/source/_components/sensor.sonarr.markdown b/source/_components/sensor.sonarr.markdown index 13a4944fea..5f4d437c02 100644 --- a/source/_components/sensor.sonarr.markdown +++ b/source/_components/sensor.sonarr.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Sonarr Sensor" -description: "Instructions on how to integrate Sonarr sensors with Home Assistant" +description: "Instructions how to integrate Sonarr sensors with Home Assistant" date: 2016-11-19 13:35 sidebar: true comments: false @@ -16,12 +16,10 @@ ha_iot_class: "Local Polling" This `sonarr` sensor platform pulls data from a given [Sonarr](https://sonarr.tv/) instance. -## {% linkable_title Configuration %} - To use your Sonarr sensor in your installation, add the following to your `configuration.yaml` file: ```yaml -# Example configuration.yaml entry +# Example configuration.yml entry sensor: - platform: sonarr api_key: YOUR_API_KEY diff --git a/source/_components/sensor.speedtest.markdown b/source/_components/sensor.speedtest.markdown index fb95a0cdff..bc1e8bf988 100644 --- a/source/_components/sensor.speedtest.markdown +++ b/source/_components/sensor.speedtest.markdown @@ -16,9 +16,7 @@ ha_iot_class: "Cloud Polling" The `speedtest` sensor component uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance. -## {% linkable_title Configuration %} - -By default, it will run every hour. The user can change the update frequency in the configuration by defining the minute, hour, and day for a speed test to run. For the `server_id` check the list of [available servers](https://www.speedtest.net/speedtest-servers.php). +By default, it will run every hour. The user can change the update frequency in the configuration by defining the minute, hour, and day for a speedtest to run. For the `server_id` check the list of [available servers](https://www.speedtest.net/speedtest-servers.php). To add a Speedtest.net sensor to your installation, add the following to your `configuration.yaml` file: @@ -34,54 +32,26 @@ sensor: - upload ``` -{% configuration %} - monitored_conditions: - description: Sensors to display in the frontend. - required: true - type: list - keys: - ping: - description: Reaction time in ms of your connection (how fast you get a response after you've sent out a request). - download: - description: Download speed (Mbit/s) - upload: - description: Upload speed (Mbit/s) - server_id: - description: Specify the speed test server to perform the test against. - required: false - type: int - day: - description: Specify the day(s) of the month to schedule the speed test. Use a list for multiple entries. - required: false - type: [int, list] - hour: - description: Specify the hour(s) of the day to schedule the speed test. Use a list for multiple entries. - required: false - type: [int, list] - minute: - description: Specify the minute(s) of the hour to schedule the speed test. Use a list for multiple entries. - required: false - type: [int, list] - default: 0 - second: - description: Specify the second(s) of the minute to schedule the speed test. Use a list for multiple entries. - required: false - type: [int, list] - default: 0 - manual: - description: True or False to turn manual mode on or off. Manual mode will disable scheduled speed tests. - required: false - type: bool - default: false -{% endconfiguration %} +Configuration variables: + +- **monitored_conditions** array (*Required*): Sensors to display in the frontend. + - **ping**: Reaction time in ms of your connection (how fast you get a response after you've sent out a request). + - **download**: Download speed in Mbps. + - **upload**: Upload speed in Mbps. +- **server_id** (*Optional*): Specify the speedtest server to perform test against. +- **minute** (*Optional*): Specify the minute(s) of the hour to schedule the speedtest. Use a list for multiple entries. Default is 0. +- **hour** (*Optional*): Specify the hour(s) of the day to schedule the speedtest. Use a list for multiple entries. Default is None. +- **day** (*Optional*): Specify the day(s) of the month to schedule the speedtest. Use a list for multiple entries. Default is None. +- **manual** (*Optional*): True or False to turn manual mode on or off. Manual mode will disable scheduled speedtests. This component uses [speedtest-cli](https://github.com/sivel/speedtest-cli) to gather network performance data from Speedtest.net. Please be aware of the potential [inconsistencies](https://github.com/sivel/speedtest-cli#inconsistency) that this component may display. -When Home Assistant first starts up, the values of the speed test will show as `Unknown`. You can use the service `sensor.update_speedtest` to run a manual speed test and populate the data or just wait for the next regularly scheduled test. You can turn on manual mode to disable the scheduled speed tests. +When Home Assistant first starts up, the values of the speedtest will show as `Unknown`. You can use the service `sensor.update_speedtest` to run a manual speedtest and populate the data or just wait for the next regularly scheduled test. You can turn on manual mode to disable the scheduled speedtests. + ## {% linkable_title Examples %} -In this section, you find some real-life examples of how to use this sensor. +In this section you find some real life examples of how to use this sensor. ### {% linkable_title Run periodically %} @@ -122,30 +92,26 @@ sensor: ### {% linkable_title Using as a trigger in an automation %} -{% raw %} ```yaml # Example configuration.yaml entry automation: - - alias: "Internet Speed Glow Connect Great" - trigger: - - platform: template - value_template: "{{ states('sensor.speedtest_download')|float > 10 }}" - action: - - service: shell_command.green - - - alias: "Internet Speed Glow Connect Poor" - trigger: - - platform: template - value_template: "{{ states('sensor.speedtest_download')|float < 10 }}" - action: - - service: shell_command.red + - alias: 'Internet Speed Glow Connect Great' + trigger: + platform: template + value_template: '{% raw %}{{ states.sensor.speedtest_download.state|float > 10}}{% endraw %}' + action: + service: shell_command.green + - alias: 'Internet Speed Glow Connect Poor' + trigger: + platform: template + value_template: '{% raw %}{{ states.sensor.speedtest_download.state| float < 10 }}{% endraw %}' + action: + service: shell_command.red ``` -{% endraw %} ## {% linkable_title Notes %} - When running on Raspberry Pi, just note that the maximum speed is limited by its 100 Mbit/s LAN adapter. -- Running this platform can have negative effects on the system's performance as it requires a fair amount of memory. -- Entries under `monitored_conditions` only control what entities are available in Home Assistant, it does not disable the condition from running. -- If ran frequently, this component has the ability to use a considerable amount of data. Frequent updates should be avoided on bandwidth-capped connections. -- While running, your network capacity is fully utilized. This may have a negative effect on other devices in use the network such as gaming consoles or streaming boxes. +- Entries under `monitored_conditions` only control what entities are available under home-assistant, it does not disable the condition from running. +- If ran frequently, this component has the capability of using a very large amount of data. Frequent updates should be avoided on bandwidth capped connections. +- While running, network usage is fully utilized. This may have a negative affect on other devices in use the network such as gaming consoles or streaming boxes. diff --git a/source/_components/sensor.spotcrime.markdown b/source/_components/sensor.spotcrime.markdown deleted file mode 100644 index b36d01b4b4..0000000000 --- a/source/_components/sensor.spotcrime.markdown +++ /dev/null @@ -1,76 +0,0 @@ ---- -layout: page -title: "Spot Crime" -description: "Instructions on how to integrate spotcrime.com into Home Assistant." -date: 2018-02-16 9:30 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Sensor -ha_release: 0.65 -ha_iot_class: "Cloud Polling" ---- - -The `spotcrime` sensor allows one to track reported incidents occurring in a given area. Incidents include anything reported to [Spot Crime](http://spotcrime.com). Your regional emergency services may or may not report data. The sensor defaults to counting incidents within one day, but can be customized via configuration.yaml. - -You will need to request an API key from [Spotcrime](mailto:pyrrhus@spotcrime.com). - -To enable this sensor, add the following lines to your `configuration.yaml`. Your `radius` should be of sufficient size to capture incidents in your area. 0.01 = 1 mile. - -```yaml -sensor: - - platform: spotcrime - name:
- 
-
-To get AVM Fritzbox switch follow the instructions for the general [Fritzbox](/components/fritzbox/). -
- -### {% linkable_title Attributes %} - -The are several attributes that can be useful for automations and templates. - -| Attribute | Description | -| --------- | ----------- | -| `device_locked` | The state of the key lock at the device. -| `locked` | The state of the lock for configuring the device via the app or the Fritzbox web interface. -| `temperature_unit` | The unit of the temperature sensor (only available if the device support temperature sensor). -| `temperature` | The current temperature sensor reading (only available if the device supports temperature sensor). -| `total_consumption` | The total power consumption since the beginning of operation (only available if the device supports power meter function). -| `total_consumption_unit` | The unit of the total_consumption (only available if the device supports power meter function). diff --git a/source/_components/switch.fritzdect.markdown b/source/_components/switch.fritzdect.markdown index 380deebdaf..b0d3b2ee3c 100644 --- a/source/_components/switch.fritzdect.markdown +++ b/source/_components/switch.fritzdect.markdown @@ -1,7 +1,7 @@ --- layout: page title: "AVM FRITZ!DECT Switch" -description: "Instructions on how to integrate your AVM FRITZ!DECT switches into Home Assistant." +description: "Instructions how to integrate your AVM FRITZ!DECT switches into Home Assistant." date: 2017-01-24 21:00 sidebar: true comments: false @@ -23,7 +23,7 @@ Supported devices (tested): Supported Firmwares (tested): - FRITZ!OS: 06.80 / FRITZ!DECT: 03.83 -- FRITZ!OS: 06.98-51288 (Beta) / FRITZ!DECT: 03.87 +- FRITZ!OS: 06.60 / FRITZ!DECT: 03.83 To use your AVM FRITZ!DECT switch(es) in your installation, add the following to your `configuration.yaml` file: @@ -35,23 +35,12 @@ switch: password: YOUR_PASSWORD ``` -{% configuration %} -username: - description: The username for your Fritz!Box. - required: true - type: string -password: - description: The password for your Fritz!Box. - required: true - type: string -host: - description: The IP address/hostname of your Fritz!Box. - required: false - type: string - default: fritz.box -{% endconfiguration %} +Configuration variables: + +- **username** (*Required*): The username for your Fritz!Box. +- **password** (*Required*): The password for your Fritz!Box. +- **host** (*Optional*): The IP address/hostname of your Fritz!Box. Defaults to `fritz.box`. -It is recommended to create a dedicated user for Home Assistant and only allow access to "Smart Home".If this component throws an error when starting home-assistant you should check if all actors are plugged in and connected to the FritzBox. Inactive actors that are not deleted from FritzBox configuration might lead to errors. diff --git a/source/_components/switch.hikvisioncam.markdown b/source/_components/switch.hikvisioncam.markdown index 64fc873989..85249cd681 100644 --- a/source/_components/switch.hikvisioncam.markdown +++ b/source/_components/switch.hikvisioncam.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Hikvision Camera Switch" -description: "Instructions on how to integrate Hikvision camera switches into Home Assistant." +description: "Instructions how to integrate Hikvision camera switches into Home Assistant." date: 2015-06-10 22:54 sidebar: true comments: false diff --git a/source/_components/switch.hive.markdown b/source/_components/switch.hive.markdown index e4ea483797..8f7d867722 100644 --- a/source/_components/switch.hive.markdown +++ b/source/_components/switch.hive.markdown @@ -14,11 +14,10 @@ ha_iot_class: "Cloud Polling" --- -The `hive` switch platform integrates your Hive plugs into Home Assistant, enabling control of your devices. +The 'hive' switch component integrates your Hive plugs into Home Assistant, enabling control of your devices. -The platform supports the following Hive products: - -- Hive Active Plug +The Hive switch component supports the following Hive products: +- **Hive Active Plug**
diff --git a/source/_components/switch.homekit_controller.markdown b/source/_components/switch.homekit_controller.markdown
deleted file mode 100644
index 43bf3be57b..0000000000
--- a/source/_components/switch.homekit_controller.markdown
+++ /dev/null
@@ -1,16 +0,0 @@
----
-layout: page
-title: "HomeKit Switch"
-description: "Instructions on how to setup HomeKit switches within Home Assistant."
-date: 2017-03-19 21:08
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: apple-homekit.png
-ha_category: Light
-ha_iot_class: "Local Polling"
-ha_release: 0.68
----
-
-To get your HomeKit switches working with Home Assistant, follow the instructions for the general [HomeKit controller component](/components/homekit_controller/).
diff --git a/source/_components/switch.homematic.markdown b/source/_components/switch.homematic.markdown
index 7902ae4974..3e3fd7e878 100644
--- a/source/_components/switch.homematic.markdown
+++ b/source/_components/switch.homematic.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Homematic Switch"
-description: "Instructions on how to integrate Homematic switches within Home Assistant."
+description: "Instructions how to integrate Homematic switches within Home Assistant."
date: 2016-06-28 08:30
sidebar: true
comments: false
diff --git a/source/_components/switch.hook.markdown b/source/_components/switch.hook.markdown
index fbfeef75b4..3ba23b8c19 100644
--- a/source/_components/switch.hook.markdown
+++ b/source/_components/switch.hook.markdown
@@ -20,44 +20,23 @@ In short, Hook is an RF to Wi-Fi bridge, controlling devices that receive comman
Hook provides a simple [REST API](https://app.swaggerhub.com/api/rahilj/GetHook_RestAPI/v1). This Home Assistant component reads in devices that have been set up in the official app.
-## {% linkable_title Configuration %}
-
Configure with either your username/password or your API token for the official app.
-To enable this platform in your installation, add the following to your `configuration.yaml` file:
-
```yaml
# Example configuration.yaml entry
switch:
- - platform: hook
- username: YOUR_E_MAIL_ADDRESS
- password: YOUR_HOOK
+ - platform: hook
+ username:
-You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/)
-configured to use this switch. After configuring that component, switches will
-automatically appear.
-
@@ -82,23 +78,21 @@ Make sure that the URL matches exactly your endpoint or resource.
### {% linkable_title Switch with templated value %}
-This example shows a switch that uses a [template](/topics/templating/) to allow Home Assistant to determine its state. In this example, the REST endpoint returns this JSON response with true indicating the switch is on.
+This example shows a switch that uses a [template](/topics/templating/) to allow Home Assistant to determine its state. In this example the REST endpoint returns this JSON response with true indicating the switch is on.
```json
{"is_active": "true"}
```
-{% raw %}
+
```yaml
switch:
- platform: rest
resource: http://IP_ADDRESS/led_endpoint
body_on: '{"active": "true"}'
body_off: '{"active": "false"}'
- is_on_template: '{{ value_json.is_active }}'
- headers:
- Content-Type: application/json
+ is_on_template: '{% raw %}{{value_json.is_active}}{% endraw %}'
```
-{% endraw %}
`body_on` and `body_off` can also depend on the state of the system. For example, to enable a remote temperature sensor tracking on a radio thermostat, one has to send the current value of the remote temperature sensor. This can be achieved by using the template `{% raw %}'{"rem_temp":{{states.sensor.bedroom_temp.state}}}'{% endraw %}`.
+
diff --git a/source/_components/switch.rflink.markdown b/source/_components/switch.rflink.markdown
index ee42e8bbd7..08b5e61458 100644
--- a/source/_components/switch.rflink.markdown
+++ b/source/_components/switch.rflink.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "RFLink Switch"
-description: "Instructions on how to integrate RFLink switches into Home Assistant."
+description: "Instructions how to integrate RFLink switches into Home Assistant."
date: 2016-01-04
sidebar: true
comments: false
diff --git a/source/_components/switch.rfxtrx.markdown b/source/_components/switch.rfxtrx.markdown
index 52b58ab4a6..434a4c4563 100644
--- a/source/_components/switch.rfxtrx.markdown
+++ b/source/_components/switch.rfxtrx.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "RFXtrx Switch"
-description: "Instructions on how to integrate RFXtrx switches into Home Assistant."
+description: "Instructions how to integrate RFXtrx switches into Home Assistant."
date: 2015-10-08 10:15
sidebar: true
comments: false
diff --git a/source/_components/switch.rpi_gpio.markdown b/source/_components/switch.rpi_gpio.markdown
index 5b3a888e24..192bb82544 100644
--- a/source/_components/switch.rpi_gpio.markdown
+++ b/source/_components/switch.rpi_gpio.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Raspberry Pi GPIO Switch"
-description: "Instructions on how to integrate the GPIO of a Raspberry Pi into Home Assistant as a switch."
+description: "Instructions how to integrate the GPIO of a Raspberry Pi into Home Assistant as a switch."
date: 2015-08-07 14:00
sidebar: true
comments: false
@@ -35,10 +35,6 @@ Configuration variables:
For more details about the GPIO layout, visit the Wikipedia [article](https://en.wikipedia.org/wiki/Raspberry_Pi#GPIO_connector) about the Raspberry Pi.
-
-Note that a pin managed by HASS is expected to be exclusive to HASS.
-
The WOL switch can only turn on your computer and monitor the state. There is no universal way to turn off a computer remotely. The `turn_off` variable is there to help you call a script when you have figured out how to remotely turn off your computer.
See below for suggestions on how to do this.
@@ -25,7 +23,7 @@ See below for suggestions on how to do this.
To enable this switch in your installation, add the following to your `configuration.yaml` file:
```yaml
-# Example configuration.yaml entry
+# Example configuration.yml entry
switch:
- platform: wake_on_lan
mac_address: "00-01-02-03-04-05"
@@ -44,8 +42,7 @@ Configuration variables:
Here are some real life examples of how to use the **turn_off** variable.
### {% linkable_title Suspending Linux %}
-
-Suggested recipe for letting the `turn_off` script suspend a Linux computer (the **target**)
+Suggested recipe for letting the turn_off script suspend a Linux computer (the **target**)
from Home Assistant running on another Linux computer (the **server**).
1. On the **server**, log in as the user account Home Assistant is running under. (I'm using `hass` in this example)
diff --git a/source/_components/switch.wemo.markdown b/source/_components/switch.wemo.markdown
index 6bca30af1a..7b6a4ae901 100644
--- a/source/_components/switch.wemo.markdown
+++ b/source/_components/switch.wemo.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Belkin WeMo Switch"
-description: "Instructions on how to integrate Belkin WeMo switches into Home Assistant."
+description: "Instructions how to integrate Belkin WeMo switches into Home Assistant."
date: 2016-02-20 00:47
sidebar: true
comments: false
diff --git a/source/_components/switch.wink.markdown b/source/_components/switch.wink.markdown
index 9a02607792..085aba3a38 100644
--- a/source/_components/switch.wink.markdown
+++ b/source/_components/switch.wink.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Wink Switch"
-description: "Instructions on how to setup the Wink switches within Home Assistant."
+description: "Instructions how to setup the Wink switches within Home Assistant."
date: 2015-01-20 22:36
sidebar: true
comments: false
diff --git a/source/_components/switch.xiaomi_aqara.markdown b/source/_components/switch.xiaomi_aqara.markdown
index 0306ba2921..f207229bee 100644
--- a/source/_components/switch.xiaomi_aqara.markdown
+++ b/source/_components/switch.xiaomi_aqara.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Xiaomi Switch"
-description: "Instructions on how to setup the Xiaomi switch within Home Assistant."
+description: "Instructions how to setup the Xiaomi switch within Home Assistant."
date: 2017-07-21 16:34
sidebar: true
comments: false
diff --git a/source/_components/switch.xiaomi_miio.markdown b/source/_components/switch.xiaomi_miio.markdown
index 6124437209..f8d03291d0 100644
--- a/source/_components/switch.xiaomi_miio.markdown
+++ b/source/_components/switch.xiaomi_miio.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Xiaomi Smart WiFi Socket and Smart Power Strip"
-description: "Instructions on how to integrate your Xiaomi Smart WiFi Socket aka Plug or Xiaomi Smart Power Strip within Home Assistant."
+description: "Instructions how to integrate your Xiaomi Smart WiFi Socket aka Plug or Xiaomi Smart Power Strip within Home Assistant."
date: 2017-08-26 10:18
sidebar: true
comments: false
@@ -13,38 +13,12 @@ ha_version: 0.56
ha_iot_class: "Local Polling"
---
-The `xiaomi_miio` switch platform allows you to control the state of your Xiaomi Smart WiFi Socket aka Plug, Xiaomi Smart Power Strip and Xiaomi Chuangmi Plug V1.
+The `xiaomi_miio` switch platform allows you to control the state of your Xiaomi Smart WiFi Socket aka Plug or Xiaomi Smart Power Strip.
+
+Currently, the supported features are `on`, `off`. If the device provides the current load, it will be reported.
Please follow the instructions on [Retrieving the Access Token](/components/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
-## Features
-
-### Xiaomi Smart WiFi Socket
-
-* Power (on, off)
-* Attributes
- - Temperature
-
-### Xiaomi Chuangmi Plug V1
-
-* Power (on, off)
-* USB (on, off)
-* Attributes
- - Temperature
-
-### Xiaomi Smart Power Strip
-
-* Power (on, off)
-* Wifi LED (on, off)
-* Power Price (0...999)
-* Power Mode (green, normal) (Power Strip V1 only)
-* Attributes
- - Temperature
- - Current
- - Load power
- - Wifi LED
- - Mode (Power Strip V1 only)
-
To add a plug to your installation, add the following to your `configuration.yaml` file:
```yaml
@@ -54,67 +28,9 @@ switch:
name: Original Xiaomi Mi Smart WiFi Socket
host: 192.168.130.59
token: YOUR_TOKEN
- model: chuangmi.plug.m1
```
Configuration variables:
-- **host** (*Required*): The IP of your miio device.
-- **token** (*Required*): The API token of your miio device.
-- **name** (*Optional*): The name of your miio device.
-- **model** (*Optional*): The model of your miio device. Valid values are `chuangmi.plug.v1`, `qmi.powerstrip.v1`, `zimi.powerstrip.v2`, `chuangmi.plug.m1` and `chuangmi.plug.v2`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available.
-
-{% configuration %}
-host:
- description: The IP address of your device.
- required: true
- type: string
-token:
- description: The API token of your device.
- required: true
- type: string
-name:
- description: The name of your device.
- required: false
- type: string
- default: Xiaomi Miio Switch
-model:
- description: The model of your device.
- required: false
- type: string
-{% endconfiguration %}
-
-## {% linkable_title Platform Services %}
-
-### {% linkable_title Service `switch.xiaomi_miio_set_wifi_led_on` %} (Power Strip only)
-
-Turn the wifi led on.
-
-| Service data attribute | Optional | Description |
-|---------------------------|----------|---------------------------------------------------------|
-| `entity_id` | yes | Only act on a specific xiaomi miio switch entity. Else targets all. |
-
-### {% linkable_title Service `switch.xiaomi_miio_set_wifi_led_off` %} (Power Strip only)
-
-Turn the wifi led off.
-
-| Service data attribute | Optional | Description |
-|---------------------------|----------|---------------------------------------------------------|
-| `entity_id` | yes | Only act on a specific xiaomi miio switch entity. Else targets all. |
-
-### {% linkable_title Service `switch.xiaomi_miio_set_power_price` %} (Power Strip)
-
-Set the power price.
-
-| Service data attribute | Optional | Description |
-|---------------------------|----------|---------------------------------------------------------|
-| `entity_id` | yes | Only act on a specific xiaomi miio switch entity. Else targets all. |
-| `price` | no | Power price, between 0 and 999. |
-
-### {% linkable_title Service `switch.xiaomi_miio_set_power_mode` %} (Power Strip V1 only)
-
-Set the power mode.
-
-| Service data attribute | Optional | Description |
-|---------------------------|----------|---------------------------------------------------------------|
-| `entity_id` | yes | Only act on a specific xiaomi miio switch entity. Else targets all. |
-| `mode` | no | Power mode, valid values are 'normal' and 'green' |
+- **host** (*Required*): The IP of your plug.
+- **token** (*Required*): The API token of your plug.
+- **name** (*Optional*): The name of your plug.
diff --git a/source/_components/switch.zwave.markdown b/source/_components/switch.zwave.markdown
index 9525daed35..2ae97b2180 100644
--- a/source/_components/switch.zwave.markdown
+++ b/source/_components/switch.zwave.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Z-Wave Switch"
-description: "Instructions on how to setup the Z-Wave switches within Home Assistant."
+description: "Instructions how to setup the Z-Wave switches within Home Assistant."
date: 2015-11-15 13:00
sidebar: true
comments: false
diff --git a/source/_components/system_log.markdown b/source/_components/system_log.markdown
index ef3ba0f5ed..fae6692223 100644
--- a/source/_components/system_log.markdown
+++ b/source/_components/system_log.markdown
@@ -12,7 +12,7 @@ ha_category: Other
ha_release: 0.58
---
-The `system_log` component stores information about all logged errors and warnings in Home Assistant. All collected information is accessible directly in the frontend, just navigate to the `Info` section under `Developer Tools`. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
+The `system_log` component stores information about all logged errors and warnings in Home Assistant. All collected information is accessible directly in the frontend, just navigate to the `Info` section under `Developer Tools`. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the amount of stored log entries using the parameter `max_entries`.
This component is automatically loaded by the `frontend` (so no need to do anything if you are using the frontend). If you are not doing so, or if you wish to change a parameter, add the following section to your `configuration.yaml` file:
@@ -35,66 +35,3 @@ max_entries:
To manually clear the system log, call this service.
-## {% linkable_title Events %}
-
-Errors and warnings are posted as the event `system_log_event`, so it is possible to write automations that trigger whenever a warning or error occurs. The following information is included in each event:
-
-| Field | Description |
-|------------------------------------------------------------------------------------------|
-| `level` | Either `WARNING` or `ERROR` depending on severity. |
-| `source` | File that triggered the error, e.g., `core.py` or `media_player/yamaha.py`. |
-| `exception` | Full stack trace if available, otherwise empty string. |
-| `message` | Descriptive message of the error, e.g., "Error handling request". |
-| `timestamp` | Unix timestamp with as a double, e.g., 1517241010.237416. |
-
-Live examples of these events can be found in the Home Assistant log file or by just looking in the system log. An example could, for instance, look like this:
-
-
-Depending on your setup, you might need to set a base URL (`base_url`) inside the [http component](/components/http/).
-
+If you are running Home Assistant over SSL or from within a container, you will have to setup a base URL (`base_url`) inside the [http component](/components/http/).
+
- If you are using a Raspberry Pi, you must use PhantomJS.
-
- Don't use apt-get to install PhantomJS. This version is not compatible.
-
diff --git a/source/_components/vacuum.dyson.markdown b/source/_components/vacuum.dyson.markdown
index b482899130..4ac3d49e5e 100644
--- a/source/_components/vacuum.dyson.markdown
+++ b/source/_components/vacuum.dyson.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Dyson 360 Eye"
-description: "Instructions on how to integrate your Dyson Eye 360 vacuum robot within Home Assistant."
+description: "Instructions how to integrate your Dyson Eye 360 vacuum robot within Home Assistant."
date: 2017-08-06 10:30
sidebar: true
comments: false
diff --git a/source/_components/vacuum.markdown b/source/_components/vacuum.markdown
index c626a39934..51b0adc667 100644
--- a/source/_components/vacuum.markdown
+++ b/source/_components/vacuum.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Vacuum cleaner robots"
-description: "Instructions on how to setup a botvac in Home Assistant."
+description: "Instructions how to setup a botvac in Home Assistant."
date: 2017-07-28 15:00
sidebar: true
comments: false
@@ -27,7 +27,7 @@ Available services: `turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_hom
Before calling one of these services, make sure your botvac platform supports it.
-#### {% linkable_title Service `vacuum.turn_on` %}
+#### {% linkable_title Service `vacuum/turn_on` %}
Start a new cleaning task.
@@ -35,7 +35,7 @@ Start a new cleaning task.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.turn_off` %}
+#### {% linkable_title Service `vacuum/turn_off` %}
Stop the current cleaning task and return to the dock.
@@ -43,7 +43,7 @@ Stop the current cleaning task and return to the dock.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.start_pause` %}
+#### {% linkable_title Service `vacuum/start_pause` %}
Start, pause or resume a cleaning task.
@@ -51,7 +51,7 @@ Start, pause or resume a cleaning task.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.stop` %}
+#### {% linkable_title Service `vacuum/stop` %}
Stop the current activity of the botvac.
@@ -59,7 +59,7 @@ Stop the current activity of the botvac.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.return_to_home` %}
+#### {% linkable_title Service `vacuum/return_to_home` %}
Tell the botvac to return home.
@@ -67,7 +67,7 @@ Tell the botvac to return home.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.locate` %}
+#### {% linkable_title Service `vacuum/locate` %}
Locate the vacuum cleaner robot.
@@ -75,7 +75,7 @@ Locate the vacuum cleaner robot.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.clean_spot` %}
+#### {% linkable_title Service `vacuum/clean_spot` %}
Tell the vacuum cleaner to do a spot clean-up.
@@ -83,7 +83,7 @@ Tell the vacuum cleaner to do a spot clean-up.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
-#### {% linkable_title Service `vacuum.set_fanspeed` %}
+#### {% linkable_title Service `vacuum/set_fanspeed` %}
Set the fan speed of the botvac. The `fanspeed` can be a label, as `balanced` or `turbo`, or be a number; it depends on the `vacuum` platform.
@@ -92,7 +92,7 @@ Set the fan speed of the botvac. The `fanspeed` can be a label, as `balanced` or
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
| `fanspeed` | no | Platform dependent vacuum cleaner fan speed, with speed steps, like 'medium', or by percentage, between 0 and 100. |
-#### {% linkable_title Service `vacuum.send_command` %}
+#### {% linkable_title Service `vacuum/send_command` %}
Send a platform-specific command to the vacuum cleaner.
diff --git a/source/_components/vacuum.mqtt.markdown b/source/_components/vacuum.mqtt.markdown
index 1777c7cd89..65ed9679ce 100644
--- a/source/_components/vacuum.mqtt.markdown
+++ b/source/_components/vacuum.mqtt.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "MQTT Vacuum"
-description: "Instructions on how to integrate your MQTT enabled Vacuum within Home Assistant."
+description: "Instructions how to integrate your MQTT enabled Vacuum within Home Assistant."
date: 2017-09-11 20:26
sidebar: true
comments: false
diff --git a/source/_components/vacuum.neato.markdown b/source/_components/vacuum.neato.markdown
index b670457369..2c0ed93464 100644
--- a/source/_components/vacuum.neato.markdown
+++ b/source/_components/vacuum.neato.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Neato Robotics Vacuum"
-description: "Instructions on how to integrate a Neato Botvac Connected Vacuum within Home Assistant."
+description: "Instructions how to integrate a Neato Botvac Connected Vacuum within Home Assistant."
date: 2017-10-18 16:11
sidebar: true
comments: false
diff --git a/source/_components/vacuum.roomba.markdown b/source/_components/vacuum.roomba.markdown
index bf28b11035..32c1393eb2 100644
--- a/source/_components/vacuum.roomba.markdown
+++ b/source/_components/vacuum.roomba.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "iRobot Roomba"
-description: "Instructions on how to integrate your Wi-Fi enabled Roomba within Home Assistant."
+description: "Instructions how to integrate your Wi-Fi enabled Roomba within Home Assistant."
date: 2017-08-04 20:43
sidebar: true
comments: false
diff --git a/source/_components/vacuum.xiaomi_miio.markdown b/source/_components/vacuum.xiaomi_miio.markdown
index 9fa8cbe3da..4abc27588c 100644
--- a/source/_components/vacuum.xiaomi_miio.markdown
+++ b/source/_components/vacuum.xiaomi_miio.markdown
@@ -13,7 +13,8 @@ ha_release: 0.51
ha_iot_class: "Local Polling"
---
-The `xiaomi miio` vacuum platform allows you to control the state of your [Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/).
+The `xiaomi miio` vacuum platform allows you to control the state of your
+[Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/).
Currently supported features are:
@@ -49,22 +50,26 @@ Configuration variables:
## {% linkable_title Platform Services %}
-In addition to all of the services provided by the `vacuum` component (`turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are:
+In addition to [all of the services provided by the `vacuum` component]
+]) (`turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`,
+`set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific
+services to access the remote control mode of the robot. These are:
- `xiaomi_remote_control_start`
- `xiaomi_remote_control_stop`
- `xiaomi_remote_control_move`
- `xiaomi_remote_control_move_step`
-### {% linkable_title Service `vacuum.xiaomi_remote_control_start` %}
+### {% linkable_title Service `vacuum/xiaomi_remote_control_start` %}
-Start the remote control mode of the robot. You can then move it with `remote_control_move`; when done, call `remote_control_stop`.
+Start the remote control mode of the robot. You can then move it with
+`remote_control_move`; when done, call `remote_control_stop`.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific robot; default targets all |
-### {% linkable_title Service `vacuum.xiaomi_remote_control_stop` %}
+### {% linkable_title Service `vacuum/xiaomi_remote_control_stop` %}
Exit the remote control mode of the robot.
@@ -72,18 +77,20 @@ Exit the remote control mode of the robot.
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific robot; default targets all |
-### {% linkable_title Service `vacuum.xiaomi_remote_control_move` %}
+### {% linkable_title Service `vacuum/xiaomi_remote_control_move` %}
-Remote control the robot. Please ensure you first set it in remote control mode with `remote_control_start`.
+Remote control the robot. Please ensure you first set it in remote control
+mode with `remote_control_start`.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific robot; default targets all |
| `velocity` | no | Speed: between -0.29 and 0.29 |
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
-| `duration` | no | The number of milliseconds that the robot should move for |
+| `duration` | no | The number of seconds that the robot should move for |
-### {% linkable_title Service `vacuum.xiaomi_remote_control_move_step` %}
+
+### {% linkable_title Service `vacuum/xiaomi_remote_control_move_step` %}
Enter remote control mode, make one move, stop, and exit remote control mode.
@@ -92,12 +99,13 @@ Enter remote control mode, make one move, stop, and exit remote control mode.
| `entity_id` | yes | Only act on specific robot; default targets all |
| `velocity` | no | Speed: between -0.29 and 0.29. |
| `rotation` | no | Rotation: between -179 degrees and 179 degrees. |
-| `duration` | no | The number of milliseconds that the robot should move for |
+| `duration` | no | The number of seconds that the robot should move for |
## {% linkable_title Attributes %}
-In addition to [all of the attributes provided by the `vacuum` component](/components/vacuum/#attributes),
-(`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, `status`, and `params`), the `xiaomi` platform introduces specific attributes. These are:
+In addition to [all of the attributes provided by the `vacuum` component](https://home-assistant.io/components/vacuum/#attributes),
+(`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, `status`, and
+`params`), the `xiaomi` platform introduces specific attributes. These are:
- `cleaning_time`
- `do_not_disturb`
@@ -125,45 +133,12 @@ The following table shows the units of measurement for each attribute:
## {% linkable_title Retrieving the Access Token %}
-As per [python-miio issue 185](https://github.com/rytilahti/python-miio/issues/185) the Mi-Home app no longer stores the token within the database (it's retrieved from Xiaomi servers from version 5.0.31+). Currently the only known fix is to uninstall, then install a downgraded version of the apk. Apkmirror is a trusted source for older versions of the app. [Mi-Home version 5.0.0](https://www.apkmirror.com/apk/xiaomi-inc/mihome/mihome-5-0-0-release/) is confirmed as working for the following Android methods.
-
-This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuum, Mi Robot 2 (Roborock) Vacuum, Xiaomi Philips Lights and Xiaomi IR Remote. The Xiaomi Gateway uses another security method and requires a `key` (16 alphanumeric chars), which can be obtained
-easily via a hidden menu item at the Mi-Home app or using the `miio` command line tool.
+This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot
+Vacuum and Xiaomi Philips Lights. The Xiaomi Gateway uses another security
+method and requires a `key` (16 alphanumeric chars), which can be obtained
+easily via a hidden menu item at the Mi-Home app.
-[Dark Sky](https://darksky.net/dev/) will charge you $0.0001 per API call if you enter your credit card details and create more than 1000 calls per day.
+[Dark Sky](https://darksky.net/dev/) will charge you $0.0001 per API call if you
+enter your credit card details and create more than 1000 calls per day.
+As of version 0.42 you have to set an initial state in your automations in order for Home Assistant to restore them upon restart.
```text
-automation:
- alias: Automation Name
initial_state: True
trigger:
...
```
+
+
-
-The message ("Unable to find service..."), source (`core.py`) and level (`WARNING`) can easily be extracted from the image. Exact timestamp and stack trace is shown if the entry is selected.
-
-## {% linkable_title Examples %}
-
-Here are some examples using the events posted by `system_log`.
-
-### {% linkable_title Counting Number of Warnings %}
-
-This will create a `counter` that increases every time a warning is logged:
-
-```yaml
-counter:
- warning_counter:
- name: Warnings
- icon: mdi:alert
-
-automation:
- - alias: Count warnings
- trigger:
- platform: event
- event_type: system_log_event
- event_data:
- level: WARNING
- action:
- service: counter.increment
- entity_id: counter.warning_counter
-```
-
-### {% linkable_title Conditional Messages %}
-
-This automation will create a persistent notification whenever an error or warning is logged that has the word "service" in the message:
-
-```yaml
-automation:
- - alias: Create notifications for "service" errors
- trigger:
- platform: event
- event_type: system_log_event
- condition:
- condition: template
- value_template: {% raw %}'{{ "service" in trigger.event.data.message }}'{% endraw %}
- action:
- service: persistent_notification.create
- data_template:
- title: Something bad happened
- message: {% raw %}'{{ trigger.event.data.message }}'{% endraw %}
-```
diff --git a/source/_components/tahoma.markdown b/source/_components/tahoma.markdown
index f41f3936cc..3d092af3fb 100644
--- a/source/_components/tahoma.markdown
+++ b/source/_components/tahoma.markdown
@@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
---
-The `Tahoma` component platform is used as an interface to the [tahomalink.com](https://www.tahomalink.com) website. It adds covers, scenes and a sun sensor from the Tahoma platform.
+The `Tahoma` component platform is used as an interface to the [tahomalink.com](https://www.tahomalink.com) website. It adds actually covers and the sun sensor from tahoma platform.
To use your Tahoma devices in your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_components/telegram_bot.markdown b/source/_components/telegram_bot.markdown
index 32397d0fbe..be2dcff5e5 100644
--- a/source/_components/telegram_bot.markdown
+++ b/source/_components/telegram_bot.markdown
@@ -19,27 +19,24 @@ This component creates notification services to send, or edit previously sent, m
If you don't need to receive messages, you can use the [broadcast](/components/telegram_bot.broadcast/) platform instead.
-## {% linkable_title Notification services %}
-
-Available services: `send_message`, `send_photo`, `send_document`, `send_location`, `send_sticker`, `edit_message`, `edit_replymarkup`, `edit_caption` and `answer_callback_query`.
-
-### {% linkable_title Service `telegram_bot.send_message` %}
+### {% linkable_title Notification services %}
+Available services: `send_message`, `send_photo`, `send_document`, `send_location`, `edit_message`, `edit_replymarkup`, `edit_caption`, `answer_callback_query`.
+#### {% linkable_title Service `telegram_bot/send_message` %}
Send a notification.
| Service data attribute | Optional | Description |
|---------------------------|----------|--------------------------------------------------|
| `message` | no | Message body of the notification. |
| `title` | yes | Optional title for your notification. Will be composed as '%title\n%message'. |
-| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
+| `target` | yes | An array of pre-authorized chat_ids to send the notification to. Defaults to the first allowed chat_id. |
| `parse_mode` | yes | Parser for the message text: `html` or `markdown`. |
| `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. |
| `disable_web_page_preview`| yes | True/false for disable link previews for links in the message. |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.send_photo` and `telegram_bot.send_sticker` %}
-
+#### {% linkable_title Service `telegram_bot/send_photo` %}
Send a photo.
| Service data attribute | Optional | Description |
@@ -47,16 +44,16 @@ Send a photo.
| `url` | no | Remote path to an image. |
| `file` | no | Local path to an image. |
| `caption` | yes | The title of the image. |
-| `username` | yes | Username for a URL which requires HTTP basic authentication. |
-| `password` | yes | Password for a URL which requires HTTP basic authentication. |
+| `username` | yes | Username for a URL which require HTTP basic authentication. |
+| `password` | yes | Password for a URL which require HTTP basic authentication. |
| `authentication` | yes | Define which authentication method to use. Set to `digest` to use HTTP digest authentication. Defaults to `basic`. |
-| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
+| `target` | yes | An array of pre-authorized chat_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.send_video` %}
+#### {% linkable_title Service `telegram_bot/send_video` %}
Send a video.
| Service data attribute | Optional | Description |
@@ -67,13 +64,12 @@ Send a video.
| `username` | yes | Username for a URL which requires HTTP basic authentication. |
| `password` | yes | Password for a URL which requires HTTP basic authentication. |
| `authentication` | yes | Define which authentication method to use. Set to `digest` to use HTTP digest authentication. Defaults to `basic`. |
-| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
+| `target` | yes | An array of pre-authorized chat_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false to send the message silently. iOS users and web users will not receive a notification. Android users will receive a notification with no sound. Defaults to False. |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.send_document` %}
-
+#### {% linkable_title Service `telegram_bot/send_document` %}
Send a document.
| Service data attribute | Optional | Description |
@@ -81,29 +77,27 @@ Send a document.
| `url` | no | Remote path to a document. |
| `file` | no | Local path to a document. |
| `caption` | yes | The title of the document. |
-| `username` | yes | Username for a URL which requires HTTP basic authentication. |
-| `password` | yes | Password for a URL which requires HTTP basic authentication. |
+| `username` | yes | Username for a URL which require HTTP basic authentication. |
+| `password` | yes | Password for a URL which require HTTP basic authentication. |
| `authentication` | yes | Define which authentication method to use. Set to `digest` to use HTTP digest authentication. Defaults to `basic`. |
-| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
+| `target` | yes | An array of pre-authorized chat_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.send_location` %}
-
+#### {% linkable_title Service `telegram_bot/send_location` %}
Send a location.
| Service data attribute | Optional | Description |
|---------------------------|----------|--------------------------------------------------|
| `latitude` | no | The latitude to send. |
| `longitude` | no | The longitude to send. |
-| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
+| `target` | yes | An array of pre-authorized chat_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.edit_message` %}
-
+#### {% linkable_title Service `telegram_bot/edit_message` %}
Edit a previously sent message in a conversation.
| Service data attribute | Optional | Description |
@@ -116,8 +110,7 @@ Edit a previously sent message in a conversation.
| `disable_web_page_preview`| yes | True/false for disable link previews for links in the message. |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.edit_caption` %}
-
+#### {% linkable_title Service `telegram_bot/edit_caption` %}
Edit the caption of a previously sent message.
| Service data attribute | Optional | Description |
@@ -128,9 +121,8 @@ Edit the caption of a previously sent message.
| `disable_web_page_preview`| yes | True/false for disable link previews for links in the message. |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.edit_replymarkup` %}
-
-Edit the inline keyboard of a previously sent message.
+#### {% linkable_title Service `telegram_bot/edit_replymarkup` %}
+Edit the inline keyboard of a previusly sent message.
| Service data attribute | Optional | Description |
|---------------------------|----------|--------------------------------------------------|
@@ -139,8 +131,7 @@ Edit the inline keyboard of a previously sent message.
| `disable_web_page_preview`| yes | True/false for disable link previews for links in the message. |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
-### {% linkable_title Service `telegram_bot.answer_callback_query` %}
-
+#### {% linkable_title Service `telegram_bot/answer_callback_query` %}
Respond to a callback query originated by clicking on an online keyboard button. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
| Service data attribute | Optional | Description |
@@ -149,7 +140,7 @@ Respond to a callback query originated by clicking on an online keyboard button.
| `callback_query_id` | no | Unique id of the callback response. In the `telegram_callback` event data: `{{ trigger.event.data.id }}` |
| `show_alert` | yes | True/false for show a permanent notification. Defaults to False. |
-### {% linkable_title Service `telegram_bot.delete_message` %}
+#### {% linkable_title Service `telegram_bot/delete_message` %}
Delete a previously sent message in a conversation.
| Service data attribute | Optional | Description |
@@ -157,12 +148,12 @@ Delete a previously sent message in a conversation.
| `message_id` | no | Id of the message to delete. When answering a callback from a pressed button, the id of the origin message is in: `{{ trigger.event.data.message.message_id }}`. You can use `"last"` to refer to the last message sent to `chat_id`. |
| `chat_id` | no | The chat_id where to delete the message. |
-## {% linkable_title `telegram` notification platform %}
+### {% linkable_title `Telegram` notification platform %}
-The [`telegram` notification platform](/components/notify.telegram/) requires the `telegram_bot` component to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility.
+
+The [Telegram notification platform](/components/notify.telegram/) requires the `telegram_bot` component to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility.
The required yaml configuration now reduces to:
-
```yaml
notify:
- name: NOTIFIER_NAME
@@ -170,7 +161,8 @@ notify:
chat_id: USER_CHAT_ID
```
-## {% linkable_title Event triggering %}
+### {% linkable_title Event triggering %}
+
A command looks like `/thecommand`, or `/othercommand with some args`.
@@ -197,7 +189,7 @@ chat_id: " Services developer tool. Services allow to change anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service `light.turn_on` is capable of turning on any light in your system. Services can be passed parameters to for example tell which device to turn on or what color to use.
-You have to set an initial state in your automations in order for Home Assistant to enable them upon restart.
+
@@ -39,20 +39,18 @@ As "Service Data" we want a simple text that is shown as part of the notificatio
}
```
-Don't forget to save your new automation rule. For your saved automation rule to come into effect, you will need to go to the **Configuration** page and click on **Reload Automation**.
+Don't forget to save your new automation rule. In order for your saved automation rule to come into effect you will need to go to the **Configuration** page and click on **Reload Automation**.
## {% linkable_title Updating your configuration to use the editor %}
-First, check that you have activated the configuration editor.
+First check that you have activated the configuration editor.
```yaml
# Activate the configuration editor
config:
```
-The automation editor reads and writes to the file `automations.yaml` in the root of your [configuration](/docs/configuration/) folder.
-Currently, both the name of this file and its location are fixed.
-Make sure that you have set up the automation component to read from it:
+The automation editor reads and writes to the file `automations.yaml` in your [configuration](/docs/configuration/) folder. Make sure that you have set up the automation component to read from it:
```yaml
# Configuration.yaml example
@@ -67,19 +65,9 @@ automation old:
platform: ...
```
-You can use the `automation:` and `automation old:` sections at the same time:
- - `automation old:` to keep your manual designed automations
- - `automation:` to save the automation created by the online editor
-
-```yaml
-automation: !include automations.yaml
-automation old: !include_dir_merge_list automations
-```
-
-
## {% linkable_title Migrating your automations to `automations.yaml` %}
-If you want to migrate your old automations to use the editor, you'll have to copy them to `automations.yaml`. Make sure that `automations.yaml` remains a list! For each automation that you copy over, you'll have to add an `id`. This can be any string as long as it's unique.
+If you want to migrate your old automations to use the editor, you'll have to copy them to `automations.yaml`. Make sure that `automations.yaml` remains a list! For each automation that you copy over you'll have to add an `id`. This can be any string as long as it's unique.
For example, the below automation will be triggered when the sun goes from below the horizon to above the horizon. Then, if the temperature is between 17 and 25 degrees, a light will be turned on.
diff --git a/source/_docs/automation/examples.markdown b/source/_docs/automation/examples.markdown
index 2e2ade256f..9e28e0b3e7 100644
--- a/source/_docs/automation/examples.markdown
+++ b/source/_docs/automation/examples.markdown
@@ -38,7 +38,6 @@ automation:
after: '16:00:00'
before: '23:00:00'
action:
- # With a single service call, we don't need a '-' before service - though you can if you want to
service: homeassistant.turn_on
entity_id: group.living_room
@@ -77,9 +76,9 @@ automation:
event_data:
entity_id: binary_sensor.cube_158d000103a3de
action:
- service_template: notify.pushover
- data_template:
- title: "Cube event detected"
- message: "Cube has triggered this event: {{ trigger.event }}"
+ - service_template: notify.pushover
+ data_template:
+ title: "Cube event detected"
+ message: "Cube has triggered this event: {{ trigger.event }}"
```
{% endraw %}
diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index 748ff6313d..140fd421ae 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -33,7 +33,7 @@ automation:
### {% linkable_title Home Assistant trigger %}
-Triggers when Home Assistant starts up or shuts down.
+Use this platform to trigger when Home Assistant starts up and shuts down.
```yaml
automation:
@@ -56,7 +56,7 @@ automation:
```
### {% linkable_title Numeric state trigger %}
-Triggers when numeric value of an entity's state crosses a given threshold. On state change of a specified entity, attempts to parse the state as a number and triggers once if value is changing from above to below or from below to above the given threshold.
+On state change of a specified entity, attempts to parse the state as a number and triggers once if value is changing from above to below a threshold, or from below to above the given threshold.
```yaml
automation:
@@ -78,13 +78,12 @@ automation:
Listing above and below together means the numeric_state has to be between the two values. -In the example above, a numeric_state that goes to 17.1-24.9 (from 17 or below, or 25 or above) -would fire this trigger. +In the example above, a numeric_state that is 17.1-24.9 would fire this trigger.
### {% linkable_title State trigger %} -Triggers when the state of a given entity changes. If only entity_id is given trigger will activate for all state changes, even if only state attributes change. +Triggers when the state of tracked entities change. If only entity_id given will match all state changes, even if only state attributes change. ```yaml automation: @@ -108,7 +107,7 @@ automation: ### {% linkable_title Sun trigger %} -Triggers when the sun is setting or rising. An optional time offset can be given to have it trigger a set time before or after the sun event (i.e. 45 minutes before sunset, when dusk is setting in). +Trigger when the sun is setting or rising. An optional time offset can be given to have it trigger for example 45 minutes before sunset, when dusk is setting in. ```yaml automation: @@ -183,7 +182,7 @@ automation 3: ### {% linkable_title 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. Currently this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/) as well as the [iCloud platform](/components/device_tracker.icloud/). ```yaml automation: diff --git a/source/_docs/autostart.markdown b/source/_docs/autostart.markdown index 48ca9fb411..95e9608adc 100644 --- a/source/_docs/autostart.markdown +++ b/source/_docs/autostart.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Autostart Home Assistant" -description: "Instructions on how to setup Home Assistant to launch on start." +description: "Instructions how to setup Home Assistant to launch on start." date: 2015-9-1 22:57 sidebar: true comments: false diff --git a/source/_docs/autostart/macos.markdown b/source/_docs/autostart/macos.markdown index 56e6b27c3f..0a1b6ea134 100644 --- a/source/_docs/autostart/macos.markdown +++ b/source/_docs/autostart/macos.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Autostart on macOS" -description: "Instructions on how to setup Home Assistant to launch on Apple macOS." +description: "Instructions how to setup Home Assistant to launch on Apple macOS." date: 2015-9-1 22:57 sidebar: true comments: false diff --git a/source/_docs/autostart/synology.markdown b/source/_docs/autostart/synology.markdown index f19f15ab73..2d97b91e57 100644 --- a/source/_docs/autostart/synology.markdown +++ b/source/_docs/autostart/synology.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Autostart on Synology NAS boot" -description: "Instructions on how to setup Home Assistant to launch on boot on Synology NAS." +description: "Instructions how to setup Home Assistant to launch on boot on Synology NAS." date: 2015-9-1 22:57 sidebar: true comments: false diff --git a/source/_docs/autostart/systemd.markdown b/source/_docs/autostart/systemd.markdown index 17211e5ed9..e1e1b6b466 100644 --- a/source/_docs/autostart/systemd.markdown +++ b/source/_docs/autostart/systemd.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Autostart using systemd" -description: "Instructions on how to setup Home Assistant to launch on boot using systemd." +description: "Instructions how to setup Home Assistant to launch on boot using systemd." date: 2015-9-1 22:57 sidebar: true comments: false @@ -21,7 +21,7 @@ If the preceding command returns the string `systemd`, continue with the instruc A service file is needed to control Home Assistant with `systemd`. The template below should be created using a text editor. Note, root permissions via `sudo` will likely be needed. The following should be noted to modify the template: - `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location. -- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as (normally `homeassistant`). In particular, this is the case for Ubuntu 16.04. +- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as (normally `homeassistant`). In particular, this is the case for Ubuntu 16.04. - If unfamiliar with command-line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file. Ex. `sudo nano -w /etc/systemd/system/home-assistant@[your user].service`. After text entered, press CTRL-X then press Y to save and exit. - If you're running Home Assistant in a Python virtual environment or a Docker container, please skip to the appropriate template listed below. @@ -41,7 +41,7 @@ WantedBy=multi-user.target ### {% linkable_title Python virtual environment %} -If you've setup Home Assistant in `virtualenv` following our [Python installation guide](/getting-started/installation-virtualenv/) or [manual installation guide for Raspberry Pi](/getting-started/installation-raspberry-pi/), the following template should work for you. If Home Assistant install is not located at `/srv/homeassistant`, please modify the `ExecStart=` line appropriately. +If you've setup Home Assistant in `virtualenv` following our [Python installation guide](https://home-assistant.io/getting-started/installation-virtualenv/) or [manual installation guide for Raspberry Pi](https://home-assistant.io/getting-started/installation-raspberry-pi/), the following template should work for you. If Home Assistant install is not located at `/srv/homeassistant`, please modify the `ExecStart=` line appropriately. ``` [Unit] @@ -80,7 +80,7 @@ WantedBy=multi-user.target ### Next Steps -You need to reload `systemd` to make the daemon aware of the new configuration. +You need to reload `systemd` to make the daemon aware of the new configuration. ```bash $ sudo systemctl --system daemon-reload diff --git a/source/_docs/autostart/upstart.markdown b/source/_docs/autostart/upstart.markdown index c77660a84d..b627ab3806 100644 --- a/source/_docs/autostart/upstart.markdown +++ b/source/_docs/autostart/upstart.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Autostart using Upstart" -description: "Instructions on how to setup Home Assistant to launch on boot using Upstart." +description: "Instructions how to setup Home Assistant to launch on boot using Upstart." date: 2015-9-1 22:57 sidebar: true comments: false diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown index 2d0dc0f027..0b7a7138ca 100644 --- a/source/_docs/configuration.markdown +++ b/source/_docs/configuration.markdown @@ -11,8 +11,6 @@ footer: true When launched for the first time, Home Assistant will write a default configuration file enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and appear in the user interface. -The web interface can be found at `http://ip.ad.dre.ss:8123/` - for example if your Home Assistant system has the IP address `192.168.0.40` then you'll find the web interface as `http://192.168.0.40:8123/`. - The location of the folder differs between operating systems: | OS | Path | @@ -26,12 +24,12 @@ If you want to use a different folder for configuration, use the config command Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains components to be loaded with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable functionality.- You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. You can load changes to [automations](/docs/automation/), [customize](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting. + You will have to restart Home Assistant for changes to `configuration.yaml` to take effect.
If you run into trouble while configuring Home Assistant, have a look at the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [configuration.yaml examples](/cookbook/#example-configurationyaml).- Test any changes to your configuration files from the command line with `hass --script check_config`. This script allows you to test changes without the need to restart Home Assistant. Remember to run this as the user you run Home Assistant as. + Test any changes to your configuration files from the command line with `hass --script check_config`. This script allows you to test changes without the need to restart Home Assistant.
diff --git a/source/_docs/configuration/basic.markdown b/source/_docs/configuration/basic.markdown index 3ac38b00a2..77e8359eba 100644 --- a/source/_docs/configuration/basic.markdown +++ b/source/_docs/configuration/basic.markdown @@ -28,7 +28,7 @@ Configuration variables: - **longitude** (*Optional*): Longitude of your location required to calculate the time the sun rises and sets. - **elevation** (*Optional*): Altitude above sea level in meters. Impacts weather/sunrise data. - **unit_system** (*Optional*): `metric` for Metric, `imperial` for Imperial. -- **time_zone** (*Optional*): Pick yours from here: [http://en.wikipedia.org/wiki/List_of_tz_database_time_zones](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones) +- **time_zone** (*Optional*): Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones - **name** (*Optional*): Name of the location where Home Assistant is running. - **customize** (*Optional*): [Customize](/docs/configuration/customizing-devices/) entities. - **customize_domain** (*Optional*): [Customize](/docs/configuration/customizing-devices/) all entities in a domain. diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index a76c1ed2aa..71b8a2f561 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -71,15 +71,14 @@ homeassistant: ### {% linkable_title Device Class %} -Device class is currently supported by the following components: +Device class is currently supported by the following platforms: * [Binary Sensor](/components/binary_sensor/) -* [Sensor](/components/sensor/) * [Cover](/components/cover/) ### {% linkable_title Reloading customize %} -Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant.reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the service developer tools, select the service `homeassistant.reload_core_config` and click "CALL SERVICE".
+Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant/reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the service developer tools, select the service `homeassistant/reload_core_config` and click "Call Service".
New customize information will be applied the next time the state of the entity gets updated. diff --git a/source/_docs/configuration/entity-registry.markdown b/source/_docs/configuration/entity-registry.markdown deleted file mode 100644 index 6c75ad8dfe..0000000000 --- a/source/_docs/configuration/entity-registry.markdown +++ /dev/null @@ -1,58 +0,0 @@ ---- -layout: page -title: "Entity Registry" -description: "The entity registry contains." -date: 2016-04-20 06:00 -sidebar: true -comments: false -sharing: true -footer: true ---- - -
-This is a new and experimental feature of Home Assistant. -
- -Starting with version 0.63, Home Assistant keeps a registry of known entities. -The entity registry makes sure that entities get unique identifiers and allow -customizing the identifiers and names of these entities. - -As this is still a very new part of Home Assistant, changes will require a -restart of Home Assistant to take effect. A config user interface will be added -in a future version. - --An entity needs to have a unique ID to be registered in the entity registry. -Not all integrations currently provide a unique id for their entities. -
- -The entity registry is stored in `- Starting 0.42, it is no longer possible to listen for event `homeassistant_start`. Use the 'homeassistant' [platform](/docs/automation/trigger) instead. -
- ### {% linkable_title Event `homeassistant_stop` %} Event `homeassistant_stop` is fired when Home Assistant is shutting down. It should be used to close any open connection or release any resources. diff --git a/source/_docs/configuration/group_visibility.markdown b/source/_docs/configuration/group_visibility.markdown index 0ea062deb9..acd352a07d 100644 --- a/source/_docs/configuration/group_visibility.markdown +++ b/source/_docs/configuration/group_visibility.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Group Visibility" -description: "Instructions on how to change group visibility using automations." +description: "Instructions how to change group visibility using automations." date: 2016-10-29 13:00 sidebar: true comments: false diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index 7c95fa719e..7e5016be99 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -10,9 +10,9 @@ footer: true redirect_from: /topics/packages/ --- -Packages in Home Assistant provides a way to bundle different component's configuration together. We already learned about the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the component key in the main `configuration.yaml` file. With packages we have a way to include different components, or different configuration parts using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration). +Packages in Home Assistant provides a way to bundle different component's configuration together. We were already introduced to the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the component key in the main `configuration.yaml` file. With packages we have a way to include different components, or parts of configuration using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration). -Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a package name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as: +Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a packages name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as: ```yaml homeassistant: @@ -22,7 +22,7 @@ homeassistant: ...package configuration here... ``` -The package configuration can include: `switch`, `light`, `automation`, `groups`, or most other Home Assistant components. +The package configuration can include: `switch`, `light`, `automation`, `groups` or the majority of the Home Assistant components. It can be specified inline or in a separate YAML file using `!include`. @@ -63,7 +63,7 @@ light: There are some rules for packages that will be merged: -1. Component names may only use the basic form (e.g., `switch`, but not `switch 1` or `switch aa`). +1. Component names may only use the basic form (e.g. `switch`, but not `switch 1` or `switch aa`). 2. Platform based components (`light`, `switch`, etc) can always be merged. 3. Components where entities are identified by a key that will represent the entity_id (`{key: config}`) need to have unique 'keys' between packages and the main configuration file. @@ -81,7 +81,7 @@ Components inside packages can only specify platform entries using configuration ### {% linkable_title Create a packages folder %} -One way to organize packages is to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages: +One way to organize packages would be to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages: ```yaml homeassistant: diff --git a/source/_docs/configuration/remote.markdown b/source/_docs/configuration/remote.markdown index a323ff1c98..bd0d0ba60b 100644 --- a/source/_docs/configuration/remote.markdown +++ b/source/_docs/configuration/remote.markdown @@ -7,6 +7,7 @@ sidebar: true comments: false sharing: true footer: true +redirect_from: /getting-started/basic/#remote-access --- If you're interested in logging in to Home Assistant while away, you'll have to make your instance remotely accessible. Remember to follow the [securing checklist](/docs/configuration/securing/) before doing this. @@ -15,7 +16,7 @@ The most common approach is to set up port forwarding from your router to port 8 A problem with making a port accessible is that some Internet Service Providers only offer dynamic IPs. This can cause you to lose access to Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/). -Remember: Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post, or this [detailed guide](/docs/ecosystem/certificates/lets_encrypt/) to using Let's Encrypt with HA. +Remember: Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post, or this [detailed guide](https://home-assistant.io/docs/ecosystem/certificates/lets_encrypt/) to using Let's Encrypt with HA. Protect your communication with a [self-signed certificate](/cookbook/tls_self_signed_certificate/) between your client and the Home Assistant instance. diff --git a/source/_docs/configuration/securing.markdown b/source/_docs/configuration/securing.markdown index fa6e91f8d3..24ec0aa4f0 100644 --- a/source/_docs/configuration/securing.markdown +++ b/source/_docs/configuration/securing.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Securing" -description: "Instructions on how to secure your Home Assistant installation." +description: "Instructions how to secure your Home Assistant installation." date: 2016-10-06 06:00 sidebar: true comments: false @@ -14,10 +14,10 @@ One major advantage of Home Assistant is that it's not dependent on cloud servic ### {% linkable_title Checklist %} -- [Protect your web interface with a password](/getting-started/basic/#password-protecting-the-web-interface) +- [Protect your web interface with a password](https://home-assistant.io/getting-started/basic/#password-protecting-the-web-interface) - Secure your host. Sources could be [Red Hat Enterprise Linux 7 Security Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Security_Guide/Red_Hat_Enterprise_Linux-7-Security_Guide-en-US.pdf), [CIS Red Hat Enterprise Linux 7 Benchmark](https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.0.0.pdf), or the [Securing Debian Manual](https://www.debian.org/doc/manuals/securing-debian-howto/index.en.html). - Restrict network access to your devices. Set `PermitRootLogin no` in your sshd config (usually `/etc/ssh/sshd_config`) and to use SSH keys for authentication instead of passwords. -- Don't run Home Assistant as root – consider the Principle of Least Privilege. +- Don't run Home Assistant as root – consider the Principle of Least Privilege. - Keep your [secrets](/topics/secrets/) safe. If you want to allow remote access, consider these additional points: diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown index ec0d021ea5..3a1a9b6e53 100644 --- a/source/_docs/configuration/splitting_configuration.markdown +++ b/source/_docs/configuration/splitting_configuration.markdown @@ -10,9 +10,9 @@ footer: true redirect_from: /topics/splitting_configuration/ --- -So you've been using Home Assistant for a while now and your [configuration.yaml file brings people to tears](/cookbook/configuration_yaml_from_bassclarinetl2/) or you simply want to start off with the distributed approach, here's how to "split the configuration.yaml" into more manageable (read: humanly readable) pieces. +So you've been using Home Assistant for a while now and your [configuration.yaml file brings people to tears](https://home-assistant.io/cookbook/configuration_yaml_from_bassclarinetl2/) or you simply want to start off with the distributed approach, here's how to "split the configuration.yaml" into more manageable (read: humanly readable) pieces. -First off, several community members have sanitized (read: without api keys/passwords etc) versions of their configurations available for viewing, you can see a list of them [here](/cookbook/#example-configurationyaml). +First off, several community members have sanitized (read: without api keys/passwords etc) versions of their configurations available for viewing, you can see a list of them [here](https://home-assistant.io/cookbook/#example-configurationyaml). As commenting code doesn't always happen, please read on for the details. diff --git a/source/_docs/configuration/state_object.markdown b/source/_docs/configuration/state_object.markdown index fdb99ea075..c9ee1f9403 100644 --- a/source/_docs/configuration/state_object.markdown +++ b/source/_docs/configuration/state_object.markdown @@ -37,7 +37,7 @@ Attribute | Description `icon` | Icon to use for the entity in the frontend. Example: `mdi:home`. `hidden` | Boolean if the entity should not be shown in the frontend. Example: `true`. `entity_picture` | URL to a picture that should be used instead of showing the domain icon. Example: `http://example.com/picture.jpg`. -`assumed_state` | Boolean if the current state is an assumption. [More info](/blog/2016/02/12/classifying-the-internet-of-things/#classifiers) Example: `True`. +`assumed_state` | Boolean if the current state is an assumption. [More info](https://home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/#classifiers) Example: `True`. `unit_of_measurement` | The unit of measurement the state is expressed in. Used for grouping graphs or understanding the entity. Example: `°C`. When an attribute contains spaces, you can retrieve it like this: `states.sensor.livingroom.attributes["Battery numeric"]`. diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index dfcd8bddce..a0d56a158a 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Templating" -description: "Instructions on how to use the templating feature of Home Assistant." +description: "Instructions how to use the templating feature of Home Assistant." date: 2015-12-12 12:00 sidebar: true comments: false @@ -43,13 +43,12 @@ script: msg_who_is_home: sequence: - service: notify.notify - data_template: - message: > - {% raw %}{% if is_state('device_tracker.paulus', 'home') %} - Ha, Paulus is home! - {% else %} - Paulus is at {{ states('device_tracker.paulus') }}. - {% endif %}{% endraw %} + message: > + {% raw %}{% if is_state('device_tracker.paulus', 'home') %} + Ha, Paulus is home! + {% else %} + Paulus is at {{ states('device_tracker.paulus') }}. + {% endif %}{% endraw %} ``` [Jinja2](http://jinja.pocoo.org/) supports a wide variety of operations: @@ -68,7 +67,6 @@ Home Assistant adds extensions to allow templates to access all of the current s - `states.sensor.temperature` returns the state object for `sensor.temperature`. - `states('device_tracker.paulus')` will return the state string (not the object) of the given entity or `unknown` if it doesn't exist. - `is_state('device_tracker.paulus', 'home')` will test if the given entity is specified state. -- `state_attr('device_tracker.paulus', 'battery')` will return the value of the attribute or None if it doesn't exist. - `is_state_attr('device_tracker.paulus', 'battery', 40)` will test if the given entity is specified state. - `now()` will be rendered as current time in your time zone. - For specific values: `now().second`, `now().minute`, `now().hour`, `now().day`, `now().month`, `now().year`, `now().weekday()` and `now().isoweekday()` @@ -80,25 +78,14 @@ Home Assistant adds extensions to allow templates to access all of the current s - `float` will format the output as float. - `strptime(string, format)` will parse a string to a datetime based on a [format][strp-format]. - `log(value, base)` will take the logarithm of the input. When the base is omitted, it defaults to `e` - the natural logarithm. Can also be used as a filter. -- `sin(value)` will return the sine of the input. Can be used as a filter. -- `cos(value)` will return the cosine of the input. Can be used as a filter. -- `tan(value)` will return the tangent of the input. Can be used as a filter. -- `sqrt(value)` will return the square root of the input. Can be used as a filter. -- `e` mathematical constant, approximately 2.71828. -- `pi` mathematical constant, approximately 3.14159. -- `tau` mathematical constant, approximately 6.28318. - Filter `round(x)` will convert the input to a number and round it to `x` decimals. - Filter `timestamp_local` will convert an UNIX timestamp to local time/data. - Filter `timestamp_utc` will convert an UNIX timestamp to UTC time/data. - Filter `timestamp_custom(format_string, local_boolean)` will convert an UNIX timestamp to a custom format, the use of a local timestamp is default, supporting [Python format options](https://docs.python.org/3/library/time.html#time.strftime). -- Filter `max` will obtain the largest item in a sequence. +- Filter `max` will obtain the larget item in a sequence. - Filter `min` will obtain the smallest item in a sequence. -- Filter `regex_match(string, find, ignorecase=FALSE)` will match the find expression at the beginning of the string using regex. -- Filter `regex_search(string, find, ignorecase=FALSE)` will match the find expression anywhere in the string using regex. -- Filter `regex_replace(string, find='', replace='', ignorecase=False)` will replace the find expression with the replace string using regex. -- Filter `regex_findall_index(string, find='', index=0, ignorecase=False)` will find all regex matches of find in string and return the match at index (findall returns an array of matches). -[strp-format]: https://docs.python.org/3.6/library/datetime.html#strftime-and-strptime-behavior +[strp-format]: https://docs.python.org/3.4/library/datetime.html#strftime-and-strptime-behaviorIf your template uses an `entity_id` that begins with a number (example: `states.device_tracker.2008_gmc`) you must use a bracket syntax to avoid errors caused by rendering the `entity_id` improperly. In the example given, the correct syntax for the device tracker would be: `states.device_tracker['2008_gmc']` @@ -126,7 +113,7 @@ The next two statements result in same value if state exists. The second one wil ### {% linkable_title Attributes %} -Print an attribute if state is defined. Both will return the same thing but the last one you can specify entity_id from a variable. +Print an attribute if state is defined ```text {% raw %}{% if states.device_tracker.paulus %} @@ -136,18 +123,6 @@ Print an attribute if state is defined. Both will return the same thing but the {% endif %}{% endraw %} ``` -With strings - -```text -{% raw %}{% set tracker_name = "paulus"%} - -{% if states("device_tracker." + tracker_name) != "unknown" %} - {{ state_attr("device_tracker." + tracker_name, "battery")}} -{% else %} - ?? -{% endif %}{% endraw %} -``` - ### {% linkable_title Sensor states %} Print out a list of all the sensor states. @@ -281,10 +256,6 @@ The following overview contains a couple of options to get the needed values: {% raw %}{{ float(value_json) * (2**10) }}{% endraw %} {% raw %}{{ value_json | log }}{% endraw %} {% raw %}{{ log(1000, 10) }}{% endraw %} -{% raw %}{{ sin(pi / 2) }}{% endraw %} -{% raw %}{{ cos(tau) }}{% endraw %} -{% raw %}{{ tan(pi) }}{% endraw %} -{% raw %}{{ sqrt(e) }}{% endraw %} # Timestamps {% raw %}{{ value_json.tst | timestamp_local }}{% endraw %} diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown index 0d867a2622..f1b88fe876 100644 --- a/source/_docs/configuration/troubleshooting.markdown +++ b/source/_docs/configuration/troubleshooting.markdown @@ -20,7 +20,7 @@ Whenever a component or configuration option results in a warning, it will be st When a component does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your component you are trying to set up. -If you have incorrect entries in your configuration files you can use the [`check_config`](/docs/tools/check_config/) script to assist in identifying them: `hass --script check_config`. If you need to provide the path for your configuration you can do this using the `-c` argument like this: `hass --script check_config -c /path/to/your/config/dir`. +If you have incorrect entries in your configuration files you can use the `check_config` script to assist in identifying them: `hass --script check_config`. #### {% linkable_title Problems with the configuration %} diff --git a/source/_docs/configuration/yaml.markdown b/source/_docs/configuration/yaml.markdown index 68503dab96..9398ec30bd 100644 --- a/source/_docs/configuration/yaml.markdown +++ b/source/_docs/configuration/yaml.markdown @@ -93,15 +93,3 @@ lights: !include lights.yaml ``` More information about this feature can also be found at [splitting configuration](/docs/configuration/splitting_configuration/). - -## {% linkable_title Common Issues %} - -### {% linkable_title found character '\t' %} - -If you see the following message: - -``` -found character '\t' that cannot start any token -``` - -This means that you've mistakenly entered a tab character, instead of spaces. diff --git a/source/_docs/ecosystem/apache.markdown b/source/_docs/ecosystem/apache.markdown index 92c27eb51a..ae0c192511 100644 --- a/source/_docs/ecosystem/apache.markdown +++ b/source/_docs/ecosystem/apache.markdown @@ -35,10 +35,10 @@ To be able to access to your Home Assistant instance by using https://home.examp ServerName home.example.org ProxyPreserveHost On ProxyRequests off - ProxyPass /api/websocket ws://localhost:8123/api/websocket - ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket ProxyPass / http://localhost:8123/ ProxyPassReverse / http://localhost:8123/ + ProxyPass /api/websocket ws://localhost:8123/api/websocket + ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket RewriteEngine on RewriteCond %{HTTP:Upgrade} =websocket [NC] diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown index f327433108..76edbc1dd5 100755 --- a/source/_docs/ecosystem/appdaemon.markdown +++ b/source/_docs/ecosystem/appdaemon.markdown @@ -76,7 +76,7 @@ class FlashyMotionLights(appapi.AppDaemon): This is starting to get a little more complex in Home Assistant automations, requiring an automation rule and two separate scripts. -Now let's extend this with a somewhat artificial example to show something that is simple in AppDaemon but very difficult if not impossible using automations. Let's warn someone inside the house that there has been motion outside by flashing a lamp on and off ten times. We are reacting to the motion as before by turning on the light and setting a timer to turn it off again, but in addition, we set a 1-second timer to run `flash_warning()`, which, when called, toggles the inside light and sets another timer to call itself a second later. To avoid re-triggering forever, it keeps a count of how many times it has been activated and bails out after ten iterations. +Now let's extend this with a somewhat artificial example to show something that is simple in AppDaemon but very difficult if not impossible using automations. Let's warn someone inside the house that there has been motion outside by flashing a lamp on and off ten times. We are reacting to the motion as before by turning on the light and setting a timer to turn it off again, but in addition, we set a 1-second timer to run `flash_warning()`, which, when called, toggles the inside light and sets another timer to call itself a second later. To avoid re-triggering forever, it keeps a count of how many times it has been activated and bales out after ten iterations. ```python import appdaemon.appapi as appapi diff --git a/source/_docs/ecosystem/appdaemon/api.markdown b/source/_docs/ecosystem/appdaemon/api.markdown index 923505b262..48c8d994ba 100755 --- a/source/_docs/ecosystem/appdaemon/api.markdown +++ b/source/_docs/ecosystem/appdaemon/api.markdown @@ -39,7 +39,7 @@ There are several circumstances under which `initialize()` might be called: - Following a change in the status of Daylight Savings Time - Following a restart of Home Assistant -In every case, the App is responsible for recreating any state it might need as if it were the first time it was ever started. If `initialize()` is called, the app can safely assume that it is either being loaded for the first time, or that all callbacks and timers have been canceled. In either case, the APP will need to recreate them. Depending upon the application it may be desirable for the App to establish state such as whether or not a particular light is on, within the `initialize()` function to ensure that everything is as expected or to make immediate remedial action (e.g., turn off a light that might have been left on by mistake when the app was restarted). +In every case, the App is responsible for recreating any state it might need as if it were the first time it was ever started. If `initialize()` is called, the app can safely assume that it is either being loaded for the first time, or that all callbacks and timers have been canceled. In either case, the APP will need to recreate them. Depending upon the application it may be desirable for the App to establish state such as whether or not a particular light is on, within the `initialize()` function to ensure that everything is as expected or to make immediate remedial action (e.g. turn off a light that might have been left on by mistake when the app was restarted). After the `initialize()` function is in place, the rest of the app consists of functions that are called by the various callback mechanisms, and any additional functions the user wants to add as part of the program logic. Apps are able to subscribe to 2 main classes of events: @@ -150,7 +150,7 @@ light = light.garage ## {% linkable_title Callback Constraints %} -Callback constraints are a feature of AppDaemon that removes the need for repetition of some common coding checks. Many Apps will wish to process their callbacks only when certain conditions are met, e.g., someone is home, and it's after sunset. These kinds of conditions crop up a lot, and use of callback constraints can significantly simplify the logic required within callbacks. +Callback constraints are a feature of AppDaemon that removes the need for repetition of some common coding checks. Many Apps will wish to process their callbacks only when certain conditions are met, e.g. someone is home, and it's after sunset. These kinds of conditions crop up a lot, and use of callback constraints can significantly simplify the logic required within callbacks. Put simply, callback constraints are one or more conditions on callback execution that can be applied to an individual App. An App's callbacks will only be executed if all of the constraints are met. If a constraint is absent it will not be checked for. @@ -194,7 +194,7 @@ constrain_input_boolean = input_boolean.enable_motion_detection,off ``` ### {% linkable_title input_select %} -The input_select constraint prevents callbacks unless the specified input_select is set to one or more of the nominated (comma separated) values. This is useful to allow certain Apps to be turned on and off according to some flag, e.g., a house mode flag. +The input_select constraint prevents callbacks unless the specified input_select is set to one or more of the nominated (comma separated) values. This is useful to allow certain Apps to be turned on and off according to some flag, e.g. a house mode flag. ```ini # Single value @@ -272,7 +272,7 @@ Any other attributes such as brightness for a lamp will only be present if the e Also bear in mind that some attributes such as brightness for a light, will not be present when the light is off. -In most cases, the attribute `state` has the most important value in it, e.g., for a light or switch this will be `on` or `off`, for a sensor it will be the value of that sensor. Many of the AppDaemon API calls and callbacks will implicitly return the value of state unless told to do otherwise. +In most cases, the attribute `state` has the most important value in it, e.g. for a light or switch this will be `on` or `off`, for a sensor it will be the value of that sensor. Many of the AppDaemon API calls and callbacks will implicitly return the value of state unless told to do otherwise. ### {% linkable_title get_state() %} @@ -294,9 +294,9 @@ All parameters are optional, and if `get_state()` is called with no parameters i ##### {% linkable_title entity %} -This is the name of an entity or device type. If just a device type is provided, e.g., `light` or `binary_sensor`, `get_state()` will return a dictionary of all devices of that type, indexed by the entity_id, containing all the state for each entity. +This is the name of an entity or device type. If just a device type is provided, e.g. `light` or `binary_sensor`, `get_state()` will return a dictionary of all devices of that type, indexed by the entity_id, containing all the state for each entity. -If a fully qualified `entity_id` is provided, `get_state()` will return the state attribute for that entity, e.g., `on` or `off` for a light. +If a fully qualified `entity_id` is provided, `get_state()` will return the state attribute for that entity, e.g. `on` or `off` for a light. ##### {% linkable_title attribute %} @@ -345,11 +345,11 @@ set_state(entity_id, **kwargs) ##### {% linkable_title entity_id %} -Entity id for which the state is to be set, e.g., `light.office_1`. +Entity id for which the state is to be set, e.g. `light.office_1`. ##### {% linkable_title values %} -A list of keyword values to be changed or added to the entities state. e.g., `state = "off"`. Note that any optional attributes such as colors for bulbs etc, need to reside in a dictionary called `attributes`; see the example. +A list of keyword values to be changed or added to the entities state. e.g. `state = "off"`. Note that any optional attributes such as colors for bulbs etc, need to reside in a dictionary called `attributes`; see the example. #### {% linkable_title Examples %} @@ -461,7 +461,7 @@ handle = listen_state(callback, entity = None, **kwargs) #### {% linkable_title Returns %} -A unique identifier that can be used to cancel the callback if required. Since variables created within object methods are local to the function they are created in, and in all likelihood the cancellation will be invoked later in a different function, it is recommended that handles are stored in the object namespace, e.g., `self.handle`. +A unique identifier that can be used to cancel the callback if required. Since variables created within object methods are local to the function they are created in, and in all likelihood the cancellation will be invoked later in a different function, it is recommended that handles are stored in the object namespace, e.g. `self.handle`. #### {% linkable_title Parameters %} @@ -473,9 +473,9 @@ Function to be invoked when the requested state change occurs. It must conform t ##### {% linkable_title entity %} -This is the name of an entity or device type. If just a device type is provided, e.g., `light` or `binary_sensor`, `listen_state()` will subscribe to state changes of all devices of that type. If a fully qualified `entity_id` is provided, `listen_state()` will listen for state changes for just that entity. +This is the name of an entity or device type. If just a device type is provided, e.g. `light` or `binary_sensor`, `listen_state()` will subscribe to state changes of all devices of that type. If a fully qualified `entity_id` is provided, `listen_state()` will listen for state changes for just that entity. -When called, AppDaemon will supply the callback function, in old and new, with the state attribute for that entity, e.g., `on` or `off` for a light. +When called, AppDaemon will supply the callback function, in old and new, with the state attribute for that entity, e.g. `on` or `off` for a light. ##### {% linkable_title attribute (optional) %} @@ -949,11 +949,11 @@ All of the scheduler calls above support 2 additional optional arguments, `rando For example: ```python -# Run a callback in 2 minutes minus a random number of seconds between 0 and 60, e.g., run between 60 and 120 seconds from now +# Run a callback in 2 minutes minus a random number of seconds between 0 and 60, e.g. run between 60 and 120 seconds from now self.handle = self.run_in(callback, 120, random_start = -60, **kwargs) -# Run a callback in 2 minutes plus a random number of seconds between 0 and 60, e.g., run between 120 and 180 seconds from now +# Run a callback in 2 minutes plus a random number of seconds between 0 and 60, e.g. run between 120 and 180 seconds from now self.handle = self.run_in(callback, 120, random_end = 60, **kwargs) -# Run a callback in 2 minutes plus or minus a random number of seconds between 0 and 60, e.g., run between 60 and 180 seconds from now +# Run a callback in 2 minutes plus or minus a random number of seconds between 0 and 60, e.g. run between 60 and 180 seconds from now self.handle = self.run_in(callback, 120, random_start = -60, random_end = 60, **kwargs) ``` @@ -1150,11 +1150,11 @@ None ##### {% linkable_title service %} -The service name, e.g., `light.turn_on`. +The service name, e.g. `light.turn_on`. ##### {% linkable_title \*\*kwargs %} -Each service has different parameter requirements. This argument allows you to specify a comma separated list of keyword value pairs, e.g., `entity_id = light.office_1`. These parameters will be different for every service and can be discovered using the developer tools. Most if not all service calls require an `entity_id` however, so use of the above example is very common with this call. +Each service has different parameter requirements. This argument allows you to specify a comma separated list of keyword value pairs, e.g. `entity_id = light.office_1`. These parameters will be different for every service and can be discovered using the developer tools. Most if not all service calls require an `entity_id` however, so use of the above example is very common with this call. #### {% linkable_title Examples %} @@ -1187,7 +1187,7 @@ None ##### {% linkable_title entity_id %} -Fully qualified entity_id of the thing to be turned on, e.g., `light.office_lamp` or ```scene.downstairs_on``` +Fully qualified entity_id of the thing to be turned on, e.g. `light.office_lamp` or ```scene.downstairs_on``` ##### {% linkable_title \*\*kwargs %} @@ -1219,7 +1219,7 @@ None ##### {% linkable_title entity_id %} -Fully qualified entity_id of the thing to be turned off, e.g., `light.office_lamp` or `scene.downstairs_on`. +Fully qualified entity_id of the thing to be turned off, e.g. `light.office_lamp` or `scene.downstairs_on`. #### {% linkable_title Examples %} @@ -1246,7 +1246,7 @@ None ##### {% linkable_title entity_id %} -Fully qualified entity_id of the thing to be toggled, e.g., `light.office_lamp` or `scene.downstairs_on`. +Fully qualified entity_id of the thing to be toggled, e.g. `light.office_lamp` or `scene.downstairs_on`. #### {% linkable_title Examples %} @@ -1273,7 +1273,7 @@ None ##### {% linkable_title entity_id %} -Fully qualified entity_id of the input_number to be changed, e.g., `input_number.alarm_hour`. +Fully qualified entity_id of the input_number to be changed, e.g. `input_number.alarm_hour`. ##### {% linkable_title value %} @@ -1303,7 +1303,7 @@ None ##### {% linkable_title entity_id %} -Fully qualified entity_id of the input_select to be changed, e.g., `input_select.mode`. +Fully qualified entity_id of the input_select to be changed, e.g. `input_select.mode`. ##### {% linkable_title value %} @@ -1385,7 +1385,7 @@ A standard Python object reference. #### {% linkable_title event_name %} -Name of the event that was called, e.g., `call_service`. +Name of the event that was called, e.g. `call_service`. #### {% linkable_title data %} @@ -1422,7 +1422,7 @@ Name of the event to subscribe to. Can be a standard Home Assistant event such a One or more keyword value pairs representing App specific parameters to supply to the callback. If the keywords match values within the event data, they will act as filters, meaning that if they don't match the values, the callback will not fire. -As an example of this, a Minimote controller when activated will generate an event called `zwave.scene_activated`, along with 2 pieces of data that are specific to the event - `entity_id` and `scene`. If you include keyword values for either of those, the values supplied to the `listen_event()` call must match the values in the event or it will not fire. If the keywords do not match any of the data in the event they are simply ignored. +As an example of this, a Minimote controller when activated will generate an event called `zwave.scene_activated`, along with 2 pieces of data that are specific to the event - `entity_id` and `scene`. If you include keyword values for either of those, the values supplied to the `listen_event()1 call must match the values in the event or it will not fire. If the keywords do not match any of the data in the event they are simply ignored. Filtering will work with any event type, but it will be necessary to figure out the data associated with the event to understand what values can be filtered on. This can be achieved by examining Home Assistant's logfiles when the event fires. @@ -1528,7 +1528,7 @@ def service(self, event_name, data): #### {% linkable_title event_name %} -The name of the event that caused the callback, e.g., `"MODE_CHANGE"` or `call_service`. +The name of the event that caused the callback, e.g. `"MODE_CHANGE"` or `call_service`. #### {% linkable_title data %} @@ -1617,7 +1617,7 @@ A string representing the location of the tracker. ##### {% linkable_title tracker_id %} -Fully qualified entity_id of the device tracker to query, e.g., `device_tracker.andrew`. +Fully qualified entity_id of the device tracker to query, e.g. `device_tracker.andrew`. #### {% linkable_title Examples %} @@ -1871,7 +1871,7 @@ self.log("{} ({}) is {}".format(tracker, self.friendly_name(tracker), self.get_ ### {% linkable_title split_entity() %} -`split_entity()` will take a fully qualified entity id of the form `light.hall_light` and split it into 2 values, the device and the entity, e.g., `light` and `hall_light`. +`split_entity()` will take a fully qualified entity id of the form `light.hall_light` and split it into 2 values, the device and the entity, e.g. `light` and `hall_light`. #### {% linkable_title Synopsis %} @@ -1925,7 +1925,7 @@ MyApp.turn_light_on() ### {% linkable_title split_device_list() %} -`split_device_list()` will take a comma separated list of device types (or anything else for that matter) and return them as an iterable list. This is intended to assist in use cases where the App takes a list of entities from an argument, e.g., a list of sensors to monitor. If only one entry is provided, an iterable list will still be returned to avoid the need for special processing. +`split_device_list()` will take a comma separated list of device types (or anything else for that matter) and return them as an iterable list. This is intended to assist in use cases where the App takes a list of entities from an argument, e.g. a list of sensors to monitor. If only one entry is provided, an iterable list will still be returned to avoid the need for special processing. #### {% linkable_title Synopsis %} @@ -1941,7 +1941,7 @@ A list of split devices with 1 or more entries. ```python for sensor in self.split_device_list(self.args["sensors"]): - do something for each sensor, e.g., make a state subscription + do something for each sensor, e.g. make a state subscription ``` diff --git a/source/_docs/ecosystem/appdaemon/tutorial.markdown b/source/_docs/ecosystem/appdaemon/tutorial.markdown index 28f325dfa0..6a9998bced 100755 --- a/source/_docs/ecosystem/appdaemon/tutorial.markdown +++ b/source/_docs/ecosystem/appdaemon/tutorial.markdown @@ -12,7 +12,7 @@ redirect_from: /ecosystem/appdaemon/tutorial/ ## {% linkable_title Another Take on Automation %} -If you haven't yet read Paulus' excellent Blog entry on [Perfect Home Automation](/blog/2016/01/19/perfect-home-automation/) I would encourage you to take a look. As a veteran of several Home Automation systems with varying degrees success, it was this article more than anything else that convinced me that Home Assistant had the right philosophy behind it and was on the right track. One of the most important points made is that being able to control your lights from your phone, 9 times out of 10 is harder than using a lightswitch - where Home Automation really comes into its own is when you start removing the need to use a phone or the switch - the "Automation" in Home Automation. A surprisingly large number of systems out there miss this essential point and have limited abilities to automate anything which is why a robust and open system such as Home Assistant is such an important part of the equation in bring this all together in the vast and chaotic ecosystem that is the "Internet of Things". +If you haven't yet read Paulus' excellent Blog entry on [Perfect Home Automation](https://home-assistant.io/blog/2016/01/19/perfect-home-automation/) I would encourage you to take a look. As a veteran of several Home Automation systems with varying degrees success, it was this article more than anything else that convinced me that Home Assistant had the right philosophy behind it and was on the right track. One of the most important points made is that being able to control your lights from your phone, 9 times out of 10 is harder than using a lightswitch - where Home Automation really comes into its own is when you start removing the need to use a phone or the switch - the "Automation" in Home Automation. A surprisingly large number of systems out there miss this essential point and have limited abilities to automate anything which is why a robust and open system such as Home Assistant is such an important part of the equation in bring this all together in the vast and chaotic ecosystem that is the "Internet of Things". So given the importance of Automation, what should Automation allow us to do? I am a pragmatist at heart so I judge individual systems by the ease of accomplishing a few basic but representative tasks: @@ -29,7 +29,7 @@ So why `AppDaemon`? AppDaemon is not meant to replace Home Assistant Automations - New paradigm - some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can't - Ease of use - AppDaemon's API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible, experienced Python programmers should feel right at home. -- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g., a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file +- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file - Dynamic - AppDaemon has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to its loose coupling. However, it is better than that - the user can make changes to code and AppDaemon will automatically reload the code, figure out which Apps were using it and restart them to use the new code with out the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result. - Complex logic - Python's If/Else constructs are clearer and easier to code for arbitrarily complex nested logic - Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened @@ -43,38 +43,22 @@ The best way to show what AppDaemon does is through a few simple examples. ### {% linkable_title Sunrise/Sunset Lighting %} -Lets start with a simple App to turn a light on every night fifteen -minutes (900 seconds) before sunset and off every morning at sunrise. -Every App when first started will have its ``initialize()`` function -called which gives it a chance to register a callback for AppDaemons's -scheduler for a specific time. In this case we are using -`run_at_sunrise()` and `run_at_sunset()` to register 2 separate -callbacks. The named argument `offset` is the number of seconds offset -from sunrise or sunset and can be negative or positive (it defaults to -zero). For complex intervals it can be convenient to use Python's -`datetime.timedelta` class for calculations. In the example below, -when sunrise or just before sunset occurs, the appropriate callback -function, `sunrise_cb()` or `before_sunset_cb()` is called which -then makes a call to Home Assistant to turn the porch light on or off by -activating a scene. The variables `args["on_scene"]` and -`args["off_scene"]` are passed through from the configuration of this -particular App, and the same code could be reused to activate completely -different scenes in a different version of the App. +Lets start with a simple App to turn a light on every night at sunset and off every morning at sunrise. Every App when first started will have its `initialize()` function called which gives it a chance to register a callback for AppDaemons's scheduler for a specific time. In this case we are using `run_at_sunrise()` and `run_at_sunset()` to register 2 separate callbacks. The argument `0` is the number of seconds offset from sunrise or sunset and can be negative or positive. For complex intervals it can be convenient to use Python's `datetime.timedelta` class for calculations. When sunrise or sunset occurs, the appropriate callback function, `sunrise_cb()` or `sunset_cb()` is called which then makes a call to Home Assistant to turn the porch light on or off by activating a scene. The variables `args["on_scene"]` and `args["off_scene"]` are passed through from the configuration of this particular App, and the same code could be reused to activate completely different scenes in a different version of the App. ```python - import appdaemon.plugins.hass.hassapi as hass +import homeassistant.appapi as appapi - class OutsideLights(hass.Hass): +class OutsideLights(appapi.AppDaemon): - def initialize(self): - self.run_at_sunrise(self.sunrise_cb) - self.run_at_sunset(self.before_sunset_cb, offset=-900) + def initialize(self): + self.run_at_sunrise(self.sunrise_cb, 0) + self.run_at_sunset(self.sunset_cb, 0) + + def sunrise_cb(self, kwargs): + self.turn_on(self.args["off_scene"]) - def sunrise_cb(self, kwargs): - self.turn_on(self.args["off_scene"]) - - def before_sunset_cb(self, kwargs): - self.turn_on(self.args["on_scene"]) + def sunset_cb(self, kwargs): + self.turn_on(self.args["on_scene"]) ``` @@ -91,12 +75,12 @@ class FlashyMotionLights(appapi.AppDaemon): def initialize(self): self.listen_state(self.motion, "binary_sensor.drive", new = "on") - + def motion(self, entity, attribute, old, new, kwargs): if self.sun_down(): self.turn_on("light.drive") self.run_in(self.light_off, 60) - + def light_off(self, kwargs): self.turn_off("light.drive") ``` @@ -112,17 +96,17 @@ class MotionLights(appapi.AppDaemon): def initialize(self): self.listen_state(self.motion, "binary_sensor.drive", new = "on") - + def motion(self, entity, attribute, old, new, kwargs): if self.self.sun_down(): self.turn_on("light.drive") self.run_in(self.light_off, 60) self.flashcount = 0 self.run_in(self.flash_warning, 1) - + def light_off(self, kwargs): self.turn_off("light.drive") - + def flash_warning(self, kwargs): self.toggle("light.living_room") self.flashcount += 1 @@ -138,7 +122,7 @@ I have spent the last few weeks moving all of my (fairly complex) automations ov Some people will maybe look at all of this and say "what use is this, I can already do all of this", and that is fine, as I said this is an alternative not a replacement, but I am hopeful that for some users this will seem a more natural, powerful and nimble way of building potentially very complex automations. -If this has whet your appetite, feel free to give it a try. +If this has whet your appetite, feel free to give it a try. Happy Automating! diff --git a/source/_docs/ecosystem/backup/backup_dropbox.markdown b/source/_docs/ecosystem/backup/backup_dropbox.markdown index 6baa2cbc9a..e0d7336899 100644 --- a/source/_docs/ecosystem/backup/backup_dropbox.markdown +++ b/source/_docs/ecosystem/backup/backup_dropbox.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Configuration Backup to Dropbox" -description: "Instructions on how backup your Home Assistant configuration to Dropbox" +description: "Instructions how backup your Home Assistant configuration to Dropbox" date: 2017-04-24 18:00 sidebar: true comments: false @@ -10,7 +10,7 @@ footer: true redirect_from: /cookbook/dropboxbackup/ --- -Backing up and regularly syncing your Home Assistant configuration to [Dropbox](http://dropbox.com) similar to [Github Backup](/docs/ecosystem/backup/backup_github/) +Backing up and regularly syncing your Home Assistant configuration to [Dropbox](http://dropbox.com) similar to [Github Backup](https://home-assistant.io/docs/ecosystem/backup/backup_github/) ### {% linkable_title Requirements %} diff --git a/source/_docs/ecosystem/backup/backup_github.markdown b/source/_docs/ecosystem/backup/backup_github.markdown index 278d3fc20c..db4ab29626 100644 --- a/source/_docs/ecosystem/backup/backup_github.markdown +++ b/source/_docs/ecosystem/backup/backup_github.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Configuration Backup to GitHub" -description: "Instructions on how backup your Home Assistant configuration to GitHub" +description: "Instructions how backup your Home Assistant configuration to GitHub" date: 2017-01-05 18:00 sidebar: true comments: false @@ -28,21 +28,21 @@ This will not create a full backup of your Home Assistant files or your OS. In a Some best practices to consider before putting your configuration on GitHub: -- Extensive use of [secrets.yaml](/topics/secrets/) to hide sensitive information like usernames, passwords, device information, and location +- Extensive use of [secrets.yaml](https://home-assistant.io/topics/secrets/) to hide sensitive information like usernames, passwords, device information, and location - Exclusion of some files, including `secrets.yaml` and device-specific information using a [`.gitignore`](https://git-scm.com/docs/gitignore) file - Regularly committing your configuration to GitHub to make sure that your backup is up to date - Use a README.md to document your configuration and include screenshots of your Home Assistant GUI ### {% linkable_title Step 1: Installing and Initializing Git %} -In order to put your configuration on GitHub, you must install the git package on your Home Assistant server (instructions below will work on Raspberry Pi, Ubunutu, or any Debian-based system) *note: this isn't required in Hass.io, it's included as default so proceed to step 2*: +In order to put your configuration on GitHub, you must install the git package on your Home Assistant server (instructions below will work on Raspberry Pi, Ubunutu, or any Debian-based system): ```bash $ sudo apt-get update $ sudo apt-get install git ``` -### {% linkable_title Step 2: Creating %} `.gitignore` +### {% linkable_title Step 2: Creating %} `.gitignore`
Before creating and pushing your Home Assistant configuration to GitHub, please make sure to follow the `secrets.yaml` best practice mentioned above and scrub your configuration for any passwords or sensitive information. diff --git a/source/_docs/ecosystem/backup/backup_usb.markdown b/source/_docs/ecosystem/backup/backup_usb.markdown index cc07a0b079..6bd6276883 100644 --- a/source/_docs/ecosystem/backup/backup_usb.markdown +++ b/source/_docs/ecosystem/backup/backup_usb.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Configuration Backup to USB drive" -description: "Instructions on how backup your Home Assistant configuration to USB drive" +description: "Instructions how backup your Home Assistant configuration to USB drive" date: 2017-04-29 08:00 sidebar: true comments: false @@ -9,12 +9,11 @@ sharing: true footer: true --- -This will step you through the process of setting up a backup of your Home Assistant configuration to a USB device. This is a good method if you don't want to mask all of your passwords since the backup is kept locally at your home/residence. +Backing up your Home Assistant configuration to USB drive. A good plus side is that you don't need to mask all your passwords since the backup is locally at your home/residence. ### {% linkable_title Requirements %} - -First, you need a USB drive. It should be formatted properly for your device and connected to your device before beginning. Any type of partition will work, but Linux filesystems are preferred so that you can set permissions. -Once connected you want to mount the drive. To find the path where it is located, you can use the `dmesg` command. +First you need a USB drive. Once you have one you need to prepare it to be used on your device. +Once connected you want to format/work with the drive. To know what path it is in, you can check with `dmesg`. ```bash # dmesg | grep sd @@ -33,17 +32,16 @@ Once connected you want to mount the drive. To find the path where it is located [726259.209004] sd 0:0:0:0: [sda] Attached SCSI removable disk ``` -The device here is `sda` and our partition is `sda1`. So our partition is located here `/dev/sda1`. +Here we see we have a drive on `/dev/sda1`. We assume you created a partition on the drive to start with. This can be any type of partition. Preferred is a Linux filesystem type so you can set permissions! Mount the drive (as root) to `/media` ```bash -# sudo mount /dev/sda1 /media/ +# mount /dev/sda1 /media/ ``` -### {% linkable_title Prepare the USB Device %} - -Change to the `/media` directory and create a folder called `hassbackup`. Change the ownership to the user that runs Home Assistant. In this example case, the user and group are both `homeassistant`. +### {% linkable_title Prepare USB Stick %} +Change into it and create a folder called `hassbackup` and change the ownership to the user that runs Home Assistant. In my case group and user are both `homeassistant`. ```bash # cd /media/ @@ -56,10 +54,11 @@ drwxr-xr-x 22 root root 4096 Mar 22 18:37 .. drwxr-xr-x 2 homeassistant homeassistant 4096 Apr 29 10:36 hassbackup drwx------ 2 root root 16384 Apr 29 10:18 lost+found ``` +You can ignore 'lost+found'. ### {% linkable_title Install Dependency %} -The script in the next section uses zip to preserve space on your drive. So we will install zip next. +In order to preserve space on your drive we use zip. Install that too. ```bash /media# apt-get install zip @@ -69,9 +68,9 @@ Building dependency tree Setting up zip (3.0-8) ... ``` -### {% linkable_title Download and Run Script %} +### {% linkable_title Install and run script %} -Become the `homeassistant` user (or whatever user runs Home Assistant). Change to whatever directory you would like the [script](https://gist.github.com/riemers/041c6a386a2eab95c55ba3ccaa10e7b0) placed into and run the following command. +Become the `homeassistant` user and place the following [script](https://gist.github.com/riemers/041c6a386a2eab95c55ba3ccaa10e7b0) to a place of your liking. ```bash # wget https://gist.githubusercontent.com/riemers/041c6a386a2eab95c55ba3ccaa10e7b0/raw/86727d4e72e9757da4f68f1c9d784720e72d0e99/usb_backup.sh @@ -83,7 +82,7 @@ Make the downloaded script executable. # chmod +x usb_backup.sh ``` -Edit the script file using your preferred text editor (use nano if you are not advanced). Change the paths to reflect your configuration, then simply run `./usb_backup.sh`. +Open up the file and change the paths you want to use, then simply run the `./usb_backup.sh`. ```bash $ .homeassistant/extraconfig/shell_code/usb_backup.sh @@ -92,27 +91,26 @@ $ .homeassistant/extraconfig/shell_code/usb_backup.sh [i] Keeping all files no prunning set ``` -### {% linkable_title Set Up Crontab %} - -To automatically backup your configuration on a schedule, you can add a crontab for it as the `homeassistant` user. -Change the path below to the directory where you placed the `usb_backup.sh` and run the following line. This will backup every night at 3 am. +### {% linkable_title Crontab %} +In order for this to automatically make a backup every night at 3 am, you can add a crontab for it as the `homeassistant` user. +Change below path to where you placed the `usb_backup.sh` and run the following line. ```bash (crontab -l 2>/dev/null; echo "0 3 * * * /home/homeassistant/.homeassistant/extraconfig/shell_code/usb_backup.sh") | crontab - ``` -### {% linkable_title Auto Mount the USB Device %} +### {% linkable_title Auto mount %} -NOTE: This does not automatically mount your USB drive at boot. You will need to manually mount your drive after each boot or add a line to your `/etc/fstab` file. +This does not automatically mount your USB drive at boot. You need to do that manually or add a line to your `/etc/fstab` file. -To manually mount a USB drive located at `/dev/sda1`, run the following line: - -```bash -# mount /dev/sda1 /media -``` - -Alternatively, auto-mount the drive by adding the following entry to your `/etc/fstab`: +If your drive is on `/dev/sda1`, you could add an entry to your `/etc/fstab` like so: ```text /dev/sda1 /media ext4 defaults,noatime 0 1 ``` + +Manual step to mount the USB drive: + +```bash +# mount /dev/sda1 /media +``` diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown index 1239eb550a..ee9cb80892 100644 --- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown +++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown @@ -10,11 +10,11 @@ footer: true ---
-If you are using Hass.io or Hassbian, do not use this guide. Instead, use the [DuckDNS add-on](/addons/duckdns/) for Hass.io or the [DuckDNS suite](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/duckdns.md) for Hassbian to automatically maintain a subdomain including HTTPS certificates via Let's Encrypt. +If you are using Hass.io, do not use this guide. Instead, use the [DuckDNS add-on](/addons/duckdns/) to automatically maintain a subdomain including HTTPS certificates via Let's Encrypt.
--Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](/docs/configuration/basic/) page. +
+Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](https://home-assistant.io/docs/configuration/basic/) page.
@@ -22,16 +22,16 @@ This guide was added by mf_social on 16/03/2017 and was valid at the time of wri * You can access your Home Assistant instance across your local network, and access the device that it is on via SSH from your local network. * You know the internal IP address of your router and can access your router's configuration pages. - * You have already set up a password for your Home Assistant instance, following the advice on this page: [http](/docs/configuration/basic/) + * You have already set up a password for your Home Assistant instance, following the advice on this page: [http](https://home-assistant.io/docs/configuration/basic/) * You want to access your Home Assistant instance when you are away from home (ie, not connected to your local network) and secure it with a TLS/SSL certificate. * You have a basic understanding of the phrases I have used so far. * You are not currently running anything on port 80 on your network (you'd know if you were). * If you are not using Home Assistant on a Debian/Raspian/Hassbian system you will be able to convert any of the terminology I use in to the correct syntax for your system. * You understand that this is a 'guide' covering the general application of these things to the general masses and there are things outside of the scope of it, and it does not cover every eventuality (although I have made some notes where people may stumble). Also, I have used some turns of phrase to make it easier to understand for the novice reader which people of advanced knowledge may say is innacurate. My goal here is to get you through this guide with a satisfactory outcome and have a decent understanding of what you are doing and why, not to teach you advanced internet communication protocols. * Each step presumes you have fully completed the previous step successfully, so if you did an earlier step following a different guide, please ensure that you have not missed anything out that may affect the step you have jumped to, and ensure that you adapt any commands to take in to account different file placements from other guides. - + Steps we will take: - + - 0 - Gain a basic level of understanding around IP addresses, port numbers and port forwarding - 1 - Set your device to have a static IP address - 2 - Set up port forwarding without TLS/SSL and test connection @@ -42,48 +42,48 @@ Steps we will take: - 7 - Set up a sensor to monitor the expiry date of the certificate - 8 - Set up an automatic renewal of the TLS/SSL certificate - 9 - Set up an alert to warn us if something went wrong - + ### {% linkable_title 0 - Gain a basic level of understanding around IP addresses, port numbers and port forwarding %} - + An IP address is a bit like a phone number. When you access your Home Assistant instance you type something similar to 192.168.0.200:8123 in to your address bar of your browser. The bit before the colon is the IP address (in this case 192.168.0.200) and the bit after is the port number (in this case 8123). When you SSH in to the device running Home Assistant you will use the same IP address, and you will use port 22. You may not be aware that you are using port 22, but if you are using Putty look in the box next to where you type the IP address, you will see that it has already selected port 22 for you. - + So, if an IP address is like a phone number, a port number is like an extension number. An analogy would be if you phone your local doctors on 192-1680-200 and the receptionist answers, you ask to speak to Dr. Smith and she will put you through to extension 8123, which is the phone Dr. Smith is sitting at. The doctors surgery is the device your Home Assistant is running on, Dr. Smith is your Home Assistant. Thusly, your Home Assistant instance is 'waiting for your call' on port 8123, at the device IP 192.168.0.200 . - + Now, to speak to the outside world your connection goes through a router. Your router will have two IP addresses. One is the internal network number, most likely 192.168.0.1 in my example, and an external IP address that incoming traffic is sent to. In the example of calling the doctors, the external IP is your telephone number's area code. - + So, when we want to connect to our Home Assistant instance from outside our network we will need to call the correct extension number, at the correct phone number, in the correct area code. - + We will be looking for a system to run like this (in this example I will pretend our external IP is 12.12.12.12): - + ```text Outside world -> 12.12.12.12:8123 -> your router -> 192.168.0.200:8123 ``` Sounds simple? It really is except for two small, but easy to overcome, complications: - + * IP addresses are often dynamically allocated, so they can change. * Because of the way the internet works you cannot chain IP addresses together to get from where you are, to where you want to go. - + To get around the issue of changing IP addresses we must remember that there are two IP addresses affected. Your external one (which we will 'call' to get on to your network from the internet) and your internal one (192.168.0.200 in the example I am currently using). - + So, we can use a static IP to ensure that whenever our device running Home Assistant connects to our router it always uses the same address. This way our internal IP never changes. This is covered in step 1 below. - + We then have no control over our external IP, as our Service Provider will give us a new one at random intervals. To fix this we will use a service called DuckDNS which will give us a name for our connection (something like examplehome.duckdns.org) and behind the scenes will continue to update your external IP. So no matter how many times the IP address changes, typing examplehome.duckdns.org in to our browser will convert to the correct, up-to-date, IP address. This is covered in step 3 below. - + To get around the issue of not being able to chain the IP addresses together (I can't say I want to call 12:12:12:12 and be put through to 192.168.0.200, and then be put through to extension 8123) we use port forwarding. Port forwarding is the process of telling your router which device to allow the outside connection to speak to. In the doctors surgery example, port forwarding is the receptionist. This takes a call from outside, and forwards it to the correct extension number inside. It is important to note that port forwarding can forward an incoming request for one port to a different port on your internal network if you so choose, and we will be doing this later on. The end result being that when we have our TSL/SSL certificate our incoming call will be requesting port 443 (because that is the SSL port, like the SSH port is always 22), but our port forwarding rule will forward this to our HA instance on port 8123. When this guide is completed we will run something like this: - + ```text Outside world -> https://examplehome.duckdns.org -> 12.12.12.12:443 -> your router -> 192.168.0.200:8123 ``` So, let's make it happen... ### {% linkable_title 1 - Set your device to have a static IP address %} - + Whenever a device is connected to a network it has an IP address. This IP address is often dynamically assigned to the device on connection. This means there are occasions where the IP address you use to access Home Assistant, or SSH in to the device running Home Assistant, may change. Setting a static IP address means that the device will always be on the same address. - + SSH in to your system running Home Assistant and login. - + Type the following command to list your network interfaces: - + ```bash $ ifconfig ``` @@ -94,17 +94,17 @@ You will receive an output similar to the image below:
Screenshot
-
+
Make a note of the interface name and the IP address you are currently on. In the picture it is the wireless connection that is highlighted, but with your setup it may be the wired one (eth0 or similar), make sure you get the correct information.
-
+
Then type the following command to open the text file that controls your network connection:
-```bash
+```bash
$ sudo nano /etc/dhcpcd.conf
```
At the bottom of the file add the following lines:
-
+
```text
interface wlan0 <----- or the interface you just wrote down.
@@ -113,7 +113,7 @@ static routers=192.168.0.1 <---- Your router's IP address
static domain_name_servers=192.168.0.1 <---- Your router's IP address
```
-It is important to note that the first three bytes of your static IP address and your router's IP address should be the same, eg:
+It is important to note that the first three bits of your static IP address and your router's IP address should be the same, eg:
```text
Router: 192.168.0.1
@@ -195,17 +195,13 @@ In the domains section pick a name for your subdomain, this can be anything you
The URL you will be using later to access your Home Assistant instance from outside will be the subdomain you picked, followed by duckdns.org . For our example we will say our URL is examplehome.duckdns.org
-Set up Home Assistant to keep your DuckDNS URL and external IP address in sync. In your `configuration.yaml` file add the following:
+On the top left of duckdns.org select the install option. Then pick your operating system from the list. In our example we will use a Raspberry Pi. In the dropdown box select the URL you just created.
-```yaml
-duckdns:
- domain: examplehome
- access_token: abcdefgh-1234-abcd-1234-abcdefgh
-```
+Duckdns.org will now generate personalised instructions for you to follow so that your device can update their website every time your IP address changes. Carefully follow the instructions given on duckdns.org to set up your device.
-The access token is available on your DuckDNS page. Restart Home Assistant after the change.
+At the end of the instructions DuckDNS will suggest you set up port forwarding. No need, we have already done this in step 2.
-What you have now done is set up DuckDNS so that whenever you type examplehome.duckdns.org in to your browser it will convert that to your router's external IP address. Your external IP address will always be up to date because Homeassistant will update DuckDNS every time it changes.
+What you have now done is set up DuckDNS so that whenever you type examplehome.duckdns.org in to your browser it will convert that to your router's external IP address. Your external IP address will always be up to date because your device running Home Assistant will update DuckDNS every time it changes.
Now type your new URL in to your address bar on your browser with port 8123 on the end:
@@ -255,7 +251,7 @@ $ sudo adduser hass sudo
If you did not already log in as the user that currently runs Home Assistant, change to that user (usually `hass` or `homeassistant` - you may have used a command similar to this in the past):
```bash
-$ sudo su -s /bin/bash hass
+$ sudo su -s /bin/bash hass
```
Make sure you are in the home directory for the Home Assistant user:
@@ -276,7 +272,7 @@ $ chmod a+x certbot-auto
You might need to stop Home Assistant before continuing with the next step. You can do this via the Web-UI or use the following command if you are running on Hassbian:
```text
-$ sudo systemctl stop home-assistant@homeassistant.service
+$ sudo systemctl stop home-assistant@homeassistant.service
```
You can restart Home Assistant after the next step using the same command and replacing `stop` with `start`.
@@ -340,8 +336,8 @@ http:
ssl_key: /etc/letsencrypt/live/examplehome.duckdns.org/privkey.pem
base_url: examplehome.duckdns.org
```
-
-You may wish to set up other options for the [http](/components/http/) component at this point, these extra options are beyond the scope of this guide.
+
+You may wish to set up other options for the [http](https://home-assistant.io/components/http/) component at this point, these extra options are beyond the scope of this guide.
Save the changes to configuration.yaml. Restart Home Assistant.
@@ -367,7 +363,11 @@ https://YOUR-HA-IP:8123
Some cases such as this are where your router does not allow 'loopback' or where there is a problem with incoming connections due to technical failure. In these cases you can still use your internal connection and safely ignore the warnings.
-If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL. Instructions for creating your new webapp can be found [here](/docs/frontend/mobile/).
+If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL. Instructions for creating your new webapp can be found here:
+
+```text
+https://home-assistant.io/docs/frontend/mobile/
+```
All done? Accessing your Home Assistant from across the world with your DuckDNS URL and a lovely secure logo on your browser? Ace! Now let's clean up our port forwards so that we are only exposing the parts of our network that are absolutely necessary to the outside world.
@@ -387,11 +387,11 @@ You are now part of one of two groups:
* If you have BOTH rules you are able to set up auto renewals of your certificates using port 80 and the standard http challenge, as performed above.
* If you only have one, you are still able to set up auto renewals of your certificates, but will have to specify additional options when renewing that will temporarily stop Home Assistant and use port 8123 for certificate renewal.
-
+
Please remember whether you are a ONE-RULE person or a BOTH-RULE person for step 8!
-
+
Let's Encrypt certificates only last for 90 days. When they have less than 30 days left they can be renewed. Renewal is a simple process.
-
+
Move on to step 7 to see how to monitor your certificates expiry date, and be ready to renew your certificate when the time comes.
### {% linkable_title 7 - Set up a sensor to monitor the expiry date of the certificate %}
@@ -402,9 +402,9 @@ Setting a sensor to read the number of days left on your TLS/SSL certificate bef
* You can set automations based on the number of days left
* You can set alerts to notify you if your certificate has not been renewed and is coming close to expiry.
* If you cannot set up automatic renewals due to your ISP blocking port 80, you will have timely reminders to complete the process manually.
-
+
If you do not wish to set up a sensor you can skip straight to step 8 to learn how to update your certificates.
-
+
The sensor will rely on a command line program that needs to be installed on your device running Home Assistant. SSH in to the device and run the following commands:
```bash
@@ -442,33 +442,33 @@ If you are a ONE-RULE person (from step 6), you can automatically renew your cer
If you are a TWO-RULE person (from step 6), you can automatically renew your certificate using a `http-01` challenge and port 80.
There are a number of options for automating the renewal process:
-
+
#### Option 1:
Your certificate can be renewed as a 'cron job' - cron jobs are background tasks run by the computer at specified intervals (and are totally independent of Home Assistant). Defining cron is outside of the scope of this guide but you will have had dealings with `crontab` when setting up DuckDNS in step 3
-
+
To set a cron job to run the script at regular intervals:
-
+
* SSH in to your device running Home Assistant.
* Change to your Home Assistant user (command similar to):
-
+
```bash
$ sudo su -s /bin/bash hass
```
-
+
* Open the crontab:
-
+
```bash
$ crontab -e
```
-
+
* If you are a TWO-RULE Person: Scroll to the bottom of the file and paste in the following line
-
+
```text
30 2 * * 1 ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
```
* If you are a ONE-RULE Person: Scroll to the bottom of the file and paste in the following line
-
+
```text
30 2 * * 1 ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges tls-sni-01 --tls-sni-01-port 8123 --pre-hook "sudo systemctl stop home-assistant@homeassistant.service" --post-hook "sudo systemctl start home-assistant@homeassistant.service"
```
@@ -478,17 +478,17 @@ $ crontab -e
3. We define pre-hooks and post-hooks that stop our Home Assistant service before certbot runs, freeing port 8123 for certificate renewal, and restart Home Assistant after renewal is complete.
* Save the file and exit
-
-
+
+
#### Option 2:
You can set an automation in Home Assistant to run the certbot renewal script.
-
+
Add the following sections to your configuration.yaml if you are a TWO-RULE person
-```yaml
-shell_command:
+```yaml
+shell_command:
renew_ssl: ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
-
+
automation:
- alias: 'Auto Renew SSL Cert'
trigger:
@@ -502,34 +502,34 @@ If you are a ONE-RULE person, replace the `certbot-auto` command above with `~/c
#### Option 3:
You can manually update the certificate when your certificate is less than 30 days to expiry.
-
-To manually update:
-
+
+To manually update:
+
* SSH in to your device running Home Assistant.
* Change to your Home Assistant user (command similar to):
-
+
```bash
$ su - s /bin/bash hass
```
-
+
* Change to your certbot folder
-
+
```bash
$ cd ~/certbot/
```
* Run the renewal command
-
+
```bash
$ ./certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
```
* If you are a ONE-RULE person, replace the `certbot-auto` command above with `~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges tls-sni-01 --tls-sni-01-port 8123 --pre-hook "sudo systemctl stop home-assistant@homeassistant.service" --post-hook "sudo systemctl start home-assistant@homeassistant.service"`
-
+
So, now were all set up. We have our secured, remotely accessible Home Assistant instance and we're on track for keeping our certificates up to date. But what if something goes wrong? What if the automation didn't fire? What if the cron job forgot to run? What if the dog ate my homework? Read on to set up an alert so you can be notified in plenty of time if you need to step in and sort out any failures.
-
+
### {% linkable_title 9 - Set up an alert to warn us if something went wrong. %}
-
+
We set up our automatic renewal of our certificates and whatever method we used the certificate should be renewed on or around 30 days before it expires. But what if a week later it still hasn't been? This alert will go off if the expiry time on the certificate gets down to 21 days. This will give you 3 weeks to fix the problem, get your new certificate installed and get another 90 days of secure Home Assistant connections in play.
In your `configuration.yaml` add the following automation, adding your preferred notification platform where appropriate:
@@ -538,15 +538,15 @@ In your `configuration.yaml` add the following automation, adding your preferred
automation:
- alias: 'SSL expiry notification'
trigger:
- platform: numeric_state
- entity_id: sensor.ssl_cert_expiry
- below: 21
- action:
- service: notify.[your_notification_preference]
- data:
- message: 'Warning - SSL certificate expires in 21 days and has not been automatically renewed'
+ platform: numeric_state
+ entity_id: sensor.ssl_cert_expiry
+ below: 21
+ action:
+ service: notify.[your_notification_preference]
+ data:
+ message: 'Warning - SSL certificate expires in 21 days and has not been automatically renewed'
```
-
+
If you receive this warning notification, follow the steps for a manual update from step 8. Any error messages received at that point can be googled and resolved. If the manual update goes without a hitch there may be something wrong with your chosen method for automatic updates, and you can start troubleshooting from there.
So, that's it. We've taken a Home Assistant instance that was only reachable on the local network, made it accessible from the internet, secured it, and set up a system to ensure that it always stays secure. Well done, go and treat yourself to a cookie!
diff --git a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown b/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
index 2aab9deb6d..53736e0693 100644
--- a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
+++ b/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
@@ -11,8 +11,8 @@ redirect_from: /cookbook/tls_self_signed_certificate/
---
If your Home Assistant instance is only accessible from your local network you can still protect the communication between your browsers and the frontend with SSL/TLS.
-[Let's encrypt]({{site_root}}/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/) will only work if you have a DNS entry and remote access is allowed.
-The solution is to use a self-signed certificate. As you most likely don't have a certification authority (CA) your browser will complain about the security. If you have a CA then this will not be an issue.
+[Let's encrypt]({{site_root}}/blog/2015/12/13/setup-encryption-using-lets-encrypt/) will only work if you have a DNS entry and remote access is allowed.
+The solution is to use a self-signed certificate. As you most likely don't have a certification authority (CA) your browser will conplain about the security. If you have a CA then this will not be an issue.
To create a certificate locally, you need the [OpenSSL](https://www.openssl.org/) command-line tool.
diff --git a/source/_docs/ecosystem/hadashboard.markdown b/source/_docs/ecosystem/hadashboard.markdown
index 87c06d166d..226b6906d9 100755
--- a/source/_docs/ecosystem/hadashboard.markdown
+++ b/source/_docs/ecosystem/hadashboard.markdown
@@ -10,7 +10,7 @@ footer: true
redirect_from: /ecosystem/hadashboard/
---
-HADashboard is a modular, skinnable dashboard for [Home Assistant](/) that is intended to be wall mounted, and is optimized for distance viewing.
+HADashboard is a modular, skinnable dashboard for [Home Assistant](https://home-assistant.io/) that is intended to be wall mounted, and is optimized for distance viewing.
diff --git a/source/_docs/ecosystem/hass-configurator.markdown b/source/_docs/ecosystem/hass-configurator.markdown
index 3087d6b6b2..c9fac261ec 100644
--- a/source/_docs/ecosystem/hass-configurator.markdown
+++ b/source/_docs/ecosystem/hass-configurator.markdown
@@ -12,7 +12,7 @@ redirect_from: /ecosystem/hass-configurator/
### {% linkable_title Configuration UI for Home Assistant %}
-Since there currently is no nice way to edit the yaml-files Home Assistant is using through the frontend, here is a small webapp that hopefully makes the configuration easier. It is a customized and embedded [Ace editor](https://ace.c9.io/), which has syntax highlighting for yaml, the format used for Home Assistants configuration files. There is an integrated file browser to select whatever file you want to edit. When you're done with editing the file, click the save-button and it will replace the original.
+Since there currently is no nice way to edit the yaml-files Home Assistant is using through the frontend, here is a small webapp that hopefully makes the configuration easier. It is a customized and embedded [Ace editor](https://ace.c9.io/), which has syntax highlighting for yaml, the format used for Home Assistants configuration files. There is an integrated file browser to select whatever file you want to edit. When you're done with editing the file, click the save-button and it will replace the original.
Essentially this is a browser-based alternative to modifying your configuration through SSH, Windows + SMB, Github etc..
@@ -38,7 +38,7 @@ This tool allows you to browse your filesystem and modify files. So be careful w Consider running the configurator as a user with limited privileges to limit possible damage.
### {% linkable_title Installation (Linux, OS X) %} -There are no dependencies on Python modules that are not part of the standard library. And all the fancy JavaScript libraries are loaded from CDN (which means this doesn't work when you're offline). +There are no dependencies on Python modules that are not part of the standard library. And all the fancy JavaScript libraries are loaded from CDN (which means this doesn't work when you're offline). - Copy [configurator.py](https://github.com/danielperna84/hass-configurator/blob/master/configurator.py) to your Home Assistant configuration directory (e.g `/home/homeassistant/.homeassistant`): `wget https://raw.githubusercontent.com/danielperna84/hass-configurator/master/configurator.py` - Make it executable: `sudo chmod 755 configurator.py` - (Optional) Set the `GIT` variable in configurator.py to `True` if [GitPython](https://gitpython.readthedocs.io/) is installed on your system. This is required if you want to make use of the Git integration. @@ -46,8 +46,8 @@ There are no dependencies on Python modules that are not part of the standard li - To terminate the process do the usual `CTRL+C`, maybe once or twice ### {% linkable_title Configuration %} -Near the top of the `configurator.py`-file you will find some global variables you can change to customize the configurator. If you are unfamiliar with Python: when setting variables of the type _string_, you have to write that within quotation marks. The default settings are fine for just checking out the configurator quickly. With more customized setups you should change some settings though. -To keep your settings across updates it is also possible to save settings in an external file. In that case copy [settings.conf](https://github.com/danielperna84/hass-configurator/blob/master/settings.conf) wherever you like and append the full path to the file to the command when starting the configurator. e.g., `sudo .configurator.py /home/homeassistant/.homeassistant/mysettings.conf`. This file is in JSON format. So make sure it has a valid syntax (you can set the editor to JSON to get syntax highlighting for the settings). The major difference to the settings in the py-file is, that `None` becomes `null`. +Near the top of the `configurator.py`-file you will find some global variables you can change to customize the configurator. If you are unfamiliar with Python: when setting variables of the type _string_, you have to write that within quotation marks. The default settings are fine for just checking out the configurator quickly. With more customized setups you should change some settings though. +To keep your settings across updates it is also possible to save settings in an external file. In that case copy [settings.conf](https://github.com/danielperna84/hass-configurator/blob/master/settings.conf) wherever you like and append the full path to the file to the command when starting the configurator. E.g. `sudo .configurator.py /home/homeassistant/.homeassistant/mysettings.conf`. This file is in JSON format. So make sure it has a valid syntax (you can set the editor to JSON to get syntax highlighting for the settings). The major difference to the settings in the py-file is, that `None` becomes `null`. #### LISTENIP (string) The IP the service is listening on. By default it is binding to `0.0.0.0`, which is every interface on the system. @@ -66,22 +66,22 @@ Set credentials in the form of `"username:password"` if authentication should be #### ALLOWED_NETWORKS (list) Limit access to the configurator by adding allowed IP addresses / networks to the list, e.g `ALLOWED_NETWORKS = ["192.168.0.0/24", "172.16.47.23"]` #### BANNED_IPS (list) -List of statically banned IP addresses, e.g., `BANNED_IPS = ["1.1.1.1", "2.2.2.2"]` +List of statically banned IP addresses, e.g. `BANNED_IPS = ["1.1.1.1", "2.2.2.2"]` #### BANLIMIT (integer) Ban IPs after `n` failed login attempts. Restart the service to reset banning. The default of `0` disables this feature. `CREDENTIALS` has to be set for this to work. #### IGNORE_PATTERN (list) -Files and folders to ignore in the UI, e.g., `IGNORE_PATTERN = [".*", "*.log", "__pycache__"]`. +Files and folders to ignore in the UI, e.g. `IGNORE_PATTERN = [".*", "*.log", "__pycache__"]`. #### DIRSFIRST (bool) If set to `True`, directories will be displayed at the top of the filebrowser. #### GIT (bool) Set this variable to `True` to enable Git integration. This feature requires [GitPython](https://gitpython.readthedocs.io) to be installed on the system that is running the configurator. For technical reasons this feature can not be enabled with the static settings file. - -__Note regarding `ALLOWED_NETWORKS`, `BANNED_IPS` and `BANLIMIT`__: + +__Note regarding `ALLOWED_NETWORKS`, `BANNED_IPS` and `BANLIMIT`__: The way this is implemented works in the following order: 1. (Only if `CREDENTIALS` is set) Check credentials - - Failure: Retry `BANLIMIT` times, after that return error 420 (unless you try again without any authentication headers set, e.g., private tab of your browser) + - Failure: Retry `BANLIMIT` times, after that return error 420 (unless you try again without any authentication headers set, e.g. private tab of your browser) - Success: Continue 2. Check if client IP address is in `BANNED_IPS` - Yes: Return error 420 @@ -91,7 +91,7 @@ The way this is implemented works in the following order: - Yes: Continue and display UI of configurator ### {% linkable_title 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](https://home-assistant.io/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. An example configuration would look like this: ```yaml @@ -107,11 +107,11 @@ Be careful when setting up port forwarding to the configurator while embedding i ### {% linkable_title Daemonizing / Keeping the configurator running %} Since the configurator script on its own is no service, you will have to take some extra steps to keep it running. Here are five options (for Linux), but there are more, depending on your usecase. -1. Fork the process into the background with the command: +1. Fork the process into the background with the command: `nohup sudo ./configurator.py &` -2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. -3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.supervisor) would be an example configuration you could use to control the configurator. -4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](/docs/hassbian/). +2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](https://home-assistant.io/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. +3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.supervisor) would be an example configuration you could use to control the configurator. +4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](https://home-assistant.io/docs/hassbian/). 5. A tool called [screen](http://ss64.com/bash/screen.html) (alternative to tmux). If it's not already installed on your system, you can do `sudo apt-get install screen` or `sudo yum install screen` to get it. When it's installed, start a screen session by executing `screen`. Then navigate to your Home Assistant directory and start the configurator like described above. Put the screen session into the background by pressing `CTRL+A` and then `CTRL+D`. It is now safe to disconnect from your SSH session. To resume the screen session, log in to your machine and execute `screen -r`. diff --git a/source/_docs/ecosystem/ios.markdown b/source/_docs/ecosystem/ios.markdown index 027fe50323..6959ade8f1 100644 --- a/source/_docs/ecosystem/ios.markdown +++ b/source/_docs/ecosystem/ios.markdown @@ -21,7 +21,7 @@ The app is available on the iOS App Store in every country that Apple supports.-## {% linkable_title Basic requirements %} +## Basic requirements * iOS device running at least iOS 9, but iOS 10 is greatly preferred. * Home Assistant 0.42.4 or higher for push notification support. @@ -33,7 +33,7 @@ Loading the `ios` component will also load the [`device_tracker`][device-tracker ## {% linkable_title Setup %} -### {% linkable_title Automated Setup %} +### Automated Setup The `ios` component will automatically be loaded under the following circumstances: @@ -44,7 +44,7 @@ Automated discovery and component loading only happens at first install of the a After the first automated setup you need to add `ios:` to your configuration so that the component loads by default even after restarting Home Assistant. -### {% linkable_title Manual Setup %} +### Manual Setup You may also manually load the `ios` component by adding the following to your configuration: diff --git a/source/_docs/ecosystem/ios/integration.markdown b/source/_docs/ecosystem/ios/integration.markdown index b6c27dd437..3bd3791ebb 100644 --- a/source/_docs/ecosystem/ios/integration.markdown +++ b/source/_docs/ecosystem/ios/integration.markdown @@ -18,7 +18,7 @@ Query parameters are passed as a dictionary in the call. Example: `homeassistant://call_service/device_tracker.see?entity_id=device_tracker.entity` ## Fire event -You can create an [event trigger](/docs/automation/trigger/#event-trigger) and fire the event. +You can create an [event trigger](https://home-assistant.io/docs/automation/trigger/#event-trigger) and fire the event. Example: `homeassistant://fire_event/custom_event?entity_id=MY_CUSTOM_EVENT` diff --git a/source/_docs/ecosystem/ios/notifications.markdown b/source/_docs/ecosystem/ios/notifications.markdown index c1eee576e3..a4a025907c 100644 --- a/source/_docs/ecosystem/ios/notifications.markdown +++ b/source/_docs/ecosystem/ios/notifications.markdown @@ -12,7 +12,7 @@ redirect_from: /ecosystem/ios/notifications/ The `ios` notify platform enables sending push notifications to the Home Assistant iOS app. -The 'ios' component will automatically load the notify service. +The 'ios' component will automatically load the notify service. The service component can be called using `service: notify.ios_
-You will at least need nginx >= 1.3.13, as WebSocket support is required for the reverse proxy. -
- ### {% linkable_title 3. Obtain an SSL certificate %} There are two ways of obtaining an SSL certificate. @@ -32,7 +28,7 @@ There are two ways of obtaining an SSL certificate. #### {% linkable_title Using Let's Encrypt %} If you purchased your own domain, you can use https://letsencrypt.org/ to obtain a free, publicly trusted SSL certificate. This will allow you to work with services like IFTTT. Download and install per the instructions online and get a certificate using the following command. -```bash +``` $ sudo ./letsencrypt-auto certonly --standalone -d example.com -d www.example.com ``` @@ -79,13 +75,14 @@ $ sudo ln ../sites-available/hass default Double check this configuration to ensure all settings are correct and start nginx. + ### {% linkable_title 8. Port forwarding. %} Forward ports 443 and 80 to your server on your router. Do not forward port 8123. ### {% linkable_title NGINX Config %} -```text +``` map $http_upgrade $connection_upgrade { default upgrade; '' close; diff --git a/source/_docs/ecosystem/scenegen.markdown b/source/_docs/ecosystem/scenegen.markdown index 37d2534b08..3cf1e1b03c 100644 --- a/source/_docs/ecosystem/scenegen.markdown +++ b/source/_docs/ecosystem/scenegen.markdown @@ -10,7 +10,7 @@ footer: true redirect_from: /ecosystem/scenegen/ --- -Scenegen is a scene generation tool for [Home Assistant](/) home automation software. It creates scenes by example, by reading the current states of devices and outputting a corresponding scene. Scenegen is written in python using Home Assistant's RESTFul API so can be run from anywhere. It currently supports lights and switches only. +Scenegen is a scene generation tool for [Home Assistant](https://home-assistant.io/) home automation software. It creates scenes by example, by reading the current states of devices and outputting a corresponding scene. Scenegen is written in python using Home Assistant's RESTFul API so can be run from anywhere. It currently supports lights and switches only. ## {% linkable_title Installation %} diff --git a/source/_docs/ecosystem/synology.markdown b/source/_docs/ecosystem/synology.markdown index c5c436da58..099ea41ef0 100644 --- a/source/_docs/ecosystem/synology.markdown +++ b/source/_docs/ecosystem/synology.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Synology" -description: "Instructions on how to get Home Assistant up and running on Synology" +description: "Instructions how to get Home Assistant up and running on Synology" release_date: 2016-12-07 15:00:00 -0500 sidebar: true comments: false diff --git a/source/_docs/frontend/browsers.markdown b/source/_docs/frontend/browsers.markdown index 2454f5989a..611b8586ae 100644 --- a/source/_docs/frontend/browsers.markdown +++ b/source/_docs/frontend/browsers.markdown @@ -37,7 +37,7 @@ We would appreciate if you help to keep this page up-to-date and add feedback. | Browser | Release | State | Comments | | :-------------------- |:---------------|:-----------|:-------------------------| -| [Firefox] | 59.0 | works | | +| [Firefox] | 57.0 | works | | | [Midori] | 0.5.11 | works | | | [Chromium] | 63.0.3239.108 | works | | | [Conkeror] | 1.0.2 | works | | diff --git a/source/_docs/frontend/mobile.markdown b/source/_docs/frontend/mobile.markdown index d7342115b7..3a2c1af740 100644 --- a/source/_docs/frontend/mobile.markdown +++ b/source/_docs/frontend/mobile.markdown @@ -10,7 +10,7 @@ footer: true redirect_from: /getting-started/mobile/ --- -Home Assistant has [a companion app for iOS](/docs/ecosystem/ios/). +Home Assistant has [a companion app for iOS](https://home-assistant.io/docs/ecosystem/ios/). On both Android and iOS, you can add the Home Assistant "web app" to your homescreen as if it was native (Home Assistant leverages the W3C [manifest.json](https://w3c.github.io/manifest/) support). diff --git a/source/_docs/installation.markdown b/source/_docs/installation.markdown index 16380e6837..4b54abe2d3 100644 --- a/source/_docs/installation.markdown +++ b/source/_docs/installation.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Installation of Home Assistant" -description: "Instructions on how to install Home Assistant to launch on start." +description: "Instructions how to install Home Assistant to launch on start." date: 2017-02-15 08:00 sidebar: true comments: false @@ -14,7 +14,7 @@ redirect_from: /getting-started/installation/ Beginners should check our [Getting started guide](/getting-started/) first. This is for users that require advanced installations. -Home Assistant provides multiple ways to be installed. A requirement is that you have [Python 3.5.3 or later](https://www.python.org/downloads/) installed. +Home Assistant provides multiple ways to be installed. A requirement is that you have [Python 3.5+](https://www.python.org/downloads/) installed. diff --git a/source/_includes/asides/developers_navigation.html b/source/_includes/asides/developers_navigation.html new file mode 100644 index 0000000000..0f42206817 --- /dev/null +++ b/source/_includes/asides/developers_navigation.html @@ -0,0 +1,135 @@ +
[MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](/components/mqtt/) will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn't care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn't matter if the data is coming from a human, a web service, or a device.
+ [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt/) will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn't care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn't matter if the data is coming from a human, a web service, or a device.
-A great example is shown in a [Laundry Automation](/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) post in this blog.
+A great example is shown in a [Laundry Automation](https://home-assistant.io/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) post in this blog.
This post will give you a small overview of some other possibilities on how to use MQTT with Home Assistant.
@@ -34,7 +34,7 @@ sensor:
state_topic: "home-assistant/fabian/mood"
```
-After a restart of Home Assistant the "Mood" sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the [MQTT component](/components/mqtt/) or the [MQTT sensor](/components/sensor.mqtt/) documentation.
+After a restart of Home Assistant the "Mood" sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the [MQTT component](https://home-assistant.io/components/mqtt/) or the [MQTT sensor](https://home-assistant.io/components/sensor.mqtt/) documentation.
Now we can set the mood. The commandline tool (`mosquitto_pub`) which is shipped with `mosquitto` is used to send an MQTT message.
diff --git a/source/_posts/2015-11-22-survey-november-2015.markdown b/source/_posts/2015-11-22-survey-november-2015.markdown
index 38a84c00a3..09efee533d 100644
--- a/source/_posts/2015-11-22-survey-november-2015.markdown
+++ b/source/_posts/2015-11-22-survey-november-2015.markdown
@@ -21,7 +21,7 @@ Of course most users are running with the [automation](/getting-started/automati
The [Alarm control panels](/components/alarm_control_panel/) and the [camera component](/components/camera/) are both used by around one third of the participants of the survey. It's safe to say that they cover a niche, but they will gain momentum when people discover how they can build alarm systems with Home Assistant.
-[Philips Hue](/components/light.hue/) is the "winner" in the light category closely followed by [MQTT lights](components/light.mqtt/). [Google Cast](/components/media_player.cast/) and [ Plex](/components/media_player.plex/) are the top media player platforms. [Pushbullet](/components/notify.pushbullet/) is by far the most-used [notification platform](/components/notify/). If you followed the recent efforts to improve this platform it's comprehensible.
+[Philips Hue](/components/light.hue/) is the "winner" in the light category closely followed by [MQTT lights](components/light.mqtt/). [Google Cast](/components/media_player.cast/) and [ Plex](/components/media_player.plex/) are the top media player platforms. [Pushbullet](/components/notify.pushbullet/) is by far the most-used [notification platform](https://home-assistant.io/components/notify/). If you followed the recent efforts to improve this platform it's comprehensible.
It's interesting to see that most of the sensor, switch, and thermostat platforms are used. A lot of people seem to be interested in the weather data provided by the [Forecast sensor](/components/sensor.forecast/). The MQTT sensors and switches are deployed in almost 50% of all Home Assistant setups.
@@ -86,6 +86,6 @@ It's interesting to see that most of the sensor, switch, and thermostat platform
Thermostats
-The conclusion is that [MQTT](http://mqtt.org/) is popular in almost every section from Alarm Control Panel, presence detection with [owntracks](http://owntracks.org/), sensors and switches, and now even for lights.
+The conclusion is that [MQTT](http://mqtt.org/) is popular in almost every section from Alarm Control Panel, presence detection with [owntracks](http://owntracks.org/), sensors and switches, and now even for lights.
The interpretation of the data is up to you. Again, thanks for participating in this survey.
diff --git a/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown b/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown
index a9deb4a4d1..2420da0399 100644
--- a/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown
+++ b/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown
@@ -169,7 +169,7 @@ homeassistant:
- mqtt
```
-This will start home-assistant, MQTT, and the Bridge, in dependency order. All config can reference the name of the docker container instead of using IP addresses (e.g., mqtt for the broker host in Home Assistant).
+This will start home-assistant, MQTT, and the Bridge, in dependency order. All config can reference the name of the docker container instead of using IP addresses (e.g. mqtt for the broker host in Home Assistant).
### How it works
diff --git a/source/_posts/2016-02-28-steam-d-link-smart-plugs-and-neurio-energy-sensors.markdown b/source/_posts/2016-02-28-steam-d-link-smart-plugs-and-neurio-energy-sensors.markdown
index 3822349f8b..767045c1ab 100644
--- a/source/_posts/2016-02-28-steam-d-link-smart-plugs-and-neurio-energy-sensors.markdown
+++ b/source/_posts/2016-02-28-steam-d-link-smart-plugs-and-neurio-energy-sensors.markdown
@@ -69,7 +69,7 @@ It's been another two weeks which means it's time for release: 0.14!
[rollershutter.command_line]: /components/rollershutter.command_line/
[Steam]: /components/sensor.steam_online/
[Wink]: /components/binary_sensor.wink/
-[the cookbook]: /cookbook/python_component_simple_alarm/
+[the cookbook]: https://home-assistant.io/cookbook/python_component_simple_alarm/
[script]: /components/script/
[Wemo component]: /components/wemo/
[switch.cmd]: /components/switch.command_line/
diff --git a/source/_posts/2016-04-17-updated-documentation.markdown b/source/_posts/2016-04-17-updated-documentation.markdown
index ae1c4371f2..e3ef6cf9a0 100644
--- a/source/_posts/2016-04-17-updated-documentation.markdown
+++ b/source/_posts/2016-04-17-updated-documentation.markdown
@@ -14,7 +14,7 @@ One of the main complaints that we receive is something along the lines "I read
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and [called it a website]. Back then we had a whopping [11 components](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown).
-As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
+As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
Today it has been almost 1.5 years since we started the website. We now have [264 components and platforms] under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
diff --git a/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown b/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown
index 8a1a8dae12..465e5278a2 100644
--- a/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown
+++ b/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown
@@ -26,7 +26,7 @@ Luckily, OwnTracks supports iBeacons so I could use them to make presence detect
### {% linkable_title Getting Started %}
-To do this you first need to set up [MQTT] and [OwnTracks] in Home Assistant - and make sure that HA can track your phone.
+To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - and make sure that HA can track your phone.
[MQTT]: /components/mqtt/#picking-a-broker
[OwnTracks]: /components/device_tracker.owntracks/
@@ -57,7 +57,7 @@ Once you’ve created the zone - you need to restart HA. The next step is:-
1. Go to the OwnTracks app on your phone
2. Touch the `Regions` menu at the bottom of the screen
3. Touch the `+` symbol at the top right of the screen
-4. Give the beacon a name e.g., `-drive` ’(start the name with a `-` see below for the reason)
+4. Give the beacon a name e.g. `-drive` ’(start the name with a `-` see below for the reason)
5. Turn Share to `On`
6. Skip the `Circular Region` section
7. Enter the `UUID` of your beacon - this may be written on your beacon - or you can copy it from the management app that came with your iBeacon device. It’s a long number – so it’s easier to copy if you can!
@@ -120,7 +120,7 @@ Presence tracking sounds easy - and it's an important part of Home Automation. T
You can find out more about configuring the OwnTracks application and beacons [here](http://owntracks.org/booklet/features/beacons/)
-There is information about configuring Homeassistant to use beacons [here](/components/device_tracker.owntracks/)
+There is information about configuring Homeassistant to use beacons [here](https://home-assistant.io/components/device_tracker.owntracks/)
#### {% linkable_title Connections and disconnecting %}
diff --git a/source/_posts/2016-05-18-why-we-use-polymer.markdown b/source/_posts/2016-05-18-why-we-use-polymer.markdown
index 68ff5f74c3..8f198665c1 100644
--- a/source/_posts/2016-05-18-why-we-use-polymer.markdown
+++ b/source/_posts/2016-05-18-why-we-use-polymer.markdown
@@ -40,5 +40,5 @@ So there it is, the reason why we use Polymer.
[ha-rn]: https://github.com/balloob/home-assistant-react-native-ios
[tools-js]: https://github.com/home-assistant/home-assistant-polymer#building-the-app
[material design for free]: https://elements.polymer-project.org/browse?package=paper-elements
-[demo]: /demo
+[demo]: https://home-assistant.io/demo
diff --git a/source/_posts/2016-06-23-usb-webcams-and-home-assistant.markdown b/source/_posts/2016-06-23-usb-webcams-and-home-assistant.markdown
index f5bc3669e6..e2d4a191b4 100644
--- a/source/_posts/2016-06-23-usb-webcams-and-home-assistant.markdown
+++ b/source/_posts/2016-06-23-usb-webcams-and-home-assistant.markdown
@@ -12,7 +12,7 @@ og_image: /images/blog/2016-06-cranberry/social.png
---
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like [pygame](http://www.pygame.org/hifi.html) or [SimpleCV](http://www.simplecv.org/) but I never finished something. With the [Local File camera platform](/components/camera.local_file/) by [Landrash](https://github.com/Landrash) and [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) you could integrate a local USB webcam with a few very easy steps.
+In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like [pygame](http://www.pygame.org/hifi.html) or [SimpleCV](http://www.simplecv.org/) but I never finished something. With the [Local File camera platform](https://home-assistant.io/components/camera.local_file/) by [Landrash](https://github.com/Landrash) and [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) you could integrate a local USB webcam with a few very easy steps.
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old [Logitech QuickCam Orbit AF](http://support.logitech.com/en_us/product/quickcam-sphere-af) and a [Logitech HD Webcam C270](http://support.logitech.com/en_us/product/hd-webcam-c270). As a start only the Quickcam is used. No multi-camera setup for now.
@@ -93,7 +93,7 @@ $ sudo motion
[0] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion.log)
```
-Your `target_dir` will start filling up with images from your camera. `motion` will create a symlink called `lastsnap.jpg` which always point to the latest snapshot. We will setup the [Local File camera platform](/components/camera.local_file/) to use this file.
+Your `target_dir` will start filling up with images from your camera. `motion` will create a symlink called `lastsnap.jpg` which always point to the latest snapshot. We will setup the [Local File camera platform](https://home-assistant.io/components/camera.local_file/) to use this file.
```yaml
camera:
@@ -109,7 +109,7 @@ camera:
The machine with the attached USB camera will become a webcam server as well because `motion`'s built-in HTTP server is enabled by default. This means that you could connect your USB webcams to a different machine in your network, run `motion` there, adjust your firewall rules, and use Home Assistant to display the videos. Just check http://[IP of your webcam host]:8081/ to see the stream. This required more powerful hardware than using snapshots, of course.
-In a scenario like this needs a [Generic MJPEG IP Camera ](/components/camera.mjpeg/) in your `configuration.yaml` file.
+In a scenario like this needs a [Generic MJPEG IP Camera ](https://home-assistant.io/components/camera.mjpeg/) in your `configuration.yaml` file.
```yaml
camera:
diff --git a/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown b/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
index 2fa8b44326..31b5ff35bc 100644
--- a/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
+++ b/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
@@ -104,4 +104,4 @@ On the config side, you can now [store your passwords][secrets] in your OS keyri
[reload core config service]: /getting-started/customizing-devices/#reloading-customize
[Sony Bravia TV]: /components/media_player.braviatv/
[Raspberry Pi GPIO pins]: /components/garage_door.rpi_gpio/
-[elevation]: /getting-started/basic/
+[elevation]: https://home-assistant.io/getting-started/basic/
diff --git a/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown b/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown
index 266dcda25d..64ff15761c 100644
--- a/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown
+++ b/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown
@@ -27,13 +27,13 @@ If you start using a PocketCHIP you will definitely look like a Blackberry or a
First a couple of tweaks like setting up `sudo`, upgrading the existing installation, change passwords, enabling ssh, and removal of the annoying stuff then installation of Home Assistant. There is not much to tell...it's straight-forward. For the sake of completeness below the notes about what I did.
-A Debian installation is available by default. This means that some dependencies for Home Assistant are missing. I haven't checked if a new build for the PocketCHIP would include them. So, after a `$ sudo apt-get update` installing those dependencies take a minute or two.
+A Debian installation is available by default. This means that some dependencies for Home Assistant are missing. I haven't checked if a new build for the PocketCHIP would include them. So, after a `$ sudo apt-get update` installing those dependencies take a minute or two.
```bash
$ sudo apt-get install python3-dev python3-pip python3-venv
```
-As usual I run Python applications in a [venv](https://docs.python.org/3/library/venv.html).
+As usual I run Python applications in a [venv](https://docs.python.org/3/library/venv.html).
```bash
$ pvenv ha
@@ -46,14 +46,14 @@ $ cd ha
$ source bin/activate
```
-If you haven't seen the next two commands already then you should visit our [frontsite](/).
+If you haven't seen the next two commands already then you should visit our [frontsite](https://home-assistant.io/).
```bash
$ pip3 install homeassistant
$ hass --open-ui
```
-With `surf` the browsing experience on the low-resolution display is not that great. Most smartphones, even very cheap ones, have touchscreens with higher resolutions. Nevermind, [`midori`](https://twitter.com/fabaff/status/748852317047418880) is not better.
+With `surf` the browsing experience on the low-resolution display is not that great. Most smartphones, even very cheap ones, have touchscreens with higher resolutions. Nevermind, [`midori`](https://twitter.com/fabaff/status/748852317047418880) is not better.
diff --git a/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown b/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown
index 2a7b6c8eef..d9d17ba37b 100644
--- a/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown
+++ b/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown
@@ -27,7 +27,7 @@ One of the graphs created with this tutorial.
_TL; DR: Use [this Jupyter Notebook][nb-prev] to visualize of your data_
-[blog post by Fabian]: /blog/2016/07/19/visualizing-your-iot-data/
+[blog post by Fabian]: https://home-assistant.io/blog/2016/07/19/visualizing-your-iot-data/
[DB Browser for SQLite]: http://sqlitebrowser.org/
[Pandas]: http://pandas.pydata.org/
[matplotlib]: http://matplotlib.org/
diff --git a/source/_posts/2016-08-03-laundry-automation-update.markdown b/source/_posts/2016-08-03-laundry-automation-update.markdown
index 041659c80d..983f706279 100644
--- a/source/_posts/2016-08-03-laundry-automation-update.markdown
+++ b/source/_posts/2016-08-03-laundry-automation-update.markdown
@@ -12,7 +12,7 @@ og_image: /images/blog/2016-07-laundry-automation/protoboard.jpg
_This is a guest post by Home Assistant user and contributor [Nolan Gilley](https://github.com/nkgilley)._
-Today I'll show you how I used Home Assistant, a NodeMCU (ESP8266), and a couple of accelerometers to automate our laundry room. This is a rewrite of an [old post](/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) where I did the same thing using a Moteino & Raspberry Pi. This version only requires a NodeMCU.
+Today I'll show you how I used Home Assistant, a NodeMCU (ESP8266), and a couple of accelerometers to automate our laundry room. This is a rewrite of an [old post](https://home-assistant.io/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) where I did the same thing using a Moteino & Raspberry Pi. This version only requires a NodeMCU.
We have an older washer and dryer which doesn't have any form of notification when cycles complete. Home Assistant was the obvious solution, I just needed to create sensors for the washer and dryer. I tried using sound sensors but found them unreliable. I ended up using an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect whether they're open or closed. I connected the accelerometers and reed switches to an NodeMCU which will relay the data to my MQTT broker.
diff --git a/source/_posts/2016-08-07-optimizing-the-home-assistant-mobile-web-app.markdown b/source/_posts/2016-08-07-optimizing-the-home-assistant-mobile-web-app.markdown
index fcb1d762a1..3633c42b50 100644
--- a/source/_posts/2016-08-07-optimizing-the-home-assistant-mobile-web-app.markdown
+++ b/source/_posts/2016-08-07-optimizing-the-home-assistant-mobile-web-app.markdown
@@ -159,7 +159,7 @@ A lot of optimizations have been applied but this journey will never be over. Th
- Reduce size of initial bundle by moving out all things that are not visible for initial paint. For example the dialogs that show more info about entities.
- Prefetch the other pages using ``
-[demo]: /demo
+[demo]: https://home-assistant.io/demo
[hap]: https://github.com/home-assistant/home-assistant-polymer
[mantra]: https://www.youtube.com/watch?v=zfQoleQEa4w&feature=youtu.be&t=1380
[sw-precache]: https://github.com/GoogleChrome/sw-precache
diff --git a/source/_posts/2016-08-16-we-have-apps-now.markdown b/source/_posts/2016-08-16-we-have-apps-now.markdown
index 00ee02e460..6edf3f8f4b 100644
--- a/source/_posts/2016-08-16-we-have-apps-now.markdown
+++ b/source/_posts/2016-08-16-we-have-apps-now.markdown
@@ -15,7 +15,7 @@ I have been working on a new subsystem to complement Home Assistant's Automation
## {% linkable_title Another Take on Automation %}
-If you haven't yet read Paulus' excellent Blog entry on [Perfect Home Automation](/blog/2016/01/19/perfect-home-automation/) I would encourage you to take a look. As a veteran of several Home Automation systems with varying degrees success, it was this article more than anything else that convinced me that Home Assistant had the right philosophy behind it and was on the right track. One of the most important points made is that being able to control your lights from your phone, 9 times out of 10 is harder than using a lightswitch - where Home Automation really comes into its own is when you start removing the need to use a phone or the switch - the "Automation" in Home Automation. A surprisingly large number of systems out there miss this essential point and have limited abilities to automate anything which is why a robust and open system such as Home Assistant is such an important part of the equation to bring this all together in the vast and chaotic ecosystem that is the "Internet of Things".
+If you haven't yet read Paulus' excellent Blog entry on [Perfect Home Automation](https://home-assistant.io/blog/2016/01/19/perfect-home-automation/) I would encourage you to take a look. As a veteran of several Home Automation systems with varying degrees success, it was this article more than anything else that convinced me that Home Assistant had the right philosophy behind it and was on the right track. One of the most important points made is that being able to control your lights from your phone, 9 times out of 10 is harder than using a lightswitch - where Home Automation really comes into its own is when you start removing the need to use a phone or the switch - the "Automation" in Home Automation. A surprisingly large number of systems out there miss this essential point and have limited abilities to automate anything which is why a robust and open system such as Home Assistant is such an important part of the equation to bring this all together in the vast and chaotic ecosystem that is the "Internet of Things".
So given the importance of Automation, what should Automation allow us to do? I am a pragmatist at heart so I judge individual systems by the ease of accomplishing a few basic but representative tasks:
@@ -32,7 +32,7 @@ So why `AppDaemon`? `AppDaemon` is not meant to replace Home Assistant Automatio
- New paradigm - some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can't
- Ease of use - `AppDaemon`'s API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible, experienced Python programmers should feel right at home.
-- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g., a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file
+- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file
- Dynamic - `AppDaemon` has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to its loose coupling. However, it is better than that - the user can make changes to code and `AppDaemon` will automatically reload the code, figure out which Apps were using it and restart them to use the new code without the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result.
- Complex logic - Python's If/Else constructs are clearer and easier to code for arbitrarily complex nested logic
- Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened
@@ -77,12 +77,12 @@ class MotionLights(appapi.AppDaemon):
def initialize(self):
self.listen_state(self.motion, "binary_sensor.drive", new = "on")
-
+
def motion(self, entity, attribute, old, new, kwargs):
if self.sun_down():
self.turn_on("light.drive")
self.run_in(self.light_off, 60)
-
+
def light_off(self, kwargs):
self.turn_off("light.drive")
```
@@ -98,17 +98,17 @@ class FlashyMotionLights(appapi.AppDaemon):
def initialize(self):
self.listen_state(self.motion, "binary_sensor.drive", new = "on")
-
+
def motion(self, entity, attribute, old, new, kwargs):
if self.self.sun_down():
self.turn_on("light.drive")
self.run_in(self.light_off, 60)
self.flashcount = 0
self.run_in(self.flash_warning, 1)
-
+
def light_off(self, kwargs):
self.turn_off("light.drive")
-
+
def flash_warning(self, kwargs):
self.toggle("light.living_room")
self.flashcount += 1
diff --git a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
index b1c417b1a3..e102f164bb 100644
--- a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
+++ b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
@@ -204,7 +204,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
- The [HTTP] component now takes a different format for authenticating IPs
- Configuration format has changed for [Proximity]
- - The [Arduino] platform are now covered by the configuration check. Please check the documentation to see how.
+ - The [Arduino] platform are now covered by the configuration check. Please check the documentation to see how.
- The Z-Wave entity ID change mentioned above
## {% linkable_title If you need help... %}
@@ -264,40 +264,40 @@ Thanks for reading all of the above, especially since this week was a pretty lon
[@vittoriom]: https://github.com/vittoriom
[@wokar]: https://github.com/wokar
-[Arduino]: /components/arduino/
-[APNS]: /components/notify.apns/
-[ARWN]: /components/sensor.arwn/
-[Concord232]: /components/alarm_control_panel.concord232/
-[HTTP]: /components/http/
-[HaveIBeenPwned]: /components/sensor.haveibeenpwned/
-[Matrix]: //components/notify.matrix/
-[Neato]: /components/switch.neato/
-[Pilight]: /components/sensor.pilight/
-[Proximity]: /components/proximity/
+[Arduino]: https://home-assistant.io/components/arduino/
+[APNS]: https://home-assistant.io/components/notify.apns/
+[ARWN]: https://home-assistant.io/components/sensor.arwn/
+[Concord232]: https://home-assistant.io/components/alarm_control_panel.concord232/
+[HTTP]: https://home-assistant.io/components/http/
+[HaveIBeenPwned]: https://home-assistant.io/components/sensor.haveibeenpwned/
+[Matrix]: https://home-assistant.io//components/notify.matrix/
+[Neato]: https://home-assistant.io/components/switch.neato/
+[Pilight]: https://home-assistant.io/components/sensor.pilight/
+[Proximity]: https://home-assistant.io/components/proximity/
[PyPi]: https://pypi.python.org/pypi
-[Synology]: /components/camera.synology/
-[Telstra]: /components/notify.telstra/
+[Synology]: https://home-assistant.io/components/camera.synology/
+[Telstra]: https://home-assistant.io/components/notify.telstra/
[UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier
-[Verisure]: /components/camera.verisure/
-[WUnderground]: /components/sensor.wunderground/
-[Yamaha]: /components/media_player.yamaha/
-[Zoneminder]: /components/zoneminder/
-[emoncms]: //components/emoncms_history/
-[filtering]: /components/logbook/
-[flash-briefing-docs]: /components/alexa/
+[Verisure]: https://home-assistant.io/components/camera.verisure/
+[WUnderground]: https://home-assistant.io/components/sensor.wunderground/
+[Yamaha]: https://home-assistant.io/components/media_player.yamaha/
+[Zoneminder]: https://home-assistant.io/components/zoneminder/
+[emoncms]: https://home-assistant.io//components/emoncms_history/
+[filtering]: https://home-assistant.io/components/logbook/
+[flash-briefing-docs]: https://home-assistant.io/components/alexa/
[hacktoberfest-blog]: /blog/2016/10/02/hacktoberfest/
[hacktoberfest-ha-prs]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
[hacktoberfest-site-prs]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
[hacktoberfest-website]: https://hacktoberfest.digitalocean.com/
[logo]: /images/blog/2016-10-hacktoberfest/hacktoberfest.png
-[min]: /components/sensor.min_max/
-[netatmo-bin]: /components/binary_sensor.netatmo/
-[netatmo-discovery]: /components/netatmo/
-[nmap]: /components/device_tracker.nmap_tracker/
-[pers-notify]: /components/persistent_notification/
+[min]: https://home-assistant.io/components/sensor.min_max/
+[netatmo-bin]: https://home-assistant.io/components/binary_sensor.netatmo/
+[netatmo-discovery]: https://home-assistant.io/components/netatmo/
+[nmap]: https://home-assistant.io/components/device_tracker.nmap_tracker/
+[pers-notify]: https://home-assistant.io/components/persistent_notification/
[runway]: http://runway.is
-[scrape]: /components/sensor.scrape/
-[updater]: /components/updater/
+[scrape]: https://home-assistant.io/components/sensor.scrape/
+[updater]: https://home-assistant.io/components/updater/
[z-wave-issue]: https://github.com/home-assistant/home-assistant/pull/3759
[zero-one-two-release]: /blog/2016/01/30/insteon-lifx-twitter-and-zigbee/#backwards-incompatible-changes
[zero-two-seven-release]: /blog/2016/08/28/notifications-hue-fake-unification/
diff --git a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
index 4cc4f06944..91d7b7844d 100644
--- a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
+++ b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
@@ -20,7 +20,7 @@ The [Hacktoberfest] is over now. Home Assistant made the 2nd and the 3rd place o
This release has improved the reporting when a config validation error occurs. Thanks to [@kellerza] you will now get a persistent notification added to your UI when this happens.
### {% linkable_title Asynchronous %}
-This release contains the first asynchronous sensor and camera platforms. [@pvizeli] and [@fabaff] ported most of the "internal" sensors to async programming. We hope that you will enjoy the new speed.
+This release contains the first asynchronous sensor and camera platforms. [@pvizeli] and [@fabaff] ported most of the "internal" sensors to async programming. We hope that you will enjoy the new speed.
[@balloob] and [@pvizeli] worked a lot on the improvement of the core itself.
@@ -41,7 +41,7 @@ For a long time we have had a bunch of [weather sensors][weather-sensors] but it
- Sensor: Monitoring support for [Dovado routers][dovado-sensor] ([@molobrakos])
- Sensor: Support for monitoring [printers][cups-sensor] ([@fabaff])
- Add mochad component ([@mtreinish])
-- Notify: Added support for [Android TV/FireTV](/components/notify.nfandroidtv/) - Sensor: New finance platform [CurrencyLayer][currencylayer] ([@arsaboo])
+- Notify: Added support for [Android TV/FireTV](https://home-assistant.io/components/notify.nfandroidtv/) - Sensor: New finance platform [CurrencyLayer][currencylayer] ([@arsaboo])
- Sensor: Support for [InfluxDB sensors][influx-sensor] ([@bestlibre])
- Sensor: New support [HDDTemp sensors][hddtemp-sensor] ([@fabaff])
([@danielperna84])
@@ -105,8 +105,8 @@ We've added a warning to 0.32 to catch platforms accidentally slowing down Home
Our website has now an additional category called "Ecosystem". This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
-- [iOS](/ecosystem/ios/)
-- [SceneGen](/ecosystem/scenegen/)
+- [iOS](https://home-assistant.io/ecosystem/ios/)
+- [SceneGen](https://home-assistant.io/ecosystem/scenegen/)
### {% linkable_title Breaking changes %}
@@ -162,30 +162,30 @@ Our website has now an additional category called "Ecosystem". This will become
[@jnewland]: https://github.com/jnewland
[@DanielHiversen]: https://github.com/DanielHiversen
-[currencylayer]: /components/sensor.currencylayer/
-[yahoo]: /components/sensor.yahoo_finance/
-[mochat]: /components/mochat/
-[firetv]: /components/notify.firetv/
-[Yamaha]: /components/media_player.yamaha/
-[hddtemp-sensor]: /components/sensor.hddtemp/
-[Sonos]: /components/media_player.sonos/
-[weather-sensors]: /components/#weather
-[rpi-camera]: /components/camera.rpi_camera/
-[rest-switch]: /components/switch.rest/
-[emby-media]: /components/media_player.emby/
-[random-sensor]: /components/sensor.random/
-[yeelight]: /components/light.yeelight/
-[influx-sensor]: /components/sensor.influxdb/
-[weather-component]: /components/weather/
-[cups-sensor]: /components/sensor.cups/
-[litejet]: /components/litejet/
-[garadget]: /components/garadget/
-[philips_player]: /components/media_player.philips_js/
-[icloud]: /components/device_tracker.icloud/
-[synologydsm]: /components/sensor.synologydsm/
-[dovado-sensor]: /components/sensor.dovado/
-[ios]: /ecosystem/ios/
+[currencylayer]: https://home-assistant.io/components/sensor.currencylayer/
+[yahoo]: https://home-assistant.io/components/sensor.yahoo_finance/
+[mochat]: https://home-assistant.io/components/mochat/
+[firetv]: https://home-assistant.io/components/notify.firetv/
+[Yamaha]: https://home-assistant.io/components/media_player.yamaha/
+[hddtemp-sensor]: https://home-assistant.io/components/sensor.hddtemp/
+[Sonos]: https://home-assistant.io/components/media_player.sonos/
+[weather-sensors]: https://home-assistant.io/components/#weather
+[rpi-camera]: https://home-assistant.io/components/camera.rpi_camera/
+[rest-switch]: https://home-assistant.io/components/switch.rest/
+[emby-media]: https://home-assistant.io/components/media_player.emby/
+[random-sensor]: https://home-assistant.io/components/sensor.random/
+[yeelight]: https://home-assistant.io/components/light.yeelight/
+[influx-sensor]: https://home-assistant.io/components/sensor.influxdb/
+[weather-component]: https://home-assistant.io/components/weather/
+[cups-sensor]: https://home-assistant.io/components/sensor.cups/
+[litejet]: https://home-assistant.io/components/litejet/
+[garadget]: https://home-assistant.io/components/garadget/
+[philips_player]: https://home-assistant.io/components/media_player.philips_js/
+[icloud]: https://home-assistant.io/components/device_tracker.icloud/
+[synologydsm]: https://home-assistant.io/components/sensor.synologydsm/
+[dovado-sensor]: https://home-assistant.io/components/sensor.dovado/
+[ios]: https://home-assistant.io/ecosystem/ios/
[Hacktoberfest]: https://hacktoberfest.digitalocean.com/
[req-insteon]: https://github.com/home-assistant/home-assistant/issues/3811
-[updater]: /blog/2016/10/25/explaining-the-updater/
-[thingspeak]: /components/thingspeak/
+[updater]: https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
+[thingspeak]: https://home-assistant.io/components/thingspeak/
diff --git a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
index 1c9ca273f8..64511f0eb0 100644
--- a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
+++ b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
@@ -173,7 +173,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@joncar]: https://github.com/joncar
[@kellerza]: https://github.com/kellerza
[@Khabi]: https://github.com/Khabi
-[@lichtteil]: https://github.com/lichtteil
+[@lichtteil]: https://github.com/lichtteil
[@LinuxChristian]: https://github.com/LinuxChristian
[@lwis]: https://github.com/lwis
[@magicus]: https://github.com/magicus
@@ -205,27 +205,27 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@vemek]: https://github.com/vemek
[@vkorn]: https://github.com/vkorn
-[amcrest]: /components/camera.amcrest/
-[boradlink]: /components/sensor.broadlink/
-[dsmr]: /components/sensor.dsmr/
-[dunehd]: /components/media_player.dunehd/
-[efergy]: /components/sensor.efergy/
-[filtering]: /components/http/
-[gpslogger]: /components/device_tracker.gpslogger/
-[harmony]: /components/remote.harmony/
-[homematic]: /components/homematic/
-[hook]: /components/switch.hook/
-[nest-cam]: /components/camera.nest/
-[nest]: /components/nest/
-[nginx]: /ecosystem/nginx/
-[nut]: /components/sensor.nut/
-[philips]: /components/media_player.philips_js/
-[remote]: /components/remote/
-[rfxtrx]: /components/rfxtrx/
-[sonarr]: /components/sensor.sonarr/
-[tellstick]: /components/tellstick/
-[temper]: /components/sensor.temper/
-[threshold]: /components/binary_sensor.threshold/
-[websockets]: /developers/websocket_api/
-[waqi]: /components/sensor.waqi/
+[amcrest]: https://home-assistant.io/components/camera.amcrest/
+[boradlink]: https://home-assistant.io/components/sensor.broadlink/
+[dsmr]: https://home-assistant.io/components/sensor.dsmr/
+[dunehd]: https://home-assistant.io/components/media_player.dunehd/
+[efergy]: https://home-assistant.io/components/sensor.efergy/
+[filtering]: https://home-assistant.io/components/http/
+[gpslogger]: https://home-assistant.io/components/device_tracker.gpslogger/
+[harmony]: https://home-assistant.io/components/remote.harmony/
+[homematic]: https://home-assistant.io/components/homematic/
+[hook]: https://home-assistant.io/components/switch.hook/
+[nest-cam]: https://home-assistant.io/components/camera.nest/
+[nest]: https://home-assistant.io/components/nest/
+[nginx]: https://home-assistant.io/ecosystem/nginx/
+[nut]: https://home-assistant.io/components/sensor.nut/
+[philips]: https://home-assistant.io/components/media_player.philips_js/
+[remote]: https://home-assistant.io/components/remote/
+[rfxtrx]: https://home-assistant.io/components/rfxtrx/
+[sonarr]: https://home-assistant.io/components/sensor.sonarr/
+[tellstick]: https://home-assistant.io/components/tellstick/
+[temper]: https://home-assistant.io/components/sensor.temper/
+[threshold]: https://home-assistant.io/components/binary_sensor.threshold/
+[websockets]: https://home-assistant.io/developers/websocket_api/
+[waqi]: https://home-assistant.io/components/sensor.waqi/
diff --git a/source/_posts/2016-12-17-text-to-speech-aquostv-flic-zamg.markdown b/source/_posts/2016-12-17-text-to-speech-aquostv-flic-zamg.markdown
index 8122118124..2f4697f628 100644
--- a/source/_posts/2016-12-17-text-to-speech-aquostv-flic-zamg.markdown
+++ b/source/_posts/2016-12-17-text-to-speech-aquostv-flic-zamg.markdown
@@ -30,7 +30,7 @@ Let you control [VLC media player][vlc-media] and play sound on connected speak
This Broadlink [switch][bl-switch] platform allow to you control Broadlink RM2 Pro and RM mini IR+RF devices. This Broadlink [sensor][bl-sensor] platform adds support for Broadlink RM2 and A1 Devices.
-The [GPSLogger](/components/device_tracker.gpslogger/) now also supports attributes as the speed, direction, altitude, provider, and activity.
+The [GPSLogger](https://home-assistant.io/components/device_tracker.gpslogger/) now also supports attributes as the speed, direction, altitude, provider, and activity.
## {% linkable_title All changes %}
- Media player: Support for Sharp [AquaosTV][aquostv] ([@titilambert])
@@ -86,7 +86,7 @@ http:
- Fix async component update on service calls ([@pvizeli])
- Fix async log handle do not close ([@pvizeli])
- Fix nest component with various KeyError exceptions ([@technicalpickles])
-
+
### {% linkable_title If you need help... %}
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
@@ -141,16 +141,16 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@turbokongen]: https://github.com/turbokongen
[@w1ll1am23]: https://github.com/w1ll1am23
-[vlc-media]: /components/media_player.vlc/
-[aquostv]: /components/media_player.aquostv/
-[digitalloggers]: /components/switch.digitalloggers/
-[netdata]: /components/sensor.netdata/
-[bl-sensor]: /components/sensor.broadlink/
-[bl-switch]: /components/switch.broadlink/
-[hikvision]: /components/binary_sensor.hikvision/
-[zamg]: /components/sensor.zamg/
-[flic]: /components/binary_sensor.flic/
-[sensehat]: /components/sensor.sensehat/
-[tts]: /components/tts/
+[vlc-media]: https://home-assistant.io/components/media_player.vlc/
+[aquostv]: https://home-assistant.io/components/media_player.aquostv/
+[digitalloggers]: https://home-assistant.io/components/switch.digitalloggers/
+[netdata]: https://home-assistant.io/components/sensor.netdata/
+[bl-sensor]: https://home-assistant.io/components/sensor.broadlink/
+[bl-switch]: https://home-assistant.io/components/switch.broadlink/
+[hikvision]: https://home-assistant.io/components/binary_sensor.hikvision/
+[zamg]: https://home-assistant.io/components/sensor.zamg/
+[flic]: https://home-assistant.io/components/binary_sensor.flic/
+[sensehat]: https://home-assistant.io/components/sensor.sensehat/
+[tts]: https://home-assistant.io/components/tts/
[discord]: https://discord.gg/c5DvZ4e
[discord-devs]: https://discord.gg/8X8DTH4
diff --git a/source/_posts/2016-12-19-thank-you.markdown b/source/_posts/2016-12-19-thank-you.markdown
index cbdc2a6d45..b91eb72494 100644
--- a/source/_posts/2016-12-19-thank-you.markdown
+++ b/source/_posts/2016-12-19-thank-you.markdown
@@ -29,7 +29,7 @@ We're taking a well deserved break and we will be back again in 2017 with more a
– Paulus
-[0.10]: /blog/2015/12/22/amazon-echo-icloud-and-templates/
+[0.10]: https://home-assistant.io/blog/2015/12/22/amazon-echo-icloud-and-templates/
[AppFolio]: http://www.appfolioinc.com/
[GitHub]: https://GitHub.com
[TravisCI]: https://Travis-ci.org
diff --git a/source/_posts/2017-01-14-iss-usps-images-packages.markdown b/source/_posts/2017-01-14-iss-usps-images-packages.markdown
index 3b6623e680..11a2b2fe71 100644
--- a/source/_posts/2017-01-14-iss-usps-images-packages.markdown
+++ b/source/_posts/2017-01-14-iss-usps-images-packages.markdown
@@ -162,34 +162,34 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@webworxshop]: https://github.com/webworxshop
[@Zac-HD]: https://github.com/Zac-HD
-[apns]: /components/notify.apns/
-[beaglebone]: /components/bbb_gpio/
-[bl-switch]: /components/switch.broadlink/
-[bom]: /components/weather.bom/
-[dublin]: /components/sensor.dublin_public_transport/
-[facebook]: /components/notify.facebook/
-[image]: /components/image_processing/
-[influx]: /components/influxdb/
-[insteon]: /components/insteon_local/
-[iss]: /components/sensor.iss/
-[kankun]: /components/switch.kankun/
-[lannouncer]: /components/notify.lannouncer/
-[mysensors]: /components/notify.mysensors/
-[packages]: /topics/packages/
-[pico]: /components/tts.picotts/
-[ping]: /components/device_tracker.ping/
-[plates]: /components/openalpr/
-[quebec]: /components/sensor.hydroquebec/
-[rest]: /components/rest_command/
-[sma]: /components/sensor.sma/
-[sonarr]: /components/sensor.sonarr/
-[tik]: /components/light.tikteck/
-[trackr]: /components/device_tracker.trackr/
-[upc]: /components/device_tracker.upc_connect/
-[usps]: /components/sensor.usps/
-[wink-fan]: /components/fan.wink/
-[xiaomi]: /components/device_tracker.xiaomi/
-[yandex]: /components/tts.yandextts/
-[yeelight]: /components/light.yeelight/
-[zengge]: /components/light.zengge/
+[apns]: https://home-assistant.io/components/notify.apns/
+[beaglebone]: https://home-assistant.io/components/bbb_gpio/
+[bl-switch]: https://home-assistant.io/components/switch.broadlink/
+[bom]: https://home-assistant.io/components/weather.bom/
+[dublin]: https://home-assistant.io/components/sensor.dublin_public_transport/
+[facebook]: https://home-assistant.io/components/notify.facebook/
+[image]: https://home-assistant.io/components/image_processing/
+[influx]: https://home-assistant.io/components/influxdb/
+[insteon]: https://home-assistant.io/components/insteon_local/
+[iss]: https://home-assistant.io/components/sensor.iss/
+[kankun]: https://home-assistant.io/components/switch.kankun/
+[lannouncer]: https://home-assistant.io/components/notify.lannouncer/
+[mysensors]: https://home-assistant.io/components/notify.mysensors/
+[packages]: https://home-assistant.io/topics/packages/
+[pico]: https://home-assistant.io/components/tts.picotts/
+[ping]: https://home-assistant.io/components/device_tracker.ping/
+[plates]: https://home-assistant.io/components/openalpr/
+[quebec]: https://home-assistant.io/components/sensor.hydroquebec/
+[rest]: https://home-assistant.io/components/rest_command/
+[sma]: https://home-assistant.io/components/sensor.sma/
+[sonarr]: https://home-assistant.io/components/sensor.sonarr/
+[tik]: https://home-assistant.io/components/light.tikteck/
+[trackr]: https://home-assistant.io/components/device_tracker.trackr/
+[upc]: https://home-assistant.io/components/device_tracker.upc_connect/
+[usps]: https://home-assistant.io/components/sensor.usps/
+[wink-fan]: https://home-assistant.io/components/fan.wink/
+[xiaomi]: https://home-assistant.io/components/device_tracker.xiaomi/
+[yandex]: https://home-assistant.io/components/tts.yandextts/
+[yeelight]: https://home-assistant.io/components/light.yeelight/
+[zengge]: https://home-assistant.io/components/light.zengge/
diff --git a/source/_posts/2017-01-28-face-coffee-wink.markdown b/source/_posts/2017-01-28-face-coffee-wink.markdown
index 4a4f572ebf..26d05a6d94 100644
--- a/source/_posts/2017-01-28-face-coffee-wink.markdown
+++ b/source/_posts/2017-01-28-face-coffee-wink.markdown
@@ -15,7 +15,7 @@ og_image: /images/blog/2017-01-0.37/social.png
No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the "Breaking changes" section because there are also massive improvements for some platforms and components.
### {% linkable_title Governance %}
-As announced, the new [Governance][gov] requires for developers to sign the CLA. [Code of Conduct][coc], [Contributor License Agreement][cla], and proper [Licensing][license] will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
+As announced, the new [Governance][gov] requires for developers to sign the CLA. [Code of Conduct][coc], [Contributor License Agreement][cla], and proper [Licensing][license] will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
### {% linkable_title Face recognition using the Microsoft Face API %}
[@pvizeli] has been on a roll with the image processing integrations. This time it's the [Microsoft Face API][face]. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
@@ -34,7 +34,7 @@ Although the old method is not insecure, the new method is a lot more secure. Up
### {% linkable_title Major Wink and HDMI CEC improvements %}
[@w1ll1am23] did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your `configuration.yaml` file, no `client_id` and `client_secret` are needed, and token which was generated with the generator located in the [Wink][wink] documentation.
-The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren't previously detected or supported in the older version.
+The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren't previously detected or supported in the older version.
Thanks to [@konikvranik] the [HDMI CEC][cec] integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
@@ -229,35 +229,35 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@mKeRix]: https://github.com/mKeRix
[@fakezeta]: https://github.com/fakezeta
-[amcrest]: /components/binary_sensor.amcrest/
-[discord]: /components/notify.discord/
-[tado]: /components/device_tracker.tado/
-[sky]: /components/device_tracker.sky_hub/
-[zabbix]: /components/zabbix/
-[avion]: /components/light.avion/
-[anthem]: /components/media_player.anthemav/
-[bb-bin]: /components/binary_sensor.bbb_gpio/
-[piglow]: /components/light.piglow/
-[wsdot]: /components/sensor.wsdot/
-[skybeacon]: /components/sensor.skybeacon/
-[lutron]: /components/lutron/
-[polly]: /components/tts.amazon_polly/
-[linksys]: /components/device_tracker.linksys_ap/
-[emul-hue]: /components/emulated_hue/
-[netatmo]: /components/netatmo/
-[face]: /components/microsoft_face/
-[iss]: /components/binary_sensor.iss/
-[roku]: /components/media_player.roku/
-[openalpr]: /components/#image-processing
-[image]: /components/image_processing/
+[amcrest]: https://home-assistant.io/components/binary_sensor.amcrest/
+[discord]: https://home-assistant.io/components/notify.discord/
+[tado]: https://home-assistant.io/components/device_tracker.tado/
+[sky]: https://home-assistant.io/components/device_tracker.sky_hub/
+[zabbix]: https://home-assistant.io/components/zabbix/
+[avion]: https://home-assistant.io/components/light.avion/
+[anthem]: https://home-assistant.io/components/media_player.anthemav/
+[bb-bin]: https://home-assistant.io/components/binary_sensor.bbb_gpio/
+[piglow]: https://home-assistant.io/components/light.piglow/
+[wsdot]: https://home-assistant.io/components/sensor.wsdot/
+[skybeacon]: https://home-assistant.io/components/sensor.skybeacon/
+[lutron]: https://home-assistant.io/components/lutron/
+[polly]: https://home-assistant.io/components/tts.amazon_polly/
+[linksys]: https://home-assistant.io/components/device_tracker.linksys_ap/
+[emul-hue]: https://home-assistant.io/components/emulated_hue/
+[netatmo]: https://home-assistant.io/components/netatmo/
+[face]: https://home-assistant.io/components/microsoft_face/
+[iss]: https://home-assistant.io/components/binary_sensor.iss/
+[roku]: https://home-assistant.io/components/media_player.roku/
+[openalpr]: https://home-assistant.io/components/#image-processing
+[image]: https://home-assistant.io/components/image_processing/
[emul_hue]: https://github.com/home-assistant/home-assistant/pull/5549
-[coc]: /developers/code_of_conduct/
-[cla]: /developers/cla/
-[gov]: /blog/2017/01/21/home-assistant-governance/
-[license]: /developers/license/
-[wink]: /components/wink/
-[coffee]: /components/switch.wemo/
-[cec]: /components/hdmi_cec/
-[mysensors]: /components/mysensors/
-[sonos]: /components/media_player.sonos/
-[twilio]: /components/notify.twilio_call/
+[coc]: https://home-assistant.io/developers/code_of_conduct/
+[cla]: https://home-assistant.io/developers/cla/
+[gov]: https://home-assistant.io/blog/2017/01/21/home-assistant-governance/
+[license]: https://home-assistant.io/developers/license/
+[wink]: https://home-assistant.io/components/wink/
+[coffee]: https://home-assistant.io/components/switch.wemo/
+[cec]: https://home-assistant.io/components/hdmi_cec/
+[mysensors]: https://home-assistant.io/components/mysensors/
+[sonos]: https://home-assistant.io/components/media_player.sonos/
+[twilio]: https://home-assistant.io/components/notify.twilio_call/
diff --git a/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown b/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
index 1c71005ad4..89a1b2a1eb 100644
--- a/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
+++ b/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
@@ -196,36 +196,36 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@w1ll1am23]: https://github.com/w1ll1am23
[@Yannic-HAW]: https://github.com/Yannic-HAW
-[alert]: /components/alert/
-[apiai]: /components/apiai/
-[apple-tv]: /components/media_player.apple_tv/
-[arwn]: /components/sensor.arwn/
-[custom-ui]: /developers/frontend_creating_custom_ui/
-[discovery]: /components/discovery/
-[face-detect]: /components/image_processing.microsoft_face_detect/
-[ffmpeg-bin]: /components/binary_sensor.ffmpeg/
-[ffmpeg]: /components/ffmpeg/
-[filters]: /topics/templating/#home-assistant-template-extensions
-[fritz]: /components/switch.fritzdect/
-[hue]: /components/light.hue/
-[light]: /cookbook/custom_ui_by_andrey-git
-[mailgun]: /components/notify.mailgun/
-[media-player]: /components/media_player/
-[moon]: /components/sensor.moon/
-[mqtt-discovery]: /components/mqtt/#discovery
-[nuki]: /components/lock.nuki/
-[openevse]: /components/sensor.openevse/
-[orange]: /components/media_player.liveboxplaytv/
-[owm]: /components/sensor.openweathermap/
+[alert]: https://home-assistant.io/components/alert/
+[apiai]: https://home-assistant.io/components/apiai/
+[apple-tv]: https://home-assistant.io/components/media_player.apple_tv/
+[arwn]: https://home-assistant.io/components/sensor.arwn/
+[custom-ui]: https://home-assistant.io/developers/frontend_creating_custom_ui/
+[discovery]: https://home-assistant.io/components/discovery/
+[face-detect]: https://home-assistant.io/components/image_processing.microsoft_face_detect/
+[ffmpeg-bin]: https://home-assistant.io/components/binary_sensor.ffmpeg/
+[ffmpeg]: https://home-assistant.io/components/ffmpeg/
+[filters]: https://home-assistant.io/topics/templating/#home-assistant-template-extensions
+[fritz]: https://home-assistant.io/components/switch.fritzdect/
+[hue]: https://home-assistant.io/components/light.hue/
+[light]: https://home-assistant.io/cookbook/custom_ui_by_andrey-git
+[mailgun]: https://home-assistant.io/components/notify.mailgun/
+[media-player]: https://home-assistant.io/components/media_player/
+[moon]: https://home-assistant.io/components/sensor.moon/
+[mqtt-discovery]: https://home-assistant.io/components/mqtt/#discovery
+[nuki]: https://home-assistant.io/components/lock.nuki/
+[openevse]: https://home-assistant.io/components/sensor.openevse/
+[orange]: https://home-assistant.io/components/media_player.liveboxplaytv/
+[owm]: https://home-assistant.io/components/sensor.openweathermap/
[python-yeelight]: https://gitlab.com/stavros/python-yeelight
-[qnap]: /components/sensor.qnap/
-[rflink]: /components/rflink/
-[systemmonitor]: /components/sensor.systemmonitor/
-[webostv]: /components/media_player.webostv/
-[yeelight]: /components/light.yeelight/
+[qnap]: https://home-assistant.io/components/sensor.qnap/
+[rflink]: https://home-assistant.io/components/rflink/
+[systemmonitor]: https://home-assistant.io/components/sensor.systemmonitor/
+[webostv]: https://home-assistant.io/components/media_player.webostv/
+[yeelight]: https://home-assistant.io/components/light.yeelight/
-[event-stream-api]: /developers/server_sent_events/
+[event-stream-api]: https://home-assistant.io/developers/server_sent_events/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
-[websocket-api]: /developers/websocket_api/
+[websocket-api]: https://home-assistant.io/developers/websocket_api/
[discord]: https://discord.gg/c5DvZ4e
diff --git a/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown b/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
index 846bc1ac4e..e92643be51 100644
--- a/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
+++ b/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
@@ -285,33 +285,33 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@kitcorey]: https://github.com/kitcorey
[@andersonshatch]: https://github.com/andersonshatch
-[telegram]: /componet/telegram_webhooks/
-[pushsafer]: /components/notify.pushsafer/
-[openhome]: /components/media_player.openhome/
-[ups]: /components/sensor.ups/
-[fedex]: /components/sensor.fedex/
-[fido]: /components/sensor.fido/
-[gstreamer]: /components/media_player.gstreamer/
-[clementine]: /components/media_player.clementine/
-[ebox]: /components/sensor.ebox/
-[aurora]: /components/binary_sensor.aurora/
-[netmonitor]: /components/sensor.fritzbox_netmonitor/
-[itach]: /components/remote.itach/
-[sunflowers]: /components/light.yeelightsunflower/
-[kodi]: /components/media_player.kodi/
-[myq]: /components/cover.myq/
-[oemt]: /components/climate.oem/
-[volvo]: /components/volvooncall/
-[pocket]: /components/sensor.pocketcasts/
-[config]: /components/config/
-[history_stats]: /components/sensor.history_stats/
+[telegram]: https://home-assistant.io/componet/telegram_webhooks/
+[pushsafer]: https://home-assistant.io/components/notify.pushsafer/
+[openhome]: https://home-assistant.io/components/media_player.openhome/
+[ups]: https://home-assistant.io/components/sensor.ups/
+[fedex]: https://home-assistant.io/components/sensor.fedex/
+[fido]: https://home-assistant.io/components/sensor.fido/
+[gstreamer]: https://home-assistant.io/components/media_player.gstreamer/
+[clementine]: https://home-assistant.io/components/media_player.clementine/
+[ebox]: https://home-assistant.io/components/sensor.ebox/
+[aurora]: https://home-assistant.io/components/binary_sensor.aurora/
+[netmonitor]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
+[itach]: https://home-assistant.io/components/remote.itach/
+[sunflowers]: https://home-assistant.io/components/light.yeelightsunflower/
+[kodi]: https://home-assistant.io/components/media_player.kodi/
+[myq]: https://home-assistant.io/components/cover.myq/
+[oemt]: https://home-assistant.io/components/climate.oem/
+[volvo]: https://home-assistant.io/components/volvooncall/
+[pocket]: https://home-assistant.io/components/sensor.pocketcasts/
+[config]: https://home-assistant.io/components/config/
+[history_stats]: https://home-assistant.io/components/sensor.history_stats/
-[docs]: /docs/
-[getting-started]: /getting-started/
+[docs]: https://home-assistant.io/docs/
+[getting-started]: https://home-assistant.io/getting-started/
[docs-issue]: https://github.com/home-assistant/home-assistant.github.io/issues/1603
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
-[t-shirt]: /blog/2017/02/22/home-assistant-tshirts-have-arrived/
+[t-shirt]: https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/
[discord]: https://discord.gg/c5DvZ4e
diff --git a/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown b/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
index d633146e60..2f495e99ab 100644
--- a/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
+++ b/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
@@ -312,7 +312,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[EFF]: https://www.eff.org
-[hass-shirt]: /blog/2017/02/22/home-assistant-tshirts-have-arrived/
+[hass-shirt]: https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/
[#6532]: https://github.com/home-assistant/home-assistant/pull/6532
[#6552]: https://github.com/home-assistant/home-assistant/pull/6552
[#6574]: https://github.com/home-assistant/home-assistant/pull/6574
diff --git a/source/_posts/2017-03-25-todo-volumio-workday.markdown b/source/_posts/2017-03-25-todo-volumio-workday.markdown
index c0ebd7f9e6..acac7c9f5f 100644
--- a/source/_posts/2017-03-25-todo-volumio-workday.markdown
+++ b/source/_posts/2017-03-25-todo-volumio-workday.markdown
@@ -11,10 +11,10 @@ categories: Release-Notes
og_image: /images/blog/2017-03-0.41/social.png
---
-Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. [Paulus][@balloob] did an [interview] with [OpenSourceCraft], [Fabian][@fabaff] did a [workshop] at the [Chemnitzer Linux Tage][clt], and we are now an award-winning Open source project (I will cover that in a separate blog post).
+Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. [Paulus][@balloob] did an [interview] with [OpenSourceCraft], [Fabian][@fabaff] did a [workshop] at the [Chemnitzer Linux Tage][clt], and we are now an award-winning Open source project (I will cover that in a separate blog post).
## Plex
-[@JesseWebDotCom] made massive changes to the [Plex][plex] media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
+[@JesseWebDotCom] made massive changes to the [Plex][plex] media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
## Component overview
The [Components][components] overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, [@bdurrer] for this.
@@ -334,16 +334,16 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@wmalgadey]: https://github.com/wmalgadey
[@yeralin]: https://github.com/yeralin
-[components]: /components/
-[kodi]: /components/notify.kodi/
-[mpd]: /components/media_player.mpd/
-[emby]: /components/media_player.emby/
-[mqtt]: /docs/mqtt/
-[plex]: /components/media_player.plex/
-[tado]: /components/climate.tado/
-[volumio]: //components/media_player.volumio/
-[workday]: /components/binary_sensor.workday/
-[android]: /components/android_ip_webcam/
+[components]: https://home-assistant.io/components/
+[kodi]: https://home-assistant.io/components/notify.kodi/
+[mpd]: https://home-assistant.io/components/media_player.mpd/
+[emby]: https://home-assistant.io/components/media_player.emby/
+[mqtt]: https://home-assistant.io/docs/mqtt/
+[plex]: https://home-assistant.io/components/media_player.plex/
+[tado]: https://home-assistant.io/components/climate.tado/
+[volumio]: https://home-assistant.io//components/media_player.volumio/
+[workday]: https://home-assistant.io/components/binary_sensor.workday/
+[android]: https://home-assistant.io/components/android_ip_webcam/
[shadow]: https://www.w3.org/TR/shadow-dom/
[forum]: https://community.home-assistant.io/
@@ -351,7 +351,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[discord]: https://discord.gg/c5DvZ4e
[@bdurrer]: https://github.com/bdurrer
-[interview]: /blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/
+[interview]: https://home-assistant.io/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/
[OpenSourceCraft]: http://codepop.com/open-sourcecraft
[clt]: https://chemnitzer.linux-tage.de/2017/en/
[workshop]: https://github.com/home-assistant/home-assistant-assets/tree/master/german/2017-clt-workshop
diff --git a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown
index 07cc25a196..8e05ea0fa2 100644
--- a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown
+++ b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown
@@ -20,7 +20,7 @@ The app could be hosted on any Node.js hosting. I prefer [Heroku: Cloud Applicat
### {% linkable_title Bringing pieces together %}
-1. Configure the Home Assistant [MQTT trigger](/docs/automation/trigger/#mqtt-trigger).
+1. Configure the Home Assistant [MQTT trigger](https://home-assistant.io/docs/automation/trigger/#mqtt-trigger).
1. Configure [CloudMQTT](https://www.cloudmqtt.com/). Check this [video tutorial](https://www.youtube.com/watch?v=VaWdvVVYU3A) for details.
1. [](https://heroku.com/deploy?template=https://github.com/petkov/http_to_mqtt) HTTP to MQTT bridge app.
1. Add the [Configuration Variables](https://devcenter.heroku.com/articles/config-vars#setting-up-config-vars-for-a-deployed-application) to your Heroku app mentioned here.
diff --git a/source/_posts/2017-04-17-ikea-tradfri-internet-of-things-done-right.markdown b/source/_posts/2017-04-17-ikea-tradfri-internet-of-things-done-right.markdown
index d44d60a79f..60b1ab239f 100644
--- a/source/_posts/2017-04-17-ikea-tradfri-internet-of-things-done-right.markdown
+++ b/source/_posts/2017-04-17-ikea-tradfri-internet-of-things-done-right.markdown
@@ -126,15 +126,15 @@ As it currently stands, this is going to be the perfect companion hardware to wo
[tradfri]: http://www.ikea.com/us/en/catalog/categories/departments/lighting/36812/
[mjg59]: http://mjg59.dreamwidth.org/47803.html
[hue-support]: https://developers.meethue.com/content/philips-hue-and-ikea-tr%C3%A5dfri#comment-2686
-[perfect]: /blog/2016/01/19/perfect-home-automation/#you-should-not-have-to-adapt-to-technology
+[perfect]: https://home-assistant.io/blog/2016/01/19/perfect-home-automation/#you-should-not-have-to-adapt-to-technology
[Patrik]: https://github.com/ggravlingen
[forums]: https://community.home-assistant.io/t/ikea-tradfri-gateway-zigbee/14788
[pytradfri]: https://github.com/ggravlingen/pytradfri
[rumors]: https://github.com/bwssytems/ha-bridge/issues/570#issuecomment-293505087
[Homebridge]: https://github.com/nfarina/homebridge
[hb-hass]: https://github.com/home-assistant/homebridge-homeassistant
-[emulated_hue]: /components/emulated_hue/
-[apiai]: /components/apiai/
+[emulated_hue]: https://home-assistant.io/components/emulated_hue/
+[apiai]: https://home-assistant.io/components/apiai/
[Haaska]: https://github.com/auchter/haaska
[great marketing material]: https://i2.wp.com/blog.smartthings.com/wp-content/uploads/2014/06/summer-vacay-683x405-blog.png?fit=683%2C405&ssl=1
-[classification]: /blog/2016/02/12/classifying-the-internet-of-things/
+[classification]: https://home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/
diff --git a/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown b/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
index ea172859d0..64f0b02ab0 100644
--- a/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
+++ b/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
@@ -495,14 +495,14 @@ Experiencing issues introduced by this release? Please report them in our [issue
[#7267]: https://github.com/home-assistant/home-assistant/pull/7267
[#7287]: https://github.com/home-assistant/home-assistant/pull/7287
[@KlaasH]: https://github.com/KlaasH
-[cover.zwave docs]: /components/cover.zwave/
-[recorder docs]: /components/recorder/
-[switch.hook docs]: /components/switch.hook/
-[switch.wemo docs]: /components/switch.wemo/
-[telegram_bot docs]: /components/telegram_bot/
-[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/
-[wemo docs]: /components/wemo/
-[zwave.workaround docs]: /components/zwave.workaround/
+[cover.zwave docs]: https://home-assistant.io/components/cover.zwave/
+[recorder docs]: https://home-assistant.io/components/recorder/
+[switch.hook docs]: https://home-assistant.io/components/switch.hook/
+[switch.wemo docs]: https://home-assistant.io/components/switch.wemo/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/
+[wemo docs]: https://home-assistant.io/components/wemo/
+[zwave.workaround docs]: https://home-assistant.io/components/zwave.workaround/
[#7271]: https://github.com/home-assistant/home-assistant/pull/7271
[#7282]: https://github.com/home-assistant/home-assistant/pull/7282
[#7290]: https://github.com/home-assistant/home-assistant/pull/7290
@@ -513,9 +513,9 @@ Experiencing issues introduced by this release? Please report them in our [issue
[#7324]: https://github.com/home-assistant/home-assistant/pull/7324
[#7329]: https://github.com/home-assistant/home-assistant/pull/7329
[#7337]: https://github.com/home-assistant/home-assistant/pull/7337
-[device_tracker.automatic docs]: /components/device_tracker.automatic/
-[hassio docs]: /components/hassio/
-[notify.html5 docs]: /components/notify.html5/
-[notify.telegram docs]: /components/notify.telegram/
-[telegram_bot.polling docs]: /components/telegram_bot.polling/
+[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/
+[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/
[discord]: https://discord.gg/c5DvZ4e
diff --git a/source/_posts/2017-04-24-hardware-contest-2017.markdown b/source/_posts/2017-04-24-hardware-contest-2017.markdown
index 0a1b08123f..083eb12242 100644
--- a/source/_posts/2017-04-24-hardware-contest-2017.markdown
+++ b/source/_posts/2017-04-24-hardware-contest-2017.markdown
@@ -22,7 +22,7 @@ The voting is now open. To keep things simple are we using the voting feature of
End of the voting period: April, 30 2017 - 23.59 UTC
-[hardware]: /blog/2017/04/01/thomas-krenn-award/
+[hardware]: https://home-assistant.io/blog/2017/04/01/thomas-krenn-award/
[award]: https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/
[forum]: https://community.home-assistant.io/c/contest-2017
[twitter]: https://twitter.com/home_assistant
diff --git a/source/_posts/2017-04-25-influxdb-grafana-docker.markdown b/source/_posts/2017-04-25-influxdb-grafana-docker.markdown
index 75cdd440c1..184028eaa4 100644
--- a/source/_posts/2017-04-25-influxdb-grafana-docker.markdown
+++ b/source/_posts/2017-04-25-influxdb-grafana-docker.markdown
@@ -11,7 +11,7 @@ categories: How-To
og_image: /images/blog/2017-04-influxdb-grafana/influxdb-grafana-ha.png
---
-Home Assistant collects volumes of (time series) data that are well suited for some fancy graphs. Although the [History](/components/history/) component provides some nice plots, I am sure you have always wanted those fancy [Grafana](https://grafana.com/) plots. The problem, however, is that low-powered device such as Raspberry Pi that most of us use for our Home Assistant setup are not well suited for such operation.
+Home Assistant collects volumes of (time series) data that are well suited for some fancy graphs. Although the [History](https://home-assistant.io/components/history/) component provides some nice plots, I am sure you have always wanted those fancy [Grafana](https://grafana.com/) plots. The problem, however, is that low-powered device such as Raspberry Pi that most of us use for our Home Assistant setup are not well suited for such operation.
Instead of running [InfluxDB](https://www.influxdata.com/) and Grafana on a Raspberry Pi or a different system and go through the [classic approach of installing both tools separately](/blog/2015/12/07/influxdb-and-grafana/), you can run them in a Docker container on another machine. For this tutorial, I am using a Synology NAS, but the instructions should apply to other devices that can run Docker. Just follow the steps below:
diff --git a/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown b/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown
index 28434d3642..ce60a7e8bc 100644
--- a/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown
+++ b/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown
@@ -15,7 +15,7 @@ og_image: /images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.
-If you have a security key set in your Open Z-Wave `options.xml`, copy `options.xml` to your Home Assistant configuration directory. This is the only place where options will get persisted. -
+If you have a security key set in your Open Z-Wave `options.xml`, copy `options.xml` to your Home Assistant configuration directory. This is the only place where options will get persisted. + Next to that [@armills] has lead the charge and managed to get full test coverage for Z-Wave! Thanks for all the hard work! @@ -53,7 +53,7 @@ And last, but not least, our Docker image is now based off Python 3.6. This vers If you are using our [experimental Hass.io image][hass.io], we made a breaking change in how the panel is served. If you have an existing installation, make sure you update your supervisor to the latest version before updating Home Assistant. If you are going to flash a new Hass.io image, make sure to only flash the new 0.8 image as linked on [the installation page][hass.io-install]. [hass.io]: https://community.home-assistant.io/t/introducing-hass-io/17296 -[hass.io-install]: /hassio/installation/ +[hass.io-install]: https://home-assistant.io/hassio/installation/ ## {% linkable_title New integrations %} @@ -335,93 +335,93 @@ Experiencing issues introduced by this release? Please report them in our [issue [@tsvi]: https://github.com/tsvi [@turbokongen]: https://github.com/turbokongen [@w1ll1am23]: https://github.com/w1ll1am23 -[alexa docs]: /components/alexa/ -[axis docs]: /components/axis/ -[config.automation docs]: /docs/automation/editor/ -[automation.event docs]: /docs/configuration/events/ -[automation.state docs]: /docs/configuration/state_object/ -[binary_sensor.mystrom docs]: /components/binary_sensor.mystrom/ -[binary_sensor.raspihats docs]: /components/binary_sensor.raspihats/ -[binary_sensor.rpi_pfio docs]: /components/binary_sensor.rpi_pfio/ -[blink docs]: /components/blink/ -[camera.__init__ docs]: /components/camera.__init__/ -[camera.uvc docs]: /components/camera.uvc/ -[camera.zoneminder docs]: /components/camera.zoneminder/ -[climate.sensibo docs]: /components/climate.sensibo/ -[config.__init__ docs]: /components/config.__init__/ -[configurator docs]: /components/configurator/ -[cover.lutron_caseta docs]: /components/cover.lutron_caseta/ -[datadog docs]: /components/datadog/ -[device_tracker.automatic docs]: /components/device_tracker.automatic/ -[device_tracker.linksys_ap docs]: /components/device_tracker.linksys_ap/ -[device_tracker.unifi docs]: /components/device_tracker.unifi/ -[dweet docs]: /components/dweet/ -[eight_sleep docs]: /components/eight_sleep/ -[homematic docs]: /components/homematic/ -[image_processing.__init__ docs]: /components/image_processing.__init__/ -[image_processing.demo docs]: /components/image_processing.demo/ -[image_processing.dlib_face_detect docs]: /components/image_processing.dlib_face_detect/ -[image_processing.dlib_face_identify docs]: /components/image_processing.dlib_face_identify/ -[image_processing.microsoft_face_detect docs]: /components/image_processing.microsoft_face_detect/ -[image_processing.microsoft_face_identify docs]: /components/image_processing.microsoft_face_identify/ -[image_processing.openalpr_cloud docs]: /components/image_processing.openalpr_cloud/ -[image_processing.openalpr_local docs]: /components/image_processing.openalpr_local/ -[image_processing.opencv docs]: /components/image_processing.opencv/ -[image_processing.seven_segments docs]: /components/image_processing.seven_segments/ -[kira docs]: /components/kira/ -[light.__init__ docs]: /components/light.__init__/ -[light.blinksticklight docs]: /components/light.blinksticklight/ -[light.enocean docs]: /components/light.enocean/ -[light.flux_led docs]: /components/light.flux_led/ -[light.insteon_local docs]: /components/light.insteon_local/ -[light.insteon_plm docs]: /components/light.insteon_plm/ -[light.isy994 docs]: /components/light.isy994/ -[light.lifx docs]: /components/light.lifx/ -[light.limitlessled docs]: /components/light.limitlessled/ -[light.mystrom docs]: /components/light.mystrom/ -[light.osramlightify docs]: /components/light.osramlightify/ -[light.tradfri docs]: /components/light.tradfri/ -[logbook docs]: /components/logbook/ -[lutron_caseta docs]: /components/lutron_caseta/ -[media_player.denonavr docs]: /components/media_player.denonavr/ -[media_player.kodi docs]: /components/media_player.kodi/ -[media_player.onkyo docs]: /components/media_player.onkyo/ -[media_player.roku docs]: /components/media_player.roku/ -[media_player.sonos docs]: /components/media_player.sonos/ -[media_player.spotify docs]: /components/media_player.spotify/ -[microsoft_face docs]: /components/microsoft_face/ -[notify.html5 docs]: /components/notify.html5/ -[notify.sendgrid docs]: /components/notify.sendgrid/ -[notify.smtp docs]: /components/notify.smtp/ -[notify.telegram docs]: /components/notify.telegram/ -[plant docs]: /components/plant/ -[raspihats docs]: /components/raspihats/ -[remote.kira docs]: /components/remote.kira/ -[rflink docs]: /components/rflink/ -[rpi_pfio docs]: /components/rpi_pfio/ -[sensor.blink docs]: /components/sensor.blink/ -[sensor.dweet docs]: /components/sensor.dweet/ -[sensor.envirophat docs]: /components/sensor.envirophat/ -[sensor.file docs]: /components/sensor.file/ -[sensor.influxdb docs]: /components/sensor.influxdb/ -[sensor.kira docs]: /components/sensor.kira/ -[sensor.miflora docs]: /components/sensor.miflora/ -[sensor.modem_callerid docs]: /components/sensor.modem_callerid/ -[sensor.nzbget docs]: /components/sensor.nzbget/ -[sensor.scrape docs]: /components/sensor.scrape/ -[sensor.snmp docs]: /components/sensor.snmp/ -[sensor.wunderground docs]: /components/sensor.wunderground/ -[sun docs]: /components/sun/ -[switch.rpi_pfio docs]: /components/switch.rpi_pfio/ -[telegram_bot docs]: /components/telegram_bot/ -[telegram_bot.polling docs]: /components/telegram_bot.polling/ -[telegram_bot.services.yaml docs]: /components/telegram_bot.services.yaml/ -[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/ -[tradfri docs]: /components/tradfri/ -[vera docs]: /components/vera/ -[websocket_api docs]: /components/websocket_api/ -[zwave docs]: /components/zwave/ -[zwave.api docs]: /components/zwave.api/ +[alexa docs]: https://home-assistant.io/components/alexa/ +[axis docs]: https://home-assistant.io/components/axis/ +[config.automation docs]: https://home-assistant.io/docs/automation/editor/ +[automation.event docs]: https://home-assistant.io/docs/configuration/events/ +[automation.state docs]: https://home-assistant.io/docs/configuration/state_object/ +[binary_sensor.mystrom docs]: https://home-assistant.io/components/binary_sensor.mystrom/ +[binary_sensor.raspihats docs]: https://home-assistant.io/components/binary_sensor.raspihats/ +[binary_sensor.rpi_pfio docs]: https://home-assistant.io/components/binary_sensor.rpi_pfio/ +[blink docs]: https://home-assistant.io/components/blink/ +[camera.__init__ docs]: https://home-assistant.io/components/camera.__init__/ +[camera.uvc docs]: https://home-assistant.io/components/camera.uvc/ +[camera.zoneminder docs]: https://home-assistant.io/components/camera.zoneminder/ +[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/ +[config.__init__ docs]: https://home-assistant.io/components/config.__init__/ +[configurator docs]: https://home-assistant.io/components/configurator/ +[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/ +[datadog docs]: https://home-assistant.io/components/datadog/ +[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/ +[device_tracker.linksys_ap docs]: https://home-assistant.io/components/device_tracker.linksys_ap/ +[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/ +[dweet docs]: https://home-assistant.io/components/dweet/ +[eight_sleep docs]: https://home-assistant.io/components/eight_sleep/ +[homematic docs]: https://home-assistant.io/components/homematic/ +[image_processing.__init__ docs]: https://home-assistant.io/components/image_processing.__init__/ +[image_processing.demo docs]: https://home-assistant.io/components/image_processing.demo/ +[image_processing.dlib_face_detect docs]: https://home-assistant.io/components/image_processing.dlib_face_detect/ +[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/ +[image_processing.microsoft_face_detect docs]: https://home-assistant.io/components/image_processing.microsoft_face_detect/ +[image_processing.microsoft_face_identify docs]: https://home-assistant.io/components/image_processing.microsoft_face_identify/ +[image_processing.openalpr_cloud docs]: https://home-assistant.io/components/image_processing.openalpr_cloud/ +[image_processing.openalpr_local docs]: https://home-assistant.io/components/image_processing.openalpr_local/ +[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/ +[image_processing.seven_segments docs]: https://home-assistant.io/components/image_processing.seven_segments/ +[kira docs]: https://home-assistant.io/components/kira/ +[light.__init__ docs]: https://home-assistant.io/components/light.__init__/ +[light.blinksticklight docs]: https://home-assistant.io/components/light.blinksticklight/ +[light.enocean docs]: https://home-assistant.io/components/light.enocean/ +[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/ +[light.insteon_local docs]: https://home-assistant.io/components/light.insteon_local/ +[light.insteon_plm docs]: https://home-assistant.io/components/light.insteon_plm/ +[light.isy994 docs]: https://home-assistant.io/components/light.isy994/ +[light.lifx docs]: https://home-assistant.io/components/light.lifx/ +[light.limitlessled docs]: https://home-assistant.io/components/light.limitlessled/ +[light.mystrom docs]: https://home-assistant.io/components/light.mystrom/ +[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/ +[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/ +[logbook docs]: https://home-assistant.io/components/logbook/ +[lutron_caseta docs]: https://home-assistant.io/components/lutron_caseta/ +[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/ +[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/ +[media_player.onkyo docs]: https://home-assistant.io/components/media_player.onkyo/ +[media_player.roku docs]: https://home-assistant.io/components/media_player.roku/ +[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/ +[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/ +[microsoft_face docs]: https://home-assistant.io/components/microsoft_face/ +[notify.html5 docs]: https://home-assistant.io/components/notify.html5/ +[notify.sendgrid docs]: https://home-assistant.io/components/notify.sendgrid/ +[notify.smtp docs]: https://home-assistant.io/components/notify.smtp/ +[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/ +[plant docs]: https://home-assistant.io/components/plant/ +[raspihats docs]: https://home-assistant.io/components/raspihats/ +[remote.kira docs]: https://home-assistant.io/components/remote.kira/ +[rflink docs]: https://home-assistant.io/components/rflink/ +[rpi_pfio docs]: https://home-assistant.io/components/rpi_pfio/ +[sensor.blink docs]: https://home-assistant.io/components/sensor.blink/ +[sensor.dweet docs]: https://home-assistant.io/components/sensor.dweet/ +[sensor.envirophat docs]: https://home-assistant.io/components/sensor.envirophat/ +[sensor.file docs]: https://home-assistant.io/components/sensor.file/ +[sensor.influxdb docs]: https://home-assistant.io/components/sensor.influxdb/ +[sensor.kira docs]: https://home-assistant.io/components/sensor.kira/ +[sensor.miflora docs]: https://home-assistant.io/components/sensor.miflora/ +[sensor.modem_callerid docs]: https://home-assistant.io/components/sensor.modem_callerid/ +[sensor.nzbget docs]: https://home-assistant.io/components/sensor.nzbget/ +[sensor.scrape docs]: https://home-assistant.io/components/sensor.scrape/ +[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/ +[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/ +[sun docs]: https://home-assistant.io/components/sun/ +[switch.rpi_pfio docs]: https://home-assistant.io/components/switch.rpi_pfio/ +[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/ +[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/ +[telegram_bot.services.yaml docs]: https://home-assistant.io/components/telegram_bot.services.yaml/ +[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/ +[tradfri docs]: https://home-assistant.io/components/tradfri/ +[vera docs]: https://home-assistant.io/components/vera/ +[websocket_api docs]: https://home-assistant.io/components/websocket_api/ +[zwave docs]: https://home-assistant.io/components/zwave/ +[zwave.api docs]: https://home-assistant.io/components/zwave.api/ [forum]: https://community.home-assistant.io/ [issue]: https://github.com/home-assistant/home-assistant/issues [#7673]: https://github.com/home-assistant/home-assistant/pull/7673 @@ -430,8 +430,8 @@ Experiencing issues introduced by this release? Please report them in our [issue [#7714]: https://github.com/home-assistant/home-assistant/pull/7714 [@cgtobi]: https://github.com/cgtobi [@tobygray]: https://github.com/tobygray -[device_tracker.ubus docs]: /components/device_tracker.ubus/ -[hassio docs]: /components/hassio/ -[media_player.volumio docs]: /components/media_player.volumio/ -[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/ +[device_tracker.ubus docs]: https://home-assistant.io/components/device_tracker.ubus/ +[hassio docs]: https://home-assistant.io/components/hassio/ +[media_player.volumio docs]: https://home-assistant.io/components/media_player.volumio/ +[telegram_bot.__init__ docs]: https://home-assistant.io/components/telegram_bot.__init__/ [discord]: https://discord.gg/c5DvZ4e diff --git a/source/_posts/2017-06-04-release-46.markdown b/source/_posts/2017-06-04-release-46.markdown index f514f61f9b..26ce625edf 100644 --- a/source/_posts/2017-06-04-release-46.markdown +++ b/source/_posts/2017-06-04-release-46.markdown @@ -307,80 +307,80 @@ Experiencing issues introduced by this release? Please report them in our [issue [@turbokongen]: https://github.com/turbokongen [@w1ll1am23]: https://github.com/w1ll1am23 [@wardcraigj]: https://github.com/wardcraigj -[alarm_control_panel.concord232 docs]: /components/alarm_control_panel.concord232/ -[apcupsd docs]: /components/apcupsd/ -[arlo docs]: /components/arlo/ -[automation.state docs]: /docs/automation/trigger/#state-trigger -[automation.time docs]: /docs/automation/trigger/#time-trigger -[calendar.demo docs]: /components/calendar.demo/ -[calendar.google docs]: /components/calendar.google/ -[camera.amcrest docs]: /components/camera.amcrest/ -[camera.arlo docs]: /components/camera.arlo/ -[camera.synology docs]: /components/camera.synology/ -[climate.tado docs]: /components/climate.tado/ -[cover.myq docs]: /components/cover.myq/ -[cover.zwave docs]: /components/cover.zwave/ -[device_tracker.__init__ docs]: /components/device_tracker.__init__/ -[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/ -[device_tracker.mikrotik docs]: /components/device_tracker.mikrotik/ -[device_tracker.snmp docs]: /components/device_tracker.snmp/ -[device_tracker.ubus docs]: /components/device_tracker.ubus/ -[eight_sleep docs]: /components/eight_sleep/ -[envisalink docs]: /components/envisalink/ -[fan.zwave docs]: /components/fan.zwave/ -[hassio docs]: /components/hassio/ -[homematic docs]: /components/homematic/ -[image_processing.seven_segments docs]: /components/image_processing.seven_segments/ -[insteon_local docs]: /components/insteon_local/ -[ios docs]: /components/ios/ -[light.__init__ docs]: /components/light.__init__/ -[light.flux_led docs]: /components/light.flux_led/ -[light.lifx docs]: /components/light.lifx/ -[light.template docs]: /components/light.template/ -[light.wink docs]: /components/light.wink/ -[lock.zwave docs]: /components/lock.zwave/ -[lutron docs]: /components/lutron/ -[media_player.denonavr docs]: /components/media_player.denonavr/ -[media_player.openhome docs]: /components/media_player.openhome/ -[media_player.services.yaml docs]: /components/media_player.services.yaml/ -[media_player.snapcast docs]: /components/media_player.snapcast/ -[media_player.sonos docs]: /components/media_player.sonos/ -[media_player.spotify docs]: /components/media_player.spotify/ -[media_player.volumio docs]: /components/media_player.volumio/ -[modbus docs]: /components/modbus/ -[mqtt.discovery docs]: /components/mqtt.discovery/ -[notify.ios docs]: /components/notify.ios/ -[notify.rest docs]: /components/notify.rest/ -[notify.slack docs]: /components/notify.slack/ -[notify.smtp docs]: /components/notify.smtp/ -[notify.telegram docs]: /components/notify.telegram/ -[recorder.__init__ docs]: /components/recorder.__init__/ -[remote docs]: /components/remote/ -[remote.harmony docs]: /components/remote.harmony/ -[remote.services.yaml docs]: /components/remote.services.yaml/ -[scene.hunterdouglas_powerview docs]: /components/scene.hunterdouglas_powerview/ -[sensor.amcrest docs]: /components/sensor.amcrest/ -[sensor.arlo docs]: /components/sensor.arlo/ -[sensor.dsmr docs]: /components/sensor.dsmr/ -[sensor.fedex docs]: /components/sensor.fedex/ -[sensor.history_stats docs]: /components/sensor.history_stats/ -[sensor.hp_ilo docs]: /components/sensor.hp_ilo/ -[sensor.influxdb docs]: /components/sensor.influxdb/ -[sensor.mvglive docs]: /components/sensor.mvglive/ -[sensor.snmp docs]: /components/sensor.snmp/ -[sensor.synologydsm docs]: /components/sensor.synologydsm/ -[sensor.time_date docs]: /components/sensor.time_date/ -[sensor.usps docs]: /components/sensor.usps/ -[switch.broadlink docs]: /components/switch.broadlink/ -[switch.rachio docs]: /components/switch.rachio/ -[switch.rflink docs]: /components/switch.rflink/ -[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/ -[telegram_bot.polling docs]: /components/telegram_bot.polling/ -[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/ -[tellduslive docs]: /components/tellduslive/ -[upnp docs]: /components/upnp/ -[zoneminder docs]: /components/zoneminder/ -[zwave docs]: /components/zwave/ +[alarm_control_panel.concord232 docs]: https://home-assistant.io/components/alarm_control_panel.concord232/ +[apcupsd docs]: https://home-assistant.io/components/apcupsd/ +[arlo docs]: https://home-assistant.io/components/arlo/ +[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger +[automation.time docs]: https://home-assistant.io/docs/automation/trigger/#time-trigger +[calendar.demo docs]: https://home-assistant.io/components/calendar.demo/ +[calendar.google docs]: https://home-assistant.io/components/calendar.google/ +[camera.amcrest docs]: https://home-assistant.io/components/camera.amcrest/ +[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/ +[camera.synology docs]: https://home-assistant.io/components/camera.synology/ +[climate.tado docs]: https://home-assistant.io/components/climate.tado/ +[cover.myq docs]: https://home-assistant.io/components/cover.myq/ +[cover.zwave docs]: https://home-assistant.io/components/cover.zwave/ +[device_tracker.__init__ docs]: https://home-assistant.io/components/device_tracker.__init__/ +[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/ +[device_tracker.mikrotik docs]: https://home-assistant.io/components/device_tracker.mikrotik/ +[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/ +[device_tracker.ubus docs]: https://home-assistant.io/components/device_tracker.ubus/ +[eight_sleep docs]: https://home-assistant.io/components/eight_sleep/ +[envisalink docs]: https://home-assistant.io/components/envisalink/ +[fan.zwave docs]: https://home-assistant.io/components/fan.zwave/ +[hassio docs]: https://home-assistant.io/components/hassio/ +[homematic docs]: https://home-assistant.io/components/homematic/ +[image_processing.seven_segments docs]: https://home-assistant.io/components/image_processing.seven_segments/ +[insteon_local docs]: https://home-assistant.io/components/insteon_local/ +[ios docs]: https://home-assistant.io/components/ios/ +[light.__init__ docs]: https://home-assistant.io/components/light.__init__/ +[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/ +[light.lifx docs]: https://home-assistant.io/components/light.lifx/ +[light.template docs]: https://home-assistant.io/components/light.template/ +[light.wink docs]: https://home-assistant.io/components/light.wink/ +[lock.zwave docs]: https://home-assistant.io/components/lock.zwave/ +[lutron docs]: https://home-assistant.io/components/lutron/ +[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/ +[media_player.openhome docs]: https://home-assistant.io/components/media_player.openhome/ +[media_player.services.yaml docs]: https://home-assistant.io/components/media_player.services.yaml/ +[media_player.snapcast docs]: https://home-assistant.io/components/media_player.snapcast/ +[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/ +[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/ +[media_player.volumio docs]: https://home-assistant.io/components/media_player.volumio/ +[modbus docs]: https://home-assistant.io/components/modbus/ +[mqtt.discovery docs]: https://home-assistant.io/components/mqtt.discovery/ +[notify.ios docs]: https://home-assistant.io/components/notify.ios/ +[notify.rest docs]: https://home-assistant.io/components/notify.rest/ +[notify.slack docs]: https://home-assistant.io/components/notify.slack/ +[notify.smtp docs]: https://home-assistant.io/components/notify.smtp/ +[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/ +[recorder.__init__ docs]: https://home-assistant.io/components/recorder.__init__/ +[remote docs]: https://home-assistant.io/components/remote/ +[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/ +[remote.services.yaml docs]: https://home-assistant.io/components/remote.services.yaml/ +[scene.hunterdouglas_powerview docs]: https://home-assistant.io/components/scene.hunterdouglas_powerview/ +[sensor.amcrest docs]: https://home-assistant.io/components/sensor.amcrest/ +[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/ +[sensor.dsmr docs]: https://home-assistant.io/components/sensor.dsmr/ +[sensor.fedex docs]: https://home-assistant.io/components/sensor.fedex/ +[sensor.history_stats docs]: https://home-assistant.io/components/sensor.history_stats/ +[sensor.hp_ilo docs]: https://home-assistant.io/components/sensor.hp_ilo/ +[sensor.influxdb docs]: https://home-assistant.io/components/sensor.influxdb/ +[sensor.mvglive docs]: https://home-assistant.io/components/sensor.mvglive/ +[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/ +[sensor.synologydsm docs]: https://home-assistant.io/components/sensor.synologydsm/ +[sensor.time_date docs]: https://home-assistant.io/components/sensor.time_date/ +[sensor.usps docs]: https://home-assistant.io/components/sensor.usps/ +[switch.broadlink docs]: https://home-assistant.io/components/switch.broadlink/ +[switch.rachio docs]: https://home-assistant.io/components/switch.rachio/ +[switch.rflink docs]: https://home-assistant.io/components/switch.rflink/ +[telegram_bot.__init__ docs]: https://home-assistant.io/components/telegram_bot.__init__/ +[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/ +[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/ +[tellduslive docs]: https://home-assistant.io/components/tellduslive/ +[upnp docs]: https://home-assistant.io/components/upnp/ +[zoneminder docs]: https://home-assistant.io/components/zoneminder/ +[zwave docs]: https://home-assistant.io/components/zwave/ [forum]: https://community.home-assistant.io/ [issue]: https://github.com/home-assistant/home-assistant/issues [#7780]: https://github.com/home-assistant/home-assistant/pull/7780 @@ -392,8 +392,8 @@ Experiencing issues introduced by this release? Please report them in our [issue [#7969]: https://github.com/home-assistant/home-assistant/pull/7969 [@cyberjacob]: https://github.com/cyberjacob [@mje-nz]: https://github.com/mje-nz -[cover.mqtt docs]: /components/cover.mqtt/ -[sensor.metoffice docs]: /components/sensor.metoffice/ -[sensor.wunderground docs]: /components/sensor.wunderground/ -[media_player.roku docs]: /components/media_player.roku/ +[cover.mqtt docs]: https://home-assistant.io/components/cover.mqtt/ +[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/ +[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/ +[media_player.roku docs]: https://home-assistant.io/components/media_player.roku/ [discord]: https://discord.gg/c5DvZ4e diff --git a/source/_posts/2017-06-17-release-47.markdown b/source/_posts/2017-06-17-release-47.markdown index b91503b06d..548f62fa45 100644 --- a/source/_posts/2017-06-17-release-47.markdown +++ b/source/_posts/2017-06-17-release-47.markdown @@ -448,130 +448,130 @@ automation: [@trisk]: https://github.com/trisk [@twendt]: https://github.com/twendt [@vrs01]: https://github.com/vrs01 -[alarm_control_panel.spc docs]: /components/alarm_control_panel.spc/ -[binary_sensor.enocean docs]: /components/binary_sensor.enocean/ -[binary_sensor.homematic docs]: /components/binary_sensor.homematic/ -[binary_sensor.spc docs]: /components/binary_sensor.spc/ -[binary_sensor.tapsaff docs]: /components/binary_sensor.tapsaff/ -[calendar.google docs]: /components/calendar.google/ -[climate.flexit docs]: /components/climate.flexit/ -[climate.wink docs]: /components/climate.wink/ -[conversation docs]: /components/conversation/ -[cover.homematic docs]: /components/cover.homematic/ -[cover.mqtt docs]: /components/cover.mqtt/ -[cover.myq docs]: /components/cover.myq/ -[device_tracker.__init__ docs]: /components/device_tracker.__init__/ -[device_tracker.owntracks docs]: /components/device_tracker.owntracks/ -[device_tracker.ping docs]: /components/device_tracker.ping/ -[device_tracker.snmp docs]: /components/device_tracker.snmp/ -[device_tracker.unifi docs]: /components/device_tracker.unifi/ -[eight_sleep docs]: /components/eight_sleep/ -[fan.__init__ docs]: /components/fan.__init__/ -[fan.demo docs]: /components/fan.demo/ -[fan.zwave docs]: /components/fan.zwave/ -[group docs]: /components/group/ -[homematic docs]: /components/homematic/ -[http docs]: /components/http/ -[image_processing.opencv docs]: /components/image_processing.opencv/ -[image_processing.seven_segments docs]: /components/image_processing.seven_segments/ -[influxdb docs]: /components/influxdb/ -[juicenet docs]: /components/juicenet/ -[light.lifx docs]: /components/light.lifx/ -[light.lutron docs]: /components/light.lutron/ -[light.osramlightify docs]: /components/light.osramlightify/ -[light.template docs]: /components/light.template/ -[light.vera docs]: /components/light.vera/ -[light.yeelight docs]: /components/light.yeelight/ -[light.zwave docs]: /components/light.zwave/ -[lock.sesame docs]: /components/lock.sesame/ -[lutron docs]: /components/lutron/ -[mailgun docs]: /components/mailgun/ -[media_player.aquostv docs]: /components/media_player.aquostv/ -[media_player.denonavr docs]: /components/media_player.denonavr/ -[media_player.firetv docs]: /components/media_player.firetv/ -[media_player.nad docs]: /components/media_player.nad/ -[media_player.nadtcp docs]: /components/media_player.nadtcp/ -[media_player.openhome docs]: /components/media_player.openhome/ -[media_player.plex docs]: /components/media_player.plex/ -[media_player.roku docs]: /components/media_player.roku/ -[media_player.sonos docs]: /components/media_player.sonos/ -[media_player.spotify docs]: /components/media_player.spotify/ -[media_player.squeezebox docs]: /components/media_player.squeezebox/ -[mqtt.__init__ docs]: /components/mqtt.__init__/ -[nest docs]: /components/nest/ -[netatmo docs]: /components/netatmo/ -[notify.html5 docs]: /components/notify.html5/ -[notify.mailgun docs]: /components/notify.mailgun/ -[notify.sendgrid docs]: /components/notify.sendgrid/ -[notify.xmpp docs]: /components/notify.xmpp/ -[opencv docs]: /components/opencv/ -[persistent_notification docs]: /components/persistent_notification/ -[plant docs]: /components/plant/ -[python_script docs]: /components/python_script/ -[sensor.bitcoin docs]: /components/sensor.bitcoin/ -[sensor.blockchain docs]: /components/sensor.blockchain/ -[sensor.buienradar docs]: /components/sensor.buienradar/ -[sensor.coinmarketcap docs]: /components/sensor.coinmarketcap/ -[sensor.cpuspeed docs]: /components/sensor.cpuspeed/ -[sensor.cups docs]: /components/sensor.cups/ -[sensor.currencylayer docs]: /components/sensor.currencylayer/ -[sensor.dsmr docs]: /components/sensor.dsmr/ -[sensor.dte_energy_bridge docs]: /components/sensor.dte_energy_bridge/ -[sensor.dublin_bus_transport docs]: /components/sensor.dublin_bus_transport/ -[sensor.dweet docs]: /components/sensor.dweet/ -[sensor.ebox docs]: /components/sensor.ebox/ -[sensor.ecobee docs]: /components/sensor.ecobee/ -[sensor.eliqonline docs]: /components/sensor.eliqonline/ -[sensor.etherscan docs]: /components/sensor.etherscan/ -[sensor.fixer docs]: /components/sensor.fixer/ -[sensor.gitter docs]: /components/sensor.gitter/ -[sensor.hddtemp docs]: /components/sensor.hddtemp/ -[sensor.homematic docs]: /components/sensor.homematic/ -[sensor.imap_email_content docs]: /components/sensor.imap_email_content/ -[sensor.juicenet docs]: /components/sensor.juicenet/ -[sensor.metoffice docs]: /components/sensor.metoffice/ -[sensor.mold_indicator docs]: /components/sensor.mold_indicator/ -[sensor.netatmo docs]: /components/sensor.netatmo/ -[sensor.openevse docs]: /components/sensor.openevse/ -[sensor.pi_hole docs]: /components/sensor.pi_hole/ -[sensor.pvoutput docs]: /components/sensor.pvoutput/ -[sensor.radarr docs]: /components/sensor.radarr/ -[sensor.ripple docs]: /components/sensor.ripple/ -[sensor.snmp docs]: /components/sensor.snmp/ -[sensor.statistics docs]: /components/sensor.statistics/ -[sensor.template docs]: /components/sensor.template/ -[sensor.ups docs]: /components/sensor.ups/ -[sensor.usps docs]: /components/sensor.usps/ -[sensor.waqi docs]: /components/sensor.waqi/ -[sensor.wunderground docs]: /components/sensor.wunderground/ -[sensor.yahoo_finance docs]: /components/sensor.yahoo_finance/ -[sensor.yweather docs]: /components/sensor.yweather/ -[spc docs]: /components/spc/ -[splunk docs]: /components/splunk/ -[switch.homematic docs]: /components/switch.homematic/ -[switch.raspihats docs]: /components/switch.raspihats/ -[switch.rest docs]: /components/switch.rest/ -[switch.template docs]: /components/switch.template/ -[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/ -[telegram_bot.polling docs]: /components/telegram_bot.polling/ -[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/ -[updater docs]: /components/updater/ -[vera docs]: /components/vera/ -[volvooncall docs]: /components/volvooncall/ -[weather.buienradar docs]: /components/weather.buienradar/ -[zeroconf docs]: /components/zeroconf/ -[zwave docs]: /components/zwave/ -[zwave blog post]: /blog/2017/06/15/zwave-entity-ids/ +[alarm_control_panel.spc docs]: https://home-assistant.io/components/alarm_control_panel.spc/ +[binary_sensor.enocean docs]: https://home-assistant.io/components/binary_sensor.enocean/ +[binary_sensor.homematic docs]: https://home-assistant.io/components/binary_sensor.homematic/ +[binary_sensor.spc docs]: https://home-assistant.io/components/binary_sensor.spc/ +[binary_sensor.tapsaff docs]: https://home-assistant.io/components/binary_sensor.tapsaff/ +[calendar.google docs]: https://home-assistant.io/components/calendar.google/ +[climate.flexit docs]: https://home-assistant.io/components/climate.flexit/ +[climate.wink docs]: https://home-assistant.io/components/climate.wink/ +[conversation docs]: https://home-assistant.io/components/conversation/ +[cover.homematic docs]: https://home-assistant.io/components/cover.homematic/ +[cover.mqtt docs]: https://home-assistant.io/components/cover.mqtt/ +[cover.myq docs]: https://home-assistant.io/components/cover.myq/ +[device_tracker.__init__ docs]: https://home-assistant.io/components/device_tracker.__init__/ +[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/ +[device_tracker.ping docs]: https://home-assistant.io/components/device_tracker.ping/ +[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/ +[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/ +[eight_sleep docs]: https://home-assistant.io/components/eight_sleep/ +[fan.__init__ docs]: https://home-assistant.io/components/fan.__init__/ +[fan.demo docs]: https://home-assistant.io/components/fan.demo/ +[fan.zwave docs]: https://home-assistant.io/components/fan.zwave/ +[group docs]: https://home-assistant.io/components/group/ +[homematic docs]: https://home-assistant.io/components/homematic/ +[http docs]: https://home-assistant.io/components/http/ +[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/ +[image_processing.seven_segments docs]: https://home-assistant.io/components/image_processing.seven_segments/ +[influxdb docs]: https://home-assistant.io/components/influxdb/ +[juicenet docs]: https://home-assistant.io/components/juicenet/ +[light.lifx docs]: https://home-assistant.io/components/light.lifx/ +[light.lutron docs]: https://home-assistant.io/components/light.lutron/ +[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/ +[light.template docs]: https://home-assistant.io/components/light.template/ +[light.vera docs]: https://home-assistant.io/components/light.vera/ +[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/ +[light.zwave docs]: https://home-assistant.io/components/light.zwave/ +[lock.sesame docs]: https://home-assistant.io/components/lock.sesame/ +[lutron docs]: https://home-assistant.io/components/lutron/ +[mailgun docs]: https://home-assistant.io/components/mailgun/ +[media_player.aquostv docs]: https://home-assistant.io/components/media_player.aquostv/ +[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/ +[media_player.firetv docs]: https://home-assistant.io/components/media_player.firetv/ +[media_player.nad docs]: https://home-assistant.io/components/media_player.nad/ +[media_player.nadtcp docs]: https://home-assistant.io/components/media_player.nadtcp/ +[media_player.openhome docs]: https://home-assistant.io/components/media_player.openhome/ +[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/ +[media_player.roku docs]: https://home-assistant.io/components/media_player.roku/ +[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/ +[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/ +[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/ +[mqtt.__init__ docs]: https://home-assistant.io/components/mqtt.__init__/ +[nest docs]: https://home-assistant.io/components/nest/ +[netatmo docs]: https://home-assistant.io/components/netatmo/ +[notify.html5 docs]: https://home-assistant.io/components/notify.html5/ +[notify.mailgun docs]: https://home-assistant.io/components/notify.mailgun/ +[notify.sendgrid docs]: https://home-assistant.io/components/notify.sendgrid/ +[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/ +[opencv docs]: https://home-assistant.io/components/opencv/ +[persistent_notification docs]: https://home-assistant.io/components/persistent_notification/ +[plant docs]: https://home-assistant.io/components/plant/ +[python_script docs]: https://home-assistant.io/components/python_script/ +[sensor.bitcoin docs]: https://home-assistant.io/components/sensor.bitcoin/ +[sensor.blockchain docs]: https://home-assistant.io/components/sensor.blockchain/ +[sensor.buienradar docs]: https://home-assistant.io/components/sensor.buienradar/ +[sensor.coinmarketcap docs]: https://home-assistant.io/components/sensor.coinmarketcap/ +[sensor.cpuspeed docs]: https://home-assistant.io/components/sensor.cpuspeed/ +[sensor.cups docs]: https://home-assistant.io/components/sensor.cups/ +[sensor.currencylayer docs]: https://home-assistant.io/components/sensor.currencylayer/ +[sensor.dsmr docs]: https://home-assistant.io/components/sensor.dsmr/ +[sensor.dte_energy_bridge docs]: https://home-assistant.io/components/sensor.dte_energy_bridge/ +[sensor.dublin_bus_transport docs]: https://home-assistant.io/components/sensor.dublin_bus_transport/ +[sensor.dweet docs]: https://home-assistant.io/components/sensor.dweet/ +[sensor.ebox docs]: https://home-assistant.io/components/sensor.ebox/ +[sensor.ecobee docs]: https://home-assistant.io/components/sensor.ecobee/ +[sensor.eliqonline docs]: https://home-assistant.io/components/sensor.eliqonline/ +[sensor.etherscan docs]: https://home-assistant.io/components/sensor.etherscan/ +[sensor.fixer docs]: https://home-assistant.io/components/sensor.fixer/ +[sensor.gitter docs]: https://home-assistant.io/components/sensor.gitter/ +[sensor.hddtemp docs]: https://home-assistant.io/components/sensor.hddtemp/ +[sensor.homematic docs]: https://home-assistant.io/components/sensor.homematic/ +[sensor.imap_email_content docs]: https://home-assistant.io/components/sensor.imap_email_content/ +[sensor.juicenet docs]: https://home-assistant.io/components/sensor.juicenet/ +[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/ +[sensor.mold_indicator docs]: https://home-assistant.io/components/sensor.mold_indicator/ +[sensor.netatmo docs]: https://home-assistant.io/components/sensor.netatmo/ +[sensor.openevse docs]: https://home-assistant.io/components/sensor.openevse/ +[sensor.pi_hole docs]: https://home-assistant.io/components/sensor.pi_hole/ +[sensor.pvoutput docs]: https://home-assistant.io/components/sensor.pvoutput/ +[sensor.radarr docs]: https://home-assistant.io/components/sensor.radarr/ +[sensor.ripple docs]: https://home-assistant.io/components/sensor.ripple/ +[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/ +[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/ +[sensor.template docs]: https://home-assistant.io/components/sensor.template/ +[sensor.ups docs]: https://home-assistant.io/components/sensor.ups/ +[sensor.usps docs]: https://home-assistant.io/components/sensor.usps/ +[sensor.waqi docs]: https://home-assistant.io/components/sensor.waqi/ +[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/ +[sensor.yahoo_finance docs]: https://home-assistant.io/components/sensor.yahoo_finance/ +[sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/ +[spc docs]: https://home-assistant.io/components/spc/ +[splunk docs]: https://home-assistant.io/components/splunk/ +[switch.homematic docs]: https://home-assistant.io/components/switch.homematic/ +[switch.raspihats docs]: https://home-assistant.io/components/switch.raspihats/ +[switch.rest docs]: https://home-assistant.io/components/switch.rest/ +[switch.template docs]: https://home-assistant.io/components/switch.template/ +[telegram_bot.__init__ docs]: https://home-assistant.io/components/telegram_bot.__init__/ +[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/ +[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/ +[updater docs]: https://home-assistant.io/components/updater/ +[vera docs]: https://home-assistant.io/components/vera/ +[volvooncall docs]: https://home-assistant.io/components/volvooncall/ +[weather.buienradar docs]: https://home-assistant.io/components/weather.buienradar/ +[zeroconf docs]: https://home-assistant.io/components/zeroconf/ +[zwave docs]: https://home-assistant.io/components/zwave/ +[zwave blog post]: https://home-assistant.io/blog/2017/06/15/zwave-entity-ids/ [forum]: https://community.home-assistant.io/ [issue]: https://github.com/home-assistant/home-assistant/issues -[first-commit]: /help/trivia/#first-commit +[first-commit]: https://home-assistant.io/help/trivia/#first-commit [#8080]: https://github.com/home-assistant/home-assistant/pull/8080 [#8101]: https://github.com/home-assistant/home-assistant/pull/8101 [#8104]: https://github.com/home-assistant/home-assistant/pull/8104 [#8113]: https://github.com/home-assistant/home-assistant/pull/8113 [#8134]: https://github.com/home-assistant/home-assistant/pull/8134 [@tsvi]: https://github.com/tsvi -[fan.dyson docs]: /components/fan.dyson/ -[remote.itach docs]: /components/remote.itach/ -[sensor.dyson docs]: /components/sensor.dyson/ +[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/ +[remote.itach docs]: https://home-assistant.io/components/remote.itach/ +[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/ [discord]: https://discord.gg/c5DvZ4e diff --git a/source/_posts/2017-07-02-release-48.markdown b/source/_posts/2017-07-02-release-48.markdown index 3dc0835b55..4fc39bea01 100644 --- a/source/_posts/2017-07-02-release-48.markdown +++ b/source/_posts/2017-07-02-release-48.markdown @@ -28,13 +28,13 @@ zwave: ## {% linkable_title Big speed up in querying the history %} -Thanks to the work by [@cmsimike] in [#8255] you'll see a significant speed up when using the history view. In his local tests queries went from 1 minute to 90ms! ⚡️ +Thanks to the work by [@cmsimike] in [#8255] you'll see a significant speed up when using the history view. In his local tests queries went from 1 minute to 90ms! ⚡️ ## {% linkable_title Snips.ai component %} Snips has contributed a component to integrate with their Snips.ai local voice assistant. This will allow you to hook a speaker and a microphone into your Raspberry Pi and make your own local Amazon Echo quickly. See [the docs][snips docs] for further instructions. -Also a shoutout to [@michaelarnauts] for keeping an eye on our Docker build and once again reducing the file size 👍 +Also a shoutout to [@michaelarnauts] for keeping an eye on our Docker build and once again reducing the file size 👍 [issue-polymer]: https://github.com/home-assistant/home-assistant-polymer/issues @@ -530,9 +530,9 @@ light: [#8336]: https://github.com/home-assistant/home-assistant/pull/8336 [@adrienball]: https://github.com/adrienball [@bergemalm]: https://github.com/bergemalm -[api docs]: /components/api/ -[camera.arlo docs]: /components/camera.arlo/ -[mqtt docs]: /components/mqtt/ -[remote.harmony docs]: /components/remote.harmony/ -[sensor.arlo docs]: /components/sensor.arlo/ -[snips docs]: /components/snips/ +[api docs]: https://home-assistant.io/components/api/ +[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/ +[mqtt docs]: https://home-assistant.io/components/mqtt/ +[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/ +[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/ +[snips docs]: https://home-assistant.io/components/snips/ diff --git a/source/_posts/2017-07-03-home-assistant-is-moving-to-discord.markdown b/source/_posts/2017-07-03-home-assistant-is-moving-to-discord.markdown index f85c83c020..fc40dfa617 100644 --- a/source/_posts/2017-07-03-home-assistant-is-moving-to-discord.markdown +++ b/source/_posts/2017-07-03-home-assistant-is-moving-to-discord.markdown @@ -86,5 +86,5 @@ Community Leader, Home Assistant [discord]: https://discord.gg/c5DvZ4e [discord-devs]: https://discord.gg/8X8DTH4 [discord-general]: https://discord.gg/pywKZRT -[FAQ]: /faq/ -[docs]: /docs/ +[FAQ]: https://home-assistant.io/faq/ +[docs]: https://home-assistant.io/docs/ diff --git a/source/_posts/2017-07-16-release-49.markdown b/source/_posts/2017-07-16-release-49.markdown index 09a24ce1f7..81aaab898a 100644 --- a/source/_posts/2017-07-16-release-49.markdown +++ b/source/_posts/2017-07-16-release-49.markdown @@ -375,105 +375,105 @@ amcrest: [@w1ll1am23]: https://github.com/w1ll1am23 [@wardcraigj]: https://github.com/wardcraigj [@wmalgadey]: https://github.com/wmalgadey -[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/ -[amcrest docs]: /components/amcrest/ -[apcupsd docs]: /components/apcupsd/ -[binary_sensor.hikvision docs]: /components/binary_sensor.hikvision/ -[binary_sensor.modbus docs]: /components/binary_sensor.modbus/ -[binary_sensor.octoprint docs]: /components/binary_sensor.octoprint/ -[binary_sensor.pilight docs]: /components/binary_sensor.pilight/ -[binary_sensor.zha docs]: /components/binary_sensor.zha/ -[camera.amcrest docs]: /components/camera.amcrest/ -[camera.arlo docs]: /components/camera.arlo/ -[climate.flexit docs]: /components/climate.flexit/ -[climate.generic_thermostat docs]: /components/climate.generic_thermostat/ -[climate.radiotherm docs]: /components/climate.radiotherm/ -[climate.tado docs]: /components/climate.tado/ -[cover.template docs]: /components/cover.template/ -[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/ -[device_tracker.linksys_smart docs]: /components/device_tracker.linksys_smart/ -[device_tracker.tplink docs]: /components/device_tracker.tplink/ -[device_tracker.upc_connect docs]: /components/device_tracker.upc_connect/ -[dyson docs]: /components/dyson/ -[fan.dyson docs]: /components/fan.dyson/ -[group docs]: /components/group/ -[hassio docs]: /hassio/ -[homematic docs]: /components/homematic/ -[image_processing.dlib_face_detect docs]: /components/image_processing.dlib_face_detect/ -[image_processing.dlib_face_identify docs]: /components/image_processing.dlib_face_identify/ -[knx docs]: /components/knx/ -[lametric docs]: /components/lametric/ -[light.avion docs]: /components/light.avion/ -[light.decora docs]: /components/light.decora/ -[light.hue docs]: /components/light.hue/ -[light.hyperion docs]: /components/light.hyperion/ -[light.knx docs]: /components/light.knx/ -[light.lifx docs]: /components/light.lifx/ -[light.mystrom docs]: /components/light.mystrom/ -[light.rflink docs]: /components/light.rflink/ -[light.zha docs]: /components/light.zha/ -[lutron docs]: /components/lutron/ -[media_extractor docs]: /components/media_extractor/ -[media_player.apple_tv docs]: /components/media_player.apple_tv/ -[media_player.denonavr docs]: /components/media_player.denonavr/ -[media_player.emby docs]: /components/media_player.emby/ -[media_player.plex docs]: /components/media_player.plex/ -[media_player.soundtouch docs]: /components/media_player.soundtouch/ -[media_player.spotify docs]: /components/media_player.spotify/ -[media_player.vizio docs]: /components/media_player.vizio/ -[modbus docs]: /components/modbus/ -[mqtt docs]: /components/mqtt/ -[notify docs]: /components/notify/ -[notify.discord docs]: /components/notify.discord/ -[notify.lametric docs]: /components/notify.lametric/ -[notify.slack docs]: /components/notify.slack/ -[notify.twitter docs]: /components/notify.twitter/ -[octoprint docs]: /components/octoprint/ -[prometheus docs]: /components/prometheus/ -[python_script docs]: /components/python_script/ -[recorder docs]: /components/recorder/ -[rflink docs]: /components/rflink/ -[rfxtrx docs]: /components/rfxtrx/ -[scene.velux docs]: /components/scene.velux/ -[sensor.amcrest docs]: /components/sensor.amcrest/ -[sensor.apcupsd docs]: /components/sensor.apcupsd/ -[sensor.arwn docs]: /components/sensor.arwn/ -[sensor.broadlink docs]: /components/sensor.broadlink/ -[sensor.buienradar docs]: /components/sensor.buienradar/ -[sensor.citybikes docs]: /components/sensor.citybikes/ -[sensor.dht docs]: /components/sensor.dht/ -[sensor.dyson docs]: /components/sensor.dyson/ -[sensor.gtfs docs]: /components/sensor.gtfs/ -[sensor.london_underground docs]: /components/sensor.london_underground/ -[sensor.modbus docs]: /components/sensor.modbus/ -[sensor.octoprint docs]: /components/sensor.octoprint/ -[sensor.openweathermap docs]: /components/sensor.openweathermap/ -[sensor.otp docs]: /components/sensor.otp/ -[sensor.rflink docs]: /components/sensor.rflink/ -[sensor.uber docs]: /components/sensor.uber/ -[sensor.waqi docs]: /components/sensor.waqi/ -[sensor.yweather docs]: /components/sensor.yweather/ -[sensor.zha docs]: /components/sensor.zha/ -[snips docs]: /components/snips/ -[switch.broadlink docs]: /components/switch.broadlink/ -[switch.dlink docs]: /components/switch.dlink/ -[switch.modbus docs]: /components/switch.modbus/ -[switch.rachio docs]: /components/switch.rachio/ -[switch.rflink docs]: /components/switch.rflink/ -[switch.xiaomi_vacuum docs]: /components/switch.xiaomi_vacuum/ -[tado docs]: /components/tado/ -[tts docs]: /components/tts/ -[tts.amazon_polly docs]: /components/tts.amazon_polly/ -[upnp docs]: /components/upnp/ -[velux docs]: /components/velux/ -[frontend docs]: /components/frontend/ -[vera docs]: /components/vera/ -[verisure docs]: /components/verisure/ -[wake_on_lan docs]: /components/wake_on_lan/ -[weather.buienradar docs]: /components/weather.buienradar/ -[weather.openweathermap docs]: /components/weather.openweathermap/ -[zha docs]: /components/zha/ -[zha.const docs]: /components/zha.const/ +[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/ +[amcrest docs]: https://home-assistant.io/components/amcrest/ +[apcupsd docs]: https://home-assistant.io/components/apcupsd/ +[binary_sensor.hikvision docs]: https://home-assistant.io/components/binary_sensor.hikvision/ +[binary_sensor.modbus docs]: https://home-assistant.io/components/binary_sensor.modbus/ +[binary_sensor.octoprint docs]: https://home-assistant.io/components/binary_sensor.octoprint/ +[binary_sensor.pilight docs]: https://home-assistant.io/components/binary_sensor.pilight/ +[binary_sensor.zha docs]: https://home-assistant.io/components/binary_sensor.zha/ +[camera.amcrest docs]: https://home-assistant.io/components/camera.amcrest/ +[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/ +[climate.flexit docs]: https://home-assistant.io/components/climate.flexit/ +[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/ +[climate.radiotherm docs]: https://home-assistant.io/components/climate.radiotherm/ +[climate.tado docs]: https://home-assistant.io/components/climate.tado/ +[cover.template docs]: https://home-assistant.io/components/cover.template/ +[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/ +[device_tracker.linksys_smart docs]: https://home-assistant.io/components/device_tracker.linksys_smart/ +[device_tracker.tplink docs]: https://home-assistant.io/components/device_tracker.tplink/ +[device_tracker.upc_connect docs]: https://home-assistant.io/components/device_tracker.upc_connect/ +[dyson docs]: https://home-assistant.io/components/dyson/ +[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/ +[group docs]: https://home-assistant.io/components/group/ +[hassio docs]: https://home-assistant.io/hassio/ +[homematic docs]: https://home-assistant.io/components/homematic/ +[image_processing.dlib_face_detect docs]: https://home-assistant.io/components/image_processing.dlib_face_detect/ +[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/ +[knx docs]: https://home-assistant.io/components/knx/ +[lametric docs]: https://home-assistant.io/components/lametric/ +[light.avion docs]: https://home-assistant.io/components/light.avion/ +[light.decora docs]: https://home-assistant.io/components/light.decora/ +[light.hue docs]: https://home-assistant.io/components/light.hue/ +[light.hyperion docs]: https://home-assistant.io/components/light.hyperion/ +[light.knx docs]: https://home-assistant.io/components/light.knx/ +[light.lifx docs]: https://home-assistant.io/components/light.lifx/ +[light.mystrom docs]: https://home-assistant.io/components/light.mystrom/ +[light.rflink docs]: https://home-assistant.io/components/light.rflink/ +[light.zha docs]: https://home-assistant.io/components/light.zha/ +[lutron docs]: https://home-assistant.io/components/lutron/ +[media_extractor docs]: https://home-assistant.io/components/media_extractor/ +[media_player.apple_tv docs]: https://home-assistant.io/components/media_player.apple_tv/ +[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/ +[media_player.emby docs]: https://home-assistant.io/components/media_player.emby/ +[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/ +[media_player.soundtouch docs]: https://home-assistant.io/components/media_player.soundtouch/ +[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/ +[media_player.vizio docs]: https://home-assistant.io/components/media_player.vizio/ +[modbus docs]: https://home-assistant.io/components/modbus/ +[mqtt docs]: https://home-assistant.io/components/mqtt/ +[notify docs]: https://home-assistant.io/components/notify/ +[notify.discord docs]: https://home-assistant.io/components/notify.discord/ +[notify.lametric docs]: https://home-assistant.io/components/notify.lametric/ +[notify.slack docs]: https://home-assistant.io/components/notify.slack/ +[notify.twitter docs]: https://home-assistant.io/components/notify.twitter/ +[octoprint docs]: https://home-assistant.io/components/octoprint/ +[prometheus docs]: https://home-assistant.io/components/prometheus/ +[python_script docs]: https://home-assistant.io/components/python_script/ +[recorder docs]: https://home-assistant.io/components/recorder/ +[rflink docs]: https://home-assistant.io/components/rflink/ +[rfxtrx docs]: https://home-assistant.io/components/rfxtrx/ +[scene.velux docs]: https://home-assistant.io/components/scene.velux/ +[sensor.amcrest docs]: https://home-assistant.io/components/sensor.amcrest/ +[sensor.apcupsd docs]: https://home-assistant.io/components/sensor.apcupsd/ +[sensor.arwn docs]: https://home-assistant.io/components/sensor.arwn/ +[sensor.broadlink docs]: https://home-assistant.io/components/sensor.broadlink/ +[sensor.buienradar docs]: https://home-assistant.io/components/sensor.buienradar/ +[sensor.citybikes docs]: https://home-assistant.io/components/sensor.citybikes/ +[sensor.dht docs]: https://home-assistant.io/components/sensor.dht/ +[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/ +[sensor.gtfs docs]: https://home-assistant.io/components/sensor.gtfs/ +[sensor.london_underground docs]: https://home-assistant.io/components/sensor.london_underground/ +[sensor.modbus docs]: https://home-assistant.io/components/sensor.modbus/ +[sensor.octoprint docs]: https://home-assistant.io/components/sensor.octoprint/ +[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/ +[sensor.otp docs]: https://home-assistant.io/components/sensor.otp/ +[sensor.rflink docs]: https://home-assistant.io/components/sensor.rflink/ +[sensor.uber docs]: https://home-assistant.io/components/sensor.uber/ +[sensor.waqi docs]: https://home-assistant.io/components/sensor.waqi/ +[sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/ +[sensor.zha docs]: https://home-assistant.io/components/sensor.zha/ +[snips docs]: https://home-assistant.io/components/snips/ +[switch.broadlink docs]: https://home-assistant.io/components/switch.broadlink/ +[switch.dlink docs]: https://home-assistant.io/components/switch.dlink/ +[switch.modbus docs]: https://home-assistant.io/components/switch.modbus/ +[switch.rachio docs]: https://home-assistant.io/components/switch.rachio/ +[switch.rflink docs]: https://home-assistant.io/components/switch.rflink/ +[switch.xiaomi_vacuum docs]: https://home-assistant.io/components/switch.xiaomi_vacuum/ +[tado docs]: https://home-assistant.io/components/tado/ +[tts docs]: https://home-assistant.io/components/tts/ +[tts.amazon_polly docs]: https://home-assistant.io/components/tts.amazon_polly/ +[upnp docs]: https://home-assistant.io/components/upnp/ +[velux docs]: https://home-assistant.io/components/velux/ +[frontend docs]: https://home-assistant.io/components/frontend/ +[vera docs]: https://home-assistant.io/components/vera/ +[verisure docs]: https://home-assistant.io/components/verisure/ +[wake_on_lan docs]: https://home-assistant.io/components/wake_on_lan/ +[weather.buienradar docs]: https://home-assistant.io/components/weather.buienradar/ +[weather.openweathermap docs]: https://home-assistant.io/components/weather.openweathermap/ +[zha docs]: https://home-assistant.io/components/zha/ +[zha.const docs]: https://home-assistant.io/components/zha.const/ [forum]: https://community.home-assistant.io/ [issue]: https://github.com/home-assistant/home-assistant/issues [discord]: https://discord.gg/c5DvZ4e @@ -490,8 +490,8 @@ amcrest: [@clkao]: https://github.com/clkao [@maikelwever]: https://github.com/maikelwever [@ypollart]: https://github.com/ypollart -[binary_sensor.rfxtrx docs]: /components/binary_sensor.rfxtrx/ -[telegram_bot docs]: /components/telegram_bot/ +[binary_sensor.rfxtrx docs]: https://home-assistant.io/components/binary_sensor.rfxtrx/ +[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/ [#8545]: https://github.com/home-assistant/home-assistant/pull/8545 [#8571]: https://github.com/home-assistant/home-assistant/pull/8571 [#8601]: https://github.com/home-assistant/home-assistant/pull/8601 @@ -502,6 +502,6 @@ amcrest: [@glance-]: https://github.com/glance- [@jawilson]: https://github.com/jawilson [@schaal]: https://github.com/schaal -[device_tracker.ubus docs]: /components/device_tracker.ubus/ -[keyboard_remote docs]: /components/keyboard_remote/ -[switch.flux docs]: /components/switch.flux/ +[device_tracker.ubus docs]: https://home-assistant.io/components/device_tracker.ubus/ +[keyboard_remote docs]: https://home-assistant.io/components/keyboard_remote/ +[switch.flux docs]: https://home-assistant.io/components/switch.flux/ diff --git a/source/_posts/2017-07-29-release-50.markdown b/source/_posts/2017-07-29-release-50.markdown index bd9fba9034..3de112daf6 100644 --- a/source/_posts/2017-07-29-release-50.markdown +++ b/source/_posts/2017-07-29-release-50.markdown @@ -13,7 +13,7 @@ og_image: /images/blog/2017-07-0.50/components.png
-Last Wednesday we released [Hass.io](/hassio/), an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
+Last Wednesday we released [Hass.io](https://home-assistant.io/hassio/), an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
The launch has been crazy successful. The [20 minute introduction video][hassio-intro] by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
@@ -333,76 +333,76 @@ conversation:
[@titilambert]: https://github.com/titilambert
[@viswa-swami]: https://github.com/viswa-swami
[@w1ll1am23]: https://github.com/w1ll1am23
-[alarm_control_panel.manual_mqtt docs]: /components/alarm_control_panel.manual_mqtt/
-[alarm_control_panel.simplisafe docs]: /components/alarm_control_panel.simplisafe/
-[alarmdecoder docs]: /components/alarmdecoder/
-[alexa docs]: /components/alexa/
-[automation.state docs]: /docs/automation/trigger/#state-trigger
-[automation.time docs]: /docs/automation/trigger/#time-trigger
-[binary_sensor.ping docs]: /components/binary_sensor.ping/
-[binary_sensor.rest docs]: /components/binary_sensor.rest/
-[binary_sensor.velbus docs]: /components/binary_sensor.velbus/
-[binary_sensor.xiaomi docs]: /components/binary_sensor.xiaomi/
-[camera.onvif docs]: /components/camera.onvif/
-[climate.maxcube docs]: /components/climate.maxcube/
-[conversation docs]: /components/conversation/
-[cover docs]: /components/cover/
-[cover.lutron_caseta docs]: /components/cover.lutron_caseta/
-[cover.xiaomi docs]: /components/cover.xiaomi/
-[cover.zwave docs]: /components/cover.zwave/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.snmp docs]: /components/device_tracker.snmp/
-[emulated_hue docs]: /components/emulated_hue/
-[fan.wink docs]: /components/fan.wink/
-[hassio docs]: /hassio/
-[history docs]: /components/history/
-[homematic docs]: /components/homematic/
-[image_processing.dlib_face_identify docs]: /components/image_processing.dlib_face_identify/
-[intent docs]: /developers/intent/
-[intent_script docs]: /components/intent_script/
-[knx docs]: /components/knx/
-[light docs]: /components/light/
-[light.decora docs]: /components/light.decora/
-[light.hue docs]: /components/light.hue/
-[light.lifx docs]: /components/light.lifx/
-[light.tplink docs]: /components/light.tplink/
-[light.velbus docs]: /components/light.velbus/
-[light.wink docs]: /components/light.wink/
-[light.xiaomi docs]: /components/light.xiaomi/
-[light.zha docs]: /components/light.zha/
-[media_extractor docs]: /components/media_extractor/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.kodi docs]: /components/media_player.kodi/
-[mqtt docs]: /components/mqtt/
-[notify.html5 docs]: /components/notify.html5/
-[notify.twitter docs]: /components/notify.twitter/
-[python_script docs]: /components/python_script/
-[recorder docs]: /components/recorder/
-[remote.harmony docs]: /components/remote.harmony/
-[sensor.citybikes docs]: /components/sensor.citybikes/
-[sensor.dht docs]: /components/sensor.dht/
-[sensor.fitbit docs]: /components/sensor.fitbit/
-[sensor.google_wifi docs]: /components/sensor.google_wifi/
-[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
-[sensor.knx docs]: /components/sensor.knx/
-[sensor.lyft docs]: /components/sensor.lyft/
-[sensor.octoprint docs]: /components/sensor.octoprint/
-[sensor.pi_hole docs]: /components/sensor.pi_hole/
-[sensor.snmp docs]: /components/sensor.snmp/
-[sensor.uk_transport docs]: /components/sensor.uk_transport/
-[sensor.xiaomi docs]: /components/sensor.xiaomi/
-[shopping_list docs]: /components/shopping_list/
-[snips docs]: /components/snips/
-[statsd docs]: /components/statsd/
-[switch.fritzdect docs]: /components/switch.fritzdect/
-[switch.mqtt docs]: /components/switch.mqtt/
-[switch.wink docs]: /components/switch.wink/
-[switch.xiaomi docs]: /components/switch.xiaomi/
-[switch.xiaomi_vacuum docs]: /components/switch.xiaomi_vacuum/
-[velbus docs]: /components/velbus/
-[weather.yweather docs]: /components/weather.yweather/
-[wink docs]: /components/wink/
-[xiaomi docs]: /components/xiaomi/
+[alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/
+[alarm_control_panel.simplisafe docs]: https://home-assistant.io/components/alarm_control_panel.simplisafe/
+[alarmdecoder docs]: https://home-assistant.io/components/alarmdecoder/
+[alexa docs]: https://home-assistant.io/components/alexa/
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[automation.time docs]: https://home-assistant.io/docs/automation/trigger/#time-trigger
+[binary_sensor.ping docs]: https://home-assistant.io/components/binary_sensor.ping/
+[binary_sensor.rest docs]: https://home-assistant.io/components/binary_sensor.rest/
+[binary_sensor.velbus docs]: https://home-assistant.io/components/binary_sensor.velbus/
+[binary_sensor.xiaomi docs]: https://home-assistant.io/components/binary_sensor.xiaomi/
+[camera.onvif docs]: https://home-assistant.io/components/camera.onvif/
+[climate.maxcube docs]: https://home-assistant.io/components/climate.maxcube/
+[conversation docs]: https://home-assistant.io/components/conversation/
+[cover docs]: https://home-assistant.io/components/cover/
+[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/
+[cover.xiaomi docs]: https://home-assistant.io/components/cover.xiaomi/
+[cover.zwave docs]: https://home-assistant.io/components/cover.zwave/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[fan.wink docs]: https://home-assistant.io/components/fan.wink/
+[hassio docs]: https://home-assistant.io/hassio/
+[history docs]: https://home-assistant.io/components/history/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/
+[intent docs]: https://home-assistant.io/developers/intent/
+[intent_script docs]: https://home-assistant.io/components/intent_script/
+[knx docs]: https://home-assistant.io/components/knx/
+[light docs]: https://home-assistant.io/components/light/
+[light.decora docs]: https://home-assistant.io/components/light.decora/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.velbus docs]: https://home-assistant.io/components/light.velbus/
+[light.wink docs]: https://home-assistant.io/components/light.wink/
+[light.xiaomi docs]: https://home-assistant.io/components/light.xiaomi/
+[light.zha docs]: https://home-assistant.io/components/light.zha/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
+[mqtt docs]: https://home-assistant.io/components/mqtt/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.twitter docs]: https://home-assistant.io/components/notify.twitter/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[recorder docs]: https://home-assistant.io/components/recorder/
+[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
+[sensor.citybikes docs]: https://home-assistant.io/components/sensor.citybikes/
+[sensor.dht docs]: https://home-assistant.io/components/sensor.dht/
+[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
+[sensor.google_wifi docs]: https://home-assistant.io/components/sensor.google_wifi/
+[sensor.hydroquebec docs]: https://home-assistant.io/components/sensor.hydroquebec/
+[sensor.knx docs]: https://home-assistant.io/components/sensor.knx/
+[sensor.lyft docs]: https://home-assistant.io/components/sensor.lyft/
+[sensor.octoprint docs]: https://home-assistant.io/components/sensor.octoprint/
+[sensor.pi_hole docs]: https://home-assistant.io/components/sensor.pi_hole/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.uk_transport docs]: https://home-assistant.io/components/sensor.uk_transport/
+[sensor.xiaomi docs]: https://home-assistant.io/components/sensor.xiaomi/
+[shopping_list docs]: https://home-assistant.io/components/shopping_list/
+[snips docs]: https://home-assistant.io/components/snips/
+[statsd docs]: https://home-assistant.io/components/statsd/
+[switch.fritzdect docs]: https://home-assistant.io/components/switch.fritzdect/
+[switch.mqtt docs]: https://home-assistant.io/components/switch.mqtt/
+[switch.wink docs]: https://home-assistant.io/components/switch.wink/
+[switch.xiaomi docs]: https://home-assistant.io/components/switch.xiaomi/
+[switch.xiaomi_vacuum docs]: https://home-assistant.io/components/switch.xiaomi_vacuum/
+[velbus docs]: https://home-assistant.io/components/velbus/
+[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
+[wink docs]: https://home-assistant.io/components/wink/
+[xiaomi docs]: https://home-assistant.io/components/xiaomi/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
@@ -418,7 +418,7 @@ conversation:
[#8754]: https://github.com/home-assistant/home-assistant/pull/8754
[#8755]: https://github.com/home-assistant/home-assistant/pull/8755
[@n8henrie]: https://github.com/n8henrie
-[light.tradfri docs]: /components/light.tradfri/
-[media_player.pioneer docs]: /components/media_player.pioneer/
-[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/
-[zwave docs]: /components/zwave/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[media_player.pioneer docs]: https://home-assistant.io/components/media_player.pioneer/
+[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/
+[zwave docs]: https://home-assistant.io/components/zwave/
diff --git a/source/_posts/2017-08-12-release-51.markdown b/source/_posts/2017-08-12-release-51.markdown
index 6e8a5f24ff..36b32d9ad9 100644
--- a/source/_posts/2017-08-12-release-51.markdown
+++ b/source/_posts/2017-08-12-release-51.markdown
@@ -353,107 +353,107 @@ vacuum:
[@viswa-swami]: https://github.com/viswa-swami
[@w1ll1am23]: https://github.com/w1ll1am23
[@wickerwaka]: https://github.com/wickerwaka
-[alarm_control_panel.simplisafe docs]: /components/alarm_control_panel.simplisafe/
-[alexa docs]: /components/alexa/
-[asterisk_mbox docs]: /components/asterisk_mbox/
-[automation docs]: /components/automation/
-[binary_sensor docs]: /components/binary_sensor/
-[binary_sensor.command_line docs]: /components/binary_sensor.command_line/
-[binary_sensor.rest docs]: /components/binary_sensor.rest/
-[binary_sensor.zwave docs]: /components/binary_sensor.zwave/
-[camera.foscam docs]: /components/camera.foscam/
-[climate docs]: /components/climate/
-[climate.honeywell docs]: /components/climate.honeywell/
-[climate.tado docs]: /components/climate.tado/
-[config.zwave docs]: /components/config.zwave/
-[cover.lutron_caseta docs]: /components/cover.lutron_caseta/
-[cover.rpi_gpio docs]: /components/cover.rpi_gpio/
-[device_tracker.huawei_router docs]: /components/device_tracker.huawei_router/
-[dyson docs]: /components/dyson/
-[emulated_hue docs]: /components/emulated_hue/
-[fan.dyson docs]: /components/fan.dyson/
-[group docs]: /components/group/
-[history docs]: /components/history/
-[image_processing.opencv docs]: /components/image_processing.opencv/
-[influxdb docs]: /components/influxdb/
-[insteon_plm docs]: /components/insteon_plm/
-[light.decora_wifi docs]: /components/light.decora_wifi/
-[light.flux_led docs]: /components/light.flux_led/
-[light.lifx docs]: /components/light.lifx/
-[light.mochad docs]: /components/light.mochad/
-[light.osramlightify docs]: /components/light.osramlightify/
-[lock.nuki docs]: /components/lock.nuki/
-[lutron_caseta docs]: /components/lutron_caseta/
-[mailbox.demo docs]: /components/mailbox.demo/
-[mailbox.demo.txt docs]: /components/mailbox.demo.txt/
-[media_extractor docs]: /components/media_extractor/
-[media_player docs]: /components/media_player/
-[media_player.bluesound docs]: /components/media_player.bluesound/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.directv docs]: /components/media_player.directv/
-[media_player.kodi docs]: /components/media_player.kodi/
-[media_player.mpd docs]: /components/media_player.mpd/
-[media_player.russound_rio docs]: /components/media_player.russound_rio/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.squeezebox docs]: /components/media_player.squeezebox/
-[notify.pushbullet docs]: /components/notify.pushbullet/
-[notify.xmpp docs]: /components/notify.xmpp/
-[recorder docs]: /components/recorder/
-[recorder.migration docs]: /components/recorder.migration/
-[recorder.models docs]: /components/recorder.models/
-[recorder.purge docs]: /components/recorder.purge/
-[recorder.util docs]: /components/recorder.util/
-[remote docs]: /components/remote/
-[remote.apple_tv docs]: /components/remote.apple_tv/
-[remote.demo docs]: /components/remote.demo/
-[remote.harmony docs]: /components/remote.harmony/
-[remote.itach docs]: /components/remote.itach/
-[remote.kira docs]: /components/remote.kira/
-[rflink docs]: /components/rflink/
-[scene.lutron_caseta docs]: /components/scene.lutron_caseta/
-[sensor.asterisk_mbox docs]: /components/sensor.asterisk_mbox/
-[sensor.buienradar docs]: /components/sensor.buienradar/
-[sensor.command_line docs]: /components/sensor.command_line/
-[sensor.dyson docs]: /components/sensor.dyson/
-[sensor.efergy docs]: /components/sensor.efergy/
-[sensor.eight_sleep docs]: /components/sensor.eight_sleep/
-[sensor.geizhals docs]: /components/sensor.geizhals/
-[sensor.google_wifi docs]: /components/sensor.google_wifi/
-[sensor.lastfm docs]: /components/sensor.lastfm/
-[sensor.neato docs]: /components/sensor.neato/
-[sensor.pi_hole docs]: /components/sensor.pi_hole/
-[sensor.pocketcasts docs]: /components/sensor.pocketcasts/
-[sensor.radarr docs]: /components/sensor.radarr/
-[sensor.rest docs]: /components/sensor.rest/
-[sensor.sabnzbd docs]: /components/sensor.sabnzbd/
-[sensor.shodan docs]: /components/sensor.shodan/
-[sensor.sonarr docs]: /components/sensor.sonarr/
-[sensor.statistics docs]: /components/sensor.statistics/
-[sensor.supervisord docs]: /components/sensor.supervisord/
-[sensor.synologydsm docs]: /components/sensor.synologydsm/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.vasttrafik docs]: /components/sensor.vasttrafik/
-[sensor.yr docs]: /components/sensor.yr/
-[sensor.zamg docs]: /components/sensor.zamg/
-[switch.command_line docs]: /components/switch.command_line/
-[switch.mqtt docs]: /components/switch.mqtt/
-[switch.neato docs]: /components/switch.neato/
-[switch.rachio docs]: /components/switch.rachio/
-[switch.rainmachine docs]: /components/switch.rainmachine/
-[switch.wink docs]: /components/switch.wink/
-[switch.xiaomi_vacuum docs]: /components/switch.xiaomi_vacuum/
-[telegram_bot docs]: /components/telegram_bot/
-[updater docs]: /components/updater/
-[vacuum docs]: /components/vacuum/
-[vacuum.demo docs]: /components/vacuum.demo/
-[vacuum.dyson docs]: /components/vacuum.dyson/
-[vacuum.roomba docs]: /components/vacuum.roomba/
-[vacuum.xiaomi docs]: /components/vacuum.xiaomi/
-[weather.buienradar docs]: /components/weather.buienradar/
-[weather.yweather docs]: /components/weather.yweather/
-[weather.zamg docs]: /components/weather.zamg/
-[wink docs]: /components/wink/
-[zwave docs]: /components/zwave/
+[alarm_control_panel.simplisafe docs]: https://home-assistant.io/components/alarm_control_panel.simplisafe/
+[alexa docs]: https://home-assistant.io/components/alexa/
+[asterisk_mbox docs]: https://home-assistant.io/components/asterisk_mbox/
+[automation docs]: https://home-assistant.io/components/automation/
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.command_line docs]: https://home-assistant.io/components/binary_sensor.command_line/
+[binary_sensor.rest docs]: https://home-assistant.io/components/binary_sensor.rest/
+[binary_sensor.zwave docs]: https://home-assistant.io/components/binary_sensor.zwave/
+[camera.foscam docs]: https://home-assistant.io/components/camera.foscam/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.honeywell docs]: https://home-assistant.io/components/climate.honeywell/
+[climate.tado docs]: https://home-assistant.io/components/climate.tado/
+[config.zwave docs]: https://home-assistant.io/components/config.zwave/
+[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/
+[cover.rpi_gpio docs]: https://home-assistant.io/components/cover.rpi_gpio/
+[device_tracker.huawei_router docs]: https://home-assistant.io/components/device_tracker.huawei_router/
+[dyson docs]: https://home-assistant.io/components/dyson/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/
+[group docs]: https://home-assistant.io/components/group/
+[history docs]: https://home-assistant.io/components/history/
+[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
+[influxdb docs]: https://home-assistant.io/components/influxdb/
+[insteon_plm docs]: https://home-assistant.io/components/insteon_plm/
+[light.decora_wifi docs]: https://home-assistant.io/components/light.decora_wifi/
+[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.mochad docs]: https://home-assistant.io/components/light.mochad/
+[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
+[lock.nuki docs]: https://home-assistant.io/components/lock.nuki/
+[lutron_caseta docs]: https://home-assistant.io/components/lutron_caseta/
+[mailbox.demo docs]: https://home-assistant.io/components/mailbox.demo/
+[mailbox.demo.txt docs]: https://home-assistant.io/components/mailbox.demo.txt/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player docs]: https://home-assistant.io/components/media_player/
+[media_player.bluesound docs]: https://home-assistant.io/components/media_player.bluesound/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[media_player.directv docs]: https://home-assistant.io/components/media_player.directv/
+[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
+[media_player.mpd docs]: https://home-assistant.io/components/media_player.mpd/
+[media_player.russound_rio docs]: https://home-assistant.io/components/media_player.russound_rio/
+[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
+[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/
+[recorder docs]: https://home-assistant.io/components/recorder/
+[recorder.migration docs]: https://home-assistant.io/components/recorder.migration/
+[recorder.models docs]: https://home-assistant.io/components/recorder.models/
+[recorder.purge docs]: https://home-assistant.io/components/recorder.purge/
+[recorder.util docs]: https://home-assistant.io/components/recorder.util/
+[remote docs]: https://home-assistant.io/components/remote/
+[remote.apple_tv docs]: https://home-assistant.io/components/remote.apple_tv/
+[remote.demo docs]: https://home-assistant.io/components/remote.demo/
+[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
+[remote.itach docs]: https://home-assistant.io/components/remote.itach/
+[remote.kira docs]: https://home-assistant.io/components/remote.kira/
+[rflink docs]: https://home-assistant.io/components/rflink/
+[scene.lutron_caseta docs]: https://home-assistant.io/components/scene.lutron_caseta/
+[sensor.asterisk_mbox docs]: https://home-assistant.io/components/sensor.asterisk_mbox/
+[sensor.buienradar docs]: https://home-assistant.io/components/sensor.buienradar/
+[sensor.command_line docs]: https://home-assistant.io/components/sensor.command_line/
+[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/
+[sensor.efergy docs]: https://home-assistant.io/components/sensor.efergy/
+[sensor.eight_sleep docs]: https://home-assistant.io/components/sensor.eight_sleep/
+[sensor.geizhals docs]: https://home-assistant.io/components/sensor.geizhals/
+[sensor.google_wifi docs]: https://home-assistant.io/components/sensor.google_wifi/
+[sensor.lastfm docs]: https://home-assistant.io/components/sensor.lastfm/
+[sensor.neato docs]: https://home-assistant.io/components/sensor.neato/
+[sensor.pi_hole docs]: https://home-assistant.io/components/sensor.pi_hole/
+[sensor.pocketcasts docs]: https://home-assistant.io/components/sensor.pocketcasts/
+[sensor.radarr docs]: https://home-assistant.io/components/sensor.radarr/
+[sensor.rest docs]: https://home-assistant.io/components/sensor.rest/
+[sensor.sabnzbd docs]: https://home-assistant.io/components/sensor.sabnzbd/
+[sensor.shodan docs]: https://home-assistant.io/components/sensor.shodan/
+[sensor.sonarr docs]: https://home-assistant.io/components/sensor.sonarr/
+[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
+[sensor.supervisord docs]: https://home-assistant.io/components/sensor.supervisord/
+[sensor.synologydsm docs]: https://home-assistant.io/components/sensor.synologydsm/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.vasttrafik docs]: https://home-assistant.io/components/sensor.vasttrafik/
+[sensor.yr docs]: https://home-assistant.io/components/sensor.yr/
+[sensor.zamg docs]: https://home-assistant.io/components/sensor.zamg/
+[switch.command_line docs]: https://home-assistant.io/components/switch.command_line/
+[switch.mqtt docs]: https://home-assistant.io/components/switch.mqtt/
+[switch.neato docs]: https://home-assistant.io/components/switch.neato/
+[switch.rachio docs]: https://home-assistant.io/components/switch.rachio/
+[switch.rainmachine docs]: https://home-assistant.io/components/switch.rainmachine/
+[switch.wink docs]: https://home-assistant.io/components/switch.wink/
+[switch.xiaomi_vacuum docs]: https://home-assistant.io/components/switch.xiaomi_vacuum/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[updater docs]: https://home-assistant.io/components/updater/
+[vacuum docs]: https://home-assistant.io/components/vacuum/
+[vacuum.demo docs]: https://home-assistant.io/components/vacuum.demo/
+[vacuum.dyson docs]: https://home-assistant.io/components/vacuum.dyson/
+[vacuum.roomba docs]: https://home-assistant.io/components/vacuum.roomba/
+[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi/
+[weather.buienradar docs]: https://home-assistant.io/components/weather.buienradar/
+[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
+[weather.zamg docs]: https://home-assistant.io/components/weather.zamg/
+[wink docs]: https://home-assistant.io/components/wink/
+[zwave docs]: https://home-assistant.io/components/zwave/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
diff --git a/source/_posts/2017-08-26-release-0-52.markdown b/source/_posts/2017-08-26-release-0-52.markdown
index 38e5e66151..c6bcb3e486 100644
--- a/source/_posts/2017-08-26-release-0-52.markdown
+++ b/source/_posts/2017-08-26-release-0-52.markdown
@@ -303,85 +303,85 @@ usps:
[@timstanley1985]: https://github.com/timstanley1985
[@tlyakhov]: https://github.com/tlyakhov
[@w1ll1am23]: https://github.com/w1ll1am23
-[abode docs]: /components/abode/
-[alarm_control_panel docs]: /components/alarm_control_panel/
-[alarm_control_panel.abode docs]: /components/alarm_control_panel.abode/
-[alarm_control_panel.egardia docs]: /components/alarm_control_panel.egardia/
-[alarm_control_panel.simplisafe docs]: /components/alarm_control_panel.simplisafe/
-[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
-[binary_sensor.abode docs]: /components/binary_sensor.abode/
-[binary_sensor.mysensors docs]: /components/binary_sensor.mysensors/
-[binary_sensor.workday docs]: /components/binary_sensor.workday/
-[camera.usps docs]: /components/camera.usps/
-[climate.mysensors docs]: /components/climate.mysensors/
-[config docs]: /components/config/
-[configurator docs]: /components/configurator/
-[cover.mysensors docs]: /components/cover.mysensors/
-[cover.template docs]: /components/cover.template/
-[device_tracker.automatic docs]: /components/device_tracker.automatic/
-[device_tracker.mysensors docs]: /components/device_tracker.mysensors/
-[ecobee docs]: /components/ecobee/
-[emulated_hue.upnp docs]: /components/emulated_hue.upnp/
-[envisalink docs]: /components/envisalink/
-[fan.isy994 docs]: /components/fan.isy994/
-[image_processing.dlib_face_detect docs]: /components/image_processing.dlib_face_detect/
-[image_processing.dlib_face_identify docs]: /components/image_processing.dlib_face_identify/
-[insteon_plm docs]: /components/insteon_plm/
-[light.decora_wifi docs]: /components/light.decora_wifi/
-[light.flux_led docs]: /components/light.flux_led/
-[light.hue docs]: /components/light.hue/
-[light.lifx docs]: /components/light.lifx/
-[light.mysensors docs]: /components/light.mysensors/
-[light.rpi_gpio_pwm docs]: /components/light.rpi_gpio_pwm/
-[light.tplink docs]: /components/light.tplink/
-[light.yeelight docs]: /components/light.yeelight/
-[lock.nello docs]: /components/lock.nello/
-[media_extractor docs]: /components/media_extractor/
-[media_player.mpd docs]: /components/media_player.mpd/
-[media_player.onkyo docs]: /components/media_player.onkyo/
-[media_player.snapcast docs]: /components/media_player.snapcast/
-[media_player.spotify docs]: /components/media_player.spotify/
-[media_player.squeezebox docs]: /components/media_player.squeezebox/
-[media_player.webostv docs]: /components/media_player.webostv/
-[mysensors docs]: /components/mysensors/
-[notify.discord docs]: /components/notify.discord/
-[notify.hipchat docs]: /components/notify.hipchat/
-[notify.mysensors docs]: /components/notify.mysensors/
-[notify.prowl docs]: /components/notify.prowl/
-[notify.pushbullet docs]: /components/notify.pushbullet/
-[notify.pushover docs]: /components/notify.pushover/
-[notify.sendgrid docs]: /components/notify.sendgrid/
-[notify.slack docs]: /components/notify.slack/
-[octoprint docs]: /components/octoprint/
-[prometheus docs]: /components/prometheus/
-[script docs]: /components/script/
-[sensor.buienradar docs]: /components/sensor.buienradar/
-[sensor.cert_expiry docs]: /components/sensor.cert_expiry/
-[sensor.eliqonline docs]: /components/sensor.eliqonline/
-[sensor.fedex docs]: /components/sensor.fedex/
-[sensor.fitbit docs]: /components/sensor.fitbit/
-[sensor.fritzbox_callmonitor docs]: /components/sensor.fritzbox_callmonitor/
-[sensor.geizhals docs]: /components/sensor.geizhals/
-[sensor.ios docs]: /components/sensor.ios/
-[sensor.london_air docs]: /components/sensor.london_air/
-[sensor.mysensors docs]: /components/sensor.mysensors/
-[sensor.netdata docs]: /components/sensor.netdata/
-[sensor.octoprint docs]: /components/sensor.octoprint/
-[sensor.snmp docs]: /components/sensor.snmp/
-[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
-[sensor.uber docs]: /components/sensor.uber/
-[sensor.uk_transport docs]: /components/sensor.uk_transport/
-[sensor.usps docs]: /components/sensor.usps/
-[sensor.version docs]: /components/sensor.version/
-[sensor.worldtidesinfo docs]: /components/sensor.worldtidesinfo/
-[switch.mqtt docs]: /components/switch.mqtt/
-[switch.mysensors docs]: /components/switch.mysensors/
-[switch.pilight docs]: /components/switch.pilight/
-[switch.rainmachine docs]: /components/switch.rainmachine/
-[switch.xiaomi docs]: /components/switch.xiaomi/
-[usps docs]: /components/usps/
-[weather.buienradar docs]: /components/weather.buienradar/
-[xiaomi docs]: /components/xiaomi/
+[abode docs]: https://home-assistant.io/components/abode/
+[alarm_control_panel docs]: https://home-assistant.io/components/alarm_control_panel/
+[alarm_control_panel.abode docs]: https://home-assistant.io/components/alarm_control_panel.abode/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alarm_control_panel.simplisafe docs]: https://home-assistant.io/components/alarm_control_panel.simplisafe/
+[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/
+[binary_sensor.abode docs]: https://home-assistant.io/components/binary_sensor.abode/
+[binary_sensor.mysensors docs]: https://home-assistant.io/components/binary_sensor.mysensors/
+[binary_sensor.workday docs]: https://home-assistant.io/components/binary_sensor.workday/
+[camera.usps docs]: https://home-assistant.io/components/camera.usps/
+[climate.mysensors docs]: https://home-assistant.io/components/climate.mysensors/
+[config docs]: https://home-assistant.io/components/config/
+[configurator docs]: https://home-assistant.io/components/configurator/
+[cover.mysensors docs]: https://home-assistant.io/components/cover.mysensors/
+[cover.template docs]: https://home-assistant.io/components/cover.template/
+[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/
+[device_tracker.mysensors docs]: https://home-assistant.io/components/device_tracker.mysensors/
+[ecobee docs]: https://home-assistant.io/components/ecobee/
+[emulated_hue.upnp docs]: https://home-assistant.io/components/emulated_hue.upnp/
+[envisalink docs]: https://home-assistant.io/components/envisalink/
+[fan.isy994 docs]: https://home-assistant.io/components/fan.isy994/
+[image_processing.dlib_face_detect docs]: https://home-assistant.io/components/image_processing.dlib_face_detect/
+[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/
+[insteon_plm docs]: https://home-assistant.io/components/insteon_plm/
+[light.decora_wifi docs]: https://home-assistant.io/components/light.decora_wifi/
+[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.mysensors docs]: https://home-assistant.io/components/light.mysensors/
+[light.rpi_gpio_pwm docs]: https://home-assistant.io/components/light.rpi_gpio_pwm/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[lock.nello docs]: https://home-assistant.io/components/lock.nello/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.mpd docs]: https://home-assistant.io/components/media_player.mpd/
+[media_player.onkyo docs]: https://home-assistant.io/components/media_player.onkyo/
+[media_player.snapcast docs]: https://home-assistant.io/components/media_player.snapcast/
+[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/
+[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/
+[media_player.webostv docs]: https://home-assistant.io/components/media_player.webostv/
+[mysensors docs]: https://home-assistant.io/components/mysensors/
+[notify.discord docs]: https://home-assistant.io/components/notify.discord/
+[notify.hipchat docs]: https://home-assistant.io/components/notify.hipchat/
+[notify.mysensors docs]: https://home-assistant.io/components/notify.mysensors/
+[notify.prowl docs]: https://home-assistant.io/components/notify.prowl/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[notify.pushover docs]: https://home-assistant.io/components/notify.pushover/
+[notify.sendgrid docs]: https://home-assistant.io/components/notify.sendgrid/
+[notify.slack docs]: https://home-assistant.io/components/notify.slack/
+[octoprint docs]: https://home-assistant.io/components/octoprint/
+[prometheus docs]: https://home-assistant.io/components/prometheus/
+[script docs]: https://home-assistant.io/components/script/
+[sensor.buienradar docs]: https://home-assistant.io/components/sensor.buienradar/
+[sensor.cert_expiry docs]: https://home-assistant.io/components/sensor.cert_expiry/
+[sensor.eliqonline docs]: https://home-assistant.io/components/sensor.eliqonline/
+[sensor.fedex docs]: https://home-assistant.io/components/sensor.fedex/
+[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
+[sensor.fritzbox_callmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_callmonitor/
+[sensor.geizhals docs]: https://home-assistant.io/components/sensor.geizhals/
+[sensor.ios docs]: https://home-assistant.io/components/sensor.ios/
+[sensor.london_air docs]: https://home-assistant.io/components/sensor.london_air/
+[sensor.mysensors docs]: https://home-assistant.io/components/sensor.mysensors/
+[sensor.netdata docs]: https://home-assistant.io/components/sensor.netdata/
+[sensor.octoprint docs]: https://home-assistant.io/components/sensor.octoprint/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.swiss_public_transport docs]: https://home-assistant.io/components/sensor.swiss_public_transport/
+[sensor.uber docs]: https://home-assistant.io/components/sensor.uber/
+[sensor.uk_transport docs]: https://home-assistant.io/components/sensor.uk_transport/
+[sensor.usps docs]: https://home-assistant.io/components/sensor.usps/
+[sensor.version docs]: https://home-assistant.io/components/sensor.version/
+[sensor.worldtidesinfo docs]: https://home-assistant.io/components/sensor.worldtidesinfo/
+[switch.mqtt docs]: https://home-assistant.io/components/switch.mqtt/
+[switch.mysensors docs]: https://home-assistant.io/components/switch.mysensors/
+[switch.pilight docs]: https://home-assistant.io/components/switch.pilight/
+[switch.rainmachine docs]: https://home-assistant.io/components/switch.rainmachine/
+[switch.xiaomi docs]: https://home-assistant.io/components/switch.xiaomi/
+[usps docs]: https://home-assistant.io/components/usps/
+[weather.buienradar docs]: https://home-assistant.io/components/weather.buienradar/
+[xiaomi docs]: https://home-assistant.io/components/xiaomi/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
@@ -395,6 +395,6 @@ usps:
[#9191]: https://github.com/home-assistant/home-assistant/pull/9191
[@foxel]: https://github.com/foxel
[@sdague]: https://github.com/sdague
-[camera.foscam docs]: /components/camera.foscam/
-[climate.ecobee docs]: /components/climate.ecobee/
-[device_tracker.icloud docs]: /components/device_tracker.icloud/
+[camera.foscam docs]: https://home-assistant.io/components/camera.foscam/
+[climate.ecobee docs]: https://home-assistant.io/components/climate.ecobee/
+[device_tracker.icloud docs]: https://home-assistant.io/components/device_tracker.icloud/
diff --git a/source/_posts/2017-09-09-release-53.markdown b/source/_posts/2017-09-09-release-53.markdown
index 7897969747..51223765d4 100644
--- a/source/_posts/2017-09-09-release-53.markdown
+++ b/source/_posts/2017-09-09-release-53.markdown
@@ -349,108 +349,108 @@ frontend:
[@tinloaf]: https://github.com/tinloaf
[@w1ll1am23]: https://github.com/w1ll1am23
[@zabuldon]: https://github.com/zabuldon
-[abode docs]: /components/abode/
-[alarm_control_panel.abode docs]: /components/alarm_control_panel.abode/
-[alarm_control_panel.egardia docs]: /components/alarm_control_panel.egardia/
-[alarm_control_panel.manual docs]: /components/alarm_control_panel.manual/
-[binary_sensor.abode docs]: /components/binary_sensor.abode/
-[binary_sensor.bayesian docs]: /components/binary_sensor.bayesian/
-[binary_sensor.hikvision docs]: /components/binary_sensor.hikvision/
-[binary_sensor.homematic docs]: /components/binary_sensor.homematic/
-[binary_sensor.ring docs]: /components/binary_sensor.ring/
-[binary_sensor.tesla docs]: /components/binary_sensor.tesla/
-[binary_sensor.xiaomi docs]: /components/binary_sensor.xiaomi/
-[binary_sensor.knx docs]: /components/binary_sensor.knx/
-[climate.homematic docs]: /components/climate.homematic/
-[climate.honeywell docs]: /components/climate.honeywell/
-[climate.tesla docs]: /components/climate.tesla/
-[climate.knx docs]: /components/climate.knx/
-[cloud docs]: /components/cloud/
-[cloud.cloud_api docs]: /components/cloud.cloud_api/
-[cloud.const docs]: /components/cloud.const/
-[cloud.http_api docs]: /components/cloud.http_api/
-[cloud.util docs]: /components/cloud.util/
-[config docs]: /components/config/
-[config.customize docs]: /components/config.customize/
-[counter docs]: /components/counter/
-[cover.abode docs]: /components/cover.abode/
-[cover.homematic docs]: /components/cover.homematic/
-[cover.lutron_caseta docs]: /components/cover.lutron_caseta/
-[cover.rfxtrx docs]: /components/cover.rfxtrx/
-[cover.xiaomi docs]: /components/cover.xiaomi/
-[cover.knx docs]: /components/cover.knx/
-[device_tracker.automatic docs]: /components/device_tracker.automatic/
-[device_tracker.geofency docs]: /components/device_tracker.geofency/
-[device_tracker.tesla docs]: /components/device_tracker.tesla/
-[device_tracker.volvooncall docs]: /components/device_tracker.volvooncall/
-[hdmi_cec docs]: /components/hdmi_cec/
-[homematic docs]: /components/homematic/
-[image_processing.dlib_face_detect docs]: /components/image_processing.dlib_face_detect/
-[image_processing.dlib_face_identify docs]: /components/image_processing.dlib_face_identify/
-[input_text docs]: /components/input_text/
-[insteon_plm docs]: /components/insteon_plm/
-[light.homematic docs]: /components/light.homematic/
-[light.hue docs]: /components/light.hue/
-[light.lutron_caseta docs]: /components/light.lutron_caseta/
-[light.mqtt docs]: /components/light.mqtt/
-[light.xiaomi_philipslight docs]: /components/light.xiaomi_philipslight/
-[light.rfxtrx docs]: /components/light.rfxtrx/
-[light.tradfri docs]: /components/light.tradfri/
-[light.knx docs]: /components/light.knx/
-[light.zha docs]: /components/light.zha/
-[lock.abode docs]: /components/lock.abode/
-[lock.nello docs]: /components/lock.nello/
-[lock.tesla docs]: /components/lock.tesla/
-[lutron_caseta docs]: /components/lutron_caseta/
-[media_extractor docs]: /components/media_extractor/
-[media_player.denonavr docs]: /components/media_player.denonavr/
-[media_player.directv docs]: /components/media_player.directv/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.spotify docs]: /components/media_player.spotify/
-[media_player.yamaha_musiccast docs]: /components/media_player.yamaha_musiccast/
-[mycroft docs]: /components/mycroft/
-[mysensors docs]: /components/mysensors/
-[notify.discord docs]: /components/notify.discord/
-[notify.mycroft docs]: /components/notify.mycroft/
-[notify.pushbullet docs]: /components/notify.pushbullet/
-[notify.sendgrid docs]: /components/notify.sendgrid/
-[notify.twitter docs]: /components/notify.twitter/
-[notify.xmpp docs]: /components/notify.xmpp/
-[rfxtrx docs]: /components/rfxtrx/
-[sensor.airvisual docs]: /components/sensor.airvisual/
-[sensor.buienradar docs]: /components/sensor.buienradar/
-[sensor.dht docs]: /components/sensor.dht/
-[sensor.dwdwarnapp docs]: /components/sensor.dwdwarnapp/
-[sensor.fitbit docs]: /components/sensor.fitbit/
-[sensor.homematic docs]: /components/sensor.homematic/
-[sensor.mopar docs]: /components/sensor.mopar/
-[sensor.radarr docs]: /components/sensor.radarr/
-[sensor.season docs]: /components/sensor.season/
-[sensor.shodan docs]: /components/sensor.shodan/
-[sensor.sonarr docs]: /components/sensor.sonarr/
-[sensor.statistics docs]: /components/sensor.statistics/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.tank_utility docs]: /components/sensor.tank_utility/
-[sensor.tesla docs]: /components/sensor.tesla/
-[sensor.uber docs]: /components/sensor.uber/
-[sensor.worldtidesinfo docs]: /components/sensor.worldtidesinfo/
-[sensor.knx docs]: /components/sensor.knx/
-[snips docs]: /components/snips/
-[switch.abode docs]: /components/switch.abode/
-[switch.digitalloggers docs]: /components/switch.digitalloggers/
-[switch.dlink docs]: /components/switch.dlink/
-[switch.homematic docs]: /components/switch.homematic/
-[switch.lutron_caseta docs]: /components/switch.lutron_caseta/
-[switch.rest docs]: /components/switch.rest/
-[switch.rfxtrx docs]: /components/switch.rfxtrx/
-[switch.knx docs]: /components/switch.knx/
-[telegram_bot docs]: /components/telegram_bot/
-[tesla docs]: /components/tesla/
-[tradfri docs]: /components/tradfri/
-[volvooncall docs]: /components/volvooncall/
-[xiaomi docs]: /components/xiaomi/
-[knx docs]: /components/knx/
-[zwave docs]: /components/zwave/
+[abode docs]: https://home-assistant.io/components/abode/
+[alarm_control_panel.abode docs]: https://home-assistant.io/components/alarm_control_panel.abode/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alarm_control_panel.manual docs]: https://home-assistant.io/components/alarm_control_panel.manual/
+[binary_sensor.abode docs]: https://home-assistant.io/components/binary_sensor.abode/
+[binary_sensor.bayesian docs]: https://home-assistant.io/components/binary_sensor.bayesian/
+[binary_sensor.hikvision docs]: https://home-assistant.io/components/binary_sensor.hikvision/
+[binary_sensor.homematic docs]: https://home-assistant.io/components/binary_sensor.homematic/
+[binary_sensor.ring docs]: https://home-assistant.io/components/binary_sensor.ring/
+[binary_sensor.tesla docs]: https://home-assistant.io/components/binary_sensor.tesla/
+[binary_sensor.xiaomi docs]: https://home-assistant.io/components/binary_sensor.xiaomi/
+[binary_sensor.knx docs]: https://home-assistant.io/components/binary_sensor.knx/
+[climate.homematic docs]: https://home-assistant.io/components/climate.homematic/
+[climate.honeywell docs]: https://home-assistant.io/components/climate.honeywell/
+[climate.tesla docs]: https://home-assistant.io/components/climate.tesla/
+[climate.knx docs]: https://home-assistant.io/components/climate.knx/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.cloud_api docs]: https://home-assistant.io/components/cloud.cloud_api/
+[cloud.const docs]: https://home-assistant.io/components/cloud.const/
+[cloud.http_api docs]: https://home-assistant.io/components/cloud.http_api/
+[cloud.util docs]: https://home-assistant.io/components/cloud.util/
+[config docs]: https://home-assistant.io/components/config/
+[config.customize docs]: https://home-assistant.io/components/config.customize/
+[counter docs]: https://home-assistant.io/components/counter/
+[cover.abode docs]: https://home-assistant.io/components/cover.abode/
+[cover.homematic docs]: https://home-assistant.io/components/cover.homematic/
+[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/
+[cover.rfxtrx docs]: https://home-assistant.io/components/cover.rfxtrx/
+[cover.xiaomi docs]: https://home-assistant.io/components/cover.xiaomi/
+[cover.knx docs]: https://home-assistant.io/components/cover.knx/
+[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/
+[device_tracker.geofency docs]: https://home-assistant.io/components/device_tracker.geofency/
+[device_tracker.tesla docs]: https://home-assistant.io/components/device_tracker.tesla/
+[device_tracker.volvooncall docs]: https://home-assistant.io/components/device_tracker.volvooncall/
+[hdmi_cec docs]: https://home-assistant.io/components/hdmi_cec/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[image_processing.dlib_face_detect docs]: https://home-assistant.io/components/image_processing.dlib_face_detect/
+[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/
+[input_text docs]: https://home-assistant.io/components/input_text/
+[insteon_plm docs]: https://home-assistant.io/components/insteon_plm/
+[light.homematic docs]: https://home-assistant.io/components/light.homematic/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.lutron_caseta docs]: https://home-assistant.io/components/light.lutron_caseta/
+[light.mqtt docs]: https://home-assistant.io/components/light.mqtt/
+[light.xiaomi_philipslight docs]: https://home-assistant.io/components/light.xiaomi_philipslight/
+[light.rfxtrx docs]: https://home-assistant.io/components/light.rfxtrx/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.knx docs]: https://home-assistant.io/components/light.knx/
+[light.zha docs]: https://home-assistant.io/components/light.zha/
+[lock.abode docs]: https://home-assistant.io/components/lock.abode/
+[lock.nello docs]: https://home-assistant.io/components/lock.nello/
+[lock.tesla docs]: https://home-assistant.io/components/lock.tesla/
+[lutron_caseta docs]: https://home-assistant.io/components/lutron_caseta/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
+[media_player.directv docs]: https://home-assistant.io/components/media_player.directv/
+[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
+[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/
+[media_player.yamaha_musiccast docs]: https://home-assistant.io/components/media_player.yamaha_musiccast/
+[mycroft docs]: https://home-assistant.io/components/mycroft/
+[mysensors docs]: https://home-assistant.io/components/mysensors/
+[notify.discord docs]: https://home-assistant.io/components/notify.discord/
+[notify.mycroft docs]: https://home-assistant.io/components/notify.mycroft/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[notify.sendgrid docs]: https://home-assistant.io/components/notify.sendgrid/
+[notify.twitter docs]: https://home-assistant.io/components/notify.twitter/
+[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/
+[rfxtrx docs]: https://home-assistant.io/components/rfxtrx/
+[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
+[sensor.buienradar docs]: https://home-assistant.io/components/sensor.buienradar/
+[sensor.dht docs]: https://home-assistant.io/components/sensor.dht/
+[sensor.dwdwarnapp docs]: https://home-assistant.io/components/sensor.dwdwarnapp/
+[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
+[sensor.homematic docs]: https://home-assistant.io/components/sensor.homematic/
+[sensor.mopar docs]: https://home-assistant.io/components/sensor.mopar/
+[sensor.radarr docs]: https://home-assistant.io/components/sensor.radarr/
+[sensor.season docs]: https://home-assistant.io/components/sensor.season/
+[sensor.shodan docs]: https://home-assistant.io/components/sensor.shodan/
+[sensor.sonarr docs]: https://home-assistant.io/components/sensor.sonarr/
+[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tank_utility docs]: https://home-assistant.io/components/sensor.tank_utility/
+[sensor.tesla docs]: https://home-assistant.io/components/sensor.tesla/
+[sensor.uber docs]: https://home-assistant.io/components/sensor.uber/
+[sensor.worldtidesinfo docs]: https://home-assistant.io/components/sensor.worldtidesinfo/
+[sensor.knx docs]: https://home-assistant.io/components/sensor.knx/
+[snips docs]: https://home-assistant.io/components/snips/
+[switch.abode docs]: https://home-assistant.io/components/switch.abode/
+[switch.digitalloggers docs]: https://home-assistant.io/components/switch.digitalloggers/
+[switch.dlink docs]: https://home-assistant.io/components/switch.dlink/
+[switch.homematic docs]: https://home-assistant.io/components/switch.homematic/
+[switch.lutron_caseta docs]: https://home-assistant.io/components/switch.lutron_caseta/
+[switch.rest docs]: https://home-assistant.io/components/switch.rest/
+[switch.rfxtrx docs]: https://home-assistant.io/components/switch.rfxtrx/
+[switch.knx docs]: https://home-assistant.io/components/switch.knx/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[tesla docs]: https://home-assistant.io/components/tesla/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[volvooncall docs]: https://home-assistant.io/components/volvooncall/
+[xiaomi docs]: https://home-assistant.io/components/xiaomi/
+[knx docs]: https://home-assistant.io/components/knx/
+[zwave docs]: https://home-assistant.io/components/zwave/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
@@ -458,5 +458,5 @@ frontend:
[#9380]: https://github.com/home-assistant/home-assistant/pull/9380
[#9387]: https://github.com/home-assistant/home-assistant/pull/9387
[@viswa-swami]: https://github.com/viswa-swami
-[camera.foscam docs]: /components/camera.foscam/
-[sensor.wunderground docs]: /components/sensor.wunderground/
+[camera.foscam docs]: https://home-assistant.io/components/camera.foscam/
+[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
diff --git a/source/_posts/2017-09-16-hassbian-1.3-a-bit-of-a-stretch.markdown b/source/_posts/2017-09-16-hassbian-1.3-a-bit-of-a-stretch.markdown
index e601496765..8d1c4732c8 100644
--- a/source/_posts/2017-09-16-hassbian-1.3-a-bit-of-a-stretch.markdown
+++ b/source/_posts/2017-09-16-hassbian-1.3-a-bit-of-a-stretch.markdown
@@ -18,9 +18,9 @@ To allow you to customize your installation further, we have made a few addition
#### {% linkable_title Upgrade scripts %}
-[@Ludeeus][ludeeus] contributed the possibility to run upgrade scripts to the `hassbian-config` tool.
+[@Ludeeus][ludeeus] contributed the possibility to run upgrade scripts to the `hassbian-config` tool.
- - Upgrade Hassbian: Upgrades packages of the base operating system. Contributed by [@Landrash][landrash].
+ - Upgrade Hassbian: Upgrades packages of the base operating system. Contributed by [@Landrash][landrash].
- Upgrade Hassbian-script: Downloads and upgrades the latest release of Hassbian-scripts. Contributed by [@Ludeeus][ludeeus].
- Upgrade Home-assistant: Upgrades the Home Assistant installation to the latest release. Contributed by [@Ludeeus][ludeeus].
@@ -28,9 +28,9 @@ To follow discussions about the development of the HASSbian image or to contribu
To get started with the new image, check out the installation instructions on the [installing Hassbian page][install].
-[landrash]: http://github.com/landrash
+[landrash]: http://github.com/landrash
[ludeeus]: http://github.com/ludeeus
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts/
[hassbian-config-release]: https://github.com/home-assistant/hassbian-scripts/releases/latest
-[install]: /docs/installation/hassbian/installation/
+[install]: https://home-assistant.io/docs/installation/hassbian/installation/
[discord-hassbian]: https://discord.gg/RkajcgS
diff --git a/source/_posts/2017-09-29-hacktoberfest.markdown b/source/_posts/2017-09-29-hacktoberfest.markdown
index 58a15d94cd..a57eaba03f 100644
--- a/source/_posts/2017-09-29-hacktoberfest.markdown
+++ b/source/_posts/2017-09-29-hacktoberfest.markdown
@@ -42,5 +42,5 @@ Our participation for [Hacktoberfest 2016][hackt-2016] was a huge success. Join
[dev-env]: /developers/development_environment/
[dev-chat]: https://discord.gg/8X8DTH4
[dev-forum]: https://community.home-assistant.io/c/development
-[hackt-2016]: /blog/2016/11/05/hacktoberfest-influxdb-weather/#hacktoberfest
+[hackt-2016]: https://home-assistant.io/blog/2016/11/05/hacktoberfest-influxdb-weather/#hacktoberfest
diff --git a/source/_posts/2017-10-06-deprecating-python-3.4-support.markdown b/source/_posts/2017-10-06-deprecating-python-3.4-support.markdown
index 7b053dd690..8d9364a143 100644
--- a/source/_posts/2017-10-06-deprecating-python-3.4-support.markdown
+++ b/source/_posts/2017-10-06-deprecating-python-3.4-support.markdown
@@ -10,11 +10,6 @@ comments: true
categories: Technology
---
-**Update February 16, 2018**:
-Home Assistant 0.64 will be the last release to support Python 3.4. Starting with release 0.65, Home Assistant will require a minimum version of Python 3.5.3.
-
----
-
Starting with our next release, 0.55, we will deprecate Python 3.4 support. The current plan is to remove support for Python 3.4 at the beginning of 2018.
Python 3.5 was released on September 13th, 2015. It has since then become the default Python installation on the stable releases of Debian, Ubuntu, Raspbian and Hassbian. Our other own operating system, Hass.io, is more advanced and is already running the greatly improved Python 3.6.
@@ -22,7 +17,7 @@ Python 3.5 was released on September 13th, 2015. It has since then become the de
The jump to Python 3.5 as a minimum version is driven by the Home Assistant core, which is based on asyncio. Starting with Python 3.5, asyncio got improved support in the language with dedicated keywords `async` and `await`. As this is the proper way of doing async in Python, we're seeing a move by async libraries to either only support the new syntax from the beginning or dropping support for the Python 3.4 approach. Not moving along means an increased maintenance burden as we cannot use the latest releases of our libraries. Next to that it will prevent our users from being able to leverage the bug fixes and performance improvements that come with Python 3.5.
#### Hass.io
-If you're running Hass.io, you don't have to do anything. Your system will always stay up to date.
+If you're running Hass.io, you don't have to do anything. Your system will always stay up to date.
#### Hassbian
If you're running Hassbian it's recommended that you make a backup of your configuration files and restore them on a fresh install. Upgrading an existing installation isn't recommended.
diff --git a/source/_posts/2017-10-07-release-55.markdown b/source/_posts/2017-10-07-release-55.markdown
index 6d1c6b36da..6517546712 100644
--- a/source/_posts/2017-10-07-release-55.markdown
+++ b/source/_posts/2017-10-07-release-55.markdown
@@ -16,7 +16,7 @@ og_image: /images/blog/2017-10-0.55/components.png
Beside the improved Wink support which was contributed by [@w1ll1am23], ships this release a wide variety of new components and platforms. The `input_slider` components has received a makeover by [@BioSehnsucht] and is now [`input_number`][input_number docs]. [@tinloaf] added a feature that allows you to enter dates: [`input_datetime`][input_datetime docs]. Both will help you to improve your automation rules.
## {% linkable_title DuckDNS %}
-Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](/addons/duckdns/). 0.55 ships a component for non Hass.io users to get a similar feature.
+Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](https://home-assistant.io/addons/duckdns/). 0.55 ships a component for non Hass.io users to get a similar feature.
## {% linkable_title Recorder %}
The purging of data was [improved][recorder docs]. With `purge_interval` you can schedule regular purges of older events and states. In combination you can specify with `purge_keep_days` the amount of days you want to keep. The new service `recorder.purge` allows you to handle this task when needed.
@@ -305,92 +305,92 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@tinloaf]: https://github.com/tinloaf
[@vickyg3]: https://github.com/vickyg3
[@w1ll1am23]: https://github.com/w1ll1am23
-[abode docs]: /components/abode/
-[alarm_control_panel.egardia docs]: /components/alarm_control_panel.egardia/
-[alarm_control_panel.manual_mqtt docs]: /components/alarm_control_panel.manual_mqtt/
-[alexa.smart_home docs]: /components/alexa/
-[apple_tv docs]: /components/apple_tv/
-[arlo docs]: /components/arlo/
-[binary_sensor.raincloud docs]: /components/binary_sensor.raincloud/
-[binary_sensor.threshold docs]: /components/binary_sensor.threshold/
-[binary_sensor.wink docs]: /components/binary_sensor.wink/
-[camera.arlo docs]: /components/camera.arlo/
-[camera.synology docs]: /components/camera.synology/
-[camera.usps docs]: /components/camera.usps/
-[climate.ecobee docs]: /components/climate.ecobee/
-[climate.mqtt docs]: /components/climate.mqtt/
-[cover.mqtt docs]: /components/cover.mqtt/
-[cover.rflink docs]: /components/cover.rflink/
-[demo docs]: /components/demo/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.owntracks_http docs]: /components/device_tracker.owntracks_http/
-[duckdns docs]: /components/duckdns/
-[ecobee docs]: /components/ecobee/
-[emulated_hue docs]: /components/emulated_hue/
-[google docs]: /components/calendar.google/
-[group docs]: /components/group/
-[hassio docs]: /hassio/
-[history docs]: /components/history/
-[homematic docs]: /components/homematic/
-[http docs]: /components/http/
-[image_processing.opencv docs]: /components/image_processing.opencv/
-[influxdb docs]: /components/influxdb/
-[input_datetime docs]: /components/input_datetime/
-[input_number docs]: /components/input_number/
-[light.flux_led docs]: /components/light.flux_led/
-[light.rflink docs]: /components/light.rflink/
-[light.tradfri docs]: /components/light.tradfri/
-[light.yeelight docs]: /components/light.yeelight/
-[lock.wink docs]: /components/lock.wink/
-[media_extractor docs]: /components/media_extractor/
-[media_player.apple_tv docs]: /components/media_player.apple_tv/
-[media_player.webostv docs]: /components/media_player.webostv/
-[media_player.yamaha_musiccast docs]: /components/media_player.yamaha_musiccast/
-[mqtt_statestream docs]: /components/mqtt_statestream/
-[notify.clicksendaudio docs]: /components/notify.clicksendaudio/
-[notify.discord docs]: /components/notify.discord/
-[notify.facebook docs]: /components/notify.facebook/
-[notify.simplepush docs]: /components/notify.simplepush/
-[raincloud docs]: /components/raincloud/
-[raspihats docs]: /components/raspihats/
-[recorder docs]: /components/recorder/
-[remote.itach docs]: /components/remote.itach/
-[rflink docs]: /components/rflink/
-[sensor.airvisual docs]: /components/sensor.airvisual/
-[sensor.arlo docs]: /components/sensor.arlo/
-[sensor.comed_hourly_pricing docs]: /components/sensor.comed_hourly_pricing/
-[sensor.dsmr docs]: /components/sensor.dsmr/
-[sensor.fedex docs]: /components/sensor.fedex/
-[sensor.geo_rss_events docs]: /components/sensor.geo_rss_events/
-[sensor.google_travel_time docs]: /components/sensor.google_travel_time/
-[sensor.imap docs]: /components/sensor.imap/
-[sensor.lyft docs]: /components/sensor.lyft/
-[sensor.onewire docs]: /components/sensor.onewire/
-[sensor.pvoutput docs]: /components/sensor.pvoutput/
-[sensor.raincloud docs]: /components/sensor.raincloud/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.thethingsnetwork docs]: /components/sensor.thethingsnetwork/
-[sensor.tibber docs]: /components/sensor.tibber/
-[sensor.ups docs]: /components/sensor.ups/
-[sensor.usps docs]: /components/sensor.usps/
-[sensor.vera docs]: /components/sensor.vera/
-[sensor.wunderground docs]: /components/sensor.wunderground/
-[splunk docs]: /components/splunk/
-[switch.abode docs]: /components/switch.abode/
-[switch.raincloud docs]: /components/switch.raincloud/
-[switch.rflink docs]: /components/switch.rflink/
-[switch.tplink docs]: /components/switch.tplink/
-[thethingsnetwork docs]: /components/thethingsnetwork/
-[tradfri docs]: /components/tradfri/
-[upnp docs]: /components/upnp/
-[usps docs]: /components/usps/
-[vacuum.xiaomi docs]: /components/vacuum.xiaomi_miio/
-[wink docs]: /components/wink/
-[zwave docs]: /components/zwave/
+[abode docs]: https://home-assistant.io/components/abode/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa/
+[apple_tv docs]: https://home-assistant.io/components/apple_tv/
+[arlo docs]: https://home-assistant.io/components/arlo/
+[binary_sensor.raincloud docs]: https://home-assistant.io/components/binary_sensor.raincloud/
+[binary_sensor.threshold docs]: https://home-assistant.io/components/binary_sensor.threshold/
+[binary_sensor.wink docs]: https://home-assistant.io/components/binary_sensor.wink/
+[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
+[camera.synology docs]: https://home-assistant.io/components/camera.synology/
+[camera.usps docs]: https://home-assistant.io/components/camera.usps/
+[climate.ecobee docs]: https://home-assistant.io/components/climate.ecobee/
+[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
+[cover.mqtt docs]: https://home-assistant.io/components/cover.mqtt/
+[cover.rflink docs]: https://home-assistant.io/components/cover.rflink/
+[demo docs]: https://home-assistant.io/components/demo/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.owntracks_http docs]: https://home-assistant.io/components/device_tracker.owntracks_http/
+[duckdns docs]: https://home-assistant.io/components/duckdns/
+[ecobee docs]: https://home-assistant.io/components/ecobee/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[google docs]: https://home-assistant.io/components/calendar.google/
+[group docs]: https://home-assistant.io/components/group/
+[hassio docs]: https://home-assistant.io/hassio/
+[history docs]: https://home-assistant.io/components/history/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[http docs]: https://home-assistant.io/components/http/
+[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
+[influxdb docs]: https://home-assistant.io/components/influxdb/
+[input_datetime docs]: https://home-assistant.io/components/input_datetime/
+[input_number docs]: https://home-assistant.io/components/input_number/
+[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
+[light.rflink docs]: https://home-assistant.io/components/light.rflink/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[lock.wink docs]: https://home-assistant.io/components/lock.wink/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.apple_tv docs]: https://home-assistant.io/components/media_player.apple_tv/
+[media_player.webostv docs]: https://home-assistant.io/components/media_player.webostv/
+[media_player.yamaha_musiccast docs]: https://home-assistant.io/components/media_player.yamaha_musiccast/
+[mqtt_statestream docs]: https://home-assistant.io/components/mqtt_statestream/
+[notify.clicksendaudio docs]: https://home-assistant.io/components/notify.clicksendaudio/
+[notify.discord docs]: https://home-assistant.io/components/notify.discord/
+[notify.facebook docs]: https://home-assistant.io/components/notify.facebook/
+[notify.simplepush docs]: https://home-assistant.io/components/notify.simplepush/
+[raincloud docs]: https://home-assistant.io/components/raincloud/
+[raspihats docs]: https://home-assistant.io/components/raspihats/
+[recorder docs]: https://home-assistant.io/components/recorder/
+[remote.itach docs]: https://home-assistant.io/components/remote.itach/
+[rflink docs]: https://home-assistant.io/components/rflink/
+[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
+[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
+[sensor.comed_hourly_pricing docs]: https://home-assistant.io/components/sensor.comed_hourly_pricing/
+[sensor.dsmr docs]: https://home-assistant.io/components/sensor.dsmr/
+[sensor.fedex docs]: https://home-assistant.io/components/sensor.fedex/
+[sensor.geo_rss_events docs]: https://home-assistant.io/components/sensor.geo_rss_events/
+[sensor.google_travel_time docs]: https://home-assistant.io/components/sensor.google_travel_time/
+[sensor.imap docs]: https://home-assistant.io/components/sensor.imap/
+[sensor.lyft docs]: https://home-assistant.io/components/sensor.lyft/
+[sensor.onewire docs]: https://home-assistant.io/components/sensor.onewire/
+[sensor.pvoutput docs]: https://home-assistant.io/components/sensor.pvoutput/
+[sensor.raincloud docs]: https://home-assistant.io/components/sensor.raincloud/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.thethingsnetwork docs]: https://home-assistant.io/components/sensor.thethingsnetwork/
+[sensor.tibber docs]: https://home-assistant.io/components/sensor.tibber/
+[sensor.ups docs]: https://home-assistant.io/components/sensor.ups/
+[sensor.usps docs]: https://home-assistant.io/components/sensor.usps/
+[sensor.vera docs]: https://home-assistant.io/components/sensor.vera/
+[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
+[splunk docs]: https://home-assistant.io/components/splunk/
+[switch.abode docs]: https://home-assistant.io/components/switch.abode/
+[switch.raincloud docs]: https://home-assistant.io/components/switch.raincloud/
+[switch.rflink docs]: https://home-assistant.io/components/switch.rflink/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[thethingsnetwork docs]: https://home-assistant.io/components/thethingsnetwork/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[upnp docs]: https://home-assistant.io/components/upnp/
+[usps docs]: https://home-assistant.io/components/usps/
+[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[wink docs]: https://home-assistant.io/components/wink/
+[zwave docs]: https://home-assistant.io/components/zwave/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
-[history_graph docs]: /components/history_graph/
+[history_graph docs]: https://home-assistant.io/components/history_graph/
[#9754]: https://github.com/home-assistant/home-assistant/pull/9754
[#9776]: https://github.com/home-assistant/home-assistant/pull/9776
[#9785]: https://github.com/home-assistant/home-assistant/pull/9785
@@ -404,9 +404,9 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@passie]: https://github.com/passie
[@pschmitt]: https://github.com/pschmitt
[@snjoetw]: https://github.com/snjoetw
-[camera.synology docs]: /components/camera.synology/
-[cover.rflink docs]: /components/cover.rflink/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[google docs]: /components/google/
-[light.tradfri docs]: /components/light.tradfri/
-[media_player.liveboxplaytv docs]: /components/media_player.liveboxplaytv/
+[camera.synology docs]: https://home-assistant.io/components/camera.synology/
+[cover.rflink docs]: https://home-assistant.io/components/cover.rflink/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[google docs]: https://home-assistant.io/components/google/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[media_player.liveboxplaytv docs]: https://home-assistant.io/components/media_player.liveboxplaytv/
diff --git a/source/_posts/2017-10-21-release-56.markdown b/source/_posts/2017-10-21-release-56.markdown
index 33c6472628..97699b6b47 100644
--- a/source/_posts/2017-10-21-release-56.markdown
+++ b/source/_posts/2017-10-21-release-56.markdown
@@ -16,23 +16,23 @@ og_image: /images/blog/2017-10-0.56/components.png
We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the "10000" is a [PR](https://github.com/home-assistant/home-assistant/pull/10000). Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.
-If you haven't noticed, there is now a [glossary](/docs/glossary/) that collects some Home Assistant relevant terms. Talking about the documentation: [@DubhAd](https://github.com/DubhAd) rewrote large parts of the [Z-Wave section](/docs/z-wave/). More structure to get started and to find details during the setup and the configuration.
+If you haven't noticed, there is now a [glossary](https://home-assistant.io/docs/glossary/) that collects some Home Assistant relevant terms. Talking about the documentation: [@DubhAd](https://github.com/DubhAd) rewrote large parts of the [Z-Wave section](https://home-assistant.io/docs/z-wave/). More structure to get started and to find details during the setup and the configuration.
## {% linkable_title Google Assistant / Google Home integration %}
This release includes a new component to integrate Home Assistant with Google Assistant by [Phil Kates][@philk]. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in [the documentation][google_assistant docs].
## {% linkable_title Hacktoberfest %}
-[Hacktoberfest](/blog/2017/09/29/hacktoberfest/) is still on and so far we have received a lot improvements. We can't make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
+[Hacktoberfest](https://home-assistant.io/blog/2017/09/29/hacktoberfest/) is still on and so far we have received a lot improvements. We can't make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
## {% linkable_title Map %}
-The [map][map docs] is now its own component. Similar to [configuration (`config:`)](/components/config/), it will not show up without adding it to your `configuration.yaml` file.
+The [map][map docs] is now its own component. Similar to [configuration (`config:`)](https://home-assistant.io/components/config/), it will not show up without adding it to your `configuration.yaml` file.
```yaml
map:
```
## {% linkable_title Travis CI %}
-Why not observe your [Travis CI](https://travis-ci.org) jobs with Home Assistant? [@tchellomello] created a [Travis CI][sensor.travisci docs] sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the [coffee](/blog/2017/01/28/face-coffee-wink/#first-coffee-maker-supported) is ready when the build passed.
+Why not observe your [Travis CI](https://travis-ci.org) jobs with Home Assistant? [@tchellomello] created a [Travis CI][sensor.travisci docs] sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the [coffee](https://home-assistant.io/blog/2017/01/28/face-coffee-wink/#first-coffee-maker-supported) is ready when the build passed.
## {% linkable_title New Platforms %}
@@ -416,133 +416,133 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@webworxshop]: https://github.com/webworxshop
[@zabuldon]: https://github.com/zabuldon
[@ziotibia81]: https://github.com/ziotibia81
-[__init__ docs]: /components/__init__/
-[abode docs]: /components/abode/
-[alarm_control_panel.arlo docs]: /components/alarm_control_panel.arlo/
-[alarm_control_panel.egardia docs]: /components/alarm_control_panel.egardia/
-[alexa.smart_home docs]: /components/alexa.smart_home/
-[arlo docs]: /components/arlo/
-[automation.event docs]: /docs/automation/trigger/#event-trigger
-[automation.numeric_state docs]: /docs/automation/trigger/#numeric-state-trigger
-[automation.state docs]: /docs/automation/trigger/#state-trigger
-[binary_sensor.iss docs]: /components/binary_sensor.iss/
-[binary_sensor.netatmo docs]: /components/binary_sensor.netatmo/
-[binary_sensor.skybell docs]: /components/binary_sensor.skybell/
-[binary_sensor.template docs]: /components/binary_sensor.template/
-[binary_sensor.tesla docs]: /components/binary_sensor.tesla/
-[binary_sensor.wink docs]: /components/binary_sensor.wink/
-[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
-[camera.arlo docs]: /components/camera.arlo/
-[camera.ffmpeg docs]: /components/camera.ffmpeg/
-[camera.onvif docs]: /components/camera.onvif/
-[camera.skybell docs]: /components/camera.skybell/
-[camera.synology docs]: /components/camera.synology/
-[camera.yi docs]: /components/camera.yi/
-[climate.eq3btsmart docs]: /components/climate.eq3btsmart/
-[climate.knx docs]: /components/climate.knx/
-[climate.mqtt docs]: /components/climate.mqtt/
-[climate.tesla docs]: /components/climate.tesla/
-[climate.toon docs]: /components/climate.toon/
-[cloud.iot docs]: /components/cloud.iot/
-[cover.rflink docs]: /components/cover.rflink/
-[device_tracker docs]: /components/device_tracker/
-[device_tracker.fritz docs]: /components/device_tracker.fritz/
-[device_tracker.mikrotik docs]: /components/device_tracker.mikrotik/
-[device_tracker.netgear docs]: /components/device_tracker.netgear/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.snmp docs]: /components/device_tracker.snmp/
-[device_tracker.unifi docs]: /components/device_tracker.unifi/
-[device_tracker.upc_connect docs]: /components/device_tracker.upc_connect/
-[enocean docs]: /components/enocean/
-[ffmpeg docs]: /components/ffmpeg/
-[google_assistant docs]: /components/google_assistant/
-[hassio docs]: /components/hassio/
-[homematic docs]: /components/homematic/
-[http docs]: /components/http/
-[knx docs]: /components/knx/
-[light.hue docs]: /components/light.hue/
-[light.mqtt_json docs]: /components/light.mqtt_json/
-[light.osramlightify docs]: /components/light.osramlightify/
-[light.skybell docs]: /components/light.skybell/
-[light.template docs]: /components/light.template/
-[light.tplink docs]: /components/light.tplink/
-[light.tradfri docs]: /components/light.tradfri/
-[light.yeelight docs]: /components/light.yeelight/
-[lock.tesla docs]: /components/lock.tesla/
-[map docs]: /components/map/
-[media_extractor docs]: /components/media_extractor/
-[media_player.denon docs]: /components/media_player.denon/
-[media_player.denonavr docs]: /components/media_player.denonavr/
-[media_player.dunehd docs]: /components/media_player.dunehd/
-[media_player.liveboxplaytv docs]: /components/media_player.liveboxplaytv/
-[media_player.monoprice docs]: /components/media_player.monoprice/
-[media_player.plex docs]: /components/media_player.plex/
-[media_player.yamaha docs]: /components/media_player.yamaha/
-[modbus docs]: /components/modbus/
-[mqtt docs]: /components/mqtt/
-[namecheapdns docs]: /components/namecheapdns/
-[notify.clicksend_tts docs]: /components/notify.clicksend_tts/
-[notify.html5 docs]: /components/notify.html5/
-[notify.rocketchat docs]: /components/notify.rocketchat/
-[notify.xmpp docs]: /components/notify.xmpp/
-[python_script docs]: /components/python_script/
-[raincloud docs]: /components/raincloud/
-[sensor.abode docs]: /components/sensor.abode/
-[sensor.airvisual docs]: /components/sensor.airvisual/
-[sensor.android_ip_webcam docs]: /components/sensor.android_ip_webcam/
-[sensor.arlo docs]: /components/sensor.arlo/
-[sensor.arwn docs]: /components/sensor.arwn/
-[sensor.darksky docs]: /components/sensor.darksky/
-[sensor.fitbit docs]: /components/sensor.fitbit/
-[sensor.fritzbox_callmonitor docs]: /components/sensor.fritzbox_callmonitor/
-[sensor.fritzbox_netmonitor docs]: /components/sensor.fritzbox_netmonitor/
-[sensor.glances docs]: /components/sensor.glances/
-[sensor.imap docs]: /components/sensor.imap/
-[sensor.ios docs]: /components/sensor.ios/
-[sensor.mqtt_room docs]: /components/sensor.mqtt_room/
-[sensor.netdata docs]: /components/sensor.netdata/
-[sensor.openweathermap docs]: /components/sensor.openweathermap/
-[sensor.raincloud docs]: /components/sensor.raincloud/
-[sensor.ring docs]: /components/sensor.ring/
-[sensor.serial docs]: /components/sensor.serial/
-[sensor.skybell docs]: /components/sensor.skybell/
-[sensor.snmp docs]: /components/sensor.snmp/
-[sensor.statistics docs]: /components/sensor.statistics/
-[sensor.steam_online docs]: /components/sensor.steam_online/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.tesla docs]: /components/sensor.tesla/
-[sensor.toon docs]: /components/sensor.toon/
-[sensor.tradfri docs]: /components/sensor.tradfri/
-[sensor.transmission docs]: /components/sensor.transmission/
-[sensor.travisci docs]: /components/sensor.travisci/
-[sensor.uptime docs]: /components/sensor.uptime/
-[sensor.vera docs]: /components/sensor.vera/
-[sensor.xiaomi_aqara docs]: /components/sensor.xiaomi_aqara/
-[sensor.zha docs]: /components/sensor.zha/
-[shiftr docs]: /components/shiftr/
-[skybell docs]: /components/skybell/
-[switch.flux docs]: /components/switch.flux/
-[switch.fritzdect docs]: /components/switch.fritzdect/
-[switch.hikvisioncam docs]: /components/switch.hikvisioncam/
-[switch.rainmachine docs]: /components/switch.rainmachine/
-[switch.skybell docs]: /components/switch.skybell/
-[switch.tesla docs]: /components/switch.tesla/
-[switch.toon docs]: /components/switch.toon/
-[switch.tplink docs]: /components/switch.tplink/
-[switch.wink docs]: /components/switch.wink/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[telegram_bot docs]: /components/telegram_bot/
-[tesla docs]: /components/tesla/
-[toon docs]: /components/toon/
-[tradfri docs]: /components/tradfri/
-[vacuum docs]: /components/vacuum/
-[vacuum.dyson docs]: /components/vacuum.dyson/
-[vacuum.mqtt docs]: /components/vacuum.mqtt/
-[vera docs]: /components/vera/
-[weather.openweathermap docs]: /components/weather.openweathermap/
-[wink docs]: /components/wink/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
-[zha docs]: /components/zha/
+[__init__ docs]: https://home-assistant.io/components/__init__/
+[abode docs]: https://home-assistant.io/components/abode/
+[alarm_control_panel.arlo docs]: https://home-assistant.io/components/alarm_control_panel.arlo/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
+[arlo docs]: https://home-assistant.io/components/arlo/
+[automation.event docs]: https://home-assistant.io/docs/automation/trigger/#event-trigger
+[automation.numeric_state docs]: https://home-assistant.io/docs/automation/trigger/#numeric-state-trigger
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[binary_sensor.iss docs]: https://home-assistant.io/components/binary_sensor.iss/
+[binary_sensor.netatmo docs]: https://home-assistant.io/components/binary_sensor.netatmo/
+[binary_sensor.skybell docs]: https://home-assistant.io/components/binary_sensor.skybell/
+[binary_sensor.template docs]: https://home-assistant.io/components/binary_sensor.template/
+[binary_sensor.tesla docs]: https://home-assistant.io/components/binary_sensor.tesla/
+[binary_sensor.wink docs]: https://home-assistant.io/components/binary_sensor.wink/
+[binary_sensor.xiaomi_aqara docs]: https://home-assistant.io/components/binary_sensor.xiaomi_aqara/
+[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
+[camera.ffmpeg docs]: https://home-assistant.io/components/camera.ffmpeg/
+[camera.onvif docs]: https://home-assistant.io/components/camera.onvif/
+[camera.skybell docs]: https://home-assistant.io/components/camera.skybell/
+[camera.synology docs]: https://home-assistant.io/components/camera.synology/
+[camera.yi docs]: https://home-assistant.io/components/camera.yi/
+[climate.eq3btsmart docs]: https://home-assistant.io/components/climate.eq3btsmart/
+[climate.knx docs]: https://home-assistant.io/components/climate.knx/
+[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
+[climate.tesla docs]: https://home-assistant.io/components/climate.tesla/
+[climate.toon docs]: https://home-assistant.io/components/climate.toon/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[cover.rflink docs]: https://home-assistant.io/components/cover.rflink/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.fritz docs]: https://home-assistant.io/components/device_tracker.fritz/
+[device_tracker.mikrotik docs]: https://home-assistant.io/components/device_tracker.mikrotik/
+[device_tracker.netgear docs]: https://home-assistant.io/components/device_tracker.netgear/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/
+[device_tracker.upc_connect docs]: https://home-assistant.io/components/device_tracker.upc_connect/
+[enocean docs]: https://home-assistant.io/components/enocean/
+[ffmpeg docs]: https://home-assistant.io/components/ffmpeg/
+[google_assistant docs]: https://home-assistant.io/components/google_assistant/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[http docs]: https://home-assistant.io/components/http/
+[knx docs]: https://home-assistant.io/components/knx/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.mqtt_json docs]: https://home-assistant.io/components/light.mqtt_json/
+[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
+[light.skybell docs]: https://home-assistant.io/components/light.skybell/
+[light.template docs]: https://home-assistant.io/components/light.template/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[lock.tesla docs]: https://home-assistant.io/components/lock.tesla/
+[map docs]: https://home-assistant.io/components/map/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.denon docs]: https://home-assistant.io/components/media_player.denon/
+[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
+[media_player.dunehd docs]: https://home-assistant.io/components/media_player.dunehd/
+[media_player.liveboxplaytv docs]: https://home-assistant.io/components/media_player.liveboxplaytv/
+[media_player.monoprice docs]: https://home-assistant.io/components/media_player.monoprice/
+[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/
+[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
+[modbus docs]: https://home-assistant.io/components/modbus/
+[mqtt docs]: https://home-assistant.io/components/mqtt/
+[namecheapdns docs]: https://home-assistant.io/components/namecheapdns/
+[notify.clicksend_tts docs]: https://home-assistant.io/components/notify.clicksend_tts/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.rocketchat docs]: https://home-assistant.io/components/notify.rocketchat/
+[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[raincloud docs]: https://home-assistant.io/components/raincloud/
+[sensor.abode docs]: https://home-assistant.io/components/sensor.abode/
+[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
+[sensor.android_ip_webcam docs]: https://home-assistant.io/components/sensor.android_ip_webcam/
+[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
+[sensor.arwn docs]: https://home-assistant.io/components/sensor.arwn/
+[sensor.darksky docs]: https://home-assistant.io/components/sensor.darksky/
+[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
+[sensor.fritzbox_callmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_callmonitor/
+[sensor.fritzbox_netmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
+[sensor.glances docs]: https://home-assistant.io/components/sensor.glances/
+[sensor.imap docs]: https://home-assistant.io/components/sensor.imap/
+[sensor.ios docs]: https://home-assistant.io/components/sensor.ios/
+[sensor.mqtt_room docs]: https://home-assistant.io/components/sensor.mqtt_room/
+[sensor.netdata docs]: https://home-assistant.io/components/sensor.netdata/
+[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
+[sensor.raincloud docs]: https://home-assistant.io/components/sensor.raincloud/
+[sensor.ring docs]: https://home-assistant.io/components/sensor.ring/
+[sensor.serial docs]: https://home-assistant.io/components/sensor.serial/
+[sensor.skybell docs]: https://home-assistant.io/components/sensor.skybell/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
+[sensor.steam_online docs]: https://home-assistant.io/components/sensor.steam_online/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tesla docs]: https://home-assistant.io/components/sensor.tesla/
+[sensor.toon docs]: https://home-assistant.io/components/sensor.toon/
+[sensor.tradfri docs]: https://home-assistant.io/components/sensor.tradfri/
+[sensor.transmission docs]: https://home-assistant.io/components/sensor.transmission/
+[sensor.travisci docs]: https://home-assistant.io/components/sensor.travisci/
+[sensor.uptime docs]: https://home-assistant.io/components/sensor.uptime/
+[sensor.vera docs]: https://home-assistant.io/components/sensor.vera/
+[sensor.xiaomi_aqara docs]: https://home-assistant.io/components/sensor.xiaomi_aqara/
+[sensor.zha docs]: https://home-assistant.io/components/sensor.zha/
+[shiftr docs]: https://home-assistant.io/components/shiftr/
+[skybell docs]: https://home-assistant.io/components/skybell/
+[switch.flux docs]: https://home-assistant.io/components/switch.flux/
+[switch.fritzdect docs]: https://home-assistant.io/components/switch.fritzdect/
+[switch.hikvisioncam docs]: https://home-assistant.io/components/switch.hikvisioncam/
+[switch.rainmachine docs]: https://home-assistant.io/components/switch.rainmachine/
+[switch.skybell docs]: https://home-assistant.io/components/switch.skybell/
+[switch.tesla docs]: https://home-assistant.io/components/switch.tesla/
+[switch.toon docs]: https://home-assistant.io/components/switch.toon/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[switch.wink docs]: https://home-assistant.io/components/switch.wink/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[tesla docs]: https://home-assistant.io/components/tesla/
+[toon docs]: https://home-assistant.io/components/toon/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[vacuum docs]: https://home-assistant.io/components/vacuum/
+[vacuum.dyson docs]: https://home-assistant.io/components/vacuum.dyson/
+[vacuum.mqtt docs]: https://home-assistant.io/components/vacuum.mqtt/
+[vera docs]: https://home-assistant.io/components/vera/
+[weather.openweathermap docs]: https://home-assistant.io/components/weather.openweathermap/
+[wink docs]: https://home-assistant.io/components/wink/
+[xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/
+[zha docs]: https://home-assistant.io/components/zha/
[#10024]: https://github.com/home-assistant/home-assistant/pull/10024
[#10029]: https://github.com/home-assistant/home-assistant/pull/10029
[@bieniu]: https://github.com/bieniu
diff --git a/source/_posts/2017-10-28-demo.markdown b/source/_posts/2017-10-28-demo.markdown
index a64b3e18d8..d6d9d89582 100644
--- a/source/_posts/2017-10-28-demo.markdown
+++ b/source/_posts/2017-10-28-demo.markdown
@@ -13,7 +13,7 @@ og_image: /images/blog/2017-10-interactive-demo/demo-random.png
If you are planning to host a Home Assistant meetup or doing a talk, then you probably want to show Home Assistant to an audience. You could use a Wireless router, bulbs, switches, and a single board computer to do a realistic demo. For a workshop, this is what I usually do because I think that working with physical hardware is more fun for the participants. The issue is that you need time to set up, power and space. For a talk or in a location, where you only have a beamer and a table or a lectern, the physical hardware approach is not very convenient.
-The simplest way to show Home Assistant to others is the online demo at [/demo/](/demo/)
+The simplest way to show Home Assistant to others is the online demo at [https://home-assistant.io/demo/](https://home-assistant.io/demo/)
-
-
-
-
-
- 
diff --git a/source/_posts/2017-11-02-secure-shell-tunnel.markdown b/source/_posts/2017-11-02-secure-shell-tunnel.markdown
index 1d02e48e3b..0d346e5389 100644
--- a/source/_posts/2017-11-02-secure-shell-tunnel.markdown
+++ b/source/_posts/2017-11-02-secure-shell-tunnel.markdown
@@ -13,7 +13,7 @@ og_image: /images/blog/2017-11-ssh/social.png
Most system engineers are very familiar with [SSH (Secure shell)](https://en.wikipedia.org/wiki/Secure_Shell). This tool which contains a server part and a client part is used to access a remote system in a secure way. It can also help you if your are running Home Assistant but don't want to expose it to the public. On a Linux system SSH is often available by default. If you are using a Windows installation additional steps are required which are not covered here.
-In this blog post we are going to use the tunneling option of SSH to create a secure connection and forward the Home Assistant frontend to a local system.
+In this blog post we are going to use the tunneling option of SSH to create a secure connection and forward the Home Assistant frontend to a local system.
@@ -22,7 +22,7 @@ The involved parties are:
- **Remote system**: Where Home Assistant is running, usually in your home network.
- **Local system**: Where you want to see the frontend.
-The prerequirements are that you need to allow the forwarding of port 22 from your router to the system where Home Assistant is running in your network. It might also be needed that you enable the SSH daemon by `$ sudo systemctl start sshd` on the remote system and to adjust the host firewall. If you are running [Hass.io](/hassio/) then enable the [SSH Server add-on](/addons/ssh/). You must also have a public IP address or hostname which can be provided by dynamic DNS (e.g., [NO-IP](https://www.noip.com/) or [DuckDNS](https://www.duckdns.org/)).
+The prerequirements are that you need to allow the forwarding of port 22 from your router to the system where Home Assistant is running in your network. It might also be needed that you enable the SSH daemon by `$ sudo systemctl start sshd` on the remote system and to adjust the host firewall. If you are running [Hass.io](https://home-assistant.io/hassio/) then enable the [SSH Server add-on](https://home-assistant.io/addons/ssh/). You must also have a public IP address or hostname which can be provided by dynamic DNS (e.g., [NO-IP](https://www.noip.com/) or [DuckDNS](https://www.duckdns.org/)).
On your local system you need only a SSH client and you need to be in a network where SSH is allowed.
First let's have a look at the command we are going to use. Use `man ssh` to get more information.
@@ -38,7 +38,7 @@ $ ssh -L 8000:localhost:8123 user@[IP_ADDRESS_REMOTE]
|_ We want to do local port forwarding.
```
-A possible example could look like the command below.
+A possible example could look like the command below.
```bash
$ ssh -L 8000:localhost:8123 ha@192.168.0.11
@@ -50,11 +50,11 @@ The first time you establish the connection you need to accept the fingerprint.
The authenticity of host '192.168.0.11 (192.168.0.11)' can't be established.
ECDSA key fingerprint is SHA256:asdf2faasd4gk45454fadr78wfadfasdfeg4vvvsae33.
ECDSA key fingerprint is MD5:44:d4:f7:44:d4:aa:b8:de:ef:09:3e:0d:4e:12:11:09.
-Are you sure you want to continue connecting (yes/no)?
+Are you sure you want to continue connecting (yes/no)?
Warning: Permanently added '192.168.0.162' (ECDSA) to the list of known hosts.
-ha@192.168.0.11's password:
+ha@192.168.0.11's password:
Last login: Fri Oct 27 17:50:09 2017
-[ha@home-assistant ~]$
+[ha@home-assistant ~]$
```
Now you are able to use your frontend on your local system: [http://localhost:8000](http://localhost:8000)
diff --git a/source/_posts/2017-11-04-release-57.markdown b/source/_posts/2017-11-04-release-57.markdown
index 5c689b185a..dc054b035c 100644
--- a/source/_posts/2017-11-04-release-57.markdown
+++ b/source/_posts/2017-11-04-release-57.markdown
@@ -32,7 +32,7 @@ As part of getting translations to work, we did a lot of cleanup work on the fro
[Hacktoberfest](https://hacktoberfest.digitalocean.com/) 2017 is over! FINALLY. Each year we're attracting more developers that want to contribute to Home Assistant. This is great but also very exhausting to our code reviewers. I want to give an enormous gigantic huge big shout out to our reviewers @pvizeli, @andrey-git, @armills, @MartinHjelmare, @fabaff. You have all done an amazing job and we couldn't run Home Assistant without any of you! ❤
-Hacktoberfest is obviously about the people contributing to open source. Big thanks to everyone that has taken the time to learn our code base and make contributions. We hope it was a pleasant experience and show how great open source can be. Hope to see many contributions in the future 👍
+Hacktoberfest is obviously about the people contributing to open source. Big thanks to everyone that has taken the time to learn our code base and make contributions. We hope it was a pleasant experience and show how great open source can be. Hope to see many contributions in the future 👍
Here are our Hacktoberfest 2017 stats. It's a miracle everyone is still alive:
@@ -56,7 +56,7 @@ Long time contributor [@lwis] jumped on the case and managed to migrate our inte
## {% linkable_title Timer %}
-Okay, one more highlight before we'll let you check out the changelog. Contributor [@danielperna84] (famous for creating the [HASS Configurator](/addons/configurator/)), had another great component up his sleeve: the Timer component. With the timer component you'll be able to start countdown timers. A neat tool for your automation toolbox! More info in the [timer docs].
+Okay, one more highlight before we'll let you check out the changelog. Contributor [@danielperna84] (famous for creating the [HASS Configurator](https://home-assistant.io/addons/configurator/)), had another great component up his sleeve: the Timer component. With the timer component you'll be able to start countdown timers. A neat tool for your automation toolbox! More info in the [timer docs].
## {% linkable_title New Platforms %}
@@ -110,7 +110,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
## {% linkable_title Breaking Changes %}
- IKEA TRÅDFRI: We no longer support entering the key in the configuration. ([@lwis] - [#10282]) ([tradfri docs]) (breaking change)
-- API.AI was renamed to [Dialogflow](/components/dialogflow/). This requires to rename the entry in your `configuration.yaml` file from `apiai:` to `dialogflow`. ([@fabaff] - [#10006]) ([dialogflow docs]) (breaking change)
+- API.AI was renamed to [Dialogflow](https://home-assistant.io/components/dialogflow/). This requires to rename the entry in your `configuration.yaml` file from `apiai:` to `dialogflow`. ([@fabaff] - [#10006]) ([dialogflow docs]) (breaking change)
- Wink: Removed support for entering your `username` and `password` in your config. Use the [new authentication method][wink-auth] instead. ([@w1ll1am23] - [#10277]) ([wink docs]) (breaking change)
- Use feed name assigned in EmonCMS if there is one. This changes the default behavior but still uses configured 'name' if it's set, so it won't break the configuration of people who have customized their feed names in HA config. ([@KlaasH] - [#10021]) ([sensor.emoncms docs]) (breaking change)
- The `namecheapdns` now uses `password:` instead of `access_token` in the configuration. Also, `host` is now optional which allow people who are not using subdomains to keep their configuration shorter. ([@fabaff] - [#10063]) ([namecheapdns docs]) (breaking change)
@@ -120,7 +120,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
This fixes errors when an entity has an attribute that is not "a string, bytearray, int, float or None" and mqtt_statestream is used. As of now, the attribute is just handed over to paho, and paho can only send the aforementioned types. This patch fixes the issue by just casting everything to string before handing it over to paho.
- There are a number of components / entities which have "other" attributes, e.g., light that have an RGB attribute which is a list. ([@tinloaf] - [#9872]) ([mqtt_statestream docs]) (breaking change)
+ There are a number of components / entities which have "other" attributes, e.g. light that have an RGB attribute which is a list. ([@tinloaf] - [#9872]) ([mqtt_statestream docs]) (breaking change)
- Generic thermostat: the configuration option `tolerance` has been removed and has been replaced by `cold_tolerance` and `hot_tolerance`. This allows on and off states to have different error bands. ([@biggms] - [#9843]) ([climate.generic_thermostat docs]) (breaking change)
- Developers only: frontend has been refactored. The method `register_panel` has been turned into a coroutine function called `async_register_panel`. The parameter `url_path` has been renamed to `frontend_url_path`. For frontend, development, you no longer pass `development: 1` to the http component but instead configure the frontend component to be in development mode by pointing it at a local checkout of the Polymer repo: ([@balloob] - [#9915]) (breaking change)
@@ -522,138 +522,138 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@wardcraigj]: https://github.com/wardcraigj
[@ypollart]: https://github.com/ypollart
[@zabuldon]: https://github.com/zabuldon
-[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
-[alexa.smart_home docs]: /components/alexa.smart_home/
-[api docs]: /components/api/
-[automation.event docs]: /docs/automation/trigger/#event-trigger
-[automation.numeric_state docs]: /docs/automation/trigger/#numeric-state-trigger
-[axis docs]: /components/axis/
-[binary_sensor.axis docs]: /components/binary_sensor.axis/
-[binary_sensor.gc100 docs]: /components/binary_sensor.gc100/
-[binary_sensor.linode docs]: /components/binary_sensor.linode/
-[binary_sensor.random docs]: /components/binary_sensor.random/
-[binary_sensor.rfxtrx docs]: /components/binary_sensor.rfxtrx/
-[binary_sensor.ring docs]: /components/binary_sensor.ring/
-[binary_sensor.tellduslive docs]: /components/binary_sensor.tellduslive/
-[binary_sensor.trend docs]: /components/binary_sensor.trend/
-[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
-[camera docs]: /components/camera/
-[camera.ring docs]: /components/camera.ring/
-[climate.ephember docs]: /components/climate.ephember/
-[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
-[climate.honeywell docs]: /components/climate.honeywell/
-[climate.toon docs]: /components/climate.toon/
-[cloud docs]: /components/cloud/
-[cloud.iot docs]: /components/cloud.iot/
-[cover.template docs]: /components/cover.template/
-[device_tracker docs]: /components/device_tracker/
-[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/
-[device_tracker.automatic docs]: /components/device_tracker.automatic/
-[device_tracker.geofency docs]: /components/device_tracker.geofency/
-[device_tracker.mikrotik docs]: /components/device_tracker.mikrotik/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.snmp docs]: /components/device_tracker.snmp/
-[device_tracker.ubus docs]: /components/device_tracker.ubus/
-[dialogflow docs]: /components/dialogflow/
-[downloader docs]: /components/downloader/
-[duckdns docs]: /components/duckdns/
-[fan.mqtt docs]: /components/fan.mqtt/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[gc100 docs]: /components/gc100/
-[google_assistant docs]: /components/google_assistant/
-[google_domains docs]: /components/google_domains/
-[hassio docs]: /components/hassio/
-[history docs]: /components/history/
-[http docs]: /components/http/
-[image_processing.openalpr_local docs]: /components/image_processing.openalpr_local/
-[input_number docs]: /components/input_number/
-[input_text docs]: /components/input_text/
-[introduction docs]: /components/introduction/
-[light.hue docs]: /components/light.hue/
-[light.hyperion docs]: /components/light.hyperion/
-[light.mqtt docs]: /components/light.mqtt/
-[light.tradfri docs]: /components/light.tradfri/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[light.yeelight docs]: /components/light.yeelight/
-[linode docs]: /components/linode/
-[logbook docs]: /components/logbook/
-[mailbox docs]: /components/mailbox/
-[media_extractor docs]: /components/media_extractor/
-[media_player docs]: /components/media_player/
-[media_player.liveboxplaytv docs]: /components/media_player.liveboxplaytv/
-[media_player.monoprice docs]: /components/media_player.monoprice/
-[media_player.plex docs]: /components/media_player.plex/
-[media_player.russound_rnet docs]: /components/media_player.russound_rnet/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.yamaha docs]: /components/media_player.yamaha/
-[mqtt_statestream docs]: /components/mqtt_statestream/
-[namecheapdns docs]: /components/namecheapdns/
-[no_ip docs]: /components/no_ip/
-[notify.aws_lambda docs]: /components/notify.aws_lambda/
-[notify.aws_sns docs]: /components/notify.aws_sns/
-[notify.aws_sqs docs]: /components/notify.aws_sqs/
-[notify.clickatell docs]: /components/notify.clickatell/
-[notify.sendgrid docs]: /components/notify.sendgrid/
-[notify.yessssms docs]: /components/notify.yessssms/
-[panel_custom docs]: /components/panel_custom/
-[persistent_notification docs]: /components/persistent_notification/
-[plant docs]: /components/plant/
-[raincloud docs]: /components/raincloud/
-[remember_the_milk docs]: /components/remember_the_milk/
-[rfxtrx docs]: /components/rfxtrx/
-[ring docs]: /components/ring/
-[sensor.coinmarketcap docs]: /components/sensor.coinmarketcap/
-[sensor.emoncms docs]: /components/sensor.emoncms/
-[sensor.fail2ban docs]: /components/sensor.fail2ban/
-[sensor.gitter docs]: /components/sensor.gitter/
-[sensor.glances docs]: /components/sensor.glances/
-[sensor.google_travel_time docs]: /components/sensor.google_travel_time/
-[sensor.hddtemp docs]: /components/sensor.hddtemp/
-[sensor.imap docs]: /components/sensor.imap/
-[sensor.irish_rail_transport docs]: /components/sensor.irish_rail_transport/
-[sensor.lastfm docs]: /components/sensor.lastfm/
-[sensor.luftdaten docs]: /components/sensor.luftdaten/
-[sensor.nederlandse_spoorwegen docs]: /components/sensor.nederlandse_spoorwegen/
-[sensor.radarr docs]: /components/sensor.radarr/
-[sensor.rest docs]: /components/sensor.rest/
-[sensor.ring docs]: /components/sensor.ring/
-[sensor.scrape docs]: /components/sensor.scrape/
-[sensor.snmp docs]: /components/sensor.snmp/
-[sensor.sonarr docs]: /components/sensor.sonarr/
-[sensor.speedtest docs]: /components/sensor.speedtest/
-[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
-[sensor.synologydsm docs]: /components/sensor.synologydsm/
-[sensor.sytadin docs]: /components/sensor.sytadin/
-[sensor.toon docs]: /components/sensor.toon/
-[sensor.uk_transport docs]: /components/sensor.uk_transport/
-[sensor.whois docs]: /components/sensor.whois/
-[shopping_list docs]: /components/shopping_list/
-[switch.deluge docs]: /components/switch.deluge/
-[switch.flux docs]: /components/switch.flux/
-[switch.gc100 docs]: /components/switch.gc100/
-[switch.snmp docs]: /components/switch.snmp/
-[switch.template docs]: /components/switch.template/
-[switch.toon docs]: /components/switch.toon/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[tellduslive docs]: /components/tellduslive/
-[tellstick docs]: /components/tellstick/
-[tesla docs]: /components/tesla/
-[timer docs]: /components/timer/
-[toon docs]: /components/toon/
-[tradfri docs]: /components/tradfri/
-[tts.amazon_polly docs]: /components/tts.amazon_polly/
-[tts.microsoft docs]: /components/tts.microsoft/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[vera docs]: /components/vera/
-[wink docs]: /components/wink/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
+[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
+[api docs]: https://home-assistant.io/components/api/
+[automation.event docs]: https://home-assistant.io/docs/automation/trigger/#event-trigger
+[automation.numeric_state docs]: https://home-assistant.io/docs/automation/trigger/#numeric-state-trigger
+[axis docs]: https://home-assistant.io/components/axis/
+[binary_sensor.axis docs]: https://home-assistant.io/components/binary_sensor.axis/
+[binary_sensor.gc100 docs]: https://home-assistant.io/components/binary_sensor.gc100/
+[binary_sensor.linode docs]: https://home-assistant.io/components/binary_sensor.linode/
+[binary_sensor.random docs]: https://home-assistant.io/components/binary_sensor.random/
+[binary_sensor.rfxtrx docs]: https://home-assistant.io/components/binary_sensor.rfxtrx/
+[binary_sensor.ring docs]: https://home-assistant.io/components/binary_sensor.ring/
+[binary_sensor.tellduslive docs]: https://home-assistant.io/components/binary_sensor.tellduslive/
+[binary_sensor.trend docs]: https://home-assistant.io/components/binary_sensor.trend/
+[binary_sensor.xiaomi_aqara docs]: https://home-assistant.io/components/binary_sensor.xiaomi_aqara/
+[camera docs]: https://home-assistant.io/components/camera/
+[camera.ring docs]: https://home-assistant.io/components/camera.ring/
+[climate.ephember docs]: https://home-assistant.io/components/climate.ephember/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.honeywell docs]: https://home-assistant.io/components/climate.honeywell/
+[climate.toon docs]: https://home-assistant.io/components/climate.toon/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[cover.template docs]: https://home-assistant.io/components/cover.template/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/
+[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/
+[device_tracker.geofency docs]: https://home-assistant.io/components/device_tracker.geofency/
+[device_tracker.mikrotik docs]: https://home-assistant.io/components/device_tracker.mikrotik/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[device_tracker.ubus docs]: https://home-assistant.io/components/device_tracker.ubus/
+[dialogflow docs]: https://home-assistant.io/components/dialogflow/
+[downloader docs]: https://home-assistant.io/components/downloader/
+[duckdns docs]: https://home-assistant.io/components/duckdns/
+[fan.mqtt docs]: https://home-assistant.io/components/fan.mqtt/
+[fan.xiaomi_miio docs]: https://home-assistant.io/components/fan.xiaomi_miio/
+[gc100 docs]: https://home-assistant.io/components/gc100/
+[google_assistant docs]: https://home-assistant.io/components/google_assistant/
+[google_domains docs]: https://home-assistant.io/components/google_domains/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[history docs]: https://home-assistant.io/components/history/
+[http docs]: https://home-assistant.io/components/http/
+[image_processing.openalpr_local docs]: https://home-assistant.io/components/image_processing.openalpr_local/
+[input_number docs]: https://home-assistant.io/components/input_number/
+[input_text docs]: https://home-assistant.io/components/input_text/
+[introduction docs]: https://home-assistant.io/components/introduction/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.hyperion docs]: https://home-assistant.io/components/light.hyperion/
+[light.mqtt docs]: https://home-assistant.io/components/light.mqtt/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[linode docs]: https://home-assistant.io/components/linode/
+[logbook docs]: https://home-assistant.io/components/logbook/
+[mailbox docs]: https://home-assistant.io/components/mailbox/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player docs]: https://home-assistant.io/components/media_player/
+[media_player.liveboxplaytv docs]: https://home-assistant.io/components/media_player.liveboxplaytv/
+[media_player.monoprice docs]: https://home-assistant.io/components/media_player.monoprice/
+[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/
+[media_player.russound_rnet docs]: https://home-assistant.io/components/media_player.russound_rnet/
+[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
+[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
+[mqtt_statestream docs]: https://home-assistant.io/components/mqtt_statestream/
+[namecheapdns docs]: https://home-assistant.io/components/namecheapdns/
+[no_ip docs]: https://home-assistant.io/components/no_ip/
+[notify.aws_lambda docs]: https://home-assistant.io/components/notify.aws_lambda/
+[notify.aws_sns docs]: https://home-assistant.io/components/notify.aws_sns/
+[notify.aws_sqs docs]: https://home-assistant.io/components/notify.aws_sqs/
+[notify.clickatell docs]: https://home-assistant.io/components/notify.clickatell/
+[notify.sendgrid docs]: https://home-assistant.io/components/notify.sendgrid/
+[notify.yessssms docs]: https://home-assistant.io/components/notify.yessssms/
+[panel_custom docs]: https://home-assistant.io/components/panel_custom/
+[persistent_notification docs]: https://home-assistant.io/components/persistent_notification/
+[plant docs]: https://home-assistant.io/components/plant/
+[raincloud docs]: https://home-assistant.io/components/raincloud/
+[remember_the_milk docs]: https://home-assistant.io/components/remember_the_milk/
+[rfxtrx docs]: https://home-assistant.io/components/rfxtrx/
+[ring docs]: https://home-assistant.io/components/ring/
+[sensor.coinmarketcap docs]: https://home-assistant.io/components/sensor.coinmarketcap/
+[sensor.emoncms docs]: https://home-assistant.io/components/sensor.emoncms/
+[sensor.fail2ban docs]: https://home-assistant.io/components/sensor.fail2ban/
+[sensor.gitter docs]: https://home-assistant.io/components/sensor.gitter/
+[sensor.glances docs]: https://home-assistant.io/components/sensor.glances/
+[sensor.google_travel_time docs]: https://home-assistant.io/components/sensor.google_travel_time/
+[sensor.hddtemp docs]: https://home-assistant.io/components/sensor.hddtemp/
+[sensor.imap docs]: https://home-assistant.io/components/sensor.imap/
+[sensor.irish_rail_transport docs]: https://home-assistant.io/components/sensor.irish_rail_transport/
+[sensor.lastfm docs]: https://home-assistant.io/components/sensor.lastfm/
+[sensor.luftdaten docs]: https://home-assistant.io/components/sensor.luftdaten/
+[sensor.nederlandse_spoorwegen docs]: https://home-assistant.io/components/sensor.nederlandse_spoorwegen/
+[sensor.radarr docs]: https://home-assistant.io/components/sensor.radarr/
+[sensor.rest docs]: https://home-assistant.io/components/sensor.rest/
+[sensor.ring docs]: https://home-assistant.io/components/sensor.ring/
+[sensor.scrape docs]: https://home-assistant.io/components/sensor.scrape/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.sonarr docs]: https://home-assistant.io/components/sensor.sonarr/
+[sensor.speedtest docs]: https://home-assistant.io/components/sensor.speedtest/
+[sensor.swiss_public_transport docs]: https://home-assistant.io/components/sensor.swiss_public_transport/
+[sensor.synologydsm docs]: https://home-assistant.io/components/sensor.synologydsm/
+[sensor.sytadin docs]: https://home-assistant.io/components/sensor.sytadin/
+[sensor.toon docs]: https://home-assistant.io/components/sensor.toon/
+[sensor.uk_transport docs]: https://home-assistant.io/components/sensor.uk_transport/
+[sensor.whois docs]: https://home-assistant.io/components/sensor.whois/
+[shopping_list docs]: https://home-assistant.io/components/shopping_list/
+[switch.deluge docs]: https://home-assistant.io/components/switch.deluge/
+[switch.flux docs]: https://home-assistant.io/components/switch.flux/
+[switch.gc100 docs]: https://home-assistant.io/components/switch.gc100/
+[switch.snmp docs]: https://home-assistant.io/components/switch.snmp/
+[switch.template docs]: https://home-assistant.io/components/switch.template/
+[switch.toon docs]: https://home-assistant.io/components/switch.toon/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[tellduslive docs]: https://home-assistant.io/components/tellduslive/
+[tellstick docs]: https://home-assistant.io/components/tellstick/
+[tesla docs]: https://home-assistant.io/components/tesla/
+[timer docs]: https://home-assistant.io/components/timer/
+[toon docs]: https://home-assistant.io/components/toon/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[tts.amazon_polly docs]: https://home-assistant.io/components/tts.amazon_polly/
+[tts.microsoft docs]: https://home-assistant.io/components/tts.microsoft/
+[vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[vera docs]: https://home-assistant.io/components/vera/
+[wink docs]: https://home-assistant.io/components/wink/
+[xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/
[ikea email]: https://twitter.com/home_assistant/status/925373865802502144
-[wink-auth]: /components/wink/#authenticate-using-developerwinkcomhttpsdeveloperwinkcom
+[wink-auth]: https://home-assistant.io/components/wink/#authenticate-using-developerwinkcomhttpsdeveloperwinkcom
[#10384]: https://github.com/home-assistant/home-assistant/pull/10384
[#10428]: https://github.com/home-assistant/home-assistant/pull/10428
[@stefan-jonasson]: https://github.com/stefan-jonasson
[@tchellomello]: https://github.com/tchellomello
-[binary_sensor.ring docs]: /components/binary_sensor.ring/
-[camera.ring docs]: /components/camera.ring/
-[sensor.ring docs]: /components/sensor.ring/
-[tellstick docs]: /components/tellstick/
+[binary_sensor.ring docs]: https://home-assistant.io/components/binary_sensor.ring/
+[camera.ring docs]: https://home-assistant.io/components/camera.ring/
+[sensor.ring docs]: https://home-assistant.io/components/sensor.ring/
+[tellstick docs]: https://home-assistant.io/components/tellstick/
diff --git a/source/_posts/2017-11-05-frontend-translations.markdown b/source/_posts/2017-11-05-frontend-translations.markdown
index aefa5588af..bf6cc8db75 100644
--- a/source/_posts/2017-11-05-frontend-translations.markdown
+++ b/source/_posts/2017-11-05-frontend-translations.markdown
@@ -17,9 +17,9 @@ The Home Assistant sidebar in 12 different languages.
## {% linkable_title Translations %}
-As mentioned in the [0.57 release notes](/blog/2017/11/04/release-57/), Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. [@c727] took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with [Lokalise](https://lokalise.co/) to manage our translations!
+As mentioned in the [0.57 release notes](https://home-assistant.io/blog/2017/11/04/release-57/), Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. [@c727] took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with [Lokalise](https://lokalise.co/) to manage our translations!
-Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our [public signup link](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/), and start translating right away. We’ve created a [translation startup guide](/developers/frontend_translation/) with additional details about how to contribute. Instructions are provided there for how to request a new language.
+Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our [public signup link](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/), and start translating right away. We’ve created a [translation startup guide](https://home-assistant.io/developers/frontend_translation/) with additional details about how to contribute. Instructions are provided there for how to request a new language.
Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!
diff --git a/source/_posts/2017-11-18-release-58.markdown b/source/_posts/2017-11-18-release-58.markdown
index d7e7fbbc25..e930abae6f 100644
--- a/source/_posts/2017-11-18-release-58.markdown
+++ b/source/_posts/2017-11-18-release-58.markdown
@@ -25,7 +25,7 @@ Talking about our translators, we now have 445 people with an account to help wi
And because more translations is more better, [@robbiet480] has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.
-[Learn more about how to help with translations](/blog/2017/11/05/frontend-translations/)
+[Learn more about how to help with translations](https://home-assistant.io/blog/2017/11/05/frontend-translations/)
## {% linkable_title Frontend improvements continue %}
@@ -381,114 +381,114 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@w1ll1am23]: https://github.com/w1ll1am23
[@wardcraigj]: https://github.com/wardcraigj
[@ziotibia81]: https://github.com/ziotibia81
-[abode docs]: /components/abode/
-[alarm_control_panel.spc docs]: /components/alarm_control_panel.spc/
-[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
-[apple_tv docs]: /components/apple_tv/
-[arlo docs]: /components/arlo/
-[axis docs]: /components/axis/
-[binary_sensor docs]: /components/binary_sensor/
-[binary_sensor.aurora docs]: /components/binary_sensor.aurora/
-[binary_sensor.spc docs]: /components/binary_sensor.spc/
-[binary_sensor.vultr docs]: /components/binary_sensor.vultr/
-[camera.arlo docs]: /components/camera.arlo/
-[climate docs]: /components/climate/
-[climate.eq3btsmart docs]: /components/climate.eq3btsmart/
-[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
-[climate.homematic docs]: /components/climate.homematic/
-[climate.knx docs]: /components/climate.knx/
-[climate.wink docs]: /components/climate.wink/
-[cloud docs]: /components/cloud/
-[cloud.auth_api docs]: /components/cloud.auth_api/
-[cloud.const docs]: /components/cloud.const/
-[cloud.http_api docs]: /components/cloud.http_api/
-[cloud.iot docs]: /components/cloud.iot/
-[config.zwave docs]: /components/config.zwave/
-[configurator docs]: /components/configurator/
-[counter docs]: /components/counter/
-[cover.mqtt docs]: /components/cover.mqtt/
-[device_tracker docs]: /components/device_tracker/
-[device_tracker.hitron_coda docs]: /components/device_tracker.hitron_coda/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.snmp docs]: /components/device_tracker.snmp/
-[device_tracker.tile docs]: /components/device_tracker.tile/
-[device_tracker.tplink docs]: /components/device_tracker.tplink/
-[device_tracker.upc_connect docs]: /components/device_tracker.upc_connect/
-[downloader docs]: /components/downloader/
-[gc100 docs]: /components/gc100/
-[google_assistant.smart_home docs]: /components/google_assistant.smart_home/
-[hassio docs]: /components/hassio/
-[influxdb docs]: /components/influxdb/
-[input_datetime docs]: /components/input_datetime/
-[knx docs]: /components/knx/
-[lametric docs]: /components/lametric/
-[light docs]: /components/light/
-[light.tradfri docs]: /components/light.tradfri/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[lutron_caseta docs]: /components/lutron_caseta/
-[media_extractor docs]: /components/media_extractor/
-[media_player docs]: /components/media_player/
-[media_player.bluesound docs]: /components/media_player.bluesound/
-[media_player.snapcast docs]: /components/media_player.snapcast/
-[media_player.universal docs]: /components/media_player.universal/
-[media_player.webostv docs]: /components/media_player.webostv/
-[media_player.yamaha_musiccast docs]: /components/media_player.yamaha_musiccast/
-[mqtt docs]: /components/mqtt/
-[mqtt.discovery docs]: /components/mqtt.discovery/
-[mqtt.server docs]: /components/mqtt.server/
-[mqtt_statestream docs]: /components/mqtt_statestream/
-[neato docs]: /components/neato/
-[no_ip docs]: /components/no_ip/
-[notify.apns docs]: /components/notify.apns/
-[notify.free_mobile docs]: /components/notify.free_mobile/
-[notify.html5 docs]: /components/notify.html5/
-[notify.lametric docs]: /components/notify.lametric/
-[notify.simplepush docs]: /components/notify.simplepush/
-[notify.telegram docs]: /components/notify.telegram/
-[python_script docs]: /components/python_script/
-[remote docs]: /components/remote/
-[remote.harmony docs]: /components/remote.harmony/
-[ring docs]: /components/ring/
-[sensor.airvisual docs]: /components/sensor.airvisual/
-[sensor.arlo docs]: /components/sensor.arlo/
-[sensor.haveibeenpwned docs]: /components/sensor.haveibeenpwned/
-[sensor.lacrosse docs]: /components/sensor.lacrosse/
-[sensor.london_air docs]: /components/sensor.london_air/
-[sensor.modbus docs]: /components/sensor.modbus/
-[sensor.neato docs]: /components/sensor.neato/
-[sensor.nederlandse_spoorwegen docs]: /components/sensor.nederlandse_spoorwegen/
-[sensor.pyload docs]: /components/sensor.pyload/
-[sensor.serial docs]: /components/sensor.serial/
-[sensor.snmp docs]: /components/sensor.snmp/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.tibber docs]: /components/sensor.tibber/
-[sensor.viaggiatreno docs]: /components/sensor.viaggiatreno/
-[sensor.vultr docs]: /components/sensor.vultr/
-[sensor.wunderground docs]: /components/sensor.wunderground/
-[sensor.yweather docs]: /components/sensor.yweather/
-[sensor.zamg docs]: /components/sensor.zamg/
-[spc docs]: /components/spc/
-[switch.broadlink docs]: /components/switch.broadlink/
-[switch.hikvisioncam docs]: /components/switch.hikvisioncam/
-[switch.modbus docs]: /components/switch.modbus/
-[switch.neato docs]: /components/switch.neato/
-[switch.snmp docs]: /components/switch.snmp/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[system_log docs]: /components/system_log/
-[telegram_bot docs]: /components/telegram_bot/
-[telegram_bot.polling docs]: /components/telegram_bot.polling/
-[tradfri docs]: /components/tradfri/
-[tts docs]: /components/tts/
-[tts.google docs]: /components/tts.google/
-[tts.yandextts docs]: /components/tts.yandextts/
-[vacuum.neato docs]: /components/vacuum.neato/
-[verisure docs]: /components/verisure/
-[volvooncall docs]: /components/volvooncall/
-[vultr docs]: /components/vultr/
-[weather docs]: /components/weather/
-[weather.demo docs]: /components/weather.demo/
-[websocket_api docs]: /components/websocket_api/
-[zwave docs]: /components/zwave/
+[abode docs]: https://home-assistant.io/components/abode/
+[alarm_control_panel.spc docs]: https://home-assistant.io/components/alarm_control_panel.spc/
+[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/
+[apple_tv docs]: https://home-assistant.io/components/apple_tv/
+[arlo docs]: https://home-assistant.io/components/arlo/
+[axis docs]: https://home-assistant.io/components/axis/
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.aurora docs]: https://home-assistant.io/components/binary_sensor.aurora/
+[binary_sensor.spc docs]: https://home-assistant.io/components/binary_sensor.spc/
+[binary_sensor.vultr docs]: https://home-assistant.io/components/binary_sensor.vultr/
+[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.eq3btsmart docs]: https://home-assistant.io/components/climate.eq3btsmart/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.homematic docs]: https://home-assistant.io/components/climate.homematic/
+[climate.knx docs]: https://home-assistant.io/components/climate.knx/
+[climate.wink docs]: https://home-assistant.io/components/climate.wink/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.auth_api docs]: https://home-assistant.io/components/cloud.auth_api/
+[cloud.const docs]: https://home-assistant.io/components/cloud.const/
+[cloud.http_api docs]: https://home-assistant.io/components/cloud.http_api/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[config.zwave docs]: https://home-assistant.io/components/config.zwave/
+[configurator docs]: https://home-assistant.io/components/configurator/
+[counter docs]: https://home-assistant.io/components/counter/
+[cover.mqtt docs]: https://home-assistant.io/components/cover.mqtt/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.hitron_coda docs]: https://home-assistant.io/components/device_tracker.hitron_coda/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[device_tracker.tile docs]: https://home-assistant.io/components/device_tracker.tile/
+[device_tracker.tplink docs]: https://home-assistant.io/components/device_tracker.tplink/
+[device_tracker.upc_connect docs]: https://home-assistant.io/components/device_tracker.upc_connect/
+[downloader docs]: https://home-assistant.io/components/downloader/
+[gc100 docs]: https://home-assistant.io/components/gc100/
+[google_assistant.smart_home docs]: https://home-assistant.io/components/google_assistant.smart_home/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[influxdb docs]: https://home-assistant.io/components/influxdb/
+[input_datetime docs]: https://home-assistant.io/components/input_datetime/
+[knx docs]: https://home-assistant.io/components/knx/
+[lametric docs]: https://home-assistant.io/components/lametric/
+[light docs]: https://home-assistant.io/components/light/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[lutron_caseta docs]: https://home-assistant.io/components/lutron_caseta/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player docs]: https://home-assistant.io/components/media_player/
+[media_player.bluesound docs]: https://home-assistant.io/components/media_player.bluesound/
+[media_player.snapcast docs]: https://home-assistant.io/components/media_player.snapcast/
+[media_player.universal docs]: https://home-assistant.io/components/media_player.universal/
+[media_player.webostv docs]: https://home-assistant.io/components/media_player.webostv/
+[media_player.yamaha_musiccast docs]: https://home-assistant.io/components/media_player.yamaha_musiccast/
+[mqtt docs]: https://home-assistant.io/components/mqtt/
+[mqtt.discovery docs]: https://home-assistant.io/components/mqtt.discovery/
+[mqtt.server docs]: https://home-assistant.io/components/mqtt.server/
+[mqtt_statestream docs]: https://home-assistant.io/components/mqtt_statestream/
+[neato docs]: https://home-assistant.io/components/neato/
+[no_ip docs]: https://home-assistant.io/components/no_ip/
+[notify.apns docs]: https://home-assistant.io/components/notify.apns/
+[notify.free_mobile docs]: https://home-assistant.io/components/notify.free_mobile/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.lametric docs]: https://home-assistant.io/components/notify.lametric/
+[notify.simplepush docs]: https://home-assistant.io/components/notify.simplepush/
+[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[remote docs]: https://home-assistant.io/components/remote/
+[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
+[ring docs]: https://home-assistant.io/components/ring/
+[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
+[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
+[sensor.haveibeenpwned docs]: https://home-assistant.io/components/sensor.haveibeenpwned/
+[sensor.lacrosse docs]: https://home-assistant.io/components/sensor.lacrosse/
+[sensor.london_air docs]: https://home-assistant.io/components/sensor.london_air/
+[sensor.modbus docs]: https://home-assistant.io/components/sensor.modbus/
+[sensor.neato docs]: https://home-assistant.io/components/sensor.neato/
+[sensor.nederlandse_spoorwegen docs]: https://home-assistant.io/components/sensor.nederlandse_spoorwegen/
+[sensor.pyload docs]: https://home-assistant.io/components/sensor.pyload/
+[sensor.serial docs]: https://home-assistant.io/components/sensor.serial/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tibber docs]: https://home-assistant.io/components/sensor.tibber/
+[sensor.viaggiatreno docs]: https://home-assistant.io/components/sensor.viaggiatreno/
+[sensor.vultr docs]: https://home-assistant.io/components/sensor.vultr/
+[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
+[sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/
+[sensor.zamg docs]: https://home-assistant.io/components/sensor.zamg/
+[spc docs]: https://home-assistant.io/components/spc/
+[switch.broadlink docs]: https://home-assistant.io/components/switch.broadlink/
+[switch.hikvisioncam docs]: https://home-assistant.io/components/switch.hikvisioncam/
+[switch.modbus docs]: https://home-assistant.io/components/switch.modbus/
+[switch.neato docs]: https://home-assistant.io/components/switch.neato/
+[switch.snmp docs]: https://home-assistant.io/components/switch.snmp/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[system_log docs]: https://home-assistant.io/components/system_log/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[tts docs]: https://home-assistant.io/components/tts/
+[tts.google docs]: https://home-assistant.io/components/tts.google/
+[tts.yandextts docs]: https://home-assistant.io/components/tts.yandextts/
+[vacuum.neato docs]: https://home-assistant.io/components/vacuum.neato/
+[verisure docs]: https://home-assistant.io/components/verisure/
+[volvooncall docs]: https://home-assistant.io/components/volvooncall/
+[vultr docs]: https://home-assistant.io/components/vultr/
+[weather docs]: https://home-assistant.io/components/weather/
+[weather.demo docs]: https://home-assistant.io/components/weather.demo/
+[websocket_api docs]: https://home-assistant.io/components/websocket_api/
+[zwave docs]: https://home-assistant.io/components/zwave/
[#10661]: https://github.com/home-assistant/home-assistant/pull/10661
[#10665]: https://github.com/home-assistant/home-assistant/pull/10665
[#10682]: https://github.com/home-assistant/home-assistant/pull/10682
@@ -497,7 +497,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@etsinko]: https://github.com/etsinko
[@tinloaf]: https://github.com/tinloaf
[@titilambert]: https://github.com/titilambert
-[remote.harmony docs]: /components/remote.harmony/
-[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
-[sensor.time_date docs]: /components/sensor.time_date/
-[weather.yweather docs]: /components/weather.yweather/
+[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
+[sensor.hydroquebec docs]: https://home-assistant.io/components/sensor.hydroquebec/
+[sensor.time_date docs]: https://home-assistant.io/components/sensor.time_date/
+[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
diff --git a/source/_posts/2017-12-03-release-59.markdown b/source/_posts/2017-12-03-release-59.markdown
index bfadb2646a..b68a0dede9 100644
--- a/source/_posts/2017-12-03-release-59.markdown
+++ b/source/_posts/2017-12-03-release-59.markdown
@@ -324,94 +324,94 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@wardcraigj]: https://github.com/wardcraigj
[@zBart]: https://github.com/zBart
[@zhujisheng]: https://github.com/zhujisheng
-[alarm_control_panel docs]: /components/alarm_control_panel/
-[alarm_control_panel.arlo docs]: /components/alarm_control_panel.arlo/
-[alarm_control_panel.demo docs]: /components/alarm_control_panel.demo/
-[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
-[amcrest docs]: /components/amcrest/
-[automation.state docs]: /docs/automation/trigger/#state-trigger
-[binary_sensor docs]: /components/binary_sensor/
-[binary_sensor.homematic docs]: /components/binary_sensor.homematic/
-[camera.amcrest docs]: /components/camera.amcrest/
-[camera.ring docs]: /components/camera.ring/
-[climate docs]: /components/climate/
-[climate.ecobee docs]: /components/climate.ecobee/
-[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
-[climate.hive docs]: /components/climate.hive/
-[climate.honeywell docs]: /components/climate.honeywell/
-[climate.mqtt docs]: /components/climate.mqtt/
-[climate.radiotherm docs]: /components/climate.radiotherm/
-[climate.sensibo docs]: /components/climate.sensibo/
-[cloud docs]: /components/cloud/
-[cloud.auth_api docs]: /components/cloud.auth_api/
-[cloud.iot docs]: /components/cloud.iot/
-[config.group docs]: /components/config.group/
-[configurator docs]: /components/configurator/
-[conversation docs]: /components/conversation/
-[cover.tahoma docs]: /components/cover.tahoma/
-[device_tracker.unifi_direct docs]: /components/device_tracker.unifi_direct/
-[dominos docs]: /components/dominos/
-[doorbird docs]: /components/doorbird/
-[ecobee docs]: /components/ecobee/
-[emulated_hue docs]: /components/emulated_hue/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[google_assistant.http docs]: /components/google_assistant.http/
-[google_assistant.smart_home docs]: /components/google_assistant.smart_home/
-[hive docs]: /components/hive/
-[homematic docs]: /components/homematic/
-[influxdb docs]: /components/influxdb/
-[knx docs]: /components/knx/
-[light.blinkt docs]: /components/light.blinkt/
-[light.hive docs]: /components/light.hive/
-[light.hue docs]: /components/light.hue/
-[light.tradfri docs]: /components/light.tradfri/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[light.yeelight docs]: /components/light.yeelight/
-[media_extractor docs]: /components/media_extractor/
-[media_player.cast docs]: /components/media_player.cast/
-[netatmo docs]: /components/netatmo/
-[notify.lametric docs]: /components/notify.lametric/
-[notify.pushbullet docs]: /components/notify.pushbullet/
-[ring docs]: /components/ring/
-[sensor.amcrest docs]: /components/sensor.amcrest/
-[sensor.currencylayer docs]: /components/sensor.currencylayer/
-[sensor.deutsche_bahn docs]: /components/sensor.deutsche_bahn/
-[sensor.fastdotcom docs]: /components/sensor.fastdotcom/
-[sensor.fritzbox_netmonitor docs]: /components/sensor.fritzbox_netmonitor/
-[sensor.hddtemp docs]: /components/sensor.hddtemp/
-[sensor.hive docs]: /components/sensor.hive/
-[sensor.homematic docs]: /components/sensor.homematic/
-[sensor.sabnzbd docs]: /components/sensor.sabnzbd/
-[sensor.serial docs]: /components/sensor.serial/
-[sensor.tahoma docs]: /components/sensor.tahoma/
-[sensor.tellduslive docs]: /components/sensor.tellduslive/
-[sensor.tellstick docs]: /components/sensor.tellstick/
-[sensor.whois docs]: /components/sensor.whois/
-[sensor.wunderground docs]: /components/sensor.wunderground/
-[sensor.yweather docs]: /components/sensor.yweather/
-[shell_command docs]: /components/shell_command/
-[shopping_list docs]: /components/shopping_list/
-[switch.hive docs]: /components/switch.hive/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[system_log docs]: /components/system_log/
-[tahoma docs]: /components/tahoma/
-[tellduslive docs]: /components/tellduslive/
-[tellstick docs]: /components/tellstick/
-[tradfri docs]: /components/tradfri/
-[tts docs]: /components/tts/
-[tts.baidu docs]: /components/tts.baidu/
-[tts.microsoft docs]: /components/tts.microsoft/
-[updater docs]: /components/updater/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[weather.ecobee docs]: /components/weather.ecobee/
-[zwave docs]: /components/zwave/
+[alarm_control_panel docs]: https://home-assistant.io/components/alarm_control_panel/
+[alarm_control_panel.arlo docs]: https://home-assistant.io/components/alarm_control_panel.arlo/
+[alarm_control_panel.demo docs]: https://home-assistant.io/components/alarm_control_panel.demo/
+[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/
+[amcrest docs]: https://home-assistant.io/components/amcrest/
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.homematic docs]: https://home-assistant.io/components/binary_sensor.homematic/
+[camera.amcrest docs]: https://home-assistant.io/components/camera.amcrest/
+[camera.ring docs]: https://home-assistant.io/components/camera.ring/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.ecobee docs]: https://home-assistant.io/components/climate.ecobee/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.hive docs]: https://home-assistant.io/components/climate.hive/
+[climate.honeywell docs]: https://home-assistant.io/components/climate.honeywell/
+[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
+[climate.radiotherm docs]: https://home-assistant.io/components/climate.radiotherm/
+[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.auth_api docs]: https://home-assistant.io/components/cloud.auth_api/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[config.group docs]: https://home-assistant.io/components/config.group/
+[configurator docs]: https://home-assistant.io/components/configurator/
+[conversation docs]: https://home-assistant.io/components/conversation/
+[cover.tahoma docs]: https://home-assistant.io/components/cover.tahoma/
+[device_tracker.unifi_direct docs]: https://home-assistant.io/components/device_tracker.unifi_direct/
+[dominos docs]: https://home-assistant.io/components/dominos/
+[doorbird docs]: https://home-assistant.io/components/doorbird/
+[ecobee docs]: https://home-assistant.io/components/ecobee/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[fan.xiaomi_miio docs]: https://home-assistant.io/components/fan.xiaomi_miio/
+[google_assistant.http docs]: https://home-assistant.io/components/google_assistant.http/
+[google_assistant.smart_home docs]: https://home-assistant.io/components/google_assistant.smart_home/
+[hive docs]: https://home-assistant.io/components/hive/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[influxdb docs]: https://home-assistant.io/components/influxdb/
+[knx docs]: https://home-assistant.io/components/knx/
+[light.blinkt docs]: https://home-assistant.io/components/light.blinkt/
+[light.hive docs]: https://home-assistant.io/components/light.hive/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[netatmo docs]: https://home-assistant.io/components/netatmo/
+[notify.lametric docs]: https://home-assistant.io/components/notify.lametric/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[ring docs]: https://home-assistant.io/components/ring/
+[sensor.amcrest docs]: https://home-assistant.io/components/sensor.amcrest/
+[sensor.currencylayer docs]: https://home-assistant.io/components/sensor.currencylayer/
+[sensor.deutsche_bahn docs]: https://home-assistant.io/components/sensor.deutsche_bahn/
+[sensor.fastdotcom docs]: https://home-assistant.io/components/sensor.fastdotcom/
+[sensor.fritzbox_netmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
+[sensor.hddtemp docs]: https://home-assistant.io/components/sensor.hddtemp/
+[sensor.hive docs]: https://home-assistant.io/components/sensor.hive/
+[sensor.homematic docs]: https://home-assistant.io/components/sensor.homematic/
+[sensor.sabnzbd docs]: https://home-assistant.io/components/sensor.sabnzbd/
+[sensor.serial docs]: https://home-assistant.io/components/sensor.serial/
+[sensor.tahoma docs]: https://home-assistant.io/components/sensor.tahoma/
+[sensor.tellduslive docs]: https://home-assistant.io/components/sensor.tellduslive/
+[sensor.tellstick docs]: https://home-assistant.io/components/sensor.tellstick/
+[sensor.whois docs]: https://home-assistant.io/components/sensor.whois/
+[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
+[sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/
+[shell_command docs]: https://home-assistant.io/components/shell_command/
+[shopping_list docs]: https://home-assistant.io/components/shopping_list/
+[switch.hive docs]: https://home-assistant.io/components/switch.hive/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[system_log docs]: https://home-assistant.io/components/system_log/
+[tahoma docs]: https://home-assistant.io/components/tahoma/
+[tellduslive docs]: https://home-assistant.io/components/tellduslive/
+[tellstick docs]: https://home-assistant.io/components/tellstick/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[tts docs]: https://home-assistant.io/components/tts/
+[tts.baidu docs]: https://home-assistant.io/components/tts.baidu/
+[tts.microsoft docs]: https://home-assistant.io/components/tts.microsoft/
+[updater docs]: https://home-assistant.io/components/updater/
+[vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[weather.ecobee docs]: https://home-assistant.io/components/weather.ecobee/
+[zwave docs]: https://home-assistant.io/components/zwave/
[#10798]: https://github.com/home-assistant/home-assistant/pull/10798
[#10923]: https://github.com/home-assistant/home-assistant/pull/10923
[#10934]: https://github.com/home-assistant/home-assistant/pull/10934
[#10935]: https://github.com/home-assistant/home-assistant/pull/10935
[@NovapaX]: https://github.com/NovapaX
[@wrboyce]: https://github.com/wrboyce
-[notify.nfandroidtv docs]: /components/notify.nfandroidtv/
+[notify.nfandroidtv docs]: https://home-assistant.io/components/notify.nfandroidtv/
[#10941]: https://github.com/home-assistant/home-assistant/pull/10941
[#10947]: https://github.com/home-assistant/home-assistant/pull/10947
[#10950]: https://github.com/home-assistant/home-assistant/pull/10950
@@ -424,8 +424,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@molobrakos]: https://github.com/molobrakos
[@w1ll1am23]: https://github.com/w1ll1am23
[@wardcraigj]: https://github.com/wardcraigj
-[device_tracker.linksys_ap docs]: /components/device_tracker.linksys_ap/
-[dominos docs]: /components/dominos/
-[media_player.cast docs]: /components/media_player.cast/
-[tellduslive docs]: /components/tellduslive/
-[wink docs]: /components/wink/
+[device_tracker.linksys_ap docs]: https://home-assistant.io/components/device_tracker.linksys_ap/
+[dominos docs]: https://home-assistant.io/components/dominos/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[tellduslive docs]: https://home-assistant.io/components/tellduslive/
+[wink docs]: https://home-assistant.io/components/wink/
diff --git a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown
index d765165e5c..b55eabb3e3 100644
--- a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown
+++ b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown
@@ -48,11 +48,11 @@ See the [Cloud component configuration](/components/cloud/) to learn how to filt
## {% linkable_title FAQ %}
-_Last updated: February 22, 2018_
+_Last updated: December 26, 2017_
#### {% linkable_title I thought the Home Assistant crew didn't like the cloud? %}
-You are right, [we don't](/blog/2016/01/19/perfect-home-automation/#your-system-should-run-at-home-not-in-the-cloud)! The Home Assistant Cloud is not an alternative to running your local Home Assistant instance. All control and automations are still running locally.
+You are right, [we don't](https://home-assistant.io/blog/2016/01/19/perfect-home-automation/#your-system-should-run-at-home-not-in-the-cloud)! The Home Assistant Cloud is not an alternative to running your local Home Assistant instance. All control and automations are still running locally.
Instead, the Home Assistant Cloud is an extension of your local instance. It allows to communicate with companies that force us to communicate via a public available cloud endpoint like Amazon Alexa and Google Assistant.
@@ -85,7 +85,7 @@ We have a lot of ideas! We are not going to make any promises but here are some
#### {% linkable_title What countries are supported at launch? %}
-As of February 2018, we are live in all countries that have Alexa except for Japan (which is under certification).
+Only US is currently supported. The reason for this limitation is that we need to do extra steps and certifications for each country's Alexa skill. This is in progress but the timeline depends on Amazon.
#### {% linkable_title How is the connection made to the cloud? %}
diff --git a/source/_posts/2017-12-17-release-60.markdown b/source/_posts/2017-12-17-release-60.markdown
index 4cfabc3417..6f795df119 100644
--- a/source/_posts/2017-12-17-release-60.markdown
+++ b/source/_posts/2017-12-17-release-60.markdown
@@ -300,78 +300,78 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@tschmidty69]: https://github.com/tschmidty69
[@uchagani]: https://github.com/uchagani
[@ziotibia81]: https://github.com/ziotibia81
-[ads docs]: /components/ads/
-[alarm_control_panel.egardia docs]: /components/alarm_control_panel.egardia/
-[alarm_control_panel.ialarm docs]: /components/alarm_control_panel.ialarm/
-[alarm_control_panel.manual docs]: /components/alarm_control_panel.manual/
-[alarm_control_panel.manual_mqtt docs]: /components/alarm_control_panel.manual_mqtt/
-[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
-[alarmdecoder docs]: /components/alarmdecoder/
-[apple_tv docs]: /components/apple_tv/
-[binary_sensor docs]: /components/binary_sensor/
-[binary_sensor.ads docs]: /components/binary_sensor.ads/
-[binary_sensor.isy994 docs]: /components/binary_sensor.isy994/
-[calendar.caldav docs]: /components/calendar.caldav/
-[camera.canary docs]: /components/camera.canary/
-[canary docs]: /components/canary/
-[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
-[climate.tado docs]: /components/climate.tado/
-[cloud docs]: /components/cloud/
-[cloud.const docs]: /components/cloud.const/
-[config.automation docs]: /components/config.automation/
-[cover.tellstick docs]: /components/cover.tellstick/
-[device_tracker docs]: /components/device_tracker/
-[device_tracker.meraki docs]: /components/device_tracker.meraki/
-[ecobee docs]: /components/ecobee/
-[homematic docs]: /components/homematic/
-[hue docs]: /components/hue/
-[isy994 docs]: /components/isy994/
-[keyboard_remote docs]: /components/keyboard_remote/
-[light.ads docs]: /components/light.ads/
-[light.hue docs]: /components/light.hue/
-[light.lifx docs]: /components/light.lifx/
-[light.mochad docs]: /components/light.mochad/
-[light.tplink docs]: /components/light.tplink/
-[light.tradfri docs]: /components/light.tradfri/
-[logbook docs]: /components/logbook/
-[media_extractor docs]: /components/media_extractor/
-[media_player.denonavr docs]: /components/media_player.denonavr/
-[media_player.liveboxplaytv docs]: /components/media_player.liveboxplaytv/
-[media_player.samsungtv docs]: /components/media_player.samsungtv/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.ue_smart_radio docs]: /components/media_player.ue_smart_radio/
-[media_player.webostv docs]: /components/media_player.webostv/
-[media_player.yamaha_musiccast docs]: /components/media_player.yamaha_musiccast/
-[media_player.ziggo_mediabox_xl docs]: /components/media_player.ziggo_mediabox_xl/
-[mochad docs]: /components/mochad/
-[neato docs]: /components/neato/
-[notify.html5 docs]: /components/notify.html5/
-[prometheus docs]: /components/prometheus/
-[scene.vera docs]: /components/scene.vera/
-[sensor.ads docs]: /components/sensor.ads/
-[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
-[sensor.canary docs]: /components/sensor.canary/
-[sensor.efergy docs]: /components/sensor.efergy/
-[sensor.eliqonline docs]: /components/sensor.eliqonline/
-[sensor.gearbest docs]: /components/sensor.gearbest/
-[sensor.luftdaten docs]: /components/sensor.luftdaten/
-[sensor.miflora docs]: /components/sensor.miflora/
-[sensor.mqtt docs]: /components/sensor.mqtt/
-[sensor.octoprint docs]: /components/sensor.octoprint/
-[sensor.rest docs]: /components/sensor.rest/
-[sensor.ripple docs]: /components/sensor.ripple/
-[sensor.shodan docs]: /components/sensor.shodan/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.tesla docs]: /components/sensor.tesla/
-[sensor.volvooncall docs]: /components/sensor.volvooncall/
-[snips docs]: /components/snips/
-[switch.ads docs]: /components/switch.ads/
-[switch.mochad docs]: /components/switch.mochad/
-[switch.tplink docs]: /components/switch.tplink/
-[tellstick docs]: /components/tellstick/
-[vera docs]: /components/vera/
-[volvooncall docs]: /components/volvooncall/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
+[ads docs]: https://home-assistant.io/components/ads/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alarm_control_panel.ialarm docs]: https://home-assistant.io/components/alarm_control_panel.ialarm/
+[alarm_control_panel.manual docs]: https://home-assistant.io/components/alarm_control_panel.manual/
+[alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/
+[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/
+[alarmdecoder docs]: https://home-assistant.io/components/alarmdecoder/
+[apple_tv docs]: https://home-assistant.io/components/apple_tv/
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.ads docs]: https://home-assistant.io/components/binary_sensor.ads/
+[binary_sensor.isy994 docs]: https://home-assistant.io/components/binary_sensor.isy994/
+[calendar.caldav docs]: https://home-assistant.io/components/calendar.caldav/
+[camera.canary docs]: https://home-assistant.io/components/camera.canary/
+[canary docs]: https://home-assistant.io/components/canary/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.tado docs]: https://home-assistant.io/components/climate.tado/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.const docs]: https://home-assistant.io/components/cloud.const/
+[config.automation docs]: https://home-assistant.io/components/config.automation/
+[cover.tellstick docs]: https://home-assistant.io/components/cover.tellstick/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.meraki docs]: https://home-assistant.io/components/device_tracker.meraki/
+[ecobee docs]: https://home-assistant.io/components/ecobee/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[hue docs]: https://home-assistant.io/components/hue/
+[isy994 docs]: https://home-assistant.io/components/isy994/
+[keyboard_remote docs]: https://home-assistant.io/components/keyboard_remote/
+[light.ads docs]: https://home-assistant.io/components/light.ads/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.mochad docs]: https://home-assistant.io/components/light.mochad/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[logbook docs]: https://home-assistant.io/components/logbook/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
+[media_player.liveboxplaytv docs]: https://home-assistant.io/components/media_player.liveboxplaytv/
+[media_player.samsungtv docs]: https://home-assistant.io/components/media_player.samsungtv/
+[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
+[media_player.ue_smart_radio docs]: https://home-assistant.io/components/media_player.ue_smart_radio/
+[media_player.webostv docs]: https://home-assistant.io/components/media_player.webostv/
+[media_player.yamaha_musiccast docs]: https://home-assistant.io/components/media_player.yamaha_musiccast/
+[media_player.ziggo_mediabox_xl docs]: https://home-assistant.io/components/media_player.ziggo_mediabox_xl/
+[mochad docs]: https://home-assistant.io/components/mochad/
+[neato docs]: https://home-assistant.io/components/neato/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[prometheus docs]: https://home-assistant.io/components/prometheus/
+[scene.vera docs]: https://home-assistant.io/components/scene.vera/
+[sensor.ads docs]: https://home-assistant.io/components/sensor.ads/
+[sensor.alpha_vantage docs]: https://home-assistant.io/components/sensor.alpha_vantage/
+[sensor.canary docs]: https://home-assistant.io/components/sensor.canary/
+[sensor.efergy docs]: https://home-assistant.io/components/sensor.efergy/
+[sensor.eliqonline docs]: https://home-assistant.io/components/sensor.eliqonline/
+[sensor.gearbest docs]: https://home-assistant.io/components/sensor.gearbest/
+[sensor.luftdaten docs]: https://home-assistant.io/components/sensor.luftdaten/
+[sensor.miflora docs]: https://home-assistant.io/components/sensor.miflora/
+[sensor.mqtt docs]: https://home-assistant.io/components/sensor.mqtt/
+[sensor.octoprint docs]: https://home-assistant.io/components/sensor.octoprint/
+[sensor.rest docs]: https://home-assistant.io/components/sensor.rest/
+[sensor.ripple docs]: https://home-assistant.io/components/sensor.ripple/
+[sensor.shodan docs]: https://home-assistant.io/components/sensor.shodan/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tesla docs]: https://home-assistant.io/components/sensor.tesla/
+[sensor.volvooncall docs]: https://home-assistant.io/components/sensor.volvooncall/
+[snips docs]: https://home-assistant.io/components/snips/
+[switch.ads docs]: https://home-assistant.io/components/switch.ads/
+[switch.mochad docs]: https://home-assistant.io/components/switch.mochad/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[tellstick docs]: https://home-assistant.io/components/tellstick/
+[vera docs]: https://home-assistant.io/components/vera/
+[volvooncall docs]: https://home-assistant.io/components/volvooncall/
+[xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/
[#11054]: https://github.com/home-assistant/home-assistant/pull/11054
[#11185]: https://github.com/home-assistant/home-assistant/pull/11185
[#11214]: https://github.com/home-assistant/home-assistant/pull/11214
@@ -397,12 +397,12 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@rwa]: https://github.com/rwa
[@veleek]: https://github.com/veleek
[@ziotibia81]: https://github.com/ziotibia81
-[alexa.smart_home docs]: /components/alexa.smart_home/
-[binary_sensor.concord232 docs]: /components/binary_sensor.concord232/
-[binary_sensor.isy994 docs]: /components/binary_sensor.isy994/
-[calendar.caldav docs]: /components/calendar.caldav/
-[homematic docs]: /components/homematic/
-[light.hue docs]: /components/light.hue/
-[lock.sesame docs]: /components/lock.sesame/
-[media_player.webostv docs]: /components/media_player.webostv/
-[switch.modbus docs]: /components/switch.modbus/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
+[binary_sensor.concord232 docs]: https://home-assistant.io/components/binary_sensor.concord232/
+[binary_sensor.isy994 docs]: https://home-assistant.io/components/binary_sensor.isy994/
+[calendar.caldav docs]: https://home-assistant.io/components/calendar.caldav/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[lock.sesame docs]: https://home-assistant.io/components/lock.sesame/
+[media_player.webostv docs]: https://home-assistant.io/components/media_player.webostv/
+[switch.modbus docs]: https://home-assistant.io/components/switch.modbus/
diff --git a/source/_posts/2017-12-28-thank-you.markdown b/source/_posts/2017-12-28-thank-you.markdown
index d1cefceb59..f5632f7d6f 100644
--- a/source/_posts/2017-12-28-thank-you.markdown
+++ b/source/_posts/2017-12-28-thank-you.markdown
@@ -13,7 +13,7 @@ og_image:
2017 is almost over and this means it's time to do a little recap of our 2017. This was a great year for Home Assistant. Again, we were able to stick to our bi-weekly release cycle. There were 25 releases over the year and each release included the work of around 60 contributors.
-We got 10.000 stars on [GitHub], reached 10.000 commits in the main repo (over 4300 were made in 2017), got a [Thomas-Krenn award], participated in [Hacktoberfest], we have now almost 1000 integrations (the exact number is 938), we [moved to Discord] and we are up to over 2 million pageviews per month on our forum. Beside that we announced the [Home Assistant cloud] and have regular [Home Assistant Podcasts].
+We got 10.000 stars on [GitHub], reached 10.000 commits in the main repo (over 4300 were made in 2017), got a [Thomas-Krenn award], participated in [Hacktoberfest], we have now almost 1000 integrations (the exact number is 938), we [moved to Discord] and we are up to over 2 million pageviews per month on our forum. Beside that we announced the [Home Assistant cloud] and have regular [Home Assistant Podcasts].
We also do not want to forget to mention [Hass.io] and all the great Hass.io add-ons.
@@ -35,7 +35,7 @@ Stay tuned for more Home Assistant awesomeness in 2018. We will keep the pace bu
[forum]: https://community.home-assistant.io
[GitHub]: https://GitHub.com
[Hacktoberfest]: /blog/2017/11/04/release-57/#hacktoberfest
-[Hass.io]: /hassio/
+[Hass.io]: https://home-assistant.io/hassio/
[Home Assistant cloud]: /blog/2017/12/17/introducing-home-assistant-cloud/
[Home Assistant Podcasts]: https://hasspodcast.io/
[moved to Discord]: /blog/2017/07/03/home-assistant-is-moving-to-discord/
diff --git a/source/_posts/2018-01-14-release-61.markdown b/source/_posts/2018-01-14-release-61.markdown
index 1cc48aad14..f83e933ee7 100644
--- a/source/_posts/2018-01-14-release-61.markdown
+++ b/source/_posts/2018-01-14-release-61.markdown
@@ -106,7 +106,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
([@balloob] - [#11461]) ([cloud docs]) ([alexa.smart_home docs]) (breaking change)
- The extension of the `alpha_vantage` requires an update of the configuration as now are exchange data available as well. ([@ChristianKuehnel] - [#11427]) ([sensor.alpha_vantage docs]) (breaking change)
- The `prometheus` component now supports pushing all sensors and fixes wrong metrics. If may require that you update your configuration. ([@michaelkuty] - [#11159]) ([prometheus docs]) (breaking change)
-- Insteon local devices will now use their address as the `entity_id` and `name`. The friendly name can be customized using the [standard customization configuration](/docs/configuration/customizing-devices/). ([@camrun91] - [#11088]) ([insteon_local docs]) ([fan.insteon_local docs]) ([light.insteon_local docs]) ([switch.insteon_local docs]) (breaking change)
+- Insteon local devices will now use their address as the `entity_id` and `name`. The friendly name can be customized using the [standard customization configuration](https://home-assistant.io/docs/configuration/customizing-devices/). ([@camrun91] - [#11088]) ([insteon_local docs]) ([fan.insteon_local docs]) ([light.insteon_local docs]) ([switch.insteon_local docs]) (breaking change)
- Google Assistant is no longer configured via `customize` but instead has its configuration under the `google_assistant` entry in your `configuration.yaml`. The attributes will no longer have to be prefixed with `google_assistant_` either.
| Old option | New option |
@@ -612,168 +612,168 @@ Note however, that this feature was replaced by a new ignore_string config optio
[@veleek]: https://github.com/veleek
[@w1ll1am23]: https://github.com/w1ll1am23
[@yienxu]: https://github.com/yienxu
-[__init__ docs]: /components/__init__/
-[alarm_control_panel.alarmdecoder docs]: /components/alarm_control_panel.alarmdecoder/
-[alarm_control_panel.concord232 docs]: /components/alarm_control_panel.concord232/
-[alarm_control_panel.egardia docs]: /components/alarm_control_panel.egardia/
-[alarmdecoder docs]: /components/alarmdecoder/
-[alexa.intent docs]: /components/alexa.intent/
-[alexa.smart_home docs]: /components/alexa.smart_home/
-[api docs]: /components/api/
-[automation.state docs]: /docs/automation/trigger/#state-trigger
-[binary_sensor docs]: /components/binary_sensor/
-[binary_sensor.alarmdecoder docs]: /components/binary_sensor.alarmdecoder/
-[binary_sensor.concord232 docs]: /components/binary_sensor.concord232/
-[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
-[binary_sensor.isy994 docs]: /components/binary_sensor.isy994/
-[binary_sensor.knx docs]: /components/binary_sensor.knx/
-[binary_sensor.rest docs]: /components/binary_sensor.rest/
-[binary_sensor.template docs]: /components/binary_sensor.template/
-[binary_sensor.threshold docs]: /components/binary_sensor.threshold/
-[binary_sensor.trend docs]: /components/binary_sensor.trend/
-[binary_sensor.workday docs]: /components/binary_sensor.workday/
-[camera.doorbird docs]: /components/camera.doorbird/
-[camera.uvc docs]: /components/camera.uvc/
-[climate docs]: /components/climate/
-[climate.daikin docs]: /components/climate.daikin/
-[climate.demo docs]: /components/climate.demo/
-[climate.econet docs]: /components/climate.econet/
-[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
-[climate.hive docs]: /components/climate.hive/
-[climate.homematic docs]: /components/climate.homematic/
-[climate.knx docs]: /components/climate.knx/
-[climate.netatmo docs]: /components/climate.netatmo/
-[climate.sensibo docs]: /components/climate.sensibo/
-[climate.tado docs]: /components/climate.tado/
-[climate.touchline docs]: /components/climate.touchline/
-[cloud docs]: /components/cloud/
-[cloud.auth_api docs]: /components/cloud.auth_api/
-[cloud.http_api docs]: /components/cloud.http_api/
-[cloud.iot docs]: /components/cloud.iot/
-[coinbase docs]: /components/coinbase/
-[conversation docs]: /components/conversation/
-[cover.isy994 docs]: /components/cover.isy994/
-[cover.knx docs]: /components/cover.knx/
-[cover.tahoma docs]: /components/cover.tahoma/
-[cover.template docs]: /components/cover.template/
-[cover.xiaomi_aqara docs]: /components/cover.xiaomi_aqara/
-[deconz docs]: /components/deconz/
-[device_tracker docs]: /components/device_tracker/
-[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/
-[device_tracker.bluetooth_le_tracker docs]: /components/device_tracker.bluetooth_le_tracker/
-[device_tracker.bluetooth_tracker docs]: /components/device_tracker.bluetooth_tracker/
-[device_tracker.gpslogger docs]: /components/device_tracker.gpslogger/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.ping docs]: /components/device_tracker.ping/
-[device_tracker.snmp docs]: /components/device_tracker.snmp/
-[device_tracker.tile docs]: /components/device_tracker.tile/
-[digital_ocean docs]: /components/digital_ocean/
-[fan.insteon_local docs]: /components/fan.insteon_local/
-[fan.isy994 docs]: /components/fan.isy994/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[google_assistant docs]: /components/google_assistant/
-[google_assistant.http docs]: /components/google_assistant.http/
-[google_assistant.smart_home docs]: /components/google_assistant.smart_home/
-[group docs]: /components/group/
-[hassio docs]: /components/hassio/
-[history docs]: /components/history/
-[hive docs]: /components/hive/
-[homematic docs]: /components/homematic/
-[http docs]: /components/http/
-[image_processing.opencv docs]: /components/image_processing.opencv/
-[input_boolean docs]: /components/input_boolean/
-[input_select docs]: /components/input_select/
-[insteon_local docs]: /components/insteon_local/
-[isy994 docs]: /components/isy994/
-[knx docs]: /components/knx/
-[light.deconz docs]: /components/light.deconz/
-[light.greenwave docs]: /components/light.greenwave/
-[light.hive docs]: /components/light.hive/
-[light.hue docs]: /components/light.hue/
-[light.iglo docs]: /components/light.iglo/
-[light.insteon_local docs]: /components/light.insteon_local/
-[light.isy994 docs]: /components/light.isy994/
-[light.knx docs]: /components/light.knx/
-[light.lifx docs]: /components/light.lifx/
-[light.mqtt docs]: /components/light.mqtt/
-[light.osramlightify docs]: /components/light.osramlightify/
-[light.template docs]: /components/light.template/
-[light.tplink docs]: /components/light.tplink/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[light.zha docs]: /components/light.zha/
-[lock.isy994 docs]: /components/lock.isy994/
-[media_extractor docs]: /components/media_extractor/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.kodi docs]: /components/media_player.kodi/
-[media_player.monoprice docs]: /components/media_player.monoprice/
-[media_player.plex docs]: /components/media_player.plex/
-[media_player.squeezebox docs]: /components/media_player.squeezebox/
-[media_player.yamaha docs]: /components/media_player.yamaha/
-[modbus docs]: /components/modbus/
-[notify.html5 docs]: /components/notify.html5/
-[notify.pushbullet docs]: /components/notify.pushbullet/
-[notify.webostv docs]: /components/notify.webostv/
-[octoprint docs]: /components/octoprint/
-[prometheus docs]: /components/prometheus/
-[python_script docs]: /components/python_script/
-[rainbird docs]: /components/rainbird/
-[remember_the_milk docs]: /components/remember_the_milk/
-[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
-[sensor.bitcoin docs]: /components/sensor.bitcoin/
-[sensor.coinbase docs]: /components/sensor.coinbase/
-[sensor.deconz docs]: /components/sensor.deconz/
-[sensor.deutsche_bahn docs]: /components/sensor.deutsche_bahn/
-[sensor.discogs docs]: /components/sensor.discogs/
-[sensor.etherscan docs]: /components/sensor.etherscan/
-[sensor.fido docs]: /components/sensor.fido/
-[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
-[sensor.imap_email_content docs]: /components/sensor.imap_email_content/
-[sensor.irish_rail_transport docs]: /components/sensor.irish_rail_transport/
-[sensor.isy994 docs]: /components/sensor.isy994/
-[sensor.knx docs]: /components/sensor.knx/
-[sensor.luftdaten docs]: /components/sensor.luftdaten/
-[sensor.metoffice docs]: /components/sensor.metoffice/
-[sensor.miflora docs]: /components/sensor.miflora/
-[sensor.mqtt docs]: /components/sensor.mqtt/
-[sensor.openweathermap docs]: /components/sensor.openweathermap/
-[sensor.plex docs]: /components/sensor.plex/
-[sensor.rainbird docs]: /components/sensor.rainbird/
-[sensor.snmp docs]: /components/sensor.snmp/
-[sensor.sochain docs]: /components/sensor.sochain/
-[sensor.statistics docs]: /components/sensor.statistics/
-[sensor.steam_online docs]: /components/sensor.steam_online/
-[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.tado docs]: /components/sensor.tado/
-[sensor.template docs]: /components/sensor.template/
-[sensor.transmission docs]: /components/sensor.transmission/
-[sensor.xbox_live docs]: /components/sensor.xbox_live/
-[sensor.zoneminder docs]: /components/sensor.zoneminder/
-[snips docs]: /components/snips/
-[switch.insteon_local docs]: /components/switch.insteon_local/
-[switch.isy994 docs]: /components/switch.isy994/
-[switch.knx docs]: /components/switch.knx/
-[switch.mochad docs]: /components/switch.mochad/
-[switch.rainbird docs]: /components/switch.rainbird/
-[switch.rpi_rf docs]: /components/switch.rpi_rf/
-[switch.snmp docs]: /components/switch.snmp/
-[switch.template docs]: /components/switch.template/
-[switch.tplink docs]: /components/switch.tplink/
-[switch.transmission docs]: /components/switch.transmission/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[tahoma docs]: /components/tahoma/
-[telegram_bot docs]: /components/telegram_bot/
-[timer docs]: /components/timer/
-[tts.baidu docs]: /components/tts.baidu/
-[tts.marytts docs]: /components/tts.marytts/
-[updater docs]: /components/updater/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[weather.darksky docs]: /components/weather.darksky/
-[weather.openweathermap docs]: /components/weather.openweathermap/
-[weather.yweather docs]: /components/weather.yweather/
-[websocket_api docs]: /components/websocket_api/
-[wemo docs]: /components/wemo/
-[zigbee docs]: /components/zigbee/
+[__init__ docs]: https://home-assistant.io/components/__init__/
+[alarm_control_panel.alarmdecoder docs]: https://home-assistant.io/components/alarm_control_panel.alarmdecoder/
+[alarm_control_panel.concord232 docs]: https://home-assistant.io/components/alarm_control_panel.concord232/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alarmdecoder docs]: https://home-assistant.io/components/alarmdecoder/
+[alexa.intent docs]: https://home-assistant.io/components/alexa.intent/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
+[api docs]: https://home-assistant.io/components/api/
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.alarmdecoder docs]: https://home-assistant.io/components/binary_sensor.alarmdecoder/
+[binary_sensor.concord232 docs]: https://home-assistant.io/components/binary_sensor.concord232/
+[binary_sensor.deconz docs]: https://home-assistant.io/components/binary_sensor.deconz/
+[binary_sensor.isy994 docs]: https://home-assistant.io/components/binary_sensor.isy994/
+[binary_sensor.knx docs]: https://home-assistant.io/components/binary_sensor.knx/
+[binary_sensor.rest docs]: https://home-assistant.io/components/binary_sensor.rest/
+[binary_sensor.template docs]: https://home-assistant.io/components/binary_sensor.template/
+[binary_sensor.threshold docs]: https://home-assistant.io/components/binary_sensor.threshold/
+[binary_sensor.trend docs]: https://home-assistant.io/components/binary_sensor.trend/
+[binary_sensor.workday docs]: https://home-assistant.io/components/binary_sensor.workday/
+[camera.doorbird docs]: https://home-assistant.io/components/camera.doorbird/
+[camera.uvc docs]: https://home-assistant.io/components/camera.uvc/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.daikin docs]: https://home-assistant.io/components/climate.daikin/
+[climate.demo docs]: https://home-assistant.io/components/climate.demo/
+[climate.econet docs]: https://home-assistant.io/components/climate.econet/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.hive docs]: https://home-assistant.io/components/climate.hive/
+[climate.homematic docs]: https://home-assistant.io/components/climate.homematic/
+[climate.knx docs]: https://home-assistant.io/components/climate.knx/
+[climate.netatmo docs]: https://home-assistant.io/components/climate.netatmo/
+[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/
+[climate.tado docs]: https://home-assistant.io/components/climate.tado/
+[climate.touchline docs]: https://home-assistant.io/components/climate.touchline/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.auth_api docs]: https://home-assistant.io/components/cloud.auth_api/
+[cloud.http_api docs]: https://home-assistant.io/components/cloud.http_api/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[coinbase docs]: https://home-assistant.io/components/coinbase/
+[conversation docs]: https://home-assistant.io/components/conversation/
+[cover.isy994 docs]: https://home-assistant.io/components/cover.isy994/
+[cover.knx docs]: https://home-assistant.io/components/cover.knx/
+[cover.tahoma docs]: https://home-assistant.io/components/cover.tahoma/
+[cover.template docs]: https://home-assistant.io/components/cover.template/
+[cover.xiaomi_aqara docs]: https://home-assistant.io/components/cover.xiaomi_aqara/
+[deconz docs]: https://home-assistant.io/components/deconz/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/
+[device_tracker.bluetooth_le_tracker docs]: https://home-assistant.io/components/device_tracker.bluetooth_le_tracker/
+[device_tracker.bluetooth_tracker docs]: https://home-assistant.io/components/device_tracker.bluetooth_tracker/
+[device_tracker.gpslogger docs]: https://home-assistant.io/components/device_tracker.gpslogger/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.ping docs]: https://home-assistant.io/components/device_tracker.ping/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[device_tracker.tile docs]: https://home-assistant.io/components/device_tracker.tile/
+[digital_ocean docs]: https://home-assistant.io/components/digital_ocean/
+[fan.insteon_local docs]: https://home-assistant.io/components/fan.insteon_local/
+[fan.isy994 docs]: https://home-assistant.io/components/fan.isy994/
+[fan.xiaomi_miio docs]: https://home-assistant.io/components/fan.xiaomi_miio/
+[google_assistant docs]: https://home-assistant.io/components/google_assistant/
+[google_assistant.http docs]: https://home-assistant.io/components/google_assistant.http/
+[google_assistant.smart_home docs]: https://home-assistant.io/components/google_assistant.smart_home/
+[group docs]: https://home-assistant.io/components/group/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[history docs]: https://home-assistant.io/components/history/
+[hive docs]: https://home-assistant.io/components/hive/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[http docs]: https://home-assistant.io/components/http/
+[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
+[input_boolean docs]: https://home-assistant.io/components/input_boolean/
+[input_select docs]: https://home-assistant.io/components/input_select/
+[insteon_local docs]: https://home-assistant.io/components/insteon_local/
+[isy994 docs]: https://home-assistant.io/components/isy994/
+[knx docs]: https://home-assistant.io/components/knx/
+[light.deconz docs]: https://home-assistant.io/components/light.deconz/
+[light.greenwave docs]: https://home-assistant.io/components/light.greenwave/
+[light.hive docs]: https://home-assistant.io/components/light.hive/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.iglo docs]: https://home-assistant.io/components/light.iglo/
+[light.insteon_local docs]: https://home-assistant.io/components/light.insteon_local/
+[light.isy994 docs]: https://home-assistant.io/components/light.isy994/
+[light.knx docs]: https://home-assistant.io/components/light.knx/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.mqtt docs]: https://home-assistant.io/components/light.mqtt/
+[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
+[light.template docs]: https://home-assistant.io/components/light.template/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[light.zha docs]: https://home-assistant.io/components/light.zha/
+[lock.isy994 docs]: https://home-assistant.io/components/lock.isy994/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
+[media_player.monoprice docs]: https://home-assistant.io/components/media_player.monoprice/
+[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/
+[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/
+[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
+[modbus docs]: https://home-assistant.io/components/modbus/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[notify.webostv docs]: https://home-assistant.io/components/notify.webostv/
+[octoprint docs]: https://home-assistant.io/components/octoprint/
+[prometheus docs]: https://home-assistant.io/components/prometheus/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[rainbird docs]: https://home-assistant.io/components/rainbird/
+[remember_the_milk docs]: https://home-assistant.io/components/remember_the_milk/
+[sensor.alpha_vantage docs]: https://home-assistant.io/components/sensor.alpha_vantage/
+[sensor.bitcoin docs]: https://home-assistant.io/components/sensor.bitcoin/
+[sensor.coinbase docs]: https://home-assistant.io/components/sensor.coinbase/
+[sensor.deconz docs]: https://home-assistant.io/components/sensor.deconz/
+[sensor.deutsche_bahn docs]: https://home-assistant.io/components/sensor.deutsche_bahn/
+[sensor.discogs docs]: https://home-assistant.io/components/sensor.discogs/
+[sensor.etherscan docs]: https://home-assistant.io/components/sensor.etherscan/
+[sensor.fido docs]: https://home-assistant.io/components/sensor.fido/
+[sensor.hydroquebec docs]: https://home-assistant.io/components/sensor.hydroquebec/
+[sensor.imap_email_content docs]: https://home-assistant.io/components/sensor.imap_email_content/
+[sensor.irish_rail_transport docs]: https://home-assistant.io/components/sensor.irish_rail_transport/
+[sensor.isy994 docs]: https://home-assistant.io/components/sensor.isy994/
+[sensor.knx docs]: https://home-assistant.io/components/sensor.knx/
+[sensor.luftdaten docs]: https://home-assistant.io/components/sensor.luftdaten/
+[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/
+[sensor.miflora docs]: https://home-assistant.io/components/sensor.miflora/
+[sensor.mqtt docs]: https://home-assistant.io/components/sensor.mqtt/
+[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
+[sensor.plex docs]: https://home-assistant.io/components/sensor.plex/
+[sensor.rainbird docs]: https://home-assistant.io/components/sensor.rainbird/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.sochain docs]: https://home-assistant.io/components/sensor.sochain/
+[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
+[sensor.steam_online docs]: https://home-assistant.io/components/sensor.steam_online/
+[sensor.swiss_public_transport docs]: https://home-assistant.io/components/sensor.swiss_public_transport/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tado docs]: https://home-assistant.io/components/sensor.tado/
+[sensor.template docs]: https://home-assistant.io/components/sensor.template/
+[sensor.transmission docs]: https://home-assistant.io/components/sensor.transmission/
+[sensor.xbox_live docs]: https://home-assistant.io/components/sensor.xbox_live/
+[sensor.zoneminder docs]: https://home-assistant.io/components/sensor.zoneminder/
+[snips docs]: https://home-assistant.io/components/snips/
+[switch.insteon_local docs]: https://home-assistant.io/components/switch.insteon_local/
+[switch.isy994 docs]: https://home-assistant.io/components/switch.isy994/
+[switch.knx docs]: https://home-assistant.io/components/switch.knx/
+[switch.mochad docs]: https://home-assistant.io/components/switch.mochad/
+[switch.rainbird docs]: https://home-assistant.io/components/switch.rainbird/
+[switch.rpi_rf docs]: https://home-assistant.io/components/switch.rpi_rf/
+[switch.snmp docs]: https://home-assistant.io/components/switch.snmp/
+[switch.template docs]: https://home-assistant.io/components/switch.template/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[switch.transmission docs]: https://home-assistant.io/components/switch.transmission/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[tahoma docs]: https://home-assistant.io/components/tahoma/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[timer docs]: https://home-assistant.io/components/timer/
+[tts.baidu docs]: https://home-assistant.io/components/tts.baidu/
+[tts.marytts docs]: https://home-assistant.io/components/tts.marytts/
+[updater docs]: https://home-assistant.io/components/updater/
+[vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[weather.darksky docs]: https://home-assistant.io/components/weather.darksky/
+[weather.openweathermap docs]: https://home-assistant.io/components/weather.openweathermap/
+[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
+[websocket_api docs]: https://home-assistant.io/components/websocket_api/
+[wemo docs]: https://home-assistant.io/components/wemo/
+[zigbee docs]: https://home-assistant.io/components/zigbee/
[#11670]: https://github.com/home-assistant/home-assistant/pull/11670
[#11677]: https://github.com/home-assistant/home-assistant/pull/11677
[#11678]: https://github.com/home-assistant/home-assistant/pull/11678
@@ -784,14 +784,14 @@ Note however, that this feature was replaced by a new ignore_string config optio
[@rcloran]: https://github.com/rcloran
[@rwa]: https://github.com/rwa
[@tinloaf]: https://github.com/tinloaf
-[binary_sensor.rfxtrx docs]: /components/binary_sensor.rfxtrx/
-[calendar.todoist docs]: /components/calendar.todoist/
-[history docs]: /components/history/
-[light.zha docs]: /components/light.zha/
-[media_player.snapcast docs]: /components/media_player.snapcast/
-[media_player.soundtouch docs]: /components/media_player.soundtouch/
-[rfxtrx docs]: /components/rfxtrx/
-[sensor.mopar docs]: /components/sensor.mopar/
-[switch.broadlink docs]: /components/switch.broadlink/
-[switch.scsgate docs]: /components/switch.scsgate/
-[zha docs]: /components/zha/
+[binary_sensor.rfxtrx docs]: https://home-assistant.io/components/binary_sensor.rfxtrx/
+[calendar.todoist docs]: https://home-assistant.io/components/calendar.todoist/
+[history docs]: https://home-assistant.io/components/history/
+[light.zha docs]: https://home-assistant.io/components/light.zha/
+[media_player.snapcast docs]: https://home-assistant.io/components/media_player.snapcast/
+[media_player.soundtouch docs]: https://home-assistant.io/components/media_player.soundtouch/
+[rfxtrx docs]: https://home-assistant.io/components/rfxtrx/
+[sensor.mopar docs]: https://home-assistant.io/components/sensor.mopar/
+[switch.broadlink docs]: https://home-assistant.io/components/switch.broadlink/
+[switch.scsgate docs]: https://home-assistant.io/components/switch.scsgate/
+[zha docs]: https://home-assistant.io/components/zha/
diff --git a/source/_posts/2018-01-21-clarification-emulated-hue.markdown b/source/_posts/2018-01-21-clarification-emulated-hue.markdown
index b1b9138ae7..5284113bc5 100644
--- a/source/_posts/2018-01-21-clarification-emulated-hue.markdown
+++ b/source/_posts/2018-01-21-clarification-emulated-hue.markdown
@@ -31,4 +31,4 @@ More info:
[pr1]: https://github.com/home-assistant/home-assistant/pull/4708
[pr2]: https://github.com/home-assistant/home-assistant/pull/5549
-[eh-conf]: /components/emulated_hue/#configuration
+[eh-conf]: https://home-assistant.io/components/emulated_hue/#configuration
diff --git a/source/_posts/2018-01-27-release-62.markdown b/source/_posts/2018-01-27-release-62.markdown
index 1b72621881..8bb54a09f0 100644
--- a/source/_posts/2018-01-27-release-62.markdown
+++ b/source/_posts/2018-01-27-release-62.markdown
@@ -383,109 +383,109 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@ttroy50]: https://github.com/ttroy50
[@w1ll1am23]: https://github.com/w1ll1am23
[@zabuldon]: https://github.com/zabuldon
-[alarm_control_panel.mqtt docs]: /components/alarm_control_panel.mqtt/
-[alexa docs]: /components/alexa/
-[asterisk_mbox docs]: /components/asterisk_mbox/
-[axis docs]: /components/axis/
-[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
-[binary_sensor.hive docs]: /components/binary_sensor.hive/
-[binary_sensor.ihc docs]: /components/binary_sensor.ihc/
-[binary_sensor.maxcube docs]: /components/binary_sensor.maxcube/
-[binary_sensor.rfxtrx docs]: /components/binary_sensor.rfxtrx/
-[binary_sensor.wink docs]: /components/binary_sensor.wink/
-[binary_sensor.workday docs]: /components/binary_sensor.workday/
-[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
-[camera.foscam docs]: /components/camera.foscam/
-[camera.onvif docs]: /components/camera.onvif/
-[climate docs]: /components/climate/
-[climate.daikin docs]: /components/climate.daikin/
-[climate.econet docs]: /components/climate.econet/
-[climate.ephember docs]: /components/climate.ephember/
-[climate.eq3btsmart docs]: /components/climate.eq3btsmart/
-[climate.hive docs]: /components/climate.hive/
-[climate.nest docs]: /components/climate.nest/
-[climate.sensibo docs]: /components/climate.sensibo/
-[climate.wink docs]: /components/climate.wink/
-[cover.homematic docs]: /components/cover.homematic/
-[cover.lutron docs]: /components/cover.lutron/
-[cover.tahoma docs]: /components/cover.tahoma/
-[cover.wink docs]: /components/cover.wink/
-[cover.xiaomi_aqara docs]: /components/cover.xiaomi_aqara/
-[deconz docs]: /components/deconz/
-[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/
-[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
-[device_tracker.tomato docs]: /components/device_tracker.tomato/
-[device_tracker.unifi_direct docs]: /components/device_tracker.unifi_direct/
-[ecobee docs]: /components/ecobee/
-[emulated_hue docs]: /components/emulated_hue/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[google_assistant docs]: /components/google_assistant/
-[hassio docs]: /components/hassio/
-[hive docs]: /components/hive/
-[homematic docs]: /components/homematic/
-[hue docs]: /components/hue/
-[ihc docs]: /components/ihc/
-[ihc.const docs]: /components/ihc.const/
-[ihc.ihcdevice docs]: /components/ihc.ihcdevice/
-[iota docs]: /components/iota/
-[light.deconz docs]: /components/light.deconz/
-[light.decora docs]: /components/light.decora/
-[light.flux_led docs]: /components/light.flux_led/
-[light.greenwave docs]: /components/light.greenwave/
-[light.hive docs]: /components/light.hive/
-[light.hyperion docs]: /components/light.hyperion/
-[light.ihc docs]: /components/light.ihc/
-[light.tplink docs]: /components/light.tplink/
-[light.wemo docs]: /components/light.wemo/
-[light.xiaomi_aqara docs]: /components/light.xiaomi_aqara/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[lutron docs]: /components/lutron/
-[map docs]: /components/map/
-[media_player.samsungtv docs]: /components/media_player.samsungtv/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.yamaha docs]: /components/media_player.yamaha/
-[notify.clicksend docs]: /components/notify.clicksend/
-[notify.prowl docs]: /components/notify.prowl/
-[plant docs]: /components/plant/
-[rfxtrx docs]: /components/rfxtrx/
-[scene docs]: /components/scene/
-[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
-[sensor.linux_battery docs]: /components/sensor.linux_battery/
-[sensor.bme680 docs]: /components/sensor.bme680/
-[sensor.deconz docs]: /components/sensor.deconz/
-[sensor.etherscan docs]: /components/sensor.etherscan/
-[sensor.fixer docs]: /components/sensor.fixer/
-[sensor.hive docs]: /components/sensor.hive/
-[sensor.ihc docs]: /components/sensor.ihc/
-[sensor.iota docs]: /components/sensor.iota/
-[sensor.metoffice docs]: /components/sensor.metoffice/
-[sensor.miflora docs]: /components/sensor.miflora/
-[sensor.min_max docs]: /components/sensor.min_max/
-[sensor.mold_indicator docs]: /components/sensor.mold_indicator/
-[mychevy docs]: /components/mychevy/
-[sensor.openweathermap docs]: /components/sensor.openweathermap/
-[sensor.random docs]: /components/sensor.random/
-[sensor.teksavvy docs]: /components/sensor.teksavvy/
-[sensor.xbox_live docs]: /components/sensor.xbox_live/
-[sensor.xiaomi_aqara docs]: /components/sensor.xiaomi_aqara/
-[sensor.yr docs]: /components/sensor.yr/
-[snips docs]: /components/snips/
-[switch.fritzdect docs]: /components/switch.fritzdect/
-[switch.hive docs]: /components/switch.hive/
-[switch.ihc docs]: /components/switch.ihc/
-[switch.snmp docs]: /components/switch.snmp/
-[switch.tplink docs]: /components/switch.tplink/
-[switch.xiaomi_aqara docs]: /components/switch.xiaomi_aqara/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[system_log docs]: /components/system_log/
-[tahoma docs]: /components/tahoma/
-[tts.google docs]: /components/tts.google/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[waterfurnace docs]: /components/waterfurnace/
-[wemo docs]: /components/wemo/
-[wink docs]: /components/wink/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
-[zwave docs]: /components/zwave/
+[alarm_control_panel.mqtt docs]: https://home-assistant.io/components/alarm_control_panel.mqtt/
+[alexa docs]: https://home-assistant.io/components/alexa/
+[asterisk_mbox docs]: https://home-assistant.io/components/asterisk_mbox/
+[axis docs]: https://home-assistant.io/components/axis/
+[binary_sensor.deconz docs]: https://home-assistant.io/components/binary_sensor.deconz/
+[binary_sensor.hive docs]: https://home-assistant.io/components/binary_sensor.hive/
+[binary_sensor.ihc docs]: https://home-assistant.io/components/binary_sensor.ihc/
+[binary_sensor.maxcube docs]: https://home-assistant.io/components/binary_sensor.maxcube/
+[binary_sensor.rfxtrx docs]: https://home-assistant.io/components/binary_sensor.rfxtrx/
+[binary_sensor.wink docs]: https://home-assistant.io/components/binary_sensor.wink/
+[binary_sensor.workday docs]: https://home-assistant.io/components/binary_sensor.workday/
+[binary_sensor.xiaomi_aqara docs]: https://home-assistant.io/components/binary_sensor.xiaomi_aqara/
+[camera.foscam docs]: https://home-assistant.io/components/camera.foscam/
+[camera.onvif docs]: https://home-assistant.io/components/camera.onvif/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.daikin docs]: https://home-assistant.io/components/climate.daikin/
+[climate.econet docs]: https://home-assistant.io/components/climate.econet/
+[climate.ephember docs]: https://home-assistant.io/components/climate.ephember/
+[climate.eq3btsmart docs]: https://home-assistant.io/components/climate.eq3btsmart/
+[climate.hive docs]: https://home-assistant.io/components/climate.hive/
+[climate.nest docs]: https://home-assistant.io/components/climate.nest/
+[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/
+[climate.wink docs]: https://home-assistant.io/components/climate.wink/
+[cover.homematic docs]: https://home-assistant.io/components/cover.homematic/
+[cover.lutron docs]: https://home-assistant.io/components/cover.lutron/
+[cover.tahoma docs]: https://home-assistant.io/components/cover.tahoma/
+[cover.wink docs]: https://home-assistant.io/components/cover.wink/
+[cover.xiaomi_aqara docs]: https://home-assistant.io/components/cover.xiaomi_aqara/
+[deconz docs]: https://home-assistant.io/components/deconz/
+[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.tomato docs]: https://home-assistant.io/components/device_tracker.tomato/
+[device_tracker.unifi_direct docs]: https://home-assistant.io/components/device_tracker.unifi_direct/
+[ecobee docs]: https://home-assistant.io/components/ecobee/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[fan.xiaomi_miio docs]: https://home-assistant.io/components/fan.xiaomi_miio/
+[google_assistant docs]: https://home-assistant.io/components/google_assistant/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[hive docs]: https://home-assistant.io/components/hive/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[hue docs]: https://home-assistant.io/components/hue/
+[ihc docs]: https://home-assistant.io/components/ihc/
+[ihc.const docs]: https://home-assistant.io/components/ihc.const/
+[ihc.ihcdevice docs]: https://home-assistant.io/components/ihc.ihcdevice/
+[iota docs]: https://home-assistant.io/components/iota/
+[light.deconz docs]: https://home-assistant.io/components/light.deconz/
+[light.decora docs]: https://home-assistant.io/components/light.decora/
+[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
+[light.greenwave docs]: https://home-assistant.io/components/light.greenwave/
+[light.hive docs]: https://home-assistant.io/components/light.hive/
+[light.hyperion docs]: https://home-assistant.io/components/light.hyperion/
+[light.ihc docs]: https://home-assistant.io/components/light.ihc/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.wemo docs]: https://home-assistant.io/components/light.wemo/
+[light.xiaomi_aqara docs]: https://home-assistant.io/components/light.xiaomi_aqara/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[lutron docs]: https://home-assistant.io/components/lutron/
+[map docs]: https://home-assistant.io/components/map/
+[media_player.samsungtv docs]: https://home-assistant.io/components/media_player.samsungtv/
+[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
+[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
+[notify.clicksend docs]: https://home-assistant.io/components/notify.clicksend/
+[notify.prowl docs]: https://home-assistant.io/components/notify.prowl/
+[plant docs]: https://home-assistant.io/components/plant/
+[rfxtrx docs]: https://home-assistant.io/components/rfxtrx/
+[scene docs]: https://home-assistant.io/components/scene/
+[sensor.alpha_vantage docs]: https://home-assistant.io/components/sensor.alpha_vantage/
+[sensor.linux_battery docs]: https://home-assistant.io/components/sensor.linux_battery/
+[sensor.bme680 docs]: https://home-assistant.io/components/sensor.bme680/
+[sensor.deconz docs]: https://home-assistant.io/components/sensor.deconz/
+[sensor.etherscan docs]: https://home-assistant.io/components/sensor.etherscan/
+[sensor.fixer docs]: https://home-assistant.io/components/sensor.fixer/
+[sensor.hive docs]: https://home-assistant.io/components/sensor.hive/
+[sensor.ihc docs]: https://home-assistant.io/components/sensor.ihc/
+[sensor.iota docs]: https://home-assistant.io/components/sensor.iota/
+[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/
+[sensor.miflora docs]: https://home-assistant.io/components/sensor.miflora/
+[sensor.min_max docs]: https://home-assistant.io/components/sensor.min_max/
+[sensor.mold_indicator docs]: https://home-assistant.io/components/sensor.mold_indicator/
+[mychevy docs]: https://home-assistant.io/components/mychevy/
+[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
+[sensor.random docs]: https://home-assistant.io/components/sensor.random/
+[sensor.teksavvy docs]: https://home-assistant.io/components/sensor.teksavvy/
+[sensor.xbox_live docs]: https://home-assistant.io/components/sensor.xbox_live/
+[sensor.xiaomi_aqara docs]: https://home-assistant.io/components/sensor.xiaomi_aqara/
+[sensor.yr docs]: https://home-assistant.io/components/sensor.yr/
+[snips docs]: https://home-assistant.io/components/snips/
+[switch.fritzdect docs]: https://home-assistant.io/components/switch.fritzdect/
+[switch.hive docs]: https://home-assistant.io/components/switch.hive/
+[switch.ihc docs]: https://home-assistant.io/components/switch.ihc/
+[switch.snmp docs]: https://home-assistant.io/components/switch.snmp/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[switch.xiaomi_aqara docs]: https://home-assistant.io/components/switch.xiaomi_aqara/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[system_log docs]: https://home-assistant.io/components/system_log/
+[tahoma docs]: https://home-assistant.io/components/tahoma/
+[tts.google docs]: https://home-assistant.io/components/tts.google/
+[vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[waterfurnace docs]: https://home-assistant.io/components/waterfurnace/
+[wemo docs]: https://home-assistant.io/components/wemo/
+[wink docs]: https://home-assistant.io/components/wink/
+[xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/
+[zwave docs]: https://home-assistant.io/components/zwave/
[@martinhjelmare]: https://github.com/martinhjelmare
[@frenck]: https://github.com/frenck
[#11929]: https://github.com/home-assistant/home-assistant/pull/11929
@@ -502,10 +502,10 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@scop]: https://github.com/scop
[@smoldaner]: https://github.com/smoldaner
[@tschmidty69]: https://github.com/tschmidty69
-[climate.daikin docs]: /components/climate.daikin/
-[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/
-[frontend docs]: /components/frontend/
-[media_player.squeezebox docs]: /components/media_player.squeezebox/
-[remote.harmony docs]: /components/remote.harmony/
-[sensor.deutsche_bahn docs]: /components/sensor.deutsche_bahn/
-[snips docs]: /components/snips/
+[climate.daikin docs]: https://home-assistant.io/components/climate.daikin/
+[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/
+[frontend docs]: https://home-assistant.io/components/frontend/
+[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/
+[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
+[sensor.deutsche_bahn docs]: https://home-assistant.io/components/sensor.deutsche_bahn/
+[snips docs]: https://home-assistant.io/components/snips/
diff --git a/source/_posts/2018-02-09-disabling-disqus.markdown b/source/_posts/2018-02-09-disabling-disqus.markdown
index 6183c238f6..980c035521 100644
--- a/source/_posts/2018-02-09-disabling-disqus.markdown
+++ b/source/_posts/2018-02-09-disabling-disqus.markdown
@@ -10,7 +10,7 @@ comments: true
categories: Community
---
-Last week, starting with the release of [Home Assistant 0.62](/blog/2018/01/27/release-62/), we switched to using our [community forums](https://community.home-assistant.io) for comments on our blog posts. By doing so, people are able to use their existing Home Assistant community accounts to comment on our blog posts and engage with one another. It has been easier for our users to stay in the loop with one less channel to keep track off.
+Last week, starting with the release of [Home Assistant 0.62](https://home-assistant.io/blog/2018/01/27/release-62/), we switched to using our [community forums](https://community.home-assistant.io) for comments on our blog posts. By doing so, people are able to use their existing Home Assistant community accounts to comment on our blog posts and engage with one another. It has been easier for our users to stay in the loop with one less channel to keep track off.
Previously, we were using the free version of Disqus to power comments on our blog. After the switch, to preserve the old comments, we decided to keep Disqus active on the older blog post pages. However, today we decided to turn them off.
diff --git a/source/_posts/2018-02-10-release-63.markdown b/source/_posts/2018-02-10-release-63.markdown
deleted file mode 100644
index dc23d2029f..0000000000
--- a/source/_posts/2018-02-10-release-63.markdown
+++ /dev/null
@@ -1,690 +0,0 @@
----
-layout: post
-title: "0.63: Entity Registry, SQL Sensor, Mercedes cars"
-description: "Reserve entity IDs for your devices with the new entity registry, show query results as a sensor and yet another car integrated."
-date: 2018-02-10 01:00:00
-date_formatted: "February 10, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Release-Notes
-og_image: /images/blog/2018-02-0.63/components.png
----
-
-
-
-## {% linkable_title Date set for dropping Python 3.4 support %}
-
-As [announced in October](/blog/2017/10/06/deprecating-python-3.4-support/), we're going to drop Python 3.4 support in 2018. We've now decided that in two releases, 0.65, the minimum Python version that will be supported is bumped to 3.5.3. This won't impact most users. You are already fine if you're using Hass.io, the latest Debian stable (Stretch) or a derivative of that (Raspbian, Ubuntu).
-
-## {% linkable_title Entity Registry %}
-
-This release introduces the entity registry. The entity registry allows integrations to reserve entity IDs. This means that we'll automatically grant an entity ID to a device. It's reserved so that no other device will ever get that entity ID. It also means that as a user, you will be able to customize the entity IDs for these devices.
-
-For an integration to leverage the entity registry, it needs to define a unique ID for each of their entities. A unique ID is something that we can uniquely identify the device and that is not configurable. So a serial number and mac address are ok, IP addresses or names are not.
-
-Examples of integrations that have unique IDs defined in this release are Z-Wave, Hue, Nest, LIFX, Sonos, Apple TV.
-
-To update the entity ID that will be assigned to your device, update `
-
-🎉 1000 integrations, 1000 integrations, 1000 integrations! 🎉
-
-That's right, Home Assistant 0.64 is here! In case you have missed our latest [Cloud update](/blog/2018/02/19/cloud-update/), the Home Assistant Alexa skill is now live in all regions and we're working with Google in getting the Smart Home skill for Google Assistant approved. Exciting times!
-
-In the meanwhile, some great new integrations have landed, including yet another car 🚗 This time it's BMW.
-
-This is going to be the last release that supports Python 3.4. Starting with the next release, the minimum version required will be Python 3.5.3. [Learn more here.](/blog/2017/10/06/deprecating-python-3.4-support/)
-
-## {% linkable_title HomeKit %}
-
-Native HomeKit support has arrived! Thanks to @cdce8p It is now possible to expose some devices over HomeKit to allow control via Siri and other things speaking the HomeKit protocol. Initial support has been added for temperature sensors and cover devices. Expect more devices to be added soon.
-
-[Check the HomeKit docs][HomeKit docs]
-
-## {% linkable_title Hass.io UI update %}
-
-Some of you already noticed that your Hass.io panel looks a bit different since this morning: @pvizeli pressed the ~~red~~ green button and the new UI got live. The Hass.io team ([@frenck] [@pvizeli] [@ryanm101]) is doing a great job in adding new features (like partial or encrypted snapshots) to the Hass.io backend and fixing bugs. However, those features where only added to the command line tools but not to the frontend.
-
-That's where [@c727] and [@ciotlosm] jumped in. They made new features accessible via the frontend and improved the overall navigation.
-
-We know that some features are still missing or broken, we are fixing this right now! Check this [issue](https://github.com/home-assistant/home-assistant-polymer/issues/912) first before you report any issues related to the Hass.io panel, please.
-
-## {% linkable_title Chart.js %}
-
-The frontend is now rendering the graphs and charts using Chart.js thanks to the hard work by [@fanthos]. This means that you can now render all the charts without being connected to the internet!
-
-## {% linkable_title August integration %}
-
-Major new integration by [@snjoetw]: August locks and door bells! Lock and unlock from Home Assistant and detect when your doorbell is rung or senses motion. Awesome!
-
-## {% linkable_title Cast bug fixes %}
-
-[@OttoWinter] has crushed a bunch of bugs for our ChromeCast integration. Including that nasy Cast group discovery issue! He is working on some more improvements that should arrive soon, stay tuned. Awesome work Otto!
-
-## {% linkable_title New Platforms %}
-
-- Support for August doorbell ([@snjoetw] - [#11124]) ([august docs]) ([binary_sensor.august docs]) ([camera.august docs]) ([lock.august docs]) (new-platform)
-- Add new component: BMW connected drive ([@ChristianKuehnel] - [#12277]) ([bmw_connected_drive docs]) ([device_tracker.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (new-platform)
-- Add New Sensor for ISP Start.ca ([@mikeodr] - [#12356]) ([sensor.startca docs]) (new-platform)
-- Add the Xiaomi TV platform. ([@fattdev] - [#12359]) ([media_player.xiaomi_tv docs]) (new-platform)
-- added smappee component ([@hmn] - [#11491]) ([smappee docs]) ([sensor.smappee docs]) ([switch.smappee docs]) (new-platform)
-- Add support for HomeKit ([@cdce8p] - [#12488]) ([homekit docs]) (new-platform)
-- Adds filesize component ([@robmarkcole] - [#12211]) ([sensor.filesize docs]) (new-platform)
-- Adds folder sensor ([@robmarkcole] - [#12208]) ([sensor.folder docs]) (new-platform)
-- Spotcrime ([@jcconnell] - [#12460]) ([sensor.spotcrime docs]) (new-platform)
-- Add Tahoma scenes ([@bakedraccoon] - [#12498]) ([scene docs]) ([tahoma docs]) (new-platform)
-
-## {% linkable_title Release 0.64.1 - February 27 %}
-
-- Frontend: Don't put unit of sensor on new line ([@NovapaX])
-- Frontend: Fix display issues on iOS 9.3.5 ([@NovapaX])
-- Frontend: Fix chart legend not showing correctly when data has 1 serie ([@fanthos])
-- Frontend: Fix cards not getting updated ([@balloob])
-- Cast automatically drop connection ([@OttoWinter] - [#12635]) ([media_player.cast docs])
-- Roomba timeout ([@kellerza] - [#12645]) ([vacuum.roomba docs])
-- Fix a problem with calling `deconz.close` ([@aronsky] - [#12657]) ([deconz docs])
-- Harmony: make activity optional ([@balloob] - [#12679]) ([remote.harmony docs])
-- Fix getting state from iglo ([@jesserockz] - [#12685]) ([light.iglo docs])
-- Fix mysensor defaults ([@balloob] - [#12687]) ([mysensors docs])
-- Component deconz: Fix dark attribute on presence sensors ([@tumik] - [#12691]) ([binary_sensor.deconz docs])
-- Bugfix: Update of sources for non AVR-X devices always fails ([@scarface-4711] - [#12711]) ([media_player.denonavr docs])
-- Don't allow to use a old unsecure library ([@pvizeli] - [#12715])
-- Unbreak tahoma ([@bakedraccoon] - [#12719]) ([tahoma docs])
-- fix for https://github.com/home-assistant/home-assistant/issues/12673 ([@ChristianKuehnel] - [#12726]) ([sensor.alpha_vantage docs])
-- Fix harmony duplicate detection ([@amelchio] - [#12729]) ([remote.harmony docs])
-- Update ZHA deps ([@balloob] - [#12737]) ([zha docs])
-- MQTT: Fix doing async inside sync context ([@OttoWinter])
-- Fix DarSky humidity precision ([@PhilRW])
-
-## {% linkable_title Release 0.64.2 - March 1 %}
-
-- updated to bimmer_connected 0.4.1 ([@ChristianKuehnel] - [#12759]) ([bmw_connected_drive docs])
-- Revert optimized logbook SQL ([@amelchio] - [#12762]) ([logbook docs])
-- bump fedex version ([@happyleavesaoc] - [#12764]) ([sensor.fedex docs])
-- Silence harmless sonos data structure warnings ([@amelchio] - [#12767]) ([media_player.sonos docs])
-- Update samsungctl library to latest version ([@uchagani] - [#12769]) ([media_player.samsungtv docs])
-- Fixed missing optional keyerror data_bits ([@basschipper] - [#12789]) ([binary_sensor.rfxtrx docs])
-- Fixed Pollen.com bugs with ZIP codes and invalid API responses ([@bachya] - [#12790]) ([sensor.pollen docs])
-- Fix dead Sonos web interface with some music sources ([@amelchio] - [#12796]) ([media_player.sonos docs])
-- Unique IDs for Plex Clients ([@ryanm101] - [#12799]) ([media_player.plex docs])
-
-## {% linkable_title Release 0.64.3 - March 2 %}
-
-- is_allowed_path: Also test folder #12788 #12807 ([@kellerza] - [#12810])
-- Fix sensibo default IDs to be according to schema ([@andrey-git] - [#12837]) ([climate.sensibo docs])
-- Cloud: handle unauth better ([@balloob] - [#12840]) ([cloud docs])
-- Handle Hue errors better ([@balloob] - [#12845]) ([hue docs])
-
-## {% linkable_title If you need help... %}
-
-...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
-
-## {% linkable_title Reporting Issues %}
-
-Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
-
-
-
-## {% linkable_title Breaking Changes %}
-
-- Home Assistant now defaults to purge recorded history that is older than 10 days. If you want to keep your recorded data for longer than that, you must configure the number of days to retain _before starting 0.64 for the first time_, for example:
- ```yaml
- recorder:
- purge_keep_days: 30
- ```
-
- If you want to keep the previous default of never deleting history, use this configuration:
- ```yaml
- recorder:
- purge_interval: 0
- ```
- ([@amelchio] - [#12271]) (breaking change)
-- Show a persistent_notification if no symbols and no currencies are configured ([@ChristianKuehnel] - [#12252]) ([sensor.alpha_vantage docs]) (breaking change)
-- Updated RainMachine unique IDs to play better with the entity registry. If RainMachine had been configured previously, new entries will be placed into the entity registry, causing there to be two of each program/zone defined. To address, simply alter the `entity_registry.yaml` as desired. ([@bachya] - [#12315]) ([switch.rainmachine docs]) (breaking change)
-- Updated AirVisual unique IDs to play better with the entity registry. If AirVisual had been configured previously, new entries will be placed into the entity registry, causing there to be two of each sensor type defined. To address, simply alter the `entity_registry.yaml` as desired. ([@bachya] - [#12319]) ([sensor.airvisual docs]) (breaking change)
-- Custom component devs only: voluptuous now requires default values for config keys to be valid values. ([@balloob] - [#12463]) (breaking change)
-- Fixes `usps` platform. Dependency `myusps` now leverages Selenium webdriver to overcome login issues. This is a breaking change since the user must now have additional dependencies installed - either `google-chrome` and `chromedriver`, or `phantomjs`. There is a new config option `driver` that allows the user to specify their preference, though `phantomjs` is the default. Doc PR forthcoming that will outline choices and make suggestions based on user's OS.
- ([@happyleavesaoc] - [#12465]) ([usps docs]) (breaking change)
-- LimitlessLED has been converted to assumed state. Will no longer turn the lights off when restarting Home Assistant. Will no longer revert changes made by other controllers. ([@amelchio] - [#12475]) ([light.limitlessled docs]) (breaking change)
-
-## {% linkable_title All changes %}
-
-- device_tracker.asuswrt: Clean up unused connection param ([@trisk] - [#12262]) ([device_tracker.asuswrt docs])
-- Fix some rfxtrx devices with multiple sensors ([@neffs] - [#12264]) ([sensor.rfxtrx docs])
-- have climate fallback to state if no ATTR_OPERATION_MODE (#12271) ([@ttroy50] - [#12279]) ([google_assistant docs])
-- check_config check bootstrap errors ([@kellerza] - [#12291])
-- Attempt fixing flakiness of check config test ([@balloob] - [#12283])
-- Fix MQTT retained message not being re-dispatched ([@OttoWinter] - [#12004]) ([mqtt docs])
-- Fix config error for FTP links, add test ([@ReneNulschDE] - [#12294]) ([weblink docs])
-- Fix Panel_IFrame - FTP URL not allowed in 0.63 ([@ReneNulschDE] - [#12295]) ([panel_iframe docs])
-- Upgrade pylint to 1.8.2 ([@OttoWinter] - [#12274])
-- Move HassIntent handler code into helpers/intent ([@tschmidty69] - [#12181]) ([conversation docs])
-- Migrated SABnzbd sensor to asyncio and switched to pypi library ([@jeradM] - [#12290]) ([sensor.sabnzbd docs])
-- 📝 Fix fixture encoding ([@OttoWinter] - [#12296])
-- Clarify tahoma errrors ([@bakedraccoon] - [#12307]) ([tahoma docs])
-- add friendly_name_template to template sensor ([@NovapaX] - [#12268]) ([sensor.template docs])
-- Purge recorder data by default ([@amelchio] - [#12271]) (breaking change)
-- Protect bloomsky platform setup ([@balloob] - [#12316]) ([binary_sensor.bloomsky docs]) ([camera.bloomsky docs]) ([sensor.bloomsky docs])
-- Removed default sensor configuration ([@ChristianKuehnel] - [#12252]) ([sensor.alpha_vantage docs]) (breaking change)
-- Force LF line endings for Windows ([@kellerza] - [#12266])
-- Updated RainMachine to play better with the entity registry ([@bachya] - [#12315]) ([switch.rainmachine docs]) (breaking change)
-- Revert #12316 ([@balloob] - [#12329]) ([binary_sensor.bloomsky docs]) ([camera.bloomsky docs]) ([sensor.bloomsky docs])
-- zha: Add remove service ([@rcloran] - [#11683]) ([zha docs])
-- Fix line endings [skipci] ([@balloob] - [#12333])
-- Unifi tracking filter by SSID ([@mikeodr] - [#12281]) ([device_tracker.unifi docs])
-- device_tracker.asuswrt: Ignore unreachable ip neigh entries ([@trisk] - [#12201]) ([device_tracker.asuswrt docs])
-- nmap_tracker: don't scan on setup ([@abmantis] - [#12322]) ([device_tracker.nmap_tracker docs])
-- Upgrade Sphinx to 1.7.0 ([@fabaff] - [#12335])
-- Mock Module + Platform default to async ([@balloob] - [#12347])
-- Change Unifi SSID filtering to list comprehension ([@mikeodr] - [#12344]) ([device_tracker.unifi docs])
-- Use the speedometer icon in the fastdotcom sensor ([@d0ugal] - [#12348]) ([sensor.fastdotcom docs])
-- Communication reduced. Setting brightness and/or color temperature will turn on the device. ([@syssi] - [#12343]) ([light.xiaomi_miio docs])
-- Add New Sensor for ISP Start.ca ([@mikeodr] - [#12356]) ([sensor.startca docs]) (new-platform)
-- bump fedex version ([@happyleavesaoc] - [#12362]) ([sensor.fedex docs])
-- Upgrade alpha_vantage to 1.9.0 ([@fabaff] - [#12352]) ([sensor.alpha_vantage docs])
-- Eq3btsmart more reliable ([@karlkar] - [#11555]) ([climate.eq3btsmart docs])
-- Allow disabling entities in the registry ([@balloob] - [#12360])
-- Upgrade panasonic_viera to 0.3.1 ([@dgomes] - [#12370]) ([media_player.panasonic_viera docs])
-- SMA sensor add SSL and upgrade to pysma 0.2 ([@kellerza] - [#12354]) ([sensor.sma docs])
-- Specify algorithms for webpush jwt verification ([@balloob] - [#12378]) ([notify.html5 docs])
-- Upgrade youtube_dl to 2018.02.11 ([@fabaff] - [#12383]) ([media_extractor docs])
-- Remove usage of deprecated assert method ([@balloob] - [#12379])
-- Add attributes (fixes #12332) ([@fabaff] - [#12377]) ([sensor.speedtest docs])
-- Improve service by allowing to reference entity id instead of deconz id ([@Kane610] - [#11862]) ([deconz docs]) ([scene docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs])
-- Pollen.com: Entity Registry updates and cleanup ([@bachya] - [#12361]) ([sensor.pollen docs])
-- Changed pyvera version to 0.2.41 ([@patrik3k] - [#12391]) ([vera docs])
-- File Path fixes for RPi Camera ([@FrederikBolding] - [#12338]) ([camera.rpi_camera docs])
-- Code cleanup of velux scene ([@Julius2342] - [#12390]) ([scene docs])
-- Upgrade sphinx-autodoc-typehints to 1.2.5 ([@fabaff] - [#12404])
-- Extract data validator to own file and add tests ([@balloob] - [#12401]) ([cloud docs]) ([conversation docs]) ([http docs]) ([shopping_list docs]) (new-platform)
-- Fix MQTT payload decode returning prematurely ([@OttoWinter] - [#12420]) ([mqtt docs])
-- Print every changed file on new line ([@cdce8p] - [#12412])
-- Added support for colored KNX lights ([@Julius2342] - [#12411]) ([knx docs]) ([light.knx docs])
-- Small code cleanup: ([@Julius2342] - [#12409]) ([scene docs])
-- Cleanup of knx component ([@Julius2342] - [#12408]) ([knx docs]) ([binary_sensor.knx docs]) ([climate.knx docs]) ([cover.knx docs]) ([light.knx docs]) ([notify.knx docs]) ([sensor.knx docs]) ([switch.knx docs])
-- Update the Tibber sensor at startup ([@danielhiversen] - [#12428]) ([sensor.tibber docs])
-- zha: Add unique_id to entities ([@rcloran] - [#12331]) ([zha docs])
-- Cleanup http ([@balloob] - [#12424]) ([frontend docs]) ([http docs])
-- Update CODEOWNERS ([@dgomes] - [#12440])
-- Fix: timeout data attribute now is parsed to float ([@sjvc] - [#12432]) ([telegram_bot docs])
-- Stop mapping zigbee switches to lights & switches. ([@igorbernstein2] - [#12280]) ([zha docs])
-- AirVisual: Entity Registry updates and cleanup ([@bachya] - [#12319]) ([sensor.airvisual docs]) (breaking change)
-- Vagrant - sendfile python3.5 debian-stretch ([@tabakhase] - [#12454])
-- Add effects to iGlo Lights ([@jesserockz] - [#12365]) ([light.iglo docs])
-- Fake the state for a short period and skip the next update. ([@syssi] - [#12446]) ([fan.xiaomi_miio docs])
-- Initial support for Config Entries ([@balloob] - [#12079])
-- Make WUnderground async ([@OttoWinter] - [#12385]) ([sensor.wunderground docs])
-- Add the Xiaomi TV platform. ([@fattdev] - [#12359]) ([media_player.xiaomi_tv docs]) (new-platform)
-- Update voluputous ([@balloob] - [#12463]) (breaking change)
-- Map Alexa StepVolume responses to volume_up/down ([@lucasweb78] - [#12467]) ([alexa docs])
-- ONVIF Camera added Error handling and rtsp authentication. ([@matt2005] - [#11129]) ([camera.onvif docs])
-- Bump aioautomatic to 0.6.5 for voluptuous 0.11 ([@armills] - [#12480]) ([device_tracker.automatic docs])
-- Add example in test how to create list or object in template ([@balloob] - [#12469])
-- KNX/Climate: Fixed platform schema min/max values. ([@Julius2342] - [#12477]) ([climate.knx docs])
-- Prevent error when no internet or DNS is available ([@mjj4791] - [#12486]) ([sensor.buienradar docs]) ([weather.buienradar docs])
-- Added doorbird_last_motion to DoorBird camera platform ([@sjvc] - [#12457]) ([camera.doorbird docs])
-- Fail gracefully with unreachable LaMetric ([@PhilRW] - [#12451]) ([notify.lametric docs])
-- Enable compression when sending json to client ([@elupus] - [#11165]) ([http docs])
-- bump usps version ([@happyleavesaoc] - [#12465]) ([usps docs]) (breaking change)
-- Try deflaking recorder tests ([@balloob] - [#12492])
-- Support for August doorbell ([@snjoetw] - [#11124]) ([august docs]) ([binary_sensor.august docs]) ([camera.august docs]) ([lock.august docs]) (new-platform)
-- Avoid warnings when purging an empty database ([@amelchio] - [#12494])
-- Support for PTZ in Onvif cameras ([@karlkar] - [#11630]) ([camera.onvif docs])
-- Rework Sonos media player platform ([@amelchio] - [#12126]) ([media_player.sonos docs])
-- Converted shopping list to use json util and added default override for json util ([@FrederikBolding] - [#12478]) ([shopping_list docs])
-- added smappee component ([@hmn] - [#11491]) ([smappee docs]) ([sensor.smappee docs]) ([switch.smappee docs]) (new-platform)
-- More features for the Bluesound component ([@thrawnarn] - [#11450]) ([media_player.bluesound docs])
-- zha: Simplify unique ID ([@rcloran] - [#12495]) ([zha docs])
-- zha: Add support for humidity sensors ([@rcloran] - [#12496]) ([zha docs]) ([sensor.zha docs])
-- bump python-eq3bt version, fixes #12499 ([@rytilahti] - [#12510]) ([climate.eq3btsmart docs])
-- new version of xiaomi lib ([@danielhiversen] - [#12513]) ([xiaomi_aqara docs])
-- python-miio version bumped. (Closes: #12471) ([@syssi] - [#12481]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
-- LimitlessLED assumed state ([@amelchio] - [#12475]) ([light.limitlessled docs]) (breaking change)
-- Add support for HomeKit ([@cdce8p] - [#12488]) ([homekit docs]) (new-platform)
-- Add password support ([@pvizeli] - [#12525]) ([hassio docs])
-- Changed to async_schedule_update_ha_state ([@thrawnarn] - [#12518]) ([media_player.bluesound docs])
-- Fix Sphinx build ([@balloob] - [#12535])
-- Update voluptuous serialize ([@balloob] - [#12538]) ([config docs])
-- Clarify a comment regarding python versions ([@aprasanna] - [#12537])
-- Adds filesize component ([@robmarkcole] - [#12211]) ([sensor.filesize docs]) (new-platform)
-- Clarify cloud error ([@balloob] - [#12540]) ([cloud docs])
-- Build JSON in executor ([@amelchio] - [#12536]) ([history docs]) ([logbook docs])
-- Bugfix: Input Datetime config schema ([@cdce8p] - [#12552]) ([input_datetime docs])
-- Fix numeric_state condition spamming on unavailable ([@OttoWinter] - [#12550])
-- Frontier silicon async ([@zhelev] - [#12503]) ([media_player.frontier_silicon docs])
-- Fix WUnderground spamming logs ([@OttoWinter] - [#12548]) ([sensor.wunderground docs])
-- Added support for milight single channel dimmer ([@rubenverhoef] - [#12558]) ([light.limitlessled docs])
-- Add new component: BMW connected drive ([@ChristianKuehnel] - [#12277]) ([bmw_connected_drive docs]) ([device_tracker.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (new-platform)
-- Cleanup hass.io component ([@pvizeli] - [#12556]) ([hassio docs])
-- Add support for smoke detector in deconz ([@Kane610] - [#12561]) ([deconz docs])
-- Fix caldav component handling missing dtend ([@bottomquark] - [#12562]) ([calendar.caldav docs])
-- Add limitlessled night effect ([@amelchio] - [#12567]) ([light.limitlessled docs])
-- Basic support of post 2016 AVR-X receivers ([@scarface-4711] - [#12569]) ([media_player.denonavr docs])
-- Fix config 404 ([@balloob] - [#12571]) ([config docs])
-- Logbook speedup ([@amelchio] - [#12566]) ([logbook docs])
-- Fix sonos default errorcodes ([@amelchio] - [#12582]) ([media_player.sonos docs])
-- Update pychromecast to 2.0.0 ([@balloob] - [#12587]) ([media_player.cast docs])
-- Set event_id foreign key in recorded states ([@amelchio] - [#12580])
-- Deconz support water sensor ([@Kane610] - [#12581]) ([deconz docs])
-- Cloud reconnect tweaks ([@balloob] - [#12586]) ([cloud docs])
-- Hassio cleanup part2 ([@pvizeli] - [#12588]) ([hassio docs])
-- Add Bluetooth and NFC card/tag Alarm types ([@matthewcky2k] - [#12151]) ([lock.zwave docs])
-- Fix fix isy994 fan detection ([@OverloadUT] - [#12595]) ([isy994 docs])
-- Adds folder sensor ([@robmarkcole] - [#12208]) ([sensor.folder docs]) (new-platform)
-- Add unique_id to Xiaomi Aqara ([@tinloaf] - [#12372]) ([xiaomi_aqara docs])
-- Make groups entities again ([@balloob] - [#12574]) ([alexa docs])
-- Python spotcrime ([@jcconnell] - [#12460]) ([sensor.spotcrime docs]) (new-platform)
-- Allow ignoring call service events in mqtt_eventstream ([@cmsimike] - [#12519]) ([mqtt_eventstream docs])
-- Set speed service fixed. ([@syssi] - [#12602]) ([fan.xiaomi_miio docs])
-- Updated script/lint ([@cdce8p] - [#12600])
-- Adding RoomHinting to GoogleAssistant to allow for room annotations. ([@jeremydk] - [#12598]) ([google_assistant docs])
-- Fix mclimate accounts with not only melissa components ([@kennedyshead] - [#12427]) ([melissa docs]) ([climate.melissa docs])
-- Cast unique_id and async discovery ([@OttoWinter] - [#12474]) ([media_player.cast docs])
-- Add Tahoma scenes ([@bakedraccoon] - [#12498]) ([scene docs]) ([tahoma docs]) (new-platform)
-- Optimize logbook SQL query ([@amelchio] - [#12608]) ([logbook docs])
-- Fix voluptuous breaking change things ([@balloob] - [#12611]) ([xiaomi_aqara docs]) ([binary_sensor.knx docs])
-- OpenGarage - correctly handle offline status (#12612) ([@swbradshaw] - [#12613]) ([cover.opengarage docs])
-- Move recorder query out of event loop ([@amelchio] - [#12615])
-- Hassio update timeout filter list ([@pvizeli] - [#12617]) ([hassio docs])
-- The name of the enum must be used here because of the speed_list. ([@syssi] - [#12625]) ([fan.xiaomi_miio docs])
-- Fix cast doing I/O in event loop ([@OttoWinter] - [#12632]) ([media_player.cast docs])
-
-[#11124]: https://github.com/home-assistant/home-assistant/pull/11124
-[#11129]: https://github.com/home-assistant/home-assistant/pull/11129
-[#11165]: https://github.com/home-assistant/home-assistant/pull/11165
-[#11450]: https://github.com/home-assistant/home-assistant/pull/11450
-[#11491]: https://github.com/home-assistant/home-assistant/pull/11491
-[#11555]: https://github.com/home-assistant/home-assistant/pull/11555
-[#11630]: https://github.com/home-assistant/home-assistant/pull/11630
-[#11683]: https://github.com/home-assistant/home-assistant/pull/11683
-[#11862]: https://github.com/home-assistant/home-assistant/pull/11862
-[#12004]: https://github.com/home-assistant/home-assistant/pull/12004
-[#12079]: https://github.com/home-assistant/home-assistant/pull/12079
-[#12126]: https://github.com/home-assistant/home-assistant/pull/12126
-[#12151]: https://github.com/home-assistant/home-assistant/pull/12151
-[#12181]: https://github.com/home-assistant/home-assistant/pull/12181
-[#12201]: https://github.com/home-assistant/home-assistant/pull/12201
-[#12208]: https://github.com/home-assistant/home-assistant/pull/12208
-[#12211]: https://github.com/home-assistant/home-assistant/pull/12211
-[#12252]: https://github.com/home-assistant/home-assistant/pull/12252
-[#12262]: https://github.com/home-assistant/home-assistant/pull/12262
-[#12264]: https://github.com/home-assistant/home-assistant/pull/12264
-[#12266]: https://github.com/home-assistant/home-assistant/pull/12266
-[#12268]: https://github.com/home-assistant/home-assistant/pull/12268
-[#12271]: https://github.com/home-assistant/home-assistant/pull/12271
-[#12274]: https://github.com/home-assistant/home-assistant/pull/12274
-[#12277]: https://github.com/home-assistant/home-assistant/pull/12277
-[#12279]: https://github.com/home-assistant/home-assistant/pull/12279
-[#12280]: https://github.com/home-assistant/home-assistant/pull/12280
-[#12281]: https://github.com/home-assistant/home-assistant/pull/12281
-[#12283]: https://github.com/home-assistant/home-assistant/pull/12283
-[#12290]: https://github.com/home-assistant/home-assistant/pull/12290
-[#12291]: https://github.com/home-assistant/home-assistant/pull/12291
-[#12294]: https://github.com/home-assistant/home-assistant/pull/12294
-[#12295]: https://github.com/home-assistant/home-assistant/pull/12295
-[#12296]: https://github.com/home-assistant/home-assistant/pull/12296
-[#12307]: https://github.com/home-assistant/home-assistant/pull/12307
-[#12315]: https://github.com/home-assistant/home-assistant/pull/12315
-[#12316]: https://github.com/home-assistant/home-assistant/pull/12316
-[#12319]: https://github.com/home-assistant/home-assistant/pull/12319
-[#12322]: https://github.com/home-assistant/home-assistant/pull/12322
-[#12329]: https://github.com/home-assistant/home-assistant/pull/12329
-[#12331]: https://github.com/home-assistant/home-assistant/pull/12331
-[#12333]: https://github.com/home-assistant/home-assistant/pull/12333
-[#12335]: https://github.com/home-assistant/home-assistant/pull/12335
-[#12338]: https://github.com/home-assistant/home-assistant/pull/12338
-[#12343]: https://github.com/home-assistant/home-assistant/pull/12343
-[#12344]: https://github.com/home-assistant/home-assistant/pull/12344
-[#12347]: https://github.com/home-assistant/home-assistant/pull/12347
-[#12348]: https://github.com/home-assistant/home-assistant/pull/12348
-[#12352]: https://github.com/home-assistant/home-assistant/pull/12352
-[#12354]: https://github.com/home-assistant/home-assistant/pull/12354
-[#12356]: https://github.com/home-assistant/home-assistant/pull/12356
-[#12359]: https://github.com/home-assistant/home-assistant/pull/12359
-[#12360]: https://github.com/home-assistant/home-assistant/pull/12360
-[#12361]: https://github.com/home-assistant/home-assistant/pull/12361
-[#12362]: https://github.com/home-assistant/home-assistant/pull/12362
-[#12365]: https://github.com/home-assistant/home-assistant/pull/12365
-[#12370]: https://github.com/home-assistant/home-assistant/pull/12370
-[#12372]: https://github.com/home-assistant/home-assistant/pull/12372
-[#12377]: https://github.com/home-assistant/home-assistant/pull/12377
-[#12378]: https://github.com/home-assistant/home-assistant/pull/12378
-[#12379]: https://github.com/home-assistant/home-assistant/pull/12379
-[#12383]: https://github.com/home-assistant/home-assistant/pull/12383
-[#12385]: https://github.com/home-assistant/home-assistant/pull/12385
-[#12390]: https://github.com/home-assistant/home-assistant/pull/12390
-[#12391]: https://github.com/home-assistant/home-assistant/pull/12391
-[#12401]: https://github.com/home-assistant/home-assistant/pull/12401
-[#12404]: https://github.com/home-assistant/home-assistant/pull/12404
-[#12408]: https://github.com/home-assistant/home-assistant/pull/12408
-[#12409]: https://github.com/home-assistant/home-assistant/pull/12409
-[#12411]: https://github.com/home-assistant/home-assistant/pull/12411
-[#12412]: https://github.com/home-assistant/home-assistant/pull/12412
-[#12420]: https://github.com/home-assistant/home-assistant/pull/12420
-[#12424]: https://github.com/home-assistant/home-assistant/pull/12424
-[#12427]: https://github.com/home-assistant/home-assistant/pull/12427
-[#12428]: https://github.com/home-assistant/home-assistant/pull/12428
-[#12432]: https://github.com/home-assistant/home-assistant/pull/12432
-[#12440]: https://github.com/home-assistant/home-assistant/pull/12440
-[#12446]: https://github.com/home-assistant/home-assistant/pull/12446
-[#12451]: https://github.com/home-assistant/home-assistant/pull/12451
-[#12454]: https://github.com/home-assistant/home-assistant/pull/12454
-[#12457]: https://github.com/home-assistant/home-assistant/pull/12457
-[#12460]: https://github.com/home-assistant/home-assistant/pull/12460
-[#12463]: https://github.com/home-assistant/home-assistant/pull/12463
-[#12464]: https://github.com/home-assistant/home-assistant/pull/12464
-[#12465]: https://github.com/home-assistant/home-assistant/pull/12465
-[#12467]: https://github.com/home-assistant/home-assistant/pull/12467
-[#12469]: https://github.com/home-assistant/home-assistant/pull/12469
-[#12474]: https://github.com/home-assistant/home-assistant/pull/12474
-[#12475]: https://github.com/home-assistant/home-assistant/pull/12475
-[#12477]: https://github.com/home-assistant/home-assistant/pull/12477
-[#12478]: https://github.com/home-assistant/home-assistant/pull/12478
-[#12480]: https://github.com/home-assistant/home-assistant/pull/12480
-[#12481]: https://github.com/home-assistant/home-assistant/pull/12481
-[#12486]: https://github.com/home-assistant/home-assistant/pull/12486
-[#12488]: https://github.com/home-assistant/home-assistant/pull/12488
-[#12492]: https://github.com/home-assistant/home-assistant/pull/12492
-[#12494]: https://github.com/home-assistant/home-assistant/pull/12494
-[#12495]: https://github.com/home-assistant/home-assistant/pull/12495
-[#12496]: https://github.com/home-assistant/home-assistant/pull/12496
-[#12498]: https://github.com/home-assistant/home-assistant/pull/12498
-[#12503]: https://github.com/home-assistant/home-assistant/pull/12503
-[#12510]: https://github.com/home-assistant/home-assistant/pull/12510
-[#12513]: https://github.com/home-assistant/home-assistant/pull/12513
-[#12518]: https://github.com/home-assistant/home-assistant/pull/12518
-[#12519]: https://github.com/home-assistant/home-assistant/pull/12519
-[#12525]: https://github.com/home-assistant/home-assistant/pull/12525
-[#12535]: https://github.com/home-assistant/home-assistant/pull/12535
-[#12536]: https://github.com/home-assistant/home-assistant/pull/12536
-[#12537]: https://github.com/home-assistant/home-assistant/pull/12537
-[#12538]: https://github.com/home-assistant/home-assistant/pull/12538
-[#12540]: https://github.com/home-assistant/home-assistant/pull/12540
-[#12548]: https://github.com/home-assistant/home-assistant/pull/12548
-[#12550]: https://github.com/home-assistant/home-assistant/pull/12550
-[#12552]: https://github.com/home-assistant/home-assistant/pull/12552
-[#12556]: https://github.com/home-assistant/home-assistant/pull/12556
-[#12558]: https://github.com/home-assistant/home-assistant/pull/12558
-[#12561]: https://github.com/home-assistant/home-assistant/pull/12561
-[#12562]: https://github.com/home-assistant/home-assistant/pull/12562
-[#12566]: https://github.com/home-assistant/home-assistant/pull/12566
-[#12567]: https://github.com/home-assistant/home-assistant/pull/12567
-[#12569]: https://github.com/home-assistant/home-assistant/pull/12569
-[#12571]: https://github.com/home-assistant/home-assistant/pull/12571
-[#12574]: https://github.com/home-assistant/home-assistant/pull/12574
-[#12580]: https://github.com/home-assistant/home-assistant/pull/12580
-[#12581]: https://github.com/home-assistant/home-assistant/pull/12581
-[#12582]: https://github.com/home-assistant/home-assistant/pull/12582
-[#12586]: https://github.com/home-assistant/home-assistant/pull/12586
-[#12587]: https://github.com/home-assistant/home-assistant/pull/12587
-[#12588]: https://github.com/home-assistant/home-assistant/pull/12588
-[#12595]: https://github.com/home-assistant/home-assistant/pull/12595
-[#12598]: https://github.com/home-assistant/home-assistant/pull/12598
-[#12600]: https://github.com/home-assistant/home-assistant/pull/12600
-[#12602]: https://github.com/home-assistant/home-assistant/pull/12602
-[#12608]: https://github.com/home-assistant/home-assistant/pull/12608
-[#12611]: https://github.com/home-assistant/home-assistant/pull/12611
-[#12613]: https://github.com/home-assistant/home-assistant/pull/12613
-[#12615]: https://github.com/home-assistant/home-assistant/pull/12615
-[#12617]: https://github.com/home-assistant/home-assistant/pull/12617
-[#12625]: https://github.com/home-assistant/home-assistant/pull/12625
-[#12632]: https://github.com/home-assistant/home-assistant/pull/12632
-[#12669]: https://github.com/home-assistant/home-assistant/pull/12669
-[@ChristianKuehnel]: https://github.com/ChristianKuehnel
-[@FrederikBolding]: https://github.com/FrederikBolding
-[@Julius2342]: https://github.com/Julius2342
-[@Kane610]: https://github.com/Kane610
-[@NovapaX]: https://github.com/NovapaX
-[@OttoWinter]: https://github.com/OttoWinter
-[@OverloadUT]: https://github.com/OverloadUT
-[@PhilRW]: https://github.com/PhilRW
-[@ReneNulschDE]: https://github.com/ReneNulschDE
-[@abmantis]: https://github.com/abmantis
-[@amelchio]: https://github.com/amelchio
-[@aprasanna]: https://github.com/aprasanna
-[@armills]: https://github.com/armills
-[@bachya]: https://github.com/bachya
-[@bakedraccoon]: https://github.com/bakedraccoon
-[@balloob]: https://github.com/balloob
-[@bottomquark]: https://github.com/bottomquark
-[@cdce8p]: https://github.com/cdce8p
-[@cmsimike]: https://github.com/cmsimike
-[@d0ugal]: https://github.com/d0ugal
-[@danielhiversen]: https://github.com/danielhiversen
-[@dgomes]: https://github.com/dgomes
-[@elupus]: https://github.com/elupus
-[@fabaff]: https://github.com/fabaff
-[@fattdev]: https://github.com/fattdev
-[@gerard33]: https://github.com/gerard33
-[@happyleavesaoc]: https://github.com/happyleavesaoc
-[@hmn]: https://github.com/hmn
-[@igorbernstein2]: https://github.com/igorbernstein2
-[@jcconnell]: https://github.com/jcconnell
-[@jeradM]: https://github.com/jeradM
-[@jeremydk]: https://github.com/jeremydk
-[@jesserockz]: https://github.com/jesserockz
-[@karlkar]: https://github.com/karlkar
-[@kellerza]: https://github.com/kellerza
-[@kennedyshead]: https://github.com/kennedyshead
-[@lucasweb78]: https://github.com/lucasweb78
-[@matt2005]: https://github.com/matt2005
-[@matthewcky2k]: https://github.com/matthewcky2k
-[@mikeodr]: https://github.com/mikeodr
-[@mjj4791]: https://github.com/mjj4791
-[@neffs]: https://github.com/neffs
-[@patrik3k]: https://github.com/patrik3k
-[@pvizeli]: https://github.com/pvizeli
-[@rcloran]: https://github.com/rcloran
-[@robmarkcole]: https://github.com/robmarkcole
-[@rubenverhoef]: https://github.com/rubenverhoef
-[@rytilahti]: https://github.com/rytilahti
-[@scarface-4711]: https://github.com/scarface-4711
-[@sjvc]: https://github.com/sjvc
-[@snjoetw]: https://github.com/snjoetw
-[@swbradshaw]: https://github.com/swbradshaw
-[@syssi]: https://github.com/syssi
-[@tabakhase]: https://github.com/tabakhase
-[@thrawnarn]: https://github.com/thrawnarn
-[@tinloaf]: https://github.com/tinloaf
-[@trisk]: https://github.com/trisk
-[@tschmidty69]: https://github.com/tschmidty69
-[@ttroy50]: https://github.com/ttroy50
-[@zhelev]: https://github.com/zhelev
-[@fanthos]: https://github.com/fanthos
-[@c727]: https://github.com/c727
-[@ciotlosm]: https://github.com/ciotlosm
-[@frenck]: https://github.com/frenck
-[@pvizeli]: https://github.com/pvizeli
-[@ryanm101]: https://github.com/ryanm101
-[alexa docs]: /components/alexa/
-[august docs]: /components/august/
-[binary_sensor.august docs]: /components/binary_sensor.august/
-[binary_sensor.bloomsky docs]: /components/binary_sensor.bloomsky/
-[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
-[binary_sensor.knx docs]: /components/binary_sensor.knx/
-[bmw_connected_drive docs]: /components/bmw_connected_drive/
-[calendar.caldav docs]: /components/calendar.caldav/
-[camera.august docs]: /components/camera.august/
-[camera.bloomsky docs]: /components/camera.bloomsky/
-[camera.doorbird docs]: /components/camera.doorbird/
-[camera.onvif docs]: /components/camera.onvif/
-[camera.rpi_camera docs]: /components/camera.rpi_camera/
-[climate.eq3btsmart docs]: /components/climate.eq3btsmart/
-[climate.knx docs]: /components/climate.knx/
-[climate.melissa docs]: /components/climate.melissa/
-[cloud docs]: /components/cloud/
-[config docs]: /components/config/
-[conversation docs]: /components/conversation/
-[cover.knx docs]: /components/cover.knx/
-[cover.opengarage docs]: /components/cover.opengarage/
-[deconz docs]: /components/deconz/
-[device_tracker.asuswrt docs]: /components/device_tracker.asuswrt/
-[device_tracker.automatic docs]: /components/device_tracker.automatic/
-[device_tracker.bmw_connected_drive docs]: /components/device_tracker.bmw_connected_drive/
-[device_tracker.nmap_tracker docs]: /components/device_tracker.nmap_tracker/
-[device_tracker.unifi docs]: /components/device_tracker.unifi/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[frontend docs]: /components/frontend/
-[google_assistant docs]: /components/google_assistant/
-[hassio docs]: /components/hassio/
-[history docs]: /components/history/
-[homekit docs]: /components/homekit/
-[homekit.accessories docs]: /components/homekit.accessories/
-[homekit.const docs]: /components/homekit.const/
-[homekit.covers docs]: /components/homekit.covers/
-[homekit.sensors docs]: /components/homekit.sensors/
-[http docs]: /components/http/
-[input_datetime docs]: /components/input_datetime/
-[isy994 docs]: /components/isy994/
-[knx docs]: /components/knx/
-[light.deconz docs]: /components/light.deconz/
-[light.iglo docs]: /components/light.iglo/
-[light.knx docs]: /components/light.knx/
-[light.limitlessled docs]: /components/light.limitlessled/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[lock.august docs]: /components/lock.august/
-[lock.zwave docs]: /components/lock.zwave/
-[logbook docs]: /components/logbook/
-[media_extractor docs]: /components/media_extractor/
-[media_player.bluesound docs]: /components/media_player.bluesound/
-[media_player.braviatv_psk docs]: /components/media_player.braviatv_psk/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.denonavr docs]: /components/media_player.denonavr/
-[media_player.frontier_silicon docs]: /components/media_player.frontier_silicon/
-[media_player.panasonic_viera docs]: /components/media_player.panasonic_viera/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.xiaomi_tv docs]: /components/media_player.xiaomi_tv/
-[melissa docs]: /components/melissa/
-[mqtt docs]: /components/mqtt/
-[mqtt_eventstream docs]: /components/mqtt_eventstream/
-[notify.html5 docs]: /components/notify.html5/
-[notify.knx docs]: /components/notify.knx/
-[notify.lametric docs]: /components/notify.lametric/
-[panel_iframe docs]: /components/panel_iframe/
-[remote.xiaomi_miio docs]: /components/remote.xiaomi_miio/
-[scene docs]: /components/scene/
-[sensor.airvisual docs]: /components/sensor.airvisual/
-[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
-[sensor.bloomsky docs]: /components/sensor.bloomsky/
-[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
-[sensor.buienradar docs]: /components/sensor.buienradar/
-[sensor.deconz docs]: /components/sensor.deconz/
-[sensor.fastdotcom docs]: /components/sensor.fastdotcom/
-[sensor.fedex docs]: /components/sensor.fedex/
-[sensor.filesize docs]: /components/sensor.filesize/
-[sensor.folder docs]: /components/sensor.folder/
-[sensor.knx docs]: /components/sensor.knx/
-[sensor.pollen docs]: /components/sensor.pollen/
-[sensor.rfxtrx docs]: /components/sensor.rfxtrx/
-[sensor.sabnzbd docs]: /components/sensor.sabnzbd/
-[sensor.sma docs]: /components/sensor.sma/
-[sensor.smappee docs]: /components/sensor.smappee/
-[sensor.speedtest docs]: /components/sensor.speedtest/
-[sensor.spotcrime docs]: /components/sensor.spotcrime/
-[sensor.startca docs]: /components/sensor.startca/
-[sensor.template docs]: /components/sensor.template/
-[sensor.tibber docs]: /components/sensor.tibber/
-[sensor.wunderground docs]: /components/sensor.wunderground/
-[sensor.zha docs]: /components/sensor.zha/
-[shopping_list docs]: /components/shopping_list/
-[smappee docs]: /components/smappee/
-[switch.knx docs]: /components/switch.knx/
-[switch.rainmachine docs]: /components/switch.rainmachine/
-[switch.smappee docs]: /components/switch.smappee/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[tahoma docs]: /components/tahoma/
-[telegram_bot docs]: /components/telegram_bot/
-[usps docs]: /components/usps/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[vera docs]: /components/vera/
-[weather.buienradar docs]: /components/weather.buienradar/
-[weblink docs]: /components/weblink/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
-[zha docs]: /components/zha/
-[#12635]: https://github.com/home-assistant/home-assistant/pull/12635
-[#12645]: https://github.com/home-assistant/home-assistant/pull/12645
-[#12657]: https://github.com/home-assistant/home-assistant/pull/12657
-[#12679]: https://github.com/home-assistant/home-assistant/pull/12679
-[#12685]: https://github.com/home-assistant/home-assistant/pull/12685
-[#12687]: https://github.com/home-assistant/home-assistant/pull/12687
-[#12691]: https://github.com/home-assistant/home-assistant/pull/12691
-[#12711]: https://github.com/home-assistant/home-assistant/pull/12711
-[#12715]: https://github.com/home-assistant/home-assistant/pull/12715
-[#12719]: https://github.com/home-assistant/home-assistant/pull/12719
-[#12726]: https://github.com/home-assistant/home-assistant/pull/12726
-[#12729]: https://github.com/home-assistant/home-assistant/pull/12729
-[#12737]: https://github.com/home-assistant/home-assistant/pull/12737
-[@ChristianKuehnel]: https://github.com/ChristianKuehnel
-[@NovapaX]: https://github.com/NovapaX
-[@OttoWinter]: https://github.com/OttoWinter
-[@amelchio]: https://github.com/amelchio
-[@aronsky]: https://github.com/aronsky
-[@bakedraccoon]: https://github.com/bakedraccoon
-[@balloob]: https://github.com/balloob
-[@jesserockz]: https://github.com/jesserockz
-[@kellerza]: https://github.com/kellerza
-[@pvizeli]: https://github.com/pvizeli
-[@scarface-4711]: https://github.com/scarface-4711
-[@tumik]: https://github.com/tumik
-[@fanthos]: https://github.com/fanthos
-[@PhilRW]: https://github.com/PhilRW
-[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
-[deconz docs]: /components/deconz/
-[light.iglo docs]: /components/light.iglo/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.denonavr docs]: /components/media_player.denonavr/
-[mysensors docs]: /components/mysensors/
-[remote.harmony docs]: /components/remote.harmony/
-[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
-[tahoma docs]: /components/tahoma/
-[vacuum.roomba docs]: /components/vacuum.roomba/
-[zha docs]: /components/zha/
-[#12759]: https://github.com/home-assistant/home-assistant/pull/12759
-[#12762]: https://github.com/home-assistant/home-assistant/pull/12762
-[#12764]: https://github.com/home-assistant/home-assistant/pull/12764
-[#12767]: https://github.com/home-assistant/home-assistant/pull/12767
-[#12769]: https://github.com/home-assistant/home-assistant/pull/12769
-[#12789]: https://github.com/home-assistant/home-assistant/pull/12789
-[#12790]: https://github.com/home-assistant/home-assistant/pull/12790
-[#12796]: https://github.com/home-assistant/home-assistant/pull/12796
-[#12799]: https://github.com/home-assistant/home-assistant/pull/12799
-[@ChristianKuehnel]: https://github.com/ChristianKuehnel
-[@amelchio]: https://github.com/amelchio
-[@bachya]: https://github.com/bachya
-[@basschipper]: https://github.com/basschipper
-[@happyleavesaoc]: https://github.com/happyleavesaoc
-[@ryanm101]: https://github.com/ryanm101
-[@uchagani]: https://github.com/uchagani
-[binary_sensor.rfxtrx docs]: /components/binary_sensor.rfxtrx/
-[bmw_connected_drive docs]: /components/bmw_connected_drive/
-[logbook docs]: /components/logbook/
-[media_player.plex docs]: /components/media_player.plex/
-[media_player.samsungtv docs]: /components/media_player.samsungtv/
-[media_player.sonos docs]: /components/media_player.sonos/
-[sensor.fedex docs]: /components/sensor.fedex/
-[sensor.pollen docs]: /components/sensor.pollen/
-[#12810]: https://github.com/home-assistant/home-assistant/pull/12810
-[#12837]: https://github.com/home-assistant/home-assistant/pull/12837
-[#12840]: https://github.com/home-assistant/home-assistant/pull/12840
-[#12845]: https://github.com/home-assistant/home-assistant/pull/12845
-[@andrey-git]: https://github.com/andrey-git
-[@balloob]: https://github.com/balloob
-[@kellerza]: https://github.com/kellerza
-[climate.sensibo docs]: /components/climate.sensibo/
-[cloud docs]: /components/cloud/
-[hue docs]: /components/hue/
\ No newline at end of file
diff --git a/source/_posts/2018-03-09-release-65.markdown b/source/_posts/2018-03-09-release-65.markdown
deleted file mode 100644
index ebf590affd..0000000000
--- a/source/_posts/2018-03-09-release-65.markdown
+++ /dev/null
@@ -1,757 +0,0 @@
----
-layout: post
-title: "0.65: Rename entities, new filter sensor, UpCloud and Channels"
-description: "A new Home Assistant release full of amazing new features. Rename entities without a restart, filter out anomalies or apply other filters to data, improved HomeKit support."
-date: 2018-03-09 00:01:00
-date_formatted: "March 9, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Release-Notes
-og_image: /images/blog/2018-03-0.65/entity-registry-name.gif
----
-
-
-
-Release 0.65 has arrived and oh boy, is it awesome. First off, in case you have missed the previous release notes and [announcements](/blog/2017/10/06/deprecating-python-3.4-support/): **Starting with this release, Home Assistant has dropped support for Python 3.4. The minimum supported version is now Python 3.5.3.** If you are on Hass.io or Docker, you'll automatically be running the latest and greatest. If you're on an older Hassbian installation or did your own Linux setup you'll need to upgrade to at least Python 3.5.3.
-
-## {% linkable_title Naming entities %}
-
-With the introduction of the entity registry in 0.63, Home Assistant is making sure that the same devices always receive the same entity IDs. This release is taking it a step further by allowing users to change the name of a device from the frontend. Changing the name will be instantly applied and overrides whatever name the device is given by the integration. If you want to switch back to the name from the integration, set the name to blank.
-
-_This feature is, just like the entity registry, only available for integrations that provide unique IDs for their entities. Adding this to each integration is still a work in progress._
-
-
- The new entity registry settings page in action.
-
- Graph showing both the input sensor and the output of the filter sensor.
-
- Have conversations with Home Assistant via the conversation component.
-
-Diagram of the new release schedule
-
-
-This is the first release with our new release schedule. During the extra week we had a total of 4 beta releases with a total of [26 fixes](https://github.com/home-assistant/home-assistant/milestone/128?closed=1). So this should be the most stable release yet!
-
-It's also a release that is full of goodies. 80 people contributed over 223 fixes, improvements and new integrations during the last 2 weeks of this release 😎 I want to highlight the work of two people who are doing an amazing job: [@NovapaX] has been doing a great job triaging and fixing weird quirks and bugs in the frontend. And I want to give a shout out to [@armills] who has enabled backend translations. This means that a bunch of things that did not have translations yet, will now soon be translatable. We're planning some cool things with this!
-
-A quick note if you are using Philips Hue and a Hue custom component: it will no longer work due to the internal changes to the Hue platform. Remove the custom component to ensure that your Hue lights keep working.
-
-## New Platforms
-
-- Add new platform for VeSync switches ([@markperdue] - [#13000]) ([switch.vesync docs]) (new-platform)
-- HomeKit Restructure (new config options) ([@cdce8p] - [#12997]) ([homekit docs]) (breaking change) (new-platform)
-- Added cover.group platform (replaces #12303) ([@cdce8p] - [#12692]) ([cover.group docs]) (new-platform)
-- Add extra sensors for BMW ConnectedDrive ([@gerard33] - [#12591]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (new-platform)
-- Homekit: New supported devices ([@cdce8p] - [#13244]) ([homekit docs]) (new-platform)
-- Adding Foobot device sensor ([@reefab] - [#12417]) ([sensor.foobot docs]) (new-platform)
-- Added Stride notification component ([@BioSehnsucht] - [#13221]) ([notify docs]) (new-platform)
-- Xiaomi MiIO Sensor: Xiaomi Air Quality Monitor (PM2.5) integration ([@syssi] - [#13264]) ([sensor.xiaomi_miio docs]) (new-platform)
-- Add initial support fo HomematicIP components ([@mxworm] - [#12761]) ([homematicip docs]) ([sensor.homematicip docs]) (new-platform)
-- Support for security systems controlled by IFTTT ([@maxclaey] - [#12975]) ([alarm_control_panel.ifttt docs]) (new-platform)
-- Zigbee fan ([@igorbernstein2] - [#12289]) ([zha docs]) ([fan.zha docs]) (new-platform)
-- Adding a discoverable Samsung Syncthru Printer sensor platform ([@nielstron] - [#13134]) ([sensor.syncthru docs]) (new-platform)
-- Add trafikverket_weatherstation sensor platform ([@Qxlkdr] - [#12115]) ([sensor.trafikverket_weatherstation docs]) (new-platform)
-- Security fix & lock for HomeMatic ([@PH89] - [#11980]) ([homematic docs]) ([lock docs]) ([lock.homematic docs]) (breaking change) (new-platform)
-
-## {% linkable_title Release 0.66.1 - April 1 %}
-
-- Update frontend to fix climate and chart issues ([@NovapaX] & [@c727])
-- Fix mqtt_json color commands ([@armills] - [#13617]) ([light.mqtt_json docs])
-- Add pincode fallback ([@cdce8p] - [#13587]) ([homekit docs])
-- Fix mysensors sensor type lookup ([@MartinHjelmare] - [#13574]) ([sensor.mysensors docs])
-
-## {% linkable_title If you need help... %}
-
-...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
-
-## {% linkable_title Reporting Issues %}
-
-Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
-
-
-## Breaking Changes
-
-- Refactor Hue: If you specify a bridge in your config, the `host` key is now required and needs to be a valid ip address. Option `allow_in_emulated_hue` has been removed. Exclude the lights via the emulated hue config. Due to the internal changes of how the Hue integration works, any Hue custom component will no longer work. ([@balloob] - [#13043]) ([hue docs]) ([light.hue docs]) (breaking change)
-- Z-Wave: In version 0.47, the opt-in `new_entity_ids` configuration was added to Z-Wave to smooth the transition through the change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will already be stored in the Entity Registry and no changes are required. If not, [entity IDs can now be manually configured using the Entity Registry](/docs/configuration/entity-registry/) if necessary. ([@armills] - [#12652]) ([zwave docs]) (breaking change)
-- Spotcrime sensor: This update changes the sensor to require a user supplied API key as a configuration entry. The default key has been removed from the Spotcrime package and has also been modified to accept a user supplied API key.([@jcconnell] - [#12926]) ([sensor.spotcrime docs]) (breaking change)
-- Smappee sensor: Fixed SI units for current consumption. Total consumption should be in kWh. not kW. ([@vandenberghev] - [#13190]) ([sensor.smappee docs]) (breaking change)
-- System monitor sensor: Used and available swap space reported by the system monitor component is now measured in MiB instead of GiB. ([@DanNixon] - [#13148]) ([sensor.systemmonitor docs]) (breaking change)
-- HomeKit: The `pincode` parameter is deprecated, since the `HomeKit` component will now generate one for you and display it as a persistence notification during setup. Additionally the default `port` changed to `51827` to avoid potential conflicts with `homebridge`. Lastly to fix a major bug, we needed to change the way accessory ids are generated. This means that in turn all previous accessory settings will need to be repeated. To avoid future conflicts, it is highly recommended to remove the `Home Assistant Bridge` from the `Home` app and repeat the setup process. ([HomeKit Setup](/components/homekit/#setup)) ([@cdce8p] - [#12997]) ([homekit docs]) (breaking change) (new-platform)
-- Tibber: The name and the entity id for the Tibber sensor will now be the same as the nickname from the app. Default nick name is the address. So if you have not changed the nickname in the app, everything should be as before. ([@clementhk] - [#13231]) ([sensor.tibber docs]) (breaking change)
-- Darsky sensor: Fix the incorrect unit of measurement for the 'Precip Intensity' and 'Daily Max Precip Intensity' for IS units according to the dark sky api documentation.([@cgtobi] - [#13415]) ([sensor.darksky docs]) (breaking change)
-- HomeMatic: Locks are now under the lock component ([@PH89] - [#11980]) ([homematic docs]) ([lock docs]) ([lock.homematic docs]) (breaking change) (new-platform)
-
-## All changes
-
-- New lazytox.py script ([@kellerza] - [#12862])
-- Update netdisco to 1.3.0 ([@balloob] - [#13007])
-- remove rounding of temperature reading ([@hthiery] - [#13018]) ([sensor.lacrosse docs])
-- Make lazytox script executable ([@OttoWinter] - [#13040])
-- python-miio version bumped. ([@syssi] - [#13055]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
-- Glances Docker Sensors ([@timmo001] - [#13026]) ([sensor.glances docs])
-- Script/lint, Lazytox: Fix issue to ignore delete files ([@cdce8p] - [#13051])
-- Sensor template don't exit early on TemplateError ([@OttoWinter] - [#13041]) ([sensor.template docs])
-- Better errors for unknown secrets ([@kellerza] - [#13072])
-- Remove Z-Wave old/new entity_id attributes ([@armills] - [#12652]) ([zwave docs]) (breaking change)
-- Make Sensibo climate registry_entity compliant ([@andrey-git] - [#13086]) ([climate.sensibo docs])
-- Rename homeassistant.util.async to .async_ ([@smurfix] - [#13088])
-- Config flow translations ([@armills] - [#13066])
-- Lint script tweaks ([@armills] - [#13093])
-- asyncio.ensure_future Python 3.5 ([@OttoWinter] - [#13141]) ([spc docs])
-- Upgrade aiohttp to 3.0.7 ([@fabaff] - [#13119])
-- Upgrade astral to 1.6 ([@fabaff] - [#13120])
-- fix: Support different JointSpace API versions ([@FezVrasta] - [#13084]) ([media_player.philips_js docs])
-- update to async/await ([@perosb] - [#13137]) ([zha docs]) ([light.zha docs])
-- Upgrade mypy to 0.570 ([@fabaff] - [#13128])
-- Upgrade TwitterAPI to 2.4.10 ([@fabaff] - [#13126]) ([notify docs])
-- Upgrade youtube_dl to 2018.03.10 ([@fabaff] - [#13124]) ([media_extractor docs])
-- Upgrade zeroconf to 0.20.0 ([@fabaff] - [#13123]) ([zeroconf docs])
-- Upgrade schiene to 0.22 ([@fabaff] - [#13121]) ([sensor.deutsche_bahn docs])
-- Remove crazy JSON encoding things that are no longer used ([@balloob] - [#13029]) ([http docs]) ([websocket_api docs])
-- Disable Monkey Patch for 3.6.3+ ([@OttoWinter] - [#13150])
-- Upgrade Sphinx to 1.7.1 ([@fabaff] - [#13127])
-- upgrade tibber libary to 0.4.0 to use aiohttp 3.0 ([@danielhiversen] - [#13164]) ([sensor.tibber docs])
-- Change iglo port to cv.port validator ([@jesserockz] - [#13163]) ([light.iglo docs])
-- deConz rewrite to use async await syntax ([@Kane610] - [#13151]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([scene.deconz docs]) ([sensor.deconz docs])
-- Upgrade holidays to 0.9.4 ([@OttoWinter] - [#13167]) ([binary_sensor.workday docs])
-- upcloud: Provide unique ID for server entities ([@scop] - [#13181]) ([upcloud docs])
-- Added IPAreaThermostat and an exception-list for HM_IGNORE_DISCOVERY_NODE ([@a-wolter] - [#13171]) ([homematic docs]) ([sensor.homematic docs])
-- Improve MQTT failed connection error message ([@OttoWinter] - [#13184]) ([mqtt docs])
-- Upgrade pytest to 3.4.2 ([@OttoWinter] - [#13169])
-- Channels clean ups ([@maddox] - [#12967]) ([media_player.channels docs])
-- Fix freegeoip ([@pvizeli] - [#13193])
-- Python Spotcrime sensor requires API key, fixes include/exclude ([@jcconnell] - [#12926]) ([sensor.spotcrime docs]) (breaking change)
-- Add new platform for VeSync switches ([@markperdue] - [#13000]) ([switch.vesync docs]) (new-platform)
-- Fixed SI units for current consumption ([@vandenberghev] - [#13190]) ([sensor.smappee docs]) (breaking change)
-- Report swap in MiB ([@DanNixon] - [#13148]) ([sensor.systemmonitor docs]) (breaking change)
-- Fix history API ([@balloob] - [#13214]) ([history docs])
-- Add notifications to downloader.py ([@engrbm87] - [#12961]) ([downloader docs])
-- HomeKit Restructure (new config options) ([@cdce8p] - [#12997]) ([homekit docs]) (breaking change) (new-platform)
-- deCONZ - Add support for consumption and power sensors ([@Kane610] - [#13218]) ([deconz docs]) ([binary_sensor.deconz docs]) ([sensor.deconz docs])
-- Change Hass.io icon to home-assistant ([@c727] - [#13230]) ([hassio docs])
-- Add docstring ([@fabaff] - [#13232]) ([sensor.crimereports docs])
-- Python 3.5 adjustments ([@OttoWinter] - [#13173]) ([mysensors docs])
-- Added cover.group platform (replaces #12303) ([@cdce8p] - [#12692]) ([cover.group docs]) (new-platform)
-- Tibber use appNickname as name ([@clementhk] - [#13231]) ([sensor.tibber docs]) (breaking change)
-- media_content_type attribute display fix ([@kuzin2006] - [#13204]) ([media_player.kodi docs])
-- Edimax component reports wrong power values ([@andreipop2005] - [#13011]) ([switch.edimax docs])
-- myStrom: Add RGB support to Wifi bulbs ([@the-glu] - [#13194]) ([light.mystrom docs])
-- Fix logbook JSON serialize issue ([@balloob] - [#13229]) ([logbook docs])
-- Try to fix caldav ([@maxlaverse] - [#13236]) ([calendar.caldav docs])
-- Cleanup Sonos platform setup ([@amelchio] - [#13225]) ([media_player.sonos docs])
-- Fix 'dict' object has no attribute 'strftime' ([@Juggels] - [#13215]) ([calendar.todoist docs])
-- Fix aiohttp deprecation warnings ([@balloob] - [#13240])
-- Add extra sensors for BMW ConnectedDrive ([@gerard33] - [#12591]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (new-platform)
-- Homekit: New supported devices ([@cdce8p] - [#13244]) ([homekit docs]) (new-platform)
-- Adding Foobot device sensor ([@reefab] - [#12417]) ([sensor.foobot docs]) (new-platform)
-- Fix for not setting up the camera if it is offline during setup phase ([@karlkar] - [#13082]) ([camera.onvif docs])
-- Added Stride notification component ([@BioSehnsucht] - [#13221]) ([notify docs]) (new-platform)
-- Homekit: Use util functions for unit conversion ([@cdce8p] - [#13253]) ([homekit docs])
-- Use the first, not the last volume controller when multiple are available on songpal ([@rytilahti] - [#13222]) ([media_player.songpal docs])
-- Xiaomi MiIO Switch: Power Strip support improved ([@syssi] - [#12917]) ([switch.xiaomi_miio docs])
-- Xiaomi MiIO light: Philips Eyecare Smart Lamp 2 integration ([@syssi] - [#12883]) ([light.xiaomi_miio docs])
-- Fix guide link in CONTRIBUTING.md ([@JensTimmerman] - [#13272])
-- Xiaomi MiIO Remote: Unique id added ([@syssi] - [#13266]) ([remote.xiaomi_miio docs])
-- Xiaomi MiIO Sensor: Xiaomi Air Quality Monitor (PM2.5) integration ([@syssi] - [#13264]) ([sensor.xiaomi_miio docs]) (new-platform)
-- Refactor Hue: phue -> aiohue ([@balloob] - [#13043]) ([hue docs]) ([light.hue docs]) (breaking change)
-- Unused xiaomi miio sensor method removed ([@syssi] - [#13281]) ([sensor.xiaomi_miio docs])
-- Changed to async/await ([@thrawnarn] - [#13246]) ([media_player.bluesound docs])
-- Python 3.5 async with ([@OttoWinter] - [#13283])
-- Fix WUnderground duplicate entity ids ([@OttoWinter] - [#13285]) ([sensor.wunderground docs])
-- Upgrade aiohttp to 3.0.9 ([@fabaff] - [#13288])
-- Upgrade aiohttp_cors to 0.7.0 ([@fabaff] - [#13289]) ([http docs])
-- Upgrade sqlalchemy to 1.2.5 ([@fabaff] - [#13292]) ([sensor.sql docs])
-- Upgrade TwitterAPI to 2.5.0 ([@fabaff] - [#13287]) ([notify docs])
-- Upgrade numpy to 1.14.2 ([@fabaff] - [#13291]) ([binary_sensor.trend docs]) ([image_processing.opencv docs])
-- Upgrade python-telegram-bot to 10.0.1 ([@fabaff] - [#13294]) ([telegram_bot docs])
-- Upgrade python-forecastio to 1.4.0 ([@cgtobi] - [#13282]) ([weather.darksky docs])
-- Delete .gitmodules ([@pvizeli] - [#13295])
-- Update to latest python-nest ([@cburgess] - [#12590]) ([nest docs])
-- Upgrade async_timeout to 2.0.1 ([@fabaff] - [#13290])
-- Add initial support fo HomematicIP components ([@mxworm] - [#12761]) ([homematicip docs]) ([sensor.homematicip docs]) (new-platform)
-- Added Time based SMA to Filter Sensor ([@dgomes] - [#13104]) ([sensor.filter docs])
-- Support for security systems controlled by IFTTT ([@maxclaey] - [#12975]) ([alarm_control_panel.ifttt docs]) (new-platform)
-- Add ecobee fan mode ([@uchagani] - [#12732]) ([ecobee docs]) ([climate.ecobee docs])
-- Zigbee fan ([@igorbernstein2] - [#12289]) ([zha docs]) ([fan.zha docs]) (new-platform)
-- Update plex.py ([@chronm] - [#12157]) ([sensor.plex docs])
-- Support MQTT Lock discovery ([@molobrakos] - [#13303]) ([mqtt docs]) ([lock.mqtt docs])
-- Adding a discoverable Samsung Syncthru Printer sensor platform ([@nielstron] - [#13134]) ([sensor.syncthru docs]) (new-platform)
-- Use hue/sat as internal light color interface ([@armills] - [#11288]) ([light docs])
-- Superfluous None ([@dgomes] - [#13326]) ([sensor.filter docs])
-- pytest 3.4.0 cache gitignore ([@OttoWinter] - [#13308])
-- Add trafikverket_weatherstation sensor platform ([@Qxlkdr] - [#12115]) ([sensor.trafikverket_weatherstation docs]) (new-platform)
-- zha: catch the exception from bellows if a device isn't available. ([@perosb] - [#13314]) ([light.zha docs]) ([switch.zha docs])
-- Plex unavailable client cleanup ([@ryanm101] - [#13156]) ([media_player.plex docs])
-- Perform check_config service in current process ([@kellerza] - [#13017])
-- Added switch for DoorBird second relay ([@sjvc] - [#13339]) ([doorbird docs]) ([switch.doorbird docs])
-- Add min and max price as attribute for Tibber sensor ([@danielhiversen] - [#13313]) ([sensor.tibber docs])
-- Bugfix: Zwave set_config_parameter failed when config list contained int ([@turbokongen] - [#13301]) ([zwave docs])
-- Update pyhomematic to 0.1.40 ([@danielperna84] - [#13354]) ([homematic docs])
-- Fix mysensors light turn on hs color ([@MartinHjelmare] - [#13349]) ([light.mysensors docs])
-- Add a polling fallback for Sonos ([@amelchio] - [#13310]) ([media_player.sonos docs])
-- Fix retrieval of track URL into medi_content_id ([@ih8gates] - [#13333]) ([media_player.spotify docs])
-- Homekit Bugfix: Use get instead of indexing ([@maxclaey] - [#13353]) ([homekit docs])
-- Configuration options for IFTTT alarm control panel ([@maxclaey] - [#13352]) ([alarm_control_panel.ifttt docs])
-- Add the possibility to filter on line(s) in Västtrafik Public Transport sensor ([@ThomasSvedberg] - [#13317]) ([sensor.vasttrafik docs])
-- Fix mysensors RGBW ([@MartinHjelmare] - [#13364]) ([light.mysensors docs])
-- Add watt to mysensors switch attributes ([@MartinHjelmare] - [#13370])
-- Mediaroom async ([@dgomes] - [#13321]) ([media_player.mediaroom docs])
-- Add language parameter to darksky sensor ([@cgtobi] - [#13297]) ([sensor.darksky docs]) ([weather.darksky docs])
-- Fixing Egardia 'home armed' state not shown correctly. ([@jeroenterheerdt] - [#13335])
-- Include all config flow translations with backend translations ([@balloob] - [#13394])
-- Avoid breaking change for BMW ConnectedDrive sensors in #12591 ([@gerard33] - [#13380]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs])
-- Support setting icon when configuring MQTT entity ([@molobrakos] - [#13304]) ([sensor.mqtt docs]) ([switch.mqtt docs])
-- Enhance mysensors sensor units and icons ([@MartinHjelmare] - [#13365]) ([sensor.mysensors docs])
-- Fix incorrect unit of measurement for precip_intensity. ([@cgtobi] - [#13415]) ([sensor.darksky docs]) (breaking change)
-- Fix Sonos playing Sveriges Radio ([@amelchio] - [#13401]) ([media_player.sonos docs])
-- Cache LaMetric devices for offline use ([@PhilRW] - [#13379])
-- Enhance mysensors binary sensor device classes ([@MartinHjelmare] - [#13367]) ([binary_sensor.mysensors docs])
-- Switched to async/await. Bumped pyxeoma version ([@jeradM] - [#13404]) ([camera.xeoma docs])
-- Added default return value for HS_Color ([@cdce8p] - [#13395]) ([homekit docs])
-- Hue: Use the currently active color mode ([@armills] - [#13376]) ([light docs]) ([light.hue docs])
-- Cleanup homematicip_cloud ([@mxworm] - [#13356]) ([homematicip_cloud docs]) ([sensor.homematicip_cloud docs])
-- Add send sticker service to telegram bot ([@syssi] - [#13387]) ([telegram_bot docs])
-- Google assistant sync ([@balloob] - [#13392]) ([cloud docs])
-- Fix current_cover_position ([@cdce8p] - [#13135]) ([cover.template docs])
-- Switched values to downcase. ([@diminishedprime] - [#13406])
-- Cast Integration Cleanup ([@OttoWinter] - [#13275]) ([media_player.cast docs])
-- Security fix & lock for HomeMatic ([@PH89] - [#11980]) ([homematic docs]) ([lock docs]) ([lock.homematic docs]) (breaking change) (new-platform)
-- Log invalid templates in script delays ([@amelchio] - [#13423])
-- LimitlessLED hs_color fixes ([@amelchio] - [#13425]) ([light.limitlessled docs])
-- Hyperion: fix typo ([@a-andre] - [#13429]) ([light.hyperion docs])
-- HomeKit: Bugfix & improved logging ([@cdce8p] - [#13431]) ([homekit docs])
-- Improve detection of entity names in templates ([@amelchio] - [#13432])
-- Add version bump script ([@balloob] - [#13447])
-- Add extra check for ESSID field in case there's a wired connection ([@Zepheus] - [#13459]) ([device_tracker docs])
-- Fix encoding errors in mikrotik device tracker ([@bdurrer] - [#13464]) ([device_tracker docs])
-- Hue: Convert XY to HS color if HS not present ([@balloob] - [#13465]) ([light.hue docs])
-- Fix ID (fixes #13444) ([@fabaff] - [#13471]) ([media_player.mpchc docs])
-- Upgrade aiohue and fix race condition ([@balloob] - [#13475]) ([hue docs])
-- version should contain just 'b' not 'beta' ([@balloob] - [#13476])
-- Fix Google Calendar caching when offline ([@PhilRW] - [#13375]) ([calendar.google docs])
-- Homekit: Bugfix Thermostat Fahrenheit support ([@cdce8p] - [#13477]) ([homekit docs])
-- Validate basic customize entries ([@cdce8p] - [#13478])
-- Homekit: Fix security systems ([@cdce8p] - [#13499]) ([homekit docs])
-- python-miio version bumped (Closes: 13449) ([@syssi] - [#13511]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([sensor.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
-- Fix mysensors light supported features ([@MartinHjelmare] - [#13512]) ([light.mysensors docs])
-- Fix Insteon Leak Sensor ([@teharris1] - [#13515])
-- HomeKit: Fix setting light brightness ([@cdce8p] - [#13518]) ([homekit docs])
-- Construct version pinned ([@syssi] - [#13528]) ([climate.eq3btsmart docs]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([sensor.eddystone_temperature docs]) ([sensor.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
-- Don't add Falsy items to list #13412 ([@kellerza] - [#13536])
-- Check whitelisted paths #13107 ([@kellerza] - [#13154])
-- Fix FLUX_LED error when no color is set ([@dramamoose] - [#13527]) ([light.flux_led docs])
-
-[#11288]: https://github.com/home-assistant/home-assistant/pull/11288
-[#11980]: https://github.com/home-assistant/home-assistant/pull/11980
-[#12115]: https://github.com/home-assistant/home-assistant/pull/12115
-[#12157]: https://github.com/home-assistant/home-assistant/pull/12157
-[#12289]: https://github.com/home-assistant/home-assistant/pull/12289
-[#12417]: https://github.com/home-assistant/home-assistant/pull/12417
-[#12590]: https://github.com/home-assistant/home-assistant/pull/12590
-[#12591]: https://github.com/home-assistant/home-assistant/pull/12591
-[#12652]: https://github.com/home-assistant/home-assistant/pull/12652
-[#12692]: https://github.com/home-assistant/home-assistant/pull/12692
-[#12732]: https://github.com/home-assistant/home-assistant/pull/12732
-[#12761]: https://github.com/home-assistant/home-assistant/pull/12761
-[#12862]: https://github.com/home-assistant/home-assistant/pull/12862
-[#12883]: https://github.com/home-assistant/home-assistant/pull/12883
-[#12917]: https://github.com/home-assistant/home-assistant/pull/12917
-[#12926]: https://github.com/home-assistant/home-assistant/pull/12926
-[#12961]: https://github.com/home-assistant/home-assistant/pull/12961
-[#12967]: https://github.com/home-assistant/home-assistant/pull/12967
-[#12975]: https://github.com/home-assistant/home-assistant/pull/12975
-[#12997]: https://github.com/home-assistant/home-assistant/pull/12997
-[#13000]: https://github.com/home-assistant/home-assistant/pull/13000
-[#13007]: https://github.com/home-assistant/home-assistant/pull/13007
-[#13011]: https://github.com/home-assistant/home-assistant/pull/13011
-[#13017]: https://github.com/home-assistant/home-assistant/pull/13017
-[#13018]: https://github.com/home-assistant/home-assistant/pull/13018
-[#13026]: https://github.com/home-assistant/home-assistant/pull/13026
-[#13029]: https://github.com/home-assistant/home-assistant/pull/13029
-[#13040]: https://github.com/home-assistant/home-assistant/pull/13040
-[#13041]: https://github.com/home-assistant/home-assistant/pull/13041
-[#13043]: https://github.com/home-assistant/home-assistant/pull/13043
-[#13051]: https://github.com/home-assistant/home-assistant/pull/13051
-[#13055]: https://github.com/home-assistant/home-assistant/pull/13055
-[#13066]: https://github.com/home-assistant/home-assistant/pull/13066
-[#13072]: https://github.com/home-assistant/home-assistant/pull/13072
-[#13082]: https://github.com/home-assistant/home-assistant/pull/13082
-[#13084]: https://github.com/home-assistant/home-assistant/pull/13084
-[#13086]: https://github.com/home-assistant/home-assistant/pull/13086
-[#13088]: https://github.com/home-assistant/home-assistant/pull/13088
-[#13093]: https://github.com/home-assistant/home-assistant/pull/13093
-[#13104]: https://github.com/home-assistant/home-assistant/pull/13104
-[#13119]: https://github.com/home-assistant/home-assistant/pull/13119
-[#13120]: https://github.com/home-assistant/home-assistant/pull/13120
-[#13121]: https://github.com/home-assistant/home-assistant/pull/13121
-[#13123]: https://github.com/home-assistant/home-assistant/pull/13123
-[#13124]: https://github.com/home-assistant/home-assistant/pull/13124
-[#13126]: https://github.com/home-assistant/home-assistant/pull/13126
-[#13127]: https://github.com/home-assistant/home-assistant/pull/13127
-[#13128]: https://github.com/home-assistant/home-assistant/pull/13128
-[#13134]: https://github.com/home-assistant/home-assistant/pull/13134
-[#13135]: https://github.com/home-assistant/home-assistant/pull/13135
-[#13137]: https://github.com/home-assistant/home-assistant/pull/13137
-[#13141]: https://github.com/home-assistant/home-assistant/pull/13141
-[#13148]: https://github.com/home-assistant/home-assistant/pull/13148
-[#13150]: https://github.com/home-assistant/home-assistant/pull/13150
-[#13151]: https://github.com/home-assistant/home-assistant/pull/13151
-[#13154]: https://github.com/home-assistant/home-assistant/pull/13154
-[#13156]: https://github.com/home-assistant/home-assistant/pull/13156
-[#13163]: https://github.com/home-assistant/home-assistant/pull/13163
-[#13164]: https://github.com/home-assistant/home-assistant/pull/13164
-[#13167]: https://github.com/home-assistant/home-assistant/pull/13167
-[#13169]: https://github.com/home-assistant/home-assistant/pull/13169
-[#13171]: https://github.com/home-assistant/home-assistant/pull/13171
-[#13173]: https://github.com/home-assistant/home-assistant/pull/13173
-[#13181]: https://github.com/home-assistant/home-assistant/pull/13181
-[#13184]: https://github.com/home-assistant/home-assistant/pull/13184
-[#13190]: https://github.com/home-assistant/home-assistant/pull/13190
-[#13193]: https://github.com/home-assistant/home-assistant/pull/13193
-[#13194]: https://github.com/home-assistant/home-assistant/pull/13194
-[#13204]: https://github.com/home-assistant/home-assistant/pull/13204
-[#13214]: https://github.com/home-assistant/home-assistant/pull/13214
-[#13215]: https://github.com/home-assistant/home-assistant/pull/13215
-[#13218]: https://github.com/home-assistant/home-assistant/pull/13218
-[#13221]: https://github.com/home-assistant/home-assistant/pull/13221
-[#13222]: https://github.com/home-assistant/home-assistant/pull/13222
-[#13225]: https://github.com/home-assistant/home-assistant/pull/13225
-[#13229]: https://github.com/home-assistant/home-assistant/pull/13229
-[#13230]: https://github.com/home-assistant/home-assistant/pull/13230
-[#13231]: https://github.com/home-assistant/home-assistant/pull/13231
-[#13232]: https://github.com/home-assistant/home-assistant/pull/13232
-[#13236]: https://github.com/home-assistant/home-assistant/pull/13236
-[#13240]: https://github.com/home-assistant/home-assistant/pull/13240
-[#13244]: https://github.com/home-assistant/home-assistant/pull/13244
-[#13246]: https://github.com/home-assistant/home-assistant/pull/13246
-[#13253]: https://github.com/home-assistant/home-assistant/pull/13253
-[#13264]: https://github.com/home-assistant/home-assistant/pull/13264
-[#13266]: https://github.com/home-assistant/home-assistant/pull/13266
-[#13272]: https://github.com/home-assistant/home-assistant/pull/13272
-[#13275]: https://github.com/home-assistant/home-assistant/pull/13275
-[#13281]: https://github.com/home-assistant/home-assistant/pull/13281
-[#13282]: https://github.com/home-assistant/home-assistant/pull/13282
-[#13283]: https://github.com/home-assistant/home-assistant/pull/13283
-[#13285]: https://github.com/home-assistant/home-assistant/pull/13285
-[#13287]: https://github.com/home-assistant/home-assistant/pull/13287
-[#13288]: https://github.com/home-assistant/home-assistant/pull/13288
-[#13289]: https://github.com/home-assistant/home-assistant/pull/13289
-[#13290]: https://github.com/home-assistant/home-assistant/pull/13290
-[#13291]: https://github.com/home-assistant/home-assistant/pull/13291
-[#13292]: https://github.com/home-assistant/home-assistant/pull/13292
-[#13294]: https://github.com/home-assistant/home-assistant/pull/13294
-[#13295]: https://github.com/home-assistant/home-assistant/pull/13295
-[#13297]: https://github.com/home-assistant/home-assistant/pull/13297
-[#13301]: https://github.com/home-assistant/home-assistant/pull/13301
-[#13303]: https://github.com/home-assistant/home-assistant/pull/13303
-[#13304]: https://github.com/home-assistant/home-assistant/pull/13304
-[#13308]: https://github.com/home-assistant/home-assistant/pull/13308
-[#13310]: https://github.com/home-assistant/home-assistant/pull/13310
-[#13313]: https://github.com/home-assistant/home-assistant/pull/13313
-[#13314]: https://github.com/home-assistant/home-assistant/pull/13314
-[#13317]: https://github.com/home-assistant/home-assistant/pull/13317
-[#13321]: https://github.com/home-assistant/home-assistant/pull/13321
-[#13326]: https://github.com/home-assistant/home-assistant/pull/13326
-[#13333]: https://github.com/home-assistant/home-assistant/pull/13333
-[#13335]: https://github.com/home-assistant/home-assistant/pull/13335
-[#13339]: https://github.com/home-assistant/home-assistant/pull/13339
-[#13349]: https://github.com/home-assistant/home-assistant/pull/13349
-[#13352]: https://github.com/home-assistant/home-assistant/pull/13352
-[#13353]: https://github.com/home-assistant/home-assistant/pull/13353
-[#13354]: https://github.com/home-assistant/home-assistant/pull/13354
-[#13356]: https://github.com/home-assistant/home-assistant/pull/13356
-[#13364]: https://github.com/home-assistant/home-assistant/pull/13364
-[#13365]: https://github.com/home-assistant/home-assistant/pull/13365
-[#13367]: https://github.com/home-assistant/home-assistant/pull/13367
-[#13370]: https://github.com/home-assistant/home-assistant/pull/13370
-[#13375]: https://github.com/home-assistant/home-assistant/pull/13375
-[#13376]: https://github.com/home-assistant/home-assistant/pull/13376
-[#13379]: https://github.com/home-assistant/home-assistant/pull/13379
-[#13380]: https://github.com/home-assistant/home-assistant/pull/13380
-[#13387]: https://github.com/home-assistant/home-assistant/pull/13387
-[#13392]: https://github.com/home-assistant/home-assistant/pull/13392
-[#13394]: https://github.com/home-assistant/home-assistant/pull/13394
-[#13395]: https://github.com/home-assistant/home-assistant/pull/13395
-[#13401]: https://github.com/home-assistant/home-assistant/pull/13401
-[#13404]: https://github.com/home-assistant/home-assistant/pull/13404
-[#13406]: https://github.com/home-assistant/home-assistant/pull/13406
-[#13415]: https://github.com/home-assistant/home-assistant/pull/13415
-[#13423]: https://github.com/home-assistant/home-assistant/pull/13423
-[#13425]: https://github.com/home-assistant/home-assistant/pull/13425
-[#13429]: https://github.com/home-assistant/home-assistant/pull/13429
-[#13431]: https://github.com/home-assistant/home-assistant/pull/13431
-[#13432]: https://github.com/home-assistant/home-assistant/pull/13432
-[#13447]: https://github.com/home-assistant/home-assistant/pull/13447
-[#13459]: https://github.com/home-assistant/home-assistant/pull/13459
-[#13464]: https://github.com/home-assistant/home-assistant/pull/13464
-[#13465]: https://github.com/home-assistant/home-assistant/pull/13465
-[#13471]: https://github.com/home-assistant/home-assistant/pull/13471
-[#13475]: https://github.com/home-assistant/home-assistant/pull/13475
-[#13476]: https://github.com/home-assistant/home-assistant/pull/13476
-[#13477]: https://github.com/home-assistant/home-assistant/pull/13477
-[#13478]: https://github.com/home-assistant/home-assistant/pull/13478
-[#13499]: https://github.com/home-assistant/home-assistant/pull/13499
-[#13511]: https://github.com/home-assistant/home-assistant/pull/13511
-[#13512]: https://github.com/home-assistant/home-assistant/pull/13512
-[#13515]: https://github.com/home-assistant/home-assistant/pull/13515
-[#13518]: https://github.com/home-assistant/home-assistant/pull/13518
-[#13527]: https://github.com/home-assistant/home-assistant/pull/13527
-[#13528]: https://github.com/home-assistant/home-assistant/pull/13528
-[#13536]: https://github.com/home-assistant/home-assistant/pull/13536
-[@BioSehnsucht]: https://github.com/BioSehnsucht
-[@DanNixon]: https://github.com/DanNixon
-[@FezVrasta]: https://github.com/FezVrasta
-[@JensTimmerman]: https://github.com/JensTimmerman
-[@Juggels]: https://github.com/Juggels
-[@Kane610]: https://github.com/Kane610
-[@MartinHjelmare]: https://github.com/MartinHjelmare
-[@OttoWinter]: https://github.com/OttoWinter
-[@PH89]: https://github.com/PH89
-[@PhilRW]: https://github.com/PhilRW
-[@Qxlkdr]: https://github.com/Qxlkdr
-[@ThomasSvedberg]: https://github.com/ThomasSvedberg
-[@Zepheus]: https://github.com/Zepheus
-[@a-andre]: https://github.com/a-andre
-[@a-wolter]: https://github.com/a-wolter
-[@amelchio]: https://github.com/amelchio
-[@andreipop2005]: https://github.com/andreipop2005
-[@andrey-git]: https://github.com/andrey-git
-[@armills]: https://github.com/armills
-[@balloob]: https://github.com/balloob
-[@bdurrer]: https://github.com/bdurrer
-[@c727]: https://github.com/c727
-[@cburgess]: https://github.com/cburgess
-[@cdce8p]: https://github.com/cdce8p
-[@cgtobi]: https://github.com/cgtobi
-[@chronm]: https://github.com/chronm
-[@clementhk]: https://github.com/clementhk
-[@danielhiversen]: https://github.com/danielhiversen
-[@danielperna84]: https://github.com/danielperna84
-[@dgomes]: https://github.com/dgomes
-[@diminishedprime]: https://github.com/diminishedprime
-[@dramamoose]: https://github.com/dramamoose
-[@engrbm87]: https://github.com/engrbm87
-[@fabaff]: https://github.com/fabaff
-[@gerard33]: https://github.com/gerard33
-[@hthiery]: https://github.com/hthiery
-[@igorbernstein2]: https://github.com/igorbernstein2
-[@ih8gates]: https://github.com/ih8gates
-[@jcconnell]: https://github.com/jcconnell
-[@jeradM]: https://github.com/jeradM
-[@jeroenterheerdt]: https://github.com/jeroenterheerdt
-[@jesserockz]: https://github.com/jesserockz
-[@karlkar]: https://github.com/karlkar
-[@kellerza]: https://github.com/kellerza
-[@kuzin2006]: https://github.com/kuzin2006
-[@maddox]: https://github.com/maddox
-[@markperdue]: https://github.com/markperdue
-[@maxclaey]: https://github.com/maxclaey
-[@maxlaverse]: https://github.com/maxlaverse
-[@molobrakos]: https://github.com/molobrakos
-[@mxworm]: https://github.com/mxworm
-[@nielstron]: https://github.com/nielstron
-[@perosb]: https://github.com/perosb
-[@pvizeli]: https://github.com/pvizeli
-[@reefab]: https://github.com/reefab
-[@ryanm101]: https://github.com/ryanm101
-[@rytilahti]: https://github.com/rytilahti
-[@scop]: https://github.com/scop
-[@sjvc]: https://github.com/sjvc
-[@smurfix]: https://github.com/smurfix
-[@syssi]: https://github.com/syssi
-[@teharris1]: https://github.com/teharris1
-[@the-glu]: https://github.com/the-glu
-[@thrawnarn]: https://github.com/thrawnarn
-[@timmo001]: https://github.com/timmo001
-[@turbokongen]: https://github.com/turbokongen
-[@uchagani]: https://github.com/uchagani
-[@vandenberghev]: https://github.com/vandenberghev
-[alarm_control_panel.ifttt docs]: /components/alarm_control_panel.ifttt/
-[binary_sensor.bmw_connected_drive docs]: /components/binary_sensor.bmw_connected_drive/
-[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
-[binary_sensor.mysensors docs]: /components/binary_sensor.mysensors/
-[binary_sensor.trend docs]: /components/binary_sensor.trend/
-[binary_sensor.workday docs]: /components/binary_sensor.workday/
-[bmw_connected_drive docs]: /components/bmw_connected_drive/
-[calendar.caldav docs]: /components/calendar.caldav/
-[calendar.google docs]: /components/calendar.google/
-[calendar.todoist docs]: /components/calendar.todoist/
-[camera.onvif docs]: /components/camera.onvif/
-[camera.xeoma docs]: /components/camera.xeoma/
-[climate.ecobee docs]: /components/climate.ecobee/
-[climate.eq3btsmart docs]: /components/climate.eq3btsmart/
-[climate.sensibo docs]: /components/climate.sensibo/
-[cloud docs]: /components/cloud/
-[cover.group docs]: /components/cover.group/
-[cover.template docs]: /components/cover.template/
-[deconz docs]: /components/deconz/
-[device_tracker docs]: /components/device_tracker/
-[doorbird docs]: /components/doorbird/
-[downloader docs]: /components/downloader/
-[ecobee docs]: /components/ecobee/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[fan.zha docs]: /components/fan.zha/
-[hassio docs]: /components/hassio/
-[history docs]: /components/history/
-[homekit docs]: /components/homekit/
-[homematic docs]: /components/homematic/
-[homematicip docs]: /components/homematicip/
-[homematicip_cloud docs]: /components/homematicip_cloud/
-[http docs]: /components/http/
-[hue docs]: /components/hue/
-[image_processing.opencv docs]: /components/image_processing.opencv/
-[light docs]: /components/light/
-[light.deconz docs]: /components/light.deconz/
-[light.flux_led docs]: /components/light.flux_led/
-[light.hue docs]: /components/light.hue/
-[light.hyperion docs]: /components/light.hyperion/
-[light.iglo docs]: /components/light.iglo/
-[light.limitlessled docs]: /components/light.limitlessled/
-[light.mysensors docs]: /components/light.mysensors/
-[light.mystrom docs]: /components/light.mystrom/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[light.zha docs]: /components/light.zha/
-[lock docs]: /components/lock/
-[lock.bmw_connected_drive docs]: /components/lock.bmw_connected_drive/
-[lock.homematic docs]: /components/lock.homematic/
-[lock.mqtt docs]: /components/lock.mqtt/
-[logbook docs]: /components/logbook/
-[media_extractor docs]: /components/media_extractor/
-[media_player.bluesound docs]: /components/media_player.bluesound/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.channels docs]: /components/media_player.channels/
-[media_player.kodi docs]: /components/media_player.kodi/
-[@NovapaX]: https://github.com/NovapaX
-[media_player.mediaroom docs]: /components/media_player.mediaroom/
-[media_player.mpchc docs]: /components/media_player.mpchc/
-[media_player.philips_js docs]: /components/media_player.philips_js/
-[media_player.plex docs]: /components/media_player.plex/
-[media_player.songpal docs]: /components/media_player.songpal/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.spotify docs]: /components/media_player.spotify/
-[mqtt docs]: /components/mqtt/
-[mysensors docs]: /components/mysensors/
-[nest docs]: /components/nest/
-[notify docs]: /components/notify/
-[remote.xiaomi_miio docs]: /components/remote.xiaomi_miio/
-[scene.deconz docs]: /components/scene.deconz/
-[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
-[sensor.crimereports docs]: /components/sensor.crimereports/
-[sensor.darksky docs]: /components/sensor.darksky/
-[sensor.deconz docs]: /components/sensor.deconz/
-[sensor.deutsche_bahn docs]: /components/sensor.deutsche_bahn/
-[sensor.eddystone_temperature docs]: /components/sensor.eddystone_temperature/
-[sensor.filter docs]: /components/sensor.filter/
-[sensor.foobot docs]: /components/sensor.foobot/
-[sensor.glances docs]: /components/sensor.glances/
-[sensor.homematic docs]: /components/sensor.homematic/
-[sensor.homematicip docs]: /components/sensor.homematicip/
-[sensor.homematicip_cloud docs]: /components/sensor.homematicip_cloud/
-[sensor.lacrosse docs]: /components/sensor.lacrosse/
-[sensor.mqtt docs]: /components/sensor.mqtt/
-[sensor.mysensors docs]: /components/sensor.mysensors/
-[sensor.plex docs]: /components/sensor.plex/
-[sensor.smappee docs]: /components/sensor.smappee/
-[sensor.spotcrime docs]: /components/sensor.spotcrime/
-[sensor.sql docs]: /components/sensor.sql/
-[sensor.syncthru docs]: /components/sensor.syncthru/
-[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
-[sensor.template docs]: /components/sensor.template/
-[sensor.tibber docs]: /components/sensor.tibber/
-[sensor.trafikverket_weatherstation docs]: /components/sensor.trafikverket_weatherstation/
-[sensor.vasttrafik docs]: /components/sensor.vasttrafik/
-[sensor.wunderground docs]: /components/sensor.wunderground/
-[sensor.xiaomi_miio docs]: /components/sensor.xiaomi_miio/
-[spc docs]: /components/spc/
-[switch.doorbird docs]: /components/switch.doorbird/
-[switch.edimax docs]: /components/switch.edimax/
-[switch.mqtt docs]: /components/switch.mqtt/
-[switch.vesync docs]: /components/switch.vesync/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[switch.zha docs]: /components/switch.zha/
-[telegram_bot docs]: /components/telegram_bot/
-[upcloud docs]: /components/upcloud/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[weather.darksky docs]: /components/weather.darksky/
-[websocket_api docs]: /components/websocket_api/
-[zeroconf docs]: /components/zeroconf/
-[zha docs]: /components/zha/
-[zwave docs]: /components/zwave/
-[#13574]: https://github.com/home-assistant/home-assistant/pull/13574
-[#13587]: https://github.com/home-assistant/home-assistant/pull/13587
-[#13617]: https://github.com/home-assistant/home-assistant/pull/13617
-[@MartinHjelmare]: https://github.com/MartinHjelmare
-[@armills]: https://github.com/armills
-[@cdce8p]: https://github.com/cdce8p
-[homekit docs]: /components/homekit/
-[light.mqtt_json docs]: /components/light.mqtt_json/
-[sensor.mysensors docs]: /components/sensor.mysensors/
diff --git a/source/_posts/2018-04-12-ubiquiti-and-home-assistant.markdown b/source/_posts/2018-04-12-ubiquiti-and-home-assistant.markdown
deleted file mode 100644
index 045f30c196..0000000000
--- a/source/_posts/2018-04-12-ubiquiti-and-home-assistant.markdown
+++ /dev/null
@@ -1,37 +0,0 @@
----
-layout: post
-title: "Home Assistant 🤝 Ubiquiti Networks"
-description: "Ubiquiti Networks has hired Paulus Schoutsen, the founder of Home Assistant, to support Home Assistant’s goals of making Home Assistant easier to configure for users, improving the integration with device makers and making it easier to create, maintain and evolve integrations."
-date: 2018-04-12 00:01:00
-date_formatted: "April 12, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Announcements
-og_image: /images/blog/2018-04-ubiquiti-and-home-assistant/paulus.jpg
----
-
-TL;DR: Ubiquiti Networks has hired Paulus Schoutsen, the founder of Home Assistant, to support Home Assistant’s goals of making Home Assistant easier to configure for users, improving the integration with device makers and making it easier to create, maintain and evolve integrations.
-
-Home Assistant is an open source project that thus far has been run by people in their spare time. In the last four and a half years it has grown from just me building a tiny framework with a handful of integrations to having our own operating system, over a 1000 integrations, superb performance, contributions by over 900 people, and our main Docker image has been pulled over 10 million times!
-
-Observing this growth and passionate community, Ubiquiti Networks approached us.
-
-Ubiquiti Networks currently focuses on 3 main technologies: high-capacity distributed Internet access, unified information technology, and next-gen consumer electronics for home and personal use. Their enterprise quality combined with their affordability has made them very popular among our users. They also share another passion of ours: trying to avoid clouds. Take for example their [UniFi Video] IP surveillance solution: it is a completely local hosted solution.
-
-They recognize great potential in Home Assistant becoming the defacto platform for the home: fast, open source and local. They also want to deepen the integration of Ubiquiti Networks products in Home Assistant and may even support hosting Home Assistant instances on their hardware.
-
-And so we have agreed that I (Paulus, founder Home Assistant) will join Ubiquiti Networks as a full time employee to focus on growing Home Assistant. I’ll now be able to devote my full energy to making Home Assistant easier to configure for users, improving the integration with device makers and making it easier to create, maintain and evolve integrations.
-
-Ubiquiti Networks will not acquire any ownership of Home Assistant. We will remain an independent and open source project, just improving faster than ever with the support of Ubiquiti Networks.
-
-I’m very excited about this opportunity and 2018 will be a really really great year for Home Assistant!
-
-
- Paulus Schoutsen, founder of Home Assistant, at the NYC Ubiquiti office.
-
-
-Release 0.67 is here! In case you missed [the announcement from yesterday][ann-ubiquiti], Ubiquiti is paying me to write these release notes. Ooooooh yeah. With more time on my hands I'm going to be focusing on major improvements that we have been postponing for a while, first up will be a user system.
-
-This release includes a security fix. The error log was accessible via the API without requiring authentication in previous releases. Although not a leak on it's own, combined with a faulty component that would log sensitive information to the error log could lead to that being exposed (we don't know of any component that does this). Thanks to [Matt Hamilton](https://github.com/Eriner) for disclosing this issue to us.
-
-## {% linkable_title New Platforms %}
-
-- Adds folder_watcher component ([@robmarkcole] - [#12918]) ([folder_watcher docs]) (new-platform)
-- Add FreeDNS component ([@bdurrer] - [#13526]) ([freedns docs]) (new-platform)
-- Google Maps location sharing device tracker ([@michaelarnauts] - [#12301]) ([device_tracker.google_maps docs]) (new-platform)
-- Added Waze travel time sensor ([@Myrddyn1] - [#12387]) ([sensor.waze_travel_time docs]) (new-platform)
-- Added switch component to Amcrest IP Camera. ([@adpriebe] - [#12992]) ([amcrest docs]) ([switch.amcrest docs]) (new-platform)
-- Add mastodon ([@fabaff] - [#13441]) ([notify docs]) (new-platform)
-- Tahoma switches ([@ikucuze] - [#13636]) ([tahoma docs]) ([switch.tahoma docs]) (new-platform)
-- Add support for Nanoleaf Aurora Light Panels ([@Oro] - [#13456]) ([light.nanoleaf_aurora docs]) (new-platform)
-
-## {% linkable_title Release 0.67.1 - April 17 %}
-
-- Fix Gogogate2 'available' attribute ([@dlbroadfoot] - [#13728])
-- Fix so it is possible to ignore discovered config entry handlers ([@Kane610] - [#13741])
-- Prevent vesync doing I/O in event loop ([@balloob] - [#13862]) ([switch.vesync docs])
-- Fix #13846 Double underscore in bluetooth address ([@aav7fl] - [#13884]) ([device_tracker docs])
-- Fix race condition for component loaded before listening ([@balloob] - [#13887]) ([config docs])
-- Missing property decorator added ([@syssi] - [#13889]) ([fan.xiaomi_miio docs])
-- Fix call to parent broadlink switch ([@Danielhiversen] - [#13906]) ([switch.broadlink docs])
-- Import operation modes from air humidifier ([@syssi] - [#13908]) ([fan.xiaomi_miio docs])
-- Upgrade pyqwikswitch to 0.71 ([@kellerza] - [#13920]) ([qwikswitch docs])
-- Upgrade somecomfort to 0.5.2 ([@balloob] - [#13940]) ([climate.honeywell docs])
-- Update pyhydroquebec to 2.2.2 ([@titilambert] - [#13946]) ([sensor.hydroquebec docs])
-- Update pyfido to 2.1.1 ([@titilambert] - [#13947]) ([sensor.fido docs])
-- Bumped pypollencom to 1.1.2 ([@bachya] - [#13959]) ([sensor.pollen docs])
-- Revert "Upgrade pyqwikswitch to 0.71 ([@balloob] - [#13920]) ([qwikswitch docs])
-
-## {% linkable_title If you need help... %}
-
-...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
-
-## {% linkable_title Reporting Issues %}
-
-Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
-
-
-## {% linkable_title Breaking Changes %}
-
-- Updates default Pilight port number ([@frenck] - [#13419]) ([pilight docs]) (breaking change)
-- Update to new "b2vapi" of BMW ConnectedDrive ([@ChristianKuehnel] - [#13305]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (breaking change)
-- Remove MercedesME component ([@ReneNulschDE] - [#13538]) ([device_tracker docs]) ([mercedesme docs]) ([binary_sensor.mercedesme docs]) ([sensor.mercedesme docs]) (breaking change)
-- Channel up and down for webostv ([@stephanerosi] - [#13624]) ([media_player.webostv docs]) (breaking change)
-- Add media type separation for video/movie ([@tadly] - [#13612]) (breaking change)
-- Added ENTITY_ID_FORMAT import and set entity_id in __init__ ([@timmo001] - [#13642]) ([switch.broadlink docs]) (breaking change)
-
-## {% linkable_title All changes %}
-
-- Updates default Pilight port number ([@frenck] - [#13419]) ([pilight docs]) (breaking change)
-- Upgrade mypy to 0.580 ([@fabaff] - [#13420])
-- Update to new "b2vapi" of BMW ConnectedDrive ([@ChristianKuehnel] - [#13305]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (breaking change)
-- Add code owner for Manual Alarm with MQTT Control ([@colinodell] - [#13438])
-- QNAP updates ([@colinodell] - [#13435]) ([sensor.qnap docs])
-- Xiaomi MiIO Fan: Xiaomi Air Humidifier integration ([@syssi] - [#12627]) ([fan.xiaomi_miio docs])
-- Bump songpal version, fixes lots of issues mentioned in #13022 ([@rytilahti] - [#13440]) ([media_player.songpal docs])
-- Removed the google home warning from emulated_hue ([@mf-social] - [#13436])
-- Fixing odometer to display km ([@alandtse] - [#13427]) ([sensor.tesla docs])
-- Upgrade keyring to 12.0.0 and keyrings.alt to 3.0 ([@fabaff] - [#13452])
-- Upgrade aiohttp to 3.1.0 ([@fabaff] - [#13451])
-- Qwikswitch async & updates ([@kellerza] - [#12641]) ([qwikswitch docs]) ([light.qwikswitch docs]) ([switch.qwikswitch docs])
-- Make Telnet Switch value template optional ([@DanNixon] - [#13433]) ([switch.telnet docs])
-- Update yeelightsunflower to 0.0.10 ([@lindsaymarkward] - [#13448])
-- Add more info to issue template ([@c727] - [#12955])
-- [RFC] Update issue template ([@amelchio] - [#12989])
-- Update total_connect_client to 0.17 for Honeywell L5100-WiFi Support ([@phileaton] - [#13473]) ([alarm_control_panel.totalconnect docs])
-- Upgrade python-mystrom to 0.4.2 ([@fabaff] - [#13485]) ([light.mystrom docs]) ([switch.mystrom docs])
-- New service added to control the power mode of the yeelight ([@syssi] - [#13267]) ([light.yeelight docs])
-- Upgrade slacker to 0.9.65 ([@fabaff] - [#13496]) ([notify docs])
-- Adds template function state_attr to get attribute from a state ([@Nossnevs] - [#13378])
-- Upgrade aiohttp to 3.1.1 ([@fabaff] - [#13510])
-- Update tradfri v5 ([@lwis] - [#11187]) ([tradfri docs]) ([light.tradfri docs]) ([sensor.tradfri docs])
-- Fix typos and update link (fixes #13520) ([@fabaff] - [#13529])
-- Tradfri - unique_id's and color_temp support for rgb-bulbs ([@NovapaX] - [#13531]) ([light.tradfri docs])
-- Qwikswitch async refactor & sensor ([@kellerza] - [#13509]) ([qwikswitch docs]) ([light.qwikswitch docs]) ([sensor.qwikswitch docs]) ([switch.qwikswitch docs]) (new-platform)
-- Adds folder_watcher component ([@robmarkcole] - [#12918]) ([folder_watcher docs]) (new-platform)
-- Update rflink to 0.0.37 ([@olskar] - [#12603]) ([rflink docs])
-- Added file path validity checks to file sensor ([@FrederikBolding] - [#12505]) ([sensor.file docs])
-- Allow for overriding the DoorBird push notification URL in configuration ([@Klikini] - [#13268]) ([doorbird docs])
-- Convert Hue to always use config entries ([@balloob] - [#13034]) ([hue docs])
-- Implement thermostat support for Alexa ([@trisk] - [#13340]) ([alexa docs])
-- deCONZ config entry ([@Kane610] - [#13402]) ([deconz docs])
-- Remove andrey-git from requirements monitoring ([@andrey-git] - [#13547])
-- Fix BMW device tracker toggling state if vehicle tracking is disabled ([@ChristianKuehnel] - [#12999]) ([device_tracker.bmw_connected_drive docs])
-- Xiaomi MiIO Switch: Support for the Xiaomi Chuangmi Plug V3 ([@syssi] - [#13271]) ([switch.xiaomi_miio docs])
-- Add FreeDNS component ([@bdurrer] - [#13526]) ([freedns docs]) (new-platform)
-- Update pylint to 1.8.3 ([@scop] - [#13544])
-- Google Maps location sharing device tracker ([@michaelarnauts] - [#12301]) ([device_tracker.google_maps docs]) (new-platform)
-- Check_config: Handle numbers correctly when printing config ([@hAmpzter] - [#13377])
-- Add support for Canary Flex ([@snjoetw] - [#13280]) ([canary docs]) ([sensor.canary docs])
-- Fixes #12758. Try other cameras even if one fails to initialize ([@PhracturedBlue] - [#13276]) ([amcrest docs])
-- Added HassOpenCover and HassCloseCover intents ([@tschmidty69] - [#13372]) ([conversation docs]) ([cover docs])
-- rfxtrx lib 0.22.0 ([@Danielhiversen] - [#13576]) ([rfxtrx docs])
-- xiaomi lib upgrade ([@Danielhiversen] - [#13577]) ([xiaomi_aqara docs])
-- Remove MercedesME component ([@ReneNulschDE] - [#13538]) ([device_tracker docs]) ([mercedesme docs]) ([binary_sensor.mercedesme docs]) ([sensor.mercedesme docs]) (breaking change)
-- Added Waze travel time sensor ([@Myrddyn1] - [#12387]) ([sensor.waze_travel_time docs]) (new-platform)
-- Added switch component to Amcrest IP Camera. ([@adpriebe] - [#12992]) ([amcrest docs]) ([switch.amcrest docs]) (new-platform)
-- Upgrade pyhydroquebec 2.2.1 ([@titilambert] - [#13586]) ([sensor.hydroquebec docs])
-- Add mastodon ([@fabaff] - [#13441]) ([notify docs]) (new-platform)
-- Added support for requesting RSSI values from Bluetooth devices ([@FrederikBolding] - [#12458]) ([device_tracker.bluetooth_tracker docs])
-- Fix mysensors update callback ([@MartinHjelmare] - [#13602]) ([mysensors docs])
-- Broadlink ([@Danielhiversen] - [#13585]) ([sensor.broadlink docs]) ([switch.broadlink docs])
-- Fix IMAP email message_data ([@zhaokoh] - [#13606]) ([sensor.imap_email_content docs])
-- Re-add group polling as a fallback for observation ([@lwis] - [#13613]) ([light.tradfri docs])
-- Unflake folder watcher test ([@balloob] - [#13569])
-- Make mysensors updates and platform setup async ([@MartinHjelmare] - [#13603])
-- Use 0/1 for raspberry pi cover GPIO writes rather than true/false ([@fezfox] - [#13610]) ([cover.rpi_gpio docs])
-- Fix Hue error logging ([@balloob] - [#13616]) ([hue docs])
-- Bugfix for tradfri to correctly execute Command. ([@lwis] - [#13618]) ([light.tradfri docs])
-- Hue mireds value is actually 153 not 154 ([@Skaronator] - [#13601]) ([light docs])
-- changed PyTado version ([@wmalgadey] - [#13626]) ([tado docs])
-- Upgrade py-cpuinfo to 4.0.0 ([@fabaff] - [#13629]) ([sensor.cpuspeed docs])
-- Add Switzerland ([@fabaff] - [#13630]) ([binary_sensor.workday docs])
-- Xiaomi Mi WiFi Repeater 2 integration as device tracker ([@syssi] - [#13521])
-- Upgrade youtube_dl to 2018.04.03 ([@fabaff] - [#13647]) ([media_extractor docs])
-- Update plex.py ([@chronm] - [#13659]) ([sensor.plex docs])
-- Always enable config entries & remove config_entry_example ([@balloob] - [#13663]) ([config docs])
-- Add missing service docs for hs_color ([@armills] - [#13667])
-- Add regex functions as templating helpers ([@mountainsandcode] - [#13631])
-- Channel up and down for webostv ([@stephanerosi] - [#13624]) ([media_player.webostv docs]) (breaking change)
-- Added headers configuration variable to notify.rest component ([@5LICK] - [#13674]) ([notify docs])
-- Spelling fixes ([@scop] - [#13681]) ([device_tracker docs]) ([smappee docs]) ([alarm_control_panel.ifttt docs]) ([climate.nest docs]) ([remote.xiaomi_miio docs])
-- Xiaomi MiIO Light: White Philips Candle Light support ([@syssi] - [#13682]) ([light.xiaomi_miio docs])
-- Bugfixes HomeKit covers, lights ([@cdce8p] - [#13689]) ([homekit docs])
-- Minor style changes, cleanup ([@cdce8p] - [#13654]) ([homekit docs])
-- Bugfix: Zwave Print_node to logfile instead of console ([@turbokongen] - [#13302]) ([zwave docs])
-- Update HAP-python to 1.1.8 ([@cdce8p] - [#13563]) ([homekit docs])
-- Update ha-philips_js to 0.0.3 ([@danielperna84] - [#13702]) ([media_player.philips_js docs])
-- Coverage & Codeowners ([@kellerza] - [#13700])
-- Bump insteonplm to 0.8.6 to fix sensor message handling ([@teharris1] - [#13691]) ([insteon_plm docs])
-- Fix asuswrt ap mode failure ([@shuaiger] - [#13693]) ([device_tracker docs])
-- Support color temperature in Homekit ([@morberg] - [#13658]) ([homekit docs])
-- Remove unused CONF_WATCHERS ([@robmarkcole] - [#13678]) ([folder_watcher docs])
-- Add media type separation for video/movie ([@tadly] - [#13612]) (breaking change)
-- Adding configration to disable ip address as a requirement Fixes: #13399 ([@PlanetJ] - [#13692]) ([device_tracker docs])
-- Tahoma switches ([@ikucuze] - [#13636]) ([tahoma docs]) ([switch.tahoma docs]) (new-platform)
-- Send XY color for non-osram hue bulbs ([@armills] - [#13665]) ([light.hue docs])
-- Update AbodePy version to 0.12.3 ([@MisterWil] - [#13709]) ([abode docs])
-- Enable autodiscovery for mqtt cameras ([@jmtatsch] - [#13697]) ([mqtt docs]) ([camera.mqtt docs])
-- Added ENTITY_ID_FORMAT import and set entity_id in __init__ ([@timmo001] - [#13642]) ([switch.broadlink docs]) (breaking change)
-- Fix #10175 ([@pschmitt] - [#13713]) ([media_player.liveboxplaytv docs])
-- Add support for Nanoleaf Aurora Light Panels ([@Oro] - [#13456]) ([light.nanoleaf_aurora docs]) (new-platform)
-- Added gogogate2 cover ([@dlbroadfoot] - [#13467])
-- Remove vendor lookup for mac addresses ([@balloob] - [#13788]) ([device_tracker docs])
-- iglo hs color fix ([@armills] - [#13808]) ([light.iglo docs])
-- Fix too green color conversion ([@amelchio] - [#13828])
-- Rename from aurora light to nanoleaf_aurora ([@Oro] - [#13831]) ([light.nanoleaf_aurora docs])
-- Channel up/down for LiveTV and next/previous for other apps ([@stephanerosi] - [#13829]) ([media_player.webostv docs])
-- Add authentication to error log endpoint ([@balloob] - [#13836]) ([api docs])
-
-[#11187]: https://github.com/home-assistant/home-assistant/pull/11187
-[#12301]: https://github.com/home-assistant/home-assistant/pull/12301
-[#12387]: https://github.com/home-assistant/home-assistant/pull/12387
-[#12458]: https://github.com/home-assistant/home-assistant/pull/12458
-[#12505]: https://github.com/home-assistant/home-assistant/pull/12505
-[#12603]: https://github.com/home-assistant/home-assistant/pull/12603
-[#12627]: https://github.com/home-assistant/home-assistant/pull/12627
-[#12641]: https://github.com/home-assistant/home-assistant/pull/12641
-[#12918]: https://github.com/home-assistant/home-assistant/pull/12918
-[#12955]: https://github.com/home-assistant/home-assistant/pull/12955
-[#12989]: https://github.com/home-assistant/home-assistant/pull/12989
-[#12992]: https://github.com/home-assistant/home-assistant/pull/12992
-[#12999]: https://github.com/home-assistant/home-assistant/pull/12999
-[#13034]: https://github.com/home-assistant/home-assistant/pull/13034
-[#13267]: https://github.com/home-assistant/home-assistant/pull/13267
-[#13268]: https://github.com/home-assistant/home-assistant/pull/13268
-[#13271]: https://github.com/home-assistant/home-assistant/pull/13271
-[#13276]: https://github.com/home-assistant/home-assistant/pull/13276
-[#13280]: https://github.com/home-assistant/home-assistant/pull/13280
-[#13302]: https://github.com/home-assistant/home-assistant/pull/13302
-[#13305]: https://github.com/home-assistant/home-assistant/pull/13305
-[#13340]: https://github.com/home-assistant/home-assistant/pull/13340
-[#13372]: https://github.com/home-assistant/home-assistant/pull/13372
-[#13377]: https://github.com/home-assistant/home-assistant/pull/13377
-[#13378]: https://github.com/home-assistant/home-assistant/pull/13378
-[#13402]: https://github.com/home-assistant/home-assistant/pull/13402
-[#13419]: https://github.com/home-assistant/home-assistant/pull/13419
-[#13420]: https://github.com/home-assistant/home-assistant/pull/13420
-[#13427]: https://github.com/home-assistant/home-assistant/pull/13427
-[#13433]: https://github.com/home-assistant/home-assistant/pull/13433
-[#13435]: https://github.com/home-assistant/home-assistant/pull/13435
-[#13436]: https://github.com/home-assistant/home-assistant/pull/13436
-[#13438]: https://github.com/home-assistant/home-assistant/pull/13438
-[#13440]: https://github.com/home-assistant/home-assistant/pull/13440
-[#13441]: https://github.com/home-assistant/home-assistant/pull/13441
-[#13448]: https://github.com/home-assistant/home-assistant/pull/13448
-[#13451]: https://github.com/home-assistant/home-assistant/pull/13451
-[#13452]: https://github.com/home-assistant/home-assistant/pull/13452
-[#13456]: https://github.com/home-assistant/home-assistant/pull/13456
-[#13467]: https://github.com/home-assistant/home-assistant/pull/13467
-[#13473]: https://github.com/home-assistant/home-assistant/pull/13473
-[#13485]: https://github.com/home-assistant/home-assistant/pull/13485
-[#13496]: https://github.com/home-assistant/home-assistant/pull/13496
-[#13509]: https://github.com/home-assistant/home-assistant/pull/13509
-[#13510]: https://github.com/home-assistant/home-assistant/pull/13510
-[#13521]: https://github.com/home-assistant/home-assistant/pull/13521
-[#13526]: https://github.com/home-assistant/home-assistant/pull/13526
-[#13529]: https://github.com/home-assistant/home-assistant/pull/13529
-[#13531]: https://github.com/home-assistant/home-assistant/pull/13531
-[#13538]: https://github.com/home-assistant/home-assistant/pull/13538
-[#13544]: https://github.com/home-assistant/home-assistant/pull/13544
-[#13547]: https://github.com/home-assistant/home-assistant/pull/13547
-[#13563]: https://github.com/home-assistant/home-assistant/pull/13563
-[#13569]: https://github.com/home-assistant/home-assistant/pull/13569
-[#13576]: https://github.com/home-assistant/home-assistant/pull/13576
-[#13577]: https://github.com/home-assistant/home-assistant/pull/13577
-[#13585]: https://github.com/home-assistant/home-assistant/pull/13585
-[#13586]: https://github.com/home-assistant/home-assistant/pull/13586
-[#13601]: https://github.com/home-assistant/home-assistant/pull/13601
-[#13602]: https://github.com/home-assistant/home-assistant/pull/13602
-[#13603]: https://github.com/home-assistant/home-assistant/pull/13603
-[#13606]: https://github.com/home-assistant/home-assistant/pull/13606
-[#13610]: https://github.com/home-assistant/home-assistant/pull/13610
-[#13612]: https://github.com/home-assistant/home-assistant/pull/13612
-[#13613]: https://github.com/home-assistant/home-assistant/pull/13613
-[#13616]: https://github.com/home-assistant/home-assistant/pull/13616
-[#13618]: https://github.com/home-assistant/home-assistant/pull/13618
-[#13624]: https://github.com/home-assistant/home-assistant/pull/13624
-[#13626]: https://github.com/home-assistant/home-assistant/pull/13626
-[#13629]: https://github.com/home-assistant/home-assistant/pull/13629
-[#13630]: https://github.com/home-assistant/home-assistant/pull/13630
-[#13631]: https://github.com/home-assistant/home-assistant/pull/13631
-[#13636]: https://github.com/home-assistant/home-assistant/pull/13636
-[#13642]: https://github.com/home-assistant/home-assistant/pull/13642
-[#13647]: https://github.com/home-assistant/home-assistant/pull/13647
-[#13654]: https://github.com/home-assistant/home-assistant/pull/13654
-[#13658]: https://github.com/home-assistant/home-assistant/pull/13658
-[#13659]: https://github.com/home-assistant/home-assistant/pull/13659
-[#13663]: https://github.com/home-assistant/home-assistant/pull/13663
-[#13665]: https://github.com/home-assistant/home-assistant/pull/13665
-[#13667]: https://github.com/home-assistant/home-assistant/pull/13667
-[#13674]: https://github.com/home-assistant/home-assistant/pull/13674
-[#13678]: https://github.com/home-assistant/home-assistant/pull/13678
-[#13681]: https://github.com/home-assistant/home-assistant/pull/13681
-[#13682]: https://github.com/home-assistant/home-assistant/pull/13682
-[#13689]: https://github.com/home-assistant/home-assistant/pull/13689
-[#13691]: https://github.com/home-assistant/home-assistant/pull/13691
-[#13692]: https://github.com/home-assistant/home-assistant/pull/13692
-[#13693]: https://github.com/home-assistant/home-assistant/pull/13693
-[#13697]: https://github.com/home-assistant/home-assistant/pull/13697
-[#13700]: https://github.com/home-assistant/home-assistant/pull/13700
-[#13702]: https://github.com/home-assistant/home-assistant/pull/13702
-[#13709]: https://github.com/home-assistant/home-assistant/pull/13709
-[#13713]: https://github.com/home-assistant/home-assistant/pull/13713
-[#13788]: https://github.com/home-assistant/home-assistant/pull/13788
-[#13808]: https://github.com/home-assistant/home-assistant/pull/13808
-[#13828]: https://github.com/home-assistant/home-assistant/pull/13828
-[#13829]: https://github.com/home-assistant/home-assistant/pull/13829
-[#13831]: https://github.com/home-assistant/home-assistant/pull/13831
-[#13836]: https://github.com/home-assistant/home-assistant/pull/13836
-[@5LICK]: https://github.com/5LICK
-[@ChristianKuehnel]: https://github.com/ChristianKuehnel
-[@DanNixon]: https://github.com/DanNixon
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@FrederikBolding]: https://github.com/FrederikBolding
-[@Kane610]: https://github.com/Kane610
-[@Klikini]: https://github.com/Klikini
-[@MartinHjelmare]: https://github.com/MartinHjelmare
-[@MisterWil]: https://github.com/MisterWil
-[@Myrddyn1]: https://github.com/Myrddyn1
-[@Nossnevs]: https://github.com/Nossnevs
-[@NovapaX]: https://github.com/NovapaX
-[@Oro]: https://github.com/Oro
-[@PhracturedBlue]: https://github.com/PhracturedBlue
-[@PlanetJ]: https://github.com/PlanetJ
-[@ReneNulschDE]: https://github.com/ReneNulschDE
-[@Skaronator]: https://github.com/Skaronator
-[@adpriebe]: https://github.com/adpriebe
-[@alandtse]: https://github.com/alandtse
-[@amelchio]: https://github.com/amelchio
-[@andrey-git]: https://github.com/andrey-git
-[@armills]: https://github.com/armills
-[@balloob]: https://github.com/balloob
-[@bdurrer]: https://github.com/bdurrer
-[@c727]: https://github.com/c727
-[@cdce8p]: https://github.com/cdce8p
-[@chronm]: https://github.com/chronm
-[@colinodell]: https://github.com/colinodell
-[@danielperna84]: https://github.com/danielperna84
-[@dlbroadfoot]: https://github.com/dlbroadfoot
-[@fabaff]: https://github.com/fabaff
-[@fezfox]: https://github.com/fezfox
-[@frenck]: https://github.com/frenck
-[@hAmpzter]: https://github.com/hAmpzter
-[@ikucuze]: https://github.com/ikucuze
-[@jmtatsch]: https://github.com/jmtatsch
-[@kellerza]: https://github.com/kellerza
-[@lindsaymarkward]: https://github.com/lindsaymarkward
-[@lwis]: https://github.com/lwis
-[@mf-social]: https://github.com/mf-social
-[@michaelarnauts]: https://github.com/michaelarnauts
-[@morberg]: https://github.com/morberg
-[@mountainsandcode]: https://github.com/mountainsandcode
-[@olskar]: https://github.com/olskar
-[@phileaton]: https://github.com/phileaton
-[@pschmitt]: https://github.com/pschmitt
-[@robmarkcole]: https://github.com/robmarkcole
-[@rytilahti]: https://github.com/rytilahti
-[@scop]: https://github.com/scop
-[@shuaiger]: https://github.com/shuaiger
-[@snjoetw]: https://github.com/snjoetw
-[@stephanerosi]: https://github.com/stephanerosi
-[@syssi]: https://github.com/syssi
-[@tadly]: https://github.com/tadly
-[@teharris1]: https://github.com/teharris1
-[@timmo001]: https://github.com/timmo001
-[@titilambert]: https://github.com/titilambert
-[@trisk]: https://github.com/trisk
-[@tschmidty69]: https://github.com/tschmidty69
-[@turbokongen]: https://github.com/turbokongen
-[@wmalgadey]: https://github.com/wmalgadey
-[@zhaokoh]: https://github.com/zhaokoh
-[abode docs]: /components/abode/
-[alarm_control_panel.ifttt docs]: /components/alarm_control_panel.ifttt/
-[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
-[alexa docs]: /components/alexa/
-[amcrest docs]: /components/amcrest/
-[api docs]: /components/api/
-[binary_sensor.bmw_connected_drive docs]: /components/binary_sensor.bmw_connected_drive/
-[binary_sensor.mercedesme docs]: /components/binary_sensor.mercedesme/
-[binary_sensor.workday docs]: /components/binary_sensor.workday/
-[bmw_connected_drive docs]: /components/bmw_connected_drive/
-[camera.mqtt docs]: /components/camera.mqtt/
-[canary docs]: /components/canary/
-[climate.nest docs]: /components/climate.nest/
-[config docs]: /components/config/
-[config_entry_example docs]: /components/config_entry_example/
-[conversation docs]: /components/conversation/
-[cover docs]: /components/cover/
-[cover.rpi_gpio docs]: /components/cover.rpi_gpio/
-[deconz docs]: /components/deconz/
-[device_tracker docs]: /components/device_tracker/
-[device_tracker.bluetooth_tracker docs]: /components/device_tracker.bluetooth_tracker/
-[device_tracker.bmw_connected_drive docs]: /components/device_tracker.bmw_connected_drive/
-[device_tracker.google_maps docs]: /components/device_tracker.google_maps/
-[doorbird docs]: /components/doorbird/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[folder_watcher docs]: /components/folder_watcher/
-[freedns docs]: /components/freedns/
-[homekit docs]: /components/homekit/
-[hue docs]: /components/hue/
-[insteon_plm docs]: /components/insteon_plm/
-[light docs]: /components/light/
-[light.nanoleaf_aurora docs]: /components/light.nanoleaf_aurora/
-[light.hue docs]: /components/light.hue/
-[light.iglo docs]: /components/light.iglo/
-[light.mystrom docs]: /components/light.mystrom/
-[light.nanoleaf_aurora docs]: /components/light.nanoleaf_aurora/
-[light.qwikswitch docs]: /components/light.qwikswitch/
-[light.tradfri docs]: /components/light.tradfri/
-[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
-[light.yeelight docs]: /components/light.yeelight/
-[lock.bmw_connected_drive docs]: /components/lock.bmw_connected_drive/
-[media_extractor docs]: /components/media_extractor/
-[media_player.liveboxplaytv docs]: /components/media_player.liveboxplaytv/
-[media_player.philips_js docs]: /components/media_player.philips_js/
-[media_player.songpal docs]: /components/media_player.songpal/
-[media_player.webostv docs]: /components/media_player.webostv/
-[mercedesme docs]: /components/mercedesme/
-[mqtt docs]: /components/mqtt/
-[mysensors docs]: /components/mysensors/
-[notify docs]: /components/notify/
-[pilight docs]: /components/pilight/
-[qwikswitch docs]: /components/qwikswitch/
-[remote.xiaomi_miio docs]: /components/remote.xiaomi_miio/
-[rflink docs]: /components/rflink/
-[rfxtrx docs]: /components/rfxtrx/
-[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
-[sensor.broadlink docs]: /components/sensor.broadlink/
-[sensor.canary docs]: /components/sensor.canary/
-[sensor.cpuspeed docs]: /components/sensor.cpuspeed/
-[sensor.file docs]: /components/sensor.file/
-[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
-[sensor.imap_email_content docs]: /components/sensor.imap_email_content/
-[sensor.mercedesme docs]: /components/sensor.mercedesme/
-[sensor.plex docs]: /components/sensor.plex/
-[sensor.qnap docs]: /components/sensor.qnap/
-[sensor.qwikswitch docs]: /components/sensor.qwikswitch/
-[sensor.tesla docs]: /components/sensor.tesla/
-[sensor.tradfri docs]: /components/sensor.tradfri/
-[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
-[smappee docs]: /components/smappee/
-[switch.amcrest docs]: /components/switch.amcrest/
-[switch.broadlink docs]: /components/switch.broadlink/
-[switch.mystrom docs]: /components/switch.mystrom/
-[switch.qwikswitch docs]: /components/switch.qwikswitch/
-[switch.tahoma docs]: /components/switch.tahoma/
-[switch.telnet docs]: /components/switch.telnet/
-[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
-[tado docs]: /components/tado/
-[tahoma docs]: /components/tahoma/
-[tradfri docs]: /components/tradfri/
-[folder_watcher docs]: /components/folder_watcher/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
-[zwave docs]: /components/zwave/
-[ann-ubiquiti]: /blog/2018/04/12/ubiquiti-and-home-assistant/
-[#13728]: https://github.com/home-assistant/home-assistant/pull/13728
-[#13741]: https://github.com/home-assistant/home-assistant/pull/13741
-[#13862]: https://github.com/home-assistant/home-assistant/pull/13862
-[#13884]: https://github.com/home-assistant/home-assistant/pull/13884
-[#13887]: https://github.com/home-assistant/home-assistant/pull/13887
-[#13889]: https://github.com/home-assistant/home-assistant/pull/13889
-[#13906]: https://github.com/home-assistant/home-assistant/pull/13906
-[#13908]: https://github.com/home-assistant/home-assistant/pull/13908
-[#13920]: https://github.com/home-assistant/home-assistant/pull/13920
-[#13940]: https://github.com/home-assistant/home-assistant/pull/13940
-[#13946]: https://github.com/home-assistant/home-assistant/pull/13946
-[#13947]: https://github.com/home-assistant/home-assistant/pull/13947
-[#13959]: https://github.com/home-assistant/home-assistant/pull/13959
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@Kane610]: https://github.com/Kane610
-[@aav7fl]: https://github.com/aav7fl
-[@bachya]: https://github.com/bachya
-[@balloob]: https://github.com/balloob
-[@dlbroadfoot]: https://github.com/dlbroadfoot
-[@kellerza]: https://github.com/kellerza
-[@syssi]: https://github.com/syssi
-[@titilambert]: https://github.com/titilambert
-[climate.honeywell docs]: /components/climate.honeywell/
-[config docs]: /components/config/
-[device_tracker docs]: /components/device_tracker/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[qwikswitch docs]: /components/qwikswitch/
-[sensor.fido docs]: /components/sensor.fido/
-[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
-[sensor.pollen docs]: /components/sensor.pollen/
-[switch.broadlink docs]: /components/switch.broadlink/
-[switch.vesync docs]: /components/switch.vesync/
diff --git a/source/_posts/2018-04-22-hassio-2018.markdown b/source/_posts/2018-04-22-hassio-2018.markdown
deleted file mode 100644
index 9050605355..0000000000
--- a/source/_posts/2018-04-22-hassio-2018.markdown
+++ /dev/null
@@ -1,64 +0,0 @@
----
-layout: post
-title: "Hass.io 2018"
-description: "We want to clarify how Hass.io relates to Home Assistant and talk about the roadmap for Hass.io in 2018."
-date: 2018-04-22 00:00:00
-date_formatted: "April 22, 2018"
-author: Pascal Vizeli
-author_twitter: pvizeli
-comments: true
-categories: Announcements
-og_image: /images/blog/2018-04-hassio-2018/blogpost.png
----
-
-We noticed that there is some confusion in the community about how Hass.io relates to Home Assistant and what impact the upcoming Hass.io changes will have. We will try to clarify it all in this blog post.
-
-## {% linkable_title What is Hass.io %}
-Hass.io is a complete solution to run Home Assistant, by the authors of Home Assistant. The goal of Hass.io is to provide an easy to use and secure system, entirely managed from within the Home Assistant user interface.
-
-Hass.io is a complete solution, which means that it comes with its own highly secure and optimized operating system, a supervisor application to maintain and configure that system, and of course Home Assistant itself.
-
-When using Hass.io, you'll see a new Hass.io panel inside the Home Assistant UI. From here users can configure the system and install Home Assistant updates with a simple click of a button. Users are also able to make snapshots of their system, making it easy to migrate all their configuration to a new system or restore their system to a previous state.
-
-We wanted to be able to provide the convenience of seamless updates and configuration via the UI to other applications too, and so we introduced Hass.io add-ons. Any application can be packaged up as a Hass.io add-on, allowing any user to install and manage it easily. Since the introduction, we’ve seen an amazing growth in users sharing their add-ons with the community. It’s now possible to install an adblocker for your network, an MQTT broker or Tor with a single click.
-
-## {% linkable_title Upcoming changes to Hass.io %}
-We’ve introduced Hass.io [last July]. Since then, we’ve noticed some room for improvements in making Hass.io easier to use, lighter to maintain and easier to integrate with other host systems.
-
-Note that the descriptions of upcoming improvements can get quite technical. Feel free to jump to [the conclusion].
-
-### {% linkable_title Automatic add-on configuration %}
-Home Assistant has recently introduced configuration entries. We’re going to hook into this new functionality and allow add-ons to configure their related integration in Home Assistant automatically. For example, if a user installs the MQTT broker add-on, we will automatically set up Home Assistant to connect to it.
-
-### {% linkable_title Host management %}
-To control the host system, we currently use a custom service called HostControl. This allows the user to manage here host and restart/shutdown the computer from within Home Assistant. Instead of relying on our own system, we’re going to change to use D-Bus. D-Bus is a standardized mechanism for services and applications to communicate. Using a defined standard means that all parts of the host can now be remotely configured: sound, network, etc, etc. We will be extending the Hass.io panel in Home Assistant with controls to configure various parts of the host.
-
-### {% linkable_title Hass.io OS %}
-Hass.io is currently using a forked version of ResinOS as our operating system. ResinOS has been designed to run a minimal environment for Docker, simple over the air updates and connect to the ResinIO cloud. Our fork removed the ResinIO logic. Over time, ResinOS has been evolving but not in a direction that is aligned with our goals, resulting in the maintenance of our fork to take up a lot of time.
-
-The ResinOS build system is based on the Yocto Project. This is a very powerful system, but also requires specific support for each hardware platform need to be specifically added and maintained (like each version of Raspberry Pi), which caused long build and development times for Hass.io.
-
-All these factors made us decide to build our own, custom, operating system. We’re obviously not starting from scratch, but instead, are basing it off [Buildroot] as the foundation and use [RAUC] for over the air updates.
-
-Some things that the new operating system will be able to do:
-- Easier to add support for new hardware.
-- Updating will be atomic and has a Fail-safe. If a system fails to boot after an OS upgrade, it will fallback, by booting the previous working version.
-- Updates are required to be securely signed by the Home Assistant team, adding a whole new level of security.
-- Compressing the root file system, making it faster on SD cards and slow IO-Interfaces.
-- Compressing parts of the memory so that we can store more information.
-
-## {% linkable_title What Hass.io users should do to prepare for these updates %}
-At this moment: Nothing.
-
-The new Hass.io supervisor still supports the old ResinOS builds (our official downloads for Raspberry Pi and Intel NUC) and generic Linux installations. If you’re using a generic Linux installation on SUSE Linux or Ubuntu, you have to update your local AppArmor profile if you want to use the new functionality (instructions will be provided upon release).
-
-Once our new installation images with HassioOS are released, you have to reflash your device once. You can do this without losing any configuration by using our Snapshot feature:
-- Create a snapshot of your current installation and download it to your PC.
-- Flash the SD card with the new Hass.io OS image.
-- Restore your snapshot.
-- Enjoy a new and improved Hass.io
-
-[last July]: https://www.home-assistant.io/blog/2017/07/25/introducing-hassio/
-[the conclusion]: #what-hassio-users-should-do-to-prepare-for-these-updates
-[Buildroot]: https://buildroot.org/
-[RAUC]: https://www.rauc.io/
diff --git a/source/_posts/2018-04-24-launch-google-assistant-support.markdown b/source/_posts/2018-04-24-launch-google-assistant-support.markdown
deleted file mode 100644
index 7a263f9682..0000000000
--- a/source/_posts/2018-04-24-launch-google-assistant-support.markdown
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: post
-title: "Our Google Assistant skill is live!"
-description: "The Google Assistant integration for Home Assistant Cloud is now available to all."
-date: 2018-04-24 00:01:00
-date_formatted: "April 24, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Announcement
-og_image: /images/blog/2018-04-google-assistant/google-assistant-home-assistant.png
----
-
-
-
-
-
-
-[Quadflight]: https://github.com/quadflight
-[Arsaboo]: https://github.com/arsaboo
diff --git a/source/_posts/2018-04-26-developer-site.markdown b/source/_posts/2018-04-26-developer-site.markdown
deleted file mode 100644
index 2895a83338..0000000000
--- a/source/_posts/2018-04-26-developer-site.markdown
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: post
-title: "New developer website"
-description: "We have extracted the developer section of our website into its own website."
-date: 2018-04-26 00:01:00
-date_formatted: "April 26, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Announcement
-og_image: /images/blog/2018-04-developer-website/screenshot.png
----
-
-When we launched the website in December 2014, we've only had a handful of components and usage instructions. Since then the website has grown to over a 1000 pages touching a wide range of topics. The growth, while great, also has put a lot of strain on how the docs are organised. One of the places that was especially suffering under the growth was the developer section. It was living under a single top menu item and had to contain everything in a single sidebar.
-
-To fix this, we're releasing a new website: [developers.home-assistant.io](https://developers.home-assistant.io). The website is aimed at people that are developing Home Assistant. It will contain resources how to setup your development environment, how to fix bugs, help with translations or improve the frontend. The main website will now solely be focused on Home Assistant users.
-
-Go check it out and let us know what you think: [developers.home-assistant.io](https://developers.home-assistant.io).
-
-
diff --git a/source/_posts/2018-04-27-release-68.markdown b/source/_posts/2018-04-27-release-68.markdown
deleted file mode 100644
index 924546f866..0000000000
--- a/source/_posts/2018-04-27-release-68.markdown
+++ /dev/null
@@ -1,533 +0,0 @@
----
-layout: post
-title: "0.68: HomeKit control, Eufy, FritzBox, SigFox sensors"
-description: "Enjoy your weekend with this brand new release of Home Assistant."
-date: 2018-04-27 00:01:00
-date_formatted: "April 27, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Release-Notes
-og_image: /images/blog/2018-04-0.68/components.png
----
-
-
-
-Weekend is around the corner and that means that it's time for the next release of Home Assistant. 0.68 brings a ton of great goodies and bug fixes.
-
-One of the coolest features this release is by [@mjg59]: you are now able to **control** HomeKit devices. Previously, it was possible to control Home Assistant from iOS devices using the HomeKit protocol. With this release, Home Assistant is able to become the controller and use HomeKit to control lights and switches directly. Since HomeKit is vendor agnostic, it means that any HomeKit light or switch will now be compatible with Home Assistant. Very cool.
-
-Another cool new platform, also by [@mjg59], is support for Eufy devices. Eufy is the Home Automation brand of Anker and they have been producing reasonably priced devices which can now be controlled by Home Assistant too. Thanks for all your contributions [@mjg59] ❤️.
-
-## {% linkable_title New Platforms %}
-
-- Add support for Eufy bulbs and switches ([@mjg59] - [#13773]) ([eufy docs]) ([light.eufy docs]) ([switch.eufy docs]) (new-platform)
-- Add support for controlling homekit lights and switches ([@mjg59] - [#13346]) ([homekit_controller docs]) ([light.homekit_controller docs]) (new-platform)
-- Adding USCIS component ([@meauxt] - [#13764]) ([sensor.uscis docs]) (new-platform)
-- Add support for new platform: climate.modbus ([@Kirchoff] - [#12224]) ([climate.modbus docs]) (new-platform)
-- Add AVM fritzbox smarthome component ([@hthiery] - [#10688]) ([fritzbox docs]) ([climate.fritzbox docs]) ([switch.fritzbox docs]) (new-platform)
-- Adds SigFox sensor ([@robmarkcole] - [#13731]) ([sensor.sigfox docs]) (new-platform)
-- Add blackbird media player component ([@koolsb] - [#13549]) ([media_player.blackbird docs]) (new-platform)
-- Add support for Sensirion SHT31 temperature/humidity sensor ([@viorels] - [#12952]) ([sensor.sht31 docs]) (new-platform)
-- Qwikswitch binary sensors ([@kellerza] - [#14008]) ([qwikswitch docs]) ([binary_sensor.qwikswitch docs]) ([sensor.qwikswitch docs]) (beta fix) (new-platform)
-
-## {% linkable_title New Features %}
-
-- Support binary_sensor and device_tracker in HomeKit ([@Yonsm] - [#13735]) ([homekit docs]) (new-feature)
-- Add Homekit locks support ([@philk] - [#13625]) ([homekit docs]) (new-feature)
-- Support CO2/PM2.5/Light sensors in HomeKit ([@Yonsm] - [#13804]) ([homekit docs]) (new-feature)
-- Support Garage Doors in HomeKit ([@marthoc] - [#13796]) ([homekit docs]) (new-feature)
-- Support basic covers with open/close/stop services HomeKit ([@nickw444] - [#13819]) ([homekit docs]) (new-feature)
-
-## {% linkable_title Release 0.68.1 - April 30 %}
-
-- Fix color setting of tplink lights ([@amelchio] - [#14108]) ([light.tplink docs])
-- Improve precision of Hue color state ([@amelchio] - [#14113]) ([light.hue docs])
-- Revert Hue color state to be xy-based ([@amelchio] - [#14154])
-- Fix Python 3.6 compatibility for HomeKit controller ([@mjg59] - [#14160]) ([homekit_controller docs])
-- Added CONF_IP_ADDRESS to HomeKit ([@cdce8p] - [#14163]) ([homekit docs])
-- Do not sync entities with an empty name ([@balloob] - [#14181]) ([google_assistant docs])
-- Improve chromecast disconnection logic ([@OttoWinter] - [#14190]) ([media_player.cast docs])
-- Fix poorly formatted automations ([@balloob] - [#14196])
-- Disable eliqonline requirement ([@balloob] - [#14156])
-
-## {% linkable_title If you need help... %}
-
-...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
-
-## {% linkable_title Reporting Issues %}
-
-Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
-
-
-## {% linkable_title Breaking Changes %}
-
-- Icons! Material Design Icons has implemented some naming guidelines and this caused 9 icons to change names, 3 of which are home automation icons: `roomba` -> `robot-vacuum`, `nest-protect` -> `smoke-detector`, `nest-thermostat` -> `thermostat` ([see all changes](http://templarian.com/2018/04/18/material-design-icons-v2-3-54/)).
-- Support for multiple MAX!Cube LAN gateways caused a slight change to the configuration schema. Make sure to check the docs for the new one. ([@syssi] - [#13517]) ([maxcube docs]) ([binary_sensor.maxcube docs]) ([climate.maxcube docs]) (breaking change)
-- Ebox sensor platform has been disabled because the dependency was not compatible with pip 10. ([@balloob] - [#14003]) ([sensor.ebox docs]) (breaking change)
-
-## {% linkable_title Beta Fixes %}
-
-- Qwikswitch binary sensors ([@kellerza] - [#14008]) ([qwikswitch docs]) ([binary_sensor.qwikswitch docs]) ([sensor.qwikswitch docs]) (beta fix) (new-platform)
-- Order the output of the automation editor ([@balloob] - [#14019]) ([config docs]) (beta fix)
-- HomeKit Alarm Control Panel Code Exception Fix ([@schmittx] - [#14025]) ([homekit docs]) (beta fix)
-- Revert cast platform polling mode ([@OttoWinter] - [#14027]) ([media_player.cast docs]) (beta fix)
-- Handle HomeKit configuration failure more cleanly ([@mjg59] - [#14041]) ([homekit_controller docs]) (beta fix)
-- Update device classes for contact sensor HomeKit ([@marthoc] - [#14051]) ([homekit docs]) (beta fix)
-- Upgrade broadlink lib ([@Danielhiversen] - [#14074]) ([sensor.broadlink docs]) ([switch.broadlink docs]) (beta fix)
-- Fix timezone issue when calculating min/max values in tibber #14009 ([@Danielhiversen] - [#14080]) ([sensor.tibber docs]) (beta fix)
-- Updated list of AWS regions for Amazon Polly ([@GotoCode] - [#14097]) ([tts docs]) (beta fix)
-- Change Eufy brightness handling ([@mjg59] - [#14111]) (beta fix)
-
-## {% linkable_title All changes %}
-
-- Update Homekit to 1.1.9 ([@cdce8p] - [#13716]) ([homekit docs])
-- Update docstrings ([@fabaff] - [#13720]) ([ihc docs]) ([cover.opengarage docs]) ([cover.tahoma docs]) ([sensor.trafikverket_weatherstation docs])
-- Add option to ignore availability in google calendar events ([@cgtobi] - [#13714]) ([calendar.google docs])
-- Allow use of date_string in service call ([@Juggels] - [#13256]) ([calendar.todoist docs])
-- Add timeout / debounce (for brightness and others) ([@cdce8p] - [#13534]) ([homekit docs])
-- added support for smappee water sensors ([@hmn] - [#12831]) ([smappee docs]) ([sensor.smappee docs])
-- Initialise filter_sensor with historical values ([@dgomes] - [#13075]) ([sensor.filter docs])
-- Fix Gogogate2 'available' attribute ([@dlbroadfoot] - [#13728]) (beta fix)
-- Bluesound bugfix status 595 and await ([@thrawnarn] - [#13727]) ([media_player.bluesound docs])
-- Upgrade aiohttp to 3.1.2 ([@fabaff] - [#13732])
-- Upgrade sqlalchemy to 1.2.6 ([@fabaff] - [#13733]) ([sensor.sql docs])
-- Brightness conversion for Abode dimmers ([@shred86] - [#13711]) ([light.abode docs])
-- Update CODEOWNERS (sensor.filter, sensor.upnp) ([@dgomes] - [#13736])
-- Reset permission ([@fabaff] - [#13743]) ([light.abode docs])
-- Throw an error when invalid device_mode is given ([@dangyuluo] - [#13739])
-- Fix so it is possible to ignore discovered config entry handlers ([@Kane610] - [#13741]) (beta fix)
-- Upgrade netdisco to 1.3.1 ([@fabaff] - [#13744])
-- Add MQTT Sensor unique_id ([@OttoWinter] - [#13318]) ([sensor.mqtt docs])
-- Prepare entity component for config entries ([@balloob] - [#13730])
-- Check valid file on get_size ([@robmarkcole] - [#13756]) ([sensor.folder docs])
-- Qwikswitch sensors ([@kellerza] - [#13622]) ([sensor.qwikswitch docs])
-- Device type mapping introduced to avoid breaking change ([@syssi] - [#13765]) ([light.yeelight docs])
-- Only flag media position as updated when it really has ([@molobrakos] - [#13737]) ([media_player.squeezebox docs])
-- Support binary_sensor and device_tracker in HomeKit ([@Yonsm] - [#13735]) ([homekit docs]) (new-feature)
-- Use config entry to setup platforms ([@balloob] - [#13752]) ([hue docs]) ([light docs]) ([light.hue docs])
-- Add Homekit locks support ([@philk] - [#13625]) ([homekit docs]) (new-feature)
-- Snips sounds ([@tschmidty69] - [#13746]) ([snips docs])
-- Add missing DISCHRG state ([@swilson] - [#13787]) ([sensor.nut docs])
-- Improved upgradeability HomeKit security_systems ([@cdce8p] - [#13783]) ([homekit docs])
-- Qwikswitch Entity Register ([@kellerza] - [#13791]) ([qwikswitch docs]) ([sensor.qwikswitch docs])
-- Updated beacontools to 1.2.3 ([@citruz] - [#13792]) ([sensor.eddystone_temperature docs])
-- script/lazytox: Ensure Flake8 passes for tests/ ([@kellerza] - [#13794])
-- Fix bad metrics format for short metrics. ([@michaelkuty] - [#13778]) ([prometheus docs])
-- Update bellows to 0.5.2 ([@rcloran] - [#13800]) ([zha docs])
-- device_tracker.ubus: Handle devices not running DHCP ([@tobygray] - [#13579]) ([device_tracker docs])
-- Update yweather.py ([@wiuwiu] - [#13802]) ([weather.yweather docs])
-- Tibber lib update ([@Danielhiversen] - [#13811]) ([sensor.tibber docs])
-- Update pyhomematic to 0.1.41 ([@danielperna84] - [#13814]) ([homematic docs])
-- Add support for Eufy bulbs and switches ([@mjg59] - [#13773]) ([eufy docs]) ([light.eufy docs]) ([switch.eufy docs]) (new-platform)
-- Homekit refactor ([@cdce8p] - [#13707]) ([homekit docs])
-- HomeKit type_cover fix ([@cdce8p] - [#13832]) ([homekit docs])
-- Allow platform unloading ([@balloob] - [#13784]) ([hue docs]) ([light docs])
-- Support CO2/PM2.5/Light sensors in HomeKit ([@Yonsm] - [#13804]) ([homekit docs]) (new-feature)
-- Clicksend: Added support for multiple recipients ([@xTCx] - [#13812]) ([notify docs])
-- Support Garage Doors in HomeKit ([@marthoc] - [#13796]) ([homekit docs]) (new-feature)
-- Abode better events ([@MisterWil] - [#13809]) ([abode docs])
-- UPnP async ([@dgomes] - [#13666]) ([upnp docs]) ([sensor.upnp docs])
-- Update example (fixes #13834) ([@fabaff] - [#13839])
-- Add support for deCONZ daylight sensor ([@marthoc] - [#13479]) ([deconz docs]) ([sensor.deconz docs])
-- initialize queue before filtering ([@dgomes] - [#13842]) ([sensor.filter docs])
-- Extract config flow to own module ([@balloob] - [#13840]) ([config docs]) ([deconz docs]) ([hue docs])
-- Add support for controlling homekit lights and switches ([@mjg59] - [#13346]) ([homekit_controller docs]) ([light.homekit_controller docs]) (new-platform)
-- bump python-ecobee-api version to 0.0.18 ([@geekofweek] - [#13854]) ([ecobee docs])
-- Adding USCIS component ([@meauxt] - [#13764]) ([sensor.uscis docs]) (new-platform)
-- Avoid unnecessary cast state updates ([@dersger] - [#13770]) ([media_player.cast docs])
-- Prevent vesync doing I/O in event loop ([@balloob] - [#13862]) ([switch.vesync docs]) (beta fix)
-- Update yweather.py ([@TheCellMC] - [#13851]) ([weather.yweather docs])
-- add support for Kodi discovery ([@escoand] - [#13790]) ([media_player.kodi docs])
-- Further untangle data entry flow ([@balloob] - [#13855])
-- Missing property decorator added ([@syssi] - [#13889]) ([fan.xiaomi_miio docs]) (beta fix)
-- Fix race condition for component loaded before listening ([@balloob] - [#13887]) ([config docs]) (beta fix)
-- Added snips service descriptions ([@tschmidty69] - [#13883])
-- Add unique_id for BMW ConnectedDrive ([@gerard33] - [#13888]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs])
-- Revert "Update yweather.py" ([@pvizeli] - [#13900]) ([weather.yweather docs])
-- Eufy colour bulb updates ([@mjg59] - [#13895]) ([eufy docs]) ([light.eufy docs])
-- Fix #13846 Double underscore in bluetooth address ([@aav7fl] - [#13884]) ([device_tracker docs]) (beta fix)
-- Import operation modes from air humidifier ([@syssi] - [#13908]) ([fan.xiaomi_miio docs]) (beta fix)
-- Fritzbox netmonitor name ([@escoand] - [#13903]) ([sensor.fritzbox_netmonitor docs])
-- Restore typeerror check for units sans energy tracking ([@andersonshatch] - [#13824]) ([switch.edimax docs])
-- Add more math functions to templates ([@Shou] - [#13915])
-- Upgrade pyqwikswitch to 0.71 ([@kellerza] - [#13920]) ([qwikswitch docs])
-- Add extra attributes for device scanner, Nmap and Unifi (IP, SSID, etc.) ([@stephanerosi] - [#13673]) ([device_tracker docs])
-- Fixed Capsman data not being used ([@Marco98] - [#13917]) ([device_tracker docs])
-- Broadlink Sensor - switch to connection-less mode ([@Paxy] - [#13761]) ([sensor.broadlink docs])
-- Add support for new platform: climate.modbus ([@Kirchoff] - [#12224]) ([climate.modbus docs]) (new-platform)
-- Hive R3 update ([@KJonline] - [#13357]) ([hive docs]) ([binary_sensor.hive docs]) ([climate.hive docs]) ([light.hive docs]) ([sensor.hive docs]) ([switch.hive docs])
-- Updated foobot_async package version ([@reefab] - [#13942]) ([sensor.foobot docs])
-- Update pyhydroquebec to 2.2.2 ([@titilambert] - [#13946]) ([sensor.hydroquebec docs]) (beta fix)
-- Upgrade alpha_vantage to 2.0.0 ([@fabaff] - [#13943]) ([sensor.alpha_vantage docs])
-- Cleanup on exit ([@dgomes] - [#13918]) ([media_player.mediaroom docs])
-- Upgrade somecomfort to 0.5.2 ([@balloob] - [#13940]) ([climate.honeywell docs]) (beta fix)
-- Add data entry flow helper ([@balloob] - [#13935]) ([config docs])
-- Xiaomi MiIO Device Tracker: Unused variable removed ([@syssi] - [#13948]) ([device_tracker docs])
-- Implement play media to set a channel based on (by priority): ([@stephanerosi] - [#13934]) ([media_player.webostv docs])
-- Update of python-mpd2 ([@karlkar] - [#13921]) ([media_player.mpd docs])
-- Add AVM fritzbox smarthome component ([@hthiery] - [#10688]) ([fritzbox docs]) ([climate.fritzbox docs]) ([switch.fritzbox docs]) (new-platform)
-- Adds SigFox sensor ([@robmarkcole] - [#13731]) ([sensor.sigfox docs]) (new-platform)
-- Upgrade aiohttp to 3.1.3 ([@fabaff] - [#13938])
-- Upgrade youtube_dl to 2018.04.16 ([@fabaff] - [#13937]) ([media_extractor docs])
-- Added FB messenger broadcast api to notify.facebook component ([@B1tMaster] - [#12459]) ([notify.facebook docs])
-- Added web view for TTS to get url ([@tschmidty69] - [#13882]) ([tts docs])
-- Add services for bmw_connected_drive ([@ChristianKuehnel] - [#13497]) ([bmw_connected_drive docs]) ([device_tracker docs])
-- Fix call to parent broadlink switch ([@Danielhiversen] - [#13906]) ([switch.broadlink docs]) (beta fix)
-- Bump deCONZ requirement to v36 ([@Kane610] - [#13960]) ([deconz docs])
-- Fix Gogogate2 'available' attribute ([@dlbroadfoot] - [#13728]) (beta fix)
-- Fix so it is possible to ignore discovered config entry handlers ([@Kane610] - [#13741]) (beta fix)
-- Prevent vesync doing I/O in event loop ([@balloob] - [#13862]) ([switch.vesync docs]) (beta fix)
-- Fix #13846 Double underscore in bluetooth address ([@aav7fl] - [#13884]) ([device_tracker docs]) (beta fix)
-- Fix race condition for component loaded before listening ([@balloob] - [#13887]) ([config docs]) (beta fix)
-- Missing property decorator added ([@syssi] - [#13889]) ([fan.xiaomi_miio docs]) (beta fix)
-- Fix call to parent broadlink switch ([@Danielhiversen] - [#13906]) ([switch.broadlink docs]) (beta fix)
-- Import operation modes from air humidifier ([@syssi] - [#13908]) ([fan.xiaomi_miio docs]) (beta fix)
-- Upgrade pyqwikswitch to 0.71 ([@kellerza] - [#13920]) ([qwikswitch docs])
-- Upgrade somecomfort to 0.5.2 ([@balloob] - [#13940]) ([climate.honeywell docs]) (beta fix)
-- Update pyhydroquebec to 2.2.2 ([@titilambert] - [#13946]) ([sensor.hydroquebec docs]) (beta fix)
-- Revert "Upgrade pyqwikswitch to 0.71 ([@balloob] - [#13920]) ([qwikswitch docs])
-- Bump skybellpy version to 0.1.2 ([@MisterWil] - [#13974]) ([skybell docs])
-- Fix typo an coding style ([@stephanerosi] - [#13970]) ([device_tracker docs])
-- Params of the send command can be a list now ([@syssi] - [#13905]) ([vacuum docs])
-- Support basic covers with open/close/stop services HomeKit ([@nickw444] - [#13819]) ([homekit docs]) (new-feature)
-- Colorlog windows fix ([@veleek] - [#13929]) ([notify docs])
-- deCONZ migrate setup fully to config entry ([@Kane610] - [#13679]) ([deconz docs])
-- Alexa thermostat fails to properly parse 'value' field for climate ([@no2chem] - [#13958]) ([alexa docs])
-- renaming icons ([@NovapaX] - [#13982]) ([hdmi_cec docs]) ([vacuum docs]) ([vacuum.dyson docs]) ([vacuum.neato docs]) ([vacuum.roomba docs]) ([vacuum.xiaomi_miio docs])
-- Fix for Lokalise backend misinterpretation of keys ([@armills] - [#13986])
-- Bump locationsharinglib to 1.2.1 ([@thelittlefireman] - [#13980]) ([device_tracker docs])
-- Support for multiple MAX!Cube LAN gateways added ([@syssi] - [#13517]) ([maxcube docs]) ([binary_sensor.maxcube docs]) ([climate.maxcube docs]) (breaking change)
-- Add additional receiver for Onkyo zone 2 ([@koolsb] - [#13551]) ([media_player.onkyo docs])
-- Add blackbird media player component ([@koolsb] - [#13549]) ([media_player.blackbird docs]) (new-platform)
-- Add support for Sensirion SHT31 temperature/humidity sensor ([@viorels] - [#12952]) ([sensor.sht31 docs]) (new-platform)
-- Useless code removed ([@syssi] - [#13996]) ([maxcube docs])
-- Add Homematic HmIP-SWO-PR weather sensor support ([@pascalhahn] - [#13904]) ([homematic docs])
-- Disable ebox requirement ([@balloob] - [#14003]) ([sensor.ebox docs]) (breaking change)
-- Upgraded miflora library to version 0.4.0 ([@ChristianKuehnel] - [#14005]) ([sensor.miflora docs])
-- Log an error instead of raising an exception ([@syssi] - [#14006]) ([sensor.sht31 docs])
-- Tibber available ([@Danielhiversen] - [#13865]) ([sensor.tibber docs])
-- Upgrade pylutron-caseta to 0.5.0 to reestablish connections ([@rohankapoorcom] - [#14013]) ([lutron_caseta docs])
-- Add sensor device classes ([@balloob] - [#14010]) ([sensor docs]) ([sensor.ecobee docs]) ([sensor.linux_battery docs]) ([sensor.nest docs])
-- Qwikswitch binary sensors ([@kellerza] - [#14008]) ([qwikswitch docs]) ([binary_sensor.qwikswitch docs]) ([sensor.qwikswitch docs]) (beta fix) (new-platform)
-- Order the output of the automation editor ([@balloob] - [#14019]) ([config docs]) (beta fix)
-- HomeKit Alarm Control Panel Code Exception Fix ([@schmittx] - [#14025]) ([homekit docs]) (beta fix)
-- Revert cast platform polling mode ([@OttoWinter] - [#14027]) ([media_player.cast docs]) (beta fix)
-- Handle HomeKit configuration failure more cleanly ([@mjg59] - [#14041]) ([homekit_controller docs]) (beta fix)
-- Update device classes for contact sensor HomeKit ([@marthoc] - [#14051]) ([homekit docs]) (beta fix)
-- Upgrade broadlink lib ([@Danielhiversen] - [#14074]) ([sensor.broadlink docs]) ([switch.broadlink docs]) (beta fix)
-- Fix timezone issue when calculating min/max values in tibber #14009 ([@Danielhiversen] - [#14080]) ([sensor.tibber docs]) (beta fix)
-- Updated list of AWS regions for Amazon Polly ([@GotoCode] - [#14097]) ([tts docs]) (beta fix)
-
-[#10688]: https://github.com/home-assistant/home-assistant/pull/10688
-[#12224]: https://github.com/home-assistant/home-assistant/pull/12224
-[#12459]: https://github.com/home-assistant/home-assistant/pull/12459
-[#12831]: https://github.com/home-assistant/home-assistant/pull/12831
-[#12952]: https://github.com/home-assistant/home-assistant/pull/12952
-[#13075]: https://github.com/home-assistant/home-assistant/pull/13075
-[#13256]: https://github.com/home-assistant/home-assistant/pull/13256
-[#13318]: https://github.com/home-assistant/home-assistant/pull/13318
-[#13346]: https://github.com/home-assistant/home-assistant/pull/13346
-[#13357]: https://github.com/home-assistant/home-assistant/pull/13357
-[#13479]: https://github.com/home-assistant/home-assistant/pull/13479
-[#13497]: https://github.com/home-assistant/home-assistant/pull/13497
-[#13517]: https://github.com/home-assistant/home-assistant/pull/13517
-[#13534]: https://github.com/home-assistant/home-assistant/pull/13534
-[#13549]: https://github.com/home-assistant/home-assistant/pull/13549
-[#13551]: https://github.com/home-assistant/home-assistant/pull/13551
-[#13579]: https://github.com/home-assistant/home-assistant/pull/13579
-[#13622]: https://github.com/home-assistant/home-assistant/pull/13622
-[#13625]: https://github.com/home-assistant/home-assistant/pull/13625
-[#13666]: https://github.com/home-assistant/home-assistant/pull/13666
-[#13673]: https://github.com/home-assistant/home-assistant/pull/13673
-[#13679]: https://github.com/home-assistant/home-assistant/pull/13679
-[#13707]: https://github.com/home-assistant/home-assistant/pull/13707
-[#13711]: https://github.com/home-assistant/home-assistant/pull/13711
-[#13714]: https://github.com/home-assistant/home-assistant/pull/13714
-[#13716]: https://github.com/home-assistant/home-assistant/pull/13716
-[#13720]: https://github.com/home-assistant/home-assistant/pull/13720
-[#13727]: https://github.com/home-assistant/home-assistant/pull/13727
-[#13728]: https://github.com/home-assistant/home-assistant/pull/13728
-[#13730]: https://github.com/home-assistant/home-assistant/pull/13730
-[#13731]: https://github.com/home-assistant/home-assistant/pull/13731
-[#13732]: https://github.com/home-assistant/home-assistant/pull/13732
-[#13733]: https://github.com/home-assistant/home-assistant/pull/13733
-[#13735]: https://github.com/home-assistant/home-assistant/pull/13735
-[#13736]: https://github.com/home-assistant/home-assistant/pull/13736
-[#13737]: https://github.com/home-assistant/home-assistant/pull/13737
-[#13739]: https://github.com/home-assistant/home-assistant/pull/13739
-[#13741]: https://github.com/home-assistant/home-assistant/pull/13741
-[#13743]: https://github.com/home-assistant/home-assistant/pull/13743
-[#13744]: https://github.com/home-assistant/home-assistant/pull/13744
-[#13746]: https://github.com/home-assistant/home-assistant/pull/13746
-[#13752]: https://github.com/home-assistant/home-assistant/pull/13752
-[#13756]: https://github.com/home-assistant/home-assistant/pull/13756
-[#13761]: https://github.com/home-assistant/home-assistant/pull/13761
-[#13764]: https://github.com/home-assistant/home-assistant/pull/13764
-[#13765]: https://github.com/home-assistant/home-assistant/pull/13765
-[#13770]: https://github.com/home-assistant/home-assistant/pull/13770
-[#13773]: https://github.com/home-assistant/home-assistant/pull/13773
-[#13778]: https://github.com/home-assistant/home-assistant/pull/13778
-[#13783]: https://github.com/home-assistant/home-assistant/pull/13783
-[#13784]: https://github.com/home-assistant/home-assistant/pull/13784
-[#13787]: https://github.com/home-assistant/home-assistant/pull/13787
-[#13790]: https://github.com/home-assistant/home-assistant/pull/13790
-[#13791]: https://github.com/home-assistant/home-assistant/pull/13791
-[#13792]: https://github.com/home-assistant/home-assistant/pull/13792
-[#13794]: https://github.com/home-assistant/home-assistant/pull/13794
-[#13796]: https://github.com/home-assistant/home-assistant/pull/13796
-[#13800]: https://github.com/home-assistant/home-assistant/pull/13800
-[#13802]: https://github.com/home-assistant/home-assistant/pull/13802
-[#13804]: https://github.com/home-assistant/home-assistant/pull/13804
-[#13809]: https://github.com/home-assistant/home-assistant/pull/13809
-[#13811]: https://github.com/home-assistant/home-assistant/pull/13811
-[#13812]: https://github.com/home-assistant/home-assistant/pull/13812
-[#13814]: https://github.com/home-assistant/home-assistant/pull/13814
-[#13819]: https://github.com/home-assistant/home-assistant/pull/13819
-[#13824]: https://github.com/home-assistant/home-assistant/pull/13824
-[#13832]: https://github.com/home-assistant/home-assistant/pull/13832
-[#13839]: https://github.com/home-assistant/home-assistant/pull/13839
-[#13840]: https://github.com/home-assistant/home-assistant/pull/13840
-[#13842]: https://github.com/home-assistant/home-assistant/pull/13842
-[#13851]: https://github.com/home-assistant/home-assistant/pull/13851
-[#13854]: https://github.com/home-assistant/home-assistant/pull/13854
-[#13855]: https://github.com/home-assistant/home-assistant/pull/13855
-[#13862]: https://github.com/home-assistant/home-assistant/pull/13862
-[#13865]: https://github.com/home-assistant/home-assistant/pull/13865
-[#13882]: https://github.com/home-assistant/home-assistant/pull/13882
-[#13883]: https://github.com/home-assistant/home-assistant/pull/13883
-[#13884]: https://github.com/home-assistant/home-assistant/pull/13884
-[#13887]: https://github.com/home-assistant/home-assistant/pull/13887
-[#13888]: https://github.com/home-assistant/home-assistant/pull/13888
-[#13889]: https://github.com/home-assistant/home-assistant/pull/13889
-[#13895]: https://github.com/home-assistant/home-assistant/pull/13895
-[#13900]: https://github.com/home-assistant/home-assistant/pull/13900
-[#13903]: https://github.com/home-assistant/home-assistant/pull/13903
-[#13904]: https://github.com/home-assistant/home-assistant/pull/13904
-[#13905]: https://github.com/home-assistant/home-assistant/pull/13905
-[#13906]: https://github.com/home-assistant/home-assistant/pull/13906
-[#13908]: https://github.com/home-assistant/home-assistant/pull/13908
-[#13915]: https://github.com/home-assistant/home-assistant/pull/13915
-[#13917]: https://github.com/home-assistant/home-assistant/pull/13917
-[#13918]: https://github.com/home-assistant/home-assistant/pull/13918
-[#13920]: https://github.com/home-assistant/home-assistant/pull/13920
-[#13921]: https://github.com/home-assistant/home-assistant/pull/13921
-[#13929]: https://github.com/home-assistant/home-assistant/pull/13929
-[#13934]: https://github.com/home-assistant/home-assistant/pull/13934
-[#13935]: https://github.com/home-assistant/home-assistant/pull/13935
-[#13937]: https://github.com/home-assistant/home-assistant/pull/13937
-[#13938]: https://github.com/home-assistant/home-assistant/pull/13938
-[#13940]: https://github.com/home-assistant/home-assistant/pull/13940
-[#13942]: https://github.com/home-assistant/home-assistant/pull/13942
-[#13943]: https://github.com/home-assistant/home-assistant/pull/13943
-[#13946]: https://github.com/home-assistant/home-assistant/pull/13946
-[#13948]: https://github.com/home-assistant/home-assistant/pull/13948
-[#13958]: https://github.com/home-assistant/home-assistant/pull/13958
-[#13960]: https://github.com/home-assistant/home-assistant/pull/13960
-[#13970]: https://github.com/home-assistant/home-assistant/pull/13970
-[#13974]: https://github.com/home-assistant/home-assistant/pull/13974
-[#13980]: https://github.com/home-assistant/home-assistant/pull/13980
-[#13982]: https://github.com/home-assistant/home-assistant/pull/13982
-[#13986]: https://github.com/home-assistant/home-assistant/pull/13986
-[#13996]: https://github.com/home-assistant/home-assistant/pull/13996
-[#14003]: https://github.com/home-assistant/home-assistant/pull/14003
-[#14005]: https://github.com/home-assistant/home-assistant/pull/14005
-[#14006]: https://github.com/home-assistant/home-assistant/pull/14006
-[#14008]: https://github.com/home-assistant/home-assistant/pull/14008
-[#14010]: https://github.com/home-assistant/home-assistant/pull/14010
-[#14013]: https://github.com/home-assistant/home-assistant/pull/14013
-[#14019]: https://github.com/home-assistant/home-assistant/pull/14019
-[#14025]: https://github.com/home-assistant/home-assistant/pull/14025
-[#14027]: https://github.com/home-assistant/home-assistant/pull/14027
-[#14041]: https://github.com/home-assistant/home-assistant/pull/14041
-[#14051]: https://github.com/home-assistant/home-assistant/pull/14051
-[#14074]: https://github.com/home-assistant/home-assistant/pull/14074
-[#14080]: https://github.com/home-assistant/home-assistant/pull/14080
-[#14097]: https://github.com/home-assistant/home-assistant/pull/14097
-[@B1tMaster]: https://github.com/B1tMaster
-[@ChristianKuehnel]: https://github.com/ChristianKuehnel
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@GotoCode]: https://github.com/GotoCode
-[@Juggels]: https://github.com/Juggels
-[@KJonline]: https://github.com/KJonline
-[@Kane610]: https://github.com/Kane610
-[@Kirchoff]: https://github.com/Kirchoff
-[@Marco98]: https://github.com/Marco98
-[@MisterWil]: https://github.com/MisterWil
-[@NovapaX]: https://github.com/NovapaX
-[@OttoWinter]: https://github.com/OttoWinter
-[@Paxy]: https://github.com/Paxy
-[@Shou]: https://github.com/Shou
-[@TheCellMC]: https://github.com/TheCellMC
-[@Yonsm]: https://github.com/Yonsm
-[@aav7fl]: https://github.com/aav7fl
-[@andersonshatch]: https://github.com/andersonshatch
-[@armills]: https://github.com/armills
-[@balloob]: https://github.com/balloob
-[@cdce8p]: https://github.com/cdce8p
-[@cgtobi]: https://github.com/cgtobi
-[@citruz]: https://github.com/citruz
-[@dangyuluo]: https://github.com/dangyuluo
-[@danielperna84]: https://github.com/danielperna84
-[@dersger]: https://github.com/dersger
-[@dgomes]: https://github.com/dgomes
-[@dlbroadfoot]: https://github.com/dlbroadfoot
-[@escoand]: https://github.com/escoand
-[@fabaff]: https://github.com/fabaff
-[@geekofweek]: https://github.com/geekofweek
-[@gerard33]: https://github.com/gerard33
-[@hmn]: https://github.com/hmn
-[@hthiery]: https://github.com/hthiery
-[@karlkar]: https://github.com/karlkar
-[@kellerza]: https://github.com/kellerza
-[@koolsb]: https://github.com/koolsb
-[@marthoc]: https://github.com/marthoc
-[@meauxt]: https://github.com/meauxt
-[@michaelkuty]: https://github.com/michaelkuty
-[@mjg59]: https://github.com/mjg59
-[@molobrakos]: https://github.com/molobrakos
-[@nickw444]: https://github.com/nickw444
-[@no2chem]: https://github.com/no2chem
-[@pascalhahn]: https://github.com/pascalhahn
-[@philk]: https://github.com/philk
-[@pvizeli]: https://github.com/pvizeli
-[@rcloran]: https://github.com/rcloran
-[@reefab]: https://github.com/reefab
-[@robmarkcole]: https://github.com/robmarkcole
-[@rohankapoorcom]: https://github.com/rohankapoorcom
-[@schmittx]: https://github.com/schmittx
-[@shred86]: https://github.com/shred86
-[@stephanerosi]: https://github.com/stephanerosi
-[@swilson]: https://github.com/swilson
-[@syssi]: https://github.com/syssi
-[@thelittlefireman]: https://github.com/thelittlefireman
-[@thrawnarn]: https://github.com/thrawnarn
-[@titilambert]: https://github.com/titilambert
-[@tobygray]: https://github.com/tobygray
-[@tschmidty69]: https://github.com/tschmidty69
-[@veleek]: https://github.com/veleek
-[@viorels]: https://github.com/viorels
-[@wiuwiu]: https://github.com/wiuwiu
-[@xTCx]: https://github.com/xTCx
-[abode docs]: /components/abode/
-[alexa docs]: /components/alexa/
-[binary_sensor.bmw_connected_drive docs]: /components/binary_sensor.bmw_connected_drive/
-[binary_sensor.hive docs]: /components/binary_sensor.hive/
-[binary_sensor.maxcube docs]: /components/binary_sensor.maxcube/
-[binary_sensor.qwikswitch docs]: /components/binary_sensor.qwikswitch/
-[bmw_connected_drive docs]: /components/bmw_connected_drive/
-[calendar.google docs]: /components/calendar.google/
-[calendar.todoist docs]: /components/calendar.todoist/
-[climate.fritzbox docs]: /components/climate.fritzbox/
-[climate.hive docs]: /components/climate.hive/
-[climate.honeywell docs]: /components/climate.honeywell/
-[climate.maxcube docs]: /components/climate.maxcube/
-[climate.modbus docs]: /components/climate.modbus/
-[config docs]: /components/config/
-[cover.opengarage docs]: /components/cover.opengarage/
-[cover.tahoma docs]: /components/cover.tahoma/
-[deconz docs]: /components/deconz/
-[device_tracker docs]: /components/device_tracker/
-[ecobee docs]: /components/ecobee/
-[eufy docs]: /components/eufy/
-[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
-[fritzbox docs]: /components/fritzbox/
-[google docs]: /components/google/
-[hdmi_cec docs]: /components/hdmi_cec/
-[hive docs]: /components/hive/
-[homekit docs]: /components/homekit/
-[homekit_controller docs]: /components/homekit_controller/
-[homematic docs]: /components/homematic/
-[hue docs]: /components/hue/
-[ihc docs]: /components/ihc/
-[light docs]: /components/light/
-[light.abode docs]: /components/light.abode/
-[light.aurora docs]: /components/light.aurora/
-[light.eufy docs]: /components/light.eufy/
-[light.hive docs]: /components/light.hive/
-[light.homekit_controller docs]: /components/light.homekit_controller/
-[light.hue docs]: /components/light.hue/
-[light.yeelight docs]: /components/light.yeelight/
-[lock.bmw_connected_drive docs]: /components/lock.bmw_connected_drive/
-[lutron_caseta docs]: /components/lutron_caseta/
-[maxcube docs]: /components/maxcube/
-[media_extractor docs]: /components/media_extractor/
-[media_player.blackbird docs]: /components/media_player.blackbird/
-[media_player.bluesound docs]: /components/media_player.bluesound/
-[media_player.cast docs]: /components/media_player.cast/
-[media_player.kodi docs]: /components/media_player.kodi/
-[media_player.mediaroom docs]: /components/media_player.mediaroom/
-[media_player.mpd docs]: /components/media_player.mpd/
-[media_player.onkyo docs]: /components/media_player.onkyo/
-[media_player.squeezebox docs]: /components/media_player.squeezebox/
-[media_player.webostv docs]: /components/media_player.webostv/
-[notify docs]: /components/notify/
-[notify.facebook docs]: /components/notify.facebook/
-[prometheus docs]: /components/prometheus/
-[qwikswitch docs]: /components/qwikswitch/
-[sensor docs]: /components/sensor/
-[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
-[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
-[sensor.broadlink docs]: /components/sensor.broadlink/
-[sensor.deconz docs]: /components/sensor.deconz/
-[sensor.ebox docs]: /components/sensor.ebox/
-[sensor.ecobee docs]: /components/sensor.ecobee/
-[sensor.eddystone_temperature docs]: /components/sensor.eddystone_temperature/
-[sensor.filter docs]: /components/sensor.filter/
-[sensor.folder docs]: /components/sensor.folder/
-[sensor.foobot docs]: /components/sensor.foobot/
-[sensor.fritzbox_netmonitor docs]: /components/sensor.fritzbox_netmonitor/
-[sensor.hive docs]: /components/sensor.hive/
-[sensor.hydroquebec docs]: /components/sensor.hydroquebec/
-[sensor.linux_battery docs]: /components/sensor.linux_battery/
-[sensor.miflora docs]: /components/sensor.miflora/
-[sensor.mqtt docs]: /components/sensor.mqtt/
-[sensor.nest docs]: /components/sensor.nest/
-[sensor.nut docs]: /components/sensor.nut/
-[sensor.qwikswitch docs]: /components/sensor.qwikswitch/
-[sensor.sht31 docs]: /components/sensor.sht31/
-[sensor.sigfox docs]: /components/sensor.sigfox/
-[sensor.smappee docs]: /components/sensor.smappee/
-[sensor.sql docs]: /components/sensor.sql/
-[sensor.tibber docs]: /components/sensor.tibber/
-[sensor.trafikverket_weatherstation docs]: /components/sensor.trafikverket_weatherstation/
-[sensor.upnp docs]: /components/sensor.upnp/
-[sensor.uscis docs]: /components/sensor.uscis/
-[skybell docs]: /components/skybell/
-[smappee docs]: /components/smappee/
-[snips docs]: /components/snips/
-[switch.broadlink docs]: /components/switch.broadlink/
-[switch.edimax docs]: /components/switch.edimax/
-[switch.eufy docs]: /components/switch.eufy/
-[switch.fritzbox docs]: /components/switch.fritzbox/
-[switch.hive docs]: /components/switch.hive/
-[switch.vesync docs]: /components/switch.vesync/
-[tts docs]: /components/tts/
-[upnp docs]: /components/upnp/
-[vacuum docs]: /components/vacuum/
-[vacuum.dyson docs]: /components/vacuum.dyson/
-[vacuum.neato docs]: /components/vacuum.neato/
-[vacuum.roomba docs]: /components/vacuum.roomba/
-[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
-[weather.yweather docs]: /components/weather.yweather/
-[zha docs]: /components/zha/
-[#14108]: https://github.com/home-assistant/home-assistant/pull/14108
-[#14113]: https://github.com/home-assistant/home-assistant/pull/14113
-[#14154]: https://github.com/home-assistant/home-assistant/pull/14154
-[#14160]: https://github.com/home-assistant/home-assistant/pull/14160
-[#14163]: https://github.com/home-assistant/home-assistant/pull/14163
-[#14181]: https://github.com/home-assistant/home-assistant/pull/14181
-[#14190]: https://github.com/home-assistant/home-assistant/pull/14190
-[#14196]: https://github.com/home-assistant/home-assistant/pull/14196
-[#14156]: https://github.com/home-assistant/home-assistant/pull/14156
-[@OttoWinter]: https://github.com/OttoWinter
-[@amelchio]: https://github.com/amelchio
-[@balloob]: https://github.com/balloob
-[@cdce8p]: https://github.com/cdce8p
-[@mjg59]: https://github.com/mjg59
-[google_assistant docs]: /components/google_assistant/
-[homekit docs]: /components/homekit/
-[homekit_controller docs]: /components/homekit_controller/
-[light.hue docs]: /components/light.hue/
-[light.tplink docs]: /components/light.tplink/
-[media_player.cast docs]: /components/media_player.cast/
\ No newline at end of file
diff --git a/source/_posts/2018-05-11-release-69.markdown b/source/_posts/2018-05-11-release-69.markdown
deleted file mode 100644
index 4063660e8c..0000000000
--- a/source/_posts/2018-05-11-release-69.markdown
+++ /dev/null
@@ -1,459 +0,0 @@
----
-layout: post
-title: "0.69: TBD - Update date"
-description: "TBD."
-date: 2018-05-05 00:01:00
-date_formatted: "May 11, 2018"
-author: Paulus Schoutsen
-author_twitter: balloob
-comments: true
-categories: Release-Notes
-og_image: /images/blog/2018-05-0.69/components.png
----
-
-
-
-## {% linkable_title New Platforms %}
-
-- New sensor domain expiry ([@masarliev] - [#14067]) ([sensor.domain_expiry docs]) (new-platform)
-- Support Xiaomi Mijia Bluetooth Wireless Temperature and Humidity Sensor ([@ratcashdev] - [#13955]) ([sensor.mitemp_bt docs]) (new-platform)
-- Move RainMachine to component/hub model ([@bachya] - [#14085]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change) (new-platform)
-- Foundation for users ([@balloob] - [#13968]) ([auth docs]) ([http docs]) (new-platform)
-- Add Social Blade Sensor ([@meauxt] - [#14060]) ([sensor.socialblade docs]) ([sensor.uscis docs]) (new-platform)
-- Add PostNL sensor (Dutch Postal Services) ([@iMicknl] - [#12366]) ([sensor.postnl docs]) (new-platform)
-- Issue/add template fans ([@giangvo] - [#12027]) ([fan.template docs]) (new-platform)
-- Matrix Chatbot ([@tinloaf] - [#13355]) ([matrix docs]) ([notify docs]) (breaking change) (new-platform)
-
-## {% linkable_title If you need help... %}
-
-...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
-
-## {% linkable_title Reporting Issues %}
-
-Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
-
-
-## {% linkable_title Breaking Changes %}
-
-- Pollen.com: Added attributes on top 3 allergens ([@bachya] - [#14018]) ([sensor.pollen docs]) (breaking change)
-- Add Sonos device attribute with grouping information ([@amelchio] - [#13553]) ([media_player.sonos docs]) (breaking change)
-- Re-implement HomematicIP cloud to async ([@mxworm] - [#13468]) ([homematicip_cloud docs]) ([sensor.homematicip_cloud docs]) (breaking change)
-- Move RainMachine to component/hub model ([@bachya] - [#14085]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change) (new-platform)
-- System log: make firing event optional ([@balloob] - [#14102]) ([system_log docs]) (breaking change)
-- Disable eliqonline requirement ([@balloob] - [#14156]) ([sensor.eliqonline docs]) (breaking change)
-- Custom component loading cleanup ([@balloob] - [#14211]) (breaking change)
-- Converts RainMachine to hub model (part 2) ([@bachya] - [#14225]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change)
-- Homekit: Changed device_class requirement Humidity Sensor ([@cdce8p] - [#14277]) ([homekit docs]) (breaking change)
-- Sensor device classes ([@cdce8p] - [#14282]) ([sensor docs]) (breaking change)
-- Matrix Chatbot ([@tinloaf] - [#13355]) ([matrix docs]) ([notify docs]) (breaking change) (new-platform)
-
-## {% linkable_title Beta Fixes %}
-
-- Add missing 'sensor' to ABODE_PLATFORMS ([@jloutsenhizer] - [#14313]) ([abode docs]) (beta fix)
-- Add debounce to move_cover ([@cdce8p] - [#14314]) ([homekit docs]) (beta fix)
-- Fix module names for custom components ([@balloob] - [#14317]) (beta fix)
-- Revert custom component loading logic ([@balloob] - [#14327]) (beta fix)
-- fix(hbmqtt): partial packets breaking hbmqtt ([@graffic] - [#14329]) ([mqtt docs]) (beta fix)
-- Fix Yeelight naming ([@syssi])
-
-## {% linkable_title All changes %}
-
-- Pollen.com: Added attributes on top 3 allergens ([@bachya] - [#14018]) ([sensor.pollen docs]) (breaking change)
-- Expose the condition code on condition sensors ([@maddox] - [#14011]) ([sensor.yweather docs])
-- upgrade rfxtrx lib, dimming support for Lighting3 ([@Danielhiversen] - [#14026]) ([rfxtrx docs])
-- Add Accuracy to Google Location Sharing ([@rdbahm] - [#14039]) ([device_tracker docs])
-- bump gogogate2 version ([@dlbroadfoot] - [#14044]) ([cover.gogogate2 docs])
-- device_tracker.ubus: catch ConnectionError ([@stintel] - [#14045]) ([device_tracker docs])
-- Show a notification when a config entry is discovered ([@balloob] - [#14022])
-- deCONZ use forward entry setup ([@Kane610] - [#13990]) ([binary_sensor docs]) ([deconz docs]) ([scene docs]) ([sensor docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([scene.deconz docs]) ([sensor.deconz docs])
-- Bump pyEight version to update API & reduce connection issues ([@mezz64] - [#14058]) ([eight_sleep docs])
-- Bump locationsharinglib to 1.2.2 ([@thelittlefireman] - [#14070]) ([device_tracker docs])
-- Remove excessive debugging in webostv module ([@stephanerosi] - [#14056]) ([media_player.webostv docs])
-- Support new Xiaomi Aqara device model names and LAN protocol 2.0 ([@ileler] - [#13540]) ([xiaomi_aqara docs]) ([binary_sensor.xiaomi_aqara docs]) ([light.xiaomi_aqara docs]) ([sensor.xiaomi_aqara docs]) ([switch.xiaomi_aqara docs])
-- Add devices to Tahoma ([@bakedraccoon] - [#14075]) ([tahoma docs]) ([cover.tahoma docs]) ([sensor.tahoma docs])
-- New sensor domain expiry ([@masarliev] - [#14067]) ([sensor.domain_expiry docs]) (new-platform)
-- Modify weather components for "new" frontend card ([@c727] - [#14076]) ([weather.buienradar docs]) ([weather.darksky docs]) ([weather.openweathermap docs])
-- Add Sonos device attribute with grouping information ([@amelchio] - [#13553]) ([media_player.sonos docs]) (breaking change)
-- Re-implement HomematicIP cloud to async ([@mxworm] - [#13468]) ([homematicip_cloud docs]) ([sensor.homematicip_cloud docs]) (breaking change)
-- Update pyhomematic to 0.1.42 ([@danielperna84] - [#14095]) ([homematic docs])
-- Adds update file_path service to local_file camera ([@robmarkcole] - [#13976]) ([camera.local_file docs])
-- Zone component config entry support ([@Kane610] - [#14059]) ([zone docs])
-- Improve MQTT topic validation ([@OttoWinter] - [#14099]) ([mqtt docs])
-- Fix the optional friendly name of the Yeelight (Closes: #14088) ([@syssi] - [#14110]) ([light.yeelight docs])
-- Update QNAP lib to 0.2.6; handle null temps gracefully ([@colinodell] - [#14117]) ([sensor.qnap docs])
-- Support Xiaomi Mijia Bluetooth Wireless Temperature and Humidity Sensor ([@ratcashdev] - [#13955]) ([sensor.mitemp_bt docs]) (new-platform)
-- Upgrade colorlog to 3.1.4 ([@fabaff] - [#14132])
-- Move RainMachine to component/hub model ([@bachya] - [#14085]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change) (new-platform)
-- Add support for light sensors with 'lx' unit to HomeKit ([@bieniu] - [#14131]) ([homekit docs])
-- Upgrade restrictedpython to 4.0b3 ([@fabaff] - [#14140]) ([python_script docs])
-- Logitech Pop support for emulated_hue component ([@dgraye] - [#12833]) ([emulated_hue docs])
-- Bump pyvizio to 0.0.3 ([@cgarwood] - [#14147]) ([media_player.vizio docs])
-- System log: make firing event optional ([@balloob] - [#14102]) ([system_log docs]) (breaking change)
-- Upgrade pylast to 2.2.0 ([@fabaff] - [#14139]) ([sensor.lastfm docs])
-- Upgrade sqlalchemy to 1.2.7 ([@fabaff] - [#14138])
-- Upgrade tapsaff to 0.2.0 ([@fabaff] - [#14137]) ([binary_sensor.tapsaff docs])
-- Upgrade python-telegram-bot to 10.0.2 ([@fabaff] - [#14144])
-- Upgrade youtube_dl to 2018.04.25 ([@fabaff] - [#14136]) ([media_extractor docs])
-- Clean up HomeKit accessory information characteristics ([@schmittx] - [#14114]) ([homekit docs])
-- Upgrade psutil to 5.4.5 ([@fabaff] - [#14135])
-- Fixed datetime values ([@gives1976] - [#14153]) ([sensor.sql docs])
-- deluge-components-update ([@engrbm87] - [#14016]) ([sensor.deluge docs]) ([switch.deluge docs])
-- Light mqtt_json: Add HS color support ([@OttoWinter] - [#14029]) ([light.mqtt_json docs])
-- Convert more files to async/await syntax ([@OttoWinter] - [#14142])
-- Disable eliqonline requirement ([@balloob] - [#14156]) ([sensor.eliqonline docs]) (breaking change)
-- deCONZ allow unloading of config entry ([@Kane610] - [#14115]) ([binary_sensor docs]) ([deconz docs]) ([scene docs]) ([sensor docs])
-- Upgrade netdisco to 1.4.0 ([@fabaff] - [#14152])
-- Add precipitation to OpenWeatherMap forecast ([@escoand] - [#13971]) ([weather.openweathermap docs])
-- Allow transitioning to colour temp for tradfri ([@Hate-Usernames] - [#14157])
-- Added update_interval to maxcube ([@dingusdk] - [#14143]) ([maxcube docs])
-- zha: Support remotes/buttons ([@rcloran] - [#12528]) ([zha docs]) ([binary_sensor.zha docs])
-- Upgrade numpy to 1.14.3 ([@fabaff] - [#14187]) ([binary_sensor.trend docs]) ([image_processing.opencv docs])
-- Updating darksky default update interval to 5 mins ([@msubra] - [#14195]) ([sensor.darksky docs])
-- Fix TypeError on round(self.humidity) (fixes #13116) ([@mvn23] - [#14174]) ([weather docs])
-- Add room hint support to Google Assistant cloud ([@balloob] - [#14180])
-- Update CODEOWNERS ([@pschmitt] - [#14214])
-- Fixes #14169 (Upgrade pyupnp-async to 0.1.0.2) ([@dgomes] - [#14210]) ([upnp docs])
-- zha: Clean up binary_sensor listener registration/state updates ([@rcloran] - [#14197])
-- HomematicIP cloud: Add logic to check accesspoint connection state ([@sander76] - [#14203]) ([homematicip_cloud docs])
-- Foundation for users ([@balloob] - [#13968]) ([auth docs]) ([http docs]) (new-platform)
-- Allow easy extension of websocket API ([@balloob] - [#14186]) ([frontend docs]) ([websocket_api docs])
-- Change the divisor for total consumption output ([@CM000n] - [#14215]) ([switch.fritzbox docs])
-- Upgrade mypy to 0.590 ([@fabaff] - [#14207])
-- Template Sensor add device_class support ([@OttoWinter] - [#14034]) ([sensor.template docs])
-- Add more parameters for DSMR sensor ([@rubenvandeven] - [#13967]) ([sensor.dsmr docs])
-- Support setting explicit mute value for Panasonic Viera TV ([@blackwind] - [#13954]) ([media_player.panasonic_viera docs])
-- Allow to set a desired update interval for camera_proxy_stream view ([@NovapaX] - [#13350]) ([camera docs])
-- panasonic_viera: Provide unique_id from SSDP UDN, if available ([@scop] - [#13541]) ([media_player.panasonic_viera docs])
-- Custom component loading cleanup ([@balloob] - [#14211]) (breaking change)
-- Buienradar improvements: continuous sensors and unique ID's ([@corneyl] - [#13249]) ([sensor.buienradar docs])
-- add volumio discovery ([@escoand] - [#14220]) ([media_player.volumio docs])
-- Converts RainMachine to hub model (part 2) ([@bachya] - [#14225]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change)
-- Add MQTT Sensor device_class ([@OttoWinter] - [#14033]) ([sensor.mqtt docs])
-- Allow independent control of white level on flux_led component ([@oblogic7] - [#13985]) ([light.flux_led docs])
-- Add Social Blade Sensor ([@meauxt] - [#14060]) ([sensor.socialblade docs]) ([sensor.uscis docs]) (new-platform)
-- UPnP code cleanup ([@dgomes] - [#14235]) ([upnp docs]) ([sensor.upnp docs])
-- Improve config schema of the blackbird component ([@syssi] - [#14007]) ([media_player.blackbird docs])
-- Add support for tracking devices on Netgear access points ([@MatMaul] - [#13331]) ([device_tracker docs])
-- WUnderground unique ids ([@OttoWinter] - [#13311]) ([sensor.wunderground docs])
-- Add PostNL sensor (Dutch Postal Services) ([@iMicknl] - [#12366]) ([sensor.postnl docs]) (new-platform)
-- python_openzwave update config service ([@perosb] - [#12060]) ([zwave docs])
-- Add unique_id to zwave node entity ([@andrey-git] - [#14201]) ([zwave docs])
-- Add prereqs for HomeKit Controller ([@marthoc] - [#14172])
-- Restores switch state, case the switch is optimistic ([@dgomes] - [#14151]) ([switch.mqtt docs])
-- Issue/add template fans ([@giangvo] - [#12027]) ([fan.template docs]) (new-platform)
-- HomeKit - Climate: power state on/off support ([@roiff] - [#14082]) ([homekit docs])
-- Demo Sensor - Added device_class support ([@cdce8p] - [#14269]) ([sensor.demo docs])
-- Re-enable eliqonline requirement ([@molobrakos] - [#14265]) ([sensor.eliqonline docs])
-- Add fetching camera thumbnails over websocket ([@balloob] - [#14231]) ([camera docs]) ([frontend docs]) ([image_processing docs]) ([microsoft_face docs]) ([websocket_api docs])
-- Allow fetching media player covers via websocket connection ([@balloob] - [#14233]) ([media_player docs])
-- Fix ZWave light brightness ([@cdce8p] - [#14261]) ([light.zwave docs])
-- fix check config not working after #14211 ([@fanthos] - [#14259])
-- Issue Template Fix CRLF ([@OttoWinter] - [#14283])
-- Upgrade attrs to 18.1.0 ([@fabaff] - [#14281])
-- Update HAP-python to 2.0.0 ([@cdce8p] - [#14278]) ([homekit docs])
-- Upgrade holidays to 0.9.5 ([@fabaff] - [#14274]) ([binary_sensor.workday docs])
-- Homekit: Changed device_class requirement Humidity Sensor ([@cdce8p] - [#14277]) ([homekit docs]) (breaking change)
-- HomeKit: Support triggered state for alarm_control_panel ([@schmittx] - [#14285]) ([homekit docs])
-- Upgrade astral to 1.6.1 ([@fabaff] - [#14297])
-- BOM Weather throttle fix ([@nickw444] - [#14234]) ([sensor.bom docs])
-- Publish attributes unconditionally ([@blackwind] - [#14179]) ([mqtt_statestream docs])
-- Sensor device classes ([@cdce8p] - [#14282]) ([sensor docs]) (breaking change)
-- Matrix Chatbot ([@tinloaf] - [#13355]) ([matrix docs]) ([notify docs]) (breaking change) (new-platform)
-- deCONZ add new device without restart ([@Kane610] - [#14221]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs])
-- Add alarmdotcom sensor status ([@jnewland] - [#14254]) ([alarm_control_panel.alarmdotcom docs])
-- Add domain to labels and count state changes to Prometheus ([@jnewland] - [#14253]) ([prometheus docs])
-- Add support for max_volume ([@relvacode] - [#13822]) ([media_player.onkyo docs])
-- Refactor ImageProcessingFaceEntity ([@robmarkcole] - [#14296]) ([image_processing docs]) ([image_processing.demo docs]) ([image_processing.dlib_face_detect docs]) ([image_processing.dlib_face_identify docs]) ([image_processing.microsoft_face_detect docs]) ([image_processing.microsoft_face_identify docs])
-- Onkyo: SUPPORT_VOLUME_STEP ([@rsmeral] - [#14299]) ([media_player.onkyo docs])
-- Add All-Linking capabilities ([@teharris1] - [#14065]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([fan.insteon_plm docs]) ([light.insteon_plm docs]) ([sensor.insteon_plm docs]) ([switch.insteon_plm docs])
-- Add missing 'sensor' to ABODE_PLATFORMS ([@jloutsenhizer] - [#14313]) ([abode docs]) (beta fix)
-- Add debounce to move_cover ([@cdce8p] - [#14314]) ([homekit docs]) (beta fix)
-- Fix module names for custom components ([@balloob] - [#14317]) (beta fix)
-- Revert custom component loading logic ([@balloob] - [#14327]) (beta fix)
-- fix(hbmqtt): partial packets breaking hbmqtt ([@graffic] - [#14329]) ([mqtt docs]) (beta fix)
-
-[#12027]: https://github.com/home-assistant/home-assistant/pull/12027
-[#12060]: https://github.com/home-assistant/home-assistant/pull/12060
-[#12366]: https://github.com/home-assistant/home-assistant/pull/12366
-[#12528]: https://github.com/home-assistant/home-assistant/pull/12528
-[#12833]: https://github.com/home-assistant/home-assistant/pull/12833
-[#13249]: https://github.com/home-assistant/home-assistant/pull/13249
-[#13311]: https://github.com/home-assistant/home-assistant/pull/13311
-[#13331]: https://github.com/home-assistant/home-assistant/pull/13331
-[#13350]: https://github.com/home-assistant/home-assistant/pull/13350
-[#13355]: https://github.com/home-assistant/home-assistant/pull/13355
-[#13468]: https://github.com/home-assistant/home-assistant/pull/13468
-[#13540]: https://github.com/home-assistant/home-assistant/pull/13540
-[#13541]: https://github.com/home-assistant/home-assistant/pull/13541
-[#13553]: https://github.com/home-assistant/home-assistant/pull/13553
-[#13822]: https://github.com/home-assistant/home-assistant/pull/13822
-[#13954]: https://github.com/home-assistant/home-assistant/pull/13954
-[#13955]: https://github.com/home-assistant/home-assistant/pull/13955
-[#13967]: https://github.com/home-assistant/home-assistant/pull/13967
-[#13968]: https://github.com/home-assistant/home-assistant/pull/13968
-[#13971]: https://github.com/home-assistant/home-assistant/pull/13971
-[#13976]: https://github.com/home-assistant/home-assistant/pull/13976
-[#13985]: https://github.com/home-assistant/home-assistant/pull/13985
-[#13990]: https://github.com/home-assistant/home-assistant/pull/13990
-[#14007]: https://github.com/home-assistant/home-assistant/pull/14007
-[#14011]: https://github.com/home-assistant/home-assistant/pull/14011
-[#14016]: https://github.com/home-assistant/home-assistant/pull/14016
-[#14018]: https://github.com/home-assistant/home-assistant/pull/14018
-[#14022]: https://github.com/home-assistant/home-assistant/pull/14022
-[#14026]: https://github.com/home-assistant/home-assistant/pull/14026
-[#14029]: https://github.com/home-assistant/home-assistant/pull/14029
-[#14033]: https://github.com/home-assistant/home-assistant/pull/14033
-[#14034]: https://github.com/home-assistant/home-assistant/pull/14034
-[#14039]: https://github.com/home-assistant/home-assistant/pull/14039
-[#14044]: https://github.com/home-assistant/home-assistant/pull/14044
-[#14045]: https://github.com/home-assistant/home-assistant/pull/14045
-[#14056]: https://github.com/home-assistant/home-assistant/pull/14056
-[#14058]: https://github.com/home-assistant/home-assistant/pull/14058
-[#14059]: https://github.com/home-assistant/home-assistant/pull/14059
-[#14060]: https://github.com/home-assistant/home-assistant/pull/14060
-[#14065]: https://github.com/home-assistant/home-assistant/pull/14065
-[#14067]: https://github.com/home-assistant/home-assistant/pull/14067
-[#14070]: https://github.com/home-assistant/home-assistant/pull/14070
-[#14075]: https://github.com/home-assistant/home-assistant/pull/14075
-[#14076]: https://github.com/home-assistant/home-assistant/pull/14076
-[#14082]: https://github.com/home-assistant/home-assistant/pull/14082
-[#14085]: https://github.com/home-assistant/home-assistant/pull/14085
-[#14095]: https://github.com/home-assistant/home-assistant/pull/14095
-[#14099]: https://github.com/home-assistant/home-assistant/pull/14099
-[#14102]: https://github.com/home-assistant/home-assistant/pull/14102
-[#14110]: https://github.com/home-assistant/home-assistant/pull/14110
-[#14114]: https://github.com/home-assistant/home-assistant/pull/14114
-[#14115]: https://github.com/home-assistant/home-assistant/pull/14115
-[#14117]: https://github.com/home-assistant/home-assistant/pull/14117
-[#14131]: https://github.com/home-assistant/home-assistant/pull/14131
-[#14132]: https://github.com/home-assistant/home-assistant/pull/14132
-[#14135]: https://github.com/home-assistant/home-assistant/pull/14135
-[#14136]: https://github.com/home-assistant/home-assistant/pull/14136
-[#14137]: https://github.com/home-assistant/home-assistant/pull/14137
-[#14138]: https://github.com/home-assistant/home-assistant/pull/14138
-[#14139]: https://github.com/home-assistant/home-assistant/pull/14139
-[#14140]: https://github.com/home-assistant/home-assistant/pull/14140
-[#14142]: https://github.com/home-assistant/home-assistant/pull/14142
-[#14143]: https://github.com/home-assistant/home-assistant/pull/14143
-[#14144]: https://github.com/home-assistant/home-assistant/pull/14144
-[#14147]: https://github.com/home-assistant/home-assistant/pull/14147
-[#14151]: https://github.com/home-assistant/home-assistant/pull/14151
-[#14152]: https://github.com/home-assistant/home-assistant/pull/14152
-[#14153]: https://github.com/home-assistant/home-assistant/pull/14153
-[#14156]: https://github.com/home-assistant/home-assistant/pull/14156
-[#14157]: https://github.com/home-assistant/home-assistant/pull/14157
-[#14172]: https://github.com/home-assistant/home-assistant/pull/14172
-[#14174]: https://github.com/home-assistant/home-assistant/pull/14174
-[#14179]: https://github.com/home-assistant/home-assistant/pull/14179
-[#14180]: https://github.com/home-assistant/home-assistant/pull/14180
-[#14186]: https://github.com/home-assistant/home-assistant/pull/14186
-[#14187]: https://github.com/home-assistant/home-assistant/pull/14187
-[#14195]: https://github.com/home-assistant/home-assistant/pull/14195
-[#14197]: https://github.com/home-assistant/home-assistant/pull/14197
-[#14201]: https://github.com/home-assistant/home-assistant/pull/14201
-[#14203]: https://github.com/home-assistant/home-assistant/pull/14203
-[#14207]: https://github.com/home-assistant/home-assistant/pull/14207
-[#14210]: https://github.com/home-assistant/home-assistant/pull/14210
-[#14211]: https://github.com/home-assistant/home-assistant/pull/14211
-[#14214]: https://github.com/home-assistant/home-assistant/pull/14214
-[#14215]: https://github.com/home-assistant/home-assistant/pull/14215
-[#14220]: https://github.com/home-assistant/home-assistant/pull/14220
-[#14221]: https://github.com/home-assistant/home-assistant/pull/14221
-[#14225]: https://github.com/home-assistant/home-assistant/pull/14225
-[#14231]: https://github.com/home-assistant/home-assistant/pull/14231
-[#14233]: https://github.com/home-assistant/home-assistant/pull/14233
-[#14234]: https://github.com/home-assistant/home-assistant/pull/14234
-[#14235]: https://github.com/home-assistant/home-assistant/pull/14235
-[#14253]: https://github.com/home-assistant/home-assistant/pull/14253
-[#14254]: https://github.com/home-assistant/home-assistant/pull/14254
-[#14259]: https://github.com/home-assistant/home-assistant/pull/14259
-[#14261]: https://github.com/home-assistant/home-assistant/pull/14261
-[#14265]: https://github.com/home-assistant/home-assistant/pull/14265
-[#14269]: https://github.com/home-assistant/home-assistant/pull/14269
-[#14274]: https://github.com/home-assistant/home-assistant/pull/14274
-[#14277]: https://github.com/home-assistant/home-assistant/pull/14277
-[#14278]: https://github.com/home-assistant/home-assistant/pull/14278
-[#14281]: https://github.com/home-assistant/home-assistant/pull/14281
-[#14282]: https://github.com/home-assistant/home-assistant/pull/14282
-[#14283]: https://github.com/home-assistant/home-assistant/pull/14283
-[#14285]: https://github.com/home-assistant/home-assistant/pull/14285
-[#14296]: https://github.com/home-assistant/home-assistant/pull/14296
-[#14297]: https://github.com/home-assistant/home-assistant/pull/14297
-[#14299]: https://github.com/home-assistant/home-assistant/pull/14299
-[#14313]: https://github.com/home-assistant/home-assistant/pull/14313
-[#14314]: https://github.com/home-assistant/home-assistant/pull/14314
-[#14317]: https://github.com/home-assistant/home-assistant/pull/14317
-[#14327]: https://github.com/home-assistant/home-assistant/pull/14327
-[#14329]: https://github.com/home-assistant/home-assistant/pull/14329
-[@CM000n]: https://github.com/CM000n
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@Hate-Usernames]: https://github.com/Hate-Usernames
-[@Kane610]: https://github.com/Kane610
-[@MatMaul]: https://github.com/MatMaul
-[@NovapaX]: https://github.com/NovapaX
-[@OttoWinter]: https://github.com/OttoWinter
-[@amelchio]: https://github.com/amelchio
-[@andrey-git]: https://github.com/andrey-git
-[@bachya]: https://github.com/bachya
-[@bakedraccoon]: https://github.com/bakedraccoon
-[@balloob]: https://github.com/balloob
-[@bieniu]: https://github.com/bieniu
-[@blackwind]: https://github.com/blackwind
-[@c727]: https://github.com/c727
-[@cdce8p]: https://github.com/cdce8p
-[@cgarwood]: https://github.com/cgarwood
-[@colinodell]: https://github.com/colinodell
-[@corneyl]: https://github.com/corneyl
-[@danielperna84]: https://github.com/danielperna84
-[@dgomes]: https://github.com/dgomes
-[@dgraye]: https://github.com/dgraye
-[@dingusdk]: https://github.com/dingusdk
-[@dlbroadfoot]: https://github.com/dlbroadfoot
-[@engrbm87]: https://github.com/engrbm87
-[@escoand]: https://github.com/escoand
-[@fabaff]: https://github.com/fabaff
-[@fanthos]: https://github.com/fanthos
-[@giangvo]: https://github.com/giangvo
-[@gives1976]: https://github.com/gives1976
-[@graffic]: https://github.com/graffic
-[@iMicknl]: https://github.com/iMicknl
-[@ileler]: https://github.com/ileler
-[@jloutsenhizer]: https://github.com/jloutsenhizer
-[@jnewland]: https://github.com/jnewland
-[@maddox]: https://github.com/maddox
-[@marthoc]: https://github.com/marthoc
-[@masarliev]: https://github.com/masarliev
-[@meauxt]: https://github.com/meauxt
-[@mezz64]: https://github.com/mezz64
-[@molobrakos]: https://github.com/molobrakos
-[@msubra]: https://github.com/msubra
-[@mvn23]: https://github.com/mvn23
-[@mxworm]: https://github.com/mxworm
-[@nickw444]: https://github.com/nickw444
-[@oblogic7]: https://github.com/oblogic7
-[@perosb]: https://github.com/perosb
-[@pschmitt]: https://github.com/pschmitt
-[@ratcashdev]: https://github.com/ratcashdev
-[@rcloran]: https://github.com/rcloran
-[@rdbahm]: https://github.com/rdbahm
-[@relvacode]: https://github.com/relvacode
-[@robmarkcole]: https://github.com/robmarkcole
-[@roiff]: https://github.com/roiff
-[@rsmeral]: https://github.com/rsmeral
-[@rubenvandeven]: https://github.com/rubenvandeven
-[@sander76]: https://github.com/sander76
-[@schmittx]: https://github.com/schmittx
-[@scop]: https://github.com/scop
-[@stephanerosi]: https://github.com/stephanerosi
-[@stintel]: https://github.com/stintel
-[@syssi]: https://github.com/syssi
-[@teharris1]: https://github.com/teharris1
-[@thelittlefireman]: https://github.com/thelittlefireman
-[@tinloaf]: https://github.com/tinloaf
-[abode docs]: /components/abode/
-[alarm_control_panel.alarmdotcom docs]: /components/alarm_control_panel.alarmdotcom/
-[auth docs]: /components/auth/
-[binary_sensor docs]: /components/binary_sensor/
-[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
-[binary_sensor.insteon_plm docs]: /components/binary_sensor.insteon_plm/
-[binary_sensor.tapsaff docs]: /components/binary_sensor.tapsaff/
-[binary_sensor.trend docs]: /components/binary_sensor.trend/
-[binary_sensor.workday docs]: /components/binary_sensor.workday/
-[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
-[binary_sensor.zha docs]: /components/binary_sensor.zha/
-[camera docs]: /components/camera/
-[camera.local_file docs]: /components/camera.local_file/
-[cover.gogogate2 docs]: /components/cover.gogogate2/
-[cover.tahoma docs]: /components/cover.tahoma/
-[deconz docs]: /components/deconz/
-[device_tracker docs]: /components/device_tracker/
-[eight_sleep docs]: /components/eight_sleep/
-[emulated_hue docs]: /components/emulated_hue/
-[fan.insteon_plm docs]: /components/fan.insteon_plm/
-[fan.template docs]: /components/fan.template/
-[frontend docs]: /components/frontend/
-[homekit docs]: /components/homekit/
-[homematic docs]: /components/homematic/
-[homematicip_cloud docs]: /components/homematicip_cloud/
-[http docs]: /components/http/
-[image_processing docs]: /components/image_processing/
-[image_processing.demo docs]: /components/image_processing.demo/
-[image_processing.dlib_face_detect docs]: /components/image_processing.dlib_face_detect/
-[image_processing.dlib_face_identify docs]: /components/image_processing.dlib_face_identify/
-[image_processing.microsoft_face_detect docs]: /components/image_processing.microsoft_face_detect/
-[image_processing.microsoft_face_identify docs]: /components/image_processing.microsoft_face_identify/
-[image_processing.opencv docs]: /components/image_processing.opencv/
-[insteon_plm docs]: /components/insteon_plm/
-[light.deconz docs]: /components/light.deconz/
-[light.flux_led docs]: /components/light.flux_led/
-[light.insteon_plm docs]: /components/light.insteon_plm/
-[light.mqtt_json docs]: /components/light.mqtt_json/
-[light.xiaomi_aqara docs]: /components/light.xiaomi_aqara/
-[light.yeelight docs]: /components/light.yeelight/
-[light.zwave docs]: /components/light.zwave/
-[matrix docs]: /components/matrix/
-[maxcube docs]: /components/maxcube/
-[media_extractor docs]: /components/media_extractor/
-[media_player docs]: /components/media_player/
-[media_player.blackbird docs]: /components/media_player.blackbird/
-[media_player.onkyo docs]: /components/media_player.onkyo/
-[media_player.panasonic_viera docs]: /components/media_player.panasonic_viera/
-[media_player.sonos docs]: /components/media_player.sonos/
-[media_player.vizio docs]: /components/media_player.vizio/
-[media_player.volumio docs]: /components/media_player.volumio/
-[media_player.webostv docs]: /components/media_player.webostv/
-[microsoft_face docs]: /components/microsoft_face/
-[mqtt docs]: /components/mqtt/
-[mqtt_statestream docs]: /components/mqtt_statestream/
-[notify docs]: /components/notify/
-[prometheus docs]: /components/prometheus/
-[python_script docs]: /components/python_script/
-[rainmachine docs]: /components/rainmachine/
-[rfxtrx docs]: /components/rfxtrx/
-[scene docs]: /components/scene/
-[scene.deconz docs]: /components/scene.deconz/
-[sensor docs]: /components/sensor/
-[sensor.bom docs]: /components/sensor.bom/
-[sensor.buienradar docs]: /components/sensor.buienradar/
-[sensor.darksky docs]: /components/sensor.darksky/
-[sensor.deconz docs]: /components/sensor.deconz/
-[sensor.deluge docs]: /components/sensor.deluge/
-[sensor.demo docs]: /components/sensor.demo/
-[sensor.domain_expiry docs]: /components/sensor.domain_expiry/
-[sensor.dsmr docs]: /components/sensor.dsmr/
-[sensor.eliqonline docs]: /components/sensor.eliqonline/
-[sensor.homematicip_cloud docs]: /components/sensor.homematicip_cloud/
-[sensor.insteon_plm docs]: /components/sensor.insteon_plm/
-[sensor.lastfm docs]: /components/sensor.lastfm/
-[sensor.mitemp_bt docs]: /components/sensor.mitemp_bt/
-[sensor.mqtt docs]: /components/sensor.mqtt/
-[sensor.pollen docs]: /components/sensor.pollen/
-[sensor.postnl docs]: /components/sensor.postnl/
-[sensor.qnap docs]: /components/sensor.qnap/
-[sensor.socialblade docs]: /components/sensor.socialblade/
-[sensor.sql docs]: /components/sensor.sql/
-[sensor.tahoma docs]: /components/sensor.tahoma/
-[sensor.template docs]: /components/sensor.template/
-[sensor.upnp docs]: /components/sensor.upnp/
-[sensor.uscis docs]: /components/sensor.uscis/
-[sensor.wunderground docs]: /components/sensor.wunderground/
-[sensor.xiaomi_aqara docs]: /components/sensor.xiaomi_aqara/
-[sensor.yweather docs]: /components/sensor.yweather/
-[switch.deluge docs]: /components/switch.deluge/
-[switch.fritzbox docs]: /components/switch.fritzbox/
-[switch.insteon_plm docs]: /components/switch.insteon_plm/
-[switch.mqtt docs]: /components/switch.mqtt/
-[switch.rainmachine docs]: /components/switch.rainmachine/
-[switch.xiaomi_aqara docs]: /components/switch.xiaomi_aqara/
-[system_log docs]: /components/system_log/
-[tahoma docs]: /components/tahoma/
-[upnp docs]: /components/upnp/
-[weather docs]: /components/weather/
-[weather.buienradar docs]: /components/weather.buienradar/
-[weather.darksky docs]: /components/weather.darksky/
-[weather.openweathermap docs]: /components/weather.openweathermap/
-[websocket_api docs]: /components/websocket_api/
-[xiaomi_aqara docs]: /components/xiaomi_aqara/
-[zha docs]: /components/zha/
-[zone docs]: /components/zone/
-[zwave docs]: /components/zwave/
diff --git a/source/addons/index.html b/source/addons/index.html
index 413106dd86..5abc6504b7 100644
--- a/source/addons/index.html
+++ b/source/addons/index.html
@@ -16,10 +16,6 @@ regenerate: false
Check the Hass.io forums for add-on repositories managed by the community.
-Add-ons are only available if you've used the Hass.io installer. If you installed Home Assistant using any other method then you cannot use add-ons (but you can achieve the same result manually). -
- {% assign addons = site.addons | sort: 'title' %}The Home Assistant Cloud is currently free and will become part of the upcoming Community Support Package. [Learn more](/blog/2017/12/17/introducing-home-assistant-cloud/)
- -The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services. The following integrations are currently available: - - - [Amazon Alexa (Amazon Echo)](/cloud/alexa/) - - [Google Assistant (Google Home)](/cloud/google_assistant/) - -### {% linkable_title How does it work? %} - -The Home Assistant Cloud has been designed with security in mind. When you activate the Cloud component, your instance will create a secure connection to the Home Assistant Cloud. There is no need for any further configuration or to expose your instance to the internet. - -Integrations like Alexa or Google will deliver messages to our cloud which we will forward to your local instance for processing. We just forward the response back. This means that we do not have to store the state of your house in our cloud, we’re just the messenger! - -You can find a list of frequently asked questions (and their answers) in [this blog post](/blog/2017/12/17/introducing-home-assistant-cloud/#faq). - -### {% linkable_title Enabling the cloud %} - -The Home Assistant Cloud is enabled by default. If not, add this to your configuration: - -```yaml -# Example configuration.yaml entry to enable the cloud component -cloud: -``` - -Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your configuration.yaml` file. - -```yaml -config: -``` diff --git a/source/code_of_conduct/index.markdown b/source/code_of_conduct/index.markdown index 57de40dede..f67555210b 100644 --- a/source/code_of_conduct/index.markdown +++ b/source/code_of_conduct/index.markdown @@ -87,4 +87,4 @@ This Code of Conduct was first adopted January 21st, 2017 and announced in [this [homepage]: http://contributor-covenant.org [version]: http://contributor-covenant.org/version/1/4/ [email]: mailto:safety@home-assistant.io -[coc-blog]: /blog/2017/01/21/home-assistant-governance/ +[coc-blog]: https://home-assistant.io/blog/2017/01/21/home-assistant-governance/ diff --git a/source/demo/frontend.html b/source/demo/frontend.html index e96a4c7a38..0cb5b14886 100644 --- a/source/demo/frontend.html +++ b/source/demo/frontend.html @@ -2,4 +2,4 @@ },_distributeDirtyRoots:function(){for(var e,t=this.shadyRoot._dirtyRoots,o=0,i=t.length;o
Home Assistant
- 
pip3 install homeassistant
hass --open-uiHere are some resources to get started.configuration.yaml and disable the introduction component.[[stateObj.attributes.description]] [[stateObj.attributes.link_name]]
[[stateObj.attributes.errors]]