- 2017-01-15T17:19:03+00:00
+ 2017-01-15T17:46:00+00:00https://home-assistant.io/
@@ -13,6 +13,99 @@
Octopress
+
+
+
+ 2017-01-14T08:04:05+00:00
+ https://home-assistant.io/blog/2017/01/14/iss-usps-images-packages
+ Welcome to 2017 and 0.36. We are proud to announce the first release for this year. While we are still migrating parts to async but 0.36 is focusing on new features and a lot of bug fixes.
+
+
Packages
+
Packages are providing a new way to organize different component’s configuration parts together. With packages we offer the option to include different components or parts of configuration using any of the !include directives.
+
+
InfluxDB export
+
The InfluxDB component was causing problems in a wide variety of use cases. @titilambert improved our InfluxDB exporter feature. It might be that you need to run the migration script to update your InfluxDB database.
No, unfortunately we are not going to space. The iss sensor is tracking the position of the International Space Station and gives your some details.
+
+
Insteon local
+
The support for Insteon was removed due to issues a while ago. With the insteon_local component support for Insteon is back and let one work locally with an Insteon setup.
+
+
Image processing
+
The new image processing component currently works with number plates. But this could level the way to integrate feature like facial recognition, motion detection, or gestures control.
APNS service was moved to the notify domain. Use notify.apns_NOTIFIER_NAME instead of apns.NOTIFIER_NAME.
+
InfluxDB component has a new schema to store values in the InfluxDB database. You may require to run the influxdb_migrator script.
+You have to note:
+
+
There will not be any tags/fields named time anymore.
+
All numeric fields (int/float/bool) will be stored as float inside influx db.
+
All string fields corresponding to state attributes will be renamed as FIELDNAME_str, where FIELDNAME is the state attribute, to avoid type conflicts.
+
All string fields corresponding to a state will be renamed as state (former value).
+
Fields named value will always be stored as float.
+
Fields named state will always be stored as string.
+
+
+
+
+
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 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.
+
+]]>
+
+
@@ -2050,121 +2143,6 @@ Heatmap
Prefetch the other pages using <link rel="preload" …>
-]]>
-
-
-
-
-
- 2016-08-03T17:22:00+00:00
- https://home-assistant.io/blog/2016/08/03/laundry-automation-update
- This is a guest post by Home Assistant user and contributor Nolan Gilley.
-
-
Today I’ll show you how I used Home Assistant, a NodeMCU (ESP8266), and a couple of accelerometers to automate our laundry room. This is a rewrite of an old post where I did the same thing using a Moteino & Raspberry Pi. This version only requires a NodeMCU.
-
-
We have an older washer and dryer which doesn’t have any form of notification when cycles complete. Home Assistant was the obvious solution, I just needed to create sensors for the washer and dryer. I tried using sound sensors but found them unreliable. I ended up using an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect whether they’re open or closed. I connected the accelerometers and reed switches to an NodeMCU which will relay the data to my MQTT broker.
-
-
-
- Block diagram of schematic
-
-
-
-
-
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in each direction for the accelerometer connected to the dryer. It’s easy to see when the dryer is in operation here. I used the same technique for the washer’s accelerometer.
-
-
-
- Graph showing the accelerometer data
-
-
-
Next it was just a matter of integrating everything with Home Assistant. I was able to use the MQTT component to read the washer and dryer states from the Moteino and display it in Home Assistant.
-
-
-
- Status of the dryer and washer in Home Assistant
-
-
-
Next I wrote scripts that are run whenever the washer or dryer completes a load. This is triggered by the automation component. When the laundry is complete I have the lights in the house turn red and notify me via Join. Once the door is opened and laundry emptied another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.
-
-
-
-
-
- NodeMCU connected to MPU-6050 accelerometer.
-
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 1bd5960d96..497a279cc1 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 523940c4cd..041c48045d 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 fc65cd5d5d..ec27857830 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 1a7b9fa12a..de25a45b15 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 2029c5180c..02568eae37 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 e51e2f4f34..9dc9d41d7c 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 80e7b290f9..f286b1e832 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 ee9d155829..909511aa5c 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 62414b315b..89355a522e 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
- 0.33: New Calendar component, Wink thermostats and Cisco IOS
-
-
-
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 244344083c..b1ddfd6702 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 0adae55ce7..2b224dd543 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 93aff6282a..a72c74db6d 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 c36383e9f0..3c60d204bf 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 8ed5c1b27f..8813109df8 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 b9fca7330d..12a3253d95 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 cfd38aa1c8..eef5ac1c0c 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 a7fbc87d62..f6d38c5f73 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 689b9deb46..c63cc953b7 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 ea942d86ec..20357bb18d 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 895c3ae309..5f49472468 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 ba2ba352f5..7462a56cf6 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
- 0.33: New Calendar component, Wink thermostats and Cisco IOS
-
-
-
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 bb660e5b8b..964cec5ed1 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 c80f3a4aa8..e5fb79b7a4 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 a132fe525f..3b62f046d0 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
- 0.33: New Calendar component, Wink thermostats and Cisco IOS
-
-
-
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 99a8a3b84b..2cb30b5d9c 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 c293f9c81d..02677c3763 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
Welcome to 2017 and 0.36. We are proud to announce the first release for this year. While we are still migrating parts to async but 0.36 is focusing on new features and a lot of bug fixes.
+
+
Packages
+
Packages are providing a new way to organize different component’s configuration parts together. With packages we offer the option to include different components or parts of configuration using any of the !include directives.
+
+
InfluxDB export
+
The InfluxDB component was causing problems in a wide variety of use cases. @titilambert improved our InfluxDB exporter feature. It might be that you need to run the migration script to update your InfluxDB database.
No, unfortunately we are not going to space. The iss sensor is tracking the position of the International Space Station and gives your some details.
+
+
Insteon local
+
The support for Insteon was removed due to issues a while ago. With the insteon_local component support for Insteon is back and let one work locally with an Insteon setup.
+
+
Image processing
+
The new image processing component currently works with number plates. But this could level the way to integrate feature like facial recognition, motion detection, or gestures control.
APNS service was moved to the notify domain. Use notify.apns_NOTIFIER_NAME instead of apns.NOTIFIER_NAME.
+
InfluxDB component has a new schema to store values in the InfluxDB database. You may require to run the influxdb_migrator script.
+You have to note:
+
+
There will not be any tags/fields named time anymore.
+
All numeric fields (int/float/bool) will be stored as float inside influx db.
+
All string fields corresponding to state attributes will be renamed as FIELDNAME_str, where FIELDNAME is the state attribute, to avoid type conflicts.
+
All string fields corresponding to a state will be renamed as state (former value).
+
Fields named value will always be stored as float.
+
Fields named state will always be stored as string.
+
+
+
+
+
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 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 1f84cc1070..938e990cc1 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -3189,6 +3189,38 @@
+
+
+
+
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 6456a6cacd..a71eb9973a 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2017-01-15T17:19:03+00:00
+ 2017-01-15T17:46:00+00:00https://home-assistant.io/
@@ -13,6 +13,173 @@
Octopress
+
+
+
+ 2017-01-14T08:04:05+00:00
+ https://home-assistant.io/blog/2017/01/14/iss-usps-images-packages
+ Packages
+[Packages][packages] are providing a new way to organize different component's configuration parts together. With packages we offer the option to include different components or parts of configuration using any of the `!include` directives.
+
+## InfluxDB export
+The [InfluxDB][influx] component was causing problems in a wide variety of use cases. [@titilambert] improved our InfluxDB exporter feature. It might be that you need to run the migration script to update your InfluxDB database.
+
+```bash
+$ hass --script influxdb_migrator \
+ -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \
+ -o test_series -d INFLUXDB_DB_NAME
+```
+
+## International Space Station (ISS)
+No, unfortunately we are not going to space. The `iss` sensor is tracking the position of the International Space Station and gives your some details.
+
+## Insteon local
+The support for Insteon was removed due to issues a while ago. With the `insteon_local` component support for [Insteon][insteon] is back and let one work locally with an Insteon setup.
+
+## Image processing
+The new [image processing component][image] currently works with [number plates][plates]. But this could level the way to integrate feature like facial recognition, motion detection, or gestures control.
+
+## All changes
+- Sensor: Support for [HydroQuebec][quebec] ([@titilambert])
+- Sensor: Tracking the [ISS][iss] ([@HydrelioxGitHub])
+- Sensor: [USPS][usps] deliveries tracking ([@happyleavesaoc])
+- Device tracker: New [ping-based][ping] tracker ([@michaelarnauts])
+- TTS: Support for [Pico][pico] ([@doudz])
+- Switch: [BeagleBone Black][beaglebone] GPIO are supported now ([@MatoKafkac])
+- Light: New support for [Tikteck][tik] Bluetooth bulbs ([@mjg59])
+- Switch: Support for customised [Kankun SP3 Wifi][kankun] switches ([@webworxshop])
+- Insteon local: Local [insteon][insteon] support([@wardcraigj])
+- `rest_command`: Support for using [REST][rest] ([@pvizeli])
+- Sensor: Show details of the [Dublin RTPI][dublin] information ([@ttroy50])
+- Light: [Zengge Bluetooth][zengge] bulbs ([@mjg59])
+- Fan: Wink support for [fans][wink-fan] ([@w1ll1am23])
+- Device tracker: New [TrackR][trackr] device tracker support ([@w1ll1am23])
+- Device tracker: Support for [Xiaomi router][xiaomi] ([@RiRomain])
+- Sensor: New [SMA Solar Webconnect][sma] sensor ([@kellerza])
+- Notify: [Lannouncer][lannouncer] TTS support ([@michaelarnauts])
+- Image processing: Support for [Image processing][image] ([@pvizeli])
+- Device tracker: [UPC][upc] Connect box platform support ([@pvizeli])
+- Weather: [Australian BOM][bom] (Bureau of Meteorology) support ([@Zac-HD])
+- Notify: Support for [MySensors][mysensors] notifications ([@MartinHjelmare])
+- TTS: New [Yandex SpeechKit TTS][yandex] integration ([@lupin-de-mid])
+
+- Sensor - sonarr: Add `urlbase` to [Sonarr][] ([@quadportnick])
+- Switch - broadlink: Support for [SP][bl-switch] devices ([@Danielhiversen])
+- Homematic: Support for HMIP-PSM or HMWIOSwitch ([@danielperna84], [@pvizeli])
+- Light - flux: Ledenet protocol support by Flux LED ([@bah2830])
+- Device tracker: Support for longer intervals ([@partofthething])
+- ISY994: Weather sensors added ([@rmkraus])
+- InfluxDB: Improvements to avoid issues with storing details ([@titilambert])
+- Light - Yeelight: Auto discovery support and color temperature feature for [Yeelight][yeelight] ([@jjensn])
+- Media player - SqueezeBox: Switch to JSON-RPC ([@dasos])
+- Scripts: Support for `last_triggered` ([@Danielhiversen])
+- Media player: Support for `SUPPORT_PLAY` flag ([@armills])
+- Minor and not so minor features and bug fixes by [@balloob], [@pvizeli], [@fabaff], [@mezz64], [@andrey-git], [@aequitas], [@abmantis], [@turbokongen], [@jabesq], [@michaelarnauts], [@kellerza], [@titilambert], [@btorresgil], [@henworth], [@armills], [@mjg59], [@Giannie], [@n8henrie], [@magicus], [@florianholzapfel], [@MrMep], [@bah2830], [@happyleavesaoc], [@lwis], [@glance-], [@markferry], and [@nikdoof].
+
+## Breaking changes
+- [APNS][apns] service was moved to the `notify` domain. Use `notify.apns_NOTIFIER_NAME` instead of `apns.NOTIFIER_NAME`.
+- [InfluxDB][influx] component has a new schema to store values in the InfluxDB database. You may require to run the `influxdb_migrator` script.
+ You have to note:
+ - There will not be any tags/fields named time anymore.
+ - All numeric fields (int/float/bool) will be stored as float inside influx db.
+ - All string fields corresponding to state attributes will be renamed as FIELDNAME_str, where FIELDNAME is the state attribute, to avoid type conflicts.
+ - All string fields corresponding to a state will be renamed as state (former value).
+ - Fields named value will always be stored as float.
+ - Fields named state will always be stored as string.
+
+## If you need help...
+...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## Reporting Issues
+Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
+
+[@abmantis]: https://github.com/abmantis
+[@aequitas]: https://github.com/aequitas
+[@andrey-git]: https://github.com/andrey-git
+[@armills]: https://github.com/armills
+[@bah2830]: https://github.com/bah2830
+[@balloob]: https://github.com/balloob
+[@brandonweeks]: https://github.com/brandonweeks
+[@btorresgil]: https://github.com/btorresgil
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@danieljkemp]: https://github.com/danieljkemp
+[@danielperna84]: https://github.com/danielperna84
+[@dasos]: https://github.com/dasos
+[@DavidLP]: https://github.com/DavidLP
+[@doudz]: https://github.com/doudz
+[@eieste]: https://github.com/eieste
+[@fabaff]: https://github.com/fabaff
+[@florianholzapfel]: https://github.com/florianholzapfel
+[@Giannie]: https://github.com/Giannie
+[@glance-]: https://github.com/glance-
+[@happyleavesaoc]: https://github.com/happyleavesaoc
+[@henworth]: https://github.com/henworth
+[@HydrelioxGitHub]: https://github.com/HydrelioxGitHub
+[@jabesq]: https://github.com/jabesq
+[@jjensn]: https://github.com/jjensn
+[@kellerza]: https://github.com/kellerza
+[@kk7ds]: https://github.com/kk7ds
+[@lwis]: https://github.com/lwis
+[@magicus]: https://github.com/magicus
+[@markferry]: https://github.com/markferry
+[@MatoKafkac]: https://github.com/MatoKafkac
+[@mezz64]: https://github.com/mezz64
+[@michaelarnauts]: https://github.com/michaelarnauts
+[@mjg59]: https://github.com/mjg59
+[@MrMep]: https://github.com/MrMep
+[@n8henrie]: https://github.com/n8henrie
+[@nikdoof]: https://github.com/nikdoof
+[@partofthething]: https://github.com/partofthething
+[@pvizeli]: https://github.com/pvizeli
+[@quadportnick]: https://github.com/quadportnick
+[@RiRomain]: https://github.com/RiRomain
+[@rmkraus]: https://github.com/rmkraus
+[@scmmmh]: https://github.com/scmmmh
+[@technicalpickles]: https://github.com/technicalpickles
+[@ttroy50]: https://github.com/ttroy50
+[@turbokongen]: https://github.com/turbokongen
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@wardcraigj]: https://github.com/wardcraigj
+[@webworxshop]: https://github.com/webworxshop
+[@titilambert]: https://github.com/titilambert
+[@Zac-HD]: https://github.com/Zac-HD
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@lupin-de-mid]: https://github.com/lupin-de-mid
+
+[beaglebone]: https://home-assistant.io/components/bbb_gpio/
+[bl-switch]: https://home-assistant.io/components/switch.broadlink/
+[dublin]: https://home-assistant.io/components/sensor.dublin_public_transport/
+[image]: https://home-assistant.io/components/image_processing/
+[insteon]: https://home-assistant.io/components/insteon_local/
+[kankun]: https://home-assistant.io/components/switch.kankun/
+[lannouncer]: https://home-assistant.io/components/notify.lannouncer/
+[packages]: https://home-assistant.io/topics/packages/
+[pico]: https://home-assistant.io/components/tts.picotts/
+[ping]: https://home-assistant.io/components/device_tracker.ping/
+[plates]: https://home-assistant.io/components/openalpr/
+[quebec]: https://home-assistant.io/components/sensor.hydroquebec/
+[rest]: https://home-assistant.io/components/rest_command/
+[sma]: https://home-assistant.io/components/sensor.sma/
+[sonarr]: https://home-assistant.io/components/sensor.sonarr/
+[tik]: https://home-assistant.io/components/light.tikteck/
+[trackr]: https://home-assistant.io/components/device_tracker.trackr/
+[upc]: https://home-assistant.io/components/device_tracker.upc_connect/
+[usps]: https://home-assistant.io/components/sensor.usps/
+[wink-fan]: https://home-assistant.io/components/fan.wink/
+[xiaomi]: https://home-assistant.io/components/device_tracker.xiaomi/
+[yeelight]: https://home-assistant.io/components/light.yeelight/
+[zengge]: https://home-assistant.io/components/light.zengge/
+[bom]: https://home-assistant.io/components/weather.bom/
+[apns]: https://home-assistant.io/components/notify.apns/
+[mysensors]: https://home-assistant.io/components/notify.mysensors/
+[influx]: https://home-assistant.io/components/influxdb/
+[iss]: https://home-assistant.io/components/sensor.iss/
+[yandex]: https://home-assistant.io/components/tts.yandextts/
+]]>
+
+
@@ -685,307 +852,6 @@ Our website has now an additional category called "Ecosystem". This will become
[req-insteon]: https://github.com/home-assistant/home-assistant/issues/3811
[updater]: https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
[thingspeak]: https://home-assistant.io/components/thingspeak/
-]]>
-
-
-
-
-
- 2016-10-22T20:00:00+00:00
- https://home-assistant.io/blog/2016/10/22/flash-briefing-updater-hacktoberfest
- Stats Update
-Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
-
-## Hacktoberfest
-
-![Hacktoberfest logo][logo]
-
-October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the [home-assistant repository][hacktoberfest-ha-prs] and 209 merged/28 open pull requests submitted to the [home-assistant.github.io repository][hacktoberfest-site-prs]. If you want to get in on the fun check out our [Hacktoberfest][hacktoberfest-blog] blog post or the [Hacktoberfest website][hacktoberfest-website]. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
-
-## ⚠️ A greatly improved updater component (Please read this!) ⚠️
-
-This release includes an update to our [updater] component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
-
-It used to be that this component would check with [PyPi] (the Python package manager) to see if a new update was available. This had a couple of problems:
-
- 1. We are unable to do a slow rollout
- 2. We are unable to show the user extra information (like a link to a changelog or the release date)
- 3. We are unable to warn users for critical security updates
-
-So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
-
-### What you need to know (the important bit!)
-
-Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
-
-Each Home Assistant instance running the updater component will generate a [unique ID][UUID] (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called `.uuid`.
-
-#### Opting out
-
-There are two ways to opt-out. The first way is by using the new `opt_out` option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
-
-```yaml
-updater:
- reporting: no
-```
-
-You can also disable the updater component entirely by removing `updater:` from your `configuration.yaml` although **we would not suggest you do this** as you would miss any critical updates.
-
-Finally, you can also reset your unique identifier by deleting the `.uuid` file and restarting Home Assistant.
-
-#### Data stored on the Home Assistant update server
-
-Here is what my production Home Assistant instance looks like from the server side:
-
-| Name | Description | Example |
-|-----------------------|--------------------------------------------|------------------------------------|
-| `arch` | CPU Architecture | `x86_64` |
-| `distribution` | Linux Distribution name (only Linux) | `Ubuntu` |
-| `docker` | True if running inside Docker | `false` |
-| `os_name` | Operating system name | `Darwin` |
-| `os_version` | Operating system version | `10.12` |
-| `python_version` | Python version | `3.5.2` |
-| `timezone` | Timezone | `America/Los_Angeles` |
-| `user_agent` | User agent used to submit analytics | `python-requests/2.11.1` |
-| `uuid` | Unique identifier | `10321ee6094d4a2ebb5ed55c675d5f5e` |
-| `version` | Home Assistant version | `0.31.0` |
-| `virtualenv` | True if running inside virtualenv | `true` |
-
-In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: __The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your `configuration.yaml`.__
-
-
-
- Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
-
-
-The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
-
-| Name | Description | Example |
-|-----------------------|--------------------------------------------|------------------------------------|
-| `first_seen_datetime` | First time instance ID was submitted | `2016-10-22T19:56:03.542Z` |
-| `geo_city` | GeoIP determined city | `Oakland` |
-| `geo_country_code` | GeoIP determined country code | `US` |
-| `geo_country_name` | GeoIP determined country name | `United States` |
-| `geo_latitude` | GeoIP determined latitude (of the city) | `37.8047` |
-| `geo_longitude` | GeoIP determined longitude (of the city) | `-122.2124` |
-| `geo_metro_code` | GeoIP determined metro code | `807` |
-| `geo_region_code` | GeoIP determined region code | `CA` |
-| `geo_region_name` | GeoIP determined region name | `California` |
-| `geo_time_zone` | GeoIP determined time zone | `America/Los_Angeles` |
-| `geo_zip_code` | GeoIP determined zip code | `94602` |
-| `last_seen_datetime` | Most recent time instance ID was submitted | `2016-10-22T19:56:03.542Z` |
-
-This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me ([@robbiet480]). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just [@balloob] and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
-
-We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
-
-We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
-
-_This section was updated on October 24 to be more clear about geo-lookups being on the city level. [See original version.][blog-orig]_
-
-Now, back to the fun stuff...
-
-## Good evening. I'm Ron Burgundy and here's what happening in your world tonight.
-
-Home Assistant got a crazy idea recently that it couldn't do enough already and wanted to challenge itself even more. I really don't understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
-
-0.31 adds support for the brand spanking new [Alexa Flash Briefing API](https://developer.amazon.com/alexa-skills-kit/flash-briefing), allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What's the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
-
-> Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
-
-Now I know how to best get to [my real job][runway] (no, Home Assistant is _not_ my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does _not_ require HTTPS (_but you should still be using HTTPS if possible_). For more information, check out the new [docs][flash-briefing-docs].
-
-
-
- You stay classy, San Diego. (It's funny, because balloob lives in San Diego))
-
-
-## Major breaking Z-Wave changes ahead
-
-A rather nasty Z-Wave [issue][z-wave-issue] was discovered recently by [@lukas-hetzenecker]. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
-
-What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here's what I had to do:
-
-- Update customizations
-- Update groups
-- Update my `zwave.customize` section
-- Update my Alexa skills that used old entity IDs
-- Because I use `emulated_hue` with Alexa and `emulated_hue` uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
-
-Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It's not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
-
-This is super annoying, I know, especially since we had said in [0.12][zero-one-two-release] that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn't change in the future but obviously we see how that went. To sum up on this section... sorry but it had to happen.
-
-## All changes
-
-- [Updater] component ([@infamy], [@robbiet480], [@kellerza])
-- Continue to setup other platforms when 1 platform config is invalid ([@kellerza])
-- Create [persistent notifications][pers-notify] when a platform contains invalid config ([@kellerza])
-- Logbook: Allow [filtering] domains and entities to be shown ([@wokar])
-- HTTP: Change `approved_ips` from string to CIDR validation ([@mweinelt])
-- Persistent Notifications: Allow using [markdown][pers-notify] ([@justweb1])
-- Netatmo: Add [discovery][netatmo-discovery] support ([@jabesq])
-- Netatmo Welcome camera: Add [binary sensor][netatmo-bin] ([@jabesq])
-- Support added for [HaveIBeenPwned] ([@joyrider3774])
-- Device tracker: `known_devices.yaml` reading and writing tweaks and fixes ([@kellerza])
-- Fix climate platforms showing the wrong temperature unit ([@rcloran])
-- Lots of voluptuous love ([@fabaff])
-- Ensure proper attribution for weather platforms ([@fabaff])
-- Fix Telegram in Docker ([@jeanregisser])
-- Support recursive config inclusions in YAML ([@lwis])
-- Camera: [Synology] SS cameras now supported ([@jgriff2])
-- History: Allow filtering domains and entities to be shown ([@wokar])
-- Media Player - Squeezebox: Now able to show artist and album ([@ih8gates])
-- Alexa: Flash Briefing skill support added ([@robbiet480])
-- Device Tracker: Add support for Bbox Modem Router ([@HydrelioxGithub])
-- Sensor: Add support for Bbox Modem Router ([@HydrelioxGithub])
-- Input select: Services added to pick next and prev option ([@persandstrom])
-- Sensor: [ARWN] now supported ([@sdague])
-- Pushbullet: Push an URL note if an url is provided inside data ([@jabesq])
-- Z-Wave: Allow certain devices to be not added to Home Assistant ([@lukas-hetzenecker])
-- New support for [Zoneminder] added ([@Khabi])
-- Weather: Allow tracking severe weather alerts with [WUnderground] ([@tchellomello])
-- Sensor: New support added to track [min/max/mean][min] ([@fabaff])
-- Convert EntityComponent to be async ([@pvizeli], [@balloob])
-- Z-Wave: Add assocation service ([@turbokongen])
-- Frontend - Services dev tool: persist state and tweak UI ([@justweb1])
-- Sensor: Support added for [scraping][scrape] websites ([@fabaff])
-- Clean up of tests ([@capellini])
-- New `fail` filter added to templates to raise on UndefinedError ([@jaharkes])
-- Support added for [Emoncms history][emoncms] ([@joyrider3774])
-- Support for [Apple Push Notifications Service][APNS] ([@sam-io])
-- Thermostat: Netatmo now supported ([@gieljnssns])
-- Alarm control panel: [Concord232] now supported ([@JasonCarter80])
-- Notify: [Matrix] support added ([@mweinelt])
-- Device tracker - nmap: Allow specifying multiple inputs for [nmap] ([@hcooper])
-- Device Tracker - snmp: SNMPv3 now supported ([@T3m3z])
-- Notify: [Telstra] SMS now supported ([@nvella])
-- Camera: [Verisure] now supported ([@turbokongen])
-- Support added for [Neato] Connected Robot ([@jabesq])
-- Media player: More options for [Yamaha] AVR ([@ehagan])
-- Sensor: Support for [Pilight] sensor ([@DavidLP])
-- iOS support ([@robbiet480])
-- Minor features and bug fixes by [@mtl010957], [@molobrakos], [@flyte], [@fabaff], [@phardy], [@sander76], [@T3m3z], [@c-w], [@balloob], [@robbiet480], [@StaticCube], [@vittoriom], [@hartmms], [@kirichkov], [@mezz64], [@ishults], [@Danielhiversen] and [@tchellomello].
-
-### Release 0.31.1 - October 24
-
- - Identify special character encoding error in YAML files ([@kellerza], [@lwis])
- - iOS app component bug fixes ([@robbiet480])
- - Fix a spelling problem on user-facing error ([@robbiet480])
- - YAML includes will ignore dirs/files prefixed with . ([@lwis])
-
-## Breaking changes
-
- - The [HTTP] component now takes a different format for authenticating IPs
- - Configuration format has changed for [Proximity]
- - The [Arduino] platform are now covered by the configuration check. Please check the documentation to see how.
- - The Z-Wave entity ID change mentioned above
-
-## If you need help...
-...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
-
-## Until next time
-
-Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
-
--- Robbie
-
-[@balloob]: https://github.com/balloob
-[@capellini]: https://github.com/capellini
-[@c-w]: https://github.com/c-w
-[@Danielhiversen]: https://github.com/Danielhiversen
-[@DavidLP]: https://github.com/DavidLP
-[@ehagan]: https://github.com/ehagan
-[@fabaff]: https://github.com/fabaff
-[@flyte]: https://github.com/flyte
-[@gieljnssns]: https://github.com/gieljnssns
-[@hartmms]: https://github.com/hartmms
-[@hcooper]: https://github.com/hcooper
-[@HydrelioxGithub]: https://github.com/HydrelioxGithub
-[@ih8gates]: https://github.com/ih8gates
-[@infamy]: https://github.com/infamy
-[@ishults]: https://github.com/ishults
-[@jabesq]: https://github.com/jabesq
-[@jaharkes]: https://github.com/jaharkes
-[@JasonCarter80]: https://github.com/JasonCarter80
-[@jeanregisser]: https://github.com/jeanregisser
-[@jgriff2]: https://github.com/jgriff2
-[@joyrider3774]: https://github.com/joyrider3774
-[@justweb1]: https://github.com/justweb1
-[@kellerza]: https://github.com/kellerza
-[@Khabi]: https://github.com/Khabi
-[@kirichkov]: https://github.com/kirichkov
-[@lukas-hetzenecker]: https://github.com/lukas-hetzenecker
-[@lwis]: https://github.com/lwis
-[@mezz64]: https://github.com/mezz64
-[@molobrakos]: https://github.com/molobrakos
-[@mtl010957]: https://github.com/mtl010957
-[@mweinelt]: https://github.com/mweinelt
-[@Nixon506E]: https://github.com/Nixon506E
-[@nvella]: https://github.com/nvella
-[@persandstrom]: https://github.com/persandstrom
-[@phardy]: https://github.com/phardy
-[@pvizeli]: https://github.com/pvizeli
-[@rcloran]: https://github.com/rcloran
-[@robbiet480]: https://github.com/robbiet480
-[@sam-io]: https://github.com/sam-io
-[@sander76]: https://github.com/sander76
-[@sdague]: https://github.com/sdague
-[@StaticCube]: https://github.com/StaticCube
-[@T3m3z]: https://github.com/T3m3z
-[@tchellomello]: https://github.com/tchellomello
-[@turbokongen]: https://github.com/turbokongen
-[@vittoriom]: https://github.com/vittoriom
-[@wokar]: https://github.com/wokar
-
-[Arduino]: https://home-assistant.io/components/arduino/
-[APNS]: https://home-assistant.io/components/notify.apns/
-[ARWN]: https://home-assistant.io/components/sensor.arwn/
-[Concord232]: https://home-assistant.io/components/alarm_control_panel.concord232/
-[HTTP]: https://home-assistant.io/components/http/
-[HaveIBeenPwned]: https://home-assistant.io/components/sensor.haveibeenpwned/
-[Matrix]: https://home-assistant.io//components/notify.matrix/
-[Neato]: https://home-assistant.io/components/switch.neato/
-[Pilight]: https://home-assistant.io/components/sensor.pilight/
-[Proximity]: https://home-assistant.io/components/proximity/
-[PyPi]: https://pypi.python.org/pypi
-[Synology]: https://home-assistant.io/components/camera.synology/
-[Telstra]: https://home-assistant.io/components/notify.telstra/
-[UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier
-[Verisure]: https://home-assistant.io/components/camera.verisure/
-[WUnderground]: https://home-assistant.io/components/sensor.wunderground/
-[Yamaha]: https://home-assistant.io/components/media_player.yamaha/
-[Zoneminder]: https://home-assistant.io/components/zoneminder/
-[emoncms]: https://home-assistant.io//components/emoncms_history/
-[filtering]: https://home-assistant.io/components/logbook/
-[flash-briefing-docs]: https://home-assistant.io/components/alexa/
-[hacktoberfest-blog]: /blog/2016/10/02/hacktoberfest/
-[hacktoberfest-ha-prs]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
-[hacktoberfest-site-prs]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
-[hacktoberfest-website]: https://hacktoberfest.digitalocean.com/
-[logo]: /images/blog/2016-10-hacktoberfest/hacktoberfest.png
-[min]: https://home-assistant.io/components/sensor.min_max/
-[netatmo-bin]: https://home-assistant.io/components/binary_sensor.netatmo/
-[netatmo-discovery]: https://home-assistant.io/components/netatmo/
-[nmap]: https://home-assistant.io/components/device_tracker.nmap_tracker/
-[pers-notify]: https://home-assistant.io/components/persistent_notification/
-[runway]: http://runway.is
-[scrape]: https://home-assistant.io/components/sensor.scrape/
-[updater]: https://home-assistant.io/components/updater/
-[z-wave-issue]: https://github.com/home-assistant/home-assistant/pull/3759
-[zero-one-two-release]: /blog/2016/01/30/insteon-lifx-twitter-and-zigbee/#backwards-incompatible-changes
-[zero-two-seven-release]: /blog/2016/08/28/notifications-hue-fake-unification/
-[twitter]: https://twitter.com/home_assistant
-[robbie-twitter]: https://twitter.com/robbie
-[blog-orig]: https://github.com/home-assistant/home-assistant.github.io/blob/c937242d154e509d2d84d10c51f654e20556fa21/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index 9f13906a7e..7124999b68 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -97,6 +97,41 @@
+
Welcome to 2017 and 0.36. We are proud to announce the first release for this year. While we are still migrating parts to async but 0.36 is focusing on new features and a lot of bug fixes.
+
+
Packages
+
Packages are providing a new way to organize different component’s configuration parts together. With packages we offer the option to include different components or parts of configuration using any of the !include directives.
+
+
InfluxDB export
+
The InfluxDB component was causing problems in a wide variety of use cases. @titilambert improved our InfluxDB exporter feature. It might be that you need to run the migration script to update your InfluxDB database.
No, unfortunately we are not going to space. The iss sensor is tracking the position of the International Space Station and gives your some details.
+
+
Insteon local
+
The support for Insteon was removed due to issues a while ago. With the insteon_local component support for Insteon is back and let one work locally with an Insteon setup.
+
+
Image processing
+
The new image processing component currently works with number plates. But this could level the way to integrate feature like facial recognition, motion detection, or gestures control.
APNS service was moved to the notify domain. Use notify.apns_NOTIFIER_NAME instead of apns.NOTIFIER_NAME.
+
InfluxDB component has a new schema to store values in the InfluxDB database. You may require to run the influxdb_migrator script.
+You have to note:
+
+
There will not be any tags/fields named time anymore.
+
All numeric fields (int/float/bool) will be stored as float inside influx db.
+
All string fields corresponding to state attributes will be renamed as FIELDNAME_str, where FIELDNAME is the state attribute, to avoid type conflicts.
+
All string fields corresponding to a state will be renamed as state (former value).
+
Fields named value will always be stored as float.
+
Fields named state will always be stored as string.
+
+
+
+
+
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 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.
Home Assistant will join this year for Hacktoberfest, an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
I have just merged the latest version of the development branch into master. Here are some of the highlights of this release:
+
+
Configuration via the frontend
+Phliips Hue will now be auto discovered and uses the new configurator component to interact with the user to finish the setup process.
+
+
Wink Hub support
+Thanks to the work done by John McLaughlin and Geoff Norton we now support the lights, switches and sensors that are connected to the Wink hub.
+
+
The getting started guide and component page have been reorganized
+The getting started instructions have been split into separate pages per component and a general overview page. The goal is to have a page per component that describes:
+
+
+
What it does
+
How to set it up
+
Which states it maintains
+
Which services it provides
+
Additional development tips
+
+
+
More reasonable errors
+Home Assistant should now throw better errors and offer solutions if you do not have the right version of Python 3, forgot to clone the git submodules or install the dependencies.
+
+
Streamlined first launch
+Home Assistant now supports --open-ui and --demo-mode command line properties to open the browser automatically and have something to show. Home Assistant now supports to be run without a password, allowing the interface to login automatically on launch.
Home Assistant will join this year for Hacktoberfest, an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
This is a guest post by Home Assistant user and contributor Nolan Gilley.
-
-
Today I’ll show you how I used Home Assistant, a NodeMCU (ESP8266), and a couple of accelerometers to automate our laundry room. This is a rewrite of an old post where I did the same thing using a Moteino & Raspberry Pi. This version only requires a NodeMCU.
-
-
We have an older washer and dryer which doesn’t have any form of notification when cycles complete. Home Assistant was the obvious solution, I just needed to create sensors for the washer and dryer. I tried using sound sensors but found them unreliable. I ended up using an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect whether they’re open or closed. I connected the accelerometers and reed switches to an NodeMCU which will relay the data to my MQTT broker.
This is a guest post by Home Assistant user and contributor Nolan Gilley.
+
+
Today I’ll show you how I used Home Assistant, a NodeMCU (ESP8266), and a couple of accelerometers to automate our laundry room. This is a rewrite of an old post where I did the same thing using a Moteino & Raspberry Pi. This version only requires a NodeMCU.
+
+
We have an older washer and dryer which doesn’t have any form of notification when cycles complete. Home Assistant was the obvious solution, I just needed to create sensors for the washer and dryer. I tried using sound sensors but found them unreliable. I ended up using an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect whether they’re open or closed. I connected the accelerometers and reed switches to an NodeMCU which will relay the data to my MQTT broker.
It’s been already almost two weeks ago that a few of the Home Assistant developers headed towards Portland for PyCon 2016 - the conference about everything Python. We were there to learn all the nifty tricks to make our code better but most of all, to talk Home Automation.
On Monday I (Paulus) gave a presentation about Home Assistant to an audience of over 400 people! It was a bit scary at first but after a couple of minutes it went all great including some great questions afterwards. Slides can be found here and the talk is embedded right below:
-
-
-
-
-
-
One of the things that really impressed me was the amount of people that approached us to tell how they love Home Assistant, how it has replaced their previous solution, how they enjoyed contributing to Home Assistant and how helpful our community is. It makes me proud of Home Assistant and especially our community.
It’s been already almost two weeks ago that a few of the Home Assistant developers headed towards Portland for PyCon 2016 - the conference about everything Python. We were there to learn all the nifty tricks to make our code better but most of all, to talk Home Automation.
On Monday I (Paulus) gave a presentation about Home Assistant to an audience of over 400 people! It was a bit scary at first but after a couple of minutes it went all great including some great questions afterwards. Slides can be found here and the talk is embedded right below:
+
+
+
+
+
+
One of the things that really impressed me was the amount of people that approached us to tell how they love Home Assistant, how it has replaced their previous solution, how they enjoyed contributing to Home Assistant and how helpful our community is. It makes me proud of Home Assistant and especially our community.
This post is by Home Assistant contributor Greg Dowling.
-
-
In 2013 Apple introduced iBeacons: a class of Bluetooth low energy (LE) devices that broadcast their identifier to nearby devices, including most smartphones. At first glance it’s hard to imagine why they might be useful. In this two part blog I’ll try and explain why they are useful and how you can use them with Home Assistant.
-
-
The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in part 1. In part 2 I’ll talk about using iBeacons to track devices that can’t track themselves.
-
-
Using beacons to improve OwnTracks location data
-
-
When you use OwnTracks in standard major move mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
-
-
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
This post is by Home Assistant contributor Greg Dowling.
+
+
In 2013 Apple introduced iBeacons: a class of Bluetooth low energy (LE) devices that broadcast their identifier to nearby devices, including most smartphones. At first glance it’s hard to imagine why they might be useful. In this two part blog I’ll try and explain why they are useful and how you can use them with Home Assistant.
+
+
The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in part 1. In part 2 I’ll talk about using iBeacons to track devices that can’t track themselves.
+
+
Using beacons to improve OwnTracks location data
+
+
When you use OwnTracks in standard major move mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
+
+
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
Home Assistant land has been busy and a lot of people have been creating awesome stuff. We’ve added a cookbook section to the website full of examples how you can automate different things. Make sure you take a look and share your own recipes too!
-
-
Home automation demo by Part of the Thing
-
-
-
-
-
-
Haaska - Alexa Skill Adapter for Home Assistant
-
-
Haaska allows you to control lights, switches, and scenes exposed by your Home Assistant instance using an Amazon Echo. This is different from our own Alexa component because it will teach the Amazon Echo directly about the devices instead of teaching it to talk to Home Assistant. It will not allow you to use custom sentences but it will allow you to skip the ‘Ask Home Assistant’ part when giving commands:
Contributor Maddox has created a plugin for HomeBridge, an open-source HomeKit bridge. This will allow you to control your home using Siri on your Apple devices. HomeBridge has recently restructured so you’ll have to install the plugin separately with the homebridge-homeassistant npm package.
User thaijames describes in the Home Assistant forums how he has created his own NFC-based alarm system using Home Assistant, DIY components and Garfield dolls.
-
-
-
-Hold your NFC tag against the belly of Garfield to unlock the alarm.
-
Home Assistant land has been busy and a lot of people have been creating awesome stuff. We’ve added a cookbook section to the website full of examples how you can automate different things. Make sure you take a look and share your own recipes too!
+
+
Home automation demo by Part of the Thing
+
+
+
+
+
+
Haaska - Alexa Skill Adapter for Home Assistant
+
+
Haaska allows you to control lights, switches, and scenes exposed by your Home Assistant instance using an Amazon Echo. This is different from our own Alexa component because it will teach the Amazon Echo directly about the devices instead of teaching it to talk to Home Assistant. It will not allow you to use custom sentences but it will allow you to skip the ‘Ask Home Assistant’ part when giving commands:
Contributor Maddox has created a plugin for HomeBridge, an open-source HomeKit bridge. This will allow you to control your home using Siri on your Apple devices. HomeBridge has recently restructured so you’ll have to install the plugin separately with the homebridge-homeassistant npm package.
User thaijames describes in the Home Assistant forums how he has created his own NFC-based alarm system using Home Assistant, DIY components and Garfield dolls.
+
+
+
+Hold your NFC tag against the belly of Garfield to unlock the alarm.
+
+
+
+
+
+
+
@@ -700,57 +791,6 @@ Example of the new views in the frontend. Learn mor
-
-
-
-
A few weeks have past and it is time again for another release: version 0.7.4. This time we’re very glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map. The geo support consists of three different parts:
A few weeks have past and it is time again for another release: version 0.7.4. This time we’re very glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map. The geo support consists of three different parts:
Wow, almost a month has gone by since the last release and this release is packed. The biggest part of this release is probably one that you won’t notice: the frontend has been upgraded from Polymer 0.5 to the brand new released Polymer 1.0. Polymer has been declared stable by the Google overlords which will allow us to expand functionality that was waiting for this moment to arrive.
A big improvement has been brought this release by wind-rider. He took the time to revive the Chromecast support and started improving the media player integration. This triggered other people to join in resulting in a revamped media player experience and support for the Music Player Daemon.
-
-
- Example of the new media player cards
-
-
-
-To update to the latest version, run scripts/update. Please report any issues on GitHub.
-
Wow, almost a month has gone by since the last release and this release is packed. The biggest part of this release is probably one that you won’t notice: the frontend has been upgraded from Polymer 0.5 to the brand new released Polymer 1.0. Polymer has been declared stable by the Google overlords which will allow us to expand functionality that was waiting for this moment to arrive.
A big improvement has been brought this release by wind-rider. He took the time to revive the Chromecast support and started improving the media player integration. This triggered other people to join in resulting in a revamped media player experience and support for the Music Player Daemon.
+
+
+ Example of the new media player cards
+
+
+
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
+
I have just merged the latest version of the development branch into master. Here are some of the highlights of this release:
-
-
Configuration via the frontend
-Phliips Hue will now be auto discovered and uses the new configurator component to interact with the user to finish the setup process.
-
-
Wink Hub support
-Thanks to the work done by John McLaughlin and Geoff Norton we now support the lights, switches and sensors that are connected to the Wink hub.
-
-
The getting started guide and component page have been reorganized
-The getting started instructions have been split into separate pages per component and a general overview page. The goal is to have a page per component that describes:
-
-
-
What it does
-
How to set it up
-
Which states it maintains
-
Which services it provides
-
Additional development tips
-
-
-
More reasonable errors
-Home Assistant should now throw better errors and offer solutions if you do not have the right version of Python 3, forgot to clone the git submodules or install the dependencies.
-
-
Streamlined first launch
-Home Assistant now supports --open-ui and --demo-mode command line properties to open the browser automatically and have something to show. Home Assistant now supports to be run without a password, allowing the interface to login automatically on launch.
diff --git a/components/arduino/index.html b/components/arduino/index.html
index 49275ca9cf..0a0d09b889 100644
--- a/components/arduino/index.html
+++ b/components/arduino/index.html
@@ -173,6 +173,9 @@ A word of caution: The Arduino boards are not storing states. This means that wi
The bbb_gpio component is the base for all [BeagleBone Black][https://beagleboard.org/black] related GPIO platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/binary_sensor.flic/index.html b/components/binary_sensor.flic/index.html
index 98e9b2269a..9a3c9c0a4d 100644
--- a/components/binary_sensor.flic/index.html
+++ b/components/binary_sensor.flic/index.html
@@ -108,6 +108,7 @@
host (Optional): The IP or hostname of the flic service server. (default: localhost)
port (Optional): The port of the flic service. (default: 5551)
discovery (Optional): If true, the component is configured to constantly scan for new buttons. (default: true)
+
ignored_click_types: List of click types whose occurrence should not trigger and flic_click event.
timeout (Optional): Maximum time in seconds an event can be queued locally on a button before discarding the event. (default: 3)
@@ -146,6 +147,10 @@
queued_time: The amount of time this event was queued on the button, in seconds.
+
Ignoring Click Types
+
+
For some purposes it might make sense to exclude a specific click type from triggering click events. For example when ignoring double clicks, pressing the button twice fast results in two single instead of a double click event. This is very useful for applications where you want to click fast.
username (Optional): The username for accessing your camera.
password (Optional): The password for accessing your camera.
authentication (Optional): basic (default) or digest auth for requests.
-
+
There is a known issue in urllib3 that you will get error messages in your logs like [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: '' but the component still works fine. You can ignore the messages.
diff --git a/components/device_tracker.actiontec/index.html b/components/device_tracker.actiontec/index.html
index 00628b9e2f..1a62d263f5 100644
--- a/components/device_tracker.actiontec/index.html
+++ b/components/device_tracker.actiontec/index.html
@@ -207,6 +207,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 4605cd84ff..a9c0bb95e4 100644
--- a/components/device_tracker.aruba/index.html
+++ b/components/device_tracker.aruba/index.html
@@ -210,6 +210,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 901114aeaa..c82d45facd 100644
--- a/components/device_tracker.bbox/index.html
+++ b/components/device_tracker.bbox/index.html
@@ -205,6 +205,9 @@ For now and due to third party limitation, the Bbox must be on the same local ne
diff --git a/components/device_tracker.bluetooth_le_tracker/index.html b/components/device_tracker.bluetooth_le_tracker/index.html
index ad22493259..0fca534fdc 100644
--- a/components/device_tracker.bluetooth_le_tracker/index.html
+++ b/components/device_tracker.bluetooth_le_tracker/index.html
@@ -109,6 +109,12 @@ Requires gattlib, which is not compatible with Windows. This tracker won’t wor
+
Configuration variables:
+
+
+
device_id (Optional): The device ID for the bluetooth device to be used for tracking. Defaults to hci0.
+
+
As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times.
Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won’t see this device.
@@ -222,6 +228,9 @@ BT LE tracking requires root privileges.
diff --git a/components/device_tracker.cisco_ios/index.html b/components/device_tracker.cisco_ios/index.html
index bd9f3823e1..9c5302d8c2 100644
--- a/components/device_tracker.cisco_ios/index.html
+++ b/components/device_tracker.cisco_ios/index.html
@@ -232,6 +232,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 cc00d71ca1..7ae78c3441 100644
--- a/components/device_tracker.fritz/index.html
+++ b/components/device_tracker.fritz/index.html
@@ -205,6 +205,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 7352994acf..2045967911 100644
--- a/components/device_tracker.icloud/index.html
+++ b/components/device_tracker.icloud/index.html
@@ -220,6 +220,9 @@ You may receive an email from Apple stating that someone has logged into your ac
diff --git a/components/device_tracker.luci/index.html b/components/device_tracker.luci/index.html
index cbcb6ad64f..237eeece39 100644
--- a/components/device_tracker.luci/index.html
+++ b/components/device_tracker.luci/index.html
@@ -212,6 +212,9 @@ Some installations have a s
The ping platform offers presence detection by using ping to send ICMP echo requests. This can be useful when devices are running a firewall and are blocking UDP or TCP packets but responding to ICMP requests (like Android phones). This tracker doesn’t need to know the MAC address since the host can be on a different subnet. This makes this an option to detect hosts on a different subnet when nmap or other solutions don’t work since arp doesn’t work.
+
+
To use this presence detection in your installation, add the following to your configuration.yaml file:
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/device_tracker.snmp/index.html b/components/device_tracker.snmp/index.html
index 8c091cc82d..7036c9970b 100644
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@@ -239,6 +239,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 69ded1f704..844b5e3907 100644
--- a/components/device_tracker.swisscom/index.html
+++ b/components/device_tracker.swisscom/index.html
@@ -193,6 +193,9 @@ There are three models of Internet-Box (light, standard and plus). The platform
diff --git a/components/device_tracker.tplink/index.html b/components/device_tracker.tplink/index.html
index eca8827bdd..3364e48951 100644
--- a/components/device_tracker.tplink/index.html
+++ b/components/device_tracker.tplink/index.html
@@ -220,6 +220,9 @@ TP-Link devices typically only allow one login at a time to the admin console.
The upc_connect platform offers presence detection by looking at connected devices to an ConnectBox router from Liberty Global, which is a Internet provider in Switzerland, Austria.
+
+
To use an Internet-Box router in your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+device_tracker:
+ platform:upc_connect
+ password:'123456'
+ host:"192.168.0.1"# only required if not 192.168.0.1
+
diff --git a/components/emulated_hue/index.html b/components/emulated_hue/index.html
index 5e307a3b09..b5d7bf6367 100644
--- a/components/emulated_hue/index.html
+++ b/components/emulated_hue/index.html
@@ -248,6 +248,9 @@ The virtual bridge has the ability to turn entities on or off, or change the bri
diff --git a/components/fan.mqtt/index.html b/components/fan.mqtt/index.html
index ed249555d4..dc75549ca9 100644
--- a/components/fan.mqtt/index.html
+++ b/components/fan.mqtt/index.html
@@ -244,6 +244,9 @@ Make sure that your topic is an exact match. som
diff --git a/components/fan.nest/index.html b/components/fan.nest/index.html
index c835763371..61c32325fb 100644
--- a/components/fan.nest/index.html
+++ b/components/fan.nest/index.html
@@ -163,6 +163,9 @@ You must have the Nest component configured to u
diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html
index 6bf739475f..978b166ab8 100644
--- a/components/ffmpeg/index.html
+++ b/components/ffmpeg/index.html
@@ -195,6 +195,9 @@ You need the ffmpeg binary in your system
The http component serves all files and data required for the Home Assistant frontend. You only need to add this to your configuration file if you want to change any of the default settings.
-
-
-It’s HIGHLY recommended that you set the api_password, especially if you are planning to expose your installation to the internet.
-
+
This offers the official frontend to control Home Assistant.
# Example configuration.yaml entryfrontend:
@@ -102,7 +98,6 @@ It’s HIGHLY recommended that you set the api_p
diff --git a/components/homematic/index.html b/components/homematic/index.html
index 4096d5ab48..36e1f8ba40 100644
--- a/components/homematic/index.html
+++ b/components/homematic/index.html
@@ -354,6 +354,9 @@ Using this service provides you direct access to the setValue-method of the prim
diff --git a/components/ifttt/index.html b/components/ifttt/index.html
index d6042bfa32..34db1bd6f1 100644
--- a/components/ifttt/index.html
+++ b/components/ifttt/index.html
@@ -270,7 +270,7 @@ You need to setup a unique trigger for each event you sent to IFTTT.
LIRC
OpenALPR integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other automation.
OpenALPR integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other automation.
+
+
Local installation
+
+
If you want process all data locally, you need version 2.3.1 or higher of the alpr commandline tool.
+
+
If you don’t find binaries for your distribution you can compile from source. Documention of how to build openalpr is found here.
+
+
On a Debian system you can use this cmake command to build only the command line tool:
The following event attributes will be present: entity_id, plate, confidence
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/index.html b/components/index.html
index 39322cbede..e104d6acbd 100644
--- a/components/index.html
+++ b/components/index.html
@@ -111,11 +111,11 @@ Support for these components is provided by the Home Assistant community.
diff --git a/components/insteon_hub/index.html b/components/insteon_hub/index.html
index d9aa1162d7..96bdbf3b27 100644
--- a/components/insteon_hub/index.html
+++ b/components/insteon_hub/index.html
@@ -173,6 +173,9 @@ This component has been disabled due to a complaint by Insteon. It will be enabl
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/isy994/index.html b/components/isy994/index.html
index 55160da0c5..04ae7bb6cd 100644
--- a/components/isy994/index.html
+++ b/components/isy994/index.html
@@ -280,6 +280,9 @@ The ISY994 controller is manufactured by MagicLight® Plus - WiFi Smart LED Light Bulb4
Some devices such as the Ledenet RGBW controller use a slightly difference protocol for communicating the brightness to each color channel. If your device is only turning on or off but not changing color or brightness try adding the LEDENET protocol.
diff --git a/components/light.hue/index.html b/components/light.hue/index.html
index c515e137ed..cb62fbb79c 100644
--- a/components/light.hue/index.html
+++ b/components/light.hue/index.html
@@ -229,6 +229,9 @@ Name. Use the values of Room name and Scene name that you see in the app. You ca
diff --git a/components/light.mqtt_template/index.html b/components/light.mqtt_template/index.html
index c48a0c029e..47bab1d621 100644
--- a/components/light.mqtt_template/index.html
+++ b/components/light.mqtt_template/index.html
@@ -245,6 +245,9 @@ It is format-agnostic so you can use any data format you want (i.e. string, JSON
devices: A list of devices with their bluetooth address, a custom name to use in the frontend and the bulb-specific password. The password can be obtained from an Android device using an app like aLogcat or the adb logcat command for phones in developer mode. Look for a line like:
+
+
+
E LedoBleSDK: login =skName=======[Smart Light]=======skPw==[password]
+
+
+
+
The password is the text between the square brackets following skPw.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/light.vera/index.html b/components/light.vera/index.html
index 4216d0e034..11f6f6c888 100644
--- a/components/light.vera/index.html
+++ b/components/light.vera/index.html
@@ -173,6 +173,9 @@
diff --git a/components/light.yeelight/index.html b/components/light.yeelight/index.html
index 93e65076ef..c062bc5448 100644
--- a/components/light.yeelight/index.html
+++ b/components/light.yeelight/index.html
@@ -170,6 +170,9 @@ Tests are only made with a YLDP03YL model. Because it’s the only hardware deve
username (Optional): The username of the Samsung Smart TV. Defaults to admin.
password (Optional): The password of the Samsung Smart TV. Defaults to password.
name (Optional): The name you would like to give to the Sharp Aquos TV.
+
power_on_enabled (Optional): If you want to be able to turn on your TV. Defaults to False.
+
+When you set power_on_enabled as True, you have to turn on your TV on the first time with the remote.
+Then you will be able to turn on with Home-Assistant.
+Also, with power_on_enabled as True, the Aquos logo on your TV will stay on when you turn off the TV and your TV could consumes more power.
+
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index e796810d05..4a41c00371 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -229,6 +229,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 a84d3cb33d..c4ee298877 100644
--- a/components/media_player.lg_netcast/index.html
+++ b/components/media_player.lg_netcast/index.html
@@ -186,6 +186,9 @@ The access token will not change until you factory reset your TV.
diff --git a/components/media_player.mpchc/index.html b/components/media_player.mpchc/index.html
index 6181113b9d..e9e00aed6a 100644
--- a/components/media_player.mpchc/index.html
+++ b/components/media_player.mpchc/index.html
@@ -189,6 +189,9 @@ The MPC-HC web interface is highly insecure, and allows remote clients full play
serial_port (Required): The serial port . Default is /dev/ttyUSB0
+
name (Optional): Name of the device. Default is NAD Receiver.
+
min_volume (optional): Minimum volume in dB to use with the slider. Default is -92
+
max_volume (optional): Maximum volume in dB to use with the slider. Default is -20
+
sources (Optional): A list of mappings from source to source name. Valid sources are 1 to 10.
+
+
+
The min_volume and max_volume are there to protect you against misclicks on the slider so you will not blow up your speakers when you go from -92dB to +20dB.
+You can still force it to go higher or lower than the values set with the plus and minus buttons.
+
+
+On linux the user running home-assistant needs dialout permissions to access the serial port.
+This can be added to the user by doing sudo usermod -a -G dialout <username>.
+Be aware that the user might need to logout and logon again to activate these permissions.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/media_player.onkyo/index.html b/components/media_player.onkyo/index.html
index d2709c9f7a..8be70fcabb 100644
--- a/components/media_player.onkyo/index.html
+++ b/components/media_player.onkyo/index.html
@@ -211,6 +211,9 @@
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index 296cb3a0d6..ddcad35568 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -211,6 +211,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 a9a34e57f6..9401e52f77 100644
--- a/components/media_player.soundtouch/index.html
+++ b/components/media_player.soundtouch/index.html
@@ -308,6 +308,9 @@ create a new zone in order to be able to add slave(s) again
arguments (Optional): Additional arguments to be passed to VLC.
+
Only “music” media type is supported for now.
+
+
This service will control a background VLC instance, therefore you cannot use this to control a VLC instance launched on your desktop, unlike the Kodi media player for example.
+
+
Full configuration
+
+
A full configuration for VLC could llok like the one below:
diff --git a/components/media_player.webostv/index.html b/components/media_player.webostv/index.html
index e15c6d0326..8f291f3dba 100644
--- a/components/media_player.webostv/index.html
+++ b/components/media_player.webostv/index.html
@@ -210,6 +210,9 @@ Home Assistant is able to turn on a LG webOS Smart TV if you specify its MAC add
diff --git a/components/mqtt/index.html b/components/mqtt/index.html
index c29ca9eaa2..af8c8cc900 100644
--- a/components/mqtt/index.html
+++ b/components/mqtt/index.html
@@ -501,6 +501,9 @@ Home Assistant will automatically load the correct certificate if you connect to
diff --git a/components/mysensors/index.html b/components/mysensors/index.html
index 85c2ebc3f1..b3a6df95e4 100644
--- a/components/mysensors/index.html
+++ b/components/mysensors/index.html
@@ -296,6 +296,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 6b52646592..e8308f6cb2 100644
--- a/components/neato/index.html
+++ b/components/neato/index.html
@@ -172,6 +172,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 ee8f8cba56..583d3c030a 100644
--- a/components/netatmo/index.html
+++ b/components/netatmo/index.html
@@ -203,6 +203,9 @@ The Home Assistant Netatmo platform has only be tested with the classic indoor,
name (Required): The name of the notifier. The notifier will bind to the service notify.NOTIFIER_NAME.
-
sandbox (Optional): If true notifications will be sent to the sandbox (test) notification service. Default false.
cert_file (Required): The certificate to use to authenticate with the APNS service.
+
topic (Required): The app bundle ID specified in the certificate.
+
sandbox (Optional): If true notifications will be sent to the sandbox (test) notification service. Default false.
-
The APNS platform will register two services, notify.NOTIFIER_NAME and apns.NOTIFIER_NAME.
+
The APNS platform will register two services, notify.NOTIFIER_NAME and notify.apns_NOTIFIER_NAME.
-
apns.NOTIFIER_NAME
+
notify.apns_NOTIFIER_NAME
This service will register device id’s with home assistant. In order to receive a notification a device must be registered. The app on the device can use this service to send an ID to Home Assistant during startup, the ID will be stored in [NOTIFIER_NAME]_apns.yaml.
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index 946186ea82..510a87ab23 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -190,6 +190,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
The lannouncer notification platform allows you to play spoken messages (TTS) or sounds on an Android device running Lannouncer. This can be useful when you have a wall mounted Android tablet, or an Android device that is permanently powered and turned on and want to use that to play notifications.
+
+
To enable Lannouncer notifications in your installation, add the following to your configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
host (Required): The hostname or IP-address of the Android device that is running Lannouncer.
+
port (Optional): The port on which Lannouncer is running. By default this is 1035.
+
+
+
Installation
+
+
You need to install the Lannouncer app and enable the Network (TCP) Listener and Auto-Start Network Listener. You can disable the GCM (Google Cloud) and WAN Messaging and SMS Listener since this component doesn’t use them.
+
+
Lannouncer uses the default Android TTS voice. You can tweak that in the Android configuration, or you can install a different TTS engine from the Play Store. You might want to raise the volume in the app settings since that depends on the actual hardware device.
Spoken messages is the default method (speak). You just invoke the notify service with the following json and the device will speak out the specified message.
+
+
{
+ "message":"I'm sorry, I cannot do that Dave."
+}
+
+
+
+
The second method is to play notifications (alarm). There are 4 build-in sounds (chime, doorbell, alarm and siren).
You can also request to play a configured additional soundfiles (FILE1, FILE2, FILE3, FILE4 or FILE5). You can configure this file in the app settings.
Integrates MySensors notifications into Home Assistant. See the main component for configuration instructions.
+
+
Setting the target key in the service call will target the name of the MySensors device in Home Assistant. MySensors device names follow the notation: “[Sketch name] [Node id] [Child id]”.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/notify.nfandroidtv/index.html b/components/notify.nfandroidtv/index.html
index ebc47b987d..89d13016e9 100644
--- a/components/notify.nfandroidtv/index.html
+++ b/components/notify.nfandroidtv/index.html
@@ -201,6 +201,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 c5e9d83f60..ad9b81e688 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -235,6 +235,9 @@ which need special attention. By default, the usage by external applications, es
OpenAlpr integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other automation.
+
OpenALPR integration for Home Assistant allows you to process licences plates recorded with a camera. You can use them to open a garage door or trigger any other automation.
If you want use a video stream. You need setup the ffmpeg component. See also there for troubleshooting local ffmpeg installation.
@@ -98,17 +98,19 @@ If you want use a video stream. You need setup the
Local installation
-
If you want process all data local you need the command line tool alpr in version > 2.3.1
+
If you want process all data locally, you need version 2.3.1 or higher of the alpr commandline tool.
-
If you don’t find binaries for your distribution you can compile from source. Documention of how to build openalpr is found here.
+
If you don’t find binaries for your distribution you can compile from source. Documention of how to build OpenALPR is found here.
-
On a debian system you can use this cmake command to build only the command line tool (which second part on linux build instruction - ubuntu 14.04+):
@@ -133,20 +135,21 @@ If you want use a video stream. You need setup the password:bla
+
Configuration variables:
engine (Required): local or cloud for processing
-
region (Required): Country or region. List of Supported value.
-
confidence (Optional): Default 80. The minimum of confidence in percent to process with Home-Assistant.
-
entities (Required): A list of device to add in Home-Assistant.
-
name (Optional): This parameter allows you to override the name of your openalpr entity.
-
interval (Optional): Default 2. Time in seconds to poll a picture. If the interval is 0 It don’t poll and it only process data with openalpr.scan service.
-
render (Optional): default is with ffmpeg. How is Home-Assistant to get a picture from. It support ffmpeg for video streams and image for a still image.
-
input (Required): The source from getting pictures. With ffmpeg it could by all supported input. Image only support a url.
-
extra_arguments (Optional): Only available with ffmpeg.
-
username (Optional): Only available with image for http authentification.
-
password (Optional): Only available with image for http authentification.
+
region (Required): Country or region. List of supported values.
+
confidence (Optional): The minimum of confidence in percent to process with Home Assistant. Defaults to 80.
+
entities (Required): A list of device to add in Home Assistant.
+
name (Optional): This parameter allows you to override the name of your OpenALPR entity.
+
interval (Optional): Time in seconds to poll a picture. If the interval is 0 It don’t poll and it only process data with openalpr.scan service. Default is 2 seconds.
+
render (Optional): How is Home Assistant to get a picture from. It support ffmpeg for video streams and image for a still image. Default is with ffmpeg.
+
input (Required): The source from getting pictures. With ffmpeg it could by all supported input. Image only support an URL.
+
extra_arguments (Optional): Only available with ffmpeg.
+
username (Optional): Only available with image for HTTP authentification.
+
password (Optional): Only available with image for HTTP authentification.
Configuration Home Assistant local processing
@@ -163,7 +166,7 @@ If you want use a video stream. You need setup the
purge_days (Optional): Delete events and states older than x days.
+
exclude (Optional): Configure which components should be excluded from recordings.
+
+
entities (Optional): The list of entity ids to be excluded from recordings.
+
domains (Optional): The list of domains to be excluded from recordings.
+
+
+
include (Optional): Configure which components should be included in recordings. If set, all other entities will not be recorded.
+
+
entities (Optional): The list of entity ids to be included from the history.
+
domains (Optional): The list of domains to be included from the history.
+
+
db_url (Optional): The URL which point to your database.
-
# Example configuration.yaml entry
+
Define domains and entities to exclude (aka. blacklist). This is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like weblink) or rarely change (updater or automation).
+
+
# Example configuration.yaml entry with excluderecorder:purge_days:5db_url:sqlite:///home/user/.homeassistant/test
+ exclude:
+ domains:
+ -automation
+ -weblink
+ -updater
+ entities:
+ -sun.sun# Don't record sun data
+ -sensor.last_boot
+ -sensor.date
+
Define domains and entities to record by using the include configuration (aka. whitelist). If you have a lot of entities in your system and your exclude lists possibly get very large, it might be better just to define the entities or domains to record.
+
+
# Example configuration.yaml entry with include
+history:
+ include:
+ domains:
+ -sensor
+ -switch
+ -media_player
+
+
+
+
Use the include list to define the domains/entities to record, and exclude some of them with in the exclude list. This makes sense if you for instance include the sensor domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the includeentities list just include the sensor domain and exclude the sensor entities you are not interested in.
+
+
# Example configuration.yaml entry with include and exclude
+history:
+ include:
+ domains:
+ -sensor
+ -switch
+ -media_player
+ exclude:
+ entities:
+ -sensor.last_boot
+ -sensor.date
+
+
+
+
If you only want to hide events from e.g. your history, take a look at the history component. Same goes for logbook. But if you have privacy concerns about certain events or neither want them in history or logbook, you should use the exclude/include options of the recorder component, that they aren’t even in your database. That way you can save storage and keep the database small by excluding certain often-logged events (like sensor.last_boot).
+Please note that the scene component currently only supports one service call per entity to achieve the state. Due to this limitation you cannot set states belonging to different services.
+
diff --git a/components/sensor.bbox/index.html b/components/sensor.bbox/index.html
index bc938e029b..ff1f43a73e 100644
--- a/components/sensor.bbox/index.html
+++ b/components/sensor.bbox/index.html
@@ -210,6 +210,9 @@ Due to third party limitation, the sensors will only be available if Home Assist
Each sensor will be given the device_id of “bom [optionalname] friendlyname units”
A name is optional but if multiple BOM weather stations are used a name will be required.
-
The sensor will update every minute 35 minutes after last data timestamp. This allows for the 30 minute observation cycle and the approximate 5 minute update delay in publishing the data.
-
-
-
To get the station ID [zone_id] and [wmo_id] for your local BOM station:
update_interval (Optional): Default 300. Time in seconds to fetch data from sensors
host (Required): The hostname/IP address to connect to.
mac (Required): Device mac address.
-
timeout (Optional): Timeout in seconds for the connection to the device
+
name (Optional): Default BL. Sensor name
+
update_interval (Optional): Time in seconds to fetch data from sensors. Default 300.
+
timeout (Optional): Timeout in seconds for the connection to the device.
monitored_conditions array (Required): States to monitor.
‘temperature’
@@ -114,8 +126,9 @@ There is currently no support for the cloud API.
To set it up, add the following information to your configuration.yaml file:
Obtain sensor data from an A1:
+
sensor:
- platform:broadlink
+ -platform:broadlinkupdate_interval:60host:IP_ADDRESSmac:'MAC_ADDRESS'
@@ -129,8 +142,9 @@ There is currently no support for the cloud API.
Obtain temperature data from an RM2:
+
sensor:
- platform:broadlink
+ -platform:broadlinkupdate_interval:60host:IP_ADDRESSmac:'MAC_ADDRESS'
@@ -139,6 +153,20 @@ There is currently no support for the cloud API.
+
Microsoft Windows installation
+
+
+The pycrypto library needs to be available on your platform. On a typical windows sysytem pip install pycrypto will fail, as a compiler needs to be installed first.
+
+
+
The quickest way around this is to use a pre-built binary, e.g. from https://github.com/sfbahr/PyCrypto-Wheels
+
+
Be sure to get the correct 64 or 32-bit binary for your system, the full commandline will look something like the sample below for a 64-bit system:
diff --git a/components/sensor.darksky/index.html b/components/sensor.darksky/index.html
index 88bdaf1f93..9d7b345e5c 100644
--- a/components/sensor.darksky/index.html
+++ b/components/sensor.darksky/index.html
@@ -215,6 +215,9 @@ Note: While the platform is called “darksky” the sensors will show up in Hom
diff --git a/components/sensor.efergy/index.html b/components/sensor.efergy/index.html
index 36049ba146..4b670cac6f 100644
--- a/components/sensor.efergy/index.html
+++ b/components/sensor.efergy/index.html
@@ -183,6 +183,9 @@ negative number of minutes your timezone is ahead/behind UTC time.
diff --git a/components/sensor.fastdotcom/index.html b/components/sensor.fastdotcom/index.html
index 0af6c3284e..b67947adfd 100644
--- a/components/sensor.fastdotcom/index.html
+++ b/components/sensor.fastdotcom/index.html
@@ -124,9 +124,10 @@ Currently fast.com only supports measuring download bandwidth. If you want to me
minute (Optional): Specify the minute(s) of the hour to schedule the speedtest. Use a list for multiple entries. Default is 0.
hour (Optional): Specify the hour(s) of the day to schedule the speedtest. Use a list for multiple entries. Default is None.
day (Optional): Specify the day(s) of the month to schedule the speedtest. Use a list for multiple entries. Default is None.
+
manual (Optional): True or False to turn manual mode on or off. Manual mode will disable scheduled speedtests.
-
There is also a service named sensor.update_fastdotcom that you can use to run a fast.com speedtest on demand.
+
There is also a service named sensor.update_fastdotcom that you can use to run a fast.com speedtest on demand. You can turn on manual mode to disable the scheduled speedtests.
diff --git a/components/sensor.haveibeenpwned/index.html b/components/sensor.haveibeenpwned/index.html
index d28d507017..a7e168235b 100644
--- a/components/sensor.haveibeenpwned/index.html
+++ b/components/sensor.haveibeenpwned/index.html
@@ -204,6 +204,9 @@ account has been breached as well as the added date of the breach data. This dat
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index 9f2dbb3766..0a6458051a 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -225,6 +225,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
The iss platform uses the Open Notify API to let you know if the station is above your home location. This means that ISS is 10° above the horizon of your home.
+You can check in the attributes of the sensor how many minutes you have to wait until the next rise of the station and the number of people in space.
+
+
To add ISS sensor to your installation, add the following to your configuration.yaml file:
+
+
# Example configuration.yaml entry
+sensor:
+ -platform:iss
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.isy994/index.html b/components/sensor.isy994/index.html
index aadbf6bf52..a196258ea6 100644
--- a/components/sensor.isy994/index.html
+++ b/components/sensor.isy994/index.html
@@ -199,6 +199,9 @@
@@ -128,9 +128,9 @@ Reducing polling intervals will have a negative effect on the battery life.
A full configuration example could looks the one below:
# Example configuration.yaml entry
-sensor
- - platform:miflora
- mac:xx:xx:xx:xx:xx:xx
+sensor:
+ -platform:miflora
+ mac:"xx:xx:xx:xx:xx:xx"name:Flower 1force_update:falsemedian:3
@@ -178,6 +178,9 @@ Reducing polling intervals will have a negative effect on the battery life.
diff --git a/components/sensor.moldindicator/index.html b/components/sensor.moldindicator/index.html
index d87cba6f3e..f6075eec73 100644
--- a/components/sensor.moldindicator/index.html
+++ b/components/sensor.moldindicator/index.html
@@ -206,6 +206,9 @@ 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 93f3600641..47653ccfe6 100644
--- a/components/sensor.mqtt_room/index.html
+++ b/components/sensor.mqtt_room/index.html
@@ -221,6 +221,9 @@ Instead of developing your own application, you can also use any of these alread
diff --git a/components/sensor.nest/index.html b/components/sensor.nest/index.html
index 7ecb28034c..651f9c0439 100644
--- a/components/sensor.nest/index.html
+++ b/components/sensor.nest/index.html
@@ -124,6 +124,7 @@ You must have the Nest component configured to u
operation_mode
temperature
target
+
hvac_state: The currently active state of the HVAC system, heating, cooling, or off.
Nest Protect:
@@ -235,6 +236,9 @@ 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 9fb9c63c1e..836d74de2f 100644
--- a/components/sensor.nest_weather/index.html
+++ b/components/sensor.nest_weather/index.html
@@ -149,6 +149,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 8bc022ff8d..c630a8da16 100644
--- a/components/sensor.octoprint/index.html
+++ b/components/sensor.octoprint/index.html
@@ -212,6 +212,9 @@ You must have the OctoPrint component confi
diff --git a/components/sensor.rfxtrx/index.html b/components/sensor.rfxtrx/index.html
index 3de680ddd1..d5abd0e3b6 100644
--- a/components/sensor.rfxtrx/index.html
+++ b/components/sensor.rfxtrx/index.html
@@ -268,6 +268,9 @@ Then you should update your configuration to (_temperature is not needed):
The sma sensor will poll a [SMA][http://www.sma-america.com/] solar inverter and present the values as sensors (or attributes of sensors) in Home Assistant.
+
+
To enable this sensor, add the following lines to your configuration.yaml file:
The SMA WebConnect module supports a wide variety of sensors, and not all these have been mapped to standard sensors. Custom sensors can be defined by using the custom section of the configuration. You will need: A sensor name (no spaces), the SMA sensor key and the unit
minute (Optional): Specify the minute(s) of the hour to schedule the speedtest. Use a list for multiple entries. Default is 0.
hour (Optional): Specify the hour(s) of the day to schedule the speedtest. Use a list for multiple entries. Default is None.
day (Optional): Specify the day(s) of the month to schedule the speedtest. Use a list for multiple entries. Default is None.
+
manual (Optional): True or False to turn manual mode on or off. Manual mode will disable scheduled speedtests.
This component uses speedtest-cli to gather network performance data from Speedtest.net. Please be aware of the potential inconsistencies that this component may display.
-
When Home Assistant first starts up, the values of the speedtest will show as Unknown. You can use the service sensor.update_speedtest to run a manual speedtest and populate the data or just wait for the next regularly scheduled test.
+
When Home Assistant first starts up, the values of the speedtest will show as Unknown. You can use the service sensor.update_speedtest to run a manual speedtest and populate the data or just wait for the next regularly scheduled test. You can turn on manual mode to disable the scheduled speedtests.
diff --git a/components/sensor.synologydsm/index.html b/components/sensor.synologydsm/index.html
index e3d7ab0a3e..731794ac3b 100644
--- a/components/sensor.synologydsm/index.html
+++ b/components/sensor.synologydsm/index.html
@@ -248,6 +248,9 @@ 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 0aa64f2e21..4c08383872 100644
--- a/components/sensor.temper/index.html
+++ b/components/sensor.temper/index.html
@@ -194,6 +194,9 @@ The calculation follows the formula scale * sens
diff --git a/components/sensor.template/index.html b/components/sensor.template/index.html
index ef126bd891..a86718b041 100644
--- a/components/sensor.template/index.html
+++ b/components/sensor.template/index.html
@@ -311,6 +311,9 @@ Please note the blank line to close the multi-line template.
diff --git a/components/sensor.wunderground/index.html b/components/sensor.wunderground/index.html
index f2adca5c89..ae12f0b1f2 100644
--- a/components/sensor.wunderground/index.html
+++ b/components/sensor.wunderground/index.html
@@ -226,6 +226,9 @@ Obtain a WUnderground API key Bureau of Meteorology (BOM) Australia
+
diff --git a/components/sensor.yr/index.html b/components/sensor.yr/index.html
index 4ba2c2244f..b9b78f3f15 100644
--- a/components/sensor.yr/index.html
+++ b/components/sensor.yr/index.html
@@ -170,6 +170,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 a99e02f272..67a49a5571 100644
--- a/components/sensor.yweather/index.html
+++ b/components/sensor.yweather/index.html
@@ -165,6 +165,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 f8ea4ad4a1..d0fff97037 100644
--- a/components/sensor.zoneminder/index.html
+++ b/components/sensor.zoneminder/index.html
@@ -201,6 +201,9 @@ You must have the ZoneMinder component con
switches (Optional): The array that contains all switches.
identifier (Required): Name of the command switch as slug. Multiple entries are possible.
@@ -128,9 +131,10 @@
Choose Call Service from the Developer Tools. Choose the service broadlink/learn_command from the list of Available services: and hit CALL SERVICE. Press the button on your remote with in 20 seconds. The packet will be printed in the log and as a persistent notification.
-
Example config:
+
Example config for rm, rm2, rm_mini, rm_pro_phicomm, rm2_home_plus, rm2_home_plus_gdt, rm2_pro_plus, rm2_pro_plus2, rm2_pro_plus_bl and rm_mini_shate devices:
-
-platform:broadlink
+
switch 2:
+ platform:broadlinkhost:192.168.1.2mac:'B4:43:0D:CC:0F:58'timeout:15
@@ -159,6 +163,38 @@
friendly_name:"LGTv"command_on:'JgBIAAABIpQPFBITETgSEw8UEhQSEhEVDzgSOBAUETgQOQ84EjgRNxITETgSExA5EDgREhI3EhMROBMSEDkQFBETEjYTEhE4EQANBQ=='command_off:'JgBIAAABH5YPFBETETgUERAUEBURFBATETgROBEUETcSNxE4ETcSOBISEBUQFREUEjUSFBA5ETcRNxE4ETkQOBAUEjcRFRAUEQANBQ=='
+
+
+switch 2:
+ platform:broadlink
+ host:192.168.1.2
+ mac:'B4:43:0D:CC:0F:58'
+ timeout:15
+# Will work on most Phillips tvs:
+ tv:
+ friendly_name:"PhillipsTv"
+ command_on:'JgAcAB0dHB44HhweGx4cHR06HB0cHhwdHB8bHhwADQUAAAAAAAAAAAAAAAA='
+
+
+
+
+
+
Example config for sp1, sp2, honeywell_sp2, sp3, spmini2 and spminiplus devices:
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index 19740464dd..b4239725ce 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -253,6 +253,9 @@ This switch will shutdown your host immediately, there will be no confirmation.
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index 84f49df8e5..7f877eedd7 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -155,6 +155,9 @@ Currently works using default https port only.
The kankun switch platform allows you to toggle customised Kankun SP3 wifi switches. Switches are
+modified to include the json.cgi
+script to provide a HTTP API. Details of the necessary modifications can be found
+here (be sure to install the JSON version
+of the script as linked above).
+
+
To enable it, add the following lines to your configuration.yaml:
switches (Required): The array that contains all Kankun switches.
+
+
identifier (Required): Name of the Kankun switch as slug. Multiple entries are possible.
+
+
host (Required): Hostname or IP address of the switch on the local network.
+
name (Optional): Friendly name of the switch.
+
port (Optional): HTTP connection port, defaults to 80.
+
path (Optional): Path of CGI script, defaults to /cgi-bin/json.cgi.
+
username (Optional): Username for basic authentication.
+
password (Optional): Password for basic authentication.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/switch.knx/index.html b/components/switch.knx/index.html
index c8099e12b5..98b9e75f34 100644
--- a/components/switch.knx/index.html
+++ b/components/switch.knx/index.html
@@ -165,6 +165,9 @@ For switching actuators that are only controlled by a single group address and c
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 6e0afeca14..d445c5d9dc 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -223,6 +223,9 @@ Make sure that your topic match exact. some-topi
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 33d0f9d172..4d2d7fc4fa 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -158,6 +158,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 4605463e18..55a3da9cfc 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -162,6 +162,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/switch.rfxtrx/index.html b/components/switch.rfxtrx/index.html
index ba1a8dd6e5..fef40f8730 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -285,6 +285,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 3ec1323b18..8148231d6b 100644
--- a/components/switch.rpi_rf/index.html
+++ b/components/switch.rpi_rf/index.html
@@ -113,6 +113,7 @@ For more info see the PyPi module description: protocol:5code_on:654321code_off:654320
+ signal_repetitions:15
@@ -128,6 +129,7 @@ For more info see the PyPi module description: 1).
pulselength (Optional): Pulselength (Default is the protocol default).
+
signal_repetitions (Optional): Number of times to repeat transmission (default is 10, can increase to try to improve reliability).
@@ -135,7 +137,6 @@ For more info see the PyPi module description: Acer Projector Switch
+
The picotts text-to-speech platform uses offline pico Text-to-Speech engine to read a text with natural sounding voices.
+This requires to install the pico tts library on the system, typically on debian just do sudo apt-get install libttspico-utils
+On some raspbian release, this package is missing but you can just copy the arm deb package from debian.
+
+
To enable text-to-speech with Pico, add the following lines to your configuration.yaml:
+
+
# Example configuration.yaml entry
+tts:
+ -platform:picotts
+
+
+
+
Configuration variables:
+
+
+
language (Optional): The language to use. Defaults to en-US.
+Supported languages : ‘en-US’, ‘en-GB’, ‘de-DE’, ‘es-ES’, ‘fr-FR’, ‘it-IT’
+
+
+
A full configuration sample:
+
+
# Example configuration.yaml entry
+tts:
+ -platform:picotts
+ language:'fr-FR'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/tts.voicerss/index.html b/components/tts.voicerss/index.html
index 90c96cf3b6..616dd6d81c 100644
--- a/components/tts.voicerss/index.html
+++ b/components/tts.voicerss/index.html
@@ -153,9 +153,15 @@
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/tts/index.html b/components/tts/index.html
index 0f5dc7a262..3afc228c4b 100644
--- a/components/tts/index.html
+++ b/components/tts/index.html
@@ -211,9 +211,15 @@ If you are running Home Assistant over SSL or from within a container, you will
Control My Christmas Tree Stats
January 3, 2017
@@ -151,11 +156,6 @@ Home Assistant is an open-source home automation platform running on Python 3. T
December 19, 2016
Packages in Home Assistant provides a way to bundle different component’s configuration together. We were already introduced to the two configuration styles (specifying platforms entries together or individually) on the adding devices page. Both of these configuration methods require you to create the component key in the main configuration.yaml file. With packages we have a way to include different components, or parts of configuration using any of the !include directives introduced in splitting the configuration.
+
+
Packages are configured under the core homeassistant/packages in the configuration and take the format of a packages name (no spaces, all lower case) followed by a dictionary with the package config. For example, package pack_1 would be created as:
There are some rules for packages that will be merged:
+
+
+
Component names may only use the basic form (e.g. switch and switch 1 or switch aa is not accepted).
+
Platform based components (light, switch, etc) can always be merged.
+
+
Components where entities are identified by a key that will represent the entity_id ({key:config}) need to have unique ‘keys’ between packages and the main configuration file.
+
+
For example if we have the following in the main config. You are not allowed to re-use “my_input” again for input_boolean in a package:
+
+
yaml
+ input_boolean:
+ my_input:
+
+
+
Any component that is not a platform [2], or dictionaries with Entity ID keys [3] cannot be merged and can only occur once between all packages and the main configuration.
+
+
+
+Components inside packages can only specify platform entries using configuration style 1, where all the platforms are grouped under the component name.
+
+
+
Create a packages folder
+
+
One way to organise packages would be to create a folder named “packages” in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your configuration.yaml will load all packages:
This uses the concept splitting the configuration and will include all files in a directory with the keys representing the filenames.
+See the documentation about splitting the configuration for more information about !include_dir_named and other include statements that might be helpful.