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

Merge remote-tracking branch 'origin/current' into next

Browse source
This commit is contained in:
Paulus Schoutsen 2018-04-20 10:59:32 -04:00
commit acd36632f7
33 changed files with 242 additions and 83 deletions
Download patch file Download diff file Expand all files Collapse all files

4
source/_docs/configuration/entity-registry.markdown
View file

@ -52,3 +52,7 @@ value to each entry.
cause integrations to fail and might be removed in the future.
_Added in Home Assistant 0.64._
{% linkable_title Supported Components %}
At the moment, only the following components are supported: Z-Wave, Hue, Nest, LIFX, Sonos, Apple TV

4
source/_docs/ecosystem/apache.markdown
View file

@ -35,10 +35,10 @@ To be able to access to your Home Assistant instance by using https://home.examp
ServerName home.example.org
ProxyPreserveHost On
ProxyRequests off
ProxyPass / http://localhost:8123/
ProxyPassReverse / http://localhost:8123/
ProxyPass /api/websocket ws://localhost:8123/api/websocket
ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket
ProxyPass / http://localhost:8123/
ProxyPassReverse / http://localhost:8123/
RewriteEngine on
RewriteCond %{HTTP:Upgrade} =websocket [NC]

4
source/_docs/installation/raspberry-pi.markdown
View file

@ -49,10 +49,10 @@ $ sudo apt-get install python3 python3-venv python3-pip
```
Add an account for Home Assistant called `homeassistant`.
Since this account is only for running Home Assistant the extra arguments of `-rm` is added to create a system account and create a home directory.
Since this account is only for running Home Assistant the extra arguments of `-rm` is added to create a system account and create a home directory. The arguments `-G dialout` adds the user to the `dialout` group. This is required for using Z-Wave and Zigbee controllers.
```bash
$ sudo useradd -rm homeassistant
$ sudo useradd -rm homeassistant -G dialout
```
Next we will create a directory for the installation of Home Assistant and change the owner to the `homeassistant` account.

8
source/_docs/installation/updating.markdown
View file

@ -16,6 +16,10 @@ The upgrade process differs depending on the installation you have, so please re
Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check the log file in the [configuration](/docs/configuration/) directory, e.g., `.homeassistant/home-assistant.log`, for details about broken components.
<p class='note'>
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Hass.io](/hassio/), [Hassbian](/docs/hassbian/installation/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
</p>
The default way to update Home Assistant to the latest release, when available, is:
```bash
@ -30,10 +34,6 @@ $ sudo docker pull homeassistant/home-assistant:latest
After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e. minutes) depending on your device. This is because all requirements are updated as well.
<p class='note'>
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Hass.io](/hassio/), [Hassbian](/docs/hassbian/installation/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
</p>
[BRUH automation](http://www.bruhautomation.com) has created [a tutorial video](https://www.youtube.com/watch?v=tuG2rs1Cl2Y) explaining how to upgrade Home Assistant.
#### {% linkable_title Run a specific version %}

6
source/_docs/z-wave/query-stage.markdown
View file

@ -9,6 +9,10 @@ sharing: true
footer: true
---
When the Z-Wave mesh is first started, the controller will go through all the following stages for every device on the mesh. This is a slow process, and to complete requires that the devices be awake. While devices that are mains or USB powered are always awake, battery-powered devices spend most of their time asleep. Because of this, you can expect that after startup your battery powered devices will spend time in `Initializing (CacheLoad)` - how long depends on the device.
Your devices will still function normally while marked as `Initializing`.
| Stage | Description |
|------------------------|--------------------------------------------------------------------|
| None | Query process hasn't started for this node |
@ -17,7 +21,7 @@ footer: true
| WakeUp | Start wake up process if a sleeping node |
| ManufacturerSpecific1 | Retrieve manufacturer name and product ids if ProtocolInfo lets us |
| NodeInfo | Retrieve info about supported, controlled command classes |
| NodePlusInfo | Retrieve ZWave+ info and update device classes |
| NodePlusInfo | Retrieve Z-Wave+ info and update device classes |
| SecurityReport | Retrieve a list of Command Classes that require Security |
| ManufacturerSpecific2 | Retrieve manufacturer name and product ids |
| Versions | Retrieve version information |