jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-17 14:26:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Homekit zeroconf default interface configuration comes from zeroconf (#13623)

Browse Source 
* merge

* homekit zeroconf default interface configuration comes from zeroconf
This commit is contained in:
J. Nick Koston 2020-06-03 09:15:17 -05:00 committed by GitHub
parent 0456cc36d7
commit ef3c79a936
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
source/_integrations/homekit.markdown
View File

@ -90,11 +90,6 @@ homekit:
required: false
type: boolean
default: false
zeroconf_default_interface:
description: By default, zeroconf will attempt to bind to all interfaces. For systems running using network isolation or similar, this may result in HomeKit not being seen on the network. Change this option to `true` if HomeKit cannot be discovered.
required: true
type: boolean
default: false
advertise_ip:
description: If you need to override the IP address used for mDNS advertisement. (For example, using network isolation in Docker and together with an mDNS forwarder like `avahi-daemon` in reflector mode)
required: false
@ -422,14 +417,13 @@ To avoid any errors, after you have successfully paired your Home Assistant Brid
The `advertise_ip` option can be used to run this integration even inside an ephemeral Docker container with network isolation enabled, e.g., not using the host network.
You may also need to set `zeroconf_default_interface` to `true`.
You may also need to set `default_interface` to `true` in the `zeroconf` integration.
To use `advertise_ip`, add the option to your `homekit` configuration:
```yaml
homekit:
advertise_ip: "STATIC_IP_OF_YOUR_DOCKER_HOST"
zeroconf_default_interface: true
```
Restart your Home Assistant instance. This feature requires running an mDNS forwarder on your Docker host, e.g., `avahi-daemon` in reflector mode. This kind of setup most likely requires `safe_mode` during the bridge setup.
@ -565,7 +559,7 @@ Configure the network mode as `networkbridge`. Otherwise the Home Assistant Brid
Pairing eventually fails, you might see and an error message `NonUniqueNameException`. Add the `safe_mode` option to your configuration, see [safe_mode](#safe-mode).
If [safe_mode](#safe-mode) is not successful, you likely need to enable `zeroconf_default_interface: true` and set a unique name such as `name: MyHASS42`.
If [safe_mode](#safe-mode) is not successful, you likely need to enable `default_interface: true` in the `zeroconf` integration configuration and set a unique name such as `name: MyHASS42`.
If you had previously paired (even unsuccessfully), you may need to delete your `.homekit.state` file in order to able to successfully pair again. See [Errors during pairing](#errors-during-pairing).