From d6ebf421a73cbe90cc34427c591e756b73a17437 Mon Sep 17 00:00:00 2001 From: Andrea Donno Date: Tue, 15 Oct 2019 23:00:10 +0200 Subject: [PATCH 01/18] Remove broken Link Seems that the CLA link to github is not existing anymore. I have been looking to find a replacement but this is all I found https://github.com/github/hub/issues/1781. So I thought I might Remove the Link --- CLA.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/CLA.md b/CLA.md index 4560e3be643..757a5a0675d 100644 --- a/CLA.md +++ b/CLA.md @@ -38,10 +38,6 @@ is covered under an appropriate open source license and you have the right under whether created in whole or in part by you, or you have clearly identified the source of the contribution and any license or other restriction (like related patents, trademarks, and license agreements) of which you are personally aware. -## Attribution - -This Contributor License Agreement is adapted from the [GitHub CLA][github-cla]. - ## Signing To sign this CLA you must first submit a pull request to a repository under the Home Assistant organization. From 51aae181cc910930e3d3826cae6b99b067c647ab Mon Sep 17 00:00:00 2001 From: tomlut <10679300+tomlut@users.noreply.github.com> Date: Wed, 16 Oct 2019 23:35:34 +1100 Subject: [PATCH 02/18] Added revert to UI edit mode instructions Added revert to UI edit mode instructions after a user identified that this was not obvious in the Lovelace discord topic. --- source/lovelace/yaml-mode.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/lovelace/yaml-mode.markdown b/source/lovelace/yaml-mode.markdown index d37598aabff..f8367645a1e 100644 --- a/source/lovelace/yaml-mode.markdown +++ b/source/lovelace/yaml-mode.markdown @@ -96,3 +96,5 @@ Your previously customized Lovelace UI won't be modifiable anymore and won't fol - There you see the config for your actual Lovelace UI, you can copy that into the `/ui-lovelace.yaml` file. Navigate to `/lovelace`. When you make changes to `ui-lovelace.yaml`, you don't have to restart Home Assistant or refresh the page. Just hit the refresh button in the menu at the top of the UI. + +To revert to using the UI to edit Lovelace, remove the `configuration.yaml` Lovelace entry and copy your `lovelace.yaml` content back into the raw config section of Home Assiatant and restart. From ee3be805290b9b2ad225276986fe2867c22f0498 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Wed, 16 Oct 2019 15:43:09 +0100 Subject: [PATCH 03/18] Clarification of time formats This PR superceeds #10796 (couldn't rebase that). I couldn't find anything in the current docs on time formats and thought it would be useful to give more details (rather than time | integer description) about ones available. --- source/_integrations/generic_thermostat.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_integrations/generic_thermostat.markdown b/source/_integrations/generic_thermostat.markdown index 6e247967a82..79bb0a2847b 100644 --- a/source/_integrations/generic_thermostat.markdown +++ b/source/_integrations/generic_thermostat.markdown @@ -55,7 +55,7 @@ ac_mode: min_cycle_duration: description: Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on. required: false - type: [time, integer] + type: time cold_tolerance: description: Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched on. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will start when the sensor equals or goes below 24.5. required: false @@ -69,7 +69,7 @@ hot_tolerance: keep_alive: description: Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate integration state (either on or off). required: false - type: [time, integer] + type: time initial_hvac_mode: description: Set the initial HVAC mode. Valid values are `off`, `heat` or `cool`. Value has to be double quoted. If this parameter is not set, it is preferable to set a *keep_alive* value. This is helpful to align any discrepancies between *generic_thermostat* and *heater* state. required: false @@ -85,12 +85,14 @@ precision: default: "`0.5` for Celsius and `1.0` for Fahrenheit." {% endconfiguration %} -A full configuration example looks like the one below. `min_cycle_duration` and `keep_alive` must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:`. +__Notes__ +Time for `min_cycle_duration` and `keep_alive` must be set as wrapped in quotes representation of time in form of "hh:mm:ss", time in seconds (without quotes) or it must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:` Currently the `generic_thermostat` climate platform supports 'heat', 'cool' and 'off' hvac modes. You can force your `generic_thermostat` to avoid starting by setting HVAC mode to 'off'. Please note that when changing the preset mode to away, you will force a target temperature change as well that will get restored once the preset mode is set to none again. +__Example__ ```yaml # Full example configuration.yaml entry climate: From 7ad24ebb0990b13122b9cecf983331186f65d370 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 16 Oct 2019 23:14:03 +0200 Subject: [PATCH 04/18] :pencil2: Tweaks --- source/lovelace/yaml-mode.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/lovelace/yaml-mode.markdown b/source/lovelace/yaml-mode.markdown index f8367645a1e..e05d2ecb584 100644 --- a/source/lovelace/yaml-mode.markdown +++ b/source/lovelace/yaml-mode.markdown @@ -97,4 +97,4 @@ Your previously customized Lovelace UI won't be modifiable anymore and won't fol Navigate to `/lovelace`. When you make changes to `ui-lovelace.yaml`, you don't have to restart Home Assistant or refresh the page. Just hit the refresh button in the menu at the top of the UI. -To revert to using the UI to edit Lovelace, remove the `configuration.yaml` Lovelace entry and copy your `lovelace.yaml` content back into the raw config section of Home Assiatant and restart. +To revert back to using the UI to edit your Lovelace interface, remove the `lovelace` sections from your `configuration.yaml` and copy the contents of your `ui-lovelace.yaml` into the raw config section of Home Assistant and restart. From 37d1c730a7ca1141bcfaa526bfe5db37449bd87b Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 16 Oct 2019 23:24:46 +0200 Subject: [PATCH 05/18] :pencil2: Tweak --- CLA.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/CLA.md b/CLA.md index 757a5a0675d..25f85f744ff 100644 --- a/CLA.md +++ b/CLA.md @@ -38,6 +38,10 @@ is covered under an appropriate open source license and you have the right under whether created in whole or in part by you, or you have clearly identified the source of the contribution and any license or other restriction (like related patents, trademarks, and license agreements) of which you are personally aware. +## Attribution + +This Contributor License Agreement is adapted from the GitHub CLA. + ## Signing To sign this CLA you must first submit a pull request to a repository under the Home Assistant organization. @@ -46,5 +50,4 @@ To sign this CLA you must first submit a pull request to a repository under the This Contributor License Agreement (CLA) was first announced on January 21st, 2017 in [this][cla-blog] blog post and adopted January 28th, 2017. -[github-cla]: https://cla.github.com/agreement [cla-blog]: https://home-assistant.io/blog/2017/01/21/home-assistant-governance/ From 84b13f359a95cb34262ab94e354e028f8d1be68f Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 16 Oct 2019 23:25:04 +0200 Subject: [PATCH 06/18] :pencil2: Tweak --- CLA.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLA.md b/CLA.md index 25f85f744ff..885090e5ec2 100644 --- a/CLA.md +++ b/CLA.md @@ -38,7 +38,7 @@ is covered under an appropriate open source license and you have the right under whether created in whole or in part by you, or you have clearly identified the source of the contribution and any license or other restriction (like related patents, trademarks, and license agreements) of which you are personally aware. -## Attribution +## Attribution This Contributor License Agreement is adapted from the GitHub CLA. From c7f1f2c688ce6e267f918a11620613433c8d1da4 Mon Sep 17 00:00:00 2001 From: Tobias Efinger Date: Thu, 17 Oct 2019 00:00:11 +0200 Subject: [PATCH 07/18] Add D6100 to the supported Samsung TV models --- source/_integrations/samsungtv.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/samsungtv.markdown b/source/_integrations/samsungtv.markdown index 4f6850422b6..724886ec6a2 100644 --- a/source/_integrations/samsungtv.markdown +++ b/source/_integrations/samsungtv.markdown @@ -54,6 +54,7 @@ Currently known supported models: - C7700 - D5500 +- D6100 - D6300SF - D6500 - D6505 From 0d66e71214869a8a21c0d0986947e3377d2bb0d5 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Wed, 16 Oct 2019 23:09:59 +0100 Subject: [PATCH 08/18] Update source/_integrations/generic_thermostat.markdown Co-Authored-By: Franck Nijhof --- source/_integrations/generic_thermostat.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/generic_thermostat.markdown b/source/_integrations/generic_thermostat.markdown index 79bb0a2847b..64595dde846 100644 --- a/source/_integrations/generic_thermostat.markdown +++ b/source/_integrations/generic_thermostat.markdown @@ -92,7 +92,8 @@ Currently the `generic_thermostat` climate platform supports 'heat', 'cool' and Please note that when changing the preset mode to away, you will force a target temperature change as well that will get restored once the preset mode is set to none again. -__Example__ +## Full configuration example + ```yaml # Full example configuration.yaml entry climate: From 9acfb35d5f8f3ac5fa45f6e7f6b79b3f3afc201d Mon Sep 17 00:00:00 2001 From: akasma74 Date: Wed, 16 Oct 2019 23:15:48 +0100 Subject: [PATCH 09/18] in response to reviewer's comments Hope it looks better now --- source/_integrations/generic_thermostat.markdown | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/source/_integrations/generic_thermostat.markdown b/source/_integrations/generic_thermostat.markdown index 64595dde846..2525bc02131 100644 --- a/source/_integrations/generic_thermostat.markdown +++ b/source/_integrations/generic_thermostat.markdown @@ -55,7 +55,7 @@ ac_mode: min_cycle_duration: description: Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on. required: false - type: time + type: [time, integer] cold_tolerance: description: Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched on. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will start when the sensor equals or goes below 24.5. required: false @@ -69,7 +69,7 @@ hot_tolerance: keep_alive: description: Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate integration state (either on or off). required: false - type: time + type: [time, integer] initial_hvac_mode: description: Set the initial HVAC mode. Valid values are `off`, `heat` or `cool`. Value has to be double quoted. If this parameter is not set, it is preferable to set a *keep_alive* value. This is helpful to align any discrepancies between *generic_thermostat* and *heater* state. required: false @@ -85,8 +85,8 @@ precision: default: "`0.5` for Celsius and `1.0` for Fahrenheit." {% endconfiguration %} -__Notes__ -Time for `min_cycle_duration` and `keep_alive` must be set as wrapped in quotes representation of time in form of "hh:mm:ss", time in seconds (without quotes) or it must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:` +Notes +Time for `min_cycle_duration` and `keep_alive` must be set as "hh:mm:ss" or it must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:`. Alternatively, it can be an integer that represents time in seconds. Currently the `generic_thermostat` climate platform supports 'heat', 'cool' and 'off' hvac modes. You can force your `generic_thermostat` to avoid starting by setting HVAC mode to 'off'. @@ -95,7 +95,6 @@ Please note that when changing the preset mode to away, you will force a target ## Full configuration example ```yaml -# Full example configuration.yaml entry climate: - platform: generic_thermostat name: Study From da129637103eb74e96338bce448bf68b62262c2f Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Wed, 16 Oct 2019 21:40:30 -0400 Subject: [PATCH 10/18] Update directions to user profile page User profile page was moved from the top of sidebar to bottom of sidebar starting in 0.96, this text was outdated. --- source/_integrations/frontend.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/frontend.markdown b/source/_integrations/frontend.markdown index a059eb35475..2abaf4600fd 100644 --- a/source/_integrations/frontend.markdown +++ b/source/_integrations/frontend.markdown @@ -111,7 +111,7 @@ automation: ### Manual Theme Selection -When themes are enabled in the `configuration.yaml` file, a new option will show up in the user profile menu (accessed by clicking your user account initials at the top of the sidebar). You can then choose any installed theme from the dropdown list and it will be applied immediately. +When themes are enabled in the `configuration.yaml` file, a new option will show up in the user profile page (accessed by clicking your user account initials at the bottom of the sidebar). You can then choose any installed theme from the dropdown list and it will be applied immediately.

@@ -138,7 +138,7 @@ HTML will be loaded via `` on an ### Manual Language Selection -The browser language is automatically detected. To use a different language, go to the user profile menu (accessed by clicking your user account initials at the top of the sidebar) and select one. It will be applied immediately. +The browser language is automatically detected. To use a different language, go to the user profile page (accessed by clicking your user account initials at the bottom of the sidebar) and select one. It will be applied immediately.

From 452cb7fef0c231674fd4c4b280a642cdbdd83fb0 Mon Sep 17 00:00:00 2001 From: Yann Jajkiewicz Date: Thu, 17 Oct 2019 10:42:48 +0200 Subject: [PATCH 11/18] Fix markdown table syntax for system log --- source/_integrations/system_log.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/system_log.markdown b/source/_integrations/system_log.markdown index b1a14f1d906..3f8fa87f588 100644 --- a/source/_integrations/system_log.markdown +++ b/source/_integrations/system_log.markdown @@ -53,7 +53,7 @@ Write a log entry Errors and warnings are posted as the event `system_log_event`, so it is possible to write automations that trigger whenever a warning or error occurs. The following information is included in each event: | Field | Description | -|-------------------------------------------------------------------------------------------| +|-------------|-----------------------------------------------------------------------------| | `level` | Either `WARNING` or `ERROR` depending on severity. | | `source` | File that triggered the error, e.g., `core.py` or `media_player/yamaha.py`. | | `exception` | Full stack trace if available, an empty string otherwise. | From b009ca8fd9be612939a0f132a12bb6c5dfa61eaa Mon Sep 17 00:00:00 2001 From: Melvin Date: Thu, 17 Oct 2019 11:07:56 +0200 Subject: [PATCH 12/18] Update todoist page for spelling mistake --- source/_integrations/todoist.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/todoist.markdown b/source/_integrations/todoist.markdown index 1632d27aaff..7c82331fc4d 100644 --- a/source/_integrations/todoist.markdown +++ b/source/_integrations/todoist.markdown @@ -156,7 +156,7 @@ Here are two example JSON payloads resulting in the same task: - **due_date_string** (*Optional*): When the task should be due, in [natural language](https://support.todoist.com/hc/en-us/articles/205325931-Dates-and-Times). Mutually exclusive with `due_date` -- **due_date_lang** (*Optional*): When `due_date_string` is set, it is posisble to set the language. +- **due_date_lang** (*Optional*): When `due_date_string` is set, it is possible to set the language. Valid languages are: `en`, `da`, `pl`, `zh`, `ko`, `de`, `pt`, `ja`, `it`, `fr`, `sv`, `ru`, `es`, `nl` - **due_date** (*Optional*): When the task should be due, in either YYYY-MM-DD format or YYYY-MM-DD HH:MM format. Mutually exclusive with `due_date_string`. From ebab213867fb9ecfdc5427d43053c45e0f2c4c8e Mon Sep 17 00:00:00 2001 From: Tobias Efinger Date: Thu, 17 Oct 2019 11:27:16 +0200 Subject: [PATCH 13/18] Add service description for route53 --- source/_integrations/route53.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/route53.markdown b/source/_integrations/route53.markdown index b682f582fa1..0d9e2264d34 100644 --- a/source/_integrations/route53.markdown +++ b/source/_integrations/route53.markdown @@ -101,3 +101,7 @@ ttl: type: integer default: 300 {% endconfiguration %} + +### Service `route53.update_records` + +Use this service to manually trigger an update of the dns records. From 4f0bd105bafc487740a83b98a2bcfbb781119055 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 17 Oct 2019 11:32:42 +0200 Subject: [PATCH 14/18] :pencil2: Tweak --- source/_integrations/route53.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_integrations/route53.markdown b/source/_integrations/route53.markdown index 0d9e2264d34..d0274ee8717 100644 --- a/source/_integrations/route53.markdown +++ b/source/_integrations/route53.markdown @@ -102,6 +102,8 @@ ttl: default: 300 {% endconfiguration %} +## Services + ### Service `route53.update_records` -Use this service to manually trigger an update of the dns records. +Use this service to manually trigger an update of the DNS records. From de2e65bd0960b71985fee24c9b9c238eeccdd9da Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 17 Oct 2019 12:21:39 +0200 Subject: [PATCH 15/18] :pencil2: Tweak --- source/_integrations/generic_thermostat.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/generic_thermostat.markdown b/source/_integrations/generic_thermostat.markdown index 2525bc02131..abadb298863 100644 --- a/source/_integrations/generic_thermostat.markdown +++ b/source/_integrations/generic_thermostat.markdown @@ -85,7 +85,6 @@ precision: default: "`0.5` for Celsius and `1.0` for Fahrenheit." {% endconfiguration %} -Notes Time for `min_cycle_duration` and `keep_alive` must be set as "hh:mm:ss" or it must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:`. Alternatively, it can be an integer that represents time in seconds. Currently the `generic_thermostat` climate platform supports 'heat', 'cool' and 'off' hvac modes. You can force your `generic_thermostat` to avoid starting by setting HVAC mode to 'off'. From 9bd098655f9bd39aa2e2ae1a02a4b0cb34952b6e Mon Sep 17 00:00:00 2001 From: mar005 Date: Thu, 17 Oct 2019 09:15:24 -0500 Subject: [PATCH 16/18] Updated information on supported countries (#10832) Added the link and the verbiage to warn users that not all countries support sender ID such as the US, and added the link. --- source/_integrations/twilio_sms.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/twilio_sms.markdown b/source/_integrations/twilio_sms.markdown index 04b774b4c40..4b7b01a9445 100644 --- a/source/_integrations/twilio_sms.markdown +++ b/source/_integrations/twilio_sms.markdown @@ -23,7 +23,7 @@ notify: {% configuration %} from_number: - description: An [E.164](https://en.wikipedia.org/wiki/E.164) formatted phone number, like +14151234567. See [Twilio's guide to formatting phone numbers](https://www.twilio.com/help/faq/phone-numbers/how-do-i-format-phone-numbers-to-work-internationally) for more information. Alternatively, a sender ID can be used instead of a phone number. The sender ID must be formatted according to Twilio's guidelines. See [Twilio's guide to sender ID](https://support.twilio.com/hc/en-us/articles/223181348-Getting-started-with-Alphanumeric-Sender-ID) for more information. + description: An [E.164](https://en.wikipedia.org/wiki/E.164) formatted phone number, like +14151234567. See [Twilio's guide to formatting phone numbers](https://www.twilio.com/help/faq/phone-numbers/how-do-i-format-phone-numbers-to-work-internationally) for more information. Alternatively, a sender ID can be used instead of a phone number. The sender ID must be formatted according to Twilio's guidelines. See [Twilio's guide to sender ID](https://support.twilio.com/hc/en-us/articles/223181348-Getting-started-with-Alphanumeric-Sender-ID) for more information. Do keep in mind that not all countries support sender ID. See [Twilio's page of supported countries](https://support.twilio.com/hc/en-us/articles/223133767-International-support-for-Alphanumeric-Sender-ID) for more information. required: true type: string name: From 248f0e33790ed9ed7a7055665fa0fc9b7cdef115 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6ren?= Date: Thu, 17 Oct 2019 17:29:04 +0200 Subject: [PATCH 17/18] Insolvency warning updated (#10851) --- source/_integrations/nello.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/nello.markdown b/source/_integrations/nello.markdown index fc1d5492e3b..b6f189168fa 100644 --- a/source/_integrations/nello.markdown +++ b/source/_integrations/nello.markdown @@ -10,7 +10,7 @@ ha_iot_class: Cloud Polling ---

-Locumi Labs, the manufacturer of Nello, entered insolvency on the 2nd of October 2019 closed their cloud service. Since Nello One locks require this cloud service, the locks will cease to operate as of the 18th October 2019. +Locumi Labs, the manufacturer of Nello, went bankrupt on 2 October 2019. Since Nello One locks require this cloud service, the locks will no longer work if the Nello shuts down the servers, which according to the official announcement should not happen for the time being. Nello has promised existing users via email that they will work on an alternative to use the lock without a server.
The `nello` platform allows you to control [Nello](https://www.nello.io) intercoms. From 816660cdbb5829bebf60daa317b4cf59a4fbc9f5 Mon Sep 17 00:00:00 2001 From: Hadi Victorya <33802468+hadipsy27@users.noreply.github.com> Date: Thu, 17 Oct 2019 22:31:30 +0700 Subject: [PATCH 18/18] update readme link (#10518) this link {https://travis-ci.org/home-assistant/home-assistant.github.io} doesn't work, I am deleted from README --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 728fc3c4a93..5fd4c6e2389 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,4 @@ [![Discord](https://img.shields.io/discord/330944238910963714.svg)](https://discord.gg/CxqDrfU) -[![Travis branch](https://img.shields.io/travis/home-assistant/home-assistant.github.io/next.svg)](https://travis-ci.org/home-assistant/home-assistant.github.io) [![Krihelimeter](https://img.shields.io/badge/Krihelimeter-unknown-brightgreen.svg)](http://www.krihelinator.xyz) [![License: CC BY-NC-SA 4.0](https://img.shields.io/badge/License-CC%20BY--NC--SA%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by-nc-sa/4.0/)