jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Overriding build-components within subfolders. (#1705)

Browse source 
It was not explained that you had to create a folder inside `config/custom_components` if the original component was also in a subfolder.
This commit is contained in:
Michaël Arnauts 2017-01-03 19:41:12 +01:00 • committed by Fabian Affolter
parent 92d8054f31
commit e0f1b354ee
No known key found for this signature in database
GPG key ID: E23CD2DD36A4397F
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/developers/component_loading.markdown
View file

@ -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.
<p class='note warning'>
You can override a built-in component by having a component with the same name in your <code>config/custom_components</code> 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 <code>config/custom_components</code> folder. If the build-in component is inside a subfolder, take care to place your customization in a folder with the same name in <code>config/custom_components/*folder*</code>. Note that overriding build-in components is not recommended and will probably break things!
</p>
<p class='note'>