jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-21 16:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Paulus Schoutsen 2019-10-09 23:42:00 -07:00
commit 60349d3f16
96 changed files with 1245 additions and 211 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
_config.yml
View File

@ -100,9 +100,9 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 99
current_patch_version: 3
date_released: 2019-09-25
current_minor_version: 100
current_patch_version: 0
date_released: 2019-10-10
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
@ -134,5 +134,6 @@ defaults:
# Support for files Jekyll will normally exclude
include:
- ".well-known"
- "_headers"
- "_redirects"
- ".well-known"

2
plugins/environment_variables.rb
View File

@ -2,7 +2,7 @@ module Jekyll
class EnvironmentVariablesGenerator < Generator
def generate(site)
# https://www.netlify.com/docs/continuous-deployment/#build-environment-variables
repo_url = ENV['REPOSITORY_URL'] || 'https://github.com/home-assistant/home-assistant.github.io'
repo_url = ENV['REPOSITORY_URL'] || 'https://github.com/home-assistant/home-assistant.io'
# Rewrite urls if repo url is the ssh format.
if repo_url.start_with? 'git@github.com:'

4
source/_addons/mariadb.markdown
View File

@ -11,14 +11,14 @@ Set up a [MariaDB](https://mariadb.org/) SQL server. It supports multiple databa
"logins": [
{
"username": "hass",
"host": "homeassistant",
"host": "%.local.hass.io",
"password": "securePassword"
}
],
"rights": [
{
"username": "hass",
"host": "homeassistant",
"host": "%.local.hass.io",
"database": "homeassistant",
"grant": "ALL PRIVILEGES ON"
}

16
source/_data/glossary.yml
View File

@ -2,16 +2,22 @@
description: "[Actions](/docs/automation/action/) are events that fires once all triggers and conditions have been met."
- topic: Automation
description: "[Automations](/docs/automation/) offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as a sunset to cause an event, such as a light turning on."
- topic: Binary sensor
description: "A [binary sensor](/integrations/binary_sensor) returns information about things that only have two states - such as on or off."
- topic: Component
description: "Integrations (see below) used to be known as components."
- topic: Condition
description: "[Conditions](/docs/scripts/conditions/) are an optional part of an automation that will prevent an action from firing if they are not met."
- topic: Cookbook
description: "The [Cookbook](/cookbook/) contains a set of configuration examples of Home Assistant from the community."
- topic: Cover
description: "[Covers](/integrations/cover) are devices such as blinds, garage doors, etc than can be opened and closed and optionally set to a specific position."
- topic: Customize
description: "[Customization](/docs/configuration/customizing-devices/) allows you to overwrite the default parameter of your devices in the configuration."
- topic: Device
description: "A device is usually a physical unit which can do or observe something."
- topic: Device tracker
description: "[Device trackers](/integrations/device_tracker) are used to track the presence, or location, of a device."
- topic: Discovery
description: "[Discovery](/integrations/discovery/) is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered."
- topic: Entity
@ -30,6 +36,10 @@
description: "[Integrations](/integrations/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
- topic: Lovelace
description: "[Lovelace](/lovelace/) is the name of the current frontend."
- topic: Light
description: "A [light](/integrations/light) has a brightness you can control, and optionally color temperature or RGB color control."
- topic: Notification
description: "You can use [notifications](/integrations/#notifications) to send messages, pictures, and more, to devices."
- topic: Packages
description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configurations together."
- topic: Platform
@ -38,11 +48,17 @@
description: "[Scenes](/integrations/scene/) capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red."
- topic: Script
description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on."
- topic: Sensor
description: "[Sensors](/integrations/sensor) return information about a thing, for instance the level of water in a tank."
- topic: Service
description: "[Services](/docs/scripts/service-calls/) are called to perform actions."
- topic: Switch
description: "[Switches](/integrations/switch) are things that have two states you can select between, such as turning on or off a socket."
- topic: Template
description: "A [template](/docs/automation/templating/) is an automation definition that can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions."
- topic: Trigger
description: "A [trigger](/docs/automation/trigger/) is a set of values or conditions of a platform that are defined to cause an automation to run."
- topic: TTS
description: "TTS ([text to speech](/integrations/tts) allows Home Assistant to talk to you."
- topic: Zone
description: "[Zones](/integrations/zone/) are areas that can be used for presence detection."

2
source/_docs/automation/troubleshooting.markdown
View File

@ -28,7 +28,7 @@ Please note that if you click on **Trigger** of an automation in the frontend, *
All this makes that Trigger feature pretty limited and nearly useless for debugging purposes so you need to find another way.
Make sure you check and adapt to your circumstances appropriate examples from Automation Trigger, Conditions and Actions.
It is also useful to go to **Configuration** -> **Server Control** and click on **Check Config** button in Configuration validation section to make sure there are no syntax errors before restarting Home Assistant.
It is also useful to go to **Configuration** -> **Server Control** and click on **Check Config** button in Configuration validation section to make sure there are no syntax errors before restarting Home Assistant. In order for **Check Config** to be visible, you must enable **Advanced Mode** on your user profile.
If your automation uses templates in any part, you can do the following to make sure it works as expected:

3
source/_docs/configuration/troubleshooting.markdown
View File

@ -18,11 +18,12 @@ If you have incorrect entries in your configuration files you can use the [`chec
#### Problems with the configuration
One of the most common problems with Home Assistant is an invalid `configuration.yaml` file.
One of the most common problems with Home Assistant is an invalid `configuration.yaml` or other configuration file.
- You can test your configuration using the command line with: `hass --script check_config`.
- On Hass.io you can use the [hassio command](/hassio/commandline/#home-assistant): `hassio homeassistant check`.
- On Docker you can use `docker exec home-assistant python -m homeassistant --script check_config --config /config` - where `homeassistant` is the name of the container.
- The configuration files, including `configuration.yaml` must be UTF-8 encoded. If you see error like `'utf-8' codec can't decode byte`, edit the offending configuration and re-save it as UTF-8.
- You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).

2
source/_docs/ecosystem/backup/backup_github.markdown
View File

@ -159,7 +159,7 @@ Example .travis.yml
```yaml
language: python
python:
- "3.5"
- "3.7"
before_install:
- mv travis_secrets.yaml secrets.yaml
- sudo apt-get install -y libudev-dev

11
source/_docs/installation/fedora.markdown
View File

@ -11,12 +11,6 @@ Install the development package of Python.
sudo dnf -y install python3-devel redhat-rpm-config
```
and Home Assistant itself.
```bash
pip3 install homeassistant
```
To isolate the Home Assistant installation a [`venv`](https://docs.python.org/3/library/venv.html) is handy. First create a new directory to store the installation and adjust the permissions.
```bash
@ -24,19 +18,20 @@ sudo mkdir -p /opt/homeassistant
sudo useradd -rm homeassistant -G dialout
sudo chown -R homeassistant:homeassistant /opt/homeassistant
```
Now switch to the new directory, setup the `venv`, and activate it.
```bash
sudo -u homeassistant -H -s
cd /opt/homeassistant
python3.6 -m venv .
python3.8 -m venv .
source bin/activate
```
Install Home Assistant itself.
```bash
$ pip3 install homeassistant colorlog
pip3 install homeassistant colorlog
```
Check the [autostart](/docs/autostart/systemd/) section in the documentation for further details and the [Firewall section](/docs/installation/troubleshooting/#no-access-to-the-frontend) if you want to access your Home Assistant installation.

37
source/_docs/installation/freenas.markdown
View File

@ -14,13 +14,15 @@ pw groupadd -n homeassistant -g 8123
echo 'homeassistant:8123:8123::::::/bin/csh:' | adduser -f -
```
Install the necessary Python packages:
Install the necessary Python packages and virtualenv:
```bash
pkg update
pkg upgrade
pkg install -y python37 py37-sqlite3 ca_root_nss
python3.7 -m ensurepip
pip3 install --upgrade pip
pip3 install --upgrade virtualenv
```
Create the configuration directory:
@ -45,11 +47,38 @@ cd /usr/local/share/homeassistant
virtualenv -p python3.7 .
source ./bin/activate.csh
pip3 install homeassistant
```
While still in the `venv`, start Home Assistant to populate the configuration directory.
```bash
hass --open-ui
```
Wait until you see:
```bash
(MainThread) [homeassistant.core] Starting Home Assistant
```
Then escape and exit the `venv`.
```bash
deactivate
exit
```
Create an `rc.d` script for the system-level service that enables Home Assistant to start when the jail starts. Create a file at `/usr/local/etc/rc.d/homeassistant` with the following contents:
Create the directory and the `rc.d` script for the system-level service that enables Home Assistant to start when the jail starts.
```bash
mkdir /usr/local/etc/rc.d/
```
Then create a file at `/usr/local/etc/rc.d/homeassistant` and insert the content below:
```bash
vi /usr/local/etc/rc.d/homeassistant
```
```bash
#!/bin/sh
@ -71,7 +100,7 @@ Create an `rc.d` script for the system-level service that enables Home Assistant
# empty string as this will cause the daemon to run with group wheel.
# Default: homeassistant
# homeassistant_config_dir: Directory where config files are located.
# Default: /usr/local/homeassistant
# Default: /usr/home/homeassistant/.homeassistant
# homeassistant_install_dir: Directory where Home Assistant is installed.
# Default: /usr/local/share/homeassistant
#
@ -89,7 +118,7 @@ load_rc_config ${name}
: ${homeassistant_enable:="NO"}
: ${homeassistant_user:="homeassistant"}
: ${homeassistant_group:="homeassistant"}
: ${homeassistant_config_dir:="/usr/local/homeassistant"}
: ${homeassistant_config_dir:="/usr/home/homeassistant/.homeassistant"}
: ${homeassistant_install_dir:="/usr/local/share/homeassistant"}
command="/usr/sbin/daemon"

2
source/_docs/mqtt/broker.markdown
View File

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

2
source/_docs/scripts/conditions.markdown
View File

@ -241,7 +241,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 setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the [OwnTracks platform](/integrations/device_tracker.owntracks/) and the [iCloud platform](/integrations/device_tracker.icloud/).
Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
```yaml
condition:

8
source/_docs/z-wave/devices.markdown
View File

@ -33,9 +33,9 @@ The key improvements are:
### Z-Wave Security 2
From 2 April 2017 all newly approved Z-Wave devices will have to support the Security 2 (S2) framework. At the time of writing this (March 2018) OpenZWave does not support the S2 framework.
From 2 April 2017 all newly approved Z-Wave devices will have to support the Security 2 (S2) framework. At the time of writing this (October 2019) OpenZWave does not support the S2 framework.
## Device power
## Device Power
Your Z-Wave mesh network is built with the devices that are mains powered (whether directly, or via a USB adapter), these relay traffic for other nodes, building the network. These devices are always awake and you can query them, or send configuration changes, at any time.
@ -65,8 +65,8 @@ Polling needs to be enabled per device, you can control this through the *pollin
The Central Scene command class isn't yet supported in OpenZWave (there is [work in progress](https://github.com/OpenZWave/open-zwave/pull/1125) to provide it it), though Home Assistant has introduced some support with [change 9178](https://github.com/home-assistant/home-assistant/pull/9178) which was part of 0.53 and [documented here](/docs/z-wave/device-specific/#homeseer-switches).
## Is my device supported
## Is my device supported?
You can check to see if OpenZWave supports your particular device by looking at the [OpenZWave github](https://github.com/OpenZWave/open-zwave/tree/master/config). Be aware that being listed here doesn't mean that it will be supported in Home Assistant, since the version of OpenZWave used by Home Assistant will often lag the github by a few months.
You can check to see if OpenZWave supports your particular device by looking at the [OpenZWave 1.4 github](https://github.com/OpenZWave/open-zwave/tree/1.4/config). Be aware that being listed here doesn't mean that it will be supported in Home Assistant, since the version of OpenZWave used by Home Assistant will often lag the github by a few months.
Even if your device isn't listed there, it's likely that it will still work as expected as long as the device complies with the Z-Wave standards. The OpenZWave wiki describes how [you can add support](https://github.com/OpenZWave/open-zwave/wiki/Adding-Devices) for your device if it isn't listed.

20
source/_headers Normal file
View File

@ -0,0 +1,20 @@
/*
Cache-Control: public, max-age: 0, s-max-age=3600, must-revalidate
Content-Security-Policy: form-action https:
Feature-Policy: vibrate 'none'; geolocation 'none'; midi 'none'; microphone 'none'; camera 'none'; magnetometer 'none'; gyroscope 'none'; speaker 'none'; vibrate 'none'; payment 'none'
Referrer-Policy: strict-origin-when-cross-origin
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
/*.css
Cache-Control: public, max-age: 604800, s-max-age=604800
/*.js
Cache-Control: public, max-age: 604800, s-max-age=604800
/assets/*
Cache-Control: public, max-age: 0, s-max-age=604800, must-revalidate
/fonts/*
Cache-Control: public, max-age: 1800, s-max-age=604800, must-revalidate
/images/*
Cache-Control: public, max-age: 1800, s-max-age=604800, must-revalidate
/static/*
Cache-Control: public, max-age: 1800, s-max-age=604800, must-revalidate

2
source/_includes/javascripts/scripts.html
View File

@ -5,7 +5,7 @@ g.src=('https:'==location.protocol?'//ssl':'//www')+'.google-analytics.com/ga.js
s.parentNode.insertBefore(g,s)}(document,'script'));
</script>
<script type="text/javascript" src="/javascripts/prism.js"></script>
<script src="/javascripts/prism.js?{{ site.time | date: '%s' }}" type="text/javascript"></script>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/2/docsearch.min.css" />
<script type="text/javascript" src="https://cdn.jsdelivr.net/docsearch.js/2/docsearch.min.js"></script>

4
source/_includes/site/head.html
View File

@ -28,8 +28,8 @@
<meta name="twitter:description" content="{{ page.description | default: site.description | strip_html | truncate: 200 }}">
<meta name="twitter:image" content="{{ page.og_image | default: "/images/default-social.png" | prepend: site.url }}">
<link href="/stylesheets/prism.css" rel="stylesheet">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/stylesheets/prism.css?{{ site.time | date: '%s' }}" rel="stylesheet">
<link href="/stylesheets/screen.css?{{ site.time | date: '%s' }}" media="screen, projection, print" rel="stylesheet">
<link href="{{ site.subscribe_rss }}" rel="alternate" title="{{ site.title }}" type="application/atom+xml">
<link rel='shortcut icon' href='/images/favicon.ico' />
<link rel='icon' type='image/png' href='/images/favicon-192x192.png' sizes='192x192' />

6
source/_integrations/anthemav.markdown
View File

@ -12,10 +12,10 @@ Both [Anthem]'s current and last generation of A/V Receivers and Processors supp
## Supported Models
* MRX 520, MRX 720, MRX 1120, and AVM 60
* MRX 310, MRX 510, MRX 710
* [MRX 520](https://www.anthemav.com/products-current/series=mrx-series-gen3/model=mrx-520/page=overview), [MRX 720](https://www.anthemav.com/products-current/collection=performance/model=mrx-720/page=overview), [MRX 1120](https://www.anthemav.com/products-current/collection=performance/model=mrx-1120/page=overview), and [AVM 60](https://www.anthemav.com/products-current/model=avm-60/page=overview)
* [MRX 310](https://www.anthemav.com/products-archived/type=av-receiver/model=mrx-310/page=overview), [MRX 510](https://www.anthemav.com/products-archived/series=mrx-series/model=mrx-510/page=overview), [MRX 710](https://www.anthemav.com/products-archived/type=av-receiver/model=mrx-710/page=overview)
Support is provided through the Python [anthemav] module. Older, RS-232 serial-based units like the D2v use a different protocol entirely and are not currently supported.
Support is provided through the Python [anthemav] module. Older, RS-232 serial-based units like the [D2v](https://www.anthemav.com/products-current/type=av-processor/model=d2v-3d/page=overview) use a different protocol entirely and are not currently supported.
[Anthem]: http://www.anthemav.com/
[anthemav]: https://github.com/nugget/python-anthemav

2
source/_integrations/binary_sensor.mqtt.markdown
View File

@ -81,7 +81,7 @@ unique_id:
required: false
type: string
device_class:
description: Sets the [class of the device](/integrations/binary_sensor/), changing the device state and icon that is displayed on the frontend.
description: Sets the [class of the device](/integrations/binary_sensor/#device-class), changing the device state and icon that is displayed on the frontend.
required: false
type: string
expire_after:

4
source/_integrations/configurator.markdown
View File

@ -18,6 +18,6 @@ The configurator integration allows integrations to request information from the
- Input fields can be defined with a description, and optional type
- It will trigger a callback when the button is pressed
The Hue integration in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo integration](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/integrations/demo) for a simple example.
The Hue integration in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo integration](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/demo) for a simple example.
See [the source](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/integrations/configurator) for more details on how to use the configurator integration.
See [the source](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/configurator) for more details on how to use the configurator integration.

2
source/_integrations/dialogflow.markdown
View File

@ -63,7 +63,7 @@ When activated, the [`alexa` integration](/integrations/alexa/) will have Home A
## Examples
Download [this zip](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/assets/HomeAssistant_APIAI.zip) and load it in your Dialogflow agent (**Settings** -> **Export and Import**) for examples intents to use with this configuration:
Download [this zip](https://github.com/home-assistant/home-assistant.io/blob/next/source/assets/HomeAssistant_APIAI.zip) and load it in your Dialogflow agent (**Settings** -> **Export and Import**) for examples intents to use with this configuration:
{% raw %}
```yaml

2
source/_integrations/doods.markdown
View File

@ -4,7 +4,7 @@ description: "Detect and recognize objects with DOODS."
ha_category:
- Image Processing
ha_iot_class: Local Polling
ha_release: 0.100
ha_release: "0.100"
---
The `doods` image processing platform allows you to detect and recognize objects in a camera image using [DOODS](https://github.com/snowzach/doods/). The state of the entity is the number of objects detected, and recognized objects are listed in the `summary` attribute along with quantity. The `matches` attribute provides the confidence `score` for recognition and the bounding `box` of the object for each detection category.

0
source/_integrations/switch.pca.markdown → source/_integrations/elv.markdown
View File

38
source/_integrations/fan.xiaomi_miio.markdown
View File

@ -311,7 +311,7 @@ Set the fan speed/operation mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------------------|
| `entity_id` | yes | Only act on a specific air purifier. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `speed` | no | Fan speed. Valid values are 'Auto', 'Silent', 'Favorite' and 'Idle' |
### Service `fan.xiaomi_miio_set_buzzer_on` (Air Purifier Pro excluded)
@ -320,7 +320,7 @@ Turn the buzzer on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_buzzer_off` (Air Purifier Pro excluded)
@ -328,7 +328,7 @@ Turn the buzzer off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_led_on` (Air Purifiers only)
@ -336,7 +336,7 @@ Turn the led on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_led_off` (Air Purifiers only)
@ -344,7 +344,7 @@ Turn the led off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_child_lock_on`
@ -352,7 +352,7 @@ Turn the child lock on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_child_lock_off`
@ -360,7 +360,7 @@ Turn the child lock off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_led_brightness` (Air Purifier 2S and Air Purifier Pro excluded)
@ -368,7 +368,7 @@ Set the led brightness. Supported values are 0 (Bright), 1 (Dim), 2 (Off).
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `brightness` | no | Brightness, between 0 and 2. |
### Service `fan.xiaomi_miio_set_favorite_level` (Air Purifiers only)
@ -377,7 +377,7 @@ Set the favorite level of the operation mode "favorite".
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `level` | no | Level, between 0 and 16. |
### Service `fan.xiaomi_miio_set_auto_detect_on` (Air Purifier 2S and Air Purifier Pro only)
@ -386,7 +386,7 @@ Turn the auto detect on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_auto_detect_off` (Air Purifier 2S and Air Purifier Pro only)
@ -394,7 +394,7 @@ Turn the auto detect off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_learn_mode_on` (Air Purifier 2 only)
@ -402,7 +402,7 @@ Turn the learn mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_learn_mode_off` (Air Purifier 2 only)
@ -410,7 +410,7 @@ Turn the learn mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_volume` (Air Purifier Pro only)
@ -418,7 +418,7 @@ Set the sound volume.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `volume` | no | Volume, between 0 and 100. |
### Service `fan.xiaomi_miio_reset_filter` (Air Purifier 2 only)
@ -427,7 +427,7 @@ Reset the filter lifetime and usage.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_extra_features` (Air Purifier only)
@ -435,7 +435,7 @@ Set the extra features.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `features` | no | Integer, known values are 0 and 1. |
### Service `fan.xiaomi_miio_set_target_humidity` (Air Humidifier only)
@ -444,7 +444,7 @@ Set the target humidity.
| Service data attribute | Optional | Description |
|---------------------------|----------|-----------------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `humidity` | no | Target humidity. Allowed values are 30, 40, 50, 60, 70 and 80 |
### Service `fan.xiaomi_miio_set_dry_on` (Air Humidifier CA only)
@ -453,7 +453,7 @@ Turn the dry mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_dry_off` (Air Humidifier CA only)
@ -461,4 +461,4 @@ Turn the dry mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miIO fan entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |

8
source/_integrations/google_maps.markdown
View File

@ -28,6 +28,10 @@ device_tracker:
username: YOUR_USERNAME
```
Once enabled and you have rebooted devices discovered through this integration wil be listed in the `known_devices.yaml`file within your configuration directory.
They will be created with indentifiers like `google_maps_<numeric_id>`. To be able to properly track entities you must set the `track` attribute to `true`.
{% configuration %}
username:
description: The email address for the Google account that has access to your shared location.
@ -43,3 +47,7 @@ scan_interval:
default: 60
type: integer
{% endconfiguration %}
<div class='note'>
As of release 0.97 Google passwords are no longer required in your configuration. Users coming from earlier releases should only remove the password entry from their configuration file (username is still required) and restart Home Assistant. The cookie file previously generated should still be valid and will allow the tracker to continue functioning normally until the cookie is invalidated.
</div>

2
source/_integrations/input_boolean.markdown
View File

@ -37,7 +37,7 @@ input_boolean:
type: boolean
default: false
icon:
description: Icon to display for the component.
description: Icon to display in front of the input element in the frontend.
required: false
type: icon
{% endconfiguration %}

2
source/_integrations/input_datetime.markdown
View File

@ -54,7 +54,7 @@ input_datetime:
type: boolean
default: false
icon:
description: Icon to display in the frontend.
description: Icon to display in front of the input element in the frontend.
required: false
type: icon
initial:

10
source/_integrations/input_number.markdown
View File

@ -8,12 +8,6 @@ ha_release: 0.55
ha_qa_scale: internal
---
<div class='note'>
Before version 0.55 this integration was known as `input_slider` and did not have the `mode` configuration option. Also, service `select_value` is now `set_value`.
</div>
The `input_number` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well.
To enable this input number in your installation, add the following lines to your `configuration.yaml`:
@ -58,7 +52,7 @@ input_number:
description: Initial value when Home Assistant starts.
required: false
type: float
default: 0
default: The value at shutdown
step:
description: Step value for the slider. Smallest value `0.001`.
required: false
@ -74,7 +68,7 @@ input_number:
required: false
type: string
icon:
description: Icon to display in front of the box/slider in the frontend.
description: Icon to display in front of the input element in the frontend.
required: false
type: icon
{% endconfiguration %}

2
source/_integrations/input_select.markdown
View File

@ -49,7 +49,7 @@ input_select:
type: map
default: First element of options
icon:
description: Icon to display for the component.
description: Icon to display in front of the input element in the frontend.
required: false
type: icon
{% endconfiguration %}

4
source/_integrations/input_text.markdown
View File

@ -53,6 +53,10 @@ input_text:
required: false
type: string
default: empty
icon:
description: Icon to display in front of the input element in the frontend.
required: false
type: icon
pattern:
description: Regex pattern for client side validation.
required: false

0
source/_integrations/pizone.markdown → source/_integrations/izone.markdown
View File

2
source/_integrations/life360.markdown
View File

@ -17,7 +17,7 @@ You must first [create a Life360 account](https://www.life360.com/websignup).
Then in the Home Assistant user interface (UI), click on Configuration in the left pane, then on Integrations and then on the yellow circle in the lower-right corner to "Set up a new integration." Scroll through the list and click on Life360. Enter your Life360 username and password and click SUBMIT. You can add as many Life360 accounts as you like.
If you would like to set any advanced options, see the following section. You may want to do this before entering your Life360 account information in the UI, or you can change it at any time. You can also enter your account information in the configuration file (in addition to, or instead of, the UI) if you prefer.
If you would like to set any advanced options, see the following section. You may want to do this before entering your Life360 account information in the UI, or you can change it at any time. Any of the advanced options you want to set from the section below will need to be set manually in your configuration.yaml file. They are not able to be set from the UI. You can also enter your account information in the configuration file (in addition to, or instead of, the UI) if you prefer.
{% configuration %}
accounts:

4
source/_integrations/light.markdown
View File

@ -1,5 +1,5 @@
---
title: "Lights"
title: "Light"
description: "Instructions on how to setup your lights with Home Assistant."
logo: home-assistant.png
ha_category:
@ -26,7 +26,7 @@ Most lights do not support all attributes. You can check the integration documen
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`s of lights. Else targets all.
| `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state.
| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/integrations/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten.
| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten.
| `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100.
| `xy_color` | yes | A list containing two floats representing the xy color you want the light to be. Two comma-separated floats that represent the color in XY. You can find a great chart here: [Hue Color Chart](https://developers.meethue.com/documentation/core-concepts#color_gets_more_complicated).
| `rgb_color` | yes | A list containing three integers between 0 and 255 representing the RGB color you want the light to be. Three comma-separated integers that represent the color in RGB, within square brackets. Note that the specified RGB value will not change the light brightness, only the color.

16
source/_integrations/light.xiaomi_miio.markdown
View File

@ -138,7 +138,7 @@ Set one of the 4 available fixed scenes.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
| `scene` | no | Scene, between 1 and 4. |
### Service `light.xiaomi_miio_set_delayed_turn_off`
@ -147,7 +147,7 @@ Delayed turn off.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
| `time_period` | no | Time period for the delayed turn off. |
### Service `light.xiaomi_miio_reminder_on` (Eyecare Smart Lamp 2 only)
@ -156,7 +156,7 @@ Enable the eye fatigue reminder/notification.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `light.xiaomi_miio_reminder_off` (Eyecare Smart Lamp 2 only)
@ -164,7 +164,7 @@ Disable the eye fatigue reminder/notification.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `light.xiaomi_miio_night_light_mode_on` (Eyecare Smart Lamp 2 only)
@ -172,7 +172,7 @@ Turn the smart night light mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `light.xiaomi_miio_night_light_mode_off` (Eyecare Smart Lamp 2 only)
@ -180,7 +180,7 @@ Turn the smart night light mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `light.xiaomi_miio_eyecare_mode_on` (Eyecare Smart Lamp 2 only)
@ -188,7 +188,7 @@ Turn the eyecare mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `light.xiaomi_miio_eyecare_mode_off` (Eyecare Smart Lamp 2 only)
@ -196,4 +196,4 @@ Turn the eyecare mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on a specific light. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |

4
source/_integrations/nello.markdown
View File

@ -9,6 +9,10 @@ ha_release: 0.52
ha_iot_class: Cloud Polling
---
<div class="note warning">
Locumi Labs, the manufacturer of Nello, entered insolvency on the 2<sup>nd</sup> of October 2019 closed their cloud service. Since Nello One locks require this cloud service, the locks will cease to operate as of the 18<sup>th</sup> October 2019.
</div>
The `nello` platform allows you to control [Nello](https://www.nello.io) intercoms.
To get started you need to create a secondary Nello account and authorize it to access your lock(s).

2
source/_integrations/samsungtv.markdown
View File

@ -116,7 +116,7 @@ Currently tested but not working models:
None of the 2014 (H) and 2015 (J) model series (e.g., J5200) will work, since Samsung have used a different (encrypted) type of interface for these.
If your model is not on the list then give it a test, if everything works correctly then add it to the list on
[GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_integrations/samsungtv.markdown).
[GitHub](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/samsungtv.markdown).
The first letter (U, P, L, H & K) represent the screen type, e.g., LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size.
If you add your model remember to remove these first 4 characters before adding to the list.

4
source/_integrations/sensor.command_line.markdown
View File

@ -75,7 +75,7 @@ sensor:
- platform: command_line
name: HD Temperature
command: "hddtemp -n /dev/sda"
# If errors occur, remove degree symbol below
# If errors occur, make sure configuration file is encoded as UTF-8
unit_of_measurement: "°C"
```
@ -90,7 +90,7 @@ sensor:
- platform: command_line
name: CPU Temperature
command: "cat /sys/class/thermal/thermal_zone0/temp"
# If errors occur, remove degree symbol below
# If errors occur, make sure configuration file is encoded as UTF-8
unit_of_measurement: "°C"
value_template: '{{ value | multiply(0.001) | round(1) }}'
```

2
source/_integrations/sensor.mqtt.markdown
View File

@ -89,7 +89,7 @@ unique_id:
required: false
type: string
device_class:
description: The type/class of the sensor to set the icon in the frontend.
description: The [type/class](/integrations/sensor/#device-class) of the sensor to set the icon in the frontend.
required: false
type: device_class
default: None

15
source/_integrations/solaredge_local.markdown
View File

@ -11,14 +11,17 @@ ha_iot_class: Local Polling
The `solaredge_local` platform uses the local API available on some SolarEdge Inverters to allow you to get details from your SolarEdge solar power setup and integrate these into your Home Assistant installation.
Only specific models support the local API. The local API is available on the SExxxxH-US models with SetApp as well as European three-phase inverters SEXXK-XXXTXBXX4 models with SetApp like SE3K-E10K, SE12.5K-SE27.6K and SE33.3K. Please check the datasheets carefully if in the section "Additional Features", sub-section "Inverter Commissioning" is present the following line "With the SetApp mobile application using built-in Wi-Fi access point for local connection".
Only specific models support the local API. The local API is available on inverters that do not have an LCD character screen. You can also check the datasheets if in the section "Additional Features", sub-section "Inverter Commissioning" is present the following line "With the SetApp mobile application using built-in Wi-Fi access point for local connection". These inverters also have a part number that ends with a 4. For example: SEXXK-XXXXXBXX4 or SEXXXXH-XXXXXBXX4
You can check by finding the IP address of your inverter and visiting it in a browser. If it supports the local API, you'll see the SolarEdge logo and a "Commissioning" menu.
You can check if the local API works by finding the IP address of your inverter and visiting it in a browser. If it supports the local API, you'll see a HTML page with the SolarEdge logo and a "Commissioning" menu.
<div class='note'>
If your inveter does not support the local API, you can use the [cloud based version](/integrations/solaredge/) instead.
If your inverter does not support the local API, you can use the [cloud based version](/integrations/solaredge/)
</div>
## Configuration
To use the SolarEdge sensors in your installation, add the following to your configuration.yaml file:
@ -26,8 +29,8 @@ To use the SolarEdge sensors in your installation, add the following to your con
```yaml
# Example configuration.yaml entry
sensor:
platform: solaredge_local
ip_address: IP_ADDRESS
- platform: solaredge_local
ip_address: IP_ADDRES
```
{% configuration %}
@ -64,5 +67,7 @@ sensor:
sensors:
solaredge_energy_this_year_template:
value_template: "{{ (states('sensor.solaredge_energy_this_year') | float / 1000) | round(2) }}"
unit_of_measurement: 'KWh'
icon_template: "mdi:solar-power"
```
{% endraw %}

4
source/_integrations/speedtestdotnet.markdown
View File

@ -15,9 +15,11 @@ Enabling this integration will automatically create the Speedtest.net Sensors fo
By default, a speed test will be run every hour. The user can change the update frequency in the configuration by defining the `scan_interval` for a speed test to run.
Most Speedtest.net servers require TCP port 8080 outbound to function. Without this port open you may experience significant delays or no results at all. See note on their [help page](https://www.speedtest.net/help).
## Configuration
For the `server_id` check the list of [available servers](https://www.speedtest.net/speedtest-servers.php).
For the `server_id` check the list of [available servers](http://www.speedtestserver.com).
To add Speedtest.net sensors to your installation, add the following to your `configuration.yaml` file:

4
source/_integrations/switch.markdown
View File

@ -1,5 +1,5 @@
---
title: "Switches"
title: "Switch"
description: "Instructions on how to set up your switches with Home Assistant."
logo: home-assistant.png
ha_category:
@ -23,4 +23,4 @@ In the frontend open the sidebar. At the bottom, under **Developer Tools**, clic
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Only act on a specific switch. Otherwise, it targets all switches.
| `entity_id` | no | The entity ID of the switch to control. To target all switches, set the entity ID to `all`|

8
source/_integrations/switch.xiaomi_miio.markdown
View File

@ -94,7 +94,7 @@ Turn the wifi led on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miio switch entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
### Service `switch.xiaomi_miio_set_wifi_led_off` (Power Strip only)
@ -102,7 +102,7 @@ Turn the wifi led off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miio switch entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
### Service `switch.xiaomi_miio_set_power_price` (Power Strip)
@ -110,7 +110,7 @@ Set the power price.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miio switch entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
| `price` | no | Power price, between 0 and 999. |
### Service `switch.xiaomi_miio_set_power_mode` (Power Strip V1 only)
@ -119,5 +119,5 @@ Set the power mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------------|
| `entity_id` | yes | Only act on a specific Xiaomi miio switch entity. Else targets all. |
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
| `mode` | no | Power mode, valid values are 'normal' and 'green' |

2
source/_integrations/todoist.markdown
View File

@ -89,7 +89,7 @@ As you can see, there are 4 custom projects here:
You can mix-and-match these attributes to create all sorts of custom projects. You can even use [IFTTT](https://ifttt.com/todoist) to create a task with a certain label, then have Home Assistant do some kind of automation when a task with that label comes due.
Home Assistant does its best to [determine what task in each project is "most" important](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/integrations/todoist/calendar.py), and it's that task which has its state reported. You can access the other tasks you have due soon via the `all_tasks` array (see below).
Home Assistant does its best to [determine what task in each project is "most" important](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/todoist/calendar.py), and it's that task which has its state reported. You can access the other tasks you have due soon via the `all_tasks` array (see below).
### Sensor attributes

6
source/_integrations/updater.markdown
View File

@ -12,6 +12,12 @@ The `updater` binary sensor will check daily for new releases. The state will be
The updater integration will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the time zone, Python version and operating system information. No identifiable information (i.e., IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python [source code](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/integrations/updater).
<div class='note'>
The `updater` binary sensor will wait one hour after startup until it performs the first update. For this period it will be in the state `unavailable`. After that it will check once a day for new releases.
</div>
## Configuration
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:

12
source/_integrations/vacuum.xiaomi_miio.markdown
View File

@ -68,7 +68,7 @@ Start the remote control mode of the robot. You can then move it with `remote_co
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------|
| `entity_id` | yes | Only act on a specific robot; default targets all |
| `entity_id` | no | Only act on a specific robot |
### Service `vacuum.xiaomi_remote_control_stop`
@ -76,7 +76,7 @@ Exit the remote control mode of the robot.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------|
| `entity_id` | yes | Only act on a specific robot; default targets all |
| `entity_id` | no | Only act on a specific robot |
### Service `vacuum.xiaomi_remote_control_move`
@ -84,7 +84,7 @@ Remote control the robot. Please ensure you first set it in remote control mode
| Service data attribute | Optional | Description |
|---------------------------|----------|-----------------------------------------------------------|
| `entity_id` | yes | Only act on a specific robot; default targets all |
| `entity_id` | no | Only act on a specific robot |
| `velocity` | no | Speed: between -0.29 and 0.29 |
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
| `duration` | no | The number of milliseconds that the robot should move for |
@ -95,7 +95,7 @@ Enter remote control mode, make one move, stop, and exit remote control mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|-----------------------------------------------------------|
| `entity_id` | yes | Only act on a specific robot; default targets all |
| `entity_id` | no | Only act on a specific robot |
| `velocity` | no | Speed: between -0.29 and 0.29 |
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
| `duration` | no | The number of milliseconds that the robot should move for |
@ -106,9 +106,9 @@ Start the cleaning operation in the areas selected for the number of repeats ind
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | yes | Only act on specific robot; default targets all |
| `entity_id` | no | Only act on a specific robot |
| `zone` | no | List of zones. Each zone is an array of 4 integer value. Example: [[23510,25311,25110,26361]] |
| `repeats` | no | Number of cleaning repeats for each zone between 1 and 3. |
| `repeats` | no | Number of cleaning repeats for each zone between 1 and 3. |
Example of `vacuum.xiaomi_clean_zone` use:

10
source/_integrations/withings.markdown
View File

@ -2,7 +2,7 @@
title: "Withings"
description: "Instructions on how to integrate Withings health products within Home Assistant."
logo: withings.png
ha_category:
ha_category:
- Health
- Sensor
ha_release: 0.99
@ -15,7 +15,7 @@ The `withings` sensor platform consumes data from various health products produc
### Step 1 - Create a Withings Account
You must have a developer account to distribute the data. [Create a free development account](https://account.withings.com/partner/add_oauth2).
You must have a developer account to distribute the data. [Create a free development account](https://account.withings.com/partner/add_oauth2).
Values for your account:
@ -42,7 +42,7 @@ Withings supports multiple profiles per account. Each profile has a person's nam
### Step 3 - Authorize Home Assistant
- Confirm your YAML configuration is valid by using the `Check Config` tool.
- Confirm your YAML configuration is valid by using the `Check Config` tool (see note).
- Restart Home Assistant.
- Go to the integrations page.
- Add a Withings integration.
@ -50,12 +50,14 @@ Withings supports multiple profiles per account. Each profile has a person's nam
- On the Withings site, choose the profile you selected in the previous step (if prompted).
- Note: It's important you select the same profile from the previous step. Choosing a different one will result in Home Assistant displaying data for profile 2, but it will be labeled as profile 1.
- Authorize the application. Your browser will redirect you to your Home Assistant URL.
- Note: If you get a browser error saying the site is inaccessible, you can modify the
- Note: If you get a browser error saying the site is inaccessible, you can modify the
`http://domain` portion of the URL to something you know is accessible, locally or publically. For example, `http://localhost:8123`.
This occurs when the base URL provided by Home Assistant to Withings is not accessible to the outside world.
Changing the domain will not affect how data is synchronized.
- Data will synchronize immediately and update every 5 minutes.
Note: In order for "Check Config" to be visible, you must enable "Advanced Mode" on your user profile. The "Check Config" tool can be found by clicking "Configuration" from the sidebar (cog icon) and then clicking "Server Control".
## Configuration
```yaml

10
source/_integrations/yamaha.markdown
View File

@ -11,11 +11,11 @@ The `yamaha` platform allows you to control [Yamaha Network Receivers](http://us
Supported devices:
- HTR-4065
- RX-V473
- RX-V573
- RX-V673
- RX-V773
- [HTR-4065](http://www.yamaha.com/cchtr4065/)
- [RX-V473](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v473/specs.html)
- [RX-V573](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v573/specs.html)
- [RX-V673](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v673/specs.html)
- [RX-V773](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v773/specs.html)
- And more
To add a Yamaha Network Receiver to your installation, add the following to your `configuration.yaml` file:

2
source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
View File

@ -43,7 +43,7 @@ Example of the new views in the frontend. <a href='/integrations/group/'>Learn m
- Bugfixes by [@molobrakos], [@MartinHjelmare], [@pavoni], [@trollkarlen], [@zmrow], [@maddox], [@persandstrom], [@happyleavesaoc], [@balloob], [@fabaff], [@stefan-jonasson], [@haraldnagel].
[the demo]: /demo/
[command sensor]: /integrations/binary_sensor.command/
[command sensor]: /integrations/command_line/
[Insteon hub]: /integrations/insteon/
[LIFX]: /integrations/lifx
[Nest]: /integrations/nest/

3
source/_posts/2016-02-28-steam-d-link-smart-plugs-and-neurio-energy-sensors.markdown
View File

@ -30,7 +30,7 @@ It's been another two weeks which means it's time for release: 0.14!
- Switch: [D-Link smart plugs] now supported ([@LinuxChristian])
- Script: Toggle support added ([@Andythigpen])
- Light: [Wemo] now supported ([@jaharkes])
- Rollershutter: [Command line platform][rollershutter.command_line] added ([@t30])
- Rollershutter: Command line platform added ([@t30])
- Sensor: [Steam] now supported ([@GreenTurtwig])
- Binary Sensor: [Wink] now supported ([@w1ll1am23])
- Demo has been updated ([@kfgoode])
@ -64,7 +64,6 @@ It's been another two weeks which means it's time for release: 0.14!
[Z-Wave]: /integrations/zwave
[D-Link smart plugs]: /integrations/dlink
[Wemo]: /integrations/wemo
[rollershutter.command_line]: /integrations/rollershutter.command_line/
[Steam]: /integrations/steam_online
[Wink]: /integrations/wink#binary-sensor
[the cookbook]: /cookbook/python_component_simple_alarm/

3
source/_posts/2016-05-21-release-020.markdown
View File

@ -25,7 +25,7 @@ Tons of new supported things in 0.20.
- Configurator: allow supplying a link to the user ([@mnestor])
- Media Player: [Roku] now supported ([@bah2830])
- Sensor: [Last.fm] now supported ([@darookee], [@GreenTurtwig])
- Notify: Amazon Lambda, [SNS], [SQS] now supported ([@robbiet480])
- Notify: Amazon Lambda, [SNS], SQS now supported ([@robbiet480])
- Light: allow human readable colors in turn_on command ([@robbiet480])
- YAML: new include dir options [`!include_dir_merge_list`] and [`!include_dir_merge_named`] ([@happyleavesaoc])
- Media Player: [LG Netcast TVs] now supported ([@wokar])
@ -76,7 +76,6 @@ device_tracker:
[purge days option]: /integrations/recorder/
[Roku]: /integrations/roku#media-player
[SNS]: /integrations/notify.aws_sns/
[SQS]: /integrations/notify.aws_sqs/
[supervisord]: /integrations/supervisord
[Twilio SMS]: /integrations/twilio_sms
[Last.fm]: /integrations/lastfm

2
source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
View File

@ -170,7 +170,7 @@ Since 0.28 [automation rules](/blog/2016/09/10/notify-group-reload-api-pihole/#r
[KNX]: /integrations/sensor.knx/
[Kodi]: /integrations/kodi
[Modbus]: /integrations/modbus/
[Nest]: /integrations/fan.nest/
[Nest]: /integrations/nest/
[Nuimo]: /integrations/nuimo_controller/
[OpenALPR]: /integrations/openalpr_local_local
[passwordless]: /integrations/http/

2
source/_posts/2016-10-02-hacktoberfest.markdown
View File

@ -34,7 +34,7 @@ Are you not a programmer but still want to contribute to Home Assistant? Check o
[Hacktoberfest]: https://hacktoberfest.digitalocean.com/
[Hacktoberfest-reg]: https://hacktoberfest.digitalocean.com/profile
[issues]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
[issues-doc]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
[issues-doc]: https://github.com/home-assistant/home-assistant.io/labels/Hacktoberfest
[dev-env]: /developers/development_environment/
[dev-chat]: https://discord.gg/8X8DTH4
[dev-forum]: https://community.home-assistant.io/c/development

4
source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
View File

@ -284,7 +284,7 @@ Thanks for reading all of the above, especially since this week was a pretty lon
[flash-briefing-docs]: /integrations/alexa/
[hacktoberfest-blog]: /blog/2016/10/02/hacktoberfest/
[hacktoberfest-ha-prs]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
[hacktoberfest-site-prs]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
[hacktoberfest-site-prs]: https://github.com/home-assistant/home-assistant.io/labels/Hacktoberfest
[hacktoberfest-website]: https://hacktoberfest.digitalocean.com/
[logo]: /images/blog/2016-10-hacktoberfest/hacktoberfest.png
[min]: /integrations/min_max
@ -300,4 +300,4 @@ Thanks for reading all of the above, especially since this week was a pretty lon
[zero-two-seven-release]: /blog/2016/08/28/notifications-hue-fake-unification/
[twitter]: https://twitter.com/home_assistant
[robbie-twitter]: https://twitter.com/robbie
[blog-orig]: https://github.com/home-assistant/home-assistant.github.io/blob/c937242d154e509d2d84d10c51f654e20556fa21/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
[blog-orig]: https://github.com/home-assistant/home-assistant.io/blob/c937242d154e509d2d84d10c51f654e20556fa21/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown

2
source/_posts/2017-01-14-iss-usps-images-packages.markdown
View File

@ -168,7 +168,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[facebook]: /integrations/facebook
[image]: /integrations/image_processing/
[influx]: /integrations/influxdb/
[insteon]: /integrations/insteon_local/
[insteon]: /integrations/insteon/
[iss]: /integrations/iss
[kankun]: /integrations/kankun
[lannouncer]: /integrations/lannouncer

2
source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
View File

@ -306,7 +306,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[docs]: /docs/
[getting-started]: /getting-started/
[docs-issue]: https://github.com/home-assistant/home-assistant.github.io/issues/1603
[docs-issue]: https://github.com/home-assistant/home-assistant.io/issues/1603
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues

4
source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
View File

@ -364,8 +364,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
[image_processing.dlib_face_identify docs]: /integrations/dlib_face_identify
[image_processing.microsoft_face_detect docs]: /integrations/microsoft_face_detect
[image_processing.microsoft_face_identify docs]: /integrations/microsoft_face_identify
[image_processing.openalpr_cloud docs]: /integrations/openalpr_local_cloud
[image_processing.openalpr_local docs]: /integrations/openalpr_local_local
[image_processing.openalpr_cloud docs]: /integrations/openalpr_cloud
[image_processing.openalpr_local docs]: /integrations/openalpr_local
[image_processing.opencv docs]: /integrations/opencv
[image_processing.seven_segments docs]: /integrations/seven_segments
[kira docs]: /integrations/kira/

5
source/_posts/2017-06-04-release-46.markdown
View File

@ -100,7 +100,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Always return rgb color of bulbs ([@w1ll1am23] - [#7743]) ([light.wink docs])
- Redesign monitored variables for hp_ilo sensor ([@Juggels] - [#7534]) ([sensor.hp_ilo docs]) (breaking change)
- Fix time_date sensor to update at predictable intervals ([@stu-gott] - [#7644]) ([sensor.time_date docs])
- Added new commands and functionality to the harmony remote component. ([@everix1992] - [#7113]) ([remote docs]) ([remote.harmony docs]) ([remote.services.yaml docs])
- Added new commands and functionality to the harmony remote component. ([@everix1992] - [#7113]) ([remote docs]) ([remote.harmony docs]) (remote.services.yaml docs)
- Template light ([@cribbstechnologies] - [#7657]) ([light.template docs]) (new-platform)
- Exclude filter for event types ([@amigian74] - [#7627])
- Change setup script to use pip install instead of setup.py develop ([@hoh] - [#7756])
@ -329,7 +329,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[hassio docs]: /integrations/hassio/
[homematic docs]: /integrations/homematic/
[image_processing.seven_segments docs]: /integrations/seven_segments
[insteon_local docs]: /integrations/insteon_local/
[insteon_local docs]: /integrations/insteon/
[ios docs]: /integrations/ios/
[light.__init__ docs]: /integrations/light.__init__/
[light.flux_led docs]: /integrations/flux_led
@ -355,7 +355,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[recorder.__init__ docs]: /integrations/recorder.__init__/
[remote docs]: /integrations/remote/
[remote.harmony docs]: /integrations/harmony
[remote.services.yaml docs]: /integrations/remote.services.yaml/
[scene.hunterdouglas_powerview docs]: /integrations/hunterdouglas_powerview
[sensor.amcrest docs]: /integrations/amcrest
[sensor.arlo docs]: /integrations/arlo#sensor

2
source/_posts/2017-06-20-things-you-should-know-about-senic-covi.markdown
View File

@ -58,7 +58,7 @@ Core Developer, Home Assistant
[netdisco-contrib]: https://github.com/home-assistant/netdisco/pull/94
[hotfix]: /blog/2017/02/25/config-panel-and-state-restoration/#release-0392---march-1
[Hass.io]: /hassio/
[to Forbes]: https://webcache.googleusercontent.com/search?q=cache:https://www.forbes.com/sites/paularmstrongtech/2017/06/19/covi-is-about-to-make-some-general-electric-execs-very-unhappy/
[to Forbes]: https://www.forbes.com/sites/paularmstrongtech/2017/06/20/covi-is-about-to-make-some-general-electric-execs-very-unhappy/
[tradfri]: /blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/
[Nuimo]: /integrations/nuimo_controller/
[developer documentation]: http://blog.senic.com/posts/the-senic-hub-a-brief-software-overview

4
source/_posts/2017-07-02-release-48.markdown
View File

@ -448,12 +448,12 @@ light:
[digital_ocean docs]: /integrations/digital_ocean/
[fan.comfoconnect docs]: /integrations/comfoconnect
[fan.dyson docs]: /integrations/dyson#fan
[fan.insteon_local docs]: /integrations/insteon_local/
[fan.insteon_local docs]: /integrations/insteon/
[group docs]: /integrations/group/
[image_processing.opencv docs]: /integrations/opencv
[influxdb docs]: /integrations/influxdb/
[insteon_hub docs]: /integrations/insteon/
[insteon_local docs]: /integrations/insteon_local/
[insteon_local docs]: /integrations/insteon/
[knx docs]: /integrations/knx/
[light.decora docs]: /integrations/decora
[light.isy994 docs]: /integrations/isy994

2
source/_posts/2017-08-12-release-51.markdown
View File

@ -376,7 +376,7 @@ vacuum:
[history docs]: /integrations/history/
[image_processing.opencv docs]: /integrations/opencv
[influxdb docs]: /integrations/influxdb/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light.decora_wifi docs]: /integrations/decora_wifi/
[light.flux_led docs]: /integrations/flux_led
[light.lifx docs]: /integrations/lifx

2
source/_posts/2017-08-26-release-0-52.markdown
View File

@ -323,7 +323,7 @@ usps:
[fan.isy994 docs]: /integrations/isy994
[image_processing.dlib_face_detect docs]: /integrations/dlib_face_detect
[image_processing.dlib_face_identify docs]: /integrations/dlib_face_identify
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light.decora_wifi docs]: /integrations/decora_wifi/
[light.flux_led docs]: /integrations/flux_led
[light.hue docs]: /integrations/hue

2
source/_posts/2017-09-09-release-53.markdown
View File

@ -385,7 +385,7 @@ frontend:
[image_processing.dlib_face_detect docs]: /integrations/dlib_face_detect
[image_processing.dlib_face_identify docs]: /integrations/dlib_face_identify
[input_text docs]: /integrations/input_text/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light.homematic docs]: /integrations/homematic
[light.hue docs]: /integrations/hue
[light.lutron_caseta docs]: /integrations/lutron_caseta/

2
source/_posts/2017-09-29-hacktoberfest.markdown
View File

@ -36,7 +36,7 @@ Our participation for [Hacktoberfest 2016][hackt-2016] was a huge success. Join
[Hacktoberfest]: https://hacktoberfest.digitalocean.com/
[Hacktoberfest-reg]: https://hacktoberfest.digitalocean.com/profile
[issues]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
[issues-doc]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
[issues-doc]: https://github.com/home-assistant/home-assistant.io/labels/Hacktoberfest
[dev-env]: /developers/development_environment/
[dev-chat]: https://discord.gg/8X8DTH4
[dev-forum]: https://community.home-assistant.io/c/development

2
source/_posts/2017-10-07-release-55.markdown
View File

@ -320,7 +320,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[cover.rflink docs]: /integrations/cover.rflink/
[demo docs]: /integrations/demo/
[device_tracker.owntracks docs]: /integrations/owntracks
[device_tracker.owntracks_http docs]: /integrations/owntracks_http/
[device_tracker.owntracks_http docs]: /integrations/owntracks
[duckdns docs]: /integrations/duckdns/
[ecobee docs]: /integrations/ecobee/
[emulated_hue docs]: /integrations/emulated_hue/

5
source/_posts/2017-11-04-release-57.markdown
View File

@ -35,7 +35,7 @@ Hacktoberfest is obviously about the people contributing to open source. Big tha
Here are our Hacktoberfest 2017 stats. It's a miracle everyone is still alive:
- Main repo: [273 Pull requests](https://github.com/home-assistant/home-assistant/pulls?utf8=%E2%9C%93&q=merged%3A%3E2017-10-01%20is%3Apr%20label%3AHacktoberfest%20is%3Aclosed%20) were merged out of 307.
- Docs repo: [295 Pull requests](https://github.com/home-assistant/home-assistant.github.io/pulls?page=1&q=merged%3A%3E2017-10-01+is%3Apr+label%3AHacktoberfest+is%3Aclosed&utf8=%E2%9C%93) merged out of 310.
- Docs repo: [295 Pull requests](https://github.com/home-assistant/home-assistant.io/pulls?page=1&q=merged%3A%3E2017-10-01+is%3Apr+label%3AHacktoberfest+is%3Aclosed&utf8=%E2%9C%93) merged out of 310.
- Frontend: [57 pull requests](https://github.com/home-assistant/home-assistant-polymer/pulls?utf8=%E2%9C%93&q=merged%3A%3E2017-10-01%20is%3Apr%20label%3AHacktoberfest%20is%3Aclosed%20) merged.
This means that we processed over 20 Pull requests per day. The result was already visible in 0.56. This release is almost the same. In those releases we were able to add over 40 new integrations.
@ -213,7 +213,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Add Sytadin Traffic component ([@gautric] - [#9524]) (new-platform)
- media_title property now returns current source ([@etsinko] - [#10120]) ([media_player.monoprice docs])
- Added new Clickatell SMS messaging Notify Platform ([@davlloyd] - [#9775]) ([notify.clickatell docs]) (new-platform)
- update boto3 to 1.4.7 and botocore to 1.7.34 ([@TopdRob] - [#10121]) (notify.aws_lambda docs) ([notify.aws_sns docs]) ([notify.aws_sqs docs]) ([tts.amazon_polly docs])
- update boto3 to 1.4.7 and botocore to 1.7.34 ([@TopdRob] - [#10121]) (notify.aws_lambda docs) ([notify.aws_sns docs]) (notify.aws_sqs docs) ([tts.amazon_polly docs])
- Add Random binary sensor ([@fabaff] - [#10164]) ([binary_sensor.random docs]) (new-platform)
- Add clickatell ([@fabaff] - [#10199])
- Update CODEOWNERS ([@ggravlingen] - [#10198])
@ -587,7 +587,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[namecheapdns docs]: /integrations/namecheapdns/
[no_ip docs]: /integrations/no_ip/
[notify.aws_sns docs]: /integrations/notify.aws_sns/
[notify.aws_sqs docs]: /integrations/notify.aws_sqs/
[notify.clickatell docs]: /integrations/clickatell
[notify.sendgrid docs]: /integrations/sendgrid
[notify.yessssms docs]: /integrations/yessssms

2
source/_posts/2017-11-05-frontend-translations.markdown
View File

@ -17,7 +17,7 @@ The Home Assistant sidebar in 12 different languages.
As mentioned in the [0.57 release notes](/blog/2017/11/04/release-57/), Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. [@c727] took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with [Lokalise](https://lokalise.co/) to manage our translations!
Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our [public signup link](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/), and start translating right away. We’ve created a [translation startup guide](/developers/frontend_translation/) with additional details about how to contribute. Instructions are provided there for how to request a new language.
Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our [public signup link](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/), and start translating right away. We’ve created a [translation startup guide](https://developers.home-assistant.io/docs/en/internationalization_translation.html) with additional details about how to contribute. Instructions are provided there for how to request a new language.
Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!

4
source/_posts/2018-01-14-release-61.markdown
View File

@ -666,7 +666,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
[device_tracker.snmp docs]: /integrations/snmp
[device_tracker.tile docs]: /integrations/tile
[digital_ocean docs]: /integrations/digital_ocean/
[fan.insteon_local docs]: /integrations/insteon_local/
[fan.insteon_local docs]: /integrations/insteon/
[fan.isy994 docs]: /integrations/isy994
[fan.xiaomi_miio docs]: /integrations/fan.xiaomi_miio/
[google_assistant docs]: /integrations/google_assistant/
@ -681,7 +681,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
[image_processing.opencv docs]: /integrations/opencv
[input_boolean docs]: /integrations/input_boolean/
[input_select docs]: /integrations/input_select/
[insteon_local docs]: /integrations/insteon_local/
[insteon_local docs]: /integrations/insteon/
[isy994 docs]: /integrations/isy994/
[knx docs]: /integrations/knx/
[light.deconz docs]: /integrations/deconz#light

14
source/_posts/2018-02-10-release-63.markdown
View File

@ -51,7 +51,7 @@ We're planning a lot of cool stuff around the entity registry. Stay tuned!
## Release 0.63.2 - February 14
- Fix MercedesMe - add check for unsupported features ([@ReneNulschDE] - [#12342]) ([mercedesme docs]) (binary_sensor.mercedesme docs) ([device_tracker.mercedesme docs]) ([sensor.mercedesme docs])
- Fix MercedesMe - add check for unsupported features ([@ReneNulschDE] - [#12342]) (mercedesme docs) (binary_sensor.mercedesme docs) (device_tracker.mercedesme docs) (sensor.mercedesme docs)
- Fix WUnderground names ([@OttoWinter] - [#12346]) ([sensor.wunderground docs])
- Updated beacontools ([@citruz] - [#12368]) ([sensor.eddystone_temperature docs])
- Introduce zone_id to identify player+zone ([@sdague] - [#12382]) ([media_player.yamaha docs])
@ -226,7 +226,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Canary live stream ([@snjoetw] - [#11949]) ([canary docs]) ([camera.canary docs]) (breaking change)
- Replace Gitter with Discord ([@fabaff] - [#12199])
- Upgrade Sphinx to 1.6.7 ([@fabaff] - [#12200])
- Change attributes in new Mercedes Me component ([@ReneNulschDE] - [#12147]) ([mercedesme docs]) (binary_sensor.mercedesme docs) ([device_tracker.mercedesme docs]) ([sensor.mercedesme docs])
- Change attributes in new Mercedes Me component ([@ReneNulschDE] - [#12147]) (mercedesme docs) (binary_sensor.mercedesme docs) (device_tracker.mercedesme docs) (sensor.mercedesme docs)
- Binary Sensor Template: Add icon_template and entity_picture_template support ([@hawk259] - [#12158]) ([binary_sensor.template docs])
- Bump pyeconet version to fix JSONDecodeError ([@w1ll1am23] - [#12204]) ([climate.econet docs])
- Add support for Alexa.StepSpeaker ([@lucasweb78] - [#12183]) ([alexa docs])
@ -528,7 +528,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[cover.template docs]: /integrations/cover.template/
[deconz docs]: /integrations/deconz/
[device_tracker.huawei_router docs]: /integrations/huawei_router
[device_tracker.mercedesme docs]: /integrations/device_tracker.mercedesme/
[device_tracker.mikrotik docs]: /integrations/mikrotik
[device_tracker.mqtt docs]: /integrations/device_tracker.mqtt/
[device_tracker.owntracks docs]: /integrations/owntracks
@ -543,7 +542,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[group docs]: /integrations/group/
[homematic docs]: /integrations/homematic/
[http docs]: /integrations/http/
[image_processing.openalpr_cloud docs]: /integrations/openalpr_local_cloud
[image_processing.openalpr_cloud docs]: /integrations/openalpr_cloud
[influxdb docs]: /integrations/influxdb/
[input_text docs]: /integrations/input_text/
[ios docs]: /integrations/ios/
@ -572,7 +571,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[media_player.volumio docs]: /integrations/volumio
[media_player.webostv docs]: /integrations/webostv#media-player
[melissa docs]: /integrations/melissa/
[mercedesme docs]: /integrations/mercedesme/
[mochad docs]: /integrations/mochad/
[notify.gntp docs]: /integrations/gntp
[notify.kodi docs]: /integrations/kodi
@ -592,7 +590,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.deutsche_bahn docs]: /integrations/deutsche_bahn
[sensor.fritzbox_callmonitor docs]: /integrations/fritzbox#sensor_callmonitor/
[sensor.melissa docs]: /integrations/melissa/
[sensor.mercedesme docs]: /integrations/sensor.mercedesme/
[sensor.miflora docs]: /integrations/miflora
[sensor.onewire docs]: /integrations/onewire
[sensor.pollen docs]: /integrations/iqvia
@ -653,12 +650,9 @@ Experiencing issues introduced by this release? Please report them in our [issue
[@amelchio]: https://github.com/amelchio
[@citruz]: https://github.com/citruz
[@sdague]: https://github.com/sdague
[device_tracker.mercedesme docs]: /integrations/device_tracker.mercedesme/
[light.limitlessled docs]: /integrations/limitlessled
[media_player.yamaha docs]: /integrations/yamaha
[mercedesme docs]: /integrations/mercedesme/
[media_player.yamaha docs]: /integrations/yamah
[sensor.eddystone_temperature docs]: /integrations/eddystone_temperature
[sensor.mercedesme docs]: /integrations/sensor.mercedesme/
[sensor.wunderground docs]: /integrations/wunderground
[#12392]: https://github.com/home-assistant/home-assistant/pull/12392
[#12421]: https://github.com/home-assistant/home-assistant/pull/12421

8
source/_posts/2018-03-09-release-65.markdown
View File

@ -178,7 +178,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
- Insteon PLM: If you have created platform overrides in your configuration.yaml file to change a your INSTEON device to map to a different Home Assistant platform, that mapping will no longer be in effect. Please see the new device override capabilities in the [insteon_plm documentation](/integrations/insteon_plm/). ([@teharris1] - [#12534]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([fan.insteon_plm docs]) ([light.insteon_plm docs]) ([sensor.insteon_plm docs]) ([switch.insteon_plm docs]) (breaking change)
- Insteon PLM: If you have created platform overrides in your configuration.yaml file to change a your INSTEON device to map to a different Home Assistant platform, that mapping will no longer be in effect. Please see the new device override capabilities in the [insteon_plm documentation](/integrations/insteon/). ([@teharris1] - [#12534]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([fan.insteon_plm docs]) ([light.insteon_plm docs]) ([sensor.insteon_plm docs]) ([switch.insteon_plm docs]) (breaking change)
- AirVisual's air index unit is AQI (Air Quality Index), not PSI (Pressure per Square Inch). ([@chilicheech] - [#12730]) ([sensor.airvisual docs]) (breaking change)
- TekSavvy Sensor: The sensor entity id for peak upload usage used to be `sensor.teksavvy_on_peak_upload_` this has been changed to `sensor.teksavvy_on_peak_upload`. The `usage` title was shared between and therefore indeterminate between GB and % usage. Therefore % usage entity ID has been changed to `sensor.teksavvy_usage_ratio` ([@mikeodr] - [#12325]) ([sensor.teksavvy docs]) (breaking change)
- Egardia redesign - generic component and sensor support ([@jeroenterheerdt] - [#11994]) ([egardia docs]) ([alarm_control_panel.egardia docs]) ([binary_sensor.egardia docs]) (breaking change) (new-platform)
@ -549,7 +549,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[binary_sensor.concord232 docs]: /integrations/concord232#binary-sensor
[binary_sensor.egardia docs]: /integrations/egardia#binary-sensor
[binary_sensor.hikvision docs]: /integrations/hikvision
[binary_sensor.insteon_plm docs]: /integrations/insteon_plm/
[binary_sensor.insteon_plm docs]: /integrations/insteon/
[binary_sensor.isy994 docs]: /integrations/isy994
[binary_sensor.knx docs]: /integrations/binary_sensor.knx/
[binary_sensor.upcloud docs]: /integrations/upcloud#binary-sensor
@ -582,7 +582,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[hue docs]: /integrations/hue/
[ihc docs]: /integrations/ihc/
[influxdb docs]: /integrations/influxdb/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[knx docs]: /integrations/knx/
[light docs]: /integrations/light/
[light.demo docs]: /integrations/light.demo/
@ -636,7 +636,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.zestimate docs]: /integrations/zestimate
[shopping_list docs]: /integrations/shopping_list/
[switch.edimax docs]: /integrations/edimax
[switch.insteon_plm docs]: /integrations/insteon_plm/
[switch.insteon_plm docs]: /integrations/insteon/
[switch.rest docs]: /integrations/switch.rest/
[switch.tesla docs]: /integrations/tesla
[switch.upcloud docs]: /integrations/upcloud#switch

8
source/_posts/2018-04-14-release-67.markdown
View File

@ -56,7 +56,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Updates default Pilight port number ([@frenck] - [#13419]) ([pilight docs]) (breaking change)
- Update to new "b2vapi" of BMW ConnectedDrive ([@ChristianKuehnel] - [#13305]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (breaking change)
- Remove MercedesME component ([@ReneNulschDE] - [#13538]) ([device_tracker docs]) ([mercedesme docs]) (binary_sensor.mercedesme docs) ([sensor.mercedesme docs]) (breaking change)
- Remove MercedesME component ([@ReneNulschDE] - [#13538]) ([device_tracker docs]) (mercedesme docs) (binary_sensor.mercedesme docs) (sensor.mercedesme docs) (breaking change)
- Channel up and down for webostv ([@stephanerosi] - [#13624]) ([media_player.webostv docs]) (breaking change)
- Add media type separation for video/movie ([@tadly] - [#13612]) (breaking change)
- Added ENTITY_ID_FORMAT import and set entity_id in __init__ ([@timmo001] - [#13642]) ([switch.broadlink docs]) (breaking change)
@ -108,7 +108,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Added HassOpenCover and HassCloseCover intents ([@tschmidty69] - [#13372]) ([conversation docs]) ([cover docs])
- rfxtrx lib 0.22.0 ([@Danielhiversen] - [#13576]) ([rfxtrx docs])
- xiaomi lib upgrade ([@Danielhiversen] - [#13577]) ([xiaomi_aqara docs])
- Remove MercedesME component ([@ReneNulschDE] - [#13538]) ([device_tracker docs]) ([mercedesme docs]) (binary_sensor.mercedesme docs) ([sensor.mercedesme docs]) (breaking change)
- Remove MercedesME component ([@ReneNulschDE] - [#13538]) ([device_tracker docs]) (mercedesme docs) (binary_sensor.mercedesme docs) (sensor.mercedesme docs) (breaking change)
- Added Waze travel time sensor ([@Myrddyn1] - [#12387]) ([sensor.waze_travel_time docs]) (new-platform)
- Added switch component to Amcrest IP Camera. ([@adpriebe] - [#12992]) ([amcrest docs]) ([switch.amcrest docs]) (new-platform)
- Upgrade pyhydroquebec 2.2.1 ([@titilambert] - [#13586]) ([sensor.hydroquebec docs])
@ -354,7 +354,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[freedns docs]: /integrations/freedns/
[homekit docs]: /integrations/homekit/
[hue docs]: /integrations/hue/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light docs]: /integrations/light/
[light.nanoleaf_aurora docs]: /integrations/nanoleaf/
[light.hue docs]: /integrations/hue
@ -371,7 +371,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[media_player.philips_js docs]: /integrations/philips_js
[media_player.songpal docs]: /integrations/songpal
[media_player.webostv docs]: /integrations/webostv#media-player
[mercedesme docs]: /integrations/mercedesme/
[mqtt docs]: /integrations/mqtt/
[mysensors docs]: /integrations/mysensors/
[notify docs]: /integrations/notify/
@ -387,7 +386,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.file docs]: /integrations/file#sensor
[sensor.hydroquebec docs]: /integrations/hydroquebec
[sensor.imap_email_content docs]: /integrations/imap_email_content/
[sensor.mercedesme docs]: /integrations/sensor.mercedesme/
[sensor.plex docs]: /integrations/plex#sensor
[sensor.qnap docs]: /integrations/qnap
[sensor.qwikswitch docs]: /integrations/qwikswitch

6
source/_posts/2018-05-11-release-69.markdown
View File

@ -376,7 +376,7 @@ rainmachine:
[auth docs]: /integrations/auth/
[binary_sensor docs]: /integrations/binary_sensor/
[binary_sensor.deconz docs]: /integrations/deconz#binary-sensor
[binary_sensor.insteon_plm docs]: /integrations/insteon_plm/
[binary_sensor.insteon_plm docs]: /integrations/insteon/
[binary_sensor.tapsaff docs]: /integrations/tapsaff
[binary_sensor.trend docs]: /integrations/trend
[binary_sensor.workday docs]: /integrations/workday
@ -405,7 +405,7 @@ rainmachine:
[image_processing.microsoft_face_identify docs]: /integrations/microsoft_face_identify
[image_processing.opencv docs]: /integrations/opencv
[influxdb docs]: /integrations/influxdb/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light.deconz docs]: /integrations/deconz#light
[light.flux_led docs]: /integrations/flux_led
[light.hue docs]: /integrations/hue
@ -466,7 +466,7 @@ rainmachine:
[sensor.yweather docs]: /integrations/yweather
[switch.deluge docs]: /integrations/deluge#switch
[switch.fritzbox docs]: /integrations/fritzbox
[switch.insteon_plm docs]: /integrations/insteon_plm/
[switch.insteon_plm docs]: /integrations/insteon/
[switch.mqtt docs]: /integrations/switch.mqtt/
[switch.rainmachine docs]: /integrations/rainmachine#switch
[switch.xiaomi_aqara docs]: /integrations/switch.xiaomi_aqara/

4
source/_posts/2018-05-18-release-70.markdown
View File

@ -358,7 +358,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
[camera docs]: /integrations/camera/
[camera.familyhub docs]: /integrations/familyhub
[camera.generic docs]: /integrations/generic
[camera.generic docs]: /integrations/generic_ip_camera
[climate.mysensors docs]: /integrations/climate.mysensors/
[climate.sensibo docs]: /integrations/sensibo
[climate.venstar docs]: /integrations/venstar
@ -379,7 +379,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[homematicip_cloud docs]: /integrations/homematicip_cloud/
[http docs]: /integrations/http/
[image_processing.facebox docs]: /integrations/facebox
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[iota docs]: /integrations/iota/
[isy994 docs]: /integrations/isy994/
[konnected docs]: /integrations/konnected/

4
source/_posts/2018-06-22-release-72.markdown
View File

@ -426,7 +426,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[hassio docs]: /integrations/hassio/
[hue docs]: /integrations/hue/
[image_processing.facebox docs]: /integrations/facebox
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[konnected docs]: /integrations/konnected/
[light.deconz docs]: /integrations/deconz#light
[light.lifx docs]: /integrations/lifx
@ -485,7 +485,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.xiaomi_miio docs]: /integrations/sensor.xiaomi_miio/
[sonos docs]: /integrations/sonos/
[switch.doorbird docs]: /integrations/doorbird#switch
[switch.insteon_plm docs]: /integrations/insteon_plm/
[switch.insteon_plm docs]: /integrations/insteon/
[switch.linode docs]: /integrations/linode#switch
[switch.mystrom docs]: /integrations/mystrom#switch
[switch.neato docs]: /integrations/neato#switch

2
source/_posts/2018-07-06-release-73.markdown
View File

@ -288,7 +288,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[http docs]: /integrations/http/
[hue docs]: /integrations/hue/
[image_processing.opencv docs]: /integrations/opencv
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light.deconz docs]: /integrations/deconz#light
[light.flux_led docs]: /integrations/flux_led
[light.homekit_controller docs]: /integrations/homekit_controller

4
source/_posts/2018-07-16-release-73-2.markdown
View File

@ -23,7 +23,7 @@ After research, the following integrations have been impacted. Although the odds
- [google_assistant](/integrations/google_assistant/) (manual setup)
- [google_domains](/integrations/google_domains/)
- [homematicip_cloud](/integrations/homematicip_cloud/)
- [image_processing.openalpr_cloud](/integrations/openalpr_local_cloud)
- [image_processing.openalpr_cloud](/integrations/openalpr_cloud)
- [microsoft_face](/integrations/microsoft_face/)
- [namecheapdns](/integrations/namecheapdns/)
- [no_ip](/integrations/no_ip/)
@ -79,7 +79,7 @@ Local, so cannot be impacted:
- [camera.amcrest](/integrations/amcrest)
- [camera.doorbird](/integrations/doorbird#camera)
- [camera.familyhub](/integrations/familyhub)
- [camera.generic](/integrations/generic)
- [camera.generic](/integrations/generic_ip_camera)
- [camera.mjpeg](/integrations/mjpeg)
- [camera.proxy](/integrations/proxy)
- [camera.synology](/integrations/synology)

2
source/_posts/2018-07-21-release-74.markdown
View File

@ -397,7 +397,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.enocean docs]: /integrations/enocean#switch
[switch.eufy docs]: /integrations/eufy
[switch.fritzbox docs]: /integrations/fritzbox
[switch.insteon_plm docs]: /integrations/insteon_plm/
[switch.insteon_plm docs]: /integrations/insteon/
[switch.tuya docs]: /integrations/tuya
[tahoma docs]: /integrations/tahoma/
[tts docs]: /integrations/tts/

8
source/_posts/2018-08-03-release-75.markdown
View File

@ -313,7 +313,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[auth docs]: /integrations/auth/
[binary_sensor.alarmdecoder docs]: /integrations/alarmdecoder
[binary_sensor.ihc docs]: /integrations/ihc#binary-sensor
[binary_sensor.insteon_plm docs]: /integrations/insteon_plm/
[binary_sensor.insteon_plm docs]: /integrations/insteon/
[binary_sensor.tahoma docs]: /integrations/tahoma
[binary_sensor.trend docs]: /integrations/trend
[calendar.todoist docs]: /integrations/todoist
@ -335,7 +335,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[fan docs]: /integrations/fan/
[fan.comfoconnect docs]: /integrations/comfoconnect
[fan.dyson docs]: /integrations/dyson#fan
[fan.insteon_local docs]: /integrations/insteon_local/
[fan.insteon_local docs]: /integrations/insteon/
[fan.template docs]: /integrations/fan.template/
[fan.tuya docs]: /integrations/tuya
[fan.wink docs]: /integrations/wink#fan
@ -347,7 +347,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[http docs]: /integrations/http/
[ihc docs]: /integrations/ihc/
[image_processing.opencv docs]: /integrations/opencv
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_plm docs]: /integrations/insteon/
[light docs]: /integrations/light/
[light.deconz docs]: /integrations/deconz#light
[light.futurenow docs]: /integrations/futurenow
@ -397,7 +397,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[spider docs]: /integrations/spider/
[switch docs]: /integrations/switch/
[switch.ihc docs]: /integrations/ihc#switch
[switch.insteon_plm docs]: /integrations/insteon_plm/
[switch.insteon_plm docs]: /integrations/insteon/
[switch.mqtt docs]: /integrations/switch.mqtt/
[switch.spider docs]: /integrations/spider
[switch.tplink docs]: /integrations/tplink

6
source/_posts/2018-08-29-release-77.markdown
View File

@ -425,7 +425,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
[calendar.google docs]: /integrations/calendar.google/
[camera docs]: /integrations/camera/
[camera.generic docs]: /integrations/generic
[camera.generic docs]: /integrations/generic_ip_camera
[camera.proxy docs]: /integrations/proxy
[camera.push docs]: /integrations/push
[climate docs]: /integrations/climate/
@ -448,8 +448,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
[http docs]: /integrations/http/
[image_processing.opencv docs]: /integrations/opencv
[input_datetime docs]: /integrations/input_datetime/
[insteon_local docs]: /integrations/insteon_local/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_local docs]: /integrations/insteon/
[insteon_plm docs]: /integrations/insteon/
[konnected docs]: /integrations/konnected/
[light.deconz docs]: /integrations/deconz#light
[light.wemo docs]: /integrations/wemo

4
source/_posts/2018-10-12-release-80.markdown
View File

@ -600,8 +600,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
[automation.webhook docs]: /docs/automation/trigger/#webhook-trigger
[binary_sensor.blink docs]: /integrations/blink
[binary_sensor.bmw_connected_drive docs]: /integrations/bmw_connected_drive
[binary_sensor.ffmpeg_motion docs]: /integrations/ffmpeg_motion_motion/
[binary_sensor.ffmpeg_noise docs]: /integrations/ffmpeg_motion_noise/
[binary_sensor.ffmpeg_motion docs]: /integrations/ffmpeg_motion/
[binary_sensor.ffmpeg_noise docs]: /integrations/ffmpeg_noise/
[binary_sensor.fritzbox docs]: /integrations/fritzbox
[binary_sensor.mqtt docs]: /integrations/binary_sensor.mqtt/
[binary_sensor.openuv docs]: /integrations/openuv

11
source/_posts/2018-11-28-release-83.markdown
View File

@ -38,7 +38,7 @@ Note, this release includes a migration to add an index to speed up the logbook
- Implemented tplink_lte components and notify service via SMS ([@andtos90] - [#17111]) ([notify docs]) ([tplink_lte docs]) (new-platform)
- Add Traccar device tracker ([@ludeeus] - [#18200]) ([device_tracker docs]) (new-platform)
- Add support for Google Home device tracking ([@ludeeus] - [#18190]) ([device_tracker docs]) (new-platform)
- Add Norwegian Public Transportation sensor (Ruter). ([@ludeeus] - [#18237]) ([sensor.ruter docs]) (new-platform)
- Add Norwegian Public Transportation sensor (Ruter). ([@ludeeus] - [#18237]) (sensor.ruter docs) (new-platform)
- Split out geofency with a component and platform. The geofency device_tracker platform no longer takes any configuration. The configuration needs to be applied to the component geofency instead. The platform will be automatically loaded with the component. ([@rohankapoorcom] - [#17933]) ([device_tracker docs]) ([geofency docs]) (breaking change) (new-platform)
- Add support for Lupusec alarm control panel ([@majuss] - [#17691]) ([lupusec docs]) ([alarm_control_panel.lupusec docs]) ([binary_sensor.lupusec docs]) ([switch.lupusec docs]) (new-platform)
- Add upload and download sensors and component for asuswrt ([@kennedyshead] - [#17757]) ([asuswrt docs]) ([device_tracker docs]) ([sensor.asuswrt docs]) (breaking change) (new-platform)
@ -181,7 +181,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- fixed wording that may confuse user ([@eliseomartelli] - [#18628]) (beta fix)
- Updated webhook_register, version bump pypoint ([@fredrike] - [#18635]) ([point docs]) (beta fix)
- Fix vol Dict -> dict ([@bramkragten] - [#18637]) ([lovelace docs]) (beta fix)
- Set correct default offset ([@ludeeus] - [#18678]) ([sensor.ruter docs]) (beta fix)
- Set correct default offset ([@ludeeus] - [#18678]) (sensor.ruter docs) (beta fix)
- Add permission checks to Rest API ([@balloob] - [#18639]) ([api docs]) ([http docs]) (beta fix)
- Fix logbook filtering entities ([@balloob] - [#18721]) ([logbook docs]) (beta fix)
- Async tests for owntracks device tracker ([@armills] - [#18681]) (beta fix)
@ -252,7 +252,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Normalize MAC addresses ([@balloob] - [#16916])
- HmIP thermostat fix with operations ([@pvizeli] - [#18068]) ([climate.homematic docs])
- Update PR checklist with commented out code check ([@armills] - [#18272])
- Add Norwegian Public Transportation sensor (Ruter). ([@ludeeus] - [#18237]) ([sensor.ruter docs]) (new-platform)
- Add Norwegian Public Transportation sensor (Ruter). ([@ludeeus] - [#18237]) (sensor.ruter docs) (new-platform)
- Split out geofency with a component and platform ([@rohankapoorcom] - [#17933]) ([device_tracker docs]) ([geofency docs]) (breaking change) (new-platform)
- Use async_add_executor_job at the xiaomi_miio platforms ([@syssi] - [#18294]) ([device_tracker docs]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([sensor.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
- Remove skipped device tracker tests ([@armills] - [#18291])
@ -265,7 +265,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Upgrade hdate to 0.7.5 ([@tsvi] - [#18296]) ([sensor.jewish_calendar docs])
- Add SUPPORT_SEEK for DLNA DMR devices + now (better) providing media_image_url for DLNA DMR devices ([@StevenLooman] - [#18157]) ([upnp docs]) ([media_player.dlna_dmr docs])
- Add upload and download sensors and component for asuswrt ([@kennedyshead] - [#17757]) ([asuswrt docs]) ([device_tracker docs]) ([sensor.asuswrt docs]) (breaking change) (new-platform)
- Update pyruter to 1.1.0 to be able to reuse aiohttp session. ([@ludeeus] - [#18310]) ([sensor.ruter docs])
- Update pyruter to 1.1.0 to be able to reuse aiohttp session. ([@ludeeus] - [#18310]) (sensor.ruter docs)
- Make flux switch async ([@jawilson] - [#18277]) ([switch.flux docs])
- Add support for 17track.net package sensors ([@bachya] - [#18038]) ([sensor.seventeentrack docs]) (new-platform)
- Added optional precision configuration option to generic_thermostat. ([@partofthething] - [#18317]) ([climate.generic_thermostat docs])
@ -380,7 +380,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- fixed wording that may confuse user ([@eliseomartelli] - [#18628]) (beta fix)
- Updated webhook_register, version bump pypoint ([@fredrike] - [#18635]) ([point docs]) (beta fix)
- Fix vol Dict -> dict ([@bramkragten] - [#18637]) ([lovelace docs]) (beta fix)
- Set correct default offset ([@ludeeus] - [#18678]) ([sensor.ruter docs]) (beta fix)
- Set correct default offset ([@ludeeus] - [#18678]) (sensor.ruter docs) (beta fix)
- Add permission checks to Rest API ([@balloob] - [#18639]) ([api docs]) ([http docs]) (beta fix)
- Fix logbook filtering entities ([@balloob] - [#18721]) ([logbook docs]) (beta fix)
- Async tests for owntracks device tracker ([@armills] - [#18681]) (beta fix)
@ -781,7 +781,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.point docs]: /integrations/point#sensor
[sensor.pollen docs]: /integrations/iqvia
[sensor.rainmachine docs]: /integrations/rainmachine
[sensor.ruter docs]: /integrations/sensor.ruter/
[sensor.season docs]: /integrations/season
[sensor.seventeentrack docs]: /integrations/seventeentrack
[sensor.sql docs]: /integrations/sql

3
source/_posts/2019-01-09-release-85.markdown
View File

@ -245,7 +245,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Clean up RFLink tests and add two tests ([@javicalle] - [#19511])
- Add ZHA battery sensor ([@dmulcahey] - [#19363]) ([zha docs]) ([sensor.zha docs])
- Restore state for zha binary_sensors on restart. ([@Adminiuga] - [#19314]) ([binary_sensor.zha docs])
- Add deprecation warning ([@ludeeus] - [#19515]) ([sensor.ruter docs])
- Add deprecation warning ([@ludeeus] - [#19515]) (sensor.ruter docs)
- Update yale smart alarm client to v0.1.6 ([@domwillcode] - [#19495]) ([alarm_control_panel.yale_smart_alarm docs])
- Add sunrise and sunset to Darksky weather sensor ([@fabaff] - [#19492]) ([sensor.darksky docs])
- Update ZHA entity state on ZigBee zdo device announce ([@dmulcahey] - [#19208]) ([zha docs])
@ -864,7 +864,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.plum_lightpad docs]: /integrations/plum_lightpad
[sensor.point docs]: /integrations/point#sensor
[sensor.prezzibenzina docs]: /integrations/prezzibenzina
[sensor.ruter docs]: /integrations/sensor.ruter/
[sensor.scrape docs]: /integrations/scrape
[sensor.seventeentrack docs]: /integrations/seventeentrack
[sensor.solaredge docs]: /integrations/solaredge

22
source/_posts/2019-02-04-introducing-home-assistant-cli.markdown
View File

@ -20,7 +20,7 @@ Last week we released version 0.4, which provides majority of the features I was
looking for to do from a CLI.
## Feature highlights:
- Get configuration info (`hass-cli config`)
- List, get, edit and delete state for entities (`hass-cli entity`')
- Query history with relative time ('hass-cli entity history')
@ -36,29 +36,29 @@ looking for to do from a CLI.
## Usage
For the basic intro to `hass-cli` see the docs at [github](github-hass-cli).
For the basic intro to `hass-cli` see the docs at [github][github-hass-cli].
## Installation
Install latest `homeassistant-cli` by pip:
$ pip3 install homeassistant-cli
or if upgrade use:
$ pip3 install --upgrade homeassistant-cli
or if you like an isolated install you can use [pipsi][pipsi]
$ pipsi install --python python3 homeassistant-cli
or if you are adventurous you can build it from [source][github-hass-cli] at.
or if you are adventurous you can build it from [source][github-hass-cli] at.
## Changes since 0.1-0.3
The first thing is that the commands have been cleaned up to be more logcial/explicit.
The first thing is that the commands have been cleaned up to be more logcial/explicit.
$ hass-cli
$ hass-cli
...
...
Commands:
@ -113,7 +113,7 @@ If you still want to get all the glory details you can use `-o yaml` to get the
A few frequent asked questions we've seen the last months are as follows:
### Why would anyone use this ?
### Why would anyone use this ?
This is not removing or trying to compete with existing ways to access Home
Assistant - this is a complementary way to access Home Assistant. If you like to
@ -132,7 +132,7 @@ type out. Finally over time as `hass-cli` will get support for utilizing the
more extensive websocket API's `hass-cli` will be more consistent and simpler to
use than using "raw" access via `curl`.
### Does this only work with HTTPS and hass.io ?
### Does this only work with HTTPS and hass.io ?
No, it works with *any* Home Assistant that has REST API exposed - something
that is done by default. In short - if you can access Home Assistant with your
@ -146,7 +146,7 @@ No, `hass-cli` does not require Home Assistant installed on the computer you
want to run it on. It should run on any install with Python 3.5 or higher on all
major operating systems.
### Does this work with client-generated certificates ?
### Does this work with client-generated certificates ?
It should, but we have not yet been able to verify it. If you would like to help
us try it run with `--cert <certificate.pem>` and let us know if it works on
@ -159,7 +159,7 @@ system control commands (like refreshing groups, restarting, etc.) but also for
accessing hass.io add-ons. Also having an easy way to hook into the event bus
(via websocket) to see what is happening live.
What would you like to see ?
What would you like to see ?
## Feedback

7
source/_posts/2019-02-20-release-88.markdown
View File

@ -206,13 +206,13 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Add ZHA binary sensor tests ([@dmulcahey] - [#20711])
- Add ZHA fan tests ([@dmulcahey] - [#20712])
- Add ZHA light tests ([@dmulcahey] - [#20713])
- Add google home alarm sensor ([@eliseomartelli] - [#20709]) ([googlehome docs]) (new-platform)
- Add google home alarm sensor ([@eliseomartelli] - [#20709]) (googlehome docs) (new-platform)
- Add missing abbreviations ([@emontnemery] - [#20741]) ([mqtt docs])
- Update pysmartthings to 0.5.0 ([@andrewsayre] - [#20759]) ([smartthings docs])
- Use PLATFORM_SCHEMA_BASE as base schema for additional components. ([@emontnemery] - [#20578]) (breaking change)
- Update flake8 to 3.7.5 ([@Danielhiversen] - [#20761]) ([cast docs]) ([device_tracker docs]) ([isy994 docs])
- Modifying MTUs acquisition ([@SupremeSports] - [#20654]) ([sensor.ted5000 docs])
- Fix googlehome alarm sensor platform ([@eliseomartelli] - [#20742]) ([googlehome docs])
- Fix googlehome alarm sensor platform ([@eliseomartelli] - [#20742]) (googlehome docs)
- SMHI component: Bugfix - calc precipitation ([@helto4real] - [#20745]) ([smhi docs])
- Added HomeKit fan speed based on speed_list ([@nd-net] - [#19767]) ([homekit docs]) (new-feature)
- Reproduce states by letting each component opt in on handling state recovery itself ([@elupus] - [#18700])
@ -649,7 +649,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[feedreader docs]: /integrations/feedreader/
[freedns docs]: /integrations/freedns/
[google_pubsub docs]: /integrations/google_pubsub/
[googlehome docs]: /integrations/googlehome/
[harmony docs]: /integrations/harmony/
[homekit docs]: /integrations/homekit/
[homematic docs]: /integrations/homematic/
@ -700,7 +699,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.modbus docs]: /integrations/sensor.modbus/
[sensor.rejseplanen docs]: /integrations/rejseplanen
[sensor.speedtest docs]: /integrations/speedtestdotnet
[sensor.speedtestdotnet docs]: /integrations/speedtestdotnetdotnet/
[sensor.speedtestdotnet docs]: /integrations/speedtestdotnet
[sensor.sql docs]: /integrations/sql
[sensor.ted5000 docs]: /integrations/ted5000
[sensor.thermoworks_smoke docs]: /integrations/thermoworks_smoke

2
source/_posts/2019-03-20-release-90.markdown
View File

@ -721,7 +721,7 @@ Users will need to change `- platform: firetv` to `- platform: androidtv` in the
[binary_sensor.workday docs]: /integrations/workday
[camera docs]: /integrations/camera/
[camera.ffmpeg docs]: /integrations/camera.ffmpeg/
[camera.generic docs]: /integrations/generic
[camera.generic docs]: /integrations/generic_ip_camera
[camera.onvif docs]: /integrations/onvif
[camera.proxy docs]: /integrations/proxy
[camera.xeoma docs]: /integrations/xeoma

4
source/_posts/2019-04-24-release-92.markdown
View File

@ -1027,8 +1027,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
[ifttt docs]: /integrations/ifttt/
[ign_sismologia docs]: /integrations/ign_sismologia/
[influxdb docs]: /integrations/influxdb/
[insteon_local docs]: /integrations/insteon_local/
[insteon_plm docs]: /integrations/insteon_plm/
[insteon_local docs]: /integrations/insteon/
[insteon_plm docs]: /integrations/insteon/
[introduction docs]: /integrations/introduction/
[lcn docs]: /integrations/lcn/
[light docs]: /integrations/light/

1
source/_posts/2019-08-28-release-98.markdown
View File

@ -805,7 +805,6 @@ anymore. - ([@abmantis] - [#25971])
[geniushub docs]: /integrations/geniushub/
[geonetnz_quakes docs]: /integrations/geonetnz_quakes/
[google_maps docs]: /integrations/google_maps/
[googlehome docs]: /integrations/googlehome/
[group docs]: /integrations/group/
[heos docs]: /integrations/heos/
[homekit_controller docs]: /integrations/homekit_controller/

960
source/_posts/2019-10-10-release-100.markdown Normal file
View File

@ -0,0 +1,960 @@
---
layout: post
title: "0.100: Better Plex, Bye JSON, HERE Travel time."
description: "A lot of frontend work, performance tweaks and more device automations."
date: 2019-10-10 01:05:02
date_formatted: "October 10, 2019"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2019-09-0.100/components.png
---
<a href='/integrations/#version/0.100'><img src='/images/blog/2019-10-0.100/components.png' style='border: 0;box-shadow: none;'></a>
Welcome to the release notes of yet another wonderful release! No, we're not going for 1.0, we're doing 0.100! We feel like we're not ready yet with our goals for 1.0, but we're making progress every day. For a sneak peak of what we're thinking about, check our blog [Simple mode in Home Assistant 1.0](https://developers.home-assistant.io/blog/2019/10/05/simple-mode.html).
## Hacktoberfest
It is Hacktoberfest. This means that we're spending the month celebrating contributing to open source. If you make 4 pull requests this month, you get a free Hacktoberfest t-shirt! More info and what to work on, check [our Hacktoberfest blog post](https://developers.home-assistant.io/blog/2019/09/27/hacktoberfest.html).
Average contributions per day have doubled for the month of October. There are now on average 40 contributions coming in each day. Breakdown is ~50% Home Assistant backend, ~37% documentation and ~13% the frontend. Most of these contributions you'll see in the next release!
<p class='img'>
<img src='/images/blog/2019-10-0.100/hacktoberfest.png' alt='Graph of 420 PRs that got opened and merged in the last 14 days.'></a>
Last 14 days of pull pequest throughput in the Home Assistant organization. (<a href="https://pullreminders.com/installs/13844975/pr-throughput?d=14d">source</a>)
</p>
## State of the Union 2019
We're going to have another State of the Union! It will be held at November 13, in Amsterdam. Like last year, it will be hosted by our friends at ING. I'm looking forward to talk about all the great things that are happening in Home Assistant land. We had 150 tickets available when we announced it on social media, and they were all gone in less than 24 hours!
We're going to make sure that there will be a live stream available. We'll announce that in time via the blog and social media. Some people are talking about hosting viewing parties across the globe. Keep an eye out on [the social category on the forums](https://community.home-assistant.io/c/social) for announcements. This would also be the place to announce if you are planning on hosting one.
## Plex
[@jjlawren] has been on fire with the Plex integration. You will now be able to link your account via the official Plex account link feature.
<p class='img'>
<img src='/images/blog/2019-10-0.100/plex.png' alt='Screenshot of the Plex user interface asking the user if they want to link with Home Assistant.'></a>
Screenshot of the Plex user interface asking the user if they want to link with Home Assistant.
</p>
## Lovelace
[@iantrich](https://github.com/iantrich) fire has not been put out yet. This version he has also added many new functions to Lovelace! Check the [Lovelace changelog](https://www.home-assistant.io/lovelace/changelog/) for all changes. Some hightlights:
- There are a lot more option for state filtering
- We have a bunch of new UI editors
- A new action `url` to link to external sites
- Config panel: Disabled entities are now hidden by default.
## Device automations
[@emontnemery] has been hard at work at further expanding device automations aided by [@dmulcahey] and [@Kane610]. This release includes improved support for Zigbee (ZHA) devices, sensors, binary sensor, switch and Deconz. One neat new improvement is the addition of a "for" option. This allows you to specify triggers for when a certain device has been on for a period of time.
<p class='img'>
<img src='/images/blog/2019-10-0.100/device-trigger-sensor.png' alt='Screenshot of a device trigger for a temperature sensor.'></a>
Screenshot of a device trigger for a temperature sensor.
</p>
## Automation editor
[@emontnemery](https://github.com/emontnemery) has added a bunch of functions to the automation editor, you can now use `and` and `or` conditions, and give your automation a description so you know why you did what you did.
<p class='img'>
<img src='/images/blog/2019-10-0.100/condition-and.png' alt='Screenshot of an and-condition in the automation editor.'></a>
Screenshot of an and-condition in the automation editor.
</p>
## Devices
Device automations are now available on the experimental device page that we introduced in the last release. You can now see all the triggers, conditions and actions the device supports. Clicking on it will open the automation editor with the automation filled in, ready to edit.
<p class='img'>
<img src='/images/blog/2019-10-0.100/action-trigger.png' alt='Screenshot of a card showing device triggers to create automations from.'></a>
</p>
We also added the entity registry, so you can change all the settings of the devices entities in one place.
And, bonus, when you rename a device on the device page, it will now also rename the entities of that device if they contain the device name. When you are in advanced mode, it can also rename the entity id's for you.
## Goodbye JSON 👋
On the backend we have been using YAML for a long time, but on the frontend, we still used JSON for a lot of things. JSON is harder to write than YAML so we have aligned that. All data inputs on the frontend now accept YAML. You can still use JSON, as JSON is valid YAML.
This includes:
- The automation editor
- The script editor
- Services data in dev tools
- States in dev tools
- Events in dev tools
<p class='img'>
<img src='/images/blog/2019-10-0.100/yaml.png' alt='Screenshot of a service action in the automation editor using YAML.'></a>
Screenshot of a service action in the automation editor using YAML.
</p>
## Thank You, @Amelchio
Core developer [@amelchio] is taking a break from working on Home Assistant. Amelchio has been a contributing member of the Home Assistant community for 2.5 years in which he made a grand total of 275 pull requests! Amelchio has worked on improving database performance and under his wing the Sonos, LIFX and Netgear LTE integrations flourished. He is an example community member, always available in the chat to help other people contribute to Home Assistant.
Thanks Anders, we're going to miss you! ❤️
## In other news
Hans Oischinger showcased how he can steer his vacuum cleaner to specific rooms in his house via his floorplan. Besides this tweet, he also wrote [a great blog about it](https://medium.com/@hans.oischinger/zoned-cleanup-with-live-map-922240b4cf8c).
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Freed my vacuum robot from the cloud with <a href="https://t.co/tirC2vcsqK">https://t.co/tirC2vcsqK</a><br>This unlocked some new functionality for my vacuum:<br>Configure and start zoned cleanup in <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a> with live map overlayed on the floorplan <a href="https://t.co/jtPZHk2xeT">pic.twitter.com/jtPZHk2xeT</a></p>&mdash; Hans Oischinger (@oischinger) <a href="https://twitter.com/oischinger/status/1178254181221769216?ref_src=twsrc%5Etfw">September 29, 2019</a>
</blockquote>
To improve discovery, we're collecting discovery info of devices and services. Please help us gather [zeroconf discovery info](https://github.com/home-assistant/home-assistant/issues/27371) and [HomeKit discovery info](https://github.com/home-assistant/home-assistant/issues/27292).
As always, this release of Home Assistant is accompanied with a new release of the [Home Assistant Podcast](https://hasspodcast.io/):
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Time for another <a href="https://twitter.com/hashtag/smarthome?src=hash&amp;ref_src=twsrc%5Etfw">#smarthome</a> <a href="https://twitter.com/hashtag/Podcast?src=hash&amp;ref_src=twsrc%5Etfw">#Podcast</a><br><br>This week we&#39;re talking <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a> version 1...hundred, <a href="https://twitter.com/hacktoberfest?ref_src=twsrc%5Etfw">@hacktoberfest</a> and catch up with 🇦🇺 Tony about his <a href="https://twitter.com/hashtag/homeautomation?src=hash&amp;ref_src=twsrc%5Etfw">#homeautomation</a> journey with Home Assistant, or maybe it should just be <a href="https://twitter.com/NodeRED?ref_src=twsrc%5Etfw">@NodeRED</a> 🤷‍♂️<a href="https://t.co/DUtNZTHOAA">https://t.co/DUtNZTHOAA</a></p>&mdash; Phil Hawthorne (@philhawthorne) <a href="https://twitter.com/philhawthorne/status/1182055672638267398?ref_src=twsrc%5Etfw">October 9, 2019</a>
</blockquote>
## New Integrations
- Add support for DOODS Image Processing ([@snowzach] - [#26208]) ([doods docs]) (new-integration)
- Izone component ([@Swamp-Ig] - [#24550]) ([izone docs]) (new-integration)
- Add transport data from maps.yandex.ru api ([@rishatik92] - [#26252]) ([yandex_transport docs]) (new-integration)
- Add Kaiterra integration ([@Michsior14] - [#26661]) ([kaiterra docs]) (new-integration)
- Add Ombi integration ([@larssont] - [#26755]) ([ombi docs]) (new-integration)
- Add here_travel_time ([@eifinger] - [#24603]) ([here_travel_time docs]) (new-integration)
- Add support for SOMA Smartshades devices ([@ratsept] - [#26226]) ([soma docs]) (new-integration)
- Add saj component ([@fredericvl] - [#26902]) ([saj docs]) (new-integration)
## New Platforms
- Add iaqualink binary sensor and unique_id ([@flz] - [#26616]) ([iaqualink docs]) (new-platform)
- Add basic support for IKEA Fyrtur blinds ([@ggravlingen] - [#26659]) ([tradfri docs]) (new-platform)
- Centralize rainbird config and add binary sensor platform ([@konikvranik] - [#26393]) ([rainbird docs]) (breaking change) (new-platform)
## If you need help...
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
## Reporting Issues
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
<!--more-->
## Breaking Changes
- **Removed** - The following integrations which were marked in .98 for pending removal have now been removed (ADR-0004):
- **UPS** - ([@frenck] - [#26824])
- **USPS** - ([@frenck] - [#26823])
- **Sytadin** - ([@frenck] - [#26819])
- **SRP Energy** - ([@frenck] - [#26826])
- **Fedex** - ([@frenck] - [#26822])
- **Linksys AP** - ([@frenck] - [#26847])
- **NZBGet** - The integration has been changed to support multiple platforms and future events, and common code has been centralized to the component. The configuration has moved from the sensor platform to the `nzbget` key in configuration.yaml, and the `monitored_variables` option has been removed. Users need to update their configuration. - ([@chriscla] - [#26462]) ([nzbget docs])
New example configuration entry:
```yaml
nzbget:
host: 192.168.1.1
ssl: false
```
- **SpaceAPI** - Values that were not compliant with the SpaceAPI specification were changed.
- `contact / mailing_list` has changed to `contact / ml`, to migrate change the `mailing_list` key to `ml`
- `location / address` is no longer required but is optional as the latitude and longitude properties of the location are added automatically from the HA config). There is no need to change anything. - ([@Bouni] - [#26453]) ([spaceapi docs])
- **Linky** - Linky sensors have been grouped to one Linky device. Users will need to remove and re-add the Linky integration to clear the device registry. - ([@piitaya] - [#26738]) ([linky docs])
- **Elv** - ELV/PCA is now its own integration. Existing configuration should be removed and replaced. Optionally the port for the serial interface can be specified (default is: /dev/ttyUSB0). - ([@majuss] - [#26552]) ([elv docs])
Example configuration entry:
```yaml
elv:
device: "/dev/ttyUSB0"
```
- **Automation** - Custom component developers who started playing with device automations only: we have restructured how integrations can expose their device triggers/conditions/actions. Instead of 1 platform `device_automation.py` it's now `device_action.py`, `device_trigger.py`, `device_condition.py`.
The method to attach a device trigger has been updated from `async_trigger` to `async_attach_trigger` to better reflect what is going on. - ([@balloob] - [#26880]) ([automation docs]) ([binary_sensor docs]) ([deconz docs]) ([device_automation docs]) ([light docs]) ([switch docs]) ([zha docs])
- **Ecobee** - Ecobee will now be set up via config flow. Existing users will have their config imported from ecobee.conf via an import flow so it shouldn't break their experience. Users configuring via configuration.yaml will have their api key and options imported into the flow but will still need to finish authorization via the flow (instead of the configurator component as previously).
The configuration parameter `hold_temp` has been removed, as it was not being used in the climate platform and had no effect on whether the temperature was held indefinitely or not. Users will need to remove the parameter `hold_temp` from configuration.yaml.
Ecobee-specific services will now be registered under the ecobee domain rather than the climate domain, and service names will not include the prefix "ecobee\_" (e.g. the service "climate.ecobee_resume_program" will become "ecobee.resume_program"). - ([@marthoc] - [#26634]) ([ecobee docs])
- **Transmission** - The Transmission integration can now be configured through a config flow via Integrations in the GUI. Once configured all sensors and switches will be created and available for the user.
`monitored_conditions` has been removed so existing users need to update their configuration in configuration.yaml and remove monitored conditions. The existing configuration will be imported as an entry under Integrations. - ([@engrbm87] - [#26434]) ([transmission docs])
Example configuration entry:
```yaml
transmission:
host: 192.168.1.1
```
- **Rainbird** - Rainbird is now its own platform. The configuration of rainbird switches has been moved under `zones:` as part of the `rainbird:` integration. - ([@konikvranik] - [#26393]) ([rainbird docs])
Example configuration entry:
```yaml
rainbird:
host: IP_ADDRESS_OF_MODULE
password: YOUR_PASSWORD
trigger_time: 6
zones:
1:
trigger_time: 6
```
- **Incomfort** - Device state attributes that were causing pointless state changes have been removed:
- `"rf_message_rssi` signal strength (between gateway & boiler), changes almost every scan_interval
- `nodenr` unknown, is static
- `rfstatus_cntr` unknown, changes
This is not likely to be considered a breaking change by users. - ([@zxdavb] - [#26802]) ([incomfort docs])
- **Evohome** - Device state attributes keys have been changed to snake_case and, since this a breaking change, the opportunity was taken to revise/simplify the entire device state attributes schema.
Evohome is a complicated integration, has had major changes in recent times, and is not yet mature - these changes address some bugs and related architectural issues:
- Modify behavior of set_temperature to mirror that of the vendor's UI (e.g. any target temp changes until next setpoint, unless explicitly set otherwise)
- Setpoint datetimes are now correctly converted to local/aware isoformat (internally, and for logging/state attributes)
- Use snake_case for device state attributes
- Add a unique_id for each entity (systemId, zoneID, dhwId)
- Refactoring - remove API wrappers (no longer using private methods)
- Add away mode for DHW (set to permanent off or Auto, depending)([@zxdavb] - [#26810]) ([evohome docs])
- **OpenTherm** - Move climate entity state to hvac_action attribute to comply with climate 1.0. May break e.g. automations. - ([@mvn23] - [#25931]) ([opentherm_gw docs])
- **Genius Hub** - Users connecting to a Hub via the v1 API will need to specify a valid MAC address for the hub (see example YAML, below). Those using the v3 API will be unaffected.
This change is in preperation for for further changes, so the geniushub entities can be given more appropriate `entity_ids`.
Some Sensor entities fro GeniusHub Issues have been renamed, and so will get a new entity ID:
- sensor.errors to sensor.geniushub_errors
- sensor.warnings to sensor.geniushub_warnings
- sensor.information to sensor.geniushub_informationeniushub and bump client to v0.6.26 - ([@zxdavb] - [#26640]) ([geniushub docs])
Example configuration entry:
```yaml
geniushub:
token: JqVFd0UUEi...
mac: 18:CC:23:12:34:56
```
## Beta Fixes
- Only generate device trigger for sensor with unit ([@emontnemery] - [#27152]) ([sensor docs]) (beta fix)
- Add above and below to sensor trigger extra_fields ([@emontnemery] - [#27160]) ([sensor docs]) (beta fix)
- Update connect-box to fix issue with attrs ([@pvizeli] - [#27194]) ([upc_connect docs]) (beta fix)
- Fix validation when automation is saved from frontend ([@emontnemery] - [#27195]) ([automation docs]) (beta fix)
- Fix ecobee binary sensor and sensor unique ids ([@marthoc] - [#27208]) ([ecobee docs]) (beta fix)
- Bump adb-shell to 0.0.4; bump androidtv to 0.0.30 ([@JeffLIrion] - [#27224]) ([androidtv docs]) (beta fix)
- Fix closed status for non horizontal awnings. ([@psicot] - [#26840]) ([tahoma docs]) (beta fix)
- Fix update on cert_expiry startup ([@jjlawren] - [#27137]) ([cert_expiry docs]) (beta fix)
- Fix onvif PTZ service freeze ([@skgsergio] - [#27250]) ([onvif docs]) (beta fix)
- Fix the todoist integration ([@boralyl] - [#27273]) ([todoist docs]) (beta fix)
- Fix Plex media_player.play_media service ([@jjlawren] - [#27278]) ([plex docs]) (beta fix)
- Remove manual config flow step ([@jjlawren] - [#27291]) ([plex docs]) (beta fix)
- Improve speed websocket sends messages ([@balloob] - [#27295]) ([websocket_api docs]) (beta fix)
- Google: Report all states on activating report state ([@balloob] - [#27312]) ([google_assistant docs]) (beta fix)
- Fix single Plex server case ([@jjlawren] - [#27326]) ([plex docs]) (beta fix)
- Updated frontend to 20191002.1 ([@bramkragten] - [#27329]) ([frontend docs]) (beta fix)
- Fix translations for binary_sensor triggers ([@emontnemery] - [#27330]) ([binary_sensor docs]) (beta fix)
- Fix connection issues with withings API by switching to a maintained codebase ([@vangorra] - [#27310]) ([withings docs]) (beta fix)
- Update zigpy-zigate to 0.4.1 ([@doudz] - [#27345]) ([zha docs]) (beta fix)
- Updated frontend to 20191002.2 ([@bramkragten] - [#27370]) ([frontend docs]) (beta fix)
## All changes
- Add support for DOODS Image Processing ([@snowzach] - [#26208]) ([doods docs]) (new-integration)
- Bump zigate to 0.3.0 ([@doudz] - [#26586]) ([zha docs])
- Upgrade youtube_dl to 2019.09.12.1 ([@BKPepe] - [#26593]) ([media_extractor docs])
- Improve bluetooth tracker device code ([@pgilad] - [#26067]) ([bluetooth_tracker docs])
- Disable Watson TTS Telemetry ([@poofyteddy] - [#26253]) ([watson_tts docs])
- Fix Typo ([@SNoof85] - [#26612]) ([cert_expiry docs])
- Refactor Bluetooth Tracker to async ([@pgilad] - [#26614]) ([bluetooth_tracker docs])
- deCONZ - create deconz_events through sensor platform ([@Kane610] - [#26592]) ([deconz docs])
- zha ZCL color loop effect ([@amigan] - [#26549]) ([zha docs])
- Add iaqualink binary sensor and unique_id ([@flz] - [#26616]) ([iaqualink docs]) (new-platform)
- Add group attribute to Homematic IP Cloud ([@SukramJ] - [#26618]) ([homematicip_cloud docs])
- Move deCONZ services to their own file ([@Kane610] - [#26645]) ([deconz docs])
- Add built in weather to Homematic IP Cloud ([@SukramJ] - [#26642]) ([homematicip_cloud docs])
- deCONZ - battery sensor instead of battery attribute ([@Kane610] - [#26591]) ([deconz docs])
- deCONZ - Remove mechanisms to import a configuration from configuration.yaml ([@Kane610] - [#26648]) ([deconz docs])
- Refactor nzbget to support future platform changes ([@chriscla] - [#26462]) ([nzbget docs]) (breaking change)
- Fix Environment Canada weather forecast, retain icon_code sensor ([@michaeldavie] - [#26646]) ([environment_canada docs])
- Emulate color temperature for non-ct lights in light groups ([@bryanyork] - [#23495]) ([google_assistant docs]) ([group docs])
- Use pynzbgetapi exceptions consistently ([@chriscla] - [#26667]) ([nzbget docs])
- deCONZ - Improve service tests ([@Kane610] - [#26663]) ([deconz docs])
- zha: fix 0 second transitions being ignored. ([@abmantis] - [#26654]) ([zha docs])
- pytfiac version bump to 0.4 ([@fredrike] - [#26669]) ([tfiac docs])
- Switch py_nextbus to py_nextbusnext ([@ViViDboarder] - [#26681]) ([nextbus docs])
- Disconnect velux on hass stop ([@gibman] - [#26266]) ([velux docs])
- Improve Envoy detection and support multiple Envoys ([@jesserizzo] - [#26665]) ([enphase_envoy docs])
- Fix volumio set shuffle ([@zewelor] - [#26660]) ([volumio docs])
- Fix mysensors validation for composite entities ([@MartinHjelmare] - [#26666]) ([mysensors docs])
- Add support for automation description ([@emontnemery] - [#26662]) ([automation docs]) ([config docs])
- Add alternative name for Tibber sensors ([@Danielhiversen] - [#26685]) ([tibber docs])
- deCONZ improve light tests ([@Kane610] - [#26697]) ([deconz docs])
- Hide "PTZ is not available on this camera" warning ([@definitio] - [#26649]) ([onvif docs])
- deCONZ rewrite sensor tests ([@Kane610] - [#26679]) ([deconz docs])
- Fix torque degree char ([@roblandry] - [#26183]) ([torque docs])
- Change datetime.now() to dt_util.now() ([@tsvi] - [#26582])
- Add additional needles to glances cpu_temp attribute ([@shutupflanders] - [#22311]) ([glances docs])
- Move alexa integration to use dt_util ([@tsvi] - [#26723]) ([alexa docs])
- Bumps pytest to 5.1.2 ([@frenck] - [#26718])
- Bumps aiohttp to 3.6.0 ([@frenck] - [#26728])
- Bumps pre-commit to 1.18.3 ([@frenck] - [#26717])
- Update Solax Library to 0.2.2 ([@squishykid] - [#26705]) ([solax docs])
- Bump aiohttp to 3.6.1 ([@frenck] - [#26739])
- Add Plex config flow support ([@jjlawren] - [#26548]) ([plex docs])
- Bump restrictedpython to 5.0 ([@frenck] - [#26741])
- Izone component ([@Swamp-Ig] - [#24550]) ([izone docs]) (new-integration)
- Bump influxdb to 5.2.3 ([@frenck] - [#26743]) ([influxdb docs])
- Update codeowners ([@amelchio] - [#26733]) ([lifx docs]) ([lifx_cloud docs]) ([netgear_lte docs]) ([sonos docs])
- Add transport data from maps.yandex.ru api ([@rishatik92] - [#26252]) ([yandex_transport docs]) (new-integration)
- deCONZ improve gateway tests ([@Kane610] - [#26709]) ([deconz docs])
- Revert "Add transport data from maps.yandex.ru api (#26252)" ([@pvizeli] - [#26762]) ([yandex_transport docs])
- Bump openwrt-luci-rpc to version 1.1.1 ([@flowolf] - [#26759]) ([luci docs])
- Type hint additions ([@scop] - [#26765]) ([automation docs]) ([cover docs]) ([frontend docs]) ([http docs]) ([media_player docs]) ([switch docs])
- Add transport data from maps.yandex.ru api ([@rishatik92] - [#26766]) ([yandex_transport docs])
- ZHA siren and warning device support ([@dmulcahey] - [#26046]) ([zha docs])
- Bump aiowwlln to 2.0.2 ([@bachya] - [#26769]) ([wwlln docs])
- Bump simplisafe-python to 5.0.1 ([@bachya] - [#26775]) ([simplisafe docs])
- Add integration scaffolding script ([@balloob] - [#26777])
- Bump HAP-python to 2.6.0 for homekit ([@Jc2k] - [#26783]) ([homekit docs])
- Bump pynws version to 0.8.1 ([@MatthewFlamm] - [#26770]) ([nws docs])
- Add optimizer data to solaredge_local ([@scheric] - [#26708]) ([solaredge_local docs])
- Mqtt binary sensor expire after ([@KiLLeRRaT] - [#26058]) ([mqtt docs])
- Upgrade importlib-metadata to 0.23 ([@fabaff] - [#26787])
- Upgrade python-whois to 0.7.2 ([@fabaff] - [#26788]) ([whois docs])
- Fix doods missing detector name kwarg ([@snowzach] - [#26784]) ([doods docs])
- Add myself as a pi_hole codeowner ([@johnluetke] - [#26796]) ([pi_hole docs])
- Fix spaceapi ([@Bouni] - [#26453]) ([spaceapi docs]) (breaking change)
- Update light.py ([@CQoute] - [#26703]) ([esphome docs])
- Bump hbmqtt to 0.9.5 ([@frenck] - [#26804]) ([mqtt docs])
- Bump python-slugify to 3.0.4 ([@frenck] - [#26801])
- Bump pytest to 5.1.3 ([@frenck] - [#26794])
- Bump iperf3 to 0.1.11 ([@frenck] - [#26795]) ([iperf3 docs])
- Bump shodan to 1.17.0 ([@frenck] - [#26797]) ([shodan docs])
- Bump request_mock to 1.7.0 ([@frenck] - [#26799])
- Bump pylutron to 0.2.5 ([@thecynic] - [#26815])
- Upgrade sendgrid to 6.1.0 ([@fabaff] - [#26809]) ([sendgrid docs])
- Exempt 'Help wanted' issue from stale bot ([@frenck] - [#26829])
- Add device automation support to binary_sensor entities ([@emontnemery] - [#26643]) ([binary_sensor docs])
- Update Vivotek camera component ([@HarlemSquirrel] - [#26754]) ([vivotek docs])
- Add basic support for IKEA Fyrtur blinds ([@ggravlingen] - [#26659]) ([tradfri docs]) (new-platform)
- Unload Plex config entries ([@jjlawren] - [#26771]) ([plex docs])
- Add Kaiterra integration ([@Michsior14] - [#26661]) ([kaiterra docs]) (new-integration)
- Add manual step to Plex config flow ([@jjlawren] - [#26773]) ([plex docs])
- Add Ombi integration ([@larssont] - [#26755]) ([ombi docs]) (new-integration)
- Prevent Wemo doing I/O in event loop ([@balloob] - [#26835]) ([wemo docs])
- Split scaffolding script ([@balloob] - [#26832])
- Remove deprecated ups integration (ADR-0004) ([@frenck] - [#26824]) (breaking change)
- Remove deprecated usps integration (ADR-0004) ([@frenck] - [#26823]) (breaking change)
- Remove deprecated sytadin integration (ADR-0004) ([@frenck] - [#26819]) (breaking change)
- Add here_travel_time ([@eifinger] - [#24603]) ([here_travel_time docs]) (new-integration)
- Remove deprecated srp_energy integration (ADR-0004) ([@frenck] - [#26826]) (breaking change)
- Remove deprecated fedex integration (ADR-0004) ([@frenck] - [#26822]) (breaking change)
- Store ZHA light brightness when fading off to turn on at the correct brightness ([@abmantis] - [#26680]) ([zha docs])
- Bump pyotp to 2.3.0 ([@frenck] - [#26849]) ([otp docs])
- Remove deprecated linksys_ap integration (ADR-0004) ([@frenck] - [#26847]) (breaking change)
- Bump up ZHA dependencies ([@Adminiuga] - [#26746])
- fix onvif/camera setting up error ([@sanyatuning] - [#26825]) ([onvif docs])
- Bump homematicip_cloud to 0.10.11 ([@SukramJ] - [#26852]) ([homematicip_cloud docs])
- Group Linky sensors to Linky meter device ([@piitaya] - [#26738]) ([linky docs]) (breaking change)
- Add unit to 'charging_level_hv' bwm_connected_drive sensor ([@timmccor] - [#26861]) ([bmw_connected_drive docs])
- Add reproduce state template ([@balloob] - [#26866])
- Put draw_box in image_processing ([@robmarkcole] - [#26712]) ([doods docs]) ([image_processing docs]) ([tensorflow docs])
- Move elv integration to component and bump pypca ([@majuss] - [#26552]) ([elv docs]) (breaking change)
- Add availability_template to Template Sensor platform ([@grillp] - [#26516]) ([template docs])
- Add device automation support to ZHA ([@dmulcahey] - [#26821]) ([zha docs])
- Removes unnecessary else/elif blocks ([@frenck] - [#26884])
- Add and corrects typehints in Entity helper & core class ([@frenck] - [#26805])
- Add comment for clarity to helper.entity.enabled() ([@frenck] - [#26793])
- Reorg device automation ([@balloob] - [#26880]) ([automation docs]) ([binary_sensor docs]) ([deconz docs]) ([device_automation docs]) ([light docs]) ([switch docs]) ([zha docs]) (breaking change)
- Use Python3 new super syntax sugar ([@frenck] - [#26890])
- bump quirks ([@dmulcahey] - [#26885]) ([zha docs])
- Update zigpy_zigate to 0.4.0 ([@doudz] - [#26883]) ([zha docs])
- Inverting states for opening/closing Homekit covers ([@tleegaard] - [#26872]) ([homekit_controller docs])
- Removes unnecessary utf8 source encoding declarations ([@frenck] - [#26887]) ([lcn docs]) ([yandex_transport docs])
- Removes unnecessary print_function future import ([@frenck] - [#26888])
- Add availability_template to Template Switch platform ([@grillp] - [#26513]) ([template docs])
- Bump ndms2-client to 0.0.9 ([@foxel] - [#26899]) ([keenetic_ndms2 docs])
- Add voltage attribute to Xiaomi Aqara devices ([@zhumuht] - [#26876]) ([xiaomi_aqara docs])
- Fix bed_activity history chart of the Xiaomi Aqara vibration sensor ([@zhumuht] - [#26875]) ([xiaomi_aqara docs])
- Fix missing whitespace around arithmetic operator ([@JeffLIrion] - [#26908]) ([xiaomi_aqara docs])
- deCONZ - Improve ssdp discovery by storing uuid in config entry ([@Kane610] - [#26882]) ([deconz docs])
- Add google_assistant alarm_control_panel ([@engrbm87] - [#26249]) ([google_assistant docs])
- Add call direction sensor for Obihai ([@dshokouhi] - [#26867]) ([obihai docs])
- deCONZ - Increase bridge discovery robustness in config flow ([@Kane610] - [#26911]) ([deconz docs])
- Add config flow to ecobee ([@marthoc] - [#26634]) ([ecobee docs]) (breaking change)
- Remove lamps and groups from ha when removed from Hue ([@bramkragten] - [#26881]) ([hue docs])
- Add MySensors ACK ([@petewill] - [#26894]) ([mysensors docs])
- Add mysensors codeowner ([@MartinHjelmare] - [#26917]) ([mysensors docs])
- Bump pyobihai, add unique ID and availability ([@dshokouhi] - [#26922]) ([obihai docs])
- Add Plex config options support ([@jjlawren] - [#26870]) ([plex docs])
- Add config flow to transmission ([@engrbm87] - [#26434]) ([transmission docs]) (breaking change)
- Centralize rainbird config and add binary sensor platform ([@konikvranik] - [#26393]) ([rainbird docs]) (breaking change) (new-platform)
- Add ecobee services to create and delete vacations ([@marthoc] - [#26923]) ([ecobee docs])
- Bump androidtv to 0.0.28 ([@JeffLIrion] - [#26906]) ([androidtv docs])
- Add more ebusd Vaillant "bai" sensors ([@sashao] - [#26750]) ([ebusd docs])
- Add xbox live custom update interval ([@MartinHjelmare] - [#26939]) ([xbox_live docs])
- Guard against non supported entities ([@balloob] - [#26941]) ([alexa docs])
- Bump pyowlet to 1.0.3 ([@jaburges] - [#26892]) ([owlet docs])
- Revert Nest HVAC mode when disabling Eco mode ([@joe248] - [#26934]) ([nest docs])
- Fix ecobee integration ([@marthoc] - [#26951]) ([ecobee docs])
- Add CO2 level reading for Kaiterra integration ([@Michsior14] - [#26935]) ([kaiterra docs])
- Improve validation of device trigger config ([@emontnemery] - [#26910]) ([automation docs]) ([config docs]) ([device_automation docs])
- Add device action support for ZHA ([@dmulcahey] - [#26903]) ([zha docs])
- Add support for Z-Wave battery level ([@oandrew] - [#26943]) ([zwave docs])
- Update Alexa discovery description ([@bramkragten] - [#26933]) ([alexa docs])
- Add templates to scaffold device_trigger, device_condition, ([@balloob] - [#26871])
- Upgrade mypy to 0.730, address raised issues ([@scop] - [#26959]) ([http docs])
- Add hive boost to climate and water_heater ([@KJonline] - [#26789]) ([hive docs])
- Bump Travis timeout to 50 minutes ([@scop] - [#26978])
- Remove no longer needed Python < 3.6 compatibility code ([@scop] - [#27024])
- Fix possible OpenUV exception due to missing data ([@bachya] - [#26958]) ([openuv docs])
- Update pythonegardia to 1.0.40 ([@SneakSnackSnake] - [#27009]) ([egardia docs])
- Improve ecobee service schemas ([@marthoc] - [#26955]) ([ecobee docs])
- Add more providers, bump yessssms version to 0.4.1 ([@flowolf] - [#26874]) ([yessssms docs])
- Upgrade youtube_dl to 2019.09.28 ([@BKPepe] - [#27031]) ([media_extractor docs])
- Add availability_template to Template Cover platform ([@grillp] - [#26509]) ([template docs])
- Add availability_template to Template Binary Sensor platform ([@grillp] - [#26510]) ([template docs])
- Add availability_template to Template Fan platform ([@grillp] - [#26511]) ([template docs])
- Add availability_template to Template Light platform ([@grillp] - [#26512]) ([template docs])
- Add availability_template to Template Vacuum platform ([@grillp] - [#26514]) ([template docs])
- Add create, remove of devices for HomematicIP_Cloud ([@SukramJ] - [#27030]) ([homematicip_cloud docs])
- Add venstar support for hvac action ([@david81] - [#26956]) ([venstar docs])
- Change hive hotwater to hot_water + bug fix ([@KJonline] - [#27038]) ([hive docs])
- Return esphome cover position as Integer ([@neffs] - [#27039]) ([esphome docs])
- Type hint additions ([@scop] - [#26831]) ([device_automation docs]) ([frontend docs]) ([group docs]) ([media_player docs]) ([persistent_notification docs]) ([sun docs]) ([websocket_api docs]) ([zone docs])
- Upgrade pytest to 5.2.0 ([@scop] - [#27058])
- Bump zha quirks to 0.0.26 ([@dmulcahey] - [#27051]) ([zha docs])
- Add Pi-hole enable and disable services ([@johnluetke] - [#27055]) ([pi_hole docs])
- add utc tz to forecast ([@MatthewFlamm] - [#27049]) ([darksky docs])
- Fix rest_command when server is unreachable ([@sebasje] - [#26948]) ([rest_command docs])
- Fix incomfort and Bump client to 0.3.5 ([@zxdavb] - [#26802]) ([incomfort docs]) (breaking change)
- Add support for SOMA Smartshades devices ([@ratsept] - [#26226]) ([soma docs]) (new-integration)
- Bump pyecobee to 0.1.4 ([@marthoc] - [#27074]) ([ecobee docs])
- Fix SSL connections to Pi-hole ([@johnluetke] - [#27073]) ([pi_hole docs])
- Bump shodan to 1.19.0 ([@frenck] - [#27079]) ([shodan docs])
- Add some icons for Obihai ([@dshokouhi] - [#27075]) ([obihai docs])
- bumped version of upstream library ([@exxamalte] - [#27083]) ([geonetnz_quakes docs])
- Remove last of device tracker scanner ([@Kane610] - [#27082]) ([unifi docs])
- Bugfix evohome ([@zxdavb] - [#26810]) ([evohome docs]) (breaking change)
- Add saj component ([@fredericvl] - [#26902]) ([saj docs]) (new-integration)
- Add availability_template to Template Lock platform ([@grillp] - [#26517]) ([template docs])
- Cleanup coroutine threadsafe ([@pvizeli] - [#27080]) ([bluetooth_le_tracker docs]) ([group docs]) ([mqtt docs]) ([proxy docs])
- Plex external config flow ([@jjlawren] - [#26936]) ([plex docs])
- Bump attrs to 19.2.0 ([@frenck] - [#27102])
- Update meteoalertapi to version 0.1.6 ([@rolfberkenbosch] - [#27099]) ([meteoalarm docs])
- Nzbget services ([@chriscla] - [#26900]) ([nzbget docs])
- Delete here_travel_time dead code COORDINATE_SCHEMA ([@eifinger] - [#27090]) ([here_travel_time docs])
- Add missing http dependency ([@jjlawren] - [#27097]) ([plex docs])
- Add entity registry support to ecobee integration ([@marthoc] - [#27088]) ([ecobee docs])
- Update opentherm_gw.climate to match Climate 1.0 ([@mvn23] - [#25931]) ([opentherm_gw docs]) (breaking change)
- Improve validation of device action config ([@emontnemery] - [#27029]) ([automation docs])
- Bump adb-shell to 0.0.3 ([@JeffLIrion] - [#27108]) ([androidtv docs])
- Add Vera last user and low battery attributes ([@colohan] - [#27043]) ([vera docs])
- Add neural support to amazon polly ([@bbrendon] - [#27101]) ([amazon_polly docs])
- Bump androidtv to 0.0.29 ([@JeffLIrion] - [#27120]) ([androidtv docs])
- Update documentation link URL for integrations in all manifests ([@frenck] - [#27114])
- Tweak geniushub and bump client to v0.6.26 ([@zxdavb] - [#26640]) ([geniushub docs]) (breaking change)
- move ATTR_MODE to homeassistant.const ([@eifinger] - [#27118])
- Update documentation link URL for integrations (part2) ([@frenck] - [#27117])
- Fix generated comment in CODEOWNERS ([@tribut] - [#27115])
- Disable flaky/slow test ([@emontnemery] - [#27125])
- UniFi - Try to handle when UniFi erroneously marks offline client as wired ([@Kane610] - [#26960]) ([unifi docs])
- deCONZ - Support Symfonisk sound controller with device triggers ([@Kane610] - [#26913]) ([deconz docs])
- Add support for `for` to binary_sensor, light and switch device triggers ([@emontnemery] - [#26658]) ([device_automation docs])
- Updated frontend to 20191002.0 ([@bramkragten] - [#27134]) ([frontend docs])
- Fix error on failed Plex setup ([@jjlawren] - [#27132]) ([plex docs])
- Bump up ZHA dependencies. ([@Adminiuga] - [#27127]) ([zha docs])
- Fix unavailable climate entities in Alexa StateReport ([@ochlocracy] - [#27128]) ([alexa docs])
- gpiozero requirement ver ([@bbrendon] - [#27129]) ([remote_rpi_gpio docs])
- Update KNX integration to xknx 0.11.2 ([@farmio] - [#27130]) ([knx docs])
- Display Fan entity as Fan category in Alexa ([@ochlocracy] - [#27135]) ([alexa docs])
- Improve validation of device condition config ([@emontnemery] - [#27131]) ([automation docs]) ([binary_sensor docs]) ([light docs]) ([switch docs])
- Fix colorTemperatureInKelvin in Alexa report when light is off ([@ochlocracy] - [#27107]) ([alexa docs])
- Add device trigger support to sensor entities ([@emontnemery] - [#27133]) ([automation docs]) ([binary_sensor docs]) ([device_automation docs]) ([sensor docs])
- Add Google Report State ([@balloob] - [#27112]) ([alexa docs]) ([cloud docs]) ([google_assistant docs])
- Handle all single zone thermostats ([@zxdavb] - [#27168]) ([evohome docs])
- Only generate device trigger for sensor with unit ([@emontnemery] - [#27152]) ([sensor docs]) (beta fix)
- Add above and below to sensor trigger extra_fields ([@emontnemery] - [#27160]) ([sensor docs]) (beta fix)
- Update connect-box to fix issue with attrs ([@pvizeli] - [#27194]) ([upc_connect docs]) (beta fix)
- Fix validation when automation is saved from frontend ([@emontnemery] - [#27195]) ([automation docs]) (beta fix)
- Fix ecobee binary sensor and sensor unique ids ([@marthoc] - [#27208]) ([ecobee docs]) (beta fix)
- Bump adb-shell to 0.0.4; bump androidtv to 0.0.30 ([@JeffLIrion] - [#27224]) ([androidtv docs]) (beta fix)
- Fix closed status for non horizontal awnings. ([@psicot] - [#26840]) ([tahoma docs]) (beta fix)
- Fix update on cert_expiry startup ([@jjlawren] - [#27137]) ([cert_expiry docs]) (beta fix)
- Fix onvif PTZ service freeze ([@skgsergio] - [#27250]) ([onvif docs]) (beta fix)
- Fix the todoist integration ([@boralyl] - [#27273]) ([todoist docs]) (beta fix)
- Fix Plex media_player.play_media service ([@jjlawren] - [#27278]) ([plex docs]) (beta fix)
- Remove manual config flow step ([@jjlawren] - [#27291]) ([plex docs]) (beta fix)
- Improve speed websocket sends messages ([@balloob] - [#27295]) ([websocket_api docs]) (beta fix)
- Google: Report all states on activating report state ([@balloob] - [#27312]) ([google_assistant docs]) (beta fix)
- Fix single Plex server case ([@jjlawren] - [#27326]) ([plex docs]) (beta fix)
- Updated frontend to 20191002.1 ([@bramkragten] - [#27329]) ([frontend docs]) (beta fix)
- Fix translations for binary_sensor triggers ([@emontnemery] - [#27330]) ([binary_sensor docs]) (beta fix)
- Fix connection issues with withings API by switching to a maintained codebase ([@vangorra] - [#27310]) ([withings docs]) (beta fix)
- Update zigpy-zigate to 0.4.1 ([@doudz] - [#27345]) ([zha docs]) (beta fix)
- Updated frontend to 20191002.2 ([@bramkragten] - [#27370]) ([frontend docs]) (beta fix)
[#22311]: https://github.com/home-assistant/home-assistant/pull/22311
[#23495]: https://github.com/home-assistant/home-assistant/pull/23495
[#24550]: https://github.com/home-assistant/home-assistant/pull/24550
[#24603]: https://github.com/home-assistant/home-assistant/pull/24603
[#25931]: https://github.com/home-assistant/home-assistant/pull/25931
[#26046]: https://github.com/home-assistant/home-assistant/pull/26046
[#26058]: https://github.com/home-assistant/home-assistant/pull/26058
[#26067]: https://github.com/home-assistant/home-assistant/pull/26067
[#26183]: https://github.com/home-assistant/home-assistant/pull/26183
[#26208]: https://github.com/home-assistant/home-assistant/pull/26208
[#26226]: https://github.com/home-assistant/home-assistant/pull/26226
[#26249]: https://github.com/home-assistant/home-assistant/pull/26249
[#26252]: https://github.com/home-assistant/home-assistant/pull/26252
[#26253]: https://github.com/home-assistant/home-assistant/pull/26253
[#26266]: https://github.com/home-assistant/home-assistant/pull/26266
[#26393]: https://github.com/home-assistant/home-assistant/pull/26393
[#26434]: https://github.com/home-assistant/home-assistant/pull/26434
[#26453]: https://github.com/home-assistant/home-assistant/pull/26453
[#26462]: https://github.com/home-assistant/home-assistant/pull/26462
[#26509]: https://github.com/home-assistant/home-assistant/pull/26509
[#26510]: https://github.com/home-assistant/home-assistant/pull/26510
[#26511]: https://github.com/home-assistant/home-assistant/pull/26511
[#26512]: https://github.com/home-assistant/home-assistant/pull/26512
[#26513]: https://github.com/home-assistant/home-assistant/pull/26513
[#26514]: https://github.com/home-assistant/home-assistant/pull/26514
[#26516]: https://github.com/home-assistant/home-assistant/pull/26516
[#26517]: https://github.com/home-assistant/home-assistant/pull/26517
[#26548]: https://github.com/home-assistant/home-assistant/pull/26548
[#26549]: https://github.com/home-assistant/home-assistant/pull/26549
[#26552]: https://github.com/home-assistant/home-assistant/pull/26552
[#26582]: https://github.com/home-assistant/home-assistant/pull/26582
[#26586]: https://github.com/home-assistant/home-assistant/pull/26586
[#26591]: https://github.com/home-assistant/home-assistant/pull/26591
[#26592]: https://github.com/home-assistant/home-assistant/pull/26592
[#26593]: https://github.com/home-assistant/home-assistant/pull/26593
[#26612]: https://github.com/home-assistant/home-assistant/pull/26612
[#26614]: https://github.com/home-assistant/home-assistant/pull/26614
[#26616]: https://github.com/home-assistant/home-assistant/pull/26616
[#26618]: https://github.com/home-assistant/home-assistant/pull/26618
[#26634]: https://github.com/home-assistant/home-assistant/pull/26634
[#26640]: https://github.com/home-assistant/home-assistant/pull/26640
[#26642]: https://github.com/home-assistant/home-assistant/pull/26642
[#26643]: https://github.com/home-assistant/home-assistant/pull/26643
[#26645]: https://github.com/home-assistant/home-assistant/pull/26645
[#26646]: https://github.com/home-assistant/home-assistant/pull/26646
[#26648]: https://github.com/home-assistant/home-assistant/pull/26648
[#26649]: https://github.com/home-assistant/home-assistant/pull/26649
[#26654]: https://github.com/home-assistant/home-assistant/pull/26654
[#26658]: https://github.com/home-assistant/home-assistant/pull/26658
[#26659]: https://github.com/home-assistant/home-assistant/pull/26659
[#26660]: https://github.com/home-assistant/home-assistant/pull/26660
[#26661]: https://github.com/home-assistant/home-assistant/pull/26661
[#26662]: https://github.com/home-assistant/home-assistant/pull/26662
[#26663]: https://github.com/home-assistant/home-assistant/pull/26663
[#26665]: https://github.com/home-assistant/home-assistant/pull/26665
[#26666]: https://github.com/home-assistant/home-assistant/pull/26666
[#26667]: https://github.com/home-assistant/home-assistant/pull/26667
[#26669]: https://github.com/home-assistant/home-assistant/pull/26669
[#26679]: https://github.com/home-assistant/home-assistant/pull/26679
[#26680]: https://github.com/home-assistant/home-assistant/pull/26680
[#26681]: https://github.com/home-assistant/home-assistant/pull/26681
[#26685]: https://github.com/home-assistant/home-assistant/pull/26685
[#26697]: https://github.com/home-assistant/home-assistant/pull/26697
[#26703]: https://github.com/home-assistant/home-assistant/pull/26703
[#26705]: https://github.com/home-assistant/home-assistant/pull/26705
[#26708]: https://github.com/home-assistant/home-assistant/pull/26708
[#26709]: https://github.com/home-assistant/home-assistant/pull/26709
[#26712]: https://github.com/home-assistant/home-assistant/pull/26712
[#26717]: https://github.com/home-assistant/home-assistant/pull/26717
[#26718]: https://github.com/home-assistant/home-assistant/pull/26718
[#26723]: https://github.com/home-assistant/home-assistant/pull/26723
[#26728]: https://github.com/home-assistant/home-assistant/pull/26728
[#26733]: https://github.com/home-assistant/home-assistant/pull/26733
[#26738]: https://github.com/home-assistant/home-assistant/pull/26738
[#26739]: https://github.com/home-assistant/home-assistant/pull/26739
[#26741]: https://github.com/home-assistant/home-assistant/pull/26741
[#26743]: https://github.com/home-assistant/home-assistant/pull/26743
[#26746]: https://github.com/home-assistant/home-assistant/pull/26746
[#26750]: https://github.com/home-assistant/home-assistant/pull/26750
[#26754]: https://github.com/home-assistant/home-assistant/pull/26754
[#26755]: https://github.com/home-assistant/home-assistant/pull/26755
[#26759]: https://github.com/home-assistant/home-assistant/pull/26759
[#26762]: https://github.com/home-assistant/home-assistant/pull/26762
[#26765]: https://github.com/home-assistant/home-assistant/pull/26765
[#26766]: https://github.com/home-assistant/home-assistant/pull/26766
[#26769]: https://github.com/home-assistant/home-assistant/pull/26769
[#26770]: https://github.com/home-assistant/home-assistant/pull/26770
[#26771]: https://github.com/home-assistant/home-assistant/pull/26771
[#26773]: https://github.com/home-assistant/home-assistant/pull/26773
[#26775]: https://github.com/home-assistant/home-assistant/pull/26775
[#26777]: https://github.com/home-assistant/home-assistant/pull/26777
[#26783]: https://github.com/home-assistant/home-assistant/pull/26783
[#26784]: https://github.com/home-assistant/home-assistant/pull/26784
[#26787]: https://github.com/home-assistant/home-assistant/pull/26787
[#26788]: https://github.com/home-assistant/home-assistant/pull/26788
[#26789]: https://github.com/home-assistant/home-assistant/pull/26789
[#26793]: https://github.com/home-assistant/home-assistant/pull/26793
[#26794]: https://github.com/home-assistant/home-assistant/pull/26794
[#26795]: https://github.com/home-assistant/home-assistant/pull/26795
[#26796]: https://github.com/home-assistant/home-assistant/pull/26796
[#26797]: https://github.com/home-assistant/home-assistant/pull/26797
[#26799]: https://github.com/home-assistant/home-assistant/pull/26799
[#26801]: https://github.com/home-assistant/home-assistant/pull/26801
[#26802]: https://github.com/home-assistant/home-assistant/pull/26802
[#26804]: https://github.com/home-assistant/home-assistant/pull/26804
[#26805]: https://github.com/home-assistant/home-assistant/pull/26805
[#26809]: https://github.com/home-assistant/home-assistant/pull/26809
[#26810]: https://github.com/home-assistant/home-assistant/pull/26810
[#26815]: https://github.com/home-assistant/home-assistant/pull/26815
[#26819]: https://github.com/home-assistant/home-assistant/pull/26819
[#26821]: https://github.com/home-assistant/home-assistant/pull/26821
[#26822]: https://github.com/home-assistant/home-assistant/pull/26822
[#26823]: https://github.com/home-assistant/home-assistant/pull/26823
[#26824]: https://github.com/home-assistant/home-assistant/pull/26824
[#26825]: https://github.com/home-assistant/home-assistant/pull/26825
[#26826]: https://github.com/home-assistant/home-assistant/pull/26826
[#26829]: https://github.com/home-assistant/home-assistant/pull/26829
[#26831]: https://github.com/home-assistant/home-assistant/pull/26831
[#26832]: https://github.com/home-assistant/home-assistant/pull/26832
[#26835]: https://github.com/home-assistant/home-assistant/pull/26835
[#26840]: https://github.com/home-assistant/home-assistant/pull/26840
[#26847]: https://github.com/home-assistant/home-assistant/pull/26847
[#26849]: https://github.com/home-assistant/home-assistant/pull/26849
[#26852]: https://github.com/home-assistant/home-assistant/pull/26852
[#26861]: https://github.com/home-assistant/home-assistant/pull/26861
[#26866]: https://github.com/home-assistant/home-assistant/pull/26866
[#26867]: https://github.com/home-assistant/home-assistant/pull/26867
[#26870]: https://github.com/home-assistant/home-assistant/pull/26870
[#26871]: https://github.com/home-assistant/home-assistant/pull/26871
[#26872]: https://github.com/home-assistant/home-assistant/pull/26872
[#26874]: https://github.com/home-assistant/home-assistant/pull/26874
[#26875]: https://github.com/home-assistant/home-assistant/pull/26875
[#26876]: https://github.com/home-assistant/home-assistant/pull/26876
[#26880]: https://github.com/home-assistant/home-assistant/pull/26880
[#26881]: https://github.com/home-assistant/home-assistant/pull/26881
[#26882]: https://github.com/home-assistant/home-assistant/pull/26882
[#26883]: https://github.com/home-assistant/home-assistant/pull/26883
[#26884]: https://github.com/home-assistant/home-assistant/pull/26884
[#26885]: https://github.com/home-assistant/home-assistant/pull/26885
[#26887]: https://github.com/home-assistant/home-assistant/pull/26887
[#26888]: https://github.com/home-assistant/home-assistant/pull/26888
[#26890]: https://github.com/home-assistant/home-assistant/pull/26890
[#26892]: https://github.com/home-assistant/home-assistant/pull/26892
[#26894]: https://github.com/home-assistant/home-assistant/pull/26894
[#26899]: https://github.com/home-assistant/home-assistant/pull/26899
[#26900]: https://github.com/home-assistant/home-assistant/pull/26900
[#26902]: https://github.com/home-assistant/home-assistant/pull/26902
[#26903]: https://github.com/home-assistant/home-assistant/pull/26903
[#26906]: https://github.com/home-assistant/home-assistant/pull/26906
[#26908]: https://github.com/home-assistant/home-assistant/pull/26908
[#26910]: https://github.com/home-assistant/home-assistant/pull/26910
[#26911]: https://github.com/home-assistant/home-assistant/pull/26911
[#26913]: https://github.com/home-assistant/home-assistant/pull/26913
[#26917]: https://github.com/home-assistant/home-assistant/pull/26917
[#26922]: https://github.com/home-assistant/home-assistant/pull/26922
[#26923]: https://github.com/home-assistant/home-assistant/pull/26923
[#26933]: https://github.com/home-assistant/home-assistant/pull/26933
[#26934]: https://github.com/home-assistant/home-assistant/pull/26934
[#26935]: https://github.com/home-assistant/home-assistant/pull/26935
[#26936]: https://github.com/home-assistant/home-assistant/pull/26936
[#26939]: https://github.com/home-assistant/home-assistant/pull/26939
[#26941]: https://github.com/home-assistant/home-assistant/pull/26941
[#26943]: https://github.com/home-assistant/home-assistant/pull/26943
[#26948]: https://github.com/home-assistant/home-assistant/pull/26948
[#26951]: https://github.com/home-assistant/home-assistant/pull/26951
[#26955]: https://github.com/home-assistant/home-assistant/pull/26955
[#26956]: https://github.com/home-assistant/home-assistant/pull/26956
[#26958]: https://github.com/home-assistant/home-assistant/pull/26958
[#26959]: https://github.com/home-assistant/home-assistant/pull/26959
[#26960]: https://github.com/home-assistant/home-assistant/pull/26960
[#26978]: https://github.com/home-assistant/home-assistant/pull/26978
[#27009]: https://github.com/home-assistant/home-assistant/pull/27009
[#27024]: https://github.com/home-assistant/home-assistant/pull/27024
[#27029]: https://github.com/home-assistant/home-assistant/pull/27029
[#27030]: https://github.com/home-assistant/home-assistant/pull/27030
[#27031]: https://github.com/home-assistant/home-assistant/pull/27031
[#27038]: https://github.com/home-assistant/home-assistant/pull/27038
[#27039]: https://github.com/home-assistant/home-assistant/pull/27039
[#27043]: https://github.com/home-assistant/home-assistant/pull/27043
[#27049]: https://github.com/home-assistant/home-assistant/pull/27049
[#27051]: https://github.com/home-assistant/home-assistant/pull/27051
[#27055]: https://github.com/home-assistant/home-assistant/pull/27055
[#27058]: https://github.com/home-assistant/home-assistant/pull/27058
[#27073]: https://github.com/home-assistant/home-assistant/pull/27073
[#27074]: https://github.com/home-assistant/home-assistant/pull/27074
[#27075]: https://github.com/home-assistant/home-assistant/pull/27075
[#27079]: https://github.com/home-assistant/home-assistant/pull/27079
[#27080]: https://github.com/home-assistant/home-assistant/pull/27080
[#27082]: https://github.com/home-assistant/home-assistant/pull/27082
[#27083]: https://github.com/home-assistant/home-assistant/pull/27083
[#27088]: https://github.com/home-assistant/home-assistant/pull/27088
[#27090]: https://github.com/home-assistant/home-assistant/pull/27090
[#27097]: https://github.com/home-assistant/home-assistant/pull/27097
[#27099]: https://github.com/home-assistant/home-assistant/pull/27099
[#27101]: https://github.com/home-assistant/home-assistant/pull/27101
[#27102]: https://github.com/home-assistant/home-assistant/pull/27102
[#27107]: https://github.com/home-assistant/home-assistant/pull/27107
[#27108]: https://github.com/home-assistant/home-assistant/pull/27108
[#27112]: https://github.com/home-assistant/home-assistant/pull/27112
[#27114]: https://github.com/home-assistant/home-assistant/pull/27114
[#27115]: https://github.com/home-assistant/home-assistant/pull/27115
[#27117]: https://github.com/home-assistant/home-assistant/pull/27117
[#27118]: https://github.com/home-assistant/home-assistant/pull/27118
[#27120]: https://github.com/home-assistant/home-assistant/pull/27120
[#27125]: https://github.com/home-assistant/home-assistant/pull/27125
[#27127]: https://github.com/home-assistant/home-assistant/pull/27127
[#27128]: https://github.com/home-assistant/home-assistant/pull/27128
[#27129]: https://github.com/home-assistant/home-assistant/pull/27129
[#27130]: https://github.com/home-assistant/home-assistant/pull/27130
[#27131]: https://github.com/home-assistant/home-assistant/pull/27131
[#27132]: https://github.com/home-assistant/home-assistant/pull/27132
[#27133]: https://github.com/home-assistant/home-assistant/pull/27133
[#27134]: https://github.com/home-assistant/home-assistant/pull/27134
[#27135]: https://github.com/home-assistant/home-assistant/pull/27135
[#27137]: https://github.com/home-assistant/home-assistant/pull/27137
[#27152]: https://github.com/home-assistant/home-assistant/pull/27152
[#27160]: https://github.com/home-assistant/home-assistant/pull/27160
[#27168]: https://github.com/home-assistant/home-assistant/pull/27168
[#27194]: https://github.com/home-assistant/home-assistant/pull/27194
[#27195]: https://github.com/home-assistant/home-assistant/pull/27195
[#27208]: https://github.com/home-assistant/home-assistant/pull/27208
[#27224]: https://github.com/home-assistant/home-assistant/pull/27224
[#27250]: https://github.com/home-assistant/home-assistant/pull/27250
[#27273]: https://github.com/home-assistant/home-assistant/pull/27273
[#27278]: https://github.com/home-assistant/home-assistant/pull/27278
[#27291]: https://github.com/home-assistant/home-assistant/pull/27291
[#27295]: https://github.com/home-assistant/home-assistant/pull/27295
[#27310]: https://github.com/home-assistant/home-assistant/pull/27310
[#27312]: https://github.com/home-assistant/home-assistant/pull/27312
[#27326]: https://github.com/home-assistant/home-assistant/pull/27326
[#27329]: https://github.com/home-assistant/home-assistant/pull/27329
[#27330]: https://github.com/home-assistant/home-assistant/pull/27330
[#27345]: https://github.com/home-assistant/home-assistant/pull/27345
[#27370]: https://github.com/home-assistant/home-assistant/pull/27370
[@adminiuga]: https://github.com/Adminiuga
[@bkpepe]: https://github.com/BKPepe
[@bouni]: https://github.com/Bouni
[@cqoute]: https://github.com/CQoute
[@danielhiversen]: https://github.com/Danielhiversen
[@harlemsquirrel]: https://github.com/HarlemSquirrel
[@jc2k]: https://github.com/Jc2k
[@jefflirion]: https://github.com/JeffLIrion
[@kjonline]: https://github.com/KJonline
[@kane610]: https://github.com/Kane610
[@killerrat]: https://github.com/KiLLeRRaT
[@martinhjelmare]: https://github.com/MartinHjelmare
[@matthewflamm]: https://github.com/MatthewFlamm
[@michsior14]: https://github.com/Michsior14
[@snoof85]: https://github.com/SNoof85
[@sneaksnacksnake]: https://github.com/SneakSnackSnake
[@sukramj]: https://github.com/SukramJ
[@swamp-ig]: https://github.com/Swamp-Ig
[@vividboarder]: https://github.com/ViViDboarder
[@abmantis]: https://github.com/abmantis
[@amelchio]: https://github.com/amelchio
[@amigan]: https://github.com/amigan
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bbrendon]: https://github.com/bbrendon
[@boralyl]: https://github.com/boralyl
[@bramkragten]: https://github.com/bramkragten
[@bryanyork]: https://github.com/bryanyork
[@chriscla]: https://github.com/chriscla
[@colohan]: https://github.com/colohan
[@david81]: https://github.com/david81
[@definitio]: https://github.com/definitio
[@dmulcahey]: https://github.com/dmulcahey
[@doudz]: https://github.com/doudz
[@dshokouhi]: https://github.com/dshokouhi
[@eifinger]: https://github.com/eifinger
[@emontnemery]: https://github.com/emontnemery
[@engrbm87]: https://github.com/engrbm87
[@exxamalte]: https://github.com/exxamalte
[@fabaff]: https://github.com/fabaff
[@farmio]: https://github.com/farmio
[@flowolf]: https://github.com/flowolf
[@flz]: https://github.com/flz
[@foxel]: https://github.com/foxel
[@fredericvl]: https://github.com/fredericvl
[@fredrike]: https://github.com/fredrike
[@frenck]: https://github.com/frenck
[@ggravlingen]: https://github.com/ggravlingen
[@gibman]: https://github.com/gibman
[@grillp]: https://github.com/grillp
[@jaburges]: https://github.com/jaburges
[@jesserizzo]: https://github.com/jesserizzo
[@jjlawren]: https://github.com/jjlawren
[@joe248]: https://github.com/joe248
[@johnluetke]: https://github.com/johnluetke
[@konikvranik]: https://github.com/konikvranik
[@larssont]: https://github.com/larssont
[@majuss]: https://github.com/majuss
[@marthoc]: https://github.com/marthoc
[@michaeldavie]: https://github.com/michaeldavie
[@mvn23]: https://github.com/mvn23
[@neffs]: https://github.com/neffs
[@oandrew]: https://github.com/oandrew
[@ochlocracy]: https://github.com/ochlocracy
[@petewill]: https://github.com/petewill
[@pgilad]: https://github.com/pgilad
[@piitaya]: https://github.com/piitaya
[@poofyteddy]: https://github.com/poofyteddy
[@psicot]: https://github.com/psicot
[@pvizeli]: https://github.com/pvizeli
[@ratsept]: https://github.com/ratsept
[@rishatik92]: https://github.com/rishatik92
[@roblandry]: https://github.com/roblandry
[@robmarkcole]: https://github.com/robmarkcole
[@rolfberkenbosch]: https://github.com/rolfberkenbosch
[@sanyatuning]: https://github.com/sanyatuning
[@sashao]: https://github.com/sashao
[@scheric]: https://github.com/scheric
[@scop]: https://github.com/scop
[@sebasje]: https://github.com/sebasje
[@shutupflanders]: https://github.com/shutupflanders
[@skgsergio]: https://github.com/skgsergio
[@snowzach]: https://github.com/snowzach
[@squishykid]: https://github.com/squishykid
[@thecynic]: https://github.com/thecynic
[@timmccor]: https://github.com/timmccor
[@tleegaard]: https://github.com/tleegaard
[@tribut]: https://github.com/tribut
[@tsvi]: https://github.com/tsvi
[@vangorra]: https://github.com/vangorra
[@zewelor]: https://github.com/zewelor
[@zhumuht]: https://github.com/zhumuht
[@zxdavb]: https://github.com/zxdavb
[alexa docs]: /integrations/alexa/
[amazon_polly docs]: /integrations/amazon_polly/
[androidtv docs]: /integrations/androidtv/
[automation docs]: /integrations/automation/
[binary_sensor docs]: /integrations/binary_sensor/
[bluetooth_le_tracker docs]: /integrations/bluetooth_le_tracker/
[bluetooth_tracker docs]: /integrations/bluetooth_tracker/
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
[cert_expiry docs]: /integrations/cert_expiry/
[cloud docs]: /integrations/cloud/
[config docs]: /integrations/config/
[cover docs]: /integrations/cover/
[darksky docs]: /integrations/darksky/
[deconz docs]: /integrations/deconz/
[device_automation docs]: /integrations/device_automation/
[doods docs]: /integrations/doods/
[ebusd docs]: /integrations/ebusd/
[ecobee docs]: /integrations/ecobee/
[egardia docs]: /integrations/egardia/
[elv docs]: /integrations/elv/
[enphase_envoy docs]: /integrations/enphase_envoy/
[environment_canada docs]: /integrations/environment_canada/
[esphome docs]: /integrations/esphome/
[evohome docs]: /integrations/evohome/
[fedex docs]: /integrations/fedex/
[frontend docs]: /integrations/frontend/
[generic docs]: /integrations/generic/
[geniushub docs]: /integrations/geniushub/
[geonetnz_quakes docs]: /integrations/geonetnz_quakes/
[glances docs]: /integrations/glances/
[google_assistant docs]: /integrations/google_assistant/
[group docs]: /integrations/group/
[here_travel_time docs]: /integrations/here_travel_time/
[hive docs]: /integrations/hive/
[homekit docs]: /integrations/homekit/
[homekit_controller docs]: /integrations/homekit_controller/
[homematicip_cloud docs]: /integrations/homematicip_cloud/
[http docs]: /integrations/http/
[hue docs]: /integrations/hue/
[iaqualink docs]: /integrations/iaqualink/
[image_processing docs]: /integrations/image_processing/
[incomfort docs]: /integrations/incomfort/
[influxdb docs]: /integrations/influxdb/
[iperf3 docs]: /integrations/iperf3/
[izone docs]: /integrations/izone/
[kaiterra docs]: /integrations/kaiterra/
[keenetic_ndms2 docs]: /integrations/keenetic_ndms2/
[knx docs]: /integrations/knx/
[lcn docs]: /integrations/lcn/
[lifx docs]: /integrations/lifx/
[lifx_cloud docs]: /integrations/lifx_cloud/
[lifx_legacy docs]: /integrations/lifx_legacy/
[light docs]: /integrations/light/
[linksys_ap docs]: /integrations/linksys_ap/
[linky docs]: /integrations/linky/
[luci docs]: /integrations/luci/
[media_extractor docs]: /integrations/media_extractor/
[media_player docs]: /integrations/media_player/
[meteoalarm docs]: /integrations/meteoalarm/
[yandex_transport docs]: /integrations/yandex_transport/
[mqtt docs]: /integrations/mqtt/
[mysensors docs]: /integrations/mysensors/
[nest docs]: /integrations/nest/
[netgear_lte docs]: /integrations/netgear_lte/
[nextbus docs]: /integrations/nextbus/
[nws docs]: /integrations/nws/
[nzbget docs]: /integrations/nzbget/
[obihai docs]: /integrations/obihai/
[ombi docs]: /integrations/ombi/
[onvif docs]: /integrations/onvif/
[opentherm_gw docs]: /integrations/opentherm_gw/
[openuv docs]: /integrations/openuv/
[otp docs]: /integrations/otp/
[owlet docs]: /integrations/owlet/
[persistent_notification docs]: /integrations/persistent_notification/
[pi_hole docs]: /integrations/pi_hole/
[plex docs]: /integrations/plex/
[proxy docs]: /integrations/proxy/
[rainbird docs]: /integrations/rainbird/
[remote_rpi_gpio docs]: /integrations/remote_rpi_gpio/
[rest_command docs]: /integrations/rest_command/
[saj docs]: /integrations/saj/
[sendgrid docs]: /integrations/sendgrid/
[sensor docs]: /integrations/sensor/
[shodan docs]: /integrations/shodan/
[simplisafe docs]: /integrations/simplisafe/
[solaredge_local docs]: /integrations/solaredge_local/
[solax docs]: /integrations/solax/
[soma docs]: /integrations/soma/
[sonos docs]: /integrations/sonos/
[spaceapi docs]: /integrations/spaceapi/
[srp_energy docs]: /integrations/srp_energy/
[sun docs]: /integrations/sun/
[switch docs]: /integrations/switch/
[sytadin docs]: /integrations/sytadin/
[tahoma docs]: /integrations/tahoma/
[template docs]: /integrations/template/
[tensorflow docs]: /integrations/tensorflow/
[tfiac docs]: /integrations/tfiac/
[tibber docs]: /integrations/tibber/
[todoist docs]: /integrations/todoist/
[torque docs]: /integrations/torque/
[tradfri docs]: /integrations/tradfri/
[transmission docs]: /integrations/transmission/
[unifi docs]: /integrations/unifi/
[upc_connect docs]: /integrations/upc_connect/
[ups docs]: /integrations/ups/
[usps docs]: /integrations/usps/
[velux docs]: /integrations/velux/
[venstar docs]: /integrations/venstar/
[vera docs]: /integrations/vera/
[vivotek docs]: /integrations/vivotek/
[volumio docs]: /integrations/volumio/
[watson_tts docs]: /integrations/watson_tts/
[websocket_api docs]: /integrations/websocket_api/
[wemo docs]: /integrations/wemo/
[whois docs]: /integrations/whois/
[withings docs]: /integrations/withings/
[wwlln docs]: /integrations/wwlln/
[xbox_live docs]: /integrations/xbox_live/
[xiaomi_aqara docs]: /integrations/xiaomi_aqara/
[yandex_transport docs]: /integrations/yandex_transport/
[yessssms docs]: /integrations/yessssms/
[zha docs]: /integrations/zha/
[zone docs]: /integrations/zone/
[zwave docs]: /integrations/zwave/

3
source/_redirects
View File

@ -2057,3 +2057,6 @@
/components/zone /integrations/zone
/components/zoneminder /integrations/zoneminder
/components/zwave /integrations/zwave
# Breaking changes
/integrations/switch.pca /integrations/elv

2
source/cookbook/index.markdown
View File

@ -14,7 +14,7 @@ For [`python_script:` examples](/integrations/python_script/) visit the [Scripts
[sec-automation]: /integrations/#automation
[organization]: /integrations/#organization
New recipes can be added via the [home-assistant.io repository](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_cookbook).
New recipes can be added via the [home-assistant.io repository](https://github.com/home-assistant/home-assistant.io/tree/current/source/_cookbook).
<div class='note'>

2
source/getting-started/configuration.markdown
View File

@ -31,7 +31,7 @@ Now let's make a small change using the configurator: we are going to change the
- Find the `homeassistant:` configuration block, which should be the first thing in `configuration.yaml`. In this block, update `name`, `latitude`, `longitude`, `unit_system` and `time_zone` to match yours.
- Click the save icon in the top right to commit changes.
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a config check. Do this by clicking on Configuration in the sidebar, click on General and click on the "Check Config" button. When it's valid, it will show the text "Configuration valid!".
- Now Restart Home Assistant using the "restart" in the Server management section on the same page.
- Now Restart Home Assistant using the "restart" in the Server management section on the same page. In order for "Check Config" to be visible, you must enable "Advanced Mode" on your user profile.
<p class='img'>
<img src='/images/screenshots/configuration-validation.png' />

BIN
source/images/blog/2019-10-0.100/action-trigger.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.2 KiB

BIN
source/images/blog/2019-10-0.100/components.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
source/images/blog/2019-10-0.100/condition-and.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.2 KiB

BIN
source/images/blog/2019-10-0.100/device-trigger-sensor.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.0 KiB

BIN
source/images/blog/2019-10-0.100/hacktoberfest.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 9.6 KiB

BIN
source/images/blog/2019-10-0.100/plex.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 173 KiB

BIN
source/images/blog/2019-10-0.100/yaml.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.2 KiB

2
source/lovelace/index.markdown
View File

@ -24,7 +24,7 @@ To try it yourself, check out [the demo](https://demo.home-assistant.io).
## Discuss Lovelace
- Suggestions are welcome in the [ui-schema repository](https://github.com/home-assistant/ui-schema)
- Suggestions are welcome in the [home-assistant-polymer repository](https://github.com/home-assistant/home-assistant-polymer/)
- For help with Lovelace, join the #lovelace channel on [our chat](/join-chat/) or [our forums](https://community.home-assistant.io/c/projects/frontend)
## Additional Lovelace Resources