Hands on with Apple's new HomeKit architecture in iOS 16.2

Posted:
in General Discussion edited November 2022
Apple is currently testing a beta version of iOS that promises to improve the speed and performance of HomeKit accessories. We put our home on the line to test it out and see what a difference it makes.

HomePod mini at the center of the smart home
HomePod mini at the center of the smart home


Slated for a late-November or mid-December release, iOS 16.2 is currently in developer and public beta. It promises several new features such as improved Live Activity support, external display support on iPad, and the new Freeform app.

It also promises to improve your HomeKit home.

You'll have to meet the requirements

To start experiencing the newfound speed improvements of the updated architecture, you'll need to meet a laundry list of requirements. Some of which may not be entirely under your control.

A new alert in the Home app
A new alert in the Home app


Initially, you'll need to update your primary device -- your iPhone or iPad -- to iOS 16.2 or iPadOS 16.2. With this update installed, the Home app will inform you of the architecture change and what you need to do to utilize it.

The minimum requirement is all HomePods are running software version 16.2. Initially, Apple said all Home Hubs needed to be updated, but in our home, only the HomePods required the update.

That's all many homes need, but there are fringe scenarios to be aware of. As an example, just because your HomePods and primary device are updated, all of your Apple devices will need updating to continue controlling your smart home.

That includes your Apple Watches, Macs, and Apple TVs. Even though you can migrate to the new architecture, you won't have the full experience until everything is on the requisite firmware.

Requirements to start the upgrade
Requirements to start the upgrade


In your home, that may not just be your devices. Your partner, children, or other family members but update their devices before they can control the home again.

If you have multiple homes, they must be updated too. This can be particularly tricky if you share access to relatives' homes. We have guest access to our parent's home and until they update their home, we won't have access to it.

Upgrading our HomeKit home
Upgrading our HomeKit home


This gets very confusing in practice. It means once you update your home's architecture, you can't control an older home until they update theirs. It's an odd technical limitation when switching between multiple homes in the Home app.

Testing the improved performance

When we set out to test the performance and reliability of the updated Apple Home architecture, it wasn't entirely easy to do. We can't run two instances of Apple Home side-by-side.

Instead, we ran through several automations and repeated them after the architecture upgrade was complete. This included turning on and off different accessories and running scenes and automations.

It feels a bit anecdotal but we believe we're seeing real, tangible performance improvements after this update. At least in some situations.

Communicating with devices directly one-on-one feels similar in speed to before. This is with Bluetooth, Thread, or Wi-Fi-based devices.

We noticed the biggest difference in our automations that were tripped by other accessories and any time we had a scene run with several accessories controlled.

These multi-accessory scenes showed the most improvements with all accessories seemingly responding at once rather than one-by-one-by-one as it was perceived before.

Redesigned Home app in iOS 16
Redesigned Home app in iOS 16


Our goodnight scene is a great example as it has a ton of accessories included in it. It turns off lights in several rooms, closes various window coverings, shuts the garage door, locks the front door, and turns down the air purifier in the bedroom.

Before, it took several moments while you waited to ensure the scene was running, and then we'd see a waterfall of devices triggered in a row. Post-update, they all seem to run simultaneously and without as much delay.

There's a reason it's a beta

We say it all the time -- do not run a beta on any device you rely on. The same goes for your home.

It's a terrible idea to run beta software on your smart home that you live in because if something goes wrong, you may lose access to your home, have to reset all your devices, or accessories won't respond.

Case in point, this initial 16.2 is wildly unstable and has caused many issues that users have expressed on social media. We, too, have had some problems.

During setup, we updated everyone in the family to 16.2. One family member though had an old, unused home that was a vestige of their pre-married life. The Home app said it needed to be updated, but since it was unneeded, we removed it.

When we removed it, it somehow reset the Home app to nothing, showing a single, empty home. Our first inclination was to remove their access to the home before re-adding them.

This didn't work, despite the invite showing on the impacted device. It shows them as an authorized resident of the home but they have no access on their Mac, iPad, Apple Watch, or iPhone.

Until Apple issues a new beta, they'll be unable to control our home. Let us reiterate -- don't install beta software on your crucial devices.

The good news is, once iOS 16.2 is released and (hopefully) polished, your HomeKit smart home is going to perform better than ever. Just be patient.

Read on AppleInsider

Comments

  • Reply 1 of 13
    AppleZuluAppleZulu Posts: 2,019member
    What if someone in the house has an older Mac on the network that can't update to the latest version of MacOS? Will that block the whole house or that user from having any access to control HomeKit from any of their devices? That seems like an unacceptably un-Apple sort of complication. I can see the home app on that one older device no longer working, but blocking everything else for everyone (or for that user) doesn't make a lot of sense. It's going to be a problem if someone who needs to keep an older device for a certain use use loses access to Home controls on all devices, or even if someone who does't need to keep an older device nonetheless loses all HomeKit access until they shell out hundreds or thousands of dollars to upgrade every piece of hardware.

    The devices that are capable ought to migrate, and only those that aren't should cease to have that functionality. 
    edited November 2022 elijahgcornchipJanNLwatto_cobra
  • Reply 2 of 13
    mobirdmobird Posts: 755member
    How do you get the update to 16.2 for the original HomePods? I have updated all devices that interact with the Home app to the latest Beta version ie. 16.2 but when I attempt to initiate the "Home Upgrade" I receive the message that the HomePods need to be updated to 16.2 before I can initiate the "Home Upgrade"
    Anyone know how to resolve this issue?
    edited November 2022 watto_cobra
  • Reply 3 of 13
    Ya know, I'd be happy if Siri could just turn music off on our multiple HomePods without telling me "I'm sorry, there is nothing playing. I can't stop"... And then ACTUALLY stopping the music that WAS playing lol. There is no way in hell I will ever deploy Google or Amazon devices in our home, but man Siri can be stupid sometimes! Just wish they'd focus on stuff like that than millisecond performance "gains" like this...
    williamlondondewmecornchipwatto_cobra
  • Reply 4 of 13
     ☘️ nice touch 
    Andrew_OSUwatto_cobra
  • Reply 5 of 13
    AppleZulu said:

    The devices that are capable ought to migrate, and only those that aren't should cease to have that functionality. 
    Agreed. We have an iPad mini 2 and an iPad Air that both still work fine but are incapable of being updated to a current iOS (I just updated the Air to 12.x.x). I also have some older Macs that I don’t use much and I don’t update beyond where they are (even though one of them I could). Does that mean I won’t be able to get this new Home architecture on the devices that are capable of supporting it? That seems silly.

    It’s no fun trying to use Home on the iPad Air, it’s just so slow. As a result, I don’t use it for that, so losing that capability on that particular device wouldn’t matter much to me. I’d rather lose Home access on it and gain whatever improvements come with the new architecture on my other devices.
    watto_cobra
  • Reply 6 of 13
    Andrew_OSUAndrew_OSU Posts: 573member, editor
    AppleZulu said:
    What if someone in the house has an older Mac on the network that can't update to the latest version of MacOS? Will that block the whole house or that user from having any access to control HomeKit from any of their devices? That seems like an unacceptably un-Apple sort of complication. I can see the home app on that one older device no longer working, but blocking everything else for everyone (or for that user) doesn't make a lot of sense. It's going to be a problem if someone who needs to keep an older device for a certain use use loses access to Home controls on all devices, or even if someone who does't need to keep an older device nonetheless loses all HomeKit access until they shell out hundreds or thousands of dollars to upgrade every piece of hardware.

    The devices that are capable ought to migrate, and only those that aren't should cease to have that functionality. 
    In this situation, you have a choice. you can upgrade the home to the new architecture and all devices will work except that older Mac. Or you stay with the old architecture to ensure that Mac still works.
    StrangeDayswatto_cobra
  • Reply 7 of 13
    It would be super helpful if they would resolve the doorbell volume to the HomePods. I can barely hear the ring and have yet to find a way to turn the ring up.
    watto_cobra
  • Reply 8 of 13
    This will be a welcome update if it does indeed performance of HomeKit. HomeKit communication can be sketchy and unreliable. I have HomePods throughout my house. I have the odd Thread device and my router (Eero) and its sub devices are also thread but still HomeKit can be sluggish.

    I am super excited for this update once it is released to see if it improves things and I hope it include Matter and that all my HomeKit accessories update for Matter so communication between them can be significantly improved too.
    watto_cobra
  • Reply 9 of 13
    I don't have any HomePods; my "central" device is my Apple TV.  How does that work, I wonder.
    watto_cobra
  • Reply 10 of 13
    AppleZuluAppleZulu Posts: 2,019member
    AppleZulu said:
    What if someone in the house has an older Mac on the network that can't update to the latest version of MacOS? Will that block the whole house or that user from having any access to control HomeKit from any of their devices? That seems like an unacceptably un-Apple sort of complication. I can see the home app on that one older device no longer working, but blocking everything else for everyone (or for that user) doesn't make a lot of sense. It's going to be a problem if someone who needs to keep an older device for a certain use use loses access to Home controls on all devices, or even if someone who does't need to keep an older device nonetheless loses all HomeKit access until they shell out hundreds or thousands of dollars to upgrade every piece of hardware.

    The devices that are capable ought to migrate, and only those that aren't should cease to have that functionality. 
    In this situation, you have a choice. you can upgrade the home to the new architecture and all devices will work except that older Mac. Or you stay with the old architecture to ensure that Mac still works.
    If by “all devices will work except that older Mac,” you mean the older Mac loses HomeKit functionality but still works the same for everything else, that would be fine. If you mean the old Mac gets bricked by this update, that would be a problem. You mean the first thing, right?
    cornchipwatto_cobra
  • Reply 11 of 13
    mobird said:
    How do you get the update to 16.2 for the original HomePods? I have updated all devices that interact with the Home app to the latest Beta version ie. 16.2 but when I attempt to initiate the "Home Upgrade" I receive the message that the HomePods need to be updated to 16.2 before I can initiate the "Home Upgrade"
    Anyone know how to resolve this issue?
    From Reddit, some have reported success by removed all OG HomePods from their home. Then doing the update followed by adding the HomePod OG back to their home. Beta caveat emptor.
    mobirdwatto_cobra
  • Reply 12 of 13
    Andrew_OSUAndrew_OSU Posts: 573member, editor
    AppleZulu said:
    AppleZulu said:
    What if someone in the house has an older Mac on the network that can't update to the latest version of MacOS? Will that block the whole house or that user from having any access to control HomeKit from any of their devices? That seems like an unacceptably un-Apple sort of complication. I can see the home app on that one older device no longer working, but blocking everything else for everyone (or for that user) doesn't make a lot of sense. It's going to be a problem if someone who needs to keep an older device for a certain use use loses access to Home controls on all devices, or even if someone who does't need to keep an older device nonetheless loses all HomeKit access until they shell out hundreds or thousands of dollars to upgrade every piece of hardware.

    The devices that are capable ought to migrate, and only those that aren't should cease to have that functionality. 
    In this situation, you have a choice. you can upgrade the home to the new architecture and all devices will work except that older Mac. Or you stay with the old architecture to ensure that Mac still works.
    If by “all devices will work except that older Mac,” you mean the older Mac loses HomeKit functionality but still works the same for everything else, that would be fine. If you mean the old Mac gets bricked by this update, that would be a problem. You mean the first thing, right?
    I mean the Mac is fine, just cant control your home.
  • Reply 13 of 13
    chabigchabig Posts: 641member
    mobird said:
    How do you get the update to 16.2 for the original HomePods? I have updated all devices that interact with the Home app to the latest Beta version ie. 16.2 but when I attempt to initiate the "Home Upgrade" I receive the message that the HomePods need to be updated to 16.2 before I can initiate the "Home Upgrade"
    Anyone know how to resolve this issue?
    I had this happen to me today. I removed all four HomePods from my Home, updated the Home architecture, reset the HomePods to factory settings, and set them up from scratch.
Sign In or Register to comment.