From 4f0812d351aee9678c3eeae73c97097e0593bd03 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Fri, 13 Sep 2019 12:34:32 +0100 Subject: [PATCH] The lack of reload is gone (#10357) The ability to reload automations etc in packages has long been addressed, apparently --- source/_docs/configuration/packages.markdown | 4 ---- 1 file changed, 4 deletions(-) diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index 444c717a5e4..44bdad8a3c5 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -6,10 +6,6 @@ redirect_from: /topics/packages/ Packages in Home Assistant provide 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 integration 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). -
-Note that if you use packages for your configuration, the configuration reloading buttons in the configuration panel will not reload your packages. -
- 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: ```yaml