Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
518dbd7b89
92 changed files with 561 additions and 364 deletions
|
|
@ -70,6 +70,11 @@ automation:
|
|||
below: 25
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
Listing above and below together means the numeric_state has to be between the two values.
|
||||
In the example above, a numeric_state that is 17.1-24.9 would fire this trigger.
|
||||
</p>
|
||||
|
||||
### {% linkable_title State trigger %}
|
||||
|
||||
Triggers when the state of tracked entities change. If only entity_id given will match all state changes, even if only state attributes change.
|
||||
|
|
@ -186,7 +191,7 @@ automation:
|
|||
|
||||
### {% linkable_title Multiple triggers %}
|
||||
|
||||
When your want your automation rule to have multiple triggers, just prefix the first line of each trigger with a dash (-) and indent the lines following accordingly. Whenever one of the triggers fires, your rule is executed.
|
||||
When your want your automation rule to have multiple triggers, just prefix the first line of each trigger with a dash (-) and indent the next lines accordingly. Whenever one of the triggers fires, your rule is executed.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
|
|
|
|||
|
|
@ -10,11 +10,11 @@ footer: true
|
|||
redirect_from: /topics/secrets/
|
||||
---
|
||||
|
||||
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secrets` you can remove any private information from you configuration files. This separation can also help you to keep easier track of your passwords and API keys. As they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple yaml files if you [split up your configuration](/topics/splitting_configuration/).
|
||||
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secrets` you can remove any private information from you configuration files. This separation can also help you to keep easier track of your passwords and API keys. As they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple yaml files if you [split up your configuration](/docs/configuration/splitting_configuration/).
|
||||
|
||||
### {% linkable_title Using secrets.yaml %}
|
||||
|
||||
The workflow for moving private information to `secrets.yaml` is very similar to the [splitting of the configuration](/topics/splitting_configuration/). Create a `secrets.yaml` file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`).
|
||||
The workflow for moving private information to `secrets.yaml` is very similar to the [splitting of the configuration](/docs/configuration/splitting_configuration/). Create a `secrets.yaml` file in your Home Assistant [configuration directory](/docs/configuration/).
|
||||
|
||||
The entries for password and API keys in the `configuration.yaml` file usually looks like the example below.
|
||||
|
||||
|
|
@ -39,7 +39,8 @@ http_password: YOUR_PASSWORD
|
|||
### {% linkable_title Debugging secrets %}
|
||||
|
||||
When you start splitting your configuration into multiple files, you might end up with configuration in sub folders. Secrets will be resolved in this order:
|
||||
- A `secrets.yaml` located in the same folder as the yaml file referencing the secret,
|
||||
|
||||
- A `secrets.yaml` located in the same folder as the YAML file referencing the secret,
|
||||
- next, parent folders will be searched for a `secrets.yaml` file with the secret, stopping at the folder with the main `configuration.yaml`,
|
||||
- lastly, `keyring` will be queried for the secret (more info below)
|
||||
|
||||
|
|
@ -55,7 +56,7 @@ This will not print the actual secret's value to the log.
|
|||
*Option 2*: View where secrets are retrieved from and the contents of all `secrets.yaml` files used, you can use the `check_config` script from the command line:
|
||||
|
||||
```bash
|
||||
hass --script check_config --secrets
|
||||
$ hass --script check_config --secrets
|
||||
```
|
||||
This will print all your secrets.
|
||||
|
||||
|
|
|
|||
|
|
@ -247,6 +247,8 @@ action:
|
|||
```
|
||||
|
||||
It is important to note that each file must contain only **one** entry when using `!include_dir_list`.
|
||||
It is also important to note that if you are splitting a file after adding -id: to support the automation UI,
|
||||
the -id: line must be removed from each of the split files.
|
||||
|
||||
#### {% linkable_title Example: `!include_dir_named` %}
|
||||
|
||||
|
|
|
|||
|
|
@ -13,14 +13,7 @@ redirect_from: /ecosystem/appdaemon/updating/
|
|||
To update AppDaemon after I have released new code, just run the following command to update your copy:
|
||||
|
||||
```bash
|
||||
$ git pull origin
|
||||
$ sudo pip3 install --upgrade appdaemon
|
||||
```
|
||||
|
||||
If you are using pip3 for the install do this:
|
||||
|
||||
```bash
|
||||
$ sudo pip3 uninstall appdaemon
|
||||
$ sudo pip3 install .
|
||||
```
|
||||
|
||||
If you are using docker, rerun the steps to create a new docker image.
|
||||
If you are using docker, rerun the steps to grab the latestdocker image.
|
||||
|
|
|
|||
21
source/_docs/ecosystem/caddy.markdown
Normal file
21
source/_docs/ecosystem/caddy.markdown
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Caddy Server reverse proxy"
|
||||
description: "Configure Caddy Server as a reverse proxy to Home Assistant."
|
||||
date: 2017-08-22 22:20
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Configure [Caddy Server](https://caddyserver.com/) for use as a reverse proxy to Home Assistant.
|
||||
|
||||
```
|
||||
hass.example.org {
|
||||
proxy / localhost:8123 {
|
||||
websocket
|
||||
transparent
|
||||
}
|
||||
}
|
||||
```
|
||||
|
|
@ -39,4 +39,4 @@ HADashboard is a modular, skinnable dashboard for [Home Assistant](https://home-
|
|||
|
||||
|
||||
|
||||
For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/latest/DASHBOARD/)
|
||||
For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/latest/DASHBOARD_INSTALL.html)
|
||||
|
|
|
|||
|
|
@ -35,9 +35,9 @@ We would appreciate if you help to keep this page up-to-date and add feedback.
|
|||
|
||||
| Browser | Release | State | Comments |
|
||||
| :-------------------- |:---------------|:-----------|:-------------------------|
|
||||
| [Firefox] | 49.0 | works | |
|
||||
| [Firefox] | 55.0 | works | |
|
||||
| [Midori] | 0.5.11 | works | |
|
||||
| [Chromium] | 53.0.2785.143 | works | |
|
||||
| [Chromium] | 60.0.3112.90 | works | |
|
||||
| [Conkeror] | 1.0.2 | works | |
|
||||
| [Konqueror] | | unknown | |
|
||||
| [Uzbl] | 0.9.0 | works | |
|
||||
|
|
@ -63,6 +63,7 @@ We would appreciate if you help to keep this page up-to-date and add feedback.
|
|||
| [Safari] | | works | Can also be added to desktop. Map is fixed since 0.51. |
|
||||
| [Chrome] | | works | |
|
||||
|
||||
There are reports that devices running with iOS prior to iOS 10, especially old iPads, are having trouble.
|
||||
|
||||
[Firefox]: https://www.mozilla.org/en-US/firefox/
|
||||
[Midori]: http://midori-browser.org/
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ footer: true
|
|||
redirect_from: /getting-started/installation/
|
||||
---
|
||||
|
||||
Home Assistant provides multiple ways to be installed. A requirement is that you have [Python](https://www.python.org/downloads/) installed. For Windows we require at least **Python 3.5** and for other operating systems at least **Python 3.4.2**.
|
||||
Home Assistant provides multiple ways to be installed. A requirement is that you have [Python](https://www.python.org/downloads/) installed. For Windows, we require at least **Python 3.5** and for other operating systems at least **Python 3.4.2**.
|
||||
|
||||
<div class="text-center hass-option-cards" markdown="0">
|
||||
<a class='option-card' href='/docs/hassbian/installation/'>
|
||||
|
|
@ -23,7 +23,7 @@ Home Assistant provides multiple ways to be installed. A requirement is that you
|
|||
<div class='img-container'>
|
||||
<img src='/images/supported_brands/raspberry-pi.png' />
|
||||
</div>
|
||||
<div class='title'>Rasbian</div>
|
||||
<div class='title'>Raspbian</div>
|
||||
</a>
|
||||
<a class='option-card' href='/docs/installation/archlinux/'>
|
||||
<div class='img-container'>
|
||||
|
|
|
|||
|
|
@ -36,6 +36,10 @@ The following extras are included on the image:
|
|||
After flashing the image to your SD Card open the partition `boot` and create a new file `wpa_supplicant.conf`. Edit the file and enter your network credentials. For more information visit [Setting up Wifi for Raspbian][wifi-setup]. During start the file will automatically be copied in the right folder and the network connection will be established. The file could look like this:
|
||||
|
||||
```conf
|
||||
country=SE
|
||||
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
|
||||
update_config=1
|
||||
|
||||
network={
|
||||
ssid="YOUR_SSID"
|
||||
psk="YOUR_PASSWORD"
|
||||
|
|
|
|||
|
|
@ -19,8 +19,8 @@ Virtualenvs are pretty easy to setup. This example will walk through one method
|
|||
```bash
|
||||
$ sudo apt-get update
|
||||
$ sudo apt-get upgrade
|
||||
$ sudo apt-get install python-pip python3-dev
|
||||
$ sudo pip install --upgrade virtualenv
|
||||
$ sudo apt-get install python3-pip python3-dev
|
||||
$ sudo pip3 install --upgrade virtualenv
|
||||
```
|
||||
|
||||
### {% linkable_title Step 1: Create a Home Assistant user & group %}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue