From b56d61193852ea103546e2f31a8ba020bf0e9e02 Mon Sep 17 00:00:00 2001 From: Vip0r Date: Wed, 10 Nov 2021 12:05:24 +0100 Subject: [PATCH] Changed override instructions (#1025) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Joakim Sørensen Co-authored-by: Martin Hjelmare --- docs/creating_integration_file_structure.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/creating_integration_file_structure.md b/docs/creating_integration_file_structure.md index c1683442..ac7d38e7 100644 --- a/docs/creating_integration_file_structure.md +++ b/docs/creating_integration_file_structure.md @@ -28,4 +28,5 @@ Home Assistant will look for an integration when it sees the domain referenced i - `/custom_components/` - `homeassistant/components/` (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. +You can override a built-in integration by having an integration with the same domain in your `/custom_components` folder. [The `manifest.json` file requires a version tag when you override a core integration](creating_integration_manifest/#version). An overridden core integration can be identified by a specific icon in the upper right corner of the integration box in the overview [![Open your Home Assistant instance and show your integrations.](https://my.home-assistant.io/badges/integrations.svg)](https://my.home-assistant.io/redirect/integrations/) +Note that overriding built-in integrations is not recommended as you will no longer get updates. It is recommended to pick a unique name.