search

openhab / openhab-addons

Add-ons for openHAB
https://www.openhab.org/
Eclipse Public License 2.0
1.88k stars 3.59k forks source link

[homekit] All accessories are in "No response" state after upgrade to iOS 16.2 (and Home upgrade) #13949

Closed georgo closed 1 year ago

georgo commented 1 year ago

Expected Behavior

Homekit accessories are available in Home app.

Current Behavior

Hi,

today I upgraded all my devices (incl. my home hub - Apple TV) to iOS 16.2 - Home app asks to upgrade it self, so I did it. Since then, all openHAB accessories are in state "No response"

I tried completely remove homekit from openHAB, incl. deletion of homekit.json file in jsondb directory and called clearPairings

After I try re-pair openHAB again in Home, it successfully find bridge, find all accessories, but all of them remains in "No response" state.

What I noticed in homekit.json is user:

  "user_2e:bd:52:5e:c5:73EF874ABF-3C30-4B6A-86CB-80D3D97A9D12": {
    "class": "java.lang.String",
    "value": "[REDACTED]"
  }

But during pairing, my log i flooded with following error:

2022-12-13 23:12:19.900 [WARN ] [.server.impl.connections.HttpSession] - Exception encountered while verifying pairing
java.lang.Exception: Unknown user: 1EAA342F-4183-49E7-B84E-1055D8D73E95
    at io.github.hapjava.server.impl.pairing.PairVerificationManager.stage2(PairVerificationManager.java:113) ~[bundleFile:?]
    at io.github.hapjava.server.impl.pairing.PairVerificationManager.handle(PairVerificationManager.java:51) ~[bundleFile:?]
    at io.github.hapjava.server.impl.connections.HttpSession.handlePairVerify(HttpSession.java:127) [bundleFile:?]
    at io.github.hapjava.server.impl.connections.HttpSession.handleRequest(HttpSession.java:56) [bundleFile:?]
    at io.github.hapjava.server.impl.connections.ConnectionImpl.doHandleRequest(ConnectionImpl.java:56) [bundleFile:?]
    at io.github.hapjava.server.impl.connections.ConnectionImpl.handleRequest(ConnectionImpl.java:49) [bundleFile:?]
    at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelRead0(AccessoryHandler.java:52) [bundleFile:?]
    at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelRead0(AccessoryHandler.java:17) [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) [?:?]

^^ where it appears to be more user ids in logs

Possible Solution

I have no idea, what changed in 16.2 in technical terms, but here is some article about it: https://9to5mac.com/2022/10/25/ios-16-2-new-architecture-home-app/ and https://www.homekithelper.net/tips/ios-16-matter-thread-new-architecture

Steps to Reproduce (for Bugs)

  1. Upgrade Apple devices to newest production iOS/iPadOS/...
  2. Open Home app, go to Home settings and upgrade your home (FYI there is no turning back)
  3. openHAB becomes unresponsible

Environment

Running openHAB 3.4.0.M6 (but it didn't work in 3.4.0.M4 either) in docker on Raspberry Pi, with host network mode This is my homekit.cfg:

org.openhab.homekit:port=9123
org.openhab.homekit:pin=123-45-679
org.openhab.homekit:networkInterface=192.168.96.8
org.openhab.homekit:useOHmDNS=false
org.openhab.homekit:blockUserDeletion=false
org.openhab.homekit:name=openHAB

Before upgrade to iOS 16.2 everything works perfect.

jlaur commented 1 year ago

FYI @ccutrer, @yfre

ccutrer commented 1 year ago

I'm just about to press Home upgrade right now. Maybe I shouldn't? ;) (yes, I will)

yfre commented 1 year ago

@georgo please make sure you have no apple tv/homepod acting as homekit bridge. just disable it for some time (you can activate it later). according to logs, you have somewhere an ios device that is still paired with old paring to openhab and it keeps trying to connect and openhab reject as unknown user as you have cleaned up old pairing. so, i would suspect it is the bridge

yfre commented 1 year ago

here is one more report https://community.openhab.org/t/homekit-doesnt-work-with-homepod/141079/4

georgo commented 1 year ago

@yfre Good point, I'll try tomorrow morning.

yfre commented 1 year ago

just did upgrade of my iphone to 16.2. home app works as usual, all 120+ accessories are responding. apple tv is still on 16.1. will upgrade tomorrow.

ktgeek commented 1 year ago

Just adding another voice, I don't have any good debug/workaround steps. Just upgraded all the OSes on Mac, AppleTV, phone, and watch, then upgraded the Home to the new framework. Tossing the Unknown User error and nothing is responding. Once the family is asleep I'll try rebooting all the devices that can be hubs, currently one of my AppleTVs is.

Update: Rebooted the AppleTV that was acting as a hub, still got the error. Rebooted the OTHER AppleTV that became the hub, still got the error, and the original ATV is the hub again.

Update: removed OpenHAB from Home and cleared pairings and then re-added. All the devices were asked about and sorted, but still show as no response and the "Exception encountered while verifying pairing java.lang.Exception: Unknown user:" error continues.

maxulm commented 1 year ago

Saw this topic too late and ran into the same problem.

yfre commented 1 year ago

@ktgeek @maxulm can you try to disable apple tv bridge and see whether this helps? do you have real homekit devices connected directly and not via openHAB? are they working

maxulm commented 1 year ago

@yfre I do not have an Apple TV but a Homepod as bridge. If I turn it off, it works but is exremely slow. And no, besides the Homepod itself there are only OpenHab-Devices.

yfre commented 1 year ago

@maxulm ok. thank you for the test. so, the issue is the homepod or apple tv acting as bridge.

could you please try one more thing, if you have access to karaf console please executed following command

homekit:allowUnauthenticated true

and check whether it works with homepod

yfre commented 1 year ago

just did small research and there are reports about similar issue with real homekit devices, without openHAB e.g. https://developer.nuki.io/t/ios-16-2-new-architecture-issues-homekit/18663

georgo commented 1 year ago

I tried homekit:allowUnauthenticated true yesterday, without effect.

do you have real homekit devices connected directly and not via openHAB? are they working

I have Eve Plugs and they're seems working. But Eve Room (thermometer) is not responding.

yfre commented 1 year ago

apple, apple, what have you done.

it looks like Apple did a breaking change. in addition, Apple has also removed the official documentation about the homekit protocol from the developer portal (at least i cannot find it anymore), so, no idea what they have changed.

we would need to wait for more reports and monitor other open source homekit implementation, e.g. homebridge.

georgo commented 1 year ago

FYI homebridge.io seems to be working for me.

grzegorz914 commented 1 year ago

On my side iOS16.2 running on all apple devices, Apple TV and 2 HomePods mini, iPhone, iPad, all working fine with new architecture, in the new architecture the data is updated in background constantly, so after open home.app the values are already updated no need to refresh it during app open. I have convert my system some weeks ago with beta update and the response was slow but now is just all fine. Some info here: https://www.homekithelper.net/tips/ios-16-matter-thread-new-architecture

P.S.- 114 accessory on openHAB 3.4 and 16 Homebridge IMG_0773

ktgeek commented 1 year ago

@ktgeek @maxulm can you try to disable apple tv bridge and see whether this helps? do you have real homekit devices connected directly and not via openHAB? are they working

Unfortunately, they removed the ability to disable the AppleTV as a hub in the new release (and I have homepods.) If I have a chance later today, I'll try to unplug everything and recreate what @maxulm did.

As others have noted, Homebridge.io continues to work, as well as the two pure Homekit devices I have: the MyQ home bridge and an iDevices outdoor switch.

I also did try the allowAuthenticated without any success.

openhab-bot commented 1 year ago

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/homekit-ios-16-2-issues-dont-upgrade/142069/1

schariwari commented 1 year ago

Same here, updated all apple-device with actual OS (including the appleTV, which is my HomeKit-hub). Did then the "manual update" via my iPhone. -> all openHAB-devices are "not responding", everything which come through home-bridge into HomeKit is working well.

grzegorz914 commented 1 year ago

May be reboot all devices

schariwari commented 1 year ago

Already done. BTW: Running OpenHAB 3.4.0 Build #3224

ccutrer commented 1 year ago

I haven't been able to upgrade my home yet, so can't try this myself. It's a long shot anyway (since apparently re-pairing doesn't help), but what happens if you add another accessory from openHAB? That sometimes works for me to force HomeKit to reconnect and re-read the accessory database, since it increments the version number essentially.

yfre commented 1 year ago

@georgo and others with issue.

if you have time, could please try following

e.g. in case of @georgo homekit.json should contain these 2 entries "user_2e:bd:52:5e:c5:73EF874ABF-3C30-4B6A-86CB-80D3D97A9D12": { "class": "java.lang.String", "value": "[REDACTED]" }, "user_2e:bd:52:5e:c5:731EAA342F-4183-49E7-B84E-1055D8D73E9": { "class": "java.lang.String", "value": "[REDACTED]" },

i known, it is pretty tricky to edit homekit.json, but this would be a huge help for troubleshooting.

background: openHAB homekit addon stores the "key" used for the encryption for each device / user in homekit.json as the "value" insides of the user entry. with ios16.2 we get suddenly requests from unkown user. my hope that the same key can be used for the uknown device.

georgo commented 1 year ago

I tried to duplicate user record in homekit.json as suggested, but still not works. Seems like encryption key is different (?)

2022-12-14 19:00:16.491 [WARN ] [impl.pairing.PairVerificationManager] - Invalid signature. Could not pair openHAB

^^ appears multiple time in log since then

yfre commented 1 year ago

@georgo thanks for checking. the only way to get the key is the pairing. so, probably there were some changes. you can also check in the backup directory the older homekit.json. maybe the unknown user was known before and have the key in the older homekit.json

yfre commented 1 year ago

i have upgraded all devices i could to 16.2 including apple tv, mac, ipad. all works fine. but i cannot switch to homekit new architecture as i have older apple devices at home with no ios 16 upgrade available. so, im afraid i will not be able to completely reproduce the issues

schariwari commented 1 year ago

@ccutrer: To answer your question: If I add something new (in this case "just" a switchable), simply nothing happened at the HomeKit-side. -> No new item at the HomeKit-side -> nothing changed at the "Not responding"-story.

ccutrer commented 1 year ago

@ccutrer: To answer your question: If I add something new (in this case "just" a switchable), simply nothing happened at the HomeKit-side.

-> No new item at the HomeKit-side

-> nothing changed at the "Not responding"-story.

Ok, thanks. I figured that's what would happen, but wanted to be sure.

sfranzis commented 1 year ago

i have upgraded all devices i could to 16.2 including apple tv, mac, ipad. all works fine. but i cannot switch to homekit new architecture as i have older apple devices at home with no ios 16 upgrade available. so, im afraid i will not be able to completely reproduce the issues

If you don't need your older devices to use HomeKit, then update should still be possible.

ktgeek commented 1 year ago

i have upgraded all devices i could to 16.2 including apple tv, mac, ipad. all works fine. but i cannot switch to homekit new architecture as i have older apple devices at home with no ios 16 upgrade available. so, im afraid i will not be able to completely reproduce the issues

@yfre, @ccutrer is there anything we could be collecting data/log wise to help here?

ccutrer commented 1 year ago

I was able to sneakily update my wife's phone, and upgrade my own home to the new framework. Strangely... everything is working for me. Maybe because I'm not at home?

I am seeing an error in my log, though:

2022-12-16 12:08:22.455 [WARN ] [.server.impl.connections.HttpSession] - Could not handle request
java.lang.RuntimeException: Unrecognized method: 5
        at io.github.hapjava.server.impl.pairing.PairingUpdateController.handle(PairingUpdateController.java:36) ~[bundleFile:?]
        at io.github.hapjava.server.impl.connections.HttpSession.handleAuthenticatedRequest(HttpSession.java:87) [bundleFile:?]
        at io.github.hapjava.server.impl.connections.ConnectionImpl.doHandleRequest(ConnectionImpl.java:55) [bundleFile:?]
        at io.github.hapjava.server.impl.connections.ConnectionImpl.handleRequest(ConnectionImpl.java:49) [bundleFile:?]
        at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelRead0(AccessoryHandler.java:52) [bundleFile:?]
        at io.github.hapjava.server.impl.http.impl.AccessoryHandler.channelRead0(AccessoryHandler.java:17) [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) [?:?]

This corresponds to a "list pairings" request that HAP-java has not implemented (but is documented in the public specification), so I'm going to try and implement that as soon as I can. It's a long shot if others aren't seeing these errors if implementing it will help them, but it's the best I have to go on at the moment.

yfre commented 1 year ago

"list pairing", this sounds promising. this would also explain why homebridge is working, it is implemented there https://github.com/homebridge/HAP-NodeJS/blob/0655c18fc3ccc0637166ccfd915bf7aef0d2b14f/src/lib/HAPServer.ts#L822

i need urgently to talk to santa about new iphone for my son so that i can upgrade my homekit as well..

ccutrer commented 1 year ago

Yup, that's where I found what it's supposed to be doing :). then I looked in the spec for that name.

As for your son... does he use HomeKit? If not, you can force it to upgrade anyway. I have one device that can't be updated. And it kept warning me about other people and devices that I know have been updated. The whole thing still feels a bit buggy on Apple's end.

ccutrer commented 1 year ago

I've written the code to implement list pairings, but have not had time to test it. I'm finally home, and my own Home app is still working. I've never gotten the unrecognized user in my log, so I'm trepitous that this will actually fix people that are broken.

CHTHSCH commented 1 year ago

Will this make it in the final release of openHAB 3.4?

ccutrer commented 1 year ago

I don't know. I've got a busy weekend (and week!) in real life, so I may not have time to finish up my PR before release. And that's even assuming the direction I'm going will fix the issues people are experiencing, which isn't certain. I can promise this is top of my list for discretional development time, though. And it's also possible one of the other contributors can pick up the ball and finish up (which is why I pushed up my draft code so early). So... we'll try!

ktgeek commented 1 year ago

After not working for a few days, I got it working again, and I think a change that @ccutrer made to the underlying HAP-Java code helped, but I'm not 100% sure. For a big long story you can read https://github.com/hap-java/HAP-Java/pull/175#issuecomment-1356350838

Up above in https://github.com/openhab/openhab-addons/issues/13949#issuecomment-1351802299 @yfre suggested replacing the erroring user id from the old file and overlying it over the new value. What I did in my novel on the other PR, is left the existing code in the current homekit.json alone, and added the whole 4 line json for the erroring user over to homekit.json.

It would be good for someone to test if this works without @ccutrer's code so we can see if that's actually part of the key to it. I think it is, but I had so many moving parts and pairing/unpairing that an easier test might help.

UPDATE (about 30 min later.) I had two home hub devices (an AppleTV and a HomePod mini) unplugged while I was doing the other tinkering. When I pulled one back in, my Unknown user error came back and HomeKit broke again. I transported the user over again, and I'm working again. Same thing when I plugged the other in.

I now wonder if the HomeKit upgrade process as it happens on each hub needs to clear out the same keys, but we get confused because we've already done it? (I have 4 AppleTVs and 4 HomePod minis... I wonder if the people who are working have the simple case of only one hub?)

ccutrer commented 1 year ago

Just an update that I got a little bit of time tonight. There are definitely some problems in the pairing process that I'm going to work through, but don't have any more time tonight. Implementing list-pairings was not sufficient to allow it to pair cleanly.

ccutrer commented 1 year ago

I'm pretty sure I've fixed this. Anyone that can test, please do - it's highly likely that there are different topologies that HomeKit will work a little bit differently. You can download the pre-release JAR from https://github.com/ccutrer/openhab-addons/releases/tag/homekit-20221219-01.

The only required PR is https://github.com/openhab/openhab-addons/pull/13982, but https://github.com/openhab/openhab-addons/pull/14016 and https://github.com/openhab/openhab-addons/pull/14017 greatly improve the experience when rapidly unpairing and re-pairing iOS devices with openHAB.

maxulm commented 1 year ago

Interesting article: https://www.heise.de/news/HomeKit-und-iOS-16-2-Probleme-nach-Umstieg-auf-neue-Architektur-7408227.html

schariwari commented 1 year ago

Hm, I'm on 3.4.0. Release Build, did a "update 298 https://github.com/ccutrer/openhab-addons/releases/download/homekit-20221219-01/org.openhab.io.homekit-3.4.0-SNAPSHOT.jar" then restarted the Homekit-bundle and have no effect; All devices in the HomeKit-app appear still " not responding"

a "bundle:list | grep Homekit" shows: 298 │ Active │ 80 │ 3.4.0.202212192047 │ openHAB Add-ons :: Bundles :: IO :: Homekit so it looks like the update has been done. Did I miss something??

ccutrer commented 1 year ago

Hm, I'm on 3.4.0. Release Build, did a "update 298 https://github.com/ccutrer/openhab-addons/releases/download/homekit-20221219-01/org.openhab.io.homekit-3.4.0-SNAPSHOT.jar" then restarted the Homekit-bundle and have no effect; All devices in the HomeKit-app appear still " not responding"

Do you have a hub (Apple TV 4th gen, HomePod)? If so, you may want to try to restart them. I was definitely in a state yesterday where the hub completely refused to connect to openHAB until I rebooted it. Note that with the new Home architecture, it seems that connections will always come from the active hub, even if you're controlling it from your phone.

Additionally, do you have any errors in your openhab.log? Note that a warn Unknown User: <GUID> once (per HomeKit instance) is fine in the log, as long as it doesn't keep repeating.

schariwari commented 1 year ago

Thanks for responding!

Yep, i have a hub, an Apple TV, which is updated to the "new architecture". Will reboot it later, currently my government does not grant access to it (aka my wife is watching daily soap). Will report the outcome.

No, i do not have seen any warning or error, the only line it drops every restart of the bundle is "2022-12-20 17:01:59.369 [INFO ] [mekit.internal.HomekitChangeListener] - Created 93 HomeKit items in instance 1 (no change from prior configuration)." So far it seems to be running on the OH-side, but the log is currently not in debug mode.

ccutrer commented 1 year ago

currently my government does not grant access to it (aka my wife is watching daily soap)

Lolol! I know the feeling. Though I was really confused when my notification truncated that at "Will reboot it later, currently my government..."

schariwari commented 1 year ago

:-)

stValDor commented 1 year ago

Hi all, I have the same problem (since I didn't read @yfre 's announcement)

is there any way to check the user id (maybe with Mac keyring "Schlüsselbund" app) or the "value" attribute stored along with the userid in the homekit.json file ?

Stefan136 commented 1 year ago

I have the same issue - installed the snapshot, but still the same.

openhab> bundle:list | grep Homekit 277 | Active | 80 | 3.4.0 | openHAB Add-ons :: Bundles :: IO :: Homekit openhab> update 277 https://github.com/ccutrer/openhab-addons/releases/download/homekit-20221219-01/org.openhab.io.homekit-3.4.0-SNAPSHOT.jar openhab> bundle:restart org.openhab.io.homekit

I use AppleTV and/or HomePod as Gateways. I already restarted my AppleTV, but still the same. Only the error message changed since I updated the binding. Before I got and "unknown user" exception. Now its

2022-12-20 18:52:32.555 [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 18:52:32.555 [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) [?:?]

ccutrer commented 1 year ago

Looks like I had a compilation problem in the JAR I posted yesterday, jumping back and forth among multiple branches. https://github.com/ccutrer/openhab-addons/releases/tag/homekit-20221220-01. I promise this is the exact JAR I'm currently running locally. You can update to it in console with:

update org.openhab.io.homekit https://github.com/ccutrer/openhab-addons/releases/download/homekit-20221220-01/org.openhab.io.homekit-4.0.0-SNAPSHOT.jar

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).

ktgeek commented 1 year ago

Looks like I had a compilation problem in the JAR I posted yesterday, jumping back and forth among multiple branches. https://github.com/ccutrer/openhab-addons/releases/tag/homekit-20221220-01. I promise this is the exact JAR I'm currently running locally. You can update to it in console with:

update org.openhab.io.homekit https://github.com/ccutrer/openhab-addons/releases/download/homekit-20221220-01/org.openhab.io.homekit-4.0.0-SNAPSHOT.jar

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).

Looks like @ccutrer getting ahead of the curve snuck in java 17 as a requirement for this jar based on the error I got in my local env. I'm still on 11, so heads up for folks like me. (Guess its time to go 17)

ccutrer commented 1 year ago

Lulz, yup, had to to build against current main of openhab-addons which now requires java17. 3.4.0 allows either java 11 or java 17. I had zero issues upgrading to java 17 this morning myself (just apt install openjdk-17-jdk on an Ubuntu system, though you can probably get away with openjdk-17-jre-headless if you're not compiling anything). I'd feel bad, but this has been a bit of a whirlwind.