mirror of
https://github.com/home-assistant/developers.home-assistant.git
synced 2025-11-13 21:10:30 +00:00
Collection of fixes and improvements (#516)
This commit is contained in:
@@ -7,8 +7,8 @@ Each integration is stored inside a directory named after the integration domain
|
||||
|
||||
The bare minimum content of this folder looks like this:
|
||||
|
||||
- `manifest.json`: The manifest file describes the integration and its dependencies. [More info](creating_integration_manifest.md)
|
||||
- `__init__.py`: The component file. If the integration only offers a platform, you can keep this file limited to a docstring introducing the integration `"""The Mobile App integration."""`.
|
||||
- `manifest.json`: The manifest file describes the integration and its dependencies. [More info](creating_integration_manifest.md)
|
||||
- `__init__.py`: The component file. If the integration only offers a platform, you can keep this file limited to a docstring introducing the integration `"""The Mobile App integration."""`.
|
||||
|
||||
## Integrating devices - `light.py`, `switch.py` etc
|
||||
|
||||
@@ -25,7 +25,7 @@ If your integration is going to register services, it will need to provide a des
|
||||
|
||||
Home Assistant will look for an integration when it sees the domain referenced in the config file (i.e. `mobile_app:`) or if it is a dependency of another integration. Home Assistant will look at the following locations:
|
||||
|
||||
* `<config directory>/custom_components/<domain>`
|
||||
* `homeassistant/components/<domain>` (built-in integrations)
|
||||
- `<config directory>/custom_components/<domain>`
|
||||
- `homeassistant/components/<domain>` (built-in integrations)
|
||||
|
||||
You can override a built-in integration by having an integration with the same domain in your `config/custom_components` folder. Note that overriding built-in components is not recommended as you will no longer get updates. It is recommended to pick a unique name.
|
||||
|
||||
Reference in New Issue
Block a user