[How-to] Node.js für ioBroker richtig updaten
-
@homoran verwende Google Chrome, hab meistens gleich auf reply gedrückt und konnte es nie abschicken.
Scheinbar muss ich die Seite vorher aktualisieren, komischerweise nach paar Stunden ging das Submit dann.
Deshalb dachte ich das eine Einstellung vom Board war. -
Warum so kompliziert?
Wenn die Infrastruktur sonst passt ändert man einfach in der Datei/etc/apt/sources.list.d/nodesource.list
Die entprechende Zeilen ab. Hier mal meine als Beispiel:deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bookworm main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bookworm main deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x bookworm main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x bookworm main # deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_19.x bookworm main # deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_19.x bookworm main # deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x bookworm main # deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x bookworm mainWenn ich mal irgendwann auf nodejs20 gehe nehme ich das
#-Kommentarzeichen raus und hol mir die Version dann wie üblich per Paketmanager rein. -
@thomas-braun said in [How-to] Node.js für ioBroker richtig updaten:
/etc/apt/sources.list.d/nodesource.list
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 mainsteht bei mir drin.
Also meinst du das ich dann
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 main deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x bullseye main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x bullseye maindazu schreibe (oder 16 auskommentieren) und dann wie weiter vorgehen um auf 18 zu gehen?
Iob stop und dann?
Wie mache ich den richtigen Downgrade auf 16 falls einiges wieder nicht geht? -
@grazer75 sagte in [How-to] Node.js für ioBroker richtig updaten:
Downgrade auf 16 falls einiges wieder nicht geht wie am besten?
So wie es im HowTo bereits drin steht (Zumindest in meinem...). Mit
sudo apt install nodejs=WUNSCHVERSIONWenn du die 18er-Quelle dann aber nicht 'trocken' legst wird dir das allerdings dann nantürlich wieder als update serviert. (Man könnte das Paket auch 'pinnen', aber das führt etwas weit).
-
@thomas-braun mit 18 wieder viele Meldungen
erstmal iob diag
Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.4 Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 20:41:31 up 2 min, 2 users, load average: 3.46, 1.59, 0.61 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=54.0'C volt=0.9460V *** Time and Time Zones *** Local time: Sun 2023-04-16 20:41:32 CEST Universal time: Sun 2023-04-16 18:41:32 UTC RTC time: n/a Time zone: Europe/Vienna (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** andreas /home/andreas andreas adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 2.2G 5.2G 6.0M 409M 5.5G Swap: 99M 0B 99M Total: 7.9G 2.2G 5.3G 7811 M total memory 2207 M used memory 2290 M active memory 198 M inactive memory 5194 M free memory 51 M buffer memory 357 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 118G 6.3G 107G 6% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 924K 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 253M 31M 222M 13% /boot tmpfs tmpfs 782M 0 782M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sun Apr 16 20:39:09 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:C5:38:E2 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyS0,115200 console=tty1 root=PARTUUID=270f37e4-02 rootfstype=ext4 fsck.repair=yes rootwait [Sun Apr 16 20:39:11 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Sun Apr 16 20:39:11 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Sun Apr 16 20:39:12 2023] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro Files in neuralgic directories: /var: 2.2G /var/ 1.6G /var/log 1.4G /var/log/journal/deee1983c79b418b90418f11a8f1c85d 1.4G /var/log/journal 317M /var/cache Archived and active journals take up 1.3G in the file system. /opt/iobroker/backups: 395M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 452M /opt/iobroker/iobroker-data/ 333M /opt/iobroker/iobroker-data/files 87M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 52M /opt/iobroker/iobroker-data/files/javascript.admin The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.10538062.js.map 23M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.904d455f.js.map 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 15M /opt/iobroker/iobroker-data/files/meteoalarm.admin/geocodes.json *** NodeJS-Installation *** /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 nodejs: Installed: 18.16.0-deb-1nodesource1 Candidate: 18.16.0-deb-1nodesource1 Version table: *** 18.16.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 16.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Node.js v18.16.0 /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is closed. at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41) at Readable.read (node:internal/streams/readable:496:12) at resume_ (node:internal/streams/readable:999:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Node.js v18.16.0 Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: 7.0.3 Adapters from github: 4 Adapter State system.adapter.accuweather.0 : accuweather : raspberrypi - enabled + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.alarm.0 : alarm : raspberrypi - enabled + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.benchmark.0 : benchmark : raspberrypi - disabled + system.adapter.bmw.0 : bmw : raspberrypi - enabled system.adapter.broadlink2.0 : broadlink2 : raspberrypi - disabled system.adapter.chromecast.0 : chromecast : raspberrypi - disabled system.adapter.cloud.0 : cloud : raspberrypi - disabled + system.adapter.coronavirus-statistics.0 : coronavirus-statistics: raspberrypi - enabled + system.adapter.countdown.0 : countdown : raspberrypi - enabled + system.adapter.device-reminder.0 : device-reminder : raspberrypi - enabled system.adapter.devices.0 : devices : raspberrypi - disabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.echarts.0 : echarts : raspberrypi - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled + system.adapter.email.0 : email : raspberrypi - enabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.fb-checkpresence.1 : fb-checkpresence : raspberrypi - disabled + system.adapter.firetv.0 : firetv : raspberrypi - enabled system.adapter.flot.0 : flot : raspberrypi - disabled system.adapter.followthesun.0 : followthesun : raspberrypi - enabled system.adapter.foobar2000.0 : foobar2000 : raspberrypi - disabled, port: 8888 + system.adapter.fritzbox.0 : fritzbox : raspberrypi - enabled system.adapter.fritzdect.0 : fritzdect : raspberrypi - disabled + system.adapter.fuelpricemonitor.0 : fuelpricemonitor : raspberrypi - enabled system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - disabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.hmip.0 : hmip : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.info.0 : info : raspberrypi - enabled system.adapter.iot.0 : iot : raspberrypi - enabled system.adapter.jarvis.0 : jarvis : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.lgtv11.0 : lgtv11 : raspberrypi - enabled, port: 8080 system.adapter.life360.0 : life360 : raspberrypi - disabled system.adapter.linkeddevices.0 : linkeddevices : raspberrypi - enabled system.adapter.linux-control.0 : linux-control : raspberrypi - enabled system.adapter.logparser.0 : logparser : raspberrypi - enabled + system.adapter.luftdaten.0 : luftdaten : raspberrypi - enabled system.adapter.meteoalarm.0 : meteoalarm : raspberrypi - enabled + system.adapter.mihome-vacuum.0 : mihome-vacuum : raspberrypi - enabled, port: 54321 system.adapter.mobile.0 : mobile : raspberrypi - disabled system.adapter.net-tools.0 : net-tools : raspberrypi - disabled + system.adapter.netatmo-crawler.0 : netatmo-crawler : raspberrypi - enabled system.adapter.netatmo-energy.0 : netatmo-energy : raspberrypi - enabled + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled + system.adapter.nuki-extended.0 : nuki-extended : raspberrypi - enabled system.adapter.nuki.0 : nuki : raspberrypi - enabled system.adapter.nut.0 : nut : raspberrypi - disabled system.adapter.onvif.0 : onvif : raspberrypi - enabled system.adapter.openweathermap.0 : openweathermap : raspberrypi - enabled + system.adapter.owntracks.0 : owntracks : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 system.adapter.parser.0 : parser : raspberrypi - enabled system.adapter.paw.0 : paw : raspberrypi - disabled, port: 8898 + system.adapter.ping.0 : ping : raspberrypi - enabled + system.adapter.pushbullet.0 : pushbullet : raspberrypi - enabled system.adapter.radar2.0 : radar2 : raspberrypi - enabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled system.adapter.sayit.0 : sayit : raspberrypi - enabled system.adapter.shelly.0 : shelly : raspberrypi - disabled, port: 1882, bind: 0.0.0.0 system.adapter.smartcontrol.0 : smartcontrol : raspberrypi - enabled system.adapter.snmp.0 : snmp : raspberrypi - enabled system.adapter.socketio.0 : socketio : raspberrypi - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1884, bind: 192.168.1.139 system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - disabled + system.adapter.spotify-premium.0 : spotify-premium : raspberrypi - enabled system.adapter.statistics.0 : statistics : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled system.adapter.tr-064.1 : tr-064 : raspberrypi - disabled system.adapter.trashschedule.0 : trashschedule : raspberrypi - disabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled system.adapter.upnp.0 : upnp : raspberrypi - enabled system.adapter.virtualpowermeter.0 : virtualpowermeter : raspberrypi - enabled system.adapter.vis-history.0 : vis-history : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : raspberrypi - enabled + system.adapter.wifilight.0 : wifilight : raspberrypi - enabled system.adapter.windows-control.0 : windows-control : raspberrypi - enabled system.adapter.withings.0 : withings : raspberrypi - enabled system.adapter.xbox.0 : xbox : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.lgtv11.0 : lgtv11 : raspberrypi - enabled, port: 8080 + system.adapter.mihome-vacuum.0 : mihome-vacuum : raspberrypi - enabled, port: 54321 + system.adapter.owntracks.0 : owntracks : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.socketio.0 : socketio : raspberrypi - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1884, bind: 192.168.1.139 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "accuweather" : 1.2.1 , installed 1.2.1 Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "alarm" : 3.3.9 , installed 3.3.9 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "backitup" : 2.6.16 , installed 2.6.16 Adapter "benchmark" : 1.1.4 , installed 1.1.4 Adapter "bmw" : 2.5.7 , installed 2.5.7 Adapter "broadlink2" : 2.1.5 , installed 2.1.5 Adapter "chromecast" : 3.0.3 , installed 3.0.3 Adapter "cloud" : 4.3.0 , installed 4.3.0 Adapter "coronavirus-statistics": 0.8.7, installed 0.8.7 Adapter "countdown" : 1.2.5 , installed 1.2.5 Adapter "device-reminder": 1.2.9 , installed 1.2.9 Adapter "devices" : 1.1.2 , installed 1.1.2 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "echarts" : 1.0.12 , installed 1.0.12 Adapter "ecovacs-deebot": 1.4.13 , installed 1.4.13 Adapter "email" : 1.1.4 , installed 1.1.4 Adapter "fb-checkpresence": 1.1.26, installed 1.1.26 Adapter "firetv" : 1.0.0 , installed 1.0.0 Adapter "flot" : 1.11.0 , installed 1.11.0 Adapter "followthesun" : 0.4.1 , installed 0.4.1 Adapter "foobar2000" : 2.0.4 , installed 2.0.4 Adapter "fritzbox" : 0.2.1 , installed 0.2.1 Adapter "fritzdect" : 2.2.6 , installed 2.2.6 Adapter "fuelpricemonitor": 0.3.4 , installed 0.3.4 Adapter "fullybrowser" : 2.1.2 , installed 2.1.2 Adapter "history" : 2.2.4 , installed 2.2.4 Adapter "hmip" : 1.20.0 , installed 1.20.0 Adapter "ical" : 1.13.2 , installed 1.13.2 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.14.2 , installed 1.14.2 Adapter "jarvis" : 3.1.2 , installed 3.1.2 Adapter "javascript" : 6.1.4 , installed 7.0.3 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "lgtv11" : 1.0.5 , installed 1.0.5 Adapter "linkeddevices": 1.5.5 , installed 1.5.5 Adapter "linux-control": 1.1.3 , installed 1.1.3 Adapter "logparser" : 2.1.1 , installed 2.1.1 Adapter "luftdaten" : 2.2.4 , installed 2.2.4 Adapter "meteoalarm" : 2.3.5 , installed 2.3.5 Adapter "mihome-vacuum": 3.9.5 , installed 3.9.5 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "net-tools" : 0.2.0 , installed 0.2.0 Adapter "netatmo" : 2.0.5 , installed 2.0.5 Adapter "netatmo-crawler": 0.8.1 , installed 0.8.1 Adapter "netatmo-energy": 2.3.1 , installed 2.3.1 Adapter "nuki" : 1.6.0 , installed 1.6.0 Adapter "nuki-extended": 2.3.1 , installed 2.3.1 Adapter "nut" : 1.6.0 , installed 1.6.0 Adapter "onvif" : 1.0.4 , installed 1.0.4 Adapter "openweathermap": 0.3.3 , installed 0.3.3 Adapter "owntracks" : 1.0.5 , installed 1.0.5 Adapter "parser" : 1.1.8 , installed 1.1.8 Adapter "paw" : 0.3.2 , installed 0.3.2 Adapter "ping" : 1.5.3 , installed 1.5.3 Adapter "pushbullet" : 0.0.11 , installed 0.0.11 Adapter "radar2" : 2.0.3 , installed 2.0.3 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "sayit" : 1.12.3 , installed 1.12.3 Adapter "shelly" : 6.3.1 , installed 6.3.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smartcontrol" : 1.3.2 , installed 1.3.2 Adapter "snmp" : 2.4.6 , installed 2.4.6 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "spotify-premium": 1.2.1 , installed 1.2.1 Adapter "statistics" : 2.3.0 , installed 2.3.0 Adapter "telegram" : 1.15.2 , installed 1.15.2 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "trashschedule": 2.2.0 , installed 2.2.0 Adapter "tuya" : 3.13.1 , installed 3.13.1 Adapter "upnp" : 1.0.21 , installed 1.0.21 Adapter "virtualpowermeter": 1.4.6, installed 1.4.6 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3 Adapter "wifilight" : 1.1.4 , installed 1.1.4 Adapter "windows-control": 0.1.5 , installed 0.1.5 Adapter "withings" : 0.0.13 , installed 0.0.13 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "xbox" : 1.0.2 , installed 1.0.2 Adapter "zigbee" : 1.8.10 , installed 1.8.10 Objects and States Please stand by - This may take a while Objects: 29904 States: 24682 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://packages.sury.org/php bullseye InRelease Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease Hit:7 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 15749 514/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 15742 514/iobroker.js-con tcp 0 0 192.168.1.139:1884 0.0.0.0:* LISTEN 1001 14194 1063/io.sonoff.0 tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 23895 1756/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 11929 562/sshd: /usr/sbin tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 13956 1009/io.owntracks.0 tcp6 0 0 :::51989 :::* LISTEN 1001 17211 1210/io.nuki-extend tcp6 0 0 :::8081 :::* LISTEN 1001 15209 765/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 26807 2137/io.web.0 tcp6 0 0 :::8084 :::* LISTEN 1001 24036 2065/io.socketio.0 tcp6 0 0 :::80 :::* LISTEN 0 15000 573/apache2 tcp6 0 0 :::22 :::* LISTEN 0 11931 562/sshd: /usr/sbin tcp6 0 0 :::9999 :::* LISTEN 0 15004 573/apache2 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 17814 1161/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 17815 1161/io.tuya.0 udp 0 0 0.0.0.0:44617 0.0.0.0:* 1001 26831 2048/io.snmp.0 udp 0 0 0.0.0.0:67 0.0.0.0:* 1001 22280 2003/io.radar2.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 13240 827/dhcpcd udp 0 0 0.0.0.0:53421 0.0.0.0:* 1001 16758 964/io.mihome-vacuu udp 0 768 0.0.0.0:46003 0.0.0.0:* 1001 32789 2241/io.xbox.0 udp 0 0 0.0.0.0:42092 0.0.0.0:* 1001 26718 2091/io.upnp.0 udp 0 0 192.168.1.139:5353 0.0.0.0:* 1001 17759 1144/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12881 397/avahi-daemon: r udp 0 0 0.0.0.0:38559 0.0.0.0:* 1001 16663 857/io.javascript.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 25730 2091/io.upnp.0 udp 0 0 0.0.0.0:59680 0.0.0.0:* 108 12883 397/avahi-daemon: r udp6 0 0 :::5353 :::* 108 12882 397/avahi-daemon: r udp6 0 0 :::51466 :::* 108 12884 397/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-04-16 20:43:57.659 - info: radar2.0 (2003) first scan took 18.02 seconds 2023-04-16 20:43:57.660 - info: radar2.0 (2003) will scan external network every 60 minutes 2023-04-16 20:43:57.713 - info: followthesun.0 (2396) Started with JSON-Explorer version 0.1.10 2023-04-16 20:43:57.716 - info: followthesun.0 (2396) Sun position calculation will be done every 120 seconds 2023-04-16 20:43:57.722 - info: followthesun.0 (2396) Daily sun parameter calculation scheduled for 00:00:33 2023-04-16 20:43:58.289 - info: radar2.0 (2003) Adapter initialization finished! 2023-04-16 20:43:58.390 - info: netatmo-crawler.0 (1845) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule 2023-04-16 20:44:02.779 - info: host.raspberrypi instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-04-16 20:44:03.617 - info: info.0 (1670) starting. Version 1.9.19 in /opt/iobroker/node_modules/iobroker.info, node: v18.16.0, js-controller: 4.0.24 2023-04-16 20:44:04.083 - info: info.0 (1670) Reading/updating systemdata. 2023-04-16 20:44:05.316 - info: xbox.0 (2241) starting. Version 1.0.2 in /opt/iobroker/node_modules/iobroker.xbox, node: v18.16.0, js-controller: 4.0.24 2023-04-16 20:44:06.014 - info: xbox.0 (2241) Successfully loaded token 2023-04-16 20:44:06.717 - info: xbox.0 (2241) Xbox login url available at: https://login.live.com/oauth20_authorize.srf?client_id=5e5ead27-ed60-482d-b3fc-702b28a97404&response_type=code&approval_prompt=auto&scope=XboxLive.signin%20XboxLive.offline_access&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Fauth%2Fcallback 2023-04-16 20:44:06.720 - info: xbox.0 (2241) Copy the token (value after code=) after login into "apiToken" of the adapter config to enable the Xbox api 2023-04-16 20:44:06.762 - warn: xbox.0 (2241) Could not poll API: "No oauth token found. Run authentication flow first" 2023-04-16 20:44:07.626 - info: info.0 (1670) State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number" 2023-04-16 20:44:08.460 - info: info.0 (1670) State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string" 2023-04-16 20:44:08.814 - info: smartcontrol.0 (2036) Subscribing to all target devices and trigger states. 4 trigger schedules activated... 2023-04-16 20:44:09.510 - info: info.0 (1670) cpu Temp res = {"main":55.504,"cores":[],"max":55.504,"socket":[],"chipset":null} 2023-04-16 20:44:28.270 - info: netatmo-energy.0 (1948) API-Anfrage starten: homestatus 2023-04-16 20:44:32.394 - info: coronavirus-statistics.0 (1281) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment 2023-04-16 20:44:33.280 - info: host.raspberrypi instance system.adapter.coronavirus-statistics.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-04-16 20:44:41.850 - info: fuelpricemonitor.0 (1616) Terminated (NO_ERROR): Without reason 2023-04-16 20:44:42.436 - info: fuelpricemonitor.0 (1616) cleaned everything up... 2023-04-16 20:44:42.680 - info: host.raspberrypi instance system.adapter.fuelpricemonitor.0 terminated with code 0 (NO_ERROR)Summary ======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Debian GNU/Linux 11 (bullseye) Kernel: 6.1.21-v8+ Installation: Native Timezone: Europe/Vienna (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.8G 2.9G 4.1G 6.0M 797M 4.8G Swap: 99M 0B 99M Total: 7.9G 2.9G 4.2G Active iob-Instances: 57 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 29904 States: 24682 Size of iob-Database: 27M /opt/iobroker/iobroker-data/objects.jsonl 14M /opt/iobroker/iobroker-data/states.jsonlIobroker log
javascript.0 2023-04-16 20:48:57.954 warn Read-only state "javascript.0.MiHomeAll.lumi.158d0002a3299c.info.rssi" has been written without ack-flag with value "0" javascript.0 2023-04-16 20:48:57.946 warn Read-only state "javascript.0.MiHomeAll.396976417.info.rssi" has been written without ack-flag with value "-55" javascript.0 2023-04-16 20:48:57.943 warn Read-only state "javascript.0.MiHomeAll.lumi.158d0004ac0836.info.rssi" has been written without ack-flag with value "0" javascript.0 2023-04-16 20:48:57.939 warn Read-only state "javascript.0.MiHomeAll.408471265.info.rssi" has been written without ack-flag with value "-46" javascript.0 2023-04-16 20:48:57.717 warn script.js.XiaomiGeraeteCN: No supported Devices found! tuya.0 2023-04-16 20:49:52.026 warn 80157022e0980602099a: Error on Reconnect (1): connect ECONNRESET 192.168.1.212:6668 tuya.0 2023-04-16 20:49:52.016 warn 80248051e098069e47eb: Error on Reconnect (1): connect ECONNRESET 192.168.1.167:6668 tuya.0 2023-04-16 20:49:51.953 warn 47804507a4cf12ccd3ef: Error on Reconnect (1): connect ECONNRESET 192.168.1.161:6668 tuya.0 2023-04-16 20:49:51.820 warn 80157022e09806010425: Error on Reconnect (1): connect ECONNRESET 192.168.1.194:6668 wifilight.0 2023-04-16 20:49:51.495 error wrong device type. not yet supported! wifilight.0 2023-04-16 20:49:51.492 error config.device.type "" (HF-LPT120) is not a known device type. Skipping this device! Known types are: LW12, LD382A, LD686, LD382, UFO, MiLight, MiLightRGB, MiLightW rpi2.0 2023-04-16 20:49:30.607 error No Value found for cpu_frequency netatmo.0 2023-04-16 20:49:17.457 warn API Error: Please Authenticate manually once using the Admin UI of this instance. backitup.0 2023-04-16 20:50:13.179 error Dropbox: "expired_access_token/." backitup.0 2023-04-16 20:50:13.160 error Dropbox: "expired_access_token/." nuki-extended.0 2023-04-16 20:50:05.279 warn getWebApi(): Error retrieving smartlocks: Cannot read properties of undefined (reading 'toLowerCase') zigbee.0 2023-04-16 20:50:05.063 warn Extended PAN ID is reversed (expected=51b8a11c004b1200, actual=00124b001ca1b851) nuki-extended.0 2023-04-16 20:50:03.493 warn Failed retrieving /list from Nuki Bridge with name Schiess Nuki Bridge (forcePlainToken: false)! firetv.0 2023-04-16 20:50:33.728 error can not connect to 192.168.1.208 Error=spawn adb ENOENT firetv.0 2023-04-16 20:50:33.634 error adb executable not found. undefined zigbee.0 2023-04-16 20:50:49.101 error DeviceConfigure:Failed to DeviceConfigure.configure 0x003c84fffeb3dbf7 TS0044 (Error: Read 0x003c84fffeb3dbf7/1 genBasic(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240)) at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:415:23) at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)) onvif.0 2023-04-16 20:51:56.636 error Error during discovery: Error: Wrong ONVIF SOAP response,Error: Wrong ONVIF SOAP response,Error: Wrong ONVIF SOAP response,TypeError: Cannot read properties of undefined (reading 'endpointReference'),TypeError: Cannot read properties of undefined (reading 'endpointReference') onvif.0 2023-04-16 20:51:52.776 error Error Error: ONVIF SOAP Fault: The action requested requires authorization and the sender is not authorized onvif.0 2023-04-16 20:51:52.775 error Failed to login to 192.168.1.218:8000 with admin:$*****************************************************************************7 onvif.0 2023-04-16 20:51:52.539 error Error Error: ONVIF SOAP Fault: The action requested requires authorization and the sender is not authorized onvif.0 2023-04-16 20:51:52.538 error Failed to login to 192.168.1.211:8000 with admin:$*****************************************************************************7 onvif.0 2023-04-16 20:51:52.320 error undefined onvif.0 2023-04-16 20:51:52.320 error <?xml version="1.0" ?> <soap:Envelope > <soap:Header> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action> <wsa:MessageID>urn:uuid:0eaaa933-a101-4933-86f1-3ce46179ab26</wsa:MessageID> <wsa:RelatesTo>urn:uuid:8d65c8dd-fa75-977b-db4d-fc1d23082a1c</wsa:RelatesTo> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To> <wsd:AppSequence InstanceId="1170846535" MessageNumber="1"/> </soap:Header> <soap:Body> <wsd:ProbeMatches/> </soap:Body> </soap:Envelope> onvif.0 2023-04-16 20:51:52.319 error Discovery error Wrong SOAP message from 192.168.1.135:35191 onvif.0 2023-04-16 20:51:52.222 error undefined onvif.0 2023-04-16 20:51:52.221 error <?xml version="1.0" ?> <soap:Envelope > <soap:Header> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action> <wsa:MessageID>urn:uuid:0eaaa933-a101-4933-86f1-3ce46179ab26</wsa:MessageID> <wsa:RelatesTo>urn:uuid:8d65c8dd-fa75-977b-db4d-fc1d23082a1c</wsa:RelatesTo> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To> <wsd:AppSequence InstanceId="1170846535" MessageNumber="1"/> </soap:Header> <soap:Body> <wsd:ProbeMatches/> </soap:Body> </soap:Envelope> onvif.0 2023-04-16 20:51:52.219 error Discovery error Wrong SOAP message from 192.168.1.135:35191 onvif.0 2023-04-16 20:51:52.137 error Error Error: connect ECONNREFUSED 192.168.1.115:8000 onvif.0 2023-04-16 20:51:52.136 error Failed to login to 192.168.1.115:8000 with admin:$*****************************************************************************7 onvif.0 2023-04-16 20:51:51.863 error undefined onvif.0 2023-04-16 20:51:51.862 error onvif.0 2023-04-16 20:51:51.862 error Discovery error Wrong SOAP message from 192.168.1.211:3702 onvif.0 2023-04-16 20:51:51.848 error undefined onvif.0 2023-04-16 20:51:51.847 error onvif.0 2023-04-16 20:51:51.846 error Discovery error Wrong SOAP message from 192.168.1.218:3702 onvif.0 2023-04-16 20:51:51.816 error undefined onvif.0 2023-04-16 20:51:51.814 error onvif.0 2023-04-16 20:51:51.813 error Discovery error Wrong SOAP message from 192.168.1.115:3702 linux-control.0 2023-04-16 20:51:44.647 warn This object will not be created in future versions. Please report this to the developer. linux-control.0 2023-04-16 20:51:44.645 warn Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string" linux-control.0 2023-04-16 20:51:40.863 warn This object will not be created in future versions. Please report this to the developer. linux-control.0 2023-04-16 20:51:40.855 warn Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"Werde daher wieder auf 16 gehen, außer ihr wisst eine Lösung für die Fehler
Mein aktueller Status
which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.19.1 v16.19.1 8.19.3 nodejs: Installed: 16.19.1-deb-1nodesource1 Candidate: 18.16.0-deb-1nodesource1 Version table: 18.16.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages *** 16.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u3 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages -
Schaut für mich eher nach Netzwerk / PW Encoding aus.
Log dich jeweils bei den Dingern nochmal ein. -
@grazer75 sagte in [How-to] Node.js für ioBroker richtig updaten:
Werde daher wieder auf 16 gehen, außer ihr wisst eine Lösung für die Fehler
Du musst auch schon die Chance lassen den Output auch zu lesen...
-
@thomas-braun ich bin auf 16 zurück allerdings sind die Fehler noch da
zigbee.0 2023-04-16 21:07:43.024 error DeviceConfigure:Failed to DeviceConfigure.configure 0x003c84fffeb3dbf7 TS0044 (Error: Read 0x003c84fffeb3dbf7/1 genBasic(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240)) at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:415:23) at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)) firetv.0 2023-04-16 21:07:32.731 error can not connect to 192.168.1.208 Error=spawn adb ENOENT firetv.0 2023-04-16 21:07:32.614 error adb executable not found. undefined coronavirus-statistics.0 2023-04-16 21:07:14.106 warn Hospital Data Warning: Error: Cannot get german hospital data from divi: TypeError: Cannot read properties of undefined (reading 'toLowerCase') backitup.0 2023-04-16 21:07:13.950 error Dropbox: "expired_access_token/.." backitup.0 2023-04-16 21:07:13.948 error Dropbox: "expired_access_token/.." coronavirus-statistics.0 2023-04-16 21:07:09.893 warn This object will not be created in future versions. Please report this to the developer. coronavirus-statistics.0 2023-04-16 21:07:09.888 warn Object coronavirus-statistics.0.countryTranslator is invalid: Default value has to be type "string" but received type "number" zigbee.0 2023-04-16 21:06:59.736 warn Extended PAN ID is reversed (expected=51b8a11c004b1200, actual=00124b001ca1b851) nuki-extended.0 2023-04-16 21:06:58.499 warn getWebApi(): Error retrieving smartlocks: Cannot read properties of undefined (reading 'toLowerCase') nuki-extended.0 2023-04-16 21:06:56.839 warn Failed retrieving /list from Nuki Bridge with name Schiesstattgasse Nuki Bridge (forcePlainToken: false)! tuya.0 2023-04-16 21:06:52.531 warn 47804507a4cf12ccd3ef: Error on Reconnect (1): connect ECONNRESET 192.168.1.161:6668 tuya.0 2023-04-16 21:06:52.501 warn 80248051e098069e47eb: Error on Reconnect (1): connect ECONNRESET 192.168.1.167:6668 tuya.0 2023-04-16 21:06:51.754 warn 80157022e0980602099a: Error on Reconnect (1): connect ECONNRESET 192.168.1.212:6668 tuya.0 2023-04-16 21:06:51.625 warn 43024001f4cfa2de874f: Error on Reconnect (1): connect ECONNRESET 192.168.1.249:6668 tuya.0 2023-04-16 21:06:51.455 warn 80157022e09806010425: Error on Reconnect (1): connect ECONNRESET 192.168.1.194:6668 wifilight.0 2023-04-16 21:06:43.474 error wrong device type. not yet supported! wifilight.0 2023-04-16 21:06:43.470 error config.device.type "" (HF-LPT120) is not a known device type. Skipping this device!Known types are: LW12, LD382A, LD686, LD382, UFO, MiLight, MiLightRGB, MiLightW rpi2.0 2023-04-16 21:06:18.496 error No Value found for cpu_frequency mihome-vacuum.0 2023-04-16 21:06:09.094 warn No Answer for DeviceModel use model from Config mihome-vacuum.0 2023-04-16 21:06:09.092 warn No Answer for DeviceModel use old one mihome-vacuum.0 2023-04-16 21:06:09.090 error YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF netatmo.0 2023-04-16 21:06:07.174 warn API Error: Please Authenticate manually once using the Admin UI of this instance.Gestern hatte ich es geschafft das wieder weg geht.
Eventuell Cache purge bzw npm rebuild?
Überall alles neu machen, hab ich nicht wirklich Zeit.
Mit einem zurück auf 16 gestern ging es ohne das ich weiter was anpassen musste -
Alles keine Dinge die ich primär auf nodejs schieben würde.
-
@thomas-braun wie gesagt gestern hab ich mehrere Sachen probiert, ohne das ich ein Backup zurück restored habe
und dann waren die Fehler weg und ich zurück auf Version 16Nun bin ich auf 16, krieg schon wieder die Fehler nicht weg
host.raspberrypi 2023-04-16 21:20:00.149 warn instance system.adapter.netatmo-crawler.0 already running with pid 1571 zigbee.0 2023-04-16 21:19:34.992 error DeviceConfigure:Failed to DeviceConfigure.configure 0x003c84fffeb3dbf7 TS0044 (Error: Read 0x003c84fffeb3dbf7/1 genBasic(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240)) at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:415:23) at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)) firetv.0 2023-04-16 21:19:09.339 error can not connect to 192.168.1.208 Error=spawn adb ENOENT firetv.0 2023-04-16 21:19:09.136 error adb executable not found. undefined coronavirus-statistics.0 2023-04-16 21:19:06.257 warn Hospital Data Warning: Error: Cannot get german hospital data from divi: TypeError: Cannot read properties of undefined (reading 'toLowerCase') zigbee.0 2023-04-16 21:18:54.487 warn DeviceAvailability:Failed to ping 0x5c0272fffe5b8c0e TRADFRI Signal Repeater backitup.0 2023-04-16 21:18:53.396 error Dropbox: "expired_access_token/." backitup.0 2023-04-16 21:18:53.395 error Dropbox: "expired_access_token/." coronavirus-statistics.0 2023-04-16 21:18:51.607 warn This object will not be created in future versions. Please report this to the developer. coronavirus-statistics.0 2023-04-16 21:18:51.603 warn Object coronavirus-statistics.0.countryTranslator is invalid: Default value has to be type "string" but received type "number" zigbee.0 2023-04-16 21:18:49.027 warn Extended PAN ID is reversed (expected=51b8a11c004b1200, actual=00124b001ca1b851) nuki-extended.0 2023-04-16 21:18:43.554 warn getWebApi(): Error retrieving smartlocks: Cannot read properties of undefined (reading 'toLowerCase') nuki-extended.0 2023-04-16 21:18:42.175 warn Failed retrieving /list from Nuki Bridge with name Schiesstattgasse Nuki Bridge (forcePlainToken: false)! wifilight.0 2023-04-16 21:18:26.393 error wrong device type. not yet supported! wifilight.0 2023-04-16 21:18:26.388 error config.device.type "" (HF-LPT120) is not a known device type. Skipping this device!Known types are: LW12, LD382A, LD686, LD382, UFO, MiLight, MiLightRGB, MiLightW rpi2.0 2023-04-16 21:18:03.613 error No Value found for cpu_frequency netatmo.0 2023-04-16 21:17:51.067 warn API Error: Please Authenticate manually once using the Admin UI of this instance.wie komm ich wieder zu einer funktionierenden 16 Version außer jetzt wieder alles mögliche wie gestern zu probieren?`
-
Du wirst dir die einzelnen Adapter und deren Einstellungen anschauen müssen.
War der iobroker eigentlich heruntergefahren, als du nodejs upgedated hast?
-
@grazer75 sagte in [How-to] Node.js für ioBroker richtig updaten:
wie komm ich wieder zu einer funktionierenden 16 Version
warum nicht ein sauberes/frisches System aufsetzen und wenn alles aktuell ist iobroker und ein Backup einspielen ?
Der Beitrag wird ja sonst weiter aufgebläht ... -
@djmarc75 weil auch andere Sachen auf dem pi habe?
Tasmotaadmin etc -
@thomas-braun war er, iob stop
Wie gesagt gestern war das gleiche mit dem Update auf 18, waren dann Fehler auch nach dem downgrade auf 16.
Hab dann alles mögliche probiert und dann ging es wieder.
Leider nichts mitgeschrieben, sondern nur in panik google durchsucht.sudo npm cache clean --force sudo -H -u iobroker npm install iobroker.js-controller iob fixprobiert.
Und jetzt hab ich es wieder geschafft das es geht ...
BLE Adapter installiert und danach wieder gelöscht und die Fehler sind weg.
Versteh ich irgendwie nicht ganz.
16er läuft wieder -
@grazer75 sagte in [How-to] Node.js für ioBroker richtig updaten:
weil auch andere Sachen auf dem pi habe?
kann ja nicht hellsehen - dann viel Glück
-
@grazer75 sagte in [How-to] Node.js für ioBroker richtig updaten:
Hab dann alles mögliche probiert und dann ging es wieder.
Leider nichts mitgeschrieben, sondern nur in panik google durchsucht.Das ist schlecht. Also Panik.
Ich würde auf 18 gehen und mir dann die jeweiligen Adapter/Instanzen Stück für Stück anschauen.
-
@thomas-braun 16er läuft wieder, weiß nicht ob es nur ble Adapter installieren und löschen war und deshalb alles wieder geht. Fehler sind alle wieder weg.
-
@grazer75 sagte in [How-to] Node.js für ioBroker richtig updaten:
BLE Adapter installiert und danach wieder gelöscht und die Fehler sind weg.
Du weißt schon, dass gerade der BLE-Adapter neugebaut wird? Geht i.d.R. automatisch.
-
@thomas-braun aber das installieren von ble und deinstallieren hat die Fehler bereinigt irgendwie
Es geht wieder mit 16.x weiß nicht ob ich den Trick auf mit 18.x probieren sollte oder lieber froh sein das ich wieder einen funktionierenden iobroker hab ohne Fehler
-
@grazer75 Hi,
also ich kann es nur nochmals wiederholen ... alle Fehler aus dem ioBroker Log haben NICHTS mit der Node.js Version zu tun!! Da die plötzlich bei node.js 16 weg sind und bei 18 da sind ist aber mal soooowas von unerklärbar!
1.) Javascript "Read-only state "javascript.0.MiHomeAll.lumi.158d0002a3299c.info.rssi" has been written ..." ist ein Fehler in einem deiner Skripte. Ein Objekt mit write:false darf nur mit ack=true beschrieben werden. Dieser Fehler KANN NICHT mit der Nodejs version zu tun haben, tut aber auch erstmal nicht weh
2.) Tuya connect ECONNRESET bedeutet das das Tuya-Gerät die Verbindung resettet/abgelehnt/abgebrochen hat. Kann ebenso NICHTS mit Nodejs zu tun haben
3.) Wifilight "(HF-LPT120) is not a known device type. Skipping this device!" ... die Meldung spricht auch für sich.
4.) firetv "adb executable not found. undefined" sagt das ein executable nicht da ist ...
ALso Wenn da vorher was tat und nach nodejs 18 nicht mehr dann ist das schon eher komisch und seehr unerklärlich. Da solltest Du denke ich mit etwas Zeit mal das Gesamtsysteme aus einem Backup restoren und neu aufsetzen und alles sauber wieder zum Laufen bekommen
