diff --git a/CLA.md b/CLA.md index 4560e3be643..885090e5ec2 100644 --- a/CLA.md +++ b/CLA.md @@ -40,7 +40,7 @@ restriction (like related patents, trademarks, and license agreements) of which ## Attribution -This Contributor License Agreement is adapted from the [GitHub CLA][github-cla]. +This Contributor License Agreement is adapted from the GitHub CLA. ## Signing @@ -50,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/ 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/) 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.

diff --git a/source/_integrations/generic_thermostat.markdown b/source/_integrations/generic_thermostat.markdown index 6e247967a82..abadb298863 100644 --- a/source/_integrations/generic_thermostat.markdown +++ b/source/_integrations/generic_thermostat.markdown @@ -85,14 +85,15 @@ 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:`. +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'. 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. +## Full configuration example + ```yaml -# Full example configuration.yaml entry climate: - platform: generic_thermostat name: Study 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. diff --git a/source/_integrations/route53.markdown b/source/_integrations/route53.markdown index b682f582fa1..d0274ee8717 100644 --- a/source/_integrations/route53.markdown +++ b/source/_integrations/route53.markdown @@ -101,3 +101,9 @@ ttl: type: integer default: 300 {% endconfiguration %} + +## Services + +### Service `route53.update_records` + +Use this service to manually trigger an update of the DNS records. 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 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. | 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`. 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: diff --git a/source/lovelace/yaml-mode.markdown b/source/lovelace/yaml-mode.markdown index d37598aabff..e05d2ecb584 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 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.