It probably won’t be a manual update like you had to do. I’m sure this will just be a code fix for you.
For the rest it’s a code fix and upgrade together.
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.
Apple Preparing to Re-Release Revamped HomeKit Architecture That Was Removed From iOS 16.2
- Thread starter MacRumors
- Start date
- Sort by reaction score
For the rest it’s a code fix and upgrade together.
We salute you, brave soul who dares to install this update. God speed.
Sadly I think we all know the answer to both questions. 😉
I hope Apple gets HomeKit right this time around. Thankfully I didn’t jump on the first release. Life’s too short to spend on trying to get Siri to turn off the lights at night.
That’s interesting. My eufy outdoor cameras work fine on my iPhone but not on Apple TV, 2 Macs, Apple Watch, or my iPad. Cameras used to work via HomeKit on everything.
I really don’t understand HomeKit. Super often the shortcuts app, Siri or the Home app on the watch tell me that my devices are not available. I have to use the Home app on the phone where it works without problems and all devices are available…
Let me guess, you run a highly complex system like one or two Homepod, an Apple TV, one motion sensor and a light switch? 😝
Home and HomeKit are such a m**, I left them (to never como back) when lights went out in the bathroom while taking a bath, sensors didn't detect movement not even waving them hello at 1cm. It was just to risky to have something like that at home.
Thanks for sharing! It sounds like you have a really interesting setup!
If you would be amenable, I (for one) would love to hear what you use as a proxy/translation gateway between HomeKit and non-HomeKit devices--and how you use it. (For example, I've heard of HomeBridge, but (a) I haven't used it and (b) I thought it was only good for surfacing non-HomeKit devices to HomeKit.)
Thats pretty common. The sensor probably have a minute or so after detecting “No movement” where it will not accept new inputs. Faulty design, when combined with the only available logic in Home/Homekit:
So you have the option to turn on light when detecting motion and turn it off after eg 10 minutes. At that point it will turn of no matter what it registers within the 10 minutes. So movement again in minute 5 after light has turned on, will not re-trigger another 10 minute count down. It will still turn off light 5 minute later.
You can also ask it to turn off when detecting "no movement". That is for most sensors a trigger that is send 1 minute after last movement detected. After that trigger message the sensor will go into a blind mode for a minute or so. So if you do not move for 1 minute and 5 seconds lights will be turned off and you will not be able to turn it off again until a minute later.
What they should implement is "when no movement has been detected for xx minutes". There's a logic for that in the aqara app (the sensors I use) that works rock solid, but that can only be combined with aqara LED lamps, which are not produced anymore.
I have seen various attempts to workaround on this with shortcuts. Looping through several rounds of wait and ask for motion detected and then exiting etc, but I cannot get anyone of them to work stable. Often I would find that the lights will not be turned off and burn all night.
Amazing that an old "dumb" PIR sensor can do this perfectly out of the box and has been so for +20 years. Two knobs: One for timing and one for sensitivity. Total blunder that Apple did not think of this.
Edit: Give apple some feedback here: https://www.apple.com/feedback/ ...not sure it will help, but it will not help if nobody gives feedback. And their feedback form only allow tvOS up to version 15.3... I'm pretty sure mine is higher ;-)
Last edited:
Unfortunately I also had the update installed, breaking geofencing when the Apple TV. Took me a while to discover it only broke down when the Apple TV was connected over WiFi. When connected to Ethernet it did work properly. Had a long chat with some Apple engineer about this (before the update was actually pulled).
I have turned off automatic updating on the Apple TV now and will only update when the weather outside is ok. My heating system is managed by HomeKit and with the roaring gas prices here in Europe that's not something to gamble with.
Luckily the bug cause the heating system not to turn oneven though someone was at home. That saved me enough money to buy the new Apple TV this spring.
I have turned off automatic updating on the Apple TV now and will only update when the weather outside is ok. My heating system is managed by HomeKit and with the roaring gas prices here in Europe that's not something to gamble with.
Luckily the bug cause the heating system not to turn oneven though someone was at home. That saved me enough money to buy the new Apple TV this spring.
I wonder how much permanent damage Apple has done with this to the whole home automation scene? I guess most of us with Homekit-based HA setups accepted there would always be occasional glitches and knew that short server outages are a fact of life, but for your whole infrastructure to stop working for weeks? That's got to have been making people think twice. At least, hopefully with Thread/Matter this should become less of an issue, but it's going to be a few years before that's fully integrated into most people's set-ups.
I know not everyone's been impacted, but it seems that the more invested in HA you were, the more likely this HomeKit issue is to have affected you and other family members.
I know not everyone's been impacted, but it seems that the more invested in HA you were, the more likely this HomeKit issue is to have affected you and other family members.
It also seems to have broken the ability to access HomePod alarms/timers remotely...
I was at a conference recently and had to get my father to my apartment to pull the power on my bedroom HomePod mini to stop it from annoying my neighbours for the week because I wasn't able to disable the recurring alarm remotely...
The wording in the panel that shows the alarms says:
This sounds intentional and really has me really worried that they knew and that this is now expected behaviour. I gotta tell you, alarms on my HomePod instantly became less useful...
On a side note, this is actually the only issue I've had after doing the architecture upgrade, but then I don't have any family sharing set up.
I was at a conference recently and had to get my father to my apartment to pull the power on my bedroom HomePod mini to stop it from annoying my neighbours for the week because I wasn't able to disable the recurring alarm remotely...
The wording in the panel that shows the alarms says:
Alarms unavailable said:
This sounds intentional and really has me really worried that they knew and that this is now expected behaviour. I gotta tell you, alarms on my HomePod instantly became less useful...
On a side note, this is actually the only issue I've had after doing the architecture upgrade, but then I don't have any family sharing set up.
Last edited:
Yes, you still have the new architecture. Even though Apple withdrew the option to upgrade to the new architecture, it didn't roll anything back for those who'd already installed it as it's not possible to do so.
Aha, that confirms what I thought I was experiencing. I figured 10 minutes should be enough that I shouldn't ever end up with lights off, but I do. Not often, but it happens.
Who came up with that logic?!?
I may have misunderstood this, or it might be device specific, but that's not my experience.
I have a Hue motion detector in my home office. In Home, I have automations set up so that if it detects movement, it will turn on my air purifier, and if it's after sunset, some lights. I have this automation set to turn off after 5 minutes.
Everything only turns off 5 minutes after I leave my office, other than that it will stay on for as long as I'm in the office. That suggests that whenever I move, the 'countdown clock' resets to 5 minutes, which doesn't seem to be what you're suggesting above?
I guess the behaviour may differ between different motion detectors. For example, some (typically in intruder alarm systems) will use battery-saving logic whereby if it detects motion, it won't 'look' again for another x minutes. If your 'off delay' was less than x minutes, you'd get the problem the OP mentioned.
Last edited:
This is seriously not thought through as it is today.
I saw someone making two automations:
- Turn on light when movement has been detected.
- Turn ON light when NO MOVEMENT has been detected AND set this to turn off light after x minutes.
I also seen some lengthy shortcuts attempts. Here's one: https://patrikmojzis.medium.com/mot...-off-lights-after-a-certain-time-a9b616b719ae but it doesn't work stable either. It should in theory, but I think it depends on the sensors and that's again a lack of standards.
Finally - and this is the most ridiculous: I have a logic circle that also offers to double as movement sensor. I quickly learned that it would as expected turn on light when detecting motion. And when not detecting motion any more it will turn off ligths as expected... and then turn them back on because the image its seeing is changing because, well... it got darker in the room. Light on - lights off - lights on - lights off... 😂
So this is lack of standards for these motion sensors that is "homekit" certified.
I think mine will maximum report back once per minute. I can get it to work in the aqara home app because it offers the more correct logic (turn off if no movement has been observed for xx minutes). The hue motion sensors might be working better and reporting every event?
It could also be how sensitive they are? Its not that I'm completely motionless for 5 minutes, but I might be standing still only moving my hands. That's also a lack of standards. At the very least you should be able to adjust sensitivity.
Talk about reverse-inventing the wheel... 😂
Edit: re-reading your message. The sensor will look no more often than once per minute. I can also see that in the logs of the sensor. Logs every whole minute. I set the off delay to 5 or 10 minutes, so that cannot be it...