jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Spelling fixes (#9942)

Browse Source
This commit is contained in:
Ville Skyttä 2019-07-22 00:55:32 +03:00 committed by Franck Nijhof
parent a29fab9f87
commit 73de39add0
26 changed files with 49 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_components/cover.mqtt.markdown
View File

@ -13,9 +13,9 @@ The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a
## Configuration
The device state (`open` or `closed`) will be updated only after a new message is published on `state_topic` matching `state_open` or `state_closed`. If these messages are published with the `retain` flag set, the cover will receive an instant state update after subscription and Home Assistant will display the correct state on startup. Otherwise, the initial state displayed in Home Assistant will be `unknown`.
`state_topic` can only manage `state_open` and `state_closed`. No percentage positons etc.
`state_topic` can only manage `state_open` and `state_closed`. No percentage positions etc.
For this purpose is `position_topic` which can set state of the cover and positon.
For this purpose is `position_topic` which can set state of the cover and position.
Default setting are 0 means the device is `closed` and all other intermediate positions means the device is `open`.
`position_topic` is managed by `position_open` and `position_closed`
You can set it up in opossite way as well.

2
source/_components/cups.markdown
View File

@ -15,7 +15,7 @@ The `cups` sensor platform is using the open source printing system [CUPS](https
## Setup
You will need to install the `python3-dev` or `python3-devel` pacakge and the development files for CUPS (`libcups2-dev` or`cups-devel`) on your system manually (e.g., `sudo apt-get install python3-dev libcups2-dev` or `sudo dnf -y install python3-devel cups-devel`) along with a compiler (`gcc`). This integration doesn't work out-of-the-box in a container-based setup.
You will need to install the `python3-dev` or `python3-devel` package and the development files for CUPS (`libcups2-dev` or`cups-devel`) on your system manually (e.g., `sudo apt-get install python3-dev libcups2-dev` or `sudo dnf -y install python3-devel cups-devel`) along with a compiler (`gcc`). This integration doesn't work out-of-the-box in a container-based setup.
To set up the sensor the "Queue Name" of the printer is needed. The fastest way to get it, is to visit the CUPS web interface at "http://[IP ADDRESS PRINT SERVER]:631" and go to "Printers".

2
source/_components/danfoss_air.markdown
View File

@ -52,7 +52,7 @@ The following sensors are supported.
- **Supply temperature:** Air temperature of the air supplied to the house.
- **Extract temperature:** Air temperature of the air extracted from the house.
- **Exhaust temperature:** Exhausted air temperature.
- **Remaining filter lifetime:** Reamining filter lifetime measured in percent.
- **Remaining filter lifetime:** Remaining filter lifetime measured in percent.
## Switch

2
source/_components/discord.markdown
View File

@ -13,7 +13,7 @@ The [Discord service](https://discordapp.com/) is a platform for the notify comp
In order to get a token you need to go to the [Discord My Apps page](https://discordapp.com/developers/applications/me) and create a new application. Once the application is ready, create a [bot](https://discordapp.com/developers/docs/topics/oauth2#bots) user (**Create a Bot User**).
Retreive the **Client ID** from the information section and the (hidden) **Token** of your bot for later.
Retrieve the **Client ID** from the information section and the (hidden) **Token** of your bot for later.
When setting up the application you can use this [icon](/images/favicon-192x192-full.png).

2
source/_components/ebusd.markdown
View File

@ -107,7 +107,7 @@ monitored_conditions:
Zone1OperativeMode:
description: Heating circuit operative mode (on/off/day/night).
ContinuosHeating:
description: Continuos heating.
description: Continuous heating.
PowerEnergyConsumptionLastMonth:
description: Power energy consumption from last month.
PowerEnergyConsumptionThisMonth:

36
source/_components/elkm1.markdown
View File

@ -75,12 +75,12 @@ area:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -96,12 +96,12 @@ counter:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -117,12 +117,12 @@ keypad:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -138,12 +138,12 @@ output:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -159,12 +159,12 @@ setting:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -180,12 +180,12 @@ task:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -201,12 +201,12 @@ thermostat:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -222,12 +222,12 @@ plc:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.
@ -243,12 +243,12 @@ zone:
required: false
default: true
include:
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a postive integer or a X10 housecode. See configuration below for examples of ranges.
description: List to include in the form of either `<value>` or `<value>-<value>` where `<value>` is a positive integer or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: All included.
exclude:
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or a X10 housecode. See configuration below for examples of ranges.
description: List to exclude in the form of either `<value>` or `<value>-<value>` where `<value>` is a number or an X10 housecode. See configuration below for examples of ranges.
type: list
required: false
default: None excluded.

2
source/_components/entur_public_transport.markdown
View File

@ -129,4 +129,4 @@ The stop id is the content after `id=` parameter in the url. Copy paste this int
**Q:** Where do I find a line id to add to the whitelisting?
**A:** The sensor will show the line id, and is the recommended way to find it, while we wait for 'Nasjonalt Stoppestedregister' to become public. It is also possible to see the line ids by using the developer tool in the browser while looking at the trafic in [Entur's travel planer](https://en-tur.no).
**A:** The sensor will show the line id, and is the recommended way to find it, while we wait for 'Nasjonalt Stoppestedregister' to become public. It is also possible to see the line ids by using the developer tool in the browser while looking at the traffic in [Entur's travel planer](https://en-tur.no).

2
source/_components/freebox.markdown
View File

@ -60,7 +60,7 @@ authorize it by pressing the right arrow on the facade of the Freebox when
prompted to do so.
To make the WiFi switch working you will have to add "Modification des réglages de la Freebox
" permission to Home Assitant application in "Paramètres de la Freebox" > "Gestion des accès" > "Applications".
" permission to Home Assistant application in "Paramètres de la Freebox" > "Gestion des accès" > "Applications".
### Supported routers

2
source/_components/google_assistant.markdown
View File

@ -248,7 +248,7 @@ The request_sync service may fail with a 404 if the project_id of the Homegraph
4. Generate a new API key.
5. Again, create a new project in the [Actions on Google console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`.
Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is techincally in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again.
Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again.
### Troubleshooting with NGINX

2
source/_components/gtt.markdown
View File

@ -28,7 +28,7 @@ stop:
required: true
type: string
bus_name:
description: The name of the choosen bus.
description: The name of the chosen bus.
required: false
type: string
{% endconfiguration %}

6
source/_components/heos.markdown
View File

@ -41,7 +41,7 @@ A connection to a single device enables control for all devices on the network.
### Service `heos.sign_in`
Use the sign-in service to sign the connected controller into a HEOS account so that it can retreive and play HEOS favorites and playlists. An error message is logged if sign-in is unsuccessful. Example service data payload:
Use the sign-in service to sign the connected controller into a HEOS account so that it can retrieve and play HEOS favorites and playlists. An error message is logged if sign-in is unsuccessful. Example service data payload:
```json
{
@ -142,7 +142,7 @@ You can play a URL through a HEOS media player using the `media_player.play_medi
### Debugging
The HEOS integration will log additional information about commands, events, and other messages when the log level is set to `debug`. Add the the relevent line below to the `configuration.yaml` to enable debug logging:
The HEOS integration will log additional information about commands, events, and other messages when the log level is set to `debug`. Add the the relevant line below to the `configuration.yaml` to enable debug logging:
```yaml
logger:
@ -157,4 +157,4 @@ logger:
If the HEOS controller is not signed in to a HEOS account, HEOS favorites will not be populated in the media player source selection and the service `media_player.play_media` for `favorite` and `playlist` will fail. Additionally, the following warning will be logged at startup:
> IP_ADDRESS is not logged in to a HEOS account and will be unable to retrieve HEOS favorites: Use the 'heos.sign_in' service to sign-in to a HEOS account
To resolve this issue, use the `heos.sign_out` service to sign the controller into an account as documented above. This only needs to be performed once, as the controller will remain signed in while the account credentails are valid.
To resolve this issue, use the `heos.sign_out` service to sign the controller into an account as documented above. This only needs to be performed once, as the controller will remain signed in while the account credentials are valid.

2
source/_components/hlk_sw16.markdown
View File

@ -76,7 +76,7 @@ deviceid:
type: map
keys:
relayid:
description: The array that contains the HLK-SW16 relays, each must be a number between 0 and 9 or letter between a and f which each corresponds to a labled relay switch on the HLK-SW16.
description: The array that contains the HLK-SW16 relays, each must be a number between 0 and 9 or letter between a and f which each corresponds to a labeled relay switch on the HLK-SW16.
required: false
type: map
keys:

6
source/_components/lcn.markdown
View File

@ -127,7 +127,7 @@ connections:
required: true
type: string
name:
description: Optional connection identifier. If omited, the connections will be named consecutively as _pchk_, _pchk1_, _pchk2_, ...
description: Optional connection identifier. If omitted, the connections will be named consecutively as _pchk_, _pchk1_, _pchk2_, ...
required: false
default: pchk
type: string
@ -423,7 +423,7 @@ If the control is set lockable, the regulator can be turned on/off.
<div class='note'>
If you intend to leave the regulation to home assistant, you should consider using the [Generic Thermostat](/components/generic_thermostat/) in conjuction with [LCN Sensor](#sensor) and [LCN Switch](#switch).
If you intend to leave the regulation to home assistant, you should consider using the [Generic Thermostat](/components/generic_thermostat/) in conjunction with [LCN Sensor](#sensor) and [LCN Switch](#switch).
</div>
@ -488,7 +488,7 @@ Example:
```yaml
service: output_abs
data:
addres: myhome.0.7
address: myhome.0.7
output: output1
brightness: 100
transition: 0

2
source/_components/mhz19.markdown
View File

@ -60,4 +60,4 @@ Then (after a reboot): you can setup the sensor using:
## Calibration
The MH-Z19B version of the sensor has Automatic Baseline Calibration enabled by default, which will calibrate the 400PPM level to the lowest measured PPM in the last 24h cycle. Currently the integration does not allow turning this functionaly off.
The MH-Z19B version of the sensor has Automatic Baseline Calibration enabled by default, which will calibrate the 400PPM level to the lowest measured PPM in the last 24h cycle. Currently the integration does not allow turning this functionality off.

2
source/_components/nilu.markdown
View File

@ -59,7 +59,7 @@ Under the attributes from a NILU station, there will be a `nilu pollution index`
### Low
Low or no health risk linked to measured air pollution. Outdoor activites are recommended.
Low or no health risk linked to measured air pollution. Outdoor activities are recommended.
### Moderate

2
source/_components/nissan_leaf.markdown
View File

@ -44,7 +44,7 @@ region:
required: true
type: string
nissan_connect:
description: If your car has the updated head unit (NissanConnect rather than Carwings) then the location can be aquired and exposed via a device tracker. If you have Carwings then this should be set to false. The easiest way to identify NissanConnect is if the T&C buttons are orange and blue, for CarWings they're both blue, or just look for anything saying "CarWings" in Settings area of the infotainment system.
description: If your car has the updated head unit (NissanConnect rather than Carwings) then the location can be acquired and exposed via a device tracker. If you have Carwings then this should be set to false. The easiest way to identify NissanConnect is if the T&C buttons are orange and blue, for CarWings they're both blue, or just look for anything saying "CarWings" in Settings area of the infotainment system.
required: false
type: boolean
default: true

2
source/_components/orangepi_gpio.markdown
View File

@ -64,7 +64,7 @@ As this platform supports different types of GPIO pinouts for difference Orange
| `neocore2` | Supports the NanoPi Neocore 2 |
## Additional steps
This integration uses the `SYSFS` filesystem to get control of the GPIOs. Therefore an operatings system with `CONFIG_GPIO_SYSFS` is required. As far as I know, most out-of-the-box distributions still enable this by default.
This integration uses the `SYSFS` filesystem to get control of the GPIOs. Therefore an operating system with `CONFIG_GPIO_SYSFS` is required. As far as I know, most out-of-the-box distributions still enable this by default.
As of Linux 4.8 sysfs-gpio is marked as obsolete. However as of today, the alternative GPIO character device is not widely used. Therefore we will use this until the new character device is more widely supported.

2
source/_components/point.markdown
View File

@ -86,7 +86,7 @@ Each Point exposes the following binary sensors:
<div class="note">
The binary sensors **button_press**, **sound** and **tamper** are switched `On` for a breif moment and are then switched back to `Off`.
The binary sensors **button_press**, **sound** and **tamper** are switched `On` for a brief moment and are then switched back to `Off`.
</div>

4
source/_components/ps4.markdown
View File

@ -116,11 +116,11 @@ Some titles will have different SKUs in the PlayStation Store database depending
| Available Regions | Unavailable Regions |
| --------------------------------------------------------------------------- | -------------------------- |
| Argentina, Australia, Austria, Bahrain, Belgium, Brazil, Bulgaria, | China, Japan, Phillipines, |
| Argentina, Australia, Austria, Bahrain, Belgium, Brazil, Bulgaria, | China, Japan, Philippines, |
| Canada, Chile, Columbia, Costa Rica, Croatia, Cyprus, Czech Republic, | Serbia, Ukraine, Vietnam |
| Denmark, Ecuador, El Salvador, Finland, France, Germany, Greece, Guatemala, | |
| Honduras, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, | |
| Italy, Korea, Kuwait, Lebanon, Luxembourg, Malta, Maylasia, Mexico, | |
| Italy, Korea, Kuwait, Lebanon, Luxembourg, Malta, Malaysia, Mexico, | |
| Middle East, Nederland, New Zealand, Nicaragua, Norway, Oman, Panama, | |
| Peru, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Singapore, | |
| Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, | |

2
source/_components/ptvsd.markdown
View File

@ -40,7 +40,7 @@ wait:
### Security
Ensure if this is a public-facing server, that the port is secured. Anyone who is able to access the debugger port can *execute arbitary code* on the home assistant server, which is very unsafe.
Ensure if this is a public-facing server, that the port is secured. Anyone who is able to access the debugger port can *execute arbitrary code* on the home assistant server, which is very unsafe.
If the home assistant server is behind your firewall with only the http(s) port exposed, then this is safe from outside connections.

2
source/_components/scrape.markdown
View File

@ -165,7 +165,7 @@ sensor:
### BOM Weather
The Australian Bureau of Meterology website returns an error if the User Agent header is not sent.
The Australian Bureau of Meteorology website returns an error if the User Agent header is not sent.
{% raw %}
```yaml

2
source/_components/smartthings.markdown
View File

@ -345,7 +345,7 @@ If you have completed the checklist above and are still unable to setup the plat
### Debugging
The SmartThings integration will log additional information about push updates received, events fired, and other messages when the log level is set to `debug`. Add the the relevent line below to the `configuration.yaml`:
The SmartThings integration will log additional information about push updates received, events fired, and other messages when the log level is set to `debug`. Add the the relevant line below to the `configuration.yaml`:
```yaml
logger:

2
source/_components/switcher_kis.markdown
View File

@ -26,7 +26,7 @@ To retrieve your device's details, please follow the instructions [here](https:/
<div class='note warning'>
Please note, on the original script repository, users recently reported difficulties controling the device after upgrading the firmware to the new 3.0 version.As this integration is based on that script, please do not upgrade to version 3.0 until this issue is resolved. You can follow the issue [here](https://github.com/NightRang3r/Switcher-V2-Python/issues/3).
Please note, on the original script repository, users recently reported difficulties controlling the device after upgrading the firmware to the new 3.0 version.As this integration is based on that script, please do not upgrade to version 3.0 until this issue is resolved. You can follow the issue [here](https://github.com/NightRang3r/Switcher-V2-Python/issues/3).
</div>
```yaml

2
source/_components/tensorflow.markdown
View File

@ -36,7 +36,7 @@ This integration requires files to be downloaded, compiled on your computer, and
|- __init__.py
```
- Copy required object_detection dependancies to the `object_detection` folder inside of the `tensorflow` folder:
- Copy required object_detection dependencies to the `object_detection` folder inside of the `tensorflow` folder:
- `research/object_detection/data`
- `research/object_detection/utils`

2
source/_components/traccar.markdown
View File

@ -63,7 +63,7 @@ max_accuracy:
type: integer
default: 0
skip_accuracy_filter_on:
description: Skip filter positon 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 pressent on the traccar message.
required: false
type: list
monitored_conditions:

2
source/_components/utility_meter.markdown
View File

@ -101,7 +101,7 @@ This service must be called by the user for the tariff switching logic to occur
The following configuration shows an example where 2 utility_meters (`daily_energy` and `monthly_energy`) track daily and monthly energy consumptions.
Both track the same sensor (`sensor.energy`) which continously monitors the energy consumed.
Both track the same sensor (`sensor.energy`) which continuously monitors the energy consumed.
4 different sensors will be created, 2 per utility meter and corresponding to each tariff.
Sensor `sensor.daily_energy_peak`, `sensor.daily_energy_offpeak`, `sensor.monthly_energy_peak` and `sensor.monthly_energy_offpeak` will automatically be created to track the consumption in each tariff for the given cycle.