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

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    Yet another HomeKit adapter

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

      Wie heißen die Datenpunkte für On und Brightness? Ist auf dem Screenshot nicht zu sehen

      Gesendet von iPhone mit Tapatalk

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

        @JW86:

        Wie heißen die Datenpunkte für On und Brightness? Ist auf dem Screenshot nicht zu sehen

        Gesendet von iPhone mit Tapatalk `

        Jeweils hm-rpc.0.NEQ0257178.1.LEVEL

        1 Reply Last reply Reply Quote 0
        • J
          JW86 last edited by

          Das kann nicht funktionieren. On ist ein bool, also 0 oder 1 und level sind Prozent (0 bis 100). Das erklärt warum du beim Einschalten eine Helligkeit von 1% hast (weil On den Level auf 1% setzt)

          Gibt es keinen State den du für On/Off nutzen kannst?

          Poste mal die Liste der verfügbaren Datenpunkte

          Gesendet von iPhone mit Tapatalk

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

            @JW86:

            Wenn du den Rolladen über die Wandtaster fahren lässt, was kommt dann eigentlich für ein Level? `
            Bei den Fibaro Autoren ist es so, dass beim Schreiben des Zielwerte in Level_1 dieser nur kurz angezeigt wird. Dann springt er auf den Startwert zurück. Ist der Zielwert erreicht, zeigt Level_1 den Zielwert an. Das ist auch mein eigentliches Grundproblem. Denn wenn unter Target nicht immer der Zielwert steht, dann zeigt HomeKit nur murks an…

            D.b. zzgl. zum "Faken" von Position, müsste man noch Target "faken". Nur da fehlt mir noch eine schlaue Lösung die kein Timingproblem hat.

            Denn der folgende Code schreibt leider oft, aber nicht immer, den Ausgangswert in mein Datenpunkt für Target. Denn anscheinen ist der Wert in Level_1 noch nicht abschließen geschrieben, obwohl der Verbrauch (PowerLevel) kleiner 1 ist.

            if (PowerLevel < 1) {
   var wert = getState(LevelRollo).val;
   console.log('### Power: ' + PowerLevel + '. Setze Target auf: ' + wert)
   setState(TargetLevel,wert);
}

            @JW86:

            Kannst du mal kurz die folgende Version des Scripts einspielen und mir die Log-Ausgabe geben? Bin mir noch nicht sicher wie man den Sollwert erkennen soll.

            Fahre am besten mal per Homekit hoch+runter und per Taster hoch+runter und poste das Skript hier. `

            Klar. Sehr gerne…

            Homekit hoch+runter

            ! ````
            javascript.0 2018-01-16 17:24:05.679 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 0.7(true)
            javascript.0 2018-01-16 17:24:05.666 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 0 - caused by level:0(true) and power: 123.1(true)
            javascript.0 2018-01-16 17:23:47.300 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(true) and power: 123.1(true)
            javascript.0 2018-01-16 17:23:46.179 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(true) and power: 0.7(true)
            javascript.0 2018-01-16 17:23:46.108 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(false) and power: 0.7(true)
            javascript.0 2018-01-16 17:15:24.169 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(true) and power: 0.7(true)
            javascript.0 2018-01-16 17:15:24.146 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 1 - caused by level:100(true) and power: 67.4(true)
            javascript.0 2018-01-16 17:15:22.304 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 67.4(true)
            javascript.0 2018-01-16 17:15:04.953 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 119.9(true)
            javascript.0 2018-01-16 17:15:03.828 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 0.7(true)
            javascript.0 2018-01-16 17:15:03.758 info script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(false) and power: 0.7(true)

            
****Taster hoch+runter****

>! ````
javascript.0	2018-01-16 17:26:31.657	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 0.7(true)
javascript.0	2018-01-16 17:26:31.637	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 0.7(true)
javascript.0	2018-01-16 17:26:30.584	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(true) and power: 0.7(true)
javascript.0	2018-01-16 17:26:13.241	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(true) and power: 123.5(true)
javascript.0	2018-01-16 17:26:05.188	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:100(true) and power: 0.7(true)
javascript.0	2018-01-16 17:26:05.168	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 1 - caused by level:100(true) and power: 73.7(true)
javascript.0	2018-01-16 17:26:03.336	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 73.7(true)
javascript.0	2018-01-16 17:25:45.984	info	script.js.common.garbage.FibaroWindowCoverStateEmulator: settings state with id: javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.position to 2 - caused by level:0(true) and power: 123.1(true)
            1 Reply Last reply Reply Quote 0
            • Paulchen67
              Paulchen67 last edited by

              @JW86:

              Das kann nicht funktionieren. On ist ein bool, also 0 oder 1 und level sind Prozent (0 bis 100). Das erklärt warum du beim Einschalten eine Helligkeit von 1% hast (weil On den Level auf 1% setzt)

              Gibt es keinen State den du für On/Off nutzen kannst?

              Poste mal die Liste der verfügbaren Datenpunkte `

              Findest du hier

              Seite 25 10.01.2018, 15:21

              Bild 2

              Davon hab ich 2 im Einsatz.

              Dann noch einen HomeMatic iP Dimmer

              Bild 4

              Da sind noch weniger Datenpunkte.

              Bild5 zeigt übrigens die Config als Door. Seltsam ist das es da funktioniert und da auch nur

              mit Level und zusätzlich noch mit Direction gearbeitet wird.

              Deswegen dachte ich ja, ob es nicht einfacher wäre einen Dimmer zu yahka hinzugefügt der

              diese Config möglich macht.

              1 Reply Last reply Reply Quote 0
              • J
                JW86 last edited by

                @Paulchen67:

                Findest du hier

                Seite 25 10.01.2018, 15:21

                Bild 2

                Davon hab ich 2 im Einsatz.

                Dann noch einen HomeMatic iP Dimmer

                Bild 4

                Da sind noch weniger Datenpunkte. `

                Ok. Ich habe nun auch mal einen Dimmer Testweise eingerichtet um zu schauen was Homekit so sendet wenn man an/aus schaltet etc.

                Aus meiner Sicht bekommst du deine Dimmer aktuell nicht in Yahka zum laufen (als Lightbulb). Du könntest es mit Javascript vllt irgendwie hinbekommen.

                Ich mach mir mal dazu Gedanken und schreibe erstelle einen GitHub-Issue

                1 Reply Last reply Reply Quote 0
                • J
                  JW86 last edited by

                  @eumats:

                  Homekit hoch+runter `

                  Hier lässt sich ganz klar erkennen, das der Sollwert (Target) das "ACK" Flag nicht gesetzt hat. D.h. der Wert in Level_1 ohne ACK-Flag, ist der Zielwert.

                  @eumats:

                  Taster hoch+runter `

                  Hier kann man aber leider gar nichts erkennen - auch keine Richtung oder ähnliches. Man sieht einfach nur, das der Rolladen auf Level 0 steht und Energie verbraucht und irgendwann ist er bei 100 und verbraucht keine Energie mehr.

                  Was hältst du von folgendem vorgehen:

                  1. Bei Leveländerung wird der Level als Target genutzt wenn ACK = false

                  2. Bei ACK = true, wird der Level als Current genutzt

                  3. X sekunden nachdem Power < 1 wurde, wird der Level sicherheitshalber als Target übernommen

                  1+2 sollten für die Homekit Steuerung funktionieren

                  3. sollte für die manuelle Bedienung halbwegs funktionieren. Homekit kann dann zwar nicht anzeigen, das der Rolladen fährt, aber X Sekunden nachdem manuellen Fahren wird der Rolladen aktualisiert (d.h. du siehst dann wenigstens den aktuellen Zustand)

                  Soll ich dir hierfür was ein Skript schreiben oder bekommst du das alleine hin?

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

                    @JW86:

                    Was hältst du von folgendem vorgehen:

                    1. Bei Leveländerung wird der Level als Target genutzt wenn ACK = false

                    2. Bei ACK = true, wird der Level als Current genutzt

                    3. X sekunden nachdem Power < 1 wurde, wird der Level sicherheitshalber als Target übernommen

                    1+2 sollten für die Homekit Steuerung funktionieren

                    3. sollte für die manuelle Bedienung halbwegs funktionieren. Homekit kann dann zwar nicht anzeigen, das der Rolladen fährt, aber X Sekunden nachdem manuellen Fahren wird der Rolladen aktualisiert (d.h. du siehst dann wenigstens den aktuellen Zustand)

                    Soll ich dir hierfür was ein Skript schreiben oder bekommst du das alleine hin? `

                    Eine ähnliche Idee hatte ich auch schon und fummele da schon ein paar Nächte dran rum, aber es hapert bei mir an der Umsetzung. Daher wäre ich Dir sehr dankbar, wenn Du mir das Skript erstellen könntest!!

                    1 Reply Last reply Reply Quote 0
                    • J
                      JW86 last edited by

                      @eumats:

                      Eine ähnliche Idee hatte ich auch schon und fummele da schon ein paar Nächte dran rum, aber es hapert bei mir an der Umsetzung. Daher wäre ich Dir sehr dankbar, wenn Du mir das Skript erstellen könntest!! `

                      Probier mal das hier:

                      ! ````
                      const FallbackTimerInMilliseconds = 10000;
                      ! function FibaroWindowCoverStateEmulator(levelId, powerId, fakeCurrentStateId, fakeTargetStateId) {
                      this.levelId = levelId;
                      this.powerId = powerId;
                      this.fakeCurrentStateId = fakeCurrentStateId;
                      this.fakeTargetStateId = fakeTargetStateId;
                      this.fallbackTimerId = undefined;

                      on({id: levelId}, () => this.refreshFakeStates());
on({id: powerId}, () => this.refreshFakeStates());
on({id: fakeTargetStateId}, this.fakeTargetChanged.bind(this))

                      }

                      ! FibaroWindowCoverStateEmulator.prototype = {
                      refreshFakeStates: function() {
                      var level = getState(this.levelId).val;
                      var levelAck = getState(this.levelId).ack;
                      var power = getState(this.powerId).val;
                      var powerAck = getState(this.powerId).ack;

                          console.log('refreshing fake states, level: ' + level + '(' + levelAck + ') | power: ' + power + '(' + powerAck + ')');
    if (levelAck) {
        this.setCurrentState(level, 'level ack is true');
    } else {
        this.setTargetState(level, 'level ack is false');
    }

    this.clearFallbackTimer();
    if (power < 1) {
        this.setupFallbackTimer();
    }
},

clearFallbackTimer: function() {
    if(this.fallbackTimerId === undefined)
        return;
    clearTimeout(this.fallbackTimerId);
},

setupFallbackTimer: function() {
    if(this.fallbackTimerId !== undefined)
        this.clearFallbackTimer();

    setTimeout(this.fallbackTimerRaised.bind(this), FallbackTimerInMilliseconds);
},

fallbackTimerRaised: function() {
    var level = getState(this.levelId).val;
    this.setCurrentState(level, 'fallback timer');
    this.setTargetState(level, 'fallback timer');
},

setCurrentState: function(value, reason) {
    setState(this.fakeCurrentStateId, value, true);
    console.log('setted ' + this.fakeCurrentStateId + ' to ' + value + ' | reason: ' + reason);
},

setTargetState: function(value, reason) {
    setState(this.fakeTargetStateId, value, true);
    console.log('setted ' + this.fakeTargetStateId + ' to ' + value + ' | reason: ' + reason);
},

setLevel: function(value, reason) {
    setState(this.levelId, value, true);
    console.log('setted ' + this.levelId + ' to ' + value + ' | reason: ' + reason);
},

fakeTargetChanged: function(stateObject) {
    if (stateObject.newState.ack) {
        console.log('cancel fake target change handler - ack is true');
        return
    }
    this.setLevel(stateObject.newState.val, 'fake target changed');
}

                      };

                      ! var test1 = new FibaroWindowCoverStateEmulator("Test1.Level", "Test1.Power2", "Test1.fakeCurrent", "Test1.fakeTarget")
                      ! ````

                      FallbackTimerInMilliseconds kannst du wahrscheinlich kleiner machen - musst du testen.

                      In Homekit CurrentState und TargetState auf die Fake Werte schauen lassen. Conversion kann jetzt "passthrough" sein.

                      Wie zuvor auch, musst du die beiden States selbst anlegen.

                      Falls was nicht geht, log posten 😉

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

                        @JW86:

                        Probier mal das hier:

                        FallbackTimerInMilliseconds kannst du wahrscheinlich kleiner machen - musst du testen.

                        In Homekit CurrentState und TargetState auf die Fake Werte schauen lassen. Conversion kann jetzt "passthrough" sein.

                        Wie zuvor auch, musst du die beiden States selbst anlegen.

                        Falls was nicht geht, log posten 😉 `

                        Wow. Das ging schnell. Besten Dank.

                        Ein erster kurzer Test hat leider nicht funktioniert. Ich wollte den Rollladen von 33% auf 22% fahren lassen. Der Slide ist dann wieder auf 31% zurückgefallen.

                        De Anzeige in HomeKit (wird geöffnet, …) war leider auch nicht korrekt... Meine yahka Konfiguration siehe Screenshot...

                        Log-Ausgabe:

                        ! ````
                        javascript.0 2018-01-16 22:52:06.504 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:06.504 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:06.503 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:06.485 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:06.484 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:06.483 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:05.083 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:05.079 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:05.078 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:05.018 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:05.014 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:05.013 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:04.994 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:04.994 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:04.993 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:04.947 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:04.943 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:04.942 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: fallback timer
                        javascript.0 2018-01-16 22:52:04.496 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: level ack is true
                        javascript.0 2018-01-16 22:52:04.495 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: refreshing fake states, level: 31(true) | power: 0.7(true)
                        javascript.0 2018-01-16 22:52:04.474 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 31 | reason: level ack is true
                        javascript.0 2018-01-16 22:52:04.473 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: refreshing fake states, level: 31(true) | power: 0.7(true)
                        javascript.0 2018-01-16 22:52:03.072 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 33 | reason: level ack is true
                        javascript.0 2018-01-16 22:52:03.071 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: refreshing fake states, level: 33(true) | power: 0.7(true)
                        javascript.0 2018-01-16 22:52:03.008 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.CurrentLevel to 33 | reason: level ack is true
                        javascript.0 2018-01-16 22:52:03.007 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: refreshing fake states, level: 33(true) | power: 0.7(true)
                        javascript.0 2018-01-16 22:52:02.988 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:02.985 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 31 | reason: level ack is false
                        javascript.0 2018-01-16 22:52:02.985 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: refreshing fake states, level: 31(false) | power: 0.7(true)
                        javascript.0 2018-01-16 22:52:02.978 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.LevelRollo to 31 | reason: fake target changed
                        javascript.0 2018-01-16 22:52:02.944 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: cancel fake target change handler - ack is true
                        javascript.0 2018-01-16 22:52:02.940 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.TargetLevel to 22 | reason: level ack is false
                        javascript.0 2018-01-16 22:52:02.939 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: refreshing fake states, level: 22(false) | power: 0.7(true)
                        javascript.0 2018-01-16 22:52:02.927 info script.js.common.Devices.Rolladen.FibaroWindowCoverStateEmulator: setted javascript.0.virtualDevice.Rolllaeden.EsszimmerOsten.LevelRollo to 22 | reason: fake target changed

                        
die Funktion setLevel musste ich wie folgt anpassen, da sonst der Fibaro Autor nicht getriggert wird.

                        setLevel: function(value, reason) {
    //setState(this.levelId, value, true);
    setState(this.levelId, value);
    console.log('setted ' + this.levelId + ' to ' + value + ' | reason: ' + reason);
},

                        [3610_untitled.jpg](/assets/uploads/files/3610_untitled.jpg)
                        1 Reply Last reply Reply Quote 0
                        • eumats
                          eumats last edited by

                          @eumats:

                          Ein erster kurzer Test hat leider nicht funktioniert. Ich wollte den Rollladen von 33% auf 22% fahren lassen. Der Slide ist dann wieder auf 31% zurückgefallen.

                          De Anzeige in HomeKit (wird geöffnet, …) war leider auch nicht korrekt... `

                          @ JW86:

                          In Anlehnung an den Skript habe ich nun eine Lösung gefunden. Ich werde sie bei Gelegenheit hier im Forum posten…

                          Nach mal Danke für Deine Hilfe!

                          1 Reply Last reply Reply Quote 0
                          • D
                            danny030 last edited by

                            Hi,

                            vermutlich seid ihr die Frage schon leid, aber ich habe nun auch dieses ominöse Cannot start file.

                            Bei mir lief der Adapter unter 0.5.5 reibungslos - alles in Ordnung. Ich habe mir dann, scheinbar dummerweise, zugetraut das Update auf 0.6.1 durchzuführen über "Installieren aus eigenem URL".

                            Anschließend kommt im Log:

                            startInstance yahka.0: cannot find start file!

                            Alles, was ich bisher dazu als mögliche Lösungen gelesen habe, funktioniert nicht. Den Adapter kann ich als Instanz hinzufügen. Wenn ich das Konfigurationsmenü öffne, sind alle Buttons aber wirkungslos. Es passiert nichts, wenn man drauf klickt.

                            ! sudo apt-get install avahi-daemon libnss-mdns avahi-discover avahi-utils sudo nano /etc/avahi/avahi-daemon.conf ! host-name=sd-pi domain-name=local enable-dbus=yes disable-publishing=no disable-user-service-publishing=no ! sudo /etc/init.d/avahi-daemon restart !
                            ! Und schließlich sogar Neustart von ioBroker (über Admin)

                            Während ich schreibe, ein Downgrade auf 0.6.0 sah erst etwas besser aus. Konfiguration ist nun möglich. Der Adapter läuft aber nicht, bleibt rot. Fehlermeldung im Log:

                            ! Restart adapter system.adapter.yahka.0 because enabled host.sd-pi 2018-01-27 23:17:45.311 error instance system.adapter.yahka.0 terminated with code 1 () host.sd-pi 2018-01-27 23:17:45.311 error Caught by controller[2]: at bootstrap_node.js:608:3 host.sd-pi 2018-01-27 23:17:45.311 error Caught by controller[2]: at startup (bootstrap_node.js:187:16) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at Function.Module.runMain (module.js:684:10) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at Function.Module._load (module.js:491:3) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at tryModuleLoad (module.js:499:12) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at Module.load (module.js:556:32) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at Object.Module._extensions..js (module.js:654:10) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at Module._compile (module.js:643:30) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: at Object. (/opt/iobroker/node_modules/iobroker.yahka/main.js:5:57) host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: TypeError: utils.adapter is not a function host.sd-pi 2018-01-27 23:17:45.310 error Caught by controller[2]: ^ host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[2]: var yahkaAdapter = new hkAdapter.TIOBrokerAdapter(utils.adapter({ name: 'yahka', systemConfig: true }), utils.controllerDir); host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[2]: /opt/iobroker/node_modules/iobroker.yahka/main.js:5 host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[1]: *** WARNING *** For more information see host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[1]: *** WARNING *** Please fix your application to use the native API of Avahi! host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[1]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[1]: *** WARNING *** For more information see host.sd-pi 2018-01-27 23:17:45.309 error Caught by controller[1]: *** WARNING *** Please fix your application to use the native API of Avahi! host.sd-pi 2018-01-27 23:17:45.306 error Caught by controller[0]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. host.sd-pi 2018-01-27 23:17:44.449 info instance system.adapter.yahka.0 started with pid 30758 !

                            Jetzt bin ich wieder zurück auf 0.5.5. Alle Einstellungen trotzdem leider weg. Ich habe vorher mit ioBroker backup ein Backup erstellt und konnte daher mit ioBroker restore 0 die Daten wiederherstellen. ABER:

                            Jetzt ist der yahka-Adapter trotzdem kaputt. Alles andere funktioniert wieder/weiterhin, nur yahka nicht. Fehlermeldung sieht übel aus:

                            ! ` > host.sd-pi 2018-01-27 23:32:44.415 error instance system.adapter.yahka.0 terminated with code 0 (OK)

                            Caught 2018-01-27 23:32:44.415 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"optio

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.ya

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 4

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket calling ack 2 with [null,"system.adapter.yahka.0.alive"]

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser decoded 32[null,"system.adapter.yahka.0.alive"] as {"type":3,"nsp":"/","id":2,"data":[null,"system.adapter.yahka.0.alive"]}

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT engine.io-client:socket socket receive: type "message", data "32[null,"system.adapter.yahka.0.alive"]"

                            Caught 2018-01-27 23:32:44.414 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getStates",["system.adapter.admin.0.logging"]],"options":{"compress":true},"id":3,"nsp":"/"} as 23["getSt

                            Caught 2018-01-27 23:32:44.413 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getStates",["system.adapter.admin.0.logging"]],"options":{"compress":true},"id":3,"nsp":"/"}

                            Caught 2018-01-27 23:32:44.413 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getStates",["system.adapter.admin.0.logging"]],"options":{"compress":true},"id":3,"nsp":"/

                            Caught 2018-01-27 23:32:44.413 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 3

                            Caught 2018-01-27 23:32:44.413 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket calling ack 1 with [null,["system.adapter.admin.0.logging"]]

                            Caught 2018-01-27 23:32:44.413 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser decoded 31[null,["system.adapter.admin.0.logging"]] as {"type":3,"nsp":"/","id":1,"data":[null,["system.adapter.admin.0.logging"]]}

                            Caught 2018-01-27 23:32:44.413 error by controller[173]: Sat, 27 Jan 2018 22:32:44 GMT engine.io-client:socket socket receive: type "message", data "31[null,["system.adapter.admin.0.logging"]]"

                            Caught 2018-01-27 23:32:44.412 error by controller[172]: Sat, 27 Jan 2018 22:32:44 GMT engine.io-client:socket flushing 35 packets in socket

                            Caught 2018-01-27 23:32:44.412 error by controller[171]: Sat, 27 Jan 2018 22:32:44 GMT engine.io-client:socket flushing 11 packets in socket

                            Caught 2018-01-27 23:32:44.412 error by controller[170]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"optio

                            Caught 2018-01-27 23:32:44.412 error by controller[170]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}

                            Caught 2018-01-27 23:32:44.412 error by controller[170]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.ya

                            Caught 2018-01-27 23:32:44.411 error by controller[169]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 2

                            Caught 2018-01-27 23:32:44.411 error by controller[168]: at EventedHTTPServer. (/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/lib/util/eventedhttp.js:65:10) errorCode: -65537 }

                            Caught 2018-01-27 23:32:44.411 error by controller[168]: at EventedHTTPServer.emit (events.js:211:7)

                            Caught 2018-01-27 23:32:44.411 error by controller[168]: at emitOne (events.js:116:13)

                            Caught 2018-01-27 23:32:44.411 error by controller[168]: at HAPServer._onListening (/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/lib/HAPServer.js:190:8)

                            Caught 2018-01-27 23:32:44.411 error by controller[168]: at HAPServer.emit (events.js:211:7)

                            Caught 2018-01-27 23:32:44.410 error by controller[168]: at emitOne (events.js:116:13)

                            Caught 2018-01-27 23:32:44.410 error by controller[168]: at Bridge.Accessory._onListening (/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/lib/Accessory.js:661:20)

                            Caught 2018-01-27 23:32:44.410 error by controller[168]: at Advertiser.startAdvertising (/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/lib/Advertiser.js:47:30)

                            Caught 2018-01-27 23:32:44.410 error by controller[168]: at Object.create [as createAdvertisement] (/opt/iobroker/node_modules/iobroker.yahka/node_modules/mdns/lib/advertisement.js:64:10)

                            Caught 2018-01-27 23:32:44.410 error by controller[168]: at new Advertisement (/opt/iobroker/node_modules/iobroker.yahka/node_modules/mdns/lib/advertisement.js:56:10)

                            Caught 2018-01-27 23:32:44.410 error by controller[168]: { Error: dns service error: unknown

                            Caught 2018-01-27 23:32:44.410 error by controller[167]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","yahka.0.checkLogging",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","yahka.0.

                            Caught 2018-01-27 23:32:44.409 error by controller[167]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","yahka.0.checkLogging",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.409 error by controller[166]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","yahka.0.checkLogging",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.409 error by controller[165]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.409 error by controller[165]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.409 error by controller[165]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.408 error by controller[164]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.408 error by controller[164]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.407 error by controller[164]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.407 error by controller[163]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 18

                            Caught 2018-01-27 23:32:44.407 error by controller[162]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.407 error by controller[162]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.407 error by controller[162]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.406 error by controller[161]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.406 error by controller[161]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.406 error by controller[161]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.406 error by controller[160]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 17

                            Caught 2018-01-27 23:32:44.406 error by controller[159]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.405 error by controller[159]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.405 error by controller[159]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.405 error by controller[158]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.405 error by controller[158]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.405 error by controller[158]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.404 error by controller[157]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 16

                            Caught 2018-01-27 23:32:44.404 error by controller[156]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.404 error by controller[155]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.404 error by controller[155]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.404 error by controller[155]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.403 error by controller[154]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.403 error by controller[154]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.403 error by controller[154]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 15

                            Caught 2018-01-27 23:32:44.403 error by controller[153]: HAP Warning: Characteristic 0000006D-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000080-0000-1000-8000-0026BB765291. Adding anyway.

                            Caught 2018-01-27 23:32:44.402 error by controller[152]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.402 error by controller[152]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.402 error by controller[152]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.402 error by controller[151]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.402 error by controller[151]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.401 error by controller[151]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.401 error by controller[150]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 14

                            Caught 2018-01-27 23:32:44.401 error by controller[149]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.401 error by controller[149]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.401 error by controller[149]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.401 error by controller[148]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.400 error by controller[148]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.400 error by controller[148]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.400 error by controller[147]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 13

                            Caught 2018-01-27 23:32:44.400 error by controller[146]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.400 error by controller[146]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.399 error by controller[145]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.399 error by controller[145]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.399 error by controller[145]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.399 error by controller[144]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.399 error by controller[144]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 12

                            Caught 2018-01-27 23:32:44.398 error by controller[143]: HAP Warning: Characteristic 0000006D-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000080-0000-1000-8000-0026BB765291. Adding anyway.

                            Caught 2018-01-27 23:32:44.398 error by controller[142]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.398 error by controller[142]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.398 error by controller[142]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.398 error by controller[141]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.397 error by controller[141]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.397 error by controller[141]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.397 error by controller[140]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 11

                            Caught 2018-01-27 23:32:44.397 error by controller[139]: HAP Warning: Characteristic 0000006D-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000080-0000-1000-8000-0026BB765291. Adding anyway.

                            Caught 2018-01-27 23:32:44.397 error by controller[138]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.396 error by controller[138]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.396 error by controller[138]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.396 error by controller[137]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.396 error by controller[137]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.396 error by controller[137]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.395 error by controller[136]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 10

                            Caught 2018-01-27 23:32:44.395 error by controller[135]: HAP Warning: Characteristic 0000006D-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000080-0000-1000-8000-0026BB765291. Adding anyway.

                            Caught 2018-01-27 23:32:44.395 error by controller[134]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.395 error by controller[134]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.394 error by controller[134]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.394 error by controller[133]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya

                            Caught 2018-01-27 23:32:44.394 error by controller[133]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"n

                            Caught 2018-01-27 23:32:44.394 error by controller[133]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.

                            Caught 2018-01-27 23:32:44.394 error by controller[132]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:socket emitting packet with ack id 9

                            Caught 2018-01-27 23:32:44.393 error by controller[131]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"} as 2["subscribe","system.adapt

                            Caught 2018-01-27 23:32:44.393 error by controller[131]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoding packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.393 error by controller[131]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-client:manager writing packet {"type":2,"data":["subscribe","system.adapter.*",null],"options":{"compress":true},"nsp":"/"}

                            Caught 2018-01-27 23:32:44.393 error by controller[131]: Sat, 27 Jan 2018 22:32:44 GMT socket.io-parser encoded {"type":2,"data":["getObjectView","system","instance",{"startkey":"system.adapter.","endkey":"system.adapter.香"},{"name":"ya `

                            Jemand noch einen Vorschlag? Auch Reboot des Raspberry hat nichts geändert.

                            Viele Grüße

                            Daniel

                            PS. einmal mehr, never change a running system :roll:

                            1 Reply Last reply Reply Quote 0
                            • M
                              Monox last edited by

                              bei mir funktioniert die 0.60.0 und 0.60.1 auch nicht, allerdings kann ich ohne Problem zurück zur 0.5.5..

                              direkt beim update findet sich folgendes bei mir im log..

                              ! 2018-01-28 12:59:12.463 - info: iobroker upgrade yahka
                              ! 2018-01-28 12:59:15.106 - info: iobroker Update yahka from @0.5.5 to @0.6.1
                              ! 2018-01-28 12:59:15.111 - info: iobroker npm install iobroker.yahka@0.6.1 –production --prefix "/opt/iobroker" (System call)
                              ! 2018-01-28 12:59:24.474 - error: yahka.0 uncaught exception: dns service error: unknown
                              ! 2018-01-28 12:59:24.489 - error: yahka.0 Error: dns service error: unknown
                              ! at Advertisement.on_service_registered (/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/node_modules/mdns/lib/advertisement.js:42:24)
                              ! at SocketWatcher.MDNSService.self.watcher.callback (/opt/iobroker/node_modules/iobroker.yahka/node_modules/hap-nodejs/node_modules/mdns/lib/mdns_service.js:18:40)
                              ! 2018-01-28 12:59:24.493 - info: yahka.0 cleaned everything up...
                              ! 2018-01-28 12:59:24.529 - info: yahka.0 terminating
                              ! 2018-01-28 12:59:24.601 - error: host.iobroker instance system.adapter.yahka.0 terminated with code 0 (OK)
                              ! 2018-01-28 12:59:24.602 - info: host.iobroker Restart adapter system.adapter.yahka.0 because enabled
                              ! 2018-01-28 12:59:54.633 - info: host.iobroker instance system.adapter.yahka.0 started with pid 25147
                              ! 2018-01-28 12:59:55.501 - error: host.iobroker instance system.adapter.yahka.0 terminated with code 1 ()
                              ! 2018-01-28 12:59:55.502 - info: host.iobroker Restart adapter system.adapter.yahka.0 because enabled

                              nach dem Update von avahi-daemon avahi-discover libnss-mdns sieht es so aus…..

                              ! 2018-01-28 13:33:07.069 - info: iobroker upgrade yahka
                              ! 2018-01-28 13:33:09.882 - info: iobroker Update yahka from @0.5.5 to @0.6.1
                              ! 2018-01-28 13:33:09.889 - info: iobroker npm install iobroker.yahka@0.6.1 –production --prefix "/opt/iobroker" (System call)
                              ! 2018-01-28 13:35:19.025 - info: iobroker npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.yahka"
                              ! 2018-01-28 13:35:22.142 - info: iobroker got /opt/iobroker/node_modules/iobroker.yahka/admin
                              ! 2018-01-28 13:35:22.168 - info: iobroker upload [18] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/yahka.png yahka.png image/png
                              ! 2018-01-28 13:35:22.193 - info: yahka.0 objectChange system.adapter.yahka {"_id":"system.adapter.yahka","type":"adapter","common":{"name":"yahka","version":"0.6.1","news":{"0.6.1":{"en":"Fixed a bug which prevent Yahka from Start","de":"Fixed a bug which prevent Yahka from Start","ru":"Fixed a bug which prevent Yahka from Start"},"0.6.0":{"en":"Support for IP-Cameras","de":"Support für IP-Kameras","ru":"Поддержка IP-Камер"},"0.5.5":{"en":"Make a config dialog bigger","de":"Config-Dialog ist vergrößert","ru":"Увеличен размер окна настроек"}},"title":"Homekit yahka adapter","desc":{"en":"ioBroker yet another homekit adapter","de":"ioBroker yet another homekit adapter","ru":"ioBroker Homekit адаптер"},"platform":"Javascript/Node.js","mode":"daemon","icon":"yahka.png","enabled":true,"extIcon":"<url url="https://raw.githubusercontent.com/jensweigele/ioBroker.yahka/master/admin/yahka.png","keywords"}],"installedVersion":"0.6.1"},"native":{"firstTimeInitialized":false,"bridge":{"devices":[]}},"from":"system.host.iobroker.cli","ts":1517142922121}
                              ! 2018-01-28 13:35:22.299 - info: iobroker Update "system.adapter.yahka.0"upload [17] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/yahka.admin.js.map yahka.admin.js.map application/json
                              ! 2018-01-28 13:35:22.331 - info: host.iobroker object change system.adapter.yahka.0
                              ! 2018-01-28 13:35:22.339 - info: yahka.0 cleaned everything up…
                              ! 2018-01-28 13:35:22.335 - info: host.iobroker stopInstance system.adapter.yahka.0
                              ! 2018-01-28 13:35:22.335 - info: host.iobroker stopInstance system.adapter.yahka.0 killing pid 2758
                              ! 2018-01-28 13:35:22.360 - info: yahka.0 terminating
                              ! 2018-01-28 13:35:22.420 - info: host.iobroker instance system.adapter.yahka.0 terminated with code 0 (OK)
                              ! 2018-01-28 13:35:22.428 - info: iobroker upload [16] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/yahka.admin.js yahka.admin.js application/javascript
                              ! 2018-01-28 13:35:22.528 - info: iobroker upload [15] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/words.js words.js application/javascript
                              ! 2018-01-28 13:35:22.595 - info: iobroker upload [14] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/index.html index.html text/html
                              ! 2018-01-28 13:35:22.666 - info: iobroker upload [13] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/home_icon_large.png home_icon_large.png image/png
                              ! 2018-01-28 13:35:22.730 - info: iobroker upload [12] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/js/metro.min.js ext/metroui/js/metro.min.js application/javascript
                              ! 2018-01-28 13:35:22.839 - info: iobroker upload [11] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/selection.json ext/metroui/fonts/selection.json application/json
                              ! 2018-01-28 13:35:23.177 - info: iobroker upload [10] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.woff ext/metroui/fonts/metro.woff font/woff
                              ! 2018-01-28 13:35:23.313 - info: iobroker upload [9] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.ttf ext/metroui/fonts/metro.ttf font/ttf
                              ! 2018-01-28 13:35:23.463 - info: iobroker upload [8] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.svg ext/metroui/fonts/metro.svg image/svg+xml
                              ! 2018-01-28 13:35:23.777 - info: iobroker upload [7] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.eot ext/metroui/fonts/metro.eot application/vnd.ms-fontobject
                              ! 2018-01-28 13:35:23.879 - info: iobroker upload [6] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro.min.css ext/metroui/css/metro.min.css text/css
                              ! 2018-01-28 13:35:23.986 - info: iobroker upload [5] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-schemes.min.css ext/metroui/css/metro-schemes.min.css text/css
                              ! 2018-01-28 13:35:24.054 - info: iobroker upload [4] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-rtl.min.css ext/metroui/css/metro-rtl.min.css text/css
                              ! 2018-01-28 13:35:24.116 - info: iobroker upload [3] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-responsive.min.css ext/metroui/css/metro-responsive.min.css text/css
                              ! 2018-01-28 13:35:24.178 - info: iobroker upload [2] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-icons.min.css ext/metroui/css/metro-icons.min.css text/css
                              ! 2018-01-28 13:35:24.246 - info: iobroker upload [1] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-colors.min.css ext/metroui/css/metro-colors.min.css text/css
                              ! 2018-01-28 13:35:24.314 - info: iobroker upload [0] yahka.admin /opt/iobroker/node_modules/iobroker.yahka/admin/css/yahka.admin.css css/yahka.admin.css text/css
                              ! 2018-01-28 13:35:24.388 - info: iobroker Adapter "yahka" updated
                              ! 2018-01-28 13:35:24.433 - info: iobroker exit 0
                              ! 2018-01-28 13:35:24.894 - info: host.iobroker instance system.adapter.yahka.0 started with pid 7125
                              ! 2018-01-28 13:35:26.080 - error: host.iobroker instance system.adapter.yahka.0 terminated with code 1 ()
                              ! 2018-01-28 13:35:26.081 - info: host.iobroker Restart adapter system.adapter.yahka.0 because enabled
                              Grüße Monox

                              1 Reply Last reply Reply Quote 0
                              • D
                                danny030 last edited by

                                Ich hab immerhin die 0.5.5 auch wieder zum Laufen gebracht. Musste alles, was ich in der /etc/avahi/avahi-daemon.conf geändert habe (also entfernen der Kommentare) wieder auskommentieren und den Ursprungszustand herstellen. Dann ging auch die 0.5.5 wieder.

                                Würde natürlich trotzdem gerne die aktuelle Version verwenden, wenn also jemand noch einen Tipp dazu hat, wäre ich dankbar.

                                Viele Grüße

                                Danny

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

                                  Hallo zusammen,

                                  ich habe in den letzten Tagen mit dem Adapter ein wenig rumgespielt und soweit klappt es auch (bis auf sehr viele Fehler beim Speichern der Instanz). Aber anschließend funktioniert trotz der Fehler soweit alles.

                                  Allerdings habe ich es noch nicht hinbekommen, den State CurrentSecuritySystemState zu verwenden. Ich habe einen State angelegt, um die 5 States zu speichern (0-4). Also ein State als Integer/Number.

                                  Das Problem ist, dass das Lesen des States problemlos klappt und eine Änderung im ioBroker sofort in Homekit übernommen wird.

                                  Wenn ich jedoch in Homekit versuche den Status zu ändern, sagt Homekit dauerhaft nur "Aktualisieren" und im ioBroker ändert sich leider nichts.

                                  Fehlt hier vielleicht noch eine Implementierung?

                                  Grüße,

                                  Jan

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

                                    Was sind denn die Ausgaben wenn du auf Debug stellst?

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

                                      Hi,

                                      das Problem hat sich gerade erledigt.

                                      Über den Homekit Developer Simulator konnte ich gerade erkennen, dass folgendes passiert:

                                      SecuritySystemCurrentState: Wenn sich dieser Status ändert, wird der Status an Homekit übermittelt.

                                      SecuritySystemTargetState: Dieser Status wird von Homekit versendet und erwartet entsprechend die Bestätigung durch den CurrentState.

                                      Daher: Ich habe nun den State im ioBroker als Current und Target gesetzt und schon funktioniert es prima.

                                      Gruß Jan

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        captaindork last edited by

                                        Hi zusammen,

                                        Ich wollte grade mal versuchen meine Bewässerung von Switch auf die neuen Valves/Faucets von 0.7.0 umzustellen (Danke @JW).

                                        Leider tauchen diese bei den Servicetypen im Dropdown aber garnicht auf. Muss ich da unter der Haube noch was tun? Ein Update von hap-nodejs oder sowas? Sorry, bin lost…

                                        Thx

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

                                          Versuch mal ein „iobroker yahka upload“ und dann den Adapter neu starten.

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            captaindork last edited by

                                            …danke!!! der wars!

                                            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

                                            450
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            204
                                            1745
                                            599371
                                            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