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-18 14:56:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Robbie Trencheny 2016-10-24 21:38:16 -07:00
commit 1af9062a5e
20 changed files with 184 additions and 67 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_config.yml
View File

@ -123,3 +123,7 @@ social:
twitter:
account: home_assistant
current_major_version: 0
current_minor_version: 31
current_patch_version: 1

10
sass/custom/_paulus.scss
View File

@ -398,6 +398,14 @@ p.note {
margin: 12px 0;
}
.added_in_current_version {
margin-top: 12px;
}
.added_two_versions_ago {
margin-bottom: 12px;
}
.btn {
display: block;
background: 0;
@ -472,4 +480,4 @@ a code {
twitterwidget {
margin-left: auto;
margin-right: auto;
}
}

9
source/_components/climate.netatmo.markdown
View File

@ -2,7 +2,7 @@
layout: page
title: "Netatmo Thermostat"
description: "Instructions how to integrate Netatmo thermostat into Home Assistant."
date: 2016-11-10 08:10
date: 2016-10-11 08:10
sidebar: true
comments: false
sharing: true
@ -12,27 +12,24 @@ ha_category: Climate
ha_release: 0.31
---
### {% linkable_title Basic Configuration %}
The `netatmo` thermostat platform is consuming the information provided by a [Netatmo Smart Thermostat](https://www.netatmo.com/product/energy/thermostat) thermostat. This component allows you to view the current temperature and setpoint.
To enable the Netatmo thermostat, you first have to set up [netatmo](/components/netatmo/), this will use discovery to add your thermostat.
### {% linkable_title Basic Configuration %}
If you want to select a specific thermostat, set discovery to False for [netatmo](/components/netatmo/) and add the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
climate:
platform: netatmo
- platform: netatmo
```
Configuration variables:
- **relay** (*Optional*): Will display the thermostats of this relay only.
- **thermostat** array (*Optional*): Thermostat to use.
- **thermostat_name**: Name of the thermostat to display.
- **thermostat_name**: Name of the thermostat to display.
If **relay** and **thermostat** are not provided, all thermostats will be displayed.

4
source/_components/device_tracker.asuswrt.markdown
View File

@ -15,6 +15,10 @@ ha_release: pre 0.7
The `asuswrt` platform offers presence detection by looking at connected devices to a [ASUSWRT](http://event.asus.com/2013/nw/ASUSWRT/) based router.
<p class='note warning'>
This platform is **NOT** available for [Microsoft Windows installations](http://pexpect.readthedocs.io/en/stable/overview.html#pexpect-on-windows).
</p>
To use an ASUSWRT router in your installation, add the following to your `configuration.yaml` file:
```yaml

17
source/_components/history.markdown
View File

@ -8,7 +8,7 @@ comments: false
sharing: true
footer: true
logo: home-assistant.png
ha_category: "History"
ha_category: History
ha_release: pre 0.7
---
@ -44,7 +44,8 @@ Configuration variables:
Without any `include` or `exclude` configuration the history displays graphs for every entity (well that's not exactly true - for instance `hidden` entities or `scenes` are never shown) on a given date. If you are only interested in some of the entities you several options:
- Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like `weblink`) or rarely change (`updater` or `automation`).
Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like `weblink`) or rarely change (`updater` or `automation`).
```yaml
# Example configuration.yaml entry with exclude
history:
@ -57,7 +58,9 @@ history:
- sensor.last_boot
- sensor.date
```
- Define domains and entities to display by using the `include` configuration (aka. whitelist). If you have a lot of entities in your system and your `exclude` lists possibly get very large, it might be better just to define the entities or domains to display.
Define domains and entities to display by using the `include` configuration (aka. whitelist). If you have a lot of entities in your system and your `exclude` lists possibly get very large, it might be better just to define the entities or domains to display.
```yaml
# Example configuration.yaml entry with include
history:
@ -67,7 +70,9 @@ history:
- switch
- media_player
```
- Use the `include` list to define the domains/entities to display, and exclude some of them with in the `exclude` list. This makes sense if you for instance include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in.
Use the `include` list to define the domains/entities to display, and exclude some of them with in the `exclude` list. This makes sense if you for instance include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in.
```yaml
# Example configuration.yaml entry with include and exclude
history:
@ -84,7 +89,7 @@ history:
#### {% linkable_title Implementation details %}
The history is stored in a SQLite database `home-assistant.db` within your config directory.
The history is stored in a SQLite database `home-assistant_v2.db` within your configuration directory.
- events table is all events except `time_changed` that happened while recorder component was running.
- states table contains all the `new_state` values of `state_changed` events.
@ -96,7 +101,7 @@ The history is stored in a SQLite database `home-assistant.db` within your confi
- `last_updated`: timestamp anything has changed (state, attributes)
- `created`: timestamp this entry was inserted into the database
When the history component queries the states table it only selects states where the state has changed: `WHERE last_changed=last_updated`
When the `history` component queries the states table it only selects states where the state has changed: `WHERE last_changed=last_updated`
#### {% linkable_title On dates %}

2
source/_components/notify.nma.markdown
View File

@ -15,7 +15,7 @@ ha_release: pre 0.7
The `nma` platform uses [Notify My Android (NMA)](http://www.notifymyandroid.com/) to delivery notifications from Home Assistant to your Android device.
Go to the [NMA website](https://www.notifymyandroid.com) and create a new API key. If you are using the trial offer then keep in mind that your limit is five (5) message per day.
Go to the [NMA website](https://www.notifymyandroid.com) and create a new API key. If you are using the trial offer then keep in mind that your limit is five messages per day.
To add NMA to your installation, add the following to your `configuration.yaml` file:

1
source/_components/sensor.tellstick.markdown
View File

@ -45,3 +45,4 @@ sensor:
only_named: True
temperature_scale: "°C"
datatype_mask: 1
```

2
source/_cookbook/automation_sun.markdown
View File

@ -89,7 +89,7 @@ Solar elevation automations can cope with offsets from sunset / sunrise as the s
trigger:
platform: numeric_state
entity_id: sun.sun
value_template: '{% raw %}{{ state.attributes.elevation }}{% end raw %}'
value_template: '{% raw %}{{ state.attributes.elevation }}{% endraw %}'
below: 1.5
action:
service: scene.turn_on

6
source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
View File

@ -83,17 +83,17 @@ Since 0.28 [automation rules](/blog/2016/09/10/notify-group-reload-api-pihole/#r
### {% linkable_title Hotfix 0.29.4 - September 30 %}
- Alexa config fix ([@baloob], reported by [@lwis])
- Alexa config fix ([@balloob], reported by [@lwis])
- Envisalink discovery fix ([@cinntax])
- Acer Projector config fix ([@pvizeli])
### {% linkable_title Hotfix 0.29.5 - September 30 %}
- Fix Climate Nest platform (@tchellomello, @jawilson)
- Fix Climate Nest platform ([@tchellomello], [@jawilson])
### {% linkable_title Hotfix 0.29.6 - October 1 %}
- Fix segmentation fault ([@bbangert], fixes #3453) 🎉
- Fix segmentation fault ([@bbangert]) 🎉
- Fix nested templates in `data_template` would incorrectly get cached ([@balloob])
### {% linkable_title Hotfix 0.29.7 - October 5 %}

4
source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
View File

@ -40,9 +40,9 @@ As the results are processed on-the-fly you still need to use the data from your
### {% linkable_title REST! We don't... %}
There was a lot of work done on our implementation which are working with RESTful APIs. [@w1ll1am23] extended the [aREST] platforms to display if an aREST unit is available or not. The aREST is now covered by the configuration check as well. Please check the Breaking changes section for more details.
There was a lot of work done on our implementation which are working with RESTful APIs. [@w1ll1am23] extended the [aREST] platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.
The [REST sensor][rest-sensor] supports now HTTP authentication (basic and digest) and custom header. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.
The [REST sensor][rest-sensor] supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.
```yaml
sensor

81
source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
View File

@ -4,6 +4,7 @@ title: "0.31: Reading you the news, some serious business, spooky hackery and a
description: "Alexa Flash Briefing API support, Markdown in persistent notifications, a new updater component, Hacktoberfest and breaking Z-Wave changes."
date: 2016-10-22 13:00:00 -0700
date_formatted: "October 22, 2016"
release_date: 2016-10-23 21:57:00 -0700
author: Robbie Trencheny
author_twitter: robbie
comments: true
@ -62,35 +63,43 @@ Finally, you can also reset your unique identifier by deleting the `.uuid` file
Here is what my production Home Assistant instance looks like from the server side:
| Name | Description | Example | Data Source |
|-----------------------|--------------------------------------------|------------------------------------|----------------|
| `arch` | CPU Architecture | `x86_64` | Local Instance |
| `distribution` | Linux Distribution name (only Linux) | `Ubuntu` | Local Instance |
| `docker` | True if running inside Docker | `false` | Local Instance |
| `first_seen_datetime` | First time instance ID was submitted | `2016-10-22T19:56:03.542Z` | Update Server |
| `geo_city` | GeoIP determined city | `Oakland` | Update Server |
| `geo_country_code` | GeoIP determined country code | `US` | Update Server |
| `geo_country_name` | GeoIP determined country name | `United States` | Update Server |
| `geo_latitude` | GeoIP determined latitude | `37.8047` | Update Server |
| `geo_longitude` | GeoIP determined longitude | `-122.2124` | Update Server |
| `geo_metro_code` | GeoIP determined metro code | `807` | Update Server |
| `geo_region_code` | GeoIP determined region code | `CA` | Update Server |
| `geo_region_name` | GeoIP determined region name | `California` | Update Server |
| `geo_time_zone` | GeoIP determined time zone | `America/Los_Angeles` | Update Server |
| `geo_zip_code` | GeoIP determined zip code | `94602` | Update Server |
| `last_seen_datetime` | Most recent time instance ID was submitted | `2016-10-22T19:56:03.542Z` | Update Server |
| `os_name` | Operating system name | `Darwin` | Local Instance |
| `os_version` | Operating system version | `10.12` | Local Instance |
| `python_version` | Python version | `3.5.2` | Local Instance |
| `timezone` | Timezone | `America/Los_Angeles` | Local Instance |
| `user_agent` | User agent used to submit analytics | `python-requests/2.11.1` | Local Instance |
| `uuid` | Unique identifier | `10321ee6094d4a2ebb5ed55c675d5f5e` | Local Instance |
| `version` | Home Assistant version | `0.31.0` | Local Instance |
| `virtualenv` | True if running inside virtualenv | `true` | Local Instance |
| Name | Description | Example |
|-----------------------|--------------------------------------------|------------------------------------|
| `arch` | CPU Architecture | `x86_64` |
| `distribution` | Linux Distribution name (only Linux) | `Ubuntu` |
| `docker` | True if running inside Docker | `false` |
| `os_name` | Operating system name | `Darwin` |
| `os_version` | Operating system version | `10.12` |
| `python_version` | Python version | `3.5.2` |
| `timezone` | Timezone | `America/Los_Angeles` |
| `user_agent` | User agent used to submit analytics | `python-requests/2.11.1` |
| `uuid` | Unique identifier | `10321ee6094d4a2ebb5ed55c675d5f5e` |
| `version` | Home Assistant version | `0.31.0` |
| `virtualenv` | True if running inside virtualenv | `true` |
In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine a general geographic area that your address is located in. To be extremely, extremely clear about this bit: __The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your `configuration.yaml`.__ Our tests show that at best, we get 4 digits of accuracy on your IP address location which is a 5 mile radius of your actual IP location, assuming that it is even correct in the first place (geo IP look ups are very hit or miss). Here's what the accuracy looks like for my data above: ![Robbie's GeoIP accuracy level](/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png)
In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: __The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your `configuration.yaml`.__
The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance.
<p class='img'>
<img src='/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png' />
Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
</p>
The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
| Name | Description | Example |
|-----------------------|--------------------------------------------|------------------------------------|
| `first_seen_datetime` | First time instance ID was submitted | `2016-10-22T19:56:03.542Z` |
| `geo_city` | GeoIP determined city | `Oakland` |
| `geo_country_code` | GeoIP determined country code | `US` |
| `geo_country_name` | GeoIP determined country name | `United States` |
| `geo_latitude` | GeoIP determined latitude (of the city) | `37.8047` |
| `geo_longitude` | GeoIP determined longitude (of the city) | `-122.2124` |
| `geo_metro_code` | GeoIP determined metro code | `807` |
| `geo_region_code` | GeoIP determined region code | `CA` |
| `geo_region_name` | GeoIP determined region name | `California` |
| `geo_time_zone` | GeoIP determined time zone | `America/Los_Angeles` |
| `geo_zip_code` | GeoIP determined zip code | `94602` |
| `last_seen_datetime` | Most recent time instance ID was submitted | `2016-10-22T19:56:03.542Z` |
This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me ([@robbiet480]). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just [@balloob] and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
@ -98,6 +107,8 @@ We currently have no plans to publicly expose any of this information. If we did
We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
_This section was updated on October 24 to be more clear about geo-lookups being on the city level. [See original version.][blog-orig]_
Now, back to the fun stuff...
## {% linkable_title Good evening. I'm Ron Burgundy and here's what happening in your world tonight. %}
@ -110,7 +121,10 @@ Home Assistant got a crazy idea recently that it couldn't do enough already and
Now I know how to best get to [my real job][runway] (no, Home Assistant is _not_ my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does _not_ require HTTPS (_but you should still be using HTTPS if possible_). For more information, check out the new [docs][flash-briefing-docs].
![You stay classy, San Diego. (It's funny, because balloob lives in San Diego))](/images/blog/2016-10-flash-briefing-updater-hacktoberfest/stay-classy.jpg)
<p class='img'>
<img src='/images/blog/2016-10-flash-briefing-updater-hacktoberfest/stay-classy.jpg'>
You stay classy, San Diego. (It's funny, because balloob lives in San Diego))
</p>
## {% linkable_title Major breaking Z-Wave changes ahead %}
@ -179,7 +193,15 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
- iOS support ([@robbiet480])
- Minor features and bug fixes by [@mtl010957], [@molobrakos], [@flyte], [@fabaff], [@phardy], [@sander76], [@T3m3z], [@c-w], [@balloob], [@robbiet480], [@StaticCube], [@vittoriom], [@hartmms], [@kirichkov], [@mezz64], [@ishults], [@Danielhiversen] and [@tchellomello].
### {% linkable_title Release 0.31.1 - October 24 %}
- Identify special character encoding error in YAML files ([@kellerza], [@lwis])
- iOS app component bug fixes ([@robbiet480])
- Fix a spelling problem on user-facing error ([@robbiet480])
- YAML includes will ignore dirs/files prefixed with . ([@lwis])
## {% linkable_title Breaking changes %}
- The [HTTP] component now takes a different format for authenticating IPs
- Config format has changed for [Proximity]
- The Z-Wave entity ID change mentioned above
@ -271,7 +293,7 @@ Thanks for reading all of the above, especially since this week was a pretty lon
[netatmo-discovery]: https://home-assistant.io/components/netatmo/
[nmap]: https://home-assistant.io/components/device_tracker.nmap_tracker/
[pers-notify]: https://home-assistant.io/components/persistent_notification/
[runway]: https://runway.is
[runway]: http://runway.is
[scrape]: https://home-assistant.io/components/sensor.scrape/
[updater]: https://home-assistant.io/components/updater/
[z-wave-issue]: https://github.com/home-assistant/home-assistant/pull/3759
@ -279,3 +301,4 @@ Thanks for reading all of the above, especially since this week was a pretty lon
[zero-two-seven-release]: /blog/2016/08/28/notifications-hue-fake-unification/
[twitter]: https://twitter.com/home_assistant
[robbie-twitter]: https://twitter.com/robbie
[blog-orig]: https://github.com/home-assistant/home-assistant.github.io/blob/c937242d154e509d2d84d10c51f654e20556fa21/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown

57
source/_posts/2016-10-24-explaining-the-updater.markdown Normal file
View File

@ -0,0 +1,57 @@
---
layout: post
title: "Explaining the Updater"
description: "An update to the recent updater component changes"
date: 2016-10-24 21:30:00 -0700
date_formatted: "October 24, 2016"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Organisation
---
On Saturday, we released [Home Assistant 0.31][0.31] which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
## {% linkable_title Why we changed the updater %}
This change was driven by two important factors.
### {% linkable_title Improving the security of the users. %}
As a user, you will be able to be notified if you are running a Home Assistant version that includes components that have known security flaws.
Although we hope to not have to use this feature often, it is important for us to be able to reach out to impacted users. We had the need for such a feature once in the past. Due to a bug the forecast.io sensor was making a huge amount of API requests causing some of our users to get charged because they went over the free quota.
Please note that this functionality is not done yet but will be available in a future release.
### {% linkable_title Focusing our resources where it matters %}
As developers of Home Assistant, we will be able to see in what kind of environments Home Assistant is running. Here’s a few data points we didn’t have until now:
* Total number of instances
* Which operating systems versions and flavors are in use
* Python version
* What option is more popular: Docker, Virtualenv or bare metal installs?
* How popular is our new [Raspberry Pi image][rpi-image]?
## {% linkable_title Why we look up your IP address with GeoIP %}
We store the city so that we can see where our users are from. This information will be used to give us a better insight in where our users are from. This will help us gather data to see if we should for example prioritize internationalization. In addition, we previously had a nasty bug with the `sun` component in which users above a certain latitude were having crashes multiple times a day. Had the updater component been in place we could have targeted a special priority update notification only to them.
As stated in the release blog post, the location information is _not_ provided by your local Home Assistant installation but is instead gathered by comparing your IP address against the [GeoLite2 data created by MaxMind][geolite]. From their documentation:
> IP geolocation is inherently imprecise. Locations are often near the center of the population. Any location provided by a GeoIP database should not be used to identify a particular address or household.
## {% linkable_title Why is it enabled by default %}
We decided to have it enabled by default because we consider the information that is gathered not harmful. We understand that not everyone will agree with us and so we have provided [multiple ways to opt out][opt-out].
It is in our short-term planning to add an option to control this to our frontend.
## {% linkable_title Source Code %}
The source code of our updater AWS Lambda function is now available [here][source].
[0.31]: /blog/2016/10/22/flash-briefing-updater-hacktoberfest/#comment-2965607849
[geolite]: https://dev.maxmind.com/geoip/geoip2/geolite2/
[opt-out]: /components/updater/
[rpi-image]: /blog/2016/10/01/we-have-raspberry-image-now/
[source]: https://github.com/home-assistant/Analytics-Receiver

16
source/components/index.html
View File

@ -18,17 +18,27 @@ regenerate: true
{% assign tot = count | minus: nocat %}
{% assign components = site.components | sort: 'title' %}
{% assign categories = components | sort: 'ha_category' | map: 'ha_category' | uniq %}
{% capture current_version %}{{ site.current_major_version }}.{{ site.current_minor_version }}{% endcapture %}
{% assign added_one_ago_minor_version = site.current_minor_version|minus: 1 %}
{% capture added_one_ago_version %}{{ site.current_major_version }}.{{ added_one_ago_minor_version }}{% endcapture %}
{% assign added_two_ago_minor_version = site.current_minor_version|minus: 2 %}
{% capture added_two_ago_version %}{{ site.current_major_version }}.{{ added_two_ago_minor_version }}{% endcapture %}
{% assign current_version_components_count = site.components | where: 'ha_release', current_version | size %}
{% assign one_ago_version_components_count = site.components | where: 'ha_release', added_one_ago_version | size %}
{% assign two_ago_version_components_count = site.components | where: 'ha_release', added_two_ago_version | size %}
<p class='note'>
Support for these components is provided by the Home Assistant community.
</p>
<div class="grid">
<div class="grid__item one-sixth lap-one-whole palm-one-whole">
<div class="filter-button-group">
<a href='#all' class="btn">All ({{tot}})</a>
<a href='#featured' class="btn featured">Featured</a>
<a href='#added_in_current_version' class="btn added_in_current_version">Added in {{ current_version }} ({{ current_version_components_count }})</a>
<a href='#added_one_version_ago' class="btn added_one_version_ago">Added in {{ added_one_ago_version }} ({{ one_ago_version_components_count }})</a>
<a href='#added_two_versions_ago' class="btn added_two_versions_ago">Added in {{ added_two_ago_version }} ({{ two_ago_version_components_count }})</a>
{% for category in categories %}
{% if category and category != 'Other' %}
@ -45,8 +55,10 @@ Support for these components is provided by the Home Assistant community.
<div class="grid__item five-sixths lap-one-whole palm-one-whole" id="componentContainer">
{% for component in components %}
{% if component.ha_category %}
{% assign sliced_version = component.ha_release | split: '.' %}
{% assign minor_version = sliced_version[1]|plus: 0 %}
<a href='{{ component.url }}'
class='{{ component.ha_category | slugify }}{% if component.featured %} featured{% endif %}'
class='{{ component.ha_category | slugify }}{% if minor_version == site.current_minor_version %} added_in_current_version{% elsif minor_version == added_one_ago_minor_version %} added_one_version_ago{% elsif minor_version == added_two_ago_minor_version %} added_two_versions_ago{% endif %}{% if component.featured %} featured{% endif %}'
{% unless component.featured %}style='display: none'{% endunless %}>
<div class='img-container'>
{% if component.logo %}

2
source/getting-started/automation-condition.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true
---
Conditions are an optional part of an automation rule and be used to prevent an action from happening when triggered. Conditions look very similar to triggers but are very different. A trigger will look at events happening in the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is currently on or off.
Conditions are an optional part of an automation rule and can be used to prevent an action from happening when triggered. Conditions look very similar to triggers but are very different. A trigger will look at events happening in the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is currently on or off.
The available conditions for an automation are the same as for the script syntax. So see that page for a [full list of available conditions][script-condition].

14
source/getting-started/installation-synology.markdown
View File

@ -40,13 +40,13 @@ $ cd /volume1/@appstore/py3k/usr/local/bin
Install PIP (Python's package management system)
```bash
$ python -m ensurepip
$ ./python3 -m ensurepip
```
Use PIP to install Homeassistant package
```bash
$ pip3 install homeassistant
$ ./python3 pip install homeassistant
```
Create homeassistant config directory & switch to it
@ -77,7 +77,7 @@ REDIRECT="> $INSTALL_DIR/home-assistant.log 2>&1"
start_daemon ()
{
su ${USER} -s /bin/sh -c "$PYTHON $HASS $FLAGS $REDIRECT;"
sudo -u ${USER} /bin/sh -c "$PYTHON $HASS $FLAGS $REDIRECT;"
}
stop_daemon ()
@ -204,25 +204,25 @@ Here are some useful commands:
- Start Home Assistant:
```bash
$ sh hass-daemon start
$ sudo /volume1/homeassistant/hass-daemon start
```
- Stop Home Assistant:
```bash
$ sh hass-daemon stop
$ sudo /volume1/homeassistant/hass-daemon stop
```
- Restart Home Assistant:
```bash
$ sh hass-daemon restart
$ sudo /volume1/homeassistant/hass-daemon restart
```
- Upgrade Home Assistant::
```bash
$ python3 -m pip install --upgrade homeassistant
$ /volume1/@appstore/py3k/usr/local/bin/python3 -m pip install --upgrade homeassistant
```
### {% linkable_title Troubleshooting %}

7
source/getting-started/z-wave-device-specific.markdown
View File

@ -25,9 +25,10 @@ You should check OZW.log to see if your new setting has been set
Example entry in dev-service, setting binary reports for an Aeotec Multisensor 6:
```yaml
# Example entry in dev-service
{"entity_id": "sensor.aetoec_multisensor_6_luminance_5",
"parameter": "5",
"value": "2"
{
"node_id": 42,
"parameter": 5,
"value": 2
}
```

7
source/getting-started/z-wave.markdown
View File

@ -44,7 +44,10 @@ $ sudo PYTHON_EXEC=$(which python3) make install
<p class='note'>
Instead of `make install`, you can alternatively build your own python-openzwave package which can be easily uninstalled:
```$ sudo PYTHON_EXEC=$(which python3) checkinstall --pkgname python-openzwave --pkgversion 1.0 --provides python-openzwave```
```bash
$ sudo apt-get install -y checkinstall
$ sudo PYTHON_EXEC=$(which python3) checkinstall --pkgname python-openzwave --pkgversion 1.0 --provides python-openzwave
```
</p>
@ -218,7 +221,7 @@ The `zwave` component exposes multiple services to help maintain the network.
| ------- | ----------- |
| add_node | Put the Z-Wave controller in inclusion mode. Allows one to add a new device to the Z-Wave network.|
| add_node_secure | Put the Z-Wave controller in secure inclusion mode. Allows one to add a new device with secure communications to the Z-Wave network. |
| association | Add or remove an association in th Z-Wave network
| change_association | Add or remove an association in th Z-Wave network
| cancel_command | Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decides you are not going to do it, then this must be used to stop the inclusion/exclusion command. |
| heal_network | Tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
| remove_node | Put the Z-Wave controller in exclusion mode. Allows one to remove a device from the Z-Wave network.|

BIN
source/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 649 KiB

After

Width:  |  Height:  |  Size: 230 KiB

0
source/images/screenshots/interlogix.png → source/images/supported_brands/interlogix.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 542 KiB

After

Width:  |  Height:  |  Size: 542 KiB

8
source/index.html
View File

@ -11,15 +11,17 @@ description: Open-source home automation platform running on Python 3. Track and
hide_github_edit: true
---
{% assign recent_release_post = site.categories['Release-Notes'].first %}
<div class="frontpage">
<div class="grid">
<div class="grid__item one-third lap-one-third palm-one-whole">
<div class='current-version material-card text'>
<h1>Current Version: 0.31</h1>
Released: <span class='release-date'>October 22, 2016</span>
<h1>Current Version: {{ site.current_major_version }}.{{ site.current_minor_version }}.{{ site.current_patch_version }}</h1>
Released: <span class='release-date' title='{{ recent_release_post.release_date }}'>{{ recent_release_post.release_date | date: '%B %d, %Y' }}</span>
<div class='links'>
<a href='/blog/2016/10/22/flash-briefing-updater-hacktoberfest/'>Release notes</a>
<a href='{{ root_url }}{{ recent_release_post.url }}'>Release notes</a>
</div>
</div>
<div class='join-community material-card text'>