Alpha Test js-controller Kiera (v6.0)

foxriver76

@mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

mcm1957

Soda:
Mal Snapshot während er mit npm rumnuckelt ...

Ansonsten ist er seht schweigsam:

**********************************************************
***               Welcome to ioBroker.                 ***
***                                                    ***
***     Type 'iob help' for list of instructions.      ***
***                For more help see                   ***
***     https://github.com/ioBroker/ioBroker.docs      ***
**********************************************************

Your environment has been set up for using Node.js 20.13.1 (x64) and npm.

C:\ioBroker>npm i iobroker.js-controller@next --omit=dev

changed 12 packages, and audited 619 packages in 2m

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

26 vulnerabilities (21 moderate, 5 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

C:\ioBroker>

Im Log nix auffälligs, system läuft soweit (mal grob gechecked)


ical.1
2024-05-24 19:18:16.241	warn	Error reading from URL "http://11111.ics"

ical.1
2024-05-24 19:18:15.892	info	starting. Version 1.15.0 in C:/ioBroker/node_modules/iobroker.ical, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240524-14a872375
host.Envy
2024-05-24 19:18:14.133	info	instance system.adapter.ical.1 started with pid 1604
host.Envy
2024-05-24 19:18:14.125	info	instance scheduled system.adapter.ical.1 0,4 0,30 * * * *
host.Envy
2024-05-24 19:18:11.929	info	Restart adapter system.adapter.notification-manager.0 because enabled
host.Envy
2024-05-24 19:18:11.928	error	instance system.adapter.notification-manager.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)

notification-manager.0
2024-05-24 19:18:11.379	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason

notification-manager.0
2024-05-24 19:18:11.377	error	notification-manager.0 already running
host.Envy
2024-05-24 19:18:10.032	info	instance system.adapter.notification-manager.0 started with pid 17028
host.Envy
2024-05-24 19:18:07.928	info	Restart adapter system.adapter.backitup.0 because enabled
host.Envy
2024-05-24 19:18:07.928	error	instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
backitup.0
2024-05-24 19:18:07.378	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
backitup.0
2024-05-24 19:18:07.377	error	backitup.0 already running
host.Envy
2024-05-24 19:18:06.016	info	instance system.adapter.backitup.0 started with pid 1772
host.Envy
2024-05-24 19:18:04.960	info	Restart adapter system.adapter.admin.0 because enabled
host.Envy
2024-05-24 19:18:04.960	error	instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)

admin.0
2024-05-24 19:18:04.388	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason

admin.0
2024-05-24 19:18:04.386	error	admin.0 already running
host.Envy
2024-05-24 19:18:02.125	info	Some obsolete host states deleted.
host.Envy
2024-05-24 19:18:02.123	info	Delete state "system.host.Envy.versions.npmNewestNext"
host.Envy
2024-05-24 19:18:02.121	info	Delete state "system.host.Envy.versions.npmNewest"
host.Envy
2024-05-24 19:18:02.118	info	Delete state "system.host.Envy.versions.npmCurrent"
host.Envy
2024-05-24 19:18:02.112	info	Delete state "system.host.Envy.versions.nodeNewestNext"
host.Envy
2024-05-24 19:18:02.111	info	instance system.adapter.admin.0 started with pid 17072
host.Envy
2024-05-24 19:18:02.098	info	Delete state "system.host.Envy.versions.nodeNewest"
host.Envy
2024-05-24 19:18:02.086	info	Delete state "system.host.Envy.versions.nodeCurrent"
host.Envy
2024-05-24 19:18:01.693	info	starting 5 instances
host.Envy
2024-05-24 19:18:01.675	info	17 instances found
host.Envy
2024-05-24 19:18:01.188	info	added notifications configuration of host
host.Envy
2024-05-24 19:18:01.174	info	connected to Objects and States
host.Envy
2024-05-24 19:18:00.523	info	ip addresses: 10.17.2.100 fe80::3089:3ca1:e684:7494 10.17.2.16
host.Envy
2024-05-24 19:18:00.522	info	hostname: Envy, node: v20.13.1
host.Envy
2024-05-24 19:18:00.522	info	Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
host.Envy
2024-05-24 19:18:00.518	info	iobroker.js-controller version 6.0.1 js-controller starting

mcm1957

Wurde im js-controller nicht was mit npm update eingebaut?
Wann sollte das denn laufen? npm wird das ja kaum triggern. Sollte da unter windows noch der fixer gestartet werden?

mcm1957

Das Ganze noch mal mit verbose

npm verb cli C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
npm info using npm@10.5.2
npm info using node@v20.13.1
npm verb title npm i iobroker.js-controller@next
npm verb argv "i" "iobroker.js-controller@next" "--omit" "dev" "--loglevel" "verbose"
npm verb logfile logs-max:10 dir:C:\Users\MartinAdmin\AppData\Local\npm-cache\_logs\2024-05-24T17_27_06_077Z-
npm verb logfile C:\Users\MartinAdmin\AppData\Local\npm-cache\_logs\2024-05-24T17_27_06_077Z-debug-0.log
npm http fetch GET 200 https://registry.npmjs.org/iobroker.js-controller 993ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-redis 30ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-redis 51ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-file 73ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-jsonl 92ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-file 120ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-jsonl 145ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-adapter 163ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fplugin-base 88ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-cli 153ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-common 154ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fplugin-sentry 93ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/deep-clone 82ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-common-db 156ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/jsonwebtoken 80ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/pidusage 72ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/readline-sync 41ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/promisify-child-process 73ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fjsonl-db 28ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/node.extend 20ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-base 41ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/ioredis 59ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fpak 70ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/event-stream 60ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/readline 75ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/chokidar 83ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/ci-info 52ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/debug 96ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/winston-daily-rotate-file 46ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/triple-beam 63ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/node-forge 74ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/winston-transport 60ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/winston 79ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@datalust%2fwinston-seq 68ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/diskusage 63ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/winston-seq-updated 49ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/winston-syslog 58ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fnode 54ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fintegrations 75ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/jws 85ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/source-map-support 94ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.includes 111ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.isboolean 112ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.isinteger 116ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.isnumber 81ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.isplainobject 69ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.isstring 65ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.once 58ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/ms 30ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/respjs 8ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fproper-lockfile 14ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/alcalzone-shared 15ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/fs-extra 17ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/retry 19ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/signal-exit 21ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.defaults 21ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/cluster-key-slot 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/denque 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.flatten 41ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lodash.isarguments 46ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/p-map 48ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/redis-commands 51ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/redis-parser 41ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/redis-errors 46ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/standard-as-callback 39ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/is 30ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/axios 15ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/execa 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/npm-run-path 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/merge-stream 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/human-signals 32ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/strip-final-newline 32ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/onetime 34ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/glob-parent 33ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/is-binary-path 37ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/anymatch 42ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/braces 45ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/is-glob 50ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/readdirp 54ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/fsevents 57ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/duplexer 45ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/split 31ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/from 51ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/pause-stream 44ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/map-stream 55ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/stream-combiner 39ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/through 38ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@dabh%2fdiagnostics 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/seq-logging 36ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/one-time 38ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/logform 42ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@colors%2fcolors 47ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/safe-stable-stringify 50ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/readable-stream 56ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/es6-promise 60ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/nan 59ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/object-hash 56ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/glossy 52ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/file-stream-rotator 66ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/unix-dgram 53ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/localforage 32ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 44ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 65ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 83ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry-internal%2ftracing 106ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 112ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 141ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/source-map 119ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 155ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lie 8ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/fill-range 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/binary-extensions 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/picomatch 36ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/is-extglob 34ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/picomatch 35ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/to-regex-range 8ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/mimic-fn 12ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/is-number 10ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/jwa 9ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/kuler 34ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/enabled 40ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/fecha 33ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@types%2ftriple-beam 40ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/fn.name 34ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/colorspace 52ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/text-hex 11ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color 15ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color-convert 11ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color-string 13ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 18ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color-name 22ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color-name 24ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 9ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/bindings 9ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/file-uri-to-path 10ms (cache hit)
npm verb reify failed optional dependency C:\ioBroker\node_modules\fsevents
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 254ms
npm http fetch GET 200 https://registry.npmjs.org/follow-redirects 97ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/request 182ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/ip 191ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tough-cookie 210ms (cache revalidated)
npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 preinstall node_modules/iobroker.js-controller node build/esm/lib/preinstallCheck.js
npm http fetch GET 200 https://registry.npmjs.org/iobroker.broadlink2 626ms (cache revalidated)
npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 preinstall { code: 0, signal: null }
npm info run diskusage@1.2.0 install node_modules/diskusage node-gyp rebuild
npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 install node_modules/iobroker.js-controller node iobroker.js setup first
npm info run unix-dgram@2.0.6 install node_modules/unix-dgram node-gyp rebuild
npm http fetch GET 200 https://registry.npmjs.org/mdns-discovery 642ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/dns-packet 58ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/node-ssdp 889ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/iobroker.kecontact 619ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/dropbox-v2-api 627ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/iobroker.discovery 255ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/iobroker.backitup 586ms (cache revalidated)
npm info run unix-dgram@2.0.6 install { code: 1, signal: null }
npm verb reify failed optional dependency C:\ioBroker\node_modules\unix-dgram
npm verb reify failed optional dependency C:\ioBroker\node_modules\bindings
npm verb reify failed optional dependency C:\ioBroker\node_modules\file-uri-to-path
npm info run diskusage@1.2.0 install { code: 1, signal: null }
npm verb reify failed optional dependency C:\ioBroker\node_modules\diskusage
npm verb reify failed optional dependency C:\ioBroker\node_modules\es6-promise
npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 install { code: 0, signal: null }

removed 32 packages, changed 14 packages, and audited 619 packages in 1m

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

26 vulnerabilities (21 moderate, 5 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm verb exit 0
npm info ok

mcm1957

Und der iob fix

C:\ioBroker>
C:\ioBroker>del iobroker.bat

C:\ioBroker>iob fix
Windows installation starting... (fixing = true)
NPM version: 10.5.2
No path given, using C:\ioBroker\iobroker-data
Compressing C:\ioBroker\iobroker-data\states.jsonl
Compressing C:\ioBroker\iobroker-data\objects.jsonl
Compressed 2 JSONL files. Done
NPM version: 10.5.2
Write "iobroker start" to start the ioBroker
npm install node-windows@1.0.0-beta.8 --force --loglevel error --production --save --prefix "C:/ioBroker"

up to date, audited 619 packages in 9s

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

26 vulnerabilities (21 moderate, 5 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm install dotenv@^16.3.1 --force --loglevel error --production --save --prefix "C:/ioBroker"

up to date, audited 619 packages in 7s

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

26 vulnerabilities (21 moderate, 5 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm install windows-shortcuts@^0.1.6 --force --loglevel error --production --save --prefix "C:/ioBroker"

up to date, audited 619 packages in 7s

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

26 vulnerabilities (21 moderate, 5 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

=============================
Running Admin shell
=============================
ioBroker service name: ioBroker
ioBroker ist nicht gestartet.

Sie erhalten weitere Hilfe, wenn Sie NET HELPMSG 3521 eingeben.

Written iobnodevars.bat successfully.
ioBroker service is already installed.
Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Stop ioBroker Service.lnk" created with Admin flag!
Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Start ioBroker Service.lnk" created with Admin flag!
Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Restart ioBroker Service.lnk" created with Admin flag!
Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Command line.lnk" created with Admin flag!
Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Admin.lnk" created!

=============================
Running Admin shell
=============================
ioBroker service name: ioBroker
ioBroker wird gestartet.
ioBroker wurde erfolgreich gestartet.

ioBroker service installed and started. Go to http://localhost:8081 to open the admin UI.
To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller"

C:\ioBroker>

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

Community Forum

NEWS

Alpha Test js-controller Kiera (v6.0)

Support us

361

32.4k

81.5k

1.3m