From 984edefb843ba4f0130d28a351218c3fa3b10e7e Mon Sep 17 00:00:00 2001 From: icovada Date: Mon, 22 Aug 2016 19:17:36 +0200 Subject: [PATCH 01/77] Update Telegram notify Add documentation for Document file format as per pull request 2937 on main project --- source/_components/notify.telegram.markdown | 25 +++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/source/_components/notify.telegram.markdown b/source/_components/notify.telegram.markdown index 07455bd989d..ff6ae938e5b 100644 --- a/source/_components/notify.telegram.markdown +++ b/source/_components/notify.telegram.markdown @@ -92,6 +92,31 @@ action: - **username** (*Optional*): Username for an URL which require HTTP basic authentication. - **password** (*Optional*): Username for an URL which require HTTP basic authentication. +### {% linkable_title Document support %} + +```yaml +... +action: + service: notify.NOTIFIER_NAME + data: + title: Send a document + message: That's a example that sends a document. + data: + document: + - url: http://192.168.1.28/bounce.gif + username: admin + password: secrete + - file: /tmp/whatever.odf + caption: Picture Title xy + - url: http://somebla.ie/video.mp4 + caption: I.e. for a Title +``` + +- **url** or **file** (*Required*): For local or remote path to an image. +- **caption** (*Optional*): The title of the image. +- **username** (*Optional*): Username for an URL which require HTTP basic authentication. +- **password** (*Optional*): Username for an URL which require HTTP basic authentication. + ### {% linkable_title Location support %} ```yaml From ef00d7557e982decf4063666cdc7db074be9896d Mon Sep 17 00:00:00 2001 From: icovada Date: Tue, 23 Aug 2016 18:40:58 +0200 Subject: [PATCH 02/77] Fixed documentation due to proposed change --- source/_components/notify.telegram.markdown | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/source/_components/notify.telegram.markdown b/source/_components/notify.telegram.markdown index ff6ae938e5b..e508a9be505 100644 --- a/source/_components/notify.telegram.markdown +++ b/source/_components/notify.telegram.markdown @@ -103,13 +103,9 @@ action: message: That's a example that sends a document. data: document: - - url: http://192.168.1.28/bounce.gif - username: admin - password: secrete - - file: /tmp/whatever.odf - caption: Picture Title xy - - url: http://somebla.ie/video.mp4 - caption: I.e. for a Title + file: /tmp/whatever.odf + caption: Picture Title xy + ``` - **url** or **file** (*Required*): For local or remote path to an image. From 7b495c239489558bed407e27c16794d123c4e852 Mon Sep 17 00:00:00 2001 From: Johann Kellerman Date: Thu, 25 Aug 2016 19:13:53 +0200 Subject: [PATCH 03/77] Introduce the check_config script in 0.27 --- source/getting-started/configuration.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index f9ed323498f..50f2b82f18b 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -23,14 +23,14 @@ If you want to use a different folder for configuration, use the config command Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains which components will be loaded and what their configuration is. Throughout the documentation you will find snippets that you can add to your configuration file to enable that functionality. -If you run into trouble while configuring Home Assistant, have a look at [the configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [configuration.yaml examples](/cookbook/#example-configurationyaml). -

- You will have to restart Home Assistant for changes to `configuration.yaml` take effect. + You will have to restart Home Assistant for changes to `configuration.yaml` to take effect.

+If you run into trouble while configuring Home Assistant, have a look at the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [configuration.yaml examples](/cookbook/#example-configurationyaml). +

- Install colorlog (`$ pip3 install colorlog`) to make the console output easier to read, hence also easier to catch errors and warnings. + Test any changes to your configuration files from the command line with `hass --script check_config`. This script allows you to test changes without the need to restart Home Assistant.

### [Next step: Get familiar with YAML »](/getting-started/yaml/) From 2ab03078d0ab660277e966d37dfc4affd4b26b33 Mon Sep 17 00:00:00 2001 From: Johann Kellerman Date: Thu, 25 Aug 2016 19:56:33 +0200 Subject: [PATCH 04/77] Update troubleshooting-configuration.markdown --- .../troubleshooting-configuration.markdown | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/source/getting-started/troubleshooting-configuration.markdown b/source/getting-started/troubleshooting-configuration.markdown index 00a1651d11b..95d67816c6f 100644 --- a/source/getting-started/troubleshooting-configuration.markdown +++ b/source/getting-started/troubleshooting-configuration.markdown @@ -19,26 +19,27 @@ Whenever a component or configuration option results in a warning, it will be st When a component does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your component you are trying to set up. +If you have incorrect entries in your configuration files you can use the `check_config` script to assist in identifying them: `hass --script check_config`. + #### {% linkable_title Problems with the configuration %} One of the most common problems with Home Assistant is an invalid `configuration.yaml` file. - - - You can test your configuration using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/). + + - You can test your configuration using the command line with: `hass --script check_config` + - You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/). - To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well). -`configuration.yaml` does not allow multiple sections to have the same name. If you want a specific platform to be loaded twice, append a [number or string](/getting-started/devices/#style-2) to the name or nest them using [this style](/getting-started/devices/#style-1). +`configuration.yaml` does not allow multiple sections to have the same name. If you want to load multiplte platforms for one component, you can append a [number or string](/getting-started/devices/#style-2-list-each-device-separately) to the name or nest them using [this style](/getting-started/devices/#style-1-collect-every-entity-under-the-parent): ```yaml sensor: - platform: forecast - ... - -sensor 2: - platform: bitcoin - ... + - platform: forecast + ... + - platform: bitcoin + ... ``` -Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to `home-assistant.log`. You can have a look at [the component page](/components/) for instructions on how to setup the components. +Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to `home-assistant.log`. You can have a look at [the various component pages](/components/) for instructions on how to setup the components. If you find any errors or want to expand the documentation, please [let us know](https://github.com/home-assistant/home-assistant.io/issues). From 425ed38599f14e1c9f928c123c5f0ddb788bec92 Mon Sep 17 00:00:00 2001 From: Johann Kellerman Date: Thu, 25 Aug 2016 20:33:50 +0200 Subject: [PATCH 05/77] Update secrets.markdown --- source/_topics/secrets.markdown | 28 ++++++++++++++++++++++++---- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/source/_topics/secrets.markdown b/source/_topics/secrets.markdown index 3b344efa0ad..60129c98ab5 100644 --- a/source/_topics/secrets.markdown +++ b/source/_topics/secrets.markdown @@ -9,11 +9,11 @@ sharing: true footer: true --- -The `configuration.yaml` file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the `configuration.yaml` file) if you don't want to [split up your configuration](/topics/splitting_configuration/). +The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secrets` you can remove any private information from you configuration files. This separation can also help you to keep easier track of your passwords and API keys. As they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple yaml files if you [split up your configuration](/topics/splitting_configuration/). ### {% linkable_title Using secrets.yaml %} -The workflow for the outsourcing in the `secrets.yaml` is very similar to the [splitting of the configuration](/topics/splitting_configuration/). Create a `secrets.yaml` file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`). +The workflow for moving private information to `secrets.yaml` is very similar to the [splitting of the configuration](/topics/splitting_configuration/). Create a `secrets.yaml` file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`). The entries for password and API keys in the `configuration.yaml` file usually looks like the example below. @@ -32,10 +32,30 @@ http: The `secrets.yaml` file contains the corresponding password assigned to the identifier. ```yaml -logger: debug http_password: YOUR_PASSWORD ``` +### {% linkable_title Debugging secrets %} + +When you start splitting your configuration into multiple files, you might end up with configuration in sub folders. Secrets will be resolved in this order: +- A `secrets.yaml` located in the same folder as the yaml file referencing the secret, +- next, parent folders will be searched for a `secrets.yaml` file with the secret, stopping at the folder with the main `configuration.yaml`, +- lastly, `keyring` will be queried for the secret (more info below) + +To see where secrets are being loaded from you can either add an option to your `secrets.yaml` file or use the `check_config` script. + +*Option 1*: Print where secrets are retrieved from to the Home Assistant log by adding the following to `secrets.yaml`: +```yaml +logger: debug +``` +This will not print the actual secret's value to the log. + +*Option 2*: View where secrets are retrieved from and the contents of all `secrets.yaml` files used, you can use the `check_config` script from the command line: +```bash +hass --script check_config --secrets +``` +This will print all your secrets + ### {% linkable_title Storing passwords in a keyring managed by your OS %} Using [Keyring](http://pythonhosted.org/keyring/) is an alternative way to `secrets.yaml`. They can be managed from the command line via the keyring script. @@ -57,7 +77,7 @@ Create an entry in your keyring. $ hass --script keyring set http_password ``` -If you launch home Assistant now, you will be prompted for the keyring password to unlock your keyring. +If you launch Home Assistant now, you will be prompted for the keyring password to unlock your keyring. ```bash $ hass From 56c83e6b9976fc209ddfa50a710f939a5178eb82 Mon Sep 17 00:00:00 2001 From: Johann Kellerman Date: Thu, 25 Aug 2016 21:12:24 +0200 Subject: [PATCH 06/77] Update splitting_configuration.markdown --- .../_topics/splitting_configuration.markdown | 22 ++++++++++++------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/source/_topics/splitting_configuration.markdown b/source/_topics/splitting_configuration.markdown index 1f3712f81e2..28899b27148 100644 --- a/source/_topics/splitting_configuration.markdown +++ b/source/_topics/splitting_configuration.markdown @@ -15,7 +15,7 @@ First off, several community members have sanitized (read: without api keys/pass As commenting code doesn't always happen, please read on for the details. -Now despite the logical assumption that the `configuration.yaml` will be replaced by this process it will in fact remain all be it in a much less cluttered form. +Now despite the logical assumption that the `configuration.yaml` will be replaced by this process it will in fact remain, albeit in a much less cluttered form. In this lighter version we will still need what could be called the core snippet: @@ -179,17 +179,23 @@ That about wraps it up. If you have issues checkout `home-assistant.log` in the configuration directory as well as your indentations. If all else fails, head over to the [Gitter Chatroom](https://gitter.im/balloob/home-assistant) and ask away. +### {% linkable_title Debugging multiple configuration files %} + +If you have many configuration files, the `check_config` script allows you to see how Home Assistant interprets them: +- Listing all loaded files: `hass --script --check_config --files` +- Viewing a component's config: `hass --script --check_config --info light` +- Or all components' config: `hass --script check_config --info all` + +You can get help from the command line using: `hass --script check_config --help` + ### {% linkable_title Advanced Usage %} We offer four advanced options to include whole directories at once. +- `!include_dir_list` will return the content of a directory as a list with each file content being an entry in the list. +- `!include_dir_named` will return the content of a directory as a dictionary which maps filename => content of file. +- `!include_dir_merge_list` will return the content of a directory as a list by merging all files (which should contain a list) into 1 big list. +- `!include_dir_merge_named` will return the content of a directory as a dictionary by loading each file and merging it into 1 big dictionary. -`!include_dir_list` will return content of a directory as a list with each file content being an entry in the list. - -`!include_dir_named` will return content of a directory as a dictionary which maps filename => content of file. - -`!include_dir_merge_list` will return content of a directory as a list by merging all files (which should contain a list) into 1 big list. - -`!include_dir_merge_named` will return content of a directory as a dictionary by loading each file and merging it into 1 big dictionary. #### {% linkable_title Example: `!include_dir_list` %} From 102e1ed70001e04b594a06a6c228a861e798ea0f Mon Sep 17 00:00:00 2001 From: icovada Date: Sat, 27 Aug 2016 13:43:19 +0200 Subject: [PATCH 07/77] Fixed open parenthesis As suggested by @Landrash --- source/_components/notify.telegram.markdown | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/source/_components/notify.telegram.markdown b/source/_components/notify.telegram.markdown index e508a9be505..4044f9ff3f1 100644 --- a/source/_components/notify.telegram.markdown +++ b/source/_components/notify.telegram.markdown @@ -25,17 +25,8 @@ The quickest way to retrieve your `chat_id` is visiting [https://api.telegram.or The result set will include your chat ID as `id` in the `from` section: ```json -{ - "ok":true, - "result":[ - { - "update_id":254199982, - "message":{ - "message_id":201, - "from":{ - "id":123456789, - "first_name":"Your first name", -... +{"ok":true,"result":[{"update_id":254199982, +"message":{"message_id":27,"from":{"id":123456789,"first_name":"YOUR_FIRST_NAME YOUR_NICK_NAME","last_name":"YOUR_LAST_NAME","username":"YOUR_NICK_NAME"},"chat":{"id":123456789,"first_name":"YOUR_FIRST_NAME YOUR_NICK_NAME","last_name":"YOUR_LAST_NAME","username":"YOUR_NICK_NAME","type":"private"},"date":1678292650,"text":"test"}}]} ``` Another way to get your chat ID directly is described below: From e5255ecd7c3f95f4d8c7d321cccd20998541afb0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robin=20Laur=C3=A9n?= Date: Sat, 27 Aug 2016 23:14:10 +0300 Subject: [PATCH 08/77] Add Added info on how to install python, pip3 and python3-libyaml on a Debian system. --- source/getting-started/troubleshooting.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/getting-started/troubleshooting.markdown b/source/getting-started/troubleshooting.markdown index c2d94b9b00f..420f4ed0d9a 100644 --- a/source/getting-started/troubleshooting.markdown +++ b/source/getting-started/troubleshooting.markdown @@ -21,6 +21,8 @@ If you are able to successfully run `python3 --version` but not `pip3`, install $ python3 -m pip install homeassistant ``` +On a Debian system, you can also install python3 by `sudo apt-get install python3`, and pip3 by `sudo apt-get install python3-pip`. + #### {% linkable_title No module named pip %} [Pip](https://pip.pypa.io/en/stable/) should come bundled with the latest Python 3 but is omitted by some distributions. If you are unable to run `python3 -m pip --version` you can install `pip` by [downloading the installer](https://bootstrap.pypa.io/get-pip.py) and running it with Python 3: @@ -28,6 +30,10 @@ $ python3 -m pip install homeassistant $ python3 get-pip.py ``` +#### {% linkable_title libyaml is not found or a compiler error %} + +On a Debian system, install the Python 3 YAML library by `sudo apt-get install python3-yaml`. + #### {% linkable_title distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both %} This is a known issue if you're on a Mac using Homebrew to install Python. Please follow [these instructions](https://github.com/Homebrew/brew/blob/master/share/doc/homebrew/Homebrew-and-Python.md#note-on-pip-install---user) to resolve it. From 6826408566dcd6280981da65a02b12792383adf3 Mon Sep 17 00:00:00 2001 From: ThinkPadNL Date: Sun, 28 Aug 2016 12:41:24 +0200 Subject: [PATCH 09/77] Update sensor.mhz19.markdown CO2 level outside isn't 250 - 350pmm, but assumed to be 400ppm. It has risen over the years, due to global warming :-( Most sensors that do automatic calibration assume 400ppm as lowest. See also https://www.co2.earth/ for actual CO2 level on the earth. --- source/_components/sensor.mhz19.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.mhz19.markdown b/source/_components/sensor.mhz19.markdown index 027ada3ee2b..31ca4073856 100644 --- a/source/_components/sensor.mhz19.markdown +++ b/source/_components/sensor.mhz19.markdown @@ -11,7 +11,7 @@ ha_category: sensor ha_release: 0.27 --- -The MH-Z19 is a small nondispersive infrared sensor that can measure CO2 sensors. High CO2 levels can lead to drowsiness, poor concentration, loss of attention or increased heart rate. Outside CO2 levels are usually between 250 and 350ppm, but inside levels can reach between 1000 and 5000 ppm. High CO2 levels indicate that you should increase ventilation. +The MH-Z19 is a small nondispersive infrared sensor that can measure CO2 sensors. High CO2 levels can lead to drowsiness, poor concentration, loss of attention or increased heart rate. The CO2 level outside is around 400ppm, but inside levels can reach between 1000 and 5000 ppm. High CO2 levels indicate that you should increase ventilation. Check out the [Open Home Automation web site](https://www.open-homeautomation.com/2016/08/24/monitor-co2-levels-in-your-house/) for a quick guide how to connect the sensor to your PC or Raspberry Pi. From fe4e5da0cc2dd14a42f2cc33b917ef8dec3804ae Mon Sep 17 00:00:00 2001 From: Brendan Berg Date: Sun, 28 Aug 2016 09:30:52 -0600 Subject: [PATCH 10/77] fix grammatical error for "climate" --- source/_components/climate.nest.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/climate.nest.markdown b/source/_components/climate.nest.markdown index 78123905739..69dbc90fdb0 100644 --- a/source/_components/climate.nest.markdown +++ b/source/_components/climate.nest.markdown @@ -17,7 +17,7 @@ The `nest` climate platform let you control a thermostat from [Nest](https://nes To set it up, add the following information to your `configuration.yaml` file: ```yaml -cliamte: +climate: platform: nest ``` From e73712f6410e7b385c0df8131e87de1f73ae37ea Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Sun, 28 Aug 2016 10:18:42 -0700 Subject: [PATCH 11/77] Update 2016-08-27-notifications-hue-fake-unification.markdown Grammar, add forgotten things to breaking changes, add some links --- ...016-08-27-notifications-hue-fake-unification.markdown | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown index aec1949f7a7..ad96944b81a 100644 --- a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown +++ b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown @@ -46,7 +46,7 @@ Now that we have that great news out of the way, onto this week's release which ## {% linkable_title 0.27 %} -While this release is **#Amazing**, we had to break a few eggs (now you understand the title reference!) to make a beautiful omelette (using home automation obviously) so some platforms and components have needed to introduce breaking changes. Please make sure to read the Breaking Changes section below. +While this release is **#Amazing**, we had to break a few eggs (now you understand the title reference!) to make a beautiful omelette (using home automation obviously) so some platforms and components have needed to introduce breaking changes. Please make sure to read the [Breaking Changes](#breaking-changes) section below. ### {% linkable_title Hue Bridge Emulation %} Thanks to [@mgbowen] we now have the functionality previously provided by [@blocke]'s [ha-local-echo](https://github.com/blocke/ha-local-echo) [built right into Home Assistant](/components/emulated_hue/)! This means that for those of you with devices that either lack or have a subpar integration with Home Assistant (looking at you Amazon Echo) you can now have a better experience by having your Home Assistant pretend to be a Hue Bridge. Personally, I have used [@auchter]'s [Haaska](https://github.com/auchter/haaska) previously but found that it was slow to respond and sometimes failed entirely. With the new [`emulated_hue`](/components/emulated_hue/) component, you can have local control of entities through Amazon Echo. @@ -55,7 +55,7 @@ Thanks to [@mgbowen] we now have the functionality previously provided by [@bloc We have some excellent upgrades to the notification system coming to you in 0.27, courtesy of me, [@robbiet480]. #### {% linkable_title HTML5 Push Notifications %} -This release adds support for [HTML5] push notifications on Chrome/Firefox/Opera on both desktop and Android devices. This means that you can send a notification to your phone even your Home Assistant is not in your mobile browser. When using Chrome you can even include 2 action buttons so that you can control your Home Assistant from your phone's lock screen, allowing you to do things like sound alarms or unlock your front door, all without leaving the notification. Thanks again to me ([@robbiet480]) and Paulus ([@balloob]) for all the hard work on this! +This release adds support for [HTML5] push notifications on Chrome/Firefox/Opera on both desktop and Android devices. This means that you can send a notification to your phone even when your Home Assistant is not open in your mobile browser. When using Chrome you can even include 2 action buttons so that you can control your Home Assistant from your phone's lock screen, allowing you to do things like sound alarms or unlock your front door, all without leaving the notification. Thanks again to me ([@robbiet480]) and Paulus ([@balloob]) for all the hard work on this!

@@ -132,6 +132,8 @@ Along with the new `climate` component, [@Teagan42] and I ([@robbiet480]) decide - Forecast.io entity IDs are now like `sensor.forecastio_temperature`. Previously they were like `sensor.weather_temperature`. Apologies for this change, but we needed to make Forecast.io more generic now that we have many weather platforms. - The [Loop Energy][Loop] sensor configuration format changed slightly, please reformat based on the revised documentation. - The configuration for the [SABnzbd] sensor has slightly changed. The prefix `type:` is no longer required for monitored variables. +- The [IMAP] sensor now uses `username` instead of `user`. +- The [NZBGet] sensor has had so many changes I can't list them all. Please refer to the documentation for more info. ### {% linkable_title Deprecations %} - Using the `thermostat` and `hvac` components has been deprecated. Please migrate to the new `climate` component. (just change the component name, the configurations are compatible) @@ -139,7 +141,7 @@ Along with the new `climate` component, [@Teagan42] and I ([@robbiet480]) decide ## {% linkable_title Finishing up %} -Thanks all for sticking with me to the end. I'll be taking over a lot of Paulus's (@balloob) work while he is gone, but as I said, don't worry because he'll be back well before 0.28.0 comes out. Hopefully you didn't find this jovial blog post too jarring from our standard style, I just wrote a lot of this at 2am after being awake for almost 20 hours, so I'm a little loopy hahaha 😴. +Thanks all for sticking with me to the end. I'll be taking over a lot of Paulus's ([@balloob]) work while he is gone, but as I said, don't worry because he'll be back well before 0.28.0 comes out. Hopefully you didn't find this jovial blog post too jarring from our standard style, I just wrote a lot of this at 2am after being awake for almost 20 hours, so I'm a little loopy hahaha 😴. Also, thanks as always to our developer contributors, documentation contributors, but most of all our users! This would've just been a script that Paulus (@balloob) used to control his lights at home if we didn't have your enthusiasm. @@ -221,3 +223,4 @@ Talk to you soon on Gitter and in your pull request comments! [attachments]: /components/notify.slack/ [Hue]: /components/emulated_hue/ [fan]: /components/fan/ +[IMAP]: /components/sensor.imap/ From c9b3fe80c858fa69bbbeecf75685516e1f80d84c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 28 Aug 2016 19:24:36 +0200 Subject: [PATCH 12/77] Alphabetical order --- source/_components/demo.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_components/demo.markdown b/source/_components/demo.markdown index 8903e3cbfc3..3ed516f9147 100644 --- a/source/_components/demo.markdown +++ b/source/_components/demo.markdown @@ -19,14 +19,14 @@ Available demo platforms: - [Alarm control panel](/components/alarm_control_panel/) (`alarm_control_panel`) - [Binary sensor](/components/binary_sensor/) (`binary_sensor`) - [Camera](/components/camera/) (`camera`) +- [Climate](/components/climate/) (`climate`) +- [Cover](/components/cover/) (`cover`) +- [Fan](/components/fan/) (`fan`) - [Light](/components/light/) (`light`) - [Lock](/components/lock/) (`lock`) - [Notification](/components/notify/) (`notify`) -- [Cover](/components/cover/) (`cover`) - [Sensor](/components/sensor/) (`sensor`) - [Switch](/components/switch/) (`switch`) -- [Climate](/components/climate/) (`climate`) -- [Fan](/components/fan/) (`fan`) To integrate a demo platform in Home Assistant, add the following section to your `configuration.yaml` file: From aaf6e26c05e8ad33a15ea1a6adebe8d484d390b1 Mon Sep 17 00:00:00 2001 From: MartinHjelmare Date: Sun, 28 Aug 2016 20:34:50 +0200 Subject: [PATCH 13/77] Fix heatmiser example config * `tstats` requires a list. --- source/_components/climate.heatmiser.markdown | 6 +++--- source/_components/thermostat.heatmiser.markdown | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_components/climate.heatmiser.markdown b/source/_components/climate.heatmiser.markdown index b74bb1c92e1..cbdebfbafde 100644 --- a/source/_components/climate.heatmiser.markdown +++ b/source/_components/climate.heatmiser.markdown @@ -25,9 +25,9 @@ climate: ipaddress: YOUR_IPADDRESS port: YOUR_PORT tstats: - 1: - id: THERMOSTAT_ID - name: THERMOSTAT_NAME + - 1: + id: THERMOSTAT_ID + name: THERMOSTAT_NAME ``` A single interface can handle up to 32 connected devices. diff --git a/source/_components/thermostat.heatmiser.markdown b/source/_components/thermostat.heatmiser.markdown index 7015e5332fb..8b5fe55835e 100644 --- a/source/_components/thermostat.heatmiser.markdown +++ b/source/_components/thermostat.heatmiser.markdown @@ -28,9 +28,9 @@ thermostat: ipaddress: YOUR_IPADDRESS port: YOUR_PORT tstats: - 1: - id: THERMOSTAT_ID - name: THERMOSTAT_NAME + - 1: + id: THERMOSTAT_ID + name: THERMOSTAT_NAME ``` A single interface can handle up to 32 connected devices. From 653f05354d046205c30127ea85cd4ffffa244394 Mon Sep 17 00:00:00 2001 From: Ben Bangert Date: Sun, 28 Aug 2016 13:18:31 -0700 Subject: [PATCH 14/77] Update component initialization for accurate count --- source/developers/component_initialization.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/component_initialization.markdown b/source/developers/component_initialization.markdown index 1724765d998..6f6a5b31587 100644 --- a/source/developers/component_initialization.markdown +++ b/source/developers/component_initialization.markdown @@ -13,7 +13,7 @@ After loading, the bootstrapper will call `setup(hass, config)` method on the co ### {% linkable_title hass: the Home Assistant instance %} -The Home Assistant instance contains three objects to help you interact with the system. +The Home Assistant instance contains four objects to help you interact with the system. | Object | Description | | ------ | ----------- | From 51acfc556028fca2449fe00f908c06d32b1b40c9 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 28 Aug 2016 22:37:00 +0200 Subject: [PATCH 15/77] Add new validations --- source/developers/development_validation.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/development_validation.markdown b/source/developers/development_validation.markdown index 4dd5c9bbf3b..50d0a675df4 100644 --- a/source/developers/development_validation.markdown +++ b/source/developers/development_validation.markdown @@ -19,7 +19,7 @@ Beside the [voluptuous](https://pypi.python.org/pypi/voluptuous) default types a - Entity ID: `entity_id` and `entity_ids` - Numbers: `small_float` and `positive_int` - Time: `time`, `time_zone` -- Misc: `template`, `slug`, `temperature_unit`, `latitude`, `longitude`, `isfile`, `sun_event`, `ensure_list`, and `icon` +- Misc: `template`, `slug`, `temperature_unit`, `latitude`, `longitude`, `isfile`, `sun_event`, `ensure_list`, `port`, `url`, and `icon` To validate plaforms using [MQTT](/components/mqtt/) there are `valid_subscribe_topic` and `valid_publish_topic` present. From c85ef82e6172ef3ebb41455614d2e3ab3542dffa Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 28 Aug 2016 22:38:40 +0200 Subject: [PATCH 16/77] Add entry for validation --- source/_includes/asides/developers_navigation.html | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_includes/asides/developers_navigation.html b/source/_includes/asides/developers_navigation.html index 080320a1141..c5c8089f310 100644 --- a/source/_includes/asides/developers_navigation.html +++ b/source/_includes/asides/developers_navigation.html @@ -19,6 +19,7 @@

  • {% active_link /developers/development_checklist/ Checklist %}
  • {% active_link /developers/development_testing/ Testing %}
  • {% active_link /developers/development_catching_up/ Catching up with Reality %}
    • +
  • {% active_link /developers/development_validation/ Validation %}
  • From 7ac8c005b282c98e528a17cea07f09481631b82d Mon Sep 17 00:00:00 2001 From: John Arild Berentsen Date: Sun, 28 Aug 2016 22:57:24 +0200 Subject: [PATCH 17/77] Update cover.command_line.markdown Wrong config commands --- source/_components/cover.command_line.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_components/cover.command_line.markdown b/source/_components/cover.command_line.markdown index d7e223ca011..42505959da6 100644 --- a/source/_components/cover.command_line.markdown +++ b/source/_components/cover.command_line.markdown @@ -22,10 +22,10 @@ cover: - platform: command_line covers: Garage door: - open_cmd: move_command up kitchen - close_cmd: move_command down kitchen - stop_cmd: move_command stop kitchen - state_cmd: state_command kitchen + opencmd: move_command up kitchen + closecmd: move_command down kitchen + stopcmd: move_command stop kitchen + statecmd: state_command kitchen value_template: {% raw %}> {% if value == 'open' %} 100 @@ -39,8 +39,8 @@ Configuration variables: - **covers** (*Required*): The array that contains all command line covers. - **entry** (*Required*): Name of the command line cover. Multiple entries are possible. - - **open_cmd** (*Required*): The command to open the cover. - - **close_cmd** (*Required*): The action to close the cover. - - **stop_cmd** (*Required*): The action to stop the cover. - - **state_cmd** (*Optional*): If given, this will act as a sensor that runs in the background and updates the state of the cover. If the command returns a `0` the indicates the cover is fully closed, whereas a 100 indicates the cover is fully open. + - **opencmd** (*Required*): The command to open the cover. + - **closecmd** (*Required*): The action to close the cover. + - **stopcmd** (*Required*): The action to stop the cover. + - **statecmd** (*Optional*): If given, this will act as a sensor that runs in the background and updates the state of the cover. If the command returns a `0` the indicates the cover is fully closed, whereas a 100 indicates the cover is fully open. - **value_template** (*optional - default: '{% raw %}{{ value }}{% endraw%}'*): if specified, `state_cmd` will ignore the result code of the command but the template evaluating will indicate the position of the cover. For example, if your `state_cmd` returns a string "open", using `value_template` as in the example config above will allow you to translate that into the valid state `100`. From 216f5a4d0292fa341c8de4b77d0c25bad2686108 Mon Sep 17 00:00:00 2001 From: Martin Hjelmare Date: Mon, 29 Aug 2016 05:08:25 +0200 Subject: [PATCH 18/77] Fix media_player services (#860) * Correct service and attribute names and add missing services. --- source/_components/media_player.markdown | 30 ++++++++++++------------ 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown index 9bf349acaa3..c6dde16fc29 100644 --- a/source/_components/media_player.markdown +++ b/source/_components/media_player.markdown @@ -14,32 +14,32 @@ Interacts with media players on your network. Please check the sidebar for a ful ## {% linkable_title Services %} ### {% linkable_title Media control services %} -Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `media_play_pause`, `media_play`, `media_pause`, `media_next_track`, `media_previous_track`, `clear_playlist` +Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `media_play_pause`, `media_play`, `media_pause`, `media_stop`, `media_next_track`, `media_previous_track`, `clear_playlist` | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | yes | Target a specific media player. Defaults to all. -#### {% linkable_title Service `media_player/mute_volume` %} +#### {% linkable_title Service `media_player/volume_mute` %} -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | Target a specific media player. Defaults to all. -| `mute` | no | True/false for mute/unmute +| Service data attribute | Optional | Description | +|------------------------|----------|--------------------------------------------------| +| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `is_volume_muted` | no | True/false for mute/unmute | -#### {% linkable_title Service `media_player/set_volume_level` %} +#### {% linkable_title Service `media_player/volume_set` %} -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | Target a specific media player. Defaults to all. -| `volume` | no | Integer for volume level +| Service data attribute | Optional | Description | +|------------------------|----------|--------------------------------------------------| +| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `volume_level` | no | Integer for volume level | #### {% linkable_title Service `media_player/media_seek` %} -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | Target a specific media player. Defaults to all. -| `position` | no | Position to seek to. The format is platform dependent. +| Service data attribute | Optional | Description | +|------------------------|----------|--------------------------------------------------------| +| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `seek_position` | no | Position to seek to. The format is platform dependent. | #### {% linkable_title Service `media_player/play_media` %} From fad9cfa968f94f7824f20193289ac030bdeae8c5 Mon Sep 17 00:00:00 2001 From: John Arild Berentsen Date: Mon, 29 Aug 2016 07:38:14 +0200 Subject: [PATCH 19/77] Update cover.mqtt.markdown --- source/_components/cover.mqtt.markdown | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown index 9b544407af7..9723c560553 100644 --- a/source/_components/cover.mqtt.markdown +++ b/source/_components/cover.mqtt.markdown @@ -30,27 +30,31 @@ cover: state_topic: "home-assistant/cover" command_topic: "home-assistant/cover/set" name: "MQTT Sensor" - optimistic: false qos: 0 retain: true + payload_open: "PAYLOAD_OPEN" + payload_close: "PAYLOD__CLOSE" + payload_stop: "PAYLOAD_STOP" state_open: "STATE_OPEN" state_closed: "STATE_CLOSED" - service_open: "SERVICE_OPEN" - service_close: "SERVICE_CLOSE" + optimistic: false + retain: false value_template: '{% raw %}{{ value.x }}{% endraw %}' ``` Configuration variables: - **state_topic** (*Required*): The MQTT topic subscribed to receive sensor values. +- **command_topic** (*Required*): The MQTT topic to publish commands to control the rollershutter. - **name** (*Optional*): The name of the sensor. Default is "MQTT Sensor". -- **state_open** (*Optional*): The payload that represents open state. Default is"STATE_OPEN" -- **state_closed** (*Optional*): The payload that represents closed state. Default is "STATE_CLOSED" -- **service_open** (*Optional*): The payload that represents open state in service mode. Default is"SERVICE_OPEN" -- **service_close** (*Optional*): The payload that represents closed state in service mode. Default is "SERVICE_CLOSE" -- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is `true` if no state topic defined, else `false`. - **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages. - **retain** (*Optional*): If the published message should have the retain flag on or not. +- **payload_open** (*Optional*): The payload that opens the cover. Default is "UP" +- **payload_close** (*Optional*): The payload that closes the cover. Default is "DOWN" +- **payload_stop** (*Optional*): The payload that stops the rollershutter. default is "STOP" +- **state_open** (*Optional*): The payload that represents open state. Default is"STATE_OPEN" +- **state_closed** (*Optional*): The payload that represents closed state. Default is "STATE_CLOSED" +- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is `true` if no state topic defined, else `false`. - **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract a value from the payload. For a quick check you can use the commandline tools shipped with `mosquitto` to send MQTT messages. Set the state of your sensor manually: From 03ad5afd9606bce855a9e7de313aee870263e0b4 Mon Sep 17 00:00:00 2001 From: oa- Date: Mon, 29 Aug 2016 11:46:34 +0200 Subject: [PATCH 20/77] Updated title Changed the title to differentiate it from the non-LE Bluetooth tracker --- source/_components/device_tracker.bluetooth_le_tracker.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/device_tracker.bluetooth_le_tracker.markdown b/source/_components/device_tracker.bluetooth_le_tracker.markdown index c037525ba82..62effa6f6d9 100644 --- a/source/_components/device_tracker.bluetooth_le_tracker.markdown +++ b/source/_components/device_tracker.bluetooth_le_tracker.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "Bluetooth Tracker" +title: "Bluetooth LE Tracker" description: "Instructions for integrating bluetooth low-energy tracking within Home Assistant." date: 2016-08-24 00:00 sidebar: true From 3ab278f809c6e5af3b1e191e17cf69155f2cc803 Mon Sep 17 00:00:00 2001 From: John Arild Berentsen Date: Mon, 29 Aug 2016 12:28:41 +0200 Subject: [PATCH 21/77] Update cover.command_line.markdown --- source/_components/cover.command_line.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/cover.command_line.markdown b/source/_components/cover.command_line.markdown index 42505959da6..63452cc16be 100644 --- a/source/_components/cover.command_line.markdown +++ b/source/_components/cover.command_line.markdown @@ -43,4 +43,4 @@ Configuration variables: - **closecmd** (*Required*): The action to close the cover. - **stopcmd** (*Required*): The action to stop the cover. - **statecmd** (*Optional*): If given, this will act as a sensor that runs in the background and updates the state of the cover. If the command returns a `0` the indicates the cover is fully closed, whereas a 100 indicates the cover is fully open. - - **value_template** (*optional - default: '{% raw %}{{ value }}{% endraw%}'*): if specified, `state_cmd` will ignore the result code of the command but the template evaluating will indicate the position of the cover. For example, if your `state_cmd` returns a string "open", using `value_template` as in the example config above will allow you to translate that into the valid state `100`. + - **value_template** (*optional - default: '{% raw %}{{ value }}{% endraw%}'*): if specified, `statecmd` will ignore the result code of the command but the template evaluating will indicate the position of the cover. For example, if your `statecmd` returns a string "open", using `value_template` as in the example config above will allow you to translate that into the valid state `100`. From e0c415b7f3ddc9667804068feb19d7e8c00b9f6b Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Mon, 29 Aug 2016 19:40:32 +0200 Subject: [PATCH 22/77] Add blog post from #664 --- ...-31-esp8266-and-micropython-part2.markdown | 106 ++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown diff --git a/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown b/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown new file mode 100644 index 00000000000..0acd2c0205e --- /dev/null +++ b/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown @@ -0,0 +1,106 @@ +--- +layout: post +title: "ESP8266 and MicroPython - Part 2" +description: "Export, process, and visualize data stored by Home Assistant." +date: 2016-08-31 06:17:25 +0200 +date_formatted: "August 31, 2016" +author: Fabian Affolter +comments: true +categories: How-To MQTT ESP8266 Micropython +og_image: /images/blog/2016-07-micropython/social.png +--- + + +So, part 1 of [ESP8266 and MicroPython](/blog/2016/07/28/esp8266-and-micropython-part1/) was pretty lame, right? Instead of getting information out of Home Assistant we are going a step forward and create our own sensor which is sending details about its state to a Home Assistant instance. + + + +Beside [HTTP POST](https://en.wikipedia.org/wiki/POST_(HTTP)) requests, MQTT is the quickest way (from the author's point of view) to publish information with DIY devices. + +You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly. This means the sensor must take initiative. + +An example for pulling is [aREST](/components/sensor.arest/). This is a great way to work with the ESP8266 based units and the Ardunio IDE. + +### {% linkable_title MQTT %} + +You can find a simple examples for publishing and subscribing with MQTT in the [MicroPython](https://github.com/micropython/micropython-lib) library overview in the section for [umqtt](https://github.com/micropython/micropython-lib/tree/master/umqtt.simple). + +The example below is adopted from the work of [@davea](https://github.com/davea) as we don't want to re-invent the wheel. The configuration feature is crafty and simplyfies the code with the usage of a file called `/config.json` which stores the configuration details. The ESP8266 device will send the value of a pin every 5 seconds. + + +```python +import machine +import time +import ubinascii +import webrepl + +from umqtt.simple import MQTTClient + +# These defaults are overwritten with the contents of /config.json by load_config() +CONFIG = { + "broker": "192.168.1.19", + "sensor_pin": 0, + "client_id": b"esp8266_" + ubinascii.hexlify(machine.unique_id()), + "topic": b"home", +} + +client = None +sensor_pin = None + +def setup_pins(): + global sensor_pin + sensor_pin = machine.ADC(CONFIG['sensor_pin']) + +def load_config(): + import ujson as json + try: + with open("/config.json") as f: + config = json.loads(f.read()) + except (OSError, ValueError): + print("Couldn't load /config.json") + save_config() + else: + CONFIG.update(config) + print("Loaded config from /config.json") + +def save_config(): + import ujson as json + try: + with open("/config.json", "w") as f: + f.write(json.dumps(CONFIG)) + except OSError: + print("Couldn't save /config.json") + +def main(): + client = MQTTClient(CONFIG['client_id'], CONFIG['broker']) + client.connect() + print("Connected to {}".format(CONFIG['broker'])) + while True: + data = sensor_pin.read() + client.publish('{}/{}'.format(CONFIG['topic'], + CONFIG['client_id']), + bytes(str(data), 'utf-8')) + print('Sensor state: {}'.format(data)) + time.sleep(5) + +if __name__ == '__main__': + load_config() + setup_pins() + main() +``` + +Subscribe to the topic `home/#` or create a [MQTT sensor](/components/sensor.mqtt/) to check if the sensor values are published. + +```bash +$ mosquitto_sub -h 192.168.1.19 -v -t "home/#" +``` + +```yaml +sensor: + - platform: mqtt + state_topic: "home/esp8266_[last part of the MAC address]" + name: "MicroPython" +``` + +[@davea](https://github.com/davea) created [sonoff-mqtt](https://github.com/davea/sonoff-mqtt). This code will work on ESP8622 based devices too and shows how to use a button to control a relay. + From 83a2c1f561c2d24469ab9d1e7d2ef9cd53b60a33 Mon Sep 17 00:00:00 2001 From: sgauche Date: Mon, 29 Aug 2016 15:19:35 -0400 Subject: [PATCH 23/77] Update device_tracker.locative.markdown --- source/_components/device_tracker.locative.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/device_tracker.locative.markdown b/source/_components/device_tracker.locative.markdown index 8c98cdd88d6..9e4f6b7b0af 100644 --- a/source/_components/device_tracker.locative.markdown +++ b/source/_components/device_tracker.locative.markdown @@ -26,7 +26,7 @@ Install on your smartphone: - [Android](https://play.google.com/store/apps/details?id=io.locative.app) - [iOS](https://itunes.apple.com/us/app/geofancy/id725198453) -To configure Locative, you must set up the app to send a `GET` request to your Home Assistant server at `http:///api/locative`. Make sure to include the API password if you have configured a password in Home Assistant (add `?api_password=` to the end of the URL). When you enter or exit a geofence, Locative will send a `GET` request to that URL, updating Home Assistant. +To configure Locative, you must set up the app to send a `GET` request to your Home Assistant server at `http:///api/locative`. Make sure to include the API password if you have configured a password in Home Assistant (add `?api_password=` to the end of the URL). When you enter or exit a geofence, Locative will send a `GET` request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your known_devices.yaml file for a new device that Locative will have created on it's first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.

    From 0a14d4cbdc75377d21103b37581fe4cd780fc049 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Mon, 29 Aug 2016 21:47:59 +0200 Subject: [PATCH 24/77] Update categories --- source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown b/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown index ef91fc3e7b6..dbd69240e14 100644 --- a/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown +++ b/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown @@ -6,7 +6,7 @@ date: 2016-07-28 06:00:00 +0200 date_formatted: "July 28, 2016" author: Fabian Affolter comments: true -categories: How-To +categories: How-To ESP8266 Micropython og_image: /images/blog/2016-07-micropython/social.png --- From 0443eceaf203b7dafc79f4ec9c9d8b3d030379ea Mon Sep 17 00:00:00 2001 From: garrettbeachy Date: Mon, 29 Aug 2016 21:22:35 -0500 Subject: [PATCH 25/77] Update climate.honeywell.markdown Fix typo on Honeywell page. --- source/_components/climate.honeywell.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/climate.honeywell.markdown b/source/_components/climate.honeywell.markdown index 28b5fd13e34..67bf292f3d5 100644 --- a/source/_components/climate.honeywell.markdown +++ b/source/_components/climate.honeywell.markdown @@ -17,7 +17,7 @@ The `honeywell` cliamte platform let you control [Honeywell Connected](http://ge To set it up, add the following information to your `configuration.yaml` file: ```yaml -cliamte: +climate: platform: honeywell username: YOUR_USERNAME password: YOUR_PASSWORD From 87c49bcc09ee21ce4aab1f06b75072d21cfe6aba Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 30 Aug 2016 11:48:38 +0200 Subject: [PATCH 26/77] Update description --- source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown b/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown index 0acd2c0205e..8d0b710a69f 100644 --- a/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown +++ b/source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown @@ -1,7 +1,7 @@ --- layout: post title: "ESP8266 and MicroPython - Part 2" -description: "Export, process, and visualize data stored by Home Assistant." +description: "Using MicroPython and MQTT on ESP8266 based devices and Home Assistant." date: 2016-08-31 06:17:25 +0200 date_formatted: "August 31, 2016" author: Fabian Affolter From 5bf47768f2374fec743c55a6cfd53178f31cd0de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20H=C3=B8yer=20Iversen?= Date: Tue, 30 Aug 2016 15:19:07 +0200 Subject: [PATCH 27/77] Update sensor.loop_energy.markdown --- source/_components/sensor.loop_energy.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/sensor.loop_energy.markdown b/source/_components/sensor.loop_energy.markdown index f2c12fe4ca0..d7ef5fb3421 100644 --- a/source/_components/sensor.loop_energy.markdown +++ b/source/_components/sensor.loop_energy.markdown @@ -53,6 +53,7 @@ sensor: gas_secret: 'GAS_SECRET' gas_type: imperial gas_calorific: 38.2 +``` Configuration variables: From 2ddeb7bde35eddd3511291162d6ba82a74360964 Mon Sep 17 00:00:00 2001 From: Thomas Wilson Date: Wed, 31 Aug 2016 03:08:22 +0800 Subject: [PATCH 28/77] Added quotes around states in examples (#870) These examples in the tutorial didn't actually work - adding the quote marks around the state names fixed it. --- source/getting-started/automation-create-first.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/getting-started/automation-create-first.markdown b/source/getting-started/automation-create-first.markdown index 066f03788da..28f4788fdf5 100644 --- a/source/getting-started/automation-create-first.markdown +++ b/source/getting-started/automation-create-first.markdown @@ -37,7 +37,7 @@ automation: condition: condition: state entity_id: group.all_devices - state: home + state: 'home' action: service: light.turn_on ``` @@ -66,7 +66,7 @@ automation: condition: condition: state entity_id: group.all_devices - state: home + state: 'home' action: service: light.turn_on entity_id: group.living_room @@ -93,7 +93,7 @@ automation: condition: condition: state entity_id: group.all_devices - state: home + state: 'home' action: service: homeassistant.turn_on entity_id: group.living_room From 8959fb2178d660d7467d69ebdecd984b86de0eb0 Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Tue, 30 Aug 2016 14:31:28 -0700 Subject: [PATCH 29/77] Update 0.27 blog post to add 0.27.1 --- ...otifications-hue-fake-unification.markdown | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown index ad96944b81a..842230872d5 100644 --- a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown +++ b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown @@ -155,11 +155,33 @@ Talk to you soon on Gitter and in your pull request comments! (p.s. To those of you that scrolled directly to the bottom to get your present, just know that you didn't earn it like the others did. 😄) +### {% linkable_title Hotfix 0.27.1 - August 30 %} + +- Migrate APCUPSd to voluptuous ([@fabaff]) +- Ecobee operation mode fix ([@turbokongen]) +- update ha-ffmpeg version to 0.9 ([@pvizeli]) +- Device tracker component & platform validation. No more home_range. ([@kellerza]) +- Added option to use effect:random for Flux Led light bulbs ([@tchellomello]) +- Use voluptuous for smtp ([@pvizeli]) +- Upgrade sendgrid to 3.2.10 ([@fabaff]) +- Upgrade TwitterAPI to 2.4.2 ([@fabaff]) +- Fix bug in wemo discovery caused by voluptuous addition. ([@pavoni]) +- Bug fix for asuswrt device_tracker. ([@Danielhiversen]) +- Remove units for humidity in Wundeground sensor ([@arsaboo]) +- Fix media_player descriptions and select_source ([@MartinHjelmare]) +- Allow user to configure server id to perform speed test against ([@Teagan42]) +- Bug fix for asuswrt device_tracker. ([@Danielhiversen]) +- More Ecobee operation mode fixes ([@turbokongen]) +- Map Modes to setpoint indexes ([@turbokongen]) +- fix voluptuous and cover autodiscovery ([@pvizeli]) +- Fixes wrong statevalue and problem with zwave setpoint ([@turbokongen]) + [@arsaboo]: https://github.com/arsaboo [@auchter]: https://github.com/auchter [@balloob]: https://github.com/balloob [@blocke]: https://github.com/blocke [@BluGeni]: https://github.com/BluGeni +[@Danielhiversen]: https://github.com/Danielhiversen [@danielperna84]: https://github.com/danielperna84 [@DavidMStraub]: https://github.com/DavidMStraub [@dpford]: https://github.com/dpford @@ -168,6 +190,7 @@ Talk to you soon on Gitter and in your pull request comments! [@jnewland]: https://github.com/jnewland [@Juggels]: https://github.com/Juggels [@kellerza]: https://github.com/kellerza +[@MartinHjelmare]: https://github.com/MartinHjelmare [@mcdeck]: https://github.com/mcdeck [@meatz]: https://github.com/meatz [@mgbowen]: https://github.com/mgbowen @@ -181,6 +204,7 @@ Talk to you soon on Gitter and in your pull request comments! [@roidayan]: https://github.com/roidayan [@roidayan]: ttps://github.com/roidayan [@shmuelzon]: https://github.com/shmuelzon +[@tchellomello]: https://github.com/tchellomello [@Teagan42]: https://github.com/Teagan42 [@technicalpickles]: https://github.com/technicalpickles [@tobiebooth]: https://github.com/tobiebooth From 8e3285c4050dee7971c2dc1b13a146bdb0d522c5 Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Tue, 30 Aug 2016 14:32:54 -0700 Subject: [PATCH 30/77] Bump version to 0.27.1 --- source/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/index.html b/source/index.html index ff9002a5941..348ec99e227 100644 --- a/source/index.html +++ b/source/index.html @@ -15,7 +15,7 @@ hide_github_edit: true

    -

    Current Version: 0.27.0

    +

    Current Version: 0.27.1

    Released: August 27, 2016
    From dad1fcce4be11983416f52160f4f3032c1620b4e Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Tue, 30 Aug 2016 14:37:02 -0700 Subject: [PATCH 31/77] few quick little fixes more for 0.27.1 --- .../2016-08-27-notifications-hue-fake-unification.markdown | 2 +- source/index.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown index 842230872d5..9ca0502c6d4 100644 --- a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown +++ b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown @@ -155,7 +155,7 @@ Talk to you soon on Gitter and in your pull request comments! (p.s. To those of you that scrolled directly to the bottom to get your present, just know that you didn't earn it like the others did. 😄) -### {% linkable_title Hotfix 0.27.1 - August 30 %} +## {% linkable_title Hotfix 0.27.1 - August 30 %} - Migrate APCUPSd to voluptuous ([@fabaff]) - Ecobee operation mode fix ([@turbokongen]) diff --git a/source/index.html b/source/index.html index 348ec99e227..3e8428bd3a4 100644 --- a/source/index.html +++ b/source/index.html @@ -16,7 +16,7 @@ hide_github_edit: true

    Current Version: 0.27.1

    - Released: August 27, 2016 + Released: August 30, 2016
    Release notes From 5a87799e94f0f5e254121757d938f3348b75015c Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Tue, 30 Aug 2016 14:55:32 -0700 Subject: [PATCH 32/77] Update Amazon Echo docs to remove reference to Haaska and instead reference Emulated Hue --- source/_components/alexa.markdown | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/source/_components/alexa.markdown b/source/_components/alexa.markdown index de63e935db5..539db723bb9 100644 --- a/source/_components/alexa.markdown +++ b/source/_components/alexa.markdown @@ -22,12 +22,11 @@ Amazon has released [Echosim], a website that simulates the Alexa service in you ## {% linkable_title I just want to turn devices on and off using Echo %} -If you just want to be able to turn anything with a switch (like lights, switches, media players, etc) on and off, check out Michael Auchter's [Haaska][haaska-github-link] which integrates the [Alexa Lighting API][alexa-lighting-api] into Home Assistant. +If you just want to be able to turn anything with a switch (like lights, switches, media players, etc) on and off, you should enable the [Emulated Hue][emulated-hue-component] component. It makes your Home Assistant appear as if it were a Phillips Hue bridge, which Echo works with natively. -[haaska-github-link]: https://github.com/auchter/haaska -[alexa-lighting-api]: https://developer.amazon.com/public/binaries/content/assets/html/alexa-lighting-api.html +[emulated-hue-component]: https://home-assistant.io/components/emulated_hue/ -Implementing Haaska means you can turn things on and off by simply saying +Enabling the Emulated Hue component means you can turn things on and off by simply saying > Alexa, turn the living room lights on. @@ -43,9 +42,9 @@ or > Alexa, tell Home Assistant to set the living room lights to twenty percent. -In addition, you would need to build custom intents for each device and on/off combination using the below method, whereas everything just works without any extra work by using Haaska. +In addition, you would need to build custom intents for each device and on/off combination using the below method, whereas everything just works without any extra work by using Emulated Hue. -Please note that you can use Haaska and the built-in Alexa component side-by-side without issue if you wish. +Please note that you can use Emulated Hue and the built-in Alexa component side-by-side without issue if you wish. ## {% linkable_title I want to build custom commands to use with Echo %} From e3379ae2aafda94761013ee12371f8c36ffdc78c Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 31 Aug 2016 08:43:32 +0200 Subject: [PATCH 33/77] Update camera.ffmpeg.markdown --- source/_components/camera.ffmpeg.markdown | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 8e988bcc702..d4496aa6c88 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -42,3 +42,13 @@ Configuration variables: You can control the `image quality` with [`extra_arguments`](https://www.ffmpeg.org/ffmpeg-codecs.html#jpeg2000) `-q:v 2-32` or with lossless option `-pred 1`. +### {% linkable_title Troubleshooting %} + +In most of case, ffmpeg autodetect all needed options to read a video/audio stream or file. But it is possible in rare cases that's needed to set a option to help ffmpeg. Default ffmpeg use 5 seconds to detect all options or abord. + +First check, if your stream playable by ffmpeg with (use option `-an` or `-vn` to disable video or audio stream): +``` +ffmpeg -i INPUT -an -f null - +``` +Now you can see what going wrong. + From 4f44889c652911313c212a4f515c776cec527885 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 31 Aug 2016 08:55:44 +0200 Subject: [PATCH 34/77] Update camera.ffmpeg.markdown --- source/_components/camera.ffmpeg.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index d4496aa6c88..4e2ea5cca6d 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -50,5 +50,8 @@ First check, if your stream playable by ffmpeg with (use option `-an` or `-vn` t ``` ffmpeg -i INPUT -an -f null - ``` -Now you can see what going wrong. +Now you can see what going wrong. Following list could be help to solve your trouble: + +- `[rtsp @ ...] UDP timeout, retrying with TCP`: You need to set rtsp transport in config with: `input: -rtsp_transport tcp -i INPUT` +- `[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size`: FFmpeg need more data or time for autodetect. You can set the 'analyzeduration' and/or 'probesize' option, play with this value. If you now the needed value you can set it to config with: `input: -analyzeduration xy -probesize xy tcp -i INPUT`. More info about that on [ffmpeg](https://www.ffmpeg.org/ffmpeg-formats.html#Description). From 74b7bb8b500fc6e0bb81784c74d880baef349710 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 31 Aug 2016 09:00:24 +0200 Subject: [PATCH 35/77] Update camera.ffmpeg.markdown --- source/_components/camera.ffmpeg.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 4e2ea5cca6d..cb36b8367e0 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -53,5 +53,5 @@ ffmpeg -i INPUT -an -f null - Now you can see what going wrong. Following list could be help to solve your trouble: - `[rtsp @ ...] UDP timeout, retrying with TCP`: You need to set rtsp transport in config with: `input: -rtsp_transport tcp -i INPUT` -- `[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size`: FFmpeg need more data or time for autodetect. You can set the 'analyzeduration' and/or 'probesize' option, play with this value. If you now the needed value you can set it to config with: `input: -analyzeduration xy -probesize xy tcp -i INPUT`. More info about that on [ffmpeg](https://www.ffmpeg.org/ffmpeg-formats.html#Description). +- `[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size`: FFmpeg need more data or time for autodetect. You can set the 'analyzeduration' and/or 'probesize' option, play with this value. If you know the needed value you can set it to config with: `input: -analyzeduration xy -probesize xy tcp -i INPUT`. More info about that on [ffmpeg](https://www.ffmpeg.org/ffmpeg-formats.html#Description). From 0e66f3259438f6051a69cc9f2d11f7e66de000e4 Mon Sep 17 00:00:00 2001 From: Greg Dowling Date: Wed, 31 Aug 2016 10:12:21 +0100 Subject: [PATCH 36/77] Fix incorrect template in example. --- source/_components/switch.template.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/switch.template.markdown b/source/_components/switch.template.markdown index 2d4694e956f..971b0824d40 100644 --- a/source/_components/switch.template.markdown +++ b/source/_components/switch.template.markdown @@ -84,7 +84,7 @@ switch: switches: blind: friendly_name: 'Blind' - value_template: {% raw %}'{{ state }}'{% endraw %} + value_template: {% raw %}'{{ is_state_attr("switch.blind_toggle", "sensor_state", "on") }}'{% endraw %} turn_on: service: switch.toggle entity_id: switch.blind_toggle From 178cfa5eed66a29d99e079286a0d4793a446bc10 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 30 Aug 2016 11:45:22 +0200 Subject: [PATCH 37/77] Small update --- .../2016-07-28-esp8266-and-micropython-part1.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown b/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown index dbd69240e14..7eb34d1bfff 100644 --- a/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown +++ b/source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown @@ -13,7 +13,7 @@ og_image: /images/blog/2016-07-micropython/social.png The first release of Micropython for ESP8266 was delivered a couple of weeks ago. The [documentation](http://docs.micropython.org/en/latest/esp8266/esp8266_contents.html) covers a lot of ground. This post is providing only a little summary which should get you started. -Until a couple of weeks ago, the pre-built MicroPython binary for the ESP8266 was only available to backers. This has changed now and it is available to the public for [download](https://micropython.org/download/#esp8266). +Until a couple of weeks ago, the pre-built MicroPython binary for the ESP8266 was only available to backers of the Kickstarter campaign. This has changed now and it is available to the public for [download](https://micropython.org/download/#esp8266). @@ -57,7 +57,7 @@ Type "help()" for more information. ```

    -The public build of the firmware may be different than the firmware distributed to the backers of the campaign. Especially in regard of the [available modules](http://docs.micropython.org/en/latest/esp8266/py-modindex.html), turned on debug messages, and alike. Also, the WebREPL may not be started by default. +The public build of the firmware may be different than the firmware distributed to the backers of the Kickstarter campaign. Especially in regard of the [available modules](http://docs.micropython.org/en/latest/esp8266/py-modindex.html), turned on debug messages, and alike. Also, the WebREPL may not be started by default.

    Connect a LED to pin 5 (or another pin of your choosing) to check if the ESP8266 is working as expected. @@ -117,7 +117,7 @@ If you reboot, you should see your current IP address in the terminal. First let's create a little consumer for Home Assistant sensor's state. The code to place in `main.py` is a mixture of code from above and the [RESTful API](/developers/rest_api/) of Home Assistant. If the temperature in the kitchen is higher than 20 °C then the LED connected to pin 5 is switched on.

    -If a module is missing then you need to download is it from [MicroPython Library overview](https://github.com/micropython/micropython-lib) and upload it to the ESP8266 with `webrepl_cli.py` manually. +If a module is missing then you need to download it from the [MicroPython Library overview](https://github.com/micropython/micropython-lib) and upload it to the ESP8266 with `webrepl_cli.py` manually.

    ```python From 0c0b2c9d18b7153c94ba92efb11aacd4a7dacade Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Aug 2016 11:41:56 +0200 Subject: [PATCH 38/77] Minor updates --- source/_components/binary_sensor.ffmpeg.markdown | 2 ++ source/_components/camera.ffmpeg.markdown | 8 +++++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/source/_components/binary_sensor.ffmpeg.markdown b/source/_components/binary_sensor.ffmpeg.markdown index 5d9d9f433df..b9e16a2a589 100644 --- a/source/_components/binary_sensor.ffmpeg.markdown +++ b/source/_components/binary_sensor.ffmpeg.markdown @@ -94,3 +94,5 @@ For playing with values (changes/100 is the scene value on ffmpeg): ```bash $ ffmpeg -i YOUR_INPUT -an -filter:v select=gt(scene\,0.1) -f framemd5 - ``` + +If you are running into trouble with this sensor, please refer to this [Troubleshooting section](/components/camera.ffmpeg/#troubleshooting). diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index cb36b8367e0..92920e10742 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -16,7 +16,7 @@ ha_release: 0.26 The `ffmpeg` platform allows you to use every video feed with [FFmpeg](http://www.ffmpeg.org/) as camera in Home Assistant.

    -You need a ffmpeg binary in your system path. On debain 8 you can install it from backports. If you want HW support on raspberry you need self build from source. Windows binary are avilable on ffmpeg homepage. +You need a `ffmpeg` binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need tobuild from source by yourself. Windows binary are avilable on the [FFmpeg](http://www.ffmpeg.org/) website.

    To enable your FFmpeg feed in your installation, add the following to your `configuration.yaml` file: @@ -36,7 +36,7 @@ Configuration variables: - **input** (*Required*): A ffmpeg compatible input file, stream or feed. - **name** (*Optional*): This parameter allows you to override the name of your camera. - **ffmpeg_bin** (*Optional*): Default 'ffmpeg'. -- **extra_arguments** (*Optional*): Extra option they will pass to ffmpeg. i.e. image quality or video filter options. +- **extra_arguments** (*Optional*): Extra option they will pass to `ffmpeg`. i.e. image quality or video filter options. ### {% linkable_title Image quality %} @@ -47,9 +47,11 @@ You can control the `image quality` with [`extra_arguments`](https://www.ffmpeg. In most of case, ffmpeg autodetect all needed options to read a video/audio stream or file. But it is possible in rare cases that's needed to set a option to help ffmpeg. Default ffmpeg use 5 seconds to detect all options or abord. First check, if your stream playable by ffmpeg with (use option `-an` or `-vn` to disable video or audio stream): + ``` -ffmpeg -i INPUT -an -f null - +$ ffmpeg -i INPUT -an -f null - ``` + Now you can see what going wrong. Following list could be help to solve your trouble: - `[rtsp @ ...] UDP timeout, retrying with TCP`: You need to set rtsp transport in config with: `input: -rtsp_transport tcp -i INPUT` From ee52d1b82fd36d12015de9909444a6002955025d Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Aug 2016 11:46:25 +0200 Subject: [PATCH 39/77] Other small changes --- source/_components/camera.ffmpeg.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 92920e10742..a9abd91d5d4 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -44,9 +44,9 @@ You can control the `image quality` with [`extra_arguments`](https://www.ffmpeg. ### {% linkable_title Troubleshooting %} -In most of case, ffmpeg autodetect all needed options to read a video/audio stream or file. But it is possible in rare cases that's needed to set a option to help ffmpeg. Default ffmpeg use 5 seconds to detect all options or abord. +In most of case, `ffmpeg` autodetect all needed options to read a video/audio stream or file. But it is possible in rare cases that's needed to set a option to help `ffmpeg`. Per default `ffmpeg` use 5 seconds to detect all options or abort. -First check, if your stream playable by ffmpeg with (use option `-an` or `-vn` to disable video or audio stream): +First check, if your stream playable by `ffmpeg` with (use option `-an` or `-vn` to disable video or audio stream): ``` $ ffmpeg -i INPUT -an -f null - @@ -54,6 +54,6 @@ $ ffmpeg -i INPUT -an -f null - Now you can see what going wrong. Following list could be help to solve your trouble: -- `[rtsp @ ...] UDP timeout, retrying with TCP`: You need to set rtsp transport in config with: `input: -rtsp_transport tcp -i INPUT` -- `[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size`: FFmpeg need more data or time for autodetect. You can set the 'analyzeduration' and/or 'probesize' option, play with this value. If you know the needed value you can set it to config with: `input: -analyzeduration xy -probesize xy tcp -i INPUT`. More info about that on [ffmpeg](https://www.ffmpeg.org/ffmpeg-formats.html#Description). +- `[rtsp @ ...] UDP timeout, retrying with TCP`: You need to set RTSP transport in the configuration with: `input: -rtsp_transport tcp -i INPUT` +- `[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size`: FFmpeg need more data or time for autodetect. You can set the `analyzeduration` and/or `probesize` option, play with this value. If you know the needed value you can set it with: `input: -analyzeduration xy -probesize xy tcp -i INPUT`. More information about that can be found on [FFmpeg](https://www.ffmpeg.org/ffmpeg-formats.html#Description). From ba42f8d77ca1e6c055e73b1a0a3056d469696014 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Aug 2016 14:57:51 +0200 Subject: [PATCH 40/77] Fix name --- source/_components/sensor.supervisord.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.supervisord.markdown b/source/_components/sensor.supervisord.markdown index d299fd8c175..57c545ddf3c 100644 --- a/source/_components/sensor.supervisord.markdown +++ b/source/_components/sensor.supervisord.markdown @@ -11,7 +11,7 @@ ha_category: System Monitor ha_release: "0.20" --- -The `supervisord` platform allows you to track the states of [Supervisor](http://supervisord.org/). +The `supervisord` platform allows you to track the states of [Supervisord](http://supervisord.org/). To use this sensor in your installation, add the following to your `configuration.yaml` file: From 322a5a88405fe603d4a5f19e7be7c3f308fc0302 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Aug 2016 16:13:18 +0200 Subject: [PATCH 41/77] Fix category --- source/_components/sensor.mhz19.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.mhz19.markdown b/source/_components/sensor.mhz19.markdown index 31ca4073856..15e05e8f87d 100644 --- a/source/_components/sensor.mhz19.markdown +++ b/source/_components/sensor.mhz19.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -ha_category: sensor +ha_category: Sensor ha_release: 0.27 --- From 4570ed9e57ffd3ff09e020942447c90b1d2634c2 Mon Sep 17 00:00:00 2001 From: John Arild Berentsen Date: Wed, 31 Aug 2016 19:40:36 +0200 Subject: [PATCH 42/77] wrong platform name in config --- source/_components/climate.generic_thermostat.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/climate.generic_thermostat.markdown b/source/_components/climate.generic_thermostat.markdown index 88cc8fb180c..bca038ff904 100644 --- a/source/_components/climate.generic_thermostat.markdown +++ b/source/_components/climate.generic_thermostat.markdown @@ -17,7 +17,7 @@ The `generic_thermostat` climate platform is a thermostat implemented in Home As ```yaml # Example configuration.yaml entry climate: - platform: heat_control + platform: generic_thermostat name: Study heater: switch.study_heater target_sensor: sensor.study_temperature From 0cb995e1db4a66ed6f04b6d7a91712caa5335374 Mon Sep 17 00:00:00 2001 From: Greg Dowling Date: Wed, 31 Aug 2016 20:08:23 +0100 Subject: [PATCH 43/77] Add entity_id example combining multiple sensors (#876) * Add entity_id example combining multiple sensors * Add raw/end raw to template --- .../binary_sensor.template.markdown | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown index 3feed08cf07..02cacfe1466 100644 --- a/source/_components/binary_sensor.template.markdown +++ b/source/_components/binary_sensor.template.markdown @@ -66,3 +66,29 @@ binary_sensor: value_template: {% raw %}"{{ states.switch.door.state == 'on' }}"{% endraw %} sensor_class: opening ``` + + +### {% linkable_title Combining multiple sensors, and using entity_id: %} + +This example combines multiple CO sensors into a single overall status. It also shows how to use `entity_id` + +```yaml +binary_sensor: + - platform: template + sensors: + co: + friendly_name: 'CO' + sensor_class: 'gas' + value_template: {% raw %}>- + {%- if is_state("sensor.bedroom_co_status", "Ok") + and is_state("sensor.kitchen_co_status", "Ok") + and is_state("sensor.wardrobe_co_status", "Ok") -%} + Off + {%- else -%} + On + {%- endif %}{% endraw %} + entity_id: + - sensor.bedroom_co_status + - sensor.kitchen_co_status + - sensor.wardrobe_co_status +``` From c9475b300f9143134b5134f6996a7066fb10ce01 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Aug 2016 23:09:36 +0200 Subject: [PATCH 44/77] Add details about the permissions --- source/_components/downloader.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/downloader.markdown b/source/_components/downloader.markdown index 4f8ac43e405..e77b2308d57 100644 --- a/source/_components/downloader.markdown +++ b/source/_components/downloader.markdown @@ -12,7 +12,7 @@ ha_category: Downloading ha_release: pre 0.7 --- -The `downloader` component provides a service to download files. It will raise an error and not continue to set itself up when the download directory does not exist. +The `downloader` component provides a service to download files. It will raise an error and not continue to set itself up when the download directory does not exist. The directory needs to be writable for the user that is running Home Assistant. To enable it, add the following lines to your `configuration.yaml` file: From f7d0ee4c6223700cd1ed488172fd4651bc150fc5 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 07:09:59 +0200 Subject: [PATCH 45/77] Add detaisl about trail limit --- source/_components/notify.nma.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_components/notify.nma.markdown b/source/_components/notify.nma.markdown index 7c548f7fb96..2ac305f971d 100644 --- a/source/_components/notify.nma.markdown +++ b/source/_components/notify.nma.markdown @@ -13,7 +13,9 @@ ha_release: pre 0.7 --- -The nma platform uses [Notify My Android (NMA)](http://www.notifymyandroid.com/) to delivery notifications from Home Assistant to your Android device. +The `nma` platform uses [Notify My Android (NMA)](http://www.notifymyandroid.com/) to delivery notifications from Home Assistant to your Android device. + +Go to the [NMA website](https://www.notifymyandroid.com) and create a new API key. If you are using the trial offer then keep in mind that your limit is five (5) message per day. To add NMA to your installation, add the following to your `configuration.yaml` file: @@ -28,8 +30,8 @@ notify: Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. -- **api_key** (*Required*): Enter the API key for NMA. Go to https://www.notifymyandroid.com and create a new API key. +- **api_key** (*Required*): Enter the API key for NMA. -Details for the API : https://www.notifymyandroid.com/api.jsp +Details for the (API)[https://www.notifymyandroid.com/api.jsp]. To use notifications, please see the [getting started with automation page](/getting-started/automation/). From 41fdcaff5cab258b87e48b6742a9a643c0458373 Mon Sep 17 00:00:00 2001 From: lee-js Date: Thu, 1 Sep 2016 13:57:29 +0100 Subject: [PATCH 46/77] Update track_battery_level.markdown (#878) --- source/_cookbook/track_battery_level.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/_cookbook/track_battery_level.markdown b/source/_cookbook/track_battery_level.markdown index 3c995af7d7c..f7722a639dd 100644 --- a/source/_cookbook/track_battery_level.markdown +++ b/source/_cookbook/track_battery_level.markdown @@ -10,7 +10,9 @@ footer: true ha_category: Automation Examples --- -The [iCloud](/components/device_tracker.icloud/) is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/components/sensor.template/). +iOS Devices + +If you have a device running iOS (iPhone, iPad, etc), The [iCloud](/components/device_tracker.icloud/) is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/components/sensor.template/). ```yaml - platform: template @@ -27,6 +29,8 @@ The [iCloud](/components/device_tracker.icloud/) is gathering various details ab The `else` part is used to have the sensor keep it's last state if the newest [iCloud](/components/device_tracker.icloud/) update doesn't have any battery state in it (which happens sometimes). Otherwise the sensor will be blank. +Android and iOS Devices + While running the [Owntracks](/components/device_tracker.owntracks/) device tracker you can retrieve the battery level with a MQTT sensor. ```yaml From f1b4cc449339fd37f78e938ccc221fed49da282e Mon Sep 17 00:00:00 2001 From: Tomek985 Date: Thu, 1 Sep 2016 08:58:01 -0400 Subject: [PATCH 47/77] Added required dependency (#877) * Added required dependency Since release 0.27.1 it became mandatory to define apcupsd and associated server and port. Missing configuration was not caught by validation script and it prevented all other sensors from loading. See more here: https://community.home-assistant.io/t/0-27-1-broke-customize * Updated per review Followed @Landrash advise for cleaner approach --- source/_components/sensor.apcupsd.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.apcupsd.markdown b/source/_components/sensor.apcupsd.markdown index 1e46ca35e97..eec87c03dae 100644 --- a/source/_components/sensor.apcupsd.markdown +++ b/source/_components/sensor.apcupsd.markdown @@ -11,9 +11,9 @@ logo: apcupsd.png ha_category: Sensor --- -The `apcupsd` sensor platform to allow you to monitor a UPS (battery backup) by using data from the [apcaccess](http://linux.die.net/man/8/apcaccess) command. +The `apcupsd` sensor platform allows you to monitor a UPS (battery backup) by using data from the [apcaccess](http://linux.die.net/man/8/apcaccess) command. -To add this platform to your installation, add the following to your `configuration.yaml` file: +To use this sensor platform, you first have to set up [apcupsd](https://home-assistant.io/components/apcupsd/) and add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry From ea3318261a1b09a7e9a8c30d3ceddc8a3187402a Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 07:13:11 +0200 Subject: [PATCH 48/77] Fix description --- source/_components/notify.nma.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.nma.markdown b/source/_components/notify.nma.markdown index 2ac305f971d..1108d3f2b87 100644 --- a/source/_components/notify.nma.markdown +++ b/source/_components/notify.nma.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Notify My Android" -description: "Instructions how to add user notifications to Home Assistant." +description: "Instructions how to add NMA notifications to Home Assistant." date: 2015-05-01 18:00 sidebar: true comments: false From 6af5ee24c5c3670950b8fca35e272b70fbe7ea9d Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 07:17:03 +0200 Subject: [PATCH 49/77] Move key details up --- source/_components/notify.pushover.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_components/notify.pushover.markdown b/source/_components/notify.pushover.markdown index bd447ea4823..20a7ca49131 100644 --- a/source/_components/notify.pushover.markdown +++ b/source/_components/notify.pushover.markdown @@ -15,6 +15,8 @@ ha_release: pre 0.7 The [Pushover service](https://pushover.net/) is a platform for the notify component. This allows components to send messages to the user using Pushover. +In order to get an API key you need to go to the [Pushover website](https://pushover.net) and register a new application. From the website you can also retrieve your user key. + To use Pushover notifications, add the following to your `configuration.yaml` file: ```yaml @@ -29,8 +31,8 @@ notify: Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. -- **api_key** (*Required*): This parameter is optional but should be configured, in order to get an API key you should go to https://pushover.net and register a new application. -- **user_key** (*Required*): To retrieve this value log into your account at https://pushover.net +- **api_key** (*Required*): Your API key. +- **user_key** (*Required*): Your user key for Pushover. This is a quote from the Pushover website regarding free/open source apps: @@ -39,3 +41,5 @@ This is a quote from the Pushover website regarding free/open source apps: When setting up the application you can use this [icon](https://home-assistant.io/images/favicon-192x192.png). + +To use notifications, please see the [getting started with automation page](/getting-started/automation/). From b260bf012d156586ab5fc5f2c6e0e4097ecdd0a1 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 07:22:24 +0200 Subject: [PATCH 50/77] Fix links --- source/_components/notify.pushetta.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/source/_components/notify.pushetta.markdown b/source/_components/notify.pushetta.markdown index 9374e7e0409..8b3a68c818a 100644 --- a/source/_components/notify.pushetta.markdown +++ b/source/_components/notify.pushetta.markdown @@ -9,10 +9,13 @@ sharing: true footer: true logo: pushetta.png ha_category: Notifications +ha_release: pre 0.7 --- -The pushetta platform uses [Pushetta](http://www.pushetta.com) to delivery notifications from Home Assistant to your devices. +The `pushetta` notify platform uses [Pushetta](http://www.pushetta.com) to delivery notifications from Home Assistant to your devices. + +To retrieve the API token, log into your account at (http://www.pushetta.com)[http://www.pushetta.com] and go to your **Dashboard**. Create a new channel by clicking on **Channels** and then **Add a Channel**. To enable Pushetta notifications in your installation, add the following to your `configuration.yaml` file: @@ -31,8 +34,6 @@ Configuration variables: - **api_key** (*Required*): Your API key for Pushetta. - **channel_name** (*Required*): The name of your channel. -To retrieve the API token, log into your account at http://www.pushetta.com and go to your **Dashboard**. Create a new channel by clicking on **Channels** and then **Add a Channel**. - It's easy to test your Pushetta setup outside of Home Assistant. Assuming you have a channel *home-assistant*, just fire a request and check the channel page in the dashboard for a new message. ```bash From efc1f70221102db44ffd76094a63272177cfebd2 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 07:22:39 +0200 Subject: [PATCH 51/77] Fix format --- source/_components/notify.instapush.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.instapush.markdown b/source/_components/notify.instapush.markdown index 4324d8da89c..fb027e59e0a 100644 --- a/source/_components/notify.instapush.markdown +++ b/source/_components/notify.instapush.markdown @@ -38,7 +38,7 @@ Configuration variables: - **event** (*Required*): The event - **tracker** (*Required*): The name of tracker inside Instapush. -To retrieve those values for existing settings, log into your account at [https://instapush.im](https://instapush.im) and go to your **Dashboard**. Then click **APPS** tab, choose an app, and check the **Basic Info** section. The *Application ID* is the ``api_key`` and ``app_secret`` is the *Application Secret*. +To retrieve the needed values for existing settings, log into your account at [https://instapush.im](https://instapush.im) and go to your **Dashboard**. Then click the **APPS** tab, choose an app, and check the **Basic Info** section. The *Application ID* is the `api_key` and `app_secret` is the *Application Secret*. Assuming that your setup looks look in the image below... From f6524bbc52759cbcc1411cacaab7f6ab7bb48ca8 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 10:11:15 +0200 Subject: [PATCH 52/77] Add IoT class --- source/_components/binary_sensor.command_line.markdown | 3 ++- source/_components/cover.command_line.markdown | 1 + source/_components/sensor.command_line.markdown | 3 ++- source/_components/switch.command_line.markdown | 3 ++- 4 files changed, 7 insertions(+), 3 deletions(-) diff --git a/source/_components/binary_sensor.command_line.markdown b/source/_components/binary_sensor.command_line.markdown index 56de407e4d9..26b613f4489 100644 --- a/source/_components/binary_sensor.command_line.markdown +++ b/source/_components/binary_sensor.command_line.markdown @@ -10,10 +10,11 @@ footer: true logo: command_line.png ha_category: Binary Sensor ha_release: 0.12 +ha_iot_class: "Local Polling" --- -The `command` binary sensor platform issues specific commands to get data. +The `command_line` binary sensor platform issues specific commands to get data. To use your Command binary sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/cover.command_line.markdown b/source/_components/cover.command_line.markdown index 63452cc16be..5c5826abe12 100644 --- a/source/_components/cover.command_line.markdown +++ b/source/_components/cover.command_line.markdown @@ -10,6 +10,7 @@ footer: true logo: command_line.png ha_category: Cover ha_release: 0.14 +ha_iot_class: "Local Polling" --- A `command_line`cover platform that issues specific commands when it is moved up, down and stopped. It allows anyone to integrate any type of cover into Home Assistant that can be controlled from the command line. diff --git a/source/_components/sensor.command_line.markdown b/source/_components/sensor.command_line.markdown index 8c516c37605..814ab0461c9 100644 --- a/source/_components/sensor.command_line.markdown +++ b/source/_components/sensor.command_line.markdown @@ -10,10 +10,11 @@ footer: true logo: command_line.png ha_category: Sensor ha_release: pre 0.7 +ha_iot_class: "Local Polling" --- -A sensor platform that issues specific commands to get data. This might become our most powerful platform as it allows anyone to integrate any type of sensor into Home Assistant that can get data from the command line. +The `command_line` sensor platform that issues specific commands to get data. This might become our most powerful platform as it allows anyone to integrate any type of sensor into Home Assistant that can get data from the command line. To enable it, add the following lines to your `configuration.yaml`: diff --git a/source/_components/switch.command_line.markdown b/source/_components/switch.command_line.markdown index d45f734179c..44994d84f14 100644 --- a/source/_components/switch.command_line.markdown +++ b/source/_components/switch.command_line.markdown @@ -10,10 +10,11 @@ footer: true logo: command_line.png ha_category: Switch ha_release: pre 0.7 +ha_iot_class: "Local Polling" --- -A switch platform that issues specific commands when it is turned on and off. This might very well become our most powerful platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts! +The `command_line` switch platform issues specific commands when it is turned on and off. This might very well become our most powerful platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts! To enable it, add the following lines to your `configuration.yaml`: From aa31566b35a5ff7cf532bd2f3e0166dda39914d6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 10:14:06 +0200 Subject: [PATCH 53/77] Minor changes --- source/_components/binary_sensor.bloomsky.markdown | 9 +++++++++ source/_components/bloomsky.markdown | 8 ++++++-- source/_components/sensor.bloomsky.markdown | 4 +++- 3 files changed, 18 insertions(+), 3 deletions(-) diff --git a/source/_components/binary_sensor.bloomsky.markdown b/source/_components/binary_sensor.bloomsky.markdown index ba3b32a98fa..2a4ba02d575 100644 --- a/source/_components/binary_sensor.bloomsky.markdown +++ b/source/_components/binary_sensor.bloomsky.markdown @@ -10,6 +10,7 @@ footer: true logo: bloomsky.png ha_category: Binary Sensor ha_release: 0.14 +ha_iot_class: "Cloud Polling" --- The `bloomsky` binary sensor platform allows you to get data from your BloomSky device. @@ -22,5 +23,13 @@ To use your BloomSky binary sensor in your installation, add the following to yo # Example configuration.yaml entry binary_sensor: - platform: bloomsky + monitored_conditions: + - Night + - Rain ``` +Configuration variables: + +- **monitored_conditions** array (*Required*): The sensors that you wish to monitor on all of your devices. Select from these options: + - Night + - Rain diff --git a/source/_components/bloomsky.markdown b/source/_components/bloomsky.markdown index 7b326baf8a4..c34d8a75931 100644 --- a/source/_components/bloomsky.markdown +++ b/source/_components/bloomsky.markdown @@ -9,10 +9,14 @@ sharing: true footer: true logo: bloomsky.png ha_category: Hub +ha_release: 0.14 +ha_iot_class: "Cloud Polling" --- -The `bloomsky` component allows you to access your [BloomSky](http://www.insteon.com/) weather station's [sensors](/components/sensor.bloomsky) and [camera](/components/camera.bloomsky) from Home Assistant. +The `bloomsky` component allows you to access your [BloomSky](https://www.bloomsky.com/) weather station's [sensors](/components/sensor.bloomsky), [binary sensors](/components/binary_sensor.bloomsky), and [camera](/components/camera.bloomsky) from Home Assistant. + +Obtain your PI key from your [BloomSky dashboard](https://dashboard.bloomsky.com). Click `developers` in the bottom left of the screen. To integrate your BloomSky hub with Home Assistant, add the following section to your `configuration.yaml` file: @@ -24,4 +28,4 @@ bloomsky: Configuration variables: -- **api_key** *Required*: Your BloomSky API key, obtained from your [BloomSky dashboard](https://dashboard.bloomsky.com) (click `developers` in the bottom left of the screen) +- **api_key** (*Required*): Your BloomSky API key. diff --git a/source/_components/sensor.bloomsky.markdown b/source/_components/sensor.bloomsky.markdown index 07c28221aa6..d085060f349 100644 --- a/source/_components/sensor.bloomsky.markdown +++ b/source/_components/sensor.bloomsky.markdown @@ -9,6 +9,8 @@ sharing: true footer: true logo: bloomsky.png ha_category: Sensor +ha_release: 0.14 +ha_iot_class: "Cloud Polling" --- @@ -33,7 +35,7 @@ sensor: Configuration variables: -- **monitored_conditions** array *Required*: The sensors that you wish to monitor on all of your devices. Select from these options: +- **monitored_conditions** array (*Required*): The sensors that you wish to monitor on all of your devices. Select from these options: - Humidity - Luminance - Night From 1e005ed65118dd9984f32c48e53efcedf5eb5572 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 17:19:20 +0200 Subject: [PATCH 54/77] Fix configuration sample --- source/_components/feedreader.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/feedreader.markdown b/source/_components/feedreader.markdown index 70e0718c481..099474692a4 100644 --- a/source/_components/feedreader.markdown +++ b/source/_components/feedreader.markdown @@ -20,8 +20,8 @@ To use RSS feeds in your installation, add the following to your `configuration. # Example configuration.yaml entry feedreader: urls: - - https://home-assistant.io/atom.xml - - https://github.com/blog.atom + - https://home-assistant.io/atom.xml + - https://github.com/blog.atom ``` Configuration variables: From aa1dad70cf2bbaec488a5405cad7b3263bc691a2 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 18:31:08 +0200 Subject: [PATCH 55/77] Add missing variable --- source/_components/binary_sensor.nest.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/binary_sensor.nest.markdown b/source/_components/binary_sensor.nest.markdown index 80bd603b05e..d7c74a38341 100644 --- a/source/_components/binary_sensor.nest.markdown +++ b/source/_components/binary_sensor.nest.markdown @@ -34,6 +34,7 @@ binary_sensor: Configuration variables: +- **scan_interval** (*Optional*): Interval in seconds to scan. - **monitored_conditions** array (*Required*): States to monitor. - 'fan' - 'hvac_ac_state' From 4d5a2197cc7a8172044c97f085f7e7ff622175bf Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 18:33:01 +0200 Subject: [PATCH 56/77] Remove half frame --- .../screenshots/nest-thermostat-card.png | Bin 9376 -> 10402 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/source/images/screenshots/nest-thermostat-card.png b/source/images/screenshots/nest-thermostat-card.png index 27a0b8316e909d22ff23d22a28a01ee919ce2a3e..e5a9fc8b166141134c1a230c6bf7379ccc006f6f 100644 GIT binary patch literal 10402 zcmZX4cRbbYAGhwi8_CKJp|Y~~$jZnjD`b!Cy+_7flF%V!WrdK04w=UY>BKRTjALeJ zJ0Y9rbGm=eAJ6M~^{S5JJFn|=z1Qc8)zeiYBVi;VARr*qP**V^Ao$A{KI;(^!oN8~ z84uwqPc7Cna$YD=Iymf zt2J%UWLyPT*Xz+-DHbPc6D*Ih5x0JHGB+KP{{15Y4a!vK&FJ)}+{siN`klWHdVUfH z|GT7k^N^S z{`2b~ZGNwZ_ybr}E?&IY)7LkP3nq?MB5)RCe5QKcu{!hh>(^QGYEsOO5fQn1+$yfF zJfY2}X%$yl5=A8?V=xPLwzdynyrB6uIH;kkYlYi)7K=mA*?M{=++w@MN2gqBl>Fj_ zikTUsYT>1t(39Ep^V0Z-lJ#C(T51T!UCWC+l`grH=jiL33}+6x7UkzZ3_tpf^ca`W z=A5FgC1z$`e)8mrv!|zHU|<@(byyPoWZsytyzFwik5>4Fb;_FwMBU)$ zUsy=DE=D4K?s1b6M(ynG`s{DnCR~wGwYFxBXk~4-x?^j5RVHZT{z!%8i}dtL#`9jO zN+f?>gom0{q#`9e*q=*0$U8e=<>cgik98k)uT^>fG9%-oyTmrd*%rmxbZg!Vc%gs& zP?J*34Mhy;TanCzqt+K`X;lHM#sp#VteY)I0)655=bce+y| zCMh}i{kuv?$N_&PHs#MMcuHg}#@M;Eos^y3GhA-og~6ByYU}G?x_tSvMRRB>RIV(G zTE3o*5JNDolRjjRb@$W@sptG@bsXmkeK#%B{MTKC>EGw zt^}0t0?CytSKb)${9eN<>*(~xElo5A@ZP<9*FP}OcX#D36c)FDK-zx~5`z})msJi4 zkxorbeO*+MRb zm~`ui%$1duPr@dZRu1m&&#J0K;^N~6Tx-e*JDxltgfdju(z?!wn8NL9{8{dw{)U&R z4p<%j)L6HAyHLNev5|q5wWO(u88sPUQi+BlpJP4C_?w9Q$KDartegSynd7==N=iyk zZ!gjTL)YWDO_sMAO>gxB{+hP#X|;&pL1e!erf}xxK%rEQZtjB(X-!SdjYH{FO^(dW zOx~$F)0O+k&l6^@0Y)>P{QG1C`;tA&pYGQ@aAH5_V)Jn zzmTS+HD(B?=l?*% zN1rJ8>C?0HTin_ey^n`pqhF8c8@{-0s3V`5Mstux0@z@eX(RLnX^-At_lm^y^pI9I z|7Ju5ZR+~_)lbu5a)0{Y1U$QN{x3<{sX5$_-OvGNu?+2EnT?J2o{9oA317cScXO3g zeiIhE%|>H|lZqLP>R3MaBY2#$^>|G-`nOoFC%1!|$2sE^tCkx42-(28taj@ERc3t> zH!z@Y6|z7}&Mf6UJ<@3@$i+oejqUmJg?Mmqu#AO15iK3IFBC(;T3la`pE_BFfccwG ziuXHA*0VQREX6-gauZlx$z5F85>pf0+5Xn&%E;sUbye&a86DiIrRZ7`v4@98)5-7g zo!`HIebW-eHE)I|zI*qMXu}MH!F2WY6<1fMDNkrV+){|}dy#j76C+>B4vUYbRC?-_?<}Sn6eQ`@ zdLpsDzP>hzN@qR(K{UU(DF1xK+|W?j!-Jn7hWyIxM1$Y?s5TDt`M=KTW=koWn9z51 zb$uTmuF&FcUcV&0^e&Mi!E)y7fxPVL*T$Bs*4e9_Gdo*jQ-l(!_q!y`@Fhui`O1}r z^wwhzbRuiX+qZEZsZcr8;$krt6Q0qfq7UcS>ouq05vo%qL#p%-_Vc=_yTMMXm!@G zf-Eg9Jzi}+<-MbDvJ>9C$ZuY|)xmoD+?4Ngkyd)W_sn1S?%n&j8w#lBS;v&4i~hYn z9X^5)GO)Aa2r-{%*juZQiY2kO>PR5G@&bg#*_7QWQsxF>0`IxH{MN$>PPYI6DG zIc?SzXuv1}-bqPMM|0(cDQRh46crT>Zngqi z!G3U|*3r>f8?Q@jYHA87lPdvrf-?{KC}V9k-!XTESGQ!bIBUPnFl!Wv{E;TX`+-6i z*OyN3vVO%{m{}fG^ddcPOud4CH-G<;Ra0=1_1WQwe?S1zYg*nabh+s6QdhH;pu!Qh zUn+Em8;>C&Gtusk6hK~IN(F)Re=+iaeLNCAjx)Go5x zOjDhIIj$xZ;t#|u&-mag4KrHC-IYRZv;bMv)oImY>{He9FmCyYnHk#(tLEK$UArN4~w+uV2rW4N2DH{zQF8R?)?!^!NoHHOhn- zNEt|L9>!)m>u6`kh)VVk^2|J??lO_6Nli(p_y62c z-cw9OAaKhidEc;D4L-UDHkE$P&QB@i_y5JyO~2B6nAH_e(KDpt63!>{1#sWf(kPI3oWsqe3nbCM=UdU3DdL7YMingzg-}y z?xD~@NJlF@)GR81!tCzW^!4*YV%_U@Es&wi*Yda#TB8 z)Obft?W}Ra;r0UZGJ_qlwO1|9>M|8e^bM2Jbv=AI%jM?$Np<)y_*8CAKGH3mZSF{4 zz8t_G(lR_HERpIcC&tA3!HmD5p#jJU*Tt2mXJys5F^TeO2%4CfVD9MXfFcpTc{9$S z^!1xJPvhc9;8oITIi7Xe_4M?7ou0k}FhWgD&7G?G>(?(>KCj-trz{+J3WtL_IX#U4 z6_JsZ)v>uZI5yS|90auvKu{sY!T0B7*uU%|8Zx~51yRivd|6}%%b4Nv==MwU(&4ET zi9tfkzXed6zGvstkGRq%S{P;nJ$aN0jlZpDd={2dW7`=Kw+%1!6Pt=uy9am`{52aV@Zm1;y>lU8wSi!qDJqo6Nya&n#_ z5FEv(d7&$%S-QyD4Ki)UBqF5L$I(L(>#B=!?5H~|}Mcv!3SJwyK+3wYexjkvu zzc%nwdG{(TI9$$VSPU?ku$b53nr{HNoh5Agn;CpbciI|4%?N z=H~HT_uGMq!SsRhU*J*(1`lR>&-mYZm^EcZ~W+^Agk0zdR zUdulg$_@La0WKmKjMo0o!bEO<{-TNs&rW+MCnwxN7{T#Df8-))Q%u4I!YDuj8;Pt7 z(Jc{?<;J{6dzKtHI@sjzJw7?3yR{N=SM&QpqF-CLOnDX!)TOE}vv9&_uT3>)J$!hMoK;?1SC`ys^B3Z}hK2@M z_wTOaUQIYc!KSVDxA`EH*@sd5bi2KMeTzdT)(c)|zr8LqF%_1VBka)$KELKQrXr3! zXh{C4Y&l$c8Q71fuG!Q2b(Q(-UExjZn~0ZgqPBI6`qOq_yD{pWFB`*Dy8JF?@v(4% zXc4<3i#reK4{^qYmZr*1Wec7jhQ!zRS5+hFwfbj{w$3}xMNJ+jgmv_e;P-^s&+!mD;Vp#?6 zYSIY@T#VM<@W1Bc3U_(B9i5Sl6S(Mm6G5`8+!Ba^GKxHlsCCD-Z*2*I+vFu|0AB>! zr9?NUpr%F~NlxCv5|WjZQ&dxvdU|@Q!c+mP7AJW2OYj&_N@l4)kBjPHRh6pTIKJ2M zItNEIyo1#7$evY^LB1aMQ6VBhm3Pg64Z_ZjrqP>wey7JFK%v~++_x%6=Dejca&kCiWU|2AL5&k+ zNqE>zw}j)V8;54~gOURXAYfo%__(yKZ*2S-TyRSL6*dKhJa{t!tEMl45x9%;2lLe6 zdOkkdlJlAr6D>W|OO}`YH*;K)A8emJ9I7DZoB^p*Zy#w(Q zGdU3>;t87N!Lx#b0@_62ruO?Hmx#~nl^V(Z`f}aK*jQlM!_3GCq6BHz8pgc-81!7* z>aHE61Umz22VHj}l%U=Uv>t<`C@6RYu>iy_)&(y#V9-GjH{m`r;jg1b@)s8eM-nU% zHcEK=O9<5)f`VXCT)PrX;RTf@Wa9P_V?-8(4dIWcBL+14-?(+Hb71Krj&u0MUMx-c zK1B^zn`?#~lp=nLx&F_Gm>Qez*T|8D?IF9pdY?{|{|c6^w-A`cNzujs14gIA%sYPd zr$t4j!r;!1zc%L}nO4GMrK{PxTuJJW;Twp`+#i8ti+Rz%be)p;)sU+&1F3=aP8RdL z(hRZJNkeqMd1%@{?;1s90?U#x;nW~q>DDKV)Sa((7oEmBWHE#DICc(_yZes_0&+$> z54bg?G_BKjKoZg&9d4$Zm2*l>DYdAKNv!B)q@f&Mq2sm{G!fzj47JfcH%0x79Cq{JwaxZ&(dwg0` zdf&S;s=j~89#mUPi#&vEkdW!{U22@NyH}x=E&y5}7PD}TE*yfgzyB9PK{>e` zGA0SVyLWFJ8xNC3{j|K`OAz3I-AQQ7%)rfB*^gK3z8~u|h61vy(N6+_n7|^Z35pjg z`j7E(v%9|pDIEasHh2_06O+AiQa^$8c<}WQmjIW<@(}Ks%d((XcSS@+JAV9N191c_ zPEAS(@t8dXc4hK`{{Anbh$uvag#K-_VUv+z0^=~Ux&Xih2X6O>_UjoM`V9&}=GWlA zOa(xScB}>msRS~mx3?FJ5QnV@GdZ3#ldh|IOEH731#EDwdFd_n46Xw@ub{3j-4YcD zh){c<|4Byd+S1wNov4Gaw4R8*V}m!HeZ&0So>RzsP&ON{?bJ+G8c35R9N zhra~7k zp;<7%U07K7y14k)e9E2VyuAKQQ75T@6&itb-b?ea4!|5T%ZD+^CLaYu}igPEK?r@~#o6iUfK7Zp$g{y*{oHg^TRpo;+S5QcVB(e42lU%$QvY6?V_H3Agi>umaP8AFzXw26oB{4uZ0hxBq<+QoAVt?ZurbgbUnTz3d zmVz6OS2t>!$=rFmlBYHC>bz$TCj@kSzrq1i!8OABgIg&;dC%O0?(WKaVJ7_ew<&D~vs34~oN+oeP_ zbsIaZyk@Js;HiUy5HN_~!5|Fg(s!{53u7)BjP00F=j&!=W@e{~eV&=A;pn&+Hy8mW z;3H5r6gTOqR$@LT;RpR0xG79AJgzAp9W)Y_*Vfp@#Z%wD8x>+EF5x$``dz`U0ig89?}+Q6Ck#wX_JM)F6Wowfzm2b$zkE2dC;r?)V+O(@jBCqe zY^MRcNDdEhy)hy&QB+1I9wZLDb4u5T6(l^bk&)5+_wS!GaQHS@FiZPB&d(8^Yv;buz4=~p6 z$JZgRhv&TztppRElA0Qgb?2lZ@qxG=0?4-g{a`zGei{;vmGI%AAprAa21}XnLouiR z+=T%(*4z1dUk3-3g&4Hm>Ao)ei;0UP!;b=CMgc-UeE7ir=ngn=z?=`YwcnrG0(3=e-UH7w!g;j!D>n1tqmpfo;dy{?u3{EKakRG^EG21V@+(7;EhRlxfd@zcN2 zp&vzuFNGVUAWOv_T zrUQ;C+kggJ4KR=hbne=0)Yl4H1Qp3!avj5GaIQSRJdS5ZX$AZfrv@4u0Bo$r?&&Ds zPWT=NjY1#u#l=NPMgioeKG=k~xZD5?TMa!0Q~)i=nGy>UdnYv9?z`u}$BzWicmYiT zk~FnrRwFl_Jv88bS=OVR3-?1Wybc3q1Gs?OWi!mgQA*QZ)#`z$${| zqI!s3_Mi1_(Br0o{GGEnj){>G?C{J@srIU$$q9oCebh0GM8E5G_^a28QlPQTH zx5LKZa642aId&lRA2BXV?uI+98NOlU`5 z>FDZm4x2@HC<>88!8U?J{9XWCPA;zWXd~!lfmK-A=6`_Tm8(?Bzg0F=U|dFx(%3YL zh>%}iUe+o$nZrrV&CS8%=v!Og2|a8UoMlZ!XJ%)=uC5lQ0M2e7JngiL{l;0x z=s$e@2drhgYAh5-?DEhpwtokgwI?F0$;g5_fbt-ocm=}Y+cyJzt^%wHO;>Od39Jgb zZfu9elG;e-Xu!O$Y?1mcT^?w@5Nyj+E;fCjEp|aKK(H(U<;CWeEsw4ZUttnxpQ-3 z)^AE(O^pcT=l%QlzkdDtZ?7Y&&`)dI;Ln^qdq&#h=vQ#75u>fbGUby z!<&B^r7S$Kr31hL_I7~105`xDHzyFMat$a$NJ>gwh{57pn=RB43>s{+xW)FKof~F9 zOn%z3;Wv;s=pF!pSU1!#1mvJ=Aw9iBG8tl0)cG}3X2z&wFbPN%HhaKJ+TOqa7?cZW zf^@{cs@E=o&1tjQs;IaM$?)yU5m7lg1ZKfZ#O!h++UI5tEKN|foGC8%frMN+#LEsOa~1uZT^5W z^qb(JAxUOnWNi1WGt}2l%7_!q)CQpgC_~G4MDsTfvq?99UTjdcp&zFmXP4P^8E&wbl5xqtX-j{1C9s~ljSB%VsSAiDEi6C z$*^M_I`*_UU+-x{gEZ()i7Z5pOb}G;&WOS@S8-64FiZHv7&b$2ef#zeMyIF0zi@E* ztFxHf%1}rd_>NJ?ilIeTQ6V6Ix^EAr?8c27!Llp>6rg9^r<$bo-S>1&%Z)`uL>O3D z7Dtix7SNf4JqC=7jKgAbji!PXm6a6b##+E@s)asSpSm#^0PK1o5IgSZBsPIAp8q?v z;h-Y`2ml%Hhy!}1CN3_{+1;HTb`rrDgX4rgB&>lZD?#}@3WTaMNChx8kSGU8SN^xe zi=YG{TUWEPVu39dfR&d>2|>)=cW_98=~Px$F4$bI>BeAUJMFUN9;87e1_~D%4zsg% z5}p%Zz`a384x1WO7)+T@8fpjIc0r_Ju~^gc;k!X!V4YPz*z*KQ0TT&BG#7}1gc5f9 z=m8=_7uL>95B7v0O{q8(jK@at0S<(&j@2Pu+|R+r08i_2!v+I&ZKOa8XG+(Lj15bd z9rYpu+iENn55U9o+}svBDYHa6OOP4w-tm1fTPKs`#_MCSZ~_+fA7RIhor$l30Tlq) z_n{&Fkh9@<0ISAE#`wJ)>YWi_?mx?@QV09PY!u34`_k^C)@K-Q(`vS!V z4mHEDL>IsB3Umi@R(CvDwhy*qSb7ZvGy_S1k6}bW)U`2oR0pZ}CS^mbBGDlzc)OQbsOjY+Kba+1-~h&jMm(S^?$uayH@go6l+Vx4 z%eblqa{1q!lnd$oZ^IDMamJegLL)ZHS4Bn9u<-#Vv#Y1)h2&DiG1u+?HnzPR0ztsf z&%d*?^8*(QEr!Cz#>18!W7_{N;d8Nl#=GEwBGkxutw&)~({am(d8#U`BIG@kb>MZ+ z)s5@0Q^8iH!jaXHnrAWp+Zcx{XX9^#_aMH?{srHy|Nl17{kL(A`0D?=f$slqtNY(c ePapg^`@5%@$Z@OI^cQ}spvG-ol?o-BNB;*@m|v{` literal 9376 zcmY*zwC#-}il8*L~gZC^eObSBdF}5eURp1$h|_1OhJvo@)@{!TEjY zEoXSR>?W`8i9nEkJ^#Cq#6?OEZ(j0JP?o(kMMyw;TU5iQHUi#awAa$}l6G}=ws!G? zmk5NkhqbwvwH1qxy_X%!Lj`3uE0pym1cC*jAS0>eJF+^iuSGvUEVA)Wv0ddOdAo~I zj9)Ft3FsSeDvf<{mh1=Y%7G)8O7?sjXH}kn`R(!DEN7Py%$qc1e$47Mobt%XW+JWS zQ)k{GZW{^~og0@!U;aeJ+8|GOCIX{b8_Y-!+_sKUwsP6#$j#1eRCkQ|`9=M8nWl}% z)wo?t0WUuJL|mvjfA`746*xcGxp@9U#`OH0#dCgUIXqtp@}LWFe);XGAv~CQM&o8A zGI+>|ULvE+X|Y|@#NiqR0_^Pb<~*4koU|l~$lKI0m!JBs80Ki)Zk}A<^!>eA`+((p zSJ&*OuRab*8TEi=YX2y^$Br+>ikJ4@y?c~VG8|MN^c+dD|NA8;xzA>0&CO@+NnFOp z##gRfiIR~*C1bnhS|Z7W1qGvISQ&7=m)J3FZXyj04dP;Aqr=0C+XpIXBIZI^<|EXj zM~^as_J(IWk{eB2-Q72rOPeRg#?t<&wk#j|^T*23(J>(42%aD*ZxDSk<6Rl4a$KKi z%+1Z^%HDP0y-OnYc!?^o6K+)~UXR=RU~3kAvZ&hF*cd1=X(#Yr>%FhIgowz{`1qX! z`4@6GBU>ch2WK|*iU*blOG7q3Ut$j0=~*4Eac6LKaA@!D4srT@R2p)!j8T>7S>C;R z^{S?(rcPm1S(#d~PBy-L;>yy};SBSc?`-?^)I4p@B)RPA?E{n2{kblzrKP1ql|gn- z(GC2FF&cR={9`>?d;@pH5#{nh*ecp&HqS0nn$16R}3#L zFRME-(bD>^H|`T&xY%^BBw53lZd&i^RhilvMqz_dX&OuG#&?2T)w-Fxxs^3Foenmi zJ~lRH9JxgqMam>DPyV%jy$Rwz{Ogy7fx*XA37h9l=MgKFVWl9A^bFJ)gm1o61;2AAxW;St!?`w?OxDfQvf%*@P$1PV5c-^SGE_wU~q^$H0I>FDSfaK9=qznk2lt*1xSa~_roX9x@A z&-LrqDWi~{V#>Xcu^d#y1bBpDq2{z1-IE`zJ5nbXer8H%sx8FuG?f_?8x-&D4w?$5 zDA^4T4ZZGNS-D5s;RSFdr=Q4tpv z6-A>>4GdD5Xm|h3(OBdO-i)!t#mTZ#)ES|uhWpC3@)A- z-Sn-QLc#_Xsry-7T^&TPW;AGLp(iUVYghD6*yryZ9UUXj^LR5AKE=N_Y1k7EkG}@@ zHaEZPk3Ri7Q}44rFgUnAR;P(dc3l|l5nznRVcL)}trmPK|5fer6hWAz)-`Ev>gKI> zuB4wWh~S9n<>7JuT~< zAjy0GWS?mjy{)G)({cqjA0ebCQY_#kM>exe6(o3%Mt`m!>@du*?jZn zO}xb6_i49=gE=fNj&XEhZ9>VQScfy|M_1RKJ9mo5u!^|`hUW(WRy?Cvb=2HZTqi2n z!}9M$t)=x?kXag2#huvUS0n!UCKJ|t$@Z5~^i6&U#73BG@6OcJ)X{n~`tIG$tqz{^ z_2W!hs&9A#$sH?aS*};4;}{eaq$5~p#yd1T?6SaK3HO0AF%JjP5o#+S}t4Ib%KGB5zxB7zu(c9TkmXaaP>-tEAvNhS3dF^gMo=W zYbrzIp*5r_jxkyrcL)$qnCT*0Hm4(*y}i7&baaFS1$zYUOGv!&LtxspIFqC@-DXN8 zIjES#eck;14acTyNY9T#ZY8ii^vld!sLYVjVL1HBe_GI5YF_?!2QH z@h01G@Xr4J*{W*@JtO1&z`q-iU=1G@(Nx4I2i+kqK!&^hx&RMvv{8YLYE0cF>p)}38lz$h`u zw()u&8XB6Gcmf1sfH9+ce*0kgarJJLEmGDeek9+xBZYohv2UHh*~of<@s0j*N61I! zAqQm*FWl6N{_@Hc^!5B+zr|m-Vp*o5kHkq&q`*Tidjoh+SPfw}3LvqTE+J z&RkDLg*3TCd7oL6DqJx%U!%Z^Pa)9?D2PTrY+V?E2+YWKJ^OmBB=@_+nxD+|PT}o# zlR)=hi*ScaP+7SH_*YmUxwL=eEHt{X@UCUrjF(m}yS%7KDZkfRWkH1v z12_*7Bs)7Bl^g?Pw|n^E17Fx@7AoR@NWT63`?s&JZ))o8|mm?G>U=8yr`9;}R~qa(K?1+#Wo+t?Pec<=)<2Mn*=cTtIs^%>9)qd8EhM zSY62Jb_NOI3{W~?XoCEofnq~I6wrC5m!I0%+ne*HAQj$-`K)!O@Z*I}wbGat6&1Z` zwE#goK0Xcti)mzNY>XSz#!cN3OD}9uK6HhrK@G%(wsw*>#Z@5Q{X2&v;}=|~u)ECB z0w3^lMff)%{h`c)y%t(|SL{4xJ+*@m!)59G-YC6{YvO1#*@$@IusGL{RPVj|L62J{ z|5_CqeRjM}<`}ZJws!hEhQ}`Tw7)cX_tztyOa*($mt*GBjYyv6W6E7-E~@Cdx_f;& z$J-fa$A8)|3uXA1NE?pU>VX+5^teZ>o%yj{HWhWn#m;VSyyQeHP_^0fZ}1TaU;ky^ zxqGxX_+##IAprriP0!vpriXR zx=I_-YH>F@3nW8whcz$lf)nuMLQgik>KlO+CEh9!W5Km`uGHyL+#PzXyyR^B4|&j> zktRCh+C`0zujp6chl^Mn@A@88mLu#^Wq2h5`3v zST9GmT)TEHCE)T?w>l$<46+v9Dud#|W#FiQ-6e>*ma*|2%BW{jaDkehp8SD67Z6jC z^g*j@Pv%EwZ&cKtWIhn7PSvbCNhq3XpDp`!J@YQf%^86td6zBvkG9=!5)u+1n@wun zGHYvVOG;47h>UI;(#X3cN9!SHqXPr4>bR(5?(pzD%GF3j-X+0w%sz}`*z|`qYs^P&D)b73eV+2D)3?kfdit`>3Ocy^bAHPM#iHpY#ULfRutM14{QP<7jXdg(hsrH^ z8g~*+N<((O11}&ZyB7*yZpa>|t*|Jv^MBz#3f;Y_+kX8T>u*EGZ~AR6I-Cvm+FDu+ zB5r2>{vWHVvVDoI!rE*?f(Jy?S>YuBJ zI@LkZ`i}XQC_4g?f>wq4PevKj(b2V!-AeAbMR{4d7jzj?VXG+?(sV85D?%jWN6bF;mVId96!k_eK}Kh&@9+c{snautp=J}q9>@Z!7g>4Q~3FYa)2M}E+G z&|Xcf_rTIXhX5;TQs)uQ@*MhYk``(jngD-)XovS!M?F28 zgY^>Rk?_i)N<~SD>iYG}s%QG#)Pc=V4gvH*F;yN(N-y>2>$;bUgg760O(H)iUN-$Y zFTr|fbK~~M(XC=x%rgRERkoqD@DirEa2k^`J#Lp8`l}u){3%MMO@|I}Rj@EqQ)ZHq z7bMBO>&NG}?FCW~5B)3OdO16ezrU(+a1q z?w4zLEYuXP^z*Ud<9JtMn3ji^_gB|G-BjUQ+>ujw&!YPDo7?US(WY9l@|WtLep#ux zl%mw+|6-T+pkzl^y@jxiK}X)OfK|fm><^KYvf1ivn1eCTZYYc#M;`jvZ=mj}W3H1% z0%37b{oXz>tZ_M++z*QbOkm?bdQF=`C<_cEc@c_dX>mspfe4t}&bLSfdoQauQB{iBSm{Ymdayx#_UqTE3DrF6F=735ec z5|PkSMwmlGh?}7x*lc8o4wZ|~lB%N@y}*|sFO#jFng_;`+2s=}zJI_5N+6<(Yq#R_ z6KBfk4q0(l&DH3!6QCmQ5$Kxr2$z~}-v*D!PJk{}Zf4W>Kd;G22+Kmm6kju!b!BF95L)c_wU0h^Mq_NrA_);slsOXQ{{}Yo^z?uW5ZOWzB?HAE z!+M*O^L{#m3Iw zGVNw*d2=bgQN(6v& zZL-<5Vt8+T(o|b}w+xY@m`g}V2)B{1#t|JI4fqDG&_Q6Z=qF7o!F%`oP7WW}kE@VB zGeX&x>ru&uOJ&jvyC^9sftskv$+5cXI8kK#=zGsA4^yLU{kv1>)mI*ZETcDW!gD7Kpen*6j1K&>U!+$4el58pMaZ~wjJ)hc+{OcyE{AJ z2Zc**j?0)PBE`hS>OX$8C}-Yor5^#dOs zgxNNG6Lh5@IG}|98UR)Ku0Em5hK3sMP%1hrA~LdAr%)vyT(SZ!&IEbzR@pEq!|uf+y`rbN)`&nitiqS$|1##&E}s(H&XLvHbp+J6!~KOHuVE~>mg&qKEJh3MJnvb zku3}7p1Zu11nLF`1|}wJyZ*2w+hy$dHKXZDY|Bea?HwKJsfKE5KY#w5+Vx-cuE)*z z>Fvm-*TQA&Ij82iGpL&SaZ@iZFISAN5{8+BceeQKHEyQAug^^+4SE8D;(=ekehF5h zOSd@?;m^+YG6^XXdPl_S4u>1bt~9zb@(ofKOhsNr4E@0i{j{>;#7irH?ScsC-wdK6 zmX(zJys}c%ySU@u$d|%R7dx`L2j82K5kI$|FZ~0I;O_a}Fn;VA9txAkNd{Z)!F$|AU*lNqkk+_ ziLK}ItVf+e@tjBVZIYG!qjVK^S#|$L6E@5}2GW>TR_Yk2@z&p$gq=M^(!PEB298<# ztOsFO&-nOB*&j+{+SKWkfAD%_DEl;z%E;mXg{us(T?50zDOjwSpx`aA0yCbEyZDGO zh{O%{^(}aPEE=SyrUp+rzjx6~G)Q6+^GZ+e?5;2I<+IfmnT?Cw@oR>~t2ixy&L{(`XvUOX^BDE=j=-rjoXw|18Y z?=k#HxcShEZy1ua*s$hjq6=9}lMzaInKj!pt4m}6bf&~Z()5$?l9Gh)it z2hpk{k^VSF)xN7n`fmgMlG}{(PEM6qFCqd>p>3B(LYSF#X7iv2fHu2pKA)rAqWrl` zR$?OMQx-LY7v9RMs@Dh-uvo4n#eN6DjBZsVC3Q@0RaO7`KKLf|v2uiAclr7G@80bh z82C2r1};87zHLZIvpkZImV_=gBI{jL)MZGE@$q7f0tW{Nkb1ysy^EE4+*GpKy1Iq^ z4(Te%DI=^Tgg4RX5GSY3MK8ckNRXX(lD#{}$AK*5?+Od0-KwKYx~0 zcT9Xbuw@JTWi=!wUg0}koom~-ITW$L8oTnzGgr)k_zx>ya3|u4tvok%Hise@Y0g`1 zmaxpRaupz;6B84QkT1GygoT8%tf-vb>&L;Q0N4|EI8&4iCl{A8TW?FrwTtNF z4j9mo$IA6oJRe;J{UZ{$>?PXA=^}(JEG$e>n)}!p3P2BOX;M09Q4anvbdRKw5Cwid zzAq4ir6sNRxE-_KB28QO5Q6w`6+Y2#mb?62am7g5^Ksytd$^4}cI{l;ArKG!{>6hs z@z+PA1SJ`epPZH^kF-OVhV><3Q$bnewD!;Oxw>KMu7?6-NDbbK@Vt)h&@ooW?dO-3@iLGeot%b-UZ{M>mAX|AN*N5%s@5Mn zdKFg>^_sIsxL74>a^JtreUAvvMLbz&7Es$;TqczGeQbo<4^6R9QBl!3TL$}PsW^wj z!QA}DHbrQw1=Kx2uwQ|`?I-uNmT3_90*VI;Jc4L6T3A?k{BN3K?%e$RNpJ`R(_g>( zu`8{fo*sPaoe`n`IiX8rxLR0974}nKzg}!Eu_i~e94@;6b0_=EdqQni9#^Lw#w*;k z65KsJJc5HIJS9{?8b-FXSy3t*8YpWSwroFB$=Bqd@~&qTlz5n}UNah7jdps{uSrZ8 zcJ6gEF`-bXi3;0zlTuq=TBi7XFvm(u$sRujk+XhK>NLEL^Hw z(pnBgk&UgbENc%)d0n-Q$5#rCP|&lAEs?xQN$GK@QXLsccX9RoiUZwhSx(D2dy*40 zbUtC3vIki%kRD5)?`gMYIm*Qq>2bZsgOF1ss z%Q18LAK;VG{`1d2OiVD~fQCI&ObrmI)^O{7T=WxA^2rV6y=SQFaX+Q9hH z;>_)L7_|22!Owg(ofP|LK_%;`p&I1}X`3JqU8XT=uziQ7AIreNKth1$xPXi}A2%+) zJfb5Z%v2MBIhce*T)WO&V*%xQqmq=A6g}=&B~Iar58etUKzAe>?JNGqP2~7rn(TfD zYd)|=Nc?+upqwRyh3CCQ6}F2UN ziJ6%>BO_zpO=KZH==VJG?=V<;y@e$u-gQPNCnt=)Iw>g#1Of5+UI0c$D%pQx<%F>5 zin$OJAD?~DF9yXZE-vZfY}N!ASGbEXfW3{yV&N+la~n)tb#;?_7X#b5U}OkK1B`BT zb!oyrKS<)SPXz@FNlir@&eO2*rDcf;O(IEdgrZUY1HZ&|HiutS?C z<7aB6GQoOC?y);QMDxUG>*&mRiQ3xQo`LNMl&!^iorDl(nAomh8ROsm zPF`L+fZD*lEaU`u7n&!#XFXuh{8Z6I944M6TAX0jfMEliHw+zKSG=8)TtxsoJ3ElF zTs8%9cuIh-roG25pe5i7l2TIpqguF1JnmYQ3;~{`r{^{up?Lm3vELx_TAbDu!!|ZH zUoBw13*|8F_8KHO4NXmD<-7hR!L)zQw?!0@73&22-7s%7LG$tb-ampWjho?2;sis< zNhtei=VBNT66kbQ)$ZTFS!LB>bWm1SmY4UWrE^ z$gAYC@3~DqF(_tYWV}ikW>T8mW(8>1KRB5D@4s(t^cZl~eE*~p{VS-X1VXIJpg=2C zWs&G9FSZM*FtY01clrVax*#)Rt>{mDn-wP&ai$tbeXvj~o=(znDua%#jQfdyNfku) z^VZ)J6DHWMh;Ogv|NQwgKR?*tpL;e@_1S&Qim%P;!|Ca1LBZ`lGiWsbc=*}d+k?lF z`VbS;`0L`a6YT$J{3#GiESrmaaR2vrGhX>bq$GKuM9BF3AD}@s4jFYSNpb>7@!13W zRG|NNFZ!~j4d9ZUozLwMP0e1gUOq&ao>X@o_a}jQ8$E&NK3USkJOpV_@VNQ(;#j&HSknJRd(uMsc zX}gtcNo>8o;uF`Bz6G)Z_%QO&pNH$ouB5uwe_9=!chbo0%1Qwq9x|6J|Lt?3|32&S z*vH4Pc;EpGOM<)-TQ6b1_kSpZ2*ey^eNY3%3;u9rrB~SdN5N#D-f@BbxqOo;KA_Pg zH4kKoBsqPf68Zo3%!prjCvX}5|G$ki|JytBe>c*c5ApxsMwZa%k$4E$g0ScNSQtTKaQ|H=>Px# From 96e20a8efecb280054730c9c3c59ad5340721f1f Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 18:33:54 +0200 Subject: [PATCH 57/77] Add variable to sample --- source/_components/binary_sensor.nest.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/binary_sensor.nest.markdown b/source/_components/binary_sensor.nest.markdown index d7c74a38341..e42d13c0db4 100644 --- a/source/_components/binary_sensor.nest.markdown +++ b/source/_components/binary_sensor.nest.markdown @@ -19,6 +19,7 @@ To set it up, add the following information to your `configuration.yaml` file: ```yaml binary_sensor: platform: nest + scan_interval: 60 monitored_conditions: - 'fan' - 'hvac_ac_state' From 0604e083e8426d1b4a1b6d8306e47dd5edab3a7c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 19:08:03 +0200 Subject: [PATCH 58/77] Update Nest docs --- source/_components/binary_sensor.nest.markdown | 5 ++++- source/_components/climate.nest.markdown | 7 ++++--- source/_components/sensor.nest.markdown | 7 ++++--- source/_components/sensor.nest_weather.markdown | 5 ++++- 4 files changed, 16 insertions(+), 8 deletions(-) diff --git a/source/_components/binary_sensor.nest.markdown b/source/_components/binary_sensor.nest.markdown index e42d13c0db4..893e5788b40 100644 --- a/source/_components/binary_sensor.nest.markdown +++ b/source/_components/binary_sensor.nest.markdown @@ -14,6 +14,10 @@ ha_category: Binary Sensor The `nest` binary sensor platform let you monitor various states of a thermostat from [Nest](https://nest.com). +

    +You must have the [Nest component](/components/nest/) configured to use this sensors. +

    + To set it up, add the following information to your `configuration.yaml` file: ```yaml @@ -47,4 +51,3 @@ Configuration variables: - 'hvac_emer_heat_state' - 'online' -

    You must have the [Nest component](/components/nest/) configured to use this sensor.

    diff --git a/source/_components/climate.nest.markdown b/source/_components/climate.nest.markdown index 69dbc90fdb0..2e8c6742055 100644 --- a/source/_components/climate.nest.markdown +++ b/source/_components/climate.nest.markdown @@ -14,6 +14,10 @@ ha_category: Climate The `nest` climate platform let you control a thermostat from [Nest](https://nest.com). +

    +You must have the [Nest component](/components/nest/) configured to use those thermostats. +

    + To set it up, add the following information to your `configuration.yaml` file: ```yaml @@ -25,6 +29,3 @@ climate:

    -

    - You must have the [Nest component](https://home-assistant.io/components/nest/) configured to use this sensor. -

    diff --git a/source/_components/sensor.nest.markdown b/source/_components/sensor.nest.markdown index e59223c77f3..55f6e35ed42 100644 --- a/source/_components/sensor.nest.markdown +++ b/source/_components/sensor.nest.markdown @@ -15,6 +15,10 @@ ha_release: pre 0.7 The `nest` sensor platform let you monitor sensors connected to your [Nest](https://nest.com) thermostat and/or your Nest Protect Smoke Alarm. +

    +You must have the [Nest component](/components/nest/) configured to use those sensors. +

    + To set it up, add the following information to your `configuration.yaml` file: ```yaml @@ -57,6 +61,3 @@ Configuration variables: - 'co_status' # Nest Protect only - 'smoke_status' # Nest Protect only -

    -You must have the [Nest component](/components/nest/) configured to use this sensor. -

    diff --git a/source/_components/sensor.nest_weather.markdown b/source/_components/sensor.nest_weather.markdown index 35617f8f0d4..7d70c588926 100644 --- a/source/_components/sensor.nest_weather.markdown +++ b/source/_components/sensor.nest_weather.markdown @@ -15,6 +15,10 @@ ha_iot_class: "Cloud Poll" The `nest` weather sensor platform let you monitor current weather conditions based on the location of your [Nest](https://nest.com) thermostat. +

    +You must have the [Nest component](/components/nest/) configured to use those sensors. +

    + To set it up, add the following information to your `configuration.yaml` file: ```yaml @@ -37,4 +41,3 @@ Configuration variables: - 'wind_speed' - 'wind_direction' -

    You must have the [Nest component](/components/nest/) configured to use this sensor.

    From e03d26d3fab20a98a94454717df79fab8092969b Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Thu, 1 Sep 2016 14:38:56 -0400 Subject: [PATCH 59/77] Added an example of an Automation using IFTTT (#884) * Added an example of an Automation using IFTTT For me, the data entry was confusing so hopefully this example helps clear it up. * Update ifttt.markdown --- source/_components/ifttt.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/source/_components/ifttt.markdown b/source/_components/ifttt.markdown index c5adde1b462..ce87fdaf248 100644 --- a/source/_components/ifttt.markdown +++ b/source/_components/ifttt.markdown @@ -55,6 +55,18 @@ When your screen looks like this, click the 'call service' button. You need to setup a unique trigger for each event you sent to IFTTT.

    +```yaml +# Example configuration.yaml Automation entry +automation: + - alias: Startup Notification + trigger: + platform: event + event_type: homeassistant_start + action: + service: ifttt.trigger + data: {"event":"TestHA_Trigger", "value1":"Hello World!"} +``` + ### {% linkable_title Sending events from IFTTT to Home Assistant %} To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web. This can be achieved by forwarding port 8123 from your router to the device running Home Assistant. If your ISP is giving you a new IP address from time to time, consider using [DuckDNS][duck-dns]. From 16b2754a66936186086816e43f2ed38a3819787e Mon Sep 17 00:00:00 2001 From: Teagan Glenn Date: Thu, 1 Sep 2016 12:40:13 -0600 Subject: [PATCH 60/77] Set date/release in future until I can fix the insteon hub. (#879) --- source/_components/fan.insteon_hub.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/fan.insteon_hub.markdown b/source/_components/fan.insteon_hub.markdown index fe21a38bdbb..364b94fa40c 100644 --- a/source/_components/fan.insteon_hub.markdown +++ b/source/_components/fan.insteon_hub.markdown @@ -2,14 +2,14 @@ layout: page title: "Insteon Hub Fan" description: "Instructions how to setup the Insteon Hub Fans within Home Assistant." -date: 2016-08-26 08:00 +date: 2017-08-26 08:00 sidebar: true comments: false sharing: true footer: true logo: insteon.png ha_category: Fan -ha_release: 0.27 +ha_release: 0.30 --- The `insteon_hub` fan component lets you control your fans connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant. From cdddf666ca2003566de781e4e2fc79ec539481be Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Thu, 1 Sep 2016 15:23:18 -0400 Subject: [PATCH 61/77] Added information to turn off Disco Lights on Aeon Gen5 (#881) * Added information to turn off Disco Lights on Aeon Gen5 Although not HA specific, this information wasn't easily found. (Found it eventually in an AMAZON review!). So since ZWave Sticks are so popular with HA users, I thought I would contribute this information. * Update z-wave-settings.markdown --- source/getting-started/z-wave-settings.markdown | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/source/getting-started/z-wave-settings.markdown b/source/getting-started/z-wave-settings.markdown index ff23871c919..fb99009139d 100644 --- a/source/getting-started/z-wave-settings.markdown +++ b/source/getting-started/z-wave-settings.markdown @@ -12,3 +12,13 @@ footer: true You may wish to modify the zwave settings ozw*.xml file in your .homeassistant root folder, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize [Open-Zwave Control Panel](https://github.com/OpenZWave/open-zwave-control-panel). Alternatively, use [Domoticz](https://www.domoticz.com/), which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image. The reasoning for using these tools is that your Zwave controller stores the values and data that are used to control the network. The XML file in the .homeassistant folder acts as a settings/values cache for the zwave network, so modifying it directly won't change the network values. The Open-Zwave Control Panel writes values directly to the network, and will provide you with an updated .xml file to overwrite in your .homeassistant folder. This is the most foolproof way to make modifications to your zwave devices. + +Although totally normal for your ZWave stick (Aeon Aeotec Z-Stick Gen5 for example) to cycle through LEDs (Yellow, Blue and Red) while plugged into your Pi, it's also super annoying. If you want to turn off the cycling color, you can use the following commands from a terminal session to your Pi. + +Turn off Disco lights + +```echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00``` + +Turn on Disco lights + +```echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00``` From 6ad4be9e1ea7639d56bdc8cc2255d0d2022ae443 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 1 Sep 2016 19:46:31 +0200 Subject: [PATCH 62/77] Move details --- source/_components/sensor.fritzbox_callmonitor.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_components/sensor.fritzbox_callmonitor.markdown b/source/_components/sensor.fritzbox_callmonitor.markdown index 84108591be8..290b9bc5051 100644 --- a/source/_components/sensor.fritzbox_callmonitor.markdown +++ b/source/_components/sensor.fritzbox_callmonitor.markdown @@ -9,13 +9,15 @@ sharing: true footer: true logo: avm.png ha_category: System Monitor -ha_release: "0.27" +ha_release: 0.27 +ha_iot_class: "Local Polling" --- The `fritzbox_callmonitor` sensor monitors the call monitor exposed by [AVM Fritz!Box](http://avm.de/produkte/fritzbox/) routers -on TCP port 1012. It will assume the values 'idle', 'ringing', 'dialing', or 'talking', -with the phone numbers involved contained in the state attributes. +on TCP port 1012. It will assume the values `idle`, `ringing`, `dialing`, or `talking` with the phone numbers involved contained in the state attributes. + +To activate the call monitor on your Fritz!Box, dial #96*5* from any phone connected to it. To use the Fritz!Box call monitor in your installation, add the following to your `configuration.yaml` file: From 6eafa32950e1de611dc7c4eeadacdb26787213bb Mon Sep 17 00:00:00 2001 From: John Lindley Date: Thu, 1 Sep 2016 16:51:41 -0400 Subject: [PATCH 63/77] GoControl can be opened/closed The text is misleading as GoControl integrated with Wink CAN be opened/closed. --- source/_components/cover.wink.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/cover.wink.markdown b/source/_components/cover.wink.markdown index ae896cef612..dc4d53b5805 100644 --- a/source/_components/cover.wink.markdown +++ b/source/_components/cover.wink.markdown @@ -12,7 +12,7 @@ ha_category: Cover ha_release: 0.13 --- -Wink cover/garage door functionality is currently limited to view only. Wink garage doors will still show the current state of the door, but control has been disabled for third parties. If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control. +Wink cover/garage door functionality depends on the product you're using. With GoControl/Linear Home Assistant can open, close, and view state. Chamberlain is currently limited to view only. Meaning Home Assistant will only show the current state of the door and control has been disabled (by Chamberlain). If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control. The following quote is from Wink. From 897f003ab9143484ea2aed5fbe04ba73b28f9e38 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 2 Sep 2016 07:48:39 +0200 Subject: [PATCH 64/77] mall format changes --- source/_components/ecobee.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_components/ecobee.markdown b/source/_components/ecobee.markdown index 81a327f03b4..b1b3eca6f6c 100644 --- a/source/_components/ecobee.markdown +++ b/source/_components/ecobee.markdown @@ -13,11 +13,11 @@ featured: true --- -The Ecobee platform lets you control a thermostats and view sensor data from the [Ecobee](https://ecobee.com) thermostat. +The `ecobee` component lets you control a thermostats and view sensor data from [ecobee](https://ecobee.com) thermostats. -You will need to obtain an API key from ecobee's [developer site](https://www.ecobee.com/developers/) to use this component. To get the key, first you need to register your thermostat. Once you have done that, click on the 'Become a developer' link on the developer site. Login with your ecobee credentials, accept the SDK agreement, fill in the fields, and click save. Now login to the regular consumer portal, and in the hamburger menu there will br a new option 'Developer'. Select that, then select 'Create New'. Give your app a name (it appears to need to be unique across all users, as I tried 'home-assistant' and it said it was already in use) and a summary (neither of these are important as they are not used anywhere). For Authorization method select 'ecobee PIN'. You don't need an Application Icon or Detailed Description. Click Save. Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the 'X' to close the Developer section. +You will need to obtain an API key from ecobee's [developer site](https://www.ecobee.com/developers/) to use this component. To get the key, first you need to register your thermostat. Once you have done that, click on the **Become a developer** link on the developer site. Login with your Ecobee credentials, accept the SDK agreement, fill in the fields, and click **save**. Now login to the regular consumer portal, and in the hamburger menu there will be a new option **Developer**. Select that, then select **Create New**. Give your app a name (it appears to need to be unique across all users, as I tried 'home-assistant' and it said it was already in use) and a summary (neither of these are important as they are not used anywhere). For Authorization method select **ecobee PIN**. You don't need an Application Icon or Detailed Description. Click **Save**. Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the **X** to close the Developer section. -The first time you run Home-Assistant with this component it will give you a PIN code that you need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by clicking 'Add Application' in the 'My Apps' section in the sidebar. Enter the PIN code from the Home Assistant screeen. To get the PIN code select the item in the Ecobee card. If you do not have an Ecobee card, you may be using groups with default_view that don't show the card. To get around this you can temporarily comment out the default_view section or add the configurator.ecobee component to your default_view and restart Home Assistant. Once you enter the PIN on the Ecobee site, wait approximately 5 minutes and then click on the 'I have authorized the app' link at the bottom of the Ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full Ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your default_view (if you had to disable it) and add the Ecobee sensors to a group and/or view. +The first time you run Home Assistant with this component it will give you a PIN code that you need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by clicking **Add Application** in the **My Apps** section in the sidebar. Enter the PIN code from the Home Assistant screeen. To get the PIN code select the item in the ecobee card. If you do not have an ecobee card, you may be using groups with `default_view` that don't show the card. To get around this you can temporarily comment out the `default_view` section or add the `configurator.ecobee` component to your `default_view` and restart Home Assistant. Once you enter the PIN on the ecobee site, wait approximately 5 minutes and then click on the **I have authorized the app** link at the bottom of the ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your `default_view` (if you had to disable it) and add the ecobee sensors to a group and/or view. To set it up, add the following information to your `configuration.yaml` file: @@ -29,8 +29,8 @@ ecobee: Configuration variables: -- **api_key** (*Required*): Your Ecobee api key. -- **hold_temp** (*Optional*): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event (False, default). +- **api_key** (*Required*): Your ecobee API key. +- **hold_temp** (*Optional*): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event. Defaults to `False`.

    From 5d84b6ca87536b97e95029d97e448133d4dcd2d6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 2 Sep 2016 07:51:14 +0200 Subject: [PATCH 65/77] Update format and wording --- .../getting-started/z-wave-settings.markdown | 20 ++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/source/getting-started/z-wave-settings.markdown b/source/getting-started/z-wave-settings.markdown index fb99009139d..76682705797 100644 --- a/source/getting-started/z-wave-settings.markdown +++ b/source/getting-started/z-wave-settings.markdown @@ -9,16 +9,22 @@ sharing: true footer: true --- -You may wish to modify the zwave settings ozw*.xml file in your .homeassistant root folder, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize [Open-Zwave Control Panel](https://github.com/OpenZWave/open-zwave-control-panel). Alternatively, use [Domoticz](https://www.domoticz.com/), which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image. +You may wish to modify the Z-Wave settings in your `ozw*.xml` file stored in the `.homeassistant` directory, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize [Open-Zwave Control Panel](https://github.com/OpenZWave/open-zwave-control-panel). Alternatively, use [Domoticz](https://www.domoticz.com/), which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image. -The reasoning for using these tools is that your Zwave controller stores the values and data that are used to control the network. The XML file in the .homeassistant folder acts as a settings/values cache for the zwave network, so modifying it directly won't change the network values. The Open-Zwave Control Panel writes values directly to the network, and will provide you with an updated .xml file to overwrite in your .homeassistant folder. This is the most foolproof way to make modifications to your zwave devices. +The reasoning for using these tools is that your Z-Wave controller stores the values and data that are used to control the network. The XML file in the `.homeassistant` folder acts as a settings/values cache for the Z-Wave network, so modifying it directly won't change the network values. The Open-Zwave Control Panel writes values directly to the network and will provide you with an updated `.xml` file to overwrite in your `.homeassistant` folder. This is the most foolproof way to make modifications to your Z-Wave devices. -Although totally normal for your ZWave stick (Aeon Aeotec Z-Stick Gen5 for example) to cycle through LEDs (Yellow, Blue and Red) while plugged into your Pi, it's also super annoying. If you want to turn off the cycling color, you can use the following commands from a terminal session to your Pi. +Although totally normal for your Z-Wave stick (Aeon Aeotec Z-Stick Gen5 for example) to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don like this behaviour then you could turn it off. -Turn off Disco lights +Use the following commands from a terminal session to your Pi where your Z-Wave stick is connected as an example. -```echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00``` +Turn off "Disco lights": -Turn on Disco lights +```bash +$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00 +``` -```echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00``` +Turn on "Disco lights": + +```bash +$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00 +``` From 8d90cd207ca94cabb9b8cf572f4205af50ec6a9c Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 2 Sep 2016 11:22:55 +0200 Subject: [PATCH 66/77] Update camera.ffmpeg.markdown --- source/_components/camera.ffmpeg.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index a9abd91d5d4..28b9e17acf2 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -13,7 +13,7 @@ ha_release: 0.26 --- -The `ffmpeg` platform allows you to use every video feed with [FFmpeg](http://www.ffmpeg.org/) as camera in Home Assistant. +The `ffmpeg` platform allows you to use every video feed with [FFmpeg](http://www.ffmpeg.org/) as camera in Home Assistant. The input for ffmpeg need to support that could have multiple connection to source (input). For every user in UI and all 10 seconds (snapshot image) it make a new connection/reading to source. Normally that should never be a trouble only in strange selfmade constructs can be make mistakes.

    You need a `ffmpeg` binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need tobuild from source by yourself. Windows binary are avilable on the [FFmpeg](http://www.ffmpeg.org/) website. From 0f4f267306247ef172d5fbb3f52e2d6a36037930 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 2 Sep 2016 11:23:49 +0200 Subject: [PATCH 67/77] Update camera.ffmpeg.markdown --- source/_components/camera.ffmpeg.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 28b9e17acf2..f6a41895cc6 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -13,7 +13,7 @@ ha_release: 0.26 --- -The `ffmpeg` platform allows you to use every video feed with [FFmpeg](http://www.ffmpeg.org/) as camera in Home Assistant. The input for ffmpeg need to support that could have multiple connection to source (input). For every user in UI and all 10 seconds (snapshot image) it make a new connection/reading to source. Normally that should never be a trouble only in strange selfmade constructs can be make mistakes. +The `ffmpeg` platform allows you to use every video feed with [FFmpeg](http://www.ffmpeg.org/) as camera in Home Assistant. The input for ffmpeg need to support that could have multiple connection to source (input) in same time. For every user in UI and all 10 seconds (snapshot image) it make a new connection/reading to source. Normally that should never be a trouble only in strange selfmade constructs can be make mistakes.

    You need a `ffmpeg` binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need tobuild from source by yourself. Windows binary are avilable on the [FFmpeg](http://www.ffmpeg.org/) website. From d882106301e20edb0647f014a698c0f1069f189c Mon Sep 17 00:00:00 2001 From: Zen Tormey Date: Fri, 2 Sep 2016 11:16:35 -0500 Subject: [PATCH 68/77] Update binary_sensor.ffmpeg.markdown (#886) Reworded a few places for grammar/readability. Also, I have never proposed a change to the documentation before, so I hope I am doing this in the proper way. Trying to be helpful, not step on anyone's feet! Please feel free to admonish me, if I am not following proper etiquette. :) --- .../_components/binary_sensor.ffmpeg.markdown | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/source/_components/binary_sensor.ffmpeg.markdown b/source/_components/binary_sensor.ffmpeg.markdown index b9e16a2a589..4a14494725c 100644 --- a/source/_components/binary_sensor.ffmpeg.markdown +++ b/source/_components/binary_sensor.ffmpeg.markdown @@ -14,10 +14,10 @@ ha_iot_class: "Local Polling" --- -The `ffmpeg` platform allows you to use every video or audio feed with [FFmpeg](http://www.ffmpeg.org/) for various sensors in Home Assistant. Available are: **noise**, **motion**. If the `ffmpeg` process is brocken, the sensor going to unavailable. It exists a service to restart a instance with *binary_sensor.ffmpeg_restart*. +The `ffmpeg` platform allows you to use every video or audio feed with [FFmpeg](http://www.ffmpeg.org/) for various sensors in Home Assistant. Available are: **noise**, **motion**. If the `ffmpeg` process is broken, the sensor will be unavailable. To restart the instance, use the service *binary_sensor.ffmpeg_restart*.

    -You need a `ffmpeg` binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need to build it from sourceby ourself. Windows binary are avilable on [FFmpeg](http://www.ffmpeg.org/) homepage. +You need the `ffmpeg` binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need to build it from source. Windows binary are avilable on [FFmpeg](http://www.ffmpeg.org/) homepage.

    ### {% linkable_title Noise %} @@ -47,7 +47,7 @@ Configuration variables: - **duration** (*Optional*): Default 1 seconds. How long need the noise over the peak to trigger the state. - **reset** (*Optional*): Defaults to 20 seconds. The time to reset the state after none new noise is over the peak. - **extra_arguments** (*Optional*): Extra option they will pass to `ffmpeg`, like audio frequence filtering. -- **output** (*Optional*): Allow you to send the audio output of this sensor to a icecast server or other ffmpeg supported output, eg. to stream with sonos after state is trigger. +- **output** (*Optional*): Allow you to send the audio output of this sensor to an icecast server or other ffmpeg supported output, eg. to stream with sonos after state is triggered. For playing with values: @@ -57,7 +57,7 @@ $ ffmpeg -i YOUR_INPUT -vn -filter:a silencedetect=n=-30dB:d=1 -f null - ### {% linkable_title Motion %} -FFmpeg don't have a motion detection filter so it use a scene filter to detect a new scene/motion. In fact you can set how big a object or size of image they need change to detect a motion. The option 'changes' is the percent value of change between frames. You can add a denoise filter to video if you want a realy small value for 'changes'. +FFmpeg doesn't have a motion detection filter, so it uses a scene filter to detect a new scene/motion. In fact, you can set how big of an object or the size of an image that needs to change in order to detect motion. The option 'changes' is the percent value of change between frames. You can add a denoise filter to the video if you want a really small value for 'changes'. To enable your FFmpeg with motion detection in your installation, add the following to your `configuration.yaml` file: @@ -79,14 +79,14 @@ camera: Configuration variables: -- **input** (*Required*): A ffmpeg compatible input file, stream or feed. +- **input** (*Required*): A ffmpeg compatible input file, stream, or feed. - **tool** (*Required*): Is fix set to `motion`. - **name** (*Optional*): This parameter allows you to override the name of your camera. - **ffmpeg_bin** (*Optional*): Default `ffmpeg`. -- **changes** (*Optional*): Default 10 percent. A lower value is more sensitive. I use 4 / 3.5 on my cameras. It describe how much of two frames need to change to detect it as motion. See on descripton. -- **reset** (*Optional*): Default 20 seconds. The time to reset the state after none new motion is detect. -- **repeat** (*Optional*): Default 0 repeats (deactivate). How many motion need to detect in *repeat_time* to trigger a motion. -- **repeat_time** (*Optional*): Default 0 seconds (deactivate). The time to repeats before it trigger a motion. +- **changes** (*Optional*): Default 10 percent. A lower value is more sensitive. I use 4 / 3.5 on my cameras. It describes how much needs to change between two frames to detect it as motion. See on descripton. +- **reset** (*Optional*): Default 20 seconds. The time to reset the state after no new motion is detected. +- **repeat** (*Optional*): Default 0 repeats (deactivate). How many events need to be detected in *repeat_time* in order to trigger a motion. +- **repeat_time** (*Optional*): Default 0 seconds (deactivate). The span of time *repeat* events need to occur in before triggering a motion. - **extra_arguments** (*Optional*): Extra option they will pass to ffmpeg. i.e. video denoise filtering. For playing with values (changes/100 is the scene value on ffmpeg): From 8bc9c9d73d25377c3bb69512c405dc9fef712db1 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 2 Sep 2016 08:17:35 +0200 Subject: [PATCH 69/77] Add link to deps --- source/developers/website.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/website.markdown b/source/developers/website.markdown index 595c3c6987b..857151af3b9 100644 --- a/source/developers/website.markdown +++ b/source/developers/website.markdown @@ -11,7 +11,7 @@ footer: true The website you're reading now is the home of Home Assistant: [https://home-assistant.io](https://home-assistant.io). This is the place where we provide documentation and additional details about Home Assistant for end users and developers. -home-assistant.io is built using [Jekyll](http://github.com/mojombo/jekyll). The pages are written in [markdown](http://daringfireball.net/projects/markdown/); to add a page you don't need to know about HTML or the like. +home-assistant.io is built using [Jekyll](http://github.com/mojombo/jekyll) and [those available dependencies](https://pages.github.com/versions/). The pages are written in [markdown](http://daringfireball.net/projects/markdown/); to add a page you don't need to know about HTML or the like. The link "**Edit this page on GitHub**" allows one to edit pages without creating a fork. From 978bb0cdb5eaa6860a5695b1c90bbc3f3caadcba Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 2 Sep 2016 08:18:20 +0200 Subject: [PATCH 70/77] Fix typo --- source/developers/add_new_platform.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/developers/add_new_platform.markdown b/source/developers/add_new_platform.markdown index 73bf3e5367c..b915eae4e08 100644 --- a/source/developers/add_new_platform.markdown +++ b/source/developers/add_new_platform.markdown @@ -9,9 +9,9 @@ sharing: true footer: true --- -Components that interact with devices are called Entity Components. They are structured in core- and platform logic. This allows the same logic to handle a light to be used by different brands. +Components that interact with devices are called "Entity Components". They are structured in core- and platform logic. This allows the same logic to handle a light to be used by different brands. -For example, the built-in `switch` component consists of various platform in [`homeassistant/components/switch/`](https://github.com/home-assistant/home-assistant/tree/master/homeassistant/components/switch). The file `__init__.py` contains the core logic of all platform and the `vendor_name.py` files only the relevant platform code. +For example, the built-in `switch` component consists of various platforms in [`homeassistant/components/switch/`](https://github.com/home-assistant/home-assistant/tree/master/homeassistant/components/switch). The file `__init__.py` contains the core logic of all platform and the `vendor_name.py` files only the relevant platform code. If you are planning to add support for a new type of device to an existing component, you can get away with only writing platform logic. Have a look at how the component works with other platforms and create a similar file for the platform that you would like to add: From 366b49ce61a088416f23e288b9711e636ea790da Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 2 Sep 2016 22:44:30 +0200 Subject: [PATCH 71/77] Add initial netio docs --- source/_components/switch.netio.markdown | 112 +++++++++++++++++++++++ source/images/supported_brands/netio.png | Bin 0 -> 4107 bytes 2 files changed, 112 insertions(+) create mode 100644 source/_components/switch.netio.markdown create mode 100644 source/images/supported_brands/netio.png diff --git a/source/_components/switch.netio.markdown b/source/_components/switch.netio.markdown new file mode 100644 index 00000000000..b30efab2212 --- /dev/null +++ b/source/_components/switch.netio.markdown @@ -0,0 +1,112 @@ +--- +layout: page +title: "Netio Switch" +description: "Instructions how to integrate Netio switches into Home Assistant." +date: 2016-09-02 19:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: netio.png +ha_category: Switch +ha_iot_class: "Local Polling" +ha_release: 0.24 +--- + + +The `netio` switch platform allows you to control your [Netio](http://www.netio-products.com/en/overview/) Netio4, Netio4 All, and Netio 230B. These are smart outlets controllable through ethernet and/or WiFi that reports consumptions (Netio4all). + +To use Netio devices in your installation, add the following to your `configuration.yaml` file: + +``` +# Example configuration.yaml entry +switch: + - platform: netio + host: 192.168.1.43 + port: 1234 + username: user + password: pwd + outlets: + 1: Free + 2: TV + 4: Lamp +``` + +Configuration variables: + +- **host** (*Required*): The IP address of your Netio plug, eg. http://192.168.1.32 +- **port** (*Optional*): The port to communicate with the switch. Defaults to `1234`. +- **username** (*Required*): The username for your plug. +- **password** (*Required*): The password for your plug. +- **outlets** (*Required*) array: List of all outlets. + - **[No.]: [Name]** (*Required*): Identification of an outlet. + + + +To get pushed updates from the Netio devices, one can add this Lua code in the device interface as an action triggered on "Netio" "System variables updated" +with an 'Always' schedule: + + +```lua +-- this will send socket and consumption status updates via CGI +-- to given address. Associate with 'System variables update' event +-- to get consumption updates when they show up + +local address='ha:8123' +local path = '/api/netio/' + + +local output = {} +for i = 1, 4 do for _, what in pairs({'state', 'consumption', + 'cumulatedConsumption', 'consumptionStart'}) do + local varname = string.format('output%d_%s', i, what) + table.insert(output, + varname..'='..tostring(devices.system[varname]):gsub(" ","|")) +end end + +local qs = table.concat(output, '&') +local url = string.format('http://%s%s?%s', address, path, qs) +devices.system.CustomCGI{url=url} +``` + + + + + + + + + + + + + + + + + + + + + +The `dlink` switch platform allows you to control the state of your [D-Link Wi-Fi Smart Plugs](http://us.dlink.com/product-category/home-solutions/connected-home/smart-plugs/). + +Supported devices (tested): + +- DSP-W215 +- DSP-W110 + +To use your D-Link smart plugs in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +switch: + platform: dlink + host: IP_ADRRESS + name: D-Link plug + username: YOUR_USERNAME + password: YOUR_PASSWORD +``` + + + diff --git a/source/images/supported_brands/netio.png b/source/images/supported_brands/netio.png new file mode 100644 index 0000000000000000000000000000000000000000..1cd239537b2d1937b3e517146d713c88d2fa7e1f GIT binary patch literal 4107 zcmV+m5cKbfP)KLZ*U+IBfRsybQWXdwQbLP>6pAqfylh#{fb6;Z(vMMVS~$e@S=j*ftg6;Uhf59&ghTmgWD0l;*T zI709Y^p6lP1rIRMx#05C~cW=H_Aw*bJ-5DT&Z2n+x)QHX^p z00esgV8|mQcmRZ%02D^@S3L16t`O%c004NIvOKvYIYoh62rY33S640`D9%Y2D-rV&neh&#Q1i z007~1e$oCcFS8neI|hJl{-P!B1ZZ9hpmq0)X0i`JwE&>$+E?>%_LC6RbVIkUx0b+_+BaR3cnT7Zv!AJxW zizFb)h!jyGOOZ85F;a?DAXP{m@;!0_IfqH8(HlgRxt7s3}k3K`kFu>>-2Q$QMFfPW!La{h336o>X zu_CMttHv6zR;&ZNiS=X8v3CR#fknUxHUxJ0uoBa_M6WNWeqIg~6QE69c9o#eyhGvpiOA@W-aonk<7r1(?fC{oI5N*U!4 zfg=2N-7=cNnjjOr{yriy6mMFgG#l znCF=fnQv8CDz++o6_Lscl}eQ+l^ZHARH>?_s@|##Rr6KLRFA1%Q+=*RRWnoLsR`7U zt5vFIcfW3@?wFpwUVxrVZ>QdQz32KIeJ}k~{cZZE^+ya? z2D1z#2HOnI7(B%_ac?{wFUQ;QQA1tBKtrWrm0_3Rgps+?Jfqb{jYbcQX~taRB;#$y zZN{S}1|}gUOHJxc?wV3fxuz+mJ4`!F$IZ;mqRrNsHJd##*D~ju=bP7?-?v~|cv>vB zsJ6IeNwVZxrdjT`yl#bBIa#GxRa#xMMy;K#CDyyGyQdMSxlWT#tDe?p!?5wT$+oGt z8L;Kp2HUQ-ZMJ=3XJQv;x5ci*?vuTfeY$;({XGW_huIFR9a(?@3)XSs8O^N5RyOM=TTmp(3=8^+zpz2r)C z^>JO{deZfso3oq3?Wo(Y?l$ge?uXo;%ru`Vo>?<<(8I_>;8Eq#KMS9gFl*neeosSB zfoHYnBQIkwkyowPu(zdms`p{<7e4kra-ZWq<2*OsGTvEV%s0Td$hXT+!*8Bnh2KMe zBmZRodjHV?r+_5^X9J0WL4jKW`}lf%A-|44I@@LTvf1rHjG(ze6+w@Jt%Bvjts!X0 z?2xS?_ve_-kiKB_KiJlZ$9G`c^=E@oNG)mWWaNo-3TIW8)$Hg0Ub-~8?KhvJ>$ z3*&nim@mj(aCxE5!t{lw7O5^0EIO7zOo&c6l<+|iDySBWCGrz@C5{St!X3hAA}`T4 z(TLbXTq+(;@<=L8dXnssyft|w#WSTW<++3>sgS%(4NTpeI-VAqb|7ssJvzNHgOZVu zaYCvgO_R1~>SyL=cFU|~g|hy|Zi}}s9+d~lYqOB71z9Z$wnC=pR9Yz4DhIM>Wmjgu z&56o6maCpC&F##y%G;1PobR9i?GnNg;gYtchD%p19a!eQtZF&3JaKv33gZ<8D~47E ztUS1iwkmDaPpj=$m#%)jCVEY4fnLGNg2A-`YwHVD3gv};>)hAvT~AmqS>Lr``i7kw zJ{5_It`yrBmlc25DBO7E8;5VoznR>Ww5hAaxn$2~(q`%A-YuS64wkBy=9dm`4cXeX z4c}I@?e+FW+b@^RDBHV(wnMq2zdX3SWv9u`%{xC-q*U}&`cyXV(%rRT*Z6MH?i+i& z_B8C(+grT%{XWUQ+f@NoP1R=AW&26{v-dx)iK^-Nmiuj8txj!m?Z*Ss1N{dh4z}01 z)YTo*JycSU)+_5r4#yw9{+;i4Ee$peRgIj+;v;ZGdF1K$3E%e~4LaI(jC-u%2h$&R z9cLXcYC@Xwnns&bn)_Q~Te?roKGD|d-g^8;+aC{{G(1^(O7m37Y1-+6)01cN&y1aw zoqc{T`P^XJqPBbIW6s}d4{z_f5Om?vMgNQEJG?v2T=KYd^0M3I6IZxbny)%vZR&LD zJpPl@Psh8QyPB@KTx+@RdcC!KX7}kEo;S|j^u2lU7XQ}Oo;f|;z4Ll+_r>@1-xl3| zawq-H%e&ckC+@AhPrP6BKT#_XdT7&;F71j}Joy zkC~6lh7E@6o;W@^IpRNZ{ptLtL(gQ-CY~4mqW;US7Zxvm_|@yz&e53Bp_lTPlfP|z zrTyx_>lv@x#=^!PzR7qqF<$gm`|ZJZ+;<)Cqu&ot2z=00004XF*Lt006O$eEU(80000WV@Og>004R=004l4008;_004mL004C` z008P>0026e000+nl3&F}000FhNklNdu^#FJPzS6b1 z#Bo=fEdcza?_Tt|mL-5E1q{9fkOFued+^VkI{>gE61<5{dv3yWRN#UmzzhEiuN>1H zKs+$NHh=)Y9sT6Op_g}Jw>f|x9J^gALZD5veq@FIcL2`-_G5WOn*BlzJ&m9{$IWCG zjcm68fPiDS3kAo`ra^lnkqjz2EA-z1WFkCsMQ4Tn0l@pj95;6RZiW7qJg#=)YrFZ3 z)(yQw4=eOvNOX>vsIkI}0KCmSv9_IutE>1L9Qp{52H?GCyf08+cn1InbW5I0C$5NWdPyj zt>0h8)Rhz7dH~@aQP=MN$KUm5;G+h(Lic*$B>^7Wby1G^{7Z$^3j^iQ7r5&&V0Y+N z2YLc8u~MQ=7spkS9j7!T8dIyMF;-J>sfh3#^s9@;0G|I*D9=yM831?$zaD%5@ZaQ~ zkBs>UAhkmOnHdrW9Z6X;F0lY`KegxtYWqLO&d88)1f{jTZ!oak-a>~NZ8%}2A1 z&z$kx4qlH#h%ds^%IgI^c+Pv;?;gMd^YF*!m)R07B*2()sQr(%9*2~TO8ZL%-3|Ck z?E3DPz?ook@>oM+N8Xf^yO>>kLx*`QCMn|e z^a(j#@RDiC2+>=~jNUvI#5Xit#xaGMv{vw#$Bh-;{9uNj?oz~uHD#}+TI*V(pI+cB zD@KcMswB&;kd-@hjPZPw0TY-H&eCG+=qBel3X{T45ue~Q{8I6v7Q%}_&>N+QPav2F zM-iVuFb~{Y7hfqhAkYcMh;OKELjog1yw%9p#PNKkX?4C5*VlpeRg!JQrnSM(slvi8 zpc0qOIJ7Wr&6lf0j6fNV?V&s2wGc2PwcIrEaW-muV$WJFFLLIg;YgRnxx=C`YRyMT znV~}6E!#Tvf(9>rMd?auR3|Pe1wPToKlWcBb3((QMW5B zZ%TYb&K`A-&{9m*XaV|AuM6F-O0xUUT39S@gq$38o9?}ss<|O(m1OsdgrNm_yX~b9 zEpCjQO-qF03C-j=C60G9aC`*tP$k*7E*b6R4U%)Db>N0-dMngfO;=3UoQW2|7QmM3 zd3PA^;ix5ryUDdBq$RE|NS6a&_-yBI9(>XK-Kyz0^wt;6L^&sypM_sze!dIGF@TtM zwRre=+?UtGW((A{!Msn+R_aZHn*|B7nOyBpCffWYcQ6=!4*=C@-bCZ`caH!7002ov JPDHLkV1h4pvfBUv literal 0 HcmV?d00001 From d3e60b3957c0de1e239711bf49a0e92b6c7f424a Mon Sep 17 00:00:00 2001 From: Zen Tormey Date: Fri, 2 Sep 2016 17:02:05 -0500 Subject: [PATCH 72/77] Update sensor.sabnzbd.markdown (#887) Added clarification about the name of the sensors created to help new users who might expect the sensor name and component name to match. Also, it would seem that after 0.27, configuration of this component may have changed. Using "http" or "https" as indicated in the documentation seems to raise an exception. Using the port number on the host line also causes an error. Omitting this (at least without SSL) seems to fix the issue. I don't know enough about how this component work to troubleshoot, so I left that part as-is. Maybe someone who knows this component better could take a look? --- source/_components/sensor.sabnzbd.markdown | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/source/_components/sensor.sabnzbd.markdown b/source/_components/sensor.sabnzbd.markdown index 37534aaf4a7..15139b77a0e 100644 --- a/source/_components/sensor.sabnzbd.markdown +++ b/source/_components/sensor.sabnzbd.markdown @@ -48,3 +48,14 @@ Configuration variables: - **queue_remaining**: Remaining elements in the queue - **disk_size**: Disk size of the storage location - **disk_free**: Free disk space at the sotrage location + +Note that this will create sensors under the name 'sab' and NOT 'sabnzbd' as follows: +``` + - sensor.sab_status + - sensor.sab_speed + - sensor.sab_queue + - sensor.sab_left + - sensor.sab_disk + - sensor.sab_disk_free +``` +As always, you can determine the names of sensors by looking at the dev-state page `< >` in the web interface. From 520b761f0dc291dabed62d5d3476fd7f6ae52db2 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 3 Sep 2016 00:05:00 +0200 Subject: [PATCH 73/77] Update variable description --- source/_components/sensor.sabnzbd.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.sabnzbd.markdown b/source/_components/sensor.sabnzbd.markdown index 15139b77a0e..1be51e231a2 100644 --- a/source/_components/sensor.sabnzbd.markdown +++ b/source/_components/sensor.sabnzbd.markdown @@ -37,8 +37,8 @@ sensor: Configuration variables: -- **host** (*Required*): This is the base URL of your SABnzbd instance including the port number if not running on 80, eg. http://192.168.1.32:8124/ -- **port** (*Optional*): The port to use whith SABnzbd instance. Defaults to 8080. +- **host** (*Required*): The host where your SABnzbd instance is running, eg. 192.168.1.32 +- **port** (*Optional*): The port to use whith SABnzbd instance. Defaults to `8080`. - **api_key** (*Required*): Name that will be used in the frontend for the pin. - **name** (*Optional*): The name to use when displaying this SABnzbd instance. - **monitored_variables** array (*Required*): List of the monitored variables. @@ -50,6 +50,7 @@ Configuration variables: - **disk_free**: Free disk space at the sotrage location Note that this will create sensors under the name 'sab' and NOT 'sabnzbd' as follows: + ``` - sensor.sab_status - sensor.sab_speed @@ -58,4 +59,5 @@ Note that this will create sensors under the name 'sab' and NOT 'sabnzbd' as fol - sensor.sab_disk - sensor.sab_disk_free ``` + As always, you can determine the names of sensors by looking at the dev-state page `< >` in the web interface. From feee2175ba9dd5610a5ae0a9c5e8ad7cad0c7eb0 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 3 Sep 2016 18:44:25 +0200 Subject: [PATCH 74/77] Delete basic_example_use_trigger_values.markdown --- .../basic_example_use_trigger_values.markdown | 41 ------------------- 1 file changed, 41 deletions(-) delete mode 100644 source/_cookbook/basic_example_use_trigger_values.markdown diff --git a/source/_cookbook/basic_example_use_trigger_values.markdown b/source/_cookbook/basic_example_use_trigger_values.markdown deleted file mode 100644 index 7c062317aac..00000000000 --- a/source/_cookbook/basic_example_use_trigger_values.markdown +++ /dev/null @@ -1,41 +0,0 @@ ---- -layout: page -title: "Example using use_trigger_values" -description: "Basic example how to use use_trigger_values in automation" -date: 2015-10-08 19:05 -sidebar: true -comments: false -sharing: true -footer: true -ha_category: Automation Examples ---- - -Turn on lights during daytime when it's dark enough < 200 lux. - -```yaml -automation: - - alias: - trigger: - - platform: numeric_state - entity_id: sensor.sensor_luminance - below: 200 - - platform: time - after: "08:00" - before: "23:00" - condition: use_trigger_values - action: - service: homeassistant.turn_on - entity_id: group.basic_lights - -automation 2: - - alias: - trigger: - - platform: numeric_state - entity_id: sensor.sensor_luminance - above: 200 - - platform: time - after: "23:00" - action: - service: homeassistant.turn_off - entity_id: group.basic_lights -``` From b3e1607ba2291706ad7694f3fa4d800a7a17c706 Mon Sep 17 00:00:00 2001 From: Josh Nichols Date: Sat, 3 Sep 2016 13:30:27 -0400 Subject: [PATCH 75/77] Recommend to assign a static IP for emulated_hue component (#890) --- source/_components/emulated_hue.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/emulated_hue.markdown b/source/_components/emulated_hue.markdown index facee1929f4..0d1af6ce973 100755 --- a/source/_components/emulated_hue.markdown +++ b/source/_components/emulated_hue.markdown @@ -15,6 +15,10 @@ ha_iot_class: "Local Push" The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo with no set up cost outside of configuration changes. +

    + It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresss, and if the IP changes, the Echo won't be able to control it. This is easiest done from your router, see your router's manual for details. +

    + ### {% linkable_title Configuration %} To enable the emulated Hue bridge, add the following to your `configuration.yaml` file: From 3bcfbcebb372ab74e7fa629afbe199b9a8b7fc80 Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Sat, 3 Sep 2016 16:03:37 -0700 Subject: [PATCH 76/77] Update release post to add 0.27.2 --- ...otifications-hue-fake-unification.markdown | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown index 9ca0502c6d4..91ca62a53e2 100644 --- a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown +++ b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown @@ -176,6 +176,28 @@ Talk to you soon on Gitter and in your pull request comments! - fix voluptuous and cover autodiscovery ([@pvizeli]) - Fixes wrong statevalue and problem with zwave setpoint ([@turbokongen]) +## {% linkable_title Hotfix 0.27.2 - September 3 %} +### home-assistant + +- Ble fix ([#3019](https://github.com/home-assistant/home-assistant/pull/3019)) - ([@open-homeautomation](https://github.com/open-homeautomation)) +- Reset insteon hub ([#3062](https://github.com/home-assistant/home-assistant/pull/3062)) - ([@Teagan42](https://github.com/Teagan42)) +- Host should be optional for apcupsd component ([#3072](https://github.com/home-assistant/home-assistant/pull/3072)) - ([@Danielhiversen](https://github.com/Danielhiversen)) +- Zwave climate Bugfix: if some setpoints have different units, we should fetch the o… ([#3078](https://github.com/home-assistant/home-assistant/pull/3078)) - ([@turbokongen](https://github.com/turbokongen)) +- Bugfix unit fix ([#3083](https://github.com/home-assistant/home-assistant/pull/3083)) - ([@turbokongen](https://github.com/turbokongen)) +- Ecobee humidity slider ([#3088](https://github.com/home-assistant/home-assistant/pull/3088)) - ([@turbokongen](https://github.com/turbokongen)) +- Zwave Climate Bugfix: If device was off target temp was null. Default to Heating setpoint ([#3091](https://github.com/home-assistant/home-assistant/pull/3091)) - ([@turbokongen](https://github.com/turbokongen)) +- Climate and cover bugfix ([#3097](https://github.com/home-assistant/home-assistant/pull/3097)) - ([@turbokongen](https://github.com/turbokongen)) +- Add missing docstrings (fix PEP257 issues) ([#3098](https://github.com/home-assistant/home-assistant/pull/3098)) - ([@fabaff](https://github.com/fabaff)) +- Allow None MAC to be loaded from known_devices ([#3102](https://github.com/home-assistant/home-assistant/pull/3102)) - ([@kellerza](https://github.com/kellerza)) +- fix homematic climate implementation ([#3114](https://github.com/home-assistant/home-assistant/pull/3114)) - ([@pvizeli](https://github.com/pvizeli)) +- Fixed Homematic cover ([#3116](https://github.com/home-assistant/home-assistant/pull/3116)) - ([@danielperna84](https://github.com/danielperna84)) +- Bugfix. climate and covermqt ([#3130](https://github.com/home-assistant/home-assistant/pull/3130)) - ([@turbokongen](https://github.com/turbokongen)) + +### home-assistant-polymer + +- Fix missing attributes on the climate and HVAC more info cards ([7e455e2](https://github.com/home-assistant/home-assistant-polymer/commit/7e455e2be1cb7cc4f55628b063019bea548a3182)) - ([@robbiet480](https://github.com/robbiet480)) +- Add a default icon for the fan component ([#101](https://github.com/home-assistant/home-assistant-polymer/pull/101)) - ([@robbiet480](https://github.com/robbiet480)) + [@arsaboo]: https://github.com/arsaboo [@auchter]: https://github.com/auchter [@balloob]: https://github.com/balloob From 1e10f23003ecb9c5f9937d5983332a72400174e3 Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Sat, 3 Sep 2016 16:07:56 -0700 Subject: [PATCH 77/77] Update index.html to point to 0.27.2 --- source/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/index.html b/source/index.html index 3e8428bd3a4..79d75e71d21 100644 --- a/source/index.html +++ b/source/index.html @@ -15,8 +15,8 @@ hide_github_edit: true
    -

    Current Version: 0.27.1

    - Released: August 30, 2016 +

    Current Version: 0.27.2

    + Released: September 3, 2016
    Release notes