diff --git a/atom.xml b/atom.xml index c21dfa4e31..39fb3cac05 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ @@ -13,6 +13,106 @@ Octopress + + <![CDATA[0.23: TBD (rename file too).]]> + + 2016-07-01T00:31:00+00:00 + https://home-assistant.io/blog/2016/07/01/tbd + It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

+ +

This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

+ +

Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

+ +

On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

+ +

+ + + +

Breaking changes:

+ +
    +
  • Homematic thermostat configuration has changed and now depends on the new Homematic component.
    • +
+ +]]> + + + + <![CDATA[0.23: Envisalink, Homematic, HDMI-CEC and CherryPi]]> + + 2016-07-01T00:31:00+00:00 + https://home-assistant.io/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi + It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

+ +

This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

+ +

Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

+ +

On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

+ +

+ + + +

Breaking changes:

+ +
    +
  • Homematic thermostat configuration has changed and now depends on the new Homematic component.
    • +
+ +]]> + + <![CDATA[Using USB webcams with Home Assistant]]> @@ -1046,93 +1146,6 @@ For example, my wife works next door - and I couldn’t detect whether she’s a

I hope that this little article could give you an idea of extending Home Assistant in an unconventional way.

-]]> - - - - <![CDATA[Your hub should be local and open]]> - - 2016-04-05T04:11:00+00:00 - https://home-assistant.io/blog/2016/04/05/your-hub-should-be-local-and-open - 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.

- -

I’ve said it before but I’ll repeat it again:

- -
-

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.

- -]]> - - - - <![CDATA[0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl]]> - - 2016-03-26T07:10:00+00:00 - https://home-assistant.io/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl - Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.

- -

Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).

- -

Rock on.

- -

- - - -

Breaking changes

-
    -
  • -

    Automation: support for old deprecated config has been removed

    -
    • -
  • -

    Tellstick configuration has changed

    -
    • -
- -
- 
tellstick:
-  signal_repetitions: X
-
-
-
- -
    -
  • Vera configuration has changed
    • -
- -
- 
vera:
-  vera_controller_url: http://192.168.1.161:3480/
-  # Optional to exclude devices - this is a list of vera device ids
-  exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
-  # Optional to import switches as lights - this is a list of vera device ids
-  lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
-
-
-
]]> diff --git a/blog/2014/12/18/website-launched/index.html b/blog/2014/12/18/website-launched/index.html index 2dfebb60d2..5464459e9f 100644 --- a/blog/2014/12/18/website-launched/index.html +++ b/blog/2014/12/18/website-launched/index.html @@ -179,6 +179,18 @@ 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 256b18e37a..7cf5a1c18d 100644 --- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html +++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html @@ -234,6 +234,18 @@ 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 3354bd781a..73c3088986 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 @@ -218,6 +218,18 @@ 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 bb14f1a680..f073fef03b 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 @@ -193,6 +193,18 @@ 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 9e3d43b623..91e02ba511 100644 --- a/blog/2015/01/13/nest-in-da-house/index.html +++ b/blog/2015/01/13/nest-in-da-house/index.html @@ -196,6 +196,18 @@ password=YOUR_PASSWORD diff --git a/blog/2015/01/24/release-notes/index.html b/blog/2015/01/24/release-notes/index.html index 7363d99a7d..77d6cc6004 100644 --- a/blog/2015/01/24/release-notes/index.html +++ b/blog/2015/01/24/release-notes/index.html @@ -202,6 +202,18 @@ 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 cb0dc8d441..24c91eb4de 100644 --- a/blog/2015/02/08/looking-at-the-past/index.html +++ b/blog/2015/02/08/looking-at-the-past/index.html @@ -210,6 +210,18 @@ 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 75fb288635..4a0578fbfd 100644 --- a/blog/2015/02/24/streaming-updates/index.html +++ b/blog/2015/02/24/streaming-updates/index.html @@ -195,6 +195,18 @@ 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 d05da86ce5..0824b688ab 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 @@ -185,6 +185,18 @@ diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html index 4f8b089073..df6aeae3ad 100644 --- a/blog/2015/03/08/new-logo/index.html +++ b/blog/2015/03/08/new-logo/index.html @@ -186,6 +186,18 @@ 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 5e7487286b..2ac7a1f0d5 100644 --- a/blog/2015/03/11/release-notes/index.html +++ b/blog/2015/03/11/release-notes/index.html @@ -225,6 +225,18 @@ 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 042d131116..f3b126109f 100644 --- a/blog/2015/03/22/release-notes/index.html +++ b/blog/2015/03/22/release-notes/index.html @@ -262,6 +262,18 @@ 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 88b5861cfb..d562ef621f 100644 --- a/blog/2015/04/25/release-notes/index.html +++ b/blog/2015/04/25/release-notes/index.html @@ -273,6 +273,18 @@ 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 759c1b6a3a..3e39778496 100644 --- a/blog/2015/05/09/utc-time-zone-awareness/index.html +++ b/blog/2015/05/09/utc-time-zone-awareness/index.html @@ -208,6 +208,18 @@ diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html index 7810439e09..99380ad562 100644 --- a/blog/2015/05/14/release-notes/index.html +++ b/blog/2015/05/14/release-notes/index.html @@ -300,6 +300,18 @@ 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 93fa31d9f3..ee5abcd3ff 100644 --- a/blog/2015/06/10/release-notes/index.html +++ b/blog/2015/06/10/release-notes/index.html @@ -353,6 +353,18 @@ 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 12669bb201..d2616ffa92 100644 --- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html +++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html @@ -305,6 +305,18 @@ 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 24889a5e08..55039cd4a5 100644 --- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html +++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html @@ -294,6 +294,18 @@ Support for Temper temperature sensors has been contributed by +
  • + 0.23: TBD (rename file too). +
    • + + + +
  • + 0.23: Envisalink, Homematic, HDMI-CEC and CherryPi +
    • + + +
  • Using USB webcams with Home Assistant
    • @@ -311,18 +323,6 @@ Support for Temper temperature sensors has been contributed by - 0.21: Improved Web and support for EnOcean, LIRC and Osram Lightify - - - - -
  • - Community Highlights -
    • - - 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 071b0f000a..f6ba7c8a1b 100644 --- a/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html +++ b/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html @@ -204,6 +204,18 @@ 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 72247824b2..2fb12c04c0 100644 --- a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html +++ b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html @@ -317,6 +317,18 @@ The automation and script syntax here is using a deprecated and no longer suppor 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 810edcfe9e..7d833130cf 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 @@ -291,6 +291,18 @@ 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 7222dfd9df..e5df12c01e 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 @@ -494,6 +494,18 @@ 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 3b2fa91d45..202e03b3cf 100644 --- a/blog/2015/09/13/home-assistant-meets-ifttt/index.html +++ b/blog/2015/09/13/home-assistant-meets-ifttt/index.html @@ -353,6 +353,18 @@ 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 32e42e06ff..15abde80e1 100644 --- a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html +++ b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html @@ -254,6 +254,18 @@ 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 a232a65de8..d8e6d2cc84 100644 --- a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html +++ b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html @@ -233,6 +233,18 @@ 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 dd35405a36..3d521f30c7 100644 --- a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html +++ b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html @@ -209,6 +209,18 @@ 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 35586c752b..1f50b5c6d2 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 @@ -553,6 +553,18 @@ 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 5661020af1..b0b97d22e9 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 @@ -198,6 +198,18 @@ 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 7f4a004934..1f1ebbdab8 100644 --- a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html +++ b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html @@ -220,6 +220,18 @@ 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 index 21959bf16e..1ea842f7f8 100644 --- 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 @@ -216,6 +216,18 @@ diff --git a/blog/2015/11/22/survey-november-2015/index.html b/blog/2015/11/22/survey-november-2015/index.html index ee8aa042fc..dc2e0b6b02 100644 --- a/blog/2015/11/22/survey-november-2015/index.html +++ b/blog/2015/11/22/survey-november-2015/index.html @@ -256,6 +256,18 @@ diff --git a/blog/2015/12/05/community-highlights/index.html b/blog/2015/12/05/community-highlights/index.html index 7c4fb86fa4..a9ea6703fd 100644 --- a/blog/2015/12/05/community-highlights/index.html +++ b/blog/2015/12/05/community-highlights/index.html @@ -191,6 +191,18 @@ diff --git a/blog/2015/12/06/locks-rollershutters-binary-sensors-and-influxdb-support/index.html b/blog/2015/12/06/locks-rollershutters-binary-sensors-and-influxdb-support/index.html index aa1d051b74..4d97a3b4ac 100644 --- a/blog/2015/12/06/locks-rollershutters-binary-sensors-and-influxdb-support/index.html +++ b/blog/2015/12/06/locks-rollershutters-binary-sensors-and-influxdb-support/index.html @@ -198,6 +198,18 @@ diff --git a/blog/2015/12/07/influxdb-and-grafana/index.html b/blog/2015/12/07/influxdb-and-grafana/index.html index bf9d23f94e..22d29aa60b 100644 --- a/blog/2015/12/07/influxdb-and-grafana/index.html +++ b/blog/2015/12/07/influxdb-and-grafana/index.html @@ -289,6 +289,18 @@ $ sudo systemctl status grafana-server 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 f28b711715..e4be8c4789 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 @@ -239,6 +239,18 @@ requests.get(' +
  • + 0.23: TBD (rename file too). +
    • + + + +
  • + 0.23: Envisalink, Homematic, HDMI-CEC and CherryPi +
    • + + +
  • Using USB webcams with Home Assistant
    • @@ -256,18 +268,6 @@ requests.get(' - 0.21: Improved Web and support for EnOcean, LIRC and Osram Lightify - - - - -
  • - Community Highlights -
    • - - diff --git a/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html b/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html index 8faad97f5f..aa88508760 100644 --- a/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html +++ b/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/index.html @@ -211,6 +211,18 @@ Philips Hue FAQ entries regarding 3rd party light bulbs. diff --git a/blog/2015/12/13/setup-encryption-using-lets-encrypt/index.html b/blog/2015/12/13/setup-encryption-using-lets-encrypt/index.html index 245e5e5437..6b83d90c23 100644 --- a/blog/2015/12/13/setup-encryption-using-lets-encrypt/index.html +++ b/blog/2015/12/13/setup-encryption-using-lets-encrypt/index.html @@ -278,6 +278,18 @@ sudo docker run -it --rm -p 80:80 --name certbot \ diff --git a/blog/2015/12/22/amazon-echo-icloud-and-templates/index.html b/blog/2015/12/22/amazon-echo-icloud-and-templates/index.html index fe3d0d69cd..5f63a683b9 100644 --- a/blog/2015/12/22/amazon-echo-icloud-and-templates/index.html +++ b/blog/2015/12/22/amazon-echo-icloud-and-templates/index.html @@ -232,6 +232,18 @@ diff --git a/blog/2016/01/17/extended-support-for-diy-solutions/index.html b/blog/2016/01/17/extended-support-for-diy-solutions/index.html index 1cef9e6477..50c1b8b190 100644 --- a/blog/2016/01/17/extended-support-for-diy-solutions/index.html +++ b/blog/2016/01/17/extended-support-for-diy-solutions/index.html @@ -212,6 +212,18 @@ diff --git a/blog/2016/01/19/perfect-home-automation/index.html b/blog/2016/01/19/perfect-home-automation/index.html index ae693fa4cc..a6566b1743 100644 --- a/blog/2016/01/19/perfect-home-automation/index.html +++ b/blog/2016/01/19/perfect-home-automation/index.html @@ -216,6 +216,18 @@ 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 21781b8b95..acf0dd6024 100644 --- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html +++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html @@ -218,6 +218,18 @@ Example of the new views in the frontend. Learn mor diff --git a/blog/2016/02/09/smarter-smart-things-with-mqtt-and-home-assistant/index.html b/blog/2016/02/09/smarter-smart-things-with-mqtt-and-home-assistant/index.html index 7e9eebc1e8..8c68f57329 100644 --- a/blog/2016/02/09/smarter-smart-things-with-mqtt-and-home-assistant/index.html +++ b/blog/2016/02/09/smarter-smart-things-with-mqtt-and-home-assistant/index.html @@ -405,6 +405,18 @@ Z-Wave light bulb | diff --git a/blog/2016/02/12/classifying-the-internet-of-things/index.html b/blog/2016/02/12/classifying-the-internet-of-things/index.html index 42822e08e6..e65ae20784 100644 --- a/blog/2016/02/12/classifying-the-internet-of-things/index.html +++ b/blog/2016/02/12/classifying-the-internet-of-things/index.html @@ -355,6 +355,18 @@ diff --git a/blog/2016/02/13/speedtest-bloomsky-splunk-and-garage-doors/index.html b/blog/2016/02/13/speedtest-bloomsky-splunk-and-garage-doors/index.html index 99fca38695..61a051cd9c 100644 --- a/blog/2016/02/13/speedtest-bloomsky-splunk-and-garage-doors/index.html +++ b/blog/2016/02/13/speedtest-bloomsky-splunk-and-garage-doors/index.html @@ -221,6 +221,18 @@ diff --git a/blog/2016/02/18/multi-room-audio-with-snapcast/index.html b/blog/2016/02/18/multi-room-audio-with-snapcast/index.html index afebfc3314..fcede642cb 100644 --- a/blog/2016/02/18/multi-room-audio-with-snapcast/index.html +++ b/blog/2016/02/18/multi-room-audio-with-snapcast/index.html @@ -323,6 +323,18 @@ output = audioresample ! audio/x-raw,rate=48000,channels=2,format=S16LE ! audioc diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html index c62664ef3b..6848e13b60 100644 --- a/blog/2016/02/20/community-highlights/index.html +++ b/blog/2016/02/20/community-highlights/index.html @@ -231,6 +231,18 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm. diff --git a/blog/2016/02/27/steam-d-link-smart-plugs-and-neurio-energy-sensors/index.html b/blog/2016/02/27/steam-d-link-smart-plugs-and-neurio-energy-sensors/index.html index 55115166a8..fb6c8e38d4 100644 --- a/blog/2016/02/27/steam-d-link-smart-plugs-and-neurio-energy-sensors/index.html +++ b/blog/2016/02/27/steam-d-link-smart-plugs-and-neurio-energy-sensors/index.html @@ -220,6 +220,18 @@ diff --git a/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html b/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html index 9c4e190a7a..a407dbc218 100644 --- a/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html +++ b/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html @@ -226,6 +226,18 @@ player state attributes. This change affects automations, scripts and scenes. +
  • + 0.23: TBD (rename file too). +
    • + + + +
  • + 0.23: Envisalink, Homematic, HDMI-CEC and CherryPi +
    • + + +
  • Using USB webcams with Home Assistant
    • @@ -243,18 +255,6 @@ player state attributes. This change affects automations, scripts and scenes. - -
  • - 0.21: Improved Web and support for EnOcean, LIRC and Osram Lightify -
    • - - - -
  • - Community Highlights -
    • - - diff --git a/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl/index.html b/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl/index.html index a542d3ae2e..1bd4de30cf 100644 --- a/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl/index.html +++ b/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl/index.html @@ -237,6 +237,18 @@ diff --git a/blog/2016/04/05/your-hub-should-be-local-and-open/index.html b/blog/2016/04/05/your-hub-should-be-local-and-open/index.html index 1322824f10..b66589f453 100644 --- a/blog/2016/04/05/your-hub-should-be-local-and-open/index.html +++ b/blog/2016/04/05/your-hub-should-be-local-and-open/index.html @@ -189,6 +189,18 @@ diff --git a/blog/2016/04/07/static-website/index.html b/blog/2016/04/07/static-website/index.html index 85454f41d3..a75750437e 100644 --- a/blog/2016/04/07/static-website/index.html +++ b/blog/2016/04/07/static-website/index.html @@ -195,6 +195,18 @@ diff --git a/blog/2016/04/09/onkyo-panasonic-gtfs-and-config-validation/index.html b/blog/2016/04/09/onkyo-panasonic-gtfs-and-config-validation/index.html index 8d0c3bfff6..3759c9c414 100644 --- a/blog/2016/04/09/onkyo-panasonic-gtfs-and-config-validation/index.html +++ b/blog/2016/04/09/onkyo-panasonic-gtfs-and-config-validation/index.html @@ -203,6 +203,18 @@ diff --git a/blog/2016/04/17/updated-documentation/index.html b/blog/2016/04/17/updated-documentation/index.html index 8ce130b845..384ac7eddc 100644 --- a/blog/2016/04/17/updated-documentation/index.html +++ b/blog/2016/04/17/updated-documentation/index.html @@ -187,6 +187,18 @@ diff --git a/blog/2016/04/19/to-infinity-and-beyond/index.html b/blog/2016/04/19/to-infinity-and-beyond/index.html index 24cc426dc7..2e96a41095 100644 --- a/blog/2016/04/19/to-infinity-and-beyond/index.html +++ b/blog/2016/04/19/to-infinity-and-beyond/index.html @@ -204,6 +204,18 @@ diff --git a/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas/index.html b/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas/index.html index 9247f3a31a..2ba171f4c3 100644 --- a/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas/index.html +++ b/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas/index.html @@ -222,6 +222,18 @@ 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 a4ae3bfac0..d763473578 100644 --- a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html +++ b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html @@ -313,6 +313,18 @@ For example, my wife works next door - and I couldn’t detect whether she’s a diff --git a/blog/2016/05/06/open-iot-summit-talk/index.html b/blog/2016/05/06/open-iot-summit-talk/index.html index e68c445db0..9f78cdccf0 100644 --- a/blog/2016/05/06/open-iot-summit-talk/index.html +++ b/blog/2016/05/06/open-iot-summit-talk/index.html @@ -185,6 +185,18 @@ diff --git a/blog/2016/05/07/empowering-scripts-and-alexa/index.html b/blog/2016/05/07/empowering-scripts-and-alexa/index.html index 879319e925..0b82a4ad82 100644 --- a/blog/2016/05/07/empowering-scripts-and-alexa/index.html +++ b/blog/2016/05/07/empowering-scripts-and-alexa/index.html @@ -275,6 +275,18 @@ diff --git a/blog/2016/05/12/video-configuring-home-assistant/index.html b/blog/2016/05/12/video-configuring-home-assistant/index.html index eb4e93ed0f..d5859b008f 100644 --- a/blog/2016/05/12/video-configuring-home-assistant/index.html +++ b/blog/2016/05/12/video-configuring-home-assistant/index.html @@ -185,6 +185,18 @@ diff --git a/blog/2016/05/18/why-we-use-polymer/index.html b/blog/2016/05/18/why-we-use-polymer/index.html index 825e253ce7..5298eeaa24 100644 --- a/blog/2016/05/18/why-we-use-polymer/index.html +++ b/blog/2016/05/18/why-we-use-polymer/index.html @@ -199,6 +199,18 @@ diff --git a/blog/2016/05/21/release-020/index.html b/blog/2016/05/21/release-020/index.html index 9634541bfe..8018238ab0 100644 --- a/blog/2016/05/21/release-020/index.html +++ b/blog/2016/05/21/release-020/index.html @@ -220,6 +220,18 @@ diff --git a/blog/2016/05/22/get-started-with-all-in-one-installer/index.html b/blog/2016/05/22/get-started-with-all-in-one-installer/index.html index a0c73ab7c3..0dcd13b69b 100644 --- a/blog/2016/05/22/get-started-with-all-in-one-installer/index.html +++ b/blog/2016/05/22/get-started-with-all-in-one-installer/index.html @@ -191,6 +191,18 @@ diff --git a/blog/2016/05/26/ibeacons-how-to-track-things-that-cant-track-themselves-part-ii/index.html b/blog/2016/05/26/ibeacons-how-to-track-things-that-cant-track-themselves-part-ii/index.html index c57bd89cbf..a1428e7e8e 100644 --- a/blog/2016/05/26/ibeacons-how-to-track-things-that-cant-track-themselves-part-ii/index.html +++ b/blog/2016/05/26/ibeacons-how-to-track-things-that-cant-track-themselves-part-ii/index.html @@ -329,6 +329,18 @@ diff --git a/blog/2016/06/01/community-highlights/index.html b/blog/2016/06/01/community-highlights/index.html index 02a2ee76e0..7872a6d609 100644 --- a/blog/2016/06/01/community-highlights/index.html +++ b/blog/2016/06/01/community-highlights/index.html @@ -205,6 +205,18 @@ diff --git a/blog/2016/06/08/super-fast-web-enocean-lirc/index.html b/blog/2016/06/08/super-fast-web-enocean-lirc/index.html index e8fc232f1e..70ae8d97ff 100644 --- a/blog/2016/06/08/super-fast-web-enocean-lirc/index.html +++ b/blog/2016/06/08/super-fast-web-enocean-lirc/index.html @@ -239,6 +239,18 @@ diff --git a/blog/2016/06/13/home-assistant-at-pycon-2016/index.html b/blog/2016/06/13/home-assistant-at-pycon-2016/index.html index 6df4f2d7f7..441ef3b7d7 100644 --- a/blog/2016/06/13/home-assistant-at-pycon-2016/index.html +++ b/blog/2016/06/13/home-assistant-at-pycon-2016/index.html @@ -210,6 +210,18 @@ diff --git a/blog/2016/06/18/pandora-bt-home-hub-5-and-local-file-camera/index.html b/blog/2016/06/18/pandora-bt-home-hub-5-and-local-file-camera/index.html index c01caaf146..6eb200cdad 100644 --- a/blog/2016/06/18/pandora-bt-home-hub-5-and-local-file-camera/index.html +++ b/blog/2016/06/18/pandora-bt-home-hub-5-and-local-file-camera/index.html @@ -234,6 +234,18 @@ diff --git a/blog/2016/06/23/usb-webcams-and-home-assistant/index.html b/blog/2016/06/23/usb-webcams-and-home-assistant/index.html index 7d8dacd7d8..495a4fe411 100644 --- a/blog/2016/06/23/usb-webcams-and-home-assistant/index.html +++ b/blog/2016/06/23/usb-webcams-and-home-assistant/index.html @@ -300,6 +300,18 @@ target_dir /tmp diff --git a/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi/index.html b/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi/index.html new file mode 100644 index 0000000000..a5c5ea7a6d --- /dev/null +++ b/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi/index.html @@ -0,0 +1,298 @@ + + + + + + + + + + 0.23: Envisalink, Homematic, HDMI-CEC and CherryPi - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + +
    + +

    0.23: Envisalink, Homematic, HDMI-CEC and CherryPi

    + + + +
    + + Paulus Schoutsen + three minutes reading time + + + + + + Comments + +
    + +
    + + +

    It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

    + +

    This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

    + +

    Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

    + +

    On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

    + +

    + + + +

    Breaking changes:

    + +
      +
    • Homematic thermostat configuration has changed and now depends on the new Homematic component.
      • +
    +
    + + +
    +

    Comments

    +
    +
    + + +
    + + + + +
    +
    + + + + + + + \ No newline at end of file diff --git a/blog/2016/07/01/tbd/index.html b/blog/2016/07/01/tbd/index.html new file mode 100644 index 0000000000..abc362d92c --- /dev/null +++ b/blog/2016/07/01/tbd/index.html @@ -0,0 +1,298 @@ + + + + + + + + + + 0.23: TBD (rename file too). - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + +
    + +

    0.23: TBD (rename file too).

    + + + +
    + + Paulus Schoutsen + three minutes reading time + + + + + + Comments + +
    + +
    + + +

    It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

    + +

    This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

    + +

    Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

    + +

    On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

    + +

    + + + +

    Breaking changes:

    + +
      +
    • Homematic thermostat configuration has changed and now depends on the new Homematic component.
      • +
    +
    + + +
    +

    Comments

    +
    +
    + + +
    + + + + +
    +
    + + + + + + + \ No newline at end of file diff --git a/blog/archives/index.html b/blog/archives/index.html index 82168afd37..07145d6f31 100644 --- a/blog/archives/index.html +++ b/blog/archives/index.html @@ -98,6 +98,70 @@

    2016

    + + + + + + + +
    @@ -2371,6 +2435,18 @@ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index a9b4f516ae..f53c18eba7 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/index.html b/blog/categories/community/index.html index b519202663..281789d788 100644 --- a/blog/categories/community/index.html +++ b/blog/categories/community/index.html @@ -268,6 +268,18 @@ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index b8c23a1a46..6d209c407d 100644 --- a/blog/categories/device-tracking/atom.xml +++ b/blog/categories/device-tracking/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Device-Tracking | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/index.html b/blog/categories/device-tracking/index.html index 9b1bf78687..180981c2bb 100644 --- a/blog/categories/device-tracking/index.html +++ b/blog/categories/device-tracking/index.html @@ -199,6 +199,18 @@ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index f935abe4bc..8e5583a65a 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/index.html b/blog/categories/esp8266/index.html index 14756016ca..58228a9cf7 100644 --- a/blog/categories/esp8266/index.html +++ b/blog/categories/esp8266/index.html @@ -199,6 +199,18 @@ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index d45e0a12df..df6da6d646 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]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/index.html b/blog/categories/how-to/index.html index c6e4d3ce1d..12342413b7 100644 --- a/blog/categories/how-to/index.html +++ b/blog/categories/how-to/index.html @@ -528,6 +528,18 @@ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 88144df2fe..6bb12e010e 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/index.html b/blog/categories/ibeacons/index.html index 3c8bb3ef56..1a23b75d71 100644 --- a/blog/categories/ibeacons/index.html +++ b/blog/categories/ibeacons/index.html @@ -235,6 +235,18 @@ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index bafb74970a..2300d7a420 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/index.html b/blog/categories/internet-of-things/index.html index 5adfafd267..1219759ffc 100644 --- a/blog/categories/internet-of-things/index.html +++ b/blog/categories/internet-of-things/index.html @@ -294,6 +294,18 @@ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 14b25f5e50..d558c37920 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/index.html b/blog/categories/mqtt/index.html index 8da81c86c0..bd20972ee5 100644 --- a/blog/categories/mqtt/index.html +++ b/blog/categories/mqtt/index.html @@ -270,6 +270,18 @@ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index b85efc64dd..5cbda87a2f 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/index.html b/blog/categories/organisation/index.html index 47f008f32e..df08221521 100644 --- a/blog/categories/organisation/index.html +++ b/blog/categories/organisation/index.html @@ -230,6 +230,18 @@ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 1ebf2fa55a..0d3623ed4b 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/index.html b/blog/categories/owntracks/index.html index b398390142..e1824e9f64 100644 --- a/blog/categories/owntracks/index.html +++ b/blog/categories/owntracks/index.html @@ -235,6 +235,18 @@ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index eef08ae9f0..edfebabf80 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/index.html b/blog/categories/presence-detection/index.html index c3d2fe6550..2d8a1f0357 100644 --- a/blog/categories/presence-detection/index.html +++ b/blog/categories/presence-detection/index.html @@ -199,6 +199,18 @@ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index 46574afc4f..72df3411d5 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/index.html b/blog/categories/public-service-announcement/index.html index e0494452cc..ca00a0781b 100644 --- a/blog/categories/public-service-announcement/index.html +++ b/blog/categories/public-service-announcement/index.html @@ -195,6 +195,18 @@ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 3d14341030..b25b992b6f 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Release-Notes | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ @@ -13,6 +13,106 @@ Octopress + + <![CDATA[0.23: TBD (rename file too).]]> + + 2016-07-01T00:31:00+00:00 + https://home-assistant.io/blog/2016/07/01/tbd + It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

    + +

    This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

    + +

    Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

    + +

    On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

    + +

    + + + +

    Breaking changes:

    + +
      +
    • Homematic thermostat configuration has changed and now depends on the new Homematic component.
      • +
    + +]]>     +     + + + <![CDATA[0.23: Envisalink, Homematic, HDMI-CEC and CherryPi]]> + + 2016-07-01T00:31:00+00:00 + https://home-assistant.io/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi + It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

    + +

    This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

    + +

    Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

    + +

    On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

    + +

    + + + +

    Breaking changes:

    + +
      +
    • Homematic thermostat configuration has changed and now depends on the new Homematic component.
      • +
    + +]]>     +     + <![CDATA[0.22: Pandora, BT Home Hub 5 and local file camera.]]> @@ -196,163 +296,6 @@
    -]]> - - - - <![CDATA[0.19: Empowering scripts and Alexa]]> - - 2016-05-07T18:06:00+00:00 - https://home-assistant.io/blog/2016/05/07/empowering-scripts-and-alexa - This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.

    - -

    Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.

    - -
    - 
    automation:
-  trigger:
-    platform: mqtt
-    topic: some/notify/topic
-  action:
-    service: notify.notify
-    data_template:
-      message: 
-
-automation 2:
-  trigger:
-    platform: state
-    entity_id: light.hue
-  action:
-    service: notify.notify
-    data_template:
-      message:  is now 
-
    -
    -
    - -

    Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:

    - -
    - 
    light:
-  platform: hue
-  entity_namespace: holiday_home
-
    -
    -
    - - - -

    Deprecations

    -
      -
    • Conditions in automations should now specify which condition to use with condition: instead of platform:. For example condition: state.
      • -
    • RFXtrx has a new config format.
      • -
    - -

    Old RFXtrx config format:

    - -
    - 
      devices:
-    123efab1:
-      name: My DI.0 light device
-      packetid: 1b2200000890efab1213f60
-
    -
    -
    - -

    New RFXtrx config format:

    - -
    - 
      devices:
-    1b2200000890efab1213f60:
-      name: My DI.0 light device
-
    -
    -
    -]]>     -     - - - <![CDATA[0.18: Bluetooth, LG WebOS TVs and Roombas.]]> - - 2016-04-20T06:10:00+00:00 - https://home-assistant.io/blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas - It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.

    - -

    Since the last release we have moved all Home Assistant source code etc into it’s own organisation on GitHub. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.

    - -

    - -

    - - - -

    Breaking changes

    -
      -
    • We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
      • -
    • The constant TEMP_CELCIUS is now correctly called TEMP_CELSIUS. Old one is deprecated and will eventually be removed.
      • -
    • The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
      • -
    • MySensors received two big changes that will cause you to update your configs. See component page for new example config. -
        -
      1. All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
        2. -
      2. The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
        3. -
      -
      • -
    ]]>         diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html index b779061034..c74248e99d 100644 --- a/blog/categories/release-notes/index.html +++ b/blog/categories/release-notes/index.html @@ -98,6 +98,70 @@

    2016

    + + + + + + + +
    @@ -1352,6 +1416,18 @@ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index c6b6ca8515..55e0ce5215 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/index.html b/blog/categories/survey/index.html index 32e1fa7746..e0aaf89ac6 100644 --- a/blog/categories/survey/index.html +++ b/blog/categories/survey/index.html @@ -195,6 +195,18 @@ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 238fa23a02..2047cc3ff2 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/index.html b/blog/categories/talks/index.html index 0afc655147..cb08c6cc42 100644 --- a/blog/categories/talks/index.html +++ b/blog/categories/talks/index.html @@ -197,6 +197,18 @@ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index ab8b8afa5b..053a99aeea 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/index.html b/blog/categories/technology/index.html index 3d039bef3c..3a84d5f842 100644 --- a/blog/categories/technology/index.html +++ b/blog/categories/technology/index.html @@ -195,6 +195,18 @@ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index e02c979c83..91e7597570 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]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/index.html b/blog/categories/user-stories/index.html index 0d39cda7e7..72c1473344 100644 --- a/blog/categories/user-stories/index.html +++ b/blog/categories/user-stories/index.html @@ -195,6 +195,18 @@ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 9ee30824c3..d5954d0b9e 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/index.html b/blog/categories/video/index.html index 0473a2945a..6db2e34b27 100644 --- a/blog/categories/video/index.html +++ b/blog/categories/video/index.html @@ -398,6 +398,18 @@ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 3b789a470c..71a5833215 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-07-01T17:20:06+00:00 + 2016-07-01T18:46:16+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/index.html b/blog/categories/website/index.html index cc9bf62800..5008844c19 100644 --- a/blog/categories/website/index.html +++ b/blog/categories/website/index.html @@ -230,6 +230,18 @@ diff --git a/blog/index.html b/blog/index.html index 0773afd2c0..4c6f0478ff 100644 --- a/blog/index.html +++ b/blog/index.html @@ -78,6 +78,170 @@ +
    +
    + +

    + 0.23: TBD (rename file too). +

    + + + +
    + + Paulus Schoutsen + three minutes reading time + + + + + + Comments + +
    + +
    + + +
    +

    It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

    + +

    This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

    + +

    Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

    + +

    On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

    + +

    + + + +

    Breaking changes:

    + +
      +
    • Homematic thermostat configuration has changed and now depends on the new Homematic component.
      • +
    + + + +
    +
    +
    + +
    +
    + +

    + 0.23: Envisalink, Homematic, HDMI-CEC and CherryPi +

    + + + +
    + + Paulus Schoutsen + three minutes reading time + + + + + + Comments + +
    + +
    + + +
    +

    It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.

    + +

    This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.

    + +

    Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.

    + +

    On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!

    + +

    + + + +

    Breaking changes:

    + +
      +
    • Homematic thermostat configuration has changed and now depends on the new Homematic component.
      • +
    + + + +
    +
    +
    +
    @@ -648,103 +812,6 @@ In the past month I was thinking about ways to integrate USB webcams into Home A -
    -
    -
    - -
    -
    - -

    - Why we use web components and Polymer -

    - - - -
    - - Paulus Schoutsen - three minutes reading time - - - - - - Comments - -
    - -
    - - -
    -

    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.

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

    - Video: How To Configure Home Assistant -

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

    Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!

    - -

    Make sure to subscribe to his YouTube channel for more Home Assistant video’s.

    - -
    - -
    - -
    diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html index c4c3b7f7a1..660ee02300 100644 --- a/blog/posts/2/index.html +++ b/blog/posts/2/index.html @@ -78,6 +78,103 @@ +
    +
    + +

    + Why we use web components and Polymer +

    + + + +
    + + Paulus Schoutsen + three minutes reading time + + + + + + Comments + +
    + +
    + + +
    +

    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.

    + + + + Read on → + +
    +
    +
    + +
    +
    + +

    + Video: How To Configure Home Assistant +

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

    Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!

    + +

    Make sure to subscribe to his YouTube channel for more Home Assistant video’s.

    + +
    + +
    + + +
    +
    +
    +
    @@ -636,157 +733,6 @@
    -
    -
    - -

    - Your hub should be local and open -

    - - - -
    - - Paulus Schoutsen - 1 minute reading time - - - - - - Comments - -
    - -
    - - -
    -

    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.

    - -

    I’ve said it before but I’ll repeat it again:

    - -
    -

    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.

    - - - -
    -
    -
    - -
    -
    - -

    - 0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl -

    - - - -
    - - Paulus Schoutsen - two minutes reading time - - - - - - Comments - -
    - -
    - - -
    -

    Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.

    - -

    Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).

    - -

    Rock on.

    - -

    - - - -

    Breaking changes

    -
      -
    • -

      Automation: support for old deprecated config has been removed

      -
      • -
    • -

      Tellstick configuration has changed

      -
      • -
    - -
    - 
    tellstick:
-  signal_repetitions: X
-
    -
    -
    - -
      -
    • Vera configuration has changed
      • -
    - -
    - 
    vera:
-  vera_controller_url: http://192.168.1.161:3480/
-  # Optional to exclude devices - this is a list of vera device ids
-  exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
-  # Optional to import switches as lights - this is a list of vera device ids
-  lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
-
    -
    -
    - - -
    -
    -
    - -
    -
    - -
    -
    - -

    - Perfect Home Automation -

    - - - -
    - - Paulus Schoutsen - five minutes reading time - - - - - - Comments - -
    - -
    - - -
    -

    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.

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

    - 0.11: Extended support for DIY solutions -

    - - - -
    - - Paulus Schoutsen - two minutes reading time - - - - - - Comments - -
    - -
    - - -
    -

    First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.

    - -

    - - - -

    Backwards incompatible changes

    - - - -
    diff --git a/blog/posts/4/index.html b/blog/posts/4/index.html index 6dc532fa3e..15506fae0d 100644 --- a/blog/posts/4/index.html +++ b/blog/posts/4/index.html @@ -78,6 +78,133 @@ +
    +
    + +

    + Perfect Home Automation +

    + + + +
    + + Paulus Schoutsen + five minutes reading time + + + + + + Comments + +
    + +
    + + +
    +

    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.

    + + + + Read on → + +
    +
    +
    + +
    +
    + +

    + 0.11: Extended support for DIY solutions +

    + + + +
    + + Paulus Schoutsen + two minutes reading time + + + + + + Comments + +
    + +
    + + +
    +

    First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.

    + +

    + + + +

    Backwards incompatible changes

    + + + + +
    +
    +
    +
    @@ -498,152 +625,6 @@ The InfluxDB database is a so-called time se
    -
    -
    - -

    - 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

    - -

    - - - - - -
    -
    -
    - -
    -
    - -

    - 0.7.6: Amazon FireTV, Radiotherm thermostats -

    - - - -
    - - Paulus Schoutsen - two minutes reading time - - - - - - Comments - -
    - -
    - - -
    -

    After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been squashed, test coverage increased to 85% and thanks to the hard work by @fabaff and myself the component section on the website has gotten a complete revamp.

    - -

    Changes

    - -

    - - - - - - 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. -

    - - -
    -
    -
    - -
    -
    - -

    - Home Assistant moving to YAML -

    - - - -
    - - Theodor Lindquist - less than one minute reading time - - - - - - Comments - -
    - -
    - - -
    -

    Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.

    - -

    The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.

    - -

    The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.

    - -

    Users of Home Assistant should migrate as the old configuration format is deprecated.

    - -
    diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html index 9c7dcd566b..333eb385f8 100644 --- a/blog/posts/7/index.html +++ b/blog/posts/7/index.html @@ -78,6 +78,101 @@ +
    +
    + +

    + 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. +

    + + +
    +
    +
    + +
    +
    + +

    + Home Assistant moving to YAML +

    + + + +
    + + Theodor Lindquist + less than one minute reading time + + + + + + Comments + +
    + +
    + + +
    +

    Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.

    + +

    The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.

    + +

    The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.

    + +

    Users of Home Assistant should migrate as the old configuration format is deprecated.

    + + +
    +
    +
    +
    diff --git a/components/alarm_control_panel.alarmdotcom/index.html b/components/alarm_control_panel.alarmdotcom/index.html index 291fea3c3a..dace16672b 100644 --- a/components/alarm_control_panel.alarmdotcom/index.html +++ b/components/alarm_control_panel.alarmdotcom/index.html @@ -144,6 +144,12 @@
  • Alarm.com Alarm Control Panel
    • +
  • + Envisalink Alarm +
    • +
  • + Envisalink Alarm Control Panel +
  • Intruder Alerts
    • diff --git a/components/alarm_control_panel.envisalink/index.html b/components/alarm_control_panel.envisalink/index.html new file mode 100644 index 0000000000..838dc1e59d --- /dev/null +++ b/components/alarm_control_panel.envisalink/index.html @@ -0,0 +1,200 @@ + + + + + + + + + + Envisalink Alarm - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Envisalink Alarm +

    +
    +
    + + +

    The envisalink alarm control panel platform allows you to control your Envisalink alarms.

    + +

    The requirement is that you have setup your Envisalink hub.

    + + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/alarm_control_panel.manual/index.html b/components/alarm_control_panel.manual/index.html index 974ccda7cd..77372c1fd2 100644 --- a/components/alarm_control_panel.manual/index.html +++ b/components/alarm_control_panel.manual/index.html @@ -175,6 +175,12 @@
  • Alarm.com Alarm Control Panel
    • +
  • + Envisalink Alarm +
    • +
  • + Envisalink Alarm Control Panel +
  • Intruder Alerts
    • diff --git a/components/alarm_control_panel.mqtt/index.html b/components/alarm_control_panel.mqtt/index.html index 9599e7e300..aa68ac9d50 100644 --- a/components/alarm_control_panel.mqtt/index.html +++ b/components/alarm_control_panel.mqtt/index.html @@ -199,6 +199,12 @@
  • Alarm.com Alarm Control Panel
    • +
  • + Envisalink Alarm +
    • +
  • + Envisalink Alarm Control Panel +
  • Intruder Alerts
    • diff --git a/components/alarm_control_panel.nx584/index.html b/components/alarm_control_panel.nx584/index.html index b99b787565..37dcd75476 100644 --- a/components/alarm_control_panel.nx584/index.html +++ b/components/alarm_control_panel.nx584/index.html @@ -146,6 +146,12 @@
  • Alarm.com Alarm Control Panel
    • +
  • + Envisalink Alarm +
    • +
  • + Envisalink Alarm Control Panel +
  • Intruder Alerts
    • diff --git a/components/alarm_control_panel.verisure/index.html b/components/alarm_control_panel.verisure/index.html index e5dddd5580..20a63bab1e 100644 --- a/components/alarm_control_panel.verisure/index.html +++ b/components/alarm_control_panel.verisure/index.html @@ -140,6 +140,12 @@
  • Alarm.com Alarm Control Panel
    • +
  • + Envisalink Alarm +
    • +
  • + Envisalink Alarm Control Panel +
  • Intruder Alerts
    • diff --git a/components/alarm_control_panel/index.html b/components/alarm_control_panel/index.html index 499ded9207..6f0309b27d 100644 --- a/components/alarm_control_panel/index.html +++ b/components/alarm_control_panel/index.html @@ -119,6 +119,9 @@
  • Alarm.com Alarm Control Panel
    • +
  • + Envisalink Alarm +
  • MQTT Alarm Control Panel
    • diff --git a/components/apcupsd/index.html b/components/apcupsd/index.html index 948efdbe8e..153c75ec16 100644 --- a/components/apcupsd/index.html +++ b/components/apcupsd/index.html @@ -158,6 +158,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/automation/index.html b/components/automation/index.html index b4d0c8d47c..5a35b354c8 100644 --- a/components/automation/index.html +++ b/components/automation/index.html @@ -114,6 +114,9 @@
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/binary_sensor.apcupsd/index.html b/components/binary_sensor.apcupsd/index.html index 9bd614c858..aef1699df9 100644 --- a/components/binary_sensor.apcupsd/index.html +++ b/components/binary_sensor.apcupsd/index.html @@ -154,9 +154,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html index f42cac4c89..b0f0c81e2f 100644 --- a/components/binary_sensor.arest/index.html +++ b/components/binary_sensor.arest/index.html @@ -173,9 +173,15 @@ This sensor is not suitable for fast state changes because there is a high possi
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.bloomsky/index.html b/components/binary_sensor.bloomsky/index.html index d1ad637636..de0a777dcb 100644 --- a/components/binary_sensor.bloomsky/index.html +++ b/components/binary_sensor.bloomsky/index.html @@ -152,9 +152,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.command_line/index.html b/components/binary_sensor.command_line/index.html index d8ce6bd16f..b6843f883f 100644 --- a/components/binary_sensor.command_line/index.html +++ b/components/binary_sensor.command_line/index.html @@ -217,9 +217,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.enocean/index.html b/components/binary_sensor.enocean/index.html index b176dc6006..d3d614fccb 100644 --- a/components/binary_sensor.enocean/index.html +++ b/components/binary_sensor.enocean/index.html @@ -163,9 +163,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.envisalink/index.html b/components/binary_sensor.envisalink/index.html new file mode 100644 index 0000000000..ecc8e2ce88 --- /dev/null +++ b/components/binary_sensor.envisalink/index.html @@ -0,0 +1,234 @@ + + + + + + + + + + Envisalink Binary Sensor - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Envisalink Binary Sensor +

    +
    +
    + + +

    The envisalink platform allows you to get data from your Envisalink binary sensors from within Home Assistant.

    + +

    The requirement is that you have setup your Envisalink hub.

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/binary_sensor.homematic/index.html b/components/binary_sensor.homematic/index.html new file mode 100644 index 0000000000..5e1c192f83 --- /dev/null +++ b/components/binary_sensor.homematic/index.html @@ -0,0 +1,240 @@ + + + + + + + + + + Homematic Binary Sensor - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Homematic Binary Sensor +

    +
    +
    + + +

    The homematic binary sensor platform lets you observe the state changes of binary Homematic sensors through Home Assistant.

    + +

    Devices will be configured automatically. Please refer to the component configuration on how to setup Homematic.

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html index 42d60c4eb5..5ad757d064 100644 --- a/components/binary_sensor.http/index.html +++ b/components/binary_sensor.http/index.html @@ -213,9 +213,15 @@ print(response.text)
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.mqtt/index.html b/components/binary_sensor.mqtt/index.html index 1aa10bc8e6..588753c99f 100644 --- a/components/binary_sensor.mqtt/index.html +++ b/components/binary_sensor.mqtt/index.html @@ -198,9 +198,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.mysensors/index.html b/components/binary_sensor.mysensors/index.html index 82b76c5bdb..6892ceb6aa 100644 --- a/components/binary_sensor.mysensors/index.html +++ b/components/binary_sensor.mysensors/index.html @@ -255,9 +255,15 @@ MyMessage msg(CHILD_ID, V_TRIPPED);
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.nest/index.html b/components/binary_sensor.nest/index.html index e0df18db37..fc7f368258 100644 --- a/components/binary_sensor.nest/index.html +++ b/components/binary_sensor.nest/index.html @@ -175,9 +175,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.nx584/index.html b/components/binary_sensor.nx584/index.html index ec9c7332aa..b34d960086 100644 --- a/components/binary_sensor.nx584/index.html +++ b/components/binary_sensor.nx584/index.html @@ -178,9 +178,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html index 03fcb52bfe..218c15f8c4 100644 --- a/components/binary_sensor.octoprint/index.html +++ b/components/binary_sensor.octoprint/index.html @@ -161,9 +161,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.rest/index.html b/components/binary_sensor.rest/index.html index 6c8fe068cf..1925f1a7b6 100644 --- a/components/binary_sensor.rest/index.html +++ b/components/binary_sensor.rest/index.html @@ -199,9 +199,15 @@ Make sure that the URL matches exactly your endpoint or resource.
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.rpi_gpio/index.html b/components/binary_sensor.rpi_gpio/index.html index c6340906ea..8817a5f41b 100644 --- a/components/binary_sensor.rpi_gpio/index.html +++ b/components/binary_sensor.rpi_gpio/index.html @@ -155,6 +155,9 @@ To avoid having to run Home Assistant as root when using this component, run a R
  • Raspberry PI GPIO Switch
    • +
  • + Raspberry Pi Garage door +
    • @@ -172,9 +175,15 @@ To avoid having to run Home Assistant as root when using this component, run a R
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.tcp/index.html b/components/binary_sensor.tcp/index.html index 74b09167cd..9f833a6320 100644 --- a/components/binary_sensor.tcp/index.html +++ b/components/binary_sensor.tcp/index.html @@ -164,9 +164,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.template/index.html b/components/binary_sensor.template/index.html index 53961561a1..20c9b84977 100644 --- a/components/binary_sensor.template/index.html +++ b/components/binary_sensor.template/index.html @@ -198,9 +198,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.vera/index.html b/components/binary_sensor.vera/index.html index ed379bfb6e..83caebc662 100644 --- a/components/binary_sensor.vera/index.html +++ b/components/binary_sensor.vera/index.html @@ -121,6 +121,9 @@
  • Vera Light
    • +
  • + Vera Lock +
  • Vera Sensor
    • @@ -144,9 +147,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html index 5a93e41260..0854f97e29 100644 --- a/components/binary_sensor.wink/index.html +++ b/components/binary_sensor.wink/index.html @@ -154,9 +154,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.zigbee/index.html b/components/binary_sensor.zigbee/index.html index 3bb6d7dcd1..ce67d71b28 100644 --- a/components/binary_sensor.zigbee/index.html +++ b/components/binary_sensor.zigbee/index.html @@ -164,9 +164,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor.zwave/index.html b/components/binary_sensor.zwave/index.html index 9aa4e7bdab..c8a97ce265 100644 --- a/components/binary_sensor.zwave/index.html +++ b/components/binary_sensor.zwave/index.html @@ -116,6 +116,9 @@
  • Z-Wave
    • +
  • + Z-Wave Garage Door +
  • Z-Wave HVAC
    • @@ -125,6 +128,9 @@
  • Z-Wave Lock
    • +
  • + Z-Wave Rollershutter +
  • Z-Wave Sensor
    • @@ -151,9 +157,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/binary_sensor/index.html b/components/binary_sensor/index.html index 172ccb97c1..a1ad76def8 100644 --- a/components/binary_sensor/index.html +++ b/components/binary_sensor/index.html @@ -143,9 +143,15 @@
  • EnOcean Binary Sensor
    • +
  • + Envisalink Binary Sensor +
  • HTTP Binary Sensor
    • +
  • + Homematic Binary Sensor +
  • MQTT Binary Sensor
    • diff --git a/components/bloomsky/index.html b/components/bloomsky/index.html index 2f96865442..f06b19ca12 100644 --- a/components/bloomsky/index.html +++ b/components/bloomsky/index.html @@ -155,6 +155,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/browser/index.html b/components/browser/index.html index ab3a8769fe..5cd12583eb 100644 --- a/components/browser/index.html +++ b/components/browser/index.html @@ -180,6 +180,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/configurator/index.html b/components/configurator/index.html index 0c6318a4d1..aaf1a8a4c2 100644 --- a/components/configurator/index.html +++ b/components/configurator/index.html @@ -154,6 +154,9 @@ This component is intended for developers.
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/demo/index.html b/components/demo/index.html index 926a99df57..8f574273a2 100644 --- a/components/demo/index.html +++ b/components/demo/index.html @@ -172,6 +172,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/device_sun_light_trigger/index.html b/components/device_sun_light_trigger/index.html index fec5577ceb..3618cb7463 100644 --- a/components/device_sun_light_trigger/index.html +++ b/components/device_sun_light_trigger/index.html @@ -144,6 +144,9 @@
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/discovery/index.html b/components/discovery/index.html index 671ce955a4..c1befade41 100644 --- a/components/discovery/index.html +++ b/components/discovery/index.html @@ -178,6 +178,9 @@ If you see Not initializing discovery because could not install dependency
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/downloader/index.html b/components/downloader/index.html index 3a726d4597..bbf31e88a0 100644 --- a/components/downloader/index.html +++ b/components/downloader/index.html @@ -189,6 +189,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/ecobee/index.html b/components/ecobee/index.html index 64e11183da..5c3a671ba3 100644 --- a/components/ecobee/index.html +++ b/components/ecobee/index.html @@ -165,6 +165,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/enocean/index.html b/components/enocean/index.html index 655825450c..d4e61ebc15 100644 --- a/components/enocean/index.html +++ b/components/enocean/index.html @@ -179,6 +179,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/envisalink/index.html b/components/envisalink/index.html new file mode 100644 index 0000000000..8ce46cde97 --- /dev/null +++ b/components/envisalink/index.html @@ -0,0 +1,259 @@ + + + + + + + + + + Envisalink Alarm Control Panel - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Envisalink Alarm Control Panel +

    +
    +
    + + +

    This component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and it’s sensors to provide Home Assistant with rich information about their homes.
    +Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.

    + +

    Please visit the eyezon website for further information about the evl3 and evl4 boards.

    + +

    There is currently support for the following device types within Home Assistant:

    + +
      +
    • Binary Sensor: Reports on zone status
      • +
    • Sensor: Emulates an alpha-numeric keypad attached to the alarm panel
      • +
    • Alarm Control Panel: Reports on partition status, and can be used to arm/disarm the system
      • +
    + +

    This is a fully event-based component- any event sent by the Envisalink device will be immediately reflected within Home Assistant.

    + +

    Configuration

    + +

    An envisalink section must be present in the configuration.yaml file and contain the following options as required:

    + +

    Required Parameters

    +
      +
    • host: The IP address of the Envisalink device on your home network.
      • +
    • panel_type: HONEYWELL or DSC, depending upon which alarm system you have.
      • +
    • user_name: Which username to authenticate with when connecting to the device. On a Honeywell alarm panel, the username/password are the same.
      • +
    • password: Which password to authenticate with when connecting to the device.
      • +
    • code: Your alarm panel’s code, for authenticating user input during arm/disarm.
      • +
    + +

    Optional Parameters

    +
      +
    • port: Which network port to connect with. Default: 4025
      • +
    • evl_version: 3 for evl3, or 4 for evl4. Default: 3
      • +
    • keepalive_interval: This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting. This is required for DSC and Honeywell systems. Default: 60 seconds
      • +
    • zonedump_interval: This is an interval (measured in seconds) where the evl will dump out all zone statuses. This is required for Honeywell systems, which do not properly send zone closure events. DSC boards do not technically need this. Default: 30
      • +
    • zones: Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. Note- if no zones are specified, Home Assistant will not load any binary_sensor components.
      • +
    • partitions: Again, Envisalink boards do not tell us what is in use, and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded.
      • +
    + +

    Example

    + +
    + 
    envisalink:
+#optional
+  port: 4025
+  evl_version: 3
+  keepalive_interval: 60
+  zonedump_interval: 30
+
+#required
+  host: <envisalink IP address>
+  panel_type: HONEYWELL or DSC
+  user_name: <pass>
+  password: <pass>
+  code: '1234'
+
+  zones:
+    11:
+      name: 'Back Door'
+      type: 'opening'
+
+    21:
+      name: 'First Floor Motion'
+      type: 'motion'
+
+  partitions:
+    1:
+      name: 'Home Alarm'
+
    +
    +
    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/feedreader/index.html b/components/feedreader/index.html index 9c968f7b75..585bec935e 100644 --- a/components/feedreader/index.html +++ b/components/feedreader/index.html @@ -187,6 +187,9 @@ hass.bus.listen(EVENT_FEEDREADER, event_listener)
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/garage_door.mqtt/index.html b/components/garage_door.mqtt/index.html index 78927090b8..ca718dbadb 100644 --- a/components/garage_door.mqtt/index.html +++ b/components/garage_door.mqtt/index.html @@ -209,9 +209,15 @@
  • MQTT Garage door
    • +
  • + Raspberry Pi Garage door +
  • Wink Garage door
    • +
  • + Z-Wave Garage Door +
    • diff --git a/components/garage_door.rpi_gpio/index.html b/components/garage_door.rpi_gpio/index.html new file mode 100644 index 0000000000..babcdb7538 --- /dev/null +++ b/components/garage_door.rpi_gpio/index.html @@ -0,0 +1,192 @@ + + + + + + + + + + Raspberry Pi Garage door - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Raspberry Pi Garage Door +

    +
    +
    + + +
    + 
    # Example configuration.yaml entry
+garage_door:
+  platform: rpi_gpio
+  doors:
+    - relay_pin: 10
+      state_pin: 11
+      name: 'Left door'
+    - relay_pin: 12
+      state_pin: 13
+      name: 'Right door'
+
    +
    +
    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/garage_door.wink/index.html b/components/garage_door.wink/index.html index 401c63a6c2..a3a9e45898 100644 --- a/components/garage_door.wink/index.html +++ b/components/garage_door.wink/index.html @@ -157,9 +157,15 @@
  • MQTT Garage door
    • +
  • + Raspberry Pi Garage door +
  • Wink Garage door
    • +
  • + Z-Wave Garage Door +
    • diff --git a/components/garage_door.zwave/index.html b/components/garage_door.zwave/index.html new file mode 100644 index 0000000000..d00c33461f --- /dev/null +++ b/components/garage_door.zwave/index.html @@ -0,0 +1,200 @@ + + + + + + + + + + Z-Wave Garage Door - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Z-Wave Garage Door +

    +
    +
    + + +

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

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/garage_door/index.html b/components/garage_door/index.html index 1838f1c4ae..98da8e1740 100644 --- a/components/garage_door/index.html +++ b/components/garage_door/index.html @@ -111,9 +111,15 @@
  • MQTT Garage door
    • +
  • + Raspberry Pi Garage door +
  • Wink Garage door
    • +
  • + Z-Wave Garage Door +
    • diff --git a/components/hdmi_cec/index.html b/components/hdmi_cec/index.html new file mode 100644 index 0000000000..c1ef0f235c --- /dev/null +++ b/components/hdmi_cec/index.html @@ -0,0 +1,239 @@ + + + + + + + + + + HDMI CEC - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + HDMI CEC +

    +
    +
    + + +

    The CEC component provides services that allow selecting the active device, powering on all devices, and setting all devices to standby. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use cec-client (part of the libcec package) to listen to traffic on the CEC bus and discover the correct numbers.

    + +

    CEC Setup

    + +

    Adapter

    + +

    The computer running Home Assistant must support CEC, and of course be connected via HDMI to a device also supporting CEC. You can purchase a USB CEC adapter to add support if necessary. Note that all Raspberry Pi models support CEC natively.

    + +

    libcec

    + +

    libcec must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. libcec installs Python 3 bindings, by default as a system Python module. If you are running Home Assistant in a Python virtual environment, make sure it can access the system module, by either symlinking it or using the --system-site-packages flag.

    + +

    Configuration Example

    + +

    In the following example, a Pi Zero running Home Assistant is on a TV’s HDMI port 1. HDMI port 2 is attached to a AV receiver. Three devices are attached to the AV receiver on HDMI ports 1 through 3.
    +yaml +hdmi_cec: + devices: + 1: Pi Zero + 2: + 1: Fire TV Stick + 2: Chromecast + 3: Another Device +

    + +

    Services

    + +

    Select Device

    + +

    Call the hdmi_cec/select_device service with the name of the device to select, for example:

    + +
    + 
    {
+  "device": "Chromecast"
+}
+
    +
    +
    + +

    Power On

    + +

    Call the hdmi_cec/power_on service (no arguments) to power on any devices that support this function.

    + +

    Standby

    + +

    Call the hdmi_cec/standby service (no arguments) to place in standby any devices that support this function.

    + +

    Useful References

    + + + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/homematic/index.html b/components/homematic/index.html new file mode 100644 index 0000000000..9f424058b0 --- /dev/null +++ b/components/homematic/index.html @@ -0,0 +1,319 @@ + + + + + + + + + + Homematic - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Homematic +

    +
    +
    + + +

    The Homematic component provides bi-directional communication of Homematic platforms with their real world counterparts. This implementation does in no way modify your existing setup. Instead it queries your setup for its devices and subscribes to them to send and receive events.

    + +

    Device support is currently available for most of:

    + +
      +
    • Switch/Dimmer-actors
      • +
    • Thermostats
      • +
    • Rollershutters
      • +
    • Sensors (shutter contacts, motion detectors, power meters and more)
      • +
    • Simple remote controls
      • +
    + +

    If you want to see if a specific device you have is supported, head over to the pyhomematic repository and browse through the sourcecode. A dictionary with the device identifiers (e.g. HM-Sec-SC-2) can be found within the relevant modules near the bottom.

    + +

    We automatically detect all devices we currently support and try to generate useful names. If you enable name-resolving, we try to fetch names from Metadata (Homegear), via JSON-RPC or the XML-API you may have installed on your CCU. Since this may fail this is disabled by default.
    +You can manually override the created entities be using Home Assistants Customizing feature. With it you are able to hide entities you don’t need to see within the UI.

    + +

    To set up the component, add the following information to your configuration.yaml file:

    + +
    + 
    homematic:
+  local_ip: 127.0.0.1
+  local_port: 8943
+  remote_ip: 127.0.0.1
+  remote_port: 2001
+
    +
    +
    + +

    Configuration variables:

    + +
      +
    • local_ip (Required): IP of device running Home Assistant
      • +
    • local_port (Optional): Port for connection with Home Assistant. Defaults to 8943.
      • +
    • remote_ip (Required): IP of CCU/Homegear
      • +
    • remote_port (Required): Port of Homegear/CCU XML-RPC Server (usually 2001)
      • +
    • resolvenames (Optional): <metadata, json, xml> Try to fetch device names. Defaults to False if not specified.
      • +
    • username (Optional): When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.
      • +
    • password (Optional): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.
      • +
    • delay (Optional): Delay fetching of current state per deivce on startup. Used to prevent overloading of the CCU. Defaults to 0.5.
      • +
    + +

    To further explain the resolvenames option:
    +We use three approaches to fetch the names of devices. Each assumes you have properly named your devices in your existing Homematic setup. As a general advice: Use ASCII for your devices names. Home Assistant won’t include non-ASCII characters in entity-names.

    + +
      +
    1. The CCU allows to fetch details of the paired devices via JSON-RPC. For this to work you need to add valid credentials to your component-configuration. Guest-access is sufficient to query for device names.
      2. +
    2. If you use a regular CCU, there is an add-on called the “XML-API”. With it installed, you are able to fetch all kinds of information from you CCU using XML-RPC. We can leverage this and fetch the names of devices set within the CCU. We don’t support authentication with this method.
      3. +
    3. Homegear provides device-names through the metadata devices internally have. When using an HM-CFG-LAN interface, you typically use a configuration software (“HomeMatic-Komponenten konfigurieren” is the name of the shortcut on your desktop by default) to pair and configure your devices. If you have paired devices, you’ll see them listed in a table. The leftmost column (Name) is prefilled with default names. You can click such a name and enter whatever you like.
      4. +
    + +

    Resolving names can take some time. So when you start Home Assistant you won’t see you devices at first. For a setup with 20+ devices it can take up to a minute until all devices show up in the UI.

    + +

    Devices with buttons

    + +

    Devices with buttons (e.g. HM-Sen-MDIR-WM55, remote controls) may not be fully visible in the UI. This is intended, as buttons don’t serve any value here and all they do is trigger events.
    +As an example:
    +The HM-Sen-MDIR-WM55 motion detector will be displayed as 2 entities. A motion sensor and a brightness sensor. On top of that we have 2 sets (one set per button) of 4 events: PRESS_SHORT, PRESS_LONG, PRESS_CONT, PRESS_LONG_RELEASE. Be aware, that there are devices which don’t provide all of these events. But in general: if you can press it, it at least has PRESS_SHORT.
    +Here’s an example of how to use these events for automations:

    + +
    + 
    automation:
+   trigger:
+     platform: event
+     event_type: homematic.keypress
+     event_data:
+       name: Kitchen Switch
+       channel: 1
+       param: PRESS_SHORT
+   action:
+     service: switch.turn_on
+     entity_id: switch.Kitchen_Ambience
+
+
    +
    +
    + +

    The channel parameter is equal to the channel of the button you are configuring the automation for. You can view the available channels in the UI you use to pair your devices.
    +The name depends on if you chose to resolve names or not. If not, it will be the device ID (e.g. LEQ1234657). If you chose to resolve names (and that is successful), it will be the name you have set in your CCU or in the metadata (e.g. “Kitchen Switch”).

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/http/index.html b/components/http/index.html index 536b2a88d8..05d5e491e0 100644 --- a/components/http/index.html +++ b/components/http/index.html @@ -187,6 +187,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/hvac.zwave/index.html b/components/hvac.zwave/index.html index 6f749b636a..2abc6a305b 100644 --- a/components/hvac.zwave/index.html +++ b/components/hvac.zwave/index.html @@ -123,12 +123,18 @@
  • Z-Wave Binary Sensor
    • +
  • + Z-Wave Garage Door +
  • Z-Wave Light
  • Z-Wave Lock
    • +
  • + Z-Wave Rollershutter +
  • Z-Wave Sensor
    • diff --git a/components/ifttt/index.html b/components/ifttt/index.html index 822f201889..75a0618911 100644 --- a/components/ifttt/index.html +++ b/components/ifttt/index.html @@ -200,6 +200,9 @@ You need to setup a unique trigger for each event you sent to IFTTT.
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/index.html b/components/index.html index dcc73fd8e2..3f570a4292 100644 --- a/components/index.html +++ b/components/index.html @@ -1042,6 +1042,48 @@ Support for these components is provided by the Home Assistant community. + + + + + + + + + + + + + + + + + + +
    + + + +
    +
    Homematic
    +
    Hub
    +     + + + + + + + + + + + + + + + + + + + + @@ -2450,6 +2588,20 @@ Support for these components is provided by the Home Assistant community. + + + + + + + @@ -2960,6 +3126,20 @@ Support for these components is provided by the Home Assistant community. + + + + + + + + + + + + + + + + + + + + + + + + +
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/input_select/index.html b/components/input_select/index.html index 69e601ffbe..6bb8c81178 100644 --- a/components/input_select/index.html +++ b/components/input_select/index.html @@ -150,6 +150,9 @@
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/input_slider/index.html b/components/input_slider/index.html index c152a8b79d..630d722bda 100644 --- a/components/input_slider/index.html +++ b/components/input_slider/index.html @@ -141,6 +141,9 @@
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/insteon_hub/index.html b/components/insteon_hub/index.html index e5cd045795..8d13e7af01 100644 --- a/components/insteon_hub/index.html +++ b/components/insteon_hub/index.html @@ -147,6 +147,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/introduction/index.html b/components/introduction/index.html index c9af56a32b..556e34af72 100644 --- a/components/introduction/index.html +++ b/components/introduction/index.html @@ -151,6 +151,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/isy994/index.html b/components/isy994/index.html index d4124f7f54..3cfb16ca94 100644 --- a/components/isy994/index.html +++ b/components/isy994/index.html @@ -208,6 +208,9 @@ The ISY994 controller is manufactured by + + + + + + + + Homematic Light - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Homematic Light +

    +
    +
    + + +

    The homematic light platform lets you control Homematic lights through Home Assistant.

    + +

    Devices will be configured automatically. Please refer to the component configuration on how to setup Homematic.

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/light.hue/index.html b/components/light.hue/index.html index 1bece60884..1cf2134d12 100644 --- a/components/light.hue/index.html +++ b/components/light.hue/index.html @@ -148,6 +148,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.hyperion/index.html b/components/light.hyperion/index.html index 75d4f74a69..80a30ee34b 100644 --- a/components/light.hyperion/index.html +++ b/components/light.hyperion/index.html @@ -136,6 +136,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.lifx/index.html b/components/light.lifx/index.html index 16c4eb618c..8972e342ff 100644 --- a/components/light.lifx/index.html +++ b/components/light.lifx/index.html @@ -146,6 +146,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.limitlessled/index.html b/components/light.limitlessled/index.html index 8c0482b0f2..6516be2409 100644 --- a/components/light.limitlessled/index.html +++ b/components/light.limitlessled/index.html @@ -209,6 +209,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.mqtt/index.html b/components/light.mqtt/index.html index ee1c8a11a7..6f204551de 100644 --- a/components/light.mqtt/index.html +++ b/components/light.mqtt/index.html @@ -230,6 +230,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.mysensors/index.html b/components/light.mysensors/index.html index 3d0830e716..735bebb05d 100644 --- a/components/light.mysensors/index.html +++ b/components/light.mysensors/index.html @@ -265,6 +265,9 @@ MyMessage rgbMsg(CHILD_ID, V_RGB);
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.osramlightify/index.html b/components/light.osramlightify/index.html index 0b75e78192..aa6efb6532 100644 --- a/components/light.osramlightify/index.html +++ b/components/light.osramlightify/index.html @@ -141,6 +141,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.qwikswitch/index.html b/components/light.qwikswitch/index.html index f59410dd6b..76d90bdbd4 100644 --- a/components/light.qwikswitch/index.html +++ b/components/light.qwikswitch/index.html @@ -142,6 +142,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.rfxtrx/index.html b/components/light.rfxtrx/index.html index 50ce704c54..4a2697b396 100644 --- a/components/light.rfxtrx/index.html +++ b/components/light.rfxtrx/index.html @@ -198,6 +198,9 @@ Then you should update your configuration to:

  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.scsgate/index.html b/components/light.scsgate/index.html index 7b691b6480..ae61e1f9b8 100644 --- a/components/light.scsgate/index.html +++ b/components/light.scsgate/index.html @@ -160,6 +160,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.tellstick/index.html b/components/light.tellstick/index.html index 75cc29a7e0..bd8b16d006 100644 --- a/components/light.tellstick/index.html +++ b/components/light.tellstick/index.html @@ -150,6 +150,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.vera/index.html b/components/light.vera/index.html index 10096b2737..0e25f87e1b 100644 --- a/components/light.vera/index.html +++ b/components/light.vera/index.html @@ -128,6 +128,9 @@
  • Vera Binary Sensor
    • +
  • + Vera Lock +
  • Vera Sensor
    • @@ -148,6 +151,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.wemo/index.html b/components/light.wemo/index.html index d460adb8b9..89047ade87 100644 --- a/components/light.wemo/index.html +++ b/components/light.wemo/index.html @@ -145,6 +145,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.wink/index.html b/components/light.wink/index.html index 8b39f8db87..a72d389d24 100644 --- a/components/light.wink/index.html +++ b/components/light.wink/index.html @@ -151,6 +151,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.zigbee/index.html b/components/light.zigbee/index.html index f000552c74..bd8482c65e 100644 --- a/components/light.zigbee/index.html +++ b/components/light.zigbee/index.html @@ -163,6 +163,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light.zwave/index.html b/components/light.zwave/index.html index edc578e64c..22292fbd47 100644 --- a/components/light.zwave/index.html +++ b/components/light.zwave/index.html @@ -120,12 +120,18 @@
  • Z-Wave Binary Sensor
    • +
  • + Z-Wave Garage Door +
  • Z-Wave HVAC
  • Z-Wave Lock
    • +
  • + Z-Wave Rollershutter +
  • Z-Wave Sensor
    • @@ -149,6 +155,9 @@
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/light/index.html b/components/light/index.html index a3d07798c0..617806e0ab 100644 --- a/components/light/index.html +++ b/components/light/index.html @@ -254,6 +254,9 @@ The light component supports multiple entries in configuration.yaml
  • EnOcean Light
    • +
  • + Homematic Light +
  • Hyperion
    • diff --git a/components/lirc/index.html b/components/lirc/index.html index 9ea70e03d1..c8d6277c4c 100644 --- a/components/lirc/index.html +++ b/components/lirc/index.html @@ -210,6 +210,9 @@ If you are on a Debian based system (like Raspberry Pi) and are having issues lo
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/lock.mqtt/index.html b/components/lock.mqtt/index.html index cc3427df9b..1bb262df0a 100644 --- a/components/lock.mqtt/index.html +++ b/components/lock.mqtt/index.html @@ -201,6 +201,9 @@ Make sure that your topic match exact. some-topic/ and some-t
  • MQTT Lock
    • +
  • + Vera Lock +
  • Verisure Lock
    • diff --git a/components/lock.vera/index.html b/components/lock.vera/index.html new file mode 100644 index 0000000000..127a731ab9 --- /dev/null +++ b/components/lock.vera/index.html @@ -0,0 +1,195 @@ + + + + + + + + + + Vera Lock - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Vera Lock +

    +
    +
    + + +

    The vera platform allows you to control your Vera locks from within Home Assistant.

    + +

    They will be automatically discovered if the vera component is loaded.

    + +

    For more configuration information see the Vera component documentation.

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/lock.verisure/index.html b/components/lock.verisure/index.html index 5f8ab1b889..ccebf2a16e 100644 --- a/components/lock.verisure/index.html +++ b/components/lock.verisure/index.html @@ -140,6 +140,9 @@
  • MQTT Lock
    • +
  • + Vera Lock +
  • Verisure Lock
    • diff --git a/components/lock.wink/index.html b/components/lock.wink/index.html index 1bd061321b..648d6ecca9 100644 --- a/components/lock.wink/index.html +++ b/components/lock.wink/index.html @@ -149,6 +149,9 @@
  • MQTT Lock
    • +
  • + Vera Lock +
  • Verisure Lock
    • diff --git a/components/lock.zwave/index.html b/components/lock.zwave/index.html index ebfdefe0fd..a87d71c787 100644 --- a/components/lock.zwave/index.html +++ b/components/lock.zwave/index.html @@ -123,12 +123,18 @@
  • Z-Wave Binary Sensor
    • +
  • + Z-Wave Garage Door +
  • Z-Wave HVAC
  • Z-Wave Light
    • +
  • + Z-Wave Rollershutter +
  • Z-Wave Sensor
    • @@ -146,6 +152,9 @@
  • MQTT Lock
    • +
  • + Vera Lock +
  • Verisure Lock
    • diff --git a/components/lock/index.html b/components/lock/index.html index 2e6458cd24..35539dd426 100644 --- a/components/lock/index.html +++ b/components/lock/index.html @@ -143,6 +143,9 @@
  • MQTT Lock
    • +
  • + Vera Lock +
  • Verisure Lock
    • diff --git a/components/logger/index.html b/components/logger/index.html index b4fa40f476..20a1022f1d 100644 --- a/components/logger/index.html +++ b/components/logger/index.html @@ -184,6 +184,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/media_player.braviatv/index.html b/components/media_player.braviatv/index.html new file mode 100644 index 0000000000..d9078c4525 --- /dev/null +++ b/components/media_player.braviatv/index.html @@ -0,0 +1,249 @@ + + + + + + + + + + Sony Bravia TV - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Sony Bravia TV +

    +
    +
    + + +

    The braviatv platform allows you to control a Sony Bravia TV.

    + +

    Almost all Sony Bravia TV 2013 and newer are supported.

    + +

    You will need to configure your TV to allow the Home Assistant for remote usage. To do that, ensure that your TV is turned on. Open the configuration popup on Home Assistant and enter a random PIN (for example 0000). After that, the TV will show you a PIN and Home Assistant will allow you to re-enter that PIN. Enter the PIN shown on your TV and Home Assistant will be able to control your Sony Bravia TV.

    + +

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

    + +
    + 
    # Example configuration.yaml entry
+media_player:
+  platform: braviatv
+  host: 192.168.0.10
+  name: Living Room TV
+
    +
    +
    + +

    Configuration variables:

    + +
      +
    • host (Required): The IP of the Sony Bravia TV, eg. 192.168.0.10
      • +
    • name (Optional): The name to use on the frontend.
      • +
    + + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/media_player.cast/index.html b/components/media_player.cast/index.html index 95f2350814..8ae0da63a9 100644 --- a/components/media_player.cast/index.html +++ b/components/media_player.cast/index.html @@ -185,12 +185,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.cmus/index.html b/components/media_player.cmus/index.html new file mode 100644 index 0000000000..b1d5b5dba7 --- /dev/null +++ b/components/media_player.cmus/index.html @@ -0,0 +1,253 @@ + + + + + + + + + + cmus - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Cmus +

    +
    +
    + + +

    The cmus platform allows you to control a cmus music player on a remote or local machine from Home Assistant.

    + +

    To add cmus to your installation, add the following to your configuration.yaml file if cmus is running on a remote server:

    + +
    + 
    # Example configuration.yaml entry
+media_player:
+  platform: cmus
+  host: IP_ADDRESS
+  port: 3000
+  password: PASSWORD
+  name: Desktop Computer Music Player
+
    +
    +
    + +

    if running locally it will look like:
    +yaml +# Example configuration.yaml entry +media_player: + platform: cmus + name: Local Music Player +

    + +

    Configuration variables:

    + +
      +
    • host Hostname or IP address of the machine running cmus. Note if a remote
      +cmus is configured that instance must be configured to listen to remote connections, which also requires a password to be set.
      • +
    • password (Required if host is set): Password for your cmus player.
      • +
    • port (Optional): Port of the cmus socket, defaults to 3000.
      • +
    • name (Optional): The name you’d like to give the cmus player in Home Assistant
      • +
    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/media_player.denon/index.html b/components/media_player.denon/index.html index 3036519483..12201b2591 100644 --- a/components/media_player.denon/index.html +++ b/components/media_player.denon/index.html @@ -204,12 +204,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html index 70afa8103f..af2cdb8a20 100644 --- a/components/media_player.firetv/index.html +++ b/components/media_player.firetv/index.html @@ -224,12 +224,18 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.gpmdp/index.html b/components/media_player.gpmdp/index.html index 2dc7b38641..d797e5bb58 100644 --- a/components/media_player.gpmdp/index.html +++ b/components/media_player.gpmdp/index.html @@ -196,12 +196,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.itunes/index.html b/components/media_player.itunes/index.html index b50c655ce4..e39e8571d8 100644 --- a/components/media_player.itunes/index.html +++ b/components/media_player.itunes/index.html @@ -193,12 +193,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.kodi/index.html b/components/media_player.kodi/index.html index 77e8495786..caed6347d6 100644 --- a/components/media_player.kodi/index.html +++ b/components/media_player.kodi/index.html @@ -198,12 +198,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.lg_netcast/index.html b/components/media_player.lg_netcast/index.html index ffa2812198..280236edc0 100644 --- a/components/media_player.lg_netcast/index.html +++ b/components/media_player.lg_netcast/index.html @@ -204,12 +204,18 @@ The access token will not change until you factory reset your TV.
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.mpd/index.html b/components/media_player.mpd/index.html index 71b6790809..41bf7de7f8 100644 --- a/components/media_player.mpd/index.html +++ b/components/media_player.mpd/index.html @@ -197,12 +197,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.onkyo/index.html b/components/media_player.onkyo/index.html index 813984d41d..c790a68f12 100644 --- a/components/media_player.onkyo/index.html +++ b/components/media_player.onkyo/index.html @@ -220,12 +220,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.panasonic_viera/index.html b/components/media_player.panasonic_viera/index.html index 02ca988933..5ba15bd82b 100644 --- a/components/media_player.panasonic_viera/index.html +++ b/components/media_player.panasonic_viera/index.html @@ -201,12 +201,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.pandora/index.html b/components/media_player.pandora/index.html index 127bcd8b91..20766dc712 100644 --- a/components/media_player.pandora/index.html +++ b/components/media_player.pandora/index.html @@ -226,12 +226,18 @@ user = you@youraccount.com
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.pioneer/index.html b/components/media_player.pioneer/index.html index 0b1a2dc43d..bef10aff18 100644 --- a/components/media_player.pioneer/index.html +++ b/components/media_player.pioneer/index.html @@ -191,12 +191,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.plex/index.html b/components/media_player.plex/index.html index 9cf6360cb4..467ba6bf19 100644 --- a/components/media_player.plex/index.html +++ b/components/media_player.plex/index.html @@ -207,12 +207,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.roku/index.html b/components/media_player.roku/index.html index 0ea5451ad3..24b2b80e4c 100644 --- a/components/media_player.roku/index.html +++ b/components/media_player.roku/index.html @@ -188,12 +188,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html index 67223fdf7d..1605b18f37 100644 --- a/components/media_player.samsungtv/index.html +++ b/components/media_player.samsungtv/index.html @@ -208,12 +208,18 @@ The two letters at the beginning of the model number represent the region, UE is
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.snapcast/index.html b/components/media_player.snapcast/index.html index dc12dcb849..4d018156e6 100644 --- a/components/media_player.snapcast/index.html +++ b/components/media_player.snapcast/index.html @@ -180,12 +180,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.sonos/index.html b/components/media_player.sonos/index.html index 92305c8c5c..f6960de2fb 100644 --- a/components/media_player.sonos/index.html +++ b/components/media_player.sonos/index.html @@ -198,12 +198,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.squeezebox/index.html b/components/media_player.squeezebox/index.html index e96d82e141..62f68c6ac9 100644 --- a/components/media_player.squeezebox/index.html +++ b/components/media_player.squeezebox/index.html @@ -195,12 +195,18 @@ This lets you control Squeezebox hardware like the Classic, Transporter, Duet, B
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.universal/index.html b/components/media_player.universal/index.html index 6cc7a3abb8..b74f48516e 100644 --- a/components/media_player.universal/index.html +++ b/components/media_player.universal/index.html @@ -258,12 +258,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.webostv/index.html b/components/media_player.webostv/index.html index cdb1814363..3f4489872b 100644 --- a/components/media_player.webostv/index.html +++ b/components/media_player.webostv/index.html @@ -205,12 +205,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player.yamaha/index.html b/components/media_player.yamaha/index.html index 8cdda1ae73..5f7e900944 100644 --- a/components/media_player.yamaha/index.html +++ b/components/media_player.yamaha/index.html @@ -206,12 +206,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/media_player/index.html b/components/media_player/index.html index 32ef829f11..c6b2890cb9 100644 --- a/components/media_player/index.html +++ b/components/media_player/index.html @@ -285,12 +285,18 @@
  • Sonos
    • +
  • + Sony Bravia TV +
  • Universal
  • Yamaha Network Receivers
    • +
  • + cmus +
  • iTunes
    • diff --git a/components/modbus/index.html b/components/modbus/index.html index d2bf5bb22a..dc0f63a953 100644 --- a/components/modbus/index.html +++ b/components/modbus/index.html @@ -197,6 +197,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/mqtt/index.html b/components/mqtt/index.html index 52a90ae3a5..d5515cf9d3 100644 --- a/components/mqtt/index.html +++ b/components/mqtt/index.html @@ -486,6 +486,9 @@ Home Assistant will automatically load the correct certificate if you connect to
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/mqtt_eventstream/index.html b/components/mqtt_eventstream/index.html index 325ecc7d1e..4cbfb62b06 100644 --- a/components/mqtt_eventstream/index.html +++ b/components/mqtt_eventstream/index.html @@ -162,6 +162,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/mysensors/index.html b/components/mysensors/index.html index 9c4fd70097..091f69414e 100644 --- a/components/mysensors/index.html +++ b/components/mysensors/index.html @@ -211,6 +211,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/nest/index.html b/components/nest/index.html index aec0c14cad..47f83387e7 100644 --- a/components/nest/index.html +++ b/components/nest/index.html @@ -158,6 +158,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/netatmo/index.html b/components/netatmo/index.html index 29ab078305..5199ea3328 100644 --- a/components/netatmo/index.html +++ b/components/netatmo/index.html @@ -185,6 +185,9 @@ The Home Assistant NetAtmo platform has only be tested with the classic indoor,
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/octoprint/index.html b/components/octoprint/index.html index 04187ab9d9..89b688e50a 100644 --- a/components/octoprint/index.html +++ b/components/octoprint/index.html @@ -156,6 +156,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/persistent_notification/index.html b/components/persistent_notification/index.html new file mode 100644 index 0000000000..5c0689fbcc --- /dev/null +++ b/components/persistent_notification/index.html @@ -0,0 +1,261 @@ + + + + + + + + + + Persistent notification - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Persistent Notification +

    +
    +
    + + +

    The persistant_notification can be used to show a message on the frontend that has to be dismissed by the user.

    + +

    + +

    + +

    Service

    + +

    The service persistent_notification/create takes in message, title, and notification_id.

    + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Service data attributeOptionalDescription
    messagenoBody of the notification.
    titleyesTitle of the notification.
    notification_idyesIf notification_id is given, it will overwrite the notification if there already was a notification with that ID.
    + +

    The persistant_notification component supports specifying templates for both the message and the title. This will allow you to use the current state of Home Assistant in your notifications.

    + +

    In an action of your automation setup it could look like this with a customized subject.

    + +
    + 
    action:
+  service: persistant_notification.create
+  data:
+    message: "Your message goes here"
+    title: "Custom subject"
+
    +
    +
    + +

    Create a persistant notification

    + +

    Choose service developer tool icon Services from the Developer Tools to call the persistant_notification service. Select persistant_notification/create from the list of Available services: and enter something like the sample below into the Service Data field and hit CALL SERVICE.

    + +
    + 
    {
+  "notification_id": "1234",
+  "title": "Sample notification",
+  "message": "This is a sample text"
+}
+
    +
    +
    +

    This will create the notification entry shown above.

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/qwikswitch/index.html b/components/qwikswitch/index.html index 797a76ed14..d8055ff85d 100644 --- a/components/qwikswitch/index.html +++ b/components/qwikswitch/index.html @@ -186,6 +186,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/rfxtrx/index.html b/components/rfxtrx/index.html index abbea29c75..22bd9015bb 100644 --- a/components/rfxtrx/index.html +++ b/components/rfxtrx/index.html @@ -165,6 +165,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/rollershutter.command_line/index.html b/components/rollershutter.command_line/index.html index bd612d2c7b..e19c19074f 100644 --- a/components/rollershutter.command_line/index.html +++ b/components/rollershutter.command_line/index.html @@ -172,6 +172,9 @@
  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -187,6 +190,9 @@
  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/thermostat.homematic/index.html b/components/rollershutter.homematic/index.html similarity index 60% rename from components/thermostat.homematic/index.html rename to components/rollershutter.homematic/index.html index 7d23c1b5b5..958b26ecf9 100644 --- a/components/thermostat.homematic/index.html +++ b/components/rollershutter.homematic/index.html @@ -7,26 +7,26 @@ - Homematic Thermostat - Home Assistant + Homematic Rollershutter - Home Assistant - + - + - + - + - + - - + + @@ -83,44 +83,15 @@

    - Homematic Thermostat + Homematic Rollershutter

    -

    The homematic thermostat platform let you control Homematic thermostat from Home Assistant. Currently there is support for Homematic (HM-TC-IT-WM-W-EU, HM-CC-RT-DN) thermostats using Homegear or Homematic central (CCU1/CCU2).

    - -

    To set it up, add the following information to your configuration.yaml file:

    - -
    - 
    thermostat:
-  platform: homematic
-  address: HOMEGEAR/CCU_ADDRESS
-  devices:
-    Livingroom 1:
-      id: DEVICE_SERIAL_NO
-    Livingroom 2:
-      id: DEVICE_SERIAL_NO
-
    -
    -
    - -

    Configuration variables:

    - -
      -
    • address (Required: Adress of your Homegear or Homeatic central, eg. http://localhost:2001
      • -
    • devices array (Required): List of all your Homeatic devices. -
        -
      • name (Required): Name to identify the device. -
          -
        • id (Required): The serial number of the device, eg. MEQ0791521
          • -
        -
        • -
      -
      • -
    +

    The homematic rollershutter platform lets you control Homematic rollershutters through Home Assistant.

    +

    Devices will be configured automatically. Please refer to the component configuration on how to setup Homematic.

    @@ -134,49 +105,66 @@
    -
    Edit this page on GitHub
    +
    Edit this page on GitHub
    - Introduced in release: 0.9 + IoT class: Local Push +
    +
    + Introduced in release: 0.23
    This is a platform for - the Thermostats component. + the Rollershutters component. +
    +
    +

    Related components

    +
    -

    Category Thermostat

    +

    Category Rollershutter

    diff --git a/components/rollershutter.mqtt/index.html b/components/rollershutter.mqtt/index.html index 8e5be14859..2b17e12a3c 100644 --- a/components/rollershutter.mqtt/index.html +++ b/components/rollershutter.mqtt/index.html @@ -193,6 +193,9 @@
  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -208,6 +211,9 @@
  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/rollershutter.rfxtrx/index.html b/components/rollershutter.rfxtrx/index.html index 5ad81fca2a..67bbfa4f97 100644 --- a/components/rollershutter.rfxtrx/index.html +++ b/components/rollershutter.rfxtrx/index.html @@ -197,6 +197,9 @@ Then you should update your configuration to:

  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -212,6 +215,9 @@ Then you should update your configuration to:

  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/rollershutter.scsgate/index.html b/components/rollershutter.scsgate/index.html index 0231fbc9d4..07d80e289a 100644 --- a/components/rollershutter.scsgate/index.html +++ b/components/rollershutter.scsgate/index.html @@ -153,6 +153,9 @@
  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -168,6 +171,9 @@
  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/rollershutter.wink/index.html b/components/rollershutter.wink/index.html index eff54a84ef..9fa279e7ff 100644 --- a/components/rollershutter.wink/index.html +++ b/components/rollershutter.wink/index.html @@ -151,6 +151,9 @@
  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -166,6 +169,9 @@
  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/rollershutter.zwave/index.html b/components/rollershutter.zwave/index.html new file mode 100644 index 0000000000..33003713b6 --- /dev/null +++ b/components/rollershutter.zwave/index.html @@ -0,0 +1,212 @@ + + + + + + + + + + Z-Wave Rollershutter - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Z-Wave Rollershutter +

    +
    +
    + + +

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

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/components/rollershutter/index.html b/components/rollershutter/index.html index 0201a8378f..05699a6f10 100644 --- a/components/rollershutter/index.html +++ b/components/rollershutter/index.html @@ -111,6 +111,9 @@
  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -123,6 +126,9 @@
  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/scene.hunterdouglas_powerview/index.html b/components/scene.hunterdouglas_powerview/index.html index 5316ccd4f6..373dda3333 100644 --- a/components/scene.hunterdouglas_powerview/index.html +++ b/components/scene.hunterdouglas_powerview/index.html @@ -137,6 +137,9 @@
  • Command line Rollershutter
    • +
  • + Homematic Rollershutter +
  • MQTT Rollershutter
    • @@ -152,6 +155,9 @@
  • Wink Rollershutter
    • +
  • + Z-Wave Rollershutter +
    • diff --git a/components/script/index.html b/components/script/index.html index bf0bb43b80..7e6c5c76df 100644 --- a/components/script/index.html +++ b/components/script/index.html @@ -172,6 +172,9 @@
  • Automation
    • +
  • + HDMI CEC +
  • IFTTT
    • diff --git a/components/scsgate/index.html b/components/scsgate/index.html index 353fee20ce..aeae9bd8e9 100644 --- a/components/scsgate/index.html +++ b/components/scsgate/index.html @@ -166,6 +166,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/sensor.apcupsd/index.html b/components/sensor.apcupsd/index.html index b5d03b742e..76f4bb184c 100644 --- a/components/sensor.apcupsd/index.html +++ b/components/sensor.apcupsd/index.html @@ -246,6 +246,9 @@
  • Fitbit
    • +
  • + Fixer.io +
  • Glances
    • @@ -255,6 +258,9 @@
  • HTTP Sensor
    • +
  • + Homematic Sensor +
  • Last.fm
    • @@ -288,6 +294,9 @@
  • One wire Sensor
    • +
  • + Open Exchange Rates +
  • Plex Sensor
    • @@ -315,6 +324,9 @@
  • Supervisord
    • +
  • + Swiss Hydrological Data +
  • Swiss Public Transport
    • @@ -357,6 +369,9 @@
  • Vera Sensor
    • +
  • + Vera Sensor +
  • Verisure Sensor
    • diff --git a/components/sensor.arest/index.html b/components/sensor.arest/index.html index 49ea8f0e13..3be31a7fda 100644 --- a/components/sensor.arest/index.html +++ b/components/sensor.arest/index.html @@ -244,6 +244,9 @@
  • Fitbit
    • +
  • + Fixer.io +
  • Glances
    • @@ -253,6 +256,9 @@
  • HTTP Sensor
    • +
  • + Homematic Sensor +
  • Last.fm
    • @@ -286,6 +292,9 @@
  • One wire Sensor
    • +
  • + Open Exchange Rates +
  • Plex Sensor
    • @@ -313,6 +322,9 @@
  • Supervisord
    • +
  • + Swiss Hydrological Data +
  • Swiss Public Transport
    • @@ -355,6 +367,9 @@
  • Vera Sensor
    • +
  • + Vera Sensor +
  • Verisure Sensor
    • diff --git a/components/sensor.bitcoin/index.html b/components/sensor.bitcoin/index.html index 2ae2fc31f4..7dda367a17 100644 --- a/components/sensor.bitcoin/index.html +++ b/components/sensor.bitcoin/index.html @@ -217,6 +217,9 @@
  • Fitbit
    • +
  • + Fixer.io +
  • Glances
    • @@ -226,6 +229,9 @@
  • HTTP Sensor
    • +
  • + Homematic Sensor +
  • Last.fm
    • @@ -259,6 +265,9 @@
  • One wire Sensor
    • +
  • + Open Exchange Rates +
  • Plex Sensor
    • @@ -286,6 +295,9 @@
  • Supervisord
    • +
  • + Swiss Hydrological Data +
  • Swiss Public Transport
    • @@ -328,6 +340,9 @@
  • Vera Sensor
    • +
  • + Vera Sensor +
  • Verisure Sensor
    • diff --git a/components/sensor.bloomsky/index.html b/components/sensor.bloomsky/index.html index 1f75d65b06..1c2489cd3d 100644 --- a/components/sensor.bloomsky/index.html +++ b/components/sensor.bloomsky/index.html @@ -199,6 +199,9 @@
  • Fitbit
    • +
  • + Fixer.io +
  • Glances
    • @@ -208,6 +211,9 @@
  • HTTP Sensor
    • +
  • + Homematic Sensor +
  • Last.fm
    • @@ -241,6 +247,9 @@
  • One wire Sensor
    • +
  • + Open Exchange Rates +
  • Plex Sensor
    • @@ -268,6 +277,9 @@
  • Supervisord
    • +
  • + Swiss Hydrological Data +
  • Swiss Public Transport
    • @@ -310,6 +322,9 @@
  • Vera Sensor
    • +
  • + Vera Sensor +
  • Verisure Sensor
    • diff --git a/components/sensor.command_line/index.html b/components/sensor.command_line/index.html index c683181df5..c2e2d3f886 100644 --- a/components/sensor.command_line/index.html +++ b/components/sensor.command_line/index.html @@ -296,6 +296,9 @@ print(response.json()[' Fitbit +
  • + Fixer.io +
  • Glances
    • @@ -305,6 +308,9 @@ print(response.json()[' HTTP Sensor +
  • + Homematic Sensor +
  • Last.fm
    • @@ -338,6 +344,9 @@ print(response.json()[' One wire Sensor +
  • + Open Exchange Rates +
  • Plex Sensor
    • @@ -365,6 +374,9 @@ print(response.json()[' Supervisord +
  • + Swiss Hydrological Data +
  • Swiss Public Transport
    • @@ -407,6 +419,9 @@ print(response.json()[' Vera Sensor +
  • + Vera Sensor +
  • Verisure Sensor
    • diff --git a/components/sensor.cpuspeed/index.html b/components/sensor.cpuspeed/index.html index bbd6a028c0..4de1bcded5 100644 --- a/components/sensor.cpuspeed/index.html +++ b/components/sensor.cpuspeed/index.html @@ -168,6 +168,9 @@
  • Fitbit
    • +
  • + Fixer.io +
  • Glances
    • @@ -177,6 +180,9 @@
  • HTTP Sensor
    • +
  • + Homematic Sensor +
  • Last.fm
    • @@ -210,6 +216,9 @@
  • One wire Sensor
    • +
  • + Open Exchange Rates +
  • Plex Sensor
    • @@ -237,6 +246,9 @@
  • Supervisord
    • +
  • + Swiss Hydrological Data +
  • Swiss Public Transport
    • @@ -279,6 +291,9 @@
  • Vera Sensor
    • +
  • + Vera Sensor +
  • Verisure Sensor
    • diff --git a/components/sensor.deutsche_bahn/index.html b/components/sensor.deutsche_bahn/index.html index 2647e2990f..355d9ea0fc 100644 --- a/components/sensor.deutsche_bahn/index.html +++ b/components/sensor.deutsche_bahn/index.html @@ -89,7 +89,7 @@
    -

    The deutsche_bahn sensor will give you the departure time of the next train for the given connection. In case of a delay, the delay is also shown. Additional ATTRIBUTES are used to inform about eg. the type of the train, price and if it is ontime. The data are coming from the bahn.de website.

    +

    The deutsche_bahn sensor will give you the departure time of the next train for the given connection. In case of a delay, the delay is also shown. Additional details are used to inform about eg. the type of the train, price, and if it is ontime.

    To enable this sensor, add the following lines to your configuration.yaml file:

    @@ -107,9 +107,24 @@
    • from (Required): The name of the start station.
      • -
    • to (Required): The name of the end station.
      • +
    • to (Required): The name of the end/destination station.
    +

    As already mentioned this sensor contains a lot of information to access those a template senosr can come handy.

    + +
    + 
    # Example configuration.yaml entry
+sensor:
+  platform: template
+  sensors:
+    next_departure:
+      value_template: '{{ states.sensor.munich_to_ulm.attributes.next }}'
+      friendly_name: 'Next departure'
+
    +
    +
    + +

    The data is coming from the bahn.de website.

    @@ -131,6 +146,9 @@ IoT class: Local Polling
    + Introduced in release: 0.14 +
    +

    Category Sensor

    @@ -180,6 +183,9 @@ If you are not running Raspbian Jessie, you will need to run Home Assistant as r
  • Hikvision Camera Switch
    • +
  • + Homematic Switch +
  • MQTT Switch
    • diff --git a/components/switch.rpi_rf/index.html b/components/switch.rpi_rf/index.html index 755b49ed41..d788fbf72e 100644 --- a/components/switch.rpi_rf/index.html +++ b/components/switch.rpi_rf/index.html @@ -186,6 +186,9 @@ For more info see the PyPi module description: Vera hub is a controller mainly connecting to Z-Wave devices.

    -

    Switches, Lights (inc Dimmers), Sensors and Binary sensors are supported - and will be automaticaly added when HA connects to your Vera controller.

    +

    Switches, Lights (inc Dimmers), Locks, Sensors and Binary sensors are supported - and will be automaticaly added when HA connects to your Vera controller.

    To use Vera devices in your installation, add the following to your configuration.yaml file using the IP and port number of your Vera controller:

    @@ -145,6 +145,9 @@
  • Vera Light
    • +
  • + Vera Lock +
  • Vera Sensor
    • @@ -171,6 +174,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/verisure/index.html b/components/verisure/index.html index 91ae5f9089..2a4512a3ec 100644 --- a/components/verisure/index.html +++ b/components/verisure/index.html @@ -188,6 +188,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/weblink/index.html b/components/weblink/index.html index 6e35c0189a..0b774fa56b 100644 --- a/components/weblink/index.html +++ b/components/weblink/index.html @@ -166,6 +166,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/wemo/index.html b/components/wemo/index.html index 94d04d39af..3cb949ccc4 100644 --- a/components/wemo/index.html +++ b/components/wemo/index.html @@ -163,6 +163,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/wink/index.html b/components/wink/index.html index 812e642bfd..feefacd980 100644 --- a/components/wink/index.html +++ b/components/wink/index.html @@ -182,6 +182,9 @@ The Wink hub can only be accessed via the cloud. This means it requires an activ
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/components/zeroconf/index.html b/components/zeroconf/index.html index 7097167cf4..ff2391ee2f 100644 --- a/components/zeroconf/index.html +++ b/components/zeroconf/index.html @@ -151,6 +151,9 @@
  • MQTT Eventstream
    • +
  • + Persistent notification +
  • UPnP
    • diff --git a/components/zwave/index.html b/components/zwave/index.html index bc8a0bb64f..df4d9fb03b 100644 --- a/components/zwave/index.html +++ b/components/zwave/index.html @@ -114,6 +114,9 @@
  • Z-Wave Binary Sensor
    • +
  • + Z-Wave Garage Door +
  • Z-Wave HVAC
    • @@ -123,6 +126,9 @@
  • Z-Wave Lock
    • +
  • + Z-Wave Rollershutter +
  • Z-Wave Sensor
    • @@ -152,6 +158,9 @@
  • EnOcean
    • +
  • + Homematic +
  • ISY994 Controller
    • diff --git a/getting-started/customizing-devices/index.html b/getting-started/customizing-devices/index.html index db6e064b7c..4aadbd88c1 100644 --- a/getting-started/customizing-devices/index.html +++ b/getting-started/customizing-devices/index.html @@ -123,6 +123,14 @@
    +

    Reloading customize

    + +

    Home Assistant offers a service to reload the core configuration while Home Assistant is running called homeassistant/reload_core_config. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the service developer tool icon service developer tools, select the service homeassistant/reload_core_config and click “Call Service”.

    + +

    +New customize information will be applied the next time the state of the entity gets updated. +

    +

    Next step: Setting up presence detection »

    diff --git a/images/screenshots/persistant-notification.png b/images/screenshots/persistant-notification.png new file mode 100644 index 0000000000..3988cbadc7 Binary files /dev/null and b/images/screenshots/persistant-notification.png differ diff --git a/images/supported_brands/bravia.png b/images/supported_brands/bravia.png new file mode 100644 index 0000000000..f36681a809 Binary files /dev/null and b/images/supported_brands/bravia.png differ diff --git a/images/supported_brands/eyezon.png b/images/supported_brands/eyezon.png new file mode 100644 index 0000000000..1dd698a885 Binary files /dev/null and b/images/supported_brands/eyezon.png differ diff --git a/images/supported_brands/fixer-io.png b/images/supported_brands/fixer-io.png new file mode 100644 index 0000000000..5559042b1f Binary files /dev/null and b/images/supported_brands/fixer-io.png differ diff --git a/images/supported_brands/openexchangerates.png b/images/supported_brands/openexchangerates.png new file mode 100644 index 0000000000..dbcf719dc4 Binary files /dev/null and b/images/supported_brands/openexchangerates.png differ diff --git a/index.html b/index.html index ca6d154f19..5cd2cfdfad 100644 --- a/index.html +++ b/index.html @@ -115,11 +115,11 @@ Home Assistant is an open-source home automation platform running on Python 3. T
    -

    Current Version: 0.22.1

    - Released: June 20, 2016 +

    Current Version: 0.23

    + Released: July 1, 2016
    - Release notes + Release notes
    @@ -138,21 +138,21 @@ Home Assistant is an open-source home automation platform running on Python 3. T

    Recent Blog Posts

    +
  • + 0.23: TBD (rename file too). + July 1, 2016 +
    • + +
  • + 0.23: Envisalink, Homematic, HDMI-CEC and CherryPi + July 1, 2016 +
    • +
  • Using USB webcams with Home Assistant June 23, 2016
    • -
  • - 0.22: Pandora, BT Home Hub 5 and local file camera. - June 18, 2016 -
    • - -
  • - Home Assistant at PyCon 2016 - June 13, 2016 -
    • -
    diff --git a/sitemap.xml b/sitemap.xml index 592c2bb96b..95c9aaf636 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1,5 +1,13 @@ + + https://home-assistant.io/blog/2016/07/01/tbd/ + 2016-07-01T00:31:00+00:00 + + + https://home-assistant.io/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi/ + 2016-07-01T00:31:00+00:00 + https://home-assistant.io/blog/2016/06/23/usb-webcams-and-home-assistant/ 2016-06-23T06:00:00+00:00 @@ -959,6 +967,12 @@ https://home-assistant.io/components/light.mqtt/ + + https://home-assistant.io/components/garage_door.zwave/ + + + https://home-assistant.io/components/rollershutter.zwave/ + https://home-assistant.io/components/sensor.zwave/ @@ -983,9 +997,6 @@ https://home-assistant.io/components/lock/ - - https://home-assistant.io/components/thermostat.homematic/ - https://home-assistant.io/components/switch.mystrom/ @@ -1202,6 +1213,9 @@ https://home-assistant.io/components/garage_door/ + + https://home-assistant.io/components/garage_door.rpi_gpio/ + https://home-assistant.io/components/garage_door.wink/ @@ -1508,9 +1522,63 @@ https://home-assistant.io/components/device_tracker.bt_home_hub_5/ + + https://home-assistant.io/components/sensor.swiss_hydrological_data/ + + + https://home-assistant.io/components/media_player.cmus/ + + + https://home-assistant.io/components/envisalink/ + + + https://home-assistant.io/components/sensor.fixer/ + + + https://home-assistant.io/components/sensor.openexchangerates/ + https://home-assistant.io/components/sensor.netatmo/ + + https://home-assistant.io/components/hdmi_cec/ + + + https://home-assistant.io/components/persistent_notification/ + + + https://home-assistant.io/components/binary_sensor.homematic/ + + + https://home-assistant.io/components/light.homematic/ + + + https://home-assistant.io/components/rollershutter.homematic/ + + + https://home-assistant.io/components/sensor.homematic/ + + + https://home-assistant.io/components/switch.homematic/ + + + https://home-assistant.io/components/homematic/ + + + https://home-assistant.io/components/lock.vera/ + + + https://home-assistant.io/components/alarm_control_panel.envisalink/ + + + https://home-assistant.io/components/binary_sensor.envisalink/ + + + https://home-assistant.io/components/media_player.braviatv/ + + + https://home-assistant.io/components/sensor.envisalink/ + https://home-assistant.io/cookbook/automation_for_rainy_days/ @@ -1604,6 +1672,9 @@ https://home-assistant.io/topics/splitting_configuration/ + + https://home-assistant.io/topics/secrets/ + https://home-assistant.io/blog/2014/12/18/website-launched/ @@ -1808,28 +1879,34 @@ https://home-assistant.io/blog/2016/06/23/usb-webcams-and-home-assistant/ + + https://home-assistant.io/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-cherrypi/ + + + https://home-assistant.io/blog/2016/07/01/tbd/ + https://home-assistant.io/demo/frontend.html - 2016-07-01T17:19:11+00:00 + 2016-07-01T18:45:16+00:00 https://home-assistant.io/demo/index.html - 2016-07-01T17:19:11+00:00 + 2016-07-01T18:45:16+00:00 https://home-assistant.io/googlef4f3693c209fe788.html - 2016-07-01T17:19:11+00:00 + 2016-07-01T18:45:16+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html - 2016-07-01T17:19:11+00:00 + 2016-07-01T18:45:16+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html - 2016-07-01T17:19:11+00:00 + 2016-07-01T18:45:16+00:00 https://home-assistant.io/static/mdi-demo.html - 2016-07-01T17:19:11+00:00 + 2016-07-01T18:45:16+00:00 diff --git a/topics/index.html b/topics/index.html index b7992429ab..8a70a4a479 100644 --- a/topics/index.html +++ b/topics/index.html @@ -106,6 +106,9 @@

  • State Objects

    • +
  • +

    Storing secrets

    +

  • Templating

    • diff --git a/topics/platform_options/index.html b/topics/platform_options/index.html index 4311ceab41..a583e191ea 100644 --- a/topics/platform_options/index.html +++ b/topics/platform_options/index.html @@ -184,6 +184,18 @@ diff --git a/topics/secrets/index.html b/topics/secrets/index.html new file mode 100644 index 0000000000..973411e48a --- /dev/null +++ b/topics/secrets/index.html @@ -0,0 +1,223 @@ + + + + + + + + + + Storing secrets - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + +
    Edit this page on GitHub
    + + + +
    +

    + Storing Secrets +

    +
    +
    + + +

    The configuration.yaml file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the configuration.yaml file) if you don’t want to split up your configuration.

    + +

    Using secrets.yaml

    + +

    The workflow for the outsourcing in the secrets.yaml are very similar to the splitting of the configuration. Create a secrets.yaml file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it’s ~/.homeassistant and on Windows it’s %APPDATA%/.homeassistant).

    + +

    The entries for password and API keys in the configuration.yaml file usally looks like the example below.

    + +
    + 
    http:
+  api_password: YOUR_PASSWORD
+
    +
    +
    + +

    Those entries need to be replaced with !secret and a identifier.

    + +
    + 
    http:
+  api_password: !secret http_password
+
    +
    +
    + +

    The secrets.yaml files stored the corresponding password assigned to the identifier.

    + +
    + 
    debug: 0
+http_password: YOUR_PASSWORD
+
    +
    +
    + +

    Python Keyring

    + +

    Using Keyring is an alternative way to secrets.yaml but requires that keyring is installed (incl. its command-line tools). This can be done with:

    + +
    + 
    $ pip3 install keyring
+
    +
    +
    + +

    Replaced your password or API key with !secret and an identifier in configuration.yaml file.

    + +
    + 
    http:
+  api_password: !secret http_password
+
    +
    +
    + +

    Create an entry in your keyring. The service (SERVICE) is homeassistant and the identifier is the USERNAME in the keyring context.

    + +
    + 
    $ keyring set homeassistant http_password
+Password for 'http_password' in 'homeassistant': 
+Please set a password for your new keyring: 
+Please confirm the password: 
+
    +
    +
    + +

    If the command-line tool keyring is not available, launch python3 and do the process manually.

    + +
    + 
    >>> import keyring
+>>> keyring.set_password("homeassistant", "http_password", "12345")
+Please set a password for your new keyring: 
+Please confirm the password: 
+>>> keyring.get_password("homeassistant", "http_password")
+'12345'
+>>> keyring.get_keyring()
+<EncryptedKeyring at /home/your_user/.local/share/python_keyring/crypted_pass.cfg>
+
    +
    +
    + +

    If you launch home Assistant now, you will be prompted for the keyring password to unlock your keyring.

    + +
    + 
    $ hass
+Config directory: /home/fab/.homeassistant
+Please enter password for encrypted keyring: 
+
    +
    +
    + +

    + With this configuration autostart will no longer work. +

    + + + +
    + + +
    + + +
    +
    + + + + + + \ No newline at end of file