Merge branch 'current' into next
This commit is contained in:
Paulus Schoutsen
commit
4c1c60df29
55 changed files with 421 additions and 159 deletions
|
|
@ -48,7 +48,6 @@ automation 2:
|
|||
message: Oh wow you really missed something great.
|
||||
```
|
||||
|
||||
|
||||
Conditions can also be part of an action. You can combine multiple service calls and conditions in a single action, and they will be processed in the order you put them in. If the result of a condition is false, the action will stop there so any service calls after that condition will not be executed.
|
||||
|
||||
```yaml
|
||||
|
|
@ -70,4 +69,4 @@ automation:
|
|||
value_template: '{% raw %}{{ states.sensor.sensorluz_7_0.state < 10 }}{% endraw %}'
|
||||
- service: scene.turn_on
|
||||
entity_id: scene.DespiertaDespacho
|
||||
```
|
||||
```
|
||||
|
|
@ -35,7 +35,7 @@ WantedBy=multi-user.target
|
|||
EOF'
|
||||
```
|
||||
|
||||
If you've setup Home Assistant in `virtualenv` following our [manual installation guide](https://home-assistant.io/getting-started/installation-raspberry-pi/), the following template should work for you.
|
||||
If you've setup Home Assistant in `virtualenv` following our [python installation guide](https://home-assistant.io/getting-started/installation-virtualenv/) or [manual installation guide for raspberry pi](https://home-assistant.io/getting-started/installation-raspberry-pi/), the following template should work for you.
|
||||
|
||||
```
|
||||
[Unit]
|
||||
|
|
@ -46,9 +46,9 @@ After=network.target
|
|||
Type=simple
|
||||
User=homeassistant
|
||||
#make sure the virtualenv python binary is used
|
||||
Environment=VIRTUAL_ENV="/srv/homeassistant/homeassistant_venv"
|
||||
Environment=VIRTUAL_ENV="/srv/homeassistant"
|
||||
Environment=PATH="$VIRTUAL_ENV/bin:$PATH"
|
||||
ExecStart=/srv/homeassistant/homeassistant_venv/bin/hass -c "/home/homeassistant/.homeassistant"
|
||||
ExecStart=/srv/homeassistant/bin/hass -c "/home/homeassistant/.homeassistant"
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
|
|
|
|||
|
|
@ -11,31 +11,26 @@ footer: true
|
|||
|
||||
By default, all of your devices will be visible and have a default icon determined by their domain. You can customize the look and feel of your front page by altering some of these parameters. This can be done by overriding attributes of specific entities.
|
||||
|
||||
This format works for version 0.37+. For pre-0.37 use [Older format](https://home-assistant.io/getting-started/customizing-devices/#older-format)
|
||||
|
||||
`customize` consists of a list of attribute customization blocks
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
homeassistant:
|
||||
name: Home
|
||||
unit_system: metric
|
||||
# etc
|
||||
|
||||
customize:
|
||||
# Only the 'entity_id' is required. All other options are optional.
|
||||
- entity_id: sensor.living_room_motion
|
||||
# Add an entry for each entity that you want to overwrite.
|
||||
sensor.living_room_motion:
|
||||
hidden: true
|
||||
- entity_id: thermostat.family_roomfamily_room
|
||||
thermostat.family_room:
|
||||
entity_picture: https://example.com/images/nest.jpg
|
||||
friendly_name: Nest
|
||||
- entity_id: switch.wemo_switch_1
|
||||
switch.wemo_switch_1:
|
||||
friendly_name: Toaster
|
||||
entity_picture: /local/toaster.jpg
|
||||
- entity_id: switch.wemo_switch_2
|
||||
switch.wemo_switch_2:
|
||||
friendly_name: Kitchen kettle
|
||||
icon: mdi:kettle
|
||||
- entity_id: switch.rfxtrx_switch
|
||||
switch.rfxtrx_switch:
|
||||
assumed_state: false
|
||||
```
|
||||
|
||||
|
|
@ -57,62 +52,9 @@ Device class is currently supported by the following platforms:
|
|||
* [Binary Sensor](/components/binary_sensor/)
|
||||
* [Cover](/components/cover/)
|
||||
|
||||
### {% linkable_title Advanced example %}
|
||||
|
||||
You can also specify attributes for all devices in a domain, use wildcards, use several entity IDs as a list or comma separated list.
|
||||
|
||||
```yaml
|
||||
homeassistant:
|
||||
customize:
|
||||
- entity_id: sensor
|
||||
icon: mdi:kettle # Give all sensor the kettle icon
|
||||
- entity_id: light.family*
|
||||
hidden: true # Hide all lights that have an ID starting with 'family'
|
||||
- entity_id: switch.wemo_switch_1,switch.wemo_switch_2,switch.wemo_switch_3
|
||||
entity_picture: /local/toaster.jpg # Set picture on multiple devices
|
||||
```
|
||||
|
||||
Either `entity_id` must be present in each customization block.
|
||||
|
||||
### {% linkable_title Older format %}
|
||||
|
||||
In the previous version of customize format the keys were the IDs:
|
||||
```yaml
|
||||
homeassistant:
|
||||
name: Home
|
||||
unit_system: metric
|
||||
# etc
|
||||
|
||||
customize:
|
||||
# Only the 'entity_id' is required. All other options are optional.
|
||||
sensor.living_room_motion:
|
||||
hidden: true
|
||||
thermostat.family_roomfamily_room:
|
||||
entity_picture: https://example.com/images/nest.jpg
|
||||
friendly_name: Nest
|
||||
switch.wemo_switch_1:
|
||||
friendly_name: Toaster
|
||||
entity_picture: /local/toaster.jpg
|
||||
switch.wemo_switch_2:
|
||||
friendly_name: Kitchen kettle
|
||||
icon: mdi:kettle
|
||||
- entity_id: switch.rfxtrx_switch:
|
||||
assumed_state: false
|
||||
```
|
||||
This format doesn't support comma-separated IDs, wildcards or domain matching.
|
||||
|
||||
The formats can't be mixed
|
||||
```yaml
|
||||
# NOT A VALID CONFIGURATION
|
||||
customize:
|
||||
sensor.living_room_motion:
|
||||
hidden: true
|
||||
- entity_id: thermostat.family_roomfamily_room
|
||||
friendly_name: Nest
|
||||
```
|
||||
|
||||
### {% linkable_title Reloading customize %}
|
||||
|
||||
|
||||
Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant/reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> service developer tools, select the service `homeassistant/reload_core_config` and click "Call Service".
|
||||
|
||||
<p class='note warning'>
|
||||
|
|
|
|||
|
|
@ -18,9 +18,9 @@ $ docker run -d --name="home-assistant" -v /path/to/your/config:/config -v /etc/
|
|||
This will launch Home Assistant and serve the web interface from port 8123 on your Docker host.
|
||||
|
||||
<p class='note'>
|
||||
When using boot2docker on OS X you are unable to map the local time to your Docker container. Replace `-v /etc/localtime:/etc/localtime:ro` with `-e "TZ=America/Los_Angeles"` (replacing America/Los_Angeles with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones))
|
||||
When using boot2docker on macOS you are unable to map the local time to your Docker container. Replace `-v /etc/localtime:/etc/localtime:ro` with `-e "TZ=America/Los_Angeles"` (replacing America/Los_Angeles with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones))
|
||||
|
||||
Additionally, if your expectation is that you will be able to browse directly to `http://localhost:8123` on your OS X host, then you will also need to replace the `--net=host` switch with `-p 8123:8123`. This is currently the only way to forward ports on to your actual host(OS X) machine instead of the virtual machine inside xhyve. More detail on this can be found in [the docker forums](https://forums.docker.com/t/should-docker-run-net-host-work/14215/10).
|
||||
Additionally, if your expectation is that you will be able to browse directly to `http://localhost:8123` on your macOS host, then you will also need to replace the `--net=host` switch with `-p 8123:8123`. This is currently the only way to forward ports on to your actual host (macOS) machine instead of the virtual machine inside `xhyve`. More detail on this can be found in [the docker forums](https://forums.docker.com/t/should-docker-run-net-host-work/14215/10).
|
||||
</p>
|
||||
|
||||
If you change the config you have to restart the server.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ footer: true
|
|||
This installation of Home Assistant requires the Raspberry Pi to run [Raspbian Lite](https://www.raspberrypi.org/downloads/raspbian/).
|
||||
The installation will be installed in a [Virtual Environment](/getting-started/installation-virtualenv) with minimal overhead. Instructions assume this is a new installation of Raspbian Lite.
|
||||
|
||||
Connect to the Raspberry Pi over ssh. Default password is `raspberry`.
|
||||
Connect to the Raspberry Pi over ssh. Default password is `raspberry`.
|
||||
You will need to enable ssh access. The raspberry pi website has instructions [here](https://www.raspberrypi.org/documentation/remote-access/ssh/).
|
||||
```bash
|
||||
$ ssh pi@ipadress
|
||||
|
|
@ -51,17 +51,17 @@ Next up is to create and change to a virtual environment for Home Assistant. Thi
|
|||
```bash
|
||||
$ sudo su -s /bin/bash homeassistant
|
||||
$ cd /srv/homeassistant
|
||||
$ python3 -m venv homeassistant_venv
|
||||
$ source /srv/homeassistant/homeassistant_venv/bin/activate
|
||||
$ python3 -m venv .
|
||||
$ source bin/activate
|
||||
```
|
||||
Once you have activated the virtual environment you will notice the prompt change and then you can install Home Assistant.
|
||||
```bash
|
||||
(homeassistant_venv) homeassistant@raspberrypi:/srv/homeassistant $ pip3 install homeassistant
|
||||
(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ pip3 install homeassistant
|
||||
```
|
||||
|
||||
Start Home Assistant for the first time. This will complete the installation, create the `.homeasssistant` configuration directory in the `/home/homeassistant` directory and install any basic dependencies.
|
||||
```bash
|
||||
(homeassistant_venv) $ hass
|
||||
(homeassistant) $ hass
|
||||
```
|
||||
|
||||
You can now reach your installation on your raspberry pi over the web interface on [http://ipaddress:8123](http://ipaddress:8123).
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ This can be anywhere you want. As example we put it in `/srv`. You also need to
|
|||
|
||||
```bash
|
||||
$ sudo mkdir /srv/homeassistant
|
||||
$ sudo chown homeassistant /srv/homeassistant
|
||||
$ sudo chown homeassistant:homeassistant /srv/homeassistant
|
||||
```
|
||||
|
||||
### {% linkable_title Step 3: Become the new user %}
|
||||
|
|
@ -103,7 +103,7 @@ Upgrading Home Assistant is simple, just repeat steps 3, 5 and 6.
|
|||
|
||||
The [autostart instructions](/getting-started/autostart/) will work just fine, just be sure to replace `/usr/bin/hass` with `/srv/homeassistant/bin/hass` and specify the `homeassistant` user where appropriate.
|
||||
|
||||
### {% linkable_title Installing python-openzwave %}
|
||||
### {% linkable_title Installing python-openzwave in a virtualenv %}
|
||||
|
||||
If you want to use Z-Wave devices, you will need to install `python-openzwave` in your virtualenv. This requires a small tweak to the instructions in [the Z-Wave Getting Started documentation](/getting-started/z-wave/)
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,9 @@ sharing: true
|
|||
footer: true
|
||||
---
|
||||
|
||||
The upgrade process differed depending on the installtion you have, review the documentaion specific to your install [HASSbian](/getting-started/installation-raspberry-pi-image/#update-home-assistant-on-hassbian), [Raspberry Pi All-In-One Installer](/getting-started/installation-raspberry-pi-all-in-one/#upgrading), [Vagrant](/getting-started/installation-vagrant/), or [Virtualenv](/getting-started/installation-virtualenv/#upgrading-home-assistant).
|
||||
<p class='note warning'>
|
||||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [HASSbian](/getting-started/hassbian-common-tasks/#update-home-assistant), [Raspberry Pi All-In-One Installer](/getting-started/installation-raspberry-pi-all-in-one/#upgrading), [Vagrant](/getting-started/installation-vagrant/), or [Virtualenv](/getting-started/installation-virtualenv/#upgrading-home-assistant).
|
||||
</p>
|
||||
|
||||
The default way to update Home Assistant to the latest release, when available, is:
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Getting the right indentation can be tricky if you're not using an editor with a
|
|||
You can use [YAMLLint](http://www.yamllint.com/) to check if your YAML-syntax is correct before loading it into Home Assistant which will save you some time.
|
||||
*Please pay attention on not putting in private data, as it is a 3rd-party website not maintained by Home Assistant.*
|
||||
|
||||
Lines that start with **#** are comments and are ignored by the system.
|
||||
Text following a **#** are comments and are ignored by the system.
|
||||
|
||||
The next example shows an [input_select](/components/input_select) component that uses a block collection for the options values.
|
||||
The other properties (like name) are specified using mappings. Note that the second line just has `threat:` with no value on the same line. Here threat is the name of the input_select and the values for it are everything nested below it.
|
||||
|
|
|
|||
|
|
@ -13,6 +13,10 @@ footer: true
|
|||
|
||||
There is currently support for climate, covers, lights, locks, sensors, switches and thermostats. All will be picked up automatically after configuring this platform.
|
||||
|
||||
### {% linkable_title Installation in Virtualenv (python-OpenZWace) %}
|
||||
|
||||
If you installed Home Assistant using a virtual environment then please read the instructions on [Installing python-OpenZWave in a virtualenv](https://home-assistant.io/getting-started/installation-virtualenv/#installing-python-openzwave-in-a-virtualenv).
|
||||
|
||||
### {% linkable_title Installation %}
|
||||
|
||||
To allow Home Assistant to talk to your Z-Wave USB stick you will have to compile the OpenZWave library and install the related [python-OpenZWave package](https://github.com/OpenZWave/python-openzwave). This can be done as follows. _(Note: The Home Assistant docker image and the All In One installer have support for Z-Wave already built-in!)_
|
||||
|
|
@ -58,7 +62,7 @@ With this installation, your `config_path` needed below will resemble:
|
|||
|
||||
If you followed along with setting up a virtual environment, your path will be:
|
||||
```bash
|
||||
/srv/hass/python-openzwave/openzwave/config
|
||||
/srv/homeassistant/python-openzwave/openzwave/config
|
||||
```
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue