- 2016-07-30T19:36:26+00:00
+ 2016-07-30T20:21:28+00:00https://home-assistant.io/
@@ -13,6 +13,69 @@
Octopress
+
+
+
+ 2016-07-30T12:00:00+00:00
+ https://home-assistant.io/blog/2016/07/30/custom-frontend-panels--jupyter-notebooks--directv
+ When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
+
+
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!
+
+
We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.
+
+
This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant cna talk to 26 different media players!
+
+
The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.
+
+
I would like to do a shoutout to @fabianhjr. He has started adding typing data (PEP484) to the Home Assistant core. This will help us identify issues before they are released.
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to @n8henrie and @AlucardZero.
+
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to [@n8henrie] and [@AlucardZero].
Entity IDs of Verisure locks will change. This is a one time change but should improve readability.
+
«««< HEAD
+=======
+[@n8henrie]: https://github.com/n8henrie/
+[@AlucardZero]: https://github.com/AlucardZero/
+«««< HEAD
+»»»> master
+=======
+[@Danielhiversen]: https://github.com/danielhiversen
+»»»> origin/master
+
]]>
@@ -1442,58 +1515,6 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
You can achieve the same effect by using the same the same UUID but different major / minor numbers - and tell OwnTracks not to worry about the minor / major numbers for a particular region by setting them to 0).
Make sure to also check out part II where I talk about how to use iBeacons to track any object.
-]]>
-
-
-
-
-
- 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 constant TEMP_CELCIUS is now correctly called TEMP_CELSIUS. Old one is deprecated and will eventually be removed.
-
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:.
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 a2a660dec1..dd57e80382 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 c8cc0944a2..11df133ec0 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 91ee6b3ed4..39f653d605 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 0c4ea953a4..8061cbb094 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 9bcdf560a6..4f32b90a2b 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 250811ce22..fd16702520 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 0bf89169f3..1c4c09ad3d 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 489cbb16d3..03497f1079 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 c02727d31f..b18693548d 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
- PocketCHIP running Home Assistant
-
-
-
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 52b916eab5..5889f91a34 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 e50cd6b1c0..b04b1a9ea5 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 77bf784d36..c993247e0e 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 0f50354f12..417b62fd00 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 39d2639bd6..8f09217ca2 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 a130f68cff..99f695a362 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
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 d24e4bcb17..4cf6a5a2dd 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 6c386f5a4b..720dafd60e 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -231,6 +231,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 aee0d4529d..9ff2d5bd66 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
@@ -313,6 +313,12 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to @n8henrie and @AlucardZero.
+
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to [@n8henrie] and [@AlucardZero].
@@ -307,12 +313,6 @@ plt.savefig('
- PocketCHIP running Home Assistant
-
-
-
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 58862852e5..eb398d9ed5 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
@@ -245,6 +245,12 @@ One of the graphs created with this tutorial.
When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
+
+
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!
+
+
We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.
+
+
This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant cna talk to 26 different media players!
+
+
The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.
+
+
I would like to do a shoutout to @fabianhjr. He has started adding typing data (PEP484) to the Home Assistant core. This will help us identify issues before they are released.
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index e685fd0970..ad4352df3c 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2016-07-30T19:36:26+00:00
+ 2016-07-30T20:21:28+00:00https://home-assistant.io/
@@ -13,6 +13,69 @@
Octopress
+
+
+
+ 2016-07-30T12:00:00+00:00
+ https://home-assistant.io/blog/2016/07/30/custom-frontend-panels--jupyter-notebooks--directv
+ When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
+
+
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!
+
+
We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.
+
+
This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant cna talk to 26 different media players!
+
+
The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.
+
+
I would like to do a shoutout to @fabianhjr. He has started adding typing data (PEP484) to the Home Assistant core. This will help us identify issues before they are released.
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to @n8henrie and @AlucardZero.
+
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to [@n8henrie] and [@AlucardZero].
When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
+
+
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!
+
+
We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.
+
+
This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant cna talk to 26 different media players!
+
+
The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.
+
+
I would like to do a shoutout to @fabianhjr. He has started adding typing data (PEP484) to the Home Assistant core. This will help us identify issues before they are released.
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to @n8henrie and @AlucardZero.
+
Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to [@n8henrie] and [@AlucardZero].
It’s time for release 0.21 and it contains massive core improvements: replacement of our home grown HTTP stack with a standardized WSGI stack. This will improve performance, speed, security and make future development of advanced HTTP features a breeze.
-
-
This work was driven by the amazing Josh Wright. His knowledge, high standards and drive for security has helped improve Home Assistant a lot ever since he started helping out. Hip hip hurray for Josh!
Media Player: Kodi now supports different turn off commands (@armills)
-
-
-
Breaking Changes
-
-
-
Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
-
The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have been updated.
-
Make sure your configuration.yaml file contains frontend: to serve the frontend
-
-
-
Hotfixes 0.21.1 and 0.21.2
-
-
We released two hotfixes to address some issues that couldn’t wait till the next release.
-
-
0.21.1 - June 12
-
-
-
Add eventlet to base requirements to resolve some installation issues (@balloob)
-
GTFS will filter out routes in the wrong direction (@imrehg)
-
Recover from rare error condition from LIRC (@partofthething)
-
Z-Wave autoheal will no longer raise exception (@balloob)
-
Alexa will now execute the script before making reply (@balloob)
It’s time for release 0.21 and it contains massive core improvements: replacement of our home grown HTTP stack with a standardized WSGI stack. This will improve performance, speed, security and make future development of advanced HTTP features a breeze.
+
+
This work was driven by the amazing Josh Wright. His knowledge, high standards and drive for security has helped improve Home Assistant a lot ever since he started helping out. Hip hip hurray for Josh!
Media Player: Kodi now supports different turn off commands (@armills)
+
+
+
Breaking Changes
+
+
+
Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
+
The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have been updated.
+
Make sure your configuration.yaml file contains frontend: to serve the frontend
+
+
+
Hotfixes 0.21.1 and 0.21.2
+
+
We released two hotfixes to address some issues that couldn’t wait till the next release.
+
+
0.21.1 - June 12
+
+
+
Add eventlet to base requirements to resolve some installation issues (@balloob)
+
GTFS will filter out routes in the wrong direction (@imrehg)
+
Recover from rare error condition from LIRC (@partofthething)
+
Z-Wave autoheal will no longer raise exception (@balloob)
+
Alexa will now execute the script before making reply (@balloob)
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 constant TEMP_CELCIUS is now correctly called TEMP_CELSIUS. Old one is deprecated and will eventually be removed.
-
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:.
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 constant TEMP_CELCIUS is now correctly called TEMP_CELSIUS. Old one is deprecated and will eventually be removed.
+
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:.
+
+
+
+
+
+
+
+
+
@@ -725,62 +809,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/arduino/index.html b/components/arduino/index.html
index 566c2143b4..98026ff908 100644
--- a/components/arduino/index.html
+++ b/components/arduino/index.html
@@ -176,6 +176,12 @@ A word of caution: The Arduino boards are not storing states. This means that wi
diff --git a/components/index.html b/components/index.html
index 9ad56b52b4..9ebb3bfaf4 100644
--- a/components/index.html
+++ b/components/index.html
@@ -124,6 +124,10 @@ Support for these components is provided by the Home Assistant community.
+ Frontend
+
+
+
Garage Door
@@ -802,6 +806,20 @@ Support for these components is provided by the Home Assistant community.
+
+
The flux_led support is integrated into Home Assistant as a light platform. Several brands use the same protocol and they have the HF-LPB100 chipset in common.
diff --git a/components/light.rfxtrx/index.html b/components/light.rfxtrx/index.html
index a03872bae8..af878f3086 100644
--- a/components/light.rfxtrx/index.html
+++ b/components/light.rfxtrx/index.html
@@ -198,6 +198,9 @@ Then you should update your configuration to:
diff --git a/components/media_player.cmus/index.html b/components/media_player.cmus/index.html
index 931a7ff5ee..6cf52e6124 100644
--- a/components/media_player.cmus/index.html
+++ b/components/media_player.cmus/index.html
@@ -148,6 +148,9 @@ cmus is configured that instance must be configured to listen to remote connecti
username (Required): Enter your the Google email address you have signed up for Google Voice with. Go to https://www.google.com/voice to setup your Google Voice account.
-
password (Required): Enter the password associated with the above email.
-
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.
+
hostOptional: Use only if you don’t want to scan for devices.
+
nameOptional: Use to give a specific name to the device.
-
Usage
-
-
Google Voice is a notify platform and thus can be controlled by calling the notify service as described here. It will send a notification to all devices listed in the notification target.
-
-
-
# Example automation notification entry
-automation:
- - alias: The sun has set
- trigger:
- platform: sun
- event: sunset
- action:
- service: notify.googlevoice
- data:
- message: 'The sun has set'
- target:
- - 5555555555
- - 5555555556
-
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index 2ff10e3885..3d4c791ee9 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -173,6 +173,9 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
diff --git a/components/media_player.lg_netcast/index.html b/components/media_player.lg_netcast/index.html
index ba7d85c6e7..68e189badc 100644
--- a/components/media_player.lg_netcast/index.html
+++ b/components/media_player.lg_netcast/index.html
@@ -153,6 +153,9 @@ The access token will not change until you factory reset your TV.
The mpchc platform allows you to connect a Media Player Classic Home Cinema to Home Assistant. It will allow you to see the current playing item, and respond to changes in the player’s state.
+
+
For this component to function, you will need to enable the Web Interface in the MPC-HC options dialog.
+
+
+
+
+
+
To add MPC-HC to your installation, add the following to your configuration.yaml file:
zones (Required): This is the list of zones available
+
sources (Required): The list of sources available, these must be in order as they are connected to the device
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index 290f8d2d18..dfa6f570f3 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -166,6 +166,9 @@ The two letters at the beginning of the model number represent the region, UE is
The sonos platform allows you to control your Sonos HiFi wireless speakers and audio components from Home Assistant.
+
The sonos platform allows you to control your Sonos HiFi wireless speakers and audio components from Home Assistant. By default it supports auto-discovery provided by Home Assistant, and you don’t need to add anything to your configuration.yaml. Alternatively, there are some manual configuration options, listed as follows:
-
To add your Sonos components to your installation, add the following to your configuration.yaml file. It will perform auto-discovery of your connected speakers.
+
To add your Sonos components to your installation, add the following to your configuration.yaml file. It will perform Sonos auto-discovery of your connected speakers.
-
# Example configuration.yaml entry
+
# Example configuration.yaml entry using Sonos discoverymedia_player:
platform: sonos
-
You can also specify hosts to connect to if they cannot be found with auto-discovery.
+
If you have multiple network devices, you can provide the IP address of the device that should be used for Sonos auto-discovery.
-
# Example configuration.yaml entry
+
# Example configuration.yaml entry using Sonos discovery on a specific interfacemedia_player:
platform: sonos
- hosts: IP
+ interface_addr: 192.0.2.1
-
Service
+
You can also specify one or more hosts to connect to if they cannot be found with Sonos auto-discovery.
-
There are two extra services exposed that will allow you to take a snapshot of what is currently playing and restore it afterwards. This is useful if you want to play a doorbell or notification sound and resume playback afterwards.
+
+
# Example configuration.yaml entry with manually specified addresses
+media_player:
+ platform: sonos
+ hosts: 192.0.2.25
+
Take a snapshot of what is currently playing on one or more speakers. This service, and the following one, are useful if you want to play a doorbell or notification sound and resume playback afterwards. If no entity_id is provided, all speakers are snapshotted.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of strings that point at entity_ids of coordinator speakers.
+
+
+
+
+
Service sonos_restore
+
+
Restore a previosly taken snapshot of one or more speakers. If no entity_id is provided, all speakers are restored.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of strings that point at entity_ids of coordinator speakers.
+
+
+
+
+
Service sonos_group_players
+
+
Group all players together under a single coordinator.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of a single entity_id that will become the coordinator speaker.
+
+
+
+
+
Service sonos_unjoin
+
+
Remove one or more speakers from a group of speakers. If no entity_id is provided, all speakers are unjoined.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of entity_ids that will be separated from their coordinator speaker.
+
+
+
-
The services are called sonos_snapshot and snapshot_restore.
diff --git a/components/media_player.squeezebox/index.html b/components/media_player.squeezebox/index.html
index bcbfb7f00d..000204ba91 100644
--- a/components/media_player.squeezebox/index.html
+++ b/components/media_player.squeezebox/index.html
@@ -144,6 +144,9 @@ This lets you control Squeezebox hardware like the Classic, Transporter, Duet, B
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index ba0a3ad454..cc67d88b7c 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -172,9 +172,6 @@ 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 edbbb5475f..7b2bc378c9 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -183,9 +183,6 @@ which need special attention. By default, the usage by external applications, es
...
+action:
service: notify.NOTIFIER_NAMEdata:
- title: test notify
- message: That's a exemple
+ title: Send an images
+ message: That's a example that sends an image.data:
photo:
- url: http://192.168.1.28/camera.jpg
@@ -180,6 +181,30 @@ print(chat_id)
password (Optional): Username for an URL which require HTTP basic authentication.
The panel_iframe support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar and can contain external resources like the web frontend of your router, your monitoring system, or your media server.
+
+
To enable Panel iFrames in your installation, add the following to your configuration.yaml file:
diff --git a/components/sensor.dht/index.html b/components/sensor.dht/index.html
index 1d3861c696..46000a93d8 100644
--- a/components/sensor.dht/index.html
+++ b/components/sensor.dht/index.html
@@ -167,6 +167,12 @@ As this requires access to the GPIO, you will need to run Home Assistant as root
diff --git a/components/sensor.efergy/index.html b/components/sensor.efergy/index.html
index 3dea1524e0..d532a5f16b 100644
--- a/components/sensor.efergy/index.html
+++ b/components/sensor.efergy/index.html
@@ -199,6 +199,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 9970c5577c..d009193e4e 100644
--- a/components/sensor.glances/index.html
+++ b/components/sensor.glances/index.html
@@ -243,6 +243,9 @@ Glances web server started on http://0.0.0.0:61208/
Tracking can be setup to track entities of type device_tracker, zone, and sensor. If an entity is placed in the origin or destination then every 5 minutes when the component updates it will use the latest location of that entity.
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index 78fb1e9ae2..73a33c4e7a 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -229,6 +229,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/sensor.modbus/index.html b/components/sensor.modbus/index.html
index cfdc53f51f..5b4aa24d42 100644
--- a/components/sensor.modbus/index.html
+++ b/components/sensor.modbus/index.html
@@ -236,6 +236,9 @@ Each named register will create an integer sensor and each named bit will create
diff --git a/components/sensor.moldindicator/index.html b/components/sensor.moldindicator/index.html
index d42511de57..030ce600a5 100644
--- a/components/sensor.moldindicator/index.html
+++ b/components/sensor.moldindicator/index.html
@@ -192,6 +192,9 @@ With the three measured temperatures (in Celsius or Fahrenheit), the calibration
diff --git a/components/sensor.nest/index.html b/components/sensor.nest/index.html
index a66e1bf309..3cbef76e5b 100644
--- a/components/sensor.nest/index.html
+++ b/components/sensor.nest/index.html
@@ -234,6 +234,9 @@ You must have the Nest component configured to u
diff --git a/components/sensor.rest/index.html b/components/sensor.rest/index.html
index 0a85b64307..8a1dbe4f09 100644
--- a/components/sensor.rest/index.html
+++ b/components/sensor.rest/index.html
@@ -285,6 +285,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/sensor.rfxtrx/index.html b/components/sensor.rfxtrx/index.html
index d0a328151a..43875c1dfa 100644
--- a/components/sensor.rfxtrx/index.html
+++ b/components/sensor.rfxtrx/index.html
@@ -146,6 +146,7 @@ Then you should update your configuration to:
devices:
0a52080705020095220269:
name: Lving
+ fire_event: True0a520802060100ff0e0269:
name: Bathdata_type:
@@ -254,6 +255,9 @@ Then you should update your configuration to:
diff --git a/components/sensor.yweather/index.html b/components/sensor.yweather/index.html
index a07d428692..26d4f71777 100644
--- a/components/sensor.yweather/index.html
+++ b/components/sensor.yweather/index.html
@@ -149,7 +149,8 @@ Use of the Yahoo Weather API should not exceed reasonable request volume. Access
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index 5816875876..c9f31cefe1 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -272,9 +272,6 @@ 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 5bb9878fb7..81f08b7b79 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -173,9 +173,6 @@ Currently works using default https port only.
name (Optional): A name for this devices used within Home assistant
+
address (Required): The KNX group address that is used to turn on/off this actuator channel
+
state_address (Optional): Some KNX devices can change their state internally without any messages on the KXN bus, e.g. if you configure a timer on a channel. The optional state_address can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this wil overwrite the state of the switch object.
+For switching actuators that are only controlled by a single group address and can’t change their state internally, you don’t have to configrue the state address.
diff --git a/components/switch.modbus/index.html b/components/switch.modbus/index.html
index 696e582e1e..d18e36ebe0 100644
--- a/components/switch.modbus/index.html
+++ b/components/switch.modbus/index.html
@@ -209,9 +209,6 @@ Each named bit will create a switch.
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 38ab751db1..ae13f8e9e0 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -225,9 +225,6 @@ 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 7d03be07b4..e140e61e43 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -183,9 +183,6 @@ 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 a808792f84..ab49ba4427 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -185,9 +185,6 @@ 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 ec144cde15..4d11d95834 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -221,9 +221,6 @@ Then you should update your configuration to:
diff --git a/components/switch.rpi_gpio/index.html b/components/switch.rpi_gpio/index.html
index 80fe879959..770107e900 100644
--- a/components/switch.rpi_gpio/index.html
+++ b/components/switch.rpi_gpio/index.html
@@ -186,9 +186,6 @@ If you are not running Raspbian Jessie, you will need to run Home Assistant as r
name (Optional): A name for this devices used within Home assistant
+
address (Required): The KNX group address that is used to turn on/off this actuator channel
+
temperature_address (Required): The group address that is used to communicate the current temperature. Data format must be datapoint type 9.001 DPT_Value_Temp (2-Octet float value) (see http://www.knx.org/fileadmin/template/documents/downloads_support_menu/KNX_tutor_seminar_page/Advanced_documentation/05_Interworking_E1209.pdf)
+
setpoint_address (Required): The group address that is used to set/read the target temperature. Data format must be datapoint type 9.001 DPT_Value_Temp (2-Octet float value). Make sure, you set the read-flag for the thermostat to allow Home Assistant to read the target temperature.
+
+
+
With the current version of the module, no advanced KNX thermostat functionalities (e.g. HVAC mode) are supported.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/thermostat/index.html b/components/thermostat/index.html
index 8e4a3d1b6c..1cc1985d29 100644
--- a/components/thermostat/index.html
+++ b/components/thermostat/index.html
@@ -127,6 +127,9 @@
diff --git a/components/zigbee/index.html b/components/zigbee/index.html
index cb0ac73e3c..7f352588b5 100644
--- a/components/zigbee/index.html
+++ b/components/zigbee/index.html
@@ -199,6 +199,12 @@ The port may also appear as /dev/ttyACM* if you’re communicating with the ZigB
diff --git a/developers/architecture_components/index.html b/developers/architecture_components/index.html
index 2d07fd4d41..eb087c1498 100644
--- a/developers/architecture_components/index.html
+++ b/developers/architecture_components/index.html
@@ -212,6 +212,7 @@ Diagram showing interaction between components and the Home Assistant core.
diff --git a/developers/component_discovery/index.html b/developers/component_discovery/index.html
index 054e843bbb..7863ea9141 100644
--- a/developers/component_discovery/index.html
+++ b/developers/component_discovery/index.html
@@ -184,6 +184,7 @@ This option is only available to built-in components.
diff --git a/developers/component_generic_discovery/index.html b/developers/component_generic_discovery/index.html
index 3e404c6fc2..6273af9ff0 100644
--- a/developers/component_generic_discovery/index.html
+++ b/developers/component_generic_discovery/index.html
@@ -232,6 +232,7 @@ In the past, this was achieved by adding your component to the DISCOVERY_P
diff --git a/developers/component_loading/index.html b/developers/component_loading/index.html
index 1e512f5cd4..a13e2f9ee3 100644
--- a/developers/component_loading/index.html
+++ b/developers/component_loading/index.html
@@ -165,6 +165,7 @@ Home Assistant will use the directory that contains your config file as the dire
diff --git a/developers/component_visibility/index.html b/developers/component_visibility/index.html
index ea48004ae1..2b4e7a8592 100644
--- a/developers/component_visibility/index.html
+++ b/developers/component_visibility/index.html
@@ -161,6 +161,7 @@ You can set a suggestion for your entity’s visibility by setting the hid
diff --git a/developers/development_catching_up/index.html b/developers/development_catching_up/index.html
index cdb97caaa1..d901f9bdb5 100644
--- a/developers/development_catching_up/index.html
+++ b/developers/development_catching_up/index.html
@@ -179,6 +179,7 @@ $ git rebase upstream/dev # to put those changes into your feature branch before
diff --git a/developers/frontend/index.html b/developers/frontend/index.html
index 269559ab06..09c89b7f7c 100644
--- a/developers/frontend/index.html
+++ b/developers/frontend/index.html
@@ -125,7 +125,7 @@ Do not use development mode in production. Home Assistant uses aggressive cachin
Development
-
While you are developing, you need to have webpack running to have your JavaScript changes be made available.
+
While you are developing, you need to have Rollup running to have your JavaScript changes be made available.
$ cd homeassistant/components/frontend/www_static/home-assistant-polymer
@@ -134,15 +134,14 @@ $ npm run js_dev
-
The source code for the frontend can be found in two different directories:
+
The source code for the frontend can be found in three different directories:
After your changes have been accepted into the home-assistant-js repository, you’ll have to update Home Assistant Polymer to use the latest version of it. This can be done by updating package.json. Look for the line that contains home-assistant-js and update the SHA to the SHA of the last commit.
-
Building the Polymer frontend
Building a new version of the frontend is as simple as running script/build_frontend. This fires off the following commands:
@@ -151,22 +150,17 @@ $ npm run js_dev
home-assistant-polymer: Install NPM dependencies.
home-assistant-polymer: start frontend build.
-
Compile all used JavaScript to _app_compiled.js.
+
Compile all used JavaScript.
Install Bower dependencies.
-
Vulcanize all Webcomponents to frontend.vulcan.html.
-
Minify frontend.vulcan.html and save it as frontend.html.
+
Vulcanize and minify the core and panel sources to build dir.
Copy the webcomponents polyfill webcomponents-lite.min.js from home-assistant-polymer to components/frontend/www_static/webcomponents-lite.min.js.
-
Copy the final frontend build frontend.html from home-assistant-polymer to components/frontend/www_static/frontend/.
-
Generate MD5 hash of frontend.html to signal caches to redownload the UI.
+
Copy the final frontend build frontend.html and panel sources from home-assistant-polymer to components/frontend/www_static/frontend/.
The instructions to add a more info dialog are very similar to adding a new card type. This example will add a new more info component for the domain camera:
Any component has the possibility to add a panel to the frontend. Panels will be rendered full screen and have real-time access to the Home Assistant object via JavaScript. Examples of this in the app are map, logbook and history.
+
+
Adding a custom panel to your component is easy. For this example we’re assuming your component is in hello_panel.py. Start by converting your panel to a folder. Create a folder called hello_panel and move hello_panel.py to hello_panel/__init__.py. In that same folder, create a file panel.html.
+
+
Your component should register the panel. The minimum required code for your component is:
diff --git a/developers/index.html b/developers/index.html
index a756cf435a..59db8bb025 100644
--- a/developers/index.html
+++ b/developers/index.html
@@ -155,6 +155,7 @@ Diagram showing interaction between components and the Home Assistant core.
Home Assistant supports running multiple synchronized instances using a master-slave model. Whenever events.fire or states.set is called on the salve it will forward it to the master. The master will replicate all events and changed states to its slaves.
+
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.
The default timeout for an API call with call_service is 5 seconds. Service
+taking longer than this to return will raise
+homeassistant.exceptions.HomeAssistantError: Timeout unless provided with a
+longer timeout.
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index 78f3b3ce95..75b7abdcd6 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -709,6 +709,7 @@ If your client does not support DELETE HTTP requests you can add an
diff --git a/developers/website/index.html b/developers/website/index.html
index d2e284f0a3..d29e30b7cf 100644
--- a/developers/website/index.html
+++ b/developers/website/index.html
@@ -214,6 +214,7 @@ That means that creating a new page is simple. The pages are written in Setup Frontend Environment
diff --git a/getting-started/scripts-conditions/index.html b/getting-started/scripts-conditions/index.html
index 00bffe6b39..b553cf4075 100644
--- a/getting-started/scripts-conditions/index.html
+++ b/getting-started/scripts-conditions/index.html
@@ -199,11 +199,11 @@ This allows you to mix several AND and OR conditions together.
Template condition
-
The template condition will test if the [given template][template] renders a value equal to true. This is achieved by having the template result in a true boolean expression or by having the template render ‘true’.
+
The template condition will test if the given template renders a value equal to true. This is achieved by having the template result in a true boolean expression or by having the template render ‘true’.
# Waits however many minutes input_slider.minute_delay is set to
+# Valid formats include HH:MM and HH:MM:SS
+delay: '00:{{ input_slider.minute_delay }}:00'
+
+
+
+
Fire an Event
This action allows you to fire an event. Events can be used for many things. It could trigger an automation or indicate to another component that something is happening. For instance, in the below example it is used to create an entry in the logbook.
diff --git a/images/frontend/polymer-build-architecture.png b/images/frontend/polymer-build-architecture.png
deleted file mode 100644
index 000e8b5d46..0000000000
Binary files a/images/frontend/polymer-build-architecture.png and /dev/null differ
diff --git a/images/screenshots/mpc-hc.png b/images/screenshots/mpc-hc.png
new file mode 100644
index 0000000000..fd0b095db8
Binary files /dev/null and b/images/screenshots/mpc-hc.png differ
diff --git a/images/supported_brands/directv.png b/images/supported_brands/directv.png
new file mode 100644
index 0000000000..96d4e34eb6
Binary files /dev/null and b/images/supported_brands/directv.png differ
diff --git a/images/supported_brands/google_voice.png b/images/supported_brands/google_voice.png
deleted file mode 100644
index d279cd5616..0000000000
Binary files a/images/supported_brands/google_voice.png and /dev/null differ
diff --git a/images/supported_brands/jupyter.png b/images/supported_brands/jupyter.png
new file mode 100644
index 0000000000..cf33301646
Binary files /dev/null and b/images/supported_brands/jupyter.png differ
diff --git a/images/supported_brands/mpchc.png b/images/supported_brands/mpchc.png
new file mode 100644
index 0000000000..621b243692
Binary files /dev/null and b/images/supported_brands/mpchc.png differ
diff --git a/images/supported_brands/russound.png b/images/supported_brands/russound.png
new file mode 100644
index 0000000000..6dc6e8b715
Binary files /dev/null and b/images/supported_brands/russound.png differ
diff --git a/index.html b/index.html
index 8d8475b18d..f38a175787 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
ESP8266 and MicroPython - Part 1
July 28, 2016
@@ -148,11 +153,6 @@ Home Assistant is an open-source home automation platform running on Python 3. T
July 23, 2016
diff --git a/topics/templating/index.html b/topics/templating/index.html
index 02cfb42109..413605e077 100644
--- a/topics/templating/index.html
+++ b/topics/templating/index.html
@@ -142,8 +142,6 @@ The frontend has a template editor developer tool to help develop and debug temp
states('device_tracker.paulus') will return the state string (not the object) of the given entity or unknown if it doesn’t exist.
is_state('device_tracker.paulus', 'home') will test if the given entity is specified state.
is_state_attr('device_tracker.paulus', 'battery', 40) will test if the given entity is specified state.
-
Filter multiply(x) will convert the input to a number and multiply it with x.
-
Filter round(x) will convert the input to a number and round it to x decimals.
now will be rendered as current time in your time zone.
utcnow will be rendered as UTC time.
as_timestamp will convert datetime object or string to UNIX timestamp
@@ -151,6 +149,10 @@ The frontend has a template editor developer tool to help develop and debug temp
closest() will find the closest entity.
relative_time(timestamp) will format the date time as relative time vs now (ie 7 seconds)
float will format the output as float.
+
Filter multiply(x) will convert the input to a number and multiply it with x.
+
Filter round(x) will convert the input to a number and round it to x decimals.
+
Filter timestamp_local will convert an UNIX timestamp to local time/data.
+
Filter timestamp_utc will convert an UNIX timestamp to UTC time/data.