From be7aaaa7ad3825374b6e89370dbd6b1352176948 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 27 Dec 2018 23:07:41 +0100 Subject: [PATCH 01/49] Update link --- source/_docs/backend/database.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/backend/database.markdown b/source/_docs/backend/database.markdown index 81a5226b41b..c8266477d4e 100644 --- a/source/_docs/backend/database.markdown +++ b/source/_docs/backend/database.markdown @@ -124,4 +124,4 @@ The `VACUUM` command cleans your database. sqlite> VACUUM; ``` -For a more interactive way of working with the database, checkout our [Jupyter notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/). +For a more interactive way of working with the database, check the [Data Science Portal](https://data.home-assistant.io/). From f348321e677595c8d86907cf75989daf1a6638ab Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 27 Dec 2018 23:20:50 +0100 Subject: [PATCH 02/49] Add data science portal blog post --- .../2018-12-27-data-science-portal.markdown | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 source/_posts/2018-12-27-data-science-portal.markdown diff --git a/source/_posts/2018-12-27-data-science-portal.markdown b/source/_posts/2018-12-27-data-science-portal.markdown new file mode 100644 index 00000000000..d5af22fc211 --- /dev/null +++ b/source/_posts/2018-12-27-data-science-portal.markdown @@ -0,0 +1,27 @@ +--- +layout: post +title: "Launched: Data Science Portal" +description: "Learn about your data that is stored and how to get started exploring it." +date: 2018-12-27 00:01:00 +date_formatted: "December 27, 2018" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Announcements +--- + +Today we are launching our brand new [data science portal][post] to teach you how you can learn from your own smart home data. Learn what data Home Assistant stores locally and learn to explore your data. In 15 minutes, you will set up a local data science environment and are running reports on your own data. + +We have worked hard on a smooth experience. Single click to set up a local data science environment powered by Jupyter. Pre-installed with our Getting Started notebook for Home Assistant, automatically connects to your database and generates reports with a single click. + +All of this is powered by the new JupyterLab hass.io add-on by [@frenck] and the new HASS Data Detective Python package by [@robmarkcole]. + +Today is only the start. We will continue to develop the data tools for Home Assistant. It’s our goal to make Home Assistant the easiest platform to use for data scientists interested in home automation. + +- [Launch blogpost][post] +- [Data Science Portal][portal] + +[post]: https://data.home-assistant.io/blog/2018/12/27/data-science-for-home-assistant-launched +[portal]: https://data.home-assistant.io +[@robmarkcole]: https://github.com/frenck +[@frenck]: https://github.com/frenck From 7707a0968648533babccc36b6c7e97942f36f3f3 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 27 Dec 2018 23:21:45 +0100 Subject: [PATCH 03/49] Update footer --- source/_includes/custom/footer.html | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_includes/custom/footer.html b/source/_includes/custom/footer.html index ad8df9a0553..911b66602cd 100644 --- a/source/_includes/custom/footer.html +++ b/source/_includes/custom/footer.html @@ -14,6 +14,7 @@
From 6d0f715812765dc8ea5431167047903a81dd4443 Mon Sep 17 00:00:00 2001 From: Steve Scott <36101200+thewishy@users.noreply.github.com> Date: Fri, 28 Dec 2018 20:45:09 +0000 Subject: [PATCH 04/49] Clarified offset for workday sensor (#7967) * Clarified offset Added indication of direction for offset. It look a little experimentation to work this out, so suspect this will help others * Minor change --- source/_components/binary_sensor.workday.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/binary_sensor.workday.markdown b/source/_components/binary_sensor.workday.markdown index 1427b7e0ad4..7a7716d3086 100644 --- a/source/_components/binary_sensor.workday.markdown +++ b/source/_components/binary_sensor.workday.markdown @@ -65,7 +65,7 @@ excludes: type: list default: "[sat, sun, holiday]" days_offset: - description: Set days offset. + description: Set days offset (e.g., -1 for yesterday, 1 for tomorrow). required: false type: integer default: 0 From 731771ea50585b59c2a002f6e420f21c82a858fa Mon Sep 17 00:00:00 2001 From: DubhAd Date: Fri, 28 Dec 2018 20:45:55 +0000 Subject: [PATCH 05/49] Update to reflect that https should be specified (#7971) Update to reflect that https should be specified --- source/_addons/duckdns.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown index 4626bd7617e..d1726880996 100644 --- a/source/_addons/duckdns.markdown +++ b/source/_addons/duckdns.markdown @@ -55,7 +55,7 @@ Use the following configuration in Home Assistant to use the generated certifica ```yaml http: - base_url: my-domain.duckdns.org:8123 + base_url: https://my-domain.duckdns.org:8123 ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem ``` From 98adcb9c269026a94e2cd869e2c1e8edccf74f05 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Fri, 28 Dec 2018 20:47:01 +0000 Subject: [PATCH 06/49] Remove embedded video (#7972) The video is from 0.73 beta, it's horribly horribly out of date. Either it needs to be kept updated, or we should remove it to avoid confusing people. --- source/lovelace/index.markdown | 4 ---- 1 file changed, 4 deletions(-) diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index f849d8af8f9..188ee6340d3 100644 --- a/source/lovelace/index.markdown +++ b/source/lovelace/index.markdown @@ -12,10 +12,6 @@ redirect_from: /components/lovelace/ Lovelace is the name of the Home Assistant user interface. It is a fast, customizable and powerful way for users to manage their homes, working both on mobile and desktop. -
- -
- Lovelace is not the default UI just yet, but we're really close. Once you are ready to start using Lovelace UI as your main user interface, click on info, the "i" icon under 'Developer Tools" in the Home Assistant side-bar. Next, locate >>Set Lovelace as default page on this device<< under the Home Assistant version information and click it. Note that this is a per-device setting and will need to be changed on each device you access the UI from. From b1cb93b8ba16a7543106419d6f0a8e91f80326d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Sch=C3=BCtz?= Date: Sat, 29 Dec 2018 15:47:58 +0100 Subject: [PATCH 07/49] Package python3-dev is required, not python2-dev (#7978) --- source/_docs/installation/virtualenv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index e9427bba34f..1238dcaa6e3 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -14,7 +14,7 @@ If you already have Python 3.5.3 or later installed, you can easily give Home As It's recommended when installing Python packages that you use a [virtual environment](https://docs.python.org/3.5/library/venv.html#module-venv). This will make sure that your Python installation and Home Assistant installation won't impact one another. The following steps will work on most UNIX like systems. -_(If you're on a Debian based system, you will need to install Python virtual environment support using `apt-get install python3-pip python3-venv`. You may also need to install development libraries using `apt-get install build-essential libssl-dev libffi-dev python-dev`.)_ +_(If you're on a Debian based system, you will need to install Python virtual environment support using `apt-get install python3-pip python3-venv`. You may also need to install development libraries using `apt-get install build-essential libssl-dev libffi-dev python3-dev`.)_

It is recommended to use the [advanced guide](/docs/installation/raspberry-pi/) which allows for the installation to run as a `homeassistant` user. The steps below may be shorter but some users find difficulty when applying updates and may run into issues. From 917bddc3bfabb2f90c9c2262eca2abdf671a7ff5 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 29 Dec 2018 16:12:01 +0100 Subject: [PATCH 08/49] Remove name option --- source/_components/luftdaten.markdown | 5 ----- 1 file changed, 5 deletions(-) diff --git a/source/_components/luftdaten.markdown b/source/_components/luftdaten.markdown index 276c10c501e..fd42e5f77a3 100644 --- a/source/_components/luftdaten.markdown +++ b/source/_components/luftdaten.markdown @@ -45,11 +45,6 @@ sensor_id: description: The ID of the sensor. required: true type: string -name: - description: Name of the sensor to use in the frontend. - required: false - default: Luftdaten Sensor - type: string show_on_map: description: Option to show the position of the sensor on the map. required: optional From 526afee562e7e42a6d2372ed2300f2284f36f2c6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 29 Dec 2018 16:42:44 +0100 Subject: [PATCH 09/49] Minor changes --- .../binary_sensor.workday.markdown | 27 +++++++------------ 1 file changed, 10 insertions(+), 17 deletions(-) diff --git a/source/_components/binary_sensor.workday.markdown b/source/_components/binary_sensor.workday.markdown index 7a7716d3086..f9526ed891a 100644 --- a/source/_components/binary_sensor.workday.markdown +++ b/source/_components/binary_sensor.workday.markdown @@ -14,19 +14,16 @@ ha_release: 0.41 ha_qa_scale: internal --- -The `workday` binary sensor indicates, whether the current day is a workday or -not. It allows specifying, which days of the week counts as workdays and also -uses the python module [holidays](https://pypi.python.org/pypi/holidays) -to incorporate information about region-specific public holidays. +The `workday` binary sensor indicates, whether the current day is a workday or not. It allows specifying, which days of the week counts as workdays and also +uses the python module [holidays](https://pypi.python.org/pypi/holidays) to incorporate information about region-specific public holidays. + +## {% linkable_title Setup %} + +Check the [country list](https://github.com/dr-prodigy/python-holidays#available-countries) for available province. ## {% linkable_title Configuration %} -Check the -[country list](https://github.com/dr-prodigy/python-holidays#available-countries) -for available province. - -To enable the `workday` sensor in your installation, -add the following to your `configuration.yaml` file: +To enable the `workday` sensor in your installation, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -44,14 +41,11 @@ name: default: Workday Sensor country: description: > - Country code according to - [holidays](https://pypi.org/project/holidays/) notation. + Country code according to [holidays](https://pypi.org/project/holidays/) notation. required: true type: string province: - description: > - Province code according to - [holidays](https://pypi.org/project/holidays/) notation. + description: Province code according to [holidays](https://pypi.org/project/holidays/) notation. required: false type: string workdays: @@ -102,7 +96,6 @@ automation: ```

-Please remember that [as explained here][devices] you can only have a single `automation:` entry. Add the automation to your existing automations. +Please remember that [as explained here](https://www.home-assistant.io/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.

-[devices]: https://www.home-assistant.io/docs/configuration/devices/ From b7fbe7862a351bfdee34907b474971ab8172d450 Mon Sep 17 00:00:00 2001 From: Jonathan Herlin Date: Sat, 29 Dec 2018 16:44:02 +0100 Subject: [PATCH 10/49] Update device_tracker.markdown (#7974) hide_if_away does not take "no" as a valid argument according to the rest of the docs. Let's change it to false where it was previously no --- source/_components/device_tracker.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown index d3483e297c2..b2257e80078 100644 --- a/source/_components/device_tracker.markdown +++ b/source/_components/device_tracker.markdown @@ -75,7 +75,7 @@ devicename: mac: EA:AA:55:E7:C6:94 picture: https://www.home-assistant.io/images/favicon-192x192.png track: yes - hide_if_away: no + hide_if_away: false ```

@@ -106,7 +106,7 @@ USERNAME_DEVICE_ID: picture: https://www.home-assistant.io/images/favicon-192x192.png gravatar: test@example.com track: yes - hide_if_away: no + hide_if_away: false ``` If you want to track whether either your GPS based tracker or your local network tracker, identify you as being at home, use [a group](/components/group/) instead. From a73e35eb6ab10f5bda30763d7602fedb598d64d3 Mon Sep 17 00:00:00 2001 From: sorinyo2004 <41705642+sorinyo2004@users.noreply.github.com> Date: Sat, 29 Dec 2018 17:44:33 +0200 Subject: [PATCH 11/49] Added example for the tap_action (#7969) --- source/_lovelace/glance.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/_lovelace/glance.markdown b/source/_lovelace/glance.markdown index 35d20b849c9..49c46ceec03 100644 --- a/source/_lovelace/glance.markdown +++ b/source/_lovelace/glance.markdown @@ -155,4 +155,7 @@ Define entities as objects and apply a custom name: - light.ceiling_lights - switch.ac - lock.kitchen_door + - entity: switch.wall_plug_switch + tap_action: + action: toggle ``` From 80969ef77435dfef748468269c11bdb50d921d56 Mon Sep 17 00:00:00 2001 From: Lance Moss <3811110+lmoss2004@users.noreply.github.com> Date: Sat, 29 Dec 2018 07:45:20 -0800 Subject: [PATCH 12/49] update to command names (#7963) I have submitted a pull request on the motorparts python API. URLS and commands have changed on morpar.com. Once that is merged then this will need changed. --- source/_components/sensor.mopar.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.mopar.markdown b/source/_components/sensor.mopar.markdown index ab620c56d9e..fc3396ab434 100644 --- a/source/_components/sensor.mopar.markdown +++ b/source/_components/sensor.mopar.markdown @@ -56,7 +56,7 @@ pin: Call the `sensor.mopar_remote_command` service to perform a remote command on your vehicle. - **vehicle_index** (*Required*): `vehicle_index` attribute found on sensor. -- **command** (*Required*): One of `lock/unlock/engineon/engineoff/horn`. +- **command** (*Required*): One of `LOCK/UNLOCK/START/STOP/HORN_LIGHT`. Example data: From 8743101e62c0da7278151d6803d2f83697792259 Mon Sep 17 00:00:00 2001 From: Purplecarrot Date: Sat, 29 Dec 2018 23:14:28 +0000 Subject: [PATCH 13/49] Tested and working fine with Marantz M-CR510 (#7983) --- source/_components/media_player.denonavr.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/media_player.denonavr.markdown b/source/_components/media_player.denonavr.markdown index 14aedd8ee0f..8a8ba032373 100644 --- a/source/_components/media_player.denonavr.markdown +++ b/source/_components/media_player.denonavr.markdown @@ -25,6 +25,7 @@ Supported devices: - Denon AVR-2312CI - Denon AVR-3311CI - Denon AVR-4810 +- Marantz M-CR510 - Marantz M-CR603 - Marantz M-RC610 - Marantz SR5008 From 8f9ccb2337ac48678c3f0c934d607dfd4d4f3bad Mon Sep 17 00:00:00 2001 From: John Shahawy Date: Sun, 30 Dec 2018 04:12:06 -0500 Subject: [PATCH 14/49] change offset to after_offset so validation will pass (#7975) --- source/_cookbook/automation_for_rainy_days.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_cookbook/automation_for_rainy_days.markdown b/source/_cookbook/automation_for_rainy_days.markdown index 7ce7c46b16a..a6e3b0bb8b7 100644 --- a/source/_cookbook/automation_for_rainy_days.markdown +++ b/source/_cookbook/automation_for_rainy_days.markdown @@ -44,7 +44,7 @@ And then of course turn off the lamp when it stops raining but only if it's with condition: - condition: sun after: 'sunset' - offset: '-01:00:00' + after_offset: '-01:00:00' action: service: light.turn_off entity_id: light.couch_lamp From e90e25c3f450bfb831dc62212e13e30a42a63b12 Mon Sep 17 00:00:00 2001 From: ctborg Date: Sun, 30 Dec 2018 07:48:32 -0500 Subject: [PATCH 15/49] Update sensor.bme680.markdown (#7986) --- source/_components/sensor.bme680.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/sensor.bme680.markdown b/source/_components/sensor.bme680.markdown index 814b276edce..f1661ac364f 100644 --- a/source/_components/sensor.bme680.markdown +++ b/source/_components/sensor.bme680.markdown @@ -154,12 +154,16 @@ customize: sensor.bme680_sensor_humidity: icon: mdi:water friendly_name: Humidity + device_class: humidity + unit_of_measurement: "%" sensor.bme680_sensor_pressure: icon: mdi:gauge friendly_name: Pressure sensor.bme680_sensor_air_quality: icon: mdi:blur friendly_name: Air Quality + device_class: pm25 + unit_of_measurement: "%" ``` To create a group, add the following to your `group` section. From 85817018031c359bcd25fb64af99db9303d9fee1 Mon Sep 17 00:00:00 2001 From: Robert Date: Sun, 30 Dec 2018 14:37:24 +0100 Subject: [PATCH 16/49] Add note for fixing cloudmqtt certificate errors (#7842) See https://community.home-assistant.io/t/cloudmqtt-issues-expired-certificate/73030/4 --- source/_docs/mqtt/broker.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown index cfff837d8ea..2fd03ed181b 100644 --- a/source/_docs/mqtt/broker.markdown +++ b/source/_docs/mqtt/broker.markdown @@ -173,4 +173,7 @@ mqtt:

Home Assistant will automatically load the correct certificate if you connect to an encrypted channel of CloudMQTT (port range 20000-30000).

+

+If you experience an error message like `Failed to connect due to exception: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed`, then add `certificate: auto` to your broker configuration and restart Home Assistant. +

From ca41a82015ffbc83b5431115cbf65efcda979f65 Mon Sep 17 00:00:00 2001 From: Bo Date: Sun, 30 Dec 2018 14:40:40 +0100 Subject: [PATCH 17/49] Clarify conditional executing in script (#7782) --- source/_docs/scripts.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index 9d8b8a218b6..fccdd277509 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -42,9 +42,10 @@ The most important one is the action to call a service. This can be done in vari ### {% linkable_title Test a Condition %} -While executing a script you can add a condition to stop further execution. When a condition does not return `true`, the script will finish. There are many different conditions which are documented at the [conditions page]. +While executing a script you can add a condition to stop further execution. When a condition does not return `true`, the script will stop executing. There are many different conditions which are documented at the [conditions page]. ```yaml +# If paulus is home, continue to execute the script below these lines - condition: state entity_id: device_tracker.paulus state: 'home' From 291909389c7d2275e6125b392085f64e91ec8686 Mon Sep 17 00:00:00 2001 From: Stuart <34009231+schford@users.noreply.github.com> Date: Sun, 30 Dec 2018 14:12:30 +0000 Subject: [PATCH 18/49] Update climate.nest.markdown (#7740) * Update climate.nest.markdown Added note about European Nest Thermostat e not working. * Update source/_components/climate.nest.markdown Co-Authored-By: schford <34009231+schford@users.noreply.github.com> * :pencil2: Whitespaces * :pencil2: More whitespaces --- source/_components/climate.nest.markdown | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/source/_components/climate.nest.markdown b/source/_components/climate.nest.markdown index 4881390d88e..70201a0444d 100644 --- a/source/_components/climate.nest.markdown +++ b/source/_components/climate.nest.markdown @@ -12,14 +12,12 @@ ha_category: Climate ha_iot_class: "Cloud Push" --- - The `nest` climate platform lets you control a thermostat from [Nest](https://nest.com).

-You must have the [Nest component](/components/nest/) configured to use these sensors. The `nest` climate component will automatically be setup when you do. +You must have the [Nest component](/components/nest/) configured to use these sensors. The `nest` climate component will automatically be setup when you do. Please note due to limitations with the European Nest Thermostat E, integration with Home Assistant for that thermostat is not possible.

- From 3e60d3ec82341509a9751fe6481e4d10fcf9db1c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 18:35:01 +0100 Subject: [PATCH 19/49] Fix token var (#7989) --- source/_components/splunk.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_components/splunk.markdown b/source/_components/splunk.markdown index 06eefe86577..049cb38e444 100644 --- a/source/_components/splunk.markdown +++ b/source/_components/splunk.markdown @@ -14,12 +14,14 @@ ha_release: 0.13 The `splunk` component makes it possible to log all state changes to an external [Splunk](http://splunk.com/) database using Splunk's HTTP Event Collector (HEC) feature. You can either use this alone, or with the Home Assistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3. +## {% linkable_title Configuration %} + To use the `splunk` component in your installation, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry splunk: - token: B4415DFF-683C-5C6C-3994-4F6D4A5DB03A + token: YOUR_SPLUNK_TOKEN ``` {% configuration %} @@ -28,7 +30,7 @@ token: required: true type: string host: - description: "IP address or host name of your Splunk host e.g., 192.168.1.10." + description: "IP address or host name of your Splunk host, e.g., 192.168.1.10." required: false default: localhost type: string From 353af943b275039c76b2463a124b2f133335951c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 18:36:50 +0100 Subject: [PATCH 20/49] Add setup section (#7991) --- source/_components/sensor.tautulli.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.tautulli.markdown b/source/_components/sensor.tautulli.markdown index 3bb5741e4a4..f78b4926c50 100644 --- a/source/_components/sensor.tautulli.markdown +++ b/source/_components/sensor.tautulli.markdown @@ -13,7 +13,7 @@ ha_release: 0.82 ha_iot_class: "Local Polling" --- -The `Tautulli` sensor platform will monitor activity on a given [Tautulli Server][tautulli]. It will create a sensor that shows the number of currently active streams as the state. If you click the sensor for more details it will show you more statistics, the following stats are available by default: +The `tautulli` sensor platform will monitor activity on a given [Tautulli Server][tautulli]. It will create a sensor that shows the number of currently active streams as the state. If you click the sensor for more details it will show you more statistics, the following stats are available by default: - LAN bandwidth - Number of direct plays @@ -28,7 +28,11 @@ The `Tautulli` sensor platform will monitor activity on a given [Tautulli Server More user statistics can be added with the `monitored_variables` configuration option, this will add one attribute per user in addition to the users current `activity`. -To find your `api_key` open the Tautulli web interface and navigate to `Settings` and then to `Web interface`, the `api_key` will be at the bottom of that page. +## {% linkable_title Setup %} + +To find your `api_key` open the Tautulli web interface and navigate to `Settings` and then to `Web interface`, the `api_key` will be at the bottom of that page. + +## {% linkable_title Configuration %} If you want to enable this sensor, add the following lines to your `configuration.yaml`: From 81d8d6bfbb96f36b75b25840403d781624b5e945 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 18:37:53 +0100 Subject: [PATCH 21/49] Minor changes (#7990) --- source/_components/fibaro.markdown | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/source/_components/fibaro.markdown b/source/_components/fibaro.markdown index b6b570c2108..a2f83455d4a 100644 --- a/source/_components/fibaro.markdown +++ b/source/_components/fibaro.markdown @@ -17,11 +17,11 @@ redirect_from: The [Fibaro](http://fibaro.com) hub is a controller mainly connecting to Z-Wave devices. -Switches, Lights (including Dimmers), Locks, Sensors, Binary sensors and Covers are supported - and will be automatically added when HA connects to your Fibaro controller. +Switches, lights (including Dimmers), locks, sensors, binary sensors and covers are supported and will be automatically added when Home Assistant connects to your Fibaro controller. ## {% linkable_title Configuration %} -To use Fibaro devices in your installation, add the following to your configuration.yaml file using the IP and port number of your Fibaro controller: +To use Fibaro devices in your installation, add the following to your `configuration.yaml` file using the IP and port number of your Fibaro controller: ```yaml fibaro: @@ -44,13 +44,14 @@ password: required: true type: string plugins: - description: Whether to import plugin-generated devices from Fibaro HomeCenter, such as Netatmo and Sonos devices, etc. Default is false. + description: Whether to import plugin-generated devices from Fibaro HomeCenter, such as Netatmo and Sonos devices, etc. required: false type: bool + default: false {% endconfiguration %}

- It is recommended to assign a static IP address to your Fibaro Controller. This ensures that it won't change IP addresses, so you won't have to change the 'url' if the controller reboots and comes up with a different IP address. See your router's manual for details on how to set this up. If you need the MAC address of your Fibaro, check the label on the bottom. + It is recommended to assign a static IP address to your Fibaro controller. This ensures that it won't change its IP address, so you won't have to change the `url` if the controller reboots and comes up with a different IP address. See your router's manual for details on how to set this up. If you need the MAC address of your Fibaro, check the label on the bottom.

### {% linkable_title Using Z-Wave devices in automation %} From 011e423d2ef7e7104b3550e5fd3e0993ed97e49c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 18:38:41 +0100 Subject: [PATCH 22/49] Various updates (names and style) (#7988) * Various updates (names and style) * Fix typo --- source/_components/alarm_control_panel.lupusec.markdown | 4 ++-- source/_components/binary_sensor.lupusec.markdown | 6 +++--- source/_components/lupusec.markdown | 8 +++++--- source/_components/switch.lupusec.markdown | 4 ++-- 4 files changed, 12 insertions(+), 10 deletions(-) diff --git a/source/_components/alarm_control_panel.lupusec.markdown b/source/_components/alarm_control_panel.lupusec.markdown index 432a7da93ae..55b7ffeada5 100644 --- a/source/_components/alarm_control_panel.lupusec.markdown +++ b/source/_components/alarm_control_panel.lupusec.markdown @@ -13,6 +13,6 @@ ha_release: 0.83 ha_iot_class: "Local Polling" --- -The `LUPUS-Electronics` security control panel platform allows you to control your [Lupusec](https://www.lupus-electronics.de) devices. +The `lupusec` security control panel platform allows you to control your [Lupusec](https://www.lupus-electronics.de) devices. -The requirement is that you have setup your [Lupusec component](/components/lupusec/). The alarm control panel is automatically added to your hass UI. \ No newline at end of file +The requirement is that you have setup your [Lupusec component](/components/lupusec/). The alarm control panel is automatically added to the Home Assistant frontend. diff --git a/source/_components/binary_sensor.lupusec.markdown b/source/_components/binary_sensor.lupusec.markdown index 4367bde3b0d..f8c98f4be34 100644 --- a/source/_components/binary_sensor.lupusec.markdown +++ b/source/_components/binary_sensor.lupusec.markdown @@ -13,8 +13,8 @@ ha_release: 0.83 ha_iot_class: "Local Polling" --- -The `LUPUS-Electronics` security control panel platform allows you to control your [Lupusec](https://www.lupus-electronics.de) devices. +The `lupusec` security control panel platform allows you to control your [Lupusec](https://www.lupus-electronics.de) devices. -This component will add `door contacts` and `window contacts` to your home-assistant setup +This platform will add `door contacts` and `window contacts` to your Home Assistant setup. -For the sensors to work you have to setup your [Lupusec component](/components/lupusec/). \ No newline at end of file +For the sensors to work you have to setup your [`lupusec` component](/components/lupusec/). diff --git a/source/_components/lupusec.markdown b/source/_components/lupusec.markdown index d26b74319ea..931386a2fe6 100644 --- a/source/_components/lupusec.markdown +++ b/source/_components/lupusec.markdown @@ -13,14 +13,16 @@ ha_release: 0.83 ha_iot_class: "Local Polling" --- -The `Lupusec` component allows the user to integrate their Lupusec alarm control panel and ultimately all connected sensors and other devices. For more information about the LUPUS-Electronics security system please visit their [website](https://www.lupus-electronics.de). +The `lupusec` component allows the user to integrate their Lupusec alarm control panel and ultimately all connected sensors and other devices. For more information about the LUPUS-Electronics security system please visit their [website](https://www.lupus-electronics.de). -The following devices are supported by the underlying `lupupy` python library and integrated into hass. +The following devices are supported by the underlying `lupupy` Python library and integrated into Home Assistant. - [Alarm Control Panel](/components/alarm_control_panel.lupusec/): Displays the alarm status and controls arming, disarming and home modus. - [Binary Sensor](/components/binary_sensor.lupusec/): Displays the status of binary sensors. Currently only Door and window sensors are supported. - [Switch](/components/switch.lupusec/): Turn off and on your Lupus power switches. +## {% linkable_title Configuration %} + To use Lupusec devices in your installation, add the following `lupusec` section to your `configuration.yaml` file: ```yaml @@ -48,4 +50,4 @@ name: description: Name for your Lupusec panel. required: false type: string -{% endconfiguration %} \ No newline at end of file +{% endconfiguration %} diff --git a/source/_components/switch.lupusec.markdown b/source/_components/switch.lupusec.markdown index f526e35da2a..32c20a59b49 100644 --- a/source/_components/switch.lupusec.markdown +++ b/source/_components/switch.lupusec.markdown @@ -13,8 +13,8 @@ ha_release: 0.83 ha_iot_class: "Local Polling" --- -The `LUPUS-Electronics` security control panel platform allows you to control your [Lupusec](https://www.lupus-electronics.de) devices. +The `lupusec` security control panel platform allows you to control your [Lupusec](https://www.lupus-electronics.de) devices. This component will automatically add `Power Switches` configured in your Lupusec control panel. -For the switches to work you have to setup your [Lupusec component](/components/lupusec/). +For the switches to work you have to setup your [`lupusec` component](/components/lupusec/). From 572ff699322c5a13e30f99a94727dbc4fc4eefa0 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:06:54 +0100 Subject: [PATCH 23/49] Fix platform --- .../_components/binary_sensor.mqtt.markdown | 79 ++++++------------- 1 file changed, 24 insertions(+), 55 deletions(-) diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown index 132c59298e0..7324e5545c6 100644 --- a/source/_components/binary_sensor.mqtt.markdown +++ b/source/_components/binary_sensor.mqtt.markdown @@ -13,28 +13,15 @@ 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 `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. +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`. ## {% linkable_title Configuration %} -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` +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 sensor 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, @@ -48,15 +35,15 @@ binary_sensor: ``` {% configuration %} +state_topic: + description: The MQTT topic subscribed to receive sensor values. + required: true + type: string name: description: The name of the binary sensor. required: false type: string default: MQTT Binary Sensor -state_topic: - description: The MQTT topic subscribed to receive sensor values. - required: true - type: string payload_on: description: The payload that represents the on state. required: false @@ -68,11 +55,7 @@ payload_off: type: string default: "OFF" availability_topic: - description: > - The MQTT topic subscribed to receive birth and LWT messages from the MQTT - device. If `availability_topic` is not defined, the binary sensor availability - state will always be `available`. If `availability_topic` is defined, - the binary sensor availability state will be `unavailable` by default. + description: "The MQTT topic subscribed to receive birth and LWT messages from the MQTT device. If `availability_topic` is not defined, the binary sensor availability state will always be `available`. If `availability_topic` is defined, the binary sensor availability state will be `unavailable` by default." required: false type: string payload_available: @@ -91,21 +74,15 @@ qos: type: integer default: 0 unique_id: - description: > - An ID that uniquely identifies this sensor. If two sensors have - the same unique ID, Home Assistant will raise an exception. + description: An ID that uniquely identifies this sensor. If two sensors have the same unique ID, Home Assistant will raise an exception. required: false type: string device_class: - description: > - The [type/class](/components/binary_sensor/) of - the sensor to set the icon in the frontend. + description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend. required: false type: string value_template: - description: > - Defines a [template](/docs/configuration/templating/#processing-incoming-data) - to extract a value from the payload. + description: Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload. required: false type: string force_update: @@ -114,36 +91,36 @@ force_update: type: boolean default: False off_delay: - description: For sensors that only sends ‘On’ state updates, this variable sets a delay in seconds after which the sensor state will be updated back to ‘Off’. + description: "For sensors that only sends `On` state updates, this variable sets a delay in seconds after which the sensor state will be updated back to `Off`." required: false type: integer device: - description: 'Information about the device this binary sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set.' + description: "Information about the device this binary sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set." required: false type: map keys: identifiers: - description: 'A list of IDs that uniquely identify the device. For example a serial number.' + description: A list of IDs that uniquely identify the device. For example a serial number. required: false type: list, string connections: - description: 'A list of connections of the device to the outside world as a list of tuples `[connection_type, connection_identifier]`. For example the MAC address of a network interface: `"connections": [["mac", "02:5b:26:a8:dc:12"]]`.' + description: "A list of connections of the device to the outside world as a list of tuples `[connection_type, connection_identifier]`. For example the MAC address of a network interface: `'connections': ['mac', '02:5b:26:a8:dc:12']`." required: false type: list, tuple manufacturer: - description: 'The manufacturer of the device.' + description: The manufacturer of the device. required: false type: string model: - description: 'The model of the device.' + description: The model of the device. required: false type: string name: - description: 'The name of the device.' + description: The name of the device. required: false type: string sw_version: - description: 'The firmware version of the device.' + description: The firmware version of the device. required: false type: string {% endconfiguration %} @@ -154,8 +131,8 @@ 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 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 @@ -184,14 +161,7 @@ binary_sensor: ### {% 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. +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. @@ -203,7 +173,6 @@ home/bathroom/switch/button 1 The configuration will look like the example below: -{% raw %} ```yaml # Example configuration.yaml entry binary_sensor: @@ -213,4 +182,4 @@ binary_sensor: payload_on: "1" payload_off: "0" ``` -{% endraw %} + From abf0c175c3279ac7f8e63811588e334412b02eda Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:11:21 +0100 Subject: [PATCH 24/49] Minimize configuration sample --- source/_components/cover.mqtt.markdown | 35 ++++++++++++++------------ 1 file changed, 19 insertions(+), 16 deletions(-) diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown index 903ac487224..b593f60ffc9 100644 --- a/source/_components/cover.mqtt.markdown +++ b/source/_components/cover.mqtt.markdown @@ -13,7 +13,7 @@ ha_iot_class: "depends" ha_release: 0.18 --- -The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a rollershutter, or a garage door). +The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a rollershutter or a garage door). ## {% linkable_title Configuration %} @@ -38,20 +38,19 @@ To use your MQTT cover in your installation, add the following to your `configur # Example configuration.yaml entry cover: - platform: mqtt - name: "MQTT Cover" command_topic: "home-assistant/cover/set" ``` {% configuration %} +command_topic: + description: The MQTT topic to publish commands to control the cover. + required: false + type: string name: description: The name of the cover. required: false type: string default: MQTT Cover -command_topic: - description: The MQTT topic to publish commands to control the cover. - required: false - type: string payload_open: description: The command payload that opens the cover. required: false @@ -129,11 +128,11 @@ value_template: required: false type: string set_position_topic: - description: The MQTT topic to publish position commands to. You need to set position_topic as well if you want to use position topic. Use template if position topic wants different values than within range `position_closed` - `position_open`. If template is not defined and `position_closed != 100` and `position_open != 0` then proper position value is calculated from percentage position. + description: "The MQTT topic to publish position commands to. You need to set position_topic as well if you want to use position topic. Use template if position topic wants different values than within range `position_closed` - `position_open`. If template is not defined and `position_closed != 100` and `position_open != 0` then proper position value is calculated from percentage position." required: false type: string set_position_template: - description: " Defines a [template](/topics/templating/) to define the position to be sent to the `set_position_topic` topic. Incoming position value is available for use in the template `{{position}}`. If no template is defined, the position (0-100) will be calculated according to `position_open` and `position_closed` values." + description: "Defines a [template](/topics/templating/) to define the position to be sent to the `set_position_topic` topic. Incoming position value is available for use in the template `{{position}}`. If no template is defined, the position (0-100) will be calculated according to `position_open` and `position_closed` values." required: false type: string tilt_command_topic: @@ -179,7 +178,7 @@ unique_id: required: false type: string device: - description: 'Information about the device this cover is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set.' + description: "Information about the device this cover is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set." required: false type: map keys: @@ -188,23 +187,23 @@ device: required: false type: list, string connections: - description: 'A list of connections of the device to the outside world as a list of tuples `[connection_type, connection_identifier]`. For example the MAC address of a network interface: `"connections": [["mac", "02:5b:26:a8:dc:12"]]`.' + description: 'A list of connections of the device to the outside world as a list of tuples `[connection_type, connection_identifier]`. For example the MAC address of a network interface: `"connections": ["mac", "02:5b:26:a8:dc:12"]`.' required: false type: list manufacturer: - description: 'The manufacturer of the device.' + description: The manufacturer of the device. required: false type: string model: - description: 'The model of the device.' + description: The model of the device. required: false type: string name: - description: 'The name of the device.' + description: The name of the device. required: false type: string sw_version: - description: 'The firmware version of the device.' + description: The firmware version of the device. required: false type: string {% endconfiguration %} @@ -217,6 +216,7 @@ In this section you will find some real-life examples of how to use this platfor The example below shows a full configuration for a cover without tilt with state topic only. +{% raw %} ```yaml # Example configuration.yaml entry cover: @@ -235,13 +235,15 @@ cover: payload_available: "online" payload_not_available: "offline" optimistic: false - value_template: '{% raw %}{{ value.x }}{% endraw %}' + value_template: '{{ value.x }}' ``` +{% endraw %} ### {% linkable_title Full configuration position topic without tilt %} The example below shows a full configuration for a cover without tilt with position topic. +{% raw %} ```yaml # Example configuration.yaml entry cover: @@ -261,8 +263,9 @@ cover: payload_available: "online" payload_not_available: "offline" optimistic: false - value_template: '{% raw %}{{ value.x }}{% endraw %}' + value_template: '{{ value.x }}' ``` +{% endraw %} ### {% linkable_title Full configuration %} From 1fee137f071f4193e3df6307e3a6a26e5bc593bf Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:16:28 +0100 Subject: [PATCH 25/49] Minimize configuration sample --- source/_components/climate.mqtt.markdown | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/source/_components/climate.mqtt.markdown b/source/_components/climate.mqtt.markdown index 66cd9a2ccdd..cf0caf75028 100644 --- a/source/_components/climate.mqtt.markdown +++ b/source/_components/climate.mqtt.markdown @@ -19,13 +19,14 @@ The platform currently works in optimistic mode, which means it does not obtain It uses a sensor under the hood to obtain the current temperature. +## {% linkable_title Configuration %} + +To enable this camera in your installation, add the following to your `configuration.yaml` file: + ```yaml # Example configuration.yaml entry climate: - platform: mqtt - name: Study - current_temperature_topic: sensors/hvac_study/current_temp - temperature_command_topic: sensors/hvac_study/target_temp ``` {% configuration %} @@ -194,15 +195,15 @@ aux_state_template: required: false type: template min_temp: - description: Minimum set point available + description: Minimum set point available. type: number required: false max_temp: - description: Maximum set point available + description: Maximum set point available. type: number required: false temp_step: - description: Step size for temperature set point + description: Step size for temperature set point. type: number required: false default: 1 From f6d059dd9a8505f5db452483cab4d9d1291d9d19 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:19:31 +0100 Subject: [PATCH 26/49] Add section --- source/_components/device_tracker.mqtt.markdown | 4 ++++ source/_components/device_tracker.mqtt_json.markdown | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/source/_components/device_tracker.mqtt.markdown b/source/_components/device_tracker.mqtt.markdown index bb40d07ea51..ca3415eafdd 100644 --- a/source/_components/device_tracker.mqtt.markdown +++ b/source/_components/device_tracker.mqtt.markdown @@ -15,6 +15,8 @@ ha_iot_class: depends The `mqtt` device tracker platform allows you to detect presence by monitoring an MQTT topic for new locations. To use this platform, you specify a unique topic for each device. +## {% linkable_title Configuration %} + To use this device tracker in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -37,6 +39,8 @@ qos: type: integer {% endconfiguration %} +## {% linkable_title Usage %} + Example JSON you can publish to the topic (e.g., via mqtt.publish service): ```json diff --git a/source/_components/device_tracker.mqtt_json.markdown b/source/_components/device_tracker.mqtt_json.markdown index cc0e4783ec3..3ebee387274 100644 --- a/source/_components/device_tracker.mqtt_json.markdown +++ b/source/_components/device_tracker.mqtt_json.markdown @@ -15,6 +15,8 @@ ha_release: 0.44 The `mqtt_json` device tracker platform allows you to detect presence by monitoring an MQTT topic for new locations. To use this platform, you specify a unique topic for each device. +## {% linkable_title Configuration %} + To use this device tracker in your installation, add the following to your `configuration.yaml` file: ```yaml @@ -37,6 +39,8 @@ qos: type: string {% endconfiguration %} +## {% linkable_title Usage %} + This platform receives JSON formatted payloads containing GPS information, for example: ```json From ff1fde7d8f6aee6c2cd0a3f6341c6554f90e6b21 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:24:02 +0100 Subject: [PATCH 27/49] Minimize configuration sample --- source/_components/sensor.mqtt_room.markdown | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/source/_components/sensor.mqtt_room.markdown b/source/_components/sensor.mqtt_room.markdown index e0c19fcfce3..caaba3e668b 100644 --- a/source/_components/sensor.mqtt_room.markdown +++ b/source/_components/sensor.mqtt_room.markdown @@ -22,12 +22,8 @@ To use this device tracker in your installation, add the following to your `conf ```yaml # Example configuration.yaml entry sensor: - platform: mqtt_room - device_id: 123testid - name: 'Cool device' - state_topic: 'room_presence' - timeout: 5 - away_timeout: 60 + - platform: mqtt_room + device_id: 123testid ``` {% configuration %} @@ -57,6 +53,8 @@ away_timeout: type: integer {% endconfiguration %} +## {% linkable_title Usage %} + Example JSON that should be published to the room topics: ```json @@ -69,8 +67,7 @@ Example JSON that should be published to the room topics: ### {% linkable_title Setting up clients %} -This component works with any software that is sending data in the given format. -Each client should post the discovered devices in its own subtopic of the configured topic. +This component works with any software that is sending data in the given format. Each client should post the discovered devices in its own subtopic of the configured topic. Instead of developing your own application, you can also use any of these already existing clients: - [**room-assistant**](https://github.com/mKeRix/room-assistant): looks for Bluetooth LE beacons, based on Node.js From 561a0c5c23988d136323500e1694a988bec4d734 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:28:46 +0100 Subject: [PATCH 28/49] Minimize configuration sample and fix it --- source/_components/vacuum.mqtt.markdown | 81 +++++++++++++++---------- 1 file changed, 48 insertions(+), 33 deletions(-) diff --git a/source/_components/vacuum.mqtt.markdown b/source/_components/vacuum.mqtt.markdown index 6ada6edfc03..6bd544dba35 100644 --- a/source/_components/vacuum.mqtt.markdown +++ b/source/_components/vacuum.mqtt.markdown @@ -22,39 +22,6 @@ To add your MQTT vacuum to your installation, add the following to your `configu # Example configuration.yaml entry vacuum: - platform: mqtt - name: "MQTT Vacuum" - supported_features: - - turn_on - - turn_off - - pause - - stop - - return_home - - battery - - status - - locate - - clean_spot - - fan_speed - - send_command - command_topic: "vacuum/command" - battery_level_topic: "vacuum/state" - battery_level_template: "{{ value_json.battery_level }}" - charging_topic: "vacuum/state" - charging_template: "{{ value_json.charging }}" - cleaning_topic: "vacuum/state" - cleaning_template: "{{ value_json.cleaning }}" - docked_topic: "vacuum/state" - docked_template: "{{ value_json.docked }}" - error_topic: "vacuum/state" - error_template: "{{ value_json.error }}" - fan_speed_topic: "vacuum/state" - fan_speed_template: "{{ value_json.fan_speed }}" - set_fan_speed_topic: "vacuum/set_fan_speed" - fan_speed_list: - - min - - medium - - high - - max - send_command_topic: 'vacuum/send_command' ``` {% configuration %} @@ -193,6 +160,50 @@ payload_not_available: default: offline {% endconfiguration %} + +### {% linkable_title Full configuration example %} + +{% raw %} +```yaml +# Example configuration.yaml entry +vacuum: + - platform: mqtt + name: "MQTT Vacuum" + supported_features: + - turn_on + - turn_off + - pause + - stop + - return_home + - battery + - status + - locate + - clean_spot + - fan_speed + - send_command + command_topic: "vacuum/command" + battery_level_topic: "vacuum/state" + battery_level_template: "{{ value_json.battery_level }}" + charging_topic: "vacuum/state" + charging_template: "{{ value_json.charging }}" + cleaning_topic: "vacuum/state" + cleaning_template: "{{ value_json.cleaning }}" + docked_topic: "vacuum/state" + docked_template: "{{ value_json.docked }}" + error_topic: "vacuum/state" + error_template: "{{ value_json.error }}" + fan_speed_topic: "vacuum/state" + fan_speed_template: "{{ value_json.fan_speed }}" + set_fan_speed_topic: "vacuum/set_fan_speed" + fan_speed_list: + - min + - medium + - high + - max + send_command_topic: 'vacuum/send_command' +``` +{% endraw %} + ### {% linkable_title Default MQTT Protocol %} The above configuration for this component expects an MQTT protocol like the following. @@ -202,6 +213,7 @@ The above configuration for this component expects an MQTT protocol like the fol MQTT topic: `vacuum/command` Possible MQTT payloads: + - `turn_on` - Begin cleaning - `turn_off` - Turn the Vacuum off - `return_to_base` - Return to base/dock @@ -215,6 +227,7 @@ Possible MQTT payloads: MQTT topic: `vacuum/set_fan_speed` Possible MQTT payloads: + - `min` - Minimum fan speed - `medium` - Medium fan speed - `high` - High fan speed @@ -231,6 +244,7 @@ MQTT payload for `send_command` can be an arbitrary value handled by the vacuum' MQTT topic: `vacuum/state` MQTT payload: + ```json { "battery_level": 61, @@ -243,5 +257,6 @@ MQTT payload: ``` ### {% linkable_title Retrofitting a non-wifi vacuums %} + - Retrofitting your old Roomba with an ESP8266. [This repo](https://github.com/johnboiles/esp-roomba-mqtt) provides MQTT client firmware. - In you own a non-wifi Neato, you can refer to [this repo](https://github.com/jeroenterheerdt/neato-serial) that uses a Raspberry Pi to retrofit an old Neato. From 1ed2343f869d46e8feae3de6d246686169176943 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:32:09 +0100 Subject: [PATCH 29/49] Replace password with bearer token --- source/_components/notify.mqtt.markdown | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/source/_components/notify.mqtt.markdown b/source/_components/notify.mqtt.markdown index a1a33ef7e43..04a40d2a110 100644 --- a/source/_components/notify.mqtt.markdown +++ b/source/_components/notify.mqtt.markdown @@ -38,10 +38,11 @@ The same will work for automations. Using the [REST API](https://developers.home-assistant.io/docs/en/external_api_rest.html) to send a message to a given topic. ```bash -$ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \ - -H "Content-Type: application/json" \ - -d '{"payload": "Test message from HA", "topic": "home/notification"}' \ - http://IP_ADDRESS:8123/api/services/mqtt/publish +$ curl -X POST \ + -H "Authorization: Bearer ABCDEFGH" \ + -H "Content-Type: application/json" \ + -d '{"payload": "Test message from HA", "topic": "home/notification"}' \ + http://IP_ADDRESS:8123/api/services/mqtt/publish ``` ### {% linkable_title Automations %} From d00c4035e01cad17699151abe4ee08268d105803 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:35:12 +0100 Subject: [PATCH 30/49] Make titles linkable --- source/_components/mqtt_statestream.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_components/mqtt_statestream.markdown b/source/_components/mqtt_statestream.markdown index ddf00e0806e..d1bcb8c642f 100644 --- a/source/_components/mqtt_statestream.markdown +++ b/source/_components/mqtt_statestream.markdown @@ -70,7 +70,7 @@ include: type: list {% endconfiguration %} -## Operation +## {% linkable_title Operation %} When any Home Assistant entity changes, this component will publish that change to MQTT. @@ -83,9 +83,9 @@ If that entity also has an attribute called `brightness`, the component will als All states and attributes are passed through JSON serialization before publishing. **Please note** that this causes strings to be quoted (e.g., the string 'on' will be published as '"on"'). You can access the JSON deserialized values (as well as unquoted strings) at many places by using `value_json` instead of `value`. -The last_updated and last_changed values for the entity will be published to `homeassistant/light/master_bedroom_dimmer/last_updated` and `homeassistant/light/master_bedroom_dimmer/last_changed`, respectively. The timestamps are in ISO 8601 format - for example, `2017-10-01T23:20:30.920969+00:00`. +The last_updated and last_changed values for the entity will be published to `homeassistant/light/master_bedroom_dimmer/last_updated` and `homeassistant/light/master_bedroom_dimmer/last_changed`, respectively. The timestamps are in ISO 8601 format - for example, `2017-10-01T23:20:30.920969+00:00`. -## Include/exclude +## {% linkable_title Include/exclude %} The **exclude** and **include** configuration variables can be used to filter the items that are published to MQTT. From 69d2c94e04777a60832feb7729492e3a6b757500 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:35:36 +0100 Subject: [PATCH 31/49] Minor changes --- .../alarm_control_panel.manual_mqtt.markdown | 18 +++++++-------- source/_components/camera.mqtt.markdown | 8 +++---- source/_components/fan.mqtt.markdown | 22 +++++++++---------- source/_components/lock.mqtt.markdown | 12 +++++----- source/_components/sensor.mqtt.markdown | 12 +++++----- source/_components/switch.mqtt.markdown | 20 ++++++++--------- 6 files changed, 46 insertions(+), 46 deletions(-) diff --git a/source/_components/alarm_control_panel.manual_mqtt.markdown b/source/_components/alarm_control_panel.manual_mqtt.markdown index 751a5e77c59..ca6b592aa67 100644 --- a/source/_components/alarm_control_panel.manual_mqtt.markdown +++ b/source/_components/alarm_control_panel.manual_mqtt.markdown @@ -12,7 +12,7 @@ ha_category: Alarm 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. +The `mqtt` 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. It's essentially the opposite of the [MQTT Alarm Panel](/components/alarm_control_panel.mqtt/) which allows Home Assistant to observe an existing, fully-featured alarm where all of the alarm logic is embedded in that physical device. @@ -91,15 +91,15 @@ armed_home/armed_away/armed_night/disarmed/triggered: type: list keys: delay_time: - description: State specific setting for **delay_time** (all states except **triggered**) + description: State specific setting for **delay_time** (all states except **triggered**). required: false type: integer pending_time: - description: State specific setting for **pending_time** (all states except **disarmed**) + description: State specific setting for **pending_time** (all states except **disarmed**). required: false type: integer trigger_time: - description: State specific setting for **trigger_time** (all states except **triggered**) + description: State specific setting for **trigger_time** (all states except **triggered**). required: false type: integer {% endconfiguration %} @@ -110,11 +110,11 @@ Additionally, the following MQTT configuration variables are also available. {% configuration %} state_topic: - description: The MQTT topic HA will publish state updates to. + description: The MQTT topic Home Assistant will publish state updates to. required: true type: string command_topic: - description: The MQTT topic HA will subscribe to, to receive commands from a remote device to change the alarm state. + description: The MQTT topic Home Assistant will subscribe to, to receive commands from a remote device to change the alarm state. required: true type: string qos: @@ -148,9 +148,9 @@ payload_arm_night: In the configuration example below: -- The disarmed state never triggers the alarm; -- The armed_home state will leave no time to leave the building or disarm the alarm; -- While other states state will give 30 seconds to leave the building before triggering the alarm, and 20 seconds to disarm the alarm when coming back; +- The disarmed state never triggers the alarm +- The armed_home state will leave no time to leave the building or disarm the alarm +- While other states state will give 30 seconds to leave the building before triggering the alarm, and 20 seconds to disarm the alarm when coming back - Setting pending_time to 0 for triggered state allows the alarm to trigger after previous state's delay time only. If not set, the alarm will be pending for previous state's delay_time plus the default pending_time before triggering. ```yaml diff --git a/source/_components/camera.mqtt.markdown b/source/_components/camera.mqtt.markdown index 177e89f8924..1f79e16cc7c 100644 --- a/source/_components/camera.mqtt.markdown +++ b/source/_components/camera.mqtt.markdown @@ -30,17 +30,15 @@ camera: {% configuration %} topic: - description: MQTT topic to subscribe to. + description: The MQTT topic to subscribe to. required: true type: string name: - description: Name of the camera. + description: The name of the camera. required: false type: string unique_id: - description: > - An ID that uniquely identifies this camera. If two cameras - have the same unique ID Home Assistant will raise an exception. + description: An ID that uniquely identifies this camera. If two cameras have the same unique ID Home Assistant will raise an exception. required: false type: string {% endconfiguration %} diff --git a/source/_components/fan.mqtt.markdown b/source/_components/fan.mqtt.markdown index 2a726f19e46..13f79898ce0 100644 --- a/source/_components/fan.mqtt.markdown +++ b/source/_components/fan.mqtt.markdown @@ -33,15 +33,15 @@ fan: ``` {% configuration %} +command_topic: + description: The MQTT topic to publish commands to change the fan state. + required: true + type: string name: description: The name of the fan. required: false type: string default: MQTT Fan -command_topic: - description: The MQTT topic to publish commands to change the fan state. - required: true - type: string state_topic: description: The MQTT topic subscribed to receive state updates. required: false @@ -125,7 +125,7 @@ speed_value_template: required: false type: string speeds: - description: "List of speeds this fan is capable of running at. Valid entries are `off`, `low`, `medium`, and `high`." + description: "List of speeds this fan is capable of running at. Valid entries are `off`, `low`, `medium` and `high`." required: false type: string list availability_topic: @@ -147,12 +147,12 @@ unique_id: required: false type: string device: - description: 'Information about the device this fan is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set.' + description: "Information about the device this fan is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set." required: false type: map keys: identifiers: - description: 'A list of IDs that uniquely identify the device. For example a serial number.' + description: A list of IDs that uniquely identify the device. For example a serial number. required: false type: list, string connections: @@ -160,19 +160,19 @@ device: required: false type: list, tuple manufacturer: - description: 'The manufacturer of the device.' + description: The manufacturer of the device. required: false type: string model: - description: 'The model of the device.' + description: The model of the device. required: false type: string name: - description: 'The name of the device.' + description: The name of the device. required: false type: string sw_version: - description: 'The firmware version of the device.' + description: The firmware version of the device. required: false type: string {% endconfiguration %} diff --git a/source/_components/lock.mqtt.markdown b/source/_components/lock.mqtt.markdown index 7009e9224e9..47238132ab4 100644 --- a/source/_components/lock.mqtt.markdown +++ b/source/_components/lock.mqtt.markdown @@ -15,6 +15,8 @@ ha_iot_class: depends The `mqtt` lock platform lets you control your MQTT enabled locks. +## {% linkable_title Configuration %} + In an ideal scenario, the MQTT device will have a `state_topic` to publish state changes. If these messages are published with a `RETAIN` flag, the MQTT lock will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the lock will be `false` / unlocked. When a `state_topic` is not available, the lock will work in optimistic mode. In this mode, the lock will immediately change state after every command. Otherwise, the lock will wait for state confirmation from the device (message from `state_topic`). @@ -31,11 +33,6 @@ lock: ``` {% configuration %} -name: - description: The name of the lock. - required: false - type: string - default: MQTT Lock command_topic: description: The MQTT topic to publish commands to change the lock state. required: true @@ -44,6 +41,11 @@ state_topic: description: The MQTT topic subscribed to receive state updates. required: false type: string +name: + description: The name of the lock. + required: false + type: string + default: MQTT Lock payload_lock: description: The payload that represents enabled/locked state. required: false diff --git a/source/_components/sensor.mqtt.markdown b/source/_components/sensor.mqtt.markdown index f29e5299776..339908943fb 100644 --- a/source/_components/sensor.mqtt.markdown +++ b/source/_components/sensor.mqtt.markdown @@ -92,12 +92,12 @@ device_class: type: device_class default: None device: - description: 'Information about the device this sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set.' + description: "Information about the device this sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set." required: false type: map keys: identifiers: - description: 'A list of IDs that uniquely identify the device. For example a serial number.' + description: A list of IDs that uniquely identify the device. For example a serial number. required: false type: list, string connections: @@ -105,19 +105,19 @@ device: required: false type: list manufacturer: - description: 'The manufacturer of the device.' + description: The manufacturer of the device. required: false type: string model: - description: 'The model of the device.' + description: The model of the device. required: false type: string name: - description: 'The name of the device.' + description: The name of the device. required: false type: string sw_version: - description: 'The firmware version of the device.' + description: The firmware version of the device. required: false type: string {% endconfiguration %} diff --git a/source/_components/switch.mqtt.markdown b/source/_components/switch.mqtt.markdown index b5f978a0adf..283ec133758 100644 --- a/source/_components/switch.mqtt.markdown +++ b/source/_components/switch.mqtt.markdown @@ -33,6 +33,10 @@ switch: ``` {% configuration %} +command_topic: + description: The MQTT topic to publish commands to change the switch state. + required: false + type: string name: description: The name to use when displaying this switch. required: false @@ -56,10 +60,6 @@ state_off: required: false type: string default: "OFF" -command_topic: - description: The MQTT topic to publish commands to change the switch state. - required: false - type: string availability_topic: description: The MQTT topic subscribed to receive availability (online/offline) updates. required: false @@ -104,12 +104,12 @@ value_template: required: false type: string device: - description: 'Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set.' + description: "Information about the device this switch is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set." required: false type: map keys: identifiers: - description: 'A list of IDs that uniquely identify the device. For example a serial number.' + description: A list of IDs that uniquely identify the device. For example a serial number. required: false type: list, string connections: @@ -117,19 +117,19 @@ device: required: false type: list manufacturer: - description: 'The manufacturer of the device.' + description: The manufacturer of the device. required: false type: string model: - description: 'The model of the device.' + description: The model of the device. required: false type: string name: - description: 'The name of the device.' + description: The name of the device. required: false type: string sw_version: - description: 'The firmware version of the device.' + description: The firmware version of the device. required: false type: string {% endconfiguration %} From ae0952d27d43edd239d84f99e63e65a6aeff3a18 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 30 Dec 2018 22:38:00 +0100 Subject: [PATCH 32/49] Update formatting --- source/_components/alarm_control_panel.mqtt.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_components/alarm_control_panel.mqtt.markdown b/source/_components/alarm_control_panel.mqtt.markdown index 8cd5dd1bfd2..d55e37e7172 100644 --- a/source/_components/alarm_control_panel.mqtt.markdown +++ b/source/_components/alarm_control_panel.mqtt.markdown @@ -17,11 +17,11 @@ The `mqtt` alarm panel platform enables the possibility to control MQTT capable The component will accept the following states from your Alarm Panel (in lower case): -- 'disarmed' -- 'armed_home' -- 'armed_away' -- 'pending' -- 'triggered' +- `disarmed` +- `armed_home` +- `armed_away` +- `pending` +- `triggered` The component can control your Alarm Panel by publishing to the `command_topic` when a user interacts with the Home Assistant frontend. From 7c5d3edfcfb1343532ce6665b6b32f6f0787ff9c Mon Sep 17 00:00:00 2001 From: DubhAd Date: Mon, 31 Dec 2018 11:19:31 +0000 Subject: [PATCH 33/49] Dubh ad patch 2 (#8003) * Graph for history-graph page Graph showing the way it appears with `unit_of_measurement` * Adding second graph * Fix --- source/_lovelace/history-graph.markdown | 9 +++++++-- .../lovelace/lovelace_history_graph_lines.png | Bin 0 -> 14127 bytes 2 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 source/images/lovelace/lovelace_history_graph_lines.png diff --git a/source/_lovelace/history-graph.markdown b/source/_lovelace/history-graph.markdown index a27641069a1..0ff77517850 100644 --- a/source/_lovelace/history-graph.markdown +++ b/source/_lovelace/history-graph.markdown @@ -13,8 +13,13 @@ footer: true History graph is a basic card, allowing you to display a graph for each of the entities in the list specified as config.

-Screenshot of the history graph card -Screenshot of the history graph card. +Screenshot of the history graph card for entities without a unit_of_measurement +Screenshot of the history graph card, when no `unit_of_measurement` is defined. +

+ +

+Screenshot of the history graph card for entities with a unit_of_measurement +Screenshot of the history graph card, when a `unit_of_measurement` is defined.

{% configuration %} diff --git a/source/images/lovelace/lovelace_history_graph_lines.png b/source/images/lovelace/lovelace_history_graph_lines.png new file mode 100644 index 0000000000000000000000000000000000000000..b72c5c70566d5366a1c000b17a10a797306fe507 GIT binary patch literal 14127 zcmdVBWmr^U*e)s{jUb{RQX&n~In>Yy(x50E0xCUpOM@UelnmV>-K{h;Fi3-R3`2M4 zUif``f8Y6Ye(dXUH4DeJg2I>3jDoq6x1|v4QXS4zJ!j-MdHJarcMO zV_*2;-aVmCB{^vwccbmJ@YKg+EvNIh^d9jn4X4b)n**1fHq64p6Hf)72^u8zjuq~+ z?~n;(i+a+ovb~Q%|4bJbij%anJv7{8XcD=_qAn zc1+^U?AYx5;NewzN~zP2#zbwjHhQ#Z<2DD6KImZ_E31_Z9zCO}1~TZO%&YcH7(RVa zOpr8)47iFP2w?`UKEgq%0M9ZK!BZZ};3++Y^4~S&`9G^+&I06SuY+W4$|@sGTl``z z=SM+7k1-}NQ?0qj2FNO_!MAm@uKLO|5CrGO)#2d8i`JdSP0ze&YLFHU2-0bc*%#V& zh2r+SU0MnQEK#W>S9g*w;Z+?(AB{pJU1}>q?@Xj6s)2lhd1sG2*}gtXk9qgy2QJ5B zx|>(mm#4ae;)jtNTU$p?FuBC=$qMt(@4V(AjmP8q$Kq=;erJoJfgUG2v&BX}$8TC* zzGs%){af?8fbgAguB`JbessghU+XcT)!1T3==DqyHQ3icP(Yw?W8?GnH9E~Ly>U58 z?8uWw!gF-cOdQ59ad zs2?BtaCx%*d9+ZIvM&6g47-0^++oNAs?p;KnL z@SJ-NIgO-jA)Vh<1v2#0D_PoHdY%lnkEBm>zj|2EzQ^q(Qy0%7rV(8kbc{3ai7J{f z_A^9>CObyYHV@t$ji?v&GeEj4x!bM|Or~N483iriP@~f|3!3KwQzW<~w4)S6Wi2P) zF9z&=b4GTXb|tSp4p#auvNO3Mty`4{%>5Vr7S3*Nn-K&mJr&ZvQ+4m$Yy#P4#)@?} z&tvWA^mTn@@Yt-B6_7EEAMnprQiW9O1UF7)fWUJKJgQI2J<$^**kRaa-KUvP zxEK7Yb7MpNApyOV`#sgEVMamq{ABz|2izj*D*Rc=Tkd6tQcwsoMkn5$U59-C|ln1`%AKtrtWS9iGkeGQZ;UpY^l1U2YRqq zp`-Un$71MZM{lk#uZs%4nAn13e!Y3~<`b&&^B6lPU9Xbf;0r6~mg$nc1PKclQ`Z7G@L{=h?jhfvn(k%nbzg&MYH*=dZPje)yP-zJJ-G$rOS&^}& zkAJ4Ng}b7zD}+a%JHv_($_WUeejZq3J#nF}O`7$MRzlAY$xP!MdwY=7HtG>Gp^zAA z_t_&7!Ng7$cD9;oKaS`+z*zM!{DWC5kNrUcm*{C`t<6++L7!VH1&(RV^~&F9$KEMH zl9hic?q{~@B`oo&RvEaQwVb@H(0~Y?O4r6%n0fVIu05?6w(NiE zL%-UX2?Rt)LGDTD!){-uGjcj{P%lD|I*(Tk1Scq%`PXTzXSG=2I9pFS7H#s(@N3yZKhe5{9D*Za-I zH^6Y}#G5%l-HBr`&;3{yS!zy+Q=RCjztD0zr#)fd^vx(y0+Rkv2A&cZ!>@p0p36VX z8^b}=6~n*cFRi*NVMXa4a@^w@L>~_u`YNZVs`?F#daM+~uXoZBN-}Y1qG9;7+~DO% zjo-=kGzImg^JzISjk^WHB07?3w7$>(<#9jh=v3|q1u!vAxyZMi3Mz<3lNbsduRN+L zB4TQh7>K=KJWRfl3zWn34P6jR`xd#z)tzHmN;+pU*X-fhS`NX9VO{+V8BpxG?`*p4 zWwAg(nKzAr*J~H@&t9a#wiSo^ z6S)-B5uzrudy|Pa+FX$C{TPav1vB_oR5#UVIoP4%#iddd_73-83O|cGlCqZ{-5cG5 z1ibSRD(#UHpAfdiWTsXO>QveT^Jbq!3_9TZte<^M%HrL_-ZlDkg{x2 z#njSQZDcaexm5iN-fEtz7JaJCFqeb~e4D^cnz@t}qH@WnFPTd8eg?i&+)--M>wO1) zKW~-cBZRUNNli`FR#0AcWNtpC8mY*DB=E-^Lv_7ns@LaOh__CI3&d)HB(}pSgUkzH zvm$*07M`t1;e__?lCe_AoRVvESLLG0|}D4Lj!F0|BuZ3|F1z5cnlef zTA@-ra}hsMMD_u-hz5^Tla zhScw)nISkdXLKWwtbzi?mZRa<8=>HW=&D7xsi z=+0dpZx+1$`7R6LWk0B3%#8fFY*pmFJHAyYERr=7r zI0fq?l}^H75za@UI_ej38F&hf32?X}2cUfDD!B`9 z$A7KMidfR!U&t>x^4LuB(4g*}>{}!m=HEWjdIdK^exzy2wNXeW7eK+h<6c@-M;U4f zF{lteE15@dw;9+@Rd!`S;=;*TegFwoZF{y!*RQ)ZX2&K=V>lOvzb+Pwpwvaxm%04? zR8Z7I>-91Za)+EekA@V-+}bV;k88?&R3AL$kt)%vfvbPRbvAAavcWm{z>wO%;yc%X zPT!mn(s^rHSK%>i{ttsZlklu=T#0+_tc$t>E23gz*E7o8o8PTVhd!M}T(c%{pPcv5 z`Tg|0In2OaS5;NLf!Ph)Mtc}Pns%HpbStu*u3Z=SdAsX-Dt6q<5WVJ=*sHCro%7k+ z`q+&Dtmm96WIKFbVf&84`8V804H^yrzfI@zDQn(2-^*=JqZR)TQFP$ak@7)WzbnTU z?(&jk^^*#lf-UovE&+TSidMSIF=!1N@l?8WAkL>ndODd}64cR{uJKsOSZlzJbyCcL zRJu*`UOVCEwLe)cjX4#AW%Wx0J~I`DtF7*b1H#8Q@q_g>{yyeAgkOBZAsjuJmwK%% z{l2k$O!EvB$|-P`VMlLGgIShsBalmdLUCp-J~Z>vw!t!;}^ox~(DbwN}Vv7vO9S^Vzr3)#rR zPL!7eX^7q1pZrnhKBuz<*pWV8Y{f3Os*XL)7f8pcFr`tU+cGJ?JX^0%rae6-b#)D0 z5?cKT$_LA%_b55r*|hWTZ{qm3UG6mLFM$-<;i3q&y9s`Pn#i?fYvtxHYxIZ%5X zH3ad6ZFe`g-W3>)_{nItU*c0Mk$kr^PJ`bj*Bj98*?Lvg_dc1ZT6klg^ zGa4e7yT5HF&>?96o*jX2{- z-n37uu-S}Q7fEtl#ILjk)339>suL=&n&LzvLF#QuOsa;xQz_Dc=j(utNcLiOi6CFF&V(;@6+Tbp>^ZE}K0;;UaoO&1Wkf{D&>9Ow}PM$0B5 zwOeMPsXun&=@-jH4}Ii0EFVkVnZ(f8^(WY_E3<|v%+~)l z(Iv-@*33~@rz4jlqU2*d`vm?%v9OHVD-{5$@gUd>KF~7y?70=jEy617sf+@xhPHNm zToOQ-(HDf3=u^E&B(LPOyL&X3MF^DR5=k+-TxYcp_T_t2X;~+9$Ec;eTZz0xjE#+5 zaDRb0w!N23HJk(JH#{XK2ng|uyP=I}%d6iqNf>xmMk`zg8B;nXL(XH^SdThf_#HUb z=(4F}Wo0$~(Z)sxNS;Um1&eMV&AgG74dnm!JLVlg77^<{3#9jNyzlZAR5B^YY}Ldu zeV=nBOEz>v0Pk5gGEbihJnpylhyIp~UO7#~QRWW2-O7cf`dpr@KW8K>e63Ny7~Z=Q zS!(Uk{l0yxF>%LEMOc5xG!qv70Hx9{1&Zf^*1(p7Ak0EgetfKdm(chq6&qHoM>z15 zAb$vw44yKnfn+55cOS+A<*&$sDLwsnAEeG|WhM*s@$bGD`(tcfSE%cDq@wC#y_jBdHakyx>PSm7g_shE#Tnr5j9n8`}<{@fLzKb$~ z_C3Tk%X_ANr8EE8ynKH_+GTEQij86wlGXZokQS^9`Oi+CqhGf;R2=rkF5H)o++5q! zhJ^lm(})gj>j@lmgTrwE_Qjz*o!^$a5;6476n!iH2^@iBeC1b?#N6V1ASdI8cqiX77)EuvG~j1=s><#2{IOd?TeiG zolyM}ec*9;1aS*)evuDDq}r>d|3qN38?!MuwGfEvvZCAhe&os1aYS;1AXoL^W%pI{IS+wlk$gAOz`#xgcKW}w1oc9{Ec1a&4&>x>Z(W6 zZiSl%?=z*G#j?Bum4-Q44h+}T%}v#7(%mNc^i2w7cYahPqB@uslI*=jb_ec4IfIbCE%S;2DpiCezPdIC7f zjxSE7e>|p_vbP#NUUpg#6bRv>UX@t1f#4Wt2(a~La6vq_D!H+c>_7CWDr@xz1qB5^ zcZQMLfRgTUG%qu=^e$VE7y4v)FBNoR(H6&%^8k^eiN8y?<$&?9et3Sj7ZT~{voj6MCU$-0h9lf*|GB$tz1!c_OhzvL<=aZk`& zbfgPUB#J0S_kt$$Nu;8<&6Mao*Lj|fxxh%Dc7Big8q42lP59Js=3x~FCl%Cb@mIJ7 z`IbDdn-!W+jS;57CFEt%CC+ByQON!{Q!6>@2!&C|z zP(KrgTKC|3?(ll7iJXy%RT zxI{n$Pti5snFWP6lNS?SPc%oi%im5_je$lA#6}EwnFccH<>Ds-6lh0<@w|*WZ>x4Z zj27?>;aFyAZA1zu?mh$GO~Bd2jwm+E1Jd_FnZGo6YjA0 z3XZRz8v_|g)br@$_}Y?d3E?67Fm-!muA;x1Hfpf@Z}R)AMT8q}}`Z^F8fw*P?mPRRg|JSA>rlcmpcn zP~0JYn!%%Y^{C!3?*5B-ew;5;CFT=V$n)NF&)wYX8C<&D8Cj8DG6sko()ds>mZM}j zQQ+c*6_t1?{b}~feL=)`N@@&Rx-MuHJ}p+wIQ}qwg`AFefAc)zzER%@J7siS2H5}Gv`r;$5ieu#y=%SVxiB9USs_PT2`doD%N0QG~P4L_UD;z z6U_!Rf>a>4H~70nzizOeZ3Ca(5-dNkS|z+3>1r`5&KYLY1?5c0!Gmf1ln=u)Xp|IJ zu4J65M0K*w{ecAEhhk#1udUm>6n|QO7?(pxZ92yxv+yP%2ogo$(J?jh?c0TKj>qi~ zv2IGIekuDm0L?S+RZ{Dw{Hn)cqi~&az|MWAB8SW~h}J@S#6`et_ujHTULdr#_Ih%3 zyXgj6lwU86ms<)Z_-MOqSU)WI8blGbd36x}OTVQ2c0ZA$i75L8w-vi4a$Twe6ZN~a z%)nn9ucmbBlm?l3__SPvB^x6G>LjjH4eM|KP(=$t69+Ay zZ&21_QVNY2yvvJ;QmPp44b5CIlt;@N*Jn&=r^H61au%#rgab_b4z~O?MXqikcJZbUza@ zpUi^M?xNmD3`$vX(i!}th0Md%8!LragcRGPNxFRIvCSIdlpOHu!;x9-;8PG1 zEZR>M-n>P*L5*!~RnKYp?Od)t6nHCm&tLkc*yWq1XlnOC)NrF3B;NvynmpYzDE=1j z@Etv~tLw()aDl~n+yo8G>n3Am$@gzK6a?uD~O=G#0u&EmHKrn{`HHb z47pqwA|8W~A|Fa0HuMtg&X5G9s5anLUGYfKU0lV|>t1zJHkqpDamZT~u3!EFLDGo- z4K)u~wxG?aYOW0UWL#P_ghjdEw(>sS^h&x;7iWT)id^oHko%0S4*;w2fRB~-=BS0K zaJR%rA>d;rOjusylnLXJw$n%AP$v&8$G@mf;&oR^-=o66y!J-Q)SMNiui+q3hlnmN z4)@u-2nI1X91F{vH@ZcR85cUrj1T^yq#3+RNMI^C=K)&dw*Wi^FSM!2>&*{C(pw(+ z84YBYDMFF%m|d)=S+v=AK}ztvdgRLBZa!piknmQ9oInS(iiTn^MVoJML<_mk05Ni2 z{`PscYVhQT4T&q`Ekz@M!=6LzeD}LDv3-`#9N{2bRy2X^T;_OLtx)|0D~5-nw3}ht zcc(rkHpi=1)otT)pq}X7hT{a?(X4^gK(CPawrg8>$_KfXW-pYoA6)6Vl}eJQDGH0^ zjIAs9ZXylUYcK(&j4y)5HYcSa1W~b%!;jfS%Z_;!k+ZkDTEtxeRHr)SD}` zRR61t%Lrqjb>0?A{PQR)fYN7*MZ%00m}QqA-kng$89n>Ineb((C+&dy%N70 zkL$M1vq9hS!7*W0^cjGwTXW;9`g$k~=?`9KpB6V@QYGh@k#(b2VgFFv1B;{dIB zP&QhA=(NVy0tElrNCWA^Qfp`1``1PyRjR+CI-L!@;^Z)r58e6U4C!|6tK0aEdkqC} z`!Y)^tN`ZQC>eFg)i$H9L<@Ct%!FO4*+7ttCRJ}}aNwZxE&V#RjL3X%k~91GN8c49 z@rGmU=lpK#GUCLbPToI((mR^uo#e+DNwr#7ooYrpgqqZGWND0o@A-oY^BZq46F-1c zM3xNu`}R{jPNo_SKE(4M^or{js2yt)sCV@?02$M9dhX}0r!#cV}%a-OFU5fd?#YV0fRLW(TZ1zMt=1=o3Umd>L&Px&< zX}`}ksljFNDYCUoPCY1Mw{<$jQt|rw)Ed+@oE_O$kWsoi?-2NRo5syB){6qW)Z5kB z*?G+&k2m|9TAA-)9x;#kaNBjN-qG~D=m-JnUD=pC@>Mk#B80LIw6m+~^4?qc{by)+ zIJ>c_DeY6_ht3le;y8Tj0x5=c7PB;T&$>9HXmiL94hO(;;rRGlt7kd(7@&!HuQL9D zs1RJ*KM>cvW5Ly%gQP|krBOh^5M85jb9$ByDCe+4hFaU{{Eh?wg4KGJeDD#U^PNsf zXWKGwTx~$Z&X)*AnF_W0KXozlffQ#GY}@U&SK_VfPPPcS{+y%cED#9pOSVOmI#=&e zZxqMpV7Jx~jM=}djz8Nrxxjh5FY7Npx7akWOs#_#=`$$iArWf3?zcV?v)D~FgrUyX zZjp%V)2vj5sL`Is+)Tgu`uS@3^XcSy**5KLt0Pe$OMFs39KWeg)Fp;E?!oWb;qpes zI4nBvK-{NXD=RA<-cP-ugn%2Zyg)zjyY+%Q!VX$?&)ERIVYNR~#ngk}_kawXCw!Tj z>XQBmd}Yd`9zCHflm(O~#w#xuuBWxqnXeFSYp5q?neXIhoT9McpcI&ht4fBrWl%y@ zUy$F8mEd(Ge}LN_EdjkD93%;et?FyXz~X}o5LqJd{WaUxAA(XVyv`xuV@AMF!(@=m zP0yYk9k8PB%Ys(-trm<2^G*rfXt?}Y!vOA;cK;<%cUg^DDP^FICQ zgw$M?y#54c0?Q%SHs(ZZzi%Wa`}d2QD~cNLDX zW2=Bz>D{ePugT!@h0+l|6-m|;eOa_l3R<4sO8Lh;s4)XVyI~w8IFbTL>P(m{!#%f$ zV73wRs}0?o8Ae^p47c>}d*_3=m*TVALFFpvNH?vhfel64eQi$$h(cb}?oMg(q4vSD zhLu%0jrPs;{8$jT_wRp0{+dB>5uThc(uiG+uKnV(I6q_J@V26cbo;E+5R#v1M-ZY^ z4w%(IsS5=xs8-Te68h87hkR)eWX2RaqiogKBk#6oSE_!MmyiM7F`l;1%mN$1TuTT9;?q*4IjY1)xwRo4T;fnUi3MR@)`%A|U- z`9fyxyWneemc=kVB(n(DYDI-#5vv-g>}DimbnEtl+t6r_rtpuF^Wz-iU*;NGxC>1z zH=Au2Yz26}C)JI5=q#9d07Q+sON192_G(oEonn=iHzALCs*y+aQvaxis)m|12*%_f z&2)LQHrG-CpQ0||oXt9z)s*1Z?|WQDeDAgIwYA{!<@_l)O$Pq`K8l(Q>cpoM2UFc5 z<5$rUb%ehcnH(CjZd-0I`~yi0J5Us5PsoLXCVDV{{g4Ih2Q5@2fw7+A6s8s*hfVWx z(<8PZSTr5z(blP8G&sF-p41URX-=_nxxFitu}#x*PNjB z(SFZ@3>%iCIJu4*&=2#$Psu2%8!aTZNvoT@KG?ndHvBQwdD@$BNPJaiJC)s@HozC1 zLtz8Iq+YBOkQ^G==EX9Cmf!mvPHG}?a+(7S?(jiao%ugLhjnaxJRgUcx^N_hn_|PR z=^I4tp|%=W!abzzNUMee)M@m8alGkG?^^K-5sL+}!?{ z3HkA0@U9mdA3Ko(!P0DVJR~gdIP&e`pDfwHM1f8sY1vWJkI%&3mUv(7FG$AF#9$Nj zuGssDxr-QPPd;K(WS2&kl(jyCazi=c4FY|-Nam;4_KCsxw@2!}1OVP(5CWxQh7_t& zrY;f7)(-u3r-E`?+$VS-qxP~{Jnbk=Ii@PyFltNKAOQ>NB(i}^tinb}HSasEUZetG zn=pCgM>gF%tnkZ@O_3Ar{IV65m}w@zpg5UV48ICyh@(niw+d&fnBf>7e0ez=O*a^(ZBy0r%@Il^19{+fBR$wi-l-$ z9=6UWM8`@n`|WytUM#5t^7<28Vrq>$qPe=>%*x40nNr5NAGY4F|C#r&`EV45;C9PT zfY?mes)llul<_thw?Qkv&`mj@IM5;shG!btEY^`bj4WV7@RLa{z zDSHBVFb8MpFPUa*#(_`2U3urVXcL{|RoYIV@NYrf`1$?sy^4(^%*m z^?CtRcxyZ=x_55~vqg(GD-Ed8CrcY$_JN315K-UN;&av9WvwQgAJFzc`c)eU=F;A^SAl zpW@4|go~n%YWen!jq`(;&^Mat;w#$>v55>ZU!dmq|G9Fu)FZgHY>nfaS3C+hZ%#JK zyI((lMi}PS_2jn_!>qT2e%%Eq93MsfAY*Hu4%!AvGWuJ5)nK+x<96nBN&^QOc{Vl% zEL(TuW?aG~ku?-Xh0*KTsdfiwRtdnL3qOKV0eH<-crP!m^YEug%CnZ|1pu1BZ4-Qn z;x>HMP|a~!?l}6)Um0L^Rd3G}|C;Nua||DrO$`kQpRy-4$X%`tNrMzrB)0{wiT5GQ;SizUAAK)H`u3F$UaQ9KA)Gbu>dh=5 z(cXasg2mAJvycp}1`T9h@TQseQb(EJ?BJVpK*VNt;%XH^O}@OG-MxaY#0H5zR|W_S zwtU#Wc(Fm>lE*mP{CU)WwCq~ko(|-*=_$>7eQkhJV(ar5{PE_uBQMjpcVO@O3=T>S z7ZUp)#raPq<0~ei)zF(i>88ufE5!@@tO1Zt>m8!pb@s&;76!4 z*XQsQC;`9#@nj;Ve?~kkZT#rxR0UR?2Np9F5_RvglgE5>w8*#gz#qb#C&Sb`bw9Az z;P@dX*p2cD)agnCN&2V7!L+Pcr}>PQ1;}Y609_@U*GCy`Jmo^#PF_Qq%A&G|CMH2q zgP~3;Tc1DT5wy)viB1kJ79;|a5Ze=WRpfdMhNb1p=EV>rmr;zKGJ?j;e}m)C%*SGK zv;11pw_A4!5NJD!11qirijtN;L~Zc*$%&DR&TP%Z$&VZZu%8mBhXiGCPqh0RAwe5Q z?k0Yj!%J*dD=l^n3uV=3h`kkO(;oQ9e z(6*wjMli3-24|xTlJ#PRh<6&(&e~f0PPnsISC4)sWRr}fNQ5L*DP1P>w(K1L^jyo5 z`U9~qY$`=&CmF01BvSVOS!6c~cF&MK5KXB?1KI zd8eW`RQhXEcH54n`4yOb)zDEMeyWMgeS9}6`&*>c{cl|MuS5Yh>8Rdlmc>6KGlHPE z;iR4LTD|K(WT=0SmD+758T-Bm&YKJ9IJ>(3Xz@A~9buO^si`Y2si|pcXR;2j85CbO zNTfmhjQ!5FsNKY;}EQ%_HC z6gY`mrC@HJ^SAm_JpZ@FsIj>lql>oN)JG95gt=1H;9HOJm}b7)9~8#UzPh~G#l^4h zj)0|fo4hi4$ljg+d}eY3wR)>9=iZyF2qP6xcj#9xEmvx{GU>l1Z<~sZ)vUd_-#Wf*Y9j-m28N58!Ny3x=m)b=aDng`d+^g zSKcF{Em_q+d8|SW1fR79#&#u>TVfG4f^z`=CUf0}4p^nT=Q`u-H)Jn$S_kqz$mJk( zm0bCKurHBY{fpOij436m;yo81s^hk@U&Vrloz*JtX@5IOe>~1YRSH)wf`uifxBel^ z<8V6dpF)KOhMeD3EHFm)!1);7iR6#iRJR%#w|J3IZbJz&3Mju4(JH>h+w_3V553UA z(oRDUrS(O2+~*_v13Kgnfg`X|jbBrt#3K2Yl=xneBdF;{7wfXhgi>k+Y?R8QKp&aK zTOJnKMsF<)Z6pdSs`$MJ0mQ}-h4q1*Fxire->^$n8MlcGXv&Z3IA|YL)C2-$r%8s! zs#O(VO&^qG1my=a5gBr5j~$kYDlX=OE^n|?F|WfhcR@*XA|aOVfuNxwoElt!V6&p7l+QtkN9sb)Zuki7YWV2nsTJHRF-7HAQwMN&-bt3n zzXT?nf_tsf4b~4ZR=S)or`~Ekdlk&qql?)?-J_kZB#32k?~^459$@EH$QIu#WfEP( wxSglVepOt3I^_Sc?*D)J0hV0W=q+wtnGfw{g-$E*Be#1>@@jIWGA0541AOO-TL1t6 literal 0 HcmV?d00001 From d722e47e0f766c66ff3146c0d0ac9d68d662264f Mon Sep 17 00:00:00 2001 From: Andrej Friesen Date: Mon, 31 Dec 2018 16:15:19 +0100 Subject: [PATCH 34/49] Add best practice on how to upgrade Hass.io (#7998) * Add best practice on how to upgrade Hass.io * Update name --- source/_docs/installation/updating.markdown | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown index 4bc5d375eb1..fa619332069 100644 --- a/source/_docs/installation/updating.markdown +++ b/source/_docs/installation/updating.markdown @@ -63,3 +63,18 @@ If you want to stay on the bleeding-edge Home Assistant development branch, you ```bash $ pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@dev ``` + +### {% linkable_title Update Hass.io installation %} + +Best practise for updating a Hass.io installation: + +1. Backup your installation + - Use the snapshot functionallity by Hass.io +2. Check the release notes for breaking changes on [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases) + - Use the search function in your browser (`STRG + f`) and search for **Breaking Changes** +3. Check your configuration via the [Check Home Assistant configuration](/addons/check_config/) add-On + - If this works you can safly update + - If this does not work change your config accordingly +4. If necassary change your Home Assistant configuration accordingly +5. Update Home Assistant +6. Restart Home Assistant From 5326d121574b3d7aa0234bc342d1ff22b45e7678 Mon Sep 17 00:00:00 2001 From: Andrej Friesen Date: Mon, 31 Dec 2018 22:49:30 +0100 Subject: [PATCH 35/49] Add how-to for Check Home Assistant configuration Add-On (#7997) * Add how-to for Check Home Assistant configuration * Make title linkable * Other changes * :pencil2: Tweaks --- source/_addons/check_config.markdown | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/source/_addons/check_config.markdown b/source/_addons/check_config.markdown index a11232b5ea3..9ae856d22a3 100644 --- a/source/_addons/check_config.markdown +++ b/source/_addons/check_config.markdown @@ -11,6 +11,16 @@ footer: true You can use this add-on to check whether your configuration files are valid against the new version of Home Assistant before you actually update your Home Assistant installation. This add-on will help you avoid errors due to breaking changes, resulting in a smooth update. +### {% linkable_title How to use this add-on %} + +1. Just start the add-on. +2. Wait (On a Raspberry Pi it can take several minutes). +3. If you see the following output then you are good to go to update Home Assistant: `[Info] Configuration check finished - no error found! :)`. + +If you get errors, then you should look for **Breaking Changes** against the version you specified for this add-on and change your configuration accordingly. + +### {% linkable_title Add-on configuration %} + ```json { "version": "latest" From 3fa118174585caa140ab702553e495b7fe1feb5d Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 1 Jan 2019 13:13:02 +0100 Subject: [PATCH 36/49] :pencil2: Updating Hass.io enhancement (#8007) --- source/_docs/installation/updating.markdown | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown index fa619332069..b82e53d1488 100644 --- a/source/_docs/installation/updating.markdown +++ b/source/_docs/installation/updating.markdown @@ -66,15 +66,10 @@ $ pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@ ### {% linkable_title Update Hass.io installation %} -Best practise for updating a Hass.io installation: +Best practice for updating a Hass.io installation: -1. Backup your installation - - Use the snapshot functionallity by Hass.io -2. Check the release notes for breaking changes on [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases) - - Use the search function in your browser (`STRG + f`) and search for **Breaking Changes** -3. Check your configuration via the [Check Home Assistant configuration](/addons/check_config/) add-On - - If this works you can safly update - - If this does not work change your config accordingly -4. If necassary change your Home Assistant configuration accordingly -5. Update Home Assistant -6. Restart Home Assistant +1. Backup your installation, using the snapshot functionality Hass.io offers. +2. Check the release notes for breaking changes on [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). Be sure to check all release notes between the version you are running and the one you are upgrading to. Use the search function in your browser (`CTRL + f`) and search for **Breaking Changes**. +3. Check your configuration using the [Check Home Assistant configuration](/addons/check_config/) add-on. +4. If the check passes, you can safely update. If not, update your configuration accordingly. +5. Update Home Assistant. From b1d966825c9afa121796dc460406990f7fcf6c04 Mon Sep 17 00:00:00 2001 From: rosscullen <35301905+rosscullen@users.noreply.github.com> Date: Tue, 1 Jan 2019 15:11:13 +0000 Subject: [PATCH 37/49] Update doorbird.markdown (#7817) * Update doorbird.markdown Added additional information on obtaining token and API-Operator Permission * :pencil2: Tweaks --- source/_components/doorbird.markdown | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/source/_components/doorbird.markdown b/source/_components/doorbird.markdown index db6cbd8444b..b8b3050ae9e 100644 --- a/source/_components/doorbird.markdown +++ b/source/_components/doorbird.markdown @@ -35,11 +35,11 @@ doorbird: {% configuration %} token: - description: Token to be used to authenticate Doorbird calls to Home Assistant. + description: Token to be used to authenticate Doorbird calls to Home Assistant. This can be obtained from your "Digital Passport" document provided with your Doorbird. required: true type: string devices: - description: List of doorbird devices. + description: List of Doorbird devices. required: true type: list keys: @@ -48,7 +48,7 @@ devices: required: true type: string username: - description: The username of a non-administrator user account on the device. This user needs the "API-Operator" permission enabled on doorbird. + description: The username of a non-administrator user account on the device. This user needs the "API-Operator" permission enabled on Doorbird. It is recommended to set up a new account on your Doorbird for use with Home Assistant. This can be added via the Doorbird App by choosing Administration -> (User) Add. When the new account is created, you will need to enable the permission "API-Operator" in the "permissions" option. required: true type: string password: @@ -69,7 +69,7 @@ devices: type: string keys: doorbell: - description: Monitor doorbell events + description: Monitor doorbell events. motion: description: Monitor motion events (Motion monitoring must be enabled on the doorstation via DoorBird app). {% endconfiguration %} @@ -114,7 +114,8 @@ Please note that clearing device registrations will prevent the device from send

#### {% linkable_title Event Data %} -Each event includes live image and live video URLs for the Doorbird device that triggered the event. These URLs can be found on the event data and can be useful in automation actions. For example, you could use `html5_viewer_url` on a notification to be linked directly to the live view of the device that triggered the automation. + +Each event includes live image and video URLs for the Doorbird device that triggered the event. These URLs can be found on the event data and can be useful in automation actions. For example, you could use `html5_viewer_url` on a notification to be linked directly to the live view of the device that triggered the automation.

The URLs on the event will be based on the configuration used to connect to your Doorbird device. Ability to connect from outside your network will depend on your configuration. From b71c931e4d71a2d140cf441e96e1519257a66d69 Mon Sep 17 00:00:00 2001 From: Nicholas Westerhausen Date: Tue, 1 Jan 2019 10:31:16 -0500 Subject: [PATCH 38/49] Fix service call documentation (#7742) See #7368 The component doesn't seem to register "turn_away_mode_off" and "turn_away_mode_on" as services and instead uses "set_away_mode" --- source/_components/water_heater.markdown | 29 ++++-------------------- 1 file changed, 5 insertions(+), 24 deletions(-) diff --git a/source/_components/water_heater.markdown b/source/_components/water_heater.markdown index 56917dcc57b..245b6eb67c8 100644 --- a/source/_components/water_heater.markdown +++ b/source/_components/water_heater.markdown @@ -77,13 +77,14 @@ automation: operation_mode: eco ``` -### {% linkable_title Service `water_heater.turn_away_mode_on` %} +### {% linkable_title Service `water_heater.set_away_mode` %} -Turn away mode on for water heater device +Turn away mode on or off for water heater device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | yes | String or list of strings that point at `entity_id`'s of water heater devices to control. Else targets all. +| `away_mode` | no | New value of away mode. 'on'/'off' or True/False #### {% linkable_title Automation example %} @@ -93,28 +94,8 @@ automation: platform: time at: "07:15:00" action: - - service: water_heater.turn_away_mode_on + - service: water_heater.set_away_mode data: entity_id: water_heater.demo + away_mode: True ``` - -### {% linkable_title Service `water_heater.turn_away_mode_off` %} - -Trun away mode off for water heater device - -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`'s of water heater devices to control. Else targets all. - -#### {% linkable_title Automation example %} - -```yaml -automation: - trigger: - platform: time - at: "07:15:00" - action: - - service: water_heater.turn_away_mode_off - data: - entity_id: water_heater.demo -``` \ No newline at end of file From 282dbc2ff0e147d82c9c117babe3404996b63a98 Mon Sep 17 00:00:00 2001 From: Eric Nagley Date: Tue, 1 Jan 2019 10:31:53 -0500 Subject: [PATCH 39/49] Update docs to reflect Climate changes. (#7764) * Update climate supported features and list available modes. * update docs to reflect auto -> heatcool change Reverted a change in the code per. --- source/_components/google_assistant.markdown | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown index dc61e9904f1..406f4f057b5 100644 --- a/source/_components/google_assistant.markdown +++ b/source/_components/google_assistant.markdown @@ -186,7 +186,7 @@ Currently, the following domains are available to be used with Google Assistant, - lock (lock/unlock (to allow assistant to unlock, set the `allow_unlock` key in configuration)) - cover (on/off/set position (via set brightness)) - media_player (on/off/set volume (via set brightness)/source (via set input source)) -- climate (temperature setting) +- climate (temperature setting, operation_mode) - vacuum (dock/start/stop/pause) ### {% linkable_title Media Player Sources %} @@ -196,8 +196,22 @@ There is currently a limitation with this feature that requires a hard-coded set https://developers.google.com/actions/reference/smarthome/traits/modes #### Example Command: + "Hey Google, change input source to TV on Living Room Receiver" +### {% linkable_title Climate Operation Modes %} + +There is not an exact 1-1 match between Home Assistant and Google Assistant for the available operation modes. +Here are the modes that are currently available: + +- off +- heat +- cool +- heatcool (auto) +- fan-only +- dry +- eco + ### {% linkable_title Troubleshooting the request_sync service %} The request_sync service requires that the initial sync from Google includes the agent_user_id. If not, the service will log an error that reads something like "Request contains an invalid argument". If this happens, then [unlink the account](https://support.google.com/googlehome/answer/7506443) from Home Control and relink. From d2420a973f10aa502f377605357d0c678e5c446e Mon Sep 17 00:00:00 2001 From: Piers Dawson-Damer Date: Wed, 2 Jan 2019 02:43:48 +1100 Subject: [PATCH 40/49] Update ios.markdown to resolve password save issue (#7747) https://community.home-assistant.io/t/ios-app-wont-save-my-home-assistant/74336 --- source/_docs/ecosystem/ios.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_docs/ecosystem/ios.markdown b/source/_docs/ecosystem/ios.markdown index d6554f1ace7..2fc5de550b1 100644 --- a/source/_docs/ecosystem/ios.markdown +++ b/source/_docs/ecosystem/ios.markdown @@ -31,6 +31,8 @@ The `ios` component is the companion component for the Home Assistant iOS app. W Loading the `ios` component will also load the [`device_tracker`](/components/device_tracker), [`zeroconf`](/components/zeroconf) and [`notify`](/components/notify) platforms. +In order to save credentials and adjust settings within the iOS Home Assistant app, the Optional (`api_password`)[https://www.home-assistant.io/components/http/#api_password] must be set. + ## {% linkable_title Setup %} ### {% linkable_title Automated Setup %} From 7f176e99762109392044f486305e3469fe39fd3a Mon Sep 17 00:00:00 2001 From: Ralph Date: Tue, 1 Jan 2019 10:48:08 -0500 Subject: [PATCH 41/49] Updating documentation to MQTT (See Pull 7455) (#7746) * Updating documentation to MQTT (See Pull 7455) As a request of user fabaff, moving change notes to Add-on Section instead of MQTT generic * :pencil2: Tweaks --- source/_addons/mosquitto.markdown | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown index 2f8a4d15fe4..26d93276cc3 100644 --- a/source/_addons/mosquitto.markdown +++ b/source/_addons/mosquitto.markdown @@ -55,6 +55,24 @@ This add-on is attached to the Home Assistant user system, so mqtt clients can m To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the integration page and install the configuration with one click. If you have old MQTT settings available, remove this old integration and restart Home Assistant to see the new one. +#### {% linkable_title Using Mosquitto with Hass.io %} + +1. Install the [Mosquitto add-on](https://www.home-assistant.io/addons/mosquitto/) with the default configuration via 'Hass.io > ADD-ON STORE'. (Don't forget to start the add-on & verify that 'Start on boot' is enabled.) + +2. Create a new user for MQTT via the `Configuration > Users (manage users)`. (Note: This name cannot be "homeassistant" or "addon") + +3. Once back on-line, return to `Configuration > Integrations` and select configure next to `MQTT`. + +``` + Broker: YOUR_HASSIO_IP_ADDRESS + Port: 1883 + Username: MQTT_USERNAME + Password: MQTT_PASSWORD +``` + +Note: .yaml modifications are not required. +See [testing your setup](https://www.home-assistant.io/docs/mqtt/testing/) to verify the steps above. + ### {% linkable_title Disable listening on insecure (1883) ports %} Remove the ports from the add-on page network card (set them as blank) to disable them. From 527afbf064cc4ac217794f2b83250b4c520d44fb Mon Sep 17 00:00:00 2001 From: Dane Date: Tue, 1 Jan 2019 16:01:49 +0000 Subject: [PATCH 42/49] Add note about not being on same network as Home Assistant during relink (#7709) * Add note about not being on same network as hass I had trouble relinking GA to Hass due to being on the same network. This may have been down to my local setup but it's what solved an issue for me. * :pencil2: Tweak --- source/_components/google_assistant.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown index 406f4f057b5..a582cb3fa41 100644 --- a/source/_components/google_assistant.markdown +++ b/source/_components/google_assistant.markdown @@ -53,6 +53,8 @@ Since release 0.80, the `Authorization Code` type of `OAuth` account linking is

If you've added Home Assistant to the home screen, you have to first remove it from home screen, otherwise, this HTML5 app will show up instead of a browser. Using it would prevent Home Assistant to redirect back to the `Google Assistant` app. + +If you're still having trouble, make sure that you're not connected to the same network Home Assistant is running on, e.g., use 4G/LTE instead.

## {% linkable_title First time setup %} From 8a268b1ad9b1a5eca74c565ebc0a307cf613dc3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Krupa?= Date: Tue, 1 Jan 2019 19:48:59 +0100 Subject: [PATCH 43/49] images: update netdata project logo (#8008) --- source/images/supported_brands/netdata.png | Bin 5495 -> 12757 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/source/images/supported_brands/netdata.png b/source/images/supported_brands/netdata.png index 73f9921703959808a27aaac81e79a193ddf2b06b..cc0367be5e48823fb293aecb8494fdc7f45e81f3 100644 GIT binary patch literal 12757 zcmZ{KbyQSg_w}6sh6d>#LQ1-%l%b@%ySuw#ND%{28k8Xg1OaIf85%@N8tIl)K{~$i zeZTcv>$leT-Syn{?B|@l&)N6+ky z1DFYJr>v_10HN#vfQ$oxOH2s40{{U60I+Kf0Fqe%K;@m+sv`{mAaZSWeMJmGdB$30 z&Q5#AS$*DKW6n-(-cD`KQGL!HGqgv&)o1M0=N(k%9sYqiyMOUnJMCp_)frpWSq#%o z{fE8UtSttpU{o`98uRvQm@)g0j2N|6o3YniaMb))&`x#MNp;3S12bkFFa(V`2UQGh z)?RzwL2V8rvD3g5pSM$;x7PSi<^P!Z*B4V9Qv}nI5`sZZENpsd6 z<4_l4W6n`$!C8II;a@L|;W>MQ^?!yjjW8FezUYYYti6mO*khdkD~=g6b{NkX$$u>U zBj4TK4O)!bV)n(iU zZJl4Utkoefx?JrgkZ)BjD7$2h1cAOVlO{8Ryg}BW>O;X1(BVfNkPYZI`D1>5{>OJq z7OUTnFkL{lYDx-b{-4uDFbiC7WfMODz$g26f`FVnYD^HvUqwR^XAK_&BV~P`t@soG zXoy4gjs10Pg5ci1UXCvA4sibvZwI(Tu!|!AI7e6InD}lqzgE1fO|k?#if6=*?;oHt zm$!xFzN)12*H!8n;Boc9Wtk3FP*QhS`FpodqeSC(d|eE~s@_GlY%}7>WJTSCwPWY! zA2HpnT`e*#1?5L2eohb8sFs;L4ke5|8)_o1zmAN$J^$ji7eN!2zq9`Jh>YFBBr}xB z>4>c4JXGd$RM5>$OKL~k+q1jXo7Lnuch_N_P&=xT%);j!@f#PG0qH$>uS+`5&_R*w z@cheT&DAjVi@n*FQKoKwSwgGck>sGgUx206( z;s2fZq$6Kc{Mv%6B*U=sM98(GCBxM1Ls!|j?od_zylLI^j~e^ABm+0cX^)dxG7`hk zgW-U^_T)}QocE03q24{z!XqNbJar>t9;XtNn{|JzJc0(1J;k3Gw2@so$>m04Cg+$ zsQyEF$K|J4eswpHr?D5fyjoV+-U<$g7vm@_8r8)nV>YM)o=j zddB9T55rrkC@xoVa29=Q1E~sRcpi(PUHV()o`pDhUc7s9742$g5Y^F%Fot%NAWgyQ z_lR6E?$1gwPkg;I^g({j)*l)^ z#!;F6#9p3m0;8rSl8NPMlV;gG31)`9i{_(`i~iRAWJ=3GK4Wl6m0psFcDX8dW&-) zrCB3L`-%m@E}jLaJ=_hS_WF73VsO)R1zGYC=X8T%l^hn+sSEkM=6jxgBEHx>4e4ZY z?nS4*DzwkdJx|(jX(X(&yBik8rQ)5w|CG)XsZ62JzN;z3Sp5c*ZSbe z{#D?Oq;W|K&TeTR>Gq-jO@ojU=xt~vU7U;X$>UTKdV4*CkSDE=O~hXbRcUOKvspwr zb+Baz6cX|jPw`RAk5OLD7dUAxSBP(-UiSGqeXKiOahCBWKz_Sl2Cax3P~<-D=*TEH zw&)n~9#hJGs_*U^^=U`ytk{|CfX-6_2hVe(C>gvopC$aApwU+PzSyt&7>5XcqeRj8 z!QE?fsjBgc99PoxmLcs&>yb zf(d&miP8w0D%mbGpoK^`W(rC-3r)NalCRIP;(<^hTOekiw zwJA}mIsheX`dPiAUQ6Z=lMS2a2p@lp*q7}Egzs0GP#6uUXW6}9wSG=$u@6ZYk8w*O z{TRW4AW9@>?%Zb!;RwJ+V@2d@EjWzu64}x+g3aMVd|b6!RD*2asNt%4J$3I z?|B|Mb}OZ`bAP8u2SZ$=#?Bg#)CQS;bnQkI3vX-7oVF6XK7}o(cGJnp*8;!H2-*Et z_HY4Zt(bIhmH9!iVxau8U7iHV3NmbCnoEpZzoRdY7+!+BC*lI$=CATIpfSDEIB`l~ zt+rt<=kZ)1aOaG0&&k>Rp66zN87=)VOfeW}h^dEheDcIwfG3PpjMLItmJlF9Q*g>2 z!Il*a0~^ZrVY)vU>_s|X&T&=B!ewh;7VVE>+oXm{Ix9kn`sJw|GN)g?#(PjZ7A;#C zTbWe8!xdB@J@$ff|BN!7JAyccA3;C?Mjhn@(qVbWE=k-pREj3Q8^Ts*GB)YH_$`un zx0=2mDx~(lq6-C~C7a1Dx+JTOHH15zl?5J_h4deic$VzHQ?^w+D(Db%P5sm*6yV7& z=K0jVdJ5gisJV{!G>+iAf@s%b(c`p59F2EeLz~cX$38?; zVn0R4zKB|XQ8WKxDmqG1m=)MJW1+=weywzWD>4+KBTV`#ppZ@*@awX_31;Jq&%x&e zd149loIQIN!?#7auA5TC9fJQlo1!*eJF&iH@h#N`NDeiQ28q8$)04~JCoLN_odM%C z0Sl18SBIfHj(S`>m2yvYGTyS1Qg%va;BMwWF?v}1X#i5e8zjP{%kSChQylUM5@e#L zO!v9uF$pX{HbKGnQX}Y%peIRAYk;GWnZ9a^k*09V@;lZKi9({t8?{MY2e-&Hz3|Dv z^d0Q|^#rA#c*YO(&}>V3)t543dIIwbjLC9Ux+L%1wi^b7#Wpr7T|?~k*-LivY9;&D zsLk!2a}R{JT#@Qa0>S%gKc&t>Z;`>n*B3)#g0w|Z@ZK2P`g1b)F38_7(~C5 zukeYKjEy!9pN*7mqSLz-FQ>roqa^7V=fbahLPgBInYh7565G!`=+xFpI}n6r&^el3 z=h(>;PyOjN_v|DsXXASct6PzaF9N4O6YI^HxuQ~1Dfp4UZbvN_gS?8>l|WYo=il?g zJCi#k6vZXXsiCR*@9FGHm{&w%tM}yeg4r0K{07&j8K(^(e{zAEy=`#x3aZGrUtB(a zzU1{mqGG%FnZ@gsV*Eq7a*|WC(xVh1p{IJW68Ln=BB&BEuFR+P%gvYv0k>4u6yi6} zYuOC3&3GRLTB}(7cwO82M}*F0ri@dfcEv&Y2HSTyMbuyHnM)+I6zZLKId%xHTyMqq z(r3Sg30*1cYvSH;DBf#%u5@bM1tF2nOWo@M9jH(lS*;TvpR9kl$|atqwcbO&1_jwV zLC?{-ML0EkJ3WJKWoz}?fPrH(RXLaaqXgQTr+jG6jqogkC-+_vGyK+C?uyz~-pn}_s593Hv0=)G5h$kx?EAErQ`@PLWlJYYYsgT9b^zVusa&T>zeaZ^3( z^Ljv#MPh9*C3ed%ocRG(L+|^kWUS7n-3|yJLhIj&OnxPuqvX^f?+l7Tde%;rGTbNB zwI+<`s$|KNfAH2?{JQ*x0Kzbx`+4y2u_A6@-89SDwTyw!o7-eja&q;fL>Hx=z zJ<&PX1!nBVvSC;7TKWr7>~}_oItDo2Y|PEC&4`5GP81}=l@EO-1~^}_xC8L{G{h77 z$Mc@_<}CAYj;JR-o7uHG>l%|FrwQB?YTZit5hObYbPLBa`%}pY?QD=Bqn#L(P0TKk zQis72mm=uRHD2XSMOwr3k)w)LduzuHGSkm9Cl%?7evq!!s_p)KqnJdvCh1StExEx| zkIp%ivZv%w>0G@BZ;hno(avRJaK_WvyK&I_V?-^pN8%6qM;Q~ zrI?YyhDsATIYe(jTc1hVOZWX#qR3@kh6|n0zNN@1y6!C43kL2$* znZlc{<8fFk-w--Iuh zXOO!AEkm|wHzJYWom8@AHEyVGE_R@_HD#!}k4MW+PF$ry)I5gYSNE8CaJeWa>Ff0m zTJPm0#295ZMG^(%P3;;D3I5|><(Q`*1K+;t? z#itK)k0D9~KYHVUMx;jMyusOd6*jNfjZDOni4}YQlt?>qkuMh@gwbe`XPzzc892!^sNalo-b$Iiv^iTn6&JwC z@@GfrdUnks&pNU+tj~xvX{SP!S$G#afN$pe!Toxq%2jDO)=iu31I8Wxc+*If4Ax8S zzSIwr*5u!wze_RhAg)z+^5NxFW`(apdI}@Rlm+&mt&#AsKc-%TJWsT;PW|e^lO=#& z^p!HC*pGn@m2rx2(c%jysj`nae5)b^EsBBbn%og%p56i}VW-T5)T}=q=nxFK{MceE zw0Tgxu#uM&sN&=I$exs)upG~l}? zt{rB;@l=PD$&jPoK==Yn$Vk322+{Vo#aQ*H)MEl2ddG_K(oI#x zFDn@NKN6O|Qb4qPN0Ox7x3gj1R-GS|3@ay2 zm8Uk6?*8u0`i2lrUoU^{P|K6`t zRGD>wRsUGj<)!)yc0=LsmcQpv&}3uRNjn_mNCL(A1adn8J6~b12Uhv+^PWW-mC4|{ zzN!mS)8Z;^idnYqB*x&?bA5nfe|$Wv!FjEQ7Q{_w-06C3x?D0YM0)vA^%u?;rl$ao z39>wVY#sDLgRF_S%IwF~3zD<+)ztal(9MQ%q(DEl4Y3V=b+qM=Vy5DQPZn>!(v#P2 z+zJ&jz9vQwe+l-;qs69K!6h4f@n)75Ym8WVeL<~o=Je6UVl;6M1Tbw(K-MtT#O^XS zGQOKSk3Kc~x)!=1`OexvBbR=F$mulG>`29Pk?i40;bSt;L3_!W0>Tg_Lk2=62niD2 z3 zJ3VtfZreV%8!wf zloGz2dX_VdMFPSG4UJ6evKKTw+5x@iRgflX@#j|MJdDmEVo}Y*7Y`@c&W4zp2Pl|y z-aTLV%VtEXAp4f&w3#%VhwubssB_*TLq|T+!+?!gGR0L7y z94wM-0z64%QyuVQD-3#k%t^p z@3!aJr^@QaALBN8A@ZKekOPZoz%J6uhr_9 zQq4#|Gk@Pa=G{(`N>L%f!9&k(Yo_0-E*o-WssS>82vKS~-FxeJ!(Qc>-I2~X;oIe*)m+tdq+(>UIdl| zU35nh9G`JM5q|qUUF-!O6L}qQ@9v(a6#O*MD^kgWcU{GYmTGvTK}WTM7G7q->-{>i zmB{8(JwpX)y~2A5oBuw2(rT&KdA{GCo%CyoU>a*pzaD>F)UXPMEaA{*`JSLXuURJINyUrL zu~hqt-R4V>$9;=}acCj%Kmez#am$@?u1ru^zt62RMJ3A^h-of># z?l_CK9w-fI48+Zt2Y<`Wc>{KvkKJKOM?Hdx?8`+l!@*$1E5)G>XXWH)>RgB!ybQN@ zANs8+v5yPE6K?9S3c=)@OcO2Jr?IVXVK~7Ro#dk6*_)qP}l!N)BM~d5tO$tJ@p@kCPeAO9AqZ2AmmsXza-+;3#K31d=k?TwiyhbnM zHv3PEIlMV@&?G=!x6WhTa(=XO#ZOzFe^bEbjSbvCBrB-J=2cgBj^5M`e-;V=3PUQn zX^@QKO@6G5_|$o+jS0quN5RqXSXtqQ^7ePztKgo}q12Dz*p+#5!X|iz>#PU=&rUYRn)$o8($b&2pZ}(nvKMgwurQ=`>r1mKw2^_Q{7&DAb1ohwCF7}k^Jh2G zC=C6hF64%bjeF}fq}jM_;AuiwJP*o_L9jcHq%JO@PKZTp_;V0Xvn7@C<;Tj|pJhr* ze?ZGISs4t*3%QtYZ?Q_Lwm z&2C;vxc}lKk=SD~!>~J_ywlAOVK-f%j9_a1GWtF6H`GTtW2S=Ey3-MG=QD zR}4H78Yk31!`lIcSaOCoT$!Nw6ck@e^4t5*YTXnFnHMPW<6|=j+L9P#;}*Hqd?z+Z zl-@DVeTQH%woV;GKPyEfvmd_2VtngV~{=I^`RZjz4(~f zwMQax#f@dH%9SnBzF^ZOg_SepnsFN60y5{Ap7yTt*i37-g!g$kc;p@TQ|R9vp`aJH z#ml7U%GTzDYn{fQ0vA3^<2@Xo&}Kkm2mauVxaTWEC#~W--k40@8A!%4_VolQUj{Yd zghjgpWI89(69Ffa>fW=pu-=~qnIqf^xgvBW27-Bv+L15yMLj0pi<$23tm2aJFRR4v z4u%@f6j*j1kvw=YQBT7k82TtY)34_t%aI3ZO`Fa=hUG#PD*Hd7>RzaPm`C2nK#fT{s$w{G}#07B#3Y+?xh88odYNM1|yvbGq{Nb9T zj*vg#MRV52_J$rs9nv$6hx31sC3!uSEVOd8Z=D`fSrRH8M1dte1@a1G(E} zCJXqjZGM`lFXc_e#(FL!Xj=d>sb_MOa}>s{JsJLr*Bu?u9b!f{zWx_ZpPhAN`8C^e z{zSJlb0spV`cTQlD_W}XNLx2-;E5ZVu6c_v5q)a>IcHS_ckL0Qkza?%pE@Jil3S+f zK=_*7K7J|yP%x?}$m$2rAH2P>TIeI~BPROQc>&!*^Y_HDiCACB$-fqxB;xI1lX%mr z!so(pb$cgM%yFpr{inzM;luqy>E--Om-2@9G{e%uQl<^2n7?2CdvH2AGz_;x(O>6- zBi0%75PT2b{*D`dImLUJ4luT^)3}|5Ex3W`-Ct2vdO;UHfckLzd>VrenQ36_ox!;0 zNS;8cb-{2nz1cw^f7VzB>$R3_+i+;x)jE%uVarjP7c@*N_v**G^y$Nyz|+H8mgN=GbmZ*-|X_eTgX7TN5N z27)!(#AGiTQgJItrAr%cuT3TkanppRu+0$^Ig|NU0^imA;z0-eu$K?@vx;M%V3KFhcVNZgDF%quGVLla^)Cp}+HGOF~iE1bLRD>+qF@b(xZ{ z*F=gzLo@I(_VB489)^H7BI(gV`@u9&o`dTT1@xJ8{*d*|G5HpwE7V1U zT(}zK5zf@|y(Cp68_o+iQ5N35pTA_3YU$yFAiL`C$i3C5&I#6ds~?{!1o|^Y#sX!o zM|H+y^d+qKhpt#X|3(gJkHwVWB$Tbo>kaI7Ceym7m4aI71q^+~KlnKBX{CRE|5^a& zg#{IuvE(jM(?k@J1?lsgiH$b;DO0#n&bEs+>|+F5*cM9@3&e{DJczR5=#`|vUj{qG zd$sNx@H2MM|7WqZiw)4Dj&kBafpZvKi9Zixq>p?lK3WxN)~) zbejzbPNdWCRNigfMlyJ{x9Agub9ddoc`wAz_eKn|T`A?a+uX5f^_5*h>wW;Uc*%Mq z&bj$5@0)dyNUV*^lPiAa*6 zM~HVfb&n94Flw_y(7l8F0}$h#^-JKgjO2RSbl;o zO=a~0n>C28-Yf4D?HNRqx#y6_-@LEv^-8j&5Kn!3$_AQ^(hPs%taR2J*nIGKTkr6P zCu!{;btiuBr2FZJ=&6|i72nbZaO6B>cWcJ39`^P4b0?7lW&%^6IR$Ydx%+? zT$hN_kcZZ)nG?5K&0h6Y{)cg>>Fku=5^8w>4{a{iePxFtqE||a?Y!j#{@_0FCkt4~ zswJ;KZA&&JIh>*?gY<`&z@gU61q1^APq0Tbka-W0Zl4@WNd+A7KqSZ#Y0>X6m<=_2Dp(UH}bMXjybYrKvl2${Y1)|2I_KX zD!|i+Bv1g?&_IMph9^t@2vo8;;zp;RfUmemT@z8-Mo_MSvQ+5d#lX@S(umSOo$KY{LzrVZfnm1(+0|kJH9t0h(bp{3IZ>;!bG{36K|eSPX*#9LzsR zp8(!upM(GqTBGaQ9w)gLna! z`i6NKBu4%gK8YlfAH$U++z||+j>z6?%J6La-2N{F@LZZgXdgZ$Z0LGdP zK&|zQ01k?9A0qo(-XaZ>0t$yqki6dAr`QDS0VZW}#AW?m3_X%y1q(MfGVONx*bfjw zQjv3_rT+Xw#M1o2E}ldPssa49>I8?#-@-vMD=A?=kuh124fli1w{YZJYyQM`hR>Fl zR1Tq_W+jo+^s~Y3yx-p6z!#l17i4cAQPp?1`y#r!S}znWPTifKhHWC_E^=*%kMG#( zNEGPC$Q)0@bx$6e#IHaO<01DPBT#Gnw~iDsoZuU4lUtg zau(;I0GNNuv%x{q%$)xqL#GBtO3Mz8`VemR@UIE3GN1*kyXtq1!p2=;jnxH-mk{Ev zaD-J|sYV6CFo-|YH7W=X13o1AMW`t$TC<|5(zYevumE21&skd-kS_rrwo$xJ9;Em^ zVGuPeQ>l<5PAmnn=A>Fg$d*FpjF{V(g?!y2pw$**a7L^uv?ESHiucM9pUK!>D`VO6 z8?%iYQ=h2<_@g>d*fvZN=^n}nw)cx+L5Nw9gFa;wC)jczIGwU!85%fbom~=g6r8z? z6^J?YJ+xMHCa77wM>@;BG+^cNnGirVT0_N|yX_1aD2*MqUZpP}X3O>Fs~>HLp_P!2 zQ`|LwS)$yD1c_L3`Dmj*N%Tr%LgTm@!@yhXxx7x0{qg51(^X4|buk2ogs2f5=Lf|} z(V!!O=Zc9z942BR1MEo5i55q?TcSbseqfvwLVAR_H?WEZ#bG2PxRykj{~{d0ya=%| zpeq^z!y$sxizB^P{JJ7>8Q`Ivup?^<6IB!OoERs^XU#7r+=Yn+dBx?{tz znO>z0(>!K)klXndvhs%6R-$)%-C?5L5BLn{%XlM&gJ4DQU{dsc{1ET)FMfasxaYfT z0Vyi}pd&J5{^0azCr}F~_s7D6uN&@LfHRcj)1zST1<#TltVRB+>w+c9Xkt-07xG|yb5x!2OJ3$dl~cE@yAiC}qf6^r$}~{J+~Krv6s(DI z)~pihfUv-R@b^F_H5RAxxr{jvCh(|{n9ev~2By%0?||UVd31X%3pZ@`T~_6o``~pd z?#{oJ*Gm~)Uh~yGe{43tnm(A)3{u)v@#&5t{f5H@*$-I*V^=>lu+N9z^h+b}gZr9Bp?8V@d)9qi#YO)z6er*PZ)BIqh%l&hW zwLd#p+;vsGw_9$}8~gXzW7Er<|5j^`mXYl7SiFt!`c6T+f1Cb$VB?6I$AZ2JE_z!! zdh3`z`-!!PqBxEbB;H?4V$Nt64bxuBHBB%mbvn!}{`k@`1#C4V;Clas2O*JeW&(^; z$qU@vtuMn_<-iR7I-Uo}sYi5jJQ~C!)&5!)S>T2P_IcnlA2#H9PCz>F}9eb|c`PwxeAQzKEie5TE1>aP-t(-k&l~QnKGKDRh1S zG)J8Qm?|QCWbMXf8^vtgS)HT5EbGz_kKunUEOHi=I|+z=-cOqX`6TcWBwB&4dyQ`= z1CMo56=PL2dr;eW+t(usyfK2zn9e*lkvNQ4rbi7`YA zEr}!NorO(7L&57nl2?-~Hs9)VNEuP14YxIJ0yjd9rp$Ci4ii*iLb)?>f)~+j1Xb1y za_Tn+VxPI*760zz0;OAn6G8yO;Ve~-JUFx`#B&L> zL#TbQ$*v!RtKLCXXvb4z%llka;MMOZKs!OTfRy));4FPHb@|Af-km!U6z_dQX`y&phcE{D+2AaG(AiWY(F3XWO(A}Ge-5eX$&qVdB`pvPmy@%;h|RAE8bE-Duc z$RX(EnUUwgWu^V*bT_5#o77y;GBxB>DSp=(8x>}esD|9?&$B~_ua!q$$*@@pb@mep z!s!cc7;43S$8de|Lz0lxew4!1&P1|VN%cmPlIFYt0>G%$Do!jrXASTqE^=2*X$M=; zUqlnfb50QFHAuBHQ6oZV#cr+Sd&EyXNrAouzAHU^;Oo)iy3{>E#@*Vxh}{5PF+L*{ z#Ljt+I#RA(b>7RuRt-MlbaHy+p~wIF+;4jar;qsz+41H_{-xRbv1r`HI&{;EszK4x5=<3CrWXD3r`z84Qy<(}W9LchCPK5Q$R39WGB#f3vv z;Jrh+mrZ)3>(ze26e{rHOJbSnwrrWm59KYTMc}Mhwv7!r0#sU2f>nCrpeCbMu|8BXlwk99|~`v~b^csm?X&Fc_xWLnM{ z{z*9Vb7W z={R&@`Y7`IlEt<2UgONEWmMSB5B`VC9XZ~9$3tE-UXhDegFW^KRUpj0tey0XH!$Yl zX1D?O>MFGLk;x7fpa+NWl>Gj%Qh~rWe%2EE4GwYdc>!d7mw$+sRL4bfrGTb?r>k7q z>7gYF-q}lH<$?`=x4B$38N#8wYhBlwgv?Ohu1X*e!t9LC+70$5(j=;dCXD{jl2sbR zdqD-@2kPJ%qnX@KmAI@S^jHX}D#$Y!519ybgDQ6zz($~6IEOiwH9dLki#%^L8R(Uq z`!5P4?(I+nQ?c!{n_A(4xC;if^ccz7O4Nd5au`4>*SG2pl*+1&i8NIbB7%X3jdM(l z)|6NK#KZ!)XV`!=l1l0TgX61CpWx;-)2-_NDxhJz6q0eU$* zc{d7?lE3usyyg9dK+2+Bj8kh;Dv9zIcS zsj!5+4We*dD>66Ph{i z))07N>%<(JRxuBXqvx9^Z-#N?P<)>6?_kBzp|jH0M&pn%(z21AptFf6s3h2cMzZ0; zh-kOd^_=W>yYjO{+$qh1?c{h%%%7{tg)C)0*0k4E)E0omC9~}L~Y8qDhlPYSu*&7e8BNGa~GENEz9R1P*w*)wFR(c)M-YA zyf85Nc{xK%Yk|Ht_*E&D_|Yoh6@R-=^mx8N6ocUs;iF&Cq`FZNukuErMMDNz9i*LY zsdbM9Xf2sfA3Bvp?G@v%tiCTg8)?u-e$yJRl`jVhtnig?)TqL(MXrU>-PO-1eneP{ zeBSTAG&T9z(J+Pcr2DMq3+}5|ypwS@OHcm}lbSEilfj-84e{yc`>+qL#4O`JDIzw4 zUAv!*@IMXL6rd$se%I7;6dfFM+(e)$Ab5Lq%y{O7BOH1YM5bXqfX`0V+P=F!*z~eU zg>&ox>rK>c_m$s3L|ArkXPY)juPKko%2bnFETPuz6HH3 zT4}zz75au3AkBOoMJV$*B5J8$??_y!9ktvZ8Wti&KRj4>&cMV@d~MJawUDsdzFxM7 z9}{`^`Nx4}d$Nz{1^?yEtI;ZV3O|Go~{{Moyu{vCgfc9U9e_y3b z%DMRaX*>Ap*?4%nI{@N5@PFgp!D9{#i}`<83K$pqE*}4NA}NSzEeIEokQ5Y^6cTAJ zCZ5EQ$^VC};$h?Dpzh%5^#A<2-o@MB4giAl*8dQ|d<;1`ziJJAQ`yu7AguU& zcKBqhWNL57A!Kj`q)4|tgtbl|J~TTy(DSW_z6WOrsf<$P19quM{r|{`rej(FDvFv4 JALXoL{tvJNQuP1; literal 5495 zcmZ`-cTiKow@xD=^iF_K1VQNuMhQWB5{eWlQk0HBL@9wFT?oAyKrHmGU_n5NhyqcX z1u2Sv6p4TkDFR9t^u^zM^Jd;3Z|>ZCX3yF0+i!Pg&N*|_&RQCCbBJ>Q003@N6TA(} zzW(>JLs{Qi$Hyfs1MxMmFaQ7=vN#Vs*jQs3FB2OJ03cEU0EkNj0QOm~I3@rPiUI(Z z+yMYw9snR3RMcjDniYV0o-xJ){{DN)+N*O}9vH>cf&iOkZKUapr#_N{?M6$2`lhHe3_*z z9HClqTnR8j3jaRG;P`>gLAcJPdbQE@*jLPDXzBiZt!Ldc)4JCMjFFs>$D)Yuaag66 zbBvFmT=S#Jn)p_7mSAfwwfcd}q~f|T73}ZgIbXtV^~sD1v*ja>C$k0cVL#wK=Wnxo z5um{;6xN zWr#j_m0n*?XSo9L8@I5p(rBXa%;uc#*ASKb6=rAjghu&y2n1Zk#i@0y=40Sp1yt&JDaDxN1jt? zwgBDX$kfb1sLD0BoMq_Ay9G>DwOCL(f7=PB4P*Fc9o2%YcyJW)mJ19C5bW9NsZ8-A z%MZ#yx9RG^LpdLt+CiFdq(2DlN$y4;UpEFVhYV4ld+%@*`N^XFg1Q?@>3#B_JIHRU zrqsrS;g5-)BmXXE(VLRg_2e@rXpNU>Eohq00=qHJD<(^5-uD-2RY6!-9QE$z?;8eb zo@tnBHT8c^7wvvqa+~vhvn}MuJA;(|%2kotUX2-@K%xQMW!`m|?Ynx&5dW`$r|Gua zBX}EBQHJ*MAS(UuLfNl9Pu|p9I;si-gkqU>MXIV6lhW~7oEnzC8m7)e!}9R$R?ulk z$|<*1Lc^2l9y)*DkqXX%X)Wf(j!9)utfKw)h#QiOR1V6hvi;NesKtnJrXnlrM9yyf z$OOmmqTj{o@^n%c%cVV{vqt10tJ%~sLolQBWpcuww>b{*l$)oh^TNhRFNp5ZedP5= z+Gm|sJg6Tnj%vwMJQUyu&AaV^Qw|r7?MLqb9b^uj!uY(TKT>Py!gQITxfgn=u664t zk?j56TtgD$d5o|=U~b$V{m~U*!dc9nU~dR(cx+GJurQrru0}0QTMjW;_Y-H7qfzc5=!8vm1R3 zecl&Tk6KPJi33jeg z3z=^oz#zwe1pJKhyq(+7)#X;NcMuyX8liHlDjGojHB+In2r&M4bMLH+iv?G zMp%ck{?N< z;pLbePhhQr7AMH({y-UJn9eDPO|&J{=VA;WJRIJt_fMS=Cf#+fQ}x63-b7-SBE8U5 z(dz!0)2VIY(=C#5_wLv+`$WDIGmwP0A)7bFpaC$~q=K(skGExuxq}qdbePPqzc&4J z+Ww^aO}=5W=PM~>$MYA&_v^FGHtsCBy8GiN?|}nXdVzWR>F+c!sSC>5)C*}luAx0A zd_jtQ<=QKbjHkn@Ege6(aPh7F%V7J8jbhY7k4C{lkUN2Ove|!S*?Dm7*L=(;p=kBn z{3*Fro2M|;L5CKAo^0KRm znTrcCy^k`|F_-CamtF5*RM%aBb|k5Nm>%zgUlbZcQ-uOd~W6a?Ze7l+zl?%#4kEZ+4)ZIQLL$>W~y$qoR_}Bbw?X*WMg;G?oWe^YV z<}6yhCt4<~6TM(eGK&)G1Q*@j0*aT&RQlhgLxCIPCBlyOmvTS$vVnM??u9vUn&+Mx z3_+fXpGPcu4uW*kWhUB05*4?m$JTQ_4L_r-@YhIgk+1S%n|x0(Emj(T3DSFS0Anr2(NEhrZy~fxOz9ki*x-w3CoC9~TFfcaRWwx| zJP0mI*4L|5A*ugIAegi+vu^y+PW+Loaj3 zuTrzvH+xdOI_SlUF;7|1MBMu_IssHSUzTvJ!Go%tkc0BG*0p972zAatY#>G2OJ&UH zsU6IXcFTM(+!`Tf05NqOHGUx$@w6~LmFz0SOzqsu3r(%U=G-^QBDD9)x;gL8mhxYi+M`sI+0}kPp^KvI;~u!~WRXyZv#2 zU};?K{@PnkZ$4O_J}y~~=FL=V)AWgPmUI_hM;jKFyp`oasoQ%ZVX=DaQKU-}Gd&Hk zR^asZ1v7Hobs2v_{+YbQfSmTcqLEt`bTx)JBXAft)!p)(8IPtm86;vwfU#72XX)4b zy8=&ycR@kI>*q&dxhEB}MN;{C9Vz_R#I%(2KPwCZV`0&Pwcf%#SPWr7t3ul4>~V7$ z3xOlFgrV`?-y5-J^7QtaGm+=M5f;h)W#pnW@!Quj1=zbuaU&B5Y9qux&Hl%0+^5s` zSA|+F89|yZ)0cMasLGJ5@Mzn3mjsKFPBzfs-6>i%#K*BMN;D1oIi-v@Y!7^3WebbZ z-McfKzWkfxIUy4X1D5hk=$NDtc?3-${I3v(W8$LVV`sS*-yf3R9;#xOxvLNR%D+5% zYV)c-4t^A$h}u7E5Y1;{TUxY*z8WXVYy{TfOEn~nrT2^IgMhw^F+)xspd(k04SFzh z?FWrQ9;DN83=YNx`Zlh#Fiv-A)yCat6jm&MSHvU}#e)w!hyh#=6rxJfuQO{J+Fttd z61;G0y?-I^x^LRZpkL*Ii_(0)l$ekQ-U~7nYS#dDqkGQkLAZ5Il3Kn28E0UNXRn0i z!HSZ;ptFqHF$9J%<9Q8Mino*h>)nEQ%VX+5AKw^8M1>G2jjtEb){6xfTeeeY*}V|8 zn4jl1$?r~H=3b0OvPFYpxL&p@bjsc0kd3IS2c_i`Eg&>w9h*RdIdK9Gb~!HApxv%B zVEr?>W_f>(enX_QZzsC(o}$enKsISOE3({@AZ^x&%q!UJ3Fh|~ z$_b)hGX6%*+xA?hVoa3t*i;C{>9%LrG6$_Lr+X>~DdYU6xK}dwvm4#MaZyGbE#ctU z+SyzB;_MZ?l42s26^=k8mH0BF_iEFF*PlqiUt1KeEy^&ghUU#AP8J*;16`8cxWZnn zhD@OeoEZ)!@DqSana`=Q1Y11unZMjUn_D59SDQeyA0A0CBq|{v%oHwGJ0n!1eWlx8 zm!#3SGKSf9JTa{f^GS1mfnlIAupYsswKA2@SUO0hz&U~^@<*n~r6`E$v!Nx#=D<_E zi9KE@jp%YCr98jslBm%DSR$?zFhhKZ7|leW`-vw42aU&EiG_H0m1yykqRfEo2uT;N z0H`aprOfEilCt(Q;DKvyD~4H;y;Y7*F&O!T^rGkePKZ5Lp8i)3NLeg~%6UBg| z6&Y)P0aD#*-WWuC7N8?Oa`kQSfQ_7)%&(zC;F+Pz4WjKNxf(}Tf@qR<{9lJF>XkhL z_e3Ryp~a=bWG*&6<+?jL{-mvJ>9XaFX3|igw1wqmUZV1Y`N){>oYu$4;;7Q4E#}?G zzPhRJ*9YohF^_wvNg7{Wm`#2{{*QLd8p{>^Do(`&@#xrk(v zv30sLtw>Nl+n>2`I5~X!u5bncTm@=)5E zg!WLj8 zx|KVmJsWL@O{vUT&nMlCmc`wAodI^&Z2L12ulB%ApHL4Chwhd#w*0$WZ3=}TBrc{q zwAQ%<5z1w;c}OWNRC5832-w)VsE*?FCT!SyI$7t_v5@ROpUp7@!3 zfpK$6V!q%(Q4;NxksUZ4Osa-o2xP9EJm2|)d_@zdGeKRz__MFbQ`(wzcXyPjt5pWh zN0tDdky}`boemt!J^fqv&QGXuh?R5M`YXmFZu7gLp3&m?GP_77`DrsWY>0oPc~7Yv zHV8|sT=B9#a-I9njI^U0)0g+X{~^*K32lB-!u=S|dm=gA+hN_+WwxW{rRp_VrSxw# z?+(J#OP!q%`(CaOtCEpo8!^m@IqxOAZx8!FIeX$p0%n!deGLoa5ec-+ zjI-7%M(r^t>bDZZy5*JIV!Zf@Ir<4 zQy~-!g^)Vf<8y3Thh{RTJy)Y+ymHPCWd+WvxJ>gMvi9XvDu{_BkD;B0fk1V< zrfhMXLWJepR#Re1nt+M7^%RHTaJ#rMa1Fn>TUU1LJlDNxR^{EWv!CWOjOdL~x@3~mV7-xH|0WBOr@F-*} zO$S*bN<2X5OdKnbWd(CoV|bI$1;@M`;XV$)MGO5|q2 z4x2i-NAc%^%w^6^d|$ckXA`tCtI$QviWd}xHE;$Z9Fg6qB>~NzC;Z*0`jaed55yA@ zilQQjlK&uZA#t`oh|OIa&3CA64@pl*8vmGgYDdHN67PkCz~&1L>C!+*s7kL!q;%(O`{X;J%w zNQm}1fvCwVXO#O!lyv<6xISFnKFlkSRSJF~wdeMJ_&ojSDy`zko#F*?a=pkBhpb>eIyCDwbz}8> Date: Wed, 2 Jan 2019 02:27:20 -0700 Subject: [PATCH 44/49] Update Google TTS URL (#8009) The URL changed on Google's side, this updates to the new address --- source/_components/tts.google.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/tts.google.markdown b/source/_components/tts.google.markdown index c3bdf2d0cca..927d672a7c4 100644 --- a/source/_components/tts.google.markdown +++ b/source/_components/tts.google.markdown @@ -12,7 +12,7 @@ ha_category: Text-to-speech ha_release: 0.35 --- -The `google` text-to-speech platform uses [Google Text-to-Speech engine](https://console.developers.google.com/apis/api/speech.googleapis.com/overview) Text-to-Speech engine to read a text with natural sounding voices. +The `google` text-to-speech platform uses [Google Text-to-Speech engine](https://console.developers.google.com/apis/library/texttospeech.googleapis.com) Text-to-Speech engine to read a text with natural sounding voices. ## {% linkable_title Configuration %} From 4e2055ae5e62520bfaaea4e50d3a74e2413912c5 Mon Sep 17 00:00:00 2001 From: Chris Helming Date: Wed, 2 Jan 2019 04:31:41 -0500 Subject: [PATCH 45/49] Update google_assistant.markdown (#8013) clarified some steps as I went through the process --- source/_components/google_assistant.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown index a582cb3fa41..af8e8dd730d 100644 --- a/source/_components/google_assistant.markdown +++ b/source/_components/google_assistant.markdown @@ -64,7 +64,7 @@ You need to create an API Key with the [Google Cloud API Console](https://consol 1. Create a new project in the [Actions on Google console](https://console.actions.google.com/). 1. Add/Import a project and give it a name. 2. Click on the `Home Control` card, select the `Smart home` recommendation. - 3. Create an Action, under the build section. Add your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / IP address and the port under which your Home Assistant is reachable. + 3. Click `Build your Action`, select `Add Action(s)`, and click `Add your first action`. Add your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / IP address and the port under which your Home Assistant is reachable. 4. Click `Done`. Then click on `Overview`, which will lead you back to the app details screen. 2. `Account linking` is required for your app to interact with Home Assistant. Set this up under the `Quick Setup` section. 1. Leave it at the default `No, I only want to allow account creation on my website` and select Next. @@ -73,7 +73,7 @@ You need to create an API Key with the [Google Cloud API Console](https://consol 4. Client Secret: Anything you like, Home Assistant doesn't need this field. 5. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize`. 6. Token URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/token`. - 7. Configure your client. Add scopes for `email` and `name`. + 7. Configure your client: Type `email` and click `Add scope`, then type `name` and click `Add scope` again. 8. Do **NOT** check `Google to transmit clientID and secret via HTTP basic auth header`. 9. Testing instructions: Enter anything. It doesn't matter since you won't submit this app. From bfc8cbc5e17075d59dcad3f8fb5e506f0d5a130f Mon Sep 17 00:00:00 2001 From: DubhAd Date: Wed, 2 Jan 2019 11:28:43 +0000 Subject: [PATCH 46/49] Documenting impact of state restore change (#8019) As it turns off all the automations without an `initial_state`, and it's hitting lots of folks, documenting it here ;) --- source/_posts/2018-12-12-release-84.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2018-12-12-release-84.markdown b/source/_posts/2018-12-12-release-84.markdown index 086039fb2de..59584e8b24f 100644 --- a/source/_posts/2018-12-12-release-84.markdown +++ b/source/_posts/2018-12-12-release-84.markdown @@ -33,6 +33,8 @@ We have a new more reliable way of state restoration introduced by [@armills]. I This comes with a downside: we will be unable to restore states the first time you start 0.84. +This means that on upgrade to 0.84 any automation that doesn't have an `initial_state` defined **will be disabled**. + ## {% linkable_title Improved service calling %} We have improved how we call services with better validation checks. This means that if you have an automation or a script that sends invalid data, we will now stop the execution and be better able to point out where your incorrect calls are coming from. From 1fbc63c7fb2b7c21f4fecd2d382d34f38587ce2f Mon Sep 17 00:00:00 2001 From: DubhAd Date: Wed, 2 Jan 2019 19:05:46 +0000 Subject: [PATCH 47/49] Fixing missing `binary_` (#8022) One of the sensor templates was a sensor template, not a binary_sensor template --- source/_components/binary_sensor.template.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown index a69deb7940a..5fe812ac1e4 100644 --- a/source/_components/binary_sensor.template.markdown +++ b/source/_components/binary_sensor.template.markdown @@ -115,7 +115,7 @@ determine if the furnace is running by checking that it is over some threshold: {% raw %} ```yaml -sensor: +binary_sensor: - platform: template sensors: furnace_on: From 44d7c05196e3c0fbf380404df559a44f5044ba72 Mon Sep 17 00:00:00 2001 From: Nicholas Westerhausen Date: Wed, 2 Jan 2019 14:27:39 -0500 Subject: [PATCH 48/49] Missing 'color2' in model options (#8023) --- source/_components/light.yeelight.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/light.yeelight.markdown b/source/_components/light.yeelight.markdown index 609bd18e1c3..ae047f196d1 100644 --- a/source/_components/light.yeelight.markdown +++ b/source/_components/light.yeelight.markdown @@ -59,7 +59,7 @@ devices: type: boolean default: False model: - description: "Yeelight model. Possible values are `mono1`, `color1`, `strip1`, `bslamp1`, `ceiling1`, `ceiling2`, `ceiling3`, `ceiling4`. The setting is used to enable model specific features f.e. a particular color temperature range." + description: "Yeelight model. Possible values are `mono1`, `color1`, `color2`, `strip1`, `bslamp1`, `ceiling1`, `ceiling2`, `ceiling3`, `ceiling4`. The setting is used to enable model specific features f.e. a particular color temperature range." required: false type: string {% endconfiguration %} From aaa59939e767fb4291916d08ba75247e81f0b30e Mon Sep 17 00:00:00 2001 From: aguedob Date: Thu, 3 Jan 2019 09:43:20 +0100 Subject: [PATCH 49/49] Added J6200 to non working models (#8028) --- 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 48d9cba191f..2568eef1730 100644 --- a/source/_components/media_player.samsungtv.markdown +++ b/source/_components/media_player.samsungtv.markdown @@ -102,6 +102,7 @@ Currently tested but not working models: - J5200 - Unable to see state and unable to control - J5500 - State is always "on" and unable to control (but port 8001 *is* open) +- J6200 - State is always "on" and unable to control (but port 8001 *is* open) - J6300 - State is always "on" and unable to control (but port 8001 *is* open) - JS8005 - State tracking working but unable to control (but port 8001 *is* open) - JS9000 - State is always "on" and unable to control (but port 8001 *is* open)