Skip to content

Commit f4d8ebb

Browse files
balloobballoob
committed
Update 0.31 release text around updater analytics
1 parent 7130abc commit f4d8ebb

File tree

2 files changed

+44
-30
lines changed

2 files changed

+44
-30
lines changed

‎source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown

Lines changed: 44 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -62,42 +62,52 @@ Finally, you can also reset your unique identifier by deleting the `.uuid` file
6262

6363
Here is what my production Home Assistant instance looks like from the server side:
6464

65-
| Name | Description | Example | Data Source |
66-
|-----------------------|--------------------------------------------|------------------------------------|----------------|
67-
| `arch` | CPU Architecture | `x86_64` | Local Instance |
68-
| `distribution` | Linux Distribution name (only Linux) | `Ubuntu` | Local Instance |
69-
| `docker` | True if running inside Docker | `false` | Local Instance |
70-
| `first_seen_datetime` | First time instance ID was submitted | `2016-10-22T19:56:03.542Z` | Update Server |
71-
| `geo_city` | GeoIP determined city | `Oakland` | Update Server |
72-
| `geo_country_code` | GeoIP determined country code | `US` | Update Server |
73-
| `geo_country_name` | GeoIP determined country name | `United States` | Update Server |
74-
| `geo_latitude` | GeoIP determined latitude | `37.8047` | Update Server |
75-
| `geo_longitude` | GeoIP determined longitude | `-122.2124` | Update Server |
76-
| `geo_metro_code` | GeoIP determined metro code | `807` | Update Server |
77-
| `geo_region_code` | GeoIP determined region code | `CA` | Update Server |
78-
| `geo_region_name` | GeoIP determined region name | `California` | Update Server |
79-
| `geo_time_zone` | GeoIP determined time zone | `America/Los_Angeles` | Update Server |
80-
| `geo_zip_code` | GeoIP determined zip code | `94602` | Update Server |
81-
| `last_seen_datetime` | Most recent time instance ID was submitted | `2016-10-22T19:56:03.542Z` | Update Server |
82-
| `os_name` | Operating system name | `Darwin` | Local Instance |
83-
| `os_version` | Operating system version | `10.12` | Local Instance |
84-
| `python_version` | Python version | `3.5.2` | Local Instance |
85-
| `timezone` | Timezone | `America/Los_Angeles` | Local Instance |
86-
| `user_agent` | User agent used to submit analytics | `python-requests/2.11.1` | Local Instance |
87-
| `uuid` | Unique identifier | `10321ee6094d4a2ebb5ed55c675d5f5e` | Local Instance |
88-
| `version` | Home Assistant version | `0.31.0` | Local Instance |
89-
| `virtualenv` | True if running inside virtualenv | `true` | Local Instance |
90-
91-
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)
92-
93-
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.
65+
| Name | Description | Example |
66+
|-----------------------|--------------------------------------------|------------------------------------|
67+
| `arch` | CPU Architecture | `x86_64` |
68+
| `distribution` | Linux Distribution name (only Linux) | `Ubuntu` |
69+
| `docker` | True if running inside Docker | `false` |
70+
| `os_name` | Operating system name | `Darwin` |
71+
| `os_version` | Operating system version | `10.12` |
72+
| `python_version` | Python version | `3.5.2` |
73+
| `timezone` | Timezone | `America/Los_Angeles` |
74+
| `user_agent` | User agent used to submit analytics | `python-requests/2.11.1` |
75+
| `uuid` | Unique identifier | `10321ee6094d4a2ebb5ed55c675d5f5e` |
76+
| `version` | Home Assistant version | `0.31.0` |
77+
| `virtualenv` | True if running inside virtualenv | `true` |
78+
79+
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`.__
80+
81+
<p class='img'>
82+
<img src='/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png' />
83+
Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
84+
</p>
85+
86+
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:
87+
88+
| Name | Description | Example |
89+
|-----------------------|--------------------------------------------|------------------------------------|
90+
| `first_seen_datetime` | First time instance ID was submitted | `2016-10-22T19:56:03.542Z` |
91+
| `geo_city` | GeoIP determined city | `Oakland` |
92+
| `geo_country_code` | GeoIP determined country code | `US` |
93+
| `geo_country_name` | GeoIP determined country name | `United States` |
94+
| `geo_latitude` | GeoIP determined latitude (of the city) | `37.8047` |
95+
| `geo_longitude` | GeoIP determined longitude (of the city) | `-122.2124` |
96+
| `geo_metro_code` | GeoIP determined metro code | `807` |
97+
| `geo_region_code` | GeoIP determined region code | `CA` |
98+
| `geo_region_name` | GeoIP determined region name | `California` |
99+
| `geo_time_zone` | GeoIP determined time zone | `America/Los_Angeles` |
100+
| `geo_zip_code` | GeoIP determined zip code | `94602` |
101+
| `last_seen_datetime` | Most recent time instance ID was submitted | `2016-10-22T19:56:03.542Z` |
94102

95103
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.
96104

97105
We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
98106

99107
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.
100108

109+
_This section was updated on October 24 to be more clear about geo-lookups being on the city level. [See original version.][blog-orig]_
110+
101111
Now, back to the fun stuff...
102112

103113
## {% linkable_title Good evening. I'm Ron Burgundy and here's what happening in your world tonight. %}
@@ -110,7 +120,10 @@ Home Assistant got a crazy idea recently that it couldn't do enough already and
110120

111121
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].
112122

113-
![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)
123+
<p class='img'>
124+
<img src='/images/blog/2016-10-flash-briefing-updater-hacktoberfest/stay-classy.jpg'>
125+
You stay classy, San Diego. (It's funny, because balloob lives in San Diego))
126+
</p>
114127

115128
## {% linkable_title Major breaking Z-Wave changes ahead %}
116129

@@ -279,3 +292,4 @@ Thanks for reading all of the above, especially since this week was a pretty lon
279292
[zero-two-seven-release]: /blog/2016/08/28/notifications-hue-fake-unification/
280293
[twitter]: https://twitter.com/home_assistant
281294
[robbie-twitter]: https://twitter.com/robbie
295+
[blog-orig]: https://github.com/home-assistant/home-assistant.github.io/blob/c937242d154e509d2d84d10c51f654e20556fa21/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown

‎source/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png

-419 KB
Loading

0 commit comments

Comments
 (0)