I´ve updated openhab2 via openhabian-config getting this warning now every 20 seconds
2020-09-15 22:38:54.581 [WARN ] [.server.impl.connections.HttpSession] - Unrecognized request for /accessories
any suggestions?
I´ve updated openhab2 via openhabian-config getting this warning now every 20 seconds
2020-09-15 22:38:54.581 [WARN ] [.server.impl.connections.HttpSession] - Unrecognized request for /accessories
any suggestions?
do you use homekit / apple home app?
yes but cleared pairings and set smarthome:homekit allowUnauthenticated true via karaf
from the source code i cannot see how that could happen. actually, if allowUnauthenticated is true it should handle any requests without complain.
try to remove home from home.app and if you have ipad or apple tv disconnect them from the homekit home.
could it have sth. to do with the openhab cloud?
no. i dont think so. the error message is from homekit binding.
i checked the source code and the only option it could only happen if
i would first try to remove home from iphone/ipad/etc. restart iphone and try to add the openHAB bridge again
removed bridge from HK
restarted Ipad
saved HK-configuration again
allowUnauthenticated true
same warning without hk paired
so, you have no homes on ipad (and other iOS devices, like apple tv) and you still get these error messages?
please enable more log. maybe we will get the IP address of the device that keep querying the accessories.
to enable more logging in the console
log:set TRACE org.openhab.io.homekit
log:set TRACE io.github.hapjava
pay attention to IP address in the log file and check which device in your network has this IP.
try also with - this would force the PIN check on pairing.
allowUnauthenticated false
2020-09-17 00:19:42.575 [TRACE] [rver.impl.http.impl.AccessoryHandler] - New HomeKit connection from /192.168.178.72:57862
2020-09-17 00:19:42.575 [TRACE] [server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 139, cap: 1024) [/192.168.178.72:57862]:
474554202F6163636573736F7269657320485454502F312E310D0A436F6E74656E742D547970653A204170706C69636174696F6E2F6A736F6E0D0A617574686F72697A6174696F6E3A203033312D34352D3135340D0A636F6E6E656374696F6E3A206B6565702D616C6976650D0A686F73743A203139322E3136382E3137382E37323A393132340D0A0D0A
2020-09-17 00:19:42.578 [WARN ] [.server.impl.connections.HttpSession] - Unrecognized request for /accessories
2020-09-17 00:19:42.580 [TRACE] [er.impl.http.HomekitClientConnection] - 404 /accessories
2020-09-17 00:19:42.582 [TRACE] [server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 69, cap: 256) [/192.168.178.72:57862]:
485454502F312E3120343034204E6F7420466F756E640D0A436F6E74656E742D4C656E6774683A20300D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A
2020-09-17 00:19:42.599 [TRACE] [rver.impl.http.impl.AccessoryHandler] - Terminated HomeKit connection from /192.168.178.72:57862
2020-09-17 00:20:12.547 [TRACE] [rver.impl.http.impl.AccessoryHandler] - New HomeKit connection from /192.168.178.72:58008
2020-09-17 00:20:12.548 [TRACE] [server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 139, cap: 1024) [/192.168.178.72:58008]:
474554202F6163636573736F7269657320485454502F312E310D0A436F6E74656E742D547970653A204170706C69636174696F6E2F6A736F6E0D0A617574686F72697A6174696F6E3A203033312D34352D3135340D0A636F6E6E656374696F6E3A206B6565702D616C6976650D0A686F73743A203139322E3136382E3137382E37323A393132340D0A0D0A
2020-09-17 00:20:12.550 [WARN ] [.server.impl.connections.HttpSession] - Unrecognized request for /accessories
2020-09-17 00:20:12.551 [TRACE] [er.impl.http.HomekitClientConnection] - 404 /accessories
2020-09-17 00:20:12.553 [TRACE] [server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 69, cap: 256) [/192.168.178.72:58008]:
485454502F312E3120343034204E6F7420466F756E640D0A436F6E74656E742D4C656E6774683A20300D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A
2020-09-17 00:20:12.556 [TRACE] [rver.impl.http.impl.AccessoryHandler] - Terminated HomeKit connection from /192.168.178.72:58008
In Paper UI > Configuration > Services > Homekit there is a field “Network Interface” in which I added the IP address of my openhab server.
No errors anymore
Thank you @yfre for helping out
2020-09-17 00:33:42.894 [TRACE] [er.impl.http.HomekitClientConnection] - 200 /accessories
2020-09-17 00:33:42.898 [TRACE] [server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 36919, cap: 65536) [/192.168.178.72:34148]:
@yfre i have the same issue on one of my hosts. 192.168.100.29 is openhab host…
2022-09-15 20:30:22.515 [TRACE] [rver.impl.http.impl.AccessoryHandler] - New HomeKit connection from /192.168.100.29:49468
2022-09-15 20:30:22.517 [TRACE] [server.impl.http.impl.LoggingHandler] - READ PooledUnsafeDirectByteBuf(ridx: 0, widx: 139, cap: 2048) [/192.168.100.29:49468]:
474554202F6163636573736F7269657320485454502F312E310D0A436F6E74656E742D547970653A204170706C69636174696F6E2F6A736F6E0D0A617574686F72697A6174696F6E3A203033312D34352D3135340D0A636F6E6E656374696F6E3A206B6565702D616C6976650D0A686F73743A203139322E3136382E3130302E32393A393132330D0A0D0A
2022-09-15 20:30:22.522 [WARN ] [.server.impl.connections.HttpSession] - Unrecognized request for /accessories
2022-09-15 20:30:22.524 [TRACE] [er.impl.http.HomekitClientConnection] - 404 /accessories
2022-09-15 20:30:22.528 [TRACE] [server.impl.http.impl.LoggingHandler] - WRITE PooledUnsafeDirectByteBuf(ridx: 0, widx: 69, cap: 256) [/192.168.100.29:49468]:
485454502F312E3120343034204E6F7420466F756E640D0A636F6E74656E742D6C656E6774683A20300D0A636F6E6E656374696F6E3A206B6565702D616C6976650D0A0D0A
2022-09-15 20:30:22.534 [TRACE] [rver.impl.http.impl.AccessoryHandler] - Terminated HomeKit connection from /192.168.100.29:49468
hm ?
please check that IP address is configured correctly for homekit binding. you can do it in via openhab UI → homekit binding.
if ip address correcty, please restart binding (or openhab) and check log files for any error during the restart.
i assume, you have a least one openhab item marked as homekit accessory (via metadata → homekit)
removing and clearpairings did the job. thank you