NEWS
js-controller 5.0.x jetzt in der BETA
-
Bei mir kommt eine Fehlermeldung deren Ursprung ich nicht so richtig lokalisieren kann:
host.ioBroker 2023-06-17 10:02:01.583 error instance system.adapter.web.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker 2023-06-17 10:02:01.582 error Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.ioBroker 2023-06-17 10:02:01.582 error Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1116:27) host.ioBroker 2023-06-17 10:02:01.581 error Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) host.ioBroker 2023-06-17 10:02:01.580 error Caught by controller[1]: Error: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern host.ioBroker 2023-06-17 10:02:01.574 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: web.0 2023-06-17 10:02:00.667 error The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:02:00.667 error Error: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1116:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) web.0 2023-06-17 10:02:00.506 error unhandled promise rejection: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:02:00.497 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().Hat jemand eine Idee wo diese ungültige ID Pattern stehen könnte? Habe ich die eventuell selbst eingebaut, weil ich in der VIS öfter mal mit Bindings gearbeitet habe?
Wenn ich meinen VIS Editor aufrufe habe ich Verbindungsprobleme. Es Kommt immer die Einblendung "no connection" am oberen Rand.Edit: Browser refresh sollte man schon mal machenEdit2:
Die Fehlermeldung ist erweitert:host.ioBroker 2023-06-17 10:22:01.014 error instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at processImmediate (node:internal/timers:476:21) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at Array.forEach (<anonymous>) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) host.ioBroker 2023-06-17 10:22:01.012 error Caught by controller[1]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) host.ioBroker 2023-06-17 10:22:01.012 error Caught by controller[1]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[0]: at processImmediate (node:internal/timers:476:21) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Array.forEach (<anonymous>) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) host.ioBroker 2023-06-17 10:22:01.009 error Caught by controller[0]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) host.ioBroker 2023-06-17 10:22:01.009 error Caught by controller[0]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) host.ioBroker 2023-06-17 10:22:01.009 error Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) host.ioBroker 2023-06-17 10:22:01.006 error Caught by controller[0]: Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:22:00.556 error The pattern "Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:22:00.555 error Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 at Array.forEach (<anonymous>) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) at processImmediate (node:internal/timers:476:21) web.0 2023-06-17 10:22:00.547 error uncaught exception: The pattern "Samstag<br>17.06.2023" is not a valid ID patternioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.
-
Bei mir kommt eine Fehlermeldung deren Ursprung ich nicht so richtig lokalisieren kann:
host.ioBroker 2023-06-17 10:02:01.583 error instance system.adapter.web.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioBroker 2023-06-17 10:02:01.582 error Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.ioBroker 2023-06-17 10:02:01.582 error Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1116:27) host.ioBroker 2023-06-17 10:02:01.581 error Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) host.ioBroker 2023-06-17 10:02:01.580 error Caught by controller[1]: Error: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern host.ioBroker 2023-06-17 10:02:01.574 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: web.0 2023-06-17 10:02:00.667 error The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:02:00.667 error Error: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1116:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) web.0 2023-06-17 10:02:00.506 error unhandled promise rejection: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:02:00.497 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().Hat jemand eine Idee wo diese ungültige ID Pattern stehen könnte? Habe ich die eventuell selbst eingebaut, weil ich in der VIS öfter mal mit Bindings gearbeitet habe?
Wenn ich meinen VIS Editor aufrufe habe ich Verbindungsprobleme. Es Kommt immer die Einblendung "no connection" am oberen Rand.Edit: Browser refresh sollte man schon mal machenEdit2:
Die Fehlermeldung ist erweitert:host.ioBroker 2023-06-17 10:22:01.014 error instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at processImmediate (node:internal/timers:476:21) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at Array.forEach (<anonymous>) host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 host.ioBroker 2023-06-17 10:22:01.013 error Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) host.ioBroker 2023-06-17 10:22:01.012 error Caught by controller[1]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) host.ioBroker 2023-06-17 10:22:01.012 error Caught by controller[1]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[1]: Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern host.ioBroker 2023-06-17 10:22:01.011 error Caught by controller[0]: at processImmediate (node:internal/timers:476:21) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Array.forEach (<anonymous>) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) host.ioBroker 2023-06-17 10:22:01.010 error Caught by controller[0]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) host.ioBroker 2023-06-17 10:22:01.009 error Caught by controller[0]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) host.ioBroker 2023-06-17 10:22:01.009 error Caught by controller[0]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) host.ioBroker 2023-06-17 10:22:01.009 error Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) host.ioBroker 2023-06-17 10:22:01.006 error Caught by controller[0]: Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:22:00.556 error The pattern "Samstag<br>17.06.2023" is not a valid ID pattern web.0 2023-06-17 10:22:00.555 error Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 at Array.forEach (<anonymous>) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) at processImmediate (node:internal/timers:476:21) web.0 2023-06-17 10:22:00.547 error uncaught exception: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern@chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.
Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.
Hier könnt ihr mich unterstützen.
-
@chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.
Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.
@foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:
Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.
Braucht ihr noch ein issue dafür beim Web Adapter?
-
@feuersturm Ja bitte gg
-
@chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.
Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.
@foxriver76 Danke.
Das fehlerhafte binding habe ich mittlerweile lokalisiert:{javascript.0.variables.dayTime.lc;momentDate(dddd)}<br>{javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}Komischerweise läuft das andere Binding in der zweiten View ohne Probleme, obwohl es (fast) gleich ist:
{javascript.0.variables.dayTime.lc;momentDate(dd)} {javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}ioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.
-
@foxriver76 Danke.
Das fehlerhafte binding habe ich mittlerweile lokalisiert:{javascript.0.variables.dayTime.lc;momentDate(dddd)}<br>{javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}Komischerweise läuft das andere Binding in der zweiten View ohne Probleme, obwohl es (fast) gleich ist:
{javascript.0.variables.dayTime.lc;momentDate(dd)} {javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}Update für Problemliste:
linux-control scheint ein Problem zu haben:
https://github.com/Scrounger/ioBroker.linux-control/issues/49Für stiebel-isg und pi-hole dürfte es Updates geben:
Im latest verfügbar (spätestens morgen), stable pending (kurze Karenzzeit erscheint sinnvoll)
https://github.com/ioBroker/ioBroker.repositories/pull/2367 -
Moin zusammen.
bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau :(
Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0
#TeamInventwo
• vis-inventwo & vis-2-widgets-inventwo
• vis-icontwo & vis-2-widgets-icontwo -
Moin zusammen.
bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau :(
Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0
Es scheint an irgendwelchen Widgets zu liegen.
@skvarel sagte in js-controller 5.0.x jetzt in der BETA:
Moin zusammen.
bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau :(
Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0
#TeamInventwo
• vis-inventwo & vis-2-widgets-inventwo
• vis-icontwo & vis-2-widgets-icontwo -
Es scheint an irgendwelchen Widgets zu liegen.
@skvarel sagte in js-controller 5.0.x jetzt in der BETA:
Moin zusammen.
bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau :(
Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0
-
Es scheint an irgendwelchen Widgets zu liegen.
@skvarel sagte in js-controller 5.0.x jetzt in der BETA:
Moin zusammen.
bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau :(
Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0
-
@chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.
Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.
@foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:
@chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.
@Chaot Du kannst dich mit deinem Problem mit an dieses issue hängen: https://github.com/ioBroker/ioBroker.web/issues/316
-
Controller v5.0.5 wird zeitnah verfügbar sein:
- Probleme mit falschem Loglevel bei Beenden von Adaptern behoben
- UI Upgrade wird nur noch angeboten, wenn das Betriebssystem dies unterstützt (das heißt aktuell: nativ Linux oder offizielles ioBroker Docker Image)
- UI Upgrade für offizielles Docker Image eingebaut
- Probleme mit dem Aufruf von
deleteStatein manchen Konstellationen behoben, was zB verhindert hat Geräte in Zigbee zu löschen
Hier könnt ihr mich unterstützen.
-
@foxriver76 Ich hab gerade meinen Master erfolgreich über die Admin GUI auf 5.0.5 aktualisiert.
Als ich jetzt im nächsten Schritt meinen Slave über die Admin GUI aktualisiseren wollte kam folgende Fehlermeldung:
Das Update scheint aber erfolgreich gewesen zu sein. Über die Konsole meldet sich ioBroker mit der Version 5.0.5 sowie auch in der Admin UI.
Das steht im Log vom Slave
2023-06-18 16:52:15.022 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:15.134 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:20.037 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:20.140 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:25.045 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:25.147 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:30.050 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:30.153 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:35.058 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:35.158 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:40.071 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:40.163 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:45.080 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:45.170 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:50.087 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:50.180 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:55.092 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:55.187 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:00.102 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:53:00.194 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:05.116 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:53:05.201 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:53:13.922 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:53:14.033 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:18.929 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:53:19.046 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:23.935 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:53:24.052 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:29.064 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:58:12.225 - info: host.ioBrokerNew Controller will upgrade itself to version 5.0.5 2023-06-18 16:58:16.320 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Stopping controller 2023-06-18 16:58:16.437 - info: host.ioBrokerNew received SIGTERM 2023-06-18 16:58:16.443 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=false) 2023-06-18 16:58:16.444 - info: host.ioBrokerNew stopInstance system.adapter.sql.0 (force=false, process=false) 2023-06-18 16:58:16.445 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=false) 2023-06-18 16:58:16.492 - info: host.ioBrokerNew terminated 2023-06-18 16:58:20.638 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller 2023-06-18 16:58:20.655 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081 2023-06-18 16:58:57.178 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] changed 12 packages in 34s 81 packages are looking for funding run `npm fund` for details 2023-06-18 16:59:07.193 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Timeout expired, initializing shutdown 2023-06-18 16:59:07.286 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller 2023-06-18 16:59:09.687 - info: host.ioBrokerNew iobroker.js-controller version 5.0.5 js-controller starting 2023-06-18 16:59:09.699 - info: host.ioBrokerNew Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-06-18 16:59:09.702 - info: host.ioBrokerNew hostname: ioBrokerNew, node: v18.16.0 2023-06-18 16:59:09.704 - info: host.ioBrokerNew ip addresses: 192.168.178.78 fe80::d4a0:37ff:fe8e:f0c1 2023-06-18 16:59:10.347 - info: host.ioBrokerNew connected to Objects and States 2023-06-18 16:59:10.391 - info: host.ioBrokerNew added notifications configuration of host 2023-06-18 16:59:11.478 - info: host.ioBrokerNew 61 instances found 2023-06-18 16:59:11.603 - warn: host.ioBrokerNew does not start any instances on this hostEdit: Github issue: https://github.com/ioBroker/ioBroker.admin/issues/1963
-
@foxriver76 Ich hab gerade meinen Master erfolgreich über die Admin GUI auf 5.0.5 aktualisiert.
Als ich jetzt im nächsten Schritt meinen Slave über die Admin GUI aktualisiseren wollte kam folgende Fehlermeldung:
Das Update scheint aber erfolgreich gewesen zu sein. Über die Konsole meldet sich ioBroker mit der Version 5.0.5 sowie auch in der Admin UI.
Das steht im Log vom Slave
2023-06-18 16:52:15.022 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:15.134 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:20.037 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:20.140 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:25.045 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:25.147 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:30.050 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:30.153 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:35.058 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:35.158 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:40.071 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:40.163 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:45.080 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:45.170 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:50.087 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:50.180 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:52:55.092 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:52:55.187 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:00.102 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:53:00.194 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:05.116 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:53:05.201 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:53:13.922 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:53:14.033 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:18.929 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-06-18 16:53:19.046 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:23.935 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:53:24.052 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-06-18 16:53:29.064 - info: host.ioBrokerNew Objects database successfully reconnected 2023-06-18 16:58:12.225 - info: host.ioBrokerNew Controller will upgrade itself to version 5.0.5 2023-06-18 16:58:16.320 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Stopping controller 2023-06-18 16:58:16.437 - info: host.ioBrokerNew received SIGTERM 2023-06-18 16:58:16.443 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=false) 2023-06-18 16:58:16.444 - info: host.ioBrokerNew stopInstance system.adapter.sql.0 (force=false, process=false) 2023-06-18 16:58:16.445 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=false) 2023-06-18 16:58:16.492 - info: host.ioBrokerNew terminated 2023-06-18 16:58:20.638 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller 2023-06-18 16:58:20.655 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081 2023-06-18 16:58:57.178 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] changed 12 packages in 34s 81 packages are looking for funding run `npm fund` for details 2023-06-18 16:59:07.193 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Timeout expired, initializing shutdown 2023-06-18 16:59:07.286 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller 2023-06-18 16:59:09.687 - info: host.ioBrokerNew iobroker.js-controller version 5.0.5 js-controller starting 2023-06-18 16:59:09.699 - info: host.ioBrokerNew Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-06-18 16:59:09.702 - info: host.ioBrokerNew hostname: ioBrokerNew, node: v18.16.0 2023-06-18 16:59:09.704 - info: host.ioBrokerNew ip addresses: 192.168.178.78 fe80::d4a0:37ff:fe8e:f0c1 2023-06-18 16:59:10.347 - info: host.ioBrokerNew connected to Objects and States 2023-06-18 16:59:10.391 - info: host.ioBrokerNew added notifications configuration of host 2023-06-18 16:59:11.478 - info: host.ioBrokerNew 61 instances found 2023-06-18 16:59:11.603 - warn: host.ioBrokerNew does not start any instances on this hostEdit: Github issue: https://github.com/ioBroker/ioBroker.admin/issues/1963
@feuersturm danke schaue ich mir mit BF an. Läuft der Admin von dem aus das gestartet wurde auf Master oder Slave? Hat das vorher schon auf Slave mal sauber funktioniert. Logfile selbst schaut sehr gut aus.
Hier könnt ihr mich unterstützen.
-
@feuersturm danke schaue ich mir mit BF an. Läuft der Admin von dem aus das gestartet wurde auf Master oder Slave? Hat das vorher schon auf Slave mal sauber funktioniert. Logfile selbst schaut sehr gut aus.
@foxriver76 der Admin läuft auf dem Master von dem das Update gestartet wurde. Den slave habe ich bisher immer über die Konsole aktualisiert und nicht über die gui.
-
@foxriver76 der Admin läuft auf dem Master von dem das Update gestartet wurde. Den slave habe ich bisher immer über die Konsole aktualisiert und nicht über die gui.
@feuersturm danke für die Info. Ich vermute Admin fragt immer lokal an auch wenn auf anderem Host aktualisiert wird. Muss voraussichtlich in Admin gefixt werden. Schauen wir uns an. 👍🏼
-
@thomas-braun Cool, das schaut sehr gut aus.
@crunchip ich schaue mir das nochmal an, eigentlich wollten wir verhindern, dass DB closed throwed, evtl. haben wir da aus Versehen was kaputt gemacht bei diversen Portierungsarbeiten
@foxriver76 Update wieder per admin mit anschließendem Browser refresh
sieht nun besser aus, aber bei mir hat der shelly nach wie vor Probleme, hatte ich schon mal ne zeitlang, werd ich wohl ggf issue wieder eröffnen2023-06-18 22:14:20.204 - info: host.IoBroker stopInstance system.adapter.countdown.0 send kill signal 2023-06-18 22:14:20.205 - info: host.IoBroker stopInstance system.adapter.tibberconnect.0 send kill signal 2023-06-18 22:14:20.205 - info: host.IoBroker stopInstance system.adapter.opendtu.0 send kill signal 2023-06-18 22:14:20.420 - info: mytime.0 (1104559) terminating with timeout 2023-06-18 22:14:20.423 - info: virtualpowermeter.0 (1105082) terminating 2023-06-18 22:14:20.784 - warn: sonoff.0 (1103739) redis get sonoff.0.PC-Server.alive, error - Connection is closed. 2023-06-18 22:14:20.793 - warn: sonoff.0 (1103739) get state error: Connection is closed. 2023-06-18 22:14:20.794 - warn: sonoff.0 (1103739) redis get sonoff.0.PC-Server.alive, error - DB closed 2023-06-18 22:14:20.757 - warn: shelly.0 (1103714) get state error: Connection is closed. 2023-06-18 22:14:20.767 - error: shelly.0 (1103714) 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(). 2023-06-18 22:14:20.769 - error: shelly.0 (1103714) unhandled promise rejection: DB closed 2023-06-18 22:14:20.973 - error: shelly.0 (1103714) Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7585:34) 2023-06-18 22:14:20.974 - error: shelly.0 (1103714) DB closed 2023-06-18 22:14:21.132 - warn: sonoff.0 (1103739) get state error: Connection is closed. 2023-06-18 22:14:21.173 - warn: sonoff.0 (1103739) get state error: Connection is closed. 2023-06-18 22:14:21.175 - warn: sonoff.0 (1103739) get state error: Connection is closed. 2023-06-18 22:14:21.316 - info: host.IoBroker stopInstance system.adapter.admin.0 killing pid 1103011 2023-06-18 22:14:21.349 - warn: opendtu.0 (1105739) Cannot get view: Connection is closed. 2023-06-18 22:14:21.316 - info: host.IoBroker stopInstance system.adapter.javascript.0 killing pid 1103278 2023-06-18 22:14:21.317 - info: host.IoBroker stopInstance system.adapter.telegram.0 killing pid 1727115 . . 2023-06-18 22:14:27.599 - warn: host.IoBroker instance system.adapter.net-tools.0 terminated due to SIGTERM 2023-06-18 22:14:27.599 - info: host.IoBroker instance system.adapter.net-tools.0 terminated with code null () 2023-06-18 22:14:27.692 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM 2023-06-18 22:14:27.693 - info: host.IoBroker instance system.adapter.nut.0 terminated with code null () 2023-06-18 22:14:27.795 - error: host.IoBroker 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: 2023-06-18 22:14:27.796 - error: host.IoBroker Caught by controller[0]: Error: DB closed 2023-06-18 22:14:27.797 - error: host.IoBroker Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-06-18 22:14:27.798 - error: host.IoBroker Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-06-18 22:14:27.798 - error: host.IoBroker Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-06-18 22:14:27.799 - error: host.IoBroker Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7585:34) 2023-06-18 22:14:27.799 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM . . ansonsten 2023-06-18 22:14:31.618 - info: host.IoBroker All instances are stopped. 2023-06-18 22:14:31.652 - info: host.IoBroker terminated 2023-06-18 22:14:36.282 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller 2023-06-18 22:14:36.290 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081 2023-06-18 22:15:30.526 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] changed 12 packages in 53s 226 packages are looking for funding run `npm fund` for details 2023-06-18 22:15:31.506 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-06-18 22:15:39.805 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller 2023-06-18 22:15:40.972 - info: host.IoBroker iobroker.js-controller version 5.0.5 js-controller starting 2023-06-18 22:15:40.978 - info: host.IoBroker Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-06-18 22:15:40.979 - info: host.IoBroker hostname: IoBroker, node: v18.16.0 2023-06-18 22:15:40.980 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484 2023-06-18 22:15:44.891 - info: host.IoBroker connected to Objects and States 2023-06-18 22:15:45.021 - info: host.IoBroker added notifications configuration of host 2023-06-18 22:15:46.309 - info: host.IoBroker Delete state "system.host.IoBroker.versions.nodeCurrent" 2023-06-18 22:15:46.360 - info: host.IoBroker 139 instances found 2023-06-18 22:15:46.490 - info: host.IoBroker starting 57 instances 2023-06-18 22:15:46.764 - info: host.IoBroker Delete state "system.host.IoBroker.versions.nodeNewest" 2023-06-18 22:15:46.772 - info: host.IoBroker Delete state "system.host.IoBroker.versions.nodeNewestNext" 2023-06-18 22:15:46.778 - info: host.IoBroker Delete state "system.host.IoBroker.versions.npmCurrent" 2023-06-18 22:15:46.852 - info: host.IoBroker instance system.adapter.admin.0 started with pid 3026764 2023-06-18 22:15:46.861 - info: host.IoBroker Delete state "system.host.IoBroker.versions.npmNewest" 2023-06-18 22:15:46.908 - info: host.IoBroker Delete state "system.host.IoBroker.versions.npmNewestNext" 2023-06-18 22:15:46.914 - info: host.IoBroker Some obsolete host states deleted. 2023-06-18 22:15:49.609 - info: admin.0 (3026764) starting. Version 6.5.8 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 5.0.5 2023-06-18 22:15:49.659 - info: admin.0 (3026764) requesting all states 2023-06-18 22:15:49.660 - info: admin.0 (3026764) requesting all objects 2023-06-18 22:15:52.077 - info: host.IoBroker instance system.adapter.history.0 started with pid 3026791 2023-06-18 22:15:52.838 - info: admin.0 (3026764) received all objects 2023-06-18 22:15:53.252 - info: admin.0 (3026764) Request actual repository... 2023-06-18 22:15:53.281 - info: admin.0 (3026764) socket.io server listening on port 8081 2023-06-18 22:15:53.284 - info: admin.0 (3026764) http server listening on port 8081 2023-06-18 22:15:53.285 - info: admin.0 (3026764) Use link "http://127.0.0.1:8081" to configure. -
seit dem Update auf 5.0.5 schmiert mir immer der Zigbee Adapter ab.
2023-06-19 10:01:37.722 - error: host.pi4b 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: 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Hub.configureScope (/opt/iobroker/node_modules/@iobroker/plugin-sentry/node_modules/@sentry/src/hub.ts:340:1) 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Object.configureScope (/opt/iobroker/node_modules/@iobroker/plugin-sentry/node_modules/@sentry/src/exports.ts:76:1) 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-06-19 10:01:37.724 - error: host.pi4b Caught by controller[0]: at Zigbee.filterError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:142:18) 2023-06-19 10:01:37.724 - error: host.pi4b Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:699:22 2023-06-19 10:01:37.724 - error: host.pi4b instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)pi4b@pi4b:/opt/iobroker$ npm ls --depth=3 | grep zigbee └─┬ iobroker.zigbee@1.8.11 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#5add9eafb4da35eedc5655ef3c0a8a919ec873b0) ├─┬ zigbee-herdsman-converters@15.22.0 │ └─┬ zigbee-herdsman@0.15.0 └─┬ zigbee-herdsman@0.14.117 pi4b@pi4b:/opt/iobroker$ -
seit dem Update auf 5.0.5 schmiert mir immer der Zigbee Adapter ab.
2023-06-19 10:01:37.722 - error: host.pi4b 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: 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Hub.configureScope (/opt/iobroker/node_modules/@iobroker/plugin-sentry/node_modules/@sentry/src/hub.ts:340:1) 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Object.configureScope (/opt/iobroker/node_modules/@iobroker/plugin-sentry/node_modules/@sentry/src/exports.ts:76:1) 2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-06-19 10:01:37.724 - error: host.pi4b Caught by controller[0]: at Zigbee.filterError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:142:18) 2023-06-19 10:01:37.724 - error: host.pi4b Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:699:22 2023-06-19 10:01:37.724 - error: host.pi4b instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)pi4b@pi4b:/opt/iobroker$ npm ls --depth=3 | grep zigbee └─┬ iobroker.zigbee@1.8.11 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#5add9eafb4da35eedc5655ef3c0a8a919ec873b0) ├─┬ zigbee-herdsman-converters@15.22.0 │ └─┬ zigbee-herdsman@0.15.0 └─┬ zigbee-herdsman@0.14.117 pi4b@pi4b:/opt/iobroker$Im Spoiler für Entwickler News im ersten Beitrag steht
Support for Node.js 12 is dropped! Supported are Node.js 14.18.0+, 16.4.0+ and 18.x
Wurde nicht node 14 enfalls gekübelt.,oder rwechsel ich das was?
Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
Support Repositoryverwaltung.Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker
-
Im Spoiler für Entwickler News im ersten Beitrag steht
Support for Node.js 12 is dropped! Supported are Node.js 14.18.0+, 16.4.0+ and 18.x
Wurde nicht node 14 enfalls gekübelt.,oder rwechsel ich das was?
@mcm57
Schon von nodejs.org selber. nodejs14 ist EOL.
710
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge