This is maddening. I cannot make Homekit work on my Raspberry Pi. I’ve tried everything in here.
cleared Pairings, allowed unauthenticated, cleared out the homekit.json file, using a new code, i’ve tried reinstalling the whole openhabian image… nothing seems to work.
do you even see “openhab” on homekit ?
I do. It shows up as an available device/accessory. It hangs for a couple minutes while it tries to connect to the device, then fails.
and whats in the log ?
this:
2018-08-21 22:29:13.065 [WARN ] [homekit.internal.HomekitAuthInfoImpl] - Could not find existing MAC in org.eclipse.smarthome.storage.json.internal.JsonStorage. Generating new MAC. This will require re-pairing of iOS devices.
EDIT: Looks like this line above is just from me trying to clear the pairings.
there’s also a ton of this in various places:
2018-08-21 22:29:50.303 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:wemo_switch_Noisermaker_Homekit in ManagedMetadataProviderImpl, because it does not exists.
2018-08-21 22:29:50.319 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:wemo_switch_ChristmasTree_Homekit in ManagedMetadataProviderImpl, because it does not exists.
Same error on a handful of devices where THING_Homekit is throwing errors.
I can’t find any errors or even reaction when I try to pair in the log.
That error is thrown when you have items configured with a homekit tag without it being bound to a channel.
If an item is not bound to a channel, remove the [“tag”] from the item.
I myself am having issues with the homekit integration as well, but in my case nothing about homekit is mentioned in any log, no matter what I do.
I tried all the thing I could find, but nothing improves.
See my topic at HomeBridge not accepting clients
keep in mind, this topic has nothing to do with HomeBridge!
Don’t be mislead by the name, it should be HomeKit 
Anyways, I have the exact same problems.
I have also tried the HomeBridge solutions mentioned in this topic, and it works flawlesly. Just wondering why the HomeKit Integration is such a pain to get working.
Same here - can’t pair, tried all advices from this and other threads, nothing showing in the log 
UPDATE: I got it working after configuring openhabian to use the latest snapshot build…
had the problem the second time, too. for me worked to put the openhab-ip into the .cfg-file (parameter: networkInterface)
hope this will help you, too, … or me if it comes to a third time 
Had same problem on a fresh installation on RPi3.
After many attempts, it worked by adding openhab IP into the Homekit Configuration panel (Paper UI).
where did you enter the openhab IP in the homekit configuration panel? I don’t see any fields for it.
son of a gun, that worked!
Nice! Glad that got it for you!
I had a different problem, tried everything mentioned here but nothing worked. In my homekit.json the mac address was missing, thats why the following worked for me:
I had the same issue on 2.0 release. Turnes out that after enabling the homekit integration, you have to restart openhab to get the JSON persistance to write the mac address. Only after that, you should do the pairing.
Steps I took:
Thank you so much!! Finally 
Fresh OH 2.4 and iOS 13 / iPhone 7
i cant get Homekit to work, its frustrating.
i’ve done every step 100 times and i always end up with “openhab couldn’t be added” in iOS.
iPhone: 192.168.1.10
OH: 192.168.1.100
2019-11-29 07:59:19.073 [INFO ] [com.beowulfe.hap.HomekitRoot ] - Added accessory Stehlampe (IT)
2019-11-29 07:59:19.084 [INFO ] [pl.http.impl.NettyHomekitHttpService] - Resetting connections
2019-11-29 07:59:19.086 [INFO ] [com.beowulfe.hap.HomekitRoot ] - Added accessory LED Mini Controller
2019-11-29 07:59:19.098 [INFO ] [pl.http.impl.NettyHomekitHttpService] - Resetting connections
2019-11-29 07:59:19.105 [DEBUG] [org.openhab.io.homekit ] - ServiceEvent REGISTERED - {org.openhab.io.homekit.Homekit}={port=9124, service.id=432, thermostatOffMode=Off, service.bundleid=261, service.scope=bundle, thermostatCoolMode=CoolOn, component.name=org.openhab.homekit, service.config.label=HomeKit Integration, component.id=277, thermostatAutoMode=Auto, pin=031-45-157, networkInterface=192.168.1.100, service.config.category=io, useFahrenheitTemperature=false, thermostatHeatMode=HeatOn, service.config.description.uri=io:homekit, service.pid=org.openhab.homekit} - org.openhab.io.homekit
2019-11-29 08:00:19.910 [TRACE] [pl.http.impl.NettyHomekitHttpService] - READ UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 58, cap: 1024) [/192.168.1.10:49719]:
2019-11-29 08:00:19.912 [INFO ] [.hap.impl.http.impl.AccessoryHandler] - New homekit connection from /192.168.1.10:49719
2019-11-29 08:00:19.957 [INFO ] [ap.impl.http.HomekitClientConnection] - 404 /identify
2019-11-29 08:00:19.970 [TRACE] [pl.http.impl.NettyHomekitHttpService] - WRITE UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 69, cap: 256) [/192.168.1.10:49719]:
2019-11-29 08:00:27.416 [TRACE] [pl.http.impl.NettyHomekitHttpService] - READ UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 125, cap: 1024) [/192.168.1.10:49719]:
2019-11-29 08:00:28.872 [INFO ] [ap.impl.http.HomekitClientConnection] - 200 /pair-setup
2019-11-29 08:00:28.880 [TRACE] [pl.http.impl.NettyHomekitHttpService] - WRITE UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 513, cap: 1024) [/192.168.1.10:49719]:
2019-11-29 08:00:30.286 [TRACE] [pl.http.impl.NettyHomekitHttpService] - READ UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 512, cap: 512) [/192.168.1.10:49719]:
2019-11-29 08:00:30.293 [TRACE] [pl.http.impl.NettyHomekitHttpService] - READ UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 66, cap: 512) [/192.168.1.10:49719]:
2019-11-29 08:00:30.912 [INFO ] [ap.impl.http.HomekitClientConnection] - 200 /pair-setup
2019-11-29 08:00:30.915 [TRACE] [pl.http.impl.NettyHomekitHttpService] - WRITE UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 172, cap: 256) [/192.168.1.10:49719]:
2019-11-29 08:00:31.029 [TRACE] [pl.http.impl.NettyHomekitHttpService] - READ UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 280, cap: 8192) [/192.168.1.10:49719]:
2019-11-29 08:00:31.381 [INFO ] [ap.impl.jmdns.JmdnsHomekitAdvertiser] - Re-creating service due to change in discoverability to false
2019-11-29 08:00:33.384 [INFO ] [ap.impl.jmdns.JmdnsHomekitAdvertiser] - Registering _hap._tcp.local. on port 9124
2019-11-29 08:00:33.411 [INFO ] [ap.impl.http.HomekitClientConnection] - 200 /pair-setup
2019-11-29 08:00:33.413 [INFO ] [.hap.impl.http.impl.AccessoryHandler] - Terminated homekit connection from /192.168.1.10:49719
2019-11-29 08:00:33.414 [TRACE] [pl.http.impl.NettyHomekitHttpService] - WRITE UnpooledUnsafeDirectByteBuf(ridx: 0, widx: 244, cap: 256) [/192.168.1.10:49719]:
{
"privateKey": {
"class": "java.lang.String",
"value": "XXXXXXXXXXXXXXXXX"
},
"salt": {
"class": "java.lang.String",
"value": "43581927356803xxxxxxx8450167975672"
},
"mac": {
"class": "java.lang.String",
"value": "xx:xx:xx:xx:xx"
}
}
The search function would have taken you to one of the ios13 threads. There is a updated version of the 2.4 binding available somewhere and also latest 2.5 milestone contains a fix for this issue.