iobroker-community-adapters / iobroker.yeelight-2 Goto Github PK
View Code? Open in Web Editor NEWControl your yeelights with ioBroker
License: MIT License
Control your yeelights with ioBroker
License: MIT License
https://github.com/MeisterTR/ioBroker.yeelight-2/blob/master/main.js#L1307
What the mode is that? RGB/Temperature? RGB/HUE? Or Dim/Color? .....
And may be change the role, else it cannot be separated from power with the same role.
Hi,
first of all I wann thank you for thins amazing Adapter for iobroker, it works very good with the most lamps.
I have 1 problem with my yeelight 650. I can't change the bg_rgb (see attachment). The value is adjustable but has no effect. When I change the color with my yeelight app, the values in iobroker change too, when i type in the value in "bg_rgb" it does not have any effect, even I don't get an error (log=debug).
Has somebody else the same problem? Or should i change the color in a special order?
regards
J
After upgrade to 0.9.5 I noticed that adapter does not reconnect to lamp after connection lost (e.g. wifi re-connection). Version 0.4.1 worked fine.
I'm currently using a script to re-enable adapter when info.connect drops to false, but wonder if it is something that can be updated in adapter itself.
thx.
Besteht die Möglichkeit bei einem Dimmwert von 0 die LED auszuschalten und umgekehrt?
Würde in der Material Visu helfen.
Gruß und Danke
yeelight-2.0 | 2018-09-08 00:19:46.118 | error | SyntaxError: Unexpected token { in JSON at position 27
-- | -- | -- | --
yeelight-2.0 | 2018-09-08 00:19:36.768 | error | SyntaxError: Unexpected token { in JSON at position 50
yeelight-2.0 | 2018-09-08 00:19:32.203 | error | SyntaxError: Unexpected token { in JSON at position 27
yeelight-2.0 | 2018-09-08 00:19:13.524 | error | SyntaxError: Unexpected token { in JSON at position 81
yeelight-2.0 | 2018-09-08 00:19:10.172 | error | SyntaxError: Unexpected token { in JSON at position 78
I have following error when i try to switch on or off my yeelight 650 or Ceiling Light.
can u help ?
thx
I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
I have also found warnings that may be fixed if possible.
Thanks,
your automatic adapter checker.
can you fix this?
Model № YLDP06YL
no control option and no connect. added by ip and port 55443
Hi,
vieloeicht ist es einfacher wenn man sich auf deutsch unterhält ;).
Dachte es wäre von Vorteil für andere User wenn man es auf Englisch versucht, sollen die Google Translate benutzen.
Die Steuerung der bg_rgb ist behoben, zumindest kann ich nunn da was einstellen.
Aber habe andere Probleme, keine Ahnung ob dies an meinem setup oder anderm Zeug liegt.
Folgende Probleme habe ich mit den Yeelights in Kombination mit dem iobroker, per Yeelight App habe ich keine Probleme.
Bei Lampen die ausgeschaltet (kein Strom) sind, also nicht per App oder per Sensor usw. wird der Wert von indicator.connected von true auf false gesetzt nach einiger Zeit, dies ist soweit korrekt, jedoch schaltet der Wert hin und wieder zwiaschen true und false obwohl die Lampe weiterhin ausgeschaltet ist und in der zwischenzeit auch nicht eingeschaltet wurde.
Schalte die Lampen abends aber auch tagsüber komplett aus (per Schalter), nach wieder einschalten habe ich in letzter Zeit dann das Problem das der iobroker die Lampen nicht mehr findet, also die Verbindung scheint anschließend nicht immer wieder aufgebaut zu werden, obwohl sich die IP Adressen der Yeelights auch nicht geändert hat. Wenn ich die Yeelight Instanz dann jedoch neu starte werden die Lampen wieder gefunden.
Hänge mal ein Log an mit der Bitte um Unterstützung, komme da leider nicht wirklcih weiter.
Kann man den yeelight Adapter irgendwie komplett löschen über Console und neu installieren? Nicht das irgendwo irgendwelche Temp Dateien stören usw.
Was mir noch aufgefallen ist das im Log (Debug) einige für mich merkwürdige Werte angezeigt werden.
Die Namen 0x000000000000000 bis 0x000000000000005 sind mir nicht bekannt, die von mir genutzen und über den Adapter gefundenen Lampen haben andere Namen (siehe Log im Anhang)
Was ich bislang versucht habe:
Gruß und besten Dank
Jay
Hi!
Cannot switch the state of Yeelight Ceiling Light to "on" from a script. Somehow it gets turned off every time.
A script example
on("mihome.0.devices.switch_158d0002b221d8.click", function(obj){
if(getState("mihome.0.devices.switch_158d0002b221d8.click").val == true){
setState("yeelight-2.0.ceiling1-0x000000000370088e.control.power", true);
}
});
If I will use simple
setState("yeelight-2.0.ceiling1-0x000000000370088e.control.power", true);
without subscription, everything is ok, lamp will not switch off
In the event log
type | ID | val | ack | from | timestamp | last change |
---|---|---|---|---|---|---|
stateChange | yeelight-2.0.ceiling1-0x000000000370088e.control.power | false | true | yeelight-2.0 | 2019-01-20 23:44:52.314 | 2019-01-20 23:44:52.314 |
stateChange | yeelight-2.0.ceiling1-0x000000000370088e.info.connect | true | true | yeelight-2.0 | 2019-01-20 23:44:52.314 | 2019-01-20 23:33:01.154 |
stateChange | system.adapter.yeelight-2.0.outputCount | 15 | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:44:44.391 |
stateChange | system.adapter.yeelight-2.0.inputCount | 8 | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:44:44.391 |
stateChange | system.adapter.yeelight-2.0.uptime | 706 | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:44:44.391 |
stateChange | system.adapter.yeelight-2.0.memHeapUsed | 10.72 | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:44:44.391 |
stateChange | system.adapter.yeelight-2.0.memHeapTotal | 13.83 | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:44:14.383 |
stateChange | system.adapter.yeelight-2.0.memRss | 37.2 | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:44:44.391 |
stateChange | system.adapter.yeelight-2.0.connected | true | true | yeelight-2.0 | 2019-01-20 23:44:44.391 | 2019-01-20 23:32:59.069 |
stateChange | system.adapter.yeelight-2.0.alive | true | true | yeelight-2.0 | 2019-01-20 23:44:44.390 | 2019-01-20 23:32:59.067 |
stateChange | yeelight-2.0.ceiling1-0x000000000370088e.control.power | true | true | yeelight-2.0 | 2019-01-20 23:44:43.930 | 2019-01-20 23:44:43.917 |
Hi,
the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.
You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.
Please update your systems to js-controller 2.0 and check your adapter.
Please close this issue once you have checked your adapter or received successfull reports from users.
Thank you very much for your support. Please contact us in the other Threads or Forum on any question.
Under Object - Control i only see the folder scene with varius scene in it.
The debug log shows the following:
yeelight-2.0 | 2018-08-30 11:26:30.477 | debug | system.adapter.admin.0: logging true |
---|---|---|---|
yeelight-2.0 | 2018-08-30 11:24:33.996 | debug | system.adapter.admin.0: logging false |
yeelight-2.0 | 2018-08-30 11:23:00.525 | error | Error: connect ECONNREFUSED 192.168.0.196:55443 |
yeelight-2.0 | 2018-08-30 11:23:00.525 | debug | regest params from:yeelight-2.0.ceiling1-Badezimmerleuchte.control _params:_undefined |
yeelight-2.0 | 2018-08-30 11:23:00.525 | error | Error: connect ECONNREFUSED 192.168.0.196:55443 |
yeelight-2.0 | 2018-08-30 11:23:00.525 | error | Error: connect ECONNREFUSED 192.168.0.196:55443 |
yeelight-2.0 | 2018-08-30 11:22:59.713 | debug | system.adapter.admin.0: logging true |
yeelight-2.0 | 2018-08-30 11:22:59.494 | debug | listen to: 192.168.0.196:55443 |
yeelight-2.0 | 2018-08-30 11:22:59.494 | debug | Update connection for:_yeelight-2.0.ceiling1-Badezimmerleuchte |
yeelight-2.0 | 2018-08-30 11:22:59.494 | debug | sid by socket:_["yeelight-2","0","ceiling1-Badezimmerleuchte","info","IPAdress"] |
yeelight-2.0 | 2018-08-30 11:22:59.494 | debug | Create Device: yeelight-2.0.ceiling1-Badezimmerleuchte |
yeelight-2.0 | 2018-08-30 11:22:57.493 | debug | der sm: Badezimmerleuchte |
yeelight-2.0 | 2018-08-30 11:22:57.493 | debug | hier die ate cfg: {"name":"Badezimmerleuchte","ip":"192.168.0.196","port":"55443","smart_name":"Badezimmerleuchte","type":"ceiling1"} |
yeelight-2.0 | 2018-08-30 11:22:57.478 | debug | Element:_yeelight-2.0.ceiling1-Badezimmerleuchte |
yeelight-2.0 | 2018-08-30 11:22:57.478 | debug | count Devices:_1 |
yeelight-2.0 | 2018-08-30 11:22:57.478 | debug | found Devices:_{"yeelight-2.0.ceiling1-Badezimmerleuchte":{"type":"device","common":{"name":"ceiling1","icon":"/icons/ceiling1.png"},"native":{"sid":"Badezimmerleuchte","type":"ceiling1"},"from":"sys |
yeelight-2.0 | 2018-08-30 11:22:57.462 | debug | from_conf: {"devices":[{"name":"Badezimmerleuchte","ip":"192.168.0.196","port":"55443","smart_name":"Badezimmerleuchte","type":"ceiling1"}]} |
The lamp works fine with Mi-Home-App and the Yeelight-App. I already deinstalled and installed the adapter but nothing changed.
in der iot-cloud eine Gruppe "Deckenfluter" wie folgt angelegt:
Hallöchen,
wenn ich die Xiaomi Bedside Lamp (MUCTD01YL) über ioBroker oder Alexa ausschalte, dann wird nach ca. 30 Sekunden der Dimmer-State wieder > 0% gesetzt und die Lampe schaltet sich mit dem letzten Status wieder ein, da gleichzeitig der Power-State auf "true" gesetzt wird. Ich habe über ein Blockly-Script einmal geschaut (da ja über iobroker/Alexa mit dem Dimm-Wert eingeschaltet wird > 0%) woher der Einschaltbefehl kommt. Der ursprüngliche Trigger ist in dem Fall der Yeelight-2 Adapter. Ich habe mir jetzt im Blockly erst einmal so beholfen das ich in diesem Fall Befehle vom Yeelight-2 Adapter ignoriere in Verbindung mit dem Power-State und so dennoch über ioBroker und Alexa die Lampe ein-/ausschalten kann.
Ich kann leider nicht sagen warum der Adapter nach ~30 Sekunden wieder einen Dimmer-Wert einträgt und gleichzeitig das Power-State auf "true" gesetzt wird. Ich habe keine Timer in der Yeelight App oder dergleichen eingetragen.
Hallo,
ich erhalte seit neuestem folgende Fehlermeldungen. Installiert ist
JS-Controller: 3.0.7
NPM: 6.14.4
Node.js: 13.12.0
yeelight-2.0 2020-04-13 08:04:12.428 info (18850) Terminated (NO_ERROR): Without reason
yeelight-2.0 2020-04-13 08:04:12.427 info (18850) terminating
yeelight-2.0 2020-04-13 08:04:12.419 info (18850) cleaned everything up...
yeelight-2.0 2020-04-13 08:04:12.417 error at processImmediate (internal/timers.js:456:21)
yeelight-2.0 2020-04-13 08:04:12.417 error at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5303:34)
yeelight-2.0 2020-04-13 08:04:12.417 error at Adapter.emit (events.js:315:20)
yeelight-2.0 2020-04-13 08:04:12.417 error at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:44:21)
yeelight-2.0 2020-04-13 08:04:12.417 error at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:116:37)
yeelight-2.0 2020-04-13 08:04:12.417 error at Yeelight.turnOn (/opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:530:19)
yeelight-2.0 2020-04-13 08:04:12.417 error at Yeelight.sendRequest (/opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:211:14)
yeelight-2.0 2020-04-13 08:04:12.417 error at new Promise (<anonymous>)
yeelight-2.0 2020-04-13 08:04:12.417 error at /opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:216:23
yeelight-2.0 2020-04-13 08:04:12.417 error at module.exports.internals.Any.root.validate (/opt/iobroker/node_modules/joi/lib/index.js:139:23)
yeelight-2.0 2020-04-13 08:04:12.417 error at internals.Array._validateWithOptions (/opt/iobroker/node_modules/joi/lib/types/any/index.js:672:20)
yeelight-2.0 2020-04-13 08:04:12.417 error at /opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:232:27
yeelight-2.0 2020-04-13 08:04:12.417 error at Socket.Writable.write (_stream_writable.js:288:11)
yeelight-2.0 2020-04-13 08:04:12.417 error (18850) Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
yeelight-2.0 2020-04-13 08:04:12.415 error (18850) uncaught exception: Cannot call write after a stream was destroyed
According to https://github.com/MeisterTR/ioBroker.yeelight-2/blob/master/admin/index_m.html#L157
at least
native: {
devices: []
}
Should be there
Hi,
ich habe im Forum auch schon einen Thread eröffnet ohne Feedback, deswegen schreibe ich es hier nochmal.
Ich hatte den Adapter ca. 60 Tage am Laufen und hatte einen Arbeitsspeicher-Verbauch von 650 MB. Ist das normal? Beim löschen der Instanz gab es auch über 3000 Elemente die gelöscht wurden und das bei 4 angelernten Geräten
Vielleicht kann sich jemand das mal näher anschauen
Hi,
wird sich die neue Yeelight Pendellechte (YEELIGHT Meteorite LED Smart Dinner Pendant Lights) über deinen Adapter mit dem ioBroker verbinden lassen?
Wirst du den Adapter entsprechend anpassen um eine Verbindung zu ermöglichen?
Gruß
jay
2018-09-09 18:25:16.308 - error: Caught by controller[0]: TypeError: Cannot read property 'val' of null
2018-09-09 18:25:16.309 - error: Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:190:59
2018-09-09 18:25:16.310 - error: Caught by controller[0]: at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:287:17)
2018-09-09 18:25:16.310 - error: Caught by controller[0]: at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21)
2018-09-09 18:25:16.311 - error: Caught by controller[0]: at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9)
2018-09-09 18:25:16.311 - error: Caught by controller[0]: at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18)
2018-09-09 18:25:16.312 - error: Caught by controller[0]: at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12)
2018-09-09 18:25:16.312 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/redis/index.js:274:27)
2018-09-09 18:25:16.312 - error: Caught by controller[0]: at emitOne (events.js:96:13)
2018-09-09 18:25:16.313 - error: Caught by controller[0]: at Socket.emit (events.js:188:7)
2018-09-09 18:25:16.313 - error: Caught by controller[0]: at readableAddChunk (_stream_readable.js:176:18)
2018-09-09 18:25:16.314 - error: host.ioBroker-Pi instance system.adapter.yeelight-2.0 terminated with code 0 (OK)
2018-09-09 18:25:16.314 - info: host.ioBroker-Pi Restart adapter system.adapter.yeelight-2.0 because enabled
Most of the Yeelight ceiling lights and the bedside lamp include a BLE gateway to connect to BLE enabled sensors like the thermo-/hygrometer to extend their otherwise limited BLE range.
The MiHome app uses this functionality to make sensors readable even if the mobile phone is not in the BLE proximity.
Do you have any plans to make this functionality available in iobroker?
please add Yeelight ylld01yl 12w smart dimmable led floor table lamp wifi
host.server | 2020-03-07 12:17:59.003 | info | Restart adapter system.adapter.yeelight-2.1 because enabled |
---|---|---|---|
host.server | 2020-03-07 12:17:59.003 | info | instance system.adapter.yeelight-2.1 terminated with code 0 (NO_ERROR) |
host.server | 2020-03-07 12:17:59.002 | error | Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:68:7) |
host.server | 2020-03-07 12:17:59.002 | error | Caught by controller[0]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49) |
host.server | 2020-03-07 12:17:59.002 | error | Caught by controller[0]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23) |
host.server | 2020-03-07 12:17:59.001 | error | Caught by controller[0]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:572:33) |
host.server | 2020-03-07 12:17:59.001 | error | Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:284:62 |
host.server | 2020-03-07 12:17:59.000 | error | Caught by controller[0]: TypeError: Cannot read property 'val' of null |
yeelight-2.1 | 2020-03-07 12:17:58.471 | info | (6376) Terminated (NO_ERROR): Without reason |
yeelight-2.1 | 2020-03-07 12:17:58.469 | info | (6376) terminating |
yeelight-2.1 | 2020-03-07 12:17:58.415 | info | (6376) cleaned everything up... |
yeelight-2.1 | 2020-03-07 12:17:58.412 | error | at process._tickCallback (internal/process/next_tick.js:68:7) |
yeelight-2.1 | 2020-03-07 12:17:58.412 | error | at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49) |
yeelight-2.1 | 2020-03-07 12:17:58.412 | error | at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23) |
yeelight-2.1 | 2020-03-07 12:17:58.412 | error | at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:572:33) |
yeelight-2.1 | 2020-03-07 12:17:58.412 | error | at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:284:62 |
yeelight-2.1 | 2020-03-07 12:17:58.412 | error | (6376) TypeError: Cannot read property 'val' of null |
yeelight-2.1 | 2020-03-07 12:17:58.410 | error | (6376) uncaught exception: Cannot read property 'val' of null |
yeelight-2.1 | 2020-03-07 12:17:58.231 | info | (6376) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v10.19.0 |
host.server | 2020-03-07 12:17:55.577 | info | instance system.adapter.yeelight-2.1 started with pid 6376 |
Hallo zusammen,
ich bekomme meine Yeelight yldp02yl nicht eingebunden.
Kann mir jemand hier helfen?
Gruß
I know that scenes like sunrise and sunset are basically predefined by the manufacturer.
However, it would be really nice if the explanation for parameters in set_scene were more precise, i.e. can I set a total duration for sunrise?
Should this scene be triggered by writing set_scene in the control section or by sunset in the scenen section?
Besides: please correct this horrible spelling error. I suppose it should read scenes.
Szenen would be German. scenen is neither.
Hi, I am fairly new to the whole iobroker world, but am slowly making progress. I am however lost with the yeelight adapter as it started out working quite well, but is now stopping either after a while or even directly when being started. The error messages in the log are quite extensive, but unfortunately don't mean a lot to me. Any help or suggestions would be appreciated. Log attached. Thanks
yeelight adapter log.log
The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466
if i want to serach for new devices i get this errors in the log:
if i insert ip name and port manually it works
yeelight-2.0 | 2018-08-27 13:48:50.206 | debug | Create Device: yeelight-2.0.color- |
---|---|---|---|
yeelight-2.0 | 2018-08-27 13:48:48.199 | debug | der sm: |
yeelight-2.0 | 2018-08-27 13:48:48.198 | debug | hier die ate cfg: {"name":"","ip":"","port":"","smart_name":"","type":"color"} |
yeelight-2.0 | 2018-08-27 13:48:48.194 | debug | Element:_yeelight-2.0.color- |
yeelight-2.0 | 2018-08-27 13:48:48.193 | debug | count Devices:_1 |
yeelight-2.0 | 2018-08-27 13:48:48.193 | debug | found Devices:_{"yeelight-2.0.color-":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user. |
yeelight-2.0 | 2018-08-27 13:48:48.143 | debug | from_conf: {"devices":[{"name":"","ip":"","port":"","smart_name":"","type":"color"}]} |
yeelight-2.0 | 2018-08-27 13:48:48.104 | info | starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v8.11.1 |
yeelight-2.0 | 2018-08-27 13:48:48.063 | info | States connected to redis: 127.0.0.1:6379 |
yeelight-2.0 | 2018-08-27 13:48:48.057 | debug | statesDB connected |
yeelight-2.0 | 2018-08-27 13:48:48.024 | debug | objectDB connected |
host.ioBroker-RasPi | 2018-08-27 13:48:46.836 | info | instance system.adapter.yeelight-2.0 started with pid 2560 |
host.ioBroker-RasPi | 2018-08-27 13:48:16.805 | info | Restart adapter system.adapter.yeelight-2.0 because enabled |
host.ioBroker-RasPi | 2018-08-27 13:48:16.805 | error | instance system.adapter.yeelight-2.0 terminated with code 0 (OK) |
Caught | 2018-08-27 13:48:16.805 | error | by controller[1]: at Socket.emit (events.js:211:7) |
Caught | 2018-08-27 13:48:16.805 | error | by controller[1]: at emitOne (events.js:116:13) |
Caught | 2018-08-27 13:48:16.805 | error | by controller[1]: at Socket. (/opt/iobroker/node_modules/redis/index.js:274:27) |
Caught | 2018-08-27 13:48:16.805 | error | by controller[1]: at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12) |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18) |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9) |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21) |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:267:49) |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: at that.states.getStates (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4632:61) |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:1361:33 |
Caught | 2018-08-27 13:48:16.804 | error | by controller[1]: TypeError: Cannot set property '' of null |
Caught | 2018-08-27 13:48:16.803 | error | by controller[0]: at Timer.listOnTimeout (timers.js:277:5) |
Caught | 2018-08-27 13:48:16.803 | error | by controller[0]: at tryOnTimeout (timers.js:317:5) |
Caught | 2018-08-27 13:48:16.803 | error | by controller[0]: at ontimeout (timers.js:482:11) |
Caught | 2018-08-27 13:48:16.803 | error | by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:158:37) |
Caught | 2018-08-27 13:48:16.803 | error | by controller[0]: at createDevice (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:322:9) |
Caught | 2018-08-27 13:48:16.803 | error | by controller[0]: at getPrps (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:333:15) |
Caught | 2018-08-27 13:48:16.802 | error | by controller[0]: at Yeelight.sendCommand (/opt/iobroker/node_modules/iobroker.yeelight-2/lib/yeelight.js:47:19) |
Caught | 2018-08-27 13:48:16.802 | error | by controller[0]: at Object.connect (net.js:113:35) |
Caught | 2018-08-27 13:48:16.802 | error | by controller[0]: at Socket.connect (net.js:1037:5) |
Caught | 2018-08-27 13:48:16.802 | error | by controller[0]: at lookupAndConnect (net.js:1064:13) |
Caught | 2018-08-27 13:48:16.801 | error | by controller[0]: RangeError: "port" option should be >= 0 and < 65536: |
yeelight-2.0 | 2018-08-27 13:48:16.787 | info | terminating |
yeelight-2.0 | 2018-08-27 13:48:16.342 | error | Error: connect ECONNREFUSED 127.0.0.1:55443 |
yeelight-2.0 | 2018-08-27 13:48:16.341 | error | Error: connect ECONNREFUSED 127.0.0.1:55443 |
yeelight-2.0 | 2018-08-27 13:48:16.334 | debug | listen to: :55443 |
yeelight-2.0 | 2018-08-27 13:48:16.326 | debug | Update connection for:_yeelight-2.0.color- |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at Socket.emit (events.js:211:7) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at emitOne (events.js:116:13) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at Socket. (/opt/iobroker/node_modules/redis/index.js:274:27) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:824:9) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:267:49) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at that.states.getStates (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4632:61) |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | at /opt/iobroker/node_modules/iobroker.yeelight-2/main.js:1361:33 |
yeelight-2.0 | 2018-08-27 13:48:16.319 | error | TypeError: Cannot set property '' of null |
yeelight-2.0 | 2018-08-27 13:48:16.318 | error | uncaught exception: Cannot set property '' of null |
yeelight-2.0 | 2018-08-27 13:48:16.303 | debug | sid by socket:_["yeelight-2","0","color-","info","IPAdress"] |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at Timer.listOnTimeout (timers.js:277:5) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at tryOnTimeout (timers.js:317:5) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at ontimeout (timers.js:482:11) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:158:37) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at createDevice (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:322:9) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at getPrps (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:333:15) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at Yeelight.sendCommand (/opt/iobroker/node_modules/iobroker.yeelight-2/lib/yeelight.js:47:19) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at Object.connect (net.js:113:35) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at Socket.connect (net.js:1037:5) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | at lookupAndConnect (net.js:1064:13) |
yeelight-2.0 | 2018-08-27 13:48:16.280 | error | RangeError: "port" option should be >= 0 and < 65536: |
yeelight-2.0 | 2018-08-27 13:48:16.279 | error | uncaught exception: "port" option should be >= 0 and < 65536: |
yeelight-2.0 | 2018-08-27 13:48:16.257 | debug | Create Device: yeelight-2.0.color- |
yeelight-2.0 | 2018-08-27 13:48:14.248 | debug | der sm: |
yeelight-2.0 | 2018-08-27 13:48:14.247 | debug | hier die ate cfg: {"name":"","ip":"","port":"","smart_name":"","type":"color"} |
yeelight-2.0 | 2018-08-27 13:48:14.243 | debug | Element:_yeelight-2.0.color- |
yeelight-2.0 | 2018-08-27 13:48:14.243 | debug | count Devices:_1 |
yeelight-2.0 | 2018-08-27 13:48:14.242 | debug | found Devices:_{"yeelight-2.0.color-":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user. |
yeelight-2.0 | 2018-08-27 13:48:14.191 | debug | from_conf: {"devices":[{"name":"","ip":"","port":"","smart_name":"","type":"color"}]} |
yeelight-2.0 | 2018-08-27 13:48:14.151 | info | starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v8.11.1 |
yeelight-2.0 | 2018-08-27 13:48:14.109 | info | States connected to redis: 127.0.0.1:6379 |
yeelight-2.0 | 2018-08-27 13:48:14.102 | debug | statesDB connected |
yeelight-2.0 | 2018-08-27 13:48:14.068 | debug | objectDB connected |
I can't add devices to this adapter. If I hit "+" then fill out all fields and hit save, nothing happens. If I open my js debugger and have a look I get the following error message:
[Error] TypeError: undefined is not an object (evaluating 'obj.rawdevices.find')
(anonymous function) (index_m.html:191)
each (jquery-3.2.1.min.js:2:2720)
save (index_m.html:189)
(anonymous function) (adapter-settings.js:175)
dispatch (jquery-3.2.1.min.js:3:10322)
index_m.html line 191 is shown as:
let yeefind = obj.rawdevices.find(item => item.host === val.ip)
I have used this adapter before (about 3month ago) and never had a problem with it.
Any help would be much appreciated.
hello I get following error:
syntaxError: Unexpected token { in JSON at position 44
The Position number is not always the same.
what is this?
update to 0.4.0
Hello,
my bedside lamp 2 sets its control.power.val sporadically to false without turning its lamp really off. After few seconds it will automatically set to true again.
It's no problem in normal use, but if you want to control the whole room with the hardware keys of the bslamp2 (if bslamp2 turns off -> turn all off) it causes issues, because other lamps, except the bslamp2 will turn off.
I can only provide the events, because there is nothing noted in the logs (imo).
Thanks in advance!
If the yeelight color is powerd off and I change the color, the yeelight power on, but in io.broker the yeelight "power" attr. stays on false.
Please check.
Thank you :)
Pierre
Ich habe bei dem Adapter das Problem, dass er ziemlich häufig mittels Skript oder Sprachsteuerung die Lampe beispielsweise auf 0% dimmt und Power ausschaltet, die Werte im Objekt ankommen, aber scheinbar nicht bei der Lampe. D.h. für iobroker ist die Lampe aus, für die Yeelight App und die Lampe selber sind Sie aber an.
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. (/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. (/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. (/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. (/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. (/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. (/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
When setting a certain color (e.g. "grün") using Alexa Yeelight-skill the color_mode seems not to be updated at all. I would assume it should switch to color_mode=1 but it simply keeps it's value.
When setting a white value (e.g. "warmweiss") the color_mode value seems to be updated correctly (switches to color_mode=0).
Hallöchen,
es ist ja auch innerhalb der Yeelight App möglich Gruppen von Leuchtmitteln zu bilden. Wird dies in Zukunft ggf. auch im Adapter möglich sein? Ich habe z.B. im Wohnzimmer drei Yeelight Birnen in einer Lampe (LED - Color Yeelight 2) die ich gerne gruppiert steuern möchte.
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet.
We recommend using:
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
My RGB-Lamp named Pilz will power on after i refresh my VIS-View. All other yeelight-lamp´s stayed turned off it´s only happen on the bulk-rgb. Here the debug log during refresh of the vis-view:
yeelight-2.0 | 2018-09-21 07:37:35.084 | debug | power |
---|---|---|---|
yeelight-2.0 | 2018-09-21 07:37:35.084 | debug | {"192.168.0.197":"yeelight-2.0.stripe-Stripe1","192.168.0.196":"yeelight-2.0.ceiling1-Badezimmerlampe","192.168.0.198":"yeelight-2.0.ceiling1-Kuechenlampe","192.168.0.195":"yeelight-2.0.color-Pilz"} |
yeelight-2.0 | 2018-09-21 07:37:35.084 | debug | {"power":"on"} |
yeelight-2.0 | 2018-09-21 07:37:35.084 | debug | This id:_yeelight-2.0.color-Pilz.control |
yeelight-2.0 | 2018-09-21 07:37:35.084 | debug | 192.168.0.195 |
yeelight-2.0 | 2018-09-21 07:37:33.930 | debug | Answer from rgb _power on an color mode before set: ["ok"] |
yeelight-2.0 | 2018-09-21 07:37:33.896 | debug | rgb to hs: [240,43] |
yeelight-2.0 | 2018-09-21 07:37:33.896 | debug | Upload State rgb host: 192.168.0.195 Port: 55443 Value: #141432 |
yeelight-2.0 | 2018-09-21 07:37:33.889 | debug | ["yeelight-2","0","color-Pilz","control","rgb"] |
Kind regards klaus
workaround: delete old device in objects
NPM 6.14.4
Node.js 10.20.1
JS controller 3.0.14
yeelight-2 adapter 1.0.3
After switching twice with the scenes adapter, the yeelight adapter crashes. Already tried reinstallation to no avail.
State changes in objects view are repeatedly shown correct when using the lamp's own switch.
Lengthy log:
2020-04-21 21:50:45.691 - debug: yeelight-2.0 (2598) YEELIGHT FOUND: x.x.x.x:55443 id: 0x0000000010275a40 model: desklamp
2020-04-21 21:50:45.709 - debug: yeelight-2.0 (2598) RESPONSE MESSAGE: from: 0x0000000010275a40, id: 1, result:[off,10,,2,2700,,,,,0,,,,,,,,]}
2020-04-21 21:50:45.710 - debug: yeelight-2.0 (2598) INITINAL ID FOUND FOR: desklamp-0x0000000010275a40
2020-04-21 21:50:45.710 - debug: yeelight-2.0 (2598) DEVICE FOUND IN AND CONFIG: {"name":"lamp4-0x0000000010275a40","ip":"x.x.x.x","port":"55443","smart_name":"","type":"desklamp","id":"0x0000000010275a40"}
2020-04-21 21:51:07.983 - debug: yeelight-2.0 (2598) SEND STATE: id:0x0000000010275a40, state: active_bright, value: 10
2020-04-21 21:51:07.990 - debug: yeelight-2.0 (2598) SEND STATE: id:0x0000000010275a40, state: ct, value: 2700
2020-04-21 21:51:07.991 - debug: yeelight-2.0 (2598) SEND STATE: id:0x0000000010275a40, state: power, value: true
2020-04-21 21:51:07.999 - debug: yeelight-2.0 (2598) RESPONSE MESSAGE: from: 0x0000000010275a40, id: 2, result:[ok]}
2020-04-21 21:51:08.020 - debug: yeelight-2.0 (2598) RESPONSE MESSAGE: from: 0x0000000010275a40, id: 3, result:[ok]}
2020-04-21 21:51:08.070 - debug: yeelight-2.0 (2598) ERROR YEELIGHT CONNECTION: null: SyntaxError: Unexpected token { in JSON at position 44: {"method":"props","params":{"power":"on"}}
{"id":3,"result":["ok"]}
2020-04-21 21:51:10.686 - debug: yeelight-2.0 (2598) SEND STATE: id:0x0000000010275a40, state: active_bright, value: false
2020-04-21 21:51:10.692 - error: yeelight-2.0 (2598) uncaught exception: "value" does not contain 1 required value(s)
2020-04-21 21:51:10.695 - error: yeelight-2.0 (2598) ValidationError: "value" does not contain 1 required value(s)
at Object.exports.process (/opt/iobroker/node_modules/joi/lib/errors.js:190:19)
at internals.Array._validateWithOptions (/opt/iobroker/node_modules/joi/lib/types/any/index.js:669:31)
at module.exports.internals.Any.root.validate (/opt/iobroker/node_modules/joi/lib/index.js:139:23)
at /opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:216:23
at new Promise ()
at Yeelight.sendRequest (/opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:211:14)
at Yeelight.setBrightness (/opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:480:19)
at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:134:29)
at Adapter. (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:44:21)
at Adapter.emit (events.js:198:13)
at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5303:34)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
2020-04-21 21:51:10.696 - info: yeelight-2.0 (2598) cleaned everything up...
2020-04-21 21:51:10.699 - debug: yeelight-2.0 (2598) SEND STATE: id:0x0000000010275a40, state: ct, value: false
2020-04-21 21:51:10.701 - debug: yeelight-2.0 (2598) SEND STATE: id:0x0000000010275a40, state: power, value: false
2020-04-21 21:51:10.702 - error: yeelight-2.0 (2598) uncaught exception: "value" does not contain 1 required value(s)
2020-04-21 21:51:10.703 - error: yeelight-2.0 (2598) ValidationError: "value" does not contain 1 required value(s)
at Object.exports.process (/opt/iobroker/node_modules/joi/lib/errors.js:190:19)
at internals.Array._validateWithOptions (/opt/iobroker/node_modules/joi/lib/types/any/index.js:669:31)
at module.exports.internals.Any.root.validate (/opt/iobroker/node_modules/joi/lib/index.js:139:23)
at /opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:216:23
at new Promise ()
at Yeelight.sendRequest (/opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:211:14)
at Yeelight.setColorTemperature (/opt/iobroker/node_modules/iobroker.yeelight-2/yeelight-wifi/build/Yeelight.js:421:19)
at uploadState (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:140:29)
at Adapter. (/opt/iobroker/node_modules/iobroker.yeelight-2/main.js:44:21)
at Adapter.emit (events.js:198:13)
at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5303:34)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
2020-04-21 21:51:10.705 - info: yeelight-2.0 (2598) terminating
2020-04-21 21:51:10.706 - info: yeelight-2.0 (2598) Terminated (NO_ERROR): Without reason
2020-04-21 21:51:10.718 - debug: yeelight-2.0 (2598) NOTIFY MESSAGE: from: 0x0000000010275a40, message: {"method":"props","params":{"power":"off"}}
2020-04-21 21:51:10.720 - debug: yeelight-2.0 (2598) DEVICE FOUND SET NOTIFY STATE: {"name":"lamp4-0x0000000010275a40","ip":"x.x.x.x","port":"55443","smart_name":"","type":"desklamp","id":"0x0000000010275a40"}
2020-04-21 21:51:10.723 - debug: yeelight-2.0 (2598) RESPONSE MESSAGE: from: 0x0000000010275a40, id: 5, result:[ok]}
2020-04-21 21:51:11.225 - info: host.iobroker instance system.adapter.yeelight-2.0 terminated with code 0 (NO_ERROR)
2020-04-21 21:51:11.226 - info: host.iobroker Restart adapter system.adapter.yeelight-2.0 because enabled
I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
I have also found warnings that may be fixed if possible.
Thanks,
your automatic adapter checker.
Wenn eine yeelight "länger" aus war, dann ist es mir schon mehrfach passiert, dass sie nicht mehr gesteurt werden konnte. Selbst nachdem sie 1/2h oder länger wieder Strom hatte. Erst ein restart des Adapters brachte die Steuerbarkeit zurück.
The yeelight meteroite pedant light cannot be controlled with me.
I have activated the LAN mode and am also connected to the lamp. But I can't control it, I can only see the status.
When I try to set the power status to true, it flashes red.
What could be the reason?
I receive sporadically the following error-messages wtih yellight-2.1 Version 0.9.4:
yeelight-2.1 2018-11-19 17:13:11.618 info cleaned everything up...
yeelight-2.1 2018-11-19 17:13:11.616 error at TCP.onread (net.js:601:20)
yeelight-2.1 2018-11-19 17:13:11.616 error at Socket.Readable.push (_stream_readable.js:208:10)
yeelight-2.1 2018-11-19 17:13:11.616 error at readableAddChunk (_stream_readable.js:250:11)
yeelight-2.1 2018-11-19 17:13:11.616 error at addChunk (_stream_readable.js:263:12)
yeelight-2.1 2018-11-19 17:13:11.616 error at Socket.emit (events.js:211:7)
yeelight-2.1 2018-11-19 17:13:11.616 error at emitOne (events.js:116:13)
yeelight-2.1 2018-11-19 17:13:11.616 error at Yeelight.formatResponse (C:\ioBroker\node_modules\iobroker.yeelight-2\node_modules\yeelight-wifi\build\Yeelight.js:288:28)
yeelight-2.1 2018-11-19 17:13:11.616 error ReferenceError: id is not defined
yeelight-2.1 2018-11-19 17:13:11.615 error uncaught exception: id is not defined
If you need further Trace please let me know.
Kind regards
Klaus
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.