js-controller 5.0.x jetzt in der BETA

[foxriver76]

@malleralle Lt. https://github.com/ioBroker/ioBroker.javascript/issues/1340 tritt das auch mit altem Controller auf, also eher javascript Issue

MK-66 created this issue in ioBroker/ioBroker.javascript

closed Export all scripts does not work since v7.0.5 #1340

[foxriver76]

@einstein67 teils teils, wird im Controller gefixt sein in der nächsten Version.

[apollon77]

@feuersturm Das ist ja im Browser ... da scheint irgendwas mit den Daten im local Storage zu sein ... da kann an sich der controller nix für ... Bitte mal vis issue

[Feuersturm]

@apollon77 mit einem Browser Cache löschen hat sich das Problem gelöst.

[fastfoot]

@malleralle ja, gibt ein issue dazu und für controller 5.x nutzer auch einen Workaround

[fastfoot]

@foxriver76 ja, tritt auch mit altem controller auf, issue gibt es schon
https://github.com/ioBroker/ioBroker.javascript/issues/1340#issuecomment-1591811349

MK-66 created this issue in ioBroker/ioBroker.javascript

closed Export all scripts does not work since v7.0.5 #1340

[Chaot]

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 machen

Edit2:
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

[foxriver76]

@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.

[Feuersturm]

@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?

[foxriver76]

@feuersturm Ja bitte gg

[Chaot]

@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)}

[mcm1957]

@apollon77

Update für Problemliste:

linux-control scheint ein Problem zu haben:
https://github.com/Scrounger/ioBroker.linux-control/issues/49

Fü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

Strobelix80 created this issue in Scrounger/ioBroker.linux-control

closed Error with js-controller 5.x #49

unltdnetworx created this issue in ioBroker/ioBroker.repositories

closed Update sources-dist-stable.json - pi-hole and stiebel-isg #2367

[skvarel]

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

[skvarel]

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

[Marty56]

Ich habe gerade diesen "Alias Error Burst" bekommen.
Schade, es scheint das js-controller 5 hier nicht geholfen hat.

[DJMarc75]

@skvarel Texte in Codetags packen bitte.

[Feuersturm]

@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

Feuer-sturm created this issue in ioBroker/ioBroker.web

closed unvalid binding in vis crashes web adapter with jjs-controller 5.0.4 #316

[foxriver76]

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 deleteState in manchen Konstellationen behoben, was zB verhindert hat Geräte in Zigbee zu löschen

[Feuersturm]

@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 host

Edit: Github issue: https://github.com/ioBroker/ioBroker.admin/issues/1963

Feuer-sturm created this issue in ioBroker/ioBroker.admin

closed Updating js-controller 5.x on Slave over admin "TypeError: Network Error when attempting to fetch ressource" #1963

[foxriver76]

@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.