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.
+
+
+
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.
@@ -233,6 +226,8 @@
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.
+
Now, back to the fun stuff…
Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
@@ -247,7 +242,10 @@
Now I know how to best get to my real job (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.
-
+
+
+ You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
+
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.
+
+
+
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.
@@ -323,6 +316,8 @@
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.
+
Now, back to the fun stuff…
Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
@@ -337,7 +332,10 @@
Now I know how to best get to my real job (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.
-
+
+
+ You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
+
Major breaking Z-Wave changes ahead
diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml
index 7db6e3d9ec..356328bf1e 100644
--- a/blog/categories/community/atom.xml
+++ b/blog/categories/community/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Community | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml
index f9addf8a48..57ae491d81 100644
--- a/blog/categories/device-tracking/atom.xml
+++ b/blog/categories/device-tracking/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Device-Tracking | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml
index 1b0c5f9139..b943dc050e 100644
--- a/blog/categories/esp8266/atom.xml
+++ b/blog/categories/esp8266/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: ESP8266 | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml
index fd69af0713..2390103a65 100644
--- a/blog/categories/how-to/atom.xml
+++ b/blog/categories/how-to/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: How-To | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml
index 2b0997cdaf..5421ee498f 100644
--- a/blog/categories/ibeacons/atom.xml
+++ b/blog/categories/ibeacons/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: iBeacons | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml
index a8cb1888b0..4a6126f268 100644
--- a/blog/categories/internet-of-things/atom.xml
+++ b/blog/categories/internet-of-things/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Internet-of-Things | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml
index a46e0c6206..b3d282a3c9 100644
--- a/blog/categories/iot-data/atom.xml
+++ b/blog/categories/iot-data/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: IoT-Data | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml
index e0653a83f3..242a093e97 100644
--- a/blog/categories/micropython/atom.xml
+++ b/blog/categories/micropython/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Micropython | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml
index 1edcf9c31e..ad18be119e 100644
--- a/blog/categories/mqtt/atom.xml
+++ b/blog/categories/mqtt/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: MQTT | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml
index de3a0dc17d..580e471702 100644
--- a/blog/categories/organisation/atom.xml
+++ b/blog/categories/organisation/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Organisation | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml
index 119dd94b76..0c2dff7656 100644
--- a/blog/categories/owntracks/atom.xml
+++ b/blog/categories/owntracks/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: OwnTracks | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml
index c6be0e3a96..6bf860107c 100644
--- a/blog/categories/presence-detection/atom.xml
+++ b/blog/categories/presence-detection/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Presence-Detection | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml
index 3b3ca319d2..e5eecb6b61 100644
--- a/blog/categories/public-service-announcement/atom.xml
+++ b/blog/categories/public-service-announcement/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Public-Service-Announcement | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 48b97ad0dc..251aeb618b 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Release-Notes | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
@@ -70,35 +70,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.
+
+
+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.
@@ -106,6 +114,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...
## Good evening. I'm Ron Burgundy and here's what happening in your world tonight.
@@ -118,7 +128,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))
+
## Major breaking Z-Wave changes ahead
@@ -287,6 +300,7 @@ 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
]]>
diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml
index d354f477ef..73416efea5 100644
--- a/blog/categories/survey/atom.xml
+++ b/blog/categories/survey/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Survey | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml
index 49a228c9af..42facc8d3b 100644
--- a/blog/categories/talks/atom.xml
+++ b/blog/categories/talks/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Talks | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml
index ee071c5821..896f4bdca9 100644
--- a/blog/categories/technology/atom.xml
+++ b/blog/categories/technology/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Technology | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml
index 405669acee..9242cbbb41 100644
--- a/blog/categories/user-stories/atom.xml
+++ b/blog/categories/user-stories/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: User-Stories | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml
index ce238f7a5b..60ff22cbe2 100644
--- a/blog/categories/video/atom.xml
+++ b/blog/categories/video/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Video | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml
index e7c5762048..d5e2091a85 100644
--- a/blog/categories/website/atom.xml
+++ b/blog/categories/website/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Website | Home Assistant]]>
- 2016-10-23T10:51:10+00:00
+ 2016-10-24T00:20:50+00:00https://home-assistant.io/
diff --git a/blog/index.html b/blog/index.html
index 2b9fe5d495..9ef3b3aaea 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -172,7 +172,6 @@
Name
Description
Example
-
Data Source
@@ -180,146 +179,140 @@
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
-
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.
+
+
+
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.
@@ -327,6 +320,8 @@
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.
+
Now, back to the fun stuff…
Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
@@ -341,7 +336,10 @@
Now I know how to best get to my real job (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.
-
+
+
+ You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
+
