Liebe Community,
bei mir läuft HomeBridge über homebridge-config-ui-x seit Monaten (und nach wie vor) problemlos auf meinem Raspberry 4 (siehe Bild). Nun wollte ich statt über homebridge-config-ui-x direkt über die Konsole ein Plugin auf die aktuelle Betaversion aktualisieren. Da dies ja nicht mittels homebridge-config-ui-x funktioniert habe ich im Terminal mittels sudo npm i homebridge-shelly@beta machen.
sudo npm i homebridge-shelly@beta
npm WARN saveError ENOENT: no such file or directory, open '/var/lib/homebridge/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/var/lib/homebridge/package.json'
npm WARN homebridge No description
npm WARN homebridge No repository field.
npm WARN homebridge No README data
npm WARN homebridge No license field.
added 90 packages from 58 contributors and audited 90 packages in 11.536s
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
Auch nach einem Reboot wird aber nach wie vor die aktuellste NICHT Beta Version 0.14 dieses Plugins von HomeBridge geladen. Alles läuft darüber hinaus weiterhin problemlos.
Also hab ich mal nachgesehen was sudo npm list -g --depth=0 so zurückgibt, und nun bin ich erstaunt:
sudo npm list -g --depth=0
/usr/lib
├─┬ UNMET DEPENDENCY [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ UNMET DEPENDENCY [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ UNMET DEPENDENCY [email protected]
│ ├── @nestjs/[email protected]
│ ├── @nestjs/[email protected]
│ ├── @nestjs/[email protected]
│ ├── @nestjs/[email protected]
│ ├── @nestjs/[email protected]
│ ├── @nestjs/[email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ UNMET DEPENDENCY [email protected]
│ ├── [email protected]
│ └── [email protected]
└─┬ UNMET DEPENDENCY [email protected]
├── @node-red/[email protected]
├── @node-red/[email protected]
├── @node-red/[email protected]
├── @node-red/[email protected]
npm ERR! missing: [email protected], required by lib
npm ERR! missing: [email protected], required by lib
npm ERR! missing: [email protected], required by lib
npm ERR! missing: [email protected], required by lib
npm ERR! missing: [email protected], required by lib
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: @types/[email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
...
...
Ich hab also irgendein Node oder NPM Problem wie es scheint. Da HomeBridge aber rund läuft und auch Plugins über das Gui von homebridge-config-ui-x problemlos nachgeladen werden können bin ich etwas ratlos. Wo könnte hier der Hund begraben sein?