apple is always good for surprises.
there are reports about issues with homekit after an upgrade to ios 16.2. especially after an upgrade of apple tv/home pod.
it is unclear what root cause of the issue and how to fix it.
please dont upgrade ios 16.2 if you use homekit with openhab and it is important for you to keep homekit working.
if you have upgraded already and it is working/not working, please report here or on the ticket
Do you know yet if it is the 16.2 upgrade or the new HomeKit architecture upgrade contained in it?
My understanding is that if you have any older devices in your “home” (that are unable to upgrade to iOS 16) then the upgrade keeps the older style architecture.
You can upgrade to iOS 16.2, just don’t “upgrade the home” in Home app, which is a manual step AFAICT (mine still warns me about upgrading because my wife’s phone and watch are still on 16.1).
Once the HomeKit architecture is updated, an iPad will no longer be considered a home hub.
Only Apple TV (4th Gen) and HomePod Mini will still be supported.
Apple provides this info only in the “small fonts” on their pages… and after the update, there is no way back at this time…
i did an update yesterday to 16.2 everythink works as expected, but i don’t see this dedicated upgrade message in iOS app at all. not sure what to think about it
Jacek, thank you for the confirmation.
in my case, upgrade is hidden in home settings in “Software update”. please check there.
WARNING: this will kill your openhab-homekit setup with high probability
I upgrade to 16.2 some days ago - no issue.
Today I updated Home App as well - HomeKit stopped working for me with OpenHAB. Unfortunately I didn’t see this discussion before
Each time I open Home App I see the following error in the log.
] [.server.impl.connections.HttpSession] - Exception encountered while verifying pairing
java.lang.Exception: Unknown user .......
Error message changed indeed - but its still not working.
2022-12-20 21:12:38.627 [WARN ] [rver.impl.http.impl.AccessoryHandler] - Error handling homekit http request
java.lang.NullPointerException: null
at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelRead0(AccessoryHandler.java:53) [bundleFile:?]
at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelRead0(AccessoryHandler.java:1) [bundleFile:?]
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99) [bundleFile:4.1.72.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [bundleFile:4.1.72.Final]
at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61) [bundleFile:4.1.72.Final]
at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:370) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:66) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) [bundleFile:4.1.72.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [bundleFile:4.1.72.Final]
at java.lang.Thread.run(Thread.java:829) [?:?]
2022-12-20 21:12:38.628 [WARN ] [rver.impl.http.impl.AccessoryHandler] - Exception caught in web handler
java.lang.NullPointerException: null
at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelInactive(AccessoryHandler.java:46) ~[?:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262) [bundleFile:4.1.72.Final]
at io.netty.channel.AbstractChannelHandlerContext.access$300(AbstractChannelHandlerContext.java:61) [bundleFile:4.1.72.Final]
at io.netty.channel.AbstractChannelHandlerContext$4.run(AbstractChannelHandlerContext.java:253) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:66) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) [bundleFile:4.1.72.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [bundleFile:4.1.72.Final]
at java.lang.Thread.run(Thread.java:829) [?:?]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) [bundleFile:4.1.72.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [bundleFile:4.1.72.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [bundleFile:4.1.72.Final]
at java.lang.Thread.run(Thread.java:829) [?:?]
Well that’s no good :(. It looks like an error when the iOS device hangs up on us. Not sure why that is, though. I’ll attempt to replicate when I have a minute.
Looks like I had a compilation problem in the JAR I posted yesterday, jumping back and forth among multiple branches. Release HomeKit 2022-12-20 v1 · ccutrer/openhab-addons · GitHub. I promise this is the exact JAR I’m currently running locally. You can update to it in console with:
And yes, it’s labeled as a 4.0.0-SNAPSHOT, but that’s just cause it’s built today. It works fine in a 3.4.0 openHAB (I’m not even actually to the final release yet).