Skip to content

Cleanup and dedupe troubleshooting in homekit #12999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
frenck merged 1 commit into from
Apr 16, 2020
Merged

Cleanup and dedupe troubleshooting in homekit #12999

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions source/_integrations/homekit.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -348,14 +348,7 @@ homekit:
```

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.

## Troubleshooting

If you see a traceback mentioning `zeroconf.NonUniqueNameException` in your log you likely need to
enable `zeroconf_default_interface: true` and set a unique name `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.


## Supported Components

The following integrations are currently supported:
Expand Down Expand Up @@ -433,7 +426,7 @@ Remember that the iOS device needs to be in the same local network as the Home A

#### `Home Assistant Bridge` doesn't appear in the Home App (for pairing) - Docker

Set `network_mode: host`. If you have further problems this [issue](https://github.com/home-assistant/home-assistant/issues/15692) might help.
Set `network_mode: host` in your `docker-compose.yaml`. If you have further problems this [issue](https://github.com/home-assistant/home-assistant/issues/15692) might help.

You can also try to use `avahi-daemon` in reflector mode together with the option `advertise_ip`, see above.

Expand All @@ -445,6 +438,10 @@ 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 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).

#### Pairing hangs - only works with debug configuration

Pairing works fine when the filter is set to only include `demo.demo`, but fails with normal configuration. See [specific entity doesn't work](#specific-entity-doesnt-work)
Expand Down