I know I should not update on the first day, but I could not resist and did the HomePod/AppleTV 16.3 update right after it was released.
I’m using openHab 3.4.1 which restored functionality after I did the “new architecture” update of 16.2, but now I’m in the same situation again:
After several seconds of “Aktualisieren” (“updating”? I do not know how this is labeled in english), I get “Keine Antwort” (“no response”).
I tried restarting all AppleTVs and homePods, restarted the homekit bundle, but no success.
it looks like another nice fix from Apple.
it is not clear from the log what exactly happening but for some reason openHAB cannot find the pairing information anymore
see last raw:
Unknown user: 805F739A-9902-41EA-815C-45B77AD8F0C6
maybe new update has requested to deleted or maybe the user (device id) has changed.
the pairing information is stored in homekit.json
could you please check
whether you have an user entry in your homekit.json (in my setup it is under “/var/lib/openhab/jsondb/homekit.json” )
whether you have an entry for the user above in the homekit.json backups (e.g. search for AD9F0C5 in /var/lib/openhab/jsondb/backup)
@ccutrer any ideas how to troubleshoot this better?
Heh, it’s partially selfish. Ever since updating to the new architecture in 16.2, it’s almost impossible for me to update anything in the Home app, like renaming an accessory or changing its icon. I’ve been obsessively updating to betas in hopes that they’ve fixed that ;).
So to understand correctly @ccutrer:
You’re in the same boat as me, iOS/tvOS/audioOS 16.3 with previously enabled “new architecture”, but your setup is working?
Then I should probably try to re-pair my Apple devices with openHAB…
Warning, this potentially contains some sarcastic comments, but those are targeted agains Apples SW department, not the openHAB community:
Ok, so I did remove the openHAB bridge from the home app, stopped openHAB, removed homekit.json from jsondb.
Afterwards I was not able to complete the pairing. Tried again and the home app told me that the device is already added (while it was not listed in there as bridge) and I should reset it.
I opened up the openHAB console and did both “homekit allowUnauthenticated” and “homekit clearPairings”.
Afterwards I was able to pair the bridge again.
Full of anticipation I tapped through the endless dialogs of adding every single device to the particular room, potentially rename the device and skipping the “create automation” screen.
Yes I wondered with each of the 87 entries I added: Why was I being asked for the room name - when in my scheme it is always part of the device name. But this probably only bugs us heavy users with this much devices that are already configured and do not introduce themselves as “GenericLightBulb in Default room”
One eternity later it was done and the beautiful overview page was presented to me with all my 87 devices - each of them labeled as “no response”
So again: No blame to you - you’re doing a wonderful job and i owe you a debt of gratitude. Apple fucked this up (and I should not have switched to the new architecture).
Let’s hope this will stabilize with 16.4 - I heard they will fix some stuff in it.
just to add, the main challenges for us in openHAB dev community is the bad (or actually missing) communication from apple.
we have 0 information what new architecture means technically, we dont know what exactly apple changes from one iOS version to another, we dont know what home app expects from a bridge. we have only an old excerpt from 2 years old technical specification apple has published.
only based on your feedback and troubleshooting we are trying to understand what that change could be. please keep sharing your experience, although it could be a frustrating one. everything helps.
and of course we are also looking on other homekit implementation like homebridge, maybe they are more lucky to find the right config/implementation