Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [Yeelight-2 Adapter] Rebuild Version 0.9.X

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    [Yeelight-2 Adapter] Rebuild Version 0.9.X

    This topic has been deleted. Only users with topic management privileges can see it.
    • simatec
      simatec Developer Most Active last edited by

      So habe gerade mal die Version 0.9.4 installiert.

      Bei mir mussten alle Objekte und auch die einzelnen Lampen in der config gelöscht werden und komplett neu eingerichtet werden.

      Dabei hat "Find" 5 von 6 Leuchten gefunden.

      Die 6. musste ich manuell anlegen.

      Danke für deine Mühe und klasse Arbeit 😉

      1 Reply Last reply Reply Quote 0
      • Meistertr
        Meistertr Developer last edited by

        Ja das ist richtig l, hatte ich oben ja auch geschrieben, dass durch den rebuild alles einmal gelöscht werden muss.

        Bei mir half ein zweites Mal suchen um auch die letzte Lampe zu finden. Im Gegensatz zu früher werden nun auch nur neue Lampen zur Tabelle hinzugefügt und nicht alle egal ob schon drin..

        Gesendet von meinem Handy

        1 Reply Last reply Reply Quote 0
        • K
          K-L-S last edited by

          Hallo Meistertr,

          ich habe eine Frage zur zusätzlichen Adapternamen Versionierung(Yeelight-2.0 bzw.Yeelight-2.1 in den Instanzen). Ist dies unbedingt notwendig? Bei mir und wahrscheinlich bei vielen anderen bedeutet dies das alle Skripte die zur Lampensteuerung eingesetzt werden angepasst werden müssen.

          Klaus

          1 Reply Last reply Reply Quote 0
          • simatec
            simatec Developer Most Active last edited by

            Perfekt … ich bin gespannt, ob der Adapter nin die Lampen auch nach einen Neustart wieder findet [emoji51]

            Gesendet von iPhone mit Tapatalk

            1 Reply Last reply Reply Quote 0
            • K
              K-L-S last edited by

              @Meistertr:

              @Itsalvatore https://github.com/ioBroker/ioBroker.vis-colorpicker

              @K-L-S fehler in 0.9.4 behoben `

              Es ging um einen Fehler in der vorherigen Adapter-Version 2.0. Ich habe eine selbsterstellte VIS und wenn ich diese refresh hatte ging die Color-Bulk automatisch an.

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

                Hab nur noch n Yeelight-Stripe, die Yeelight Bulbs hatte ich vor ein paar Monaten in die Tonne gehauen, weil se sich immer aufgehängt hatten.. war nach n Firmware-Update, hatte auch nichts mit iobroker/controller zu tun, auch mein Stripe muss ich seitdem immer einmal am Tag power resetten, dann läufts wieder.. hab einfach n Sonoff Basic davor gemacht, der mittags mal ausschaltet.

                war soweit mit dem alten Adapter zufrieden, hatte vorher ein javascript, mit dem ich die Lampen steuerte ( hatte ich auch mal hier aus dem Forum)

                Hab also Instanz und Adapter gelöscht, neu installiert, das Stripe hat er auf Anhieb gefunden, habe den Smartname eingetragen, läuft sofort auch mit der Tante, farben stimmen, alles gut. Top!! Sogar in Material wird es richtig angezeigt und ist steuerbar, Klasse! DANKE!

                Was ich super finde, es werden sogar jetzt die Szenen aus der App eingelesen, allerdings passiert nichts, wenn ich den Button drücke…?
                6359_3e6619bc-96f5-4380-b9f0-27cdd34fd68b.png

                1 Reply Last reply Reply Quote 0
                • R
                  RichieXX last edited by

                  Hab die 0.9.4 installiert. Leider funktionieren die Szenen nicht mehr, die in der 0.4.1 noch funktioniert hatten.

                  1 Reply Last reply Reply Quote 0
                  • K
                    K-L-S last edited by

                    @K-L-S:

                    Hallo Meistertr,

                    ich habe eine Frage zur zusätzlichen Adapternamen Versionierung(Yeelight-2.0 bzw.Yeelight-2.1 in den Instanzen). Ist dies unbedingt notwendig? Bei mir und wahrscheinlich bei vielen anderen bedeutet dies das alle Skripte die zur Lampensteuerung eingesetzt werden angepasst werden müssen.

                    Klaus `

                    Sorry ist meiner Unkenntnis geschuldet. Habe nun gesehen wenn eine neue Instanz hinzugefügt wird erhöht sich jeweils die Nummer.

                    1 Reply Last reply Reply Quote 0
                    • simatec
                      simatec Developer Most Active last edited by

                      Hallo,

                      bei mir stürzt die Version 0.9.4 immer wieder ab.

                      Ich schalte mehrere Lampen (3 Stück) gleichzeitig und nach 1-2 Farbwechseln oder Schaltvorgängen stürzt der Adapter mit dem Log ab.

                      Danach reagieren die Lampen erstmal nicht mehr auf Befehle.

                      Nehme ich Lampen die einzeln geschalten werden, tritt der Fehler nach ersten Tests nicht auf.

                      Hier kann ich schnell zwischen Farben und Szenen wechseln, ohne das der Adapter abstürzt.

                      In der Gruppe sind zwei Bulb und ein LED Stripe

                       host.tinkerboard	2018-11-19 20:45:19.460	info	instance system.adapter.yeelight-2.0 started with pid 16046
host.tinkerboard	2018-11-19 20:45:16.984	info	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-19 20:45:16.927	info	stopInstance system.adapter.yeelight-2.0 killing pid 16011
host.tinkerboard	2018-11-19 20:45:16.927	info	stopInstance system.adapter.yeelight-2.0
host.tinkerboard	2018-11-19 20:45:16.926	info	object change system.adapter.yeelight-2.0
backitup.0	2018-11-19 20:44:57.621	debug	system.adapter.admin.0: logging true
backitup.0	2018-11-19 20:44:57.620	debug	redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1542656697616,"q":0,"from":"system.adapter.admin.0","lc":1542656697616}
host.tinkerboard	2018-11-19 20:44:55.784	info	instance system.adapter.yeelight-2.0 started with pid 16011
host.tinkerboard	2018-11-19 20:44:25.759	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-19 20:44:25.759	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at TCP.onread (net.js:601:20)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at Socket.emit (events.js:211:7)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at emitOne (events.js:116:13)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
Caught	2018-11-19 20:44:25.759	error	by controller[2]: at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17)
Caught	2018-11-19 20:44:25.758	error	by controller[2]: at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:61:45
Caught	2018-11-19 20:44:25.758	error	by controller[2]: TypeError: Cannot read property 'val' of null
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at TCP.onread (net.js:601:20)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at Socket.emit (events.js:211:7)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at emitOne (events.js:116:13)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17)
Caught	2018-11-19 20:44:25.758	error	by controller[1]: at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:61:45
Caught	2018-11-19 20:44:25.758	error	by controller[1]: TypeError: Cannot read property 'val' of null
Caught	2018-11-19 20:44:25.758	error	by controller[0]: at TCP.onread (net.js:601:20)
Caught	2018-11-19 20:44:25.758	error	by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at Socket.emit (events.js:211:7)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at emitOne (events.js:116:13)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17)
Caught	2018-11-19 20:44:25.757	error	by controller[0]: at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:61:45
Caught	2018-11-19 20:44:25.757	error	by controller[0]: TypeError: Cannot read property 'val' of null
yeelight-2.0	2018-11-19 20:44:25.731	error	at TCP.onread (net.js:601:20)
yeelight-2.0	2018-11-19 20:44:25.731	error	at Socket.Readable.push (_stream_readable.js:208:10)
yeelight-2.0	2018-11-19 20:44:25.731	error	at readableAddChunk (_stream_readable.js:250:11)
yeelight-2.0	2018-11-19 20:44:25.731	error	at addChunk (_stream_readable.js:263:12)
yeelight-2.0	2018-11-19 20:44:25.731	error	at Socket.emit (events.js:211:7)
yeelight-2.0	2018-11-19 20:44:25.731	error	at emitOne (events.js:116:13)
yeelight-2.0	2018-11-19 20:44:25.731	error	at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27)
yeelight-2.0	2018-11-19 20:44:25.731	error	at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
yeelight-2.0	2018-11-19 20:44:25.731	error	at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
yeelight-2.0	2018-11-19 20:44:25.731	error	at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
yeelight-2.0	2018-11-19 20:44:25.731	error	at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
yeelight-2.0	2018-11-19 20:44:25.731	error	at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17)
yeelight-2.0	2018-11-19 20:44:25.731	error	at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:61:45
yeelight-2.0	2018-11-19 20:44:25.731	error	TypeError: Cannot read property 'val' of null
yeelight-2.0	2018-11-19 20:44:25.731	error	uncaught exception: Cannot read property 'val' of null
yeelight-2.0	2018-11-19 20:44:25.726	error	at TCP.onread (net.js:601:20)
yeelight-2.0	2018-11-19 20:44:25.726	error	at Socket.Readable.push (_stream_readable.js:208:10)
yeelight-2.0	2018-11-19 20:44:25.726	error	at readableAddChunk (_stream_readable.js:250:11)
yeelight-2.0	2018-11-19 20:44:25.726	error	at addChunk (_stream_readable.js:263:12)
yeelight-2.0	2018-11-19 20:44:25.726	error	at Socket.emit (events.js:211:7)
yeelight-2.0	2018-11-19 20:44:25.726	error	at emitOne (events.js:116:13)
yeelight-2.0	2018-11-19 20:44:25.726	error	at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27)
yeelight-2.0	2018-11-19 20:44:25.726	error	at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
yeelight-2.0	2018-11-19 20:44:25.726	error	at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
yeelight-2.0	2018-11-19 20:44:25.726	error	at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
yeelight-2.0	2018-11-19 20:44:25.726	error	at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
yeelight-2.0	2018-11-19 20:44:25.726	error	at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17)
yeelight-2.0	2018-11-19 20:44:25.726	error	at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:61:45
yeelight-2.0	2018-11-19 20:44:25.726	error	TypeError: Cannot read property 'val' of null
yeelight-2.0	2018-11-19 20:44:25.726	error	uncaught exception: Cannot read property 'val' of null
yeelight-2.0	2018-11-19 20:44:25.723	error	at TCP.onread (net.js:601:20)
yeelight-2.0	2018-11-19 20:44:25.723	error	at Socket.Readable.push (_stream_readable.js:208:10)
yeelight-2.0	2018-11-19 20:44:25.723	error	at readableAddChunk (_stream_readable.js:250:11)
yeelight-2.0	2018-11-19 20:44:25.723	error	at addChunk (_stream_readable.js:263:12)
yeelight-2.0	2018-11-19 20:44:25.723	error	at Socket.emit (events.js:211:7)
yeelight-2.0	2018-11-19 20:44:25.723	error	at emitOne (events.js:116:13)
yeelight-2.0	2018-11-19 20:44:25.723	error	at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27)
yeelight-2.0	2018-11-19 20:44:25.723	error	at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
yeelight-2.0	2018-11-19 20:44:25.723	error	at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
yeelight-2.0	2018-11-19 20:44:25.723	error	at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
yeelight-2.0	2018-11-19 20:44:25.723	error	at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
yeelight-2.0	2018-11-19 20:44:25.723	error	at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17)
yeelight-2.0	2018-11-19 20:44:25.723	error	at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:61:45
yeelight-2.0	2018-11-19 20:44:25.723	error	TypeError: Cannot read property 'val' of null
yeelight-2.0	2018-11-19 20:44:25.719	error	uncaught exception: Cannot read property 'val' of null</anonymous></anonymous></anonymous></anonymous></anonymous></anonymous>

                      Gesendet von iPhone mit Tapatalk

                      1 Reply Last reply Reply Quote 0
                      • B
                        Bielefelder81 last edited by

                        Mensch, da packt man sich an den Kopf.

                        Da denkt man nichts böses, installiert das neue Update und dann geht gar nichts mehr.

                        • Lampen werden doppelt angelegt, also muss man das alte Löschen…

                        Ok, kein Problem, aber ich muss alle Scripte umschreiben, dadurch darf ich alle Gruppen und Routinen umschreiben.

                        • Auf einmal kann man nicht mehr über Active_Bright bzw Color Temperature die Lampe anschalten. Nein, man muss zwingend nun auch Power auf True vorher setzen.

                        • RGB Werte werden nicht mehr mit #ff0000 oder so angezeigt sondern, irgendeine 7-stellige Nummer.

                        • Wenn ich nun versuche alles wieder gerade zu biegen, dann kommt folgende Fehlermeldung:

                        uncaught exception: id is not defined

                        ReferenceError: id is not defined
                        1 Reply Last reply Reply Quote 0
                        • Meistertr
                          Meistertr Developer last edited by

                          @Bielefelder81:

                          Mensch, da packt man sich an den Kopf.

                          Da denkt man nichts böses, installiert das neue Update und dann geht gar nichts mehr.

                          • Lampen werden doppelt angelegt, also muss man das alte Löschen…

                          Ok, kein Problem, aber ich muss alle Scripte umschreiben, dadurch darf ich alle Gruppen und Routinen umschreiben.

                          • Auf einmal kann man nicht mehr über Active_Bright bzw Color Temperature die Lampe anschalten. Nein, man muss zwingend nun auch Power auf True vorher setzen.

                          • RGB Werte werden nicht mehr mit #ff0000 oder so angezeigt sondern, irgendeine 7-stellige Nummer.

                          • Wenn ich nun versuche alles wieder gerade zu biegen, dann kommt folgende Fehlermeldung:

                          uncaught exception: id is not defined

                          ReferenceError: id is not defined
```` `

                          -Der Adapter muss zwingen neu Installiert werden, das heißt alle Objekte Löschen und neu die Geräte in der Config neu anlegen. Das steht aber auch in der Readme. da es sich im einen rebuild handelt und auch die Config geändert wurde.

                          • Wenn du die Lampen so benennst wie sie vorher hießen, brauchst du nix ändern.

                          -Die werte werden wie zuvor als Hex eingegeben, die Dezimalzahl ist mir gestern selbst aufgefallen, da ist noch ein Umrechnungsfehler.

                          -id not deined ist dem nicht ordnungsgemäßen löschen geschuldet.

                          Dem einschalten bei Helligkeit oder rgb oder ct muss ich mir nochmal durch den kopf gehen lassen und die vor und nachteile abwägen, der rest sollte bis heute abend gefixed sein

                          1 Reply Last reply Reply Quote 0
                          • B
                            Bielefelder81 last edited by

                            Ich hatte, nachdem es nicht funktionierte und als ich sah dass der Name doppelt angelegt wurde, den Adapter und die Objekte gelöscht und neu installiert.

                            Habe dann einfach wieder downgegraded und es funktionierte auf Anhieb…

                            1 Reply Last reply Reply Quote 0
                            • Meistertr
                              Meistertr Developer last edited by

                              habe gerade die 0.9.5 hochgeladen:

                              • scenen funktionieren wieder

                              • RGB wert wird richtig eingetragen

                              • undefined val beim schnellen senden sollte nun behoben sein (@simatec bitte testen)

                              1 Reply Last reply Reply Quote 0
                              • simatec
                                simatec Developer Most Active last edited by

                                Habs gleich getestet …

                                Bei meiner Gruppe mit 3 Lampen über Alexa und Homekit noch immer das selbe Problem ... Leider.

                                Anbei der Log.

                                Eventuell hilft er dir bei der Fehlersuche.

                                host.tinkerboard	2018-11-20 20:40:48.304	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: ReferenceError: id is not defined
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: ReferenceError: id is not defined
yeelight-2.0	2018-11-20 20:40:48.275	error	ReferenceError: id is not defined at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28) at emitOne (events.js:116:13) at Socket.emit (events.js:211
yeelight-2.0	2018-11-20 20:40:48.275	error	uncaught exception: id is not defined
yeelight-2.0	2018-11-20 20:40:48.275	error	ReferenceError: id is not defined at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28) at emitOne (events.js:116:13) at Socket.emit (events.js:211
yeelight-2.0	2018-11-20 20:40:48.274	error	uncaught exception: id is not defined
host.tinkerboard	2018-11-20 20:40:08.928	info	instance system.adapter.yeelight-2.0 started with pid 13665
host.tinkerboard	2018-11-20 20:40:08.205	info	instance system.adapter.dwd.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-20 20:40:00.042	info	instance system.adapter.dwd.0 started with pid 13626
host.tinkerboard	2018-11-20 20:39:38.907	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-20 20:39:38.907	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-20 20:39:38.907	error	Caught by controller[1]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:39:38.907	error	Caught by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:39:38.907	error	Caught by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: ReferenceError: id is not defined
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:39:38.905	error	Caught by controller[0]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:39:38.905	error	Caught by controller[0]: ReferenceError: id is not defined
host.tinkerboard	2018-11-20 20:39:28.364	info	instance system.adapter.yeelight-2.0 started with pid 13609
host.tinkerboard	2018-11-20 20:38:58.351	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-20 20:38:58.350	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at processImmediate (timers.js:745:5)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at tryOnImmediate (timers.js:768:5)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at runCallback (timers.js:810:20)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3429:38)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at Adapter.emit (events.js:214:7)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at emitTwo (events.js:126:13)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:66:21)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:129:33)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: TypeError: Cannot read property 'getYeelightById' of undefined
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at processImmediate [as _immediateCallback] (timers.js:745:5)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at tryOnImmediate (timers.js:768:5)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at runCallback (timers.js:810:20)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3429:38)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at Adapter.emit (events.js:214:7)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: at emitTwo (events.js:126:13)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:66:21)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:129:33)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: TypeError: Cannot read property 'getYeelightById' of undefined
Caught	2018-11-20 20:38:58.349	error	by controller[0]: at processImmediate [as _immediateCallback] (timers.js:745:5)
Caught	2018-11-20 20:38:58.349	error	by controller[0]: at tryOnImmediate (timers.js:768:5)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at runCallback (timers.js:810:20)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3429:38)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at Adapter.emit (events.js:214:7)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at emitTwo (events.js:126:13)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:66:21)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:129:33)
Caught	2018-11-20 20:38:58.346	error	by controller[0]: TypeError: Cannot read property 'getYeelightById' of undefined
yeelight-2.0	2018-11-20 20:38:58.311	error	uncaught exception: Cannot read property 'getYeelightById' of undefined
host.tinkerboard	2018-11-20 20:38:56.908	info	instance system.adapter.yeelight-2.0 started with pid 13566
host.tinkerboard	2018-11-20 20:38:26.883	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-20 20:38:26.883	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at TCP.onread (net.js:601:20)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at Socket.emit (events.js:211:7)
Caught	2018-11-20 20:38:26.882	error	by controller[2]: at emitOne (events.js:116:13)
Caught	2018-11-20 20:38:26.882	error	by controller[2]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
Caught	2018-11-20 20:38:26.882	error	by controller[2]: ReferenceError: id is not defined
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at TCP.onread (net.js:601:20)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at Socket.emit (events.js:211:7)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at emitOne (events.js:116:13)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: ReferenceError: id is not defined
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at TCP.onread (net.js:601:20)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at Socket.emit (events.js:211:7)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at emitOne (events.js:116:13)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
Caught	2018-11-20 20:38:26.881	error	by controller[0]: ReferenceError: id is not defined</anonymous></anonymous></anonymous>
                                1 Reply Last reply Reply Quote 0
                                • Meistertr
                                  Meistertr Developer last edited by

                                  @simatec:

                                  Habs gleich getestet …

                                  Bei meiner Gruppe mit 3 Lampen über Alexa und Homekit noch immer das selbe Problem ... Leider.

                                  Anbei der Log.

                                  Eventuell hilft er dir bei der Fehlersuche.

                                  host.tinkerboard	2018-11-20 20:40:48.304	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:40:48.304	error	Caught by controller[1]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[1]: ReferenceError: id is not defined
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:40:48.303	error	Caught by controller[0]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:40:48.302	error	Caught by controller[0]: ReferenceError: id is not defined
yeelight-2.0	2018-11-20 20:40:48.275	error	ReferenceError: id is not defined at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28) at emitOne (events.js:116:13) at Socket.emit (events.js:211
yeelight-2.0	2018-11-20 20:40:48.275	error	uncaught exception: id is not defined
yeelight-2.0	2018-11-20 20:40:48.275	error	ReferenceError: id is not defined at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28) at emitOne (events.js:116:13) at Socket.emit (events.js:211
yeelight-2.0	2018-11-20 20:40:48.274	error	uncaught exception: id is not defined
host.tinkerboard	2018-11-20 20:40:08.928	info	instance system.adapter.yeelight-2.0 started with pid 13665
host.tinkerboard	2018-11-20 20:40:08.205	info	instance system.adapter.dwd.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-20 20:40:00.042	info	instance system.adapter.dwd.0 started with pid 13626
host.tinkerboard	2018-11-20 20:39:38.907	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-20 20:39:38.907	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
host.tinkerboard	2018-11-20 20:39:38.907	error	Caught by controller[1]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:39:38.907	error	Caught by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:39:38.907	error	Caught by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[1]: ReferenceError: id is not defined
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at TCP.onread (net.js:601:20)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at addChunk (_stream_readable.js:263:12)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at Socket.emit (events.js:211:7)
host.tinkerboard	2018-11-20 20:39:38.906	error	Caught by controller[0]: at emitOne (events.js:116:13)
host.tinkerboard	2018-11-20 20:39:38.905	error	Caught by controller[0]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
host.tinkerboard	2018-11-20 20:39:38.905	error	Caught by controller[0]: ReferenceError: id is not defined
host.tinkerboard	2018-11-20 20:39:28.364	info	instance system.adapter.yeelight-2.0 started with pid 13609
host.tinkerboard	2018-11-20 20:38:58.351	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-20 20:38:58.350	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at processImmediate (timers.js:745:5)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at tryOnImmediate (timers.js:768:5)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at runCallback (timers.js:810:20)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3429:38)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at Adapter.emit (events.js:214:7)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at emitTwo (events.js:126:13)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:66:21)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:129:33)
Caught	2018-11-20 20:38:58.350	error	by controller[2]: TypeError: Cannot read property 'getYeelightById' of undefined
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at processImmediate [as _immediateCallback] (timers.js:745:5)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at tryOnImmediate (timers.js:768:5)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at runCallback (timers.js:810:20)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3429:38)
Caught	2018-11-20 20:38:58.350	error	by controller[1]: at Adapter.emit (events.js:214:7)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: at emitTwo (events.js:126:13)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:66:21)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:129:33)
Caught	2018-11-20 20:38:58.349	error	by controller[1]: TypeError: Cannot read property 'getYeelightById' of undefined
Caught	2018-11-20 20:38:58.349	error	by controller[0]: at processImmediate [as _immediateCallback] (timers.js:745:5)
Caught	2018-11-20 20:38:58.349	error	by controller[0]: at tryOnImmediate (timers.js:768:5)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at runCallback (timers.js:810:20)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3429:38)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at Adapter.emit (events.js:214:7)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at emitTwo (events.js:126:13)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:66:21)
Caught	2018-11-20 20:38:58.347	error	by controller[0]: at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:129:33)
Caught	2018-11-20 20:38:58.346	error	by controller[0]: TypeError: Cannot read property 'getYeelightById' of undefined
yeelight-2.0	2018-11-20 20:38:58.311	error	uncaught exception: Cannot read property 'getYeelightById' of undefined
host.tinkerboard	2018-11-20 20:38:56.908	info	instance system.adapter.yeelight-2.0 started with pid 13566
host.tinkerboard	2018-11-20 20:38:26.883	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.tinkerboard	2018-11-20 20:38:26.883	error	instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at TCP.onread (net.js:601:20)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-20 20:38:26.883	error	by controller[2]: at Socket.emit (events.js:211:7)
Caught	2018-11-20 20:38:26.882	error	by controller[2]: at emitOne (events.js:116:13)
Caught	2018-11-20 20:38:26.882	error	by controller[2]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
Caught	2018-11-20 20:38:26.882	error	by controller[2]: ReferenceError: id is not defined
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at TCP.onread (net.js:601:20)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at Socket.emit (events.js:211:7)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at emitOne (events.js:116:13)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
Caught	2018-11-20 20:38:26.882	error	by controller[1]: ReferenceError: id is not defined
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at TCP.onread (net.js:601:20)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at Socket.Readable.push (_stream_readable.js:208:10)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at readableAddChunk (_stream_readable.js:250:11)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at addChunk (_stream_readable.js:263:12)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at Socket.emit (events.js:211:7)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at emitOne (events.js:116:13)
Caught	2018-11-20 20:38:26.882	error	by controller[0]: at Yeelight.formatResponse (/opt/iobroker/node_modules/yeelight-wifi/build/Yeelight.js:288:28)
Caught	2018-11-20 20:38:26.881	error	by controller[0]: ReferenceError: id is not defined</anonymous></anonymous></anonymous>
```` `

                                  den Fehler habe ich gestern schon behoben.

                                  https://github.com/MeisterTR/yeelight-w … ht.js#L288

                                  am besten noch mal drüber installieren und neu starten, scheinbar hat er das repository nicht richtig nachgeladen

                                  1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active last edited by

                                    OK teste ich noch einmal.

                                    Hatte das Update direkt vom github gemacht auf Version 0.9.5.

                                    Gesendet von iPhone mit Tapatalk

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      smarti2015 last edited by

                                      Hab einfach nochmal neu installiert, die alten Daten gelöscht und Lampen neu gesucht. Danach lief wieder alles super. Vielen Dank für den Adapter, die viele Mühe und Weiterentwicklung 🙂

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

                                        Hallo,

                                        super, Version 0.9.5 funktioniert hier mit dem Stripe einwandfrei!

                                        Sogar die Scenen funktionieren, echt klasse!

                                        Der darf von meiner Seite aus als V1.0 raus ins stable. 🙂

                                        Frage, möchtest du dir den Wifilight-Adapter mal antun, der bräuchte auch eine überarbeitung, ab und zu hängt der sich auf und die Datenpunkte sind nicht Material/Alexa kompatibel … ?? 🙂

                                        1 Reply Last reply Reply Quote 0
                                        • simatec
                                          simatec Developer Most Active last edited by

                                          So habe den Adapter noch einmal komplett deinstalliert und neu aufgesetzt.

                                          Jetzt schein der Fehler weg zu sein.

                                          Konnte allerdings nur aus der Ferne testen.

                                          Werde heute Abend nochmal wild die Farben wechseln und schauen, ob der Adapter überlebt 😄

                                          1 Reply Last reply Reply Quote 0
                                          • E
                                            e-p-s last edited by

                                            Vielen Dank für deine Arbeit.

                                            Meine Konstellation läuft auch:

                                            -Schlauch Küche

                                            -2x Mono Esszimmer

                                            -3x Color Wohnzimmer

                                            -3x Color Kinderzimmer

                                            -1x Mono Kinderzimmer.

                                            Was jetzt noch cool wäre (Meine Kids lieben es), ist dieser Farbwechsler Modus. Wo die Lampen durch alle Farben durchwechseln.

                                            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

                                            479
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            21
                                            91
                                            8829
                                            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