@mickym
Ja Danke für die Erklärung, hab ich gefunden.
NEWS
Latest posts made by ledies
-
RE: ioBroker zerschossen
-
RE: ioBroker zerschossen
@mickym sagte in ioBroker zerschossen:
@ledies Die Sicherung der state und object.jsonl findet automatisch alle paar Stunden statt und die kann man einfach nehmen. Da braucht man keine uralten States oder Objekts aus einer 1 Woche alten Sicherung zu nehmen.
Ja und wo ist die dann zu finden?
ich dachte ja auch mit iobroker restore kann man alle wieder zurückspielen, hat aber nicht funktioniert - siehe oben.. -
RE: ioBroker zerschossen
Du bist aber auch lange wach...
Danke für die Antwort.
del des Adapters Lovelace hatte ich auch gerade noch probiert, halt aber nichts.
Habe dann die /opt/iobroker/iobroker-dataobjects.jsonl, die ja so groß war mit der aus der Vollsicherung überschrieben. War vom 15.01.24 (sichere 2x im Monat komplett) und der ioBroker und alle Adapter laufen wieder. Die Datei aus der Sicherung hat auch nur 35MB.Wenn ich das richtig verstehe, sind die vom Adapter Lovelace eingetragenen Stati einfach zu viel und der Speicher in Java reicht nicht.. Darum auch das Einfrieren.
Dann noch mal Danke und gute Nacht, Gruß Frank
-
ioBroker zerschossen
- Systemdaten kommen unten mit.
Hallo und gute Abend.
Habe heute den Adapter Lovelace installiert und bisschen versucht eine Oberfläche zu bauen. Dabei waren wenig Geräte in der Entität vorhanden, warum ich dummerweise in der Übersicht auf Konfiguration alle Geräte für Lovelace hinzufügen geklickt habe.
Bei der Hälfte des Balkens blieb ioB stehen und danach ging nichts mehr.Die iobroker-data/objects.jsonl ist 484MB groß, keine Ahnung, ob es damit zu tun hat, aber bei
curl -sL https://iobroker.net/fix.sh | bash -
kommt:
Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl <--- Last few GCs ---> [20150:0x55e4968] 13613 ms: Scavenge (reduce) 1023.4 (1034.7) -> 1023.4 (1035.7) MB, 24.2 / 0.0 ms (average mu = 0.763, current mu = 0.574) allocation failure; [20150:0x55e4968] 13653 ms: Mark-sweep (reduce) 1024.1 (1035.7) -> 1024.0 (1036.5) MB, 28.8 / 0.0 ms (+ 89.4 ms in 30 steps since start of marking, biggest step 70.9 ms, walltime since start of marking 248 ms) (average mu = 0.716, current mu = 0.644) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory Aborted
Bei IOB Diag kommt:
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi4 Icon name: computer Operating System: Raspbian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.103-v7l+ Architecture: arm Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : armv7l Userland : armhf Systemuptime and Load: 00:41:59 up 1:27, 2 users, load average: 1.54, 1.50, 1.71 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Sun 2024-01-21 00:41:59 CET Universal time: Sat 2024-01-20 23:41:59 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 7.9G 597M 5.1G 3.0M 2.2G 7.0G Swap: 99M 0B 99M Total: 8.0G 597M 5.2G 7897 M total memory 597 M used memory 1212 M active memory 1348 M inactive memory 5132 M free memory 308 M buffer memory 1859 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 *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * media-mount-Vollsicherung.mount loaded failed failed /media/mount/Vollsicherung * apache2.service loaded failed failed The Apache HTTP Server * argononed.service loaded failed failed Argon One Fan and Button Service * iobroker.service loaded failed failed ioBroker Server * logrotate.service loaded failed failed Rotate log files LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 5 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 110G 21G 85G 20% / devtmpfs devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 3.0M 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 253M 50M 203M 20% /boot tmpfs tmpfs 790M 16K 790M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Jan 20 23:14:56 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:DA:BE:B6 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyS0,115200 console=tty1 root=PARTUUID=555c78ad-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Sat Jan 20 23:14:59 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [Sat Jan 20 23:14:59 2024] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Sat Jan 20 23:15:03 2024] EXT4-fs (sda2): re-mounted. Opts: (null) 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: 11G /var/ 5.6G /var/cache 5.5G /var/cache/apt/archives 5.5G /var/cache/apt 3.9G /var/log Archived and active journals take up 2.9G in the file system. /opt/iobroker/backups: 52M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 950M /opt/iobroker/iobroker-data/ 333M /opt/iobroker/iobroker-data/files 131M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/javascript.admin 55M /opt/iobroker/iobroker-data/files/material The five largest files in iobroker-data are: 462M /opt/iobroker/iobroker-data/objects.jsonl 41M /opt/iobroker/iobroker-data/files/material/static/js/main.c5478f66.js.map 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: *** 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 12.22.12~dfsg-1~deb11u4 600 600 http://mirrordirector.raspbian.org/raspbian bullseye/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! extraneous: @ampproject/remapping@2.2.1 /opt/iobroker/node_modules/@ampproject/remapping npm ERR! extraneous: @babel/code-frame@7.23.5 /opt/iobroker/node_modules/@babel/code-frame npm ERR! extraneous: @babel/compat-data@7.23.5 /opt/iobroker/node_modules/@babel/compat-data npm ERR! extraneous: @babel/core@7.23.7 /opt/iobroker/node_modules/@babel/core npm ERR! extraneous: @babel/generator@7.23.6 /opt/iobroker/node_modules/@babel/generator npm ERR! extraneous: @babel/helper-compilation-targets@7.23.6 /opt/iobroker/node_modules/@babel/helper-compilation-targets npm ERR! extraneous: @babel/helper-environment-visitor@7.22.20 /opt/iobroker/node_modules/@babel/helper-environment-visitor npm ERR! extraneous: @babel/helper-function-name@7.23.0 /opt/iobroker/node_modules/@babel/helper-function-name npm ERR! extraneous: @babel/helper-hoist-variables@7.22.5 /opt/iobroker/node_modules/@babel/helper-hoist-variables npm ERR! extraneous: @babel/helper-module-imports@7.22.15 /opt/iobroker/node_modules/@babel/helper-module-imports npm ERR! extraneous: @babel/helper-module-transforms@7.23.3 /opt/iobroker/node_modules/@babel/helper-module-transforms npm ERR! extraneous: @babel/helper-simple-access@7.22.5 /opt/iobroker/node_modules/@babel/helper-simple-access npm ERR! extraneous: @babel/helper-split-export-declaration@7.22.6 /opt/iobroker/node_modules/@babel/helper-split-export-declaration npm ERR! extraneous: @babel/helper-string-parser@7.23.4 /opt/iobroker/node_modules/@babel/helper-string-parser npm ERR! extraneous: @babel/helper-validator-identifier@7.22.20 /opt/iobroker/node_modules/@babel/helper-validator-identifier npm ERR! extraneous: @babel/helper-validator-option@7.23.5 /opt/iobroker/node_modules/@babel/helper-validator-option npm ERR! extraneous: @babel/helpers@7.23.8 /opt/iobroker/node_modules/@babel/helpers npm ERR! extraneous: @babel/highlight@7.23.4 /opt/iobroker/node_modules/@babel/highlight npm ERR! extraneous: @babel/parser@7.23.6 /opt/iobroker/node_modules/@babel/parser npm ERR! extraneous: @babel/template@7.22.15 /opt/iobroker/node_modules/@babel/template npm ERR! extraneous: @babel/traverse@7.23.7 /opt/iobroker/node_modules/@babel/traverse npm ERR! extraneous: @babel/types@7.23.6 /opt/iobroker/node_modules/@babel/types npm ERR! extraneous: @istanbuljs/load-nyc-config@1.1.0 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config npm ERR! extraneous: @istanbuljs/schema@0.1.3 /opt/iobroker/node_modules/@istanbuljs/schema npm ERR! extraneous: @jridgewell/gen-mapping@0.3.3 /opt/iobroker/node_modules/@jridgewell/gen-mapping npm ERR! extraneous: @jridgewell/resolve-uri@3.1.1 /opt/iobroker/node_modules/@jridgewell/resolve-uri npm ERR! extraneous: @jridgewell/set-array@1.1.2 /opt/iobroker/node_modules/@jridgewell/set-array npm ERR! extraneous: @jridgewell/sourcemap-codec@1.4.15 /opt/iobroker/node_modules/@jridgewell/sourcemap-codec npm ERR! extraneous: @jridgewell/trace-mapping@0.3.22 /opt/iobroker/node_modules/@jridgewell/trace-mapping npm ERR! extraneous: @mapbox/node-pre-gyp@1.0.11 /opt/iobroker/node_modules/@mapbox/node-pre-gyp npm ERR! extraneous: abbrev@1.1.1 /opt/iobroker/node_modules/abbrev npm ERR! extraneous: aggregate-error@3.1.0 /opt/iobroker/node_modules/aggregate-error npm ERR! extraneous: append-transform@2.0.0 /opt/iobroker/node_modules/append-transform npm ERR! extraneous: aproba@2.0.0 /opt/iobroker/node_modules/aproba npm ERR! extraneous: archy@1.0.0 /opt/iobroker/node_modules/archy npm ERR! extraneous: are-we-there-yet@2.0.0 /opt/iobroker/node_modules/are-we-there-yet npm ERR! extraneous: argparse@2.0.1 /opt/iobroker/node_modules/argparse npm ERR! extraneous: browserslist@4.22.2 /opt/iobroker/node_modules/browserslist npm ERR! extraneous: caching-transform@4.0.0 /opt/iobroker/node_modules/caching-transform npm ERR! extraneous: caniuse-lite@1.0.30001579 /opt/iobroker/node_modules/caniuse-lite npm ERR! extraneous: chalk@2.4.2 /opt/iobroker/node_modules/chalk npm ERR! extraneous: clean-stack@2.2.0 /opt/iobroker/node_modules/clean-stack npm ERR! extraneous: color-support@1.1.3 /opt/iobroker/node_modules/color-support npm ERR! extraneous: commander@1.1.1 /opt/iobroker/node_modules/commander npm ERR! extraneous: commondir@1.0.1 /opt/iobroker/node_modules/commondir npm ERR! extraneous: console-control-strings@1.1.0 /opt/iobroker/node_modules/console-control-strings npm ERR! extraneous: convert-source-map@1.9.0 /opt/iobroker/node_modules/convert-source-map npm ERR! extraneous: default-require-extensions@3.0.1 /opt/iobroker/node_modules/default-require-extensions npm ERR! extraneous: delegates@1.0.0 /opt/iobroker/node_modules/delegates npm ERR! extraneous: detect-libc@2.0.2 /opt/iobroker/node_modules/detect-libc npm ERR! extraneous: electron-to-chromium@1.4.640 /opt/iobroker/node_modules/electron-to-chromium npm ERR! extraneous: es6-error@4.1.1 /opt/iobroker/node_modules/es6-error npm ERR! extraneous: escape-string-regexp@1.0.5 /opt/iobroker/node_modules/escape-string-regexp npm ERR! extraneous: esprima@4.0.1 /opt/iobroker/node_modules/esprima npm ERR! extraneous: find-cache-dir@3.3.2 /opt/iobroker/node_modules/find-cache-dir npm ERR! extraneous: foreground-child@2.0.0 /opt/iobroker/node_modules/foreground-child npm ERR! extraneous: fromentries@1.3.2 /opt/iobroker/node_modules/fromentries npm ERR! extraneous: gauge@3.0.2 /opt/iobroker/node_modules/gauge npm ERR! extraneous: gensync@1.0.0-beta.2 /opt/iobroker/node_modules/gensync npm ERR! extraneous: get-package-type@0.1.0 /opt/iobroker/node_modules/get-package-type npm ERR! extraneous: globals@11.12.0 /opt/iobroker/node_modules/globals npm ERR! extraneous: has-flag@3.0.0 /opt/iobroker/node_modules/has-flag npm ERR! extraneous: has-unicode@2.0.1 /opt/iobroker/node_modules/has-unicode npm ERR! extraneous: hasha@5.2.2 /opt/iobroker/node_modules/hasha npm ERR! extraneous: html-escaper@2.0.2 /opt/iobroker/node_modules/html-escaper npm ERR! extraneous: imurmurhash@0.1.4 /opt/iobroker/node_modules/imurmurhash npm ERR! extraneous: indent-string@4.0.0 /opt/iobroker/node_modules/indent-string npm ERR! missing: iobroker.lovelace@3.0.1, required by iobroker.inst@2.0.3 npm ERR! extraneous: is-windows@1.0.2 /opt/iobroker/node_modules/is-windows npm ERR! extraneous: istanbul-lib-coverage@3.2.2 /opt/iobroker/node_modules/istanbul-lib-coverage npm ERR! extraneous: istanbul-lib-hook@3.0.0 /opt/iobroker/node_modules/istanbul-lib-hook npm ERR! extraneous: istanbul-lib-instrument@4.0.3 /opt/iobroker/node_modules/istanbul-lib-instrument npm ERR! extraneous: istanbul-lib-processinfo@2.0.3 /opt/iobroker/node_modules/istanbul-lib-processinfo npm ERR! extraneous: istanbul-lib-report@3.0.1 /opt/iobroker/node_modules/istanbul-lib-report npm ERR! extraneous: istanbul-lib-source-maps@4.0.1 /opt/iobroker/node_modules/istanbul-lib-source-maps npm ERR! extraneous: istanbul-reports@3.1.6 /opt/iobroker/node_modules/istanbul-reports npm ERR! extraneous: js-tokens@4.0.0 /opt/iobroker/node_modules/js-tokens npm ERR! extraneous: js-yaml@4.1.0 /opt/iobroker/node_modules/js-yaml npm ERR! extraneous: jsesc@2.5.2 /opt/iobroker/node_modules/jsesc npm ERR! extraneous: jstimezonedetect@1.0.7 /opt/iobroker/node_modules/jstimezonedetect npm ERR! extraneous: keypress@0.1.0 /opt/iobroker/node_modules/keypress npm ERR! extraneous: lodash.flattendeep@4.4.0 /opt/iobroker/node_modules/lodash.flattendeep npm ERR! extraneous: node-preload@0.2.1 /opt/iobroker/node_modules/node-preload npm ERR! extraneous: node-releases@2.0.14 /opt/iobroker/node_modules/node-releases npm ERR! extraneous: nodejieba@2.5.2 /opt/iobroker/node_modules/nodejieba npm ERR! extraneous: nopt@5.0.0 /opt/iobroker/node_modules/nopt npm ERR! extraneous: npmlog@5.0.1 /opt/iobroker/node_modules/npmlog npm ERR! extraneous: nyc@15.1.0 /opt/iobroker/node_modules/nyc npm ERR! extraneous: package-hash@4.0.0 /opt/iobroker/node_modules/package-hash npm ERR! extraneous: pinyin@2.11.2 /opt/iobroker/node_modules/pinyin npm ERR! extraneous: pkg-dir@4.2.0 /opt/iobroker/node_modules/pkg-dir npm ERR! extraneous: process-on-spawn@1.0.0 /opt/iobroker/node_modules/process-on-spawn npm ERR! extraneous: release-zalgo@1.0.0 /opt/iobroker/node_modules/release-zalgo npm ERR! extraneous: resolve-from@5.0.0 /opt/iobroker/node_modules/resolve-from npm ERR! extraneous: rimraf@3.0.2 /opt/iobroker/node_modules/rimraf npm ERR! extraneous: spawn-wrap@2.0.0 /opt/iobroker/node_modules/spawn-wrap npm ERR! extraneous: sprintf-js@1.0.3 /opt/iobroker/node_modules/sprintf-js npm ERR! extraneous: supports-color@5.5.0 /opt/iobroker/node_modules/supports-color npm ERR! extraneous: test-exclude@6.0.0 /opt/iobroker/node_modules/test-exclude npm ERR! extraneous: to-fast-properties@2.0.0 /opt/iobroker/node_modules/to-fast-properties npm ERR! extraneous: translit-rus-eng@1.0.8 /opt/iobroker/node_modules/translit-rus-eng npm ERR! extraneous: type-fest@0.8.1 /opt/iobroker/node_modules/type-fest npm ERR! extraneous: typedarray-to-buffer@3.1.5 /opt/iobroker/node_modules/typedarray-to-buffer npm ERR! extraneous: update-browserslist-db@1.0.13 /opt/iobroker/node_modules/update-browserslist-db npm ERR! extraneous: wide-align@1.1.5 /opt/iobroker/node_modules/wide-align npm ERR! extraneous: write-file-atomic@3.0.3 /opt/iobroker/node_modules/write-file-atomic npm ERR! extraneous: convert-source-map@2.0.0 /opt/iobroker/node_modules/@babel/core/node_modules/convert-source-map npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/@babel/core/node_modules/debug npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/@babel/core/node_modules/ms npm ERR! extraneous: semver@6.3.1 /opt/iobroker/node_modules/@babel/core/node_modules/semver npm ERR! extraneous: lru-cache@5.1.1 /opt/iobroker/node_modules/@babel/helper-compilation-targets/node_modules/lru-cache npm ERR! extraneous: semver@6.3.1 /opt/iobroker/node_modules/@babel/helper-compilation-targets/node_modules/semver npm ERR! extraneous: yallist@3.1.1 /opt/iobroker/node_modules/@babel/helper-compilation-targets/node_modules/yallist npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/@babel/traverse/node_modules/debug npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/@babel/traverse/node_modules/ms npm ERR! extraneous: argparse@1.0.10 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/argparse npm ERR! extraneous: camelcase@5.3.1 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/camelcase npm ERR! extraneous: find-up@4.1.0 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/find-up npm ERR! extraneous: js-yaml@3.14.1 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml npm ERR! extraneous: path-exists@4.0.0 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/path-exists npm ERR! extraneous: semver@7.5.4 /opt/iobroker/node_modules/@mapbox/node-pre-gyp/node_modules/semver npm ERR! extraneous: readable-stream@3.6.2 /opt/iobroker/node_modules/are-we-there-yet/node_modules/readable-stream npm ERR! extraneous: ansi-styles@3.2.1 /opt/iobroker/node_modules/chalk/node_modules/ansi-styles npm ERR! extraneous: strip-bom@4.0.0 /opt/iobroker/node_modules/default-require-extensions/node_modules/strip-bom npm ERR! extraneous: ansi-regex@5.0.1 /opt/iobroker/node_modules/gauge/node_modules/ansi-regex npm ERR! extraneous: is-fullwidth-code-point@3.0.0 /opt/iobroker/node_modules/gauge/node_modules/is-fullwidth-code-point npm ERR! extraneous: string-width@4.2.3 /opt/iobroker/node_modules/gauge/node_modules/string-width npm ERR! extraneous: strip-ansi@6.0.1 /opt/iobroker/node_modules/gauge/node_modules/strip-ansi npm ERR! missing: simple-ssh@^1.1.1, required by iobroker.javascript@7.1.6 npm ERR! extraneous: semver@6.3.1 /opt/iobroker/node_modules/istanbul-lib-instrument/node_modules/semver npm ERR! extraneous: p-map@3.0.0 /opt/iobroker/node_modules/istanbul-lib-processinfo/node_modules/p-map npm ERR! extraneous: uuid@8.3.2 /opt/iobroker/node_modules/istanbul-lib-processinfo/node_modules/uuid npm ERR! extraneous: has-flag@4.0.0 /opt/iobroker/node_modules/istanbul-lib-report/node_modules/has-flag npm ERR! extraneous: make-dir@4.0.0 /opt/iobroker/node_modules/istanbul-lib-report/node_modules/make-dir npm ERR! extraneous: semver@7.5.4 /opt/iobroker/node_modules/istanbul-lib-report/node_modules/semver npm ERR! extraneous: supports-color@7.2.0 /opt/iobroker/node_modules/istanbul-lib-report/node_modules/supports-color npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/istanbul-lib-source-maps/node_modules/debug npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/istanbul-lib-source-maps/node_modules/ms npm ERR! extraneous: node-addon-api@3.2.1 /opt/iobroker/node_modules/nodejieba/node_modules/node-addon-api npm ERR! extraneous: ansi-regex@5.0.1 /opt/iobroker/node_modules/nyc/node_modules/ansi-regex npm ERR! extraneous: camelcase@5.3.1 /opt/iobroker/node_modules/nyc/node_modules/camelcase npm ERR! extraneous: cliui@6.0.0 /opt/iobroker/node_modules/nyc/node_modules/cliui npm ERR! extraneous: find-up@4.1.0 /opt/iobroker/node_modules/nyc/node_modules/find-up npm ERR! extraneous: get-caller-file@2.0.5 /opt/iobroker/node_modules/nyc/node_modules/get-caller-file npm ERR! extraneous: is-fullwidth-code-point@3.0.0 /opt/iobroker/node_modules/nyc/node_modules/is-fullwidth-code-point npm ERR! extraneous: p-map@3.0.0 /opt/iobroker/node_modules/nyc/node_modules/p-map npm ERR! extraneous: path-exists@4.0.0 /opt/iobroker/node_modules/nyc/node_modules/path-exists npm ERR! extraneous: require-main-filename@2.0.0 /opt/iobroker/node_modules/nyc/node_modules/require-main-filename npm ERR! extraneous: string-width@4.2.3 /opt/iobroker/node_modules/nyc/node_modules/string-width npm ERR! extraneous: strip-ansi@6.0.1 /opt/iobroker/node_modules/nyc/node_modules/strip-ansi npm ERR! extraneous: which-module@2.0.1 /opt/iobroker/node_modules/nyc/node_modules/which-module npm ERR! extraneous: wrap-ansi@6.2.0 /opt/iobroker/node_modules/nyc/node_modules/wrap-ansi npm ERR! extraneous: y18n@4.0.3 /opt/iobroker/node_modules/nyc/node_modules/y18n npm ERR! extraneous: yargs-parser@18.1.3 /opt/iobroker/node_modules/nyc/node_modules/yargs-parser npm ERR! extraneous: yargs@15.4.1 /opt/iobroker/node_modules/nyc/node_modules/yargs npm ERR! extraneous: find-up@4.1.0 /opt/iobroker/node_modules/pkg-dir/node_modules/find-up npm ERR! extraneous: path-exists@4.0.0 /opt/iobroker/node_modules/pkg-dir/node_modules/path-exists npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-01-20T23_42_08_018Z-debug-0.log *** ioBroker-Installation *** ioBroker Status <--- Last few GCs ---> [11474:0x505f8e0] 24880 ms: Scavenge (reduce) 1022.6 (1034.4) -> 1022.6 (1035.4) MB, 27.5 / 0.0 ms (average mu = 0.763, current mu = 0.639) allocation failure; [11474:0x505f8e0] 24942 ms: Mark-sweep (reduce) 1023.6 (1035.4) -> 1023.2 (1036.2) MB, 31.9 / 0.0 ms (+ 90.3 ms in 44 steps since start of marking, biggest step 12.8 ms, walltime since start of marking 196 ms) (average mu = 0.689, current mu = 0.553) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iobroker: line 12: 11472 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: 7.1.6 npm ERR! code ELSPROBLEMS npm ERR! extraneous: @ampproject/remapping@2.2.1 /opt/iobroker/node_modules/@ampproject/remapping npm ERR! extraneous: @babel/code-frame@7.23.5 /opt/iobroker/node_modules/@babel/code-frame npm ERR! extraneous: @babel/compat-data@7.23.5 /opt/iobroker/node_modules/@babel/compat-data npm ERR! extraneous: @babel/core@7.23.7 /opt/iobroker/node_modules/@babel/core npm ERR! extraneous: @babel/generator@7.23.6 /opt/iobroker/node_modules/@babel/generator npm ERR! extraneous: @babel/helper-compilation-targets@7.23.6 /opt/iobroker/node_modules/@babel/helper-compilation-targets npm ERR! extraneous: @babel/helper-environment-visitor@7.22.20 /opt/iobroker/node_modules/@babel/helper-environment-visitor npm ERR! extraneous: @babel/helper-function-name@7.23.0 /opt/iobroker/node_modules/@babel/helper-function-name npm ERR! extraneous: @babel/helper-hoist-variables@7.22.5 /opt/iobroker/node_modules/@babel/helper-hoist-variables npm ERR! extraneous: @babel/helper-module-imports@7.22.15 /opt/iobroker/node_modules/@babel/helper-module-imports npm ERR! extraneous: @babel/helper-module-transforms@7.23.3 /opt/iobroker/node_modules/@babel/helper-module-transforms npm ERR! extraneous: @babel/helper-simple-access@7.22.5 /opt/iobroker/node_modules/@babel/helper-simple-access npm ERR! extraneous: @babel/helper-split-export-declaration@7.22.6 /opt/iobroker/node_modules/@babel/helper-split-export-declaration npm ERR! extraneous: @babel/helper-string-parser@7.23.4 /opt/iobroker/node_modules/@babel/helper-string-parser npm ERR! extraneous: @babel/helper-validator-identifier@7.22.20 /opt/iobroker/node_modules/@babel/helper-validator-identifier npm ERR! extraneous: @babel/helper-validator-option@7.23.5 /opt/iobroker/node_modules/@babel/helper-validator-option npm ERR! extraneous: @babel/helpers@7.23.8 /opt/iobroker/node_modules/@babel/helpers npm ERR! extraneous: @babel/highlight@7.23.4 /opt/iobroker/node_modules/@babel/highlight npm ERR! extraneous: @babel/parser@7.23.6 /opt/iobroker/node_modules/@babel/parser npm ERR! extraneous: @babel/template@7.22.15 /opt/iobroker/node_modules/@babel/template npm ERR! extraneous: @babel/traverse@7.23.7 /opt/iobroker/node_modules/@babel/traverse npm ERR! extraneous: @babel/types@7.23.6 /opt/iobroker/node_modules/@babel/types npm ERR! extraneous: @istanbuljs/load-nyc-config@1.1.0 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config npm ERR! extraneous: @istanbuljs/schema@0.1.3 /opt/iobroker/node_modules/@istanbuljs/schema npm ERR! extraneous: @jridgewell/gen-mapping@0.3.3 /opt/iobroker/node_modules/@jridgewell/gen-mapping npm ERR! extraneous: @jridgewell/resolve-uri@3.1.1 /opt/iobroker/node_modules/@jridgewell/resolve-uri npm ERR! extraneous: @jridgewell/set-array@1.1.2 /opt/iobroker/node_modules/@jridgewell/set-array npm ERR! extraneous: @jridgewell/sourcemap-codec@1.4.15 /opt/iobroker/node_modules/@jridgewell/sourcemap-codec npm ERR! extraneous: @jridgewell/trace-mapping@0.3.22 /opt/iobroker/node_modules/@jridgewell/trace-mapping npm ERR! extraneous: @mapbox/node-pre-gyp@1.0.11 /opt/iobroker/node_modules/@mapbox/node-pre-gyp npm ERR! extraneous: abbrev@1.1.1 /opt/iobroker/node_modules/abbrev npm ERR! extraneous: aggregate-error@3.1.0 /opt/iobroker/node_modules/aggregate-error npm ERR! extraneous: append-transform@2.0.0 /opt/iobroker/node_modules/append-transform npm ERR! extraneous: aproba@2.0.0 /opt/iobroker/node_modules/aproba npm ERR! extraneous: archy@1.0.0 /opt/iobroker/node_modules/archy npm ERR! extraneous: are-we-there-yet@2.0.0 /opt/iobroker/node_modules/are-we-there-yet npm ERR! extraneous: argparse@2.0.1 /opt/iobroker/node_modules/argparse npm ERR! extraneous: browserslist@4.22.2 /opt/iobroker/node_modules/browserslist npm ERR! extraneous: caching-transform@4.0.0 /opt/iobroker/node_modules/caching-transform npm ERR! extraneous: caniuse-lite@1.0.30001579 /opt/iobroker/node_modules/caniuse-lite npm ERR! extraneous: chalk@2.4.2 /opt/iobroker/node_modules/chalk npm ERR! extraneous: clean-stack@2.2.0 /opt/iobroker/node_modules/clean-stack npm ERR! extraneous: color-support@1.1.3 /opt/iobroker/node_modules/color-support npm ERR! extraneous: commander@1.1.1 /opt/iobroker/node_modules/commander npm ERR! extraneous: commondir@1.0.1 /opt/iobroker/node_modules/commondir npm ERR! extraneous: console-control-strings@1.1.0 /opt/iobroker/node_modules/console-control-strings npm ERR! extraneous: convert-source-map@1.9.0 /opt/iobroker/node_modules/convert-source-map npm ERR! extraneous: default-require-extensions@3.0.1 /opt/iobroker/node_modules/default-require-extensions npm ERR! extraneous: delegates@1.0.0 /opt/iobroker/node_modules/delegates npm ERR! extraneous: detect-libc@2.0.2 /opt/iobroker/node_modules/detect-libc npm ERR! extraneous: electron-to-chromium@1.4.640 /opt/iobroker/node_modules/electron-to-chromium npm ERR! extraneous: es6-error@4.1.1 /opt/iobroker/node_modules/es6-error npm ERR! extraneous: escape-string-regexp@1.0.5 /opt/iobroker/node_modules/escape-string-regexp npm ERR! extraneous: esprima@4.0.1 /opt/iobroker/node_modules/esprima npm ERR! extraneous: find-cache-dir@3.3.2 /opt/iobroker/node_modules/find-cache-dir npm ERR! extraneous: foreground-child@2.0.0 /opt/iobroker/node_modules/foreground-child npm ERR! extraneous: fromentries@1.3.2 /opt/iobroker/node_modules/fromentries npm ERR! extraneous: gauge@3.0.2 /opt/iobroker/node_modules/gauge npm ERR! extraneous: gensync@1.0.0-beta.2 /opt/iobroker/node_modules/gensync npm ERR! extraneous: get-package-type@0.1.0 /opt/iobroker/node_modules/get-package-type npm ERR! extraneous: globals@11.12.0 /opt/iobroker/node_modules/globals npm ERR! extraneous: has-flag@3.0.0 /opt/iobroker/node_modules/has-flag npm ERR! extraneous: has-unicode@2.0.1 /opt/iobroker/node_modules/has-unicode npm ERR! extraneous: hasha@5.2.2 /opt/iobroker/node_modules/hasha npm ERR! extraneous: html-escaper@2.0.2 /opt/iobroker/node_modules/html-escaper npm ERR! extraneous: imurmurhash@0.1.4 /opt/iobroker/node_modules/imurmurhash npm ERR! extraneous: indent-string@4.0.0 /opt/iobroker/node_modules/indent-string npm ERR! missing: iobroker.lovelace@3.0.1, required by iobroker.inst@2.0.3 npm ERR! extraneous: is-windows@1.0.2 /opt/iobroker/node_modules/is-windows npm ERR! extraneous: istanbul-lib-coverage@3.2.2 /opt/iobroker/node_modules/istanbul-lib-coverage npm ERR! extraneous: istanbul-lib-hook@3.0.0 /opt/iobroker/node_modules/istanbul-lib-hook npm ERR! extraneous: istanbul-lib-instrument@4.0.3 /opt/iobroker/node_modules/istanbul-lib-instrument npm ERR! extraneous: istanbul-lib-processinfo@2.0.3 /opt/iobroker/node_modules/istanbul-lib-processinfo npm ERR! extraneous: istanbul-lib-report@3.0.1 /opt/iobroker/node_modules/istanbul-lib-report npm ERR! extraneous: istanbul-lib-source-maps@4.0.1 /opt/iobroker/node_modules/istanbul-lib-source-maps npm ERR! extraneous: istanbul-reports@3.1.6 /opt/iobroker/node_modules/istanbul-reports npm ERR! extraneous: js-tokens@4.0.0 /opt/iobroker/node_modules/js-tokens npm ERR! extraneous: js-yaml@4.1.0 /opt/iobroker/node_modules/js-yaml npm ERR! extraneous: jsesc@2.5.2 /opt/iobroker/node_modules/jsesc npm ERR! extraneous: jstimezonedetect@1.0.7 /opt/iobroker/node_modules/jstimezonedetect npm ERR! extraneous: keypress@0.1.0 /opt/iobroker/node_modules/keypress npm ERR! extraneous: lodash.flattendeep@4.4.0 /opt/iobroker/node_modules/lodash.flattendeep npm ERR! extraneous: node-preload@0.2.1 /opt/iobroker/node_modules/node-preload npm ERR! extraneous: node-releases@2.0.14 /opt/iobroker/node_modules/node-releases npm ERR! extraneous: nodejieba@2.5.2 /opt/iobroker/node_modules/nodejieba npm ERR! extraneous: nopt@5.0.0 /opt/iobroker/node_modules/nopt npm ERR! extraneous: npmlog@5.0.1 /opt/iobroker/node_modules/npmlog npm ERR! extraneous: nyc@15.1.0 /opt/iobroker/node_modules/nyc npm ERR! extraneous: package-hash@4.0.0 /opt/iobroker/node_modules/package-hash npm ERR! extraneous: pinyin@2.11.2 /opt/iobroker/node_modules/pinyin npm ERR! extraneous: pkg-dir@4.2.0 /opt/iobroker/node_modules/pkg-dir npm ERR! extraneous: process-on-spawn@1.0.0 /opt/iobroker/node_modules/process-on-spawn npm ERR! extraneous: release-zalgo@1.0.0 /opt/iobroker/node_modules/release-zalgo npm ERR! extraneous: resolve-from@5.0.0 /opt/iobroker/node_modules/resolve-from npm ERR! extraneous: rimraf@3.0.2 /opt/iobroker/node_modules/rimraf npm ERR! extraneous: spawn-wrap@2.0.0 /opt/iobroker/node_modules/spawn-wrap npm ERR! extraneous: sprintf-js@1.0.3 /opt/iobroker/node_modules/sprintf-js npm ERR! extraneous: supports-color@5.5.0 /opt/iobroker/node_modules/supports-color npm ERR! extraneous: test-exclude@6.0.0 /opt/iobroker/node_modules/test-exclude npm ERR! extraneous: to-fast-properties@2.0.0 /opt/iobroker/node_modules/to-fast-properties npm ERR! extraneous: translit-rus-eng@1.0.8 /opt/iobroker/node_modules/translit-rus-eng npm ERR! extraneous: type-fest@0.8.1 /opt/iobroker/node_modules/type-fest npm ERR! extraneous: typedarray-to-buffer@3.1.5 /opt/iobroker/node_modules/typedarray-to-buffer npm ERR! extraneous: update-browserslist-db@1.0.13 /opt/iobroker/node_modules/update-browserslist-db npm ERR! extraneous: wide-align@1.1.5 /opt/iobroker/node_modules/wide-align npm ERR! extraneous: write-file-atomic@3.0.3 /opt/iobroker/node_modules/write-file-atomic npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-01-20T23_42_48_786Z-debug-0.log Adapters from github: 0 Adapter State <--- Last few GCs ---> [11812:0x566c910] 24762 ms: Mark-sweep (reduce) 1023.2 (1039.2) -> 1022.9 (1035.9) MB, 57.5 / 0.0 ms (+ 82.4 ms in 40 steps since start of marking, biggest step 23.7 ms, walltime since start of marking 162 ms) (average mu = 0.696, current mu = 0.438) [11812:0x566c910] 25003 ms: Mark-sweep (reduce) 1024.1 (1035.9) -> 1023.8 (1036.9) MB, 134.4 / 0.0 ms (+ 22.1 ms in 13 steps since start of marking, biggest step 20.2 ms, walltime since start of marking 163 ms) (average mu = 0.569, current mu = 0.351) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 11811 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Enabled adapters with bindings <--- Last few GCs ---> [11990:0x609a910] 24801 ms: Scavenge (reduce) 1022.6 (1034.4) -> 1022.6 (1035.4) MB, 33.3 / 0.0 ms (average mu = 0.749, current mu = 0.508) allocation failure; [11990:0x609a910] 24867 ms: Mark-sweep (reduce) 1023.6 (1035.4) -> 1023.2 (1036.2) MB, 53.9 / 0.0 ms (+ 174.3 ms in 44 steps since start of marking, biggest step 27.8 ms, walltime since start of marking 341 ms) (average mu = 0.623, current mu = 0.435) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 11989 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" ioBroker-Repositories <--- Last few GCs ---> [12169:0x4d19980] 24868 ms: Mark-sweep (reduce) 1023.3 (1039.2) -> 1022.9 (1035.9) MB, 60.8 / 0.0 ms (+ 98.0 ms in 40 steps since start of marking, biggest step 44.3 ms, walltime since start of marking 182 ms) (average mu = 0.644, current mu = 0.387) [12169:0x4d19980] 25089 ms: Mark-sweep (reduce) 1024.2 (1035.9) -> 1023.9 (1036.9) MB, 91.0 / 0.0 ms (+ 44.0 ms in 13 steps since start of marking, biggest step 16.5 ms, walltime since start of marking 161 ms) (average mu = 0.557, current mu = 0.389) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 12168 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Installed ioBroker-Instances <--- Last few GCs ---> [12360:0x5091980] 24957 ms: Mark-sweep (reduce) 1023.3 (1035.2) -> 1022.9 (1035.9) MB, 184.2 / 0.0 ms (+ 101.7 ms in 42 steps since start of marking, biggest step 22.1 ms, walltime since start of marking 355 ms) (average mu = 0.633, current mu = 0.365[12360:0x5091980] 25105 ms: Mark-sweep (reduce) 1024.1 (1035.9) -> 1023.8 (1036.9) MB, 93.3 / 0.0 ms (+ 44.0 ms in 13 steps since start of marking, biggest step 19.8 ms, walltime since start of marking 146 ms) (average mu = 0.517, current mu = 0.075) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 12359 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye-proposed-updates InRelease Hit:2 http://mirrordirector.raspbian.org/raspbian bullseye InRelease Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:6 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable 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 0.0.0.0:80 0.0.0.0:* LISTEN 0 14401 643/nginx: master p tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 9156 540/sshd: /usr/sbin tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 2455589 23565/cupsd tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 0 15649 944/master tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 118 14371 547/mosquitto tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 14948 1156/smbd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 14949 1156/smbd tcp6 0 0 :::8080 :::* LISTEN 115 15058 451/java tcp6 0 0 :::80 :::* LISTEN 0 14402 643/nginx: master p tcp6 0 0 :::22 :::* LISTEN 0 9158 540/sshd: /usr/sbin tcp6 0 0 ::1:631 :::* LISTEN 0 2455588 23565/cupsd tcp6 0 0 :::25 :::* LISTEN 0 15650 944/master tcp6 0 0 :::8443 :::* LISTEN 115 17863 451/java tcp6 0 0 :::1883 :::* LISTEN 118 14372 547/mosquitto tcp6 0 0 :::445 :::* LISTEN 0 14946 1156/smbd tcp6 0 0 127.0.0.1:8101 :::* LISTEN 115 17161 451/java tcp6 0 0 192.168.2.52:9126 :::* LISTEN 115 20401 451/java tcp6 0 0 127.0.0.1:37163 :::* LISTEN 115 15936 451/java tcp6 0 0 :::139 :::* LISTEN 0 14947 1156/smbd tcp6 0 0 :::5007 :::* LISTEN 115 15188 451/java udp 0 0 0.0.0.0:47627 0.0.0.0:* 108 12942 361/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14526 411/dhcpcd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 2455598 23572/cups-browsed udp 0 0 192.168.2.255:137 0.0.0.0:* 0 14882 444/nmbd udp 0 0 192.168.2.52:137 0.0.0.0:* 0 14881 444/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 0 14472 444/nmbd udp 0 0 192.168.2.255:138 0.0.0.0:* 0 14884 444/nmbd udp 0 0 192.168.2.52:138 0.0.0.0:* 0 14883 444/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 0 14473 444/nmbd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12940 361/avahi-daemon: r udp6 0 0 192.168.2.52:45040 :::* 115 15234 451/java udp6 0 0 :::546 :::* 0 14248 411/dhcpcd udp6 0 0 :::5683 :::* 115 21477 451/java udp6 0 0 :::6767 :::* 115 18575 451/java udp6 0 0 :::44765 :::* 115 22428 451/java udp6 0 0 :::5353 :::* 115 15103 451/java udp6 0 0 :::5353 :::* 115 15099 451/java udp6 0 0 :::5353 :::* 108 12941 361/avahi-daemon: r udp6 0 0 :::1900 :::* 115 15233 451/java udp6 0 0 :::55180 :::* 108 12943 361/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-01-21 00:22:30.555 - info: host.raspberrypi4 ip addresses: 192.168.2.52 2003:e8:8723:e000:9058:567:6623:3aec fe80::1a2e:6a3c:c218:5b1f 2024-01-21 00:22:48.710 - info: host.raspberrypi4 iobroker.js-controller version 5.0.17 js-controller starting 2024-01-21 00:22:48.718 - info: host.raspberrypi4 Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-21 00:22:48.719 - info: host.raspberrypi4 hostname: raspberrypi4, node: v18.19.0 2024-01-21 00:22:48.721 - info: host.raspberrypi4 ip addresses: 192.168.2.52 2003:e8:8723:e000:9058:567:6623:3aec fe80::1a2e:6a3c:c218:5b1f 2024-01-21 00:23:06.687 - info: host.raspberrypi4 iobroker.js-controller version 5.0.17 js-controller starting 2024-01-21 00:23:06.696 - info: host.raspberrypi4 Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-21 00:23:06.698 - info: host.raspberrypi4 hostname: raspberrypi4, node: v18.19.0 2024-01-21 00:23:06.700 - info: host.raspberrypi4 ip addresses: 192.168.2.52 2003:e8:8723:e000:9058:567:6623:3aec fe80::1a2e:6a3c:c218:5b1f 2024-01-21 00:23:24.714 - info: host.raspberrypi4 iobroker.js-controller version 5.0.17 js-controller starting 2024-01-21 00:23:24.724 - info: host.raspberrypi4 Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-21 00:23:24.725 - info: host.raspberrypi4 hostname: raspberrypi4, node: v18.19.0 2024-01-21 00:23:24.727 - info: host.raspberrypi4 ip addresses: 192.168.2.52 2003:e8:8723:e000:9058:567:6623:3aec fe80::1a2e:6a3c:c218:5b1f 2024-01-21 00:23:42.769 - info: host.raspberrypi4 iobroker.js-controller version 5.0.17 js-controller starting 2024-01-21 00:23:42.776 - info: host.raspberrypi4 Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-21 00:23:42.777 - info: host.raspberrypi4 hostname: raspberrypi4, node: v18.19.0 2024-01-21 00:23:42.779 - info: host.raspberrypi4 ip addresses: 192.168.2.52 2003:e8:8723:e000:9058:567:6623:3aec fe80::1a2e:6a3c:c218:5b1f 2024-01-21 00:24:01.087 - info: host.raspberrypi4 iobroker.js-controller version 5.0.17 js-controller starting 2024-01-21 00:24:01.096 - info: host.raspberrypi4 Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-21 00:24:01.098 - info: host.raspberrypi4 hostname: raspberrypi4, node: v18.19.0 2024-01-21 00:24:01.099 - info: host.raspberrypi4 ip addresses: 192.168.2.52 2003:e8:8723:e000:9058:567:6623:3aec fe80::1a2e:6a3c:c218:5b1f 2024-01-21 00:24:03.049 - info: host.raspberrypi4 received SIGTERM 2024-01-21 00:24:03.057 - info: host.raspberrypi4 terminated. Could not reset alive status for instances 2024-01-21 00:34:17.565 - warn: vis.0 (6532) no connection to objects DB. Terminating 2024-01-21 00:34:17.571 - info: vis.0 (6532) Terminated (NO_ERROR): Without reason
============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
Copy text starting here:
======================= SUMMARY ======================= v.2023-10-10 Static hostname: raspberrypi4 Icon name: computer Operating System: Raspbian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.103-v7l+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 <--- Last few GCs ---> [13816:0x5878980] 25178 ms: Scavenge (reduce) 1022.6 (1034.4) -> 1022.6 (1035.4) MB, 25.2 / 0.0 ms (average mu = 0.796, current mu = 0.626) allocation failure; [13816:0x5878980] 25233 ms: Mark-sweep (reduce) 1023.6 (1035.4) -> 1023.2 (1036.2) MB, 30.9 / 0.0 ms (+ 90.6 ms in 44 steps since start of marking, biggest step 33.8 ms, walltime since start of marking 194 ms) (average mu = 0.722, current mu = 0.551) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 13815 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.9G 605M 5.1G 3.0M 2.2G 7.0G Swap: 99M 0B 99M Total: 8.0G 605M 5.2G <--- Last few GCs ---> [14054:0x5be1910] 24976 ms: Mark-sweep (reduce) 1023.1 (1037.2) -> 1023.1 (1035.9) MB, 71.4 / 0.0 ms (+ 79.3 ms in 29 steps since start of marking, biggest step 16.0 ms, walltime since start of marking 168 ms) (average mu = 0.612, current mu = 0.402) [14054:0x5be1910] 25174 ms: Mark-sweep (reduce) 1024.2 (1035.9) -> 1024.0 (1036.9) MB, 64.7 / 0.0 ms (+ 75.6 ms in 2 steps since start of marking, biggest step 39.6 ms, walltime since start of marking 142 ms) (average mu = 0.493, current mu = 0.294) a <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 14053 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Active iob-Instances: 0 <--- Last few GCs ---> [14231:0x5cf7980] 24511 ms: Scavenge 1020.6 (1034.4) -> 1020.6 (1039.4) MB, 19.7 / 0.0 ms (average mu = 0.805, current mu = 0.632) allocation failure; [14231:0x5cf7980] 24709 ms: Mark-sweep (reduce) 1023.3 (1039.4) -> 1022.9 (1036.2) MB, 52.9 / 0.0 ms (+ 98.4 ms in 40 steps since start of marking, biggest step 18.2 ms, walltime since start of marking 175 ms) (average mu = 0.687, current mu = 0.411) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 12: 14230 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" ioBroker Core: js-controller 5.0.17 admin 6.12.0 <--- Last few GCs ---> [14477:0x617c8e0] 25080 ms: Mark-sweep (reduce) 1023.4 (1035.2) -> 1022.9 (1035.9) MB, 226.7 / 0.0 ms (+ 82.3 ms in 42 steps since start of marking, biggest step 24.9 ms, walltime since start of marking 408 ms) (average mu = 0.589, current mu = 0.385)[14477:0x617c8e0] 25248 ms: Mark-sweep (reduce) 1024.2 (1035.9) -> 1023.8 (1036.9) MB, 109.9 / 0.0 ms (+ 45.8 ms in 13 steps since start of marking, biggest step 15.6 ms, walltime since start of marking 165 ms) (average mu = 0.471, current mu = 0.071) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iobroker: line 12: 14476 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" ioBroker Status: Status admin and web instance: <--- Last few GCs ---> [14652:0x437f910] 24769 ms: Scavenge (reduce) 1022.6 (1034.4) -> 1022.6 (1035.4) MB, 26.5 / 0.0 ms (average mu = 0.746, current mu = 0.539) allocation failure; [14652:0x437f910] 24830 ms: Mark-sweep (reduce) 1023.6 (1035.4) -> 1023.2 (1036.2) MB, 32.2 / 0.0 ms (+ 90.6 ms in 44 steps since start of marking, biggest step 18.3 ms, walltime since start of marking 200 ms) (average mu = 0.679, current mu = 0.553) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iobroker: line 12: 14651 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Objects: 0 States: 0 Size of iob-Database: 462M /opt/iobroker/iobroker-data/objects.jsonl 8.6M /opt/iobroker/iobroker-data/objects.json.migrated 8.6M /opt/iobroker/iobroker-data/objects.json.bak.migrated 0 /opt/iobroker/iobroker-data/objects.json.broken 3.1M /opt/iobroker/iobroker-data/states.jsonl 2.0M /opt/iobroker/iobroker-data/states.json.migrated 2.0M /opt/iobroker/iobroker-data/states.json.bak.migrated 0 /opt/iobroker/iobroker-data/states.json.broken =================== END OF SUMMARY ==================== === Mark text until here for copying === pi@raspberrypi4:/opt/iobroker $
Habe mit meinen Kenntnissen versucht, das Backup wieder einzuspielen:
sudo iobroker restore /backups/iobroker_2024_01_20-02_00_10_backupiobroker.tar.gz
endet in
<--- Last few GCs ---> [23750:0x5884a28] 24804 ms: Scavenge (reduce) 1022.5 (1034.2) -> 1022.5 (1035.7) MB, 22.5 / 0.0 ms (average mu = 0.802, current mu = 0.637) allocation failure; [23750:0x5884a28] 24878 ms: Mark-sweep (reduce) 1023.5 (1035.7) -> 1023.2 (1036.2) MB, 29.7 / 0.0 ms (+ 86.3 ms in 44 steps since start of marking, biggest step 19.6 ms, walltime since start of marking 186 ms) (average mu = 0.727, current mu = 0.555) <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iobroker: Zeile 12: 23749 Abgebrochen sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@"``` Ach ja - hätte ich mal die Finger davon gelassen... Hab zwar noch ne Vollsicherung als Image, hoffe aber erst mal auf die Profis. Gute Nacht, Gruß Frank
-
RE: Schon wieder ZigBee Problem
@arteck sagte in Schon wieder ZigBee Problem:
@ledies sagte in Schon wieder ZigBee Problem:
Kann es sein, dass das gelöschte Pairing im Iobroker noch irgendwo nicht angekommen ist und somit nicht neu gepairt wird?
nein.. dem coordinator ist es egal ob der shon driw war oder nicht.. aber vielleicht hast du damit das kaputte Gerät gefunden was dein Netz gestört hat.. also warum die anderen schicht immer direkt geschaltet haben
Danke für die Idee - daran hab ich gar nicht gedacht - ist vielleicht wirklich defekt.
Werde mal versuchen ihn zu reklamieren - sind ja erst ein paar Monate alt.Beim Versuch der Kopplung habe ich nicht richtig gelesen und. dachte im Reiter Ausschliessen wäre die Möglichkeit der direkten Kopplung gegeben und ich habe dummerweise auf das Plus geklickt und konnte dort den A1Z auswählen, was dann zu diesem Ergebnis führte:
Habe leider keine Ahnung, worum es hier geht:
Sie können hier einige Geräte hinzufügen, die von unserer Verarbeitung ausgeschlossen werden sollten. Sie verwenden dann nur exposes vom ZigBee-Herdsman-Converter. Nach dem Hinzufügen starten Sie bitte den Adapter neu.Allerdings bekomme ich den Eintrag nicht mehr gelöscht - die Mülltonne antwortet zwar mit
aber gelöscht wird der Eintrag nicht.Funktionieren tut trotzdem alles - kann das stehen bleiben oder wie bekomme ich den Eintrag wieder weg?
Ja - man sollte eigentlich vorher lesen... Fehler 40..
Danke für die Hilfe. -
RE: Schon wieder ZigBee Problem
Ich noch mal - die Geräteübernahme war dann doch nicht ganz problemlos.
Die Steckdosen NOUS A1Z schalteten doch sehr unzuverlässig und reagierten mal schnell und mal langsam.
Manche deutlich besser als andere, obwohl alle dieselben sind - hab 12 Stück davon.Also habe ich mit den Butte im Adapter (Neukonfiguration, Neukopplung, AN/Aus) versucht das Problem zu beheben - hat nichts gebracht.
Also mal auf Gerät löschen gedrückt , danach fing die LED am A1Z an zu blinken und auf Koppeln gedrückt. Das Gerät wurde sogleich wieder mit gleicher ID gekoppelt, den Namen wieder geändert, wie er vorher war und der A1Z funktioniert sofort und reagiert sofort.
Die Liste der Optionen in der Geräteansicht hat sich auch geändert - On/Off ist jetzt ganz Ober, vorher war es ganz unten.
Soweit, so gut - also einen nach dem anderen gelöscht und neu gekoppelt.Ging bei 11 der 12 gut, nur einer lässt sich einfach nicht mehr koppeln.
Die LED blinkt wie bei den anderen, ne Weile ausgesteckt, Werksreset (10 sek Taste halten) ohne Erfolg, IOB Neustart, Sonoff aus- einstecken, System Reboot - alles ohne Erfolg.Kann es sein, dass das gelöschte Pairing im Iobroker noch irgendwo nicht angekommen ist und somit nicht neu gepairt wird?
Der A1Z hat ja bis dahin funktioniert, nur nicht sofort.. -
RE: Schon wieder ZigBee Problem
@arteck sagte in Schon wieder ZigBee Problem:
@ledies sagte in Schon wieder ZigBee Problem:
Hoffentlich ist das ZigBee dann endlich stabil und man muss nicht mehr bei jedem reboot bangen..
nöö..damit wirst du auch problemem haben..
schick den zurück und hol den
wenn du glück hast musst du nix neu anlernen.. der übernimmt die config.
der Conbee zu 100 % macht es nichtKurzes Update - heute kam der neue Sonoff Stick, IOB mit dem neuen Stick neu gestartet, den USB Port ausgewählt und alle Geräte sind wieder da und funktionieren.
Hat wohl doch der alte Stick einen Defekt..Vielen Dank für die Unterstützung, hier werden sie geholfen
Schönen Gruß und schönes Wochenende.
-
RE: Schon wieder ZigBee Problem
@arteck said in Schon wieder ZigBee Problem:
@ledies sagte in Schon wieder ZigBee Problem:
Hoffentlich ist das ZigBee dann endlich stabil und man muss nicht mehr bei jedem reboot bangen..
nöö..damit wirst du auch problemem haben..
schick den zurück und hol den
wenn du glück hast musst du nix neu anlernen.. der übernimmt die config.
der Conbee zu 100 % macht es nichtDanke für den Tip - hab storniert und umbestellt .
Hab hier im Forum auch Infos zum udev Bug gefunden und versucht zu beheben.
ls -l /dev/serial/by-id ls: Zugriff auf '/dev/serial/by-id' nicht möglich: Datei oder Verzeichnis nicht gefunden
habe aus dem Beitrag
sudo nano /etc/apt/sources.list.d/bullseye-proposed-updates.list
mit
deb http://deb.debian.org/debian bullseye-proposed-updates main
eingerichtet, ändert aber nichts an der udev Version.
pi@raspberrypi4:~ $ sudo apt update OK:1 http://deb.debian.org/debian bullseye-proposed-updates InRelease OK:2 http://mirrordirector.raspbian.org/raspbian bullseye InRelease OK:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease OK:4 http://archive.raspberrypi.org/debian bullseye InRelease Holen:5 https://deb.nodesource.com/node_18.x bullseye InRelease [4.586 B] OK:6 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease Es wurden 4.586 B in 2 s geholt (2.208 B/s). Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Alle Pakete sind aktuell. pi@raspberrypi4:~ $ apt policy udev udev: Installiert: 247.3-7+rpi1+deb11u2 Installationskandidat: 247.3-7+rpi1+deb11u2 Versionstabelle: *** 247.3-7+rpi1+deb11u2 600 600 http://mirrordirector.raspbian.org/raspbian bullseye/main armhf Packages 100 /var/lib/dpkg/status
was mache ich falsch und was sind das für nicht aktualisierte Pakete?
sudo apt -t bullseye-proposed-updates install udev Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig udev ist schon die neueste Version (247.3-7+rpi1+deb11u2). 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 11 nicht aktualisiert.
-
RE: Schon wieder ZigBee Problem
@arteck said in Schon wieder ZigBee Problem:
ich sag nur Sonoff Stick.. bemühe die suche bitte
Tja - nach der Suche war ich genauso schlau wie vorher - gibt einfach zu viele gegensächliche Meinungen und je nach Anwenungen wahrscheinlich auch begründet.
Hab mir jetzt den "Phoscon ConBee II - universelles Zigbee 3.0 USB-Gateway, inkl. deCONZ & Phoscon App, Home Automation, Home Assistant, ioBroker, Zigbee2MQTT" bestellt, da er bei Amazon die meisten und besten Bewertungen hat.
Hoffentlich ist das ZigBee dann endlich stabil und man muss nicht mehr bei jedem reboot bangen..
Muss ich eigentlich mit dem neuen Adapter alle Geräte neu pairen und alles neu einrichten oder sind die Geräte weiter gekoppelt, bleiben die IDs erhalten?
-
Schon wieder ZigBee Problem
Systemdata Bitte Ausfüllen Hardwaresystem: RasperryPi 4 Arbeitsspeicher: 8GB Festplattenart: SSD Betriebssystem: linux 11 bullseye Node-Version: 18.17.1 Nodejs-Version: v18.17.1 NPM-Version: 9.6.7 Installationsart: Manuell Image genutzt: Nein raspberrypi4
Plattform linux
Betriebssystem linux 11 bullseye
Architektur arm
CPUs 4
Geschwindigkeit 1500 MHz
Modell ARMv7 Processor rev 3 (v7l)
RAM 7.71 GB
System-Betriebszeit 06:49:57
Node.js v18.17.1 (Es gibt eine neuere Version: v18.18.2)
time 1698212148160
timeOffset -120
NPM 9.6.7
Anzahl der Adapter 506
Datenträgergröße 109.75 GB
freier Festplattenspeicher 91.86 GB
Aktive Instanzen 22Schönen guten Morgen in die Runde.
Es fing so harmlos an - alles funktionierte.
Da sehe ich im Flur einen abgefallenen Aquara Türsensor. Also ein neues Klebepad geholt, hab ja genug und neu angeklebt.
Neben der Schachtel mit den Klebepads steht doch tatsächlich noch ein neuer Türsensor von Aquara - den kann ich doch gleich mal anmelden.Dumme Idee - war übrigens gestern ca 23 Uhr
Ich gehe in den ZigBee Adapter und starte die Kopplung
Im Fenster der Anmeldung zählt der Timer runter, kurz sehe ich eine lange Zeichekette reinkommen und das wars.
Kein neues Gerät gekoppelt, also noch mal - doch ab hier ging garnichts mehr.
Alle Geräte weg, ich soll doch erst mal einen Adpater pairen...Der USB Sniffer ist ein CC2531, billig in China bestellt und mit dem Programmer vor langer Zeit irgenwie mit ner FW von Texas Instruments geflasht.
So richtig krieg ich das nicht mehr zusammen - ist lange her.Jetzt kommt jedenfalls bei Aufruf des Zigbee Adapter die Meldung:
Error
You need save and run adapter before pairing!im Log:
zigbee.0
2023-10-25 07:31:08.617 error Error herdsman start
zigbee.0
2023-10-25 07:31:08.616 error Failed to start Zigbee
zigbee.0
2023-10-25 07:31:08.613 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0
2023-10-25 07:31:03.088 info Installed Version: iobroker.zigbee@1.8.23
zigbee.0
2023-10-25 07:31:03.042 info Starting Zigbee npm ...
zigbee.0
2023-10-25 07:31:03.038 info Try to reconnect. 1 attempts leftAdapter ausstecken, reboot mit angehaltener Instanz und ohne,
IObroker neustart, Zigbee Backup von gestern zurück gespielt - alles ohne Erfolg.Der Adapter ist auch anwählbar - funktioniert aber nicht mehr - eventuell ist er kaputt?
Wenn ich ihn anstecke, wird er in der Konsole auch gefunden:
ls -l /dev/serial/by-path insgesamt 0 lrwxrwxrwx 1 root root 13 25. Okt 06:16 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0 -> ../../ttyACM0
Stimmen hier eventuell Rechte nicht? Was bedeutet "insgesamt 0".
Im Adapter ist er auch mit ttyACM0 anwählbar - also sollte doch alles passen.
ls -l /dev/serial/by-id
geht seit einiger Zeit nicht mehr - obwohl damals so eingerichtet - (Datei oder Verzeichnis nicht gefunden)
Irgendwie hab ich von dem Teil die Nase voll - bin heute morgen gegen 2 Uhr hinter die Schränke gekrochen um die Steckdosen auszuschalten...
Ich bitte hiermit um Lösungsvorschläge bzw Hardwareempfehlungen zu einem Stick, welcher besser funktioniert.
Vielen Dank im Vorraus.