Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[technogodder]

Hallo zusammen,

ich habe irgendwann mal einen McLighting Adapter Vvon Github installiert, welcher aber nie so richtig funktionierte.
Wahrscheinlich seitdem kann ich nichts mehr von Github installieren, und den js-controller V3.1.6 nicht mehr aktualisieren. Den Adapter zu löschen oder aktualisieren gibt auch etliche Fehlermeldungen.

Kann mir jemand weiterhelfen, wie ich diesen Adapter deinstalliert/gelöscht bekomme?

Meldung:
pi@ioBroker-RasPi4:/opt/iobroker $ iobroker upgrade self
Update js-controller from @3.1.6 to @4.0.23
NPM version: 8.19.2
npm install iobroker.js-controller@4.0.23 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
npm ERR! code E404
npm ERR! 404 Not Found - GET https://codeload.github.com/instalator/iobroker.mclighting/legacy.tar.gz/79d8d632146e9b2b5ee117f5e018a526698f1994
npm ERR! 404
npm ERR! 404 'iobroker.mclighting@https://github.com/instalator/ioBroker.mclighting/tarball/79d8d632146e9b2b5ee117f5e018a526698f1994' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/iobroker/.npm/_logs/2022-10-28T08_33_45_384Z-debug-0.log
Starting node restart.js
pi@ioBroker-RasPi4:/opt/iobroker $

Gruß Timo

Systemdata	Bitte Ausfüllen
Hardwaresystem:	PI 4
Arbeitsspeicher:	4GB
Festplattenart:	SSD
Betriebssystem:	Bullseye
Node-Version:	3.1.6
Nodejs-Version:	16.18.0
NPM-Version:	8.19.2
Installationsart:	Skript/Manuell
Image genutzt:	Ja/Nein
Ort/Name der Imagedatei:	Link

[technogodder]

@technogodder

Hier die Meldung, wenn ich versuche den Adapter zu löschen:

pi@ioBroker-RasPi4:/opt/iobroker $ iobroker del mclighting
Delete adapter "mclighting"
host.ioBroker-RasPi4 Counted 1 instances of mclighting
host.ioBroker-RasPi4 Counted 1 meta of mclighting
host.ioBroker-RasPi4 Counted 1 adapter for mclighting
host.ioBroker-RasPi4 Counted 12 states of mclighting
host.ioBroker-RasPi4 Counted 14 states of system.adapter.mclighting
host.ioBroker-RasPi4 Counted 12 states (io.mclighting.) from states
host.ioBroker-RasPi4 Counted 1 states (system.adapter.mclighting.) from states
host.ioBroker-RasPi4 file mclighting deleted
host.ioBroker-RasPi4 file mclighting.admin deleted
host.ioBroker-RasPi4 object mclighting deleted
host.ioBroker-RasPi4 object mclighting.admin deleted
host.ioBroker-RasPi4 Deleting 29 object(s).
host.ioBroker-RasPi4 Deleting 13 state(s).
npm uninstall iobroker.mclighting --error --prefix "/opt/iobroker" (System call)
Cannot write files: /opt/iobroker/iobroker-data/files/mclighting/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/mclighting/_data.json'
Cannot write files: /opt/iobroker/iobroker-data/files/mclighting.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/mclighting.admin/_data.json'
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated passport.socketio@3.7.0: Please check the workaround in https://github.com/jfromaniello/passport.socketio/issues/148
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated tough-cookie@0.12.1: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated bcrypt@3.0.6: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated bcrypt@3.0.8: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated node-pre-gyp@0.12.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated node-pre-gyp@0.14.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated axios@0.20.0: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
Objects 127.0.0.1:52042 Error from InMemDB: Error: client NOT SUPPORTED
Objects 127.0.0.1:52044 Error from InMemDB: Error: client NOT SUPPORTED
Objects 127.0.0.1:52046 Error from InMemDB: Error: client NOT SUPPORTED
States 127.0.0.1:33974 Error from InMemDB: Error: client NOT SUPPORTED
States 127.0.0.1:33976 Error from InMemDB: Error: client NOT SUPPORTED
States 127.0.0.1:33978 Error from InMemDB: Error: client NOT SUPPORTED
Objects 127.0.0.1:52042 Error from InMemDB: Error: scan NOT SUPPORTED
Objects 127.0.0.1:52054 Error from InMemDB: Error: client NOT SUPPORTED
Objects 127.0.0.1:52056 Error from InMemDB: Error: client NOT SUPPORTED
Objects 127.0.0.1:52058 Error from InMemDB: Error: client NOT SUPPORTED
States 127.0.0.1:33986 Error from InMemDB: Error: client NOT SUPPORTED
States 127.0.0.1:33988 Error from InMemDB: Error: client NOT SUPPORTED
States 127.0.0.1:33990 Error from InMemDB: Error: client NOT SUPPORTED
Objects 127.0.0.1:52054 Error from InMemDB: Error: scan NOT SUPPORTED
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/iobroker.sayit
npm ERR! command failed
npm ERR! command sh -c -- node main.js --install
npm ERR! ReplyError: Error scan NOT SUPPORTED
npm ERR! at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
npm ERR! at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

npm ERR! A complete log of this run can be found in:
npm ERR! /home/iobroker/.npm/_logs/2022-10-28T08_53_13_509Z-debug-0.log
Error deleting adapter mclighting from disk: Error: host.ioBroker-RasPi4: Cannot uninstall iobroker.mclighting: 1
You might have to delete it yourself!
pi@ioBroker-RasPi4:/opt/iobroker $

[arteck]

@technogodder nimm die Brechhammer Methode
lösche den direkt von der platte

rm -R /opt/iobroker/node_modules/iobroker.mclighting

danach noch die objecte fettisch