From e0f1b354eed56986ea83604d25e7239488f23f44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C3=ABl=20Arnauts?= Date: Tue, 3 Jan 2017 19:41:12 +0100 Subject: [PATCH] Overriding build-components within subfolders. (#1705) It was not explained that you had to create a folder inside `config/custom_components` if the original component was also in a subfolder. --- source/developers/component_loading.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/component_loading.markdown b/source/developers/component_loading.markdown index 35b50ee975c..f57148ec8b5 100644 --- a/source/developers/component_loading.markdown +++ b/source/developers/component_loading.markdown @@ -17,7 +17,7 @@ A component will be loaded on start if a section (ie. `light:`) for it exists in Once loaded, a component will only be setup if all dependencies can be loaded and are able to setup. Keep an eye on the logs to see if your component could be loaded and initialized.

-You can override a built-in component by having a component with the same name in your config/custom_components folder. This is not recommended and will probably break things! +You can override a built-in component by having a component with the same name in your config/custom_components folder. If the build-in component is inside a subfolder, take care to place your customization in a folder with the same name in config/custom_components/*folder*. Note that overriding build-in components is not recommended and will probably break things!