Monatsrückblick Januar/Februar 2026 ist online!

[t4x]

Hi zusammen,

ich muss euch um Hilfe bitten. Es passiert mir ständig, dass meine Geräte in HomeKit nicht erreichbar sind. Nach einem Neustart von yahka werden immer einige Fehler ins Logfile geschrieben. Ich kann leider nicht viel damit anfangen. Grundsätzlich läuft der Adapter auch nach dem Neustart, alle Geräte sind erreichbar und lassen sich bedienen.

Den pi starte ich jede Nach einmal durch (halte vorher Biobroker an).

Außerdem habe ich jetzt auch schon einen stündlichen yahka-neustart jede volle Stunde eingeplant, es kommt dennoch immer wieder einmal vor, dass die Geräte nicht erreichbar sind.

Ich habe auch schon allen Geräten den identischen Subservice-Namen gegeben, wie in folgendem Thread erwähnt:

viewtopic.php?t=7506#p78276

Hat leider auch keine Besserung gebracht.

Könnt ihr euch mein Log einmal ansehen. Da muss doch grundsätzlich was nicht stimmen. Fehlt vielleicht irgendwo eine Einstellung in yahka?

! ````
Caught 2018-05-01 20:21:22.253 error by controller[14]: Tue, 01 May 2018 20:21:22 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.253 error by controller[14]: Tue, 01 May 2018 20:21:22 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yah
Caught 2018-05-01 20:21:22.253 error by controller[14]: Tue, 01 May 2018 20:21:22 GMT socket.io-client:socket emitting packet with ack id 5
Caught 2018-05-01 20:21:22.252 error by controller[14]: Tue, 01 May 2018 20:21:22 GMT socket.io-client:socket calling ack 4 with [null,"system.adapter.yahka.0.alive"]
Caught 2018-05-01 20:21:22.252 error by controller[14]: Tue, 01 May 2018 20:21:22 GMT engine.io-client:socket socket receive: type "message", data "34[null,"system.adapter.yahka.0.alive"]"
Caught 2018-05-01 20:21:22.252 error by controller[14]: Tue, 01 May 2018 20:21:22 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.251 error by controller[13]: Tue, 01 May 2018 20:21:22 GMT socket.io-client:manager writing packet {"type":2,"data":["pushLog","system.adapter.admin.0",{"message":"yahka.0 cleaned everything up...","severity":
Caught 2018-05-01 20:21:22.251 error by controller[13]: Tue, 01 May 2018 20:21:22 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.251 error by controller[13]: Tue, 01 May 2018 20:21:22 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yah
Caught 2018-05-01 20:21:22.251 error by controller[13]: Tue, 01 May 2018 20:21:22 GMT socket.io-client:socket emitting packet with ack id 4
Caught 2018-05-01 20:21:22.251 error by controller[12]: Tue, 01 May 2018 20:21:18 GMT engine.io-client:socket flushing 7 packets in socket
Caught 2018-05-01 20:21:22.251 error by controller[11]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.y
Caught 2018-05-01 20:21:22.250 error by controller[10]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.ya
Caught 2018-05-01 20:21:22.250 error by controller[9]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":32,"ack":true,"from":"system.adapter.yahka.
Caught 2018-05-01 20:21:22.250 error by controller[9]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":13.72,"ack":true,"from":"system.adapte
Caught 2018-05-01 20:21:22.250 error by controller[9]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":29.98,"ack":true,"from":"system.adapt
Caught 2018-05-01 20:21:22.250 error by controller[8]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":42.78,"ack":true,"from":"system.adapter.yah
Caught 2018-05-01 20:21:22.250 error by controller[8]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"syst
Caught 2018-05-01 20:21:22.249 error by controller[8]: Tue, 01 May 2018 20:21:18 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.249 error by controller[7]: Tue, 01 May 2018 20:21:18 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.a
Caught 2018-05-01 20:21:22.248 error by controller[6]: Tue, 01 May 2018 20:21:12 GMT engine.io-client:socket socket receive: type "pong", data "undefined"
Caught 2018-05-01 20:21:22.248 error by controller[5]: Tue, 01 May 2018 20:21:12 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.248 error by controller[5]: Tue, 01 May 2018 20:21:12 GMT engine.io-client:socket writing ping packet - expecting pong within 60000ms
Caught 2018-05-01 20:21:22.246 error by controller[4]: Tue, 01 May 2018 20:21:12 GMT engine.io-client:socket socket receive: type "pong", data "undefined"
Caught 2018-05-01 20:21:22.246 error by controller[3]: Tue, 01 May 2018 20:21:12 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.245 error by controller[3]: Tue, 01 May 2018 20:21:12 GMT engine.io-client:socket writing ping packet - expecting pong within 60000ms
Caught 2018-05-01 20:21:22.245 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT engine.io-client:socket flushing 7 packets in socket
Caught 2018-05-01 20:21:22.245 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.ya
Caught 2018-05-01 20:21:22.244 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":1,"ack":true,"from":"system.adapter.yah
Caught 2018-05-01 20:21:22.244 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":17,"ack":true,"from":"system.adapter.yahka.
Caught 2018-05-01 20:21:22.244 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":13.61,"ack":true,"from":"system.adapte
Caught 2018-05-01 20:21:22.243 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":28.98,"ack":true,"from":"system.adapt
Caught 2018-05-01 20:21:22.243 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":42.78,"ack":true,"from":"system.adapter.yah
Caught 2018-05-01 20:21:22.243 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"syst
Caught 2018-05-01 20:21:22.242 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT engine.io-client:socket flushing 1 packets in socket
Caught 2018-05-01 20:21:22.242 error by controller[2]: Tue, 01 May 2018 20:21:03 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.a
Caught 2018-05-01 20:21:22.241 error by controller[1]: Tue, 01 May 2018 20:20:54 GMT socket.io-client:socket emitting event ["message","hm-rpc.0.MEQ0048205.2.ACTUAL_TEMPERATURE","hm-rpc.0.MEQ0048205.2.ACTUAL_TEMPERATURE",{"val":20.9,"ac
Caught 2018-05-01 20:21:22.240 error by controller[1]: Tue, 01 May 2018 20:20:54 GMT engine.io-client:socket socket receive: type "message", data "2["message","hm-rpc.0.MEQ0048205.2.ACTUAL_TEMPERATURE","hm-rpc.0.MEQ0048205.2.ACTUAL_TEMP
yahka.0 2018-05-01 20:21:22.192 info terminating

Vielen Dank schonmal für eure Hilfe!

[t4x]

Hi zusammen,

irgendwie lief die Installation von iobroker und yahka nicht rund. Nach einer aktuellen Neuinstallation auf iobroker 3.3.5 läuft es jetzt sauber.

Gruß,

t4x