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-16 22:06:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix a bunch of anchor links (#28127)

Browse Source
This commit is contained in:
Franck Nijhof 2023-07-07 14:38:06 +02:00 committed by GitHub
parent a71ea12e1d
commit 0691b87d5e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
source/_docs/automation/trigger.markdown
View File

@ -689,11 +689,11 @@ automation:
The Entity ID of an [Input Datetime](/integrations/input_datetime/).
has_date | has_time | Description
-|-|-
`true` | `true` | Will fire at specified date & time.
`true` | `false` | Will fire at midnight on specified date.
`false` | `true` | Will fire once a day at specified time.
| has_date | has_time | Description |
| -------- | -------- | ---------------------------------------- |
| `true` | `true` | Will fire at specified date & time. |
| `true` | `false` | Will fire at midnight on specified date. |
| `false` | `true` | Will fire once a day at specified time. |
{% raw %}
@ -941,7 +941,7 @@ Punctuation and casing are ignored, so "It's PARTY TIME!!!" will also match.
## Multiple triggers
It is possible to specify multiple triggers for the same rule. To do so just prefix the first line of each trigger with a dash (-) and indent the next lines accordingly. Whenever one of the triggers fires, [processing](#what-are-triggers) of your automation rule begins.
It is possible to specify multiple triggers for the same rule. To do so just prefix the first line of each trigger with a dash (-) and indent the next lines accordingly. Whenever one of the triggers fires, processing of your automation rule begins.
```yaml
automation:
@ -956,7 +956,7 @@ automation:
## Multiple Entity IDs for the same Trigger
It is possible to specify multiple entities for the same trigger. To do so add multiple entities using a nested list. The trigger will fire and start, [processing](#what-are-triggers) your automation each time the trigger is true for any entity listed.
It is possible to specify multiple entities for the same trigger. To do so add multiple entities using a nested list. The trigger will fire and start, processing your automation each time the trigger is true for any entity listed.
```yaml
automation:

2
source/_integrations/alarm_control_panel.mqtt.markdown
View File

@ -77,7 +77,7 @@ availability_topic:
required: false
type: string
code:
description: If defined, specifies a code to enable or disable the alarm in the frontend. Note that the code is validated locally and blocks sending MQTT messages to the remote device. For remote code validation, the code can be configured to either of the special values `REMOTE_CODE` (numeric code) or `REMOTE_CODE_TEXT` (text code). In this case, local code validation is bypassed but the frontend will still show a numeric or text code dialog. Use `command_template` to send the code to the remote device. Example configurations for remote code validation [can be found here](./#configurations-with-remote-code-validation).
description: If defined, specifies a code to enable or disable the alarm in the frontend. Note that the code is validated locally and blocks sending MQTT messages to the remote device. For remote code validation, the code can be configured to either of the special values `REMOTE_CODE` (numeric code) or `REMOTE_CODE_TEXT` (text code). In this case, local code validation is bypassed but the frontend will still show a numeric or text code dialog. Use `command_template` to send the code to the remote device. Example configurations for remote code validation [can be found here](#configurations-with-remote-code-validation).
required: false
type: string
code_arm_required:

24
source/_integrations/apple_tv.markdown
View File

@ -22,7 +22,7 @@ The Apple TV integration allows you to control an Apple TV (any generation).
There is currently support for the following entities within the Apple TV device:
- [Media Player](#media_player)
- [Media Player](#media-player)
- [Remote](#remote)
{% include integrations/config_flow.md %}
@ -43,12 +43,12 @@ launch specific content in applications.
Examples of some `Deep Links` for popular applications:
| App | URL |
|-----------| --- |
| YouTube | youtube://www.youtube.com/watch?v=dQw4w9WgXcQ
| Netflix | https://www.netflix.com/title/80234304
| Disney+ | https://www.disneyplus.com/series/the-beatles-get-back/7DcWEeWVqrkE
| Apple TV+ | https://tv.apple.com/show/severance/umc.cmc.1srk2goyh2q2zdxcx605w8vtx
| App | URL |
| --------- | --------------------------------------------------------------------- |
| YouTube | youtube://www.youtube.com/watch?v=dQw4w9WgXcQ |
| Netflix | https://www.netflix.com/title/80234304 |
| Disney+ | https://www.disneyplus.com/series/the-beatles-get-back/7DcWEeWVqrkE |
| Apple TV+ | https://tv.apple.com/show/severance/umc.cmc.1srk2goyh2q2zdxcx605w8vtx |
The simplest way to find useful `Deep Links` is to use the “Share” feature in iOS
or macOS versions of the App. Share sheets will often have a “Copy” or
@ -112,11 +112,11 @@ The following commands are currently available:
### Service `send_command`
| Service data<br>attribute | Optional | Description |
| ------------------------- | -------- | ------------ |
| `entity_id` | no | `entity_id` of the Apple TV |
| `command` | no | Command, or list of commands to be sent |
| `num_repeats` | yes | Number of times to repeat the commands |
| Service data<br>attribute | Optional | Description |
| ------------------------- | -------- | ---------------------------------------------------------------------------------------------- |
| `entity_id` | no | `entity_id` of the Apple TV |
| `command` | no | Command, or list of commands to be sent |
| `num_repeats` | yes | Number of times to repeat the commands |
| `delay_secs` | yes | Interval in seconds between one send and another <br> This is a `float` value e.g. 1, 1.2 etc. |
### Examples

2
source/_integrations/doorbird.markdown
View File

@ -48,7 +48,7 @@ See [Schedules](#schedules) section below for details on how to configure schedu
Event names will be prefixed by `doorbird_devicename`. For example, the example event `somebody_pressed_the_button` for the device 'Driveway Gate' will be seen in Home Assistant as `doorbird_driveway_gate_somebody_pressed_the_button`. This is to prevent conflicts with other events.
See [Automation Example](#automation_example) section below for details on how to use the event names in an automation.
See [Automation Example](#automation-example) section below for details on how to use the event names in an automation.
<div class="note info">
Events will not be received in Home Assistant until a schedule is defined via the DoorBird app.

2
source/_integrations/modbus.markdown
View File

@ -1176,7 +1176,7 @@ and restart Home Assistant, reproduce the problem, and include the log in the is
## Building on top of Modbus
- [Modbus Binary Sensor](#configuring-platform-binary_sensor)
- [Modbus Binary Sensor](#configuring-platform-binary-sensor)
- [Modbus Climate](#configuring-platform-climate)
- [Modbus Cover](#configuring-platform-cover)
- [Modbus Fan](#configuring-platform-fan)

2
source/_integrations/purpleair.markdown
View File

@ -33,7 +33,7 @@ Remove Sensor:
To add this integration, you need a (free) Purple Air API Key. A new account currently comes with 1 million free points. After that, you need to buy additional points to continue to use the API. The current plugin uses ~30K points/day. The 1 million points last about a month. A lack of points will trigger API errors until you buy more points.
Detailed instructions are at [https://community.purpleair.com/t/creating-api-keys/3951]([https://community.purpleair.com/t/creating-api-keys/3951]) but in summary you:
Detailed instructions can be found [here](https://community.purpleair.com/t/creating-api-keys/3951) but in summary you:
* Create an account at https://develop.purpleair.com/ (which uses Single Sign-On through a Google account).
* On the ['keys'](https://develop.purpleair.com/keys) page press the "plus" button to create an API key. Leave the defaults of **Read** and **Enabled**.

4
source/_integrations/webostv.markdown
View File

@ -23,8 +23,8 @@ The `webostv` platform allows you to control a [LG](https://www.lg.com/) webOS S
There is currently support for the following device types within Home Assistant:
- [Media Player](#media-player)
- [Notifications](#notifications)
- [Media Player](/integrations/media_player/)
- [Notifications](/integrations/notification/)
To begin with enable *LG Connect Apps* feature in *Network* settings of the TV.