Alpha Test js-controller Kiera (v6.0)
-
echad@chet:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller@next --omit=dev npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: @iobroker/adapter-core@3.1.4 npm WARN Found: @iobroker/types@5.0.20-alpha.0-20240522-9b71d3242 npm WARN node_modules/iobroker.admin/node_modules/@iobroker/types npm WARN @iobroker/types@"5.0.20-alpha.0-20240522-9b71d3242" from iobroker.admin@6.17.13 npm WARN node_modules/iobroker.admin npm WARN iobroker.admin@"6.17.13" from the root project npm WARN npm WARN Could not resolve dependency: npm WARN peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm WARN node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm WARN @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.13 npm WARN node_modules/iobroker.admin npm WARN npm WARN Conflicting peer dependency: @iobroker/types@5.0.19 npm WARN node_modules/@iobroker/types npm WARN peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm WARN node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm WARN @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.13 npm WARN node_modules/iobroker.admin added 35 packages, removed 196 packages, and changed 16 packages in 59s 189 packages are looking for funding run `npm fund` for details echad@chet:/opt/iobroker $Die Meldungen zum Build mit letsencrypt sind weg, das Log ist soweit ruhig.
-
Das Thema mit den Skripten hab ich auch eingrenzen können. Ich hatte ein externes npm-Modul eingetragen. Das Ding sorgt im Moment für diese Fehlermeldungen:
2024-05-25 12:54:44.240 - info: javascript.0 (170137) starting. Version 8.3.1 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240525-56d9e4a2e 2024-05-25 12:54:54.549 - error: javascript.0 (170137) An error happened which is most likely from one of your scripts, but the originating script could not be detected. 2024-05-25 12:54:54.550 - error: javascript.0 (170137) Error: Cannot find package '/opt/iobroker/node_modules/@iobroker-javascript.0/playactor/package.json' imported from /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js 2024-05-25 12:54:54.551 - error: javascript.0 (170137) Error: Cannot find package '/opt/iobroker/node_modules/@iobroker-javascript.0/playactor/package.json' imported from /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js at legacyMainResolve (node:internal/modules/esm/resolve:215:26) at packageResolve (node:internal/modules/esm/resolve:841:14) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1157:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleLoader.import (node:internal/modules/esm/loader:315:34) at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31) at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12) 2024-05-25 12:54:54.549 - error: javascript.0 (170137) An error happened which is most likely from one of your scripts, but the originating script could not be detected. 2024-05-25 12:54:54.550 - error: javascript.0 (170137) Error: Cannot find package '/opt/iobroker/node_modules/@iobroker-javascript.0/playactor/package.json' imported from /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js 2024-05-25 12:54:54.551 - error: javascript.0 (170137) Error: Cannot find package '/opt/iobroker/node_modules/@iobroker-javascript.0/playactor/package.json' imported from /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js at legacyMainResolve (node:internal/modules/esm/resolve:215:26) at packageResolve (node:internal/modules/esm/resolve:841:14) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1157:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleLoader.import (node:internal/modules/esm/loader:315:34) at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31) at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12)Wenn ich das Modul
playactorherausnehme starten die anderen Skripte korrekt. -
@thomas-braun ah top. Evtl. Kann @haus-automatisierung was zu sagen ob da aktuell noch was falsch läuft das bekannt ist, ansonsten kann ich auch mal rein schauen.
-
Update lief durch, nur der Heatcontrol Adapter startet wie zuvor nicht.
Soll ich ein issue beim Adapter öffnen? -
@fortune95 welche Version hat dein Admin?
Und mal bitte
npm ls @iobroker/adapter-coreAusgabe zeigen -
Der Admin hat die Version 6.17.13
iobroker@iobroker:~$ npm ls @iobroker/adapter-core iobroker@ /home/iobroker `-- iobroker.js-controller@6.0.1-alpha.0-20240522-72e34be5c `-- @iobroker/adapter-core@3.1.4 -
@thomas-braun said in Alpha Test js-controller Kiera (v6.0):
Wenn ich das Modul
playactorherausnehme starten die anderen Skripte korrekt.Bitte jedenfalls mit aktuellster Version testen:
https://github.com/ioBroker/ioBroker.javascript#840-2024-05-25
8.4.0 (2024-05-25)
(klein0r) Added checks/warnings for more incorrect blockly connections
(klein0r) Added option to disable certificate validation in httpGet
(klein0r) Added expire option to Blockly block
(klein0r) Fixed variables.astro times when date is not available
(klein0r) Fixed jsonConfig for libraries and library typings
(klein0r) Implemented new js-controller 6.x functions for package handling
(klein0r) Updated to ChatGPT-4o -
Bestimmt falsch unterwegs, an der Stelle liegt kein npm-Modul...
echad@chet:/home/iobroker $ npm ls @iobroker/adapter-core /home/iobroker `-- (empty) echad@chet:/home/iobroker $ -
@fortune95 im folder
/opt/iobrokerbitte das Kommando ausführen. -
iobroker@iobroker:/opt/iobroker$ npm ls @iobroker/adapter-core iobroker.inst@3.0.0 /opt/iobroker +-- iobroker.admin@6.17.13 | +-- @iobroker/adapter-core@3.1.4 | `-- @iobroker/socket-classes@1.5.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.alias-manager@1.2.6 | `-- @iobroker/adapter-core@2.6.12 +-- iobroker.backitup@2.11.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.bydhvs@1.5.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.daswetter@3.1.13 | `-- @iobroker/adapter-core@3.0.4 +-- iobroker.device-reminder@3.1.2 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.discovery@4.5.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.dwd@2.8.5 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.ebus@3.3.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.energiefluss-erweitert@0.4.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.esphome@0.5.0-beta.8 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.feiertage@1.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.fritzdect@2.5.9 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.gruenbeck@0.0.43 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.heatingcontrol@2.12.5 | `-- @iobroker/adapter-core@3.0.4 +-- iobroker.hm-rega@4.0.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.hm-rpc@1.17.0 | +-- @iobroker/adapter-core@3.1.4 | `-- @iobroker/dm-utils@0.1.9 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.homeconnect@1.4.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.homekit-controller@0.5.10 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.ical@1.15.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.influxdb@4.0.2 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.iot@3.3.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.iqontrol@2.3.0 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.javascript@8.3.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.jeelink@1.2.3 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.js-controller@6.0.1-alpha.0-20240525-56d9e4a2e | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.klf200@1.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.mercedesme@0.2.3 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.mihome-vacuum@4.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.modbus@6.2.2 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.mqtt@5.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.node-red@5.2.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.openknx@0.9.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.pushover@3.0.6 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.pvforecast@2.9.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.selverf@0.6.3 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.shelly@7.0.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.shuttercontrol@1.7.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.simple-api@2.8.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.sma-em@1.0.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.smartcontrol@2.0.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.socketio@6.7.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.sonoff@3.0.3 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.tankerkoenig@3.4.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.telegram@3.2.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.text2command@3.0.3 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.tr-064@4.3.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.unifi@0.7.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.vis-2@2.9.64 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.web@6.2.5 | +-- @iobroker/adapter-core@3.1.4 | +-- iobroker.socketio@6.6.1 | | `-- @iobroker/adapter-core@3.1.4 deduped | `-- iobroker.ws@2.5.11 | `-- @iobroker/adapter-core@3.1.4 deduped +-- iobroker.ws@2.6.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.yahka@1.0.3 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.yamaha@0.5.3 | `-- @iobroker/adapter-core@2.6.12 deduped `-- iobroker.zigbee@1.10.3 `-- @iobroker/adapter-core@3.1.4 -
@fortune95 Jop liegt an heating Control der hat eine Version von Adapter Core fest spezifiziert die inkompatibel ist. Ist im Endeffekt schon auf GitHub gefixt aber gerne mal ein issue machen dass diese released wird
-
@foxriver76 said in Alpha Test js-controller Kiera (v6.0):
@fortune95 Jop liegt an heating Control der hat eine Version von Adapter Core fest spezifiziert die inkompatibel ist. Ist im Endeffekt schon auf GitHub gefixt aber gerne mal ein issue machen dass diese released wird
Ich würd vorschlagen heatcontrol und allfällige ander bekanntermaßen inkompatible Adapter im Comment #2 ebenfalls als 'inkompatibel' zu listen. Könnte weitere Meldungen sparen und wir wissen ja nicht, wann das gefixt wird.
-
@foxriver76
Du warst schneller
Danke!
Mit der github Version startet der Adapter jetzt. -
@mcm1957 @haus-automatisierung
Start mit dem custom modul
playactoraktiv:2024-05-25 14:25:54.749 - info: javascript.0 (179133) starting. Version 8.4.0 (non-npm: ioBroker/ioBroker.javascript) in /opt/iobroker/node_modules/iobroker.javascript, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240525-56d9e4a2e 2024-05-25 14:26:03.646 - warn: javascript.0 (179133) Cannot install custom npm package playactor: Error: Cannot find package '/opt/iobroker/node_modules/@iobroker-javascript.0/playactor/package.json' imported from /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js 2024-05-25 14:26:04.391 - info: javascript.0 (179133) requesting all states 2024-05-25 14:26:04.393 - info: javascript.0 (179133) requesting all objects 2024-05-25 14:26:07.025 - info: javascript.0 (179133) received all objects 2024-05-25 14:26:07.474 - info: javascript.0 (179133) received all states 2024-05-25 14:26:07.722 - info: javascript.0 (179133) Start JavaScript script.js.common.awtrix (Blockly) 2024-05-25 14:26:07.781 - info: javascript.0 (179133) script.js.common.awtrix: registered 3 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.795 - info: javascript.0 (179133) Start JavaScript script.js.common.frostwarner (Blockly) 2024-05-25 14:26:07.805 - info: javascript.0 (179133) script.js.common.frostwarner: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.805 - info: javascript.0 (179133) Start JavaScript script.js.common.lautstaerke_bad (Blockly) 2024-05-25 14:26:07.812 - info: javascript.0 (179133) script.js.common.lautstaerke_bad: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.813 - info: javascript.0 (179133) Start JavaScript script.js.common.lautstaerke_kueche (Blockly) 2024-05-25 14:26:07.819 - info: javascript.0 (179133) script.js.common.lautstaerke_kueche: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.820 - info: javascript.0 (179133) Start JavaScript script.js.common.nuki_ext_wohnungstuer_entriegelt (Blockly) 2024-05-25 14:26:07.827 - info: javascript.0 (179133) script.js.common.nuki_ext_wohnungstuer_entriegelt: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.827 - info: javascript.0 (179133) Start JavaScript script.js.common.paketlieferungen (Blockly) 2024-05-25 14:26:07.918 - info: javascript.0 (179133) script.js.common.paketlieferungen: registered 1 subscription, 2 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.918 - info: javascript.0 (179133) Start JavaScript script.js.common.pakettruhe_offen (Blockly) 2024-05-25 14:26:07.924 - info: javascript.0 (179133) script.js.common.pakettruhe_offen: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.926 - info: javascript.0 (179133) Start JavaScript script.js.common.ps4_waker (Blockly) 2024-05-25 14:26:07.932 - info: javascript.0 (179133) script.js.common.ps4_waker: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.933 - info: javascript.0 (179133) Start JavaScript script.js.common.sonnenaufgang (Blockly) 2024-05-25 14:26:07.939 - info: javascript.0 (179133) script.js.common.sonnenaufgang: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.940 - info: javascript.0 (179133) Start JavaScript script.js.common.sonnenuntergang (Blockly) 2024-05-25 14:26:07.946 - info: javascript.0 (179133) script.js.common.sonnenuntergang: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.947 - info: javascript.0 (179133) Start JavaScript script.js.common.speedtest (Javascript/js) 2024-05-25 14:26:07.954 - info: javascript.0 (179133) script.js.common.speedtest: Speedtest: Erster Start des Skriptes! Datenpunkte werden erstellt! 2024-05-25 14:26:07.958 - info: javascript.0 (179133) script.js.common.speedtest: Speedtest: Datenpunkte erstellt! Erster Speedtest wird in 180 Sekunden ausgeführt! 2024-05-25 14:26:07.970 - info: javascript.0 (179133) script.js.common.speedtest: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.971 - info: javascript.0 (179133) Start JavaScript script.js.common.telefon_klingelt (Blockly) 2024-05-25 14:26:07.977 - info: javascript.0 (179133) script.js.common.telefon_klingelt: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.979 - info: javascript.0 (179133) Start JavaScript script.js.common.treppenhaus_licht_hub (Blockly) 2024-05-25 14:26:07.985 - info: javascript.0 (179133) script.js.common.treppenhaus_licht_hub: registered 2 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:07.986 - info: javascript.0 (179133) Start JavaScript script.js.common.tuerklingel_laeutet (Blockly) 2024-05-25 14:26:07.992 - info: javascript.0 (179133) script.js.common.tuerklingel_laeutet: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:08.010 - info: javascript.0 (179133) Start JavaScript script.js.common.usv_warner (Blockly) 2024-05-25 14:26:08.018 - info: javascript.0 (179133) script.js.common.usv_warner: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:08.019 - info: javascript.0 (179133) Start JavaScript script.js.common.wohnung_verlassen (Blockly) 2024-05-25 14:26:08.026 - info: javascript.0 (179133) script.js.common.wohnung_verlassen: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:08.027 - info: javascript.0 (179133) Start JavaScript script.js.common.zuhause_verlassen (Blockly) 2024-05-25 14:26:08.034 - info: javascript.0 (179133) script.js.common.zuhause_verlassen: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:08.060 - info: javascript.0 (179133) Watch /home/iobroker/skripte/common/ 2024-05-25 14:26:08.063 - info: javascript.0 (179133) Watch /home/iobroker/skripte/global/ 2024-05-25 14:26:08.064 - info: javascript.0 (179133) Watch /home/iobroker/skripte/ 2024-05-25 14:26:08.085 - info: javascript.0 (179133) Start JavaScript script.js.nuki_extended_restart_fix (Javascript/js) 2024-05-25 14:26:08.092 - info: javascript.0 (179133) script.js.nuki_extended_restart_fix: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:08.108 - info: javascript.0 (179133) Start JavaScript script.js.solix2mqtt (Javascript/js) 2024-05-25 14:26:08.115 - info: javascript.0 (179133) script.js.solix2mqtt: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-05-25 14:26:08.115 - info: javascript.0 (179133) Start JavaScript script.js.stromzaehler2 (Javascript/js) 2024-05-25 14:26:08.122 - info: javascript.0 (179133) script.js.stromzaehler2: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptionsSchaut so auf den ersten Blick gut aus, die anderen Skripte starten wohl alle richtig auf.
-
Bei mir hat das Update nicht funktioniert. Ich komme nicht mehr in den Admin Adapter.
Heute morgen hatte ich nodejs auf 20 hochgezogen. Das lief ohne Probleme. -
@lobomau Admin ist nicht aktuell
-
@lobomau sagte in Alpha Test js-controller Kiera (v6.0):
system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
system.adapter.admin.1 : admin : ioBroker - enabled, port: 8089, bind: 0.0.0.0, run as: admin
system.adapter.admin.2 : admin : Pi4 - disabled, port: 8081, bind: 0.0.0.0, run as: adminkeiner deiner admin`s läuft
-
@foxriver76 ok, ich hatte nur 3 Adapter unter dem #2 geupdatet. Admin war stable.
wie war nochmal der Befehl bzw. welches ist die zu installierende Admin-Version?
Ich habe folgendes versucht. Er sagt nun eigentlich admin läuft!?lobomau@ioBroker:~$ iob upgrade admin ..... Would you like to upgrade admin from @6.17.6 to @6.17.14 now? [(y)es, (n)o]: y Update admin from @6.17.6 to @6.17.14 host.ioBroker Adapter "system.adapter.admin.0" is stopped. host.ioBroker Adapter "system.adapter.admin.1" is stopped. NPM version: 10.5.2 Installing iobroker.admin@6.17.14... (System call) .... host.ioBroker Adapter "system.adapter.admin.0" is started host.ioBroker Adapter "system.adapter.admin.1" is started -
@crunchip als Laie habe ich daraus gelesen, dass die beiden Instanzen auf ioBroker laufen. Komisch.
Bin erstmal wieder zurück auf js-controller 5.0.19 und alles läuft wieder normal. -
@lobomau sagte in Alpha Test js-controller Kiera (v6.0):
dass die beiden Instanzen auf ioBroker laufen.
ne
, ein punkt davor bedeutet er läuft
bei dir aber
