The HomeKit architecture upgrade is only available for people with a HomeKit Hub, correct?
I do see the upgrade in the (Apple) Home App on my iPhone, but get a “A home hub is required to allow shared users continued access to this home”. I am only using the HomeKit integration to expose HA devices to Siri. I am not using the HomeKit Controller integration and don’t have (and don’t want) a Apple TV, iPad, HomePod as hub.
I was just wondering if the upgrade is not applicable for this setup. Anyone knows?
I believe that’s correct. You will need a hub. The cheapest way is probably to get a homepod mini, but I fell in love with everything, and have 5 apple TV’s in various places and basically don’t ever use anything else to stream video. I even stream our antenna and play via Apple TV. And the homepods were so nice I have over a dozen of them scattered in 4 buildings over 2 sites.
To complete my above post, everything is working well after the upgrade to the new homekit style. I did end up just splitting my 2 main sites into 2 separate “homes”, which got rid of my 2nd site becoming a hub for my first. In the end it was a good thing to do and I shouldn’t have waited so long.
@RVTim Do you have any automation, which uses media.player and TTS to let the homepod(s) say something? And is it still working after the update? For me it stopped working …
@Blackway I don’t. I just tried creating one now. I actually hadn’t ever done the “Configure” of my homepods to HomeAssistant because most of my automations are done in homekit. But I configured it as a media player, then set up a time-based TTS automation to kick off and play some text at the time it was triggered. It did not play. It DID, however, play when played manually, by hitting the 3 dots on the right of the automation and choosing Run. I’m not sure why that would be. I’ve never had to dig too far into Home Assistant’s logs, but I’d be curious what it did. The automation run time DID update, so at least Home Assistant thought it did run. So the mechanism itself seems to work but something’s just not right with the automation execution I’d think.
Been trying to figure this out for the last 48 Hours.
2 Days ago i received a notificaton in Apple Home on Iphone saying there was an Home upgrade available. After update i started to receive NO RESPONSE on all my Entites in Apple Home.
All apple devices are on the latest IOS (16.5).
Home Assistant 2023.5.4
Supervisor 2023.04.1
Operating System 10.1
Frontend 20230503.3.
I have deleted my home via my Iphone,
have then deleted the home kit bridge intergration,
then run the delete profile described by @sooty
then re added the intergration, then joined it via the QR code. after 3-4 minutes the items return to NO REPONSE.
I have Retarted my router several times with no effect (Unifi UDMP v3.1.9 - network 7.4.156), i have turned off IGMP Snooping - no effect, turned on IGMP Snooping - no effect
If i reload the intergration via the intergration panel, etities recover, but after a couple of miutes return to NO RESPONSE
The biggest head ache is that this was working fine before i accepted the update to upgrade the Apple Home architecture.
Any pointers would be grate full as im loosing my mind trying to find the issue!
I have also noticed that Home assistant provides a joining code in the format XXX-XX-XXX, but now apple home is asking for the code to be in the format XXXX-XXX-XXXX. So using the code manually does not work, but scanning the QR code does work unless you leave it a while the joining fails and says “Accessory can not be found”
After updating, my Homeassistant Supervised VM went totally blind and wasn’t able to boot up. This VM wasn’t in perfect shaped and I was planning for some time to do a clean reinstall since was having issues with Zigbee coverage (trying multiple coordinators (Zigstar vs Skyconnect) and platforms (ZHA vs Z2M).
So I went ahead and installed a new VM. ZHA was reinstalled, all devices were added and named. I was using this for 1 day without issues. Then I went ahead and configured a Homekit bridge in HA and added to my home. Almost immediately in an hour HA was inaccessible again. I tried restarting but didn’t booted up. Then I accessed it and saw that it had the error that Waiting for HA CLI to be ready..... It wasn’t able to start so after issuing a login command I had to do a ha core restart and then I was able to access the Web UI also.
So now I am staring again, but it really seems that the new architecture (maybe Matter ?! ) is fucking up something pretty much. The strange things is that it even messed up my clean my HA installation which is really strange.
Anyone been following this thing from the dev team who’s close to people related to this integration? @frenck@bdraco maybe? I saw you made a commit related to this in the HA repo.
Has anyone found a solution to this issue? Similar to others, I updated my Apple Home app after receiving the notification. Since then, all of my devices I’m exposing from HA through HomeKit Bridge are showing as No Response.
I’ve tried to reboot HA a few times, reload the HomeKit Bridge integration, remove the HomeKit Bridge integration entirely and start clean (removed from Home.app, then connect again with QR code), but still having the same issue.
I’ve also tried to remove a HomePod Mini, which didn’t solve the issue as one person mentioned earlier. Also tried to re-add the HomePod & remove again to see if either would work (nope).
I’m currently running on latest firmwares for iOS (16.5) and HA (2023.6.1).
Any help would be GREATLY appreciated so I can use Siri, CarPlay and my HomePod again.
Recently had the same issue. TLDR version: AppleTV is my home hub, I had to delete the integration from homeassisant, re-add and re-pair it, then everything came back just as before. Phew.
Longer version…
After saying ‘yes’ to the architecture upgrade from my iPhone, for the next few minutes everything seemed fine. Then I had to re-add my AppleTV (from the AppleTV) to the home as it provides the home hub function in my set up and apparently had to re-connect. At that point, all my devices ghosted showing ‘no response’ in Home. All still fine in Homeassistant. Stayed that way for a few days while I googled all the issues people have had with this upgrade. Some people reported that disconnecting the home hub (Homepod or AppleTV) restored their devices in Home, so I deleted AppleTV from my Home. DIdn’t make any difference for me. Then I deleted AppleTV integration from Homeassistant ad rebooted everthing. No change. So I re-added it AppleTV figuring it wasn;t that. It went through the pairing process with the PIN codes (3 of them) to restore the integration in Homeassisant. Then suddenly all my devices came back online. All works as before now.
Doing this seemed to briefly work for me when I tried to open Home.app from my Mac. However, as soon as I opened it from my iPhone, all entities went back to No Response and now I’m back to being unable to access any of my entities through Siri or HomePods.
I have the same issue since updating to iOS 16.5, now on 16.5.1. After adding HomeAssistant HomeBridge to Apple Home, it’s visible for 20 seconds, then everything disappears.
I had the same issue and figured out why it was happening (at least in my case).
Like many of you, I upgraded the Home app to the new architecture, and after that all my devices turned to “not responding”. Long story short, it was a networking issue.
My network at home is a little bit complex, but I believe not so uncommon : I have my “internet box”, on which I have a small router/switch, and a couple of Google WiFis (the WiFi provided by my internet router is not good enough, and doesn’t provide a mesh network).
As a result, I have 2 sub-networks:
One coming from the internet router
One coming from the Google WiFi (connected on the internet router via ethernet)
Most of my computers and devices are connected to the WiFi network, including my HA server, my Homepods, etc. I also have an Apple TV, but for obvious connectivity reasons, it’s connected via ethernet directly to the internet router (and that was the issue!).
The thing is that the HomeKit network automatically selects the main home hub and tends to give priority to Apple TVs (most likely with the fastest connectivity), and that the one using Ethernet was always selected. However, as I mentioned earlier, my internet router uses a different sub-network than my wifi. I finally figured this out checking the IP address of the Apple TV, which didn’t use the same mask than my other servers and devices (including my HA server).
Now how to fix it?
Before the Home upgrade, it was possible to exclude an Apple TV from being a HomeKit hub. I did this before and it solved my previous issues. However, it’s no longer possible with the new architecture.
So what I did is to remove the incriminated Apple TV from my Home app, so that it’s no longer part of any room. It also removes it as a hub. Homekit automatically selects another available device (my main Homepod in my case), and everything automagically started to work again!
Lesson learned: HomeKit doesn’t like subnetworks AT ALL
I hope this helps.
I too have a similar setup with Mesh WIFI and thinking back I ended up cutting over my Apple TV to an Ethernet port on the Mesh WIFI which explains why it has all been working fine for me since.
Did anyone found a solution around the “sharing” issue?
I recently upgraded (yesterday) to the new architecture after it popped up on my iPad, without reading the fine print (I know!). I didn’t have a hub before, but was sharing my home with other family members living here (spouse and two children).
After the update, I’m the only one who still has all devices. The sharing feature was dropped, and now I read that you can no longer use an ipad as a hub, which was previously possible. So the only way to make the sharing feature work again seems to buy a HomePod or Apple TV
