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

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2020-01-03 12:33:57 +01:00
commit 3a573899ff
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
34 changed files with 180 additions and 159 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Gemfile
View File

@ -18,7 +18,7 @@ group :jekyll_plugins do
gem 'jekyll-commonmark', '1.3.1' gem 'jekyll-commonmark', '1.3.1'
end end
gem 'sinatra', '2.0.7' gem 'sinatra', '2.0.8.1'
gem 'nokogiri', '1.10.7' gem 'nokogiri', '1.10.7'
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem

12
Gemfile.lock
View File

@ -70,7 +70,8 @@ GEM
mercenary (0.3.6) mercenary (0.3.6)
mini_portile2 (2.4.0) mini_portile2 (2.4.0)
multi_json (1.14.1) multi_json (1.14.1)
mustermann (1.0.3) mustermann (1.1.0)
ruby2_keywords (~> 0.0.1)
nokogiri (1.10.7) nokogiri (1.10.7)
mini_portile2 (~> 2.4.0) mini_portile2 (~> 2.4.0)
nokogiri (1.10.7-x64-mingw32) nokogiri (1.10.7-x64-mingw32)
@ -79,7 +80,7 @@ GEM
forwardable-extended (~> 2.6) forwardable-extended (~> 2.6)
public_suffix (4.0.1) public_suffix (4.0.1)
rack (2.0.8) rack (2.0.8)
rack-protection (2.0.7) rack-protection (2.0.8.1)
rack rack
rake (13.0.1) rake (13.0.1)
rb-fsevent (0.10.3) rb-fsevent (0.10.3)
@ -88,6 +89,7 @@ GEM
rouge (3.13.0) rouge (3.13.0)
ruby-enum (0.7.2) ruby-enum (0.7.2)
i18n i18n
ruby2_keywords (0.0.1)
safe_yaml (1.0.5) safe_yaml (1.0.5)
sass (3.4.25) sass (3.4.25)
sass-globbing (1.1.5) sass-globbing (1.1.5)
@ -96,10 +98,10 @@ GEM
ffi (~> 1.9) ffi (~> 1.9)
sassc (2.2.1-x64-mingw32) sassc (2.2.1-x64-mingw32)
ffi (~> 1.9) ffi (~> 1.9)
sinatra (2.0.7) sinatra (2.0.8.1)
mustermann (~> 1.0) mustermann (~> 1.0)
rack (~> 2.0) rack (~> 2.0)
rack-protection (= 2.0.7) rack-protection (= 2.0.8.1)
tilt (~> 2.0) tilt (~> 2.0)
stringex (2.8.5) stringex (2.8.5)
terminal-table (1.8.0) terminal-table (1.8.0)
@ -126,7 +128,7 @@ DEPENDENCIES
nokogiri (= 1.10.7) nokogiri (= 1.10.7)
rake (= 13.0.1) rake (= 13.0.1)
sass-globbing (= 1.1.5) sass-globbing (= 1.1.5)
sinatra (= 2.0.7) sinatra (= 2.0.8.1)
stringex (= 2.8.5) stringex (= 2.8.5)
tzinfo (~> 2.0) tzinfo (~> 2.0)
tzinfo-data tzinfo-data

4
_config.yml
View File

@ -101,8 +101,8 @@ social:
# Home Assistant release details # Home Assistant release details
current_major_version: 0 current_major_version: 0
current_minor_version: 103 current_minor_version: 103
current_patch_version: 4 current_patch_version: 5
date_released: 2019-12-22 date_released: 2019-12-28
# Either # or the anchor link to latest release notes in the blog post. # Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it. # Must be prefixed with a # and have double quotes around it.

60
source/_addons/google_assistant.markdown
View File

@ -4,12 +4,6 @@ description: "Enhance your Hass.io installation with Google Assistant."
featured: true featured: true
--- ---
<div class='note warning'>
These instructions are outdated - the add-on has been updated and these are no longer accurate or complete.
</div>
<div class='note'> <div class='note'>
If you want to integrate your Google Home or mobile phone running Google Assistant, with Home Assistant, then you want the [Google Assistant component](/integrations/google_assistant/). If you want to integrate your Google Home or mobile phone running Google Assistant, with Home Assistant, then you want the [Google Assistant component](/integrations/google_assistant/).
@ -23,36 +17,11 @@ To enable access to the Google Assistant API, do the following:
1. In the [Cloud Platform Console][project], go to the Projects page. Select an existing project or create a new project 1. In the [Cloud Platform Console][project], go to the Projects page. Select an existing project or create a new project
1. Open the project. In the top of the page search for Google Assistant API or use [this link][API] and enable it. 1. Open the project. In the top of the page search for Google Assistant API or use [this link][API] and enable it.
1. Create an [OAuth Client ID][oauthclient], pick type "Other", click "Create" and download the JSON file by clicking the Download JSON button on the right side. 1. Create an [OAuth Client ID][oauthclient], pick type "Other", click "Create" and download the JSON file by clicking the Download JSON button on the right side.
1. Upload your "google_assistant.json" file to the "hassio/share" folder, for example by using the [Samba] add-on.
1. In the config window, fill in your "project-id", which can be found in your "google_assistant.json" file or in on the [Cloud Platform Resource Manager][cloudConsole]. Also choose a "model_id".
1. Below the "Config" window select the microphone and speaker that you want to use. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port.
Now install and activate the [Samba] add-on so you can upload your credential file. Connect to the "share" Samba share and copy your credentials over. Name the file `google_assistant.json`. You are now ready to start the add-on. The next step is to authenticate your Google account with Google Assistant. After starting the add-on and click on the "OPEN WEB UI" button to start authentication.
Now it's time to start Google Assistant for the first time. When the Google Assistant add-on starts, it will output your audio devices in the "Logs" card. You might have to hit "refresh" to get the latest logs:
```text
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Microphone [Yeti Stereo Microphone], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
```
You need to use this information to point the add-on at the right speakers and microphone. The information describes different cards and devices. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port. In the example above, the USB microphone showed up as card 1 - device 0.
Find the microphone and speakers that you want to use and note down their device and card number. We will need that to configure the add-on options `mic` (microphone to use) and `speaker` (speaker to use). The format for these options is `<card #>,<device #>`. Change the configuration options and click save.
The next step is to authenticate your Google account with Google Assistant. Start the add-on and click on the "OPEN WEB UI" button to start authentication.
### Add-on configuration ### Add-on configuration
@ -60,19 +29,23 @@ Configuration example that uses the USB microphone and the built-in headset audi
```json ```json
{ {
"mic": "1,0", "client_secrets": "google_assistant.json",
"speaker": "0,0", "project_id": null,
"client_secrets": "google_assistant.json" "model_id": null
} }
``` ```
{% configuration %} {% configuration %}
mic: client_secrets:
description: This is the hardware address of your microphone. Look at the add-on output. description: The file downloaded from the Google Cloud Platform Console - Google Assistant API page. By default the add-on look in the "hassio/share" folder.
required: true required: true
type: float type: string
speaker: project_id:
description: This is the hardware address of your speakers. Look at the add-on output. description: The project id can be found in your "google_assistant.json" file.
required: true
type: string
model_id:
description: A chosen model_id.
required: true required: true
type: string type: string
{% endconfiguration %} {% endconfiguration %}
@ -88,3 +61,4 @@ Use the Home Assistant [DialogFlow component][comp] to integrate the add-on into
[project]: https://console.cloud.google.com/project [project]: https://console.cloud.google.com/project
[API]: https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview [API]: https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview
[oauthclient]: https://console.developers.google.com/apis/credentials/oauthclient [oauthclient]: https://console.developers.google.com/apis/credentials/oauthclient
[cloudConsole]: https://console.cloud.google.com/cloud-resource-manager

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

@ -216,7 +216,7 @@ automation:
trigger: trigger:
platform: numeric_state platform: numeric_state
entity_id: sun.sun entity_id: sun.sun
value_template: "{{ state.attributes.elevation }}" value_template: "{{ state_attr('sun.sun', 'elevation') }}"
# Can be a positive or negative number # Can be a positive or negative number
below: -4.0 below: -4.0
action: action:

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

@ -184,12 +184,17 @@ pkg install libudev-devd
Then you can install the zwave package Then you can install the zwave package
```bash ```bash
pip3 install homeassistant-pyozw==0.1.4 su homeassistant
cd /usr/local/share/homeassistant
source ./bin/activate.csh
pip3 install homeassistant-pyozw==0.1.7
deactivate
exit
``` ```
Stop the hass Jail Stop the hass Jail
```bash ```bash
sudo iocage stop hass sudo iocage stop HomeAssistant
``` ```
Edit the devfs rules on the Freenas Host Edit the devfs rules on the Freenas Host
@ -213,12 +218,12 @@ Set it to 7
Start the hass jail Start the hass jail
```bash ```bash
sudo iocage start hass sudo iocage start HomeAssistant
``` ```
Connect to the hass jail and verify that you see the modem devices Connect to the hass jail and verify that you see the modem devices
```bash ```bash
sudo iocage console hass sudo iocage console HomeAssistant
``` ```
```bash ```bash

8
source/_docs/installation/raspberry-pi.markdown
View File

@ -67,22 +67,22 @@ cd /srv/homeassistant
python3 -m venv . python3 -m venv .
source bin/activate source bin/activate
``` ```
Once you have activated the virtual environment (notice the prompt change) you will need to run the following command to install a required python package. Once you have activated the virtual environment (notice the prompt change to `(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $`) you will need to run the following command to install a required python package.
```bash ```bash
(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ python3 -m pip install wheel python3 -m pip install wheel
``` ```
Once you have installed the required python package it is now time to install Home Assistant! Once you have installed the required python package it is now time to install Home Assistant!
```bash ```bash
(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ pip3 install homeassistant pip3 install homeassistant
``` ```
Start Home Assistant for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies. Start Home Assistant for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies.
```bash ```bash
(homeassistant) $ hass hass
``` ```
You can now reach your installation on your Raspberry Pi over the web interface on `http://ipaddress:8123`. You can now reach your installation on your Raspberry Pi over the web interface on `http://ipaddress:8123`.

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

@ -16,7 +16,7 @@ mqtt:
{% configuration %} {% configuration %}
certificate: certificate:
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`." 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 'certificate' 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 required: false
type: string type: string
client_key: client_key:

4
source/_docs/z-wave/control-panel.markdown
View File

@ -78,11 +78,11 @@ Battery powered devices need to be awake before you can use the Z-Wave control p
This is a dropdown where you can select all the entities of this node. Once selected you can then use: This is a dropdown where you can select all the entities of this node. Once selected you can then use:
* **Refresh Entity** to refresh just that entity's values * **Refresh Entity** to refresh just that entity's values
* **Entity Attributes** to display the attributes of that entity (e.g., its friendly name, the ID of the node, etc) * **Entity Information** to display the attributes of that entity (e.g., its friendly name, the ID of the node, etc)
Here you can mark a device as requiring polling so the controller is aware of changes because the device doesn't send updates itself. Do see the information on [polling here](/docs/z-wave/devices/#polling), since excessive polling can break your Z-Wave network. Here you can mark a device as requiring polling so the controller is aware of changes because the device doesn't send updates itself. Do see the information on [polling here](/docs/z-wave/devices/#polling), since excessive polling can break your Z-Wave network.
The **Polling intensity** says how many poll intervals does is this device polled on. For example, if you set 2 then it's polled on every second interval. The **Polling intensity** says how many poll intervals this device is polled on. For example, if you set 2 then it's polled on every second interval.
You can also exclude a Z-Wave devices from Home Assistant. You can do that if you have a device that you need to have on the Z-Wave network, but you don't want it to appear in Home Assistant, or if you've got a device that's failed and you're unable to exclude it. You can also exclude a Z-Wave devices from Home Assistant. You can do that if you have a device that you need to have on the Z-Wave network, but you don't want it to appear in Home Assistant, or if you've got a device that's failed and you're unable to exclude it.

15
source/_docs/z-wave/installation.markdown
View File

@ -122,7 +122,7 @@ You can also check what hardware has been found using the [hassio command](/hass
$ hassio hardware info $ hassio hardware info
``` ```
If you did an alternative install on Linux then the `modemmanager` package will interfere with any Z-Wave (or Zigbee) stick and should be removed or disabled. Failure to do so will result in random failures of those components. For example you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager`. If you did an alternative install of Hass.io on Linux (e.g. installing Ubuntu, then Docker, then Hass.io) then the `modemmanager` package will interfere with any Z-Wave (or Zigbee) stick and should be removed or disabled in the host OS. Failure to do so will result in random failures of those components, e.g. dead or unreachable Z-Wave nodes, most notably right after HomeAssistant restarts. Connect to your host OS via SSH, then you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager` (commands are for Debian/Ubuntu).
### Docker ### Docker
@ -153,7 +153,7 @@ On the Raspberry Pi you will need to enable the serial interface in the `raspi-c
On Debian Linux platforms there are dependencies you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems): On Debian Linux platforms there are dependencies you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems):
```bash ```bash
$ sudo apt-get install libudev-dev $ sudo apt-get install libudev-dev build-essential
``` ```
You may also have to install the Python development libraries for your version of Python. For example `libpython3.6-dev`, and possibly `python3.6-dev` if you're using Python 3.6. You may also have to install the Python development libraries for your version of Python. For example `libpython3.6-dev`, and possibly `python3.6-dev` if you're using Python 3.6.
@ -215,13 +215,16 @@ ls /dev/cu.usbmodem*
If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it. If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it.
## Ubuntu and Debian based host system ## Random unreachable Z-Wave nodes: ModemManager interference
If your instance is running on a Debian based system, e.g., Ubuntu, the ModemManager may cause unexpected issues. If this applies to your situation:
- Some or all Z-Wave nodes are unreachable after restarting Home Assistant; not necessarily after every restart but seemingly random.
- The Z-Wave stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back.
- Your host OS is Debian-based/Ubuntu (for example: you installed Ubuntu, then Docker, then Hass.io).
The ModemManager might be claiming or interfering with a USB Z-Wave stick, like the much used Aeotec ones. If you experience issues where the stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back, chances are high that the ModemManager is causing the issue. Then chances are high that the ModemManager in the host OS is causing the issue, claiming or interfering with the USB Z-Wave stick like the much used Aeotec ones. In this case you need to disable ModemManager.
Execute the following command on your host system to disable the ModemManager: Connect to your host OS (e.g. Ubuntu) through SSH, then execute the following command on your host system to disable the ModemManager:
```bash ```bash
systemctl disable ModemManager.service systemctl disable ModemManager.service

2
source/_faq/ha-vs-hassio.markdown
View File

@ -4,7 +4,7 @@ description: "Home Assistant vs. Hass.io"
ha_category: Installation ha_category: Installation
--- ---
Home Assistant is a Python program, in simple words. It can be run various operating system and provide the ability to track, control and automate your devices. When people talking about Home Assistant they usually refer to a standalone [installation method](/docs/installation/). Home Assistant is a Python program, in simple words. It can be run on various operating systems and provide the ability to track, control and automate your devices. When people talking about Home Assistant they usually refer to a standalone [installation method](/docs/installation/).
[Hass.io](/hassio/) is a combination of Home Assistant and tools which allows one to run it easily on a Raspberry Pi and other platforms without setting up an operating system first. Hass.io is an all-in one-solution and has a management user interface that can be used from the Home Assistant frontend. This interface is not present in a standalone setup of Home Assistant. [Hass.io](/hassio/) is a combination of Home Assistant and tools which allows one to run it easily on a Raspberry Pi and other platforms without setting up an operating system first. Hass.io is an all-in one-solution and has a management user interface that can be used from the Home Assistant frontend. This interface is not present in a standalone setup of Home Assistant.

7
source/_integrations/alexa.intent.markdown
View File

@ -19,7 +19,7 @@ The built-in Alexa integration allows you to integrate Home Assistant into Alexa
- Amazon Developer Account. You can sign on [here](https://developer.amazon.com). - Amazon Developer Account. You can sign on [here](https://developer.amazon.com).
- An [AWS account](https://aws.amazon.com/free/) is need if you want to use Alexa Custom Skill API. Part of your Alexa Custom Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However you don't need worry the cost, AWS Lambda allow free to use up to 1 millions requests and 1GB outbound data transfer per month. - An [AWS account](https://aws.amazon.com/free/) is need if you want to use Alexa Custom Skill API. Part of your Alexa Custom Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However you don't need worry the cost, AWS Lambda allow free to use up to 1 millions requests and 1GB outbound data transfer per month.
- The Alexa Custom Skill API also needs your Home Assistant instance can be accessed from Internet. We strongly suggest you host HTTPS server and use validation certificate. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method. - The Alexa Custom Skill API also needs your Home Assistant instance to be accessible from the internet via HTTPS on port 443 using a certificate signed by [an Amazon approved certificate authority](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport), this is so account linking can take place. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method.
### Create Your Amazon Alexa Custom Skill ### Create Your Amazon Alexa Custom Skill
@ -94,8 +94,9 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom
- Find the skill you just created and click `Edit` in the `Actions` column. - Find the skill you just created and click `Edit` in the `Actions` column.
- Click `ACCOUNT LINKING` in the left navigation bar of build page - Click `ACCOUNT LINKING` in the left navigation bar of build page
- Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT] - Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT]
* `Authorization URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize * `Authorization URI`: https://[YOUR HOME ASSISTANT URL]/auth/authorize
* `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token * `Access Token URI`: https://[YOUR HOME ASSISTANT URL]/auth/token
- Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work
* `Client ID`: * `Client ID`:
- https://pitangui.amazon.com/ if you are in US - https://pitangui.amazon.com/ if you are in US
- https://layla.amazon.com/ if you are in EU - https://layla.amazon.com/ if you are in EU

6
source/_integrations/alexa.smart_home.markdown
View File

@ -37,7 +37,7 @@ For Home Assistant Cloud Users, documentation can be found [here](https://www.na
- Amazon Developer Account. You can sign on [here](https://developer.amazon.com). - Amazon Developer Account. You can sign on [here](https://developer.amazon.com).
- An [AWS account](https://aws.amazon.com/free/) is need if you want to use Smart Home Skill API. Part of your Smart Home Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However you don't need worry the cost, AWS Lambda allow free to use up to 1 millions requests and 1GB outbound data transfer per month. - An [AWS account](https://aws.amazon.com/free/) is need if you want to use Smart Home Skill API. Part of your Smart Home Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However you don't need worry the cost, AWS Lambda allow free to use up to 1 millions requests and 1GB outbound data transfer per month.
- Smart Home API also needs your Home Assistant instance can be accessed from Internet. We strongly suggest you host HTTPS server and use validation certificate. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method. - The Smart Home API also needs your Home Assistant instance to be accessible from the internet via HTTPS on port 443 using a certificate signed by [an Amazon approved certificate authority](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport), this is so account linking can take place. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method.
### Create Your Amazon Alexa Smart Home Skill ### Create Your Amazon Alexa Smart Home Skill
@ -171,8 +171,8 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom
- Find the skill you just created, click `Edit` link in the `Actions` column. - Find the skill you just created, click `Edit` link in the `Actions` column.
- Click `ACCOUNT LINKING` in the left navigation bar of build page - Click `ACCOUNT LINKING` in the left navigation bar of build page
- Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT] - Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT]
* `Authorization URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize * `Authorization URI`: https://[YOUR HOME ASSISTANT URL]/auth/authorize
* `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token * `Access Token URI`: https://[YOUR HOME ASSISTANT URL]/auth/token
- Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work - Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work
* `Client ID`: * `Client ID`:
- https://pitangui.amazon.com/ if you are in US - https://pitangui.amazon.com/ if you are in US

18
source/_integrations/climate.markdown
View File

@ -28,7 +28,7 @@ Turn auxiliary heater on/off for climate device
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `aux_heat` | no | New value of auxiliary heater. | `aux_heat` | no | New value of auxiliary heater.
#### Automation example #### Automation example
@ -53,7 +53,7 @@ reflecting a situation where the climate device is set to save energy. For examp
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `preset_mode` | no | New value of preset mode. | `preset_mode` | no | New value of preset mode.
#### Automation example #### Automation example
@ -76,7 +76,7 @@ Set target temperature of climate device
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `temperature` | no | New target temperature for climate device (commonly referred to as a *setpoint*). Do not use if `hvac_mode` is `heat_cool`. | `temperature` | no | New target temperature for climate device (commonly referred to as a *setpoint*). Do not use if `hvac_mode` is `heat_cool`.
| `target_temp_high` | yes | The highest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. | `target_temp_high` | yes | The highest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`.
| `target_temp_low` | yes | The lowest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. | `target_temp_low` | yes | The lowest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`.
@ -119,7 +119,7 @@ Set target humidity of climate device
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `humidity` | no | New target humidity for climate device | `humidity` | no | New target humidity for climate device
#### Automation example #### Automation example
@ -142,7 +142,7 @@ Set fan operation for climate device
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `fan_mode` | no | New value of fan mode | `fan_mode` | no | New value of fan mode
#### Automation example #### Automation example
@ -165,7 +165,7 @@ Set climate device's HVAC mode
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `hvac_mode` | no | New value of HVAC mode | `hvac_mode` | no | New value of HVAC mode
#### Automation example #### Automation example
@ -188,7 +188,7 @@ Set swing operation mode for climate device
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
| `swing_mode` | no | New value of swing mode | `swing_mode` | no | New value of swing mode
#### Automation example #### Automation example
@ -211,7 +211,7 @@ Turn climate device on. This is only supported if the climate device supports be
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.
### Service `climate.turn_off` ### Service `climate.turn_off`
@ -219,4 +219,4 @@ Turn climate device off. This is only supported if the climate device has the hv
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`.

2
source/_integrations/discovery.markdown
View File

@ -47,7 +47,7 @@ Zeroconf discoverable integrations [Axis](/integrations/axis/)/[ESPHome](/integr
</div> </div>
`discovery` is included in the defalult configuration. To load this component manually, add the following lines to your `configuration.yaml` file: `discovery` is included in the default configuration. To load this component manually, add the following lines to your `configuration.yaml` file:
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

2
source/_integrations/fastdotcom.markdown
View File

@ -75,6 +75,6 @@ action:
## Notes ## Notes
- When running on Raspberry Pi, the maximum speed is limited by its 100 Mbit/s LAN adapter. - When running on Raspberry Pi 3 or older, the maximum speed is limited by its 100 Mbit/s LAN adapter.
- The sensor will return the maximum measured speed during a 15-second test. - The sensor will return the maximum measured speed during a 15-second test.
- Speed tests consume data depending on your internet speed, make sure to consider this if your internet connection has limited bandwidth. - Speed tests consume data depending on your internet speed, make sure to consider this if your internet connection has limited bandwidth.

2
source/_integrations/homekit.markdown
View File

@ -459,7 +459,7 @@ To use the HomeKit integration with to different Home Assistant instances on the
#### Specific entity doesn't work #### Specific entity doesn't work
Although we try our best, some entities don't work with the HomeKit integration yet. The result will be that either pairing fails completely or all Home Assistant accessories will stop working. Use the filter to identify which entity is causing the issue. It's best to try pairing and step by step including more entities. If it works unpair and repeat until you find the one that is causing the issues. To help others and the developers, please open a new issue here: [home-assistant/issues/new](https://github.com/home-assistant/home-assistant/issues/new?labels=component: homekit) Although we try our best, some entities don't work with the HomeKit integration yet. The result will be that either pairing fails completely or all Home Assistant accessories will stop working. Use the filter to identify which entity is causing the issue. It's best to try pairing and step by step including more entities. If it works unpair and repeat until you find the one that is causing the issues. To help others and the developers, please open a new issue here: [home-assistant/issues/new](https://github.com/home-assistant/home-assistant/issues/new?labels=component:%20homekit)
#### Accessories are all listed as not responding #### Accessories are all listed as not responding

12
source/_integrations/html5.markdown
View File

@ -54,15 +54,15 @@ name:
type: string type: string
default: notify default: notify
vapid_pub_key: vapid_pub_key:
description: The VAPID public key generated by Google (this is the key that is immediately visible under "webpush certificates"). description: The VAPID public key generated by Google (this is the key that is immediately visible under "webpush certificates"), [see configuring the platform](#configuring_the_platform).
required: true required: true
type: string type: string
vapid_prv_key: vapid_prv_key:
description: The VAPID private key generated by Google. description: The VAPID private key generated by Google, [see configuring the platform](#configuring_the_platform).
required: true required: true
type: string type: string
vapid_email: vapid_email:
description: The e-mail account associated with your Firebase project. description: The e-mail account associated with your Firebase project, [see configuring the platform](#configuring_the_platform).
required: true required: true
type: string type: string
gcm_api_key: gcm_api_key:
@ -80,7 +80,7 @@ gcm_sender_id:
The `html5` platform can only function if all of the following requirements are met: The `html5` platform can only function if all of the following requirements are met:
* You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android. * You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android.
* Your Home Assistant instance is accessible from outside your network over HTTPS. * Your Home Assistant instance is accessible from outside your network over HTTPS or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
* If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards. * If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.
* If you don't run Hass.io: `pywebpush` must be installed. `libffi-dev`, `libpython-dev` and `libssl-dev` must be installed prior to `pywebpush` (i.e. `pywebpush` probably won't automatically install). * If you don't run Hass.io: `pywebpush` must be installed. `libffi-dev`, `libpython-dev` and `libssl-dev` must be installed prior to `pywebpush` (i.e. `pywebpush` probably won't automatically install).
* You have configured SSL/TLS for your Home Assistant. It doesn't need to be configured in Home Assistant though, e.g., you can be running [NGINX](/ecosystem/nginx/) in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed). * You have configured SSL/TLS for your Home Assistant. It doesn't need to be configured in Home Assistant though, e.g., you can be running [NGINX](/ecosystem/nginx/) in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed).
@ -88,8 +88,8 @@ The `html5` platform can only function if all of the following requirements are
### Configuring the platform ### Configuring the platform
1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see docs](/docs/configuration/remote/)). 1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see docs](/docs/configuration/remote/)) or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). 2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard), this project will be imported into Firebase later (alternatively, the project can also be created during step 4).
3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [see below](#verify-your-domain). 3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [see below](#verify-your-domain).
4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project and select the project you created. 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project and select the project you created.
5. Then, click the cogwheel on top left and select "Project settings". 5. Then, click the cogwheel on top left and select "Project settings".

12
source/_integrations/hunterdouglas_powerview.markdown
View File

@ -24,3 +24,15 @@ address:
required: true required: true
type: string type: string
{% endconfiguration %} {% endconfiguration %}
## Example Automations
``` yaml
- alias: "blinds closed at night"
trigger:
platform: time
at: "18:00:00"
action:
- service: scene.turn_on
entity_id: scene.10877
```

14
source/_integrations/integration.markdown
View File

@ -10,7 +10,7 @@ logo: integral.png
ha_qa_scale: internal ha_qa_scale: internal
--- ---
The `integration` platform provides the [Riemann sum](https://en.wikipedia.org/wiki/Riemann_sum) of the values provided by a source sensor. The Riemann sum is an approximation of an **integral** by a finite sum. The integration sensors is updated upon changes of the the **source**. Fast sampling source sensors provide better results. In this implementation, the default is the Trapezoidal method, but Left and Right methods can optionally be used. The `integration` platform provides the [Riemann sum](https://en.wikipedia.org/wiki/Riemann_sum) of the values provided by a source sensor. The Riemann sum is an approximation of an **integral** by a finite sum. The integration sensors is updated upon changes of the **source**. Fast sampling source sensors provide better results. In this implementation, the default is the Trapezoidal method, but Left and Right methods can optionally be used.
## Configuration ## Configuration
@ -25,7 +25,7 @@ sensor:
{% configuration %} {% configuration %}
source: source:
description: The entity ID of the sensor providing numeric readings description: The entity ID of the sensor providing numeric readings.
required: true required: true
type: string type: string
name: name:
@ -39,27 +39,27 @@ round:
default: 3 default: 3
type: integer type: integer
unit_prefix: unit_prefix:
description: Metric unit to prefix the integration result. Available units are k, M, G, T. description: "Metric unit to prefix the integration result. Available units are `k`, `M`, `G` and `T`."
required: false required: false
default: None default: None
type: string type: string
unit_time: unit_time:
description: SI unit of time to integrate over. Available units are s, min, h, d. description: "SI unit of time to integrate over. Available units are `s`, `min`, `h` and `d`."
required: false required: false
default: h default: h
type: string type: string
unit: unit:
description: Unit of Measurement to be used for the integration. description: Unit of measurement to be used for the integration.
required: false required: false
type: string type: string
method: method:
description: Riemann sum method to be used. Available methods are trapezoidal, left, right. description: Riemann sum method to be used. Available methods are `trapezoidal`, `left` and `right`."
required: false required: false
type: string type: string
default: trapezoidal default: trapezoidal
{% endconfiguration %} {% endconfiguration %}
If 'unit' is set then 'unit_prefix' and 'unit_time' are ignored. In case you have an appliance which produces spikey consumption (like an on/off electrical boiler) you should opt for the `left` method to get accurate readings. If `unit` is set then `unit_prefix` and `unit_time` are ignored.
## Energy ## Energy

4
source/_integrations/light.markdown
View File

@ -24,7 +24,7 @@ Most lights do not support all attributes. You can check the integration documen
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`s of lights. Else targets all. | `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all the lights use all as `entity_id`.
| `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state. | `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state.
| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten. | `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten.
| `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100. | `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100.
@ -82,7 +82,7 @@ Turns one or multiple lights off.
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`s of lights. Else targets all. | `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all the lights use all as `entity_id`.
| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds. | `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds.
### Service `light.toggle` ### Service `light.toggle`

2
source/_integrations/limitlessled.markdown
View File

@ -8,7 +8,7 @@ ha_iot_class: Assumed State
ha_release: pre 0.7 ha_release: pre 0.7
--- ---
`limitlessled` can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, [MiLight](https://www.milight.com/), LEDme, dekolight, or iLight. `limitlessled` can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight, or iLight.
LimitlessLED bulbs are controlled via groups, so you can only control an individual bulb via the bridge if it is in a group by itself. LimitlessLED bulbs are controlled via groups, so you can only control an individual bulb via the bridge if it is in a group by itself.

12
source/_integrations/media_player.markdown
View File

@ -17,34 +17,34 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ------------------------------------------------ | | ---------------------- | -------- | ------------------------------------------------ |
| `entity_id` | yes | Target a specific media player. Defaults to all. | | `entity_id` | no | Target a specific media player. To target all media players, use `all`. |
#### Service `media_player.volume_mute` #### Service `media_player.volume_mute`
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
|------------------------|----------|--------------------------------------------------| |------------------------|----------|--------------------------------------------------|
| `entity_id` | yes | Target a specific media player. Defaults to all. | | `entity_id` | no | Target a specific media player. To target all media players, use `all`. |
| `is_volume_muted` | no | True/false for mute/unmute | | `is_volume_muted` | no | True/false for mute/unmute |
#### Service `media_player.volume_set` #### Service `media_player.volume_set`
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
|------------------------|----------|--------------------------------------------------| |------------------------|----------|--------------------------------------------------|
| `entity_id` | yes | Target a specific media player. Defaults to all. | | `entity_id` | yes | Target a specific media player. To target all media players, use `all`. |
| `volume_level` | no | Float for volume level. Range 0..1 | | `volume_level` | no | Float for volume level. Range 0..1 |
#### Service `media_player.media_seek` #### Service `media_player.media_seek`
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
|------------------------|----------|--------------------------------------------------------| |------------------------|----------|--------------------------------------------------------|
| `entity_id` | yes | Target a specific media player. Defaults to all. | | `entity_id` | no | Target a specific media player. To target all media players, use `all`. |
| `seek_position` | no | Position to seek to. The format is platform dependent. | | `seek_position` | no | Position to seek to. The format is platform dependent. |
#### Service `media_player.play_media` #### Service `media_player.play_media`
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| -----------------------| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | -----------------------| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | yes | Target a specific media player. Defaults to all. | | `entity_id` | no | Target a specific media player. To target all media players, use `all`. |
| `media_content_id` | no | A media identifier. The format of this is integration dependent. For example, you can provide URLs to Sonos and Cast but only a playlist ID to iTunes. | | `media_content_id` | no | A media identifier. The format of this is integration dependent. For example, you can provide URLs to Sonos and Cast but only a playlist ID to iTunes. |
| `media_content_type` | no | A media type. Must be one of `music`, `tvshow`, `video`, `episode`, `channel` or `playlist`. For example, to play music you would set `media_content_type` to `music`. | | `media_content_type` | no | A media type. Must be one of `music`, `tvshow`, `video`, `episode`, `channel` or `playlist`. For example, to play music you would set `media_content_type` to `music`. |
@ -52,7 +52,7 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------------------------------- | | ---------------------- | -------- | ---------------------------------------------------- |
| `entity_id` | yes | Target a specific media player. Defaults to all. | | `entity_id` | no | Target a specific media player. To target all media players, use `all`. |
| `source` | no | Name of the source to switch to. Platform dependent. | | `source` | no | Name of the source to switch to. Platform dependent. |
#### Service `media_player.select_sound_mode` #### Service `media_player.select_sound_mode`

2
source/_integrations/proxmoxve.markdown
View File

@ -97,6 +97,6 @@ proxmoxve:
## Binary Sensor ## Binary Sensor
The integration will automatically create a binary sensor for each tracked virtual machone or container. The binary sensor will either be on if the VM's state is running or off if the VM's state is different. The integration will automatically create a binary sensor for each tracked virtual machine or container. The binary sensor will either be on if the VM's state is running or off if the VM's state is different.
The created sensor will be called `binary_sensor.NODE_NAME_VMNAME_running`. The created sensor will be called `binary_sensor.NODE_NAME_VMNAME_running`.

17
source/_integrations/recorder.markdown
View File

@ -122,17 +122,18 @@ If you only want to hide events from your history, take a look at the [`history`
Call the service `recorder.purge` to start a purge task which deletes events and states older than x days, according to `keep_days` service data. Call the service `recorder.purge` to start a purge task which deletes events and states older than x days, according to `keep_days` service data.
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `keep_days` | yes | The number of history days to keep in recorder database (defaults to the integration `purge_keep_days` configuration) | `keep_days` | yes | The number of history days to keep in recorder database (defaults to the integration `purge_keep_days` configuration) |
| `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. | `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. |
## Custom database engines ## Custom database engines
| Database engine | `db_url` | | Database engine | `db_url` |
| :---------------|:---------------------------------------------------------| | :--------------------- | :------------------------------------------------------------------------------------------- |
| SQLite | `sqlite:////PATH/TO/DB_NAME` | | SQLite | `sqlite:////PATH/TO/DB_NAME` |
| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | | MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` |
| MariaDB         | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | | MariaDB | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| MariaDB (omit pymysql) | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` | | MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` |
| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | | MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | | PostgreSQL | `postgresql://SERVER_IP/DB_NAME` |
@ -148,6 +149,12 @@ Some installations of MariaDB/MySQL may require an ALTERNATE_PORT (3rd-party hos
<div class='note'> <div class='note'>
If using an external MariaDB backend (e.g., running on a separate NAS) with Home Assistant, you should omit `pymysql` from the URL. `pymysql` is not included in the base docker image, and is not necessary for this to work.
</div>
<div class='note'>
Unix Socket connections always bring performance advantages over TCP, if the database is on the same host as the `recorder` instance (i.e. `localhost`). Unix Socket connections always bring performance advantages over TCP, if the database is on the same host as the `recorder` instance (i.e. `localhost`).
</div> </div>

8
source/_integrations/rmvtransport.markdown
View File

@ -59,9 +59,9 @@ next_departure:
required: false required: false
type: [string, integer] type: [string, integer]
products: products:
description: "One or more modes of transport `['U-Bahn', 'Tram', 'Bus', 'S-Bahn', 'RB', 'RE', 'EC', 'IC', 'ICE']`." description: "One or more modes of transport `['U-Bahn', 'Tram', 'Bus', 'S', 'RB', 'RE', 'EC', 'IC', 'ICE']`."
required: false required: false
default: ['U-Bahn', 'Tram', 'Bus', 'S-Bahn', 'RB', 'RE', 'EC', 'IC', 'ICE'] default: ['U-Bahn', 'Tram', 'Bus', 'S', 'RB', 'RE', 'EC', 'IC', 'ICE']
type: [string] type: [string]
time_offset: time_offset:
description: Do not display departures leaving sooner than this number of minutes. Useful if you are a couple of minutes away from the stop. description: Do not display departures leaving sooner than this number of minutes. Useful if you are a couple of minutes away from the stop.
@ -97,7 +97,7 @@ sensor:
- 'RB' - 'RB'
- 'RE' - 'RE'
- 'Bus' - 'Bus'
- 'S-Bahn' - 'S'
- station: 3006907 - station: 3006907
products: 'Bus' products: 'Bus'
destinations: ['Wiesbaden Dernsches Gelände', 'Mainz Hauptbahnhof'] destinations: ['Wiesbaden Dernsches Gelände', 'Mainz Hauptbahnhof']
@ -105,7 +105,7 @@ sensor:
- station: 3006904 - station: 3006904
lines: 'S8' lines: 'S8'
max_journeys: 5 max_journeys: 5
products: 'S-Bahn' products: 'S'
``` ```
The first sensor will return S-Bahn, bus, RB and RE trains departures from Frankfurt Hauptbahnhof to Frankfurt Airport or Stadium that are at least 5 minutes away. The first sensor will return S-Bahn, bus, RB and RE trains departures from Frankfurt Hauptbahnhof to Frankfurt Airport or Stadium that are at least 5 minutes away.

24
source/_integrations/samsungtv.markdown
View File

@ -55,7 +55,17 @@ broadcast_address:
type: string type: string
{% endconfiguration %} {% endconfiguration %}
Currently known supported models: ### Supported models
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/samsungtv.markdown).
#### Naming
The first letter (U, P, L, H & K) represent the screen type, e.g., LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these first 4 characters before adding to the list.
For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North American, 55 inch TV, and the model number listed below would be the remainder: `NU7100`.
#### Models tested and working
- C7700 - C7700
- D5500 - D5500
@ -103,7 +113,7 @@ Currently known supported models:
- UE49KU6470 (port must be set to 8001, On/Off, Forward/Backward, Volume are OK, but no Play button) - UE49KU6470 (port must be set to 8001, On/Off, Forward/Backward, Volume are OK, but no Play button)
- UE46ES5500 (partially supported, turn on doesn't works) - UE46ES5500 (partially supported, turn on doesn't works)
Currently tested but not working models: #### Models tested but not yet working
- J5200 - Unable to see state and unable to control - J5200 - Unable to see state and unable to control
- J5500 - State is always "on" and unable to control (but port 8001 *is* open) - J5500 - State is always "on" and unable to control (but port 8001 *is* open)
@ -125,10 +135,9 @@ Currently tested but not working models:
None of the 2014 (H) and 2015 (J) model series (e.g., J5200) will work, since Samsung have used a different (encrypted) type of interface for these. None of the 2014 (H) and 2015 (J) model series (e.g., J5200) will work, since Samsung have used a different (encrypted) type of interface for these.
If your model is not on the list then give it a test, if everything works correctly then add it to the list on ### Usage
[GitHub](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/samsungtv.markdown).
The first letter (U, P, L, H & K) represent the screen type, e.g., LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size. #### Changing channels
If you add your model remember to remove these first 4 characters before adding to the list.
Changing channels can be done by calling the `media_player.play_media` service Changing channels can be done by calling the `media_player.play_media` service
with the following payload: with the following payload:
@ -140,8 +149,9 @@ with the following payload:
"media_content_type": "channel" "media_content_type": "channel"
} }
``` ```
#### Selecting a source
Currently the ability to select a source is not implemented. Source selection is not yet implemented.
### Hass.io ### Hass.io

2
source/_integrations/simplisafe.markdown
View File

@ -8,7 +8,7 @@ ha_category:
- Lock - Lock
--- ---
The `simplisafe` integration integrates SimpliSafe home security (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated. The `simplisafe` integration integrates [SimpliSafe home security](https://simplisafe.com) (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated.
There is currently support for the following device types within Home Assistant: There is currently support for the following device types within Home Assistant:

2
source/_integrations/stream.markdown
View File

@ -33,7 +33,7 @@ Both `duration` and `lookback` options are suggestions, but should be consistent
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
| `stream_source` | no | The input source for the stream, e.g., `rtsp://my.stream.feed:554`. | | `stream_source` | no | The input source for the stream, e.g., `rtsp://my.stream.feed:554`. |
| `filename` | no | The file name string. Variable is `entity_id`, e.g., `/tmp/my_stream.mp4`. | | `filename` | no | The file name string. e.g., `/tmp/my_stream.mp4`. |
| `duration` | yes | Target recording length (in seconds). Default: 30 | | `duration` | yes | Target recording length (in seconds). Default: 30 |
| `lookback` | yes | Target lookback period (in seconds) to include in addition to duration. Only available if there is currently an active HLS stream for `stream_source`. Default: 0 | | `lookback` | yes | Target lookback period (in seconds) to include in addition to duration. Only available if there is currently an active HLS stream for `stream_source`. Default: 0 |

6
source/_integrations/synologydsm.markdown
View File

@ -29,7 +29,7 @@ sensor:
{% configuration %} {% configuration %}
name: name:
description: The name of your device description: The name to use in the frontend for your Synology device.
required: false required: false
default: Synology DSM default: Synology DSM
type: string type: string
@ -56,11 +56,11 @@ ssl:
default: true default: true
type: boolean type: boolean
volumes: volumes:
description: Array of volumes to monitor. Defaults to all volumes. description: "Array of volumes to monitor. Defaults to all volumes. Replace any spaces in the volume name with underscores, e.g., `volume 1` with `volume_1`."
required: false required: false
type: list type: list
disks: disks:
description: Array of disks to monitor. Defaults to all disks. description: "Array of disks to monitor. Defaults to all disks. Use only disk names like `sda`, `sdb`, etc."
required: false required: false
type: list type: list
monitored_conditions: monitored_conditions:

20
source/_integrations/transmission.markdown
View File

@ -70,18 +70,18 @@ scan_interval:
The Transmission Integration will add the following sensors and switches. The Transmission Integration will add the following sensors and switches.
Sensors: Sensors:
- current_status: The status of your Transmission daemon. - transmission_current_status: The status of your Transmission daemon.
- download_speed: The current download speed [MB/s]. - transmission_download_speed: The current download speed [MB/s].
- upload_speed: The current upload speed [MB/s]. - transmission_upload_speed: The current upload speed [MB/s].
- active_torrents: The current number of active torrents. - transmission_active_torrents: The current number of active torrents.
- paused_torrents: The current number of paused torrents. - transmission_paused_torrents: The current number of paused torrents.
- total_torrents: The total number of torrents present in the client. - transmission_total_torrents: The total number of torrents present in the client.
- started_torrents: The current number of started torrents (downloading). - transmission_started_torrents: The current number of started torrents (downloading).
- completed_torrents: The current number of completed torrents (seeding) - transmission_completed_torrents: The current number of completed torrents (seeding)
Switches: Switches:
- on_off: A switch to start/stop all torrents - transmission_switch: A switch to start/stop all torrents
- turtle_mode: A switch to enable turtle mode. - transmission_turtle_mode: A switch to enable turtle mode.
## Event Automation ## Event Automation

2
source/_integrations/wwlln.markdown
View File

@ -65,7 +65,7 @@ the standard ones:
| latitude | Latitude of the lightning strike. | | latitude | Latitude of the lightning strike. |
| longitude | Longitude of the lightning strike. | | longitude | Longitude of the lightning strike. |
| source | `wwlln` to be used in conjunction with the `geo_location` automation trigger. | | source | `wwlln` to be used in conjunction with the `geo_location` automation trigger. |
| external_id | The external ID used in the feed to identify the earthquake in the feed. | | external_id | The external ID used in the feed to identify the lightning strike in the feed. |
| publication_date | Date and time when this event occurred. | | publication_date | Date and time when this event occurred. |
## Full Configuration ## Full Configuration

8
source/_posts/2019-12-11-release-103.markdown
View File

@ -334,6 +334,14 @@ All services for use in Home Assistant are moved to their integration naming spa
[seven_segments docs]: /integrations/seven_segments/ [seven_segments docs]: /integrations/seven_segments/
[tensorflow docs]: /integrations/tensorflow/ [tensorflow docs]: /integrations/tensorflow/
## Release 0.103.5 - December 28
- Bump ring to 0.2.8 to fix Oauth issues ([@tchellomello] - [#30245]) ([ring docs])
[#30245]: https://github.com/home-assistant/home-assistant/pull/30245
[@tchellomello]: https://github.com/tchellomello
[ring docs]: /components/ring/
## If you need help... ## 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). ...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).

9
source/getting-started/presence-detection.markdown
View File

@ -17,11 +17,10 @@ Screenshot of Home Assistant showing a school, work and home zone and two people
There are different ways of setting up presence detection. Usually the easiest way to detect presence is by checking which devices are connected to the network. You can do that if you have one of our [supported routers][routers]. By leveraging what your router already knows, you can easily detect if people are at home. There are different ways of setting up presence detection. Usually the easiest way to detect presence is by checking which devices are connected to the network. You can do that if you have one of our [supported routers][routers]. By leveraging what your router already knows, you can easily detect if people are at home.
It's also possible to run an app on your phone to provide detailed location information to your Home Assistant instance. If you're on iOS we suggest to use the [Home Assistant iOS app](/ios/). For Android, we suggest [OwnTracks][ha-owntracks]. It's also possible to run an app on your phone to provide detailed location information to your Home Assistant instance. For iOS and Android, we suggest using the [Home Assistant Companion app][companion].
During the setup of Home Assistant Companion on your mobile device, the app will ask for permission to allow the device's location to be provided to Home Assistant. Allowing this will create a `device_tracker` entity for that device which can be used in automations and conditions.
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube.com/embed/UieAQ8sC6GY" frameborder="0" allowfullscreen></iframe>
</div>
### Zones ### Zones
@ -37,7 +36,6 @@ The map view will hide all devices that are home.
[nmap]: /integrations/nmap_tracker [nmap]: /integrations/nmap_tracker
[ha-bluetooth]: /integrations/bluetooth_tracker [ha-bluetooth]: /integrations/bluetooth_tracker
[ha-bluetooth-le]: /integrations/bluetooth_le_tracker [ha-bluetooth-le]: /integrations/bluetooth_le_tracker
[ha-owntracks]: /integrations/owntracks/
[ha-locative]: /integrations/locative [ha-locative]: /integrations/locative
[ha-gpslogger]: /integrations/gpslogger [ha-gpslogger]: /integrations/gpslogger
[ha-presence]: /integrations/#presence-detection [ha-presence]: /integrations/#presence-detection
@ -47,5 +45,6 @@ The map view will hide all devices that are home.
[trigger]: /getting-started/automation-trigger/#zone-trigger [trigger]: /getting-started/automation-trigger/#zone-trigger
[condition]: /getting-started/automation-condition/#zone-condition [condition]: /getting-started/automation-condition/#zone-condition
[ha-map]: /integrations/map/ [ha-map]: /integrations/map/
[companion]: https://companion.home-assistant.io/
### [Next step: Join the Community &raquo;](/getting-started/join-the-community/) ### [Next step: Join the Community &raquo;](/getting-started/join-the-community/)