New Homekit Architecture Support (Introduced in iOS 16.2 beta) #3250
Comments
|
Do you have any links to such announcements? |
|
I have entered precisely to see if there was any information about this, since yesterday I also read the news of the new architecture of the app, I will be attentive to this topic |
Ok again, what did you read? Is there a link? Screenshot? It is known that the "next Home app" should also support Matter as pürotocol I assume ... but more I do not know personally, thats why I was interested in what exactly you read |
|
Hi, E.g. here: https://9to5mac.com/2022/10/25/ios-16-2-new-architecture-home-app/ |
|
|
|
If only the Home app would be affected by the change, why would it affect the operation of other devices? |
|
That warning is for iOS/iPadOS/tvOS/macOS devices not "HomeKit" devices. |
donavanbecker
changed the title
Same as I read it, architecture of the app makes sense - hopefully improved, but they aren’t going to abandon supporting existing devices and homebridge is just seen as a device, a bridge. |
|
As I mentioned above, if I upgrade to a new architecture, the older devices will not be able to access the Home screen. IMHO this means something is changing that older tools (below 16.1) can't handle. |
|
Homebridge, like any other HomeKit accessory exposes itself to the HomeKit runtime over the HomeKit Accessory Protocol. Introducing breaking changes to that protocol (other than blocking uncertified accessories) would not only impact Homebridge, but also every other (native) HomeKit accessory. I doubt they will want to require firmware updates to all existing accessories to cope with such a change. Note that HomeKit apps talk to the HomeKit runtime using the HomeKit framework, a different protocol from HAP. The framework tends to be updated with each (major or minor) iOS version, but mostly adding features rather than breaking changes. The Home app uses the HomeKit framework, but also has some undocumented way to talk to the HomeKit runtime (notably for TV accessories, notifications, and other features not available to other HomeKit apps). In addition, it talks Airplay2 to speakers. I think/hope the new HomeKit architecture has to do mostly with the HomeKit runtime, how it syncs over iCloud with its peers on other Apple devices and on the Home hubs, and maybe/hopefully how it deals with bridged accessories. Currently there is a limit on the size of the HomeKit configuration, above which the syncing comes to a grinding hold. I’m hoping that the improved stability, especially for larger homes with many accessories will address this. |
|
I also hope that it is about the "Home Apps internal datastructures" (which would also be in line with "all systems needs to be updated to same 16.2 else do not work). This would mean it is irrelevant |
|
I will be upgrading mine once public beta comes out and I will report back. |
|
I have convert my Home to new architecture 16.2 also updated HomePod mini , iPad and iPhone to 16.2 and all working as before. Homebridge is not affected and working OK. |
|
@grzegorz914 Thanks for the report! Do you know if:
|
|
|
Here is an article explaining what’s changing with the new architecture. https://www.homekithelper.net/tips/ios-16-matter-thread-new-architecture |
|
Bummer, so it only works when you have a home hub. |
grzegorz914: |
|
Does anyone know if the new home architecture affects the usage of a homepod that is still on 16.1. ? I have three homepods mini on 16.2 but cannot update to the beta on my original homepod. |
|
When you see the official wording then as soon as you upgraded one device all "non 16.2" will be incompatible... but reality? ;-) |
Yeah that was what I thought. I have everything on 16.2 but can not update my original HomePod....was just wondering whether I use the ability to use it after I upgraded my home. Anyone here who tried this? |
Do you have the beta profile installed? |
|
I am on the public beta, es far as I know Apple only issues Betas to the HomePod minis right?
Am 17. Nov. 2022, 15:30 +0100 schrieb Donavan Becker ***@***.***>:
… > but can not update my original HomePod....
Do you have the beta profile installed?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
@ebaauw that's not correct, i have some accessories outside of BT range of the Homekit Hub, and when my iPhone gets close to them they go from No response to the actual state. So The hub is still only required when using remote access. I think the article shared is incorrect in saying that the state comes only from the hub. |
|
since iOS 16.2 is public now i'm very interested how homebridge will handle the Apple Home upgrade. |
|
Worked like a charm, did not notice many changes. Cameras react a little faster but as far as the first impression goes, that's it. |
|
@pelu89 |
|
I just applied the Home update and now all my devices are showing in the Home app with No Response. Anyone else having better luck?? |
|
I had this problem only on my Apple Watch before I updated the watch to the latest watchOS Version. I've got a wall mounted iPad that took a while to display anything in the home app, but since then it just works. Are all devices showing as "not responding" or just homebridge devices? |
|
I have two native Homekti devices and they appear to be back "on" now....they were previously showing the same No Response. Everything else is via Homebridge and is still showing no response :-( |
|
might sound stupid but have you rebooted your homebridge? everything is working fine on my end |
|
Yeah, I am going to reboot everything (firewall, apple tv, etc) to see if I can get things back :-). Will let you know how it goes |
|
SOOOOO relieved :-)......after rebooting the firewall, AppleTV, Homebridge docker and my Hubitat hub, all my devices are now back and functioning again. |
|
The universal solution: turning it off and back on again ^^ |
|
lol.....yep :-) |
|
👍🏼
Am 14. Dez. 2022, 16:22 +0100 schrieb kevinwestby ***@***.***>:
… Yeah, I am going to reboot everything (firewall, apple tv, etc) to see if I can get things back :-). Will let you know how it goes
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Hi there ! |
|
Well, I am not a homebridge developer or something, but why shouldn't it? All the other bridges also work without an update with iOS 16.2 (Hue, IKEA, ...), I think the interplay of devices using the new "architecture" only affects apples own devices. They heave to be updated in order to operate you Home (using HomeKit), all your "client devices" (bridges, lights, thermostats etc.) should keep working as they were. |
|
Hi, yes, Homebridge working well with new Home architecture.i ’m using many zigbee, z-wave (!!) devices throught Homebridge, and everything working well.2022. dec. 17. dátummal, 14:45 időpontban remibou78 ***@***.***> írta:
Hi there !
Please could you confirm Homebridge is supported in IOS16.2 with the new architecture Matter ? Behind Homebridge I've a CC2531 to connect zigbee accessories. Thanks per advance !
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
For me, updating has cause some issues with the SimpliSafe plug in - mainly cameras are reporting as privacy shutter enabled (it’s not for all three conditions in the SS app), or i am seeing a No Response error in Home and any iOS or Mac OS device - opening the camera in Home doesn’t show a stream either Ring cameras via the plug in seem ok The new architecture reintroduced some major issues with original HomePods and Apple TVs, a bit that was nasty about two years ago and fixed - the Default Audio (“Home Theater”) option from ATV to original HP no longer works - only temporary Airplay connections and that is flaky - five Apple TVs with single and stereo pair HP’s Also has reintroduced the Siri request failure to play music - the HP responds, but then “sorry there was a problem connecting to Apple Music” You can push a stream from you phone usually to get around this, but I am finding if you set the associated AppleTv to use the HP as a temporary audio output it seems to interfere with this - eventually you bash things enough and it works again until it doesn’t… |
|
Is there any update regarding this issue? Is this working for the rest of you? For me, nothing is working on my iOS 16.2 devices (I have accidentally adopted the new architecture). I'm running homebridge with When I scan the QR code with my 16.2 iPhone, it gets stuck on "Connecting to Bridge" state and then after a few minutes results in "Accessory Not Found" failure. It is working correctly though on my iOS 14 device. |
|
I think the "new Architecture" is a topic for later ... when I read newspapers right then new users can not activate that at all because removed by Apple because of many issues |
|
Thanks @Apollon77, so then I'm stuck until it gets resolved (one way or another) :) |
|
Switching to Ciao Advertiser. That solve the problem in other installations with homebridge 1.6.0 |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been closed as no further activity has occurred. |
Current Situation
Hi,
It's basically a question. Apple announced new Homekit architecture after ios (ipad) 16 (maybe 16.2). Homebridge is one of the biggest developments in the Homekit environment, and I really like it.
Does the new Homekit architecture affect the Homebridge application, or does everything continue as before?
br,
Tamás
Proposed Change
I don't know, if it should be change.
Additional Context
No response
The text was updated successfully, but these errors were encountered: