Merge branch 'current' into next

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:

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.
 

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

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
 

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

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

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"
   },

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

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/)

source/_integrations/vacuum.xiaomi_miio.markdown

@@ -316,6 +316,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 <ip of the vacuum> get_room_mapping
+```
+
 ## Retrieving Zoned Cleaning Coordinates
 
 ### Using FloleVac (Android)

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: