- 2016-11-05T07:59:48+00:00
+ 2016-11-05T16:08:18+00:00https://home-assistant.io/
@@ -13,6 +13,92 @@
Octopress
+
+
+
+ 2016-11-05T03:04:05+00:00
+ https://home-assistant.io/blog/2016/11/05/hacktoberfest-influxdb-weather
+ Another two weeks have passed and we are pleased to present Home Assistant 0.32.
+
+
Hacktoberfest
+
The Hacktoberfest is over now. Home Assistant made the 2nd and the 3rd place out of almost 30’000 participating repositories with a total of 528 pull requests closed - that’s an average of 17 pull requests a day! Thanks to all the contributors but also to the team of reviewers. This wouldn’t been possible without you 👏 .
+
+
Improved error reporting
+
This release has improved the reporting when a config validation error occurs. Thanks to @kellerza you will now get a persistent notification added to your UI when this happens.
+
+
Asynchronous
+
This release contains the first asynchronous sensor and camera platforms. @pvizeli and @fabaff ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.
+
+
@balloob and @pvizeli worked a lot on the improvement of the core itself.
+
+
Weather component
+
+
For a long time we have had a bunch of weather sensors but it’s getting better: There is now a Weather component. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.
+
+
All changes
+
+
+
+
+
Config: Exclude dirs/files prefixed with . (@lwis)
Our website has now an additional category called “Ecosystem”. This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
Entity IDs of Verisure locks will change. This is a one time change but should improve readability.
-]]>
-
-
-
-
-
- 2016-07-06T05:00:00+00:00
- https://home-assistant.io/blog/2016/07/06/pocketchip-running-home-assistant
-
-Over a year ago I participated in the kickstarter campaign for “CHIP - The World’s First Nine Dollar Computer” by Next Thing Co.. I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives…
-
-
-
-
Thanks to Next Thing Co. and their CHIP which is actually 9 USD the space requirement for a single board computer has decreased. No Ethernet and HDMI output helped with that. But I guess that the next development cycle will allow us to put those boards in a matchbox including wired networking and a SATA interface.
-
-
-
- Size comparison of a Cubieboard, OrangePi One, and CHIP.
-
-
-
If you start using a PocketCHIP you will definitely look like a Blackberry or a GameBoy user. Typing is done with your thumbs :-)
-
-
First a couple of tweaks like setting up sudo, upgrading the existing installation, change passwords, enabling ssh, and removal of the annoying stuff then installation of Home Assistant. There is not much to tell…it’s straight-forward. For the sake of completeness below the notes about what I did.
-
-
A Debian installation is available by default. This means that some dependencies for Home Assistant are missing. I haven’t checked if a new build for the PocketCHIP would include them. So, after a $ sudo apt-get update installing those dependencies take a minute or two.
If you haven’t seen the next two commands already then you should visit our frontsite.
-
-
$ pip3 install homeassistant
-$ hass --open-ui
-
-
-
-
With surf the browsing experience on the low-resolution display is not that great. Most smartphones, even very cheap ones, have touchscreens with higher resolutions. Nevermind, midori is not better.
-
-
-
- PocketCHIP with Home Assistant frontend
-
-
-
Well, with PocketCHIP and Home Assistant you could run your home automation on a 49 USD device with a touchscreen, an integrated USP, and a keyboard. With the GPIO available on top of the display you could even connect your PocketCHIP directly to sensors and actuators.
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 3329f309b0..85ff3a355c 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
@@ -225,6 +225,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 c81dea7bd0..c8a9dffddb 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -201,6 +201,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 018540916c..d5ed724a95 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -177,6 +177,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 2c7c7d5017..c19afb42d7 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -210,6 +210,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 c32cf414fe..1fe291fe40 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -245,6 +245,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 44053c3b6c..3e9c6d025a 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -277,6 +277,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 81edaf7b14..e422c750de 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -328,6 +328,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 f33817b228..b90b5719be 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
@@ -284,6 +284,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 3c5a1f4be3..3bfa4ee334 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
@@ -269,6 +269,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -292,12 +298,6 @@ Support for Temper temperature sensors has been contributed by
- We have a Raspberry Pi image now
-
-
-
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 bf551b7c65..b06d89413b 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
@@ -193,6 +193,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 ee6a9ed39f..7359fa254e 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
@@ -306,6 +306,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 8f2f3c2180..b4a92b6fe3 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
@@ -235,6 +235,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 937cbbefd3..ca6279aded 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
@@ -220,6 +220,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 a1f0cb3e06..55b03cea71 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
@@ -200,6 +200,12 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index 8ce62f8aa9..af8bd670ba 100644
--- a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
+++ b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
@@ -409,6 +409,12 @@ Home Assistant will keep track of historical values and allow you to integrate i
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index df6443a401..f117037f50 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
@@ -211,6 +211,12 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index 01797ce2d2..9c713dc694 100644
--- a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
+++ b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
@@ -226,6 +226,12 @@ This is where we’ll configure our task, so select the plus icon to select an a
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index a0254db60d..fc9f256cd6 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
@@ -209,6 +209,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 ebd7a886c8..741526afb8 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -220,6 +220,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 318798ad28..f4cd07792e 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
@@ -300,6 +300,12 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index 0613bb74fe..14fb3c3d93 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -219,6 +219,12 @@ Over a year ago I participated in the
+
@@ -242,12 +248,6 @@ Over a year ago I participated in the
- We have a Raspberry Pi image now
-
-
-
diff --git a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
index cd14b23e89..52c90d9735 100644
--- a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
+++ b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
@@ -219,6 +219,12 @@
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 5975e35bbf..6a3a99d186 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
@@ -236,6 +236,12 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index 547f1c2bdd..278f073515 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -323,6 +323,12 @@ If a module is missing then you need to download it from the
+
@@ -346,12 +352,6 @@ If a module is missing then you need to download it from the
- We have a Raspberry Pi image now
-
-
-
diff --git a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
index 9be2da7710..4090cd46ce 100644
--- a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
+++ b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
@@ -238,6 +238,12 @@
diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
index 6a5568b56e..73fdd8fc04 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -267,6 +267,12 @@ So, part 1 of ESP8266
Another two weeks have passed and we are pleased to present Home Assistant 0.32.
+
+
Hacktoberfest
+
The Hacktoberfest is over now. Home Assistant made the 2nd and the 3rd place out of almost 30’000 participating repositories with a total of 528 pull requests closed - that’s an average of 17 pull requests a day! Thanks to all the contributors but also to the team of reviewers. This wouldn’t been possible without you 👏 .
+
+
Improved error reporting
+
This release has improved the reporting when a config validation error occurs. Thanks to @kellerza you will now get a persistent notification added to your UI when this happens.
+
+
Asynchronous
+
This release contains the first asynchronous sensor and camera platforms. @pvizeli and @fabaff ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.
+
+
@balloob and @pvizeli worked a lot on the improvement of the core itself.
+
+
Weather component
+
+
For a long time we have had a bunch of weather sensors but it’s getting better: There is now a Weather component. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.
+
+
All changes
+
+
+
+
+
Config: Exclude dirs/files prefixed with . (@lwis)
Our website has now an additional category called “Ecosystem”. This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+
+
+
+
+
Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 7b935b3801..c3a1e8ae23 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -2994,6 +2994,38 @@
+
+
+
+
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 9eb60b5d0a..ca09f05083 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2016-11-05T07:59:48+00:00
+ 2016-11-05T16:08:18+00:00https://home-assistant.io/
@@ -13,6 +13,152 @@
Octopress
+
+
+
+ 2016-11-05T03:04:05+00:00
+ https://home-assistant.io/blog/2016/11/05/hacktoberfest-influxdb-weather
+ Hacktoberfest
+The [Hacktoberfest] is over now. Home Assistant made the 2nd and the 3rd place out of almost 30'000 participating repositories with a total of 528 pull requests closed - that's an average of 17 pull requests a day! Thanks to all the contributors but also to the team of reviewers. This wouldn't been possible without you 👏 .
+
+### Improved error reporting
+This release has improved the reporting when a config validation error occurs. Thanks to [@kellerza] you will now get a persistent notification added to your UI when this happens.
+
+### Asynchronous
+This release contains the first asynchronous sensor and camera platforms. [@pvizeli] and [@fabaff] ported most of the "internal" sensors to async programming. We hope that you will enjoy the new speed.
+
+[@balloob] and [@pvizeli] worked a lot on the improvement of the core itself.
+
+### Weather component
+
+For a long time we have had a bunch of [weather sensors][weather-sensors] but it's getting better: There is now a [Weather component][weather-component]. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.
+
+### All changes
+
+
+
+- Config: Exclude dirs/files prefixed with . ([@lwis])
+- Add mochad component ([@mtreinish])
+- Notify: Added support for [Android TV/FireTV](https://home-assistant.io/components/notify.nfandroidtv/) ([@danielperna84])
+- HTTP: Migrate WSGI to asyncio ([@balloob])
+- Configurator: Support for `entity_picture` ([@amills])
+- Core: Configuration validation error prints line numbers ([@persandstrom])
+- Media player: [Sonos] improvements incl. timer setting functionality ([@bjarniivarsson], [@americanwookie])
+- Zoneminder: SSL/TLS support ([@Khabi])
+- Media player: Discovery support for [Yamaha] ([@sdague])
+- Sensor: New finance platform [CurrencyLayer][currencylayer] ([@arsaboo])
+- Sensor: Support for [InfluxDB sensors][influx-sensor] ([@bestlibre])
+- Sensor: New support [HDDTemp sensors][hddtemp-sensor] ([@fabaff])
+- Camera: Improvements to [RPi camera][rpi-camera] ([@postlund])
+- [ThingSpeak][thingspeak] component ([@simonszu])
+- Core: New property `hass.data` to store internal data ([@balloob])
+- Switch: Templating and configurable timeout for [REST][rest-switch] ([@aa755])
+- Light: [Yeelight][yeelight] Wifi bulbs are now supported ([@HydrelioxGitHub])
+- Sensor: New [random number][random-sensor] sensor ([@fabaff])
+- Media player: New support for [Emby][emby-media] ([@mezz64])
+- [LiteJet][litejet] switches and lights support ([@joncar])
+- Cover: New [garadget] platform ([@JasonCarter80])
+- Pilight: `send_delay` feature ([@janLo])
+- Config: Improvements for `known_devices` ([@kellerza])
+- Device tracker: New discovered event ([@lwis])
+- Device tracker: Improvements and new features for the Volvo on Call platform ([@molobrakos])
+- Climate: Use unit of measurement from a Vera device ([@pavoni])
+- Media player: [Philips TVs][philips_player] with jointSPACE API re now supported ([@danielperna84])
+- Device tracker: [ICloud][icloud] improvements ([@Bart274])
+- Sensor: Support for [Synology DSM][synologydsm] ([@StaticCube])
+- Sensor: Monitoring support for [Dovado routers][dovado-sensor] ([@molobrakos])
+- Sensor: Support for monitoring [printers][cups-sensor] ([@fabaff])
+- Minor features and bug fixes by [@fabaff], [@kellerza], [@robbiet480], [@balloob], [@DavidLP], [@Bart274], [@sdague], [@mtreinish], [@Khabi], [@bbesset], [@bestlibre], [@pvizeli], [@turbokongen], [@devdelay], [@molobrakos], [@postlund], [@wokar], [@amills], [@arsaboo], [@hartmms], [@nsideras], [@tbeckha], and [@kirichkov].
+
+### Misc
+
+Our website has now an additional category called "Ecosystem". This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
+
+- [iOS](https://home-assistant.io/ecosystem/ios/)
+- [SceneGen](https://home-assistant.io/ecosystem/scenegen/)
+
+### Breaking changes
+
+- The [Yahoo Finance][yahoo] platform supports now multiple stock. Please adjust your configuration.
+- Deprecated components `garage_door`, `rollershutter`, `thermostat`, and `hvac` have been removed.
+- The minimum Python version on Windows has been bumped to Python 3.5.
+- The Insteon Hub integration has been disabled due to a [request from Insteon][req-insteon].
+
+### If you need help...
+
+...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
+
+[@aa755]: https://github.com/aa755
+[@americanwookie]: https://github.com/americanwookie
+[@amills]: https://github.com/armills
+[@arsaboo]: https://github.com/arsaboo
+[@balloob]: https://github.com/balloob
+[@Bart274]: https://github.com/Bart274
+[@bbesset]: https://github.com/bbesset
+[@bestlibre]: https://github.com/bestlibre
+[@bjarniivarsson]: https://github.com/bjarniivarsson
+[@danielperna84]: https://github.com/danielperna84
+[@DavidLP]: https://github.com/DavidLP
+[@devdelay]: https://github.com/devdelay
+[@fabaff]: https://github.com/fabaff
+[@hartmms]: https://github.com/hartmms
+[@HydrelioxGitHub]: https://github.com/HydrelioxGitHub
+[@janLo]: https://github.com/janLo
+[@JasonCarter80]: https://github.com/JasonCarter80
+[@joncar]: https://github.com/joncar
+[@kellerza]: https://github.com/kellerza
+[@Khabi]: https://github.com/Khabi
+[@kirichkov]: https://github.com/kirichkov
+[@lwis]: https://github.com/lwis
+[@mezz64]: https://github.com/mezz64
+[@molobrakos]: https://github.com/molobrakos
+[@mtreinish]: https://github.com/mtreinish
+[@nsideras]: https://github.com/nsideras
+[@pavoni]: https://github.com/pavoni
+[@persandstrom]: https://github.com/persandstrom
+[@postlund]: https://github.com/postlund
+[@pvizeli]: https://github.com/pvizeli
+[@robbiet480]: https://github.com/robbiet480
+[@sdague]: https://github.com/sdague
+[@simonszu]: https://github.com/simonszu
+[@StaticCube]: https://github.com/StaticCube
+[@tbeckha]: https://github.com/tbeckha
+[@tchellomello]: https://github.com/tchellomello
+[@turbokongen]: https://github.com/turbokongen
+[@wokar]: https://github.com/wokar
+
+[currencylayer]: https://home-assistant.io/components/sensor.currencylayer/
+[yahoo]: https://home-assistant.io/components/sensor.yahoo_finance/
+[mochat]: https://home-assistant.io/components/mochat/
+[firetv]: https://home-assistant.io/components/notify.firetv/
+[Yamaha]: https://home-assistant.io/components/media_player.yamaha/
+[hddtemp-sensor]: https://home-assistant.io/components/sensor.hddtemp/
+[Sonos]: https://home-assistant.io/components/media_player.sonos/
+[weather-sensors]: https://home-assistant.io/components/#weather
+[rpi-camera]: https://home-assistant.io/components/camera.rpi_camera/
+[rest-switch]: https://home-assistant.io/components/switch.rest/
+[emby-media]: https://home-assistant.io/components/media_player.emby/
+[random-sensor]: https://home-assistant.io/components/sensor.random/
+[yeelight]: https://home-assistant.io/components/light.yeelight/
+[influx-sensor]: https://home-assistant.io/components/sensor.influxdb/
+[weather-component]: https://home-assistant.io/components/weather/
+[cups-sensor]: https://home-assistant.io/components/sensor.cups/
+[litejet]: https://home-assistant.io/components/litejet/
+[garadget]: https://home-assistant.io/components/garadget/
+[philips_player]: https://home-assistant.io/components/media_player.philips_js/
+[icloud]: https://home-assistant.io/components/device_tracker.icloud/
+[synologydsm]: https://home-assistant.io/components/sensor.synologydsm/
+[dovado-sensor]: https://home-assistant.io/components/sensor.dovado/
+[ios]: https://home-assistant.io/ecosystem/ios/
+[Hacktoberfest]: https://hacktoberfest.digitalocean.com/
+[req-insteon]: https://github.com/home-assistant/home-assistant/issues/3811
+[updater]: https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
+[thingspeak]: https://home-assistant.io/components/thingspeak/
+]]>
+
+
@@ -833,274 +979,6 @@ The validation of the configuration is still on-going. Approximatly 80 % is done
[Kodi]: /components/media_player.kodi/
[command-line-switch]: /components/switch.command_line/
[command-line-cover]: /components/cover.command_line/
-]]>
-
-
-
-
-
- 2016-08-28T03:30:25+00:00
- https://home-assistant.io/blog/2016/08/28/notifications-hue-fake-unification
- or maybe#supersized
-
-Keep reading to see what **#Amazing** things we have in store for you this week 😄! And make sure you read all the way to the end, because I left a present down there for those committed few among you :)
-
-But first...
-
-## Some general housekeeping
-
-Paulus ([@balloob]) is on vacation in Europe this week, so you will all have to deal with me, Robbie ([@robbiet480]) for this release blog post. Don't worry, Paulus will be back to tearing apart your pull requests in no time 😈.
-
-Special thanks to my awesome helpers for this week's release who are looking over my shoulder to make sure I'm crossing my t's and dotting my i's: [@Teagan42], [@infamy] and [@fabaff].
-
-For my next trick, let's hand out some...
-
-## Trophies
-
-I felt that I had to 1-up Paulus ([@balloob]) somehow with his 500,000 pageviews stat he shared in the [0.26 blog post](/blog/2016/08/13/foursquare-fast-com-ffmpeg-gpsd/), so I pushed myself and our development community as a whole super hard the last two weeks to put a lot of love into Home Assistant to bring you not just one, but six **#Amazing** stats for this release. As of 0.27, we have now surpassed the following milestones:
-
-* [10,000](https://travis-ci.org/home-assistant/home-assistant/builds/154660811) builds on Travis (congrats to [@BluGeni])
-* [3,000](https://github.com/home-assistant/home-assistant/pull/3000) issues and pull requests (thanks [@kellerza]!)
-* [2,000](https://github.com/home-assistant/home-assistant/pull/2991) pull requests alone (awesome [@fabaff]!!)
-* 900 forks on Github!
-
-In addition,
-
-* We are very close to 4,000 stars on Github!
-* [I'm now #5 contributor by most commits!!!](https://github.com/home-assistant/home-assistant/graphs/contributors) Hey wait, how'd this get in here 😳...
-
-Now that we have that great news out of the way, onto this week's release which is going to keep the **#Amazing** gravy train rolling right along and get to the stuff you all _really_ are here for.
-
-## 0.27
-
-While this release is **#Amazing**, we had to break a few eggs (now you understand the title reference!) to make a beautiful omelette (using home automation obviously) so some platforms and components have needed to introduce breaking changes. Please make sure to read the [Breaking Changes](#breaking-changes) section below.
-
-### Hue Bridge Emulation
-Thanks to [@mgbowen] we now have the functionality previously provided by [@blocke]'s [ha-local-echo](https://github.com/blocke/ha-local-echo) [built right into Home Assistant](/components/emulated_hue/)! This means that for those of you with devices that either lack or have a subpar integration with Home Assistant (looking at you Amazon Echo) you can now have a better experience by having your Home Assistant pretend to be a Hue Bridge. Personally, I have used [@auchter]'s [Haaska](https://github.com/auchter/haaska) previously but found that it was slow to respond and sometimes failed entirely. With the new [`emulated_hue`](/components/emulated_hue/) component, you can have local control of entities through Amazon Echo.
-
-### Notification improvements
-We have some excellent upgrades to the notification system coming to you in 0.27, courtesy of me, [@robbiet480].
-
-#### HTML5 Push Notifications
-This release adds support for [HTML5] push notifications on Chrome/Firefox/Opera on both desktop and Android devices. This means that you can send a notification to your phone even when your Home Assistant is not open in your mobile browser. When using Chrome you can even include 2 action buttons so that you can control your Home Assistant from your phone's lock screen, allowing you to do things like sound alarms or unlock your front door, all without leaving the notification. Thanks again to me ([@robbiet480]) and Paulus ([@balloob]) for all the hard work on this!
-
-
-
-
-
-#### Notification Groups
-Using the new notify `group` platform allows you to cut down a lot of duplicate automation logic by combining multiple notification platforms and `target`s into a single notify service. Check out the [docs](/components/notify.group/) for more info.
-
-#### `target` is no longer needed!
-For platforms that support it, starting with the new HTML5 platform, any `target`s that are available will be exposed as individual services, so no more having to remember which `target`s to use. Please note that the existing services also still exist so you can keep using `target` if you wish.
-
-### Validate configuration before restarting Home Assistant
-Ever restarted Home Assistant to test a configuration change just to find out there is a validation error? Well, not anymore! [@kellerza] has added a command line script that will validate your configuration as if you started Home Assistant.
-
-```bash
-$ hass --script check_config
-```
-
-### Configuration validation
-This release includes a big push on making sure all platforms contain proper configuration validation. This should help in getting your configuration right. Thanks to [@fabaff], [@pavoni], [@pvizeli], [@nkgilley] for all the hard work on this, you all rock!
-
-
-
-
-
-### FFMpeg motion/noise sensing
-It's now possible to use [FFMpeg] to monitor a video stream and detect motion thanks to a new binary sensor platform by [@pvizeli].
-
-### Component clean up - Thermostat & HVAC -> Climate. Rollershutter & Garage Door -> Cover.
-Due to our wild growth we ended up with a few components that had a lot of overlapping functionality. [@turbokongen] took on the hard job on merging them. Thermostat and HVAC platforms are now combined under the new Climate component. Rollershutter and Garage Door platforms are now combined under the new Cover component. You can easily upgrade by just swapping out the name. For example replace `thermostat` with `climate`. The old components have been deprecated and will be removed in the near future.
-
-### A new `fan` component
-Along with the new `climate` component, [@Teagan42] and I ([@robbiet480]) decided we needed something simpler to just control a fan. Currently it has support for controlling Insteon fans. MQTT support will appear in 0.28.0. I tried to get it implemented before 0.27.0 but spent too long writing this blog post 😢.
-
-### All changes
-
-
-
-- Merge thermostat and HVAC components into new [climate] component ([@turbokongen])
-- Merge rollershutter and garage door components into new [cover] component ([@turbokongen])
-- Alarm Control Panel - Manual: Allow returning to previous state after [trigger] ([@tobiebooth])
-- Sensor - DHT: Allow range [checking] ([@open-homeautomation])
-- Light entities will now [expose] their features ([@shmuelzon])
-- Sensor: Monitor HP ILO sensors on [HP] servers ([@Juggels])
-- Sensor: Monitor [Fritzbox] Calls ([@DavidMStraub])
-- Notify: LlamaLab [Automate] is now supported ([@danielperna84])
-- Sensor: Serial [CO2] sensors now supported ([@open-homeautomation])
-- Sensor: MQTT room [presence] detection ([@mKerix])
-- Notify: New group platform allows [grouping] notify targets across platforms ([@robbiet480])
-- [HTML5] push notifications ([@robbiet480], [@balloob])
-- Weather: [Wunderground] now supported ([@arsaboo], [@Teagan42])
-- New check config script to test validity before restarting HA ([@kellerza])
-- Binary Sensor: Allow [monitoring] a camera feed using FFMpeg ([@pvizeli])
-- Cover: Z-Wave platform now supports [positions] ([@nunofgs])
-- Device tracker: allow using [Gravatar] for entity picture ([@robbiet480])
-- Notify: platforms with known targets will expose them as standalone services ([@robbiet480])
-- Camera: [MJPEG] and [Generic] camera's can now authenticate using digest auth ([@meatz])
-- Weather: Forecast.io now can show daily temp/precip [forecast] values ([@DavidMStraub])
-- Media Player: WebOS TV now allows [customizing][webos] the sources ([@roidayan])
-- Device tracker: Allow tracking devices using [Bluetooth] Low-Energy ([@open-homeautomation])
-- Notify: Ensure [Slack] messages appear as correct user ([@technicalpickles])
-- YAML: [Secrets] will look for values in all parents folders up to the config root folder ([@Teagan42])
-- Camera: Generic camera now supports [template] support ([@balloob])
-- Slack: Allow sending [attachments] ([@technicalpickles])
-- Device Tracking: TP-Link Archer C7 5 GHz devices will now also be [found] ([@dpford])
-- Z-Wave: New rename [node] service added ([@jnewland])
-- Wink: [Bug] fixes ([@w1ll1am23])
-- Homematic: new device and controller variable [support] ([@danielperna84], [@pvizeli], [@mcdeck])
-- Allow emulating a [Hue] bridge to control entities ([@mgbowen])
-- New [Fan][fan] component ([@Teagan42], [@robbiet480])
-
-### Breaking changes
-- Ecobee3 occupancy sensors have moved from sensor platform to binary sensor platform.
-- Forecast.io entity IDs are now like `sensor.forecastio_temperature`. Previously they were like `sensor.weather_temperature`. Apologies for this change, but we needed to make Forecast.io more generic now that we have many weather platforms.
-- The [Loop Energy][Loop] sensor configuration format changed slightly, please reformat based on the revised documentation.
-- The configuration for the [SABnzbd] sensor has slightly changed. The prefix `type:` is no longer required for monitored variables.
-- The [IMAP] sensor now uses `username` instead of `user`.
-- The [NZBGet] sensor has had so many changes I can't list them all. Please refer to the documentation for more info.
-
-### Deprecations
-- Using the `thermostat` and `hvac` components has been deprecated. Please migrate to the new `climate` component. (just change the component name, the configurations are compatible)
-- Using the `rollershutter` and `garage_door` components have also been deprecated. Please migrate to the new `cover` component. (just change the component name, the configurations are compatible)
-
-## Finishing up
-
-Thanks all for sticking with me to the end. I'll be taking over a lot of Paulus's ([@balloob]) work while he is gone, but as I said, don't worry because he'll be back well before 0.28.0 comes out. Hopefully you didn't find this jovial blog post too jarring from our standard style, I just wrote a lot of this at 2am after being awake for almost 20 hours, so I'm a little loopy hahaha 😴.
-
-Also, thanks as always to our developer contributors, documentation contributors, but most of all our users! This would've just been a script that Paulus (@balloob) used to control his lights at home if we didn't have your enthusiasm.
-
-Feel free to let me know what you thought of this blog post and release on Gitter or my [Twitter](https://twitter.com/robbie), or even the [Home Assistant Twitter](https://twitter.com/home_assistant). Did I mention we have a brand new [Facebook page](https://www.facebook.com/homeassistantio) that you should absolutely Like? There's a convenient Facebook Like and Twitter follow button right on the sidebar.
-
-I almost forgot about your 🎁 for reading all the way to here: a 🍪! Hope you enjoy it in good health 😄.
-
-Talk to you soon on Gitter and in your pull request comments!
-
--- Robbie
-
-(p.s. To those of you that scrolled directly to the bottom to get your present, just know that you didn't earn it like the others did. 😄)
-
-## Hotfix 0.27.1 - August 30
-
-- Migrate APCUPSd to voluptuous ([@fabaff])
-- Ecobee operation mode fix ([@turbokongen])
-- update ha-ffmpeg version to 0.9 ([@pvizeli])
-- Device tracker component & platform validation. No more home_range. ([@kellerza])
-- Added option to use effect:random for Flux Led light bulbs ([@tchellomello])
-- Use voluptuous for smtp ([@pvizeli])
-- Upgrade sendgrid to 3.2.10 ([@fabaff])
-- Upgrade TwitterAPI to 2.4.2 ([@fabaff])
-- Fix bug in wemo discovery caused by voluptuous addition. ([@pavoni])
-- Bug fix for asuswrt device_tracker. ([@Danielhiversen])
-- Remove units for humidity in Wundeground sensor ([@arsaboo])
-- Fix media_player descriptions and select_source ([@MartinHjelmare])
-- Allow user to configure server id to perform speed test against ([@Teagan42])
-- Bug fix for asuswrt device_tracker. ([@Danielhiversen])
-- More Ecobee operation mode fixes ([@turbokongen])
-- Map Modes to setpoint indexes ([@turbokongen])
-- fix voluptuous and cover autodiscovery ([@pvizeli])
-- Fixes wrong statevalue and problem with zwave setpoint ([@turbokongen])
-
-## Hotfix 0.27.2 - September 3
-### home-assistant
-
-- Ble fix ([#3019](https://github.com/home-assistant/home-assistant/pull/3019)) - ([@open-homeautomation](https://github.com/open-homeautomation))
-- Reset insteon hub ([#3062](https://github.com/home-assistant/home-assistant/pull/3062)) - ([@Teagan42](https://github.com/Teagan42))
-- Host should be optional for apcupsd component ([#3072](https://github.com/home-assistant/home-assistant/pull/3072)) - ([@Danielhiversen](https://github.com/Danielhiversen))
-- Zwave climate Bugfix: if some setpoints have different units, we should fetch the o… ([#3078](https://github.com/home-assistant/home-assistant/pull/3078)) - ([@turbokongen](https://github.com/turbokongen))
-- Bugfix unit fix ([#3083](https://github.com/home-assistant/home-assistant/pull/3083)) - ([@turbokongen](https://github.com/turbokongen))
-- Ecobee humidity slider ([#3088](https://github.com/home-assistant/home-assistant/pull/3088)) - ([@turbokongen](https://github.com/turbokongen))
-- Zwave Climate Bugfix: If device was off target temp was null. Default to Heating setpoint ([#3091](https://github.com/home-assistant/home-assistant/pull/3091)) - ([@turbokongen](https://github.com/turbokongen))
-- Climate and cover bugfix ([#3097](https://github.com/home-assistant/home-assistant/pull/3097)) - ([@turbokongen](https://github.com/turbokongen))
-- Add missing docstrings (fix PEP257 issues) ([#3098](https://github.com/home-assistant/home-assistant/pull/3098)) - ([@fabaff](https://github.com/fabaff))
-- Allow None MAC to be loaded from known_devices ([#3102](https://github.com/home-assistant/home-assistant/pull/3102)) - ([@kellerza](https://github.com/kellerza))
-- fix homematic climate implementation ([#3114](https://github.com/home-assistant/home-assistant/pull/3114)) - ([@pvizeli](https://github.com/pvizeli))
-- Fixed Homematic cover ([#3116](https://github.com/home-assistant/home-assistant/pull/3116)) - ([@danielperna84](https://github.com/danielperna84))
-- Bugfix. climate and covermqt ([#3130](https://github.com/home-assistant/home-assistant/pull/3130)) - ([@turbokongen](https://github.com/turbokongen))
-
-### home-assistant-polymer
-
-- Fix missing attributes on the climate and HVAC more info cards ([7e455e2](https://github.com/home-assistant/home-assistant-polymer/commit/7e455e2be1cb7cc4f55628b063019bea548a3182)) - ([@robbiet480](https://github.com/robbiet480))
-- Add a default icon for the fan component ([#101](https://github.com/home-assistant/home-assistant-polymer/pull/101)) - ([@robbiet480](https://github.com/robbiet480))
-
-[@arsaboo]: https://github.com/arsaboo
-[@auchter]: https://github.com/auchter
-[@balloob]: https://github.com/balloob
-[@blocke]: https://github.com/blocke
-[@BluGeni]: https://github.com/BluGeni
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@danielperna84]: https://github.com/danielperna84
-[@DavidMStraub]: https://github.com/DavidMStraub
-[@dpford]: https://github.com/dpford
-[@fabaff]: https://github.com/fabaff
-[@infamy]: https://github.com/infamy
-[@jnewland]: https://github.com/jnewland
-[@Juggels]: https://github.com/Juggels
-[@kellerza]: https://github.com/kellerza
-[@MartinHjelmare]: https://github.com/MartinHjelmare
-[@mcdeck]: https://github.com/mcdeck
-[@meatz]: https://github.com/meatz
-[@mgbowen]: https://github.com/mgbowen
-[@mKerix]: https://github.com/mKerix
-[@nkgilley]: https://github.com/nkgilley
-[@nunofgs]: https://github.com/nunofgs
-[@open-homeautomation]: https://github.com/open-homeautomation
-[@pavoni]: https://github.com/pavoni
-[@pvizeli]: https://github.com/pvizeli
-[@robbiet480]: https://github.com/robbiet480
-[@roidayan]: https://github.com/roidayan
-[@roidayan]: ttps://github.com/roidayan
-[@shmuelzon]: https://github.com/shmuelzon
-[@tchellomello]: https://github.com/tchellomello
-[@Teagan42]: https://github.com/Teagan42
-[@technicalpickles]: https://github.com/technicalpickles
-[@tobiebooth]: https://github.com/tobiebooth
-[@turbokongen]: https://github.com/turbokongen
-[@w1ll1am23]: https://github.com/w1ll1am23
-
-[checking]: /components/sensor.dht/
-[FFMpeg]: /components/binary_sensor.ffmpeg/
-[Climate]: /components/climate/
-[NZBGet]: /components/sensor.nzbget/
-[SABnzbd]: /components/sensor.sabnzbd/
-[HP]: /components/sensor.hp_ilo/
-[Fritzbox]: /components/sensor.fritzbox_callmonitor/
-[webos]: /components/media_player.webostv/
-[HTML5]: /components/notify.html5/
-[Gravatar]: /components/device_tracker/
-[Loop]: /components/sensor.loop_energy/
-[cover]: /components/cover/
-[climate]: /components/climate/
-[expose]: /components/light/
-[Automate]: /components/notify.llamalab_automate/
-[Secrets]: /topics/secrets/
-[trigger]: /components/alarm_control_panel.manual/
-[CO2]: /components/sensor.mhz19/
-[presence]: /components/sensor.mqtt_room
-[grouping]: /components/notify.group/
-[Wunderground]: /components/sensor.wunderground/
-[monitoring]: /components/binary_sensor.ffmpeg/
-[MJPEG]: /components/camera.mjpeg/
-[Generic]: /components/camera.generic/
-[positions]: /components/cover.zwave/
-[forecast]: /components/sensor.forecast/
-[Bluetooth]: /components/device_tracker.bluetooth_le_tracker/
-[Slack]: /components/notify.slack/
-[template]: /components/camera.generic/
-[Bug]: /components/wink/
-[support]: /components/homematic/
-[node]: /components/zwave/
-[found]: /components/device_tracker.tplink/
-[attachments]: /components/notify.slack/
-[Hue]: /components/emulated_hue/
-[fan]: /components/fan/
-[IMAP]: /components/sensor.imap/
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index 3912854e3f..fe2b91f511 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -99,6 +99,38 @@
Another two weeks have passed and we are pleased to present Home Assistant 0.32.
+
+
Hacktoberfest
+
The Hacktoberfest is over now. Home Assistant made the 2nd and the 3rd place out of almost 30’000 participating repositories with a total of 528 pull requests closed - that’s an average of 17 pull requests a day! Thanks to all the contributors but also to the team of reviewers. This wouldn’t been possible without you 👏 .
+
+
Improved error reporting
+
This release has improved the reporting when a config validation error occurs. Thanks to @kellerza you will now get a persistent notification added to your UI when this happens.
+
+
Asynchronous
+
This release contains the first asynchronous sensor and camera platforms. @pvizeli and @fabaff ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.
+
+
@balloob and @pvizeli worked a lot on the improvement of the core itself.
+
+
Weather component
+
+
For a long time we have had a bunch of weather sensors but it’s getting better: There is now a Weather component. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.
+
+
All changes
+
+
+
+
+
Config: Exclude dirs/files prefixed with . (@lwis)
Our website has now an additional category called “Ecosystem”. This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+
+
+
+
+
+
+
@@ -1414,55 +1532,6 @@ So, part 1 of ESP8266
-
Thanks to Anton Kireyeu we are able to present another awesome Jupyter notebook. I guess that you all know the graph which Github is using to visualize your commits per day over a time-line. It’s a so-called heatmap. If there are more commits, it’s getting hotter. The latest notebook is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.
Thanks to Anton Kireyeu we are able to present another awesome Jupyter notebook. I guess that you all know the graph which Github is using to visualize your commits per day over a time-line. It’s a so-called heatmap. If there are more commits, it’s getting hotter. The latest notebook is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.
+
+
+
+Heatmap
+
+
+
+
+
+
+
+
@@ -713,51 +762,6 @@ One of the graphs created with this tutorial.
-
-
-
-
-
-
-
-
-Over a year ago I participated in the kickstarter campaign for “CHIP - The World’s First Nine Dollar Computer” by Next Thing Co.. I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives…
+Over a year ago I participated in the kickstarter campaign for “CHIP - The World’s First Nine Dollar Computer” by Next Thing Co.. I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives…
I’ve been planning to write this post for a while now as we get questions like this a lot: “Why does Home Assistant use Polymer? Why not React, Redux and what not?”
-
-
It’s understandable, Polymer is quite the underdog in the world of web frameworks. A corporate backer does not guarantee popularity or an active community and this shows in the number of projects using Polymer.
-
-
Still, we use Polymer and it’s awesome. To explain why, I’ll be referencing the React workflow quite a bit, as they do a lot of things right, and show how it is done in Polymer.
-
-
Polymer gives us components for the web, just like React, but based on web standards: web components, CSS variables. These standards don’t have wide browser support yet but it’s being implemented by every major browser: It’s the future. For now they are being polyfilled and that works just fine but in the future the Home Assistant web app will be able to run native in the browsers == fast.
I’ve been planning to write this post for a while now as we get questions like this a lot: “Why does Home Assistant use Polymer? Why not React, Redux and what not?”
+
+
It’s understandable, Polymer is quite the underdog in the world of web frameworks. A corporate backer does not guarantee popularity or an active community and this shows in the number of projects using Polymer.
+
+
Still, we use Polymer and it’s awesome. To explain why, I’ll be referencing the React workflow quite a bit, as they do a lot of things right, and show how it is done in Polymer.
+
+
Polymer gives us components for the web, just like React, but based on web standards: web components, CSS variables. These standards don’t have wide browser support yet but it’s being implemented by every major browser: It’s the future. For now they are being polyfilled and that works just fine but in the future the Home Assistant web app will be able to run native in the browsers == fast.
Today the news spread that Google will be shutting down the Revolv hubs. And shutting down here doesn’t mean they stop selling or supporting them - no, they are sending an update to each hub to turn your perfectly fine home automation hub into a useless piece of plastic. The fact that this seemed like a good idea by Google astonishes me. If anything, they should have gone the same route as ninjasphere: open it all up and let people decide on the fate of their own hub.
The cloud should be treated as an extension to your smart home instead of running it.
-
-
-
Your hub should not be affected when your internet breaks down or the company that sold you your hub goes out of business. It should work locally so that it can continue to work even long after the vendor goes out of business or decides to kill it. Preferably, your hub should also be open so that the community can take over development after the vendor stops caring.
-
-
Unless you can afford losing a product here and there, be cautious when buying IoT products that depend on the cloud from companies that are not well established. The chances are high that they go bankrupt or get acquired and closed. This however is easier said than done as Gartner predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.
Today the news spread that Google will be shutting down the Revolv hubs. And shutting down here doesn’t mean they stop selling or supporting them - no, they are sending an update to each hub to turn your perfectly fine home automation hub into a useless piece of plastic. The fact that this seemed like a good idea by Google astonishes me. If anything, they should have gone the same route as ninjasphere: open it all up and let people decide on the fate of their own hub.
The cloud should be treated as an extension to your smart home instead of running it.
+
+
+
Your hub should not be affected when your internet breaks down or the company that sold you your hub goes out of business. It should work locally so that it can continue to work even long after the vendor goes out of business or decides to kill it. Preferably, your hub should also be open so that the community can take over development after the vendor stops caring.
+
+
Unless you can afford losing a product here and there, be cautious when buying IoT products that depend on the cloud from companies that are not well established. The chances are high that they go bankrupt or get acquired and closed. This however is easier said than done as Gartner predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.
+
+
+
+
+
+
+
@@ -814,58 +866,6 @@ Example of the new views in the frontend. Learn mor
-
-
-
-
People often ask me about my vision for Home Assistant. Before I can describe where I want to go with Home Assistant, I should first talk about how home automation would look in my ideal world. This will be the aim of this post. I’m not going to focus on protocols, networks or specific hubs. That’s all implementation details. Instead, this post will focus on what is most important: the interaction between the users and their home.
-
-
You should not have to adapt to technology.
-
-
When people start using home automation, they always experience home control first: being able to control devices in new ways using a phone or computer. They believe the future is now and their app will be their remote for their lives. They only focus on what they are getting, not on what they are losing. You install some light bulbs and all of a sudden you are no longer able to use the light switches. You’ll arrive at home at night and have to pull out your phone, open the app, let it connect and finally you’ll be able to turn on the light. All while turning the light on could have been a switch away.
-
-
Yes, you can solve this with presence detection. What if your phone runs out of battery? You’ll have to resort to the switch again.
-
-
If you find that using your new home devices is cumbersome, the promise of home automation technology has failed you. Your lights should work with both a switch (or button) at the entrance of your room and via presence detection. Honestly, there are hardly any valid use cases for being able to control lights from your phone except for showing off.
People often ask me about my vision for Home Assistant. Before I can describe where I want to go with Home Assistant, I should first talk about how home automation would look in my ideal world. This will be the aim of this post. I’m not going to focus on protocols, networks or specific hubs. That’s all implementation details. Instead, this post will focus on what is most important: the interaction between the users and their home.
+
+
You should not have to adapt to technology.
+
+
When people start using home automation, they always experience home control first: being able to control devices in new ways using a phone or computer. They believe the future is now and their app will be their remote for their lives. They only focus on what they are getting, not on what they are losing. You install some light bulbs and all of a sudden you are no longer able to use the light switches. You’ll arrive at home at night and have to pull out your phone, open the app, let it connect and finally you’ll be able to turn on the light. All while turning the light on could have been a switch away.
+
+
Yes, you can solve this with presence detection. What if your phone runs out of battery? You’ll have to resort to the switch again.
+
+
If you find that using your new home devices is cumbersome, the promise of home automation technology has failed you. Your lights should work with both a switch (or button) at the entrance of your room and via presence detection. Honestly, there are hardly any valid use cases for being able to control lights from your phone except for showing off.
We have all been hard at work to get this latest release ready. One of the big highlights in this release is the introduction of an extended iconset to be used in the frontend (credits to @happyleavesaoc for idea and prototype). To get started with customizing, pick any icon from MaterialDesignIcons.com, prefix the name with mdi: and stick it into your customize section in configuration.yaml:
We have all been hard at work to get this latest release ready. One of the big highlights in this release is the introduction of an extended iconset to be used in the frontend (credits to @happyleavesaoc for idea and prototype). To get started with customizing, pick any icon from MaterialDesignIcons.com, prefix the name with mdi: and stick it into your customize section in configuration.yaml:
This is a guest post by Home Assistant user and contributor Nolan Gilley.
-
-
In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.
-
-
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a Moteino, an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don’t have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the MQTT component to my Raspberry Pi.
-
-
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It’s easy to see when the washing machine is in operation here. I used the same technique for the dryer’s accelerometer.
This is a guest post by Home Assistant user and contributor Nolan Gilley.
+
+
In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.
+
+
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a Moteino, an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don’t have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the MQTT component to my Raspberry Pi.
+
+
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It’s easy to see when the washing machine is in operation here. I used the same technique for the dryer’s accelerometer.
It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.
-
-
The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).
-
-
-
-The old logo, the new detailed logo and the new simple logo.
-
It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.
+
+
The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).
+
+
+
+The old logo, the new detailed logo and the new simple logo.
+
diff --git a/components/binary_sensor.nest/index.html b/components/binary_sensor.nest/index.html
index fe6e9e3c93..8345313b56 100644
--- a/components/binary_sensor.nest/index.html
+++ b/components/binary_sensor.nest/index.html
@@ -168,9 +168,6 @@ You must have the Nest component configured to u
diff --git a/components/climate.nest/index.html b/components/climate.nest/index.html
index 5fc7deb83c..aac19e90cf 100644
--- a/components/climate.nest/index.html
+++ b/components/climate.nest/index.html
@@ -143,9 +143,6 @@ You must have the Nest component configured to u
diff --git a/components/rollershutter.wink/index.html b/components/climate.wink/index.html
similarity index 64%
rename from components/rollershutter.wink/index.html
rename to components/climate.wink/index.html
index f38e68c868..b8a20a20e3 100644
--- a/components/rollershutter.wink/index.html
+++ b/components/climate.wink/index.html
@@ -7,26 +7,26 @@
- Wink Rollershutter - Home Assistant
+ Wink Thermostat - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,19 +84,13 @@
- Wink Rollershutter
+ Wink Thermostat
-
-This platform has been deprecated in favor of a “cover” platform and will be removed in the future. Please use the cover platform.
-
-
-
The wink rollershutter platform allows you to control your Wink enabled rollershutters. It supports Wink shades/blinds/rollershutters such as the Bali Somfy or Lutron Serena blinds.
-
-
The Wink API currently doesn’t provide status for shades.
+
The Wink climate platform allows you to get data from your Wink thermostats.
The requirement is that you have setup your Wink hub.
diff --git a/components/climate.zwave/index.html b/components/climate.zwave/index.html
index 15c0d8a9e2..68a1a5d797 100644
--- a/components/climate.zwave/index.html
+++ b/components/climate.zwave/index.html
@@ -197,30 +197,18 @@ If the thermostat support different operating modes, you will get one thermostat
diff --git a/components/climate/index.html b/components/climate/index.html
index 4238fae2e8..bfa4a7f316 100644
--- a/components/climate/index.html
+++ b/components/climate/index.html
@@ -461,6 +461,9 @@ Not all climate services may be available for your platform. Be sure to check th
diff --git a/components/cover.mqtt/index.html b/components/cover.mqtt/index.html
index 017f8bfae6..ada619027b 100644
--- a/components/cover.mqtt/index.html
+++ b/components/cover.mqtt/index.html
@@ -200,9 +200,6 @@ state from state_topic. If these messages
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 fan will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the fan will be false.
-
When a state_topic is not available, the fan will work in optimistic mode. In this mode, the fan will immediately change state after every command. Otherwise, the fan will wait for state confirmation from device (message from state_topic).
+
When a state_topic is not available, the fan will work in optimistic mode. In this mode, the fan will immediately change state after every command. Otherwise, the fan will wait for state confirmation from the device (message from state_topic).
-
Optimistic mode can be forced, even if state topic is available. Try to enable it, if experiencing incorrect fan operation.
+
Optimistic mode can be forced even if a state_topic is available. Try to enable it if you are experiencing incorrect fan operation.
To enable MQTT fans in your installation, add the following to your configuration.yaml file:
command_topic (Required): The MQTT topic to publish commands to change the fan state.
state_topic (Optional): The MQTT topic subscribed to receive state updates.
name (Optional): The name of the fan. Default is ‘MQTT Fan’.
+
state_topic (Optional): The MQTT topic subscribed to receive state updates.
payload_on (Optional): The payload that represents the running state. Default is “ON”.
payload_off (Optional): The payload that represents the stop state. Default is “OFF”.
-
optimistic (Optional): Flag that defines if lock works in optimistic mode. Default is true if no state topic defined, else false.
-
qos (Optional): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
-
retain (Optional): If the published message should have the retain flag on or not.
state_value_template (Optional): Defines a template to extract a value from the state.
-
speed_state_topic (Optional): The MQTT topic subscribed to receive speed updates.
-
speed_command_topic (Optional): The MQTT topic to publish commands to change the fan speed.
-
speed_value_template (Optional): Defines a template to extract a value from the speed.
-
oscillation_state_topic (Optional): The MQTT topic subscribed to receive oscillation updates.
-
oscillation_command_topic (Optional): The MQTT topic to publish commands to change the fan oscillation.
+
qos (Optional): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+
optimistic (Optional): Flag that defines if lock works in optimistic mode. Default is true if no state topic defined, else false.
+
retain (Optional): If the published message should have the retain flag on or not.
+
oscillation_state_topic (Optional): The MQTT topic subscribed to receive oscillation state updates.
+
oscillation_command_topic (Optional): The MQTT topic to publish commands to change the oscillation state.
+
payload_oscillation_on (Optional): The payload that represents the oscillation on state. Default is “oscillate_on”.
+
payload_oscillation_off (Optional): The payload that presents the oscillation off state. Default is “oscillate_off”.
oscillation_value_template (Optional): Defines a template to extract a value from the oscillation.
-
payload_oscillation_on (Optional): The payload that represents the oscillation state. Default is “ON”.
-
payload_oscillation_off (Optional): The payload that represents the oscillation state. Default is “OFF”.
-
payload_low_speed (Optional): The payload that represents the low speed state. Default is “low”.
-
payload_medium_speed (Optional): The payload that represents the low speed state. Default is “med”.
-
payload_high_speed (Optional): The payload that represents the low speed state. Default is “high”.
+
speed_state_topic (Optional): The MQTT topic subscribed to receive speed state updates.
+
speed_command_topic (Optional): The MQTT topic to publish commands to change speed state.
+
payload_low_speed (Optional): The payload that represents the fan’s low speed.
+
payload_medium_speed (Optional): The payload that represents the fan’s medium speed.
+
payload_high_speed (Optional): The payload that represents the fan’s high speed.
+
speed_value_template (Optional): Defines a template to extract a value from the speed payload.
speeds array (Optional): Valid entries for the list are off, low, med, and high.
-Make sure that your topic match exact. some-topic/ and some-topic are different topics.
+Make sure that your topic is an exact match. some-topic/ and some-topic are different topics.
+
Examples
+
+
In this section you find some real life examples of how to use this fan.
+
+
Full configuration
+
+
The example below shows a full configuration for a MQTT fan.
diff --git a/components/fan.nest/index.html b/components/fan.nest/index.html
index 4ab814c50c..e3f305450c 100644
--- a/components/fan.nest/index.html
+++ b/components/fan.nest/index.html
@@ -145,9 +145,6 @@ You must have the Nest component configured to u
diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html
index 989f97e340..7b8ea1a2d0 100644
--- a/components/ffmpeg/index.html
+++ b/components/ffmpeg/index.html
@@ -201,9 +201,15 @@ You need the ffmpeg binary in your system
-This platform has been deprecated in favor of a “cover” platform and will be removed in the future. Please use the cover platform.
-
-
-
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:
-This platform has been deprecated in favor of a “cover” platform and will be removed in the future. Please use the cover platform.
-
-
-
The rpi_gpio garage door platform allows you to use a Raspberry Pi to control your Garage door.
-
-
It uses two pins on the Raspberry Pi.
-
-
-
The state_pin will detect if the door is closed, and
-
the relay_pin will trigger the door to open or close.
-
-
-
Although you do not need Andrews Hilliday’s software controller when you run Home Assistant, he has written clear instructions on how to hook your garage door & sensors up to your Raspberry Pi, which can be found here.
-
-
To enable Raspberry Pi Garage doors in your installation, add the following to your configuration.yaml file:
-This platform has been deprecated in favor of a “cover” platform and will be removed in the future. Please use the cover platform.
-
-
-
Wink garage door functionality is currently limited to view only. Wink garage doors will still show the current state of the door, but control has been disabled for third parties. If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control.
-
-
The following quote is from Wink.
-
-
-
As part of our agreement with Chamberlain, third-party access to control Chamberlain garage doors has been restricted. Please contact Chamberlain directly to inquire about permissions.
-
-
-
The Wink garage door platform allows you to control your Wink enabled garage door.
-
-
The requirement is that you have setup your Wink hub.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/components/graphite/index.html b/components/graphite/index.html
index be9d8cee7e..32dab0566c 100644
--- a/components/graphite/index.html
+++ b/components/graphite/index.html
@@ -160,6 +160,9 @@
diff --git a/components/history/index.html b/components/history/index.html
index f9ca46bb95..17931feadb 100644
--- a/components/history/index.html
+++ b/components/history/index.html
@@ -257,6 +257,9 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/components/homematic/index.html b/components/homematic/index.html
index 6b2fdcb86f..5b8292396d 100644
--- a/components/homematic/index.html
+++ b/components/homematic/index.html
@@ -228,9 +228,6 @@ The name depends on if you chose to resolve names or not. If not, it will be the
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
-
-
To get your Z-Wave hvac devices working with Home Assistant, follow the instructions for the general Z-Wave component and the HVAC component.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/components/index.html b/components/index.html
index 975a2f0e76..a09891df1e 100644
--- a/components/index.html
+++ b/components/index.html
@@ -111,11 +111,11 @@ Support for these components is provided by the Home Assistant community.
+Before trying to control your light through Home Assistant, you have to setup your bulb using Yeelight app. ( Android, IOS ).
+In the bulb property, you have to enable “Developer Mode”
+Determine your bulb ip (using router, software, ping …)
+
+
+
+Tests are only made with a YLDP03YL model. Because it’s the only hardware developer owns. If you have bugs with another kind of model, you could open an issue on Home Assitant Github
-
To get your Z-Wave garage doors working with Home Assistant, follow the instructions for the general Z-Wave component.
LiteJet is a centralized lighting system that predates most home automation technology. All lights and wall switches are wired to a central panel. This central panel has a serial port interface that allows a computer to control the system via LiteJet’s third party protocol.
+
+
Home Assistant integrates the LiteJet 3rd party protocol and allows you to get the status and control the connected lights.
+
+
After connecting the LiteJet’s RS232-2 port to your computer, add the following to your configuration.yaml:
Your LiteJet MCP should be configured for 19.2 K baud, 8 data bits, 1 stop bit, no parity, and to transmit a ‘CR’ after each response. These settings can be configured using the LiteJet programming software.
+
+
You can also configure the Home Assistant to ignore lights, scenes, and switches via their name. This is highly recommended since LiteJet has a fixed number of each of these and with most systems many will be unused.
+
+
litejet:
+
+
+
+
Configuration variables:
+
+
+
port (Required): The path to the serial port connected to the LiteJet.
+
exclude_names (Optional): A list of light or switch names that should be ignored.
+
include_switches (Optional): Cause entities to be created for all the LiteJet switches. Default is false. This can be useful when debugging your lighting as you can press/release switches remotely.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/lock.mqtt/index.html b/components/lock.mqtt/index.html
index 77b0d6a609..8035a0d8d5 100644
--- a/components/lock.mqtt/index.html
+++ b/components/lock.mqtt/index.html
@@ -204,18 +204,12 @@ Make sure that your topic match exact. some-topi
diff --git a/components/logbook/index.html b/components/logbook/index.html
index 9691d92e6f..d352e0ee8d 100644
--- a/components/logbook/index.html
+++ b/components/logbook/index.html
@@ -233,6 +233,9 @@ To exclude these entities just add them to the e
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index 53fdc53b26..4eeec1d5f3 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -196,6 +196,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 5017275fcd..5ff8a573cc 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.
diff --git a/components/media_player.mpchc/index.html b/components/media_player.mpchc/index.html
index 142647731a..20ab0c8847 100644
--- a/components/media_player.mpchc/index.html
+++ b/components/media_player.mpchc/index.html
@@ -156,6 +156,9 @@ The MPC-HC web interface is highly insecure, and allows remote clients full play
diff --git a/components/thermostat.honeywell/index.html b/components/media_player.philips_js/index.html
similarity index 55%
rename from components/thermostat.honeywell/index.html
rename to components/media_player.philips_js/index.html
index 470d6467f5..40d7e2389d 100644
--- a/components/thermostat.honeywell/index.html
+++ b/components/media_player.philips_js/index.html
@@ -7,26 +7,26 @@
- Honeywell Thermostat - Home Assistant
+ Philips TV - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,35 +84,29 @@
- Honeywell Thermostat
+ Philips TV
-
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
+
The philips_js platform allows you to control Philips TVs which expose the jointSPACE API. Instructions on how to activate the API and if your model is supported can be found here.
-
The honeywell thermostat platform let you control Honeywell Connected thermostats from Home Assistant.
+
To add your TV to your installation, add the following to your configuration.yaml file:
-
To set it up, add the following information to your configuration.yaml file:
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index 4460ba2c7e..d83b44bc09 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -174,6 +174,9 @@ If you add your model remember to remove these before adding them to the list.
Sets a timer that will turn off a speaker by tapering the volume down to 0 after a certain amount of time. Protip: If you set the sleep_time value to 0, then the speaker will immediately start tapering the volume down.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of entity_ids that will have their timers set. Must be a coordinator speaker.
+
+
+
sleep_time
+
no
+
Integer number of seconds that the speaker should wait until it starts tapering. Cannot exceed 86399 (one day).
+
+
+
+
+
Service sonos_clear_sleep_timer
+
+
Clear the sleep timer on a speaker, if one is set.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of entity_ids that will have their timers cleared. Must be a coordinator speaker.
diff --git a/components/thermostat.nest/index.html b/components/mochad/index.html
similarity index 58%
rename from components/thermostat.nest/index.html
rename to components/mochad/index.html
index 254a707d98..b32ae6ae79 100644
--- a/components/thermostat.nest/index.html
+++ b/components/mochad/index.html
@@ -7,26 +7,26 @@
- Nest Thermostat - Home Assistant
+ Mochad - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,30 +84,36 @@
- Nest Thermostat
+ Mochad
-
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
+
The mochad component is the main component to integrate all X10 platforms being controlled by mochad. Besides this component you will have to setup your X10 devices separately.
-
The nest thermostat platform let you control a thermostat from Nest.
+
To integrate your Mochad units with Home Assistant, add the following section to your configuration.yaml file:
-
To set it up, add the following information to your configuration.yaml file:
-
-
thermostat:
- platform:nest
+
# Example configuration.yaml entry
+mochad:
-
-
-
+
Configuration variables:
-
You must have the Nest component configured to use this sensor.
+
+
host (Optional): The host that mochad is running on. Defaults to localhost.
+
port (Optional): The port that mochad is running on. Defaults to 1099.
+
+
+
A full configuration sample could look like the one below:
+
+
# Example configuration.yaml entry
+mochad:
+ host:localhost
+ port:1099
+
diff --git a/components/mqtt/index.html b/components/mqtt/index.html
index 46bd2470a1..014102b0f1 100644
--- a/components/mqtt/index.html
+++ b/components/mqtt/index.html
@@ -428,9 +428,6 @@ Home Assistant will automatically load the correct certificate if you connect to
diff --git a/components/mysensors/index.html b/components/mysensors/index.html
index 96c5947405..45de21b3fb 100644
--- a/components/mysensors/index.html
+++ b/components/mysensors/index.html
@@ -336,9 +336,15 @@ The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway
diff --git a/components/netatmo/index.html b/components/netatmo/index.html
index 034fa738e8..cb7691cddb 100644
--- a/components/netatmo/index.html
+++ b/components/netatmo/index.html
@@ -209,9 +209,15 @@ The Home Assistant Netatmo platform has only be tested with the classic indoor,
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index 6474b354e7..946186ea82 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -202,6 +202,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
Google has a handy guide that goes into great detail about how to set up for pushing to Chrome. Once you have your GCM API Key and Sender ID in hand, plug them into your configuration as described above.
+
Create new project at https://console.cloud.google.com/home/dashboard
+Go to https://console.cloud.google.com/apis/credentials/domainverification and verify your domain
+After that, go to https://console.firebase.google.com and select import Google project, select the project you created
+Then, click the clogwheel on top left and select Project settings
+Select Cloud messaging tab
+if under server key is button Regenerate key, click that
Notification platform for Notifications for Android TV and Notifications for FireTV.
+The notifications are in the global scope of your Android TV device. They will be displayed regardless of which application is running.
+The In-App purchases only apply to the client for Android smartphones, so there isn’t any limit when pushing notifications from HASS.
+
+
To enable the notification platform, add the following to your configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
host (Required): IP address of the Android TV / FireTV device.
+
duration (Optional): The duration in seconds for which the notification will be displayed. Default is 5 seconds.
+
position (Optional): Has to be one of: bottom-right (default), bottom-left, top-right, top-left, center
+
color (Optional): Has to be one of: grey (default), black, indigo, green, red, cyan, teal, amber, pink
+
transparency (Optional): Has to be one of: 0%, 25% (default), 50%, 75%, 100%
+
interrupt (Optional): If set to true, 1, on etc., the notification is interactive and can be dismissed or selected to display more details.
+
+
+
The configuration will be used to configure the default values for the notification for the host specified by the IP. However, you can override most of the settings by passing them with the data-attribute when calling the service.
+This is a fully customized JSON you can use to test how the final notification will look like:
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index ef9d3f0b6f..c5e9d83f60 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -247,6 +247,9 @@ which need special attention. By default, the usage by external applications, es
-This platform has been deprecated in favor of a “cover” platform and will be removed in the future. Please use the cover platform.
-
-
-
A rollershutter platform that issues specific commands when it is moved up, down and stopped. This might very well become our most powerful platform as it allows anyone to integrate any type of rollershutter into Home Assistant that can be controlled from the command line, including calling other scripts!
-
-
To enable command_rollershutter in your installation, add the following to your configuration.yaml file:
-
-
# Example configuration.yaml entry
-rollershutter:
--platform:command_line
- rollershutters:
- Kitchen Rollershutter:
- upcmd:move_command up kitchen
- downcmd:move_command down kitchen
- stopcmd:move_command stop kitchen
- statecmd:state_command kitchen
- value_template:'{{value}}'
-
-
-
-
Configuration variables:
-
-
-
rollershutters (Required): The array that contains all command rollershutters.
-
-
entry (Required): Name of the command rollershutter. Multiple entries are possible.
-
-
upcmd (Required): The action to take for move up.
-
downcmd (Required): The action to take for move down.
-
stopcmd (Required): The action to take for stop.
-
statecmd (Optional): If given, this command will be run. Returning a result code 0 will indicate that the rollershutter is fully closed, returning a result code 100 will indicate that the rollershutter is fully open.
-
value_template (Optional - default: ‘{{ value }}’): If specified, statecmd will ignore the result code of the command but the template evaluating will indicate the position of the rollershutter.
-This platform has been deprecated in favor of a “cover” platform and will be removed in the future. Please use the cover platform.
-
-
-
The mqtt rollershutter platform enables the possibility to control an MQTT rollershutter. The device state will be updated only after receiving the a new state from state_topic. If these messages are published with RETAIN flag, the MQTT device will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state will be unknown.
-
-
There is a state attribute that stores the relative position of the device, where 0% means the device is closed and all other intermediate positions means the device is open.
-
-
To enable this platform, add the following lines to your configuration.yaml:
command_topic (Required): The MQTT topic to publish commands to control the rollershutter.
-
-
name (Optional): The name of the rollershutter. Default is ‘MQTT Rollershutter’.
-
state_topic (Optional): The MQTT topic subscribed to receive state updates. If not defined, the rollershutter will be stateless, that is, no information about current position or open/closed. If defined, the received payload must be a integer between 0 and 100, that represents the percentage for fully closed and fully open, respectively.
-
qos (Optional): The maximum QoS level of the state topic. Default is 0. This QoS will also be used to publishing messages.
-
payload_up (Optional): The payload to open the rollershutter. Default is “OPEN”.
-
payload_down (Optional): The payload to close the rollershutter. Default is “CLOSE”.
-
payload_stop (Optional): The payload to stop the rollershutter. Default is “STOP”.
-
value_template (Optional): Defines a template to extract a value from the payload.
Launch your homeassistant and go the website (e.g http://localhost:8123).
-Push your remote and your device should be added.
-
-
Once added it will show an ID (e.g 0b11000102ef9f210010f70) and you can verify that it works from the frontend.
-Then you should update your configuration to:
The RFXtrx433e is required for RFY support, however it does not support receive for the RFY protocol - as such devices cannot be automatically added. Instead, configure the device in the rfxmngr tool. Make a note of the assigned ID and Unit Code and then add a device to the configuration with the following id 071a0000[id][unit_code]. Eg, if the id was 0a0001, and the unit code was 01 then the fully qualified id would be 071a00000a000101.
devices (Required): A list of devices with their name to use in the frontend.
-
automatic_add (Optional): To enable the automatic addition of new roller shutters (Siemens/LightwaveRF only).
-
signal_repetitions (Optional): Because the rxftrx device sends its actions via radio and from most receivers it’s impossible to know if the signal was received or not. Therefore you can configure the roller shutter to try to send each signal repeatedly.
-
fire_event (Optional): Fires an event even if the state is the same as before. Can be used for automations.
diff --git a/components/sensor.bbox/index.html b/components/sensor.bbox/index.html
index 7d8b812690..091610a88f 100644
--- a/components/sensor.bbox/index.html
+++ b/components/sensor.bbox/index.html
@@ -201,6 +201,9 @@ Due to third party limitation, the sensors will only be available if Home Assist
diff --git a/components/rollershutter/index.html b/components/sensor.cups/index.html
similarity index 62%
rename from components/rollershutter/index.html
rename to components/sensor.cups/index.html
index 656785ad33..b3c1fa07a6 100644
--- a/components/rollershutter/index.html
+++ b/components/sensor.cups/index.html
@@ -7,26 +7,26 @@
- Rollershutters - Home Assistant
+ CUPS Sensor - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,17 +84,40 @@
- Rollershutters
+ CUPS Sensor
-
-This component has been deprecated in favor of the “cover” component and will be removed in the future. Please use cover.
+
The cups sensor platform is using the open source printing system CUPS to show details about your printers.
+
+
To set up the sensor the “Queue Name” of the printer is needed. The fastest way to get it, is to visit the CUPS webinterface at “http://[IP ADDRESS PRINT SERVER]:631” and go to “Printers”.
+
+
+
-
Home Assistant can give you an interface to control any rollershutters.
+
To enable the CUPS sensor, add the following lines to your configuration.yaml:
printers array (Required): List of printers to add.
+
+
+
+You will need to install the python3-dev or python3-devel and the development files for CUPS (libcups2-dev orcups-devel) package on your system manually (eg. sudo apt-get install python3-dev libcups2-dev or sudo dnf -y install python3-devel cups-devel) along with a compiler (gcc).
+
The currencylayer sensor will show you the current exchange rate from Currencylayer that provides realtime exchange rates for 170 currencies. The free account is limited to only USD as a base currency, allows 1000 requests per month, and updates every hour.
base (Optional): The symbol of the base currency. Defaults to USD.
+
quote (Required): The symbol(s) of the quote or target currencies.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.darksky/index.html b/components/sensor.darksky/index.html
index cb61215433..2177e2f1ff 100644
--- a/components/sensor.darksky/index.html
+++ b/components/sensor.darksky/index.html
@@ -211,6 +211,9 @@ Note: While the platform is called “darksky” the sensors will show up in Hom
diff --git a/components/sensor.fastdotcom/index.html b/components/sensor.fastdotcom/index.html
index 8a2baab62d..edb96aa46d 100644
--- a/components/sensor.fastdotcom/index.html
+++ b/components/sensor.fastdotcom/index.html
@@ -165,6 +165,9 @@ Currently fast.com only supports measuring download bandwidth. If you want to me
diff --git a/components/sensor.fritzbox_callmonitor/index.html b/components/sensor.fritzbox_callmonitor/index.html
index c9b52c914d..dc5291f83e 100644
--- a/components/sensor.fritzbox_callmonitor/index.html
+++ b/components/sensor.fritzbox_callmonitor/index.html
@@ -150,6 +150,9 @@ on TCP port 1012. It will assume the values idle
diff --git a/components/sensor.glances/index.html b/components/sensor.glances/index.html
index f62b73c76a..97dba937d3 100644
--- a/components/sensor.glances/index.html
+++ b/components/sensor.glances/index.html
@@ -199,6 +199,9 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/components/sensor.haveibeenpwned/index.html b/components/sensor.haveibeenpwned/index.html
index a4bb6f292b..f7f7207059 100644
--- a/components/sensor.haveibeenpwned/index.html
+++ b/components/sensor.haveibeenpwned/index.html
@@ -195,6 +195,9 @@ account has been breached as well as the added date of the breach data. This dat
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index 9855c8587d..93210efcf9 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -216,6 +216,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
The InfluxDB sensor allows you to use values from an InfluxDB database to populate a sensor state. This can be use to present statistic about home_assistant sensors if used with the influxdb history component. It can also be used with an external data source.
+
+
To configure this sensor, you need to define the sensor connection variables and a list of queries to your configuration.yaml file. A sensor will be created for each query:
+
+
# Example configuration.yaml entry
+sensor:
+ -platform:influxdb
+ queries:
+ -name:mean value of foo
+ where:'"name"=''foo'''
+ measurement:'"°C"'
+
+
+
+
Configuration variables for the server:
+
+
+
host (Optional): IP address of your database host, eg. 192.168.1.10. Defaults to localhost.
+
port (Optional): Port to use. Defaults to 8086.
+
username (Optional): The username of the database user.
+
password (Optional): The password for the database user account.
+
ssl (Optional): Use https instead of http to connect. Defaults to false.
+
verify_ssl (Optional): Verify SSL certificate for https request. Defaults to false.
+
queries array (Required): List of queries
+
+
name (Required): The name of the sensor.
+
unit_of_measurement (Optional): Defines the units of measurement of the sensor, if any.
+
measurement (Required): Defines the measurement name in InfluxDB (the from clause of the query).
+
where (Required): Defines the data selection clause (the where clause of the query).
+
value_template (Optional): Defines a template to extract a value from the payload.
+
database (Optional): Name of the database to use. Defaults to home_assistant.
+
group_function (Optional): The group function to be used. Defaults to mean.
+
field (Optional): The field name to select. Defaults to value.
+
+
+
+
+
Examples
+
+
Full configuration
+
+
The example configuration entry bellow create two request to your local InfluxDB instance, one to the database db1, the other to db2:
+
+
+
select last(value) as value from "°C" where "name" = "foo"
+
select min(tmp) as value from "%" where "entity_id" = ''salon'' and time > now() - 1h
diff --git a/components/sensor.moldindicator/index.html b/components/sensor.moldindicator/index.html
index e803ce495e..4524ef4895 100644
--- a/components/sensor.moldindicator/index.html
+++ b/components/sensor.moldindicator/index.html
@@ -196,6 +196,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 e89ae5194e..1b8e1f273a 100644
--- a/components/sensor.nest/index.html
+++ b/components/sensor.nest/index.html
@@ -171,9 +171,6 @@ You must have the Nest component configured to u
diff --git a/components/sensor.nest_weather/index.html b/components/sensor.nest_weather/index.html
index 2a717aca9d..f8a95b654f 100644
--- a/components/sensor.nest_weather/index.html
+++ b/components/sensor.nest_weather/index.html
@@ -161,6 +161,9 @@ You must have the Nest component configured to u
diff --git a/components/sensor.octoprint/index.html b/components/sensor.octoprint/index.html
index 2b5a4a18ff..dcbf9ddc2d 100644
--- a/components/sensor.octoprint/index.html
+++ b/components/sensor.octoprint/index.html
@@ -203,6 +203,9 @@ You must have the OctoPrint component confi
diff --git a/components/sensor.rfxtrx/index.html b/components/sensor.rfxtrx/index.html
index 499278cf0c..be52d78331 100644
--- a/components/sensor.rfxtrx/index.html
+++ b/components/sensor.rfxtrx/index.html
@@ -189,9 +189,6 @@ Then you should update your configuration to:
This synologydms sensor allows getting various statistics from your Synology NAS. Please note that using this sensor wakes up your synology if in hibernation mode.
+
+
To use the SynologyDSM sensor in your installation, add the following to your configuration.yaml file:
host (Required): The IP address of the Synology NAS to monitor
+
port (Optional): The port number on which the NAS is reachable. Defaults to 5000.
+
username (Required): An user to connect to the Synology NAS (a seperate account is adviced).
+
password (Required): The password of the user to connect to the Synology NAS.
+
volumes (Optional): Array of volumes to monitor. Defaults to all volumes.
+
disks (Optional): Array of disks to monitor. Defaults to all disks.
+
monitored_conditions (Required): Defines a template to extract a value from the payload.
+
+
cpu_other_load: Displays unspecified load in percentage.
+
cpu_user_load: Displays user load in percentage.
+
cpu_system_load: Displays system load in percentage.
+
cpu_total_load: Displays combined load in percentage.
+
cpu_1min_load: Displays maximum load in past minute.
+
cpu_5min_load: Displays maximum load in past 5 minutes.
+
cpu_15min_load: Displays maximum load in past 15 minutes.
+
memory_real_usage: Displays percentage of memory used.
+
memory_size: Displays total size of memory in MB.
+
memory_cached: Displays total size of cache in MB.
+
memory_available_swap: Displays total size of available swap in MB.
+
memory_available_real: Displays total size of memory used (based on real memory) in MB.
+
memory_total_swap: Displays total size of actual memory in MB.
+
memory_total_real: Displays total size of real memory in MB.
+
network_up: Displays total up speed of network interfaces (combines all interfaces).
+
network_down: Displays total down speed of network interfaces (combines all interfaces).
+
disk_name: Displays the name of the harddisk (creates a new entry for each disk).
+
disk_device: Displays the path of the harddisk (creates a new entry for each disk).
+
disk_smart_status: Displays the S.M.A.R.T status of the harddisk (creates a new entry for each disk).
+
disk_status: Displays the status of the harddisk (creates a new entry for each disk).
+
disk_exceed_bad_sector_thr: Displays true / false to indicate if the harddisk exceeded the maximum bad sector threshold (creates a new entry for each disk).
+
disk_below_remain_life_thr: Displays true / false to indicate if the harddisk dropped below the remain life threshold (creates a new entry for each disk).
+
disk_temp: Displays the temperature of the harddisk (creates a new entry for each disk, uses the unit_system to display in C or F).
+
volume_status: Displays the status of the volume (creates a new entry for each volume).
+
volume_device_type: Displays the volume type (RAID, etc) (creates a new entry for each volume).
+
volume_size_total: Displays the total size of the volume in GB’s (creates a new entry for each volume).
+
volume_size_used: Displays the used space on this volume in GB’s (creates a new entry for each volume).
+
volume_percentage_used: Displays the percentage used for this volume in GB’s (creates a new entry for each volume).
+
volume_disk_temp_avg: Displays the average temperature of all disks in the volume (creates a new entry for each volume).
+
volume_disk_temp_max: Displays the maximum temperature of all disks in the volume (creates a new entry for each volume).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.systemmonitor/index.html b/components/sensor.systemmonitor/index.html
index ea06209a55..612745afcf 100644
--- a/components/sensor.systemmonitor/index.html
+++ b/components/sensor.systemmonitor/index.html
@@ -246,6 +246,9 @@
diff --git a/components/sensor.temper/index.html b/components/sensor.temper/index.html
index c745d5424c..765999389c 100644
--- a/components/sensor.temper/index.html
+++ b/components/sensor.temper/index.html
@@ -185,6 +185,9 @@ The calculation follows the formula scale * sens
diff --git a/components/sensor.template/index.html b/components/sensor.template/index.html
index f925aa73ed..1c34b1eb5f 100644
--- a/components/sensor.template/index.html
+++ b/components/sensor.template/index.html
@@ -302,6 +302,9 @@ Please note the blank line to close the multi-line template.
diff --git a/components/sensor.yr/index.html b/components/sensor.yr/index.html
index 5dc3d72e20..d0edc08d24 100644
--- a/components/sensor.yr/index.html
+++ b/components/sensor.yr/index.html
@@ -182,6 +182,9 @@ weather forecast is delivered by the Norwegian Meteorological Institute and the
diff --git a/components/sensor.yweather/index.html b/components/sensor.yweather/index.html
index 19085d9e46..9c3255ddf4 100644
--- a/components/sensor.yweather/index.html
+++ b/components/sensor.yweather/index.html
@@ -177,6 +177,9 @@ Use of the Yahoo Weather API should not exceed reasonable request volume. Access
The ZoneMinder sensor platform let you monitor the current state of your zoneminder install including the number of events and the current state of the cameras.
+
The zoneminder sensor platform let you monitor the current state of your zoneminder install including the number of events and the current state of the cameras.
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index b5980e91ec..2d45fbd243 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -233,9 +233,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 6c759e8a19..2a67e9c608 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -174,9 +174,15 @@ Currently works using default https port only.
diff --git a/components/switch.knx/index.html b/components/switch.knx/index.html
index af909e34b8..19f5d44823 100644
--- a/components/switch.knx/index.html
+++ b/components/switch.knx/index.html
@@ -151,9 +151,6 @@ For switching actuators that are only controlled by a single group address and c
diff --git a/components/thermostat.eq3btsmart/index.html b/components/switch.mochad/index.html
similarity index 52%
rename from components/thermostat.eq3btsmart/index.html
rename to components/switch.mochad/index.html
index 4972404ffc..af7e8595da 100644
--- a/components/thermostat.eq3btsmart/index.html
+++ b/components/switch.mochad/index.html
@@ -7,26 +7,26 @@
- EQ3 Bluetooth Smart Thermostats - Home Assistant
+ Mochad Switch - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,65 +84,33 @@
- EQ3 Bluetooth Smart Thermostats
+ Mochad Switch
-
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
+
The mochad switch platform lets you control an X10 enabled switch device.
-
This platform allows you to integrate EQ3 Bluetooth Smart Thermostats.
+
To enable this sensor, you first have to set up the mochad component and then add the following to your configuration.yaml file:
-
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:
-
-
/usr/bin/bt-device -d CC-RT-BLE
-
-
-
-
to the start function of /etc/init.d/hass-daemon.
-
-
# Example configuration.yaml entry
-thermostat:
- platform:eq3btsmart
+
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 936ac78d60..67ad1c4a3f 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -200,9 +200,6 @@ Make sure that your topic match exact. some-topi
diff --git a/components/switch.neato/index.html b/components/switch.neato/index.html
index 7287d9b082..3732d0726e 100644
--- a/components/switch.neato/index.html
+++ b/components/switch.neato/index.html
@@ -174,9 +174,15 @@ The Home Assistant Neato platform has only be tested with a Botvac Connected. Th
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 3d568a30f9..24fc221e66 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -185,9 +185,15 @@ This component relies on raw TCP commands to PulseAudio. In order for PulseAudio
resource (Required): The resource or endpoint that contains the value.
name (Optional): Name of the REST switch.
-
body_on (Optional): The body that represents enabled state. Default is “ON”.
-
body_off (Optional):The body that represents disabled state. Default is “OFF”.
+
body_on (Optional): The body of the POST request that commands the switch to become enabled. Default is “ON”. This value can be a template, which is useful if the POST request needs to depend on the state of the system. For example, to enable remote-temperature-sensor tracking on a radio thermostat, one has to send the current value of the remote temperature sensor. On can achieve this using the template '{"rem_temp":}'.
+
body_off (Optional): The body of the POST request that commands the switch to become disabled. Default is “OFF”. This value can also be a template.
+
is_on_template (Optional): A template that determines the state of the switch from the value returned by the GET request on the resource url. This template should compute to a boolean (True or False). Default is equivalent to '{{ value.json == body_on }}'. This means that by default, the state of the switch is on if and only if the response to the GET request matches body_on.
@@ -188,9 +189,15 @@ 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 31d3dd115f..83d358a0ab 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -137,7 +137,7 @@ Then you should update your configuration to:
Go to home-assistant-IP:8123/dev-template
Use this code to generate a code:
-
0b11000bc0cfe0010f70
+
0b11000{{ range(0,700) | random | int }}bc0cfe0{{ range(0,10) | random | int }}010f70
@@ -268,9 +268,6 @@ Then you should update your configuration to:
diff --git a/components/switch.rpi_rf/index.html b/components/switch.rpi_rf/index.html
index 8f4f18e0fc..edab9b8f69 100644
--- a/components/switch.rpi_rf/index.html
+++ b/components/switch.rpi_rf/index.html
@@ -194,9 +194,15 @@ For more info see the PyPi module description: configuration.yaml file:
@@ -186,9 +187,15 @@
diff --git a/components/switch.wake_on_lan/index.html b/components/switch.wake_on_lan/index.html
index 045d061ff5..4dc856ec53 100644
--- a/components/switch.wake_on_lan/index.html
+++ b/components/switch.wake_on_lan/index.html
@@ -173,9 +173,15 @@ The WOL switch can only turn on your computer and monitor the state. There is no
diff --git a/components/tellduslive/index.html b/components/tellduslive/index.html
index b442ec453d..2d123d2b85 100644
--- a/components/tellduslive/index.html
+++ b/components/tellduslive/index.html
@@ -189,9 +189,15 @@ API requests to certain methods are limited to one request every 10 minutes.
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
-
-
Heat Control is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater under the hood. If the measured temperature is cooler then the target temperature, the heater will be turned on and turned off when required temperature is reached.
-
-
# Example configuration.yaml entry
-thermostat:
- platform:heat_control
- name:Study
- heater:switch.study_heater
- target_sensor:sensor.study_temperature
- min_temp:15
- max_temp:21
- target_temp:15
- min_cycle_duration:
- # At least one of these must be specified:
- days:2
- hours:1
- minutes:10
- seconds:5
- milliseconds:20
-
-
-
-
Configuration variables:
-
-
-
name (Required): Name of thermostat
-
heater (Required: entity_id for heater switch, must be a toggle device.
-
target_sensor (Required): entity_id for a temperature sensor, target_sensor.state must be temperature.
-
min_temp (Optional): Set minimum set point available (default: 7)
-
max_temp (Optional): Set maximum set point available (default: 35)
-
target_temp (Required): Set intital target temperature. Failure to set this variable will result in target temperature being set to null on startup.
-
ac_mode (Optional): Set the switch specified in the heater option to be treated as a cooling device instead of a heating device.
-
min_cycle_duration (Optional): Set a minimum amount of time that the switch specified in the heater option must be in it’s current state prior to being switched either off or on.
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
-
-
The heatmiser thermostat platform let you control Heatmiser DT/DT-E/PRT/PRT-E thermostats from Heatmiser. The module itself is currently setup to work over a RS232 -> RS485 converter, therefore it connects over IP.
-
-
Further work would be required to get this setup to connect over Wifi, but the HeatmiserV3 python module being used is a full implementation of the V3 protocol. If you would like to contribute to making this work over wifi, please contact @andylockran on github.
-
-
To set it up, add the following information to your configuration.yaml file:
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.
host (Required): Adress of your thermostat, eg. 192.168.1.32
-
username (Required): Username for the thermostat.
-
password (Required): Password for the thermostat.
-
-
-
The Proliphix NT Thermostat series are ethernet connected thermostats. They have a local HTTP interface that is based on get/set
-of OID values. A complete collection of the API is available in this API documentation.
host (Required): List of your Radiotherm thermostats
-
hold_temp (Required): Boolean to control if Home Assistant temperature adjustments hold (True) or are temporary (False).
-
-
-
Temperature settings from Home Assistant will be sent to thermostat and then hold at that temperature. Set to False if you set a thermostat schedule on the thermostat itself and just want Home Assistant to send temporary temperature changes.
-This platform has been deprecated in favor of a “climate” platform and will be removed in the future. Please use the climate platform.
-
-
-
To get your Z-Wave thermostat working with Home Assistant, follow the instructions for the general Z-Wave component.
-
-
-If your thermostat support fan modes or different operating modes, it should be considered a HVAC component, and will also be detected as one. Thermostat component does not support setting fan or operation mode. This is controlled via the HVAC component.
-
-If the thermostat support different operationg modes, you will get one thermostat entity for each mode. These can be hidden with settings using the customize setting in the configuration.yaml file.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/components/thermostat/index.html b/components/thingspeak/index.html
similarity index 58%
rename from components/thermostat/index.html
rename to components/thingspeak/index.html
index 388dd9d7d2..9ce51888a5 100644
--- a/components/thermostat/index.html
+++ b/components/thingspeak/index.html
@@ -7,26 +7,26 @@
- Thermostats - Home Assistant
+ ThingSpeak - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,21 +84,36 @@
- Thermostats
+ ThingSpeak
-
-This component has been deprecated in favor of the “climate” component and will be removed in the future. Please use climate.
-
+
The thingspeak components makes Home Assistant communicate with the ThingSpeak API.
+For now, it records exactly one entity at once, which is great for testing purposes. For long-time storage you should rely
+on the InfluxDB component.
-
Thermostats offer Home Assistant a peek into the current and target temperature in a house. Some thermostats will also offer an away mode that will lower use of heating/cooling.
+
You will have to create a new channel on ThingSpeak and grab your API key from your account page.
+
+
To setup the ThinkSpeak component in your installation, add the following to your configuration.yaml file:
api_key (Required): Your API key for http://openweathermap.org/.
+
latitude (Optional): Latitude of the location to display the weather. Defaults to the latitude in your your configuration.yaml file.
+
longitude (Optional): Longitude of the location to display the weather. Defaults to the longitude in your configuration.yaml file.
+
+
+
+This platform is an alternative to the openweathermap sensor.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/garage_door/index.html b/components/weather/index.html
similarity index 78%
rename from components/garage_door/index.html
rename to components/weather/index.html
index 4927584e43..9a78b2be58 100644
--- a/components/garage_door/index.html
+++ b/components/weather/index.html
@@ -7,26 +7,26 @@
- Garage door - Home Assistant
+ Weather - Home Assistant
-
+
-
+
-
+
-
+
-
+
-
-
+
+
@@ -84,17 +84,16 @@
- Garage Door
+ Weather
-
-This component has been deprecated in favor of the “cover” component and will be removed in the future. Please use cover.
-
+
The weather platforms are gathering meteorological information from web services and displays the conditions and other details about the weather at the given location.
+
+
Home Assistant currently supports free web services and such which requires a registration. Please check the sidebar for a full list of supported weather platforms.
-
Home Assistant can give you an interface to control any garage door.
diff --git a/components/wink/index.html b/components/wink/index.html
index dedeeb4b48..ab9c8f8a86 100644
--- a/components/wink/index.html
+++ b/components/wink/index.html
@@ -170,24 +170,21 @@ The Wink hub can only be accessed via the cloud. This means it requires an activ
diff --git a/components/zone/index.html b/components/zone/index.html
index 01ee9ee877..3dd4f432f0 100644
--- a/components/zone/index.html
+++ b/components/zone/index.html
@@ -138,11 +138,11 @@ Devices that are in the zone ‘Home’ will not appear on the
Icons
-
It is preferred to pick an icon to use for your zone. Pick any zone that you can find on materialdesignicons.com and prefix the name with mdi:. For example mdi:school, mdi:worker, mdi:home, mdi:cart, or mdi:castle.
+
It is preferred to pick an icon to use for your zone. Pick any icon that you can find on materialdesignicons.com and prefix the name with mdi:. For example mdi:school, mdi:worker, mdi:home, mdi:cart, or mdi:castle.
State
-
zoning is the state a zone has when it is configured. A zone doesn’t have another state, all configured zones are zoning all the time
+
zoning is the state a zone has when it is configured. A zone doesn’t have another state, all configured zones are zoning all the time.
Home Assistant is built from the ground up to be easily extensible using components. Home Assistant uses Python 3 for the backend and Polymer (Web components) for the frontend.
-
Home Assistant is open-source and MIT-licensed. Here are links to the source::
+
Home Assistant is open-source and MIT-licensed. Here are links to the source:
For those new to contributing to open source software, make sure you are familiar with all of the tools and concepts used in Home Assistant before you start.
There are a few very important rules to remember when writing automation templates:
+
+
+
You must use data_template in place of data when using templates in the data section of a service call.
+
You must use service_template in place of service when using templates in the service section of a service call.
+
You must surround single-line templates with double quotes (") or single quotes (').
+
It is advised that you prepare for undefined variables by using if ... is not none or the default filter, or both.
+
It is advised that when comparing numbers, you convert the number(s) to a float or an int by using the respective filter.
+
While the float and int filters do allow a default fallback value if the conversion is unsuccessful, they do not provide the ability to catch undefined variables.
+
+
+
Remembering these simple rules will help save you from many headaches and endless hours of frustration when using automation templates.
+
Available Trigger Data
The following tables show the available trigger data per platform.
Home Assistant will be able to automatically discover a bunch of devices and services available on your network if you have the discovery component enabled (which is by default).
+
Home Assistant will be able to automatically discover many devices and services available on your network if you have the discovery component enabled (the default setting).
Once you have a bunch of devices set up, it is time to organize them into groups.
+
Once you have several devices set up, it is time to organize them into groups.
Each group consists of a name and a list of entity IDs. Entity IDs can be retrieved from the web interface by using the Set State page in the Developer Tools ().
# Example configuration.yaml entry showing two styles
diff --git a/getting-started/index.html b/getting-started/index.html
index f9ce5b00c7..29507876c0 100644
--- a/getting-started/index.html
+++ b/getting-started/index.html
@@ -90,9 +90,9 @@
-
Below you can find the standard instructions. See the sidebar for installation instructions for specific platforms. If you’re running a Linux-based platform, we suggest you to follow the VirtualEnv Linux instructions to avoid using root.
+
Below you can find the standard instructions. See the sidebar for installation instructions for specific platforms. If you’re running a Linux-based platform, we suggest you follow the VirtualEnv Linux instructions to avoid using root.
-
Installing and running Home Assistant on your local machine is easy. Make sure you have Python 3.4 or higher installed and execute the following code in a console:
+
Installing and running Home Assistant on your local machine is easy. The only requirement is that you have Python installed. For Windows we require at least Python 3.5 and for other operating systems at least Python 3.4.2. Once installed, execute the following code in a console:
$ pip3 install homeassistant
$ hass --open-ui
diff --git a/getting-started/presence-detection/index.html b/getting-started/presence-detection/index.html
index 2a7e326f8e..c985fb2c7e 100644
--- a/getting-started/presence-detection/index.html
+++ b/getting-started/presence-detection/index.html
@@ -94,7 +94,7 @@
We care about privacy. Collected data is only stored in your instance of Home Assistant.
-
Presence detection detects if people are home, an important input for automation. The most important piece of information is to know if anyone is home. But knowing who is home or where they are will open a whole range of other automation options:
+
Presence detection detects if people are home, which is the most important input for automation. Knowing who is home or where they are will open a whole range of other automation options:
Send me a notification when my child arrives at school
@@ -110,12 +110,12 @@ Screenshot of Home Assistant showing a school, work and home zone and two people
The device tracker component offers presence detection for Home Assistant. It supports two different methods for presence detection: scan for connected devices on the local network and connect to third party service.
-
Scanning for connected devices is easy to setup. See the instructions for our supported routers or scan the network using nmap. This approach does have its limitations however, it will only be able to detect if a device is home. It also struggles with iPhones because they disconnect from WiFi if idle, marking them as not home when they actually are.
+
Scanning for connected devices is easy to setup. See the instructions for our supported routers or scan the network using nmap. This approach does have its limitations, however: it will only be able to detect if a device is home, and iPhones may show as not home inaccurately (as iPhones disconnect from WiFi if idle).
-
Home Assistant currently supports two third party services for presence detection: OwnTracks and Locative. OwnTracks is an app that you install on your iPhone or Android phone that allows you to push the location of your device to Home Assistant using an MQTT broker. An MQTT broker is an Internet of Things communication platform that you can freely host yourself or get a private instance for free in the cloud.
+
Home Assistant currently supports two third-party services for presence detection: OwnTracks and Locative. OwnTracks is an app that you install on your iPhone or Android phone that allows you to push the location of your device to Home Assistant using an MQTT broker. An MQTT broker is an Internet of Things communication platform that you can freely host yourself or get a private instance for free in the cloud.
-OwnTracks communicates directly with your MQTT broker, no data will pass through their servers.
+OwnTracks communicates directly with your MQTT broker; no data will pass through their servers.
Zones
diff --git a/images/screenshots/cups-sensor.png b/images/screenshots/cups-sensor.png
new file mode 100644
index 0000000000..b86af326c8
Binary files /dev/null and b/images/screenshots/cups-sensor.png differ
diff --git a/images/supported_brands/cups.png b/images/supported_brands/cups.png
new file mode 100644
index 0000000000..d3e37abc6a
Binary files /dev/null and b/images/supported_brands/cups.png differ
diff --git a/images/supported_brands/currencylayer.png b/images/supported_brands/currencylayer.png
new file mode 100644
index 0000000000..93fe98e6a3
Binary files /dev/null and b/images/supported_brands/currencylayer.png differ
diff --git a/images/supported_brands/emby.png b/images/supported_brands/emby.png
new file mode 100644
index 0000000000..a6c51ff23d
Binary files /dev/null and b/images/supported_brands/emby.png differ
diff --git a/images/supported_brands/garadget_logo.jpg b/images/supported_brands/garadget_logo.jpg
new file mode 100644
index 0000000000..6465496d03
Binary files /dev/null and b/images/supported_brands/garadget_logo.jpg differ
diff --git a/images/supported_brands/nfandroidtv.png b/images/supported_brands/nfandroidtv.png
new file mode 100644
index 0000000000..043aa2d5e5
Binary files /dev/null and b/images/supported_brands/nfandroidtv.png differ
diff --git a/images/supported_brands/philips.png b/images/supported_brands/philips.png
new file mode 100644
index 0000000000..5bb29fee30
Binary files /dev/null and b/images/supported_brands/philips.png differ
diff --git a/images/supported_brands/synologydsm.png b/images/supported_brands/synologydsm.png
new file mode 100644
index 0000000000..9c007a0876
Binary files /dev/null and b/images/supported_brands/synologydsm.png differ
diff --git a/images/supported_brands/yeelight.png b/images/supported_brands/yeelight.png
new file mode 100644
index 0000000000..27c7c9a86a
Binary files /dev/null and b/images/supported_brands/yeelight.png differ
diff --git a/index.html b/index.html
index 607edce1b0..cbda51c1f6 100644
--- a/index.html
+++ b/index.html
@@ -118,11 +118,11 @@ Home Assistant is an open-source home automation platform running on Python 3. T
Explaining the Updater
October 24, 2016
@@ -151,11 +156,6 @@ Home Assistant is an open-source home automation platform running on Python 3. T
October 22, 2016
After filling Home Assistant with all your precious home automation devices, you usually end up with a cluttered interface and lots of groups that are not interesting in your current context. What if you just want to show groups that are interesting now and hide the rest? That’s when group visibility comes to play.
+
+
Changing visibility of a group
+
+
To change visibility of a group, use the service group.set_visibility, pass the group name as entity_id and use visible to decide wheter the group should be shown or hidden.
+If a sensor belongs to only one group and that group is hidden, the sensor will “jump” to the top of the web interface. Add the sensor to an additional (visible) group if you do not want this to happen.
+
+
+
Automations
+
+
First you should decide under which circumstances a group should be visible or not. Depending on the complexity, you might have to write two automations: one that hides the group and another that shows it.
+
+
In this example, the group group.basement is hidden when the sun sets and shown again when it rises:
One of the most common uses cases are to show groups during certain times of day, maybe commuting information durig a work day morning or light switches when it is getting dark. The complexity of automations needed to make this happen will quickly get out of hands. So, one way to make the automations easier is to create a sensor that alters its state depending on time of day. One way of doing that is using a command_line sensor and a script:
+
+
#!/usr/bin/env python3
+# -*- coding: utf-8 -*-
+
+fromdatetimeimporttime,datetime
+
+defmk_occasion(name,start,end,days=None):
+ s=start.split(':')
+ e=end.split(':')
+ return{'name':name,
+ 'start':time(int(s[0]),int(s[1]),int(s[2])),
+ 'end':time(int(e[0]),int(e[1]),int(e[2])),
+ 'days':days}
+
+# Matching is done from top to bottom
+OCCASIONS=[
+ # More specific occasions
+ mk_occasion('work_morning','06:00:00','07:10:00',range(5)),
+
+ # General matching
+ mk_occasion('weekday','00:00:00','23:59:59',range(5)),
+ mk_occasion('weekend','00:00:00','23:59:59',[5,6])
+]
+
+defget_current_occasion(occasion_list,default_occasion='normal'):
+ now=datetime.now()
+ foroccasioninOCCASIONS:
+ ifoccasion['start']<=now.time()<=occasion['end']and \
+ (occasion['days']isNoneornow.weekday()inoccasion['days']):
+ returnoccasion['name']
+ returndefault_occasion
+
+if__name__=='__main__':
+ print(get_current_occasion(OCCASIONS))
+
+
+
+
This script will output “work_morning” from 06:00-07:10 during weekdays (monday-friday), “weekday” during all other time from monday-friday and “weekend” on saturdays and sundays. Adjust according to your needs. To create the sensor, just add it like this:
Our previously defined script will be called if sensor.occasion changes state OR when Home Assistant has started. The group group.work_sensors will be shown when sensor.occasion changes state to “work_morning” and hidden otherwise.
+
+
The complete example
+
+
group:
+ default_view:
+ entities:
+ -group.work_sensors
+
+ # Only visible when it's time to go to work
+ work_sensors:
+ name:Time to go to work
+ entities:
+ -sensor.something1
+ -sensor.something2
+
+sensor:
+ -platform:command_line
+ name:Occasion
+ command:"python3occasion.py"
+
+script:
+ group_visibility:
+ sequence:
+ -service:group.set_visibility
+ data_template:
+ entity_id:'{{entity_id}}'
+ visible:'{{is_state(cond,visible_state)}}'
+
+automation:
+ -alias:Work morning
+ trigger:
+ -platform:state
+ entity_id:sensor.occasion
+ -platform:event
+ event_type:homeassistant_start
+ action:
+ service:script.group_visibility
+ data:
+ entity_id:group.work_sensors
+ cond:sensor.occasion
+ visible_state:'work_morning'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/topics/index.html b/topics/index.html
index 33a7e7d6e3..e43f133cfa 100644
--- a/topics/index.html
+++ b/topics/index.html
@@ -101,6 +101,9 @@