The problem is not the update of the HomePods, it is the update of the Home architecture. My HomePods are well up to date, but not the architecture, as far as I understand.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
PSA: Apple Has Made Its New Home Architecture Update Available Again
- Thread starter MacRumors
- Start date
- Sort by reaction score
The problem is not the update of the HomePods, it is the update of the Home architecture. My HomePods are well up to date, but not the architecture, as far as I understand.
Well my iPhone 7 Plus are no longer working with the home architecture because I missed the iOS minimum. And no, I don’t notice anything faster. My Schlage auto lock from my automation with Homebridge ring sensors are no faster
Only if that first gen google home mini device was ALSO updated for Matter. If it doesn’t support Matter than nothing Apple does will change that.
So after a few weeks am I the only person that finds its much slower then before especially when: Renaming a device, Changing a devices room, updating when opening the home app. Basically slower in general.... I have 65 devices not sure if that matters but compared to before its just slow
Many things seem slower. And at least nothing is faster. And my wife got kicked out of the home. And was presented with a circle of “remove home before you can add home” and “cannot remove home”. And pop ups preventing her from removing the home etc. Something like that. Can’t remember the exact wording. And then suddenly after a lot of restarts and hours it worked.
Basically I have a hard time figuring out what that update did apart from a day of frustration 🤷♂️
Yes, definitely BUT...
The way this used to work was that these changes would happen locally, then (supposedly) be propagated out to iCloud, your Apple TV, etc. This second stage frequently did not work, with all sorts of horrors, like different names in different places, or you create a Scene or Automation but it just doesn't seem to work (because it hasn't propagated to the HomeKit hub).
The new scheme seems to be that you send the change to iCloud and the hub, and you ONLY make the change "appear" on your local device when the remote world (iCloud and hub) tell the local device that the change has happened. This is still not great in terms of UI, but is VASTLY preferable in terms of reliability and being able to trust the system.
This is still not a great architecture, but it was a fairly easy modification to what they had. A better solution (and one I expect they will evolve to once they have time to write the code) is one that has an intermediate local state to capture the situation I have described above. ie something like
- I make local changes of some sort
- the changes are immediately reflected in my local UI, but in some sort of "don't trust this" form, like the icon and writing are all pink (or upside down, or whatever)
- when the remote confirmation comes in, the UI shows the changed state as trustworthy.
This would at least allow you to make changes like renaming and see that *something* happened right away, without the current feeling that you are going mad, that you keep changing things but nothing actually changes!
Overall, the current HomeKit (as of about iOS 16.3) has more or less FINALLY got its act together. It's still terrible in so many areas (scripting, debugging, logging, error reporting, code reuse, changing or moving a device, etc etc) but in the single most important area of reliability, it feels like I can trust it in a way that has not been true for many many years.
I'm comfortable saying that it's moved up from being the single worst product Apple ships to number three.
(Finder returns to #1, as it has been for much of about the past 20 years. No matter WHAT the issue is, you can rely on Finder to fsck it in some way, to keep doing so year after year, and to simply ignore bugs year after year -- things like window persistence are still unreliable after 20+ years!!!
Number two is Shorcuts which STILL cannot perform Automations with anything close to reliability. Unlike HomeKit which is now very reliable in this regard.)
This may be more a problem with Location Services. There are a whole lot of problems around Location Services and in particular how it recognizes that you are "home". Sometimes the only solution is to dick around with the address of "home" in your Contact card, like maybe delete it then recreate it or variants on that.
You make a good point however implementation is terrible and that's what matters. Renaming a device for example instead of a wheel or something saying saving when you leave the location where you set the name it stays its old name making the user think the change did not stick.....for years OS's both desktop and Phones have had this, its nothing new... For all the part about the cloud whatever the changes if my HomeKit stops working when the internet goes out (hasn't happened yet) it will be the deal breaker for me. Before this last update when my power went out and i was on generator it all seemed to work just fine i hope the same is true...
So why did it happen when I upgraded to the new architecture and disappeared by it self after a few days?
So what is the verdict regarding the revised New Home Architecture Update? Is it now worth the upgrade over the old architecture?
Nope it works slower in almost every way. And if you have older devices those won’t work anymore. I have no pros yet.
Specifically, what kind of devices are you talking about? Bluetooth ones? What products? Can you list some so I know what to avoid?
Garage doors, lights wifi HomeKit and philips hue, blinds, motion sensors, temp sensors, electric outlets, air conditioners, buttons switches. All of these devices worked fine before HomeKit is what slow. Example the philips hue lights are fine with philips hue app but with home app they are slow and laggy
Accessing HomeKit secure video recordings. When I open a camera view it will take much longer to load recent recordings. I can browse around for +30 seconds in the clips of yesterday before the most recent clips will be available. That was not an issue before the upgrade.
Before I update to the new architecture, I have a question.
All my devices have the latest IOS & MacOS versions. A person I invited and currently has access, has a MacPro (2014) that is too old to get Ventura OS. All his other devices (iPhone, iPad) are updated.
I get a warning when I start the HomeKit upgrade. The warning is his iCloud, not his individual devices.
Does the invited person lose access across all his devices completely, because of the MacPro? Or will the iPhone and iPad still have access, and it's just the MacPro that won't?
All my devices have the latest IOS & MacOS versions. A person I invited and currently has access, has a MacPro (2014) that is too old to get Ventura OS. All his other devices (iPhone, iPad) are updated.
I get a warning when I start the HomeKit upgrade. The warning is his iCloud, not his individual devices.
Does the invited person lose access across all his devices completely, because of the MacPro? Or will the iPhone and iPad still have access, and it's just the MacPro that won't?