Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Yet another HomeKit adapter

    NEWS

    • JAHRESRÜCKBLICK 2024 ✨

    • NEWS von ioBroker im Blog!

    • Cloud/Vis-Offline-Weihnachtsangebot 2024

    Yet another HomeKit adapter

    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      roqstailor last edited by

      alsoooo habe es zum laufen bekommen 😄 😄

      bin wie folgt vorgegangen

      cd /opt/iobroker

      npm cache clean

      sudo npm install –unsafe-perm mdns

      und dann

      reboot

      und fertig 😄

      1 Reply Last reply Reply Quote 0
      • N
        nico_93 last edited by

        Hi Leute,

        ich wollte iobroker mit yahka mal ausprobieren und habe iobroker auf meinem Debian-Server installiert. Scheinbar läuft auch alles ohne Probleme, aber die Bridge wird nicht mit dem iPhone gefunden.

        Hatte das schon mal jemand? Die dependencies habe ich alle installiert… Gibt es vielleicht ein ausführlicheres log? Das dort unten hilt ja nicht wirklich.

        ! yahka.0 2018-03-17 08:59:11.980 info adding Rollladen with UUID: 35cd37a2-987f-4686-bd8e-fd210422bd68
        ! yahka.0 2018-03-17 08:59:11.972 info adapter ready, checking config
        ! yahka.0 2018-03-17 08:59:11.956 info starting. Version 0.7.1 in /opt/app/iobroker/node_modules/iobroker.yahka, node: v6.13.1

        1 Reply Last reply Reply Quote 0
        • eumats
          eumats last edited by

          Bitte mal yahka unter Instanzen auf Debug stellen und Log hier posten (bitte Spoiler und Code-Atha nutzen)…

          1 Reply Last reply Reply Quote 0
          • A
            algermi last edited by

            Servus zusammen,

            ja es von Euch jemand erfolgreich hinbekommen die MiLight LED Lichtleisten vollständig zu steuern.

            Also auch die RBG Farm Steuerung, Sättigung usw.

            Ich kann meine über HomeKit nur ein/ausschalten und Dimmern.

            Danke für's Feedback.

            1 Reply Last reply Reply Quote 0
            • R
              rom.wagner80 last edited by

              @algermi:

              Servus zusammen,

              ja es von Euch jemand erfolgreich hinbekommen die MiLight LED Lichtleisten vollständig zu steuern.

              Also auch die RBG Farm Steuerung, Sättigung usw.

              Ich kann meine über HomeKit nur ein/ausschalten und Dimmern.

              Danke für's Feedback. `

              Das würde mich auch mal interessieren. Die Mi-Lights benötigen einen Farbcode im Format #FFFFFF und der YAHKA gibt bei der Einstellung hue Werte bis 65535 raus. wie kann ich beides auf einen Nenner bringen ?

              1 Reply Last reply Reply Quote 0
              • V
                Vossi80 last edited by

                @eumats:

                @algermi:

                @eumats

                was hast Du für einen neigungssensor verbaut und würdest Du mir Dein Script zukommen lassen? `

                Ich mache die Lösung mal allen zugänglich…

                Beschreibung der korrekten Steuerung und Anzeige eines Garagentors per yahka in Homekit in folgender Konfiguration:

                • Schaltung des Garagenmotors durch einen "Tast-Aktor" (Fibaro 212, potentialfreie Ausgänge) der einen kurzen Impuls (1sec) zum Starten des Motors gibt. Die Richtung kann ich dabei nicht beeinflussen. D.b. z.B. Tor offen, Tast-Aktor ansteuern -> Tor geht zu, Tast-Aktor erneut an steuern -> Tor stoppt, Tast-Aktor erneut an steuern -> Tor fährt wieder zu, ….

                • Das Tor kann zzgl. per Funk und per Taster (beide gehen direkt an den Garagenmotor und sind nicht mit dem Tast-Aktor verbunden)

                • Nutzung eines Neigungssensor zum Abfragen der Anfangs- und Endlage

                Garagensensor:

                • true = Tor offen

                • false = Tor geschlossen

                Skript zum Setzen von offen und geschlossen in Homekit, falls das Tor per Taster oder Fernbedienung (und nicht aus Homekit) geöffnet oder geschlossen wurde.

                "javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK" und "javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK" sind manuell angelegte Datenpunkte die später auch in yahka eingetragen werden.

                ! var timeout; ! on({id: 'zwave.0.NODE2.SENSOR_BINARY.Sensor_1', change: "ne"}, function (obj) { var value = obj.state.val; var oldValue = obj.oldState.val; timeout = setTimeout(function () { if (getState("zwave.0.NODE2.SENSOR_BINARY.Sensor_1").val == false) { // Definiere Tor für HK als geschlossen setState("javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK"/*LageGaragentor_HK*/, 1, true); setState("javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK"/*schalteGaragentor_HK*/, 1, true); } else { // Definiere Tor für HK als offen setState("javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK"/*LageGaragentor_HK*/, 0, true); setState("javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK"/*schalteGaragentor_HK*/, 0, true); } }, 1000); }); !

                Skript zum Konvertieren des Schaltwertes aus Homekit (yahka: TargetState) um umgekehrt.

                ! on({id: 'zwave.0.NODE4.SWITCH_BINARY.Switch_1', change: "ne"}, function (obj) { var value = obj.state.val; var oldValue = obj.oldState.val; if (getState("javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK").val == 1) { // Tor geschlossen if (getState("zwave.0.NODE4.SWITCH_BINARY.Switch_1").val == true) { // Öffne das Tor setState("javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK"/*schalteGaragentor_HK*/, 0, true); } } else if (getState("javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK").val == 0) { // Tor offen if (getState("zwave.0.NODE4.SWITCH_BINARY.Switch_1").val == true) { // Schließe das Tor setState("javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK"/*schalteGaragentor_HK*/, 1, true); // Tor wird geschlossen } } }); on({id: 'javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK', change: "ne"}, function (obj) { var value = obj.state.val; var oldValue = obj.oldState.val; if (getState("javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK").val == 1) { // Tor geschlossen if (getState("javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK").val == 0) { // Öffne das Tor setState("zwave.0.NODE4.SWITCH_BINARY.Switch_1"/*Switch*/, true); } } else if (getState("javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK").val == 0) { // Tor offen if (getState("javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK").val == 1) { // Schließe das Tor setState("zwave.0.NODE4.SWITCH_BINARY.Switch_1"/*Switch*/, true); } } }); !

                In yahka ein device mit "Garage door opener" mit gleichanmigem Service definieren und folgendes eintragen:

                CurrentDoorState: ioBroker.State javascript.0.scriptEnabled.common.LageGaragentor_HK.LageGaragentor_HK

                TargetDoorState: ioBroker.State. javascript.0.scriptEnabled.common.schalteGaragentor_HK.schalteGaragentor_HK `

                Hallo, versuche grade auch mein Garagentor einzubinden doch leider komme ich nicht weiter. Habe mich versucht an die Anleitung zu halten aber ich glaube beim Script mache ich ein Fehler. Ich löse den Torantrieb über ein Homematic Batterie Schaltaktor aus der den kurzen Impuls gibt. Als Überwachung ob Tor auf oder zu benutze ich ein optischen Homematic Tür/Fensterkontakt. Habe mir dann die 2 Javascripte erstellt und das passende Gerät mit den Einstellungen wie beschrieben eingestellt. Jetzt muss ich ja sicher in den Skripten meine Geräte ID's einfügen aber irgendwie klappt das nicht. Kann mir da mal einer helfen?

                Wandtaster Homematic zum auslösen des Aktors: hm-rpc.0.LTK0044294.1.PRESS_SHORT

                Optischer Kontakt: hm-rpc.0.NEQ0067397.1.STATE

                Wäre nett wenn mir da einer auf die Sprünge helfen könnte

                Lg

                1 Reply Last reply Reply Quote 0
                • N
                  nico_93 last edited by

                  @eumats:

                  Bitte mal yahka unter Instanzen auf Debug stellen und Log hier posten (bitte Spoiler und Code-Atha nutzen)… `

                  Hab es hinbekommen. Die Homebridge Erkennung funktioniert über multicast. Das muss man natürlich im Netzwerk erlauben :lol:

                  1 Reply Last reply Reply Quote 0
                  • H
                    Hohenbostler last edited by

                    Hallo zusmmen,

                    ich bekomme den Adapter leider nicht installiert.

                    kann mir jemand genau sagen wo das Problem ist ?

                    $ ./iobroker add yahka
NPM version: 3.10.10
npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call)
In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>^

compilation terminated.
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error 
gyp
 ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)

gyp ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v6.13.0

gyp ERR! node-gyp -v v3.4.0gyp ERR! not ok 

npm
 WARN
 optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm 
WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/iobroker.js2fs/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm 
ERR! Linux 4.9.59-v7+npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.yahka" "--production" "--save" "--prefix" "/opt/iobroker"
npm ERR! node v6.13.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! mdns@2.3.4 install: `node-gyp rebuild`
npm ERR! Exit status 1

npm ERR! npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild

npm ERR!
 You can get information on how to open an issue for this project with:npm ERR!     npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:npm ERR!
     /npm-debug.lognpm ERR! code 1

host.raspberrypi install adapter yahka
NPM version: 3.10.10npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call)

In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>^
compilation terminated.

make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error 
gyp
 ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp 
ERR! stack     at emitTwo (events.js:106:13)gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)

gyp
 ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

gyp ERR! cwd /opt/iobroker/node_modules/mdnsgyp ERR! node -v v6.13.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/iobroker.js2fs/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! Linux 4.9.59-v7+
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.yahka" "--production" "--save" "--prefix" "/opt/iobroker"npm ERR! node v6.13.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! mdns@2.3.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR!
 You can get information on how to open an issue for this project with:npm ERR!     npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!
     /npm-debug.lognpm ERR! code 1

host.raspberrypi install adapter yahka
NPM version: 3.10.10
npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call)
In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>^
compilation terminated.

make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error gyp 
ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp
 ERR! stack     at emitTwo (events.js:106:13)gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)

gyp ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v6.13.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 

npm
 WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/iobroker.js2fs/node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm 
ERR! Linux 4.9.59-v7+npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.yahka" "--production" "--save" "--prefix" "/opt/iobroker"

npm ERR! node v6.13.0npm ERR! npm  v3.10.10

npm ERR! code ELIFECYCLE
npm ERR!
 mdns@2.3.4 install: `node-gyp rebuild`npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR!
 You can get information on how to open an issue for this project with:npm ERR!     npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm
 ERR! Please include the following file with any support request:npm ERR!
     /npm-debug.lognpm ERR! code 1

host.raspberrypi install adapter yahka
ERROR: host.raspberrypi Cannot install yahka
ERROR: process exited with code 13</dns_sd.h></dns_sd.h></dns_sd.h>
                    1 Reply Last reply Reply Quote 0
                    • R
                      rh1212 last edited by

                      @Hohenbostler:

                      Hallo zusmmen,

                      ich bekomme den Adapter leider nicht installiert.

                      kann mir jemand genau sagen wo das Problem ist ?

                      $ ./iobroker add yahka
NPM version: 3.10.10
npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call)
In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>^

compilation terminated.
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error 
gyp
 ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)

gyp ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v6.13.0

gyp ERR! node-gyp -v v3.4.0gyp ERR! not ok 

npm
 WARN
 optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm 
WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/iobroker.js2fs/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm 
ERR! Linux 4.9.59-v7+npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.yahka" "--production" "--save" "--prefix" "/opt/iobroker"
npm ERR! node v6.13.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! mdns@2.3.4 install: `node-gyp rebuild`
npm ERR! Exit status 1

npm ERR! npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild

npm ERR!
 You can get information on how to open an issue for this project with:npm ERR!     npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:npm ERR!
     /npm-debug.lognpm ERR! code 1

host.raspberrypi install adapter yahka
NPM version: 3.10.10npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call)

In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>^
compilation terminated.

make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error 
gyp
 ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp 
ERR! stack     at emitTwo (events.js:106:13)gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)

gyp
 ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

gyp ERR! cwd /opt/iobroker/node_modules/mdnsgyp ERR! node -v v6.13.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/iobroker.js2fs/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! Linux 4.9.59-v7+
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.yahka" "--production" "--save" "--prefix" "/opt/iobroker"npm ERR! node v6.13.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! mdns@2.3.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR!
 You can get information on how to open an issue for this project with:npm ERR!     npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!
     /npm-debug.lognpm ERR! code 1

host.raspberrypi install adapter yahka
NPM version: 3.10.10
npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call)
In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>^
compilation terminated.

make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error gyp 
ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp
 ERR! stack     at emitTwo (events.js:106:13)gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)

gyp ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v6.13.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 

npm
 WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/iobroker.js2fs/node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm 
ERR! Linux 4.9.59-v7+npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.yahka" "--production" "--save" "--prefix" "/opt/iobroker"

npm ERR! node v6.13.0npm ERR! npm  v3.10.10

npm ERR! code ELIFECYCLE
npm ERR!
 mdns@2.3.4 install: `node-gyp rebuild`npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR!
 You can get information on how to open an issue for this project with:npm ERR!     npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm
 ERR! Please include the following file with any support request:npm ERR!
     /npm-debug.lognpm ERR! code 1

host.raspberrypi install adapter yahka
ERROR: host.raspberrypi Cannot install yahka
ERROR: process exited with code 13</dns_sd.h></dns_sd.h></dns_sd.h> 
```` `

                      Hast du ]das gemacht?

                      "Wichtig vor der Installation müssen einige Pakete installiert werden: sudo apt-get install libavahi-compat-libdnssd-dev"

                      Lese Seite 30 da hatte ich auch Probleme hab alles was die anderen vorgeschlagen gemacht. Glaube apt-get update hat mein Problem gelöst

                      1 Reply Last reply Reply Quote 0
                      • H
                        Hohenbostler last edited by

                        Sorry auch alles andere ohne erfolg . hier nochmal ein versuch

                        ! ````
                        Using username "root".
                        root@192.168.178.55's password:
                        Access denied
                        root@192.168.178.55's password:
                        Linux raspberrypi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l
                        ! The programs included with the Debian GNU/Linux system are free software;
                        the exact distribution terms for each program are described in the
                        individual files in /usr/share/doc/*/copyright.
                        ! Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                        permitted by applicable law.
                        Last login: Sun Mar 25 19:19:28 2018 from 192.168.178.31
                        root@raspberrypi:~# cd /opt/iobroker
                        root@raspberrypi:/opt/iobroker# npm cache clean
                        root@raspberrypi:/opt/iobroker# sudo npm install --unsafe-perm mdns
                        ! > mdns@2.3.4 install /opt/iobroker/node_modules/mdns
                        node-gyp rebuild
                        ! make: Verzeichnis „/opt/iobroker/node_modules/mdns/build“ wird betreten
                        CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
                        In file included from ../src/dns_sd.cpp:1:0:
                        ../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefun den
                        #include <dns_sd.h>^
                        compilation terminated.
                        dns_sd_bindings.target.mk:149: die Regel für Ziel „Release/obj.target/dns_sd_bin dings/src/dns_sd.o“ scheiterte
                        make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
                        make: Verzeichnis „/opt/iobroker/node_modules/mdns/build“ wird verlassen
                        gyp ERR! build error
                        gyp ERR! stack Error: make failed with exit code: 2
                        gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_module s/node-gyp/lib/build.js:276:23)
                        gyp ERR! stack at emitTwo (events.js:106:13)
                        gyp ERR! stack at ChildProcess.emit (events.js:191:7)
                        gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces s.js:219:12)
                        gyp ERR! System Linux 4.9.59-v7+
                        gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy p/bin/node-gyp.js" "rebuild"
                        gyp ERR! cwd /opt/iobroker/node_modules/mdns
                        gyp ERR! node -v v6.13.1
                        gyp ERR! node-gyp -v v3.4.0
                        gyp ERR! not ok
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/ch okidar/node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@ 1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"} )
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/io broker.js2fs/node_modules/chokidar/node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@ 1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"} )
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modu les/noble/node_modules/xpc-connection):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-conne ction@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch": "arm"})
                        npm ERR! Linux 4.9.59-v7+
                        npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "--unsafe-perm" "mdns"
                        npm ERR! node v6.13.1
                        npm ERR! npm v3.10.10
                        npm ERR! code ELIFECYCLE
                        ! npm ERR! mdns@2.3.4 install: node-gyp rebuild
                        npm ERR! Exit status 1
                        npm ERR!
                        npm ERR! Failed at the mdns@2.3.4 install script 'node-gyp rebuild'.
                        npm ERR! Make sure you have the latest version of node.js and npm installed.
                        npm ERR! If you do, this is most likely a problem with the mdns package,
                        npm ERR! not with npm itself.
                        npm ERR! Tell the author that this fails on your system:
                        npm ERR! node-gyp rebuild
                        npm ERR! You can get information on how to open an issue for this project with:
                        npm ERR! npm bugs mdns
                        npm ERR! Or if that isn't available, you can get their info via:
                        npm ERR! npm owner ls mdns
                        npm ERR! There is likely additional logging output above.
                        ! npm ERR! Please include the following file with any support request:
                        npm ERR! /opt/iobroker/npm-debug.log
                        root@raspberrypi:/opt/iobroker# ^C
                        root@raspberrypi:/opt/iobroker#</dns_sd.h>

                        1 Reply Last reply Reply Quote 0
                        • W
                          Wunk last edited by

                          Hallo Leute!

                          Bei mir läuft der Yahka-Adapter zeitweise ganz gut, aber immer wieder mal sind einige Geräte plötzlich "weg". Ich hatte schon dass gar kein Gerät (außer yahka.0 selbst) mehr im Homekit angezeigt wird, in letzter Zeit fehlte meistens ein gutes Drittel.

                          Starte ich den Adapter neu, tauchen die Geräte in Homekit zwar wieder auf, aber haben natürlich ihre Raumzuordnungen verloren und müssen neu sortiert werden. 😞

                          Kennt irgendjemand das Problem und/oder hat ne Idee was man tun könnte?

                          Ich habe das Forum schon durchstöbert und Beiträge mit vertraut klingenden Problembeschreibungen gefunden, aber leider nichts in Richtung Lösung. Mit einem "das hat außer euch keiner" ist mir leider nicht geholfen :lol:

                          ! @thoduh:
                          ! > In dem Link geht es aber um homebridge, ich habe aber Probleme mit yahka.

                          Oder hab ich was falsch verstanden?

                          PS: Habe macOS 10.13

                          Das Logfile von iobroker:

                          `Caught	2017-10-05 21:50:22.474	error	by controller[26]: :"CurrentRelativeHumidity","enabled":true,"inOutFunction":"ioBroker.State","inOutParameters":"hm-rpc.0.LEQ1213764.2.ACTUAL_HUMIDITY"}]}]},{"manufacturer":"Homematic","model":"HM-Se
Caught	2017-10-05 21:50:22.474	error	by controller[25]: roker.State","inOutParameters":"hm-rpc.0.LEQ1214207.2.ACTUAL_HUMIDITY"}]}]},{"manufacturer":"Homematic","model":"HM-TC-IT-WM-W-EU","name":"Temperatur Wohnzimmer","serial":"KEQ01144
Caught	2017-10-05 21:50:22.474	error	by controller[24]: Thu, 05 Oct 2017 19:50:22 GMT engine.io-client:socket socket receive: type "message", data "2["message","system.adapter.*","system.adapter.yahka.0",{"_id":"system.adapter.yahka.0",
Caught	2017-10-05 21:50:22.474	error	by controller[23]: Thu, 05 Oct 2017 19:50:18 GMT socket.io-client:socket emitting event ["message","hm-rpc.0.KEQ1074517.1.STATE","hm-rpc.0.KEQ1074517.1.STATE",{"val":false,"ack":true,"ts":15072330189
Caught	2017-10-05 21:50:22.474	error	by controller[22]: Thu, 05 Oct 2017 19:50:18 GMT socket.io-parser decoded 2["message","hm-rpc.0.KEQ1074517.1.STATE","hm-rpc.0.KEQ1074517.1.STATE",{"val":false,"ack":true,"ts":1507233018942,"q":0,"fro
Caught	2017-10-05 21:50:22.474	error	by controller[21]: Thu, 05 Oct 2017 19:50:18 GMT engine.io-client:socket socket receive: type "message", data "2["message","hm-rpc.0.KEQ1074517.1.STATE","hm-rpc.0.KEQ1074517.1.STATE",{"val":false,"ac
Caught	2017-10-05 21:50:22.474	error	by controller[20]: Thu, 05 Oct 2017 19:50:17 GMT engine.io-client:socket flushing 7 packets in socket
Caught	2017-10-05 21:50:22.474	error	by controller[19]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],
Caught	2017-10-05 21:50:22.474	error	by controller[19]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"
Caught	2017-10-05 21:50:22.474	error	by controller[19]: Thu, 05 Oct 2017 19:50:17 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	2017-10-05 21:50:22.474	error	by controller[18]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"
Caught	2017-10-05 21:50:22.474	error	by controller[18]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"}
Caught	2017-10-05 21:50:22.474	error	by controller[17]: Thu, 05 Oct 2017 19:50:17 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	2017-10-05 21:50:22.474	error	by controller[17]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":301,"ack":true,"from":"system.adapter.yahka.0"},null],"op
Caught	2017-10-05 21:50:22.474	error	by controller[17]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":301,"ack":true,"from":"system.adapter.yahka.0"},n
Caught	2017-10-05 21:50:22.473	error	by controller[17]: Thu, 05 Oct 2017 19:50:17 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":301,"ack":true,"from":"system.adapter.yahk[/code]`

Zwischendurch funktioniert yahka dann mal wieder, allerdings sind alle Geräte (72 Stück) dem Standardraum zugeordnet. Sehr ärgerlich, da nicht zum ersten mal...

Lässt sich Homebridge von: [https://github.com/nfarina/homebridge](https://github.com/nfarina/homebridge) und [https://github.com/thkl/homebridge-homematic](https://github.com/thkl/homebridge-homematic) nicht in ioBroker einbinden?

Diese laufen wesentlich stabiler, es gibt regelmäßige Updates und auch Dimmer funktionieren Problemlos.

``` `
                          1 Reply Last reply Reply Quote 0
                          • P
                            peer6969 last edited by

                            @rom.wagner80:

                            @eumats:

                            Hast du ihn nur ganz kurz (also 3%) fahren lassen? Lass ihn mal bitte länger fahre. Natürlich manuell und dann das Log posten. `
                            Werd ich morgen mal machen… weiß nicht mehr ob’s 3% waren... könnte aber sein.

                            Schönen Abend noch `

                            Hat sich das Problem mit den KNX Rolladenaktoren gelöst? Plane etwas ähnliches umzusetzen und würde gern vorher sichergehen, dass es klappt 😉

                            1 Reply Last reply Reply Quote 0
                            • R
                              rom.wagner80 last edited by

                              @peer6969:

                              @rom.wagner80:

                              @eumats:

                              Hast du ihn nur ganz kurz (also 3%) fahren lassen? Lass ihn mal bitte länger fahre. Natürlich manuell und dann das Log posten. `
                              Werd ich morgen mal machen… weiß nicht mehr ob’s 3% waren... könnte aber sein.

                              Schönen Abend noch `

                              Hat sich das Problem mit den KNX Rolladenaktoren gelöst? Plane etwas ähnliches umzusetzen und würde gern vorher sichergehen, dass es klappt 😉 `

                              Nein, leider noch nicht. Hab das Script erstmal wieder deaktiviert. Werde, wenn die Zeit es zulässt nochmal daran herum probieren. Solange muss ich erstmal auf die Positionierung über Homekit verzichten und nutze die X1 Software von Gira.

                              Schönen Gruß

                              Gesendet von iPhone mit Tapatalk

                              1 Reply Last reply Reply Quote 0
                              • W
                                worfinator last edited by

                                Funktionieren bei euch eigentlich die Automationen von iOS? Bei mir haut das irgendwie nicht hin. Normal sollte immer eine Lampe angehen, wenn ich Heim komme. Tut sie aber leider nicht…

                                1 Reply Last reply Reply Quote 0
                                • P
                                  peer6969 last edited by

                                  Ja. Die Automations funktionieren einwandfrei. Sowohl zeit- als auch ereignis- oder standortbasiert. Hast du einen Apple TV oder ein iPad als Hub für HomeKit eingerichtet das dauerhaft am Strom hängt? Sonst geht es nicht.

                                  1 Reply Last reply Reply Quote 0
                                  • R
                                    rom.wagner80 last edited by

                                    @worfinator:

                                    Funktionieren bei euch eigentlich die Automationen von iOS? Bei mir haut das irgendwie nicht hin. Normal sollte immer eine Lampe angehen, wenn ich Heim komme. Tut sie aber leider nicht… `

                                    Also die standortbasierten regeln funktionieren nicht wirklich zuverlässig. Bei meinem device schon aber das von meiner Frau wird nicht verarbeitet…

                                    Gesendet von iPhone mit Tapatalk

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      peer6969 last edited by

                                      In den iCloud Settings unter „Share my location“ ist „this device“ ausgewählt und beim Location Sharing ist es auch nicht vielleicht überall deaktiviert? Bisher war es noch bei jedem im Bekanntenkreis so, dass sie die standortdienste an irgendeiner Stelle abgedreht haben und dann geschimpft haben, dass es nicht funktioniert…

                                      1 Reply Last reply Reply Quote 0
                                      • W
                                        worfinator last edited by

                                        Ich schaue mir das grad an. Also "Dieses Gerät" ist bei meinem iPhone auf jeden Fall ausgewählt für die Freigabe des Standorts. So einfach wird es nicht werden. Aber wenn es bei dir geht peer6969 stimmt es mich optimistisch, dass ich es auch ans Laufen bekomme.

                                        Vor Yahka hatte ich Homebridge verwendet. Damit ging es auf jeden Fall. Ich schau auf jeden Fall nochmal rum. Stand jetzt wird die Lampe nicht eingeschaltet, wenn ich "nach Hause" komme.

                                        1 Reply Last reply Reply Quote 0
                                        • U
                                          useful_idiot last edited by

                                          Hi,

                                          ich hatte den yahka eine ganze Zeit problemlos am laufen, da ist auch nur ein Gerät drin. Seit gestern zeigte yahka als Status disconnected an und gab auch keine Lebenszeichen - auchkann ich yahka nicht mehr über das Webinterface starten, es kommt im Log nur der Code 1

                                          host.raspberrypi	2018-05-22 22:07:38.700	info	Restart adapter system.adapter.yahka.0 because enabled
host.raspberrypi	2018-05-22 22:07:38.699	error	instance system.adapter.yahka.0 terminated with code 1 ()
host.raspberrypi	2018-05-22 22:07:37.892	info	instance system.adapter.yahka.0 started with pid 4533
host.raspberrypi	2018-05-22 22:07:07.873	info	Restart adapter system.adapter.yahka.0 because enabled
host.raspberrypi	2018-05-22 22:07:07.872	error	instance system.adapter.yahka.0 terminated with code 1 ()
host.raspberrypi	2018-05-22 22:07:07.066	info	instance system.adapter.yahka.0 started with pid 4521
host.raspberrypi	2018-05-22 22:06:37.047	info	Restart adapter system.adapter.yahka.0 because enabled
host.raspberrypi	2018-05-22 22:06:37.046	error	instance system.adapter.yahka.0 terminated with code 1 ()
host.raspberrypi	2018-05-22 22:06:36.228	info	instance system.adapter.yahka.0 started with pid 4253
host.raspberrypi	2018-05-22 22:06:06.216	info	Restart adapter system.adapter.yahka.0 because enabled

                                          Ich verstehe nicht, wo ich noch weiter ansetzen kann, alle Voraussetzungen sind noch da, ein detaillierteres Log zu yahka finde ich nicht… die Ausgabe wiederholt sich endlos. Ich habe den Adapter schon einige Male neu installiert, auch /opt/iobroker/node_modules/iobroker.yahka gelöscht, die "yahka_meta" in den Objekten gelöscht, "sudo npm cache clean" bzw. "verify" ausgeführt und neu heruntergeladen... immer wieder lande ich bei diesem Status. Node Version ist 8.9.4

                                          Wenn ich dagegen in /opt/iobroker/node_modules/iobroker.yahka wechsle und "node main.js --force --logs" ausführe, dann startet es und wird auch im Webinterface als Verbunden mit Lebenszeichen angezeigt, aber ich kann ja nicht immer die Konsole offen lassen... Da die Ausgabe dann relativ umfangreich ist, packe ich es mal in einen Spoiler

                                          ! ````
                                          508 history | grep npm
                                          root@raspberrypi:/home/pi# cd /opt/iobroker/node_modules/iobroker.yahka
                                          root@raspberrypi:/opt/iobroker/node_modules/iobroker.yahka# node -v
                                          v8.9.4
                                          root@raspberrypi:/opt/iobroker/node_modules/iobroker.yahka# node main.js --force --logs
                                          socket.io-client:url parse http://127.0.0.1:9001 +0ms
                                          socket.io-client new io instance for http://127.0.0.1:9001 +8ms
                                          socket.io-client:manager readyState closed +4ms
                                          socket.io-client:manager opening http://127.0.0.1:9001 +0ms
                                          engine.io-client:socket creating transport "polling" +0ms
                                          engine.io-client:polling polling +4ms
                                          engine.io-client:polling-xhr xhr poll +1ms
                                          engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=ME9VrcL&b64=1 +6ms
                                          engine.io-client:polling-xhr xhr data null +2ms
                                          engine.io-client:socket setting transport polling +39ms
                                          socket.io-client:manager connect attempt will timeout after 20000 +59ms
                                          socket.io-client:manager readyState opening +10ms
                                          engine.io-client:polling polling got data 97:0{"sid":"Gw5j89wIrizAfDAbAAAQ","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000} +123ms
                                          engine.io-client:socket socket receive: type "open", data "{"sid":"Gw5j89wIrizAfDAbAAAQ","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}" +4ms
                                          engine.io-client:socket socket open +2ms
                                          socket.io-client:manager open +118ms
                                          socket.io-client:manager cleanup +1ms
                                          socket.io-client:socket transport is open - connecting +2ms
                                          engine.io-client:socket starting upgrade probes +5ms
                                          engine.io-client:socket probing transport "websocket" +1ms
                                          engine.io-client:socket creating transport "websocket" +1ms
                                          engine.io-client:polling polling +18ms
                                          engine.io-client:polling-xhr xhr poll +0ms
                                          engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=ME9VrfT&b64=1&sid=Gw5j89wIrizAfDAbAAAQ +1ms
                                          engine.io-client:polling-xhr xhr data null +1ms
                                          engine.io-client:socket probe transport "websocket" opened +38ms
                                          engine.io-client:polling polling got data 2:40 +16ms
                                          engine.io-client:socket socket receive: type "message", data "0" +1ms
                                          socket.io-client:url parse http://127.0.0.1:9000 +94ms
                                          socket.io-client new io instance for http://127.0.0.1:9000 +1ms
                                          socket.io-client:manager readyState closed +1ms
                                          socket.io-client:manager opening http://127.0.0.1:9000 +0ms
                                          engine.io-client:socket creating transport "polling" +19ms
                                          engine.io-client:polling polling +1ms
                                          engine.io-client:polling-xhr xhr poll +0ms
                                          engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9000/socket.io/?EIO=3&transport=polling&t=ME9Vrgg&b64=1 +1ms
                                          engine.io-client:polling-xhr xhr data null +0ms
                                          engine.io-client:socket setting transport polling +2ms
                                          socket.io-client:manager connect attempt will timeout after 20000 +5ms
                                          socket.io-client:manager readyState opening +1ms
                                          engine.io-client:polling polling +3ms
                                          engine.io-client:polling-xhr xhr poll +0ms
                                          engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=ME9Vrgm&b64=1&sid=Gw5j89wIrizAfDAbAAAQ +1ms
                                          engine.io-client:polling-xhr xhr data null +0ms
                                          engine.io-client:socket probe transport "websocket" pong +11ms
                                          engine.io-client:socket pausing current transport "polling" +1ms
                                          engine.io-client:polling we are currently polling - waiting to pause +1ms
                                          engine.io-client:polling polling got data 97:0{"sid":"1d25fAFFFb9XerGLAAAR","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000} +8ms
                                          engine.io-client:socket socket receive: type "open", data "{"sid":"1d25fAFFFb9XerGLAAAR","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}" +2ms
                                          engine.io-client:socket socket open +0ms
                                          socket.io-client:manager open +27ms
                                          socket.io-client:manager cleanup +0ms
                                          socket.io-client:socket transport is open - connecting +1ms
                                          engine.io-client:socket starting upgrade probes +2ms
                                          engine.io-client:socket probing transport "websocket" +1ms
                                          engine.io-client:socket creating transport "websocket" +0ms
                                          engine.io-client:polling polling +5ms
                                          engine.io-client:polling-xhr xhr poll +0ms
                                          engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9000/socket.io/?EIO=3&transport=polling&t=ME9VrhG&b64=1&sid=1d25fAFFFb9XerGLAAAR +1ms
                                          engine.io-client:polling-xhr xhr data null +0ms
                                          engine.io-client:socket probe transport "websocket" opened +10ms
                                          engine.io-client:polling polling got data 2:40 +6ms
                                          engine.io-client:socket socket receive: type "message", data "0" +1ms
                                          socket.io-client:socket emitting packet with ack id 0 +29ms
                                          socket.io-client:manager writing packet {"type":2,"data":["getState","system.adapter.yahka.0.alive"],"options":{"compress":true},"id":0,"nsp":"/"} +1ms
                                          engine.io-client:socket flushing 1 packets in socket +8ms
                                          engine.io-client:polling-xhr xhr open POST: http://127.0.0.1:9000/socket.io/?EIO=3&transport=polling&t=ME9Vrhk&b64=1&sid=1d25fAFFFb9XerGLAAAR +4ms
                                          engine.io-client:polling-xhr xhr data 46:420["getState","system.adapter.yahka.0.alive"] +1ms
                                          engine.io-client:polling polling +4ms
                                          engine.io-client:polling-xhr xhr poll +0ms
                                          engine.io-client:polling-xhr xhr open GET: http://127.0.0.1:9000/socket.io/?EIO=3&transport=polling&t=ME9Vrhp&b64=1&sid=1d25fAFFFb9XerGLAAAR +1ms
                                          engine.io-client:polling-xhr xhr data null +0ms
                                          engine.io-client:socket probe transport "websocket" pong +5ms
                                          engine.io-client:socket pausing current transport "polling" +1ms
                                          engine.io-client:polling we are currently polling - waiting to pause +0ms
                                          engine.io-client:polling we are currently writing - waiting to pause +0ms
                                          engine.io-client:polling polling got data 1:6 +4ms
                                          engine.io-client:socket socket receive: type "noop", data "undefined" +1ms
                                          engine.io-client:polling pre-pause polling complete +2ms
                                          engine.io-client:polling paused +0ms
                                          engine.io-client:socket changing transport and sending upgrade packet +1ms
                                          engine.io-client:socket setting transport websocket +1ms
                                          engine.io-client:socket clearing existing transport polling +0ms
                                          engine.io-client:polling ignoring poll - transport state "paused" +2ms
                                          engine.io-client:polling pre-pause writing complete +9ms
                                          engine.io-client:polling polling got data 111:430[null,{"val":false,"ack":true,"ts":1527020214245,"q":0,"from":"system.host.raspberrypi","lc":1527018357361}] +3ms
                                          engine.io-client:socket socket receive: type "message", data "30[null,{"val":false,"ack":true,"ts":1527020214245,"q":0,"from":"system.host.raspberrypi","lc":1527018357361}]" +1ms
                                          socket.io-client:socket calling ack 0 with [null,{"val":false,"ack":true,"ts":1527020214245,"q":0,"from":"system.host.raspberrypi","lc":1527018357361}] +44ms
                                          socket.io-client:socket emitting packet with ack id 0 +2ms
                                          socket.io-client:manager writing packet {"type":2,"data":["getObject","system.adapter.yahka.0",null],"options":{"compress":true},"id":0,"nsp":"/"} +1ms
                                          engine.io-client:socket flushing 1 packets in socket +5ms
                                          engine.io-client:polling pre-pause polling complete +2ms
                                          engine.io-client:polling paused +0ms
                                          engine.io-client:socket changing transport and sending upgrade packet +0ms
                                          engine.io-client:socket setting transport websocket +1ms
                                          engine.io-client:socket clearing existing transport polling +0ms
                                          engine.io-client:polling ignoring poll - transport state "paused" +1ms
                                          engine.io-client:socket socket receive: type "message", data "30[null,{"_id":"system.adapter.yahka.0","type":"instance","common":{"name":"yahka","version":"0.7.1","news":{"0.7.1":{"en":"Fixed the ID select dialog in Admin 2.0.9. restructured repo to allow install via git-url","de":"Der ID-Auswahldialog in Admin 2.0.9 wurde korrigiert. Repository umstrukturiert um Installation via git-url zu ermöglichen"},"0.7.0":{"en":"Fixed the ID select dialog in Admin3, added new services and fixed some other bugs","de"(GEKÜRZT) Homekit"},"platform":"Javascript/Node.js","mode":"daemon","icon":"yahka.png","enabled":true,"extIcon":"https://raw.githubusercontent.com/jensweigele/ioBroker.yahka/master/admin/yahka.png","keywords":["homekit","siri"],"readme":"https://github.com/jensweigele/ioBroker.yahka/blob/master/README.md","loglevel":"info","type":"iot-systems","materialize":true,"config":{"minWidth":800,"width ":1440,"minHeight":600,"height ":860},"authors":[{"name":"Jens Weigele","email":"iobroker.yahka@gmail.com"}],"installedVersion":"0.7.1","host":"raspberrypi"},"native":{"firstTimeInitialized":false,"bridge":{"devices":[{"configType":"customdevice","manufacturer":"RFTEC","model":"PointClick","name":"Bett","serial":"2525A25","enabled":true,"category":"5","services":[{"name":"Bett","subType":"Bett","type":"Lightbulb","characteristics":[{"name":"On","enabled":true,"inOutFunction":"ioBroker.State","inOutParameters":"broadlink2.0.States.Bett"}]}]}],"configType":"bridge","name":"ioBroker","manufacturer":"Raspberry","model":"ioBroker","serial":":yahka.0","username":"1A:43:23:52:41:42","pincode":"534-23-242","port":"0"},"cameras":[]},"from":"system.adapter.admin.0","ts":1527019225616,"acl":{"object":1636}}]" +31ms
                                          socket.io-client:socket calling ack 0 with [null,{"_id":"system.adapter.yahka.0","type":"instance","common":{"name":"yahka","version":"0.7.1","news":{"0.7.1":{"en":"Fixed the ID select dialog in Admin 2.0.9. restructured repo to allow install via git-url","de":"Der ID-Auswahldialog in Admin 2.0.9 wurde korrigiert. Repository umstrukturiert um Installation via git-url zu ermöglichen"},"0(GEKÜRZT)es":"otro adaptador para el Homekit","pl":"kolejny adapter Homekit"},"platform":"Javascript/Node.js","mode":"daemon","icon":"yahka.png","enabled":true,"extIcon":"https://raw.githubusercontent.com/jensweigele/ioBroker.yahka/master/admin/yahka.png","keywords":["homekit","siri"],"readme":"https://github.com/jensweigele/ioBroker.yahka/blob/master/README.md","loglevel":"info","type":"iot-systems","materialize":true,"config":{"minWidth":800,"width ":1440,"minHeight":600,"height ":860},"authors":[{"name":"Jens Weigele","email":"iobroker.yahka@gmail.com"}],"installedVersion":"0.7.1","host":"raspberrypi"},"native":{"firstTimeInitialized":false,"bridge":{"devices":[{"configType":"customdevice","manufacturer":"RFTEC","model":"PointClick","name":"Bett","serial":"2525A25","enabled":true,"category":"5","services":[{"name":"Bett","subType":"Bett","type":"Lightbulb","characteristics":[{"name":"On","enabled":true,"inOutFunction":"ioBroker.State","inOutParameters":"broadlink2.0.States.Bett"}]}]}],"configType":"bridge","name":"ioBroker","manufacturer":"Raspberry","model":"ioBroker","serial":":yahka.0","username":"1A:43:23:52:41:42","pincode":"534-23-242","port":"0"},"cameras":[]},"from":"system.adapter.admin.0","ts":1527019225616,"acl":{"object":1636}}] +37ms
                                          socket.io-client:socket emitting packet with ack id 1 +5ms
                                          socket.io-client:manager writing packet {"type":2,"data":["getKeys",".logging"],"options":{"compress":true},"id":1,"nsp":"/"} +0ms
                                          engine.io-client:socket flushing 1 packets in socket +8ms
                                          socket.io-client:manager writing packet {"type":2,"data":["subscribe","                                          .logging",null],"options":{"compress":true},"nsp":"/"} +4ms
                                          starting. Version 0.7.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v8.9.4
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +14ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":35.3,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":16.49,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":8.96,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +0ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":4,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +0ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +0ms
                                          adapter ready, checking config
                                          first time initialization
                                          system config:{"system":{"memoryLimitMB":0,"hostname":""},"multihostService":{"enabled":false,"secure":true},"network":{"IPv4":true,"IPv6":true,"bindAddress":null,"useSystemNpm":true},"objects":{"type":"file","typeComment":"Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].","host":"127.0.0.1","port":9001,"user":"","pass":"","noFileCache":false,"connectTimeout":2000},"states":{"type":"file","typeComment":"Possible values: 'file' - [port 9000], 'redis' - [port 6379].","host":"127.0.0.1","port":9000,"maxQueue":1000,"options":{"auth_pass":null,"retry_max_delay":15000}},"log":{"level":"info","maxDays":7,"noStdout":true,"transport":{"file1":{"type":"file","enabled":true,"filename":"log/iobroker","fileext":".log","maxsize":null,"maxFiles":null},"syslog1":{"type":"syslog","enabled":false,"host":"localhost","host_comment":"The host running syslogd, defaults to localhost.","port_comment":"The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).","protocol":"udp4","protocol_comment":"The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).","path_comment":"The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).","facility_comment":"Syslog facility to use (Default: local0).","localhost":"iobroker","localhost_comment":"Host to indicate that log messages are coming from (Default: localhost).","sysLogType_comment":"The type of the syslog protocol to use (Default: BSD).","app_name_comment":"The name of the application (Default: process.title).","eol_comment":"The end of line character to be added to the end of the message (Default: Message without modifications)."}}},"dataDirComment":"Always relative to iobroker.js-controller/","dataDir":"../../iobroker-data/","forceIfDisabled":true,"consoleOutput":true}
                                          socket.io-client:manager writing packet {"type":2,"data":["extendObject","system.adapter.yahka.0",{"native":{"firstTimeInitialized":true,"bridge":{"devices":[{"configType":"customdevice","manufacturer":"RFTEC","model":"PointClick","name":"Bett","serial":"2525A25","enabled":true,"category":"5","services":[{"name":"Bett","subType":"Bett","type":"Lightbulb","characteristics":[{"name":"On","enabled":true,"inOutFunction":"ioBroker.State","inOutParameters":"broadlink2.0.States.Bett"}]}]}],"configType":"bridge","name":":yahka.0","manufacturer":"Raspberry","model":"ioBroker","serial":":yahka.0","username":"b1:dc:1b:94:c1:12","pincode":"123-45-678","port":0,"ident":":yahka.0","verboseLogging":false},"cameras":[]},"from":"system.adapter.yahka.0","ts":1527020215149},null,null],"options":{"compress":true},"nsp":"/"} +23ms
                                          engine.io-client:socket flushing 1 packets in socket +45ms
                                          creating bridge
                                          adding Bett with UUID: 6ec733ba-7739-4b70-b449-2a75d3bda8d8
                                          socket.io-client:socket emitting packet with ack id 1 +38ms
                                          socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"yahka","systemConfig":true}],"options":{"compress":true},"id":1,"nsp":"/"} +0ms
                                          socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} +1ms
                                          added subscription for: [state]broadlink2.0.States.Bett
                                          socket.io-client:manager writing packet {"type":2,"data":["subscribe","yahka.0.checkLogging",null],"options":{"compress":true},"nsp":"/"} +54ms
                                          engine.io-client:socket flushing 10 packets in socket +106ms
                                          engine.io-client:socket flushing 2 packets in socket +9ms
                                          engine.io-client:socket socket receive: type "message", data "31[null,["system.adapter.admin.0.logging"]]" +18ms
                                          socket.io-client:socket calling ack 1 with [null,["system.adapter.admin.0.logging"]] +43ms
                                          socket.io-client:socket emitting packet with ack id 2 +3ms
                                          socket.io-client:manager writing packet {"type":2,"data":["getStates",["system.adapter.admin.0.logging"]],"options":{"compress":true},"id":2,"nsp":"/"} +1ms
                                          engine.io-client:socket flushing 1 packets in socket +8ms
                                          engine.io-client:socket socket receive: type "message", data "32[null,[{"val":true,"ack":true,"ts":1527018644708,"q":0,"from":"system.adapter.admin.0","lc":1527017803436}]]" +37ms
                                          socket.io-client:socket calling ack 2 with [null,[{"val":true,"ack":true,"ts":1527018644708,"q":0,"from":"system.adapter.admin.0","lc":1527017803436}]] +40ms
                                          socket.io-client:manager writing packet {"type":2,"data":["pushLog","system.adapter.admin.0",{"message":"yahka.0 starting. Version 0.7.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v8.9.4","severity":"info","from":"yahka.0","ts":1527020215306},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          engine.io-client:socket flushing 1 packets in socket +5ms
                                          socket.io-client:manager writing packet {"type":2,"data":["pushLog","system.adapter.admin.0",{"message":"yahka.0 adapter ready, checking config","severity":"info","from":"yahka.0","ts":1527020215309},null],"options":{"compress":true},"nsp":"/"} +4ms
                                          socket.io-client:manager writing packet {"type":2,"data":["pushLog","system.adapter.admin.0",{"message":"yahka.0 first time initialization","severity":"info","from":"yahka.0","ts":1527020215309},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["pushLog","system.adapter.admin.0",{"message":"yahka.0 adding Bett with UUID: 6ec733ba-7739-4b70-b449-2a75d3bda8d8","severity":"info","from":"yahka.0","ts":1527020215309},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          engine.io-client:socket flushing 3 packets in socket +7ms
                                          engine.io-client:socket socket receive: type "message", data "31[null,{"rows":[{"id":"system.adapter.admin.0","value":{"_id":"system.adapter.admin.0","type":"instance","common":{"name":"admin","title":"ioBroker Admin","version":"2.0.9","news":{"2.0.9":{"en":"fix sorting, when using adapters with more than one instance","de":"Sortierung für Adapter mit mehr als einer Instanz repariert"},"2.0.8":{"en":"fix quickEdit: number with boolean value","de":"behoben: quickEdit, (GEKÜRZT)pens a webserver for the ioBroker admin UI","de":"Stellt Webserver für 'ioBroker Admin UI' zur Verfügung","ru":"Запускает веб сервер с 'ioBroker admin UI' для удобной настройки через веб интерфейс"},"docs":{"en":"docs/en/admin.md","ru":"docs/ru/admin.md","de":["docs/de/admin.md","docs/de/admin/tab-adapters.md","docs/de/admin/tab-instances.md","docs/de/admin/tab-objects.md","docs/de/admin/tab-states.md","docs/de/admin/tab-groups.md","docs/de/admin/tab-users.md","docs/de/admin/tab-events.md","docs/de/admin/tab-hosts.md","docs/de/admin/tab-enums.md","docs/de/admin/tab-log.md","docs/de/admin/tab-system.md"]},"mode":"daemon","platform":"Javascript/Node.js","loglevel":"info","icon":"admin.png","messagebox":true,"enabled":true,"extIcon":"https://raw.githubusercontent.com/ioBroker/ioBroker.admin/master/admin/admin.png","keywords":["setup","config","update","upgrade","system","konfiguration","administration","einrichtung","wartung"],"readme":"https://github.com/ioBroker/ioBroker.admin/blob/master/README.md","authors":["bluefox bluefox@ccu.io","hobbyquaker hq@ccu.io"],"dependencies":[{"js-controller":">=0.12.0"}],"type":"general","license":"MIT","logTransporter":true,"stopBeforeUpdate":true,"wwwDontUpload":true,"welcomeScreenPro":{"link":"admin/index.html","name":"Admin","img":"admin/img/gear.png","color":"pink","order":5,"localLink":true},"localLink":"%protocol%://%ip%:%port%","installedVersion":"2.0.9","host":"raspberrypi"},"native":{"port":8081,"auth":false,"secure":false,"bind":"0.0.0.0","cache":false,"certPublic":"","certPrivate":"","certChained":"","ttl":3600,"defaultUser":"admin","tmpPath":"/tmp","tmpPathAllow":false,"leEnabled":false,"leUpdate":false,"leCheckPort":80},"from":"system.host.raspberrypi.cli","ts":1526732851507,"acl":{"object":1636}}},{"id":"system.adapter.discovery.0","value":{"_id":"system.adapter.discovery.0","type":"instance","common":{"name":"discovery","version":"1.1.0","news":{"1.1.0":{"en":"Support of admin3","de":"Unterstützung von admin3","ru":"Поддержка admin3","pt":"Suporte de admin3","nl":"Ondersteuning van admin3","fr":"Support de admin3","it":"Supporto di admin3","es":"Soporte de admin3"},"1.0.1":{"en":"Fix Epson Stylus PX830\nAdd Bose Soundtouch","de":"Epson Stylus PX830 KORRIGIERT\nBose Soundtouch hinzugefügt","ru":"Fix Epson Stylus PX830\nAdd Bose Soundtouch"},"1.0.0":{"en":"Add Epson Stylus PX830, Loxone\nAdd Homepilot","de":"Epson Stylus PX830, Loxone und Homepilot sind hinzugefügt","ru":"Добавлены Epson Stylus PX830, Loxone и Homepilot"},"0.4.5":{"en":"Fixes in mihome","de":"Fixes in mihome","ru":"Fixes in mihome"},"0.4.4":{"en":"Add lgtv","de":"LGTV hinzugefügt","ru":"Добавлен lgtv"},"0.4.2":{"en":"Add discovery methods selection","de":"Methodenauswahl hinzugefügt","ru":"Добавлен выбор методов поиска"},"0.4.0":{"en":"add SamsungTV, Lightify, Miele and yamaha\nadd new discovery method mDNS","de":"SamsungTV, Lightify, Miele und yamaha sind hinzugefügt\nNeues Discovery Methode mDNS hinzugefügt","ru":"Добавлены SamsungTV, Lightify, Miele and yamaha\nДобавлен новый метод обнаружения - mDNS"},"0.3.3":{"en":"Add Philips HUE","de":"Philips HUE hinzugefügt","ru":"Добавлен Philips HUE"},"0.3.2":{"en":"Add discovery of USB mysensors","de":"Erkennung für den USB mysensors hinzugefügt","ru":"Добавлено обнаружение USB mysensors"},"0.3.1":{"en":"Add discovery of Daikin Adapter","de":"Erkennung für den Daikin-Adapter hinzugefügt","ru":"Add discovery of Daikin Adapter"},"0.3.0":{"en":"Fixed serial discovery","de":"Serialsuche korrigiert","ru":"исправлен поиск на последовательных портах"},"0.2.3":{"en":"added more adapters","de":"Wietere Adapters hinzugefügt","ru":"Добавлены дополнительные драйвера"},"0.2.2":{"en":"Fix typo","de":"Fix typo","ru":"Исправлена синтаксическая ошибка"},"0.2.1":{"en":"initial commit","de":"initial commit","ru":"initial commit"}},"title":"Discovery devices","titleLang":{"en":"Discovery devices","de":"Gerätesuche","ru":"Драйвер поиска устройств","pt":"Dispositivos de descoberta","nl":"Ontdekkingsapparaten","fr":"Dispositifs de découverte","it":"Dispositivi di scoperta","es":"Dispositivos de descubrimiento","pl":"Urządzenia Discovery"},"desc":{"en":"This adapter tries to discover all known devices in your network and on your machine","de":"Dieser Adapter versucht, alle bekannten Geräte in Ihrem Netzwerk und auf Ihrem Computer zu finden","ru":"Этот адаптер пытается обнаружить все известные устройства в вашей сети и на вашем компьютере","pt":"Este adaptador tenta descobrir todos os dispositivos conhecidos da sua rede e da sua máquina","nl":"Deze adapter probeert alle bekende apparaten in uw netwerk en op uw computer te ontdekken","fr":"Cet adaptateur essaie de découvrir tous les périphériques connus sur votre réseau et sur votre machine","it":"Questo adattatore tenta di rilevare tutti i dispositivi noti nella rete e sulla macchina","es":"Este adaptador intenta descubrir todos los dispositivos conocidos en su red y en su máquina","pl":"Ten adapter próbuje wykryć wszystkie znane urządzenia w sieci i na twoim komputerze"},"authors":["bluefox dogafox@gmail.com"],"license":"MIT","platform":"Javascript/Node.js","mode":"daemon","enabled":true,"singletonHost":true,"materialize":true,"messagebox":true,"readme":"https://github.com/ioBroker/ioBroker.discovery/blob/master/README.md","dependencies":[{"js-controller":">=1.2.0"}],"loglevel":"info","icon":"discovery.png","keywords":["poll","discovery","ip"],"extIcon":"https://raw.githubusercontent.com/ioBroker/ioBroker.discovery/master/admin/discovery.png","type":"general","config":{"width":1224,"height":700},"installedVersion":"1.1.0","host":"raspberrypi"},"native":{"pingTimeout":1000,"pingBlock":20},"from":"system.host.raspberrypi.cli","ts":1526732894714,"acl":{"object":1636}}},{"id":"system.adapter.web.0","v

                                          GEKÜRZT, hier kommen 1000e Changelog Einträge...

                                          dattatore Homekit","es":"otro adaptador para el Homekit","pl":"kolejny adapter Homekit"},"platform":"Javascript/Node.js","mode":"daemon","icon":"yahka.png","enabled":true,"extIcon":"https://raw.githubusercontent.com/jensweigele/ioBroker.yahka/master/admin/yahka.png","keywords":["homekit","siri"],"readme":"https://github.com/jensweigele/ioBroker.yahka/blob/master/README.md","loglevel":"info","type":"iot-systems","materialize":true,"config":{"minWidth":800,"width ":1440,"minHeight":600,"height ":860},"authors":[{"name":"Jens Weigele","email":"iobroker.yahka@gmail.com"}],"installedVersion":"0.7.1","host":"raspberrypi"},"native":{"firstTimeInitialized":true,"bridge":{"devices":[{"configType":"customdevice","manufacturer":"RFTEC","model":"PointClick","name":"Bett","serial":"2525A25","enabled":true,"category":"5","services":[{"name":"Bett","subType":"Bett","type":"Lightbulb","characteristics":[{"name":"On","enabled":true,"inOutFunction":"ioBroker.State","inOutParameters":"broadlink2.0.States.Bett"}]}]}],"configType":"bridge","name":":yahka.0","manufacturer":"Raspberry","model":"ioBroker","serial":":yahka.0","username":"b1:dc:1b:94:c1:12","pincode":"123-45-678","port":0,"ident":":yahka.0","verboseLogging":false},"cameras":[]},"from":"system.adapter.yahka.0","ts":1527020215149,"acl":{"object":1636}}}]}] +68ms
                                          socket.io-client:manager writing packet {"type":2,"data":["subscribe","broadlink2.0.States.Bett",null],"options":{"compress":true},"nsp":"/"} +8ms
                                          engine.io-client:socket flushing 1 packets in socket +24ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +15s
                                          engine.io-client:socket flushing 1 packets in socket +15s
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +3ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":36.61,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":16.99,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.25,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +3ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":19,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          engine.io-client:socket flushing 7 packets in socket +15ms
                                          engine.io-client:socket writing ping packet - expecting pong within 60000ms +10s
                                          engine.io-client:socket flushing 1 packets in socket +1ms
                                          engine.io-client:socket socket receive: type "pong", data "undefined" +5ms
                                          engine.io-client:socket writing ping packet - expecting pong within 60000ms +107ms
                                          engine.io-client:socket flushing 1 packets in socket +1ms
                                          engine.io-client:socket socket receive: type "pong", data "undefined" +3ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +15s
                                          engine.io-client:socket flushing 1 packets in socket +5s
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +3ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":36.86,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":16.99,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.47,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":34,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          engine.io-client:socket flushing 7 packets in socket +12ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +15s
                                          engine.io-client:socket flushing 1 packets in socket +15s
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +3ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":37.12,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":16.99,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +2ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.63,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":49,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],"options":{"compress":true},"nsp":"/"} +1ms
                                          engine.io-client:socket flushing 7 packets in socket +11ms
                                          engine.io-client:socket writing ping packet - expecting pong within 60000ms +5s
                                          engine.io-client:socket flushing 1 packets in socket +0ms
                                          engine.io-client:socket socket receive: type "pong", data "undefined" +4ms
                                          engine.io-client:socket writing ping packet - expecting pong within 60000ms +108ms
                                          engine.io-client:socket flushing 1 pack/dogafox@gmail.com/hq@ccu.io/bluefox@ccu.io

                                          
Im WebIF versucht er offenbar immer noch weiter zu starten, der erfolgreiche Start per Konsole taucht dann aber auch auf.

                                          host.raspberrypi 2018-05-22 22:17:26.957 info Restart adapter system.adapter.yahka.0 because enabled
                                          host.raspberrypi 2018-05-22 22:17:26.957 error instance system.adapter.yahka.0 terminated with code 1 ()
                                          host.raspberrypi 2018-05-22 22:17:26.081 info instance system.adapter.yahka.0 started with pid 5014
                                          host.raspberrypi 2018-05-22 22:16:56.061 info Restart adapter system.adapter.yahka.0 because enabled
                                          host.raspberrypi 2018-05-22 22:16:56.060 error instance system.adapter.yahka.0 terminated with code 1 ()
                                          yahka.0 2018-05-22 22:16:55.174 info adding Bett with UUID: 6ec733ba-7739-4b70-b449-2a75d3bda8d8
                                          yahka.0 2018-05-22 22:16:55.147 info first time initialization
                                          yahka.0 2018-05-22 22:16:55.145 info adapter ready, checking config
                                          yahka.0 2018-05-22 22:16:55.115 info starting. Version 0.7.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v8.9.4
                                          host.raspberrypi 2018-05-22 22:16:55.192 info instance system.adapter.yahka.0 started with pid 4987
                                          host.raspberrypi 2018-05-22 22:16:55.177 info object change system.adapter.yahka.0
                                          host.raspberrypi 2018-05-22 22:16:54.249 info Restart adapter system.adapter.yahka.0 because enabled
                                          host.raspberrypi 2018-05-22 22:16:54.249 error instance system.adapter.yahka.0 terminated with code 1 ()
                                          host.raspberrypi 2018-05-22 22:16:53.379 info instance system.adapter.yahka.0 started with pid 4977
                                          host.raspberrypi 2018-05-22 22:16:23.368 info Restart adapter system.adapter.yahka.0 because enabled
                                          host.raspberrypi 2018-05-22 22:16:23.367 error instance system.adapter.yahka.0 terminated with code 1 ()
                                          host.raspberrypi 2018-05-22 22:16:22.549 info instance system.adapter.yahka.0 started with pid 4959
                                          host.raspberrypi 2018-05-22 22:15:52.531 info Restart adapter system.adapter.yahka.0 because enabled
                                          host.raspberrypi 2018-05-22 22:15:52.530 error instance system.adapter.yahka.0 terminated with code 1 ()
                                          host.raspberrypi 2018-05-22 22:15:51.677 info instance system.adapter.yahka.0 started with pid 4945
                                          host.raspberrypi 2018-05-22 22:15:21.657 info Restart adapter system.adapter.yahka.0 because enabled
                                          host.raspberrypi 2018-05-22 22:15:21.657 error instance system.adapter.yahka.0 terminated with code 1 ()

                                          
EDIT: Ich habe jetzt den Service mal herausgenommen und manuell ioBroker über die Konsole gestartet. yahka wurde mitgestartet, ich probiere morgen weiter und ergänze dann.
                                          1 Reply Last reply Reply Quote 0
                                          • eumats
                                            eumats last edited by

                                            Du könntest zzgl. das Debug-Level von yahka noch mal auf debug stellen. Dann werden ein paar mehr Infos ausgegeben…

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            1.3k
                                            Online

                                            30.9k
                                            Users

                                            77.6k
                                            Topics

                                            1.2m
                                            Posts

                                            201
                                            1673
                                            376901
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo