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-24 09:46:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix misc typos (#10753)

Browse Source 
* fix typos

* More typos
This commit is contained in:
Alok Saboo 2019-10-12 17:52:29 -04:00 committed by Franck Nijhof
parent 3758a4cf3a
commit 915def2c11
18 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_addons/dhcp_server.markdown
View File

@ -86,7 +86,7 @@ hosts:
required: true
type: string
ip:
description: Fix ip address for device.
description: Fix IP address for device.
required: true
type: string
{% endconfiguration %}

4
source/_docs/ecosystem/certificates/tls_domain_certificate.markdown
View File

@ -48,12 +48,12 @@ Press Enter to Continue
If your router uses DNSMasq (for example DDWRT) add the following line to DNSMasq options:
```text
address=/mydomain.com/<hass ip>
address=/mydomain.com/<hass IP>
```
### Edit your Home Assistant configuration to use your certificates
The [`http`](/integrations/http/) section must contain the full path to the needed files.
The [`http`](/integrations/http/) section must contain the full path to the needed files.
```yaml
http:

2
source/_integrations/asterisk_mbox.markdown
View File

@ -34,7 +34,7 @@ password:
required: true
type: string
host:
description: The ip-address of the server that is running the Asterisk PBX
description: The IP-address of the server that is running the Asterisk PBX
required: true
type: string
port:

2
source/_integrations/concord232.markdown
View File

@ -43,7 +43,7 @@ code:
required: false
type: string
mode:
description: audible/silent if defined, specifies wether Alarm Panel should be audible or silent when armed in Home Mode.
description: audible/silent if defined, specifies whether Alarm Panel should be audible or silent when armed in Home Mode.
required: false
type: string
default: audible

2
source/_integrations/emulated_roku.markdown
View File

@ -23,7 +23,7 @@ Windows is not supported because Home Assistant uses `ProactorEventLoop` which d
This integration opens an unauthenticated API on the host, allowing anything on the local network to access
your Home Assistant instance through the automations you create with emulated Roku as the trigger.
Using a proxy with whitelisted IP addresses is recommended. (set `advertise_ip` to the proxy's ip or DNS name)
Using a proxy with whitelisted IP addresses is recommended. (set `advertise_ip` to the proxy's IP or DNS name)
</div>

2
source/_integrations/flux_led.markdown
View File

@ -41,7 +41,7 @@ automatic_add:
default: false
type: boolean
devices:
description: A list of devices with their ip address.
description: A list of devices with their IP address.
required: false
type: list
keys:

2
source/_integrations/fritzbox_netmonitor.markdown
View File

@ -43,7 +43,7 @@ The following statistics will be exposed as attributes.
|is_linked |True if the FritzBox is physically linked to the provider |
|is_connected |True if the FritzBox has established an internet-connection |
|wan_access_type |Connection-type, can be `DSL` or `Cable` |
|external_ip |External ip address |
|external_ip |External IP address |
|uptime |Uptime in seconds |
|bytes_sent |Bytes sent |
|bytes_received |Bytes received |

6
source/_integrations/hangouts.markdown
View File

@ -17,7 +17,7 @@ There is currently support for the following device types within Home Assistant:
## Setup the integration via the frontend
Menu: *Configuration* -> *Integrations*
Configure the integration:
* Enter your **Google Mail Address** and **Password**
* In the authentication form there is an Optional Field: **Authorization Code** which should only be used if you get an invalid login error with email and password (see note below for details).
@ -225,9 +225,9 @@ Reconnects the hangouts bot.
## Advanced
### Automatic reconnect after ip change
### Automatic reconnect after IP change
The hangouts integration can't detect if your ip address changes, so it can't automatic reconnect to the Google servers. This is a workaround for this problem.
The hangouts integration can't detect if your IP address changes, so it can't automatic reconnect to the Google servers. This is a workaround for this problem.
{% raw %}

2
source/_integrations/lightwave.markdown
View File

@ -37,7 +37,7 @@ lightwave:
name: Torch socket
```
Where `192.168.1.2` is the ip address of your Lightwave hub.
Where `192.168.1.2` is the IP address of your Lightwave hub.
Each `switch` or `light` requires an `id` and a `name`. The `id` takes the form `R#D#` where `R#` is the room number and `D#` is the device number.
`lights` and `switches` are optional but one of these must be present.

8
source/_integrations/remote_rpi_gpio.markdown
View File

@ -6,15 +6,15 @@ ha_category:
- DIY
- Binary Sensor
- Switch
ha_release: 0.94
ha_release: 0.94
ha_iot_class: Local Push
---
The `rpi_gpio` integration is the base for all related GPIO platforms in Home Assistant. For the platform configurations, please check their corresponding sections.
The `rpi_gpio` integration is the base for all related GPIO platforms in Home Assistant. For the platform configurations, please check their corresponding sections.
The remote RPi and the control computer where Home Assistant is running must be prepared to run remote_rpi_gpio, see details [here](https://gpiozero.readthedocs.io/en/stable/remote_gpio.html).
Note that for virtual environments you may need to set an environment variable when starting the environment to set the pin factory, example:
Note that for virtual environments you may need to set an environment variable when starting the environment to set the pin factory, example:
`Environment = GPIOZERO_PIN_FACTORY=pigpio PIGPIO_ADDR=YOUR_RPi_IP_ADDRESS`
@ -122,4 +122,4 @@ switch:
### Troubleshooting
If you receive an error such as `gpiozero.exc.BadPinFactory: Unable to load any default pin factory!` try changing the pinfactory from `pigpio` to `mock`, this adresses a [known issue](https://www.raspberrypi.org/forums/viewtopic.php?p=1417922).
If you receive an error such as `gpiozero.exc.BadPinFactory: Unable to load any default pin factory!` try changing the pinfactory from `pigpio` to `mock`, this addresses a [known issue](https://www.raspberrypi.org/forums/viewtopic.php?p=1417922).

2
source/_integrations/tplink.markdown
View File

@ -197,4 +197,4 @@ For Archer C9 models running firmware version 150811 or later please use the enc
See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.
For Archer D9 model the default ip is 192.168.1.1, the username is not necessary and you can leave that field blank.
For Archer D9 model the default IP is 192.168.1.1, the username is not necessary and you can leave that field blank.

4
source/_integrations/wemo.markdown
View File

@ -30,7 +30,7 @@ There is currently support for the following device types within Home Assistant:
type: boolean
default: true
static:
description: One or more static IP adresses for WeMo to use
description: One or more static IP addresses for WeMo to use
required: false
type: list
{% endconfiguration %}
@ -103,4 +103,4 @@ There are several services which can be used for automations and control of the
| `turn_off` | Calling this service will turn the humidifier off (entity_id is required).
| `turn_on` | Calling this service will turn the humidifier on and set the speed to the last used speed (defaults to medium, entity_id is required).
| `wemo_set_humidity` | Calling this service will set the desired relative humidity setting on the device (entity_id is a required list of 1 or more entities to set humidity on, and target_humidity is a required float value between 0 and 100 (this value will be rounded down and mapped to one of the valid desired humidity settings of 45, 50, 55, 60, or 100 that are supported by the WeMo humidifier)).
| `wemo_reset_filter_life` | Calling this service will reset the humdifier's filter life back to 100% (entity_id is a required list of 1 or more entities to reset the filter life on). Call this service when you change the filter on your humidifier.
| `wemo_reset_filter_life` | Calling this service will reset the humdifier's filter life back to 100% (entity_id is a required list of 1 or more entities to reset the filter life on). Call this service when you change the filter on your humidifier.

2
source/_integrations/worxlandroid.markdown
View File

@ -22,7 +22,7 @@ sensor:
{% configuration %}
host:
description: The ip address or host name of the mower.
description: The IP address or host name of the mower.
required: true
type: string
pin:

2
source/_integrations/xiaomi.markdown
View File

@ -112,7 +112,7 @@ camera:
```
## Hostname template
The hostname/ip address can be provided either a value or from the existing entity attributes.
The hostname/IP address can be provided either a value or from the existing entity attributes.
```yaml
camera:

2
source/_posts/2018-03-30-release-66.markdown
View File

@ -52,7 +52,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
- Refactor Hue: If you specify a bridge in your config, the `host` key is now required and needs to be a valid ip address. Option `allow_in_emulated_hue` has been removed. Exclude the lights via the emulated hue config. Due to the internal changes of how the Hue integration works, any Hue custom component will no longer work. ([@balloob] - [#13043]) ([hue docs]) ([light.hue docs]) (breaking change)
- Refactor Hue: If you specify a bridge in your config, the `host` key is now required and needs to be a valid IP address. Option `allow_in_emulated_hue` has been removed. Exclude the lights via the emulated hue config. Due to the internal changes of how the Hue integration works, any Hue custom component will no longer work. ([@balloob] - [#13043]) ([hue docs]) ([light.hue docs]) (breaking change)
- Z-Wave: In version 0.47, the opt-in `new_entity_ids` configuration was added to Z-Wave to smooth the transition through the change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will already be stored in the Entity Registry and no changes are required. If not, entity IDs can now be manually configured using the Entity Registry if necessary. ([@armills] - [#12652]) ([zwave docs]) (breaking change)
- Spotcrime sensor: This update changes the sensor to require a user supplied API key as a configuration entry. The default key has been removed from the Spotcrime package and has also been modified to accept a user supplied API key.([@jcconnell] - [#12926]) ([sensor.spotcrime docs]) (breaking change)
- Smappee sensor: Fixed SI units for current consumption. Total consumption should be in kWh. not kW. ([@vandenberghev] - [#13190]) ([sensor.smappee docs]) (breaking change)

2
source/_posts/2018-04-14-release-67.markdown
View File

@ -148,7 +148,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Support color temperature in Homekit ([@morberg] - [#13658]) ([homekit docs])
- Remove unused CONF_WATCHERS ([@robmarkcole] - [#13678]) ([folder_watcher docs])
- Add media type separation for video/movie ([@tadly] - [#13612]) (breaking change)
- Adding configration to disable ip address as a requirement Fixes: #13399 ([@PlanetJ] - [#13692]) ([device_tracker docs])
- Adding configuration to disable IP address as a requirement Fixes: #13399 ([@PlanetJ] - [#13692]) ([device_tracker docs])
- Tahoma switches ([@ikucuze] - [#13636]) ([tahoma docs]) ([switch.tahoma docs]) (new-platform)
- Send XY color for non-osram hue bulbs ([@armills] - [#13665]) ([light.hue docs])
- Update AbodePy version to 0.12.3 ([@MisterWil] - [#13709]) ([abode docs])

2
source/_posts/2018-06-04-esphomelib.markdown
View File

@ -67,7 +67,7 @@ switch:
name: "Living Room Dehumidifer"
pin: GPIO5
```
If you now press upload again (this time the ESP doesn't need to be connected via USB, as updates [can be done over WiFi](https://esphomelib.com/esphomeyaml/integrations/ota.html)), you will see a switch show up in Home Assisstant automatically through [MQTT discovery](/docs/mqtt/discovery/).
If you now press upload again (this time the ESP doesn't need to be connected via USB, as updates [can be done over WiFi](https://esphomelib.com/esphomeyaml/integrations/ota.html)), you will see a switch show up in Home Assistant automatically through [MQTT discovery](/docs/mqtt/discovery/).
<p class='img'>
<img

4
source/_posts/2019-03-13-release-89.markdown
View File

@ -159,13 +159,13 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Fix calc next ([@balloob] - [#21630]) (beta fix)
- Cast displaytime to int for JSON RPC ([@GGeezes] - [#21649]) ([notify docs]) (beta fix)
- :shirt: Corrects unit of measurement symbol for Watt ([@frenck] - [#21654]) ([toon docs]) (beta fix)
- Rename Google Assistant evenets ([@balloob] - [#21655]) ([google_assistant docs]) (beta fix)
- Rename Google Assistant events ([@balloob] - [#21655]) ([google_assistant docs]) (beta fix)
- :ambulance: Fixes Toon doing I/O in coroutines ([@frenck] - [#21657]) ([toon docs]) (beta fix)
- Upgrade toonapilib to 3.1.0 ([@frenck] - [#21661]) ([toon docs]) (beta fix)
- Avoid recorder thread crashing ([@balloob] - [#21668]) (beta fix)
- check we have a tb ([@dgomes] - [#21670]) ([system_log docs]) (beta fix)
- Fix ADS race condition ([@carstenschroeder] - [#21677]) ([ads docs]) (beta fix)
- resync hass that changes have occured ([@fredrike] - [#21705]) ([tellduslive docs]) (beta fix)
- resync hass that changes have occurred ([@fredrike] - [#21705]) ([tellduslive docs]) (beta fix)
- Upgrade toonapilib to 3.2.1 ([@frenck] - [#21706]) ([toon docs]) (beta fix)
## All changes