diff --git a/sass/inuitcss/README.md b/sass/inuitcss/README.md index 77155d091d9..3567be2208e 100644 --- a/sass/inuitcss/README.md +++ b/sass/inuitcss/README.md @@ -177,7 +177,7 @@ variables required for the library to compile without failing. These variables are preset because Sass will error without them, however they are **not** set in stone, and you are encouranged to override and experiment with them. -It is tempting to modify their vaules in the inuit.css submodule but this is +It is tempting to modify their values in the inuit.css submodule but this is **not** the correct method for modifying inuit.css, and in doing so you will prevent yourself from being able to update inuit.css’ core library. The correct procedure is to redefine that variable in `_vars.scss` found in the inuit.css diff --git a/sass/inuitcss/generic/_widths.scss b/sass/inuitcss/generic/_widths.scss index 66d76f1a610..6e2a4b34310 100644 --- a/sass/inuitcss/generic/_widths.scss +++ b/sass/inuitcss/generic/_widths.scss @@ -145,7 +145,7 @@ /** * If you have set the additional `$responsive-extra` variable to ‘true’ in * `_vars.scss` then you now have access to the following class available to - * accomodate much larger screen resolutions. + * accommodate much larger screen resolutions. */ @if $responsive-extra == true{ diff --git a/sass/inuitcss/objects/_grids.scss b/sass/inuitcss/objects/_grids.scss index 9499e5ed612..4fcf51f3e8f 100644 --- a/sass/inuitcss/objects/_grids.scss +++ b/sass/inuitcss/objects/_grids.scss @@ -46,7 +46,7 @@ /** - * Very infrequently occuring grid wrappers as children of grid wrappers. + * Very infrequently occurring grid wrappers as children of grid wrappers. */ .grid > .grid{ margin-left:0; diff --git a/sass/inuitcss/objects/_icon-text.scss b/sass/inuitcss/objects/_icon-text.scss index 0f8250ff3b8..e5cd910d72c 100644 --- a/sass/inuitcss/objects/_icon-text.scss +++ b/sass/inuitcss/objects/_icon-text.scss @@ -11,7 +11,7 @@ Help & support * - * However we will sometimes want a larger, explicity set gap: + * However we will sometimes want a larger, explicitly set gap: Help & support diff --git a/sass/oscailte/base/_solarized.scss b/sass/oscailte/base/_solarized.scss index 086044990ec..7924d26cb7e 100644 --- a/sass/oscailte/base/_solarized.scss +++ b/sass/oscailte/base/_solarized.scss @@ -1,4 +1,4 @@ -// // This file is just a butchered version fo the one included in the default Octopress theme. +// // This file is just a butchered version of the one included in the default Octopress theme. // // It could most definitely do with some cleaning up in the future. // @mixin selection($bg, $color: inherit, $text-shadow: none){ diff --git a/sass/plugins/_plugins.scss b/sass/plugins/_plugins.scss index 3b4ba0b8a80..25af026ba02 100644 --- a/sass/plugins/_plugins.scss +++ b/sass/plugins/_plugins.scss @@ -1,6 +1,6 @@ /* Add plugin stylesheets to this directory and they will be automatically - Imported. Load order is alphabetical and styles can be overriden in + Imported. Load order is alphabetical and styles can be overridden in custom/_style.scss which is loaded after all plugin stylesheets. */ diff --git a/source/_docs/asterisk_mbox.markdown b/source/_docs/asterisk_mbox.markdown index 8b2da063d7b..058d006a549 100644 --- a/source/_docs/asterisk_mbox.markdown +++ b/source/_docs/asterisk_mbox.markdown @@ -56,7 +56,7 @@ Before beginning make sure that you have the following: - `host` (*Optional*): The IP address to listen on for client requests. This defaults to all IP addresses on the server. To listen only locally, choose `127.0.0.1` - `port` (*Optional*): The port to listen on for client requests. Defaults to 12345. - - `password` (*Required*): A password shared between client and server. Use only alpha-numeric characters and spaces + - `password` (*Required*): A password shared between client and server. Use only alphanumeric characters and spaces - `mbox_path` (*Required*): The path to the storage location of mailbox files. This is typically `/var/spool/asterisk/voicemail/default//` - `cache_file` (*Required*): A fully-qualified path to a file that can be written by the server containing transcriptions of voicemails. Example: `/var/spool/asterisk/transcription.cache` - `google_key` (*Required*): Your 40 characters Google API key. diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown index 6f1d89e1ab6..de2ba58cd2c 100644 --- a/source/_docs/automation/templating.markdown +++ b/source/_docs/automation/templating.markdown @@ -34,7 +34,7 @@ The following describes trigger data associated with all platforms. | `trigger.platform` | Hardcoded: `mqtt`. | `trigger.topic` | Topic that received payload. | `trigger.payload` | Payload. -| `trigger.payload_json` | Dictonary of the JSON parsed payload. +| `trigger.payload_json` | Dictionary of the JSON parsed payload. | `trigger.qos` | QOS of payload. ### Numeric State diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 8cd2284fd57..0b481d5e677 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -454,7 +454,7 @@ Setting up a device tracker: - State topic: `homeassistant/device_tracker/paulus/state` - Example state payload: `home` or `not_home` or `location name` -If the device supports gps co-ordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload: +If the device supports gps coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload: - Attributes topic: `homeassistant/device_tracker/paulus/attributes` - Example attributes payload: diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown index 980a7a12b29..b7f69946a6a 100644 --- a/source/_docs/z-wave/device-specific.markdown +++ b/source/_docs/z-wave/device-specific.markdown @@ -62,7 +62,7 @@ For both processes below you will need to insert your SD card into your PC and o #### Raspberry Pi 4 procedure -Add the following paramaters to the bottom of the `/boot/config.txt` file. +Add the following parameters to the bottom of the `/boot/config.txt` file. ```text dtoverlay=disable-bt @@ -384,7 +384,7 @@ Zen22v2 (Dimmer): - Enables/Disables the double-tap fucntion and assign brightness to single tap. Last level: single tap returns to last brightness level. Full/Max level: single tap returns to full/max level + Enables/Disables the double-tap function and assign brightness to single tap. Last level: single tap returns to last brightness level. Full/Max level: single tap returns to full/max level @@ -708,7 +708,7 @@ Zen30 (Double Switch): - Enable/Disable Double-tap for Dimmer. Enables/Disables the double-tap fucntion and assign brightness to single tap. enabled: single tap turns on to maximum brightness level. disabled (last level): single tap returns to last brightness level. disabled (full/max level): single tap returns to full brightmess. Default: enabled + Enable/Disable Double-tap for Dimmer. Enables/Disables the double-tap function and assign brightness to single tap. enabled: single tap turns on to maximum brightness level. disabled (last level): single tap returns to last brightness level. disabled (full/max level): single tap returns to full brightmess. Default: enabled @@ -899,7 +899,7 @@ Zen34 Remote Switch: - Choose the LED indicator color for the upper paddle remote controle triggers + Choose the LED indicator color for the upper paddle remote controlled triggers diff --git a/source/_includes/common-tasks/file_access.md b/source/_includes/common-tasks/file_access.md index f21403ed590..e28f99d57f5 100644 --- a/source/_includes/common-tasks/file_access.md +++ b/source/_includes/common-tasks/file_access.md @@ -37,9 +37,9 @@ You would then enter the IP address or hostname of your Home Assistant OS instan ### Installing and using the SSH add-on (requires enabling advanced mode for the HA user) -The Terminal & SSH add-on provides access over an SSH connection, and also includes nano and vi editors. It can be installed from the add-on store's Official add-on repository after enabling advanced mode for your Home Assistant user's profile. Addtionally, this add-on provides access to the Home Assistant Command Line Interface (CLI) which provides custom commands for checking logs, stopping and starting Home Assistant and add-ons, creating/restoring snapshots, and more. (See [Home Assistant via Command Line](https://www.home-assistant.io/hassio/commandline/) for further info). The Terminal & SSH add-on does *not* provide access to the underlying host file system. +The Terminal & SSH add-on provides access over an SSH connection, and also includes nano and vi editors. It can be installed from the add-on store's Official add-on repository after enabling advanced mode for your Home Assistant user's profile. Additionally, this add-on provides access to the Home Assistant Command Line Interface (CLI) which provides custom commands for checking logs, stopping and starting Home Assistant and add-ons, creating/restoring snapshots, and more. (See [Home Assistant via Command Line](https://www.home-assistant.io/hassio/commandline/) for further info). The Terminal & SSH add-on does *not* provide access to the underlying host file system. -To use the add-on, enter a password or public key on its configuration page, then save and start the add-on. +To use the add-on, enter a password or public key on its configuration page, then save and start the add-on. The Terminal & SSH add-on also provides a web terminal which allows you to access a terminal via the Home Assistant user interface. In order to access from an ssh client, a port needs to be entered in the network section of the add-on's configuration page. @@ -49,7 +49,7 @@ The Terminal & SSH add-on also provides a web terminal which allows you to acces The Visual Studio Code add-on provides access through a feature packed web-based version of the Visual Studio Code editor and currently only supports AMD64 and aarch64/ARM64 machines. This add-on can be installed in the add-on store from the Community add-on repository. The add-on also provides access to the Home Assistant Command Line Interface (CLI) using VSC's built in terminal, which allows for checking logs, stopping and starting Home Assistant and add-ons, creating/restoring snapshots, and more. (See [Home Assistant via Command Line](https://www.home-assistant.io/hassio/commandline/) for further info). -There is no configuration required for editing files within your `/config` directory. In order to enable access to other directories, it is necessary to edit the add-on's configuration from its configuration tab. See the add-on documentation for details. +There is no configuration required for editing files within your `/config` directory. In order to enable access to other directories, it is necessary to edit the add-on's configuration from its configuration tab. See the add-on documentation for details. --- @@ -57,4 +57,4 @@ There is no configuration required for editing files within your `/config` direc A more basic and light weight alternative to Visual Studio Code, the File Editor add-on provides access through Hass-Configurator, which is a web-based filesystem-browser and text-editor. YAML files are automatically checked for syntax errors while editing. This add-on can be installed via the add-on store from the official add-on repository. -There is no configuration required for editing files within your `/config` directory. In order to enable access to further directories, editing the add-on configuration is required. See the add-on documentation for details. +There is no configuration required for editing files within your `/config` directory. In order to enable access to further directories, editing the add-on configuration is required. See the add-on documentation for details. diff --git a/source/_includes/installation/container/alternative.md b/source/_includes/installation/container/alternative.md index 549f72836b4..ec9aa89e7e7 100644 --- a/source/_includes/installation/container/alternative.md +++ b/source/_includes/installation/container/alternative.md @@ -22,7 +22,7 @@ The steps would be: If you are using the built-in firewall, you must also add the port 8123 to allowed list. This can be found in "Control Panel -> Security" and then the Firewall tab. Click "Edit Rules" besides the Firewall Profile dropdown box. Create a new rule and select "Custom" for Ports and add 8123. Edit Source IP if you like or leave it at default "All". Action should stay at "Allow". -To use a Z-Wave USB stick for Z-Wave control, the HA Docker container needs extra configuration to access to the USB stick. While there are multiple ways to do this, the least privileged way of granting access can only be performed via the Terminal, at the time of writing. See this page for configuring Terminal acces to your Synology NAS: +To use a Z-Wave USB stick for Z-Wave control, the HA Docker container needs extra configuration to access to the USB stick. While there are multiple ways to do this, the least privileged way of granting access can only be performed via the Terminal, at the time of writing. See this page for configuring Terminal access to your Synology NAS: diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md index f33af51dd51..73d00f256ee 100644 --- a/source/_includes/installation/operating_system.md +++ b/source/_includes/installation/operating_system.md @@ -207,7 +207,7 @@ _All these can be extended if your usage calls for more resources._ - title: VMware ESXi/vSphere content: | - Use the “E1001” or “E1001E” virtual network adapater. There are confirmed mDNS/Multicast discovery issues when using VMware’s “VMXnet3” virtual network adapter. + Use the “E1001” or “E1001E” virtual network adapter. There are confirmed mDNS/Multicast discovery issues when using VMware’s “VMXnet3” virtual network adapter. {% endif %} {% if page.installation_type == 'windows' %} - title: Hyper-V diff --git a/source/_integrations/ads.markdown b/source/_integrations/ads.markdown index 395c0926b5a..796e6f481ad 100644 --- a/source/_integrations/ads.markdown +++ b/source/_integrations/ads.markdown @@ -104,7 +104,7 @@ device_class: ## Light -The `ads` light platform allows you to control your connecte ADS lights. +The `ads` light platform allows you to control your connected ADS lights. To use your ADS device, you first have to set up your [ADS hub](#configuration) and then add the following to your `configuration.yaml` file: diff --git a/source/_integrations/arlo.markdown b/source/_integrations/arlo.markdown index bc19851c80d..5da9f285464 100644 --- a/source/_integrations/arlo.markdown +++ b/source/_integrations/arlo.markdown @@ -86,12 +86,12 @@ home_mode_name: required: false type: string away_mode_name: - description: "Arlo base station does not have a built-in away mode. You can map one of your custom modes to Home Assistant's away mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match eactly as you set it up in the Arlo app." + description: "Arlo base station does not have a built-in away mode. You can map one of your custom modes to Home Assistant's away mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app." required: false type: string default: "`Armed` mode in Arlo" night_mode_name: - description: "Arlo base station does not have a built-in night mode. You can map one of your custom modes to Home Assistant's night mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match eactly as you set it up in the Arlo app." + description: "Arlo base station does not have a built-in night mode. You can map one of your custom modes to Home Assistant's night mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app." required: false type: string default: "`Armed` mode in Arlo" diff --git a/source/_integrations/atag.markdown b/source/_integrations/atag.markdown index eef42a145ca..5329226f892 100644 --- a/source/_integrations/atag.markdown +++ b/source/_integrations/atag.markdown @@ -57,7 +57,7 @@ This integration supports the following services (see [Climate](/integrations/cl - `boost` enable fireplace mode
-`HVAC mode Auto` (Weather based) should not be confused with `Preset mode Auto` (Sheduled, thermostat mode). +`HVAC mode Auto` (Weather based) should not be confused with `Preset mode Auto` (Scheduled, thermostat mode). Currently selection of custom timeframes in Extend, Away and boost modes is not supported. The default settings can be changed on the device.
diff --git a/source/_integrations/blink.markdown b/source/_integrations/blink.markdown index fef78a2318e..7bf13851502 100644 --- a/source/_integrations/blink.markdown +++ b/source/_integrations/blink.markdown @@ -50,7 +50,7 @@ Please note that each camera reports two different states: one as `sensor.blink_ ## Services -Any sequential calls to services relating to blink should have a minimum of a 5 second delay in between them to prevent the calls fro being throttled and ignored. +Any sequential calls to services relating to blink should have a minimum of a 5 second delay in between them to prevent the calls from being throttled and ignored. ### `blink.blink_update` diff --git a/source/_integrations/bme280.markdown b/source/_integrations/bme280.markdown index 7f28292c9ea..70448586ef8 100644 --- a/source/_integrations/bme280.markdown +++ b/source/_integrations/bme280.markdown @@ -68,7 +68,7 @@ oversampling_humidity: default: 1 type: integer filter_mode: - description: IIR filter coeficient as described in the sensor datasheet. + description: IIR filter coefficient as described in the sensor datasheet. required: false default: 0 type: integer diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index c6ffab8fed7..0352f91d420 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -280,7 +280,7 @@ Example values to cast [BBC Radio 1](https://www.bbc.co.uk/sounds/play/live:bbc_ This app doesn't retrieve its own metadata, so if you want the cast interface or media player card to show titles and/or images you will have to provide the data yourself. See the examples below. -Note: Media ID is NOT the 8 digit alpha-numeric in the URL, it can be found by right-clicking the playing video. E.g., [this episode](https://www.bbc.co.uk/iplayer/episode/b09w7fd9/bitz-bob-series-1-1-castle-makeover) shows: +Note: Media ID is NOT the 8 digit alphanumeric in the URL, it can be found by right-clicking the playing video. E.g., [this episode](https://www.bbc.co.uk/iplayer/episode/b09w7fd9/bitz-bob-series-1-1-castle-makeover) shows: 2908kbps | dash (mf_cloudfront_dash_https) b09w70r2 | 960x540 diff --git a/source/_integrations/cloud.markdown b/source/_integrations/cloud.markdown index 237401fc592..6b84558902b 100644 --- a/source/_integrations/cloud.markdown +++ b/source/_integrations/cloud.markdown @@ -26,7 +26,7 @@ This integration is by default enabled, unless you've disabled or removed the [` cloud: ``` -Documentation of further configuration possibilites are located at [NabuCasa](https://www.nabucasa.com/config/) +Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/) Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your `configuration.yaml` file. diff --git a/source/_integrations/cover.mqtt.markdown b/source/_integrations/cover.mqtt.markdown index 102e6d8747f..fc10d2fe405 100644 --- a/source/_integrations/cover.mqtt.markdown +++ b/source/_integrations/cover.mqtt.markdown @@ -554,7 +554,7 @@ cover: {% set tilt_value = min(max((tilt + movement), tilt_min), max) %} { - "postition": value, + "position": value, "pos": position, "tilt": tilt, "tilt_value": tilt_value, diff --git a/source/_integrations/cups.markdown b/source/_integrations/cups.markdown index 1737470792c..7c59e690003 100644 --- a/source/_integrations/cups.markdown +++ b/source/_integrations/cups.markdown @@ -12,7 +12,7 @@ ha_platforms: - sensor --- -The `cups` sensor platform is using the open source printing system [CUPS](https://www.cups.org/) to show details about your printers, including the ink levels. It can obtain the informations using a CUPS server or communicating directly with the printer with the Internet Printing Protocol. +The `cups` sensor platform is using the open source printing system [CUPS](https://www.cups.org/) to show details about your printers, including the ink levels. It can obtain the information using a CUPS server or communicating directly with the printer with the Internet Printing Protocol. ## Setup diff --git a/source/_integrations/danfoss_air.markdown b/source/_integrations/danfoss_air.markdown index c83dda15ffa..5245ca10765 100644 --- a/source/_integrations/danfoss_air.markdown +++ b/source/_integrations/danfoss_air.markdown @@ -42,7 +42,7 @@ host: The following binary sensor is supported. -- **Bypass active:** Indicator if heat recovery is currrently bypassed. +- **Bypass active:** Indicator if heat recovery is currently bypassed. ## Sensor @@ -57,7 +57,7 @@ The following sensors are supported. - **Fan step:** Fan step. - **Exhaust fan speed:** Exhausted fan speed. - **Supply fan speed:** Supply fan speed. -- **Dial battery:** Dial bettery level in percent. +- **Dial battery:** Dial battery level in percent. ## Switch diff --git a/source/_integrations/enocean.markdown b/source/_integrations/enocean.markdown index 7148ed5f27f..86b8c35a4da 100644 --- a/source/_integrations/enocean.markdown +++ b/source/_integrations/enocean.markdown @@ -145,7 +145,7 @@ sender_id: required: true type: list name: - description: An identifier for the Ligh in the frontend. + description: An identifier for the light in the frontend. required: false default: EnOcean Light type: string diff --git a/source/_integrations/envisalink.markdown b/source/_integrations/envisalink.markdown index 228d5c1dc1d..6cc1430f60c 100644 --- a/source/_integrations/envisalink.markdown +++ b/source/_integrations/envisalink.markdown @@ -21,7 +21,7 @@ Please visit the [eyezon website](http://www.eyezon.com/) for further informatio There is currently support for the following device types within Home Assistant: - Binary Sensor: Reports on zone status (Check the [type/class](/integrations/binary_sensor/#device-class) list for a possible visualization of your zone.) -- Sensor: Emulates an alpha-numeric keypad attached to the alarm panel +- Sensor: Emulates an alphanumeric keypad attached to the alarm panel - Alarm Control Panel: Reports on partition status, and can be used to arm/disarm the system This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant. diff --git a/source/_integrations/fints.markdown b/source/_integrations/fints.markdown index 23d394780ad..7dd5ac15242 100644 --- a/source/_integrations/fints.markdown +++ b/source/_integrations/fints.markdown @@ -55,7 +55,7 @@ accounts: type: list keys: account: - description: The IBAN of the blance account. + description: The IBAN of the balance account. required: true type: string name: diff --git a/source/_integrations/firmata.markdown b/source/_integrations/firmata.markdown index 6a6b14f61b9..45fff0f9c92 100644 --- a/source/_integrations/firmata.markdown +++ b/source/_integrations/firmata.markdown @@ -70,7 +70,7 @@ sleep_tune: required: false type: float sampling_interval: - description: Sampling interval in millseconds sent to Firmata. Most Firmata sketches will ignore any interval less than 10 milliseconds. + description: Sampling interval in milliseconds sent to Firmata. Most Firmata sketches will ignore any interval less than 10 milliseconds. required: false type: integer switches: diff --git a/source/_integrations/flux_led.markdown b/source/_integrations/flux_led.markdown index c5b30bb9d07..9fe9e68cf7f 100644 --- a/source/_integrations/flux_led.markdown +++ b/source/_integrations/flux_led.markdown @@ -172,7 +172,7 @@ The Flux LED light offers a number of effects which are not included in other li | `random` | Chooses a random color by selecting random values for R, G, and B. | | `custom` | Custom effect (if defined, see below). | -Users can define their own custom effect. It consists of three parameters: a list of 1 to 16 colors, speed and type of transition. The controller will transition between the colors in a loop, with sepcified transition and speed. Here is an example of a custom effect that will quickly flash red, yellow, green, cyan, blue, magenta in a loop: +Users can define their own custom effect. It consists of three parameters: a list of 1 to 16 colors, speed and type of transition. The controller will transition between the colors in a loop, with specified transition and speed. Here is an example of a custom effect that will quickly flash red, yellow, green, cyan, blue, magenta in a loop: ```yaml light: diff --git a/source/_integrations/heos.markdown b/source/_integrations/heos.markdown index 8ba06854109..8184209445c 100644 --- a/source/_integrations/heos.markdown +++ b/source/_integrations/heos.markdown @@ -84,7 +84,7 @@ media_content_id: "Awesome Music" #### Play Quick Select -You can play a HEOS Quick Select by nubmer or name with the `media_player.play_media` service. Example service data payload: +You can play a HEOS Quick Select by number or name with the `media_player.play_media` service. Example service data payload: ```yaml entity_id: media_player.office diff --git a/source/_integrations/here_travel_time.markdown b/source/_integrations/here_travel_time.markdown index b019a13aa51..5adeeb0b93f 100644 --- a/source/_integrations/here_travel_time.markdown +++ b/source/_integrations/here_travel_time.markdown @@ -21,7 +21,7 @@ You need to register for an API key (REST & XYZ HUB API/CLI) by following the in HERE offers a Freemium Plan which includes 250,000 free Transactions per month. For the Routing API, one transaction equals one request with one starting point (no multi stop). More information can be found [here](https://developer.here.com/faqs#payment-subscription) -By default HERE will deactivate your account if you exceed the free Transaction limit for the month. You can add payment details to reenable your account as described [here](https://developer.here.com/faqs) +By default HERE will deactivate your account if you exceed the free Transaction limit for the month. You can add payment details to re-enable your account as described [here](https://developer.here.com/faqs) ### Migrate from app_code to api_key diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown index 73792ffbd6b..498f3fc9e29 100644 --- a/source/_integrations/homekit.markdown +++ b/source/_integrations/homekit.markdown @@ -468,7 +468,7 @@ The following home hubs have been reported to have trouble with a large number o 1. Delete the `HomeKit` integration in the **{% my integrations %}** screen. 2. **Restart** Home Assistant. - 3. The configuration will be automaticlly reimported from YAML. + 3. The configuration will be automatically reimported from YAML. 4. [Pair the bridge or accessory](#setup). ### Resetting when created via the **Integrations** screen diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown index 1846d13772b..955bde8d262 100644 --- a/source/_integrations/homematic.markdown +++ b/source/_integrations/homematic.markdown @@ -475,11 +475,11 @@ automation: The important part is the `sensor.time` entity (from time_date component). This will update the binary sensor on every change of the sensor and every minute. If the Homematic sensor does not send any updates anymore, the `sensor.time` will set the binary sensor to `off` 10 minutes after the last sensor update. This will trigger the automation. -- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot) this is another option to call *homematic.reconnect*. Even though this option might look preferrable to many since it does not rely on a sensor, **it is less fail-safe** than checking for updates of a sensor. Since the variable on the CCU is only changed on boot, any problem that causes the connection between Home Assistant and the CCU to break but will not result in a reboot will not be detected (eg. in case of networking issues). This is how this can be done: +- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot) this is another option to call *homematic.reconnect*. Even though this option might look preferable to many since it does not rely on a sensor, **it is less fail-safe** than checking for updates of a sensor. Since the variable on the CCU is only changed on boot, any problem that causes the connection between Home Assistant and the CCU to break but will not result in a reboot will not be detected (eg. in case of networking issues). This is how this can be done: 1. Create a string variable **V_Last_Reboot** on the CCU - 2. Creata a new programm on the CCU **without any conditions**, which executes the following *HM-Script* with a delay of 30 seconds. The Script needs to be implemented within the section `Activity: Then`. + 2. Create a new program on the CCU **without any conditions**, which executes the following *HM-Script* with a delay of 30 seconds. The script needs to be implemented within the section `Activity: Then`. ```javascript var obj = dom.GetObject("V_Last_Reboot"); diff --git a/source/_integrations/hvv_departures.markdown b/source/_integrations/hvv_departures.markdown index 6a86714e9ec..8932d4d2ced 100644 --- a/source/_integrations/hvv_departures.markdown +++ b/source/_integrations/hvv_departures.markdown @@ -1,6 +1,6 @@ --- title: HVV Departures -description: Display the departures of busses, trains and ferries in Hamburg within Home Assistant. +description: Display the departures of buses, trains and ferries in Hamburg within Home Assistant. ha_category: - Transport ha_iot_class: Cloud Polling @@ -14,7 +14,7 @@ ha_platforms: - sensor --- -The `hvv_departures` sensor will display the departures of busses, trains and ferries in Hamburg. +The `hvv_departures` sensor will display the departures of buses, trains and ferries in Hamburg. {% include integrations/config_flow.md %} diff --git a/source/_integrations/hydrawise.markdown b/source/_integrations/hydrawise.markdown index 48054314774..5a0f614ba1a 100644 --- a/source/_integrations/hydrawise.markdown +++ b/source/_integrations/hydrawise.markdown @@ -73,7 +73,7 @@ monitored_conditions: {% endconfiguration %}
-The Hydrawise API removed the ability to read the rain sensor status. Therefore it is no longer suppored by the Hydrawise integration to Home Assistant. +The Hydrawise API removed the ability to read the rain sensor status. Therefore it is no longer supported by the Hydrawise integration to Home Assistant.
## Sensor diff --git a/source/_integrations/iammeter.markdown b/source/_integrations/iammeter.markdown index 77cea09b626..13ad92c7eef 100644 --- a/source/_integrations/iammeter.markdown +++ b/source/_integrations/iammeter.markdown @@ -60,7 +60,7 @@ Sensors available in the library: | wem3080_voltage | V | Voltage. | | wem3080_current | A | current. | | wem3080_power | W | active power. | -| wem3080_importenergy | kWh | Energy consumption from gird | +| wem3080_importenergy | kWh | Energy consumption from grid | | wem3080_exportgrid | kWh | Energy export to grid | ### Three-phase energy meter (WEM3080T) diff --git a/source/_integrations/iqvia.markdown b/source/_integrations/iqvia.markdown index 88669ff5d76..e7771363f15 100644 --- a/source/_integrations/iqvia.markdown +++ b/source/_integrations/iqvia.markdown @@ -17,7 +17,7 @@ The `iqvia` sensor platform collects and displays allergy, asthma and disease information (based on a U.S. ZIP code) from [IQVIA](https://www.iqvia.com/). Data measured includes: -* Indicies for allergies, asthma and cold/flu indices +* Indices for allergies, asthma and cold/flu indices * Trends * Current outlook * more! diff --git a/source/_integrations/joaoapps_join.markdown b/source/_integrations/joaoapps_join.markdown index 8cd85102102..5e836b2ed02 100644 --- a/source/_integrations/joaoapps_join.markdown +++ b/source/_integrations/joaoapps_join.markdown @@ -56,7 +56,7 @@ device_names: required: false type: string name: - description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.`. The name will defailt to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details. + description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.`. The name will default to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details. required: false type: string {% endconfiguration %} diff --git a/source/_integrations/kaiterra.markdown b/source/_integrations/kaiterra.markdown index 40161e7c8aa..7a7702f928c 100644 --- a/source/_integrations/kaiterra.markdown +++ b/source/_integrations/kaiterra.markdown @@ -15,7 +15,7 @@ ha_platforms: The `kaiterra` integration allows you to view the readings from your Laser Egg or Sensedge device using the [Kaiterra REST API](https://www.kaiterra.com/dev/). -To use the integration, you need to get the API key by signing up at [Kaiterra dashboard](https://dashboard.kaiterra.cn/), registring the device and create the key under `Settings -> Profile -> Developer`. +To use the integration, you need to get the API key by signing up at [Kaiterra dashboard](https://dashboard.kaiterra.cn/), registering the device and create the key under `Settings -> Profile -> Developer`. ## Configuration diff --git a/source/_integrations/keyboard_remote.markdown b/source/_integrations/keyboard_remote.markdown index b119368b3a8..49a193f1b26 100644 --- a/source/_integrations/keyboard_remote.markdown +++ b/source/_integrations/keyboard_remote.markdown @@ -97,7 +97,7 @@ automation: entity_id: light.all ``` -`device_descriptor` or `device_name` may be specificed in the trigger so the automation will be fired only for that keyboard. This is especially useful if you wish to use several Bluetooth remotes to control different devices. Omit them to ensure the same key triggers the automation for all keyboards/remotes. +`device_descriptor` or `device_name` may be specified in the trigger so the automation will be fired only for that keyboard. This is especially useful if you wish to use several Bluetooth remotes to control different devices. Omit them to ensure the same key triggers the automation for all keyboards/remotes. ## Disconnections diff --git a/source/_integrations/lannouncer.markdown b/source/_integrations/lannouncer.markdown index 6659329cbb4..9c7cf4b5f24 100644 --- a/source/_integrations/lannouncer.markdown +++ b/source/_integrations/lannouncer.markdown @@ -59,7 +59,7 @@ Spoken messages is the default method (`speak`). You just invoke the `notify` se } ``` -The second method is to play notifications (`alarm`). There are 4 build-in sounds (`chime`, `doorbell`, `alarm` and `siren`). +The second method is to play notifications (`alarm`). There are 4 built-in sounds (`chime`, `doorbell`, `alarm` and `siren`). ```json { diff --git a/source/_integrations/lcn.markdown b/source/_integrations/lcn.markdown index 7b165df86b2..09bc96b1ef2 100644 --- a/source/_integrations/lcn.markdown +++ b/source/_integrations/lcn.markdown @@ -627,7 +627,7 @@ data: ```
- Ensure that the LCN module is configured properly to provide acces to the defined variable. + Ensure that the LCN module is configured properly to provide access to the defined variable. Otherwise the module might show unexpected behaviors or return error messages.
diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown index a77cf71bb23..03a0f492050 100644 --- a/source/_integrations/light.markdown +++ b/source/_integrations/light.markdown @@ -22,7 +22,7 @@ profile,color_x,color_y,brightness,transition The field transition is optional and can be omitted. -The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g., for `light.ceiling_2` the `profile` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supercede the `all_lights` default setting. +The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g., for `light.ceiling_2` the `profile` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supersede the `all_lights` default setting.
diff --git a/source/_integrations/mycroft.markdown b/source/_integrations/mycroft.markdown index 5ad0a625be1..4bd8ff58b46 100644 --- a/source/_integrations/mycroft.markdown +++ b/source/_integrations/mycroft.markdown @@ -54,7 +54,7 @@ name: ## Examples -Send a mesage to Mycroft by calling `notify.mycroft` service: +Send a message to Mycroft by calling `notify.mycroft` service: ```yaml message: "Hey Mycroft. Turn on the office light. " diff --git a/source/_integrations/neato.markdown b/source/_integrations/neato.markdown index ba317ac98cb..e56db785c09 100644 --- a/source/_integrations/neato.markdown +++ b/source/_integrations/neato.markdown @@ -125,7 +125,7 @@ Some information about the capabilities might be found on the [Neato Developer P Try to restart the vacuum and wait about 5 minutes to see if it is no longer unavailable. If you are still having issues check the Neato app and make sure your robot is connected and working. If it is not then follow the steps in the app to reset your robot and give it the same name as before then restart Home Assistant. -### My robot is not deteced by Home Assistant +### My robot is not detected by Home Assistant Please check your logs if there are any warnings. When there is a message about your robot being offline, check if it is connected to the internet and available though the app. If there is a message about a bad response, try to reset this robot via your app. diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index f7080e34058..e1412846b84 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -182,7 +182,7 @@ project_id: required: false type: string subscriber_id: - description: Full path for the Pub/sub Subscription ID used to receive events. This is required to use the SDM API. Enter this exactly as it appers under "Subscription name" in the [Pub/Sub console](https://console.cloud.google.com/cloudpubsub/subscription/list). + description: Full path for the Pub/sub Subscription ID used to receive events. This is required to use the SDM API. Enter this exactly as it appears under "Subscription name" in the [Pub/Sub console](https://console.cloud.google.com/cloudpubsub/subscription/list). type: string required: false {% endconfiguration %} diff --git a/source/_integrations/nfandroidtv.markdown b/source/_integrations/nfandroidtv.markdown index ecedc42a4c3..88aadaad5d8 100644 --- a/source/_integrations/nfandroidtv.markdown +++ b/source/_integrations/nfandroidtv.markdown @@ -10,7 +10,7 @@ ha_platforms: - notify --- -Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). You can use this plarform to send notifications to your Android TV device. An overlay with the message content will appear for a configurable amount of seconds and then disapper again. Sending images (e.g., security cam) is supported too. +Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). You can use this plarform to send notifications to your Android TV device. An overlay with the message content will appear for a configurable amount of seconds and then disappear again. Sending images (e.g., security cam) is supported too. The notifications are in the global scope of your Android TV device. They will be displayed regardless of which application is running. diff --git a/source/_integrations/nilu.markdown b/source/_integrations/nilu.markdown index 5e8c1a0e1aa..3fa338d5d80 100644 --- a/source/_integrations/nilu.markdown +++ b/source/_integrations/nilu.markdown @@ -55,7 +55,7 @@ show_on_map: type: boolean {% endconfiguration %} -## Health risk index explainations +## Health risk index explanations Under the attributes from a NILU station, there will be a `nilu pollution index`. This indicates how polluted the air is in the area around the sensor station. Following is a longer explanation of what the indexes mean. @@ -75,7 +75,7 @@ Health effects may occur in asthmatics and people with other respiratory disease Sensitive groups in the population can have health effects. Respiratory irritation and discomfort may occur in healthy subjects. People with heart or respiratory distress should reduce outdoor activity and not stay in the most polluted areas. -Source: [Explainations in Norwegian](http://www.luftkvalitet.info/home/Varslingsklasser.aspx) +Source: [Explanations in Norwegian](http://www.luftkvalitet.info/home/Varslingsklasser.aspx) ## Available areas diff --git a/source/_integrations/onvif.markdown b/source/_integrations/onvif.markdown index 22ce907a248..7168d78b647 100644 --- a/source/_integrations/onvif.markdown +++ b/source/_integrations/onvif.markdown @@ -77,6 +77,6 @@ If your ONVIF camera supports PTZ, you will be able to pan, tilt or zoom your ca | `speed` | Speed coefficient. Sets how fast PTZ will be executed. Allowed values: floating point numbers, 0 to 1. Default : 0.5 | | `preset` | PTZ preset profile token. Sets the preset profile token which is executed with GotoPreset. | | `move_mode` | PTZ moving mode. Allowed values: `ContinuousMove`, `RelativeMove`, `AbsoluteMove`, `GotoPreset`, `Stop`. Default :`RelativeMove` | -| `continuous_duration` | Set ContinuousMove delay in seconds before stoping the move. Allowed values: floating point numbers or integer. Default : 0.5 | +| `continuous_duration` | Set ContinuousMove delay in seconds before stopping the move. Allowed values: floating point numbers or integer. Default : 0.5 | If you are running into trouble with this sensor, please refer to the [Troubleshooting section](/integrations/ffmpeg/#troubleshooting). diff --git a/source/_integrations/osramlightify.markdown b/source/_integrations/osramlightify.markdown index 90172db4d11..cefceeee73f 100644 --- a/source/_integrations/osramlightify.markdown +++ b/source/_integrations/osramlightify.markdown @@ -62,7 +62,7 @@ Also for sensors a list of raw values is exposed as `sensor_values` attribute, a in automations, if you know what particular values mean for your sensor. It is suggested to make [scan_interval](/docs/configuration/platform_options/#scan-interval) -(30 seconds by default) less or equal to `interval_lightify_status`, oherwise the latter won't work +(30 seconds by default) less or equal to `interval_lightify_status`, otherwise the latter won't work as expected. Shorter `scan_interval` may improve synchronization speed between individual lights and groups. For example, if you turn on a group, all its lights may be updated to `on` immediately, without querying the bridge. diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown index 455e1ecb400..b33e71dd3ab 100644 --- a/source/_integrations/plex.markdown +++ b/source/_integrations/plex.markdown @@ -57,7 +57,7 @@ Alternatively, you can manually configure a Plex server connection by selecting **Verify SSL certificate**: Verify the SSL certificate of your Plex server. May be used if connecting with an IP or if using a self-signed certificate. -**Token**: A valid authorization token for your Plex server. If provided without 'Host', a connection URL will be retreived from Plex. +**Token**: A valid authorization token for your Plex server. If provided without 'Host', a connection URL will be retrieved from Plex. ## Sensor diff --git a/source/_integrations/point.markdown b/source/_integrations/point.markdown index d18a7b7e8db..af0e199e6f1 100644 --- a/source/_integrations/point.markdown +++ b/source/_integrations/point.markdown @@ -68,7 +68,7 @@ Each home configured in the Point mobile application will show up as a separate
-The Point only supports a Arm/Disarm action, so it is only `Arm Away` that is implememented. +The Point only supports a Arm/Disarm action, so it is only `Arm Away` that is implemented.
diff --git a/source/_integrations/rejseplanen.markdown b/source/_integrations/rejseplanen.markdown index dec099121d1..471b58da69a 100644 --- a/source/_integrations/rejseplanen.markdown +++ b/source/_integrations/rejseplanen.markdown @@ -162,7 +162,7 @@ The sensor can filter the timetables by one or more routes, directions and types | `type` | Transport type | | `route` | Route code | | `direction` | Destination stop | -| `final_stop` | Final stop (if departure doesn't go all the way to the destionation stop) | +| `final_stop` | Final stop (if departure doesn't go all the way to the destination stop) | | `stop` | Departure stop | | `stop_id` | ID of departure stop | | `track` | Departure track (if available) | @@ -180,6 +180,6 @@ The sensor can filter the timetables by one or more routes, directions and types | `type` | Transport type | | `route` | Route code | | `direction` | Destination stop | -| `final_stop` | Final stop (if departure doesn't go all the way to the destionation stop) | +| `final_stop` | Final stop (if departure doesn't go all the way to the destination stop) | | `stop` | Departure stop | | `track` | Departure track (if available) | diff --git a/source/_integrations/risco.markdown b/source/_integrations/risco.markdown index ff59522dd6d..db4261fa444 100644 --- a/source/_integrations/risco.markdown +++ b/source/_integrations/risco.markdown @@ -94,7 +94,7 @@ This undoes a zone bypass. You can only unbypass a zone when the partitions it b | ---------------------- | -------- | ----------- | | `entity_id` | no | String or list of strings of entity_ids of zones. Use entity_id: all to target all zones. | -## Supported Plaforms: +## Supported Platforms: - [Alarm Control Panel](/integrations/alarm_control_panel/) - [Binary Sensor](/integrations/binary_sensor/) diff --git a/source/_integrations/roon.markdown b/source/_integrations/roon.markdown index 34f11e9ca39..7778baf681b 100644 --- a/source/_integrations/roon.markdown +++ b/source/_integrations/roon.markdown @@ -36,7 +36,7 @@ Roon uses a path based on the roon browser hierarchy to specify which media to p | -----------------------| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `entity_id` | yes | Target a specific media player. To target all media players, use `all`. | | `media_content_id` | no | A path to specify the media you want to play, see examples below. | -| `media_content_type` | no | Only `music` is suppported | +| `media_content_type` | no | Only `music` is supported | For example to play the album Harvest by Neil Young you should set `media_content_id` to `Library/Artists/Neil Young/Harvest` and to play BBC Radio 4 you would set `media_content_id` to `My Live Radio/BBC Radio 4` diff --git a/source/_integrations/satel_integra.markdown b/source/_integrations/satel_integra.markdown index 21aba110246..5e43e9075cc 100644 --- a/source/_integrations/satel_integra.markdown +++ b/source/_integrations/satel_integra.markdown @@ -27,7 +27,7 @@ The module communicates via Satel's open TCP protocol published on their website ## Setup -Please note that **ETHM-1 module is currently not supported**: it does not provide functionality used by this extension. At the moment only ETHM-1 Plus module is supported. That might change in the future, but no promisses are given. +Please note that **ETHM-1 module is currently not supported**: it does not provide functionality used by this extension. At the moment only ETHM-1 Plus module is supported. That might change in the future, but no promises are given. The library currently doesn't support encrypted connection to your alarm, so you need **to turn off encryption for integration protocol**. In Polish: "koduj integracje" must be unchecked. You will find this setting in your DloadX program. diff --git a/source/_integrations/sensehat.markdown b/source/_integrations/sensehat.markdown index f2adbcc264c..6f7a303f250 100644 --- a/source/_integrations/sensehat.markdown +++ b/source/_integrations/sensehat.markdown @@ -60,7 +60,7 @@ display_options: pressure: description: Pressure name: - description: Change the name of te sensor, for in the frontend. + description: Change the name of the sensor, for in the frontend. required: false type: string is_hat_attached: diff --git a/source/_integrations/sma.markdown b/source/_integrations/sma.markdown index 2d49261db2f..f57ebda9534 100644 --- a/source/_integrations/sma.markdown +++ b/source/_integrations/sma.markdown @@ -98,7 +98,7 @@ The SMA WebConnect module supports a wide variety of sensors, but not all of the | power_l2 | W | Power for phase 2 | | power_l3 | W | Power for phase 3 | -### Batery Inverter +### Battery Inverter | name | Unit | Description | | --- | --- | --- | diff --git a/source/_integrations/smarthab.markdown b/source/_integrations/smarthab.markdown index a915b374f31..2c1df153afe 100644 --- a/source/_integrations/smarthab.markdown +++ b/source/_integrations/smarthab.markdown @@ -27,5 +27,5 @@ Assistant. To prevent being automatically logged out of your SmartHab mobile app, you might want to create a secondary user in the app's settings and grant it access to your home. You can then configure the integration using this account's - credentials. This is also more secure, as this user should be less priviledged. + credentials. This is also more secure, as this user should be less privileged.
diff --git a/source/_integrations/synology_dsm.markdown b/source/_integrations/synology_dsm.markdown index ee9bcff7a68..ca0dc7a18a5 100644 --- a/source/_integrations/synology_dsm.markdown +++ b/source/_integrations/synology_dsm.markdown @@ -28,7 +28,7 @@ The Synology DSM sensor platform provides access to various statistics from your This sensor will wake up your Synology NAS if it's in hibernation mode. -You can change the scan interal within the configuration options (default is 15 min). +You can change the scan interval within the configuration options (default is 15 min). Having cameras or the Home mode toggle from [Surveillance Station](https://www.synology.com/en-us/surveillance) will fetch every 30 seconds. Disable those entities if you don't want your NAS to be fetch as frequently. diff --git a/source/_integrations/tado.markdown b/source/_integrations/tado.markdown index 169f076aebf..d33d93db612 100644 --- a/source/_integrations/tado.markdown +++ b/source/_integrations/tado.markdown @@ -140,7 +140,7 @@ You can use the service `tado.set_water_heater_timer` to set your water heater t ### Service `tado.set_climate_temperature_offset` -You can use the service `tado.set_climate_temperature_offset` to set the temprature offset for Tado climate devices +You can use the service `tado.set_climate_temperature_offset` to set the temperature offset for Tado climate devices. | Service data attribute | Optional | Description | | ---------------------- | -------- | ---------------------------------------------------------------------- | @@ -170,7 +170,7 @@ script: {% raw %} ```yaml -# Example automation to set temprature offset based on another thermostat value +# Example automation to set temperature offset based on another thermostat value automation: # Trigger if the state of either thermostat changes trigger: diff --git a/source/_integrations/traccar.markdown b/source/_integrations/traccar.markdown index d421164b881..d3d571bf202 100644 --- a/source/_integrations/traccar.markdown +++ b/source/_integrations/traccar.markdown @@ -70,7 +70,7 @@ max_accuracy: type: integer default: 0 skip_accuracy_filter_on: - description: Skip filter position by "max_accuracy filter" if any of specified attributes are pressent on the traccar message. + description: Skip filter position by "max_accuracy filter" if any of specified attributes are present on the traccar message. required: false type: list monitored_conditions: diff --git a/source/_integrations/weather.template.markdown b/source/_integrations/weather.template.markdown index 50235f8b044..295485397b6 100644 --- a/source/_integrations/weather.template.markdown +++ b/source/_integrations/weather.template.markdown @@ -13,7 +13,7 @@ The `template` integrations creates weather provider that combines integrations There are several powerful ways to use this integration, including localizing your weather provider information with local information from temperature, humidity, pressure sensors that you own. -Another use case could be using temperature and humidity from one weather plaform, with forecasts from a different one. +Another use case could be using temperature and humidity from one weather platform, with forecasts from a different one. ## Configuration diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index 05739174f99..09260d7bde8 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -54,7 +54,7 @@ Please read the linked sections for those devices for more information. It is recommend to supply your Xiaomi cloud credentials during configuration to automatically connect to your devices. You need to specify the cloud server -you used in the Xiaomi Home App (where you initialy setup the device). There are +you used in the Xiaomi Home App (where you initially setup the device). There are 6 servers: `cn`, `de`, `i2`, `ru`, `sg` and `us`; please see [this page](https://www.openhab.org/addons/bindings/miio/#country-servers) for the server to use for each country. @@ -1244,7 +1244,7 @@ Allowed `params` for the `reset_consumable` command: [RRCC](https://github.com/LazyT/rrcc) supports both rooted and non-rooted Vacuums and acts as a mostly fully featured replacement for Mi Home that works locally without the cloud. If you have installed the rooted firmware [Valetudo](https://github.com/Hypfer/Valetudo) you are able to SSH into your Vacuum and enable MQTT plus use map functions with no cloud requirement. -Using the map editor you are able to acquire the co-ordinates required for zoned clean up. Here is an example script for zoned clean up: +Using the map editor you are able to acquire the coordinates required for zoned clean up. Here is an example script for zoned clean up: ```yaml vacuum_kitchen: @@ -1269,7 +1269,7 @@ miiocli vacuum --ip --token get_room_mapp It will return the full mapping of room numbers to user-defined names as a list of (number,name) tuples. Alternatively, one can just test the clean_segment service with a number and see which room it cleans. -It seems to be the case that Numbers 1..15 are used to number the intitial segmentation done by the vacuum cleaner itself. Numbers 16 and upwards numbers rooms from the users manual editing. +It seems to be the case that Numbers 1..15 are used to number the initial segmentation done by the vacuum cleaner itself. Numbers 16 and upwards numbers rooms from the users manual editing. ## Xiaomi Philips Light diff --git a/source/_integrations/xmpp.markdown b/source/_integrations/xmpp.markdown index 84e847e0a94..f5d8b955c67 100644 --- a/source/_integrations/xmpp.markdown +++ b/source/_integrations/xmpp.markdown @@ -204,6 +204,6 @@ Number 6 sends an image from a templated URL. {% endraw %} -The possible source of a file is prioritized and only one will be picked up. `url_template` has the hightest priority; next is `url` then `path_template` and finally if none of them are defined `path` would be used. `path` will be used to eliminate file extension guessing for unknown URL downloads. Only the file extension will be left, as Home Assistant changes the filename to a random string for added privacy. +The possible source of a file is prioritized and only one will be picked up. `url_template` has the highest priority; next is `url` then `path_template` and finally if none of them are defined `path` would be used. `path` will be used to eliminate file extension guessing for unknown URL downloads. Only the file extension will be left, as Home Assistant changes the filename to a random string for added privacy. To find out more about notifications, please see the [getting started with automation page](/getting-started/automation/). diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 7f03fc798da..7dbaa6f43ac 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -339,7 +339,7 @@ To help resolve any kinks or compatibility problems, report bugs as issues with There is no official compatibility list of supported devices for the simple reason that practically all devices Zigbee Home Automation that are fully compliant with the standards and specifications as set by the [Zigbee Alliance](https://zigbeealliance.org) should technically be compatible with this ZHA integration. The fact remains, however, that some hardware manufacturers do not always fully comply with each set specification, which can cause a few devices to only partially work or not work at all with ZHA, but developers can create workarounds for such issues via a solution for 'ZHA exception and deviation handling' that this implementation features. See that section for more information. -Tip to new users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub softwares, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate. +Tip to new users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub software, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate. ### ZHA exception and deviation handling diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index 3641ba228d0..e7a955f1930 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -613,7 +613,7 @@ Z-Wave JS keeps a database of all devices it supports, including any special tre ### I get a lot of sensor entities for my device that I'm probably never going to use -The integration will add as many useable entities for you as possible from the information it retrieves from your Z-Wave devices. Entities that you don't want/like, can be disabled within the Home Assistant interface. +The integration will add as many usable entities for you as possible from the information it retrieves from your Z-Wave devices. Entities that you don't want/like, can be disabled within the Home Assistant interface. ### I renamed my devices in Z-Wave JS 2 MQTT but those names are not visible in Home Assistant diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown index 9c2aa22eb1b..b8fb0de1f50 100644 --- a/source/help/reporting_issues.markdown +++ b/source/help/reporting_issues.markdown @@ -48,7 +48,7 @@ Make sure that you don't post your username, password, API key, access token or ### Traceback (if applicable) -If things go wrong there will be a so-called traceback or an error message in other words in your log. Please include this. It starts with **Traceback** and can contain informations where the error was triggered in the code. +If things go wrong there will be a so-called traceback or an error message in other words in your log. Please include this. It starts with **Traceback** and can contain information where the error was triggered in the code. ```bash Traceback (most recent call last):