No I removed bridge from Homekit and add again it, I back up all configuration before with Controller for Homekit and restore it after.
I’ll add another data point.
I updated HA core to the current release and 3 Apple TVs to 16.2. All devices exposed to Homekit were showing as offline. I rebuilt the bridge from scratch and eventually discovered that all devices become unresponsive when a home hub is active. It doesn’t matter which of the Apple TVs is the active hub – all devices show “no response”.
I’ll need a long term solution as I need a hub to allow device access when outside my network and as a bluetooth device for one of my locks.
I’m not seeing much in Github issues on this, either.
Edit: Here’s a relevant issue: HomeKit integration devices unresponsive · Issue #84387 · home-assistant/core · GitHub
Thanks @kmak - There are infact 2 issues depending on wether you were able to take the final step in the Apple Home app to update your architecture. I didn’t get to the “update my home” option after upgrading to 16.2 - so the HASS Bridge is still fine for me. The problem I have (even after following @miquellaboria suggestion) is that I can’t add discovered Apple TV’s and Home Pod’s back into Home Assistant as media devices post their upgrade to 16.2 - hence the separate issue I raised on GitHub.
Did the following while just messing around:
- verified the mdns entries for the bridge are the same whether a hub is active or not
- I tried adding an iPad as a hub instead of an AppleTV. Same behavior from all home.app clients when the iPad is active. Interestingly, home.app from the iPad itself works fine in this scenario (?!)
Debug logging shows that clients are getting disconnected when any hub is made active.
2023-01-09 12:26:52.997 DEBUG (MainThread) [pyhap.hap_protocol] ('10.10.0.238', 49862) (2dea7b9d-e73c-46c9-95ae-8388333c90ac): Connection lost to Master House: None
2023-01-09 12:26:53.322 DEBUG (MainThread) [pyhap.hap_protocol] ('10.10.0.102', 56470) (2dea7b9d-e73c-46c9-95ae-8388333c90ac): Connection lost to Master House: None
2023-01-09 12:38:34.636 DEBUG (MainThread) [pyhap.hap_protocol] ('10.10.0.180', 49204) (2dea7b9d-e73c-46c9-95ae-8388333c90ac): Connection lost to Master House: None
2023-01-09 12:38:46.196 DEBUG (MainThread) [pyhap.hap_protocol] ('10.10.0.238', 49863) (2dea7b9d-e73c-46c9-95ae-8388333c90ac): Connection lost to Master House: None
(those IPs are all clients like laptops/phones where someone would typically be using home.app)
Found the profile. Might try this at some point.
I’ve just done this. Fixes performance of HomeKit but still doesn’t help bringing AppleTV/HomePods on 16.2 back into Home Assistant 
To me this feels like this is 100% related to HomeKit’s new architecture then, as the biggest change is to relay all requests and commands through the home hub, no matter if the device is on the local network or not.
I’m not sure if this is a (subtle) incompatibility in pyhap, or apple just messing up their new architecture change. Considering they basically halted all upgrades (by removing the feature), I’m thinking it is the latter, and there’s not much to do besides wait.
Not sure what has happened over the last couple of days but I now have the same situation. All Homekit Devices become unresponsive. Removal and reinstall of the HASS bridge only works for a few minutes then all devices turn unresponsive…
I ultimately used the profile to reset all my HomeKit data. I removed my existing home(s) and rebuilt again (glad I was just using an ‘include’ and a yaml file). My home has been running for a few days now.
We’ll see what happens in the coming days,
Hi, Having the same issue!! No response after updating to 16.2. Deleting and repairing hub with 100 + Accessories is not working, after first reboot all devices became not responsible again! damn this is so bad! What can we do with this? Is there any working solution? I cant take a hours of mi life to fix this. All my devices connected to homekit using home assistant.! This is fail of century!
Indeed - Apple have properly screwed up. You can get this working by resetting your HomeKit profile (nuclear approach) see here but as yet I have not been able to get my Apple media devices integrated back into HA.
1 Like
Apple released ios 16.4 yesterday, bringing back the HomeKit Upgrade. Is this still a problem now, or does it work flawlessly now when upgrade to the new HomeLit architecture?
2 Likes
Great question… I eventually was able to reintegrate my media devices - but honestly I have no idea what changed. Therefore, having been burnt the last time around with Apple’s upgrade to 16.2, I am going to take a step back and wait for the feedback of others before pressing the upgrade button this time around!
1 Like
Wondering it too, I don’t dare to update
1 Like
Yes! Also wondering about that!
So it turns out that I couldn’t contain myself…
Upgraded to 16.4 across all devices (iPhone/iPad/ATV/HomePods). One of my HomePods and Eve strip-light went offline but recovered overnight and so far, the only glitch I seem to have is playing media from the HA Media browser through the Apple devices. All the other media control functions seem to work.
1 Like
Did you also upgrade to new HomeKit architecture?
No option for me to do so… Assume this must have happened last time before Apple pulled the plug.
I was patient last time at 16.2 so hadn’t yet upgraded. Today I couldn’t keep myself from doing it. I upgraded all my devices to 16.4 yesterday, and my macbooks today to 13.3. Then I pulled the trigger on the new Homekit architecture.
Everything worked right away on my phone using apple home. My Macbooks seemed to have a lot of stuff that wasn’t responding right away. I went through the process of the various dialogue boxes that come up after the upgrade, and then closed down apple home and re-opened. Then things worked right away on that too. And, I can’t for sure say it is faster, but it does seem nearly instant to get things to work.
But then after closing and opening the Home app on my macbooks another time, both seem to have issues with some specific devices. I use command line switch on a few things, and some yolink sensors, combined into a garage door opener on a few garage doors. Those don’t seem to be liking something. With the doors being operated by command line switch, and the sensors being separate, I had been updating the door status in homeassistant with a query of the yolink sensor. Now that seems to be broken. I’ll have to figure out why it’s not happy. So some things are fine, but a couple aren’t.
Update: Everything is working OK now that I found what was causing my issues. I have a single homekit home, but I’m VPN connected between 2 physical sites. I have 2 homepods at the remote site. For some reason, whenever they are allowed to reach the internet, one of the becomes the active homekit hub. That’s when all my stuff at home starts hanging. This never happened with the older architecture, but I’m going to have to assume that it’s here to stay. I guess I’ll finally have to run those as a separate “home” from here on out, or they’ll cause issues. Sad, because it always worked fine before. What I really wish was that apple would have a “hub disable” switch for homepods, or at least let you set primary and backup hubs. I’ve got about 16 qualifying devices and it would be great if I could pick the best ones to act as the actual hub.
2 Likes
I also did the upgrade to the new architecture. No problems so far!