You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/_docs/configuration/packages.markdown
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ footer: true
10
10
redirect_from: /topics/packages/
11
11
---
12
12
13
-
Packages in Home Assistant provides a way to bundle different component's configuration together. We were already introduced to the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the component key in the main `configuration.yaml` file. With packages we have a way to include different components, or parts of configuration using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
13
+
Packages in Home Assistant provides a way to bundle different component's configuration together. We already learned about the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the component key in the main `configuration.yaml` file. With packages we have a way to include different components, or different configuration parts using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
14
14
15
-
Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a packages name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as:
15
+
Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a package name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as:
16
16
17
17
```yaml
18
18
homeassistant:
@@ -22,7 +22,7 @@ homeassistant:
22
22
...package configuration here...
23
23
```
24
24
25
-
The package configuration can include: `switch`, `light`, `automation`, `groups` or the majority of the Home Assistant components.
25
+
The package configuration can include: `switch`, `light`, `automation`, `groups`, or most other Home Assistant components.
26
26
27
27
It can be specified inline or in a separate YAML file using `!include`.
28
28
@@ -81,7 +81,7 @@ Components inside packages can only specify platform entries using configuration
81
81
82
82
### {% linkable_title Create a packages folder %}
83
83
84
-
One way to organize packages would be to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages:
84
+
One way to organize packages is to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages:
0 commit comments