Skip to content

Commit 3f1972b

Browse files
flowolffabaff
flowolf
authored and
fabaff
committed
fixed typos, spelling mistakes (home-assistant#3436)
1 parent 9d94f28 commit 3f1972b

File tree

139 files changed

+209
-209
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

139 files changed

+209
-209
lines changed

‎source/_components/alarm_control_panel.egardia.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Configuration variables:
4141
Note that this basic configuration will only enable you to read the armed/armed away/disarmed status of your alarm and will **not** update the status if the alarm is triggered. This is because of how Egardia built their system. The alarm triggers normally go through their servers.
4242
You can change this, however, using the following procedure. This is a more advanced configuration.
4343

44-
1. Log in into your alarm system's control panel. You will need to access http://[ip of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
44+
1. Log in into your alarm system's control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
4545
2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. Also, update the port number 85 or to anything you like. The provided software that you will set up in the next steps runs on port 85 by default. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'.
4646
3. On your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, armhome) as well as trigger the alarm in all ways possible to get 100% coverage. **Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
4747
4. Once you have the codes, update your `configuration.yaml`:

‎source/_components/alert.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ freshwater_temp_alert:
7575

7676
### {% linkable_title Complex Alert Criteria %}
7777

78-
By design, the `alert` component only handles very simple criteria for firing. That is, it only checks if a single entity's state is equal to a value. At some point, it may be desireable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a `Template Binary Sensor`. The following example does that.
78+
By design, the `alert` component only handles very simple criteria for firing. That is, it only checks if a single entity's state is equal to a value. At some point, it may be desirable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a `Template Binary Sensor`. The following example does that.
7979

8080
```yaml
8181
binary_sensor:
@@ -99,7 +99,7 @@ This example will begin firing as soon as the entity `sensor.motion`'s `battery`
9999

100100
### {% linkable_title Dynamic Notification Delay Times %}
101101

102-
It may be desireable to have the delays between alert notifications dynamically change as the alert continues to fire. This can be done by setting the `repeat` configuration key to a list of numbers rather than a single number. Altering the first example would look like the following.
102+
It may be desirable to have the delays between alert notifications dynamically change as the alert continues to fire. This can be done by setting the `repeat` configuration key to a list of numbers rather than a single number. Altering the first example would look like the following.
103103

104104
```yaml
105105
# Example configuration.yaml entry

‎source/_components/alexa.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The built-in Alexa component allows you to integrate Home Assistant into Alexa/A
3333

3434
### {% linkable_title Requirements %}
3535

36-
Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. When running Hass.io, using the [Let's Encrypt](/addons/lets_encrypt/) the and [Duck DNS](/addons/duckdns/) add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using [this AWS Lambda proxy for Alexa skills](https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230).
36+
Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are OK because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. When running Hass.io, using the [Let's Encrypt](/addons/lets_encrypt/) the and [Duck DNS](/addons/duckdns/) add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using [this AWS Lambda proxy for Alexa skills](https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230).
3737

3838
Additionally, note that at the time of this writing, your Alexa skill endpoint *must* accept requests over port 443 (Home Assistant default to 8123). There are two ways you can handle this:
3939

@@ -295,7 +295,7 @@ alexa:
295295
{% endif %}{% endraw %}
296296
```
297297

298-
You can add multiple items for a feed if you want. The Amazon required uid and timestamp will be randomly generated at startup and change at every restart of Home Assistant.
298+
You can add multiple items for a feed if you want. The Amazon required UID and timestamp will be randomly generated at startup and change at every restart of Home Assistant.
299299

300300
Please refer to the [Amazon documentation][flash-briefing-api-docs] for more information about allowed configuration parameters and formats.
301301

‎source/_components/binary_sensor.bayesian.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Configuration variables:
4141
- **prob_given_true** (*Required*): The probability of the observation occurring, given the event is `true`.
4242
- **prob_given_false** (*Optional*): The probability of the observation occurring, given the event is `false` can be set as well. If `prob_given_false` is not set, it will default to `1 - prob_given_true`.
4343
- **platform** (*Required*): The only supported observation platforms are `state` and `numeric_state`, which are modeled after their corresponding triggers for automations.
44-
- **to_state** (*Required*): THe target start.
44+
- **to_state** (*Required*): The target start.
4545
- **probability_threshold** (*Optional*): The probability at which the sensor should trigger to `on`.
4646
- **name** (*Optional*): Name of the sensor to use in the frontend. Defaults to `Bayesian Binary`.
4747

‎source/_components/binary_sensor.enocean.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Configuration variables:
3030
- **name** (*Optional*): An identifier for the switch in the frontend.
3131
- **device_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
3232
33-
EnOcean binary sensors only generate 'button_pressed' events. The event data has follwing four fields:
33+
EnOcean binary sensors only generate 'button_pressed' events. The event data has following four fields:
3434
3535
- **id**: The ID of the device (see configuration).
3636
- **pushed**: `1` for a button press, `0` for a button release.

‎source/_components/binary_sensor.flic.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ automation:
6262
Event data:
6363

6464
- **button_name**: The name of the button, that triggered the event.
65-
- **button_address**: The bluetooth address of the button, that triggered the event.
65+
- **button_address**: The Bluetooth address of the button, that triggered the event.
6666
- **click_type**: The type of click. Possible values are `single`, `double` and `hold`.
6767
- **queued_time**: The amount of time this event was queued on the button, in seconds.
6868

‎source/_components/binary_sensor.hikvision.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ binary_sensor.front_porch_motion
2424
binary_sensor.front_port_line_crossing
2525
```
2626

27-
When used with a NVR device the sensors will be appeneded with the channel number they represent. For example, if you configure an NVR with the name "Home" that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:
27+
When used with a NVR device the sensors will be appended with the channel number they represent. For example, if you configure an NVR with the name "Home" that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:
2828

2929
```
3030
binary_sensor.home_motion_1

‎source/_components/binary_sensor.mqtt.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Configuration variables:
3535
- **device_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
3636
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
3737
38-
For a quick check you can use the commandline tools shipped with `mosquitto` to send MQTT messages. Set the state of a sensor manually:
38+
For a quick check you can use the command line tools shipped with `mosquitto` to send MQTT messages. Set the state of a sensor manually:
3939

4040
```bash
4141
$ mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m "OFF"

‎source/_components/binary_sensor.mystrom.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ binary_sensor:
4040
4141
You need to configure every button to make it work with Home Assistant. First connect the Wifi Buttons to your wireless network. Keep in mind that they only support WPS (Wi-FI Protected Setup). Once a button is connected you have three minutes to set the actions for the push patterns. The fastest way is to use `curl`. Check the [documentation](https://mystrom.ch/wp-content/uploads/REST_API_WBP.txt) of the WiFi Button for further details about the implementation (`http://` is replaced by `get://` or `post://`). `action` is the name of the corresponding push pattern (see above).
4242

43-
The endpoint that is recieving the data is `[IP address Home Assistant]:8123/api/mystrom`.
43+
The endpoint that is receiving the data is `[IP address Home Assistant]:8123/api/mystrom`.
4444

4545
```bash
4646
$ curl -d "[action]=get://[IP address Home Assistant]:8123/api/mystrom?[action]%3D[ID of the button]" http://[IP address of the button]/api/v1/device/[MAC address of the button]

‎source/_components/binary_sensor.pilight.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ha_release: 0.44
1313
ha_iot_class: "Local Polling"
1414
---
1515

16-
The `pilight` binary sensor platform implement the [pilight hub](/components/pilight/) binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happend (for example lots of cheap PIR motion detector).
16+
The `pilight` binary sensor platform implement the [pilight hub](/components/pilight/) binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happened (for example lots of cheap PIR motion detector).
1717

1818
To enable a Pilight binary sensor in your installation, add the following to your `configuration.yaml` file:
1919

‎source/_components/binary_sensor.rfxtrx.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ binary_sensor:
2525
automatic_add: True
2626
```
2727
28-
Open your local home-assistant web UI and go to the "states" page. Then make sure to trigger your sensor. You should see a new entity appear in the *Current entites* list, starting with "binary_sensor." and some hexadecimal digits. Those hexadecimal digits are your device id.
28+
Open your local home-assistant web UI and go to the "states" page. Then make sure to trigger your sensor. You should see a new entity appear in the *Current entities* list, starting with "binary_sensor." and some hexadecimal digits. Those hexadecimal digits are your device id.
2929
3030
For example: "binary_sensor.0913000022670e013b70". Here your device id is `0913000022670e013b70`. Then you should update your configuration to:
3131

@@ -70,7 +70,7 @@ binary_sensor:
7070

7171
## Options for PT-2262 devices under the Lighting4 protocol
7272

73-
When a data packet is transmitted by a PT-2262 device using the Lighting4 protocol, there is no way to automatically extract the device identifier and the command from the packet. Each device has its own id/command length combination and the fields lengths are not included in the data. One device that sends 2 different commands will be seen as 2 devices on Home Assistant. For sur cases, the following options are available in order to circumvent the problem:
73+
When a data packet is transmitted by a PT-2262 device using the Lighting4 protocol, there is no way to automatically extract the device identifier and the command from the packet. Each device has its own id/command length combination and the fields lengths are not included in the data. One device that sends 2 different commands will be seen as 2 devices on Home Assistant. For such cases, the following options are available in order to circumvent the problem:
7474

7575
- **data_bits** (*Optional*): Defines how many bits are used for commands inside the data packets sent by the device.
7676
- **command_on** (*Optional*): Defines the data bits value that is sent by the device upon an 'On' command.

‎source/_components/binary_sensor.ring.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,6 @@ Configuration variables:
2929
3030
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
3131
- **ding**: Return a boolean value when the doorbell button was pressed.
32-
- **motion**: Return a boolean value when a moviment was detected by the Ring doorbell.
32+
- **motion**: Return a boolean value when a movement was detected by the Ring doorbell.
3333
3434
Currently only doorbells are supported by this sensor.

‎source/_components/binary_sensor.velbus.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,6 @@ Configuration variables:
3737
- **name** (*Required*): Name of the binary sensor.
3838
- **module** (*Required*): The hexadecimal module address
3939
- **channel** (*Required*): The channel number in the module.
40-
- **is_pushbutton** (*Optional*): Booelan to indicate if a wall switch is a push button or not (default: false)
40+
- **is_pushbutton** (*Optional*): Boolean to indicate if a wall switch is a push button or not (default: false)
4141
4242
For hub configuration, see [the Velbus component](/components/velbus/).

‎source/_components/binary_sensor.wink.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,6 @@ The requirement is that you have setup [Wink](/components/wink/).
3434
- Dropcam sensors
3535

3636
<p class='note'>
37-
The above devices are confimed to work, but others may work as well.
37+
The above devices are confirmed to work, but others may work as well.
3838
</p>
3939

‎source/_components/binary_sensor.workday.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ The `workday` binary sensor indicates, whether the current day is a workday or n
1818
To enable the `workday` sensor in your installation, add the following to your `configuration.yaml` file:
1919

2020
```yaml
21-
# Example configuation.yaml entry
21+
# Example configuration.yaml entry
2222
binary_sensor:
2323
- platform: workday
2424
country: DE

‎source/_components/camera.generic.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Configuration variables:
3434
- **username** (*Optional*): The username for accessing your camera.
3535
- **password** (*Optional*): The password for accessing your camera.
3636
- **authentication** (*Optional*): Type for authenticating the requests `basic` (default) or `digest`.
37-
- **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits refetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image.
37+
- **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits re-fetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image.
3838
- **content_type** (*Optional*): Set the content type for the IP camera if it is not a jpg file (default: `image/jpeg`). Use `image/svg+xml` to add a dynamic svg file.
3939

4040
<p class='img'>

‎source/_components/camera.mjpeg.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ camera:
2828
Configuration variables:
2929
3030
- **mjpeg_url** (*Required*): The URL your camera serves the video on, eg. http://192.168.1.21:2112/
31-
- **still_image_url** (*Optional*): The URL for thumbmail picture if camera support that.
31+
- **still_image_url** (*Optional*): The URL for thumbnail picture if camera support that.
3232
- **name** (*Optional*): This parameter allows you to override the name of your camera.
3333
- **username** (*Optional*): The username for accessing your camera.
3434
- **password** (*Optional*): The password for accessing your camera.

‎source/_components/camera.mqtt.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ha_release: 0.43
1313
ha_iot_class: depends
1414
---
1515

16-
The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Everytime a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated.
16+
The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated.
1717

1818
This can be used with an application or a service capable of sending images through MQTT, for example [Zanzito](https://play.google.com/store/apps/details?id=it.barbaro.zanzito).
1919

‎source/_components/camera.synology.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: page
33
title: "Synology Camera"
4-
description: "Instructions how to integrate Synolog Surveillance Station cameras within Home Assistant."
4+
description: "Instructions how to integrate Synology Surveillance Station cameras within Home Assistant."
55
date: 2016-10-13 08:01
66
sidebar: true
77
comments: false

‎source/_components/climate.ecobee.markdown

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Returns the current temperature measured by the thermostat.
8787

8888
| Attribute type | Description |
8989
| ---------------| ----------- |
90-
| Integer | Currenly measured temperature
90+
| Integer | Currently measured temperature
9191

9292
### {% linkable_title Attribute `target_temperature` %}
9393

@@ -171,7 +171,7 @@ is returned as the user-visible name (rather than the internally used name).
171171

172172
### {% linkable_title Attribute `fan_min_on_time` %}
173173

174-
Returns the current fan mimimum on time.
174+
Returns the current fan minimum on time.
175175

176176
| Attribute type | Description |
177177
| ---------------| ----------- |
@@ -234,7 +234,7 @@ Turns the away mode on or off for the thermostat.
234234
### {% linkable_title Service `set_hold_mode` %}
235235

236236
Puts the thermostat into the given hold mode. For 'home', 'away', 'sleep',
237-
and ony other hold based on a reference climate, the
237+
and any other hold based on a reference climate, the
238238
target temperature is taken from the reference climate.
239239
For 'temp', the current temperature is taken as the target temperature.
240240
When None is provided as parameter, the hold_mode is turned off.

‎source/_components/climate.knx.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: page
33
title: "KNX Climate"
4-
description: "Instructions on how to integrate KXN thermostats with Home Assistant."
4+
description: "Instructions on how to integrate KNX thermostats with Home Assistant."
55
date: 2016-06-24 12:00
66
sidebar: true
77
comments: false
@@ -56,7 +56,7 @@ climate:
5656
* **controller_status_state_address** (*Optional*) Explicit KNX address for reading HVAC controller status
5757
5858
* **operation_mode_frost_protection_address** (*Optional*) KNX address for switching on/off frost/heat protection mode.
59-
* **operation_mode_night_address** (*Optional*) KNX address for switching on/off night nmode.
59+
* **operation_mode_night_address** (*Optional*) KNX address for switching on/off night mode.
6060
* **operation_mode_comfort_address** (*Optional*) KNX address for switching on/off comfort mode.
6161
6262
`operation_mode_frost_protection_address` / `operation_mode_night_address` / `operation_mode_comfort_address` are not necessary if `operation_mode_address` was specified.

0 commit comments

Comments
 (0)