From 64b938b3d1c9f4e228ddf23306e9228390eed05f Mon Sep 17 00:00:00 2001 From: John Hollowell Date: Fri, 10 Jan 2020 03:30:44 -0500 Subject: [PATCH] Update Misc Typos (#11597) * Update providers.markdown * Update tutorial.markdown * Update aws.markdown * Update vera.markdown --- source/_docs/authentication/providers.markdown | 2 +- source/_docs/ecosystem/appdaemon/tutorial.markdown | 2 +- source/_integrations/aws.markdown | 2 +- source/_integrations/vera.markdown | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown index 3e5aca59414..9068562e563 100644 --- a/source/_docs/authentication/providers.markdown +++ b/source/_docs/authentication/providers.markdown @@ -118,7 +118,7 @@ homeassistant: - group: system-users ``` -First note, for `trusted_users` configuration you need to use `user id`, which you can find through Configuration -> Users -> View User Detail. The `trusted_users` configuration will not validate the existing of the user, so please make sure you have put in the correct user id by yourself. +First note, for `trusted_users` configuration you need to use `user id`, which you can find through Configuration -> Users -> View User Detail. The `trusted_users` configuration will not validate the existence of the user, so please make sure you have put in the correct user id by yourself. Second note, a trusted user with an IPv6 address must put the IPv6 address in quotes as shown. diff --git a/source/_docs/ecosystem/appdaemon/tutorial.markdown b/source/_docs/ecosystem/appdaemon/tutorial.markdown index 67475316b7c..fdf445b4c1d 100644 --- a/source/_docs/ecosystem/appdaemon/tutorial.markdown +++ b/source/_docs/ecosystem/appdaemon/tutorial.markdown @@ -75,7 +75,7 @@ This is also fairly easy to achieve with Home Assistant automations, but we are ### Motion Light -Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changesd where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callback function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms: +Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changes where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callback function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms: ```python import appdaemon.appapi as appapi diff --git a/source/_integrations/aws.markdown b/source/_integrations/aws.markdown index 526da0b321c..b86c8792049 100644 --- a/source/_integrations/aws.markdown +++ b/source/_integrations/aws.markdown @@ -164,7 +164,7 @@ The SQS event payload will contain everything passed in the service call payload ```json { "title": "Test message!", - "target": "https://sqs.us-east-1.amazonaws.com/123456789012/queue2%22, + "target": "https://sqs.us-east-1.amazonaws.com/123456789012/queue2%22", "data": { "test": "okay" }, diff --git a/source/_integrations/vera.markdown b/source/_integrations/vera.markdown index b4787b103a4..d46ccbfc236 100644 --- a/source/_integrations/vera.markdown +++ b/source/_integrations/vera.markdown @@ -15,7 +15,7 @@ ha_category: ha_release: pre 0.7 --- -The [Vera](https://getvera.com/) hub is a controller mainly connecting to Z-Wave devices. +The [Vera](https://getvera.com/) hub is a controller mainly for connecting to Z-Wave devices. There is currently support for the following device types within Home Assistant: