diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown
index 364bc1572f6..e5e42f02a38 100644
--- a/source/_docs/mqtt/broker.markdown
+++ b/source/_docs/mqtt/broker.markdown
@@ -78,7 +78,7 @@ If you are running a Mosquitto instance on a different server with proper SSL en
### Public broker
-The Mosquitto project runs a [public broker](http://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices or controlling your home.
+The Mosquitto project runs a [public broker](https://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices or controlling your home.
```yaml
mqtt:
@@ -88,7 +88,7 @@ mqtt:
# Optional, replace port 1883 with following if you want encryption
# (doesn't really matter because broker is public)
port: 8883
- # Download certificate from http://test.mosquitto.org/ssl/mosquitto.org.crt
+ # Download certificate from https://test.mosquitto.org/ssl/mosquitto.org.crt
certificate: /home/paulus/downloads/mosquitto.org.crt
```
diff --git a/source/_docs/mqtt/logging.markdown b/source/_docs/mqtt/logging.markdown
index 87e937effea..ef77050610a 100644
--- a/source/_docs/mqtt/logging.markdown
+++ b/source/_docs/mqtt/logging.markdown
@@ -13,4 +13,3 @@ logger:
logs:
homeassistant.components.mqtt: debug
```
-
diff --git a/source/_docs/mqtt/service.markdown b/source/_docs/mqtt/service.markdown
index 130ff59e469..f80d37297c7 100644
--- a/source/_docs/mqtt/service.markdown
+++ b/source/_docs/mqtt/service.markdown
@@ -6,7 +6,7 @@ logo: mqtt.png
The MQTT integration will register the service `mqtt.publish` which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/topics/templating/) that will be rendered to generate the payload.
-### Service `mqtt.publish`
+## Service `mqtt.publish`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
@@ -26,10 +26,12 @@ payload: on
```
{% raw %}
+
```yaml
topic: home-assistant/light/1/state
payload_template: "{{ states('device_tracker.paulus') }}"
```
+
{% endraw %}
`payload` must be a string. If you want to send JSON then you need to format/escape it properly. Like:
diff --git a/source/_docs/mqtt/testing.markdown b/source/_docs/mqtt/testing.markdown
index 0c7bd51ced2..6a26d86159d 100644
--- a/source/_docs/mqtt/testing.markdown
+++ b/source/_docs/mqtt/testing.markdown
@@ -4,7 +4,7 @@ description: "Instructions on how to test your MQTT setup."
logo: mqtt.png
---
-The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below:
+The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](https://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](https://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below:
```bash
mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown
index 4635f680a68..9a991597106 100644
--- a/source/_docs/scripts.markdown
+++ b/source/_docs/scripts.markdown
@@ -75,6 +75,39 @@ The variables action allows you to set/override variables that will be accessibl
{% endraw %}
+### Scope of Variables
+
+Variables have local scope. This means that if a variable is changed in a nested sequence block, that change will not be visible in an outer sequence block.
+
+The following example will always say "There are 0 people home". Inside the `choose` sequence the `variables` action will only alter the `people` variable for that sequence.
+
+{% raw %}
+
+```yaml
+sequence:
+ # Set the people variable to a default value
+ - variables:
+ people: 0
+ # Try to increment people if Paulus is home
+ - choose:
+ - conditions:
+ - condition: state
+ entity_id: device_tracker.paulus
+ state: "home"
+ sequence:
+ # At this scope and this point of the sequence, people == 0
+ - variables:
+ people: "{{ people + 1 }}"
+ # At this scope, people will now be 1 ...
+ # ... but at this scope it will still be 0
+ # Announce the count of people home
+ - service: notify.notify
+ data:
+ message: "There are {{ people }} people home"
+```
+
+{% endraw %}
+
## Test a Condition
While executing a script you can add a condition in the main sequence to stop further execution. When a condition does not return `true`, the script will stop executing. There are many different conditions which are documented at the [conditions page].
@@ -161,7 +194,7 @@ The template is re-evaluated whenever an entity ID that it references changes st
### Wait for Trigger
-This action can use the same triggers that are available in an automation's `trigger` section. See [Automation Trigger](/docs/automation/trigger). The script will continue whenever any of the triggers fires. All previously defined [trigger_variables](/docs/automation/trigger#trigger_variables), [variables](#variables) and [script variables] are passed to the trigger.
+This action can use the same triggers that are available in an automation's `trigger` section. See [Automation Trigger](/docs/automation/trigger). The script will continue whenever any of the triggers fires. All previously defined [trigger variables](/docs/automation/trigger#trigger-variables), [variables](#variables) and [script variables] are passed to the trigger.
{% raw %}
```yaml
diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown
index f1de345d3bb..8167a02c335 100644
--- a/source/_docs/tools/dev-tools.markdown
+++ b/source/_docs/tools/dev-tools.markdown
@@ -110,4 +110,4 @@ The Template Editor provides a way to quickly test templates prior to placing th
By default this will contain sample code that illustrates how templates can be written and tested. This sample code can be removed and replaced with your own. You can restore the default example by pressing the "Reset to Demo Template" button beneath the code editor.
-For more information about Jinja2, visit [Jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/).
+For more information about Jinja2, visit [Jinja2 documentation](https://jinja.palletsprojects.com/templates/), and also read templating document [here](/topics/templating/).
diff --git a/source/_docs/z-wave/control-panel.markdown b/source/_docs/z-wave/control-panel.markdown
index 8d53023c1b2..8d71fd04d54 100644
--- a/source/_docs/z-wave/control-panel.markdown
+++ b/source/_docs/z-wave/control-panel.markdown
@@ -144,7 +144,7 @@ If your node has user codes, you can set and delete them. The format is raw hex
\x39 = 9
```
Some non compliant device like tag readers, have implemented to use raw hex code.
-Please refer to a hex ASCII table to set your code. Example: http://www.asciitable.com/
+Please refer to a hex ASCII table to set your code. Example: https://www.asciitable.com/
Here is a small Python program than will take numbers on the command line and print the correct sequence for compliant devices:
diff --git a/source/_includes/common-tasks/data_disk.md b/source/_includes/common-tasks/data_disk.md
new file mode 100644
index 00000000000..0cc4189c0d7
--- /dev/null
+++ b/source/_includes/common-tasks/data_disk.md
@@ -0,0 +1,66 @@
+## Using external Data Disk
+
+Home Assistant Operating System supports storing most data on an external storage medium (e.g. USB attached SSD or HDD). This data disk contains not only user data but also most of the Home Assistant software as well (Core, Supervisor etc.). This means a fast data disk will make the system overall much faster.
+
+
+
+The data disk feature can be used on an existing installation without losing data: The system will move existing data to the external data disk automatically. However, it is recommended to create and download a full
Backup before proceeding!
+
+
+
+ All data on the target disk will be overwritten!
+
+
+
+
+
+ The storage capacity of the external data disk must be larger than the storage capacity of the existing (boot) disk.
+
+
+
+
+
+ If you have been using a data disk previously with Home Assistant Operating System, you need to use your host computer to delete all partitions *before* using it as a data disk again.
+
+
+
+### Using UI to move the data partition
+
+1. Connect the data disk to your system.
+2. Go to **{% my supervisor_info title="Supervisor >> System" %}** in the UI.
+3. Press the three dots on the bottom right of the Host card and choose "Move datadisk"
+4. Select the data disk from the list of available devices.
+5. Press "Move".
+
+
+
+### Using CLI to move the data partition
+
+To see the current data disk use:
+
+```sh
+$ ha os info
+...
+data_disk: /dev/mmcblk1p4
+...
+```
+
+To getting a list of supported detected devices which can be used by `datadisk`:
+
+```sh
+ha os datadisk list
+```
+
+To initiate the move to the new data disk use the `move` command:
+
+```sh
+ha os datadisk move /dev/sdx
+```
+
+The system will prepare the data disk and immediately reboot. The reboot will take 10 minutes or more depending on the speed of the new data disk; please be patient!
+
+
+
+Using an USB attached SSD can draw quite some power. For instance on Raspberry Pi 3 the official Raspberry Pi power supply (PSU) only provides 2.5A which can be too tight. Use a more powerful power supply if you experience issues. Alternatively use a powered USB hub. Connect the Hub to one of the USB slots of your Raspberry Pi, and connect the SSD to the Hub. In this setup the power supply of the Hub will power the attached device(s).
+
+
diff --git a/source/_includes/common-tasks/development_version.md b/source/_includes/common-tasks/development_version.md
index 96cde097ae7..a163cdd5269 100644
--- a/source/_includes/common-tasks/development_version.md
+++ b/source/_includes/common-tasks/development_version.md
@@ -53,7 +53,7 @@ docker pull {{ site.installation.container.base }}:dev
3. Download and install the version you want
```bash
- pip3 install --upgrade git+git://github.com/home-assistant/core.git@dev
+ pip3 install --upgrade git+https://github.com/home-assistant/core.git@dev
```
4. When that is complete restart the service for it to use the new files.
diff --git a/source/_includes/installation/container/alternative.md b/source/_includes/installation/container/alternative.md
index ec9aa89e7e7..f62d55ec85b 100644
--- a/source/_includes/installation/container/alternative.md
+++ b/source/_includes/installation/container/alternative.md
@@ -15,7 +15,7 @@ The steps would be:
- Set "Enable auto-restart" if you like
- Within "Volume" click on "Add Folder" and choose either an existing folder or add a new folder. The "mount path" has to be "/config", so that Home Assistant will use it for the configs and logs. It is therefore recommended that the folder you choose should be named "config" or "homeassistant/config" to avoid confusion when referencing it within service calls.
- Within "Network" select "Use same network as Docker Host"
-- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
+- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
- Confirm the "Advanced Settings"
- Click on "Next" and then "Apply"
- Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Synology NAS IP address - for example `http://192.168.1.10:8123`)
@@ -37,7 +37,7 @@ Adjust the following Terminal command as follows :
- Replace `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration
- Replace `/PATH_TO_YOUR_USB_STICK` matches the path for your USB stick (e.g., `/dev/ttyACM0` for most Synology users)
-- Replace "Australia/Melbourne" with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
+- Replace "Australia/Melbourne" with [your timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
Run it in Terminal.
@@ -83,7 +83,7 @@ The steps would be:
- Click on "Advanced Settings"
- Within "Shared Folders" click on "Volume from host" > "Add" and choose either an existing folder or add a new folder. The "mount point has to be `/config`, so that Home Assistant will use it for the configuration and logs.
- Within "Network" and select Network Mode to "Host"
-- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
+- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
- Click on "Create"
- Wait for some time until your NAS has created the container
- Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Qnap NAS IP address - for example `http://192.xxx.xxx.xxx:8123`)
diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md
index 7fb69b791e7..87d3385479d 100644
--- a/source/_includes/installation/operating_system.md
+++ b/source/_includes/installation/operating_system.md
@@ -87,7 +87,7 @@ If you prefer to use a live operating system, follow the instructions of your Li
{% endif %}
2. Download and start
Balena Etcher
3. Select "Flash from URL"
-
+
4. Get the URL for your {{site.installation.types[page.installation_type].board}}:
{% if site.installation.types[page.installation_type].variants.size > 1 %}
@@ -121,15 +121,15 @@ If you prefer to use a live operating system, follow the instructions of your Li
_Select and copy the URL or use the "copy" button that appear when you hover it._
1. Paste the URL for your {{site.installation.types[page.installation_type].board}} into Balena Etcher and click "OK"
-
+
6. Balena Etcher will now download the image, when that is done click "Select target"
-
+
7. Select the {{site.installation.types[page.installation_type].installation_media}} you want to use for your {{site.installation.types[page.installation_type].board}}
-
+
8. Click on "Flash!" to start writing the image
-
+
9. When Balena Etcher is finished writing the image you will get this confirmation
-
+
### Start up your {{site.installation.types[page.installation_type].board}}
diff --git a/source/_integrations/airthings.markdown b/source/_integrations/airthings.markdown
index 6cc79412233..cf7da18d164 100644
--- a/source/_integrations/airthings.markdown
+++ b/source/_integrations/airthings.markdown
@@ -4,7 +4,7 @@ description: Instructions on how to integrate Airthings into Home Assistant.
ha_category:
- Sensor
- Environment
-ha_release: 2021.10
+ha_release: '2021.10'
ha_iot_class: Cloud Polling
ha_codeowners:
- '@danielhiversen'
@@ -16,9 +16,9 @@ ha_platforms:
Integrates Airthings sensors into Home Assistant.
-[Airthings](https://www.airthings.com/) provide different sensors for meassuring the air quality. The focus specially on Radon sensors.
+[Airthings](https://www.airthings.com/) provide different sensors for measuring the air quality. The focus specially on Radon sensors.
-Login [here](https://dashboard.airthings.com/integrations/api-integration) to find your credentials
+Login [here](https://dashboard.airthings.com/integrations/api-integration) to find your credentials.
{% include integrations/config_flow.md %}
diff --git a/source/_integrations/amberelectric.markdown b/source/_integrations/amberelectric.markdown
index 45b5494da8c..e4686310f3a 100644
--- a/source/_integrations/amberelectric.markdown
+++ b/source/_integrations/amberelectric.markdown
@@ -4,13 +4,14 @@ description: Instructions on how to integrate Amber Electric live prices within
ha_category:
- Sensor
- Energy
-ha_release: "2021.10"
+ha_release: '2021.10'
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- - "@madpilot"
+ - '@madpilot'
ha_domain: amberelectric
ha_platforms:
+ - binary_sensor
- sensor
---
diff --git a/source/_integrations/analytics.markdown b/source/_integrations/analytics.markdown
index cddcd7ba759..34ca991779c 100644
--- a/source/_integrations/analytics.markdown
+++ b/source/_integrations/analytics.markdown
@@ -20,7 +20,7 @@ Home Assistant allows users to share their usage data via the analytics integrat
The information sent depends on what options you opt-in to. You can opt-in during onboarding and by going to **{% my general title="Configuration >> General" %}** .
-**{% my general badge %}**
+{% my general badge %}
When enabled, data will be sent 15 minutes after each start, and every 24h after startup. Sent data is printed to your log.
@@ -74,7 +74,7 @@ This includes:
- The names of all your core integrations
- The names and versions of all your custom integrations if you have any
-- Boolean to indicate that the [`energy` integration](/integrations/energy) is configured
+- Boolean to indicate that the [energy integration](/integrations/energy) is configured
If your system includes the Supervisor, this will also contain:
diff --git a/source/_integrations/aurora_abb_powerone.markdown b/source/_integrations/aurora_abb_powerone.markdown
index 0752dce0833..e0ab3265ead 100644
--- a/source/_integrations/aurora_abb_powerone.markdown
+++ b/source/_integrations/aurora_abb_powerone.markdown
@@ -13,17 +13,17 @@ ha_platforms:
- sensor
---
-This implements a direct RS485 connection to a solar inverter in the
+This implements a direct RS485 connection to a solar inverter in the
PVI-3.0/3.6/4.2-TL-OUTD ABB series, and may work on others.
The inverter was formerly made by PowerOne who got taken over by ABB.
-The TCP/IP method of communicating with inverters is supported by the
+The TCP/IP method of communicating with inverters is supported by the
Python library, but not by this implementation in this integration.
This integration provides a single sensor which reports the live power output
in watts.
-Note the PV inverter will be unresponsive to communications when in darkness,
+Note the PV inverter will be unresponsive to communications when in darkness,
so the value 'unknown' will be displayed during the night.
## Configuration
@@ -39,7 +39,7 @@ sensor:
{% configuration %}
device:
- description: The serial port your RS485 adaptor is connected to.
+ description: The serial port your RS485 adapter is connected to.
required: true
type: string
address:
diff --git a/source/_integrations/azure_event_hub.markdown b/source/_integrations/azure_event_hub.markdown
index 03c3e9e4e33..e8989741c74 100644
--- a/source/_integrations/azure_event_hub.markdown
+++ b/source/_integrations/azure_event_hub.markdown
@@ -10,13 +10,13 @@ ha_codeowners:
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).
+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 an [Azure IoT Hub](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-builtin).
## First time setup
-This assumes you already have a Azure account. Otherwise create a Free account [here](https://azure.microsoft.com/en-us/free/).
+This assumes you already have an Azure account. Otherwise create a Free account [here](https://azure.microsoft.com/en-us/free/).
-You need to create a Event Hub namespace and a Event Hub in that namespace, you can follow [this guide](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create). Alternatively you can directly deploy an ARM template with the namespace and the Event Hub [from here](https://github.com/Azure/azure-quickstart-templates/tree/master/201-event-hubs-create-event-hub-and-consumer-group/).
+You need to create an Event Hub namespace and an Event Hub in that namespace, you can follow [this guide](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create). Alternatively you can directly deploy an ARM template with the namespace and the Event Hub [from here](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.eventhub/event-hubs-create-event-hub-and-consumer-group).
You must then create a Shared Access Policy for the Event Hub with 'Send' claims or use the RootManageAccessKey from your namespace (this key has additional claims, including managing the event hub and listening, which are not needed for this purpose), for more details on the security of Event Hubs [go here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-authentication-and-security-model-overview).
@@ -171,8 +171,8 @@ azure_event_hub:
There are a number of ways to stream the data that comes into the Event Hub into storages in Azure, the easiest way is to use the built-in Capture function and this allows you to capture the data in Azure Blob Storage or Azure Data Lake store, [details here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-capture-overview).
-Other storages in Azure (and outside) are possible with a [Azure Stream Analytics job](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-inputs#stream-data-from-event-hubs), for instance for [Cosmos DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-documentdb-output), [Azure SQL DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-sql-output-perf), [Azure Table Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-outputs#table-storage), custom writing to [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-custom-path-patterns-blob-storage-output) and [Topic and Queues](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-quick-create-portal#configure-job-output).
+Other storages in Azure (and outside) are possible with an [Azure Stream Analytics job](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-inputs#stream-data-from-event-hubs), for instance for [Cosmos DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-documentdb-output), [Azure SQL DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-sql-output-perf), [Azure Table Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-outputs#table-storage), custom writing to [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-custom-path-patterns-blob-storage-output) and [Topic and Queues](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-quick-create-portal#configure-job-output).
On the analytical side, Event Hub can be directly fed into [Azure Databricks Spark](https://docs.microsoft.com/en-us/azure/azure-databricks/databricks-stream-from-eventhubs?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fevent-hubs%2FTOC.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json), [Azure Time Series Insights](https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-how-to-add-an-event-source-eventhub) and [Microsoft Power BI](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-tutorial-visualize-anomalies).
-The final way to use the data in Azure is to connect a Azure Function to the Event Hub using the [Event Hub trigger binding](https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-hubs).
+The final way to use the data in Azure is to connect an Azure Function to the Event Hub using the [Event Hub trigger binding](https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-hubs).
diff --git a/source/_integrations/blackbird.markdown b/source/_integrations/blackbird.markdown
index 45a7266394b..a138337b023 100644
--- a/source/_integrations/blackbird.markdown
+++ b/source/_integrations/blackbird.markdown
@@ -10,9 +10,9 @@ ha_platforms:
- media_player
---
-The `blackbird` platform allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) using a serial connection.
+The `blackbird` platform allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) (8x8) using a serial or IP connection, this integration does not support the 4x4 matrix switch.
-To add a Blackbird device to your installation, add the following to your `configuration.yaml` file:
+To add a Blackbird 8x8 device to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
diff --git a/source/_integrations/bluesound.markdown b/source/_integrations/bluesound.markdown
index ffa051049c0..a8c5bd8562f 100644
--- a/source/_integrations/bluesound.markdown
+++ b/source/_integrations/bluesound.markdown
@@ -1,7 +1,6 @@
---
title: Bluesound
description: Instructions on how to integrate Bluesound devices into Home Assistant.
-logo: bluesound.png
ha_category:
- Media Player
ha_release: 0.51
diff --git a/source/_integrations/bmp280.markdown b/source/_integrations/bmp280.markdown
index 8172c8e9524..5ae64297615 100644
--- a/source/_integrations/bmp280.markdown
+++ b/source/_integrations/bmp280.markdown
@@ -15,7 +15,7 @@ ha_platforms:
- sensor
---
-The `bmp280` sensor platform allows you to read temperature and pressure values of a [Bosch BMP280 Environmental sensor](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp280-1.html) connected via [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins).
+The `bmp280` sensor platform allows you to read temperature and pressure values of a [Bosch BMP280 Environmental sensor](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp280/) connected via [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins).
This integration has been tested on a Raspberry Pi 4B, but it should work on any device which is supported by [CircuitPython](https://circuitpython.org/).
diff --git a/source/_integrations/bond.markdown b/source/_integrations/bond.markdown
index 48b7f6813fb..17ad3701a7d 100644
--- a/source/_integrations/bond.markdown
+++ b/source/_integrations/bond.markdown
@@ -12,6 +12,7 @@ ha_release: 0.113
ha_domain: bond
ha_codeowners:
- '@prystupa'
+ - '@joshs85'
ha_config_flow: true
ha_quality_scale: platinum
ha_zeroconf: true
diff --git a/source/_integrations/brother.markdown b/source/_integrations/brother.markdown
index 38131400b01..db3a927dc9d 100644
--- a/source/_integrations/brother.markdown
+++ b/source/_integrations/brother.markdown
@@ -37,21 +37,21 @@ For some Brother devices, `SNMPv3 read-write access and v1/v2c read-only access`
## Sensor Example
-You can configure Home Assistant to alert you when the printer jams or runs out of paper as follows. First, add the following to `configuration.yaml` under the `binary_sensor:` section (replace `sensor.hl_l2340d_status` with the actual name of your sensor):
+You can configure Home Assistant to alert you when the printer jams or runs out of paper as follows. First, add the following to `configuration.yaml` under the `template:` section (Note: replace `sensor.hl_l2340d_status` with the actual name of your sensor):
{% raw %}
```yaml
- - platform: template
- sensors:
- laser_out_of_paper:
- value_template: "{{ is_state('sensor.hl_l2340d_status', 'no paper') }}"
- friendly_name: "Laser Printer Out of Paper"
- - platform: template
- sensors:
- laser_paper_jam:
- value_template: "{{ is_state('sensor.hl_l2340d_status', 'paper jam') }}"
- friendly_name: "Laser Printer Paper Jam"
+template:
+ - binary_sensor:
+ - name: 'Laser Printer Out Of Paper'
+ state: >
+ {{ is_state('sensor.hl_l2340d_status', 'no paper') }}
+
+ - binary_sensor:
+ - name: 'Later Printer Paper Jam'
+ state: >
+ {{ is_state('sensor.hl_l2340d_status', 'paper jam') }}
```
{% endraw %}
@@ -62,14 +62,15 @@ Then, add this under the `alert:` section:
laser_out_of_paper:
name: Laser Printer is Out of Paper
done_message: Laser Printer Has Paper
- entity_id: binary_sensor.laser_out_of_paper
+ entity_id: binary_sensor.laser_printer_out_of_paper
can_acknowledge: true
notifiers:
- my_phone_notify
+
laser_paper_jam:
name: Laser Printer has a Paper Jam
done_message: Laser Printer Paper Jam Cleared
- entity_id: binary_sensor.laser_paper_jam
+ entity_id: binary_sensor.laser_printer_paper_jam
can_acknowledge: true
notifiers:
- my_phone_notify
diff --git a/source/_integrations/caldav.markdown b/source/_integrations/caldav.markdown
index 98abca786f1..29d9b45617f 100644
--- a/source/_integrations/caldav.markdown
+++ b/source/_integrations/caldav.markdown
@@ -127,7 +127,7 @@ verify_ssl:
## Sensor attributes
-- **offset_reached**: If set in the event title and parsed out will be on/off once the offset in the title in minutes is reached. So the title Very important meeting !!-10 would trigger this attribute to be on 10 minutes before the event starts. This should be in the format of `HH:MM` or `MM`.
+- **offset_reached**: If set in the event title and parsed out will be on/off once the offset in the title in minutes is reached. So the title Very important meeting !! `-10` would trigger this attribute to be on 10 minutes before the event starts. This should be in the format of `HH:MM` or `MM`.
- **all_day**: `True/False` if this is an all day event. Will be `False` if there is no event found.
- **message**: The event title with the `search` values extracted. So in the above example for `offset_reached` the message would be set to Very important meeting
- **description**: The event description.
diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown
index 30f8f2b07ac..b2d71fda26a 100644
--- a/source/_integrations/cast.markdown
+++ b/source/_integrations/cast.markdown
@@ -52,6 +52,14 @@ Home Assistant Cast requires your Home Assistant installation to be accessible v
## Playing media
+
+
+Chromecasts generally ignore DNS servers from DHCP and will instead use Google's DNS servers, 8.8.8.8 and 8.8.4.4. This means media URLs must either be specifying the IP-address of the server directly, e.g. `http://192.168.1.1:8123/movie.mp4`, or be publicly resolvable, e.g. `http://homeassistant.internal.mydomain.com:8123/movie.mp4` where `homeassistant.internal.mydomain.com` resolves to `129.168.1.1`. A hostname which can't be publicly resolved, e.g. `http://homeassistant.local:8123/movie.mp4` will fail to play.
+
+This is important when casting TTS or local media sources; the cast integration will cast such media from the `external_url` if [configured](/docs/configuration/basic), otherwise from the Home Assistant Cloud if configured, otherwise from the [`internal_url`](/docs/configuration/basic). Note that the Home Assistant Cloud will not be used if an `external_url` is configured.
+
+
+
### Using the built in media player app (Default Media Receiver)
Chromecasts can play many kinds of modern [media (image/audio/video) formats](https://developers.google.com/cast/docs/media) using the built in app Default Media Receiver. As a rule of thumb, if a Chrome browser can play a media file a Chromecast will be able to handle that too.
diff --git a/source/_integrations/cover.mqtt.markdown b/source/_integrations/cover.mqtt.markdown
index 04e0d2b9b46..34647ce56b1 100644
--- a/source/_integrations/cover.mqtt.markdown
+++ b/source/_integrations/cover.mqtt.markdown
@@ -341,7 +341,7 @@ cover:
command_topic: "home-assistant/cover/set"
position_topic: "home-assistant/cover/position"
availability:
- - "home-assistant/cover/availability"
+ - topic: "home-assistant/cover/availability"
set_position_topic: "home-assistant/cover/set_position"
qos: 0
retain: true
diff --git a/source/_integrations/crownstone.markdown b/source/_integrations/crownstone.markdown
index fd3274ce4c4..5c10408bb5b 100644
--- a/source/_integrations/crownstone.markdown
+++ b/source/_integrations/crownstone.markdown
@@ -3,14 +3,15 @@ title: Crownstone
description: Instructions on how to setup the Crownstone integration within Home Assistant.
ha_category:
- Light
-ha_iot_class: Cloud Push
+ha_iot_class: Cloud Push
ha_release: '2021.10'
ha_config_flow: true
-ha_quality_scale: silver
ha_codeowners:
- '@Crownstone'
- '@RicArch97'
ha_domain: crownstone
+ha_platforms:
+ - light
---
The Crownstone integration allows you to control your Crownstones either via the cloud or using a [Crownstone USB](#crownstone-usb) dongle.
diff --git a/source/_integrations/deconz.markdown b/source/_integrations/deconz.markdown
index 2e089ec8d05..98cf981de0b 100644
--- a/source/_integrations/deconz.markdown
+++ b/source/_integrations/deconz.markdown
@@ -37,7 +37,6 @@ ha_platforms:
[deCONZ](https://www.dresden-elektronik.de/funk/software/deconz.html) by [dresden elektronik](https://www.dresden-elektronik.de) is a software that communicates with ConBee/RaspBee Zigbee gateways and exposes Zigbee devices that are connected to the gateway.
-[deCONZ REST API](https://dresden-elektronik.github.io/deconz-rest-doc/).
There is currently support for the following device types within Home Assistant:
@@ -63,7 +62,7 @@ See [deCONZ wiki](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/
{% include integrations/config_flow.md %}
-Running a stand-alone instance of deCONZ (non add-on installation) requires a pairing between the deCONZ gateway and Home Assistant. To allow Home Assistant to connect with deCONZ go to the Phoscon UI click Settings -> Gateway -> Advanced and press the "Authenticate app" button. This same information is also shown during the config flow of the deCONZ integration.
+Running a stand-alone instance of deCONZ (non add-on installation) requires a pairing between the deCONZ gateway and Home Assistant. To allow Home Assistant to connect with deCONZ go to the Phoscon **UI click Settings -> Gateway -> Advanced** and press the "Authenticate app" button. This same information is also shown during the config flow of the deCONZ integration.
## Debugging integration
@@ -91,7 +90,7 @@ Available services: `configure`, `deconz.device_refresh` and `deconz.remove_orph
### Service `deconz.configure`
-Set attribute of device in deCONZ using [REST-API](https://dresden-elektronik.github.io/deconz-rest-doc/rest/).
+Set the attribute of device in deCONZ using [REST-API](https://dresden-elektronik.github.io/deconz-rest-doc/about_rest/).
| Service data attribute | Optional | Description |
| ---------------------- | -------- | --------------------------------------------------------------------------- |
diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown
index 989734ab63c..59beef92ead 100644
--- a/source/_integrations/denonavr.markdown
+++ b/source/_integrations/denonavr.markdown
@@ -125,7 +125,7 @@ So for example, the above command `/goform/formiPhoneAppDirect.xml?VSMONI2` will
-The denonavr platform supports the standard media player controls such as `turn_on` and `volume_up`. Thus calling the service `media_player.turn_on` is equivalent to calling `denonavr.get_command` with the command `/goform/formiPhoneAppDirect.xml?PWON`. See [media_player](/integrations/meida_player/) for more details.
+The denonavr platform supports the standard media player controls such as `turn_on` and `volume_up`. Thus calling the service `media_player.turn_on` is equivalent to calling `denonavr.get_command` with the command `/goform/formiPhoneAppDirect.xml?PWON`. See [media_player](/integrations/media_player/) for more details.
diff --git a/source/_integrations/dlna_dmr.markdown b/source/_integrations/dlna_dmr.markdown
index d33df1f2046..e5f61e1c15f 100644
--- a/source/_integrations/dlna_dmr.markdown
+++ b/source/_integrations/dlna_dmr.markdown
@@ -10,7 +10,6 @@ ha_codeowners:
- '@StevenLooman'
- '@chishm'
ha_domain: dlna_dmr
-ha_ssdp: true
ha_platforms:
- media_player
---
diff --git a/source/_integrations/ecovacs.markdown b/source/_integrations/ecovacs.markdown
index 795c2db74e7..0b784dc1b4c 100644
--- a/source/_integrations/ecovacs.markdown
+++ b/source/_integrations/ecovacs.markdown
@@ -70,7 +70,7 @@ logger:
sucks: debug
```
-Warning: doing this will cause your authentication token to visible in your log files. Be sure to remove any tokens and other authentication details from your log before posting them in an issue.
+**Warning**: doing this will cause your authentication token to be visible in your log files. Be sure to remove any tokens and other authentication details from your log before posting them in an issue.
## Vacuum
diff --git a/source/_integrations/epsonworkforce.markdown b/source/_integrations/epsonworkforce.markdown
index ad51e194604..b4e99f0cb18 100644
--- a/source/_integrations/epsonworkforce.markdown
+++ b/source/_integrations/epsonworkforce.markdown
@@ -37,7 +37,7 @@ host:
required: true
type: string
monitored_conditions:
- description: The cartridge colours to monitor.
+ description: The cartridge colours to monitor.
required: true
type: list
keys:
@@ -50,14 +50,14 @@ monitored_conditions:
magenta:
description: The magenta (=red) ink cartridge.
cyan:
- description: The cyan (=blue) ink cartridge.
+ description: The cyan (=blue) ink cartridge.
clean:
- description: The cleaning cartridge.
+ description: The cleaning cartridge.
{% endconfiguration %}
Supported devices:
-- Epson Workforce (and some EcoTank) printers who publish a HTTP page containing the ink cardridge levels
+- Epson Workforce (and some EcoTank) printers who publish a HTTP page containing the ink cartridge levels
Tested devices:
@@ -67,7 +67,8 @@ Tested devices:
- Epson WF3640
- Epson EcoTank ET-77x0
- Epson ET-2650
+- Espon ET-4750
- Epson Expression Home XP-2105
To make this module work you need to connect your printer to your LAN.
-The best is to navigate to the status page of the printer to check if it shows the page with the ink levels on the URL http://
/PRESENTATION/HTML/TOP/PRTINFO.HTML
+The best is to navigate to the status page of the printer to check if it shows the page with the ink levels on the URL `http:///PRESENTATION/HTML/TOP/PRTINFO.HTML`
diff --git a/source/_integrations/etherscan.markdown b/source/_integrations/etherscan.markdown
index 9d66ece6a68..60ee4ad9de8 100644
--- a/source/_integrations/etherscan.markdown
+++ b/source/_integrations/etherscan.markdown
@@ -1,7 +1,6 @@
---
title: Etherscan
description: Instructions on how to integrate Etherscan.io data within Home Assistant.
-logo: etherscan.png
ha_category:
- Finance
ha_release: 0.47
diff --git a/source/_integrations/everlights.markdown b/source/_integrations/everlights.markdown
index 00bee6f113d..810bfcd4d30 100644
--- a/source/_integrations/everlights.markdown
+++ b/source/_integrations/everlights.markdown
@@ -1,7 +1,6 @@
---
title: EverLights
description: Instructions on how to set up EverLights within Home Assistant.
-logo: everlights.png
ha_category:
- Light
ha_iot_class: Local Polling
diff --git a/source/_integrations/file.markdown b/source/_integrations/file.markdown
index c9f4c9bc856..c0d4c2466d5 100644
--- a/source/_integrations/file.markdown
+++ b/source/_integrations/file.markdown
@@ -141,4 +141,3 @@ sensor:
```
{% endraw %}
-
diff --git a/source/_integrations/flipr.markdown b/source/_integrations/flipr.markdown
index 04147886bfa..de9583c337a 100644
--- a/source/_integrations/flipr.markdown
+++ b/source/_integrations/flipr.markdown
@@ -10,6 +10,7 @@ ha_codeowners:
- '@cnico'
ha_domain: flipr
ha_platforms:
+ - binary_sensor
- sensor
---
diff --git a/source/_integrations/foscam.markdown b/source/_integrations/foscam.markdown
index e2db7f57724..57f6c28b196 100644
--- a/source/_integrations/foscam.markdown
+++ b/source/_integrations/foscam.markdown
@@ -160,4 +160,4 @@ elements:
### Extra CGI Commands
-Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](https://www.iltucci.com/blog/wp-content/uploads/2018/12/Foscam-IPCamera-CGI-User-Guide-V1.0.4.pdf)).
+Foscam Webcams which support CGI Commands can be controlled by Home Assistant ([Source](https://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf)).
diff --git a/source/_integrations/fritz.markdown b/source/_integrations/fritz.markdown
index 7ae3e2e8c07..d1b52bd39ad 100644
--- a/source/_integrations/fritz.markdown
+++ b/source/_integrations/fritz.markdown
@@ -100,10 +100,9 @@ As a result, this integration will create entities only for rules that have your
## Example Automations and Scripts
+### Script: Reconnect / get new IP
-**Script: Reconnect / get new IP**
-
-The following script can be used to easily add a reconnect button to your UI. If you want to reboot your FRITZ!Box, you can use `fritzbox_tools.reboot` instead.
+The following script can be used to easily add a reconnect button to your UI. If you want to reboot your FRITZ!Box, you can use `fritz.reboot` instead.
```yaml
fritz_box_reconnect:
@@ -111,37 +110,38 @@ fritz_box_reconnect:
sequence:
- service: fritz.reconnect
target:
- entity_id: binary_sensor.fritz_box_7530_connectivity
+ entity_id: binary_sensor.fritzbox_7530_connection
```
-**Automation: Reconnect / get new IP every night**
+
+### Automation: Reconnect / get new IP every night
```yaml
automation:
-- alias: "System: Reconnect FRITZ!Box"
+- alias: "System - Reconnect FRITZ!Box"
trigger:
- platform: time
at: "05:00:00"
action:
- service: fritz.reconnect
target:
- entity_id: binary_sensor.fritzbox_x_connectivity
+ entity_id: binary_sensor.fritzbox_7530_connection
```
-**Automation: Phone notification with wifi credentials when guest wifi is created**
+### Automation: Phone notification with Wi-fi credentials when guest Wi-fi is created
```yaml
automation:
- - alias: "Guests Wifi Turned On -> Send Password To Phone"
+ - alias: "Guests Wi-fi Turned On -> Send Password To Phone"
trigger:
- platform: state
- entity_id: switch.fritzbox_x_wifi_x
+ entity_id: switch.fritzbox_7530_wifi_myssid
to: "on"
action:
- service: notify.notify
data:
- title: "Guest wifi is enabled"
+ title: "Guest Wi-Fi is enabled"
message: "Password: ..."
```
diff --git a/source/_integrations/graphite.markdown b/source/_integrations/graphite.markdown
index 03b766a0650..887f5acf636 100644
--- a/source/_integrations/graphite.markdown
+++ b/source/_integrations/graphite.markdown
@@ -1,7 +1,6 @@
---
title: Graphite
description: Instructions on how to record Home Assistant history in Graphite.
-logo: graphite.png
ha_category:
- History
ha_release: 0.13
diff --git a/source/_integrations/group.markdown b/source/_integrations/group.markdown
index b7765ee2d4d..fd59692e83c 100644
--- a/source/_integrations/group.markdown
+++ b/source/_integrations/group.markdown
@@ -10,6 +10,7 @@ ha_codeowners:
- '@home-assistant/core'
ha_domain: group
ha_platforms:
+ - binary_sensor
- cover
- light
- media_player
diff --git a/source/_integrations/harmony.markdown b/source/_integrations/harmony.markdown
index 2ef615d5bbf..5f403dbc461 100644
--- a/source/_integrations/harmony.markdown
+++ b/source/_integrations/harmony.markdown
@@ -11,6 +11,7 @@ ha_codeowners:
- '@bramkragten'
- '@bdraco'
- '@mkeesey'
+ - '@Aohzan'
ha_domain: harmony
ha_ssdp: true
ha_platforms:
@@ -184,15 +185,14 @@ Template sensors can be utilized to display current activity in the frontend.
{% raw %}
```yaml
-sensor:
- - platform: template
- sensors:
- family_room:
- value_template: '{{ state_attr("remote.family_room", "current_activity") }}'
- friendly_name: "Family Room"
- bedroom:
- value_template: '{{ state_attr("remote.bedroom", "current_activity") }}'
- friendly_name: "bedroom"
+template:
+ - sensor:
+ - name: 'Family Room Harmony Remote'
+ state: >
+ {{ state_attr('remote.family_room', 'current_activity') }}
+ - name: 'Bedroom Harmony Remote'
+ state: >
+ {{ state_attr('remote.bedroom', 'current_activity') }}
```
{% endraw %}
diff --git a/source/_integrations/hive.markdown b/source/_integrations/hive.markdown
index 9b9c459ebc1..1cf937258f3 100644
--- a/source/_integrations/hive.markdown
+++ b/source/_integrations/hive.markdown
@@ -67,7 +67,7 @@ script:
### Service `hive.boost_heating_off`
-You can use the service `hive.boost_heating_off` to set your heating to boost for a period of time at a certain target temperature". Individual TRVs can also be boosted in the same way, using this service.
+You can use the service `hive.boost_heating_off` to turn your heating boost off.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------------------------- |
diff --git a/source/_integrations/home_plus_control.markdown b/source/_integrations/home_plus_control.markdown
index 79d8af2c5fb..e35f21c1ced 100644
--- a/source/_integrations/home_plus_control.markdown
+++ b/source/_integrations/home_plus_control.markdown
@@ -30,6 +30,10 @@ This integration has been tested to work with the following range of Legrand pro
- Valena Next™ with Netatmo
+This integration has also been tested to work with the following range of BTicino products
+
+- Living Now (Light switches)
+
## Authentication
Before you are able to configure the Legrand Home + Control integration into Home Assistant, you must register with the *Works with Legrand* platform.
diff --git a/source/_integrations/homeworks.markdown b/source/_integrations/homeworks.markdown
index 40112375148..4698ad22a14 100644
--- a/source/_integrations/homeworks.markdown
+++ b/source/_integrations/homeworks.markdown
@@ -42,7 +42,7 @@ homeworks:
{% configuration %}
host:
- description: The IP address of the ethernet to serial adapter. It is assumed that the adaptor has been preconfigured.
+ description: The IP address of the ethernet to serial adapter. It is assumed that the adapter has been preconfigured.
required: true
type: string
port:
diff --git a/source/_integrations/hp_ilo.markdown b/source/_integrations/hp_ilo.markdown
index 9739acc9904..68cee7e1dcd 100644
--- a/source/_integrations/hp_ilo.markdown
+++ b/source/_integrations/hp_ilo.markdown
@@ -114,6 +114,7 @@ sensor:
value_template: '{{ ilo_data.temperature["01-Inlet Ambient"].currentreading[0] }}'
- name: Server Health
sensor_type: server_health
+ value_template: '{{ ilo_data.health_at_a_glance }}'
```
{% endraw %}
diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown
index 834a272d462..c9ac8556007 100644
--- a/source/_integrations/hue.markdown
+++ b/source/_integrations/hue.markdown
@@ -19,6 +19,7 @@ ha_platforms:
- binary_sensor
- light
- sensor
+ha_zeroconf: true
---
The Philips Hue integration allows you to control and monitor the lights and motion sensors connected to your Hue bridge.
diff --git a/source/_integrations/hunterdouglas_powerview.markdown b/source/_integrations/hunterdouglas_powerview.markdown
index 1ba5a0b9e21..a5838e5a35c 100644
--- a/source/_integrations/hunterdouglas_powerview.markdown
+++ b/source/_integrations/hunterdouglas_powerview.markdown
@@ -20,7 +20,7 @@ ha_zeroconf: true
ha_dhcp: true
---
-The `hunterdouglas_powerview` integration allows you to integrate your [Hunter Douglas PowerView](https://www.hunterdouglas.com/operating-systems/powerview-motorization/support) devices in Home Assistant.
+The `hunterdouglas_powerview` integration allows you to integrate your [Hunter Douglas PowerView](https://www.hunterdouglas.com/operating-systems/powerview-motorization/support) devices in Home Assistant. The product is also known by the brand name Luxaflex Powerview in Europe and Australia [as explained on their website](https://www.hunterdouglasgroup.com/company/brands-in-action/), however this integration should work for both brands.
There is currently support for the following device types within Home Assistant:
diff --git a/source/_integrations/iotawatt.markdown b/source/_integrations/iotawatt.markdown
index f47f1436428..9dfc1d06d5e 100644
--- a/source/_integrations/iotawatt.markdown
+++ b/source/_integrations/iotawatt.markdown
@@ -13,6 +13,7 @@ ha_codeowners:
ha_platforms:
- sensor
---
+
Integration for the [IoTaWatt](https://www.iotawatt.com/) Open WiFi Electricity Monitor. It
will collect data from the Current Transformer Clamps (Input CTs) and any Outputs that are defined on the IoTaWatt
and create them as sensors in Home Assistant.
diff --git a/source/_integrations/keyboard_remote.markdown b/source/_integrations/keyboard_remote.markdown
index 7db0b3aa9f3..d7f7ed717a8 100644
--- a/source/_integrations/keyboard_remote.markdown
+++ b/source/_integrations/keyboard_remote.markdown
@@ -102,7 +102,7 @@ automation:
`device_descriptor` or `device_name` may be specified in the trigger so the automation will be fired only for that keyboard. This is especially useful if you wish to use several Bluetooth remotes to control different devices. Omit them to ensure the same key triggers the automation for all keyboards/remotes.
-`key_code` should be set to the code generated by the key press, otherwise the trigger will file on every key press.
+`key_code` should be set to the code generated by the key press, otherwise the trigger will fire on every key press.
`type` can optionally be set to one of `key_down`, `key_up`, or `key_hold` to limit the trigger to that specific event type.
## Disconnections
diff --git a/source/_integrations/kodi.markdown b/source/_integrations/kodi.markdown
index 1d59971c579..5d6ee2eb141 100644
--- a/source/_integrations/kodi.markdown
+++ b/source/_integrations/kodi.markdown
@@ -19,7 +19,7 @@ ha_platforms:
The `kodi` platform allows you to control a [Kodi](https://kodi.tv/) multimedia system from Home Assistant.
-The preferred way to set up the Kodi platform is by through discovery, which requires an enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation.
+The preferred way to set up the Kodi platform is through discovery, which requires an enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation.
There is currently support for the following device types within Home Assistant:
diff --git a/source/_integrations/lametric.markdown b/source/_integrations/lametric.markdown
index dbbdf083411..04a322e8f3b 100644
--- a/source/_integrations/lametric.markdown
+++ b/source/_integrations/lametric.markdown
@@ -1,7 +1,6 @@
---
title: LaMetric
description: Instructions on how to integrate LaMetric with Home Assistant.
-logo: lametric.png
ha_category:
- Hub
- Notifications
diff --git a/source/_integrations/launch_library.markdown b/source/_integrations/launch_library.markdown
index 3e11ca6eeb1..0b8e8346f3a 100644
--- a/source/_integrations/launch_library.markdown
+++ b/source/_integrations/launch_library.markdown
@@ -1,7 +1,6 @@
---
title: Launch Library
description: Instructions on how to integrate space launch information within Home Assistant.
-logo: rocket.png
ha_category:
- Sensor
ha_iot_class: Cloud Polling
diff --git a/source/_integrations/linux_battery.markdown b/source/_integrations/linux_battery.markdown
index 2cfaa13d0cf..9f549ce4c90 100644
--- a/source/_integrations/linux_battery.markdown
+++ b/source/_integrations/linux_battery.markdown
@@ -1,7 +1,6 @@
---
title: Linux Battery
description: Instructions on how to integrate Linux Battery information into Home Assistant.
-logo: linux_battery.png
ha_category:
- System Monitor
ha_release: 0.28
diff --git a/source/_integrations/lock.template.markdown b/source/_integrations/lock.template.markdown
index 40fadbbe30e..235b99b3b4b 100644
--- a/source/_integrations/lock.template.markdown
+++ b/source/_integrations/lock.template.markdown
@@ -77,7 +77,7 @@ lock:
## Considerations
-If you are using the state of a platform that takes extra time to load, the Template Lock may get an `unknown` state during startup. This results in error messages in your log file until that platform has completed loading. If you use `is_state()` function in your template, you can avoid this situation. For example, you would replace {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an unknown result: {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}
+If you are using the state of a platform that takes extra time to load, the Template Lock may get an `unknown` state during startup. This results in error messages in your log file until that platform has completed loading. If you use `is_state()` function in your template, you can avoid this situation. For example, you would replace {% raw %}`{{ state('switch.source') == 'on') }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an unknown result: {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}
## Examples
diff --git a/source/_integrations/lutron_caseta.markdown b/source/_integrations/lutron_caseta.markdown
index 63ab3530439..57845c6a5d2 100644
--- a/source/_integrations/lutron_caseta.markdown
+++ b/source/_integrations/lutron_caseta.markdown
@@ -46,16 +46,16 @@ Additionally RA2 Select Main Repeater (`RR-SEL-REP2-BL`) or Lutron Caséta Smart
- Pico Remotes as [device triggers](/integrations/device_automation/)
- Shade Remotes as [device triggers](/integrations/device_automation/)
+When configured, the Lutron Caséta integration will automatically discover the currently supported devices as set up in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Lamp' in a room called 'Bedroom' becomes `light.bedroom_lamp` in Home Assistant.
+
{% include integrations/config_flow.md %}
-## Manual configuration
-
-Alternatively, if you already have `caseta.key`, `caseta.crt`, `caseta-bridge.crt`, and cannot physically access the bridge to press the button, pairing can be done manually using the following steps:
-
-When configured, the `lutron_caseta` integration will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Lamp' in a room called 'Bedroom' becomes `light.bedroom_lamp` in Home Assistant.
+## Manual hub configuration
To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [get_lutron_cert.py](https://github.com/gurumitts/pylutron-caseta/blob/master/get_lutron_cert.py), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
+If you already have `caseta.key`, `caseta.crt`, `caseta-bridge.crt`, and cannot physically access the bridge to press the button, pairing can be done by utilizing these existing files.
+
Once you have the three necessary files, place them in your configuration directory and add the following to your `configuration.yaml`:
```yaml
diff --git a/source/_integrations/marytts.markdown b/source/_integrations/marytts.markdown
index a29f1539765..918e30afd18 100644
--- a/source/_integrations/marytts.markdown
+++ b/source/_integrations/marytts.markdown
@@ -76,15 +76,15 @@ tts:
voice: "cmu-slt-hsmm"
language: "en_US"
effect:
- Volume: "amount:2.0;",
- TractScaler: "amount:1.5;",
- F0Scale: "f0Scale:2.0;",
- F0Add: "f0Add:50.0;",
- Rate: "durScale:1.5;",
- Robot: "amount:100.0;",
- Whisper: "amount:100.0;",
- Stadium: "amount:100.0",
- Chorus: "delay1:466;amp1:0.54;delay2:600;amp2:-0.10;delay3:250;amp3:0.30",
- FIRFilter: "type:3;fc1:500.0;fc2:2000.0",
+ Volume: "amount:2.0;"
+ TractScaler: "amount:1.5;"
+ F0Scale: "f0Scale:2.0;"
+ F0Add: "f0Add:50.0;"
+ Rate: "durScale:1.5;"
+ Robot: "amount:100.0;"
+ Whisper: "amount:100.0;"
+ Stadium: "amount:100.0"
+ Chorus: "delay1:466;amp1:0.54;delay2:600;amp2:-0.10;delay3:250;amp3:0.30"
+ FIRFilter: "type:3;fc1:500.0;fc2:2000.0"
JetPilot: ""
```
diff --git a/source/_integrations/maxcube.markdown b/source/_integrations/maxcube.markdown
index 0d0ada06c9d..64a7b875795 100644
--- a/source/_integrations/maxcube.markdown
+++ b/source/_integrations/maxcube.markdown
@@ -1,7 +1,6 @@
---
title: eQ-3 MAX!
description: Instructions on how to integrate eQ-3 MAX! components with Home Assistant via eQ-3 MAX! Cube.
-logo: maxcube.png
ha_category:
- Climate
- Binary Sensor
diff --git a/source/_integrations/media_player.markdown b/source/_integrations/media_player.markdown
index f8a1b7d6da0..3c340bf711e 100644
--- a/source/_integrations/media_player.markdown
+++ b/source/_integrations/media_player.markdown
@@ -120,7 +120,7 @@ data:
media_content_id: "https://fake-home-assistant.io.stream/aac"
extra:
thumb: "https://brands.home-assistant.io/_/homeassistant/logo.png"
- title: HomeAssitantRadio
+ title: HomeAssistantRadio
```
#### Service `media_player.select_source`
diff --git a/source/_integrations/microsoft.markdown b/source/_integrations/microsoft.markdown
index a6ef468f3fb..203d8f5a8d1 100644
--- a/source/_integrations/microsoft.markdown
+++ b/source/_integrations/microsoft.markdown
@@ -71,11 +71,16 @@ region:
-Not all Azure regions support high-quality neural voices. Use [this overview](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/regions#standard-and-neural-voices) to determine the availability of standard and neural voices by region/endpoint.
+Not all Azure regions support high-quality neural voices. Use [this overview](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/regions#neural-and-standard-voices) to determine the availability of standard and neural voices by region/endpoint.
-
+
+
+If you set the language to anything other than the default `en-us`, you will need to specify a matching voice type as well.
+
+
+
## Full configuration example
A full configuration sample including optional variables:
diff --git a/source/_integrations/modem_callerid.markdown b/source/_integrations/modem_callerid.markdown
index 0eed0b031f5..a30584393f2 100644
--- a/source/_integrations/modem_callerid.markdown
+++ b/source/_integrations/modem_callerid.markdown
@@ -1,24 +1,29 @@
---
-title: Modem Caller ID
+title: Phone Modem
description: Instructions on how to integrate the Caller ID sensor into Home Assistant.
ha_category:
- Sensor
ha_release: '0.40'
ha_iot_class: Local Polling
ha_domain: modem_callerid
+ha_codeowners:
+ - '@tkdrob'
+ha_platforms:
+ - sensor
+ha_config_flow: true
---
The `modem_callerid` integration uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1). Usually any modem that uses a CX93001 will support this.
When the sensor detects a new call, its state changes to 'ring' for each ring and 'callerid' when caller id information is received. It returns to 'idle' once ringing stops. The state event includes an attribute payload that includes the time of the call, name and number.
-This integration also offers two services. `modem_callerid.reject_call` to pick up and then hang up the call to properly reject a call (via ATA anf ATH). `modem_callerid.hangup_call` to hang up an existing call (via ATH).
+This integration also offers a service. `modem_callerid.reject_call` to pick up and then hang up the call to properly reject a call (via ATA anf ATH).
{% include integrations/config_flow.md %}
## Examples
-Some example automations:
+An example automation:
{% raw %}
@@ -55,19 +60,3 @@ automation:
```
{% endraw %}
-
-## Extra instructions for the Home Assistant Core installation type
-
-To find the path of your USB modem, run:
-
-```bash
-ls /dev/ttyACM*
-```
-
-If Home Assistant (`hass`) runs with another user (e.g., `homeassistant`) give access to the stick with:
-
-```bash
-sudo usermod -a -G dialout homeassistant
-```
-
-Depending on what's plugged into your USB ports, the name found above may change. You can lock in a name, such as `/dev/modem`, by following [these instructions](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/).
diff --git a/source/_integrations/monoprice.markdown b/source/_integrations/monoprice.markdown
index ec051c6ac13..f3608ac5b75 100644
--- a/source/_integrations/monoprice.markdown
+++ b/source/_integrations/monoprice.markdown
@@ -27,7 +27,7 @@ Sources can also be later edited from the integration options (gear icon in the
## Zone Management
-Devices and entities are created for each of the possible 18 zones, and can be enabled, disabled and renamed through regular Home Assisant methods.
+Devices and entities are created for each of the possible 18 zones, and can be enabled, disabled and renamed through regular Home Assistant methods.
By default, the first 6 zones (11..16) are enabled, and there's an attempt to automatically detect the 12 extension zones (21..26, and 31..36) on the first run.
## Services
diff --git a/source/_integrations/mullvad.markdown b/source/_integrations/mullvad.markdown
index b6d2bf1ab86..19c751976c8 100644
--- a/source/_integrations/mullvad.markdown
+++ b/source/_integrations/mullvad.markdown
@@ -14,7 +14,7 @@ ha_platforms:
- binary_sensor
---
-The Mullvad VPN integration pulls [Mullvad](https://mullvad.net/) VPN status information into Home Assistant.
+The Mullvad VPN integration uses the [Mullvad](https://mullvad.net/) VPN API to detect if your Home Assistant instance is connected to the Mullvad VPN service.
diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown
index 38179bbf10e..d0cd603ad80 100644
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@@ -32,12 +32,10 @@ There is currently support for the following device types within Home Assistant:
- [Sensor](#sensor)
-This integration supports two Nest APIs. The SDM API is the new primary API that accepts new users. The Legacy Works With Nest API is not accepting new users, but the documentation still exists at the bottom of the page so existing users can keep using it.
+This integration supports two Nest APIs: The SDM API (new) accepts new users and requires a US$5 fee. The Legacy Works With Nest API (old) does not accept new users, but the documentation is still available at the bottom of the page for existing users.
-Google applies strict [Redirect URI validation
-rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) to keep your login
-credentials secure. In practice, this means that you must access Home Assistant *over SSL* and a *public top-level domain* when setting up this integration. See the documentation on [Securing](/docs/configuration/securing/) or [Troubleshooting](#troubleshooting), and note that you don't actually need to enable remote access.
+Google applies strict [Redirect URI validation rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) to keep your login credentials secure. In practice, this means that you must access Home Assistant *over SSL* and a *public top-level domain* when setting up this integration. See the documentation on [Securing](/docs/configuration/securing/) or [Troubleshooting](#troubleshooting), and note that you don't actually need to enable remote access.
## Overview: Supported Devices
@@ -64,7 +62,9 @@ The full detailed instructions for account setup are available in the [Device Ac
For the first phase, you will turn on the API and create the necessary credentials to have Home Assistant talk to the Nest API.
-1. First go to the [Device Access Registration](https://developers.google.com/nest/device-access/registration) page. Click on the button **Go to the Device Access Console**.
+{% details "Create a Device Access Project [Device Access Console]" %}
+
+1. First go to the [Device Access Registration](https://developers.google.com/nest/device-access/registration) page. Click on the button **[Go to the Device Access Console](https://console.nest.google.com/device-access/)**.
1. Check the box to "Accept the Terms of Service" and click **Continue to Payment** where you need to pay a fee (currently US$5).
@@ -80,7 +80,15 @@ For the first phase, you will turn on the API and create the necessary credentia
1. Give your Device Access project a name and click **Next**.
-1. Next you will be asked for an *OAuth client ID*. It is a good idea to go create that now. Open a new tab to the [Google API Console](https://console.developers.google.com/apis/credentials).
+1. Next you will be asked for an *OAuth client ID*. It is a good idea to go create that now following instructions in the next section in a new browser tab.
+
+{% enddetails %}
+
+{% details "Configure OAuth client_id and client_secret [Cloud Console]" %}
+
+By the end of this section you will have the `client_id` and `client_secret`.
+
+1. Open a new tab to the [Google API Console](https://console.developers.google.com/apis/credentials).
1. If this is your first time here, you likely need to create a new Google API project. Click **Create Project** then **New
Project**. Note: This is a different type of project from the Device Access project you are also creating.
@@ -119,13 +127,24 @@ Project**. Note: This is a different type of project from the Device Access proj
1. You should now be presented with an *OAuth client created* message. Take note of *Your Client ID* and *Your Client Secret* as these are needed for Home Assistant set up.
-1. Now head back to the *Device Access Console* tab and *Add your OAuth client ID* then click **Next**.
+{% enddetails %}
+
+{% details "Link Device Access project_id [Device Access Console]" %}
+
+By the end of this section you will have a `project_id` as well as the *Topic Name* needed to configure Cloud Pub/Sub.
+
+1. Now head back to the *[Device Access Console](https://console.nest.google.com/device-access/project-list)* tab and *Add your OAuth client ID* then click **Next**.
1. Enable Events by clicking on **Enable** and **Create project**.
-1. Take note of the *Project ID* as you will need it later. At this point you have the `project_id`, `client_id` and `client_secret` configuration options needed for Home Assistant.
+1. Take note of the *Project ID* as you will it later. At this point you have the `project_id`, `client_id` and `client_secret` configuration options needed for Home Assistant.
+1. Also Take note of the *Pub/Sub Topic* which is later entered manually as the *Topic Name* when configuring Pub/Sub in a follow up step.
+
+{% enddetails %}
+
+{% details "Enable Device Access APIs [Cloud Console]" %}
1. Go back to the [Google Cloud Console: API & Services](https://console.developers.google.com/apis/dashboard)
@@ -135,10 +154,20 @@ Project**. Note: This is a different type of project from the Device Access proj
1. Search for **Smart Device management** and enable the API.
+{% enddetails %}
+
## Pub/Sub subscriber setup
The next phase is to enable the Pub/Sub API by creating a subscription that can keep Home Assistant informed of events or device changes in near real-time. See [Device Access: Events](https://developers.google.com/nest/device-access/api/events) for the full detailed instructions.
+{% details "Configure Cloud Pub/Sub subscriber_id [Cloud Console]" %}
+
+By the end of this section you will have the `subscriber_id` needed for configuration.
+
+What is Pub/Sub? You can think of your Nest device as the publisher and your Home Assistant as the subscriber. As your Nest device publishes events like a temperature change or motion event, it notifies your Home Assistant subscriber about
+those events so it can record the new value or trigger an automation.
+
+
1. Visit [Enable the Cloud Pub/Sub API](https://console.developers.google.com/apis/library/pubsub.googleapis.com) in the Cloud Console and click **Enable**.
1. Go to the [Google Cloud Platform: Pub/Sub: Subscriptions](https://console.cloud.google.com/cloudpubsub/subscription/list) page and click **Create Subscription**.
@@ -146,7 +175,9 @@ The next phase is to enable the Pub/Sub API by creating a subscription that can
1. You will need to pick a *Subscription ID*.
-1. The *Topic name* should match the topic name in your project in the [Device Access Console](https://console.nest.google.com/device-access/) and typically looks like `projects/sdm-prod/topics/EXAMPLE`. The SDM topic names do not show up by default so make sure to **Enter topic manually**.
+1. Select **Enter Topic Manually** from the topic drop down list.
+1. The *Topic name* comes from the [Device Access Console](https://console.nest.google.com/device-access/) *Topic name*
+and typically looks like `projects/sdm-prod/topics/EXAMPLE`.
1. Select **Pull** as the *Delivery Type*.
@@ -155,11 +186,15 @@ The next phase is to enable the Pub/Sub API by creating a subscription that can
1. Leave the rest of the defaults and click **Create**.
-1. Once created, copy the *Subscription name* which you will want to hold on to as your `subscriber_id` for configuring Home Assistant. This typically looks like `projects/MY-CLOUD-ID/subscriptions/EXAMPLE`. Don't confuse *Subscription name* with *Topic name* since they look similar.
+1. Once created, copy the *Subscription name* which you will want to hold on to as your `subscriber_id` for configuring Home Assistant. This typically looks like `projects/MY-CLOUD-ID/subscriptions/EXAMPLE`.
+1. Don't confuse *Subscription name* with *Topic name* since they look similar. Remember that *Subscription name* is
+your `subscriber_id`.
+
+{% enddetails %}
## Configuration
-Congratulations, you now should have everything you need to configure Home Assistant. Edit your `configuration.yaml` file and populate a `nest` entry in the format of the example [Configuration](#configuration) below.
+You now should have everything needed to configure Nest in Home Assistant. Edit your `configuration.yaml` file and populate a `nest` entry in the format of the example configuration below.
```yaml
# Example configuration.yaml entry
@@ -193,9 +228,25 @@ subscriber_id:
## Device Setup
-Once your developer account is set up and you have a valid `nest` entry in `configuration.yaml`, you need to connect devices with the following steps:
+Once `configuration.yaml` has a valid `nest` entry, you need to add Nest to your Home Assistant instance via the user interface by using this My button:
-1. Using your externally accessible address from the Home Assistant front-end, navigate to **Configuration** then **Integrations**. Click **Add Integration** then locate 'Nest'.
+{% my config_flow_start badge domain=page.ha_domain %}
+
+{% details "Manual configuration steps" %}
+
+1. Browse to your Home Assistant instance using.
+1. In the sidebar click on _**{% my config icon %}**_.
+1. From the configuration menu select: _**{% my integrations icon %}**_.
+1. In the bottom right, click on the
+ _**{% my config_flow_start icon domain=page.ha_domain %}**_ button.
+1. From the list, search and select _**"Nest"**_ and follow the instructions.
+
+{% enddetails %}
+
+The Nest integration setup will walk you through the steps of authorizing
+your Home Assistant to access your account and Nest devices.
+
+{% details "OAuth and Device Authorization steps" %}
1. You should get redirected to Google to choose an account. This should be the same developer account you configured above.
@@ -220,6 +271,7 @@ everything, however, you can leave out any feature you do not wish to use with H
1. If all went well, you are ready to go!
+{% enddetails %}
## Troubleshooting
@@ -227,34 +279,56 @@ everything, however, you can leave out any feature you do not wish to use with H
- Check **Configuration** then **Logs** to see if there are any error messages or misconfigurations then see the error messages below.
-- *Reauthentication required often*: If you are frequently getting logged out, this means your authentication token was revoked by Google. This most likely reason is the *OAuth Consent Screen* is set to *Testing* by default which expires the token after 7 days. Follow the steps above to set it to *Production* to resolve this and reauthorize your integration one more time to get a new token. You may also see this as the error message *invalid_grant: Token has been expired or revoked*. See [Google Identity: Refresh token expiration](https://developers.google.com/identity/protocols/oauth2#expiration) for more reasons on why your token may have expired.
+- *Reauthentication required often*: If you are frequently getting logged out, this means your authentication token was revoked by Google likely due to a misconfiguration.
+
+{% details "Details about reauthentication issues" %}
+
+- This most likely reason is the *OAuth Consent Screen* is set to *Testing* by default which expires the token after 7 days.
+- Follow the steps above to set it to *Production* to resolve this and reauthorize your integration one more time to get a new token.
+- You may also see this as the error message *invalid_grant: Token has been expired or revoked*.
+- See [Google Identity: Refresh token expiration](https://developers.google.com/identity/protocols/oauth2#expiration) for more reasons on why your token may have expired.
+
+{% enddetails %}
- *Thermostat does not appear or is unavailable* happens due to a bug where the SDM API does return the devices. A common fix get the API to work again is to:
- - Restart the Thermostat device. See [How to restart or reset a Nest thermostat](https://support.google.com/googlenest/answer/9247296) for more details.
- - In the official Nest app or on https://home.nest.com: Move the Thermostat to a different or fake/temporary room.
- - Reload the integration in Home Assistant: Navigate to **Configuration** then **Integrations**, click `...` next to *Nest* and choose **Reload**.
+
+{% details "How to restart thermostat" %}
+
+- Restart the Thermostat device. See [How to restart or reset a Nest thermostat](https://support.google.com/googlenest/answer/9247296) for more details.
+- In the official Nest app or on https://home.nest.com: Move the Thermostat to a different or fake/temporary room.
+- Reload the integration in Home Assistant: Navigate to **Configuration** then **Integrations**, click `...` next to *Nest* and choose **Reload**.
+
+{% enddetails %}
- *No devices or entities are created* if the SDM API is not returning any devices for the authorized account. Double-check that GCP is configured correctly to [Enable the API](https://developers.google.com/nest/device-access/get-started#set_up_google_cloud_platform) and authorize at least one device in the OAuth setup flow. If you have trouble here, then you may want to walk through the Google instructions and issue commands directly against the API until you successfully get back the devices.
- *Error 400: redirect_uri_mismatch* means that your OAuth Client ID is not configured to match your Home Assistant URL.
- - To resolve this, copy and paste the redirect URI in the error message (`https://:/auth/external/callback`).
+{% details "Details about resolving redirect_uri_mismatch" %}
- 
+- To resolve this, copy and paste the redirect URI in the error message (`https://:/auth/external/callback`).
- - Go back to the [API Console](https://console.developers.google.com/apis/credentials) and select your *OAuth 2.0 Client ID*.
- - Add the URL to the list of *Authorized redirect URIs* and click **Save** and start the flow over.
+ 
- 
+- Go back to the [API Console](https://console.developers.google.com/apis/credentials) and select your *OAuth 2.0 Client ID*.
+- Add the URL to the list of *Authorized redirect URIs* and click **Save** and start the flow over.
+
+ 
+
+{% enddetails %}
- When configuring the OAuth Client ID redirect URI, you may see an error such as *must end with a public top-level
domain (such as .com or .org)* or *must use a valid domain that is a valid top private domain*. This means that you
may need to change the URL you use to access Home Assistant in order to access your devices.
- - See [Securing](https://www.home-assistant.io/docs/configuration/securing/) Home Assistant for convient solutions e.g. [Nabu Casa](https://www.nabucasa.com/) or Duck DNS.
- - There are subtle [rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) for what types of URLs are allowed, namely that they must use SSL and a publicly known hostname, though your Home Assistant ports do not need to be exposed to the internet.
- - You can use any publicly known hostname you own
- - As a hack, you can use hosts tricks to temporarily assign a public hostname to your Home Assistant IP address.
+{% details "Details about URL configuration" %}
+
+- See [Securing](https://www.home-assistant.io/docs/configuration/securing/) Home Assistant for convenient solutions e.g. [Nabu Casa](https://www.nabucasa.com/) or Duck DNS.
+- There are subtle [rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) for what types of URLs are allowed, namely that they must use SSL and a publicly known hostname, though your Home Assistant ports do not need to be exposed to the internet.
+- You can use any publicly known hostname you own
+- As a hack, you can use hosts tricks to temporarily assign a public hostname to your Home Assistant IP address.
+
+{% enddetails %}
- *Error 403: access_denied* means that you need to visit the [OAuth Consent Screen](https://console.developers.google.com/apis/credentials/consent) and add your Google Account as a *Test User*.
@@ -264,9 +338,9 @@ everything, however, you can leave out any feature you do not wish to use with H
- *Subscriber error: Subscription misconfigured. Expected topic name to match ...* means that the topic name in the Google Cloud Console was entered incorrectly. The topic name comes from the Device Console and must start with `projects/sdm-prod/topics/`. It is easy to make the mistake of creating a new topic rather than manually entering the right topic name.
-- *Not receiving updates* typically means a problem with the subscriber configuration. Changes for things like sensors or thermostat temperature set points should be instantly published to a topic and received by the Home Assistant susbcriber when everything is configured correctly.
+- *Not receiving updates* typically means a problem with the subscriber configuration. Changes for things like sensors or thermostat temperature set points should be instantly published to a topic and received by the Home Assistant subscriber when everything is configured correctly.
-- You can see stats about your subscriber in the [Cloud Console](https://console.cloud.google.com/cloudpubsub/subscription/list) which includes counts of messages published by your devices, and how many have been acknowledged by your Home Assistant subscriber. You can also `View Messages` to see examples of published. Many old unacknowledged messages indicate the subscriber is not receivng the messages and working properly or not connected at all. Double check the `subscriber_id` matches the `Subscription Name`
+- You can see stats about your subscriber in the [Cloud Console](https://console.cloud.google.com/cloudpubsub/subscription/list) which includes counts of messages published by your devices, and how many have been acknowledged by your Home Assistant subscriber. You can also `View Messages` to see examples of published. Many old unacknowledged messages indicate the subscriber is not receiving the messages and working properly or not connected at all. Double check the `subscriber_id` matches the `Subscription Name`
- To aid in diagnosing subscriber problems or camera stream issues it may help to turn up verbose logging by adding some or all of these to your `configuration.yaml` depending on where you are having trouble:
@@ -322,7 +396,7 @@ All Google Nest Cam models and the Google Nest Hello Video Doorbell support devi
- **Motion detected**
- **Person detected**
- **Sound detected**
-- **Doorbell pressed** *for Google Nest Hello Video Doorbell only*
+- **Doorbell pressed** *for Doorbell only*
The lower level Pub/Sub subscriber receives events in real time and internally fires `nest_event` events within Home Assistant:
@@ -333,7 +407,7 @@ The lower level Pub/Sub subscriber receives events in real time and internally f
| Sound detected | [CameraSound](https://developers.google.com/nest/device-access/traits/device/camera-sound#events) | `sound_detected` |
| Doorbell pressed | [DoorbellChime](https://developers.google.com/nest/device-access/traits/device/doorbell-chime#events) | `doorbell_chime` |
-### Example
+## Example
This automation will trigger when a `nest_event` event type with a type of `camera_motion` is received from the specified `device_id`.
@@ -364,8 +438,7 @@ This section contains instructions for the Legacy [Works with Nest](https://deve
New users are not currently able to set up a Works With Nest Developer account. The documentation is preserved here for existing users of the API.
+
-### Sensor
+**Sensor**
The `nest` sensor platform lets you monitor sensors connected to your [Nest](https://nest.com) devices.
@@ -635,7 +708,7 @@ The sensors will be setup if the `nest` integration is configured and the requir
-#### Configuration
+**Configuration**
To enable sensors and customize which sensors are setup, you can extend the [Nest component](/integrations/nest/) configuration in your `configuration.yaml` file with the following settings:
@@ -675,7 +748,7 @@ The following conditions are available by device:
- `color_status`: `gray`, `green`, `yellow` or `red`. Indicates device status by color in the Nest app UI. It is an aggregate condition for battery+smoke+CO states, and reflects the actual color indicators displayed in the Nest app.
- Nest Camera: none
-### Security State
+**Security State**
+
+October! I love this month!
+
+For most of you (just like me), it means winter is coming. We all go back
+inside. An excellent excuse to spent a bit more time on our smart homes, right? 😃
+
+It is also the month of celebrating open source by joining
+[Hacktoberfest][hacktoberfest]! If you make 4 contributions to any open-source
+project (Home Assistant, for example 😘), you'll receive a free t-shirt!
+
+For the Home Assistant project, this means a busy month. However, that doesn't
+matter. It is always great to see new people contributing!
+
+Meanwhile, Home Assistant turned 8 years old already! Wild! And the birthday
+announcement was even wilder (more about that below).
+
+Anyways, about this release: Z-Wave JS is stepping up its game! If you have
+a Z-Wave network and are not using Z-Wave JS yet... well... it might be time
+to bite the bullet and go for it. You won't regret it.
+
+This release also brings the new much-talked-about, Tuya integration
+supported by Tuya themselves! I'm looking forward to how that evolves!
+
+Oh, and of course, we will be live streaming the 2021.10 release party later today!
+Join us at 
+
+## Z-Wave JS updates!
+
+We have two awesome Z-Wave JS updates to share with you this release.
+
+### S2 is now supported
+
+Security is something we all care about; We don't want devices to be tampered
+with, when using things like door locks or motion sensors that trip the alarm
+system. For our Z-Wave devices, this is no different!
+
+As of this release, Home Assistant's Z-Wave JS integration supports S2!
+
+S2 is short for Security 2, a new security standard for Z-Wave devices,
+providing different keys for each device in the network. It is
+the more secure upgrade of the previous S0 version.
+
+Besides improved security, S2 capable devices (in general) are more reliable,
+provide greater battery life and have less latency compared to S0.
+
+The Z-Wave JS integration will automatically pick the best and most optimal
+security method available.
+
+
+Automatically uses the best possible security method when adding a new Z-Wave device.
+
+Some really useful new MDI icons have been added in this release!
+
+
+About two months ago my phone kept buzzing with notifications. I got the kindest tweets after it was announced that I was joining Home Assistant as the first full-time UX designer. That enthusiasm is also reflected in the more than 500 registrations for our [user research group](https://forms.gle/5NSabxHJ3qkp7Vke9) and the many comments we received on design ideas [I've shared on Twitter](https://twitter.com/matthiasdebaat).
+
+## User Experiences
+Home Assistant has a large group of users with a common goal: home automation that puts local control and privacy first. From our [analytics](https://analytics.home-assistant.io) we have over 85,000 users who opted in to share their data anonymously, but we know that there are a lot more. None of these houses and users are alike and may have different, perhaps conflicting interests. Here lies the power of UX. As [Scott Jenson](https://youtu.be/Mjup7Mrj7uU) shared in his fantastic keynote, UX offers perspective. Who are the users? What are their tasks? And what is their pain? What do they want to achieve?
+
+In the coming period, I will investigate what type of smart home users there are, what their needs are and what stands in the way of achieving this.
+
+## Designers
+Last year alone, there were over 8,000 GitHub contributors to Home Assistant. That's really fantastic! With a Designer-to-Developer ratio of 1 per 8,000, it’s easy to get lost in the backend of design and forget the users. This can result in inconsistent user interfaces or designs that could be more user-friendly. For now we’re working on three areas.
+
+### UX contributors
+We want to make it as easy for designers to contribute as it is for developers. There’s a lot a designer can contribute to. For example, making it easier to work with light groups or getting started with automating your house. If you have a design you really think we should look at? Would you like to help build our own Design System? Do you have experience with user testing? Do you have strategic design ideas? Want to organize an online design workshop? Or just want to meet fellow designers? Meet us at [devs_ux Discord channel](/join-chat) or join us on [GitHub discussions](https://github.com/home-assistant/frontend/discussions/10147).
+
+### Tooling
+We want it to be easy to start creating and iterating on design mockups for Home Assistant. We want anyone that is interested to be able to jump in. To achieve this we’ve been hard at work at re-creating the components that make up the Home Assistant interface as a [DesignKit for Figma](https://www.figma.com/community/file/967153512097289521/Home-Assistant-DesignKit). This allows anyone to experiment with the Home Assistant interface and quickly try out different concepts. Try it yourself and feel free to share your designs.
+
+### Documentation
+With clear guidelines, you can ensure speed and quality. That’s why we’re working on design documentation that will be available soon. Its goal is to help designers and developers make better choices. Got suggestions or want to help with our guidelines? Meet us at [devs_ux Discord channel](/join-chat).
diff --git a/source/_redirects b/source/_redirects
index 7b3762d5e8c..e21f15067cf 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -1066,6 +1066,7 @@
/integrations/climate.modbus /integrations/modbus
/integrations/cover.modbus /integrations/modbus
/integrations/fan.xiaomi_miio /integrations/xiaomi_miio
+/integrations/google /integrations/calendar.google
/integrations/light.xiaomi_miio /integrations/xiaomi_miio
/integrations/lovelace /lovelace
/integrations/remote.xiaomi_miio /integrations/xiaomi_miio
@@ -2043,6 +2044,7 @@
/integrations/scene.knx /integrations/knx#scene
/integrations/sensor.knx /integrations/knx#sensor
/integrations/switch.knx /integrations/knx#switch
+/integrations/trace /docs/automation/troubleshooting
/integrations/weather.knx /integrations/knx#weather
/integrations/zigbee /integrations/xbee
/integrations/hassio /hassio
diff --git a/source/blue/index.html b/source/blue/index.html
index 0419884d72e..8a741f05aee 100644
--- a/source/blue/index.html
+++ b/source/blue/index.html
@@ -358,7 +358,7 @@ frontpage_image: /images/frontpage/blue-frontpage.jpg