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-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'rc' into current

Browse Source
This commit is contained in:
Paulus Schoutsen 2019-03-20 11:53:40 -07:00
commit fc641dd944
58 changed files with 1943 additions and 604 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_config.yml
View File

@ -138,9 +138,9 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 89
current_patch_version: 2
date_released: 2019-03-12
current_minor_version: 90
current_patch_version: 0
date_released: 2019-03-20
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

5
source/_components/alarm_control_panel.mqtt.markdown
View File

@ -85,6 +85,11 @@ code:
description: If defined, specifies a code to enable or disable the alarm in the frontend.
required: false
type: string
code_arm_required:
description: If true the code is required to arm the alarm.
required: false
type: boolean
default: true
availability_topic:
description: The MQTT topic subscribed to receive availability (online/offline) updates.
required: false

226
source/_components/androidtv.markdown Normal file
View File

@ -0,0 +1,226 @@
---
layout: page
title: "Android TV"
description: "Instructions on how to integrate Android TV and Fire TV devices into Home Assistant."
date: 2015-10-23 18:00
sidebar: true
comments: false
sharing: true
footer: true
logo: androidtv.png
ha_category: Media Player
ha_release: 0.7.6
ha_iot_class: Local Polling
redirect_from:
- /components/media_player.firetv/
---
The `androidtv` platform allows you to control an Android TV device or [Amazon Fire TV](https://www.amazon.com/b/?node=8521791011) device.
## {% linkable_title Device preparation %}
To set up your device, you will need to find its IP address and enable ADB debugging. For Android TV devices, please consult the documentation for your device.
For Fire TV devices, the instructions are as follows:
- Turn on ADB Debugging on your Amazon Fire TV:
- From the main (Launcher) screen, select Settings.
- Select System > Developer Options.
- Select ADB Debugging.
- Find Amazon Fire TV device IP address:
- From the main (Launcher) screen, select Settings.
- Select System > About > Network.
## {% linkable_title Configuration %}
```yaml
# Example configuration.yaml entry
media_player:
# Use the Python ADB implementation without authentication
- platform: androidtv
name: Android TV 1
host: 192.168.0.111
# Use the Python ADB implementation with authentication
- platform: androidtv
name: Android TV 2
host: 192.168.0.222
adbkey: "/config/android/adbkey"
# Use an ADB server for sending ADB commands
- platform: androidtv
name: Android TV 3
host: 192.168.0.123
adb_server_ip: 127.0.0.1
```
{% configuration %}
host:
description: The IP address for your Android TV / Fire TV device.
required: true
type: string
name:
description: The friendly name of the device.
required: false
default: Android TV
type: string
port:
description: The port for your Android TV / Fire TV device.
required: false
default: 5555
type: integer
adbkey:
description: The path to your `adbkey` file. Note that the file `adbkey.pub` must be in the same directory.
required: false
type: string
adb_server_ip:
description: The IP address of the ADB server.
required: false
type: string
adb_server_port:
description: The port for the ADB server.
required: false
default: 5037
type: port
get_sources:
description: Whether or not to retrieve the running apps as the list of sources for Fire TV devices; not used for Android TV devices.
required: false
default: true
type: boolean
apps:
description: A dictionary where the keys are app IDs and the values are app names that will be displayed in the UI; see example below.
required: false
default: {}
type: dict
device_class:
description: "The type of device: `auto` (detect whether it is an Android TV or Fire TV device), `androidtv`, or `firetv`."
required: false
default: auto
type: string
{% endconfiguration %}
### {% linkable_title Full Configuration %}
```yaml
# Example configuration.yaml entry
media_player:
# Use an ADB server to setup an Android TV device
# and provide an app name
- platform: androidtv
name: Android TV
device_class: androidtv
host: 192.168.0.222
adb_server_ip: 127.0.0.1
apps:
com.amazon.tv.launcher: "Fire TV"
# Use the Python ADB implementation with authentication
# to setup a Fire TV device and don't get the running apps
- platform: androidtv
name: Fire TV
device_class: firetv
host: 192.168.0.222
adbkey: "/config/android/adbkey"
get_sources: false
```
## {% linkable_title ADB Setup %}
This component works by sending ADB commands to your Android TV / Fire TV device. There are two ways to accomplish this:
### {% linkable_title 1. ADB Server %}
You can use an ADB server to connect to your Android TV and Fire TV devices.
For Hass.io users, you can install the [Android Debug Bridge](https://github.com/hassio-addons/addon-adb/blob/master/README.md) addon. Using this approach, Home Assistant will send the ADB commands to the server, which will then send them to the Android TV / Fire TV device and report back to Home Assistant. To use this option, add the `adb_server_ip` option to your configuration. If you are running the server on the same machine as Home Assistant, you can use `127.0.0.1` for this value.
### {% linkable_title 2. Python ADB Implementation %}
The second option is to connect to your device using the `adb` Python package.
If your device requires ADB authentication, you will need to follow the instructions in the [ADB Authentication](#adb-authentication) section below. Once you have an authenticated key, this approach does not require any additional setup or addons. However, users with newer devices may find that the ADB connection is unstable. For a Fire TV device, you can try setting the `get_sources` configuration option to `false`. If the problem cannot be resolved, you should use the ADB server option.
### {% linkable_title ADB Authentication %}
If you get a "Device authentication required, no keys available" error when trying to set up your Android TV or Fire TV, then you'll need to create an adbkey and add its path to your configuration. Follow the instructions on this page to connect to your device from your computer: [Connecting to Fire TV Through adb](https://developer.amazon.com/zh/docs/fire-tv/connecting-adb-to-device.html).
<p class='note warning'>
In the dialog appearing on your Android TV / Fire TV, you must check the box that says "always allow connections from this device." ADB authentication in Home Assistant will only work using a trusted key.
</p>
Once you've successfully connected to your Android TV / Fire TV via the command `adb connect <ipaddress>`, the files `adbkey` and `adbkey.pub` will be created on your computer. The default locations for these files are (from [https://developer.android.com/studio/command-line/adb](https://developer.android.com/studio/command-line/adb)):
- Linux and Mac: `$HOME/.android.`
- Windows: `%userprofile%\.android.`
Copy the `adbkey` and `adbkey.pub` files to your Home Assistant folder and add the path to the `adbkey` file to your configuration.
#### {% linkable_title ADB Troubleshooting %}
If you receive the error message `Issue: Error while setting up platform androidtv` in your log when trying to set up an Android TV or Fire TV device with an ADB key, then there is probably an issue with your ADB key. Here are some possible causes.
1. ADB is not enabled on your device.
2. Your key is not pre-authenticated. Before using the `adbkey` in Home Assistant, you _**must**_ connect to your device using the ADB binary and tell it to always allow connections from this computer. For more information, see the section [ADB Authentication](#adb-authentication) above.
3. Home Assistant does not have the appropriate permissions for the `adbkey` file and so it is not able to use it. Once you fix the permissions, the component should work.
4. You are already connected to the Android TV / Fire TV via ADB from another device. Only one device can be connected, so disconnect the other device, restart the Android TV / Fire TV (for good measure), and then restart Home Assistant.
## {% linkable_title Services %}
### {% linkable_title `media_player.select_source` %}
For Fire TV devices, you can launch an app using the `media_player.select_source` command. Simply provide the app ID as the `source`. You can also stop an app by prefixing the app ID with a `!`. For example, you could define [scripts](/docs/scripts) to start and stop Netflix as follows:
```yaml
start_netflix:
sequence:
- service: media_player.select_source
data:
entity_id: media_player.fire_tv_living_room
source: 'com.netflix.ninja'
stop_netflix:
sequence:
- service: media_player.select_source
data:
entity_id: media_player.fire_tv_living_room
source: '!com.netflix.ninja'
```
### {% linkable_title `androidtv.adb_command` %}
The service `androidtv.adb_command` allows you to send either keys or ADB shell commands to your Android TV / Fire TV device.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Name(s) of Android TV / Fire TV entities.
| `command` | no | Either a key command or an ADB shell command.
In an [action](/getting-started/automation-action/) of your [automation setup](/getting-started/automation/) it could look like this:
```yaml
action:
service: androidtv.adb_command
data:
entity_id: media_player.androidtv_tv_living_room
command: "HOME"
```
Available key commands include:
- `POWER`
- `SLEEP`
- `HOME`
- `UP`
- `DOWN`
- `LEFT`
- `RIGHT`
- `CENTER`
- `BACK`
- `MENU`
The full list of key commands can be found [here](https://github.com/JeffLIrion/python-androidtv/blob/e1c07176efc9216cdcff8245c920224c0234ea56/androidtv/constants.py#L115-L155).
You can also use the command `GET_PROPERTIES` to retrieve the properties used by Home Assistant to update the device's state. These will be logged at the INFO level and can be used to help improve state detection in the backend [androidtv](https://github.com/JeffLIrion/python-androidtv) package.

25
source/_components/binary_sensor.workday.markdown
View File

@ -30,7 +30,6 @@ To enable the `workday` sensor in your installation, add the following to your `
binary_sensor:
- platform: workday
country: DE
workdays: [mon, wed, fri]
```
{% configuration %}
@ -63,11 +62,14 @@ days_offset:
required: false
type: integer
default: 0
add_holidays:
description: "Add custom holidays (such as company, personal holidays or vacations). Needs to formatted as `YYYY-MM-DD`."
required: false
type: list
{% endconfiguration %}
Days are specified as follows: `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun`.
The keyword `holiday` is used for public
holidays identified by the holidays module.
The keyword `holiday` is used for public holidays identified by the holidays module.
<p class='note warning'>
If you use the sensor for Norway (`NO`) you need to wrap `NO` in quotes or write the name in full.
@ -76,6 +78,22 @@ If you use the sensor for Canada (`CA`) with Ontario (`ON`) as `province:` then
Otherwise the value is evaluated as `true` (check the YAML documentation for further details) and the sensor will not work.
</p>
## {% linkable_title Full example %}
This examples excludes Saturdays, Sundays and holiday. Two custom holidays are added.
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: workday
country: DE
workdays: [mon, wed, fri]
excludes: [sat, sun, holiday]
add_holidays:
- '2018-12-26'
- '2018-12-31'
```
## {% linkable_title Automation example %}
Example usage for automation:
@ -98,4 +116,3 @@ automation:
<p class='note'>
Please remember that [as explained here](/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.
</p>

4
source/_components/blink.markdown
View File

@ -23,8 +23,6 @@ redirect_from:
- /components/sensor.blink/
---
<p class='note warning'>Blink has started blocking Home Assistant users. More info in <a href="https://community.home-assistant.io/t/blink-block-account/98718">the forums</a>.</p>
The `blink` component lets you view camera images and motion events from [Blink](http://blinkforhome.com) camera and security systems.
## {% linkable_title Setup %}
@ -109,6 +107,8 @@ blink:
## {% linkable_title Services %}
Any sequential calls to services relating to blink should have a minimum of a 5 second delay in between them to prevent the calls fro being throttled and ignored.
### {% linkable_title `blink.blink_update` %}
Force a refresh of the Blink system.

22
source/_components/camera.markdown
View File

@ -16,7 +16,7 @@ The camera component allows you to use IP cameras with Home Assistant. With a li
Once loaded, the `camera` platform will expose services that can be called to perform various actions.
Available services: `turn_on`, `turn_off`, `enable_motion_detection`, `disable_motion_detection`, and `snapshot`.
Available services: `turn_on`, `turn_off`, `enable_motion_detection`, `disable_motion_detection`, `snapshot`, and `play_stream`.
#### {% linkable_title Service `turn_on` %}
@ -73,6 +73,26 @@ action:
```
{% endraw %}
#### {% linkable_title Service `play_stream` %}
Play a live stream from a camera to selected media player(s). Requires `stream` component to be set up.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Name of entity to fetch stream from, e.g., `camera.living_room_camera`. |
| `media_player` | no | Name of media player to play stream on, e.g., `media_player.living_room_tv`. |
| `format` | yes | Stream format supported by `stream` component and selected `media_player`. Default: `hls` |
For example, the following action in an automation would send an `hls` live stream to your chromecast.
```yaml
action:
service: camera.play_stream
data:
entity_id: camera.yourcamera
media_player: media_player.chromecast
```
### {% linkable_title Test if it works %}
A simple way to test if you have set up your `camera` platform correctly, is to use <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services** from the **Developer Tools**. Choose your service from the dropdown menu **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**.

53
source/_components/cisco_mobility_express.markdown Normal file
View File

@ -0,0 +1,53 @@
---
layout: page
title: "Cisco Mobility Express"
description: "Instructions on how to integrate Cisco Mobility Express wireless controllers into Home Assistant."
date: 2019-02-27 11:59
sidebar: true
comments: false
sharing: true
footer: true
logo: cisco.png
ha_category: Presence Detection
ha_release: "0.90"
---
This is a presence detection scanner for [Cisco](https://www.cisco.com) Mobility Express wireless controllers.
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
device_tracker:
- platform: cisco_mobility_express
host: CONTROLLER_IP_ADDRESS
username: YOUR_ADMIN_USERNAME
password: YOUR_ADMIN_PASSWORD
```
{% configuration %}
host:
description: The IP address of your controller, e.g., 192.168.10.150.
required: true
type: string
username:
description: The username of a user with administrative privileges.
required: true
type: string
password:
description: The password for your given admin account.
required: true
type: string
ssl:
description: Use HTTPS instead of HTTP to connect.
required: false
type: boolean
default: false
verify_ssl:
description: Enable or disable SSL certificate verification. Set to false if you have a self-signed SSL certificate and haven't installed the CA certificate to enable verification.
required: false
default: true
type: boolean
{% endconfiguration %}
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

30
source/_components/climate.knx.markdown
View File

@ -27,7 +27,7 @@ climate:
temperature_address: '5/1/1'
setpoint_shift_address: '5/1/2'
setpoint_shift_state_address: '5/1/3'
target_temperature_address: '5/1/4'
target_temperature_state_address: '5/1/4'
operation_mode_address: '5/1/5'
```
@ -41,16 +41,32 @@ climate:
temperature_address: '5/1/1'
setpoint_shift_address: '5/1/2'
setpoint_shift_state_address: '5/1/3'
target_temperature_address: '5/1/4'
target_temperature_state_address: '5/1/4'
operation_mode_frost_protection_address: '5/1/5'
operation_mode_night_address: '5/1/6'
operation_mode_comfort_address: '5/1/7'
```
`operation_mode_frost_protection_address` / `operation_mode_night_address` / `operation_mode_comfort_address` are not necessary if `operation_mode_address` is specified.
If your device doesn't support setpoint_shift calculations (i.e. if you don't provide a `setpoint_shift_address` value) please set the `min_temp` and `max_temp`
attributes of the climate device to avoid issues with increasing the temperature in the frontend.
attributes of the climate device to avoid issues with increasing the temperature in the frontend. Please do also make sure to add the `target_temperature_address`
to the config in this case.:
```yaml
# Example configuration.yaml entry
climate:
- platform: knx
name: HASS-Kitchen.Temperature
temperature_address: '5/1/2'
target_temperature_address: '5/1/4'
target_temperature_state_address: '5/1/1'
operation_mode_frost_protection_address: '5/1/5'
operation_mode_night_address: '5/1/6'
operation_mode_comfort_address: '5/1/7'
min_temp: 7.0
max_temp: 32.0
```
`operation_mode_frost_protection_address` / `operation_mode_night_address` / `operation_mode_comfort_address` are not necessary if `operation_mode_address` is specified.
The following values are valid for the `operation_modes` attribute:
@ -72,6 +88,10 @@ temperature_address:
required: true
type: string
target_temperature_address:
description: KNX group address for setting target temperature.
required: false
type: string
target_temperature_state_address:
description: KNX group address for reading current target temperature from KNX bus.
required: true
type: string

35
source/_components/climate.netatmo.markdown
View File

@ -18,7 +18,7 @@ The `netatmo` thermostat platform is consuming the information provided by a [Ne
To enable the Netatmo thermostat, you first have to set up [netatmo](/components/netatmo/), this will use discovery to add your thermostat.
If you want to select a specific thermostat, set discovery to False for [netatmo](/components/netatmo/) and add the following lines to your `configuration.yaml`:
If you want to select specific homes or specific rooms, set discovery to False for [netatmo](/components/netatmo/) and add the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
@ -27,26 +27,35 @@ climate:
```
{% configuration %}
relay:
description: Will display the thermostats of this relay only.
required: false
type: string
thermostat:
description: Thermostat to use.
homes:
description: Will display the thermostats of the homes listed.
required: false
type: list
keys:
thermostat_name:
description: Name of the thermostat to display.
name:
required: true
description: The home name.
rooms:
description: Rooms to be displayed. Multiple entities allowed.
required: false
type: [list, string]
description: List of the names of the rooms to be displayed.
{% endconfiguration %}
If **relay** and **thermostat** are not provided, all thermostats will be displayed.
If **homes** and **rooms** are not provided, all thermostats will be displayed.
```yaml
# Example configuration.yaml entry
climate:
platform: netatmo
relay: relay_name
thermostat:
- thermostat_name
homes:
- name: home1_name
rooms:
- room1_name
- room2_name
- name: home2_name
rooms:
- room3_name
- room4_name
- room5_name
```

52
source/_components/cppm.markdown Normal file
View File

@ -0,0 +1,52 @@
---
layout: page
title: "Aruba ClearPass"
description: "Instructions on how to integrate Aruba ClearPass into Home Assistant."
date: 2019-03-05 10:45
sidebar: true
comments: false
sharing: true
footer: true
logo: aruba.png
ha_category: Presence Detection
ha_release: "0.90"
ha_iot_class: Local Polling
---
This platform allows you to detect presence by looking at connected devices to [Aruba Clearpass](https://www.arubanetworks.com/products/security/network-access-control/).
Supported platforms (tested):
- Aruba ClearPass 6.7.5
<p class='note warning'>
You must first creat an API client from here: https://clearpass.server.com/guest/api_clients.php
</p>
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
device_tracker:
- platform: cppm_tracker
host: clearpass.server.org
client_id: clearpassapi
api_key: 00000004qyO513hTdCfjIO2ZWWnmex8QZ5000000000
```
{% configuration %}
host:
description: "The IP address or hostname of the ClearPass server, e.g., `clearpass.server.com`."
required: true
type: string
client_id:
description: "The client ID from here: `https://clearpass.server.com/guest/api_clients.php`"
required: true
type: string
api_key:
description: "Secret from here: `https://clearpass.server.com/guest/api_clients.php`"
required: true
type: string
{% endconfiguration %}
See the [device tracker component page](/components/device_tracker/) for instructions on how to configure the people to be tracked.

5
source/_components/device_tracker.quantum_gateway.markdown
View File

@ -38,6 +38,11 @@ password:
description: The password for the `admin` user. The default password may be printed on the gateway itself.
required: true
type: string
ssl:
description: Use HTTPS when connecting to gateway. New firmware may require HTTPS while older may require this to be False.
required: false
type: boolean
default: True
{% endconfiguration %}
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

39
source/_components/device_tracker.xfinity.markdown Normal file
View File

@ -0,0 +1,39 @@
---
layout: page
title: "Xfinity Gateway"
description: "Instructions on how to integrate Xfinity Gateways into Home Assistant."
date: 2019-02-12 19:44
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Presence Detection
logo: xfinity.svg
ha_release: 0.90
ha_iot_class: "Local Polling"
---
The `xfinity` device tracker platform offers presence detection by looking at connected devices to an Xfinity gateway.
It was tested with an Xfinity Gateway model TG1682G.
## {% linkable_title Configuration %}
To use an Xfinity Gateway in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
device_tracker:
- platform: xfinity
```
{% configuration %}
host:
description: The IP address of your router, e.g., `192.168.1.1`.
required: false
type: string
default: 10.0.0.1
{% endconfiguration %}
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

2
source/_components/discovery.markdown
View File

@ -23,6 +23,7 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
* [Denon network receivers](/components/media_player.denonavr/)
* [DirecTV receivers](/components/media_player.directv/)
* [DLNA DMR enabled devices](/components/media_player.dlna_dmr/)
* [Enigma2 media player](/components/media_player.enigma2/)
* [Frontier Silicon internet radios](/components/media_player.frontier_silicon/)
* [Google Cast](/components/media_player.cast/)
* [HomeKit](/components/homekit_controller/)
@ -80,6 +81,7 @@ Valid values for ignore are:
* `bose_soundtouch`: Bose Soundtouch speakers
* `denonavr`: Denon network receivers
* `directv`: DirecTV receivers
* `enigma2`: Enigma2 media players
* `frontier_silicon`: Frontier Silicon internet radios
* `google_cast`: Google Cast
* `harmony`: Logitech Harmony Hub

69
source/_components/enigma2.markdown Normal file
View File

@ -0,0 +1,69 @@
---
layout: page
title: "Enigma2 (OpenWebif)"
description: "Instructions on how to integrate an Enigma2 based box running OpenWebif into Home Assistant."
date: 2019-02-21 12:02
sidebar: true
comments: false
sharing: true
footer: true
logo: openwebif.png
ha_category: Media Player
featured: false
ha_release: "0.90"
ha_iot_class: "Local Polling"
redirect_from:
- /components/media_player.enigma2/
---
The `enigma2` platform allows you to control a Linux based set-top box which is running [Enigma2](https://github.com/oe-alliance/oe-alliance-enigma2) with the OpenWebif plugin installed.
[OpenWebif](https://github.com/E2OpenPlugins/e2openplugin-OpenWebif) is an open source web interface for Enigma2 based set-top boxes.
Enigma2 devices should be discovered automatically by using the [the discovery component](/components/discovery/).
To manually add a set-top box to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
media_player:
- platform: enigma2
host: IP_ADDRESS
```
{% configuration %}
host:
description: The IP/hostname of the Enigma2 set-top box on your home network.
required: true
type: string
use_channel_icon:
description: By default, a screen grab of the current channel is shown. If you prefer the channel icon to be shown instead, set this to true.
required: false
type: boolean
default: false
port:
description: Port which OpenWebif is listening on.
required: false
type: integer
default: 80
username:
description: The username of a user with privileges to access the box. This is only required if you have enabled the setting "Enable HTTP Authentication" in OpenWebif settings. _(e.g., on the remote by pressing `Menu`>`Plugins`>`OpenWebif`)_.
required: false
type: string
default: root
password:
description: The password for your given account. Again, this is only required if you have enabled the setting "Enable HTTP Authentication" in OpenWebif settings. _(e.g., on the remote by pressing `Menu`>`Plugins`>`OpenWebif`)_.
required: false
type: string
default: dreambox
ssl:
description: Use HTTPS instead of HTTP to connect. This is only required if you have enabled the setting "Enable HTTPS" in OpenWebif settings. _(e.g., on the remote by pressing `Menu`>`Plugins`>`OpenWebif`)_. You will need to ensure you have a valid CA certificate in place or SSL verification will fail with this component.
required: false
type: boolean
default: false
name:
description: A name for easy identification of the device.
required: false
type: string
default: Enigma2 Media Player
{% endconfiguration %}

4
source/_components/google_assistant.markdown
View File

@ -206,6 +206,10 @@ https://developers.google.com/actions/reference/smarthome/traits/modes
"Hey Google, change input source to TV on Living Room Receiver"
### {% linkable_title Room/Area support %}
Entities that have not got rooms explicitly set and that have been placed in Home Assistant areas will return room hints to Google with the devices in those areas.
### {% linkable_title Climate Operation Modes %}
There is not an exact 1-1 match between Home Assistant and Google Assistant for the available operation modes.

18
source/_components/harmony.markdown
View File

@ -67,6 +67,11 @@ delay_secs:
description: Default duration in seconds between sending commands to a device.
required: false
type: float
default: 0.4
hold_secs:
description: Default duration in seconds between sending the "press" command and sending the "release" command.
required: false
default: 0
{% endconfiguration %}
### {% linkable_title Configuration file %}
@ -77,7 +82,7 @@ Upon startup one file will be written to your Home Assistant configuration direc
- List of all programmed device names and ID numbers
- List of all available commands per programmed device
This file will be overwritten whenever the Harmony HUB has a new configuration, there is no need to restart HASS.
This file will be overwritten whenever the Harmony HUB has a new configuration, there is no need to restart Home Assistant.
### {% linkable_title Service `remote.turn_off` %}
@ -85,7 +90,7 @@ Turn off all devices that were switched on from the start of the current activit
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Only act on a specific remote, else target all.
| `entity_id` | no | Entity ID to target.
### {% linkable_title Service `remote.turn_on` %}
@ -93,7 +98,7 @@ Start an activity. Will start the default `activity` from configuration.yaml if
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Only act on a specific remote, else target all.
| `entity_id` | no | Entity ID to target.
| `activity` | yes | Activity ID or Activity Name to start.
##### {% linkable_title Example %}
@ -127,7 +132,7 @@ Send a single command or a set of commands to one device, device ID and availabl
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Only act on a specific remote, else target all.
| `entity_id` | no | Entity ID to target.
| `device` | no | Device ID or Device Name to send the command to.
| `command` | no | A single command or a list of commands to send.
| `num_repeats` | yes | The number of times to repeat the command(s).
@ -159,7 +164,6 @@ In the file 'harmony_REMOTENAME.conf' you can find the available devices and com
}
```
A typical service call for sending several button presses looks like this:
```yaml
@ -190,7 +194,7 @@ Sends the change channel command to the Harmony HUB
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Only act on a specific remote, else target all.
| `entity_id` | no | Entity ID to target.
| `channel` | no | Channel number to change to
A typical service call for changing the channel would be::
@ -208,7 +212,7 @@ Force synchronization between the Harmony device and the Harmony cloud.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Only act on a specific remote, else target all.
| `entity_id` | no | Entity ID to target.
### {% linkable_title Examples %}

3
source/_components/homekit_controller.markdown
View File

@ -17,6 +17,7 @@ ha_category:
- Lock
- Switch
- Binary Sensor
- Sensor
ha_release: 0.68
ha_iot_class: Local Polling
redirect_from:
@ -26,6 +27,7 @@ redirect_from:
- /components/light.homekit_controller/
- /components/lock.homekit_controller/
- /components/switch.homekit_controller/
- /components/sensor.homekit_controller/
---
[HomeKit](https://developer.apple.com/homekit/) controller integration for Home Assistant allows you to connect HomeKit accessories to Home Assistant. This component should not be confused with the [HomeKit](/components/homekit/) component, which allows you to control Home Assistant devices via HomeKit.
@ -39,6 +41,7 @@ There is currently support for the following device types within Home Assistant:
- Lock (HomeKit lock)
- Switch (HomeKit switches)
- Binary Sensor (HomeKit motion sensors)
- Sensor (HomeKit humidity, temperature, and light level sensors)
The component will be automatically configured if the [`discovery:`](/components/discovery/) component is enabled and an enable entry added for HomeKit:

18
source/_components/homematicip_cloud.markdown
View File

@ -40,6 +40,7 @@ There is currently support for the following device types within Home Assistant:
* Light
* Sensor
* Switch
* Weather
## {% linkable_title Setup the component via the frontend %}
@ -97,29 +98,44 @@ authtoken:
* Water detector (*HmIP-SWD*)
* homematicip_cloud.climate
* Radiator thermostat (*HmIP-eTRV,-2*) - should also work with (*HmIP-eTRV-2-UK, -B, -B1, -C*)
* Climate group (*HmIP-HeatingGroup*)
* This includes temperature/humidity measures for climate devices of a room delivered by:
* Wall-mounted thermostat (*HmIP-WTH, -2*)
* Brand Wall-mounted thermostat (*HmIP-BWTH, -24*)
* Radiator thermostat (*HmIP-eTRV, -2, -C*)
* Temperature and humidity sensor (*HmIP-STH*)
* Temperature and humidity Sensor with display (*HmIP-STHD*)
* homematicip_cloud.light
* Switch actuator and meter for brand switches (*HmIP-BSM*)
* Dimming actuator for brand switches (*HmIP-BDT*)
* Dimming actuator flush-mount (*HmIP-FDT*)
* Switch Actuator and Meter – flush-mount (*HmIP-FSM*)
* Switch Actuator for brand switches – with signal lamp (*HmIP-BSL*)
* homematicip_cloud.sensor
* Accesspoint duty-cycle (*HmIP-HAP, -B1*)
* Wall-mounted thermostat (*HmIP-WTH, -2*)
* Brand Wall-mounted thermostat (*HmIP-BWTH, -24*)
* Radiator thermostat (valve position only) (*HmIP-eTRV,-2*, -C) - should also work with (*HmIP-eTRV-2-UK, -B, -B1*)
* Temperature and humidity sensor (*HmIP-STH*)
* Temperature and humidity Sensor with display (*HmIP-STHD*)
* Outdoor temperature and humidity sensor (*HmIP-STHO, -A*)
* Illuminance sensor (*HmIP-SMI*)
* Light Sensor outdoor (*HmIP-SLO*)
* homematicip_cloud.switch
* Pluggable Switch (*HmIP-PS*)
* Pluggable Switch and Meter (*HmIP-PSM*) - should also work with (*HmIP-PSM-CH, -IT, -UK, -PE*)
* Switch actuator with open collector output (*HmIP-MOD-OC8*)
* homematicip_cloud.shutter
* Blind actuator for brand switches (*HmIP-BBL*)
* Shutter actuator brand-mount (*HmIP-BROLL*)
* Shutter actuator flush-mount (*HmIP-FROLL*)
* homematicip_cloud.weather
* Weather Sensor – basic (*HmIP-SWO-B*)
* Weather Sensor – plus (*HmIP-SWO-PL*)
* Weather Sensor – pro (*HmIP-SWO-PR*)

8
source/_components/http.markdown
View File

@ -27,7 +27,7 @@ http:
{% configuration %}
api_password:
description: Deprecated. Do not use. Protect the Home Assistant API with a password - this password can also be used to log in to the frontend. Use [long lasting access token](/docs/authentication/#your-account-profile) instead, as [shown in the REST API](https://developers.home-assistant.io/docs/en/external_api_rest.html) and [websocket API](https://developers.home-assistant.io/docs/en/external_api_websocket.html) documentation.
description: "**Deprecated since 0.90 release. Configuration moved to [Legacy API password auth provider](/docs/authentication/providers/#legacy-api-password).** Protect the Home Assistant API with a password - this password can also be used to log in to the frontend. Where your client or other software supports it, you should use [long lasting access token](/docs/authentication/#your-account-profile) instead, as [shown in the REST API](https://developers.home-assistant.io/docs/en/external_api_rest.html) and [websocket API](https://developers.home-assistant.io/docs/en/external_api_websocket.html) documentation."
required: false
type: string
server_host:
@ -71,7 +71,7 @@ trusted_proxies:
required: false
type: string, list
trusted_networks:
description: "List of trusted networks, consisting of IP addresses or networks, that are allowed to bypass password protection when accessing Home Assistant. If using a reverse proxy with the `use_x_forwarded_for` and `trusted_proxies` options enabled, requests proxied to Home Assistant with a trusted `X-Forwarded-For` header will appear to come from the IP given in that header instead of the proxy IP."
description: "**Deprecated since 0.89 release. Configuration moved to [Trusted Networks auth provider](/docs/authentication/providers/#trusted-networks).** List of trusted networks, consisting of IP addresses or networks, that are allowed to bypass password protection when accessing Home Assistant. If using a reverse proxy with the `use_x_forwarded_for` and `trusted_proxies` options enabled, requests proxied to Home Assistant with a trusted `X-Forwarded-For` header will appear to come from the IP given in that header instead of the proxy IP."
required: false
type: string, list
ip_ban_enabled:
@ -100,7 +100,6 @@ The sample below shows a configuration entry with possible values:
```yaml
# Example configuration.yaml entry
http:
api_password: YOUR_PASSWORD
server_port: 12345
ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem
ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem
@ -111,9 +110,6 @@ http:
trusted_proxies:
- 127.0.0.1
- ::1
trusted_networks:
- 192.168.0.0/24
- fd00::/8
ip_ban_enabled: true
login_attempts_threshold: 5
```

24
source/_components/ifttt.markdown
View File

@ -71,6 +71,19 @@ Once you have added your key to your `configuration.yaml` file, restart your Hom
After restarting the server, be sure to watch the console for any logging errors that show up in red, white or yellow.
</p>
### {% linkable_title Multiple IFTTT keys %}
If you have multiple IFTTT users you can specify multiple IFTTT keys with:
```yaml
# Example configuration.yaml entry
ifttt:
key:
YOUR_KEY_NAME1: YOUR_API_KEY1
YOUR_KEY_NAME2: YOUR_API_KEY2
```
### {% linkable_title Testing your trigger %}
You can use the **Developer tools** to test your [Webhooks](https://ifttt.com/maker_webhooks) trigger. To do this, open the Home Assistant frontend, open the sidebar, click on the first icon in the developer tools. This should get you to the **Call Service** screen. Fill in the following values:
@ -86,6 +99,17 @@ Service Data | `{"event": "EventName", "value1": "Hello World"}`
When your screen looks like this, click the 'call service' button.
</p>
By default the trigger is sent to all the api keys from `configuration.yaml`. If you
want to send the trigger to a specific key use the `target` field:
Field | Value
----- | -----
domain | `ifttt`
service | `trigger`
Service Data | `{"event": "EventName", "value1": "Hello World", "target": "YOUR_KEY_NAME1"}`
The `target` field can contain a single key name or a list of key names.
### {% linkable_title Setting up a recipe %}
Press the *New applet* button and search for *Webhooks*.

5
source/_components/knx.markdown
View File

@ -52,6 +52,11 @@ config_file:
description: The path for XKNX configuration file.
required: false
type: string
rate_limit:
description: Defines the maximum number of telegrams to be sent to the bus per second (range 1-100).
required: false
default: 20
type: integer
{% endconfiguration %}
If the auto detection of the KNX/IP device does not work you can specify ip/port of the tunneling device:

48
source/_components/konnected.markdown
View File

@ -12,6 +12,7 @@ ha_category:
- Alarm
- Binary Sensor
- Switch
- Sensor
ha_release: "0.70"
redirect_from:
- /components/binary_sensor.konnected/
@ -26,8 +27,13 @@ The component currently supports the following device types in Home Assistant:
- Binary Sensor: Wired door and window sensors, motion detectors, glass-break detectors, leak sensors, smoke & CO detectors or any open/close switch.
- Switch: Actuate a siren, strobe, buzzer or relay module.
- Sensor: Periodic measurements from DHT temperature/humidity sensors and DS18B20 temperature sensors.
This component requires the [`discovery`](/components/discovery) component to be enabled.
This component uses the [`discovery`](/components/discovery) component, which must be enabled for device discovery to work. If you don't want to use discovery, set the _host_ and _port_ for each device in the description.
<p class='note info'>
Konnected devices communicate with Home Assistant over your local LAN -- there is no cloud component! For best performance we recommend allowing unsecured HTTP API traffic between Konnected devices and Home Assistant on your LAN. This means that you should not use the `http` component to serve SSL/TLS certificates. Instead, use a proxy like Nginx or Caddy to serve SSL/TLS. [Read more.](https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy)
</p>
### {% linkable_title Configuration %}
@ -77,7 +83,7 @@ devices:
type: list
keys:
pin:
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are 1, 2, 5, 6, 7 and 9.
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are `1`, `2`, `5`, `6`, `7` and `9`.
required: exclusive
zone:
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values are `1`, `2`, `3`, `4`, `5` and `6`.
@ -94,6 +100,29 @@ devices:
description: Inverts the open/closed meaning of a binary sensor circuit. Commonly needed for normally open wired smoke alarm circuits.
required: false
default: false
sensors:
description: A list of digital sensors (currently supports DHT and DS18B20 sensors) connected to the device
required: false
type: list
keys:
pin:
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values for sensors are `1`, `2`, `5`, `6`, `7` and `9`.
required: exclusive
zone:
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values for sensors are `1`, `2`, `3`, `4`, `5` and `6`.
required: exclusive
name:
description: The name of the device used in the front end.
required: false
default: automatically generated
type:
description: The type of sensor. Valid values are `dht` or `ds18b20`
required: true
poll_interval:
type: integer
description: The frequency (in minutes) that the Konnected device will report sensor data. Minimum `1` minute. _Note:_ this is only implemented for `dht` sensors.
required: false
default: not set (device default is 3 minutes)
switches:
description: A list of actuators (on/off switches) connected to the device. See [Konnected Switch](/components/switch.konnected/) for configuration variables.
required: false
@ -184,17 +213,22 @@ konnected:
binary_sensors:
- pin: 1
type: motion
name: 'Office Motion'
name: Office Motion
- pin: 2
type: door
name: 'Office Door'
name: Office Door
switches:
- pin: 5
name: 'Garage Door'
name: Garage Door
activation: low
momentary: 500
- pin: 8
name: LED Light
sensors:
- pin: 6
name: Kitchen
type: dht
```
### {% linkable_title Pin Mapping %}
@ -213,6 +247,10 @@ Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly use
### {% linkable_title Revision History %}
#### 0.89
- Added support for `dht` and `ds18b20` temperature sensors
#### 0.80
- Added ability to specify `host` and `port` to set up devices without relying on discovery.

8
source/_components/light.ihc.markdown
View File

@ -57,6 +57,14 @@ light:
description: The IHC resource id.
required: true
type: integer
on_id:
description: Optional IHC resource id that will be pulsed to turn ON this light.
required: false
type: integer
off_id:
description: Optional IHC resource id that will be pulsed to turn OFF this light.
required: false
type: integer
name:
description: The name of the component
required: false

7
source/_components/light.markdown
View File

@ -77,11 +77,8 @@ Turns one or multiple lights off.
### {% linkable_title Service `light.toggle` %}
Toggles the state of one or multiple lights using [groups]({{site_root}}/components/group/).
Toggles the state of one or multiple lights using [groups]({{site_root}}/components/group/).
Takes the same arguments as [`turn_on`](#service-lightturn_on) service.
*Note*: If `light.toggle` is used for a group of lights, it will toggle the individual state of each light.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all.
| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds.

18
source/_components/light.nanoleaf_aurora.markdown → source/_components/light.nanoleaf.markdown
View File

@ -1,13 +1,13 @@
---
layout: page
title: "Nanoleaf Aurora Light Panel"
description: "Instructions how to integrate Nanoleaf Aurora Light Panels into Home Assistant."
title: "Nanoleaf Light Panel"
description: "Instructions how to integrate Nanoleaf Light Panels into Home Assistant."
date: 2018-01-04 20:00
sidebar: true
comments: false
sharing: true
footer: true
logo: nanoleaf_aurora_light.png
logo: nanoleaf_light.png
ha_category: Light
ha_iot_class: Local Polling
ha_release: 0.67
@ -15,16 +15,16 @@ ha_release: 0.67
### {% linkable_title Configuration Sample %}
The `nanoleaf_aurora` platform allows you to control [Nanoleaf Aurora Light Panels](https://nanoleaf.me) from Home Assistant.
The `nanoleaf` platform allows you to control [Nanoleaf Light Panels](https://nanoleaf.me) from Home Assistant.
The preferred way to set up this platform is by enabling the [discovery component](/components/discovery/). Make sure to press and hold the *ON* button for 5 seconds (the LED will start flashing) on your Nanoleaf Aurora Panel while Home Assistant is starting.
The preferred way to set up this platform is by enabling the [discovery component](/components/discovery/). Make sure to press and hold the *ON* button for 5 seconds (the LED will start flashing) on your Nanoleaf Lights while Home Assistant is starting.
To configure the Aurora lights manually, add the following lines to your `configuration.yaml` file:
To configure the Nanoleaf lights manually, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
light:
- platform: nanoleaf_aurora
- platform: nanoleaf
host: 192.168.1.10
token: xxxxxxxxxxxxxxxxxxxxx
```
@ -42,12 +42,12 @@ name:
description: Name of the component, make this unique if you have multiple Light Panels
required: false
type: string
default: Aurora
default: Nanoleaf
{% endconfiguration %}
### {% linkable_title Getting The Auth Token %}
1. Make sure that your Nanoleaf Aurora Panel is fully patched (as of the time of writing the latest version was 2.2.0)
1. Make sure that your Nanoleaf Light Panel is fully patched (as of the time of writing the latest version was 3.0.8 for Aurora and 1.2.0 for Canvas)
2. Hold down the *ON* button on the Panel for 5 seconds; the LED will start flashing
3. Issue a *POST* request to the API endpoint, e.g., via `$ curl -i -X POST http://192.168.1.155:16021/api/v1/new`
4. The output should include the auth token like *{"auth_token":"xxxxxxxxxxxxxxxxxxxxx"}*, copy the resulting token into your configuration

61
source/_components/light.tplink.markdown
View File

@ -1,61 +0,0 @@
---
layout: page
title: "TP-Link Bulb"
description: "Instructions on how to integrate TP-Link bulbs into Home Assistant."
date: 2017-07-25 08:00
sidebar: true
comments: false
sharing: true
footer: true
logo: tp-link.png
ha_category: Light
ha_iot_class: Local Polling
ha_release: "0.50"
---
The `tplink` light platform allows you to control the state of your [TP-Link smart bulb](http://www.tp-link.com/en/products/list-5609.html).
Supported units:
- LB100
- LB110
- LB120
- LB130
- LB230
- KL110
- KL120
- KL130
To use your TP-Link light in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
light:
- platform: tplink
host: IP_ADDRESS
```
{% configuration %}
name:
description: The name to use when displaying this bulb.
required: false
type: string
default: TP-Link Light
host:
description: "The IP address of your TP-Link bulb, e.g., `192.168.1.32`."
required: true
type: string
{% endconfiguration %}
## {% linkable_title Adding multiple lights %}
You may need to add [multiple lights](https://community.home-assistant.io/t/multiple-tp-link-switches/6935) and the config would need to include multiple lights separately.
```yaml
# Example configuration.yaml entry
light:
- platform: tplink
host: FIRST_IP_ADDRESS
- platform: tplink
host: SECOND_IP_ADDRESS
```

4
source/_components/media_player.dlna_dmr.markdown
View File

@ -46,4 +46,8 @@ name:
description: The name you would like to give to the device, e.g., `TV living room`.
required: false
type: string
callback_url_override:
description: Override the advertised callback URL. In case the home assistant instance is not directly reachable (e.g., running in a docker container without bridged-networking), advertise this callback URL for events.
required: false
type: string
{% endconfiguration %}

119
source/_components/media_player.firetv.markdown
View File

@ -1,119 +0,0 @@
---
layout: page
title: "FireTV"
description: "Instructions on how to integrate Fire-TV into Home Assistant."
date: 2015-10-23 18:00
sidebar: true
comments: false
sharing: true
footer: true
logo: firetv.png
ha_category: Media Player
ha_release: 0.7.6
ha_iot_class: Local Polling
---
The `firetv` platform allows you to control an [Amazon Fire TV/stick](https://www.amazon.com/b/?node=8521791011).
Steps to configure your Amazon Fire TV stick with Home Assistant:
- Turn on ADB Debugging on your Amazon Fire TV:
- From the main (Launcher) screen, select Settings.
- Select System > Developer Options.
- Select ADB Debugging.
- Find Amazon Fire TV device IP:
- From the main (Launcher) screen, select Settings.
- Select System > About > Network.
To add FireTV to your installation, Note your device name, and add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
media_player:
# a device that does not require ADB authentication
- platform: firetv
name: Fire TV 1
host: 192.168.0.111
# a device that does require ADB authentication
- platform: firetv
name: Fire TV 2
host: 192.168.0.222
adbkey: "/config/android/adbkey"
# use an ADB server for sending ADB commands instead of the Python ADB implementation
- platform: firetv
name: Fire TV 3
host: 192.168.0.123
adb_server_ip: 127.0.0.1
```
{% configuration %}
host:
description: The IP address for your Fire TV device.
required: true
type: string
name:
description: The friendly name of the device.
required: false
default: Amazon Fire TV
type: string
port:
description: The port for your Fire TV device.
required: false
default: 5555
type: integer
adbkey:
description: The path to your `adbkey` file. Note that the file `adbkey.pub` must be in the same directory.
required: false
type: string
adb_server_ip:
description: The IP address of the ADB server.
required: false
type: string
adb_server_port:
description: The port for the ADB server.
required: false
default: 5037
type: port
get_sources:
description: Whether or not to retrieve the running apps as the list of sources.
required: false
default: true
type: boolean
{% endconfiguration %}
## {% linkable_title ADB Setup %}
This component works by sending ADB commands to your Fire TV device. There are two ways to accomplish this:
1. Using the `adb` Python package. If your device requires ADB authentication, you will need to follow the instructions in the "ADB Authentication (for Fire TV devices with recent software)" section below. Once you have an authenticated key, this approach does not require any additional setup or addons. However, users with newer devices may find that the ADB connection is unstable. If setting the `get_sources` configuration option to `false` does not help, they should use the next option.
2. Using an ADB server. For Hass.io users, you can install the [Android Debug Bridge](https://github.com/hassio-addons/addon-adb/blob/v0.1.0/README.md) addon. With this approach, Home Assistant will send the ADB commands to the server, which will then send them to the Fire TV device and report back to Home Assistant. To use this option, add the `adb_server_ip` option to your configuration. If you are running the server on the same machine as Home Assistant, you can use `127.0.0.1` for this value.
### {% linkable_title ADB Authentication (for Fire TV devices with recent software) %}
If you get a "Device authentication required, no keys available" error when trying to set up Fire TV, then you'll need to create an adbkey and add its path to your configuration. Follow the instructions on this page to connect to your Fire TV from your computer: [Connecting to Fire TV Through adb](https://developer.amazon.com/zh/docs/fire-tv/connecting-adb-to-device.html).
<p class='note warning'>
In the dialog appearing on your Fire TV, you must check the box that says "always allow connections from this device." ADB authentication in Home Assistant will only work using a trusted key.
</p>
Once you've successfully connected to your Fire TV via the command `adb connect <ipaddress>`, the files `adbkey` and `adbkey.pub` will be created on your computer. The default locations for these files are (from [https://developer.android.com/studio/command-line/adb](https://developer.android.com/studio/command-line/adb)):
* Linux and Mac: `$HOME/.android.`
* Windows: `%userprofile%\.android.`
Copy the `adbkey` and `adbkey.pub` files to your Home Assistant folder and add the path to the `adbkey` file to your configuration.
#### ADB Troubleshooting
If you receive the error message `Issue: Error while setting up platform firetv` in your log when trying to set up a Fire TV device with an ADB key, then there is probably an issue with your ADB key. Here are some possible causes.
1. ADB is not enabled on your Fire TV. To remedy this, enable ADB by following the instructions above.
2. Your key is not pre-authenticated. Before using the `adbkey` in Home Assistant, you _**must**_ connect to your Fire TV device using the ADB binary and tell the Fire TV to always allow connections from this computer. For more information, see the section "ADB Authentication (for Fire TV devices with recent software)" above.
3. Home Assistant does not have the appropriate permissions for the `adbkey` file and so it is not able to use it. Once you fix the permissions, the component should work.
4. You are already connected to the Fire TV via ADB from another device. Only one device can be connected, so disconnect the other device, restart the Fire TV (for good measure), and then restart Home Assistant.

2
source/_components/modbus.markdown
View File

@ -149,7 +149,7 @@ modbus:
| hub | Hub name (defaults to 'default' when omitted) |
| unit | Slave address (set to 255 you talk to Modbus via TCP) |
| address | Address of the Register (e.g., 138) |
| value | An array of 16-bit values. Might need reverse ordering. E.g., to set 0x0004 you might need to set `[4,0]` |
| value | A single value or an array of 16-bit values. Single value will call modbus function code 6. Array will call modbus function code 16. Array might need reverse ordering. E.g., to set 0x0004 you might need to set `[4,0]` |
## {% linkable_title Building on top of Modbus %}

17
source/_components/ness_alarm.markdown
View File

@ -59,6 +59,11 @@ port:
description: The port on which the IP232 module listens for clients.
required: true
type: integer
scan_interval:
description: "Time interval between updates. Supported formats: `scan_interval: 'HH:MM:SS'`, `scan_interval: 'HH:MM'` and Time period dictionary (see example below)."
required: false
default: '00:01:00'
type: time
zones:
description: List of zones to add
required: false
@ -79,6 +84,18 @@ zones:
type: string
{% endconfiguration %}
#### {% linkable_title Time period dictionary example %}
```yaml
scan_interval:
# At least one of these must be specified:
days: 0
hours: 0
minutes: 0
seconds: 10
milliseconds: 0
```
## {% linkable_title Services %}
### {% linkable_title Service `aux` %}

2
source/_components/notify.mastodon.markdown
View File

@ -12,7 +12,7 @@ ha_category: Notifications
ha_release: 0.67
---
The `mastodon` platform uses [MAstodon](https://joinmastodon.org/) to delivery notifications from Home Assistant.
The `mastodon` platform uses [Mastodon](https://joinmastodon.org/) to delivery notifications from Home Assistant.
Go to **Preferences** in the Mastodon web interface, then to **Development** and create a new application.

4
source/_components/notify.sendgrid.markdown
View File

@ -46,6 +46,10 @@ sender:
description: The e-mail address of the sender.
required: true
type: string
sender_name:
description: The name of the sender. Defaults to "Home Assistant" if not set.
required: false
type: string
recipient:
description: The recipient of the notification.
required: true

16
source/_components/onboarding.markdown Normal file
View File

@ -0,0 +1,16 @@
---
layout: page
title: "Onboarding"
description: "This component is responsible for providing the onboarding endpoints."
date: 2018-03-19 21:04
sidebar: true
comments: false
sharing: true
footer: true
logo: home-assistant.png
ha_category: Other
ha_release: 0.73
ha_qa_scale: internal
---
This component creates the endpoints for the onboarding that is built into Home Assistant. There are no configuration options for this component directly.

4
source/_components/ps4.markdown
View File

@ -16,7 +16,7 @@ ha_iot_class: Local Polling
The `ps4` component allows you to control a
[Sony PlayStation 4 console](https://www.playstation.com/en-us/explore/ps4/).
- This component supports controlling a single PlayStation 4 for your instance. Additional consoles may be supported in a future release.
- This component supports controlling multiple PlayStation 4 consoles for your Home Assistant instance. Additional consoles can be added by running the configuration for the PS4 Integration again.
## {% linkable_title Requirements %}
@ -53,7 +53,7 @@ There are varying methods to perform this, dependent on your OS that is running
If your Home Assistant device is running <b>Hass.io</b> on <b>HassOS</b>, it does not require additional configuration.
</p>
- Example for Debian:
- Example for Debian-based and most UNIX operating systems:
`sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.5`
Replace "/usr/bin/python3.5" with your path to Python that is running Home Assistant.

46
source/_components/rainmachine.markdown
View File

@ -113,6 +113,48 @@ switches:
## {% linkable_title Services %}
### {% linkable_title `rainmachine.disable_program` %}
Disable a RainMachine program. This will mark the program switch as
`Unavailable` in the UI.
| Service Data Attribute | Optional | Description |
|---------------------------|----------|-------------------------|
| `program_id` | no | The program to disable |
### {% linkable_title `rainmachine.disable_zone` %}
Disable a RainMachine zone. This will mark the zone switch as
`Unavailable` in the UI.
| Service Data Attribute | Optional | Description |
|---------------------------|----------|-------------------------|
| `zone_id` | no | The zone to disable |
### {% linkable_title `rainmachine.enable_program` %}
Enable a RainMachine program.
| Service Data Attribute | Optional | Description |
|---------------------------|----------|-------------------------|
| `program_id` | no | The program to enable |
### {% linkable_title `rainmachine.enable_zone` %}
Enable a RainMachine zone.
| Service Data Attribute | Optional | Description |
|---------------------------|----------|-------------------------|
| `zone_id` | no | The zone to enable |
### {% linkable_title `rainmachine.pause_watering` %}
Pause all watering activities for a number of seconds.
| Service Data Attribute | Optional | Description |
|---------------------------|----------|--------------------------------|
| `seconds` | no | The number of seconds to pause |
### {% linkable_title `rainmachine.start_program` %}
Start a RainMachine program.
@ -150,6 +192,10 @@ Stop a RainMachine zone.
|---------------------------|----------|----------------------|
| `zone_id` | no | The zone to stop |
### {% linkable_title `rainmachine.unpause_watering` %}
Unpause all watering activities.
## {% linkable_title Switch %}
The `rainmachine` switch platform allows you to control programs and zones within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).

2
source/_components/sensor.google_travel_time.markdown
View File

@ -97,7 +97,7 @@ options:
## {% linkable_title Dynamic Configuration %}
Tracking can be setup to track entities of type `device_tracker`, `zone` and `sensor`. If an entity is placed in the origin or destination then every 5 minutes when the platform updates it will use the latest location of that entity.
Tracking can be setup to track entities of type `device_tracker`, `zone`, `sensor` and `person`. If an entity is placed in the origin or destination then every 5 minutes when the platform updates it will use the latest location of that entity.
```yaml
# Example entry for configuration.yaml

5
source/_components/sensor.netdata.markdown
View File

@ -96,4 +96,9 @@ resources:
required: false
type: icon
default: "mdi:desktop-classic"
invert:
description: Invert the sensor values.
required: false
type: boolean
default: false
{% endconfiguration %}

48
source/_components/sensor.systemmonitor.markdown
View File

@ -47,29 +47,31 @@ resources:
The table contains types and their argument to use in your `configuration.yaml`
file.
| Type (`type:`) | Argument (`arg:`) |
| :------------------ |:--------------------------|
| disk_use_percent | Path, e.g., `/` |
| disk_use | Path, e.g., `/` |
| disk_free | Path, e.g., `/` |
| memory_use_percent | |
| memory_use | |
| memory_free | |
| swap_use_percent | |
| swap_use | |
| swap_free | |
| load_1m | |
| load_5m | |
| load_15m | |
| network_in | Interface, e.g., `eth0` |
| network_out | Interface, e.g., `eth0` |
| packets_in | Interface, e.g., `eth0` |
| packets_out | Interface, e.g., `eth0` |
| ipv4_address | Interface, e.g., `eth0` |
| ipv6_address | Interface, e.g., `eth0` |
| processor_use | |
| process | Binary, e.g., `octave-cli` |
| last_boot | |
| Type (`type:`) | Argument (`arg:`) |
| :--------------------- |:--------------------------|
| disk_use_percent | Path, e.g., `/` |
| disk_use | Path, e.g., `/` |
| disk_free | Path, e.g., `/` |
| memory_use_percent | |
| memory_use | |
| memory_free | |
| swap_use_percent | |
| swap_use | |
| swap_free | |
| load_1m | |
| load_5m | |
| load_15m | |
| network_in | Interface, e.g., `eth0` |
| network_out | Interface, e.g., `eth0` |
| throughput_network_in | Interface, e.g., `eth0` |
| throughput_network_out | Interface, e.g., `eth0` |
| packets_in | Interface, e.g., `eth0` |
| packets_out | Interface, e.g., `eth0` |
| ipv4_address | Interface, e.g., `eth0` |
| ipv6_address | Interface, e.g., `eth0` |
| processor_use | |
| process | Binary, e.g., `octave-cli` |
| last_boot | |
## {% linkable_title Linux specific %}

35
source/_components/smartthings.markdown
View File

@ -58,6 +58,17 @@ See it in action, with a step-by-step setup guide, thanks to a fan! (v0.87 featu
## {% linkable_title Basic requirements %}
The SmartThings integration utilizes a webhook to receive push updates from the SmartThings cloud through either a cloudhook or an internet accessible webhook based on whether Home Assistant Cloud is configured and logged in with a non-expired subscription (this is not configurable at this time).
### {% linkable_title Cloudhook via Nabu Casa %}
If you are using Home Assistant Cloud (Nabu Casa) the integraiton will create a cloudhook automatically. This greatly simplifies the basic requirements and does not require Home Assistant to be exposed to the internet. **If you have previously setup the component prior to meeting the requirements for a cloudhook or prior to v0.90.0, you must remove all prior integrations and run through the configuration again.**
1. A [personal access token](https://account.smartthings.com/tokens) tied to a Samsung or SmartThings account (see below for instructions).
2. Home Assistant Cloud is configured and logged-in with a non-expired subscription.
### {% linkable_title Webhook %}
1. A [personal access token](https://account.smartthings.com/tokens) tied to a Samsung or SmartThings account (see below for instructions).
2. Home Assistant setup for [remote access](/docs/configuration/remote/) via a domain name secured with SSL. *Self-signed SSL certificates are not supported by the SmartThings Cloud API.*
3. [`base_url` of the http component](/components/http#base_url) set the URL that Home Assistant is available on the internet.
@ -158,7 +169,26 @@ The SmartThings Binary Sensor platform lets you view devices that have binary se
### {% linkable_title Climate %}
The SmartThings Climate platform lets you control devices that have thermostat-related capabilities. For a SmartThings device to be represented by the climate platform, it must have all the capabilities from either "set a" _or_ "set b":
The SmartThings Climate platform lets you control devices that have air conditioner or thermostat related capabilities.
#### {% linkable_title Air Conditioners %}
For a SmartThings Air Conditioner to be represented by the climate platform, it must have all of the following required capabilities:
| Capability |Climate Features
|-------------------------------------|--------------------------------------------|
| [`airConditionerMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Air-Conditioner-Mode) (required) | `operation mode`
| [`fanSpeed`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Fan-Speed) (required) | `fan mode`
| [`switch`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Switch) (required) | `on/off`
| [`temperatureMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Temperature-Measurement) (required) | `temperature`
| [`thermostatCoolingSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Cooling-Setpoint) (required) | `target temp`
| [`demandResponseLoadControl`](https://docs.smartthings.com/en/latest/capabilities-reference.html#demand-response-load-control) | `drlc_status_duration` (state attribute), `drlc_status_level` (state attribute), `drlc_status_override` (state attribute), `drlc_status_start` (state attribute)
| [`powerConsumptionReport`](https://docs.smartthings.com/en/latest/capabilities-reference.html#power-consumption-report) | `power_consumption_end` (state attribute), `power_consumption_energy` (state attribute), `power_consumption_power` (state attribute), `power_consumption_start` (state attribute)
#### {% linkable_title Thermostats %}
For a SmartThings thermostat to be represented by the climate platform, it must have all the capabilities from either "set a" _or_ "set b":
| Capability |Climate Features
|-------------------------------------|--------------------------------------------|
@ -256,6 +286,7 @@ The SmartThings Sensor platform lets your view devices that have sensor-related
| [`thermostatMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Mode) | `thermostatMode`
| [`thermostatOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Operating-State) | `thermostatOperatingState`
| [`thermostatSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Setpoint) | `thermostatSetpoint`
| [`threeAxis`](https://docs.smartthings.com/en/latest/capabilities-reference.html#three-axis) | `threeAxis` (as discrete sensors `X`, `Y` and `Z`)
| [`tvChannel`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Tv-Channel) | `tvChannel`
| [`tvocMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Tvoc-Measurement) | `tvocLevel`
| [`ultravioletIndex`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Ultraviolet-Index) | `ultravioletIndex`
@ -280,7 +311,7 @@ The SmartThings Switch platform lets you control devices that have the [`switch`
### {% linkable_title Setup %}
Perform the following steps if you receive one of the following error messages while attempting to setup the integration:
Perform the following steps if you receive one of the following error messages while attempting to setup the integration (this does not apply when integrated through Home Assistant Cloud):
- "SmartThings could not validate the endpoint configured in base_url. Please review the component requirements."
- "Unable to setup the SmartApp. Please try again."

43
source/_components/stream.markdown Normal file
View File

@ -0,0 +1,43 @@
---
layout: page
title: "Stream"
description: "Instructions on how to integrate live streams within Home Assistant."
date: 2019-02-06 13:40
sidebar: true
comments: false
sharing: true
footer: true
logo: home-assistant.png
ha_category:
- Other
ha_release: "0.90"
ha_iot_class: Local Push
ha_qa_scale: internal
---
The `stream` component provides a way to proxy live streams through Home Assistant. The component currently only supports the HLS format.
## {% linkable_title Configuration %}
To enable this component, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
stream:
```
## {% linkable_title Troubleshooting %}
Some users on manual installs may see the following error in their logs after restarting:
```
2019-03-12 08:49:59 ERROR (SyncWorker_5) [homeassistant.util.package] Unable to install package av==6.1.2: Command "/home/pi/home-assistant/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-udfl2b3t/av/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-ftn5zmh2/install-record.txt --single-version-externally-managed --compile --install-headers /home/pi/home-assistant/include/site/python3.6/av" failed with error code 1 in /tmp/pip-install-udfl2b3t/av/
2019-03-12 08:49:59 ERROR (MainThread) [homeassistant.requirements] Not initializing stream because could not install requirement av==6.1.2
2019-03-12 08:49:59 ERROR (MainThread) [homeassistant.setup] Setup failed for stream: Could not install all requirements.
```
If you see this error you can solve it by running the following commands and restarting Home Assistant (commands do not need to be ran as the `homeassistant` user):
```
sudo apt-get install -y python-dev pkg-config libavformat-dev libavcodec-dev libavdevice-dev libavutil-dev libswscale-dev libavresample-dev libavfilter-dev
```

8
source/_components/switch.ihc.markdown
View File

@ -50,6 +50,14 @@ switch:
description: The IHC resource id.
required: true
type: integer
on_id:
description: Optional IHC resource id that will be pulsed to turn ON this switch.
required: false
type: integer
off_id:
description: Optional IHC resource id that will be pulsed to turn OFF this switch.
required: false
type: integer
name:
description: The name of the component
required: false

96
source/_components/switch.tplink.markdown
View File

@ -1,96 +0,0 @@
---
layout: page
title: "TP-Link Switch"
description: "Instructions on how to integrate TP-Link switches into Home Assistant."
date: 2016-07-13 08:00
sidebar: true
comments: false
sharing: true
footer: true
logo: tp-link.png
ha_category: Switch
ha_iot_class: Local Polling
ha_release: 0.24
---
The `tplink` switch platform allows you to control the state of your [TP-Link smart switch](http://www.tp-link.com/en/products/list-5258.html).
Supported units:
- HS100
- HS103
- HS105
- HS110
- HS200
## {% linkable_title Configuration %}
To use your TP-Link switch or socket in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
switch:
- platform: tplink
host: IP_ADDRESS
```
{% configuration %}
name:
description: The name to use when displaying this switch.
required: false
type: string
default: TP-Link Switch
host:
description: "The IP address of your TP-Link switch, e.g., `192.168.1.32`."
required: true
type: string
enable_leds:
description: If the LEDs on the switch (WiFi and power) should be lit.
required: false
type: boolean
{% endconfiguration %}
## {% linkable_title Adding multiple switches %}
You may need to add [multiple switches](https://community.home-assistant.io/t/multiple-tp-link-switches/6935) and the config would need to include multiple switches separately.
```yaml
# Example configuration.yaml entry
switch:
- platform: tplink
host: FIRST_IP_ADDRESS
- platform: tplink
host: SECOND_IP_ADDRESS
```
## {% linkable_title Configure Energy Sensors %}
In order to get the power consumption readings from the HS110, you'll have to create a [template sensor](/components/switch.template/). In the example below, change all of the `my_tp_switch`'s to match your switch's entity ID.
{% raw %}
```yaml
sensor:
- platform: template
sensors:
my_tp_switch_amps:
friendly_name_template: "{{ states.switch.my_tp_switch.name}} Current"
value_template: '{{ states.switch.my_tp_switch.attributes["current_a"] | float }}'
unit_of_measurement: 'A'
my_tp_switch_watts:
friendly_name_template: "{{ states.switch.my_tp_switch.name}} Current Consumption"
value_template: '{{ states.switch.my_tp_switch.attributes["current_power_w"] | float }}'
unit_of_measurement: 'W'
my_tp_switch_total_kwh:
friendly_name_template: "{{ states.switch.my_tp_switch.name}} Total Consumption"
value_template: '{{ states.switch.my_tp_switch.attributes["total_energy_kwh"] | float }}'
unit_of_measurement: 'kWh'
my_tp_switch_volts:
friendly_name_template: "{{ states.switch.my_tp_switch.name}} Voltage"
value_template: '{{ states.switch.my_tp_switch.attributes["voltage"] | float }}'
unit_of_measurement: 'V'
my_tp_switch_today_kwh:
friendly_name_template: "{{ states.switch.my_tp_switch.name}} Today's Consumption"
value_template: '{{ states.switch.my_tp_switch.attributes["today_energy_kwh"] | float }}'
unit_of_measurement: 'kWh'
```
{% endraw %}

10
source/_components/switch.vesync.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "VeSync Switch"
description: "Instructions on how to set up Etekcity VeSync switches within Home Assistant."
description: "Instructions on how to set up Etekcity VeSync switches and outlets within Home Assistant."
date: 2018-03-09 02:11
sidebar: true
comments: false
@ -12,9 +12,11 @@ ha_category: Switch
ha_release: 0.66
---
The `vesync` switch platform enables integration with Etekcity VeSync smart switches.
The `vesync` switch platform enables integration with Etekcity VeSync smart wall switches and outlets.
VeSync switches are low-cost wifi smart plugs that offer energy monitoring and work with popular voice assistants.
VeSync outlets are low-cost wifi smart plugs that offer energy monitoring and work with popular voice assistants.
Supports both the 7A round outlets and 15A rectangular outlets, as well as the in wall switches.
## {% linkable_title Configuration %}
@ -41,7 +43,7 @@ password:
## {% linkable_title Exposed Attributes %}
VeSync switches will expose the following details.
VeSync switches will expose the following details for only the smart outlets. Energy monitoring not available for in-wall switches.
| Attribute | Description | Example |
| ------------------- | ------------------------------------------------------------------- | --------------- |

21
source/_components/tellstick.markdown
View File

@ -108,10 +108,19 @@ sensor:
required: false
type: string
only_named:
description: Only show the named sensors. Set to `true` to hide sensors.
description: Only add and include specified sensors. If this is not specified all sensors will be imported and the names will be based on each sensor's ID number.
required: false
default: false
type: boolean
type: list
keys:
id:
description: The ID-number of the sensor to include.
required: true
type: integer
name:
description: Specify the name of the selected sensor.
required: true
type: string
temperature_scale:
description: The scale of the temperature value.
required: false
@ -134,11 +143,13 @@ In this section you find some real-life examples of how to use this sensor.
# Example configuration.yaml entry
sensor:
- platform: tellstick
135: Outside
21: Inside
only_named: true
temperature_scale: "°C"
datatype_mask: 1
only_named:
- id: 135
name: Outside
- id: 21
name: Inside
```
## {% linkable_title Switch %}

119
source/_components/tof.markdown Normal file
View File

@ -0,0 +1,119 @@
---
layout: page
title: "Time of Flight sensor using VL53L1X"
description: "Instructions on how to integrate a VL53L1X ToF sensor into Home Assistant."
date: 2019-02-21 00:00
sidebar: true
comments: false
sharing: true
footer: true
logo: raspberry-pi.png
ha_category:
- DIY
- Sensor
ha_release: "0.90"
ha_iot_class: Local Polling
---
The Time of Flight sensor uses an invisible laser to measure distance with millimeter resolution.
Tested devices:
- [Raspberry Pi](https://www.raspberrypi.org/)
- [VL53L1X](https://www.st.com/en/imaging-and-photonics-solutions/vl53l1x.html)
- [Schematic](https://cdn.sparkfun.com/assets/3/5/c/e/2/Qwiic_Distance_Sensor_-_VL53L1X.pdf)
## {% linkable_title Configuration %}
To use the VL53L1X sensor in your installation, add to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
sensor:
- platform: tof
```
{% configuration %}
name:
description: Name of the sensor.
required: false
default: VL53L1X
type: string
i2c_bus:
description: I2c bus used.
required: false
default: 1, for Raspberry Pi 2 and 3.
type: integer
i2c_address:
description: I2c address of the sensor.
required: false
default: "0x29"
type: string
xshut:
description: GPIO port used to reset device.
required: false
default: 16
type: integer
{% endconfiguration %}
## {% linkable_title Example %}
The distance is measured in millimeters, according to the VL53L1X specifications.
```yaml
# Example of customized configuration.yaml entry
sensor:
- platform: tof
name: ToF sensor
i2c_address: 0x29
xshut: 16
```
Several devices may be attached and a GPIO port from RPI is used for reset. XSHUT signal is generated pulsing LOW at initialization and after that, it is kept HIGH all time. This version uses VL53L1X long-range mode that may reach up to 4 meters.
## {% linkable_title Directions for installing i2c on Raspberry Pi %}
Enable the I2c interface with the Raspberry Pi configuration utility:
```bash
# pi user environment: Enable i2c interface
$ sudo raspi-config
```
Select `Interfacing options->I2C` choose `<Yes>` and hit `Enter`, then go to `Finish` and you'll be prompted to reboot.
Install dependencies for use the `smbus-cffi` module and enable your _homeassistant_ user to join the _i2c_ group:
```bash
# pi user environment: Install i2c dependencies and utilities
$ sudo apt-get install build-essential libi2c-dev i2c-tools python-dev libffi-dev
# pi user environment: Add homeassistant user to the i2c group
$ sudo addgroup homeassistant i2c
# pi user environment: Reboot Raspberry Pi to apply changes
$ sudo reboot
```
### {% linkable_title Check the i2c address of the sensor %}
After installing `i2c-tools`, a new utility is available to scan the addresses of the connected sensors:
```bash
$ /usr/sbin/i2cdetect -y 1
```
It will output a table like this:
```text
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- 23 -- -- -- -- -- 29 -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: 40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
```
So you can see the sensor address what you are looking for is **0x29** (there are more i2c sensors in this Raspberry Pi).

13
source/_components/utility_meter.markdown
View File

@ -46,9 +46,10 @@ cycle:
required: true
type: string
offset:
description: Cycle reset occur at the beginning of the period (0 minutes, 0h00 hours, Monday, day 1, January). This option enables the offsetting of these beginnings.
description: "Cycle reset occur at the beginning of the period (0 minutes, 0h00 hours, Monday, day 1, January). This option enables the offsetting of these beginnings. Supported formats: `offset: 'HH:MM:SS'`, `offset: 'HH:MM'` and Time period dictionary (see example below)."
required: false
default: 0
type: time
type: integer
net_consumption:
description: Set this to True if you would like to treat the source as a net meter. This will allow your counter to go both positive and negative.
@ -62,6 +63,16 @@ tariffs:
type: list
{% endconfiguration %}
### {% linkable_title Time period dictionary example %}
```yaml
offset:
# At least one of these must be specified:
days: 1
hours: 0
minutes: 0
```
## {% linkable_title Services %}
### {% linkable_title Service `utility_meter.reset` %}

217
source/_cookbook/automation_knx.markdown
View File

@ -1,217 +0,0 @@
---
layout: page
title: "KNX automation and interaction with other systems"
description: "General KNX set up and communication with other systems like the Philips Hue."
date: 2019-01-20 22:00 +0100
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Automation Examples
---
This cookbook shows a general KNX set up and communication with other systems like the Philips Hue.
## {% linkable_title General KNX setup %}
``` yaml
knx:
# This is all you need to get the KNX component up and running.
# Auto config works nicely and usually no config data for your KNX ip tunnel is needed.
# If the KNX router is not found automatically, check the docs and add the IP config here.
# get some sensor data from KNX to HA
sensor:
- platform: knx
name: Helligkeit Treppe oben
address: '6/1/0'
type: 'illuminance'
# The entity_id of this sensor will be generated from the name by a slug function.
# In this case, it will be sensor.helligkeit_treppe_oben
# See dev tools' state page (icons at the bottom of left side menu) for a list of all entity_ids
light:
# See "sensor" remarks above for an explanation of the resulting entity_ids
- platform: knx
# switched light
name: 'Eltern Decke'
address: '1/2/10'
state_address: '1/2/11'
- platform: knx
# dimmed light
name: 'Eltern Bett'
address: '1/2/12'
state_address: '1/2/15'
brightness_address: '1/2/13'
brightness_state_address: '1/2/16'
cover:
# KNX Covers are roller shutters and blinds.
# These items currently expose a bug with the invert_position setting:
# Either you will get 100% for an open shutter and 0% for a closed one
# or you will get the function of up and down arrows exchanged wrongly.
# Hope this is resolved soon.
# ---
# See "sensor" remarks above for an explanation of the resulting entity_ids
- platform: knx
name: "Eltern"
move_long_address: '3/2/0'
move_short_address: '3/2/1'
position_address: '3/2/3'
position_state_address: '3/2/2'
travelling_time_up: 23
travelling_time_down: 21
invert_position: true
- platform: knx
name: "Büro"
move_long_address: '3/2/4'
move_short_address: '3/2/5'
position_address: '3/2/7'
position_state_address: '3/2/6'
travelling_time_up: 23
travelling_time_down: 21
invert_position: true
```
## {% linkable_title Using some values from HA within KNX %}
``` yaml
# configuration.yaml example
sensor:
# Register with Dark Sky to retrieve current environment data.
# Registration is free for the amount of requests we need here.
- platform: openweathermap
name: OpenWeather
language: de
api_key: YOUR_API_KEY
monitored_conditions:
- weather
- temperature
- wind_speed
- wind_bearing
- humidity
- pressure
- clouds
- rain
- snow
- weather_code
knx:
# Expose the above sensor data from HA to KNX group addresses.
# To find the right "type" setting for each parameter, create a group address in ETS,
# add a consuming actor for this kind of parameter to it and check the properties pane.
# ETS will show you a data type (DPT) that you can compare to the available DPTs in the
# documentation of the HA KNX component.
expose:
- type: 'temperature'
entity_id: 'sensor.dark_sky_temperature'
address: '0/1/10'
- type: 'humidity'
entity_id: 'sensor.dark_sky_humidity'
address: '0/1/11'
- type: 'temperature'
entity_id: 'sensor.dark_sky_pressure'
address: '0/1/12'
- type: 'DPT-9'
entity_id: 'sensor.dark_sky_wind_speed'
address: '0/1/13'
- type: 'DPT-14'
entity_id: 'sensor.dark_sky_wind_bearing'
address: '0/1/14'
```
## {% linkable_title Basic KNX automation %}
This example uses an automation that is activated by a KNX switch.
The automation then triggers a script that controls a KNX light and dims it down in 5 steps from 80% to 0% over a time span of 5 minutes.
Care must be taken to stop the script, when the light is otherwise switched (i.e., by its normal on/off KNX switch). If we don't do that, the light will first switch correctly, but then the script will continue to run in the background and after the next delay has passed it will kick in again and activate its next dim level.
```yaml
knx:
switch:
- platform: knx
# The normal on/off switch for the light
name: "Licht, Eltern Bett"
address: '1/2/12'
- platform: knx
# The switch that triggers the dim script
# This switch must be configured in ETS to send on when pressed and off when released
name: "Licht, Eltern Bett, Fadeout"
address: '1/2/17'
light:
# This is the light that we want to dim (more precisely it is the dimming actuator of the light).
# It is directly controlled through the first switch above.
# (Note that the switch shares its group address with this light and thus controls it over the KNX bus.)
- platform: knx
name: 'Eltern Bett'
address: '1/2/12'
state_address: '1/2/15'
brightness_address: '1/2/13'
brightness_state_address: '1/2/16'
automation:
# start the dim script, if the dim switch is pressed
- id: light_eltern_bett_fadeout
alias: Licht Eltern Bett Fade-Out
trigger:
- entity_id: switch.licht_eltern_bett_fadeout
platform: state
to: 'on'
condition: []
action:
# in case the script was already running, we first stop it
- service: script.turn_off
entity_id: script.light_eltern_bett_fadeout
- service: script.turn_on
entity_id: script.light_eltern_bett_fadeout
# stop the dim script, if light is switched manually
- id: light_eltern_bett_fadeout_stop
alias: Licht Eltern Bett Fade-Out STOP
trigger:
- entity_id: switch.licht_eltern_bett
platform: state
# no argument here = trigger with ANY state change
condition: []
action:
- service: script.turn_off
entity_id: script.light_eltern_bett_fadeout
script:
light_eltern_bett_fadeout:
alias: Licht Eltern Bett Fade-Out
sequence:
- service: light.turn_on
entity_id: light.eltern_bett
data:
brightness_pct: 80
- delay: '00:01:00'
- service: light.turn_on
entity_id: light.eltern_bett
data:
brightness_pct: 60
- delay: '00:01:00'
- service: light.turn_on
entity_id: light.eltern_bett
data:
brightness_pct: 40
- delay: '00:01:00'
- service: light.turn_on
entity_id: light.eltern_bett
data:
brightness_pct: 20
- delay: '00:01:00'
- service: light.turn_on
entity_id: light.eltern_bett
data:
brightness_pct: 10
- delay: '00:01:00'
- service: light.turn_off
entity_id: light.eltern_bett
```

6
source/_docs/authentication/providers.markdown
View File

@ -130,11 +130,11 @@ Activating this auth provider will allow you to authenticate with the API passwo
homeassistant:
auth_providers:
- type: legacy_api_password
http:
api_password: !secret http_password
api_password: !secret http_password
```
`api_password` is required option since 0.90 rlease.
Activating this auth provider will also allow you to provide the API password using an authentication header to make requests against the Home Assistant API. This feature will be dropped in the future in favor of long-lived access tokens.
If you don't specify any `auth_providers` section in the `configuration.yaml` file then this provider will be set up automatically if `api_password` was configured under `http` section.

10
source/_docs/configuration/templating.markdown
View File

@ -149,7 +149,7 @@ With strings:
- For specific values: `now().second`, `now().minute`, `now().hour`, `now().day`, `now().month`, `now().year`, `now().weekday()` and `now().isoweekday()`
- `utcnow()` will be rendered as UTC time.
- For specific values: `utcnow().second`, `utcnow().minute`, `utcnow().hour`, `utcnow().day`, `utcnow().month`, `utcnow().year`, `utcnow().weekday()` and `utcnow().isoweekday()`.
- `as_timestamp()` will convert datetime object or string to UNIX timestamp.
- `as_timestamp()` will convert datetime object or string to UNIX timestamp. This function also be used as a filter.
- `strptime(string, format)` will parse a string to a datetime based on a [format](https://docs.python.org/3.6/library/datetime.html#strftime-and-strptime-behavior).
- Filter `timestamp_local` will convert an UNIX timestamp to local time/data.
- Filter `timestamp_utc` will convert a UNIX timestamp to UTC time/data.
@ -236,10 +236,10 @@ The other part of templating is processing incoming data. It allows you to modif
It depends per component or platform, but it is common to be able to define a template using the `value_template` configuration key. When a new value arrives, your template will be rendered while having access to the following values on top of the usual Home Assistant extensions:
| Variable | Description |
| ------------ | -------------------------------------- |
| `value` | The incoming value. |
| `value_json` | The incoming value parsed as JSON. |
| Variable | Description |
|--------------|------------------------------------|
| `value` | The incoming value. |
| `value_json` | The incoming value parsed as JSON. |
This means that if the incoming values looks like the sample below:

12
source/_lovelace/entity-button.markdown
View File

@ -41,6 +41,16 @@ icon:
description: Overwrites icon or entity picture.
type: string
default: Entity Domain Icon
show_name:
required: false
description: Show name.
type: boolean
default: "true"
show_icon:
required: false
description: Show icon.
type: boolean
default: "true"
tap_action:
required: false
description: Action to take on tap
@ -50,7 +60,7 @@ tap_action:
required: true
description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `none`)"
type: string
default: "`more-info`"
default: "`toggle`"
navigation_path:
required: false
description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`"

7
source/_lovelace/glance.markdown
View File

@ -32,7 +32,12 @@ title:
type: string
show_name:
required: false
description: Show entity names.
description: Show entity name.
type: boolean
default: "true"
show_icon:
required: false
description: Show entity icon.
type: boolean
default: "true"
show_state:

777
source/_posts/2019-03-20-release-90.markdown Normal file
View File

@ -0,0 +1,777 @@
---
layout: post
title: "0.90: Remote UI, Streams, User Groups"
description: "Bring your next level home to the next next leve."
date: 2019-03-20 00:11:03
date_formatted: "March 20, 2019"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2019-03-release-90/remote.png
---
It's time for Home Assistant 0.90 and it's just wow. This release is so packed with cool stuff that it's difficult to even know where to start, so let's just jump in.
The first big feature is that Home Assistant Cloud now supports remote control. This allows you to check in on your home while away from home. Get a notification that motion was detected? Now you can easily check what happened and take action while away. It works end-to-end encrypted. Only thing needed to get started is to enable it. That's it.
For more information on how it works, check out [the documentation](https://www.nabucasa.com/config/remote/) or listen to [the latest episode of the Home Assistant Podcast](https://hasspodcast.io/) (will be released soon).
<p class='img'>
<img src='/images/blog/2019-03-release-90/remote.png' alt='Screenshot of the Remote UI preference.'>
Screenshot of the Remote UI preference.
</p>
## {% linkable_title Camera streams for everyone %}
With this release we're getting serious about cameras. [@hunterjm] has worked months on this and it's finally ready for the first reveal. With the stream component, we will be able to forward streams from cameras in your house and repackage it into formats that your display devices understand. Previously, streaming cameras was limited to 2 frames per second and only in the frontend. For the first version we focused on the HLS format, which is supported by modern browsers and Chromecast. Each camera integration will need to be individually updated, for the first version we have only added support for the generic camera integration.
So what is possible now? You can start streaming your frontdoor feed on your TV when the doorbell rings or you can install a camera in the nursery and turn your Google Home Hub into a babymonitor.
To get started, add `stream:` to your configuration.yaml, configure the [generic camera][camera.generic docs] and start using the new `camera.play_stream` service.
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube.com/embed/l9eBRNBf5Zg" frameborder="0" allowfullscreen></iframe>
</div>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Stream any camera on any device.<br><br>New feature by <a href="https://twitter.com/hunterjm?ref_src=twsrc%5Etfw">@hunterjm</a> coming soon to a <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a> near you. <a href="https://t.co/At9wUkcZZJ">pic.twitter.com/At9wUkcZZJ</a></p>&mdash; Paulus Schoutsen (@balloob) <a href="https://twitter.com/balloob/status/1101216098442067968?ref_src=twsrc%5Etfw">February 28, 2019</a>
</blockquote>
## {% linkable_title User Groups %}
This has been a long time in the making, and has been worked on for a long time: you can now put users in groups to prevent them from being able to configure things from the UI. Users in the new "users" group will not see links to the configuration panel or to the developer tools. This is currently a UI feature, not a security feature. [We're working](https://developers.home-assistant.io/blog/2019/03/11/user-permissions.html) on making this a security feature by limiting access at API level too.
## {% linkable_title Smarter SmartThings %}
If you use Home Assistant Cloud, setting up SmartThings will now automatically leverage Cloudhooks. This means that you will not need to expose your instance to the internet to start using SmartThings. Yay for easy set up and thanks [@andrewsayre]! SmartThings support has also been added for 3 axis sensors and air conditioners.
## {% linkable_title Area love %}
This release also adds some more love to areas. Thanks to [@Swamp-Ig], areas will now be included as room hints when you sync Home Assistant with Google Assistant. This should make setting up a breeze.
Areas can now also be used as targets in services. Just specify `area_id` instead of `entity_id` in your scripts or automations.
We've also made areas a part of the set up flow for integrations. When you add an integration, we will check which devices are added and ask you to configure them right away. That way you won't forget.
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube.com/embed/DVQtsFFg4mc" frameborder="0" allowfullscreen></iframe>
</div>
## {% linkable_title VSCode extension %}
In case you missed it, earlier this week Kees Schollaart released the first version of his Home Assistant extension for the free text editor [VSCode](https://code.visualstudio.com/). It will connect to your instance and will provide you with entity ID autocompletion while editing your config!
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">This weekend I built a <a href="https://twitter.com/code?ref_src=twsrc%5Etfw">@code</a> extension for <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a>! It connects with your Home Assistant host and will provide auto-completion for your entity_id&#39;s! Check it out in the Marketplace: <a href="https://t.co/21PxCqWrlQ">https://t.co/21PxCqWrlQ</a> Ideas/feedback more than welcome! Thanks for helping <a href="https://twitter.com/balloob?ref_src=twsrc%5Etfw">@balloob</a>! <a href="https://t.co/la9SPr5Rjw">pic.twitter.com/la9SPr5Rjw</a></p>&mdash; Kees Schollaart (@keesschollaart) <a href="https://twitter.com/keesschollaart/status/1107362271095898113?ref_src=twsrc%5Etfw">March 17, 2019</a>
</blockquote>
## {% linkable_title New Platforms %}
- Live Streams Component ([@hunterjm] - [#21473]) ([camera docs]) ([stream docs]) (new-platform)
- Add support for homekit controller sensors ([@cpopp] - [#21535]) ([homekit_controller docs]) (new-platform)
- Add SmartThingsAccelCluster to ZHA binary_sensor ([@roblandry] - [#21609]) ([zha docs]) (new-platform)
- Xfinity Gateway device_tracker platform ([@cisasteelersfan] - [#21026]) ([device_tracker docs]) (new-platform)
- Add Time of Flight Sensor using VL53L1X ([@josemotta] - [#21230]) ([tof docs]) (new-platform)
- Adding enigma2 media player ([@fbradyirl] - [#21271]) ([media_player.enigma2 docs]) (new-platform)
- Add support for Cisco Mobility Express ([@fbradyirl] - [#21531]) ([cisco_mobility_express docs]) (new-platform)
- Add ClearPass Policy Manger device tracker ([@zemerick1] - [#21673]) ([device_tracker docs]) (new-platform)
- Add Weather Sensors to Homematic IP ([@SukramJ] - [#21887]) ([homematicip_cloud docs]) (new-platform)
## {% linkable_title If you need help... %}
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
## {% linkable_title Reporting Issues %}
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
<!--more-->
## {% linkable_title Breaking Changes %}
- __http.api_password__ - __Deprecated__ - Users who are still using api_password for authentication will need to move its configuration under auth_providers. Please see the [updated documentation](https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password) for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, __api_password authentication will eventually be removed completely__ and we advise users to change to use one of the [other authentication methods](https://www.home-assistant.io/docs/authentication/providers/#available-auth-providers). If you manually specify auth providers in your `configuration.yaml`, you will need to migrate your API Password from the http section to the auth provider section to continue using it. ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs])
- __Default Config__ - Default config no longer contains the discovery component. That is now part of the initial written configuration.yaml. If you rely on default config and want to use discovery, add `discovery:` back to your configuration.yaml.
- __Netatmo__
* Added support for multiple Netatmo thermostats/valves allowing the user to specify different homes or rooms! Please check the [updated documentation](https://www.home-assistant.io/components/climate.netatmo/) for configuration details. ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs])
* `current_operation` will no longer return the the boiler status, but the operation_mode. For example, heat, cool, or idle. Please check the [updated documentation](https://www.home-assistant.io/components/climate.netatmo/) for more details. ([@shanbs] - [#21633]) ([netatmo docs])
- __Utility Meter__ - Currently the offset configuration parameter is an integer that limits daily cycles to have offsets in days, monthly cycles to have offsets in months, etc.
This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the [updated documentation](https://www.home-assistant.io/components/utility_meter/) for the new configuration options. ([@dgomes] - [#20926]) ([utility_meter docs])
- __KNX__ - An update for xknx to version 0.10.0 requires users to update their configuration by changing `target_temperature_address` to `target_temperature_state_address`. Other fixes and features:
* Connection config can now be configured in xknx.yml.
* Introduce a configurable rate limit which limits the number of KNX telegrams sent to the bus per second.
* Users who configured their lights via xknx.yml no longer need to manually set min_kelvin and max_kelvin (fixes #21251) ([@marvin-w] - [#21541]) ([knx docs])
- __Nanoleaf__ - The Nanoleaf component now supports _both_ nanoleaf lights, Aurora and Canvas. As a result of this change the user needs to change the platform from `nanoleaf_aurora` to `nanoleaf` ([@Oro] - [#21913]) ([light.nanoleaf docs])
- __FireTV__- is now androidtv. Instead of having near-duplicate integrations for androidtv and firetv, the decision was made to combine them into one.
Users will need to change `- platform: firetv` to `- platform: androidtv` in their configuration. ([@JeffLIrion] - [#21944])
- __Tellstick__ - Some configuration cleanup. The way Tellsick sensor configuration was set up using dynamic values for named sensors will not be supported in future versions of Home Assistant. Users that have configured the optional named sensors initiated with only_named will have to update their configuration. Make sure to check the updated documentation for further details. ([@endor-force] - [#21402]) ([tellstick docs])
- __MQTT__ - Pass `Message` object to MQTT message callbacks instead of `topic`, `message` and `qos`. Users of custom components please take note, these values are now available on the passed in message object: `msg.topic`, `msg.message`, `msg.qos`. The old method will continue to work for now but will print warnings. ([@emontnemery] - [#21959]) ([mqtt docs])
## {% linkable_title Beta Fixes %}
- mobile_app component ([@robbiet480] - [#21475]) ([mobile_app docs]) (beta fix) (new-platform)
- Remove UTF8 decoding for Waze ([@philhawthorne] - [#22020]) ([sensor.waze_travel_time docs]) (beta fix)
- Bring back the boiler status ([@cgtobi] - [#22021]) ([netatmo docs]) (beta fix)
- Update additional platforms to use new MQTT message callback ([@emontnemery] - [#22030]) ([device_tracker docs]) ([mqtt_eventstream docs]) ([owntracks docs]) ([snips docs]) ([alarm_control_panel.manual_mqtt docs]) ([automation.mqtt docs]) ([sensor.arwn docs]) ([sensor.mqtt_room docs]) (beta fix)
- Fix lifx light async error ([@awarecan] - [#22031]) ([lifx docs]) (beta fix)
- Fix Google Assistant User with Cloud ([@pvizeli] - [#22042]) ([cloud docs]) (beta fix)
- Mobile App: Require encryption for registrations that support it ([@robbiet480] - [#21852]) ([mobile_app docs]) (beta fix)
- Mobile App: Support rendering multiple templates at once ([@robbiet480] - [#21851]) ([mobile_app docs]) (beta fix)
- Mobile App: Update Location schema updates & device ID generation ([@robbiet480] - [#21849]) ([mobile_app docs]) (beta fix)
- Mobile App: Register devices into the registry ([@robbiet480] - [#21856]) ([mobile_app docs]) (beta fix)
- Mobile App: Sensors ([@robbiet480] - [#21854]) ([mobile_app docs]) (beta fix) (new-platform)
- Bump androidtv to 0.0.11 ([@JeffLIrion] - [#22025]) ([androidtv docs]) (beta fix)
- Mobile App: Enable loading via discovery (surprise inside!) ([@robbiet480] - [#22027]) ([mobile_app docs]) (beta fix)
- Mobile App: Discovery to default configuration.yaml, zeroconf to default_config ([@robbiet480] - [#22028]) ([default_config docs]) ([mobile_app docs]) (beta fix)
- Mobile App: Expose Cloud Remote UI FQDN in registration response ([@robbiet480] - [#22055]) ([cloud docs]) ([mobile_app docs]) (beta fix)
- Return config entry ID after creation ([@balloob] - [#22060]) ([config docs]) (beta fix)
- Correct context ([@awarecan] - [#22061]) ([alexa docs]) (beta fix)
- Binary Sensor for Remote UI & Fix timezone ([@pvizeli] - [#22076]) (beta fix)
- Bump androidtv to 0.0.12 ([@JeffLIrion] - [#22072]) ([androidtv docs]) (beta fix)
- Prevent cloud remote UI when using 127.0.0.1 as trusted network ([@balloob] - [#22093]) ([cloud docs]) (beta fix)
- Beta Fix: FFMPEG and Stream component ([@hunterjm] - [#22091]) ([camera.ffmpeg docs]) ([camera.generic docs]) ([camera.onvif docs]) (beta fix)
- delete previously removed service option from services yaml ([@hunterjm] - [#22123]) (beta fix)
- Remove hass.config from aws_lambda notify payload ([@awarecan] - [#22125]) (breaking change) (beta fix)
- Allow non-admins to listen to certain events ([@balloob] - [#22137]) ([websocket_api docs]) (beta fix)
- Bump tado version ([@WebSpider] - [#22145]) ([tado docs]) (beta fix)
- Fix resetting access token on streams with keepalive ([@hunterjm] - [#22148]) ([stream docs]) (beta fix)
- Remove config check over supervisor ([@pvizeli] - [#22156]) ([hassio docs]) (beta fix)
- Upgrade toonapilib to 3.2.2 + lower interval ([@frenck] - [#22160]) ([toon docs]) (beta fix)
- bump total_connect_client to 0.24 ([@uchagani] - [#22166]) ([totalconnect docs]) (beta fix)
- Update Hass-NabuCasa 0.8 ([@pvizeli] - [#22177]) ([cloud docs]) (beta fix)
- Always load Hass.io component on Hass.io ([@balloob] - [#22185]) (beta fix)
- Fixed typing errors ([@Swamp-Ig] - [#22207]) (beta fix)
## {% linkable_title All changes %}
- Upgrade pyopenuv to 1.0.9 ([@bachya] - [#21513]) ([openuv docs])
- Upgrade pypollencom to 2.2.3 ([@bachya] - [#21517]) ([sensor.pollen docs])
- Upgrade pytile to 2.0.6 ([@bachya] - [#21516]) ([device_tracker docs])
- Upgraded py17track to 2.2.2 ([@bachya] - [#21515]) ([sensor.seventeentrack docs])
- Upgrade pyflunearyou to 1.0.2 ([@bachya] - [#21514]) ([sensor.flunearyou docs])
- Bump starlingbank version to 3.1 ([@Dullage] - [#21501]) ([sensor.starlingbank docs])
- Upgrade opensensemap-api to 0.1.5 ([@fabaff] - [#21524]) ([air_quality docs])
- Register 'firetv.adb_command' service ([@JeffLIrion] - [#21419]) ([media_player.firetv docs])
- Add arm night for alarm decoder ([@koolsb] - [#21488]) ([alarmdecoder docs])
- Upgrade numpy to 1.16.2 ([@fabaff] - [#21525]) ([binary_sensor.trend docs]) ([image_processing.opencv docs]) ([image_processing.tensorflow docs]) ([sensor.pollen docs])
- Upgrade python-mystrom to 0.5.0 ([@fabaff] - [#21523]) ([light.mystrom docs]) ([switch.mystrom docs])
- Mqtt alarm added value_template and code_arm_required ([@ToRvaLDz] - [#19558]) ([alarm_control_panel.mqtt docs])
- Add direct binding for remotes and lights for ZHA ([@dmulcahey] - [#21498]) ([zha docs])
- Add support for homekit controller sensors ([@cpopp] - [#21535]) ([homekit_controller docs]) (new-platform)
- Update CODEOWNERS ([@dgomes] - [#21545])
- Clean up gpslogger tests ([@MartinHjelmare] - [#21543])
- new websocket api way ([@dmulcahey] - [#21533]) ([zha docs])
- Add pause/unpause services to RainMachine ([@bachya] - [#21548]) ([rainmachine docs])
- prevent duplicate event channel registration ([@dmulcahey] - [#21534]) ([zha docs])
- Allow config entry reloading ([@balloob] - [#21502])
- Add separate on/off ids on manual configured IHC lights ([@msvinth] - [#20253]) ([ihc docs]) ([light.ihc docs]) (new-platform)
- add friendly name to devices in the device registry ([@dmulcahey] - [#21499]) ([zha docs])
- Allow chaining contexts ([@balloob] - [#21028]) ([automation docs])
- bump pyxeoma to 1.4.1 to fix and close #19306 ([@trunet] - [#21568]) ([camera.xeoma docs])
- fix exception ([@dmulcahey] - [#21571]) ([zha docs])
- Add config entry remove callback ([@andrewsayre] - [#21576])
- mobile_app component ([@robbiet480] - [#21475]) ([mobile_app docs]) (beta fix) (new-platform)
- Memory optimization for logbook ([@amelchio] - [#21549]) ([logbook docs])
- Get room hints from areas ([@Swamp-Ig] - [#21519]) ([google_assistant docs])
- Centrally define Watt ([@dgomes] - [#21570])
- Add network throughput statistics to systemmonitor sensor ([@dgomes] - [#21575]) ([sensor.systemmonitor docs])
- Update for new pyvesyncv_v2 library and vesync switch support ([@webdjoe] - [#21449]) ([switch.vesync docs])
- ZHA fixes ([@dmulcahey] - [#21592]) ([zha docs])
- Update pyhomematic ([@danielperna84] - [#21600]) ([homematic docs])
- Add parameter hold_secs for Harmony remote send command ([@ehendrix23] - [#19650]) ([remote docs]) ([remote.harmony docs])
- Upgrade motorparts to 1.1.0 ([@rohankapoorcom] - [#21602]) ([sensor.mopar docs])
- Further Yale ZWave lock device mapping cleanup ([@mw-white] - [#21128]) ([zwave docs])
- Added support for multiple Netatmo thermostats/valves ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs]) (breaking change)
- Add the velbus sync clock service ([@Cereal2nd] - [#21308]) ([velbus docs])
- SmartThings remove SmartApp/Automation on integration removal ([@andrewsayre] - [#21594]) ([smartthings docs]) (new-feature)
- Bumping aioasuswrt ([@kennedyshead] - [#21627]) ([asuswrt docs])
- Add device HMIP-eTRV-C to HomematicIP ([@SukramJ] - [#21612])
- Add 'app_name' property and 'apps' config entry to Fire TV ([@JeffLIrion] - [#21601]) ([androidtv docs])
- Add optional sender name for SendGrid ([@srirams] - [#21610]) ([notify.sendgrid docs])
- fix derived rate, fixes #20097 ([@wburgers] - [#21620]) ([sensor.dsmr docs])
- Bump pyflunearyou to 1.0.3 ([@bachya] - [#21634]) ([sensor.flunearyou docs])
- Return Netatmo climate operation_mode instead of boiler status ([@shanbs] - [#21633]) ([netatmo docs]) (breaking change)
- Expose create/delete cloudhook ([@balloob] - [#21606]) ([cloud docs])
- Add storage helper to ZHA and use it for the device node descriptor ([@dmulcahey] - [#21500]) ([zha docs]) (new-platform)
- Allow configuration of update interval for ness_alarm ([@nickw444] - [#21415]) ([ness_alarm docs])
- Replace travis ([@pvizeli] - [#21641])
- Fix actions with tox ([@pvizeli] - [#21642])
- GitHub Workflow ([@pvizeli] - [#21643])
- Upgrade youtube_dl to 2019.03.01 ([@fabaff] - [#21647]) ([media_extractor docs])
- Add support for DHT and DS18B20 sensors via Konnected firmware ([@heythisisnate] - [#21189]) ([konnected docs])
- Allow targeting areas in service calls ([@balloob] - [#21472]) ([alert docs]) ([automation docs]) ([group docs]) ([image_processing docs]) ([light docs]) ([scene docs]) ([script docs])
- Add camera name to logs ([@arsaboo] - [#21653]) ([camera.generic docs])
- Netatmo, handle missing thermostat devices ([@Danielhiversen] - [#21651]) ([netatmo docs])
- Add SmartThingsAccelCluster to ZHA binary_sensor ([@roblandry] - [#21609]) ([zha docs]) (new-platform)
- Add support for multiple devices for PS4 component ([@ktnrg45] - [#21302]) ([ps4 docs])
- Xfinity Gateway device_tracker platform ([@cisasteelersfan] - [#21026]) ([device_tracker docs]) (new-platform)
- Adds option in UPnP component to override callback url ([@StevenLooman] - [#21583]) ([media_player.dlna_dmr docs])
- Serialize amcrest snapshot commands and bump PyPI package to 1.2.4 ([@pnbruckner] - [#21664]) ([amcrest docs])
- Bump nessclient version to 0.9.14 ([@nickw444] - [#21679]) ([ness_alarm docs])
- Allow 202 status code as a successful REST notify response ([@u1f35c] - [#21678]) ([notify docs])
- Bump teslajsonpy to 0.0.24 ([@alandtse] - [#21675]) ([tesla docs])
- Fix Z-Wave relative imports ([@balloob] - [#21693]) ([zwave docs])
- Use new style for built-in ws commmands ([@balloob] - [#21694]) ([websocket_api docs])
- Google Assistant: Create and pass context to service calls ([@Swamp-Ig] - [#21551]) ([google_assistant docs])
- Update to teslajsonpy v0.0.25 ([@alandtse] - [#21702]) ([tesla docs])
- Utility Meter offset defined by a time_period ([@dgomes] - [#20926]) ([utility_meter docs]) (breaking change)
- Change amcrest camera_image to async ([@pnbruckner] - [#21720]) ([amcrest docs])
- Start preparing for homekit_controller config entries ([@Jc2k] - [#21564]) ([homekit_controller docs])
- Support multiple keys in ifttt triggers ([@zeehio] - [#21454]) ([ifttt docs])
- Fix initialization and add "pending" status of Satel integra ([@c-soft] - [#21194]) ([satel_integra docs])
- Fix pylint warning on python 3.7 ([@awarecan] - [#21714]) ([climate.eq3btsmart docs])
- Make pytest in tox quite ([@awarecan] - [#21727])
- tplink - catch SmartDeviceException on is_dimmable call ([@ljmerza] - [#21726]) ([tplink docs])
- Remove pytest warning message ([@awarecan] - [#21713])
- Update .travis.yml ([@pvizeli] - [#21736])
- Revert Travis until github actions work better for PR ([@pvizeli] - [#21746])
- Allow light toggle service to accept all turn on params ([@zewelor] - [#20912]) ([light docs])
- Introduce target_temperature_state_address for climate device ([@marvin-w] - [#21541]) ([knx docs]) (breaking change)
- Upgrade pylint to 2.3.1 ([@scop] - [#21789])
- Add Time of Flight Sensor using VL53L1X ([@josemotta] - [#21230]) ([tof docs]) (new-platform)
- Upgrade huawei-lte-api to 1.1.5 ([@scop] - [#21791]) ([huawei_lte docs])
- Adding enigma2 media player ([@fbradyirl] - [#21271]) ([media_player.enigma2 docs]) (new-platform)
- Bump loopenergy to 0.1.0. Loop updated their socket.io server from 0.9 to 2.0 - which required a library update. ([@pavoni] - [#21809]) ([sensor.loopenergy docs])
- remove occupancy, as it is not available at this level in the iRail api ([@nudded] - [#21810]) ([sensor.nmbs docs])
- Onboarding to generate auth code ([@balloob] - [#21777]) ([auth docs]) ([onboarding docs])
- Remove stub from config component ([@balloob] - [#21822]) ([config docs])
- change paths to be relative ([@uchagani] - [#21827]) ([zwave docs])
- Change how we import config modules ([@balloob] - [#21824]) ([config docs])
- Load logger and system_log components as soon as possible ([@awarecan] - [#21799])
- Resolve auth_store loading race condition ([@awarecan] - [#21794])
- Log if aiohttp hits error during IndieAuth ([@robbiet480] - [#21780]) ([auth docs])
- Add support for Cisco Mobility Express ([@fbradyirl] - [#21531]) ([cisco_mobility_express docs]) (new-platform)
- Synology sensor quick return if attr is null ([@cmsimike] - [#21709]) ([sensor.synologydsm docs])
- fix empty TOPIC_BASE issue ([@engrbm87] - [#21740]) ([mqtt docs])
- Updated to pyeconet 0.0.10 ([@w1ll1am23] - [#21837]) ([water_heater docs])
- Fix config entry exception in Ambient PWS ([@bachya] - [#21836]) ([ambient_station docs])
- Fixed a misspelling in a docstring ([@bachya] - [#21846]) ([ambient_station docs])
- mobile_app improvements ([@robbiet480] - [#21607]) ([mobile_app docs])
- Update honeywell.py to read current humidity for US Thermostats ([@Hackashaq666] - [#21728]) ([climate.honeywell docs])
- Fix TypeError ([@wburgers] - [#21734]) ([sensor.dsmr docs])
- Introduce Entity.async_write_ha_state() to not miss state transition ([@emontnemery] - [#21590])
- Fix authorization header in cors ([@piitaya] - [#21662]) ([http docs])
- Only commit if need. ([@awarecan] - [#21848])
- Bump quirks for ZHA and handle resulting battery % change ([@dmulcahey] - [#21869]) ([zha docs])
- Better cloud check ([@balloob] - [#21875]) ([cloud docs]) ([mobile_app docs])
- Add ClearPass Policy Manger device tracker ([@zemerick1] - [#21673]) ([device_tracker docs]) (new-platform)
- Add SmartThings climate support for Air Conditioners ([@andrewsayre] - [#21840]) ([smartthings docs]) (new-feature)
- Add SmartThings sensor support for Three Axis ([@andrewsayre] - [#21841]) ([smartthings docs]) (new-feature)
- Add user group ([@balloob] - [#21832])
- Update ZHA state handling ([@dmulcahey] - [#21866]) ([zha docs])
- Change lib for whois sensor ([@ludeeus] - [#21878]) ([sensor.whois docs])
- Don't wait until final position of Velux cover is reached ([@Julius2342] - [#21558]) ([velux docs])
- Fix missing code_required check in async_alarm_arm_night ([@ToRvaLDz] - [#21858]) ([mqtt docs])
- Fix icon for sensor.discogs_random_record ([@thibmaek] - [#21891]) ([sensor.discogs docs])
- Add myself to CODEOWNERS for NMBS code ([@thibmaek] - [#21892])
- Modbus write_register accept single value and array ([@gertdb] - [#21621]) ([modbus docs])
- Add custom holidays to workday sensor ([@epleypa] - [#21718]) ([binary_sensor.workday docs])
- Return time based attributes as datetime in Unifi module ([@ndonegan] - [#21146]) ([device_tracker docs])
- Allow emulated hue to set climate component temperature ([@chilicheech] - [#19034]) ([emulated_hue docs])
- bump netdisco to 2.4.0 ([@fbradyirl] - [#21914])
- Deprecate http.api_password ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs]) (breaking change)
- Don't hang forever if manually added cast is down ([@emontnemery] - [#21565]) ([cast docs])
- Add WS subscription command for MQTT ([@balloob] - [#21696]) ([mqtt docs]) ([websocket_api docs])
- Add 'ssl' parameter for FiOS Quantum Gateway and upgrade Pypi ([@cisasteelersfan] - [#21669]) ([device_tracker docs])
- Add as_timestamp() to Jinja filters. ([@rbdixon] - [#21910])
- HomeKit controller config flow fixes ([@Jc2k] - [#21898]) ([homekit_controller docs])
- Update enigma2 based on review comments ([@fbradyirl] - [#21890]) ([enigma2 docs])
- Remove confusing warning for TTS without entity_id ([@amelchio] - [#21927]) ([tts docs])
- Fixes Modbus service.yaml validity ([@gertdb] - [#21923])
- Add cloudhook support to SmartThings component ([@andrewsayre] - [#21905]) ([smartthings docs])
- If registration supports encryption then return encrypted payloads ([@robbiet480] - [#21853]) ([mobile_app docs])
- Allow inverting netdata sensor values ([@michaelarnauts] - [#21711]) ([sensor.netdata docs])
- Changed from nanoleaf_aurora to nanoleaf ([@Oro] - [#21913]) ([light.nanoleaf docs]) (breaking change)
- Minor version bump for anthemav package ([@nugget] - [#21932]) ([media_player.anthemav docs])
- Add area permission check ([@balloob] - [#21835])
- Add an asyncio Lock around pairing, which cant be used concurrently ([@Jc2k] - [#21933]) ([homekit_controller docs])
- Add update user command ([@balloob] - [#21922]) ([config docs])
- Offload Cloud component ([@pvizeli] - [#21937]) ([cloud docs])
- Upgrade schiene to 0.23 ([@fabaff] - [#21940]) ([sensor.deutsche_bahn docs])
- Live Streams Component ([@hunterjm] - [#21473]) ([camera docs]) ([stream docs]) (new-platform)
- Update lametric icon to be HA logo ([@robbiet480] - [#21957]) ([lametric docs])
- Avoid playing queue pollution when restoring Sonos snapshots ([@amelchio] - [#21963]) ([sonos docs])
- Update to sense component to fully be async ([@kbickar] - [#21698]) ([sense docs])
- fix ephember doing http call from property ([@ttroy50] - [#21855]) ([climate.ephember docs])
- Add Weather Sensors to Homematic IP ([@SukramJ] - [#21887]) ([homematicip_cloud docs]) (new-platform)
- Add cloud status ([@balloob] - [#21960]) ([cloud docs])
- Fix MagicHome LEDs with flux_led component ([@autinerd] - [#20733]) ([light.flux_led docs])
- Stream: Only add base url when needed ([@balloob] - [#21979]) ([camera docs]) ([stream docs])
- Allow changing password without being admin ([@balloob] - [#21978]) ([config docs])
- Fix some cloud things ([@balloob] - [#21977])
- homekit_controller: Bump homekit to 0.13.0 ([@Jc2k] - [#21965]) ([homekit_controller docs])
- skip flaky test ([@balloob] - [#21981])
- Write state directly in all MQTT platforms ([@emontnemery] - [#21971]) ([mqtt docs])
- Use .get to ensure we dont get KeyError ([@robbiet480] - [#21993]) ([mobile_app docs])
- Fix error introduced by #21933 ([@Jc2k] - [#21988]) ([homekit_controller docs])
- Add stream source for amcrest component ([@dshokouhi] - [#21983]) ([amcrest docs])
- Set homekit controller entity as unavailable if new connections fail ([@Jc2k] - [#21901]) ([homekit_controller docs])
- Centrally define Energy Units (kWh and Wh) ([@dgomes] - [#21719])
- Mobile App: Registration schema improvements ([@robbiet480] - [#21850]) ([mobile_app docs])
- Add a service require_admin wrapper ([@balloob] - [#21953])
- Update pyhomematic to 0.1.58 ([@danielperna84] - [#21989]) ([homematic docs])
- Use asyncio lock ([@amelchio] - [#21985]) ([sonos docs])
- Add breaking change section to PR template ([@awarecan] - [#21994])
- Rename 'firetv' to 'androidtv' and add Android TV functionality ([@JeffLIrion] - [#21944]) (breaking change)
- Tellstick sensor configuration cleanup ([@endor-force] - [#21402]) ([tellstick docs]) (breaking change)
- Add availability and next run datetime to RainMachine switches ([@bachya] - [#21786]) ([rainmachine docs])
- Add program/zone enable/disable services to RainMachine ([@bachya] - [#21785]) ([rainmachine docs])
- Bump NabuCasa library to 0.5 ([@pvizeli] - [#22010]) ([cloud docs])
- Avoid playing queue pollution with Sonos unjoin ([@amelchio] - [#22004]) ([sonos docs])
- Wait for Sonos regrouping in service calls ([@amelchio] - [#22006]) ([sonos docs])
- fix error in LutronButton init if Button doesn't have a type ([@beavis9k] - [#21921]) ([lutron docs])
- HomeKit controller light - remove code that can never execute ([@Jc2k] - [#21951]) ([homekit_controller docs])
- Nanoleaf availability check ([@Oro] - [#21945]) ([light.nanoleaf docs])
- Pass Message object to MQTT message callbacks ([@emontnemery] - [#21959]) ([mqtt docs]) (breaking change)
- Remove default temp unit ([@andrewsayre] - [#22012]) ([smartthings docs])
- Allow all success status codes in REST notify response ([@isabellaalstrom] - [#22011]) ([notify docs])
- Check updated_date for list and pick first ([@GGeezes] - [#22008])
- Remove UTF8 decoding for Waze ([@philhawthorne] - [#22020]) ([sensor.waze_travel_time docs]) (beta fix)
- Bring back the boiler status ([@cgtobi] - [#22021]) ([netatmo docs]) (beta fix)
- Update additional platforms to use new MQTT message callback ([@emontnemery] - [#22030]) ([device_tracker docs]) ([mqtt_eventstream docs]) ([owntracks docs]) ([snips docs]) ([alarm_control_panel.manual_mqtt docs]) ([automation.mqtt docs]) ([sensor.arwn docs]) ([sensor.mqtt_room docs]) (beta fix)
- Fix lifx light async error ([@awarecan] - [#22031]) ([lifx docs]) (beta fix)
- Fix Google Assistant User with Cloud ([@pvizeli] - [#22042]) ([cloud docs]) (beta fix)
- Mobile App: Require encryption for registrations that support it ([@robbiet480] - [#21852]) ([mobile_app docs]) (beta fix)
- Mobile App: Support rendering multiple templates at once ([@robbiet480] - [#21851]) ([mobile_app docs]) (beta fix)
- Mobile App: Update Location schema updates & device ID generation ([@robbiet480] - [#21849]) ([mobile_app docs]) (beta fix)
- Mobile App: Register devices into the registry ([@robbiet480] - [#21856]) ([mobile_app docs]) (beta fix)
- Mobile App: Sensors ([@robbiet480] - [#21854]) ([mobile_app docs]) (beta fix) (new-platform)
- Bump androidtv to 0.0.11 ([@JeffLIrion] - [#22025]) ([androidtv docs]) (beta fix)
- Mobile App: Enable loading via discovery (surprise inside!) ([@robbiet480] - [#22027]) ([mobile_app docs]) (beta fix)
- Mobile App: Discovery to default configuration.yaml, zeroconf to default_config ([@robbiet480] - [#22028]) ([default_config docs]) ([mobile_app docs]) (beta fix)
- Mobile App: Expose Cloud Remote UI FQDN in registration response ([@robbiet480] - [#22055]) ([cloud docs]) ([mobile_app docs]) (beta fix)
- Return config entry ID after creation ([@balloob] - [#22060]) ([config docs]) (beta fix)
- Correct context ([@awarecan] - [#22061]) ([alexa docs]) (beta fix)
- Binary Sensor for Remote UI & Fix timezone ([@pvizeli] - [#22076]) (beta fix)
- Bump androidtv to 0.0.12 ([@JeffLIrion] - [#22072]) ([androidtv docs]) (beta fix)
- Prevent cloud remote UI when using 127.0.0.1 as trusted network ([@balloob] - [#22093]) ([cloud docs]) (beta fix)
- Beta Fix: FFMPEG and Stream component ([@hunterjm] - [#22091]) ([camera.ffmpeg docs]) ([camera.generic docs]) ([camera.onvif docs]) (beta fix)
- delete previously removed service option from services yaml ([@hunterjm] - [#22123]) (beta fix)
- Remove hass.config from aws_lambda notify payload ([@awarecan] - [#22125]) (breaking change) (beta fix)
- Allow non-admins to listen to certain events ([@balloob] - [#22137]) ([websocket_api docs]) (beta fix)
- Bump tado version ([@WebSpider] - [#22145]) ([tado docs]) (beta fix)
- Fix resetting access token on streams with keepalive ([@hunterjm] - [#22148]) ([stream docs]) (beta fix)
- Remove config check over supervisor ([@pvizeli] - [#22156]) ([hassio docs]) (beta fix)
- Upgrade toonapilib to 3.2.2 + lower interval ([@frenck] - [#22160]) ([toon docs]) (beta fix)
- bump total_connect_client to 0.24 ([@uchagani] - [#22166]) ([totalconnect docs]) (beta fix)
- Update Hass-NabuCasa 0.8 ([@pvizeli] - [#22177]) ([cloud docs]) (beta fix)
- Always load Hass.io component on Hass.io ([@balloob] - [#22185]) (beta fix)
- Fixed typing errors ([@Swamp-Ig] - [#22207]) (beta fix)
[#19034]: https://github.com/home-assistant/home-assistant/pull/19034
[#19407]: https://github.com/home-assistant/home-assistant/pull/19407
[#19558]: https://github.com/home-assistant/home-assistant/pull/19558
[#19650]: https://github.com/home-assistant/home-assistant/pull/19650
[#20253]: https://github.com/home-assistant/home-assistant/pull/20253
[#20733]: https://github.com/home-assistant/home-assistant/pull/20733
[#20912]: https://github.com/home-assistant/home-assistant/pull/20912
[#20926]: https://github.com/home-assistant/home-assistant/pull/20926
[#21026]: https://github.com/home-assistant/home-assistant/pull/21026
[#21028]: https://github.com/home-assistant/home-assistant/pull/21028
[#21128]: https://github.com/home-assistant/home-assistant/pull/21128
[#21146]: https://github.com/home-assistant/home-assistant/pull/21146
[#21189]: https://github.com/home-assistant/home-assistant/pull/21189
[#21194]: https://github.com/home-assistant/home-assistant/pull/21194
[#21230]: https://github.com/home-assistant/home-assistant/pull/21230
[#21271]: https://github.com/home-assistant/home-assistant/pull/21271
[#21302]: https://github.com/home-assistant/home-assistant/pull/21302
[#21308]: https://github.com/home-assistant/home-assistant/pull/21308
[#21402]: https://github.com/home-assistant/home-assistant/pull/21402
[#21415]: https://github.com/home-assistant/home-assistant/pull/21415
[#21419]: https://github.com/home-assistant/home-assistant/pull/21419
[#21449]: https://github.com/home-assistant/home-assistant/pull/21449
[#21454]: https://github.com/home-assistant/home-assistant/pull/21454
[#21472]: https://github.com/home-assistant/home-assistant/pull/21472
[#21473]: https://github.com/home-assistant/home-assistant/pull/21473
[#21475]: https://github.com/home-assistant/home-assistant/pull/21475
[#21488]: https://github.com/home-assistant/home-assistant/pull/21488
[#21498]: https://github.com/home-assistant/home-assistant/pull/21498
[#21499]: https://github.com/home-assistant/home-assistant/pull/21499
[#21500]: https://github.com/home-assistant/home-assistant/pull/21500
[#21501]: https://github.com/home-assistant/home-assistant/pull/21501
[#21502]: https://github.com/home-assistant/home-assistant/pull/21502
[#21513]: https://github.com/home-assistant/home-assistant/pull/21513
[#21514]: https://github.com/home-assistant/home-assistant/pull/21514
[#21515]: https://github.com/home-assistant/home-assistant/pull/21515
[#21516]: https://github.com/home-assistant/home-assistant/pull/21516
[#21517]: https://github.com/home-assistant/home-assistant/pull/21517
[#21519]: https://github.com/home-assistant/home-assistant/pull/21519
[#21523]: https://github.com/home-assistant/home-assistant/pull/21523
[#21524]: https://github.com/home-assistant/home-assistant/pull/21524
[#21525]: https://github.com/home-assistant/home-assistant/pull/21525
[#21531]: https://github.com/home-assistant/home-assistant/pull/21531
[#21533]: https://github.com/home-assistant/home-assistant/pull/21533
[#21534]: https://github.com/home-assistant/home-assistant/pull/21534
[#21535]: https://github.com/home-assistant/home-assistant/pull/21535
[#21541]: https://github.com/home-assistant/home-assistant/pull/21541
[#21543]: https://github.com/home-assistant/home-assistant/pull/21543
[#21545]: https://github.com/home-assistant/home-assistant/pull/21545
[#21548]: https://github.com/home-assistant/home-assistant/pull/21548
[#21549]: https://github.com/home-assistant/home-assistant/pull/21549
[#21551]: https://github.com/home-assistant/home-assistant/pull/21551
[#21558]: https://github.com/home-assistant/home-assistant/pull/21558
[#21564]: https://github.com/home-assistant/home-assistant/pull/21564
[#21565]: https://github.com/home-assistant/home-assistant/pull/21565
[#21568]: https://github.com/home-assistant/home-assistant/pull/21568
[#21570]: https://github.com/home-assistant/home-assistant/pull/21570
[#21571]: https://github.com/home-assistant/home-assistant/pull/21571
[#21575]: https://github.com/home-assistant/home-assistant/pull/21575
[#21576]: https://github.com/home-assistant/home-assistant/pull/21576
[#21583]: https://github.com/home-assistant/home-assistant/pull/21583
[#21590]: https://github.com/home-assistant/home-assistant/pull/21590
[#21592]: https://github.com/home-assistant/home-assistant/pull/21592
[#21594]: https://github.com/home-assistant/home-assistant/pull/21594
[#21600]: https://github.com/home-assistant/home-assistant/pull/21600
[#21601]: https://github.com/home-assistant/home-assistant/pull/21601
[#21602]: https://github.com/home-assistant/home-assistant/pull/21602
[#21606]: https://github.com/home-assistant/home-assistant/pull/21606
[#21607]: https://github.com/home-assistant/home-assistant/pull/21607
[#21609]: https://github.com/home-assistant/home-assistant/pull/21609
[#21610]: https://github.com/home-assistant/home-assistant/pull/21610
[#21612]: https://github.com/home-assistant/home-assistant/pull/21612
[#21620]: https://github.com/home-assistant/home-assistant/pull/21620
[#21621]: https://github.com/home-assistant/home-assistant/pull/21621
[#21627]: https://github.com/home-assistant/home-assistant/pull/21627
[#21633]: https://github.com/home-assistant/home-assistant/pull/21633
[#21634]: https://github.com/home-assistant/home-assistant/pull/21634
[#21641]: https://github.com/home-assistant/home-assistant/pull/21641
[#21642]: https://github.com/home-assistant/home-assistant/pull/21642
[#21643]: https://github.com/home-assistant/home-assistant/pull/21643
[#21647]: https://github.com/home-assistant/home-assistant/pull/21647
[#21651]: https://github.com/home-assistant/home-assistant/pull/21651
[#21653]: https://github.com/home-assistant/home-assistant/pull/21653
[#21662]: https://github.com/home-assistant/home-assistant/pull/21662
[#21664]: https://github.com/home-assistant/home-assistant/pull/21664
[#21669]: https://github.com/home-assistant/home-assistant/pull/21669
[#21673]: https://github.com/home-assistant/home-assistant/pull/21673
[#21675]: https://github.com/home-assistant/home-assistant/pull/21675
[#21678]: https://github.com/home-assistant/home-assistant/pull/21678
[#21679]: https://github.com/home-assistant/home-assistant/pull/21679
[#21693]: https://github.com/home-assistant/home-assistant/pull/21693
[#21694]: https://github.com/home-assistant/home-assistant/pull/21694
[#21696]: https://github.com/home-assistant/home-assistant/pull/21696
[#21698]: https://github.com/home-assistant/home-assistant/pull/21698
[#21702]: https://github.com/home-assistant/home-assistant/pull/21702
[#21709]: https://github.com/home-assistant/home-assistant/pull/21709
[#21711]: https://github.com/home-assistant/home-assistant/pull/21711
[#21713]: https://github.com/home-assistant/home-assistant/pull/21713
[#21714]: https://github.com/home-assistant/home-assistant/pull/21714
[#21718]: https://github.com/home-assistant/home-assistant/pull/21718
[#21719]: https://github.com/home-assistant/home-assistant/pull/21719
[#21720]: https://github.com/home-assistant/home-assistant/pull/21720
[#21726]: https://github.com/home-assistant/home-assistant/pull/21726
[#21727]: https://github.com/home-assistant/home-assistant/pull/21727
[#21728]: https://github.com/home-assistant/home-assistant/pull/21728
[#21734]: https://github.com/home-assistant/home-assistant/pull/21734
[#21736]: https://github.com/home-assistant/home-assistant/pull/21736
[#21740]: https://github.com/home-assistant/home-assistant/pull/21740
[#21746]: https://github.com/home-assistant/home-assistant/pull/21746
[#21777]: https://github.com/home-assistant/home-assistant/pull/21777
[#21780]: https://github.com/home-assistant/home-assistant/pull/21780
[#21785]: https://github.com/home-assistant/home-assistant/pull/21785
[#21786]: https://github.com/home-assistant/home-assistant/pull/21786
[#21789]: https://github.com/home-assistant/home-assistant/pull/21789
[#21791]: https://github.com/home-assistant/home-assistant/pull/21791
[#21794]: https://github.com/home-assistant/home-assistant/pull/21794
[#21799]: https://github.com/home-assistant/home-assistant/pull/21799
[#21809]: https://github.com/home-assistant/home-assistant/pull/21809
[#21810]: https://github.com/home-assistant/home-assistant/pull/21810
[#21822]: https://github.com/home-assistant/home-assistant/pull/21822
[#21824]: https://github.com/home-assistant/home-assistant/pull/21824
[#21827]: https://github.com/home-assistant/home-assistant/pull/21827
[#21832]: https://github.com/home-assistant/home-assistant/pull/21832
[#21835]: https://github.com/home-assistant/home-assistant/pull/21835
[#21836]: https://github.com/home-assistant/home-assistant/pull/21836
[#21837]: https://github.com/home-assistant/home-assistant/pull/21837
[#21840]: https://github.com/home-assistant/home-assistant/pull/21840
[#21841]: https://github.com/home-assistant/home-assistant/pull/21841
[#21846]: https://github.com/home-assistant/home-assistant/pull/21846
[#21848]: https://github.com/home-assistant/home-assistant/pull/21848
[#21849]: https://github.com/home-assistant/home-assistant/pull/21849
[#21850]: https://github.com/home-assistant/home-assistant/pull/21850
[#21851]: https://github.com/home-assistant/home-assistant/pull/21851
[#21852]: https://github.com/home-assistant/home-assistant/pull/21852
[#21853]: https://github.com/home-assistant/home-assistant/pull/21853
[#21854]: https://github.com/home-assistant/home-assistant/pull/21854
[#21855]: https://github.com/home-assistant/home-assistant/pull/21855
[#21856]: https://github.com/home-assistant/home-assistant/pull/21856
[#21858]: https://github.com/home-assistant/home-assistant/pull/21858
[#21866]: https://github.com/home-assistant/home-assistant/pull/21866
[#21869]: https://github.com/home-assistant/home-assistant/pull/21869
[#21875]: https://github.com/home-assistant/home-assistant/pull/21875
[#21878]: https://github.com/home-assistant/home-assistant/pull/21878
[#21884]: https://github.com/home-assistant/home-assistant/pull/21884
[#21887]: https://github.com/home-assistant/home-assistant/pull/21887
[#21890]: https://github.com/home-assistant/home-assistant/pull/21890
[#21891]: https://github.com/home-assistant/home-assistant/pull/21891
[#21892]: https://github.com/home-assistant/home-assistant/pull/21892
[#21898]: https://github.com/home-assistant/home-assistant/pull/21898
[#21901]: https://github.com/home-assistant/home-assistant/pull/21901
[#21905]: https://github.com/home-assistant/home-assistant/pull/21905
[#21910]: https://github.com/home-assistant/home-assistant/pull/21910
[#21913]: https://github.com/home-assistant/home-assistant/pull/21913
[#21914]: https://github.com/home-assistant/home-assistant/pull/21914
[#21921]: https://github.com/home-assistant/home-assistant/pull/21921
[#21922]: https://github.com/home-assistant/home-assistant/pull/21922
[#21923]: https://github.com/home-assistant/home-assistant/pull/21923
[#21927]: https://github.com/home-assistant/home-assistant/pull/21927
[#21932]: https://github.com/home-assistant/home-assistant/pull/21932
[#21933]: https://github.com/home-assistant/home-assistant/pull/21933
[#21937]: https://github.com/home-assistant/home-assistant/pull/21937
[#21940]: https://github.com/home-assistant/home-assistant/pull/21940
[#21944]: https://github.com/home-assistant/home-assistant/pull/21944
[#21945]: https://github.com/home-assistant/home-assistant/pull/21945
[#21951]: https://github.com/home-assistant/home-assistant/pull/21951
[#21953]: https://github.com/home-assistant/home-assistant/pull/21953
[#21957]: https://github.com/home-assistant/home-assistant/pull/21957
[#21959]: https://github.com/home-assistant/home-assistant/pull/21959
[#21960]: https://github.com/home-assistant/home-assistant/pull/21960
[#21963]: https://github.com/home-assistant/home-assistant/pull/21963
[#21965]: https://github.com/home-assistant/home-assistant/pull/21965
[#21971]: https://github.com/home-assistant/home-assistant/pull/21971
[#21977]: https://github.com/home-assistant/home-assistant/pull/21977
[#21978]: https://github.com/home-assistant/home-assistant/pull/21978
[#21979]: https://github.com/home-assistant/home-assistant/pull/21979
[#21981]: https://github.com/home-assistant/home-assistant/pull/21981
[#21983]: https://github.com/home-assistant/home-assistant/pull/21983
[#21985]: https://github.com/home-assistant/home-assistant/pull/21985
[#21988]: https://github.com/home-assistant/home-assistant/pull/21988
[#21989]: https://github.com/home-assistant/home-assistant/pull/21989
[#21993]: https://github.com/home-assistant/home-assistant/pull/21993
[#21994]: https://github.com/home-assistant/home-assistant/pull/21994
[#22004]: https://github.com/home-assistant/home-assistant/pull/22004
[#22006]: https://github.com/home-assistant/home-assistant/pull/22006
[#22008]: https://github.com/home-assistant/home-assistant/pull/22008
[#22010]: https://github.com/home-assistant/home-assistant/pull/22010
[#22011]: https://github.com/home-assistant/home-assistant/pull/22011
[#22012]: https://github.com/home-assistant/home-assistant/pull/22012
[#22020]: https://github.com/home-assistant/home-assistant/pull/22020
[#22021]: https://github.com/home-assistant/home-assistant/pull/22021
[#22025]: https://github.com/home-assistant/home-assistant/pull/22025
[#22027]: https://github.com/home-assistant/home-assistant/pull/22027
[#22028]: https://github.com/home-assistant/home-assistant/pull/22028
[#22030]: https://github.com/home-assistant/home-assistant/pull/22030
[#22031]: https://github.com/home-assistant/home-assistant/pull/22031
[#22042]: https://github.com/home-assistant/home-assistant/pull/22042
[#22055]: https://github.com/home-assistant/home-assistant/pull/22055
[#22060]: https://github.com/home-assistant/home-assistant/pull/22060
[#22061]: https://github.com/home-assistant/home-assistant/pull/22061
[#22072]: https://github.com/home-assistant/home-assistant/pull/22072
[#22076]: https://github.com/home-assistant/home-assistant/pull/22076
[#22091]: https://github.com/home-assistant/home-assistant/pull/22091
[#22093]: https://github.com/home-assistant/home-assistant/pull/22093
[#22123]: https://github.com/home-assistant/home-assistant/pull/22123
[#22125]: https://github.com/home-assistant/home-assistant/pull/22125
[#22137]: https://github.com/home-assistant/home-assistant/pull/22137
[#22145]: https://github.com/home-assistant/home-assistant/pull/22145
[#22148]: https://github.com/home-assistant/home-assistant/pull/22148
[#22156]: https://github.com/home-assistant/home-assistant/pull/22156
[#22160]: https://github.com/home-assistant/home-assistant/pull/22160
[#22166]: https://github.com/home-assistant/home-assistant/pull/22166
[#22177]: https://github.com/home-assistant/home-assistant/pull/22177
[#22185]: https://github.com/home-assistant/home-assistant/pull/22185
[#22207]: https://github.com/home-assistant/home-assistant/pull/22207
[@Cereal2nd]: https://github.com/Cereal2nd
[@Danielhiversen]: https://github.com/Danielhiversen
[@Dullage]: https://github.com/Dullage
[@GGeezes]: https://github.com/GGeezes
[@Hackashaq666]: https://github.com/Hackashaq666
[@Jc2k]: https://github.com/Jc2k
[@JeffLIrion]: https://github.com/JeffLIrion
[@Julius2342]: https://github.com/Julius2342
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@Oro]: https://github.com/Oro
[@StevenLooman]: https://github.com/StevenLooman
[@SukramJ]: https://github.com/SukramJ
[@Swamp-Ig]: https://github.com/Swamp-Ig
[@ToRvaLDz]: https://github.com/ToRvaLDz
[@WebSpider]: https://github.com/WebSpider
[@alandtse]: https://github.com/alandtse
[@amelchio]: https://github.com/amelchio
[@andrewsayre]: https://github.com/andrewsayre
[@arsaboo]: https://github.com/arsaboo
[@autinerd]: https://github.com/autinerd
[@awarecan]: https://github.com/awarecan
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@beavis9k]: https://github.com/beavis9k
[@c-soft]: https://github.com/c-soft
[@cgtobi]: https://github.com/cgtobi
[@chilicheech]: https://github.com/chilicheech
[@cisasteelersfan]: https://github.com/cisasteelersfan
[@cmsimike]: https://github.com/cmsimike
[@cpopp]: https://github.com/cpopp
[@danielperna84]: https://github.com/danielperna84
[@dgomes]: https://github.com/dgomes
[@dmulcahey]: https://github.com/dmulcahey
[@dshokouhi]: https://github.com/dshokouhi
[@ehendrix23]: https://github.com/ehendrix23
[@emontnemery]: https://github.com/emontnemery
[@endor-force]: https://github.com/endor-force
[@engrbm87]: https://github.com/engrbm87
[@epleypa]: https://github.com/epleypa
[@fabaff]: https://github.com/fabaff
[@fbradyirl]: https://github.com/fbradyirl
[@frenck]: https://github.com/frenck
[@gertdb]: https://github.com/gertdb
[@heythisisnate]: https://github.com/heythisisnate
[@hunterjm]: https://github.com/hunterjm
[@isabellaalstrom]: https://github.com/isabellaalstrom
[@josemotta]: https://github.com/josemotta
[@kbickar]: https://github.com/kbickar
[@kennedyshead]: https://github.com/kennedyshead
[@koolsb]: https://github.com/koolsb
[@ktnrg45]: https://github.com/ktnrg45
[@ljmerza]: https://github.com/ljmerza
[@ludeeus]: https://github.com/ludeeus
[@marvin-w]: https://github.com/marvin-w
[@michaelarnauts]: https://github.com/michaelarnauts
[@msvinth]: https://github.com/msvinth
[@mw-white]: https://github.com/mw-white
[@ndonegan]: https://github.com/ndonegan
[@nickw444]: https://github.com/nickw444
[@nudded]: https://github.com/nudded
[@nugget]: https://github.com/nugget
[@pavoni]: https://github.com/pavoni
[@philhawthorne]: https://github.com/philhawthorne
[@piitaya]: https://github.com/piitaya
[@pnbruckner]: https://github.com/pnbruckner
[@pvizeli]: https://github.com/pvizeli
[@rbdixon]: https://github.com/rbdixon
[@robbiet480]: https://github.com/robbiet480
[@roblandry]: https://github.com/roblandry
[@rohankapoorcom]: https://github.com/rohankapoorcom
[@scop]: https://github.com/scop
[@shanbs]: https://github.com/shanbs
[@srirams]: https://github.com/srirams
[@thibmaek]: https://github.com/thibmaek
[@trunet]: https://github.com/trunet
[@ttroy50]: https://github.com/ttroy50
[@u1f35c]: https://github.com/u1f35c
[@uchagani]: https://github.com/uchagani
[@w1ll1am23]: https://github.com/w1ll1am23
[@wburgers]: https://github.com/wburgers
[@webdjoe]: https://github.com/webdjoe
[@zeehio]: https://github.com/zeehio
[@zemerick1]: https://github.com/zemerick1
[@zewelor]: https://github.com/zewelor
[air_quality docs]: /components/air_quality/
[alarm_control_panel.manual_mqtt docs]: /components/alarm_control_panel.manual_mqtt/
[alarm_control_panel.mqtt docs]: /components/alarm_control_panel.mqtt/
[alarmdecoder docs]: /components/alarmdecoder/
[alert docs]: /components/alert/
[alexa docs]: /components/alexa/
[ambient_station docs]: /components/ambient_station/
[amcrest docs]: /components/amcrest/
[androidtv docs]: /components/androidtv/
[api docs]: /components/api/
[asuswrt docs]: /components/asuswrt/
[auth docs]: /components/auth/
[automation docs]: /components/automation/
[automation.mqtt docs]: /docs/automation/trigger/#mqtt-trigger
[binary_sensor.trend docs]: /components/binary_sensor.trend/
[binary_sensor.workday docs]: /components/binary_sensor.workday/
[camera docs]: /components/camera/
[camera.ffmpeg docs]: /components/camera.ffmpeg/
[camera.generic docs]: /components/camera.generic/
[camera.onvif docs]: /components/camera.onvif/
[camera.proxy docs]: /components/camera.proxy/
[camera.xeoma docs]: /components/camera.xeoma/
[cast docs]: /components/cast/
[cisco_mobility_express docs]: /components/cisco_mobility_express/
[climate.ephember docs]: /components/climate.ephember/
[climate.eq3btsmart docs]: /components/climate.eq3btsmart/
[climate.honeywell docs]: /components/climate.honeywell/
[climate.netatmo docs]: /components/climate.netatmo/
[cloud docs]: /components/cloud/
[config docs]: /components/config/
[default_config docs]: /components/default_config/
[device_tracker docs]: /components/device_tracker/
[emulated_hue docs]: /components/emulated_hue/
[enigma2 docs]: /components/enigma2/
[frontend docs]: /components/frontend/
[google_assistant docs]: /components/google_assistant/
[group docs]: /components/group/
[hassio docs]: /components/hassio/
[homekit_controller docs]: /components/homekit_controller/
[homematic docs]: /components/homematic/
[homematicip_cloud docs]: /components/homematicip_cloud/
[http docs]: /components/http/
[huawei_lte docs]: /components/huawei_lte/
[ifttt docs]: /components/ifttt/
[ihc docs]: /components/ihc/
[image_processing docs]: /components/image_processing/
[image_processing.opencv docs]: /components/image_processing.opencv/
[image_processing.tensorflow docs]: /components/image_processing.tensorflow/
[knx docs]: /components/knx/
[konnected docs]: /components/konnected/
[lametric docs]: /components/lametric/
[lifx docs]: /components/lifx/
[light docs]: /components/light/
[light.flux_led docs]: /components/light.flux_led/
[light.ihc docs]: /components/light.ihc/
[light.mystrom docs]: /components/light.mystrom/
[light.nanoleaf docs]: /components/light.nanoleaf/
[logbook docs]: /components/logbook/
[lutron docs]: /components/lutron/
[media_extractor docs]: /components/media_extractor/
[media_player.anthemav docs]: /components/media_player.anthemav/
[media_player.dlna_dmr docs]: /components/media_player.dlna_dmr/
[media_player.enigma2 docs]: /components/media_player.enigma2/
[media_player.firetv docs]: /components/media_player.firetv/
[mobile_app docs]: /components/mobile_app/
[modbus docs]: /components/modbus/
[mqtt docs]: /components/mqtt/
[mqtt_eventstream docs]: /components/mqtt_eventstream/
[ness_alarm docs]: /components/ness_alarm/
[netatmo docs]: /components/netatmo/
[notify docs]: /components/notify/
[notify.sendgrid docs]: /components/notify.sendgrid/
[onboarding docs]: /components/onboarding/
[openuv docs]: /components/openuv/
[owntracks docs]: /components/owntracks/
[ps4 docs]: /components/ps4/
[rainmachine docs]: /components/rainmachine/
[remote docs]: /components/remote/
[remote.harmony docs]: /components/remote.harmony/
[satel_integra docs]: /components/satel_integra/
[scene docs]: /components/scene/
[script docs]: /components/script/
[sense docs]: /components/sense/
[sensor.arwn docs]: /components/sensor.arwn/
[sensor.deutsche_bahn docs]: /components/sensor.deutsche_bahn/
[sensor.discogs docs]: /components/sensor.discogs/
[sensor.dsmr docs]: /components/sensor.dsmr/
[sensor.flunearyou docs]: /components/sensor.flunearyou/
[sensor.loopenergy docs]: /components/sensor.loopenergy/
[sensor.mopar docs]: /components/sensor.mopar/
[sensor.mqtt_room docs]: /components/sensor.mqtt_room/
[sensor.netdata docs]: /components/sensor.netdata/
[sensor.nmbs docs]: /components/sensor.nmbs/
[sensor.pollen docs]: /components/sensor.pollen/
[sensor.seventeentrack docs]: /components/sensor.seventeentrack/
[sensor.starlingbank docs]: /components/sensor.starlingbank/
[sensor.synologydsm docs]: /components/sensor.synologydsm/
[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
[sensor.whois docs]: /components/sensor.whois/
[smartthings docs]: /components/smartthings/
[snips docs]: /components/snips/
[sonos docs]: /components/sonos/
[stream docs]: /components/stream/
[switch.mystrom docs]: /components/switch.mystrom/
[switch.vesync docs]: /components/switch.vesync/
[tado docs]: /components/tado/
[tellstick docs]: /components/tellstick/
[tesla docs]: /components/tesla/
[tof docs]: /components/tof/
[toon docs]: /components/toon/
[totalconnect docs]: /components/totalconnect/
[tplink docs]: /components/tplink/
[tts docs]: /components/tts/
[utility_meter docs]: /components/utility_meter/
[velbus docs]: /components/velbus/
[velux docs]: /components/velux/
[water_heater docs]: /components/water_heater/
[websocket_api docs]: /components/websocket_api/
[zeroconf docs]: /components/zeroconf/
[zha docs]: /components/zha/
[zwave docs]: /components/zwave/

BIN
source/images/blog/2019-03-release-90/remote.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 33 KiB

BIN
source/images/supported_brands/androidtv.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

0
source/images/supported_brands/nanoleaf_aurora_light.png → source/images/supported_brands/nanoleaf_light.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 1.9 KiB

After

Width:  |  Height:  |  Size: 1.9 KiB

BIN
source/images/supported_brands/openwebif.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.9 KiB

102
source/images/supported_brands/xfinity.svg Normal file
View File

@ -0,0 +1,102 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="1000"
height="337.54373"
id="svg3091"
version="1.1"
inkscape:version="0.48.5 r10040"
sodipodi:docname="New document 5">
<defs
id="defs3093" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="0.56806641"
inkscape:cx="58.867679"
inkscape:cy="8.199806"
inkscape:document-units="px"
inkscape:current-layer="layer1"
showgrid="false"
fit-margin-top="0"
fit-margin-left="0"
fit-margin-right="0"
fit-margin-bottom="0"
inkscape:window-width="1920"
inkscape:window-height="1028"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata3096">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title></dc:title>
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1"
transform="translate(94.857143,-211.56067)">
<path
sodipodi:nodetypes="ccccccccccccccccc"
inkscape:connector-curvature="0"
id="path3049"
d="m -94.857143,473.78389 69.005304,-91.97704 -62.595048,-84.30501 25.84625,0 c 16.598959,0 21.165625,6.81756 27.038366,13.79025 L -4.2528966,354.4335 25.335164,315.13004 c 12.314295,-16.47992 15.895641,-17.6282 33.653846,-17.6282 l 22.061875,0 -63.48133,84.27384 123.150225,167.32872 -27.24359,0 c -15.6546,0 -21.64468,-6.6301 -25.765706,-12.15301 L -4.6121595,409.61408 -43.136903,460.91807 c -5.105721,6.56686 -12.31492,12.86582 -26.079214,12.86582 z"
style="fill:#c8001d;fill-opacity:1;stroke:none" />
<path
sodipodi:nodetypes="ccccccccccccccc"
inkscape:connector-curvature="0"
id="path3051"
d="m 164.27667,473.78389 -35.25641,0 0,-144.23077 -41.185096,0 22.435896,-32.05128 18.7492,0 0,-17.98401 c 0,-60.49803 57.63324,-75.21421 89.99032,-64.95867 l -7.23117,32.04162 c -23.94851,-5.21444 -47.50274,3.3982 -47.50274,39.68311 l 0,11.21795 45.35337,0 0,32.05128 -45.35337,0 z"
style="fill:#c8001d;fill-opacity:1;stroke:none" />
<path
sodipodi:nodetypes="ccccc"
inkscape:connector-curvature="0"
id="path3053"
d="m 273.7326,297.50184 0,176.28205 -36.05769,0 0,-176.28205 z"
style="fill:#c8001d;fill-opacity:1;stroke:none" />
<path
sodipodi:nodetypes="cccccccccccccc"
inkscape:connector-curvature="0"
id="path3055"
d="m 316.0403,473.78389 0,-176.28205 35.57692,0 0,17.6282 c 0,0 17.40888,-21.27723 55.07529,-21.27723 43.19527,0 71.0465,32.07534 71.0465,75.76441 l 0,104.16667 -19.71154,0 c -10.65862,0 -16.02564,-8.2991 -16.02564,-16.02564 l 0,-80.12821 c 0,-33.20739 -17.10049,-49.60014 -43.63288,-49.60014 -32.60838,0 -46.75173,25.56168 -46.75173,25.56168 l 0,120.19231 z"
style="fill:#c8001d;fill-opacity:1;stroke:none" />
<path
style="fill:#c8001d;fill-opacity:1;stroke:none"
d="m 555.32932,297.50184 0,176.28205 -36.0577,0 0,-176.28205 z"
id="path3057"
inkscape:connector-curvature="0"
sodipodi:nodetypes="ccccc" />
<path
sodipodi:nodetypes="cccccccccccccccc"
inkscape:connector-curvature="0"
id="path3059"
d="m 583.02747,329.55312 0,-32.05128 37.98077,0 0,-55.21702 35.73718,-15.2958 0,70.51282 35.25641,0 14.42308,32.05128 -49.67949,0 0,83.33333 c 0,24.71766 22.16725,36.29709 48.79441,28.95625 l 7.23118,31.54292 c 0,0 -10.21911,3.61559 -26.18187,3.61559 -41.9072,0 -65.5809,-26.88742 -65.5809,-62.51219 l 0,-84.9359 z"
style="fill:#c8001d;fill-opacity:1;stroke:none" />
<path
sodipodi:nodetypes="cccccccccccc"
inkscape:connector-curvature="0"
id="path3061"
d="m 720.84799,297.50184 17.6282,0 c 20.40175,0 25.02018,6.28024 31.09724,20.42394 l 40.1451,86.2004 48.48652,-90.69929 c 5.86952,-10.32108 11.45077,-15.92505 29.3096,-15.92505 l 17.62821,0 -124.42367,231.1774 c -8.48987,15.3491 -13.22053,20.42516 -32.62761,20.42516 l -18.33348,0 59.77203,-108.05474 z"
style="fill:#c8001d;fill-opacity:1;stroke:none" />
</g>
</svg>
Side by Side

After

Width:  |  Height:  |  Size: 4.7 KiB

7
source/lovelace/changelog.markdown
View File

@ -8,6 +8,13 @@ comments: false
sharing: true
footer: true
---
## {% linkable_title Changes in 0.88.0 %}
- 📣 Disable toast notifications for successful operations ([#2700](https://github.com/home-assistant/home-assistant-polymer/pull/2822))
- 📣 Color Picker: Toggleable between segmented and continuous ([#2806](https://github.com/home-assistant/home-assistant-polymer/pull/2806))
- 📣 Theming: New CSS card style `ha-card-box-shadow` ([#2855](https://github.com/home-assistant/home-assistant-polymer/pull/2855))
- 🔧 Fix login issue on Firefox ([#2860](https://github.com/home-assistant/home-assistant-polymer/pull/2860))
- 🔧 [light card]: Fix click events ([#2850](https://github.com/home-assistant/home-assistant-polymer/pull/2850))
## {% linkable_title Changes in 0.87.0 %}
- 📣 MDI icons updated to [3.3.92](https://cdn.materialdesignicons.com/3.3.92/)
- 📣 Theming: New CSS card style `ha-card-border-radius`