diff --git a/components/updater/index.html b/components/updater/index.html
index 4d5821f49c..0bc47fc0fd 100644
--- a/components/updater/index.html
+++ b/components/updater/index.html
@@ -74,8 +74,8 @@
- The updater
component will check daily for new releases. It will show a badge in the frontend if a new version was found.
-The updater component will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the timezone, Python version and operating system information. No identifiable information (i.e. IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python source code. For further information about the Updater’s data please check the detailed overview.
+ The updater
component will check daily for new releases. It will show a badge in the frontend if a new version is found.
+The updater component will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the time zone, Python version and operating system information. No identifiable information (i.e., IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python source code. For further information about the Updater’s data, please check the detailed overview.
To integrate this into Home Assistant, add the following section to your configuration.yaml
file:
updater:
diff --git a/components/vacuum.roomba/index.html b/components/vacuum.roomba/index.html
index 1effb12e17..ddfb388de3 100644
--- a/components/vacuum.roomba/index.html
+++ b/components/vacuum.roomba/index.html
@@ -76,7 +76,7 @@
The roomba
component allows you to control your Roomba.
-This platform has only been tested with an iRobot Roomba 980, but should work find
+This platform has only been tested with an iRobot Roomba 980 but should work find
with any Wi-Fi enabled Roomba like the 690, 890 or the 960.
To add your roomba vacuum to your installation, add the following to your configuration.yaml
file:
diff --git a/components/vacuum.xiaomi/index.html b/components/vacuum.xiaomi/index.html
index fbdbee6963..88ce6e3a06 100644
--- a/components/vacuum.xiaomi/index.html
+++ b/components/vacuum.xiaomi/index.html
@@ -84,18 +84,18 @@ If your Home Assistant installation is running in a
$ source /srv/homeassistant/bin/activate
-In order to fetch the token follow these instructions depending on your mobile phone platform.
+To fetch the token follow these instructions depending on your mobile phone platform.
Windows and Android
- Configure the robot with the Mi-Home app.
- Enable developer mode and USB debugging on the Android phone and plug it into the computer.
- - Get ADB tool for Windows : https://developer.android.com/studio/releases/platform-tools.html
+ - Get ADB tool for Windows: https://developer.android.com/studio/releases/platform-tools.html
- Create a backup of the application com.xiaomi.smarthome:
.\adb backup -noapk com.xiaomi.smarthome -f backup.ab
- - If you have this message : “More than one device or emulator”, use this command to list all devices:
+
- If you have this message: “More than one device or emulator”, use this command to list all devices:
@@ -105,15 +105,15 @@ If your Home Assistant installation is running in a
java.exe -jar ../android-backup-extractor/abe.jar unpack backup.ab backup.tar ""
- Unzip the “.tar” file.
- - Open the sqlite DB miio2.db with a tool like SQLite Manager extension for FireFox.
- - Get token from “devicerecord” table.
+ - Open the SQLite DB miio2.db with a tool like SQLite Manager extension for FireFox.
+ - Get the token from “devicerecord” table.
macOS and iOS
@@ -211,7 +211,7 @@ If your Home Assistant installation is running in a Service vacuum/xiaomi_remote_control_move_step
-Use this call to enter the remote control mode, make one movement, and stop and exit the remote control mode.
+Use this call to enter the remote control mode, make one move, and stop and exit the remote control mode.
diff --git a/components/vacuum/index.html b/components/vacuum/index.html
index 4c77200d7a..6cbe87409f 100644
--- a/components/vacuum/index.html
+++ b/components/vacuum/index.html
@@ -214,7 +214,7 @@
Service vacuum/set_fanspeed
-Set the fan speed of the botvac. The fanspeed
can be a label, as balanced
or turbo
, or be a number, it depends of the vacuum
platform.
+Set the fan speed of the botvac. The fanspeed
can be a label, as balanced
or turbo
, or be a number; it depends on the vacuum
platform.
diff --git a/components/vera/index.html b/components/vera/index.html
index f82e786606..b654392804 100644
--- a/components/vera/index.html
+++ b/components/vera/index.html
@@ -89,8 +89,8 @@
It is recommended to assign a static IP address to your Vera Controller. This ensures that it won’t change IP addresses, so you won’t have to change the vera_controller_url
if it reboots and comes up with a different IP address. See your router’s manual for details on how to set this up. If you need the MAC address of your Vera, check the label on the bottom.
Configure devices
-By default your switches will be added to Home Assistant as switches, however if some of them are light switches, you can tell Home Assistant this using the optional lights
parameter as shown below.
-Vera imports detailed Z-Wave devices into Home Assistant. This can include system devices and other devices that you don’t use, you can tell Home Assistant not to load these devices using the exclude:
parameter as shown below.
+By default your switches will be added to Home Assistant as switches, however, if some of them are light switches, you can tell Home Assistant this using the optional lights
parameter as shown below.
+Vera imports detailed Z-Wave devices into Home Assistant. This can include system devices and other devices that you don’t use; you can tell Home Assistant not to load these devices using the exclude:
parameter as shown below.
You can find the Vera device id either via the advanced properties of the device in the Vera UI or by checking the Vera Device Id
attribute on each device imported into Home Assistant (under the developer tools).
vera:
vera_controller_url: http://192.168.1.161:3480/
@@ -101,7 +101,7 @@
Using Z-Wave devices in automation
-If you want to use a Z-Wave device from the Vera controller in Home Assistant automation, you’ll need the entity id. In the Home Assistant UI you’ll find all entities listed under the
icon of the Developer Tools section. Look for entities that contain ‘Vera Device Id’ in their attributes, you’ll find the entity id on the left.
+If you want to use a Z-Wave device from the Vera controller in Home Assistant automation, you’ll need the entity id. In the Home Assistant UI you’ll find all entities listed under the
icon of the Developer Tools section. Look for entities that contain ‘Vera Device Id’ in their attributes, and you’ll find the entity id on the left.