Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Yet another HomeKit adapter

NEWS

  • Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar
    BluefoxB
    Bluefox
    12
    2
    256

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.7k

Yet another HomeKit adapter

Yet another HomeKit adapter

Scheduled Pinned Locked Moved ioBroker Allgemein
1.8k Posts 206 Posters 832.4k Views 68 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    adrianthomas
    wrote on last edited by
    #807

    @Monox:

    Hi, ich gehe jetzt mal davon aus das du, dass du dein Homematic mit ioBroker verbunden hast und somit kannst du YAHKA auch direkt drauf Zugreifen lassen. `

    Eben nicht. Der HMIP Access Point kann nicht direkt in ioBroker eingebunden werden, nur die CCU2/CCU3.

    Oder?

    1 Reply Last reply
    0
    • StM47S Offline
      StM47S Offline
      StM47
      wrote on last edited by
      #808

      Hallo,

      ich würde gerne Yahaka und Apple HomeKit nutzen.

      Leider bekomme ich keine Verbindung vom iPhone zu ioBroker.

      Habe schon alle Foreneinträge zum Thema gelesen und nichts gefunden, was mir hilft.

      Ich habe ioBroker im Docker meiner Synology Diskstation laufen.

      Irgendwo habe ich gelesen, dass in der DiskStation Bonjour abgeschaltet werden muss.

      Habe ich getan und trotzdem läuft es nicht. Die DiskStation und der ioBroker Container wurden auch schon mehrfach neu gestartet.

      9039_bildschirmfoto_2018-11-16_um_20.38.59.png

      Yahka in der Version 0.7.1. in ioBroker installiert.

      9039_bildschirmfoto_2018-11-16_um_20.42.59_kopie.png

      im iPhone X mit iOS 12.1.1 wird Yahka auch gesehen

      9039_img_2681.jpg

      Nachdem ich den Code eingegeben haben, wird auch versucht zu verbinden, aber leider ohne Erfolg.

      9039_img_2682.jpg

      und dann bekomme ich die Fehlermeldung:

      9039_img_2683.jpg

      Auch mit dem iPod meiner Tochter, welcher noch auf iOS 11 läuft, habe ich das gleiche Problem.

      Ich weiß nicht mehr weiter und bitte um Hilfe!

      Hier mal eine Kopie der Fehlermeldungen:

      ! Caught 2018-11-16 20:22:11.735 error by controller[49]: 2018-11-16T19:22:11.712Z engine.io-client:socket flushing 1 packets in socket
      ! Caught 2018-11-16 20:22:11.735 error by controller[48]: 2018-11-16T19:22:11.711Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"options":{"
      ! Caught 2018-11-16 20:22:11.735 error by controller[48]: 2018-11-16T19:22:11.711Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"opt
      ! Caught 2018-11-16 20:22:11.735 error by controller[48]: 2018-11-16T19:22:11.711Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"
      ! Caught 2018-11-16 20:22:11.735 error by controller[47]: 2018-11-16T19:22:11.711Z socket.io-client:socket emitting packet with ack id 4
      ! Caught 2018-11-16 20:22:11.735 error by controller[46]: 2018-11-16T19:22:11.708Z socket.io-client:socket calling ack 3 with [null,"system.adapter.yahka.0.alive"]
      ! Caught 2018-11-16 20:22:11.735 error by controller[45]: 2018-11-16T19:22:11.708Z socket.io-parser decoded 33[null,"system.adapter.yahka.0.alive"] as {"type":3,"nsp":"/","id":3,"data":[null,"system.adapter.yahka.0.alive"]}
      ! Caught 2018-11-16 20:22:11.734 error by controller[44]: 2018-11-16T19:22:11.707Z engine.io-client:socket socket receive: type "message", data "33[null,"system.adapter.yahka.0.alive"]"
      ! Caught 2018-11-16 20:22:11.734 error by controller[43]: 2018-11-16T19:22:11.695Z engine.io-client:socket flushing 1 packets in socket
      ! Caught 2018-11-16 20:22:11.734 error by controller[42]: 2018-11-16T19:22:11.694Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"options":{"
      ! Caught 2018-11-16 20:22:11.734 error by controller[42]: 2018-11-16T19:22:11.694Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"opt
      ! Caught 2018-11-16 20:22:11.734 error by controller[41]: 2018-11-16T19:22:11.694Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"
      ! Caught 2018-11-16 20:22:11.734 error by controller[40]: 2018-11-16T19:22:11.694Z socket.io-client:socket emitting packet with ack id 3
      ! Caught 2018-11-16 20:22:11.734 error by controller[39]: 2018-11-16T19:22:04.044Z socket.io-client:socket emitting event ["message",".logging","system.adapter.admin.0.logging",{"val":false,"ack":true,"ts":1542396124036,"q":0,"from":"sys
      ! Caught 2018-11-16 20:22:11.734 error by controller[38]: 2018-11-16T19:22:04.043Z socket.io-parser decoded 2["message","
      .logging","system.adapter.admin.0.logging",{"val":false,"ack":true,"ts":1542396124036,"q":0,"from":"system.adapter.a
      ! Caught 2018-11-16 20:22:11.733 error by controller[37]: 2018-11-16T19:22:04.041Z engine.io-client:socket socket receive: type "message", data "2["message","*.logging","system.adapter.admin.0.logging",{"val":false,"ack":true,"ts":1542396
      ! Caught 2018-11-16 20:22:11.733 error by controller[36]: 2018-11-16T19:21:59.396Z engine.io-client:socket flushing 7 packets in socket
      ! Caught 2018-11-16 20:22:11.733 error by controller[35]: 2018-11-16T19:21:59.395Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],"opti
      ! Caught 2018-11-16 20:22:11.733 error by controller[35]: 2018-11-16T19:21:59.395Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},nul
      ! Caught 2018-11-16 20:22:11.733 error by controller[34]: 2018-11-16T19:21:59.395Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.
      ! Caught 2018-11-16 20:22:11.733 error by controller[33]: 2018-11-16T19:21:59.395Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"optio
      ! Caught 2018-11-16 20:22:11.733 error by controller[32]: 2018-11-16T19:21:59.395Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null
      ! Caught 2018-11-16 20:22:11.733 error by controller[31]: 2018-11-16T19:21:59.395Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0
      ! Caught 2018-11-16 20:22:11.733 error by controller[30]: 2018-11-16T19:21:59.395Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":61,"ack":true,"from":"system.adapter.yahka.0"},null],"options"
      ! Caught 2018-11-16 20:22:11.733 error by controller[29]: 2018-11-16T19:21:59.395Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":61,"ack":true,"from":"system.adapter.yahka.0"},null],"
      ! Caught 2018-11-16 20:22:11.732 error by controller[28]: 2018-11-16T19:21:59.394Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":61,"ack":true,"from":"system.adapter.yahka.0"},
      ! Caught 2018-11-16 20:22:11.732 error by controller[27]: 2018-11-16T19:21:59.394Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.74,"ack":true,"from":"system.adapter.yahka.0"},null],"
      ! Caught 2018-11-16 20:22:11.732 error by controller[26]: 2018-11-16T19:21:59.394Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.74,"ack":true,"from":"system.adapter.yahka.0"}
      ! Caught 2018-11-16 20:22:11.731 error by controller[26]: 2018-11-16T19:21:59.394Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.74,"ack":true,"from":"system.adapter.ya
      ! Caught 2018-11-16 20:22:11.731 error by controller[25]: 2018-11-16T19:21:59.394Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":19.03,"ack":true,"from":"system.adapter.yahka.0"},null],
      ! Caught 2018-11-16 20:22:11.731 error by controller[25]: 2018-11-16T19:21:59.394Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":19.03,"ack":true,"from":"system.adapter.yahka.0"
      ! Caught 2018-11-16 20:22:11.731 error by controller[24]: 2018-11-16T19:21:59.393Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":19.03,"ack":true,"from":"system.adapter.y
      ! Caught 2018-11-16 20:22:11.731 error by controller[24]: 2018-11-16T19:21:59.393Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":29.3,"ack":true,"from":"system.adapter.yahka.0"},null],"option
      ! Caught 2018-11-16 20:22:11.731 error by controller[24]: 2018-11-16T19:21:59.393Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":29.3,"ack":true,"from":"system.adapter.yahka.0"},null]
      ! Caught 2018-11-16 20:22:11.731 error by controller[24]: 2018-11-16T19:21:59.393Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":29.3,"ack":true,"from":"system.adapter.yahka.0"
      ! Caught 2018-11-16 20:22:11.731 error by controller[24]: 2018-11-16T19:21:59.393Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"
      ! Caught 2018-11-16 20:22:11.731 error by controller[24]: 2018-11-16T19:21:59.392Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.
      ! Caught 2018-11-16 20:22:11.730 error by controller[24]: 2018-11-16T19:21:59.392Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.a
      ! Caught 2018-11-16 20:22:11.730 error by controller[23]: 2018-11-16T19:21:59.391Z engine.io-client:socket flushing 1 packets in socket
      ! Caught 2018-11-16 20:22:11.730 error by controller[22]: 2018-11-16T19:21:59.390Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":25,"from":"system.adapter.yahka.0"},nu
      ! Caught 2018-11-16 20:22:11.730 error by controller[21]: 2018-11-16T19:21:59.390Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":25,"from":"system.adapter.yahk
      ! Caught 2018-11-16 20:22:11.730 error by controller[20]: 2018-11-16T19:21:59.388Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":25,"from":"system.adapt
      ! Caught 2018-11-16 20:22:11.730 error by controller[19]: 2018-11-16T19:21:49.249Z engine.io-client:socket socket receive: type "pong", data "undefined"
      ! Caught 2018-11-16 20:22:11.730 error by controller[18]: 2018-11-16T19:21:49.248Z engine.io-client:socket flushing 1 packets in socket
      ! Caught 2018-11-16 20:22:11.730 error by controller[17]: 2018-11-16T19:21:49.247Z engine.io-client:socket writing ping packet - expecting pong within 5000ms
      ! Caught 2018-11-16 20:22:11.730 error by controller[16]: 2018-11-16T19:21:49.181Z engine.io-client:socket socket receive: type "pong", data "undefined"
      ! Caught 2018-11-16 20:22:11.729 error by controller[15]: 2018-11-16T19:21:49.179Z engine.io-client:socket flushing 1 packets in socket
      ! Caught 2018-11-16 20:22:11.729 error by controller[14]: 2018-11-16T19:21:49.179Z engine.io-client:socket writing ping packet - expecting pong within 5000ms
      ! Caught 2018-11-16 20:22:11.729 error by controller[13]: 2018-11-16T19:21:44.389Z engine.io-client:socket flushing 7 packets in socket
      ! Caught 2018-11-16 20:22:11.729 error by controller[12]: 2018-11-16T19:21:44.386Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},null],"opti
      ! Caught 2018-11-16 20:22:11.729 error by controller[12]: 2018-11-16T19:21:44.386Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.0"},nul
      ! Caught 2018-11-16 20:22:11.729 error by controller[11]: 2018-11-16T19:21:44.386Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.outputCount",{"val":8,"ack":true,"from":"system.adapter.yahka.
      ! Caught 2018-11-16 20:22:11.729 error by controller[11]: 2018-11-16T19:21:44.386Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null],"optio
      ! Caught 2018-11-16 20:22:11.729 error by controller[11]: 2018-11-16T19:21:44.386Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0"},null
      ! Caught 2018-11-16 20:22:11.729 error by controller[11]: 2018-11-16T19:21:44.385Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.inputCount",{"val":0,"ack":true,"from":"system.adapter.yahka.0
      ! Caught 2018-11-16 20:22:11.729 error by controller[11]: 2018-11-16T19:21:44.385Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":46,"ack":true,"from":"system.adapter.yahka.0"},null],"options"
      ! Caught 2018-11-16 20:22:11.728 error by controller[11]: 2018-11-16T19:21:44.385Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":46,"ack":true,"from":"system.adapter.yahka.0"},null],"
      ! Caught 2018-11-16 20:22:11.728 error by controller[10]: 2018-11-16T19:21:44.384Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.uptime",{"val":46,"ack":true,"from":"system.adapter.yahka.0"},
      ! Caught 2018-11-16 20:22:11.728 error by controller[9]: 2018-11-16T19:21:44.384Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.38,"ack":true,"from":"system.adapter.yahka.0"},null],"o
      ! Caught 2018-11-16 20:22:11.728 error by controller[8]: 2018-11-16T19:21:44.384Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.38,"ack":true,"from":"system.adapter.yahka.0"},
      ! Caught 2018-11-16 20:22:11.728 error by controller[7]: 2018-11-16T19:21:44.384Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapUsed",{"val":10.38,"ack":true,"from":"system.adapter.yah
      ! Caught 2018-11-16 20:22:11.728 error by controller[6]: 2018-11-16T19:21:44.383Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":19.03,"ack":true,"from":"system.adapter.yahka.0"},null],"
      ! Caught 2018-11-16 20:22:11.728 error by controller[5]: 2018-11-16T19:21:44.383Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":19.03,"ack":true,"from":"system.adapter.yahka.0"}
      ! Caught 2018-11-16 20:22:11.728 error by controller[4]: 2018-11-16T19:21:44.383Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memHeapTotal",{"val":19.03,"ack":true,"from":"system.adapter.ya
      ! Caught 2018-11-16 20:22:11.728 error by controller[3]: 2018-11-16T19:21:44.383Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":28.79,"ack":true,"from":"system.adapter.yahka.0"},null],"option
      ! Caught 2018-11-16 20:22:11.727 error by controller[3]: 2018-11-16T19:21:44.383Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":28.79,"ack":true,"from":"system.adapter.yahka.0"},null]
      ! Caught 2018-11-16 20:22:11.727 error by controller[2]: 2018-11-16T19:21:44.382Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.memRss",{"val":28.79,"ack":true,"from":"system.adapter.yahka.0"
      ! Caught 2018-11-16 20:22:11.727 error by controller[2]: 2018-11-16T19:21:44.382Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.yahka.0"}
      ! Caught 2018-11-16 20:22:11.727 error by controller[2]: 2018-11-16T19:21:44.382Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.adapter.y
      ! Caught 2018-11-16 20:22:11.727 error by controller[2]: 2018-11-16T19:21:44.382Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.connected",{"val":true,"ack":true,"expire":30,"from":"system.ad
      ! Caught 2018-11-16 20:22:11.727 error by controller[1]: 2018-11-16T19:21:44.381Z engine.io-client:socket flushing 1 packets in socket
      ! Caught 2018-11-16 20:22:11.727 error by controller[1]: 2018-11-16T19:21:44.381Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":25,"from":"system.adapter.yahka.0"},nul
      ! Caught 2018-11-16 20:22:11.727 error by controller[1]: 2018-11-16T19:21:44.380Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":25,"from":"system.adapter.yahka
      ! Caught 2018-11-16 20:22:11.726 error by controller[1]: 2018-11-16T19:21:44.380Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":true,"ack":true,"expire":25,"from":"system.adapte
      ! yahka.0 2018-11-16 20:22:11.709 info terminating
      ! yahka.0 2018-11-16 20:22:11.687 info cleaned everything up…
      ! host.iobroker 2018-11-16 20:22:11.680 info stopInstance system.adapter.yahka.0 killing pid 4701
      ! host.iobroker 2018-11-16 20:22:11.680 info stopInstance system.adapter.yahka.0
      ! host.iobroker 2018-11-16 20:22:11.679 info object change system.adapter.yahka.0
      ! javascript.0 2018-11-16 20:21:02.205 info script.js.Scripte.Anwesenheit.Mike: registered 1 subscription and 0 schedules
      ! javascript.0 2018-11-16 20:21:02.203 info Start javascript script.js.Scripte.Anwesenheit.Mike
      ! javascript.0 2018-11-16 20:21:02.196 info Stop script script.js.Scripte.Anwesenheit.Mike
      ! yahka.0 2018-11-16 20:20:59.396 info adding Alarmanlage with UUID: 85f29310-269a-4dfb-85f4-b1df7e5bfba3
      ! yahka.0 2018-11-16 20:20:59.381 info adapter ready, checking config
      ! yahka.0 2018-11-16 20:20:59.355 info starting. Version 0.7.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v6.14.4

      ioBroker im Docker auf Synology DiskStation DS 716+II mit DSM 6.2.1

      • Lightmanager Air / Lupusec XT2 Plus mit div. Fenster- u. Türkontakten, Rauch- u. Bewegungsmelder / Harmony Hub / Fritzbox 7590 OS7
      • schaltbare Steckdosen / Alexa Echo Dot 3 / Zigbee USB Stick / diverse Xiaomi Produkte / Xiaomi Yeelight Birnen
      1 Reply Last reply
      0
      • M Offline
        M Offline
        Monox
        wrote on last edited by
        #809

        Nenn den yahka mal anders zb iobroker, hatte das bei beim Umzug vom iobroker in eine vm auf meiner Synology auch nicht binden konnte, nach dem umbenennen ging es dann.

        Grüße Monox

        1 Reply Last reply
        0
        • StM47S Offline
          StM47S Offline
          StM47
          wrote on last edited by
          #810

          Funktioniert leider nicht. Alles schon probiert.

          Es wird ja gefunden, es kann nur nicht zum HomeKit hinzugefügt werden.

          ioBroker im Docker auf Synology DiskStation DS 716+II mit DSM 6.2.1

          • Lightmanager Air / Lupusec XT2 Plus mit div. Fenster- u. Türkontakten, Rauch- u. Bewegungsmelder / Harmony Hub / Fritzbox 7590 OS7
          • schaltbare Steckdosen / Alexa Echo Dot 3 / Zigbee USB Stick / diverse Xiaomi Produkte / Xiaomi Yeelight Birnen
          1 Reply Last reply
          0
          • B Offline
            B Offline
            bertuz
            wrote on last edited by
            #811

            Erst mal vielen Dank für den tollen Adapter!

            Läuft super bei mir, auch wenn ich über einige der Parameter / Service-Typen leider kaum Infos finde.

            Kann mir jemand auf die Sprünge helfen, wie ich bei die Color Temperatur meiner Yeelight Ceiling 1 zu konfigurieren habe?

            Aktuell ist meine Konfig so (s. Anhang) und da tut sich nichts, wenn ich in der Home-App die Temperatur ändere. Der Rest funktioniert einwandfrei 😉

            9877_captura.png

            1 Reply Last reply
            0
            • B Offline
              B Offline
              bo0n
              wrote on last edited by
              #812

              Hallo,

              ich habe den ganzen Thread aufmerksam gelesen und alle möglichen Optionen durchgespielt aber der Adapter taucht leider nicht auf dem IPhone auf.

              0.7.1 ist installiert und alles ist "grün"…

              Folgende Fehlermeldung in den Log's:

              Caught	2018-11-30 23:06:29.930	error	by controller[6]: Fri, 30 Nov 2018 22:06:09 GMT engine.io-client:socket socket receive: type "pong", data "undefined"
              Caught	2018-11-30 23:06:29.930	error	by controller[5]: Fri, 30 Nov 2018 22:06:09 GMT engine.io-client:socket flushing 1 packets in socket
              Caught	2018-11-30 23:06:29.929	error	by controller[4]: Fri, 30 Nov 2018 22:06:09 GMT engine.io-client:socket writing ping packet - expecting pong within 60000ms
              

              Benutzername mehrfach geändert, MAC mehrfach geändert usw…die "üblichen" Tipps bzgl. dieses Problems helfen nicht. Hat jemand diesen Fehler schon einmal gehabt?

              Gruß

              1 Reply Last reply
              0
              • DutchmanD Offline
                DutchmanD Offline
                Dutchman
                Developer Most Active Administrators
                wrote on last edited by
                #813

                Auf was für einem System läuft dein ioBroker?

                Sent from my iPhone using Tapatalk

                1 Reply Last reply
                0
                • B Offline
                  B Offline
                  bo0n
                  wrote on last edited by
                  #814

                  Der Broker läuft auf einem Raspi3B…

                  Ich habe mal an den Interface Einstellungen rumgespielt....wenn ich nur WLAN auf dem Raspi anhabe sehe ich ihn?! Es hängt wohl mit dem Zusammenspiel Lan\WLan auf dem Raspi zusammen!? Ideen?

                  Aktuell hängt der Raspi per lan im Netz...wlan aus. Pivccu und Rest läuft einwandfrei...

                  1 Reply Last reply
                  0
                  • W Offline
                    W Offline
                    whitbread
                    wrote on last edited by
                    #815

                    Mal ganz blöd gefragt: Bin ich hier beim falschen Adapter?!?

                    Ich möchte nicht meine bestehenden Geräte in Homekit haben, sondern Homekit-Geräte in ioBroker haben. Diese sollten dann Aktualisierungen erfahren und über ioBroker steuerbar sein. Konkret habe ich aktuell Steckdosen mit Leistungsmessung von Koogeek hier. Geht das überhaupt mit Yahka?

                    1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      MikeG31
                      wrote on last edited by
                      #816

                      Hallo,

                      ich versuche gerade ein Gerät über Yahka hinzuzufügen. Normalerweise müsste ich im unteren Bereich mein Gerät auswählen können, jedoch kann ich nichts auswählen. Was genau machen ich falsch?

                      11956_yahka.jpg

                      1 Reply Last reply
                      0
                      • V Offline
                        V Offline
                        Videonisse
                        wrote on last edited by
                        #817

                        Hast du auch Geräteeigenschaften konfiguriert?

                        ioBroker v3.3.18, Debian 10 Buster 64-bit (Vmware 6.5 VM), Node.js: v12.22.6, NPM: 6.14.15
                        Most important Device Adapters: KNX, Trådfri, Homekit/Yahka

                        1 Reply Last reply
                        0
                        • M Offline
                          M Offline
                          MikeG31
                          wrote on last edited by
                          #818

                          Ja. Habe den Fehler gefunden. Es lag am Internet Explorer, mit Firefox klappt es ohne Probleme. Auf die Idee muss man erst mal kommen….

                          1 Reply Last reply
                          0
                          • DutchmanD Offline
                            DutchmanD Offline
                            Dutchman
                            Developer Most Active Administrators
                            wrote on last edited by
                            #819

                            @whitbread:

                            Geht das überhaupt mit Yahka? `

                            Nein! Yahka ist ioBroker nach homekit.

                            Für die meisten Geräte welche homekit können gibt es ja auch Adapter (zB Philips Hue, Ikea usw)

                            Sent from my iPhone using Tapatalk

                            1 Reply Last reply
                            0
                            • M Offline
                              M Offline
                              MaxMan23
                              wrote on last edited by
                              #820

                              Hallo zusammen,

                              kann mir hier jemand weiterhelfen? Es geht darum, bei einem Homematic Dimmer den letzten Einschaltwert vom Level wieder aufzurufen, anstelle von 100% Licht an. viewtopic.php?f=23&t=6427#p200306

                              1 Reply Last reply
                              0
                              • DutchmanD Offline
                                DutchmanD Offline
                                Dutchman
                                Developer Most Active Administrators
                                wrote on last edited by
                                #821

                                Das liegt am Befehl, bei homematic ist an halt 100% anstatt drauf drücken gedrückt halten und Dan dimmen.

                                Es ist nach europäischer Richtlinie nicht erlaubt den letzen wert bei einschalten Standard zu benutzen es müssen 100% sein wegen Sicherheit

                                Sent from my iPhone using Tapatalk

                                1 Reply Last reply
                                0
                                • M Offline
                                  M Offline
                                  MaxMan23
                                  wrote on last edited by
                                  #822

                                  Das ist doch falsch. Es geht sowohl mit dem Lichtschalter als auch mit der Homebrige. Leuchtet mit nicht ein wieso ein wieso das in yahka nicht funktionieren sollte…

                                  1 Reply Last reply
                                  0
                                  • K Offline
                                    K Offline
                                    Kugelkopf
                                    wrote on last edited by
                                    #823

                                    Ich habe inzw. die Version 8.1 installiert. Allerdings gab es die Fehler auch schon unter v7.1.

                                    Inzw. habe ich aber ein paar Geräte mehr im Homekit YAHKA Adapter hinzugefügt. Doch leider führt es inzw. dazu das das ganze raspi abschmiert wenn ich neue Geräte hinzugefügt habe oder den Adapter neu starte. Der Log ist voller Fehler.

                                    5370_yahkalog.txt
                                    Musste den Log als txt -Datei speichern weil er sonst die Zugelassen Zeichenanzahl hier übersteigen würde. Es ist nur ein Auszug aus den ganzen Fehlern die er wirft…

                                    Und es geht unendlich so weiter. Irgendwann ist dann iobroker wieder zu erreichen und dann läuft er auch. Allerdings ist dann die Web Instanze rot und muss neu gestartet werden.

                                    Hat jemand eine Idee woran es liegt?

                                    1 Reply Last reply
                                    0
                                    • P Offline
                                      P Offline
                                      peer6969
                                      wrote on last edited by
                                      #824

                                      Die engine.io/socket.io-Error habe ich auch. Keine Ahnung woran das liegen könnte. Habe sie auch nur beim yahka-Adapter, beim Hinweis auf neue dependencies im Changelog der 0.8.1 hatte ich Hoffnung, dass diese Fehler gefixt wurden, leider ist das nicht der Fall.

                                      Bisher haben die Fehler bei mir aber nicht zu Fehlfunktionen geführt, lediglich das Log wird gespamt.

                                      1 Reply Last reply
                                      0
                                      • B Offline
                                        B Offline
                                        bo0n
                                        wrote on last edited by
                                        #825

                                        Mahlzeit!

                                        Nach Update auf V. 0.8.2 habe ich folgendes im Log!

                                        host.All-In-One_RasPi	2018-12-10 10:32:14.414	info	Restart adapter system.adapter.yahka.0 because enabled
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.414	error	instance system.adapter.yahka.0 terminated with code 1 ()
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.414	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/lib/HAPServer.js:8:15)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.413	error	Caught by controller[0]: at require (internal/module.js:11:18)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.413	error	Caught by controller[0]: at Module.require (module.js:597:17)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.413	error	Caught by controller[0]: at Function.Module._load (module.js:498:3)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.413	error	Caught by controller[0]: at tryModuleLoad (module.js:506:12)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.412	error	Caught by controller[0]: at Module.load (module.js:566:32)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.412	error	Caught by controller[0]: at Object.Module._extensions..js (module.js:664:10)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.412	error	Caught by controller[0]: at Module._compile (module.js:653:30)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.412	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/index.js:1:99)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.412	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.yahka/node_modules/bindings/bindings.js:96:9)
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.411	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/compiled/8.14.0/linux/arm/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.411	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/build/default/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.411	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/Release/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.411	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/out/Release/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.410	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/Debug/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.410	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/out/Debug/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.410	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/build/Release/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.410	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/build/Debug/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.409	error	Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.yahka/node_modules/ed25519-hap/build/ed25519.node
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.409	error	Caught by controller[0]: Error: Could not locate the bindings file. Tried:
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.409	error	Caught by controller[0]: ^
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.409	error	Caught by controller[0]: throw err
                                        host.All-In-One_RasPi	2018-12-10 10:32:14.408	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.yahka/node_modules/bindings/bindings.js:99</anonymous></anonymous>
                                        

                                        0.8.1 lief problemlos!

                                        Jemand eine Idee?

                                        EDIT:

                                        Habe im Verzeichnis node_modules/iobroker.yahka mal ein „npm rebuild“ ausgeführt…danach ging alles wieder!

                                        1 Reply Last reply
                                        0
                                        • flugwelleF Offline
                                          flugwelleF Offline
                                          flugwelle
                                          wrote on last edited by
                                          #826

                                          Bei mir funktioniert auch 0.8.2 ohne neue Besonderheiten ..

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

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

                                          132

                                          Online

                                          32.4k

                                          Users

                                          81.3k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe