NEWS
Test Adapter Grünbeck v0.0.x
Tester
506
Beiträge
57
Kommentatoren
121.1k
Aufrufe
52
Watching
-
@tombox
Ich habe gestern den Adapter neu installiert und seit dem wird keine Verbindung mehr aufgebaut.
Die Grünbeck SC18 ist über Ping und Webbrowser erreichbar.Im LOG kommt folgende Fehlermeldung:
gruenbeck.0 2022-07-11 16:19:19.904 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (_http_client.js:515:22) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) gruenbeck.0 2022-07-11 16:19:19.904 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 16:19:19.903 debug statechange: 4 432 gruenbeck.0 2022-07-11 16:19:17.686 debug sendRequest gruenbeck.0 2022-07-11 16:19:17.686 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 16:19:17.682 info [INFO] Configured polling interval: 15000 gruenbeck.0 2022-07-11 16:19:17.682 info Connecting to SC Device with:xxx.xxx.xxx.xxx gruenbeck.0 2022-07-11 16:19:17.618 info starting. Version 0.0.41 in /opt/iobroker/node_modules/iobroker.gruenbeck, node: v14.20.0, js-controller: 4.0.23 gruenbeck.0 2022-07-11 16:19:15.902 debug Plugin sentry Initialize Plugin (enabled=true) host.iobroker 2022-07-11 16:19:10.949 info instance system.adapter.gruenbeck.0 started with pid 30117 host.iobroker 2022-07-11 16:19:10.696 info "system.adapter.gruenbeck.0" enabledHast du eine Idee an was das liegen könnte ?
-
@tombox
selbes Problem hier mein log.
Kann nicht sagen seid wann es nicht mehr geht.
Hatte aber gestern nen Neustart nach node update.SC18 auch noch erreichbar über Browser.
gruenbeck.0 2022-07-11 18:17:20.057 debug Error: socket hang up at connResetException (internal/errors.js:639:14) at Socket.socketOnEnd (_http_client.js:499:23) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) gruenbeck.0 2022-07-11 18:17:20.056 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 18:17:20.055 debug statechange: 4 297 gruenbeck.0 2022-07-11 18:17:18.710 debug Powermode schedule not active gruenbeck.0 2022-07-11 18:17:18.698 debug sendRequest gruenbeck.0 2022-07-11 18:17:18.697 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 18:17:18.696 info [INFO] Configured polling interval: 15000 gruenbeck.0 2022-07-11 18:17:18.695 info Connecting to SC Device with:xx.xx.xx.xx gruenbeck.0 2022-07-11 18:17:18.657 info starting. Version 0.0.41 in /opt/iobroker/node_modules/iobroker.gruenbeck, node: v14.20.0, js-controller: 4.0.23 -
@tombox
selbes Problem hier mein log.
Kann nicht sagen seid wann es nicht mehr geht.
Hatte aber gestern nen Neustart nach node update.SC18 auch noch erreichbar über Browser.
gruenbeck.0 2022-07-11 18:17:20.057 debug Error: socket hang up at connResetException (internal/errors.js:639:14) at Socket.socketOnEnd (_http_client.js:499:23) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) gruenbeck.0 2022-07-11 18:17:20.056 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 18:17:20.055 debug statechange: 4 297 gruenbeck.0 2022-07-11 18:17:18.710 debug Powermode schedule not active gruenbeck.0 2022-07-11 18:17:18.698 debug sendRequest gruenbeck.0 2022-07-11 18:17:18.697 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 18:17:18.696 info [INFO] Configured polling interval: 15000 gruenbeck.0 2022-07-11 18:17:18.695 info Connecting to SC Device with:xx.xx.xx.xx gruenbeck.0 2022-07-11 18:17:18.657 info starting. Version 0.0.41 in /opt/iobroker/node_modules/iobroker.gruenbeck, node: v14.20.0, js-controller: 4.0.23 -
@smartboart @ArnoD Auf welchem System läuft euer iobroker
@tombox ioBroker-Master
Plattform: linux RAM: 7.7 GB Node.js: v14.20.0 NPM: 6.14.17Raspi 4 8GB
Debian Buster
-
@tombox ioBroker-Master
Plattform: linux RAM: 7.7 GB Node.js: v14.20.0 NPM: 6.14.17Raspi 4 8GB
Debian Buster
-
@smartboart Aber fängt er sich nach einer weile und kommen irgendwann daten?
@tombox nein. Status ist permanent disconnected. Habe es nur gesehen, weil ich heute mal den Pool nachfüllen musste und die Regeneration nicht manuell starten konnte.
Muss mein Warnicon mal grösser machen.
seit 14:18 kein Sync...siehe Bild. Aber Datum kann ich nicht sagen. -
@tombox nein. Status ist permanent disconnected. Habe es nur gesehen, weil ich heute mal den Pool nachfüllen musste und die Regeneration nicht manuell starten konnte.
Muss mein Warnicon mal grösser machen.
seit 14:18 kein Sync...siehe Bild. Aber Datum kann ich nicht sagen. -
@smartboart Es wäre interessant wie der log weiter geht gerne auch per pn
@tombox ok hab wieder den log auf alöles gestellt und schicke gleich nochmal ne längere sequenz.
Vlt. als Hinweis: Hab es auch mal mit down und upgrade probiert, Dabei standen auch Fehler im log von wegen not supported ...suche den teil und hänge es gleich mal an. -
@tombox ok hab wieder den log auf alöles gestellt und schicke gleich nochmal ne längere sequenz.
Vlt. als Hinweis: Hab es auch mal mit down und upgrade probiert, Dabei standen auch Fehler im log von wegen not supported ...suche den teil und hänge es gleich mal an.@smartboart Ja wäre gut zu wissen ob es mit der 0.0.34 geht
-
@smartboart Ja wäre gut zu wissen ob es mit der 0.0.34 geht
@tombox ok,
versuche gleich die vorgänger Version.
Hier erstmal nen längerer Verlauf.gruenbeck.0 2022-07-11 20:18:16.216 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563496210,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:18:16.202 debug Error: socket hang up at connResetException (internal/errors.js:639:14) at Socket.socketOnEnd (_http_client.js:499:23) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) gruenbeck.0 2022-07-11 20:18:16.201 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:18:16.199 debug statechange: 4 297 gruenbeck.0 2022-07-11 20:18:14.959 debug sendRequest gruenbeck.0 2022-07-11 20:18:14.958 debug id=0000&show=D_A_1_1|D_A_1_2|D_A_2_2|D_A_3_1|D_A_3_2|D_Y_1|D_A_1_3|D_A_2_3|D_Y_5|D_A_2_1|D_C_4_1|D_C_4_3|D_C_1_1|D_C_4_2|D_C_5_1|D_C_6_1|D_C_8_1|D_C_8_2|D_D_1|D_E_1|D_Y_9|D_Y_9_8|D_Y_9_24|D_C_7_1|D_Y_10_1|D_B_1~ gruenbeck.0 2022-07-11 20:18:07.295 debug Resume connections. gruenbeck.0 2022-07-11 20:17:49.346 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.connected gruenbeck.0 2022-07-11 20:17:07.310 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563427306,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:17:07.295 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (_http_client.js:515:22) at Socket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) gruenbeck.0 2022-07-11 20:17:07.294 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:17:07.293 debug statechange: 4 394 gruenbeck.0 2022-07-11 20:17:04.955 debug sendRequest gruenbeck.0 2022-07-11 20:17:04.955 debug id=0000&show=D_A_1_1|D_A_1_2|D_A_2_2|D_A_3_1|D_A_3_2|D_Y_1|D_A_1_3|D_A_2_3|D_Y_5|D_A_2_1|D_C_4_1|D_C_4_3|D_C_1_1|D_C_4_2|D_C_5_1|D_C_6_1|D_C_8_1|D_C_8_2|D_D_1|D_E_1|D_Y_9|D_Y_9_8|D_Y_9_24|D_C_7_1|D_Y_10_1|D_B_1~ gruenbeck.0 2022-07-11 20:16:56.126 debug Resume connections. gruenbeck.0 2022-07-11 20:16:39.844 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.dwd.0.connected gruenbeck.0 2022-07-11 20:15:56.136 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563356133,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:15:56.125 debug Error: socket hang up at connResetException (internal/errors.js:639:14) at Socket.socketOnEnd (_http_client.js:499:23) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) gruenbeck.0 2022-07-11 20:15:56.124 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:15:56.124 debug statechange: 4 297 gruenbeck.0 2022-07-11 20:15:54.951 debug sendRequest gruenbeck.0 2022-07-11 20:15:54.951 debug id=0000&show=D_A_1_1|D_A_1_2|D_A_2_2|D_A_3_1|D_A_3_2|D_Y_1|D_A_1_3|D_A_2_3|D_Y_5|D_A_2_1|D_C_4_1|D_C_4_3|D_C_1_1|D_C_4_2|D_C_5_1|D_C_6_1|D_C_8_1|D_C_8_2|D_D_1|D_E_1|D_Y_9|D_Y_9_8|D_Y_9_24|D_C_7_1|D_Y_10_1|D_B_1~ gruenbeck.0 2022-07-11 20:15:47.293 debug Resume connections. gruenbeck.0 2022-07-11 20:14:47.300 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563287297,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:14:47.293 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (_http_client.js:515:22) at Socket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) gruenbeck.0 2022-07-11 20:14:47.293 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:14:47.292 debug statechange: 4 394 gruenbeck.0 2022-07-11 20:14:44.949 debug sendRequest gruenbeck.0 2022-07-11 20:14:44.948 debug id=0000&show=D_A_1_1|D_A_1_2|D_A_2_2|D_A_3_1|D_A_3_2|D_Y_1|D_A_1_3|D_A_2_3|D_Y_5|D_A_2_1|D_C_4_1|D_C_4_3|D_C_1_1|D_C_4_2|D_C_5_1|D_C_6_1|D_C_8_1|D_C_8_2|D_D_1|D_E_1|D_Y_9|D_Y_9_8|D_Y_9_24|D_C_7_1|D_Y_10_1|D_B_1~ gruenbeck.0 2022-07-11 20:14:36.183 debug Resume connections. gruenbeck.0 2022-07-11 20:13:36.193 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563216191,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:13:36.182 debug Error: socket hang up at connResetException (internal/errors.js:639:14) at Socket.socketOnEnd (_http_client.js:499:23) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) gruenbeck.0 2022-07-11 20:13:36.181 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:13:36.181 debug statechange: 4 297 gruenbeck.0 2022-07-11 20:13:34.942 debug sendRequest gruenbeck.0 2022-07-11 20:13:34.942 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 20:13:26.478 debug Resume connections. gruenbeck.0 2022-07-11 20:12:26.491 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563146487,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:12:26.477 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (_http_client.js:515:22) at Socket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) gruenbeck.0 2022-07-11 20:12:26.476 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:12:26.475 debug statechange: 4 394 gruenbeck.0 2022-07-11 20:12:24.966 silly States system redis pmessage io.system.adapter.gruenbeck.0.logLevel/io.system.adapter.gruenbeck.0.logLevel:{"val":"silly","ack":true,"ts":1657563144939,"q":0,"from":"system.adapter.gruenbeck.0","lc":1657562284709} gruenbeck.0 2022-07-11 20:12:24.935 debug Powermode schedule not active gruenbeck.0 2022-07-11 20:12:24.922 debug sendRequest gruenbeck.0 2022-07-11 20:12:24.921 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 20:12:24.920 info [INFO] Configured polling interval: 15000 gruenbeck.0 2022-07-11 20:12:24.919 info Connecting to SC Device with:192.168.1.24 gruenbeck.0 2022-07-11 20:12:24.878 info starting. Version 0.0.41 in /opt/iobroker/node_modules/iobroker.gruenbeck, node: v14.20.0, js-controller: 4.0.23 gruenbeck.0 2022-07-11 20:12:23.765 debug Plugin sentry destroyed because not initialized correctly gruenbeck.0 2022-07-11 20:12:23.753 debug Plugin sentry Do not initialize Plugin (enabled=false) gruenbeck.0 2022-07-11 20:12:23.696 silly statesDB connected gruenbeck.0 2022-07-11 20:12:23.695 debug States connected to redis: 0.0.0.0:6379 gruenbeck.0 2022-07-11 20:12:23.685 debug States create User PubSub Client gruenbeck.0 2022-07-11 20:12:23.684 debug States create System PubSub Client gruenbeck.0 2022-07-11 20:12:23.676 debug Redis States: Use Redis connection: 0.0.0.0:6379 gruenbeck.0 2022-07-11 20:12:23.673 silly objectDB connected gruenbeck.0 2022-07-11 20:12:23.667 silly redis psubscribe cfg.o.enum.* gruenbeck.0 2022-07-11 20:12:23.423 silly redis psubscribe cfg.o.system.user.* gruenbeck.0 2022-07-11 20:12:23.419 debug Objects connected to redis: 0.0.0.0:6379 gruenbeck.0 2022-07-11 20:12:23.412 debug Objects client initialize lua scripts gruenbeck.0 2022-07-11 20:12:23.199 debug Objects create User PubSub Client gruenbeck.0 2022-07-11 20:12:23.198 debug Objects create System PubSub Client gruenbeck.0 2022-07-11 20:12:23.195 debug Objects client ready ... initialize now gruenbeck.0 2022-07-11 20:12:23.143 debug Redis Objects: Use Redis connection: 0.0.0.0:6379 gruenbeck.0 2022-07-11 20:12:08.096 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason gruenbeck.0 2022-07-11 20:12:08.095 info terminating gruenbeck.0 2022-07-11 20:12:08.092 info Got terminate signal TERMINATE_YOURSELF gruenbeck.0 2022-07-11 20:12:08.091 silly States system redis pmessage io.system.adapter.gruenbeck.0.sigKill/io.system.adapter.gruenbeck.0.sigKill:{"val":-1,"ack":false,"ts":1657563128083,"q":0,"from":"system.host.ioBroker-Master","lc":1657563128083} gruenbeck.0 2022-07-11 20:11:55.857 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.dwd.0.connected gruenbeck.0 2022-07-11 20:11:54.481 silly States user redis pmessage io.gruenbeck.0.*/io.gruenbeck.0.info.connection:{"val":false,"ack":true,"ts":1657563114479,"q":0,"from":"system.adapter.gruenbeck.0","user":"system.user.admin","lc":1657537250517} gruenbeck.0 2022-07-11 20:11:54.474 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (_http_client.js:515:22) at Socket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) gruenbeck.0 2022-07-11 20:11:54.474 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 20:11:54.473 debug statechange: 4 394 gruenbeck.0 2022-07-11 20:11:52.280 debug sendRequest gruenbeck.0 2022-07-11 20:11:52.279 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 20:11:46.296 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.vis.0.connected gruenbeck.0 2022-07-11 20:11:44.107 debug Resume connections. gruenbeck.0 2022-07-11 20:11:43.492 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.feiertage.0.connected gruenbeck.0 2022-07-11 20:11:41.383 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.vis.0.alive gruenbeck.0 2022-07-11 20:11:33.613 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.connected gruenbeck.0 2022-07-11 20:11:30.626 silly system.adapter.logparser.0: logging true gruenbeck.0 2022-07-11 20:11:30.620 silly States system redis pmessage io.*.logging/io.system.adapter.logparser.0.logging:{"val":true,"ack":true,"ts":1657563090597,"q":0,"from":"system.adapter.logparser.0","lc":1657563090597} -
@smartboart Ja wäre gut zu wissen ob es mit der 0.0.34 geht
@tombox
unten mal 2 install logs...beide älteren Versionen gleicher Fehler.
$ iobroker upgrade gruenbeck@0.0.41 --debug Update gruenbeck from @0.0.33 to @0.0.41 NPM version: 6.14.17 Installing iobroker.gruenbeck@0.0.41... (System call) npm WARN deprecated regex@0.1.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated statemachines@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated nomnom@1.5.2: Package no longer supported. Contact support@npmjs.com for more info. npm WARN deprecated sorted-array@1.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN crc@4.1.1 requires a peer of buffer@>=6.0.3 but none is installed. You must install peer dependencies yourself. npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/common@>= 5.0.0 but none is installed. You must install peer dependencies yourself. + iobroker.gruenbeck@0.0.41added 2 packages from 2 contributors, removed 1 package and updated 5 packages in 30.193s 93 packages are looking for funding run `npm fund` for details Update "system.adapter.gruenbeck.0" upload [5] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/admin.d.ts admin.d.ts video/mp2t upload [4] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/gruenbeck.png gruenbeck.png image/png upload [3] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/icon.png icon.png image/png upload [2] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/index_m.html index_m.html text/html upload [1] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/style.css style.css text/css upload [0] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/words.js words.js application/javascript Process exited with code 0$ iobroker upgrade gruenbeck@0.0.33 --debug Update gruenbeck from @0.0.34 to @0.0.33 NPM version: 6.14.17 Installing iobroker.gruenbeck@0.0.33... (System call) npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in. npm WARN deprecated regex@0.1.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated statemachines@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated nomnom@1.5.2: Package no longer supported. Contact support@npmjs.com for more info. npm WARN deprecated sorted-array@1.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN crc@4.1.1 requires a peer of buffer@>=6.0.3 but none is installed. You must install peer dependencies yourself. npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/common@>= 5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/core@>= 5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.gruenbeck@0.0.33updated 1 package in 27.706s 93 packages are looking for funding run `npm fund` for details Update "system.adapter.gruenbeck.0" upload [5] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/admin.d.ts admin.d.ts video/mp2t upload [4] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/gruenbeck.png gruenbeck.png image/png upload [3] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/icon.png icon.png image/png upload [0] gruenbeck.admin /opt/iobroker/node_modules/iobroker.gruenbeck/admin/words.js words.js application/javascript Process exited with code 0 -
@tombox
War bei mir auch nach dem Update auf Nodejs 16.
Bin aber heute wieder zurück auf Node.js v 14.20.0 und NPM 6.14.17, dachte damit das Problem lösen zu können, aber leider ohne Erfolg.
System:
-
Ok Version 0.0.34 installiert und das gleiche Problem
LOG:
gruenbeck.0 2022-07-11 21:02:30.742 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (node:_http_client:494:22) at Socket.emit (node:events:527:28) at Socket.emit (node:domain:475:12) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at Socket.Readable.push (node:internal/streams/readable:228:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) gruenbeck.0 2022-07-11 21:02:30.742 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 21:02:30.741 debug statechange: 4 446 gruenbeck.0 2022-07-11 21:02:28.766 debug sendRequest gruenbeck.0 2022-07-11 21:02:28.766 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 21:02:27.734 debug Resume connections. gruenbeck.0 2022-07-11 21:01:27.733 debug Error: Parse Error: Missing expected CR after header value at Socket.socketOnData (node:_http_client:494:22) at Socket.emit (node:events:527:28) at Socket.emit (node:domain:475:12) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at Socket.Readable.push (node:internal/streams/readable:228:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) gruenbeck.0 2022-07-11 21:01:27.732 info Device cannot handle new connections this is normal. Adapter pause all requests for 1min gruenbeck.0 2022-07-11 21:01:27.731 debug statechange: 4 446 gruenbeck.0 2022-07-11 21:01:25.731 debug sendRequest gruenbeck.0 2022-07-11 21:01:25.730 debug id=0000&code=245&show=D_D_1|D_A_4_1|D_A_4_2|D_A_4_3|D_C_1_1|D_C_2_1|D_C_5_1|D_C_4_1|D_C_4_2|D_C_4_3|D_C_6_1|D_C_7_1|D_A_2_2|D_A_2_3|D_C_3_6_1|D_C_8_1|D_C_8_2|D_C_3_6_2|D_C_3_6_3|D_C_3_6_4|D_C_3_6_5|D_C_3_7_1|D_C_3_7_2|D_C_3_7_3|D_Y_5|D_Y_7|D_Y_6|D_Y_8_11|D_Y_10_1|D_B_1|D_A_1_1|D_A_1_2|D_A_1_3|D_A_2_1|D_A_3_1|D_A_3_2|D_K_1|D_K_2|D_K_3|D_K_4|D_K_7|D_K_8|D_K_9|D_Y_2_1|D_Y_4_1|D_Y_2_2|D_Y_4_2|D_Y_2_3|D_Y_4_3|D_Y_2_4|D_Y_4_4|D_Y_2_5|D_Y_4_5|D_Y_2_6|D_Y_4_6|D_Y_2_7|D_Y_4_7|D_Y_2_8|D_Y_4_8|D_Y_2_9|D_Y_4_9|D_Y_2_10|D_Y_4_10|D_Y_2_11|D_Y_4_11|D_Y_2_12|D_Y_4_12|D_Y_2_13|D_Y_4_13|D_Y_2_14|D_Y_4_14~ gruenbeck.0 2022-07-11 21:01:25.727 debug [INFO] Configured polling interval: 15000 gruenbeck.0 2022-07-11 21:01:25.726 debug Starting gruenbeck adapter with:192.168.1.230 gruenbeck.0 2022-07-11 21:01:25.673 info starting. Version 0.0.34 in /opt/iobroker/node_modules/iobroker.gruenbeck, node: v16.16.0, js-controller: 4.0.23 gruenbeck.0 2022-07-11 21:01:23.143 debug Plugin sentry Initialize Plugin (enabled=true) host.iobroker 2022-07-11 21:01:17.982 info instance system.adapter.gruenbeck.0 started with pid 2677 host.iobroker 2022-07-11 21:01:17.480 info "system.adapter.gruenbeck.0" enabled -
@arnod @smartboart
Ich habe mal die alte Variante wie daten geholt werden aktualisiert. Installiert mal die github version wie es sich dann verhält@tombox habe ich gemacht...keine Änderung.mal sehen was ArnoD schreibt..irgendwas muss sich ja beim Update des Systems negativ auswirken...hab jetzt auch Node und npm auf die empfohlene version gehoben...bringt auch nix...ne idee zu den Installations Meldungen im install log? Oder kann man die vernachlässigen.?
-
@tombox habe ich gemacht...keine Änderung.mal sehen was ArnoD schreibt..irgendwas muss sich ja beim Update des Systems negativ auswirken...hab jetzt auch Node und npm auf die empfohlene version gehoben...bringt auch nix...ne idee zu den Installations Meldungen im install log? Oder kann man die vernachlässigen.?
@smartboart Und Adapter stoppen. Gerät 5min Stromlos. starten und dann adapter starten bringt auch nichts?
-
@tombox habe ich gemacht...keine Änderung.mal sehen was ArnoD schreibt..irgendwas muss sich ja beim Update des Systems negativ auswirken...hab jetzt auch Node und npm auf die empfohlene version gehoben...bringt auch nix...ne idee zu den Installations Meldungen im install log? Oder kann man die vernachlässigen.?
@smartboart Also ich konnte soweit das Problem identifizieren
Node v14.20.0
Node v16.16.0
Node v18.5.0hat ein striktere http header parsing eingebaut.
https://github.com/nodejs/node/commit/f2407748e3Damit werden die inkorrekten ausgaben von gruenbeck als fehler gewertet.
Bisher habe ich keine gute Lösung außer Node v16.15.1 installieren
Support us
792
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge