+ Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
++This platform is **NOT** available for [Microsoft Windows installations](http://pexpect.readthedocs.io/en/stable/overview.html#pexpect-on-windows). +
+ To use an ASUSWRT router in your installation, add the following to your `configuration.yaml` file: ```yaml diff --git a/source/_components/history.markdown b/source/_components/history.markdown index 09f021e4174..c831072e61f 100644 --- a/source/_components/history.markdown +++ b/source/_components/history.markdown @@ -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 %} diff --git a/source/_components/notify.nma.markdown b/source/_components/notify.nma.markdown index c16a7ae04e4..bbe4e871101 100644 --- a/source/_components/notify.nma.markdown +++ b/source/_components/notify.nma.markdown @@ -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: diff --git a/source/_components/sensor.tellstick.markdown b/source/_components/sensor.tellstick.markdown index 431217096fe..0ef1b1ac04e 100644 --- a/source/_components/sensor.tellstick.markdown +++ b/source/_components/sensor.tellstick.markdown @@ -45,3 +45,4 @@ sensor: only_named: True temperature_scale: "°C" datatype_mask: 1 +``` diff --git a/source/_cookbook/automation_sun.markdown b/source/_cookbook/automation_sun.markdown index fff78fb29ab..550904ebb99 100644 --- a/source/_cookbook/automation_sun.markdown +++ b/source/_cookbook/automation_sun.markdown @@ -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 diff --git a/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown b/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown index accc37f17d1..88c7eb45bed 100644 --- a/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown +++ b/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown @@ -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 %} diff --git a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown index 89627e40bfd..c3f29f84c70 100644 --- a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown +++ b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown @@ -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 diff --git a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown index 19b4945fbdc..8d2d249edf5 100644 --- a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown +++ b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown @@ -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:  +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. +
+
+ Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
+
+ 
+ You stay classy, San Diego. (It's funny, because balloob lives in San Diego))
+
Support for these components is provided by the Home Assistant community.
-