mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-09 18:36:51 +00:00
Fix minor typos/punctuation, improve some phrasing (#31420)
* Remove repeated word (i.e., "AirNow Developer Tools Page page." —> "AirNow Developer Tools page.") * Upper-case Celsius * Edit misc spelling and phrasing * Rephrase description to add more detail on variable * Fix minor typos, spacing, and punctuation * tiny tweaks --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
This commit is contained in:
parent
efda2f74d0
commit
64dfa91f7c
@ -20,7 +20,7 @@ as a source for air quality data for your location.
|
|||||||
|
|
||||||
## Setup
|
## Setup
|
||||||
|
|
||||||
To generate an AirNow API key, go to the [AirNow Developer Tools Page](https://docs.airnowapi.org/account/request/) page.
|
To generate an AirNow API key, go to the [AirNow Developer Tools](https://docs.airnowapi.org/account/request/) page.
|
||||||
|
|
||||||
{% include integrations/config_flow.md %}
|
{% include integrations/config_flow.md %}
|
||||||
|
|
||||||
|
@ -78,7 +78,7 @@ repeat:
|
|||||||
required: true
|
required: true
|
||||||
type: [integer, list]
|
type: [integer, list]
|
||||||
can_acknowledge:
|
can_acknowledge:
|
||||||
description: Allows the alert to be unacknowledgeable.
|
description: Control whether the notification can be acknowledged; set to `false` if the alert should not be acknowledgeable.
|
||||||
required: false
|
required: false
|
||||||
type: boolean
|
type: boolean
|
||||||
default: true
|
default: true
|
||||||
|
@ -71,4 +71,4 @@ Enable temperature mode on your AC:
|
|||||||
| Service data attribute | Optional | Description |
|
| Service data attribute | Optional | Description |
|
||||||
| ---------------------- | -------- | ----------- |
|
| ---------------------- | -------- | ----------- |
|
||||||
| `Name` | yes | String with device name.
|
| `Name` | yes | String with device name.
|
||||||
| `value` | yes | Target value in celsius
|
| `value` | yes | Target value in Celsius
|
||||||
|
@ -539,4 +539,4 @@ cards:
|
|||||||
- Some devices, like TCL, become unavailable after they are turned off, unless you activate the **Screenless service**. To activate it, go to **Settings** > **System** > **Power and energy** > **Screenless service**, and activate it.
|
- Some devices, like TCL, become unavailable after they are turned off, unless you activate the **Screenless service**. To activate it, go to **Settings** > **System** > **Power and energy** > **Screenless service**, and activate it.
|
||||||
- Some devices experience disconnects every 15 seconds. This is typically resolved by rebooting the Android TV device after the initial setup of the integration.
|
- Some devices experience disconnects every 15 seconds. This is typically resolved by rebooting the Android TV device after the initial setup of the integration.
|
||||||
- If you are not able to connect to the Android TV device, or are asked to pair it again and again, try force-stopping the Android TV Remote Service and clearing its storage. On the Android TV device, go to **Settings** > **Apps** > **Show system apps**. Then, select **Android TV Remote Service** > **Storage** > **Clear storage**. You will have to pair again.
|
- If you are not able to connect to the Android TV device, or are asked to pair it again and again, try force-stopping the Android TV Remote Service and clearing its storage. On the Android TV device, go to **Settings** > **Apps** > **Show system apps**. Then, select **Android TV Remote Service** > **Storage** > **Clear storage**. You will have to pair again.
|
||||||
- Some onscreen keyboards enabled by TV manufacturers do not support concurrent virtual and onscreen keyboard use. This presents whenever a text field is selected, such as "search" where a constant **use the keyboard on your mobile device** will show, preventing you from opening the onscreen keyboard to type. This can be overcome by either disabling your 3rd party keyboard and using the default Gboard keyboard or by unselecting **Enable IME** in the **Configure** page of the integration.
|
- Some onscreen keyboards enabled by TV manufacturers do not support concurrent virtual and onscreen keyboard use. This presents whenever a text field is selected, such as "search" where a constant **use the keyboard on your mobile device** will show, preventing you from opening the onscreen keyboard to type. This can be overcome by either disabling your 3rd party keyboard and using the default Gboard keyboard or by deselecting **Enable IME** in the **Configure** page of the integration.
|
||||||
|
@ -52,7 +52,7 @@ port:
|
|||||||
## Notes and limitations
|
## Notes and limitations
|
||||||
|
|
||||||
- The tuner is currently unsupported as are the `media_player` play, pause, prev, and next controls.
|
- The tuner is currently unsupported as are the `media_player` play, pause, prev, and next controls.
|
||||||
- Enabling this platform will set and enforce **Standby IP Control On** on your Anthem device. You almost certainly want this. If you disable it on the device, it will just get re-enabled by Home Assistant.
|
- Enabling this platform will set and enforce **Standby IP Control On** within your Anthem device. You almost certainly want this. If you disable it on the device, it will just get re-enabled by Home Assistant.
|
||||||
|
|
||||||
<div class='note warning'>
|
<div class='note warning'>
|
||||||
|
|
||||||
|
@ -40,7 +40,7 @@ Before using this integration, your water heater must be connected to a Wi-Fi ne
|
|||||||
- HPV10-66H01DV
|
- HPV10-66H01DV
|
||||||
- HPV10-80H01DV
|
- HPV10-80H01DV
|
||||||
|
|
||||||
Water heaters that can be controlled using the A. O. Smith mobile app should be compatible with this integration. If your water heater is not detected by the integration, but it can be controlled using the mobile app, please [open an issue on GitHub](https://github.com/home-assistant/core/issues/new?template=bug_report.yml&integration_name=A.%20O.%20Smith&integration_link=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Faosmith) so that support can be added. Similarly, if your water heater is working with this integration, but its model number is not listed here, please [open an documentation issue](https://github.com/home-assistant/home-assistant.io/issues/new?template=feedback.yml&url=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Faosmith) so it can be added to the list.
|
Water heaters that can be controlled using the A. O. Smith mobile app should be compatible with this integration. If your water heater is not detected by the integration, but it can be controlled using the mobile app, please [open an issue on GitHub](https://github.com/home-assistant/core/issues/new?template=bug_report.yml&integration_name=A.%20O.%20Smith&integration_link=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Faosmith) so that support can be added. Similarly, if your water heater is working with this integration, but its model number is not listed here, please [open a documentation issue](https://github.com/home-assistant/home-assistant.io/issues/new?template=feedback.yml&url=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Faosmith) so it can be added to the list.
|
||||||
|
|
||||||
{% include integrations/config_flow.md %}
|
{% include integrations/config_flow.md %}
|
||||||
|
|
||||||
|
@ -51,7 +51,7 @@ Using the media browser, you can view a list of all installed applications and T
|
|||||||
|
|
||||||
## Play media service
|
## Play media service
|
||||||
|
|
||||||
The `play_media` {% term service %} can be used in a automation or script to switch to a specified application or TV channel. It selects the best matching application or channel according to the `media_content_id`:
|
The `play_media` {% term service %} can be used in an automation or script to switch to a specified application or TV channel. It selects the best matching application or channel according to the `media_content_id`:
|
||||||
|
|
||||||
1. Channel number *(i.e., '1' or '6')*
|
1. Channel number *(i.e., '1' or '6')*
|
||||||
2. Exact app or channel name *(i.e., 'Google Play' or 'CNN')*
|
2. Exact app or channel name *(i.e., 'Google Play' or 'CNN')*
|
||||||
|
@ -17,7 +17,7 @@ ha_config_flow: true
|
|||||||
The CalDAV integration allows you to connect your WebDAV calendar to Home Assistant
|
The CalDAV integration allows you to connect your WebDAV calendar to Home Assistant
|
||||||
as one of these entity types:
|
as one of these entity types:
|
||||||
|
|
||||||
- A [calendar](/integrations/calendar) entity which can be used to trigger automations based on the the start or end of an event using criteria such as the event name or description.
|
- A [calendar](/integrations/calendar) entity which can be used to trigger automations based on the start or end of an event using criteria such as the event name or description.
|
||||||
- A [todo](/integrations/todo) entity which tracks the number of active items
|
- A [todo](/integrations/todo) entity which tracks the number of active items
|
||||||
on the to-do list.
|
on the to-do list.
|
||||||
|
|
||||||
|
@ -31,7 +31,7 @@ There is currently support for the following device types within Home Assistant:
|
|||||||
|
|
||||||
It is recommended to set up a new & dedicated account on your DoorBird App/web portal for use with Home Assistant. The instructions in this document refer specifically to the DoorBird IOS/Android app. Still, most actions can also be performed using the web-based [DoorBird - WebAdmin](https://webadmin.doorbird.com) portal and logging in on your DoorBird admin account.
|
It is recommended to set up a new & dedicated account on your DoorBird App/web portal for use with Home Assistant. The instructions in this document refer specifically to the DoorBird IOS/Android app. Still, most actions can also be performed using the web-based [DoorBird - WebAdmin](https://webadmin.doorbird.com) portal and logging in on your DoorBird admin account.
|
||||||
|
|
||||||
To setup a new account for Home Assistant, open the DoorBird App by clicking settings (cog icon) -> Administration-> LOGIN (using your DoorBird App Administration details). Under the "USER" section, choose "Add". This new user account requires specific permissions enabled (depending on what functionality you want). Permissions can be found under "Permissions". The following permissions are recommended (or amend depending on your requirements:
|
To setup a new account for Home Assistant, open the DoorBird App by selecting **Settings** (cog icon) > **Administration** > **LOGIN** (using your DoorBird App Administration details). Under the **USER** section, choose **Add**. This new user account requires specific permissions enabled (depending on what functionality you want). Permissions can be found under **Permissions**. The following permissions are recommended (or amend depending on your requirements:
|
||||||
|
|
||||||
- "Watch Always" (live view)
|
- "Watch Always" (live view)
|
||||||
- "History" (last motion)
|
- "History" (last motion)
|
||||||
@ -63,7 +63,7 @@ localhost:8123`. Replace `{DEVICE_TOKEN}` with the token specified in your confi
|
|||||||
<br><br>
|
<br><br>
|
||||||
Please note that clearing device events will require configuration steps above to be taken again. It could also affect other third-party applications you may use with your DoorBird device. It will not break the official mobile app in any way, so mobile push notifications will still work.
|
Please note that clearing device events will require configuration steps above to be taken again. It could also affect other third-party applications you may use with your DoorBird device. It will not break the official mobile app in any way, so mobile push notifications will still work.
|
||||||
<br><br>
|
<br><br>
|
||||||
If DoorBird was setup using UI prompts, a token can be discovered through DoorBird App by clicking settings (cog icon) -> Administration-> LOGIN (using your App Administration details). Under the "FAVORITES" section, choose "HTTP(S) Calls". This displays all events and the associated HTTP URL. In that URL field, you will be able to see the token that was auto-generated by Home Assistant.
|
If DoorBird was setup using UI prompts, a token can be discovered through DoorBird App by selecting **Settings** (cog icon) > **Administration** > **LOGIN** (using your App Administration details). Under the **FAVORITES** section, choose **HTTP(S) Calls**. This displays all events and the associated HTTP URL. In that URL field, you will be able to see the token that was auto-generated by Home Assistant.
|
||||||
|
|
||||||
### Event data
|
### Event data
|
||||||
|
|
||||||
@ -87,7 +87,7 @@ Once events have been registered on the DoorBird device, they must be attached t
|
|||||||
|
|
||||||
The schedules can be found by navigating to the following area of the DoorBird app (Android or IOS):
|
The schedules can be found by navigating to the following area of the DoorBird app (Android or IOS):
|
||||||
|
|
||||||
Settings (cog icon) -> Administration -> LOGIN LOGIN (using your App Administration details) -> (under "EXPERT SETTINGS") Schedule for doorbell
|
**Settings** (cog icon) > **Administration** > **LOGIN** (using your App Administration details) > (under **EXPERT SETTINGS**) Schedule for doorbell.
|
||||||
|
|
||||||
- `Push notification`
|
- `Push notification`
|
||||||
- `Trigger Relay ("Relay 1" or "Relay 2")`
|
- `Trigger Relay ("Relay 1" or "Relay 2")`
|
||||||
|
@ -41,10 +41,10 @@ Using the vacuum entity, you can monitor and control your Ecovacs Deebot vacuum.
|
|||||||
|
|
||||||
Additionally, **depending on your model**, the integration provides the following entities:
|
Additionally, **depending on your model**, the integration provides the following entities:
|
||||||
|
|
||||||
- **Binary sensor**:
|
- **Binary sensor**:
|
||||||
- `Mop attached`: On if the mop is attached. Note: If you do not see the state change to `Mop attached` in Home Assistant, you may need to wake up the robot in order to push the state change. Some models report an entity state change only if the overall status of the vacuum has changed. For example, if the overall state changes from `docked` to `cleaning`.
|
- `Mop attached`: On if the mop is attached. Note: If you do not see the state change to `Mop attached` in Home Assistant, you may need to wake up the robot in order to push the state change. Some models report an entity state change only if the overall status of the vacuum has changed. For example, if the overall state changes from `docked` to `cleaning`.
|
||||||
- **Button**:
|
- **Button**:
|
||||||
- `Reset lifespan`: For each supported component an button entity to reset the lifespan will be created. All disabled by default
|
- `Reset lifespan`: For each supported component, a button entity to reset the lifespan will be created. All disabled by default.
|
||||||
- `Relocate`: Button entity to trigger manual relocation.
|
- `Relocate`: Button entity to trigger manual relocation.
|
||||||
- **Image**:
|
- **Image**:
|
||||||
- `Map`: The floorplan/map as an image in SVG format.
|
- `Map`: The floorplan/map as an image in SVG format.
|
||||||
@ -55,16 +55,16 @@ Additionally, **depending on your model**, the integration provides the followin
|
|||||||
- `Water amount`: Specify the water amount used during cleaning with the mop.
|
- `Water amount`: Specify the water amount used during cleaning with the mop.
|
||||||
- `Work mode`: Specify the mode, how the bot should clean.
|
- `Work mode`: Specify the mode, how the bot should clean.
|
||||||
- **Sensor**:
|
- **Sensor**:
|
||||||
- `Error`: The error code and a description of the error. `0` means no error. Disabled by default
|
- `Error`: The error code and a description of the error. `0` means no error. Disabled by default.
|
||||||
- `Lifespan`: For each supported component an entity with the remaining lifespan will be created
|
- `Lifespan`: For each supported component, an entity with the remaining lifespan will be created.
|
||||||
- `Network`: The following network related entities will be created. All disabled by default
|
- `Network`: The following network related entities will be created. All disabled by default.
|
||||||
- `Ip address`
|
- `Ip address`
|
||||||
- `Wi-Fi RSSI`
|
- `Wi-Fi RSSI`
|
||||||
- `Wi-Fi SSID`
|
- `Wi-Fi SSID`
|
||||||
- `Cleaning cycle`:
|
- `Cleaning cycle`:
|
||||||
- `Area`: The cleaned area
|
- `Area`: The cleaned area
|
||||||
- `Time`: The cleaned time
|
- `Time`: The cleaned time
|
||||||
- `Total statistics`: Updated after each cleaning cycle:
|
- `Total statistics`: Updated after each cleaning cycle:
|
||||||
- `Area`: Total cleaned area
|
- `Area`: Total cleaned area
|
||||||
- `Cleanings`: The number of cleanings
|
- `Cleanings`: The number of cleanings
|
||||||
- `Time`: The total cleaning time
|
- `Time`: The total cleaning time
|
||||||
|
@ -28,7 +28,7 @@ The **Environment Canada** {% term integration %} provides meteorological data f
|
|||||||
|
|
||||||
The integration automatically determines the closest weather station based on the latitude and longitude specified. If integration-specific coordinates are not provided, the coordinates configured for Home Assistant are used.
|
The integration automatically determines the closest weather station based on the latitude and longitude specified. If integration-specific coordinates are not provided, the coordinates configured for Home Assistant are used.
|
||||||
|
|
||||||
You can also specify a weather station to use by providing a identification code of the form `AB/s0000123`, based on those listed in [this CSV file](https://dd.weather.gc.ca/citypage_weather/docs/site_list_towns_en.csv).
|
You can also specify a weather station to use by providing an identification code of the form `AB/s0000123`, based on those listed in [this CSV file](https://dd.weather.gc.ca/citypage_weather/docs/site_list_towns_en.csv).
|
||||||
|
|
||||||
## Entities
|
## Entities
|
||||||
|
|
||||||
|
@ -72,7 +72,7 @@ user_name:
|
|||||||
required: true
|
required: true
|
||||||
type: string
|
type: string
|
||||||
password:
|
password:
|
||||||
description: Which password to authenticate with when connecting to the device. This must be the password for connceting directly to the device and not the password for your EyezOn account. EVL3 only works with max. 6 characters.
|
description: Which password to authenticate with when connecting to the device. This must be the password for connecting directly to the device and not the password for your EyezOn account. EVL3 only works with max. 6 characters.
|
||||||
required: true
|
required: true
|
||||||
type: string
|
type: string
|
||||||
code:
|
code:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user