jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Merge branch 'current' into next

Browse source
This commit is contained in:
Robbie Trencheny 2016-10-05 15:44:06 -07:00
commit afdd04e844
63 changed files with 290 additions and 226 deletions
Download patch file Download diff file Expand all files Collapse all files

6
source/getting-started/automation-trigger.markdown
View file

@ -62,10 +62,12 @@ automation:
platform: state
entity_id: device_tracker.paulus, device_tracker.anne_therese
# Optional
state: 'xy'
# or (don't use that with condition: use_trigger_values)
from: 'not_home'
to: 'home'
# Alias for 'to'
state: 'home'
# If given, will trigger when state has been the to state for X time.
for:
hours: 1

2
source/getting-started/automation.markdown
View file

@ -34,7 +34,7 @@ The second line is the condition part of the automation rule. Conditions are opt
The third part is the action which will be performed when a rule is triggered and all conditions are met.For example, it can turn a light on, set the temperature on your thermostat or activate a scene.
<p class='note'>
The difference between a condition and a trigger can be confusing as they are very similar. Triggers are looking at the actions while conditions look at the result: turning a light on vs a light being on.
The difference between a condition and a trigger can be confusing as they are very similar. Triggers look at the actions, while conditions look at the results: turning a light on vs a light being on.
</p>
### {% linkable_title Exploring the internal state %}

2
source/getting-started/autostart-synology.markdown
View file

@ -11,7 +11,7 @@ footer: true
To get Home Assistant to automatically start when you boot your Synology NAS:
SSH onto your synology & login as admin or root
SSH into your synology & login as admin or root
```bash
$ cd /volume1/homeassistant

6
source/getting-started/basic.markdown
View file

@ -43,7 +43,7 @@ http:
```
<p class='note warning'>
If you are planing to expose your Home Assistant instance to the internet and don't set a password then your installation could be accessed by everybody.
If you are planning to expose your Home Assistant instance to the internet and don't set a password then your installation could be accessed by everybody.
</p>
See the [HTTP component documentation](/components/http/) for more options like HTTPS encryption.
@ -56,11 +56,11 @@ Home Assistant runs as a self-hosted web application and contains support to be
To make Home Assistant accessible while away from home, you will have to make it accessible.
The common approach is to setup port forwarding from your router to port 8123 on the computer that is hosting Home Assistant. Instructions on how to do this can be found by searching `<Router model> port forwarding instructions`.
The most common approach is to set up port forwarding from your router to port 8123 on the computer that is hosting Home Assistant. Instructions on how to do this can be found by searching `<Router model> port forwarding instructions`.
The problem with making a port accessible is that some Internet service providers will only offer dynamic IPs. This can cause you to be unable to access Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/).
Just putting a port up is not secure. You should definitely consider to encrypt your traffic if you are accessing your Home Assistant installation from abroad. For details please check the [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post.
Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post.
If you want the very best security, check out [the instructions how to use Tor to access your home](/cookbook/tor_configuration/).

2
source/getting-started/customizing-devices.markdown
View file

@ -15,7 +15,7 @@ By default, all of your devices will be visible and have a default icon determin
# Example configuration.yaml entry
homeassistant:
name: Home
unit_system: celsius
unit_system: metric
# etc
customize:

2
source/getting-started/index.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
---
Below you can find the standard instructions. See the sidebar for installation instructions for specific platforms. If you're running a Linux based platform, we suggest to follow the [VirtualEnv Linux instructions] to avoid having to use root.
Below you can find the standard instructions. See the sidebar for installation instructions for specific platforms. If you're running a Linux-based platform, we suggest to follow the [VirtualEnv Linux instructions] to avoid having to use root.
[Virtualenv Linux instructions]: /getting-started/installation-virtualenv/

2
source/getting-started/installation-raspberry-pi-image.markdown
View file

@ -21,7 +21,7 @@ The easiest way to install Home Assistant on your Raspberry Pi is by using Hassb
These instructions are also available as a [video](https://www.youtube.com/watch?v=iIz6XqDwHEk).
Home Assistant will now be available by navigating with a browser to `http://ip-address-of-pi:8123`. The default username is `pi` and password is `raspberry` (please change this by running `passwd`)
Home Assistant will now be available by navigating with a browser to `http://ip-address-of-pi:8123`. The default username is `pi` and password is `raspberry` (please change this by running `passwd`). The Home Assistant configuration is located at `/home/homeassistant/.homeassistant/`.
The following extras are included on the image:

8
source/getting-started/installation-raspberry-pi.markdown
View file

@ -13,8 +13,12 @@ footer: true
There's currently three documented ways to install Home Assistant on a Raspberry Pi.
- [Manual installation](/getting-started/installation-raspberry-pi/#Manual-Installation). Following this guide doing each step manually. This is highly recommended as a first installation since you get a good overview of the installation.
- [Hassbian image](/getting-started/installation-raspberry-pi-image). Basic installation with the same settings as following the manual installation guide. Some additional software is preinstalled to make installation quicker and easier.
- [All-in-One Installer](/getting-started/installation-raspberry-pi-all-in-one/). Fabric based installation script that installs and compiles many of the things an advanced Home Assistant install is likely to need.
- [Hassbian image](/getting-started/installation-raspberry-pi-image). Basic installation with the same settings as following the manual installation guide. Some additional software is preinstalled to make installation quicker and easier. Installation uses `homeassistant` user.
- [All-in-One Installer](/getting-started/installation-raspberry-pi-all-in-one/). Fabric based installation script that installs and compiles many of the things an advanced Home Assistant install is likely to need. Installation uses `hass` user.
<p class='note note'>
Since each installation type uses a different user for Home Assistant, be sure to note and use the correct username for the `adduser` commands listed below for camera and GPIO extensions.
</p>
### {% linkable_title Manual Installation %}

2
source/getting-started/installation-synology.markdown
View file

@ -18,7 +18,7 @@ Running these commands will:
Using the Synology webadmin:
- Install python3 using the Synology package centre
- Install python3 using the Synology Package Center
- Create homeassistant user and add to the "users" group
SSH onto your synology & login as admin or root

2
source/getting-started/yaml.markdown
View file

@ -11,7 +11,7 @@ footer: true
Home Assistant uses the [YAML](http://yaml.org/) syntax for configuration. YAML might take a while to get used to but is really powerful in allowing you to express complex configurations.
For each component that you want to use in Home Assistant, you add code in your `configuraton.yaml` file to specify its settings.
For each component that you want to use in Home Assistant, you add code in your `configuration.yaml` file to specify its settings.
The following example entry specifies that you want to use the [notify component](/components/notify) with the [pushbullet platform](/components/notify.pushbullet).

10
source/getting-started/z-wave.markdown
View file

@ -54,6 +54,11 @@ With this installation, your `config_path` needed below will resemble:
/usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.0b8-py3.4-linux-x86_64.egg/config
```
If you followed along with setting up a virtual environment, your path will be:
```bash
/srv/hass/python-openzwave/openzwave/config
```
### {% linkable_title Configuration %}
@ -116,6 +121,11 @@ Uncomment the line:
You can replace these values with your own 16 byte network key. For more information on this process see the [OpenZwave](https://github.com/OpenZWave/open-zwave) wiki article [Adding Security Devices to OZW](https://github.com/OpenZWave/open-zwave/wiki/Adding-Security-Devices-to-OZW)
An easy script to generate a random key:
```bash
cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g'
```
### {% linkable_title Events %}
#### {% linkable_title zwave.network_complete %}