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-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Additional troubleshooting step to fix PIN error (#5309)

Browse Source 
* Additional troubleshooting step to fix PIN error

Persistent notification of PIN doesn't appear when too many entities are included on initial start.  Adding a filter allows the PIN to properly present.

* Added Error Notation

Added Error notation to PIN presentation Issue

* ✏️ Language tweaks
This commit is contained in:
Jeremy Roe 2018-06-28 15:34:53 -05:00 committed by Alok Saboo
parent 4c0b5272da
commit 4787b97074
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
source/_components/homekit.markdown
View File

@ -291,3 +291,17 @@ logger:
- The configuration entries for `homekit` and the `component` that is causing the issue.
- The log / traceback you have generated before.
- Screenshots of the failing entity in the `states` panel.
## {% linkable_title Troubleshooting PIN not appearing %}
In some instances, the PIN will not appear as a persistent status or in the log files despite deleting `.homekit.state`, enabling logging, and reboot. The log files will include the error ```Duplicate AID found when attempting to add accessory```.
In such cases, modifying your configuration.yaml to add a filter limiting the included entities similar to the following:
```yaml
filter:
include_domains:
- light
```
Restart Home-Assistant and re-attempt pairing - a persistent status should now correctly appear.