Thanks to @pvizeli, all the core components are now written asynchronously. All entity components are now migrated from synchronously to asynchronously code!
+
+
+
Now when you restart Home Assistant using the homeassistant.restart service, your configuration is checked. If it appears to be invalid the restart will fail.
+
+
+
+
Rewritten frontend
+
The frontend has been completely been rewritten, optimizing for speed and lost connection recovery. Even on the slowest phones it should fly now. The frontend also now uses the new WebSockets API instead of the EventStream API.
+
+
Custom state card UI
+
A nice new feature is the possibility to create custom state cards in the frondend. Go ahead and write your own state card for lights, sensors, locks, etc.
+
+
MQTT discovery
+
MQTT now has discovery support which is different than our discovery component. Similar to the HTTP sensor and HTTP binary sensor, MQTT discovery removes the need for configuration by allowing devices to make their presence known to Home Assistant.
+
+
Alert component
+
If you left your front door open, then the new alert component can be used to remind you of this by sending you repeating notifications at a given interval.
+
+
Yeelight
+
The yeelight component has been ported to use a more stable and feature-complete python-yeelight backend, and supports now both white and RGB bulbs. The component also supports transitions and can be configured to save the settings to the bulb on changes. The users currently using custom components for Yeelight are encouraged to move back to use the included version and report any problems with it to our issue tracker.
+
+
Apple TV
+
Apple TV is now a supported media_player! It has support for just about every media player function, including a realtime display of playback status and artwork.
The support for LG webOS Smart TVs was improved. This requires you to move $HOME/.pylgtv to $HASS_CONFIG_DIR/webostv.conf or Home Assistant will need to be paired with the TV again.
+
Image processing events have been renamed: identify_face has become image_processing.detect_face, found_plate has become image_processing.found_plate
+
The FFmpeg binary sensor change the platform name from ffmpeg to ffmpeg_noise and ffmpeg_motion. Also all FFmpeg-related services are moved from a platform implementation to a the FFmpeg components and were rename from binary_sensor.ffmpeg_xy to ffmpeg.xy.
+
+
+
If you need help…
+
…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+
+
Reporting Issues
+
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+
+]]>
+
+
@@ -1960,107 +2081,6 @@ You have to note:
If you need help…
…don’t hesitate to use our Forum or join us for a little chat.
-]]>
-
-
-
-
-
- 2016-08-31T04:17:25+00:00
- https://home-assistant.io/blog/2016/08/31/esp8266-and-micropython-part2
-
-So, part 1 of ESP8266 and MicroPython was pretty lame, right? Instead of getting information out of Home Assistant we are going a step forward and create our own sensor which is sending details about its state to a Home Assistant instance.
-
-
-
-
Beside HTTP POST requests, MQTT is the quickest way (from the author’s point of view) to publish information with DIY devices.
-
-
You have to make a decision: Do you want to pull or to poll the information for the sensor? For slowly changing values like temperature it’s perfectly fine to wait a couple of seconds to retrieve the value. If it’s a motion detector the state change should be available instantly in Home Assistant or it could be missed. This means the sensor must take initiative and send the data to Home Assistant.
-
-
An example for pulling is aREST. This is a great way to work with the ESP8266 based units and the Ardunio IDE.
-
-
MQTT
-
-
You can find a simple examples for publishing and subscribing with MQTT in the MicroPython library overview in the section for umqtt.
-
-
The example below is adopted from the work of @davea as we don’t want to re-invent the wheel. The configuration feature is crafty and simplyfies the code with the usage of a file called /config.json which stores the configuration details. The ESP8266 device will send the value of a pin every 5 seconds.
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 c9301a8316..24eaaf4ca4 100644
--- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
+++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
@@ -225,6 +225,12 @@ This article will try to explain how they all relate.
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index 6de8ee639a..69b8981734 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -201,6 +201,12 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index e1455445be..126836f9e0 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -177,6 +177,12 @@ The old logo, the new detailed logo and the new simple logo.
diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html
index 661f1b0dad..facdf28b6a 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -210,6 +210,12 @@ An initial version of voice control for Home Assistant has landed. The current i
diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html
index 95ad6b9cad..0236f85686 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -245,6 +245,12 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index c0bfa60417..7950028417 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -277,6 +277,12 @@ Before diving into the newly supported devices and services, I want to highlight
diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html
index 4f0c85207e..56fd82b8bf 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -328,6 +328,12 @@ This switch platform allows you to control your motion detection setting on your
diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
index c551579fa9..d007bd4b19 100644
--- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
+++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
@@ -284,6 +284,12 @@ Fabian has added support for Forecast.io to g
diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
index 9c3a53ae4c..3e33e67847 100644
--- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
+++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
@@ -269,6 +269,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -292,12 +298,6 @@ Support for Temper temperature sensors has been contributed by
- Numbers
-
-
-
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 796a56f8de..9682b842a2 100644
--- a/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
+++ b/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
@@ -193,6 +193,12 @@
diff --git a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
index ddabf830bb..a363e821cf 100644
--- a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
+++ b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
@@ -306,6 +306,12 @@ The automation and script syntax here is using a deprecated and no longer suppor
diff --git a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
index 48bac710b9..26c00d0eee 100644
--- a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
+++ b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
@@ -235,6 +235,12 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
index 9c2ccd8da7..d6cf8e3372 100644
--- a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
+++ b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
@@ -220,6 +220,12 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge
diff --git a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
index be4f8ef002..f23101faa7 100644
--- a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
+++ b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
@@ -200,6 +200,12 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index babbaf0e6a..873d4869a8 100644
--- a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
+++ b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
@@ -409,6 +409,12 @@ Home Assistant will keep track of historical values and allow you to integrate i
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index 22861e537c..6f392bde4e 100644
--- a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
+++ b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
@@ -211,6 +211,12 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index 26165a4609..1545cdb364 100644
--- a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
+++ b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
@@ -226,6 +226,12 @@ This is where we’ll configure our task, so select the plus icon to select an a
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index 1fec30ff0c..1cb70cb644 100644
--- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
+++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
@@ -209,6 +209,12 @@ Example of the new views in the frontend. Learn mor
diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html
index 86ec296438..311ea56200 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -220,6 +220,12 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
diff --git a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
index 929b693726..9a3e67049d 100644
--- a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
+++ b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
@@ -300,6 +300,12 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index d5c654f3ad..163a5f6e14 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -219,6 +219,12 @@ Over a year ago I participated in the
+
@@ -242,12 +248,6 @@ Over a year ago I participated in the
- Numbers
-
-
-
diff --git a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
index 0943d38901..d8bb99b8df 100644
--- a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
+++ b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
@@ -219,6 +219,12 @@
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 54c08a7988..64f5d1f729 100644
--- a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
+++ b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
@@ -236,6 +236,12 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index 6739181df2..d63d5bd2ac 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -323,6 +323,12 @@ If a module is missing then you need to download it from the
+
@@ -346,12 +352,6 @@ If a module is missing then you need to download it from the
- Numbers
-
-
-
diff --git a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
index 1f1dd1b628..fe04b98af3 100644
--- a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
+++ b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
@@ -238,6 +238,12 @@
diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
index 702120be4b..a19642826c 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -267,6 +267,12 @@ So, part 1 of ESP8266
diff --git a/blog/2017/01/14/iss-usps-images-packages/index.html b/blog/2017/01/14/iss-usps-images-packages/index.html
index 6d73712e08..1a6e922d3c 100644
--- a/blog/2017/01/14/iss-usps-images-packages/index.html
+++ b/blog/2017/01/14/iss-usps-images-packages/index.html
@@ -271,6 +271,12 @@ You have to note:
diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html
index 44a2090003..f9f9de3f1e 100644
--- a/blog/2017/02/03/babyphone/index.html
+++ b/blog/2017/02/03/babyphone/index.html
@@ -303,6 +303,12 @@ We change the platform name for binary sensor in 0.38 from
+
@@ -322,12 +328,6 @@ We change the platform name for binary sensor in 0.38 from
- Numbers
-
-
-
diff --git a/blog/2017/02/04/hassbian-toybox/index.html b/blog/2017/02/04/hassbian-toybox/index.html
index f776109aea..f47d234c52 100644
--- a/blog/2017/02/04/hassbian-toybox/index.html
+++ b/blog/2017/02/04/hassbian-toybox/index.html
@@ -217,6 +217,12 @@ On the close horizon from @Landrash th
Thanks to @pvizeli, all the core components are now written asynchronously. All entity components are now migrated from synchronously to asynchronously code!
+
+
+
Now when you restart Home Assistant using the homeassistant.restart service, your configuration is checked. If it appears to be invalid the restart will fail.
+
+
+
+
Rewritten frontend
+
The frontend has been completely been rewritten, optimizing for speed and lost connection recovery. Even on the slowest phones it should fly now. The frontend also now uses the new WebSockets API instead of the EventStream API.
+
+
Custom state card UI
+
A nice new feature is the possibility to create custom state cards in the frondend. Go ahead and write your own state card for lights, sensors, locks, etc.
+
+
MQTT discovery
+
MQTT now has discovery support which is different than our discovery component. Similar to the HTTP sensor and HTTP binary sensor, MQTT discovery removes the need for configuration by allowing devices to make their presence known to Home Assistant.
+
+
Alert component
+
If you left your front door open, then the new alert component can be used to remind you of this by sending you repeating notifications at a given interval.
+
+
Yeelight
+
The yeelight component has been ported to use a more stable and feature-complete python-yeelight backend, and supports now both white and RGB bulbs. The component also supports transitions and can be configured to save the settings to the bulb on changes. The users currently using custom components for Yeelight are encouraged to move back to use the included version and report any problems with it to our issue tracker.
+
+
Apple TV
+
Apple TV is now a supported media_player! It has support for just about every media player function, including a realtime display of playback status and artwork.
The support for LG webOS Smart TVs was improved. This requires you to move $HOME/.pylgtv to $HASS_CONFIG_DIR/webostv.conf or Home Assistant will need to be paired with the TV again.
+
Image processing events have been renamed: identify_face has become image_processing.detect_face, found_plate has become image_processing.found_plate
+
The FFmpeg binary sensor change the platform name from ffmpeg to ffmpeg_noise and ffmpeg_motion. Also all FFmpeg-related services are moved from a platform implementation to a the FFmpeg components and were rename from binary_sensor.ffmpeg_xy to ffmpeg.xy.
+
+
+
If you need help…
+
…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+
+
Reporting Issues
+
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+
+
+
+
+
Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/blog/archives/index.html b/blog/archives/index.html
index d81c4a9e2b..6edecd602b 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -3381,6 +3381,38 @@
+
+
+
+
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 06af4d107e..fef0afbed9 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2017-02-11T22:28:32+00:00
+ 2017-02-11T22:47:53+00:00https://home-assistant.io/
@@ -13,6 +13,200 @@
Octopress
+
+
+
+ 2017-02-11T08:04:05+00:00
+ https://home-assistant.io/blog/2017/02/11/alert-appletv-mqtt-yeelight
+ Core updates
+- Thanks to [@pvizeli], all the core components are now written asynchronously. All entity components are now migrated from synchronously to asynchronously code!
+
+- Now when you restart Home Assistant using the `homeassistant.restart` service, your configuration is checked. If it appears to be invalid the restart will fail.
+
+### Rewritten frontend
+The frontend has been completely been rewritten, optimizing for speed and lost connection recovery. Even on the slowest phones it should fly now. The frontend also now uses the new [WebSockets API][websocket-api] instead of the [EventStream API][event-stream-api].
+
+### Custom state card UI
+A nice new feature is the possibility to create [custom state cards][custom-ui] in the frondend. Go ahead and write your own state card for [lights][light], sensors, locks, etc.
+
+### MQTT discovery
+MQTT now has [discovery][mqtt-discovery] support which is different than our [`discovery`][discovery] component. Similar to the HTTP sensor and HTTP binary sensor, MQTT discovery removes the need for configuration by allowing devices to make their presence known to Home Assistant.
+
+### Alert component
+If you left your front door open, then the new [`alert`][alert] component can be used to remind you of this by sending you repeating notifications at a given interval.
+
+### Yeelight
+The [`yeelight`][yeelight] component has been ported to use a more stable and feature-complete [python-yeelight][python-yeelight] backend, and supports now both white and RGB bulbs. The component also supports transitions and can be configured to save the settings to the bulb on changes. The users currently using custom components for Yeelight are encouraged to move back to use the included version and report any problems with it to our [issue tracker][issue].
+
+### Apple TV
+[Apple TV][apple-tv] is now a supported [`media_player`][media-player]! It has support for just about every media player function, including a realtime display of playback status and artwork.
+
+### All changes
+#### New platforms/components
+
+- Sensor: Support for monitoring [OpenEVSE][openevse] chargers ([@miniconfig])
+- Voice command [API.AI][apiai] ([@adrianlzt])
+- [Alert][alert] Component ([@rmkraus])
+- [Rflink][rflink] 433Mhz gateway platform and components ([@aequitas])
+- Lock: Support for [Nuki.io][nuki] smart locks ([@pschmitt])
+- Sensor: [QNAP][qnap] Sensor ([@colinodell])
+- Switch: Add support for [FRITZ!DECT][fritz] wireless switches based on fritzhome ([@BastianPoe])
+- Sensor: Add [moon][moon] sensor ([@fabaff])
+- Media player: Support for the [Orange Livebox Play TV][orange] appliance ([@pschmitt])
+- Media player: [Apple TV][apple-tv] support ([@postlund])
+- MQTT: [MQTT discovery][mqtt-discovery] support ([@balloob], [@fabaff])
+- Notify: [Mailgun][mailgun] notify service ([@pschmitt])
+- Image Processing: Support [Microsoft Face detection][face-detect] ([@pvizeli])
+
+#### Improvements
+
+- Switch - Pilight: Validation no longer rejects alphanumeric IDs ([@DavidLP])
+- Device tracker - ASUSWrt: Fixes `ip neigh` regex to handle the possible IPv6 "router" flag ([@kylehendricks])
+- Light - MySensors: Fix mysensors RGB and W light turn on ([@MartinHjelmare])
+- Light - Yeelight: new yeelight backend lib, new features ([@rytilahti])
+- Climate - Eq3btsmart: Cleanup modes & available, bump version requirement ([@rytilahti])
+- Sensor - SMA: Handle units correctly ([@kellerza])
+- MQTT eventstream: Prevent infinite loop in cross configured MQTT event streams ([@aequitas])
+- Light - [Hue][hue]: Fix lightgroups not syncing state ([@tboyce1])
+- Dvice tracker - Owntracks: Fix OwnTracks state names ([@tboyce1])
+- Wink: Wink AC and additional sensor support ([@w1ll1am23])
+- Modbus: Modbus write_register accept list ([@benvm])
+- Device tracker - Ping: Add devices detected by ping as SOURCE_TYPE_ROUTER instead of GPS ([@michaelarnauts])
+- Climate - Ecobee: Cleanup climate and ecobee ([@Duoxilian])
+- Sensor - Miflora: Allow specification of bluetooth adapter ([@Danielhiversen])
+- Sensor - [Systemmonitor][systemmonitor]: Add average load to systemmonitor ([@eagleamon])
+- Sensor - [Openweathermap][owm]: Add wind bearing ([@fabaff])
+- Notify - Facebook: Allow to use data for enhanced messages ([@adrianlzt])
+- Light - Hyperion: Change CONF_DEFAULT_COLOR CV type ([@Joeboyc2])
+- Mysensors: Fix validation of serial port on windows ([@MartinHjelmare])
+- Notify - Webostv: Store the key file in the configuration directory ([@pschmitt])
+- TTS: TTS ID3 support ([@robbiet480])
+- Switch - Broadlink: Add send packet service ([@Yannic-HAW])
+- Wink: Add support for position on Wink cover ([@albertoarias])
+- Light - Flux: Make brightness display work for RGB devices. ([@aequitas])
+- Media player - Roku: Fix attribute error for media_player/roku ([@tchellomello])
+- Light - MQTT template: Fix brightness slider for MQTT template lights ([@ray0711])
+- Template: Add `min` and `max` Jinja2 [filters][filters] ([@sbidoul])
+- Device tracker - Skyhub: Improve Sky Hub error handling ([@alexmogavero])
+- Notify - SMTP: Add error checking to the MIMEImage encoding ([@stratosmacker])
+- Light - MQTT: Check for command topics when determining the capabilities of an MQTT light ([@herm])
+- Core: Check config before restarting ([@andrey-git])
+- Light - [Hue][hue]: Fix groups with same names ([@tboyce1])
+- Template: Add icon_template to template sensor ([@tboyce1])
+- Recorder: Refactoring, scoping, and better handling of SQLAlchemy Sessions ([@kellerza])
+- Light - Flux: Add support for fluxled discovery. ([@aequitas])
+- Media player - AppleTV: Add discovery support to Apple TV ([@postlund])
+- Sensor - Template: Improve warning message in template rendering ([@Danielhiversen])
+- Light - Demo: Add available property and typing hints ([@rytilahti])
+- Sensor - ARWN: Enhancements to [ARWN][arwn] platform ([@sdague])
+- Fan - ISY994: Change medium state for filtering ([@Teagan42])
+- Climate - Ecobee: Support away_mode as permanent hold and hold_mode as temporary hold. ([@Duoxilian])
+- Tellduslive: Don't throw exception if connection to server is lost ([@molobrakos])
+- Zoneminder: Refactoring and JSON decode error handling ([@pschmitt])
+- Image processing: Cleanup Base face class add support for microsoft face detect ([@pvizeli])
+
+Bugfixes: [@balloob], [@fabaff], [@pvizeli], [@mnoorenberghe] [@Danielhiversen], [@armills], [@tchellomello], [@aequitas], [@mathewpeterson], [@molobrakos], [@michaelarnauts], [@jabesq], [@turbokongen], [@JshWright], [@andriej], [@jawilson], [@andrey-git], [@nodinosaur], [@konikvranik], and you if you are missing here.
+
+### Breaking changes
+- The support for [LG webOS Smart TVs][webostv] was improved. This requires you to move `$HOME/.pylgtv` to `$HASS_CONFIG_DIR/webostv.conf` or Home Assistant will need to be paired with the TV again.
+- Image processing events have been renamed: `identify_face` has become `image_processing.detect_face`, `found_plate` has become `image_processing.found_plate`
+- The [FFmpeg binary sensor][ffmpeg-bin] change the platform name from `ffmpeg` to `ffmpeg_noise` and `ffmpeg_motion`. Also all FFmpeg-related services are moved from a platform implementation to a the [FFmpeg components][ffmpeg] and were rename from `binary_sensor.ffmpeg_xy` to `ffmpeg.xy`.
+
+### If you need help...
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+### Reporting Issues
+Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
+[@acambitsis]: https://github.com/acambitsis
+[@adrianlzt]: https://github.com/adrianlzt
+[@aequitas]: https://github.com/aequitas
+[@albertoarias]: https://github.com/albertoarias
+[@alexmogavero]: https://github.com/alexmogavero
+[@andrey-git]: https://github.com/andrey-git
+[@andriej]: https://github.com/andriej
+[@armills]: https://github.com/armills
+[@balloob]: https://github.com/balloob
+[@BastianPoe]: https://github.com/BastianPoe
+[@benvm]: https://github.com/benvm
+[@colinodell]: https://github.com/colinodell
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@DavidLP]: https://github.com/DavidLP
+[@Duoxilian]: https://github.com/Duoxilian
+[@eagleamon]: https://github.com/eagleamon
+[@fabaff]: https://github.com/fabaff
+[@herm]: https://github.com/herm
+[@jabesq]: https://github.com/jabesq
+[@jawilson]: https://github.com/jawilson
+[@Joeboyc2]: https://github.com/Joeboyc2
+[@JshWright]: https://github.com/JshWright
+[@kellerza]: https://github.com/kellerza
+[@konikvranik]: https://github.com/konikvranik
+[@kylehendricks]: https://github.com/kylehendricks
+[@LinuxChristian]: https://github.com/LinuxChristian
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@mathewpeterson]: https://github.com/mathewpeterson
+[@michaelarnauts]: https://github.com/michaelarnauts
+[@miniconfig]: https://github.com/miniconfig
+[@mnoorenberghe]: https://github.com/mnoorenberghe
+[@molobrakos]: https://github.com/molobrakos
+[@nodinosaur]: https://github.com/nodinosaur
+[@postlund]: https://github.com/postlund
+[@pschmitt]: https://github.com/pschmitt
+[@pvizeli]: https://github.com/pvizeli
+[@ray0711]: https://github.com/ray0711
+[@rmkraus]: https://github.com/rmkraus
+[@robbiet480]: https://github.com/robbiet480
+[@rytilahti]: https://github.com/rytilahti
+[@sbidoul]: https://github.com/sbidoul
+[@sdague]: https://github.com/sdague
+[@stratosmacker]: https://github.com/stratosmacker
+[@tboyce1]: https://github.com/tboyce1
+[@tchellomello]: https://github.com/tchellomello
+[@Teagan42]: https://github.com/Teagan42
+[@turbokongen]: https://github.com/turbokongen
+[@valentinalexeev]: https://github.com/valentinalexeev
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@Yannic-HAW]: https://github.com/Yannic-HAW
+
+[alert]: https://home-assistant.io/components/alert/
+[apiai]: https://home-assistant.io/components/apiai/
+[apple-tv]: https://home-assistant.io/components/media_player.apple_tv/
+[arwn]: https://home-assistant.io/components/sensor.arwn/
+[custom-ui]: https://home-assistant.io/developers/frontend_creating_custom_ui/
+[discovery]: https://home-assistant.io/components/discovery/
+[face-detect]: https://home-assistant.io/components/image_processing.microsoft_face_detect/
+[ffmpeg-bin]: https://home-assistant.io/components/binary_sensor.ffmpeg/
+[ffmpeg]: https://home-assistant.io/components/ffmpeg/
+[filters]: https://home-assistant.io/topics/templating/#home-assistant-template-extensions
+[fritz]: https://home-assistant.io/components/switch.fritzdect/
+[hue]: https://home-assistant.io/components/light.hue/
+[light]: https://home-assistant.io/cookbook/custom_ui_by_andrey-git
+[mailgun]: https://home-assistant.io/components/notify.mailgun/
+[media-player]: https://home-assistant.io/components/media_player/
+[moon]: https://home-assistant.io/components/sensor.moon/
+[mqtt-discovery]: https://home-assistant.io/components/mqtt/#discovery
+[nuki]: https://home-assistant.io/components/lock.nuki/
+[openevse]: https://home-assistant.io/components/sensor.openevse/
+[orange]: https://home-assistant.io/components/media_player.liveboxplaytv/
+[owm]: https://home-assistant.io/components/sensor.openweathermap/
+[python-yeelight]: https://gitlab.com/stavros/python-yeelight
+[qnap]: https://home-assistant.io/components/sensor.qnap/
+[rflink]: https://home-assistant.io/components/rflink/
+[systemmonitor]: https://home-assistant.io/components/sensor.systemmonitor/
+[webostv]: https://home-assistant.io/components/media_player.webostv/
+[yeelight]: https://home-assistant.io/components/light.yeelight/
+
+[event-stream-api]: https://home-assistant.io/developers/server_sent_events/
+[forum]: https://community.home-assistant.io/
+[gitter]: https://gitter.im/home-assistant/home-assistant
+[issue]: https://github.com/home-assistant/home-assistant/issues
+[websocket-api]: https://home-assistant.io/developers/websocket_api/
+]]>
+
+
@@ -832,120 +1026,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[websockets]: https://home-assistant.io/developers/websocket_api/
[waqi]: https://home-assistant.io/components/sensor.waqi/
-]]>
-
-
-
-
-
- 2016-11-20T00:04:05+00:00
- https://home-assistant.io/blog/2016/11/20/calendar--wink-thermostats--cisco-ios
- Changes
-
-- New [calendar component][google] including Google support ([@mnestor])
-- Final core upgrade for async ([@pvizeli])
-- [Neato] refactor + sensor support ([@turbokongen])
-- Device Tracker: [Swisscom Internet-Box][swisscom] now supported ([@betrisey])
-- Device Tracker - Locative: [Map support][locative] added ([@danijelst])
-- [Emulated Hue] will now sent request info as variables to scripts that get called ([@bah2830])
-- Wink: [Thermostats][wink-climate] are now supported ([@w1ll1am23])
-- Light: New [MQTT template][mqtt-template] platform for custom communication ([@Diaoul])
-- [Wake on Lan switch] can now configure a custom OFF script ([@Chris-V])
-- Device Tracker: [Cisco IOS][cisco] now supported ([@fbradyirl])
-- Sensor: Support for [PVOutput][pvoutput] snesor ([@fabaff])
-- Sensor: Show count of connected clients to the [API stream][api-stream] ([@balloob])
-- Fix platforms from doing I/O in the event loop ([@balloob], [@pvizeli], [@lwis], [@kellerza])
-- Switch - [TP Link]: Add daily consumption ([@gonzalezcalleja])
-- Templates: Add new `strptime` [template function] for parsing times ([@lwis])
-- [HTTP] component: Fix X-Forwarded-For parsing ([@mweinelt])
-- Switch - [Command Line]: Use configured object_id for entity IDs ([@n8henrie])
-- [MQTT] now supports birth and last will messages ([@bestlibre])
-- Better handling of accented characters in slugify ([@magicus])
-- Alarm Control Panel - [Envisalink]: Add new keypress service ([@jnimmo])
-- Light - [Hue]: Add service to activate scenes defined in Hue app ([@sdague])
-
-### Release 0.33.1 - November 20
-
- - Fix Z-Wave lights ([@turbokongen])
-
-### Release 0.33.2 - November 22
-
- - Fix Device Tracker init ([@pvizeli])
- - Fix Discovery init ([@pvizeli])
- - Fix TP-Link switch ([@mweinelt])
- - Fix Zwave light naming & configurable refresh ([@jchapple])
- - Neato fixes ([@turbokongen])
- - Fix 'Unknown' status for Nest Protect devices ([@Khabi])
-
-### Release 0.33.3 - November 23
-
- - Update Yr.no entities every hour ([@kellerza])
- - Bump Netdisco to 0.7.7 (fixes discovery on Synology)
- - Fix discovery race condition (most obvious in Wemo) ([@balloob])
-
-### Release 0.33.4 - November 24
-
- - Set executor pool size to 10 (as intended) ([@pvizeli])
-
-This should fix occasional performance problems that some people have reported.
-
-### Breaking changes
-
- - We have included a fix that impacts how we generate entity ids. This only impacts devices with accented characters. Instead of being stripped out, they are now replaced with the non-accented version. So now `Tèst Mörê` will become `test_more` instead of `tst_mr`.
- - Command line switches will now use the specified object ID for their entity ID instead of basing it off the name.
-
-### Reporting issues
-
-Experiencing issues introduced by this release? Please report them in our [issue tracker]. Make sure to fill in all fields of the issue template.
-
-[issue tracker]: https://github.com/home-assistant/home-assistant/issues
-[@bah2830]: https://github.com/bah2830
-[@balloob]: https://github.com/balloob
-[@bestlibre]: https://github.com/bestlibre
-[@betrisey]: https://github.com/betrisey
-[@Chris-V]: https://github.com/Chris-V
-[@danijelst]: https://github.com/danijelst
-[@Diaoul]: https://github.com/Diaoul
-[@fabaff]: https://github.com/fabaff
-[@fbradyirl]: https://github.com/fbradyirl
-[@gonzalezcalleja]: https://github.com/
-[@jnimmo]: https://github.com/jnimmo
-[@kellerza]: https://github.com/kellerza
-[@lwis]: https://github.com/lwis
-[@magicus]: https://github.com/magicus
-[@mnestor]: https://github.com/mnestor
-[@mweinelt]: https://github.com/mweinelt
-[@n8henrie]: https://github.com/n8henrie
-[@pvizeli]: https://github.com/pvizeli
-[@sdague]: https://github.com/sdague
-[@turbokongen]: https://github.com/turbokongen
-[@w1ll1am23]: https://github.com/w1ll1am23
-[@jchapple]: https://github.com/jchapple
-[@Khabi]: https://github.com/Khabi
-
-[api-stream]: /components/sensor.api_stream/
-[cisco]: /components/device_tracker.cisco_ios/
-[Command Line]: /components/switch.command_line/
-[Envisalink]: /components/envisalink/
-[google]: /components/calendar.google/
-[Hue]: /components/light.hue/
-[locative]: /components/device_tracker.locative/
-[mqtt-template]: /components/light.mqtt_template/
-[mqtt-will]: /components/mqtt/
-[pvoutput]: /components/sensor.pvoutput/
-[swisscom]: /components/device_tracker.swisscom/
-[TP Link]: /components/switch.tplink/
-[wink-climate]: /components/climate.wink/
-[neato]: /components/neato/
-[Emulated Hue]: /components/emulated_hue/
-[Wake on Lan switch]: /components/switch.wake_on_lan/
-[template function]: /topics/templating/#home-assistant-template-extensions
-[HTTP]: /components/http/
-[MQTT]: /components/mqtt/
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index 367491ec55..76e7d1394b 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -99,6 +99,38 @@
Thanks to @pvizeli, all the core components are now written asynchronously. All entity components are now migrated from synchronously to asynchronously code!
+
+
+
Now when you restart Home Assistant using the homeassistant.restart service, your configuration is checked. If it appears to be invalid the restart will fail.
+
+
+
+
Rewritten frontend
+
The frontend has been completely been rewritten, optimizing for speed and lost connection recovery. Even on the slowest phones it should fly now. The frontend also now uses the new WebSockets API instead of the EventStream API.
+
+
Custom state card UI
+
A nice new feature is the possibility to create custom state cards in the frondend. Go ahead and write your own state card for lights, sensors, locks, etc.
+
+
MQTT discovery
+
MQTT now has discovery support which is different than our discovery component. Similar to the HTTP sensor and HTTP binary sensor, MQTT discovery removes the need for configuration by allowing devices to make their presence known to Home Assistant.
+
+
Alert component
+
If you left your front door open, then the new alert component can be used to remind you of this by sending you repeating notifications at a given interval.
+
+
Yeelight
+
The yeelight component has been ported to use a more stable and feature-complete python-yeelight backend, and supports now both white and RGB bulbs. The component also supports transitions and can be configured to save the settings to the bulb on changes. The users currently using custom components for Yeelight are encouraged to move back to use the included version and report any problems with it to our issue tracker.
+
+
Apple TV
+
Apple TV is now a supported media_player! It has support for just about every media player function, including a realtime display of playback status and artwork.
The support for LG webOS Smart TVs was improved. This requires you to move $HOME/.pylgtv to $HASS_CONFIG_DIR/webostv.conf or Home Assistant will need to be paired with the TV again.
+
Image processing events have been renamed: identify_face has become image_processing.detect_face, found_plate has become image_processing.found_plate
+
The FFmpeg binary sensor change the platform name from ffmpeg to ffmpeg_noise and ffmpeg_motion. Also all FFmpeg-related services are moved from a platform implementation to a the FFmpeg components and were rename from binary_sensor.ffmpeg_xy to ffmpeg.xy.
+
+
+
If you need help…
+
…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+
+
Reporting Issues
+
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
Here we go… 0.34. Let’s call it the “Santa Claus” release. Rudolph was faster than expected and there’s lot’s of goodies on the sleigh. Of course, more work on async programming done by @pvizeli and @balloob, new components, new platforms, major improvements, and much more.
-
-
GPSLogger
-
-
The work of @dainok let’s you use your Android device, with the Geolocation feature enabled, to track itself using GPS or WiFi networks with the GPSLogger app. GPSLogger can use multiple sources: the passive one just get the latest Android known location, without activating GPS sensors or scanning for WiFi networks.
-
-
Remote component
-
-
The brand new remote component made by @iandday will simplify the integration of all kinds of remote control units. The first platform for Harmony is included in this release.
-
-
HomeMatic
-
-
The HomeMatic component has received some updates worth mentioning:
-
-
-
Additional services
-
-
reconnect: Reconnect to your CCU/Homegear without restarting Home Assistant.
-
set_dev_value: Manually control a device, even if it’s not supported by Home Assistant yet.
-
-
-
Support for multiple HomeMatic hosts
-
Support for HomeMatic Wired (most devices) and HomeMatic IP (a few devices)
-
Various improvements and fixes, especially for HM-Sec-Key (KeyMatic)
-
-
-
The support for multiple hosts is a result of allowing mixed configurations with wireless, wired, and IP devices. This has the drawback of making the update a breaking change (along with the renamed set_value service). However, the benefits and possibilities gained will be worth it.
-
-
Websocket API
-
-
This release includes a new websockets based API by @balloob to power the next generation of Home Assistant frontends. The current frontend has been partly migrated to use it and will be further migrated in the future.
This release has a bunch of bug fixes including a big one: emulated_hue will now work with Google Home! We usually reserve patch releases for small bug fixes but we considered this more impactful bug fix so important that we’re including it now instead of having people wait two weeks.
-
-
To make the fix backwards compatible (it is a patch release after all) you will have to add two new configuration option to emulated_hue to have it work with Google Home:
-
-
emulated_hue:
- type:google_home
- # This is important. Sadly, Google Home will not work with other ports.
- listen_port:80
-
The frontend now uses websockets. If you run a server in front of Home Assistant, you will have to update your config (example nginx)
-
Nest contains changes which will require your attention.
-
-
-
If you need help…
-
-
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use these communication channels. Thanks.
-
-
Reporting Issues
-
-
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
A new version of Home Assistant has just been pushed out. It contains bugfixes contributed by jamespcole, andythigpen, trainman419 and me. It also adds a bunch of great new features:
+
+
Script
+Andythigpen has contributed a script component. This allows users to create a sequence of service calls and delays. Scripts can be started using the service script/turn_on and interrupted using the service script/turn_off. A separate page has been added to the frontend to see the status of your scripts.
+
+
# Example configuration.yaml entry
+script:
+ # Turns on the bedroom lights and then the living room lights 1 minute later
+ wakeup:
+ alias:Wake Up
+ sequence:
+ -alias:Bedroom lights on
+ execute_service:light.turn_on
+ service_data:
+ entity_id:group.bedroom
+ -delay:
+ # supports seconds, milliseconds, minutes, hours, etc.
+ minutes:1
+ -alias:Living room lights on
+ execute_service:light.turn_on
+ service_data:
+ entity_id:group.living_room
+
The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
-This article will try to explain how they all relate.
-
-
The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.
-
-
There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a hub.
-
-
As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers home control.
-
-
-
-
-
- Example of a hub’s dashboard. Showing the state of 2 persons, 4 lights and the sun.
-
The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
+This article will try to explain how they all relate.
+
+
The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.
+
+
There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a hub.
+
+
As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers home control.
+
+
+
+
+
+ Example of a hub’s dashboard. Showing the state of 2 persons, 4 lights and the sun.
+
Here we go… 0.34. Let’s call it the “Santa Claus” release. Rudolph was faster than expected and there’s lot’s of goodies on the sleigh. Of course, more work on async programming done by @pvizeli and @balloob, new components, new platforms, major improvements, and much more.
+
+
GPSLogger
+
+
The work of @dainok let’s you use your Android device, with the Geolocation feature enabled, to track itself using GPS or WiFi networks with the GPSLogger app. GPSLogger can use multiple sources: the passive one just get the latest Android known location, without activating GPS sensors or scanning for WiFi networks.
+
+
Remote component
+
+
The brand new remote component made by @iandday will simplify the integration of all kinds of remote control units. The first platform for Harmony is included in this release.
+
+
HomeMatic
+
+
The HomeMatic component has received some updates worth mentioning:
+
+
+
Additional services
+
+
reconnect: Reconnect to your CCU/Homegear without restarting Home Assistant.
+
set_dev_value: Manually control a device, even if it’s not supported by Home Assistant yet.
+
+
+
Support for multiple HomeMatic hosts
+
Support for HomeMatic Wired (most devices) and HomeMatic IP (a few devices)
+
Various improvements and fixes, especially for HM-Sec-Key (KeyMatic)
+
+
+
The support for multiple hosts is a result of allowing mixed configurations with wireless, wired, and IP devices. This has the drawback of making the update a breaking change (along with the renamed set_value service). However, the benefits and possibilities gained will be worth it.
+
+
Websocket API
+
+
This release includes a new websockets based API by @balloob to power the next generation of Home Assistant frontends. The current frontend has been partly migrated to use it and will be further migrated in the future.
This release has a bunch of bug fixes including a big one: emulated_hue will now work with Google Home! We usually reserve patch releases for small bug fixes but we considered this more impactful bug fix so important that we’re including it now instead of having people wait two weeks.
+
+
To make the fix backwards compatible (it is a patch release after all) you will have to add two new configuration option to emulated_hue to have it work with Google Home:
+
+
emulated_hue:
+ type:google_home
+ # This is important. Sadly, Google Home will not work with other ports.
+ listen_port:80
+
The frontend now uses websockets. If you run a server in front of Home Assistant, you will have to update your config (example nginx)
+
Nest contains changes which will require your attention.
+
+
+
If you need help…
+
+
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use these communication channels. Thanks.
+
+
Reporting Issues
+
+
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
-So, part 1 of ESP8266 and MicroPython was pretty lame, right? Instead of getting information out of Home Assistant we are going a step forward and create our own sensor which is sending details about its state to a Home Assistant instance.
+So, part 1 of ESP8266 and MicroPython was pretty lame, right? Instead of getting information out of Home Assistant we are going a step forward and create our own sensor which is sending details about its state to a Home Assistant instance.
The history component is tracking everything that is going on within Home Assistant. This means that you have access to all stored information about your home. Our history is not a full-fledged graphical processing and visualization component as you may know from systems and network monitoring tools. The current limitation is that you only can select a day for a visual output of your information and not a period. Also, there is no possibility to drill down on a specific entity.
-
-
This blog post will show you ways to export data for reporting, visualization, or further analysis of automation rules.
The history component is tracking everything that is going on within Home Assistant. This means that you have access to all stored information about your home. Our history is not a full-fledged graphical processing and visualization component as you may know from systems and network monitoring tools. The current limitation is that you only can select a day for a visual output of your information and not a period. Also, there is no possibility to drill down on a specific entity.
+
+
This blog post will show you ways to export data for reporting, visualization, or further analysis of automation rules.
We are always hard at work at the virtual Home Assistant headquarters to make it easier for you to get started with Home Assistant. That’s why @jbags81 recently introduced the all-in-one installer. It allows you to get up and running with a complete Home Assistant setup by entering one line of code into your Raspberry Pi running Raspbian Jessie:
This feature wouldn’t be complete if it wasn’t accompanied by a new video by Ben from BRUH Automation. The video shows how to install Raspbian Jessie on your Raspberry Pi and use the new installation script to get a full Home Assistant system up and running.
We are always hard at work at the virtual Home Assistant headquarters to make it easier for you to get started with Home Assistant. That’s why @jbags81 recently introduced the all-in-one installer. It allows you to get up and running with a complete Home Assistant setup by entering one line of code into your Raspberry Pi running Raspbian Jessie:
This feature wouldn’t be complete if it wasn’t accompanied by a new video by Ben from BRUH Automation. The video shows how to install Raspbian Jessie on your Raspberry Pi and use the new installation script to get a full Home Assistant system up and running.
+
+
+
+
+
+
+
+
+
+
+
@@ -688,71 +740,6 @@
Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.
Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to @jaharkes for his hard work on this. Config validation is still in it’s early stages. More common platforms and components have been added but we didn’t do everything yet.
-
-
When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.
-
-
Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.
As of now we are not aware of any breaking changes. However, it might be that Home Assistant will not start for you because of an invalid configuration. A common mistake that people are making is that they are still referring to execute_service in their script configs. This should be service.
Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to @jaharkes for his hard work on this. Config validation is still in it’s early stages. More common platforms and components have been added but we didn’t do everything yet.
+
+
When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.
+
+
Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.
As of now we are not aware of any breaking changes. However, it might be that Home Assistant will not start for you because of an invalid configuration. A common mistake that people are making is that they are still referring to execute_service in their script configs. This should be service.
+
+
+
+
+
+
@@ -780,62 +845,6 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
-
-
-
-
So you own a SmartThings Hub. You probably bought it when you were looking to get into the whole Home Automation hobby because it worked with pretty much everything and offered you the ability to automate anything. After a week of ownership, you realized that building dashboards and automating required writing way more Groovy then you expected. Then one day you were browsing reddit and discovered the amazingness that is Home Assistant! A solution that offered dashboards, graphs, working support for Nest, and REAL EASY automation!
-
-
You spent your weekend getting everything set up, showing it off to your significant other, but in the end you got stumped when it came to integrating with all your existing SmartThings toys. What do I do now? Should I buy another hub? Should I just buy a Z-Wave stick?
-
-
That’s where we came in. We wanted a solution that can bridge the awesomeness of Home Assistant with the SmartThings hub that works with almost everything.
So you own a SmartThings Hub. You probably bought it when you were looking to get into the whole Home Automation hobby because it worked with pretty much everything and offered you the ability to automate anything. After a week of ownership, you realized that building dashboards and automating required writing way more Groovy then you expected. Then one day you were browsing reddit and discovered the amazingness that is Home Assistant! A solution that offered dashboards, graphs, working support for Nest, and REAL EASY automation!
+
+
You spent your weekend getting everything set up, showing it off to your significant other, but in the end you got stumped when it came to integrating with all your existing SmartThings toys. What do I do now? Should I buy another hub? Should I just buy a Z-Wave stick?
+
+
That’s where we came in. We wanted a solution that can bridge the awesomeness of Home Assistant with the SmartThings hub that works with almost everything.
From time to time we come along things that are worth sharing with fellow Home Assisters. Here a list of some cool stuff from last week:
-
-
First is the public beta of Let’s Encrypt. Let’s Encrypt is a new certificate authority that is free, automated and open. This means that it will now be very easy to secure your connection to Home Assistant while you are away from home. W1ll1am23 has written up a guide how to get started.
-
-
The next thing is a show-off of some of the cool stuff people do with Home Assistant. This is miniconfig talking to Home Assistant using the Amazon Echo!
-
-
-
-
-
-
And last but not least, Midwestern Mac did a microSD card performance comparison for the Raspberry Pi. If you’re using a Pi, make sure to check it out!
From time to time we come along things that are worth sharing with fellow Home Assisters. Here a list of some cool stuff from last week:
+
+
First is the public beta of Let’s Encrypt. Let’s Encrypt is a new certificate authority that is free, automated and open. This means that it will now be very easy to secure your connection to Home Assistant while you are away from home. W1ll1am23 has written up a guide how to get started.
+
+
The next thing is a show-off of some of the cool stuff people do with Home Assistant. This is miniconfig talking to Home Assistant using the Amazon Echo!
+
+
+
+
+
+
And last but not least, Midwestern Mac did a microSD card performance comparison for the Raspberry Pi. If you’re using a Pi, make sure to check it out!
MQTT support was added to Home Assistant recently. The MQTT component will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn’t care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn’t matter if the data is coming from a human, a web service, or a device.
MQTT support was added to Home Assistant recently. The MQTT component will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn’t care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn’t matter if the data is coming from a human, a web service, or a device.
A new version of Home Assistant has just been pushed out. It contains bugfixes contributed by jamespcole, andythigpen, trainman419 and me. It also adds a bunch of great new features:
-
-
Script
-Andythigpen has contributed a script component. This allows users to create a sequence of service calls and delays. Scripts can be started using the service script/turn_on and interrupted using the service script/turn_off. A separate page has been added to the frontend to see the status of your scripts.
-
-
# Example configuration.yaml entry
-script:
- # Turns on the bedroom lights and then the living room lights 1 minute later
- wakeup:
- alias:Wake Up
- sequence:
- -alias:Bedroom lights on
- execute_service:light.turn_on
- service_data:
- entity_id:group.bedroom
- -delay:
- # supports seconds, milliseconds, minutes, hours, etc.
- minutes:1
- -alias:Living room lights on
- execute_service:light.turn_on
- service_data:
- entity_id:group.living_room
-
The alert component is designed to notify you when problematic issues arise. For example, if the garage door is left open, the alert component can be used remind you of this by sending you repeating notifications at customizable intervals. This is also useful for low battery sensors, water leak sensors, or any condition that may need your attention.
+
+
Alerts will add an entity to the front end only when they are firing. This entity allows you to silence an alert until it is resolved.
+
+
Basic Example
+
+
The alert component makes use of any of the notifications components. To setup the alert component, first, you must setup a notification component. Then, add the following to your configuration file:
+
+
# Example configuration.yaml entry
+alert:
+ garage_door:
+ name:Garage is open
+ entity_id:input_boolean.garage_door
+ state:'on'
+ repeat:30
+ can_acknowledge:True
+ skip_first:True
+ notifiers:
+ -ryans_phone
+ -kristens_phone
+
+
+
Configuration variables:
+
+
+
name (Required): The friendly name of the alert.
+
entity_id (Required): The ID of the entity to watch.
+
state (Optional): The problem condition for the entity. Defaults to on.
+
repeat (Required): Number of minutes before the notification should be repeated. Can be either a number or a list of numbers.
+
can_acknowledge (Optional): Allows the alert to be unacknowledgable. Defaults to true.
+
skip_first (Optional): Controls whether the notification should be sent immediately or after the first delay. Defaults to false.
+
notifiers (Required): List of notification components to use for alerts.
+
+
+
In this example, the garage door status (input_boolean.garage_door) is watched and this alert will be triggered when its status is equal to on. This indicates that the door has been opened. Because the skip_first option was set to True, the first notification will not be delivered immediately. However, every 30 minutes, a notification will be delivered until either input_boolean.garage_door no longer has a state of on or until the alert is acknowledged using the Home Assistant frontend.
+
+
Complex Alert Criteria
+
+
By design, the alert component only handles very simple criteria for firing. That is, is only checks if a single entity’s state is equal to a value. At some point, it may be desireable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a Template Binary Sensor. The following example does that.
This example will begin firing as soon as the entity sensor.motion’s battery attribute falls below 15. It will continue to fire until the battery attribute raises above 15 or the alert is acknowledged on the frontend.
+
+
Dynamic Notification Delay Times
+
+
It may be desireable to have the delays between alert notifications dynamically change as the alert continues to fire. This can be done by setting the repeat configuration key to a list of numbers rather than a single number. Altering the first example would look like the following.
+
+
# Example configuration.yaml entry
+alert:
+ garage_door:
+ name:Garage is open
+ entity_id:input_boolean.garage_door
+ state:'on'# Optional, 'on' is the default value
+ repeat:
+ -15
+ -30
+ -60
+ can_acknowledge:True# Optional, default is True
+ skip_first:True# Optional, false is the default
+ notifiers:
+ -ryans_phone
+ -kristens_phone
+
+
+
+
Now, the first message will be sent after a 15 minute delay. The second will be sent after a 30 minute delay. A 60 minute delay will fall between every following notification.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/alexa/index.html b/components/alexa/index.html
index 2d2c107fb1..d108d6dd32 100644
--- a/components/alexa/index.html
+++ b/components/alexa/index.html
@@ -246,9 +246,11 @@ WhereAreWeIntent where we are
{%- for state in states.device_tracker -%}{%- if state.name.lower() == User.lower() -%}{{ state.name }} is at {{ state.state }}
+ {%- elif loop.last -%}
+ I am sorry, I do not know where {{ User }} is.{%- endif -%}{%- else -%}
- I am sorry, I do not know where {{ User }} is.
+ Sorry, I don't have any trackers registered.{%- endfor -%}card:type:simple
diff --git a/components/apcupsd/index.html b/components/apcupsd/index.html
index bdff2e8add..2072a358cd 100644
--- a/components/apcupsd/index.html
+++ b/components/apcupsd/index.html
@@ -221,6 +221,9 @@
Flic Smart Button
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 862096e414..0277e377d3 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -197,7 +197,10 @@ This sensor is not suitable for fast state changes because there is a high possi
Envisalink Binary Sensor
The ffmpeg platform allows you to use any video or audio feed with FFmpeg for various sensors in Home Assistant. Available are: noise, motion.
-
-
-If the ffmpeg process is broken, the sensor will be unavailable. To controll the ffmpeg process of sensor, use the service binary_sensor.ffmpeg_start, binary_sensor.ffmpeg_stop, binary_sensor.ffmpeg_restart.
-
-
-
Noise
-
-
To add FFmpeg with noise detection to your installation, add the following to your configuration.yaml file:
-
-
# Example configuration.yaml entry
-binary_sensor:
- -platform:ffmpeg
- tool:noise
-
-
-
-
Configuration variables:
-
-
-
input (Required): An FFmpeg-compatible input file, stream, or feed.
-
tool (Required): noise.
-
name (Optional): Override the name of your camera.
-
initial_state (Optional): Default true. Start ffmpeg with home-assistant.
-
peak (Optional): Default -30. The threshold of detecting noise, in dB. 0 is very loud and -100 is low.
-
duration (Optional): Default 1 second. How long the noise needs to be over the peak to trigger the state.
-
reset (Optional): Default 20 seconds. The time to reset the state after no new noise is over the peak.
-
extra_arguments (Optional): Extra options to pass to ffmpeg, like audio frequency filtering.
-
output (Optional): Allows you to send the audio output of this sensor to an Icecast server or other FFmpeg-supported output, e.g. to stream with Sonos after a state is triggered.
FFmpeg doesn’t have a motion detection filter, but can use a scene filter to detect a new scene/motion. You can set how much needs to change in order to detect motion with the option ‘changes’, the percent value of change between frames. If you want a really small value for ‘changes’, you can also add a denoise filter.
-
-
To add FFmpeg with motion detection to your installation, add the following to your configuration.yaml file:
The ffmpeg platform allows you to use any video feed with FFmpeg for motion sensors in Home Assistant.
+
+
+If the ffmpeg process is broken, the sensor will be unavailable. To controll the ffmpeg process of sensor, use the service ffmpeg.start, ffmpeg.stop, ffmpeg.restart.
+
+
+
Motion
+
+
FFmpeg doesn’t have a motion detection filter, but can use a scene filter to detect a new scene/motion. You can set how much needs to change in order to detect motion with the option ‘changes’, the percent value of change between frames. If you want a really small value for ‘changes’, you can also add a denoise filter.
+
+
To add FFmpeg with motion detection to your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+binary_sensor:
+ -platform:ffmpeg
+ input:FFMPEG_SUPPORTED_INPUT
+
+
+
+
Configuration variables:
+
+
+
input (Required): An FFmpeg-compatible input file, stream, or feed.
+
name (Optional): Override the name of your camera for the frontend.
+
initial_state (Optional): Start ffmpeg with Home Assistant. Defaults to true.
+
changes (Optional): How much needs to change between two frames to detect it as motion (a lower value is more sensitive). Defaults to 10%.
+
reset (Optional): The time to reset the state after no new motion is detected. Defaults to 20 seconds.
+
repeat (Optional): How many events need to be detected in repeat_time in order to trigger a motion. Defaults to 0 repeats (deactivated).
+
repeat_time (Optional): The span of time repeat events need to occur in before triggering a motion. Defaults to 0 seconds (deactivated).
+
extra_arguments (Optional): Extra options to pass to ffmpeg, e.g. video denoise filtering.
+
+
+
To experiment with values (changes/100 is the scene value in ffmpeg):
The ffmpeg platform allows you to use any video or audio feed with FFmpeg for various sensors in Home Assistant.
+
+
+If the ffmpeg process is broken, the sensor will be unavailable. To controll the ffmpeg process of sensor, use the service ffmpeg.start, ffmpeg.stop, ffmpeg.restart.
+
+
+
Noise
+
+
To add FFmpeg with noise detection to your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+binary_sensor:
+ -platform:ffmpeg
+ input:FFMPEG_SUPPORTED_INPUT
+
+
+
+
Configuration variables:
+
+
+
input (Required): An FFmpeg-compatible input file, stream, or feed.
+
name (Optional): Override the name of your camera.
+
initial_state (Optional): Default true. Start ffmpeg with home-assistant.
+
peak (Optional): Default -30. The threshold of detecting noise, in dB. 0 is very loud and -100 is low.
+
duration (Optional): Default 1 second. How long the noise needs to be over the peak to trigger the state.
+
reset (Optional): Default 20 seconds. The time to reset the state after no new noise is over the peak.
+
extra_arguments (Optional): Extra options to pass to ffmpeg, like audio frequency filtering.
+
output (Optional): Allows you to send the audio output of this sensor to an Icecast server or other FFmpeg-supported output, e.g. to stream with Sonos after a state is triggered.
Flic Smart Button
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index f3e38d3c5c..52e27221d6 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -220,7 +220,10 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
Envisalink Binary Sensor
Flic Smart Button
diff --git a/components/binary_sensor.nest/index.html b/components/binary_sensor.nest/index.html
index 36abb1b73e..b9ecf4bb68 100644
--- a/components/binary_sensor.nest/index.html
+++ b/components/binary_sensor.nest/index.html
@@ -210,7 +210,10 @@ You must have the Nest component configured to u
Envisalink Binary Sensor
Flic Smart Button
diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html
index 23380ee984..91c6e46f6c 100644
--- a/components/binary_sensor.wink/index.html
+++ b/components/binary_sensor.wink/index.html
@@ -200,7 +200,10 @@ The above devices are confimed to work, but others may work as well.
Envisalink Binary Sensor
diff --git a/components/climate.ecobee/index.html b/components/climate.ecobee/index.html
index ce922b42f1..de4dba2b1f 100644
--- a/components/climate.ecobee/index.html
+++ b/components/climate.ecobee/index.html
@@ -98,23 +98,45 @@ To get your Ecobee thermostats working with Home Assistant, follow the instructi
The Ecobee Thermostat supports the following key concepts.
-
The target temperature is the temperature that the device attempts to achieve. The target temperature is either determined by the
-currently active climate or it may be overridden by a hold. When the thermostat is not in auto mode, there is a single target temperature. When the thermostat is in auto operation mode, there is a pair of target temperatures: the lower target temperature determines the lowest desired temperature, while the higher target temperature determines the highest desired temperature (the thermostat will switch between heating and cooling to keep the temperature within these limits).
+
The target temperature is the temperature that the device attempts
+to achieve. The target temperature is either determined by the
+currently active climate or it may be overridden by a hold. When the
+thermostat is not in auto mode, there is a single target
+temperature. When the thermostat is in auto operation mode, there is a
+pair of target temperatures: the lower target temperature determines
+the lowest desired temperature, while the higher target temperature
+determines the highest desired temperature (the thermostat will switch
+between heating and cooling to keep the temperature within these
+limits).
-
A climate is a predefined or user-defined set of states that the thermostat aims to achieve. The ecobee thermostat provides three predefined climates: home, away, and sleep. The user can define additional climates.
+
A climate is a predefined or user-defined set of states that the
+thermostat aims to achieve. The ecobee thermostat provides three predefined
+climates: home, away, and sleep. The user can define additional climates.
-
A hold is an override of the target temperature defined in the currently active climate. The temperature targeted in the hold mode may be explicitly set (temperature hold) or it may be derived from a reference climate (home or away hold). All holds are temporary. Temperature and climate holds expire when the thermostat transitions to the next climate defined in its program.
+
A hold is an override of the target temperature defined in the
+currently active climate. The temperature targeted in the hold mode may be
+explicitly set (temperature hold) or it may be derived from a reference
+climate (home or away hold). All holds are temporary. Temperature and
+climate holds expire when the thermostat transitions to the next climate
+defined in its program.
-
When in away mode, the target temperature is permanently overridden by the target temperature defined for the away climate. The away mode is a simple way to emulate a vacation mode.
+
When in away mode, the target temperature is permanently overridden by
+the target temperature defined for the away climate. The away mode is a
+simple way to emulate a vacation mode.
-
The operation mode of the device is the currently active operational modes that the Ecobee thermostat provides: heat, auxHeatOnly, cool, auto, and off.
+
The operation mode of the device is the currently active operational
+modes that the Ecobee thermostat provides: heat, auxHeatOnly, cool,
+auto, and off.
Attributes
The following attributes are provided by the Ecobee Thermostat:
-name, temperature_unit, current_temperature, target_temperature, target_temperature_low, target_temperature_high, desired_fan_mode, fan, current_hold_mode, current_operation, operation_list,operation_mode, mode, fan_min_on_time, device_state_attributes, is_away_mode_on.
-
-
The attributes min_temp and max_temp are meaningless constant values.
Returns whether the thermostat is in away mode (see the corresponding service for more detail).
+
Returns whether the thermostat is in away mode (see the corresponding
+service for more detail).
Attribute actual humidity
@@ -396,9 +419,11 @@ auto operation mode.
Services
The following services are provided by the Ecobee Thermostat:
-set_away_mode, set_hold_mode, set_temperature, set_operation_mode, fan_min_on_time, resume_program.
-
-
The services set_aux_heat, set_humidity, set_fan_mode, and set_swing_mode offered by the Climate component are not implemented for this thermostat.
+set_away_mode, set_hold_mode, set_temperature, set_operation_mode,
+fan_min_on_time, resume_program.
+The services set_aux_heat, set_humidity, set_fan_mode, and
+set_swing_mode offered by the Climate component
+are not implemented for this thermostat.
Service set_away_mode
@@ -428,7 +453,10 @@ auto operation mode.
Service set_hold_mode
-
Puts the thermostat into the given hold mode. For ‘home’ and ‘away’, the target temperature is taken from the home or away, climate, respectively. For ‘temp’, the current temperature is taken as the target temperature. When None is provided as parameter, the hold_mode is turned off.
+
Puts the thermostat into the given hold mode. For ‘home’ and ‘away’, the
+target temperature is taken from the home or away, climate, respectively.
+For ‘temp’, the current temperature is taken as the target temperature.
+When None is provided as parameter, the hold_mode is turned off.
@@ -488,7 +516,8 @@ auto operation mode.
-
Only the target temperatures relevant for the current operation mode need to be provided.
+
Only the target temperatures relevant for the current operation mode need to
+be provided.
Available services: climate.set_aux_heat, climate.set_away_mode, climate.set_temperature, climate.set_humidity, climate.set_fan_mode, climate.set_operation_mode, climate.set_swing_mode
+
Available services: climate.set_aux_heat, climate.set_away_mode, climate.set_temperature, climate.set_humidity, climate.set_fan_mode, climate.set_operation_mode, climate.set_swing_mode, climate.set_hold_mode
Not all climate services may be available for your platform. Be sure to check the available services Home Assistant has enabled by checking Services.
@@ -151,11 +151,52 @@ Not all climate services may be available for your platform. Be sure to check th
Service climate.set_away_mode
-
This service has been deprecated. Use climate.set_hold_mode instead.
+
Set away mode for climate device. The away mode changes the target temperature permanently to a temperature
+reflecting a situation where the climate device is set to save energy. This may be used to emulate a
+“vacation mode”, for example.
+
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
yes
+
String or list of strings that point at entity_id’s of climate devices to control. Else targets all.
Set hold mode for climate device. The hold mode changes the target temperature of the client device temporarily to
+a different temperature. Typical hold modes provided by a climate device are “away” or “home”, where the hold temperature
+is chosen depending on a predefined climate, or “temperature” hold, where a particular temperature is selected as the
+temporary target temperature. The particular modes available depend on the climate device.
diff --git a/components/configurator/index.html b/components/configurator/index.html
index 1b80f9945e..3dba8372af 100644
--- a/components/configurator/index.html
+++ b/components/configurator/index.html
@@ -147,7 +147,7 @@ This component is intended for developers.
HTTP
diff --git a/components/device_tracker.actiontec/index.html b/components/device_tracker.actiontec/index.html
index 9ae162792a..d3ea7d2367 100644
--- a/components/device_tracker.actiontec/index.html
+++ b/components/device_tracker.actiontec/index.html
@@ -195,6 +195,9 @@ This device tracker needs telnet to be enabled on the router.
diff --git a/components/device_tracker.aruba/index.html b/components/device_tracker.aruba/index.html
index 6d4f4d8cd3..9c90a9dd95 100644
--- a/components/device_tracker.aruba/index.html
+++ b/components/device_tracker.aruba/index.html
@@ -198,6 +198,9 @@ This device tracker needs telnet to be enabled on the router.
diff --git a/components/device_tracker.bbox/index.html b/components/device_tracker.bbox/index.html
index 691a796cb7..3c8a83deb0 100644
--- a/components/device_tracker.bbox/index.html
+++ b/components/device_tracker.bbox/index.html
@@ -193,6 +193,9 @@ For now and due to third party limitation, the Bbox must be on the same local ne
diff --git a/components/device_tracker.cisco_ios/index.html b/components/device_tracker.cisco_ios/index.html
index 9d4b27f1c6..0bf9f18e52 100644
--- a/components/device_tracker.cisco_ios/index.html
+++ b/components/device_tracker.cisco_ios/index.html
@@ -220,6 +220,9 @@ If you have a very large number of devices on your VLan (+1000), then you may wa
diff --git a/components/device_tracker.fritz/index.html b/components/device_tracker.fritz/index.html
index 1f2832b037..39b8e8b5cd 100644
--- a/components/device_tracker.fritz/index.html
+++ b/components/device_tracker.fritz/index.html
@@ -193,6 +193,9 @@ It seems that it is not necessary to use it in current generation Fritz!Box rout
diff --git a/components/device_tracker.icloud/index.html b/components/device_tracker.icloud/index.html
index 69f03e24a9..55e38f0aea 100644
--- a/components/device_tracker.icloud/index.html
+++ b/components/device_tracker.icloud/index.html
@@ -208,6 +208,9 @@ You may receive an email from Apple stating that someone has logged into your ac
diff --git a/components/device_tracker.linksys_ap/index.html b/components/device_tracker.linksys_ap/index.html
index ce85de587b..828bd4c8e4 100644
--- a/components/device_tracker.linksys_ap/index.html
+++ b/components/device_tracker.linksys_ap/index.html
@@ -202,6 +202,9 @@ It was tested with a LAPAC1750 AC1750 Dual Band Access Point.
diff --git a/components/device_tracker.luci/index.html b/components/device_tracker.luci/index.html
index 4b5aa9e216..344ec68b41 100644
--- a/components/device_tracker.luci/index.html
+++ b/components/device_tracker.luci/index.html
@@ -200,6 +200,9 @@ Some installations have a s
Integrates MySensors device trackers into Home Assistant. See the main component for configuration instructions.
+
+
The following sensor types are supported:
+
+
MySensors version 2.0 and higher
+
+
+
+
+
S_TYPE
+
V_TYPE
+
+
+
+
+
S_GPS
+
V_POSITION
+
+
+
+
+
For more information, visit the serial api of MySensors.
+
+
MySensors 2.x example sketch
+
+
/**
+ * Documentation: http://www.mysensors.org
+ * Support Forum: http://forum.mysensors.org
+ *
+ * http://www.mysensors.org/build/gps
+ */
+
+// Enable debug prints to serial monitor
+#define MY_DEBUG
+// Enable and select radio type attached
+#define MY_RADIO_NRF24
+//#define MY_RADIO_RFM69
+
+#include <MySensors.h>
+
+#define SN "GPS Sensor"
+#define SV "1.0"
+
+// GPS position send interval (in millisectonds)
+#define GPS_SEND_INTERVAL 30000
+// The child id used for the gps sensor
+#define CHILD_ID_GPS 1
+
+MyMessagemsg(CHILD_ID_GPS,V_POSITION);
+
+// Last time GPS position was sent to controller
+unsignedlonglastGPSSent=-31000;
+
+// Some buffers
+charlatBuf[11];
+charlngBuf[11];
+charaltBuf[6];
+charpayload[30];
+
+// Dummy values. Implementation of real GPS device is not done.
+floatgpsLocationLat=40.741895;
+floatgpsLocationLng=-73.989308;
+floatgpsAltitudeMeters=12.0;
+
+voidsetup(){
+
+}
+
+voidpresentation(){
+ sendSketchInfo(SN,SV);
+ present(CHILD_ID_GPS,S_GPS);
+}
+
+voidloop()
+{
+ unsignedlongcurrentTime=millis();
+
+ // Evaluate if it is time to send a new position
+booltimeToSend=currentTime-lastGPSSent>GPS_SEND_INTERVAL;
+
+ if(timeToSend){
+ // Send current gps location
+// Build position and altitude string to send
+dtostrf(gpsLocationLat,1,6,latBuf);
+ dtostrf(gpsLocationLng,1,6,lngBuf);
+ dtostrf(gpsAltitudeMeters,1,0,altBuf);
+ sprintf(payload,"%s,%s,%s",latBuf,lngBuf,altBuf);
+
+ Serial.print(F("Position: "));
+ Serial.println(payload);
+
+ send(msg.set(payload));
+ lastGPSSent=currentTime;
+ }
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/device_tracker.netgear/index.html b/components/device_tracker.netgear/index.html
index d78ed01a8e..fe22514358 100644
--- a/components/device_tracker.netgear/index.html
+++ b/components/device_tracker.netgear/index.html
@@ -191,6 +191,9 @@
diff --git a/components/device_tracker.snmp/index.html b/components/device_tracker.snmp/index.html
index 77eca1a8cf..8417250127 100644
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@@ -107,6 +107,7 @@ This device tracker needs SNMP to be enabled on the router.
pfSense: 1.3.6.1.2.1.4.22.1.2 (tested on 2.2.4-RELEASE, need to enable SNMP service)
TPLink: 1.3.6.1.2.1.3.1.1.2.19.1 (Archer VR2600v, need to enable SNMP service)
EdgeRouter 1.3.6.1.2.1.4.22.1.2 (EdgeRouter Lite v1.9.0, need to enable SNMP service)
+
Ruckus: 1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6 (Ruckus ZoneDirector, tested on 9.13.3)
To use the SNMP version 1 platform in your installation, add the following to your configuration.yaml file:
@@ -227,6 +228,9 @@ This device tracker needs SNMP to be enabled on the router.
diff --git a/components/device_tracker.swisscom/index.html b/components/device_tracker.swisscom/index.html
index 9277ea3bd6..eb35bfb5e2 100644
--- a/components/device_tracker.swisscom/index.html
+++ b/components/device_tracker.swisscom/index.html
@@ -186,6 +186,9 @@ There are three models of Internet-Box (light, standard and plus). The platform
diff --git a/components/device_tracker.tado/index.html b/components/device_tracker.tado/index.html
index 6d8ffbceb2..f3022a0641 100644
--- a/components/device_tracker.tado/index.html
+++ b/components/device_tracker.tado/index.html
@@ -190,6 +190,9 @@ Polling Tado API for presence information will occure at most once every 30 seco
diff --git a/components/device_tracker.tplink/index.html b/components/device_tracker.tplink/index.html
index bf31e17026..bcb7f3794a 100644
--- a/components/device_tracker.tplink/index.html
+++ b/components/device_tracker.tplink/index.html
@@ -208,6 +208,9 @@ TP-Link devices typically only allow one login at a time to the admin console.
diff --git a/components/discovery/index.html b/components/discovery/index.html
index 6adf6b5215..09abbafaff 100644
--- a/components/discovery/index.html
+++ b/components/discovery/index.html
@@ -175,7 +175,7 @@ If you see Not initializing discovery because co
HTTP
diff --git a/components/emulated_hue/index.html b/components/emulated_hue/index.html
index 9bd0914eae..03f19834a5 100644
--- a/components/emulated_hue/index.html
+++ b/components/emulated_hue/index.html
@@ -309,6 +309,9 @@ The virtual bridge has the ability to turn entities on or off, or change the bri
Introduction
diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html
index 97dc832ede..57df6a033b 100644
--- a/components/ffmpeg/index.html
+++ b/components/ffmpeg/index.html
@@ -159,9 +159,6 @@ You need the ffmpeg binary in your system
If after symlinking and adding hdmi_cec: to your configuration you are getting the following error in your logs,
* failed to open vchiq instance you will also need to add the user account Home Assistant runs under, to the video group. To add the Home Assistant user account to the video group, run the following command. $ usermod -a -G video <hass_user_account>
diff --git a/components/homematic/index.html b/components/homematic/index.html
index 1f4adfc2c3..5b1855e510 100644
--- a/components/homematic/index.html
+++ b/components/homematic/index.html
@@ -126,7 +126,7 @@ You can manually rename the created entities by using Home Assistants true when using multiple hosts and this host should provide the services and variables.
-
Example configuration with multiple protocols and some other options set:
@@ -153,7 +153,7 @@ You can manually rename the created entities by using Home Assistants resolvenames option
+
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.
@@ -165,19 +165,33 @@ You can manually rename the created entities by using Home Assistants Multiple hosts
In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
This does not affect the entites in Home Assistant. They all use their own connection and work as expected.
-
Variables
+
Reading attributes of entities
-
It is possible to read and set values of system variables you have setup on the CCU/Homegear. An example of how that is done can be found below. The supported types for setting values are float- and bool-variables.
-Each variable will be available as it’s own entity in the form of homematic.name. The predefined homematic.homematic variable has the number of service messages as it’s value. You can use these variable-entities like any other entity in Home Assistant to trigger automations.
+
Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the template sensor component. Here’s an example of a template sensor that exposes the valve state of a thermostat.
It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables.
+The states of the variables are available through the attributes of your hub entity (e.g. homematic.rf). Use templates (as mentioned above) to make your variables available to automations or as entities.
The values of variables are polled from the CCU/Homegear in an interval of 30 seconds. Setting the value of a variable happens instantly and is directly pushed.
-
Events
+
Events
When HomeMatic devices change their state or some other internal value, the CCU/Homegear sends event messages to Home Assistant. These events are automatically parsed and the entities in Home Assistant are updated. However, you can also manually use these events to trigger automations. Two event-types are available:
@@ -186,7 +200,7 @@ The values of variables are polled from the CCU/Homegear in an interval of 30 se
homematic.impulse: For impulse sensors
-
Devices with buttons
+
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:
@@ -211,7 +225,7 @@ The HM-Sen-MDIR-WM55 motion detector will be displayed as 2 entities. A motion s
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”).
-
Services
+
Services
homematic.virtualkey: Simulate a keypress (or other valid action) on CCU/Homegear with device or virtual keys.
@@ -220,7 +234,7 @@ The name depends on if you chose to resolve names or not. If not, it will be the
homematic.set_dev_value: Control a device manually (even devices without support). Equivalent to setValue-method from XML-RPC.
-
Examples
+
Examples
Simulate a button being pressed
...action:
@@ -243,17 +257,18 @@ The name depends on if you chose to resolve names or not. If not, it will be the
If you are familiar with the internals of HomeMatic devices, you can manually set values on the devices. This can serve as a workaround if support for a device is currently not available, or only limited functionality has been implemented.
Using this service provides you direct access to the setValue-method of the primary connection. If you have multiple hosts, you may select the one hosting a specific device by providing the proxy-parameter with a value equivalent to the name you have chosen. In the example configuration from above rf, wired and ip would be valid values.
@@ -408,6 +423,9 @@ Using this service provides you direct access to the setValue-method of the prim
Introduction
diff --git a/components/ifttt/index.html b/components/ifttt/index.html
index c3f6111b59..fe0d4d171d 100644
--- a/components/ifttt/index.html
+++ b/components/ifttt/index.html
@@ -242,6 +242,9 @@ You need to setup a unique trigger for each event you sent to IFTTT.
The microsoft_face_detect image processing platform allows you to use the Microsoft Face Identify API through Home Assistant. This platform enables you do detect face on camera and fire a event with attributes.
+
+
Please refer to the component configuration on how to setup the API key.
+
+
For using the result inside an automation rule, take a look at the component page.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/image_processing.microsoft_face_identify/index.html b/components/image_processing.microsoft_face_identify/index.html
index 96409c2572..d3e6aa8ac2 100644
--- a/components/image_processing.microsoft_face_identify/index.html
+++ b/components/image_processing.microsoft_face_identify/index.html
@@ -7,26 +7,26 @@
- Microsoft Face identify - Home Assistant
+ Microsoft Face Identify - Home Assistant
-
+
-
+
-
+
-
-
+
+
@@ -90,7 +90,7 @@
-
The microsoft_face_identify image processing platform lets you use Microsoft Face identify API through Home Assistant.
+
The microsoft_face_identify image processing platform lets you use Microsoft Face identify API through Home Assistant. This platform allow you do identify persons on camera and fire a event with identify persons.
Please refer to the component configuration on how to setup the API key.
OpenALPR Cloud
diff --git a/components/image_processing/index.html b/components/image_processing/index.html
index d3dbc61ef5..fb1a32db8f 100644
--- a/components/image_processing/index.html
+++ b/components/image_processing/index.html
@@ -109,7 +109,7 @@ If you are running Home Assistant over SSL or from within a container, you will
-alias:Open garage doortrigger:platform:event
- event_type:found_plate
+ event_type:image_processing.found_plateevent_data:entity_id:openalpr.camera_garage_1plate:BE2183423
@@ -117,20 +117,20 @@ If you are running Home Assistant over SSL or from within a container, you will
-
The following event attributes will be present: entity_id, plate, confidence
+
The following event attributes will be present (platform-dependent): entity_id, plate, confidence
-
Face identify
+
Face
-
Face entities attribute have a face counter total_faces and all validated person as known_faces.
+
Face entities attribute have a face counter total_faces and all face data as faces.
-
This event is trigger after Microsoft Face identify found a known faces.
+
This event is trigger after Microsoft Face found a faces.
# Example configuration.yaml automation entryautomation:-alias:Known person in front of my doortrigger:platform:event
- event_type:identify_face
+ event_type:image_processing.detect_faceevent_data:entity_id:image_processing.doorname:'HansMaier'
@@ -138,7 +138,7 @@ If you are running Home Assistant over SSL or from within a container, you will
-
The following event attributes will be present: entity_id, name, confidence
+
The following event attributes will be present (platform-dependent): entity_id, name, confidence, age, gender, motion, glasses
@@ -160,8 +160,11 @@ If you are running Home Assistant over SSL or from within a container, you will
diff --git a/components/insteon_hub/index.html b/components/insteon_hub/index.html
index 98032b363c..f24e252301 100644
--- a/components/insteon_hub/index.html
+++ b/components/insteon_hub/index.html
@@ -227,6 +227,9 @@ This component has been disabled due to a complaint by Insteon. It will be enabl
diff --git a/components/light.flux_led/index.html b/components/light.flux_led/index.html
index bd1387fb65..32cbe32fcb 100644
--- a/components/light.flux_led/index.html
+++ b/components/light.flux_led/index.html
@@ -296,6 +296,9 @@ The component defaults to rgbw. If your device has a separate white channel, you
diff --git a/components/light.mqtt_template/index.html b/components/light.mqtt_template/index.html
index 0f4aa185f1..ab1898ef16 100644
--- a/components/light.mqtt_template/index.html
+++ b/components/light.mqtt_template/index.html
@@ -293,6 +293,9 @@ It is format-agnostic so you can use any data format you want (i.e. string, JSON
V_RGB*, [V_LIGHT* or V_STATUS*], [V_DIMMER or V_PERCENTAGE]
+
+
S_RGBW_LIGHT
+
V_RGBW*, [V_LIGHT* or V_STATUS*], [V_DIMMER or V_PERCENTAGE]
+
-
V_TYPES with a star (*) denote V_TYPES that should be sent at sketch startup. For an S_DIMMER, send both a V_DIMMER/V_PERCENTAGE and a V_LIGHT/V_STATUS message. For an S_RGB_LIGHT, send both a V_RGB and a V_LIGHT/V_STATUS message with a V_DIMMER/V_PERCENTAGE message being optional. Sketch should acknowledge a command sent from controller with the same type. If command invokes a change to off state (including a V_PERCENTAGE or V_RGB message of zero), only a V_STATUS of zero message should be sent. See sketches below for examples.
+
V_TYPES with a star (*) denote V_TYPES that should be sent at sketch startup. For an S_DIMMER, send both a V_DIMMER/V_PERCENTAGE and a V_LIGHT/V_STATUS message. For an S_RGB_LIGHT, send both a V_RGB and a V_LIGHT/V_STATUS message with a V_DIMMER/V_PERCENTAGE message being optional. Same principal applies for S_RGBW_LIGHT and V_RGBW.
+
+
Sketch should acknowledge a command sent from controller with the same type. If command invokes a change to off state (including a V_PERCENTAGE, V_RGB, or V_RGBW message of zero), only a V_STATUS of zero message should be sent. See sketches below for examples.
For more information, visit the serial api of MySensors.
@@ -210,12 +216,13 @@
}
+
MySensors 2.x example sketch
-
/*
+
/*
* Example Dimmable Light
* Code adapted from http://github.com/mysensors/MySensors/tree/master/examples/DimmableLight
- *
+ *
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
@@ -271,7 +278,7 @@
voidreceive(constMyMessage&message){
- //When receiving a V_STATUS command, switch the light between OFF
+ //When receiving a V_STATUS command, switch the light between OFF
//and the last received dimmer value
if(message.type==V_STATUS){Serial.println("V_STATUS command received...");
@@ -290,7 +297,7 @@
//Update constroller status
send_status_message();
-
+
}elseif(message.type==V_PERCENTAGE){Serial.println("V_PERCENTAGE command received...");intdim_value=constrain(message.getInt(),0,100);
@@ -303,11 +310,11 @@
}else{last_state=LIGHT_ON;last_dim=dim_value;
-
+
//Update constroller with dimmer value
send_dimmer_message();}
-
+
}else{Serial.println("Invalid command received...");return;
@@ -345,6 +352,7 @@
The rflink component support devices that use Rflink gateway firmware, for example the Nodo Rflink Gateway. Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
After configuring the Rflink hub lights will be automatically discovered and added.
+
+
New/unknown lights can be assigned to a default group automatically by specifying the new_devices_group option with a group name. If the group doesn’t exist it will be created.
+
+
For example:
+
+
# Example configuration.yaml entry
+sensor:
+ platform:rflink
+ new_devices_group:"NewRflinkLights"
+
+
+
+
Rflink switch/light ID’s are composed of: protocol, id, switch. For example: newkaku_0000c6c2_1.
+
+
Once the ID of a light is known it can be used to configure the light in HA, for example to add it to a different group, hide it or configure a nice name.
devices (Optional): A list of devices with their name to use in the frontend.
+
new_devices_group (Optional): Create group to add new/unknown devices to.
+
device_defaults: (Optional)
+
+
fire_event_ (Optional): Set default fire_event for Rflink switch devices (see below).
+
signal_repetitions (Optional): Set default signal_repetitions for Rflink switch devices (see below).
+
+
+
+
+
Device configuration variables:
+
+
+
name (Optional): Name for the device, defaults to Rflink ID.
+
type (Optional): Override automatically detected type of the light device, can be: switchable, dimmable or hybrid. See ‘Light Types’ below.
+
aliasses (Optional): Alternative Rflink ID’s this device is known by.
+
fire_event_ (Optional): Fire an button_pressed event if this device is turned on or off (default: False).
+
signal_repetitions (Optional): Repeat every Rflink command this number of times (default: 1)
+
+
+
Light state
+
+
Initially the state of a light is unknown. When the light is turned on or off (via frontend or 433Mhz remote) the state is known and will be shown in the frontend.
+
+
Sometimes a light is controlled by multiple 433Mhz remotes, each remote has its own code programmed in the light. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
Any on/off command from any allias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.
+
+
Light types
+
+
Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated on command as they turn into a pulsating state until on is pressed again (for example KlikAanKlikUit). The Rflink component support three types of lights to make things work in every situation:
+
+
+
Hybrid: This type sends a dim followed by an a on command; and off commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple on signals will cause dimmers to go into disco mode.
+
Switchable: Device type that sends only on and off commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).
+
Dimmable: Sends only dim and off commands. This does not work on on/off type devices as they don’t understand the dim command. For dimmers this does not cause issues with signal repetitions.
+
+
+
By default new lights are assigned the switchable type. Protocol supporting dimming are assigned the hybrid type. Currently only newkaku protocol is detected as dimmable. Please refer to Device Support to get your dimmers supported.
+
+
Hiding/ignoring lights
+
+
Lights are added automatically when the Rflink gateway intercepts a 433Mhz command in the ether. To prevent cluttering the frontend use any of these methods:
+
+
+
Configure a new_devices_group for lights and optionally add it to a different view.
diff --git a/components/light.wink/index.html b/components/light.wink/index.html
index 8fdf99eaae..5f872a1d66 100644
--- a/components/light.wink/index.html
+++ b/components/light.wink/index.html
@@ -232,6 +232,9 @@ The above devices are confimed to work, but others may work as well.
diff --git a/components/light.yeelight/index.html b/components/light.yeelight/index.html
index 08d903e53c..d72946736e 100644
--- a/components/light.yeelight/index.html
+++ b/components/light.yeelight/index.html
@@ -230,6 +230,9 @@ This component is tested to work with models YLDP01YL and YLDP03YL. If you have
diff --git a/components/lock.mqtt/index.html b/components/lock.mqtt/index.html
index 4667279254..ab28689cf4 100644
--- a/components/lock.mqtt/index.html
+++ b/components/lock.mqtt/index.html
@@ -227,6 +227,9 @@ Make sure that your topic match exact. some-topi
To add a Nuki bridge to your installation, you need to enable developper mode on your bridge and define a port and an access token. This can be achieved using the Android app. Please note that there seems to be a maximum length for the API token, even though the app allows you to set a longer one.
+Then add the following to your configuration.yaml file:
diff --git a/components/lock.wink/index.html b/components/lock.wink/index.html
index 1e80e98ee3..31b4aac379 100644
--- a/components/lock.wink/index.html
+++ b/components/lock.wink/index.html
@@ -170,6 +170,9 @@ If supported by your lock, a binary sensor will be created for each user key cod
The lutron component is the base for all Lutron in Home Assistant. The preferred way to setup the lutron component is by enabling the the discovery component.
+
Lutron is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The lutron component in Home Assistant is responsible for communicating with the main hub for these systems.
+
Presently, there’s only support for communicating with the RadioRA 2 Main Repeater and only handle light switches and dimmers.
+
+
When configured, the lutron component will automatically discover the rooms and their associated switches/dimmers as configured by the RadioRA 2 software from Lutron. Each room will be treated as a separate group.
+
+
To use Lutron RadioRA 2 devices in your installation, add the following to your configuration.yaml file using the IP of your RadioRA 2 Main Repeater:
lutron_ip (Required): The IP address of the Main Repeater.
+
lutron_user (Required): The login name of the user. The user lutron always exists, but other users can be added via RadioRA 2 software.
+
lutron_password (Required): The password for the user specified above. integration is the password for the always-present lutron user.
+
+
+
+ It is recommended to assign a static IP address to your Main Repeater. This ensures that it won’t change IP addresses, so you won’t have to change the lutron_ip if it reboots and comes up with a different IP address.
+
The apple_tv platform allows you to control an Apple TV (3rd and 4th generation).
+
+
+Currently you must have Home Sharing enabled for this to work. Support for pairing Home Assistant with your device will be supported in a later release.
+
+
+
If you want to automatically discover new devices, just make sure you have discovery: in your configuration.yaml file. To manually add an Apple TV to your installation, add the following to your configuration.yaml file:
login_id (Required): An identifier used to login to the device, see below
+
name (Optional): The name of the device used in the frontend
+
+
+
In order to connect to the device you need a login id. The easiest way to obtain this identifier is to use the application atvremote. It should be available in the same environment as you installed Home-Assistant. Just run it like this to scan for all devices (try again if a device is missing):
+
+
$ atvremote scan
+Found Apple TVs:
+ - Apple TV at 10.0.10.22 (login id: 00000000-1234-5678-9012-345678901234)
+
+
+
+
Just copy and paste the login id from the device you want to add. For more details about atvremote, see: this page.
+
+
Notes and Limitations
+
+
+
Pairing is currently not supported
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/media_player.aquostv/index.html b/components/media_player.aquostv/index.html
index dbf7d30c3a..fd82a94a7c 100644
--- a/components/media_player.aquostv/index.html
+++ b/components/media_player.aquostv/index.html
@@ -166,6 +166,9 @@ Also, with power_on_enabled as True, the Aquos logo on your TV
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index 0d2c1998d8..0e090e6b26 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -193,6 +193,9 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
diff --git a/components/media_player.lg_netcast/index.html b/components/media_player.lg_netcast/index.html
index a1284be48c..5d8057a330 100644
--- a/components/media_player.lg_netcast/index.html
+++ b/components/media_player.lg_netcast/index.html
@@ -150,6 +150,9 @@ The access token will not change until you factory reset your TV.
To add an Orange Livebox Play TV to your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+media_player:
+ -platform:liveboxplaytv
+ host:192.168.1.3
+
+
+
+
Configuration variables:
+
+
+
host (Required): The IP or hostname of the Orange Livebox Play TV appliance.
+
name (Optional): The name to use in the frontend. Defaults to Livebox Play TV.
+
port (Optional): The port on which the Livebox is listening on. Defaults to 8080.
+
+
+
Full configuration
+
+
A full configuration example for an Orange TV appliance can look like this:
+
+
# Example configuration.yaml entry
+media_player:
+ -platform:liveboxplaytv
+ host:192.168.1.3
+ port:8080
+ name:Orange Livebox Play TV
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/media_player.mpchc/index.html b/components/media_player.mpchc/index.html
index f729f136b8..d74ad5f2e1 100644
--- a/components/media_player.mpchc/index.html
+++ b/components/media_player.mpchc/index.html
@@ -153,6 +153,9 @@ The MPC-HC web interface is highly insecure, and allows remote clients full play
diff --git a/components/media_player.nad/index.html b/components/media_player.nad/index.html
index d72f1297aa..cb310f1ddd 100644
--- a/components/media_player.nad/index.html
+++ b/components/media_player.nad/index.html
@@ -159,6 +159,9 @@ Be aware that the user might need to logout and logon again to activate these pe
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index 18c7c9ac9c..7a359bc5c1 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -174,6 +174,9 @@ If you add your model remember to remove these before adding them to the list.
diff --git a/components/media_player.soundtouch/index.html b/components/media_player.soundtouch/index.html
index e1aadec7a1..d0b5b5c7a7 100644
--- a/components/media_player.soundtouch/index.html
+++ b/components/media_player.soundtouch/index.html
@@ -272,6 +272,9 @@ create a new zone in order to be able to add slave(s) again
host (Optional): The IP of the LG webOS Smart TV, e.g. 192.168.0.10.
mac (Optional): The MAC address of the TV, e.g. C8:08:E9:99:99:1A.
name (Optional): The name you would like to give to the LG webOS Smart TV.
+
filename (Optional): The filename where the pairing key with the TV should be stored. This path is relative to Home Assistant’s config directory. It defaults to webostv.conf.
customize array (Optional): List of options to customize.
sources array (Optional*): List of hardware inputs.
@@ -126,6 +127,7 @@ Home Assistant is able to turn on a LG webOS Smart TV if you specify its MAC add
host:192.168.0.10mac:C8:08:E9:99:99:1Aname:Living Room TV
+ filename:webostv.confcustomize:sources:-livetv
@@ -174,6 +176,9 @@ Home Assistant is able to turn on a LG webOS Smart TV if you specify its MAC add
The MQTT component will register the service publish which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use payload to hard-code a payload or use payload_template to specify a template that will be rendered to generate the payload.
@@ -319,7 +321,23 @@ Home Assistant will automatically load the correct certificate if you connect to
-
Logging
+
Discovery
+
+
The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the HTTP binary sensor and the HTTP sensor. Only support for binary sensor is available at the moment.
+
+
To enable MQTT discovery, add the following to your configuration.yaml file:
A motion detection device for your garden would sent its configuration as JSON payload {"name":"garden","sensor_class":"motion"} to the topic homeassistant/binary_sensor/garden/config. After the first message to config, then the MQTT messages sent to state, eg. homeassistant/binary_sensor/garden/state, will update the state in Home Assistant.
+
+
Logging
The logger component allow the logging of received MQTT messages.
@@ -566,6 +584,9 @@ Home Assistant will automatically load the correct certificate if you connect to
Introduction
diff --git a/components/mysensors/index.html b/components/mysensors/index.html
index 3dc86c881b..eddb775edd 100644
--- a/components/mysensors/index.html
+++ b/components/mysensors/index.html
@@ -290,6 +290,9 @@ The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway
diff --git a/components/neato/index.html b/components/neato/index.html
index a88ba2e6b9..0bb0f1d354 100644
--- a/components/neato/index.html
+++ b/components/neato/index.html
@@ -226,6 +226,9 @@ The Home Assistant Neato platform has only be tested with a Botvac Connected. Th
diff --git a/components/netatmo/index.html b/components/netatmo/index.html
index ec6e7f7a56..71423e325c 100644
--- a/components/netatmo/index.html
+++ b/components/netatmo/index.html
@@ -257,6 +257,9 @@ The Home Assistant Netatmo platform has only be tested with the classic indoor,
diff --git a/components/notify.facebook/index.html b/components/notify.facebook/index.html
index 9a5c62b86e..5188df7c29 100644
--- a/components/notify.facebook/index.html
+++ b/components/notify.facebook/index.html
@@ -130,6 +130,29 @@ The phone number used in target should be registered with faceb
+
Rich messages
+
You could also send rich messing (cards, buttons, images, videos, etc). Info to which types or messages and how to build them.
+
+
# Example script with a notification entry with rich message
+
+script:
+ test_fb_notification:
+ sequence:
+ -service:notify.facebook
+ data:
+ message:Some text before the quick replies
+ target:0034643123212
+ data:
+ quick_replies:
+ -content_type:text
+ title:Red
+ payload:DEVELOPER_DEFINED_PAYLOAD_FOR_PICKING_RED
+ -content_type:text
+ title:Blue
+ payload:DEVELOPER_DEFINED_PAYLOAD_FOR_PICKING_BLUE
+
+
+
@@ -213,6 +236,9 @@ The phone number used in target should be registered with faceb
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index 125f2cfb0a..5a9ce374d2 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -205,6 +205,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
If you use NGINX as an proxy with authentication in front of HASS, you may have trouble with receiving events back to HASS. It’s because of authentication token that cannot be passed through the proxy.
+
+
To solve the issue put additional location into your nginx site’s configuration:
domain (Optional): This is the domain name to be used when sending out mail. Defaults to the first custom domain you have set up.
+
sandbox (Optional): Whether to use the sandboxed domain for outgoing mail. The domain item takes precedence over this. Defaults to False.
+
token (Required): This is the API token that has been generated in your Mailgun account.
+
recipient (Required): The email address of the recipient.
+
sender (Optional): The sender’s email address. Defaults to hass@DOMAIN, where DOMAIN is outgoint mail domain, as defined by the domain and sanbox configuration entries.
+
+
+
Full configuration
+
+
A full configuration example for the Mailgun notifier system can look like this:
diff --git a/components/notify.nfandroidtv/index.html b/components/notify.nfandroidtv/index.html
index 179cc740fc..f9c3a54fbb 100644
--- a/components/notify.nfandroidtv/index.html
+++ b/components/notify.nfandroidtv/index.html
@@ -216,6 +216,9 @@ This is a fully customized JSON you can use to test how the final notification w
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index 74e270989f..eeabb0e4d4 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -250,6 +250,9 @@ which need special attention. By default, the usage by external applications, es
diff --git a/components/notify.twilio_call.markdown b/components/notify.twilio_call.markdown
new file mode 100644
index 0000000000..a5989bd142
--- /dev/null
+++ b/components/notify.twilio_call.markdown
@@ -0,0 +1,61 @@
+yout: page
+title: "Twilio Call"
+description: "Instructions how to add user notifications to Home Assistant."
+date: 2017-01-27 00:09
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: twilio.png
+ha_category: Notifications
+ha_release: "0.37"
+---
+
+The `twilio` notification platform enables sending notifications via Voice, powered by [Twilio](https://twilio.com).
+Passed message will be read by Text-To-Speech service.
+
+This component is just an adaptation from the Twilio SMS notification platform and won't exist without it.
+
+Free trial account is available at [Twilio](https://twilio.com) website providing free calls to verified phone numbers.
+Calls are limited to 10 minutes and will play a short trial message before your message runs.
+
+Upgraded accounts have no limitation.
+
+To use this notification platform in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+notify:
+ - name: NOTIFIER_NAME
+ platform: twilio_call
+ account_sid: ACCOUNT_SID_FROM_TWILIO
+ auth_token: AUTH_TOKEN_FROM_TWILIO
+ from_number: E164_PHONE_NUMBER
+```
+
+Configuration variables:
+
+- **account_sid** (*Required*): Your Twilio Account SID which can be found in your [console](https://www.twilio.com/console). It starts with the letters `AC`.
+- **auth_token** (*Required*): Your Twilio Account SID which can be found in your [console](https://www.twilio.com/console). It should be directly under where you found the `account_sid`.
+- **from_number** (*Required*): An [E.164](https://en.wikipedia.org/wiki/E.164) formatted phone number, like +14151234567. See [Twilio's guide to formatting phone numbers](https://www.twilio.com/help/faq/phone-numbers/how-do-i-format-phone-numbers-to-work-internationally) for more information.
+- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
+
+### {% linkable_title Usage %}
+
+Twilio is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will send a notification to all E.164 phone numbers in the notification **target**. See the notes above regarding the `from_number` configuration variable for information about formatting phone numbers.
+
+```yaml
+# Example automation notification entry
+automation:
+ - alias: The sun has set
+ trigger:
+ platform: sun
+ event: sunset
+ action:
+ service: notify.twilio_sms
+ data:
+ message: 'The sun has set'
+ target:
+ - +14151234567
+ - +15105555555
+```
diff --git a/components/notify.twilio_sms/index.html b/components/notify.twilio_sms/index.html
index c402930d4d..5b002cb2eb 100644
--- a/components/notify.twilio_sms/index.html
+++ b/components/notify.twilio_sms/index.html
@@ -216,6 +216,9 @@
host (Required): The IP of the LG WebOS Smart TV, e.g. 192.168.0.10
name (Required): The name you would like to give to the LG WebOS Smart TV.
+
filename (Optional): The filename where the pairing key with the TV should be stored. This path is relative to Home Assistant’s config directory. It defaults to webostv.conf.
The rflink component support devices that use Rflink gateway firmware, for example the Nodo Rflink Gateway. Rflink gateway is an Arduino firmware that allows communication with 433 Mhz devices using cheap hardware (Arduino + 433 Mhz tranceiver).
+
+
The 433 Mhz spectrum is used by many manufacturers mostly using their own protocol/standard and includes devices like: light switches, blinds, weather stations, alarms and various other sensors.
+
+
A complete list of devices supported by Rflink can be found here
+
+
This component is tested with the following hardware/software:
+
+
+
Nodo Rflink Gateway V1.4/Rflink R44
+
+
+
To enable Rflink in your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+rflink:
+ port:/dev/serial/by-id/usb-id01234
+
+
+
+
Configuration variables:
+
+
+
port (Required): The path to Rflink usb/serial device or TCP port in TCP mode.
+
host (Optional): Switches to TCP mode, connects to host instead of to USB/serial.
+
wait_for_ack (Optional): Wait for Rflink to ackowledge commands sent before sending new command (slower but more reliable). Defaults to True
+
ignore_devices (Optional): List of devices id’s to ignore. Supports wildcards (*) at the end.
+
reconnect_interval (Optional): Time in seconds between reconnect attempts.
TCP mode allows connect to a Rflink device over TCP/IP network. This is for example useful if placing the Rflink device next to the HA server is not optimal or desired (eg: bad reception).
+
+
To expose the usb/serial interface over TCP on a different host (Linux) the following command can be used:
Other methods of exposing the serial interface over TCP are possible (eg: ESP8266 or using Arduino Wifi shield). Basically the serial stream should be directly mapped to the TCP stream.
+
+
# Example configuration.yaml entry
+rflink:
+ host:192.168.0.10
+ port:1234
+
+
+
+
Ignoring devices
+
+
Rflink platform can be configured to completely ignore a device on a platform level. This is useful when you have neighbors which also use 433 Mhz technology.
This configuration will ignore the button 1 of the newkaku device with ID 000001, all devices of the digitech protocol and all switches of the kaku protocol device with codewheel ID 1.
+
+
Wildcards only work at the end of the ID, not in the middle of front!
+
+
Device support
+
+
Even though a lot of devices are supported by Rflink, not all have been tested/implemented. If you have a device supported by Rflink but not by this component please consider testing and adding support yourself or create an issue and mention @aequitas in the description.
+
+
Technical overview
+
+
+
Therflink Python module a asyncio transport/protocol is setup that fires an callback for every (valid/supported) packet received by the Rflink gateway.
+
This component uses this callback to distribute ‘rflink packet events’ over the HASS bus which can be subscribed to by entities/platform implementations.
+
The platform implementions take care of creating new devices (if enabled) for unsees incoming packet id’s.
+
Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entitiy logic is maintained in this main component.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/rfxtrx/index.html b/components/rfxtrx/index.html
index dd72ab797f..60727d9017 100644
--- a/components/rfxtrx/index.html
+++ b/components/rfxtrx/index.html
@@ -232,6 +232,9 @@
diff --git a/components/script/index.html b/components/script/index.html
index 43e9c93fc6..db3e9b1e3c 100644
--- a/components/script/index.html
+++ b/components/script/index.html
@@ -209,6 +209,9 @@ The preferred way to separate words for better readability is to use underscore
diff --git a/components/sensor.bbox/index.html b/components/sensor.bbox/index.html
index d8b274ddc5..9443ae5781 100644
--- a/components/sensor.bbox/index.html
+++ b/components/sensor.bbox/index.html
@@ -246,9 +246,15 @@ Due to third party limitation, the sensors will only be available if Home Assist
diff --git a/components/sensor.bom/index.html b/components/sensor.bom/index.html
index 75b022366a..b8b041df97 100644
--- a/components/sensor.bom/index.html
+++ b/components/sensor.bom/index.html
@@ -195,6 +195,9 @@ The weather platform is easier to configure but less customisable.
diff --git a/components/sensor.broadlink/index.html b/components/sensor.broadlink/index.html
index 447e472bfb..baa0099305 100644
--- a/components/sensor.broadlink/index.html
+++ b/components/sensor.broadlink/index.html
@@ -290,9 +290,15 @@ The pycrypto library needs to be available on your platform. On a typical window
diff --git a/components/sensor.darksky/index.html b/components/sensor.darksky/index.html
index 2640b4fdc4..d8fa570b97 100644
--- a/components/sensor.darksky/index.html
+++ b/components/sensor.darksky/index.html
@@ -221,6 +221,9 @@ Note: While the platform is called “darksky” the sensors will show up in Hom
diff --git a/components/sensor.haveibeenpwned/index.html b/components/sensor.haveibeenpwned/index.html
index 3e4c87b625..9ac8d9df77 100644
--- a/components/sensor.haveibeenpwned/index.html
+++ b/components/sensor.haveibeenpwned/index.html
@@ -240,9 +240,15 @@ account has been breached as well as the added date of the breach data. This dat
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index 765d87ab42..9a9dad7bf6 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -106,7 +106,7 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
-
For a quick test curl can be useful to “simulate” a device.
+
For a quick test, curl can be useful to “simulate” a device.
$ curl -X POST -H "x-ha-access: YOUR_PASSWORD"\
-H "Content-Type: application/json"\
@@ -115,7 +115,7 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
-
Use again curl to retrieve the current state to check if the sensor is working.
+
You can then use curl again to retrieve the current sensor state and verify the sensor is working.
$ curl -X GET -H "x-ha-access: YOUR_PASSWORD"\
-H "Content-Type: application/json"\
@@ -261,9 +261,15 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
timeout (Optional): Define the timeout value in seconds when polling (defaults to 10 if not defined)
retries (Optional): Define the number of retries when polling (defaults to 2 if not defined)
cache (Optional): Define cache expiration value in seconds (defaults to 1200 if not defined)
+
adapter (Optional): Define the bluetooth adapter to use (defaults to hci0). Run hciconfig to get a list of available adapters.
Note that by default the sensor is only polled once every 15 minutes. This means with the median: 3 setting will take as least 30 minutes before the sensor will report a value after a Home Assistant restart. As the values usually change very slowly, this isn’t a big problem.
diff --git a/components/sensor.min_max/index.html b/components/sensor.min_max/index.html
index 1b2eb9a4b1..e32c1a07c1 100644
--- a/components/sensor.min_max/index.html
+++ b/components/sensor.min_max/index.html
@@ -240,9 +240,15 @@
diff --git a/components/sensor.moldindicator/index.html b/components/sensor.moldindicator/index.html
index 82500da5ae..faa1e3f76d 100644
--- a/components/sensor.moldindicator/index.html
+++ b/components/sensor.moldindicator/index.html
@@ -242,9 +242,15 @@ With the three measured temperatures (in Celsius or Fahrenheit), the calibration
diff --git a/components/sensor.mqtt_room/index.html b/components/sensor.mqtt_room/index.html
index 1d40505c16..af410d9a38 100644
--- a/components/sensor.mqtt_room/index.html
+++ b/components/sensor.mqtt_room/index.html
@@ -209,6 +209,9 @@ Instead of developing your own application, you can also use any of these alread
By using V_UNIT_PREFIX, it’s possible to set a custom unit for any sensor. The string value that is sent for V_UNIT_PREFIX will be used in preference to any other unit of measurement, for the defined sensors. V_UNIT_PREFIX can’t be used as a standalone sensor value type. Sending a supported value type and value from the tables above is also required. V_UNIT_PREFIX is available with MySensors version 1.5 and later.
-
For more information, visit the serial api of MySensors.
+
For more information, visit the serial api of MySensors.
diff --git a/components/sensor.nest/index.html b/components/sensor.nest/index.html
index db0ce599b4..a04d3898ef 100644
--- a/components/sensor.nest/index.html
+++ b/components/sensor.nest/index.html
@@ -269,9 +269,15 @@ You must have the Nest component configured to u
diff --git a/components/sensor.nest_weather/index.html b/components/sensor.nest_weather/index.html
index 8659ee49d4..5be4f4e79b 100644
--- a/components/sensor.nest_weather/index.html
+++ b/components/sensor.nest_weather/index.html
@@ -155,6 +155,9 @@ You must have the Nest component configured to u
diff --git a/components/sensor.octoprint/index.html b/components/sensor.octoprint/index.html
index e87fbc217c..6fb96434e7 100644
--- a/components/sensor.octoprint/index.html
+++ b/components/sensor.octoprint/index.html
@@ -248,9 +248,15 @@ You must have the OctoPrint component confi
host (Required): The IP address of the QNAP NAS to monitor
+
port (Optional): The port number on which the QNAP NAS web interface is reachable. Defaults to 8080.
+
ssl (Optional): Whether to connect via https. Defaults to false.
+
username (Required): An user to connect to the QNAP NAS.
+
password (Required): The password of the user to connect to the QNAP NAS.
+
drives (Optional): Array of drives to monitor (ex: 0:1). Defaults to all drives.
+
volumes (Optional): Array of volumes to monitor (ex: DataVol1). Defaults to all volumes.
+
nics (Optional): Array of network interfaces to monitor (ex: eth0). Defaults to all NICs.
+
monitored_conditions (Required): Defines the stats to monitor as sensors.
+
+
status: Displays overall system health.
+
cpu_temp: Displays the CPU’s temperature.
+
cpu_usage: Displays the CPU’s utilization as a percentage.
+
memory_free: Displays the size of available RAM in GB.
+
memory_used: Displays the size of used RAM in GB.
+
memory_percent_used: Displays the size of used RAM as a percentage of total RAM.
+
network_link_status: Displays whether the network interfaces is up (creates a new entry for each interface).
+
network_tx: Displays the upload speed of a network interface in MB/s (creates a new entry for each interface).
+
network_rx: Displays the download speed of a network interface in MB/s (creates a new entry for each interface).
+
drive_smart_status: Displays the S.M.A.R.T. status of the drive (creates a new entry for each drive).
+
drive_temp: Displays the temperature of the drive (creates a new entry for each drive).
+
volume_size_free: Displays the available space of the volume in GB (creates a new entry for each volume).
+
volume_size_used: Displays the used space of the volume in GB (creates a new entry for each volume).
+
volume_percentage_used: Displays the used space of the volume as a percentage (creates a new entry for each volume).
+
+
+
+
+
QNAP device support:
+
+
This component has been tested on a TS-451 running QTS 4.2.2. Other QNAP NAS devices using similar firmware should work fine.
+For more information about supported devices, or to report issues with your device, please visit the qnapstats project.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.random/index.html b/components/sensor.random/index.html
index dc43535079..e0aaea97c5 100644
--- a/components/sensor.random/index.html
+++ b/components/sensor.random/index.html
@@ -227,9 +227,15 @@
The rflink component support devices that use Rflink gateway firmware, for example the Nodo Rflink Gateway. Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
After configuring the Rflink hub sensors will be automatically discovered and added.
+
+
New/unknown sensors can be assigned to a default group automatically by specifying the new_devices_group option with a group name. If the group doesn’t exist it will be created.
+
+
For example:
+
+
# Example configuration.yaml entry
+sensor:
+ platform:rflink
+ new_devices_group:"NewRflinkSensors"
+
+
+
+
Rflink sensor ID’s are composed of: protocol, id and type (optional). For example: alectov1_0334_temp. Some sensors emit multiple types of data. Each will be created as its own
+
+
Once the ID of a sensor is known it can be used to configure the sensor in HA, for example to add it to a different group, hide it or configure a nice name.
+
+
Assigning name to a sensor:
+
+
# Example configuration.yaml entry
+sensor:
+ platform:rflink
+ devices:
+ # assign name to a sensor
+ alectov1_0334_temp:
+ name:Temperature Outside
+
+
+
+
Configuration variables:
+
+
+
devices (Optional): A list of devices with their name to use in the frontend.
+
new_devices_group (Optional): Create group to add new/unknown devices to.
+
+
+
Device configuration variables:
+
+
+
name (Optional): Name for the device, defaults to Rflink ID.
+
sensor_type_ (Optional): Override automatically detected type of sensor.
+
unit_of_measurement (Optional): Override automatically detected unit of sensor.
+
aliasses (Optional): Alternative Rflink ID’s this device is known by.
+
+
+
Hiding/ignoring sensors
+
+
Sensors are added automatically when the Rflink gateway intercepts a 433Mhz command in the ether. To prevent cluttering the frontend use any of these methods:
+
+
+
Configure a new_devices_group for sensors and optionally add it to a different view.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.rfxtrx/index.html b/components/sensor.rfxtrx/index.html
index 5be2bfc951..1ecb0ea66c 100644
--- a/components/sensor.rfxtrx/index.html
+++ b/components/sensor.rfxtrx/index.html
@@ -304,9 +304,15 @@ Then you should update your configuration to (_temperature is not needed):
diff --git a/components/sensor.synologydsm/index.html b/components/sensor.synologydsm/index.html
index 87544a37ec..fa7c3b6e95 100644
--- a/components/sensor.synologydsm/index.html
+++ b/components/sensor.synologydsm/index.html
@@ -284,9 +284,15 @@ This sensor will wake up your Synology NAS if it’s in hibernation mode.
diff --git a/components/sensor.temper/index.html b/components/sensor.temper/index.html
index d4cbbd84fc..acb0dd20e2 100644
--- a/components/sensor.temper/index.html
+++ b/components/sensor.temper/index.html
@@ -230,9 +230,15 @@ The calculation follows the formula scale * sens
friendly_name (Optional): Name to use in the Frontend.
unit_of_measurement (Optional): Defines the units of measurement of the sensor, if any.
value_template (Required): Defines a template to extract a value from the event bus.
+
icon_template (Optional): Defines a template for the icon of the sensor.
entity_id (Optional): Add a list of entity IDs so the sensor only reacts to state changes of these entities. This will reduce the number of times the sensor will try to update it’s state.
@@ -217,6 +218,21 @@ Please note the blank line to close the multi-line template.
+
Change the icon
+
+
This example shows how to change the icon based on the day/night cycle.
diff --git a/components/sensor.usps/index.html b/components/sensor.usps/index.html
index acef41324f..38526c0d4c 100644
--- a/components/sensor.usps/index.html
+++ b/components/sensor.usps/index.html
@@ -246,9 +246,15 @@ The USPS sensor logs into the MyUSPS website to scrape package data. It does not
diff --git a/components/sensor.wink/index.html b/components/sensor.wink/index.html
index af8bd8caf4..bb6afd3fbd 100644
--- a/components/sensor.wink/index.html
+++ b/components/sensor.wink/index.html
@@ -254,9 +254,15 @@ The above devices are confimed to work, but others may work as well.
diff --git a/components/sensor.yr/index.html b/components/sensor.yr/index.html
index b49bf4483c..ecf0dc411d 100644
--- a/components/sensor.yr/index.html
+++ b/components/sensor.yr/index.html
@@ -176,6 +176,9 @@ weather forecast is delivered by the Norwegian Meteorological Institute and the
diff --git a/components/sensor.yweather/index.html b/components/sensor.yweather/index.html
index 63e3441586..24490a2b64 100644
--- a/components/sensor.yweather/index.html
+++ b/components/sensor.yweather/index.html
@@ -171,6 +171,9 @@ Use of the Yahoo Weather API should not exceed reasonable request volume. Access
diff --git a/components/sensor.zoneminder/index.html b/components/sensor.zoneminder/index.html
index 823c76506b..15d664a1e6 100644
--- a/components/sensor.zoneminder/index.html
+++ b/components/sensor.zoneminder/index.html
@@ -237,9 +237,15 @@ You must have the ZoneMinder component con
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index e37fdb2b26..27e5809d70 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -250,6 +250,9 @@ This switch will shutdown your host immediately, there will be no confirmation.
The fritzdect switch platform allows you to control the state of your AVM FRITZ!DECT DECT-based wireless switches. The AVM FRITZ!DECT switches need to be paired to your Fritz!Box and then can be monitored and controlled via Home Assistant.
+
+
Supported devices (tested):
+
+
+
FRITZ!DECT 200
+
+
+
Supported Firmwares (tested):
+
+
+
FRITZ!OS: 06.80 / FRITZ!DECT: 03.83
+
FRITZ!OS: 06.60 / FRITZ!DECT: 03.83
+
+
+
To use your AVM FRITZ!DECT switch(es) in your installation, add the following to your configuration.yaml file:
username (Required): The username for your Fritz!Box.
+
password (Required): The password for your Fritz!Box.
+
host (Optional): The IP address/hostname of your Fritz!Box. Defaults to fritz.box.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index a1fab4c2ae..de60903bd1 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -152,6 +152,9 @@ Currently works using default https port only.
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index c3fa2b6918..55826b584e 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -220,6 +220,9 @@ Make sure that your topic match exact. some-topi
All V_TYPES for each S_TYPE above are required to activate the actuator for the platform. Use either V_LIGHT or V_STATUS depending on library version for cases where that V_TYPE is required.
-
For more information, visit the serial api of MySensors.
+
For more information, visit the serial api of MySensors.
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 87dafa0ac1..2e512dea10 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -155,6 +155,9 @@ This component relies on raw TCP commands to PulseAudio. In order for PulseAudio
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index 95b9b87050..47e7be7682 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -159,6 +159,9 @@ Make sure that the URL matches exactly your endpoint or resource.
The rflink component support devices that use Rflink gateway firmware, for example the Nodo Rflink Gateway. Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
The Rflink component does not know the difference between a switch and a light. Therefore all switchable devices are automatically added as light by default.
+
+
Rflink switch/light ID’s are composed of: protocol, id, switch. For example: newkaku_0000c6c2_1.
+
+
Once the ID of a switch is known it can be used to configure it as a switch type in HA, for example to add it to a different group, hide it or configure a nice name.
devices (Optional): A list of devices with their name to use in the frontend.
+
device_defaults: (Optional)
+
+
fire_event_ (Optional): Set default fire_event for Rflink switch devices (see below).
+
signal_repetitions (Optional): Set default signal_repetitions for Rflink switch devices (see below).
+
+
+
+
+
Device configuration variables:
+
+
+
name (Optional): Name for the device, defaults to Rflink ID.
+
aliasses (Optional): Alternative Rflink ID’s this device is known by.
+
fire_event_ (Optional): Fire an button_pressed event if this device is turned on or off (default: False).
+
signal_repetitions (Optional): Repeat every Rflink command this number of times (default: 1)
+
+
+
Switch state
+
+
Initially the state of a switch is unknown. When the switch is turned on or off (via frontend or 433Mhz remote) the state is known and will be shown in the frontend.
+
+
Sometimes a switch is controlled by multiple 433Mhz remotes, each remote has its own code programmed in the switch. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
Any on/off command from any alias ID updates the current state of the switch. However when sending a command through the frontend only the primary ID is used.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/switch.rfxtrx/index.html b/components/switch.rfxtrx/index.html
index 47bb530706..bfe596ba6b 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -282,6 +282,9 @@ Then you should update your configuration to:
diff --git a/components/switch.rpi_rf/index.html b/components/switch.rpi_rf/index.html
index 7fb954522f..9160aceaf8 100644
--- a/components/switch.rpi_rf/index.html
+++ b/components/switch.rpi_rf/index.html
@@ -165,6 +165,9 @@ For more info see the PyPi module description:
Raspberry Pi RF Switch
+
diff --git a/components/switch.wake_on_lan/index.html b/components/switch.wake_on_lan/index.html
index 853998e563..bba84e03ed 100644
--- a/components/switch.wake_on_lan/index.html
+++ b/components/switch.wake_on_lan/index.html
@@ -175,6 +175,9 @@ from Home Assistant running on another Linux computer (the server
ANEL PwrCtrl Switch
+
diff --git a/components/weather.bom/index.html b/components/weather.bom/index.html
index 74af8b109b..8798e7cb08 100644
--- a/components/weather.bom/index.html
+++ b/components/weather.bom/index.html
@@ -154,6 +154,9 @@ The weather platform is easier to configure but less customisable.
diff --git a/components/weather.openweathermap/index.html b/components/weather.openweathermap/index.html
index 8499f561c1..914c936b70 100644
--- a/components/weather.openweathermap/index.html
+++ b/components/weather.openweathermap/index.html
@@ -160,6 +160,9 @@ This platform is an alternative to the Flashing lights triggered by an alarm
-
For flashing regular lights in case the the triggering of an alarm.
+
For flashing regular lights in case an alarm is triggered.
# AlmAct1 - switch to activate the alarm in Room1# AlmSnd1 - switch for a buzzer
diff --git a/cookbook/custom_panel_using_react/index.html b/cookbook/custom_panel_using_react/index.html
index 7c56e44f01..67606c6dde 100644
--- a/cookbook/custom_panel_using_react/index.html
+++ b/cookbook/custom_panel_using_react/index.html
@@ -143,6 +143,9 @@
diff --git a/developers/architecture_components/index.html b/developers/architecture_components/index.html
index 1f958c657e..433addfa66 100644
--- a/developers/architecture_components/index.html
+++ b/developers/architecture_components/index.html
@@ -213,6 +213,7 @@ Diagram showing interaction between components and the Home Assistant core
diff --git a/developers/component_discovery/index.html b/developers/component_discovery/index.html
index a47d797913..e5b3ccf750 100644
--- a/developers/component_discovery/index.html
+++ b/developers/component_discovery/index.html
@@ -194,6 +194,7 @@ This option is only available for built-in components.
diff --git a/developers/component_generic_discovery/index.html b/developers/component_generic_discovery/index.html
index eea4088f99..cff05aad05 100644
--- a/developers/component_generic_discovery/index.html
+++ b/developers/component_generic_discovery/index.html
@@ -228,6 +228,7 @@ This can be achieved using the load_platformAdd State Card
diff --git a/developers/component_loading/index.html b/developers/component_loading/index.html
index 83f485776a..b7811f0df5 100644
--- a/developers/component_loading/index.html
+++ b/developers/component_loading/index.html
@@ -177,6 +177,7 @@ Home Assistant will use the directory that contains your config file as the dire
diff --git a/developers/component_visibility/index.html b/developers/component_visibility/index.html
index df667c7b74..f2dd4b9917 100644
--- a/developers/component_visibility/index.html
+++ b/developers/component_visibility/index.html
@@ -171,6 +171,7 @@ You can set a suggestion for your entity’s visibility by setting the Add State Card
diff --git a/developers/development_environment/index.html b/developers/development_environment/index.html
index bef90bee66..bfd92a9682 100644
--- a/developers/development_environment/index.html
+++ b/developers/development_environment/index.html
@@ -237,6 +237,7 @@ logging to DEBUG to see even more details about what is going on.
diff --git a/developers/frontend/index.html b/developers/frontend/index.html
index 44ca5f30b4..3807bc4236 100644
--- a/developers/frontend/index.html
+++ b/developers/frontend/index.html
@@ -229,6 +229,7 @@ Do not use development mode in production. Home Assistant uses aggressive cachin
If you would like to use your own State card without merging your code into home-assistant-polymer you can create your own implementation.
+
+
+
Put the element source file and its dependencies in www/custom_ui/ directory under you homeassistant config.
+
+
+
For example if creating a state card for the light domain named my_custom_light_card put state-card-my_custom_light_card.html in www/custom_ui/.
+
+
That file should implement <state-card-my_custom_light_card> tag with Polymer.
+
+
In state-card-my_custom_light_card.html you should use <link rel="import"> to import all the dependencies not used by Homeassistant UI.
+Do not import any dependencies used by Homeassistant UI.
+Importing those will work in development: 1 mode, but will fail in production mode.
+
+
+
In the customize: section of configuration.yaml put custom_ui_state_card: <element-name>.
diff --git a/developers/index.html b/developers/index.html
index a4612f9fee..29a8ca0231 100644
--- a/developers/index.html
+++ b/developers/index.html
@@ -174,6 +174,7 @@ Diagram showing interaction between components and the Home Assistant core.
diff --git a/developers/multiple_instances/index.html b/developers/multiple_instances/index.html
index a408e7cd10..3279582203 100644
--- a/developers/multiple_instances/index.html
+++ b/developers/multiple_instances/index.html
@@ -193,6 +193,7 @@ Because each slave maintains its own Service Registry it is possible to have mul
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index d82c0e3240..a12f4d79d4 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -651,6 +651,7 @@ If your client does not support DELETE HTTP requests you can add an
diff --git a/developers/websocket_api/index.html b/developers/websocket_api/index.html
index b948ec48bd..529d1904de 100644
--- a/developers/websocket_api/index.html
+++ b/developers/websocket_api/index.html
@@ -526,6 +526,7 @@ b. Server can send results of previous commands.
diff --git a/ecosystem/ios/index.html b/ecosystem/ios/index.html
index 93ea4a7dd2..6986e787f7 100644
--- a/ecosystem/ios/index.html
+++ b/ecosystem/ios/index.html
@@ -120,7 +120,7 @@ Currently, the app is only available via a closed beta. It will be on the App St
The ios component is the companion component for the Home Assistant iOS app. While not required, adding the ios component to your setup will greatly enhance the iOS app with new notification, location and sensor functions not possible with a standalone app.
-
Loading the ios component will also load the device_tracker and zeroconf components. It also provides functionality required for the iOS notify platform but will not automatically load the notify component or platform as of 0.31.1. You must manually load it. See the iOS notify platform for more information.