Alpha Test js-controller 5.0
-
hier mit dem Yeelight-Adapter keine Probleme, hab Node 18 installiert, im lxc unter debian bullseye.., alles auf latest:
Welche Node Version hast du installiert?
-
seq.0 2023-04-01 10:17:13.167 warn State "seq.0.system.adapter.seq.0.logging" has no existing object, this might lead to an error in future versions seq.0 2023-04-01 10:17:13.145 info starting. Version 0.2.10 in /opt/iobroker/node_modules/iobroker.seq, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230330-e0b409fe host.usv-serverschrank 2023-04-01 10:17:12.531 info instance system.adapter.seq.0 started with pid 24436der ist verkehrt
seq.0.system.adapter.seq.0.logging -
@ilovegym Node.js: v18.15.0 wie bei dir....
Nachtrag; Ich habe die Instanz gelöscht....eine neue gemacht....und jetzt kommen keine Fehler mehr -
@arteck danke. Foxriver hat damit Fehler gefunden.
-
@docgame hat nichts mit Controller zu tun.
-
@apollon77 Schreibst du hier, wenn es eine neue Version vom js-controller gibt die getestet werden soll?
-
Beeindruckend wie schnell das update auf den js-controller 5.0 durchgeführt worden ist.
Ich habe auch das bekannte Problem mit dem log und der milight-smart-light Adapter funktioniert nicht wirklich.
https://github.com/Steiger04/ioBroker.milight-smart-light/issues/58Ansonsten läuft alles.
-
@feuersturm Na klar,
-
Nach einem erneuten Neustart von ioBroker, will mein Yeelight Adapter plötzlich auch nicht mehr.
host.ioBroker-Rock 2023-04-02 21:33:58.543 warn Do not restart adapter system.adapter.yeelight-2.0 because restart loop detected host.ioBroker-Rock 2023-04-02 21:33:58.543 info Restart adapter system.adapter.yeelight-2.0 because enabled host.ioBroker-Rock 2023-04-02 21:33:58.543 error instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker-Rock 2023-04-02 21:33:58.542 error Caught by controller[0]: at TCP.<anonymous> (node:net:322:12) host.ioBroker-Rock 2023-04-02 21:33:58.542 error Caught by controller[0]: at Socket.emit (node:domain:489:12) host.ioBroker-Rock 2023-04-02 21:33:58.542 error Caught by controller[0]: at Socket.emit (node:events:525:35) host.ioBroker-Rock 2023-04-02 21:33:58.541 error Caught by controller[0]: at Object.onceWrapper (node:events:628:26) host.ioBroker-Rock 2023-04-02 21:33:58.541 error Caught by controller[0]: at Socket.onClose (node:net:911:10) host.ioBroker-Rock 2023-04-02 21:33:58.541 error Caught by controller[0]: at new NodeError (node:internal/errors:399:5) host.ioBroker-Rock 2023-04-02 21:33:58.540 error Caught by controller[0]: Error: Socket closed before the connection was established host.ioBroker-Rock 2023-04-02 21:33:58.539 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: yeelight-2.0 2023-04-02 21:33:58.409 info terminating yeelight-2.0 2023-04-02 21:33:57.906 warn Terminated (UNCAUGHT_EXCEPTION): Without reason yeelight-2.0 2023-04-02 21:33:57.904 info terminating yeelight-2.0 2023-04-02 21:33:57.903 info cleaned everything up... yeelight-2.0 2023-04-02 21:33:57.875 error Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established yeelight-2.0 2023-04-02 21:33:57.874 error Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12) yeelight-2.0 2023-04-02 21:33:57.873 error unhandled promise rejection: Socket closed before the connection was established yeelight-2.0 2023-04-02 21:33:57.871 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). yeelight-2.0 2023-04-02 21:33:54.669 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230330-e0b409fe host.ioBroker-Rock 2023-04-02 21:33:50.899 info instance system.adapter.yeelight-2.0 started with pid 23551 alexa2.0 2023-04-02 21:33:50.136 info Alexa-Push-Connection disconnected - retry: Retry Connection in 60s host.ioBroker-Rock 2023-04-02 21:33:20.706 info Restart adapter system.adapter.yeelight-2.0 because enabled host.ioBroker-Rock 2023-04-02 21:33:20.705 error instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker-Rock 2023-04-02 21:33:20.705 error Caught by controller[1]: at TCP.<anonymous> (node:net:322:12) host.ioBroker-Rock 2023-04-02 21:33:20.704 error Caught by controller[1]: at Socket.emit (node:domain:489:12) host.ioBroker-Rock 2023-04-02 21:33:20.704 error Caught by controller[1]: at Socket.emit (node:events:525:35) host.ioBroker-Rock 2023-04-02 21:33:20.701 error Caught by controller[1]: at Object.onceWrapper (node:events:628:26) host.ioBroker-Rock 2023-04-02 21:33:20.701 error Caught by controller[1]: at Socket.onClose (node:net:911:10) host.ioBroker-Rock 2023-04-02 21:33:20.701 error Caught by controller[1]: at new NodeError (node:internal/errors:399:5) host.ioBroker-Rock 2023-04-02 21:33:20.700 error Caught by controller[1]: Error: Socket closed before the connection was established host.ioBroker-Rock 2023-04-02 21:33:20.699 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: yeelight-2.0 2023-04-02 21:33:20.586 info terminating yeelight-2.0 2023-04-02 21:33:20.084 warn Terminated (UNCAUGHT_EXCEPTION): Without reason yeelight-2.0 2023-04-02 21:33:20.082 info terminating yeelight-2.0 2023-04-02 21:33:20.081 info cleaned everything up... yeelight-2.0 2023-04-02 21:33:20.051 error Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established yeelight-2.0 2023-04-02 21:33:20.049 error Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12) yeelight-2.0 2023-04-02 21:33:20.048 error unhandled promise rejection: Socket closed before the connection was established yeelight-2.0 2023-04-02 21:33:20.047 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). yeelight-2.0 2023-04-02 21:33:16.855 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230330-e0b409fe host.ioBroker-Rock 2023-04-02 21:33:13.855 info instance system.adapter.yeelight-2.0 started with pid 23534 -
Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e
- Fixes missing logging object when logTransporter is used (e.g. Admin)
- Fixes other issue with logTransporter (e.g. Admin) - events should now stream again in Admin
- Fixed Compact group initialization
- Fixes Binary/Text detection in writeFile
- Fixes sendToHost (all) command
Laut aktuellem stand sind damit alle gemeldete und auf den controller zurückzuführeden Themen behoben. Das Windows Kodi/git-npm-Fehler Thema muss man noch genauer untersuchen denke ich.
-
@apollon77
Die Missing Logging object Warnung tritt hier nicht mehr auf
Admin Log wird automatisch aktualisiert (wobei das bei mir ja auch mit der Vorgängerversion ging)Sonst ist mir erst mal nix aufgefallen,
nur ein alter bekannter unter Windows ist wieder da (das liegt aber am aktualisierten JavaScript Adapter): Der Font für die Symbole im Suchfenster ist kaputt:
Fehlermeldung im Logjavascript.0 2023-04-03 12:43:30.883 error Cannot patch font: Error: Parameter "data" needs to be a Buffer but type "object" has been passedEdit: OK, vergiss es, hat Bluefox bereits (wieder) in GIT gefixt.
-
Danke für das Update.
Das Problem mit Yeelight besteht weiterhin.host.ioBroker-Rock 2023-04-03 21:29:21.231 info Restart adapter system.adapter.yeelight-2.0 because enabled host.ioBroker-Rock 2023-04-03 21:29:21.230 error instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker-Rock 2023-04-03 21:29:21.229 error Caught by controller[1]: at TCP.<anonymous> (node:net:322:12) host.ioBroker-Rock 2023-04-03 21:29:21.228 error Caught by controller[1]: at Socket.emit (node:domain:489:12) host.ioBroker-Rock 2023-04-03 21:29:21.227 error Caught by controller[1]: at Socket.emit (node:events:525:35) host.ioBroker-Rock 2023-04-03 21:29:21.227 error Caught by controller[1]: at Object.onceWrapper (node:events:628:26) host.ioBroker-Rock 2023-04-03 21:29:21.226 error Caught by controller[1]: at Socket.onClose (node:net:911:10) host.ioBroker-Rock 2023-04-03 21:29:21.225 error Caught by controller[1]: at new NodeError (node:internal/errors:399:5) host.ioBroker-Rock 2023-04-03 21:29:21.225 error Caught by controller[1]: Error: Socket closed before the connection was established host.ioBroker-Rock 2023-04-03 21:29:21.224 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: yeelight-2.0 2023-04-03 21:29:20.592 warn Terminated (UNCAUGHT_EXCEPTION): Without reason yeelight-2.0 2023-04-03 21:29:20.590 info terminating yeelight-2.0 2023-04-03 21:29:20.589 info cleaned everything up... yeelight-2.0 2023-04-03 21:29:20.562 error Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established yeelight-2.0 2023-04-03 21:29:20.561 error Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12) yeelight-2.0 2023-04-03 21:29:20.560 error unhandled promise rejection: Socket closed before the connection was established yeelight-2.0 2023-04-03 21:29:20.558 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). host.ioBroker-Rock 2023-04-03 21:29:20.372 info instance system.adapter.alexa2.0 started with pid 33531 host.ioBroker-Rock 2023-04-03 21:29:18.170 info instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.ioBroker-Rock 2023-04-03 21:29:17.910 info instance system.adapter.device-watcher.0 started with pid 33520 yeelight-2.0 2023-04-03 21:29:17.308 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e -
@apollon77 sagte in Alpha Test js-controller 5.0:
Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e
Master Slave System wurde erfolgreich aktualisiert.
Admin Log aktualisiert sich jetzt auch wieder automatischBisher keine weiteren Auffälligkeiten bei mir
Dankeschön
-
@e-i-k-e mach mal loglevel Debug. Vllt sieht man da mehr.
-
Gerne.
host.ioBroker-Rock 2023-04-03 23:27:06.136 info Restart adapter system.adapter.yeelight-2.0 because enabled host.ioBroker-Rock 2023-04-03 23:27:06.135 error instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker-Rock 2023-04-03 23:27:06.135 error Caught by controller[1]: at TCP.<anonymous> (node:net:322:12) host.ioBroker-Rock 2023-04-03 23:27:06.135 error Caught by controller[1]: at Socket.emit (node:domain:489:12) host.ioBroker-Rock 2023-04-03 23:27:06.134 error Caught by controller[1]: at Socket.emit (node:events:525:35) host.ioBroker-Rock 2023-04-03 23:27:06.134 error Caught by controller[1]: at Object.onceWrapper (node:events:628:26) host.ioBroker-Rock 2023-04-03 23:27:06.134 error Caught by controller[1]: at Socket.onClose (node:net:911:10) host.ioBroker-Rock 2023-04-03 23:27:06.134 error Caught by controller[1]: at new NodeError (node:internal/errors:399:5) host.ioBroker-Rock 2023-04-03 23:27:06.133 error Caught by controller[1]: Error: Socket closed before the connection was established host.ioBroker-Rock 2023-04-03 23:27:06.133 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: yeelight-2.0 2023-04-03 23:27:05.485 warn Terminated (UNCAUGHT_EXCEPTION): Without reason yeelight-2.0 2023-04-03 23:27:05.484 debug Plugin sentry destroyed yeelight-2.0 2023-04-03 23:27:05.483 info terminating yeelight-2.0 2023-04-03 23:27:05.482 info cleaned everything up... yeelight-2.0 2023-04-03 23:27:05.446 error Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established yeelight-2.0 2023-04-03 23:27:05.445 error Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12) yeelight-2.0 2023-04-03 23:27:05.445 error unhandled promise rejection: Socket closed before the connection was established yeelight-2.0 2023-04-03 23:27:05.444 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). yeelight-2.0 2023-04-03 23:27:05.436 debug ERROR YEELIGHT CONNECTION: 0x000000000000000: Connection 192.168.3.140:55443: Error: connect EHOSTUNREACH 192.168.3.140:55443 yeelight-2.0 2023-04-03 23:27:02.673 debug DEVICE FOUND IN AND CONFIG: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"} yeelight-2.0 2023-04-03 23:27:02.670 debug INITINAL ID FOUND FOR: color-0x0000000005ed0835 yeelight-2.0 2023-04-03 23:27:02.669 debug RESPONSE MESSAGE: from: 0x0000000005ed0835, id: 1, result:[off,23,16711680,2,3000,,,0,100,0,,,,,,,,]} yeelight-2.0 2023-04-03 23:27:02.642 debug YEELIGHT FOUND: 192.168.3.141:55443 id: 0x0000000005ed0835 model: color yeelight-2.0 2023-04-03 23:27:02.349 debug YEELIGHT FOUND: 192.168.3.140:55443 id: 0x000000000000000 model: color yeelight-2.0 2023-04-03 23:27:02.333 debug SMARTNAME: yeelight-2.0 2023-04-03 23:27:02.331 debug OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]} yeelight-2.0 2023-04-03 23:27:02.323 debug OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_groß yeelight-2.0 2023-04-03 23:27:02.322 debug SMARTNAME: yeelight-2.0 2023-04-03 23:27:02.320 debug OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"} yeelight-2.0 2023-04-03 23:27:02.308 debug OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_klein yeelight-2.0 2023-04-03 23:27:02.307 debug DEVICES IN OBJECTS FOUND: 2 yeelight-2.0 2023-04-03 23:27:02.306 debug DEVICES IN OBJECTS: {"yeelight-2.0.Stehlampe_Schlafzimmer_klein":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_klein","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629168,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_klein","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},"yeelight-2.0.Stehlampe_Schlafzimmer_groß":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_groß","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629164,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_groß","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}} yeelight-2.0 2023-04-03 23:27:02.272 debug DEVICES IN CONFIG: [{"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]},{"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}] yeelight-2.0 2023-04-03 23:27:02.218 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e yeelight-2.0 2023-04-03 23:27:01.853 debug Plugin sentry Initialize Plugin (enabled=true) mqtt.0 2023-04-03 23:27:01.267 info Client [] connected with secret 1680557221267_3140 mqtt.0 2023-04-03 23:27:01.022 info Client [] connection closed: disconnected host.ioBroker-Rock 2023-04-03 23:26:59.134 info instance system.adapter.yeelight-2.0 started with pid 34722 influxdb.0 2023-04-03 23:26:36.571 info Store 501 buffered influxDB history points host.ioBroker-Rock 2023-04-03 23:26:29.001 info Restart adapter system.adapter.yeelight-2.0 because enabled host.ioBroker-Rock 2023-04-03 23:26:29.000 error instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker-Rock 2023-04-03 23:26:29.000 error Caught by controller[0]: at TCP.<anonymous> (node:net:322:12) host.ioBroker-Rock 2023-04-03 23:26:29.000 error Caught by controller[0]: at Socket.emit (node:domain:489:12) host.ioBroker-Rock 2023-04-03 23:26:28.999 error Caught by controller[0]: at Socket.emit (node:events:525:35) host.ioBroker-Rock 2023-04-03 23:26:28.999 error Caught by controller[0]: at Object.onceWrapper (node:events:628:26) host.ioBroker-Rock 2023-04-03 23:26:28.999 error Caught by controller[0]: at Socket.onClose (node:net:911:10) host.ioBroker-Rock 2023-04-03 23:26:28.999 error Caught by controller[0]: at new NodeError (node:internal/errors:399:5) host.ioBroker-Rock 2023-04-03 23:26:28.998 error Caught by controller[0]: Error: Socket closed before the connection was established host.ioBroker-Rock 2023-04-03 23:26:28.997 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: yeelight-2.0 2023-04-03 23:26:28.347 warn Terminated (UNCAUGHT_EXCEPTION): Without reason yeelight-2.0 2023-04-03 23:26:28.346 debug Plugin sentry destroyed yeelight-2.0 2023-04-03 23:26:28.345 info terminating yeelight-2.0 2023-04-03 23:26:28.344 info cleaned everything up... yeelight-2.0 2023-04-03 23:26:28.323 error Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established yeelight-2.0 2023-04-03 23:26:28.323 error Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12) yeelight-2.0 2023-04-03 23:26:28.322 error unhandled promise rejection: Socket closed before the connection was established yeelight-2.0 2023-04-03 23:26:28.322 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). yeelight-2.0 2023-04-03 23:26:28.315 debug ERROR YEELIGHT CONNECTION: 0x000000000000000: Connection 192.168.3.140:55443: Error: connect EHOSTUNREACH 192.168.3.140:55443 yeelight-2.0 2023-04-03 23:26:26.545 debug DEVICE FOUND IN AND CONFIG: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"} yeelight-2.0 2023-04-03 23:26:26.542 debug INITINAL ID FOUND FOR: color-0x0000000005ed0835 yeelight-2.0 2023-04-03 23:26:26.542 debug RESPONSE MESSAGE: from: 0x0000000005ed0835, id: 1, result:[off,23,16711680,2,3000,,,0,100,0,,,,,,,,]} yeelight-2.0 2023-04-03 23:26:25.547 debug YEELIGHT FOUND: 192.168.3.141:55443 id: 0x0000000005ed0835 model: color yeelight-2.0 2023-04-03 23:26:25.254 debug YEELIGHT FOUND: 192.168.3.140:55443 id: 0x000000000000000 model: color yeelight-2.0 2023-04-03 23:26:25.238 debug SMARTNAME: yeelight-2.0 2023-04-03 23:26:25.236 debug OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]} yeelight-2.0 2023-04-03 23:26:25.229 debug OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_groß yeelight-2.0 2023-04-03 23:26:25.228 debug SMARTNAME: yeelight-2.0 2023-04-03 23:26:25.226 debug OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"} yeelight-2.0 2023-04-03 23:26:25.213 debug OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_klein yeelight-2.0 2023-04-03 23:26:25.212 debug DEVICES IN OBJECTS FOUND: 2 yeelight-2.0 2023-04-03 23:26:25.211 debug DEVICES IN OBJECTS: {"yeelight-2.0.Stehlampe_Schlafzimmer_klein":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_klein","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629168,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_klein","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},"yeelight-2.0.Stehlampe_Schlafzimmer_groß":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_groß","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629164,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_groß","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}} yeelight-2.0 2023-04-03 23:26:25.181 debug DEVICES IN CONFIG: [{"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]},{"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}] yeelight-2.0 2023-04-03 23:26:25.142 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e yeelight-2.0 2023-04-03 23:26:24.734 debug Plugin sentry Initialize Plugin (enabled=true) yeelight-2.0 2023-04-03 23:26:24.629 debug States connected to redis: 192.168.3.104:6379 yeelight-2.0 2023-04-03 23:26:24.617 debug States create User PubSub Client yeelight-2.0 2023-04-03 23:26:24.615 debug States create System PubSub Client yeelight-2.0 2023-04-03 23:26:24.608 debug Redis States: Use Redis connection: 192.168.3.104:6379 yeelight-2.0 2023-04-03 23:26:24.587 debug Objects connected to redis: 192.168.3.104:6379 yeelight-2.0 2023-04-03 23:26:24.579 debug Objects client initialize lua scripts yeelight-2.0 2023-04-03 23:26:23.863 debug Objects create User PubSub Client yeelight-2.0 2023-04-03 23:26:23.861 debug Objects create System PubSub Client yeelight-2.0 2023-04-03 23:26:23.856 debug Objects client ready ... initialize now yeelight-2.0 2023-04-03 23:26:23.793 debug Redis Objects: Use Redis connection: 192.168.3.104:6379 host.ioBroker-Rock 2023-04-03 23:26:21.996 info instance system.adapter.yeelight-2.0 started with pid 34705 host.ioBroker-Rock 2023-04-03 23:26:21.680 info "system.adapter.yeelight-2.0" enabled host.ioBroker-Rock 2023-04-03 23:26:10.184 info "system.adapter.yeelight-2.0" disabled -
@e-i-k-e sagte in Alpha Test js-controller 5.0:
2023-04-03 23:27:05.436 debug ERROR YEELIGHT CONNECTION: 0x000000000000000: Connection 192.168.3.140:55443: Error: connect EHOSTUNREACH 192.168.3.140:55443
Also mal abgesehen vom crash tippe ich das eher das dein issue ist ... EHOSTUNREACH heisst das das gerät im Netzwerk nicht da ist ... Ich denke er adapter code schliesst darauf hin das socket was aber nie offen war wegen dem Fehler. Bitte adapter issue anlegen das man das dort fixt ... und schau warum das Geröt nicht online ist
-
Alpha Update
5.0.1-alpha.0-20230406-4552d569
- Fixes compact mode
- Hide warning about "www folder not found" for widgets adapters
Wenn alles so stabil bleibt würde wir überlegen Mitte nächste Woche in den Beta Test im Latest Repo zu gehen ...
-
@apollon77
Keine Auffälligkeiten. Den Compact Mode nutze ich normalerweise nicht. Hab ihn jetzt mal testweise nach langer Suche eingeschaltet (Windows) und merke keinen Unterschied zu vorher. Ist wahrscheinlich gut so, aber kann ich irgendwie kontrollieren, dass er auch wirklich aktiv ist? Hinter jeder Instanz wird jedenfalls noch unterschiedliche RAM Nutzung angezeigt.@apollon77 said in Alpha Test js-controller 5.0:
Hide warning about "www folder not found" for widgets adapters
Dazu kann ich nix sagen, kenne die Warning nicht.
-
So auf den ersten Blick läuft das rund hier. Das Log ist ruhig, ich verwende allerdings auch den CompactMode nicht.
-
@gaspode Compat einschalten macht erstmal nichts. Du musst jetzt Instanzen sagen das sie in compact laufen sollen und eine gruppe angeben (0 ist "Mit controller", 1....n ist eigene Gruppen, je gruppe gibts einen prozess). das geht via admin bei den instanzen. ggf expertenmodus. Dann sollte ram nutzung weg sein bei den instanzen.
