JS-Controller update, was jetzt
-
pi@raspberrypi:~ $ curl -sL https:deb.nodesource.com/setup_16.x | sudo -E bash - pi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. pi@raspberrypi:~ $ apt policy nodejs nodejs: Installed: 12.22.12-deb-1nodesource1 Candidate: 12.22.12-deb-1nodesource1 Version table: *** 12.22.12-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@raspberrypi:~ $jetzt habe ich 12.22.12
-
sudo apt update apt policy nodejs -
-
pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/nodesource.list deb https://deb.nodesource.com/node_12.x buster main deb-src https://deb.nodesource.com/node_12.x buster mainso?
-
Nach dem Installationsskript für nodejs16 sollte die eigentlich so aussehen:
deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye mainWas sagt denn:
curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bashso?
-
pi@raspberrypi:~ $ sudo apt install -y nodejs Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: nodejs 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 24.2 MB of archives. After this operation, 2,727 kB of additional disk space will be used. Get:1 https://deb.nodesource.com/node_16.x buster/main armhf nodejs armhf 16.18.0-deb-1nodesource1 [24.2 MB] Fetched 24.2 MB in 2s (10.3 MB/s) apt-listchanges: Reading changelogs... (Reading database ... 57436 files and directories currently installed.) Preparing to unpack .../nodejs_16.18.0-deb-1nodesource1_armhf.deb ... Unpacking nodejs (16.18.0-deb-1nodesource1) over (14.20.1-deb-1nodesource1) ... Setting up nodejs (16.18.0-deb-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/nodesource.list deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main pi@raspberrypi:~ $jetzt ist gegangen.
-
@silbroker sagte in JS-Controller update, was jetzt:
Unpacking nodejs (16.18.0-deb-1nodesource1) over (14.20.1-deb-1nodesource1)
Wo kam denn die 14.20.1 nun her?
-
@thomas-braun
habe zuerst die 14er kopiert und ausgeführt
und dann gemerkt das es geht.
Danach noch die 16er -
@silbroker
Und was kommt beiuname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejsjetzt um's Eck?
-
@silbroker sagte in JS-Controller update, was jetzt:
habe zuerst die 14er kopiert und ausgeführt
und dann gemerkt das es geht.Mach bitte nicht irgendwas nebenher von dem ich nichts weiß. Das macht es nicht leichter dir zu helfen! Im Gegenteil...
-
pi@raspberrypi:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.18.0 v16.18.0 8.19.2 pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker /home/pi Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_16.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. nodejs: Installed: 16.18.0-deb-1nodesource1 Candidate: 16.18.0-deb-1nodesource1 Version table: *** 16.18.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages -
iobroker restart iobroker status -
pi@raspberrypi:~ $ iobroker restart pi@raspberrypi:~ $ iobroker status node:internal/modules/cjs/loader:988 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15) at Function.Module._load (node:internal/modules/cjs/loader:833:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:22:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } pi@raspberrypi:~ $ -
iobroker stop cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iobroker start -
@thomas-braun sagte in JS-Controller update, was jetzt:
iobroker start
pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller 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 deprecated @types/keyv@4.2.0: This is a stub types definition. keyv provides its own type definitions, so you do not need this installed. added 682 packages, removed 21 packages, and changed 29 packages in 2m 101 packages are looking for funding run `npm fund` for details pi@raspberrypi:/opt/iobroker $ iobroker startjetzt ist sie wieder online. Muss ich sonst noch etwas machen / beachten?
-
iobroker update -i iobroker status -
pi@raspberrypi:/opt/iobroker $ iobroker update -i Used repository: beta Adapter "admin" : 6.2.23 , installed 4.1.12 [Updatable] Adapter "deconz" : 1.3.21 , installed 2.0.5 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "info" : 1.9.21 , installed 1.9.21 Adapter "jarvis" : 3.0.15 , installed 2.2.5 [Updatable] Adapter "javascript" : 6.0.3 , installed 4.10.8 [Updatable] Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "loxone" : 3.0.0 , installed 2.2.3 [Updatable] Adapter "rpi2" : 1.3.2 , installed 1.3.1 [Updatable] Adapter "shelly" : 6.2.4 , installed 4.1.2 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.1.10 , installed 3.1.5 [Updatable] Adapter "sonos" : 2.2.3 , installed 2.1.1 [Updatable] Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3 Adapter "web" : 5.2.10 , installed 3.1.0 [Updatable] pi@raspberrypi:/opt/iobroker $ iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonl pi@raspberrypi:/opt/iobroker $ -
@silbroker Was willste denn mit dem alten Kram beta-testen?
Stell das Repo auf stable und dann zieh das alles auf den stabilen Stand. -
@silbroker sagte in JS-Controller update, was jetzt:
Adapter "deconz" : 1.3.21 , installed 2.0.5
Und was ist das für eine Version?
deconz github: 1.3.21 latest: 1.3.21 for 5 months stable: 1.3.21 for 5 months -
Das konnte ich nicht updaten weil der JS-Controller zu alt war.
