root@Server ~ > sudo apt-get update
Holen:1 http://security.debian.org/debian-security stretch/updates InRelease [94,3 kB]
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
Holen:3 http://ftp.de.debian.org/debian stretch-updates InRelease [91,0 kB]
OK:4 http://ftp.de.debian.org/debian stretch Release
OK:5 https://deb.nodesource.com/node_11.x stretch InRelease
Es wurden 185 kB in 2 s geholt (90,7 kB/s).
Paketlisten werden gelesen... Fertig
root@Server ~ > sudo apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.... 50%
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
tzdata
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 273 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 2.048 B Plattenplatz zusätzlich benutzt.
Holen:1 http://ftp.de.debian.org/debian stretch-updates/main i386 tzdata all 2019a-0+deb9u1 [273 kB]
Es wurden 273 kB in 0 s geholt (1.099 kB/s).
Lese Changelogs... Fertig
Vorkonfiguration der Pakete ...
(Lese Datenbank ... 62855 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../tzdata_2019a-0+deb9u1_all.deb ...
Entpacken von tzdata (2019a-0+deb9u1) über (2018i-0+deb9u1) ...
tzdata (2019a-0+deb9u1) wird eingerichtet ...
Current default time zone: 'Europe/Berlin'
Local time is now: Tue Apr 2 17:08:28 CEST 2019.
Universal Time is now: Tue Apr 2 15:08:28 UTC 2019.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
root@Server ~ > sudo apt-get install build-essential libssl-dev
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.... 50%
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
build-essential ist schon die neueste Version (12.3).
libssl-dev ist schon die neueste Version (1.1.0j-1~deb9u1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@Server ~ >
root@Server ~ > curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 4.x LTS Argon is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_8.x — Node.js 8 LTS "Carbon" (recommended)
* https://deb.nodesource.com/setup_10.x — Node.js 10 Current
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 4.x LTS Argon repo...
## Populating apt-get cache...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
OK:5 https://deb.nodesource.com/node_11.x stretch InRelease
Paketlisten werden gelesen... Fertig
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_4.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK
## Creating apt sources list file for the NodeSource Node.js 4.x LTS Argon repo...
+ echo 'deb https://deb.nodesource.com/node_4.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_4.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
Holen:5 https://deb.nodesource.com/node_4.x stretch InRelease [4.647 B]
Holen:7 https://deb.nodesource.com/node_4.x stretch/main Sources [762 B]
Holen:8 https://deb.nodesource.com/node_4.x stretch/main i386 Packages [1.006 B]
Es wurden 6.415 B in 2 s geholt (2.384 B/s).
Paketlisten werden gelesen... Fertig
## Run `sudo apt-get install -y nodejs` to install Node.js 4.x LTS Argon and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
root@Server ~ > sudo apt-get install -y nodejs
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
nodejs
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 8.016 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 22,2 MB Plattenplatz zusätzlich benutzt.
Holen:1 https://deb.nodesource.com/node_4.x stretch/main i386 nodejs i386 4.9.1-1nodesource1 [8.016 kB]
Es wurden 8.016 kB in 1 s geholt (4.213 kB/s).
apt-listchanges: Lese Changelogs...
(Lese Datenbank ... 62855 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../nodejs_4.9.1-1nodesource1_i386.deb ...
Entpacken von nodejs (4.9.1-1nodesource1) über (4.8.2~dfsg-1) ...
nodejs (4.9.1-1nodesource1) wird eingerichtet ...
Trigger für man-db (2.7.6.1-2) werden verarbeitet ...
root@Server ~ > curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 5.x is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_8.x — Node.js 8 LTS "Carbon" (recommended)
* https://deb.nodesource.com/setup_10.x — Node.js 10 Current
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 5.x repo...
## Populating apt-get cache...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
OK:5 https://deb.nodesource.com/node_4.x stretch InRelease
Paketlisten werden gelesen... Fertig
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dists/stretch/Release'
## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
root@Server ~ > sudo apt-get install -y nodejs
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
nodejs ist schon die neueste Version (4.9.1-1nodesource1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@Server ~ > curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
## Installing the NodeSource Node.js 6.x LTS Boron repo...
## Populating apt-get cache...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
OK:5 https://deb.nodesource.com/node_4.x stretch InRelease
Paketlisten werden gelesen... Fertig
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_6.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK
## Creating apt sources list file for the NodeSource Node.js 6.x LTS Boron repo...
+ echo 'deb https://deb.nodesource.com/node_6.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_6.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
Holen:5 https://deb.nodesource.com/node_6.x stretch InRelease [4.635 B]
Holen:7 https://deb.nodesource.com/node_6.x stretch/main i386 Packages [1.011 B]
Es wurden 5.646 B in 2 s geholt (2.539 B/s).
Paketlisten werden gelesen... Fertig
## Run `sudo apt-get install -y nodejs` to install Node.js 6.x LTS Boron and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
root@Server ~ > sudo apt-get install -y nodejs
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
nodejs
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 10,6 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 13,5 MB Plattenplatz zusätzlich benutzt.
Holen:1 https://deb.nodesource.com/node_6.x stretch/main i386 nodejs i386 6.16.0-1nodesource1 [10,6 MB]
Es wurden 10,6 MB in 2 s geholt (4.340 kB/s).
apt-listchanges: Lese Changelogs...
(Lese Datenbank ... 65516 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../nodejs_6.16.0-1nodesource1_i386.deb ...
Detected old npm client, removing...
Entpacken von nodejs (6.16.0-1nodesource1) über (4.9.1-1nodesource1) ...
nodejs (6.16.0-1nodesource1) wird eingerichtet ...
Trigger für man-db (2.7.6.1-2) werden verarbeitet ...
root@Server ~ > curl -sL https://deb.nodesource.com/setup_11.x | sudo -E bash -
## Installing the NodeSource Node.js 11.x repo...
## Populating apt-get cache...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
OK:5 https://deb.nodesource.com/node_6.x stretch InRelease
Paketlisten werden gelesen... Fertig
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_11.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK
## Creating apt sources list file for the NodeSource Node.js 11.x repo...
+ echo 'deb https://deb.nodesource.com/node_11.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_11.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
OK:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
OK:3 http://ftp.de.debian.org/debian stretch-updates InRelease
OK:4 http://ftp.de.debian.org/debian stretch Release
Holen:5 https://deb.nodesource.com/node_11.x stretch InRelease [4.585 B]
Es wurden 4.585 B in 1 s geholt (2.533 B/s).
Paketlisten werden gelesen... Fertig
## Run `sudo apt-get install -y nodejs` to install Node.js 11.x and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
root@Server ~ > sudo apt-get install -y nodejs
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
nodejs ist schon die neueste Version (6.16.0-1nodesource1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@Server ~ > sudo apt-get install python g++ libavahi-compat-libdnssd-dev
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
libavahi-compat-libdnssd-dev ist schon die neueste Version (0.6.32-2).
g++ ist schon die neueste Version (4:6.3.0-4).
python ist schon die neueste Version (2.7.13-2).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@Server ~ > npm install -g --unsafe-perm homebridge
/usr/bin/homebridge -> /usr/lib/node_modules/homebridge/bin/homebridge
> [email protected] install /usr/lib/node_modules/homebridge/node_modules/curve25519-n
> node-gyp rebuild
make: Verzeichnis „/usr/lib/node_modules/homebridge/node_modules/curve25519-n/build“ wird betreten
CXX(target) Release/obj.target/curve/node_curve.o
SOLINK_MODULE(target) Release/obj.target/curve.node
COPY Release/curve.node
make: Verzeichnis „/usr/lib/node_modules/homebridge/node_modules/curve25519-n/build“ wird verlassen
> [email protected] install /usr/lib/node_modules/homebridge/node_modules/ed25519-hap
> node-gyp rebuild
make: Verzeichnis „/usr/lib/node_modules/homebridge/node_modules/ed25519-hap/build“ wird betreten
CC(target) Release/obj.target/ed25519/src/ed25519/keypair.o
CC(target) Release/obj.target/ed25519/src/ed25519/sign.o
CC(target) Release/obj.target/ed25519/src/ed25519/open.o
CC(target) Release/obj.target/ed25519/src/ed25519/crypto_verify_32.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_double_scalarmult.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_scalarmult_base.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_precomp_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_cached.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_madd.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_msub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p3.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_1.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_cmov.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_copy.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_neg.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_mul.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq2.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_invert.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnegative.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnonzero.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_pow22523.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_reduce.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_muladd.o
CXX(target) Release/obj.target/ed25519/src/ed25519.o
SOLINK_MODULE(target) Release/obj.target/ed25519.node
COPY Release/ed25519.node
make: Verzeichnis „/usr/lib/node_modules/homebridge/node_modules/ed25519-hap/build“ wird verlassen
/usr/lib
??? [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]
? ? ??? [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]
root@Server ~ > npm -g outdated
Package Current Wanted Latest Location
npm 3.10.10 6.9.0 6.9.0
root@Server ~ > npm -g update homebridge
root@Server ~ > mkdir -p ~/.homebridge
root@Server ~ > cd ~/.homebridge/
root@Server ~/.homebridge > nano ~/.homebridge/config.json
root@Server ~/.homebridge > homebridge
[2019-4-2 17:14:32] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-2 17:14:32] ---
[2019-4-2 17:14:32] No plugins found. See the README for information on installing plugins.
[2019-4-2 17:14:32] Loading 1 platforms...
/usr/lib/node_modules/homebridge/lib/api.js:134
throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
^
Error: The requested platform 'FHEM' was not registered by any plugin.
at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:134:13)
at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:326:45)
at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:89:36)
at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
root@Server ~/.homebridge > cd..
-bash: cd..: Kommando nicht gefunden.
root@Server ~/.homebridge > cd
root@Server ~ > homebridge
[2019-4-2 17:14:52] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-2 17:14:52] ---
[2019-4-2 17:14:53] No plugins found. See the README for information on installing plugins.
[2019-4-2 17:14:53] Loading 1 platforms...
/usr/lib/node_modules/homebridge/lib/api.js:134
throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
^
Error: The requested platform 'FHEM' was not registered by any plugin.
at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:134:13)
at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:326:45)
at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:89:36)
at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
root@Server ~ >