From e90d506a2ca43ff10504142cc9518b5cacceed09 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Sat, 20 Jul 2019 12:54:33 +0100 Subject: [PATCH 01/67] Converting JSON to YAML (#9927) Given that people use YAML, another old JSON approach converted to YAML. --- source/_components/discord.markdown | 22 ++++++++-------------- 1 file changed, 8 insertions(+), 14 deletions(-) diff --git a/source/_components/discord.markdown b/source/_components/discord.markdown index 16f0ea7f283..b9f32559438 100644 --- a/source/_components/discord.markdown +++ b/source/_components/discord.markdown @@ -66,21 +66,15 @@ Right click channel name and copy the channel ID (**Copy ID**). This channel ID has to be used as the target when calling the notification service. Multiple channel IDs can be specified, across multiple servers. -#### Example service payload +#### Example service call -```json -{ - "message": "A message from Home Assistant", - "target": [ - "1234567890", - "0987654321" - ], - "data": { - "images": [ - "/tmp/garage_cam.jpg" - ] - } -} +```yaml +- service: notify.discord + data: + message from Home Assistant", + target: "1234567890", "0987654321" + data: + images: "/tmp/garage_cam" ``` ### Notes From fd9d50b4e6d0fb85c58fef4655853b55cb8a0ca3 Mon Sep 17 00:00:00 2001 From: LuBeDa Date: Sat, 20 Jul 2019 13:59:28 +0200 Subject: [PATCH 02/67] Added infos about the windows parameter (#9926) * Added infos about the windows parameter Default value 10 minutes * :pencil2: Tweak --- source/_components/wwlln.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/wwlln.markdown b/source/_components/wwlln.markdown index b7f083447f9..e3107cc5d1f 100644 --- a/source/_components/wwlln.markdown +++ b/source/_components/wwlln.markdown @@ -49,6 +49,7 @@ window: description: The amount of time before now for which strikes should be considered "active" and shown in the UI. required: false type: time + default: 10 minutes {% endconfiguration %} ## State Attributes From ce01ef1c14a502ee3b91e7a19e3a789a9a70b3cf Mon Sep 17 00:00:00 2001 From: Aaron Bach Date: Sat, 20 Jul 2019 10:34:47 -0600 Subject: [PATCH 03/67] Fix incorrect timing statement on WWLLN docs (#9929) --- source/_components/wwlln.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/wwlln.markdown b/source/_components/wwlln.markdown index e3107cc5d1f..f44fad3d8da 100644 --- a/source/_components/wwlln.markdown +++ b/source/_components/wwlln.markdown @@ -21,7 +21,7 @@ is available as the state of each entity.

-New data is returned every 5 minutes. +New data is returned every 10 minutes. ## Configuration From bc6c748b4b3d48949562b4d9c0150052c21c2354 Mon Sep 17 00:00:00 2001 From: Aaron Bach Date: Sun, 21 Jul 2019 05:31:58 -0600 Subject: [PATCH 04/67] Add ctags file to .gitignore (#9930) * Add ctags file to .gitignore * Wildcard --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 6ea9502ede3..28eb6d32a30 100644 --- a/.gitignore +++ b/.gitignore @@ -16,3 +16,4 @@ source/.jekyll-metadata !.vscode/extensions.json !.vscode/tasks.json *.suo +tags* From 64de6a001b45165ced27889b687e9d73e9ad425e Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Sun, 21 Jul 2019 15:35:35 +0200 Subject: [PATCH 05/67] Removes archlinux package instructions (#9934) --- source/_docs/installation/archlinux.markdown | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/source/_docs/installation/archlinux.markdown b/source/_docs/installation/archlinux.markdown index d8277cb7ba4..710052da803 100644 --- a/source/_docs/installation/archlinux.markdown +++ b/source/_docs/installation/archlinux.markdown @@ -8,18 +8,9 @@ description: "Installation of Home Assistant on your Arch Linux computer." Install the needed Python packages. ```bash -$ sudo pacman -S python -$ sudo pacman -S python-pip +sudo pacman -S python +sudo pacman -S python-pip ``` -and Home Assistant itself. - -```bash -$ pip3 install --user homeassistant -``` - -Home Assistant is part of the [AUR](https://aur.archlinux.org/packages/home-assistant/). This means that it can be installed with `pacaur`. This package is often broken or outdated: - -```bash -$ pacaur -S home-assistant -``` +From here on, we recommend you to follow the +[virtualenv](https://www.home-assistant.io/docs/installation/virtualenv/) guide. From 480fbc15b964f90bd3f5d1847040cb12ac28f67e Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 21 Jul 2019 11:10:59 -0700 Subject: [PATCH 06/67] 96.2 --- _config.yml | 4 ++-- source/_posts/2019-07-17-release-96.markdown | 23 ++++++++++++++++++++ 2 files changed, 25 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index a0df0693e03..89439b5464d 100644 --- a/_config.yml +++ b/_config.yml @@ -99,8 +99,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 96 -current_patch_version: 1 -date_released: 2019-07-18 +current_patch_version: 2 +date_released: 2019-07-19 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index 851a5934e84..1a776e323bc 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -146,6 +146,29 @@ The Home Assistant Podcast has published [episode 53](https://hasspodcast.io/ha0 [smartthings docs]: /components/smartthings/ [zwave docs]: /components/zwave/ +## Release 0.96.2 - July 19 + +- Fix fritzbox climate HVAC mode / temperature ([@cgtobi] - [#25275]) ([fritzbox docs]) +- Fixed python-wink method names ([@w1ll1am23] - [#25285]) ([wink docs]) +- [climate] Correct honeywell supported_features ([@zxdavb] - [#25292]) ([honeywell docs]) +- Fix HM with use wrong datapoint for off ([@pvizeli] - [#25298]) ([homematic docs]) +- Fix plant error when adding new value ([@cgtobi] - [#25302]) ([plant docs]) + +[#25275]: https://github.com/home-assistant/home-assistant/pull/25275 +[#25285]: https://github.com/home-assistant/home-assistant/pull/25285 +[#25292]: https://github.com/home-assistant/home-assistant/pull/25292 +[#25298]: https://github.com/home-assistant/home-assistant/pull/25298 +[#25302]: https://github.com/home-assistant/home-assistant/pull/25302 +[@cgtobi]: https://github.com/cgtobi +[@pvizeli]: https://github.com/pvizeli +[@w1ll1am23]: https://github.com/w1ll1am23 +[@zxdavb]: https://github.com/zxdavb +[fritzbox docs]: /components/fritzbox/ +[homematic docs]: /components/homematic/ +[honeywell docs]: /components/honeywell/ +[plant docs]: /components/plant/ +[wink docs]: /components/wink/ + ## If you need help... ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). From 5026a0e3c08be5b7731fd701a0addd6eadcdbcb0 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 21 Jul 2019 11:12:43 -0700 Subject: [PATCH 07/67] 0.96.3 --- _config.yml | 4 +- source/_posts/2019-07-17-release-96.markdown | 47 ++++++++++++++++++++ 2 files changed, 49 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 89439b5464d..c0b11998288 100644 --- a/_config.yml +++ b/_config.yml @@ -99,8 +99,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 96 -current_patch_version: 2 -date_released: 2019-07-19 +current_patch_version: 3 +date_released: 2019-07-21 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index 1a776e323bc..c338c613941 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -169,6 +169,53 @@ The Home Assistant Podcast has published [episode 53](https://hasspodcast.io/ha0 [plant docs]: /components/plant/ [wink docs]: /components/wink/ +## Release 0.96.3 - July 21 + +- temporary patch to fix KNX climate devices ([@farmio] - [#25356]) ([knx docs]) +- Restore sensiobo turn on/off methods ([@balloob] - [#25321]) ([sensibo docs]) +- Update zwave climate mappings ([@eyager1] - [#25327]) ([zwave docs]) +- Restore Daikin A/C on/off services ([@fredrike] - [#25332]) ([daikin docs]) +- Fix for hvac_modes list being null ([@schmic] - [#25347]) ([zwave docs]) +- add available to device info ([@dmulcahey] - [#25349]) ([zha docs]) +- Fix preset service call ([@cgtobi] - [#25358]) ([netatmo docs]) +- Improve geniushub logging and bump client ([@zxdavb] - [#25359]) ([geniushub docs]) +- Introduce PRESET_NONE for climate ([@balloob] - [#25360]) +- bump quirks version ([@dmulcahey] - [#25362]) ([zha docs]) +- Fix ESPHome climate migration ([@OttoWinter] - [#25366]) ([esphome docs]) +- fix remove and re-add scenario ([@dmulcahey] - [#25370]) ([zha docs]) +- change and condition to or condition ([@dmulcahey] - [#25374]) + +[#25321]: https://github.com/home-assistant/home-assistant/pull/25321 +[#25327]: https://github.com/home-assistant/home-assistant/pull/25327 +[#25332]: https://github.com/home-assistant/home-assistant/pull/25332 +[#25347]: https://github.com/home-assistant/home-assistant/pull/25347 +[#25349]: https://github.com/home-assistant/home-assistant/pull/25349 +[#25356]: https://github.com/home-assistant/home-assistant/pull/25356 +[#25358]: https://github.com/home-assistant/home-assistant/pull/25358 +[#25359]: https://github.com/home-assistant/home-assistant/pull/25359 +[#25360]: https://github.com/home-assistant/home-assistant/pull/25360 +[#25362]: https://github.com/home-assistant/home-assistant/pull/25362 +[#25366]: https://github.com/home-assistant/home-assistant/pull/25366 +[#25370]: https://github.com/home-assistant/home-assistant/pull/25370 +[#25374]: https://github.com/home-assistant/home-assistant/pull/25374 +[@OttoWinter]: https://github.com/OttoWinter +[@balloob]: https://github.com/balloob +[@cgtobi]: https://github.com/cgtobi +[@dmulcahey]: https://github.com/dmulcahey +[@eyager1]: https://github.com/eyager1 +[@farmio]: https://github.com/farmio +[@fredrike]: https://github.com/fredrike +[@schmic]: https://github.com/schmic +[@zxdavb]: https://github.com/zxdavb +[daikin docs]: /components/daikin/ +[esphome docs]: /components/esphome/ +[geniushub docs]: /components/geniushub/ +[knx docs]: /components/knx/ +[netatmo docs]: /components/netatmo/ +[sensibo docs]: /components/sensibo/ +[zha docs]: /components/zha/ +[zwave docs]: /components/zwave/ + ## If you need help... ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). From 0a7857030e86a9330f1c5854dd6882df28413f24 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 21 Jul 2019 12:01:58 -0700 Subject: [PATCH 08/67] Add 1 more changelog line --- source/_posts/2019-07-17-release-96.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index c338c613941..0b019205967 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -184,8 +184,10 @@ The Home Assistant Podcast has published [episode 53](https://hasspodcast.io/ha0 - Fix ESPHome climate migration ([@OttoWinter] - [#25366]) ([esphome docs]) - fix remove and re-add scenario ([@dmulcahey] - [#25370]) ([zha docs]) - change and condition to or condition ([@dmulcahey] - [#25374]) +- Add Netatmo climate battery level ([@cgtobi] - [#25143]) ([netatmo docs]) [#25321]: https://github.com/home-assistant/home-assistant/pull/25321 +[#25143]: https://github.com/home-assistant/home-assistant/pull/25143 [#25327]: https://github.com/home-assistant/home-assistant/pull/25327 [#25332]: https://github.com/home-assistant/home-assistant/pull/25332 [#25347]: https://github.com/home-assistant/home-assistant/pull/25347 From ff2db73b3064e576d3e4a1326bd27ed7c8cacc5a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Magnus=20=C3=98verli?= Date: Sun, 21 Jul 2019 22:15:33 +0200 Subject: [PATCH 09/67] Fix deprecated link (#9938) Updated the link to hassio installation instructions on linux/vm. --- source/hassio/installation.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index a9a842408ce..f738258f1d9 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -178,7 +178,7 @@ A detailed guide about running Hass.io as a virtual machine is available in the [vmdk]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_ova-2.12.vmdk.gz [vhdx]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_ova-2.12.vhdx.gz [vdi]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_ova-2.12.vdi.gz -[linux]: https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio +[linux]: https://github.com/home-assistant/hassio-installer [local]: http://hassio.local:8123 [samba]: /addons/samba/ [ssh]: /addons/ssh/ From 75cad96c7d71ef8f1f4b6134c3406feac6cb53c3 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Sun, 21 Jul 2019 22:15:53 +0200 Subject: [PATCH 10/67] Correct incorrect YAML in Discord example (#9936) --- source/_components/discord.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_components/discord.markdown b/source/_components/discord.markdown index b9f32559438..fc085fbe50e 100644 --- a/source/_components/discord.markdown +++ b/source/_components/discord.markdown @@ -71,9 +71,9 @@ This channel ID has to be used as the target when calling the notification servi ```yaml - service: notify.discord data: - message from Home Assistant", - target: "1234567890", "0987654321" - data: + message: "A message from Home Assistant" + target: ["1234567890", "0987654321"] + data: images: "/tmp/garage_cam" ``` From a29fab9f87c3dd15c72c4ce7c458dcd70128a212 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Sun, 21 Jul 2019 23:31:14 +0200 Subject: [PATCH 11/67] Update installation.markdown --- source/hassio/installation.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index f738258f1d9..d93ae51b33d 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -15,6 +15,8 @@ The following will take you through the steps required to install Hass.io. - [Raspberry Pi 2 Model B][pi2] - [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] (recommended) - [Raspberry Pi 3 Model B and B+ 64bit][pi3-64] + - [(Beta) Raspberry Pi 4 Model B 32bit][pi4-32] (recommended) + - [(Beta) Raspberry Pi 4 Model B 64bit][pi4-64] - [Tinkerboard][tinker] - [Odroid-C2][odroid-c2] - [Odroid-XU4][odroid-xu4] @@ -170,6 +172,8 @@ A detailed guide about running Hass.io as a virtual machine is available in the [pi2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi2-2.12.img.gz [pi3-32]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-2.12.img.gz [pi3-64]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-64-2.12.img.gz +[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.3/hassos_rpi3-3.3.img.gz +[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.3/hassos_rpi3-64-3.3.img.gz [tinker]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_tinker-2.12.img.gz [odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-c2-2.12.img.gz [odroid-xu4]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-xu4-2.12.img.gz From 73de39add08b5f0a90790fbd9e3cbbe3e2d20eef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Mon, 22 Jul 2019 00:55:32 +0300 Subject: [PATCH 12/67] Spelling fixes (#9942) --- source/_components/cover.mqtt.markdown | 4 +-- source/_components/cups.markdown | 2 +- source/_components/danfoss_air.markdown | 2 +- source/_components/discord.markdown | 2 +- source/_components/ebusd.markdown | 2 +- source/_components/elkm1.markdown | 36 +++++++++---------- .../entur_public_transport.markdown | 2 +- source/_components/freebox.markdown | 2 +- source/_components/google_assistant.markdown | 2 +- source/_components/gtt.markdown | 2 +- source/_components/heos.markdown | 6 ++-- source/_components/hlk_sw16.markdown | 2 +- source/_components/lcn.markdown | 6 ++-- source/_components/mhz19.markdown | 2 +- source/_components/nilu.markdown | 2 +- source/_components/nissan_leaf.markdown | 2 +- source/_components/orangepi_gpio.markdown | 2 +- source/_components/point.markdown | 2 +- source/_components/ps4.markdown | 4 +-- source/_components/ptvsd.markdown | 2 +- source/_components/scrape.markdown | 2 +- source/_components/smartthings.markdown | 2 +- source/_components/switcher_kis.markdown | 2 +- source/_components/tensorflow.markdown | 2 +- source/_components/traccar.markdown | 2 +- source/_components/utility_meter.markdown | 2 +- 26 files changed, 49 insertions(+), 49 deletions(-) diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown index 5d47ba55b8c..d15d6a5f674 100644 --- a/source/_components/cover.mqtt.markdown +++ b/source/_components/cover.mqtt.markdown @@ -13,9 +13,9 @@ The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a ## Configuration The device state (`open` or `closed`) will be updated only after a new message is published on `state_topic` matching `state_open` or `state_closed`. If these messages are published with the `retain` flag set, the cover 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`. -`state_topic` can only manage `state_open` and `state_closed`. No percentage positons etc. +`state_topic` can only manage `state_open` and `state_closed`. No percentage positions etc. -For this purpose is `position_topic` which can set state of the cover and positon. +For this purpose is `position_topic` which can set state of the cover and position. Default setting are 0 means the device is `closed` and all other intermediate positions means the device is `open`. `position_topic` is managed by `position_open` and `position_closed` You can set it up in opossite way as well. diff --git a/source/_components/cups.markdown b/source/_components/cups.markdown index e65d00fd32d..67ea00369a1 100644 --- a/source/_components/cups.markdown +++ b/source/_components/cups.markdown @@ -15,7 +15,7 @@ The `cups` sensor platform is using the open source printing system [CUPS](https ## Setup -You will need to install the `python3-dev` or `python3-devel` pacakge and the development files for CUPS (`libcups2-dev` or`cups-devel`) on your system manually (e.g., `sudo apt-get install python3-dev libcups2-dev` or `sudo dnf -y install python3-devel cups-devel`) along with a compiler (`gcc`). This integration doesn't work out-of-the-box in a container-based setup. +You will need to install the `python3-dev` or `python3-devel` package and the development files for CUPS (`libcups2-dev` or`cups-devel`) on your system manually (e.g., `sudo apt-get install python3-dev libcups2-dev` or `sudo dnf -y install python3-devel cups-devel`) along with a compiler (`gcc`). This integration doesn't work out-of-the-box in a container-based setup. To set up the sensor the "Queue Name" of the printer is needed. The fastest way to get it, is to visit the CUPS web interface at "http://[IP ADDRESS PRINT SERVER]:631" and go to "Printers". diff --git a/source/_components/danfoss_air.markdown b/source/_components/danfoss_air.markdown index e944546d3db..8e3458f0d80 100644 --- a/source/_components/danfoss_air.markdown +++ b/source/_components/danfoss_air.markdown @@ -52,7 +52,7 @@ The following sensors are supported. - **Supply temperature:** Air temperature of the air supplied to the house. - **Extract temperature:** Air temperature of the air extracted from the house. - **Exhaust temperature:** Exhausted air temperature. -- **Remaining filter lifetime:** Reamining filter lifetime measured in percent. +- **Remaining filter lifetime:** Remaining filter lifetime measured in percent. ## Switch diff --git a/source/_components/discord.markdown b/source/_components/discord.markdown index fc085fbe50e..316a813675e 100644 --- a/source/_components/discord.markdown +++ b/source/_components/discord.markdown @@ -13,7 +13,7 @@ The [Discord service](https://discordapp.com/) is a platform for the notify comp In order to get a token you need to go to the [Discord My Apps page](https://discordapp.com/developers/applications/me) and create a new application. Once the application is ready, create a [bot](https://discordapp.com/developers/docs/topics/oauth2#bots) user (**Create a Bot User**). -Retreive the **Client ID** from the information section and the (hidden) **Token** of your bot for later. +Retrieve the **Client ID** from the information section and the (hidden) **Token** of your bot for later. When setting up the application you can use this [icon](/images/favicon-192x192-full.png). diff --git a/source/_components/ebusd.markdown b/source/_components/ebusd.markdown index 533b24dd48c..7e430da574c 100644 --- a/source/_components/ebusd.markdown +++ b/source/_components/ebusd.markdown @@ -107,7 +107,7 @@ monitored_conditions: Zone1OperativeMode: description: Heating circuit operative mode (on/off/day/night). ContinuosHeating: - description: Continuos heating. + description: Continuous heating. PowerEnergyConsumptionLastMonth: description: Power energy consumption from last month. PowerEnergyConsumptionThisMonth: diff --git a/source/_components/elkm1.markdown b/source/_components/elkm1.markdown index 063db11650f..c0abdf4fe92 100644 --- a/source/_components/elkm1.markdown +++ b/source/_components/elkm1.markdown @@ -75,12 +75,12 @@ area: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -96,12 +96,12 @@ counter: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -117,12 +117,12 @@ keypad: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -138,12 +138,12 @@ output: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -159,12 +159,12 @@ setting: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -180,12 +180,12 @@ task: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -201,12 +201,12 @@ thermostat: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -222,12 +222,12 @@ plc: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. @@ -243,12 +243,12 @@ zone: required: false default: true include: - description: List to include in the form of either `` or `-` where `` is a postive integer or a X10 housecode. See configuration below for examples of ranges. + description: List to include in the form of either `` or `-` where `` is a positive integer or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: All included. exclude: - description: List to exclude in the form of either `` or `-` where `` is a number or a X10 housecode. See configuration below for examples of ranges. + description: List to exclude in the form of either `` or `-` where `` is a number or an X10 housecode. See configuration below for examples of ranges. type: list required: false default: None excluded. diff --git a/source/_components/entur_public_transport.markdown b/source/_components/entur_public_transport.markdown index 34d78de21cf..7e449d40d68 100644 --- a/source/_components/entur_public_transport.markdown +++ b/source/_components/entur_public_transport.markdown @@ -129,4 +129,4 @@ The stop id is the content after `id=` parameter in the url. Copy paste this int **Q:** Where do I find a line id to add to the whitelisting? -**A:** The sensor will show the line id, and is the recommended way to find it, while we wait for 'Nasjonalt Stoppestedregister' to become public. It is also possible to see the line ids by using the developer tool in the browser while looking at the trafic in [Entur's travel planer](https://en-tur.no). +**A:** The sensor will show the line id, and is the recommended way to find it, while we wait for 'Nasjonalt Stoppestedregister' to become public. It is also possible to see the line ids by using the developer tool in the browser while looking at the traffic in [Entur's travel planer](https://en-tur.no). diff --git a/source/_components/freebox.markdown b/source/_components/freebox.markdown index d1ec96b5197..df7c6bc8611 100644 --- a/source/_components/freebox.markdown +++ b/source/_components/freebox.markdown @@ -60,7 +60,7 @@ authorize it by pressing the right arrow on the facade of the Freebox when prompted to do so. To make the WiFi switch working you will have to add "Modification des réglages de la Freebox -" permission to Home Assitant application in "Paramètres de la Freebox" > "Gestion des accès" > "Applications". +" permission to Home Assistant application in "Paramètres de la Freebox" > "Gestion des accès" > "Applications". ### Supported routers diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown index 4f2d5aba68e..4dc35bc5a0b 100644 --- a/source/_components/google_assistant.markdown +++ b/source/_components/google_assistant.markdown @@ -248,7 +248,7 @@ The request_sync service may fail with a 404 if the project_id of the Homegraph 4. Generate a new API key. 5. Again, create a new project in the [Actions on Google console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`. -Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is techincally in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again. +Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again. ### Troubleshooting with NGINX diff --git a/source/_components/gtt.markdown b/source/_components/gtt.markdown index 15a922a1074..1c2ddd72976 100644 --- a/source/_components/gtt.markdown +++ b/source/_components/gtt.markdown @@ -28,7 +28,7 @@ stop: required: true type: string bus_name: - description: The name of the choosen bus. + description: The name of the chosen bus. required: false type: string {% endconfiguration %} diff --git a/source/_components/heos.markdown b/source/_components/heos.markdown index 2b27acccfbd..d49f308d4d5 100644 --- a/source/_components/heos.markdown +++ b/source/_components/heos.markdown @@ -41,7 +41,7 @@ A connection to a single device enables control for all devices on the network. ### Service `heos.sign_in` -Use the sign-in service to sign the connected controller into a HEOS account so that it can retreive and play HEOS favorites and playlists. An error message is logged if sign-in is unsuccessful. Example service data payload: +Use the sign-in service to sign the connected controller into a HEOS account so that it can retrieve and play HEOS favorites and playlists. An error message is logged if sign-in is unsuccessful. Example service data payload: ```json { @@ -142,7 +142,7 @@ You can play a URL through a HEOS media player using the `media_player.play_medi ### Debugging -The HEOS integration will log additional information about commands, events, and other messages when the log level is set to `debug`. Add the the relevent line below to the `configuration.yaml` to enable debug logging: +The HEOS integration will log additional information about commands, events, and other messages when the log level is set to `debug`. Add the the relevant line below to the `configuration.yaml` to enable debug logging: ```yaml logger: @@ -157,4 +157,4 @@ logger: If the HEOS controller is not signed in to a HEOS account, HEOS favorites will not be populated in the media player source selection and the service `media_player.play_media` for `favorite` and `playlist` will fail. Additionally, the following warning will be logged at startup: > IP_ADDRESS is not logged in to a HEOS account and will be unable to retrieve HEOS favorites: Use the 'heos.sign_in' service to sign-in to a HEOS account -To resolve this issue, use the `heos.sign_out` service to sign the controller into an account as documented above. This only needs to be performed once, as the controller will remain signed in while the account credentails are valid. +To resolve this issue, use the `heos.sign_out` service to sign the controller into an account as documented above. This only needs to be performed once, as the controller will remain signed in while the account credentials are valid. diff --git a/source/_components/hlk_sw16.markdown b/source/_components/hlk_sw16.markdown index fbeb7109a12..571562e0074 100644 --- a/source/_components/hlk_sw16.markdown +++ b/source/_components/hlk_sw16.markdown @@ -76,7 +76,7 @@ deviceid: type: map keys: relayid: - description: The array that contains the HLK-SW16 relays, each must be a number between 0 and 9 or letter between a and f which each corresponds to a labled relay switch on the HLK-SW16. + description: The array that contains the HLK-SW16 relays, each must be a number between 0 and 9 or letter between a and f which each corresponds to a labeled relay switch on the HLK-SW16. required: false type: map keys: diff --git a/source/_components/lcn.markdown b/source/_components/lcn.markdown index 3b8dc83ea94..f5aef008c98 100644 --- a/source/_components/lcn.markdown +++ b/source/_components/lcn.markdown @@ -127,7 +127,7 @@ connections: required: true type: string name: - description: Optional connection identifier. If omited, the connections will be named consecutively as _pchk_, _pchk1_, _pchk2_, ... + description: Optional connection identifier. If omitted, the connections will be named consecutively as _pchk_, _pchk1_, _pchk2_, ... required: false default: pchk type: string @@ -423,7 +423,7 @@ If the control is set lockable, the regulator can be turned on/off.
-If you intend to leave the regulation to home assistant, you should consider using the [Generic Thermostat](/components/generic_thermostat/) in conjuction with [LCN Sensor](#sensor) and [LCN Switch](#switch). +If you intend to leave the regulation to home assistant, you should consider using the [Generic Thermostat](/components/generic_thermostat/) in conjunction with [LCN Sensor](#sensor) and [LCN Switch](#switch).
@@ -488,7 +488,7 @@ Example: ```yaml service: output_abs data: - addres: myhome.0.7 + address: myhome.0.7 output: output1 brightness: 100 transition: 0 diff --git a/source/_components/mhz19.markdown b/source/_components/mhz19.markdown index 849a21bde1d..32afb526793 100644 --- a/source/_components/mhz19.markdown +++ b/source/_components/mhz19.markdown @@ -60,4 +60,4 @@ Then (after a reboot): you can setup the sensor using: ## Calibration -The MH-Z19B version of the sensor has Automatic Baseline Calibration enabled by default, which will calibrate the 400PPM level to the lowest measured PPM in the last 24h cycle. Currently the integration does not allow turning this functionaly off. +The MH-Z19B version of the sensor has Automatic Baseline Calibration enabled by default, which will calibrate the 400PPM level to the lowest measured PPM in the last 24h cycle. Currently the integration does not allow turning this functionality off. diff --git a/source/_components/nilu.markdown b/source/_components/nilu.markdown index fc212b6f6b0..c4e0d76d894 100644 --- a/source/_components/nilu.markdown +++ b/source/_components/nilu.markdown @@ -59,7 +59,7 @@ Under the attributes from a NILU station, there will be a `nilu pollution index` ### Low -Low or no health risk linked to measured air pollution. Outdoor activites are recommended. +Low or no health risk linked to measured air pollution. Outdoor activities are recommended. ### Moderate diff --git a/source/_components/nissan_leaf.markdown b/source/_components/nissan_leaf.markdown index 76ae305b433..534fb8d5c00 100644 --- a/source/_components/nissan_leaf.markdown +++ b/source/_components/nissan_leaf.markdown @@ -44,7 +44,7 @@ region: required: true type: string nissan_connect: - description: If your car has the updated head unit (NissanConnect rather than Carwings) then the location can be aquired and exposed via a device tracker. If you have Carwings then this should be set to false. The easiest way to identify NissanConnect is if the T&C buttons are orange and blue, for CarWings they're both blue, or just look for anything saying "CarWings" in Settings area of the infotainment system. + description: If your car has the updated head unit (NissanConnect rather than Carwings) then the location can be acquired and exposed via a device tracker. If you have Carwings then this should be set to false. The easiest way to identify NissanConnect is if the T&C buttons are orange and blue, for CarWings they're both blue, or just look for anything saying "CarWings" in Settings area of the infotainment system. required: false type: boolean default: true diff --git a/source/_components/orangepi_gpio.markdown b/source/_components/orangepi_gpio.markdown index c1c61481a61..0bc5b813028 100644 --- a/source/_components/orangepi_gpio.markdown +++ b/source/_components/orangepi_gpio.markdown @@ -64,7 +64,7 @@ As this platform supports different types of GPIO pinouts for difference Orange | `neocore2` | Supports the NanoPi Neocore 2 | ## Additional steps -This integration uses the `SYSFS` filesystem to get control of the GPIOs. Therefore an operatings system with `CONFIG_GPIO_SYSFS` is required. As far as I know, most out-of-the-box distributions still enable this by default. +This integration uses the `SYSFS` filesystem to get control of the GPIOs. Therefore an operating system with `CONFIG_GPIO_SYSFS` is required. As far as I know, most out-of-the-box distributions still enable this by default. As of Linux 4.8 sysfs-gpio is marked as obsolete. However as of today, the alternative GPIO character device is not widely used. Therefore we will use this until the new character device is more widely supported. diff --git a/source/_components/point.markdown b/source/_components/point.markdown index 20e7d447a5c..226a81fbd84 100644 --- a/source/_components/point.markdown +++ b/source/_components/point.markdown @@ -86,7 +86,7 @@ Each Point exposes the following binary sensors:
-The binary sensors **button_press**, **sound** and **tamper** are switched `On` for a breif moment and are then switched back to `Off`. +The binary sensors **button_press**, **sound** and **tamper** are switched `On` for a brief moment and are then switched back to `Off`.
diff --git a/source/_components/ps4.markdown b/source/_components/ps4.markdown index 1f2b41c2654..0f006beecee 100644 --- a/source/_components/ps4.markdown +++ b/source/_components/ps4.markdown @@ -116,11 +116,11 @@ Some titles will have different SKUs in the PlayStation Store database depending | Available Regions | Unavailable Regions | | --------------------------------------------------------------------------- | -------------------------- | -| Argentina, Australia, Austria, Bahrain, Belgium, Brazil, Bulgaria, | China, Japan, Phillipines, | +| Argentina, Australia, Austria, Bahrain, Belgium, Brazil, Bulgaria, | China, Japan, Philippines, | | Canada, Chile, Columbia, Costa Rica, Croatia, Cyprus, Czech Republic, | Serbia, Ukraine, Vietnam | | Denmark, Ecuador, El Salvador, Finland, France, Germany, Greece, Guatemala, | | | Honduras, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, | | -| Italy, Korea, Kuwait, Lebanon, Luxembourg, Malta, Maylasia, Mexico, | | +| Italy, Korea, Kuwait, Lebanon, Luxembourg, Malta, Malaysia, Mexico, | | | Middle East, Nederland, New Zealand, Nicaragua, Norway, Oman, Panama, | | | Peru, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Singapore, | | | Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, | | diff --git a/source/_components/ptvsd.markdown b/source/_components/ptvsd.markdown index dfc2bcf651a..34f5fb95294 100644 --- a/source/_components/ptvsd.markdown +++ b/source/_components/ptvsd.markdown @@ -40,7 +40,7 @@ wait: ### Security -Ensure if this is a public-facing server, that the port is secured. Anyone who is able to access the debugger port can *execute arbitary code* on the home assistant server, which is very unsafe. +Ensure if this is a public-facing server, that the port is secured. Anyone who is able to access the debugger port can *execute arbitrary code* on the home assistant server, which is very unsafe. If the home assistant server is behind your firewall with only the http(s) port exposed, then this is safe from outside connections. diff --git a/source/_components/scrape.markdown b/source/_components/scrape.markdown index ae231fbad09..baa09f09bf9 100644 --- a/source/_components/scrape.markdown +++ b/source/_components/scrape.markdown @@ -165,7 +165,7 @@ sensor: ### BOM Weather -The Australian Bureau of Meterology website returns an error if the User Agent header is not sent. +The Australian Bureau of Meteorology website returns an error if the User Agent header is not sent. {% raw %} ```yaml diff --git a/source/_components/smartthings.markdown b/source/_components/smartthings.markdown index 26f15e0bea6..499c9fa2a84 100644 --- a/source/_components/smartthings.markdown +++ b/source/_components/smartthings.markdown @@ -345,7 +345,7 @@ If you have completed the checklist above and are still unable to setup the plat ### Debugging -The SmartThings integration will log additional information about push updates received, events fired, and other messages when the log level is set to `debug`. Add the the relevent line below to the `configuration.yaml`: +The SmartThings integration will log additional information about push updates received, events fired, and other messages when the log level is set to `debug`. Add the the relevant line below to the `configuration.yaml`: ```yaml logger: diff --git a/source/_components/switcher_kis.markdown b/source/_components/switcher_kis.markdown index 08b27786579..5a8aa70fd86 100644 --- a/source/_components/switcher_kis.markdown +++ b/source/_components/switcher_kis.markdown @@ -26,7 +26,7 @@ To retrieve your device's details, please follow the instructions [here](https:/
- Please note, on the original script repository, users recently reported difficulties controling the device after upgrading the firmware to the new 3.0 version.As this integration is based on that script, please do not upgrade to version 3.0 until this issue is resolved. You can follow the issue [here](https://github.com/NightRang3r/Switcher-V2-Python/issues/3). + Please note, on the original script repository, users recently reported difficulties controlling the device after upgrading the firmware to the new 3.0 version.As this integration is based on that script, please do not upgrade to version 3.0 until this issue is resolved. You can follow the issue [here](https://github.com/NightRang3r/Switcher-V2-Python/issues/3).
```yaml diff --git a/source/_components/tensorflow.markdown b/source/_components/tensorflow.markdown index 1fdcf98d071..38066ccb35e 100644 --- a/source/_components/tensorflow.markdown +++ b/source/_components/tensorflow.markdown @@ -36,7 +36,7 @@ This integration requires files to be downloaded, compiled on your computer, and |- __init__.py ``` -- Copy required object_detection dependancies to the `object_detection` folder inside of the `tensorflow` folder: +- Copy required object_detection dependencies to the `object_detection` folder inside of the `tensorflow` folder: - `research/object_detection/data` - `research/object_detection/utils` diff --git a/source/_components/traccar.markdown b/source/_components/traccar.markdown index d21ed030071..1f0cfe181af 100644 --- a/source/_components/traccar.markdown +++ b/source/_components/traccar.markdown @@ -63,7 +63,7 @@ max_accuracy: type: integer default: 0 skip_accuracy_filter_on: - description: Skip filter positon by "max_accuracy filter" if any of specified attributes are pressent on the traccar message. + description: Skip filter position by "max_accuracy filter" if any of specified attributes are pressent on the traccar message. required: false type: list monitored_conditions: diff --git a/source/_components/utility_meter.markdown b/source/_components/utility_meter.markdown index 1d25f7b312f..a79537d2ee2 100644 --- a/source/_components/utility_meter.markdown +++ b/source/_components/utility_meter.markdown @@ -101,7 +101,7 @@ This service must be called by the user for the tariff switching logic to occur The following configuration shows an example where 2 utility_meters (`daily_energy` and `monthly_energy`) track daily and monthly energy consumptions. -Both track the same sensor (`sensor.energy`) which continously monitors the energy consumed. +Both track the same sensor (`sensor.energy`) which continuously monitors the energy consumed. 4 different sensors will be created, 2 per utility meter and corresponding to each tariff. Sensor `sensor.daily_energy_peak`, `sensor.daily_energy_offpeak`, `sensor.monthly_energy_peak` and `sensor.monthly_energy_offpeak` will automatically be created to track the consumption in each tariff for the given cycle. From 86b8f09f6bb61976c84efd1c378a832ee97ba2ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Mon, 22 Jul 2019 12:13:45 +0300 Subject: [PATCH 13/67] Spell categories in title case (#9941) For consistency, and gets rid of "Binary Sensor"/"Binary sensor" duplicate listing entry. --- source/_components/config.markdown | 2 +- source/_components/ecoal_boiler.markdown | 2 +- source/_components/econet.markdown | 2 +- source/_components/geniushub.markdown | 4 ++-- source/_components/incomfort.markdown | 4 ++-- source/_components/panel_custom.markdown | 2 +- source/_components/panel_iframe.markdown | 2 +- source/_components/rss_feed_template.markdown | 2 +- source/_components/weblink.markdown | 2 +- source/_components/wink.markdown | 2 +- 10 files changed, 12 insertions(+), 12 deletions(-) diff --git a/source/_components/config.markdown b/source/_components/config.markdown index 90615cb5576..95d346783ff 100644 --- a/source/_components/config.markdown +++ b/source/_components/config.markdown @@ -3,7 +3,7 @@ title: "Config" description: "Instructions on how to setup the configuration panel for Home Assistant." logo: home-assistant.png ha_category: - - Front end + - Front End ha_release: 0.39 ha_qa_scale: internal --- diff --git a/source/_components/ecoal_boiler.markdown b/source/_components/ecoal_boiler.markdown index d49d8bf973f..617be151a62 100644 --- a/source/_components/ecoal_boiler.markdown +++ b/source/_components/ecoal_boiler.markdown @@ -2,7 +2,7 @@ title: "eCoal water boiler controller" description: "Instructions on how to integrate eSterownik.pl eCoal.pl controller into Home Assistant." ha_category: - - Water heater + - Water Heater ha_release: 0.87 ha_iot_class: Local Polling redirect_from: diff --git a/source/_components/econet.markdown b/source/_components/econet.markdown index 6120e7eba60..a83bce25e5a 100644 --- a/source/_components/econet.markdown +++ b/source/_components/econet.markdown @@ -3,7 +3,7 @@ title: "EcoNet water heater" description: "Instructions on how to integrate Rheem EcoNet water heaters into Home Assistant." logo: econet.png ha_category: - - Water heater + - Water Heater ha_release: 0.61 ha_iot_class: Cloud Polling redirect_from: diff --git a/source/_components/geniushub.markdown b/source/_components/geniushub.markdown index cc5aeb34de8..703ca7f966a 100644 --- a/source/_components/geniushub.markdown +++ b/source/_components/geniushub.markdown @@ -4,9 +4,9 @@ description: "Instructions on how to integrate Genius Hub with Home Assistant." logo: geniushub.png ha_category: - Climate - - Water heater + - Water Heater - Sensor - - Binary sensor + - Binary Sensor ha_release: 0.92 ha_iot_class: Local Polling --- diff --git a/source/_components/incomfort.markdown b/source/_components/incomfort.markdown index eea63d85b9d..57748c30438 100644 --- a/source/_components/incomfort.markdown +++ b/source/_components/incomfort.markdown @@ -3,10 +3,10 @@ title: "Intergas InComfort" description: "Instructions on how to integrate an Intergas Lan2RF gateway with Home Assistant." logo: incomfort.png ha_category: - - Water heater + - Water Heater - Climate - Sensor - - Binary sensor + - Binary Sensor ha_release: 0.93 ha_iot_class: Local Polling --- diff --git a/source/_components/panel_custom.markdown b/source/_components/panel_custom.markdown index 6e0ee4b58b7..fd2aa8176d1 100644 --- a/source/_components/panel_custom.markdown +++ b/source/_components/panel_custom.markdown @@ -3,7 +3,7 @@ title: "Panel Custom" description: "Instructions on how to add customized panels to the frontend of Home Assistant." logo: home-assistant.png ha_category: - - Front end + - Front End ha_release: 0.26 ha_qa_scale: internal --- diff --git a/source/_components/panel_iframe.markdown b/source/_components/panel_iframe.markdown index 0d79abffc6d..cea10eab2be 100644 --- a/source/_components/panel_iframe.markdown +++ b/source/_components/panel_iframe.markdown @@ -3,7 +3,7 @@ title: "Panel iFrame" description: "Instructions on how to add iFrames in the frontend of Home Assistant." logo: home-assistant.png ha_category: - - Front end + - Front End ha_release: 0.25 ha_qa_scale: internal --- diff --git a/source/_components/rss_feed_template.markdown b/source/_components/rss_feed_template.markdown index cd2e650c300..a0a73702de9 100644 --- a/source/_components/rss_feed_template.markdown +++ b/source/_components/rss_feed_template.markdown @@ -3,7 +3,7 @@ title: "RSS feed template" description: "Use this integration to generate RSS feeds showing your latest data." logo: home-assistant.png ha_category: - - Front end + - Front End ha_release: 0.44 ha_qa_scale: internal --- diff --git a/source/_components/weblink.markdown b/source/_components/weblink.markdown index 3cb968fb35f..bdbe73101c4 100644 --- a/source/_components/weblink.markdown +++ b/source/_components/weblink.markdown @@ -3,7 +3,7 @@ title: "Weblink" description: "Instructions on how to setup Links within Home Assistant." logo: home-assistant.png ha_category: - - Front end + - Front End ha_release: 0.13 ha_qa_scale: internal --- diff --git a/source/_components/wink.markdown b/source/_components/wink.markdown index c03c387d0d3..46a07a2558a 100644 --- a/source/_components/wink.markdown +++ b/source/_components/wink.markdown @@ -14,7 +14,7 @@ ha_category: - Scene - Sensor - Switch - - Water heater + - Water Heater featured: true ha_iot_class: Cloud Polling ha_release: pre 0.7 From d26b521ec03b7a1f62e402e3f473e01cd1e3d483 Mon Sep 17 00:00:00 2001 From: cgtobi Date: Mon, 22 Jul 2019 19:16:39 +0200 Subject: [PATCH 14/67] Add note about manual config and discovery (#9945) --- source/_components/netatmo.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/netatmo.markdown b/source/_components/netatmo.markdown index fa9aefdcd81..f5406df2294 100644 --- a/source/_components/netatmo.markdown +++ b/source/_components/netatmo.markdown @@ -60,7 +60,7 @@ password: required: true type: string discovery: - description: Whether to discover Netatmo devices. Set it to False, if you want to choose which Netatmo device you want to add. + description: Whether to discover Netatmo devices automatically. Set it to False, if you want to choose which Netatmo device you want to add. Do not use discovery and manual configuration at the same time. required: false type: boolean default: true From 241de1f28ebb4e08dffa0f040dac0301daf9071d Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 22 Jul 2019 11:29:28 -0700 Subject: [PATCH 15/67] RPi4 images link to RPi 4 images instead of 3 --- source/hassio/installation.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index d93ae51b33d..9a316216e60 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -172,8 +172,8 @@ A detailed guide about running Hass.io as a virtual machine is available in the [pi2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi2-2.12.img.gz [pi3-32]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-2.12.img.gz [pi3-64]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-64-2.12.img.gz -[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.3/hassos_rpi3-3.3.img.gz -[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.3/hassos_rpi3-64-3.3.img.gz +[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.3/hassos_rpi4-3.3.img.gz +[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.3/hassos_rpi4-64-3.3.img.gz [tinker]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_tinker-2.12.img.gz [odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-c2-2.12.img.gz [odroid-xu4]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-xu4-2.12.img.gz From 6e4424dcf97ea07843768daf63ad22934e05ce7e Mon Sep 17 00:00:00 2001 From: cogneato Date: Mon, 22 Jul 2019 13:34:10 -0600 Subject: [PATCH 16/67] Change component to integration (#9946) Changing stray mentions of "component" to "integration" --- source/_components/homekit_controller.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/homekit_controller.markdown b/source/_components/homekit_controller.markdown index c595c781d09..6deea76e083 100644 --- a/source/_components/homekit_controller.markdown +++ b/source/_components/homekit_controller.markdown @@ -24,7 +24,7 @@ redirect_from: - /components/sensor.homekit_controller/ --- -[HomeKit](https://developer.apple.com/homekit/) controller integration for Home Assistant allows you to connect HomeKit accessories to Home Assistant. This integration should not be confused with the [HomeKit](/components/homekit/) component, which allows you to control Home Assistant devices via HomeKit. +[HomeKit](https://developer.apple.com/homekit/) controller integration for Home Assistant allows you to connect HomeKit accessories to Home Assistant. This integration should not be confused with the [HomeKit](/components/homekit/) integration, which allows you to control Home Assistant devices via HomeKit. There is currently support for the following device types within Home Assistant: @@ -39,4 +39,4 @@ There is currently support for the following device types within Home Assistant: The integration will be automatically configured if the [`discovery`](/components/discovery/) integration is enabled. -For each detected HomeKit accessory, a configuration prompt will appear in the web front end. Use this to provide the HomeKit PIN. Note that HomeKit accessories can only be paired to one device at once. If your device is currently paired with Siri, you will need to reset it in order to pair it with Home Assistant. Once Home Assistant is configured to work with the device, you can export it back to Siri with the [`HomeKit`](/components/homekit/) component. +For each detected HomeKit accessory, a configuration prompt will appear in the web front end. Use this to provide the HomeKit PIN. Note that HomeKit accessories can only be paired to one device at once. If your device is currently paired with Siri, you will need to reset it in order to pair it with Home Assistant. Once Home Assistant is configured to work with the device, you can export it back to Siri with the [`HomeKit`](/components/homekit/) integration. From b7f2396ce78128cad9f3067f994a8571fc0e07c7 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 23 Jul 2019 04:10:47 -0400 Subject: [PATCH 17/67] Correct service calls on persistent_notification page (#9954) I updated the service calls to correct ones (they had a / instead of a .) and also removed the Services icon image since it's gone with the redesigned Dev Tools in 0.96. --- source/_components/persistent_notification.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_components/persistent_notification.markdown b/source/_components/persistent_notification.markdown index 7556eccadd1..4be8e781ae7 100644 --- a/source/_components/persistent_notification.markdown +++ b/source/_components/persistent_notification.markdown @@ -8,7 +8,7 @@ ha_release: 0.23 ha_qa_scale: internal --- -The `persistent_notification` can be used to show a message on the frontend that has to be dismissed by the user. +The `persistent_notification` integration can be used to show a notfication on the frontend that has to be dismissed by the user.

@@ -16,7 +16,7 @@ The `persistent_notification` can be used to show a message on the frontend that ### Service -The service `persistent_notification/create` takes in `message`, `title`, and `notification_id`. +The service `persistent_notification.create` takes in `message`, `title`, and `notification_id`. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | @@ -36,7 +36,7 @@ action: title: "Custom subject" ``` -The service `persistent_notification/dismiss` requires a `notification_id`. +The service `persistent_notification.dismiss` requires a `notification_id`. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | @@ -97,7 +97,7 @@ The message attribute supports the [Markdown formatting syntax](https://daringfi ### Create a persistent notification -Choose service developer tool icon **Services** from the **Developer Tools** to call the `persistent_notification` service. Select `persistent_notification/create` from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**. +Choose the **Services** tab from the **Developer Tools** sidebar item, then select the `persistent_notification.create` service from the "Service" dropdown. Enter something like the sample below into the **Service Data** field and press the **CALL SERVICE** button. ```json { From a902ed8281d27d698502c5e239a8e4290739bb86 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 23 Jul 2019 04:26:02 -0400 Subject: [PATCH 18/67] Remove link from Logbook introduction (#9952) The Home Assistant demo website doesn't have Logbook, so there's no "live example" that can be seen anymore. Better to remove this link rather than causing confusion. --- source/_components/logbook.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/logbook.markdown b/source/_components/logbook.markdown index f442871f462..92679be5101 100644 --- a/source/_components/logbook.markdown +++ b/source/_components/logbook.markdown @@ -11,7 +11,7 @@ ha_release: 0.7 The logbook integration provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse -chronological order. [See the demo for a live example](/demo/). It depends on +chronological order. It depends on the `recorder` integration for storing the data. This means that if the [`recorder`](/components/recorder/) integration is set up to use e.g., MySQL or PostgreSQL as data store, the `logbook` integration does not use the default From b1c42a1b43bef446bbd1ca03bd2f99bdec128b47 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 23 Jul 2019 06:21:22 -0400 Subject: [PATCH 19/67] Recorder page - rename component to integration (#9953) Changes 4 mentions of "component" to "integration" --- source/_components/recorder.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_components/recorder.markdown b/source/_components/recorder.markdown index f770db3fd89..512fc11a6d5 100644 --- a/source/_components/recorder.markdown +++ b/source/_components/recorder.markdown @@ -8,7 +8,7 @@ ha_release: pre 0.7 ha_qa_scale: internal --- -The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` component](/components/history/). +The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` integration](/components/history/). Home Assistant uses [SQLAlchemy](http://www.sqlalchemy.org/), which is an Object Relational Mapper (ORM). This means that you can use **any** SQL backend for the recorder that is supported by SQLAlchemy, like [MySQL](https://www.mysql.com/), [MariaDB](https://mariadb.org/), [PostgreSQL](https://www.postgresql.org/), or [MS SQL Server](https://www.microsoft.com/en-us/sql-server/). @@ -23,7 +23,7 @@ recorder: {% configuration %} recorder: - description: Enables the recorder component. Only allowed once. + description: Enables the recorder integration. Only allowed once. required: true type: map keys: @@ -115,7 +115,7 @@ recorder: - sensor.date ``` -If you only want to hide events from your history, take a look at the [`history` component](/components/history/). The same goes for the [logbook](/components/logbook/). But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the `exclude`/`include` options of the `recorder` component. That way they aren't even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`). +If you only want to hide events from your history, take a look at the [`history` integration](/components/history/). The same goes for the [logbook](/components/logbook/). But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the `exclude`/`include` options of the `recorder` integration. That way they aren't even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`). ### Service `purge` From d662b36198dabe1b76fd19397bc7ab7bfb4c277d Mon Sep 17 00:00:00 2001 From: michaeldavie Date: Tue, 23 Jul 2019 06:24:56 -0400 Subject: [PATCH 20/67] Add note on prerequisites to Environment Canada (#9951) * Add note regarding prerequisites * :ambulance: Fixed Markdown. Mixed with HTML requires spacing. --- source/_components/environment_canada.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_components/environment_canada.markdown b/source/_components/environment_canada.markdown index 3c229dd4594..9de19098664 100644 --- a/source/_components/environment_canada.markdown +++ b/source/_components/environment_canada.markdown @@ -18,6 +18,13 @@ The following device types and data are supported: - [Sensor](#sensor) - Current conditions and alerts - [Camera](#camera) - Radar imagery +

+ + On Raspbian or Hassbian, you may need to manually install additional prerequisites with the following command: + `sudo apt-get install libatlas-base-dev libopenjp2-7` + +

+ ## Location Selection Each platform automatically determines which weather station's data to use. However, as station coordinates provided by Environment Canada are somewhat imprecise, in some cases you may need to override the automatic selection to use the desired station. From e7e3397acc283d96631f6d6696c9b4a4ddfeb1f3 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Tue, 23 Jul 2019 20:56:00 +0100 Subject: [PATCH 21/67] Adding warning (#9960) * Adding warning As reported by multiple folks in the beta channel, looks like there's issues * :ambulance: Fixed Markdown --- source/_docs/z-wave/controllers.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_docs/z-wave/controllers.markdown b/source/_docs/z-wave/controllers.markdown index 35c96c5035c..b82dddb5f69 100644 --- a/source/_docs/z-wave/controllers.markdown +++ b/source/_docs/z-wave/controllers.markdown @@ -7,6 +7,12 @@ description: "Extended instructions how to setup Z-Wave." You need to have a compatible Z-Wave stick or module installed. This needs to be a *static controller*, which most Z-Wave sticks and modules will be. If yours is a *bridge* device then it won't work with [OpenZWave](http://openzwave.com/), which is what provides Home Assistant's Z-Wave capabilities. The following devices have been confirmed to work: +

+ +There have [been reports](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) of the Aeotec stick not working on the Raspberry Pi 4. + +

+ * Aeotec Z-Stick Series 5 * Everspring USB stick - Gen 5 * Sigma Designs UZB stick From 0047c75467656ecd6fe91ec37c750565ab9792ab Mon Sep 17 00:00:00 2001 From: Jeff Irion Date: Tue, 23 Jul 2019 13:13:54 -0700 Subject: [PATCH 22/67] Update link to the full list of ADB key commands (#9961) --- source/_components/androidtv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/androidtv.markdown b/source/_components/androidtv.markdown index 84fa928582a..660860063a5 100644 --- a/source/_components/androidtv.markdown +++ b/source/_components/androidtv.markdown @@ -232,6 +232,6 @@ Available key commands include: - `BACK` - `MENU` -The full list of key commands can be found [here](https://github.com/JeffLIrion/python-androidtv/blob/e1c07176efc9216cdcff8245c920224c0234ea56/androidtv/constants.py#L115-L155). +The full list of key commands can be found [here](https://github.com/JeffLIrion/python-androidtv/blob/bf1058a2f746535921b3f5247801469c4567e51a/androidtv/constants.py#L143-L186). You can also use the command `GET_PROPERTIES` to retrieve the properties used by Home Assistant to update the device's state. These will be stored in the media player's `'adb_response'` attribute and logged at the INFO level, this information can be used to help improve state detection in the backend [androidtv](https://github.com/JeffLIrion/python-androidtv) package. From 32603662fa9d0a2ab6596b27dd9661b12b42d353 Mon Sep 17 00:00:00 2001 From: Alec Rust Date: Tue, 23 Jul 2019 21:15:21 +0100 Subject: [PATCH 23/67] Fix Markdown link (#9959) --- source/_components/cast.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/cast.markdown b/source/_components/cast.markdown index 21f939240e1..59ac474f86e 100644 --- a/source/_components/cast.markdown +++ b/source/_components/cast.markdown @@ -11,7 +11,7 @@ redirect_from: /components/media_player.cast/ --- Google Cast devices like Android TVs and Chromecasts will be automatically -discovered if you enable [the discovery integration(/components/discovery/). If +discovered if you enable [the discovery integration](/components/discovery/). If you don't have the discovery integration enabled, you can enable the Cast integration by going to the Integrations page inside the config panel. From e93572a45c48ef3787c2a9139a76ac501d52eb42 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 23 Jul 2019 17:14:56 -0700 Subject: [PATCH 24/67] Release 96.4 --- _config.yml | 4 +-- source/_posts/2019-07-17-release-96.markdown | 27 ++++++++++++++++++++ 2 files changed, 29 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index c0b11998288..2e4d5e75e81 100644 --- a/_config.yml +++ b/_config.yml @@ -99,8 +99,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 96 -current_patch_version: 3 -date_released: 2019-07-21 +current_patch_version: 4 +date_released: 2019-07-23 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index 0b019205967..0549951710e 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -218,6 +218,33 @@ The Home Assistant Podcast has published [episode 53](https://hasspodcast.io/ha0 [zha docs]: /components/zha/ [zwave docs]: /components/zwave/ +## Release 0.96.4 - July 23 + +- Fix Netatmo climate battery level ([@cgtobi] - [#25165]) ([netatmo docs]) +- Tweak evohome migration ([@zxdavb] - [#25281]) ([evohome docs]) +- Bump pyatmo version to 2.1.2 ([@cgtobi] - [#25296]) ([netatmo docs]) +- [climate] Bugfix/Tweak honeywell migration ([@zxdavb] - [#25369]) ([honeywell docs]) +- Update Daikin preset modes ([@fredrike] - [#25395]) ([daikin docs]) +- Update pysonos to 0.0.22 ([@amelchio] - [#25399]) ([sonos docs]) +- [climate] Correct evohome hvac_action ([@zxdavb] - [#25407]) ([evohome docs]) + +[#25165]: https://github.com/home-assistant/home-assistant/pull/25165 +[#25281]: https://github.com/home-assistant/home-assistant/pull/25281 +[#25296]: https://github.com/home-assistant/home-assistant/pull/25296 +[#25369]: https://github.com/home-assistant/home-assistant/pull/25369 +[#25395]: https://github.com/home-assistant/home-assistant/pull/25395 +[#25399]: https://github.com/home-assistant/home-assistant/pull/25399 +[#25407]: https://github.com/home-assistant/home-assistant/pull/25407 +[@amelchio]: https://github.com/amelchio +[@cgtobi]: https://github.com/cgtobi +[@fredrike]: https://github.com/fredrike +[@zxdavb]: https://github.com/zxdavb +[daikin docs]: /components/daikin/ +[evohome docs]: /components/evohome/ +[honeywell docs]: /components/honeywell/ +[netatmo docs]: /components/netatmo/ +[sonos docs]: /components/sonos/ + ## If you need help... ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). From a586093fabb5cea1657be63e72d6c837d9ba3ab4 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Wed, 24 Jul 2019 03:22:17 -0400 Subject: [PATCH 25/67] Minor tweaks to notify page (#9964) Fix developer tools changes, rename component to integration, case changes, other very minor tweaks. --- source/_components/notify.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown index 5dbb6d04ab7..f9c43ccf489 100644 --- a/source/_components/notify.markdown +++ b/source/_components/notify.markdown @@ -10,7 +10,7 @@ ha_release: 0.7 The `notify` integration makes it possible to send notifications to a wide variety of platforms. Please check the sidebar for a full list of platforms that are supported. -If you want to send notifications to the Home Assistant Web Interface you may use the [Persistent Notification Component](/components/persistent_notification/). +If you want to send notifications to the Home Assistant web interface, you may use the [Persistent Notification integration](/components/persistent_notification/). ## Service @@ -19,11 +19,11 @@ Once loaded, the `notify` platform will expose a service that can be called to s | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `message` | no | Body of the notification. -| `title` | yes | Title of the notification. Default is `Home Assistant`. -| `target` | yes | Some platforms will allow specifying a recipient that will receive the notification. See your platform page if it is supported. +| `title` | yes | Title of the notification. +| `target` | yes | Some platforms allow specifying a recipient that will receive the notification. See your platform page if it is supported. | `data` | yes | On platforms who have extended functionality. See your platform page if it is supported. -The notification integration supports specifying [templates](/topics/templating/) with `data_template`. This will allow you to use the current state of Home Assistant in your notifications. +The notify integration supports specifying [templates](/topics/templating/) with `data_template`. This will allow you to use the current state of Home Assistant in your notifications. In an [action](/getting-started/automation-action/) of your [automation setup](/getting-started/automation/) it could look like this with a customized subject. @@ -37,7 +37,7 @@ action: ### Test if it works -A simple way to test if you have set up your notify platform correctly, is to use service developer tool icon **Services** from the **Developer Tools**. Choose your service from the dropdown menu **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**. +A simple way to test if you have set up your notify platform correctly, is to open **Developer Tools** from the sidebar and then select the **Services** tab. Choose your service from the **Service** dropdown menu, enter the sample below into the **Service Data** field, and press the **CALL SERVICE** button. ```json { From be066bb1a35860591950ca0666e4363f83e107b0 Mon Sep 17 00:00:00 2001 From: pander8828 <32925971+pander8828@users.noreply.github.com> Date: Wed, 24 Jul 2019 10:52:12 +0200 Subject: [PATCH 26/67] Update yi.markdown / solution for Pure-FTPd (#9958) * Update yi.markdown * Fix typo --- source/_components/yi.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_components/yi.markdown b/source/_components/yi.markdown index 5b8199ec54d..eb10adaa464 100644 --- a/source/_components/yi.markdown +++ b/source/_components/yi.markdown @@ -33,6 +33,12 @@ Currently, version 0.1.4-beta2 of the custom firmware is the highest supported w +
+ +If you use a version higher than 0.1.4-beta2, you can simply solve the FTP issue by creating a symlink to `/tmp` in the `/home/yi-hack-v4` directory (the directory name can be different depending on the version which you use). For example, access the Yi camera via SSH and type command: `ln -s /tmp tmp`. + +
+
Hassbian users: don't forget to install ffmpeg support on your platform, otherwise, you'll not see video.
From b45d12a35488eeeb7c0914ce3ad7b08906b2a5b4 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Wed, 24 Jul 2019 11:53:30 +0300 Subject: [PATCH 27/67] Fix links appearance (#9963) * Fix links appearance For some reason the links inside p tag are not rendered properly, but inside br tag it works properly. * Fix links Better fix (by adding space) --- source/_docs/installation/virtualenv.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index 5b7c6e917e2..f1766a13b7b 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -98,9 +98,11 @@ $ pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@ - It's recommended to run Home Assistant as a dedicated user. - If you want Home Assistant to automatically start at boot, check the [autostart docs](/docs/autostart/) -

+

+ Looking for more advanced guides? Check our [Raspbian guide](/docs/installation/raspberry-pi/) or the [other installation guides](/docs/installation/). -

+ +
### After upgrading Python From d02d29b6939ce817a09193d7c6f6f4b957ea69a7 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 24 Jul 2019 15:06:07 +0200 Subject: [PATCH 28/67] :ambulance: Fixes issue in version.json (#9966) --- source/version.json | 1 + 1 file changed, 1 insertion(+) diff --git a/source/version.json b/source/version.json index a120dcbb44d..460cd5faf54 100644 --- a/source/version.json +++ b/source/version.json @@ -1,4 +1,5 @@ --- +layout: null --- {% assign recent_release_post = site.categories['Release-Notes'].first %}{ "current_version": "{{ site.current_major_version }}.{{ site.current_minor_version }}.{{ site.current_patch_version }}", From 9963bd2fa0125e708c5f1c8166e1af08b3a8909e Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 24 Jul 2019 07:27:26 -0700 Subject: [PATCH 29/67] Clarify sidebar --- source/_posts/2019-07-17-release-96.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index 0549951710e..c5d70834b35 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -21,7 +21,7 @@ Home Assistant has adopted a new [Python support strategy](https://github.com/ho ## Pimp my Sidebar -The sidebar has gotten an improved look! Idea started with [a mockup by @JuanMTech on Twitter](https://twitter.com/JuanMTech/status/1143757213971943424) and grew into a full blown implementation. The sidebar will now always be visible in a minimized mode. Hovering it will expand it. The developer tool buttons have been collapsed into a single menu item. The dev tools will now store it's exact state when you navigate away, included the dev tool that is open. We've also taken the opportunity to make notifications accessible from the sidebar, instead of only via the Lovelace UI. +The sidebar has gotten an improved look! Idea started with [a mockup by @JuanMTech on Twitter](https://twitter.com/JuanMTech/status/1143757213971943424) and grew into a full blown implementation. When visiting Home Assistant on devices with big screens (tablets, laptops, desktops), the sidebar will now always be visible in a minimized mode with the ability to fully hide it via the profile page. The developer tool buttons have been collapsed into a single menu item. The dev tools will now store it's exact state when you navigate away, included the dev tool that is open. We've also taken the opportunity to make notifications accessible from the sidebar, instead of only via the Lovelace UI. On mobile devices the sidebar will behave like it previously did. Check [the demo](https://demo.home-assistant.io) for a preview. From 337a1659349f885dec44d40d8790ce18fd64e831 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 24 Jul 2019 23:01:29 +0200 Subject: [PATCH 30/67] :ambulance: Fixes type links in configuration blocks (#9968) --- plugins/configuration.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/configuration.rb b/plugins/configuration.rb index dd497576922..5a5b94b7bfa 100644 --- a/plugins/configuration.rb +++ b/plugins/configuration.rb @@ -37,7 +37,7 @@ module Jekyll type.strip! if TYPE_LINKS.include? type.downcase url = TYPE_LINKS[type.downcase] % {component: component} - "[%s](%s)" % [type, url] + "%s" % [url, type] else type end From 6038ba16172865c04efba4ed1674f2809f2a833e Mon Sep 17 00:00:00 2001 From: Maarten Date: Wed, 24 Jul 2019 21:05:25 +0000 Subject: [PATCH 31/67] Update attribute of input_datetime with icon: (#9967) * Update input_datetime.markdown It's possible to set an icon for input_datetime, but it's not mentioned in the documentation. * :pencil2: Tweak --- source/_components/input_datetime.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source/_components/input_datetime.markdown b/source/_components/input_datetime.markdown index 406575ab317..e04b2f692f5 100644 --- a/source/_components/input_datetime.markdown +++ b/source/_components/input_datetime.markdown @@ -53,6 +53,10 @@ input_datetime: required: false type: boolean default: false + icon: + description: Icon to display in the frontend. + required: false + type: icon initial: description: Set the initial value of this input, depending on `has_time` and `has_date`. required: false @@ -71,6 +75,7 @@ automations and templates. | `has_date` | `true` if this entity has a date. | `year`
`month`
`day` | The year, month and day of the date.
(only available if `has_| `hour`
`minute`
`second` | The hour, minute and second of the time.
(only available if `has_time: true`) | `timestamp` | A timestamp representing the time held in the input.
If `has_ + ### Restore State This integration will automatically restore the state it had prior to Home From 20143387eaba5c817f43acb909e4ebe974926f86 Mon Sep 17 00:00:00 2001 From: Fredrik Erlandsson Date: Wed, 24 Jul 2019 23:11:40 +0200 Subject: [PATCH 32/67] Add support for turn_on/off, add note on Away mode (#9965) * Add support for turn_on/off, add note on Away mode * Fix url * :pencil2: Tweak --- source/_components/daikin.markdown | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/source/_components/daikin.markdown b/source/_components/daikin.markdown index eb93f8840dc..9f952d233d8 100644 --- a/source/_components/daikin.markdown +++ b/source/_components/daikin.markdown @@ -57,9 +57,10 @@ The `daikin` climate platform integrates Daikin air conditioning systems into Ho - [**set_hvac_mode**](/components/climate/#service-climateset_hvac_mode) (off, heat, cool, auto, or fan only) - [**target temperature**](https://www.home-assistant.io/components/climate#service-climateset_temperature) +- [**turn on/off**](https://www.home-assistant.io/components/climate#service-climateturn_on) - [**fan mode**](https://www.home-assistant.io/components/climate#service-climateset_fan_mode) (speed) - [**swing mode**](https://www.home-assistant.io/components/climate#service-climateset_swing_mode) -- [**set_preset_mode**](https://www.home-assistant.io/components/climate#service-climateset_away_mode) (away, home) +- [**set_preset_mode**](https://www.home-assistant.io/components/climate#service-climateset_preset_mode) (away, none) Current inside temperature is displayed. @@ -69,6 +70,17 @@ Some models do not support setting of **fan speed** or **swing mode**. +
+ +Preset mode **away** translates to Daikin's *Holiday Mode*:
+*Holiday mode* is used when you want to turn off your units when you leave you home for a longer time.
+
+When *Holiday mode* is enabled, the following action take place: +- All connected units are turned OFF. +- All schedule timers are disabled." + +
+ ## Sensor The `daikin` sensor platform integrates Daikin air conditioning systems into Home Assistant, enabling displaying the following parameters: From 18b98032ae7ad89fb527ffd23a23eecbe61bd15a Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 25 Jul 2019 09:53:29 -0700 Subject: [PATCH 33/67] Release 0.96.5 --- _config.yml | 4 ++-- source/_posts/2019-07-17-release-96.markdown | 15 +++++++++++++++ 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 2e4d5e75e81..22f707391b6 100644 --- a/_config.yml +++ b/_config.yml @@ -99,8 +99,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 96 -current_patch_version: 4 -date_released: 2019-07-23 +current_patch_version: 5 +date_released: 2019-07-25 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index c5d70834b35..78eb93ed8a4 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -245,6 +245,21 @@ The Home Assistant Podcast has published [episode 53](https://hasspodcast.io/ha0 [netatmo docs]: /components/netatmo/ [sonos docs]: /components/sonos/ +## Release 0.96.5 - July 25 + +- Bump geniushub client ([@zxdavb] - [#25458]) ([geniushub docs]) +- Allow cors for static files ([@balloob] - [#25468]) ([http docs]) +- Fix Nest turning off eco ([@balloob] - [#25472]) ([nest docs]) + +[#25458]: https://github.com/home-assistant/home-assistant/pull/25458 +[#25468]: https://github.com/home-assistant/home-assistant/pull/25468 +[#25472]: https://github.com/home-assistant/home-assistant/pull/25472 +[@balloob]: https://github.com/balloob +[@zxdavb]: https://github.com/zxdavb +[geniushub docs]: /components/geniushub/ +[http docs]: /components/http/ +[nest docs]: /components/nest/ + ## If you need help... ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). From bea02c883f61458dcad0161cf1c385881ca15308 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 25 Jul 2019 21:39:21 -0700 Subject: [PATCH 34/67] Fix Twitter social image --- source/_includes/site/head.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_includes/site/head.html b/source/_includes/site/head.html index 5ad9eff0a27..c6455ea4b25 100644 --- a/source/_includes/site/head.html +++ b/source/_includes/site/head.html @@ -26,7 +26,7 @@ {% if page.author_twitter %}{% endif %} - + From 56a1ad935e2ab0dffe723eea8e23ce2f548c85e2 Mon Sep 17 00:00:00 2001 From: Kanga-Who Date: Fri, 26 Jul 2019 21:58:38 +1000 Subject: [PATCH 35/67] Extends Hass.io installation manual for generic Linux (#9972) * Update installation.markdown * Update installation.markdown * :pencil2: Extends machine type list * :pencil2: Minor tweak --- source/hassio/installation.markdown | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 9a316216e60..7cd33f94fc3 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -141,7 +141,7 @@ You also need to have Docker-CE installed. There are well-documented procedures -To perform the Hass.io installation on Ubuntu, run the following commands: +To prepare your machine for the Hass.io installation, run the following commands: ```bash sudo -i @@ -152,12 +152,30 @@ apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificat curl -fsSL get.docker.com | sh ``` -And to install Hass.io the one below. That one is used also for other distributions. +The following script will then install Hass.io on a variety of operating systems and machine types. ```bash curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s ``` +Some installation types require flags to identify the computer type, for example, when using a Raspberry Pi 3, the flag `-- -m raspberrypi3` is required. The install script would then look like this: + +```bash +curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s -- -m raspberrypi3 +``` + +#### Other machine types + + - `intel-nuc` + - `raspberrypi` + - `raspberrypi2` + - `raspberrypi3` + - `raspberrypi3-64` + - `odroid-c2` + - `odroid-cu2` + - `odriod-xu` + - `orangepi-prime` +
When you use this installation method, the core SSH add-on may not function correctly. If that happens, use the community SSH add-on. Some of the documentation might not work for your installation either.
From 7c008914be3d0c37672144e3c85a2e5bbb12effc Mon Sep 17 00:00:00 2001 From: tubalainen Date: Fri, 26 Jul 2019 14:39:25 +0200 Subject: [PATCH 36/67] Integrations via the GUI (#9973) Added information about that the component can be added via the GUI - Integrations function. --- source/_components/wwlln.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/wwlln.markdown b/source/_components/wwlln.markdown index f44fad3d8da..79868f1b854 100644 --- a/source/_components/wwlln.markdown +++ b/source/_components/wwlln.markdown @@ -25,9 +25,9 @@ New data is returned every 10 minutes. ## Configuration -To retrieve data from the WWLLN, add the following to your `configuration.yaml` -file: +To retrieve data from the WWLLN, edit your `configuration.yaml` file manually or use the "Integrations" feature in the GUI, you find it under Configurations - Integrations. +To manually add the component, add the following to your `configuration.yaml`: ```yaml wwlln: ``` From 59b92ef9a2c2bf20288555651e648a7b0da9b727 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Magnus=20=C3=98verli?= Date: Fri, 26 Jul 2019 15:09:41 +0200 Subject: [PATCH 37/67] Added info on supported Ubuntu versions (#9940) * Added info on supported Ubuntu versions Adding a note on the latest docker-supported version of Ubuntu. * Added info on supported versions of Ubuntu Added a note to remind users that docker needs to be supported by their version of Ubuntu, and where to check if it is. --- source/hassio/installation.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 7cd33f94fc3..c2206d779e5 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -138,6 +138,8 @@ You also need to have Docker-CE installed. There are well-documented procedures Some distributions, like Ubuntu, have a `docker.io` package available. Using that packages will cause issues! Be sure to install the official Docker-CE from the above listed URL. + + Docker is not always ready with a release when a new Ubuntu version is out. Check if your version of Ubuntu is supported by docker [here](https://docs.docker.com/install/linux/docker-ce/ubuntu/). From 1df189b778b1241c8f18b6e4e3d56341076555d0 Mon Sep 17 00:00:00 2001 From: Marius <33354141+Mariusthvdb@users.noreply.github.com> Date: Fri, 26 Jul 2019 16:06:23 +0200 Subject: [PATCH 38/67] several changes to Manual Alarm panel doc (#9969) * several changes to Manual Alarm panel doc took out the double underscores in the sensor.date_time templates changed the data field to data_template field where applicable (since the messages use the template) commented out the initial_state: 'on', since that is no longer required provided 1 example using multi-line notation * Update manual.markdown all agreed and changed --- source/_components/manual.markdown | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/source/_components/manual.markdown b/source/_components/manual.markdown index f8d3340621f..fc33d00a268 100644 --- a/source/_components/manual.markdown +++ b/source/_components/manual.markdown @@ -214,59 +214,57 @@ Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pend {% raw %} ```yaml - alias: 'Send notification when alarm is Disarmed' - initial_state: 'on' trigger: - platform: state entity_id: alarm_control_panel.home_alarm to: 'disarmed' action: - service: notify.notify - data: - message: "ALARM! The alarm is Disarmed at {{ states('sensor.date__time') }}" + data_template: + message: "ALARM! The alarm is Disarmed at {{ states('sensor.date_time') }}" ``` {% endraw %} {% raw %} ```yaml - alias: 'Send notification when alarm is in pending status' - initial_state: 'on' trigger: - platform: state entity_id: alarm_control_panel.home_alarm to: 'pending' action: - service: notify.notify - data: - message: "ALARM! The alarm is in pending status at {{ states('sensor.date__time') }}" + data_template: + message: "ALARM! The alarm is in pending status at {{ states('sensor.date_time') }}" ``` {% endraw %} {% raw %} ```yaml - alias: 'Send notification when alarm is Armed in Away mode' - initial_state: 'on' trigger: - platform: state entity_id: alarm_control_panel.home_alarm to: 'armed_away' action: - service: notify.notify - data: - message: "ALARM! The alarm is armed in Away mode {{ states('sensor.date__time') }}" + data_template: + message: "ALARM! The alarm is armed in Away mode {{ states('sensor.date_time') }}" ``` {% endraw %} {% raw %} ```yaml - alias: 'Send notification when alarm is Armed in Home mode' - initial_state: 'on' trigger: - platform: state entity_id: alarm_control_panel.home_alarm to: 'armed_home' action: - service: notify.notify - data: - message: "ALARM! The alarm is armed in Home mode {{ states('sensor.date__time') }}" + data_template: + # Using multi-line notation allows for easier quoting + message: > + ALARM! The alarm is armed in Home mode {{ states('sensor.date_time') }} ``` {% endraw %} From 5b8206b58ccd0ba77beaf761f4886593fb19d835 Mon Sep 17 00:00:00 2001 From: ambarkhuizen <52946823+ambarkhuizen@users.noreply.github.com> Date: Fri, 26 Jul 2019 20:02:22 +0200 Subject: [PATCH 39/67] Update history-graph.markdown (#9978) * Update history-graph.markdown Changed minimum time_to_show from 10 to 1 * :pencil2: Tweak --- source/_lovelace/history-graph.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_lovelace/history-graph.markdown b/source/_lovelace/history-graph.markdown index 50d5224e013..29d155e143d 100644 --- a/source/_lovelace/history-graph.markdown +++ b/source/_lovelace/history-graph.markdown @@ -27,7 +27,7 @@ entities: type: list hours_to_show: required: false - description: Hours to show. Minimum is 10 hours, maximum of 80 hours. + description: Hours to show. Minimum is 1 hour, maximum of 80 hours. type: integer default: 24 refresh_interval: From 751662c904898551f2221139f2f899652487d3c7 Mon Sep 17 00:00:00 2001 From: Michal Date: Fri, 26 Jul 2019 22:23:47 +0100 Subject: [PATCH 40/67] Update rest_command.markdown (#9979) --- source/_components/rest_command.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/rest_command.markdown b/source/_components/rest_command.markdown index 3f0797b8f91..98d518d6174 100644 --- a/source/_components/rest_command.markdown +++ b/source/_components/rest_command.markdown @@ -24,7 +24,7 @@ rest_command: {% configuration %} service_name: - description: The name used to expose the service. E.g., in the above example, it would be 'rest_command.service_name'. + description: The name used to expose the service. E.g., in the above example, it would be 'rest_command.example_request'. required: true type: map keys: From 0315f476c2637a068c69ae0b4c487ccd3df41908 Mon Sep 17 00:00:00 2001 From: SimonThoustrup <41516634+SimonThoustrup@users.noreply.github.com> Date: Sat, 27 Jul 2019 23:40:57 +0200 Subject: [PATCH 41/67] Change sequence of commands to virtualenv before activate (#9980) --- source/_docs/installation/freenas.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/installation/freenas.markdown b/source/_docs/installation/freenas.markdown index 47fc0dcf4a7..5ea23f33090 100644 --- a/source/_docs/installation/freenas.markdown +++ b/source/_docs/installation/freenas.markdown @@ -42,8 +42,8 @@ Install Home Assistant itself: ```bash # su homeassistant % cd /usr/local/share/homeassistant -% source ./bin/activate.csh % virtualenv -p python3.7 . +% source ./bin/activate.csh % pip3 install homeassistant % deactivate % exit From 01c786781b9e5830a22f6eef1fd7c706fbd1386a Mon Sep 17 00:00:00 2001 From: Anders Melchiorsen Date: Sun, 28 Jul 2019 12:17:20 +0200 Subject: [PATCH 42/67] Add raw tags to netgear_lte example (#9989) --- source/_components/netgear_lte.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_components/netgear_lte.markdown b/source/_components/netgear_lte.markdown index 0c1f7e61bdd..5905d2950b8 100644 --- a/source/_components/netgear_lte.markdown +++ b/source/_components/netgear_lte.markdown @@ -171,6 +171,7 @@ This service can set modem configuration options (otherwise available in the mod The following automation example processes incoming SMS messages with the [Conversation](/components/conversation/) integration and then deletes the message from the inbox. +{% raw %} ```yaml automation: - alias: SMS conversation @@ -186,3 +187,4 @@ automation: host: '{{ trigger.event.data.host }}' sms_id: '{{ trigger.event.data.sms_id }}' ``` +{% endraw %} From 0e36ae0d842a3c9eb661e37d868d28762fb0db67 Mon Sep 17 00:00:00 2001 From: svedese <37276705+svedese@users.noreply.github.com> Date: Sun, 28 Jul 2019 19:23:48 +0200 Subject: [PATCH 43/67] Updated with data_template (#9994) Changed "data:" in "data_template:" as suggested in: https://www.home-assistant.io/docs/automation/templating/ --- source/_components/blink.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/blink.markdown b/source/_components/blink.markdown index 9227f6b2f23..a53b546b95e 100644 --- a/source/_components/blink.markdown +++ b/source/_components/blink.markdown @@ -220,7 +220,7 @@ Again, this example assumes your camera's name (in the blink app) is `My Camera` to: 'on' action: service: blink.save_video - data: + data_template: name: "My Camera" filename: "/tmp/videos/blink_video_{{ now().strftime('%Y%m%d_%H%M%S') }}.mp4" From bf12bae4384a27c4461c21fd137659bbbecc5a09 Mon Sep 17 00:00:00 2001 From: "Carlos Duarte Do Nascimento (Chester)" Date: Sun, 28 Jul 2019 13:26:59 -0400 Subject: [PATCH 44/67] Minor clarification on Telegram bot setup (#9988) * clarify: ID only returned if a message was sent It took me quite a long time fighting a near-empty empty JSON * Drop redundant phrase Next paragraph has it all --- source/_components/telegram.markdown | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/source/_components/telegram.markdown b/source/_components/telegram.markdown index 067534e6dca..6594709dc91 100644 --- a/source/_components/telegram.markdown +++ b/source/_components/telegram.markdown @@ -20,9 +20,7 @@ The requirements are: - You need to configure a [Telegram bot in Home Assistant](/components/telegram_bot) and define there your API key and the allowed chat ids to interact with. - The `chat_id` of an allowed user. -To retrieve your `chat_id`, contact any of the Telegram bots created for this purpose (@myidbot, @get_id_bot) - -The quickest way to retrieve your `chat_id` is visiting [https://api.telegram.org/botYOUR_API_TOKEN/getUpdates](https://api.telegram.org/botYOUR_API_TOKEN/getUpdates) or to use `$ curl -X GET https://api.telegram.org/botYOUR_API_TOKEN/getUpdates`. Replace `YOUR_API_TOKEN` with your actual token. +The quickest way to retrieve your `chat_id` is visiting [https://api.telegram.org/botYOUR_API_TOKEN/getUpdates](https://api.telegram.org/botYOUR_API_TOKEN/getUpdates) or to use `$ curl -X GET https://api.telegram.org/botYOUR_API_TOKEN/getUpdates` **after** you have sent the bot a message. Replace `YOUR_API_TOKEN` with your actual token. The result set will include your chat ID as `id` in the `chat` section: From d57ce11313cce99cef8ed78c9d3362bcc81b5b7a Mon Sep 17 00:00:00 2001 From: Keith Pine Date: Sun, 28 Jul 2019 11:33:20 -0700 Subject: [PATCH 45/67] Update installation.markdown (#9985) Remove instructions to install libopenzwave1.5 on Linux installs. This instruction causes a lot of problems as the installed files interfere with the Python openzwave installation. --- source/_docs/z-wave/installation.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index 1b8caee77ae..82949532be1 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -160,11 +160,10 @@ On the Raspberry Pi you will need to enable the serial interface in the `raspi-c #### Linux (except Hassbian) -On Debian Linux platforms there two dependencies you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems): +On Debian Linux platforms there are dependencies you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems): ```bash $ sudo apt-get install libudev-dev -$ sudo apt-get install libopenzwave1.5-dev ``` You may also have to install the Python development libraries for your version of Python. For example `libpython3.6-dev`, and possibly `python3.6-dev` if you're using Python 3.6. From b58d0740ba19aaf9f39a5d6d04f7973fa0b91d7f Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Mon, 29 Jul 2019 03:33:41 -0400 Subject: [PATCH 46/67] Add note on Advanced mode toggle (#10001) Customization menu will be hidden by default starting in 0.96, unless the user toggles on Advanced mode first. --- source/_docs/configuration/customizing-devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index 0a9ff25575e..420cd090a76 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -19,7 +19,7 @@ By default, all of your devices will be visible and have a default icon determin ### Customization using the UI -Under the *Configuration* menu you'll find the *Customization* menu. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those, or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). +Under the *Configuration* menu you'll find the *Customization* menu. If this menu item is not visible, enable advanced mode on your [profile page](/docs/authentication/#your-account-profile) first. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those, or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). #### Possible values From c9e85b9361fdd1e0bc3b9dc71e92f521329b7a12 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Mon, 29 Jul 2019 03:34:45 -0400 Subject: [PATCH 47/67] Update basic setup instructions for onboarding (#10000) Updated instructions to reflect onboarding improvements in Home Assistant 0.94 (see video in blog post: https://www.home-assistant.io/blog/2019/06/05/release-94/) and mention the fact that this can be updated directly in the user interface now. --- source/_docs/configuration/basic.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_docs/configuration/basic.markdown b/source/_docs/configuration/basic.markdown index dde064c07b7..ff2bf2c2943 100644 --- a/source/_docs/configuration/basic.markdown +++ b/source/_docs/configuration/basic.markdown @@ -4,7 +4,9 @@ description: "Setting up the basic info of Home Assistant." redirect_from: /getting-started/basic/ --- -By default, Home Assistant will try to detect your location from IP address geolocation. Home Assistant will automatically select a temperature unit and time zone based on this location. You can overwrite this by adding the following information to your `configuration.yaml`: +As part of the default onboarding proccess, Home Assistant can detect your location from IP address geolocation. Home Assistant will automatically select a temperature unit and time zone based on this location. You may adjust this during onboarding, or afterwards at Configuration -> General. + +If you prefer YAML, you can add the following information to your `configuration.yaml`: ```yaml homeassistant: From 7f13b27ce2ce91090fb145eb001cf9af200d5093 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Mon, 29 Jul 2019 03:35:56 -0400 Subject: [PATCH 48/67] Update outdated PS4 integration information (#9999) * This removes outdated info about the PS4 integration only supporting a single console. Support for that was added in 0.90 a few months back (PR here: https://github.com/home-assistant/home-assistant/pull/21302). * Added field to sidebar that it's configurable from UI (that's the *only* way it can be configured in fact which the docs already mention). * Also tweaks the instructions to reflect design changes that were made to Home Assistant Integrations panel (must press the + button to add integrations). * Lastly updated a URL that was changed in the Dev Tools redesign in 0.96 release (`/dev-info` has now become `/developer-tools/info`). --- source/_components/ps4.markdown | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/source/_components/ps4.markdown b/source/_components/ps4.markdown index 0f006beecee..baadd494be5 100644 --- a/source/_components/ps4.markdown +++ b/source/_components/ps4.markdown @@ -5,14 +5,13 @@ logo: ps4.png ha_category: - Media Player ha_release: 0.89 +ha_config_flow: true ha_iot_class: Local Polling --- The `ps4` integration allows you to control a [Sony PlayStation 4 console](https://www.playstation.com/en-us/explore/ps4/). -- This integration supports controlling a single PlayStation 4 for your instance. Additional consoles may be supported in a future release. - ## Requirements - Android or iOS device @@ -26,7 +25,7 @@ The `ps4` integration allows you to control a Read the section "Granting Port Access" below before continuing. -2. Navigate to `Configuration -> Integrations` and select `Configure` for `PlayStation 4`. +2. Navigate to `Configuration -> Integrations` and press the plus button in the bottom right corner. Select `PlayStation 4` from the list of integrations. 3. Follow instructions displayed to generate user credentials. You will know this step is completed when a form with fields appears. @@ -71,7 +70,7 @@ sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.5 To find your system Python path: -- Add the [System Health](/components/system_health/) integration to your `configuration.yaml`. In a web browser access your frontend and navigate to the about/logs page "http:///dev-info). In the System Health box locate the item **python_version** and note the value that is displayed. Then in terminal run: +- Add the [System Health](/components/system_health/) integration to your `configuration.yaml`. In a web browser access your frontend and navigate to the about/logs page "http:///developer-tools/info). In the System Health box locate the item **python_version** and note the value that is displayed. Then in terminal run: ```bash whereis python From 9de3f9d554aa0ed4d9a493f97317d3ba8ce0a07e Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Mon, 29 Jul 2019 03:36:35 -0400 Subject: [PATCH 49/67] Note that Life360 is configurable through UI (#9998) --- source/_components/life360.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/life360.markdown b/source/_components/life360.markdown index 43ee24c7def..1da8d6524ad 100644 --- a/source/_components/life360.markdown +++ b/source/_components/life360.markdown @@ -3,6 +3,7 @@ title: "Life360" description: "Instructions how to use Life360 to track devices in Home Assistant." logo: life360.png ha_release: 0.95 +ha_config_flow: true ha_category: - Presence Detection ha_iot_class: Cloud Polling From bbf18982e4ef0bbdc17ff45201ef973e7c2c065c Mon Sep 17 00:00:00 2001 From: VDRainer <26381449+VDRainer@users.noreply.github.com> Date: Mon, 29 Jul 2019 12:07:53 +0200 Subject: [PATCH 50/67] Set default payloads in quotes because the docs show true/false (#10002) https://github.com/home-assistant/home-assistant/blob/a90ec88e5c7098e11fbcf8212c8bc9dcae713a60/homeassistant/components/command_line/binary_sensor.py#L19-L20 https://community.home-assistant.io/t/command-line-binary-sensor-never-switches-to-on/128840?u=vdrainer --- source/_components/command_line.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/command_line.markdown b/source/_components/command_line.markdown index 9761296bdaf..c22e5a513d1 100644 --- a/source/_components/command_line.markdown +++ b/source/_components/command_line.markdown @@ -47,12 +47,12 @@ payload_on: description: The payload that represents enabled state. required: false type: string - default: ON + default: 'ON' payload_off: description: The payload that represents disabled state. required: false type: string - default: OFF + default: 'OFF' value_template: description: Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload. required: false From 44213344d4ee4036c3454d4da773fe24fa741b17 Mon Sep 17 00:00:00 2001 From: 7even Date: Mon, 29 Jul 2019 17:14:44 +0200 Subject: [PATCH 51/67] Update sensibo.markdown (#10004) --- source/_components/sensibo.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensibo.markdown b/source/_components/sensibo.markdown index 1ebefcad72c..aac799d56d3 100644 --- a/source/_components/sensibo.markdown +++ b/source/_components/sensibo.markdown @@ -61,12 +61,12 @@ switch: friendly_name: "AC" value_template: "{{ is_state('climate.ac', 'cool') or is_state('climate.ac', 'heat') or is_state('climate.ac', 'dry') or is_state('climate.ac', 'fan_only') }}" turn_on: - service: climate.set_havc_mode + service: climate.set_hvac_mode data: entity_id: climate.ac hvac_mode: cool turn_off: - service: climate.set_havc_mode + service: climate.set_hvac_mode data: entity_id: climate.ac hvac_mode: off From 5b670502312a62ad5004e8deec6a2c911b2affe5 Mon Sep 17 00:00:00 2001 From: gjbadros Date: Mon, 29 Jul 2019 11:10:24 -0700 Subject: [PATCH 52/67] Corrected an example (#10005) This example is trying to draw a distinction but has two identical lines. I suspect this came from a search and replace to switch to the newer states('') notation. --- source/_docs/configuration/templating.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index 018c7a5bedc..042c19a0c3a 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -74,7 +74,7 @@ The next two statements result in the same value if the state exists. The second {% raw %} ```text {{ states('device_tracker.paulus') }} -{{ states('device_tracker.paulus') }} +{{ states.device_tracker.paulus }} ``` {% endraw %} From 8743f8487b40a6b1c13f1c3715583d9416df16c1 Mon Sep 17 00:00:00 2001 From: Max Rumpf Date: Mon, 29 Jul 2019 21:28:47 +0200 Subject: [PATCH 53/67] Add logo & category to the weather info page, remove side bar hint (#10006) Since there is no real sidebar anymore, we should link to the component category instead. --- source/_components/weather.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_components/weather.markdown b/source/_components/weather.markdown index 4efe19bfe16..55683718b6a 100644 --- a/source/_components/weather.markdown +++ b/source/_components/weather.markdown @@ -1,12 +1,16 @@ --- title: "Weather" description: "Instructions on how to setup your Weather platforms with Home Assistant." +logo: home-assistant.png +ha_category: + - Weather +ha_qa_scale: internal ha_release: 0.32 --- -The `weather` platforms are gathering meteorological information from web services and display the conditions and other details about the weather at the given location. +The `weather` platforms are gathering meteorological information from web services and display the conditions and other details about the weather at the given location. Read the integration documentation for your particular weather provider to learn how to set it up. -Home Assistant currently supports free web services and such which require a registration. Please check the sidebar for a full list of supported `weather` platforms. +Home Assistant currently supports free web services and such which require a registration. ## Condition mapping From 5b3426b94dff2e944360f0583b60a0ff3bff8d70 Mon Sep 17 00:00:00 2001 From: Adam <22942687+SilvrrGIT@users.noreply.github.com> Date: Tue, 30 Jul 2019 17:55:23 -0500 Subject: [PATCH 54/67] Remove Outdated text (#10012) The option to 'Try out the new Lovelace UI" is no longer available and Lovelace is the default so this text is not needed. --- source/_docs/tools/dev-tools.markdown | 3 --- 1 file changed, 3 deletions(-) diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index f5ce662e245..887195c8113 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -95,6 +95,3 @@ Even though MQTT in general provides deeper functionality, the developer tools s Info The Information tab simply provides information about the current installed version, additional links and credits. The tab also contains a section that shows `syslog` information, and the contents of `home-assistant.log` with an option to clear and refresh the logs. - -The Information tab also allows makes it possible to try out the Lovelace User Interface (UI) by clicking "Try out the new Lovelace UI" or set Lovelace as the default UI, so that when the "Overview" link in the Sidebar is selected, the Lovelace UI will load by default. - From 9dcdcdc305f1a8277a279f2ac747d75c71fc5bed Mon Sep 17 00:00:00 2001 From: Baruch Rothkoff Date: Wed, 31 Jul 2019 02:03:13 +0300 Subject: [PATCH 55/67] Fix title hirarchy (#10011) It is not clear that `Restart` and the other nex titles are relevant to all installation types --- source/_docs/installation/docker.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_docs/installation/docker.markdown b/source/_docs/installation/docker.markdown index 932e68cd097..392e5bf5523 100644 --- a/source/_docs/installation/docker.markdown +++ b/source/_docs/installation/docker.markdown @@ -4,6 +4,8 @@ description: "Instructions to install Home Assistant on a Docker." redirect_from: /getting-started/installation-docker/ --- +## Platform Installation + Installation with Docker is straightforward. Adjust the following command so that `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration and run it: ### Linux @@ -176,14 +178,14 @@ device_tracker: - platform: bluetooth_tracker ``` -### Restart +## Restart If you change the configuration you have to restart the server. To do that you have 2 options. 1. You can go to the service developer tool icon service developer tools, select the service `homeassistant/restart` and click "Call Service". 2. Or you can restart it from a terminal by running `docker restart home-assistant` -### Docker Compose +## Docker Compose As the docker command becomes more complex, switching to `docker-compose` can be preferable and support automatically restarting on failure or system restart. Create a `docker-compose.yml` file: @@ -212,7 +214,7 @@ To restart Home Assistant when you have changed configuration: $ docker-compose restart ``` -### Exposing Devices +## Exposing Devices In order to use Z-Wave, Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your docker command: From ca4bd45df9067f0323c6f4ee1e65fe571fb75eb2 Mon Sep 17 00:00:00 2001 From: Alex Molodoj Date: Wed, 31 Jul 2019 01:36:19 +0200 Subject: [PATCH 56/67] Clarification regarding Alexa's proactive mode (#9863) * Clarification regarding Alexa's proactive mode Clarification to restart HA as well as modified lambda function are added following the issue https://github.com/home-assistant/home-assistant/issues/24867#issuecomment-509063673 * Update alexa.smart_home.markdown * Update alexa.smart_home.markdown --- source/_components/alexa.smart_home.markdown | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/source/_components/alexa.smart_home.markdown b/source/_components/alexa.smart_home.markdown index 67ae364ab49..f3618932853 100644 --- a/source/_components/alexa.smart_home.markdown +++ b/source/_components/alexa.smart_home.markdown @@ -97,7 +97,7 @@ Next you need create a Lambda function. - Under `Configuration` tab, expand `Designer`, then click `Alexa Smart Home` in the left part of the panel to add a Alexa Smart Home trigger to your Lambda function. - Scroll down little bit, you need input the `Skill ID` from the skill you created in previous step. (tips: you may need switch back to Alexa Developer Console to copy the `Skill ID`. - Click your Lambda Function icon in the middle of the diagram, scroll down you will see a `Function code` window. -- Clear the example code, copy the Python script from: +- Clear the example code, copy the Python script from: (modified code to support Alexa's proactive mode, see details below) - Scroll down a little bit, you will find `Environment variables`, you need add 4 environment variables: * BASE_URL *(required)*: your Home Assistant instance's Internet accessible URL with port if need * NOT_VERIFY_SSL *(optional)*: you can set it to *True* to ignore the SSL issue, if you don't have a valid SSL certificate or you are using self-signed certificate. @@ -168,7 +168,7 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom * `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token * `Client ID`: - https://pitangui.amazon.com/ if you are in US - - https://layla.amazon.com/ if you are in EU (not verified yet) + - https://layla.amazon.com/ if you are in EU - https://alexa.amazon.co.jp/ if you are in JP and AU (not verified yet) The trailing slash is important here. @@ -216,12 +216,11 @@ alexa: display_categories: LIGHT ``` -The `endpoint`, `client_id` and `client_secret` are optional, and are only required if you want to enable Alexa's proactive mode. Please note the following if you want to enable proactive mode: +The `endpoint`, `client_id` and `client_secret` are optional, and are only required if you want to enable Alexa's proactive mode (i.e. "Send Alexa Events" enabled). Please note the following if you want to enable proactive mode: - There are different endpoint URLs, depending on the region of your skill. Please check the available endpoints at - The `client_id` and `client_secret` are not the ones used by the skill that have been set up using "Login with Amazon" (in the [Alexa Developer Console][amazon-dev-console]: Build > Account Linking), but rather from the "Alexa Skill Messaging" (in the Alexa Developer Console: Build > Permissions > Alexa Skill Messaging). To get them, you need to enable the "Send Alexa Events" permission. -- If the "Send Alexa Events" permission was not enabled previously, you need to unlink and relink the skill using the Alexa App, or else Home Assistant will show the following error: "Token invalid and no refresh token available." - +- If the "Send Alexa Events" permission was not enabled previously, you need to unlink and relink the skill using the Alexa App, or else Home Assistant will show the following error: "Token invalid and no refresh token available. Also, you need to restart your Home Assistant after each disabling/enabling the skill in Alexa." ### Alexa web-based app From c97be0dfec8ae4e4742e1ef050599d0cc8cdcf1b Mon Sep 17 00:00:00 2001 From: Max Rumpf Date: Wed, 31 Jul 2019 09:49:26 +0200 Subject: [PATCH 57/67] Fix developer API link in openwrt component (#10010) --- source/_components/openwrt.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/openwrt.markdown b/source/_components/openwrt.markdown index d23133df208..cb7890ae88d 100644 --- a/source/_components/openwrt.markdown +++ b/source/_components/openwrt.markdown @@ -34,7 +34,7 @@ There are _multiple_ ways of integrating an OpenWRT router for presence detectio ### Event-based device tracker -This can be achieved by running a simple shell script on the OpenWRT router which calls the appropriate Home Assistant service. An OpenWRT package which does this is listed above. As this method directly calls the [service API](/developers/rest_api.markdown#post-apiservicesltdomainltservice), no special configuration is necessary on the Home Assistant side, except for ensuring the device_tracker API is running, which is achieved by adding the following to your `configuration.yaml` file: +This can be achieved by running a simple shell script on the OpenWRT router which calls the appropriate Home Assistant service. An OpenWRT package which does this is listed above. As this method directly calls the [service API](https://developers.home-assistant.io/docs/en/external_api_rest.html#post-api-services-lt-domain-lt-service), no special configuration is necessary on the Home Assistant side, except for ensuring the device_tracker API is running, which is achieved by adding the following to your `configuration.yaml` file: ```yaml device_tracker: From 62c4d0d4bb01d164b137d7c51ebafb859e8ac74f Mon Sep 17 00:00:00 2001 From: Tony Brobston Date: Wed, 31 Jul 2019 03:04:11 -0500 Subject: [PATCH 58/67] Update trigger.markdown (#10008) When I was reading through the offset documentation I noticed what I think is a mistake in the comment. Could someone validate that this change is correct? Thank you. --- source/_docs/automation/trigger.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index cea62fc31c2..7b521c2e262 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -192,7 +192,7 @@ automation: platform: sun # Possible values: sunset, sunrise event: sunset - # Optional time offset. This example will trigger 45 minutes before sunrise. + # Optional time offset. This example will trigger 45 minutes before sunset. offset: '-00:45:00' ``` From b43d467d75b1ce7728297eaf17f75b1b70bf0b4a Mon Sep 17 00:00:00 2001 From: Alex Popoutsis <41379678+apop880@users.noreply.github.com> Date: Wed, 31 Jul 2019 03:04:51 -0500 Subject: [PATCH 59/67] Correct service call (#10013) Updating reference from `mqtt/mqtt_send` to use `mqtt.publish`. --- source/_docs/mqtt/testing.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/mqtt/testing.markdown b/source/_docs/mqtt/testing.markdown index 7db04673c45..f294ba83610 100644 --- a/source/_docs/mqtt/testing.markdown +++ b/source/_docs/mqtt/testing.markdown @@ -16,7 +16,7 @@ If you are using the embedded MQTT broker, the command looks a little different $ mosquitto_pub -V mqttv311 -u homeassistant -P -t "hello" -m world ``` -Another way to send MQTT messages by hand is to use the "Developer Tools" in the Frontend. Choose "Call Service" and then `mqtt/mqtt_send` under "Available Services". Enter something similar to the example below into the "Service Data" field. +Another way to send MQTT messages by hand is to use the "Developer Tools" in the Frontend. Choose "Call Service" and then `mqtt.publish` under "Available Services". Enter something similar to the example below into the "Service Data" field. ```json { From 18501783b305ae0b8e8b44aba3c2015547ef99b2 Mon Sep 17 00:00:00 2001 From: Matthew Dornquast Date: Wed, 31 Jul 2019 10:10:50 +0200 Subject: [PATCH 60/67] Update to reflect current capabilities (#10009) Features were added but documentation did not reflect this. Helpful for folks to know wind items and more are already done! --- source/_components/sensor.rfxtrx.markdown | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/source/_components/sensor.rfxtrx.markdown b/source/_components/sensor.rfxtrx.markdown index f350301312a..0d7dd72f8a4 100644 --- a/source/_components/sensor.rfxtrx.markdown +++ b/source/_components/sensor.rfxtrx.markdown @@ -54,17 +54,28 @@ sensor: Only these data_type are valid: -- *Temperature* +- *Temperature*, *Temperature2* - *Humidity* +- *Humidity status* - *Barometer* - *Wind direction* +- *Wind average speed* +- *Wind gust* - *Rain rate* -- *Energy usage* -- *Total usage* +- *Rain total* - *Sound* - *Sensor Status* - *Counter value* - *UV* +- *Forecast* +- *Forecast numeric* +- *Chill* +- *Energy usage* +- *Total usage* +- *Voltage* +- *Current* +- *Battery numeric* +- *Rssi numeric* Example configuration: From 6953727b9485129d818dc60018a95ad620719bbd Mon Sep 17 00:00:00 2001 From: James Date: Wed, 31 Jul 2019 09:11:59 +0100 Subject: [PATCH 61/67] Update binary_sensor.template.markdown (#10007) The example was corrected, but is now wrong, so I have made it wrong again, which is now correct --- 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 d57dd513cdf..3eff2ecfb53 100644 --- a/source/_components/binary_sensor.template.markdown +++ b/source/_components/binary_sensor.template.markdown @@ -85,7 +85,7 @@ Template Binary Sensor may get an `unknown` state during startup. This results in error messages in your log file until that platform has completed loading. If you use `is_state()` function in your template, you can avoid this situation. For example, you would replace -{% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %} +{% raw %}`{{ states.switch.source.state == 'on' }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an unknown result: {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %} From 09181270fb9debf04c54208e8c4f27769eab7496 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Wed, 31 Jul 2019 10:44:27 +0200 Subject: [PATCH 62/67] :hammer: Fix broken Github user links (#10015) --- source/_posts/2019-07-17-release-96.markdown | 4 ++-- source/developers/credits.markdown | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index 78eb93ed8a4..de8aeb95b01 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -67,7 +67,7 @@ Huge thanks to [@pvizeli] who drove the core implementation and to the following [@marvin-w]: https://github.com/marvin-w [@OnFreund]: https://github.com/OnFreund [@SukramJ]: https://github.com/SukramJ -[@teachingbirds]: https://github.com/teachingbirds +[@isabellaalstrom]: https://github.com/isabellaalstrom ## Advanced mode @@ -87,7 +87,7 @@ The [Home Assistant code repository on GitHub](https://github.com/home-assistant The Home Assistant Podcast has published [episode 53](https://hasspodcast.io/ha053/) to discuss all the ins and outs of this new release. -[@teachingbirds] has redone her Lovelace UI and it is looking fabulous! +[@isabellaalstrom] has redone her Lovelace UI and it is looking fabulous! diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown index 78ad137a384..45b545902d3 100644 --- a/source/developers/credits.markdown +++ b/source/developers/credits.markdown @@ -2113,7 +2113,7 @@ This page contains a list of people who have contributed in one way or another t 3 commits to open-zwave 3 commits to home-assistant.io ") -- [Collin Allen (@commandtab)](https://github.com/commandtab "1 total commits to the Home Assistant orga: +- [Collin Allen (@command-tab)](https://github.com/command-tab "1 total commits to the Home Assistant orga: 1 commit to home-assistant.io ") - [Comic Chang (@comicchang)](https://github.com/comicchang "1 total commits to the Home Assistant orga: @@ -2728,7 +2728,7 @@ This page contains a list of people who have contributed in one way or another t - [dennisaion (@dennisaion)](https://github.com/dennisaion "1 total commits to the Home Assistant orga: 1 commit to home-assistant.io ") -- [Denver P (@DrTexxOfficial)](https://github.com/DrTexxOfficial "1 total commits to the Home Assistant orga: +- [Denver P (@DrTexx)](https://github.com/DrTexx "1 total commits to the Home Assistant orga: 1 commit to home-assistant.io ") - [Department G33k (@department-g33k)](https://github.com/department-g33k "1 total commits to the Home Assistant orga: @@ -3076,7 +3076,7 @@ This page contains a list of people who have contributed in one way or another t 25 commits to home-assistant 6 commits to home-assistant.io ") -- [eltoro81 (@eltoro81)](https://github.com/eltoro81 "1 total commits to the Home Assistant orga: +- [mvjt (@mvjt)](https://github.com/mvjt "1 total commits to the Home Assistant orga: 1 commit to home-assistant.io ") - [Elvis (@mu3)](https://github.com/mu3 "1 total commits to the Home Assistant orga: @@ -3374,7 +3374,7 @@ This page contains a list of people who have contributed in one way or another t 2 commits to home-assistant.io 1 commit to home-assistant ") -- [fedor1210 (@fedor1210)](https://github.com/fedor1210 "3 total commits to the Home Assistant orga: +- [augustdipierro (@augustdipierro)](https://github.com/augustdipierro "3 total commits to the Home Assistant orga: 3 commits to home-assistant.io ") - [Felipe Cypriano (@fcy)](https://github.com/fcy "1 total commits to the Home Assistant orga: From 7e89f931c23111d4207c760dfe75c4e8877ae8c6 Mon Sep 17 00:00:00 2001 From: Fredrik Erlandsson Date: Wed, 31 Jul 2019 11:06:01 +0200 Subject: [PATCH 63/67] Fix quotes (#9974) * Fix quotes * fix citation * :pencil2: Tweak * :pencil2: Tweak --- source/_components/daikin.markdown | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/source/_components/daikin.markdown b/source/_components/daikin.markdown index 9f952d233d8..e6443de7c78 100644 --- a/source/_components/daikin.markdown +++ b/source/_components/daikin.markdown @@ -65,19 +65,20 @@ The `daikin` climate platform integrates Daikin air conditioning systems into Ho Current inside temperature is displayed.
- + Some models do not support setting of **fan speed** or **swing mode**. - +
-Preset mode **away** translates to Daikin's *Holiday Mode*:
-*Holiday mode* is used when you want to turn off your units when you leave you home for a longer time.
-
-When *Holiday mode* is enabled, the following action take place: -- All connected units are turned OFF. -- All schedule timers are disabled." +Preset mode **away** translates to Daikin's "Holiday Mode":
+
+_"Holiday mode" is used when you want to turn off your units when you leave you home for a longer time._
+
+_When "Holiday mode" is enabled, the following action take place:_ + - _All connected units are turned OFF._ + - _All schedule timers are disabled._
From fffad9d0f7b77f7c6a395e6b8758479623110c26 Mon Sep 17 00:00:00 2001 From: capstan1 Date: Wed, 31 Jul 2019 11:10:47 +0200 Subject: [PATCH 64/67] add details on usb-stick (#9971) * add details on usb-stick A question I asked myself and that got asked frequently in the forums is weather the usb stick used for configuration needs to stay within the device. So I just added one line to make this more precise. * :pencil2: Tweak --- source/getting-started/index.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 5787f6b8dbc..eb0af987d16 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -63,6 +63,7 @@ We will need a few things to get started with installing Home Assistant. The lat 1. Connect your Raspberry Pi to the power supply, so it turns on. 1. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant, which will take about 20 minutes. 1. Home Assistant will be available at [http://hassio.local:8123][local]. If you are running an older Windows or have stricter network configuration, you might need to access Home Assistant at [http://hassio:8123][host]. +1. If you have used a USB-stick for configuring the network, it can now be removed. [local]: http://hassio.local:8123 [host]: http://hassio:8123 From a5533dd669c6ce80564517d3c02156311509756b Mon Sep 17 00:00:00 2001 From: Max Thirouin Date: Wed, 31 Jul 2019 15:12:42 +0200 Subject: [PATCH 65/67] reporting_issues: markdown typo (#10017) My 2 cts :) --- source/help/reporting_issues.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown index e3a0f364437..73c204d3177 100644 --- a/source/help/reporting_issues.markdown +++ b/source/help/reporting_issues.markdown @@ -6,7 +6,7 @@ sidebar: false If you have an installation, a setup or a configuration issue please use our [Forum](https://community.home-assistant.io/) to get help. We have a big community which will help you if they can. -If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markddown](https://guides.github.com/features/mastering-markdown/). +If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://guides.github.com/features/mastering-markdown/). Use the command below to get the Home Assistant release you are running from a command-line. From 3fb1e31392d48127ac868d46ff2f0bcafe5ca477 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Wed, 31 Jul 2019 15:44:21 +0200 Subject: [PATCH 66/67] =?UTF-8?q?=F0=9F=94=A8=20Fix=20broken=20links=20(pa?= =?UTF-8?q?rt=204)=20(#10018)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- source/_components/aquostv.markdown | 2 +- source/_components/binary_sensor.rfxtrx.markdown | 2 +- source/_components/kodi.markdown | 2 -- source/_components/mystrom.markdown | 7 +++++-- source/_components/openhome.markdown | 2 +- source/_components/panasonic_bluray.markdown | 2 +- source/_components/panasonic_viera.markdown | 2 +- source/_components/tellstick.markdown | 15 ++++++++++----- source/_docs/ecosystem/hass-configurator.markdown | 2 +- ...test-bloomsky-splunk-and-garage-doors.markdown | 3 +-- ...z-wave-pep257-templated-service-calls.markdown | 2 +- ...a-bt-home-hub-5-and-local-file-camera.markdown | 2 +- ...-flash-briefing-updater-hacktoberfest.markdown | 7 +++---- .../2017-04-24-hardware-contest-2017.markdown | 10 +++++----- ...nt-on-raspberry-pi-zero-in-30-minutes.markdown | 2 +- .../_posts/2017-05-06-zigbee-opencv-dlib.markdown | 2 +- ...-20-automation-editor-zwave-panel-ocr.markdown | 4 ++-- source/_posts/2017-06-04-release-46.markdown | 2 +- source/_posts/2017-06-17-release-47.markdown | 2 +- source/_posts/2017-10-28-demo.markdown | 2 +- source/_posts/2018-02-26-release-64.markdown | 2 +- source/_posts/2018-08-29-release-77.markdown | 2 +- source/_posts/2018-10-12-release-80.markdown | 2 +- source/_posts/2018-10-29-release-81.markdown | 2 +- source/_posts/2019-01-09-release-85.markdown | 2 +- source/_posts/2019-02-06-release-87.markdown | 3 +-- source/help/index.markdown | 2 +- source/tos/index.markdown | 2 +- 28 files changed, 47 insertions(+), 44 deletions(-) diff --git a/source/_components/aquostv.markdown b/source/_components/aquostv.markdown index 179ed0a8ed3..df895237204 100644 --- a/source/_components/aquostv.markdown +++ b/source/_components/aquostv.markdown @@ -75,4 +75,4 @@ Currently known supported models: - LC-60EQ10U - LC-60SQ15U -If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.aquostv.markdown). +If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_components/aquostv.markdown). diff --git a/source/_components/binary_sensor.rfxtrx.markdown b/source/_components/binary_sensor.rfxtrx.markdown index 0cdb7344617..d8b463b0bd5 100644 --- a/source/_components/binary_sensor.rfxtrx.markdown +++ b/source/_components/binary_sensor.rfxtrx.markdown @@ -90,7 +90,7 @@ automatic_add:
-This integration and the [rfxtrx switch](/components/switch/rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`. +This integration and the [rfxtrx switch](/components/switch.rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`. Set `automatic_add` only when you have some devices to add to your installation, otherwise leave it to `false`.
diff --git a/source/_components/kodi.markdown b/source/_components/kodi.markdown index 9301bf6aa49..57142d81195 100644 --- a/source/_components/kodi.markdown +++ b/source/_components/kodi.markdown @@ -299,8 +299,6 @@ script: method: VideoLibrary.Scan ``` -For a more complex usage of the `kodi_call_method` service, with event triggering of Kodi API results, you can have a look at this [example](/cookbook/automation_kodi_dynamic_input_select/) - ## Notifications The `kodi` notifications platform allows you to send messages to your [Kodi](https://kodi.tv/) multimedia system from Home Assistant. diff --git a/source/_components/mystrom.markdown b/source/_components/mystrom.markdown index 984a127ae32..e6a642c0857 100644 --- a/source/_components/mystrom.markdown +++ b/source/_components/mystrom.markdown @@ -18,9 +18,12 @@ The `mystrom` light platform allows you to control your [myStrom](https://mystro There is currently support for the following device types within Home Assistant: -- [Binary Sensor](#binary-sensor) - [Light](#light) +- [Binary Sensor](#binary-sensor) + - [Setup of myStrom Buttons](#setup-of-mystrom-buttons) - [Switch](#switch) + - [Setup](#setup) + - [Get the current power consumption](#get-the-current-power-consumption) ## Light @@ -159,7 +162,7 @@ The `mystrom` switch platform allows you to control the state of your [myStrom]( Make sure that you have enabled the REST API under **Advanced** in the web frontend of the switch.

- +

To use your myStrom switch in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/openhome.markdown b/source/_components/openhome.markdown index d6c2183e6ab..0c47aceb67c 100644 --- a/source/_components/openhome.markdown +++ b/source/_components/openhome.markdown @@ -11,7 +11,7 @@ redirect_from: --- -The `openhome` platform allows you to connect an [Openhome Compliant Renderer](https://www.openhome.org) to Home Assistant such as a [Linn Products Ltd](https://www.linn.co.uk) HiFi streamer. It will allow you to control media playback, volume, source and see the current playing item. Openhome devices should be discovered by using the [the discovery component](/components/discovery/), their device names are taken from the name of the room configured on the device. +The `openhome` platform allows you to connect an [Openhome Compliant Renderer](http://openhome.org/) to Home Assistant such as a [Linn Products Ltd](https://www.linn.co.uk) HiFi streamer. It will allow you to control media playback, volume, source and see the current playing item. Openhome devices should be discovered by using the [the discovery component](/components/discovery/), their device names are taken from the name of the room configured on the device. ```yaml # Example configuration.yaml entry diff --git a/source/_components/panasonic_bluray.markdown b/source/_components/panasonic_bluray.markdown index 145c6e4443d..d813c8f0186 100644 --- a/source/_components/panasonic_bluray.markdown +++ b/source/_components/panasonic_bluray.markdown @@ -21,7 +21,7 @@ Currently known supported models: - DMP-BDT500 - DMP-BBT01 -If your model is not on the list, then give it a try, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/blob/current/source/_components/media_player.panasonic_bluray.markdown). +If your model is not on the list, then give it a try, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_components/panasonic_bluray.markdown). Example configuration: diff --git a/source/_components/panasonic_viera.markdown b/source/_components/panasonic_viera.markdown index b725f530f79..01cfb0474eb 100644 --- a/source/_components/panasonic_viera.markdown +++ b/source/_components/panasonic_viera.markdown @@ -29,7 +29,7 @@ Currently known supported models: - TX-42AS650 - TX55ASW654 -If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/_components/media_player.panasonic_viera.markdown). +If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_components/panasonic_viera.markdown). Some Panasonic Viera TVs allow Home Assistant to turn them on, if you specify the MAC address with `mac:`. diff --git a/source/_components/tellstick.markdown b/source/_components/tellstick.markdown index 392346be873..b77d76a2c4f 100644 --- a/source/_components/tellstick.markdown +++ b/source/_components/tellstick.markdown @@ -17,13 +17,16 @@ redirect_from: - /components/switch.tellstick/ --- -The `tellstick` integration integrates [TellStick](https://telldus.com/produkt/z-wave-gateway-tellstick-znet-lite-ver-2/) devices into Home Assistant. This integration allows users to add switches, lights, and sensors which are communicating with 433 MHz. There are a number of vendors (Capidi Elro, Intertechno, Nexa, Proove, Sartano, and Viking) who are selling products that work with TellStick. For more details, please check the TellStick [protocol list](http://developer.telldus.com/wiki/TellStick_conf). +The `tellstick` integration integrates [TellStick][tellstick-gateway] devices into Home Assistant. This integration allows users to add switches, lights, and sensors which are communicating with 433 MHz. There are a number of vendors (Capidi Elro, Intertechno, Nexa, Proove, Sartano, and Viking) who are selling products that work with TellStick. For more details, please check the TellStick [protocol list](http://developer.telldus.com/wiki/TellStick_conf). There is currently support for the following device types within Home Assistant: +- [Configuration](#configuration) - [Cover](#cover) - [Light](#light) - [Sensor](#sensor) +- [Examples](#examples) + - [Full configuration](#full-configuration) - [Switch](#switch) ## Configuration @@ -62,7 +65,7 @@ port: ## Cover -This `tellstick` cover platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) covers. +This `tellstick` cover platform allows you to control your [TellStick][tellstick-gateway] covers. To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file: @@ -74,7 +77,7 @@ cover: ## Light -This `tellstick` light platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) dimmers. +This `tellstick` light platform allows you to control your [TellStick][tellstick-gateway] dimmers. To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file: @@ -86,7 +89,7 @@ light: ## Sensor -The `tellstick` sensor platform allows you to get current meteorological data from a [TellStick](http://www.telldus.se/products/tellstick) device. +The `tellstick` sensor platform allows you to get current meteorological data from a [TellStick][tellstick-gateway] device. To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file: @@ -148,7 +151,7 @@ sensor: ## Switch -This `tellstick` switch platform allows you to control [TellStick](http://www.telldus.se/products/tellstick) devices. +This `tellstick` switch platform allows you to control [TellStick][tellstick-gateway] devices. To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file: @@ -157,3 +160,5 @@ To use your TellStick device, you first have to set up your [Tellstick hub](#con switch: - platform: tellstick ``` + +[tellstick-gateway]: https://telldus.com/produkt/z-wave-gateway-tellstick-znet-lite-ver-2/ diff --git a/source/_docs/ecosystem/hass-configurator.markdown b/source/_docs/ecosystem/hass-configurator.markdown index 9e2ac3f93c1..c8f39f7b751 100644 --- a/source/_docs/ecosystem/hass-configurator.markdown +++ b/source/_docs/ecosystem/hass-configurator.markdown @@ -108,7 +108,7 @@ Since the configurator script on its own is no service, you will have to take so `nohup sudo ./configurator.py &` 2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. 3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.supervisor) would be an example configuration you could use to control the configurator. -4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](/docs/hassbian/). +4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](/docs/installation/hassbian/). 5. A tool called [screen](http://ss64.com/bash/screen.html) (alternative to tmux). If it's not already installed on your system, you can do `sudo apt-get install screen` or `sudo yum install screen` to get it. When it's installed, start a screen session by executing `screen`. Then navigate to your Home Assistant directory and start the configurator like described above. Put the screen session into the background by pressing `CTRL+A` and then `CTRL+D`. It is now safe to disconnect from your SSH session. To resume the screen session, log in to your machine and execute `screen -r`. diff --git a/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown b/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown index 2ff92e9dbd9..aa48f049f2b 100644 --- a/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown +++ b/source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown @@ -22,7 +22,7 @@ Not only did we gain a lot of test coverage, we also attracted a lot of new deve - Core: Add service to restart Home Assistant ([@rmkraus]) - Core: Allow device to report as unavailable ([@MartinHjelmare]) - - Core: Allow overriding polling interval in platforms and [via config][polling-config] ([@balloob]) + - Core: Allow overriding polling interval in platforms and via config ([@balloob]) - Frontend: support for a [default view] have been added to replace the show all view ([@balloob]) - Component: Added [apcupsd] component ([@flyte]) - Component: Added component to log values to [Splunk] ([@miniconfig]) @@ -82,7 +82,6 @@ Not only did we gain a lot of test coverage, we also attracted a lot of new deve [@Danielhiversen]: https://github.com/Danielhiversen/ [@roqeer]: https://github.com/roqeer/ [@jaharkes]: https://github.com/jaharkes/ -[polling-config]: /cookbook/customize_polling_interval/ [default view]: /components/group/ [apcupsd]: /components/apcupsd/ [Splunk]: /components/splunk/ diff --git a/source/_posts/2016-03-12-z-wave-pep257-templated-service-calls.markdown b/source/_posts/2016-03-12-z-wave-pep257-templated-service-calls.markdown index 5ad89e1f608..e1b02be760d 100644 --- a/source/_posts/2016-03-12-z-wave-pep257-templated-service-calls.markdown +++ b/source/_posts/2016-03-12-z-wave-pep257-templated-service-calls.markdown @@ -49,7 +49,7 @@ automation: `media_content_type` and `media_content_id`, to match the corresponding media player state attributes. This change affects automations, scripts and scenes. -[services]: /topics/service_calls/#use-templates-to-decide-which-service-to-call +[services]: /docs/scripts/service-calls/#use-templates-to-decide-which-service-to-call [Hunter Douglas Powerview]: /components/scene.hunterdouglas_powerview/ [MQTT]: /components/lock.mqtt/ [OwnTracks]: /components/device_tracker.owntracks/ diff --git a/source/_posts/2016-06-18-pandora-bt-home-hub-5-and-local-file-camera.markdown b/source/_posts/2016-06-18-pandora-bt-home-hub-5-and-local-file-camera.markdown index d14b9106dc6..6993da37354 100644 --- a/source/_posts/2016-06-18-pandora-bt-home-hub-5-and-local-file-camera.markdown +++ b/source/_posts/2016-06-18-pandora-bt-home-hub-5-and-local-file-camera.markdown @@ -88,5 +88,5 @@ netatmo: [Swagger.yaml format]: https://github.com/home-assistant/home-assistant/blob/dev/docs/swagger.yaml [All-in-One installer]: /getting-started/installation-raspberry-pi-all-in-one/ [standalone Raspberry Pi installation guide]: /getting-started/installation-raspberry-pi/ -[Voltage sensor]: /components/sensor.bloomsky/ +[Voltage sensor]: /components/bloomsky/#sensor [SNMP]: /components/sensor.snmp/ diff --git a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown index 7105677f3b4..999be9dd496 100644 --- a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown +++ b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown @@ -183,7 +183,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one- - Notify: [Matrix] support added ([@mweinelt]) - Device tracker - nmap: Allow specifying multiple inputs for [nmap] ([@hcooper]) - Device Tracker - snmp: SNMPv3 now supported ([@T3m3z]) -- Notify: [Telstra] SMS now supported ([@nvella]) +- Notify: Telstra SMS now supported ([@nvella]) - Camera: [Verisure] now supported ([@turbokongen]) - Support added for [Neato] Connected Robot ([@jabesq]) - Media player: More options for [Yamaha] AVR ([@ehagan]) @@ -268,19 +268,18 @@ Thanks for reading all of the above, especially since this week was a pretty lon [Concord232]: /components/alarm_control_panel.concord232/ [HTTP]: /components/http/ [HaveIBeenPwned]: /components/sensor.haveibeenpwned/ -[Matrix]: //components/notify.matrix/ +[Matrix]: /components/matrix/#notifications [Neato]: /components/switch.neato/ [Pilight]: /components/sensor.pilight/ [Proximity]: /components/proximity/ [PyPi]: https://pypi.python.org/pypi [Synology]: /components/camera.synology/ -[Telstra]: /components/notify.telstra/ [UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier [Verisure]: /components/camera.verisure/ [WUnderground]: /components/sensor.wunderground/ [Yamaha]: /components/media_player.yamaha/ [Zoneminder]: /components/zoneminder/ -[emoncms]: //components/emoncms_history/ +[emoncms]: /components/emoncms_history/ [filtering]: /components/logbook/ [flash-briefing-docs]: /components/alexa/ [hacktoberfest-blog]: /blog/2016/10/02/hacktoberfest/ diff --git a/source/_posts/2017-04-24-hardware-contest-2017.markdown b/source/_posts/2017-04-24-hardware-contest-2017.markdown index 5b240ff64b3..71ba58bf7e8 100644 --- a/source/_posts/2017-04-24-hardware-contest-2017.markdown +++ b/source/_posts/2017-04-24-hardware-contest-2017.markdown @@ -11,10 +11,10 @@ og_image: /images/default-social.png We have four submissions for our [Hardware Contest 2017][hardware]. -- [Part of IoT-course](https://community.home-assistant.io/t/entry-for-hardware-contest-part-of-iot-course/14827) -- [Automating a nursing home!](https://community.home-assistant.io/t/entry-automating-a-nursing-home/14872) -- [Dedicated hardware for coding, testing, building, and contributing to Home Assistant](https://community.home-assistant.io/t/entry-dedicated-hardware-for-coding-testing-building-and-contributing-to-home-assistant/15515) -- [HassIO - Home Assistant hub for dummies](https://community.home-assistant.io/t/entry-hassio-home-assistant-hub-for-dummies/16037) +- Part of IoT-course +- Automating a nursing home! +- Dedicated hardware for coding, testing, building, and contributing to Home Assistant +- HassIO - Home Assistant hub for dummies The voting is now open. To keep things simple are we using the voting feature of the [forum]. Vote for your choices. @@ -22,6 +22,6 @@ End of the voting period: April, 30 2017 - 23.59 UTC [hardware]: /blog/2017/04/01/thomas-krenn-award/ [award]: https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/ -[forum]: https://community.home-assistant.io/c/contest-2017 +[forum]: https://community.home-assistant.io/t/hardware-contest-2017/42546 [twitter]: https://twitter.com/home_assistant diff --git a/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown b/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown index d563ee1725b..8f893167616 100644 --- a/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown +++ b/source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown @@ -71,5 +71,5 @@ Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspber To try it out, go to [http://hassbian:8123](http://hassbian:8123) or [http://hassbian.local:8123](http://hassbian.local:8123) if you're using Mac. -For further details about HASSbian, take a look at the [documentation](/docs/hassbian/). +For further details about HASSbian, take a look at the [documentation](/docs/installation/hassbian/). diff --git a/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown b/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown index 7bb892bd024..4482ebc21f5 100644 --- a/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown +++ b/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown @@ -459,7 +459,7 @@ influxdb: [notify.html5 docs]: /components/notify.html5/ [notify.joaoapps_join docs]: /components/notify.joaoapps_join/ [notify.mailgun docs]: /components/notify.mailgun/ -[notify.matrix docs]: /components/notify.matrix/ +[notify.matrix docs]: /components/matrix/#notifications [notify.smtp docs]: /components/notify.smtp/ [notify.telegram docs]: /components/notify.telegram/ [notify.webostv docs]: /components/notify.webostv/ diff --git a/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown b/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown index 2626c0041af..c7e0936af09 100644 --- a/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown +++ b/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown @@ -421,7 +421,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [vera docs]: /components/vera/ [websocket_api docs]: /components/websocket_api/ [zwave docs]: /components/zwave/ -[zwave.api docs]: /components/zwave.api/ +[zwave.api docs]: /components/zwave/ [forum]: https://community.home-assistant.io/ [issue]: https://github.com/home-assistant/home-assistant/issues [#7673]: https://github.com/home-assistant/home-assistant/pull/7673 @@ -433,5 +433,5 @@ Experiencing issues introduced by this release? Please report them in our [issue [device_tracker.ubus docs]: /components/device_tracker.ubus/ [hassio docs]: /components/hassio/ [media_player.volumio docs]: /components/media_player.volumio/ -[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/ +[telegram_bot.__init__ docs]: /components/telegram_bot/ [discord]: https://discord.gg/c5DvZ4e diff --git a/source/_posts/2017-06-04-release-46.markdown b/source/_posts/2017-06-04-release-46.markdown index ab31a184063..6574aaef863 100644 --- a/source/_posts/2017-06-04-release-46.markdown +++ b/source/_posts/2017-06-04-release-46.markdown @@ -372,7 +372,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [switch.broadlink docs]: /components/switch.broadlink/ [switch.rachio docs]: /components/switch.rachio/ [switch.rflink docs]: /components/switch.rflink/ -[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/ +[telegram_bot.__init__ docs]: /components/telegram_bot/ [telegram_bot.polling docs]: /components/telegram_bot.polling/ [telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/ [tellduslive docs]: /components/tellduslive/ diff --git a/source/_posts/2017-06-17-release-47.markdown b/source/_posts/2017-06-17-release-47.markdown index 8e37c33f34d..88e66b3c131 100644 --- a/source/_posts/2017-06-17-release-47.markdown +++ b/source/_posts/2017-06-17-release-47.markdown @@ -549,7 +549,7 @@ automation: [switch.raspihats docs]: /components/switch.raspihats/ [switch.rest docs]: /components/switch.rest/ [switch.template docs]: /components/switch.template/ -[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/ +[telegram_bot.__init__ docs]: /components/telegram_bot/ [telegram_bot.polling docs]: /components/telegram_bot.polling/ [telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/ [updater docs]: /components/updater/ diff --git a/source/_posts/2017-10-28-demo.markdown b/source/_posts/2017-10-28-demo.markdown index b91a1ad8faa..e6b4c9972b3 100644 --- a/source/_posts/2017-10-28-demo.markdown +++ b/source/_posts/2017-10-28-demo.markdown @@ -44,7 +44,7 @@ switch:

## `random` platforms -Till now the frontend is static. Nothing is changing over time. Starting with 0.57 we ship a [`random` binary sensor](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/_components/binary_sensor.random.markdown) platform in addition to the already available [`random` sensor](/components/sensor.random/). +Till now the frontend is static. Nothing is changing over time. Starting with 0.57 we ship a [`random` binary sensor](/components/random/#binary-sensor) platform in addition to the already available [`random` sensor](/components/sensor.random/). By adding those platform to your `configuration.yaml` file, your demo will become more interactive. diff --git a/source/_posts/2018-02-26-release-64.markdown b/source/_posts/2018-02-26-release-64.markdown index c47ca20519f..6460dba5321 100644 --- a/source/_posts/2018-02-26-release-64.markdown +++ b/source/_posts/2018-02-26-release-64.markdown @@ -549,7 +549,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [scene docs]: /components/scene/ [sensor.airvisual docs]: /components/sensor.airvisual/ [sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/ -[sensor.bloomsky docs]: /components/sensor.bloomsky/ +[sensor.bloomsky docs]: /components/bloomsky/#sensor [sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/ [sensor.buienradar docs]: /components/sensor.buienradar/ [sensor.deconz docs]: /components/sensor.deconz/ diff --git a/source/_posts/2018-08-29-release-77.markdown b/source/_posts/2018-08-29-release-77.markdown index d68a21390ed..c6b4c57c317 100644 --- a/source/_posts/2018-08-29-release-77.markdown +++ b/source/_posts/2018-08-29-release-77.markdown @@ -469,7 +469,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [sensor.deconz docs]: /components/sensor.deconz/ [sensor.geizhals docs]: /components/sensor.geizhals/ [sensor.glances docs]: /components/sensor.glances/ -[sensor.netatmo_public docs]: /components/sensor.netatmo_public/ +[sensor.netatmo_public docs]: /components/netatmo/#sensor [sensor.noaa_tides docs]: /components/sensor.noaa_tides/ [sensor.openuv docs]: /components/sensor.openuv/ [sensor.scrape docs]: /components/sensor.scrape/ diff --git a/source/_posts/2018-10-12-release-80.markdown b/source/_posts/2018-10-12-release-80.markdown index 863533111f7..68d358d6fc9 100644 --- a/source/_posts/2018-10-12-release-80.markdown +++ b/source/_posts/2018-10-12-release-80.markdown @@ -693,7 +693,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [sensor.miflora docs]: /components/sensor.miflora/ [sensor.mqtt docs]: /components/sensor.mqtt/ [sensor.mqtt_room docs]: /components/sensor.mqtt_room/ -[sensor.netatmo_public docs]: /components/sensor.netatmo_public/ +[sensor.netatmo_public docs]: /components/netatmo/#sensor [sensor.openweathermap docs]: /components/sensor.openweathermap/ [sensor.scrape docs]: /components/sensor.scrape/ [sensor.tibber docs]: /components/sensor.tibber/ diff --git a/source/_posts/2018-10-29-release-81.markdown b/source/_posts/2018-10-29-release-81.markdown index 7fb4f12994f..fd388fa081d 100644 --- a/source/_posts/2018-10-29-release-81.markdown +++ b/source/_posts/2018-10-29-release-81.markdown @@ -791,7 +791,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [route53 docs]: /components/route53/ [sabnzbd docs]: /components/sabnzbd/ [sensor.api_streams docs]: /components/sensor.api_streams/ -[sensor.bloomsky docs]: /components/sensor.bloomsky/ +[sensor.bloomsky docs]: /components/bloomsky/#sensor [sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/ [sensor.dnsip docs]: /components/sensor.dnsip/ [sensor.dsmr docs]: /components/sensor.dsmr/ diff --git a/source/_posts/2019-01-09-release-85.markdown b/source/_posts/2019-01-09-release-85.markdown index 7ec1ba92cd5..9306f47df1d 100644 --- a/source/_posts/2019-01-09-release-85.markdown +++ b/source/_posts/2019-01-09-release-85.markdown @@ -838,7 +838,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [sensor.dublin_bus_transport docs]: /components/sensor.dublin_bus_transport/ [sensor.eliqonline docs]: /components/sensor.eliqonline/ [sensor.entur_public_transport docs]: /components/sensor.entur_public_transport/ -[sensor.esphome docs]: /components/sensor.esphome/ +[sensor.esphome docs]: /components/esphome/ [sensor.fail2ban docs]: /components/sensor.fail2ban/ [sensor.filter docs]: /components/sensor.filter/ [sensor.flunearyou docs]: /components/sensor.flunearyou/ diff --git a/source/_posts/2019-02-06-release-87.markdown b/source/_posts/2019-02-06-release-87.markdown index 7d375ae2f7b..a3325c8ef47 100644 --- a/source/_posts/2019-02-06-release-87.markdown +++ b/source/_posts/2019-02-06-release-87.markdown @@ -37,7 +37,7 @@ If you prefer a podcast over release notes, check out [the Hass Podcast](https:/ - Utility meter ([@dgomes] - [#19718]) ([utility_meter docs]) (new-platform) - Add Co2signal sensor ([@danielsjf] - [#19204]) ([sensor.co2signal docs]) (new-platform) - Add nilu air_quality platform ([@hfurubotten] - [#19674]) ([air_pollutants docs]) (new-platform) -- Add Iliad Italy (Mobile Telephony Provider) Sensor ([@eliseomartelli] - [#19645]) ([sensor.iliad_italy docs]) (new-platform) +- Add Iliad Italy (Mobile Telephony Provider) Sensor ([@eliseomartelli] - [#19645]) (new-platform) - Add support for HomeKit motion sensor devices ([@Jc2k] - [#20555]) ([homekit_controller docs]) (new-platform) - Add an Integration sensor ([@dgomes] - [#19703]) ([sensor.integration docs]) (new-platform) - Add Synology SRM device tracker ([@aerialls] - [#20320]) ([device_tracker docs]) (new-platform) @@ -636,7 +636,6 @@ Experiencing issues introduced by this release? Please report them in our [issue [sensor.filter docs]: /components/sensor.filter/ [sensor.fritzbox docs]: /components/sensor.fritzbox/ [sensor.history_stats docs]: /components/sensor.history_stats/ -[sensor.iliad_italy docs]: /components/sensor.iliad_italy/ [sensor.imap docs]: /components/sensor.imap/ [sensor.influxdb docs]: /components/sensor.influxdb/ [sensor.integration docs]: /components/sensor.integration/ diff --git a/source/help/index.markdown b/source/help/index.markdown index ed710378460..918566b4ee2 100644 --- a/source/help/index.markdown +++ b/source/help/index.markdown @@ -37,7 +37,7 @@ Have you found an issue in your Home Assistant installation? Please report it. R - [Home Assistant - Erweiterungen (Platforms/Components)](https://github.com/home-assistant/home-assistant-assets/tree/master/german/2016-puzzle) at [Puzzle ITC](https://www.puzzle.ch/de/) - December 2016 - [Automating Your Life - Home Automation](http://slides.com/teagan42/life_automation#/) at Develop Denver 2016 - August - [Building Online Communities: Home Assistant](https://medium.com/@gitter/building-online-communities-home-assistant-8818dff671ad#.och4x4rhx) - July 2016 -- [Home Assistant Support 101 - Getting around in Home Assistant](https://www.youtube.com/watch?v=dRfk9JAlPJk) ([Slides](https://docs.google.com/presentation/d/1PUnOpeFZxNj4LEjaohGqH_1hOGQGuS5yRHD1ThHr6nk/edit?usp=sharing)) - June 2016 +- [Home Assistant Support 101 - Getting around in Home Assistant](https://www.youtube.com/watch?v=dRfk9JAlPJk) (Slides) - June 2016 - [Awaken your home: Python and the Internet of Things](https://www.youtube.com/watch?v=Cfasc9EgbMU&list=PLKsVm4cWHDQB9JBcD7_ZfNcvC6xx47QHT&index=1) at PyCon 2016 - June 2016 - [Automating your Home with Home Assistant](https://www.youtube.com/watch?v=4-6rTwKl6ww&list=PLKsVm4cWHDQB9JBcD7_ZfNcvC6xx47QHT&index=2) at OpenIoT 2016 - March 2016 diff --git a/source/tos/index.markdown b/source/tos/index.markdown index baa03330571..58554f567d2 100644 --- a/source/tos/index.markdown +++ b/source/tos/index.markdown @@ -88,7 +88,7 @@ In no event will Home Assistant, or its suppliers or licensors, be liable with r ## 16. General Representation and Warranty -You represent and warrant that (i) your use of the Website will be in strict accordance with the Home Assistant [Privacy Policy](/privacy), [Community Guidelines](/guidelines), with this Agreement and with all applicable laws and regulations (including without limitation any local laws or regulations in your country, state, city, or other governmental area, regarding online conduct and acceptable content, and including all applicable laws regarding the transmission of technical data exported from the country in which this website resides or the country in which you reside) and (ii) your use of the Website will not infringe or misappropriate the intellectual property rights of any third party. +You represent and warrant that (i) your use of the Website will be in strict accordance with the Home Assistant [Privacy Policy](/privacy), [Community Guidelines](https://community.home-assistant.io/t/how-to-help-us-help-you-or-how-to-ask-a-good-question/114371), with this Agreement and with all applicable laws and regulations (including without limitation any local laws or regulations in your country, state, city, or other governmental area, regarding online conduct and acceptable content, and including all applicable laws regarding the transmission of technical data exported from the country in which this website resides or the country in which you reside) and (ii) your use of the Website will not infringe or misappropriate the intellectual property rights of any third party. ## 17. Indemnification From f9004d324defb833ebc35933dc73e7e1ff1e4d2a Mon Sep 17 00:00:00 2001 From: Adam <22942687+SilvrrGIT@users.noreply.github.com> Date: Wed, 31 Jul 2019 09:54:40 -0500 Subject: [PATCH 67/67] Update Hass.io update image to reflect current view. (#10020) * Delete dashboard.png * Update screenshot to reflect current view --- .../images/hassio/screenshots/dashboard.png | Bin 9778 -> 12931 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/source/images/hassio/screenshots/dashboard.png b/source/images/hassio/screenshots/dashboard.png index ebe13598e367bda44baeea9e017e12afb2d833af..89d4d5a60fb30e9e8948ed1b2f2dfed811b92fff 100644 GIT binary patch literal 12931 zcma*O2T)Vr);AnL1Vs@ARJwo^L7Iqk5D`HXkdhEW?+|+Lpwgs+5UL;`H7B8m4pO8S zrGzRV9YT{5df-L>_ul6|^UgcpH?wE&-(GvQv-ZkbCo@Ud8&$>YSLv^UK%na{m7Z&W zK*RtDL^MH8azUZe{4H^@T(Xo?kpqEBV<=9INiX(9E*gr@Kt=tGs~6bg&1)@%^YioU z?Cjm$T|6FtbaZrhcsPqcBPrZFK0e;x-*0GWSYBQ}I6Ro2pWoWrVr6BWot+H`2(YMw z|NQxLb#?XZ>^v+iY;$unFfh=;!NJAFrKYB)v$JzrIhl~ZwX@xH#k*4Eb0&`_JcBT6(r5PLj2I=a5T zj+#FuCMK$=s4zA*77!4Kj*iyT)dPdU0@eG)#l@S)=T=r$(c>qQ^#}R+`7CAlip5ho zIk|np`FW@G($dn;y)&b(BNY{ugoFfe`=O$uVopv@Qc@Cj=gj@bQEF=HmtQ9HYJ)Q^%FF#2+ce-FOh^BOdxoU-@r>;u{QAJnmKS)WN(^Q_VAw z_SOjY%Z+EEf^{t?dq37GbX~=0Za)^GnU1MBmJ{Q@Lwuol4LA8aN+8^FR_H`(D_{J4 za zq&M?(>?!MB>pJ7D458!?4MG!rg!elRQ2Q~mZ0v!6W+V}}l3zTuVZtdxmx;`a9)kxA zoe@j0b>=3lb#1EM?v`a%VU|a^$h3=1Fk;aQf32tmyIL)=puTc5O?y75t8)-#aI3tf zd0X)t;OG{zgcX(HJ9}uL!YB1b-XOUKe)z@jE#*GZFC5K0_Fc&j%jQ+ZL|r$MD7#Dz zsyd@oDf+v4sd*;=MQR8ETrGj|Kw0|9tn{cLUxX&Cjw5C?_XXMNISAFG9DlZQDeE3@oK+}i z@f+dwSf1ciuJ8~xirF6m*e5#0wf5yde+2cABD3362GpS{`k0mcEbGfBnN+E35h}Wx z!}qeCL&K%x&noHC!g0@C=@l_M67gNIN-YVF6$GV5eUOCdP+x+N=3Z$vME(1ZvE^^` z8&vx_HYfae#})Mhc7N))*@E@`G8fv=syuE9Lf2Q3SA9h{w2NKcV#P?rvsx_-SIV3o zFZyQ(_x^|j2=~YD5Dye|5sdC7_c_}MU#Zo#FU$hM9`|8Lu$+=(RC(@Ws|9OF`^k6N z5tZ~~MK1y+ov{!RQFTmbnO!`1_rf~|ew%R(Cgkf;9!d=`3D!wP!66!-w_@sq&d$h6 zsoda>{yxDP`EqoGwqpd_RK6Nrz%GHw9_p&K)D*&)Zjad3DHdI3l3-PDq|wet=;CYr zQUfl(mgHp&l0SaK@Z+9UnXWq`+S}NWv70Dr+uw>7qab{rNl%AQ#8pJdg=>)UGbdka zdJR+K7j?P3aO2dB)^DY>J_|_8)ZtucuKFD&nQX80u!F=Z+fr(Fz7-m>lrDbV=Z|Id zmm9iZQHNow`wz|Wo}mQ;AF71uaAh5v4=lLKtg#yL^$A+b@s06nXQ%xlv_%j{@HMmJ zoxmSxtW@bx5>sPmOdU>g!CH19oBYc}A>dw+K%e>x3D48a`XUbhG%+xwr@v-i^hnrE zVe3PiQQ0k-{_&^zXA5qeGrA+rNJut5JP>t5J)hjuO<5WPi8lLk`}qFABn`?Y38f8FelFCVKu zA#-`1obKK3D_yMlnWn)~ZWDzQsw)W1OKShrzu*|kwr(ttK6O-Pq*;yhG1t~%&r?Km zrp`*{QD_6TID2suM)>+9*5*-Lj+C+rBXiB5UUrv77dHFJcl0H+W*3+~>$#@Yw6oGv zu%)|a-n<8Kst{i5b?wuk?8jy+`9w?#xk=Tjqbc>*Ecpyw5k(5#iF$oLnw#?+MHbSp z=dm`uI}cXOn+5xlt#=ky>Gd%SJarAp_Cuw^V%Z{~B1kxq6?oM1B=E8E2e`2>zk$f* zKr0#&8jOy;Namcn{OFGgYXy(7*V&h)X1dDkGIa5eP9&ml2-5eoAq*MndttCd0D=`N$Jkf-KMO3GX|DCKSzBS3MR~!LS&{oO?E&f`VuLIf;AfD*KJsi)5z=So zFY^@oCHd-$7s5n3K2Zq`O^T497S-NOES@e`hFYe6nU2Ie(J)y4N&6@sAIMqkmX3KE zaM|biVFvaGOAOIi2BMWYfvqYK7;T_f$?2)nrr?WdpeSg&Gfi6X#e*n!!k6V9<-rDS ziql!}&o#8%z=5MZIVJ8<6hofT;A}@#bW9T=A3pvWPB5ZYc z-CIhZJ59xiHqcGdv2}$OPkV%gZGsNne+usZ6a1$F|Ev7truMQVm@hLHwSWariu_5M zrY?&8MSm_Lu7*K=uj1~iY5(F$R?+@mSX*05q1|j-TkB2qw{29-!jH%=*sg-~NDV`Q z^?%p z0t(d#@y`I26%cNK4U=*d%yLL4j3eDL>nE~7WNi$ z6i}^LIu{YfVIE;}t~!ab*{q6fLV8W@VPM6{dChV9-n?gXLxZ$4evg{El2qHW2V3IK z-tx5#>y&RFdHQ*OZPLjtw@q9;7!Y2;{jw;cv>3o9OgiG-)(&RI>tWwOFh1*Reelb4Ktk4@!2UGI6Np{|J3I`k8MB=wnS)O zU;RBG1@st?bbcS1w4Sxnnf@6!u_oK~{`a$qg(?5aU7Xj^>Fb)G*dxVIjd^TD@G#a= zfHG%)Nx9Ht(MIos_NW*6Q=ulqfE}w}RkARKi*Pt%2pSXOR!SROsP(SsVX?6|O0Qfp zf!uu}0`|sk%f#kT`u@_U>EMdn7bnjji3T#<&jv=XTRWJ>R5_mi`fZ3>S6r2>@ja^s zY(fY7+l}QXrc8=7$o5xSr(pwir8atwh-^^%>iJk*>r6%5L(nhkOje;FqMFN$+)bIt zBDE(4??lGj*$vCfZqX{QY*wA57HH&dVkWVh(^D(~yX{ZzX4bgAa((Re1u0?_!-b1k z7X9vStG`Wt5@F+4KdqWei{7jU(!ThKoHgm6IDY8R|ud#|iALOciLkG*lOk4nKmbcrDflj_NS*ycu z?K&`NK}z%}y=&EziyPDs7h(N%^Ji{1wH2O!y(`~g;@WcpE!NT5>i_w_5O)={^OXyLnc*K zHnI&WXXg_RATZx_TdoDpt-bE)#j=LS9xN{h_)Ew-1W-Z5v4Bla*#M4G*YE5!8r`ia z!7tgrT?Y2~c~zHDdt9>*!jvyX%aG=dSZwzXN7;U^m=Jk9>hx*g4w~~|fNFI!8-e=1 z{JH4-+R)pWQI=v)t;J^iWI3q9+Y&NkR_?Gld=YSZTM@FcHz360EfaM~zUui;_cg*6 zH{y?QW1BpHc+*Ghf($(`ht3*K%6<#=d@U2JkLfP-zp@quQSo6U%-svySrJ|Ky1fKg zQUK0WMKxv^hZyaEqzGzznuEs!wO|q?re~51b@AoS;JdcZt}mvhF-BnsEgLixaL#PJ zNX;urPE76c_K(&^-y>3#D2&N7_5STgcF7cjM4>Z2b>Yk*IdFVDE^;%dc}4nKkA0UNis*H562Cy(!=&UR&gA0XWD#WN4Dd@tQB z0juK80?va>`z*fpBL{z63%fb^z-B1>2MMM(Qof-h+Zj_(OerPN6I)TF0BJoMd{b@{ z$xTR1OJm9D@H-1(=&RI_$@Q77Vyp3MLE4VxM`|HqR$v-WijHBm4k1r#7KFDs+Nf=E z>zo`7`>LZ``<4_v9R^kc?Vs<%S$5tQS6tO(MMjY*w;9K;rND<0Z>CqlFVEE@EJ;!{ z8?)s^Za9;Ect5e1aDL+Anh3wEoqL&G*)Hv}+}*4$=BP(Maxb28{JF1DRp#&RdCaS* z#a&33A7h1rmwT=eZRJIUVu$PaSh;zi!}ahRU0su3O~C5McKm~r5%A;+-Cal#SpojK z6S92OCUp`K2_yj`yb8mtfHw9dM&IvVa~Q+U@BkrmAC!G{W}yS@|6! z5xveve?f>s?Nzb>-5Ku-p-IT+-KWPxH)PL#Q$w%cDH~tD(S|hB*{bsYtq6D|6sf%wp_+^1#Jc1GI(agxX!htAEKGNQb zpmHNRp`*{UbQ+2BWBl5odc7|yv$N<4nxs<>%iYnMEc@WZb?@uvobFLMzzQGoc^}oiJw8_A-CM`w$Fp+N>{Iw4*;kuEZilO>!Pyr@^>8pU+#vAyUG)#cGA9klRHX> zo_3~7+1L{!1o&0(dzd)_QtT*n6&{nbO+Dxqv*S(U!Xd)pNVO>RoVi_XXmTsrw|J7DPKE~6fk_eowZ7oeco+v!e6+Waz?_NQ8t0)^kxpn}Gi-}j z_#mn2_0|r10~{8scQ^9hwbb8Fab-oZTq+}0!jA--;lUlRMy~0X5wqv4|F&vZY7@Q# zSsO6?DJ2z+kKBr-?l}@B+AFZ6blqNXcf9LC-X(X{nKb1!XSh^1)9>jU*r873;Oxqp zfgJO7@;E&uV{^~i64z7m_ByGL@^0iY;R?V3YthI%su;r-o^LYtm_g!>*)IVRQbgQM zrm#LE*Wo2) zvpS@_xOdqoTB4Ol)06V4HG4F$nj&WnuB5 zo-({AlA;tdET)%#1|7QM%E|dSCX}5S(Y$E7wf;6i6so@f$`KzyE?%*&MYPqE!)m0| zZnjX)BD8513!@z>IoQ-VF0)gjA1N}$9+zQB35d8%tdE)71F{dOJc9Hy8lkS2Cm^&q zk6AAftGozlht&|tJt^vYDf1zYSL_p}Q?Uy_mG8$RUuIMs_Sk<|bH0sccW3e-_h*Rh z-MOiv>>oXRR5IuSu&H`9@7N@5alDI#>eQJY5NpHhrwPhsW*EK~f5^sRdrWjPU{NW(mh3M?&YUCmB_}v>>sD#hs`w!LN_V2i-9x#p0OFaFV#T{!s^s4wl zBZn`Ie5-%=&;++3Q$ecF>f-ah?yiWe-z?975bL&Xr4ozaQIcPH(AbYZb?yJ2FKX4F z%5)tq0|gvwR}$rUr@KJ*E?c)@e!n5J*@#J9w+S-CN(26xY%=TGcRq8|XqEJzKZP!o z88Rg~nBp^;)~Bk8VT5Tk&ms?dO=4j(b1;R}JcV?o!od?ndYpH1eN@+IMWdOGA|Nvcf*pwprY zgd;C|RNud>5dMW#FMwgDkamjt@@R9isYKCvQiJ3hWnJr55F-)IB`6a)=>pAFOcZys zh9ih5>Y3A1Dgc`@eI9&zV&^XZRBCSEY-P{Svi|{_R%B46r>rf zn`>=zMXj4g0g|opY9we|F`LEIrGlfWXO8cTJ>_f-LNt#%DWkVD-`f`Z{EPjwjOq$M zfUJC=o-@$>!1NYYBZaAh$1dw5C-@)x>iHJzJgC9j9>Ur>w{0@-iVp|~?Jo#L4sjfR&hB;h+ZI$s?V5<07uFmFr&~cJHQ_Kd5CbdhSUM{~0>sx>_##?zYhyhA7G;mDpcmvp>Ah+ki5>-TR){l>kwuV$cSpJ^5ZR6w|{O2 za0x@ecJU<=e5T&R$cKHYRrGcVe4~j;(5OD0beRW2(iV|CE#|q2`qVFW!P0|vx-8Gx z!S$rT)(||adD*R2nC#cBT&fE<9Z*2z%U+^N*FuiZeaE`v0I zA}-onZdz&9pHagfMU3Unlzcg#QZo%)xYUf3)Gw!JV0`|>a;YaCm6-BPN zUfZ3#&8!(UFd!2k%cI+ctTxk>XtWd0xWTtTg@QvGCvOY?ls5ab8se{RB-JJ zZ&6n$9D$|IUdto35tTbTNY7U~xfglGq(iF^;BE13f|J0?^u<-IbQvhC44Z~}&}n{q z#3|`zKVW57hwlEz%!|O(f2{0PhqVWa014`~`_}fr5Erdd1O|KRuAYQ|m2pPuVtd%1 zj1OSY?y`B|RSDqQ>yVi^Y|It?llYso1K-IJo<69^%AF=0LpgmUrdReTWZ9-;ewo0Z zy!xhbGP;!q)gNGLPqQ1~s0L#Z0 zni)pViVrs8i&n-%Sig#eLocU)B89{ubo;pCr>$^F)t~6h13O%4I$r|orJ{-qQ}q+q zfKFv}$ja95M1{hS{?Ht1wPaZ5ghm>$CyGvzP-j4~1&krZ%D%}o2T66;^soBg;xf_v zq{($xJFdzID^3?KRuv@X^4x_hHlE)FQL-Wd&u`rw2-U4J>nK$=n-w%yCDEt$r<`O=+9?C z$AO`P-1P1EcYOX8v5TPnJ8tBE@P7sKzmEPB)&Bwi1RT|Z^QoeLmUtayqSsdaZ{2@2 z{Z;&rzJKWdmiXTW{})@aty{6P(fL+pS!wCOy!Ohot=G2oTdt}b44(Fj!41KL^<6&1 zR;v3%*2(&Az(L!_&=Ysd)F%rb(qCt9C^M`Kv^5kx9uIo5b;DeiAzc%jHAD$9#yCGY zb)K%vq7be6raI)W#UuN8!$eGK%a=JLyzW})od~qM%#0o+y1LZG|FcgL7~8)2x=w71 zaQMvjfX74CfsA&*^>fpHbhNkc?(y%)8RMzdAJ$|*32ZiSMt!lr(Q%w%Cn_nuU-ZGY z)`tn7J)sq5(FWa)m0={DU6Nt{@cc%R{kme}>=%Kk%=#{-ca8IE@-ia%?Dmm!RVdhj19xI({J za1jap_~BiT`!B>gkjZi~5{6UN*bOhvEqjYbWxG%Pssg-2N4UnaT95IQi(>0%iSD*W z!!O)crtYB-xfSk&N4k8Su5;F1^w0^g)gzpy%QSARF1D@vA|_r-4)Je#`v%eOVtqPr z-VWz+PIx^Pn+^Ap<0_c++~>)OgYMir4)4tULHT7uj5@;=*5TUpXQnfVn@p#fY zF5Z;k&iO(|$WR(4Xy`W4jGKYGHH;qZeDUzdRVuH6e2u;ke$VPJ+Pdp8WysVzxal78 zgvwz~{Badd5_MayjnnHc73FInpNZ9@kOoS}dm}^^9ay}zB$Qxtk>WpZuBF%m`^UIo zkhfZ3u1{mF(}};fDEt@CyFbKBf7s%*%jko!mO9s4a5&WM%S3ne9v#UML9{JJ z^vD%_-&AY)2EJjv1_0%_La;~CXl%Yq12y2)l3Du*@Ru z%b74}n1WXaxqeK=I{JlBsSz!G|siZZ(uJx37;}TJ4=bg2DEf%GB@wG5~`iSgT_x;GJCd%N`Kq zn!_DbV>lN2Sw+*(3LDO!Od@56`2NmxDx^8pyxy?nm>v?rk9@e{#ICgquKB)a)Hp$? zIzsN&{V;HaULyv+SJGpWX~QOuI4F$@F&3jly-T;&KpA9^j+%}4Haehp*d$or<9x*; zi&quja164QjWBN$Keu+c_WsE#n8P250|o)gx~wyt^OA{cL2n&#{uG8 zk_M5>jaC9x-IBZPJ?6(P^I)H|hcdYD}W zA4veoNX5Sr7JR9!8@h;07nqPN;W5+ekAKDa<1Udg0&p*~V%qLQb;~6IUe2qRADLc| zDy_Dfkt6f)3_WjH8;|ye-oW%b>=SLm!|};TaM8qgwi84g_yjf(yO{cUED`11I*X{C zmW#>x@4+8hPyhegmUmP9i|-H1ciJBFfSUrpP#OGpEb*2lJU3Py(5a_NzIHfAh}s*w z@3>z}b93c0Un(oFeV)pSynMLpNuTx!JBr-QZt{A4mi=^_AJv!%i^s;LpjnQMBr}pw z-R`L`zl7ej#N(0d2?2w#wKYsPgoEZnBSPcCj)%7WRAVu1^Bu`NF&}ot8i&LIGNiiL ziKyRj9m7oj6~b60MX4DrtIK@Ej^loTFr<*_k#=F1j$a^dDkZd1Uge?SY9CFu)Jk){ zLI;Tw`UDD7BSF?bN^`w^<5fRg6BCZLt-W{r`dv&;$z*{Atyg)Gl%A-5@&!c1;=)T<$+Gds}w6l&1=Qs0cSP-Hm=Y4=Y zcqgG^cyO|P`l?%g*JdvqKUQ3w5fkeC{adQ`g%d7 zqsnH`46$%9Une75F7XB()p4*&B3bV3s$4_k4jJ^k{Zz+pGM2=wZKG}elOx3I$PIOd z{-68|xCP*9t%-*O68c5y>GbX}AN+Y~5Yvk{c7|?C_^J zu5a5e2E14eeJ8*3D$PZqj7!E{4HKtK3E9LcrN$=|v-9QNUU~-2xNjZHUuhSD;Q0=G zod?i1`ddrZj+B5R;p`pogw$SP!_Jgv;far7RqD*AA-_iB3d z&tYfz0Co58s${uOGiJkJ6&mLrCOG-9^uh}OIQ<7n<$oaN&o}i_xmTr2Emnt)uqa}@Jsx}140w}vHsh*P$@~vF9 zv)dePAbPmwa6@Mb+?5sB6N_P$uUeW@v&4?umqMyUn%$9Gp?9ER_D?^2a`@)GFh$kE z_YM}f!IdFL3b0!aOr5BpK;j{v1;cU>tx}Kd5FZlQMW@ii?{CoUf3l*S?rm7laH!_Y zwpi!laZaQuTlZFn29HUfAyt335s)J^u5cQS?( zEo#yS$8Qh;Cp=!dqSw@%AHJ&?(SV4_eg^9fNPuvFdyz zl0QmTXj=B!yW&Z*IIndFytQKIniHl-X9>vMqJ~JP-tjEV8+z%0X1#PX$4e3dIM4wP zO@lfc0h8;obaMBJWP2SeKK5JUA7i_HF~OfcWFq+xl*Rg!BUf@%0e#BSi{K?_s1q?m5{eSzwG1DyQ1;kRez|^WJA^6N?PF3 zF=AmNkxfe)LUl`&a;=9gZ@0I@W z9_w!Sla){2BCcd8NFHLjA<6lXWSEF&3lA+bUulspy~{wW=d{Ry_*+PR!AZ5ZUhuK; z!Fxgr>>yAW(A1i2!$RC<#^GpKZ>XWPxHy5x?&GD2}=p(o78AsFj`Y`0kPR9D2-3$>fl_VF#%2R6p{k&W+%+lee=zPTyJ)=rx~<& znppvJ%FL{=n@Pm1@k?YPz*6&u0GTK=qBumNli^O6a}65jVWeJPX|*%c`B)(Spa9a6b2WO(%OR|ir=2R*@d zv%#{ndHQPB{oGY85$6ecVeb~69-^Eu$LcELn^@W>d#I~l8Uh(X`w+HU5503dn|LO5 z<<`vJ`4#JPlV=gRlzb;T`&kXIg>LETQj~qWLI}JS@T{ITSH9#fB^7fjsy_k%5XJGN zl2_l+-Fk2Lyh0u#$!riiQL*p)4f%;7mZ?rqHw*rP0`a!sw3cZTGL7&u9>vPIdHs3!P4H%|Nc2M*aTt2o$sSgYVRty6SKJ6&hhx=H4N83FkyV&U8RgW+$(i z9%e(HN9*KTLMGQ&bU@faS6`;EaN`p!v|AXMDt~(=*SQ0?sRPmtH8Dbbd(b-&u#qn3 zko}bAt(%jRJDrC6Sr7V+ff8;VYc^R+KMoE!NE+8*CBA!0B2M#fRzFpV>$C@}tJvI1UPb5xR>kf*ZH&x;0kmyRKSSkG^t{FpBBPWNO& zsgjVKUbU;Su-%AWcz5t_M|F1dGpFVZaqhG3kB^JsDW+`C)5{zssGis~U%R}Ff4935 zx>X>2jW0kb%%vSoef*-uWwX}NAQCvi2|OfT#Aj0#q;{6`_$c3Y%mT}=R1jWv&fVL? zq%mmwQ6lfSddVcR+tD8FG@U&4%IE$q^m%3}KhNx?379w8lPpMc6-C=?wAXSw%{{>O zU3#m~=tRFwe>JAvHuioTohKb2j@K?JD7u3}7AY?S8Mp@=9VWoD{5BXp%@2oY?6la( zn}TSI`R`)Vzh&M`KQObTiL&#YD3}v2g;`+ke@ZVt*ZvKGnU zI+knsGG~LN9&q)Bd*!q|s#x_#A7!dK?0v^gy5v9HvFGV z%vt90!)j_o)1v3bCRys_eR?V`%)FZU>a9pS`pWMdUKIy>`sH2BdHE;UanUay3yg9U zzKqokW`cn7ecRocIC~O1Y#jzR!QZ(b1?7N*fv;Yi{8|4l4?g^}{@vzQPy^q1N|jN! z{#i7r{(CF;hm17CywWK~?DLl?>j3E$oKSOsGPm61ke5>@7ll=Uk)Tr73rF*UAmRJC zu#`?7bF}+lsu6}(u|HJRNkWE^*FHsRE&Yi(+JCT-aF4!e*yc=0oueL+>=kx}*Bosy z*!Z2taH#C?C~VGEsv}asDh}KYBjkuQ@vyK*-c~>e);?Ne>Yku`dGZ8^b&t=66`(x0 fZ7lC^u+-F^j*@His9pSv1oTot^?A`Vqxb&@Ua|5U literal 9778 zcmbVycT`hPyDmjQ0mYwEq=`zEP((nKDk{B1S|D^Jp@k+T(yNG|hy(&km0q%Gq4$8G z1O%i7DWTVdCcVn#_no`ecfY&Nx#v4~|1oVn^RC%@zwf9P|_v6qhyB zpXpOjPyrMalqVOd&s%u?E<2oO7wnaFlqo36V;N3tXwK`Dp89G}C`x*{R?aIH&$SIz zj*gDHyMGiH7n4?278Vxv4-TlQsn5>Ns0(+tx3@h#J<$mXJUl$FU%xgrH68u+OHxuY zD=SM?RTYQB)zs9)j~rUz4<+mO@#K@KGWnj!7jtFhue~OY$Fz=j+^>vW|4Kn|i$dd> zvZ2q|YFboc%EPNF9Re!1uD*jZBLAF8s_94dtb0v-M$Rq}e|)wUp?;90rr}O?Oo@xf zZCZr^}VEVUXM0Nx)J>zM_M~vmMxO21=SG6H77^D@ca7xA4 zw)S0@v8Dmlxo*`p){`H)zPPOnvL-Wpym(~BXLZoY_T!Hspc zF@6)>CkXNhHEeo3iR8F>6T`SXp1I38BpRRc8G+p+A_aT|gt~+bmyE$bTkAhou{f&> zk=OVxJ9`P7j`~r3Nv@J~>n=@Y!P(-+Qp6HD>qr?Igg=p|bFj6vz+P3EQ6{8y_$VsR zqU&{UQ_mZs_NFs7nTYTxJXP-fv(O)+R19SUfHZ}#`$!aukiLbV4tlgCmt@9~&Ur!B z3@l7em0as7k;ggUem+|KxOxifL)DEay|p--;wRq&2B+`BS@tG=G1W9|#bi@X=~p22 z`SkS*l1n9irifn0lQ3Ek32VlgQTVA-nZhrJ$6&SbYuNBj8Cfq;vv0HYX@ELmKW?{N zmAc@XH+EpyI3-J}%C10*aQpXQ0rWO`3IpB8B71Q*++UoQN(lNTUPG-OlAqhtgL$B5 zrw+JgM)fhIJKQUS&t*gac*PBrc<(DzO1&M{E5(puVb+1X(0Dqs_2}9PyC=7ZKmdL$ zxo-WFQ*lGHu5^>w1KjW{)UH)5t-0E1jax{gmv`+~&0C;@#96o6 z+LfYkU^*=npukd5Kq+A~|D(JWbnbNj{eydoqS#!U&@j4$tMO#A=#jWZae!RES|VWl zyCF;tH^1L4%zIKYee>CrE8>pr2{3)L{Ub|bDR2!-#Rm!j)FC0~z-=+muwjpfa)V2#ZI zN~0qF537!r9_p$>{LgIL+aGpFtd9luz=~_P4Cs1Wz=Y`SsnO)Rh(DpgiY(&cW$op; zmr^R^LKeT&J3|zuDL}9=1|au21CRQG$eyPy@R+u0M?qfl%hWJs?Qg@5ZQP6M1ckqr zG8nHq_6GBOTi*`8g=kLWA9a+!SzPk{mse$uyMkBD zA0*n2Aoyg~mj(%Nl9{SwVYFSMw1}pWakYz0@3!|$&VZerp2ZRC4XYIkH;A5zZ+Iod zdtG-Z@{Sc84$bV!`V99@`BH;bt%G{^mcZaH5bm^+rR_t(_^&@XtozLPFtao@LP_sJ zJ;XHy5l=Qu{O>1Y;f{~vJN8!n@2yE2BUud^e@BFxE9PgZJVi;1^=NOa>S75)MNoK5 z0^<2MW4v&M!J>r%515EQ8F^5)B#Iio5%(R?lNvYSxR|C-ne6FpjlH9`bpJ6ZUBYI} zIB97Q)w`%@lV+p3s*MfzsCI!D`*Oei1*i=Qd@>x)tw=L1N3jhETbOrpboj~Z-FBC{ zp6~v+=SUY%nuxA565UbFlj_P5zF+>U(=`6kA@+u!xaEC`PgP2vAi}u@4P)KH-TDUf z_RQ;I_v;iW3XF6mxF4p}V0Gtw_{?-l7UvG%X6+WEq?zBLB1T?}v}XP8heCAi4}Trj zk(pJ35;4>PdS&lfIs>s{QK_yEZdW1lAysa(>NnVuX0mA$id*$Oulk30_`RakN)(sWS`XQ3}=P^M*Jlb>()>9x`a(9DhsyXfl z!dz4prpVg{hgaotl7v<5BK-5ng)3!%zd0o7y=GqJ*rx60`ydONxt-1_#)wxG~;QS_~CYI zY_ZBKnz?`v$RL4c+G4S;kZ%6_z3+yU(_Vp$RT;Lntngz8ymsPn!H_Mt#j%U| zb64XRMRc(W;??aa*JlfRcR&>*7K0v5c;U%Z?A_OE?k*3KIwpW9=ZQ|I8s)loCWcX; zlp?a24*SO@T=*=6x<^8##+&Z%k`jvl&`;djtj9YAxQ`ej6e2UpJI7B%X`E(V5 zzUc^TzhzWUQfyMU2~L&Y?2&`8bfZ$HirS3U1HdgV$^W7%Yt}mQM9YT?Q3ySc@ftk{Ip_D$!|H{Kuozbwr zF(1#>;|`P(#X|9)()Brs{{se%1I}5T0>$ze!UuYcr8;Nzk1Tll^WNvI4paG?>?zKz z{R4KyZ76dlIku|EiCeDH#tHFi5wLmE=vfm&xB7TcZhc~T_guqEx zVm}PneOB?aoeK%};mTc)GQQk06D6XZn<17+GXlPO;xL)69oXo$x;>W|gX(g%Guk>D z`EIApbfF4-dHm$*L0uYWzGiNajR>#}4vxc=)+kax=>>Nm)5S&{fbbmSOZ1xPDVt*> zfoFjjV0DgYJ|xr4;nAUJ=G0S{w$gm>Mj%}$+(O9AT2U8MkF_Q6QBS-RBxTNw?X{T_; zzL}wD4A$hevQfE6FNY+k^ja%cNNO!xneJBT4VAj+akcwDR%>87tUq7q%sr=1^K94@kQubo%CQK^ zP%Exfa3Ur#UeW1YHh3})9{@|b6%DpYl`Q^LD9HN4sM{#;zFOMBi*<}weF^#)o45CL zdyZ4(^H?3y=8;089$nTBwhKNe^Ul0Fp*hmU)|lN0`IXPjL9mW)=Fj)ZItQ6(kX}N5 z+3TxMroW#BuM`Vky4tQFS!WBbkFPKme0lF8Wy;e__R`0{j})abkfzlm6&f(-UHhf0 z`jAKYc7EUAV9O_Sm#ku=Eg@-fYM8#XCB!Fe(5zaCnU%xB)8|^Y2Qz3xTAvC_?c7Wk ziH*b1HAh#?RKK)#IR4OHZJF~$TSGC z8A=Z74>=;Jq^o}l_~gz>1)1CPV>CH6j2E7_=hjc!HwYlTWAIRx!ixo|e25Cm`ge~( zOwM`v3U|N-uO4)Dc_PW^=6!vx%>_Yc@WGB5dl^yz;j!j8b|pPB?|owLP-uptu9$5ImKR`@R{E8t71hx%we@o0Eh+85 zg0`n;t4l{b>7=a(`(@{Kn2#uRtyEsE7N;YyPRLa!1di+={<8EKN-BJq8KI(_-R39T zU|Jo<`69TkPs<#=8fD1UFLH75@+&MBJ5XM1kZs{CWc42F zm}UlxiJ#vhp@3$=_X80=kAKJ6p?Ggn6-!w7`np)A)4KVd?aY>;ax@u`fDY;$!gJU!RRD97 zy8!X2!1R13@y~7fO-P@%-es-VIr*%8= z(Hw^Z9ubm-^~aIeE-nm!V81$|*|UHh$o*iFb$>{?n|yagST{bo)!>dtg~dVwPxhzY zaq?voT)yh=D?UI0# zvl!#UWRizcFKp!^)2~bwM4A&+Kbtn3I}6yZk-~`8h%30KD92?2g&rTaYw*rJ+%iubCypdShA$MwVD?gh!t2oZ@_)E5 z-IP@59)^Cm({D`*ByJX@D!3g0{41e_zeL?Smh5oqD*%QwVDmH$pW4@jb zijz2*Xf=PSoc$Ewz9{k8n2bJ`mR337I5LlYptvqN?uOOp{t}R}PB(xhIAfihZ~zbe zPvN4quG_w5vK-&?e<=|F#K^vY0eJ9y+94b>x-L&H>%nwV?iX$O^OKR+L20j{M(I=U z#P?Q;6-7Q0pD0ZvjyV3lCvVYb74XI+pS<#Ns{%|*ie)I>UUOS{arV;b8IO{>5GmhH zVZ~#jc5dLPF*3a*@6WJ(O`oC_kxgE@FryEW@gVoWPMX{xGgpzZ;3S7uMROnY2X}7q z2YWA^*k@d_qUGG=I?NCQ{Yn3OEB1eh_P?d=(<%Ij%eZbwr}H&H4?Ts`{}%jztM9)o zA2!YS$#Wjr8zbG>4HjZa$7}uGmH2)M;*c{q_7TSt>J`O75$rSqNGN3b9MH0H$N+71 ziw8`VToZD#=Fz-p?Iuev0rEmn%anU6Ze#>_$z0Waq;3UecW)rxYo=;Z#wy-qYO-8) z^9T+JGYoplP7xFi6MZ0EXeU~4q`_`Ye5Ah6e11-I4n*bGkadO{bM6L&N3-+@hv+~i z>Zz=f0E=!O+6gZ)#L@F<0b5Y=WPl>Xfhhx3QI zXb`B5SsK%4Me+1zt#ampO+ZA+caK5}pSxO*2uH&u9+e;XDa7ppo|bK$hSa-K`0#sM zw0t#UhdCZaiU%~UzH4sjFv1%BnPIRJKc@QcH~#;Dm}bhOnO|feeYFAbyTe=`_|2g41Wh4-s0zh^%)=dwgP{CX&SOjqP0D7iN zcvKsl0VoHWFr2rDg9)T4wG1?R@$4u4f7I=My5BN_yC z_mEs^f+uei5NX|nP!vEY_;9|F(oW%OA_zk9hFji}k{P*+RlR~xHZ?@@3zk`0((B#A zz;q(##Lz)M-U+SO_G8dIfVg<(3>NPK#5Y^1l@1fJI4`ID^D>fBp(|^yZ;cDP(j&XFUdmV+EmReGus#3p>bD zqS%nB7{=h~$f4BALk6fRGW$_NW#v)Pbo|#2tJNIe572sz+kI(5)8E0m5RDQ`5wEOE zrxzQ5id~oY)xU+vS9_w|4t&aan6Ly*Y5#urPZ2+gZO7KJ)s8cIRDqfjPS68YQ_YQ# zj1=IGI`0436?``uX}QJV zD}r7<+g7GMP{j))9rYY5yOQf35-$r0%$Yy8hZc@;-vAG|rgOt~`^y}5UnYKZRVhQs zvKDz2)oO1UL3j-cIW8)^F;*v75K7`Cbhr*nu^#9`XAx;hC})+;p4{^~!0?tfi_Npa zIT3Qe9gOYKr%bbnoA5Qi^@t2>I+QmWZD}}<5q$+!yUC_-mwK6GDH<2|<`j$?UX|@5 zIwmsLM;-&?IwgYmE^hV%JC2>lSXb;8**j#z6RJ1_99l=_v7L{z*Gu)|-iL}>!_7sk zYliemY?Eidiv>-V(2e&U-PUtwX9PLPk3)_r)%hd^L8HAy659>6t*$)^T|xI5PLt!1 zCzL$ykT>4Ch2CKU48Yus^ThZSNWQu+m85rmD!5FS4V3FXe5gV+jLN>3Zaqw`BA!$q zDxJ4G_BnhSSOpr!?OWY9Tvv|2rfNE){~WMGh>^BS3M}kuUvkI5PmPbehtT(s1|5QT zU1a6}42IeLM`f~AYf*%irOh&Z@0iVkV{V`hb=15MD`AVzXzjFMoE^}nk=HB}zQjGz z>{-kJ>|IEFpEn7akvOZW_j-eF{>w49Td<;0lH((!9dIYeWK%ZW{GGG&UMk-7-4Eu8 zX3n2EIdmE6eSlv}TQc|tt1oT}5~uv;rz@?e{YpHZ;gXvw_53l)e)@Mpuipk~;i$TD z!2U0@LA@&is&Qp^a z;M_piInX+y;>o#z{}OoC2_1j%0bLxpV!LvDIFRM9^iGq$HYH@2E_D}mYcpBrRFbAf zL?Ef00{A)QNvIOMIxnAO_2c#8qs(C`))1B>|K56t#@ILf@C}Gkgb-T$2dbjyd)eqJ zTaU)5bG6pHZsrLNc&m-_mG3N&r&TOG6`!+cwEVY2hCMvJLMW9UaC5lcvpzMjC+=4v z_iasdG!Y9@U;BrNYfj}JIH)YnTDIwRIpXFKOj+T1sWpqn48QyqVr0lZF>nU9(G*Ezse8Wd@TIx#d2 z2HF!N8l=-?O^zpJu9#tqLjzYx(Ag& zjG)9Uq)phM-4kaotysh94Vc(pePYAWo3yL}uut!~QXG&ek6urVorhiOoH=4?uYO-p zr-m#DJ^L5|_Af^WQxnFzgdd3fe(WT0zkgynoiUDQErG*2(0%iTVu@T(cSr)Xa)j*z#k(L0a^bUP_dnPh-6Q$?o;{dvER#9DKINV(-K+B? zZJwZji}t6{w7^fv0`>j+D~j-@kzfikqe*7pQ0*BO;JsoJZ#u*_x#q)VFYWS8CxF#u zRy)ZxLPvV&s7wO1vs#vX9oQzJ%!b81Aj?rw#E0bMRsDgMW$RXGCb**_;l91tw=T(8 zEhK5<>-mgQ-1xF7KbH%Z?w)`hu$|Ag%)Y8TJ1VA2^WWrBh(W^-K|6+ouI=}OK6Bx( zCP-(L=TmbTlq`21>nR0}+U_!K0Hm{rBU~Far!*H7s{bTbjBV1=v@DbbQdLhrnQWGa z-ivwHX{z(+*_G%pAyRXq@Iuol>TO1=JU6f*M`pG>^8qjPeBuqhQJC;0FzPqCtV<=~ zYMlz1)5XX3js?E&+p=|xUI}ry!>_fc z+DARYoHp-4!M;robNCI*__M{v-@zPTm+v#GJ!5jqApHzi!1|m1f!>aw7BB17_a4pj+;yCLcNNv{LpQV?Wo**T03h`)*vBDj zfVaW?V4Bsp^Z>DIXI6%6BUQ&ZL-+&zZ3mt`y9j&gcsJGx0HZ)GGp z3!3OTT|P1;ave-jr;{tSPmv%MU()f(b<5jPefcCOdYhB$BN|!MQ#NUZEj&jNbO4El zAdj!30?AxelMjR`oxdtrj>BE8D0XHX{&=UCu{9UGZnf6E_sOJLrhMAv!~W5ZQ&8}6 z_THEL8}_Fke{G&M9nMOCXiS2)ib3e#$*enC=lT;A^X~}RKNaua(!GDe|8s#nqJx&_ zb9JAB%L%cHw)C~&pH`j(l(~+W5RP7MvO|^OTe1>3$bd>FTAFI>7aEO+49H1>O5S=%s29#ET;TYTPbplDCO)@u)D%=pm z5LjCOll5~B0qn{4{cGi3S^8Xa%&`wWSaDn>Ac?u+E1zGq?Mqio(o@| z6*iW0y)Isr7OX3dA^Kk+6P@^tG3~(dq*5urpxB2eZ=g@6W3w$TmIWbFjY=79`5cH0 zKwH7OzjL~$`_@~l`pXR*ePxMgEjnN<>e~8k>r)N;Dmt}9;Wha?)`>n$1ap~IWu!Oagb zNw;Yu%r2S)`=v@F{vuO+p`f6#|NAb02VQ#>&dt4>W7$d~WEm_(Umw=W4zEhY$^}Ol z)s2nmzNZJ~+cKAQG1%Rz<;xw(M*TT6t7+h;yz+y2H0)~QzTw69ac1eW?)*x# z?S~U^>2?D`Flzv5L;Xif-_qMKuJ0!omH41=@`?OCcmJn}Xoy2z=+NuT56{e$#7C%jv;{zR(p9e7a zg3z9EuTo{sO(fmd)tFrP;V($;z>oaY9Z`8*AKd)zwCYW8<0tYgiD8o%0LCuzO`JXY zo+IsXY!J@pG@R;CeG#ALjIn)IzHc69G*RzY$NIa?+3Xs6+_6MNjSNrJF=b@J`n7~4(*G4a|47aQ<-i|*#)lA4 zgC-{2!Mx8CK`gtd3$n#@c0j?f;=A@)20B4&wQ<=ut8+E@3D`}k$F54x>r})}2{etp z?tVMPZY-mVLfpT(l>bnnWO7LtG5xX#O(?Gg*+MeMln)|qW)Y|Q-SZD_&vddQIk5Xx zUNr8c!=ZBd{v_)p)rnruU-4BY7+xn`C!LQ6_epPbR&_?-*M8%Dl_`dpV*y}7Ov5n? zlc;!Xc44P!DJ*UGz&C!Bk}QuPy-&!ef7u&lE7~EpO4cA0jY~0!e#}E`G_(xM^*_Sw zu@`C8e*N}x3Apwg*-45Yshjx*Wgm^{O4dlOKb5l1obbxUJ$-mQm}03zJydr-_Nu}S z>z-s`OyP;eiY%&!^K5>%8b~hbUOm<%==*4zIfVms=@nf+;v@CYXq}>2+Sp;sa01iu z9u~sx1ntCWtmx{LBFp@+ANZbmoFY zC3s&3Qur?3g;GXS*i1`9)iYzTR&=_fpCajD%y@mL@XSzU2J;OJ80zaxpfTDfT*sfh z8X9s8X>t(1glTZVX6aO>(5lZ|(+%8+M>9kpo(x@EFMElD5qSqg>hdL7W439!V~7aJ z#Lw`N9nx;eB;3(+do7SBgF*DTd4J>ccwo3KAGr#kXjH>qgVDI5&PzJ~@2KDZahA0i z0A)*L3C?6p5AoH+wm~)-jnA1PDyX7|a`SmIF(9B4bFDaqX1diGd=c{K=5!#%bezvd z#!S&VOyy52b!?=Ee|=On9eBVtpDmGZeny@3H%dcA_gTpk>#+X? DVxsWJ