diff --git a/atom.xml b/atom.xml index 63e367686b..9be679786d 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ @@ -13,6 +13,53 @@ Octopress + + <![CDATA[0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights ]]> + + 2015-11-16T20:27:00-08:00 + https://home-assistant.io/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported + 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:

+ +
+ 
homeassistant:
+  customize:
+    switch.ac:
+      icon: 'mdi:air-conditioner'
+
+
+
+ +

Breaking changes

+ +
    +
  • Any existing zone icon will have to be replaced with one from MaterialDesignIcons.com.
    • +
  • LimitlessLED light services require colors to be specified in RGB instead of XY.
    • +
+ +

Changes

+ +

+ + + +]]> + + <![CDATA[0.7.6: Amazon FireTV, Radiotherm thermostats]]> @@ -2302,22 +2349,6 @@ An initial version of voice control for Home Assistant has landed. The current i -]]> - - - - <![CDATA[New logo for Home Assistant]]> - - 2015-03-08T23:16:10-07:00 - https://home-assistant.io/blog/2015/03/08/new-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/blog/2014/12/18/website-launched/index.html b/blog/2014/12/18/website-launched/index.html index e78f2e4c27..4d53f84a70 100644 --- a/blog/2014/12/18/website-launched/index.html +++ b/blog/2014/12/18/website-launched/index.html @@ -187,6 +187,12 @@ 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 14812e027a..46be10f333 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 @@ -242,6 +242,12 @@ This article will try to explain how they all relate.

diff --git a/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html b/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html index 66ba6c743d..56cbe1763b 100644 --- a/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html +++ b/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/index.html @@ -226,6 +226,12 @@ api_key=ABCDEFGHJKLMNOPQRSTUVXYZ diff --git a/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html index 5ef8d8b796..1a5e55c8ae 100644 --- a/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html +++ b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html @@ -201,6 +201,12 @@ diff --git a/blog/2015/01/13/nest-in-da-house/index.html b/blog/2015/01/13/nest-in-da-house/index.html index d2886998fd..b9ffe5a94f 100644 --- a/blog/2015/01/13/nest-in-da-house/index.html +++ b/blog/2015/01/13/nest-in-da-house/index.html @@ -204,6 +204,12 @@ password=YOUR_PASSWORD diff --git a/blog/2015/01/24/release-notes/index.html b/blog/2015/01/24/release-notes/index.html index 8687bc5017..b6cb6d4f10 100644 --- a/blog/2015/01/24/release-notes/index.html +++ b/blog/2015/01/24/release-notes/index.html @@ -210,6 +210,12 @@ Home Assistant now supports --open-ui and --demo-mode 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 004c15efcb..472e52d6f6 100644 --- a/blog/2015/02/08/looking-at-the-past/index.html +++ b/blog/2015/02/08/looking-at-the-past/index.html @@ -220,6 +220,12 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D diff --git a/blog/2015/02/24/streaming-updates/index.html b/blog/2015/02/24/streaming-updates/index.html index 02f565cb82..fa23bcebe5 100644 --- a/blog/2015/02/24/streaming-updates/index.html +++ b/blog/2015/02/24/streaming-updates/index.html @@ -203,6 +203,12 @@ diff --git a/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html b/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html index b58f53a09a..8f67a043ce 100644 --- a/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html +++ b/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html @@ -193,6 +193,12 @@ diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html index 75e01a236c..d8a50d9595 100644 --- a/blog/2015/03/08/new-logo/index.html +++ b/blog/2015/03/08/new-logo/index.html @@ -194,6 +194,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 6374a60ae2..105981c182 100644 --- a/blog/2015/03/11/release-notes/index.html +++ b/blog/2015/03/11/release-notes/index.html @@ -233,6 +233,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 cb22ec7b07..f50eed4d6f 100644 --- a/blog/2015/03/22/release-notes/index.html +++ b/blog/2015/03/22/release-notes/index.html @@ -270,6 +270,12 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap diff --git a/blog/2015/04/25/release-notes/index.html b/blog/2015/04/25/release-notes/index.html index 1f830775cc..b59c461da0 100644 --- a/blog/2015/04/25/release-notes/index.html +++ b/blog/2015/04/25/release-notes/index.html @@ -281,6 +281,12 @@ diff --git a/blog/2015/05/09/utc-time-zone-awareness/index.html b/blog/2015/05/09/utc-time-zone-awareness/index.html index c097f10b13..91576aff15 100644 --- a/blog/2015/05/09/utc-time-zone-awareness/index.html +++ b/blog/2015/05/09/utc-time-zone-awareness/index.html @@ -216,6 +216,12 @@ diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html index 39cf15b364..f479736d33 100644 --- a/blog/2015/05/14/release-notes/index.html +++ b/blog/2015/05/14/release-notes/index.html @@ -308,6 +308,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 691d7f6213..d7b1a7eac3 100644 --- a/blog/2015/06/10/release-notes/index.html +++ b/blog/2015/06/10/release-notes/index.html @@ -361,6 +361,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 89c2f920c2..a39c753755 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 @@ -313,6 +313,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 d6cc3ed201..da212f1933 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 @@ -302,6 +302,12 @@ Support for Temper temperature sensors has been contributed by +
  • + 0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights +
    • + + +
  • 0.7.6: Amazon FireTV, Radiotherm thermostats
    • @@ -325,12 +331,6 @@ Support for Temper temperature sensors has been contributed by - Alarms, Sonos and iTunes now supported - - - 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 dc2d229c8e..605ccda4dc 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 @@ -212,6 +212,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 f56257f5df..be9b2d813c 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 @@ -321,6 +321,12 @@ diff --git a/blog/2015/08/31/version-7-revamped-ui-and-improved-distribution/index.html b/blog/2015/08/31/version-7-revamped-ui-and-improved-distribution/index.html index 8561f27837..a64ad4c347 100644 --- a/blog/2015/08/31/version-7-revamped-ui-and-improved-distribution/index.html +++ b/blog/2015/08/31/version-7-revamped-ui-and-improved-distribution/index.html @@ -299,6 +299,12 @@ diff --git a/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html b/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html index 69c57d2fb8..8c6c378109 100644 --- a/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html +++ b/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html @@ -502,6 +502,12 @@ PubSubClient client(ethClient); diff --git a/blog/2015/09/13/home-assistant-meets-ifttt/index.html b/blog/2015/09/13/home-assistant-meets-ifttt/index.html index 9eeb002e5d..afd4913036 100644 --- a/blog/2015/09/13/home-assistant-meets-ifttt/index.html +++ b/blog/2015/09/13/home-assistant-meets-ifttt/index.html @@ -361,6 +361,12 @@ 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 b364a768d6..a56a98555c 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 @@ -262,6 +262,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 e4e2a20426..5c54dd3a0d 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 @@ -241,6 +241,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 a22f05564d..53db51fc9a 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 @@ -217,6 +217,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 dd07f59b65..5462938c32 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 @@ -548,6 +548,12 @@ Adafruit_HDC1000 hdc = Adafruit_HDC1000(); diff --git a/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html b/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html index c14b348069..2f7b63a259 100644 --- a/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html +++ b/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html @@ -206,6 +206,12 @@ 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 452a22e7e3..45cff3d416 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 @@ -228,6 +228,12 @@ This makes more sense as most people run Home Assistant as a daemon

    diff --git a/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/index.html b/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/index.html new file mode 100644 index 0000000000..dcf47e9408 --- /dev/null +++ b/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/index.html @@ -0,0 +1,303 @@ + + + + + + + + + + + 0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + +
    + +

    0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights

    + + + +
    + + Paulus Schoutsen + 1 minute reading time + + + + + + Comments + +
    + +
    + + +

    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:

    + +
    + 
    homeassistant:
+  customize:
+    switch.ac:
+      icon: 'mdi:air-conditioner'
+
    +
    +
    + +

    Breaking changes

    + +
      +
    • Any existing zone icon will have to be replaced with one from MaterialDesignIcons.com.
      • +
    • LimitlessLED light services require colors to be specified in RGB instead of XY.
      • +
    + +

    Changes

    + +

    + + +
    + + +
    +

    Comments

    +
    +
    + + +
    + + + + +
    +
    + + + + + + + + + + \ No newline at end of file diff --git a/blog/archives/index.html b/blog/archives/index.html index 2cb732ceb9..b9aefc09fe 100644 --- a/blog/archives/index.html +++ b/blog/archives/index.html @@ -44,17 +44,11 @@ - Oct 26 + Nov 16 - 0.7.6: Amazon FireTV, Radiotherm thermostats - - - - - - ..."> + 0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights..."> @@ -143,6 +137,38 @@

    2015

    +
    +
    + +
    + +
    +
    +

    0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights

    + + + +
    +
    + +
    +
    + + +
    @@ -1141,6 +1167,12 @@ diff --git a/blog/categories/architecture/atom.xml b/blog/categories/architecture/atom.xml index 25b0ae99f6..45a2af4712 100644 --- a/blog/categories/architecture/atom.xml +++ b/blog/categories/architecture/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: architecture | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/architecture/index.html b/blog/categories/architecture/index.html index 3e993b9971..6da25cb727 100644 --- a/blog/categories/architecture/index.html +++ b/blog/categories/architecture/index.html @@ -199,6 +199,12 @@ diff --git a/blog/categories/branding/atom.xml b/blog/categories/branding/atom.xml index a91088d92b..34af931ace 100644 --- a/blog/categories/branding/atom.xml +++ b/blog/categories/branding/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: branding | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/branding/index.html b/blog/categories/branding/index.html index 2a462b9254..b8f6c521a1 100644 --- a/blog/categories/branding/index.html +++ b/blog/categories/branding/index.html @@ -199,6 +199,12 @@ diff --git a/blog/categories/component/atom.xml b/blog/categories/component/atom.xml index 2c5376384f..58d190f3ee 100644 --- a/blog/categories/component/atom.xml +++ b/blog/categories/component/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: component | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/component/index.html b/blog/categories/component/index.html index 5c9e3d04e6..7ee4435014 100644 --- a/blog/categories/component/index.html +++ b/blog/categories/component/index.html @@ -297,6 +297,12 @@ diff --git a/blog/categories/core/atom.xml b/blog/categories/core/atom.xml index c3b28afcd7..7ca46e59b8 100644 --- a/blog/categories/core/atom.xml +++ b/blog/categories/core/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: core | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/core/index.html b/blog/categories/core/index.html index 0fef523b18..445656f0aa 100644 --- a/blog/categories/core/index.html +++ b/blog/categories/core/index.html @@ -231,6 +231,12 @@ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 79f5dcb1ce..2248a6e517 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: esp8266 | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/index.html b/blog/categories/esp8266/index.html index 7d747a5e40..24e687652d 100644 --- a/blog/categories/esp8266/index.html +++ b/blog/categories/esp8266/index.html @@ -203,6 +203,12 @@ diff --git a/blog/categories/frontend/atom.xml b/blog/categories/frontend/atom.xml index 0b431bc2f1..c530d07386 100644 --- a/blog/categories/frontend/atom.xml +++ b/blog/categories/frontend/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: frontend | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/frontend/index.html b/blog/categories/frontend/index.html index 285685b45a..6b96047f4e 100644 --- a/blog/categories/frontend/index.html +++ b/blog/categories/frontend/index.html @@ -233,6 +233,12 @@ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index d7cdd2da72..213d64588f 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: how-to | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/index.html b/blog/categories/how-to/index.html index d83e201241..306c29ae10 100644 --- a/blog/categories/how-to/index.html +++ b/blog/categories/how-to/index.html @@ -303,6 +303,12 @@ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 64cc098795..5c6c45e69c 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: mqtt | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/index.html b/blog/categories/mqtt/index.html index 40b4cf4fcb..18c537c380 100644 --- a/blog/categories/mqtt/index.html +++ b/blog/categories/mqtt/index.html @@ -237,6 +237,12 @@ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index b28089df82..86e0414d3f 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: release-notes | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ @@ -13,6 +13,53 @@ Octopress + + <![CDATA[0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights ]]> + + 2015-11-16T20:27:00-08:00 + https://home-assistant.io/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported + 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:

    + +
    + 
    homeassistant:
+  customize:
+    switch.ac:
+      icon: 'mdi:air-conditioner'
+
    +
    +
    + +

    Breaking changes

    + +
      +
    • Any existing zone icon will have to be replaced with one from MaterialDesignIcons.com.
      • +
    • LimitlessLED light services require colors to be specified in RGB instead of XY.
      • +
    + +

    Changes

    + +

    + + + +]]>     +     + <![CDATA[0.7.6: Amazon FireTV, Radiotherm thermostats]]> @@ -190,187 +237,6 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge

    Verisure Alarms
    We now support arming and disarming your verisure alarm from within Home Assistant thanks to added support by @persandstrom.

    -]]> -     - - - <![CDATA[Home Assistant meets IFTTT]]> - - 2015-09-13T09:28:00-07:00 - https://home-assistant.io/blog/2015/09/13/home-assistant-meets-ifttt - Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.

    - -

    It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.

    - -

    - -

    - -

    Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.

    - - - -

    In each of the following examples, make sure to replace the XXX in the url with your correct host address and api password.

    - -

    Turn off irregation system when not needed

    - -

    - -

    - -

    Maker channel setup:

    - - - - - - - - - - - - - - - - - - - - - - - - - - -
    FieldValue
    URLhttp://xxx.xxx.xxx.xxx:8123/api/services/switch/turn_off?api_password=xxxxxxxx
    METHODPOST
    CONTENT TYPEapplication/json
    BODY{ “entity_id”: “switch.irrigation” }
    - -

    Tweet when important events happen

    - -

    - -

    - -

    This will tweet a message when an MQTT message is received that the smoke alarm has been triggered. Setup Maker channel with event name HA_FIRE_ALARM and Twitter channel to tweet the message in value1.

    - -
    - 
    # Configuration.yaml entry
-automation:
-- alias: Post a tweet when fire alarm is triggered
-  trigger:
-    platform: mqtt
-    mqtt_topic: home/alarm/fire
-    mqtt_payload: 'on'
-
-  action:
-    service: ifttt.trigger
-    data: {"event":"HA_FIRE_ALARM", "value1":"The fire alarm just triggered!"}
-
    -
    -
    - -

    Turn on lights when I get home

    - -

    - -

    - -

    Maker channel setup:

    - - - - - - - - - - - - - - - - - - - - - - - - - - -
    FieldValue
    URLhttp://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
    METHODPOST
    CONTENT TYPEapplication/json
    BODY{ “entity_id”: “light.kitchen” }
    - -

    Flash lights when a new PR comes in for Home Assistant

    - -

    - -

    - -

    Maker channel setup:

    - - - - - - - - - - - - - - - - - - - - - - - - - - -
    FieldValue
    URLhttp://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
    METHODPOST
    CONTENT TYPEapplication/json
    BODY{ “entity_id”: “group.all_lights”, “flash”:”yes” }
    - -

    Fire events when pressing the DO button

    - -

    - -

    - -

    Maker channel setup:

    - - - - - - - - - - - - - - - - - - - - - - -
    FieldValue
    URLhttp://xxx.xxx.xxx.xxx:8123/api/events/do_button_pressed?api_password=xxxxxxxx
    METHODPOST
    CONTENT TYPEapplication/json
    ]]>         diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html index cb89561836..59f570c3df 100644 --- a/blog/categories/release-notes/index.html +++ b/blog/categories/release-notes/index.html @@ -110,6 +110,38 @@

    2015

    + + + +
    @@ -617,6 +649,12 @@ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index b6b3ef9914..d9d401a5c5 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: user-stories | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/index.html b/blog/categories/user-stories/index.html index 4cd9eb05aa..0017f3f42b 100644 --- a/blog/categories/user-stories/index.html +++ b/blog/categories/user-stories/index.html @@ -231,6 +231,12 @@ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 37faa9930b..1577f05225 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: website | Home Assistant]]> - 2015-10-30T22:13:50-07:00 + 2015-11-16T21:44:43-08:00 https://home-assistant.io/ diff --git a/blog/categories/website/index.html b/blog/categories/website/index.html index 89010b1923..eccb29b824 100644 --- a/blog/categories/website/index.html +++ b/blog/categories/website/index.html @@ -199,6 +199,12 @@ diff --git a/blog/index.html b/blog/index.html index f4957a3bf0..7a22287088 100644 --- a/blog/index.html +++ b/blog/index.html @@ -27,21 +27,18 @@ - 0.7.6: Amazon FireTV, Radiotherm thermostats + 0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights - October 26, 2015 + November 16, 2015 Paulus Schoutsen - two minutes reading time + 1 minute reading time - - - - releas..."> + ..."> @@ -114,6 +111,85 @@ +
    +
    + +

    + 0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights +

    + + + +
    + + Paulus Schoutsen + 1 minute reading time + + + + + + Comments + +
    + +
    + + +
    +

    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:

    + +
    + 
    homeassistant:
+  customize:
+    switch.ac:
+      icon: 'mdi:air-conditioner'
+
    +
    +
    + +

    Breaking changes

    + +
      +
    • Any existing zone icon will have to be replaced with one from MaterialDesignIcons.com.
      • +
    • LimitlessLED light services require colors to be specified in RGB instead of XY.
      • +
    + +

    Changes

    + +

    + + + + + +
    +
    +
    +
    @@ -651,63 +727,6 @@ Inspried by a fea
    -
    -
    - -

    - Laundry Automation: insight and notifications -

    - - - -
    - - Paulus Schoutsen - four minutes reading time - - - - - - Comments - -
    - -
    - - -
    -

    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.

    - -

    - - - - Graph showing the accelerometer data -

    - - - - Read on → - -
    -
    -
    - -
    -
    -
    - -
    -
    - -

    - New logo for Home Assistant -

    - - - -
    - - Paulus Schoutsen - less than one minute reading time - - - - - - Comments - -
    - -
    - - -
    -

    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/blog/posts/3/index.html b/blog/posts/3/index.html index e018996c8c..e2fa9be785 100644 --- a/blog/posts/3/index.html +++ b/blog/posts/3/index.html @@ -27,23 +27,23 @@ - Home Assistant moving to YAML + New logo for Home Assistant - March 1, 2015 - Theodor Lindquist + March 8, 2015 + Paulus Schoutsen less than one minute reading time - core + branding - ..."> + ..."> @@ -116,6 +116,54 @@ +
    +
    + +

    + New logo for Home Assistant +

    + + + +
    + + Paulus Schoutsen + less than one minute reading time + + + + + + Comments + +
    + +
    + + +
    +

    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/alarm_control_panel.mqtt/index.html b/components/alarm_control_panel.mqtt/index.html index bb6a341b80..28a6a565eb 100644 --- a/components/alarm_control_panel.mqtt/index.html +++ b/components/alarm_control_panel.mqtt/index.html @@ -161,6 +161,9 @@
  • MQTT device tracker
    • +
  • + MQTT light +
  • MQTT sensor
    • diff --git a/components/browser/index.html b/components/browser/index.html index 40444f60b1..68a81e6000 100644 --- a/components/browser/index.html +++ b/components/browser/index.html @@ -164,6 +164,12 @@
  • Introduction
    • +
  • + Logger +
    • +
  • + Updater +
    • diff --git a/components/camera.foscam/index.html b/components/camera.foscam/index.html index c1aa452322..f46abf2bc1 100644 --- a/components/camera.foscam/index.html +++ b/components/camera.foscam/index.html @@ -144,17 +144,23 @@
    This is a platform for - the component. + the Camera component.

    Category Camera

      +
    • + Camera +
    • Foscam IP camera
    • Generic IP Camera
      • +
    • + Generic MJPEG IP Camera +
    • Hikvision camera
      • diff --git a/components/camera.generic/index.html b/components/camera.generic/index.html index b72cf49b7f..b2459ecf7e 100644 --- a/components/camera.generic/index.html +++ b/components/camera.generic/index.html @@ -150,17 +150,23 @@
    This is a platform for - the component. + the Camera component.

    Category Camera

    diff --git a/components/conversation/index.html b/components/conversation/index.html index 3e59efabd2..4b8929469b 100644 --- a/components/conversation/index.html +++ b/components/conversation/index.html @@ -151,6 +151,12 @@
  • Introduction
    • +
  • + Logger +
    • +
  • + Updater +
    • diff --git a/components/device_tracker.mqtt/index.html b/components/device_tracker.mqtt/index.html index dd5825034b..9f733747ea 100644 --- a/components/device_tracker.mqtt/index.html +++ b/components/device_tracker.mqtt/index.html @@ -149,6 +149,9 @@
  • MQTT Alarm Control Panel
    • +
  • + MQTT light +
  • MQTT sensor
    • diff --git a/components/device_tracker.ubus/index.html b/components/device_tracker.ubus/index.html index ac72bcea2c..68b5a1d9f3 100644 --- a/components/device_tracker.ubus/index.html +++ b/components/device_tracker.ubus/index.html @@ -102,7 +102,7 @@

    This is one of the two ways we support OpenWRT. If you encounter problems, try luci.

    -

    This is a presence detection scanner for OpenWRT using ubus.

    +

    This is a presence detection scanner for OpenWRT using ubus.

    Before this scanner can be used you have to install the ubus RPC package on OpenWRT:

    @@ -131,7 +131,24 @@ -

    After this is done, configure Home Assistant as follows:

    +

    Restart the services.

    + +
    + 
    # /etc/init.d/rpcd restart && /etc/init.d/uhttpd restart
+
    +
    +
    + +

    Check if the file namespaces is registered with the RPC server.

    + +
    + 
    # ubus list | grep file
+file
+
    +
    +
    + +

    After this is done, add the following to your configuration.yaml file:

    # Example configuration.yaml entry
@@ -147,9 +164,9 @@
 
    Configuration variables:
    
 
 
      
-  
    • host (Required): The IP address of your router, e.g. 192.168.1.1.
      • 
-  
    • username (Required): The username of an user with administrative privileges, usually admin.
      • 
-  
    • password (Required): The password for your given admin account.
      • 
+  
    • host (Required): The IP address of your router, eg. 192.168.1.1.
      • 
+  
    • username (Required): The username of an user with administrative privileges, usually root.
      • 
+  
    • password (Required): The password for your given account.
      • 
 
    
 
 
    See the device tracker component page for instructions how to configure the people to be tracked.
    
diff --git a/components/discovery/index.html b/components/discovery/index.html
index ac3b02dff8..0bc402ceb6 100644
--- a/components/discovery/index.html
+++ b/components/discovery/index.html
@@ -161,6 +161,12 @@ There is currently a Category Camera
    diff --git a/components/light.blinksticklight/index.html b/components/light.blinksticklight/index.html index e6a2ce5c47..b1d4bce1eb 100644 --- a/components/light.blinksticklight/index.html +++ b/components/light.blinksticklight/index.html @@ -151,6 +151,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -166,6 +169,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.hue/index.html b/components/light.hue/index.html index 40be3facb1..9323c2e6f1 100644 --- a/components/light.hue/index.html +++ b/components/light.hue/index.html @@ -142,6 +142,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -157,6 +160,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.hyperion/index.html b/components/light.hyperion/index.html index 5e0d2973aa..481c846087 100644 --- a/components/light.hyperion/index.html +++ b/components/light.hyperion/index.html @@ -100,7 +100,7 @@
    -

    This platform allows you to integrate your Hyperion into Home Assistant.

    +

    This platform allows you to integrate your Hyperion into Home Assistant.

    # Example configuration.yaml entry
@@ -142,6 +142,9 @@
         
  • 
             LimitlessLED
         
    • 
+        
  • 
+            MQTT light
+        
    • 
         
  • 
             Philips Hue
         
    • 
@@ -157,6 +160,9 @@
         
  • 
             Wink light
         
    • 
+        
  • 
+            Z-Wave light
+        
    •
    diff --git a/components/light.limitlessled/index.html b/components/light.limitlessled/index.html index a6bbbcd965..e8d2bdbc86 100644 --- a/components/light.limitlessled/index.html +++ b/components/light.limitlessled/index.html @@ -100,7 +100,7 @@
    -

    The limitlessled can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight or iLight.

    +

    The limitlessled platform can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight or iLight.

    To add limitlessled to your installation, add the following to your configuration.yaml file:

    @@ -153,6 +153,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -168,6 +171,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.mqtt/index.html b/components/light.mqtt/index.html new file mode 100644 index 0000000000..2001e02894 --- /dev/null +++ b/components/light.mqtt/index.html @@ -0,0 +1,275 @@ + + + + + + + + + + + MQTT light - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    +
    +

    + MQTT light +

    +
    +
    + +

    The mqtt light platform let you control your MQTT enabled light.

    + +

    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 light will work in optimistic mode. In this mode, the light will immediately change state after every command. Otherwise, the light 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 light operation.

    + +

    To enable a light with brightness and RGB support in your installation, add the following to your configuration.yaml file:

    + +
    + 
    # Example configuration.yml entry
+light:
+  platform: mqtt
+  name: "Office Light RGB"
+  state_topic: "office/rgb1/light/status"
+  command_topic: "office/rgb1/light/switch"
+  brightness_state_topic: "office/rgb1/brightness/status"
+  brightness_command_topic: "office/rgb1/brightness/set"
+  rgb_state_topic: "office/rgb1/rgb/status"
+  rgb_command_topic: "office/rgb1/rgb/set"
+  qos: 0
+  payload_on: "ON"
+  payload_off: "OFF"
+  optimistic: false
+
    +
    +
    + +

    To enable a light with brightness (no RGB version) in your installation, add the following to your configuration.yaml file:

    + +
    + 
    # Example configuration.yml entry
+light:
+  platform: mqtt
+  name: "Office light"
+  state_topic: "office/rgb1/light/status"
+  command_topic: "office/rgb1/light/switch"
+  qos: 0
+  payload_on: "ON"
+  payload_off: "OFF"
+  optimistic: false
+
    +
    +
    + +

    Configuration variables:

    + +
      +
    • name (Optional): The name of the switch. Default is ‘MQTT Switch’.
      • +
    • state_topic (Optional): The MQTT topic subscribed to receive state updates.
      • +
    • command_topic (Required): The MQTT topic to publish commands to change the switch state.
      • +
    • brightness_state_topic (Optional): The MQTT topic subscribed to receive brightness state updates.
      • +
    • brightness_command_topic (Optional): The MQTT topic to publish commands to change the light’s brightness.
      • +
    • rgb_state_topic (Optional): The MQTT topic subscribed to receive RGB state updates.
      • +
    • rgb_command_topic (Optional): The MQTT topic to publish commands to change the light’s RGB state.
      • +
    • qos (Optional): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
      • +
    • payload_on (Optional): The payload that represents enabled state. Default is “ON”.
      • +
    • payload_off (Optional): The payload that represents disabled state. Default is “OFF”.
      • +
    • optimistic (Optional): Flag that defines if switch works in optimistic mode. Default is true if no state topic defined, else false.
      • +
    + +

    + Make sure that your topics match exact. some-topic/ and some-topic are different topics. +

    + + +
    + + +
    + + + + +
    +
    + + + + + + + + + \ No newline at end of file diff --git a/components/light.rfxtrx/index.html b/components/light.rfxtrx/index.html index fa67d1bb48..b1ed2a79d6 100644 --- a/components/light.rfxtrx/index.html +++ b/components/light.rfxtrx/index.html @@ -167,6 +167,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -182,6 +185,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.tellstick/index.html b/components/light.tellstick/index.html index 3354be5e68..b110f68af4 100644 --- a/components/light.tellstick/index.html +++ b/components/light.tellstick/index.html @@ -157,6 +157,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -172,6 +175,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.vera/index.html b/components/light.vera/index.html index e6b2e68abc..d9fe093d18 100644 --- a/components/light.vera/index.html +++ b/components/light.vera/index.html @@ -177,6 +177,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -192,6 +195,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.wink/index.html b/components/light.wink/index.html index d708dcc7b5..5fe60d097d 100644 --- a/components/light.wink/index.html +++ b/components/light.wink/index.html @@ -148,6 +148,9 @@
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -163,6 +166,9 @@
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/light.zwave/index.html b/components/light.zwave/index.html new file mode 100644 index 0000000000..8e4d58e182 --- /dev/null +++ b/components/light.zwave/index.html @@ -0,0 +1,204 @@ + + + + + + + + + + + Z-Wave light - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    +
    +

    + Z-Wave light +

    +
    +
    + +

    To get your Z-Wave lights working with Home Assistant, follow the instructions for the general Z-Wave component.

    + +
    + + +
    + + + + +
    +
    + + + + + + + + + \ No newline at end of file diff --git a/components/light/index.html b/components/light/index.html index 75ef64a185..5b28265aa0 100644 --- a/components/light/index.html +++ b/components/light/index.html @@ -104,26 +104,22 @@

    It has 4 built-in light profiles which you’re able to extend by putting a light_profiles.csv file in your config dir.

    -

    It supports the following platforms:

    - - -

    Preferred way to setup the Philips Hue platform is through the the discovery component. For the Wink light platform enable the wink component.

    If you want to enable the light component directly, add the following lines to your configuration.yaml:

    -
    light:
-  platform: hue
-
    +
    + 
    light:
+  platform: hue
+
    +
    +

    The light component supports multiple entries in configuration.yaml by appending a sequential number to the section: light 2:, light 3: etc.

    -

    Service light.turn_on

    +

    Service light.turn_on

    Turns one light on or multiple lights on using groups.

    @@ -139,32 +135,37 @@ The light component supports multiple entries in configuration.yaml entity_id no - Only act on specified lights. Else targets all. + String or list of strings that point at entity_ids of lights. Else targets all. transition yes - Seconds to take to switch to new state. *not supported by Wink + Integer that represents the time the light should take to transition to the new state. *not supported by Wink profile yes - Which light profile to use. + String with the name of one of the built-in profiles (relax, energize, concentrate, reading) or one of the custom profiles defined in light_profiles.csv in the current working directory. Light profiles define a xy color and a brightness. If a profile is given and a brightness or xy color then the profile values will be overwritten. xy_color yes - Two comma seperated floats that represent the color in XY + A list containing two floats representing the xy color you want the light to be. Two comma seperated floats that represent the color in XY. rgb_color yes - Three comma seperated integers that represent the color in RGB + A list containing three integers representing the xy color you want the light to be. Three comma seperated integers that represent the color in RGB + + + color_temp + yes + An INT in mireds represending the color temperature you want the light to be. brightness yes - Integer between 0 and 255 for how bright the color should be + Integer between 0 and 255 for how bright the color should be. flash @@ -174,7 +175,7 @@ The light component supports multiple entries in configuration.yaml -

    Service light.turn_off

    +

    Service light.turn_off

    Turns one or multiple lights off.

    @@ -190,11 +191,17 @@ The light component supports multiple entries in configuration.yaml entity_id no - Only act on specified lights. Else targets all. + String or list of strings that point at entity_ids of lights. Else targets all. + + + transition + no + Integer that represents the time the light should take to transition to the new state. +
    @@ -219,6 +226,9 @@ The light component supports multiple entries in configuration.yaml
  • LimitlessLED
    • +
  • + MQTT light +
  • Philips Hue
    • @@ -234,6 +244,9 @@ The light component supports multiple entries in configuration.yaml
  • Wink light
    • +
  • + Z-Wave light +
    • diff --git a/components/logger/index.html b/components/logger/index.html new file mode 100644 index 0000000000..8b3d889ceb --- /dev/null +++ b/components/logger/index.html @@ -0,0 +1,223 @@ + + + + + + + + + + + Logger - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    +
    +

    + Logger +

    +
    +
    + +

    The logger component let one define the level of logging activities in Home Assistant.

    + +

    To enable the logger in your installation, add the following to your configuration.yaml file:

    + +

    By default log all messages and ignore log event lowest than critical for custom omponents.

    + +
    + 
    # Example configuration.yaml entry
+logger:
+  default: info
+  logs:
+    homeassistant.components.device_tracker: critical
+    homeassistant.components.camera: critical
+
    +
    +
    + +

    By default ignore all messages lowest than critical and log event for custom components.

    + +
    + 
    # Example configuration.yaml entry
+logger:
+  default: critical
+  logs:
+    homeassistant.components: info
+    homeassistant.components.rfxtrx: debug
+    homeassistant.components.device_tracker: critical
+    homeassistant.components.camera: critical
+
    +
    +
    + +

    Possible log severities are:

    + +
      +
    • citical
      • +
    • fatal
      • +
    • error
      • +
    • warning
      • +
    • warn
      • +
    • info
      • +
    • debug
      • +
    • notset
      • +
    + + +
    + + +
    + + + + +
    +
    + + + + + + + + + \ No newline at end of file diff --git a/components/media_player/index.html b/components/media_player/index.html index 7125edab91..265391d0a3 100644 --- a/components/media_player/index.html +++ b/components/media_player/index.html @@ -102,9 +102,9 @@

    Interacts with media players on your network. Please check the sidebar for a full list of supported devices.

    -

    Services

    +

    Services

    -

    Media control services

    +

    Media control services

    Available services: turn_off, volume_up, volume_down, media_play_pause, media_play, media_pause, media_next_track

    @@ -124,11 +124,12 @@
    -

    Media play services

    +

    Media play services

    There are three services to start playing YouTube video’s on the media player.

    -

    Service media_player/play_youtube_video

    +

    Service media_player/play_youtube_video

    +

    Service to start playing a YouTube video on the media player.

    @@ -153,7 +154,8 @@
    -

    Service media_player/start_fireplace and media_player/start_epic_sax

    +

    Service media_player/start_fireplace and media_player/start_epic_sax

    +

    Will either start a fireplace or Epic Sax Guy 10h on the media player.

    diff --git a/components/mqtt/index.html b/components/mqtt/index.html index 2927025b58..22c517f58f 100644 --- a/components/mqtt/index.html +++ b/components/mqtt/index.html @@ -275,6 +275,9 @@ Home Assistant will automatically load the correct certificate if you connect to
  • MQTT device tracker
    • +
  • + MQTT light +
  • MQTT sensor
    • diff --git a/components/notify.file/index.html b/components/notify.file/index.html index a47383e0fe..02228511f2 100644 --- a/components/notify.file/index.html +++ b/components/notify.file/index.html @@ -163,6 +163,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.instapush/index.html b/components/notify.instapush/index.html index 0fdb1f0037..76495de2f7 100644 --- a/components/notify.instapush/index.html +++ b/components/notify.instapush/index.html @@ -184,6 +184,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.nma/index.html b/components/notify.nma/index.html index f793a58b99..746446dff3 100644 --- a/components/notify.nma/index.html +++ b/components/notify.nma/index.html @@ -164,6 +164,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.pushbullet/index.html b/components/notify.pushbullet/index.html index 2f45d027d7..368160f1ec 100644 --- a/components/notify.pushbullet/index.html +++ b/components/notify.pushbullet/index.html @@ -100,16 +100,17 @@
    -

    Home Assistant currently supports the awesome PushBullet, a free service to send information between your phones, browsers and friends.

    +

    PushBullet is a free service to send information between your phones, browsers and friends.

    -

    To add PushBullet to your installation, add the following to your configuration.yaml file:

    +

    Configuration

    # Example configuration.yaml entry
 notify:
-  name: NOTIFIER_NAME
   platform: pushbullet
   api_key: YOUR_API_KEY
+  # Optional
+  name: NOTIFIER_NAME
    @@ -117,11 +118,65 @@

    Configuration variables:

    -

    For more automation examples, see the getting started with automation page.

    +

    Usage

    + +

    PushBullet is a notify platform and thus can be controlled by calling the notify service as described here. An optional target parameter can be given to PushBullet to specify one or many account’s devices, contacts or channels to notify.

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    TypePrefixSuffixExample
    All devicesdevice–device
    Devicedevice/Device nicknamedevice/iphone
    Contactcontact/Contact e-mail (lowercase)contact/email@example.com
    Channelchannel/Channel tagchannel/my_home
    + +

    Example service payload

    + +
    + 
    {
+  "message": "A message for many people",
+  "target": [
+    "device",
+    "contact/hello@example.com",
+    "channel/my_home"
+  ]
+}
+
    +
    +
    @@ -162,6 +217,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.pushetta/index.html b/components/notify.pushetta/index.html new file mode 100644 index 0000000000..2fab374bbb --- /dev/null +++ b/components/notify.pushetta/index.html @@ -0,0 +1,232 @@ + + + + + + + + + + + Pushetta - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    +
    +

    + Pushetta +

    +
    +
    + +

    The pushetta platform uses Pushetta to delivery notifications from Home Assistant to your devices.

    + +

    To enable Pushetta notifications in your installation, add the following to your configuration.yaml file:

    + +
    + 
    # Example configuration.yaml entry
+notify:
+  name: NOTIFIER_NAME
+  platform: pushetta
+  api_key: YOUR_API_KEY
+  channel_name: YOUR_CHANNEL_NAME
+
    +
    +
    + +

    Configuration variables:

    + +
      +
    • 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.
      • +
    • api_key (Required): Your API key for Pushetta.
      • +
    • channel_name (Required): The name of your channel.
      • +
    + +

    To retrieve the API token, log into your account at http://www.pushetta.com and go to your Dashboard. Create a new channel by clicking on Channels and then Add a Channel.

    + +

    It’s easy to test your Pushetta setup outside of Home Assistant. Assuming you have a channel home-assistant, just fire a request and check the channel page in the dashboard for a new message.

    + +
    + 
    curl -X POST \
+    -H "Authorization: Token YOUR_API_KEY" \
+    -H "Content-Type: application/json" \
+    -d "{ \"body\" : \"Hello World\", \"message_type\" : \"text/plain\" }" \
+    http://api.pushetta.com/api/pushes/home-assistant/
+
    +
    +
    + +

    For further details, please check the API.

    + +

    To use notifications, please see the getting started with automation page.

    + +
    + + +
    + + + + +
    +
    + + + + + + + + + \ No newline at end of file diff --git a/components/notify.pushover/index.html b/components/notify.pushover/index.html index 2d4d1d3b6d..77882c90f3 100644 --- a/components/notify.pushover/index.html +++ b/components/notify.pushover/index.html @@ -170,6 +170,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.slack/index.html b/components/notify.slack/index.html index 4f1eabfcc5..8d256b22c1 100644 --- a/components/notify.slack/index.html +++ b/components/notify.slack/index.html @@ -167,6 +167,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html index 543e40fd5c..dacbd00b06 100644 --- a/components/notify.smtp/index.html +++ b/components/notify.smtp/index.html @@ -183,6 +183,9 @@ which need special attention. By default, the usage by external applications, es
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.syslog/index.html b/components/notify.syslog/index.html index bd830761b2..ca1a7b77ad 100644 --- a/components/notify.syslog/index.html +++ b/components/notify.syslog/index.html @@ -271,6 +271,9 @@
  • PushOver
    • +
  • + Pushetta +
  • SMTP
    • diff --git a/components/notify.telegram/index.html b/components/notify.telegram/index.html index 28fdfe3801..46ef507ed1 100644 --- a/components/notify.telegram/index.html +++ b/components/notify.telegram/index.html @@ -105,8 +105,8 @@

    The requirement are:

    An easy way to get your chat ID is described below:

    @@ -120,6 +120,26 @@ print(chat_id) +

    Another way to retrieve your chat_id is visiting https://api.telegram.org/botYOUR_API_TOKEN/getUpdates.

    + +

    The result set will include your chat ID as id in the from section:

    + +
    + 
    {
+   "ok":true,
+   "result":[
+      {
+         "update_id":254199982,
+         "message":{
+            "message_id":201,
+            "from":{
+               "id":123456789,
+               "first_name":"Your first name",
+...
+
    +
    +
    +

    To enable Telegram notifications in your installation, add the following to your configuration.yaml file:

    @@ -127,7 +147,6 @@ print(chat_id) notify: name: NOTIFIER_NAME platform: telegram - # Get those by creating a new bot on https://core.telegram.org/bots api_key: ABCDEFGHJKLMNOPQRSTUVXYZ chat_id: YOUR_CHAT_ID
    @@ -137,8 +156,7 @@ print(chat_id)

    Configuration variables: