- 2016-04-20T11:27:04+00:00
+ 2016-04-21T01:52:29+00:00https://home-assistant.io/
@@ -13,6 +13,57 @@
Octopress
+
+
+
+ 2016-04-20T06:10:00+00:00
+ https://home-assistant.io/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas
+ Itβs time for 0.18. This release cycle is 2 days shorter than usual as Iβll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
+
+
Since the last release we have moved all Home Assistant source code etc into itβs own organisation on GitHub. Weβre growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Media player: Plex will now monitor the server and add clients as they pop up (@infamy)
+
Core: We now use iso8601 for datetimes (@balloob).
+
Media Player: MPD now supports service to play playlists (@Cinntax)
+
Z-Wave should be a little bit more stable (@Turbokongen)
+
Media Player: Sonos will now only add visible devices (@jpmossin)
+
Light: Wink will now allow controlling the colors (@bradsk88)
+
+
+
Breaking changes
+
+
We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
+
The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
+
MySensors received two big changes that will cause you to update your configs. See component page for new example config.
+
+
All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
+
The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
I will no longer suggest people to buy into the Philips Hue ecosystem.
-]]>
-
-
-
-
-
- 2015-12-10T10:39:41+00:00
- https://home-assistant.io/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches
-
-In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either βOnβ or βOffβ.
-
-
You could also do this with the automation component instead so whenever you put your house to sleep mode for example your Android device will open up Google Play Books or the Kindle app ready for you to read as well as dimming your lights, but this tutorial is all about the switches.
-
-
-
-
AutoRemote URL
-
-
First things first you should install Tasker and AutoRemote onto your Android device and launch AutoRemote. You should see a URL above the QR code, visit it in your browser and it should bring up a page a bit like this.
-
-
-
-
-
-
Now type in SayOn in the Message box and you should see a box appear on the right with a URL in it, this is what we will be using in the Python script later on so save that for later. Do the same thing again but this time replace SayOn with SayOff. Now just click the Send message now! button to test that your commands will get sent to your Android device, if they do you will see a toast message at the bottom of your screen like this one.
-
-
-
-
-
-
Tasker Setup
-
-
Open up Tasker and make sure youβre in the PROFILES tab, then select the plus icon to create a new profile. Select Event -> Plugin -> AutoRemote -> AutoRemote and then the pencil icon to configure the AutoRemote event. Select Message Filter and enter in SayOn then go back until it asks you for a task. Select New task then just leave the next field blank and select the tick icon.
-This is where weβll configure our task, so select the plus icon to select an action. Select Alert -> Say to add a Say action. Enter On in the text field and go back to test your task, make sure your media volume is up then select the play icon, you should hear your device say βOnβ.
-
-
-
-
-
-
Now you can go back to the main Tasker screen and create another profile but this time replace SayOn with SayOff and On with Off. After youβve done that go to the main screen again and select the menu button at the top then Exit and Save first to make sure everything is saved properly.
-
-
Python Script
-
-
Now itβs time to set it up the script, so create a new Python script and name it On.py then enter this code:
-
-
-
importrequests
-requests.get('[URL]')
-
-
-
-
-
Enter in your βOnβ URL then save it. Create another script but this time call it Off.py and enter your βoffβ URL instead.
-
-
Home Assistant Configuration
-
-
Add a command line switch to your Home Assistant configuration:
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 c3d48252a9..1c41f69e38 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
@@ -234,6 +234,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 9bdba402e4..d032f9af6a 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -210,6 +210,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 3d3a792de1..e361f4213a 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -186,6 +186,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 e229162c15..a59ce479df 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -225,6 +225,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 1d98b328a3..7e7e4ece8f 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -262,6 +262,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 7e8ba798a5..fddc792102 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -300,6 +300,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 d284126cfe..f346ffe50e 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -353,6 +353,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 8c74a9e2f4..ff8faa529b 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
@@ -305,6 +305,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 ad852b2d48..e554b49ca6 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
@@ -294,6 +294,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -317,12 +323,6 @@ Support for Temper temperature sensors has been contributed by
- Your hub should be local and open
-
-
-
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 9d2d9f677e..fda7183b59 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
@@ -204,6 +204,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 1ac920860d..018845fe3c 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
@@ -317,6 +317,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 1f41fff2bf..70b6385084 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
@@ -254,6 +254,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 d4ba2de161..3d7a6d05c1 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
@@ -233,6 +233,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 e02298e56d..4551aa5334 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
@@ -209,6 +209,12 @@ Map in Home Assistant showing two people and three zones (home, school, work)
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 3d45c0b401..a2e261e840 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
@@ -220,6 +220,12 @@ This makes more sense as most people run Home Assistant as a daemon
@@ -262,12 +268,6 @@ requests.get('
- Your hub should be local and open
-
-
-
diff --git a/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html b/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html
index 091846644b..2ded56adad 100644
--- a/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html
+++ b/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html
@@ -211,6 +211,12 @@ Philips Hue FAQ entries regarding 3rd party light bulbs.
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 2e09eb492f..087612ea2a 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
@@ -218,6 +218,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 5d88500f6c..3ec3f7bf2d 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -229,6 +229,12 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
Itβs time for 0.18. This release cycle is 2 days shorter than usual as Iβll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
+
+
Since the last release we have moved all Home Assistant source code etc into itβs own organisation on GitHub. Weβre growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Media player: Plex will now monitor the server and add clients as they pop up (@infamy)
+
Core: We now use iso8601 for datetimes (@balloob).
+
Media Player: MPD now supports service to play playlists (@Cinntax)
+
Z-Wave should be a little bit more stable (@Turbokongen)
+
Media Player: Sonos will now only add visible devices (@jpmossin)
+
Light: Wink will now allow controlling the colors (@bradsk88)
+
+
+
Breaking changes
+
+
We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
+
The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
+
MySensors received two big changes that will cause you to update your configs. See component page for new example config.
+
+
All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
+
The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
+
+
+
+
+
+
+
+
Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 9d33fde2bb..236f45086a 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -98,6 +98,38 @@
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 77a4f24f0b..248e9398d8 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2016-04-20T11:27:04+00:00
+ 2016-04-21T01:52:29+00:00https://home-assistant.io/
@@ -13,6 +13,57 @@
Octopress
+
+
+
+ 2016-04-20T06:10:00+00:00
+ https://home-assistant.io/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas
+ Itβs time for 0.18. This release cycle is 2 days shorter than usual as Iβll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
+
+
Since the last release we have moved all Home Assistant source code etc into itβs own organisation on GitHub. Weβre growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Media player: Plex will now monitor the server and add clients as they pop up (@infamy)
+
Core: We now use iso8601 for datetimes (@balloob).
+
Media Player: MPD now supports service to play playlists (@Cinntax)
+
Z-Wave should be a little bit more stable (@Turbokongen)
+
Media Player: Sonos will now only add visible devices (@jpmossin)
+
Light: Wink will now allow controlling the colors (@bradsk88)
+
+
+
Breaking changes
+
+
We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
+
The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
+
MySensors received two big changes that will cause you to update your configs. See component page for new example config.
+
+
All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
+
The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
+
+
+
+]]>
+
+
@@ -218,58 +269,6 @@ player state attributes. This change affects automations, scripts and scenes.The rfxtrx sensors entity ids will incur a one time change to move to a stable format. See the docs for more details.
-]]>
-
-
-
-
-
- 2016-02-13T06:15:00+00:00
- https://home-assistant.io/blog/2016/02/13/speedtest-bloomsky-splunk-and-garage-doors
- The focus of 0.13 was on test coverage, big cheers to @rmkraus for his hard work on this. Iβm proud to announce that weβve hit the 90% test coverage of the core + important components. A big milestone for the project.
-
-
Itβs time for 0.18. This release cycle is 2 days shorter than usual as Iβll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
+
+
Since the last release we have moved all Home Assistant source code etc into itβs own organisation on GitHub. Weβre growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Media player: Plex will now monitor the server and add clients as they pop up (@infamy)
+
Core: We now use iso8601 for datetimes (@balloob).
+
Media Player: MPD now supports service to play playlists (@Cinntax)
+
Z-Wave should be a little bit more stable (@Turbokongen)
+
Media Player: Sonos will now only add visible devices (@jpmossin)
+
Light: Wink will now allow controlling the colors (@bradsk88)
+
+
+
Breaking changes
+
+
We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
+
The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
+
MySensors received two big changes that will cause you to update your configs. See component page for new example config.
+
+
All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
+
The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
+
+
+
+
+
+
+
+
+
@@ -723,62 +806,6 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
-
-
-
-
Would you like to listen to music in every room in your home, controlled from one source? Then multi-room audio is for you.
-
-
Multi-room audio can be achieved by having a computer attached to speakers in every room. On each computer, services run to play and/or control the audio. With this DIY approach, the kind of computer and speakers is very much up to you. It could be your desktop computer with attached powered speakers, your HTPC hooked up to your TV and receiver, a Raspberry Pi with Amp or DAC, or even an Android device.
-
-
Youβll need two key software packages, besides Home Assistant. The first is Mopidy, a music server that can play local files, or connect to streaming music services like Spotify. The second is Snapcast, which enables synchronized audio streaming across your network. Both can be integrated into Home Assistant. Each room audio device will run an instance of the Snapcast client, and optionally a Mopidy instance. Your server will run a special instance of Mopidy and the Snapcast server.
-
-
Finally, you also need a player to control Mopidy. Any MPD-compatible player will work, and there are several Mopidy-only web-based options available. On Android, Remotedy is particularly nice since you can access multiple Mopidy instances in one place.
-
-
Home Assistant will provide device status, and volume control for each room. If you want to play music in all your rooms (on all your clients), access the server instance of Mopidy. If you want to play music only in a specific room, access that specific Mopidy instance. If youβre using a web UI for Mopidy, you can add links to each instance in Home Assistant with the weblink component.
Would you like to listen to music in every room in your home, controlled from one source? Then multi-room audio is for you.
+
+
Multi-room audio can be achieved by having a computer attached to speakers in every room. On each computer, services run to play and/or control the audio. With this DIY approach, the kind of computer and speakers is very much up to you. It could be your desktop computer with attached powered speakers, your HTPC hooked up to your TV and receiver, a Raspberry Pi with Amp or DAC, or even an Android device.
+
+
Youβll need two key software packages, besides Home Assistant. The first is Mopidy, a music server that can play local files, or connect to streaming music services like Spotify. The second is Snapcast, which enables synchronized audio streaming across your network. Both can be integrated into Home Assistant. Each room audio device will run an instance of the Snapcast client, and optionally a Mopidy instance. Your server will run a special instance of Mopidy and the Snapcast server.
+
+
Finally, you also need a player to control Mopidy. Any MPD-compatible player will work, and there are several Mopidy-only web-based options available. On Android, Remotedy is particularly nice since you can access multiple Mopidy instances in one place.
+
+
Home Assistant will provide device status, and volume control for each room. If you want to play music in all your rooms (on all your clients), access the server instance of Mopidy. If you want to play music only in a specific room, access that specific Mopidy instance. If youβre using a web UI for Mopidy, you can add links to each instance in Home Assistant with the weblink component.
-In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either βOnβ or βOffβ.
-
-
You could also do this with the automation component instead so whenever you put your house to sleep mode for example your Android device will open up Google Play Books or the Kindle app ready for you to read as well as dimming your lights, but this tutorial is all about the switches.
+In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either βOnβ or βOffβ.
+
+
You could also do this with the automation component instead so whenever you put your house to sleep mode for example your Android device will open up Google Play Books or the Kindle app ready for you to read as well as dimming your lights, but this tutorial is all about the switches.
Itβs like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
Migration note: the scheduler component has been removed in favor of the automation component.
-
-
Sonos
- Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically detect Sonos devices in your network and set them up for you. It will allow you to control music playing on your Sonos and change the volume.
-
-
iTunes and airplay speakers
-@maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run itunes-api on your Mac as middleware.
Itβs like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
Migration note: the scheduler component has been removed in favor of the automation component.
+
+
Sonos
+ Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically detect Sonos devices in your network and set them up for you. It will allow you to control music playing on your Sonos and change the volume.
+
+
iTunes and airplay speakers
+@maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run itunes-api on your Mac as middleware.
Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.
-
-
This release includes a significant startup boost for the frontend and a fix for Wemo discovery after their latest firmware upgrade.
-
-
I would like to give a big shout out to our newest contributor fabaff for taking the time to improve the documentation.
-
-
-To update to the latest version, run scripts/update. Please report any issues on GitHub.
-
Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.
+
+
This release includes a significant startup boost for the frontend and a fix for Wemo discovery after their latest firmware upgrade.
+
+
I would like to give a big shout out to our newest contributor fabaff for taking the time to improve the documentation.
+
+
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
+
+
+
+
@@ -646,64 +698,6 @@ Home Assistant should now throw better errors and offer solutions if you do not
Home Assistant now supports --open-ui and --demo-mode command line properties to open the browser automatically and have something to show. Home Assistant now supports to be run without a password, allowing the interface to login automatically on launch.
-
For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as weβre expanding the supported devices. Today, weβre proud to introduce Nest Thermostat integration for Home Assistant contributed by Stefano Fiorini!
-
-
-
-
-
-
The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package python-nest by jkoelker to talk to the Nest.
-
-
If you own a Nest thermostat, add the following lines to your home-assistant.conf:
For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as weβre expanding the supported devices. Today, weβre proud to introduce Nest Thermostat integration for Home Assistant contributed by Stefano Fiorini!
+
+
+
+
+
+
The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package python-nest by jkoelker to talk to the Nest.
+
+
If you own a Nest thermostat, add the following lines to your home-assistant.conf:
diff --git a/components/binary_sensor.rpi_gpio/index.html b/components/binary_sensor.rpi_gpio/index.html
index 7d70c99a71..5acfc89de5 100644
--- a/components/binary_sensor.rpi_gpio/index.html
+++ b/components/binary_sensor.rpi_gpio/index.html
@@ -262,6 +262,9 @@ To avoid having to run Home Assistant as root when using this component, run a R
diff --git a/components/device_tracker.actiontec/index.html b/components/device_tracker.actiontec/index.html
index 5a75f6d54e..f37f4e8851 100644
--- a/components/device_tracker.actiontec/index.html
+++ b/components/device_tracker.actiontec/index.html
@@ -157,6 +157,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 0b52d92493..ef594d0339 100644
--- a/components/device_tracker.aruba/index.html
+++ b/components/device_tracker.aruba/index.html
@@ -157,6 +157,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 fbf7fd08bd..24003843dd 100644
--- a/components/device_tracker.asuswrt/index.html
+++ b/components/device_tracker.asuswrt/index.html
@@ -150,6 +150,9 @@ This device tracker needs telnet to be enabled on the router.
This tracker discovers new devices on boot and tracks bluetooth devices periodically based on interval_seconds value. Devices discovered are stored with βbt_β as the prefix for device mac in known_devices.yaml.
+
+
+Requires PyBluez
+
+
+
To use the Bluetooth tracker in your installation, add the following to your configuration.yaml file:
diff --git a/components/device_tracker.fritz/index.html b/components/device_tracker.fritz/index.html
index 70f587af66..69ad88ea3c 100644
--- a/components/device_tracker.fritz/index.html
+++ b/components/device_tracker.fritz/index.html
@@ -155,6 +155,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 80e33b1402..17094785b9 100644
--- a/components/device_tracker.icloud/index.html
+++ b/components/device_tracker.icloud/index.html
@@ -153,6 +153,9 @@ You may receive an email from Apple stating that someone has logged into your ac
diff --git a/components/device_tracker.luci/index.html b/components/device_tracker.luci/index.html
index 6811390ff8..f14636d5a9 100644
--- a/components/device_tracker.luci/index.html
+++ b/components/device_tracker.luci/index.html
@@ -161,6 +161,9 @@ Some installations have a s
diff --git a/components/device_tracker.snmp/index.html b/components/device_tracker.snmp/index.html
index 58ae04cdb2..fd23acb2cc 100644
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@@ -159,6 +159,9 @@ This device tracker needs SNMP to be enabled on the router.
diff --git a/components/discovery/index.html b/components/discovery/index.html
index 6821746179..bcf3032dd8 100644
--- a/components/discovery/index.html
+++ b/components/discovery/index.html
@@ -175,12 +175,18 @@ If you see Not initializing discovery because could not install dependency
The mqtt garage door platform let you control your MQTT enabled garage door.
+
+
In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with RETAIN flag, the MQTT switch will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the switch will be false/off.
+
+
When a state topic is not available, the switch will work in optimistic mode. In this mode, the switch will immediately change state after every command. Otherwise, the switch will wait for state confirmation from device (message from state_topic).
+
+
Optimistic mode can be forced, even if state topic is available. Try to enable it, if experiencing incorrect switch operation.
+
+
To use your MQTT binary sensor in your installation, add the following to your configuration.yaml file:
diff --git a/components/index.html b/components/index.html
index 9bce251847..d4aac8d06c 100644
--- a/components/index.html
+++ b/components/index.html
@@ -490,6 +490,20 @@ Support for these components is provided by the Home Assistant community.
+
+
diff --git a/components/lock.mqtt/index.html b/components/lock.mqtt/index.html
index 16f996e2db..540bb2f3f9 100644
--- a/components/lock.mqtt/index.html
+++ b/components/lock.mqtt/index.html
@@ -169,6 +169,9 @@ Make sure that your topic match exact. some-topic/ and some-t
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index 85eba90b32..d9c99f50d9 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -179,6 +179,9 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index 3d8e53a0a1..d0c8b40354 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -160,6 +160,9 @@ The two letters at the beginning of the model number represent the region, UE is
diff --git a/components/media_player.squeezebox/index.html b/components/media_player.squeezebox/index.html
index d109651893..ce0c50ed59 100644
--- a/components/media_player.squeezebox/index.html
+++ b/components/media_player.squeezebox/index.html
@@ -150,6 +150,9 @@ This lets you control Squeezebox hardware like the Classic, Transporter, Duet, B
The webostv platform allows you to control a LG WebOS Smart TV.
+
+
When the TV is first connected, you will need to accept Home Assistant on the TV to allow communication.
+
+
To add a TV to your installation, add the following to your configuration.yaml file and follow the configurator instructions:
+
+
+
# Example configuration.yaml entry
+media_player:
+ platform: webostv
+ host: 192.168.0.10
+ name: Living Room TV
+
+
+
+
+
Configuration variables:
+
+
+
hostOptional: The IP of the LG WebOS Smart TV, e.g. 192.168.0.10
+
nameOptional: The name you would like to give to the LG WebOS Smart TV.
+
+
+
If you do not provide a host name, all LG WebOS Smart TVβs within your network will be auto-discovered if your TV network name is set to [LG] webOS TV
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/media_player.yamaha/index.html b/components/media_player.yamaha/index.html
index 5467ac44b7..9690cbe8fe 100644
--- a/components/media_player.yamaha/index.html
+++ b/components/media_player.yamaha/index.html
@@ -161,6 +161,9 @@
diff --git a/components/mqtt/index.html b/components/mqtt/index.html
index 972d19f954..4082140a07 100644
--- a/components/mqtt/index.html
+++ b/components/mqtt/index.html
@@ -423,6 +423,9 @@ Home Assistant will automatically load the correct certificate if you connect to
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index 957bd12264..bcde94357c 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -166,6 +166,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index 833d898ecd..944aaa6eca 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -177,6 +177,9 @@ which need special attention. By default, the usage by external applications, es
diff --git a/components/sensor.efergy/index.html b/components/sensor.efergy/index.html
index d163372a3a..248e70c95a 100644
--- a/components/sensor.efergy/index.html
+++ b/components/sensor.efergy/index.html
@@ -247,6 +247,9 @@ negative number of minutes your timezone is ahead/behind UTC time.
diff --git a/components/sensor.glances/index.html b/components/sensor.glances/index.html
index dc879a508d..dd7176558f 100644
--- a/components/sensor.glances/index.html
+++ b/components/sensor.glances/index.html
@@ -291,6 +291,9 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index ae4150778c..9983e3bda5 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -275,6 +275,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
This should show something like
-
-client_ip: "127.0.0.1"
-gas_secret: "GAS_SECRET"
-gas_serial: "GAS_SERIAL"
-host: "www.your-loop.com"
-...
-secret: "ELECTRICAL_SECRET"
-serial: "ELECTRICAL_SERIAL"
-
diff --git a/components/sensor.modbus/index.html b/components/sensor.modbus/index.html
index 322dc2c4ce..63e60a3e55 100644
--- a/components/sensor.modbus/index.html
+++ b/components/sensor.modbus/index.html
@@ -284,6 +284,9 @@ Each named register will create an integer sensor and each named bit will create
diff --git a/components/sensor.netatmo/index.html b/components/sensor.netatmo/index.html
index 38fe9c37c6..a3691eb362 100644
--- a/components/sensor.netatmo/index.html
+++ b/components/sensor.netatmo/index.html
@@ -303,6 +303,9 @@ The Home Assistant NetAtmo platform has only be tested with the classic indoor,
diff --git a/components/sensor.rest/index.html b/components/sensor.rest/index.html
index 2d9f2ae20b..75cf1fcffb 100644
--- a/components/sensor.rest/index.html
+++ b/components/sensor.rest/index.html
@@ -333,6 +333,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index 0a2d2d3932..0131a0348a 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -192,6 +192,9 @@ Currently works using default https port only.
diff --git a/components/switch.modbus/index.html b/components/switch.modbus/index.html
index 576749682b..ee70d2e51d 100644
--- a/components/switch.modbus/index.html
+++ b/components/switch.modbus/index.html
@@ -230,6 +230,9 @@ Each named bit will create a switch.
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 3841d73ad2..187398da01 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -169,6 +169,9 @@ Make sure that your topic match exact. some-topic/ and some-t
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index a27c1acf63..1e1954eaeb 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -204,6 +204,9 @@ this component, module-cli-protocol must be loaded on the PulseAudio server.
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index 99fa46194e..6e3c464b79 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -206,6 +206,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/switch.rpi_gpio/index.html b/components/switch.rpi_gpio/index.html
index eb5a4ea2fa..006d27295b 100644
--- a/components/switch.rpi_gpio/index.html
+++ b/components/switch.rpi_gpio/index.html
@@ -204,6 +204,9 @@ If you are not running Raspbian Jessie, you will need to run Home Assistant as r
diff --git a/components/switch.wake_on_lan/index.html b/components/switch.wake_on_lan/index.html
index 145bd06b3f..da5089e4cb 100644
--- a/components/switch.wake_on_lan/index.html
+++ b/components/switch.wake_on_lan/index.html
@@ -191,6 +191,9 @@ The WOL switch can only turn on your computer and monitor the state. There is no
This platform allows you to integrate EQ3 Bluetooth Smart Thermostats.
+
+
The only functionality is to set the temperature, there doesnβt seem to be any way to query the temperature sensor or battery level (read more).
+
+
Setup is a bit more cumbersome than for most other thermostats. It has to be paired first:
+
+
+
bluetoothctl
+scan on
+<Wait for the thermostat to be found, which looks like this: [NEW] Device 00:11:22:33:44:55 CC-RT-BLE>
+scan off
+<Set the thermostat to pairing mode.>
+pair <MAC>
+trust <MAC>
+disconnect <MAC>
+exit
+
+
+
+
+
Then check with gatttool if the connection works as expected:
+
+
+
gatttool -b 00:11:22:33:44:55 -I
+[00:11:22:33:44:55][LE]> connect
+Attempting to connect to 00:11:22:33:44:55
+Connection successful
+[00:11:22:33:44:55][LE]> char-write-req 0x0411 03
+Characteristic value was written successfully
+Notification handle = 0x0421 value: 02 01 09 14 04 2d
+[00:11:22:33:44:55][LE]> disconnect
+[00:11:22:33:44:55][LE]> exit
+
+
+
+
+
Important: For gatttool or homeassistant to work, the thermostat needs to be disconnected from bluetoothd, so I found it best to modify the hass-daemon startscript by adding:
diff --git a/components/thermostat.proliphix/index.html b/components/thermostat.proliphix/index.html
index a7dd0005f6..db21348599 100644
--- a/components/thermostat.proliphix/index.html
+++ b/components/thermostat.proliphix/index.html
@@ -145,9 +145,15 @@ of OID values. A complete collection of the API is available in this
The upnp component automatically creates port forwarding mappings on your router for Home Assistant. UPnP or NAT-PMP needs to be enabled on your router for this component to work.
+
+
Installation
+
You need to install miniupnpc before using the UPnP component:
+
+
+
$ git clone https://github.com/miniupnp/miniupnp.git
+$ cd miniupnp/miniupnpc
+$ make
+$ make pythonmodule3
+$ sudo make installpythonmodule3
+
+
+
+
+
Configuration
+
+
+
# Example configuration.yaml entry
+upnp:
+
+
+
+
+
A port mapping will be created using the IP address and port that Home Assistant is running on. The mapping will never automatically expire. Upon stopping Home Assistant, the mapping will be removed from your router.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/weblink/index.html b/components/weblink/index.html
index f97e16034a..aebaf51681 100644
--- a/components/weblink/index.html
+++ b/components/weblink/index.html
@@ -160,12 +160,18 @@
The zeroconf component exposes your Home Assistant to the local network using Zeroconf. Zeroconf is also sometimes known as Bonjour, Rendezvous and Avahi.
+
+
+
# Example configuration.yaml entry
+zeroconf:
+
+
+
+
+
The registration will include metadata about the Home Assistant instance, including a base URL that can be used to access Home Assistant, the currently running Home Assistant version, and whether an API password is needed to access the instance.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/zwave/index.html b/components/zwave/index.html
index 6b09662fef..f0d71c64b3 100644
--- a/components/zwave/index.html
+++ b/components/zwave/index.html
@@ -198,7 +198,7 @@ Depending on whatβs plugged into your USB ports, the name found above may chan
trigger:
platform: eventevent_type: zwave.scene_activated
- event_data:
+ event_data:
entity_id: zwaveme_zme_wallcs_secure_wall_controller_8scene_id: 11