Typical of recent Apple. Apple is terrible at services. I mean it took what 5 years to get iCould working? No surprise here.
And it still isn't reliable. Screen Time across devices doesn't work, iMessages sync across devices unstable etc.
Typical of recent Apple. Apple is terrible at services. I mean it took what 5 years to get iCould working? No surprise here.
Before Homekit New Architecture (HNA), We had the option to enable/disable homekit hub on each AppleTV. That control was taken from us.
Apart from just iOS upgrades, you'll have been given a very clear option to upgrade HomeKit - it's only if you've accepted that (which you would have known you were doing, it wasn't just a standard pop-up box - see the pictures in the article) that you'll be affected.
Plenty of stuff froze back then too. Although we did get new products every couple of years.
And it still isn't reliable. Screen Time across devices doesn't work, iMessages sync across devices unstable etc.
Cross device data has been a huge problem for Apple for YEARS.
One of the longest standing issues: iTunes/Apple Music play counts. Lots of us use a bunch of smart playlists to manage our music libraries. Many of these playlists are predicated on play count. The idea that Apple proposed to us is that interacting with media anywhere means interacting with media everywhere. Great! How hard could it be for Apple to update your play counts in real time across all your devices? Isn’t that EXACTLY what iCloud was supposed to be for? Yes, but evidently the simple act of synching play counts across various devices logged into the same Apple ID in real time is SO hard that after a solid decade Apple still can’t pull it off.
One of dozens of examples of current Apple software and services utterly failing.
If it is helpful, you can still disable HomeKit on Apple TV by removing it from home; under Apple TV HomeKit settings, choose the option to select a room, and at the end of the list is the option to remove from home. May help at least temporarily.Before Homekit New Architecture (HNA), We had the option to enable/disable homekit hub on each AppleTV. That control was taken from us.
The 2x AppleTV4k 2019s had their homekit hub function disabled as they are way out of Bluetooth reach if the NUKI lock, and also two homekit hubs (homepod and 2021 AppleTV4k, both with matter support) seemed enough. This worked very well before HNA.
I just restart HomePod this morning and add one user to Home successfully!!!Power cycle your hubs (Apple TVs and HomePods), then try again.
I don't have it running via Docker, but with the method you linked to at the end of your post.Mine's working great on my Synology Homebridge Docker Container. Well, just as well as it did before, so:
Old arch: works 80% of the time
New arch: works 80% of the time
Oh...uh. Were we not supposed to update Homebridge? I'm already on 1.6.0. I'm using this version.
![]()
I believe DSM 7, once I upgrade, will actually allow a native Synology package from the official Homebrige repo and removes all the Docker stuff. But that's neither here nor there.
When the day comes make sure you first update every single device for family and whoever you plan to invite. No mixed mode.Well glad I didn't pull the trigger on this yet. HomeKit is pretty integral to my whole smart home setup. Its reliability is why I stick with it over Google or Amazon, wouldn't want to jeopardize that.
Are you sure that isn’t just the stupid scenes bug that’s been around since day 1? If I set lights to certain colors and brightness, and then tap “create scene” and select those lights, the scene is a mess. It only saves the colors of some. This bug has been present for so long that it’s 100% clear Apple do not test HomeKit beyond the absolute basics of turning things off and on.Everything is updated and Home has been way worse. All my scenes are messed up, now the only thing that saves is which lights go on/off, but it will match the colors of whatever the last setting was.
For example, if I manually make all my lights red, then switch directly to a preset scene, the lights will stay red but will turn off/on or dim/brighten according to the scene…
Ahhhh I’m really starting to hate HomeKit and Home! It’s the one feature I use the most, and I’m thinking of dropping HomeKit altogether
Well, how do you know it would have been a total disaster for you if you haven't upgraded yet? In general it is safe to avoid being an early adopter. However, in some cases this strategy leads to missing on features for longer than necessary.Total disaster— glad I saw this coming and haven’t updated yet. Over 70 devices here and can’t afford the “early adopter tax” on this. Apple wants us all to be beta testers — it’s horrible.
A steady downward slide is how I’d characterize it. Apple needs to get their software act together. HomeKit isn’t the only 16.X related nightmare.
Total disaster— glad I saw this coming and haven’t updated yet. Over 70 devices here and can’t afford the “early adopter tax” on this. Apple wants us all to be beta testers — it’s horrible.
I'm safe, all my apple devices are set to auto update which never works. Just checked and all my OG Homepods are showing an update for 16.1 while they are on 16.1.
I think I'll leave mine as is as everything works fine.
If you upgrade to the new Home Architecture you also can’t disable Apple TV from being a HomeKit hub as the option to do so disappears.You cannot disable HomePods from being HomeKit hubs! Nor can you control what is the active hub.
Sadly it’s not thatAre you sure that isn’t just the stupid scenes bug that’s been around since day 1? If I set lights to certain colors and brightness, and then tap “create scene” and select those lights, the scene is a mess. It only saves the colors of some. This bug has been present for so long that it’s 100% clear Apple do not test HomeKit beyond the absolute basics of turning things off and on.
Tell us more. Please. 🙃
What must be factored into this is that new software mixed into an existing platform makes that platform much more complex. One can't expect a swath of new functionality to roll out perfectly on day one, no matter how much testing is done. Real-world users will *always* find issues that weren't discovered during testing.
I don't disagree with you that Apple needs to do more testing in real-world situations, but it's not a "steady downward slide", it's just normal software development. I'm running 16.2 on my iPhone and there are zero noticeable issues for me, so that is an example of how they've done an excellent job from my perspective.