NEWS
js-controller 5.0.x jetzt in der BETA
-
@mcm57
Kurz zum km200 und js 5.X
Habe km200 auf 2.0.4 aktualisiert gehabt und nur stichprobenartig in meine Datenpunkte geschaut. Abgastemperatur z.B. hat sich korrekt aktualisiert und geändert.
Habe dann auf die 2.0.5 aktualisiert und die Anzahl der Datenpunkte (bei nicht geändertem Filter) ist auf 18 zusammengeschrumpft. Der Datenpunkt Flamme AN/AUS ist zum Beispiel nicht mehr vorhanden. Downgrade auf 2.0.4 hat die Datenpunkte auch nicht zurück gebracht.
Im Log kommt als Warnung nur:INit getservices error TypeError: Cannot create property '0' on boolean 'false' at /opt/iobroker/node_modules/iobroker.km200/km200.js:455:61 at Array.forEach (<anonymous>) at /opt/iobroker/node_modules/iobroker.km200/km200.js:455:37 at /opt/iobroker/node_modules/iobroker.km200/lib/myAdapter.js:822:53Wenn ich den Filter, also die Blacklist komplett leer lasse kommt nur ein Datenpunkt zur Firmware und die anderen 18 sind weg. Für mein Verständnis sollte eine leere Blacklist keine Datenpunkte blockieren.
Ich werde mir den EMS Adapter mal anschauen was der für Daten liefert, vielleicht hat Buderus auch was geändert. Da ich dafür den QR auf dem Brenner brauche wird das allerdings frühestens nächste Woche was, selbiger steht aktuell gut 1000 km entfernt ;-)
Sorry,
Wenn es auch mit der .4 nicht geht hab ich im Moment keine Ahnung.Da es aber - wie ich gestern mitbekommen habe - den ems-esp Adapter gibt laufen zur Zeit Überlegungen den km200 offiziell auf DEPRECATED zu setzen da es einerseits keine Maintainer mit Testmöglichkeit gibt (so wie es aussieht) und andrerseits 2 Adapter für dasselbe Gerät selten Sinn machen.
-
Sorry,
Wenn es auch mit der .4 nicht geht hab ich im Moment keine Ahnung.Da es aber - wie ich gestern mitbekommen habe - den ems-esp Adapter gibt laufen zur Zeit Überlegungen den km200 offiziell auf DEPRECATED zu setzen da es einerseits keine Maintainer mit Testmöglichkeit gibt (so wie es aussieht) und andrerseits 2 Adapter für dasselbe Gerät selten Sinn machen.
@mcm57
Kein Grund sich zu entschuldigen, ich hab da auf jeden Fall noch weniger Ahnung von :D
Ich schaue mir nächste Woche den EMS Adapter an. Wenn der die gleiche (ähnliche) Funktionalität bietet wäre der km200 für mich obsolet. -
@apollon77
Update auf 5.0.7 verlief Problemlos und alles scheint zu funktionieren.
Lediglich eine Fehlermeldung:host.ioBroker 2023-07-10 22:33:52.784 error [CONTROLLER_AUTO_UPGRADE] npm WARN skipping integrity check for git dependency ssh://git@github.com/gerbuchner/ioBroker.vis-owl.git npm WARN skipping integrity check for git dependency ssh://git@github.com/aendue/ioBroker.reolink.git npm WARN skipping integrity check for git dependency ssh://git@github.com/xXBJXx/ioBroker.fully-tablet-control.git npm WARN skipping integrity check for git dependency ssh://git@github.com/nVuln/homebridge-lg-thinq.gitScheinen wohl alte Adapterleichen zu sein, wenn ich das richtig verstehe.
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.
-
js-controller 5.0.7 wurde auch auf meinem Master / Slave System aktualisiert und beide ioBrokers sind ohne Probleme gestartet
-
@foxriver76 gerne, ich hab zwar Vis installiert, benutze das aber nicht. Meine view wird mit MinuVis dargestellt.
System: Debian Bookworm, Proxmox lxc, Node 18.16.1, NPM 9.5.1, Admin 6.6.0, JS Controller 5.0.72023-07-10 13:21:00.633 - error: host.iobrokerS2 cannot call visUtils: Not existsWas ist das VisUtils…?
@ilovegym Ist Code, der schaut wie viele vis Projekte, DPs, etc. du hast. Allerdings nur für statistische Zwecke.
Die Frage ist, tritt das bei anderen auch noch auf?
D.h. du hast in deinem Fall kein einziges vis-Projekt oder ist das default noch da?
-
@ilovegym Ist Code, der schaut wie viele vis Projekte, DPs, etc. du hast. Allerdings nur für statistische Zwecke.
Die Frage ist, tritt das bei anderen auch noch auf?
D.h. du hast in deinem Fall kein einziges vis-Projekt oder ist das default noch da?
@foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:
@ilovegym Ist Code, der schaut wie viele vis Projekte, DPs, etc. du hast. Allerdings nur für statistische Zwecke.
Die Frage ist, tritt das bei anderen auch noch auf?
D.h. du hast in deinem Fall kein einziges vis-Projekt oder ist das default noch da?
Objekte: 116948, Zustände: 98389, 78 Adapter, insgesamt so um die 650 Devices..
definitiv default.. irgendwann vor 3 oder 4 Jahren mit js-controller 1.21 mal gestartet, fuer seltsam befunden und seitdem nicht mehr angerührt.. :-)
Instanz irgendwie immer mal mitgeschleppt... auch zwischendurch mal geloescht gehabt, aber irgenwelche Adapter hatten dann gemeckert.. also wieder installiert..
Eben mal aufgerufen, da kam das:
habs jetzt n paarmal weg geclickt und n iob upload vis gemacht, jetzt kommt der Default..
sieht jetzt so aus, als ob der Fehler mit den VisUtils nicht mehr kommt.. war anscheinend was in dem Vis verbogen oder nicht vorhanden, weil nie benutzt..
Haben die anderen diesen Fehler auch (noch?)...
-
@apollon77
Update auf 5.0.7 verlief Problemlos und alles scheint zu funktionieren.
Lediglich eine Fehlermeldung:host.ioBroker 2023-07-10 22:33:52.784 error [CONTROLLER_AUTO_UPGRADE] npm WARN skipping integrity check for git dependency ssh://git@github.com/gerbuchner/ioBroker.vis-owl.git npm WARN skipping integrity check for git dependency ssh://git@github.com/aendue/ioBroker.reolink.git npm WARN skipping integrity check for git dependency ssh://git@github.com/xXBJXx/ioBroker.fully-tablet-control.git npm WARN skipping integrity check for git dependency ssh://git@github.com/nVuln/homebridge-lg-thinq.gitScheinen wohl alte Adapterleichen zu sein, wenn ich das richtig verstehe.
@chaot
Kommen diese skipping integrity check meldungen nicht IMMER wenn von github installiert wird? Kann es sein dass die gelisteten Adapter allesamt github Installationen sind?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
-
@chaot
Kommen diese skipping integrity check meldungen nicht IMMER wenn von github installiert wird? Kann es sein dass die gelisteten Adapter allesamt github Installationen sind? -
Raspi4, NPM 9.5.1,Node.js v18.16.0, JSController 5.0.7
Ich bekomme seit Installation des ViessmannAPI Adapters nur noch Fehler und kann nicht mehr auf Objekte zugreifen. Hier rotiert nur noch dieser Kreis.
Kann mir jemand was dazu sagen?
admin.0 10647 2023-07-15 13:14:47.947 info terminating http server on port 8081 admin.0 10647 2023-07-15 13:14:47.857 error The pattern "viessmannapi.0.2277908.0.general.roles.capability:monetization;AdvancedReport" is not a valid ID pattern admin.0 10647 2023-07-15 13:14:47.856 error Error: The pattern "viessmannapi.0.2277908.0.general.roles.capability:monetization;AdvancedReport" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2473:15) at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) at SocketCommandsAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) at SocketCommandsAdmin._subscribeStates (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) at Object.commands.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) at Socket.<anonymous> (/opt/iobroker/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) admin.0 10647 2023-07-15 13:14:47.855 error uncaught exception: The pattern "viessmannapi.0.2277908.0.general.roles.capability:monetization;AdvancedReport" is not a valid ID pattern admin.0 10647 2023-07-15 13:14:47.817 error The pattern "viessmannapi.0.2277908.0.general.roles.capability:backup;0002_HMU_VD2" is not a valid ID pattern admin.0 10647 2023-07-15 13:14:47.816 error Error: The pattern "viessmannapi.0.2277908.0.general.roles.capability:backup;0002_HMU_VD2" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2473:15) at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) at SocketCommandsAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) at SocketCommandsAdmin._subscribeStates (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) at Object.commands.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) at Socket.<anonymous> (/opt/iobroker/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) admin.0 10647 2023-07-15 13:14:47.815 error uncaught exception: The pattern "viessmannapi.0.2277908.0.general.roles.capability:backup;0002_HMU_VD2" is not a valid ID pattern -
Neue erkannte Probleme, die noch nicht behandelt sind:
- stiebel-isg update nötig
- lgtv sollte fixed sein mit 1.1.12
- web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
- js-controller upgrade via Admin startet js-controller nicht wieder
- Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
- km200 sollte gefixt sein mit 2.0.4
- miio muss geprüft werden
- fakeroku GitHub Version gefixt, release fehlt noch
- pi-hole update nötig
- node-red muss geprüft werden
- enigma2.0 mindestens 1.4.0+
- doorbird update nötig
- linux-control update nötig
@apollon77 said in js-controller 5.0.x jetzt in der BETA:
Neue erkannte Probleme, die noch nicht behandelt sind:
- stiebel-isg update nötig
- lgtv sollte fixed sein mit 1.1.12
- web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
- js-controller upgrade via Admin startet js-controller nicht wieder
- Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
- km200 sollte gefixt sein mit 2.0.4
- miio muss geprüft werden
- fakeroku GitHub Version gefixt, release fehlt noch
- pi-hole update nötig
- node-red muss geprüft werden
- enigma2.0 mindestens 1.4.0+
- doorbird update nötig
- linux-control update nötig
Liste wär anzupassen:
Km200 funktioniert weder in 1.4 noch 1.5 stabil.
Km200 wurde deprecated und wir - sollte sich nicht noch ein dev finden - ab js controller 5.x nicht mehr laufen. ems-esp existiert als ersatz.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
-
Controller 5.0.8 auf dem Weg:
- remove duplicate logging and fix https prefix on ssl server (controller upgrade)
- requireLog should not throw on invalid permissions
- fixed multihost communication upgrade manager (erstmals testbar beim update von v5.0.8 auf eine potentielle 5.0.9)
- try to solve
ENOTEMPTYerrors automatically on adapter upgrades/installations
Update von 5.0.7 auf 5.0.8 kann auch erstmals mit offiziellem Docker Container (mindestens v8.1.0-beta.3) erfolgreich stattfinden. Hierzu gerne Feedback geben.
Hier könnt ihr mich unterstützen.
-
->
SyntaxError: Unexpected token '<', "<!doctype "... is not valid JSON2023-07-10 07:22:33.789 - info: host.iobroker-testsystem8 Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json" 2023-07-10 07:23:44.644 - info: host.iobroker-testsystem8 Controller will upgrade itself to version 5.0.7 2023-07-10 07:23:50.402 - info: host.iobroker-testsystem8 [CONTROLLER_AUTO_UPGRADE] Stopping controllerioBroker.admin: v6.6.0
ioBroker.js-controller: v5.0.6 -> v5.0.7
Plattform: ioBroker.docker v8.1.0-beta.3
Betriebssystem: linux
Architektur: x64
Node.js: v18.16.1
NPM: 9.5.1
ioBroker.admin: v6.6.0
ioBroker.js-controller: v5.0.7 -> v5.0.8
Plattform: ioBroker.docker v8.1.0-beta.3
Betriebssystem: linux
Architektur: x64
Node.js: v18.16.1
NPM: 9.5.1 -
ioBroker.admin: v6.6.0
ioBroker.js-controller: v5.0.7 -> v5.0.8
Plattform: ioBroker.docker v8.1.0-beta.3
Betriebssystem: linux
Architektur: x64
Node.js: v18.16.1
NPM: 9.5.1 -
Ist das Problem mit Iqontrol bekannt?
2023-07-16 09:21:35.737 - info: host.Beelink "system.adapter.iqontrol.0" enabled 2023-07-16 09:21:35.794 - info: host.Beelink instance system.adapter.iqontrol.0 started with pid 20691 2023-07-16 09:21:36.657 - info: iqontrol.0 (20691) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v18.16.1, js-controller: 5.0.8 2023-07-16 09:21:36.673 - error: iqontrol.0 (20691) 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-07-16 09:21:36.673 - error: iqontrol.0 (20691) unhandled promise rejection: Parameter "options" needs to be a real object but type "string" has been passed 2023-07-16 09:21:36.821 - error: iqontrol.0 (20691) Error: Parameter "options" needs to be a real object but type "string" has been passed at Function.assertObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:301:19) at Iqontrol.getObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:3587:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2312:16 at new Promise () at Iqontrol.getObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2311:16) at Iqontrol.createOrUpdateObject (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1673:25) at Iqontrol.createInfoConnection (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:413:14) at Iqontrol.onReady (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1779:14) at Iqontrol.emit (node:events:513:28) at Iqontrol.emit (node:domain:489:12) 2023-07-16 09:21:36.822 - error: iqontrol.0 (20691) Parameter "options" needs to be a real object but type "string" has been passed 2023-07-16 09:21:36.831 - info: iqontrol.0 (20691) Stop trigger intervals... 2023-07-16 09:21:36.832 - info: iqontrol.0 (20691) cleaned everything up... 2023-07-16 09:21:36.832 - info: iqontrol.0 (20691) terminating 2023-07-16 09:21:36.833 - warn: iqontrol.0 (20691) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-16 09:21:37.336 - info: iqontrol.0 (20691) terminating 2023-07-16 09:21:37.408 - error: host.Beelink 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-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: Error: Parameter "options" needs to be a real object but type "string" has been passed 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Function.assertObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:301:19) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.getObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:3587:23) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2312:16 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at new Promise () 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.getObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2311:16) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.createOrUpdateObject (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1673:25) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.createInfoConnection (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:413:14) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.onReady (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1779:14) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.emit (node:events:513:28) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.emit (node:domain:489:12) 2023-07-16 09:21:37.408 - error: host.Beelink instance system.adapter.iqontrol.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-16 09:21:37.409 - info: host.Beelink Restart adapter system.adapter.iqontrol.0 because enabledMit der stable Version läufts
-
Seit dem Update von js-controller 5.0.7 -> 5.0.8 startet mein zigbee v1.8.17 nicht mehr.
host.iobroker 2023-07-16 07:23:46.497 error instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: Node.js v18.16.1 host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at node:internal/main/run_main_module:23:47 host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1220:27) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1178:20) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at internalCompileFunction (node:internal/vm:73:18) host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: SyntaxError: missing ) after argument list host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: ^^^^^ host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: this.log.error(`Error ${error.code} on send command to ${payload.device}.` + ` Error: ${error.stack} ` + `Send command to ${payload.device} failed with ` + error; host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/main.js:791 -
Seit dem Update von js-controller 5.0.7 -> 5.0.8 startet mein zigbee v1.8.17 nicht mehr.
host.iobroker 2023-07-16 07:23:46.497 error instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: Node.js v18.16.1 host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at node:internal/main/run_main_module:23:47 host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1220:27) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1178:20) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at internalCompileFunction (node:internal/vm:73:18) host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: SyntaxError: missing ) after argument list host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: ^^^^^ host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: this.log.error(`Error ${error.code} on send command to ${payload.device}.` + ` Error: ${error.stack} ` + `Send command to ${payload.device} failed with ` + error; host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/main.js:791@marius-schäfer
Das liegt aber am Zigbee ;)
Weil v1.8.17 läuft auch mit 5.0.7 nicht.https://forum.iobroker.net/topic/66893/zigbee-1-8-17-bleibt-rot/2
-
Ist das Problem mit Iqontrol bekannt?
2023-07-16 09:21:35.737 - info: host.Beelink "system.adapter.iqontrol.0" enabled 2023-07-16 09:21:35.794 - info: host.Beelink instance system.adapter.iqontrol.0 started with pid 20691 2023-07-16 09:21:36.657 - info: iqontrol.0 (20691) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v18.16.1, js-controller: 5.0.8 2023-07-16 09:21:36.673 - error: iqontrol.0 (20691) 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-07-16 09:21:36.673 - error: iqontrol.0 (20691) unhandled promise rejection: Parameter "options" needs to be a real object but type "string" has been passed 2023-07-16 09:21:36.821 - error: iqontrol.0 (20691) Error: Parameter "options" needs to be a real object but type "string" has been passed at Function.assertObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:301:19) at Iqontrol.getObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:3587:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2312:16 at new Promise () at Iqontrol.getObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2311:16) at Iqontrol.createOrUpdateObject (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1673:25) at Iqontrol.createInfoConnection (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:413:14) at Iqontrol.onReady (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1779:14) at Iqontrol.emit (node:events:513:28) at Iqontrol.emit (node:domain:489:12) 2023-07-16 09:21:36.822 - error: iqontrol.0 (20691) Parameter "options" needs to be a real object but type "string" has been passed 2023-07-16 09:21:36.831 - info: iqontrol.0 (20691) Stop trigger intervals... 2023-07-16 09:21:36.832 - info: iqontrol.0 (20691) cleaned everything up... 2023-07-16 09:21:36.832 - info: iqontrol.0 (20691) terminating 2023-07-16 09:21:36.833 - warn: iqontrol.0 (20691) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-16 09:21:37.336 - info: iqontrol.0 (20691) terminating 2023-07-16 09:21:37.408 - error: host.Beelink 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-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: Error: Parameter "options" needs to be a real object but type "string" has been passed 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Function.assertObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:301:19) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.getObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:3587:23) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2312:16 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at new Promise () 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.getObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2311:16) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.createOrUpdateObject (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1673:25) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.createInfoConnection (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:413:14) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.onReady (/opt/iobroker/node_modules/iobroker.iqontrol/main.js:1779:14) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.emit (node:events:513:28) 2023-07-16 09:21:37.408 - error: host.Beelink Caught by controller[1]: at Iqontrol.emit (node:domain:489:12) 2023-07-16 09:21:37.408 - error: host.Beelink instance system.adapter.iqontrol.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-16 09:21:37.409 - info: host.Beelink Restart adapter system.adapter.iqontrol.0 because enabledMit der stable Version läufts
@jan1 said in js-controller 5.0.x jetzt in der BETA:
Ist das Problem mit Iqontrol bekannt?
-
@marius-schäfer
Das liegt aber am Zigbee ;)
Weil v1.8.17 läuft auch mit 5.0.7 nicht.https://forum.iobroker.net/topic/66893/zigbee-1-8-17-bleibt-rot/2
-
Seit dem Update von js-controller 5.0.7 -> 5.0.8 startet mein zigbee v1.8.17 nicht mehr.
host.iobroker 2023-07-16 07:23:46.497 error instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: Node.js v18.16.1 host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at node:internal/main/run_main_module:23:47 host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1220:27) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1178:20) host.iobroker 2023-07-16 07:23:46.497 error Caught by controller[0]: at internalCompileFunction (node:internal/vm:73:18) host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: SyntaxError: missing ) after argument list host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: ^^^^^ host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: this.log.error(`Error ${error.code} on send command to ${payload.device}.` + ` Error: ${error.stack} ` + `Send command to ${payload.device} failed with ` + error; host.iobroker 2023-07-16 07:23:46.496 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/main.js:791@marius-schäfer installier die GIT version oder warte auf 1.8.18..
-
Controller 5.0.8 auf dem Weg:
- remove duplicate logging and fix https prefix on ssl server (controller upgrade)
- requireLog should not throw on invalid permissions
- fixed multihost communication upgrade manager (erstmals testbar beim update von v5.0.8 auf eine potentielle 5.0.9)
- try to solve
ENOTEMPTYerrors automatically on adapter upgrades/installations
Update von 5.0.7 auf 5.0.8 kann auch erstmals mit offiziellem Docker Container (mindestens v8.1.0-beta.3) erfolgreich stattfinden. Hierzu gerne Feedback geben.
@foxriver76 Update auf Master Slave Testsystem war erfolgreich
Beim Master kommt nach dem Update auf 5.0.8 und starten des Controllers folgende Warnung
2023-07-16 12:37:00.799 - warn: host.ioBrokerTestsystem-Server Objects 192.168.178.78:58884 Error from InMemDB: Error: Unknown Script b0bd9e6fd92479ccf43654a7ba7443c915d0a742 at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/build/lib/objects/objectsInMemServerRedis.js:301:59) at RedisHandler.emit (node:events:513:28) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/build/lib/redisHandler.js:132:37) at process.processImmediate (node:internal/timers:476:21)Log Master:
2023-07-16 12:35:28.691 - info: host.ioBrokerTestsystem All instances are stopped. 2023-07-16 12:35:28.827 - info: host.ioBrokerTestsystem terminated 2023-07-16 12:35:33.225 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller 2023-07-16 12:35:33.242 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081 2023-07-16 12:36:48.197 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] removed 123 packages, and changed 21 packages in 1m 143 packages are looking for funding run `npm fund` for details 2023-07-16 12:36:48.872 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:36:54.084 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller 2023-07-16 12:36:58.279 - info: host.ioBrokerTestsystem iobroker.js-controller version 5.0.8 js-controller starting 2023-07-16 12:36:58.292 - info: host.ioBrokerTestsystem Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-07-16 12:36:58.295 - info: host.ioBrokerTestsystem hostname: ioBrokerTestsystem, node: v18.16.1 2023-07-16 12:36:58.308 - info: host.ioBrokerTestsystem ip addresses: 192.168.178.77 fe80::f854:cfff:fe5f:6c25 2023-07-16 12:37:00.799 - warn: host.ioBrokerTestsystem-Server Objects 192.168.178.78:58884 Error from InMemDB: Error: Unknown Script b0bd9e6fd92479ccf43654a7ba7443c915d0a742 at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/build/lib/objects/objectsInMemServerRedis.js:301:59) at RedisHandler.emit (node:events:513:28) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/build/lib/redisHandler.js:132:37) at process.processImmediate (node:internal/timers:476:21) 2023-07-16 12:37:02.688 - info: host.ioBrokerTestsystem connected to Objects and States 2023-07-16 12:37:02.834 - info: host.ioBrokerTestsystem added notifications configuration of host 2023-07-16 12:37:04.623 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.nodeCurrent" 2023-07-16 12:37:04.627 - info: host.ioBrokerTestsystem 62 instances found 2023-07-16 12:37:04.812 - info: host.ioBrokerTestsystem starting 36 instancesIm Log vom Slave taucht ein paar Mal diese Meldung auf (während der Master aktualisiert wird).
2023-07-16 12:36:34.300 - error: host.ioBrokerNew Could not execute primary host determination: Error Unknown Script b0bd9e6fd92479ccf43654a7ba7443c915d0a7422023-07-16 02:12:48.100 - info: host.ioBrokerNew Delete log file iobroker.2023-07-08.log.gz 2023-07-16 12:35:33.812 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:35:33.848 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:35:38.832 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:35:38.860 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:35:43.842 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:35:43.870 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:35:48.858 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:35:48.883 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:35:53.864 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:35:53.905 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:35:58.892 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:35:58.912 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:03.900 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:03.923 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:08.907 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:08.935 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:13.922 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:13.943 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:18.929 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:18.950 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:23.946 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:23.956 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:28.953 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:28.963 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:33.967 - info: host.ioBrokerNew Objects database successfully reconnected 2023-07-16 12:36:33.974 - info: host.ioBrokerNew Objects database successfully reconnected 2023-07-16 12:36:34.300 - error: host.ioBrokerNew Could not execute primary host determination: Error Unknown Script b0bd9e6fd92479ccf43654a7ba7443c915d0a742 2023-07-16 12:36:34.302 - error: host.ioBrokerNew Could not execute primary host determination: Error Unknown Script b0bd9e6fd92479ccf43654a7ba7443c915d0a742 2023-07-16 12:36:45.498 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:45.575 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:50.505 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:50.584 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:36:55.517 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001 2023-07-16 12:36:55.589 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:37:00.524 - info: host.ioBrokerNew Objects database successfully reconnected 2023-07-16 12:37:00.595 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000 2023-07-16 12:37:00.859 - error: host.ioBrokerNew Could not execute primary host determination: Error Unknown Script b0bd9e6fd92479ccf43654a7ba7443c915d0a742 2023-07-16 12:37:05.601 - info: host.ioBrokerNew Objects database successfully reconnected 2023-07-16 12:42:21.065 - info: host.ioBrokerNew Controller will upgrade itself to version 5.0.8 2023-07-16 12:42:25.561 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Stopping controller 2023-07-16 12:42:25.701 - info: host.ioBrokerNew received SIGTERM 2023-07-16 12:42:25.707 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=false) 2023-07-16 12:42:25.708 - info: host.ioBrokerNew stopInstance system.adapter.sql.0 (force=false, process=false) 2023-07-16 12:42:25.710 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=false) 2023-07-16 12:42:25.789 - info: host.ioBrokerNew terminated 2023-07-16 12:42:29.896 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller 2023-07-16 12:42:29.915 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081 2023-07-16 12:43:21.442 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] changed 19 packages in 48s 81 packages are looking for funding run `npm fund` for details 2023-07-16 12:43:22.417 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:23.423 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:25.447 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:26.460 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:27.468 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:28.480 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:29.495 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:30.498 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:31.504 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:32.508 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:33.521 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:34.534 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:35.549 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:36.548 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:37.562 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:38.582 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:39.589 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:40.596 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:41.602 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:42.605 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:43.620 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:44.631 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:45.636 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:46.650 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:47.655 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:48.665 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:49.676 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:50.682 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:51.687 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:52.699 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:53.700 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:54.709 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:55.736 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:56.722 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:57.727 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:58.747 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:43:59.745 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:00.754 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:01.760 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:02.768 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:03.776 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:04.783 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:05.796 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:06.789 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:07.806 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:08.810 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:09.819 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:10.828 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:11.842 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:12.851 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:13.855 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:14.874 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:15.878 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:16.883 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:17.905 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:18.905 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:19.915 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:20.922 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:21.934 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered 2023-07-16 12:44:24.588 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller 2023-07-16 12:44:26.169 - info: host.ioBrokerNew iobroker.js-controller version 5.0.8 js-controller starting 2023-07-16 12:44:26.180 - info: host.ioBrokerNew Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-07-16 12:44:26.182 - info: host.ioBrokerNew hostname: ioBrokerNew, node: v18.16.0 2023-07-16 12:44:26.185 - info: host.ioBrokerNew ip addresses: 192.168.178.78 fe80::d4a0:37ff:fe8e:f0c1 2023-07-16 12:44:26.843 - info: host.ioBrokerNew connected to Objects and States 2023-07-16 12:44:26.900 - info: host.ioBrokerNew added notifications configuration of host 2023-07-16 12:44:28.166 - info: host.ioBrokerNew 62 instances found 2023-07-16 12:44:28.214 - warn: host.ioBrokerNew does not start any instances on this hostDiese Warnung/Fehler ist mir bisher noch nicht aufgefallen. Vielleicht könnt ihr damit etwas anfangen.
814
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge