core: Unable to pair HomeKit device: Koogeek LS1

Home Assistant release with the issue: 0.91.4

Last working Home Assistant release (if known): N/A

Operating environment (Hass.io/Docker/Windows/etc.):

System param	value
arch	x86_64
dev	false
docker	true
hassio	false
os_name	Linux
python_version	3.7.3
timezone	Europe/Paris
version	0.91.4
virtualenv	false

Component/platform:

https://www.home-assistant.io/components/homekit_controller/

Description of problem:

Hello,

I am trying to pair my Koogeek LS1 (my first HomeKit HA pairing) for an automation, but I am facing some problems :

HA recognize the device hours after I powered it
I have two Koogeek LS1 actually and when HA recognize them, all friendly names are “LS1”, so … how should I know which one is it ? (Display “Koogeek LS1” may be better, and when this name isn’t unique it may be nice to append the MAC address in parentheses 😉)
After clicking on the configuration button, it is asking me for the HomeKit code, nice ! But could you add the pattern (if there is) ? Because I don’t know if I should enter XXX-XX-XXX (which is my pattern) or XXXXXXXX.
No success or fail feedback are comming to the configure popup (that also explain my disappointment of the point 2 and 3)
No log are printed !

I did : I solved the problem of the 2 LS1 by unplugged one (old fashon way 😄). I reset the LS1, which was previously paired with my iPhone. I tryed all pattern of the HomeKit code (XXX-XX-XXX and XXXXXXXX) I tryed to just give the Wi-Fi to the LS1 but to pairing with my iPhone. Of course, restart HA and LS1. I looked at issues in GitHub, but no log to find any good match.

Nothing works.

I have the /config/.homekit folder created and empty.

configuration.yaml

discovery:
  enable:
    - homekit

Traceback (if applicable):

No log at all 😢

Additional information:

Maybe linked with #23189, #18949, #23172 and #15692

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 33 (28 by maintainers)

Most upvoted comments

OK, so zeroconf is awesome, it’s working perfectly now !!!

I plugged only one LS1, add the zeroconf component and restart HA, the LS1 was recognized directly after HA started.

And then I plugged the other one, and it took 10s to discover it.

I’m closing the issue.

Quentame on Jul 10, 2019

Have actually managed to fix point (2) in my local dev environment, but it’s going to be in 0.94 (lots of large pending changes first).

The best workaround for (1) atm is to restart HA after your device is in pairing mode. HA will do a scan at boot and after about 30s your device should show up. I’m not sure how frequent scans are after that. I think the core team might be making improvements around discovery but I can’t help with this bit atm.

For (3), it is definitely always XXX-XX-XXX for all HomeKit devices, regardless of what the label says. It’s part of the crypto implementation so if a manufacturer deviates from this it wont work with an iPhone. Validation has been added for this and its trickling its way down from unmerged Github branches. But we need to update the input text to be clearer too.

There should normally be a popup! So this must be an ‘unusual’ error.

On this version of HA i’d expect LS1 to work so can you confirm it’s version for me.

Then one LS1 at a time:

if you have /config/configuration.yaml, make sure /config/.homekit exists (you said that it did, but i wanted to make sure it was relative to your configuration.yaml in particular. I often say /config/.homekit when its just a path i made up).
reset your LS1 (press and hold button till it glows red)
pair it with your iPhone
unpair it (by tapping on its detail panel and choosing remove accessory)
restart HA (this will remove any pairings in memory and force discovery to run)
try to pair

I followed this procedure with my LS1 and it works.

Jc2k on Apr 22, 2019