-
-Screenshot of the Configurator.
-
-Consider running the configurator as a user with limited privileges to limit possible damage. -
- 
-
- 
-
- 
-
+ 
+ 
+ 
on generic Linux server
@@ -241,7 +245,7 @@ A better weekday condition could be by using the [Workday Binary Sensor](/integr
### Zone condition
-Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have set up a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
+Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have set up a device tracker platform that supports reporting GPS coordinates.
```yaml
condition:
diff --git a/source/_docs/tools/credstash.markdown b/source/_docs/tools/credstash.markdown
index cede4f23e0c..c696f102b87 100644
--- a/source/_docs/tools/credstash.markdown
+++ b/source/_docs/tools/credstash.markdown
@@ -5,7 +5,7 @@ description: "Script to store credentials securely in AWS"
Using [Credstash](https://github.com/fugue/credstash) is an alternative way to `secrets.yaml`. They can be managed from the command line via the credstash script.
-Before using credstash, you need to set up AWS credentials either via the `aws` command line tool or using environment variables as explained in the [AWS CLI docs](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) as well as creating a KMS key named `credstash` as explained in the [credstash Readme](https://github.com/fugue/credstash#setting-up-kms). After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash.
+Before using credstash, you need to set up AWS credentials either via the `aws` command line tool or using environment variables as explained in the [AWS CLI documentation](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) as well as creating a KMS key named `credstash` as explained in the [credstash Readme](https://github.com/fugue/credstash#setting-up-kms). After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash.
```bash
$ hass --script credstash --help
diff --git a/source/_docs/z-wave/devices.markdown b/source/_docs/z-wave/devices.markdown
index b8c79c760c3..94d36ff44ea 100644
--- a/source/_docs/z-wave/devices.markdown
+++ b/source/_docs/z-wave/devices.markdown
@@ -59,7 +59,7 @@ Where a device doesn't send updates on status changes to the controller, you can
For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic.
-Polling needs to be enabled per device, you can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details.
+Polling needs to be enabled per device, you can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) documentation for details.
## Central Scene support
diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown
index d8922f499a6..bfd703af5ea 100644
--- a/source/_docs/z-wave/installation.markdown
+++ b/source/_docs/z-wave/installation.markdown
@@ -123,7 +123,7 @@ You can also check what hardware has been found using the [`ha` command](/hassio
ha hardware info
```
-If you did an alternative install of Home Assistant on Linux (e.g. installing Ubuntu, then Docker, then Home Assistant Supervised) then the `modemmanager` package will interfere with any Z-Wave (or Zigbee) stick and should be removed or disabled in the host OS. Failure to do so will result in random failures of those components, e.g. dead or unreachable Z-Wave nodes, most notably right after Home Assistant restarts. Connect to your host OS via SSH, then you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager` (commands are for Debian/Ubuntu).
+If you did an alternative install of Home Assistant on Linux (e.g., installing Ubuntu, then Docker, then Home Assistant Supervised) then the `modemmanager` package will interfere with any Z-Wave (or Zigbee) stick and should be removed or disabled in the host OS. Failure to do so will result in random failures of those components, e.g., dead or unreachable Z-Wave nodes, most notably right after Home Assistant restarts. Connect to your host OS via SSH, then you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager` (commands are for Debian/Ubuntu).
### Docker
@@ -227,7 +227,7 @@ If this applies to your situation:
Then chances are high that the ModemManager in the host OS is causing the issue, claiming or interfering with the USB Z-Wave stick like the much used Aeotec ones. In this case you need to disable ModemManager.
-Connect to your host OS (e.g. Ubuntu) through SSH, then execute the following command on your host system to disable the ModemManager:
+Connect to your host OS (e.g., Ubuntu) through SSH, then execute the following command on your host system to disable the ModemManager:
```bash
systemctl disable ModemManager.service
diff --git a/source/_faq/missing-documentation.markdown b/source/_faq/missing-documentation.markdown
index cceaf744134..3c5e89e033f 100644
--- a/source/_faq/missing-documentation.markdown
+++ b/source/_faq/missing-documentation.markdown
@@ -1,6 +1,6 @@
---
title: "Missing Documentation"
-description: "The docs are missing or outdated"
+description: "The documentation is missing or outdated"
ha_category: Documentation
---
diff --git a/source/_includes/asides/component_navigation.html b/source/_includes/asides/component_navigation.html
index 66e78373bdd..853d4bacd33 100644
--- a/source/_includes/asides/component_navigation.html
+++ b/source/_includes/asides/component_navigation.html
@@ -1,20 +1,18 @@
-{%- assign github_main_repo = 'https://github.com/home-assistant/home-assistant/blob/dev/homeassistant' -%}
+ {%- else -%}
+ 
{%- endif -%}
-
-
- - {% active_link /docs/frontend/mobile/ Android/iOS Homescreen %} -
- {% active_link /docs/frontend/browsers/ Browser Compatibility List %} @@ -270,27 +267,6 @@
- {% active_link /docs/ecosystem/hadashboard/ HADashboard %} -
-
- {% active_link /docs/ecosystem/notebooks/ Notebooks %}
-
-
-
- {% active_link /docs/ecosystem/notebooks/ Introduction %} -
- - {% active_link /docs/ecosystem/notebooks/installation/ - Installation %} - -
- {% active_link /docs/ecosystem/notebooks/graph/ Graph %} -
- - {% active_link /docs/ecosystem/notebooks/api/ Home Assistant API - %} - -
- - {% active_link /docs/ecosystem/notebooks/database/ Database %} - -
- - {% active_link /docs/ecosystem/notebooks/stats/ Statistics %} - -
-
Remote access
-
@@ -342,10 +318,6 @@
- {% active_link /docs/ecosystem/synology/ Synology %} -
- - {% active_link /docs/ecosystem/hass-configurator/ Configurator - %} -
- 
+ 
@@ -41,9 +41,6 @@
-
diff --git a/source/_integrations/avea.markdown b/source/_integrations/avea.markdown index 91e303a981a..807f78f7512 100644 --- a/source/_integrations/avea.markdown +++ b/source/_integrations/avea.markdown @@ -8,6 +8,7 @@ ha_release: 0.97 ha_iot_class: Local Polling ha_codeowners: - '@pattyland' +ha_domain: avea --- [Elgato Avea](https://www.elgato.com/en/news/elgato-avea-transform-your-home) is a Bluetooth light bulb that is no longer supported by the manufacturer. The `avea` integration allows you to control all your Avea bulbs with Home Assistant. diff --git a/source/_integrations/avion.markdown b/source/_integrations/avion.markdown index 7e9df4e04c4..cce0ef0b77f 100644 --- a/source/_integrations/avion.markdown +++ b/source/_integrations/avion.markdown @@ -6,6 +6,7 @@ ha_category: ha_iot_class: Assumed State logo: avi-on.png ha_release: 0.37 +ha_domain: avion --- Support for the Avi-on Bluetooth dimmer switch [Avi-on](https://avi-on.com/). diff --git a/source/_integrations/awair.markdown b/source/_integrations/awair.markdown index 7d075fcb5b5..4c448eddce2 100644 --- a/source/_integrations/awair.markdown +++ b/source/_integrations/awair.markdown @@ -1,13 +1,13 @@ --- title: Awair description: Instructions on how to setup Awair devices in Home Assistant. -logo: awair.jpg ha_category: - Health ha_release: 0.84 ha_iot_class: Cloud Polling ha_codeowners: - '@danielsjf' +ha_domain: awair --- The `awair` sensor platform will fetch data from your [Awair device(s)](https://getawair.com). diff --git a/source/_integrations/aws.markdown b/source/_integrations/aws.markdown index b86c8792049..598d1424e99 100644 --- a/source/_integrations/aws.markdown +++ b/source/_integrations/aws.markdown @@ -1,13 +1,13 @@ --- title: Amazon Web Services (AWS) description: Instructions on how to integrate Amazon Web Services with Home Assistant. -logo: aws.png ha_category: - Notifications ha_release: '0.91' ha_codeowners: - '@awarecan' - '@robbiet480' +ha_domain: aws --- The `aws` integration provides a single place to interact with [Amazon Web Services](https://aws.amazon.com/). Currently it provides a notification platform that can send a message to [AWS SQS](https://aws.amazon.com/sqs/), [AWS SNS](https://aws.amazon.com/sns/), or invoke [AWS Lambda](https://aws.amazon.com/lambda/) functions. @@ -103,7 +103,7 @@ context: ## Lambda Notify Usage -AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke). +AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke). The Lambda event payload will contain everything passed in the service call payload. Here is an example payload that would be sent to Lambda: @@ -131,7 +131,7 @@ The context will look like this: ## SNS Notify Usage -AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish). +AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish). If one exists, the SNS Subject will be set to the title. All attributes from the payload, except the message, will be sent as stringified message attributes. @@ -157,7 +157,7 @@ If you do not download them, you will lose them and will have to recreate a new ## SQS Notify Usage -AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS docs](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message) +AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS documentation](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message) The SQS event payload will contain everything passed in the service call payload. SQS payloads will be published as stringified JSON. All attributes from the payload, except message, will also be sent as stringified message attributes. Here is an example message that would be published to the SQS queue: diff --git a/source/_integrations/axis.markdown b/source/_integrations/axis.markdown index 6b4befd53cd..4e296522c15 100644 --- a/source/_integrations/axis.markdown +++ b/source/_integrations/axis.markdown @@ -11,6 +11,7 @@ ha_release: 0.45 ha_iot_class: Local Push ha_codeowners: - '@kane610' +ha_domain: axis --- [Axis Communications](https://www.axis.com/) devices are surveillance cameras, speakers, access control and other security-related network connected hardware. Event API works with firmware 5.50 and newer. diff --git a/source/_integrations/azure_event_hub.markdown b/source/_integrations/azure_event_hub.markdown index b8994ad77c9..958be7981e9 100644 --- a/source/_integrations/azure_event_hub.markdown +++ b/source/_integrations/azure_event_hub.markdown @@ -1,12 +1,12 @@ --- title: Azure Event Hub description: Setup for Azure Event Hub integration -logo: azure_event_hub.svg ha_category: - History ha_release: 0.94 ha_codeowners: - '@eavanvalkenburg' +ha_domain: azure_event_hub --- The `Azure Event Hub` integration allows you to hook into the Home Assistant event bus and send events to [Azure Event Hub](https://azure.microsoft.com/en-us/services/event-hubs/) or to a [Azure IoT Hub](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-builtin). diff --git a/source/_integrations/azure_service_bus.markdown b/source/_integrations/azure_service_bus.markdown index 5c8d23d6dc7..0509c735a21 100644 --- a/source/_integrations/azure_service_bus.markdown +++ b/source/_integrations/azure_service_bus.markdown @@ -1,12 +1,12 @@ --- title: Azure Service Bus description: Setup for Azure Service Bus integration -logo: azure_service_bus.svg ha_category: - Notifications ha_release: 0.102 ha_codeowners: - '@hfurubotten' +ha_domain: azure_service_bus --- The `Azure Service Bus` integration allows you to send messages to [Azure Service Bus](https://azure.microsoft.com/en-us/services/service-bus/) from within Home Assistant. diff --git a/source/_integrations/baidu.markdown b/source/_integrations/baidu.markdown index b56b334b02a..cfec3e92b2e 100644 --- a/source/_integrations/baidu.markdown +++ b/source/_integrations/baidu.markdown @@ -5,6 +5,7 @@ logo: baiducloud.png ha_category: - Text-to-speech ha_release: 0.59 +ha_domain: baidu --- The `baidu` text-to-speech platform uses [Baidu TTS engine](https://cloud.baidu.com/product/speech/tts) to read a text with natural sounding voices. diff --git a/source/_integrations/bayesian.markdown b/source/_integrations/bayesian.markdown index 54868a6d3b6..89403363fd5 100644 --- a/source/_integrations/bayesian.markdown +++ b/source/_integrations/bayesian.markdown @@ -1,12 +1,12 @@ --- title: Bayesian description: Instructions on how to integrate threshold Bayesian sensors into Home Assistant. -logo: home-assistant.png ha_category: - Utility ha_iot_class: Local Polling ha_release: 0.53 ha_quality_scale: internal +ha_domain: bayesian --- The `bayesian` binary sensor platform observes the state from multiple sensors and uses [Bayes' rule](https://en.wikipedia.org/wiki/Bayes%27_theorem) to estimate the probability that an event has occurred given the state of the observed sensors. If the estimated posterior probability is above the `probability_threshold`, the sensor is `on` otherwise it is `off`. diff --git a/source/_integrations/bbb_gpio.markdown b/source/_integrations/bbb_gpio.markdown index 9585de1f001..eb2e89df87c 100644 --- a/source/_integrations/bbb_gpio.markdown +++ b/source/_integrations/bbb_gpio.markdown @@ -1,13 +1,13 @@ --- title: BeagleBone Black GPIO description: Instructions on how to integrate the GPIO capability of a BeagleBone Black into Home Assistant. -logo: beaglebone-black.png ha_category: - DIY - Binary Sensor - Switch ha_release: 0.36 ha_iot_class: Local Push +ha_domain: bbb_gpio --- The `bbb_gpio` integration is the base for all [BeagleBone Black](https://beagleboard.org/black) related GPIO platforms in Home Assistant. diff --git a/source/_integrations/bbox.markdown b/source/_integrations/bbox.markdown index 7378484c515..6cd532d0dcc 100644 --- a/source/_integrations/bbox.markdown +++ b/source/_integrations/bbox.markdown @@ -8,6 +8,7 @@ ha_category: - Presence Detection ha_release: 0.31 ha_iot_class: Local Polling +ha_domain: bbox --- The `bbox` platform uses the [Bbox Modem Router](https://www.bouyguestelecom.fr/offres-internet/bbox-fit) from the French Internet provider Bouygues Telecom. Sensors are mainly bandwidth measures. diff --git a/source/_integrations/beewi_smartclim.markdown b/source/_integrations/beewi_smartclim.markdown index 70a54b08ad0..6136b733834 100644 --- a/source/_integrations/beewi_smartclim.markdown +++ b/source/_integrations/beewi_smartclim.markdown @@ -1,13 +1,13 @@ --- title: BeeWi SmartClim BLE sensor description: Instructions on how to integrate MBeeWi SmartClim BLE sensor with Home Assistant. -logo: beewi_by_otio.png ha_category: - Sensor ha_release: 0.99 ha_iot_class: Local Polling ha_codeowners: - '@alemuro' +ha_domain: beewi_smartclim --- The `beewi_smartclim` sensor platform allows one to monitor room or external temperature and humidity. The [BeeWi SmartClim BLE](http://www.bee-wi.com/produits/capteurs/capteur-de-temperature/) is a Bluetooth Low Energy sensor device that monitors temperature from a room or a garden from your smartphone by using an APP. Use this integration to track these metrics from any location thanks to Home Assistant, as well as to create some automation scripts based on your room's temperature. diff --git a/source/_integrations/bh1750.markdown b/source/_integrations/bh1750.markdown index 2ba909f0806..bd8b56e819c 100644 --- a/source/_integrations/bh1750.markdown +++ b/source/_integrations/bh1750.markdown @@ -1,11 +1,11 @@ --- title: BH1750 description: Instructions on how to integrate a BH1750 light sensor into Home Assistant. -logo: raspberry-pi.png ha_category: - DIY ha_release: 0.48 ha_iot_class: Local Push +ha_domain: bh1750 --- The `bh1750` sensor platform allows you to read the ambient light level in Lux from a [BH1750FVI sensor](https://www.mouser.com/ds/2/348/bh1750fvi-e-186247.pdf) connected via [I2c](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). It allows you to use all the resolution modes of the sensor described in its datasheet. diff --git a/source/_integrations/binary_sensor.knx.markdown b/source/_integrations/binary_sensor.knx.markdown index 2818ad36a1b..89ceea46cb0 100644 --- a/source/_integrations/binary_sensor.knx.markdown +++ b/source/_integrations/binary_sensor.knx.markdown @@ -1,11 +1,11 @@ --- title: "KNX Binary Sensor" description: "Instructions on how to setup the KNX binary sensors within Home Assistant." -logo: knx.png ha_category: - Binary Sensor ha_release: 0.24 ha_iot_class: Local Push +ha_domain: knx ---
**Services**.
+
+
- 
+ 
- 
+ 
- 
-
@@ -65,7 +65,6 @@ logbook:
- sensor.date
domains:
- sun
- - weblink
```
In case you just want to see messages from some specific entities or domains use
diff --git a/source/_integrations/logentries.markdown b/source/_integrations/logentries.markdown
index bb4f4f7a4dc..ab62a2148df 100644
--- a/source/_integrations/logentries.markdown
+++ b/source/_integrations/logentries.markdown
@@ -1,10 +1,10 @@
---
title: Logentries
description: Send events to Logentries.
-logo: logentries.png
ha_category:
- History
ha_release: 0.13
+ha_domain: logentries
---
The `logentries` integration makes it possible to log all state changes to [Logentries](http://logentries.com/) using Logentries Webhook endpoint.
diff --git a/source/_integrations/logger.markdown b/source/_integrations/logger.markdown
index 38d2320776e..8bca5f4fcba 100644
--- a/source/_integrations/logger.markdown
+++ b/source/_integrations/logger.markdown
@@ -1,13 +1,13 @@
---
title: Logger
description: Instructions on how to enable the logger integration for Home Assistant.
-logo: home-assistant.png
ha_category:
- Utility
ha_release: 0.8
ha_quality_scale: internal
ha_codeowners:
- '@home-assistant/core'
+ha_domain: logger
---
The `logger` integration lets you define the level of logging activities in Home
diff --git a/source/_integrations/logi_circle.markdown b/source/_integrations/logi_circle.markdown
index d7612456f05..e252a8d592d 100644
--- a/source/_integrations/logi_circle.markdown
+++ b/source/_integrations/logi_circle.markdown
@@ -1,7 +1,6 @@
---
title: Logi Circle
description: Instructions on how to integrate your Logi Circle cameras within Home Assistant.
-logo: logi_circle.png
ha_category:
- Camera
- Sensor
@@ -10,6 +9,7 @@ ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@evanjd'
+ha_domain: logi_circle
---
The `logi_circle` implementation allows you to integrate your [Logi Circle](https://circle.logi.com/) cameras in Home Assistant. To connect Logi Circle, you will have to [sign up for API access](#requesting-api-access) and get a `client_id`, `client_secret` and `api_key`.
diff --git a/source/_integrations/london_air.markdown b/source/_integrations/london_air.markdown
index 9a011d0e5ca..a658cd136df 100644
--- a/source/_integrations/london_air.markdown
+++ b/source/_integrations/london_air.markdown
@@ -1,11 +1,11 @@
---
title: London Air
description: Display the current status of London air quality by area and pollution type.
-logo: waqi.png
ha_category:
- Health
ha_iot_class: Cloud Polling
ha_release: 0.52
+ha_domain: london_air
---
The `london_air` integration [queries](https://api.erg.kcl.ac.uk/AirQuality/Hourly/MonitoringIndex/GroupName=London/Json) the London air quality [data feed](https://www.londonair.org.uk/LondonAir/API/) provided by Kings College London. A single sensor will be added for each `location` ([local authority district or borough](https://en.wikipedia.org/wiki/List_of_London_boroughs)) specified in the configuration file. The state of each sensor is the overall air quality in that borough. Note that only 28 of the 32 boroughs have data available.
diff --git a/source/_integrations/london_underground.markdown b/source/_integrations/london_underground.markdown
index cb2e1ecdb23..fbbb898bafb 100644
--- a/source/_integrations/london_underground.markdown
+++ b/source/_integrations/london_underground.markdown
@@ -1,11 +1,11 @@
---
title: London Underground
description: Display the current status of London underground & overground lines within Home Assistant.
-logo: london_underground.png
ha_category:
- Transport
ha_iot_class: Cloud Polling
ha_release: 0.49
+ha_domain: london_underground
---
The `london_underground` sensor will display the status of London underground lines, as well as the Overground, DLR and Tfl rail.
diff --git a/source/_integrations/loopenergy.markdown b/source/_integrations/loopenergy.markdown
index c56d4ef8fb4..30fc4c5e7fe 100644
--- a/source/_integrations/loopenergy.markdown
+++ b/source/_integrations/loopenergy.markdown
@@ -1,11 +1,11 @@
---
title: Loop Energy
description: Instructions on how to integrate Loop Energy devices within Home Assistant.
-logo: loop.png
ha_category:
- Energy
ha_release: 0.17
ha_iot_class: Cloud Push
+ha_domain: loopenergy
---
Integrate your [Loop Energy](https://www.your-loop.com/) meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices.
diff --git a/source/_integrations/luci.markdown b/source/_integrations/luci.markdown
index 0b459c82500..61383e46d71 100644
--- a/source/_integrations/luci.markdown
+++ b/source/_integrations/luci.markdown
@@ -8,6 +8,7 @@ ha_release: pre 0.7
ha_codeowners:
- '@fbradyirl'
- '@mzdrale'
+ha_domain: luci
---
_This is one of multiple ways we support OpenWrt. For an overview, see [OpenWrt](/integrations/openwrt/)._
diff --git a/source/_integrations/luftdaten.markdown b/source/_integrations/luftdaten.markdown
index b6f46f8cb81..442b57fd1b6 100644
--- a/source/_integrations/luftdaten.markdown
+++ b/source/_integrations/luftdaten.markdown
@@ -1,7 +1,6 @@
---
title: Luftdaten
description: Instructions on how to setup Luftdaten sensors in Home Assistant.
-logo: luftdaten.png
ha_category:
- Health
- Sensor
@@ -11,6 +10,7 @@ ha_config_flow: true
ha_quality_scale: gold
ha_codeowners:
- '@fabaff'
+ha_domain: luftdaten
---
The `luftdaten` integration will query the open data API of [luftdaten.info](https://luftdaten.info/) to monitor air quality and other weather data from a specific (self build) sensor station.
diff --git a/source/_integrations/lupusec.markdown b/source/_integrations/lupusec.markdown
index fecabb37fce..86f9b84d3d8 100644
--- a/source/_integrations/lupusec.markdown
+++ b/source/_integrations/lupusec.markdown
@@ -11,6 +11,7 @@ ha_release: 0.83
ha_iot_class: Local Polling
ha_codeowners:
- '@majuss'
+ha_domain: lupusec
---
The `lupusec` integration allows the user to integrate their Lupusec alarm control panel and ultimately all connected sensors and other devices. For more information about the LUPUS-Electronics security system please visit their [website](https://www.lupus-electronics.de).
diff --git a/source/_integrations/lutron.markdown b/source/_integrations/lutron.markdown
index ae9988f9570..32237caff57 100644
--- a/source/_integrations/lutron.markdown
+++ b/source/_integrations/lutron.markdown
@@ -12,6 +12,7 @@ ha_release: 0.37
ha_iot_class: Local Polling
ha_codeowners:
- '@JonGilmore'
+ha_domain: lutron
---
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron` integration in Home Assistant is responsible for communicating with the main hub for these systems.
diff --git a/source/_integrations/lutron_caseta.markdown b/source/_integrations/lutron_caseta.markdown
index 3b35920e0f8..f087344f856 100644
--- a/source/_integrations/lutron_caseta.markdown
+++ b/source/_integrations/lutron_caseta.markdown
@@ -11,6 +11,7 @@ ha_category:
- Fan
ha_release: 0.41
ha_iot_class: Local Polling
+ha_domain: lutron_caseta
---
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](https://www.casetawireless.com/) product line of dimmers, switches and shades.
diff --git a/source/_integrations/lw12wifi.markdown b/source/_integrations/lw12wifi.markdown
index 3b1a10f1466..00baebaf9d6 100644
--- a/source/_integrations/lw12wifi.markdown
+++ b/source/_integrations/lw12wifi.markdown
@@ -6,6 +6,7 @@ ha_category:
ha_iot_class: Local Polling
logo: lagute.png
ha_release: 0.71
+ha_domain: lw12wifi
---
The `lw12wifi` light platform supports Lagute LW-12 Wifi LED controller.
diff --git a/source/_integrations/lyft.markdown b/source/_integrations/lyft.markdown
index 504e4174d27..afd295bd80c 100644
--- a/source/_integrations/lyft.markdown
+++ b/source/_integrations/lyft.markdown
@@ -1,11 +1,11 @@
---
title: Lyft
description: How to integrate Lyft in Home Assistant
-logo: lyft.png
ha_category:
- Transport
ha_iot_class: Cloud Polling
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/).
diff --git a/source/_integrations/magicseaweed.markdown b/source/_integrations/magicseaweed.markdown
index 5bd4da3446f..a1827e9ace7 100644
--- a/source/_integrations/magicseaweed.markdown
+++ b/source/_integrations/magicseaweed.markdown
@@ -6,6 +6,7 @@ ha_category:
- Sensor
ha_release: 0.75
ha_iot_class: Cloud Polling
+ha_domain: magicseaweed
---
The `magicseaweed` platform uses the [Magicseaweed Forecast API](https://magicseaweed.com/developer/forecast-api) as a source for surf forecasting data for the surf spots of your choice.
diff --git a/source/_integrations/mailbox.markdown b/source/_integrations/mailbox.markdown
index 5cf36250816..b59f062feb1 100644
--- a/source/_integrations/mailbox.markdown
+++ b/source/_integrations/mailbox.markdown
@@ -2,6 +2,7 @@
title: Mailbox
description: Instructions on how to setup your mailboxes with Home Assistant.
ha_release: 0.51
+ha_domain: mailbox
---
Mailboxes provide a list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend.
diff --git a/source/_integrations/mailgun.markdown b/source/_integrations/mailgun.markdown
index 97808d3cf9f..e4414ce9370 100644
--- a/source/_integrations/mailgun.markdown
+++ b/source/_integrations/mailgun.markdown
@@ -6,9 +6,10 @@ ha_category:
- Notifications
ha_release: 0.38
ha_config_flow: true
+ha_domain: mailgun
---
-To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([docs](/integrations/http/#base_url)).
+To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)).
To set it up, go to the integrations page in the configuration screen and find Mailgun. Click on configure. Follow the instructions on the screen to configure Mailgun.
diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown
index cea79d6c9f9..ed33d84527c 100644
--- a/source/_integrations/manual.markdown
+++ b/source/_integrations/manual.markdown
@@ -1,11 +1,11 @@
---
title: Manual
description: Instructions on how to integrate manual alarms into Home Assistant.
-logo: home-assistant.png
ha_category:
- Alarm
ha_release: 0.7.6
ha_quality_scale: internal
+ha_domain: manual
---
The `manual` alarm control panel platform enables you to set manual alarms in Home Assistant.
diff --git a/source/_integrations/manual_mqtt.markdown b/source/_integrations/manual_mqtt.markdown
index b73920ed819..89e89943fed 100644
--- a/source/_integrations/manual_mqtt.markdown
+++ b/source/_integrations/manual_mqtt.markdown
@@ -1,10 +1,10 @@
---
title: Manual MQTT
description: Instructions on how to integrate manual alarms into Home Assistant with MQTT support.
-logo: home-assistant.png
ha_category:
- Alarm
ha_release: '0.50'
+ha_domain: manual_mqtt
---
The `mqtt` platform extends the [manual alarm](/integrations/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
diff --git a/source/_integrations/map.markdown b/source/_integrations/map.markdown
index 98c8e62d986..33c096743c6 100644
--- a/source/_integrations/map.markdown
+++ b/source/_integrations/map.markdown
@@ -1,11 +1,11 @@
---
title: Map
description: Offers a map to show tracked devices.
-logo: home-assistant.png
ha_category:
- Other
ha_release: 0.56
ha_quality_scale: internal
+ha_domain: map
---
This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/integrations/device_tracker/) documentation. This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
@@ -18,3 +18,7 @@ map:
+The QVR Pro user must have Surveillance Management permission. +
diff --git a/source/_integrations/qwikswitch.markdown b/source/_integrations/qwikswitch.markdown index ebceff31cd5..aadfc1c54f9 100644 --- a/source/_integrations/qwikswitch.markdown +++ b/source/_integrations/qwikswitch.markdown @@ -11,6 +11,7 @@ ha_category: ha_release: '0.20' ha_codeowners: - '@kellerza' +ha_domain: qwikswitch --- The `qwikswitch` integration is the main integration to integrate various [QwikSwitch](https://www.qwikswitch.co.za/) devices with Home Assistant. The integration requires the QSUSB Modem device and connects to the QS Mobile application. @@ -48,7 +49,7 @@ button_events: default: TOGGLE,SCENE EXE,LEVEL type: string switches: - description: A list of device QS_id's that should be switches, and not lights (i.e. `['@0dev01', '@0dev02']`) + description: A list of device QS_id's that should be switches, and not lights (i.e., `['@0dev01', '@0dev02']`) required: false type: list sensors: diff --git a/source/_integrations/rachio.markdown b/source/_integrations/rachio.markdown index 9642ba9f698..469bfba989a 100644 --- a/source/_integrations/rachio.markdown +++ b/source/_integrations/rachio.markdown @@ -8,6 +8,7 @@ ha_category: - Switch ha_iot_class: Cloud Push ha_release: 0.73 +ha_domain: rachio --- The `rachio` platform allows you to control your [Rachio irrigation system](https://rachio.com/). diff --git a/source/_integrations/radarr.markdown b/source/_integrations/radarr.markdown index 91368831d8f..aca49c1bac8 100644 --- a/source/_integrations/radarr.markdown +++ b/source/_integrations/radarr.markdown @@ -1,10 +1,10 @@ --- title: Radarr description: Instructions on how to integrate Radarr sensors with Home Assistant -logo: radarr.png ha_category: - Downloading ha_release: 0.47 +ha_domain: radarr --- This `radarr` sensor platform pulls data from a given [Radarr](https://radarr.video/) instance. diff --git a/source/_integrations/radiotherm.markdown b/source/_integrations/radiotherm.markdown index c5f81b08bfe..3623c7fb3fb 100644 --- a/source/_integrations/radiotherm.markdown +++ b/source/_integrations/radiotherm.markdown @@ -6,6 +6,7 @@ ha_category: - Climate ha_iot_class: Local Polling ha_release: 0.7.6 +ha_domain: radiotherm --- The `radiotherm` climate platform let you control a thermostat from [Radio Thermostat](https://www.radiothermostat.com/) or [3M Filtrete](https://www.filtrete.com/). Your thermostat must have the Wi-Fi module installed and connected to your network. diff --git a/source/_integrations/rainbird.markdown b/source/_integrations/rainbird.markdown index 3bcda2c5109..6ed3cbdf444 100644 --- a/source/_integrations/rainbird.markdown +++ b/source/_integrations/rainbird.markdown @@ -10,6 +10,7 @@ ha_release: 0.61 ha_iot_class: Local Polling ha_codeowners: - '@konikvranik' +ha_domain: rainbird --- This `rainbird` integration allows interacting with [LNK WiFi](https://www.rainbird.com/products/lnk-wifi-module) module of the Rain Bird Irrigation system in Home Assistant. diff --git a/source/_integrations/raincloud.markdown b/source/_integrations/raincloud.markdown index 03be231d021..dcb6b3b5063 100644 --- a/source/_integrations/raincloud.markdown +++ b/source/_integrations/raincloud.markdown @@ -11,6 +11,7 @@ ha_release: 0.55 ha_iot_class: Cloud Polling ha_codeowners: - '@vanstinator' +ha_domain: raincloud --- The `raincloud` integration allows you to integrate your [Melnor RainCloud](https://wifiaquatimer.com) sprinkler system in Home Assistant. diff --git a/source/_integrations/rainforest_eagle.markdown b/source/_integrations/rainforest_eagle.markdown index 1ef1cc76d49..c6ebf9c7ecb 100644 --- a/source/_integrations/rainforest_eagle.markdown +++ b/source/_integrations/rainforest_eagle.markdown @@ -1,7 +1,6 @@ --- -title: "Rainforest Eagle" -description: "Instructions on how to setup the Rainforest Eagle with Home Assistant." -logo: rainforest_automation_logo.png +title: Rainforest Eagle-200 +description: Instructions on how to setup the Rainforest Eagle with Home Assistant. ha_category: - Energy - Sensor @@ -9,6 +8,8 @@ ha_release: 0.97 ha_iot_class: Local Polling ha_codeowners: - '@gtdiehl' + - '@jcalbert' +ha_domain: rainforest_eagle --- A `sensor` platform for the Rainforest Automation's [Eagle-200](https://rainforestautomation.com/rfa-z114-eagle-200/) diff --git a/source/_integrations/rainmachine.markdown b/source/_integrations/rainmachine.markdown index 6c0fe882932..318391070c4 100644 --- a/source/_integrations/rainmachine.markdown +++ b/source/_integrations/rainmachine.markdown @@ -1,7 +1,6 @@ --- title: RainMachine description: Instructions on how to integrate RainMachine units within Home Assistant. -logo: rainmachine.png ha_category: - Irrigation - Binary Sensor @@ -12,6 +11,7 @@ ha_iot_class: Local Polling ha_config_flow: true ha_codeowners: - '@bachya' +ha_domain: rainmachine --- The `rainmachine` integration is the main integration to integrate all platforms related to [RainMachine smart Wi-Fi sprinkler controllers](https://www.rainmachine.com/). diff --git a/source/_integrations/random.markdown b/source/_integrations/random.markdown index ca2ab90c4e1..ef708b1f7a2 100644 --- a/source/_integrations/random.markdown +++ b/source/_integrations/random.markdown @@ -1,7 +1,6 @@ --- title: Random description: Instructions on how to integrate random numbers into Home Assistant. -logo: home-assistant.png ha_category: - Utility - Sensor @@ -11,6 +10,7 @@ ha_release: 0.32 ha_quality_scale: internal ha_codeowners: - '@fabaff' +ha_domain: random --- The `random` integration simply creates random values or state. This can be useful if you want to test automation rules or run an interactive demo. It generates a new state every time it is polled. diff --git a/source/_integrations/raspihats.markdown b/source/_integrations/raspihats.markdown index eb22f0e719c..85f65646b80 100644 --- a/source/_integrations/raspihats.markdown +++ b/source/_integrations/raspihats.markdown @@ -8,6 +8,7 @@ ha_category: - Switch ha_release: 0.45 ha_iot_class: Local Push +ha_domain: raspihats --- The `raspihats` integration is the base for all related Raspihats platforms in Home Assistant. There is no setup needed for the integration itself. diff --git a/source/_integrations/raspyrfm.markdown b/source/_integrations/raspyrfm.markdown index 9d22260d7ca..c411791997f 100644 --- a/source/_integrations/raspyrfm.markdown +++ b/source/_integrations/raspyrfm.markdown @@ -6,6 +6,7 @@ ha_category: - Switch ha_release: 0.85 ha_iot_class: Assumed State +ha_domain: raspyrfm --- The `raspyrfm` integration adds support for cheap RC 433 MHz outlets via one of the supported gateways. diff --git a/source/_integrations/recollect_waste.markdown b/source/_integrations/recollect_waste.markdown index 06fc4da938d..3a7b7d92fe8 100644 --- a/source/_integrations/recollect_waste.markdown +++ b/source/_integrations/recollect_waste.markdown @@ -6,6 +6,7 @@ ha_category: - Sensor ha_release: 0.87 ha_iot_class: Cloud Polling +ha_domain: recollect_waste --- The `recollect_waste` integration allows you to track the next scheduled waste pickup and what type of waste from [Recollect](https://recollect.net/private-waste-haulers/). To use this sensor your city's waste company must be Recollect and you will need to find your place_id and service_id. diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 3292d62cb27..5396e2c1aeb 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -1,15 +1,21 @@ --- title: Recorder description: Instructions on how to configure the data recorder for Home Assistant. -logo: home-assistant.png ha_category: - History ha_release: pre 0.7 ha_quality_scale: internal +ha_domain: recorder --- The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` integration](/integrations/history/). ++The Avri sensor uses an unofficial API to obtain data. Use it at your own risk. +
diff --git a/source/_integrations/sensor.buienradar.markdown b/source/_integrations/sensor.buienradar.markdown index d9497a56a4f..6546f29fa36 100644 --- a/source/_integrations/sensor.buienradar.markdown +++ b/source/_integrations/sensor.buienradar.markdown @@ -6,6 +6,7 @@ ha_category: - Weather ha_release: 0.47 ha_iot_class: Cloud Polling +ha_domain: buienradar --- The `buienradar` platform uses [buienradar.nl](https://buienradar.nl/) as a source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands. The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weather stations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0). diff --git a/source/_integrations/sensor.command_line.markdown b/source/_integrations/sensor.command_line.markdown index fb5b2c78f72..90e908941e8 100644 --- a/source/_integrations/sensor.command_line.markdown +++ b/source/_integrations/sensor.command_line.markdown @@ -1,11 +1,11 @@ --- title: "Command line Sensor" description: "Instructions on how to integrate command line sensors into Home Assistant." -logo: command_line.png ha_category: - Utility ha_release: pre 0.7 ha_iot_class: Local Polling +ha_domain: command_line --- diff --git a/source/_integrations/sensor.ios.markdown b/source/_integrations/sensor.ios.markdown index d80d2198582..c3a766f6337 100644 --- a/source/_integrations/sensor.ios.markdown +++ b/source/_integrations/sensor.ios.markdown @@ -1,11 +1,11 @@ --- title: "iOS Sensor" description: "Instructions on how to use the iOS sensors with Home Assistant." -logo: apple.png ha_category: - Sensor ha_release: 0.31 ha_iot_class: Local Push +ha_domain: ios --- The `ios` sensor platform is the Home Assistant part for using the iOS companion app. For further details please check the [iOS section](/docs/ecosystem/ios/) in the documentation for further details. diff --git a/source/_integrations/sensor.knx.markdown b/source/_integrations/sensor.knx.markdown index c68015799d5..a60c3a0aa38 100644 --- a/source/_integrations/sensor.knx.markdown +++ b/source/_integrations/sensor.knx.markdown @@ -1,11 +1,11 @@ --- title: "KNX Sensor" description: "Instructions on how to use a KNX Sensor with Home Assistant." -logo: knx.png ha_category: - Sensor ha_release: 0.29 ha_iot_class: Local Push +ha_domain: knx ---
diff --git a/source/_lovelace/button.markdown b/source/_lovelace/button.markdown
index 2c06e57d49f..4250db8e1f2 100644
--- a/source/_lovelace/button.markdown
+++ b/source/_lovelace/button.markdown
@@ -1,7 +1,7 @@
---
title: "Button Card"
sidebar_label: Button
-description: "The Button card allows you to add buttons to perform tasks"
+description: "The Button card allows you to add buttons to perform tasks."
---
The Button card allows you to add buttons to perform tasks.
@@ -57,129 +57,22 @@ state_color:
default: true
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`toggle`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
theme:
required: false
description: "Set to any theme within `themes.yaml`"
type: string
{% endconfiguration %}
-## Options For Confirmation
-
-If you define confirmation as an object instead of boolean, you can add more customization and configurations:
-{% configuration %}
-text:
- required: false
- description: Text to present in the confirmation dialog.
- type: string
-exemptions:
- required: false
- description: "List of `exemption` objects. See below"
- type: list
-{% endconfiguration %}
-
## Options For Exemptions
{% configuration badges %}
diff --git a/source/_lovelace/conditional.markdown b/source/_lovelace/conditional.markdown
index ed3b6e9fff8..a82ba6c9212 100644
--- a/source/_lovelace/conditional.markdown
+++ b/source/_lovelace/conditional.markdown
@@ -1,10 +1,10 @@
---
title: Conditional Card
sidebar_label: Conditional
-description: Displays another card based on entity states.
+description: The Conditional card displays another card based on entity states.
---
-Displays another card based on entity states.
+The Conditional card displays another card based on entity states.
{% configuration %}
type:
diff --git a/source/_lovelace/entities.markdown b/source/_lovelace/entities.markdown
index 6931968a4fc..ddabf75f3c3 100644
--- a/source/_lovelace/entities.markdown
+++ b/source/_lovelace/entities.markdown
@@ -1,10 +1,10 @@
---
title: "Entities Card"
sidebar_label: Entities
-description: "Entities will be the most common type of card that will also be the most familiar to people using the standard interface. It groups items together very close to how groups used to do."
+description: "The Entities card is the most common type of card. It groups items together into lists."
---
-Entities will be the most common type of card that will also be the most familiar to people using the standard interface. It groups items together very close to how groups used to do.
+The Entities card is the most common type of card. It groups items together into lists.
{% configuration %}
type:
@@ -99,94 +99,16 @@ state_color:
default: false
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`toggle`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
{% endconfiguration %}
## Special Row Elements
diff --git a/source/_lovelace/entity-filter.markdown b/source/_lovelace/entity-filter.markdown
index 089930c171f..3f6e6da06e5 100644
--- a/source/_lovelace/entity-filter.markdown
+++ b/source/_lovelace/entity-filter.markdown
@@ -1,10 +1,10 @@
---
title: "Entity Filter Card"
sidebar_label: Entity Filter
-description: "This card allows you to define a list of entities that you want to track only when in a certain state. Very useful for showing lights that you forgot to turn off or show a list of people only when they're at home. "
+description: "The Entity Filter card allows you to define a list of entities that you want to track only when in a certain state. Very useful for showing lights that you forgot to turn off or show a list of people only when they're at home. "
---
-This card allows you to define a list of entities that you want to track only when in a certain state. Very useful for showing lights that you forgot to turn off or show a list of people only when they're at home.
+The Entity Filter card allows you to define a list of entities that you want to track only when in a certain state. Very useful for showing lights that you forgot to turn off or show a list of people only when they're at home.
This type of card can also be used together with rest of cards that allow multiple entities, allowing you to use [glance](/lovelace/glance/) or [picture-glance](/lovelace/picture-glance/). By default it uses [entities](/lovelace/entities/) card model.
diff --git a/source/_lovelace/gauge.markdown b/source/_lovelace/gauge.markdown
index 235b019ea73..4d0f362f1ac 100644
--- a/source/_lovelace/gauge.markdown
+++ b/source/_lovelace/gauge.markdown
@@ -1,10 +1,10 @@
---
title: "Gauge Card"
sidebar_label: Gauge
-description: "The Gauge card allows you to display sensor information visually"
+description: "The Gauge card is a basic card that allows visually seeing sensor data."
---
-Gauge card is a basic card that allows visually seeing sensor data.
+The Gauge card is a basic card that allows visually seeing sensor data.
diff --git a/source/_lovelace/glance.markdown b/source/_lovelace/glance.markdown
index 90d731e8278..45b808d4c9f 100644
--- a/source/_lovelace/glance.markdown
+++ b/source/_lovelace/glance.markdown
@@ -1,10 +1,10 @@
---
title: "Glance Card"
sidebar_label: Glance
-description: "The Glance card allows you to see a list of entities at a glance."
+description: "The Glance card is useful to group multiple sensors in a compact overview."
---
-Glance cards are very compact. Very useful to group together multiple sensors for a quick and easy overview. Keep in mind that this can be used together with [entity-filter](/lovelace/entity-filter/) cards to create dynamic cards.
+The Glance card is useful to group multiple sensors in a compact overview. Keep in mind that this can be used together with [entity-filter](/lovelace/entity-filter/) cards to create dynamic cards.
@@ -87,123 +87,16 @@ show_state:
default: true
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
-{% endconfiguration %}
-
-## Options For Confirmation
-
-If you define confirmation as an object instead of boolean, you can add more customization and configurations:
-{% configuration %}
-text:
- required: false
- description: Text to present in the confirmation dialog.
- type: string
-exemptions:
- required: false
- description: "List of `exemption` objects. See below"
- type: list
{% endconfiguration %}
## Options For Exemptions
diff --git a/source/_lovelace/history-graph.markdown b/source/_lovelace/history-graph.markdown
index 0ab31ec0ddf..04fa9819ced 100644
--- a/source/_lovelace/history-graph.markdown
+++ b/source/_lovelace/history-graph.markdown
@@ -1,10 +1,10 @@
---
title: "History Graph Card"
sidebar_label: History Graph
-description: "History graph is a basic card, allowing you to display a graph for each of the entities in the list specified as config."
+description: "The History Graph card allows you to display a graph for each of the entities listed."
---
-History graph is a basic card, allowing you to display a graph for each of the entities in the list specified configuration.
+The History Graph card allows you to display a graph for each of the entities listed.
-
+ A janky video of my 3d printed @home_assistant floorplan running @NervesProject on a @Raspberry_Pi pic.twitter.com/jrLyrR5TNO
diff --git a/source/_lovelace/horizontal-stack.markdown b/source/_lovelace/horizontal-stack.markdown
index 0c3c05a4581..4fc74ed3aa3 100644
--- a/source/_lovelace/horizontal-stack.markdown
+++ b/source/_lovelace/horizontal-stack.markdown
@@ -1,10 +1,10 @@
---
title: "Horizontal Stack Card"
sidebar_label: Horizontal Stack
-description: "Horizontal stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column."
+description: "The Horizontal Stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column."
---
-Horizontal stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column.
+The Horizontal Stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column.
{% configuration %}
type:
diff --git a/source/_lovelace/iframe.markdown b/source/_lovelace/iframe.markdown
index 332a08947f0..24db48ba9ee 100644
--- a/source/_lovelace/iframe.markdown
+++ b/source/_lovelace/iframe.markdown
@@ -1,18 +1,18 @@
---
-title: "Iframe Card"
-sidebar_label: Iframe
-description: "Embed data from other webservices in your dashboard."
+title: "Webpage Card"
+sidebar_label: Webpage
+description: "The Webpage card allows you to embed your favorite webpage right into Home Assistant."
---
-Embed data from other webservices in your dashboard. You can also embed files stored in your `
- Windy weather radar as iframe.
+
+ Windy weather radar as Webpage.
diff --git a/source/_lovelace/markdown.markdown b/source/_lovelace/markdown.markdown
index 4df04eaa741..d4eaa7a0feb 100644
--- a/source/_lovelace/markdown.markdown
+++ b/source/_lovelace/markdown.markdown
@@ -1,10 +1,10 @@
---
title: "Markdown Card"
sidebar_label: Markdown
-description: "Markdown card is used to render markdown"
+description: "The Markdown card is used to render Markdown"
---
-Markdown card is used to render [Markdown](https://commonmark.org/help/).
+The Markdown card is used to render [Markdown](https://commonmark.org/help/).
The renderer uses [Marked.js](https://marked.js.org), which supports [several specifications of Markdown](https://marked.js.org/#/README.md#specifications), including CommonMark, GitHub Flavored Markdown (GFM) and `markdown.pl`.
diff --git a/source/_lovelace/media-control.markdown b/source/_lovelace/media-control.markdown
index f3c7b961340..17378ed4012 100644
--- a/source/_lovelace/media-control.markdown
+++ b/source/_lovelace/media-control.markdown
@@ -1,10 +1,10 @@
---
title: "Media Control Card"
sidebar_label: Media Control
-description: "The media controller card is used to display Media Player entities on an interface with easy to use controls. "
+description: "The Media Control card is used to display media player entities on an interface with easy to use controls."
---
-The media control card is used to display [Media Player](/integrations/#search/media-player) entities on an interface with easy to use controls.
+The Media Control card is used to display [Media Player](/integrations/#search/media-player) entities on an interface with easy to use controls.
diff --git a/source/_lovelace/picture-elements.markdown b/source/_lovelace/picture-elements.markdown
index 4cb8999ead2..6de03f07d2c 100644
--- a/source/_lovelace/picture-elements.markdown
+++ b/source/_lovelace/picture-elements.markdown
@@ -1,10 +1,10 @@
---
title: "Picture Elements Card"
sidebar_label: Picture Elements
-description: "Picture elements card is one of the most versatile types of cards"
+description: "The Picture Elements card is one of the most versatile types of cards. The cards allow you to position icons or text and even services! On an image based on coordinates."
---
-Picture elements card is one of the most versatile types of cards.
+The Picture Elements card is one of the most versatile types of cards.
The cards allow you to position icons or text and even services! On an image based on coordinates. Imagine floor plan, imagine [picture-glance](/lovelace/picture-glance/) with no restrictions!
@@ -64,109 +64,16 @@ title:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`toggle`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
{% endconfiguration %}
### Icon representing an entity state
@@ -205,22 +112,22 @@ tap_action:
default: "`more-info`"
navigation_path:
required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
+ description: "Path to navigate to (e.g., `/lovelace/0/`) when `action` defined as `navigate`"
type: string
default: none
url_path:
required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
+ description: "Path to navigate to (e.g., `https://www.home-assistant.io`) when `action` defined as `url`"
type: string
default: none
service:
required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
+ description: "Service to call (e.g., `media_player.media_play_pause`) when `action` defined as `call-service`"
type: string
default: none
service_data:
required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
+ description: "Service data to include (e.g., `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
type: string
default: none
confirmation:
@@ -228,76 +135,18 @@ tap_action:
description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
type: [boolean, map]
default: "false"
+tap_action:
+ required: false
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
+ type: map
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
style:
required: true
description: Position and style the element using CSS.
@@ -330,109 +179,16 @@ title:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`,, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
style:
required: true
description: Position and style the element using CSS.
@@ -487,109 +243,16 @@ entity:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
style:
required: true
description: Position and style the element using CSS.
@@ -614,109 +277,16 @@ title:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
image:
required: false
description: The image to display.
@@ -786,20 +356,6 @@ elements:
type: list
{% endconfiguration %}
-## Options For Confirmation
-
-If you define confirmation as an object instead of boolean, you can add more customization and configurations:
-{% configuration %}
-text:
- required: false
- description: Text to present in the confirmation dialog.
- type: string
-exemptions:
- required: false
- description: "List of `exemption` objects. See below"
- type: list
-{% endconfiguration %}
-
## Options For Exemptions
{% configuration badges %}
@@ -824,7 +380,7 @@ style:
{% endconfiguration %}
The process for creating and referencing custom elements is the same as for custom cards.
-Please see the [developer docs on creating custom cards](https://developers.home-assistant.io/docs/en/lovelace_custom_card.html)
+Please see the [developer documentation](https://developers.home-assistant.io/docs/en/lovelace_custom_card.html)
for more information.
## How to use the style object
diff --git a/source/_lovelace/picture-entity.markdown b/source/_lovelace/picture-entity.markdown
index 5e989299daa..907e410501f 100644
--- a/source/_lovelace/picture-entity.markdown
+++ b/source/_lovelace/picture-entity.markdown
@@ -1,10 +1,10 @@
---
title: Picture Entity Card
sidebar_label: Picture Entity
-description: Displays the entity in form of an image. Instead of images from URL it can also show the picture of `camera` entities.
+description: The Picture Entity card displays an entity in the form of an image. Instead of images from URL, it can also show the picture of camera entities.
---
-Displays the entity in form of an image. Instead of images from URL it can also show the picture of `camera` entities.
+The Picture Entity card displays an entity in the form of an image. Instead of images from URL, it can also show the picture of `camera` entities.
@@ -65,123 +65,16 @@ theme:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
-{% endconfiguration %}
-
-## Options For Confirmation
-
-If you define confirmation as an object instead of boolean, you can add more customization and configurations:
-{% configuration %}
-text:
- required: false
- description: Text to present in the confirmation dialog.
- type: string
-exemptions:
- required: false
- description: "List of `exemption` objects. See below"
- type: list
{% endconfiguration %}
## Options For Exemptions
@@ -226,6 +119,7 @@ state_image:
Displaying a live feed from an FFmpeg camera:
{% raw %}
+
```yaml
type: picture-entity
entity: camera.backdoor
@@ -237,6 +131,7 @@ tap_action:
entity_id: camera.backdoor
filename: '/shared/backdoor-{{ now().strftime("%Y-%m-%d-%H%M%S") }}.jpg'
```
+
{% endraw %}
The filename needs to be a path that is writable by Home Assistant in your system. You may need to configure `whitelist_external_dirs` ([documentation](/docs/configuration/basic/)).
diff --git a/source/_lovelace/picture-glance.markdown b/source/_lovelace/picture-glance.markdown
index cf92f560d7a..b1f538974f4 100644
--- a/source/_lovelace/picture-glance.markdown
+++ b/source/_lovelace/picture-glance.markdown
@@ -1,10 +1,10 @@
---
title: "Picture Glance Card"
sidebar_label: Picture Glance
-description: "Show an image card and corresponding entity states as icon"
+description: "The Picture Glance card shows an image and corresponding entity states as an icon. The entities on the right side allow toggle actions, others show the more information dialog."
---
-Show an image card and corresponding entity states as icon. The entities on the right side allow toggle actions, others show the more-info-dialog.
+The Picture Glance card shows an image and corresponding entity states as an icon. The entities on the right side allow toggle actions, others show the more information dialog.
@@ -69,109 +69,16 @@ theme:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
{% endconfiguration %}
## Options For Entities
@@ -194,113 +101,16 @@ show_state:
default: true
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g., `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g., `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g., `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g., `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g., `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g., `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
-{% endconfiguration %}
-
-## Options For Confirmation
-
-If you define confirmation as an object instead of boolean, you can add more customization and configurations:
-{% configuration %}
-text:
- required: false
- description: Text to present in the confirmation dialog.
- type: string
-exemptions:
- required: false
- description: "List of `exemption` objects. See below"
- type: list
{% endconfiguration %}
## Options For Exemptions
diff --git a/source/_lovelace/picture.markdown b/source/_lovelace/picture.markdown
index 6a97fb0e5e4..c38959d6ca0 100644
--- a/source/_lovelace/picture.markdown
+++ b/source/_lovelace/picture.markdown
@@ -1,10 +1,10 @@
---
title: "Picture Card"
sidebar_label: Picture
-description: "A very simple card that allows you to set an image to use for navigation to various paths in your interface or to call a service."
+description: "The Picture card allows you to set an image to use for navigation to various paths in your interface or to call a service."
---
-A very simple card that allows you to set an image to use for navigation to various paths in your interface or to call a service.
+The Picture card allows you to set an image to use for navigation to various paths in your interface or to call a service.
@@ -26,123 +26,16 @@ theme:
type: string
tap_action:
required: false
- description: Action to take on tap
+ description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`none`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
hold_action:
required: false
- description: Action to take on tap-and-hold
+ description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`none`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
double_tap_action:
required: false
- description: Action to take on double tap
+ description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
type: map
- keys:
- action:
- required: true
- description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `url`, `none`)"
- type: string
- default: "`more-info`"
- navigation_path:
- required: false
- description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"
- type: string
- default: none
- url_path:
- required: false
- description: "Path to navigate to (e.g. `https://www.home-assistant.io`) when `action` defined as `url`"
- type: string
- default: none
- service:
- required: false
- description: "Service to call (e.g. `media_player.media_play_pause`) when `action` defined as `call-service`"
- type: string
- default: none
- service_data:
- required: false
- description: "Service data to include (e.g. `entity_id: media_player.bedroom`) when `action` defined as `call-service`"
- type: string
- default: none
- confirmation:
- required: false
- description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
- type: [boolean, map]
- default: "false"
-{% endconfiguration %}
-
-## Options For Confirmation
-
-If you define confirmation as an object instead of boolean, you can add more customization and configurations:
-{% configuration %}
-text:
- required: false
- description: Text to present in the confirmation dialog.
- type: string
-exemptions:
- required: false
- description: "List of `exemption` objects. See below"
- type: list
{% endconfiguration %}
## Options For Exemptions
diff --git a/source/_lovelace/plant-status.markdown b/source/_lovelace/plant-status.markdown
index 4a51516674a..221345752a1 100644
--- a/source/_lovelace/plant-status.markdown
+++ b/source/_lovelace/plant-status.markdown
@@ -1,10 +1,10 @@
---
title: "Plant Status Card"
sidebar_label: Plant Status
-description: "The Plant card gives you an easy way of viewing the status of your plants"
+description: "The Plant Status card is for all the lovely botanists out there."
---
-A card for all the lovely botanists out there.
+The Plant Status card is for all the lovely botanists out there.
diff --git a/source/_lovelace/sensor.markdown b/source/_lovelace/sensor.markdown
index d856949503d..d47eef1de3a 100644
--- a/source/_lovelace/sensor.markdown
+++ b/source/_lovelace/sensor.markdown
@@ -1,10 +1,10 @@
---
title: "Sensor Card"
sidebar_label: Sensor
-description: "The sensor card gives you information about the sensor state"
+description: "The Sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time."
---
-The sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time.
+The Sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time.
diff --git a/source/_lovelace/shopping-list.markdown b/source/_lovelace/shopping-list.markdown
index ac066ceb7a6..276128687cc 100644
--- a/source/_lovelace/shopping-list.markdown
+++ b/source/_lovelace/shopping-list.markdown
@@ -1,10 +1,10 @@
---
title: "Shopping List Card"
sidebar_label: Shopping List
-description: "The Shopping List Card allows you to add, edit, check-off, and clear items from your shopping list"
+description: "The Shopping List card allows you to add, edit, check-off, and clear items from your shopping list."
---
-The Shopping List Card allows you to add, edit, check-off, and clear items from your shopping list.
+The Shopping List card allows you to add, edit, check-off, and clear items from your shopping list.
Setup of the [Shopping List Intent](/integrations/shopping_list/) is required
diff --git a/source/_lovelace/thermostat.markdown b/source/_lovelace/thermostat.markdown
index 941092e775e..b56883fe984 100644
--- a/source/_lovelace/thermostat.markdown
+++ b/source/_lovelace/thermostat.markdown
@@ -1,10 +1,10 @@
---
title: "Thermostat Card"
sidebar_label: Thermostat
-description: "The thermostat card allows you to control a climate entity."
+description: "The Thermostat card gives control of your climate entity. Allowing you to change the temperature and mode of the entity."
---
-The thermostat card gives control of your climate entity.
+The Thermostat card gives control of your climate entity. Allowing you to change the temperature and mode of the entity.
diff --git a/source/_lovelace/vertical-stack.markdown b/source/_lovelace/vertical-stack.markdown
index c918c3cc4ef..6d12f2dc03c 100644
--- a/source/_lovelace/vertical-stack.markdown
+++ b/source/_lovelace/vertical-stack.markdown
@@ -1,10 +1,10 @@
---
title: "Vertical Stack Card"
sidebar_label: Vertical Stack
-description: "The Vertical Stack card allows you to stack multiple cards together"
+description: "The Vertical Stack card allows you to group multiple cards so they always sit in the same column."
---
-Vertical stack allows you to group multiple cards so they always sit in the same column.
+The Vertical Stack card allows you to group multiple cards so they always sit in the same column.
{% configuration %}
type:
diff --git a/source/_lovelace/weather-forecast.markdown b/source/_lovelace/weather-forecast.markdown
index 64354728c2e..5edc5aa6081 100644
--- a/source/_lovelace/weather-forecast.markdown
+++ b/source/_lovelace/weather-forecast.markdown
@@ -1,10 +1,10 @@
---
title: "Weather Forecast Card"
sidebar_label: Weather Forecast
-description: "The Weather card allows you a visual card to display the weather."
+description: "The Weather Forecast card displays the weather. Very useful to include on interfaces that people display on the wall."
---
-The weather forecast is a card to display the weather. Very useful to include on interfaces that people display on the wall.
+The Weather Forecast card displays the weather. Very useful to include on interfaces that people display on the wall.
diff --git a/source/_posts/2015-05-14-release-notes.markdown b/source/_posts/2015-05-14-release-notes.markdown
index 5fb47c858cc..e2009dd82a9 100644
--- a/source/_posts/2015-05-14-release-notes.markdown
+++ b/source/_posts/2015-05-14-release-notes.markdown
@@ -38,7 +38,7 @@ homeassistant:
```
__MySensors__
-
[Andythigpen](https://github.com/andythigpen) and [Theolind](https://github.com/theolind) have added support for the [MySensors platform](http://www.mysensors.org) to Home Assistant.
+
[Andythigpen](https://github.com/andythigpen) and [Theolind](https://github.com/theolind) have added support for the [MySensors platform](http://www.mysensors.org) to Home Assistant.
```yaml
# Example configuration.yaml entry
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 30c63dd2cdf..4fa16538b3d 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
@@ -15,7 +15,7 @@ We discovered two issues annoying enough to warrant the release of 0.7.5:
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))
diff --git a/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown b/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown
index b39db3f69e0..48d3b1e7e61 100644
--- a/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown
+++ b/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown
@@ -13,7 +13,7 @@ First release of 2016 and we are on 🔥! The [main repository][github-ha] has p
[github-ha]: https://github.com/home-assistant/home-assistant/
[release-pr]: https://github.com/home-assistant/home-assistant/pull/883#partial-users-participants
-
+
- [MySensors] revamped and switch support added ([@MartinHjelmare][@MartinHjelmare])
- Full refactor of RPi GPIO. Now includes [binary sensor][rpi-bs] and [switch][rpi-s] ([@sfam])
diff --git a/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown b/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown
index 35ea53dbe13..672fab2fc19 100644
--- a/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown
+++ b/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown
@@ -13,7 +13,7 @@ The focus of 0.13 was on test coverage, big cheers to [@rmkraus] for his hard wo
- Examples of the new [input_select] and [weblink] components.
+ Examples of the new [input_select] and weblink components.
@@ -134,6 +134,5 @@ weblink:
url: xxxx
```
-[weblink]: /integrations/weblink/
[snapcast]: /integrations/snapcast
[mpd]: /integrations/mpd
diff --git a/source/_posts/2016-05-21-release-020.markdown b/source/_posts/2016-05-21-release-020.markdown
index ab894fddc31..355de586afa 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-16-sqlalchemy-knx-join-simplisafe.markdown b/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
index 1881baaef42..39d7a4dd884 100644
--- a/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
+++ b/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
@@ -21,7 +21,7 @@ hass --script db_migrator --config /path/to/config
You can omit the `--config` option if you use the default configuration directory. Run the script with `--help` to get more options.
-
+
- Config: Improved support for storing [secrets][secrets] ([@kellerza])
- Sensor: Support for [Yahoo! Weather][yahoo-weather] ([@pvizeli])
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 79408404736..47d40348a43 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
@@ -12,7 +12,7 @@ It's time for 0.26 and it's again full of new features and fixes. First I want t
This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you'll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to [@Teagan42] for her hard work on this!
-
+
- Core: Introduce notion of unit system (deprecates temperature unit option) ([@Teagan42])
- Front end: Speed improvements ([@balloob])
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 8621f25ec01..ea14e2ea640 100644
--- a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
+++ b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
@@ -107,7 +107,7 @@ sensor
- Fix some html5 push notification configuration options were discarded after first use ([@T3m3z])
- Fix Homematic device name with autodiscovery ([@pvizeli])
- Make 'pin' optional for zigbee device config ([@flyte])
-- Fix when sending a notification to a service with target attached (i.e. `notify.html5_unnamed_device_2`) the target was not submitted to the platform as a list causing iteration over every character in the string. ([@robbiet480])
+- Fix when sending a notification to a service with target attached (i.e., `notify.html5_unnamed_device_2`) the target was not submitted to the platform as a list causing iteration over every character in the string. ([@robbiet480])
- Fix for Slack targets ([@fabaff])
- Fix for Pushover targets ([@Nixon506E])
diff --git a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
index e613bda7bc2..3f144e3cda6 100644
--- a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
+++ b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
@@ -28,7 +28,7 @@ For a long time we have had a bunch of [weather sensors][weather-sensors] but it
### All changes
-
+
- Cover: New [garadget] platform ([@JasonCarter80])
- Media player: New support for [Emby][emby-media] ([@mezz64])
diff --git a/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown b/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
index dda9b5bb667..deb6f410341 100644
--- a/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
+++ b/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
@@ -472,7 +472,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.tplink docs]: /integrations/tplink
[switch.wake_on_lan docs]: /integrations/wake_on_lan#switch
[switch.wemo docs]: /integrations/wemo
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[telegram_bot.polling docs]: /integrations/telegram_polling
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[tts.google docs]: /integrations/google_translate
@@ -493,7 +493,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[cover.zwave docs]: /integrations/zwave#cover
[recorder docs]: /integrations/recorder/
[switch.wemo docs]: /integrations/wemo
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[wemo docs]: /integrations/wemo/
[#7271]: https://github.com/home-assistant/home-assistant/pull/7271
diff --git a/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown b/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
index d67e2ddd53d..ea557720d74 100644
--- a/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
+++ b/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
@@ -486,7 +486,7 @@ influxdb:
[switch.thinkingcleaner docs]: /integrations/thinkingcleaner#switch
[switch.wemo docs]: /integrations/wemo
[switch.zha docs]: /integrations/zha
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[telegram_bot.polling docs]: /integrations/telegram_polling
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[updater docs]: /integrations/updater/
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 fd7684ca022..8bf09909cb9 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
@@ -413,9 +413,9 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.wunderground docs]: /integrations/wunderground
[sun docs]: /integrations/sun/
[switch.rpi_pfio docs]: /integrations/rpi_pfio#switch
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[telegram_bot.polling docs]: /integrations/telegram_polling
-[telegram_bot.services.yaml docs]: /integrations/telegram_chatbot/#notification-services
+[telegram_bot.services.yaml docs]: /integrations/telegram_bot/#notification-services
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[tradfri docs]: /integrations/tradfri/
[vera docs]: /integrations/vera/
@@ -434,5 +434,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_chatbot/
+[telegram_bot.__init__ 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 e9de42940d8..2f402e7a76b 100644
--- a/source/_posts/2017-06-04-release-46.markdown
+++ b/source/_posts/2017-06-04-release-46.markdown
@@ -369,7 +369,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.broadlink docs]: /integrations/broadlink#switch
[switch.rachio docs]: /integrations/rachio#switch
[switch.rflink docs]: /integrations/switch.rflink/
-[telegram_bot.__init__ docs]: /integrations/telegram_chatbot/
+[telegram_bot.__init__ docs]: /integrations/telegram_bot/
[telegram_bot.polling docs]: /integrations/telegram_polling
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[tellduslive docs]: /integrations/tellduslive/
diff --git a/source/_posts/2017-06-17-release-47.markdown b/source/_posts/2017-06-17-release-47.markdown
index af58001c4d2..a1463d5f2e7 100644
--- a/source/_posts/2017-06-17-release-47.markdown
+++ b/source/_posts/2017-06-17-release-47.markdown
@@ -547,7 +547,7 @@ automation:
[switch.raspihats docs]: /integrations/raspihats#switch
[switch.rest docs]: /integrations/switch.rest/
[switch.template docs]: /integrations/switch.template/
-[telegram_bot.__init__ docs]: /integrations/telegram_chatbot/
+[telegram_bot.__init__ docs]: /integrations/telegram_bot/
[telegram_bot.polling docs]: /integrations/telegram_polling
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[updater docs]: /integrations/updater/
diff --git a/source/_posts/2017-07-02-release-48.markdown b/source/_posts/2017-07-02-release-48.markdown
index e3d54c7e025..651d975d5fd 100644
--- a/source/_posts/2017-07-02-release-48.markdown
+++ b/source/_posts/2017-07-02-release-48.markdown
@@ -504,7 +504,7 @@ light:
[switch.verisure docs]: /integrations/verisure
[switch.wake_on_lan docs]: /integrations/wake_on_lan#switch
[tado docs]: /integrations/tado/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[telegram_bot.webhooks docs]: /integrations/telegram_webhooks
[tellduslive docs]: /integrations/tellduslive/
[tts docs]: /integrations/tts/
diff --git a/source/_posts/2017-07-16-release-49.markdown b/source/_posts/2017-07-16-release-49.markdown
index e7d2c1100b2..6f8201c8916 100644
--- a/source/_posts/2017-07-16-release-49.markdown
+++ b/source/_posts/2017-07-16-release-49.markdown
@@ -488,7 +488,7 @@ amcrest:
[@maikelwever]: https://github.com/maikelwever
[@ypollart]: https://github.com/ypollart
[binary_sensor.rfxtrx docs]: /integrations/binary_sensor.rfxtrx/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[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
[#8601]: https://github.com/home-assistant/home-assistant/pull/8601
diff --git a/source/_posts/2017-08-12-release-51.markdown b/source/_posts/2017-08-12-release-51.markdown
index 8ce4edd2269..76f8cd2fb65 100644
--- a/source/_posts/2017-08-12-release-51.markdown
+++ b/source/_posts/2017-08-12-release-51.markdown
@@ -442,7 +442,7 @@ vacuum:
[switch.rainmachine docs]: /integrations/rainmachine#switch
[switch.wink docs]: /integrations/wink#switch
[switch.xiaomi_vacuum docs]: /integrations/vacuum.xiaomi_miio/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[updater docs]: /integrations/updater/
[vacuum docs]: /integrations/vacuum/
[vacuum.demo docs]: /integrations/vacuum.demo/
diff --git a/source/_posts/2017-09-09-release-53.markdown b/source/_posts/2017-09-09-release-53.markdown
index 27abd107487..d0c05471051 100644
--- a/source/_posts/2017-09-09-release-53.markdown
+++ b/source/_posts/2017-09-09-release-53.markdown
@@ -439,7 +439,7 @@ frontend:
[switch.rest docs]: /integrations/switch.rest/
[switch.rfxtrx docs]: /integrations/switch.rfxtrx/
[switch.knx docs]: /integrations/switch.knx/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tesla docs]: /integrations/tesla/
[tradfri docs]: /integrations/tradfri/
[volvooncall docs]: /integrations/volvooncall/
diff --git a/source/_posts/2017-10-07-release-55.markdown b/source/_posts/2017-10-07-release-55.markdown
index 7d43e88825c..ef0742b215d 100644
--- a/source/_posts/2017-10-07-release-55.markdown
+++ b/source/_posts/2017-10-07-release-55.markdown
@@ -61,7 +61,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
## Breaking Changes
-- history_graph component: If your component used `history.get_significant_states` function then you need to adjust the string `entity_id` parameter has been changed to a list of strings `entity_ids` parameter. ([@andrey-git] - [#9472]) ([history_graph docs]) (breaking change)
+- history_graph component: If your component used `history.get_significant_states` function then you need to adjust the string `entity_id` parameter has been changed to a list of strings `entity_ids` parameter. ([@andrey-git] - [#9472]) (breaking change)
- UPNP component: The `external_port` configuration option was removed. ([@balloob] - [#9560]) ([upnp docs]) (breaking change)
- New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by "_" and no longer " ". ([@w1ll1am23] - [#9303]) ([wink docs]) ([binary_sensor.wink docs]) ([lock.wink docs]) (breaking change)
- TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. ([@djchen] - [#9607]) ([switch.tplink docs]) (breaking change)
@@ -383,7 +383,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
-[history_graph docs]: /integrations/history_graph/
[#9754]: https://github.com/home-assistant/home-assistant/pull/9754
[#9776]: https://github.com/home-assistant/home-assistant/pull/9776
[#9785]: https://github.com/home-assistant/home-assistant/pull/9785
diff --git a/source/_posts/2017-10-21-release-56.markdown b/source/_posts/2017-10-21-release-56.markdown
index fd8ac7e6a77..b25ba71446f 100644
--- a/source/_posts/2017-10-21-release-56.markdown
+++ b/source/_posts/2017-10-21-release-56.markdown
@@ -527,7 +527,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.tplink docs]: /integrations/tplink
[switch.wink docs]: /integrations/wink#switch
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tesla docs]: /integrations/tesla/
[toon docs]: /integrations/toon/
[tradfri docs]: /integrations/tradfri/
diff --git a/source/_posts/2017-11-18-release-58.markdown b/source/_posts/2017-11-18-release-58.markdown
index 23d5576758f..c95fc35b056 100644
--- a/source/_posts/2017-11-18-release-58.markdown
+++ b/source/_posts/2017-11-18-release-58.markdown
@@ -469,7 +469,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.snmp docs]: /integrations/snmp#switch
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
[system_log docs]: /integrations/system_log/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[telegram_bot.polling docs]: /integrations/telegram_polling
[tradfri docs]: /integrations/tradfri/
[tts docs]: /integrations/tts/
diff --git a/source/_posts/2017-12-17-release-60.markdown b/source/_posts/2017-12-17-release-60.markdown
index 6ec45d50acd..b4afdf02547 100644
--- a/source/_posts/2017-12-17-release-60.markdown
+++ b/source/_posts/2017-12-17-release-60.markdown
@@ -121,7 +121,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Added force_update for REST sensor ([@foxel] - [#11016]) ([sensor.miflora docs]) ([sensor.mqtt docs]) ([sensor.rest docs])
- Add support for Logitech UE Smart Radios. ([@GreenTurtwig] - [#10077]) ([media_player.ue_smart_radio docs]) (new-platform)
- Make notify.html5 depend on config ([@balloob] - [#11052]) ([notify.html5 docs])
-- This change fixes the error `OSError: [WinError 193]` on Windows debuggers (i.e. PyCharm) ([@tringler] - [#11034])
+- This change fixes the error `OSError: [WinError 193]` on Windows debuggers (i.e., PyCharm) ([@tringler] - [#11034])
- Added support for cover in tellstick ([@perfalk] - [#10858]) ([tellstick docs]) ([cover.tellstick docs]) (new-platform)
- Add a caldav calendar component ([@maxlaverse] - [#10842]) ([calendar.caldav docs]) (new-platform)
- Add GPS coords to meraki ([@addelovein] - [#10998]) ([device_tracker.meraki docs])
diff --git a/source/_posts/2018-01-14-release-61.markdown b/source/_posts/2018-01-14-release-61.markdown
index fba4b0fd1a8..eed5ed65952 100644
--- a/source/_posts/2018-01-14-release-61.markdown
+++ b/source/_posts/2018-01-14-release-61.markdown
@@ -760,7 +760,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
[switch.transmission docs]: /integrations/transmission
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
[tahoma docs]: /integrations/tahoma/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[timer docs]: /integrations/timer/
[tts.baidu docs]: /integrations/baidu
[tts.marytts docs]: /integrations/marytts
diff --git a/source/_posts/2018-02-10-release-63.markdown b/source/_posts/2018-02-10-release-63.markdown
index dcf388d94af..0eaafb14648 100644
--- a/source/_posts/2018-02-10-release-63.markdown
+++ b/source/_posts/2018-02-10-release-63.markdown
@@ -127,7 +127,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Map media_stop to idle state ([@akloeckner] - [#11819])
- Adds allergy/disease sensor platform from Pollen.com ([@bachya] - [#11573]) ([sensor.pollen docs]) (new-platform)
- check_config.py: allow colorlog==3.1. ([@dotlambda] - [#11927])
-- Weblink - Allow relative urls in config ([@ReneNulschDE] - [#11808]) ([weblink docs])
+- Weblink - Allow relative urls in config ([@ReneNulschDE] - [#11808])
- Panel_Iframe - Allow relative urls in config ([@ReneNulschDE] - [#11832]) ([panel_iframe docs])
- Python 3.6 invalid escape sequence deprecation fixes ([@scop] - [#11941])
- tests: Use assertEqual instead of deprecated assertEquals ([@scop] - [#11943])
@@ -622,7 +622,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[wake_on_lan docs]: /integrations/wake_on_lan/
[waterfurnace docs]: /integrations/waterfurnace/
[weather.openweathermap docs]: /integrations/openweathermap#weather
-[weblink docs]: /integrations/weblink/
[websocket_api docs]: /integrations/websocket_api/
[zha docs]: /integrations/zha/
[zha.const docs]: /integrations/zha.const/
diff --git a/source/_posts/2018-02-26-release-64.markdown b/source/_posts/2018-02-26-release-64.markdown
index 72a5c8cff7e..e58b5fcdeae 100644
--- a/source/_posts/2018-02-26-release-64.markdown
+++ b/source/_posts/2018-02-26-release-64.markdown
@@ -139,7 +139,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- check_config check bootstrap errors ([@kellerza] - [#12291])
- Attempt fixing flakiness of check config test ([@balloob] - [#12283])
- Fix MQTT retained message not being re-dispatched ([@OttoWinter] - [#12004]) ([mqtt docs])
-- Fix config error for FTP links, add test ([@ReneNulschDE] - [#12294]) ([weblink docs])
+- Fix config error for FTP links, add test ([@ReneNulschDE] - [#12294])
- Fix Panel_IFrame - FTP URL not allowed in 0.63 ([@ReneNulschDE] - [#12295]) ([panel_iframe docs])
- Upgrade pylint to 1.8.2 ([@OttoWinter] - [#12274])
- Move HassIntent handler code into helpers/intent ([@tschmidty69] - [#12181]) ([conversation docs])
@@ -576,11 +576,10 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.smappee docs]: /integrations/smappee
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
[tahoma docs]: /integrations/tahoma/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[vacuum.xiaomi_miio docs]: /integrations/vacuum.xiaomi_miio/
[vera docs]: /integrations/vera/
[weather.buienradar docs]: /integrations/buienradar
-[weblink docs]: /integrations/weblink/
[xiaomi_aqara docs]: /integrations/xiaomi_aqara/
[zha docs]: /integrations/zha/
[#12635]: https://github.com/home-assistant/home-assistant/pull/12635
diff --git a/source/_posts/2018-03-30-release-66.markdown b/source/_posts/2018-03-30-release-66.markdown
index bf0ec721ad6..939ae2a063f 100644
--- a/source/_posts/2018-03-30-release-66.markdown
+++ b/source/_posts/2018-03-30-release-66.markdown
@@ -550,7 +550,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.vesync docs]: /integrations/vesync#switches
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
[switch.zha docs]: /integrations/zha
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[upcloud docs]: /integrations/upcloud/
[vacuum.xiaomi_miio docs]: /integrations/vacuum.xiaomi_miio/
[weather.darksky docs]: /integrations/weather.darksky/
diff --git a/source/_posts/2018-05-18-release-70.markdown b/source/_posts/2018-05-18-release-70.markdown
index 1fde7339710..60cd476658b 100644
--- a/source/_posts/2018-05-18-release-70.markdown
+++ b/source/_posts/2018-05-18-release-70.markdown
@@ -432,7 +432,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.tahoma docs]: /integrations/tahoma
[system_log docs]: /integrations/system_log/
[tahoma docs]: /integrations/tahoma/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tts docs]: /integrations/tts/
[updater docs]: /integrations/updater/
[weather.bom docs]: /integrations/bom
diff --git a/source/_posts/2018-06-10-release-71.markdown b/source/_posts/2018-06-10-release-71.markdown
index 83443597398..ab53fcad357 100644
--- a/source/_posts/2018-06-10-release-71.markdown
+++ b/source/_posts/2018-06-10-release-71.markdown
@@ -56,7 +56,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- BOM sensor: `'Wind Direction kt'` to `'Wind Speed kt'` (fixes #14535) ([@fabaff] - [#14541]) ([sensor.bom docs]) (breaking change)
- Removed attribute current_time from Raincloudy sensors to avoid being triggered by recorder component ([@tchellomello] - [#14584]) ([raincloud docs]) ([switch.raincloud docs]) (breaking change)
- Remove Notify My Android component as it shut down on May 24 ([@cgarwood] - [#14594]) ([notify docs]) (breaking change)
-- CoinMarketCap sensor: It is no longer possible to query a ticker by the name of the currency (i.e. bitcoin). The API instead uses IDs (integers) for these tickers (i.e. bitcoin -> 1). Rounding of decimals is now configurable, because it made no sense to round to 2 decimals if display_currency was set to BTC, some values showed up as 0.00. (#14437) ([@kotlarz] - [#14604]) ([sensor.coinmarketcap docs]) (breaking change)
+- CoinMarketCap sensor: It is no longer possible to query a ticker by the name of the currency (i.e., bitcoin). The API instead uses IDs (integers) for these tickers (i.e., bitcoin -> 1). Rounding of decimals is now configurable, because it made no sense to round to 2 decimals if display_currency was set to BTC, some values showed up as 0.00. (#14437) ([@kotlarz] - [#14604]) ([sensor.coinmarketcap docs]) (breaking change)
- Give unknown zwave nodes a better name and don't add them to entity registry ([@andrey-git] - [#14353]) ([zwave docs]) (breaking change)
- The `netdata` sensor was re-worked to support all available details from [Netdata](https://my-netdata.io/). This requires you to adjust the your existing configuration if you use the `netdata` sensor.
([@fabaff] - [#14613]) ([sensor.netdata docs]) (breaking change)
diff --git a/source/_posts/2018-09-15-release-78.markdown b/source/_posts/2018-09-15-release-78.markdown
index 92655fe1979..ddebd0a075c 100644
--- a/source/_posts/2018-09-15-release-78.markdown
+++ b/source/_posts/2018-09-15-release-78.markdown
@@ -480,7 +480,7 @@ The configuration value type should no longer be used. ([@endor-force] - [#15935
[switch.tahoma docs]: /integrations/tahoma
[switch.tplink docs]: /integrations/tplink
[tahoma docs]: /integrations/tahoma/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tts docs]: /integrations/tts/
[upnp docs]: /integrations/upnp/
[vacuum docs]: /integrations/vacuum/
diff --git a/source/_posts/2018-10-12-release-80.markdown b/source/_posts/2018-10-12-release-80.markdown
index fa54d4a3f93..4351081033e 100644
--- a/source/_posts/2018-10-12-release-80.markdown
+++ b/source/_posts/2018-10-12-release-80.markdown
@@ -80,7 +80,7 @@ On the devices side, we got basic support for the new IKEA TRÅDFRI switches, Ho
[camera.blink docs]: /integrations/blink
[cloud docs]: /integrations/cloud/
[sensor.blink docs]: /integrations/blink
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
## Release 0.80.3 - October 18
@@ -709,7 +709,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.tradfri docs]: /integrations/tradfri
[switch.volvooncall docs]: /integrations/volvooncall
[switch.xiaomi_aqara docs]: /integrations/switch.xiaomi_aqara/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tibber docs]: /integrations/tibber/
[timer docs]: /integrations/timer/
[tradfri docs]: /integrations/tradfri/
diff --git a/source/_posts/2018-10-29-release-81.markdown b/source/_posts/2018-10-29-release-81.markdown
index 8ac74a3bdb7..17466e657ec 100644
--- a/source/_posts/2018-10-29-release-81.markdown
+++ b/source/_posts/2018-10-29-release-81.markdown
@@ -843,7 +843,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.xiaomi_aqara docs]: /integrations/switch.xiaomi_aqara/
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
[switch.zwave docs]: /integrations/zwave
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tts docs]: /integrations/tts/
[twilio docs]: /integrations/twilio/
[unifi docs]: /integrations/unifi/
diff --git a/source/_posts/2018-11-08-release-82.markdown b/source/_posts/2018-11-08-release-82.markdown
index cdc29a83f86..1f95b61a1a3 100644
--- a/source/_posts/2018-11-08-release-82.markdown
+++ b/source/_posts/2018-11-08-release-82.markdown
@@ -678,7 +678,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.xiaomi_aqara docs]: /integrations/switch.xiaomi_aqara/
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/
[switch.zigbee docs]: /integrations/zigbee#switch
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tts docs]: /integrations/tts/
[twilio docs]: /integrations/twilio/
[updater docs]: /integrations/updater/
diff --git a/source/_posts/2019-03-13-release-89.markdown b/source/_posts/2019-03-13-release-89.markdown
index 906e336ab93..d407e4730cc 100644
--- a/source/_posts/2019-03-13-release-89.markdown
+++ b/source/_posts/2019-03-13-release-89.markdown
@@ -713,7 +713,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.tplink docs]: /integrations/tplink
[system_log docs]: /integrations/system_log/
[tahoma docs]: /integrations/tahoma/
-[telegram_bot docs]: /integrations/telegram_chatbot/
+[telegram_bot docs]: /integrations/telegram_bot/
[tellduslive docs]: /integrations/tellduslive/
[tibber docs]: /integrations/tibber/
[toon docs]: /integrations/toon/
diff --git a/source/_posts/2019-04-03-release-91.markdown b/source/_posts/2019-04-03-release-91.markdown
index 7e6886ff03f..907e0548259 100644
--- a/source/_posts/2019-04-03-release-91.markdown
+++ b/source/_posts/2019-04-03-release-91.markdown
@@ -210,7 +210,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- __Axis__ - Events supplied from component might differ. Events will not be configurable in the beginning but will instead provide a subset set of events supported per device. This will be configurable in a later stage when config entry options are available. Configuration.yaml support for Axis component will be removed in the future so make sure to remove references to Axis component after upgrade. ([@Kane610] - [#18543]) ([axis docs])
- __HTTP__ - Lower severity level of log messages from http.view ([@thomasloven] - [#21091]) ([http docs])
- __Dark Sky__ - Dark Sky provides hourly forecasts for various monitored conditions. This change creates new sensors for each hourly forecasted condition with suffix `_
+
+In December 2019, an outbreak of a novel [Coronavirus](https://en.wikipedia.org/wiki/Coronavirus)
+also called severe acute respiratory syndrome coronavirus-2
+([SARS-CoV-2](https://en.wikipedia.org/wiki/Severe_acute_respiratory_syndrome_coronavirus_2)),
+began in the Wuhan region of China. This virus can cause the
+[COVID-19](https://en.wikipedia.org/wiki/Coronavirus_disease_2019) disease.
+
+This novel Coronavirus is spreading globally at a disturbing rate, which keeps
+everybody on top of the news. The media worldwide is covering the spread of
+the virus constantly, and a lot of people are tracking the number of cases
+in their country.
+
+This special release adds the [Coronavirus integration](/integrations/coronavirus),
+allowing you to track the outbreak from within Home Assistant.
+
+## The Coronavirus integration
+
+While having a meeting at [Nabu Casa](https://www.nabucasa.com/),
+we caught ourselves talking a lot about the state of the virus spreading in
+the countries we live in. Which brought us to the subject of being able to
+track the virus in Home Assistant itself.
+
+So together, we started working on an integration right away. We decided to
+bring you a special release of Home Assistant that includes this integration.
+
+The Coronavirus integration tracks the number of people that are confirmed with,
+recovered from, and deceased caused by the virus in your country, or worldwide.
+
+The data is sourced from the [Johns Hopkins University](https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6).
+
+
+Screenshot of the Coronavirus integration in Home Assistant.
+
+
+### Getting started with your own 3D floorplan
+
+Ok, so the above two, rather impressive, listings might be a bit out of reach
+for the most of us. Still, with some help, you could still achieve some pretty
+nice looking 3D floorplans. [Aaron Godfrey](https://github.com/boralyl) wrote a
+couple of excellent blog posts on this.
+
+In his [first blog post](https://aarongodfrey.dev/home%20automation/floorplan-in-home-assistant/),
+Aaron shows you what his floorplan looks like
+
+
+
+This is a result of a 3D floorplan created with [HomeByMe](https://home.by.me/en/).
+
+It works fully in the browser and I enjoyed the experience using that.
+So credits where credits due: Thanks for recommending me this sweet little
+gem [Andrea Donno](https://www.twitter.com/andreadonno)!
+
+## Got a tip for the next edition?
+
+Have you seen (or made) something awesome, interesting, unique, amazing, inspirational, unusual or funny, using Home Assistant?
+
+[Click here to send us your Community Highlight suggestion](/suggest-community-highlight).
+
+Also, don't forget to share your creations with us via Social Media:
+
+- Twitter it! Be sure to mention [@home_assistant][twitter]
+- Share it on our [Facebook group][facebook-group]
+- Post it to our [subreddit][reddit]
+- Tag [@homeasssistant][instagram] on Instagram
+- Or via chat, drop us a line in the [#lounge at Discord][chat]
+
+See you next edition!
+
+[chat]: https://www.home-assistant.io/join-chat
+[facebook-group]: https://www.facebook.com/groups/HomeAssistant/
+[instagram]: https://www.instagram.com/homeassistant/
+[reddit]: https://www.reddit.com/r/homeassistant
+[twitter]: https://www.twitter.com/home_assistant
diff --git a/source/_redirects b/source/_redirects
index 85c6100244f..321aa5292db 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -373,7 +373,6 @@
/components/device_tracker.unifi_direct /integrations/unifi_direct
/components/device_tracker.upc_connect /integrations/upc_connect
/components/device_tracker.volvooncall /integrations/volvooncall
-/components/device_tracker.xfinity /integrations/xfinity
/components/device_tracker.xiaomi_miio /integrations/xiaomi_miio
/components/fan.comfoconnect /integrations/comfoconnect
/components/fan.dyson /integrations/dyson#fan
@@ -1420,7 +1419,6 @@
/components/hikvision /integrations/hikvision
/components/hikvisioncam /integrations/hikvisioncam
/components/history /integrations/history
-/components/history_graph /integrations/history_graph
/components/history_stats /integrations/history_stats
/components/hitron_coda /integrations/hitron_coda
/components/hive /integrations/hive
@@ -1887,7 +1885,7 @@
/components/ted5000 /integrations/ted5000
/components/teksavvy /integrations/teksavvy
/components/telegram /integrations/telegram
-/components/telegram_bot /integrations/telegram_chatbot
+/components/telegram_bot /integrations/telegram_bot
/components/tellduslive /integrations/tellduslive
/components/tellstick /integrations/tellstick
/components/telnet /integrations/telnet
@@ -1989,7 +1987,6 @@
/components/weather.darksky /integrations/weather.darksky
/components/webhook /integrations/webhook
/components/webhooks /integrations/telegram_webhooks
-/components/weblink /integrations/weblink
/components/webostv /integrations/webostv
/components/websocket_api /integrations/websocket_api
/components/wemo /integrations/wemo
@@ -2008,7 +2005,6 @@
/components/x10 /integrations/x10
/components/xbox_live /integrations/xbox_live
/components/xeoma /integrations/xeoma
-/components/xfinity /integrations/xfinity
/components/xiaomi /integrations/xiaomi
/components/xiaomi_aqara /integrations/xiaomi_aqara
/components/xiaomi_miio /integrations/xiaomi_miio
@@ -2040,9 +2036,9 @@
# Breaking changes
/integrations/switch.pca /integrations/elv
+/integrations/telegram_chatbot /integrations/telegram_bot
-# App documentation
-/ios/whats-new https://companion.home-assistant.io/docs/getting_started/getting-started
+# Moved documentation
/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
@@ -2056,7 +2052,21 @@
/docs/ecosystem/ios/notifications/privacy_security_rate_limits https://companion.home-assistant.io/docs/notifications/notifications-basic
/docs/ecosystem/ios/notifications/requesting_location_updates https://companion.home-assistant.io/docs/notifications/notifications-basic
/docs/ecosystem/ios/notifications/sounds https://companion.home-assistant.io/docs/notifications/notification-sounds
+/docs/ecosystem/notebooks https://data.home-assistant.io
+/docs/ecosystem/notebooks/api https://data.home-assistant.io
+/docs/ecosystem/notebooks/database https://data.home-assistant.io
+/docs/ecosystem/notebooks/graph https://data.home-assistant.io
+/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
/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
+/ecosystem/notebooks/database https://data.home-assistant.io
+/ecosystem/notebooks/graph https://data.home-assistant.io
+/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
# Add-ons
/addons/cec_scan https://github.com/home-assistant/hassio-addons/blob/master/cec_scan/README.md
diff --git a/source/cloud/index.markdown b/source/cloud/index.markdown
index a16af21ad7c..b172af08f5a 100644
--- a/source/cloud/index.markdown
+++ b/source/cloud/index.markdown
@@ -2,10 +2,10 @@
title: "Home Assistant Cloud"
description: "Enable the Home Assistant Cloud integration."
sidebar: false
-logo: home-assistant.png
ha_release: "0.60"
ha_category: Voice
ha_iot_class: Cloud Push
+ha_domain: cloud
---
Home Assistant Cloud is a subscription service provided by our partner Nabu Casa, Inc. Check out [their website](https://www.nabucasa.com) for more information on features, pricing and [how to configure Home Assistant](https://www.nabucasa.com/config/).
diff --git a/source/docs/index.markdown b/source/docs/index.markdown
index 8d2a4446926..489af81e433 100644
--- a/source/docs/index.markdown
+++ b/source/docs/index.markdown
@@ -8,7 +8,7 @@ The documentation covers beginner to advanced topics around the installation, se
+
+ 
+ 
+
-From the Hass.io main panel, open the add-on store.
+From the Supervisor main panel, open the add-on store.
[Browse the forums »][forums]
[Join the Home Assistant chat »][chat]
[Browse community add-on repositories »][comm-add-ons]
';
} else {
return '