Can't connect to yahka with HomeKit.

[Marinek]

HI ;)

i'm using yahka for over 3 years now. It has alsways woking. since 2 month homekit displays a connection lost to all yahka controlled devices. Since then I can't established an connection to yahka with homekit anymore.

I'm using the beta version since 13.1 does the binding only to ip6 and the beta seemes to fixed that.

Details:

I have yahka and a Bridge configured as follows:

Please note that i tried the legacy and current version of the Advertiser.

In Homekit I can see the adapter when I try to add. It states, that the configuration may take some minutes. After that the connection state an error "The device is not visisble".

When I Input the wrong passcode, then this is recordnized. So I assume that a network connection is established.

Ôò¡                ŸN@b†c N   N   ܦ2é|¬IÛ4æX E  @  @ @UÀ¨²(À¨²'Ãäa8HŸ    °ÿÿ*¤  ´
f»      ŸN@bâc J   J   ¬IÛ4æXܦ2é| E  <  @ @UÀ¨²'À¨²(aÃä08HŸ þˆåÏ  ´
€`ånf»ŸN@být B   B   ܦ2é|¬IÛ4æX E  4  @ @U#À¨²(À¨²'Ãäa8HŸ0€
¼n  
f€`ånŸN@bßz Å   Å   ܦ2é|¬IÛ4æX E  ·  @ @T À¨²(À¨²'Ãäa8HŸ0€
U  
f€`ånPOST /pair-setup HTTP/1.1
Host: Yahka\0325151._hap._tcp.local
Content-Length: 6
Content-Type: application/pairing+tlv8

  ŸN@b{ B   B   ¬IÛ4æXܦ2é| E  4!&@ @3ýÀ¨²'À¨²(aÃä08HŸ‹€ýåÇ  
€`åtf N@be {  {  ¬IÛ4æXܦ2é| E m!'@ @1ÃÀ¨²'À¨²(aÃä08HŸ‹€ýè   
€`æÇfÂHTTP/1.1 200 OK
Content-Type: application/pairing+tlv8
Date: Sun, 27 Mar 2022 11:46:40 GMT
Connection: keep-alive
Transfer-Encoding: chunked

199
¥	-ÐUs-Èèji7gŠQYÿ„.+'0Qw$–Nšø§¯æ 5ðë!‡Œ`–ø¿E¢ê`ꌠó©>¹þŠƒ`€¸ƒ‡Ó§òðCLDY—\ü'AµÏŒ@œ¼þ®Ãºlf!ê7˜Ô­þ´¢Ü»ø{9T‚<cS¼²ý¬ª¡xB³½ØµŒ­«Ô‚—Ë™.Þžþ«—GҐ&ƒ/MLXË?¸"^ÎF[ ;6þkQ‹BIžåÑØ5
îü„ça®§¡l{RA¥_5Пr‡	ȸWáø™‘‹Ë“XÁ½aÀ÷튘D½«)¶tƒùËv>t
Í*!gj1¾lÐþ@¯Qäf¸\Vш· Ãf@8ÛT"ªl&E7#DÉà.MGF?nÕùBGª•’›>·úYž{™ÌñK|´÷󂸾ãÂЩ¾®cÖZÕû‚˜øÎJTAö¡uI&Œí~ód&bÀçÖ#k´ÿ¤!a:¯.¹Vxmª´(óºxôuš\º”±*-Ò^\
0

tcpdum reveals at least a positiv communication. I'm hosting yahka on an ibroker-bian on a raspberry pi 6.

Plattform
    linux
Modell
    ARMv7 Processor rev 3 (v7l)
Node.js
    v17.6.0 

There is also an test device configured. I deleted yahka and its data folder.

2022-03-27 16:23:39.552  - debug: yahka.0 (8610) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-03-27 16:23:39.609  - debug: yahka.0 (8610) Objects client ready ... initialize now
2022-03-27 16:23:39.613  - debug: yahka.0 (8610) Objects create System PubSub Client
2022-03-27 16:23:39.614  - debug: yahka.0 (8610) Objects create User PubSub Client
2022-03-27 16:23:39.653  - debug: yahka.0 (8610) Objects client initialize lua scripts
2022-03-27 16:23:39.661  - debug: yahka.0 (8610) Objects connected to redis: 127.0.0.1:9001
2022-03-27 16:23:39.665  - silly: yahka.0 (8610) redis psubscribe cfg.o.system.user.*
2022-03-27 16:23:39.682  - silly: yahka.0 (8610) redis psubscribe cfg.o.enum.*
2022-03-27 16:23:39.689  - silly: yahka.0 (8610) objectDB connected
2022-03-27 16:23:39.693  - debug: yahka.0 (8610) Redis States: Use Redis connection: 127.0.0.1:9000
2022-03-27 16:23:39.706  - debug: yahka.0 (8610) States create System PubSub Client
2022-03-27 16:23:39.708  - debug: yahka.0 (8610) States create User PubSub Client
2022-03-27 16:23:39.727  - debug: yahka.0 (8610) States connected to redis: 127.0.0.1:9000
2022-03-27 16:23:39.728  - silly: yahka.0 (8610) statesDB connected
2022-03-27 16:23:39.911  - info: yahka.0 (8610) starting. Version 0.14.0 (non-npm: jensweigele/ioBroker.yahka) in /opt/iobroker/node_modules/iobroker.yahka, node: v17.6.0, js-controller: 4.0.18
2022-03-27 16:23:39.951  - info: yahka.0 (8610) adapter ready, checking config
2022-03-27 16:23:39.953  - debug: yahka.0 (8610) creating bridge
2022-03-27 16:23:39.968  - info: yahka.0 (8610) adding Test with UUID: d56da95b-60fa-48b9-928f-cefdb6e7cdc4
2022-03-27 16:23:39.971  - debug: yahka.0 (8610) [Test] adding Service Test
2022-03-27 16:23:39.979  - debug: yahka.0 (8610) added subscription for: [state]hm-rpc.0.MEQ0333665
2022-03-27 16:23:39.982  - debug: yahka.0 (8610) reading state from ioBroker [hm-rpc.0.MEQ0333665]
2022-03-27 16:23:39.984  - info: yahka.0 (8610) publishing bridge Yahka on 192.168.178.39 using ciao
2022-03-27 16:23:40.051  - debug: yahka.0 (8610) change event from ioBroker via [hm-rpc.0.MEQ0333665]null
2022-03-27 16:23:40.052  - debug: yahka.0 (8610) state was filtered - notification is canceled
2022-03-27 16:23:40.053  - debug: yahka.0 (8610) read state from ioBroker [hm-rpc.0.MEQ0333665]: null
2022-03-27 16:23:40.055  - debug: yahka.0 (8610) [Test.CurrentPosition] initializing homekit with value from ioBroker(undefined) to homekit as (undefined)
2022-03-27 16:23:40.248  - debug: yahka.0 (8610) [Test.CurrentPosition] got a set event, hkValue: 0
2022-03-27 16:23:40.249  - debug: yahka.0 (8610) [Test.CurrentPosition] set was initiated from ioBroker - exiting here
2022-03-27 16:23:40.251  - silly: yahka.0 (8610) States system redis pmessage system.adapter.yahka.0.logLevel/system.adapter.yahka.0.logLevel:{"val":"silly","ack":true,"ts":1648391020033,"q":0,"from":"system.adapter.yahka.0","lc":1648391020033}
2022-03-27 16:23:40.339  - silly: yahka.0 (8610) redis psubscribe cfg.o.system.adapter.*

After that no more log entries =(

[samoht0403]

@Marinek: did you find a solution? I'm desperately searching as well...