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-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: apply sentence-style capitalization (#29867)

Browse Source 
* Docs: apply sentence-style capitalization

* Update source/_docs/automation/trigger.markdown
This commit is contained in:
c0ffeeca7 2023-11-16 13:13:28 +01:00 committed by GitHub
parent 89da813570
commit 8bb2c3ead3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
23 changed files with 51 additions and 51 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/authentication/providers.markdown
View File

@ -53,7 +53,7 @@ homeassistant:
If you don't specify any `auth_providers` section in the `configuration.yaml` file then this provider will be set up automatically. If you don't specify any `auth_providers` section in the `configuration.yaml` file then this provider will be set up automatically.
### Trusted Networks ### Trusted networks
The Trusted Networks auth provider defines a range of IP addresses for which no authentication will be required (also known as "allowlisting"). For example, you can allowlist your local network so you won't be prompted for a password if you access Home Assistant from inside your home. The Trusted Networks auth provider defines a range of IP addresses for which no authentication will be required (also known as "allowlisting"). For example, you can allowlist your local network so you won't be prompted for a password if you access Home Assistant from inside your home.
@ -152,7 +152,7 @@ homeassistant:
Assuming you have only the owner created though onboarding process, no other users ever created. The above example configuration will allow you directly access Home Assistant main page if you access from your internal network (192.168.0.0/24) or from localhost (127.0.0.1). If you get a login abort error, then you can change to use Home Assistant Authentication Provider to login, if you access your Home Assistant instance from outside network. Assuming you have only the owner created though onboarding process, no other users ever created. The above example configuration will allow you directly access Home Assistant main page if you access from your internal network (192.168.0.0/24) or from localhost (127.0.0.1). If you get a login abort error, then you can change to use Home Assistant Authentication Provider to login, if you access your Home Assistant instance from outside network.
### Command Line ### Command line
The Command Line auth provider executes a configurable shell command to perform user authentication. Two environment variables, `username` and `password`, are passed to the command. Access is granted when the command exits successfully (with exit code 0). The Command Line auth provider executes a configurable shell command to perform user authentication. Two environment variables, `username` and `password`, are passed to the command. Access is granted when the command exits successfully (with exit code 0).

2
source/_docs/automation/modes.markdown
View File

@ -38,7 +38,7 @@ automation:
- delay: 300 # seconds (=5 minutes) - delay: 300 # seconds (=5 minutes)
``` ```
## Example Queued ## Example queued
Sometimes an automation is doing an action on a device that does not support multiple simultaneous actions. In such cases, a queue can be used. In that case, the automation will be executed once it's current invocation and queue are done. Sometimes an automation is doing an action on a device that does not support multiple simultaneous actions. In such cases, a queue can be used. In that case, the automation will be executed once it's current invocation and queue are done.

6
source/_docs/automation/templating.markdown
View File

@ -78,7 +78,7 @@ These are the properties available for a [MQTT trigger](/docs/automation/trigger
| `trigger.payload_json` | Dictionary of the JSON parsed payload. | `trigger.payload_json` | Dictionary of the JSON parsed payload.
| `trigger.qos` | QOS of payload. | `trigger.qos` | QOS of payload.
### Numeric State ### Numeric state
These are the properties available for a [Numeric State trigger](/docs/automation/trigger/#numeric-state-trigger). These are the properties available for a [Numeric State trigger](/docs/automation/trigger/#numeric-state-trigger).
@ -146,7 +146,7 @@ These are the properties available for a [Time trigger](/docs/automation/trigger
| `trigger.platform` | Hardcoded: `time` | `trigger.platform` | Hardcoded: `time`
| `trigger.now` | DateTime object that triggered the time trigger. | `trigger.now` | DateTime object that triggered the time trigger.
### Time Pattern ### Time pattern
These are the properties available for a [Time Pattern trigger](/docs/automation/trigger/#time-pattern-trigger). These are the properties available for a [Time Pattern trigger](/docs/automation/trigger/#time-pattern-trigger).
@ -155,7 +155,7 @@ These are the properties available for a [Time Pattern trigger](/docs/automation
| `trigger.platform` | Hardcoded: `time_pattern` | `trigger.platform` | Hardcoded: `time_pattern`
| `trigger.now` | DateTime object that triggered the time_pattern trigger. | `trigger.now` | DateTime object that triggered the time_pattern trigger.
### Persistent Notification ### Persistent notification
These properties are available for a [Persistent Notification trigger](/docs/automation/trigger/#persistent-notification-trigger). These properties are available for a [Persistent Notification trigger](/docs/automation/trigger/#persistent-notification-trigger).

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

@ -33,7 +33,7 @@ An automation can be triggered by an event, a certain entity state, at a given t
All triggers can be assigned an optional `id`. If the ID is omitted, it will instead be set to the index of the trigger. The `id` can be referenced from [trigger conditions and actions](/docs/scripts/conditions/#trigger-condition). The `id` does not have to be unique for each trigger, and it can be used to group similar triggers for use later in the automation (i.e., several triggers of different types that should all turn some entity on). All triggers can be assigned an optional `id`. If the ID is omitted, it will instead be set to the index of the trigger. The `id` can be referenced from [trigger conditions and actions](/docs/scripts/conditions/#trigger-condition). The `id` does not have to be unique for each trigger, and it can be used to group similar triggers for use later in the automation (i.e., several triggers of different types that should all turn some entity on).
### Video Tutorial ### Video tutorial
This video tutorial explains how trigger IDs work. This video tutorial explains how trigger IDs work.
<lite-youtube videoid="fE_MYcXYwMI" videotitle="How to use Trigger IDs in Home Assistant - Tutorial" posterquality="maxresdefault"></lite-youtube> <lite-youtube videoid="fE_MYcXYwMI" videotitle="How to use Trigger IDs in Home Assistant - Tutorial" posterquality="maxresdefault"></lite-youtube>
@ -673,7 +673,7 @@ If for your use case this is undesired, you could consider using the automation
The time trigger is configured to fire once a day at a specific time, or at a specific time on a specific date. There are three allowed formats: The time trigger is configured to fire once a day at a specific time, or at a specific time on a specific date. There are three allowed formats:
### Time String ### Time string
A string that represents a time to fire on each day. Can be specified as `HH:MM` or `HH:MM:SS`. If the seconds are not specified, `:00` will be used. A string that represents a time to fire on each day. Can be specified as `HH:MM` or `HH:MM:SS`. If the seconds are not specified, `:00` will be used.
@ -685,7 +685,7 @@ automation:
at: "15:32:00" at: "15:32:00"
``` ```
### Input Datetime ### Input datetime
The Entity ID of an [Input Datetime](/integrations/input_datetime/). The Entity ID of an [Input Datetime](/integrations/input_datetime/).
@ -740,7 +740,7 @@ automation:
entity_id: light.bedroom entity_id: light.bedroom
``` ```
### Multiple Times ### Multiple times
Multiple times can be provided in a list. Both formats can be intermixed. Multiple times can be provided in a list. Both formats can be intermixed.
@ -939,7 +939,7 @@ The sentences matched by this trigger will be:
Punctuation and casing are ignored, so "It's PARTY TIME!!!" will also match. Punctuation and casing are ignored, so "It's PARTY TIME!!!" will also match.
### Sentence Wildcards ### Sentence wildcards
Adding one or more `{lists}` to your trigger sentences will capture any text at that point in the sentence. A `slots` object will be [available in the trigger data](/docs/automation/templating#sentence). Adding one or more `{lists}` to your trigger sentences will capture any text at that point in the sentence. A `slots` object will be [available in the trigger data](/docs/automation/templating#sentence).
This allows you to match sentences with variable parts, such as album/artist names or a description of a picture. This allows you to match sentences with variable parts, such as album/artist names or a description of a picture.
@ -971,7 +971,7 @@ automation:
event: sunset event: sunset
``` ```
## Multiple Entity IDs for the same Trigger ## 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 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.

6
source/_docs/automation/yaml.markdown
View File

@ -112,7 +112,7 @@ action:
type: list type: list
{% endconfiguration %} {% endconfiguration %}
### Automation Modes ### Automation modes
Mode | Description Mode | Description
-|- -|-
@ -127,7 +127,7 @@ Mode | Description
## YAML Example ## YAML example
Example of a YAML based automation that you can add to `configuration.yaml`. Example of a YAML based automation that you can add to `configuration.yaml`.
@ -262,7 +262,7 @@ If you want to migrate your manual automations to use the editor, you'll have to
{% endraw %} {% endraw %}
### Deleting Automations ### Deleting automations
When automations remain visible in the Home Assistant Dashboard, even after having deleted in the YAML file, you have to delete them in the UI. When automations remain visible in the Home Assistant Dashboard, even after having deleted in the YAML file, you have to delete them in the UI.

14
source/_docs/blueprint/selectors.markdown
View File

@ -75,7 +75,7 @@ action:
The output of this selector is a list of actions. For example: The output of this selector is a list of actions. For example:
```yaml ```yaml
# Example Action selector output result # Example action selector output result
- service: scene.turn_on - service: scene.turn_on
target: target:
entity_id: scene.watching_movies entity_id: scene.watching_movies
@ -96,7 +96,7 @@ selected add-on.
This selector does not have any other options; therefore, it only has its key. This selector does not have any other options; therefore, it only has its key.
```yaml ```yaml
# Example Add-on selector # Example add-on selector
addon: addon:
``` ```
@ -201,10 +201,10 @@ The output of this selector is the area ID, or (in case `multiple` is set to
`true`) a list of area IDs. `true`) a list of area IDs.
```yaml ```yaml
# Example Area selector output result, when multiple is set to false # Example area selector output result, when multiple is set to false
living_room living_room
# Example Area selector output result, when multiple is set to true # Example area selector output result, when multiple is set to true
- living_room - living_room
- kitchen - kitchen
``` ```
@ -346,7 +346,7 @@ condition:
The output of this selector is a list of conditions. For example: The output of this selector is a list of conditions. For example:
```yaml ```yaml
# Example Condition selector output result # Example condition selector output result
- condition: numeric_state - condition: numeric_state
entity_id: "sensor.outside_temperature" entity_id: "sensor.outside_temperature"
below: 20 below: 20
@ -567,10 +567,10 @@ The output of this selector is the device ID, or (in case `multiple` is set to
`true`) a list of devices IDs. `true`) a list of devices IDs.
```yaml ```yaml
# Example Device selector output result, when multiple is set to false # Example device selector output result, when multiple is set to false
faadde5365842003e8ca55267fe9d1f4 faadde5365842003e8ca55267fe9d1f4
# Example Device selector output result, when multiple is set to true # Example device selector output result, when multiple is set to true
- faadde5365842003e8ca55267fe9d1f4 - faadde5365842003e8ca55267fe9d1f4
- 3da77cb054352848b9544d40e19de562 - 3da77cb054352848b9544d40e19de562
``` ```

2
source/_docs/blueprint/tutorial.markdown
View File

@ -248,7 +248,7 @@ Don't forget to reload automations after you make changes to your blueprint to h
![Screenshot of the blueprint UI](/images/blueprints/tutorial-ui.png) ![Screenshot of the blueprint UI](/images/blueprints/tutorial-ui.png)
## Video Tutorial ## Video tutorial
This video tutorial explains how to create a blueprint that toggles a light on motion when the lux value is below a certain threshold. This video tutorial explains how to create a blueprint that toggles a light on motion when the lux value is below a certain threshold.

2
source/_docs/configuration/customizing-devices.markdown
View File

@ -57,7 +57,7 @@ initial_state:
default: None default: None
{% endconfiguration %} {% endconfiguration %}
### Device Class ### Device class
Device class is currently supported by the following platforms: Device class is currently supported by the following platforms:

2
source/_docs/configuration/remote.markdown
View File

@ -23,7 +23,7 @@ A secure way to remotely access your Home Assistant is to use a Virtual Private
A VPN connection needs to be established before you can connect to your Home Assistant from outside your local network. The VPN makes this connection secure. When using the Home Assistant Companion app (such as on a mobile device), without this connection, your sensors will not update in Home Assistant. A VPN connection needs to be established before you can connect to your Home Assistant from outside your local network. The VPN makes this connection secure. When using the Home Assistant Companion app (such as on a mobile device), without this connection, your sensors will not update in Home Assistant.
## Port Forwarding ## Port forwarding
Set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching `<router model> port forwarding instructions`. You can use any free port on your router and forward that to port 8123. Set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching `<router model> port forwarding instructions`. You can use any free port on your router and forward that to port 8123.

2
source/_docs/configuration/securing.markdown
View File

@ -13,7 +13,7 @@ Here's the summary of what you *must* do to secure your Home Assistant system:
- **Note**: Storing secrets in `secrets.yaml` does not encrypt them. - **Note**: Storing secrets in `secrets.yaml` does not encrypt them.
- Regularly keep the system up to date - Regularly keep the system up to date
## Remote Access ## Remote access
If you want secure remote access, the easiest option is to use [Home Assistant cloud](/cloud/) by which you also [support](https://www.nabucasa.com/about/) the founders of Home Assistant. If you want secure remote access, the easiest option is to use [Home Assistant cloud](/cloud/) by which you also [support](https://www.nabucasa.com/about/) the founders of Home Assistant.

2
source/_docs/configuration/splitting_configuration.markdown
View File

@ -200,7 +200,7 @@ If you have many configuration files, Home Assistant provides a CLI that allows
- [Core](/common-tasks/core/#configuration-check) - [Core](/common-tasks/core/#configuration-check)
- [Supervised](/common-tasks/supervised/#configuration-check) - [Supervised](/common-tasks/supervised/#configuration-check)
## Advanced Usage ## Advanced usage
We offer four advanced options to include whole directories at once. Please note that your files must have the `.yaml` file extension; `.yml` is not supported. We offer four advanced options to include whole directories at once. Please note that your files must have the `.yaml` file extension; `.yml` is not supported.

6
source/_docs/configuration/templating.markdown
View File

@ -65,7 +65,7 @@ extensions:
- [Loop Controls](https://jinja.palletsprojects.com/en/3.0.x/extensions/#loop-controls) (`break` and `continue`) - [Loop Controls](https://jinja.palletsprojects.com/en/3.0.x/extensions/#loop-controls) (`break` and `continue`)
### Reusing Templates ### Reusing templates
You can write reusable Jinja templates by adding them to a `custom_templates` folder under your You can write reusable Jinja templates by adding them to a `custom_templates` folder under your
configuration directory. All template files must have the `.jinja` extension and be less than 5MiB. configuration directory. All template files must have the `.jinja` extension and be less than 5MiB.
@ -102,7 +102,7 @@ In your automations, you could then reuse this macro by importing it:
Extensions allow templates to access all of the Home Assistant specific states and adds other convenience functions and filters. Extensions allow templates to access all of the Home Assistant specific states and adds other convenience functions and filters.
### Limited Templates ### Limited templates
Templates for some [triggers](/docs/automation/trigger/) as well as `trigger_variables` only support a subset of the Home Assistant template extensions. This subset is referred to as "Limited Templates". Templates for some [triggers](/docs/automation/trigger/) as well as `trigger_variables` only support a subset of the Home Assistant template extensions. This subset is referred to as "Limited Templates".
@ -418,7 +418,7 @@ The same thing can also be expressed as a test:
{% endraw %} {% endraw %}
### Config Entries ### Config entries
- `config_entry_id(entity_id)` returns the config entry ID for a given entity ID. Can also be used as a filter. - `config_entry_id(entity_id)` returns the config entry ID for a given entity ID. Can also be used as a filter.

2
source/_docs/configuration/troubleshooting.markdown
View File

@ -115,7 +115,7 @@ To enable debug logging for an integration, go to **Settings** > **Devices & Ser
Once you enable debug logging, you ideally need to make the error happen. Run your automation, change up your device or whatever was giving you an error and then come back and disable the debug logging. Disabling the debug logging is the same as enabling, but now the button says **Disable Debug Logging**. After you disable it, you will be automatically prompted you to download your log file. Save this to a safe location to upload later. Once you enable debug logging, you ideally need to make the error happen. Run your automation, change up your device or whatever was giving you an error and then come back and disable the debug logging. Disabling the debug logging is the same as enabling, but now the button says **Disable Debug Logging**. After you disable it, you will be automatically prompted you to download your log file. Save this to a safe location to upload later.
### Download Diagnostics ### Download diagnostics
After you download logs, you will also want to download the diagnostics for the integration giving you trouble. If the integration provides diagnostics, it will appear in the three dot menu next to the integration configuration. After you download logs, you will also want to download the diagnostics for the integration giving you trouble. If the integration provides diagnostics, it will appear in the three dot menu next to the integration configuration.

2
source/_docs/configuration/yaml.markdown
View File

@ -93,7 +93,7 @@ light: !include lights.yaml
More information about this feature can also be found at [splitting configuration](/docs/configuration/splitting_configuration/). More information about this feature can also be found at [splitting configuration](/docs/configuration/splitting_configuration/).
## Common Issues ## Common issues
### found character '\t' ### found character '\t'

2
source/_docs/energy/electricity-grid.markdown
View File

@ -69,7 +69,7 @@ _Attention! Installing CT clamp sensor devices requires opening your electrical
Some energy providers will provide you real-time information about your usage and have this data integrated into Home Assistant. Some energy providers will provide you real-time information about your usage and have this data integrated into Home Assistant.
### Manual Integration ### Manual integration
If you manually integrate your sensors, for example, using the [MQTT](/integrations/mqtt) or [Template](/integrations/template) integrations: Make sure you set and provide the `device_class`, `state_class`, and `unit_of_measurement` for those sensors. If you manually integrate your sensors, for example, using the [MQTT](/integrations/mqtt) or [Template](/integrations/template) integrations: Make sure you set and provide the `device_class`, `state_class`, and `unit_of_measurement` for those sensors.

2
source/_docs/energy/faq.markdown
View File

@ -29,7 +29,7 @@ If you are using a 3rd party device (e.g. not reading directly from your utility
To accomplish such, you can use the [utility_meter integration](/integrations/utility_meter/). With this integration, you define as many tariffs as required (in accordance with your utility provider contract) and HA will be able to differentiate energy consumptions in each of the tariffs. Please note that each utility provider has its own time schedules for peak and off-peak and you are required to create an automation that switches the utility_meter entity from one tariff to the other. To accomplish such, you can use the [utility_meter integration](/integrations/utility_meter/). With this integration, you define as many tariffs as required (in accordance with your utility provider contract) and HA will be able to differentiate energy consumptions in each of the tariffs. Please note that each utility provider has its own time schedules for peak and off-peak and you are required to create an automation that switches the utility_meter entity from one tariff to the other.
## The Energy panel is not visible ## The energy panel is not visible
If you do not see the Energy panel in the sidebar, make sure you have not removed [`default_config:`](/integrations/default_config/) from your `configuration.yaml`. If you have, you will need to add the `energy:` integration manually. If you do not see the Energy panel in the sidebar, make sure you have not removed [`default_config:`](/integrations/default_config/) from your `configuration.yaml`. If you have, you will need to add the `energy:` integration manually.

2
source/_docs/energy/individual-devices.markdown
View File

@ -13,7 +13,7 @@ Smart plugs sit between the device and the outlet and measure the energy flowing
Depending on what protocols you use at home, you can use Zigbee, Z-Wave or Wi-Fi based plugs. Depending on what protocols you use at home, you can use Zigbee, Z-Wave or Wi-Fi based plugs.
### Smart Relays ### Smart relays
Smart relays sit behind your "normal" switches and make them smart. It allows you to control the devices via Home Assistant and via the connected buttons/switches. Smart relays sit behind your "normal" switches and make them smart. It allows you to control the devices via Home Assistant and via the connected buttons/switches.

6
source/_docs/frontend/icons.markdown
View File

@ -9,13 +9,13 @@ description: "Material Design Icons in the Home Assistant frontend"
Home Assistant utilizes the community-driven [Material Design Icons](https://pictogrammers.com/library/mdi/) (MDI) project for icons in the frontend. The icon library is a superset of the base icon library provided by Google and contains thousands of community-made icons for very specific applications, industries, and use-cases. Home Assistant utilizes the community-driven [Material Design Icons](https://pictogrammers.com/library/mdi/) (MDI) project for icons in the frontend. The icon library is a superset of the base icon library provided by Google and contains thousands of community-made icons for very specific applications, industries, and use-cases.
## Default Icons ## Default icons
Every entity in Home Assistant has a default icon assigned to it. There are way too many to list out here, but you'll see them in your dashboard. You can [customize any of your entities](/docs/configuration/customizing-devices/#icon) to change the icons displayed to you. Every entity in Home Assistant has a default icon assigned to it. There are way too many to list out here, but you'll see them in your dashboard. You can [customize any of your entities](/docs/configuration/customizing-devices/#icon) to change the icons displayed to you.
## Finding Icons ## Finding icons
### Icon Picker ### Icon picker
The most common way you can find icons is by using the icon picker built right into Home Assistant. Click into the "Icon" field when customizing an entity and start typing. The list will filter to icons that match your search criteria. You can also scroll through all available icons when the field is empty. The most common way you can find icons is by using the icon picker built right into Home Assistant. Click into the "Icon" field when customizing an entity and start typing. The list will filter to icons that match your search criteria. You can also scroll through all available icons when the field is empty.

4
source/_docs/locked_out.md
View File

@ -78,7 +78,7 @@ If you lose the password associated with the owner account and the steps above d
- `hassio` - `hassio`
- `cloud` - `cloud`
## Recovering Data for Home Assistant (including Supervised) ## Recovering data for Home Assistant (including Supervised)
Unless your SD card/data is corrupted, you can still get to your files or troubleshoot further. Unless your SD card/data is corrupted, you can still get to your files or troubleshoot further.
There are a few routes: There are a few routes:
@ -101,7 +101,7 @@ You will then be at the Home Assistant CLI, where you can run the custom command
- `dns logs` for checking DNS - `dns logs` for checking DNS
- etc (typing `help` will show more) - etc (typing `help` will show more)
## Accessing Files from the SD/HDD ## Accessing files from the SD/HDD
### Remove the SD and access the files from another computer ### Remove the SD and access the files from another computer

10
source/_docs/scripts.markdown
View File

@ -241,7 +241,7 @@ This action can use the same triggers that are available in an automation's `tri
{% endraw %} {% endraw %}
### Wait Timeout ### Wait timeout
With both types of waits it is possible to set a timeout after which the script will continue its execution if the condition/event is not satisfied. Timeout has the same syntax as `delay`, and like `delay`, also accepts templates. With both types of waits it is possible to set a timeout after which the script will continue its execution if the condition/event is not satisfied. Timeout has the same syntax as `delay`, and like `delay`, also accepts templates.
@ -275,7 +275,7 @@ You can also get the script to abort after the timeout by using optional `contin
Without `continue_on_timeout: false` the script will always continue since the default for `continue_on_timeout` is `true`. Without `continue_on_timeout: false` the script will always continue since the default for `continue_on_timeout` is `true`.
### Wait Variable ### Wait variable
After each time a wait completes, either because the condition was met, the event happened, or the timeout expired, the variable `wait` will be created/updated to indicate the result. After each time a wait completes, either because the condition was met, the event happened, or the timeout expired, the variable `wait` will be created/updated to indicate the result.
@ -392,7 +392,7 @@ The following automation example shows how to capture the custom event `event_li
This action allows you to repeat a sequence of other actions. Nesting is fully supported. This action allows you to repeat a sequence of other actions. Nesting is fully supported.
There are three ways to control how many times the sequence will be run. There are three ways to control how many times the sequence will be run.
### Counted Repeat ### Counted repeat
This form accepts a count value. The value may be specified by a template, in which case This form accepts a count value. The value may be specified by a template, in which case
the template is rendered when the repeat step is reached. the template is rendered when the repeat step is reached.
@ -473,7 +473,7 @@ repeat:
{% endraw %} {% endraw %}
### While Loop ### While loop
This form accepts a list of conditions (see [conditions page] for available options) that are evaluated _before_ each time the sequence This form accepts a list of conditions (see [conditions page] for available options) that are evaluated _before_ each time the sequence
is run. The sequence will be run _as long as_ the condition(s) evaluate to true. is run. The sequence will be run _as long as_ the condition(s) evaluate to true.
@ -514,7 +514,7 @@ For example:
{% endraw %} {% endraw %}
### Repeat Until ### Repeat until
This form accepts a list of conditions that are evaluated _after_ each time the sequence This form accepts a list of conditions that are evaluated _after_ each time the sequence
is run. Therefore the sequence will always run at least once. The sequence will be run is run. Therefore the sequence will always run at least once. The sequence will be run

2
source/_docs/tools/dev-tools.markdown
View File

@ -58,7 +58,7 @@ brightness: 255
rgb_color: [255, 0, 0] rgb_color: [255, 0, 0]
``` ```
## Template Editor ## Template editor
The Template Editor provides a way to quickly test templates prior to placing them into automations and scripts. A code editor is on the left side and your real-time output is displayed in the preview on the right side. The Template Editor provides a way to quickly test templates prior to placing them into automations and scripts. A code editor is on the left side and your real-time output is displayed in the preview on the right side.

6
source/_docs/tools/quick-bar.markdown
View File

@ -26,7 +26,7 @@ Type these from anywhere in the application to launch the dialog.
The application must have focus for the hotkey to register. If the dialog doesn't launch, try clicking into an empty part of the main content area of Home Assistant and type it again. The application must have focus for the hotkey to register. If the dialog doesn't launch, try clicking into an empty part of the main content area of Home Assistant and type it again.
</div> </div>
## Entity Filter ## Entity filter
*Hotkey: `e`* *Hotkey: `e`*
@ -41,7 +41,7 @@ Once launched, start typing your entity id (or ["bits and pieces" of your entity
This is helpful when, say, you are in the middle of writing an automation and need some quick insight about an entity but don't want to navigate away to Developer Tools. This is helpful when, say, you are in the middle of writing an automation and need some quick insight about an entity but don't want to navigate away to Developer Tools.
## Command Palette ## Command palette
*Hotkey: `c`* *Hotkey: `c`*
@ -66,7 +66,7 @@ Type | Available |
Create [`my`](/integrations/my) links from any supported page in the user interface, when invoked on a supported page it will open a new tab that will allow you to share the link in different formats. Create [`my`](/integrations/my) links from any supported page in the user interface, when invoked on a supported page it will open a new tab that will allow you to share the link in different formats.
## Disabling Shortcuts ## Disabling shortcuts
You can enable or disable all of Home Assistant's keyboard shortcuts by going to your User Profile and clicking the "Keyboard Shortcuts" toggle button. You can enable or disable all of Home Assistant's keyboard shortcuts by going to your User Profile and clicking the "Keyboard Shortcuts" toggle button.

4
source/_docs/z-wave/controllers.markdown
View File

@ -52,7 +52,7 @@ If you are just starting out, we recommend that you purchase a 700 series contro
If you're using Home Assistant OS, Supervised, or Container, it's recommended to use a USB stick, not a module. Passing a module through Docker is more complicated than passing a USB stick through. If you're using Home Assistant OS, Supervised, or Container, it's recommended to use a USB stick, not a module. Passing a module through Docker is more complicated than passing a USB stick through.
</div> </div>
## Stick Alternatives ## Stick alternatives
The alternative to a stick is a hub that supports Z-Wave. Home Assistant supports the following hubs with Z-Wave support: The alternative to a stick is a hub that supports Z-Wave. Home Assistant supports the following hubs with Z-Wave support:
@ -61,7 +61,7 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
- [SmartThings](/integrations/smartthings/) - [SmartThings](/integrations/smartthings/)
- [Z-Wave.Me Z-Way](/integrations/zwave_me) - [Z-Wave.Me Z-Way](/integrations/zwave_me)
## Controller Notes ## Controller notes
### 800 Series Controllers ### 800 Series Controllers