From f6ce417e02337b85a603b4ec19e35c9299632c27 Mon Sep 17 00:00:00 2001 From: Logan Marchione Date: Mon, 28 Sep 2020 11:27:55 +0000 Subject: [PATCH] Update HomeKit docs with warning about multiple instances (#14633) --- source/_integrations/homekit.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown index d45c9a83c20..7963487d5d1 100644 --- a/source/_integrations/homekit.markdown +++ b/source/_integrations/homekit.markdown @@ -291,6 +291,12 @@ Unfortunately, `HomeKit` doesn't support any persistent storage - only the confi A common situation might be if you decide to disable parts of the configuration for testing. Please make sure to disable `auto start` and `turn off` the `Start HomeKit` automation (if you have one). +### Multiple HomeKit instances + +If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Integrations**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port. + +It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML. + ## Disable Auto Start Depending on your setup, it might be necessary to disable `Auto Start` for all accessories to be available for `HomeKit`. Only those entities that are fully set up when the `HomeKit` integration is started, can be added. To start `HomeKit` when `auto_start: false`, you can call the service `homekit.start`.