mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-20 07:46:52 +00:00
Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
ae8be44658
@ -100,9 +100,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 98
|
||||
current_patch_version: 5
|
||||
date_released: 2019-09-07
|
||||
current_minor_version: 99
|
||||
current_patch_version: 2
|
||||
date_released: 2019-09-19
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -3,9 +3,7 @@ title: "HomeMatic"
|
||||
description: "HomeMatic hardware support to turn you Home-Assistant into a CCU."
|
||||
---
|
||||
|
||||
Set up a [HomeMatic](https://github.com/eq-3/occu) hardware layer. For learning and handling devices use [Homematic-Manager](https://github.com/hobbyquaker/homematic-manager) > 2.0.
|
||||
|
||||
The logic layer will be Home Assistant. There is no ReGa or other logic layer installed. You can't import an existing configuration, you'll need re-learn it into Home Assistant.
|
||||
You can't import an existing configuration, you'll need re-learn it into Home Assistant. There is an experimental WebUI alias Regahss support since 9.0 - before it was required to use a 3party tool.
|
||||
|
||||
Follow devices will be supported and tested:
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ Set up [Mosquitto](https://mosquitto.org/) as MQTT broker.
|
||||
|
||||
<div class='warning note'>
|
||||
|
||||
Since version 4.1 of the addon, an explicit ACL definition is now required, [see these instructions](https://www.home-assistant.io/addons/mosquitto/#access-control-lists-acls).
|
||||
Since version 4.1 of the addon, an explicit ACL definition is now required if you plan to use legacy logins and `"anonymous": true` [see these instructions](https://www.home-assistant.io/addons/mosquitto/#access-control-lists-acls).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -174,7 +174,7 @@ If you get a "Device authentication required, no keys available" error when tryi
|
||||
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.
|
||||
</div>
|
||||
|
||||
Once you've successfully connected to your Android TV / Fire TV via the command `adb connect <ipaddress>`, the file `adbkey` will be created on your computer. The default locations for this file is (from [https://developer.android.com/studio/command-line/adb](https://developer.android.com/studio/command-line/adb)):
|
||||
Once you've successfully connected to your Android TV / Fire TV via the command `adb connect <ipaddress>:5555`, the file `adbkey` will be created on your computer. The default locations for this file is (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.`
|
||||
|
||||
@ -37,7 +37,7 @@ device_tracker:
|
||||
track_new_devices:
|
||||
description: If new discovered devices are tracked by default.
|
||||
required: false
|
||||
default: true
|
||||
default: false
|
||||
type: boolean
|
||||
interval_seconds:
|
||||
description: Seconds between each scan for new devices.
|
||||
|
||||
@ -9,6 +9,7 @@ ha_category:
|
||||
- Lock
|
||||
- Sensor
|
||||
ha_release: 0.64
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.bmw_connected_drive/
|
||||
- /components/device_tracker.bmw_connected_drive/
|
||||
|
||||
@ -10,10 +10,18 @@ ha_iot_class: Local Polling
|
||||
redirect_from: /components/media_player.cast/
|
||||
---
|
||||
|
||||
Google Cast devices like Android TVs and Chromecasts will be automatically
|
||||
discovered if you enable [the discovery integration](/components/discovery/). If
|
||||
you don't have the discovery integration enabled, you can enable the Cast
|
||||
integration by going to the Integrations page inside the config panel.
|
||||
You can enable the Cast integration by going to the Integrations page inside the config panel.
|
||||
|
||||
## Home Assistant Cast
|
||||
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI. You can load it on your Chromecast by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI or by using the `cast.show_lovelace_ui` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on.
|
||||
|
||||
```json
|
||||
{
|
||||
"entity_id": "media_player.office_display_4",
|
||||
"view_path": "lights"
|
||||
}
|
||||
```
|
||||
|
||||
## Home Assistant Cast
|
||||
|
||||
@ -28,13 +36,11 @@ The Cast integration allows you to start Home Assistant Cast on any Chromecast d
|
||||
|
||||
## Advanced use
|
||||
|
||||
The Cast integration has some extra configuration options available for advanced
|
||||
users. You will still need to create a config entry to initialize the Cast
|
||||
integration.
|
||||
Note that Home Assistant Cast requires your Home Assistant installation to be accessible via `https://`. If you're using Home Assistant Cloud, you don't need to do anything. Otherwise you must make sure that you have configured the `base_url` for [the `http` integration](/components/http/).
|
||||
|
||||
For example, Cast devices can only be discovered if they are on the same subnet
|
||||
as Home Assistant. If this is not the case,
|
||||
you want to configure the IP address of the Cast device directly:
|
||||
## Advanced use
|
||||
|
||||
Cast devices can only be discovered if they are on the same subnet as Home Assistant. If this is not the case, you need to configure the IP address of the Cast device directly:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -43,10 +49,6 @@ cast:
|
||||
- host: 192.168.1.10
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
You may need to enable Multicast DNS (MDNS) on your router if you are on a different subnet or VLAN.
|
||||
</div>
|
||||
|
||||
{% configuration %}
|
||||
media_player:
|
||||
description: A list that contains all Cast devices.
|
||||
@ -64,14 +66,3 @@ media_player:
|
||||
required: false
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
If you want to manually configure multiple Cast media players, you can define
|
||||
those as follows:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for multiple devices
|
||||
cast:
|
||||
media_player:
|
||||
- host: IP_ADDRESS_DEVICE_1
|
||||
- host: IP_ADDRESS_DEVICE_2
|
||||
```
|
||||
|
||||
@ -24,7 +24,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
## Supported hardware
|
||||
|
||||
- The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the [Daikin Online Controller](https://play.google.com/store/apps/details?id=eu.daikin.remoapp) application.
|
||||
- The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the [Daikin Online Controller](https://play.google.com/store/apps/details?id=eu.daikin.remoapp) application. The new versions of WiFi Controller Unit (BRP069Bxx) also should work but it have to be confirmed by users. Tested and working device is BRP069B45.
|
||||
- The Australian version of the Daikin Wifi Controller Unit BRP072A42. Confirmed working on a Daikin Cora Series Reverse Cycle Split System Air Conditioner 2.5kW Cooling FTXM25QVMA with operation mode, temp, fan swing (3d, horizontal, vertical) which is powered by the [DAIKIN Mobile Controller](https://itunes.apple.com/au/app/daikin-mobile-controller/id917168708?mt=8) ([Android version](https://play.google.com/store/apps/details?id=eu.daikin.remoapp)) application.
|
||||
- The Australian version of the Daikin Wifi Controller for **AirBase** units (BRP15B61), which is powered by the [Daikin Airbase](https://play.google.com/store/apps/details?id=au.com.daikin.airbase) application.
|
||||
|
||||
|
||||
29
source/_components/device_automation.markdown
Normal file
29
source/_components/device_automation.markdown
Normal file
@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "Device Automation"
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Automation
|
||||
ha_qa_scale: internal
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
Device Automations is a plugin for the automation integration to allow other integrations to provide device specific triggers, conditions and actions.
|
||||
|
||||
There is no device automation specific configuration. Instead, it is configured as part of the normal automations.
|
||||
|
||||
Device automations are meant to be configured via the UI.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
- id: "123456789"
|
||||
alias: Light turns off
|
||||
trigger:
|
||||
- platform: device
|
||||
device_id: 7a92d5ee74014a0b86903fc669b0bcd6
|
||||
domain: light
|
||||
type: turn_off
|
||||
entity_id: light.bowl
|
||||
action:
|
||||
- service: camera.turn_off
|
||||
```
|
||||
@ -84,8 +84,23 @@ Field | Description
|
||||
`key` | the code of the pressed key when the command `type` is `keypress`, `keyup` or `keydown`.
|
||||
`app_id` | the id of the app that was launched when command `type` is `launch`.
|
||||
|
||||
The available keys are listed here:
|
||||
[Roku key codes](https://sdkdocs.roku.com/display/sdkdoc/External+Control+API#ExternalControlAPI-KeypressKeyValues)
|
||||
Available key codes |
|
||||
------------------- |
|
||||
`Home`
|
||||
`Rev`
|
||||
`Fwd`
|
||||
`Play`
|
||||
`Select`
|
||||
`Left`
|
||||
`Right`
|
||||
`Down`
|
||||
`Up`
|
||||
`Back`
|
||||
`InstantReplay`
|
||||
`Info`
|
||||
`Backspace`
|
||||
`Search`
|
||||
`Enter`
|
||||
|
||||
## Automations
|
||||
|
||||
|
||||
@ -249,7 +249,7 @@ The request_sync service may fail with a 404 if the project_id of the Homegraph
|
||||
4. Generate a new API key.
|
||||
5. Again, create a new project in the [Actions on Google console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`.
|
||||
|
||||
Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again.
|
||||
Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again. If regenerating the draft does not work, go back to the `Action` section and just hit the `enter` key for the URL to recreate the Preview.
|
||||
|
||||
### Troubleshooting with NGINX
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ redirect_from:
|
||||
- /components/google/
|
||||
---
|
||||
|
||||
The `google_translate` text-to-speech platform uses unofficial [Google Translate Text-to-Speech engine](https://translate.google.com/) to read a text with natural sounding voices.
|
||||
The `google_translate` text-to-speech platform uses the unofficial [Google Translate Text-to-Speech engine](https://translate.google.com/) to read a text with natural sounding voices.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -93,9 +93,8 @@ havdalah_minutes_after_sunset:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: jewish_calendar
|
||||
language: english
|
||||
diaspora: true
|
||||
havdalah_minutes_after_sunset: 50
|
||||
jewish_calendar:
|
||||
language: english
|
||||
diaspora: true
|
||||
havdalah_minutes_after_sunset: 50
|
||||
```
|
||||
|
||||
@ -86,7 +86,7 @@ Template Light may get an `unknown` state during startup. This results
|
||||
in error messages in your log file until that platform has completed loading.
|
||||
If you use `is_state()` function in your template, you can avoid this situation.
|
||||
For example, you would replace
|
||||
{% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}
|
||||
{% raw %}`{{ states.switch.source.state == 'on' }}`{% endraw %}
|
||||
with this equivalent that returns `true`/`false` and never gives an unknown
|
||||
result:
|
||||
{% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}
|
||||
|
||||
@ -36,6 +36,7 @@ password:
|
||||
default: admin
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
The following is a list of expected sensors and their expected states:
|
||||
|
||||
- Obihai service status (`Normal`, `Down` or other states from Obihais network)
|
||||
@ -44,3 +45,4 @@ The following is a list of expected sensors and their expected states:
|
||||
- Sensor if the device requires a reboot (`True` or `False`)
|
||||
- Sensor for each configured service (`0` for no calls, `1` for a call and `2` for call waiting/3way calling)
|
||||
- Sensor for the last reboot date
|
||||
|
||||
|
||||
@ -10,8 +10,8 @@ redirect_from:
|
||||
- /components/media_player.onkyo/
|
||||
---
|
||||
|
||||
|
||||
The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/) and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant. Please be aware that you need to enable "Network Standby" for this integration to work in your Hardware.
|
||||
The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/), [Integra](http://www.integrahometheater.com/)
|
||||
and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant. Please be aware that you need to enable "Network Standby" for this integration to work in your Hardware.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ sensor:
|
||||
garage_car_present:
|
||||
friendly_name: 'Honda in Garage'
|
||||
value_template: {% raw %}'{% if states.cover.honda %}
|
||||
{% if is_state('cover.honda', 'open') %}
|
||||
{% if is_state("cover.honda", "open") %}
|
||||
n/a
|
||||
{% elif ((states.cover.honda.attributes["distance_sensor"] > 40) and (states.cover.honda.attributes["distance_sensor"] < 100)) %}
|
||||
Yes
|
||||
|
||||
@ -10,11 +10,11 @@ redirect_from:
|
||||
- /components/sensor.pi_hole/
|
||||
---
|
||||
|
||||
The `pi_hole` integration allows you to retrieve and display statistics from a [Pi-hole](https://pi-hole.net/) system.
|
||||
The `pi_hole` integration allows you to retrieve and display statistics from a single [Pi-hole](https://pi-hole.net/) system.
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file for a GET request:
|
||||
To enable this integration with the default configuration, add the following lines to your `configuration.yaml` file
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -23,10 +23,15 @@ pi_hole:
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: IP address of the host where Pi-hole is running.
|
||||
description: >
|
||||
The hostname (and port), e.g. '192.168.0.3:4685' of the host where Pi-hole is running.
|
||||
|
||||
|
||||
**Note:** If your Pi-Hole instance is the Hass.io add-on, you *must* specify port `4685`.
|
||||
required: false
|
||||
type: string
|
||||
default: pi.hole
|
||||
|
||||
location:
|
||||
description: The installation location of the Pi-hole API.
|
||||
required: false
|
||||
@ -49,10 +54,9 @@ verify_ssl:
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
pi_hole:
|
||||
host: IP_ADDRESS
|
||||
|
||||
sensor:
|
||||
- platform: pi_hole
|
||||
host: 'localhost:4685'
|
||||
ssl: false
|
||||
verify_ssl: false
|
||||
```
|
||||
|
||||
This integration was not made by Pi-hole LLC or the Pi-hole community. They did not provide support, feedback, testing, or any other help during its creation. This is a third party platform which may break if Pi-hole changes their API in a later release. It is not official, not developed, not supported, and not endorsed Pi-hole LLC or the Pi-hole community. The trademark `Pi-hole` and the logo is used here to describe the platform. `Pi-hole` is a registered trademark of Pi-hole LLC.
|
||||
|
||||
@ -41,16 +41,11 @@ The `plex` integration can also be configured via `configuration.yaml`:
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
plex:
|
||||
token: MYSECRETTOKEN
|
||||
token: MYSECRETTOKEN
|
||||
```
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
At least one of `host` or `token` must be provided.
|
||||
|
||||
</div>
|
||||
<div class='note warning'>
|
||||
|
||||
Only one Plex server can be configured when using `configuration.yaml`. To add more servers, set up via **Configuration** -> **Integrations**.
|
||||
|
||||
</div>
|
||||
@ -103,14 +98,14 @@ media_player:
|
||||
```yaml
|
||||
# Complete configuration.yaml entry
|
||||
plex:
|
||||
host: 192.168.1.100
|
||||
port: 32400
|
||||
token: MY_SECRET_TOKEN
|
||||
ssl: true
|
||||
verify_ssl: true
|
||||
media_player:
|
||||
use_episode_art: true
|
||||
show_all_controls: false
|
||||
host: 192.168.1.100
|
||||
port: 32400
|
||||
token: MY_SECRET_TOKEN
|
||||
ssl: true
|
||||
verify_ssl: true
|
||||
media_player:
|
||||
use_episode_art: true
|
||||
show_all_controls: false
|
||||
```
|
||||
|
||||
## Media Player
|
||||
|
||||
@ -15,17 +15,17 @@ You can create scenes that capture the states you want certain entities to be. F
|
||||
scene:
|
||||
- name: Romantic
|
||||
entities:
|
||||
light.tv_back_light: true
|
||||
light.tv_back_light: on
|
||||
light.ceiling:
|
||||
state: true
|
||||
state: on
|
||||
xy_color: [0.33, 0.66]
|
||||
brightness: 200
|
||||
- name: Movies
|
||||
entities:
|
||||
light.tv_back_light:
|
||||
state: true
|
||||
state: on
|
||||
brightness: 100
|
||||
light.ceiling: false
|
||||
light.ceiling: off
|
||||
media_player.sony_bravia_tv:
|
||||
source: HDMI 1
|
||||
```
|
||||
@ -46,8 +46,6 @@ As you can see, there are two ways to define the states of each `entity_id`:
|
||||
- Define the `state` directly with the entity.
|
||||
- Define a complex state with its attributes.
|
||||
|
||||
The mapping from states to services is done with the [state helper](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/state.py#L82). So, please have a look there for available states for your scenes.
|
||||
|
||||
Scenes can be activated using the service `scene.turn_on` (there is no 'scene.turn_off' service).
|
||||
|
||||
```yaml
|
||||
@ -63,7 +61,3 @@ automation:
|
||||
service: scene.turn_on
|
||||
entity_id: scene.romantic
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
Please note that the scene integration for the most part only supports one service call per entity to achieve the state. Due to this limitation, you cannot set states belonging to different services. A workaround for this limitation is to write a script, which you then turn on in your scene. A few integrations have direct support for multiple service calls per state, Currently this is the media_player and climate components.
|
||||
</div>
|
||||
|
||||
@ -88,7 +88,7 @@ sensor:
|
||||
|
||||
### Startup
|
||||
|
||||
If you are using the state of a platform that takes extra time to load, the Template Sensor may get an `unknown` state during startup. To avoid this (and the resulting error messages in your log file), you can use `is_state()` function in your template. For example, you would replace {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an `unknown` result:
|
||||
If you are using the state of a platform that takes extra time to load, the Template Sensor may get an `unknown` state during startup. To avoid this (and the resulting error messages in your log file), you can use `is_state()` function in your template. For example, you would replace {% raw %}`{{ states.cover.source.state == 'open' }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an `unknown` result:
|
||||
|
||||
{% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ tuya:
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
description: Your username to log in to Tuya. This may be your phone number.
|
||||
description: Your username to log in to Tuya. This may be your phone number which needs to be enquoted as this is a string.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
@ -53,7 +53,7 @@ password:
|
||||
required: true
|
||||
type: string
|
||||
country_code:
|
||||
description: "Your account [country code](https://www.countrycode.org/), e.g., 1 for USA or 86 for China."
|
||||
description: "Your account [country code](https://www.countrycode.org/), e.g., 1 for USA or 86 for China, again enquoted."
|
||||
required: true
|
||||
type: string
|
||||
platform:
|
||||
|
||||
@ -3,7 +3,7 @@ title: "Updater"
|
||||
description: "Detecting when Home Assistant updates are available."
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- binary_sensor
|
||||
- Binary Sensor
|
||||
ha_qa_scale: internal
|
||||
ha_release: 0.8
|
||||
---
|
||||
|
||||
@ -40,8 +40,8 @@ To use this integration, all devices must be registered with the VeSync App. Onc
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
vesync:
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
|
||||
@ -53,12 +53,9 @@ The `wake_on_lan` (WOL) switch platform allows you to turn on a [WOL](https://en
|
||||
|
||||
### Switch configuration
|
||||
|
||||
<div class='note warning'>
|
||||
The WOL switch can only turn on your computer and monitor the state. There is no universal way to turn off a computer remotely. The `turn_off` variable is there to help you call a script when you have figured out how to remotely turn off your computer. See below for suggestions on how to do this.
|
||||
|
||||
The WOL switch can only turn on your computer and monitor the state. There is no universal way to turn off a computer remotely. The `turn_off` variable is there to help you call a script when you have figured out how to remotely turn off your computer.
|
||||
See below for suggestions on how to do this.
|
||||
|
||||
</div>
|
||||
It's required that the binary `ping` is in your `$PATH`.
|
||||
|
||||
To enable this switch in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -103,12 +100,12 @@ Here are some real-life examples of how to use the **turn_off** variable.
|
||||
Suggested recipe for letting the `turn_off` script suspend a Linux computer (the **target**)
|
||||
from Home Assistant running on another Linux computer (the **server**).
|
||||
|
||||
1. On the **server**, log in as the user account Home Assistant is running under. (I'm using `hass` in this example)
|
||||
2. On the **server**, create ssh keys by running `ssh-keygen`. Just press enter on all questions.
|
||||
3. On the **target**, create a new account that Home Assistant can ssh into: `sudo adduser hass`. Just press enter on all questions except password. I recommend using the same user name as on the server. If you do, you can leave out `hass@` in the ssh commands below.
|
||||
4. On the **server**, transfer your public ssh key by `ssh-copy-id hass@TARGET` where TARGET is your target machine's name or IP address. Enter the password you created in step 3.
|
||||
1. On the **server**, log in as the user account Home Assistant is running under. In this exampleit's `hass`.
|
||||
2. On the **server**, create SSH keys by running `ssh-keygen`. Just press enter on all questions.
|
||||
3. On the **target**, create a new account that Home Assistant can ssh into: `sudo adduser hass`. Just press enter on all questions except password. It's recommended using the same user name as on the server. If you do, you can leave out `hass@` in the SSH commands below.
|
||||
4. On the **server**, transfer your public SSH key by `ssh-copy-id hass@TARGET` where TARGET is your target machine's name or IP address. Enter the password you created in step 3.
|
||||
5. On the **server**, verify that you can reach your target machine without password by `ssh TARGET`.
|
||||
6. On the **target**, we need to let the hass user execute the program needed to suspend/shut down the target computer. I'm using `pm-suspend`, use `poweroff` to turn off the computer. First, get the full path: `which pm-suspend`. On my system, this is `/usr/sbin/pm-suspend`.
|
||||
6. On the **target**, we need to let the `hass` user execute the program needed to suspend/shut down the target computer. Here is it `pm-suspend`, use `poweroff` to turn off the computer. First, get the full path: `which pm-suspend`. On my system, this is `/usr/sbin/pm-suspend`.
|
||||
7. On the **target**, using an account with sudo access (typically your main account), `sudo visudo`. Add this line last in the file: `hass ALL=NOPASSWD:/usr/sbin/pm-suspend`, where you replace `hass` with the name of your user on the target, if different, and `/usr/sbin/pm-suspend` with the command of your choice, if different.
|
||||
8. On the **server**, add the following to your configuration, replacing TARGET with the target's name:
|
||||
|
||||
@ -122,4 +119,4 @@ switch:
|
||||
|
||||
shell_command:
|
||||
turn_off_TARGET: 'ssh hass@TARGET sudo pm-suspend'
|
||||
```
|
||||
```
|
||||
|
||||
@ -122,3 +122,10 @@ sensor:
|
||||
vehicle_type: motorcycle # vehicle type used for route
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## Using the live map in a iFrame
|
||||
|
||||
If you plan to use [Waze's live map](https://developers.google.com/waze/iframe/)
|
||||
in Lovelace [iframe](/lovelace/iframe/) then use
|
||||
[https://embed.waze.com/iframe](https://embed.waze.com/iframe) and not the live map URL itself.
|
||||
|
||||
|
||||
@ -47,14 +47,17 @@ password:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
To enable local push notifications from the Tags Manager, you need to add the IP address of the Tags Manager into whitelist in `http` component; i.e., add it to `trusted_networks`. See the [HTTP](/components/http/) for details.
|
||||
Additionally, you need add at least one [WirelessTag binary sensor](#binary-sensor) in config to start receiving local push notifications.
|
||||
To enable local push notifications from the Tags Manager, you need to add the IP address of the Tags Manager into `trusted_networks` under Authentication Providers. See the [Authentication Providers](https://www.home-assistant.io/docs/authentication/providers/#trusted-networks) for details.
|
||||
|
||||
If you are using a version prior to v0.89 you can do the whitelisting under the [HTTP](/components/http) integration.
|
||||
|
||||
Additionally, you need to add at least one [WirelessTag binary sensor](#binary-sensor) in the configuration to start receiving local push notifications.
|
||||
|
||||
</div>
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Tags Manager supports local push notifications for `http` schema only. So if your hass uses `https`, local push notifications are disabled and data is received via cloud polling.
|
||||
Tags Manager supports local push notifications for `http` schema only. So if your Home Assistant uses `https`, local push notifications are disabled and data is received via cloud polling.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -1,48 +1,48 @@
|
||||
- topic: Platform
|
||||
description: "[Platforms](/docs/configuration/platform_options/) make the connection to a specific software or hardware platform. For example, the `pushbullet` platform works with the service pushbullet.com to send notifications."
|
||||
- topic: Component
|
||||
description: "[Components](/docs/configuration/platform_options/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
|
||||
- topic: Condition
|
||||
description: "[Conditions](/docs/scripts/conditions/) are an optional part of an automation that will prevent an action from firing if they are not met."
|
||||
- topic: Service
|
||||
description: "[Services](/docs/scripts/service-calls/) are called to perform actions."
|
||||
- topic: Action
|
||||
description: "[Actions](/docs/automation/action/) are events that fires once all triggers and conditions have been met."
|
||||
- topic: Event
|
||||
description: "An [event](/docs/configuration/events/) is when something happens."
|
||||
- topic: Entity
|
||||
description: "An [entity](/docs/configuration/platform_options/) is the representation of a single device, unit or web service."
|
||||
- topic: Device
|
||||
description: "A device is usually a physical unit which can do or observe something."
|
||||
- topic: Hassbian
|
||||
description: "[Hassbian](/docs/installation/hassbian/) is a customized operating system specifically tailored for Raspberry Pi users. It is one of the easiest way of installing and running Home Assistant on a Raspberry Pi."
|
||||
- topic: Discovery
|
||||
description: "[Discovery](/components/discovery/) is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered."
|
||||
- topic: Group
|
||||
description: "[Groups](/components/group/) are a way to organize your entities into a single unit."
|
||||
- topic: Automation
|
||||
description: "[Automations](/docs/automation/) offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as sunset to cause an event, such as a light turning on."
|
||||
- topic: Trigger
|
||||
description: "A [trigger](/docs/automation/trigger/) is a set of values or conditions of a platform that are defined to cause an automation to run."
|
||||
- topic: Template
|
||||
description: "A [template](/docs/automation/templating/) is an automation definition that can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions."
|
||||
- topic: Script
|
||||
description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on."
|
||||
- topic: Scene
|
||||
description: "[Scenes](/components/scene/) capture the states you want certain entities to be. For example a scene can specify that light A should be turned on and light B should be bright red."
|
||||
- topic: HADashboard
|
||||
description: "[HADashboard](/docs/ecosystem/hadashboard/) is a modular, skinnable dashboard for Home Assistant that is intended to be wall mounted, and is optimized for distance viewing."
|
||||
- topic: hass
|
||||
description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is also the command line tool."
|
||||
- topic: Hass.io
|
||||
description: "[Hass.io](/hassio/) is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration, and can easily be extended."
|
||||
description: "[Automations](/docs/automation/) offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as a sunset to cause an event, such as a light turning on."
|
||||
- topic: Component
|
||||
description: "Integrations (see below) used to be known as components."
|
||||
- topic: Condition
|
||||
description: "[Conditions](/docs/scripts/conditions/) are an optional part of an automation that will prevent an action from firing if they are not met."
|
||||
- topic: Cookbook
|
||||
description: "The [Cookbook](/cookbook/) contains a set of configuration examples of Home Assistant from the community."
|
||||
- topic: Packages
|
||||
description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configurations together."
|
||||
- topic: Customize
|
||||
description: "[Customization](/docs/configuration/customizing-devices/) allows you to overwrite the default parameter of your devices in the configuration."
|
||||
- topic: Zone
|
||||
description: "[Zones](/components/zone/) are areas that can be used for presence detection."
|
||||
- topic: Device
|
||||
description: "A device is usually a physical unit which can do or observe something."
|
||||
- topic: Discovery
|
||||
description: "[Discovery](/components/discovery/) is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered."
|
||||
- topic: Entity
|
||||
description: "An [entity](/docs/configuration/platform_options/) is the representation of function a single device, unit, or web service. There may be multiple entities for a single device, unit, or web service, or there may be only one."
|
||||
- topic: Event
|
||||
description: "An [event](/docs/configuration/events/) is when something happens."
|
||||
- topic: Frontend
|
||||
description: "The [frontend](/components/frontend/) is a necessary component for the UI, it is also where you can define your themes."
|
||||
- topic: Group
|
||||
description: "[Groups](/components/group/) are a way to organize your entities into a single unit."
|
||||
- topic: hass
|
||||
description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is also the command-line tool."
|
||||
- topic: Hass.io
|
||||
description: "[Hass.io](/hassio/) is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration, and can easily be extended."
|
||||
- topic: Integration
|
||||
description: "[Integrations](/components/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
|
||||
- topic: Lovelace
|
||||
description: "[Lovelace](/lovelace/) is the name of the current frontend."
|
||||
- topic: Packages
|
||||
description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configurations together."
|
||||
- topic: Platform
|
||||
description: "[Platforms](/docs/configuration/platform_options/) make the connection to a specific software or hardware platform. For example, the `pushbullet` platform works with the service pushbullet.com to send notifications."
|
||||
- topic: Scene
|
||||
description: "[Scenes](/components/scene/) capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red."
|
||||
- topic: Script
|
||||
description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on."
|
||||
- topic: Service
|
||||
description: "[Services](/docs/scripts/service-calls/) are called to perform actions."
|
||||
- topic: Template
|
||||
description: "A [template](/docs/automation/templating/) is an automation definition that can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions."
|
||||
- topic: Trigger
|
||||
description: "A [trigger](/docs/automation/trigger/) is a set of values or conditions of a platform that are defined to cause an automation to run."
|
||||
- topic: Zone
|
||||
description: "[Zones](/components/zone/) are areas that can be used for presence detection."
|
||||
|
||||
@ -234,8 +234,8 @@ Although the actual amount of light depends on weather, topography and land cove
|
||||
|
||||
This is what is meant by twilight for the average person: Under clear weather conditions, civil twilight approximates the limit at which solar illumination suffices for the human eye to clearly distinguish terrestrial objects. Enough illumination renders artificial sources unnecessary for most outdoor activities.
|
||||
|
||||
- Nautical twilight: 6° > Solar angle > -12°
|
||||
- Astronomical twilight: 12° > Solar angle > -18°
|
||||
- Nautical twilight: -6° > Solar angle > -12°
|
||||
- Astronomical twilight: -12° > Solar angle > -18°
|
||||
|
||||
A very thorough explanation of this is available in the Wikipedia article about the [Twilight](https://en.wikipedia.org/wiki/Twilight).
|
||||
|
||||
|
||||
@ -58,7 +58,7 @@ entity_picture:
|
||||
required: false
|
||||
type: string
|
||||
icon:
|
||||
description: "Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://cdn.materialdesignicons.com/3.5.95/)). Prefix name with `mdi:`, ie `mdi:home`. Note: Newer icons may not yet be available in the current Home Assistant release. You can check when an icon was added to MaterialDesignIcons.com at [MDI History](https://materialdesignicons.com/history)."
|
||||
description: "Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://cdn.materialdesignicons.com/4.4.95/)). Prefix name with `mdi:`, ie `mdi:home`. Note: Newer icons may not yet be available in the current Home Assistant release. You can check when an icon was added to MaterialDesignIcons.com at [MDI History](https://materialdesignicons.com/history)."
|
||||
required: false
|
||||
type: string
|
||||
assumed_state:
|
||||
|
||||
@ -6,10 +6,6 @@ redirect_from: /topics/packages/
|
||||
|
||||
Packages in Home Assistant provide a way to bundle different component's configuration together. We already learned about the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the integration key in the main `configuration.yaml` file. With packages we have a way to include different components, or different configuration parts using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
|
||||
|
||||
<div class='note tip'>
|
||||
Note that if you use packages for your configuration, the configuration reloading buttons in the configuration panel will not reload your packages.
|
||||
</div>
|
||||
|
||||
Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a package name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -16,7 +16,7 @@ mqtt:
|
||||
|
||||
{% configuration %}
|
||||
certificate:
|
||||
description: "'auto' or the certificate authority certificate file that is to be treated as trusted by this client. 'auto' uses the bundled certificates. If a file is specified the file should contain the root certificate of the certificate authority that signed your broker's certificate, but may contain multiple certificates. Example: `/home/user/identrust-root.pem`"
|
||||
description: "'auto' or the certificate authority certificate file that is to be treated as trusted by this client. To enable a secure (TLS) connection to your server you must define the 'certitificate' configuration parameter. 'auto' uses the certifite CAs bundled certificates. If a file is specified the file should contain the root certificate of the certificate authority that signed your broker's certificate, but may contain multiple certificates. Example: `/home/user/identrust-root.pem`."
|
||||
required: false
|
||||
type: string
|
||||
client_key:
|
||||
|
||||
@ -21,7 +21,7 @@ Screenshot of Home Assistant's Developer Tools.
|
||||
## What can I do with Developer Tools?
|
||||
The Developer Tools is meant for **all** (not just for the developers) to quickly try out things - like calling services, update states, raising events, and publish messages in mqtt…etc.). It is also a necessary tool for those who write custom automations and scripts by hand. The following describes each of the section in detail.
|
||||
|
||||
Services
|
||||
## Services
|
||||
|
||||
This section is used to call Services that are available in the ServiceRegistry.
|
||||
|
||||
@ -45,7 +45,7 @@ To turn on a light bulb, use the following steps:
|
||||
"rgb_color": [255, 0, 0]
|
||||
}
|
||||
```
|
||||
States
|
||||
## States
|
||||
|
||||
This section shows all the available entities, their corresponding state and the attribute values. The state and the attribute information is what Home Assistant sees at run time. To update the entity with a new state, or a new attribute value, click on the entity, scroll to the top, and modify the values, and click on “SET STATE” button.
|
||||
|
||||
@ -53,7 +53,7 @@ Note that this is the state representation of a device within Home Assistant. Th
|
||||
|
||||
For ex: Changing the `light.bedroom` state from `off` to `on` does not turn on the light. If there is an automation that triggers on the `state` change of the `light.bedroom`, it will be triggered – even though the actual bulb has not turned on. Also, when the bulb state changes – the state information will be overridden. In other words, the changes that are made through the “States” section are temporary, and is recommended to use for testing purposes only.
|
||||
|
||||
Events
|
||||
## Events
|
||||
|
||||
This Events section is as basic as it can get. It does only one thing – fires events on the event bus.
|
||||
To fire an event, simply type the name of the event, and pass the event data in JSON format.
|
||||
@ -75,7 +75,7 @@ If there is an automation that handles that event, it will be automatically trig
|
||||
message: "Light is turned {{ trigger.event.data.state }}"
|
||||
```
|
||||
|
||||
Template Editor
|
||||
## Template Editor
|
||||
|
||||
The Template Editor provides a way to test the template code quickly. When the Template Editor page is loaded, it comes with a sample template code that illustrates how the code can be written and tested.
|
||||
|
||||
@ -86,12 +86,12 @@ It is a good practice to test the template code in the template editor prior to
|
||||
For more information about jinja2, visit [jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/)
|
||||
|
||||
|
||||
mqtt
|
||||
## MQTT
|
||||
|
||||
This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [mqtt](/components/mqtt/) component.
|
||||
|
||||
Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button.
|
||||
|
||||
Info
|
||||
## Info
|
||||
|
||||
The Information tab simply provides information about the current installed version, additional links and credits. The tab also contains a section that shows `syslog` information, and the contents of `home-assistant.log` with an option to clear and refresh the logs.
|
||||
|
||||
@ -34,6 +34,7 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
|
||||
- [Vera](/components/vera/)
|
||||
- [Wink](/components/wink/)
|
||||
- [Fibaro](/components/fibaro/)
|
||||
- [SmartThings](/components/smartthings/)
|
||||
|
||||
## Controller Notes
|
||||
|
||||
|
||||
@ -67,6 +67,6 @@ card:
|
||||
- {{ l.entity }}
|
||||
{%- endfor %}
|
||||
|
||||
And the door is {% if is_state('binary_sensor.door', 'on' %} open {% else %} closed {% endif %}.
|
||||
And the door is {% if is_state('binary_sensor.door', 'on') %} open {% else %} closed {% endif %}.
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
74
source/_posts/2019-09-17-happy-birthday.markdown
Normal file
74
source/_posts/2019-09-17-happy-birthday.markdown
Normal file
@ -0,0 +1,74 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Happy 6th Birthday"
|
||||
description: "Thank you community for making Home Assistant a special place."
|
||||
date: 2019-09-17 01:11:03
|
||||
date_formatted: "September 17, 2019"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Announcements
|
||||
og_image: /images/blog/2019-09-birthday/social.png
|
||||
---
|
||||
|
||||
<img src='/images/blog/2019-09-birthday/top.png' style='border: 0;box-shadow: none;'>
|
||||
|
||||
### Dear community, happy sixth birthday.
|
||||
|
||||
#### It has been six amazing years
|
||||
|
||||
Thanks to all the people working on the core of Home Assistant.
|
||||
|
||||
Thanks to all the people working on the Home Assistant frontend.
|
||||
|
||||
Thanks to all the people working on Hass.io.
|
||||
|
||||
Thanks to all the people workin on the mobile apps.
|
||||
|
||||
Thanks to all the people working on Hass.io add-ons.
|
||||
|
||||
Thanks to all the people who help with design and user stories.
|
||||
|
||||
Thanks to all the people who make the documentation possible.
|
||||
|
||||
Thanks to all the people active on the forums.
|
||||
|
||||
Thanks to all the people active in the chat rooms.
|
||||
|
||||
Thanks to all the people active on social media.
|
||||
|
||||
Thanks to all the people making videos helping people use Home Assistant.
|
||||
|
||||
Thanks to all the people making videos sharing their achievements using Home Assistant.
|
||||
|
||||
Thanks to all the people writing blog posts about Home Assistant.
|
||||
|
||||
Thanks to all the people invovled in making the Home Asssistant Podcast.
|
||||
|
||||
Thanks to all the people moderating our community, maintaining its high quality.
|
||||
|
||||
Thanks to all the people working on running our infrastructure.
|
||||
|
||||
Thanks to all the people who help out with code reviews and maintaining our code quality.
|
||||
|
||||
Thanks to all the people building and sharing cool frontends build with Lovelace.
|
||||
|
||||
Thanks to all the people creating and sharing custom Lovelace cards.
|
||||
|
||||
Thanks to all the people creating and sharing custom components.
|
||||
|
||||
Thanks to all the manufacturers that work on integrating with Home Assistant.
|
||||
|
||||
Thanks to all the companies providing the Home Assistant project with resources: Nabu Casa, GitHub/Azure/Microsoft, CloudFlare, Netlify, Lokalise.co, CARTO.
|
||||
|
||||
Thanks to the Material Design Icons team for beautiful icons.
|
||||
|
||||
Thanks to all the people who support Home Assistant by subscribing to Home Assistant Cloud.
|
||||
|
||||
Thanks to all the people who share the Home Assistant love.
|
||||
|
||||
Thanks.
|
||||
|
||||
❤️
|
||||
|
||||
Paulus
|
||||
799
source/_posts/2019-09-18-release-99.markdown
Normal file
799
source/_posts/2019-09-18-release-99.markdown
Normal file
@ -0,0 +1,799 @@
|
||||
---
|
||||
layout: post
|
||||
title: "0.99: Withings, Device Automations, launch Home Assistant Cast from Python."
|
||||
description: "11 new integrations, many tweaks/features for the frontend and easier automations for everyone."
|
||||
date: 2019-09-18 01:11:03
|
||||
date_formatted: "September 18, 2019"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2019-09-0.99/components.png
|
||||
---
|
||||
|
||||
<a href='/components/#version/0.99'><img src='/images/blog/2019-09-0.99/components.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
[Happy 6th birthday to us!](/blog/2019/09/17/happy-birthday/) Yep, it's been 6 years since the first commit, 6 years since we started our quest for a local and privacy foucsed home automation hub. And I think that we're doing a pretty ok job 😏
|
||||
|
||||
It’s time for Home Assistant release 99. And this release is adding a bunch of new great features all over the place.
|
||||
|
||||
## Welcome Bram!
|
||||
|
||||
[Nabu Casa](https://www.nabucasa.com/) has hired [Bram Kragten][@bramkragten]. Bram has been active in the Home Assistant community for a while and is one of the driving forces behind the Lovelace UI. He will work on the Home Assistant frontend full-time. He will focus on making it easier to manage your Home Assistant installation, make sure all of the frontend is translatable and drive our efforts on making the frontend accessible for visually impaired people.
|
||||
|
||||
This is possible thanks to all the people who subscribe to Home Assistant Cloud ❤️
|
||||
|
||||
## Device Automations
|
||||
|
||||
We took a step back, looked at Home Assistant, and thought about how we could make it easier for users to create automations. We realized that there was room for improvement. We identified the following issues:
|
||||
|
||||
- To write automations, users need to learn Home Assistant concepts like events, entities and services.
|
||||
- It's difficult to discover what can be automated. For example, if you’re automating a long press on the "turn on" button on a Zigbee remote, you need to know to listen to the event “zha_event” and match against the Zigbee device identifier of your remote and the long press type.
|
||||
|
||||
So we put our inventor hat on and have come up with a solution that allows users to create automations in the concepts that they already know: devices. Now when a user starts configuring an automation trigger, it can pick device automation as a new type.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2019-09-0.99/device-automation-trigger.png' alt="Screenshot of defining a device trigger.">
|
||||
Screenshot of defining a device trigger in the UI.
|
||||
</p>
|
||||
|
||||
The user starts by picking one of their devices that is integrated into Home Assistant. A second dropdown will now appear that contains all the possible triggers for this device. This list is populated based on the integrations that are linked to this device (ie. Hue & Light).
|
||||
|
||||
Device automations are available for triggers, conditions and actions. Today’s release supports lights, switches and Deconz. More to come in future releases as integration developers adopt it.
|
||||
|
||||
Big thanks to [@emontomery] for driving this effort. He added initial support for device automations as a YAML-only feature in Home Assistant 0.97 and has worked hard to extend it in this release with UI support and support for conditions, actions and more integrations. Also a big thanks to [@kane610] who added added support for device automations to Deconz which helped squash bugs and improve the design.
|
||||
|
||||
## Frontend
|
||||
|
||||
There is a lot to talk here. Buckle up.
|
||||
|
||||
[@thomasloven] has built a brand new round slider from scratch for use in Home Assistant. It is using modern technologies to create a great experience. This component was so useful standalone that he has decided to release it as [a standalone web component](https://github.com/thomasloven/round-slider/) that anyone can use in their websites.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2019-09-0.99/round-slider.png' alt="Screenshot of a light card showing a round slider.">
|
||||
</p>
|
||||
|
||||
Shout out to [@iantrich] who has been on fire in recent weeks squashing a ton of bugs and adding some nice features to improve the Lovelace experience. And a shout out to [@SeanPM5] who has been bringing UX bugs and improvements to our attention. Our frontend team is seriously awesome.
|
||||
|
||||
Unused entities has been moved into the configure UI section and completely revamped by [@bramkragten]. It's now a table, you can see a lot more info, you can sort it. If you are using Lovelace storage mode, you can select entities and add them to your UI directly from that screen.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2019-09-0.99/unused-entities.png' alt="Screenshot of the new unused entities page.">
|
||||
Screenshot of the new unused entities page.
|
||||
</p>
|
||||
|
||||
Now that we have a data table component, Bram also went ahead and used it in a new devices page. This page, still experimental, will allow users to see a list of all their devices and sort them by manufacturer, area or battery %. The goal is to create a one stop shop for device management.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2019-09-0.99/devices.png' alt="Screenshot of the new devices page.">
|
||||
Screenshot of the new devices page.
|
||||
</p>
|
||||
|
||||
And there is a ton more, here are some of the other highlights:
|
||||
|
||||
- Allow subscribing to an MQTT topic inside the MQTT dev tools [@bramkragten]
|
||||
- Option to display last changed in glance-card [@iantrich]
|
||||
- Add image option to glance card entities [@iantrich]
|
||||
- Allow controlling timer entities from the more info dialog [@iantrich]
|
||||
- Fill example data in dev tools [@bramkragten]
|
||||
- Stop effect in more-info-light [@iantrich]
|
||||
- Add vibration on mobile when controlling entities [@bramkragten]
|
||||
- Update Home Assistant logs when activating the info developer tool tab [@bramkragten]
|
||||
|
||||
[@thomasloven]: https://github.com/thomasloven
|
||||
[@iantrich]: https://github.com/iantrich
|
||||
[@emontomery]: https://github.com/emontomery
|
||||
[@seanpm5]: https://github.com/SeanPM5
|
||||
|
||||
## Launch Home Assistant Cast from Python
|
||||
|
||||
Home Assistant now supports opening [Home Assistant Cast](/blog/2019/08/06/home-assistant-cast/) from the backend. It is available as the service `cast.show_lovelace_view`. This allows you to open a view on your Chromecast as part of an automation. For example, show the frontdoor and who is home when your doorbell rings.
|
||||
|
||||
<div class="videoWrapper">
|
||||
<iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/4KMJDOWa_ao" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
Note that Home Assistant Cast requires your Home Assistant installation to be accessible via `https://`. If you're using Home Assistant Cloud, you don't need to do anything. Otherwise you must make sure that you have configured the `base_url` for [the `http` integration](/components/http/).
|
||||
|
||||
## Hass.io
|
||||
|
||||
Hass.io is now able to work with your secrets stored in Home Assistant. So now you are able to use `!secret my_value` inside add-on options like you can do inside `configuration.yaml`. For more info about how to define secrets, [check the docs](/docs/configuration/secrets/).
|
||||
|
||||
We have published a release candidate of HassOS that is compatible with the new Raspberry Pi 4. [Download it here](https://github.com/home-assistant/hassos/releases/tag/3.5).
|
||||
|
||||
## In other news
|
||||
|
||||
Home Assistant had a booth this year at the [CEDIA home tech trade show](https://www.cediaexpo.com/). We spend a lot of time talking to manufacturers about local APIs, official integrations and better support for open source systems.
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Hanging out at <a href="https://twitter.com/CEDIAExpo?ref_src=twsrc%5Etfw">@CEDIAExpo</a> in innovation alley <a href="https://t.co/9SnUXo11oA">pic.twitter.com/9SnUXo11oA</a></p>— Home Assistant (@home_assistant) <a href="https://twitter.com/home_assistant/status/1172559987979292673?ref_src=twsrc%5Etfw">September 13, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
|
||||
|
||||
We also had some great drinks in the evenings with companies that integrate with Home Assistant. In this picture [Konnected.io](/components/konnected) and [Senic](/components/nuimo_controller/).
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Beers after CEDIA with <a href="https://twitter.com/balloob?ref_src=twsrc%5Etfw">@balloob</a> from Home Assistant and teams from Senic and Neeo. <a href="https://t.co/c6Ag4DeEtU">pic.twitter.com/c6Ag4DeEtU</a></p>— Konnected.io (@Konnected_io) <a href="https://twitter.com/Konnected_io/status/1172689994059661318?ref_src=twsrc%5Etfw">September 14, 2019</a>
|
||||
</blockquote>
|
||||
|
||||
[@timmo] has released version 2.0 of his Home Panel. This is an alternative user interface for Home Assistant.
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">It's finally here. 🎉<br><br>Home Panel v2.0.0 is now released and has been completely rewritten in <a href="https://twitter.com/hashtag/React?src=hash&ref_src=twsrc%5Etfw">#React</a> with <a href="https://twitter.com/hashtag/TypeScript?src=hash&ref_src=twsrc%5Etfw">#TypeScript</a><br><br>⚠️Please read the release notes before upgrading as are breaking changes to know about before upgrading!<a href="https://t.co/NMDQu4zZW8">https://t.co/NMDQu4zZW8</a><a href="https://twitter.com/hashtag/HomePanel?src=hash&ref_src=twsrc%5Etfw">#HomePanel</a> <a href="https://twitter.com/hashtag/HomeAssistant?src=hash&ref_src=twsrc%5Etfw">#HomeAssistant</a> <a href="https://t.co/ucA1HxwurB">pic.twitter.com/ucA1HxwurB</a></p>— Timmo (@timmo001) <a href="https://twitter.com/timmo001/status/1172958335982850052?ref_src=twsrc%5Etfw">September 14, 2019</a>
|
||||
</blockquote>
|
||||
|
||||
[@cogneato]: https://github.com/cogneato
|
||||
[@timmo]: https://github.com/timmo001
|
||||
|
||||
## New Integrations
|
||||
|
||||
- Add Withings support ([@vangorra] - [#25154]) ([withings docs]) (new-integration)
|
||||
- Add NWS weather ([@MatthewFlamm] - [#23647]) ([nws docs]) (new-integration)
|
||||
- Add BeeWi SmartClim BLE sensors ([@alemuro] - [#26174]) ([beewi_smartclim docs]) (new-integration)
|
||||
- Add support Slide cover ([@ualex73] - [#25913]) ([slide docs]) (new-integration)
|
||||
- Add atome sensor platform ([@BaQs] - [#26197]) ([atome docs]) (new-integration)
|
||||
- Add Viessmann ViCare Climate platform ([@oischinger] - [#26151]) ([vicare docs]) (new-integration)
|
||||
- Add new integration for Jandy iAqualink pool control ([@flz] - [#26034]) ([iaqualink docs]) (new-integration)
|
||||
- Add vivotek camera component ([@HarlemSquirrel] - [#26071]) ([vivotek docs]) (new-integration)
|
||||
- Add growatt server integration ([@indykoning] - [#25635]) ([growatt_server docs]) (new-integration)
|
||||
- Add Obihai integration ([@dshokouhi] - [#26537]) ([obihai docs]) (new-integration)
|
||||
|
||||
## New Platforms
|
||||
|
||||
- Add support for Supla switches ([@Rocik] - [#26188]) ([supla docs]) (new-platform)
|
||||
- GeoNet NZ Quakes Sensor ([@exxamalte] - [#26078]) ([geonetnz_quakes docs]) (new-platform)
|
||||
- Jewish calendar binary sensor ([@tsvi] - [#26200]) ([jewish_calendar docs]) (breaking change) (new-platform)
|
||||
- Add light platform to iaqualink integration ([@flz] - [#26484]) ([iaqualink docs]) (new-platform)
|
||||
- Add sensor platform to iaqualink component ([@flz] - [#26544]) ([iaqualink docs]) (new-platform)
|
||||
- Add switch platform to iaqualink integration ([@flz] - [#26545]) ([iaqualink docs]) (new-platform)
|
||||
|
||||
## Release 0.99.1 - September 19
|
||||
|
||||
- Encode prometheus metric names per the prom spec ([@growse] - [#26639]) ([prometheus docs])
|
||||
- Bump TRADFRI ([@balloob] - [#26731]) ([tradfri docs])
|
||||
- Bump pyobihai to fix issue with user account ([@dshokouhi] - [#26736]) ([obihai docs])
|
||||
|
||||
[#26639]: https://github.com/home-assistant/home-assistant/pull/26639
|
||||
[#26731]: https://github.com/home-assistant/home-assistant/pull/26731
|
||||
[#26736]: https://github.com/home-assistant/home-assistant/pull/26736
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@dshokouhi]: https://github.com/dshokouhi
|
||||
[@growse]: https://github.com/growse
|
||||
[obihai docs]: /components/obihai/
|
||||
[prometheus docs]: /components/prometheus/
|
||||
[tradfri docs]: /components/tradfri/
|
||||
|
||||
## Release 0.99.2 - September 19
|
||||
|
||||
Forgot to include frontend update 99.1.
|
||||
|
||||
- fix continue integration flow ([#3766](https://github.com/home-assistant/home-assistant-polymer/pull/3766)) [@bramkragten]
|
||||
- Show toast on success save entity settings ([#3763](https://github.com/home-assistant/home-assistant-polymer/pull/3763)) [@bramkragten]
|
||||
- Align behaviour state badge ([#3767](https://github.com/home-assistant/home-assistant-polymer/pull/3767)) [@bramkragten]
|
||||
|
||||
## If you need help...
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
|
||||
|
||||
## Reporting Issues
|
||||
|
||||
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Breaking Changes
|
||||
|
||||
- **Unifi** - Removes support of directly configuring the UniFi platform for device trackers. Use `unifi:` instead. Extra configuration through config entry options from the GUI (see release notes 0.98 for example) and through unifi configuration in configuration.yaml will continue to work.- ([@Kane610] - [#26587]) ([unifi docs])
|
||||
|
||||
```yaml
|
||||
# This will no longer work
|
||||
device_tracker:
|
||||
- platform: unifi
|
||||
|
||||
# This does
|
||||
unifi:
|
||||
```
|
||||
|
||||
- **Plex**
|
||||
|
||||
- Configuration is moved from the media_player and sensor platforms to the plex component. Existing configurations will need to be updated. The `remove_unavailable_clients` and `client_remove_interval` options for media_player entities have been removed as the functionality has limited value now that the entity registry exists. - ([@jjlawren] - [#26488]) ([discovery docs]) ([plex docs])
|
||||
- Logins using a username/password/servername are no longer supported on the Plex sensor platform. This functionality will be partially restored in followup PRs which add a configuration flow and external authentication. - ([@jjlawren] - [#26444]) ([plex docs])
|
||||
- Remove default host for Plex config. - ([@jjlawren] - [#26583]) ([plex docs])
|
||||
- Removes default value of host config parameter.
|
||||
- Requires one of host or token in the configuration.
|
||||
|
||||
New example configuration entry:
|
||||
|
||||
```yaml
|
||||
plex:
|
||||
host: 192.168.1.5
|
||||
token: mysecrettoken
|
||||
media_player:
|
||||
use_episode_art: false
|
||||
```
|
||||
|
||||
- **PiHole** - This change requires existing configurations for the `pi_hole` integration to be moved from sensor platform key to a `pi_hole` top level key. This allows services, switches, and possibly other entities to be added to the integration in a future pull request. - ([@johnluetke] - [#25837]) ([pi_hole docs])
|
||||
|
||||
- `monitored_conditions` is removed
|
||||
- `pi_hole` configuration block defines host, port, location and ssl options
|
||||
|
||||
New example configuration entry:
|
||||
|
||||
```yaml
|
||||
pi_hole:
|
||||
host: pi.hole
|
||||
```
|
||||
|
||||
- **Jewish calendar** - This platform has been moved to an integration. Automations based on `sensor.issur_melacha_in_effect` comparison to `True/False` need to be updated to use `binary_sensor.issur_melacha_in_effect` on and off states. - ([@tsvi] - [#26200]) ([jewish_calendar docs])
|
||||
|
||||
New example configuration entry:
|
||||
|
||||
```yaml
|
||||
jewish_calender:
|
||||
language: hebrew
|
||||
diaspora: False
|
||||
```
|
||||
|
||||
- **Homematic IP** - Unify device_state_attributes handling for Homematic IP Cloud. The naming of entity attributes has been corrected (missing underscore) to follow the standards:
|
||||
|
||||
- moisture detected --> moisture_detected
|
||||
- motion detected --> motion_detected
|
||||
- power mains failure --> power_mains_failure
|
||||
- presence detected --> presence_detected
|
||||
- smoke detector alarm --> smoke_detector_alarm
|
||||
- water level detected --> water_level_detected
|
||||
- window state --> window_state
|
||||
|
||||
([@SukramJ] - [#26449]) ([homematicip_cloud docs])
|
||||
|
||||
- **Linky** - This platform has been moved to an integration. - ([@Quentame] - [#26076]) ([linky docs])
|
||||
|
||||
New example configuration entry:
|
||||
|
||||
```yaml
|
||||
linky:
|
||||
- username: email_address
|
||||
password: password
|
||||
```
|
||||
|
||||
* **Radiotherm** - Update climate attributes. Automations may break if the user is checking against the previous "mode" or "fan" attributes or previous mode or fan attribute values. - ([@dieselrabbit] - [#26465]) ([radiotherm docs])
|
||||
|
||||
- The old "mode" attribute is now supported via "hvac_action" attribute.
|
||||
- The old "fan" attribute now called "fan_action" to follow "hvac_action" .
|
||||
|
||||
* **SolarEdge** - Monitored conditions are no longer supported. - ([@Cereal2nd] - [#26282]) ([solaredge docs])
|
||||
|
||||
- **SMA** - Removes deprecated SMA config - ([@balloob] - [#26306]) ([sma docs])
|
||||
|
||||
## Beta Fixes
|
||||
|
||||
- Fix CCM messages ([@gerard33] - [#26589]) ([bmw_connected_drive docs]) (beta fix)
|
||||
- Update PyChromecast ([@balloob] - [#26594]) ([cast docs]) (beta fix)
|
||||
- Use Nabu Casa url if no https url set ([@balloob] - [#26682]) ([cast docs]) (beta fix)
|
||||
- Updated frontend to 20190917.0 ([@bramkragten] - [#26686]) ([frontend docs]) (beta fix)
|
||||
- Fix Nuki issues ([@pvizeli] - [#26689]) ([nuki docs]) (breaking change) (beta fix)
|
||||
- Bump connect-box library to fix logging ([@pvizeli] - [#26690]) ([upc_connect docs]) (beta fix)
|
||||
- Updated frontend to 20190917.1 ([@bramkragten] - [#26691]) ([frontend docs]) (beta fix)
|
||||
- Rename MockToggleDevice to MockToggleEntity ([@emontnemery] - [#26644]) (beta fix)
|
||||
- Fix translation, adjust trigger names ([@emontnemery] - [#26635]) ([device_automation docs]) ([light docs]) ([switch docs]) (beta fix)
|
||||
- Fix cert expiry config flow check and update ([@Cereal2nd] - [#26638]) ([cert_expiry docs]) (beta fix)
|
||||
- Fix release access for bram ([@pvizeli] - [#26693]) (beta fix)
|
||||
- Updated frontend to 20190917.2 ([@bramkragten] - [#26696]) ([frontend docs]) (beta fix)
|
||||
- Verify withings config ([@balloob] - [#26698]) ([withings docs]) (beta fix)
|
||||
- Updated frontend to 20190918.0 ([@bramkragten] - [#26704]) ([frontend docs]) (beta fix)
|
||||
- Fix yeelight inheritance order ([@zewelor] - [#26706]) ([yeelight docs]) (beta fix)
|
||||
|
||||
## All changes
|
||||
|
||||
- Update azure-pipelines-release.yml for Azure Pipelines ([@pvizeli] - [#26128])
|
||||
- Add myself as codeowner to HmIP Cloud ([@SukramJ] - [#26140]) ([homematicip_cloud docs])
|
||||
- DuckDNS setup backoff ([@kellerza] - [#25899]) ([duckdns docs])
|
||||
- Venstar: define success for all branches of set_temperature() ([@iamtpage] - [#26148]) ([venstar docs])
|
||||
- Add NWS weather ([@MatthewFlamm] - [#23647]) ([nws docs]) (new-integration)
|
||||
- Use literal string interpolation in core (f-strings) ([@frenck] - [#26166])
|
||||
- Allow bumping version for nightly builds ([@balloob] - [#26167])
|
||||
- Update ambiclimate library ([@Danielhiversen] - [#26182]) ([ambiclimate docs])
|
||||
- Refactor open garage ([@Danielhiversen] - [#26179]) ([opengarage docs])
|
||||
- Speed up history `get_states` ([@bramkragten] - [#23881]) ([history docs])
|
||||
- Huawei LTE misc improvements ([@scop] - [#26203]) ([huawei_lte docs])
|
||||
- Nightly builds ([@pvizeli] - [#26204])
|
||||
- Add web socket API command to get a single ZHA device ([@dmulcahey] - [#26196]) ([zha docs])
|
||||
- Update sensor.py ([@newbee112] - [#26218]) ([glances docs])
|
||||
- Support formatting and scaling with ZHA Metering cluster ([@presslab-us] - [#26201]) ([zha docs])
|
||||
- Fix flaky updater tests ([@andrewsayre] - [#26221])
|
||||
- Remove throttle from update ([@michaeldavie] - [#26216]) ([environment_canada docs])
|
||||
- Bump dependency to add PLAY_STATE_STOPPED ([@schmittx] - [#26239]) ([apple_tv docs])
|
||||
- Cleanup strings ([@andrewsayre] - [#26243]) ([smartthings docs])
|
||||
- Fix WWLLN entity management ([@exxamalte] - [#26250]) ([wwlln docs])
|
||||
- Enable cert_expiry config entries ([@Cereal2nd] - [#25624]) ([cert_expiry docs])
|
||||
- Velbus config entries remove decorator ([@Cereal2nd] - [#26256]) ([velbus docs])
|
||||
- Bump androidtv to 0.0.25 and add tests ([@JeffLIrion] - [#26202]) ([androidtv docs])
|
||||
- Add two new methods to the OpenUV component that consume only a singl… ([@StephenWetzel] - [#26207]) ([openuv docs])
|
||||
- Clean up HEOS strings ([@andrewsayre] - [#26242]) ([heos docs])
|
||||
- Fix deConz thermostat integration ([@5mauggy] - [#26267]) ([deconz docs])
|
||||
- Remove deprecated SMA config ([@balloob] - [#26306]) ([sma docs]) (breaking change)
|
||||
- Add HEAD and PUT support to webhooks ([@balloob] - [#26299]) ([webhook docs])
|
||||
- Add support for Homekit accessory battery sensors ([@Jc2k] - [#26210]) ([homekit_controller docs])
|
||||
- Add Withings support ([@vangorra] - [#25154]) ([withings docs]) (new-integration)
|
||||
- Add precision argument to the Range Filter ([@dgomes] - [#25874]) ([filter docs])
|
||||
- Fetch Onkyo current radio preset ([@pszafer] - [#26211]) ([onkyo docs])
|
||||
- UniFi - use entity registry disabled_by to control available entities ([@Kane610] - [#26141]) ([unifi docs])
|
||||
- Fix onvif camera setup error ([@sanyatuning] - [#24585]) ([onvif docs])
|
||||
- Upgrade youtube_dl to 2019.09.01 ([@BKPepe] - [#26330]) ([media_extractor docs])
|
||||
- Add a keypress service for AlarmDecoder ([@jkeljo] - [#26100]) ([alarmdecoder docs])
|
||||
- Add support for Supla switches ([@Rocik] - [#26188]) ([supla docs]) (new-platform)
|
||||
- Change evohome to asyncio client ([@zxdavb] - [#26042]) ([evohome docs])
|
||||
- Upgrade sqlalchemy to 1.3.8 ([@BKPepe] - [#26331]) ([recorder docs]) ([sql docs])
|
||||
- Migrate Axis, deCONZ and UniFi to use config entry subclass ([@Kane610] - [#26173]) ([axis docs]) ([deconz docs]) ([unifi docs])
|
||||
- Upgrade tibber library ([@Danielhiversen] - [#26332]) ([tibber docs])
|
||||
- Inverted rflink cover ([@fmartens] - [#26038]) ([rflink docs])
|
||||
- UniFi - Simplify getting controller from config entry ([@Kane610] - [#26335]) ([unifi docs])
|
||||
- Add BeeWi SmartClim BLE sensors ([@alemuro] - [#26174]) ([beewi_smartclim docs]) (new-integration)
|
||||
- New template sensor attributes ([@gadgetchnnel] - [#26127]) ([template docs])
|
||||
- Add improvements of device_automation from frontend PR 3514 ([@emontnemery] - [#26295]) ([automation docs]) ([device_automation docs]) ([light docs])
|
||||
- added missing bluepy dependency for miflora ([@ChristianKuehnel] - [#26297]) ([miflora docs])
|
||||
- USGS Earthquakes icon for geolocation entities ([@exxamalte] - [#26353]) ([usgs_earthquakes_feed docs])
|
||||
- Test with 3.6.1 in Travis ([@scop] - [#26347])
|
||||
- Push to version 0.7.10 of denonavr ([@scarface-4711] - [#26362]) ([denonavr docs])
|
||||
- Bump androidtv to 0.0.26 and update tests ([@JeffLIrion] - [#26340])
|
||||
- Update google_maps dependency and improve error message ([@costastf] - [#26361]) ([google_maps docs])
|
||||
- Update zigpy_zigate to 0.2.0 ([@doudz] - [#26327]) ([zha docs])
|
||||
- Allow passing dictionaries to async_register_entity_service ([@balloob] - [#26370]) ([light docs]) ([switch docs])
|
||||
- Support new climate arch for zhong_hong ([@crhan] - [#26309]) ([zhong_hong docs])
|
||||
- Correct file permissions, removing executable bits ([@frenck] - [#26376])
|
||||
- Use literal string interpolation in integrations A (f-strings) ([@frenck] - [#26377])
|
||||
- Remove solaredge_local duplicate code ([@ThaStealth] - [#25941]) ([solaredge_local docs])
|
||||
- Use literal string interpolation in integrations B-D (f-strings) ([@frenck] - [#26378])
|
||||
- Use literal string interpolation in integrations E-G (f-strings) ([@frenck] - [#26379])
|
||||
- GeoNet NZ Quakes Sensor ([@exxamalte] - [#26078]) ([geonetnz_quakes docs]) (new-platform)
|
||||
- Use literal string interpolation in integrations H-J (f-strings) ([@frenck] - [#26380])
|
||||
- Removes executable but from hassfest codeowners ([@frenck] - [#26381])
|
||||
- Add support Slide cover ([@ualex73] - [#25913]) ([slide docs]) (new-integration)
|
||||
- Use literal string interpolation in integrations N-Q (f-strings) ([@frenck] - [#26391])
|
||||
- Update OpenCV 4.1.1 / Numpy 1.17.1 ([@pvizeli] - [#26387]) ([iqvia docs]) ([opencv docs]) ([tensorflow docs]) ([trend docs])
|
||||
- Use literal string interpolation in integrations T-W (f-strings) ([@frenck] - [#26394])
|
||||
- Use literal string interpolation in integrations K-M (f-strings) ([@frenck] - [#26389])
|
||||
- Use literal string interpolation in integrations R-S (f-strings) ([@frenck] - [#26392])
|
||||
- Use literal string interpolation in integrations X-Z (f-strings) ([@frenck] - [#26395])
|
||||
- Fixes invalid JSON files and whitespace corrections in YAML files ([@frenck] - [#26396]) ([ihc docs]) ([point docs]) ([solax docs])
|
||||
- Refactor pihole integration ([@johnluetke] - [#25837]) ([pi_hole docs]) (breaking change)
|
||||
- Change xiaomi camera conf_host to template ([@vaidyasr] - [#25799]) ([xiaomi docs])
|
||||
- Fix Emulated Hue AttributeError: 'NoneType' object has no attribute '… ([@croghostrider] - [#26018]) ([emulated_hue docs])
|
||||
- Allow passing None as input_text config ([@balloob] - [#26409]) ([input_text docs])
|
||||
- IGN Sismologia icon for geolocation entities ([@exxamalte] - [#26408]) ([ign_sismologia docs])
|
||||
- Migrate legacy typehints in core to PEP-526 ([@frenck] - [#26403]) ([device_tracker docs])
|
||||
- Add X10 devices as ISY994 switches ([@taylorsilva] - [#26342]) ([isy994 docs])
|
||||
- Add config flow to linky ([@Quentame] - [#26076]) ([linky docs]) (breaking change)
|
||||
- Correct file permissions in slide integration ([@frenck] - [#26390]) ([slide docs])
|
||||
- Use literal string interpolation in honeywell ([@zxdavb] - [#26386]) ([honeywell docs])
|
||||
- Initial commit ([@zxdavb] - [#26385]) ([geniushub docs])
|
||||
- Initial commit ([@zxdavb] - [#26383]) ([evohome docs])
|
||||
- NSW Rural Fire Service icon for geolocation entities ([@exxamalte] - [#26416]) ([nsw_rural_fire_service_feed docs])
|
||||
- Add prettier to vscode ([@pvizeli] - [#26417])
|
||||
- Updated frontend to 20190904.0 ([@bramkragten] - [#26421]) ([frontend docs])
|
||||
- Add device to mqtt camera ([@zewelor] - [#26238]) ([mqtt docs])
|
||||
- Entity registry doesn't overwrite with None ([@Swamp-Ig] - [#24275])
|
||||
- Replaces IOError by OSError ([@frenck] - [#26428])
|
||||
- Add atome sensor platform ([@BaQs] - [#26197]) ([atome docs]) (new-integration)
|
||||
- Cleanup Dockerfile.dev ([@pvizeli] - [#26451])
|
||||
- Add device automation condition ([@emontnemery] - [#26313]) ([automation docs]) ([device_automation docs]) ([light docs])
|
||||
- Queensland Bushfire Alert icon for geolocation entities ([@exxamalte] - [#26439]) ([qld_bushfire docs])
|
||||
- Standardize Plex server connections ([@jjlawren] - [#26444]) ([plex docs]) (breaking change)
|
||||
- Add plex server config options to media_player platform ([@jjlawren] - [#26458]) ([plex docs])
|
||||
- Add device automation action ([@emontnemery] - [#26455]) ([device_automation docs]) ([light docs])
|
||||
- deCONZ - use entity registry disabled_by to control available entities ([@Kane610] - [#26219]) ([deconz docs])
|
||||
- Add person to device_sun_light_trigger ([@kellerza] - [#25877]) ([device_sun_light_trigger docs])
|
||||
- Change darksky icon for clear night ([@Mariusthvdb] - [#26452]) ([darksky docs])
|
||||
- Jewish calendar binary sensor ([@tsvi] - [#26200]) ([jewish_calendar docs]) (breaking change) (new-platform)
|
||||
- bump geniushub client ([@zxdavb] - [#26476]) ([geniushub docs])
|
||||
- Unify device_state_attributes handling for Homematic IP Cloud ([@SukramJ] - [#26449]) ([homematicip_cloud docs]) (breaking change)
|
||||
- Add yeelight nightlight support via separate light entity ([@zewelor] - [#26224]) ([yeelight docs])
|
||||
- Add set scene service calls to yeelight ([@zewelor] - [#26255]) ([yeelight docs])
|
||||
- Add device_info to Linky integration ([@Quentame] - [#26477]) ([linky docs])
|
||||
- Update radiotherm climate attributes ([@dieselrabbit] - [#26465]) ([radiotherm docs]) (breaking change)
|
||||
- Add Viessmann ViCare Climate platform ([@oischinger] - [#26151]) ([vicare docs]) (new-integration)
|
||||
- Add new integration for Jandy iAqualink pool control ([@flz] - [#26034]) ([iaqualink docs]) (new-integration)
|
||||
- Add protocol and model as an optional restriction for tellstick sensors ([@brange] - [#26026]) ([tellstick docs])
|
||||
- Fix KNX light tunable white rounding error ([@farmio] - [#26364]) ([knx docs])
|
||||
- Bump aiowwlln to 2.0.1 ([@bachya] - [#26486]) ([wwlln docs])
|
||||
- Vicare: Avoid invalid temperature values ([@oischinger] - [#26485]) ([vicare docs])
|
||||
- Use PEP 526 type annotations, add some type hints ([@scop] - [#26464])
|
||||
- Restructure Z-Wave Climate ([@Santobert] - [#25724]) ([zwave docs])
|
||||
- fix cluster configuration ([@dmulcahey] - [#26494]) ([zha docs])
|
||||
- Bump androidtv to 0.0.27 ([@JeffLIrion] - [#26497]) ([androidtv docs])
|
||||
- Device automations: Rename name to entity_name in translations ([@emontnemery] - [#26491]) ([light docs])
|
||||
- Bump ZHA dependencies. ([@Adminiuga] - [#26504]) ([zha docs])
|
||||
- Bump geniushubclient ([@zxdavb] - [#26519]) ([geniushub docs])
|
||||
- Update to async_upnp_client==0.14.11 ([@StevenLooman] - [#26515]) ([dlna_dmr docs]) ([upnp docs])
|
||||
- Updated frontend to 20190908.0 ([@bramkragten] - [#26524]) ([frontend docs])
|
||||
- Add vivotek camera component ([@HarlemSquirrel] - [#26071]) ([vivotek docs]) (new-integration)
|
||||
- Enable SolarEdge config entries ([@Cereal2nd] - [#26282]) ([solaredge docs]) (breaking change)
|
||||
- use newly added is_server for cluster reporting ([@dmulcahey] - [#26533]) ([zha docs])
|
||||
- Add device automation support to switch entities ([@emontnemery] - [#26466]) ([device_automation docs]) ([light docs]) ([switch docs])
|
||||
- Remove device from device action schema ([@emontnemery] - [#26536]) ([device_automation docs])
|
||||
- Move iaqualink update from climate to component ([@flz] - [#26505]) ([iaqualink docs])
|
||||
- Do not complain about automatic generated files ([@balloob] - [#26540])
|
||||
- Fix Tuya Light without brightness ([@tyjtyj] - [#26534]) ([tuya docs])
|
||||
- Add Delta Counter of HmIP-SPDR to Homematic IP Cloud ([@SukramJ] - [#26538]) ([homematicip_cloud docs])
|
||||
- Add light platform to iaqualink integration ([@flz] - [#26484]) ([iaqualink docs]) (new-platform)
|
||||
- Move config and connections to Plex component ([@jjlawren] - [#26488]) ([discovery docs]) ([plex docs]) (breaking change)
|
||||
- Fix radiotherm local time ([@tsvi] - [#26526]) ([radiotherm docs])
|
||||
- Add more attributes to vicare climate entity ([@oischinger] - [#26521]) ([vicare docs])
|
||||
- Add growatt server integration ([@indykoning] - [#25635]) ([growatt_server docs]) (new-integration)
|
||||
- Add zwave application version ([@lifeisafractal] - [#26205]) ([zwave docs])
|
||||
- Remove unnecessary force_refresh=True, clarify system behavior ([@flz] - [#26543]) ([iaqualink docs])
|
||||
- Add Météo France icons + device_class ([@Quentame] - [#26441]) ([meteo_france docs])
|
||||
- Bump geniushub-client to 0.6.13 ([@zxdavb] - [#26554]) ([geniushub docs])
|
||||
- Add sensor platform to iaqualink component ([@flz] - [#26544]) ([iaqualink docs]) (new-platform)
|
||||
- Refactor Cast ([@balloob] - [#26550]) ([cast docs])
|
||||
- fix events for smartthings acceleration cluster ([@dmulcahey] - [#26557]) ([zha docs])
|
||||
- osram cluster ([@dmulcahey] - [#26555]) ([zha docs])
|
||||
- Nuki less strict ([@pvizeli] - [#26542]) ([nuki docs])
|
||||
- deCONZ device automations ([@Kane610] - [#26366]) ([deconz docs])
|
||||
- Improve startup of devcontainer ([@pvizeli] - [#26572])
|
||||
- Cleanup stale script stuff ([@pvizeli] - [#26573])
|
||||
- Bump UPC connect / fix auth issue ([@pvizeli] - [#26570]) ([upc_connect docs])
|
||||
- bump dependencies ([@dmulcahey] - [#26576]) ([zha docs])
|
||||
- Updated frontend to 20190911.0 ([@bramkragten] - [#26578]) ([frontend docs])
|
||||
- Make uk_transport sensor timezone/DST aware ([@tsvi] - [#26577]) ([uk_transport docs])
|
||||
- Fix GTFS sensor wrong timezone ([@tsvi] - [#26580]) ([gtfs docs])
|
||||
- Add switch platform to iaqualink integration ([@flz] - [#26545]) ([iaqualink docs]) (new-platform)
|
||||
- Add Obihai integration ([@dshokouhi] - [#26537]) ([obihai docs]) (new-integration)
|
||||
- Remove default host for Plex config ([@jjlawren] - [#26583]) ([plex docs]) (breaking change)
|
||||
- Home Assistant Cast ([@balloob] - [#26566]) ([cast docs])
|
||||
- Deprecate Python 3.6.0 ([@pvizeli] - [#26575])
|
||||
- Check if git is dirty before committing ([@balloob] - [#26588])
|
||||
- Remove support of UniFi device tracker configuration import ([@Kane610] - [#26587]) ([unifi docs]) (breaking change)
|
||||
- Fix CCM messages ([@gerard33] - [#26589]) ([bmw_connected_drive docs]) (beta fix)
|
||||
- Update PyChromecast ([@balloob] - [#26594]) ([cast docs]) (beta fix)
|
||||
- Use Nabu Casa url if no https url set ([@balloob] - [#26682]) ([cast docs]) (beta fix)
|
||||
- Updated frontend to 20190917.0 ([@bramkragten] - [#26686]) ([frontend docs]) (beta fix)
|
||||
- Fix Nuki issues ([@pvizeli] - [#26689]) ([nuki docs]) (breaking change) (beta fix)
|
||||
- Bump connect-box library to fix logging ([@pvizeli] - [#26690]) ([upc_connect docs]) (beta fix)
|
||||
- Updated frontend to 20190917.1 ([@bramkragten] - [#26691]) ([frontend docs]) (beta fix)
|
||||
- Rename MockToggleDevice to MockToggleEntity ([@emontnemery] - [#26644]) (beta fix)
|
||||
- Fix translation, adjust trigger names ([@emontnemery] - [#26635]) ([device_automation docs]) ([light docs]) ([switch docs]) (beta fix)
|
||||
- Fix cert expiry config flow check and update ([@Cereal2nd] - [#26638]) ([cert_expiry docs]) (beta fix)
|
||||
- Fix release access for bram ([@pvizeli] - [#26693]) (beta fix)
|
||||
- Updated frontend to 20190917.2 ([@bramkragten] - [#26696]) ([frontend docs]) (beta fix)
|
||||
- Verify withings config ([@balloob] - [#26698]) ([withings docs]) (beta fix)
|
||||
- Updated frontend to 20190918.0 ([@bramkragten] - [#26704]) ([frontend docs]) (beta fix)
|
||||
- Fix yeelight inheritance order ([@zewelor] - [#26706]) ([yeelight docs]) (beta fix)
|
||||
|
||||
[#23647]: https://github.com/home-assistant/home-assistant/pull/23647
|
||||
[#23881]: https://github.com/home-assistant/home-assistant/pull/23881
|
||||
[#24275]: https://github.com/home-assistant/home-assistant/pull/24275
|
||||
[#24585]: https://github.com/home-assistant/home-assistant/pull/24585
|
||||
[#25154]: https://github.com/home-assistant/home-assistant/pull/25154
|
||||
[#25624]: https://github.com/home-assistant/home-assistant/pull/25624
|
||||
[#25635]: https://github.com/home-assistant/home-assistant/pull/25635
|
||||
[#25724]: https://github.com/home-assistant/home-assistant/pull/25724
|
||||
[#25799]: https://github.com/home-assistant/home-assistant/pull/25799
|
||||
[#25837]: https://github.com/home-assistant/home-assistant/pull/25837
|
||||
[#25874]: https://github.com/home-assistant/home-assistant/pull/25874
|
||||
[#25877]: https://github.com/home-assistant/home-assistant/pull/25877
|
||||
[#25899]: https://github.com/home-assistant/home-assistant/pull/25899
|
||||
[#25913]: https://github.com/home-assistant/home-assistant/pull/25913
|
||||
[#25941]: https://github.com/home-assistant/home-assistant/pull/25941
|
||||
[#26018]: https://github.com/home-assistant/home-assistant/pull/26018
|
||||
[#26026]: https://github.com/home-assistant/home-assistant/pull/26026
|
||||
[#26034]: https://github.com/home-assistant/home-assistant/pull/26034
|
||||
[#26038]: https://github.com/home-assistant/home-assistant/pull/26038
|
||||
[#26042]: https://github.com/home-assistant/home-assistant/pull/26042
|
||||
[#26071]: https://github.com/home-assistant/home-assistant/pull/26071
|
||||
[#26076]: https://github.com/home-assistant/home-assistant/pull/26076
|
||||
[#26078]: https://github.com/home-assistant/home-assistant/pull/26078
|
||||
[#26100]: https://github.com/home-assistant/home-assistant/pull/26100
|
||||
[#26127]: https://github.com/home-assistant/home-assistant/pull/26127
|
||||
[#26128]: https://github.com/home-assistant/home-assistant/pull/26128
|
||||
[#26140]: https://github.com/home-assistant/home-assistant/pull/26140
|
||||
[#26141]: https://github.com/home-assistant/home-assistant/pull/26141
|
||||
[#26148]: https://github.com/home-assistant/home-assistant/pull/26148
|
||||
[#26151]: https://github.com/home-assistant/home-assistant/pull/26151
|
||||
[#26166]: https://github.com/home-assistant/home-assistant/pull/26166
|
||||
[#26167]: https://github.com/home-assistant/home-assistant/pull/26167
|
||||
[#26173]: https://github.com/home-assistant/home-assistant/pull/26173
|
||||
[#26174]: https://github.com/home-assistant/home-assistant/pull/26174
|
||||
[#26179]: https://github.com/home-assistant/home-assistant/pull/26179
|
||||
[#26182]: https://github.com/home-assistant/home-assistant/pull/26182
|
||||
[#26188]: https://github.com/home-assistant/home-assistant/pull/26188
|
||||
[#26196]: https://github.com/home-assistant/home-assistant/pull/26196
|
||||
[#26197]: https://github.com/home-assistant/home-assistant/pull/26197
|
||||
[#26200]: https://github.com/home-assistant/home-assistant/pull/26200
|
||||
[#26201]: https://github.com/home-assistant/home-assistant/pull/26201
|
||||
[#26202]: https://github.com/home-assistant/home-assistant/pull/26202
|
||||
[#26203]: https://github.com/home-assistant/home-assistant/pull/26203
|
||||
[#26204]: https://github.com/home-assistant/home-assistant/pull/26204
|
||||
[#26205]: https://github.com/home-assistant/home-assistant/pull/26205
|
||||
[#26207]: https://github.com/home-assistant/home-assistant/pull/26207
|
||||
[#26210]: https://github.com/home-assistant/home-assistant/pull/26210
|
||||
[#26211]: https://github.com/home-assistant/home-assistant/pull/26211
|
||||
[#26216]: https://github.com/home-assistant/home-assistant/pull/26216
|
||||
[#26218]: https://github.com/home-assistant/home-assistant/pull/26218
|
||||
[#26219]: https://github.com/home-assistant/home-assistant/pull/26219
|
||||
[#26221]: https://github.com/home-assistant/home-assistant/pull/26221
|
||||
[#26224]: https://github.com/home-assistant/home-assistant/pull/26224
|
||||
[#26238]: https://github.com/home-assistant/home-assistant/pull/26238
|
||||
[#26239]: https://github.com/home-assistant/home-assistant/pull/26239
|
||||
[#26242]: https://github.com/home-assistant/home-assistant/pull/26242
|
||||
[#26243]: https://github.com/home-assistant/home-assistant/pull/26243
|
||||
[#26250]: https://github.com/home-assistant/home-assistant/pull/26250
|
||||
[#26255]: https://github.com/home-assistant/home-assistant/pull/26255
|
||||
[#26256]: https://github.com/home-assistant/home-assistant/pull/26256
|
||||
[#26267]: https://github.com/home-assistant/home-assistant/pull/26267
|
||||
[#26282]: https://github.com/home-assistant/home-assistant/pull/26282
|
||||
[#26295]: https://github.com/home-assistant/home-assistant/pull/26295
|
||||
[#26297]: https://github.com/home-assistant/home-assistant/pull/26297
|
||||
[#26299]: https://github.com/home-assistant/home-assistant/pull/26299
|
||||
[#26306]: https://github.com/home-assistant/home-assistant/pull/26306
|
||||
[#26309]: https://github.com/home-assistant/home-assistant/pull/26309
|
||||
[#26313]: https://github.com/home-assistant/home-assistant/pull/26313
|
||||
[#26327]: https://github.com/home-assistant/home-assistant/pull/26327
|
||||
[#26330]: https://github.com/home-assistant/home-assistant/pull/26330
|
||||
[#26331]: https://github.com/home-assistant/home-assistant/pull/26331
|
||||
[#26332]: https://github.com/home-assistant/home-assistant/pull/26332
|
||||
[#26335]: https://github.com/home-assistant/home-assistant/pull/26335
|
||||
[#26340]: https://github.com/home-assistant/home-assistant/pull/26340
|
||||
[#26342]: https://github.com/home-assistant/home-assistant/pull/26342
|
||||
[#26347]: https://github.com/home-assistant/home-assistant/pull/26347
|
||||
[#26353]: https://github.com/home-assistant/home-assistant/pull/26353
|
||||
[#26361]: https://github.com/home-assistant/home-assistant/pull/26361
|
||||
[#26362]: https://github.com/home-assistant/home-assistant/pull/26362
|
||||
[#26364]: https://github.com/home-assistant/home-assistant/pull/26364
|
||||
[#26366]: https://github.com/home-assistant/home-assistant/pull/26366
|
||||
[#26370]: https://github.com/home-assistant/home-assistant/pull/26370
|
||||
[#26376]: https://github.com/home-assistant/home-assistant/pull/26376
|
||||
[#26377]: https://github.com/home-assistant/home-assistant/pull/26377
|
||||
[#26378]: https://github.com/home-assistant/home-assistant/pull/26378
|
||||
[#26379]: https://github.com/home-assistant/home-assistant/pull/26379
|
||||
[#26380]: https://github.com/home-assistant/home-assistant/pull/26380
|
||||
[#26381]: https://github.com/home-assistant/home-assistant/pull/26381
|
||||
[#26383]: https://github.com/home-assistant/home-assistant/pull/26383
|
||||
[#26385]: https://github.com/home-assistant/home-assistant/pull/26385
|
||||
[#26386]: https://github.com/home-assistant/home-assistant/pull/26386
|
||||
[#26387]: https://github.com/home-assistant/home-assistant/pull/26387
|
||||
[#26389]: https://github.com/home-assistant/home-assistant/pull/26389
|
||||
[#26390]: https://github.com/home-assistant/home-assistant/pull/26390
|
||||
[#26391]: https://github.com/home-assistant/home-assistant/pull/26391
|
||||
[#26392]: https://github.com/home-assistant/home-assistant/pull/26392
|
||||
[#26394]: https://github.com/home-assistant/home-assistant/pull/26394
|
||||
[#26395]: https://github.com/home-assistant/home-assistant/pull/26395
|
||||
[#26396]: https://github.com/home-assistant/home-assistant/pull/26396
|
||||
[#26403]: https://github.com/home-assistant/home-assistant/pull/26403
|
||||
[#26408]: https://github.com/home-assistant/home-assistant/pull/26408
|
||||
[#26409]: https://github.com/home-assistant/home-assistant/pull/26409
|
||||
[#26416]: https://github.com/home-assistant/home-assistant/pull/26416
|
||||
[#26417]: https://github.com/home-assistant/home-assistant/pull/26417
|
||||
[#26421]: https://github.com/home-assistant/home-assistant/pull/26421
|
||||
[#26428]: https://github.com/home-assistant/home-assistant/pull/26428
|
||||
[#26439]: https://github.com/home-assistant/home-assistant/pull/26439
|
||||
[#26441]: https://github.com/home-assistant/home-assistant/pull/26441
|
||||
[#26444]: https://github.com/home-assistant/home-assistant/pull/26444
|
||||
[#26449]: https://github.com/home-assistant/home-assistant/pull/26449
|
||||
[#26451]: https://github.com/home-assistant/home-assistant/pull/26451
|
||||
[#26452]: https://github.com/home-assistant/home-assistant/pull/26452
|
||||
[#26455]: https://github.com/home-assistant/home-assistant/pull/26455
|
||||
[#26458]: https://github.com/home-assistant/home-assistant/pull/26458
|
||||
[#26464]: https://github.com/home-assistant/home-assistant/pull/26464
|
||||
[#26465]: https://github.com/home-assistant/home-assistant/pull/26465
|
||||
[#26466]: https://github.com/home-assistant/home-assistant/pull/26466
|
||||
[#26476]: https://github.com/home-assistant/home-assistant/pull/26476
|
||||
[#26477]: https://github.com/home-assistant/home-assistant/pull/26477
|
||||
[#26484]: https://github.com/home-assistant/home-assistant/pull/26484
|
||||
[#26485]: https://github.com/home-assistant/home-assistant/pull/26485
|
||||
[#26486]: https://github.com/home-assistant/home-assistant/pull/26486
|
||||
[#26488]: https://github.com/home-assistant/home-assistant/pull/26488
|
||||
[#26491]: https://github.com/home-assistant/home-assistant/pull/26491
|
||||
[#26494]: https://github.com/home-assistant/home-assistant/pull/26494
|
||||
[#26497]: https://github.com/home-assistant/home-assistant/pull/26497
|
||||
[#26504]: https://github.com/home-assistant/home-assistant/pull/26504
|
||||
[#26505]: https://github.com/home-assistant/home-assistant/pull/26505
|
||||
[#26515]: https://github.com/home-assistant/home-assistant/pull/26515
|
||||
[#26519]: https://github.com/home-assistant/home-assistant/pull/26519
|
||||
[#26521]: https://github.com/home-assistant/home-assistant/pull/26521
|
||||
[#26524]: https://github.com/home-assistant/home-assistant/pull/26524
|
||||
[#26526]: https://github.com/home-assistant/home-assistant/pull/26526
|
||||
[#26533]: https://github.com/home-assistant/home-assistant/pull/26533
|
||||
[#26534]: https://github.com/home-assistant/home-assistant/pull/26534
|
||||
[#26536]: https://github.com/home-assistant/home-assistant/pull/26536
|
||||
[#26537]: https://github.com/home-assistant/home-assistant/pull/26537
|
||||
[#26538]: https://github.com/home-assistant/home-assistant/pull/26538
|
||||
[#26540]: https://github.com/home-assistant/home-assistant/pull/26540
|
||||
[#26542]: https://github.com/home-assistant/home-assistant/pull/26542
|
||||
[#26543]: https://github.com/home-assistant/home-assistant/pull/26543
|
||||
[#26544]: https://github.com/home-assistant/home-assistant/pull/26544
|
||||
[#26545]: https://github.com/home-assistant/home-assistant/pull/26545
|
||||
[#26550]: https://github.com/home-assistant/home-assistant/pull/26550
|
||||
[#26554]: https://github.com/home-assistant/home-assistant/pull/26554
|
||||
[#26555]: https://github.com/home-assistant/home-assistant/pull/26555
|
||||
[#26557]: https://github.com/home-assistant/home-assistant/pull/26557
|
||||
[#26566]: https://github.com/home-assistant/home-assistant/pull/26566
|
||||
[#26570]: https://github.com/home-assistant/home-assistant/pull/26570
|
||||
[#26572]: https://github.com/home-assistant/home-assistant/pull/26572
|
||||
[#26573]: https://github.com/home-assistant/home-assistant/pull/26573
|
||||
[#26575]: https://github.com/home-assistant/home-assistant/pull/26575
|
||||
[#26576]: https://github.com/home-assistant/home-assistant/pull/26576
|
||||
[#26577]: https://github.com/home-assistant/home-assistant/pull/26577
|
||||
[#26578]: https://github.com/home-assistant/home-assistant/pull/26578
|
||||
[#26580]: https://github.com/home-assistant/home-assistant/pull/26580
|
||||
[#26583]: https://github.com/home-assistant/home-assistant/pull/26583
|
||||
[#26587]: https://github.com/home-assistant/home-assistant/pull/26587
|
||||
[#26588]: https://github.com/home-assistant/home-assistant/pull/26588
|
||||
[#26589]: https://github.com/home-assistant/home-assistant/pull/26589
|
||||
[#26594]: https://github.com/home-assistant/home-assistant/pull/26594
|
||||
[#26635]: https://github.com/home-assistant/home-assistant/pull/26635
|
||||
[#26638]: https://github.com/home-assistant/home-assistant/pull/26638
|
||||
[#26644]: https://github.com/home-assistant/home-assistant/pull/26644
|
||||
[#26682]: https://github.com/home-assistant/home-assistant/pull/26682
|
||||
[#26686]: https://github.com/home-assistant/home-assistant/pull/26686
|
||||
[#26689]: https://github.com/home-assistant/home-assistant/pull/26689
|
||||
[#26690]: https://github.com/home-assistant/home-assistant/pull/26690
|
||||
[#26691]: https://github.com/home-assistant/home-assistant/pull/26691
|
||||
[#26693]: https://github.com/home-assistant/home-assistant/pull/26693
|
||||
[#26696]: https://github.com/home-assistant/home-assistant/pull/26696
|
||||
[#26698]: https://github.com/home-assistant/home-assistant/pull/26698
|
||||
[#26704]: https://github.com/home-assistant/home-assistant/pull/26704
|
||||
[#26706]: https://github.com/home-assistant/home-assistant/pull/26706
|
||||
[@5mauggy]: https://github.com/5mauggy
|
||||
[@adminiuga]: https://github.com/Adminiuga
|
||||
[@bkpepe]: https://github.com/BKPepe
|
||||
[@baqs]: https://github.com/BaQs
|
||||
[@cereal2nd]: https://github.com/Cereal2nd
|
||||
[@christiankuehnel]: https://github.com/ChristianKuehnel
|
||||
[@danielhiversen]: https://github.com/Danielhiversen
|
||||
[@harlemsquirrel]: https://github.com/HarlemSquirrel
|
||||
[@jc2k]: https://github.com/Jc2k
|
||||
[@jefflirion]: https://github.com/JeffLIrion
|
||||
[@kane610]: https://github.com/Kane610
|
||||
[@mariusthvdb]: https://github.com/Mariusthvdb
|
||||
[@matthewflamm]: https://github.com/MatthewFlamm
|
||||
[@quentame]: https://github.com/Quentame
|
||||
[@rocik]: https://github.com/Rocik
|
||||
[@santobert]: https://github.com/Santobert
|
||||
[@stephenwetzel]: https://github.com/StephenWetzel
|
||||
[@stevenlooman]: https://github.com/StevenLooman
|
||||
[@sukramj]: https://github.com/SukramJ
|
||||
[@swamp-ig]: https://github.com/Swamp-Ig
|
||||
[@thastealth]: https://github.com/ThaStealth
|
||||
[@alemuro]: https://github.com/alemuro
|
||||
[@andrewsayre]: https://github.com/andrewsayre
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@brange]: https://github.com/brange
|
||||
[@costastf]: https://github.com/costastf
|
||||
[@crhan]: https://github.com/crhan
|
||||
[@croghostrider]: https://github.com/croghostrider
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[@dieselrabbit]: https://github.com/dieselrabbit
|
||||
[@dmulcahey]: https://github.com/dmulcahey
|
||||
[@doudz]: https://github.com/doudz
|
||||
[@dshokouhi]: https://github.com/dshokouhi
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@exxamalte]: https://github.com/exxamalte
|
||||
[@farmio]: https://github.com/farmio
|
||||
[@flz]: https://github.com/flz
|
||||
[@fmartens]: https://github.com/fmartens
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@gadgetchnnel]: https://github.com/gadgetchnnel
|
||||
[@gerard33]: https://github.com/gerard33
|
||||
[@iamtpage]: https://github.com/iamtpage
|
||||
[@indykoning]: https://github.com/indykoning
|
||||
[@jjlawren]: https://github.com/jjlawren
|
||||
[@jkeljo]: https://github.com/jkeljo
|
||||
[@johnluetke]: https://github.com/johnluetke
|
||||
[@kellerza]: https://github.com/kellerza
|
||||
[@lifeisafractal]: https://github.com/lifeisafractal
|
||||
[@michaeldavie]: https://github.com/michaeldavie
|
||||
[@newbee112]: https://github.com/newbee112
|
||||
[@oischinger]: https://github.com/oischinger
|
||||
[@presslab-us]: https://github.com/presslab-us
|
||||
[@pszafer]: https://github.com/pszafer
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@sanyatuning]: https://github.com/sanyatuning
|
||||
[@scarface-4711]: https://github.com/scarface-4711
|
||||
[@schmittx]: https://github.com/schmittx
|
||||
[@scop]: https://github.com/scop
|
||||
[@taylorsilva]: https://github.com/taylorsilva
|
||||
[@tsvi]: https://github.com/tsvi
|
||||
[@tyjtyj]: https://github.com/tyjtyj
|
||||
[@ualex73]: https://github.com/ualex73
|
||||
[@vaidyasr]: https://github.com/vaidyasr
|
||||
[@vangorra]: https://github.com/vangorra
|
||||
[@zewelor]: https://github.com/zewelor
|
||||
[@zxdavb]: https://github.com/zxdavb
|
||||
[alarmdecoder docs]: /components/alarmdecoder/
|
||||
[ambiclimate docs]: /components/ambiclimate/
|
||||
[androidtv docs]: /components/androidtv/
|
||||
[apple_tv docs]: /components/apple_tv/
|
||||
[atome docs]: /components/atome/
|
||||
[automation docs]: /components/automation/
|
||||
[axis docs]: /components/axis/
|
||||
[beewi_smartclim docs]: /components/beewi_smartclim/
|
||||
[bmw_connected_drive docs]: /components/bmw_connected_drive/
|
||||
[cast docs]: /components/cast/
|
||||
[cert_expiry docs]: /components/cert_expiry/
|
||||
[darksky docs]: /components/darksky/
|
||||
[deconz docs]: /components/deconz/
|
||||
[denonavr docs]: /components/denonavr/
|
||||
[device_automation docs]: /components/device_automation/
|
||||
[device_sun_light_trigger docs]: /components/device_sun_light_trigger/
|
||||
[device_tracker docs]: /components/device_tracker/
|
||||
[discovery docs]: /components/discovery/
|
||||
[dlna_dmr docs]: /components/dlna_dmr/
|
||||
[duckdns docs]: /components/duckdns/
|
||||
[emulated_hue docs]: /components/emulated_hue/
|
||||
[environment_canada docs]: /components/environment_canada/
|
||||
[evohome docs]: /components/evohome/
|
||||
[filter docs]: /components/filter/
|
||||
[frontend docs]: /components/frontend/
|
||||
[geniushub docs]: /components/geniushub/
|
||||
[geonetnz_quakes docs]: /components/geonetnz_quakes/
|
||||
[glances docs]: /components/glances/
|
||||
[google_maps docs]: /components/google_maps/
|
||||
[slide docs]: /components/slide/
|
||||
[growatt_server docs]: /components/growatt_server/
|
||||
[gtfs docs]: /components/gtfs/
|
||||
[heos docs]: /components/heos/
|
||||
[history docs]: /components/history/
|
||||
[homekit_controller docs]: /components/homekit_controller/
|
||||
[homematicip_cloud docs]: /components/homematicip_cloud/
|
||||
[honeywell docs]: /components/honeywell/
|
||||
[huawei_lte docs]: /components/huawei_lte/
|
||||
[iaqualink docs]: /components/iaqualink/
|
||||
[ign_sismologia docs]: /components/ign_sismologia/
|
||||
[ihc docs]: /components/ihc/
|
||||
[input_text docs]: /components/input_text/
|
||||
[iqvia docs]: /components/iqvia/
|
||||
[isy994 docs]: /components/isy994/
|
||||
[jewish_calendar docs]: /components/jewish_calendar/
|
||||
[knx docs]: /components/knx/
|
||||
[light docs]: /components/light/
|
||||
[linky docs]: /components/linky/
|
||||
[media_extractor docs]: /components/media_extractor/
|
||||
[meteo_france docs]: /components/meteo_france/
|
||||
[miflora docs]: /components/miflora/
|
||||
[mqtt docs]: /components/mqtt/
|
||||
[nsw_rural_fire_service_feed docs]: /components/nsw_rural_fire_service_feed/
|
||||
[nuki docs]: /components/nuki/
|
||||
[nws docs]: /components/nws/
|
||||
[obihai docs]: /components/obihai/
|
||||
[onkyo docs]: /components/onkyo/
|
||||
[onvif docs]: /components/onvif/
|
||||
[opencv docs]: /components/opencv/
|
||||
[opengarage docs]: /components/opengarage/
|
||||
[openuv docs]: /components/openuv/
|
||||
[pi_hole docs]: /components/pi_hole/
|
||||
[plex docs]: /components/plex/
|
||||
[point docs]: /components/point/
|
||||
[qld_bushfire docs]: /components/qld_bushfire/
|
||||
[radiotherm docs]: /components/radiotherm/
|
||||
[recorder docs]: /components/recorder/
|
||||
[rflink docs]: /components/rflink/
|
||||
[slide docs]: /components/slide/
|
||||
[sma docs]: /components/sma/
|
||||
[smartthings docs]: /components/smartthings/
|
||||
[solaredge docs]: /components/solaredge/
|
||||
[solaredge_local docs]: /components/solaredge_local/
|
||||
[solax docs]: /components/solax/
|
||||
[sql docs]: /components/sql/
|
||||
[supla docs]: /components/supla/
|
||||
[switch docs]: /components/switch/
|
||||
[tellstick docs]: /components/tellstick/
|
||||
[template docs]: /components/template/
|
||||
[tensorflow docs]: /components/tensorflow/
|
||||
[tibber docs]: /components/tibber/
|
||||
[trend docs]: /components/trend/
|
||||
[tuya docs]: /components/tuya/
|
||||
[uk_transport docs]: /components/uk_transport/
|
||||
[unifi docs]: /components/unifi/
|
||||
[upc_connect docs]: /components/upc_connect/
|
||||
[upnp docs]: /components/upnp/
|
||||
[usgs_earthquakes_feed docs]: /components/usgs_earthquakes_feed/
|
||||
[velbus docs]: /components/velbus/
|
||||
[venstar docs]: /components/venstar/
|
||||
[vicare docs]: /components/vicare/
|
||||
[vivotek docs]: /components/vivotek/
|
||||
[webhook docs]: /components/webhook/
|
||||
[withings docs]: /components/withings/
|
||||
[wwlln docs]: /components/wwlln/
|
||||
[xiaomi docs]: /components/xiaomi/
|
||||
[yeelight docs]: /components/yeelight/
|
||||
[zha docs]: /components/zha/
|
||||
[zhong_hong docs]: /components/zhong_hong/
|
||||
[zwave docs]: /components/zwave/
|
||||
@ -13,11 +13,14 @@ On the SSH command line, you can use the `hassio` command to retrieve logs, chec
|
||||
## Home Assistant
|
||||
|
||||
```bash
|
||||
$ hassio homeassistant check
|
||||
$ hassio homeassistant info
|
||||
$ hassio homeassistant logs
|
||||
$ hassio homeassistant check
|
||||
$ hassio homeassistant options
|
||||
$ hassio homeassistant rebuild
|
||||
$ hassio homeassistant restart
|
||||
$ hassio homeassistant start
|
||||
$ hassio homeassistant stats
|
||||
$ hassio homeassistant stop
|
||||
$ hassio homeassistant update
|
||||
```
|
||||
|
||||
@ -15,8 +15,8 @@ The following will take you through the steps required to install Hass.io.
|
||||
- [Raspberry Pi 2 Model B][pi2]
|
||||
- [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] (recommended)
|
||||
- [Raspberry Pi 3 Model B and B+ 64bit][pi3-64]
|
||||
- [(Beta) Raspberry Pi 4 Model B 32bit][pi4-32] (recommended)
|
||||
- [(Beta) Raspberry Pi 4 Model B 64bit][pi4-64]
|
||||
- [(RC) Raspberry Pi 4 Model B 32bit][pi4-32] (recommended)
|
||||
- [(RC) Raspberry Pi 4 Model B 64bit][pi4-64]
|
||||
- [Tinkerboard][tinker]
|
||||
- [Odroid-C2][odroid-c2]
|
||||
- [Odroid-XU4][odroid-xu4]
|
||||
@ -180,7 +180,7 @@ curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/mast
|
||||
- `raspberrypi3-64`
|
||||
- `odroid-c2`
|
||||
- `odroid-cu2`
|
||||
- `odriod-xu`
|
||||
- `odroid-xu`
|
||||
- `orangepi-prime`
|
||||
|
||||
<div class='note'>
|
||||
@ -197,8 +197,8 @@ A detailed guide about running Hass.io as a virtual machine is available in the
|
||||
[pi2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi2-2.12.img.gz
|
||||
[pi3-32]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-2.12.img.gz
|
||||
[pi3-64]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-64-2.12.img.gz
|
||||
[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.4/hassos_rpi4-3.4.img.gz
|
||||
[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.4/hassos_rpi4-64-3.4.img.gz
|
||||
[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.5/hassos_rpi4-3.5.img.gz
|
||||
[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.5/hassos_rpi4-64-3.5.img.gz
|
||||
[tinker]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_tinker-2.12.img.gz
|
||||
[odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-c2-2.12.img.gz
|
||||
[odroid-xu4]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-xu4-2.12.img.gz
|
||||
|
||||
BIN
source/images/blog/2019-09-0.99/components.png
Normal file
BIN
source/images/blog/2019-09-0.99/components.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
BIN
source/images/blog/2019-09-0.99/device-automation-trigger.png
Normal file
BIN
source/images/blog/2019-09-0.99/device-automation-trigger.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.2 KiB |
BIN
source/images/blog/2019-09-0.99/devices.png
Normal file
BIN
source/images/blog/2019-09-0.99/devices.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.3 KiB |
BIN
source/images/blog/2019-09-0.99/round-slider.png
Normal file
BIN
source/images/blog/2019-09-0.99/round-slider.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.2 KiB |
BIN
source/images/blog/2019-09-0.99/unused-entities.png
Normal file
BIN
source/images/blog/2019-09-0.99/unused-entities.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.2 KiB |
BIN
source/images/blog/2019-09-birthday/social.png
Normal file
BIN
source/images/blog/2019-09-birthday/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 219 KiB |
BIN
source/images/blog/2019-09-birthday/top.png
Normal file
BIN
source/images/blog/2019-09-birthday/top.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
Loading…
x
Reference in New Issue
Block a user