From ffdd815aec7649d7669a026333ffc384dcab1bbc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=85ke=20Strandberg?= Date: Wed, 8 Jan 2020 19:03:06 +0100 Subject: [PATCH 1/8] Add link to Modbus Climate (#11675) --- source/_integrations/modbus.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/modbus.markdown b/source/_integrations/modbus.markdown index 36fdf80aacc..a143bc7c937 100644 --- a/source/_integrations/modbus.markdown +++ b/source/_integrations/modbus.markdown @@ -150,5 +150,6 @@ modbus: ## Building on top of Modbus - [Modbus Binary Sensor](/integrations/binary_sensor.modbus/) + - [Modbus Climate](/integrations/climate.modbus/) - [Modbus Sensor](/integrations/sensor.modbus/) - [Modbus Switch](/integrations/switch.modbus/) From d704be3803ad9bad1f3b2ddc8d64f2e26ae6221b Mon Sep 17 00:00:00 2001 From: Alexander Petrov Date: Thu, 9 Jan 2020 16:44:23 +0700 Subject: [PATCH 2/8] Update input_datetime: reorder default values (#11685) --- source/_integrations/input_datetime.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/input_datetime.markdown b/source/_integrations/input_datetime.markdown index a857135c556..774cce64224 100644 --- a/source/_integrations/input_datetime.markdown +++ b/source/_integrations/input_datetime.markdown @@ -63,7 +63,7 @@ input_datetime: description: Set the initial value of this input, depending on `has_time` and `has_date`. required: false type: [datetime, time, date] - default: 1970-01-01 00:00 | 1970-01-01 | 00:00 + default: 1970-01-01 00:00 | 00:00 | 1970-01-01 {% endconfiguration %} ### Attributes From 4a902a7835a31a63b0387d9de3f6141f7e08a732 Mon Sep 17 00:00:00 2001 From: Mattheus Date: Thu, 9 Jan 2020 10:50:47 +0100 Subject: [PATCH 3/8] remove api_password option from http: config (#11680) remove api_password option from http: config because the option are deprecated since 0.90 release of HomeAssistant. --- .../_docs/ecosystem/certificates/tls_domain_certificate.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_docs/ecosystem/certificates/tls_domain_certificate.markdown b/source/_docs/ecosystem/certificates/tls_domain_certificate.markdown index 27563e1a3d7..5a67900752d 100644 --- a/source/_docs/ecosystem/certificates/tls_domain_certificate.markdown +++ b/source/_docs/ecosystem/certificates/tls_domain_certificate.markdown @@ -57,7 +57,6 @@ The [`http`](/integrations/http/) section must contain the full path to the need ```yaml http: - api_password: YOUR_SECRET_PASSWORD base_url: https://mydomain.com:8123 ssl_certificate: /etc/letsencrypt/live/mydomain.com/fullchain.pem ssl_key: /etc/letsencrypt/live/mydomain.com/privkey.pem From 5c307536bf957f372a200178a14da32e97ca0243 Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 9 Jan 2020 11:25:23 +0100 Subject: [PATCH 4/8] =?UTF-8?q?Add=20docs=20in=20vaccum.xiaomi=5Fmiio.mark?= =?UTF-8?q?down=20with=20how=20to=20clean=20a=20sp=E2=80=A6=20(#11676)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Add documentation in vaccum.xiaomi_miio.markdown with instructions how to clean a specific room It specifies how the command send_command can be used for Xiaomi vacuums. * Update Xiaomi vacuum docs on how to clean a room An example is specified under a new section. The service vacuum.send_command is not documented here anymore. * :pencil2: Tweaks Co-authored-by: Franck Nijhof --- .../_integrations/vacuum.xiaomi_miio.markdown | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/source/_integrations/vacuum.xiaomi_miio.markdown b/source/_integrations/vacuum.xiaomi_miio.markdown index cce32980088..8a4f3ecc9d9 100644 --- a/source/_integrations/vacuum.xiaomi_miio.markdown +++ b/source/_integrations/vacuum.xiaomi_miio.markdown @@ -315,6 +315,30 @@ The information output is: - `Address` - The IP that the device has on the network. - `Token` - The token of the device or `???` if it could not be automatically determined. + +## Example on how to clean a specific room + +Example script using [`vacuum.send_command`](/integrations/vacuum/) to clean a specific room: + +```yaml +vacuum_kitchen: + alias: "Clean the kitchen" + sequence: + - service: vacuum.send_command + data: + entity_id: vacuum.xiaomi_vacuum_cleaner + command: app_segment_clean + params: [18] +``` + +Where params specify room numbers, for multiple rooms, params can be specified like `[17,18]`. + +Valid room numbers can be retrieved using miio command-line tool. It will only give room numbers and not the room names. To get the room names, one can just test the app_segment_clean command and see which room it cleans. + +```bash +miio protocol call get_room_mapping +``` + ## Retrieving Zoned Cleaning Coordinates ### Using FloleVac (Android) From bb483a5540b99d2b9ef02bcf8f0c3dd63ff0de71 Mon Sep 17 00:00:00 2001 From: Petro31 <35082313+Petro31@users.noreply.github.com> Date: Thu, 9 Jan 2020 12:29:36 -0500 Subject: [PATCH 5/8] Update condition.markdown (#11688) Quoting was wrong. --- source/_docs/automation/condition.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/automation/condition.markdown b/source/_docs/automation/condition.markdown index 76072d2f3ec..931b26c19c5 100644 --- a/source/_docs/automation/condition.markdown +++ b/source/_docs/automation/condition.markdown @@ -21,9 +21,9 @@ automation: condition: or conditions: - condition: template - value_template: '{% raw %}{{ state_attr('sun.sun', 'elevation') < 4 }}{% endraw %}' + value_template: "{% raw %}{{ state_attr('sun.sun', 'elevation') < 4 }}{% endraw %}" - condition: template - value_template: '{% raw %}{{ states('sensor.sensorluz_7_0') < 10 }}{% endraw %}' + value_template: "{% raw %}{{ states('sensor.sensorluz_7_0') < 10 }}{% endraw %}" action: - service: scene.turn_on entity_id: scene.DespiertaDespacho From cc24c23fcdfd61cab4e73d6b113c11e40f7b2468 Mon Sep 17 00:00:00 2001 From: THATDONFC Date: Fri, 10 Jan 2020 00:29:05 -0800 Subject: [PATCH 6/8] Update PiVPN URL (#11693) Update PiVPN URL to match the new site location. --- source/_docs/configuration/securing.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/securing.markdown b/source/_docs/configuration/securing.markdown index 34391126d78..2d7774f51ab 100644 --- a/source/_docs/configuration/securing.markdown +++ b/source/_docs/configuration/securing.markdown @@ -15,7 +15,7 @@ Here's the summary of what you *must* do to secure your Home Assistant system: ## Remote Access -If you want secure remote access, the easiest option is to use [Home Assistant cloud](/cloud/). Other options are to use [TLS/SSL](/docs/ecosystem/certificates/lets_encrypt/) to expose your instance to the internet, use a [VPN](http://www.pivpn.io/), [Tor](/docs/ecosystem/tor/) or an [SSH tunnel](/blog/2017/11/02/secure-shell-tunnel/). +If you want secure remote access, the easiest option is to use [Home Assistant cloud](/cloud/). Other options are to use [TLS/SSL](/docs/ecosystem/certificates/lets_encrypt/) to expose your instance to the internet, use a [VPN](https://pivpn.dev/), [Tor](/docs/ecosystem/tor/) or an [SSH tunnel](/blog/2017/11/02/secure-shell-tunnel/). ### Extras for manual installations From 64b938b3d1c9f4e228ddf23306e9228390eed05f Mon Sep 17 00:00:00 2001 From: John Hollowell Date: Fri, 10 Jan 2020 03:30:44 -0500 Subject: [PATCH 7/8] 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: From d503e4af3ea1567635b80a6c3f23d58ed7f600c4 Mon Sep 17 00:00:00 2001 From: sjee105 Date: Fri, 10 Jan 2020 15:21:54 +0100 Subject: [PATCH 8/8] tts platform renamed (#11699) --- source/_cookbook/sonos_say.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_cookbook/sonos_say.markdown b/source/_cookbook/sonos_say.markdown index 1c77c4e6bb3..0d89583d62f 100644 --- a/source/_cookbook/sonos_say.markdown +++ b/source/_cookbook/sonos_say.markdown @@ -52,7 +52,7 @@ Note that this example uses the `voicerss` text-to-speech platform. There are ma ```yaml tts: - - platform: google + - platform: google_translate ``` If you want to use this TTS engine, change the line in the example provided to: