[SOLVED] HomeKit Integration - Pairing Problems (iOS 10 - iOS 14)

can you try with only one accessory. the simple one, something like light.

I tried all your suggested steps above, however, HomeKit is keeping adding openHAB as a device not as a bridge. I‘m getting out of ideas. I removed my complete home from HomeKit, made several iterations of the recommendations above, with no success. Would be grateful for any guidance! I‘m pretty new to openHAB and did quite some progress on other stuff, so things start working for me but I got completely stuck with HomeKit.

do you have any items tag with homekit tag? what you see in home app?
if you have access to karaf console, what you get if you execute there

homekit list

Yes, I‘ve one WeMo Outlet tagged with HomeKit metadata. The list command in karaf returns nothing.image

I believe this is the bridge itself not the „device“. You need to delete the bridge in Homekit, Clear the pairings via Karaf (and select a new pin in OH). Then you should be able again to add the homekit-bridge.

if karaf returns nothing then the item is not tagged correctly. the list in the karaf is the list home app receives.
check your tagging

Thank you for your willingness to help!
I removed the tagging from the WeMo and followed the whole remove, clean-up and restart procedure described above again. I found that I left out one part of step 8 which is another restart of OH (setup HomeKit and restart OH). Which of both actions (or both?) did the trick I don’t know, but now I could add OH as Bridge (and not as device). It also displayed for a while the temperature of the Netatmo sensor in HomeKit, however I messed that up again by trying to add another temperature sensor (this time outside temp) to the game.
Is it necessary to do the whole procedure after every change in the metadata tagging? Just changing the metadata appears not to translate to what karaf reports with the list command.

Definetly no need for a restart after every change!

If you have a working „Thing/Item“ in Homekit just add one after the one. Most important is deleting the bridge in HK and waiting a bit. Clearing the pairings and then readding the bridge with one working item and continue.

there was a bug in 3.0 version of homekit binding that ignored metadata changes. basically, only change in non-metadata would trigger refresh of accessory.
bug was fixed in the recent snapshot releases.

an ugly workaround if you dont have the fixed version - after adding metadata change something on the non-metadata, e.g. name of the item. this would trigger the refresh.
no openhab, binding, repairing should be needed

Thank you both for the reassuring and explaining answers! I‘ll try again after work today. (And will find out how to install Snapshot releases).

Hello!
I have the same problem as the Topic-Author.
I use the metadata by giving them into the items-files.

To get the items into Homekit.App on the iPad, I have to follow the instructions by RiotMOde (steps 1 to 8 (using WindowsExplorer)). Then in the log of Openhab3 shows up that there are items found for Homekit. In the Homekit.App there are the “old” ones. I have to delete the openhab-Bridge. After new pairing I get all the items.

My questions:

  1. Is there a clever/better way for integrating new items to Homekit? Especially for using the code-files which I replace with the updates.

  2. By deleting the openhab-Bridge in Homekit ALL Automations and Scenes are deleted, too. That means, that I have to create them again.

  3. Is it possible to give more Data into the Metadata? For example the room information. Now I have to use a special Name for each item (e.g. “Light Bath”) to not confuse them. After pairing I have to rename every item (60+). In Homekit.App the Items are sorted by room which means that the room-information isn`t needed in the name but you have to specify a room for each item. Wouldn´t it be great when pairing with the room (and favourite) information would be integrated into Homekit.

Hope you can understand my questions.

Hi Friedo,

i assume, Homekit.App is the native home app that is on all apple devices, right?

regarding your questions:

  1. and 2.
    actually, the accessories should get refreshed in home app automatically, few seconds after you have updated your items files. there is no need to remove the bridge and re-add. this should really the last option.

if this does not happen automatically, you can

  • try to rename an existing item, e.g.
    if you have
    Rollershutter window_covering "Window Rollershutter" {homekit = "WindowCovering"}
    make it to
    Rollershutter window_covering2 "Window Rollershutter" {homekit = "WindowCovering"}

  • try to restart openhab or homekit binding. without removing bridge, clearing cache, etc. just restart.

  • make sure you dont have apple tv and ipad running in homekit bridge mode, sometime it keeps the old accessory for a longer time

  • if it still does not work, please share you log files and i will take a look.

  1. regarding additional metadata and especially room names - unfortunately it is not possible. the homekit protocol does not support it.

but try to use this naming convention “room_name item_name”, e.g. “Bath Light”.
in my case, if you would add this item to the room “Bath” home app would hide “Bath”, so, in the room “bath” i have only item “Light”.

1 Like

Correct.

I will try it.
EDIT: Yes, it´s working. The changed items are marked as Favorite and belong to the room of the iPad. Unchanged item still belong to scnes. Hope it does remove Homekit-groups when there is a small update to an item.

read about this option, too. This is not very handy…
EDIT: For that I have to change the names in .things, .items (and .sitemap). Did not use it - was not necessary.

The iPad is a “Steuerzentrale”/Conrolunit not a Bridge. There is only the openhab-Bridge as Bridge.

Sounds nice, already had that in first try. Will try it again.
EDIT: now I´m familar with this function. In items file the label has to be as you have described. That works nicely.

So my questions are solved. - for now :wink: .Thanks a lot to yfre.

1 Like

Thanks so much! This did the trick! :slight_smile:

How would this work in a docker container environment ? I’m running OH in a docker on a Synology NAS. I have a terminal in the docker but it doesn’t recognise ssh command.

Anyone an idea on how to do this is a docker ? I also have the problem that connection is lost every time Openhab reboots

Not an expert on Synology, but did you try to access your enviroment on the Synology via a terminal from a remote PC? What’s the precise error message? Screenshot etc could help.

i assume, you are rebooting not OH in in the container but the docker container.
there were some reports with OH in docker + homekit + ipv6. deactivating ipv6 solved for some the issue with homekit connection.
check this thread

@yfre Eugen thanks a lot !! that topic really helped. Changing use of OHmDNS from true to false solved it :slight_smile:

1 Like

Hello Friends,
For a year now I’ve been using OpenHAB as a regular install (not openHABian) on Raspberry Pi 4, and I set it up successfully to work with the Homekit binding.
Today, I upgraded my home server to an Intel based CPU running UnRAID.
I installed OpenHAB as a docker app from the UnRAID community apps repository, and continued to recreate manually the previous OpenHAB setup I used on the Raspberry Pi 4.
I managed to properly recreate almost everything, except for the Homekit integration connection.
Can someone please help me fix the Homekit setup so that I can connect OpenHAB to the iOS Home app?
At the moment, when I scan the Homekit Binding’s QR code with the iOS Home app, OpenHAB is not found as a bridge.
Hope someone can help.

probably the same issue as reported here

looks like we need to find a working docker setup.