Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[Codierknecht]

@thomas-braun sagte in backup&discovery Adapter kein upgrade:

Mit Bildchen von Text kann nämlich keiner gescheit arbeiten. Nicht kopieren, nicht zitieren, nix

Nicht mal vernünftig lesen kann man's.

BTW:

@fred-freund sagte in backup&discovery Adapter kein upgrade:

die beiden Adapter

Welche beiden?
Wenn ich schon versuche aus Deinem Bildchen etwas zu lesen, sehe ich 2x die identische Ausgabe.

[Fred Freund]

@codierknecht

$ iobroker upgrade discovery@3.1.0

Update discovery from @3.0.5 to @3.1.0

NPM version: 6.14.17

Installing iobroker.discovery@3.1.0... (System call)

upload [6] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png

upload [2] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html

upload [0] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript

Process exited with code 0

[Homoran]

@fred-freund sagte in backup&discovery Adapter kein upgrade:

Process exited with code 0

und wo ist das Problem?

[Fred Freund]

@homoran Problem :immer wieder sagt er das die alte Version drauf ist und ich upgraden soll.

und das bei beiden Adaptern

[Thomas Braun]

@fred-freund

Updates/upgrades durchgeführt?

[Fred Freund]

@thomas-braun mach ich jetzt inklusive JS...

[Homoran]

@fred-freund sagte in backup&discovery Adapter kein upgrade:

@homoran Problem :immer wieder sagt er das die alte Version drauf ist und ich upgraden soll.

und das bei beiden Adaptern

STRG-F5 probiert?

[Fred Freund]

@homoran ja schon probiert ...immer wieder die beiden

[Fred Freund]

@fred-freund trotz

$ iobroker upgrade backitup@2.5.4 --debug

host.iobroker1 Adapter "system.adapter.backitup.0" is stopped.

NPM version: 8.19.2

Installing iobroker.backitup@2.5.4... (System call)

npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient...npm WARN old lockfile

npm WARN old lockfile FetchError: invalid json response body at https://registry.npmjs.org/@types%2fiobroker reason: Invalid response body while trying to fetch https://registry.npmjs.org/@types%2fiobroker: sha512-ZGXiTsAdkwOiVVRyqX4NJ7zNEIUT5h9pBjM96xp+qkyzlBWXZsRGBax17lus28B+rkFLrN0mfqMvlKnVnRVOYQ== integrity checksum failed when using sha512: wanted sha512-ZGXiTsAdkwOiVVRyqX4NJ7zNEIUT5h9pBjM96xp+qkyzlBWXZsRGBax17lus28B+rkFLrN0mfqMvlKnVnRVOYQ== but got sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==. (0 bytes)npm WARN old lockfile at Response.json (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/body.js:79:13)npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:99:25)npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24)npm WARN old lockfile Could not fetch metadata for @types/iobroker@4.0.5 FetchError: invalid json response body at https://registry.npmjs.org/@types%2fiobroker reason: Invalid response body while trying to fetch https://registry.npmjs.org/@types%2fiobroker: sha512-ZGXiTsAdkwOiVVRyqX4NJ7zNEIUT5h9pBjM96xp+qkyzlBWXZsRGBax17lus28B+rkFLrN0mfqMvlKnVnRVOYQ== integrity checksum failed when using sha512: wanted sha512-ZGXiTsAdkwOiVVRyqX4NJ7zNEIUT5h9pBjM96xp+qkyzlBWXZsRGBax17lus28B+rkFLrN0mfqMvlKnVnRVOYQ== but got sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==. (0 bytes)npm WARN old lockfile at Response.json (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/body.js:79:13)npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:99:25)npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24) {npm WARN old lockfile code: 'FETCH_ERROR',npm WARN old lockfile errno: 'FETCH_ERROR',npm WARN old lockfile type: 'invalid-json'npm WARN old lockfile }

removed 107 packages, and changed 21 packages in 2m126 packages are looking for funding run `npm fund` for details

Update "system.adapter.backitup.0"

upload [19] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript

upload [18] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png

upload [17] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml

upload [11] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/nl/translations.json i18n/nl/translations.json application/json

host.iobroker1 Adapter "system.adapter.backitup.0" is started

Process exited with code 0

Beide Adapter gingen jetzt :...os update/ js update. sorry ...mein Fehler

danke nochmal

[Thomas Braun]

@fred-freund

Was sagt jetzt

sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs