@@ -72,7 +68,7 @@ logger:
#### 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.
Edit `/mnt/user/appdata/letsencrypt/fail2ban/jail.local` and append the following to the end of the file:
diff --git a/source/_integrations/fan.markdown b/source/_integrations/fan.markdown
index 648ffb98b66..4ab86e1aa1e 100644
--- a/source/_integrations/fan.markdown
+++ b/source/_integrations/fan.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to setup Fan devices within Home Assistant.
ha_category:
- Fan
ha_release: 0.27
+ha_iot_class: ~
ha_quality_scale: internal
ha_domain: fan
---
@@ -19,13 +20,13 @@ Available services:
### Service `fan.set_speed`
-Sets the speed for fan device
+Sets the speed for fan device.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
@@ -48,7 +49,7 @@ automation:
### Service `fan.set_direction`
-Sets the rotation for fan device
+Sets the rotation for fan device.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
@@ -71,7 +72,7 @@ automation:
### Service `fan.oscillate`
-Sets the oscillation for fan device
+Sets the oscillation for fan device.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
diff --git a/source/_integrations/feedreader.markdown b/source/_integrations/feedreader.markdown
index 61854bb9565..e7f3379d720 100644
--- a/source/_integrations/feedreader.markdown
+++ b/source/_integrations/feedreader.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate RSS feeds into Home Assistant.
ha_category:
- Other
ha_release: 0.18
+ha_iot_class: Cloud Polling
ha_domain: feedreader
---
diff --git a/source/_integrations/filter.markdown b/source/_integrations/filter.markdown
index dfb8eb17227..80d5469f727 100644
--- a/source/_integrations/filter.markdown
+++ b/source/_integrations/filter.markdown
@@ -17,7 +17,7 @@ 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](/lovelace/history-graph/) component.
## Configuration
diff --git a/source/_integrations/flock.markdown b/source/_integrations/flock.markdown
index 7c9b9c3e799..07978084b99 100644
--- a/source/_integrations/flock.markdown
+++ b/source/_integrations/flock.markdown
@@ -16,13 +16,13 @@ The `flock` platform uses [Flock.com](https://flock.com) to deliver notification
Go to the [Flock.com Admin website](https://admin.flock.com/#!/webhooks) and create a new "Incoming Webhooks". Choose a channel to send the notifications from Home Assistant to, specify a name and press *Save and Generate URL*.
You will need the last part of the URL which is the `access_token` for your room.
## Configuration
diff --git a/source/_integrations/flume.markdown b/source/_integrations/flume.markdown
index 5c4811e5585..33ed0e10750 100644
--- a/source/_integrations/flume.markdown
+++ b/source/_integrations/flume.markdown
@@ -12,13 +12,13 @@ ha_codeowners:
ha_domain: flume
---
-The `flume` sensor will show you the current [flume](https://portal.flumetech.com/) status for the given Device ID.
+The `flume` sensor will show you the current [flume](https://portal.flumewater.com) status for the given Device ID.
Flume monitors the real-time status of your home water meter. Allowing the end-user to detect small leaks, gain real-time information on household water consumption, set water goals and budgets, and receive push notifications when suspicious water activities occur.
## Configuration
-You can find your Client ID and Client Secret under "API Access" on the [settings page](https://portal.flumetech.com/#settings).
+You can find your Client ID and Client Secret under "API Access" on the [settings page](https://portal.flumewater.com/#settings).
To add `Flume` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
diff --git a/source/_integrations/free_mobile.markdown b/source/_integrations/free_mobile.markdown
index 0d5af30f4d1..47a3e4b786f 100644
--- a/source/_integrations/free_mobile.markdown
+++ b/source/_integrations/free_mobile.markdown
@@ -33,6 +33,11 @@ notify:
```
{% configuration %}
+name:
+ description: "The optional parameter name allows multiple notifiers to be created. The notifier will bind to the service notify.NOTIFIER_NAME."
+ required: false
+ type: string
+ default: notify
username:
description: This is the id given by FreeMobile to access to your online account.
required: true
diff --git a/source/_integrations/fritz.markdown b/source/_integrations/fritz.markdown
index 19741dfe9b6..e38f2e955da 100644
--- a/source/_integrations/fritz.markdown
+++ b/source/_integrations/fritz.markdown
@@ -5,6 +5,7 @@ ha_category:
- Presence Detection
ha_release: '0.10'
ha_domain: fritz
+ha_iot_class: Local Polling
---
The `fritz` platform offers presence detection by looking at connected devices to a [AVM FRITZ!Box](https://avm.de/produkte/fritzbox/) based router.
diff --git a/source/_integrations/fritzbox.markdown b/source/_integrations/fritzbox.markdown
index 4e012162ab6..31564825f5a 100644
--- a/source/_integrations/fritzbox.markdown
+++ b/source/_integrations/fritzbox.markdown
@@ -25,7 +25,7 @@ There is currently support for the following device types within Home Assistant:
- [FRITZ!Box 6490 Cable](https://en.avm.de/products/fritzbox/fritzbox-6490-cable/)
- [FRITZ!Box 7590](https://en.avm.de/products/fritzbox/fritzbox-7590/)
-- [FRITZ!Box 7490](https://en.avm.de/products/fritzbox/fritzbox-7490/)
+- [FRITZ!Box 7490](https://en.avm.de/service/fritzbox/fritzbox-7490/overview/)
- [FRITZ!Box 7430](https://en.avm.de/products/fritzbox/fritzbox-7430/)
- [FRITZ!DECT 200](https://en.avm.de/products/fritzdect/fritzdect-200/)
- [FRITZ!DECT 301](https://en.avm.de/products/fritzdect/fritzdect-301/)
diff --git a/source/_integrations/frontend.markdown b/source/_integrations/frontend.markdown
index d62267162bb..17c11e774ad 100644
--- a/source/_integrations/frontend.markdown
+++ b/source/_integrations/frontend.markdown
@@ -4,6 +4,7 @@ description: Offers a frontend to Home Assistant.
ha_category:
- Other
ha_release: 0.7
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/frontend'
diff --git a/source/_integrations/garadget.markdown b/source/_integrations/garadget.markdown
index 0b60db49f8b..d9bfcaef045 100644
--- a/source/_integrations/garadget.markdown
+++ b/source/_integrations/garadget.markdown
@@ -67,7 +67,7 @@ If provided, the **access_token** will be used, otherwise the **username** and *
## Example
{% raw %}
diff --git a/source/_integrations/geizhals.markdown b/source/_integrations/geizhals.markdown
index fd725ccbf52..415449d6159 100644
--- a/source/_integrations/geizhals.markdown
+++ b/source/_integrations/geizhals.markdown
@@ -1,7 +1,6 @@
---
title: Geizhals
description: Instructions on how to integrate a Geizhals sensor into Home Assistant.
-logo: geizhals.png
ha_category:
- Sensor
ha_iot_class: Cloud Polling
diff --git a/source/_integrations/geniushub.markdown b/source/_integrations/geniushub.markdown
index 035fcb20f4e..eac41e90fae 100644
--- a/source/_integrations/geniushub.markdown
+++ b/source/_integrations/geniushub.markdown
@@ -180,7 +180,7 @@ The hub does not have to be in the same subnet as your Home Assistant server.
This option is recommended only if Option 1 does not work. The MAC address should match that written on the back of the Hub.
-- Requires a **hub token** obtained from [my.geniushub.co.uk/tokens](https://my.geniushub.co.uk/tokens).
+- Requires a **hub token** obtained from [my.geniushub.co.uk](https://my.geniushub.co.uk/).
- Uses the v1 API - which is well-documented.
- Polls Heat Genius' own servers (so is slower, say ~5-10s response time).
- You should use the Hub's MAC address (although any valid MAC will do).
diff --git a/source/_integrations/geo_location.markdown b/source/_integrations/geo_location.markdown
index 976afa5e2b4..9ac2f85b2d3 100644
--- a/source/_integrations/geo_location.markdown
+++ b/source/_integrations/geo_location.markdown
@@ -1,6 +1,8 @@
---
title: Geolocation
description: Instructions on how to integrate geolocation aware platforms into Home Assistant.
+ha_category:
+ - Geolocation
logo: geo_location.png
ha_release: 0.78
ha_domain: geo_location
diff --git a/source/_integrations/geo_rss_events.markdown b/source/_integrations/geo_rss_events.markdown
index fabb67fa044..9e512cd9b1f 100644
--- a/source/_integrations/geo_rss_events.markdown
+++ b/source/_integrations/geo_rss_events.markdown
@@ -15,7 +15,7 @@ The `geo_rss_events` sensor retrieves events from a GeoRSS feed and shows inform
This sensor is particularly useful if events occur unexpectedly in the vicinity of the home while the GeoRSS feed also contains many events representing distant unrelated entries. Typical examples are bush fires alerts or earthquakes.
The reference point for comparing the distance is by default defined by `latitude` and `longitude` in the basic configuration.
diff --git a/source/_integrations/geonetnz_volcano.markdown b/source/_integrations/geonetnz_volcano.markdown
index 209839d4d89..ead5d2fd47c 100644
--- a/source/_integrations/geonetnz_volcano.markdown
+++ b/source/_integrations/geonetnz_volcano.markdown
@@ -25,11 +25,11 @@ to show on the default map automatically.
The data is updated every 5 minutes.
diff --git a/source/_integrations/gitter.markdown b/source/_integrations/gitter.markdown
index 0a76d463cce..9af9cbbc216 100644
--- a/source/_integrations/gitter.markdown
+++ b/source/_integrations/gitter.markdown
@@ -3,6 +3,7 @@ title: Gitter
description: Instructions on how to integrate a Gitter room sensor with Home Assistant
ha_category:
- Sensor
+ha_iot_class: Cloud Polling
ha_release: 0.47
ha_codeowners:
- '@fabaff'
diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown
index 12a10dd1175..47dd2a41866 100644
--- a/source/_integrations/google_assistant.markdown
+++ b/source/_integrations/google_assistant.markdown
@@ -5,6 +5,7 @@ ha_category:
- Voice
featured: true
ha_release: 0.56
+ha_iot_class: Cloud Push
ha_codeowners:
- '@home-assistant/cloud'
ha_domain: google_assistant
diff --git a/source/_integrations/google_domains.markdown b/source/_integrations/google_domains.markdown
index 34d2e7bc35b..bb9ea6df8a1 100644
--- a/source/_integrations/google_domains.markdown
+++ b/source/_integrations/google_domains.markdown
@@ -5,6 +5,7 @@ ha_category:
- Network
ha_release: 0.57
ha_domain: google_domains
+ha_iot_class: Cloud Polling
---
With the Google Domains integration you can keep your Google Domains record up to date.
diff --git a/source/_integrations/gpslogger.markdown b/source/_integrations/gpslogger.markdown
index a9e756e3bde..cbc50891522 100644
--- a/source/_integrations/gpslogger.markdown
+++ b/source/_integrations/gpslogger.markdown
@@ -17,7 +17,7 @@ To configure GPSLogger, you must set it up via the integrations panel in the con
## Setup on your smartphone
-Install [GPSLogger for Android](https://play.google.com/store/apps/details?id=com.mendhak.gpslogger) on your device.
+Install GPSLogger for Android from [GitHub](https://github.com/mendhak/gpslogger/releases) or [F-Droid](https://apt.izzysoft.de/fdroid/index/apk/com.mendhak.gpslogger) on your device.
After the launch, go to **General Options**. Enable **Start on bootup** and **Start on app launch**.
diff --git a/source/_integrations/group.markdown b/source/_integrations/group.markdown
index ed1c4b9b3ea..0d38cfa24a5 100644
--- a/source/_integrations/group.markdown
+++ b/source/_integrations/group.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to setup groups within Home Assistant.
ha_category:
- Organization
ha_release: pre 0.7
+ha_iot_class: Calculated
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
@@ -12,7 +13,7 @@ ha_domain: group
Groups allow the user to combine multiple entities into one.
-Check the **States**
page from the **Developer Tools** and browse the **Current entities:** listing for all available entities.
+Check **Developer Tools** -> **States** and browse the **Current entities:** listing for all available entities.
```yaml
# Example configuration.yaml entry
diff --git a/source/_integrations/hangouts.markdown b/source/_integrations/hangouts.markdown
index 789a71b0143..b550738840b 100644
--- a/source/_integrations/hangouts.markdown
+++ b/source/_integrations/hangouts.markdown
@@ -7,6 +7,7 @@ ha_category:
ha_release: 0.77
ha_config_flow: true
ha_domain: hangouts
+ha_iot_class: Cloud Push
---
This integration allows you to send messages to [Google Hangouts](https://hangouts.google.com) conversations, as well as to react to messages in conversations. Reacting to commands is accomplished by firing an event when one of the configured commands is triggered. Home Assistant will impersonate a Smartisan YQ603 phone which will then show up in your Google devices.
diff --git a/source/_integrations/heos.markdown b/source/_integrations/heos.markdown
index 298501dc42b..e328a901036 100644
--- a/source/_integrations/heos.markdown
+++ b/source/_integrations/heos.markdown
@@ -11,7 +11,7 @@ ha_codeowners:
ha_domain: heos
---
-The HEOS integration adds support for [HEOS](http://heosbydenon.denon.com) capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. Features currently include:
+The HEOS integration adds support for [HEOS](https://www.denon.com/en-gb/shop/amplifiersmrs/heosavr) capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. Features currently include:
- Each device is represented as a media player entity
- View the currently playing media
diff --git a/source/_integrations/history.markdown b/source/_integrations/history.markdown
index e2816cb88c8..de4092d0c65 100644
--- a/source/_integrations/history.markdown
+++ b/source/_integrations/history.markdown
@@ -24,8 +24,8 @@ history:
```
-
- 
+
+ 
diff --git a/source/_integrations/hitron_coda.markdown b/source/_integrations/hitron_coda.markdown
index 48d1e5aac4a..488b886afb3 100644
--- a/source/_integrations/hitron_coda.markdown
+++ b/source/_integrations/hitron_coda.markdown
@@ -5,6 +5,7 @@ ha_category:
- Presence Detection
ha_release: 0.58
ha_domain: hitron_coda
+ha_iot_class: Local Polling
---
This integration offers presence detection by examining devices connected to a [Rogers Hitron CODA](https://www.rogers.com/customer/support/article/wi-fi-password-hitron-coda4582-cgn3amr-cgnm3552-cgn3acr-cgn3)
diff --git a/source/_integrations/homeassistant.markdown b/source/_integrations/homeassistant.markdown
index 0f82403e070..8a026e4dfda 100644
--- a/source/_integrations/homeassistant.markdown
+++ b/source/_integrations/homeassistant.markdown
@@ -2,6 +2,8 @@
title: Home Assistant Core Integration
description: Description of the homeassistant integration.
ha_release: 0.0
+ha_category:
+ - Other
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
diff --git a/source/_integrations/hp_ilo.markdown b/source/_integrations/hp_ilo.markdown
index 263334aa4c8..9da5cce69a7 100644
--- a/source/_integrations/hp_ilo.markdown
+++ b/source/_integrations/hp_ilo.markdown
@@ -15,7 +15,7 @@ If the ILO or specified jsonpath query returns only a single value (e.g., a temp
Some more details about what can be retrieved from these sensors is available in the [python-hpilo documentation](https://seveas.github.io/python-hpilo/).
- 
+ 
## Configuration
@@ -114,7 +114,7 @@ sensor:
```
- 
+ 
## Hardware specifics
diff --git a/source/_integrations/html5.markdown b/source/_integrations/html5.markdown
index c9a76e19e27..aa59b053941 100644
--- a/source/_integrations/html5.markdown
+++ b/source/_integrations/html5.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to use the HTML5 push notifications platform fr
ha_category:
- Notifications
ha_release: 0.27
+ha_iot_class: Cloud Push
ha_domain: html5
---
@@ -83,7 +84,7 @@ The `html5` platform can only function if all of the following requirements are
* Your Home Assistant instance is accessible from outside your network over HTTPS or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
* If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.
* If you don't run Hass.io: `pywebpush` must be installed. `libffi-dev`, `libpython-dev` and `libssl-dev` must be installed prior to `pywebpush` (i.e., `pywebpush` probably won't automatically install).
-* You have configured SSL/TLS for your Home Assistant. It doesn't need to be configured in Home Assistant though, e.g., you can be running [NGINX](/ecosystem/nginx/) in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e., not self signed).
+* You have configured SSL/TLS for your Home Assistant. It doesn't need to be configured in Home Assistant though, e.g., you can be running NGINX in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e., not self-signed).
* You are willing to accept the notification permission in your browser.
### Configuring the platform
@@ -311,7 +312,7 @@ You will receive an event named `html5_notification.closed` when the notificatio
### Making notifications work with NGINX proxy
-If you use [NGINX](/ecosystem/nginx/) as a proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It's because of authentication token that cannot be passed through the proxy.
+If you use NGINX as a proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It's because of an authentication token that cannot be passed through the proxy.
To solve the issue put additional location into your NGINX site's configuration:
diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown
index 8d6e189aabe..e433e7fa1f2 100644
--- a/source/_integrations/http.markdown
+++ b/source/_integrations/http.markdown
@@ -117,7 +117,7 @@ The [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-us
## APIs
-On top of the `http` integration is a [REST API](/developers/rest_api/), [Python API](/developers/python_api/) and [WebSocket API](/developers/websocket_api/) available. There is also support for [Server-sent events](/developers/server_sent_events/).
+On top of the `http` integration is a [REST API](https://developers.home-assistant.io/docs/api/rest), [Python API](https://developers.home-assistant.io/docs/api_lib_index) and [WebSocket API](https://developers.home-assistant.io/docs/api/websocket) available. There is also support for [Server-sent events](/developers/server_sent_events/).
The `http` platforms are not real platforms within the meaning of the terminology used around Home Assistant. Home Assistant's [REST API](/developers/rest_api/) sends and receives messages over HTTP.
@@ -125,9 +125,9 @@ The `http` platforms are not real platforms within the meaning of the terminolog
To use those kind of [sensors](#sensor) or [binary sensors](#binary-sensor) in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.
-Create a [Long-Lived Access Tokens](https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token) in the Home Assistant UI at the bottom of your profile if you want to use HTTP sensors.
+Create a [Long-Lived Access Tokens](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) in the Home Assistant UI at the bottom of your profile if you want to use HTTP sensors.
-All [requests](/developers/rest_api/#post-apistatesltentity_id) need to be sent to the endpoint of the device and must be **POST**.
+All [requests](https://developers.home-assistant.io/docs/api/rest#post-apistatesentity_id) need to be sent to the endpoint of the device and must be **POST**.
## IP filtering and banning
diff --git a/source/_integrations/huawei_lte.markdown b/source/_integrations/huawei_lte.markdown
index 1c53727abec..5401426ba0d 100644
--- a/source/_integrations/huawei_lte.markdown
+++ b/source/_integrations/huawei_lte.markdown
@@ -30,7 +30,7 @@ There is currently support for the following platforms within Home Assistant:
## Configuration
The integration can be enabled in two ways, either using the frontend
-or using YAML. Additionally, if the [SSDP integration](../ssdp/) is
+or using YAML. Additionally, if the [SSDP integration](/integrations/ssdp) is
enabled in Home Assistant, automatically discovered Huawei LTE devices
which support and have UPnP enabled are made available for further
optional configuration in the frontend.
diff --git a/source/_integrations/huawei_router.markdown b/source/_integrations/huawei_router.markdown
index e869c312e0d..b3860dd84dc 100644
--- a/source/_integrations/huawei_router.markdown
+++ b/source/_integrations/huawei_router.markdown
@@ -3,6 +3,7 @@ title: Huawei Router
description: Instructions on how to integrate Huawei Routers into Home Assistant.
ha_category:
- Presence Detection
+ha_iot_class: Local Polling
ha_release: 0.51
ha_codeowners:
- '@abmantis'
diff --git a/source/_integrations/ifttt.markdown b/source/_integrations/ifttt.markdown
index 3f0b24cc1c9..988c1378ce2 100644
--- a/source/_integrations/ifttt.markdown
+++ b/source/_integrations/ifttt.markdown
@@ -166,11 +166,3 @@ ifttt_notify:
data: {"event":"TestHA_Trigger", "value1":"{{ value1 }}", "value2":"{{ value2 }}", "value3":"{{ value3 }}"}
```
{% endraw %}
-
-### Additional Channel Examples
-
-Additional examples of using IFTTT channels can be found below.
-
-Channel | Description
------ | -----
-[Manything](/integrations/ifttt.manything/) | Automates turning recording ON and OFF based on Home Assistant AWAY and HOME values.
diff --git a/source/_integrations/ign_sismologia.markdown b/source/_integrations/ign_sismologia.markdown
index 2c976e21462..d2b0daeb1e7 100644
--- a/source/_integrations/ign_sismologia.markdown
+++ b/source/_integrations/ign_sismologia.markdown
@@ -23,7 +23,7 @@ on the default map automatically, or on a map card by defining the source
of each entity.
- 
+ 
The data is updated every 5 minutes.
diff --git a/source/_integrations/image_processing.markdown b/source/_integrations/image_processing.markdown
index bd4049998de..2ed2b3679a1 100644
--- a/source/_integrations/image_processing.markdown
+++ b/source/_integrations/image_processing.markdown
@@ -1,6 +1,8 @@
---
title: Image Processing
description: Instructions on how to setup image processing with Home Assistant.
+ha_category:
+ - Image Processing
ha_release: 0.36
ha_domain: image_processing
---
diff --git a/source/_integrations/input_boolean.markdown b/source/_integrations/input_boolean.markdown
index 8a3a9ef191d..bd0989073d4 100644
--- a/source/_integrations/input_boolean.markdown
+++ b/source/_integrations/input_boolean.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate the Input Boolean integration into
ha_category:
- Automation
ha_release: 0.11
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
diff --git a/source/_integrations/input_datetime.markdown b/source/_integrations/input_datetime.markdown
index 30618331ae9..3a4b9c8898d 100644
--- a/source/_integrations/input_datetime.markdown
+++ b/source/_integrations/input_datetime.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate the Input Datetime integration int
ha_category:
- Automation
ha_release: 0.55
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
@@ -104,7 +105,7 @@ To set both the date and time in the same call, use `date` and `time` together,
#### input_datetime.reload
-`input_dateteime.reload` service allows one to reload `input_datetime`'s configuration without restarting Home Assistant itself.
+`input_datetime.reload` service allows one to reload `input_datetime`'s configuration without restarting Home Assistant itself.
## Examples
diff --git a/source/_integrations/input_number.markdown b/source/_integrations/input_number.markdown
index 30410c1553a..34a64c9bd3b 100644
--- a/source/_integrations/input_number.markdown
+++ b/source/_integrations/input_number.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate the Input Number integration into
ha_category:
- Automation
ha_release: 0.55
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
diff --git a/source/_integrations/input_select.markdown b/source/_integrations/input_select.markdown
index af2213676f8..185401ad7e3 100644
--- a/source/_integrations/input_select.markdown
+++ b/source/_integrations/input_select.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate the Input Select integration into
ha_category:
- Automation
ha_release: 0.13
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
diff --git a/source/_integrations/input_text.markdown b/source/_integrations/input_text.markdown
index eb0c13fcc1f..0a39b287c95 100644
--- a/source/_integrations/input_text.markdown
+++ b/source/_integrations/input_text.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate the Input Text integration into Ho
ha_category:
- Automation
ha_release: 0.53
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
diff --git a/source/_integrations/intesishome.markdown b/source/_integrations/intesishome.markdown
index 22152b91f95..0779baa37de 100644
--- a/source/_integrations/intesishome.markdown
+++ b/source/_integrations/intesishome.markdown
@@ -10,7 +10,7 @@ ha_codeowners:
ha_domain: intesishome
---
-The `IntesisHome` climate platform lets you control [IntesisHome](https://www.intesishome.com) and [Airconwithme](https://www.airconwithme.com) devices. IntesisHome provides integrations with air conditioners, including Panasonic, Daikin, Fujitsu, Toshiba, LG and more.
+The `IntesisHome` climate platform lets you control [IntesisHome](https://www.intesishome.com) and [Airconwithme](https://airconwithme.com) devices. IntesisHome provides integrations with air conditioners, including Panasonic, Daikin, Fujitsu, Toshiba, LG and more.
Note: IntesisHome products are a separate product line to IntesisBox. This platform does not support IntesisBox devices (which can be controlled locally using the WMP protocol).
@@ -27,7 +27,7 @@ climate:
{% configuration %}
username:
- description: "Your username for [IntesisHome.com](https://user.intesishome.com) / [Airconwithme](https://user.airconwithme.com)"
+ description: "Your username for [IntesisHome.com](https://accloud.intesis.com) / [Airconwithme](https://airconwithme.com)"
required: true
type: string
password:
diff --git a/source/_integrations/ios.markdown b/source/_integrations/ios.markdown
index 3d40fa53c33..65765b77d51 100644
--- a/source/_integrations/ios.markdown
+++ b/source/_integrations/ios.markdown
@@ -11,4 +11,6 @@ ha_codeowners:
ha_domain: ios
---
-The `ios` integration 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.
+The `ios` integration is used by the Home Assistant Companion App for iOS to store and provide settings for [actionable notifications](https://companion.home-assistant.io/docs/notifications/actionable-notifications) and [actions](https://companion.home-assistant.io/docs/core/actions). Both of these can also be configured for a single device within the app, in which case the `ios` integration is not required.
+
+For further details please check the [Companion App Documentation Site](https://companion.home-assistant.io).
diff --git a/source/_integrations/iss.markdown b/source/_integrations/iss.markdown
index 10cebe55c57..5b16be2a82b 100644
--- a/source/_integrations/iss.markdown
+++ b/source/_integrations/iss.markdown
@@ -3,6 +3,7 @@ title: International Space Station (ISS)
description: Know if or when ISS will be above your home location
ha_category:
- Binary Sensor
+ha_iot_class: Cloud Polling
ha_release: 0.36
ha_domain: iss
---
diff --git a/source/_integrations/isy994.markdown b/source/_integrations/isy994.markdown
index bfae5b8bcae..d9230e4763d 100644
--- a/source/_integrations/isy994.markdown
+++ b/source/_integrations/isy994.markdown
@@ -292,7 +292,7 @@ A device is created by creating a directory, with the name for the device, under
A program, named *status*, is required under the program device directory. A program, named *actions*, is required for all program devices except for binary_sensor. Any other programs in these device directories will be ignored. The *status* program requires that you create a variable with the name of your choice. This variable will store the actual status of the new device and will be updated by the *action* program.
- 
+ 
The *status* program in this directory is what indicates the state of the device:
@@ -304,7 +304,7 @@ The *status* program in this directory is what indicates the state of the device
- *switch* on if the clause returns true, otherwise off.
- 
+ 
The *actions* program indicates what should be performed for the following device services:
@@ -315,7 +315,7 @@ The *actions* program indicates what should be performed for the following devic
- *switch* the THEN clause is evaluated for the turn_on service, the ELSE clause is evaluated for the turn_off service.
- 
+ 
The example program above shows how to control a legacy X10 device from Home Assistant using an ISY controller.
diff --git a/source/_integrations/keenetic_ndms2.markdown b/source/_integrations/keenetic_ndms2.markdown
index 08e076692a2..39b4f446fe5 100644
--- a/source/_integrations/keenetic_ndms2.markdown
+++ b/source/_integrations/keenetic_ndms2.markdown
@@ -3,6 +3,7 @@ title: Keenetic NDMS2 Routers
description: Instructions on how to integrate Keenetic NDMS2 Routers into Home Assistant.
ha_category:
- Presence Detection
+ha_iot_class: Local Polling
ha_release: 0.54
ha_codeowners:
- '@foxel'
diff --git a/source/_integrations/kef.markdown b/source/_integrations/kef.markdown
index 01f3c1348e6..03ed4f1384b 100644
--- a/source/_integrations/kef.markdown
+++ b/source/_integrations/kef.markdown
@@ -10,7 +10,7 @@ ha_codeowners:
ha_domain: kef
---
-The `kef` platform allows you to control the [KEF LS50 Wireless](https://international.kef.com/products/ls50-wireless) and [KEF LSX](https://international.kef.com/products/lsx) speakers from Home Assistant.
+The `kef` platform allows you to control the KEF LS50 Wireless and [KEF LSX](https://international.kef.com/products/lsx) speakers from Home Assistant.
Supported devices:
diff --git a/source/_integrations/kira.markdown b/source/_integrations/kira.markdown
index 345296f7a62..c0f0499d346 100644
--- a/source/_integrations/kira.markdown
+++ b/source/_integrations/kira.markdown
@@ -6,6 +6,7 @@ ha_category:
- Remote
- Sensor
ha_release: 0.45
+ha_iot_class: Local Push
ha_domain: kira
---
diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown
index 14c3b1bbd5f..1bc5b270d95 100644
--- a/source/_integrations/knx.markdown
+++ b/source/_integrations/knx.markdown
@@ -7,7 +7,7 @@ ha_category:
- Climate
- Cover
- Light
- - Notify
+ - Notifications
- Scene
- Sensor
- Switch
@@ -182,7 +182,7 @@ payload:
description: Payload to send to the bus. When `type` is not set, raw bytes are sent. Integers are then treated as DPT 1/2/3 payloads. For DPTs > 6 bits send a list. Each value represents 1 octet (0-255). Pad with 0 to DPT byte length.
type: [integer, list]
type:
- description: If set, the payload will not be sent as raw bytes, but encoded as given DPT. KNX sensor types are valid values - see table in [KNX Sensor](/integrations/sensor.knx).
+ description: If set, the payload will not be sent as raw bytes, but encoded as given DPT. KNX sensor types are valid values - see table in [KNX Sensor](#sensor).
type: [string, integer, float]
{% endconfiguration %}
@@ -222,7 +222,7 @@ knx:
{% configuration %}
type:
- description: Type of the exposed value. Either 'binary', 'time', 'date', 'datetime' or any supported type of [KNX Sensor](/integrations/sensor.knx/) (e.g., "temperature" or "humidity").
+ description: Type of the exposed value. Either 'binary', 'time', 'date', 'datetime' or any supported type of [KNX Sensor](#sensor) (e.g., "temperature" or "humidity").
type: string
required: true
entity_id:
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 38ac557fb1b..ff429c1d3fb 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -244,7 +244,7 @@ devices:
### Configuration Notes
- Either `pin` or `zone` is required for each actuator or sensor. Do not use both in the same definition.
-- `pin` represents the number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are `1`, `2`, `5`, `6`, `7`, `8`, and `9`. Pin based configuration is only allowed with ESP8266 based devices.
+- `pin` represents the number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/release/modules/gpio/) for more details. Valid values are `1`, `2`, `5`, `6`, `7`, `8`, and `9`. Pin based configuration is only allowed with ESP8266 based devices.
- Pin `D8` or the `out` zone will only work when activation is set to high (the default).
- `zone` represents the value corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) boards. Valid zone values are `1`, `2`, `3`, `4`, `5`, `6`, and `out` for the Konnected Alarm Panel (`out` represents the dedicated ALARM/OUT terminal) and `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`, `11`, `12`, `out1`, `alarm1`, and `alarm2_out2` for the Konnected Alarm Panel Pro.
- **The Konnected Alarm Panel Pro does not support configuration via `pin`.**
diff --git a/source/_integrations/lannouncer.markdown b/source/_integrations/lannouncer.markdown
index 576f996bc66..464ee1d6e14 100644
--- a/source/_integrations/lannouncer.markdown
+++ b/source/_integrations/lannouncer.markdown
@@ -8,7 +8,7 @@ ha_release: 0.36
ha_domain: lannouncer
---
-The `lannouncer` notification platform allows you to play spoken messages (TTS) or sounds on an Android device running [Lannouncer](https://www.keybounce.com/lannouncer/). This can be useful when you have a wall mounted Android tablet, or an Android device that is permanently powered and turned on and want to use that to play notifications.
+The `lannouncer` notification platform allows you to play spoken messages (TTS) or sounds on an Android device running [Lannouncer](https://play.google.com/store/apps/details?id=com.keybounce.lannouncer&hl=en_US). This can be useful when you have a wall mounted Android tablet, or an Android device that is permanently powered and turned on and want to use that to play notifications.
To enable Lannouncer notifications in your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_integrations/lifx.markdown b/source/_integrations/lifx.markdown
index 184939259c7..63240ee0ed1 100644
--- a/source/_integrations/lifx.markdown
+++ b/source/_integrations/lifx.markdown
@@ -32,11 +32,11 @@ Change the light to a new state.
| `zones` | List of integers for the zone numbers to affect (each LIFX Z strip has 8 zones, starting at 0).
| `infrared` | Automatic infrared level (0..255) when light brightness is low (for compatible bulbs).
| `power` | Turn the light on (`True`) or off (`False`). Leave out to keep the power as it is.
-| `...` | Use `color_name`, `brightness` etc. from [`light.turn_on`]({{site_root}}/integrations/light/#service-lightturn_on) to specify the new state.
+| `...` | Use `color_name`, `brightness` etc. from [`light.turn_on`](/integrations/light/#service-lightturn_on) to specify the new state.
## Light effects
-The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`]({{site_root}}/integrations/light/#service-lightturn_on) service, for example like this:
+The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`](/integrations/light/#service-lightturn_on) service, for example like this:
```yaml
automation:
- alias: ...
diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown
index 71ede78fe02..bc739ce0243 100644
--- a/source/_integrations/light.markdown
+++ b/source/_integrations/light.markdown
@@ -18,7 +18,7 @@ The `.default` suffix should be added to the entity identifier of each light to
### Service `light.turn_on`
-Turns one light on or multiple lights on using [groups]({{site_root}}/integrations/group/).
+Turns one light on or multiple lights on using [groups](/integrations/group/).
Most lights do not support all attributes. You can check the integration documentation of your particular light for hints, but in general, you will have to try things out and see what works.
diff --git a/source/_integrations/light.rflink.markdown b/source/_integrations/light.rflink.markdown
index cfc2a0891c7..4a003e3b1ac 100644
--- a/source/_integrations/light.rflink.markdown
+++ b/source/_integrations/light.rflink.markdown
@@ -4,8 +4,8 @@ description: "Instructions on how to integrate RFLink lights into Home Assistant
logo: rflink.png
ha_category:
- Light
-ha_release: 0.38
ha_iot_class: Assumed State
+ha_release: 0.38
ha_domain: rflink
---
diff --git a/source/_integrations/limitlessled.markdown b/source/_integrations/limitlessled.markdown
index d94d5800f9d..98b22a1098e 100644
--- a/source/_integrations/limitlessled.markdown
+++ b/source/_integrations/limitlessled.markdown
@@ -116,7 +116,7 @@ automation:
### Properties
-Refer to the [light]({{site_root}}/integrations/light/) documentation for general property usage, but keep in mind the following notes specific to LimitlessLED.
+Refer to the [light](/integrations/light/) documentation for general property usage, but keep in mind the following notes specific to LimitlessLED.
- **RGBWW** (Only supported on v6 bridges)
- *Color*: There are 25,856 color possibilities along the LimitlessLED color spectrum. For colors, hue and saturation can be used, but not lightness. If you select a color with lightness, Home Assistant will calculate the nearest valid LimitlessLED color. In white mode, the temperature can be set.
diff --git a/source/_integrations/locative.md b/source/_integrations/locative.md
index e07784c7914..732414d24b5 100644
--- a/source/_integrations/locative.md
+++ b/source/_integrations/locative.md
@@ -18,7 +18,7 @@ Install on your smartphone:
To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on it's first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
- 
+ 
When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
diff --git a/source/_integrations/lutron_caseta.markdown b/source/_integrations/lutron_caseta.markdown
index 76fc7134653..f435be8dd41 100644
--- a/source/_integrations/lutron_caseta.markdown
+++ b/source/_integrations/lutron_caseta.markdown
@@ -119,7 +119,7 @@ Available services: `switch.turn_on` and `switch.turn_off`.
## Fan
-After setup, fans will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light switch called 'Master Bathroom Vanity' will appear in Home Assistant as `fan.master_bedroom_ceiling_fan`.
+After setup, fans will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light switch called 'Master Bedroom Ceiling Fan' will appear in Home Assistant as `fan.master_bedroom_ceiling_fan`.
For more information on working with fans in Home Assistant, see the [Fans component](/components/fan/).
diff --git a/source/_integrations/lyft.markdown b/source/_integrations/lyft.markdown
index afd295bd80c..92ec4142d1c 100644
--- a/source/_integrations/lyft.markdown
+++ b/source/_integrations/lyft.markdown
@@ -8,9 +8,9 @@ ha_release: 0.41
ha_domain: lyft
---
-The `lyft` sensor will give you time and price estimates for all available [Lyft](https://lyft.com) products at the given `start_latitude` and `start_longitude`.The `ATTRIBUTES` are used to provide extra information about products, such as vehicle capacity and fare rates. If an `end_latitude` and `end_longitude` are specified, a price estimate will also be provided. One sensor will be created for each product at the given `start` location, for pickup time. A second sensor for each product, for estimated price, will be created if a destination is specified. The sensor is powered by the official Lyft [API](https://developer.lyft.com/reference/).
+The `lyft` sensor will give you time and price estimates for all available [Lyft](https://lyft.com) products at the given `start_latitude` and `start_longitude`.The `ATTRIBUTES` are used to provide extra information about products, such as vehicle capacity and fare rates. If an `end_latitude` and `end_longitude` are specified, a price estimate will also be provided. One sensor will be created for each product at the given `start` location, for pickup time. A second sensor for each product, for estimated price, will be created if a destination is specified. The sensor is powered by the official Lyft [API](https://developer.lyft.com/docs).
-You must create an application [here](https://www.lyft.com/developers/manage) to obtain a `client_id` and `client_secret`.
+You must create an application [here](https://www.lyft.com/developers/apps) to obtain a `client_id` and `client_secret`.
To enable this sensor, add the following lines to your `configuration.yaml` file:
@@ -24,11 +24,11 @@ sensor:
{% configuration %}
client_id:
- description: "A client id obtained from [developer.lyft.com](https://developer.lyft.com) after [creating an app](https://www.lyft.com/developers/manage)."
+ description: "A client id obtained from [developer.lyft.com](https://developer.lyft.com) after [creating an app](https://www.lyft.com/developers/apps)."
required: true
type: string
client_secret:
- description: "A client secret obtained from [developer.lyft.com](https://developer.lyft.com) after [creating an app](https://www.lyft.com/developers/manage)."
+ description: "A client secret obtained from [developer.lyft.com](https://developer.lyft.com) after [creating an app](https://www.lyft.com/developers/apps)."
required: true
type: string
start_latitude:
diff --git a/source/_integrations/mailgun.markdown b/source/_integrations/mailgun.markdown
index c146ad8c0a1..f2ec994c4ea 100644
--- a/source/_integrations/mailgun.markdown
+++ b/source/_integrations/mailgun.markdown
@@ -74,19 +74,11 @@ notify:
```
{% configuration %}
-domain:
- description: This is the domain name to be used when sending out mail.
- required: true
- type: string
-sandbox:
- description: "(**Deprecated**) If a sandboxed domain is used, specify it in `domain`."
+name:
+ description: "The optional parameter name allows multiple notifiers to be created. The notifier will bind to the service notify.NOTIFIER_NAME."
required: false
- default: false
- type: boolean
-api_key:
- description: This is the API Key that has been generated in your Mailgun account.
- required: true
type: string
+ default: notify
recipient:
description: The email address of the recipient.
required: true
diff --git a/source/_integrations/mastodon.markdown b/source/_integrations/mastodon.markdown
index 54af064ebe9..78f20c7ba38 100644
--- a/source/_integrations/mastodon.markdown
+++ b/source/_integrations/mastodon.markdown
@@ -30,6 +30,11 @@ notify:
```
{% configuration %}
+name:
+ description: "The optional parameter name allows multiple notifiers to be created. The notifier will bind to the service notify.NOTIFIER_NAME."
+ required: false
+ type: string
+ default: notify
access_token:
description: Your Mastodon access token.
required: true
diff --git a/source/_integrations/maxcube.markdown b/source/_integrations/maxcube.markdown
index f76aa4ab07a..b70f46cb030 100644
--- a/source/_integrations/maxcube.markdown
+++ b/source/_integrations/maxcube.markdown
@@ -10,7 +10,7 @@ ha_iot_class: Local Polling
ha_domain: maxcube
---
-[eQ-3 MAX!](https://www.eq-3.com/products/max.html) integration for Home Assistant allows you to connect eQ-3 MAX! components via the eQ-3 MAX! Cube. The components connects to the eQ-3 MAX! Cube via TCP and automatically makes all supported integrations available in Home Assistant. The name for each device is created by concatenating the MAX! room and device names.
+[eQ-3 MAX!](https://www.eq-3.com/products/homematic/detail/max-cube-lan-gateway.html) integration for Home Assistant allows you to connect eQ-3 MAX! components via the eQ-3 MAX! Cube. The components connects to the eQ-3 MAX! Cube via TCP and automatically makes all supported integrations available in Home Assistant. The name for each device is created by concatenating the MAX! room and device names.
There is currently support for the following device types within Home Assistant:
@@ -68,3 +68,9 @@ maxcube:
type: integer
default: 300
{% endconfiguration %}
+
+### Problems connecting or setting up
+
+Due to the connection limits of the eQ-3 MAX! Cube, Home Assistant will not be able to connect to the gateway if another application is still connected. It may result in timeout errors like _Error: timed out You will need to restart Home Assistant after fixing._ and _The following integrations and platforms could not be set up: maxcube Please check your configuration._
+
+To prevent these issues, ensure all other applications connecting to the gateway are closed, e.g., the mobile app or the MAX! desktop app (On Windows machines, close from the status bar, it keeps running when you close the browser window).
diff --git a/source/_integrations/media_extractor.markdown b/source/_integrations/media_extractor.markdown
index 3c5bf906962..223b517f2ab 100644
--- a/source/_integrations/media_extractor.markdown
+++ b/source/_integrations/media_extractor.markdown
@@ -45,12 +45,10 @@ media_extractor:
This configuration sets query for all service calls like to 'bestaudio' with the mp3 extension:
-```json
-{
- "entity_id": "media_player.my_sonos",
- "media_content_id": "https://soundcloud.com/bruttoband/brutto-11",
- "media_content_type": "music"
-}
+```yaml
+entity_id: media_player.my_sonos
+media_content_id: https://soundcloud.com/bruttoband/brutto-11
+media_content_type: music
```
Query examples with explanations:
@@ -61,11 +59,11 @@ Query examples with explanations:
* **worst**: Worst video + audio stream
* **bestaudio[ext=m4a]/bestaudio[ext=ogg]/bestaudio**: Best m4a audio, otherwise best ogg audio and only then any best audio
-More info about queries [here](https://github.com/rg3/youtube-dl#format-selection)
+More info about queries can be found [here](https://github.com/ytdl-org/youtube-dl#format-selection).
### Use the service
-Use
**Services** from the **Developer Tools**. Choose `media_extractor` from the dropdown menu **Domain** and `play_media` from **Service**, enter something like the JSON sample from above into the **Service Data** field, and hit **CALL SERVICE**.
+Navigate to the **Services** tab inside **Developer Tools**. From the "Service" dropdown menu select `media_extractor.play_media` and then press the "Fill Example Data" button at the bottom of the page. Use the "Entity ID" dropdown to select your media player and then press the **Call Service** button.
This will download the file from the given URL.
diff --git a/source/_integrations/mikrotik.markdown b/source/_integrations/mikrotik.markdown
index 9bbd4868aaf..514416ec689 100644
--- a/source/_integrations/mikrotik.markdown
+++ b/source/_integrations/mikrotik.markdown
@@ -9,6 +9,7 @@ ha_codeowners:
- '@engrbm87'
ha_config_flow: true
ha_domain: mikrotik
+ha_iot_class: Local Polling
---
The `mikrotik` platform offers presence detection by looking at connected devices to a [MikroTik RouterOS](https://mikrotik.com) based router.
diff --git a/source/_integrations/minecraft_server.markdown b/source/_integrations/minecraft_server.markdown
index ddb57fc7b2a..a6c09df2029 100644
--- a/source/_integrations/minecraft_server.markdown
+++ b/source/_integrations/minecraft_server.markdown
@@ -13,7 +13,7 @@ ha_codeowners:
ha_domain: minecraft_server
---
-Minecraft servers allow players to play the sandbox video game [Minecraft](https://www.minecraft.net) by [Mojang AB](https://www.mojang.com) online or via a local area network with other players. The `Minecraft Server` integration lets you retrieve information from a Minecraft server (Java edition) within Home Assistant.
+Minecraft servers allow players to play the sandbox video game [Minecraft](https://www.minecraft.net/en-us) by [Mojang AB](https://www.mojang.com) online or via a local area network with other players. The `Minecraft Server` integration lets you retrieve information from a Minecraft server (Java edition) within Home Assistant.
The server must be version 1.7 or higher, since older versions don't expose any information.
diff --git a/source/_integrations/mochad.markdown b/source/_integrations/mochad.markdown
index f0a9f561c19..af47f803a8d 100644
--- a/source/_integrations/mochad.markdown
+++ b/source/_integrations/mochad.markdown
@@ -5,6 +5,7 @@ ha_category:
- Hub
- Light
- Switch
+ha_iot_class: Local Polling
ha_release: 0.32
ha_domain: mochad
---
diff --git a/source/_integrations/mpchc.markdown b/source/_integrations/mpchc.markdown
index b0e105ec25c..c78fb3a6a03 100644
--- a/source/_integrations/mpchc.markdown
+++ b/source/_integrations/mpchc.markdown
@@ -13,7 +13,7 @@ The `mpchc` platform allows you to connect a [Media Player Classic Home Cinema](
For this integration to function, you will need to enable the Web Interface in the MPC-HC options dialog.
- 
+ 
If the server running Home Assistant is not the same device that is running MPC-HC, you will need to ensure that the *allow access from localhost only* option is not set.
diff --git a/source/_integrations/msteams.markdown b/source/_integrations/msteams.markdown
index aa9694e235b..5e1cb30b1fc 100644
--- a/source/_integrations/msteams.markdown
+++ b/source/_integrations/msteams.markdown
@@ -3,6 +3,7 @@ title: Microsoft Teams
description: Instructions on how to send a notification to a Microsoft Teams channel.
ha_category:
- Notifications
+ha_iot_class: Cloud Push
ha_release: 0.101
ha_codeowners:
- '@peroyvind'
diff --git a/source/_integrations/mystrom.markdown b/source/_integrations/mystrom.markdown
index b21b5db3d45..ffc9ddfb776 100644
--- a/source/_integrations/mystrom.markdown
+++ b/source/_integrations/mystrom.markdown
@@ -160,7 +160,7 @@ The `mystrom` switch platform allows you to control the state of your [myStrom](
Make sure that you have enabled the REST API under **Advanced** in the web frontend of the switch.
- 
+ 
To use your myStrom switch in your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_integrations/neato.markdown b/source/_integrations/neato.markdown
index d8e768795c2..bb193ef5437 100644
--- a/source/_integrations/neato.markdown
+++ b/source/_integrations/neato.markdown
@@ -15,7 +15,14 @@ ha_codeowners:
ha_domain: neato
---
-The `neato` integration allows you to control your [Neato Botvac Connected Robots](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/).
+The `neato` integration allows you to control your [Neato Botvac Connected Robots][botvac-connected].
+
+There is support for the following platform types within Home Assistant:
+
+- **Camera** - allows you to view the latest cleaning map.
+- **Sensor** - allows you to view the battery level.
+- **Switch** - allows you to enable or disable the schedule.
+- [**Vacuum**](#vacuum)
To activate `neato` in your installation, you can set it up from the integration screen or add it to your `configuration.yaml` file.
@@ -61,7 +68,7 @@ After the update to firmware 4.0 (which adds cleaning maps) there is also suppor
## Vacuum
-The `neato` vacuum platform allows you to control your [Neato Botvac Connected](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/).
+The `neato` vacuum platform allows you to control your [Neato Botvac Connected][botvac-connected].
The status will contain attributes on the robots last clean session.
@@ -104,17 +111,4 @@ Some information about the capabilities might be found on the [Neato Developer P
| `category` | yes | Whether to use a persistent map or not for cleaning (i.e., No go lines): 2 for no map, 4 for map. Default to using map if not set (and fallback to no map if no map is found). |
| `zone` | yes | Only supported on the Botvac D7. Name of the zone to clean from the Neato app. Use unique names for the zones to avoid the wrong zone from running. Defaults to no zone i.e., complete house cleanup. |
-
-## Camera
-
-The `neato` camera platform allows you to view the latest cleaning map of your [Neato Botvac Connected](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/botvac-connected/).
-
-## Sensor
-
-The `neato` sensor platform allows you to view the battery level for your [Neato Botvac Connected](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/botvac-connected/).
-
-## Switch
-
-The `neato` switch platform allows you to enable or disable the schedule of your [Neato Botvac Connected](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/botvac-connected/).
-
-To add `neato` switch, camera and vacuum to your installation, follow instructions above.
+[botvac-connected]: https://neatorobotics.com/products
\ No newline at end of file
diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown
index 3df50afe5f7..b4babfd61d4 100644
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@@ -272,7 +272,7 @@ Please note due to limitations with the European Nest Thermostat E, integration
- 
+ 
## Sensor
diff --git a/source/_integrations/netdata.markdown b/source/_integrations/netdata.markdown
index a687df52991..71b2b112e43 100644
--- a/source/_integrations/netdata.markdown
+++ b/source/_integrations/netdata.markdown
@@ -17,7 +17,7 @@ The `netdata` sensor platform allows you to display information collected by [Ne
Getting the details to configure the sensors is a bit tricky as Netdata uses different name for the `element:` value that is required. To get the value for the `data_group:` use Netdata's web interface. `1.` marks the name for the `data_group:`. `2.` are the names for the element to show in Home Assistant. The name that is shown can be different than the name under which the metrics are available.
- 
+ 
To check if the `element:` name matches the name in the Netdata frontend, use `curl` with the IP address of your Netdata instance, its port and the `data_group`:
diff --git a/source/_integrations/nmap_tracker.markdown b/source/_integrations/nmap_tracker.markdown
index 12b252d2cf7..4ac83d1b2ef 100644
--- a/source/_integrations/nmap_tracker.markdown
+++ b/source/_integrations/nmap_tracker.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate Nmap into Home Assistant.
ha_category:
- Presence Detection
ha_release: 0.7
+ha_iot_class: Local Polling
ha_domain: nmap_tracker
---
diff --git a/source/_integrations/nmbs.markdown b/source/_integrations/nmbs.markdown
index b353dabe94c..e84712cbe7b 100644
--- a/source/_integrations/nmbs.markdown
+++ b/source/_integrations/nmbs.markdown
@@ -59,6 +59,6 @@ show_on_map:
{% endconfiguration %}
- 
+ 
Example using the Lovelace Attributes custom card
diff --git a/source/_integrations/no_ip.markdown b/source/_integrations/no_ip.markdown
index 37b1f37f16e..9b6f9f404a4 100644
--- a/source/_integrations/no_ip.markdown
+++ b/source/_integrations/no_ip.markdown
@@ -3,6 +3,7 @@ title: No-IP.com
description: Keep your computer registered with the NO-IP.com dynamic DNS.
ha_category:
- Network
+ha_iot_class: Cloud Polling
ha_release: 0.57
ha_codeowners:
- '@fabaff'
diff --git a/source/_integrations/noaa_tides.markdown b/source/_integrations/noaa_tides.markdown
index e56081bb0c4..40b64c46a9d 100644
--- a/source/_integrations/noaa_tides.markdown
+++ b/source/_integrations/noaa_tides.markdown
@@ -4,6 +4,7 @@ description: Instructions to add NOAA Tide information to Home Assistant.
ha_category:
- Environment
ha_release: 0.75
+ha_iot_class: Cloud Polling
ha_domain: noaa_tides
ha_codeowners:
- '@jdelaney72'
diff --git a/source/_integrations/nsw_rural_fire_service_feed.markdown b/source/_integrations/nsw_rural_fire_service_feed.markdown
index 594c787cdba..7b226e43979 100644
--- a/source/_integrations/nsw_rural_fire_service_feed.markdown
+++ b/source/_integrations/nsw_rural_fire_service_feed.markdown
@@ -13,13 +13,13 @@ ha_domain: nsw_rural_fire_service_feed
The `nsw_rural_fire_service_feed` platform lets you integrate a GeoJSON feed provided by the [NSW Rural Fire Service](https://www.rfs.nsw.gov.au/fire-information/fires-near-me) with information about bush fires, grass fires, hazard reductions and more. It retrieves incidents from a feed and shows information of those incidents filtered by distance to Home Assistant's location.
- 
+ 
Entities are generated, updated and removed automatically with each update from the feed. Each entity defines latitude and longitude and will be shown on the map automatically. The distance in kilometers is available as the state of each entity.
- 
+ 
The entity's information can be used for example if a bush fire that produces smoke or embers is reported close to your home, and you want to automatically close windows, turn on a sprinkler system or simply send yourself a reminder to clean the gutters from dry leaves.
diff --git a/source/_integrations/onkyo.markdown b/source/_integrations/onkyo.markdown
index c4846053c00..a62daeaae88 100644
--- a/source/_integrations/onkyo.markdown
+++ b/source/_integrations/onkyo.markdown
@@ -8,8 +8,8 @@ ha_iot_class: Local Polling
ha_domain: onkyo
---
-The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/), [Integra](http://www.integrahometheater.com/)
-and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant.
+The `onkyo` platform allows you to control a [Onkyo](https://www.onkyo.com), [Integra](http://www.integrahometheater.com)
+and some recent [Pioneer](https://www.pioneerelectronics.com) receivers from Home Assistant.
Please be aware that you need to enable "Network Standby" for this integration to work in your Hardware.
## Configuration
diff --git a/source/_integrations/opengarage.markdown b/source/_integrations/opengarage.markdown
index 8ce7357c01f..cf8ca7d16f1 100644
--- a/source/_integrations/opengarage.markdown
+++ b/source/_integrations/opengarage.markdown
@@ -76,7 +76,7 @@ covers:
**Example with more detail:**
- 
+ 
{% raw %}
diff --git a/source/_integrations/opentherm_gw.markdown b/source/_integrations/opentherm_gw.markdown
index c0cf858114c..fc91b43536c 100644
--- a/source/_integrations/opentherm_gw.markdown
+++ b/source/_integrations/opentherm_gw.markdown
@@ -112,7 +112,7 @@ Improper use of this service may continuously keep your central heating system a
Set the central heating control setpoint override on the OpenTherm Gateway.
-In a normal situation, the thermostat will calculate and control the central heating setpoint on the boiler. Setting this to any value other than 0 will enable the override and allow the OpenTherm Gateway to control this setting. While the override is active, the OpenTherm Gateway will also request your boiler to activate the central heating circuit. For your boiler's actual maximum and minimum supported setpoint value, please see the [`slave_ch_max_setp`](#slave_ch_max_setp) and [`slave_ch_min_setp`](#slave_ch_min_setp) variables. Due to the potential consequences of leaving this setting enabled for prolonged periods, the override will be disabled when Home Assistant is shut down or restarted.
+In a normal situation, the thermostat will calculate and control the central heating setpoint on the boiler. Setting this to any value other than 0 will enable the override and allow the OpenTherm Gateway to control this setting. While the override is active, the OpenTherm Gateway will also request your boiler to activate the central heating circuit. For your boiler's actual maximum and minimum supported setpoint value, please see the `slave_ch_max_setp` and `slave_ch_min_setp` [sensors](#sensors). Due to the potential consequences of leaving this setting enabled for prolonged periods, the override will be disabled when Home Assistant is shut down or restarted.
**You will only need this if you are writing your own software thermostat.**
| Service data attribute | Optional | Description |
diff --git a/source/_integrations/opnsense.markdown b/source/_integrations/opnsense.markdown
index 991bb74d550..6012e9df88d 100644
--- a/source/_integrations/opnsense.markdown
+++ b/source/_integrations/opnsense.markdown
@@ -8,6 +8,7 @@ ha_release: 0.105
ha_codeowners:
- '@mtreinish'
ha_domain: opnsense
+ha_iot_class: Local Polling
---
[OPNsense](https://opnsense.org/) is an open source HardenedBSD based firewall
diff --git a/source/_integrations/osramlightify.markdown b/source/_integrations/osramlightify.markdown
index 921cccf1f38..bb9332f834a 100644
--- a/source/_integrations/osramlightify.markdown
+++ b/source/_integrations/osramlightify.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate Osram Lightify into Home Assistant
ha_category:
- Light
ha_release: 0.21
+ha_iot_class: Local Polling
ha_domain: osramlightify
---
diff --git a/source/_integrations/pilight.markdown b/source/_integrations/pilight.markdown
index d8453a6ba61..080fdc99d1e 100644
--- a/source/_integrations/pilight.markdown
+++ b/source/_integrations/pilight.markdown
@@ -42,7 +42,7 @@ host:
default: 127.0.0.1
type: string
port:
- description: "The network port to connect to, see also: (https://manual.pilight.org/development/api.html)."
+ description: "The network port to connect to, see also: (https://manual.pilight.org/development/socket/index.html)."
required: false
default: 5001
type: integer
@@ -57,7 +57,7 @@ whitelist:
type: string
{% endconfiguration %}
-In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight [API](https://manual.pilight.org/development/api.html).
+In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight [API](https://manual.pilight.org/development/index.html).
A full configuration sample could look like the sample below:
@@ -268,7 +268,7 @@ Variables for the different codes (`on_code` and `off_code`):
- **'off'** (*Optional*): `1` or `0`
- **'on'** (*Optional*): `1` or `0`
-For possible code entries, look at the [pilight API](https://manual.pilight.org/development/api.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring.
+For possible code entries, look at the [pilight API](https://manual.pilight.org/development/index.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring.
Variables for the different receive codes (`on_code_receive` and `off_code_receive`):
diff --git a/source/_integrations/ping.markdown b/source/_integrations/ping.markdown
index 245b9c15be4..b8fe3a0d489 100644
--- a/source/_integrations/ping.markdown
+++ b/source/_integrations/ping.markdown
@@ -6,6 +6,7 @@ ha_category:
- Binary Sensor
- Presence Detection
ha_release: 0.43
+ha_iot_class: Local Polling
ha_quality_scale: internal
ha_domain: ping
---
@@ -34,7 +35,7 @@ host:
required: true
type: string
count:
- description: Number of packets to send.
+ description: Number of packages to be sent up to a maximum of 100.
required: false
type: integer
default: 5
@@ -42,7 +43,7 @@ name:
description: Let you overwrite the name of the device.
required: false
type: string
- default: Ping Binary sensor
+ default: Binary sensor Ping [hostname]
{% endconfiguration %}
The sensor exposes the different round trip times values measured by `ping` as attributes:
@@ -52,13 +53,14 @@ The sensor exposes the different round trip times values measured by `ping` as a
- `round trip time min`
- `round trip time max`
-The default polling interval is 5 minutes. As many integrations [based on the entity class](/docs/configuration/platform_options), it is possible to overwrite this scan interval by specifying a `scan_interval` configuration key (value in seconds). In the example below we setup the `ping` binary sensor to poll the devices every 30 seconds.
+The default polling interval is 5 minutes. As many integrations [based on the entity class](/docs/configuration/platform_options), it is possible to overwrite this scan interval by specifying a `scan_interval` configuration key (value in seconds). In the example below we setup the `ping` binary sensor to poll the device every 30 seconds.
```yaml
# Example configuration.yaml entry to ping host 192.168.0.1 with 2 packets every 30 seconds.
binary_sensor:
- platform: ping
host: 192.168.0.1
+ name: "device name"
count: 2
scan_interval: 30
```
@@ -84,7 +86,7 @@ To use this presence detection in your installation, add the following to your `
device_tracker:
- platform: ping
hosts:
- hostone: 192.168.2.10
+ hostname: 192.168.2.10
```
{% configuration %}
diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown
index 8fd9bd94b10..837dae45417 100644
--- a/source/_integrations/plex.markdown
+++ b/source/_integrations/plex.markdown
@@ -13,19 +13,20 @@ ha_codeowners:
ha_domain: plex
---
-The `plex` integration allows you to connect to a [Plex Media Server](https://plex.tv). Once connected, [Plex Clients](https://www.plex.tv/apps-devices/) playing media from the connected Plex Media Server will show up as [Media Players](/integrations/media_player/) and report playback status via a [Sensor](/integrations/sensor/) in Home Assistant. The Media Players will allow you to control media playback and see the current playing item.
+The Plex integration allows you to connect Home Assistant to a [Plex Media Server](https://plex.tv). Once configured, actively streaming [Plex Clients](https://www.plex.tv/apps-devices/) show up as [Media Players](/integrations/media_player/) and report playback status via a [Sensor](/integrations/sensor/) in Home Assistant. Media Players will allow you to control media playback and see the current playing item.
-Support for playing music directly on linked [Sonos](/integrations/sonos/) speakers is also available for users with an active [Plex Pass](https://www.plex.tv/plex-pass/) subscription. More information [here](#sonos-playback).
+Support for playing music directly on linked [Sonos](/integrations/sonos/) speakers is available for users with an active [Plex Pass](https://www.plex.tv/plex-pass/) subscription. More information [here](#sonos-playback).
There is currently support for the following device types within Home Assistant:
- [Sensor](#sensor)
- [Media Player](#media-player)
-If your Plex server has been claimed by a Plex account via the [claim interface](https://plex.tv/claim), Home Assistant will require authentication to connect.
+If a Plex server has been claimed by a Plex account via the [claim interface](https://plex.tv/claim), Home Assistant will require authentication to connect.
-The Plex integration is set up via **Configuration** -> **Integrations**. You will be redirected to the [Plex](https://plex.tv) website to sign in with your Plex account. Once access is granted, Home Assistant will connect to the server linked to the associated account. If multiple Plex servers are available on the account, you will be prompted to complete the configuration by selecting the desired server on the Integrations page. Home Assistant will show as an authorized device on the [Plex Web](https://app.plex.tv/web/app) interface under **Settings** -> **Authorized Devices**.
+### Configuration
+The Plex integration is set up via **Configuration** -> **Integrations**. During the configuration, you will be redirected to the [Plex](https://plex.tv) website to sign in with your Plex account. Once access is granted, Home Assistant will connect to the Plex server linked to the provided account. If multiple Plex servers are available on the account, you will be prompted to complete the configuration by selecting the desired server on the **Integrations** page. Upon completeion, Home Assistant will be displayed as an authorized device on the [Plex Web](https://app.plex.tv/web/app) interface under **Settings** -> **Authorized Devices**.
### Integration Options
@@ -39,7 +40,6 @@ Several options are provided to adjust the behavior of `media_player` entities.
**Ignore Plex Web clients**: Do not create `media_player` entities for Plex Web clients.
-
### Manual Configuration
Alternatively, you can manually configure a Plex server connection by selecting the "Configure Plex server manually" when configuring a Plex integration. This option is only available to users in "Advanced Mode". This will allow you to specify the server connection options which will be validated before setup is completed. The available options are described below:
@@ -54,17 +54,15 @@ Alternatively, you can manually configure a Plex server connection by selecting
**Token**: A valid authorization token for your Plex server. If provided without 'Host', a connection URL will be retreived from Plex.
-
## Sensor
-The `plex` sensor platform will monitor activity on a given Plex Media Server. It will create a sensor that shows the number of currently watching users as the state. If you click the sensor for more details, it will show you who is watching what.
-
+The Plex sensor platform monitors activity on a given Plex Media Server. The sensor state provides the a count of users currently watching media from the Plex server. Clicking the sensor shows who is watching what media.
## Media Player
-The `plex` media_player platform will create Media Player entities for each connected client device. These entities will display media information, playback progress, and playback controls if supported by the device.
+The Plex media player platform will create Media Player entities for each connected client device. These entities will display media information, playback progress, and playback controls (if supported by the streaming device).
-By default the Plex integration will create Media Player entities for all local, managed, and shared users on the Plex server. To customize which users or client types to monitor, adjust the "*Monitored users*", "*Ignore new managed/shared users*", and "*Ignore Plex Web clients*" options described under [Integration Options](#integration-options).
+By default, the Plex integration will create Media Player entities for all local, managed, and shared users on the Plex server. To customize which users or client types to monitor, adjust the "*Monitored users*", "*Ignore new managed/shared users*", and "*Ignore Plex Web clients*" options described under [Integration Options](#integration-options).
### Service `play_media`
@@ -81,6 +79,7 @@ Required fields within the `media_content_id` payloads are marked as such, other
| `media_content_type` | `MUSIC` |
##### Examples:
+
```yaml
entity_id: media_player.plex_player
media_content_type: MUSIC
@@ -116,6 +115,7 @@ media_content_id: '{ "playlist_name": "The Best of Disco", "shuffle": "1" }'
| `media_content_type` | `EPISODE` |
##### Examples:
+
```yaml
entity_id: media_player.plex_player
media_content_type: EPISODE
@@ -149,6 +149,7 @@ For movies it's usually sufficient to provide the title. However, if the title y
* `year`: Restrict search to a specific year
##### Examples:
+
```yaml
entity_id: media_player.plex_player
media_content_type: movie
@@ -170,7 +171,6 @@ media_content_id: '{ "library_name": "Adult Movies", "title": "die hard", year=1
# Would find the sequel, "Die Hard: With a Vengeance"
```
-
### Compatibility
| Client | Limitations |
@@ -183,7 +183,6 @@ media_content_id: '{ "library_name": "Adult Movies", "title": "die hard", year=1
| NVidia Shield | Controlling playback when the Shield is both a client and a server will work but with error logging |
| Plex Web | None |
-
## Sonos Playback
To play Plex music directly to Sonos speakers, the following requirements must be met:
@@ -254,5 +253,5 @@ play_plex_on_tv:
## Notes
-* The `plex` integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Integrations**.
-* Movies must be located under 'Movies' section in the Plex library to properly get 'playing' state.
+- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Integrations**.
+- Movies must be located under the 'Movies' section in a Plex library to properly view the 'playing' state.
diff --git a/source/_integrations/powerwall.markdown b/source/_integrations/powerwall.markdown
index e5adce900c0..59605cdf9cd 100644
--- a/source/_integrations/powerwall.markdown
+++ b/source/_integrations/powerwall.markdown
@@ -51,7 +51,7 @@ The following binary sensors are added for each Powerwall:
### Sensor
-The following binary sensors are added for each Powerwall:
+The following sensors are added for each Powerwall:
- Powerwall Charge
- Powerwall Site Now
diff --git a/source/_integrations/prometheus.markdown b/source/_integrations/prometheus.markdown
index 1df7c93ec88..28450367127 100644
--- a/source/_integrations/prometheus.markdown
+++ b/source/_integrations/prometheus.markdown
@@ -4,6 +4,7 @@ description: Record events in Prometheus.
ha_category:
- History
ha_release: 0.49
+ha_iot_class: Assumed State
ha_domain: prometheus
ha_codeowners:
- '@knyar'
diff --git a/source/_integrations/pushover.markdown b/source/_integrations/pushover.markdown
index 8634267dc27..5e160d053c0 100644
--- a/source/_integrations/pushover.markdown
+++ b/source/_integrations/pushover.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to add Pushover notifications to Home Assistant
ha_category:
- Notifications
ha_release: pre 0.7
+ha_iot_class: Cloud Push
ha_domain: pushover
---
diff --git a/source/_integrations/pyload.markdown b/source/_integrations/pyload.markdown
index 26a954af583..c9056b7c116 100644
--- a/source/_integrations/pyload.markdown
+++ b/source/_integrations/pyload.markdown
@@ -52,5 +52,5 @@ ssl:
If everything is setup correctly, the download speed will show up in the frontend.
- 
+ 
diff --git a/source/_integrations/qld_bushfire.markdown b/source/_integrations/qld_bushfire.markdown
index 801ce5629fd..785c1870184 100644
--- a/source/_integrations/qld_bushfire.markdown
+++ b/source/_integrations/qld_bushfire.markdown
@@ -23,7 +23,7 @@ on the default map automatically, or on a map card by defining the source
of each entity.
- 
+ 
The data is updated every 5 minutes.
diff --git a/source/_integrations/qvr_pro.markdown b/source/_integrations/qvr_pro.markdown
index 819217ad78f..9a957e762b4 100644
--- a/source/_integrations/qvr_pro.markdown
+++ b/source/_integrations/qvr_pro.markdown
@@ -10,7 +10,7 @@ ha_codeowners:
- '@oblogic7'
---
-[QVR Pro](https://www.qnap.com/solution/qvr-pro-official) allows you to create
+[QVR Pro](https://www.qnap.com/en/software/qvr-pro) allows you to create
an independent and expandable surveillance environment on your QNAP NAS. The
`qvr_pro` component allows you to view your QVR Pro channels in Home Assistant.
diff --git a/source/_integrations/rachio.markdown b/source/_integrations/rachio.markdown
index 237cd276706..5cd8fa5b2e9 100644
--- a/source/_integrations/rachio.markdown
+++ b/source/_integrations/rachio.markdown
@@ -29,6 +29,12 @@ They will be automatically added if the Rachio integration integration is loaded
3. Click "Get API Key"
4. Copy the API key from the dialog that opens.
+
+
+In order for Rachio switches and sensors to update, your Home Assistant instance must be accessible from the internet, either via Home Assistant Cloud or another method. See the [Remote Access documentation](/docs/configuration/remote/) for more information.
+
+
+
## Configuration
To add `Rachio` go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Rachio**.
diff --git a/source/_integrations/radarr.markdown b/source/_integrations/radarr.markdown
index aca49c1bac8..bdbbee01d0e 100644
--- a/source/_integrations/radarr.markdown
+++ b/source/_integrations/radarr.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate Radarr sensors with Home Assistant
ha_category:
- Downloading
ha_release: 0.47
+ha_iot_class: Local Polling
ha_domain: radarr
---
diff --git a/source/_integrations/rflink.markdown b/source/_integrations/rflink.markdown
index 825a03a0778..806a96c5173 100644
--- a/source/_integrations/rflink.markdown
+++ b/source/_integrations/rflink.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate RFLink gateway into Home Assistant
logo: rflink.png
ha_category:
- Hub
+ha_iot_class: Assumed State
ha_release: 0.38
ha_domain: rflink
---
diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown
index 0e1d151b4f1..4b3d3122067 100644
--- a/source/_integrations/rfxtrx.markdown
+++ b/source/_integrations/rfxtrx.markdown
@@ -21,9 +21,9 @@ There is currently support for the following device types within Home Assistant:
- [Cover](#covers)
- [Light](#lights)
+- [Switch](#switches)
- [Sensor](#sensors)
- [Binary Sensor](#binary-sensors)
-- [Switch](#switch)
To enable RFXtrx in your installation, something like the following to your `configuration.yaml` file.
diff --git a/source/_integrations/rocketchat.markdown b/source/_integrations/rocketchat.markdown
index 6fec23d8cfc..f035e9ceb78 100644
--- a/source/_integrations/rocketchat.markdown
+++ b/source/_integrations/rocketchat.markdown
@@ -45,6 +45,6 @@ rocketchat_notification:
#### Message variables
- **message** (*Required*): Message to be displayed.
-- **data** (*Optional*): Dictionary containing any of the variables defined in the [Rocket.Chat documentation](https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage#message-object-example)
+- **data** (*Optional*): Dictionary containing any of the variables defined in the [Rocket.Chat documentation](https://docs.rocket.chat/api/rest-api/methods/chat/postmessage)
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
diff --git a/source/_integrations/sabnzbd.markdown b/source/_integrations/sabnzbd.markdown
index fa3e9db076a..6e957974efc 100644
--- a/source/_integrations/sabnzbd.markdown
+++ b/source/_integrations/sabnzbd.markdown
@@ -14,7 +14,7 @@ The `sabnzbd` integration will allow you to monitor and control your downloads w
If SABnzbd is discovered on your network, you can enter your API Key in the Configurator. Press "CONFIGURE" to do it.
- 
+ 
This will create services for interacting with SABnzbd in scripts and automations, but no sensors will be created.
diff --git a/source/_integrations/scene.markdown b/source/_integrations/scene.markdown
index 990247788e5..0d3d9e8f969 100644
--- a/source/_integrations/scene.markdown
+++ b/source/_integrations/scene.markdown
@@ -12,6 +12,8 @@ ha_domain: scene
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.
+Scenes can be created and managed via the user interface using the [Scene Editor](/docs/scene/editor/). They can also be configured via `configuration.yaml`:
+
```yaml
# Example configuration.yaml entry
scene:
diff --git a/source/_integrations/sendgrid.markdown b/source/_integrations/sendgrid.markdown
index 24e498e2e16..c2b3d2d9afc 100644
--- a/source/_integrations/sendgrid.markdown
+++ b/source/_integrations/sendgrid.markdown
@@ -5,6 +5,7 @@ ha_category:
- Notifications
ha_release: 0.14
ha_domain: sendgrid
+ha_iot_class: Cloud Push
---
The `sendgrid` notification platform sends email notifications via [SendGrid](https://sendgrid.com/), a proven cloud-based email platform.
diff --git a/source/_integrations/sensor.rflink.markdown b/source/_integrations/sensor.rflink.markdown
index 213c182631d..b4b9c5f40b3 100644
--- a/source/_integrations/sensor.rflink.markdown
+++ b/source/_integrations/sensor.rflink.markdown
@@ -4,8 +4,8 @@ description: "Instructions on how to integrate RFLink sensors into Home Assistan
logo: rflink.png
ha_category:
- Sensor
+ha_iot_class: Local Push
ha_release: 0.38
-ha_iot_class: Local Polling
ha_domain: rflink
---
diff --git a/source/_integrations/seven_segments.markdown b/source/_integrations/seven_segments.markdown
index 8f5bce76965..c081034c085 100644
--- a/source/_integrations/seven_segments.markdown
+++ b/source/_integrations/seven_segments.markdown
@@ -130,7 +130,7 @@ image_processing:
```
- 
+ 
With the help of a [template sensor](/integrations/template), the value can be shown as badge.
diff --git a/source/_integrations/shell_command.markdown b/source/_integrations/shell_command.markdown
index 296903b2446..a5028bf72e3 100644
--- a/source/_integrations/shell_command.markdown
+++ b/source/_integrations/shell_command.markdown
@@ -3,6 +3,7 @@ title: Shell Command
description: Instructions on how to integrate Shell commands into Home Assistant.
ha_category:
- Automation
+ha_iot_class: Local Push
ha_release: 0.7.6
ha_quality_scale: internal
ha_codeowners:
diff --git a/source/_integrations/shelly.markdown b/source/_integrations/shelly.markdown
index 5ac20b9c38d..c19049ebdb9 100644
--- a/source/_integrations/shelly.markdown
+++ b/source/_integrations/shelly.markdown
@@ -7,6 +7,7 @@ ha_release: 0.115
ha_codeowners:
- '@balloob'
- '@bieniu'
+ha_iot_class: Local Polling
ha_domain: shelly
featured: true
ha_config_flow: true
diff --git a/source/_integrations/shopping_list.markdown b/source/_integrations/shopping_list.markdown
index e959fde4780..95e71e2c26f 100644
--- a/source/_integrations/shopping_list.markdown
+++ b/source/_integrations/shopping_list.markdown
@@ -6,6 +6,7 @@ ha_category:
ha_release: '0.50'
ha_config_flow: true
ha_quality_scale: internal
+ha_iot_class: Local Push
ha_domain: shopping_list
---
diff --git a/source/_integrations/simplepush.markdown b/source/_integrations/simplepush.markdown
index bc00dccb2c3..9e032af170a 100644
--- a/source/_integrations/simplepush.markdown
+++ b/source/_integrations/simplepush.markdown
@@ -3,6 +3,7 @@ title: Simplepush
description: Instructions on how to add Simplepush notifications to Home Assistant.
ha_category:
- Notifications
+ha_iot_class: Cloud Polling
ha_release: 0.29
ha_domain: simplepush
---
diff --git a/source/_integrations/sky_hub.markdown b/source/_integrations/sky_hub.markdown
index aafb2e22efb..078b9f0f26b 100644
--- a/source/_integrations/sky_hub.markdown
+++ b/source/_integrations/sky_hub.markdown
@@ -7,6 +7,7 @@ ha_release: 0.37
ha_domain: sky_hub
ha_codeowners:
- '@rogerselwyn'
+ha_iot_class: Local Polling
---
The `sky_hub` platform offers presence detection by looking at connected devices to a [Sky Hub router](https://www.sky.com/shop/broadband-talk/sky-hub/) based router.
diff --git a/source/_integrations/smarthab.markdown b/source/_integrations/smarthab.markdown
index 382f1014c6e..aa317d8b391 100644
--- a/source/_integrations/smarthab.markdown
+++ b/source/_integrations/smarthab.markdown
@@ -13,7 +13,7 @@ ha_codeowners:
ha_domain: smarthab
---
-If your home is fitted with [SmartHab](https://www.smarthab.fr/en/home/)'s
+If your home is fitted with [SmartHab](https://smarthab.fr/index.php/home-en)'s
devices and you have access to their app-based services, you will be able
to control your lights and shutters with the SmartHab integration for Home
Assistant.
diff --git a/source/_integrations/snips.markdown b/source/_integrations/snips.markdown
index 5039cdc8b7c..94d6824105a 100644
--- a/source/_integrations/snips.markdown
+++ b/source/_integrations/snips.markdown
@@ -207,10 +207,6 @@ You can send TTS notifications to Snips using the `snips.say` and `snips.say_act
| `can_be_enqueued` | yes | If True, session waits for an open session to end, if False session is dropped if one is running. |
| `intent_filter` | yes | Array of Strings - A list of intents names to restrict the NLU resolution to on the first query. |
-### Snips Support
-
-There is an active [Forum](https://forum.snips.ai) for further support.
-
### Configuration Examples
#### Turn on a light
diff --git a/source/_integrations/sochain.markdown b/source/_integrations/sochain.markdown
index ad8d84fdac6..efcc1dca87d 100644
--- a/source/_integrations/sochain.markdown
+++ b/source/_integrations/sochain.markdown
@@ -9,7 +9,7 @@ ha_iot_class: Cloud Polling
ha_domain: sochain
---
-The `SoChain` sensor platform displays supported cryptocurrency wallet balances from [SoChain](https://chain.so).
+The `SoChain` sensor platform displays supported cryptocurrency wallet balances from [SoChain](https://sochain.com).
To add the SoChain sensor to your installation, specify a network and address to watch in the `configuration.yaml` file:
@@ -37,7 +37,7 @@ name:
default: Crypto Balance
{% endconfiguration %}
-Supported networks (which can also be found [here](https://chain.so/api#networks-supported)) are:
+Supported networks (which can also be found [here](https://sochain.com/api#networks-supported)) are:
* BTC
* LTC
diff --git a/source/_integrations/sonarr.markdown b/source/_integrations/sonarr.markdown
index 99fac8d3655..d661a240d11 100644
--- a/source/_integrations/sonarr.markdown
+++ b/source/_integrations/sonarr.markdown
@@ -16,4 +16,20 @@ The `Sonarr` integration pulls data from a given [Sonarr](https://sonarr.tv/) in
## Configuration
-Go to the integrations page in your configuration and click on new integration -> Sonarr.
+To add Sonarr to Home Assistant, go to **Configuration** -> **Integrations** and click the + button in the bottom right corner. Search for Sonarr and follow the on-screen instructions to complete the setup.
+
+To retrieve your API key, open your Sonarr web interface and navigate to Settings then General tab. Your Sonarr API Key will be listed on this page under the Security section.
+
+## Sensors
+
+The Sonarr integration will add the following sensors:
+
+`sensor.sonarr_upcoming`: The number of upcoming episodes.
+
+The remaining five sensors are disabled by default and can be enabled on the device page.
+
+- `sensor.sonarr_commands`: The number of commands being run.
+- `sensor.sonarr_disk_space`: Available disk space.
+- `sensor.sonarr_queue`: The number of episodes in the queue.
+- `sensor.sonarr_shows`: The number of series in Sonarr.
+- `sensor.sonarr_wanted`: The number of episodes still wanted.
diff --git a/source/_integrations/spaceapi.markdown b/source/_integrations/spaceapi.markdown
index 9ca772520ad..35410ae776b 100644
--- a/source/_integrations/spaceapi.markdown
+++ b/source/_integrations/spaceapi.markdown
@@ -3,6 +3,7 @@ title: Space API
description: Instructions on how to configure the SpaceAPI for Home Assistant.
ha_category:
- Social
+ha_iot_class: Cloud Polling
ha_release: '0.70'
ha_codeowners:
- '@fabaff'
diff --git a/source/_integrations/spotcrime.markdown b/source/_integrations/spotcrime.markdown
index 1d3734f60a4..de4e5ef21d1 100644
--- a/source/_integrations/spotcrime.markdown
+++ b/source/_integrations/spotcrime.markdown
@@ -2,6 +2,8 @@
title: Spot Crime
description: Instructions on how to integrate spotcrime.com into Home Assistant.
ha_release: 0.65
+ha_category:
+ - Sensor
ha_iot_class: Cloud Polling
ha_domain: spotcrime
---
diff --git a/source/_integrations/spotify.markdown b/source/_integrations/spotify.markdown
index 5cba5f98a95..4e4e6cb5752 100644
--- a/source/_integrations/spotify.markdown
+++ b/source/_integrations/spotify.markdown
@@ -12,25 +12,25 @@ ha_codeowners:
ha_domain: spotify
---
-The `spotify` media player integration allows you to control [Spotify](https://www.spotify.com/) playback from Home Assistant.
+The Spotify media player integration allows you to control [Spotify](https://www.spotify.com/) playback from Home Assistant.
## Prerequisites
- Spotify account
-- Spotify application, properly configured (see below).
+- Spotify application configured for Home Assistant (see [below](#create-a-spotify-application))
- Controlling the Spotify integration (pause, play, next, etc.) requires a Premium account.
- If you do not have a Premium account, the integration in the frontend will not show the controls.
+ Spotify integrated media controls (pause, play, next, etc.) requires a Premium account.
+ If you do not have a Premium account, the integration's frontend will not show the controls.
-To create the required Spotify application:
+### Create a 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.
-- On the Spotify page, enter the **Edit Settings** dialog of your newly created application and add a **Redirect URI**:
+- On the Spotify page, enter the **Edit Settings** dialog of your newly created application and add a *Redirect URI*:
- If you are not using SSL: `http://
:/auth/external/callback`
- If you are using SSL: `https://:/auth/external/callback`
- Click **Save** after adding the URI.
@@ -41,7 +41,7 @@ To create the required Spotify application:
## Configuration
-To add Spotify to your installation, add the following to your `configuration.yaml` file:
+To add Spotify to Home Assistant, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
@@ -63,12 +63,11 @@ client_secret:
## Activating the Spotify integration
-After you have set up the above:
-
- Go to the **Configurations** page in the Home Assistant frontend.
-- Go to **Integrations**.
-- Add a new **Spotify** integration.
-- Follow the steps shown to authenticate Home Assistant with your Spotify account.
+- Click on **Integrations**.
+- Click the orange **+** on the bottom-right.
+- Click on "Spotify".
+- Once the new Spotify tab opens, enter your Spotify credentials and allow Home Assistant to access your Spotify account.
@@ -82,18 +81,18 @@ After you have set up the above:
## Using multiple Spotify accounts
The integration support multiple Spotify accounts at once. You don't need to
-create another Spotify Application in the Spotify Developer portal and no
+create another Spotify application in the Spotify Developer Portal and no
modification to the `configuration.yaml` file is needed. Multiple Spotify
-accounts can be linked on a _single_ Spotify application.
+accounts can be linked to a _single_ Spotify application.
To add an additional Spotify account to Home Assistant, repeat _only_ the steps
in the [Activating the Spotify integration](#activating-the-spotify-integration)
-chapter. However, make sure you go to the Spotify website and log out before
+section. However, make sure you go to the Spotify website and log out before
you do so.
## URI Links for Playlists
-You can send playlists to Spotify using the `"media_content_type": "playlist"`, which are part of the
+You can send playlists to Spotify using the `"media_content_type": "playlist"`, which is part of the
[media_player.play_media](/integrations/media_player/#service-media_playerplay_media) service.
The `media_content_id` can be obtained from the Spotify desktop-app by clicking on the more options ("...") next to the album art picture, selecting "share" and then "Copy Spotify URI" or "Copy Playlist Link" (also available in the Spotify phone and web app).
diff --git a/source/_integrations/sql.markdown b/source/_integrations/sql.markdown
index 8dbde56f5ca..8de5999f1e1 100644
--- a/source/_integrations/sql.markdown
+++ b/source/_integrations/sql.markdown
@@ -5,6 +5,7 @@ ha_category:
- Utility
- Sensor
ha_release: 0.63
+ha_iot_class: Local Polling
ha_codeowners:
- '@dgomes'
ha_domain: sql
diff --git a/source/_integrations/statistics.markdown b/source/_integrations/statistics.markdown
index eef4cb23b10..e2948782569 100644
--- a/source/_integrations/statistics.markdown
+++ b/source/_integrations/statistics.markdown
@@ -62,5 +62,5 @@ precision:
{% endconfiguration %}
- 
+ 
diff --git a/source/_integrations/sun.markdown b/source/_integrations/sun.markdown
index 56d34e62b23..1a62c7b5381 100644
--- a/source/_integrations/sun.markdown
+++ b/source/_integrations/sun.markdown
@@ -7,6 +7,7 @@ ha_release: pre 0.7
ha_quality_scale: internal
ha_codeowners:
- '@Swamp-Ig'
+ha_iot_class: Calculated
ha_domain: sun
---
diff --git a/source/_integrations/supervisord.markdown b/source/_integrations/supervisord.markdown
index 7ece0e19100..656012cc364 100644
--- a/source/_integrations/supervisord.markdown
+++ b/source/_integrations/supervisord.markdown
@@ -20,7 +20,7 @@ port=127.0.0.1:9001
After a restart of `supervisord` you should be able to access the web interface. If needed then this could be added as an [iFrame panel](/integrations/panel_iframe/).
- 
+ 
To use this sensor in your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_integrations/supla.markdown b/source/_integrations/supla.markdown
index f6d33d0e142..289344661e5 100644
--- a/source/_integrations/supla.markdown
+++ b/source/_integrations/supla.markdown
@@ -11,7 +11,7 @@ ha_codeowners:
ha_domain: supla
---
-The [Supla](https://supla.org/) is an Open Source home automation system for ESP8266 based devices. It has its own set of protocols, its own firmware and commercially available devices (produced for example by [Zamel](https://supla.zamel.pl/))
+The [Supla](https://supla.org/) is an Open Source home automation system for ESP8266 based devices. It has its own set of protocols, its own firmware and commercially available devices (produced for example by [Zamel](https://zamel.pl/pl-PL/produkty/supla-sterowanie-wi-fi))
Currently only covers (shutters in Supla's lingo), gates and switches are supported, but, thanks to comprehensive and universal REST API, it's pretty easy to add more.
diff --git a/source/_integrations/swisscom.markdown b/source/_integrations/swisscom.markdown
index dc6c370a64a..4df355257a4 100644
--- a/source/_integrations/swisscom.markdown
+++ b/source/_integrations/swisscom.markdown
@@ -5,6 +5,7 @@ ha_category:
- Presence Detection
ha_release: 0.32
ha_domain: swisscom
+ha_iot_class: Local Polling
---
The `swisscom` platform offers presence detection by looking at connected devices to an [Internet-Box](https://www.swisscom.ch/en/residential/help/device/internet-router.html) router from [Swisscom](https://www.swisscom.ch) which is an Internet provider in Switzerland.
diff --git a/source/_integrations/switch.rflink.markdown b/source/_integrations/switch.rflink.markdown
index 2d9279e58d0..798c446bf11 100644
--- a/source/_integrations/switch.rflink.markdown
+++ b/source/_integrations/switch.rflink.markdown
@@ -4,6 +4,7 @@ description: "Instructions on how to integrate RFLink switches into Home Assista
logo: rflink.png
ha_category:
- Switch
+ha_iot_class: Assumed State
ha_release: 0.38
ha_domain: rflink
---
diff --git a/source/_integrations/syslog.markdown b/source/_integrations/syslog.markdown
index 9f9c716ffb4..80d68cbb861 100644
--- a/source/_integrations/syslog.markdown
+++ b/source/_integrations/syslog.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to add syslog notifications to Home Assistant.
ha_category:
- Notifications
ha_release: pre 0.7
+ha_iot_class: Local Push
ha_codeowners:
- '@fabaff'
ha_domain: syslog
diff --git a/source/_integrations/system_health.markdown b/source/_integrations/system_health.markdown
index 53b55ab484f..549ea17b106 100644
--- a/source/_integrations/system_health.markdown
+++ b/source/_integrations/system_health.markdown
@@ -17,4 +17,4 @@ This integration is by default enabled, unless you've disabled or removed the [`
system_health:
```
-System Health integration data can be viewed in Developer Tools on the "Info" tab.
+System Health integration data can be viewed in Configuration -> General Configuration, on the "Info" tab.
diff --git a/source/_integrations/tank_utility.markdown b/source/_integrations/tank_utility.markdown
index ea2f0cf9a84..aaf30f633b5 100644
--- a/source/_integrations/tank_utility.markdown
+++ b/source/_integrations/tank_utility.markdown
@@ -3,6 +3,7 @@ title: Tank Utility
description: How to integrate Tank Utility sensors within Home Assistant.
ha_category:
- Energy
+ha_iot_class: Cloud Polling
ha_release: 0.53
ha_domain: tank_utility
---
diff --git a/source/_integrations/telegram.markdown b/source/_integrations/telegram.markdown
index 4717fa11b75..3d945dcf3fd 100644
--- a/source/_integrations/telegram.markdown
+++ b/source/_integrations/telegram.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to add Telegram notifications to Home Assistant
ha_category:
- Notifications
ha_release: 0.7.5
+ha_iot_class: Cloud Polling
ha_domain: telegram
---
diff --git a/source/_integrations/tellduslive.markdown b/source/_integrations/tellduslive.markdown
index fc99d063d2a..e34389cbd8c 100644
--- a/source/_integrations/tellduslive.markdown
+++ b/source/_integrations/tellduslive.markdown
@@ -19,7 +19,7 @@ ha_domain: tellduslive
The `tellduslive` integration let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick Net or Tellstick ZNet connected gear at home.
-Home Assistant will automatically discover the presence of a Tellstick Net or Tellstick ZNet on your local network if the [discovery]({{site_root}}/integrations/discovery/) integration is enabled. When discovery and the key exchange with Telldus Live have been completed, you will be presented with an option to integrate with the cloud or local API for direct communication with your hardware in your LAN. Local API supports only one device at this stage. Local API is only supported with the Znet Lite products, the older hardware (such as Tellstick Net) does not support local API.
+Home Assistant will automatically discover the presence of a Tellstick Net or Tellstick ZNet on your local network if the [discovery](/integrations/discovery/) integration is enabled. When discovery and the key exchange with Telldus Live have been completed, you will be presented with an option to integrate with the cloud or local API for direct communication with your hardware in your LAN. Local API supports only one device at this stage. Local API is only supported with the Znet Lite products, the older hardware (such as Tellstick Net) does not support local API.
## Configuration
diff --git a/source/_integrations/thomson.markdown b/source/_integrations/thomson.markdown
index 2b445ad7f38..d1427b20ee8 100644
--- a/source/_integrations/thomson.markdown
+++ b/source/_integrations/thomson.markdown
@@ -5,6 +5,7 @@ ha_category:
- Presence Detection
ha_release: 0.7
ha_domain: thomson
+ha_iot_class: Local Polling
---
Thomson produced networking equipment (under the brand name SpeedTouch) till 2010 and was then renamed to Technicolor.
diff --git a/source/_integrations/time_date.markdown b/source/_integrations/time_date.markdown
index 2be41354a75..656078cd769 100644
--- a/source/_integrations/time_date.markdown
+++ b/source/_integrations/time_date.markdown
@@ -32,5 +32,5 @@ sensor:
- **display_options** array (*Required*): The option to display. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://www.swatch.com/en_us/internet-time).
- 
+ 
diff --git a/source/_integrations/timer.markdown b/source/_integrations/timer.markdown
index 2595218159a..8fb0f2f93ff 100644
--- a/source/_integrations/timer.markdown
+++ b/source/_integrations/timer.markdown
@@ -110,13 +110,7 @@ Reload `timer`'s configuration without restarting Home Assistant itself. This se
### Use the service
-Select
**Services** from the **Developer Tools**. Choose **timer** from the list of **Domains**, select the **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**.
-
-```json
-{
- "entity_id": "timer.timer0"
-}
-```
+Navigate to **Developer Tools** -> **Services** and select the `timer.start` service, then click the **Fill Example Data** button. Now change the `entity_id` and `duration` and click **Call Service** button.
## Examples
diff --git a/source/_integrations/totalconnect.markdown b/source/_integrations/totalconnect.markdown
index c30007ac8de..9727736c885 100644
--- a/source/_integrations/totalconnect.markdown
+++ b/source/_integrations/totalconnect.markdown
@@ -5,6 +5,7 @@ ha_category:
- Alarm
- Binary Sensor
ha_release: 0.42
+ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@austinmroczek'
diff --git a/source/_integrations/trafikverket_weatherstation.markdown b/source/_integrations/trafikverket_weatherstation.markdown
index dbf0467d8dc..b57991c0b0e 100644
--- a/source/_integrations/trafikverket_weatherstation.markdown
+++ b/source/_integrations/trafikverket_weatherstation.markdown
@@ -91,7 +91,7 @@ Please click [here](https://api.trafikinfo.trafikverket.se/) and register to obt
Click [here](https://www.trafikverket.se/trafikinformation/vag/?TrafficType=personalTraffic&map=1/606442.17/6886316.22/&Layers=RoadWeather%2b) to get a map of valid weather stations. Once a station is found, copy the name according to the below picture and paste it in your `configuration.yaml` file as the `station` variable.
- 
+ 
## Examples
diff --git a/source/_integrations/transmission.markdown b/source/_integrations/transmission.markdown
index 1079880051b..66e36b71661 100644
--- a/source/_integrations/transmission.markdown
+++ b/source/_integrations/transmission.markdown
@@ -14,27 +14,17 @@ ha_codeowners:
ha_domain: transmission
---
-The `transmission` integration allows you to monitor your downloads with [Transmission](https://www.transmissionbt.com/) from within Home Assistant and setup automation based on the information.
+The Transmission integration allows you to monitor your [Transmission](https://www.transmissionbt.com/) BitTorrent downloads from within Home Assistant and set up automations based on that information.
## Setup
-To use the monitoring, your transmission client needs to allow remote access. If you are running the graphical transmission client (transmission-gtk) go to **Edit** -> **Preferences** and choose the tab **Remote**. Check **Allow remote access**, enter your username and your password, and uncheck the network restriction as needed.
-
-
- 
-
-
-If everything is set up correctly, the details will show up in the frontend.
-
-
- 
-
+Your Transmission client must first be configured to allow remote access. In your Transmission client navigate to **Preferences** -> **Remote** tab and then click the **Allow remote access** checkbox.
## Configuration
-Set up the integration through **Configuration** -> **Integrations** -> **Transmission**. For legacy support old transmission configuration is imported and set up as new integration. Make sure to remove `monitored_condiditions` as they are now automatically added to Home Assistant
+In Home Assistant, navigate to **Configuration** -> **Integrations** and click the plus button to add a new integration and search for **Transmission**. For legacy support old Transmission configuration is imported and set up as a new integration. Make sure to remove `monitored_conditions` as they are now automatically added to Home Assistant.
-To enable this sensor, add the following lines to your `configuration.yaml`:
+Alternatively, the integration can be set up via YAML by adding the following lines to your `configuration.yaml`:
```yaml
transmission:
@@ -71,21 +61,21 @@ scan_interval:
## Integration Entities
-The Transmission Integration will add the following sensors and switches.
+The Transmission integration will add the following sensors and switches.
-Sensors:
-- transmission_current_status: The status of your Transmission daemon.
-- transmission_download_speed: The current download speed [MB/s].
-- transmission_upload_speed: The current upload speed [MB/s].
-- transmission_active_torrents: The current number of active torrents.
-- transmission_paused_torrents: The current number of paused torrents.
-- transmission_total_torrents: The total number of torrents present in the client.
-- transmission_started_torrents: The current number of started torrents (downloading).
-- transmission_completed_torrents: The current number of completed torrents (seeding)
+**Sensors**:
+- `sensor.transmission_current_status`: The status of your Transmission daemon.
+- `sensor.transmission_download_speed`: The current download speed [MB/s].
+- `sensor.transmission_upload_speed`: The current upload speed [MB/s].
+- `sensor.transmission_active_torrents`: The current number of active torrents.
+- `sensor.transmission_paused_torrents`: The current number of paused torrents.
+- `sensor.transmission_total_torrents`: The total number of torrents present in the client.
+- `sensor.transmission_started_torrents`: The current number of started torrents (downloading).
+- `sensor.transmission_completed_torrents`: The current number of completed torrents (seeding).
-Switches:
-- transmission_switch: A switch to start/stop all torrents
-- transmission_turtle_mode: A switch to enable turtle mode.
+**Switches**:
+- `switch.transmission_switch`: A switch to start/stop all torrents.
+- `switch.transmission_turtle_mode`: A switch to enable turtle mode (a.k.a. alternative speed limits).
## Event Automation
@@ -94,9 +84,9 @@ The Transmission integration is continuously monitoring the status of torrents i
Possible events are:
-- transmission_downloaded_torrent
-- transmission_started_torrent
-- transmission_removed_torrent
+- `transmission_downloaded_torrent`
+- `transmission_started_torrent`
+- `transmission_removed_torrent`
Inside of the event, there is the name of the torrent that is started or completed, as it is seen in the Transmission User Interface.
@@ -142,7 +132,7 @@ Removes a torrent from the client.
### Attribute `torrent_info`
-All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a Markdown Card to Lovelace.
+All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a [Markdown card](/lovelace/markdown/) to Lovelace with the following code:
{% raw %}
```yaml
diff --git a/source/_integrations/tts.markdown b/source/_integrations/tts.markdown
index aa24da0370c..9c679491bda 100644
--- a/source/_integrations/tts.markdown
+++ b/source/_integrations/tts.markdown
@@ -1,6 +1,8 @@
---
title: Text-to-Speech (TTS)
description: Instructions on how to set up Text-to-Speech (TTS) with Home Assistant.
+ha_category:
+ - Text-to-speech
ha_release: 0.35
ha_codeowners:
- '@pvizeli'
@@ -92,7 +94,9 @@ The Google cast devices (Google Home, Chromecast, etc.) present the following pr
* They [reject self-signed certificates](#self-signed-certificates).
-* They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). Setting a internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname.
+* They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). If you are _not_ using SSL then setting a internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname.
+
+* If you are using an SSL (e.g., `https://yourhost.example.org/...`) then you _must_ use the hostname in the certificate (e.g., `base_url: https://yourhost.example.org`). You cannot use an IP address since the certificate won't be valid for the IP address, and the cast device will refuse the connection.
## Service say
diff --git a/source/_integrations/twilio_sms.markdown b/source/_integrations/twilio_sms.markdown
index b240d36d14f..db1cad1683a 100644
--- a/source/_integrations/twilio_sms.markdown
+++ b/source/_integrations/twilio_sms.markdown
@@ -5,6 +5,7 @@ ha_category:
- Notifications
ha_release: '0.20'
ha_domain: twilio_sms
+ha_iot_class: Cloud Push
---
The `twilio` notification platform enables sending notifications via SMS, powered by [Twilio](https://twilio.com).
diff --git a/source/_integrations/twitch.markdown b/source/_integrations/twitch.markdown
index 12927722335..26f019be52f 100644
--- a/source/_integrations/twitch.markdown
+++ b/source/_integrations/twitch.markdown
@@ -12,7 +12,7 @@ The `twitch` platform will allow you to monitor [Twitch](https://www.twitch.tv/)
## Setup Client ID
-Create a new app at "Register Your Application" in the [Twitch developer portal](https://glass.twitch.tv/console/apps). Then get the __Client ID__ for the new application.
+Create a new app at "Register Your Application" in the [Twitch developer portal](https://dev.twitch.tv/console/apps). Then get the __Client ID__ for the new application.
## Setup OAuth Token
diff --git a/source/_integrations/twitter.markdown b/source/_integrations/twitter.markdown
index e63d4287f46..eae0d8dec16 100644
--- a/source/_integrations/twitter.markdown
+++ b/source/_integrations/twitter.markdown
@@ -5,6 +5,7 @@ ha_category:
- Notifications
ha_release: 0.12
ha_domain: twitter
+ha_iot_class: Cloud Push
---
The `twitter` notification platform uses [Twitter](https://twitter.com) to deliver notifications from Home Assistant.
diff --git a/source/_integrations/ubee.markdown b/source/_integrations/ubee.markdown
index d106181b596..6e355a24120 100644
--- a/source/_integrations/ubee.markdown
+++ b/source/_integrations/ubee.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate Ubee routers into Home Assistant.
ha_category:
- Presence Detection
ha_release: 0.89
+ha_iot_class: Local Polling
ha_codeowners:
- '@mzdrale'
ha_domain: ubee
diff --git a/source/_integrations/uk_transport.markdown b/source/_integrations/uk_transport.markdown
index 10247ffe356..b8eacf5b8e5 100644
--- a/source/_integrations/uk_transport.markdown
+++ b/source/_integrations/uk_transport.markdown
@@ -8,7 +8,7 @@ ha_release: '0.50'
ha_domain: uk_transport
---
-The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier](https://www.transportapi.com/plans/) allows 1000 requests daily, which is sufficient for a single sensor refreshing every 87 seconds.
+The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier](https://www.transportapi.com/benefits/) allows 30,000 requests a month, which is sufficient for a single sensor refreshing every 87 seconds.
diff --git a/source/_integrations/upc_connect.markdown b/source/_integrations/upc_connect.markdown
index 18921c03faf..3aff1a1b7b3 100644
--- a/source/_integrations/upc_connect.markdown
+++ b/source/_integrations/upc_connect.markdown
@@ -8,6 +8,7 @@ ha_codeowners:
- '@pvizeli'
- '@fabaff'
ha_domain: upc_connect
+ha_iot_class: Local Polling
---
The `upc_connect` platform offers presence detection by looking at connected devices to a [Connect Box](https://www.upc.ch/en/internet/learn-about-internet/) from [Liberty Global](https://www.libertyglobal.com) (also known as UPC Cablecom in Switzerland) which is an Internet provider in Switzerland, Austria and the Netherlands (under Ziggo).
diff --git a/source/_integrations/updater.markdown b/source/_integrations/updater.markdown
index a9459387da2..5488a931e04 100644
--- a/source/_integrations/updater.markdown
+++ b/source/_integrations/updater.markdown
@@ -4,6 +4,7 @@ description: Detecting when Home Assistant updates are available.
ha_category:
- Binary Sensor
ha_release: 0.8
+ha_iot_class: Cloud Polling
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
diff --git a/source/_integrations/usgs_earthquakes_feed.markdown b/source/_integrations/usgs_earthquakes_feed.markdown
index 3ce7e4b9dcf..2a24463e2f9 100644
--- a/source/_integrations/usgs_earthquakes_feed.markdown
+++ b/source/_integrations/usgs_earthquakes_feed.markdown
@@ -13,13 +13,13 @@ ha_domain: usgs_earthquakes_feed
The `usgs_earthquakes_feed` platform lets you integrate a GeoJSON feed provided by the [U.S. Geological Survey](https://earthquake.usgs.gov/) with information about seismic events like earthquakes. It retrieves incidents from a feed and shows information of those incidents filtered by distance to Home Assistant's location.
- 
+ 
Entities are generated, updated and removed automatically with each update from the feed. Each entity defines latitude and longitude and will be shown on the map automatically. The distance in kilometers is available as the state of each entity.
- 
+ 
The data is updated every 5 minutes.
diff --git a/source/_integrations/vacuum.markdown b/source/_integrations/vacuum.markdown
index dcc4f981132..6d11b4c6705 100644
--- a/source/_integrations/vacuum.markdown
+++ b/source/_integrations/vacuum.markdown
@@ -9,7 +9,7 @@ The `vacuum` integration enables the ability to control home cleaning robots wit
## Configuration
-To use this integration in your installation, add a `vacuum` platform to your `configuration.yaml` file, like the [Xiaomi](/integrations/vacuum.xiaomi_miio/).
+To use this integration in your installation, add a `vacuum` platform to your `configuration.yaml` file, like the [Xiaomi](/integrations/xiaomi_miio#xiaomi-mi-robot-vacuum).
```yaml
# Example configuration.yaml entry
diff --git a/source/_integrations/vallox.markdown b/source/_integrations/vallox.markdown
index b9826cb0361..977aa2f9fb5 100644
--- a/source/_integrations/vallox.markdown
+++ b/source/_integrations/vallox.markdown
@@ -78,10 +78,10 @@ automation:
- entity_id: sensor.vallox_current_profile
platform: state
action:
- - data_template:
- entity_id: input_select.ventilation_profile
- option: "{{ states('sensor.vallox_current_profile') }}"
- service: input_select.select_option
+ - service: input_select.select_option
+ data:
+ entity_id: input_select.ventilation_profile
+ option: "{{ states('sensor.vallox_current_profile') }}"
```
{% endraw %}
diff --git a/source/_integrations/velux.markdown b/source/_integrations/velux.markdown
index 6aeca027e3c..4272304154d 100644
--- a/source/_integrations/velux.markdown
+++ b/source/_integrations/velux.markdown
@@ -13,7 +13,7 @@ ha_domain: velux
[Velux](https://www.velux.com/) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200.
-At least firmware version > 2.0.0.0 is required on the KLF 200 device. The firmware images may be obtained [here](https://www.velux.com/api/klf200) and may be imported via the webinterface of your KLF 200.
+At least firmware version > 2.0.0.0 is required on the KLF 200 device. The firmware images may be obtained [here](https://www.velux.com/klf200) and may be imported via the webinterface of your KLF 200.
There is currently support for the following device types within Home Assistant:
@@ -27,8 +27,8 @@ A `velux` section must be present in the `configuration.yaml` file and contain t
```yaml
# Example configuration.yaml entry
velux:
- host: "192.168.1.23"
- password: "VELUX_PASSWORD"
+ host: IP_ADDRESS
+ password: VELUX_PASSWORD
```
{% configuration %}
diff --git a/source/_integrations/vera.markdown b/source/_integrations/vera.markdown
index 4ff7aa9cd98..5c7f94f139a 100644
--- a/source/_integrations/vera.markdown
+++ b/source/_integrations/vera.markdown
@@ -12,6 +12,7 @@ ha_category:
- Switch
- Climate
ha_release: pre 0.7
+ha_iot_class: Local Polling
ha_config_flow: true
ha_domain: vera
ha_codeowners:
diff --git a/source/_integrations/vesync.markdown b/source/_integrations/vesync.markdown
index b2b7602b0cd..eb5c5856ef4 100644
--- a/source/_integrations/vesync.markdown
+++ b/source/_integrations/vesync.markdown
@@ -5,6 +5,7 @@ ha_category:
- Switch
- Fan
ha_release: 0.66
+ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@markperdue'
diff --git a/source/_integrations/voicerss.markdown b/source/_integrations/voicerss.markdown
index 013a93f4bf7..8d059c7ef68 100644
--- a/source/_integrations/voicerss.markdown
+++ b/source/_integrations/voicerss.markdown
@@ -42,7 +42,7 @@ format:
default: 8khz_8bit_mono
{% endconfiguration %}
-Check the [VoiceRSS API documentation](http://www.voicerss.org/api/documentation.aspx) for allowed values.
+Check the [VoiceRSS API documentation](http://www.voicerss.org/api/) for allowed values.
## Full configuration example
diff --git a/source/_integrations/watson_tts.markdown b/source/_integrations/watson_tts.markdown
index f2dc28c131b..f0235ebd945 100644
--- a/source/_integrations/watson_tts.markdown
+++ b/source/_integrations/watson_tts.markdown
@@ -32,7 +32,7 @@ tts:
You can get these tokens after you generated the credentials on the IBM Cloud console:
- 
+ 
{% configuration %}
diff --git a/source/_integrations/weather.markdown b/source/_integrations/weather.markdown
index 3c74ca7b68a..74a007397f1 100644
--- a/source/_integrations/weather.markdown
+++ b/source/_integrations/weather.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to setup your Weather platforms with Home Assis
ha_category:
- Weather
ha_release: 0.32
+ha_iot_class: ~
ha_quality_scale: internal
ha_codeowners:
- '@fabaff'
diff --git a/source/_integrations/wemo.markdown b/source/_integrations/wemo.markdown
index 85aec666763..64e2f69435c 100644
--- a/source/_integrations/wemo.markdown
+++ b/source/_integrations/wemo.markdown
@@ -8,11 +8,12 @@ ha_category:
- Light
- Switch
ha_release: pre 0.7
+ha_iot_class: Local Push
ha_config_flow: true
ha_domain: wemo
---
-The `wemo` integration is the main integration to integrate various [Belkin WeMo](https://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) devices with Home Assistant.
+The `wemo` integration is the main integration to integrate various [Belkin WeMo](https://www.belkin.com/us/c/wemo/) devices with Home Assistant.
There is currently support for the following device types within Home Assistant:
diff --git a/source/_integrations/worldtidesinfo.markdown b/source/_integrations/worldtidesinfo.markdown
index 341af74e66e..a5fe41c135a 100644
--- a/source/_integrations/worldtidesinfo.markdown
+++ b/source/_integrations/worldtidesinfo.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to add Tides information to Home Assistant.
ha_category:
- Environment
ha_release: 0.52
+ha_iot_class: Cloud Polling
ha_domain: worldtidesinfo
---
diff --git a/source/_integrations/wsdot.markdown b/source/_integrations/wsdot.markdown
index cba9c7cee98..d6263dbf6e4 100644
--- a/source/_integrations/wsdot.markdown
+++ b/source/_integrations/wsdot.markdown
@@ -87,5 +87,5 @@ WSDOT does provide information about ferry schedules, mountain passes, tolls, et
Here's an example of the sensor in use:
- 
+ 
diff --git a/source/_integrations/wunderground.markdown b/source/_integrations/wunderground.markdown
index 20df1435faa..b2d22baa0b1 100644
--- a/source/_integrations/wunderground.markdown
+++ b/source/_integrations/wunderground.markdown
@@ -12,7 +12,7 @@ The `wunderground` platform uses [Weather Underground](https://www.wunderground.
-Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). They no longer offer free API keys, and all keys must be paid for. At this time existing free keys will continue to work, but will be disabled Dec 31, 2018, except you own a personal weather station and provide your data to WU (PWS Uploader). As of Sept 6, 2018 Weather Underground states they are declaring the [End of Service for the Weather Underground API](https://apicommunity.wunderground.com/weatherapi/topics/end-of-service-for-the-weather-underground-api). They say they will develop new plans for non-commercial users. No timeline for this has been announced.
+Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). They no longer offer free API keys, and all keys must be paid for. At this time existing free keys will continue to work, but will be disabled Dec 31, 2018, except you own a personal weather station and provide your data to WU (PWS Uploader). As of Sept 6, 2018 Weather Underground states they are declaring the End of Service for the Weather Underground API. They say they will develop new plans for non-commercial users. No timeline for this has been announced.
Please consider this when using the following information.
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 973e47c6917..802d64c365d 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -321,7 +321,7 @@ Supported devices:
| Air Purifier 2 (mini) | zhimi.airpurifier.m1 | |
| Air Purifier (mini) | zhimi.airpurifier.m2 | |
| Air Purifier MA1 | zhimi.airpurifier.ma1 | |
-| Air Purifier 2S | zhimi.airpurifier.ma2 | |
+| Air Purifier MA2 | zhimi.airpurifier.ma2 | |
| Air Purifier 2S | zhimi.airpurifier.mc1 | |
| Air Purifier Super | zhimi.airpurifier.sa1 | |
| Air Purifier Super 2 | zhimi.airpurifier.sa2 | |
diff --git a/source/_integrations/yale_smart_alarm.markdown b/source/_integrations/yale_smart_alarm.markdown
index 9f493012d93..63db9a507c6 100644
--- a/source/_integrations/yale_smart_alarm.markdown
+++ b/source/_integrations/yale_smart_alarm.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate Yale Smart Alarms into Home Assist
ha_category:
- Alarm
ha_release: 0.78
+ha_iot_class: Cloud Polling
ha_domain: yale_smart_alarm
---
diff --git a/source/_integrations/yandex_transport.markdown b/source/_integrations/yandex_transport.markdown
index 3f3a81b585a..6d92d606572 100644
--- a/source/_integrations/yandex_transport.markdown
+++ b/source/_integrations/yandex_transport.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to set up Yandex transport with Home Assistant.
ha_category:
- Sensor
- Transport
+ha_iot_class: Cloud Polling
ha_release: '0.100'
ha_codeowners:
- '@rishatik92'
diff --git a/source/_integrations/yessssms.markdown b/source/_integrations/yessssms.markdown
index a41bac51895..c77f4dbc594 100644
--- a/source/_integrations/yessssms.markdown
+++ b/source/_integrations/yessssms.markdown
@@ -7,6 +7,7 @@ ha_release: 0.57
ha_codeowners:
- '@flowolf'
ha_domain: yessssms
+ha_iot_class: Cloud Push
---
The `yessssms` platform is using the Austrian mobile operator [Yesss.at](https://yesss.at) and others to send SMS via their web-site.
@@ -50,6 +51,11 @@ notify:
```
{% configuration %}
+name:
+ description: "The optional parameter name allows multiple notifiers to be created. The notifier will bind to the service notify.NOTIFIER_NAME."
+ required: false
+ type: string
+ default: notify
username:
description: This is your login name (usually your phone number). Veryfy that you can use your credentials on the Yesss.at website.
required: true
diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown
index 50ec8521451..a30b2021d0c 100644
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@@ -21,8 +21,9 @@ ha_codeowners:
ha_domain: zha
---
-[Zigbee Home Automation](https://zigbeealliance.org) (ZHA)
-integration for Home Assistant allows you to connect many off-the-shelf Zigbee based devices to Home Assistant, using one of the available Zigbee radio modules that is compatible with [zigpy](https://github.com/zigpy/zigpy) (an open source Python library implementing a Zigbee stack, which in turn relies on separate libraries which can each interface a with Zigbee radio module a different manufacturer).
+The ZHA (Zigbee Home Automation) integration allows you to connect many off-the-shelf [Zigbee based devices](https://zigbeealliance.org) directly to Home Assistant, using one of the many available Zigbee coordinators.
+
+ZHA uses an open-source Python library implementing a hardware-independent Zigbee stack called [zigpy](https://github.com/zigpy/zigpy). All coordinators compatible with zigpy can be used with ZHA.
There is currently support for the following device types within Home Assistant:
diff --git a/source/_integrations/zone.markdown b/source/_integrations/zone.markdown
index e2277ab15aa..17a983d882c 100644
--- a/source/_integrations/zone.markdown
+++ b/source/_integrations/zone.markdown
@@ -8,6 +8,7 @@ ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
ha_domain: zone
+ha_iot_class: ~
---
Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a [trigger](/getting-started/automation-trigger/#zone-trigger) or [condition](/getting-started/automation-condition/#zone-condition) inside automation setups.
diff --git a/source/_lovelace/entities.markdown b/source/_lovelace/entities.markdown
index c514ddc5534..63540c99193 100644
--- a/source/_lovelace/entities.markdown
+++ b/source/_lovelace/entities.markdown
@@ -124,6 +124,10 @@ name:
required: true
description: Main Label.
type: string
+icon:
+ required: false
+ description: An icon to display to the left of the label.
+ type: string
action_name:
required: false
description: Button label.
@@ -361,6 +365,14 @@ entities:
name: Home Assistant
url: https://www.home-assistant.io/
icon: mdi:home-assistant
+ - type: button
+ name: Power cycle LibreELEC
+ icon: mdi:power-cycle
+ tap_action:
+ action: call-service
+ confirmation:
+ text: Are you sure you want to restart?
+ service: script.libreelec_power_cycle
```
diff --git a/source/_posts/2014-12-26-home-control-home-automation-and-the-smart-home.markdown b/source/_posts/2014-12-26-home-control-home-automation-and-the-smart-home.markdown
index 57c89c7b547..aef14d092d6 100644
--- a/source/_posts/2014-12-26-home-control-home-automation-and-the-smart-home.markdown
+++ b/source/_posts/2014-12-26-home-control-home-automation-and-the-smart-home.markdown
@@ -18,9 +18,9 @@ There is no widely adopted open standard for smart device communication. This pr
As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers **home control**.
-
+
+ src='/images/screenshots/nexus_7_dashboard.png' />
Example of a hub's dashboard. Showing the state of 2 persons, 4 lights and the sun.
@@ -38,9 +38,9 @@ A glimpse today at how the future can look is the [Nest thermostat](https://nest
All this results in the following overview of Home Automation.
-
+
+ src='/images/architecture/home_automation_landscape.png' />
Overview of the home automation landscape.
diff --git a/source/_posts/2015-01-04-hey-pushbullet-nice-talking-to-you.markdown b/source/_posts/2015-01-04-hey-pushbullet-nice-talking-to-you.markdown
index 2e6acf5183f..2cb35ceb7f1 100644
--- a/source/_posts/2015-01-04-hey-pushbullet-nice-talking-to-you.markdown
+++ b/source/_posts/2015-01-04-hey-pushbullet-nice-talking-to-you.markdown
@@ -13,7 +13,7 @@ One of the things that was missing in Home Assistant for a while was a way to co
The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome [PushBullet](https://www.pushbullet.com/) but any other messaging platform can be easily added.
- 
+ 
A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
diff --git a/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown b/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
index c91d1f9296e..b594c8269ff 100644
--- a/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
+++ b/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
@@ -20,4 +20,4 @@ To enable the discovery component, add the following to your `home-assistant.con
[discovery]
```
-A new [discovery section]({{site_root}}/developers/add_new_platform/#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.
+A new [discovery section](/developers/add_new_platform/#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.
diff --git a/source/_posts/2015-01-13-nest-in-da-house.markdown b/source/_posts/2015-01-13-nest-in-da-house.markdown
index 9de412752d8..4642af07161 100644
--- a/source/_posts/2015-01-13-nest-in-da-house.markdown
+++ b/source/_posts/2015-01-13-nest-in-da-house.markdown
@@ -11,7 +11,7 @@ categories: Release-Notes
For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as we're expanding the supported devices. Today, we're proud to introduce Nest Thermostat integration for Home Assistant contributed by [Stefano Fiorini](https://github.com/sfiorini)!
-
+
The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package [python-nest by jkoelker](https://github.com/jkoelker/python-nest) to talk to the Nest.
diff --git a/source/_posts/2015-02-07-looking-at-the-past.markdown b/source/_posts/2015-02-07-looking-at-the-past.markdown
index 08b4db93801..16ec71f5d71 100644
--- a/source/_posts/2015-02-07-looking-at-the-past.markdown
+++ b/source/_posts/2015-02-07-looking-at-the-past.markdown
@@ -20,8 +20,8 @@ Adding history to the UI was a challenge on itself because the old UI did not su
The history component will be enabled for new users by default. For current users, run `scripts/update` to upgrade to the latest version and add `[history]` to your `home-assistant.conf` file.
-
-
+
+
diff --git a/source/_posts/2015-03-08-new-logo.markdown b/source/_posts/2015-03-08-new-logo.markdown
index 753e0d06791..da5e6ed1fb5 100644
--- a/source/_posts/2015-03-08-new-logo.markdown
+++ b/source/_posts/2015-03-08-new-logo.markdown
@@ -13,6 +13,6 @@ It is well known that you are either a good programmer or a good designer. It's
The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).
-
+
The old logo, the new detailed logo and the new simple logo.
diff --git a/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown b/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown
index 4fa16538b3d..c86fe872ab9 100644
--- a/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown
+++ b/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown
@@ -19,8 +19,8 @@ This release also includes some new platforms (because they keep coming!):
- Light: [blinkstick platform](/integrations/blinksticklight) added ([@alanbowman](https://github.com/alanbowman))
- Device Tracker: [SNMP platform](/integrations/snmp) added ([@tomduijf](https://github.com/tomduijf))
- - Light: [rfxtrx platform](/integrations/light.rfxtrx/) added ([@badele](https://github.com/badele))
- - Switch: [rfxtrx platform](/integrations/switch.rfxtrx/) added ([@badele](https://github.com/badele))
+ - Light: [rfxtrx platform](/integrations/rfxtrx#lights) added ([@badele](https://github.com/badele))
+ - Switch: [rfxtrx platform](/integrations/rfxtrx#switches) added ([@badele](https://github.com/badele))
- Notify: [telegram platform](/integrations/telegram) added ([@fabaff](https://github.com/fabaff))
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command. This has been implemented for the [iTunes platform](/integrations/itunes).
diff --git a/source/_posts/2015-12-12-philips-hue-blocks-3rd-party-bulbs.markdown b/source/_posts/2015-12-12-philips-hue-blocks-3rd-party-bulbs.markdown
index d94741df9c5..07ca7f69c90 100644
--- a/source/_posts/2015-12-12-philips-hue-blocks-3rd-party-bulbs.markdown
+++ b/source/_posts/2015-12-12-philips-hue-blocks-3rd-party-bulbs.markdown
@@ -19,7 +19,7 @@ Philips Hue FAQ entries regarding reversing the decision.
Philips Hue was one of the first to get smart lights accepted by the mainstream. Their Zigbee-based hub is rock solid, never crashes, great API and worked with other Zigbee light bulbs too. They are a bit expensive but the platform was worth every penny, till now.
-Yesterday a thread on [/r/homeautomation][reddit-hue] published that Philips Hue now blocks all but their own bulbs and those of "friends of Hue". I have been able to confirm this in the [Philips Hue FAQ][philips-hue-faq] (Update Dec 14: they have removed the entries - [mirror here][philips-hue-faq-mirror]):
+Yesterday a thread on [/r/homeautomation][reddit-hue] published that Philips Hue now blocks all but their own bulbs and those of "friends of Hue". I have been able to confirm this in the Philips Hue FAQ (Update Dec 14: they have removed the entries - [mirror here][philips-hue-faq-mirror]):
@@ -41,5 +41,4 @@ I will no longer suggest people to buy into the Philips Hue ecosystem.
[philips-reverse]: http://www.developers.meethue.com/documentation/friends-hue-update
[reddit-hue]: https://www.reddit.com/r/homeautomation/comments/3wet8h/fyi_the_hue_hub_is_now_blocking_third_party/
-[philips-hue-faq]: http://www2.meethue.com/en-us/support/search/?q=Another+brand
[philips-hue-faq-mirror]: /images/blog/2015-12-philips-hue-3rd-party/mirror.png
diff --git a/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown b/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
index a51912801d5..d55ab615381 100644
--- a/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
+++ b/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
@@ -49,7 +49,7 @@ Example of the new views in the frontend. Learn m
[Nest]: /integrations/nest/
[onewire]: /integrations/onewire
[OwnTracks]: /integrations/owntracks
-[Rfxtrx]: /integrations/light.rfxtrx/
+[Rfxtrx]: /integrations/rfxtrx#lights
[Statsd]: /integrations/statsd/
[Template]: /integrations/template
[Thermostat]: /integrations/climate/
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 1f263841b77..25cc77213bd 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
@@ -42,13 +42,13 @@ It's been another two weeks which means it's time for release: 0.14!
### Backwards incompatible changes
- - Component: Simple Alarm has been removed. Still available in [the cookbook].
+ - Component: Simple Alarm has been removed. Still available in the cookbook.
- Script: Turning on a [script] that is already on is now a no-op instead of skipping current delay.
- Wemo switches now have to be set up via the main [Wemo component]
- Command line platforms for [switch][switch.cmd], [sensor][sensor.cmd] and [binary_sensor][binary_sensor.cmd] have been renamed to `command_line`.
- The rfxtrx sensors entity ids will incur a one time change to move to a stable format. See [the docs][sensor.rfxtrx] for more details.
-[sensor.rfxtrx]: /integrations/sensor.rfxtrx/
+[sensor.rfxtrx]: /integrations/rfxtrx#sensors
[notify.command_line]: /integrations/notify.command_line/
[Verisure]: /integrations/verisure
[binary_sensor.tcp]: /integrations/tcp#binary-sensor
@@ -66,7 +66,6 @@ It's been another two weeks which means it's time for release: 0.14!
[Wemo]: /integrations/wemo
[Steam]: /integrations/steam_online
[Wink]: /integrations/wink#binary-sensor
-[the cookbook]: /cookbook/python_component_simple_alarm/
[script]: /integrations/script/
[Wemo component]: /integrations/wemo/
[switch.cmd]: /integrations/switch.command_line/
diff --git a/source/_posts/2016-05-21-release-020.markdown b/source/_posts/2016-05-21-release-020.markdown
index 355de586afa..c2ad7797887 100644
--- a/source/_posts/2016-05-21-release-020.markdown
+++ b/source/_posts/2016-05-21-release-020.markdown
@@ -8,7 +8,7 @@ author_twitter: balloob
categories: Release-Notes
---
-
+
Tons of new supported things in 0.20.
diff --git a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
index 9750eeaadb3..ab81d5afd8e 100644
--- a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
+++ b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
@@ -20,11 +20,11 @@ The brand-new [iFrame panel component][iframe_panel] allows you to add other web
I would like to do a shoutout to [@fabianhjr]. He has started adding [typing] data ([PEP484]) to the Home Assistant core. This will help us identify issues before they are released.
-
+
- Frontend: Support for [iFrame panels][iframe_panel] to adding other sites to sidebar ([@balloob])
- Allow components to register [custom frontend panels][custom-panels] ([@balloob])
-- Add example custom_component [react_panel][react-panel] showing custom panels ([@balloob])
+- Add example custom_component react_panel showing custom panels ([@balloob])
- Light: [MagicLight/Flux WiFi Color LED Light][flux] support ([@Danielhiversen])
- Script: Specify a delay [using templates][script] ([@Teagan42])
- Media player: [Russound RNET][Russound] integration ([@laf])
@@ -102,7 +102,6 @@ I would like to do a shoutout to [@fabianhjr]. He has started adding [typing] da
[custom-panels]: /developers/frontend_creating_custom_panels/
[iframe_panel]: /integrations/panel_iframe/
-[custom]: /cookbook/custom_panel_using_react/
[flux]: /integrations/flux_led
[script]: /getting-started/scripts/#delay
[Russound]: /integrations/russound_rnet
@@ -120,7 +119,6 @@ I would like to do a shoutout to [@fabianhjr]. He has started adding [typing] da
[PEP484]: https://www.python.org/dev/peps/pep-0484/
[MPC-HC]: /integrations/mpchc
[Telegram]: /integrations/telegram
-[react-panel]: /cookbook/custom_panel_using_react/
[KNX]: /integrations/climate.knx/
[Nest]: /integrations/nest/#climate
[filters]: /topics/templating/#home-assistant-template-extensions
diff --git a/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown b/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
index 47d40348a43..392a9d5674e 100644
--- a/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
+++ b/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
@@ -106,7 +106,7 @@ homeassistant:
[Fast.com]: /integrations/fastdotcom
[pilight]: /integrations/pilight/
[GPSD]: /integrations/gpsd
-[heat control]: /integrations/thermostat.heat_control/
+[heat control]: /integrations/generic_thermostat
[Proximity]: /integrations/proximity/
[Flux]: /integrations/flux
[Proliphix]: /integrations/proliphix/
diff --git a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
index fb66486a0df..3e99a62ed72 100644
--- a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
+++ b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
@@ -59,7 +59,7 @@ We have some excellent upgrades to the notification system coming to you in 0.27
This release adds support for [HTML5] push notifications on Chrome/Firefox/Opera on both desktop and Android devices. This means that you can send a notification to your phone even when your Home Assistant is not open in your mobile browser. When using Chrome you can even include 2 action buttons so that you can control your Home Assistant from your phone's lock screen, allowing you to do things like sound alarms or unlock your front door, all without leaving the notification. Thanks again to me ([@robbiet480]) and Paulus ([@balloob]) for all the hard work on this!
- 
+ 
#### Notification Groups
@@ -83,7 +83,7 @@ hass --script check_config
This release includes a big push on making sure all platforms contain proper configuration validation. This should help in getting your configuration right. Thanks to [@fabaff], [@pavoni], [@pvizeli], [@nkgilley] for all the hard work on this, you all rock!
- 
+ 
### FFMpeg motion/noise sensing
@@ -268,7 +268,7 @@ Talk to you soon on Discord and in your pull request comments!
[forecast]: /integrations/darksky
[Bluetooth]: /integrations/bluetooth_le_tracker
[Slack]: /integrations/slack
-[template]: /integrations/generic
+[template]: /integrations/generic_ip_camera
[Bug]: /integrations/wink/
[support]: /integrations/homematic/
[node]: /integrations/zwave/
diff --git a/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown b/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
index 97979b9f10c..d6ca4e749ed 100644
--- a/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
+++ b/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
@@ -15,7 +15,7 @@ It's already time for 0.28 thanks to our super short release cycles. Now, it' of
This release brings you a huge improvement of the [automation] and [group] handling. Both can be reloaded without a Home Assistant restart by calling their new reload services. The automations can be controlled directly from the frontend.
- 
+ 
### Raspberry Pi installation guide
@@ -32,7 +32,7 @@ The validation of the configuration is still on-going. Approximately 80 % is don
### All changes
-
+
- Light: Added bitfield to Flux LED since we are supporting effects ([@tchellomello])
- Device tracker: [Owntracks] waypoint import ([@pavoni])
@@ -43,7 +43,7 @@ The validation of the configuration is still on-going. Approximately 80 % is don
- Device tracker: Allow 'None' MAC addresses to be loaded from `known_devices` file ([@kellerza])
- Cover: Bugfixes ([@turbokongen], [@danielperna84])
- Sensor: Support for displaying details about [crypto currencies][Coinmarketcap] ([@fabaff])
-- Device tracker: Support for [automatic] to track your vehicles ([@Teagan42])
+- Device tracker: Support for automatic to track your vehicles ([@Teagan42])
- Devie tracker: Add exclude option to [Nmap] device tracker ([@danieljkemp])
- Device tracker: Improved login errors for Asus device tracker ([@kellerza])
- Sensor: Support for displaying the status of [Xbox] Live accounts ([@mKerix])
@@ -146,7 +146,6 @@ The validation of the configuration is still on-going. Approximately 80 % is don
[mqtt-fan]: /integrations/fan.mqtt/
[Xbox]: /integrations/xbox_live
[Nmap]: /integrations/nmap_tracker
-[automatic]: /integrations/automatic
[Owntracks]: /integrations/owntracks
[OpenweatherMap]: /integrations/openweathermap#sensor
[OctoPrint]: /integrations/octoprint/
diff --git a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
index c7079ba0997..d49233c9e4c 100644
--- a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
+++ b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
@@ -21,7 +21,7 @@ To reduce the run-time of your tests, [@balloob] did a lot of tweaking. For now
All configuration sample entries are now minimized. This should help to avoid problem for starters and newbies as they only get what's needed and not a full sample with all optional entries. If there is an issue with an entry in your `configuration.yaml` file the error message will provide you an URL that point to the documentation.
- 
+ 
As soon as the [Hacktoberfest] started there were a lot of incoming Pull Requests for the documentation. A huge "Thank you" to all participants. Especially, we would like to give a cookie to [@hillaryfraley]. She created around a dozen Pull Requests so far and didn't only fix typos but complete sections. The [Hacktoberfest] is still on-going and we are looking forward to get more Pull Requests.
@@ -31,7 +31,7 @@ As soon as the [Hacktoberfest] started there were a lot of incoming Pull Request
With the [statistics sensor][stats-sensor] we would like to introduce a new sensor that is similar to the [template sensor][template-sensor] or the [trend sensor][trend-sensor]. This sensor is consuming values from another sensor and is doing some statistical analysis of the data. Over a group of samples is the average/mean, the min/max, the total, the standard deviation, and the variance calculated which can be used in your automation rules. If the source is a binary sensor then the state changes are counted.
-
+
As the results are processed on-the-fly you still need to use the data from your database for an in-depth analysis of your stored information. Check the latest [notebook] for doing statistics with your Home Assistant database.
diff --git a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
index 03fba69d3c7..774ab908024 100644
--- a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
+++ b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
@@ -13,7 +13,7 @@ Here we go... 0.34. Let's call it the "Santa Claus" release. Rudolph was faster
### GPSLogger
-The work of [@dainok] let's you use your Android device, with the Geolocation feature enabled, to track itself using GPS or WiFi networks with the [GPSLogger](https://play.google.com/store/apps/details?id=com.mendhak.gpslogger) app. GPSLogger can use multiple sources: the passive one just get the latest Android known location, without activating GPS sensors or scanning for WiFi networks.
+The work of [@dainok] let's you use your Android device, with the Geolocation feature enabled, to track itself using GPS or WiFi networks with the [GPSLogger](https://github.com/mendhak/gpslogger/releases) app. GPSLogger can use multiple sources: the passive one just get the latest Android known location, without activating GPS sensors or scanning for WiFi networks.
### Remote component
diff --git a/source/_posts/2017-01-18-numbers.markdown b/source/_posts/2017-01-18-numbers.markdown
index 7285ce591fd..ebf6f86ed99 100644
--- a/source/_posts/2017-01-18-numbers.markdown
+++ b/source/_posts/2017-01-18-numbers.markdown
@@ -10,7 +10,7 @@ categories: Community
It's week 3 of 2017 and great things did already happen. This is just a little recap.
-- In the [OSS Metrics leaderboard](https://ossmetrics.com/leaderboard) we are on place 30. Within three months we moved from our starting place which was 66 in September 2016 up to the current one.
+- In the OSS Metrics leaderboard we are on place 30. Within three months we moved from our starting place which was 66 in September 2016 up to the current one.
- We were listed on [Github Trending](https://github.com/trending/python). Also, was [@balloob](https://github.com/balloob) mentioned as trending developer.
- [@balloob](https://github.com/balloob)'s talk at the OpenIoT Summit 2016 was rated as one of the [Top 5 videos](https://www.linuxfoundation.org/blog/2017/01/top-5-videos-from-embedded-linux-conference-and-openiot-summit-2016/) of the conference.
- We now ship over [500](/integrations/#all) components and platforms.
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 b2ecfa575e7..cc46f9d26f1 100644
--- a/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
+++ b/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
@@ -20,7 +20,7 @@ Another Saturday, another release!
The frontend has been completely been rewritten, optimizing for speed and lost connection recovery. Even on the slowest phones it should fly now. The frontend also now uses the new [WebSockets API][websocket-api] instead of the [EventStream API][event-stream-api].
### Custom state card UI
-A nice new feature is the possibility to create [custom state cards][custom-ui] in the frontend. Go ahead and write your own state card for [lights][light], sensors, locks, etc.
+A nice new feature is the possibility to create [custom state cards][custom-ui-cards] in the frontend. Go ahead and write your own state card for lights, sensors, locks, etc.
### MQTT discovery
MQTT now has [discovery][mqtt-discovery] support which is different than our [`discovery`][discovery] component. Similar to the HTTP sensor and HTTP binary sensor, MQTT discovery removes the need for configuration by allowing devices to make their presence known to Home Assistant.
@@ -197,14 +197,13 @@ Experiencing issues introduced by this release? Please report them in our [issue
[apiai]: /integrations/dialogflow
[apple-tv]: /integrations/apple_tv
[arwn]: /integrations/arwn
-[custom-ui]: /developers/frontend_creating_custom_ui/
+[custom-ui-cards]: /developers/frontend_creating_custom_ui
[discovery]: /integrations/discovery/
[face-detect]: /integrations/microsoft_face_detect
[ffmpeg-bin]: /integrations/ffmpeg_motion
[ffmpeg]: /integrations/ffmpeg/
[filters]: /topics/templating/#home-assistant-template-extensions
[hue]: /integrations/hue
-[light]: /cookbook/custom_ui_by_andrey-git
[mailgun]: /integrations/mailgun
[media-player]: /integrations/media_player/
[moon]: /integrations/moon
diff --git a/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown b/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
index 415250c56bf..5ca55b00049 100644
--- a/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
+++ b/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
@@ -16,7 +16,7 @@ Welcome to another great release of Home Assistant! While some of contributors a
First thing for this release is a feature that has been requested a lot: an automation editor! It's still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you're all good to go. Otherwise check [these instructions](/docs/automation/editor/) to get your automations ready for editing in the UI.
- 
+ 
Check this [video](https://youtu.be/0j_hWdCTip4) by [Ben](https://twitter.com/BRUHautomation) from [BRUHautomation](http://www.bruhautomation.com/) to see the new release in action.
@@ -30,7 +30,7 @@ As the editor is experimental, there are some limitations. These include that Ch
On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to [@turbokongen]! You will now be able to change config parameters and manage your devices.
- 
+ 
Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
@@ -45,7 +45,7 @@ Next to that [@armills] has lead the charge and managed to get full test coverag
This release also contains two integrations which could help you to make non-smart devices a little smarter. The [`file` sensor][sensor.file docs] and the [`seven_segments` OCR image processing platform][image_processing.seven_segments docs]. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
- 
+ 
And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!
@@ -72,7 +72,7 @@ If you are using our [experimental Hass.io image][hass.io], we made a breaking c
## Release 0.45.1 - May 22
-- Fix telegram chats ([@azogue] - [#7689]) ([notify.telegram docs]) ([telegram_bot.__init__ docs])
+- Fix telegram chats ([@azogue] - [#7689]) ([notify.telegram docs]) ([telegram_bot docs])
- Fix playback control of web streams ([@cgtobi] - [#7683]) ([media_player.volumio docs])
- device_tracker.ubus: Handle empty results ([@tobygray] - [#7673]) ([device_tracker.ubus docs])
- Allow fetching hass.io panel without auth ([@balloob] - [#7714]) ([hassio docs])
@@ -122,7 +122,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- new source only forces "play" if the current state is "playing" ([@abmantis] - [#7506]) ([media_player.spotify docs])
- Correct retrieval of spotify shuffle state ([@andersonshatch] - [#7505]) ([media_player.spotify docs])
- Fix sonos sleep timer ([@frog32] - [#7503]) ([media_player.sonos docs])
-- Add support for automation config panel ([@balloob] - [#7509]) ([automation.__init__ docs]) ([config.automation docs]) ([config.__init__ docs]) (new-platform)
+- Add support for automation config panel ([@balloob] - [#7509]) ([automation docs]) ([config.automation docs]) ([config docs]) (new-platform)
- Zwave panel api ([@turbokongen] - [#7456]) ([zwave docs]) ([zwave.api docs]) (new-platform)
- Update docker dev environment to python3.6 ([@frog32] - [#7520])
- Switch basicmodem and python-roku to pypi ([@andrey-git] - [#7514]) ([media_player.roku docs]) ([sensor.modem_callerid docs])
@@ -174,24 +174,24 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Fix handling of single user ([@mezz64] - [#7587]) ([eight_sleep docs])
- File sensor ([@fabaff] - [#7569]) ([sensor.file docs]) (new-platform)
- Make miflora monitored_conditions parameter optional ([@frog32] - [#7598]) ([sensor.miflora docs])
-- Force automation ids to always be a string ([@balloob] - [#7612]) ([automation.__init__ docs])
+- Force automation ids to always be a string ([@balloob] - [#7612]) ([automation docs])
- Update Docker base image to python 3.6 ([@pschmitt] - [#7613])
-- Add Content-type: image/jpeg for camera proxy ([@olekenneth] - [#7581]) ([camera.__init__ docs])
+- Add Content-type: image/jpeg for camera proxy ([@olekenneth] - [#7581]) ([camera docs])
- Fix typo and update style to match the other platforms ([@fabaff] - [#7621]) ([image_processing.opencv docs])
- Bump pyvera - fixes issue with % in brightness levels. ([@pavoni] - [#7622]) ([vera docs])
-- Add kelvin/brightness_pct alternatives to light.turn_on ([@amelchio] - [#7596]) ([light.lifx docs]) ([light.__init__ docs])
+- Add kelvin/brightness_pct alternatives to light.turn_on ([@amelchio] - [#7596]) ([light.lifx docs]) ([light docs])
- Add support for disabling tradfri groups ([@cnrd] - [#7593]) ([tradfri docs]) ([light.tradfri docs])
- Update docstrings and comments ([@fabaff] - [#7626]) ([image_processing.openalpr_cloud docs]) ([image_processing.openalpr_local docs])
- Upgrade Sphinx to 1.6.1 ([@fabaff] - [#7624])
-- Update docstrings ([@fabaff] - [#7630]) ([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]) ([image_processing.opencv docs])
+- Update docstrings ([@fabaff] - [#7630]) ([image_processing 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]) ([image_processing.opencv docs])
- Kodi specific service to call Kodi API methods ([@azogue] - [#7603]) ([media_player.kodi docs])
- Updated limitlessled requirement to v1.0.8 ([@corneyl] - [#7629])
- Osram lightify Removed wrong assignment ([@commento] - [#7615]) ([light.osramlightify docs])
- Updated dependency ([@danielperna84] - [#7638]) ([homematic docs])
-- Seven segments OCR image processing ([@fabaff] - [#7632]) ([image_processing.seven_segments docs]) ([image_processing.__init__ docs]) (new-platform)
+- Seven segments OCR image processing ([@fabaff] - [#7632]) ([image_processing.seven_segments docs]) ([image_processing docs]) (new-platform)
- Abort tests when instances leaked ([@balloob] - [#7623])
-- Coerce color_temp to int even when passed in as kelvin ([@amelchio] - [#7640]) ([light.__init__ docs])
-- Fix automation failing to setup if no automations specified ([@balloob] - [#7647]) ([automation.__init__ docs])
+- Coerce color_temp to int even when passed in as kelvin ([@amelchio] - [#7640]) ([light docs])
+- Fix automation failing to setup if no automations specified ([@balloob] - [#7647]) ([automation docs])
[#6844]: https://github.com/home-assistant/home-assistant/pull/6844
[#7062]: https://github.com/home-assistant/home-assistant/pull/7062
@@ -345,11 +345,11 @@ Experiencing issues introduced by this release? Please report them in our [issue
[binary_sensor.raspihats docs]: /integrations/raspihats#binary-sensor
[binary_sensor.rpi_pfio docs]: /integrations/rpi_pfio#binary-sensor
[blink docs]: /integrations/blink/
-[camera.__init__ docs]: /integrations/camera.__init__/
+[camera docs]: /integrations/camera
[camera.uvc docs]: /integrations/uvc
[camera.zoneminder docs]: /integrations/zoneminder#camera
[climate.sensibo docs]: /integrations/sensibo
-[config.__init__ docs]: /integrations/config.__init__/
+[config docs]: /integrations/config
[configurator docs]: /integrations/configurator/
[cover.lutron_caseta docs]: /integrations/lutron_caseta/
[datadog docs]: /integrations/datadog/
@@ -357,8 +357,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[dweet docs]: /integrations/dweet/
[eight_sleep docs]: /integrations/eight_sleep/
[homematic docs]: /integrations/homematic/
-[image_processing.__init__ docs]: /integrations/image_processing.__init__/
-[image_processing.demo docs]: /integrations/image_processing.demo/
+[image_processing docs]: /integrations/image_processing
[image_processing.dlib_face_detect docs]: /integrations/dlib_face_detect
[image_processing.dlib_face_identify docs]: /integrations/dlib_face_identify
[image_processing.microsoft_face_detect docs]: /integrations/microsoft_face_detect
@@ -368,7 +367,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[image_processing.opencv docs]: /integrations/opencv
[image_processing.seven_segments docs]: /integrations/seven_segments
[kira docs]: /integrations/kira/
-[light.__init__ docs]: /integrations/light.__init__/
+[light docs]: /integrations/light
[light.blinksticklight docs]: /integrations/blinksticklight
[light.enocean docs]: /integrations/enocean#light
[light.flux_led docs]: /integrations/flux_led
@@ -433,5 +432,5 @@ Experiencing issues introduced by this release? Please report them in our [issue
[device_tracker.ubus docs]: /integrations/ubus
[hassio docs]: /integrations/hassio/
[media_player.volumio docs]: /integrations/volumio
-[telegram_bot.__init__ docs]: /integrations/telegram_bot/
+[telegram_bot docs]: /integrations/telegram_bot/
[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 2f402e7a76b..995b853d442 100644
--- a/source/_posts/2017-06-04-release-46.markdown
+++ b/source/_posts/2017-06-04-release-46.markdown
@@ -27,7 +27,7 @@ It's time for 0.46! This release does not have too many new integrations, instea
- Fix typos in Wunderground component (Percipitation -> Precipitation) ([@mje-nz] - [#7901]) ([sensor.wunderground docs])
- Mqtt cover: Making command topic optional and add ability to set up/down position including ability to template the value ([@cribbstechnologies] - [#7841]) ([cover.mqtt docs])
- Media Player - OpenHome: Fixed metadata issue ([@bazwilliams] - [#7932]) ([media_player.openhome docs])
-- Sensor - MetOffice: Fix last updated date ([@cyberjacob] - [#7965]) ([sensor.metoffice docs])
+- Sensor - MetOffice: Fix last updated date ([@cyberjacob] - [#7965]) ([metoffice docs])
- Prevent Roku doing I/O in event loop ([@balloob] - [#7969]) ([media_player.roku docs])
## Breaking changes
@@ -345,6 +345,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[media_player.sonos docs]: /integrations/sonos
[media_player.spotify docs]: /integrations/spotify
[media_player.volumio docs]: /integrations/volumio
+[metoffice docs]: /integrations/metoffice/
[modbus docs]: /integrations/modbus/
[mqtt.discovery docs]: /docs/mqtt/discovery/
[notify.ios docs]: /docs/ecosystem/ios/notifications/basic/
@@ -388,7 +389,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@cyberjacob]: https://github.com/cyberjacob
[@mje-nz]: https://github.com/mje-nz
[cover.mqtt docs]: /integrations/cover.mqtt/
-[sensor.metoffice docs]: /integrations/sensor.metoffice/
[sensor.wunderground docs]: /integrations/wunderground
[media_player.roku docs]: /integrations/roku#media-player
[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 49406fc741f..dca11468bea 100644
--- a/source/_posts/2017-06-17-release-47.markdown
+++ b/source/_posts/2017-06-17-release-47.markdown
@@ -216,7 +216,7 @@ automation:
- Add configuration check and use default var names ([@fabaff] - [#7963]) ([lutron docs]) ([light.lutron docs]) (breaking change)
- lock.sesame: Update pysesame, add state attributes ([@trisk] - [#7953]) ([lock.sesame docs])
- Fixed metadata issue ([@bazwilliams] - [#7932]) ([media_player.openhome docs])
-- Create metoffice.py ([@cyberjacob] - [#7965]) ([sensor.metoffice docs])
+- Create metoffice.py ([@cyberjacob] - [#7965]) ([metoffice docs])
- Prevent Roku doing I/O in event loop ([@balloob] - [#7969]) ([media_player.roku docs])
- Fix platforms being able to block startup ([@balloob] - [#7970])
- New component: Python Script ([@balloob] - [#7950]) ([python_script docs]) (new-platform)
@@ -495,6 +495,7 @@ automation:
[media_player.sonos docs]: /integrations/sonos
[media_player.spotify docs]: /integrations/spotify
[media_player.squeezebox docs]: /integrations/squeezebox
+[metoffice docs]: /integrations/metoffice/
[mqtt.__init__ docs]: /integrations/mqtt.__init__/
[nest docs]: /integrations/nest/
[netatmo docs]: /integrations/netatmo/
@@ -527,7 +528,6 @@ automation:
[sensor.homematic docs]: /integrations/homematic
[sensor.imap_email_content docs]: /integrations/imap_email_content/
[sensor.juicenet docs]: /integrations/juicenet#sensor
-[sensor.metoffice docs]: /integrations/sensor.metoffice/
[sensor.mold_indicator docs]: /integrations/mold_indicator
[sensor.netatmo docs]: /integrations/netatmo#sensor
[sensor.openevse docs]: /integrations/openevse
diff --git a/source/_posts/2017-07-02-release-48.markdown b/source/_posts/2017-07-02-release-48.markdown
index 91a1dee7bc7..85070ec8ead 100644
--- a/source/_posts/2017-07-02-release-48.markdown
+++ b/source/_posts/2017-07-02-release-48.markdown
@@ -426,7 +426,7 @@ light:
[binary_sensor.arest docs]: /integrations/arest#binary-sensor
[binary_sensor.digital_ocean docs]: /integrations/digital_ocean#binary-sensor
[binary_sensor.modbus docs]: /integrations/binary_sensor.modbus/
-[binary_sensor.rfxtrx docs]: /integrations/binary_sensor.rfxtrx/
+[binary_sensor.rfxtrx docs]: /integrations/rfxtrx#binary-sensors
[binary_sensor.verisure docs]: /integrations/verisure
[calendar.google docs]: /integrations/calendar.google/
[camera.arlo docs]: /integrations/arlo#camera
diff --git a/source/_posts/2017-07-16-release-49.markdown b/source/_posts/2017-07-16-release-49.markdown
index 00722f59865..cd459ab8e1c 100644
--- a/source/_posts/2017-07-16-release-49.markdown
+++ b/source/_posts/2017-07-16-release-49.markdown
@@ -486,7 +486,7 @@ amcrest:
[@clkao]: https://github.com/clkao
[@maikelwever]: https://github.com/maikelwever
[@ypollart]: https://github.com/ypollart
-[binary_sensor.rfxtrx docs]: /integrations/binary_sensor.rfxtrx/
+[binary_sensor.rfxtrx docs]: /integrations/rfxtrx#binary-sensors
[telegram_bot docs]: /integrations/telegram_bot/
[#8545]: https://github.com/home-assistant/home-assistant/pull/8545
[#8571]: https://github.com/home-assistant/home-assistant/pull/8571
diff --git a/source/_posts/2017-08-26-release-0-52.markdown b/source/_posts/2017-08-26-release-0-52.markdown
index 5b93e7207b9..2ed7e471711 100644
--- a/source/_posts/2017-08-26-release-0-52.markdown
+++ b/source/_posts/2017-08-26-release-0-52.markdown
@@ -39,7 +39,7 @@ script: !include scripts.yaml
- Add version sensor ([@fabaff] - [#8912]) ([sensor.version docs]) (new-platform)
- Nello.io lock support ([@pschmitt] - [#8957]) ([lock.nello docs]) (new-platform)
-- Add HipChat notify service. ([@BioSehnsucht] - [#8918]) ([notify.hipchat docs]) (new-platform)
+- Add HipChat notify service. ([@BioSehnsucht] - [#8918]) (new-platform)
- Refactor USPS into component with Sensors+Camera ([@mezz64] - [#8679]) (breaking change) (new-platform)
- Adds London_air component ([@robmarkcole] - [#9020]) ([sensor.london_air docs]) (new-platform)
- Add Abode home security component ([@arsaboo] - [#9030]) ([abode docs]) ([alarm_control_panel.abode docs]) ([binary_sensor.abode docs]) (new-platform)
@@ -117,7 +117,7 @@ usps:
- Pushbullet, fix multiple messages sent when url param is set ([@karlkar] - [#9006]) ([notify.pushbullet docs])
- Update to pyenvisalink 2.2, and remove range validation on zonedump i… ([@Cinntax] - [#8981]) ([envisalink docs])
- Fix #9010 - Swiss Public Transportation shows departure time in the past ([@hertg] - [#9011]) ([sensor.swiss_public_transport docs])
-- Add HipChat notify service. ([@BioSehnsucht] - [#8918]) ([notify.hipchat docs]) (new-platform)
+- Add HipChat notify service. ([@BioSehnsucht] - [#8918]) (new-platform)
- Update onkyo-eiscp to 1.2.3 ([@danieljkemp] - [#9019]) ([media_player.onkyo docs])
- Check if album image(s) exist in spotify ([@Tommatheussen] - [#9024]) ([media_player.spotify docs])
- Update ffmpeg to 1.7 to fix severals problems ([@pvizeli] - [#9029])
@@ -156,7 +156,7 @@ usps:
- Remove dash ([@fabaff] - [#9089])
- Upgrade credstash to 1.13.3 ([@fabaff] - [#9088])
- 9043 Fixed error while running dev docker ([@MungoRae] - [#9044])
-- Don't redefine consts ([@fabaff] - [#9086]) ([notify.hipchat docs])
+- Don't redefine consts ([@fabaff] - [#9086])
- Fix octoprint errors when printer is off/disconnected ([@w1ll1am23] - [#8988]) ([octoprint docs]) ([sensor.octoprint docs])
- Pilight switch: restore last state after restart ([@janLo] - [#8580]) ([switch.pilight docs])
- Fix netdata system_load and add disk_free. ([@michaelarnauts] - [#9091]) ([sensor.netdata docs])
@@ -341,7 +341,6 @@ usps:
[media_player.webostv docs]: /integrations/webostv#media-player
[mysensors docs]: /integrations/mysensors/
[notify.discord docs]: /integrations/discord
-[notify.hipchat docs]: /integrations/hipchat
[notify.mysensors docs]: /integrations/notify.mysensors/
[notify.prowl docs]: /integrations/prowl
[notify.pushbullet docs]: /integrations/pushbullet
diff --git a/source/_posts/2017-09-09-release-53.markdown b/source/_posts/2017-09-09-release-53.markdown
index 00b001a17c5..3ac467737d9 100644
--- a/source/_posts/2017-09-09-release-53.markdown
+++ b/source/_posts/2017-09-09-release-53.markdown
@@ -372,7 +372,7 @@ frontend:
[cover.abode docs]: /integrations/abode
[cover.homematic docs]: /integrations/homematic
[cover.lutron_caseta docs]: /integrations/lutron_caseta/
-[cover.rfxtrx docs]: /integrations/cover.rfxtrx/
+[cover.rfxtrx docs]: /integrations/rfxtrx#covers
[cover.xiaomi docs]: /integrations/cover.xiaomi_aqara/
[cover.knx docs]: /integrations/cover.knx/
[device_tracker.geofency docs]: /integrations/geofency
@@ -389,7 +389,7 @@ frontend:
[light.lutron_caseta docs]: /integrations/lutron_caseta/
[light.mqtt docs]: /integrations/light.mqtt/
[light.xiaomi_philipslight docs]: /integrations/light.xiaomi_miio/
-[light.rfxtrx docs]: /integrations/light.rfxtrx/
+[light.rfxtrx docs]: /integrations/rfxtrx#lights
[light.tradfri docs]: /integrations/tradfri
[light.knx docs]: /integrations/light.knx/
[light.zha docs]: /integrations/zha
@@ -435,7 +435,7 @@ frontend:
[switch.homematic docs]: /integrations/homematic
[switch.lutron_caseta docs]: /integrations/lutron_caseta/
[switch.rest docs]: /integrations/switch.rest/
-[switch.rfxtrx docs]: /integrations/switch.rfxtrx/
+[switch.rfxtrx docs]: /integrations/rfxtrx#switches
[switch.knx docs]: /integrations/switch.knx/
[telegram_bot docs]: /integrations/telegram_bot/
[tesla docs]: /integrations/tesla/
diff --git a/source/_posts/2017-10-21-release-56.markdown b/source/_posts/2017-10-21-release-56.markdown
index b25ba71446f..39ae7454336 100644
--- a/source/_posts/2017-10-21-release-56.markdown
+++ b/source/_posts/2017-10-21-release-56.markdown
@@ -147,7 +147,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Update CODEOWNERS */axis.py ([@Kane610] - [#9823])
- fix climate services (missing indentation, wrongly formatted example) ([@rytilahti] - [#9805])
- Run initial generation for development mode ([@armills] - [#9826])
-- Add service descriptions ([@cgarwood] - [#9806]) ([__init__ docs])
+- Add service descriptions ([@cgarwood] - [#9806]) ([homeassistant docs])
- Bugfix: Include MQTT schema ([@tinloaf] - [#9802]) ([climate.mqtt docs])
- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841])
@@ -414,7 +414,6 @@ 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]: /integrations/__init__/
[abode docs]: /integrations/abode/
[alarm_control_panel.arlo docs]: /integrations/arlo
[alarm_control_panel.egardia docs]: /integrations/egardia
@@ -455,6 +454,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[ffmpeg docs]: /integrations/ffmpeg/
[google_assistant docs]: /integrations/google_assistant/
[hassio docs]: /integrations/hassio/
+[homeassistant docs]: /integrations/homeassistant
[homematic docs]: /integrations/homematic/
[http docs]: /integrations/http/
[knx docs]: /integrations/knx/
diff --git a/source/_posts/2017-11-04-release-57.markdown b/source/_posts/2017-11-04-release-57.markdown
index 0a33bc952ba..e8f786460d8 100644
--- a/source/_posts/2017-11-04-release-57.markdown
+++ b/source/_posts/2017-11-04-release-57.markdown
@@ -253,7 +253,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Avoid Sonos error during startup ([@amelchio] - [#10146]) ([media_player.sonos docs])
- Update netdisco to 1.2.3 ([@balloob] - [#10266])
- Extracted json saving and loading ([@molobrakos] - [#10216]) ([media_player.plex docs])
-- Change introduction card to use persistent notification ([@balloob] - [#10265]) ([introduction docs])
+- Change introduction card to use persistent notification ([@balloob] - [#10265])
- Add unit test for wake on lan component. ([@cgtobi] - [#10262])
- Add link to docs ([@fabaff] - [#10272])
- Add xy support to Alexa HomeAPI v3 ([@pvizeli] - [#10268])
@@ -530,7 +530,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[binary_sensor.gc100 docs]: /integrations/gc100#binary-sensor
[binary_sensor.linode docs]: /integrations/linode#binary-sensor
[binary_sensor.random docs]: /integrations/random#binary-sensor
-[binary_sensor.rfxtrx docs]: /integrations/binary_sensor.rfxtrx/
+[binary_sensor.rfxtrx docs]: /integrations/rfxtrx#binary-sensors
[binary_sensor.ring docs]: /integrations/ring#binary-sensor
[binary_sensor.tellduslive docs]: /integrations/tellduslive
[binary_sensor.trend docs]: /integrations/trend
@@ -564,7 +564,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[image_processing.openalpr_local docs]: /integrations/openalpr_local/
[input_number docs]: /integrations/input_number/
[input_text docs]: /integrations/input_text/
-[introduction docs]: /integrations/introduction/
[light.hue docs]: /integrations/hue
[light.hyperion docs]: /integrations/hyperion
[light.mqtt docs]: /integrations/light.mqtt/
diff --git a/source/_posts/2017-11-12-tor.markdown b/source/_posts/2017-11-12-tor.markdown
index 4ce34c7339f..e3e980bbb8b 100644
--- a/source/_posts/2017-11-12-tor.markdown
+++ b/source/_posts/2017-11-12-tor.markdown
@@ -88,7 +88,7 @@ Simply download and install the [Tor Browser](https://www.torproject.org/project
Some other clients:
- [Orbot](https://guardianproject.info/apps/orbot/) for Android
-- ~~[Orfox](https://play.google.com/store/apps/details?id=info.guardianproject.orfox&hl=nl) for Android~~ Orfox for Android has been deprecated. Please use [Tor Browser for Android](https://www.torproject.org/download/#android). More information about the deprecation [here](https://trac.torproject.org/projects/tor/ticket/29955).
+- Orfox for Android has been deprecated. Please use [Tor Browser for Android](https://www.torproject.org/download/#android). More information about the deprecation [here](https://trac.torproject.org/projects/tor/ticket/29955).
- [Onion Browser](https://mike.tig.as/onionbrowser/) for iOS
## Cranking up security
diff --git a/source/_posts/2017-12-17-release-60.markdown b/source/_posts/2017-12-17-release-60.markdown
index 14e655aabfe..a3f929436a4 100644
--- a/source/_posts/2017-12-17-release-60.markdown
+++ b/source/_posts/2017-12-17-release-60.markdown
@@ -141,7 +141,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Report availability for TP-Link smart bulbs ([@DanNixon] - [#10976]) ([light.tplink docs])
- Fix incorrect comment. ([@emosenkis] - [#11111])
- Update Warrant ([@balloob] - [#11101]) ([cloud docs])
-- Fixed typo in automation.py ([@ryanm101] - [#11116]) ([config.automation docs])
+- Fixed typo in automation.py ([@ryanm101] - [#11116]) ([config docs])
- Add media position properties ([@pschmitt] - [#10076])
- update pyripple ([@nkgilley] - [#11122]) ([sensor.ripple docs])
- Skip HASS emulated Hue bridges from detection. ([@andreacampi] - [#11128]) ([hue docs])
@@ -316,7 +316,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[climate.tado docs]: /integrations/tado
[cloud docs]: /integrations/cloud/
[cloud.const docs]: /integrations/cloud/
-[config.automation docs]: /integrations/config.automation/
+[config docs]: /integrations/config
[cover.tellstick docs]: /integrations/tellstick#cover
[device_tracker docs]: /integrations/device_tracker/
[device_tracker.meraki docs]: /integrations/meraki
diff --git a/source/_posts/2018-01-14-release-61.markdown b/source/_posts/2018-01-14-release-61.markdown
index 426ee0dca16..5a5ccf108d6 100644
--- a/source/_posts/2018-01-14-release-61.markdown
+++ b/source/_posts/2018-01-14-release-61.markdown
@@ -272,7 +272,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
- Add Touchline climate platform ([@abondoe] - [#10547]) ([climate.touchline docs]) (new-platform)
- Upgrade pysnmp to 4.4.4 ([@fabaff] - [#11485]) ([device_tracker.snmp docs]) ([sensor.snmp docs]) ([switch.snmp docs])
- Add new iGlo component ([@jesserockz] - [#11171]) ([light.iglo docs]) (new-platform)
-- Add missing configuration variables ([@fabaff] - [#11390]) ([sensor.metoffice docs])
+- Add missing configuration variables ([@fabaff] - [#11390]) ([metoffice docs])
- Clean up Alexa.intent and DialogFlow.intent ([@balloob] - [#11492]) ([alexa.intent docs])
- Fix time functions would throw errors in python scripts ([@tomwaters] - [#11414]) ([python_script docs])
- Upgrade pywebpush to 1.5.0 ([@Chris-V] - [#11497]) ([notify.html5 docs])
@@ -329,7 +329,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
- add velux roller shutter to tahoma ([@thijsdejong] - [#11586]) ([tahoma docs])
- Added support for enable/disable motion detection ([@abjorshammar] - [#11583]) ([camera.uvc docs])
- Avoid returning empty media_image_url string ([@JackWindows] - [#11557]) ([media_player.cast docs])
-- Core support for hass.io calls & Bugfix check_config ([@pvizeli] - [#11571]) ([__init__ docs]) ([hassio docs]) ([updater docs])
+- Core support for hass.io calls & Bugfix check_config ([@pvizeli] - [#11571]) ([homeassistant docs]) ([hassio docs]) ([updater docs])
- Fix Tahoma stop command for 2 types of shutters ([@thijsdejong] - [#11588]) ([cover.tahoma docs])
- Pushbullet email support (fix) ([@tschmidty69] - [#11590]) ([notify.pushbullet docs])
- Fix state for trigger with forced updates ([@armills] - [#11595]) ([automation.state docs])
@@ -610,7 +610,6 @@ 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]: /integrations/__init__/
[alarm_control_panel.alarmdecoder docs]: /integrations/alarmdecoder#alarm-control-panel
[alarm_control_panel.concord232 docs]: /integrations/concord232#alarm-control-panel
[alarm_control_panel.egardia docs]: /integrations/egardia
@@ -673,6 +672,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
[google_assistant.http docs]: /integrations/google_assistant/
[google_assistant.smart_home docs]: /integrations/google_assistant
[group docs]: /integrations/group/
+[homeassistant docs]: /integrations/homeassistant
[hassio docs]: /integrations/hassio/
[history docs]: /integrations/history/
[hive docs]: /integrations/hive/
@@ -707,6 +707,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
[media_player.plex docs]: /integrations/plex#media-player
[media_player.squeezebox docs]: /integrations/squeezebox
[media_player.yamaha docs]: /integrations/yamaha
+[metoffice docs]: /integrations/metoffice/
[modbus docs]: /integrations/modbus/
[notify.html5 docs]: /integrations/html5
[notify.pushbullet docs]: /integrations/pushbullet
@@ -730,7 +731,6 @@ Note however, that this feature was replaced by a new ignore_string config optio
[sensor.isy994 docs]: /integrations/isy994#sensors
[sensor.knx docs]: /integrations/sensor.knx/
[sensor.luftdaten docs]: /integrations/luftdaten#sensor
-[sensor.metoffice docs]: /integrations/sensor.metoffice/
[sensor.miflora docs]: /integrations/miflora
[sensor.mqtt docs]: /integrations/sensor.mqtt/
[sensor.openweathermap docs]: /integrations/openweathermap#sensor
@@ -781,7 +781,7 @@ 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]: /integrations/binary_sensor.rfxtrx/
+[binary_sensor.rfxtrx docs]: /integrations/rfxtrx#binary-sensors
[calendar.todoist docs]: /integrations/todoist
[history docs]: /integrations/history/
[light.zha docs]: /integrations/zha
diff --git a/source/_posts/2018-01-27-release-62.markdown b/source/_posts/2018-01-27-release-62.markdown
index f6a8d1989ef..198847f71ee 100644
--- a/source/_posts/2018-01-27-release-62.markdown
+++ b/source/_posts/2018-01-27-release-62.markdown
@@ -100,7 +100,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Round off exchange rate ([@arsaboo] - [#11765]) ([sensor.alpha_vantage docs])
- Update icon (fixes #11744) ([@fabaff] - [#11758]) ([sensor.fixer docs])
- Use localized forecast for openweathermap ([@brainexe] - [#11770]) ([sensor.openweathermap docs])
-- Unit should be mph as that is what the metoffices datapoint API returns ([@ioangogo] - [#11760]) ([sensor.metoffice docs])
+- Unit should be mph as that is what the metoffices datapoint API returns ([@ioangogo] - [#11760]) ([metoffice docs])
- Owntracks: Use bluetooth_le as source_type if beacon was used for location change. ([@cnrd] - [#11615]) ([device_tracker.owntracks docs])
- Add a 'last' mode and attribute to min_max sensor ([@markferry] - [#11037]) ([sensor.min_max docs])
- Update header and make it less verbose ([@fabaff] - [#11774]) ([asterisk_mbox docs])
@@ -389,7 +389,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[binary_sensor.hive docs]: /integrations/hive#binary-sensor
[binary_sensor.ihc docs]: /integrations/ihc#binary-sensor
[binary_sensor.maxcube docs]: /integrations/maxcube
-[binary_sensor.rfxtrx docs]: /integrations/binary_sensor.rfxtrx/
+[binary_sensor.rfxtrx docs]: /integrations/rfxtrx#binary-sensors
[binary_sensor.wink docs]: /integrations/wink#binary-sensor
[binary_sensor.workday docs]: /integrations/workday
[binary_sensor.xiaomi_aqara docs]: /integrations/binary_sensor.xiaomi_aqara/
@@ -442,6 +442,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[media_player.samsungtv docs]: /integrations/samsungtv
[media_player.sonos docs]: /integrations/sonos
[media_player.yamaha docs]: /integrations/yamaha
+[metoffice docs]: /integrations/metoffice/
[notify.clicksend docs]: /integrations/clicksend
[notify.prowl docs]: /integrations/prowl
[plant docs]: /integrations/plant/
@@ -456,7 +457,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.hive docs]: /integrations/hive#sensor
[sensor.ihc docs]: /integrations/ihc#sensor
[sensor.iota docs]: /integrations/iota#sensor
-[sensor.metoffice docs]: /integrations/sensor.metoffice/
[sensor.miflora docs]: /integrations/miflora
[sensor.min_max docs]: /integrations/min_max
[sensor.mold_indicator docs]: /integrations/mold_indicator
diff --git a/source/_posts/2018-02-26-release-64.markdown b/source/_posts/2018-02-26-release-64.markdown
index 055e991ecaa..1d5765bf981 100644
--- a/source/_posts/2018-02-26-release-64.markdown
+++ b/source/_posts/2018-02-26-release-64.markdown
@@ -557,7 +557,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.folder docs]: /integrations/folder
[sensor.knx docs]: /integrations/sensor.knx/
[sensor.pollen docs]: /integrations/iqvia
-[sensor.rfxtrx docs]: /integrations/sensor.rfxtrx/
+[sensor.rfxtrx docs]: /integrations/rfxtrx#sensors
[sensor.sabnzbd docs]: /integrations/sabnzbd
[sensor.sma docs]: /integrations/sma#sensors
[sensor.smappee docs]: /integrations/sma#sensorsppee/
@@ -634,7 +634,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@happyleavesaoc]: https://github.com/happyleavesaoc
[@ryanm101]: https://github.com/ryanm101
[@uchagani]: https://github.com/uchagani
-[binary_sensor.rfxtrx docs]: /integrations/binary_sensor.rfxtrx/
+[binary_sensor.rfxtrx docs]: /integrations/rfxtrx#binary-sensors
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
[logbook docs]: /integrations/logbook/
[media_player.plex docs]: /integrations/plex#media-player
diff --git a/source/_posts/2018-03-09-release-65.markdown b/source/_posts/2018-03-09-release-65.markdown
index 7288bd091b7..31420d29391 100644
--- a/source/_posts/2018-03-09-release-65.markdown
+++ b/source/_posts/2018-03-09-release-65.markdown
@@ -165,7 +165,7 @@ intent_script:
- Tado: don't reference unset hass var ([@balloob] - [#13237]) ([device_tracker docs])
- Fix Sonos join/unjoin in scripts ([@amelchio] - [#13248]) ([media_player.sonos docs])
- Fix Sonos radio stations with ampersand ([@amelchio] - [#13293]) ([media_player.sonos docs])
-- Do not include unavailable entities in Google Assistant SYNC ([@balloob] - [#13358]) ([google_assistant docs]) ([light.demo docs])
+- Do not include unavailable entities in Google Assistant SYNC ([@balloob] - [#13358]) ([google_assistant docs]) ([light docs])
## If you need help...
@@ -584,8 +584,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[insteon_plm docs]: /integrations/insteon/
[knx docs]: /integrations/knx/
[light docs]: /integrations/light/
-[light.demo docs]: /integrations/light.demo/
-[light.group docs]: /integrations/light.group/
[light.group docs]: /integrations/light.group/
[light.hue docs]: /integrations/hue
[light.hyperion docs]: /integrations/hyperion
@@ -749,5 +747,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
[camera.proxy docs]: /integrations/proxy
[device_tracker docs]: /integrations/device_tracker/
[google_assistant docs]: /integrations/google_assistant/
-[light.demo docs]: /integrations/light.demo/
[media_player.sonos docs]: /integrations/sonos
diff --git a/source/_posts/2018-03-30-release-66.markdown b/source/_posts/2018-03-30-release-66.markdown
index 939ae2a063f..a56a7cc1905 100644
--- a/source/_posts/2018-03-30-release-66.markdown
+++ b/source/_posts/2018-03-30-release-66.markdown
@@ -27,7 +27,7 @@ A quick note if you are using Philips Hue and a Hue custom component: it will no
- 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)
+- Add initial support fo HomematicIP components ([@mxworm] - [#12761]) (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)
@@ -149,7 +149,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- 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)
+- Add initial support fo HomematicIP components ([@mxworm] - [#12761]) (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])
@@ -476,7 +476,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[history docs]: /integrations/history/
[homekit docs]: /integrations/homekit/
[homematic docs]: /integrations/homematic/
-[homematicip docs]: /integrations/homematicip/
[homematicip_cloud docs]: /integrations/homematicip_cloud/
[http docs]: /integrations/http/
[hue docs]: /integrations/hue/
@@ -526,7 +525,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.foobot docs]: /integrations/foobot
[sensor.glances docs]: /integrations/glances
[sensor.homematic docs]: /integrations/homematic
-[sensor.homematicip docs]: /integrations/homematicip/
[sensor.homematicip_cloud docs]: /integrations/homematicip_cloud/
[sensor.lacrosse docs]: /integrations/lacrosse
[sensor.mqtt docs]: /integrations/sensor.mqtt/
diff --git a/source/_posts/2018-06-04-esphomelib.markdown b/source/_posts/2018-06-04-esphomelib.markdown
index 53c53ccbb39..3c68102ea4a 100644
--- a/source/_posts/2018-06-04-esphomelib.markdown
+++ b/source/_posts/2018-06-04-esphomelib.markdown
@@ -59,7 +59,7 @@ At this point, you can already flash the firmware. To do this, first plug in the
## Adding some basic functionality
-Above configuration is, let’s face it, pretty dull. It really only connects to WiFi and MQTT and sits idle. So let’s add a basic [GPIO switch](https://esphomelib.com/esphomeyaml/integrations/switch/gpio.html)! The GPIO switch component in esphomelib allows you to control the ON/OFF state of any of the pins on your ESP. For example, if you add this configuration to the bottom of your YAML file, you’re setting up the pin `GPIO5` to be controlled as a switch with the name "Living Room Dehumidifer".
+Above configuration is, let’s face it, pretty dull. It really only connects to WiFi and MQTT and sits idle. So let’s add a basic [GPIO switch](https://esphome.io/components/switch/gpio.html)! The GPIO switch component in esphomelib allows you to control the ON/OFF state of any of the pins on your ESP. For example, if you add this configuration to the bottom of your YAML file, you’re setting up the pin `GPIO5` to be controlled as a switch with the name "Living Room Dehumidifer".
```yaml
switch:
diff --git a/source/_posts/2018-06-22-release-72.markdown b/source/_posts/2018-06-22-release-72.markdown
index 7cc8b84d813..c3111a4c61c 100644
--- a/source/_posts/2018-06-22-release-72.markdown
+++ b/source/_posts/2018-06-22-release-72.markdown
@@ -11,7 +11,7 @@ og_image: /images/blog/2018-06-release-0.72/lovelace.png
I am super excited about this release as it brings some great examples of how we are refining the system to become more customizable and, at the same time, user friendly. The first thing that I am really excited about is a new experimental user interface that we call Lovelace. Check [this awesome rundown](https://gist.github.com/ciotlosm/9508388876edf92c4c1f3579e740fbd5) of all the features by [@ciotlosm]. The TL;DR: a faster, more customizable and more extensible UI with the same look and feel as the old one.
-Be aware, this _is_ experimental, so things will change. However, we felt like we didn't want to keep this away from you any longer. Check the [Lovelace UI docs](https://developers.home-assistant.io/docs/en/lovelace_index.html) on how to get started. Make sure to share your creations!
+Be aware, this _is_ experimental, so things will change. However, we felt like we didn't want to keep this away from you any longer. Check the [Lovelace UI docs](/lovelace) on how to get started. Make sure to share your creations!
Thanks to all the people that have been hanging out in the #beta channel on [Discord](https://discord.gg/c5DvZ4e) helping development, finding and squashing bugs and making suggestions. Especially thanks to [@c727] for all his development work and [@arsaboo] for being the first guinea pig.
diff --git a/source/_posts/2018-09-17-thinking-big.markdown b/source/_posts/2018-09-17-thinking-big.markdown
index 1f3bc7b1b4f..31fe7e742b6 100644
--- a/source/_posts/2018-09-17-thinking-big.markdown
+++ b/source/_posts/2018-09-17-thinking-big.markdown
@@ -40,7 +40,7 @@ Many things! However, here is a list of things that I am most enthusiastic about
- Accessibility. We want to make Hass.io run on as many devices as possible, making it very easy for people to get started with a private home.
- Integrate Mozilla's [Web Things API] to make it easier to interact with other home automation platforms. The introduced device management makes it perfectly aligned with the Web Things data model.
- Cloud Transparency. We want to make it visible what data is being shared with Amazon Alexa and Google Home clouds.
- - Better Z-Wave. Our current integration has room for improvement. The owner of Z-Wave has announced a [public SDK](http://zwavepublic.com/), which we should explore to integrate with Home Assistant.
+ - Better Z-Wave. Our current integration has room for improvement. The owner of Z-Wave has announced a public SDK, which we should explore to integrate with Home Assistant.
## What we need to achieve this goal
diff --git a/source/_posts/2018-09-30-hacktoberfest.markdown b/source/_posts/2018-09-30-hacktoberfest.markdown
index 24b35a4c3c7..e0e845d6bad 100644
--- a/source/_posts/2018-09-30-hacktoberfest.markdown
+++ b/source/_posts/2018-09-30-hacktoberfest.markdown
@@ -47,11 +47,11 @@ Hacktoberfest will create a lot of work for us. In 2017 we processed 625 Pull Re
### Home Assistant Frontend
- Take a look at the [Polymer documentation](https://www.polymer-project.org/).
-- Read the [Home Assistant Frontend documentation](https://developers.home-assistant.io/docs/en/frontend_index.html).
+- Read the [Home Assistant Frontend documentation](https://developers.home-assistant.io/docs/frontend).
### Home Assistant
-- Get familiar with our [Style Guidelines](https://developers.home-assistant.io/docs/en/development_guidelines.html) and the existing code.
+- Get familiar with our [Style Guidelines](https://developers.home-assistant.io/docs/development_guidelines) and the existing code.
- Go through the [Developer documentation](https://developers.home-assistant.io).
- Don’t forget the documentation. Changes often require an update of the documentation. Also, new integrations. You know how it works, but the users don’t.
- [Architectural changes](https://github.com/home-assistant/architecture) need to be discussed before a change is proposed. Also, keep in mind that those kinds of Pull Request may not be reviewed during October.
@@ -59,8 +59,8 @@ Hacktoberfest will create a lot of work for us. In 2017 we processed 625 Pull Re
### Home Assistant Documentation
-- Make yourself familiar with [Markdown](https://developers.home-assistant.io/docs/en/documentation_index.html).
-- Understand our [Standards and Guidelines](https://developers.home-assistant.io/docs/en/documentation_standards.html).
+- Make yourself familiar with [Markdown](https://www.markdownguide.org/cheat-sheet).
+- Understand our [Standards and Guidelines](https://developers.home-assistant.io/docs/documenting/standards).
- For small changes like typos and clarifications, use the GitHub editor functionality.
- For more significant changes, we highly recommended that you set up an environment to build the documentation locally before opening a Pull Request.
- Keep an eye on the branches. `current` is for changes on the existing documentation, `next` for new features or integrations that will be available with the next release.
diff --git a/source/_posts/2019-01-09-release-85.markdown b/source/_posts/2019-01-09-release-85.markdown
index 3347db6f216..a4c2b2bd4da 100644
--- a/source/_posts/2019-01-09-release-85.markdown
+++ b/source/_posts/2019-01-09-release-85.markdown
@@ -205,7 +205,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Add native ESPHome API service call feature ([@OttoWinter] - [#19401]) ([esphome docs])
- Upgade colorlog to 4.0.2 ([@fabaff] - [#19390])
- Provide charging indicator for mychevy ([@sdague] - [#19348]) ([mychevy docs]) ([sensor.mychevy docs])
-- Add GTT Sensor ([@eliseomartelli] - [#18449]) ([sensor.gtt docs]) (new-platform)
+- Add GTT Sensor ([@eliseomartelli] - [#18449]) (new-platform)
- Upgrade volvooncall to 0.8.7 ([@molobrakos] - [#19398]) ([volvooncall docs])
- Cast lametric cycles parameter to int ([@deftdawg] - [#19370]) ([notify docs])
- Satel integra monitor outputs ([@c-soft] - [#19149]) ([satel_integra docs]) ([binary_sensor.satel_integra docs])
@@ -846,7 +846,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.geo_rss_events docs]: /integrations/geo_rss_events
[sensor.glances docs]: /integrations/glances
[sensor.gtfs docs]: /integrations/gtfs
-[sensor.gtt docs]: /integrations/gtt
[sensor.homematic docs]: /integrations/homematic
[sensor.homematicip_cloud docs]: /integrations/homematicip_cloud/
[sensor.huawei_lte docs]: /integrations/huawei_lte#sensor
diff --git a/source/_posts/2019-01-23-release-86.markdown b/source/_posts/2019-01-23-release-86.markdown
index e5dfc93a7a3..e77c94e565a 100644
--- a/source/_posts/2019-01-23-release-86.markdown
+++ b/source/_posts/2019-01-23-release-86.markdown
@@ -61,7 +61,7 @@ Another noteworthy breaking change (sorry!), is that the automation `time` trigg
## Release 0.86.1 - January 23
- Hotfix for blink initialization failure. Fixes #20335 ([@fronzbot] - [#20351]) ([blink docs])
-- [FIX] Time reporting incorrect in sensor.gtt ([@eliseomartelli] - [#20362]) ([sensor.gtt docs])
+- [FIX] Time reporting incorrect in sensor.gtt ([@eliseomartelli] - [#20362])
- Fix error when API doesn't return a forecast. ([@dgomes] - [#20365])
- Fix restore state crashing invalid entity ID ([@balloob] - [#20367])
- Calling save before load would crash Lovelace storage ([@balloob] - [#20368])
@@ -76,7 +76,6 @@ Another noteworthy breaking change (sorry!), is that the automation `time` trigg
[@eliseomartelli]: https://github.com/eliseomartelli
[@fronzbot]: https://github.com/fronzbot
[blink docs]: /integrations/blink/
-[sensor.gtt docs]: /integrations/gtt
## Release 0.86.2 - January 24
@@ -290,7 +289,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Added partial detection to async_add_job ([@andrewsayre] - [#20119])
- Fix tellduslive discovery and auth issues ([@fredrike] - [#20023]) ([tellduslive docs])
- Use voluptuous to perform validation for the geofency webhook ([@rohankapoorcom] - [#20067]) ([geofency docs])
-- fixed gtt to report isotime ([@eliseomartelli] - [#20128]) ([sensor.gtt docs])
+- fixed gtt to report isotime ([@eliseomartelli] - [#20128])
- Move MQTT platforms under the component ([@emontnemery] - [#20050]) ([mqtt docs])
- Split time_pattern triggers from time trigger ([@armills] - [#19825]) ([automation.interval docs]) ([automation.time docs]) (breaking change)
- Change deCONZ to embedded platforms ([@Kane610] - [#20113]) ([deconz docs])
@@ -676,7 +675,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.fibaro docs]: /integrations/fibaro
[sensor.flunearyou docs]: /integrations/flunearyou
[sensor.freebox docs]: /integrations/freebox#sensor
-[sensor.gtt docs]: /integrations/gtt
[sensor.hive docs]: /integrations/hive#sensor
[sensor.imap_email_content docs]: /integrations/imap_email_content/
[sensor.influxdb docs]: /integrations/influxdb#sensor
diff --git a/source/_posts/2019-01-24-nest-cannot-access-data.markdown b/source/_posts/2019-01-24-nest-cannot-access-data.markdown
index e83230261af..7c180a44a13 100644
--- a/source/_posts/2019-01-24-nest-cannot-access-data.markdown
+++ b/source/_posts/2019-01-24-nest-cannot-access-data.markdown
@@ -8,7 +8,7 @@ author_twitter: balloob
categories: Public-Service-Announcement
---
-**Update 1 (Jan 24):** We got some reports from people that they are still able to create accounts and generate the right keys. We just verified and this is the case. So for now you can still access your data, which is good. We're still puzzled on the response to our tweet. And thanks to Reddit user /u/lefos123 for [pointing out](https://www.reddit.com/r/homeassistant/comments/ajgiz2/nest_locks_users_out_of_their_own_data/eevh8on/) that they ~~[announced this](https://nestdevelopers.io/t/client-reviews-currently-suspended/1548)~~ [updated link](https://developers.nest.com/) on Nov 2018.
+**Update 1 (Jan 24):** We got some reports from people that they are still able to create accounts and generate the right keys. We just verified and this is the case. So for now you can still access your data, which is good. We're still puzzled on the response to our tweet. And thanks to Reddit user /u/lefos123 for [pointing out](https://www.reddit.com/r/homeassistant/comments/ajgiz2/nest_locks_users_out_of_their_own_data/eevh8on/) that they ~~announced this~~ [updated link](https://developers.nest.com/) on Nov 2018.
Although it's still working, we're still scared about the future of the Nest API.
diff --git a/source/_posts/2019-03-13-release-89.markdown b/source/_posts/2019-03-13-release-89.markdown
index 9a7b3957357..501f2566429 100644
--- a/source/_posts/2019-03-13-release-89.markdown
+++ b/source/_posts/2019-03-13-release-89.markdown
@@ -13,7 +13,7 @@ og_image: /images/blog/2019-03-release-89/components.png
It's time for release 0.89. It's another great new release with some cool new features, bug fixes and improvements. The first cool new feature is that yet another car is integrated into Home Assistant: the Nissan Leaf. Both deConz and SmartThings integrations keep expanding to cover more devices.
-This release introduces a new mobile app component. [@robbiet480], who also works on the iOS app, has taken the best parts of the Home Assistant iOS app component and turned it into a standardized API that any mobile app can build upon. This will allow any mobile apps to integrate with Home Assistant with a great user experience. If you are a mobile app developer, please check the updated [app integration docs](https://developers.home-assistant.io/docs/en/app_integration_index.html). We will be fine tuning the API in upcoming releases. Feedback is welcome.
+This release introduces a new mobile app component. [@robbiet480], who also works on the iOS app, has taken the best parts of the Home Assistant iOS app component and turned it into a standardized API that any mobile app can build upon. This will allow any mobile apps to integrate with Home Assistant with a great user experience. If you are a mobile app developer, please check the updated [app integration docs](https://developers.home-assistant.io/docs/api/native-app-integration/). We will be fine tuning the API in upcoming releases. Feedback is welcome.
## Noteworthy Breaking Changes
diff --git a/source/_posts/2019-04-15-hassio-ingress.markdown b/source/_posts/2019-04-15-hassio-ingress.markdown
index 296e9945619..b64b04e4169 100644
--- a/source/_posts/2019-04-15-hassio-ingress.markdown
+++ b/source/_posts/2019-04-15-hassio-ingress.markdown
@@ -83,4 +83,4 @@ We found a last minute issue impacting Firefox based browsers (including the Tor
[InfluxDB]: https://github.com/hassio-addons/addon-influxdb#readme
[SSH & Web Terminal]: https://github.com/hassio-addons/addon-ssh#readme
[AdGuard Home]: https://github.com/hassio-addons/addon-adguard-home#readme
-[dev-docs]: https://developers.home-assistant.io/docs/en/next/hassio_addon_presentation.html#ingress
+[dev-docs]: https://developers.home-assistant.io/docs/add-ons/presentation/#ingress
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index d87370cb7af..6b88d49a624 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -7,7 +7,6 @@ author: Paulus Schoutsen
author_twitter: balloob
categories: Release-Notes
og_image: /images/blog/2019-06-release-94/google-ui.png
-redirect_from: /blog/2019/05/29/release-94/
---
diff --git a/source/_posts/2019-10-10-release-100.markdown b/source/_posts/2019-10-10-release-100.markdown
index 7c386062eae..f50b8720265 100644
--- a/source/_posts/2019-10-10-release-100.markdown
+++ b/source/_posts/2019-10-10-release-100.markdown
@@ -908,7 +908,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[evohome docs]: /integrations/evohome/
[fedex docs]: /integrations/fedex/
[frontend docs]: /integrations/frontend/
-[generic docs]: /integrations/generic/
[geniushub docs]: /integrations/geniushub/
[geonetnz_quakes docs]: /integrations/geonetnz_quakes/
[glances docs]: /integrations/glances/
diff --git a/source/_posts/2019-10-30-release-101.markdown b/source/_posts/2019-10-30-release-101.markdown
index 3001649441b..d47bfca302a 100644
--- a/source/_posts/2019-10-30-release-101.markdown
+++ b/source/_posts/2019-10-30-release-101.markdown
@@ -223,8 +223,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
- __Removed__ - The following integrations have been removed:
- __Direct authentication via trusted networks or API password__ - It is no longer possible to make authenticated requests using trusted networks or by appending ?api_password=X to the URL. You will now first need to get an authentication token and use that token to make requests. Auth providers for trusted networks and API passwords are still available. - ([@balloob] - [#27656]) ([auth docs]) ([http docs]) ([websocket_api docs])
- - __Stride__ - The Stride notification integration was discontinued in February 2019 due to a take over by Slack. - ([@hmmbob] - [#27934]) ([stride docs])
- - __Hipchat__ - The Hipchat notification integration was discontinued in February 2019, also due to a take over by Slack. - ([@fabaff] - [#27399]) ([hipchat docs])
+ - __Stride__ - The Stride notification integration was discontinued in February 2019 due to a take over by Slack. - ([@hmmbob] - [#27934])
+ - __Hipchat__ - The Hipchat notification integration was discontinued in February 2019, also due to a take over by Slack. - ([@fabaff] - [#27399])
- __Deprecated__ - Python 3.6 support is deprecated (to be removed completely by December 2019), as version 3.8.0 is now out - ([@scop] - [#27680])
- __Scene__ - Scenes have to be configured more strictly from now on. Each entity must be configured with a valid state. Furthermore, the attributes that can be used must be `device state attributes`. This means that they should be listed under _developer-tools -> states_. - ([scene docs])
- __Ecobee__ - Adds `turn_on` method to ecobee climate platform. Previously, calling `climate.turn_on` would cause the ecobee thermostat to turn on in heat mode, regardless of the mode when the thermostat was turned off. Now, the thermostat will turn on to the last "active" HVAC mode (i.e., "heat", "cool", or "auto") (or, if the thermostat was "off" when Home Assistant started, to "auto"). - ([@marthoc] - [#27103]) ([ecobee docs])
@@ -370,7 +370,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
- move import to top-level ([@exxamalte] - [#27353]) ([onkyo docs])
- move import to top-level ([@exxamalte] - [#27352]) ([systemmonitor docs])
- Allow Google Assistant relative volume control ([@RyanEwen] - [#26585]) ([google_assistant docs])
-- Remove hipchat ([@fabaff] - [#27399]) ([hipchat docs]) (breaking change)
+- Remove hipchat ([@fabaff] - [#27399]) (breaking change)
- Move imports in waze_travel_time component ([@eifinger] - [#27384]) ([waze_travel_time docs])
- Move imports in wemo component ([@Quentame] - [#27393]) ([wemo docs])
- Move imports in wink component ([@Quentame] - [#27392]) ([wink docs])
@@ -385,7 +385,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
- Move imports in github component ([@mnigbur] - [#27406]) ([github docs])
- Move imports in eufy component ([@mnigbur] - [#27405]) ([eufy docs])
- Move imports in apple_tv component ([@Quentame] - [#27356]) ([apple_tv docs])
-- Remove hydroquebec integration (ADR-0004) ([@frenck] - [#27407]) ([hydroquebec docs])
+- Remove hydroquebec integration (ADR-0004) ([@frenck] - [#27407])
- Standardize times in time sensors Jewish calendar ([@tsvi] - [#26940]) ([jewish_calendar docs]) (breaking change)
- Revert "Allow Google Assistant relative volume control (#26585)" ([@balloob] - [#27416]) ([google_assistant docs])
- Bump aiohttp to 3.6.2 ([@frenck] - [#27409])
@@ -672,7 +672,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
- Bump abodepy version ([@shred86] - [#27931]) ([abode docs])
- Add support for AdGuard Home v0.99.0 ([@frenck] - [#27926]) ([adguard docs]) (breaking change)
- remove duplicate unique_id, add unique_id for issues ([@zxdavb] - [#27916]) ([geniushub docs]) (breaking change)
-- Remove stride ([@hmmbob] - [#27934]) ([stride docs]) (breaking change)
+- Remove stride ([@hmmbob] - [#27934]) (breaking change)
- Import shuffle ([@balloob] - [#27935]) ([http docs]) ([persistent_notification docs]) ([stream docs])
- Update pysonos to 0.0.24 ([@timmccor] - [#27937]) ([sonos docs])
- Bump pybotvac ([@Santobert] - [#27933]) ([neato docs])
@@ -1654,7 +1654,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
[glances docs]: /integrations/glances/
[gntp docs]: /integrations/gntp/
[goalfeed docs]: /integrations/goalfeed/
-[google docs]: /integrations/google/
+[google docs]: /integrations/calendar.google/
[google_assistant docs]: /integrations/google_assistant/
[google_travel_time docs]: /integrations/google_travel_time/
[gpsd docs]: /integrations/gpsd/
@@ -1666,7 +1666,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
[hassio docs]: /integrations/hassio/
[hikvision docs]: /integrations/hikvision/
[hikvisioncam docs]: /integrations/hikvisioncam/
-[hipchat docs]: /integrations/hipchat/
[hive docs]: /integrations/hive/
[homeassistant docs]: /integrations/homeassistant/
[homekit docs]: /integrations/homekit/
@@ -1677,7 +1676,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
[http docs]: /integrations/http/
[htu21d docs]: /integrations/htu21d/
[hue docs]: /integrations/hue/
-[hydroquebec docs]: /integrations/hydroquebec/
[ifttt docs]: /integrations/ifttt/
[ign_sismologia docs]: /integrations/ign_sismologia/
[image_processing docs]: /integrations/image_processing/
@@ -1833,7 +1831,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
[statsd docs]: /integrations/statsd/
[steam_online docs]: /integrations/steam_online/
[stream docs]: /integrations/stream/
-[stride docs]: /integrations/stride/
[sun docs]: /integrations/sun/
[supla docs]: /integrations/supla/
[switch docs]: /integrations/switch/
diff --git a/source/_posts/2019-11-20-release-102.markdown b/source/_posts/2019-11-20-release-102.markdown
index c430b62fbaa..95e272e9402 100644
--- a/source/_posts/2019-11-20-release-102.markdown
+++ b/source/_posts/2019-11-20-release-102.markdown
@@ -887,7 +887,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[geonetnz_quakes docs]: /integrations/geonetnz_quakes/
[google_assistant docs]: /integrations/google_assistant/
[greeneye_monitor docs]: /integrations/greeneye_monitor/
-[gtt docs]: /integrations/gtt/
[hangouts docs]: /integrations/hangouts/
[hassio docs]: /integrations/hassio/
[here_travel_time docs]: /integrations/here_travel_time/
diff --git a/source/_posts/2019-11-22-state-of-the-union.markdown b/source/_posts/2019-11-22-state-of-the-union.markdown
index 4c2718372b3..ac9e89a7f37 100644
--- a/source/_posts/2019-11-22-state-of-the-union.markdown
+++ b/source/_posts/2019-11-22-state-of-the-union.markdown
@@ -8,8 +8,6 @@ author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Announcements
-redirect_from:
- - /state-of-the-union/
og_image: /images/blog/2019-11-state-of-the-union/social.jpeg
---
diff --git a/source/_posts/2019-12-11-release-103.markdown b/source/_posts/2019-12-11-release-103.markdown
index 45b3791a04a..04ccdf2b4bf 100644
--- a/source/_posts/2019-12-11-release-103.markdown
+++ b/source/_posts/2019-12-11-release-103.markdown
@@ -224,7 +224,7 @@ All services for use in Home Assistant are moved to their integration naming spa
- **Z-Wave** - This changes the primary command class for z-wave thermostats in discovery schemas from `COMMAND_CLASS_THERMOSTAT_SETPOINT` to `COMMAND_CLASS_THERMOSTAT_MODE`. This will cause a typical dual setpoint thermostat to be correctly represented as a single entity. - ([@oandrew] - [#27040]) ([zwave docs])
- **Transmission** - Added host field to `add_torrent` service in order to support multiple Transmission instances. ([@engrbm87] - [#28653]) ([transmission docs])
- **Opentherm Gateway** - Adds device support. This change breaks enabled `sensor` and `binary_sensor` entities, which are now disabled by default and can be re-enabled through the Devices panel. It also breaks `entity_id` of the climate entity in some configurations. The `entity_id` is now based on the `gateway_id` rather than the configured `name` to guarantee uniqueness. - ([@mvn23] - [#28722]) ([opentherm_gw docs])
-- **Intent** - If you use the built-in intents for shopping list, cover or light, you need to add `intent:` to your `configuration.yaml`. - ([@balloob] - [#29280]) ([conversation docs]) ([cover docs]) ([intent docs]) ([light docs]) ([shopping_list docs])
+- **Intent** - If you use the built-in intents for shopping list, cover or light, you need to add `intent:` to your `configuration.yaml`. - ([@balloob] - [#29280]) ([conversation docs]) ([cover docs]) ([light docs]) ([shopping_list docs])
- **Emulated Hue** - As previous `entityid` were not Hue compliant, `emulated_hue_ids.json` will need to be cleared out and devices re-discovered and configured in Alexa / Google Home. This is a necessary growing pain to move the integration forward in a Hue-compliant fashion. - ([@NobleKangaroo] - [#28317]) ([emulated_hue docs])
- **Miflora** - Values for an unresponsive device aren't reported any more as if they were valid, so it's possible to send an alert. - ([@ferbar] - [#29276]) ([miflora docs])
@@ -516,7 +516,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Move velux imports at top-level ([@Quentame] - [#29085]) ([velux docs])
- Move upnp imports at top-level ([@Quentame] - [#29083]) ([upnp docs])
- Move dlna_dmr imports at top-level ([@Quentame] - [#29082]) ([dlna_dmr docs])
-- Move imports to top for xfinity ([@springstan] - [#29077]) ([xfinity docs])
+- Move imports to top for xfinity ([@springstan] - [#29077])
- Move imports to top for xeoma ([@springstan] - [#29076]) ([xeoma docs])
- Move imports to top for version ([@springstan] - [#29075]) ([version docs])
- Move imports to top for yale_smart_alarm ([@springstan] - [#29074]) ([yale_smart_alarm docs])
@@ -601,7 +601,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- move wink service definitions from lock to wink domain ([@raman325] - [#29137]) ([wink docs]) (breaking change)
- Update service domain for lifx from 'light' to 'lifx' ([@raman325] - [#29136]) ([lifx docs]) (breaking change)
- move service constants to const.py and move channels services to channels domain ([@raman325] - [#29139]) ([channels docs]) (breaking change)
-- Add intent integration to expose intent handle API ([@balloob] - [#29124]) ([conversation docs]) ([intent docs]) (new-integration)
+- Add intent integration to expose intent handle API ([@balloob] - [#29124]) ([conversation docs]) (new-integration)
- Update service domain for todoist from 'calendar' to 'todoist' ([@raman325] - [#29131]) ([todoist docs]) (breaking change)
- update envisalink service domain ([@raman325] - [#29126]) ([envisalink docs]) (breaking change)
- Update service domain for mysensors from 'switch' to 'mysensor… ([@raman325] - [#29147]) ([mysensors docs])
@@ -705,7 +705,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Move imports to top for seventeentrack ([@springstan] - [#29264]) ([seventeentrack docs])
- Improve naming and attrs of hostnameless Huawei LTE device tracker entities ([@scop] - [#29281]) ([huawei_lte docs])
- Limit parallel requests to Philips Hue ([@bramkragten] - [#29189]) ([hue docs])
-- Move intent registration to own integration ([@balloob] - [#29280]) ([conversation docs]) ([cover docs]) ([intent docs]) ([light docs]) ([shopping_list docs]) (breaking change)
+- Move intent registration to own integration ([@balloob] - [#29280]) ([conversation docs]) ([cover docs]) ([light docs]) ([shopping_list docs]) (breaking change)
- Overhaul Emulated Hue ([@NobleKangaroo] - [#28317]) ([emulated_hue docs]) (breaking change)
- Add name option to season sensor ([@springstan] - [#29302]) ([season docs])
- Add capability-attributes ([@balloob] - [#29306]) ([light docs])
@@ -1581,7 +1581,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[iglo docs]: /integrations/iglo/
[ihc docs]: /integrations/ihc/
[input_datetime docs]: /integrations/input_datetime/
-[intent docs]: /integrations/intent/
[intent_script docs]: /integrations/intent_script/
[ios docs]: /integrations/ios/
[iota docs]: /integrations/iota/
@@ -1802,7 +1801,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[wled docs]: /integrations/wled/
[workday docs]: /integrations/workday/
[xeoma docs]: /integrations/xeoma/
-[xfinity docs]: /integrations/xfinity/
[xiaomi docs]: /integrations/xiaomi/
[xiaomi_aqara docs]: /integrations/xiaomi_aqara/
[xiaomi_miio docs]: /integrations/xiaomi_miio/
diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown
index f36ea8d92b9..b09976634eb 100644
--- a/source/_posts/2020-01-15-release-104.markdown
+++ b/source/_posts/2020-01-15-release-104.markdown
@@ -724,7 +724,7 @@ Make sure to fill in all fields of the issue template, that is helping us a lot!
- Sort imports according to PEP8 for components starting with "W" ([@basnijholt] - [#29781])
- Sort imports according to PEP8 for components starting with "Q" ([@basnijholt] - [#29785])
- Sort imports according to PEP8 for components starting with "Y" ([@basnijholt] - [#29783]) ([yale_smart_alarm docs]) ([yamaha docs]) ([yamaha_musiccast docs]) ([yandex_transport docs]) ([yeelightsunflower docs]) ([yessssms docs])
-- Sort imports according to PEP8 for components starting with "X" ([@basnijholt] - [#29782]) ([x10 docs]) ([xbox_live docs]) ([xeoma docs]) ([xfinity docs]) ([xiaomi_tv docs]) ([xmpp docs]) ([xs1 docs])
+- Sort imports according to PEP8 for components starting with "X" ([@basnijholt] - [#29782]) ([x10 docs]) ([xbox_live docs]) ([xeoma docs]) ([xiaomi_tv docs]) ([xmpp docs]) ([xs1 docs])
- Move imports to top for homekit ([@springstan] - [#29560]) ([homekit docs])
- Cleanup removed component ([@pvizeli] - [#29788])
- Sort imports according to PEP8 for 'script' folder ([@basnijholt] - [#29790])
@@ -2073,7 +2073,6 @@ Make sure to fill in all fields of the issue template, that is helping us a lot!
[x10 docs]: /integrations/x10/
[xbox_live docs]: /integrations/xbox_live/
[xeoma docs]: /integrations/xeoma/
-[xfinity docs]: /integrations/xfinity/
[xiaomi_miio docs]: /integrations/xiaomi_miio/
[xiaomi_tv docs]: /integrations/xiaomi_tv/
[xmpp docs]: /integrations/xmpp/
diff --git a/source/_posts/2020-02-05-release-105.markdown b/source/_posts/2020-02-05-release-105.markdown
index bbdcc333b51..1101061275d 100644
--- a/source/_posts/2020-02-05-release-105.markdown
+++ b/source/_posts/2020-02-05-release-105.markdown
@@ -1448,7 +1448,7 @@ Hats over your heart for these shuttered integrations. Pour one out for:
[fritzbox_netmonitor docs]: /integrations/fritzbox_netmonitor/
[frontend docs]: /integrations/frontend/
[garmin_connect docs]: /integrations/garmin_connect/
-[generic docs]: /integrations/generic/
+[generic docs]: /integrations/generic_ip_camera/
[generic_thermostat docs]: /integrations/generic_thermostat/
[geniushub docs]: /integrations/geniushub/
[geonetnz_volcano docs]: /integrations/geonetnz_volcano/
diff --git a/source/_posts/2020-02-07-community-highlights.markdown b/source/_posts/2020-02-07-community-highlights.markdown
index 1f2adb85fbd..604d59f4477 100644
--- a/source/_posts/2020-02-07-community-highlights.markdown
+++ b/source/_posts/2020-02-07-community-highlights.markdown
@@ -46,7 +46,7 @@ _Thanks, [Robbie Trencheny](https://twitter.com/robbie) & [cgtobi](https://twitt
## An auto-generating Lovelace UI theme
-Dwain Scheeren shared a preview of his Lovelace theme on the [Home Assistant Community Forum]((https://community.home-assistant.io/t/dwains-theme-an-auto-generating-lovelace-ui-theme/168593)). The cool think about this theme, is that it automatically generates itself!
+Dwain Scheeren shared a preview of his Lovelace theme on the [Home Assistant Community Forum](https://community.home-assistant.io/t/dwains-theme-an-auto-generating-lovelace-ui-theme/168593). The cool think about this theme, is that it automatically generates itself!
diff --git a/source/_posts/2020-05-20-release-110.markdown b/source/_posts/2020-05-20-release-110.markdown
index 825eee440c1..52eac734a40 100644
--- a/source/_posts/2020-05-20-release-110.markdown
+++ b/source/_posts/2020-05-20-release-110.markdown
@@ -1052,7 +1052,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Bump plexwebsocket to 0.0.8 ([@jjlawren] - [#35351]) ([plex docs])
- Enable async_update for entities in NWS ([@MatthewFlamm] - [#35048]) ([nws docs])
- Migrate ISY994 to PyISY v2 ([@shbatm] - [#35338]) ([isy994 docs]) (breaking-change)
-- Delete flapping automatic tests ([@bdraco] - [#35356]) ([automatic docs])
+- Delete flapping automatic tests ([@bdraco] - [#35356])
- Rewrite JuiceNet for async and config flow ([@jesserockz] - [#34365]) ([juicenet docs])
- Add modbus sensor string data_type ([@bradkeifer] - [#35269]) ([modbus docs])
- Capitalize kane610 in codeowners since scripts are case sensitive ([@Kane610] - [#35375]) ([axis docs]) ([deconz docs]) ([unifi docs])
@@ -1731,7 +1731,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[arest docs]: /integrations/arest/
[atag docs]: /integrations/atag/
[august docs]: /integrations/august/
-[automatic docs]: /integrations/automatic/
[automation docs]: /integrations/automation/
[axis docs]: /integrations/axis/
[basic config docs]: /docs/configuration/basic/
diff --git a/source/_posts/2020-07-01-release-113.markdown b/source/_posts/2020-07-01-release-113.markdown
index 61097dbb990..b688f43ce04 100644
--- a/source/_posts/2020-07-01-release-113.markdown
+++ b/source/_posts/2020-07-01-release-113.markdown
@@ -344,7 +344,7 @@ Please note: It is possible that custom integrations (also known as
custom components) use deprecated icons. These can throw warnings that need
to be addressed in the custom integration.
-[mdi]: https://www.materialdesignicons.com
+[mdi]: https://materialdesignicons.com
[mdi-upgrade]: https://dev.materialdesignicons.com/upgrade#4.9.95-to-5.0.45
[simple-icons]: https://simpleicons.org/
[hass-simpleicons]: https://github.com/vigonotion/hass-simpleicons
diff --git a/source/_posts/2020-08-05-mobile-apps-new-features.markdown b/source/_posts/2020-08-05-mobile-apps-new-features.markdown
index 495006c927a..299ee6ff657 100644
--- a/source/_posts/2020-08-05-mobile-apps-new-features.markdown
+++ b/source/_posts/2020-08-05-mobile-apps-new-features.markdown
@@ -91,7 +91,7 @@ Screenshot of Biometric Unlock.
We have also been hard at working making improvements in other areas of the app:
-* There are now 2 [widgets](https://companion.home-assistant.io/docs/core/android-widgets) that you can set up, with Entity State being the latest addition. The Entity State widget will display the state and any attribute of the selected entity. It will update once every 30 minutes or when tapped. The Service Call widget was also enhanced to allow you to select from a list of valid and available services along with the ability to add additional data fields that the service may require.
+* There are now 2 [widgets](https://companion.home-assistant.io/docs/integrations/android-widgets) that you can set up, with Entity State being the latest addition. The Entity State widget will display the state and any attribute of the selected entity. It will update once every 30 minutes or when tapped. The Service Call widget was also enhanced to allow you to select from a list of valid and available services along with the ability to add additional data fields that the service may require.
* In App Configuration the Home Network WiFi SSID option now allows the user to select multiple SSIDs.
* A Cookie Manager was added to our WebView that will allow you to save cookies from sites that you may use in the [webpage card](/lovelace/iframe/).
* More descriptive SSL error messages were added to help users resolve local issues they may encounter while setting up the app.
@@ -130,7 +130,7 @@ Another avenue of improvement is making things a bit easier. You’ll now find e
#### A look ahead at iOS 14
-Coming to iOS 14 is Widgets, and no doubt there’s some huge potential here. A good analogy for what they can do is to think of them as Apple Watch complications; relatively static displays that can be updated with a multitude of data. One thing we’d love is to get an idea of the information and displays you’re interested in seeing here as Widgets get built out over the next few months. Please let us know any ideas you have on [this thread](https://community.home-assistant.io/t/what-kind-of-ios-14-widgets-would-you-like-to-see).
+Coming to iOS 14 is Widgets, and no doubt there’s some huge potential here. A good analogy for what they can do is to think of them as Apple Watch complications; relatively static displays that can be updated with a multitude of data. One thing we’d love is to get an idea of the information and displays you’re interested in seeing here as Widgets get built out over the next few months. Please let us know any ideas you have on [this thread](https://community.home-assistant.io/t/what-kind-of-ios-14-big-sur-widgets-would-you-like-to-see).
iOS 14 is also introducing [Local Push Connectivity](https://developer.apple.com/documentation/networkextension/local_push_connectivity), which adds support for push notifications on your local network that do not require a trip to the cloud. This, like Critical Alerts, requires explicit approval from Apple, but we’re hopeful about improving the experience with your boats and RVs!
diff --git a/source/_posts/2020-09-17-release-115.markdown b/source/_posts/2020-09-17-release-115.markdown
index b6af59d4854..27b4f89de74 100644
--- a/source/_posts/2020-09-17-release-115.markdown
+++ b/source/_posts/2020-09-17-release-115.markdown
@@ -130,10 +130,10 @@ Thanks to [@jjlawren] for the initial implementation and to [@cgtobi],
integrations and backend refining.
But a media browser isn't just backend, it also needs to look good. Thankfully,
-we had [@NKDZCK] on the case, with the help of [@bramkragten]. They came up with
+we had [@zsarnett] on the case, with the help of [@bramkragten]. They came up with
a beautiful design so you can browse your media in style.
-[@nkdzck]: https://github.com/NKDZCK
+[@zsarnett]: https://github.com/zsarnett
@@ -173,7 +173,7 @@ If you click its media browser button, you will be presented with the available
local sources.
Sometimes you just want to play your media without having to turn on the TV. To
-cover that case, [@NKDZCK] added a new media browser to the Home Assistant
+cover that case, [@zsarnett] added a new media browser to the Home Assistant
interface, which can be used to play your media. That way, you can quickly see
what that motion event that you just received was about.
diff --git a/source/_posts/2020-10-01-hacktoberfest-2020.markdown b/source/_posts/2020-10-01-hacktoberfest-2020.markdown
new file mode 100644
index 00000000000..bea7dbf57c6
--- /dev/null
+++ b/source/_posts/2020-10-01-hacktoberfest-2020.markdown
@@ -0,0 +1,94 @@
+---
+title: "Hacktoberfest 2020"
+description: "It is October and Hacktoberfest started! Home Assistant participates again this year, and you?"
+date: 2020-10-01 00:00:00
+date_formatted: "October 1, 2020"
+author: Franck Nijhof
+author_twitter: frenck
+categories: Community
+og_image: /images/blog/2020-10-01-hacktoberfest-2020/social.png
+---
+
+
+
+October has started, which means: [Hacktoberfest][hacktoberfest]!
+
+Hacktoberfest is a worldwide, month-long celebration of open source. An event
+open to everyone. Whether you’re a developer, student learning to code,
+documenter, designer, you can help drive the growth of open source projects,
+like Home Assistant.
+
+By participating in Hacktoberfest, and by contributing four GitHub pull
+requests, you will earn either a free t-shirt or, new this year, have a
+tree planted. All backgrounds and skill levels are encouraged to complete the
+Hacktoberfest challenge.
+
+Just like all other years, Home Assistant participates in Hacktoberfest.
+
+## What to work on?
+
+So, you’ve decided to earn yourself that free Hacktoberfest t-shirt? Great!
+We've collected a bunch of tasks/suggestions/bugs that we'd love to get
+some help on. You can find those by filtering/searching for issues with
+the [`hacktoberfest` label][all].
+
+- **[Core Hacktoberfest issues][core]**
+
+ For example, help us migrate
+ [unittest tests to pytest style test][testcase] functions or lend a hand with
+ using as many references as possible
+ in the [configuration flow translations][translations].
+
+- **[Frontend Hacktoberfest issues][frontend]**
+
+ We could use some help with [moving all `paper-dialogs` to `ha-dialogs`][paper].
+
+- **[Documentation Hacktoberfest issues][docs]**
+
+ [Find and fix broken links][links] on our website or help to complete the
+ addition of the [right IoT Class to every integration][class].
+
+Or view all our Hacktoberfest issues across [all Home Assistant projects][all].
+
+Additionally, we recently held the [month of "What the heck?!"][wth-blog]. During
+this month a lot of suggestions and annoyances got reported by our community.
+While, those topic may not be approved as a change yet, it might be a great
+source of inspiration to contribute something the community wants. Check out
+the [WTH community forum posts][wth].
+
+## But, I'm not a developer?!
+
+If you are not a developer, new to git, GitHub or open source in general,
+documentation can be a great way to get started. A relatively easy way to
+contribute, is by reviewing the documentation of integrations you use or are
+familiar with, checking if everything is still up to date and is free of
+spelling/grammar mistakes.
+
+Every single documentation page on our website has a "Edit this page on GitHub",
+on the top right corner. Using that link, you can change the text on that page
+and provide a suggestion for improvement.
+
+On our Community forum, there is a good, step-by-step, guide on how this works:
+[Editing the Documentation and Creating a Pull Request on GitHub][docs-how-to].
+
+So, what are you waiting for? Sign-up on the [Hacktoberfest][hacktoberfest]
+website and start hacking! If you have any questions, please, drop by on our
+[Discord chat server](/join-chat). We have dedicated developer channels and
+are happy to assist you.
+
+Happy Hacktoberfest 🎉
+
+[all]: https://github.com/search?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Ahacktoberfest+org%3Ahome-assistant
+[brands]: https://github.com/home-assistant/brands/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Ahacktoberfest
+[class]: https://github.com/home-assistant/home-assistant.io/issues/14661
+[core]: https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Ahacktoberfest
+[docs-how-to]: https://community.home-assistant.io/t/editing-the-documentation-and-creating-a-pull-request-on-github/9573
+[docs]: https://github.com/home-assistant/home-assistant.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Ahacktoberfest
+[frontend]: https://github.com/home-assistant/frontend/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Ahacktoberfest
+[hacktoberfest]: https://hacktoberfest.digitalocean.com/
+[links]: https://github.com/home-assistant/home-assistant.io/issues/14663
+[paper]: https://github.com/home-assistant/frontend/issues/6138
+[testcase]: https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Aunittest.TestCase
+[translations]: https://github.com/home-assistant/core/issues/40578
+[wth-blog]: https://www.home-assistant.io/blog/2020/08/18/the-month-of-what-the-heck/
+[wth]: https://community.home-assistant.io/c/what-the-heck/52/l/latest?order=votes
diff --git a/source/_redirects b/source/_redirects
index 4cb24d19dbb..f6a264a3355 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -40,18 +40,18 @@
/developers/development_testing https://developers.home-assistant.io/docs/development_testing/
/developers/development_validation https://developers.home-assistant.io/docs/development_validation/
/developers/development https://developers.home-assistant.io/docs/development_index/
-/developers/documentation/create_page https://developers.home-assistant.io/docs/documenting/create-page/
-/developers/documentation https://developers.home-assistant.io/docs/documentation_index/
-/developers/documentation/standards https://developers.home-assistant.io/docs/documentation_standards/
-/developers/frontend_add_card https://developers.home-assistant.io/docs/frontend_add_card/
-/developers/frontend_add_more_info https://developers.home-assistant.io/docs/frontend_add_more_info/
-/developers/frontend_creating_custom_panels https://developers.home-assistant.io/docs/frontend_creating_custom_panels/
-/developers/frontend_creating_custom_ui https://developers.home-assistant.io/docs/frontend_creating_custom_ui/
-/developers/frontend https://developers.home-assistant.io/docs/frontend_index/
+/developers/documentation/create_page https://developers.home-assistant.io/docs/documenting/create-page
+/developers/documentation https://developers.home-assistant.io/docs/documenting
+/developers/documentation/standards https://developers.home-assistant.io/docs/documenting/standards
+/developers/frontend_add_card https://developers.home-assistant.io/docs/frontend/extending/adding-state-card
+/developers/frontend_add_more_info https://developers.home-assistant.io/docs/frontend/extending/adding-more-info-dialogs
+/developers/frontend_creating_custom_panels https://developers.home-assistant.io/docs/frontend/custom-ui/creating-custom-panels
+/developers/frontend_creating_custom_ui https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card
+/developers/frontend https://developers.home-assistant.io/docs/frontend
/developers/hassio/addon_communication https://developers.home-assistant.io/docs/hassio_addon_communication/
/developers/hassio/addon_config https://developers.home-assistant.io/docs/hassio_addon_config/
/developers/hassio/addon_development https://developers.home-assistant.io/docs/hassio_addon_index/
-/developers/hassio/addon_presentation https://developers.home-assistant.io/docs/hassio_addon_presentation/
+/developers/hassio/addon_presentation https://developers.home-assistant.io/docs/add-ons/presentation/
/developers/hassio/addon_publishing https://developers.home-assistant.io/docs/hassio_addon_publishing/
/developers/hassio/addon_repository https://developers.home-assistant.io/docs/hassio_addon_repository/
/developers/hassio/addon_testing https://developers.home-assistant.io/docs/hassio_addon_testing/
@@ -76,6 +76,7 @@
/developers/rest_api https://developers.home-assistant.io/docs/api/rest/
/developers/server_sent_events https://developers.home-assistant.io/docs/external_api_server_sent_events/
/developers/websocket_api https://developers.home-assistant.io/docs/api/websocket/
+/developers/code_of_conduct /code_of_conduct
# Platform pages to integration pages migration
/components/air_pollutants /integrations/air_quality
@@ -174,7 +175,7 @@
/components/binary_sensor.rainmachine /integrations/rainmachine
/components/binary_sensor.random /integrations/random#binary-sensor
/components/binary_sensor.raspihats /integrations/raspihats#binary-sensor
-/components/binary_sensor.rfxtrx /integrations/rfxtrx#binary-sensor
+/components/binary_sensor.rfxtrx /integrations/rfxtrx#binary-sensors
/components/binary_sensor.ring /integrations/ring#binary-sensor
/components/binary_sensor.rpi_gpio /integrations/rpi_gpio#binary-sensor
/components/binary_sensor.rpi_pfio /integrations/rpi_pfio#binary-sensor
@@ -829,7 +830,7 @@
/components/sensor.reddit /integrations/reddit
/components/sensor.rejseplanen /integrations/rejseplanen
/components/sensor.rest /integrations/rest
-/components/sensor.rfxtrx /integrations/rfxtrx#sensor
+/components/sensor.rfxtrx /integrations/rfxtrx#sensors
/components/sensor.ring /integrations/ring#sensor
/components/sensor.ripple /integrations/ripple
/components/sensor.rmvtransport /integrations/rmvtransport
@@ -1085,6 +1086,7 @@
/integrations/sensor.xiaomi_miio /integrations/xiaomi_miio
/integrations/switch.xiaomi_miio /integrations/xiaomi_miio
/integrations/vacuum.xiaomi_miio /integrations/xiaomi_miio
+/integrations/lovelace /lovelace
# Renaming components to integrations
/components /integrations
@@ -1158,7 +1160,6 @@
/components/binary_sensor.mysensors /integrations/binary_sensor.mysensors
/components/binary_sensor.rest /integrations/binary_sensor.rest
/components/binary_sensor.rflink /integrations/binary_sensor.rflink
-/components/binary_sensor.rfxtrx /integrations/binary_sensor.rfxtrx
/components/binary_sensor.template /integrations/binary_sensor.template
/components/binary_sensor.xiaomi_aqara /integrations/binary_sensor.xiaomi_aqara
/components/bitcoin /integrations/bitcoin
@@ -1763,12 +1764,12 @@
/components/sensor.command_line /integrations/sensor.command_line
/components/sensor.ios /integrations/sensor.ios
/components/sensor.knx /integrations/sensor.knx
-/components/sensor.metoffice /integrations/sensor.metoffice
+/components/sensor.metoffice /integrations/metoffice
/components/sensor.modbus /integrations/sensor.modbus
/components/sensor.mqtt /integrations/sensor.mqtt
/components/sensor.mysensors /integrations/sensor.mysensors
/components/sensor.rflink /integrations/sensor.rflink
-/components/sensor.rfxtrx /integrations/sensor.rfxtrx
+/components/sensor.rfxtrx /integrations/rfxtrx#sensors
/components/sensor.websocket_api /integrations/sensor.websocket_api
/components/sensor.xiaomi_aqara /integrations/sensor.xiaomi_aqara
/components/sensor.xiaomi_miio /integrations/sensor.xiaomi_miio
@@ -1834,7 +1835,6 @@
/components/stiebel_eltron /integrations/stiebel_eltron
/components/stream /integrations/stream
/components/streamlabswater /integrations/streamlabswater
-/components/stride /integrations/stride
/components/suez_water /integrations/suez_water
/components/sun /integrations/sun
/components/supervisord /integrations/supervisord
@@ -2027,6 +2027,8 @@
/integrations/telegram_chatbot /integrations/telegram_bot
# Moved documentation
+/details/database /docs/backend/database
+/details/updater /docs/backend/updater
/docs/ecosystem/ios/ https://companion.home-assistant.io/
/docs/ecosystem/ios/devices_file https://companion.home-assistant.io/
/docs/ecosystem/ios/integration https://companion.home-assistant.io/docs/integrations/integrations
@@ -2047,6 +2049,7 @@
/docs/ecosystem/notebooks/installation https://data.home-assistant.io
/docs/ecosystem/notebooks/stats https://data.home-assistant.io
/docs/frontend/mobile https://companion.home-assistant.io
+/docs/script/editor /docs/scripts/editor
/ecosystem/ios/notifications https://companion.home-assistant.io/docs/notifications/notifications-basic
/ecosystem/notebooks https://data.home-assistant.io
/ecosystem/notebooks/api https://data.home-assistant.io
@@ -2055,15 +2058,56 @@
/ecosystem/notebooks/installation https://data.home-assistant.io
/ecosystem/notebooks/stats https://data.home-assistant.io
/ios/whats-new https://companion.home-assistant.io/docs/getting_started/getting-started
+/integrations/auth /docs/authentication
/integrations/binary_sensor.knx /integrations/knx#binary-sensor
/integrations/climate.knx /integrations/knx#climate
/integrations/cover.knx /integrations/knx#cover
/integrations/light.knx /integrations/knx#light
/integrations/notify.knx /integrations/knx#notify
+/integrations/notify.mqtt /cookbook/notify.mqtt
/integrations/scene.knx /integrations/knx#scene
/integrations/sensor.knx /integrations/knx#sensor
/integrations/switch.knx /integrations/knx#switch
/integrations/weather.knx /integrations/knx#weather
+/integrations/zigbee /integrations/xbee
+/integrations/hassio /hassio
+/integrations/cloud.alexa /cloud/alexa
+/getting-started/automation-create-first /getting-started/automation
+/getting-started/automation-2 /getting-started/automation
+/getting-started/automation-action /docs/automation/action
+/getting-started/automation-condition /docs/automation/condition
+/getting-started/automation-examples /docs/automation/examples
+/getting-started/automation-troubleshooting /docs/automation/troubleshooting
+/getting-started/automation-trigger /docs/automation/trigger
+/getting-started/automation-templating /docs/automation/templating
+/getting-started/basic /docs/configuration/basic
+/getting-started/browsers /docs/frontend/browsers
+/getting-started/customizing-devices /docs/configuration/customizing-devices
+/getting-started/devices /docs/configuration/devices
+/getting-started/installation /docs/installation
+/getting-started/installation-docker /docs/installation/docker
+/getting-started/installation-virtualenv /docs/installation/virtualenv
+/getting-started/installation-raspberry-pi /docs/installation/raspberry-pi
+/getting-started/scripts /docs/scripts
+/getting-started/scripts-service-calls /docs/scripts/service-calls
+/getting-started/scripts-conditions /docs/scripts/conditions
+/getting-started/securing /docs/configuration/securing
+/getting-started/troubleshooting /docs/installation/troubleshooting
+/getting-started/troubleshooting-configuration /docs/configuration/troubleshooting
+/getting-started/updating /docs/installation/updating
+/getting-started/yaml /docs/configuration/yaml
+/getting-started/z-wave /docs/z-wave
+/getting-started/z-wave-devices /docs/z-wave/devices
+/getting-started/z-wave-installation /docs/z-wave/installation
+/getting-started/z-wave-panel /docs/z-wave/control-panel
+/getting-started/z-wave-device-specific /docs/z-wave/device-specific
+/topics/events /docs/configuration/events
+/topics/packages /docs/configuration/packages
+/topics/platform_options /docs/configuration/platform_options
+/topics/secrets /docs/configuration/secrets
+/topics/splitting_configuration /docs/configuration/splitting_configuration
+/topics/state_object /docs/configuration/state_object
+/topics/templating /docs/configuration/templating
# Migrated Community Guides
/cookbook/apache_configuration https://community.home-assistant.io/t/reverse-proxy-with-apache/196942
@@ -2133,6 +2177,7 @@
/lovelace/views /lovelace/dashboards-and-views
/lovelace/yaml-mode /lovelace/dashboards-and-views
/lovelace/calendar-card /lovelace/calendar
+/integrations/lovelace /lovelace
# Removed documentation
/docs/installation/hassbian /getting-started
@@ -2140,3 +2185,7 @@
/docs/installation/raspberry-pi-all-in-one /getting-started
/getting-started/hassbian /getting-started
/getting-started/installation-raspberry-pi-all-in-one /getting-started
+
+# Blog
+/blog/2019/05/29/release-94 /blog/2019/06/05/release-94
+/state-of-the-union /blog/2019/11/22/state-of-the-union
diff --git a/source/cloud/alexa.markdown b/source/cloud/alexa.markdown
index 269b0cd56b6..77cfe7a691b 100644
--- a/source/cloud/alexa.markdown
+++ b/source/cloud/alexa.markdown
@@ -2,8 +2,6 @@
title: "Alexa via Home Assistant Cloud"
description: "Enable the Alexa integration via Home Assistant Cloud integration."
sidebar: false
-redirect_from:
- - /integrations/cloud.alexa/
---
Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [the Nabu Casa website](https://www.nabucasa.com/config/amazon_alexa/) for help with the Amazon Alexa integration via Home Assistant Cloud.
diff --git a/source/code_of_conduct/index.markdown b/source/code_of_conduct/index.markdown
index 494e125502b..a4eaf2e2bc4 100644
--- a/source/code_of_conduct/index.markdown
+++ b/source/code_of_conduct/index.markdown
@@ -2,7 +2,6 @@
title: "Code of Conduct"
description: "The Code of Conduct for Home Assistant projects."
sidebar: false
-redirect_from: /developers/code_of_conduct/
---
## Our Pledge
@@ -22,23 +21,23 @@ diverse, inclusive, and healthy community.
Examples of behavior that contributes to a positive environment for our
community include:
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for us as individuals, but for the
overall community
Examples of unacceptable behavior include:
-* The use of sexualized language or imagery, and sexual attention or
+- The use of sexualized language or imagery, and sexual attention or
advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
professional setting
## Enforcement Responsibilities
@@ -112,7 +111,7 @@ Violating these terms may lead to a permanent ban.
### 4. Permanent Ban
**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
+standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
**Consequence**: A permanent ban from any sort of public interaction within
diff --git a/source/cookbook/index.markdown b/source/cookbook/index.markdown
index 0c34d0c036a..87a5bf0ac12 100644
--- a/source/cookbook/index.markdown
+++ b/source/cookbook/index.markdown
@@ -17,7 +17,7 @@ A great place to find popular configurations is on this
-[automation]: /getting-started/automation/
+[automations]: /getting-started/automation/
[github-search]: https://github.com/search?q=topic%3Ahome-assistant-config&type=Repositories
{% assign cookbook = site.cookbook | sort: 'title' %}
diff --git a/source/docs/index.markdown b/source/docs/index.markdown
index 23a0488faf8..f074423ba76 100644
--- a/source/docs/index.markdown
+++ b/source/docs/index.markdown
@@ -34,7 +34,7 @@ The documentation covers beginner to advanced topics around the installation, se
-
Lovelace user interface
+
User Interface
diff --git a/source/getting-started/automation.markdown b/source/getting-started/automation.markdown
index 3ccd5f801ff..67082f494f9 100644
--- a/source/getting-started/automation.markdown
+++ b/source/getting-started/automation.markdown
@@ -1,9 +1,6 @@
---
title: "Automating Home Assistant"
description: "A quick intro on getting your first automation going."
-redirect_from:
- - /getting-started/automation-create-first/
- - /getting-started/automation-2/
---
Once your devices are set up, it's time to put the cherry on the pie: automation. In this guide we're going to create a simple automation rule to **turn on the lights when the sun sets**.
diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown
index 40ee02b5aac..0c1860ba2bf 100644
--- a/source/getting-started/index.markdown
+++ b/source/getting-started/index.markdown
@@ -35,7 +35,7 @@ Follow this guide if you want to get started with Home Assistant easily or if yo
We will need a few things to get started with installing Home Assistant. The Raspberry Pi 4 Model B is a good, affordable starting point for your home automation journey. Links below lead to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country.
-- [Raspberry Pi 4 Model B (2GB)](https://amzn.to/2XULT2z) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A)
+- [Raspberry Pi 4 Model B (2GB)](https://amzn.to/2XULT2z) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 3A)
- [Micro SD Card](https://amzn.to/2X0Z2di). Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html) as they handle small I/O much more consistently than cards not optimized to host applications. A 32 GB or bigger card is recommended.
- SD Card reader. This is already part of most laptops, but you can purchase a [standalone USB adapter](https://amzn.to/2WWxntY) if you don't have one. The brand doesn't matter, just pick the cheapest.
- Ethernet cable. Home Assistant can work with Wi-Fi, but an Ethernet connection would be more reliable.
@@ -52,7 +52,7 @@ We will need a few things to get started with installing Home Assistant. The Ras
1. Put the SD card in your card reader.
2. Open balenaEtcher, select the Home Assistant image and flash it to the SD card.
3. Unmount the SD card and remove it from your card reader.
-4. The most reliable networking setup for your Raspberry Pi is to connect it using an Ethernet cable, however, if you want to configure Wi-Fi or a static IP address (this step requires a USB stick) you can try this:
+4. The most reliable networking setup for your Raspberry Pi is to connect it using an Ethernet cable; however, if you want to configure Wi-Fi or a static IP address (this step requires a USB stick) you can try this:
- Format a USB stick to FAT32 with the volume name `CONFIG`.
- Create a folder named `network` in the root of the newly-formatted USB stick.
- Within that folder, create a file named `my-network` without a file extension.
@@ -62,11 +62,17 @@ We will need a few things to get started with installing Home Assistant. The Ras
5. Insert the SD card into your Raspberry Pi. If you are going to use an Ethernet cable, connect that too.
6. Connect your power supply to the Raspberry Pi.
7. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes.
-8. Home Assistant will be available at `http://homeassistant.local:8123`. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at `http://homeassistant:8123` or `http://X.X.X.X:8123` (replace `X.X.X.X` with your Pi's IP address).
+8. On another computer, navigate to `http://homeassistant.local:8123` to access Home Assistant. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at `http://homeassistant:8123` or `http://X.X.X.X:8123` (replace `X.X.X.X` with your Pi's IP address).
9. If you used a USB stick for configuring the network, you can now remove it.
[the examples]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md
+
+
+ The Raspberry Pi will not show a user interface for Home Assistant if you connect a display. You need to use another computer to access Home Assistant.
+
+
+
### [Next step: Onboarding »][next-step]
[next-step]: /getting-started/onboarding/
diff --git a/source/hassio/index.markdown b/source/hassio/index.markdown
index 5241e043899..298110c7a08 100644
--- a/source/hassio/index.markdown
+++ b/source/hassio/index.markdown
@@ -1,7 +1,6 @@
---
title: "Home Assistant"
description: "Manage your Home Assistant and custom add-ons."
-redirect_from: /integrations/hassio/
---
Home Assistant turns your Raspberry Pi (or another device) into the ultimate home automation hub. With Home Assistant, you can focus on integrating your devices and writing automations.
@@ -32,14 +31,14 @@ Home Assistant users can update via the 'Supervisor' panel in the UI when a new
Home Assistant dashboard with upgrade notification (under the hamburger menu -> Supervisor)
-[Google Assistant]: /addons/google_assistant/
-[Snips.ai]: /addons/snips/
-[Let's Encrypt]: /addons/lets_encrypt/
-[Duck DNS]: /addons/duckdns/
+[google assistant]: /addons/google_assistant/
+[snips.ai]: /addons/snips/
+[let's encrypt]: /addons/lets_encrypt/
+[duck dns]: /addons/duckdns/
[forums]: https://community.home-assistant.io/c/hass-io
[comm-add-ons]: https://community.home-assistant.io/tags/hassio-repository
[all]: /addons/
[chat]: https://discord.gg/K3UVxJd
-[Home Assistant Operating System]: https://github.com/home-assistant/operating-system
-[Home Assistant Core]: https://www.home-assistant.io/docs/installation/
+[home assistant operating system]: https://github.com/home-assistant/operating-system
+[home assistant core]: https://www.home-assistant.io/docs/installation/
[install]: /hassio/installation/
diff --git a/source/help/index.markdown b/source/help/index.markdown
index a08c481ea9e..6d79663742d 100644
--- a/source/help/index.markdown
+++ b/source/help/index.markdown
@@ -42,7 +42,6 @@ Have you found an issue in your Home Assistant installation? Please report it. R
- [Building Online Communities: Home Assistant](https://medium.com/@gitter/building-online-communities-home-assistant-8818dff671ad#.och4x4rhx) - July 2016
- [Home Assistant Support 101 - Getting around in Home Assistant](https://www.youtube.com/watch?v=dRfk9JAlPJk) (Slides) - June 2016
- [Awaken your home: Python and the Internet of Things](https://www.youtube.com/watch?v=Cfasc9EgbMU&list=PLKsVm4cWHDQB9JBcD7_ZfNcvC6xx47QHT&index=1) at PyCon 2016 - June 2016
-- [Automating your Home with Home Assistant](https://www.youtube.com/watch?v=4-6rTwKl6ww&list=PLKsVm4cWHDQB9JBcD7_ZfNcvC6xx47QHT&index=2) at OpenIoT 2016 - March 2016
Looking for [talking points](/help/talking-points/) or [trivia](/help/trivia)?
diff --git a/source/images/blog/2020-10-01-hacktoberfest-2020/social.png b/source/images/blog/2020-10-01-hacktoberfest-2020/social.png
new file mode 100644
index 00000000000..6e6477aa3d9
Binary files /dev/null and b/source/images/blog/2020-10-01-hacktoberfest-2020/social.png differ
diff --git a/source/images/frontpage/hacktoberfest.png b/source/images/frontpage/hacktoberfest.png
new file mode 100644
index 00000000000..b8bc641a349
Binary files /dev/null and b/source/images/frontpage/hacktoberfest.png differ
diff --git a/source/index.html b/source/index.html
index 6c729f6dced..d7b2bde6832 100644
--- a/source/index.html
+++ b/source/index.html
@@ -5,7 +5,8 @@ hero_unit: true
is_homepage: true
regenerate: true
hide_github_edit: true
-description: Open source home automation that puts local control and privacy first.
+description:
+ Open source home automation that puts local control and privacy first.
---
@@ -35,6 +36,15 @@ description: Open source home automation that puts local control and privacy fir
+
Alexa, turn on the lights
Use Alexa to control Home Assistant.
@@ -107,7 +117,8 @@ description: Open source home automation that puts local control and privacy fir
href="/blog/2017/07/25/introducing-hassio/"
>
Learn how our OS can turn your Raspberry Pi into the ultimate home
- automation hub
+ automation hub
+
Home Assistant is sponsored by
@@ -197,32 +208,32 @@ description: Open source home automation that puts local control and privacy fir
diff --git a/source/lovelace/actions.markdown b/source/lovelace/actions.markdown
index fafba26b913..34592a1ac43 100644
--- a/source/lovelace/actions.markdown
+++ b/source/lovelace/actions.markdown
@@ -167,6 +167,10 @@ double_tap_action:
confirmation:
text: Are you sure you want to restart?
service: script.restart
+hold_action:
+ action: call-service
+ confirmation: true
+ service: script.do_other_thing
```
{% configuration confirmation%}
@@ -185,10 +189,21 @@ exemptions:
{% configuration exemptions %}
user:
required: true
- description: User id that can see the view tab.
+ description: User id that can see the view tab. For each user´s id listed, the confirmation dialog will NOT be shown.
type: string
{% endconfiguration %}
+```yaml
+double_tap_action:
+ action: call-service
+ confirmation:
+ text: Are you sure you want to restart?
+ exemptions:
+ - x9405b8c64ee49bb88c42000e0a9dfa8
+ - 88bcfbdc39155d16c3b2d09cbf8b0367
+ service: script.restart
+```
+
## Examples
Tap action implemented on an entity button card:
diff --git a/source/lovelace/dashboards-and-views.markdown b/source/lovelace/dashboards-and-views.markdown
index 49fb469c22b..1baafdb87be 100644
--- a/source/lovelace/dashboards-and-views.markdown
+++ b/source/lovelace/dashboards-and-views.markdown
@@ -5,7 +5,7 @@ description: "The Lovelace UI is a powerful and configurable interface for Home
You can define multiple dashboards in Lovelace. Each dashboard can be added to the sidebar. This makes it possible to create separate control dashboards for each individual part of your house.
-You can manage your dashboards via the user interface. Go to configuration -> Lovelace Dashboards. Here you can see all defined dashboards and create new ones.
+You can manage your dashboards via the user interface. Go to **Configuration** -> **Lovelace Dashboards**. Here you can see all defined dashboards and create new ones.
### Using YAML for the default dashboard
@@ -18,9 +18,9 @@ lovelace:
A good way to start this file is to copy and paste the "Raw configuration" from the UI so your manual configuration starts the same as your existing UI.
-- Go into the `Overview` tab.
-- Click the three dots menu (top-right) and click on `Configure UI`.
-- Click the three dots menu again and click on `Raw config editor`.
+- Click `Overview` in your sidebar.
+- Click the three dots menu (top-right) and click on `Edit Dashboard`.
+- Click the three dots menu again and click on `Raw configuration editor`.
- There you see the configuration for your current Lovelace UI. Copy that into the `
/ui-lovelace.yaml` file.
Once you take control of your UI via YAML, the Home Assistant interface for modifying it won't be available anymore and new entities will not automatically be added to your UI.
diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown
index bb8c7fa1350..ef7ab61eeef 100644
--- a/source/lovelace/index.markdown
+++ b/source/lovelace/index.markdown
@@ -1,8 +1,6 @@
---
title: "Lovelace"
description: "Lovelace is a powerful and configurable dashboard for Home Assistant."
-redirect_from:
- - /integrations/lovelace/
---
Lovelace is the Home Assistant dashboard. It's a fast, customizable and powerful way for users to manage their homes, working on mobile and desktop.
@@ -31,7 +29,7 @@ To try it yourself, check out [the demo](https://demo.home-assistant.io).
## Additional Lovelace Resources
-* [Awesome HA](https://www.awesome-ha.com/#lovelace-ui)
-* [Community Custom Cards](https://github.com/custom-cards)
-* [Home Assistant Cards](https://home-assistant-cards.bessarabov.com/)
-* [Material Design Icons](https://materialdesignicons.com/tag/community)
+- [Awesome HA](https://www.awesome-ha.com/#lovelace-ui)
+- [Community Custom Cards](https://github.com/custom-cards)
+- [Home Assistant Cards](https://home-assistant-cards.bessarabov.com/)
+- [Material Design Icons](https://materialdesignicons.com/tag/community)
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
- 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ src='/images/screenshots/nexus_7_dashboard.png' />
Example of a hub's dashboard. Showing the state of 2 persons, 4 lights and the sun.
+ src='/images/architecture/home_automation_landscape.png' />
Overview of the home automation landscape.
