Tuya (original) in IO-Broker
-
Nachdem ich den ewelink Adapter jetzt erfolgreich reparieren konnte scheitere ich momentan an Tuya.
Wenn ich den tyua Adapter von apollon installieren möchte kommt:$ iobroker add tuya auto --host raspberrypi202 NPM version: 8.11.0 npm install iobroker.tuya@3.6.15 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code ENOTEMPTY npm ERR! syscall renamenpm ERR! path /opt/iobroker/node_modules/futoin-hkdfnpm ERR! dest /opt/iobroker/node_modules/.futoin-hkdf-YATH4k85npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/futoin-hkdf' -> '/opt/iobroker/node_modules/.futoin-hkdf-YATH4k85' npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2022-07-15T13_07_05_449Z-debug-0.log host.raspberrypi202 Cannot install iobroker.tuya@3.6.15: 217 ERROR: Process exited with code 25ein
rm -rf /opt/iobroker/node_modules/.futoin-hkdf-YATH4k85hilft leider nicht. (der Ordnername wird dann jedes mal geändert)
Wenn ich versuche tuya in den ham Adapter einzubinden weiß ich zuerst einmal nicht, welches Modul ich genau nehmen soll.
Ich habe es mal mit homebridge-tuya versucht. Es werden zwar im ham Objekte Ordner die Geräte angezeigt (hier Steckdosen), es werden aber keine Daten übermittelt. Es ist auch nur "Name", "On" und "Outlet-In-Use" da, die Energie und Leistungswerte fehlen. -
Nachdem ich den ewelink Adapter jetzt erfolgreich reparieren konnte scheitere ich momentan an Tuya.
Wenn ich den tyua Adapter von apollon installieren möchte kommt:$ iobroker add tuya auto --host raspberrypi202 NPM version: 8.11.0 npm install iobroker.tuya@3.6.15 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code ENOTEMPTY npm ERR! syscall renamenpm ERR! path /opt/iobroker/node_modules/futoin-hkdfnpm ERR! dest /opt/iobroker/node_modules/.futoin-hkdf-YATH4k85npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/futoin-hkdf' -> '/opt/iobroker/node_modules/.futoin-hkdf-YATH4k85' npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2022-07-15T13_07_05_449Z-debug-0.log host.raspberrypi202 Cannot install iobroker.tuya@3.6.15: 217 ERROR: Process exited with code 25ein
rm -rf /opt/iobroker/node_modules/.futoin-hkdf-YATH4k85hilft leider nicht. (der Ordnername wird dann jedes mal geändert)
Wenn ich versuche tuya in den ham Adapter einzubinden weiß ich zuerst einmal nicht, welches Modul ich genau nehmen soll.
Ich habe es mal mit homebridge-tuya versucht. Es werden zwar im ham Objekte Ordner die Geräte angezeigt (hier Steckdosen), es werden aber keine Daten übermittelt. Es ist auch nur "Name", "On" und "Outlet-In-Use" da, die Energie und Leistungswerte fehlen.@wolfgangfb sagte in Tuya (original) in IO-Broker:
futoin-hkdf
Hat nix mit tuya zu tun, würde ich behaupten.
cd /opt/iobroker npm ls futoin-hkdfsagt?
-
Nachdem ich den ewelink Adapter jetzt erfolgreich reparieren konnte scheitere ich momentan an Tuya.
Wenn ich den tyua Adapter von apollon installieren möchte kommt:$ iobroker add tuya auto --host raspberrypi202 NPM version: 8.11.0 npm install iobroker.tuya@3.6.15 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code ENOTEMPTY npm ERR! syscall renamenpm ERR! path /opt/iobroker/node_modules/futoin-hkdfnpm ERR! dest /opt/iobroker/node_modules/.futoin-hkdf-YATH4k85npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/futoin-hkdf' -> '/opt/iobroker/node_modules/.futoin-hkdf-YATH4k85' npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2022-07-15T13_07_05_449Z-debug-0.log host.raspberrypi202 Cannot install iobroker.tuya@3.6.15: 217 ERROR: Process exited with code 25ein
rm -rf /opt/iobroker/node_modules/.futoin-hkdf-YATH4k85hilft leider nicht. (der Ordnername wird dann jedes mal geändert)
Wenn ich versuche tuya in den ham Adapter einzubinden weiß ich zuerst einmal nicht, welches Modul ich genau nehmen soll.
Ich habe es mal mit homebridge-tuya versucht. Es werden zwar im ham Objekte Ordner die Geräte angezeigt (hier Steckdosen), es werden aber keine Daten übermittelt. Es ist auch nur "Name", "On" und "Outlet-In-Use" da, die Energie und Leistungswerte fehlen.pi@raspberrypi202:/opt/iobroker $ npm ls futoin-hkdf iobroker.inst@3.0.0 /opt/iobroker ├── futoin-hkdf@1.4.3 extraneous ├─┬ homebridge-plugin-wrapper@2.2.1 extraneous │ └── futoin-hkdf@1.4.3 deduped └─┬ iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project └─┬ homebridge-plugin-wrapper@2.2.1 └── futoin-hkdf@1.4.3 -
pi@raspberrypi202:/opt/iobroker $ npm ls futoin-hkdf iobroker.inst@3.0.0 /opt/iobroker ├── futoin-hkdf@1.4.3 extraneous ├─┬ homebridge-plugin-wrapper@2.2.1 extraneous │ └── futoin-hkdf@1.4.3 deduped └─┬ iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project └─┬ homebridge-plugin-wrapper@2.2.1 └── futoin-hkdf@1.4.3@wolfgangfb sagte in Tuya (original) in IO-Broker:
iobroker.ham
Der ist nicht richtig installiert worden. Oder zweimal.
-
Den haben wir doch gestern mit viel Mühe hinbekommen. Wie biege ich das jetzt gerade?
-
Den haben wir doch gestern mit viel Mühe hinbekommen. Wie biege ich das jetzt gerade?
Wie hattest du den denn nochgleich installiert?
-
Den haben wir doch gestern mit viel Mühe hinbekommen. Wie biege ich das jetzt gerade?
@wolfgangfb
Über "Adapter", dann ham, hat Version 4.0.2 aus stable installiert, dann als Quellen "Beta" genommen und dann auf 5.0.1 upgedatet (wobei das ein paar Versuche gebraucht hat). -
@wolfgangfb
Über "Adapter", dann ham, hat Version 4.0.2 aus stable installiert, dann als Quellen "Beta" genommen und dann auf 5.0.1 upgedatet (wobei das ein paar Versuche gebraucht hat).iob repo list -
iob repo listpi@raspberrypi202:/opt/iobroker $ iob repo list default : http://download.iobroker.net/sources-dist.json latest : http://download.iobroker.net/sources-dist-latest.json Active repo: latest -
pi@raspberrypi202:/opt/iobroker $ iob repo list default : http://download.iobroker.net/sources-dist.json latest : http://download.iobroker.net/sources-dist-latest.json Active repo: latestcd /opt/iobroker npm prune npm ls -
cd /opt/iobroker npm prune npm lspi@raspberrypi202:/opt/iobroker $ cd /opt/iobroker/ pi@raspberrypi202:/opt/iobroker $ npm prune 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 tarball tarball data for eiscp@https://github.com/GermanBluefox/node-eiscp/tarball/master/ (sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==) seems to be corrupted. Trying again. npm WARN tarball tarball data for eiscp@https://github.com/GermanBluefox/node-eiscp/tarball/master/ (sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==) seems to be corrupted. Trying again. npm WARN old lockfile Error: sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== integrity checksum failed when using sha512: wanted sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== but got sha512-ztYQ+rSQ8dXTqIhWgZ0TyQzo2UF0Nn1CBy0dqaJXDr7DqveVQHEzLOnLlNBpi8Nslmwqpmjfk+bO8RTXCvpKDw==. (49025 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18) npm WARN old lockfile at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:265:12) npm WARN old lockfile at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:269:24) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18) npm WARN old lockfile at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) npm WARN old lockfile Could not fetch metadata for eiscp@https://github.com/GermanBluefox/node-eiscp/tarball/master/ Error: sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== integrity checksum failed when using sha512: wanted sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== but got sha512-ztYQ+rSQ8dXTqIhWgZ0TyQzo2UF0Nn1CBy0dqaJXDr7DqveVQHEzLOnLlNBpi8Nslmwqpmjfk+bO8RTXCvpKDw==. (49025 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18) npm WARN old lockfile at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:265:12) npm WARN old lockfile at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:269:24) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18) npm WARN old lockfile at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) { npm WARN old lockfile code: 'EINTEGRITY', npm WARN old lockfile found: Integrity { sha512: [ [Hash] ] }, npm WARN old lockfile expected: [ npm WARN old lockfile Hash { npm WARN old lockfile source: 'sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==', npm WARN old lockfile digest: '8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==', npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile options: [] npm WARN old lockfile } npm WARN old lockfile ], npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile sri: Integrity { sha512: [ [Hash] ] } npm WARN old lockfile } npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/homebridge-plugin-wrapper npm ERR! dest /opt/iobroker/node_modules/.homebridge-plugin-wrapper-fUhrzAmo npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/homebridge-plugin-wrapper' -> '/opt/iobroker/node_modules/.homebridge-plugin-wrapper-fUhrzAmo' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-15T14_37_58_730Z-debug-0.log pi@raspberrypi202:/opt/iobroker $ nüm ls -bash: nüm: Kommando nicht gefunden. pi@raspberrypi202:/opt/iobroker $ npm ls iobroker.inst@3.0.0 /opt/iobroker ├── @types/caseless@0.12.2 extraneous ├── @types/request@2.48.7 extraneous ├── @types/tough-cookie@4.0.1 extraneous ├── buffer-shims@1.0.0 extraneous ├── coffee-compiler@0.3.2 extraneous ├── coffee-script@1.12.7 extraneous ├── decimal.js@10.3.1 extraneous ├── futoin-hkdf@1.4.3 extraneous ├── homebridge-plugin-wrapper@2.2.1 extraneous ├── iobroker.admin@5.1.25 ├── iobroker.backitup@2.1.17 ├── iobroker.discovery@2.7.0 ├── iobroker.esphome@0.2.4 ├── iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project ├── iobroker.heatingcontrol@2.7.1 ├── iobroker.history@1.9.13 ├── iobroker.influxdb@2.6.2 ├── iobroker.info@1.9.8 ├── iobroker.javascript@5.2.13 ├── iobroker.js-controller@3.3.18 ├── iobroker.modbus@3.4.17 ├── iobroker.mqtt@2.4.0 ├── iobroker.onkyo@2.1.0 ├── iobroker.openweathermap@0.1.0 ├── iobroker.ping@1.5.0 ├── iobroker.shelly@5.3.1 ├── iobroker.tr-064@4.2.14 ├── iobroker.vis@1.4.4 ├── iobroker.web@3.4.7 ├── iobroker.zigbee@1.6.3 ├── jsonata@1.8.5 extraneous ├── mock-require@3.0.3 extraneous ├── node-inspect@2.0.0 extraneous ├── node-persist@0.0.11 extraneous ├── q@1.1.2 extraneous ├── string-argv@0.3.1 extraneous ├── suncalc2@1.8.1 extraneous ├── virtual-tsc@0.6.1 extraneous ├── vm2@3.9.5 extraneous └── wake_on_lan@1.0.0 extraneous npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.2 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.7 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.1 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: buffer-shims@1.0.0 /opt/iobroker/node_modules/buffer-shims npm ERR! extraneous: coffee-compiler@0.3.2 /opt/iobroker/node_modules/coffee-compiler npm ERR! extraneous: coffee-script@1.12.7 /opt/iobroker/node_modules/coffee-script npm ERR! extraneous: decimal.js@10.3.1 /opt/iobroker/node_modules/decimal.js npm ERR! extraneous: futoin-hkdf@1.4.3 /opt/iobroker/node_modules/futoin-hkdf npm ERR! extraneous: homebridge-plugin-wrapper@2.2.1 /opt/iobroker/node_modules/homebridge-plugin-wrapper npm ERR! invalid: iobroker.ham@5.0.1 /opt/iobroker/node_modules/iobroker.ham npm ERR! extraneous: jsonata@1.8.5 /opt/iobroker/node_modules/jsonata npm ERR! extraneous: mock-require@3.0.3 /opt/iobroker/node_modules/mock-require npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect npm ERR! extraneous: node-persist@0.0.11 /opt/iobroker/node_modules/node-persist npm ERR! extraneous: q@1.1.2 /opt/iobroker/node_modules/q npm ERR! extraneous: string-argv@0.3.1 /opt/iobroker/node_modules/string-argv npm ERR! extraneous: suncalc2@1.8.1 /opt/iobroker/node_modules/suncalc2 npm ERR! extraneous: virtual-tsc@0.6.1 /opt/iobroker/node_modules/virtual-tsc npm ERR! extraneous: vm2@3.9.5 /opt/iobroker/node_modules/vm2 npm ERR! extraneous: wake_on_lan@1.0.0 /opt/iobroker/node_modules/wake_on_lan npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-15T14_40_18_995Z-debug-0.log pi@raspberrypi202:/opt/iobroker $was bedeutet: iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project
-
pi@raspberrypi202:/opt/iobroker $ cd /opt/iobroker/ pi@raspberrypi202:/opt/iobroker $ npm prune 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 tarball tarball data for eiscp@https://github.com/GermanBluefox/node-eiscp/tarball/master/ (sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==) seems to be corrupted. Trying again. npm WARN tarball tarball data for eiscp@https://github.com/GermanBluefox/node-eiscp/tarball/master/ (sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==) seems to be corrupted. Trying again. npm WARN old lockfile Error: sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== integrity checksum failed when using sha512: wanted sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== but got sha512-ztYQ+rSQ8dXTqIhWgZ0TyQzo2UF0Nn1CBy0dqaJXDr7DqveVQHEzLOnLlNBpi8Nslmwqpmjfk+bO8RTXCvpKDw==. (49025 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18) npm WARN old lockfile at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:265:12) npm WARN old lockfile at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:269:24) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18) npm WARN old lockfile at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) npm WARN old lockfile Could not fetch metadata for eiscp@https://github.com/GermanBluefox/node-eiscp/tarball/master/ Error: sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== integrity checksum failed when using sha512: wanted sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w== but got sha512-ztYQ+rSQ8dXTqIhWgZ0TyQzo2UF0Nn1CBy0dqaJXDr7DqveVQHEzLOnLlNBpi8Nslmwqpmjfk+bO8RTXCvpKDw==. (49025 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18) npm WARN old lockfile at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:265:12) npm WARN old lockfile at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:269:24) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18) npm WARN old lockfile at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) { npm WARN old lockfile code: 'EINTEGRITY', npm WARN old lockfile found: Integrity { sha512: [ [Hash] ] }, npm WARN old lockfile expected: [ npm WARN old lockfile Hash { npm WARN old lockfile source: 'sha512-8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==', npm WARN old lockfile digest: '8rhOGaP70dl/3YEOhvfbDcw0qX90S1wrqjyb6eQ4+/ptDMAmk6nD+sYK+hgXwxGln3gRaqIm8ePgkRRFpbV91w==', npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile options: [] npm WARN old lockfile } npm WARN old lockfile ], npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile sri: Integrity { sha512: [ [Hash] ] } npm WARN old lockfile } npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/homebridge-plugin-wrapper npm ERR! dest /opt/iobroker/node_modules/.homebridge-plugin-wrapper-fUhrzAmo npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/homebridge-plugin-wrapper' -> '/opt/iobroker/node_modules/.homebridge-plugin-wrapper-fUhrzAmo' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-15T14_37_58_730Z-debug-0.log pi@raspberrypi202:/opt/iobroker $ nüm ls -bash: nüm: Kommando nicht gefunden. pi@raspberrypi202:/opt/iobroker $ npm ls iobroker.inst@3.0.0 /opt/iobroker ├── @types/caseless@0.12.2 extraneous ├── @types/request@2.48.7 extraneous ├── @types/tough-cookie@4.0.1 extraneous ├── buffer-shims@1.0.0 extraneous ├── coffee-compiler@0.3.2 extraneous ├── coffee-script@1.12.7 extraneous ├── decimal.js@10.3.1 extraneous ├── futoin-hkdf@1.4.3 extraneous ├── homebridge-plugin-wrapper@2.2.1 extraneous ├── iobroker.admin@5.1.25 ├── iobroker.backitup@2.1.17 ├── iobroker.discovery@2.7.0 ├── iobroker.esphome@0.2.4 ├── iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project ├── iobroker.heatingcontrol@2.7.1 ├── iobroker.history@1.9.13 ├── iobroker.influxdb@2.6.2 ├── iobroker.info@1.9.8 ├── iobroker.javascript@5.2.13 ├── iobroker.js-controller@3.3.18 ├── iobroker.modbus@3.4.17 ├── iobroker.mqtt@2.4.0 ├── iobroker.onkyo@2.1.0 ├── iobroker.openweathermap@0.1.0 ├── iobroker.ping@1.5.0 ├── iobroker.shelly@5.3.1 ├── iobroker.tr-064@4.2.14 ├── iobroker.vis@1.4.4 ├── iobroker.web@3.4.7 ├── iobroker.zigbee@1.6.3 ├── jsonata@1.8.5 extraneous ├── mock-require@3.0.3 extraneous ├── node-inspect@2.0.0 extraneous ├── node-persist@0.0.11 extraneous ├── q@1.1.2 extraneous ├── string-argv@0.3.1 extraneous ├── suncalc2@1.8.1 extraneous ├── virtual-tsc@0.6.1 extraneous ├── vm2@3.9.5 extraneous └── wake_on_lan@1.0.0 extraneous npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.2 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.7 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.1 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: buffer-shims@1.0.0 /opt/iobroker/node_modules/buffer-shims npm ERR! extraneous: coffee-compiler@0.3.2 /opt/iobroker/node_modules/coffee-compiler npm ERR! extraneous: coffee-script@1.12.7 /opt/iobroker/node_modules/coffee-script npm ERR! extraneous: decimal.js@10.3.1 /opt/iobroker/node_modules/decimal.js npm ERR! extraneous: futoin-hkdf@1.4.3 /opt/iobroker/node_modules/futoin-hkdf npm ERR! extraneous: homebridge-plugin-wrapper@2.2.1 /opt/iobroker/node_modules/homebridge-plugin-wrapper npm ERR! invalid: iobroker.ham@5.0.1 /opt/iobroker/node_modules/iobroker.ham npm ERR! extraneous: jsonata@1.8.5 /opt/iobroker/node_modules/jsonata npm ERR! extraneous: mock-require@3.0.3 /opt/iobroker/node_modules/mock-require npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect npm ERR! extraneous: node-persist@0.0.11 /opt/iobroker/node_modules/node-persist npm ERR! extraneous: q@1.1.2 /opt/iobroker/node_modules/q npm ERR! extraneous: string-argv@0.3.1 /opt/iobroker/node_modules/string-argv npm ERR! extraneous: suncalc2@1.8.1 /opt/iobroker/node_modules/suncalc2 npm ERR! extraneous: virtual-tsc@0.6.1 /opt/iobroker/node_modules/virtual-tsc npm ERR! extraneous: vm2@3.9.5 /opt/iobroker/node_modules/vm2 npm ERR! extraneous: wake_on_lan@1.0.0 /opt/iobroker/node_modules/wake_on_lan npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-15T14_40_18_995Z-debug-0.log pi@raspberrypi202:/opt/iobroker $was bedeutet: iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project
@wolfgangfb sagte in Tuya (original) in IO-Broker:
was bedeutet: iobroker.ham@5.0.1 invalid: "^4.0.2" from the root project
Das bedeutet, das die package-lock.json nicht richtig ist und da noch eine Version 4.0.2 eingetragen ist.
Und bei node-eiscp ist auch was schief. Ich kenne das Modul auch garnicht, hab ich nicht in meinem System drin.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden579
Online32.9k
Benutzer83.0k
Themen1.3m
Beiträge