From ab3772913cc4d27e3e501672a6ea60c1a7df3903 Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Sat, 25 Nov 2017 14:41:05 +0100 Subject: [PATCH 01/59] Fix HTML5 notify domain verification instructions Didn't say you need to restart. Can't get the internal link working --- source/_components/notify.html5.markdown | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 34547169778..52f800e9a7f 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -33,19 +33,23 @@ Configuration variables: ### {% linkable_title Getting ready for Chrome %} -1. Create new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). -2. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain. -3. After that, go to [https://console.firebase.google.com](https://console.firebase.google.com) and select import Google project, select the project you created. -4. Then, click the cogwheel on top left and select "Project settings". -5. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID'. +1. Make sure you can access your Home Assistant installation from outside your network over https ([see docs](https://home-assistant.io/docs/configuration/remote/)). +2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). +3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [hass.io instructions](#verify-your-domain-with-hassio). +4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project, and select the project you created. +5. Then, click the cogwheel on top left and select "Project settings". +6. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID'. #### {% linkable_title Verify your domain with Hass.io %} -1. For verifying your domain you need to download a file in step 2. -2. Create a dictionary named "www" in you Hass.io configuration dictionary. -3. Place the file (something like this: google*.html) in the "www" directory. -4. You can open it by going to **https://yourdomain/local/exact_file_name.html** -5. Proceed with step 3. +Follow these steps to verify domain ownership with Google Webmaster Central / Search Console: +1. Enter your domain and add **'/local'** at the end, ie. https://whitehouse.duckdns.org:8123/local +2. Select HTML file verification and download the google*.html file. +2. Create a directory named "www" in your Hass.io configuration directory (/config share from Samba add-on). +3. Place the downloaded google*.html file in the "www" directory. +4. RESTART Home Assistant - this is important! +5. Verify the file can be accessed in the browser, ie. **https://whitehouse.duckdns.org:8123/local/goole123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps. +6. Go back to Google Webmaster Central / Search Console and proceed with the verification. ### {% linkable_title Requirements %} From 27bf0fa0b4a9bcac972a7cd6fe97e28cd19af6bf Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Sat, 25 Nov 2017 14:44:15 +0100 Subject: [PATCH 02/59] update on requirements --- source/_components/notify.html5.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 52f800e9a7f..2b75901d10c 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -54,12 +54,11 @@ Follow these steps to verify domain ownership with Google Webmaster Central / Se ### {% linkable_title Requirements %} The `html5` platform can only function if all of the following requirements are met: -(On Hass.io these requirements are already met.) * You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android. * Your Home Assistant instance is exposed to the world. * If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards. -* `pywebpush` must be installed. `libffi-dev`, `libpython-dev`, and `libssl-dev` must be installed prior to `pywebpush` (i.e. `pywebpush` probably won't automatically install). +* If you don't run Hass.io: `pywebpush` must be installed. `libffi-dev`, `libpython-dev`, and `libssl-dev` must be installed prior to `pywebpush` (i.e. `pywebpush` probably won't automatically install). * You have configured SSL for your Home Assistant. It doesn't need to be configured in Home Assistant though, i.e. you can be running [NGINX](/ecosystem/nginx/) in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed). * You are willing to accept the notification permission in your browser. From 52cb747bdef1a9b0ff404ff6b80acfec3c0e0f8f Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Sat, 25 Nov 2017 14:48:34 +0100 Subject: [PATCH 03/59] Update notify.html5.markdown --- source/_components/notify.html5.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 2b75901d10c..8331ad249fd 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -38,7 +38,7 @@ Configuration variables: 3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [hass.io instructions](#verify-your-domain-with-hassio). 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project, and select the project you created. 5. Then, click the cogwheel on top left and select "Project settings". -6. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID'. +6. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID' you need for configuring this component. #### {% linkable_title Verify your domain with Hass.io %} From 26754ea34011324dd48504c0e63a2d31a3255cda Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jens=20=C3=98stergaard=20Nielsen?= Date: Fri, 26 Jan 2018 23:05:10 +0100 Subject: [PATCH 04/59] IHC component (#4520) * New IHC platform * autosetup -> auto_setup * Moved auto setup to the IHC component * Removed by LK in logo * Changes from review. * Defaults in configurations. manualy setup" changed to "manual setup" (Anchors adjusted) * Relative links changed to absolute links * 'host' renamed to 'url' * :pencil2: Tweaks --- source/_components/ihc.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_components/ihc.markdown b/source/_components/ihc.markdown index 7bffc484155..0030d30361f 100644 --- a/source/_components/ihc.markdown +++ b/source/_components/ihc.markdown @@ -21,7 +21,7 @@ An `ihc` section must be present in the `configuration.yaml` file and contain th ```yaml # Example configuration.yaml entry ihc: - host: http://192.168.1.3 + url: http://192.168.1.3 username: admin password: mysecret auto_setup: True @@ -33,10 +33,6 @@ auto_setup: description: True to have IHC products auto setup. required: false type: bool -host: - description: The URL of the IHC Controller. - required: true - type: string info: description: If True additional IHC info will be shown on each component. required: false @@ -45,6 +41,10 @@ password: description: The password for the IHC Controller. required: true type: string +url: + description: The URL of the IHC Controller. + required: true + type: string username: description: The username for the IHC Controller. required: true @@ -63,7 +63,7 @@ There is currently support for the following device types within Home Assistant: ### Auto setup of IHC products -If auto setup is enabled, the `ihc` component will automatically find IHC products and insert these as devices in Home Assistant. +If the auto setup is enabled, the `ihc` component will automatically find IHC products and insert these as devices in Home Assistant. To disable this set auto_setup to False. (Auto setup is on by default) See the individual device types for a list of IHC products to be recognized automatically. @@ -87,4 +87,4 @@ The IHC resource id should be specified as an integer value. (In the project fil If you want an easier way to get the IHC resource ids, you can download the [Alternative Service View application](https://www.dingus.dk/updated-ihc-alternative-service-view/). The application will show the product tree. You can expand it, select inputs and outputs and when selected you can see the resource id. -See each device type for the manual configuration options. +See the manual of each device type for configuration options. From a43ec05a4dd5e210d88b093acc349fba3dec293c Mon Sep 17 00:00:00 2001 From: Nolan Gilley Date: Fri, 26 Jan 2018 16:12:31 -0500 Subject: [PATCH 05/59] add erc20 token (#4523) * add erc20 token * :pencil2: Minor corrections --- source/_components/sensor.etherscan.markdown | 23 +++++++++++++++----- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/source/_components/sensor.etherscan.markdown b/source/_components/sensor.etherscan.markdown index fcdc5387059..a94f0689a2f 100644 --- a/source/_components/sensor.etherscan.markdown +++ b/source/_components/sensor.etherscan.markdown @@ -13,16 +13,22 @@ ha_release: 0.47 ha_iot_class: "Cloud Polling" --- +The `Etherscan` sensor platform displays Ether and ERC-20 token balances from [Etherscan.io](https://etherscan.io). -The `Etherscan` sensor platform displays Ethereum wallet balances from [Etherscan.io](https://etherscan.io). - -To add the Etherscan sensor to your installation, specify an ethereum address to watch in the `configuration.yaml` file: +To add the Etherscan sensor to your installation, specify an Ethereum address to watch in the `configuration.yaml` file. You can also optionally provide a token name to retrieve and ERC-20 token balance. If no token is provided then the balance retrieved will be in ETH. You can also optionally provide the token contract address in case the token name is not found. ```yaml # Example configuration.yaml entry sensor: - platform: etherscan address: '0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359' + - platform: etherscan + address: "0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359" + token: OMG + - platform: etherscan + address: "0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359" + token_address: "0xef68e7c694f40c8202821edf525de3782458639f" + token: LRC ``` {% configuration %} @@ -34,6 +40,13 @@ name: description: The name of the sensor used in the frontend. required: false type: string - default: Ethereum Balance + default: ETH Balance +token: + description: The ERC20 token symbol. i.e., OMG. + required: false + type: string +token_address: + description: The ERC20 token contract address. + required: false + type: string {% endconfiguration %} - From d300a9dc44f074e2688171f02e16474caa5930bf Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 27 Jan 2018 00:30:24 -0800 Subject: [PATCH 06/59] Add Discourse for comments --- _config.yml | 3 +++ source/_includes/article.html | 2 +- source/_includes/blog/post/article.html | 2 +- source/_includes/javascripts/scripts.html | 4 ++++ source/_layouts/post.html | 19 ++++++++++++++++++- 5 files changed, 27 insertions(+), 3 deletions(-) diff --git a/_config.yml b/_config.yml index 673e9d8eacd..732f3e54776 100644 --- a/_config.yml +++ b/_config.yml @@ -148,3 +148,6 @@ date_released: 2018-01-27 # Major release: patch_version_notes: "#" # Minor release (Example #release-0431---april-25): + +# Date we moved to Discourse for comments +disqus_end_date: 2018-01-26 0:00:00 diff --git a/source/_includes/article.html b/source/_includes/article.html index b7a6e0e2edb..f88d16cc9c4 100644 --- a/source/_includes/article.html +++ b/source/_includes/article.html @@ -9,7 +9,7 @@

{% include post/date.html %}{{ time }} {% if site.disqus_short_name and page.comments != false and post.comments != false and site.disqus_show_comment_count == true %} - | Comments {% endif %}

diff --git a/source/_includes/blog/post/article.html b/source/_includes/blog/post/article.html index 2cef69f00ea..ed236247662 100644 --- a/source/_includes/blog/post/article.html +++ b/source/_includes/blog/post/article.html @@ -15,7 +15,7 @@ {% include blog/post/tags.html %} {% if site.disqus_short_name and page.comments != false and post.comments != false and site.disqus_show_comment_count == true %} Comments {% endif %} diff --git a/source/_includes/javascripts/scripts.html b/source/_includes/javascripts/scripts.html index 32903641a22..71b49ae662e 100644 --- a/source/_includes/javascripts/scripts.html +++ b/source/_includes/javascripts/scripts.html @@ -4,7 +4,11 @@ {% endcomment %} {% include javascripts/google_analytics.html %} + +{% if site.disqus_short_name and post.date < site.disqus_end_date and page.comments == true %} {% include javascripts/disqus.html %} +{% endif %} + {% include javascripts/algolia.html %} {% if page.sidebar != false %} diff --git a/source/_layouts/post.html b/source/_layouts/post.html index 9d5c8e41ad5..3ba1b0b4e6b 100644 --- a/source/_layouts/post.html +++ b/source/_layouts/post.html @@ -8,9 +8,26 @@ is_post: true {% include blog/post/article.html %} -{% if site.disqus_short_name and page.comments == true %} +
+ +{% if site.disqus_short_name and post.date < site.disqus_end_date and page.comments == true %}

Comments

{% include blog/post/disqus_thread.html %}
+{% endif %} + +{% if page.comments == true and post.date > site.disqus_end_date %} +
+ + {% endif %} \ No newline at end of file From b18f20e6f334c8e670129df1b5b79ed7da98cb4b Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 27 Jan 2018 00:42:37 -0800 Subject: [PATCH 07/59] Update breaking change --- source/_posts/2018-01-27-release-62.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2018-01-27-release-62.markdown b/source/_posts/2018-01-27-release-62.markdown index 60a7f006010..95815a31048 100644 --- a/source/_posts/2018-01-27-release-62.markdown +++ b/source/_posts/2018-01-27-release-62.markdown @@ -43,7 +43,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - Tahoma platform will get new entity IDs ([@glpatcern] - [#11547]) ([tahoma docs]) ([cover.tahoma docs]) (breaking change) - Mold indicator: attribute names no longer include spaces or periods ([@olskar] - [#11694]) ([sensor.mold_indicator docs]) (breaking change) -- Custom component devs only: `EntityComponent.add_entity(entity)` and `EntityComponent.async_add_entity(entity)` have been removed. Use `EntityComponent.add_entities([entity])` and `EntityComponent.async_add_entities([entity])` instead. ([@balloob] - [#11691]) (breaking change) +- Custom component devs only: `EntityComponent.add_entity(entity)` and `EntityComponent.async_add_entity(entity)` have been removed. Use `EntityComponent.add_entities([entity])` and `EntityComponent.async_add_entities([entity])` instead. Also `EntityComponent.entities` is no longer a dictionary but instead an iterable. Use `EntityComponent.get_entity(entity_id)` to get entity by id. ([@balloob] - [#11691]) (breaking change) ## All changes From e66d5b81d2afcfb09bb16b63b3f059f98a59ce42 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 27 Jan 2018 01:01:24 -0800 Subject: [PATCH 08/59] Fix disqus comments --- source/_includes/javascripts/scripts.html | 5 ----- source/_layouts/post.html | 2 ++ 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/source/_includes/javascripts/scripts.html b/source/_includes/javascripts/scripts.html index 71b49ae662e..dcb2fc520a1 100644 --- a/source/_includes/javascripts/scripts.html +++ b/source/_includes/javascripts/scripts.html @@ -4,11 +4,6 @@ {% endcomment %} {% include javascripts/google_analytics.html %} - -{% if site.disqus_short_name and post.date < site.disqus_end_date and page.comments == true %} -{% include javascripts/disqus.html %} -{% endif %} - {% include javascripts/algolia.html %} {% if page.sidebar != false %} diff --git a/source/_layouts/post.html b/source/_layouts/post.html index 3ba1b0b4e6b..27171790019 100644 --- a/source/_layouts/post.html +++ b/source/_layouts/post.html @@ -15,6 +15,8 @@ is_post: true

Comments

{% include blog/post/disqus_thread.html %}
+ +{% include javascripts/disqus.html %} {% endif %} {% if page.comments == true and post.date > site.disqus_end_date %} From 7a805853a3b6ff9939334a0f85fef2392988f849 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 27 Jan 2018 13:44:30 +0100 Subject: [PATCH 09/59] Replaced with local saved version --- source/_faq/release.markdown | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/_faq/release.markdown b/source/_faq/release.markdown index 5abcafcee59..f109e5468d0 100644 --- a/source/_faq/release.markdown +++ b/source/_faq/release.markdown @@ -10,7 +10,5 @@ footer: true ha_category: Common --- -The usual release cycle is two weeks. - - -There will be no support for Python 2.x. Python 2 will be EOL in [2020](https://www.python.org/dev/peps/pep-0373/#id2) and it doesn't make any sense to support a release which was planned to be retired in 2015. +The usual release cycle is two weeks. Every other weekend will a new release of Home Assistant be available. There is no fix day or time when the release will happen because that depends on the person who is finishing the release. It can already be Monday at your location. If there was no announcement made in the previous release notes or on another communication channel then the release will happen. + From 4c45677ce13384f101282f055c994ee0845084d9 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 27 Jan 2018 14:34:38 +0100 Subject: [PATCH 10/59] Add section with firmware releases that supports discovery --- source/_docs/mqtt/discovery.markdown | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index e9139095d75..26ddd658c3d 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -51,6 +51,14 @@ The payload will be checked like an entry in your `configuration.yaml` file if a The `` level can be used by clients to only subscribe to their own (command) topics by using one wildcard topic like `/+//+/set`. +### {% linkable_title Support by third-party tools %} + +The following firmware for ESP8266, ESP32 and Sonoff unit has built-in support for MQTT discovery: + +- [Sonoff-Tasmota](https://github.com/arendst/Sonoff-Tasmota) (starting with 5.11.1e) +- [esphomelib](https://github.com/OttoWinter/esphomelib) +- [ESPurna](https://bitbucket.org/xoseperez/espurna) + ### {% linkable_title Examples %} A motion detection device which can be represented by a [binary sensor](/components/binary_sensor.mqtt/) for your garden would sent its configuration as JSON payload to the Configuration topic. After the first message to `config`, then the MQTT messages sent to the state topic will update the state in Home Assistant. @@ -93,3 +101,5 @@ Setting up a sensor with multiple measurement values requires multiple consecuti - Configuration topic no2: `homeassistant/sensor/sensorBedroomH/config` - Configuration payload no2: `{"device_class": "sensor", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{% raw %}{{ value_json.humidity}}{% endraw %}" }` - Common state payload: `{ "temperature": 23.20, "humidity": 43.70 }` + + From 50e4cec1fffdfee9e823e555a2c2da6c9616c067 Mon Sep 17 00:00:00 2001 From: Jerry Workman Date: Sat, 27 Jan 2018 12:18:16 -0500 Subject: [PATCH 11/59] Fix symbolic links, permissions and ownership (#4528) Fix symbolic links to python3 and homeassistant executable. Fix permissions and ownership to homeassistant directory to allow writing to home-assistant.log. --- source/_docs/installation/synology.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_docs/installation/synology.markdown b/source/_docs/installation/synology.markdown index 34e228ebb59..9edf9fbb001 100644 --- a/source/_docs/installation/synology.markdown +++ b/source/_docs/installation/synology.markdown @@ -61,6 +61,8 @@ Create homeassistant config directory & switch to it ```bash # mkdir /volume1/homeassistant +# chown /volume1/homeassistant homeassistant +# chmod 755 /volume1/homeassistant # cd /volume1/homeassistant ``` Hint: alternatively you can also create a "Shared Folder" via Synology WebUI (e.g. via "File Station") - this has the advantage that the folder is visible via "File Station". @@ -175,8 +177,8 @@ esac Create links to python folders to make things easier in the future: ```bash -# ln -s /volume1/@appstore/py3k/usr/local/bin python3 -# ln -s /volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/homeassistant +# ln -s /volume1/@appstore/py3k/usr/local/bin/python3 python3 +# ln -s /volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/homeassistant homeassistant ``` Set the owner and permissions on your config folder From a964ae5ac813246ba319149d16adb45058dd94f7 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 27 Jan 2018 20:26:47 +0100 Subject: [PATCH 12/59] Add examples for ESPEasy (#4527) * Add sensor example * Small changes * Add ESPEasy example * Add ESPEasy example * Fixes * :pencil2: Minor improvements --- .../_components/binary_sensor.mqtt.markdown | 40 +++++++++++++++++-- source/_components/sensor.mqtt.markdown | 38 ++++++++++++++++-- source/_components/switch.mqtt.markdown | 28 ++++++++++++- 3 files changed, 98 insertions(+), 8 deletions(-) diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown index 65058598382..b9b0b2ba55b 100644 --- a/source/_components/binary_sensor.mqtt.markdown +++ b/source/_components/binary_sensor.mqtt.markdown @@ -13,12 +13,11 @@ ha_release: 0.9 ha_iot_class: "depends" --- - The `mqtt` binary sensor platform uses an MQTT message payload to set the binary sensor to one of two states: `on` or `off`. The binary sensor state will be updated only after a new message is published on `state_topic` matching `payload_on` or `payload_off`. If these messages are published with the `retain` flag set, the binary sensor will receive an instant state update after subscription and Home Assistant will display the correct state on startup. Otherwise, the initial state displayed in Home Assistant will be `unknown`. -The `mqtt` binary sensor platform optionally supports an `availability_topic` to receive online and offline messages (birth and LWT messages) from the MQTT device. During normal operation, if the MQTT cover device goes offline (i.e. publishes `payload_not_available` to `availability_topic`), Home Assistant will display the binary sensor as `unavailable`. If these messages are published with the `retain` flag set, the binary sensor will receive an instant update after subscription and Home Assistant will display the correct availability state of the binary sensor when Home Assistant starts up. If the `retain` flag is not set, Home Assistant will display the binary sensor as `unavailable` when Home Assistant starts up. If no `availability_topic` is defined, Home Assistant will consider the MQTT device to be available. +The `mqtt` binary sensor platform optionally supports an `availability_topic` to receive online and offline messages (birth and LWT messages) from the MQTT device. During normal operation, if the MQTT cover device goes offline (i.e., publishes `payload_not_available` to `availability_topic`), Home Assistant will display the binary sensor as `unavailable`. If these messages are published with the `retain` flag set, the binary sensor will receive an instant update after subscription and Home Assistant will display the correct availability state of the binary sensor when Home Assistant starts up. If the `retain` flag is not set, Home Assistant will display the binary sensor as `unavailable` when Home Assistant starts up. If no `availability_topic` is defined, Home Assistant will consider the MQTT device to be available. To use an MQTT binary sensor in your installation, add the following to your `configuration.yaml` file: @@ -78,6 +77,13 @@ value_template: type: string {% endconfiguration %} + +## {% linkable_title Examples %} + +In this section, you will find some real-life examples of how to use this sensor. + +### {% linkable_title Full configuration %} + To test, you can use the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages. To set the state of the binary sensor manually: ```bash @@ -86,6 +92,7 @@ $ mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m "OFF" The example below shows a full configuration for a binary sensor: +{% raw %} ```yaml # Example configuration.yaml entry binary_sensor: @@ -99,5 +106,32 @@ binary_sensor: payload_not_available: "offline" qos: 0 device_class: opening - value_template: '{% raw %}{{ value.x }}{% endraw %}' + value_template: '{{ value.x }}' ``` +{% endraw %} + +### {% linkable_title Get the state of a device with ESPEasy %} + +Assuming that you have flashed your ESP8266 unit with [ESPEasy](https://github.com/letscontrolit/ESPEasy). Under "Config" is a name ("Unit Name:") set for your device (here it's "bathroom"). A configuration for a "Controller" for MQTT with the protocol "OpenHAB MQTT" is present and the entries ("Controller Subscribe:" and "Controller Publish:") are adjusted to match your needs. In this example, the topics are prefixed with "home". Also, add a "Switch Input" in the "Devices" tap with the name "switch" and "button" as value. + +As soon as the unit is online, you will get the state of the attached button. + +```bash +home/bathroom/status Connected +... +home/bathroom/switch/button 1 +``` + +The configuration will look like the example below: + +{% raw %} +```yaml +# Example configuration.yml entry +binary_sensor: + - platform: mqtt + name: Bathroom + state_topic: "home/bathroom/switch/button" + payload_on: "1" + payload_off: "0" +``` +{% endraw %} diff --git a/source/_components/sensor.mqtt.markdown b/source/_components/sensor.mqtt.markdown index 2f80c563b15..e6b96b3bc1d 100644 --- a/source/_components/sensor.mqtt.markdown +++ b/source/_components/sensor.mqtt.markdown @@ -90,8 +90,9 @@ If you are using the [Owntracks](/components/device_tracker.owntracks/) and enab owntracks/tablet/tablet {"_type":"location","lon":7.21,"t":"u","batt":92,"tst":144995643,"tid":"ta","acc":27,"lat":46.12} ``` -Thus the trick is extract the battery level from the payload. +Thus the trick is extracting the battery level from the payload. +{% raw %} ```yaml # Example configuration.yml entry sensor: @@ -99,8 +100,9 @@ sensor: state_topic: "owntracks/tablet/tablet" name: "Battery Tablet" unit_of_measurement: "%" - value_template: {% raw %}'{{ value_json.batt }}'{% endraw %} + value_template: '{{ value_json.batt }}' ``` +{% endraw %} ### {% linkable_title Get temperature and humidity %} @@ -116,6 +118,7 @@ office/sensor1 Then use this configuration example to extract the data from the payload: +{% raw %} ```yaml # Example configuration.yml entry sensor: @@ -123,10 +126,37 @@ sensor: state_topic: 'office/sensor1' name: 'Temperature' unit_of_measurement: '°C' - value_template: {% raw %}'{{ value_json.temperature }}'{% endraw %} + value_template: '{{ value_json.temperature }}' - platform: mqtt state_topic: 'office/sensor1' name: 'Humidity' unit_of_measurement: '%' - value_template: {% raw %}'{{ value_json.humidity }}'{% endraw %} + value_template: '{{ value_json.humidity }}' ``` +{% endraw %} + +### {% linkable_title Get sensor value from a device with ESPEasy %} + +Assuming that you have flashed your ESP8266 unit with [ESPEasy](https://github.com/letscontrolit/ESPEasy). Under "Config" set a name ("Unit Name:") for your device (here it's "bathroom"). A "Controller" for MQTT with the protocol "OpenHAB MQTT" is present and the entries ("Controller Subscribe:" and "Controller Publish:") are adjusted to match your needs. In this example the topics are prefixed with "home". Also, add a sensor in the "Devices" tap with the name "analog" and "brightness" as value. + +As soon as the unit is online, you will get the state of the sensor. + +```bash +home/bathroom/status Connected +... +home/bathroom/analog/brightness 290.00 +``` + +The configuration will look like the example below: + +{% raw %} +```yaml +# Example configuration.yml entry +sensor: + - platform: mqtt + state_topic: 'home/bathroom/analog/brightness' + name: Brightness +``` +{% endraw %} + + diff --git a/source/_components/switch.mqtt.markdown b/source/_components/switch.mqtt.markdown index 3804130cc61..17430c9c8f5 100644 --- a/source/_components/switch.mqtt.markdown +++ b/source/_components/switch.mqtt.markdown @@ -119,5 +119,31 @@ switch: For a check you can use the command line tools `mosquitto_pub` shipped with `mosquitto` to send MQTT messages. This allows you to operate your switch manually: ```bash -$ mosquitto_pub -h 127.0.0.1 -t home/bedroom/switch1 -m "ON" +$ mosquitto_pub -h 127.0.0.1 -t home/bedroom/switch1 -m "ON" ``` + +### {% linkable_title Set the state of a device with ESPEasy %} + +Assuming that you have flashed your ESP8266 unit with [ESPEasy](https://github.com/letscontrolit/ESPEasy). Under "Config" is a name ("Unit Name:") set for your device (here it's "bathroom"). A configuration for a "Controller" for MQTT with the protocol "OpenHAB MQTT" is present and the entries ("Controller Subscribe:" and "Controller Publish:") are adjusted to match your needs. In this example the topics are prefixed with "home". There is no further configuration needed as the [GPIOs](https://www.letscontrolit.com/wiki/index.php/GPIO) can be controlled with MQTT directly. + +Manually you can set pin 13 to high with `mosquitto_pub` or another MQTT tool: + +```bash +$ mosquitto_pub -h 127.0.0.1 -t home/bathroom/gpio/13 -m "1" +``` + +The configuration will look like the example below: + +{% raw %} +```yaml +# Example configuration.yml entry +switch: + - platform: mqtt + name: bathroom + state_topic: "home/bathroom/gpio/13" + command_topic: "home/bathroom/gpio/13" + payload_on: "1" + payload_off: "0" +``` +{% endraw %} + From 9b8f0eacc5e27ab76d9afe31ed9c0f7fed35d222 Mon Sep 17 00:00:00 2001 From: Ronnie Garcia Date: Sat, 27 Jan 2018 20:57:53 +0100 Subject: [PATCH 13/59] Add UV data_type (#4531) --- source/_components/sensor.rfxtrx.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/sensor.rfxtrx.markdown b/source/_components/sensor.rfxtrx.markdown index 6d9089e6127..9df49ee6847 100644 --- a/source/_components/sensor.rfxtrx.markdown +++ b/source/_components/sensor.rfxtrx.markdown @@ -66,6 +66,7 @@ Only these data_type are valid : - *Sound* - *Sensor Status* - *Counter value* +- *UV* Example configuration: From 757eb292f240bb48f25a8b751a132659e19cf400 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Sun, 28 Jan 2018 10:10:52 +0200 Subject: [PATCH 14/59] Update ESPurna home page (#4535) --- source/_docs/mqtt/discovery.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 26ddd658c3d..0fa7a45c040 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -57,7 +57,7 @@ The following firmware for ESP8266, ESP32 and Sonoff unit has built-in support f - [Sonoff-Tasmota](https://github.com/arendst/Sonoff-Tasmota) (starting with 5.11.1e) - [esphomelib](https://github.com/OttoWinter/esphomelib) -- [ESPurna](https://bitbucket.org/xoseperez/espurna) +- [ESPurna](https://github.com/xoseperez/espurna) ### {% linkable_title Examples %} From 28a2b7ea5e1abec9fad16d501656d08890d10579 Mon Sep 17 00:00:00 2001 From: aquarium Date: Sun, 28 Jan 2018 03:12:00 -0500 Subject: [PATCH 15/59] Added KU7000 to supported models (#4539) --- source/_components/media_player.samsungtv.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/media_player.samsungtv.markdown b/source/_components/media_player.samsungtv.markdown index c743a692698..edaec8ca36e 100644 --- a/source/_components/media_player.samsungtv.markdown +++ b/source/_components/media_player.samsungtv.markdown @@ -57,6 +57,7 @@ Currently known supported models: - K6500AF (port must be set to 8001) - KS8005 (port must be set to 8001, and `pip3 install websocket-client` must be executed) - KU6290 (port must be set to 8001) +- KU7000 (port must be set to 8001) - MU6170UXZG (port must be set to 8001, and `pip3 install websocket-client` must be executed) - KS7502 (port must be set to 8001, and `pip3 install websocket-client` must be executed, turn on doesn't work, turn off works fine) - K5600AK (partially supported, turn on works but state is not updated) From 72530aae812ca962a3844d77ff0db2c8cf2d6e6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Sun, 28 Jan 2018 10:12:56 +0200 Subject: [PATCH 16/59] Viera updates (#4536) * panasonic_viera: Add TX-P50GT30Y to known supported models * panasonic_viera: Sort list of known supported models * panasonic_viera: Point to actual source of page on GitHub --- .../media_player.panasonic_viera.markdown | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/source/_components/media_player.panasonic_viera.markdown b/source/_components/media_player.panasonic_viera.markdown index 38cf5f1f8bd..0e58bcb3903 100644 --- a/source/_components/media_player.panasonic_viera.markdown +++ b/source/_components/media_player.panasonic_viera.markdown @@ -18,17 +18,18 @@ The `panasonic_viera` platform allows you to control a Panasonic Viera TV. Currently known supported models: -- TX-P42STW50 - TC-P65VT30 -- TX-55CX700E +- TX-32AS520E - TX-49DX650B - TX-50DX700B -- TX-L42ET50 -- TX-P50GT60E +- TX-55CX700E - TX-65EXW784 -- TX-32AS520E +- TX-L42ET50 +- TX-P42STW50 +- TX-P50GT30Y +- TX-P50GT60E -If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io). +If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/_components/media_player.panasonic_viera.markdown). Some Panasonic Viera TVs allow Home Assistant to turn them on, if you specify the MAC address with `mac:`. From c11484b983e2c30d5c118d64198620e4e557315a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Sun, 28 Jan 2018 11:48:43 +0200 Subject: [PATCH 17/59] getting-started: Add some clarifications, notes and what (not) to expect Note volume where the resin-sample config is on the SD card, note RPI being a 2.4GHz WiFi device, state (non-)expectations about HDMI/keyboard/mouse, encourage browsing to landing page during download. --- source/getting-started/index.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 0c0150e1c02..766e76eef2e 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -35,12 +35,12 @@ We will need a few things to get started with installing Home Assistant. Links b 1. Put the SD card in your SD card reader. 1. Open Etcher, select the Hass.io image and flash it to the SD card. -1. WiFi setup only: open the file `system-connections/resin-sample` with a text editor. Change `ssid` to be your network name and `psk` to be your password. +1. WiFi setup only: open the file `system-connections/resin-sample` (from the `resin-boot` volume on the SD card) with a text editor. Change `ssid` to be your network name and `psk` to be your password. Note that the Raspberry Pi 3 is a 2.4GHz WiFi device, so do not try to connect it to a 5GHz network. 1. Unmount the SD card and remove it from your SD card reader. 1. Insert the SD card into your Raspberry Pi 3. If you are going to use an Ethernet cable, connect that too. 1. Connect your Raspberry Pi to the power supply so it turns on. -1. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes. -1. Home Assistant will be available at [http://hassio.local:8123][local]. +1. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes. Do not expect anything but the Home Assistant logo on the HDMI display, or any use for a keyboard or mouse. +1. Home Assistant will be available at [http://hassio.local:8123][local]. Shortly after the download has started, a simple preparation status page will be available at this URL. Point your browser there. The page refreshes automatically, and Home Assistant will be shown when the download is complete. [local]: http://hassio.local:8123 From b39bd81c6e7b70184dec07c5e4e47a97a428214b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Sun, 28 Jan 2018 23:28:56 +0200 Subject: [PATCH 18/59] Spelling fixes (#4532) * Spelling fixes * "It's" -> "its" fixes * Fix capitalization of "Pi" in "Raspberry Pi" "Pi", not "PI" or "pi". --- source/_components/alarmdecoder.markdown | 2 +- .../_components/binary_sensor.arest.markdown | 2 +- .../_components/binary_sensor.gc100.markdown | 2 +- .../binary_sensor.raspihats.markdown | 4 ++-- .../binary_sensor.rpi_gpio.markdown | 4 ++-- source/_components/camera.generic.markdown | 2 +- source/_components/climate.mqtt.markdown | 2 +- source/_components/climate.oem.markdown | 2 +- source/_components/cover.mqtt.markdown | 2 +- source/_components/cover.rflink.markdown | 2 +- .../device_tracker.icloud.markdown | 2 +- .../device_tracker.owntracks.markdown | 2 +- .../_components/device_tracker.tado.markdown | 2 +- source/_components/envisalink.markdown | 2 +- source/_components/hue.markdown | 2 +- ..._processing.microsoft_face_detect.markdown | 2 +- ...rocessing.microsoft_face_identify.markdown | 2 +- source/_components/light.ihc.markdown | 2 +- source/_components/light.rflink.markdown | 4 ++-- source/_components/logbook.markdown | 2 +- source/_components/mailbox.markdown | 2 +- source/_components/media_player.cast.markdown | 2 +- .../media_player.gstreamer.markdown | 4 ++-- .../_components/media_player.yamaha.markdown | 2 +- source/_components/mycroft.markdown | 2 +- source/_components/notify.clickatell.markdown | 2 +- source/_components/notify.html5.markdown | 2 +- source/_components/notify.pushsafer.markdown | 2 +- source/_components/raspihats.markdown | 2 +- source/_components/rflink.markdown | 2 +- source/_components/rpi_gpio.markdown | 4 ++-- source/_components/satel_integra.markdown | 2 +- source/_components/sensor.arduino.markdown | 2 +- source/_components/sensor.buienradar.markdown | 2 +- source/_components/sensor.dsmr.markdown | 2 +- source/_components/sensor.miflora.markdown | 2 +- .../sensor.modem_callerid.markdown | 2 +- .../sensor.openweathermap.markdown | 2 +- .../_components/sensor.supervisord.markdown | 2 +- source/_components/sensor.vera.markdown | 2 +- source/_components/sensor.yr.markdown | 2 +- source/_components/sensor.yweather.markdown | 2 +- source/_components/switch.gc100.markdown | 2 +- source/_components/switch.raspihats.markdown | 4 ++-- source/_components/switch.rflink.markdown | 2 +- source/_components/switch.rpi_gpio.markdown | 4 ++-- source/_components/updater.markdown | 2 +- source/_components/waterfurnace.markdown | 2 +- ...n_using_timeinterval_inputboolean.markdown | 2 +- source/_cookbook/track_battery_level.markdown | 2 +- source/_docs/asterisk_mbox.markdown | 2 +- .../_docs/configuration/state_object.markdown | 2 +- source/_docs/ecosystem/appdaemon/api.markdown | 20 +++++++++---------- .../_docs/ecosystem/appdaemon/reboot.markdown | 2 +- .../ecosystem/appdaemon/tutorial.markdown | 4 ++-- .../ecosystem/backup/backup_usb.markdown | 2 +- .../certificates/lets_encrypt.markdown | 2 +- .../ecosystem/hass-configurator.markdown | 2 +- .../hassbian/integrations.markdown | 4 ++-- source/_docs/scripts.markdown | 2 +- source/_docs/z-wave/control-panel.markdown | 2 +- source/_docs/z-wave/entities.markdown | 2 +- source/_docs/z-wave/services.markdown | 2 +- ...rry-pi-squeezebox-asuswrt-support.markdown | 10 +++++----- ...ings-with-MQTT-and-Home-Assistant.markdown | 2 +- .../_posts/2016-04-07-static-website.markdown | 2 +- ...asonic-gtfs-and-config-validation.markdown | 2 +- ...luetooth-lg-webos-tvs-and-roombas.markdown | 2 +- ...hat-cant-track-themselves-part-ii.markdown | 2 +- ...anels--jupyter-notebooks--directv.markdown | 2 +- .../2016-08-16-we-have-apps-now.markdown | 4 ++-- ...10-08-hassbian-rest-digital-ocean.markdown | 2 +- .../2017-01-28-face-coffee-wink.markdown | 2 +- source/_posts/2017-02-04-babyphone.markdown | 6 +++--- ...onfig-panel-and-state-restoration.markdown | 4 ++-- source/_posts/2017-10-07-release-55.markdown | 2 +- .../_posts/2017-11-10-ttn-with-mqtt.markdown | 2 +- source/_posts/2017-11-12-tor.markdown | 2 +- .../developers/code_review_component.markdown | 2 +- .../hassio/addon_communication.markdown | 2 +- .../developers/hassio/addon_config.markdown | 2 +- .../hassio/addon_repository.markdown | 2 +- .../developers/hassio/addon_testing.markdown | 2 +- source/developers/websocket_api.markdown | 2 +- source/getting-started/index.markdown | 2 +- 85 files changed, 111 insertions(+), 111 deletions(-) diff --git a/source/_components/alarmdecoder.markdown b/source/_components/alarmdecoder.markdown index aa1109dbdf7..8cfc24d2152 100644 --- a/source/_components/alarmdecoder.markdown +++ b/source/_components/alarmdecoder.markdown @@ -20,7 +20,7 @@ Please visit the [AlarmDecoder website](https://www.alarmdecoder.com/) for furth There is currently support for the following device types within Home Assistant: - [Binary Sensor](/components/binary_sensor.alarmdecoder/): Reports on zone status -- [Sensor](/components/sensor.alarmdecoder/): Emulates an keypad display +- [Sensor](/components/sensor.alarmdecoder/): Emulates a keypad display - [Alarm Control Panel](/components/alarm_control_panel.alarmdecoder/): Reports on alarm status, and can be used to arm/disarm the system This is a fully event-based component. Any event sent by the AlarmDecoder device will be immediately reflected within Home Assistant. diff --git a/source/_components/binary_sensor.arest.markdown b/source/_components/binary_sensor.arest.markdown index a03c972e7b8..8b359f464aa 100644 --- a/source/_components/binary_sensor.arest.markdown +++ b/source/_components/binary_sensor.arest.markdown @@ -14,7 +14,7 @@ ha_release: 0.9 --- -The `arest` binary sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework. +The `arest` binary sensor platform allows you to get all data from your devices (like Arduinos with an ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework. To use your aREST binary sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/binary_sensor.gc100.markdown b/source/_components/binary_sensor.gc100.markdown index 3be8c013046..80d828723bd 100644 --- a/source/_components/binary_sensor.gc100.markdown +++ b/source/_components/binary_sensor.gc100.markdown @@ -1,7 +1,7 @@ --- layout: page title: gc100 Binary Sensor -description: "Instructions on how to set up an gc100 binary sensor within Home Assistant." +description: "Instructions on how to set up a gc100 binary sensor within Home Assistant." date: 2017-10-27 17:26 sidebar: true comments: false diff --git a/source/_components/binary_sensor.raspihats.markdown b/source/_components/binary_sensor.raspihats.markdown index 4815aa2de7b..83f355aaf55 100644 --- a/source/_components/binary_sensor.raspihats.markdown +++ b/source/_components/binary_sensor.raspihats.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Raspihats Binary Sensor" -description: "Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor." +description: "Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor." date: 2017-05-01 04:09 sidebar: true comments: false @@ -87,4 +87,4 @@ It will output a table like this: 70: -- -- -- -- -- -- -- 77 ``` -For more details about the `raspihats` add-on boards for Raspberry PI, visit [raspihats.com](http://www.raspihats.com/). +For more details about the `raspihats` add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). diff --git a/source/_components/binary_sensor.rpi_gpio.markdown b/source/_components/binary_sensor.rpi_gpio.markdown index 99a7eda5eb4..dbae9b1b8d3 100644 --- a/source/_components/binary_sensor.rpi_gpio.markdown +++ b/source/_components/binary_sensor.rpi_gpio.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "Raspberry PI GPIO Binary Sensor" -description: "Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant." +title: "Raspberry Pi GPIO Binary Sensor" +description: "Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into Home Assistant." date: 2015-08-30 19:00 sidebar: true comments: false diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown index c6f41ac3376..3f99910e1c4 100644 --- a/source/_components/camera.generic.markdown +++ b/source/_components/camera.generic.markdown @@ -60,7 +60,7 @@ camera: ### {% linkable_title Local image with Hass.io %} -You can show an static image with this platform. Just place the image here: `/config/www/your_image.png` +You can show a static image with this platform. Just place the image here: `/config/www/your_image.png` ```yaml camera: diff --git a/source/_components/climate.mqtt.markdown b/source/_components/climate.mqtt.markdown index 85675df1f62..504610dea47 100644 --- a/source/_components/climate.mqtt.markdown +++ b/source/_components/climate.mqtt.markdown @@ -201,7 +201,7 @@ climate: ``` {% endraw %} -This will parse the incoming `"auto"` as JSON, resulting in `auto`. Obvisouly, in this case you could also just set `value_template: {% raw %}"{{ value_json }}"{% endraw %}`. +This will parse the incoming `"auto"` as JSON, resulting in `auto`. Obviously, in this case you could also just set `value_template: {% raw %}"{{ value_json }}"{% endraw %}`. ### {% linkable_title Example %} diff --git a/source/_components/climate.oem.markdown b/source/_components/climate.oem.markdown index c123b0e0f7b..be9b8cda217 100644 --- a/source/_components/climate.oem.markdown +++ b/source/_components/climate.oem.markdown @@ -15,7 +15,7 @@ ha_iot_class: "Local Polling" This platform supports the ESP82666 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](http://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/). -This platform controls the setpoint of the thermostat in it's "manual" mode, therefore there is a configuration option the away setpoint. +This platform controls the setpoint of the thermostat in its "manual" mode, therefore there is a configuration option the away setpoint. To set it up, add the following information to your `configuration.yaml` file: diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown index 94cc013f787..f06204cfaa4 100755 --- a/source/_components/cover.mqtt.markdown +++ b/source/_components/cover.mqtt.markdown @@ -134,7 +134,7 @@ tilt_max: type: integer default: 100 tilt_closed_value: - description: The value that will be sent on an `close_cover_tilt` command. + description: The value that will be sent on a `close_cover_tilt` command. required: false type: integer default: 0 diff --git a/source/_components/cover.rflink.markdown b/source/_components/cover.rflink.markdown index 5bbe5e2f6ed..1bd3a1a50c7 100644 --- a/source/_components/cover.rflink.markdown +++ b/source/_components/cover.rflink.markdown @@ -85,7 +85,7 @@ Device configuration variables: - **name** (*Optional*): Name for the device, defaults to Rflink ID. - **aliases** (*Optional*): Alternative Rflink ID's this device is known by. -- **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False). +- **fire_event** (*Optional*): Fire a `button_pressed` event if this device is turned on or off (default: False). - **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1). - **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below). - **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below). diff --git a/source/_components/device_tracker.icloud.markdown b/source/_components/device_tracker.icloud.markdown index e98b8271577..74f22f02f6b 100644 --- a/source/_components/device_tracker.icloud.markdown +++ b/source/_components/device_tracker.icloud.markdown @@ -50,5 +50,5 @@ To disable the drainage of the battery, a dynamic interval is being used for eac 4 services are available for this component: - **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. - **icloud_lost_iphone**: This service will play the Lost iPhone sound on a certain iDevice. The `account_name` and `device_name` are optional. -- **icloud_set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to it's default dynamic interval based on it's current zone, it's distance towards home and it's battery level. +- **icloud_set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level. - **icloud_reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are being found by the component or if you have added a new iDevice to your account. The `account_name` is optional. diff --git a/source/_components/device_tracker.owntracks.markdown b/source/_components/device_tracker.owntracks.markdown index 0bd137c0ab7..631d8dc669d 100644 --- a/source/_components/device_tracker.owntracks.markdown +++ b/source/_components/device_tracker.owntracks.markdown @@ -96,7 +96,7 @@ iBeacons don't need to be stationary. You could put one on your key ring, or in When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location. -To use mobile iBeacons with HA, you just set up a region that doesn't match your Zone names. If HA sees an entry event for a iBeacon region that doesn't match a Zone name (say `keys`) - it will start tracking it, calling the device `device_tracker.beacon_keys`). +To use mobile iBeacons with HA, you just set up a region that doesn't match your Zone names. If HA sees an entry event for an iBeacon region that doesn't match a Zone name (say `keys`) - it will start tracking it, calling the device `device_tracker.beacon_keys`). This allows you to write zone automations for devices that can't track themselves (for example *alert me if I leave the house and my keys are still at home*). Another example would be *open the gates if my car arrives home*. diff --git a/source/_components/device_tracker.tado.markdown b/source/_components/device_tracker.tado.markdown index 446c79131d6..bc1d91b37bc 100644 --- a/source/_components/device_tracker.tado.markdown +++ b/source/_components/device_tracker.tado.markdown @@ -12,7 +12,7 @@ ha_category: Presence Detection ha_release: 0.37 --- -The `tado` device tracker is using the [Tado Smart Thermostat](https://www.tado.com/) and it's support for person presence detection based on smartphone location by geofencing. +The `tado` device tracker is using the [Tado Smart Thermostat](https://www.tado.com/) and its support for person presence detection based on smartphone location by geofencing. This tracker uses the Tado API to determine if a mobile device is at home. It tracks all devices in your home that Tado knows about. diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index 02d0746982c..57deb9f53fb 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -13,7 +13,7 @@ ha_release: 0.23 ha_iot_class: "Local Push" --- -The `envisalink` component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and it's sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4. +The `envisalink` component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4. Please visit the [eyezon website](http://www.eyezon.com/) for further information about the evl3 and evl4 boards. diff --git a/source/_components/hue.markdown b/source/_components/hue.markdown index 46d8f2cc9f3..40623c9a95a 100644 --- a/source/_components/hue.markdown +++ b/source/_components/hue.markdown @@ -103,7 +103,7 @@ More information can be found on the [Philips Hue API documentation](https://www ### {% linkable_title Using Hue Scenes in Home Assistant %} -The Hue platform has it's own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you've never used, almost all very poorly named. +The Hue platform has its own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you've never used, almost all very poorly named. To avoid user interface overload we don't expose scenes directly. Instead there is a hue.hue_activate_scene service which can be used by `automation` or `script` components. This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant. diff --git a/source/_components/image_processing.microsoft_face_detect.markdown b/source/_components/image_processing.microsoft_face_detect.markdown index c15e5baab07..39aecb15340 100644 --- a/source/_components/image_processing.microsoft_face_detect.markdown +++ b/source/_components/image_processing.microsoft_face_detect.markdown @@ -13,7 +13,7 @@ featured: false ha_release: 0.38 --- -The `microsoft_face_detect` image processing platform allows you to use the [Microsoft Face Identify](https://www.microsoft.com/cognitive-services/en-us/) API through Home Assistant. This platform enables you do detect face on camera and fire a event with attributes. +The `microsoft_face_detect` image processing platform allows you to use the [Microsoft Face Identify](https://www.microsoft.com/cognitive-services/en-us/) API through Home Assistant. This platform enables you do detect face on camera and fire an event with attributes. Please refer to the [component](/components/microsoft_face/) configuration on how to setup the API key. diff --git a/source/_components/image_processing.microsoft_face_identify.markdown b/source/_components/image_processing.microsoft_face_identify.markdown index e600ae36a61..76fb2ad1be0 100644 --- a/source/_components/image_processing.microsoft_face_identify.markdown +++ b/source/_components/image_processing.microsoft_face_identify.markdown @@ -13,7 +13,7 @@ featured: false ha_release: 0.37 --- -The `microsoft_face_identify` image processing platform lets you use [Microsoft Face identify](https://www.microsoft.com/cognitive-services/en-us/) API through Home Assistant. This platform allow you do identify persons on camera and fire a event with identify persons. +The `microsoft_face_identify` image processing platform lets you use [Microsoft Face identify](https://www.microsoft.com/cognitive-services/en-us/) API through Home Assistant. This platform allow you do identify persons on camera and fire an event with attributes. Please refer to the [component](/components/microsoft_face/) configuration on how to setup the API key. diff --git a/source/_components/light.ihc.markdown b/source/_components/light.ihc.markdown index a289ea942f3..741d2168cd9 100644 --- a/source/_components/light.ihc.markdown +++ b/source/_components/light.ihc.markdown @@ -61,5 +61,5 @@ lights: {% endconfiguration %} In the example above 12345 is ihc resource id and "tablelight" is the name. -The IHC resource id can be a light level for dimmers or an boolean output of a relay. +The IHC resource id can be a light level for dimmers or a boolean output of a relay. For more information about IHC resource ids see [Manual Setup](/components/ihc/#manual-setup) diff --git a/source/_components/light.rflink.markdown b/source/_components/light.rflink.markdown index 0bd73b588ef..ebba128f88a 100644 --- a/source/_components/light.rflink.markdown +++ b/source/_components/light.rflink.markdown @@ -50,7 +50,7 @@ Device configuration variables: - **name** (*Optional*): Name for the device, defaults to Rflink ID. - **type** (*Optional*): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See 'Light Types' below. (default: Switchable) - **aliases** (*Optional*): Alternative Rflink ID's this device is known by. -- **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False). +- **fire_event** (*Optional*): Fire a `button_pressed` event if this device is turned on or off (default: False). - **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1). - **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below). - **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below). @@ -86,7 +86,7 @@ Any on/off command from any alias ID updates the current state of the light. How Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated `on` command as they turn into a pulsating state until `on` is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation: -- *Hybrid*: This type sends a `dim` followed by an a `on` command; and `off` commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple `on` signals will cause dimmers to go into disco mode. +- *Hybrid*: This type sends a `dim` followed by an an `on` command; and `off` commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple `on` signals will cause dimmers to go into disco mode. - *Switchable*: Device type that sends only `on` and `off` commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above). - *Dimmable*: Sends only `dim` and `off` commands. This does not work on on/off type devices as they don't understand the `dim` command. For dimmers this does not cause issues with signal repetitions. - *Toggle*: Device type that sends only `on` commands to turn on or off the device. Some switches like for example Livolo light switches use the same 'on' command to switch on and switch off the lights. If the light is on and 'on' gets sent, the light will turn off and if the light is off and 'on' gets sent, the light will turn on. If the device has an unknown state, it will assume it is off by default. diff --git a/source/_components/logbook.markdown b/source/_components/logbook.markdown index 74e493fc9bf..adabef99d19 100644 --- a/source/_components/logbook.markdown +++ b/source/_components/logbook.markdown @@ -73,7 +73,7 @@ logbook: ### {% linkable_title Exclude Events %} -Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the `sensor.date`to show the current date in the UI, but you do not want an logbook entry for that sensor every day. +Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the `sensor.date`to show the current date in the UI, but you do not want a logbook entry for that sensor every day. To exclude these entities just add them to the `exclude` > `entities` list in the configuration of the logbook. To exclude all events from a whole domain add it to the `exclude` > `domain` list. For instance you use the `sun` domain only to trigger automations on the `azimuth attribute, then you possible are not interested in the logbook entries for sun rise and sun set. diff --git a/source/_components/mailbox.markdown b/source/_components/mailbox.markdown index 88ff203523f..28f4d77f436 100644 --- a/source/_components/mailbox.markdown +++ b/source/_components/mailbox.markdown @@ -10,7 +10,7 @@ ha_version: 0.51 footer: true --- -Mailboxes provide an list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend. +Mailboxes provide a list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend. Home Assistant currently supports only the [Asterisk Voicemail](/component/mailbox.asterisk_mbox) mailbox. diff --git a/source/_components/media_player.cast.markdown b/source/_components/media_player.cast.markdown index 63271c16760..c97f391dab8 100644 --- a/source/_components/media_player.cast.markdown +++ b/source/_components/media_player.cast.markdown @@ -15,7 +15,7 @@ ha_iot_class: "Local Polling" --- -Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast. +Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is an issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast. The Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`: diff --git a/source/_components/media_player.gstreamer.markdown b/source/_components/media_player.gstreamer.markdown index c77e8c40496..288ef12120c 100644 --- a/source/_components/media_player.gstreamer.markdown +++ b/source/_components/media_player.gstreamer.markdown @@ -58,7 +58,7 @@ If you're running Home Assistant in a virtual environment, you'll need to symlin ln -s /path/to/your/installation/of/gi /path/to/your/venv/lib/python3.4/site-packages ``` -On a Raspberry PI, you may need to add the Home Assistant user to the `audio` group: +On a Raspberry Pi, you may need to add the Home Assistant user to the `audio` group: ```bash sudo usermod -a -G audio @@ -68,7 +68,7 @@ sudo usermod -a -G audio ### {% linkable_title Using with TTS %} -To play TTS on your local computer (for example, if you have speakers attached to your Raspberry PI: +To play TTS on your local computer (for example, if you have speakers attached to your Raspberry Pi: ```yaml media_player: diff --git a/source/_components/media_player.yamaha.markdown b/source/_components/media_player.yamaha.markdown index bfe7c81c9c1..c306b1d5272 100644 --- a/source/_components/media_player.yamaha.markdown +++ b/source/_components/media_player.yamaha.markdown @@ -52,7 +52,7 @@ Configuration variables: have your receiver switched off. - In some cases, auto-discovery fails due to a known bug in the receiver's firmware. It is possible to manually specify the - receiver's IP address or via it's hostname (if it is discoverable by + receiver's IP address or via its hostname (if it is discoverable by your DNS) then. ### {% linkable_title Supported operations %} diff --git a/source/_components/mycroft.markdown b/source/_components/mycroft.markdown index 50241b7a2f1..705800f6e34 100644 --- a/source/_components/mycroft.markdown +++ b/source/_components/mycroft.markdown @@ -12,7 +12,7 @@ ha_category: Voice ha_release: 0.53 --- -[Mycroft](https://mycroft.ai) is a open source voice assistant that allows you to send notifications and more to Mycroft from Home Assistant. +[Mycroft](https://mycroft.ai) is an open source voice assistant that allows you to send notifications and more to Mycroft from Home Assistant. ```yaml # Example configuration.yaml entry diff --git a/source/_components/notify.clickatell.markdown b/source/_components/notify.clickatell.markdown index 0c274c9a1b7..783f3deb588 100644 --- a/source/_components/notify.clickatell.markdown +++ b/source/_components/notify.clickatell.markdown @@ -16,7 +16,7 @@ ha_release: 0.56 The `clickatell` platform uses [Clickatell](https://clickatell.com) to deliver SMS notifications from Home Assistant. ### Get your Clickatell API Credentials -Go to your [Clickatell SMS Platform Portal](https://portal.clickatell.com/#/) section and create a new SMS integration. There are three screens of information required to creater an integration. Please ensure the following: +Go to your [Clickatell SMS Platform Portal](https://portal.clickatell.com/#/) section and create a new SMS integration. There are three screens of information required to create an integration. Please ensure the following: 1. Give the new Integration an identification name. 2. Ensure it is set for 'production' use. diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 1adf5f015e1..04df895ccd1 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -250,7 +250,7 @@ You will receive an event named `html5_notification.closed` when the notificatio ### {% linkable_title Making notifications work with NGINX proxy %} -If you use [NGINX](/ecosystem/nginx/) as an proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It's because of authentication token that cannot be passed through the proxy. +If you use [NGINX](/ecosystem/nginx/) as a proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It's because of authentication token that cannot be passed through the proxy. To solve the issue put additional location into your nginx site's configuration: diff --git a/source/_components/notify.pushsafer.markdown b/source/_components/notify.pushsafer.markdown index e7664866497..61edbe9d8d7 100644 --- a/source/_components/notify.pushsafer.markdown +++ b/source/_components/notify.pushsafer.markdown @@ -15,7 +15,7 @@ ha_release: 0.39 The [Pushsafer service](https://www.pushsafer.com/) is a platform for the notify component. This allows you to send messages to the user using Pushsafer. -In order to get an private or alias key you need to go to the [Pushsafer website](https://www.pushsafer.com) and register. +In order to get a private or alias key you need to go to the [Pushsafer website](https://www.pushsafer.com) and register. To use Pushsafer notifications, add the following to your `configuration.yaml` file: diff --git a/source/_components/raspihats.markdown b/source/_components/raspihats.markdown index 3c1d33ed1e7..b20878e6482 100644 --- a/source/_components/raspihats.markdown +++ b/source/_components/raspihats.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Raspihats" -description: "Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant." +description: "Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant." date: 2017-05-01 04:06 sidebar: true comments: false diff --git a/source/_components/rflink.markdown b/source/_components/rflink.markdown index 26515b5f8c3..33e21132150 100644 --- a/source/_components/rflink.markdown +++ b/source/_components/rflink.markdown @@ -135,7 +135,7 @@ If you find a device is recognized differently, with different protocols or the ### {% linkable_title Technical Overview %} -- The`rflink` Python module is a asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway. +- The`rflink` Python module is an asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway. - This component uses this callback to distribute 'rflink packet events' over [Home Assistant's event bus](https://home-assistant.io/docs/configuration/events/) which can be subscribed to by entities/platform implementations. - The platform implementation takes care of creating new devices (if enabled) for unseen incoming packet ID's. - Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entity logic is maintained in this main component. diff --git a/source/_components/rpi_gpio.markdown b/source/_components/rpi_gpio.markdown index b0f2fdc3703..642804ffff0 100644 --- a/source/_components/rpi_gpio.markdown +++ b/source/_components/rpi_gpio.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "Raspberry PI GPIO" -description: "Instructions how to integrate the GPIO capability of a Raspberry PI into Home Assistant." +title: "Raspberry Pi GPIO" +description: "Instructions how to integrate the GPIO capability of a Raspberry Pi into Home Assistant." date: 2016-08-30 19:00 sidebar: true comments: false diff --git a/source/_components/satel_integra.markdown b/source/_components/satel_integra.markdown index 4cbe5957bfd..8e71d59e7f0 100644 --- a/source/_components/satel_integra.markdown +++ b/source/_components/satel_integra.markdown @@ -56,7 +56,7 @@ Configuration variables: - **port** (*Optional*): The port on which the ETHM module listens for clients using integration protocol. Default: `7094` - **partition** (*Optional*): The partition to operate on. Integra can support multiple partitions, this platform only supports one. Default: `1` - **arm_home_mode** (*Optional*): The mode in which arm Satel Integra when 'arm home' is used. Possible options are `1`,`2` or `3`, default being `1`. For more information on what are the differences between them, please refer to Satel Integra manual. -- **zones** (*Optional*): This module does not discover currently which zones are actually in use, so it will only monitor the ones defined in the config. For each zone, a proper ID must be given as well as it's name (does not need to match the one specified in Satel Integra alarm). For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.* +- **zones** (*Optional*): This module does not discover currently which zones are actually in use, so it will only monitor the ones defined in the config. For each zone, a proper ID must be given as well as its name (does not need to match the one specified in Satel Integra alarm). For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.* List of all zone IDs can be taken from DloadX program. diff --git a/source/_components/sensor.arduino.markdown b/source/_components/sensor.arduino.markdown index 02fa7f6aaac..b7e4c1c6d7a 100644 --- a/source/_components/sensor.arduino.markdown +++ b/source/_components/sensor.arduino.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Local Polling" --- -The `arduino` sensor platform allows you to get an numerical values from an analog input pin of an [Arduino](https://www.arduino.cc/) board. Usually the value is between 0 and 1024. +The `arduino` sensor platform allows you to get numerical values from an analog input pin of an [Arduino](https://www.arduino.cc/) board. Usually the value is between 0 and 1024. To enable an Arduino sensor with Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/sensor.buienradar.markdown b/source/_components/sensor.buienradar.markdown index 1cdebf9290a..cb1cd65660d 100644 --- a/source/_components/sensor.buienradar.markdown +++ b/source/_components/sensor.buienradar.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling" --- -The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a web service that provides detailed weather information for users in The Netherlands. The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weather stations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0). +The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as a source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a web service that provides detailed weather information for users in The Netherlands. The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weather stations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0). The selected weather station will provide all weather data, with the exception of the forecasted precipitation. The forecasted precipitation data will be retrieved from buienradar using your actual gps-location (and not the location of the nearest weather station). diff --git a/source/_components/sensor.dsmr.markdown b/source/_components/sensor.dsmr.markdown index a83d5a8ac0e..b073aae82ff 100644 --- a/source/_components/sensor.dsmr.markdown +++ b/source/_components/sensor.dsmr.markdown @@ -131,7 +131,7 @@ DSMR is a standard to which Dutch smartmeters must comply. It specifies that the The contents of this telegram differ between version but they generally consist of lines with 'obis' (Object Identification System, a numerical ID for a value) followed with the value and unit. -This module sets up a asynchronous reading loop using the `dsmr_parser` module which waits for a complete telegram, parser it and puts it on an async queue as a dictionary of `obis`/object mapping. The numeric value and unit of each value can be read from the objects attributes. Because the `obis` are know for each DSMR version the Entities for this component are create during bootstrap. +This module sets up an asynchronous reading loop using the `dsmr_parser` module which waits for a complete telegram, parser it and puts it on an async queue as a dictionary of `obis`/object mapping. The numeric value and unit of each value can be read from the objects attributes. Because the `obis` are know for each DSMR version the Entities for this component are create during bootstrap. Another loop (DSMR class) is setup which reads the telegram queue, stores/caches the latest telegram and notifies the Entities that the telegram has been updated. diff --git a/source/_components/sensor.miflora.markdown b/source/_components/sensor.miflora.markdown index 4d15463a1c7..8fcfca3d09d 100644 --- a/source/_components/sensor.miflora.markdown +++ b/source/_components/sensor.miflora.markdown @@ -20,7 +20,7 @@ Depending on the operating system you're running, you have to configure the prop - On [Hass.io](https://home-assistant.io/hassio/installation/): Miflora will work out of the box. - On other Linux systems: - - Prefered solution: Install the `bluepy` library (via pip). When using a virtual environment, make sure to use install the library in the right one. + - Preferred solution: Install the `bluepy` library (via pip). When using a virtual environment, make sure to use install the library in the right one.    - Fallback solution: Install `gatttool` via your package manager. Depending on the distribution, the package name might be: `bluez`, `bluetooth`, `bluez-deprecated` - Windows and MacOS are currently not supported by the [miflora library](https://github.com/open-homeautomation/miflora/). diff --git a/source/_components/sensor.modem_callerid.markdown b/source/_components/sensor.modem_callerid.markdown index 30f1c98f9e6..d2d0340bb39 100644 --- a/source/_components/sensor.modem_callerid.markdown +++ b/source/_components/sensor.modem_callerid.markdown @@ -37,7 +37,7 @@ If Home Assistant (`hass`) runs with another user (e.g. `homeassistant` on Hassb Depending on what's plugged into your USB ports, the name found above may change. You can lock in a name, such as `/dev/modem`, by following [these instructions](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/). -When the sensor detects a new call, it's state changes to 'ring' for each ring and 'callerid' when caller id information is received. It returns to 'idle' once ringing stops. The state event includes an attribute payload that includes the time of the call, name and number. +When the sensor detects a new call, its state changes to 'ring' for each ring and 'callerid' when caller id information is received. It returns to 'idle' once ringing stops. The state event includes an attribute payload that includes the time of the call, name and number. Some example automations: ```yaml diff --git a/source/_components/sensor.openweathermap.markdown b/source/_components/sensor.openweathermap.markdown index f672ff07291..6f9186a6f6e 100644 --- a/source/_components/sensor.openweathermap.markdown +++ b/source/_components/sensor.openweathermap.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling" --- -The `openweathermap` platform uses [OpenWeatherMap](http://openweathermap.org/) as an source for current meteorological data for your location. The `forecast` will show you the condition in 3 h. +The `openweathermap` platform uses [OpenWeatherMap](http://openweathermap.org/) as a source for current meteorological data for your location. The `forecast` will show you the condition in 3 h. You need an API key which is free but requires a [registration](http://home.openweathermap.org/users/sign_up). diff --git a/source/_components/sensor.supervisord.markdown b/source/_components/sensor.supervisord.markdown index 4fcb8f24157..93a191fc9cb 100644 --- a/source/_components/sensor.supervisord.markdown +++ b/source/_components/sensor.supervisord.markdown @@ -22,7 +22,7 @@ It required that you enable the HTTP feature in the `/etc/supervisord.conf` conf port=127.0.0.1:9001 ``` -After a restart of `supervisord` you should be able to access the web interface. If needed then this could be added as a [iFrame panel](/components/panel_iframe/). +After a restart of `supervisord` you should be able to access the web interface. If needed then this could be added as an [iFrame panel](/components/panel_iframe/).

diff --git a/source/_components/sensor.vera.markdown b/source/_components/sensor.vera.markdown index bd32fdd408e..c1e7b16a374 100644 --- a/source/_components/sensor.vera.markdown +++ b/source/_components/sensor.vera.markdown @@ -17,7 +17,7 @@ The `vera` platform allows you to get data from your [Vera](http://getvera.com/) They will be automatically discovered if the vera component is loaded. -Please note that some vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that vera will send alerts (email messages to txts) when they are _armed_ an change state. +Please note that some vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that vera will send alerts (email messages to txts) when they are _armed_ and change state. Home Assistant will display the state of these sensors regardless of the _armed_ state. diff --git a/source/_components/sensor.yr.markdown b/source/_components/sensor.yr.markdown index 362c3aaedbf..35813cb4598 100644 --- a/source/_components/sensor.yr.markdown +++ b/source/_components/sensor.yr.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling" --- -The `yr` platform uses [YR.no](http://www.yr.no/) as an source for current meteorological data for your location. The +The `yr` platform uses [YR.no](http://www.yr.no/) as a source for current meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK. To add YR to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.yweather.markdown b/source/_components/sensor.yweather.markdown index 7ac041c1cb1..0f9bcd7a859 100644 --- a/source/_components/sensor.yweather.markdown +++ b/source/_components/sensor.yweather.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling" --- -The `yweather` platform uses [Yahoo Weather](https://www.yahoo.com/news/weather/) as an source for current meteorological data. The `forecast` will show you the condition for 5 days, 0 is the current day. You can use only `weather`, `temp_min`, and `temp_max` with forecast. It's important to note that a yweather sensor will only show ONE days forecast at a time so to show multiple days forecasts, you will need to use the 'name:' option and give each sensor a unique name. +The `yweather` platform uses [Yahoo Weather](https://www.yahoo.com/news/weather/) as a source for current meteorological data. The `forecast` will show you the condition for 5 days, 0 is the current day. You can use only `weather`, `temp_min`, and `temp_max` with forecast. It's important to note that a yweather sensor will only show ONE days forecast at a time so to show multiple days forecasts, you will need to use the 'name:' option and give each sensor a unique name.

Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2000 signed calls per day. diff --git a/source/_components/switch.gc100.markdown b/source/_components/switch.gc100.markdown index 9fcf7217b66..59649d72d15 100644 --- a/source/_components/switch.gc100.markdown +++ b/source/_components/switch.gc100.markdown @@ -1,7 +1,7 @@ --- layout: page title: gc100 Switch -description: "Instructions on how to set up an gc100 switch within Home Assistant." +description: "Instructions on how to set up a gc100 switch within Home Assistant." date: 2017-10-27 17:26 sidebar: true comments: false diff --git a/source/_components/switch.raspihats.markdown b/source/_components/switch.raspihats.markdown index b2fa067e130..23f7afb96f6 100644 --- a/source/_components/switch.raspihats.markdown +++ b/source/_components/switch.raspihats.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Raspihats Switch" -description: "Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a switch." +description: "Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a switch." date: 2017-05-15 04:20 sidebar: true comments: false @@ -89,4 +89,4 @@ It will output a table like this: 70: -- -- -- -- -- -- -- 77 ``` -For more details about the Raspihats add-on boards for Raspberry PI, visit [raspihats.com](http://www.raspihats.com/). +For more details about the Raspihats add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). diff --git a/source/_components/switch.rflink.markdown b/source/_components/switch.rflink.markdown index fc7ab2b7a9f..08b5e614585 100644 --- a/source/_components/switch.rflink.markdown +++ b/source/_components/switch.rflink.markdown @@ -50,7 +50,7 @@ Device configuration variables: - **name** (*Optional*): Name for the device, defaults to RFLink ID. - **aliases** (*Optional*): Alternative RFLink ID's this device is known by. -- **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False). +- **fire_event** (*Optional*): Fire a `button_pressed` event if this device is turned on or off (default: False). - **signal_repetitions** (*Optional*): Repeat every RFLink command this number of times (default: 1) - **group** (*Optional*): Allow switch to respond to group commands (ALLON/ALLOFF). (default: yes) - **group_aliases** (*Optional*): `aliases` which only respond to group commands. diff --git a/source/_components/switch.rpi_gpio.markdown b/source/_components/switch.rpi_gpio.markdown index 2e1d74786d1..192bb82544e 100644 --- a/source/_components/switch.rpi_gpio.markdown +++ b/source/_components/switch.rpi_gpio.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "Raspberry PI GPIO Switch" -description: "Instructions how to integrate the GPIO of a Raspberry PI into Home Assistant as a switch." +title: "Raspberry Pi GPIO Switch" +description: "Instructions how to integrate the GPIO of a Raspberry Pi into Home Assistant as a switch." date: 2015-08-07 14:00 sidebar: true comments: false diff --git a/source/_components/updater.markdown b/source/_components/updater.markdown index 4a5b9777b35..b87d554bb91 100644 --- a/source/_components/updater.markdown +++ b/source/_components/updater.markdown @@ -11,7 +11,7 @@ logo: home-assistant.png ha_category: Other --- -The `updater` component will check daily for new releases. It will show a badge in the frontend if a new version is found. As [Hass.io](/hassio/) has it's own schedule for release it doesn't make sense to use this component on Hass.io. +The `updater` component will check daily for new releases. It will show a badge in the frontend if a new version is found. As [Hass.io](/hassio/) has its own schedule for release it doesn't make sense to use this component on Hass.io. The updater component will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the time zone, Python version and operating system information. No identifiable information (i.e., IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python [source code](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/updater.py#L91). For further information about the Updater's data, please check the [detailed overview](/docs/backend/updater/). diff --git a/source/_components/waterfurnace.markdown b/source/_components/waterfurnace.markdown index b747ff597a2..9bf884e0c29 100644 --- a/source/_components/waterfurnace.markdown +++ b/source/_components/waterfurnace.markdown @@ -64,5 +64,5 @@ every polling cycle. While this is communicating with a thermostat, geothermal systems operate most efficiently when setbacks are not used, and the home is kept at a constant temperature. It remains useful to collect the data -from the system to understand it's performance, but a full climate +from the system to understand its performance, but a full climate interface won't be implemented. diff --git a/source/_cookbook/automation_using_timeinterval_inputboolean.markdown b/source/_cookbook/automation_using_timeinterval_inputboolean.markdown index 499bc7aa5bb..d5edc5e9613 100644 --- a/source/_cookbook/automation_using_timeinterval_inputboolean.markdown +++ b/source/_cookbook/automation_using_timeinterval_inputboolean.markdown @@ -10,7 +10,7 @@ footer: true ha_category: Automation Examples --- -#### {% linkable_title Change Hue light on interval to random color based on state of a input boolean %} +#### {% linkable_title Change Hue light on interval to random color based on state of an input boolean %} _Note, Philips Hue is currently the only light platform that support the random effect._ diff --git a/source/_cookbook/track_battery_level.markdown b/source/_cookbook/track_battery_level.markdown index 9de6b14cfb0..b623f46b04e 100644 --- a/source/_cookbook/track_battery_level.markdown +++ b/source/_cookbook/track_battery_level.markdown @@ -43,7 +43,7 @@ sensor: ``` {% endraw %} -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. +The `else` part is used to have the sensor keep its 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. ### {% linkable_title Android and iOS Devices %} diff --git a/source/_docs/asterisk_mbox.markdown b/source/_docs/asterisk_mbox.markdown index 65c570aab89..fae79de9276 100644 --- a/source/_docs/asterisk_mbox.markdown +++ b/source/_docs/asterisk_mbox.markdown @@ -44,7 +44,7 @@ Before beginning make sure that you have the following: 3. Create a configuration file for the server - As the `asterisk` user create a `asterisk_mbox.ini` file (You can place this in any directory you choose, but the rommended location is `/etc/asterisk/asterisk_mbox.ini`) + As the `asterisk` user create an `asterisk_mbox.ini` file (You can place this in any directory you choose, but the rommended location is `/etc/asterisk/asterisk_mbox.ini`) ```ini [default] diff --git a/source/_docs/configuration/state_object.markdown b/source/_docs/configuration/state_object.markdown index 72e62321477..c9ee1f94036 100644 --- a/source/_docs/configuration/state_object.markdown +++ b/source/_docs/configuration/state_object.markdown @@ -27,7 +27,7 @@ Field | Description `state.last_changed` | Time the state changed. This is not updated when there are only updated attributes. Example: `2017-10-28 08:13:36.715874+00:00`. `state.attributes` | A dictionary with extra attributes related to the current state. -The attributes of an entity are optional. There are a few attributes that are used by Home Assistant for representing the entity in a specific way. Each component will also have it's own attributes to represent extra state data about the entity. For example, the light component has attributes for the current brightness and color of the light. When an attribute is not available, Home Assistant will not write it to the state. +The attributes of an entity are optional. There are a few attributes that are used by Home Assistant for representing the entity in a specific way. Each component will also have its own attributes to represent extra state data about the entity. For example, the light component has attributes for the current brightness and color of the light. When an attribute is not available, Home Assistant will not write it to the state. When using templates, attributes will be available by their name. For example `state.attributes.assumed_state`. diff --git a/source/_docs/ecosystem/appdaemon/api.markdown b/source/_docs/ecosystem/appdaemon/api.markdown index 384dab6d3a9..48c8d994ba3 100755 --- a/source/_docs/ecosystem/appdaemon/api.markdown +++ b/source/_docs/ecosystem/appdaemon/api.markdown @@ -22,13 +22,13 @@ import homeassistant.appapi as appapi class MotionLights(appapi.AppDaemon): ``` -When configured as an app in the config file (more on that later) the lifecycle of the App begins. It will be instantiated as an object by AppDaemon, and immediately, it will have a call made to it's `initialize()` function - this function must appear as part of every app: +When configured as an app in the config file (more on that later) the lifecycle of the App begins. It will be instantiated as an object by AppDaemon, and immediately, it will have a call made to its `initialize()` function - this function must appear as part of every app: ```python def initialize(self): ``` -The initialize function allows the app to register any callbacks it might need for responding to state changes, and also any setup activities. When the `initialize()` function returns, the App will be dormant until any of it's callbacks are activated. +The initialize function allows the app to register any callbacks it might need for responding to state changes, and also any setup activities. When the `initialize()` function returns, the App will be dormant until any of its callbacks are activated. There are several circumstances under which `initialize()` might be called: @@ -93,7 +93,7 @@ class = NewApp When AppDaemon sees the following configuration it will expect to find a class called `NewApp` defined in a module called `new.py` in the apps subdirectory. Apps can be placed at the root of the Apps directory or within a subdirectory, an arbitrary depth down - wherever the App is, as long as it is in some subdirectory of the Apps dir, or in the Apps dir itself, AppDaemon will find it. There is no need to include information about the path, just the name of the file itself (without the `.py`) is sufficient. If names in the subdirectories overlap, AppDir will pick one of them but the exact choice it will make is undefined. -When starting the system for the first time or when reloading an App or Module, the system will log the fact in it's main log. It is often the case that there is a problem with the class, maybe a syntax error or some other problem. If that is the case, details will be output to the error log allowing the user to remedy the problem and reload. +When starting the system for the first time or when reloading an App or Module, the system will log the fact in its main log. It is often the case that there is a problem with the class, maybe a syntax error or some other problem. If that is the case, details will be output to the error log allowing the user to remedy the problem and reload. ## {% linkable_title Steps to writing an App %} @@ -154,7 +154,7 @@ Callback constraints are a feature of AppDaemon that removes the need for repeti Put simply, callback constraints are one or more conditions on callback execution that can be applied to an individual App. An App's callbacks will only be executed if all of the constraints are met. If a constraint is absent it will not be checked for. -For example, the presence callback constraint can be added to an App by adding a parameter to it's configuration like this: +For example, the presence callback constraint can be added to an App by adding a parameter to its configuration like this: ```ini [some_app] @@ -565,7 +565,7 @@ self.cancel_listen_state(self.office_light_handle) ### {% linkable_title info_listen_state() %} -Get information on state a callback from it's handle. +Get information on state a callback from its handle. #### {% linkable_title Synopsis %} @@ -909,7 +909,7 @@ self.cancel_timer(handle) ### {% linkable_title info_timer() %} -Get information on a scheduler event from it's handle. +Get information on a scheduler event from its handle. #### {% linkable_title Synopsis %} @@ -944,7 +944,7 @@ All of the scheduler calls above support 2 additional optional arguments, `rando - `random_start` - start of range of the random time - `random_end` - end of range of the random time -`random_start` must always be numerically lower than `random_end`, they can be negative to denote a random offset before and event, or positive to denote a random offset after an event. The event would be a an absolute or relative time or sunrise/sunset depending on which scheduler call you use and these values affect the base time by the spcified amount. If not specified, they will default to `0`. +`random_start` must always be numerically lower than `random_end`, they can be negative to denote a random offset before and event, or positive to denote a random offset after an event. The event would be an absolute or relative time or sunrise/sunset depending on which scheduler call you use and these values affect the base time by the spcified amount. If not specified, they will default to `0`. For example: @@ -1463,7 +1463,7 @@ self.cancel_listen_event(handle) ### {% linkable_title info_listen_event() %} -Get information on an event callback from it's handle. +Get information on an event callback from its handle. #### {% linkable_title Synopsis %} @@ -1552,7 +1552,7 @@ The custom event `MODE_CHANGE` would be subscribed to with: self.listen_event(self.mode_event, "MODE_CHANGE") ``` -Home Assistant can send these events in a variety of other places - within automations, and also directly from Alexa intents. Home Assistant can also listen for custom events with it's automation component. This can be used to signal from AppDaemon code back to Home Assistant. Here is a sample automation: +Home Assistant can send these events in a variety of other places - within automations, and also directly from Alexa intents. Home Assistant can also listen for custom events with its automation component. This can be used to signal from AppDaemon code back to Home Assistant. Here is a sample automation: ```yaml automation: @@ -2058,7 +2058,7 @@ OK, time travel sadly isn't really possible but it can be very useful when testi ### {% linkable_title Choosing a Start Time %} -Internally, AppDaemon keeps track of it's own time relative to when it was started. This make is possible to start AppDaemon with a different start time and date to the current time. For instance to test that sunset App, start AppDaemon at a time just before sunset and see if it works as expected. To do this, simply use the "-s" argument on AppDaemon's command line. e,g,: +Internally, AppDaemon keeps track of its own time relative to when it was started. This make is possible to start AppDaemon with a different start time and date to the current time. For instance to test that sunset App, start AppDaemon at a time just before sunset and see if it works as expected. To do this, simply use the "-s" argument on AppDaemon's command line. e,g,: ```bash $ appdaemon -s "2016-06-06 19:16:00" diff --git a/source/_docs/ecosystem/appdaemon/reboot.markdown b/source/_docs/ecosystem/appdaemon/reboot.markdown index 1ccdd8773a9..2eba9f75a6c 100644 --- a/source/_docs/ecosystem/appdaemon/reboot.markdown +++ b/source/_docs/ecosystem/appdaemon/reboot.markdown @@ -10,4 +10,4 @@ footer: true redirect_from: /ecosystem/appdaemon/reboot/ --- -To run `AppDaemon` at reboot, I have provided a sample init script in the `./scripts` directory. These have been tested on a Raspberry PI - your mileage may vary on other systems. There is also a sample Systemd script. +To run `AppDaemon` at reboot, I have provided a sample init script in the `./scripts` directory. These have been tested on a Raspberry Pi - your mileage may vary on other systems. There is also a sample Systemd script. diff --git a/source/_docs/ecosystem/appdaemon/tutorial.markdown b/source/_docs/ecosystem/appdaemon/tutorial.markdown index 6eee88e98b0..6a9998bced3 100755 --- a/source/_docs/ecosystem/appdaemon/tutorial.markdown +++ b/source/_docs/ecosystem/appdaemon/tutorial.markdown @@ -23,14 +23,14 @@ So given the importance of Automation, what should Automation allow us to do? I - Is it open and expandable? - Does it run locally without any reliance on the cloud? -In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and it's Restful API. +In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and its Restful API. So why `AppDaemon`? AppDaemon is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table: - New paradigm - some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can't - Ease of use - AppDaemon's API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible, experienced Python programmers should feel right at home. - Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file -- Dynamic - AppDaemon has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to it's loose coupling. However, it is better than that - the user can make changes to code and AppDaemon will automatically reload the code, figure out which Apps were using it and restart them to use the new code with out the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result. +- Dynamic - AppDaemon has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to its loose coupling. However, it is better than that - the user can make changes to code and AppDaemon will automatically reload the code, figure out which Apps were using it and restart them to use the new code with out the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result. - Complex logic - Python's If/Else constructs are clearer and easier to code for arbitrarily complex nested logic - Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened - All the power of Python - use any of Python's libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits! diff --git a/source/_docs/ecosystem/backup/backup_usb.markdown b/source/_docs/ecosystem/backup/backup_usb.markdown index 279c76c3bda..6bd62768830 100644 --- a/source/_docs/ecosystem/backup/backup_usb.markdown +++ b/source/_docs/ecosystem/backup/backup_usb.markdown @@ -103,7 +103,7 @@ Change below path to where you placed the `usb_backup.sh` and run the following This does not automatically mount your USB drive at boot. You need to do that manually or add a line to your `/etc/fstab` file. -If your drive is on `/dev/sda1`, you could add a entry to your `/etc/fstab` like so: +If your drive is on `/dev/sda1`, you could add an entry to your `/etc/fstab` like so: ```text /dev/sda1 /media ext4 defaults,noatime 0 1 diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown index b2ca1f4bea6..ee9cb80892f 100644 --- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown +++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown @@ -241,7 +241,7 @@ In cases where your ISP blocks port 80 you will need to change the port forward Now SSH in to the device your Home Assistant is running on.

-If you're running the 'standard' setup on a Raspberry Pi the chances are you just logged in as the 'pi' user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the `sudoers` list. If you are not using the 'standard' pi setup it is presumed you will know how to get your Home Assistant user on the `sudoers` list before continuing. If you are running the 'standard' pi setup, from your 'pi' user issue the following command (where `hass` is the Home Assistant user): +If you're running the 'standard' setup on a Raspberry Pi the chances are you just logged in as the 'pi' user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the `sudoers` list. If you are not using the 'standard' Pi setup it is presumed you will know how to get your Home Assistant user on the `sudoers` list before continuing. If you are running the 'standard' Pi setup, from your 'pi' user issue the following command (where `hass` is the Home Assistant user): ``` $ sudo adduser hass sudo diff --git a/source/_docs/ecosystem/hass-configurator.markdown b/source/_docs/ecosystem/hass-configurator.markdown index d88d4a2d7fe..c9fac261ec8 100644 --- a/source/_docs/ecosystem/hass-configurator.markdown +++ b/source/_docs/ecosystem/hass-configurator.markdown @@ -109,7 +109,7 @@ Since the configurator script on its own is no service, you will have to take so 1. Fork the process into the background with the command: `nohup sudo ./configurator.py &` -2. If your system is using systemd (that's usually what you'll find on a Raspberry PI), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](https://home-assistant.io/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. +2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](https://home-assistant.io/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. 3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.supervisor) would be an example configuration you could use to control the configurator. 4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](https://home-assistant.io/docs/hassbian/). 5. A tool called [screen](http://ss64.com/bash/screen.html) (alternative to tmux). If it's not already installed on your system, you can do `sudo apt-get install screen` or `sudo yum install screen` to get it. When it's installed, start a screen session by executing `screen`. Then navigate to your Home Assistant directory and start the configurator like described above. Put the screen session into the background by pressing `CTRL+A` and then `CTRL+D`. It is now safe to disconnect from your SSH session. diff --git a/source/_docs/installation/hassbian/integrations.markdown b/source/_docs/installation/hassbian/integrations.markdown index e48f9e35367..5658ce712eb 100644 --- a/source/_docs/installation/hassbian/integrations.markdown +++ b/source/_docs/installation/hassbian/integrations.markdown @@ -28,8 +28,8 @@ Just follow the component pages for each on how to add them to your Home Assista - [DHT Sensor](/components/sensor.dht/). - [Raspberry Pi Cover](/components/cover.rpi_gpio/). - - [Raspberry PI GPIO Binary Sensor](/components/binary_sensor.rpi_gpio/). - - [Raspberry PI GPIO Switch](/components/switch.rpi_gpio/). + - [Raspberry Pi GPIO Binary Sensor](/components/binary_sensor.rpi_gpio/). + - [Raspberry Pi GPIO Switch](/components/switch.rpi_gpio/). - [Raspberry Pi RF Switch](/components/switch.rpi_rf/). ### {% linkable_title Raspberry Pi Camera %} diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index c0c23fe63ca..f630d283d4d 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -155,7 +155,7 @@ The following automation shows how to raise a custom event called `event_light_t ``` {% endraw %} -The following automation shows how to capture the custom event `event_light_turned_on`, and retrieve corresponsing `entity_id` that was passed as the event data. +The following automation shows how to capture the custom event `event_light_turned_on`, and retrieve corresponding `entity_id` that was passed as the event data. {% raw %} ```yaml diff --git a/source/_docs/z-wave/control-panel.markdown b/source/_docs/z-wave/control-panel.markdown index f204afed4f6..06c9bd741b4 100644 --- a/source/_docs/z-wave/control-panel.markdown +++ b/source/_docs/z-wave/control-panel.markdown @@ -52,7 +52,7 @@ Battery powered devices need to be awake before you can use the Z-Wave control p This is a dropdown where you can select all the entities of this node. Once selected you can then use: * **Refresh Entity** to refresh just that entity's values -* **Entity Attributes** to display the attributes of that entity (eg it's friendly name, the ID of the node, etc) +* **Entity Attributes** to display the attributes of that entity (eg its friendly name, the ID of the node, etc) Here you can mark a device as requiring polling so the controller is aware of changes because the device doesn't send updates itself. Do see the information on [polling here](/docs/z-wave/devices/#polling), since excessive polling can break your Z-Wave network. diff --git a/source/_docs/z-wave/entities.markdown b/source/_docs/z-wave/entities.markdown index b5a597b4ebf..d3c856d8352 100644 --- a/source/_docs/z-wave/entities.markdown +++ b/source/_docs/z-wave/entities.markdown @@ -147,7 +147,7 @@ binary_sensor: - **254**: Deep sleep - **255**: Case open -If your device has an `burglar` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](/components/binary_sensor.template/) to create one: +If your device has a `burglar` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](/components/binary_sensor.template/) to create one: ``` binary_sensor: diff --git a/source/_docs/z-wave/services.markdown b/source/_docs/z-wave/services.markdown index 61c2ff7a860..0a6499d2d4e 100644 --- a/source/_docs/z-wave/services.markdown +++ b/source/_docs/z-wave/services.markdown @@ -15,7 +15,7 @@ The `zwave` component exposes multiple services to help maintain the network. Al | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | add_node | Put the Z-Wave controller in inclusion mode. Allows you to add a new device to the Z-Wave network. | | add_node_secure | Put the Z-Wave controller in secure inclusion mode. Allows you to add a new device with secure communications to the Z-Wave network. | -| cancel_command | Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decide you are not going to do it, then this must be used to stop the inclusion/exclusion command. | +| cancel_command | Cancels a running Z-Wave command. If you have started an add_node or remove_node command, and decide you are not going to do it, then this must be used to stop the inclusion/exclusion command. | | change_association | Add or remove an association in the Z-Wave network | | heal_network | Tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. | | heal_node | Tells the controller to "heal" a specific node on the network. Requires `node_id` field. You can also force return route update with `return_routes` field. diff --git a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown index 7c810aee00d..14d83f62020 100644 --- a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown +++ b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown @@ -1,7 +1,7 @@ --- layout: post -title: "MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported" -description: "New support for MQTT, Rasperry PI GPIO, Logitech Squeezebox and ASUSWRT routers" +title: "MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported" +description: "New support for MQTT, Rasperry Pi GPIO, Logitech Squeezebox and ASUSWRT routers" date: 2015-08-09 18:01 0000 date_formatted: "August 9, 2015" author: Paulus Schoutsen @@ -10,7 +10,7 @@ comments: true categories: Release-Notes --- -It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/home-assistant/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documentating all the various components. +It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/home-assistant/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documenting all the various components. __MQTT Support__ The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component]. @@ -33,8 +33,8 @@ mqtt: -__Raspberry PI GPIO Support__ - [@gbarba](https://github.com/gbarba) has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant. +__Raspberry Pi GPIO Support__ + [@gbarba](https://github.com/gbarba) has contributed support to use the general purpose input and output pins on a Raspberry Pi as switches inside Home Assistant. ```yaml # Example configuration.yaml entry diff --git a/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown b/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown index 33ada39515d..2420da03999 100644 --- a/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown +++ b/source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown @@ -198,7 +198,7 @@ Here is the final sequence of events: There are a lot of stops along the way for these events, but each piece is a simple translation layer to shuttle the events between systems. ### Future Improvements -- **Raspberry pi**: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point. +- **Raspberry Pi**: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point. - **Authentication for MQTT**: At the moment, the MQTT bridge doesn't understand how to authenticate to MQTT, so only unauthenticated MQTT is supported. This is mitigated to some degree if you use our Docker Compose config, because MQTT's port is not actually shared publicly. - **Authentication for MQTT Bridge**: Right now the bridge expects that anyone subscribing is the SmartThings hub. This could use proper authentication. diff --git a/source/_posts/2016-04-07-static-website.markdown b/source/_posts/2016-04-07-static-website.markdown index a4ec4f90b1f..e7bb788ce9b 100644 --- a/source/_posts/2016-04-07-static-website.markdown +++ b/source/_posts/2016-04-07-static-website.markdown @@ -25,7 +25,7 @@ In the past the buzz word "Smart mirror" was used a couple of times in our [chat There are plenty of ways to achieve this...[RESTful API](/developers/rest_api/), [Python API](/developers/python_api/), or one of the [history components](/components/#history). If it is to be a web page I'm using the [MQTT Eventstream component](/components/mqtt_eventstream/) and [mqttws31.js](http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src). -The [HBMQTT](https://pypi.python.org/pypi/hbmqtt) broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It's a matter of minutes. OK, it took a little longer because I'm not a Javascript guy to create the software part that will show details about your environment. The source is available at [https://github.com/fabaff/home-assistant-display](https://github.com/fabaff/home-assistant-display) and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it's a only prototype and showcase to include an image in this blog post. +The [HBMQTT](https://pypi.python.org/pypi/hbmqtt) broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It's a matter of minutes. OK, it took a little longer because I'm not a Javascript guy to create the software part that will show details about your environment. The source is available at [https://github.com/fabaff/home-assistant-display](https://github.com/fabaff/home-assistant-display) and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it's only a prototype and showcase to include an image in this blog post. I hope that this little article could give you an idea of extending Home Assistant in an unconventional way. diff --git a/source/_posts/2016-04-09-onkyo-panasonic-gtfs-and-config-validation.markdown b/source/_posts/2016-04-09-onkyo-panasonic-gtfs-and-config-validation.markdown index 33c8d3e97c5..d2067b9be87 100644 --- a/source/_posts/2016-04-09-onkyo-panasonic-gtfs-and-config-validation.markdown +++ b/source/_posts/2016-04-09-onkyo-panasonic-gtfs-and-config-validation.markdown @@ -10,7 +10,7 @@ comments: true categories: Release-Notes --- -Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we've been hard at work to introduce config validation! Especially huge thanks to [@jaharkes] for his hard work on this. Config validation is still in it's early stages. More common platforms and components have been added but we didn't do everything yet. +Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we've been hard at work to introduce config validation! Especially huge thanks to [@jaharkes] for his hard work on this. Config validation is still in its early stages. More common platforms and components have been added but we didn't do everything yet. When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We're looking into options to make it more clear - it is a work in progress. diff --git a/source/_posts/2016-04-21-bluetooth-lg-webos-tvs-and-roombas.markdown b/source/_posts/2016-04-21-bluetooth-lg-webos-tvs-and-roombas.markdown index 72b13a6c8a7..af96dc1778f 100644 --- a/source/_posts/2016-04-21-bluetooth-lg-webos-tvs-and-roombas.markdown +++ b/source/_posts/2016-04-21-bluetooth-lg-webos-tvs-and-roombas.markdown @@ -13,7 +13,7 @@ og_image: /images/blog/2016-04-release-18/social.png It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs. -Since the last release we have moved all Home Assistant source code etc into it's own [organization on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info. +Since the last release we have moved all Home Assistant source code etc into its own [organization on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info. diff --git a/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown b/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown index 579cde5579f..89a0a442cc1 100644 --- a/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown +++ b/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown @@ -122,7 +122,7 @@ script: ### {% linkable_title Using both types of iBeacons at the same time %} -Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. +Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.

diff --git a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown index 48a43201b78..93bec4b2156 100644 --- a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown +++ b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown @@ -12,7 +12,7 @@ categories: Release-Notes When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms! -Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can [add it's own page to the frontend][custom-panels]. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you'll come up with! +Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can [add its own page to the frontend][custom-panels]. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you'll come up with! We have also seen an exciting trend of people starting to visualize their Internet of Things data using [Jupyter] Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the [blog] post by [@kireyeu] shows an advanced usecase while our [Notebooks][jupyter-notebooks] in the [Home Assistant Notebooks repository][jupyter-repo] cover the basics. diff --git a/source/_posts/2016-08-16-we-have-apps-now.markdown b/source/_posts/2016-08-16-we-have-apps-now.markdown index 535a88e0365..6edf3f8f4b2 100644 --- a/source/_posts/2016-08-16-we-have-apps-now.markdown +++ b/source/_posts/2016-08-16-we-have-apps-now.markdown @@ -26,14 +26,14 @@ So given the importance of Automation, what should Automation allow us to do? I - Is it open and expandable? - Does it run locally without any reliance on the cloud? -In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and it's Restful API. +In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and its Restful API. So why `AppDaemon`? `AppDaemon` is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table: - New paradigm - some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can't - Ease of use - `AppDaemon`'s API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible, experienced Python programmers should feel right at home. - Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file -- Dynamic - `AppDaemon` has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to it's loose coupling. However, it is better than that - the user can make changes to code and `AppDaemon` will automatically reload the code, figure out which Apps were using it and restart them to use the new code without the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result. +- Dynamic - `AppDaemon` has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to its loose coupling. However, it is better than that - the user can make changes to code and `AppDaemon` will automatically reload the code, figure out which Apps were using it and restart them to use the new code without the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result. - Complex logic - Python's If/Else constructs are clearer and easier to code for arbitrarily complex nested logic - Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened - All the power of Python - use any of Python's libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits! diff --git a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown index a7386785f15..1c4f4ea6a63 100644 --- a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown +++ b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown @@ -36,7 +36,7 @@ With the [statistics sensor][stats-sensor] we would like to introduce a new sens

-As the results are processed on-the-fly you still need to use the data from your database for a in-depth analysis of your stored information. Check the latest [notebook] for doing statistics with your Home Assistant database. +As the results are processed on-the-fly you still need to use the data from your database for an in-depth analysis of your stored information. Check the latest [notebook] for doing statistics with your Home Assistant database. ### {% linkable_title REST! We don't... %} diff --git a/source/_posts/2017-01-28-face-coffee-wink.markdown b/source/_posts/2017-01-28-face-coffee-wink.markdown index 6201e628ec6..26d05a6d945 100644 --- a/source/_posts/2017-01-28-face-coffee-wink.markdown +++ b/source/_posts/2017-01-28-face-coffee-wink.markdown @@ -152,7 +152,7 @@ Bugfix: [@balloob], [@fabaff], [@freol35241], [@pvizeli], [@Danielhiversen], [@t - Due to massive improvements of the [Wink][wink] integration, the names of your binary sensors will change and new devices can show up. - The [MySensors][mysensors] component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you. - The [Sonos][sonos] service `sonos_group_players` was removed. Use now `sonos_join` for this function. -- TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. `HASH_LANG_PLATFORM.xxx` -> `HASH_LANG_OPTIONS_PLATFORM.xxx`, replace *OPTIONS* with `-` on exiting platforms. +- TTS cache have change for the last time. Files use now also an option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. `HASH_LANG_PLATFORM.xxx` -> `HASH_LANG_OPTIONS_PLATFORM.xxx`, replace *OPTIONS* with `-` on exiting platforms. ### {% linkable_title If you need help... %} ...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. diff --git a/source/_posts/2017-02-04-babyphone.markdown b/source/_posts/2017-02-04-babyphone.markdown index 3703bcd1938..9da9d97c458 100644 --- a/source/_posts/2017-02-04-babyphone.markdown +++ b/source/_posts/2017-02-04-babyphone.markdown @@ -26,7 +26,7 @@ Next, we attach a `ffmpeg_noise` binary sensor to our IP camera. The sensor has We change the platform name for binary sensor in 0.38 from `ffmpeg` to `ffmpeg_noise`. Also all service going to component and was rename from `binary_sensor.ffmpeg_xy` to `ffmpeg.xy`.

-On Raspbian Jessie, you can setup [FFmpeg](/components/ffmpeg) and install a [icecast2](http://icecast.org/) server using: +On Raspbian Jessie, you can setup [FFmpeg](/components/ffmpeg) and install an [icecast2](http://icecast.org/) server using: ```bash $ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list @@ -35,7 +35,7 @@ $ sudo apt-get -t jessie-backports install ffmpeg $ sudo apt-get install icecast2 ``` -We setup a icecast mount point for our babyphone and update `/etc/icecast2/icecast.xml`: +We setup an icecast mount point for our babyphone and update `/etc/icecast2/icecast.xml`: ``` @@ -93,7 +93,7 @@ automation: entity_id: binary_sensor.ffmpeg_noise ``` -### {% linkable_title Trigger a alarm %} +### {% linkable_title Trigger an alarm %} Now we can make a lot stuff. Here is a simple example of an automation what should be possible with Sonos speakers. diff --git a/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown b/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown index ee59872448f..e92643be510 100644 --- a/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown +++ b/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown @@ -71,9 +71,9 @@ So starting this release, we had to make some breaking changes to right the wron [**Update: the online tool can be found here.**](https://jsfiddle.net/balloob/d2e56q6f/74/) -#### Customize has been reverted to it's original config +#### Customize has been reverted to its original config -The old customize is back. The options to match by domain or using glob have been moved to it's own options. It will now look like this: +The old customize is back. The options to match by domain or using glob have been moved to its own options. It will now look like this: ```yaml homeassistant: diff --git a/source/_posts/2017-10-07-release-55.markdown b/source/_posts/2017-10-07-release-55.markdown index bbe1bc77380..65175467125 100644 --- a/source/_posts/2017-10-07-release-55.markdown +++ b/source/_posts/2017-10-07-release-55.markdown @@ -63,7 +63,7 @@ Experiencing issues introduced by this release? Please report them in our [issue ## {% linkable_title Breaking Changes %} -- history_graph component: If your component used `history.get_significant_states` function then you need to adjust the string `entitity_id` parameter has been changed to a list of strings `entity_ids` parameter. ([@andrey-git] - [#9472]) ([history_graph docs]) (breaking change) +- history_graph component: If your component used `history.get_significant_states` function then you need to adjust the string `entity_id` parameter has been changed to a list of strings `entity_ids` parameter. ([@andrey-git] - [#9472]) ([history_graph docs]) (breaking change) - UPNP component: The `external_port` configuration option was removed. ([@balloob] - [#9560]) ([upnp docs]) (breaking change) - New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by "_" and no longer " ". ([@w1ll1am23] - [#9303]) ([wink docs]) ([binary_sensor.wink docs]) ([lock.wink docs]) (breaking change) - TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. ([@djchen] - [#9607]) ([switch.tplink docs]) (breaking change) diff --git a/source/_posts/2017-11-10-ttn-with-mqtt.markdown b/source/_posts/2017-11-10-ttn-with-mqtt.markdown index d619623c020..38341bdc9f2 100644 --- a/source/_posts/2017-11-10-ttn-with-mqtt.markdown +++ b/source/_posts/2017-11-10-ttn-with-mqtt.markdown @@ -195,4 +195,4 @@ sensor: state_topic: "home/ttn/garden_temp" ``` -This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to `mqtt_ttn` sensor which allows you to select the device. +This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to `mqtt_ttn` sensor which allows you to select the device. diff --git a/source/_posts/2017-11-12-tor.markdown b/source/_posts/2017-11-12-tor.markdown index 612faf1ffc2..cd4e018f7a7 100644 --- a/source/_posts/2017-11-12-tor.markdown +++ b/source/_posts/2017-11-12-tor.markdown @@ -27,7 +27,7 @@ The most amazing part? It is super easy to set up! ## {% linkable_title Setting up Tor %} -Our [documentation](/docs/ecosystem/tor/) provides an detailed guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward: +Our [documentation](/docs/ecosystem/tor/) provides a detailed guide about setting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward: 1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor` 2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines: diff --git a/source/developers/code_review_component.markdown b/source/developers/code_review_component.markdown index 9b7bdff4601..bebe3dc7847 100644 --- a/source/developers/code_review_component.markdown +++ b/source/developers/code_review_component.markdown @@ -33,4 +33,4 @@ Not all existing platforms follow the requirements in this checklist. This canno ### {% linkable_title 3. Component/platform communication %} 1. If you need to share global data with platforms, use the dictionary `hass.data`. `hass.data[DATA_XY]` while `XY` is the component is preferred over `hass.data[DOMAIN]`. - 2. If the component fetches data that causes it's related platform entities to update, you can notify them using the dispatcher code in `homeassistant.helpers.dispatcher`. + 2. If the component fetches data that causes its related platform entities to update, you can notify them using the dispatcher code in `homeassistant.helpers.dispatcher`. diff --git a/source/developers/hassio/addon_communication.markdown b/source/developers/hassio/addon_communication.markdown index 9b4d3fbdc16..c95be391a57 100644 --- a/source/developers/hassio/addon_communication.markdown +++ b/source/developers/hassio/addon_communication.markdown @@ -14,7 +14,7 @@ There are different ways to communication between add-ons inside Home Assistant. ## {% linkable_title Network %} -We use a internal network. That allow to speak with every add-on or from Home Assistant to add-on by name or alias. Only the add-ons which runs on the host network are a bit limited. They can speak with all internal add-ons over their name but all other add-on can't address the add-on in question with its name. But using an alias work well. Thus the name/alias is used to communicate inside Hass.io. The name have the following format `{REPO}-{SLUG}`, e.g. `local-xy` or `3283fh-myaddon`. +We use an internal network. That allow to speak with every add-on or from Home Assistant to add-on by name or alias. Only the add-ons which runs on the host network are a bit limited. They can speak with all internal add-ons over their name but all other add-on can't address the add-on in question with its name. But using an alias work well. Thus the name/alias is used to communicate inside Hass.io. The name have the following format `{REPO}-{SLUG}`, e.g. `local-xy` or `3283fh-myaddon`. Use `hassio` to speak with the internal API. diff --git a/source/developers/hassio/addon_config.markdown b/source/developers/hassio/addon_config.markdown index 005c8a0cd83..cf91e022b4d 100644 --- a/source/developers/hassio/addon_config.markdown +++ b/source/developers/hassio/addon_config.markdown @@ -140,7 +140,7 @@ The config for an add-on is stored in `config.json`. ### {% linkable_title Options / Schema %} -The `options` dictionary contains all available options and their default value. Set the default value to `null` if the value is required to be given by the user before the add-on can start, and it show it inside default values. Only nested arrays and dictionaries are supported with a deep of two size. If you want make a option optional, put `?` to the end of data type, otherwise it will be a required value. +The `options` dictionary contains all available options and their default value. Set the default value to `null` if the value is required to be given by the user before the add-on can start, and it show it inside default values. Only nested arrays and dictionaries are supported with a deep of two size. If you want make an option optional, put `?` to the end of data type, otherwise it will be a required value. ```json { diff --git a/source/developers/hassio/addon_repository.markdown b/source/developers/hassio/addon_repository.markdown index 645fb1cf819..9a8373fa514 100644 --- a/source/developers/hassio/addon_repository.markdown +++ b/source/developers/hassio/addon_repository.markdown @@ -10,7 +10,7 @@ footer: true redirect_from: /hassio/addon_repository/ --- -An add-on repository can contain one or more add-ons. Each add-on is stored in it's own unique folder. To be indentified as a repository, the repository must contain a configuration file. +An add-on repository can contain one or more add-ons. Each add-on is stored in its own unique folder. To be indentified as a repository, the repository must contain a configuration file. Check the [Example add-on repository](https://github.com/home-assistant/hassio-addons-example) for further details. diff --git a/source/developers/hassio/addon_testing.markdown b/source/developers/hassio/addon_testing.markdown index d1a2dfc17f8..f2f562f4431 100644 --- a/source/developers/hassio/addon_testing.markdown +++ b/source/developers/hassio/addon_testing.markdown @@ -16,7 +16,7 @@ Right now add-ons will work with images that are stored on Docker Hub (using `im ## {% linkable_title Local build %} -You can build an try the addon on your developer machine also. Move all addon stuff into a temp folder. If you use `FROM $BUILD_FROM` you need set a base image with build args. Normally you can use follow base images: +You can build and try the addon on your developer machine also. Move all addon stuff into a temp folder. If you use `FROM $BUILD_FROM` you need set a base image with build args. Normally you can use follow base images: - armhf: `homeassistant/armhf-base:latest` - aarch64: `homeassistant/aarch64-base:latest` diff --git a/source/developers/websocket_api.markdown b/source/developers/websocket_api.markdown index 4f226bc668b..76f7f0b0c7a 100644 --- a/source/developers/websocket_api.markdown +++ b/source/developers/websocket_api.markdown @@ -35,7 +35,7 @@ If you are not using the [`frontend`](/components/frontend/) in your setup then 1. Server can send results of previous commands. 1. Client or server disconnects session. -During the command phase, the client attaches a unique identifier to each message. The server will add this identifier to each message so that the client can link each message to it's origin. +During the command phase, the client attaches a unique identifier to each message. The server will add this identifier to each message so that the client can link each message to its origin. ## {% linkable_title Message format %} diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 766e76eef2e..472503ae24c 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -The goal of this getting started guide is to install Hass.io on a Raspberry Pi 3. Hass.io is our own all in one solution that turns your Raspberry PI into the ultimate home automation hub. +The goal of this getting started guide is to install Hass.io on a Raspberry Pi 3. Hass.io is our own all in one solution that turns your Raspberry Pi into the ultimate home automation hub. Follow this guide if you want to easily get started with Home Assistant, or if you have no or little Linux experience. For advanced users, check our [alternative installation methods](/docs/installation/). From 034e65aa1393e59e93bb2772b6a134d057019527 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 28 Jan 2018 10:01:06 +0100 Subject: [PATCH 19/59] Remove left-over from merge --- source/_components/coinbase.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_components/coinbase.markdown b/source/_components/coinbase.markdown index d39e34e3a73..f5d657ab4fb 100644 --- a/source/_components/coinbase.markdown +++ b/source/_components/coinbase.markdown @@ -28,7 +28,6 @@ coinbase: - BTC - ETH - LTC -======= ``` {% configuration %} From 5eba15c0e4f7a267a9afd22afdcc8c75df3b7763 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 28 Jan 2018 23:07:24 +0100 Subject: [PATCH 20/59] Add example --- source/_components/timer.markdown | 36 ++++++++++++++++++++++++++++--- 1 file changed, 33 insertions(+), 3 deletions(-) diff --git a/source/_components/timer.markdown b/source/_components/timer.markdown index 7cb9984ee82..61ff400aea0 100644 --- a/source/_components/timer.markdown +++ b/source/_components/timer.markdown @@ -92,17 +92,19 @@ Select serv } ``` -### {% linkable_title Configuration example %} +## {% linkable_title Examples %} + +Set a timer called `test` to a duration of 30 seconds. ```yaml # Example configuration.yaml entry - -# Set a timer called test to a duration of 30 seconds: timer: test: duration: Date: Mon, 29 Jan 2018 08:14:19 +0100 Subject: [PATCH 21/59] Change hassio to Home Assistant --- source/_components/notify.html5.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 8bf9a4c528e..4f96f0707c8 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -35,17 +35,17 @@ Configuration variables: 1. Make sure you can access your Home Assistant installation from outside your network over https ([see docs](https://home-assistant.io/docs/configuration/remote/)). 2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). -3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [hass.io instructions](#verify-your-domain-with-hassio). +3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [hass.io instructions](#verify-your-domain-with-home-assistant). 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project, and select the project you created. 5. Then, click the cogwheel on top left and select "Project settings". 6. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID' you need for configuring this component. -#### {% linkable_title Verify your domain with Hass.io %} +#### {% linkable_title Verify your domain with Home Assistant %} Follow these steps to verify domain ownership with Google Webmaster Central / Search Console: 1. Enter your domain and add **'/local'** at the end, ie. https://whitehouse.duckdns.org:8123/local 2. Select HTML file verification and download the google*.html file. -2. Create a directory named "www" in your Hass.io configuration directory (/config share from Samba add-on). +2. Create a directory named "www" in your Home Assistant configuration directory (/config share from Samba add-on). 3. Place the downloaded google*.html file in the "www" directory. 4. RESTART Home Assistant - this is important! 5. Verify the file can be accessed in the browser, ie. **https://whitehouse.duckdns.org:8123/local/goole123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps. From a71800bcbaeba5a98b18ddfc726639532c4e168d Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Mon, 29 Jan 2018 08:15:04 +0100 Subject: [PATCH 22/59] Update notify.html5.markdown --- source/_components/notify.html5.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 4f96f0707c8..f506eb18872 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -35,7 +35,7 @@ Configuration variables: 1. Make sure you can access your Home Assistant installation from outside your network over https ([see docs](https://home-assistant.io/docs/configuration/remote/)). 2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). -3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [hass.io instructions](#verify-your-domain-with-home-assistant). +3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [instructions](#verify-your-domain-with-home-assistant). 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project, and select the project you created. 5. Then, click the cogwheel on top left and select "Project settings". 6. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID' you need for configuring this component. From 5da84711b4e746ffec5b53a44ca6a64214b9aa80 Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Mon, 29 Jan 2018 08:16:40 +0100 Subject: [PATCH 23/59] Update notify.html5.markdown --- source/_components/notify.html5.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index f506eb18872..f53d7dc74af 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -35,12 +35,12 @@ Configuration variables: 1. Make sure you can access your Home Assistant installation from outside your network over https ([see docs](https://home-assistant.io/docs/configuration/remote/)). 2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). -3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [instructions](#verify-your-domain-with-home-assistant). +3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [instructions](#verify-your-domain). 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project, and select the project you created. 5. Then, click the cogwheel on top left and select "Project settings". 6. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID' you need for configuring this component. -#### {% linkable_title Verify your domain with Home Assistant %} +#### {% linkable_title Verify your domain %} Follow these steps to verify domain ownership with Google Webmaster Central / Search Console: 1. Enter your domain and add **'/local'** at the end, ie. https://whitehouse.duckdns.org:8123/local From 4c0c19e49bd8114c2d158c40bd011e39f1365575 Mon Sep 17 00:00:00 2001 From: dtorner Date: Mon, 29 Jan 2018 19:40:22 +0100 Subject: [PATCH 24/59] Update camera.markdown (#4546) typo --- source/_components/camera.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/camera.markdown b/source/_components/camera.markdown index 21629b68d86..2d922539935 100644 --- a/source/_components/camera.markdown +++ b/source/_components/camera.markdown @@ -40,7 +40,7 @@ Take a snapshot from a camera. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | no | Name(s) of entities to create a snopshot from, e.g., `camera.living_room_camera`. | +| `entity_id` | no | Name(s) of entities to create a snapshot from, e.g., `camera.living_room_camera`. | | `filename ` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id }}`{% endraw %}. | The path part of `filename` must be an entry in the `whitelist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file. From 9b31e9c476231fcc3f50f6994e01f61385a5dfea Mon Sep 17 00:00:00 2001 From: cogneato Date: Mon, 29 Jan 2018 12:20:24 -0700 Subject: [PATCH 25/59] Add files via upload (#4547) --- .../hassio/screenshots/local_repository.png | Bin 5185 -> 7388 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/source/images/hassio/screenshots/local_repository.png b/source/images/hassio/screenshots/local_repository.png index 0c0af4fb4349354e90d9a8dc33bd06cc9024639c..06bc8e245def1120d6eec8ed219d2a6518bfac2f 100644 GIT binary patch literal 7388 zcmd6McT|(xvo?wXN>}L-j9>*0MT#7n^dKS@B!~zCB7_zp(g_hnIwXRCQU#)-bPT5bFyQ$kAJ6WmPhAi2wFhy{!kDX~AM_Jw?DH_PHsa!{M)PmE><8Kh?n7=O zxVVHmci(#m@RGYg=b;B?_7ASZ?>z{132^7K2yl1zLwLd;INjg_L_pUqO^s|roamGE z(%T--35+f7Hpb)W7SVm8q6dzr7R6sY@x)G~V=$5O^~FBjX%kJ7of+hL;!y$l{c3q_ z1LkL69wj;OjQ>h5A2{R%28b?STONc{D$bL4r zgvV0tA_3{ZLf5hk##UCo+5~61-vnNEx7;D`lzM8Edc3LxVE^<9W`g^GjvA%X4t4DA zq)c~Bdqp7_io+~W-kn-grdi@JeAe3wlGJgzz+iIwrw!_lKu?X`)w^#qVrmC4nVn;A zuD@8oY$C|)RkurdW=BZ}MtqMi4E9EDu922MuV9&m`}^+M8Zjwv zrIM6b4W9Es3-;`Vcf`xF848wzUQfzD+21XHZtUP_MoF6(D7HA&X_=+~E5}rSaxj5@ z`O>JI{C^vr)jb|*d|q}qSyi*bgSNv zt_7c(pp)BC0S~m$ddm=Y(@1Lt%DV0MW0eP}^&aPw9{04D!q#r98n)+zDl01o22Tb; z*&V`>RpG$s6q+3^(ek2sI-0*}zM{E8H{i!7>`Mj9ZUGqWy+aI6#;>7J_?$}EK+;B) zxo6G@`8ZaeJ%N}+N3Ikv)>a~Y4S807LED?gYuv5aue4j=kYxx?Yab+nbb}WcI&&2) z!}7s&ki9QNH*zb4-NtUM4DXbg`huJ}TrlS>VLaZ#5eL(G4cCm=X<02;VYh7X(^>Al)p)j(feHDWIAusn+HhiJF(b&Oh=LYolkUq2bT>81rwO;8>Mff~^ zYb#>;^QmSPj>3s|}0y-4n23$uT5%%gygW-@1U;EUvEZ}h`iD+HrY z>)&1*3=zA;v%|~SVPB0+i2sN(>;@ZJF!n~Xy3=ziDi zsibQ}gg$JnXj$&2!fVVS#ogo~VkGOG0VE)mY&GpA&qS>h%hB1QA-!rO6jjk#N3p>w z?OXO^L72bH{SsmLhX{NEbN%2q6Jh;ttqbld^OaTKhWm%)_KMEC6vTikCVubXkZzPo zqOXY856%k0s!ti4x79v}gNOI>bfj=;<6iSchU$m*k~}&Z{_dhppEtCEYyx&T$zJ~* zXE>4fcc53mgC@Sa5ke|$KcxuW<1fC?JMV;{IN9D6&q1MWMC~?4%I7CEM)Sj}uG7Z|*DJ^|c}WF6B=xvc{uk61Ts#$F^i@ibeyaXPdve%Uyigdg|k*voqwX&x;?Kdpb#0NgaYE;}Gh*T1&Y71`PoJ2OP17J>)%L&XM zOgMb1=@G9m3)&>9*aoR0Vayw5&PurrRb)~XZ#hc!G^AWLEATOu(L;6 zW|IT6_;ixP4NM&97fD~X7~~5EMCAdizZ$WIml=&32B=RSOF~Eg#+~eNOv5r=ZpUe) zBJzW9gfiwsZO&HT2ghB1+8j?W6@)Ry>I1eM{H-*|6*+aULyj(ot$k)zW9(vIY=vct z`Sy2t47x5{Q^rP(oJ93#N*D#tbr&jFDvyak2iJNf3oJgAF@M0Vm+1uhcs(2HzP9P^ zIQjN*UZ}A{#I$~!zC-DnIc&Y}b3>ZlCP>^1uybt6<2Rwkq{g)%52+6yu0Z%5H7UQO z>Muwcwx!%^c2}~z<}I#;H9If8dC6gGGi&`EjG5oqRD^n^2iM@sfFnl8b$de@%NZ9;vK8J0^2-cX4Wmw_l)6sXDSTuUhVJEtPIy`! zi}>~C^-1NOjaVBlmx%t#lURoKn56v98w_~;oj0R?q9H7hUOU1fG?WvR4XPsjdd&IG zjvRJL)c+mUHE+Q+n^Uw>cux>^dWYV>%sO64J{mkRP?@0P1wHE_2#X&{yY+2LQ8a2K zS}~|B!7y2uRe2SX_APqWn1t(g@l@t?MXi;tFrW)(@X4tD)6PE=0ClL6mW3a^J83}f zqP3`6L3+rfUewb-zVHOaJL_bo!t_UHlE>|ZQ-CbAZ8>Ax!E64^j^_TocVZO%P9P%k zF|oXI5mmyb$wpmEr*@L|w4_d4OI6Gp(*viBno(uGj0TG)zag3A=pPUkbHhcgk^omyIKmJKMQ1otL(9@?vxh z`0D zlflkA5mOkR;oV0z^f)3UlAt>^Kqu9f{z(O>W3vZf@nmI$s)X-M@T{1Ig}I5$w7F7J^YWKb;V%U&2er=y-+m*o@&t4Hl{ zK0om`s+@2%V=g%C=g-B`od+I3v`%VT#Ecl0nvt6o@`U?hH1>A0=;OqL7xtxF z=V+Cm$M(4nV}kzj#bS8&O2d0wj64{zt(yf)d7$TgMQz{VI7}vxUB0P!j=_t)1-vv@ z?Am#AD#jdBtp8m(Q4Paw9aD9?IY_xa$-n3}2+eh*u*wG=aUvy9ozC&Z9qX>{ z#&osKfc6ABKzitI6(P#5JMk=PMC~z1P79%Bwl7D!U_dKUqEKtde(=%mTHlZ!LSiq zNb}}mGx4AdsGVLnp83c$CJiJ$cR1=e@6!-Rp6t1vb>ROP=sYvs@pO*WAk9{L%FL^D z3eyoU3Y{A()Q>!t)J11)(gLFznM@JpkCA8o%h^onZW=CSyJ+HTSqP$Xe|CsT|M#f( z7!ydOEPM@=q|FA^sN;_-nMz*J3CfocHFmueX+9ml?kY!R1}tnv_)LDqE3=;vjCGvM z$=;mr!&FT(Oky4AwTdBgi5qujM2^_8QH1nMa&S(~@J^wv2Y+m+4z?tn&OQj^6_#Bv zxgaE?r^0P>Chjqx#>!{3iI7HaK~VEK-t>uj@he5XF@<_6bHsI0lNaSNjNa4ME80=2 zf!nc1jH$3}4a{|x%DS}~Tlf@EW_R7#s7&M;bV4C(Uku-V_Y0rEMRgUm_H3L#lY$xf z%m96?38Hi@OY7n=o5QSrL~2}NEuiILTZsJW`WfAi@Eur)M z_A5012q9H;RyA!DwV?6^r3qG!JNgv@&>aIdLBL%!_*Olvm2QmZ|YvpbylnTE`?TS%Ph^VtO)m*VjIG_Bi>df`xj>SrV~7fdo2DMDKN-mYbQxJY8Ax86Sy z;5qd^G}^IkMhiFFva=;gm7W!auNZRrIq&v%*hAvAgQmXxv$@b*@IHaFKMZ<1C(6KO zT}`i3bTxSAx7d|aWOT-6=6MSl5`OAukA%Yc*p{|z(t2T_i)MHhHl?Hy!xMd>ExU^d z8VtCTK=bx*e&@(bq=>ugp_#Q0(@X>qv%-^E;L~U^TEM0f>uMb_3PzHYqQN96j|2Ls zh~eJ9?S-GAPB5(xLvIF%7)N%hkQ3;@3v`|D3C9&a zhT;=0bXISje~J**kc^{a{~vz4EcI;Usuk9(~tPzq?q^;&jRvqQI}$I+io?Jm4w8H zJb18%DlaYIj){<-t>jE=PYAmi{499M-(Z6pILv9! z#IBYkU|!W4LEi4KJOuVy=-L1G;SMk_HdFL2-$hYR;I7t#sk_{JsKxUfiyDofzkg(- zlrm6~@qWTW@^%b=n2|YB}%^9eR<&>cV zV@Ybm&pW@4g373aRx0!$I%%jNsoFE0EghbqRtG2h0gJ%6?LPq_^YflF8y0-o;)9a# zGE_q33US^|!1y{yk(R4vk$jUMT|FXsZb^TZ`dY!#p&dYS|Jo8eQQPAaPoolPq9NVy zpPD%I-r)H#(SC$trdlKj?Wpq^tI^}7Eaw&|K7S-lvRKIA=*)pPc8}PBEWUWrLAl`} zO*9Q}OtRmp*8K6?^p>A)K&g7FH9zzd!gTa3t%vf15Jdo;1F|t(oAO;q>1|l?aY-|b z)Ik{Id`=xtzXji2$3%kTRX3$!`y7=XM41AXiu3?!{}Cw9QG|`*Fn04qCZCI@j%~GU zB))pwubH0wzBWzA?$F>eMI`*+wH+ZcUOh}cS2wV4iJ@LvQER<%^=Go&W~Slmu!tq=@IT(^3_w~fF{h^v}D@mBI6wSjIr|ljNpVKVP8)fLY(pS z&{JnVT;1Z=t8Jr>+AbELh0Ehy4P8!vQ&N_y9CAFSiFpjdxX8MqHw z%GmA`G&YM#RxkO;oY0cT{!mTd{Ps~#?edshZqgSqy1c;957xBDx<_sIw0VIZTnJ_o z-WOg4jHew8-J8*8;HG>1(O}e*s7;VWb$R{FE-0q=pzjFTUNq z{S>TB%t$ie6#~tnGQs5&84A`rZ^K(=0v_V_R3bTA+!g zB3?==&ItWE1)8R`Vs*ON2xs?KJE zkU3f-#%Drc|(#|p{W6rjYvJBOG5Q?`K36730QDJ zzCeYh#Fm}c04yAPL-CP?IIWw@>@+yuGy@5kmHl%~ESUF235XQHC+}G3c#4Sl?V1Yu z;5GjODeLA_`E=KE0Do8Az29g8SROQTJ2(*Pj0`k%>ccVJWW(kP7ngffmgZUG@Fl|c z(XwZoB=1VPEOKSw^Aki;XhUz4IJ25njjW_PYHo2Vntr`yvPgi1$Z8xOthg(>4RFOFAcD6`oTjQBE=dc7jBU5(&HTh|fKl{DPAT0M-R zxx=fMFl@{7`Qn4!BM%weXes&jDQf7h#l3@_#nLC6*~!|$c-k70Jy{Pj26EczcvU<8 z%g2&GK5K;Q%|^rrs@_}AWw}8IJ#Xrkqk;{%$r)S!;M*C`> zCDGJudUeH%TqE%1`ZN#Oc1JlH0iUH{>EV4Ad(?<2H} zIK|HW6eW{i zuD##;Y723@%o{o!Cha5}wzfmF}mYZ_|JCLe2!*Z^$ z7hcY_O*Yzrfy;9rwGOkoLXvx`Ney3F_y(%?rExw2b*e}6{uB@@27R*mVJ+1bqtlXx zI`|v|bO(`74A&Qh{kYC&wvzN4BbRmjn@EJ~l%9vRl&z<>c#Ui1Z2T%!4Znd<`f#(% zFxuAFxmqrD2;Ud(CMde$x+SSwTn^Oxv541=82mH6S%jykK*&3E)sgdr8``8<$_bL1 zfv3cGu%Ya=I-q`HEmJ^g)L)kDJ$Gc#6B>Im|N4r1^60r&^l+cQo`!R8OT{r>(ewUQ zgCm67Mc(;Dchs@_$y)CAXZ#KJS_uieV=gqN>Zxd2LAVLaP0ZX-pWnILA0^#7-sC3H z)@x4_{&FTx6wEN};}ZkFRpe7hyh_BgM7_auG=WhQ zAPn9xrLHgQY%J4*{cu zUn5ogU-D_c*m{DJ*}syt56x3zaSc?sUV%fU5Aky{fF{$2z^rc>DoWk)#(>ki@_;H=hzpe;;jNs z+2rH?$9i6K2+u}rP*cE3gbJ`{{>Ppyw(5! literal 5185 zcmZ8lcQo8v*B&L2=m|lH3=tO*Av%dsq78`5ORW~T;$Ky*-bgpS68D@sGB!$hJ=LB z($WS61(}VJ{TzkcoHQ)QA144EHDnz@& z?tVsh-Rv@Y+n6)?_ws(cEn;D8>kpn}a5HgsXv6$YT0{0Q`uo~=*Yes=>>dW6?1+pq ztNq^av$hsY{I9s-jTRCyo{LJR`8uqq>rC8;QO8ub1p`hTeNQE+NL}kd7l)WI4k7xsf#`68y z=u`rPOI8Q57)_}2fQBag#MQbGB_R`gibTaT=Z1Y?9g{sbFe>w$g-NZRR-@{QKj-Rf z^jx7i@*7a2MjGDg63-AwUrBlP)YRB@PGbmwCvgUyQ{9HDye!dT$B??jr45yt zWBjzC-bMs7>0FskQxeYd1Kr|Z7_4rzhpUoK71mD#^{lKXq&-|VYev-rdsQe~Ug=SR zPhy(hyzmn2&lEF4Is~|uJF=_HYn1$8&@wfy-Nsl$bC&DA6EX31$*1Oez1v|opHKZo zNFB?ly|W`^VV3VB31I2|@eh#;!ok{fqZgBeZU8?v!T(aIS66AD@JxMXB- zbqTtLg43IB%)=A+ha7ySdos4Pkc2hy_Ai9e5+JlLMyK;l3052W)bzmG5QEb#nV9m8Do?S(5WRe0y*osoy!y~J=kyc-NM0HwP-3``b=Z>d1QXO z?N-ff*JSlk7>AfV->adRh$1QgWegYQ&%6J5{}TV2z^6a~WPmlM&G8?|z37@s*_ zRW$?~ltzxN6&6gh;~p(cb~ZeTnsqSEdAwA!n=nmPeKc-?`wEd);8N#*iiqCsU|JIv zVo_)k-DhPryk5^j&9Twq_hK;z?%HD^)~5PyyG*o+`IR6Tbb~=qla&*y{@1 z*B^B1&$zx(LM}hZ4BPa(N5d%KNcsKl9sBNFkshUoFLMQo$vj!U7jv702974_!3@O# z=Ni0>(wAFgUq?xYvpbw{IM(}SVBKpwMRtqELAtJ0nYQWDUU`K4sm-&W-g`E<*MaBd zkwu0%{>?d#USHZAa)Ub=@Xat+-NgxFle_se3l-xhgWV(Z#4J-)`9zbX92TR+2&~G> z?(Qub@obXo1JdR2xF|I|(@s%@5X?Qo;RfN8;)vl=4{OV_$QXX9$t)A}QMz73;#>gy z{auaU<`!3-)OO!^vsJhh7>F^!9X-+mF4^8PoJegn36D;_)X!ViAAFA+;Z?doB%h_K zOT8XxB~Wm=K8|BUtj|c~U5RNa?pdoZ>YMm)FJtNHS-Wm-I4&EPlmDr`cR?%o=#9w{!nRYkXQo|s6 zkvDqsNM0rZW+ouD>O99KNYa@UnKbRMP*CdYNp~$M{vRwbU~3dfaQ<93 z8{{qeP)^`+JmuV_+CX9f))1HXeCR7BV&`OeS#O(E1*uT%gh0`TDVVEbNk`3vl`mTt zUYLg@4s5->9#NM1m(jh2(86K1-gM;^Gl7WrCedZ(0q;6jv5;*j3yxu|FYo~~T-|E3 zv2hz1NtV_sWUaIvR9Zu7}`$o<5}Q;o>(H$Lqz zZ7Qc05+BF=`?`0%mjt8}x1$apEq_M(*FLjU-v35UM|t-*x5W4-VaAuoh40SdO=$Us zxcV+FqZJ8~9-Cr4bU=BQ8oofkrUi4`QVUgRFpjswF%)UAB(RhwkLt~) zzDtRC$xFtApn4ob=e-$0e*T%LMN;+Vlriv_)!d1Q3aF-+V-+?zI+~WZ|BkOjTZ26( zk3a5|q6%lg()pyq5M=oTo5mFBX{wqrB`hiQks?P6OWUN3C}hC& zf{z%Itm}e>a}u(#N2j9dAK#gMEW`qRJo@1mr3YhgIHSukzIl-pIFXF?uBYT3WcI zfAyX(<{b*$UE>D~?mp_R%BUjNN)H>GFw6S@Qx!?rDy_Ldh9?h3gBK>G9>V7r2w^ zn@yOzRR%0DWsXzM`4*vc8RL+JA}rjQbhgUa3VyURg>6Pl5o1-QK3}{pa9Uc&+iGEW zzswWxO?|BejduqXxB5djw6xYwwYAe+Zaf3~HG9No6TcqNB^)#+>)%o6&!A0@5u7Z3 z5oc3POqHndhpoI8FS{FlJC<9Fvxbz0%v(T?jxdRU#|`rBzIr%37T)II`8bv0Tt=vB z|CpD>UL)lU4aMJ;9~zXZ_vI14yUs4U{Arzyr_C-tyX2tW@rRs=$Jq`+I#i*NeiIY; z+<>7sH~`mZsC!0tc!)JLTe3|LW}jZqyL}%J2Wh{iDU5{*F7|o|=5muE-qm3yQE} z2=+QIf@Q!00z%G@)hmp*ViQR@433LuLV}M zHUiQDkzZr7P{)YVJslNb3IWjc5XyzmM z-g>hqioQK-K!N!FN8`sUtTrka5noq>m4J8*B3i)s!%*cgTJlHGoXBRJGujKRpccT=2fGU8gEeL@O!6{vBxnDS}Inj{HbcNe)5l?$Znbo z@E-`3fVtCrd_Hb>WaJ8B4!=%*m7BRkoB7@79lNJY_v)tBr|U01NJP<+kCL3)`2B>|g3^j+}vJYt$5D0vD6$ ztR8M7?crIxhr8BfMI(?%pHP>Fvq{G?`YSNn!vH6iXYAm4*H8p+X4ZgGLEAQ1hP%@@ z2OKuP$4$6lNR{N#_U9_%*DH#HN$FP3ez4d`*Ds+0zo@DKWDQc-=%r3uUq@8qv^nu| zsK{xUXJ?cAfz3?CUu%)gLrU!4G9M__3QXcvQ#QWpC!nuX7WA19kK`n5yahRGgs$~^ zjMb?PcQEm0FUiEpsptBAWww9nSKBoFQ_>UZiqA4a0wHFa*j(3Fq?`z|?$(BU^Ln5G z5bdpfLJ#R|UXgd8uiX=`4wsyB3{Q8{XJY)pIA($1wzOU$pR}oeDE&v@_S)t*SoB)T zgF^lmM~&akt&3M2y!~H71EQ(i5BgQ@R1j zI6WX==b!>32b6TJ;pzx&%JGAc=R~xjlFz&*L3H4qvjihG|c$+Y~t3H9VjlUNuigP$aIy7!s$Uy$x}LkeBEU9cL}mQ?TkRVw(R=(a zFJ~yaF9wM-L&L9|>miChoH*=1eIgzv#v4%x2+%y~Y6OWFE)P>lP|)U5`;tZLW{HzA znsHr}!*g3)E#eKQL<4XRT6yMnn}9xC^xvA64r99lTFSjm$37zUi#>WoIwJEA3ERcH zNg-3~*cjRHPlNEJ|Gz=aKb_(aiIfGL#J1+n9HTnDv0|hLK$75nmRD_qcomP8qrl*f z7sI`-Za0~XP2?eqwG$hgRd$1Rt&6HrB|SS9V(XtL=vd&qEAQT}k^eJES_&bM*|wh- TS8G!y{7pbrw3Mrrtls Date: Mon, 29 Jan 2018 23:42:45 +0100 Subject: [PATCH 26/59] Update for 0.62 --- source/developers/credits.markdown | 202 +++++++++++++++-------------- 1 file changed, 106 insertions(+), 96 deletions(-) diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown index 9e5a224e4b6..3055c86bb31 100644 --- a/source/developers/credits.markdown +++ b/source/developers/credits.markdown @@ -2,7 +2,7 @@ layout: page title: "Credits" description: "Credits for the developers who contributed to Home Assistant." -date: 2018-01-13 18:07:58 +0000 +date: 2018-01-29 22:42:30 +0000 sidebar: true comments: false sharing: true @@ -13,22 +13,22 @@ This page contains a list of people who have contributed in one way or another t ### {% linkable_title Author %} -- [Paulus Schoutsen (@balloob)](https://github.com/balloob "6125 total commits to the home-assistant organization, 3619 commits to home-assistant, 1332 commits to home-assistant.github.io, 682 commits to home-assistant-polymer, 244 commits to home-assistant-js, 118 commits to netdisco, 44 commits to home-assistant-js-websocket, 26 commits to hass-release, 14 commits to home-assistant-assets, 10 commits to LabelBot, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 5 commits to hassio, 3 commits to hassio-addons, 2 commits to hassio-addons-example, 2 commits to hassio-build, 2 commits to python-hassbian, 2 commits to issue-bot, 2 commits to lambda-home-assistant-github, 1 commit to home-assistant-notebooks, 1 commit to warrant, 1 commit to home-assistant-iOS") +- [Paulus Schoutsen (@balloob)](https://github.com/balloob "6159 total commits to the home-assistant organization, 3630 commits to home-assistant, 1345 commits to home-assistant.github.io, 689 commits to home-assistant-polymer, 244 commits to home-assistant-js, 119 commits to netdisco, 44 commits to home-assistant-js-websocket, 26 commits to hass-release, 15 commits to home-assistant-assets, 11 commits to LabelBot, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 5 commits to hassio, 3 commits to hassio-addons, 2 commits to hassio-addons-example, 2 commits to hassio-build, 2 commits to python-hassbian, 2 commits to lambda-home-assistant-github, 2 commits to issue-bot, 1 commit to warrant, 1 commit to home-assistant-notebooks, 1 commit to home-assistant-iOS") ### {% linkable_title Contributors %} (in alphabetical order) - [7even (@hwikene)](https://github.com/hwikene "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Aaron Bach (@bachya)](https://github.com/bachya "36 total commits to the home-assistant organization, 23 commits to home-assistant, 13 commits to home-assistant.github.io") +- [Aaron Bach (@bachya)](https://github.com/bachya "40 total commits to the home-assistant organization, 24 commits to home-assistant, 16 commits to home-assistant.github.io") - [Aaron Linville (@linville)](https://github.com/linville "2 total commits to the home-assistant organization, 2 commits to appdaemon") -- [Abílio Costa (@abmantis)](https://github.com/abmantis "20 total commits to the home-assistant organization, 12 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-js-websocket, 1 commit to home-assistant-polymer") -- [Adam (@SilvrrGIT)](https://github.com/SilvrrGIT "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io") +- [Abílio Costa (@abmantis)](https://github.com/abmantis "20 total commits to the home-assistant organization, 12 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to home-assistant-js-websocket, 1 commit to netdisco, 1 commit to home-assistant-polymer") +- [Adam (@SilvrrGIT)](https://github.com/SilvrrGIT "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io") - [Adam Baxter (@voltagex)](https://github.com/voltagex "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Adam Cooper (@GenericStudent)](https://github.com/GenericStudent "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io") - [Adam Dullage (@Dullage)](https://github.com/Dullage "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [Adam Mills (@armills)](https://github.com/armills "286 total commits to the home-assistant organization, 150 commits to home-assistant, 81 commits to home-assistant-polymer, 51 commits to home-assistant.github.io, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant") -- [Adrian Popa (@mad-ady)](https://github.com/mad-ady "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") +- [Adam Mills (@armills)](https://github.com/armills "289 total commits to the home-assistant organization, 151 commits to home-assistant, 82 commits to home-assistant-polymer, 52 commits to home-assistant.github.io, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant") +- [Adrian Popa (@mad-ady)](https://github.com/mad-ady "5 total commits to the home-assistant organization, 4 commits to appdaemon, 1 commit to home-assistant-polymer") - [Adrien Ball (@adrienball)](https://github.com/adrienball "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Adrien Brault (@adrienbrault)](https://github.com/adrienbrault "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Adrián López (@adrianlzt)](https://github.com/adrianlzt "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant") @@ -51,12 +51,12 @@ This page contains a list of people who have contributed in one way or another t - [Alexandre Perrin (@kAworu)](https://github.com/kAworu "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Alexis Iglauer (@ax42)](https://github.com/ax42 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Alfie Day (@Azelphur)](https://github.com/Azelphur "12 total commits to the home-assistant organization, 12 commits to home-assistant") -- [Aliaksandr (@minchik)](https://github.com/minchik "7 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant, 2 commits to appdaemon") -- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "125 total commits to the home-assistant organization, 75 commits to home-assistant.github.io, 45 commits to home-assistant, 3 commits to home-assistant-polymer, 1 commit to pi-gen, 1 commit to hassio-addons") +- [Aliaksandr (@minchik)](https://github.com/minchik "7 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to appdaemon, 2 commits to home-assistant") +- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "132 total commits to the home-assistant organization, 78 commits to home-assistant.github.io, 48 commits to home-assistant, 4 commits to home-assistant-polymer, 1 commit to pi-gen, 1 commit to hassio-addons") - [amigian74 (@amigian74)](https://github.com/amigian74 "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [amorsillo (@AndrewMorsillo)](https://github.com/AndrewMorsillo "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Anders Fogh Eriksen (@Fogh)](https://github.com/Fogh "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "126 total commits to the home-assistant organization, 91 commits to home-assistant, 33 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") +- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "131 total commits to the home-assistant organization, 95 commits to home-assistant, 34 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") - [Andrea Campi (@andreacampi)](https://github.com/andreacampi "8 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to home-assistant.github.io") - [Andrea Falcone (@asfalcone)](https://github.com/asfalcone "5 total commits to the home-assistant organization, 5 commits to issue-bot") - [Andreas Björshammar (@abjorshammar)](https://github.com/abjorshammar "2 total commits to the home-assistant organization, 2 commits to home-assistant") @@ -65,20 +65,18 @@ This page contains a list of people who have contributed in one way or another t - [Andreas Renberg (@IQAndreas)](https://github.com/IQAndreas "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Andreea-Daniela Ene (@AndreeaEne)](https://github.com/AndreeaEne "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Andrej Friesen (@ajfriesen)](https://github.com/ajfriesen "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [Andrew (@aneisch)](https://github.com/aneisch "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Andrew (@aoakeson)](https://github.com/aoakeson "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "692 total commits to the home-assistant organization, 560 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 19 commits to home-assistant.github.io") +- [Andrew (@aneisch)](https://github.com/aneisch "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") +- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "734 total commits to the home-assistant organization, 602 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 19 commits to home-assistant.github.io") - [Andrew Smith (@andrewmichaelsmith)](https://github.com/andrewmichaelsmith "2 total commits to the home-assistant organization, 2 commits to pi-gen") - [Andrew Stock (@watchforstock)](https://github.com/watchforstock "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Andrew Thigpen (@andythigpen)](https://github.com/andythigpen "33 total commits to the home-assistant organization, 32 commits to home-assistant, 1 commit to home-assistant-js") - [andrew-curtis (@andrew-curtis)](https://github.com/andrew-curtis "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") -- [Andrey (@andrey-git)](https://github.com/andrey-git "264 total commits to the home-assistant organization, 116 commits to home-assistant-polymer, 111 commits to home-assistant, 37 commits to home-assistant.github.io") +- [Andrey (@andrey-git)](https://github.com/andrey-git "275 total commits to the home-assistant organization, 124 commits to home-assistant-polymer, 114 commits to home-assistant, 37 commits to home-assistant.github.io") - [Andrey Kupreychik (@foxel)](https://github.com/foxel "9 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.github.io") - [Andrzej (@andriej)](https://github.com/andriej "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Andréas Lundgren (@adevade)](https://github.com/adevade "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Andy Castille (@Klikini)](https://github.com/Klikini "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io") -- [Andy Loughran (@andylockran)](https://github.com/andylockran "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [andyat (@andyat)](https://github.com/andyat "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Andy Castille (@Klikini)](https://github.com/Klikini "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.github.io") - [anotherthomas (@anotherthomas)](https://github.com/anotherthomas "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Anthony Hughes (@tony2nite)](https://github.com/tony2nite "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Antoine Bertin (@Diaoul)](https://github.com/Diaoul "5 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") @@ -86,6 +84,7 @@ This page contains a list of people who have contributed in one way or another t - [Anton Lundin (@glance-)](https://github.com/glance- "7 total commits to the home-assistant organization, 6 commits to home-assistant, 1 commit to netdisco") - [Anton Sarukhanov (@antsar)](https://github.com/antsar "6 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") - [apo-mak (@apo-mak)](https://github.com/apo-mak "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") +- [arcsur (@arcsur)](https://github.com/arcsur "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Ardetus (@Ardetus)](https://github.com/Ardetus "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io") - [Ardi Mehist (@omgapuppy)](https://github.com/omgapuppy "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Ari Lotter (@arilotter)](https://github.com/arilotter "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") @@ -98,7 +97,6 @@ This page contains a list of people who have contributed in one way or another t - [Assaf Inbal (@shmuelzon)](https://github.com/shmuelzon "11 total commits to the home-assistant organization, 9 commits to homebridge-homeassistant, 2 commits to home-assistant") - [Audric Schiltknecht (@chemicalstorm)](https://github.com/chemicalstorm "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Audun Ytterdal (@auduny)](https://github.com/auduny "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [aufano (@aufano)](https://github.com/aufano "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Austin (@trainman419)](https://github.com/trainman419 "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Avraham David Gelbfish (@adgelbfish)](https://github.com/adgelbfish "2 total commits to the home-assistant organization, 1 commit to hadashboard, 1 commit to pi-gen") - [azeroth12 (@azeroth12)](https://github.com/azeroth12 "1 total commits to the home-assistant organization, 1 commit to appdaemon") @@ -107,7 +105,7 @@ This page contains a list of people who have contributed in one way or another t - [Baran Kaynak (@barankaynak)](https://github.com/barankaynak "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Barry Williams (@bazwilliams)](https://github.com/bazwilliams "10 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to netdisco, 2 commits to home-assistant.github.io") - [Bart274 (@Bart274)](https://github.com/Bart274 "26 total commits to the home-assistant organization, 17 commits to home-assistant, 8 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") -- [Bas Schipper (@basschipper)](https://github.com/basschipper "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io") +- [Bas Schipper (@basschipper)](https://github.com/basschipper "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io") - [bastshoes (@bastshoes)](https://github.com/bastshoes "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [bcl1713 (@bcl1713)](https://github.com/bcl1713 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Beat (@bdurrer)](https://github.com/bdurrer "11 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") @@ -127,11 +125,10 @@ This page contains a list of people who have contributed in one way or another t - [Björn Orri (@bjornorri)](https://github.com/bjornorri "1 total commits to the home-assistant organization, 1 commit to home-assistant-iOS") - [Björn Ramberg (@bjorne)](https://github.com/bjorne "1 total commits to the home-assistant organization, 1 commit to hassio-build") - [Blanyal D'Souza (@blanyal)](https://github.com/blanyal "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Bob Anderson (@rwa)](https://github.com/rwa "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [Bob Anderson (@rwa)](https://github.com/rwa "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io") - [Bob Igo (@Human)](https://github.com/Human "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Boced66 (@boced66)](https://github.com/boced66 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [boltgolt (@Boltgolt)](https://github.com/Boltgolt "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [boojew (@boojew)](https://github.com/boojew "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant") +- [boojew (@boojew)](https://github.com/boojew "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") - [Boris K (@bokub)](https://github.com/bokub "11 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 5 commits to home-assistant") - [Boyi C (@fanthos)](https://github.com/fanthos "11 total commits to the home-assistant organization, 6 commits to home-assistant-polymer, 3 commits to home-assistant, 2 commits to home-assistant.github.io") - [bpoirriez (@bpoirriez)](https://github.com/bpoirriez "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") @@ -156,11 +153,11 @@ This page contains a list of people who have contributed in one way or another t - [Bruno Adele (@badele)](https://github.com/badele "22 total commits to the home-assistant organization, 22 commits to home-assistant") - [Bruno Binet (@bbinet)](https://github.com/bbinet "1 total commits to the home-assistant organization, 1 commit to hassio-build") - [Bryce Edwards (@hoopty)](https://github.com/hoopty "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io") -- [c727 (@c727)](https://github.com/c727 "18 total commits to the home-assistant organization, 11 commits to home-assistant-polymer, 7 commits to home-assistant.github.io") +- [c727 (@c727)](https://github.com/c727 "21 total commits to the home-assistant organization, 14 commits to home-assistant-polymer, 7 commits to home-assistant.github.io") - [Caius Cioran (@caiuspb)](https://github.com/caiuspb "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Caleb (@finish06)](https://github.com/finish06 "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Cameron Bulock (@cbulock)](https://github.com/cbulock "5 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to netdisco") -- [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "95 total commits to the home-assistant organization, 87 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to fabric-home-assistant, 1 commit to homebridge-homeassistant, 1 commit to hassbian-scripts") +- [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "95 total commits to the home-assistant organization, 87 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to fabric-home-assistant, 1 commit to hassbian-scripts, 1 commit to homebridge-homeassistant") - [carlosmgr (@carlosmgr)](https://github.com/carlosmgr "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Carter (@BluGeni)](https://github.com/BluGeni "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [cdce8p (@cdce8p)](https://github.com/cdce8p "21 total commits to the home-assistant organization, 12 commits to home-assistant.github.io, 7 commits to home-assistant, 2 commits to home-assistant-polymer") @@ -187,34 +184,35 @@ This page contains a list of people who have contributed in one way or another t - [Christian Brædstrup (@LinuxChristian)](https://github.com/LinuxChristian "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Christian Lasarczyk (@ChrisLasar)](https://github.com/ChrisLasar "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Christian Studer (@cstuder)](https://github.com/cstuder "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") -- [ChristianKuehnel (@ChristianKuehnel)](https://github.com/ChristianKuehnel "15 total commits to the home-assistant organization, 8 commits to home-assistant, 7 commits to home-assistant.github.io") +- [ChristianKuehnel (@ChristianKuehnel)](https://github.com/ChristianKuehnel "19 total commits to the home-assistant organization, 10 commits to home-assistant, 9 commits to home-assistant.github.io") - [Christoffer Kylvåg (@christoe)](https://github.com/christoe "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Christoph Wagner (@Christoph-Wagner)](https://github.com/Christoph-Wagner "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Christopher Viel (@Chris-V)](https://github.com/Chris-V "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io") - [chrysn (@chrysn)](https://github.com/chrysn "65 total commits to the home-assistant organization, 65 commits to libcoap") - [chz^3 (@chzchzchz)](https://github.com/chzchzchz "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [Ciquattro (@CiquattroFPV)](https://github.com/CiquattroFPV "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [clach04 (@clach04)](https://github.com/clach04 "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant") +- [clach04 (@clach04)](https://github.com/clach04 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Claus F. Strasburger (@cfstras)](https://github.com/cfstras "1 total commits to the home-assistant organization, 1 commit to pi-gen") -- [cogneato (@cogneato)](https://github.com/cogneato "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") +- [cogneato (@cogneato)](https://github.com/cogneato "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Colin Dunn (@colindunn)](https://github.com/colindunn "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Colin O'Dell (@colinodell)](https://github.com/colinodell "24 total commits to the home-assistant organization, 13 commits to home-assistant, 11 commits to home-assistant.github.io") - [Colin Teubner (@netopiax)](https://github.com/netopiax "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Conrad Juhl Andersen (@cnrd)](https://github.com/cnrd "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Conrad Juhl Andersen (@cnrd)](https://github.com/cnrd "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io") - [Constantine Grantcharov (@conz27)](https://github.com/conz27 "1 total commits to the home-assistant organization, 1 commit to libcoap") - [Constantine Poltyrev (@shprota)](https://github.com/shprota "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [Corban Mailloux (@corbanmailloux)](https://github.com/corbanmailloux "18 total commits to the home-assistant organization, 18 commits to home-assistant.github.io") - [Corey Pauley (@devspacenine)](https://github.com/devspacenine "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant") -- [corneyl (@corneyl)](https://github.com/corneyl "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Craig J. Ward (@wardcraigj)](https://github.com/wardcraigj "23 total commits to the home-assistant organization, 17 commits to home-assistant, 6 commits to home-assistant.github.io") +- [covrig (@covrig)](https://github.com/covrig "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") +- [Craig J. Ward (@wardcraigj)](https://github.com/wardcraigj "25 total commits to the home-assistant organization, 18 commits to home-assistant, 7 commits to home-assistant.github.io") - [CTLS (@CTLS)](https://github.com/CTLS "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [CV (@dagobert)](https://github.com/dagobert "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [cxlwill (@cxlwill)](https://github.com/cxlwill "2 total commits to the home-assistant organization, 2 commits to home-assistant-polymer") - [Dale Higgs (@dale3h)](https://github.com/dale3h "33 total commits to the home-assistant organization, 21 commits to home-assistant.github.io, 10 commits to home-assistant, 1 commit to hassbot, 1 commit to homebridge-homeassistant") - [Dan (@danieljkemp)](https://github.com/danieljkemp "23 total commits to the home-assistant organization, 16 commits to home-assistant, 7 commits to home-assistant.github.io") - [Dan Chen (@djchen)](https://github.com/djchen "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "14 total commits to the home-assistant organization, 12 commits to home-assistant, 2 commits to home-assistant.github.io") +- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "17 total commits to the home-assistant organization, 14 commits to home-assistant, 3 commits to home-assistant.github.io") - [Dan Faulknor (@danielfaulknor)](https://github.com/danielfaulknor "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Dan Nixon (@DanNixon)](https://github.com/DanNixon "17 total commits to the home-assistant organization, 12 commits to home-assistant, 5 commits to home-assistant.github.io") +- [Dan Nixon (@DanNixon)](https://github.com/DanNixon "19 total commits to the home-assistant organization, 14 commits to home-assistant, 5 commits to home-assistant.github.io") - [Dan Ports (@drkp)](https://github.com/drkp "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Dan Sarginson (@dansarginson)](https://github.com/dansarginson "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Dan Smith (@kk7ds)](https://github.com/kk7ds "84 total commits to the home-assistant organization, 68 commits to home-assistant, 14 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") @@ -222,8 +220,8 @@ This page contains a list of people who have contributed in one way or another t - [Dani (@danichispa)](https://github.com/danichispa "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io") - [Daniel (@delneet)](https://github.com/delneet "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Daniel Escoz (@Darkhogg)](https://github.com/Darkhogg "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "367 total commits to the home-assistant organization, 245 commits to home-assistant, 119 commits to home-assistant.github.io, 3 commits to home-assistant-polymer") -- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "77 total commits to the home-assistant organization, 38 commits to home-assistant.github.io, 35 commits to home-assistant, 4 commits to hassio-addons") +- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "374 total commits to the home-assistant organization, 252 commits to home-assistant, 119 commits to home-assistant.github.io, 3 commits to home-assistant-polymer") +- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "79 total commits to the home-assistant organization, 38 commits to home-assistant.github.io, 36 commits to home-assistant, 5 commits to hassio-addons") - [Daniel Peukert (@dpeukert)](https://github.com/dpeukert "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") - [Daniel Schaal (@schaal)](https://github.com/schaal "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Daniel Stone (@daniel-stoneuk)](https://github.com/daniel-stoneuk "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") @@ -239,9 +237,10 @@ This page contains a list of people who have contributed in one way or another t - [Dave J (@kxtcd950)](https://github.com/kxtcd950 "3 total commits to the home-assistant organization, 3 commits to hassbian-scripts") - [DaveSergeant (@dethpickle)](https://github.com/dethpickle "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [David (@fanaticDavid)](https://github.com/fanaticDavid "13 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 2 commits to home-assistant, 1 commit to home-assistant-polymer") +- [David (Drew) Jackson (@David-Jackson)](https://github.com/David-Jackson "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [David De Sloovere (@DavidDeSloovere)](https://github.com/DavidDeSloovere "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") +- [David Fiel (@dfiel)](https://github.com/dfiel "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [David Grant (@davegravy)](https://github.com/davegravy "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant") -- [David Jackson (@David-Jackson)](https://github.com/David-Jackson "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [David McNett (@nugget)](https://github.com/nugget "10 total commits to the home-assistant organization, 5 commits to home-assistant, 5 commits to home-assistant.github.io") - [David Ohayon (@ohayon)](https://github.com/ohayon "3 total commits to the home-assistant organization, 3 commits to issue-bot") - [David Straub (@DavidMStraub)](https://github.com/DavidMStraub "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io") @@ -259,16 +258,16 @@ This page contains a list of people who have contributed in one way or another t - [Dennis Sutch (@sutch)](https://github.com/sutch "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Derek (@itchaboy)](https://github.com/itchaboy "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Derek Brooks (@broox)](https://github.com/broox "39 total commits to the home-assistant organization, 30 commits to home-assistant, 9 commits to home-assistant.github.io") -- [dersger (@dersger)](https://github.com/dersger "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant-polymer") +- [dersger (@dersger)](https://github.com/dersger "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [devdelay (@devdelay)](https://github.com/devdelay "16 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 5 commits to home-assistant, 4 commits to homebridge-homeassistant") - [Devon Peet (@dpeet)](https://github.com/dpeet "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Diogo Gomes (@dgomes)](https://github.com/dgomes "10 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant.github.io") - [DoloresHA (@DoloresHA)](https://github.com/DoloresHA "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Domantas (@Dohxis)](https://github.com/Dohxis "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Dougal Matthews (@d0ugal)](https://github.com/d0ugal "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io") -- [dramamoose (@dramamoose)](https://github.com/dramamoose "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant") +- [dramamoose (@dramamoose)](https://github.com/dramamoose "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [DrewSK (@dzsquared)](https://github.com/dzsquared "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io") -- [DubhAd (@DubhAd)](https://github.com/DubhAd "107 total commits to the home-assistant organization, 107 commits to home-assistant.github.io") +- [DubhAd (@DubhAd)](https://github.com/DubhAd "122 total commits to the home-assistant organization, 122 commits to home-assistant.github.io") - [Duoxilian (@Duoxilian)](https://github.com/Duoxilian "11 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 5 commits to home-assistant") - [ebpetway (@ebpetway)](https://github.com/ebpetway "55 total commits to the home-assistant organization, 55 commits to warrant") - [Edwin Smulders (@Dutchy-)](https://github.com/Dutchy- "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io") @@ -278,7 +277,6 @@ This page contains a list of people who have contributed in one way or another t - [Eleftherios Chamakiotis (@lexam79)](https://github.com/lexam79 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Ellis Percival (@flyte)](https://github.com/flyte "31 total commits to the home-assistant organization, 25 commits to home-assistant, 6 commits to home-assistant.github.io") - [Emil Horpen Hetty (@emilhetty)](https://github.com/emilhetty "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [emlt (@emlt)](https://github.com/emlt "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [endor-force (@endor-force)](https://github.com/endor-force "9 total commits to the home-assistant organization, 4 commits to hassio-addons, 4 commits to home-assistant.github.io, 1 commit to hassio-build") - [engrbm87 (@engrbm87)](https://github.com/engrbm87 "3 total commits to the home-assistant organization, 3 commits to appdaemon") - [Eric Hagan (@ehagan)](https://github.com/ehagan "4 total commits to the home-assistant organization, 3 commits to home-assistant, 1 commit to home-assistant-polymer") @@ -286,12 +284,13 @@ This page contains a list of people who have contributed in one way or another t - [Eric Rolf (@xrolfex)](https://github.com/xrolfex "13 total commits to the home-assistant organization, 13 commits to home-assistant") - [Eric Thompson (@er0ck)](https://github.com/er0ck "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Erik Eriksson (@molobrakos)](https://github.com/molobrakos "111 total commits to the home-assistant organization, 97 commits to home-assistant, 11 commits to home-assistant.github.io, 3 commits to netdisco") -- [Erik-jan Riemers (@riemers)](https://github.com/riemers "13 total commits to the home-assistant organization, 13 commits to home-assistant.github.io") +- [Erik-jan Riemers (@riemers)](https://github.com/riemers "14 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 1 commit to hassbian-scripts") - [ettisan (@ettisan)](https://github.com/ettisan "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Eugenio Panadero (@azogue)](https://github.com/azogue "76 total commits to the home-assistant organization, 45 commits to home-assistant, 25 commits to home-assistant.github.io, 3 commits to homebridge-homeassistant, 3 commits to home-assistant-polymer") - [Ezra Bowden (@bn0)](https://github.com/bn0 "2 total commits to the home-assistant organization, 2 commits to warrant") -- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4452 total commits to the home-assistant organization, 2870 commits to home-assistant.github.io, 1483 commits to home-assistant, 32 commits to home-assistant-assets, 30 commits to home-assistant-notebooks, 11 commits to hassio-build, 10 commits to home-assistant-polymer, 8 commits to netdisco, 5 commits to hassio-addons, 2 commits to hassio, 1 commit to home-assistant-js-websocket") +- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4510 total commits to the home-assistant organization, 2903 commits to home-assistant.github.io, 1507 commits to home-assistant, 32 commits to home-assistant-assets, 30 commits to home-assistant-notebooks, 11 commits to hassio-build, 11 commits to home-assistant-polymer, 8 commits to netdisco, 5 commits to hassio-addons, 2 commits to hassio, 1 commit to home-assistant-js-websocket") - [Fabian Heredia Montiel (@fabianhjr)](https://github.com/fabianhjr "4 total commits to the home-assistant organization, 4 commits to home-assistant") +- [Fabien Piuzzi (@reefab)](https://github.com/reefab "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Fabrizio Furnari (@fabfurnari)](https://github.com/fabfurnari "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant") - [fakezeta (@fakezeta)](https://github.com/fakezeta "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Fares Rihani (@anchepiece)](https://github.com/anchepiece "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") @@ -304,14 +303,12 @@ This page contains a list of people who have contributed in one way or another t - [florianj1 (@florianj1)](https://github.com/florianj1 "1 total commits to the home-assistant organization, 1 commit to hassio") - [florincosta (@florincosta)](https://github.com/florincosta "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io") - [Fonta (@f0nt4)](https://github.com/f0nt4 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") -- [Franck Nijhof (@frenck)](https://github.com/frenck "17 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 2 commits to hassio, 2 commits to home-assistant-polymer") +- [Franck Nijhof (@frenck)](https://github.com/frenck "28 total commits to the home-assistant organization, 19 commits to home-assistant.github.io, 5 commits to hassio, 2 commits to home-assistant-polymer, 1 commit to appdaemon, 1 commit to hassio-cli") - [Frank (@syphernl)](https://github.com/syphernl "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [Frantz (@rofrantz)](https://github.com/rofrantz "7 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to netdisco, 2 commits to home-assistant.github.io") +- [Frantz (@rofrantz)](https://github.com/rofrantz "14 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io, 3 commits to netdisco") - [Frederic Hemberger (@fhemberger)](https://github.com/fhemberger "93 total commits to the home-assistant organization, 93 commits to home-assistant.github.io") - [Fredrik Fjeld (@fredrikfjeld)](https://github.com/fredrikfjeld "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "176 total commits to the home-assistant organization, 74 commits to hassbian-scripts, 70 commits to home-assistant.github.io, 27 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer") -- [freol35241 (@freol35241)](https://github.com/freol35241 "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [froz (@froz)](https://github.com/froz "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "177 total commits to the home-assistant organization, 75 commits to hassbian-scripts, 70 commits to home-assistant.github.io, 27 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer") - [fuga2136 (@fuga2136)](https://github.com/fuga2136 "13 total commits to the home-assistant organization, 13 commits to home-assistant.github.io") - [Gabor SZOLLOSI (@szogi)](https://github.com/szogi "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to appdaemon") - [GadgetReactor (@GadgetReactor)](https://github.com/GadgetReactor "2 total commits to the home-assistant organization, 2 commits to home-assistant") @@ -321,13 +318,14 @@ This page contains a list of people who have contributed in one way or another t - [Georgi Kirichkov (@kirichkov)](https://github.com/kirichkov "17 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to appdaemon") - [Georgi Yanev (@jumpalottahigh)](https://github.com/jumpalottahigh "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") - [Georgii Staroselskii (@staroselskii)](https://github.com/staroselskii "1 total commits to the home-assistant organization, 1 commit to pi-gen") -- [gerard33 (@gerard33)](https://github.com/gerard33 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") +- [Gerard (@gerard33)](https://github.com/gerard33 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Gergely Imreh (@imrehg)](https://github.com/imrehg "16 total commits to the home-assistant organization, 11 commits to home-assistant, 5 commits to home-assistant.github.io") - [Gianluca Barbaro (@MrMep)](https://github.com/MrMep "24 total commits to the home-assistant organization, 16 commits to home-assistant, 8 commits to home-assistant.github.io") - [Gianpaolo Macario (@gmacario)](https://github.com/gmacario "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Giel Janssens (@gieljnssns)](https://github.com/gieljnssns "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io") - [githubbuh (@githubbuh)](https://github.com/githubbuh "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [gitmopp (@gitmopp)](https://github.com/gitmopp "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") +- [Giuseppe (@glpatcern)](https://github.com/glpatcern "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [GMFalka (@GMFalka)](https://github.com/GMFalka "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Gopal Kildoliya (@gopalkildoliya)](https://github.com/gopalkildoliya "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io") - [Graeme Smith (@Instagraeme)](https://github.com/Instagraeme "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") @@ -339,10 +337,10 @@ This page contains a list of people who have contributed in one way or another t - [Greg Stengel (@theCMack)](https://github.com/theCMack "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Greg Stevenson (@gstevenson)](https://github.com/gstevenson "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Greg. A. (@gautric)](https://github.com/gautric "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [groth-its (@groth-its)](https://github.com/groth-its "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [GTH (@gunnarhelgason)](https://github.com/gunnarhelgason "2 total commits to the home-assistant organization, 2 commits to appdaemon") - [Guillaume Rischard (@grischard)](https://github.com/grischard "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Gustav Ahlberg (@Gyran)](https://github.com/Gyran "20 total commits to the home-assistant organization, 20 commits to home-assistant") +- [Guyanthalas (@Guyanthalas)](https://github.com/Guyanthalas "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [gwendalg (@gwendalg)](https://github.com/gwendalg "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Hamid (@hamid-elaosta)](https://github.com/hamid-elaosta "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Hao Hu (@howiehu)](https://github.com/howiehu "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") @@ -353,6 +351,7 @@ This page contains a list of people who have contributed in one way or another t - [hawk259 (@hawk259)](https://github.com/hawk259 "10 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") - [Heath Paddock (@heathbar)](https://github.com/heathbar "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Heiko Rothe (@mKeRix)](https://github.com/mKeRix "20 total commits to the home-assistant organization, 15 commits to home-assistant, 5 commits to home-assistant.github.io") +- [Heiko Thiery (@hthiery)](https://github.com/hthiery "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io") - [Hellowlol (@Hellowlol)](https://github.com/Hellowlol "4 total commits to the home-assistant organization, 3 commits to netdisco, 1 commit to appdaemon") - [Helmut Januschka (@hjanuschka)](https://github.com/hjanuschka "3 total commits to the home-assistant organization, 3 commits to issue-bot") - [Henning Dickten (@hensing)](https://github.com/hensing "2 total commits to the home-assistant organization, 2 commits to home-assistant") @@ -372,18 +371,20 @@ This page contains a list of people who have contributed in one way or another t - [ianj001 (@ianj001)](https://github.com/ianj001 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") - [icovada (@icovada)](https://github.com/icovada "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io") - [Igor Shults (@ishults)](https://github.com/ishults "12 total commits to the home-assistant organization, 6 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") -- [Ioan Loosley (@ioangogo)](https://github.com/ioangogo "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") +- [Ioan Loosley (@ioangogo)](https://github.com/ioangogo "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io") - [IoTmessenger (@IoTmessenger)](https://github.com/IoTmessenger "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Issac Kelly (@issackelly)](https://github.com/issackelly "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [J-CMartin (@J-CMartin)](https://github.com/J-CMartin "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [J. B. Rainsberger (@jbrains)](https://github.com/jbrains "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [jack (@jackmakesthings)](https://github.com/jackmakesthings "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Jack Chapple (@jchapple)](https://github.com/jchapple "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Jack Fan (@JackWindows)](https://github.com/JackWindows "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Jack Minardi (@jminardi)](https://github.com/jminardi "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Jacob Mansfield (@cyberjacob)](https://github.com/cyberjacob "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Jacob Minnis (@jminn)](https://github.com/jminn "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Jacob Siverskog (@jsiverskog)](https://github.com/jsiverskog "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [Jacob Tomlinson (@jacobtomlinson)](https://github.com/jacobtomlinson "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant") +- [Jaimyn Mayer (@jabelone)](https://github.com/jabelone "1 total commits to the home-assistant organization, 1 commit to hassbian-scripts") - [Jake McCrary (@jakemcc)](https://github.com/jakemcc "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Jakub Bittner (@rexcze)](https://github.com/rexcze "2 total commits to the home-assistant organization, 2 commits to home-assistant-polymer") - [James Cole (@jamespcole)](https://github.com/jamespcole "94 total commits to the home-assistant organization, 93 commits to home-assistant, 1 commit to home-assistant-js") @@ -410,6 +411,7 @@ This page contains a list of people who have contributed in one way or another t - [Jeff Wilson (@jawilson)](https://github.com/jawilson "24 total commits to the home-assistant organization, 19 commits to home-assistant, 5 commits to home-assistant.github.io") - [Jeffrey Lin (@linjef)](https://github.com/linjef "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Jens (@jhoepken)](https://github.com/jhoepken "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") +- [Jens Østergaard Nielsen (@dingusdk)](https://github.com/dingusdk "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Jeremiah Wuenschel (@jer)](https://github.com/jer "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Jeremy (@Wutname1)](https://github.com/Wutname1 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Jeremy Williams (@jwillaz)](https://github.com/jwillaz "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") @@ -417,37 +419,34 @@ This page contains a list of people who have contributed in one way or another t - [Jeroen ter Heerdt (@jeroenterheerdt)](https://github.com/jeroenterheerdt "29 total commits to the home-assistant organization, 16 commits to home-assistant, 13 commits to home-assistant.github.io") - [Jerold Albertson (@jeroldalbertson-wf)](https://github.com/jeroldalbertson-wf "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Jerry Workman (@JerryWorkman)](https://github.com/JerryWorkman "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [Jesse Hills (@jesserockz)](https://github.com/jesserockz "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") +- [Jesse Hills (@jesserockz)](https://github.com/jesserockz "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io") - [Jesse Newland (@jnewland)](https://github.com/jnewland "14 total commits to the home-assistant organization, 11 commits to home-assistant, 3 commits to hubot-home-assistant") - [JesseWebDotCom (@JesseWebDotCom)](https://github.com/JesseWebDotCom "16 total commits to the home-assistant organization, 8 commits to home-assistant, 8 commits to home-assistant.github.io") - [jgrieger1 (@jgrieger1)](https://github.com/jgrieger1 "1 total commits to the home-assistant organization, 1 commit to appdaemon") -- [jgriff2 (@jgriff2)](https://github.com/jgriff2 "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Jim Rollenhagen (@jimrollenhagen)](https://github.com/jimrollenhagen "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [jimbob1001 (@jimbob1001)](https://github.com/jimbob1001 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Joakim Nohlgård (@gebart)](https://github.com/gebart "2 total commits to the home-assistant organization, 2 commits to libcoap") -- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "28 total commits to the home-assistant organization, 15 commits to hassbian-scripts, 13 commits to home-assistant.github.io") +- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "38 total commits to the home-assistant organization, 25 commits to hassbian-scripts, 13 commits to home-assistant.github.io") - [Job (@jmvermeulen)](https://github.com/jmvermeulen "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [jodur (@jodur)](https://github.com/jodur "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Joe Lee (@xnoodle)](https://github.com/xnoodle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Joe Lu (@snjoetw)](https://github.com/snjoetw "12 total commits to the home-assistant organization, 9 commits to home-assistant, 3 commits to home-assistant.github.io") -- [Joe McMonagle (@joemcmonagle)](https://github.com/joemcmonagle "12 total commits to the home-assistant organization, 12 commits to home-assistant.github.io") +- [Joe Lu (@snjoetw)](https://github.com/snjoetw "13 total commits to the home-assistant organization, 10 commits to home-assistant, 3 commits to home-assistant.github.io") +- [Joe McMonagle (@joemcmonagle)](https://github.com/joemcmonagle "13 total commits to the home-assistant organization, 13 commits to home-assistant.github.io") - [joe248 (@joe248)](https://github.com/joe248 "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Joeboyc2 (@Joeboyc2)](https://github.com/Joeboyc2 "15 total commits to the home-assistant organization, 15 commits to home-assistant.github.io") - [Johan Bloemberg (@aequitas)](https://github.com/aequitas "43 total commits to the home-assistant organization, 35 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco") - [Johan Haals (@jhaals)](https://github.com/jhaals "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to appdaemon") -- [Johan Klintberg (@moogblob)](https://github.com/moogblob "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Johan van der Kuijl (@Rubyan)](https://github.com/Rubyan "4 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 1 commit to appdaemon") - [Johann Kellerman (@kellerza)](https://github.com/kellerza "144 total commits to the home-assistant organization, 114 commits to home-assistant, 30 commits to home-assistant.github.io") - [Johannes K. (@roadrash2108)](https://github.com/roadrash2108 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [John (@J-C-B)](https://github.com/J-C-B "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [John Arild Berentsen (@turbokongen)](https://github.com/turbokongen "200 total commits to the home-assistant organization, 148 commits to home-assistant, 37 commits to home-assistant.github.io, 15 commits to home-assistant-polymer") -- [John Coggeshall (@coogle)](https://github.com/coogle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [John Lindley (@jwl17330536)](https://github.com/jwl17330536 "1 total commits to the home-assistant organization, 1 commit to appdaemon") - [John McLaughlin (@loghound)](https://github.com/loghound "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [John Mihalic (@mezz64)](https://github.com/mezz64 "45 total commits to the home-assistant organization, 31 commits to home-assistant, 12 commits to home-assistant.github.io, 1 commit to hadashboard, 1 commit to home-assistant-polymer") -- [Johnny Chadda (@joch)](https://github.com/joch "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") +- [Johnny Chadda (@joch)](https://github.com/joch "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Jon (@JonMurphy)](https://github.com/JonMurphy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") -- [Jon Caruana (@joncar)](https://github.com/joncar "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io") +- [Jon Caruana (@joncar)](https://github.com/joncar "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Jon Griffith (@arretx)](https://github.com/arretx "11 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 1 commit to appdaemon") - [Jon Maddox (@maddox)](https://github.com/maddox "102 total commits to the home-assistant organization, 78 commits to home-assistant, 16 commits to homebridge-homeassistant, 8 commits to home-assistant.github.io") - [Jonas Pedersen (@JonasPed)](https://github.com/JonasPed "1 total commits to the home-assistant organization, 1 commit to appdaemon") @@ -472,22 +471,18 @@ This page contains a list of people who have contributed in one way or another t - [jumpkick (@jumpkick)](https://github.com/jumpkick "15 total commits to the home-assistant organization, 12 commits to home-assistant, 3 commits to home-assistant.github.io") - [Justin Dray (@justin8)](https://github.com/justin8 "9 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 2 commits to home-assistant") - [Justin Hayes (@GussyH)](https://github.com/GussyH "7 total commits to the home-assistant organization, 7 commits to hadashboard") -- [Justin Weberg (@justweb1)](https://github.com/justweb1 "28 total commits to the home-assistant organization, 13 commits to home-assistant-polymer, 7 commits to hassbot, 4 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to home-assistant-js, 1 commit to hassio") +- [Justin Weberg (@justweb1)](https://github.com/justweb1 "26 total commits to the home-assistant organization, 13 commits to home-assistant-polymer, 7 commits to hassbot, 4 commits to home-assistant, 1 commit to home-assistant-js, 1 commit to hassio") - [Justyn Shull (@justyns)](https://github.com/justyns "5 total commits to the home-assistant organization, 5 commits to home-assistant") -- [Jürgen W (@jurgenweber)](https://github.com/jurgenweber "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Kai (@luxus)](https://github.com/luxus "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Kane610 (@Kane610)](https://github.com/Kane610 "18 total commits to the home-assistant organization, 8 commits to home-assistant, 8 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-polymer") +- [Kane610 (@Kane610)](https://github.com/Kane610 "22 total commits to the home-assistant organization, 11 commits to home-assistant, 9 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-polymer") - [Karen Goode (@kfgoode)](https://github.com/kfgoode "4 total commits to the home-assistant organization, 4 commits to home-assistant") -- [karlkar (@karlkar)](https://github.com/karlkar "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [karlkar (@karlkar)](https://github.com/karlkar "5 total commits to the home-assistant organization, 5 commits to home-assistant") - [Keaton Taylor (@keatontaylor)](https://github.com/keatontaylor "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io") -- [Keith (@seedzero)](https://github.com/seedzero "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Keith Lamprecht (@Nixon506E)](https://github.com/Nixon506E "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Ken Bannister (@kb2ma)](https://github.com/kb2ma "1 total commits to the home-assistant organization, 1 commit to libcoap") - [Ken Davidson (@kwdavidson)](https://github.com/kwdavidson "13 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 2 commits to appdaemon") +- [kennedyshead (@kennedyshead)](https://github.com/kennedyshead "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Kenny Millington (@kmdm)](https://github.com/kmdm "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Kevin (@Mister-Espria)](https://github.com/Mister-Espria "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Kevin Christensen (@nivekmai)](https://github.com/nivekmai "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") -- [Kevin Delaney (@kevindelaney)](https://github.com/kevindelaney "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io") - [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "19 total commits to the home-assistant organization, 11 commits to home-assistant, 8 commits to home-assistant.github.io") - [Kevin Gisi (@gisikw)](https://github.com/gisikw "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Kevin Gottsman (@gottsman)](https://github.com/gottsman "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") @@ -520,8 +515,8 @@ This page contains a list of people who have contributed in one way or another t - [Ludovic (@ldvc)](https://github.com/ldvc "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Ludovico de Nittis (@RyuzakiKK)](https://github.com/RyuzakiKK "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Lukas (@lukas-hetzenecker)](https://github.com/lukas-hetzenecker "14 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io") -- [Lukas Barth (@tinloaf)](https://github.com/tinloaf "27 total commits to the home-assistant organization, 15 commits to home-assistant, 10 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") -- [Lukas Ecklmayr (@outrun0506)](https://github.com/outrun0506 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") +- [Lukas Barth (@tinloaf)](https://github.com/tinloaf "32 total commits to the home-assistant organization, 19 commits to home-assistant, 11 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") +- [Lukas Ecklmayr (@outrun0506)](https://github.com/outrun0506 "6 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") - [Lukas Porubcan (@Luc3as)](https://github.com/Luc3as "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Luke Armstrong (@lukearmstrong)](https://github.com/lukearmstrong "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [LvivEchoes (@LvivEchoes)](https://github.com/LvivEchoes "8 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") @@ -532,7 +527,7 @@ This page contains a list of people who have contributed in one way or another t - [Magnus Ihse Bursie (@magicus)](https://github.com/magicus "16 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to netdisco, 3 commits to home-assistant.github.io") - [Magnus Lyckå (@magnus-lycka)](https://github.com/magnus-lycka "1 total commits to the home-assistant organization, 1 commit to netdisco") - [MagnusKnutas (@MagnusKnutas)](https://github.com/MagnusKnutas "29 total commits to the home-assistant organization, 29 commits to home-assistant") -- [Mahasri Kalavala (@skalavala)](https://github.com/skalavala "10 total commits to the home-assistant organization, 10 commits to home-assistant.github.io") +- [Mahasri Kalavala (@skalavala)](https://github.com/skalavala "14 total commits to the home-assistant organization, 14 commits to home-assistant.github.io") - [Maikel Wever (@maikelwever)](https://github.com/maikelwever "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Marc Egli (@frog32)](https://github.com/frog32 "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Marc Forth (@mf-social)](https://github.com/mf-social "13 total commits to the home-assistant organization, 12 commits to home-assistant.github.io, 1 commit to fabric-home-assistant") @@ -541,12 +536,14 @@ This page contains a list of people who have contributed in one way or another t - [Marcel030nl (@Marcel030nl)](https://github.com/Marcel030nl "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "140 total commits to the home-assistant organization, 77 commits to home-assistant, 61 commits to home-assistant.github.io, 1 commit to home-assistant-assets, 1 commit to home-assistant-polymer") - [Marcin Jaworski (@yawor)](https://github.com/yawor "12 total commits to the home-assistant organization, 12 commits to appdaemon") +- [Marco (@marconett)](https://github.com/marconett "3 total commits to the home-assistant organization, 3 commits to appdaemon") - [Marcus Schmidt (@mar-schmidt)](https://github.com/mar-schmidt "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Marijn Giesen (@marijngiesen)](https://github.com/marijngiesen "5 total commits to the home-assistant organization, 5 commits to hadashboard") -- [Marius (@ciotlosm)](https://github.com/ciotlosm "6 total commits to the home-assistant organization, 4 commits to home-assistant-polymer, 2 commits to home-assistant") +- [Marius (@ciotlosm)](https://github.com/ciotlosm "8 total commits to the home-assistant organization, 5 commits to home-assistant-polymer, 3 commits to home-assistant") - [Mark Coombes (@marthoc)](https://github.com/marthoc "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Mark Grosen (@mgsb)](https://github.com/mgsb "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Mark Huson (@mehuman)](https://github.com/mehuman "11 total commits to the home-assistant organization, 11 commits to home-assistant.github.io") +- [markferry (@markferry)](https://github.com/markferry "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Markus (@iMarkus)](https://github.com/iMarkus "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to hassio") - [Markus Becker (@markushx)](https://github.com/markushx "6 total commits to the home-assistant organization, 6 commits to libcoap") - [Markus Peter (@bimbar)](https://github.com/bimbar "3 total commits to the home-assistant organization, 3 commits to home-assistant") @@ -555,6 +552,7 @@ This page contains a list of people who have contributed in one way or another t - [Martin Donlon (@wickerwaka)](https://github.com/wickerwaka "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Martin Eberhardt (@DarkFox)](https://github.com/DarkFox "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Martin Hjelmare (@MartinHjelmare)](https://github.com/MartinHjelmare "143 total commits to the home-assistant organization, 114 commits to home-assistant, 29 commits to home-assistant.github.io") +- [Martin Rowan (@shortbloke)](https://github.com/shortbloke "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Martin Vacula (@MatoKafkac)](https://github.com/MatoKafkac "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Martin Weinelt (@mweinelt)](https://github.com/mweinelt "17 total commits to the home-assistant organization, 9 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") - [Martokk (@martokk)](https://github.com/martokk "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") @@ -569,6 +567,7 @@ This page contains a list of people who have contributed in one way or another t - [Matthew Garrett (@mjg59)](https://github.com/mjg59 "10 total commits to the home-assistant organization, 7 commits to home-assistant, 3 commits to home-assistant.github.io") - [Matthew Schick (@mattsch)](https://github.com/mattsch "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Matthew Treinish (@mtreinish)](https://github.com/mtreinish "20 total commits to the home-assistant organization, 13 commits to home-assistant, 7 commits to home-assistant.github.io") +- [Matthias Dötsch (@brainexe)](https://github.com/brainexe "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [mattie47 (@mattie47)](https://github.com/mattie47 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [mauriciobonani (@mauriciobonani)](https://github.com/mauriciobonani "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") - [Max Rumpf (@Maxr1998)](https://github.com/Maxr1998 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") @@ -588,10 +587,9 @@ This page contains a list of people who have contributed in one way or another t - [Michael Prokop (@mika)](https://github.com/mika "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Michael Requeny (@requenym)](https://github.com/requenym "14 total commits to the home-assistant organization, 14 commits to home-assistant.github.io") - [Michael Shim (@shimeez)](https://github.com/shimeez "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant") -- [Michaël Arnauts (@michaelarnauts)](https://github.com/michaelarnauts "61 total commits to the home-assistant organization, 31 commits to home-assistant, 26 commits to home-assistant.github.io, 3 commits to home-assistant-polymer, 1 commit to netdisco") +- [Michaël Arnauts (@michaelarnauts)](https://github.com/michaelarnauts "62 total commits to the home-assistant organization, 32 commits to home-assistant, 26 commits to home-assistant.github.io, 3 commits to home-assistant-polymer, 1 commit to netdisco") - [Michel Settembrino (@Michel-Settembrino)](https://github.com/Michel-Settembrino "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [micw (@micw)](https://github.com/micw "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io") -- [Mikael Bergemalm (@bergemalm)](https://github.com/bergemalm "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Mike Christianson (@MikeChristianson)](https://github.com/MikeChristianson "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Mike Megally (@cmsimike)](https://github.com/cmsimike "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Mike Nestor (@mnestor)](https://github.com/mnestor "6 total commits to the home-assistant organization, 5 commits to home-assistant, 1 commit to home-assistant-polymer") @@ -610,25 +608,28 @@ This page contains a list of people who have contributed in one way or another t - [moose51789 (@moose51789)](https://github.com/moose51789 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [moskovskiy82 (@moskovskiy82)](https://github.com/moskovskiy82 "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") - [motir (@motir)](https://github.com/motir "1 total commits to the home-assistant organization, 1 commit to appdaemon") +- [mukundv (@mukundv)](https://github.com/mukundv "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Mārtiņš Grunskis (@grunskis)](https://github.com/grunskis "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Nate (@BillyNate)](https://github.com/BillyNate "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Nathan Flynn (@eperdeme)](https://github.com/eperdeme "1 total commits to the home-assistant organization, 1 commit to hassio-addons") -- [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "19 total commits to the home-assistant organization, 9 commits to home-assistant, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant, 1 commit to home-assistant-polymer, 1 commit to appdaemon") +- [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "19 total commits to the home-assistant organization, 9 commits to home-assistant, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant, 1 commit to appdaemon, 1 commit to home-assistant-polymer") - [Neil Lathwood (@laf)](https://github.com/laf "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant") - [Nelis Willers (@NelisW)](https://github.com/NelisW "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant") - [NeLLyMerC (@NeLLyMerC)](https://github.com/NeLLyMerC "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [neonbunny (@neonbunny)](https://github.com/neonbunny "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") +- [Nicholas Amadori (@namadori)](https://github.com/namadori "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Nicholas Griffin (@nicholasgriffintn)](https://github.com/nicholasgriffintn "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") - [Nicholas Sielicki (@sielicki)](https://github.com/sielicki "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Nick (@quadportnick)](https://github.com/quadportnick "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Nick Touran (@partofthething)](https://github.com/partofthething "38 total commits to the home-assistant organization, 25 commits to home-assistant, 13 commits to home-assistant.github.io") - [Nick Waring (@nickwaring)](https://github.com/nickwaring "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Nicko van Someren (@nickovs)](https://github.com/nickovs "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Nicolas Graziano (@ngraziano)](https://github.com/ngraziano "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Nicolas Martignoni (@martignoni)](https://github.com/martignoni "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [Nigel Rook (@NigelRook)](https://github.com/NigelRook "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Niklas (@niklaswa)](https://github.com/niklaswa "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Nikolas Beutler (@biacz)](https://github.com/biacz "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Nolan Gilley (@nkgilley)](https://github.com/nkgilley "119 total commits to the home-assistant organization, 93 commits to home-assistant, 26 commits to home-assistant.github.io") +- [Nolan Gilley (@nkgilley)](https://github.com/nkgilley "122 total commits to the home-assistant organization, 95 commits to home-assistant, 27 commits to home-assistant.github.io") - [NotoriousBDG (@notoriousbdg)](https://github.com/notoriousbdg "3 total commits to the home-assistant organization, 3 commits to hassio-addons") - [NovapaX (@NovapaX)](https://github.com/NovapaX "9 total commits to the home-assistant organization, 4 commits to home-assistant-polymer, 4 commits to home-assistant, 1 commit to home-assistant-assets") - [ntalekt (@ntalekt)](https://github.com/ntalekt "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") @@ -636,7 +637,7 @@ This page contains a list of people who have contributed in one way or another t - [obgm (@obgm)](https://github.com/obgm "480 total commits to the home-assistant organization, 480 commits to libcoap") - [OLD PROFILE! Go to /dennisreimann (@dbloete)](https://github.com/dbloete "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Ole-Kenneth (@olekenneth)](https://github.com/olekenneth "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant") -- [Oleksii Serdiuk (@leppa)](https://github.com/leppa "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [Oleksii Serdiuk (@leppa)](https://github.com/leppa "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Oliv3rDog (@Oliv3rDog)](https://github.com/Oliv3rDog "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Oliver (@scarface-4711)](https://github.com/scarface-4711 "24 total commits to the home-assistant organization, 14 commits to home-assistant, 9 commits to home-assistant.github.io, 1 commit to netdisco") - [Oliver van Porten (@mcdeck)](https://github.com/mcdeck "10 total commits to the home-assistant organization, 10 commits to home-assistant") @@ -646,11 +647,13 @@ This page contains a list of people who have contributed in one way or another t - [Parker Moore (@parkr)](https://github.com/parkr "60 total commits to the home-assistant organization, 60 commits to home-assistant.github.io") - [pascal (@passie)](https://github.com/passie "4 total commits to the home-assistant organization, 3 commits to home-assistant, 1 commit to home-assistant-polymer") - [Pascal Bach (@bachp)](https://github.com/bachp "10 total commits to the home-assistant organization, 9 commits to home-assistant, 1 commit to netdisco") -- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "2335 total commits to the home-assistant organization, 917 commits to hassio, 446 commits to home-assistant, 323 commits to hassio-build, 315 commits to hassio-addons, 305 commits to home-assistant.github.io, 16 commits to hassio-addons-example, 10 commits to hassio-cli, 1 commit to netdisco, 1 commit to home-assistant-js-websocket, 1 commit to hassio-os") +- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "2393 total commits to the home-assistant organization, 939 commits to hassio, 451 commits to home-assistant, 343 commits to hassio-build, 324 commits to hassio-addons, 307 commits to home-assistant.github.io, 16 commits to hassio-addons-example, 10 commits to hassio-cli, 1 commit to home-assistant-js-websocket, 1 commit to hassio-os, 1 commit to netdisco") - [Patrick Aikens (@duckpuppy)](https://github.com/duckpuppy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Patrick Easters (@patrickeasters)](https://github.com/patrickeasters "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [Patrik (@ggravlingen)](https://github.com/ggravlingen "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io") +- [Paul Annekov (@PaulAnnekov)](https://github.com/PaulAnnekov "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Paul Hendry (@pshendry)](https://github.com/pshendry "1 total commits to the home-assistant organization, 1 commit to warrant") +- [Paul Nicholls (@pauln)](https://github.com/pauln "1 total commits to the home-assistant organization, 1 commit to netdisco") - [Paul Sokolovsky (@pfalcon)](https://github.com/pfalcon "6 total commits to the home-assistant organization, 3 commits to netdisco, 3 commits to home-assistant") - [Pavel Ponomarev (@awsum)](https://github.com/awsum "2 total commits to the home-assistant organization, 2 commits to home-assistant-polymer") - [PawelWMS (@PawelWMS)](https://github.com/PawelWMS "12 total commits to the home-assistant organization, 12 commits to libcoap") @@ -659,29 +662,34 @@ This page contains a list of people who have contributed in one way or another t - [Per Osbäck (@perosb)](https://github.com/perosb "12 total commits to the home-assistant organization, 12 commits to home-assistant") - [Per Sandström (@persandstrom)](https://github.com/persandstrom "124 total commits to the home-assistant organization, 98 commits to home-assistant, 14 commits to home-assistant.github.io, 12 commits to home-assistant-polymer") - [Pete Peterson (@petey)](https://github.com/petey "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") -- [PeteBa (@PeteBa)](https://github.com/PeteBa "6 total commits to the home-assistant organization, 5 commits to home-assistant, 1 commit to home-assistant-polymer") +- [PeteBa (@PeteBa)](https://github.com/PeteBa "7 total commits to the home-assistant organization, 5 commits to home-assistant, 2 commits to home-assistant-polymer") - [Peter Epley (@epleypa)](https://github.com/epleypa "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") - [Petr Vraník (@konikvranik)](https://github.com/konikvranik "11 total commits to the home-assistant organization, 6 commits to home-assistant, 5 commits to home-assistant.github.io") - [pezinek (@pezinek)](https://github.com/pezinek "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [Phil (@godloth)](https://github.com/godloth "10 total commits to the home-assistant organization, 10 commits to home-assistant.github.io") - [Phil Cole (@filcole)](https://github.com/filcole "8 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 3 commits to home-assistant") +- [Phil Frost (@bitglue)](https://github.com/bitglue "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Phil Haack (@Haacked)](https://github.com/Haacked "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Phil Hawthorne (@philhawthorne)](https://github.com/philhawthorne "24 total commits to the home-assistant organization, 18 commits to home-assistant.github.io, 6 commits to home-assistant") -- [Phil Kates (@philk)](https://github.com/philk "5 total commits to the home-assistant organization, 5 commits to home-assistant") +- [Phil Kates (@philk)](https://github.com/philk "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Philip Hofstetter (@pilif)](https://github.com/pilif "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io") +- [Philip Kleimeyer (@philklei)](https://github.com/philklei "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Philip Lundrigan (@philipbl)](https://github.com/philipbl "65 total commits to the home-assistant organization, 56 commits to home-assistant, 9 commits to home-assistant.github.io") -- [Philipp Schmitt (@pschmitt)](https://github.com/pschmitt "37 total commits to the home-assistant organization, 24 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to hassio-build, 1 commit to appdaemon") +- [Philipp Hellmich (@runningman84)](https://github.com/runningman84 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") +- [Philipp Schmitt (@pschmitt)](https://github.com/pschmitt "37 total commits to the home-assistant organization, 24 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to appdaemon, 1 commit to hassio-build") - [Phill Price (@phillprice)](https://github.com/phillprice "11 total commits to the home-assistant organization, 11 commits to home-assistant.github.io") - [PhracturedBlue (@PhracturedBlue)](https://github.com/PhracturedBlue "25 total commits to the home-assistant organization, 15 commits to home-assistant, 9 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") -- [Pierre Ståhl (@postlund)](https://github.com/postlund "45 total commits to the home-assistant organization, 30 commits to home-assistant, 9 commits to home-assistant.github.io, 4 commits to netdisco, 2 commits to home-assistant-polymer") +- [Pierre Ståhl (@postlund)](https://github.com/postlund "47 total commits to the home-assistant organization, 31 commits to home-assistant, 10 commits to home-assistant.github.io, 4 commits to netdisco, 2 commits to home-assistant-polymer") - [Piratonym (@Piratonym)](https://github.com/Piratonym "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [pkonnekermetametrics (@pkonnekermetametrics)](https://github.com/pkonnekermetametrics "5 total commits to the home-assistant organization, 5 commits to warrant") - [PuckStar (@PuckStar)](https://github.com/PuckStar "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") -- [R Huish (@Genestealer)](https://github.com/Genestealer "20 total commits to the home-assistant organization, 20 commits to home-assistant.github.io") +- [R Huish (@Genestealer)](https://github.com/Genestealer "22 total commits to the home-assistant organization, 22 commits to home-assistant.github.io") +- [Raiford (@raiford)](https://github.com/raiford "1 total commits to the home-assistant organization, 1 commit to hassio-addons") - [Rasmus (@rasmusbe)](https://github.com/rasmusbe "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [rbflurry (@rbflurry)](https://github.com/rbflurry "16 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 3 commits to home-assistant") - [Reed Riley (@reedriley)](https://github.com/reedriley "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Rendili (@Rendili)](https://github.com/Rendili "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Rendili (@Rendili)](https://github.com/Rendili "3 total commits to the home-assistant organization, 3 commits to home-assistant") +- [Rene Nulsch (@ReneNulschDE)](https://github.com/ReneNulschDE "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Rene Tode (@ReneTode)](https://github.com/ReneTode "38 total commits to the home-assistant organization, 38 commits to appdaemon") - [René Kliment (@renekliment)](https://github.com/renekliment "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Reza Moallemi (@moallemi)](https://github.com/moallemi "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") @@ -693,7 +701,7 @@ This page contains a list of people who have contributed in one way or another t - [rkabadi (@rkabadi)](https://github.com/rkabadi "17 total commits to the home-assistant organization, 17 commits to home-assistant") - [Rob Capellini (@capellini)](https://github.com/capellini "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Rob Slifka (@rslifka)](https://github.com/rslifka "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") -- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1315 total commits to the home-assistant organization, 646 commits to home-assistant-iOS, 259 commits to home-assistant, 248 commits to home-assistant.github.io, 91 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to hassbot, 3 commits to hadashboard, 3 commits to home-assistant-js-websocket, 3 commits to appdaemon, 3 commits to home-assistant-js, 3 commits to scenegen, 3 commits to organization, 2 commits to LabelBot, 2 commits to home-assistant-assets, 2 commits to fabric-home-assistant, 2 commits to home-assistant-notebooks, 2 commits to micropython-home-assistant, 2 commits to lambda-home-assistant-github") +- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1315 total commits to the home-assistant organization, 646 commits to home-assistant-iOS, 259 commits to home-assistant, 248 commits to home-assistant.github.io, 91 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to home-assistant-js, 3 commits to organization, 3 commits to hassbot, 3 commits to appdaemon, 3 commits to scenegen, 3 commits to home-assistant-js-websocket, 3 commits to hadashboard, 2 commits to LabelBot, 2 commits to fabric-home-assistant, 2 commits to micropython-home-assistant, 2 commits to home-assistant-notebooks, 2 commits to home-assistant-assets, 2 commits to lambda-home-assistant-github") - [Robby Grossman (@freerobby)](https://github.com/freerobby "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Robin (@robmarkcole)](https://github.com/robmarkcole "16 total commits to the home-assistant organization, 9 commits to home-assistant.github.io, 6 commits to home-assistant, 1 commit to home-assistant-assets") - [Robin Laurén (@llauren)](https://github.com/llauren "1 total commits to the home-assistant organization, 1 commit to appdaemon") @@ -706,14 +714,13 @@ This page contains a list of people who have contributed in one way or another t - [Ross Schulman (@rschulman)](https://github.com/rschulman "1 total commits to the home-assistant organization, 1 commit to pi-gen") - [rpitera (@rpitera)](https://github.com/rpitera "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") - [rubund (@rubund)](https://github.com/rubund "4 total commits to the home-assistant organization, 4 commits to home-assistant") -- [runningman84 (@runningman84)](https://github.com/runningman84 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Ruslan Kiyanchuk (@zoresvit)](https://github.com/zoresvit "1 total commits to the home-assistant organization, 1 commit to pi-gen") -- [Russell Cloran (@rcloran)](https://github.com/rcloran "19 total commits to the home-assistant organization, 15 commits to home-assistant, 4 commits to homebridge-homeassistant") +- [Russell Cloran (@rcloran)](https://github.com/rcloran "21 total commits to the home-assistant organization, 17 commits to home-assistant, 4 commits to homebridge-homeassistant") - [Ryan Bahm (@rdbahm)](https://github.com/rdbahm "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Ryan Borstelmann (@SlothCroissant)](https://github.com/SlothCroissant "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Ryan Daigle (@rwdaigle)](https://github.com/rwdaigle "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Ryan Kraus (@rmkraus)](https://github.com/rmkraus "193 total commits to the home-assistant organization, 163 commits to home-assistant, 15 commits to home-assistant.github.io, 14 commits to home-assistant-polymer, 1 commit to home-assistant-notebooks") -- [Ryan McLean (@ryanm101)](https://github.com/ryanm101 "47 total commits to the home-assistant organization, 35 commits to hassio-cli, 7 commits to home-assistant, 5 commits to home-assistant.github.io") +- [Ryan McLean (@ryanm101)](https://github.com/ryanm101 "65 total commits to the home-assistant organization, 53 commits to hassio-cli, 7 commits to home-assistant, 5 commits to home-assistant.github.io") - [Ryan Turner (@turnrye)](https://github.com/turnrye "6 total commits to the home-assistant organization, 6 commits to home-assistant") - [Sabesto (@Sabesto)](https://github.com/Sabesto "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Sam Birch (@hotplot)](https://github.com/hotplot "2 total commits to the home-assistant organization, 2 commits to home-assistant") @@ -724,15 +731,15 @@ This page contains a list of people who have contributed in one way or another t - [Scott Griffin (@scottocs11)](https://github.com/scottocs11 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io") - [Scott O'Neil (@americanwookie)](https://github.com/americanwookie "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io") - [Scott Reston (@ih8gates)](https://github.com/ih8gates "9 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 1 commit to home-assistant-polymer") -- [Sean Dague (@sdague)](https://github.com/sdague "64 total commits to the home-assistant organization, 44 commits to home-assistant, 11 commits to home-assistant.github.io, 5 commits to home-assistant-polymer, 3 commits to netdisco, 1 commit to home-assistant-js") +- [Sean Dague (@sdague)](https://github.com/sdague "72 total commits to the home-assistant organization, 49 commits to home-assistant, 14 commits to home-assistant.github.io, 5 commits to home-assistant-polymer, 3 commits to netdisco, 1 commit to home-assistant-js") - [Sean Gollschewsky (@gollo)](https://github.com/gollo "17 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io, 3 commits to hassio-build") - [Sean Wilson (@swilson)](https://github.com/swilson "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Sebastian (@sebk-666)](https://github.com/sebk-666 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Sebastian (@sgso)](https://github.com/sgso "3 total commits to the home-assistant organization, 3 commits to libcoap") -- [Sebastian Muszynski (@syssi)](https://github.com/syssi "42 total commits to the home-assistant organization, 21 commits to home-assistant, 19 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") +- [Sebastian Muszynski (@syssi)](https://github.com/syssi "49 total commits to the home-assistant organization, 24 commits to home-assistant, 23 commits to home-assistant.github.io, 2 commits to home-assistant-polymer") - [Sebastian von Minckwitz (@teodoc)](https://github.com/teodoc "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Semir Patel (@analogue)](https://github.com/analogue "2 total commits to the home-assistant organization, 2 commits to appdaemon") -- [Sergey Isachenko (@zabuldon)](https://github.com/zabuldon "6 total commits to the home-assistant organization, 6 commits to home-assistant") +- [Sergey Isachenko (@zabuldon)](https://github.com/zabuldon "7 total commits to the home-assistant organization, 7 commits to home-assistant") - [Sergey Vishnikin (@armicron)](https://github.com/armicron "33 total commits to the home-assistant organization, 33 commits to warrant") - [sfam (@sfam)](https://github.com/sfam "65 total commits to the home-assistant organization, 58 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-polymer") - [sharukins (@sharukins)](https://github.com/sharukins "3 total commits to the home-assistant organization, 3 commits to hassio-build") @@ -752,6 +759,7 @@ This page contains a list of people who have contributed in one way or another t - [Steven Looman (@StevenLooman)](https://github.com/StevenLooman "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Stu Gott (@stu-gott)](https://github.com/stu-gott "9 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant") - [Stuart Mumford (@Cadair)](https://github.com/Cadair "2 total commits to the home-assistant organization, 2 commits to home-assistant") +- [Stuart Williams (@stuwil)](https://github.com/stuwil "1 total commits to the home-assistant organization, 1 commit to netdisco") - [swanwila (@swanwila)](https://github.com/swanwila "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [System Tester (@systemtester)](https://github.com/systemtester "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Sytone (@sytone)](https://github.com/sytone "9 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant, 1 commit to hassio-build") @@ -763,7 +771,7 @@ This page contains a list of people who have contributed in one way or another t - [tedstriker (@tedstriker)](https://github.com/tedstriker "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [Teemu Mikkonen (@T3m3z)](https://github.com/T3m3z "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Teemu Patja (@tpatja)](https://github.com/tpatja "2 total commits to the home-assistant organization, 2 commits to home-assistant") -- [Teemu R. (@rytilahti)](https://github.com/rytilahti "44 total commits to the home-assistant organization, 35 commits to home-assistant, 7 commits to home-assistant.github.io, 2 commits to netdisco") +- [Teemu R. (@rytilahti)](https://github.com/rytilahti "45 total commits to the home-assistant organization, 36 commits to home-assistant, 7 commits to home-assistant.github.io, 2 commits to netdisco") - [Teguh Sobirin (@tjstyle)](https://github.com/tjstyle "2 total commits to the home-assistant organization, 2 commits to pi-gen") - [Tentoe (@Tentoe)](https://github.com/Tentoe "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Theb-1 (@Theb-1)](https://github.com/Theb-1 "5 total commits to the home-assistant organization, 5 commits to home-assistant") @@ -772,9 +780,9 @@ This page contains a list of people who have contributed in one way or another t - [Thiago Oliveira (@chilicheech)](https://github.com/chilicheech "3 total commits to the home-assistant organization, 3 commits to home-assistant") - [Thibault Cohen (@titilambert)](https://github.com/titilambert "41 total commits to the home-assistant organization, 28 commits to home-assistant, 13 commits to home-assistant.github.io") - [Thibault Maekelbergh (@thibmaek)](https://github.com/thibmaek "4 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 1 commit to hassio-addons") -- [Thijs de Jong (@bakedraccoon)](https://github.com/bakedraccoon "5 total commits to the home-assistant organization, 5 commits to home-assistant") +- [Thijs de Jong (@bakedraccoon)](https://github.com/bakedraccoon "8 total commits to the home-assistant organization, 8 commits to home-assistant") - [ThinkPadNL (@ThinkPadNL)](https://github.com/ThinkPadNL "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") -- [Thom Troy (@ttroy50)](https://github.com/ttroy50 "11 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 4 commits to home-assistant") +- [Thom Troy (@ttroy50)](https://github.com/ttroy50 "12 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 5 commits to home-assistant") - [Thomas Friedel (@tfriedel)](https://github.com/tfriedel "2 total commits to the home-assistant organization, 2 commits to home-assistant") - [Thomas Petazzoni (@tpetazzoni)](https://github.com/tpetazzoni "1 total commits to the home-assistant organization, 1 commit to libcoap") - [Thomas Phillips (@thomas-phillips-nz)](https://github.com/thomas-phillips-nz "2 total commits to the home-assistant organization, 2 commits to pi-gen") @@ -807,7 +815,7 @@ This page contains a list of people who have contributed in one way or another t - [Trevor (@tboyce021)](https://github.com/tboyce021 "15 total commits to the home-assistant organization, 10 commits to home-assistant, 5 commits to home-assistant.github.io") - [Trey Hunner (@treyhunner)](https://github.com/treyhunner "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io") - [trollkarlen (@trollkarlen)](https://github.com/trollkarlen "5 total commits to the home-assistant organization, 5 commits to home-assistant") -- [tschmidty69 (@tschmidty69)](https://github.com/tschmidty69 "6 total commits to the home-assistant organization, 6 commits to home-assistant") +- [tschmidty69 (@tschmidty69)](https://github.com/tschmidty69 "16 total commits to the home-assistant organization, 13 commits to home-assistant, 3 commits to home-assistant.github.io") - [Tsvi Mostovicz (@tsvi)](https://github.com/tsvi "9 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant") - [Tyler Page (@iamtpage)](https://github.com/iamtpage "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant") - [Tõnis Tobre (@tobre6)](https://github.com/tobre6 "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant") @@ -817,8 +825,10 @@ This page contains a list of people who have contributed in one way or another t - [upsert (@upsert)](https://github.com/upsert "1 total commits to the home-assistant organization, 1 commit to netdisco") - [User5981 (@User5981)](https://github.com/User5981 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Valentin Alexeev (@valentinalexeev)](https://github.com/valentinalexeev "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io") +- [Victor Cerutti (@victorcerutti)](https://github.com/victorcerutti "2 total commits to the home-assistant organization, 2 commits to home-assistant-polymer") - [Viet Dzung (@dzungpv)](https://github.com/dzungpv "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [Vignesh Venkat (@vickyg3)](https://github.com/vickyg3 "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io") +- [Ville Skyttä (@scop)](https://github.com/scop "13 total commits to the home-assistant organization, 9 commits to home-assistant, 3 commits to netdisco, 1 commit to hassio-build") - [viswa-swami (@viswa-swami)](https://github.com/viswa-swami "9 total commits to the home-assistant organization, 9 commits to home-assistant") - [Vlad Korniev (@vkorn)](https://github.com/vkorn "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to hassio-build") - [vllungu (@vllungu)](https://github.com/vllungu "3 total commits to the home-assistant organization, 3 commits to libcoap") @@ -831,11 +841,11 @@ This page contains a list of people who have contributed in one way or another t - [Will W. (@tiktok7)](https://github.com/tiktok7 "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [Willems Davy (@joyrider3774)](https://github.com/joyrider3774 "7 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant") - [William Johansson (@radhus)](https://github.com/radhus "1 total commits to the home-assistant organization, 1 commit to hassio") -- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "106 total commits to the home-assistant organization, 71 commits to home-assistant, 33 commits to home-assistant.github.io, 2 commits to netdisco") +- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "110 total commits to the home-assistant organization, 75 commits to home-assistant, 33 commits to home-assistant.github.io, 2 commits to netdisco") - [williamlehman (@williamlehman)](https://github.com/williamlehman "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer") - [wind-rider (@wind-rider)](https://github.com/wind-rider "5 total commits to the home-assistant organization, 5 commits to home-assistant") - [wokar (@wokar)](https://github.com/wokar "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.github.io") -- [Wolf-Bastian Pöttner (@BastianPoe)](https://github.com/BastianPoe "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io") +- [Wolf-Bastian Pöttner (@BastianPoe)](https://github.com/BastianPoe "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io") - [Wolfgang Malgadey (@wmalgadey)](https://github.com/wmalgadey "4 total commits to the home-assistant organization, 4 commits to home-assistant") - [XECDesign (@XECDesign)](https://github.com/XECDesign "97 total commits to the home-assistant organization, 97 commits to pi-gen") - [Xorso (@Xorso)](https://github.com/Xorso "22 total commits to the home-assistant organization, 21 commits to home-assistant, 1 commit to hassio-addons") @@ -848,9 +858,9 @@ This page contains a list of people who have contributed in one way or another t - [Zhao Lu (@zlu)](https://github.com/zlu "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io") - [Zio Tibia (@ziotibia81)](https://github.com/ziotibia81 "14 total commits to the home-assistant organization, 7 commits to home-assistant, 7 commits to home-assistant.github.io") - [Zorks (@Zorks)](https://github.com/Zorks "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io") -- [Åskar Andersson (@olskar)](https://github.com/olskar "5 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 1 commit to hassbian-scripts") +- [Åskar Andersson (@olskar)](https://github.com/olskar "6 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 1 commit to hassbian-scripts") This page is irregularly updated using the [`credits_generator` tool](https://github.com/home-assistant/home-assistant.github.io/tree/next/credits_generator). If you think that you are missing, please let us know. -This page was last updated Saturday, January 13th 2018, 6:07:58 pm UTC. +This page was last updated Monday, January 29th 2018, 10:42:30 pm UTC. From 6132263e2ba7707d326ad279aa39dd5ad591ff96 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 29 Jan 2018 16:41:05 -0800 Subject: [PATCH 27/59] Release 0.62.1 --- _config.yml | 6 ++-- source/_posts/2018-01-27-release-62.markdown | 33 +++++++++++++++++++- 2 files changed, 35 insertions(+), 4 deletions(-) diff --git a/_config.yml b/_config.yml index 732f3e54776..25bc8745bcd 100644 --- a/_config.yml +++ b/_config.yml @@ -140,13 +140,13 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 62 -current_patch_version: 0 -date_released: 2018-01-27 +current_patch_version: 1 +date_released: 2018-01-30 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. # Major release: -patch_version_notes: "#" +patch_version_notes: "#release-0621---january-30" # Minor release (Example #release-0431---april-25): # Date we moved to Discourse for comments diff --git a/source/_posts/2018-01-27-release-62.markdown b/source/_posts/2018-01-27-release-62.markdown index 95815a31048..8bb54a09f06 100644 --- a/source/_posts/2018-01-27-release-62.markdown +++ b/source/_posts/2018-01-27-release-62.markdown @@ -29,6 +29,16 @@ With this new integration by [@sdague] you are able to keep an eye on your Chevy - Ihc component and platforms ([@dingusdk] - [#10916]) ([ihc docs]) ([binary_sensor.ihc docs]) ([light.ihc docs]) ([sensor.ihc docs]) ([switch.ihc docs]) (new-platform) - Iota wallet ([@jinnerbichler] - [#11398]) ([iota docs]) ([sensor.iota docs]) (new-platform) +## {% linkable_title Release 0.62.1 - January 30 %} + +- Snips - (fix/change) remove response when intent not handled ([@tschmidty69] - [#11929]) ([snips docs]) +- Fix asuswrt AttributeError on neigh for unknown device ([@scop] - [#11960]) ([device_tracker.asuswrt docs]) +- Set default values for Daikin devices that don't support fan direction and fan speed features ([@rofrantz] - [#12000]) ([climate.daikin docs]) +- Fix parameter escaping ([@smoldaner] - [#12008]) ([media_player.squeezebox docs]) +- Error handling, in case no connections are available ([@ReneNulschDE] - [#12010]) ([sensor.deutsche_bahn docs]) +- Fix 404 for Hass.io panel using frontend dev ([@c727] - [#12039]) ([frontend docs]) +- Upgrade pyharmony to 1.0.20 ([@amelchio] - [#12043]) ([remote.harmony docs]) + ## {% linkable_title If you need help... %} ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. @@ -477,4 +487,25 @@ Experiencing issues introduced by this release? Please report them in our [issue [xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/ [zwave docs]: https://home-assistant.io/components/zwave/ [@martinhjelmare]: https://github.com/martinhjelmare -[@frenck]: https://github.com/frenck \ No newline at end of file +[@frenck]: https://github.com/frenck +[#11929]: https://github.com/home-assistant/home-assistant/pull/11929 +[#11960]: https://github.com/home-assistant/home-assistant/pull/11960 +[#12000]: https://github.com/home-assistant/home-assistant/pull/12000 +[#12008]: https://github.com/home-assistant/home-assistant/pull/12008 +[#12010]: https://github.com/home-assistant/home-assistant/pull/12010 +[#12039]: https://github.com/home-assistant/home-assistant/pull/12039 +[#12043]: https://github.com/home-assistant/home-assistant/pull/12043 +[@ReneNulschDE]: https://github.com/ReneNulschDE +[@amelchio]: https://github.com/amelchio +[@c727]: https://github.com/c727 +[@rofrantz]: https://github.com/rofrantz +[@scop]: https://github.com/scop +[@smoldaner]: https://github.com/smoldaner +[@tschmidty69]: https://github.com/tschmidty69 +[climate.daikin docs]: https://home-assistant.io/components/climate.daikin/ +[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/ +[frontend docs]: https://home-assistant.io/components/frontend/ +[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/ +[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/ +[sensor.deutsche_bahn docs]: https://home-assistant.io/components/sensor.deutsche_bahn/ +[snips docs]: https://home-assistant.io/components/snips/ From 6c9bacf74052e34bc910274f43033dcce6ac30cd Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Tue, 30 Jan 2018 08:06:53 +0100 Subject: [PATCH 28/59] Change domain Use an official IANA example domain: example.com - which nobody owns (except IANA) --- source/_components/notify.html5.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index f53d7dc74af..e43d99aa349 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -43,12 +43,12 @@ Configuration variables: #### {% linkable_title Verify your domain %} Follow these steps to verify domain ownership with Google Webmaster Central / Search Console: -1. Enter your domain and add **'/local'** at the end, ie. https://whitehouse.duckdns.org:8123/local +1. Enter your domain and add **'/local'** at the end, ie. https://example.com:8123/local 2. Select HTML file verification and download the google*.html file. 2. Create a directory named "www" in your Home Assistant configuration directory (/config share from Samba add-on). 3. Place the downloaded google*.html file in the "www" directory. 4. RESTART Home Assistant - this is important! -5. Verify the file can be accessed in the browser, ie. **https://whitehouse.duckdns.org:8123/local/goole123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps. +5. Verify the file can be accessed in the browser, ie. **https://example.com:8123/local/goole123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps. 6. Go back to Google Webmaster Central / Search Console and proceed with the verification. ### {% linkable_title Requirements %} From 1c4f1dc13d031e9e10bb1df0b928b8a67d97af0f Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Tue, 30 Jan 2018 08:07:23 +0100 Subject: [PATCH 29/59] fix typo --- source/_components/notify.html5.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index e43d99aa349..5081ff20138 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -48,7 +48,7 @@ Follow these steps to verify domain ownership with Google Webmaster Central / Se 2. Create a directory named "www" in your Home Assistant configuration directory (/config share from Samba add-on). 3. Place the downloaded google*.html file in the "www" directory. 4. RESTART Home Assistant - this is important! -5. Verify the file can be accessed in the browser, ie. **https://example.com:8123/local/goole123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps. +5. Verify the file can be accessed in the browser, ie. **https://example.com:8123/local/google123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps. 6. Go back to Google Webmaster Central / Search Console and proceed with the verification. ### {% linkable_title Requirements %} From 5b6c51c1548d9f5647c0427396a05d05d76c6788 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Jan 2018 09:43:05 +0100 Subject: [PATCH 30/59] Move all scripts to one location as one page per script (#4554) --- source/_components/influxdb.markdown | 116 +------------------ source/_docs/configuration/secrets.markdown | 58 +--------- source/_docs/tools/benchmark.markdown | 20 ++++ source/_docs/tools/check_config.markdown | 18 +++ source/_docs/tools/credstash.markdown | 33 ++++++ source/_docs/tools/db_migrator.markdown | 72 ++++++++++++ source/_docs/tools/ensure_config.markdown | 18 +++ source/_docs/tools/influxdb_import.markdown | 64 ++++++++++ source/_docs/tools/keyring.markdown | 42 +++++++ source/_docs/tools/scripts.markdown | 42 +------ source/_includes/asides/docs_navigation.html | 8 +- 11 files changed, 282 insertions(+), 209 deletions(-) create mode 100644 source/_docs/tools/benchmark.markdown create mode 100644 source/_docs/tools/check_config.markdown create mode 100644 source/_docs/tools/credstash.markdown create mode 100644 source/_docs/tools/db_migrator.markdown create mode 100644 source/_docs/tools/ensure_config.markdown create mode 100644 source/_docs/tools/influxdb_import.markdown create mode 100644 source/_docs/tools/keyring.markdown diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown index f2291bda29d..4252068c038 100644 --- a/source/_components/influxdb.markdown +++ b/source/_components/influxdb.markdown @@ -49,123 +49,13 @@ Configuration variables: - **tags** (*Optional*): Tags to mark the data. - **tags_attributes** (*Optional*): The list of attribute names which should be reported as tags and not fields to InfluxDB. For example, if set to `friendly_name`, it will be possible to group by entities' friendly names as well, in addition to their ids. -## {% linkable_title Data migration %} +## {% linkable_title Helper scripts %} -Starting with 0.36 the InfluxDB component has a new schema to store values in the InfluxDB databases. - -- There will no longer be any tags/fields named `time`. -- All numeric fields (int/float/bool) will be stored as float inside InfluxDB database. -- All string fields corresponding to state attributes will be renamed as `FIELDNAME_str`, where `FIELDNAME` is the state attribute, to avoid type conflicts. -- All string fields corresponding to a state will be renamed as `state` (former value). -- Fields named `value` will always be stored as float. -- Fields named `state` will always be stored as string. - -### {% linkable_title Migration script %} - -If you need to migrate your database, you may require to run the `influxdb_migrator` script. Run the script after upgrade to 0.36 but before the first regular start of `hass` version 0.36. - -These are the steps the script will perform: -1. Create a new database (called `DBNAME__old`) to store old data. -2. Copy data from `DBNAME` database to `DBNAME__old` database. -3. Empty `DBNAME` database (using `drop` then `create`). `DBNAME` database is now considered as the new database. -4. For each measurement of `DBNAME__old` database: - 1. Read all points from the current measurement (in groups of 1000 points by default) and convert them. - 2. Send group of points to `DBNAME` database. -5. Delete the `DBNAME__old` database if needed. - -Example to run the script: - -```bash -$ hass --script influxdb_migrator \ - -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \ - -d INFLUXDB_DB_NAME -``` -Script arguments: - -``` -required arguments: - -d dbname, --dbname dbname InfluxDB database name - -optional arguments: - -h, --help show this help message and exit - -H host, --host host InfluxDB host address - -P port, --port port InfluxDB host port - -u username, --username username - InfluxDB username - -p password, --password password - InfluxDB password - -s step, --step step How many points to migrate at the same time - -o override_measurement, --override-measurement override_measurement - Store all your points in the same measurement - -D, --delete Delete old database -``` - -- If you run the script with only the `-h` option, you will get a help printout with a short explanation of the different options. -- The host option defaults to `'127.0.0.1'`. -- The port option defaults to `8086`. -- You should be able to omit username and password if InfluxDB authentication is disabled, which it is by default. -- The step option defaults to `1000`. - - -## {% linkable_title Data import script %} - -If you want to import all the recorded data from your recorder database you can use the data import script. -It will read all your state_change events from the database and add them as data-points to the InfluxDB. -You can specify the source database either by pointing the `--config` option to the config directory which includes the default SQLite database or by giving a sqlalchemy connection URI with `--uri`. -The writing to InfluxDB is done in batches that can be changed with `--step`. - -You can control, which data is imported by using the command line options `--exclude_entities` and `--exclude_domains`. -Both get a comma separated list of either entity-ids or domain names that are excluded from the import. - -To test what gets imported you can use the `--simulate` option, which disables the actual write to the InfluxDB instance. -This only writes the statistics how much points would be imported from which entity. - -Example to run the script: - -```bash -$ hass --script influxdb_import --config CONFIG_DIR \ - -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \ - --dbname INFLUXDB_DB_NAME --exclude_domains automation,configurator -``` -Script arguments: - -``` -required arguments: - -d dbname, --dbname dbname - InfluxDB database name - -optional arguments: - -h, --help show this help message and exit - -c path_to_config_dir, --config path_to_config_dir - Directory that contains the Home Assistant - configuration - --uri URI Connect to URI and import (if other than default - sqlite) eg: mysql://localhost/homeassistant - - -H host, --host host InfluxDB host address - -P port, --port port InfluxDB host port - -u username, --username username - InfluxDB username - -p password, --password password - InfluxDB password - -s step, --step step How many points to import at the same time - -t tags, --tags tags Comma separated list of tags (key:value) for all - points - -D default_measurement, --default-measurement default_measurement - Store all your points in the same measurement - -o override_measurement, --override-measurement override_measurement - Store all your points in the same measurement - -e exclude_entities, --exclude_entities exclude_entities - Comma separated list of excluded entities - -E exclude_domains, --exclude_domains exclude_domains - Comma separated list of excluded domains - -S, --simulate Do not write points but simulate preprocessing - and print statistics -``` +- [Helper script `influxdb_import`](/docs/tools/influxdb_import/) +- [Helper script `db_migrator`](/docs/tools/db_migrator/) (only used for [Home Assistant 0.36](/blog/2017/01/14/iss-usps-images-packages/#influxdb-export)) ## {% linkable_title Examples %} - ### {% linkable_title Full configuration %} ```yaml diff --git a/source/_docs/configuration/secrets.markdown b/source/_docs/configuration/secrets.markdown index 523bba9c4c4..906c40f536e 100644 --- a/source/_docs/configuration/secrets.markdown +++ b/source/_docs/configuration/secrets.markdown @@ -53,65 +53,15 @@ 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: +*Option 2*: View where secrets are retrieved from and the contents of all `secrets.yaml` files used, you can use the [`check_config` script](/docs/tools/check_config/) 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 %} +## {% linkable_title Alternatives to `secrets.yaml` %} -Using [Keyring](https://github.com/jaraco/keyring) is an alternative way to `secrets.yaml`. They can be managed from the command line via the `keyring` script. +- [Using a keyring that is managed by your OS to store secrets](/docs/tools/keyring/) +- [Storing passwords securely in AWS](/docs/tools/credstash/) -```bash -$ hass --script keyring --help -``` - -To store a password in keyring, replace your password or API key with `!secret` and an identifier in `configuration.yaml` file. - -```yaml -http: - api_password: !secret http_password -``` - -Create an entry in your keyring. - -```bash -$ hass --script keyring set http_password -``` - -If you launch Home Assistant now, you will be prompted for the keyring password to unlock your keyring. - -```bash -$ hass -Config directory: /home/homeassistant/.homeassistant -Please enter password for encrypted keyring: -``` - -

- If you are using the Python Keyring, [autostarting](/getting-started/autostart/) of Home Assistant will no longer work. -

- -### {% linkable_title Storing passwords securely in AWS %} - -Using [Credstash](https://github.com/fugue/credstash) is an alternative way to `secrets.yaml`. They can be managed from the command line via the credstash script. - -Before using credstash, you need to set up AWS credentials either via the `aws` command line tool or using environment variables as explained in the [AWS CLI docs](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) as well as creating a KMS key named `credstash` as explained in the [credstash Readme](https://github.com/fugue/credstash#setting-up-kms). After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash. - -```bash -$ hass --script credstash --help -``` - -To store a password in credstash, replace your password or API key with `!secret` and an identifier in `configuration.yaml` file. - -```yaml -http: - api_password: !secret http_password -``` - -Create an entry in your credstash store. - -```bash -$ hass --script credstash set http_password -``` diff --git a/source/_docs/tools/benchmark.markdown b/source/_docs/tools/benchmark.markdown new file mode 100644 index 00000000000..c95894489e3 --- /dev/null +++ b/source/_docs/tools/benchmark.markdown @@ -0,0 +1,20 @@ +--- +layout: page +title: "benchmark" +description: "Script to perform benchmarking of Home Assistant" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /docs/tools/scripts/#benchmark +--- + +For testing the performance of Home Assistant the Benchmark script runs until you exit using Control+C. + +Firing and handling of a million events. + +```bash +$ hass --script benchmark async_million_events +``` + diff --git a/source/_docs/tools/check_config.markdown b/source/_docs/tools/check_config.markdown new file mode 100644 index 00000000000..f3a926783e2 --- /dev/null +++ b/source/_docs/tools/check_config.markdown @@ -0,0 +1,18 @@ +--- +layout: page +title: "check_config" +description: "Script to perform a check of the current configuration" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /docs/tools/scripts/#configuration-check +--- + +Test any changes to your `configuration.yaml` file before launching Home Assistant. This script allows you to test changes without the need to restart Home Assistant. + +```bash +$ hass --script check_config +``` + diff --git a/source/_docs/tools/credstash.markdown b/source/_docs/tools/credstash.markdown new file mode 100644 index 00000000000..0d419a104f4 --- /dev/null +++ b/source/_docs/tools/credstash.markdown @@ -0,0 +1,33 @@ +--- +layout: page +title: "credstash" +description: "Script to store credentials securely in AWS" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /docs/configuration/secrets/#storing-passwords-securely-in-aws +--- + +Using [Credstash](https://github.com/fugue/credstash) is an alternative way to `secrets.yaml`. They can be managed from the command line via the credstash script. + +Before using credstash, you need to set up AWS credentials either via the `aws` command line tool or using environment variables as explained in the [AWS CLI docs](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) as well as creating a KMS key named `credstash` as explained in the [credstash Readme](https://github.com/fugue/credstash#setting-up-kms). After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash. + +```bash +$ hass --script credstash --help +``` + +To store a password in credstash, replace your password or API key with `!secret` and an identifier in `configuration.yaml` file. + +```yaml +http: + api_password: !secret http_password +``` + +Create an entry in your credstash store. + +```bash +$ hass --script credstash set http_password +``` + diff --git a/source/_docs/tools/db_migrator.markdown b/source/_docs/tools/db_migrator.markdown new file mode 100644 index 00000000000..bdce8d1ab04 --- /dev/null +++ b/source/_docs/tools/db_migrator.markdown @@ -0,0 +1,72 @@ +--- +layout: page +title: "db_migrator" +description: "Script to migrate data in an InfluxDB database" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /components/influxdb/#data-migration +--- + +

+This script was only use for 0.36 release cycle! +

+ +Starting with 0.36 the [InfluxDB](omponents/influxdb/) component has a new schema to store values in the InfluxDB databases. + +- There will no longer be any tags/fields named `time`. +- All numeric fields (int/float/bool) will be stored as float inside InfluxDB database. +- All string fields corresponding to state attributes will be renamed as `FIELDNAME_str`, where `FIELDNAME` is the state attribute, to avoid type conflicts. +- All string fields corresponding to a state will be renamed as `state` (former value). +- Fields named `value` will always be stored as float. +- Fields named `state` will always be stored as string. + +## {% linkable_title Migration script %} + +If you need to migrate your database, you may require to run the `influxdb_migrator` script. Run the script after upgrade to 0.36 but before the first regular start of `hass` version 0.36. + +These are the steps the script will perform: + +1. Create a new database (called `DBNAME__old`) to store old data. +2. Copy data from `DBNAME` database to `DBNAME__old` database. +3. Empty `DBNAME` database (using `drop` then `create`). `DBNAME` database is now considered as the new database. +4. For each measurement of `DBNAME__old` database: + 1. Read all points from the current measurement (in groups of 1000 points by default) and convert them. + 2. Send group of points to `DBNAME` database. +5. Delete the `DBNAME__old` database if needed. + +Example to run the script: + +```bash +$ hass --script influxdb_migrator \ + -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \ + -d INFLUXDB_DB_NAME +``` +Script arguments: + +``` +required arguments: + -d dbname, --dbname dbname InfluxDB database name + +optional arguments: + -h, --help show this help message and exit + -H host, --host host InfluxDB host address + -P port, --port port InfluxDB host port + -u username, --username username + InfluxDB username + -p password, --password password + InfluxDB password + -s step, --step step How many points to migrate at the same time + -o override_measurement, --override-measurement override_measurement + Store all your points in the same measurement + -D, --delete Delete old database +``` + +- If you run the script with only the `-h` option, you will get a help printout with a short explanation of the different options. +- The host option defaults to `'127.0.0.1'`. +- The port option defaults to `8086`. +- You should be able to omit username and password if InfluxDB authentication is disabled, which it is by default. +- The step option defaults to `1000`. + diff --git a/source/_docs/tools/ensure_config.markdown b/source/_docs/tools/ensure_config.markdown new file mode 100644 index 00000000000..c9539398567 --- /dev/null +++ b/source/_docs/tools/ensure_config.markdown @@ -0,0 +1,18 @@ +--- +layout: page +title: "ensure_config" +description: "Script to perform a check if the configuration file exists" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /docs/tools/scripts/#existence-of-configuration +--- + +This script checks if the `configuration.yaml` file exists. If the file is not available, one is created. + +```bash +$ hass --script ensure_config +``` + diff --git a/source/_docs/tools/influxdb_import.markdown b/source/_docs/tools/influxdb_import.markdown new file mode 100644 index 00000000000..b8bea1046cc --- /dev/null +++ b/source/_docs/tools/influxdb_import.markdown @@ -0,0 +1,64 @@ +--- +layout: page +title: "influxdb_import" +description: "Script to import data into an InfluxDB database" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /components/influxdb/#data-import-script +--- + +If you want to import all the recorded data from your recorder database you can use the data import script. It will read all your state_change events from the database and add them as data-points to the InfluxDB. You can specify the source database either by pointing the `--config` option to the config directory which includes the default SQLite database or by giving a sqlalchemy connection URI with `--uri`. + +The writing to InfluxDB is done in batches that can be changed with `--step`. + +You can control, which data is imported by using the command line options `--exclude_entities` and `--exclude_domains`. Both get a comma separated list of either entity-ids or domain names that are excluded from the import. + +To test what gets imported you can use the `--simulate` option, which disables the actual write to the InfluxDB instance. This only writes the statistics how much points would be imported from which entity. + +Example to run the script: + +```bash +$ hass --script influxdb_import --config CONFIG_DIR \ + -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \ + --dbname INFLUXDB_DB_NAME --exclude_domains automation,configurator +``` +Script arguments: + +``` +required arguments: + -d dbname, --dbname dbname + InfluxDB database name + +optional arguments: + -h, --help show this help message and exit + -c path_to_config_dir, --config path_to_config_dir + Directory that contains the Home Assistant + configuration + --uri URI Connect to URI and import (if other than default + sqlite) eg: mysql://localhost/homeassistant + + -H host, --host host InfluxDB host address + -P port, --port port InfluxDB host port + -u username, --username username + InfluxDB username + -p password, --password password + InfluxDB password + -s step, --step step How many points to import at the same time + -t tags, --tags tags Comma separated list of tags (key:value) for all + points + -D default_measurement, --default-measurement default_measurement + Store all your points in the same measurement + -o override_measurement, --override-measurement override_measurement + Store all your points in the same measurement + -e exclude_entities, --exclude_entities exclude_entities + Comma separated list of excluded entities + -E exclude_domains, --exclude_domains exclude_domains + Comma separated list of excluded domains + -S, --simulate Do not write points but simulate preprocessing + and print statistics +``` + + diff --git a/source/_docs/tools/keyring.markdown b/source/_docs/tools/keyring.markdown new file mode 100644 index 00000000000..6434337b39f --- /dev/null +++ b/source/_docs/tools/keyring.markdown @@ -0,0 +1,42 @@ +--- +layout: page +title: "keyring" +description: "Script to store secrets in a keyring" +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +redirect_from: /docs/configuration/secrets/#storing-passwords-in-a-keyring-managed-by-your-os +--- + +Using [Keyring](https://github.com/jaraco/keyring) is an alternative way to `secrets.yaml`. The secrets can be managed from the command line via the `keyring` script. + +```bash +$ hass --script keyring --help +``` + +To store a password in keyring, replace your password or API key with `!secret` and an identifier in `configuration.yaml` file. + +```yaml +http: + api_password: !secret http_password +``` + +Create an entry in your keyring. + +```bash +$ hass --script keyring set http_password +``` + +If you launch Home Assistant now, you will be prompted for the keyring password to unlock your keyring. + +```bash +$ hass +Config directory: /home/homeassistant/.homeassistant +Please enter password for encrypted keyring: +``` + +

+ If you are using the Python Keyring, [autostarting](/getting-started/autostart/) of Home Assistant will no longer work. +

diff --git a/source/_docs/tools/scripts.markdown b/source/_docs/tools/scripts.markdown index a0b96505e3f..2b40ba28c5c 100644 --- a/source/_docs/tools/scripts.markdown +++ b/source/_docs/tools/scripts.markdown @@ -7,47 +7,7 @@ sidebar: true comments: false sharing: true footer: true +redirect_from: /docs/tools/ --- -The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with Home Assistant's [script](/docs/scripts/) feature. -### {% linkable_title Configuration check %} - -Test any changes to your `configuration.yaml` file before launching Home Assistant. This script allows you to test changes without the need to restart Home Assistant. - -```bash -$ hass --script check_config -``` - -### {% linkable_title Existence of configuration %} - -This script checks if the `configuration.yaml` file exists. If the file is not available, one is created. - -```bash -$ hass --script ensure_config -``` - -### {% linkable_title Secrets %} - -There is a method to store secrets outside of your `configuration.yaml` file. For further details, please refer to the [Storing Secrets](/docs/configuration/secrets/) documentation. - -```bash -$ hass --script keyring -``` - -### {% linkable_title Benchmark %} - -For testing the performance of Home Assistant the Benchmark script runs until you exit using Control+C. - -Firing and handling of a million events. - -```bash -$ hass --script benchmark async_million_events -``` - -### {% linkable_title Old scripts %} - -Usually those scripts were only used when a massive update happened and was announced in the release notes. - -- `db_migrator`: Migrate an existing SQLite database to the new schema. -- `influxdb_migrator`: Convert an old InfluxDB to the new format. diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html index 463f65313e5..c697024aac3 100644 --- a/source/_includes/asides/docs_navigation.html +++ b/source/_includes/asides/docs_navigation.html @@ -87,7 +87,13 @@
  • {% active_link /docs/tools/dev-tools/ Developer Tools %}
  • {% active_link /docs/tools/hass/ hass %}
    • -
  • {% active_link /docs/tools/scripts/ Scripts %}
    • +
  • {% active_link /docs/tools/benchmark/ benchmark %}
    • +
  • {% active_link /docs/tools/check_config/ check_config %}
    • +
  • {% active_link /docs/tools/credstash/ credstash %}
    • +
  • {% active_link /docs/tools/db_migrator/ db_migrator %}
    • +
  • {% active_link /docs/tools/ensure_config/ ensure_config %}
    • +
  • {% active_link /docs/tools/influxdb_import/ influxdb_import %}
    • +
  • {% active_link /docs/tools/keyring/ keyring %}
  • From 51f5cd59e99398841abb8eeca6a72ed3768c48df Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 31 Jan 2018 10:25:22 +0100 Subject: [PATCH 31/59] Add missing influxdb_migrator (#4555) * Add missing influxdb_migrator * remove redirect --- source/_docs/tools/influxdb_migrator.markdown | 39 +++++++++++++++++++ source/_includes/asides/docs_navigation.html | 1 + 2 files changed, 40 insertions(+) create mode 100644 source/_docs/tools/influxdb_migrator.markdown diff --git a/source/_docs/tools/influxdb_migrator.markdown b/source/_docs/tools/influxdb_migrator.markdown new file mode 100644 index 00000000000..df8e83e4058 --- /dev/null +++ b/source/_docs/tools/influxdb_migrator.markdown @@ -0,0 +1,39 @@ +--- +layout: page +title: "influxdb_migrator" +description: "Script to convert an old-structure Influx database to a new one." +release_date: 2017-02-23 11:00:00 +sidebar: true +comments: false +sharing: true +footer: true +--- + +Script to convert an old-structure Influx database to a new one. + +Example to run the script: + +```bash +$ hass --script influxdb_migrator -H IP_INFLUXDB_HOST \ + -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \ + --dbname INFLUXDB_DB_NAME +``` +Script arguments: + +``` +optional arguments: + -h, --help show this help message and exit + -d dbname, --dbname dbname + InfluxDB database name + -H host, --host host InfluxDB host address + -P port, --port port InfluxDB host port + -u username, --username username + InfluxDB username + -p password, --password password + InfluxDB password + -s step, --step step How many points to migrate at the same time + -o override_measurement, --override-measurement override_measurement + Store all your points in the same measurement + -D, --delete Delete old database +``` + diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html index c697024aac3..add2fd1bbc6 100644 --- a/source/_includes/asides/docs_navigation.html +++ b/source/_includes/asides/docs_navigation.html @@ -93,6 +93,7 @@
  • {% active_link /docs/tools/db_migrator/ db_migrator %}
  • {% active_link /docs/tools/ensure_config/ ensure_config %}
  • {% active_link /docs/tools/influxdb_import/ influxdb_import %}
    • +
  • {% active_link /docs/tools/influxdb_migrator/ influxdb_migrator %}
  • {% active_link /docs/tools/keyring/ keyring %}
    • From bcdf76407a1929e6a28f609ef94d6d67b239e33a Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 31 Jan 2018 11:38:02 -0800 Subject: [PATCH 32/59] Fix ha_release --- source/_components/alarm_control_panel.manual_mqtt.markdown | 2 +- source/_components/camera.dispatcher.markdown | 2 +- source/_components/cloud.alexa.markdown | 2 +- source/_components/cloud.markdown | 2 +- source/_components/fan.insteon_hub.markdown | 2 +- source/_components/hue.markdown | 4 ++-- source/_components/sensor.darksky.markdown | 2 +- source/_components/sensor.kwb.markdown | 2 +- source/_components/sensor.ted5000.markdown | 2 +- 9 files changed, 10 insertions(+), 10 deletions(-) diff --git a/source/_components/alarm_control_panel.manual_mqtt.markdown b/source/_components/alarm_control_panel.manual_mqtt.markdown index 95fd3e09ff2..be1508c6761 100644 --- a/source/_components/alarm_control_panel.manual_mqtt.markdown +++ b/source/_components/alarm_control_panel.manual_mqtt.markdown @@ -9,7 +9,7 @@ sharing: true footer: true logo: home-assistant.png ha_category: Alarm -ha_release: 0.50 +ha_release: "0.50" --- This platform extends the [manual alarm](/components/alarm_control_panel.manual/) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant. diff --git a/source/_components/camera.dispatcher.markdown b/source/_components/camera.dispatcher.markdown index 62395dc993e..2672c6c48ec 100644 --- a/source/_components/camera.dispatcher.markdown +++ b/source/_components/camera.dispatcher.markdown @@ -9,7 +9,7 @@ sharing: true footer: true ha_category: Camera logo: camcorder.png -ha_release: 0.40 +ha_release: "0.40" ha_iot_class: "depends" --- diff --git a/source/_components/cloud.alexa.markdown b/source/_components/cloud.alexa.markdown index 81a4b09eac6..5f30f112a11 100644 --- a/source/_components/cloud.alexa.markdown +++ b/source/_components/cloud.alexa.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: home-assistant.png -ha_release: 0.60 +ha_release: "0.60" ha_category: Cloud ha_iot_class: "Cloud Push" --- diff --git a/source/_components/cloud.markdown b/source/_components/cloud.markdown index 57717e6eabe..d45e9aa15f3 100644 --- a/source/_components/cloud.markdown +++ b/source/_components/cloud.markdown @@ -8,7 +8,7 @@ comments: false sharing: true footer: true logo: home-assistant.png -ha_release: 0.60 +ha_release: "0.60" ha_category: Voice ha_iot_class: "Cloud Push" --- diff --git a/source/_components/fan.insteon_hub.markdown b/source/_components/fan.insteon_hub.markdown index 364b94fa40c..b5ce9adbc79 100644 --- a/source/_components/fan.insteon_hub.markdown +++ b/source/_components/fan.insteon_hub.markdown @@ -9,7 +9,7 @@ sharing: true footer: true logo: insteon.png ha_category: Fan -ha_release: 0.30 +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. diff --git a/source/_components/hue.markdown b/source/_components/hue.markdown index 40623c9a95a..fb73a05824c 100644 --- a/source/_components/hue.markdown +++ b/source/_components/hue.markdown @@ -11,7 +11,7 @@ logo: philips_hue.png ha_category: Hub ha_iot_class: "Local Polling" featured: true -ha_release: 0.60 +ha_release: "0.60" --- Philips Hue support is integrated into Home Assistant as a Hub that can drive the light platform. The preferred way to setup the Philips Hue platform is by enabling the [discovery component](/components/discovery/). @@ -54,7 +54,7 @@ You will need to convert each bridge into an entry in the new configuration styl ### {% linkable_title Multiple Hue bridges %} -Multiple Hue bridges work transparently with discovery, you don't have to do anything. If you prefer to configure them manually and use multiple Hue bridges then it's needed that you provide a configuration file for every bridge. The bridges can't share a single configuration file. +Multiple Hue bridges work transparently with discovery, you don't have to do anything. If you prefer to configure them manually and use multiple Hue bridges then it's needed that you provide a configuration file for every bridge. The bridges can't share a single configuration file. Add `filename` to your Hue configuration entry in your `configuration.yaml` file: diff --git a/source/_components/sensor.darksky.markdown b/source/_components/sensor.darksky.markdown index 427d5afb683..11edb0c1ceb 100644 --- a/source/_components/sensor.darksky.markdown +++ b/source/_components/sensor.darksky.markdown @@ -10,7 +10,7 @@ footer: true logo: dark_sky.png ha_category: Weather featured: true -ha_release: 0.30 +ha_release: "0.30" redirect_from: /components/sensor.forecast/ ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/sensor.kwb.markdown b/source/_components/sensor.kwb.markdown index c53b43e8c27..7148e016f22 100644 --- a/source/_components/sensor.kwb.markdown +++ b/source/_components/sensor.kwb.markdown @@ -10,7 +10,7 @@ footer: true logo: kwb.png ha_category: Sensor ha_iot_class: "Local Polling" -ha_release: 0.40 +ha_release: "0.40" --- The `kwb` component integrates the sensors of KWB Easyfire pellet central heating units with the Comfort3 controller (http://www.kwbheizung.de/de/produkte/kwb-comfort-3.html) into Home Assistant. diff --git a/source/_components/sensor.ted5000.markdown b/source/_components/sensor.ted5000.markdown index fd09ab7d2ff..20e94ba3e8d 100644 --- a/source/_components/sensor.ted5000.markdown +++ b/source/_components/sensor.ted5000.markdown @@ -9,7 +9,7 @@ sharing: true footer: true logo: ted.png ha_category: Sensor -ha_release: 0.30 +ha_release: "0.30" ha_iot_class: "Local Polling" --- From 5ba8fa279fca6d5bcc9d768549952a792670e9ef Mon Sep 17 00:00:00 2001 From: Alex Barcelo Date: Thu, 1 Feb 2018 20:54:42 +0100 Subject: [PATCH 33/59] Document approach to IPv6 through `server_host` (#4561) Simplest way to listen to IPv6 is use the `server_host` directive in the http component. That was undocumented (and may be considered a workaround) but works as expected and requires no changes on the codebase. It is worth documenting that here IMHO. --- source/_components/http.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/http.markdown b/source/_components/http.markdown index 0a6d20b2cd0..98ec03f5a05 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -30,7 +30,7 @@ http: Configuration variables: - **api_password** (*Optional*): Protect Home Assistant with a password. -- **server_host** (*Optional*): Only listen to incoming requests on specific IP/host (default: accept all) +- **server_host** (*Optional*): Only listen to incoming requests on specific IP/host (default: bind to `0.0.0.0` which means accept all IPv4 connections). Use `server_host: "::0"` if you want to listen to (and only) IPv6. - **server_port** (*Optional*): Let you set a port to use. Defaults to 8123. - **base_url** (*Optional*): The URL that Home Assistant is available on the internet. For example: `hass-example.duckdns.org:8123`. Defaults to the local IP address. The iOS app finds local installations, if you have an outside URL use this so that you can auto-fill when discovered in the app. - **ssl_certificate** (*Optional*): Path to your TLS/SSL certificate to serve Home Assistant over a secure connection. From c9d67e8cd9bca0854e0cfef6d5609839f213894b Mon Sep 17 00:00:00 2001 From: Wopalecki <35042958+Wopalecki@users.noreply.github.com> Date: Thu, 1 Feb 2018 20:55:14 +0100 Subject: [PATCH 34/59] Adding quotes for the "login attempts" command (#4563) In hass.io installation, the command value must be quoted. --- source/_components/sensor.command_line.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.command_line.markdown b/source/_components/sensor.command_line.markdown index 3d5f533fbeb..e27656e9a5f 100644 --- a/source/_components/sensor.command_line.markdown +++ b/source/_components/sensor.command_line.markdown @@ -81,7 +81,7 @@ If you'd like to know how many failed login attempts are made to Home Assistant, sensor: - platform: command_line name: badlogin - command: grep -c 'Login attempt' /home/hass/.homeassistant/home-assistant.log + command: "grep -c 'Login attempt' /home/hass/.homeassistant/home-assistant.log" ``` Make sure to configure the [logger component](/components/logger) to monitor the [http component](https://home-assistant.io/components/http/) at least the `warning` level. From d270587129fd868c62ea37346be17df7e0f20606 Mon Sep 17 00:00:00 2001 From: boojew Date: Fri, 2 Feb 2018 04:23:55 -0500 Subject: [PATCH 35/59] Update mailgun.markdown (#4560) * Update mailgun.markdown * Update mailgun.markdown * Remove tailing whitespace --- source/_components/mailgun.markdown | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/source/_components/mailgun.markdown b/source/_components/mailgun.markdown index 835464dfd06..78764d7507e 100644 --- a/source/_components/mailgun.markdown +++ b/source/_components/mailgun.markdown @@ -12,7 +12,7 @@ ha_category: Notifications ha_release: 0.38 --- -The component supports push messages and generates events based on inbound data. To use, add a Route set to Store and Notify with a URL of the following form: `https:///api/mailgun?api_password=` +The component supports push messages and generates events based on inbound data. To use, add a Route set to Store and Notify with a URL of the following form: `https:///api/mailgun?api_password=` To send messages, use the [Mailgun notify platform][notify]. @@ -25,11 +25,10 @@ To send messages, use the [Mailgun notify platform][notify]. mailgun: domain: mg.example.com api_key: token-XXXXXXXXX - sandbox: False ``` Configuration variables: -- **domain** (*Optional*): This is the domain name to be used when sending out mail. Defaults to the first custom domain you have set up. -- **sandbox** (*Optional*): Whether to use the sandboxed domain for outgoing mail. The `domain` item takes precedence over this. Defaults to `False`. +- **domain** (*Required*): This is the domain name to be used when sending out mail. Defaults to the first custom domain you have set up. - **api_key** (*Required*): This is the API token that has been generated in your Mailgun account. +- **sandbox** (*Optional*): Whether to use the sandboxed domain for outgoing mail. The `domain` item takes precedence over this. Defaults to `False`. From ef66f7e2532e7b3874c4e1ebf3a899ac198928ab Mon Sep 17 00:00:00 2001 From: Andrew Cockburn Date: Fri, 2 Feb 2018 10:26:49 -0500 Subject: [PATCH 36/59] Update appdaemon.markdown --- source/_docs/ecosystem/appdaemon.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown index ca2a59f65e4..76edbc1dd54 100755 --- a/source/_docs/ecosystem/appdaemon.markdown +++ b/source/_docs/ecosystem/appdaemon.markdown @@ -107,4 +107,4 @@ Of course, if I wanted to make this App or its predecessor reusable, I would hav In addition, Apps can write to `AppDaemon`'s log files, and there is a system of constraints that allows you to control when and under what circumstances Apps and callbacks are active to keep the logic clean and simple. -For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/latest/). +For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/). From 2edccadc9fcb9fb65d86041f0646bafd01d9d044 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 3 Feb 2018 10:58:49 +0100 Subject: [PATCH 37/59] Re-add random sensor sample (it's referenced in automation) --- source/getting-started/configuration.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index 4d0175ec8b5..d9a23fcbcf9 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -68,4 +68,11 @@ Now that you are able to edit the configuration, it's time to set up some of you

    YAML can be a little daunting at first. A lot is possible! [Here is some more info.](/docs/configuration/devices/)

    +For a sensor that is showing [random values](/components/sensor.random/), the entry would look like the sample below: + +```yaml +sensor: + - platform: random +``` + ### [Next step: Automate Home Assistant »](/getting-started/automation/) From 2d61ef7f074735b812d1bd94da3547512e5f4d34 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sat, 3 Feb 2018 17:21:07 +0000 Subject: [PATCH 38/59] Added links to the voice components Added links to the voice components it supports. --- source/_components/intent_script.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/intent_script.markdown b/source/_components/intent_script.markdown index 68336fd79d5..eab43f4b930 100644 --- a/source/_components/intent_script.markdown +++ b/source/_components/intent_script.markdown @@ -12,7 +12,7 @@ ha_category: Intent ha_release: "0.50" --- -The intent_script component allows users to configure actions and responses to intents. Intents can be fired by any component that supports it. Examples are Alexa (Amazon Echo), API.ai (Google Assistant) and Snips. +The intent_script component allows users to configure actions and responses to intents. Intents can be fired by any component that supports it. Examples are [Alexa](/components/alexa/) (Amazon Echo), [API.ai](/components/dialogflow/) (Google Assistant) and [Snips](/components/snips/). ```yaml # Example configuration.yaml entry From f7679d10e93aaef44c6a5b071bf37bf79a3401de Mon Sep 17 00:00:00 2001 From: Andrew Cockburn Date: Sat, 3 Feb 2018 13:29:03 -0500 Subject: [PATCH 39/59] Update hadashboard.markdown (#4572) --- source/_docs/ecosystem/hadashboard.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/ecosystem/hadashboard.markdown b/source/_docs/ecosystem/hadashboard.markdown index c73560401ac..226b6906d96 100755 --- a/source/_docs/ecosystem/hadashboard.markdown +++ b/source/_docs/ecosystem/hadashboard.markdown @@ -39,4 +39,4 @@ HADashboard is a modular, skinnable dashboard for [Home Assistant](https://home- -For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/latest/DASHBOARD_INSTALL.html) +For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/stable/DASHBOARD_INSTALL.html) From 47822f61fdb30411353f0d81d47146a18a0b743d Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 3 Feb 2018 22:28:29 -0800 Subject: [PATCH 40/59] Update light.hue.markdown --- source/_components/light.hue.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_components/light.hue.markdown b/source/_components/light.hue.markdown index d4d37548b6b..8cd9aad47ea 100644 --- a/source/_components/light.hue.markdown +++ b/source/_components/light.hue.markdown @@ -10,7 +10,6 @@ footer: true logo: philips_hue.png ha_category: Light ha_iot_class: "Local Polling" -featured: true ha_release: pre 0.7 --- From 590a7bc3459f2e2dd7ff8c3c4db86253ec79d4f2 Mon Sep 17 00:00:00 2001 From: Robert Date: Mon, 5 Feb 2018 08:20:15 +0100 Subject: [PATCH 41/59] Note for 2014 and 2015 models (#4581) * Note for 2014 and 2015 models * Remove marking --- source/_components/media_player.samsungtv.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_components/media_player.samsungtv.markdown b/source/_components/media_player.samsungtv.markdown index edaec8ca36e..744488bebe7 100644 --- a/source/_components/media_player.samsungtv.markdown +++ b/source/_components/media_player.samsungtv.markdown @@ -74,6 +74,8 @@ Currently tested but not working models: - JS9500 - State is always "on" and unable to control (but port 8001 *is* open) - MU6300 - Port set to 8001, `pip3 install websocket-client` must be executed, turning on works, status not working reliably, turning off is not permanent (it comes back on) +None of the 2014 (H) and 2015 (J) model series (e.g. J5200) will work, since Samsung have used a different (encrypted) type of interface for these. + If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.samsungtv.markdown). The first letter (U, P, L, H & K) represent the screen type, e.g. LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these before adding them to the list. From c20709e3d09c5270189a86a179cb6a9540a134af Mon Sep 17 00:00:00 2001 From: Mike O'Driscoll Date: Mon, 5 Feb 2018 02:21:19 -0500 Subject: [PATCH 42/59] Add troubleshooting for Unifi Controller (#4578) Added documentation regarding accurate time sync for presence detection between home assistant and unifi controller. --- source/_components/device_tracker.unifi.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_components/device_tracker.unifi.markdown b/source/_components/device_tracker.unifi.markdown index f2b5e2a4350..cfb630d1a1a 100644 --- a/source/_components/device_tracker.unifi.markdown +++ b/source/_components/device_tracker.unifi.markdown @@ -79,4 +79,11 @@ well. It is recommended that you run the Unifi controller in a dedicate virtual machine to avoid that situation. +### {% linkable_title Troubleshooting and Time Synchronization %} + +Presence detection depends on accurate time configuration between Home Assistant and the Unifi controller. + +If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are syncronized. +Failing to have syncronized clocks will lead to Home Assistant failing to mark a device as home. + [Related Issue](https://github.com/home-assistant/home-assistant/issues/10507) From 280bac6515edaa39bacdaaa413004416c251c1db Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Mon, 5 Feb 2018 08:22:45 +0100 Subject: [PATCH 43/59] Remove line breaks --- source/_components/device_tracker.unifi.markdown | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/source/_components/device_tracker.unifi.markdown b/source/_components/device_tracker.unifi.markdown index cfb630d1a1a..a71db056556 100644 --- a/source/_components/device_tracker.unifi.markdown +++ b/source/_components/device_tracker.unifi.markdown @@ -64,26 +64,18 @@ See the [device tracker component page](/components/device_tracker/) for instruc ### {% linkable_title Configuring Users %} -The Unifi controller allows you to create multiple users on it besides -the main administrator. It is recommended that you create a limited -user that has `read-only` permissions for the Unifi device tracker. +The Unifi controller allows you to create multiple users on it besides the main administrator. It is recommended that you create a limited user that has `read-only` permissions for the Unifi device tracker. ### {% linkable_title Conflicts with MQTT %} -The Unifi controller can either be a dedicated hardware device -(Unifi's cloud key), or as software any Linux system. If you run the -the Unifi controller on the same operating system as Home Assistant -there may be conflicts in ports if you have the MQTT component as -well. +The Unifi controller can either be a dedicated hardware device (Unifi's cloud key), or as software any Linux system. If you run the the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well. -It is recommended that you run the Unifi controller in a dedicate -virtual machine to avoid that situation. +It is recommended that you run the Unifi controller in a dedicate virtual machine to avoid that situation. ### {% linkable_title Troubleshooting and Time Synchronization %} Presence detection depends on accurate time configuration between Home Assistant and the Unifi controller. -If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are syncronized. -Failing to have syncronized clocks will lead to Home Assistant failing to mark a device as home. +If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are syncronized. Failing to have syncronized clocks will lead to Home Assistant failing to mark a device as home. [Related Issue](https://github.com/home-assistant/home-assistant/issues/10507) From 15cf8299f5a1a8c5faeaf3fa6e63a71e1efae5fc Mon Sep 17 00:00:00 2001 From: cogneato Date: Wed, 7 Feb 2018 16:35:50 -0700 Subject: [PATCH 44/59] adding supported domains ref: https://github.com/home-assistant/home-assistant.github.io/issues/4036 Adds supported domains and default mappings. --- source/_components/google_assistant.markdown | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown index 350f07f1703..95ef0fff199 100644 --- a/source/_components/google_assistant.markdown +++ b/source/_components/google_assistant.markdown @@ -107,6 +107,19 @@ entity_config: type: string {% endconfiguration %} +### {% linkable_title Available domains %} +Currently, the following domains are available to be used with Google Assistant, listed with their default types: + +- group = switch (on/off) +- scene = scene (on) +- script = scene (on) +- switch = switch (on/off) +- fan = switch (on/off) +- light = light (on/off/brightness/rgb color/color temp) +- cover = switch (on/off/set position (brightness) ) +- media_player = switch (on/off/set volume (brightness) ) +- climate = thermostat (temperature setting) + It's very important that you use very long strings for `client_id` and `access_token`. Those are essentially the credentials to your Home Assistant instance. You can generate them with the following command: ```bash From af74298fddefca6f78e729aa848fa16080241318 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 8 Feb 2018 11:07:00 -0800 Subject: [PATCH 45/59] Bye disqus --- _config.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_config.yml b/_config.yml index 25bc8745bcd..286ea08babc 100644 --- a/_config.yml +++ b/_config.yml @@ -150,4 +150,6 @@ patch_version_notes: "#release-0621---january-30" # Minor release (Example #release-0431---april-25): # Date we moved to Discourse for comments -disqus_end_date: 2018-01-26 0:00:00 +# disqus_end_date: 2018-01-26 0:00:00 +# Disqus is adding gross ads, move all comments to discourse. +disqus_end_date: 2010-01-26 0:00:00 From f9802d1c0dde7a627c500eef2fe0ee4f65bc39af Mon Sep 17 00:00:00 2001 From: Daniel Perna Date: Thu, 8 Feb 2018 21:24:10 +0100 Subject: [PATCH 46/59] Added information for new sesame-option (#4550) --- source/_addons/configurator.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_addons/configurator.markdown b/source/_addons/configurator.markdown index 4b91a46b66d..c601025a126 100644 --- a/source/_addons/configurator.markdown +++ b/source/_addons/configurator.markdown @@ -49,6 +49,7 @@ Screenshot of the HASS Configurator. "banlimit": 0, "ignore_pattern": ["__pycache__"], "dirsfirst": false, + "sesame": "somesecretnobodycanguess" } ``` @@ -60,6 +61,7 @@ Screenshot of the HASS Configurator. - **banlimit** (*Optional*): Ban access from IPs after `banlimit` failed login attempts. The default value `0` disables this feature. Restart the add-on to clear the list of banned IP addresses. - **ignore_pattern** (*Optional*): Files and folders to ignore in the UI. - **dirsfirst** (*Optional*): List directories before files in the file browser. +- **sesame** (*Optional*): Secret token to dynamically allow access from the IP the request originates from. Open your bookmark https://hassio.yourdomain.com:8123/somesecretnobodycanguess while `allowed_networks` is set to `[]` and boom! Open Sesame! You can use the _Network status_ menu to revoke IP addresses for which access has been granted. ### {% linkable_title Embedding into Home-Assistant %} From b6258f5326d76bbe639e2382c5924ca494e404fc Mon Sep 17 00:00:00 2001 From: DubhAd Date: Thu, 8 Feb 2018 20:33:10 +0000 Subject: [PATCH 47/59] Added note about display in Overview (#4597) It's come up quite a few times, with people asking why some scripts have a toggle, and some don't. This is to add a little clarity about it (I'm **assuming** that `wait` also results in a toggle - it'd be good to get that verified). --- source/_components/script.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_components/script.markdown b/source/_components/script.markdown index 4b0fa016dce..52dd1110538 100644 --- a/source/_components/script.markdown +++ b/source/_components/script.markdown @@ -112,3 +112,9 @@ script: title: "{% raw %}{{ title }}{% endraw %}" message: "{% raw %}{{ message }}{% endraw %}" ``` + +### {% linkable_title In the Overview %} + +Scripts in the Overview panel will be displayed with an **ACTIVATE** button if the device has no `delay:` or `wait:` statement, and as a toggle switch if it has either of those. + +This is to enable you to stop a running script. From 08b3fee9bc6242d56faacb4a1c6049af790491fc Mon Sep 17 00:00:00 2001 From: JonnyaiR Date: Thu, 8 Feb 2018 21:46:30 +0100 Subject: [PATCH 48/59] Update switch.pilight.markdown to add variables and update links (#4522) * Update switch.pilight.markdown to add variables and update links The variables unitcode and programcode are missing from the variables-list, unitcode is mentioned in the text below but they should be listed as optional variables if they are in fact optional variables. furthermore the wiki-links to pilight are outdated, so i replaced the wiki.pilight.org links with manual.pilight,org links to their respective updated pages. * Update switch.pilight.markdown delete programcode * :pencil2: Small improvements --- source/_components/switch.pilight.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_components/switch.pilight.markdown b/source/_components/switch.pilight.markdown index 6bd48c3087f..8c803184a48 100644 --- a/source/_components/switch.pilight.markdown +++ b/source/_components/switch.pilight.markdown @@ -13,10 +13,9 @@ ha_release: 0.26 ha_iot_class: "Local Polling" --- - The `pilight` switch platform is issuing 433 MHz commands using [pilight](https://www.pilight.org/) to turn a 433 MHz device on or off. The Pilight Home Assistant hub has to be set up. -Additionally RF commands can be defined that trigger this switch to turn on and off. This allows you to also use the remote shipped with your 433 MHz switch without mixing up the Home Assistant states. You can even define several on/off commands, thus several RF remotes to toggle this switch. +Additionally, RF commands can be defined that trigger this switch to turn on and off. This allows you to also use the remote shipped with your 433 MHz switch without mixing up the Home Assistant states. You can even define several on/off commands, thus several RF remotes to toggle this switch. To be really sure that Home Assistant knows the actual state of your device it is recommended to use the RF remote with codes unknown to any of your 433 MHz devices. Thus you use the remote to trigger this switch to send the correct RF code to the device. @@ -42,20 +41,21 @@ Configuration variables: - **[entry]** (*Required*): Name of the command switch. Multiple entries are possible. - **on_code** (*Required*): The code to turn the device on. - **off_code** (*Required*): The code to turn the device off. - - **on_code_receive** (*Optional*): If given, this command will turn the switch on if it is received by Pilight. - - **off_code_receive** (*Optional*): If given, this command will turn the switch off if it is received by Pilight. + - **on_code_receive** (*Optional*): If given, this command will turn the switch on if it is received by pilight. + - **off_code_receive** (*Optional*): If given, this command will turn the switch off if it is received by pilight. Variables for the different codes (`on_code` and `off_code`): - **protocol** (*Required*): Protocol to use, eg. `intertechno_old` or `daycom`. - **systemcode** (*Optional*): The systemcode of the device. -- **unit** (*Optional*): The unit to use. +- **unit** (*Optional*): The unit to use (is equivalent to `pilight-send --unit`). +- **unitcode** (*Optional*): The unitcode to use (is equivalent to `pilight-send --unitcode`). - **id** (*Optional*): ID of the device - **state** (*Optional*): `'on'` or `'off'` has to be in apostrophes to be parsed correctly. - **'off'** (*Optional*): `1` or `0` - **'on'** (*Optional*): `1` or `0` -For possible code entries look at the [pilight API](https://www.pilight.org/development/api/). All commands allowed by [pilight-send](https://wiki.pilight.org/doku.php/psend) can be used. Which means that if for a certain protocol there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring. +For possible code entries, look at the [pilight API](https://manual.pilight.org/development/api.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring. Variables for the different receive codes (`on_code_receive` and `off_code_receive`): From 34c5baefa3067ad9e31ce08a4db635fef341632c Mon Sep 17 00:00:00 2001 From: DubhAd Date: Thu, 8 Feb 2018 20:48:06 +0000 Subject: [PATCH 49/59] Added note about error (#4559) Adding a specific note about the error that indicates the library is missing --- source/_docs/z-wave/installation.markdown | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index 1846468f829..63904021c44 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -232,3 +232,11 @@ sudo chmod g+rw /dev/ttyAMA0 ### {% linkable_title Device path changes %} If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it. + +### {% Unable to install python_openzwave %} + +If you're getting errors like: + + openzwave-embed/open-zwave-master/libopenzwave.a: No such file or directory + +Then the problem is that you're missing `libudev-dev`, please [install it](/docs/z-wave/installation/#linux-except-hassio). From f4ac7feb29711aa688df050f51cc118a7b473446 Mon Sep 17 00:00:00 2001 From: basst22778 Date: Thu, 8 Feb 2018 21:52:05 +0100 Subject: [PATCH 50/59] Added Hint to Unpack the file (#4584) Flashing will stop if you try to flash the .img.bz2 file directly on MacOS --- source/hassio/installation.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index be34f95a303..1a3113dffce 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -16,6 +16,8 @@ Hass.io images are available for all available Raspberry Pi and Intel NUC platfo - [Raspberry Pi 2][pi2] - [Raspberry Pi 3][pi3] - [Intel NUC][nuc] + +- Unpack the .bz2 File - Flash the downloaded image to an SD card using [Etcher]. - Optional - Setup the WiFi or static IP: On the SD-card, edit the `system-connections/resin-sample` file and follow the [ResinOS howto][resinos-network]. - Insert SD card to Raspberry Pi and turn it on. On first boot, it downloads the latest version of Home Assistant which takes ~20 minutes (slower/faster depending on the platform). From 23d3db267b2ffe2df9fdc6777ceba6aaffe15412 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 8 Feb 2018 15:36:44 -0800 Subject: [PATCH 51/59] Update python_script.markdown --- source/_components/python_script.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/python_script.markdown b/source/_components/python_script.markdown index 48bd6a1a149..a470ec3960c 100644 --- a/source/_components/python_script.markdown +++ b/source/_components/python_script.markdown @@ -44,4 +44,4 @@ hass.bus.fire(name, { "wow": "from a Python script!" }) } ``` -For [`python_script:` examples](/components/python_script/) visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum. +For examples, visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum. From 73b0e785fc91e89ce2f53bb61834b82a87eae158 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 8 Feb 2018 22:23:50 -0800 Subject: [PATCH 52/59] Add blog post disabling Disqus --- source/_docs/z-wave/installation.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index 63904021c44..4031738a7d2 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -233,7 +233,7 @@ sudo chmod g+rw /dev/ttyAMA0 If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it. -### {% Unable to install python_openzwave %} +### {% linkable_title Unable to install python_openzwave %} If you're getting errors like: From 12d5f0486fd39f849c5ae4f96edbc191cbb0cbc2 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 8 Feb 2018 22:24:04 -0800 Subject: [PATCH 53/59] Add blog post disabling Disqus --- .../2018-02-09-disabling-disqus.markdown | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 source/_posts/2018-02-09-disabling-disqus.markdown diff --git a/source/_posts/2018-02-09-disabling-disqus.markdown b/source/_posts/2018-02-09-disabling-disqus.markdown new file mode 100644 index 00000000000..980c0355213 --- /dev/null +++ b/source/_posts/2018-02-09-disabling-disqus.markdown @@ -0,0 +1,19 @@ +--- +layout: post +title: "Disabling Disqus comments" +description: "We have disabled Disqus comments on the site due to inappropriate advertisements." +date: 2018-02-09 01:00:00 +date_formatted: "February 9, 2018" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Community +--- + +Last week, starting with the release of [Home Assistant 0.62](https://home-assistant.io/blog/2018/01/27/release-62/), we switched to using our [community forums](https://community.home-assistant.io) for comments on our blog posts. By doing so, people are able to use their existing Home Assistant community accounts to comment on our blog posts and engage with one another. It has been easier for our users to stay in the loop with one less channel to keep track off. + +Previously, we were using the free version of Disqus to power comments on our blog. After the switch, to preserve the old comments, we decided to keep Disqus active on the older blog post pages. However, today we decided to turn them off. + +Today Disqus changed their advertisement strategy and turned on irrelevant graphical advertisement above and below the comment thread ([screenshot](https://twitter.com/balloob/status/961677501725421568)). On a phone, it took so much screen real estate that it filled the whole page with an advertisement for weight loss milk. Previously, Disqus had advertisements in an unobtrusive way: showing suggested content a visitor might also be interesed in. + +Today we have switched all blog posts to the new commenting system and are no longer serving Disqus comments. We are exploring ways to restore the old comments. From b6e9abe95d6ee5d05a3a6f7a859a1fdf662eb039 Mon Sep 17 00:00:00 2001 From: Mahasri Kalavala Date: Fri, 9 Feb 2018 11:39:38 -0500 Subject: [PATCH 54/59] Added additional details to the Developer Tools. More documentation to help clarify how the Developer Tools is and how it should be used. --- source/_docs/tools/dev-tools.markdown | 76 +++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index 1fbbe59fa3d..88e282683c9 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -24,3 +24,79 @@ Screenshot of Home Assistant's Developer Tools. | Templates | service developer tool icon | Renders templates | | Info | service developer tool icon | Details about Home Assistant | +## What can I do with Developer Tools? +The Developer Tools is meant for **all** (not just for the developers) to quickly try out things - like calling services, update states, raising events, and publish messages in mqtt…etc.). It is also a necessary tool for those who write custom automations and scripts by hand. The following describes each of the section in detail. + +{% linkable_title Services %} + +This section is used to call Services that are available in the ServiceRegistry. + +The list of services in the “Service” drop down are automatically populated based on the components that are found in the configuration, automation and script files. If a desired service does not exist, it means either the component is not configured properly or not defined in the configuration, automation or script files. + +When a Service is selected, and if that service requires an `entity_id` to be passed, the “Entity” drop down will automatically be populated with corresponding entities. + +A Service may also require additional input to be passed. It is commonly referred to as “service data”. The service data is only accepted in the JSON format, and it may be optional depending on the service. + +When an entity is selected from the Entity drop down, it automatically populates service data with the corresponding `entity_id`. The service data JSON can then be modified to pass additional \[optional\] parameters. The following is an illustration on how to call a `light.turn_on` service. + +To turn on a light bulb, use the following steps: +1. Select `light.turn_on` from the Service drop down +2. Select the entity (typically the light bulb) from the Entity drop down (if no entity_id is selected, it turns on ALL lights) +3. If an entity is selected, the service data is populated with basic JSON that will be passed to the service. An additional data can also be passed by updating the JSON as below. + +```json +{ + "entity_id": "light.bedroom", + "brightness": 255, + "rgb_color": [255, 0, 0] +} +``` +{% linkable_title States %} + +This section shows all the available entities, their corresponding state and the attribute values. The state and the attribute information is what Home Assistant sees at run time. To update the entity with a new state, or a new attribute value, click on the entity, scroll to the top, and modify the values, and click on “SET STATE” button. + +Note that this is the state representation of a device within Home Assistant. That means, it is what Home Assistant sees, and it does not communicate with the actual device in any manner. The updated information can still be used to trigger events, and state changes. To communicate with the actual device, it is recommended to call services in the services section above, instead of updating state. + +For ex: Changing the `light.bedroom` state from `off` to `on` does not turn on the light. If there is an automation that triggers on the `state` change of the `light.bedroom`, it will be triggered – even though the actual bulb has not turned on. Also, when the bulb state changes – the state information will be overridden. In other words, the changes that are made through the “States” section are temporary, and is recommended to use for testing purposes only. + +{% linkable_title Events %} + +This Events section is as basic as it can get. It does only one thing – fires events on the event bus. +To fire an event, simply type the name of the event, and pass the event data in JSON format. +For ex: To fire a custom event, enter the `event_type` as `event_light_state_changed` and the event data JSON as + +```json +{ "state":"on" } +``` + +If there is an automation that handles that event, it will be automatically triggered. See below: +```yaml +- alias: Capture Event + trigger: + platform: event + event_type: event_light_state_changed + action: + - service: notify.notify + data_template: + message: "Light is turned {{ trigger.event.data.state }}" +``` + +{% linkable_title Template Editor %} + +The Template Editor provides a way to test the template code quickly. When the Template Editor page is loaded, it comes with a sample template code that illustrates how the code can be written and tested. + +It has two sections, code goes on the left hand side, and the output is shown on the right hand side. The code can be removed and replaced, and when the page is loaded/refreshed, the default sample code will be loaded back. + +It is a good practice to test the template code in the template editor prior to putting it in automations and scripts. + +For more information about jinja2, visit [jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](https://home-assistant.io/topics/templating/) + + +{% linkable_title mqtt %} + +This section is only visible if the MQTT is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to [mqtt]( https://home-assistant.io/components/mqtt/) +Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button. + +{% linkable_title Info %} + +The Information tab simply provides information about the current installed version, additional links and credits. The tab also contains a section that shows `syslog` information, and the contents of `home-assistant.log` with an option to clear and refresh the logs. From de28af78b60003c48392ce9530afba8299210272 Mon Sep 17 00:00:00 2001 From: Marko Korhonen Date: Fri, 9 Feb 2018 21:40:55 +0200 Subject: [PATCH 55/59] Added single quotes around format value (#4609) The service wont work without these --- source/_components/tts.voicerss.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/tts.voicerss.markdown b/source/_components/tts.voicerss.markdown index a256b144dcc..612ae41082f 100644 --- a/source/_components/tts.voicerss.markdown +++ b/source/_components/tts.voicerss.markdown @@ -41,7 +41,7 @@ tts: api_key: 'XXXXX' language: 'de-de' codec: mp3 - format: 8khz_8bit_mono + format: '8khz_8bit_mono' ``` Please note, some media_players require a certain format. For example the Sonos requires a format of '44khz_16bit_stereo' From f5a18c25544421006db4272923885f97be61792d Mon Sep 17 00:00:00 2001 From: Robin Date: Fri, 9 Feb 2018 19:52:43 +0000 Subject: [PATCH 56/59] Add sharing images between HASS instances (#4607) * Add sharing images between HASS instances Adds description of how to share camera feeds between multiple home-assistant instances using the REST API. * Minor changes --- source/_components/camera.generic.markdown | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown index 3f99910e1c4..71a16ba40e6 100644 --- a/source/_components/camera.generic.markdown +++ b/source/_components/camera.generic.markdown @@ -68,3 +68,14 @@ camera: name: Some Image still_image_url: https://127.0.0.1:8123/local/your_image.png ``` + +### {% linkable_title Sharing a camera feed from one Home Assistant instance to another %} + +If you are running more than one Home Assistant instance (let's call them the 'host' and 'receiver' instances) you may wish to display the camera feed from the host instance on the receiver instance. You can use the [REST API](/developers/rest_api/#get-apicamera_proxycameraltentity_id) to access the camera feed on the host (IP address 127.0.0.5) and display it on the receiver instance by configuring the receiver with the the following: + +```yaml +camera: + - platform: generic + name: Host instance camera feed + still_image_url: https://127.0.0.5:8123/api/camera_proxy/camera.live_view +``` From 1247a72051b00dcc338805b49e5f2df85202ca62 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 9 Feb 2018 21:02:30 +0100 Subject: [PATCH 57/59] Minor updates --- source/_docs/z-wave/installation.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index 4031738a7d2..b110e34863e 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -189,7 +189,7 @@ Security Z-Wave devices require a network key before being added to the network An easy script to generate a random key: ```bash -cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' +$ cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' ``` ```yaml @@ -213,7 +213,7 @@ The first run after adding a device is when the `zwave` component will take time Sometimes the device may not be accessible and you'll get an error message upon startup about not being able to set up Z-Wave. Run the following command for your device path: ```bash -ls -l /dev/ttyAMA0 +$ ls -l /dev/ttyAMA0 ``` You should then see something like this: @@ -225,15 +225,15 @@ crw-rw---- 1 root dialout 204, 64 Apr 1 12:34 /dev/ttyAMA0 The important pieces are the first piece `crw-rw----` and the group `dialout`. If those are different then, for your device path, run: ```bash -sudo chgrp dialout /dev/ttyAMA0 -sudo chmod g+rw /dev/ttyAMA0 +$ sudo chgrp dialout /dev/ttyAMA0 +$ sudo chmod g+rw /dev/ttyAMA0 ``` ### {% linkable_title Device path changes %} If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it. -### {% linkable_title Unable to install python_openzwave %} +### {% linkable_title Unable to install Python Openzwave %} If you're getting errors like: From d797d4dd48a556bc955532c04ece0ad32ec381af Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maido=20K=C3=A4=C3=A4ra?= Date: Fri, 9 Feb 2018 23:09:32 +0200 Subject: [PATCH 58/59] Incorrect event name (#4540) * Incorrect event name event_light_state_changed is the correct event in the configuration example * Put back typo fix --- source/_docs/scripts.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index f630d283d4d..5c39a604ab0 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -139,7 +139,7 @@ event_data_template: ### {% linkable_title Raise and Consume Custom Events %} -The following automation shows how to raise a custom event called `event_light_turned_on` with `entity_id` as the event data. The action part could be inside a script or an automation. +The following automation shows how to raise a custom event called `event_light_state_changed` with `entity_id` as the event data. The action part could be inside a script or an automation. {% raw %} ```yaml @@ -155,7 +155,7 @@ The following automation shows how to raise a custom event called `event_light_t ``` {% endraw %} -The following automation shows how to capture the custom event `event_light_turned_on`, and retrieve corresponding `entity_id` that was passed as the event data. +The following automation shows how to capture the custom event `event_light_state_changed`, and retrieve corresponding `entity_id` that was passed as the event data. {% raw %} ```yaml From 3dec0a3a585e511e2194e891aeabf3812b121ca6 Mon Sep 17 00:00:00 2001 From: Mahasri Kalavala Date: Fri, 9 Feb 2018 16:56:34 -0500 Subject: [PATCH 59/59] added service call example (#4606) * added service call example * Minor changes --- source/_components/python_script.markdown | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/source/_components/python_script.markdown b/source/_components/python_script.markdown index a470ec3960c..5e03edc16c0 100644 --- a/source/_components/python_script.markdown +++ b/source/_components/python_script.markdown @@ -44,4 +44,21 @@ hass.bus.fire(name, { "wow": "from a Python script!" }) } ``` -For examples, visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum. +## {% linkable_title Calling Services %} + +The following example shows how to call a service from `python_script`. This script takes two parameters: `entity_id` (required), `rgb_color` (optional) and calls `light.turn_on` service by setting the brightness value to `255`. + +```python +entity_id = data.get('entity_id') +rgb_color = data.get('rgb_color', [255, 255, 255]) +if entity_id is not None: + service_data = {'entity_id': entity_id, 'rgb_color': rgb_color, 'brightness': 255 } + hass.services.call('light', 'turn_on', service_data, False) +``` +The above `python_script` can be called using the following JSON as an input. + +```json +{"entity_id": "light.bedroom", "rgb_color": [255, 0, 0] } +``` + +For more examples, visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum.