diff --git a/atom.xml b/atom.xml
index 950bf1fc1d..b6876a106e 100644
--- a/atom.xml
+++ b/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Home Assistant]]>
- 2016-10-22T19:15:15+00:00
+ 2016-10-22T22:35:39+00:00https://home-assistant.io/
@@ -13,6 +13,332 @@
Octopress
+
+ <![CDATA[0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change]]>
+
+ 2016-10-22T20:00:00+00:00
+ https://home-assistant.io/blog/2016/10/22/flash-briefing-updater-hacktoberfest
+ Hello again friend,
+
+
How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
+
+
Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
+
+
One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
+
+
Stats Update
+
Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+
+
Hacktoberfest
+
+
+
+
October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+
+
⚠️ A greatly improved updater component (Please read this!) ⚠️
+
+
This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+
+
It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
+
+
+
We are unable to do a slow rollout
+
We are unable to show the user extra information (like a link to a changelog or the release date)
+
We are unable to warn users for critical security updates
+
+
+
So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+
+
What you need to know (the important bit!)
+
+
Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+
+
Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
+
+
Opting out
+
+
There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
+
+
updater:
+ reporting:no
+
+
+
+
You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
+
+
Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
+
+
Data stored on the Home Assistant update server
+
+
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
+
+
+
+
+
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:
+
+
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 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.
+
+
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.
+
+
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.
+
+
Now, back to the fun stuff…
+
+
Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
+
+
Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+
+
0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+
+
+
Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
+
+
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.
+
+
+
+
Major breaking Z-Wave changes ahead
+
+
A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+
+
What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
+
+
+
Update customizations
+
Update groups
+
Update my zwave.customize section
+
Update my Alexa skills that used old entity IDs
+
Because I use emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
+
+
Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+
+
This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+
+
Until next time
+
+
Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
+
+
– Robbie
+
+]]>
+
+
<![CDATA[0.30: More Async, HASSbian, Digital Ocean, statistics, REST]]>
@@ -1847,123 +2173,6 @@ Over a year ago I participated in the elevation: was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning [homeassistant.config] Incomplete core config. Auto detected elevation: 665 to your configuration.yaml file.
-]]>
-
-
-
- <![CDATA[Using USB webcams with Home Assistant]]>
-
- 2016-06-23T06:00:00+00:00
- https://home-assistant.io/blog/2016/06/23/usb-webcams-and-home-assistant
-
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
-
-
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
-
-
-
-
Check first if the your operating system lists your cameras.
-
-
$ lsusb
-[...]
-Bus 002 Device 016: ID 046d:08cc Logitech, Inc. Mic (PTZ)
-[...]
-
-
-
-
The camera we are going to use is available at /dev/video1. The C270 is the one on /dev/video0.
-
-
$ ls -al /dev/video*
-crw-rw----+ 1 root video 81, 0 Jun 23 08:05 /dev/video0
-crw-rw----+ 1 root video 81, 1 Jun 23 08:36 /dev/video1
-
-
-
-
We need an additional software part to handle the cameras. motion is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the RPM Fusion respository enabled.
-
-
$ sudo dnf -y install motion
-
-
-
-
For our setup we need to modify the file /etc/motion/motion.conf. For now the most important parameters are videodevice, snapshot_interval, and target_dir. The other settings can be left to their defaults. We are going to use the device /dev/video1, use a 30 seconds interval, and set the path to /tmp.
-
-
[...]
-###########################################################
-# Capture device options
-############################################################
-
-# Videodevice to be used for capturing (default /dev/video0)
-# for FreeBSD default is /dev/bktr0
-videodevice /dev/video1
-
-[..]
-############################################################
-# Snapshots (Traditional Periodic Webcam File Output)
-############################################################
-
-# Make automated snapshot every N seconds (default: 0 = disabled)
-snapshot_interval 30
-
-[...]
-############################################################
-# Target Directories and filenames For Images And Films
-# For the options snapshot_, picture_, movie_ and timelapse_filename
-# you can use conversion specifiers
-# %Y = year, %m = month, %d = date,
-# %H = hour, %M = minute, %S = second,
-# %v = event, %q = frame number, %t = thread (camera) number,
-# %D = changed pixels, %N = noise level,
-# %i and %J = width and height of motion area,
-# %K and %L = X and Y coordinates of motion center
-# %C = value defined by text_event
-# Quotation marks round string are allowed.
-############################################################
-
-# Target base directory for pictures and films
-# Recommended to use absolute path. (Default: current working directory)
-target_dir /tmp
-
-[...]
-
-
-
-
It’s suggested that you adjust at least width and height to get a bigger image from your camera. If you are done, fire up motion.
Your target_dir will start filling up with images from your camera. motion will create a symlink called lastsnap.jpg which always point to the latest snapshot. We will setup the Local File camera platform to use this file.
The machine with the attached USB camera will become a webcam server as well because motion’s built-in HTTP server is enabled by default. This means that you could connect your USB webcams to a different machine in your network, run motion there, adjust your firewall rules, and use Home Assistant to display the videos. Just check http://[IP of your webcam host]:8081/ to see the stream. This required more powerful hardware than using snapshots, of course.
camera:
- -platform:mjpeg
- mjpeg_url:http://[IP of your webcam host]:8081
- name:Cranberry Live cam
-
-
-
-
motion is a powerful tool and this blog post only showed two very simple use cases. Take a look at the documentation of motion to unleash its potential.
diff --git a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
index 5e05bb5b8a..d353c509ff 100644
--- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
+++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
@@ -224,6 +224,12 @@ This article will try to explain how they all relate.
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index ce1bcb2d0e..9f2f5b0f47 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -200,6 +200,12 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index 05ec5e1283..c7f58fd26d 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -176,6 +176,12 @@ The old logo, the new detailed logo and the new simple logo.
diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html
index c4b04d0367..a6e7c5ab34 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -209,6 +209,12 @@ An initial version of voice control for Home Assistant has landed. The current i
diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html
index 736d90b89e..7b54680b1b 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -244,6 +244,12 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index 2a263ff684..477098a742 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -276,6 +276,12 @@ Before diving into the newly supported devices and services, I want to highlight
diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html
index 1978574583..b9741a273b 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -327,6 +327,12 @@ This switch platform allows you to control your motion detection setting on your
diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
index 109017410b..4c3c7bd5e6 100644
--- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
+++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
@@ -283,6 +283,12 @@ Fabian has added support for Forecast.io to g
diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
index 5c4dd8a140..b98d99b55a 100644
--- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
+++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
@@ -268,6 +268,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -291,12 +297,6 @@ Support for Temper temperature sensors has been contributed by
- 0.28: Reload automation and groups, API documentation, car tracking, Pi-Hole stats
-
-
-
diff --git a/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html b/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
index 68928bb8a0..1eb4a69418 100644
--- a/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
+++ b/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
@@ -192,6 +192,12 @@
diff --git a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
index 4728ba4e9e..34199888e1 100644
--- a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
+++ b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
@@ -305,6 +305,12 @@ The automation and script syntax here is using a deprecated and no longer suppor
diff --git a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
index 43c89ddf46..2366226298 100644
--- a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
+++ b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
@@ -234,6 +234,12 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
index 537147cb3b..4d49ea112d 100644
--- a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
+++ b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
@@ -219,6 +219,12 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge
diff --git a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
index 9d32877b51..d65274012b 100644
--- a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
+++ b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
@@ -199,6 +199,12 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index c2e32264f2..2b5a13ee00 100644
--- a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
+++ b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
@@ -408,6 +408,12 @@ Home Assistant will keep track of historical values and allow you to integrate i
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index 77d593d48b..dbc6a187ae 100644
--- a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
+++ b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
@@ -210,6 +210,12 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index dca4d27b39..8805445806 100644
--- a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
+++ b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
@@ -225,6 +225,12 @@ This is where we’ll configure our task, so select the plus icon to select an a
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index 79a82a4248..211432b224 100644
--- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
+++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
@@ -143,10 +143,10 @@ Example of the new views in the frontend. Learn mor
Nest config has moved from thermostat to the Nest component.
-
Entity IDs for Z-Wave devices are now generated in a deterministic way causing all IDs to change starting this release. This is a one time change.
+
Entity IDs for Z-Wave devices are now generated in a deterministic way causing all IDs to change starting this release. This is a one time change. (Changed again in 0.31)
@@ -208,6 +208,12 @@ Example of the new views in the frontend. Learn mor
diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html
index 5f8586df32..1f9eed1116 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -219,6 +219,12 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
diff --git a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
index 8cc070d5c0..c53b78c1a4 100644
--- a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
+++ b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
@@ -299,6 +299,12 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index a12fc47ab2..03ecdd9d8f 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -218,6 +218,12 @@ Over a year ago I participated in the
+
@@ -241,12 +247,6 @@ Over a year ago I participated in the
- 0.28: Reload automation and groups, API documentation, car tracking, Pi-Hole stats
-
-
-
diff --git a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
index a3d80106de..f32ebde896 100644
--- a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
+++ b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
@@ -218,6 +218,12 @@
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 38fb3a11f5..4989b5a9c0 100644
--- a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
+++ b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
@@ -235,6 +235,12 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index 9b27b86b5d..22d0408e31 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -322,6 +322,12 @@ If a module is missing then you need to download it from the
+
@@ -345,12 +351,6 @@ If a module is missing then you need to download it from the
- 0.28: Reload automation and groups, API documentation, car tracking, Pi-Hole stats
-
-
-
diff --git a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
index a4bd36d780..3b6516dfce 100644
--- a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
+++ b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
@@ -237,6 +237,12 @@
diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
index 02ff516f00..4a8baa6673 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -266,6 +266,12 @@ So, part 1 of ESP8266
How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
+
+
Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
+
+
One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
+
+
Stats Update
+
Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+
+
Hacktoberfest
+
+
+
+
October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+
+
⚠️ A greatly improved updater component (Please read this!) ⚠️
+
+
This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+
+
It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
+
+
+
We are unable to do a slow rollout
+
We are unable to show the user extra information (like a link to a changelog or the release date)
+
We are unable to warn users for critical security updates
+
+
+
So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+
+
What you need to know (the important bit!)
+
+
Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+
+
Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
+
+
Opting out
+
+
There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
+
+
updater:
+ reporting:no
+
+
+
+
You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
+
+
Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
+
+
Data stored on the Home Assistant update server
+
+
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
+
+
+
+
+
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:
+
+
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 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.
+
+
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.
+
+
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.
+
+
Now, back to the fun stuff…
+
+
Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
+
+
Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+
+
0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+
+
+
Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
+
+
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.
+
+
+
+
Major breaking Z-Wave changes ahead
+
+
A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+
+
What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
+
+
+
Update customizations
+
Update groups
+
Update my zwave.customize section
+
Update my Alexa skills that used old entity IDs
+
Because I use emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
+
+
Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+
+
This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+
+
Until next time
+
+
Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
+
+
– Robbie
+
+
+
+
+
Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 82a7b6e2db..6e9eb0b24f 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -2929,6 +2929,38 @@
+
+
+
+
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 7d472bcb8d..87cd84a934 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-22T19:15:15+00:00
+ 2016-10-22T22:35:39+00:00https://home-assistant.io/
@@ -13,6 +13,283 @@
Octopress
+
+ <![CDATA[0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change]]>
+
+ 2016-10-22T20:00:00+00:00
+ https://home-assistant.io/blog/2016/10/22/flash-briefing-updater-hacktoberfest
+ Stats Update
+Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+
+## Hacktoberfest
+
+![Hacktoberfest logo][logo]
+
+October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the [home-assistant repository][hacktoberfest-ha-prs] and 209 merged/28 open pull requests submitted to the [home-assistant.github.io repository][hacktoberfest-site-prs]. If you want to get in on the fun check out our [Hacktoberfest][hacktoberfest-blog] blog post or the [Hacktoberfest website][hacktoberfest-website]. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+
+## ⚠️ A greatly improved updater component (Please read this!) ⚠️
+
+This release includes an update to our [updater] component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+
+It used to be that this component would check with [PyPi] (the Python package manager) to see if a new update was available. This had a couple of problems:
+
+ 1. We are unable to do a slow rollout
+ 2. We are unable to show the user extra information (like a link to a changelog or the release date)
+ 3. We are unable to warn users for critical security updates
+
+So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+
+### What you need to know (the important bit!)
+
+Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+
+Each Home Assistant instance running the updater component will generate a [unique ID][UUID] (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called `.uuid`.
+
+#### Opting out
+
+There are two ways to opt-out. The first way is by using the new `opt_out` option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
+
+```yaml
+updater:
+ reporting: no
+```
+
+You can also disable the updater component entirely by removing `updater:` from your `configuration.yaml` although **we would not suggest you do this** as you would miss any critical updates.
+
+Finally, you can also reset your unique identifier by deleting the `.uuid` file and restarting Home Assistant.
+
+#### Data stored on the Home Assistant update server
+
+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 |
+
+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: 
+
+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 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.
+
+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.
+
+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.
+
+Now, back to the fun stuff...
+
+## Good evening. I'm Ron Burgundy and here's what happening in your world tonight.
+
+Home Assistant got a crazy idea recently that it couldn't do enough already and wanted to challenge itself even more. I really don't understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+
+0.31 adds support for the brand spanking new [Alexa Flash Briefing API](https://developer.amazon.com/alexa-skills-kit/flash-briefing), allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What's the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+
+> Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
+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].
+
+
+
+## Major breaking Z-Wave changes ahead
+
+A rather nasty Z-Wave [issue][z-wave-issue] was discovered recently by [@lukas-hetzenecker]. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+
+What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here's what I had to do:
+
+- Update customizations
+- Update groups
+- Update my `zwave.customize` section
+- Update my Alexa skills that used old entity IDs
+- Because I use `emulated_hue` with Alexa and `emulated_hue` uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
+Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It's not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+
+This is super annoying, I know, especially since we had said in [0.12][zero-one-two-release] that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn't change in the future but obviously we see how that went. To sum up on this section... sorry but it had to happen.
+
+## All changes
+
+- [Updater] component ([@infamy], [@robbiet480], [@kellerza])
+- Continue to setup other platforms when 1 platform config is invalid ([@kellerza])
+- Create [persistent notifications][pers-notify] when a platform contains invalid config ([@kellerza])
+- Logbook: Allow [filtering] domains and entities to be shown ([@wokar])
+- HTTP: Change `approved_ips` from string to CIDR validation ([@mweinelt])
+- Persistent Notifications: Allow using [markdown][pers-notify] ([@justweb1])
+- Netatmo: Add [discovery][netatmo-discovery] support ([@jabesq])
+- Netatmo Welcome camera: Add [binary sensor][netatmo-bin] ([@jabesq])
+- Support added for [HaveIBeenPwned] ([@joyrider3774])
+- Device tracker: `known_devices.yaml` reading and writing tweaks and fixes ([@kellerza])
+- Fix climate platforms showing the wrong temperature unit ([@rcloran])
+- Lots of voluptuous love ([@fabaff])
+- Ensure proper attribution for weather platforms ([@fabaff])
+- Fix Telegram in Docker ([@jeanregisser])
+- Support recursive config inclusions in YAML ([@lwis])
+- Camera: [Synology] SS cameras now supported ([@jgriff2])
+- History: Allow filtering domains and entities to be shown ([@wokar])
+- Media Player - Squeezebox: Now able to show artist and album ([@ih8gates])
+- Alexa: Flash Briefing skill support added ([@robbiet480])
+- Device Tracker: Add support for Bbox Modem Router ([@HydrelioxGithub])
+- Sensor: Add support for Bbox Modem Router ([@HydrelioxGithub])
+- Input select: Services added to pick next and prev option ([@persandstrom])
+- Sensor: [ARWN] now supported ([@sdague])
+- Pushbullet: Push an URL note if an url is provided inside data ([@jabesq])
+- Z-Wave: Allow certain devices to be not added to Home Assistant ([@lukas-hetzenecker])
+- New support for [Zoneminder] added ([@Khabi])
+- Weather: Allow tracking severe weather alerts with [WUnderground] ([@tchellomello])
+- Sensor: New support added to track [min/max/mean][min] ([@fabaff])
+- Convert EntityComponent to be async ([@pvizeli], [@balloob])
+- Z-Wave: Add assocation service ([@turbokongen])
+- Frontend - Services dev tool: persist state and tweak UI ([@justweb1])
+- Sensor: Support added for [scraping][scrape] websites ([@fabaff])
+- Clean up of tests ([@capellini])
+- New `fail` filter added to templates to raise on UndefinedError ([@jaharkes])
+- Support added for [Emoncms history][emoncms] ([@joyrider3774])
+- Support for [Apple Push Notifications Service][APNS] ([@sam-io])
+- Thermostat: Netatmo now supported ([@gieljnssns])
+- Alarm control panel: [Concord232] now supported ([@JasonCarter80])
+- Notify: [Matrix] support added ([@mweinelt])
+- Device tracker - nmap: Allow specifying multiple inputs for [nmap] ([@hcooper])
+- Device Tracker - snmp: SNMPv3 now supported ([@T3m3z])
+- Notify: [Telstra] SMS now supported ([@nvella])
+- Camera: [Verisure] now supported ([@turbokongen])
+- Support added for [Neato] Connected Robot ([@jabesq])
+- Media player: More options for [Yamaha] AVR ([@ehagan])
+- Sensor: Support for [Pilight] sensor ([@DavidLP])
+- 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].
+
+## 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
+
+## If you need help...
+...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
+
+## Until next time
+
+Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
+
+-- Robbie
+
+[@balloob]: https://github.com/balloob
+[@capellini]: https://github.com/capellini
+[@c-w]: https://github.com/c-w
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@DavidLP]: https://github.com/DavidLP
+[@ehagan]: https://github.com/ehagan
+[@fabaff]: https://github.com/fabaff
+[@flyte]: https://github.com/flyte
+[@gieljnssns]: https://github.com/gieljnssns
+[@hartmms]: https://github.com/hartmms
+[@hcooper]: https://github.com/hcooper
+[@HydrelioxGithub]: https://github.com/HydrelioxGithub
+[@ih8gates]: https://github.com/ih8gates
+[@infamy]: https://github.com/infamy
+[@ishults]: https://github.com/ishults
+[@jabesq]: https://github.com/jabesq
+[@jaharkes]: https://github.com/jaharkes
+[@JasonCarter80]: https://github.com/JasonCarter80
+[@jeanregisser]: https://github.com/jeanregisser
+[@jgriff2]: https://github.com/jgriff2
+[@joyrider3774]: https://github.com/joyrider3774
+[@justweb1]: https://github.com/justweb1
+[@kellerza]: https://github.com/kellerza
+[@Khabi]: https://github.com/Khabi
+[@kirichkov]: https://github.com/kirichkov
+[@lukas-hetzenecker]: https://github.com/lukas-hetzenecker
+[@lwis]: https://github.com/lwis
+[@mezz64]: https://github.com/mezz64
+[@molobrakos]: https://github.com/molobrakos
+[@mtl010957]: https://github.com/mtl010957
+[@mweinelt]: https://github.com/mweinelt
+[@Nixon506E]: https://github.com/Nixon506E
+[@nvella]: https://github.com/nvella
+[@persandstrom]: https://github.com/persandstrom
+[@phardy]: https://github.com/phardy
+[@pvizeli]: https://github.com/pvizeli
+[@rcloran]: https://github.com/rcloran
+[@robbiet480]: https://github.com/robbiet480
+[@sam-io]: https://github.com/sam-io
+[@sander76]: https://github.com/sander76
+[@sdague]: https://github.com/sdague
+[@StaticCube]: https://github.com/StaticCube
+[@T3m3z]: https://github.com/T3m3z
+[@tchellomello]: https://github.com/tchellomello
+[@turbokongen]: https://github.com/turbokongen
+[@vittoriom]: https://github.com/vittoriom
+[@wokar]: https://github.com/wokar
+
+[APNS]: https://home-assistant.io/components/notify.apns/
+[ARWN]: https://home-assistant.io/components/sensor.arwn/
+[Concord232]: https://home-assistant.io/components/alarm_control_panel.concord232/
+[HTTP]: https://home-assistant.io/components/http/
+[HaveIBeenPwned]: https://home-assistant.io/components/sensor.haveibeenpwned/
+[Matrix]: https://home-assistant.io//components/notify.matrix/
+[Neato]: https://home-assistant.io/components/switch.neato/
+[Pilight]: https://home-assistant.io/components/sensor.pilight/
+[Proximity]: https://home-assistant.io/components/proximity/
+[PyPi]: https://pypi.python.org/pypi
+[Synology]: https://home-assistant.io/components/camera.synology/
+[Telstra]: https://home-assistant.io/components/notify.telstra/
+[UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier
+[Verisure]: https://home-assistant.io/components/camera.verisure/
+[WUnderground]: https://home-assistant.io/components/sensor.wunderground/
+[Yamaha]: https://home-assistant.io/components/media_player.yamaha/
+[Zoneminder]: https://home-assistant.io/components/zoneminder/
+[emoncms]: https://home-assistant.io//components/emoncms_history/
+[filtering]: https://home-assistant.io/components/logbook/
+[flash-briefing-docs]: https://home-assistant.io/components/alexa/
+[hacktoberfest-blog]: /blog/2016/10/02/hacktoberfest/
+[hacktoberfest-ha-prs]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
+[hacktoberfest-site-prs]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
+[hacktoberfest-website]: https://hacktoberfest.digitalocean.com/
+[logo]: /images/blog/2016-10-hacktoberfest/hacktoberfest.png
+[min]: https://home-assistant.io/components/sensor.min_max/
+[netatmo-bin]: https://home-assistant.io/components/binary_sensor.netatmo/
+[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
+[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
+[zero-one-two-release]: /blog/2016/01/30/insteon-lifx-twitter-and-zigbee/#backwards-incompatible-changes
+[zero-two-seven-release]: /blog/2016/08/28/notifications-hue-fake-unification/
+[twitter]: https://twitter.com/home_assistant
+[robbie-twitter]: https://twitter.com/robbie
+]]>
+
+
<![CDATA[0.30: More Async, HASSbian, Digital Ocean, statistics, REST]]>
@@ -800,121 +1077,6 @@ Talk to you soon on Gitter and in your pull request comments!
[Hue]: /components/emulated_hue/
[fan]: /components/fan/
[IMAP]: /components/sensor.imap/
-]]>
-
-
-
- <![CDATA[0.26: Foursquare, Fast.com, FFMPEG and GPSD]]>
-
- 2016-08-13T19:00:00+00:00
- https://home-assistant.io/blog/2016/08/13/foursquare-fast-com-ffmpeg-gpsd
-
-
-- Core: Introduce notion of unit system (deprecates temperature unit option) ([@Teagan42])
-- Front end: Speed improvements ([@balloob])
-- Front end: Improve layout of state dev tool ([@balloob])
-- [Proximity]\: Allow definition of unit of measurement ([@Teagan42])
-- [Flux]\: Add mired and kelvin mode ([@HBDK])
-- Thermostat - [Proliphix]: Support for cooling ([@sdague])
-- Media Player - [LG Netcast TV]: Show screenshot of what is currently playing ([@shmuelzon])
-- Z-Wave improvements ([@jnewland], [@turbokongen])
-- Thermostat - [heat control]: now also able to control an AC ([@mtreinish])
-- Thermostat - [heat control]: allow specifying a minimum duration before switching ([@mtreinish])
-- [InfluxDB]\: Whitelist entities option added ([@tchellomello])
-- Sensor: Serial [particulate matters][particulate] sensors now supported ([@open-homeautomation])
-- Sensor - [Fitbit]: Fix unit system ([@tchellomello])
-- Light - [Flux LED]: Add support for [color and brightness][color] ([@Danielhiversen])
-- Media Player - [Plex]: Now able to report on music ([@abcminiuser])
-- Alarm Control Panel - [Verisure]: Now able to see who changed the alarm ([@persandtrom])
-- Thermostat - [Honeywell]: Add option to read and control HVAC mode ([@Teagan42])
-- [Foursquare] component to receive instant notifications of checkins ([@robbiet480])
-- Camera: New [FFMPEG] platform allows to stream anything through front end ([@pvizeli])
-- Manage [secrets] with new command line script ([@kellerza])
-- Notify - [SMTP]: Allow embedding of images ([@partofthething])
-- Sensor: [OhmConnect] is now supported ([@robbiet480])
-- [panel_custom] component allows the registering of new panels ([@balloob])
-- Light: New [mqtt_json] platform for working with JSON payload ([@corbanmailloux])
-- Sensor: New [Fast.com] platform to measure network bandwidth performance ([@nkgilley])
-- New [pilight] component to control 433 Mz devices ([@DavidLP])
-- Sensor: [GPSD] now supported ([@fabaff])
-
-### Hotfix 0.26.1 - August 14
-
-- Fix serial_pm config validation ([@open-homeautomation])
-- Check for existence of system mode on Honeywell thermostats ([@mKeRix])
-- Fix unknown unit of measurement for hvac and thermostat component ([@turbokongen])
-
-### Hotfix 0.26.2 - August 15
-
-- Fix Wemo: have PyWemo play nicely with the latest Requests ([@pavoni])
-
-### Hotfix 0.26.3 - August 19
-
-- Media Player cover art would not work when an API password was set. Thanks to [@maddox] for reporting it and [@balloob] for the fix.
-
-### Breaking changes
-
- - A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
-
-```yaml
-# Configuration.yaml example
-homeassistant:
- # 'metric' for the metric system, 'imperial' for the imperial system
- unit_system: metric
-```
-
-[@maddox]: https://github.com/maddox
-[@pavoni]: https://github.com/pavoni
-[@mKeRix]: https://github.com/mKeRix
-[@abcminiuser]: https://github.com/abcminiuser
-[@balloob]: https://github.com/balloob
-[@corbanmailloux]: https://github.com/corbanmailloux
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@DavidLP]: https://github.com/DavidLP
-[@fabaff]: https://github.com/fabaff
-[@HBDK]: https://github.com/HBDK
-[@jnewland]: https://github.com/jnewland
-[@kellerza]: https://github.com/kellerza
-[@mtreinish]: https://github.com/mtreinish
-[@nkgilley]: https://github.com/nkgilley
-[@open-homeautomation]: https://github.com/open-homeautomation
-[@partofthething]: https://github.com/partofthething
-[@persandtrom]: https://github.com/persandtrom
-[@pvizeli]: https://github.com/pvizeli
-[@robbiet480]: https://github.com/robbiet480
-[@sdague]: https://github.com/sdague
-[@shmuelzon]: https://github.com/shmuelzon
-[@tchellomello]: https://github.com/tchellomello
-[@Teagan42]: https://github.com/Teagan42
-[@turbokongen]: https://github.com/turbokongen
-[@fabaff]: https://github.com/fabaff
-
-[Foursquare]: /components/foursquare/
-[OhmConnect]: /components/sensor.ohmconnect/
-[FFMPEG]: /components/camera.ffmpeg/
-[SMTP]: /components/notify.smtp/
-[panel_custom]: /components/panel_custom/
-[Verisure]: /components/alarm_control_panel.verisure/
-[Flux LED]: /components/light.flux_led/
-[InfluxDB]: /components/influxdb/
-[particulate]: /components/sensor.serial_pm/
-[LG Netcast TV]: /components/media_player.lg_netcast/
-[mqtt_json]: /components/light.mqtt_json/
-[Fast.com]: /components/sensor.fastdotcom/
-[pilight]: /components/pilight/
-[GPSD]: /components/sensor.gpsd/
-[heat control]: /components/thermostat.heat_control/
-[Proximity]: /components/proximity/
-[Flux]: /components/switch.flux/
-[Proliphix]: /components/thermostat.proliphix/
-[Fitbit]: /components/sensor.fitbit/
-[Plex]: /components/media_player.plex/
-[Honeywell]: /components/thermostat.honeywell/
-[Secrets]: /topics/secrets/
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index b983ead0ad..fe3f169577 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -98,6 +98,38 @@
How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
+
+
Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
+
+
One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
+
+
Stats Update
+
Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+
+
Hacktoberfest
+
+
+
+
October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+
+
⚠️ A greatly improved updater component (Please read this!) ⚠️
+
+
This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+
+
It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
+
+
+
We are unable to do a slow rollout
+
We are unable to show the user extra information (like a link to a changelog or the release date)
+
We are unable to warn users for critical security updates
+
+
+
So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+
+
What you need to know (the important bit!)
+
+
Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+
+
Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
+
+
Opting out
+
+
There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
+
+
updater:
+ reporting:no
+
+
+
+
You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
+
+
Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
+
+
Data stored on the Home Assistant update server
+
+
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
+
+
+
+
+
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:
+
+
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 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.
+
+
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.
+
+
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.
+
+
Now, back to the fun stuff…
+
+
Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
+
+
Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+
+
0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+
+
+
Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
+
+
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.
+
+
+
+
Major breaking Z-Wave changes ahead
+
+
A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+
+
What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
+
+
+
Update customizations
+
Update groups
+
Update my zwave.customize section
+
Update my Alexa skills that used old entity IDs
+
Because I use emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
+
+
Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+
+
This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+
+
Until next time
+
+
Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
-
-
This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
-
-
-
-
-
Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42)
Check for existence of system mode on Honeywell thermostats (@mKeRix)
-
Fix unknown unit of measurement for hvac and thermostat component (@turbokongen)
-
-
-
Hotfix 0.26.2 - August 15
-
-
-
Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni)
-
-
-
Hotfix 0.26.3 - August 19
-
-
-
Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix.
-
-
-
Breaking changes
-
-
-
A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
-
-
-
# Configuration.yaml example
-homeassistant:
- # 'metric' for the metric system, 'imperial' for the imperial system
- unit_system:metric
-
It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
+
+
This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
+
+
+
+
+
Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42)
Check for existence of system mode on Honeywell thermostats (@mKeRix)
+
Fix unknown unit of measurement for hvac and thermostat component (@turbokongen)
+
+
+
Hotfix 0.26.2 - August 15
+
+
+
Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni)
+
+
+
Hotfix 0.26.3 - August 19
+
+
+
Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix.
+
+
+
Breaking changes
+
+
+
A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
+
+
+
# Configuration.yaml example
+homeassistant:
+ # 'metric' for the metric system, 'imperial' for the imperial system
+ unit_system:metric
+
+
+
+
+
+
+
+
+
@@ -700,53 +809,6 @@ Over a year ago I participated in the
-
-
-
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
-
-
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
+In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
+
+
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
-
-
Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
+
+
Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
-
-
-
@fabaff has upgraded the codebase to follow the PEP257 documentation standard.
-
@partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version.
-
To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more.
-
@MartinHjelmare has upgraded our scene support to now support all built-in services and components.
-
-
-
Besides bug fixes, this release also brings:
-
-
-
-
-
Scene: Converted to a platform based component (@sander76)
# Example using templates for service and data in service call.
-# Works for automation, Alexa, universal media player, template switch.
-automation:
- -trigger:
- -platform:state
- entity_id:switch.bathroom
- action:
- service_template:>
- {% if is_state('switch.bathroom', 'on') %}
- switch.turn_on
- {% else %}
- switch.turn_off
- {% endif %}
- data_template:
- entity_id:switch.{{ states('input_select.is') }}
-
-
-
-
Breaking Changes
-
-
-
Media Player: Attributes to call service play_media has been renamed to
-media_content_type and media_content_id, to match the corresponding media
-player state attributes. This change affects automations, scripts and scenes.
Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
+
+
+
@fabaff has upgraded the codebase to follow the PEP257 documentation standard.
+
@partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version.
+
To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more.
+
@MartinHjelmare has upgraded our scene support to now support all built-in services and components.
+
+
+
Besides bug fixes, this release also brings:
+
+
+
+
+
Scene: Converted to a platform based component (@sander76)
# Example using templates for service and data in service call.
+# Works for automation, Alexa, universal media player, template switch.
+automation:
+ -trigger:
+ -platform:state
+ entity_id:switch.bathroom
+ action:
+ service_template:>
+ {% if is_state('switch.bathroom', 'on') %}
+ switch.turn_on
+ {% else %}
+ switch.turn_off
+ {% endif %}
+ data_template:
+ entity_id:switch.{{ states('input_select.is') }}
+
+
+
+
Breaking Changes
+
+
+
Media Player: Attributes to call service play_media has been renamed to
+media_content_type and media_content_id, to match the corresponding media
+player state attributes. This change affects automations, scripts and scenes.
+
+
+
+
+
+
+
+
@@ -620,10 +707,10 @@ Example of the new views in the frontend. Learn mor
Nest config has moved from thermostat to the Nest component.
-
Entity IDs for Z-Wave devices are now generated in a deterministic way causing all IDs to change starting this release. This is a one time change.
+
Entity IDs for Z-Wave devices are now generated in a deterministic way causing all IDs to change starting this release. This is a one time change. (Changed again in 0.31)
@@ -754,71 +841,6 @@ Example of the new views in the frontend. Learn mor
-
-
-
-
-
-
-
-
Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.
-
-
For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Asssistant can pick it up.
-
-
-
-Picture of the final setup (+ 2 LED for decoration)
-
-
-
-
-Home Assistant will keep track of historical values and allow you to integrate it into automation.
-
I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.
+
+
For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Asssistant can pick it up.
+
+
+
+Picture of the final setup (+ 2 LED for decoration)
+
+
+
+
+Home Assistant will keep track of historical values and allow you to integrate it into automation.
+
It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.
-
-
MQTT Support
- The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.
-
-
# Example configuration.yaml entry
-mqtt:
- broker:IP_ADDRESS_BROKER
- # All the other options are optional:
- port:1883
- keepalive:60
- qos:0
- username:your_username
- password:your_secret_password
-
It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.
+
+
MQTT Support
+ The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.
+
+
# Example configuration.yaml entry
+mqtt:
+ broker:IP_ADDRESS_BROKER
+ # All the other options are optional:
+ port:1883
+ keepalive:60
+ qos:0
+ username:your_username
+ password:your_secret_password
+
Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
-
-
A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
+
+
A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
The concord232 platform provides integration with GE, Interlogix (and other brands) alarm panels that support the RS-232 Automation Control Panel interface module (or have it built in). Supported panels include Concord 4.
+
+
To enable this, add the following lines to your configuration.yaml:
+
+
# Example configuration.yaml entry
+alarm_control_panel:
+ -platform:concord232
+
+
+
+
Configuration variables:
+
+
+
host (Optional): The host where the concord232 server process is running. Defaults to localhost.
+
port (Optional): The port where the Alarm panel ist listening. Defaults to 5007.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/alarm_control_panel.envisalink/index.html b/components/alarm_control_panel.envisalink/index.html
index 5803564e59..7fa867eb0e 100644
--- a/components/alarm_control_panel.envisalink/index.html
+++ b/components/alarm_control_panel.envisalink/index.html
@@ -140,6 +140,9 @@
There are two ways that you can use Amazon Echo and Home Assistant together.
+
There are a few ways that you can use Amazon Echo and Home Assistant together.
-
No matter which method(s) you decide to use, please remember that Amazon Echo requires an active Internet connection to function. If your Internet is down or experiencing issues (or Amazon’s infrastructure is having issues), neither of these methods will work.
No matter which method(s) you decide to use, please remember that Amazon Echo requires an active Internet connection to function. If your Internet is down or experiencing issues (or Amazon’s infrastructure is having issues), none of these methods will work.
Amazon has released Echosim, a website that simulates the Alexa service in your browser. That way it is easy to test your skills without having access to a physical Amazon Echo.
Alexa works based on intents. Each intent has a name and variable slots. For example, a LocateIntent with a slot that contains a User. Example intent schema:
@@ -383,6 +392,70 @@ Custom slot type for script support.
Alexa will now respond with a random phrase each time. You can use the include for as many different intents as you like so you only need to create the list once.
+
Flash Briefing Skills
+
+
As of version 0.31 Home Assistant supports the new Alexa Flash Briefing Skills API. A Flash Briefing Skill adds a new Flash Briefing source that is generated by Home Assistant.
+
+
Configuring a Flash Briefing skill in Home Assistant
+
+
You can use templates for the title, audio, text and display_url configuration parameters.
+
+
Here’s an example configuration of a Flash briefing skill that will tell you who is at home:
+
+
# Example configuration.yaml entry
+alexa:
+ flash_briefings:
+ whoishome:
+ -title:Who's at home?
+ text:>
+ {%- if is_state('device_tracker.paulus', 'home') and
+ is_state('device_tracker.anne_therese', 'home') -%}
+ You are both home, you silly
+ {%- else -%}
+ Anne Therese is at {{ states("device_tracker.anne_therese") }}
+ and Paulus is at {{ states("device_tracker.paulus") }}
+ {% endif %}
+
+
+
+
You can add multiple items for a feed if you want. The Amazon required uid and timestamp will be randomly generated at startup and change at every restart of Home Assistant.
+
+
Please refer to the Amazon documentation for more information about allowed configuration parameters and formats.
Click the yellow “Add a new skill” button in the top right
+
+
Skill Information
+
+
For Skill Type select Flash Briefing Skill API
+
You can enter whatever name you want
+
Hit next
+
+
+
Interaction Model
+
+
Nothing to do here
+
+
+
Configuration
+
+
Add new feed
+
+
For URL, enter https://YOUR_HOST/api/alexa/flash_briefings/BRIEFING_ID?api_password=YOUR_API_PASSWORD where BRIEFING_ID is the key you entered in your configuration (such as whoishome in the above example)
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index e9315c5af3..6f7ce04b77 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -215,6 +215,9 @@ This sensor is not suitable for fast state changes because there is a high possi
The concord232 platform provides integration with GE, Interlogix (and other brands) alarm panels that support the RS-232 Automation Control Panel interface module (or have it built in). Supported panels include Concord 4.
+
+
To enable this, add the following lines to your configuration.yaml:
+
+
# Example configuration.yaml entry
+binary_sensor:
+ -platform:concord232
+
+
+
+
Configuration variables:
+
+
+
host (Optional): The host where the concord232 server process is running. Defaults to localhost.
+
port (Optional): The port where the Alarm panel ist listening. Defaults to 5007.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/binary_sensor.ecobee/index.html b/components/binary_sensor.ecobee/index.html
index 61b43f58e2..042af38014 100644
--- a/components/binary_sensor.ecobee/index.html
+++ b/components/binary_sensor.ecobee/index.html
@@ -181,6 +181,9 @@
diff --git a/components/binary_sensor.ffmpeg/index.html b/components/binary_sensor.ffmpeg/index.html
index 327f688718..5f4837d4d9 100644
--- a/components/binary_sensor.ffmpeg/index.html
+++ b/components/binary_sensor.ffmpeg/index.html
@@ -250,6 +250,9 @@ If the ffmpeg process is broken, the sens
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index 0daafe959f..7f94bc5d62 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -238,6 +238,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/binary_sensor.nest/index.html b/components/binary_sensor.nest/index.html
index 35d48d64d7..ea1c3bbf0a 100644
--- a/components/binary_sensor.nest/index.html
+++ b/components/binary_sensor.nest/index.html
@@ -223,6 +223,9 @@ You must have the Nest component configured to u
The netatmo binary sensor platform is consuming the information provided by a Netatmo Welcome camera. This component allows you to get the latest event seen by the camera.
+
+
To enable the Netatmo binary sensor, you have to set up netatmo, this will use discovery to add your binary sensor.
+
+
Advanced configuration
+
+
If you want to select a specific sensor, set discovery to False for netatmo and add the following lines to your configuration.yaml:
home (Optional): Will use the cameras of this home only.
+
cameras array (Optional): Cameras to use. Multiple enties allowed.
+
+
‘camera_name’: Name of the camera to display.
+
+
+
monitored_conditions array (Optional): List of monitored conditions.
+
+
‘Someone known’
+
‘Someone unknown’
+
‘Motion’
+
+
+
+
+
If home and cameras is not provided, all cameras will be used. If multiple cameras are available then each monitored conditions will create a specific sensor for each camera
+
+
+Welcome tags are not yet supported, but will be in a next update.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/binary_sensor.nx584/index.html b/components/binary_sensor.nx584/index.html
index 51a103edf4..817a77e6d1 100644
--- a/components/binary_sensor.nx584/index.html
+++ b/components/binary_sensor.nx584/index.html
@@ -208,6 +208,9 @@
diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html
index d8835b8e1f..3bff8fdce4 100644
--- a/components/binary_sensor.octoprint/index.html
+++ b/components/binary_sensor.octoprint/index.html
@@ -201,6 +201,9 @@ You must have the OctoPrint component confi
diff --git a/components/binary_sensor.rest/index.html b/components/binary_sensor.rest/index.html
index 8d980475ac..4b44e92128 100644
--- a/components/binary_sensor.rest/index.html
+++ b/components/binary_sensor.rest/index.html
@@ -244,6 +244,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/camera.foscam/index.html b/components/camera.foscam/index.html
index 659635abc7..38dfc6ca8a 100644
--- a/components/camera.foscam/index.html
+++ b/components/camera.foscam/index.html
@@ -169,9 +169,18 @@ There seems to be some issues within Foscam with lengthy passwords and passwords
diff --git a/components/camera.local_file/index.html b/components/camera.local_file/index.html
index 9a4d64fe18..fccf9417a9 100644
--- a/components/camera.local_file/index.html
+++ b/components/camera.local_file/index.html
@@ -170,9 +170,18 @@ The given file_path must be an existing f
diff --git a/components/camera.mjpeg/index.html b/components/camera.mjpeg/index.html
index 55dff54f47..4dde7657d7 100644
--- a/components/camera.mjpeg/index.html
+++ b/components/camera.mjpeg/index.html
@@ -169,9 +169,18 @@ There is a
-
To enable the Netatmo camera, you first have to set up netatmo, and add the following lines to your configuration.yaml:
+
The netatmo camera platform is consuming the information provided by a Netatmo Welcome camera. This component allows you to view the current photo created by the Camera.
+
+
To enable the Netatmo camera, you have to set up netatmo, this will use discovery to add your camera.
+
+
Advanced configuration
+
+
If you want to select a specific camera, set discovery to False for netatmo and add the following lines to your configuration.yaml:
# Example configuration.yaml entrycamera:
@@ -151,6 +157,9 @@
diff --git a/components/device_tracker.actiontec/index.html b/components/device_tracker.actiontec/index.html
index 62b7b8f992..a32c169fd9 100644
--- a/components/device_tracker.actiontec/index.html
+++ b/components/device_tracker.actiontec/index.html
@@ -161,6 +161,9 @@ This device tracker needs telnet to be enabled on the router.
diff --git a/components/device_tracker.aruba/index.html b/components/device_tracker.aruba/index.html
index 7d18e87c10..18df4a1561 100644
--- a/components/device_tracker.aruba/index.html
+++ b/components/device_tracker.aruba/index.html
@@ -164,6 +164,9 @@ This device tracker needs telnet to be enabled on the router.
diff --git a/components/device_tracker.asuswrt/index.html b/components/device_tracker.asuswrt/index.html
index e444721fb6..91c2854220 100644
--- a/components/device_tracker.asuswrt/index.html
+++ b/components/device_tracker.asuswrt/index.html
@@ -159,6 +159,9 @@ You need to enable telnetBT Home Hub 5
+
The bbox platform offers presence detection by looking at connected devices to a Bbox based router from Bouygues, which is one of the main Internet provider in France.
+
+
+Bbox is a generic name for different hardware routers. The platform has only been tested on a Sagem F@st 5330b because it’s the only model the developer owns.
+
+
+
To use an Bbox router in your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+device_tracker:
+ -platform:bbox
+
+
+
+
+For now and due to third party limitation, the Bbox must be on the same local network as the Home Assistant installation. And with the default IP configuration (IP of the router must be 192.168.1.254).
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/device_tracker.bluetooth_le_tracker/index.html b/components/device_tracker.bluetooth_le_tracker/index.html
index 60d731191a..1cada6346e 100644
--- a/components/device_tracker.bluetooth_le_tracker/index.html
+++ b/components/device_tracker.bluetooth_le_tracker/index.html
@@ -168,6 +168,9 @@ Some BTLE devices (e.g. fitness trackers) are only visible to the devices that t
diff --git a/components/device_tracker.fritz/index.html b/components/device_tracker.fritz/index.html
index 0c5927a0b0..6fa81009a3 100644
--- a/components/device_tracker.fritz/index.html
+++ b/components/device_tracker.fritz/index.html
@@ -159,6 +159,9 @@ It seems that it is not necessary to use it in current generation Fritz!Box rout
diff --git a/components/device_tracker.icloud/index.html b/components/device_tracker.icloud/index.html
index c29d0c14bb..aeb127b771 100644
--- a/components/device_tracker.icloud/index.html
+++ b/components/device_tracker.icloud/index.html
@@ -164,6 +164,9 @@ If you have two-factor authentication enabled on your iCloud account you will no
diff --git a/components/device_tracker.luci/index.html b/components/device_tracker.luci/index.html
index 90ab0ac97c..0d421165e3 100644
--- a/components/device_tracker.luci/index.html
+++ b/components/device_tracker.luci/index.html
@@ -166,6 +166,9 @@ Some installations have a s
If you’re on Debian or Ubuntu, you might have to install the packages for arp and nmap. Do so by running $ sudo apt-get install net-tools nmap. On a Fedora host run $ sudo dnf -y install nmap.
+
Host detection is done via Nmap’s “fast scan” (-F) of the most frequently used 100 ports, with a host timeout of 5 seconds.
+
To use this device tracker in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
@@ -105,7 +107,7 @@
Configuration variables:
-
hosts (Required): The network range to scan in CIDR notation, eg. 192.168.1.1/24.
+
hosts (Required): The network address to scan (in any supported NMap format). Mixing subnets and IPs is possible.
home_interval (Optional): The number of minutes nmap will not scan this device, assuming it is home, in order to preserve the device battery.
exclude (Optional): Hosts not to include in nmap scanning.
@@ -113,6 +115,7 @@
A full example for the nmap tracker could look like the following sample:
# Example configuration.yaml entry for nmap
+# One whole subnet, and skipping two specific IPs.device_tracker:-platform:nmap_trackerhosts:192.168.1.1/24
@@ -123,6 +126,17 @@
+
# Example configuration.yaml for nmap
+# One subnet, and two specific IPs in another subnet.
+device_tracker:
+ -platform:nmap_tracker
+ hosts:
+ -192.168.1.1/24
+ -10.0.0.2
+ -10.0.0.15
+
diff --git a/components/device_tracker.snmp/index.html b/components/device_tracker.snmp/index.html
index 6c281b4755..dff00655be 100644
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@@ -107,9 +107,9 @@ This device tracker needs SNMP to be enabled on the router.
TPLink: 1.3.6.1.2.1.3.1.1.2.19.1 (Archer VR2600v, need to enable SNMP service)
-
To use the SNMP platform in your installation, add the following to your configuration.yaml file:
+
To use the SNMP version 1 platform in your installation, add the following to your configuration.yaml file:
-
# Example configuration.yaml entry
+
# Example configuration.yaml entry for SNMP version 1device_tracker:-platform:snmphost:192.168.1.1
@@ -117,12 +117,28 @@ This device tracker needs SNMP to be enabled on the router.
baseoid:1.3.6.1.4.1.14988.1.1.1.2.1.1
+
+
If you want to use encryption, you must enable SNMP version 3 by adding authkey and privkey variables and enabling SNMP version 3 on your router. Currently only SHA1 is supported for authentication and AES for encryption. Example of SNMPv3 configuration:
+
+
# Example configuration.yaml entry for SNMP version 3
+device_tracker:
+ -platform:snmp
+ host:192.168.1.1
+ community:username
+ authkey:authpass
+ privkey:privpass
+ baseoid:1.3.6.1.4.1.14988.1.1.1.2.1.1
+
+
+
Configuration variables:
host (Required): The IP address of the router, eg. 192.168.1.1.
community (Required): The SNMP community which is set for the device. Most devices have a default community set to to public with read-only permission (which is sufficient).
baseoid (Required): The OID prefix where wireless client registrations can be found, usually vendor specific. It’s advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.
+
authkey (Inclusive): Authentication key for SNMPv3. Variable privkey must also be set.
+
privkey (Inclusive): Privacy key SNMPv3. Variable authkey must also be set.
diff --git a/components/device_tracker.tplink/index.html b/components/device_tracker.tplink/index.html
index b7bec43976..37407fd585 100644
--- a/components/device_tracker.tplink/index.html
+++ b/components/device_tracker.tplink/index.html
@@ -174,6 +174,9 @@ TP-Link devices typically only allow one login at a time to the admin console.
The emoncms_history component makes it possible to transfer details collected with Home Assistant to Emoncms.org or your local running Emoncms instance. It will send the data to a specific input node on Emoncms with the entity IDs as a key. Afterwards you can create feeds and dashboards in Emoncms with the collected data.
+
+
To use the emoncms_history component in your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+emoncms_history:
+ api_key:put your emoncms WRITE api key here
+ url:https://emoncms.org
+ inputnode:19
+ whitelist:
+ -sensor.owm_temperature
+ -sensor.owm_wind_speed
+
+
+
+
Configuration variables:
+
+
+
api_key (Required): Your emoncms write api key
+
url (Required): The root URL of your Emoncms installation. (Use https://emoncms.org for the cloud based version)
+
inputnode (Required): Input node that will be used inside emoncms. Please make sure you use a dedicated, not used before, node for this component!
+
whitelist (Required): List of entity IDs you want to publish.
+
scan_interval (Optional): Defines, in seconds, how reguarly the states of the whitelisted entities are being gathered and send to emoncms. Default is 30 seconds.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/envisalink/index.html b/components/envisalink/index.html
index 29f58ce368..451c88e24b 100644
--- a/components/envisalink/index.html
+++ b/components/envisalink/index.html
@@ -192,6 +192,9 @@
diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html
index ea7112feab..2fff5a9be6 100644
--- a/components/ffmpeg/index.html
+++ b/components/ffmpeg/index.html
@@ -108,6 +108,18 @@ You need the ffmpeg binary in your system
run_test (Optional): Default True. Check if input is usable by ffmpeg.
+
Raspbian Debian Jessie Lite Installations
+
To get the binary on Raspbian Debian Jessie Lite on a RPi you need to perform the following:
+
$ sudo apt-get install libav-tools
+
+
+
This will get a forked version of ffmpeg called avconv, once this is installed you need to use the following in the configuration:
+
+
ffmpeg:
+ ffmpeg_bin: /usr/bin/avconv
+
+
+
Troubleshooting
In most cases, ffmpeg automatically detects all needed options to read a video or audio stream or file. But it is possible in rare cases that you will need to set options to help ffmpeg out.
To enable the history option in your installation, add the following to your configuration.yaml file:
-
# Example configuration.yaml entry
+
# Basic configuration.yaml entryhistory:
@@ -108,6 +108,70 @@
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser. No data is transferred to anyone at any time.
+
Configuration variables:
+
+
+
exclude (Optional): Configure which components should not be displayed.
+
+
entities (Optional): The list of entity ids to be excluded from the history.
+
domains (Optional): The list of domains to be excluded from the history.
+
+
+
include (Optional): Configure which components should be displayed.
+
+
entities (Optional): The list of entity ids to be included from the history.
+
domains (Optional): The list of domains to be included from the history.
+
+
+
+
+
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 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.
+
# Example configuration.yaml entry with include
+history:
+include:
+ domains:
+ -sensor
+ -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 includeentities 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
diff --git a/components/http/index.html b/components/http/index.html
index 5e972c71b3..779d8ef770 100644
--- a/components/http/index.html
+++ b/components/http/index.html
@@ -111,7 +111,7 @@ It’s HIGHLY recommended that you set the api_p
ssl_certificate (Optional): Path to your TLS/SSL certificate to serve Home Assistant over a secure connection.
ssl_key (Optional): Path to your TLS/SSL key to serve Home Assistant over a secure connection.
cors_allowed_origins (Optional): A list of origin domain names to allow CORS requests from. Enabling this will set the Access-Control-Allow-Origin header to the Origin header if it is found in the list, and the Access-Control-Allow-Headers header to Origin, Accept, X-Requested-With, Content-type, X-HA-access. You must provide the exact Origin, i.e. https://home-assistant.io will allow requests from https://home-assistant.io but nothttp://home-assistant.io.
-
approved_ips (Optional): A list of approved ips. Then it will be possible to login from given ips without providing a password.
+
trusted_networks (Optional): List of trusted networks, consisting of IP addresses or networks, that are allowed to bypass password protection when accessing Home Assistant.
The sample below shows a configuration entry with possible values:
@@ -125,9 +125,11 @@ It’s HIGHLY recommended that you set the api_p
cors_allowed_origins:-https://google.com-https://home-assistant.io
- approved_ips:
+ trusted_networks:-127.0.0.1
- -192.168.1.9
+ -::1
+ -192.168.0.0/24
+ -2001:DB8:ABCD::/48
diff --git a/components/ifttt.manything/index.html b/components/ifttt.manything/index.html
index 2e3132ce91..e7c78a22a5 100644
--- a/components/ifttt.manything/index.html
+++ b/components/ifttt.manything/index.html
@@ -219,9 +219,18 @@ For ManyThing support, you need to set up an on<
diff --git a/components/index.html b/components/index.html
index 2d0b9a5630..030187b5fe 100644
--- a/components/index.html
+++ b/components/index.html
@@ -103,7 +103,7 @@ Support for these components is provided by the Home Assistant community.
If you do not have this version or you are running in a virtual environment, then your system will completely freeze with this component active. You will need to build python3-lirc from source. The version of this library in the Python package index is also broken, so the typical dependency system cannot fix this. Build it from source like this:
-
-
As regular user:
-
-
sudo apt-get install liblircclient-dev
-
-
-
-
As the user that runs hass:
-
-
(hass)$ git clone https://github.com/tompreston/python-lirc.git
-(hass)$ cd python-lirc
-(hass)$ make py3
-(hass)$ python3 setup.py build
-(hass)$ python3 setup.py install
-
-
-
-
If you are not using a virtual environment setup, then you’ll need a sudo before the install line above.
-
If you are configuring on a Raspberry Pi, there are excellent instructions with GPIO schematics and driver configurations here. Consider following these.
exclude (Optional): Configure which components should not create logbook enties.
-
entities (Optional): The list of entity ids to be excluded from creating logbook entries.
-
domains (Optional): The list of domains to be excluded from creating logbook entries.
+
exclude (Optional): Configure which components should not create logbook entries.
+
+
entities (Optional): The list of entity ids to be excluded from creating logbook entries.
+
domains (Optional): The list of domains to be excluded from creating logbook entries.
+
+
+
include (Optional): Configure which components should create logbook entries.
+
+
entities (Optional): The list of entity ids to be included from creating logbook entries.
+
domains (Optional): The list of domains to be included from creating logbook entries.
+
+
If you want to exclude messages of some entities or domains from the logbook just add the exclude parameter like:
-
logbook:
+
# Example of excluding domains and entities from the logbook
+logbook:exclude:entities:-sensor.last_boot
@@ -119,6 +129,34 @@
+
In case you just want to see messages from some specific entities or domains use the include configuration:
+
+
# Example to show how to include only the listed domains and entities in the logbook
+logbook:
+ include:
+ domains:
+ -sensor
+ -switch
+ -media_player
+
+
+
+
You can also use the include list and filter out some entities or domains with an exclude list. Usually this makes sense if you define domains on the include side and filter out some specific entities.
+
+
# Example of combining include and exclude configurations
+logbook:
+ include:
+ domains:
+ -sensor
+ -switch
+ -media_player
+ exclude:
+ entities:
+ -sensor.last_boot
+ -sensor.date
+
+
+
Exclude Events
Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the sensor.dateto show the current date in the UI, but you do not want an logbook entry for that sensor every day.
@@ -167,6 +205,9 @@ To exclude these entities just add them to the e
Not specifying the host variable will result in automatically searching your network for Yamaha Receivers. It will add a media player device for each one.
+
Not specifying the host variable will result in automatically searching your network for Yamaha Receivers. It will add a media player device for each one.
+
For receivers that support more than one zone, Home Assistant will add one media player per zone supported by the player, named “$name Zone 2” and “$name Zone 3”.
In some cases, autodiscovery fails due to a known bug in the receiver’s firmware. It is possible to manually specify the reveiver’s IP address or via it’s hostname (if it is discoverably by your DNS) then.
Please note: If adding the IP address or hostname manually, you must enable network standby on your receiver, or else startup of Home Assistant will hang if you have your receiver switched off.
Currently, this component supports powering on/off, mute, volume control and source selection.
The netatmo component platform is the main component to integrate all Netatmo related platforms. Besides this component you will have to setup any connected sensors separately.
+
The netatmo component platform is the main component to integrate all Netatmo related platforms.
To enable the Netatmo component, add the following lines to your configuration.yaml:
@@ -109,6 +109,7 @@
secret_key (Required): Your netatmo secret key
username (Required): Username for the netatmo account.
password (Required): Password for the netatmo account.
+
discovery (Optional): Whether to discover Netatmo devices. Set it to False, if you want to choose which Netatmo device you want to add (default True).
Get API and Secret Key
@@ -132,7 +133,7 @@ Click on ‘Create an App’ at the top of the page.
-The Home Assistant NetAtmo platform has only be tested with the classic indoor, outdoor module and rainmeter. There is no support for the windmeter module at this time because developers does not own these modules.
+The Home Assistant Netatmo platform has only be tested with the classic indoor, outdoor module and rainmeter. There is no support for the windmeter module at this time because developers does not own these modules.
@@ -157,6 +158,9 @@ The Home Assistant NetAtmo platform has only be tested with the classic indoor,
The apns platform uses the Apple Push Notification service (APNS) to deliver notifications from Home Assistant.
+
+
To use the APNS service you will need an Apple developer account and you will need to create an App to receive push notifications. For more information see the apple developer documentation.
name (Required): The name of the notifier. The notifier will bind to the service notify.NOTIFIER_NAME.
+
sandbox (Optional): If true notifications will be sent to the sandbox (test) notification service. Default false.
+
cert_file (Required): The certificate to use to authenticate with the APNS service.
+
+
+
The APNS platform will register two services, notify.NOTIFIER_NAME and apns.NOTIFIER_NAME.
+
+
apns.NOTIFIER_NAME
+
+
This service will register device id’s with home assistant. In order to receive a notification a device must be registered. The app on the device can use this service to send an ID to Home Assistant during startup, the ID will be stored in [NOTIFIER_NAME]_apns.yaml.
+
+
See didRegisterForRemoteNotificationsWithDeviceToken in the Apple developer documentation for more information about how to obtain a device id.
+
+
notify.NOTIFIER_NAME
+
+
This service will send messages to a registered device. The following parameters can be used:
+
+
+
+
message: The message to send
+
+
+
target: The desired state of the device, only devices that match the state will receive messages. To enable state tracking a registered device must have a tracking_device_id attribute added to the [NOTIFIER_NAME]_apns.yaml file. If this ID matches a device in known_devices.yaml the device state will be tracked.
+
+
+
data:
+
+
badge: The number to display as the badge of the app ic.
+
sound: The name of a sound file in the app bundle or in the Library/Sounds folder.
+
category: Provide this key with a string value that represents the identifier property of the UIMutableUserNotificationCategory.
+
content_available: Provide this key with a value of 1 to indicate that new content is available.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/notify.aws_lambda/index.html b/components/notify.aws_lambda/index.html
index 9b5274bf42..0726a7ae6c 100644
--- a/components/notify.aws_lambda/index.html
+++ b/components/notify.aws_lambda/index.html
@@ -179,6 +179,9 @@
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index ab25737374..c8b5be3021 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -147,6 +147,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
homeserver (Required): The base URL of the homeserver, where the notifier account is registered (e.g. https://matrix.org).
+
username (Required): The username of the notifying Matrix account.
+
password (Required): The password for the given Matrix account.
+
default_room (Required): The room all messages will be sent to, when no other target is given.
+
verify_ssl (Optional): Verify the homeservers certificate. Defaults to true.
+
+
+
The target room has to be precreated, the room id can be obtained from the rooms settings dialog. Rooms by default have a canonical id of the form !<randomid>:homeserver.tld, but can also be allocated aliases like #roomname:homeserver.tld. The notifying account may need to be invited to the room, depending on the individual rooms policies.
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index 7ca8fb1352..7cd970d77c 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -192,6 +192,9 @@ which need special attention. By default, the usage by external applications, es
The telstra notification platform allows you to deliver Home Assistant notifications to Australian phone numbers over the Telstra SMS API.
+
+
To enable the Telstra notifications in your installation, you must first create an account and API app over at dev.telstra.com. The free tier allows for 1000 notifications to be sent per month.
+
+
After your API app is approved, add the following to your configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
consumer_key (Required): The consumer key of your Telstra API app.
+
consumer_secret (Required): The consumer secret of your Telstra API app.
+
phone_number (Required): The phone number of where the notifications will be sent.
zone (Optional): The zone to which this component is measuring the distance to. Default is the home zone.
ignored_zones array (Optional): Where proximity is not calculated for a device (either the device being monitored or ones being compared (e.g. work or school).
-
devices array (Optional): A list of devices to compare location against to check closeness to the configured zone.
+
devices array (Optional): A list of devices to compare location against to check closeness to the configured zone.
tolerance (Optional): The tolerance used to calculate the direction of travel in meters (m) to filter out small GPS coordinate changes.
unit_of_measurement (Optional): The unit of measurement for distance. Valid values are (km, m, mi, ft) [kilometers, meters, miles and feet respectfully]. The default value is kilometers.
The arwn sensor platform is a client for the Ambient Radio Weather Network project. This collects weather station data and makes it available in an MQTT subtree.
+
+
To use your ARWN setup, you must already have configured the MQTT platform. Then add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+sensor:
+ platform:arwn
+
+
+
+
Currently all temperature, barometer, and wind sensors will be displayed. Support for rain guage sensors will happen in the future.
The bbox platform uses the Bbox Modem Router from the French Internet provider Bouygues Telecom. Sensors are mainly bandwidth measures.
+
+
+Due to third party limitation, the sensors will only be available if Home Assistant and the Bbox are on the same local area network. You can check this by going to 192.168.1.254 with your web browser.
+
+
+
To add Bbox sensors to your installation, add the following to your configuration.yaml file:
The haveibeenpwned sensor platform creates sensors that check for breached email accounts on haveibeenpwned.
+To enable this sensor, add the following lines to your configuration.yaml, it will list every specified email address as a sensor showing
+the number of breaches on that email account:
+
+
# Example configuration.yaml entry using cloud based emoncms
+sensor:
+ platform:haveibeenpwned
+ email:
+ -your_email1@domain.com
+ -your_email2@domain.com
+
+
+
+
Breach meta data
+
+
If one of your email accounts is breached the sensor will display breach meta data. It will list the title of the site where your email
+account has been breached as well as the added date of the breach data. This data is displayed in descending order so that the state attribute
+breach 1 will always contain the last known breach for the specific email account, if there are any breaches detected.
+
+
+
+
+
+
Configuration variables
+
+
+
email (Required): List of email addresses.
+
+
+
+ The sensor will scan all email addresses specified with a 5 second delay between all breach data requests on Home Assistant startup.
+ After this initial startup scanning, the sensor will only scan one email account per 15 minutes to prevent abuse, and not hammer “the
+ Have I been Pwned” service, as this breach data almost never changes.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.homematic/index.html b/components/sensor.homematic/index.html
index 174cb63f0a..367a20656c 100644
--- a/components/sensor.homematic/index.html
+++ b/components/sensor.homematic/index.html
@@ -147,6 +147,12 @@
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index 8a873894cc..6cc3a3d65e 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -170,6 +170,12 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
The min_max sensor platform is consuming the state from other sensors and determine the minimum, maximum, and the mean of the collected states. The sensor will always show you the highest/lowest value which was received from your all monitored sensors. If you have spikes in your values, it’s recommanded filter/equalize your values with a statistics sensor first.
+
+
It’s an alternative to the template sensor’s value_template: to get the average of multiple sensors.
diff --git a/components/sensor.moldindicator/index.html b/components/sensor.moldindicator/index.html
index 8be751df79..ef0850856c 100644
--- a/components/sensor.moldindicator/index.html
+++ b/components/sensor.moldindicator/index.html
@@ -150,6 +150,12 @@ With the three measured temperatures (in Celsius or Fahrenheit), the calibration
diff --git a/components/sensor.mqtt_room/index.html b/components/sensor.mqtt_room/index.html
index a4d131c2f7..f1955be9ac 100644
--- a/components/sensor.mqtt_room/index.html
+++ b/components/sensor.mqtt_room/index.html
@@ -175,6 +175,9 @@ Instead of developing your own application, you can also use any of these alread
diff --git a/components/sensor.nest/index.html b/components/sensor.nest/index.html
index 274046c862..316859b83b 100644
--- a/components/sensor.nest/index.html
+++ b/components/sensor.nest/index.html
@@ -181,6 +181,12 @@ You must have the Nest component configured to u
diff --git a/components/sensor.octoprint/index.html b/components/sensor.octoprint/index.html
index cdf45d6954..bc90930123 100644
--- a/components/sensor.octoprint/index.html
+++ b/components/sensor.octoprint/index.html
@@ -157,6 +157,12 @@ You must have the OctoPrint component confi
This pilight sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. uuid) can be set to distinguish between multile pilight devices. To use a pilight sensor the pilight home assistant hub has to be set up.
+
+
To use your sensor via pilight, make sure it is supported and add the following to your configuration.yaml file:
diff --git a/components/sensor.rfxtrx/index.html b/components/sensor.rfxtrx/index.html
index f1f5bf17c0..07e8266b10 100644
--- a/components/sensor.rfxtrx/index.html
+++ b/components/sensor.rfxtrx/index.html
@@ -202,6 +202,12 @@ Then you should update your configuration to:
The scrape sensor platform is scraping information from websites. The sensor loads a HTML page and gives you the option to search and split out a value. As this is not a full-blown web scraper like scrapy. It will most likely only works with simple webpage and it can be time-consuming to get the right section.
+
+
To enable this sensor, add the following lines to your configuration.yaml file:
resource (Required): The URL to the website that contains the value.
+
select (Required): Defines the HTML tag to search for. Check Beautifulsoup’s CSS selectors for details.
+
name (Optional): Name of the sensor.
+
unit_of_measurement (Optional): Defines the units of measurement of the sensor, if any.
+
+
+
Examples
+
+
In this section you find some real life examples of how to use this sensor. There is also a Jupyter notebook available for this example to give you a bit more insight.
If you make heavy use of the IFTTT web service for your automations and are curious about the status of IFTTT then you can display the current state of IFTTT in your frontend.
+
+
sensor:
+# Example configuration.yaml entry
+ -platform:scrape
+ resource:http://status.ifttt.com/
+ name:IFTTT status
+ select:'.component-status'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.sleepiq/index.html b/components/sensor.sleepiq/index.html
index 6cdf702bfb..80ed40d1c5 100644
--- a/components/sensor.sleepiq/index.html
+++ b/components/sensor.sleepiq/index.html
@@ -130,6 +130,12 @@
diff --git a/components/sensor.temper/index.html b/components/sensor.temper/index.html
index e39897464f..c4e0bbcd82 100644
--- a/components/sensor.temper/index.html
+++ b/components/sensor.temper/index.html
@@ -139,6 +139,12 @@ The calculation follows the formula scale * sens
diff --git a/components/sensor.template/index.html b/components/sensor.template/index.html
index c69dd83fcf..504a104289 100644
--- a/components/sensor.template/index.html
+++ b/components/sensor.template/index.html
@@ -256,6 +256,12 @@ Please note the blank line to close the multi-line template.
name (Required): The name you would like to give the sensor in Home Assistant.
type (Required): Set to analog or temperature.
-
pin (Required): The number identifying which pin to sample
+
pin (Optional): The number identifying which pin to sample.
address (Optional): The long 64 bit address of the remote ZigBee device whose pin you would like to sample. Do not include this variable if you want to sample the local ZigBee device’s pins.
-
max_volts (Optional): The maximum voltage which the input pin is able to read. Defaults to 1.2
+
max_volts (Optional): The maximum voltage which the input pin is able to read. Defaults to 1.2.
The ZoneMinder sensor platform let you monitor the current state of your zoneminder install including the number of events and the current state of the cameras.
pins (Required): Array of pins to use. The number corresponds with the pin numbering schema of your board.
+
pins array (Required): List of pins to use.
-
name: Name that will be used in the frontend for the pin.
-
type: The type of the pin. At the moment only ‘digital’ is supported.
-
default: The initial value for this port.
-
negate: If this pin should be inverted.
+
[number] (Required): The pin number that corresponds with the pin numbering schema of your board.
+
+
name (Required): Name that will be used in the frontend for the pin.
+
initial (Optional): The initial value for this port. Defaults to False .
+
negate (Optional): If this pin should be inverted. Defaults to False.
+
+
-
The digital pins are numbered from 0 to 13. The available pins are 2 till 13. For testing purposes you can use pin 13 because with that pin you can control the internal LED.
+
The digital pins are numbered from 0 to 13 on a Arduino UNO. The available pins are 2 till 13. For testing purposes you can use pin 13 because with that pin you can control the internal LED.
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index 8ba226ecfd..306a88b783 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -285,6 +285,9 @@ This switch will shutdown your host immediately, there will be no confirmation.
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index 0010e0c058..e5496c9391 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -182,6 +182,9 @@ Currently works using default https port only.
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 1b7fc4fa07..2673ceaff4 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -264,6 +264,9 @@ Make sure that your topic match exact. some-topi
This will automatically add a switch for each Botvac Connected that you have. The switch will start a full home cleaning when turned ON and return the robot to base when turned OFF.
+
+
To enable this switch in your installation, add the following to your configuration.yaml file:
username (Required): Username for the Neato account.
+
password (Required): Password for the Neato account.
+
+
+
+The Home Assistant Neato platform has only be tested with a Botvac Connected. There is no support for the Botvac D3 Connected and Botvac D5 Connected robots at this time.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/switch.netio/index.html b/components/switch.netio/index.html
index 052f8e4371..db830eabf1 100644
--- a/components/switch.netio/index.html
+++ b/components/switch.netio/index.html
@@ -216,6 +216,9 @@
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 838638d0c7..b4e76991c7 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -193,6 +193,9 @@ This component relies on raw TCP commands to PulseAudio. In order for PulseAudio
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index 6f59b1d22d..532cffda75 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -196,6 +196,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/switch.rfxtrx/index.html b/components/switch.rfxtrx/index.html
index 75eb741f48..2bcc8d5d60 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -235,6 +235,9 @@ Then you should update your configuration to:
diff --git a/components/switch.rpi_rf/index.html b/components/switch.rpi_rf/index.html
index f345d6740a..37561737ec 100644
--- a/components/switch.rpi_rf/index.html
+++ b/components/switch.rpi_rf/index.html
@@ -202,6 +202,9 @@ For more info see the PyPi module description: ZigBee Switch
+
diff --git a/components/switch.wake_on_lan/index.html b/components/switch.wake_on_lan/index.html
index e5275951f5..7c28f5aee8 100644
--- a/components/switch.wake_on_lan/index.html
+++ b/components/switch.wake_on_lan/index.html
@@ -181,6 +181,9 @@ The WOL switch can only turn on your computer and monitor the state. There is no
The updater component will check for new releases at startup and everyday at noon and midnight. It will show a badge in the frontend if a new version has been detected.
+
The updater component will check daily for new releases. It will show a badge in the frontend if a new version was found.
+
+
The updater component will also collect basic information about Home Assistant and its environment. The information includes the current Home Assistant version, the timezone, Python version and operating system infomation. No identifiable information (i.e. IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python source code.
To integrate this into Home Assistant, add the following section to your configuration.yaml file:
-
# Example configuration.yaml entry
-updater:
+
updater:
+
If you choose not to share any information when checking for updates, you can add reporting: False.
+
+
Notification
+
For an added bonus, an automation component can be created to send a message with a notifier when that state of this component’s entity changes.
# Example configuration.yaml entry
@@ -114,6 +119,7 @@
Home Control is responsible for collecting information and controlling devices.
-
Home Automation triggers commands based on user configurations.
-
Smart Home triggers commands based on previous behavior.
+
Home Automation triggers command based on user configurations.
+
Smart Home triggers commands based on previous behaviour.
diff --git a/developers/component_discovery/index.html b/developers/component_discovery/index.html
index 5da6595c18..2a4245b6e6 100644
--- a/developers/component_discovery/index.html
+++ b/developers/component_discovery/index.html
@@ -99,7 +99,7 @@ This option is only available for built-in components.
Device discovery for Home Assistant has been extracted into an external library called NetDisco. This library is integrated using the discovery component and scans the network in intervals for uPnP and zeroconf/mDNS services.
By default logging in home-assistant is tuned for operating in
+production (set to INFO by default, with some modules set to even less
+verbose logging levels).
+
+
You can use the logger component to adjust
+logging to DEBUG to see even more details about what is going on.
+
Developing on Windows
If you are using Windows as a development platform, make sure that you have the correct Microsoft Visual C++ build tools installed. Check the Windows Compilers section on the Python website for details. Validation using tox will fail if this is not done correctly.
The configuration.yaml file contains the configuration options for components and platforms. We use voluptuous to make sure that the configuration provided by the user is valid. Some entries are optional or could be required to set up a platform or a component. Others must be a defined type or from an already-defined list.
-
We test the configuration to ensure that users have a great experience and minimize notifications if something is wrong with a platform or component setup before Home Assistant runs.
+
We test the configuration to ensure that users have a great experience and minimise notifications if something is wrong with a platform or component setup before Home Assistant runs.
Besides voluptuous default types, many custom types are available. For an overview, take a look at the config_validation.py helper.
Home Assistant uses Polymer for the UI and NuclearJS for maintaing the app state.
+
Home Assistant uses Polymer for the UI and NuclearJS for maintaining the app state.
Polymer allows building encapsulated custom HTML elements.
@@ -111,7 +111,7 @@ Do not use development mode in production. Home Assistant uses aggressive cachin
-
As everything is compiled into the file frontend.html you do not want to work with the compiled version but with the seperate files during development.
+
As everything is compiled into the file frontend.html you do not want to work with the compiled version but with the separate files during development.
Next step is to get the frontend code. When you clone the Home Assistant repository, the frontend repository is not cloned by default. You can setup the frontend development environment by running:
Home Assistant supports running multiple synchronized instances using a master-slave model. Whenever events.fire or states.set is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.
+
Home Assistant supports running multiple synchronised instances using a master-slave model. Whenever events.fire or states.set is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.
Create a pull request from dev to master with the upcoming release number as title.
-
Merge master into dev to make the PR mergable. PR message contains intro, highlighting major changes, and an overview of all changes tagging each author.
-
Update homeassistant/const.py with the correct version number (remove the the dev tag) and push that commit.
+
Create a pull request from dev to master with the upcoming release number as the title.
+
Merge master into dev to make the PR mergeable. PR message contains intro, highlighting major changes, and an overview of all changes tagging each author.
+
Update homeassistant/const.py with the correct version number (remove the dev tag) and push that commit.
Merge pull request (DO NOT SQUASH!).
-
Then, after merged, push another update to dev of homeassistant/const.py that includes the next version with the dev tag. Add a meaningful commit message like “Version bump to X”. This commit acts as marker for the next release.
+
Then, after merged, push another update to dev of homeassistant/const.py that includes the next version with the dev tag. Add a meaningful commit message like “Version bump to X”. This commit acts as a marker for the next release.
Go to releases and tag a new release on the master branch. “Tag version” and “Release title” are the version number (O.x for major version, 0.x.y for minor and bug fix releases). Release description is the text from PR. Press “Publish release” to finish the process.
Website
-
Create a blog post in next and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in message to documentation.
+
Create a blog post in next and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in a message to documentation.
Create missing documentation as stumbs in next.
Update the link on the frontpage (source/index.html) to link to the new release blog post and version number.
-
Create a pull request from next to current with the upcoming release number as title.
-
Merge current into next ($ git checkout next && git merge current) to make the PR mergable.
+
Create a pull request from next to current with the upcoming release number as the title.
+
Merge current into next ($ git checkout next && git merge current) to make the PR mergeable.
Merge pull request (blog post, updated frontpage, and all new documentation) to current.
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index abacb4023d..27f2a21c1c 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -417,7 +417,7 @@ You can append ?api_password=YOUR_PASSWORD
-
Return code is 200 if the entity existed, 201 if the state of a new entity was set. A location header will be returned with the url of the new resource. The response body will contain a JSON encoded State object.
+
The return code is 200 if the entity existed, 201 if the state of a new entity was set. A location header will be returned with the URL of the new resource. The response body will contain a JSON encoded State object.
The simplest script to consume the SSE in Python looks like this:
+
«««< HEAD
+The simplest script to consume the SSE looks like the following snippet.
+=======
+The simplest script to consume the SSE in Python looks like this:
Create/edit/update a page in the directory source/_components/ for your platform/component.
Test your changes to home-assistant.io locally: run rake preview and navigate to http://127.0.0.1:4000
-
Create a Pull Request (PR) against the next branch of home-assistant.github.io if your documentation is for a new feature, platform, or component.
+
Create a Pull Request (PR) against the next branch of home-assistant.github.io if your documentation is a new feature, platform, or component.
Create a Pull Request (PR) against the current branch of home-assistant.github.io if you fix stuff, create Cookbook entries, or expand existing documentation.
@@ -123,7 +123,7 @@ It could be necessary that you run rake generate
For a platform page, the fastest way is to make a copy of an existing page and edit it. The Component overview and the Examples section are generated automatically, so there is no need to add a link to those pages.
-
If you start from scratch with a page, you need to add a header. Different sections of the doumentation may need different headers.
+
If you start from scratch with a page, you need to add a header. Different sections of the documentation may need different headers.
---
layout: page
@@ -143,11 +143,11 @@ Content...Written in markdown.
-
There are pre-definied variables available but usually it’s not necessary to use them when writing documentation.
+
There are pre-definied variables available but usually, it’s not necessary to use them when writing documentation.
Embedding Code
-
You can use the default markdown syntax to generate syntax highlighted code. For inline code wrap your code in `. For multi line syntax wrap your code as shown below.
+
You can use the default markdown syntax to generate syntax highlighted code. For inline code wrap your code in `. For multi-line, syntax wrap your code as shown below.
```yaml
sensor:
diff --git a/getting-started/z-wave-device-specific/index.html b/getting-started/z-wave-device-specific/index.html
index aa4261aa15..0d24810dbb 100644
--- a/getting-started/z-wave-device-specific/index.html
+++ b/getting-started/z-wave-device-specific/index.html
@@ -98,12 +98,12 @@ These devices will either show as a binary sensor or a sensor called The following parameters can be entered:
-
entity_id (Required): The entity_id of the device that you are going to set a parameter to. Any entity_id of the node can be used.
+
node_id (Required): The node_id of the device that you are going to set a parameter to.
parameter (Required): The index number of the parameter to be set. Refer to device manual or zwcfg_[home_id].xml
value (Required): The value to set the parameter to. Refer to device manual or zwcfg_[home_id].xml
size (Optional): The size of the value. It is normally not needed to specify this parameter, but in some cases it’s needed. Check OZW.log for details on this.
-You should check OZW.log to see if setting has been set
-Example entry in dev-service, setting binary report for Aeotec multisensor 6:
+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:
# Example entry in dev-service{"entity_id":"sensor.aetoec_multisensor_6_luminance_5","parameter":"5",
@@ -116,10 +116,10 @@ Example entry in dev-service, setting binary report for Aeotec multisensor 6:
Locks and other secure devices
-
These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZwave’s options.xml which is located in OpenZWave’s directory. This should also be the same directory as config_path: in your configuration.yaml. If it’s not, make sure you have the same values in all the files you are using.
+
These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZWave’s options.xml which is located in OpenZWave’s directory. This should also be the same directory as config_path: in your configuration.yaml. If it’s not, make sure you have the same values in all the files you are using.
The option is commented out by default in options.xml and is a default key. Make your own unique key. The key is in Hexadecimals.
-It is best to pair these devices in OpenZWave Control Panel or other Z-wave tool that can show you logs while pairing. Home Assistant show logs from zwave too and it is OZW.log in the Home Assistant config directory.
-You should see communication from the node with lines starting with info: NONCES in OZW.log when the device is paired secure successfully. If you use Open Zwave Control Panel to pair, test the device before you save the configuration.
+It is best to pair these devices in OpenZWave Control Panel or another Z-Wave tool that can show you logs while pairing. Home Assistant stores logs from Z-Wave in OZW.log in the Home Assistant config directory.
+You should see communication from the node with lines starting with info: NONCES in OZW.log when the device is paired successfully with a secure connection. If you use OpenZWave Control Panel to pair, test the device before you save the configuration.
Make sure you copy the newly saved zwcfg_[home_id].xmlinto your Home Assistant configuration directory.
Aeon Minimote
diff --git a/getting-started/z-wave/index.html b/getting-started/z-wave/index.html
index 5a1ea9efd5..08c5897a88 100644
--- a/getting-started/z-wave/index.html
+++ b/getting-started/z-wave/index.html
@@ -156,7 +156,8 @@ Instead of make install, you can alternat
polling_interval (Optional): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.
customize (Optional): This attribute contains node-specific override values:
-
polling_intensity (Optional): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2-every other time, etc). If not specified then your device will not be polled.
+
polling_intensity (Optional): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2=every other time, etc). If not specified then your device will not be polled.
+
ignored (Optional): Ignore this entitiy completely. It won’t be shown in the Web Interface and no events are generated for it.
@@ -295,7 +296,7 @@ You can use this for automations.
Services
-
The zwave component exposes ten services to help maintain the network.
+
The zwave component exposes multiple services to help maintain the network.
@@ -313,6 +314,10 @@ You can use this for automations.
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
+
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.
diff --git a/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png b/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png
new file mode 100644
index 0000000000..76293d51e5
Binary files /dev/null and b/images/blog/2016-10-flash-briefing-updater-hacktoberfest/map.png differ
diff --git a/images/blog/2016-10-flash-briefing-updater-hacktoberfest/stay-classy.jpg b/images/blog/2016-10-flash-briefing-updater-hacktoberfest/stay-classy.jpg
new file mode 100644
index 0000000000..c28298c45d
Binary files /dev/null and b/images/blog/2016-10-flash-briefing-updater-hacktoberfest/stay-classy.jpg differ
diff --git a/images/components/alexa/alexa-108x108.png b/images/components/alexa/alexa-108x108.png
new file mode 100644
index 0000000000..f1a56e1c1f
Binary files /dev/null and b/images/components/alexa/alexa-108x108.png differ
diff --git a/images/components/alexa/alexa-512x512.png b/images/components/alexa/alexa-512x512.png
new file mode 100644
index 0000000000..e48e6ead03
Binary files /dev/null and b/images/components/alexa/alexa-512x512.png differ
diff --git a/images/components/haveibeenpwned/sensor.png b/images/components/haveibeenpwned/sensor.png
new file mode 100644
index 0000000000..1fd4f7598a
Binary files /dev/null and b/images/components/haveibeenpwned/sensor.png differ
diff --git a/images/screenshots/interlogix.png b/images/screenshots/interlogix.png
new file mode 100644
index 0000000000..e8abf587bd
Binary files /dev/null and b/images/screenshots/interlogix.png differ
diff --git a/images/supported_brands/bbox.png b/images/supported_brands/bbox.png
new file mode 100644
index 0000000000..b596213f12
Binary files /dev/null and b/images/supported_brands/bbox.png differ
diff --git a/images/supported_brands/haveibeenpwned.png b/images/supported_brands/haveibeenpwned.png
new file mode 100644
index 0000000000..6848ed88fe
Binary files /dev/null and b/images/supported_brands/haveibeenpwned.png differ
diff --git a/images/supported_brands/matrix.png b/images/supported_brands/matrix.png
new file mode 100644
index 0000000000..807049fd07
Binary files /dev/null and b/images/supported_brands/matrix.png differ
diff --git a/images/supported_brands/neato.png b/images/supported_brands/neato.png
new file mode 100644
index 0000000000..33272d0b0f
Binary files /dev/null and b/images/supported_brands/neato.png differ
diff --git a/images/supported_brands/synology.png b/images/supported_brands/synology.png
new file mode 100644
index 0000000000..25fd9f3b05
Binary files /dev/null and b/images/supported_brands/synology.png differ
diff --git a/images/supported_brands/telstra.png b/images/supported_brands/telstra.png
new file mode 100644
index 0000000000..c86d95af6b
Binary files /dev/null and b/images/supported_brands/telstra.png differ
diff --git a/images/supported_brands/zoneminder.png b/images/supported_brands/zoneminder.png
new file mode 100644
index 0000000000..0fefee6798
Binary files /dev/null and b/images/supported_brands/zoneminder.png differ
diff --git a/index.html b/index.html
index 1c709c8753..7664c5d294 100644
--- a/index.html
+++ b/index.html
@@ -115,11 +115,11 @@ Home Assistant is an open-source home automation platform running on Python 3. T
Home Assistant is built from many small building blocks that together offer a powerful and customizable system. This page is a collection of the more advanced topics.
Starting with 0.31 the updater component sends an optional report about Home Assistant instance.
+
+
We are only collecting this information to better understand our user base to provide better long term support and feature development.
+
+
+
+
+
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
+
+
+
+
+
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 showed 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 lookups are very hit or miss).
+
+
The server also adds two timestamps to the data:
+
+
+
the original date your instance UUID was first seen
+
the timestamp of the last time we have seen your instance
+
+
+
There are currently 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.
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like 
- The “Cranberry cam” in action
-
+ 
-
-- Core: Introduce notion of unit system (deprecates temperature unit option) ([@Teagan42])
-- Front end: Speed improvements ([@balloob])
-- Front end: Improve layout of state dev tool ([@balloob])
-- [Proximity]\: Allow definition of unit of measurement ([@Teagan42])
-- [Flux]\: Add mired and kelvin mode ([@HBDK])
-- Thermostat - [Proliphix]: Support for cooling ([@sdague])
-- Media Player - [LG Netcast TV]: Show screenshot of what is currently playing ([@shmuelzon])
-- Z-Wave improvements ([@jnewland], [@turbokongen])
-- Thermostat - [heat control]: now also able to control an AC ([@mtreinish])
-- Thermostat - [heat control]: allow specifying a minimum duration before switching ([@mtreinish])
-- [InfluxDB]\: Whitelist entities option added ([@tchellomello])
-- Sensor: Serial [particulate matters][particulate] sensors now supported ([@open-homeautomation])
-- Sensor - [Fitbit]: Fix unit system ([@tchellomello])
-- Light - [Flux LED]: Add support for [color and brightness][color] ([@Danielhiversen])
-- Media Player - [Plex]: Now able to report on music ([@abcminiuser])
-- Alarm Control Panel - [Verisure]: Now able to see who changed the alarm ([@persandtrom])
-- Thermostat - [Honeywell]: Add option to read and control HVAC mode ([@Teagan42])
-- [Foursquare] component to receive instant notifications of checkins ([@robbiet480])
-- Camera: New [FFMPEG] platform allows to stream anything through front end ([@pvizeli])
-- Manage [secrets] with new command line script ([@kellerza])
-- Notify - [SMTP]: Allow embedding of images ([@partofthething])
-- Sensor: [OhmConnect] is now supported ([@robbiet480])
-- [panel_custom] component allows the registering of new panels ([@balloob])
-- Light: New [mqtt_json] platform for working with JSON payload ([@corbanmailloux])
-- Sensor: New [Fast.com] platform to measure network bandwidth performance ([@nkgilley])
-- New [pilight] component to control 433 Mz devices ([@DavidLP])
-- Sensor: [GPSD] now supported ([@fabaff])
-
-### 
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like 
-Picture of the final setup (+ 2 LED for decoration)
-
-Home Assistant will keep track of historical values and allow you to integrate it into automation.
-
The big new addition in this release is the support for the MQTT protocol by 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
