HomeKit crashed - reconnecting impossible

Add-ons Other
,
1

Hi,

after having a crash of the homekit addon a few hours ago, I’m no longer able to connect via homekit.
I’ve cleaned the tmp and the cache folder, deleted the homekit.json file, reinstalled the service several times and changed the password but it doesn’t work.
This is the log:

openhab> log:set TRACE io.github.hapjava
openhab> log:tail io.github.hapjava
17:50:09.876 [TRACE] [erver.impl.http.impl.AccessoryHandler] - New HomeKit connection from /192.168.178.207:49275
17:50:09.877 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 125, cap: 1024) [/192.168.178.207:49275]:
504F5354202F706169722D736574757020485454502F312E310D0A486F73743A206F70656E4841422E5F6861702E5F7463702E6C6F63616C0D0A436F6E74656E742D4C656E6774683A20360D0A436F6E74656E742D547970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A0D0A000100060101

17:50:09.895 [TRACE] [va.server.impl.pairing.PairingManager] - Starting pair for openHAB
17:50:09.973 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /pair-setup
17:50:09.976 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 513, cap: 1024) [/192.168.178.207:49275]:
485454502F312E3120323030204F4B0D0A436F6E74656E742D747970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A436F6E74656E742D4C656E6774683A203430390D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A0601020

17:50:19.539 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 578, cap: 1024) [/192.168.178.207:49275]:
504F5354202F706169722D736574757020485454502F312E310D0A486F73743A206F70656E4841422E5F6861702E5F7463702E6C6F63616C0D0A436F6E74656E742D4C656E6774683A203435370D0A436F6E74656E742D547970653A206170706C69636174696F6E2F706169726

17:50:19.542 [TRACE] [va.server.impl.pairing.PairingManager] - Entering second stage of pair for openHAB
17:50:19.628 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /pair-setup
17:50:19.630 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 172, cap: 232) [/192.168.178.207:49275]:
485454502F312E3120323030204F4B0D0A436F6E74656E742D747970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A436F6E74656E742D4C656E6774683A2036390D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A0601040440B8A

17:50:19.684 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 280, cap: 1024) [/192.168.178.207:49275]:
504F5354202F706169722D736574757020485454502F312E310D0A486F73743A206F70656E4841422E5F6861702E5F7463702E6C6F63616C0D0A436F6E74656E742D4C656E6774683A203135390D0A436F6E74656E742D547970653A206170706C69636174696F6E2F706169726

17:50:19.716 [TRACE] [va.server.impl.pairing.PairingManager] - Entering third stage of pair for openHAB
17:50:19.724 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /pair-setup
17:50:19.727 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 244, cap: 256) [/192.168.178.207:49275]:
485454502F312E3120323030204F4B0D0A436F6E74656E742D747970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A436F6E74656E742D4C656E6774683A203134300D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A0601060587451587E5EDC2

17:50:19.761 [TRACE] [erver.impl.http.impl.AccessoryHandler] - Terminated HomeKit connection from /192.168.178.207:4927517:50:19.799 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 158, cap: 1024) [/192.168.178.207:49276]:
504F5354202F706169722D76657269667920485454502F312E310D0A486F73743A206F70656E4841422E5F6861702E5F7463702E6C6F63616C0D0A436F6E74656E742D4C656E6774683A2033370D0A436F6E74656E742D547970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A0D0A06010103201B6F6CD4D37703BB350A7CE5BDF9E22EF21AF4DB943956885755F4A62A583277

17:50:19.802 [TRACE] [erver.impl.http.impl.AccessoryHandler] - New HomeKit connection from /192.168.178.207:49276
17:50:19.804 [TRACE] [.impl.pairing.PairVerificationManager] - Starting pair verification for openHAB
17:50:19.810 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /pair-verify
17:50:19.813 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 244, cap: 256) [/192.168.178.207:49276]:
485454502F312E3120323030204F4B0D0A436F6E74656E742D747970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A436F6E74656E742D4C656E6774683A203134300D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A0601020565AEEB851D8

17:50:19.846 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 247, cap: 1024) [/192.168.178.207:49276]:
504F5354202F706169722D76657269667920485454502F312E310D0A486F73743A206F70656E4841422E5F6861702E5F7463702E6C6F63616C0D0A436F6E74656E742D4C656E6774683A203132350D0A436F6E74656E742D547970653A206170706C69636174696F6E2F70616972696E672B

17:50:19.852 [TRACE] [.impl.pairing.PairVerificationManager] - Completed pair verification for openHAB
17:50:19.856 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /pair-verify
17:50:19.859 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 105, cap: 256) [/192.168.178.207:49276]:
485454502F312E3120323030204F4B0D0A436F6E74656E742D747970653A206170706C69636174696F6E2F70616972696E672B746C76380D0A436F6E74656E742D4C656E6774683A20330D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A060104

17:50:19.870 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 78, cap: 512) [/192.168.178.207:49276]:
3C000EC5AF068663B33E58246AB1DDE39F95810AEE34E0E29E3BFD612243F642D4C37E6ACF7AE583A6AA96BF2FD71CBCB3663AFCA3C0A1354AF9C191F6ACEFF5D8229BAA0AA4C0BA3F2D49D1601B

17:50:19.873 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Received message of length 78. Existing buffer is 0
17:50:19.875 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Attempting to read message of length 78
17:50:19.876 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Read complete message
17:50:19.878 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Returning 1 results
17:50:19.881 [TRACE] [ver.impl.jmdns.JmdnsHomekitAdvertiser] - Re-creating service due to change in discoverability to false
17:50:21.884 [INFO ] [ver.impl.jmdns.JmdnsHomekitAdvertiser] - Registering _hap._tcp.local. on port 9124
17:50:21.977 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /accessories
17:50:21.992 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 34356, cap: 65536) [/192.168.178.207:49276]:
000437CDF04B37AB2D588510E66C23F090FAF212C00E8EADC5EDDCC393B01E2D8EC8DFC51F8EC0195C8846A03DFCC070642F48AEA941934184F5923AEEE441954325EA08DAB39DA4AE982860B43230EBA0AF51B4BF6D6756AC649139E8D2FA3CFA3EE3910ED1971AA7AB9

17:50:22.433 [TRACE] [.server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 180, cap: 512) [/192.168.178.207:49276]:
A200ED83C881BB52F0CBB80E225B1E99DDA982474E30A464FA02D2E0B89B7BA761BA1A40A7D5728E152BE19DAB59A39648EE7452DB3FEF18E6F8E1EC9B5782055DCB9894C47143EFAB60C9DC0E01E1E1FD47BBABB618DE80DAC2B43AB9D00D1969D59C15EC67E238DDBE20
17:50:22.435 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Received message of length 180. Existing buffer is 0
17:50:22.437 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Attempting to read message of length 180
17:50:22.438 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Read complete message
17:50:22.440 [TRACE] [ions.LengthPrefixedByteArrayProcessor] - Returning 1 results
17:50:22.444 [TRACE] [ver.impl.jmdns.JmdnsHomekitAdvertiser] - Re-creating service due to change in discoverability to true
17:50:24.447 [INFO ] [ver.impl.jmdns.JmdnsHomekitAdvertiser] - Registering _hap._tcp.local. on port 9124
17:50:24.449 [TRACE] [ver.impl.http.HomekitClientConnection] - 200 /pairings
17:50:24.452 [TRACE] [.server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 123, cap: 256) [/192.168.178.207:49276]:
6900E23BCF7357FC8D9AFF6D3E8273EAB1AADE87E491CBAA1EA6DBFD327F94F6F3459AC6483507031151F652DD3E863281E611CFA753B0D8824F9A93287FD1F2B06317D9BBE5B9B6EFFE7546AD0DEA929C4BDC7A41CAE96D246FC00FE3AAF9D75ECB1AEF2F698C73D86080F16AA0EF27524FF0D7D04D2546BB8C02

17:50:24.499 [TRACE] [erver.impl.http.impl.AccessoryHandler] - Terminated HomeKit connection from /192.168.178.207:49276

I’ve cutted the long hex values because of the body limitiation of the board.
iOS always tells me “Gerät ist nicht kompatibel.”

Maybe anybody can help?

Regards
Max

2

which item/homekit accessories you have? do you have color temperature?

3

I’ve found the problem.
It was the position of the lamellas on my window coverings.
OpenHAB reports it in percent, Homekit demands it as degree.
Having a value more than 90 degree caused an error in homekit.
I’ll write a transition.

Thank @yfre for your reply :slight_smile:

1 Like
4

in the recent snapshot i have added the conversion between percent and angles
if item is a dimmer it will convert automatically to angle for homekit

see this discussion OH3 Rollershutter and Apple HomeKit - #2 by Bruce_Osborne