hm. that steps usually helped to fix it.
do you see any error messages in the log file?
one more things to try - disable private wifi address in iphone settings if not done yet. this will not fix the issue but potentially avoid the issue in the future. you would need to re-pair again (remove, clearPairings, add bridge again)
Hi @yfre,
Thanks, I’ll try that by tomorrow.
One question: what do you mean by clearPearings?
Best regards
Ok, @yfre. I’ve done the steps incl. deactivating “private Wi-Fi addresses in iOS 14”
Now my devices are back online in HomeKit - hopefully it stays online after some days 
@dirkdirk: Thanks for the link. Done that steps as well
Thanks 
happy to hear. we should add this documentation as mandatory 1st step
@Stefan83 please give us update in 3-4 days whether it is still working for you
I just struggled with something like this myself. What I have found is that the act of “Saving” the Homekit Add-on inside the OpenHab3 UI causes some of the data to be lost when the config file is over written. Specifically the entires pertaining to MAC address and User Identifications. I would set up the binding with the suggestions above (Remove, clearPairings, Re-Add Bridge to HomeKit etc…) and still find my devices non-responsive after a while. Finally I figured out that the data was being lost when I was saving to make changes like such as to enable the use of mDNS. So I examined the config file and confirmed the discovery, I then after going through the process again to get it all set up correct then simply duplicated the config file just incase I clicked the save button again and lost all the specific data for users, If I did I can now replace with a good copy again and not lose the connection to my devices. I have at this point started to only modify the config file manually - it does require OpenHab3 rebooted to see the effects take place but I don’t lose my devices. I have now been running stable for approximately 5 days and everything is stable and works. I no longer get told by Siri that she can’t communicate with my OpenHab3 Devices.
Update
The Specific file to backup is located here, to recover if you lose the connection.
we were hunting this big (loosing mac address) almost for a year now. i think with your hint, we could finally fix it. i will try to reproduce it on my side. thank you for investigation.
Short update from my side: day5 and still working 
bad news: after approx. 21days, I’ve got the same issue.
All HomeKit devices from openhab are dead: “No Response” 
Stefan83, by chance did you make any settings changes to the settings for the HomeKit Add-on in OpenHab3 and save them by pressing the Save button displayed in the image below?
I have seen this happen to me usually within a day of clicking that save button. I have avoided clicking Save or using Crtl-S, and instead manually edited the .config file. So far my setup has not had any connection issues since I posted here almost 20 days ago now.
Note: I did experience once where Siri told me it couldn’t connect to OpenHab since making this change, but turns out one of my kids decided they needed the power outlet more then my HomePod Mini and unplugged it. Since the HomePod Mini is considered the Hub for HomeKit in my setup this makes complete sense. After pugging it back in the connection was restored and everything is back to working properly with no changes needed to OH.
Are you using Unifi equipment? I’d suggest inspecting the MDNS response to see if the Homekit entry is there.
Hm, no…
I didn’t touch the HomeKit settings (or press Save) after I re-installed the HomeKit integration.
I’m facing the same issue on OH3.1. HomeKit worked for a few days then all openHAB items appeared no responses in HomeKit. Already disable private ip
I’ve been struggling with this as well on OH 3.1.0.
Do we have a fix yet, or are we just hanging in with the config backup method?
Thanks
Hi Matt
the issue with corrupt homekit.json is not fixed as it is not reproducible and root cause is unclear.
i tried hard to get this issue on my machine - killing openhab process, running out of hard drive space, putting machine in sleep mode, saving non-stop the binding configuration via UI - no effect, user entry remains in homekit.json.
do you know when it happens on your side? any specific time or any specific action? any information would help to nail down the issue and fix it
while writing to you, i got an idea what else i could try to implement as fix.
this PR
will add homekit binding setting to disable deletion of the user information by binding. this will also blocks unpairing, but if setup is done then usually you dont unpair/re-pair
it is still not 100% clear whether the user information gets deleted from homekit.json by binding or by something else. but with this setting we could at least exclude binding from potential root causes.
once the PR get merged and release you will find the new setting in homekit UI settings. by default it is disable, i.e. deletion is not blocked. if you have working setup, enable it. maybe it will fix your issue
Hey there,
I’ve only just set this up for the first time, and it was working fine. OH is running on my QNAP NAS, and after a reboot I had noticed the HK was not working anymore.
It’s still currently in failure mode, so if there’s anything else that you’d like me to check, or steps to take prior to reconfiguring, let me know!
Ty
Hi Matt,
i dont know whether you have tried/ checked following points:
if you dont have “user” entry there, you would definitely need to re-pair, i.e. add openhab as bridge in home app. once you re-paired, check the homekit.json again and make a backup of it.
So this morning I re-added the hub; all is well. I was indeed missing the “User” entry in the homekit.json file. I’ve gone down the route of keeping a backup of it, and I’ll play a bit more. I’m going to try setting some file permissions to see if I can block the change, and maybe get an error identifying what is trying to access it.
I did/do have an IP address defined, and I had tried the mDNS switch back and forth a few times with no luck.
Thanks!
