UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Thomas Braun]

@foxriver76 sagte in Alpha Test js-controller Kiera (v6.0):

@mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

Ich hab das volle Log. Aber das sind 4300 Zeilen. Krieg ich nirgends hochgeladen.

[Homoran]

@thomas-braun .txt

[Thomas Braun]

@foxriver76 js-controller-inst-log.txt

[Feuersturm]

@haus-automatisierung sagte in Alpha Test js-controller Kiera (v6.0):

Bitte als Issue auf GitHub öffnen. Sonst laufen da zig Themen durcheinander.

erledigt https://github.com/ioBroker/ioBroker.javascript/issues/1576
@TT-Tom fyi

[Feuersturm]

@foxriver76
Update js-controller auf 6.0.1-alpha.0-20240524-14a872375

proxmox@ioBrokerTestsystem:~$ iob stop
proxmox@ioBrokerTestsystem:~$ cd /opt/iobroker/
proxmox@ioBrokerTestsystem:/opt/iobroker$ npm i iobroker.js-controller@next --om                                                                                                 it=dev
[sudo] password for proxmox:
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @mui/x-date-pickers@7.5.1
npm warn Found: @mui/material@5.14.14
npm warn node_modules/@iobroker/adapter-react-v5/node_modules/@mui/material
npm warn   @mui/material@"5.14.14" from @iobroker/adapter-react-v5@4.13.22
npm warn   node_modules/@iobroker/adapter-react-v5
npm warn     @iobroker/adapter-react-v5@"^4.13.13" from @iobroker/json-config@6.                                                                                                 17.13
npm warn     node_modules/@iobroker/json-config
npm warn     1 more (iobroker.radar-trap)
npm warn
npm warn Could not resolve dependency:
npm warn peer @mui/material@"^5.15.14" from @mui/x-date-pickers@7.5.1
npm warn node_modules/@iobroker/adapter-react-v5/node_modules/@mui/x-date-picker                                                                                                 s
npm warn   @mui/x-date-pickers@"^7.5.0" from @iobroker/adapter-react-v5@4.13.22
npm warn   node_modules/@iobroker/adapter-react-v5
npm warn
npm warn Conflicting peer dependency: @mui/material@5.15.18
npm warn node_modules/@mui/material
npm warn   peer @mui/material@"^5.15.14" from @mui/x-date-pickers@7.5.1
npm warn   node_modules/@iobroker/adapter-react-v5/node_modules/@mui/x-date-pick                                                                                                 ers
npm warn     @mui/x-date-pickers@"^7.5.0" from @iobroker/adapter-react-v5@4.13.2                                                                                                 2
npm warn     node_modules/@iobroker/adapter-react-v5
npm warn reify invalid or damaged lockfile detected
npm warn reify please re-try this operation once it completes
npm warn reify so that the damage can be corrected, or perform
npm warn reify a fresh install with no lockfile if the problem persists.

changed 12 packages in 6m

397 packages are looking for funding
  run `npm fund` for details

iobroker log vom start des Systems enthält keine relevanten Fehler

[mcm1957]

@foxriver76

Bitte samsung 0.6.0 in die Liste der zu aktualisierenden Adapter eintragen.

Release ist im Latest.
Danke

[DLehmann]

update gemacht - das Testsystem startet.

hier meine Instanzen

root@iobroker-test:/opt/iobroker# iobroker list instances
+ system.adapter.adguard.0                : adguard               : iobroker-test                            -  enabled
+ system.adapter.admin.0                  : admin                 : iobroker-test                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.alexa2.0                 : alexa2                : iobroker-test                            -  enabled
  system.adapter.alias-manager.0          : alias-manager         : iobroker-test                            -  enabled
  system.adapter.backitup.0               : backitup              : iobroker-test                            - disabled
+ system.adapter.cloud.0                  : cloud                 : iobroker-test                            -  enabled
  system.adapter.daswetter.0              : daswetter             : iobroker-test                            -  enabled
  system.adapter.devices.0                : devices               : iobroker-test                            -  enabled
  system.adapter.discovery.0              : discovery             : iobroker-test                            - disabled
  system.adapter.dwd.0                    : dwd                   : iobroker-test                            -  enabled
  system.adapter.ecovacs-deebot.0         : ecovacs-deebot        : iobroker-test                            -  enabled
+ system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: iobroker-test                            -  enabled
  system.adapter.feiertage.0              : feiertage             : iobroker-test                            -  enabled
+ system.adapter.gotify.0                 : gotify                : iobroker-test                            -  enabled
  system.adapter.heatingcontrol.0         : heatingcontrol        : iobroker-test                            -  enabled
+ system.adapter.history.0                : history               : iobroker-test                            -  enabled
+ system.adapter.hm-rpc.0                 : hm-rpc                : iobroker-test                            -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : iobroker-test                            -  enabled, port: 0
+ system.adapter.hue.0                    : hue                   : iobroker-test                            -  enabled, port: 443
+ system.adapter.iot.0                    : iot                   : iobroker-test                            -  enabled
+ system.adapter.iqontrol.0               : iqontrol              : iobroker-test                            -  enabled
  system.adapter.jarvis.0                 : jarvis                : iobroker-test                            -  enabled
+ system.adapter.javascript.0             : javascript            : iobroker-test                            -  enabled
+ system.adapter.ping.0                   : ping                  : iobroker-test                            -  enabled
+ system.adapter.pvforecast.0             : pvforecast            : iobroker-test                            -  enabled
  system.adapter.ring.0                   : ring                  : iobroker-test                            - disabled
+ system.adapter.scenes.0                 : scenes                : iobroker-test                            -  enabled
+ system.adapter.scheduler.0              : scheduler             : iobroker-test                            -  enabled
+ system.adapter.smartcontrol.0           : smartcontrol          : iobroker-test                            -  enabled
+ system.adapter.sonnen.0                 : sonnen                : iobroker-test                            -  enabled
+ system.adapter.tesla-motors.0           : tesla-motors          : iobroker-test                            -  enabled
+ system.adapter.teslamateapi.0           : teslamateapi          : iobroker-test                            -  enabled
  system.adapter.vis-materialdesign.0     : vis-materialdesign    : iobroker-test                            -  enabled
  system.adapter.vis.0                    : vis                   : iobroker-test                            -  enabled
+ system.adapter.web.0                    : web                   : iobroker-test                            -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

+ instance is alive

Beim npm update kam folgende Meldung

root@iobroker-test:/opt/iobroker# npm update
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/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

up to date in 2m

137 packages are looking for funding
  run `npm fund` for details

Die drei Instanzen wollen nicht starten
ecovacs-deebot
heatingcontrol
jarvis

Folgende Fehlermeldungen kommen hierzu

host.iobroker-test
2024-05-24 20:39:36.517	error	instance system.adapter.jarvis.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: Node.js v20.13.1
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/index.js:19:27)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at require (node:internal/modules/helpers:179:18)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/controllerTools.js:126:18)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/controllerTools.js:83:11)
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: ^
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
host.iobroker-test
2024-05-24 20:39:36.517	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/controllerTools.js:83
host.iobroker-test
2024-05-24 20:39:33.235	error	instance system.adapter.heatingcontrol.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: Node.js v20.13.1
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/index.js:19:27)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at require (node:internal/modules/helpers:179:18)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/controllerTools.js:157:18)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/controllerTools.js:83:11)
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: ^
host.iobroker-test
2024-05-24 20:39:33.235	error	Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
host.iobroker-test
2024-05-24 20:39:33.234	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/controllerTools.js:83
host.iobroker-test
2024-05-24 20:39:30.682	error	instance system.adapter.ecovacs-deebot.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker-test
2024-05-24 20:39:30.682	error	Caught by controller[0]: Node.js v20.13.1
host.iobroker-test
2024-05-24 20:39:30.682	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
host.iobroker-test
2024-05-24 20:39:30.682	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/index.js:19:27)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at require (node:internal/modules/helpers:179:18)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/controllerTools.js:157:18)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/controllerTools.js:83:11)
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: ^
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
host.iobroker-test
2024-05-24 20:39:30.681	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/controllerTools.js:83

[TT-Tom]

@foxriver76
habe das Update eingespielt, lief ohne Probleme durch. Es sind auch alle Instanzen gestartet ohne Probleme. Da npm update mit der ersten Version von Hand ausgeführt wurde, kann ich nicht genau bestätigen, ob es jetzt funktioniert.
schönes WE noch

[foxriver76]

Gerne nochmal updaten.

Das Problem, dass er sich über invalide Instanz Objekte vom Typ device beschwert wurde behoben und nochmal ein anderer Versuch für die alten Adapter-Core Versionen wird ausprobiert.

[Thomas Braun]

@foxriver76

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.

[Thomas Braun]

@foxriver76

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 playactor herausnehme starten die anderen Skripte korrekt.

[foxriver76]

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

[Fortune95]

@foxriver76

Update lief durch, nur der Heatcontrol Adapter startet wie zuvor nicht.
Soll ich ein issue beim Adapter öffnen?

[foxriver76]

@fortune95 welche Version hat dein Admin?

Und mal bitte npm ls @iobroker/adapter-core Ausgabe zeigen

[Fortune95]

@foxriver76

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

[mcm1957]

@thomas-braun said in Alpha Test js-controller Kiera (v6.0):

Wenn ich das Modul playactor herausnehme 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

[Thomas Braun]

@fortune95

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 $

[foxriver76]

@fortune95 im folder /opt/iobroker bitte das Kommando ausführen.

[Fortune95]

@foxriver76

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

[foxriver76]

@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