UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[stoffel67]

so hab die Änderungen gemacht…
Adapter Instanz gestoppt und neu gestartet…

Leider kein Erfolg

im iPhone taucht nichts auf...

Müßte YAHKA.0 nicht schon bevor man den PIN am iPhone eingibt, auftauchen?

[peer6969]

du hast da keine gültige mac adresse eingegeben.

versuchs zB mit der mal: 6b:8a:58:72:df:2a

[Matze1708]

Stimmt!

Änder die nochmal…. ggf. Gurgel dir mal eine... da gibts so macadressen tools.

Gesendet von iPhone mit Tapatalk

[stoffel67]

Ja das mit der mac Adresse hab ich direkt nach dem screenshot gemerkt, und die letzte 5 weg genommen…

ging dann aber auch nicht...

gibt es da mehr DEBUG Möglichkeiten?

[stoffel67]

auch mit der 6b:8a:58:72:df:2a kein Erfolg…

ich hatte heute mal die LOG Meldung: ( kommt jetzt aber nicht mehr)
` > Caught 2018-05-31 16:26:12.073 error by controller[15]: Thu, 31 May 2018 16:26:11 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.073 error by controller[14]: Thu, 31 May 2018 16:26:11 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-31 16:26:12.072 error by controller[13]: Thu, 31 May 2018 16:26:11 GMT socket.io-client:socket emitting packet with ack id 5

Caught 2018-05-31 16:26:12.072 error by controller[12]: Thu, 31 May 2018 16:26:11 GMT socket.io-client:socket calling ack 3 with [null,"system.adapter.yahka.0.alive"]

Caught 2018-05-31 16:26:12.072 error by controller[11]: Thu, 31 May 2018 16:26:11 GMT engine.io-client:socket socket receive: type "message", data "33[null,"system.adapter.yahka.0.alive"]"

Caught 2018-05-31 16:26:12.071 error by controller[10]: Thu, 31 May 2018 16:26:11 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.071 error by controller[10]: Thu, 31 May 2018 16:26:11 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-31 16:26:12.070 error by controller[10]: Thu, 31 May 2018 16:26:11 GMT socket.io-client:socket emitting packet with ack id 4

Caught 2018-05-31 16:26:12.070 error by controller[10]: Thu, 31 May 2018 16:26:11 GMT socket.io-client:socket emitting event ["message","system.adapter.*","system.adapter.yahka.0",{"_id":"system.adapter.yahka.0","type":"instance","commo

Caught 2018-05-31 16:26:12.069 error by controller[10]: Thu, 31 May 2018 16:26:11 GMT engine.io-client:socket socket receive: type "message", data "2["message","system.adapter.*","system.adapter.yahka.0",{"_id":"system.adapter.yahka.0",

Caught 2018-05-31 16:26:12.069 error by controller[9]: Thu, 31 May 2018 16:26:11 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.068 error by controller[9]: Thu, 31 May 2018 16:26:11 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-31 16:26:12.068 error by controller[9]: Thu, 31 May 2018 16:26:11 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.068 error by controller[9]: Thu, 31 May 2018 16:26:11 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahk

Caught 2018-05-31 16:26:12.067 error by controller[9]: Thu, 31 May 2018 16:26:11 GMT socket.io-client:socket emitting packet with ack id 3

Caught 2018-05-31 16:26:12.067 error by controller[8]: Thu, 31 May 2018 16:25:58 GMT engine.io-client:socket flushing 7 packets in socket

Caught 2018-05-31 16:26:12.067 error by controller[7]: Thu, 31 May 2018 16:25:58 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-31 16:26:12.066 error by controller[7]: Thu, 31 May 2018 16:25:58 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yah

Caught 2018-05-31 16:26:12.066 error by controller[7]: Thu, 31 May 2018 16:25:58 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":379,"ack":true,"from":"system.adapter.yahka

Caught 2018-05-31 16:26:12.066 error by controller[7]: Thu, 31 May 2018 16:25:58 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":12.83,"ack":true,"from":"system.adapte

Caught 2018-05-31 16:26:12.066 error by controller[7]: Thu, 31 May 2018 16:25:58 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":14.98,"ack":true,"from":"system.adapt

Caught 2018-05-31 16:26:12.065 error by controller[7]: Thu, 31 May 2018 16:25:58 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":33.5,"ack":true,"from":"system.adapter.yahk

Caught 2018-05-31 16:26:12.065 error by controller[7]: Thu, 31 May 2018 16:25:58 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-31 16:26:12.065 error by controller[7]: Thu, 31 May 2018 16:25:58 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.064 error by controller[7]: Thu, 31 May 2018 16:25:58 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-31 16:26:12.064 error by controller[6]: Thu, 31 May 2018 16:25:57 GMT engine.io-client:socket socket receive: type "pong", data "undefined"

Caught 2018-05-31 16:26:12.063 error by controller[5]: Thu, 31 May 2018 16:25:57 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.063 error by controller[5]: Thu, 31 May 2018 16:25:57 GMT engine.io-client:socket writing ping packet - expecting pong within 60000ms

Caught 2018-05-31 16:26:12.063 error by controller[4]: Thu, 31 May 2018 16:25:57 GMT engine.io-client:socket socket receive: type "pong", data "undefined"

Caught 2018-05-31 16:26:12.063 error by controller[3]: Thu, 31 May 2018 16:25:57 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.062 error by controller[3]: Thu, 31 May 2018 16:25:57 GMT engine.io-client:socket writing ping packet - expecting pong within 60000ms

Caught 2018-05-31 16:26:12.062 error by controller[2]: Thu, 31 May 2018 16:25:43 GMT engine.io-client:socket flushing 7 packets in socket

Caught 2018-05-31 16:26:12.062 error by controller[2]: Thu, 31 May 2018 16:25:43 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-31 16:26:12.061 error by controller[2]: Thu, 31 May 2018 16:25:43 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yah

Caught 2018-05-31 16:26:12.061 error by controller[2]: Thu, 31 May 2018 16:25:43 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":364,"ack":true,"from":"system.adapter.yahka

Caught 2018-05-31 16:26:12.061 error by controller[2]: Thu, 31 May 2018 16:25:43 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":12.71,"ack":true,"from":"system.adapte

Caught 2018-05-31 16:26:12.060 error by controller[2]: Thu, 31 May 2018 16:25:43 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":14.98,"ack":true,"from":"system.adapt

Caught 2018-05-31 16:26:12.060 error by controller[2]: Thu, 31 May 2018 16:25:43 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":33.45,"ack":true,"from":"system.adapter.yah

Caught 2018-05-31 16:26:12.059 error by controller[2]: Thu, 31 May 2018 16:25:43 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-31 16:26:12.059 error by controller[1]: Thu, 31 May 2018 16:25:43 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-05-31 16:26:12.057 error by controller[1]: Thu, 31 May 2018 16:25:43 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/quote]

kann es daran liegen? `

[Matze1708]

Noch ne Idee, noch ne Idee….

Hast du diese Deamons manuell aufm Pi installiert?

Gesendet von iPhone mit Tapatalk

[stoffel67]

Ich hab den Adapter über Adapter hinzufügen, dann aus der Liste ganz unten Yahka ausgewählt

Inst lief problemlos durch…

Welche Deamons meinst du?

Ich habe irgendwie das Gefühl, dass da noch was auf der ioBroker Seite(raspi) fehlt<emoji seq="1f914"></emoji>

[mabas]

Ich habe jetzt bestimmt 6-8h an Yahka rumgebastelt. Und endlich läuft es. Meine Erfahrung mag ich teilen und für Suchende auffindbar machen:

Vorgeschichte:

Die iOS homekit App verlor die Verbindung zu iobroker nach ca. 2h und konnte nur wiederhergestellt werden, indem der Benutzername im Yahka Adapter geändert wurde. Das hielt dann wieder 2h. Daher habe ich den Adapter deinstalliert und den neusten aus dem Repository installiert. Leider hat sich dadurch mein Problem verschlimmert.

Mein Fehlerszenario:

Yahka startet gemäß aller Logs problemlos. Adapter ist grün. Logs zeigen nur Infos, keine Error/Warning. Dennoch ist iobroker nicht in der iOS homekit App zu sehen.

Lösung:

Eher Zufallstreffer. Ich habe immer den alten Namen (Yahka Adapter Einstellungen) weiterverwendet: iobroker.yahka.0. Das habe ich geändert in "homeserver".

Lief sofort. Und läuft auch dauerhaft (nun schon > 24h).

[mabas]

@stoeffel67: siehe https://github.com/jensweigele/ioBroker … leshooting

Der Avahi daemon.

[stoffel67]

Hab ich beachtet, und der daemon läuft…

@mabas: welchen Namen hast du wo geändert, kannst du einen screenshot machen?

Heißt dein ioBroker Rechner "Homeserver" (Hostname?)

[Blackeye]

Hi,

wieso gibt es denn 2 Möglichkeiten Kameras einzubinden? Einmal oben der Direktbutton und dann über den Services?

Bei mir hakt das Bild etwas und daher schaue ich nach einer alternativen Methode….

Gruß

Lars

[eumats]

@Blackeye:

Hi,

wieso gibt es denn 2 Möglichkeiten Kameras einzubinden? Einmal oben der Direktbutton und dann über den Services?

Bei mir hakt das Bild etwas und daher schaue ich nach einer alternativen Methode….

Gruß

Lars `

Es muss eines eigene Bridge für die Kamera eingerichtet werden ("Einmal oben"). Danach fügt man dann die eigentliche Kamera mit "dann über den Services" hinzu.

Wo läuft das Ganze denn bei Dir? auf einem Pi3?

[eumats]

@stoffel67:

so hab die Änderungen gemacht…Bildschirmfoto 2018-05-31 um 17.43.52.png

Adapter Instanz gestoppt und neu gestartet...

Leider kein Erfolg

im iPhone taucht nichts auf...

Müßte YAHKA.0 nicht schon bevor man den PIN am iPhone eingibt, auftauchen? `

Vielleicht ist das :yahka.0 zu kompliziert. Versuch mal folgendes (als Bsp.)

Name: zuHause

Hersteller: leer lassen

Modell: leer lassen

Serial: zuHause

Benutzername: c1:4e:a3:a1:55:2e

Pincode: 297-58-734

[Blackeye]

Hi,

danke, aber wieso kann ich dann bei der Bridge (Button oben) dann schon den Stream eintragen? Ich habe dann im Moment meine CAM über die Bridge am Laufen?

Und ja läuft auf einem PI3 für den PI3 + ist das Netzteil noch unterwegs

Gruß

Lars

@eumats:

@Blackeye:

Hi,

wieso gibt es denn 2 Möglichkeiten Kameras einzubinden? Einmal oben der Direktbutton und dann über den Services?

Bei mir hakt das Bild etwas und daher schaue ich nach einer alternativen Methode….

Gruß

Lars `

Es muss eines eigene Bridge für die Kamera eingerichtet werden ("Einmal oben"). Danach fügt man dann die eigentliche Kamera mit "dann über den Services" hinzu.

Wo läuft das Ganze denn bei Dir? auf einem Pi3? `

[stoffel67]

YEPP….

das scheint's gewesen zu sein...

hab den Namen geändert und die MAC-adresse des Raspis genommen( leider beides geändert, daher kann ich nicht sagen was es genau war..)

Jetzt seh' ich die Bridge im iPhone und auch mein Gatte mit den zwei Services...

Vielen Dank für eure Hilfe...

Ich hab' bestimmt noch weitere Fragen...

[Blackeye]

Hi,

es müsste der Name sein, hatte heute das gleiche Problem MAC Adresse hatte keinen Einfluss und mit Namen tatata…. klappt es wieder

@stoffel67:

YEPP….

das scheint's gewesen zu sein...

hab den Namen geändert und die MAC-adresse des Raspis genommen( leider beides geändert, daher kann ich nicht sagen was es genau war..)

Jetzt seh' ich die Bridge im iPhone und auch mein Gatte mit den zwei Services...

Vielen Dank für eure Hilfe...

Ich hab' bestimmt noch weitere Fragen... `

[eumats]

Auf einem PI ist „normal“ das es ruckeln. Der Raspi ist dafür zu schwach.

[stoffel67]

Hallo,

jetzt lief der Adapter doch problemlos…

heute wollte ich ein weiteres Gerät konfigurieren, aber nach dem Speichern und Schließen läuft der Adpater nicht mehr an...

er startet immer wieder neu und folgendes steht im log:
` > host.raspberrypi 2018-06-04 06:59:11.156 info instance system.adapter.yahka.0 started with pid 2778

host.raspberrypi 2018-06-04 06:58:41.135 info Restart adapter system.adapter.yahka.0 because enabled

host.raspberrypi 2018-06-04 06:58:41.132 error instance system.adapter.yahka.0 terminated with code 0 (OK)

Caught 2018-06-04 06:58:41.132 error by controller[95]: Mon, 04 Jun 2018 06:58:41 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-06-04 06:58:41.131 error by controller[95]: Mon, 04 Jun 2018 06:58:41 GMT socket.io-client:socket emitting packet with ack id 4

Caught 2018-06-04 06:58:41.131 error by controller[95]: Mon, 04 Jun 2018 06:58:41 GMT socket.io-client:socket calling ack 2 with [null,"system.adapter.yahka.0.alive"]

Caught 2018-06-04 06:58:41.131 error by controller[95]: Mon, 04 Jun 2018 06:58:41 GMT engine.io-client:socket socket receive: type "message", data "32[null,"system.adapter.yahka.0.alive"]"

Caught 2018-06-04 06:58:41.130 error by controller[95]: Mon, 04 Jun 2018 06:58:41 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-06-04 06:58:41.130 error by controller[95]: Mon, 04 Jun 2018 06:58:41 GMT socket.io-client:manager writing packet {"type":2,"data":["getStates",["system.adapter.admin.0.logging"]],"options":{"compress":true},"id":3,"nsp":"/"

Caught 2018-06-04 06:58:41.129 error by controller[95]: Mon, 04 Jun 2018 06:58:41 GMT socket.io-client:socket emitting packet with ack id 3

Caught 2018-06-04 06:58:41.129 error by controller[95]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket calling ack 1 with [null,["system.adapter.admin.0.logging"]]

Caught 2018-06-04 06:58:41.129 error by controller[95]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket receive: type "message", data "31[null,["system.adapter.admin.0.logging"]]"

Caught 2018-06-04 06:58:41.128 error by controller[94]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket flushing 3 packets in socket

Caught 2018-06-04 06:58:41.128 error by controller[93]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket flushing 10 packets in socket

Caught 2018-06-04 06:58:41.128 error by controller[92]: Mon, 04 Jun 2018 06:58:40 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-06-04 06:58:41.127 error by controller[91]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket emitting packet with ack id 2

Caught 2018-06-04 06:58:41.127 error by controller[90]: at TIOBrokerAdapter.createHomeKitBridges (/opt/iobroker/node_modules/iobroker.yahka/yahka.ioBroker-adapter.js:58:27)

Caught 2018-06-04 06:58:41.126 error by controller[90]: at new THomeKitBridge (/opt/iobroker/node_modules/iobroker.yahka/yahka.homekit-bridge.js:14:14)

Caught 2018-06-04 06:58:41.126 error by controller[90]: at THomeKitBridge.init (/opt/iobroker/node_modules/iobroker.yahka/yahka.homekit-bridge.js:24:38)

Caught 2018-06-04 06:58:41.126 error by controller[90]: at THomeKitBridge.createDevice (/opt/iobroker/node_modules/iobroker.yahka/yahka.homekit-bridge.js:74:18)

Caught 2018-06-04 06:58:41.126 error by controller[90]: at THomeKitBridge.initService (/opt/iobroker/node_modules/iobroker.yahka/yahka.homekit-bridge.js:93:18)

Caught 2018-06-04 06:58:41.125 error by controller[90]: at THomeKitBridge.initCharacteristic (/opt/iobroker/node_modules/iobroker.yahka/yahka.homekit-bridge.js:112:57)

Caught 2018-06-04 06:58:41.125 error by controller[90]: at TIOBrokerAdapter.CreateBinding (/opt/iobroker/node_modules/iobroker.yahka/yahka.ioBroker-adapter.js:138:69)

Caught 2018-06-04 06:58:41.125 error by controller[90]: at Object.createConversionFunction (/opt/iobroker/node_modules/iobroker.yahka/yahka.function-factory.js:557:53)

Caught 2018-06-04 06:58:41.124 error by controller[90]: at Object.scaleInt (/opt/iobroker/node_modules/iobroker.yahka/yahka.function-factory.js:418:31)

Caught 2018-06-04 06:58:41.124 error by controller[90]: at Object.parse (native)

Caught 2018-06-04 06:58:41.124 error by controller[90]: SyntaxError: Unexpected token j in JSON at position 0

Caught 2018-06-04 06:58:41.123 error by controller[89]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

Caught 2018-06-04 06:58:41.123 error by controller[89]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香

Caught 2018-06-04 06:58:41.123 error by controller[89]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket emitting packet with ack id 2

Caught 2018-06-04 06:58:41.122 error by controller[88]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

Caught 2018-06-04 06:58:41.122 error by controller[88]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-06-04 06:58:41.122 error by controller[87]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香

Caught 2018-06-04 06:58:41.121 error by controller[86]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket emitting packet with ack id 1

Caught 2018-06-04 06:58:41.121 error by controller[85]: Mon, 04 Jun 2018 06:58:40 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-06-04 06:58:41.121 error by controller[84]: Mon, 04 Jun 2018 06:58:40 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-06-04 06:58:41.120 error by controller[83]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":4,"ack":true,"from":"system.adapter.yahka.

Caught 2018-06-04 06:58:41.120 error by controller[82]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":11.69,"ack":true,"from":"system.adapt

Caught 2018-06-04 06:58:41.119 error by controller[81]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":18.98,"ack":true,"from":"system.adap

Caught 2018-06-04 06:58:41.119 error by controller[80]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":35.6,"ack":true,"from":"system.adapter.yah

Caught 2018-06-04 06:58:41.119 error by controller[79]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"sys

Caught 2018-06-04 06:58:41.118 error by controller[79]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.

Caught 2018-06-04 06:58:41.118 error by controller[79]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","*.logging",null],"options":{"compress":true},"nsp":"/"}

Caught 2018-06-04 06:58:41.118 error by controller[78]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-06-04 06:58:41.117 error by controller[77]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["getKeys","*.logging"],"options":{"compress":true},"id":1,"nsp":"/"}

Caught 2018-06-04 06:58:41.117 error by controller[76]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket emitting packet with ack id 1

Caught 2018-06-04 06:58:41.116 error by controller[75]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket calling ack 0 with [null,{"_id":"system.adapter.yahka.0","type":"instance","common":{"name":"yahka","version":"0.7.1","news":{

Caught 2018-06-04 06:58:41.115 error by controller[74]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket receive: type "message", data "30[null,{"_id":"system.adapter.yahka.0","type":"instance","common":{"name":"yahka","vers

Caught 2018-06-04 06:58:41.115 error by controller[73]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-06-04 06:58:41.115 error by controller[72]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["getObject","system.adapter.yahka.0",null],"options":{"compress":true},"id":0,"nsp":"/"}

Caught 2018-06-04 06:58:41.114 error by controller[71]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket emitting packet with ack id 0

Caught 2018-06-04 06:58:41.114 error by controller[70]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket calling ack 0 with [null,{"val":false,"ack":true,"ts":1528095486775,"q":0,"from":"system.host.raspberrypi","lc":1528095486697}

Caught 2018-06-04 06:58:41.113 error by controller[69]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket receive: type "message", data "30[null,{"val":false,"ack":true,"ts":1528095486775,"q":0,"from":"system.host.raspberrypi

Caught 2018-06-04 06:58:41.113 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket flushing 1 packets in socket

Caught 2018-06-04 06:58:41.113 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling ignoring poll - transport state "paused"

Caught 2018-06-04 06:58:41.112 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket clearing existing transport polling

Caught 2018-06-04 06:58:41.112 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket setting transport websocket

Caught 2018-06-04 06:58:41.112 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket changing transport and sending upgrade packet

Caught 2018-06-04 06:58:41.111 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling paused

Caught 2018-06-04 06:58:41.111 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling pre-pause polling complete

Caught 2018-06-04 06:58:41.111 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager writing packet {"type":2,"data":["getState","system.adapter.yahka.0.alive"],"options":{"compress":true},"id":0,"nsp":"/"}

Caught 2018-06-04 06:58:41.110 error by controller[68]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket emitting packet with ack id 0

Caught 2018-06-04 06:58:41.110 error by controller[67]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket receive: type "message", data "0"

Caught 2018-06-04 06:58:41.110 error by controller[66]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling polling got data 2:40

Caught 2018-06-04 06:58:41.109 error by controller[65]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling we are currently polling - waiting to pause

Caught 2018-06-04 06:58:41.109 error by controller[64]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket pausing current transport "polling"

Caught 2018-06-04 06:58:41.109 error by controller[63]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket probe transport "websocket" pong

Caught 2018-06-04 06:58:41.108 error by controller[62]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket probe transport "websocket" opened

Caught 2018-06-04 06:58:41.108 error by controller[61]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr data null

Caught 2018-06-04 06:58:41.107 error by controller[60]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9000/socket.io/?EIO=3& … IGsCRKAAAz

Caught 2018-06-04 06:58:41.107 error by controller[59]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr poll

Caught 2018-06-04 06:58:41.107 error by controller[58]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling polling

Caught 2018-06-04 06:58:41.106 error by controller[57]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket creating transport "websocket"

Caught 2018-06-04 06:58:41.106 error by controller[56]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket probing transport "websocket"

Caught 2018-06-04 06:58:41.106 error by controller[55]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket starting upgrade probes

Caught 2018-06-04 06:58:41.106 error by controller[54]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket transport is open - connecting

Caught 2018-06-04 06:58:41.105 error by controller[53]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager cleanup

Caught 2018-06-04 06:58:41.105 error by controller[52]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager open

Caught 2018-06-04 06:58:41.105 error by controller[51]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket open

Caught 2018-06-04 06:58:41.104 error by controller[50]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket receive: type "open", data "{"sid":"gGFmCf6sKoIGsCRKAAAz","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":6

Caught 2018-06-04 06:58:41.104 error by controller[49]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling polling got data 97:0{"sid":"gGFmCf6sKoIGsCRKAAAz","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}

Caught 2018-06-04 06:58:41.103 error by controller[48]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling ignoring poll - transport state "paused"

Caught 2018-06-04 06:58:41.103 error by controller[47]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket clearing existing transport polling

Caught 2018-06-04 06:58:41.103 error by controller[46]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket setting transport websocket

Caught 2018-06-04 06:58:41.102 error by controller[45]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket changing transport and sending upgrade packet

Caught 2018-06-04 06:58:41.102 error by controller[44]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling paused

Caught 2018-06-04 06:58:41.102 error by controller[43]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling pre-pause polling complete

Caught 2018-06-04 06:58:41.101 error by controller[42]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager readyState opening

Caught 2018-06-04 06:58:41.101 error by controller[41]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager connect attempt will timeout after 20000

Caught 2018-06-04 06:58:41.101 error by controller[40]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket setting transport polling

Caught 2018-06-04 06:58:41.100 error by controller[39]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr data null

Caught 2018-06-04 06:58:41.100 error by controller[38]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9000/socket.io/?EIO=3& … bpRR&b64=1

Caught 2018-06-04 06:58:41.100 error by controller[37]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr poll

Caught 2018-06-04 06:58:41.099 error by controller[36]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling polling

Caught 2018-06-04 06:58:41.099 error by controller[35]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket creating transport "polling"

Caught 2018-06-04 06:58:41.099 error by controller[34]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager opening http://127.0.0.1:9000

Caught 2018-06-04 06:58:41.098 error by controller[33]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager readyState closed

Caught 2018-06-04 06:58:41.098 error by controller[32]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client new io instance for http://127.0.0.1:9000

Caught 2018-06-04 06:58:41.097 error by controller[31]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:url parse http://127.0.0.1:9000

Caught 2018-06-04 06:58:41.097 error by controller[30]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket receive: type "message", data "0"

Caught 2018-06-04 06:58:41.097 error by controller[29]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling polling got data 2:40

Caught 2018-06-04 06:58:41.096 error by controller[28]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling we are currently polling - waiting to pause

Caught 2018-06-04 06:58:41.096 error by controller[27]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket pausing current transport "polling"

Caught 2018-06-04 06:58:41.096 error by controller[26]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket probe transport "websocket" pong

Caught 2018-06-04 06:58:41.095 error by controller[25]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket probe transport "websocket" opened

Caught 2018-06-04 06:58:41.095 error by controller[24]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr data null

Caught 2018-06-04 06:58:41.095 error by controller[23]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9001/socket.io/?EIO=3& … pbd6U-AAAy

Caught 2018-06-04 06:58:41.094 error by controller[22]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling-xhr xhr poll

Caught 2018-06-04 06:58:41.094 error by controller[21]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:polling polling

Caught 2018-06-04 06:58:41.094 error by controller[20]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket creating transport "websocket"

Caught 2018-06-04 06:58:41.093 error by controller[19]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket probing transport "websocket"

Caught 2018-06-04 06:58:41.093 error by controller[18]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket starting upgrade probes

Caught 2018-06-04 06:58:41.093 error by controller[17]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:socket transport is open - connecting

Caught 2018-06-04 06:58:41.092 error by controller[16]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager cleanup

Caught 2018-06-04 06:58:41.092 error by controller[15]: Mon, 04 Jun 2018 06:58:40 GMT socket.io-client:manager open

Caught 2018-06-04 06:58:41.092 error by controller[14]: Mon, 04 Jun 2018 06:58:40 GMT engine.io-client:socket socket open `

was könnte denn jetzt wider falsch sein…?

[Blackeye]

Hi,

gibt es einen Service YAHKA der einen Taster darstellt? Im Prinzip gibt es Taster ja, habe aber nichts gefunden.

Danke

[stoffel67]

Kurze Rückmeldung,

Adapter läuft wieder nachdem ich das Gerät gelöscht und "identisch" wieder angelegt habe :shock:

seltsam ist das schon…