NEWS

@thomas-braun

Läuft, danke. Bin somit mit allem auf Trixie umgezogen.

scheint alles funktioniert zu haben 😉

========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: raspberrypi Icon name: computer Kernel: Linux 6.12.34+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.2 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 17:50:13 up 4:42, 1 user, load average: 0.38, 0.28, 0.29 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Mon 2025-09-08 17:50:13 CEST Universal time: Mon 2025-09-08 15:50:13 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 2.6G 778M 10M 694M 1.4G Swap: 536M 0B 536M Total: 4.5G 2.6G 1.3G Active iob-Instances: 20 3795 M total memory 2486 M used memory 2469 M active memory 388 M inactive memory 742 M free memory 71 M buffer memory 591 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 17:50:13 up 4:42, 1 user, load average: 0.43, 0.30, 0.29 Tasks: 205 total, 1 running, 204 sleeping, 0 stopped, 0 zombie %Cpu(s): 2.2 us, 0.0 sy, 0.0 ni, 97.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3795.8 total, 743.3 free, 2486.3 used, 662.7 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 1309.5 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 380M 6.6M 374M 2% /run /dev/sda2 ext4 220G 5.4G 204G 3% / tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 1.9G 3.0M 1.9G 1% /tmp tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service /dev/sda1 vfat 510M 65M 446M 13% /boot/firmware tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 380M 12K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon Sep 8 13:08:00 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=E4:5F:01:05:E3:AC vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyS0,115200 console=tty1 root=PARTUUID=e74f749d-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE [Mon Sep 8 13:08:02 2025] EXT4-fs (sda2): mounted filesystem d4cc7d63-da78-48ad-9bdd-64ffbba449a8 ro with ordered data mode. Quota mode: none. [Mon Sep 8 13:08:04 2025] EXT4-fs (sda2): re-mounted d4cc7d63-da78-48ad-9bdd-64ffbba449a8 r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot/firmware /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 872M /var/ 185M /var/lib 172M /var/cache 164M /var/cache/apt 144M /var/lib/apt Archived and active journals take up 5.3M in the file system. /opt/iobroker/backups: 162M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 365M /opt/iobroker/iobroker-data/ 168M /opt/iobroker/iobroker-data/files 103M /opt/iobroker/iobroker-data/backup-objects 47M /opt/iobroker/iobroker-data/files/admin.admin 46M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets The five largest files in iobroker-data are: 90M /opt/iobroker/iobroker-data/objects.jsonl 8.8M /opt/iobroker/iobroker-data/files/matter.admin/assets/index-CjzUbllv.js 8.6M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js 5.1M /opt/iobroker/iobroker-data/states.jsonl 4.6M /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2419780-if00 Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.19.0 /usr/bin/node v22.19.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.19.0-1nodesource1 Candidate: 22.19.0-1nodesource1 Version table: *** 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberrypi raspberrypi (version: 7.0.7, hostname: raspberrypi , alive, uptime: 16932) Core adapters versions js-controller: 7.0.7 admin: 7.6.17 javascript: 8.9.2 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : raspberrypi - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled + system.adapter.deconz.0 : deconz : raspberrypi - enabled, port: 80 system.adapter.devices.0 : devices : raspberrypi - disabled + system.adapter.email.0 : email : raspberrypi - enabled + system.adapter.fritzdect.0 : fritzdect : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.iot.0 : iot : raspberrypi - disabled + system.adapter.iqontrol.0 : iqontrol : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.matter.0 : matter : raspberrypi - enabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : raspberrypi - enabled, port: 8084, bind: 192.168.178.42, run as: admin + 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.trashschedule.0 : trashschedule : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + 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.admin.1 : admin : raspberrypi - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.deconz.0 : deconz : raspberrypi - enabled, port: 80 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : raspberrypi - enabled, port: 8084, bind: 192.168.178.42, run as: admin + 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 ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 2 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.6.17 , installed 7.6.17 Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "deconz" : 1.6.4 , installed 1.6.4 Adapter "devices" : 1.1.5 , installed 1.2.8 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "fritzdect" : 2.6.2 , installed 2.6.2 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "ical" : 1.16.2 , installed 1.16.2 Adapter "iot" : 3.3.0 , installed 3.6.0 Adapter "iqontrol" : 3.0.0 , installed 3.0.0 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "matter" : 0.5.2 , installed 0.5.2 Adapter "rpi2" : 2.4.0 , installed 2.4.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 5779 States: 4283 *** OS-Repositories and Updates *** W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://phoscon.de/apt/deconz generic InRelease Hit:5 http://archive.raspberrypi.com/debian trixie InRelease Hit:6 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details 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 192.168.178.42:8084 0.0.0.0:* LISTEN 1001 12609 1535/io.socketio.0 tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 7397 1015/exim4 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 6984 721/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 6989 721/iobroker.js-con tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 6864 738/sshd: /usr/sbin tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1000 7169 529/deCONZ tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1000 5117 529/deCONZ tcp6 0 0 :::8088 :::* LISTEN 1001 9303 1040/io.admin.1 tcp6 0 0 :::8087 :::* LISTEN 1001 12549 1509/io.simple-api. tcp6 0 0 :::8082 :::* LISTEN 1001 12746 1746/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 7087 1029/io.admin.0 tcp6 0 0 ::1:25 :::* LISTEN 0 7398 1015/exim4 tcp6 0 0 :::22 :::* LISTEN 0 6866 738/sshd: /usr/sbin udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 123306 11803/io.matter.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 123292 11803/io.matter.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 123284 11803/io.matter.0 udp 0 0 192.168.178.42:5353 0.0.0.0:* 1001 11333 1410/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 4931 523/avahi-daemon: r udp 0 0 0.0.0.0:5540 0.0.0.0:* 1001 123301 11803/io.matter.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 10653 1312/io.deconz.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 8196 529/deCONZ udp 0 0 0.0.0.0:44997 0.0.0.0:* 104 4933 523/avahi-daemon: r udp6 0 0 fe80::62d5:ebcd:e5c:546 :::* 0 7295 701/NetworkManager udp6 0 0 :::42215 :::* 104 4934 523/avahi-daemon: r udp6 0 0 :::5353 :::* 1001 123307 11803/io.matter.0 udp6 0 0 :::5353 :::* 1001 123295 11803/io.matter.0 udp6 0 0 :::5353 :::* 1001 123287 11803/io.matter.0 udp6 0 0 :::5353 :::* 104 4932 523/avahi-daemon: r udp6 0 0 :::5540 :::* 1001 123300 11803/io.matter.0 udp6 0 0 :::1900 :::* 1001 10656 1312/io.deconz.0 udp6 0 0 :::1900 :::* 1001 10655 1312/io.deconz.0 udp6 0 0 :::1900 :::* 1001 10654 1312/io.deconz.0 *** Log File - Last 25 Lines *** 2025-09-08 16:42:06.727 - info: email.0 (1058) terminating 2025-09-08 16:42:07.008 - info: host.raspberrypi instance system.adapter.email.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-09-08 16:42:20.939 - info: host.raspberrypi "system.adapter.email.0" enabled 2025-09-08 16:42:22.603 - info: host.raspberrypi instance system.adapter.email.0 in version "2.0.4" started with pid 12291 2025-09-08 16:42:25.327 - info: email.0 (12291) starting. Version 2.0.4 in /opt/iobroker/node_modules/iobroker.email, node: v22.19.0, js-controller: 7.0.7 2025-09-08 16:42:37.080 - info: javascript.0 (1141) script.js.common.Wichtig.System_Adapter_wahr_falsch_TEST: telegram[Michael]: email.0 is connected Wert: false Adapter NICHT erreichbar 2025-09-08 16:43:10.364 - info: javascript.0 (1141) script.js.common.Wichtig.System_Adapter_wahr_falsch_TEST: telegram[Michael]: email.0 is connected Wert: true Adapter ist wieder erreichbar 2025-09-08 16:43:34.817 - info: admin.0 (1029) <== Disconnect system.user.admin from ::ffff:192.168.178.76 admin 2025-09-08 16:43:35.934 - info: admin.0 (1029) <== Disconnect system.user.admin from ::ffff:192.168.178.76 devices 2025-09-08 16:43:35.936 - info: admin.0 (1029) <== Disconnect system.user.admin from ::ffff:192.168.178.76 admin 2025-09-08 16:43:41.620 - info: admin.0 (1029) <== Disconnect system.user.admin from ::ffff:192.168.178.76 admin 2025-09-08 17:00:00.085 - info: javascript.0 (1141) script.js.common.Müllkalender.Müllerinnerung: telegram['Michael']: Morgen wird die Biotonne abgeholt 2025-09-08 17:07:18.731 - info: javascript.0 (1141) script.js.common.Tür_Fenster_Sensoren.Wohnungstüre: telegram[Michael]: Wohnungstür wurde geöffnet ! 2025-09-08 17:07:40.805 - info: javascript.0 (1141) script.js.common.Tür_Fenster_Sensoren.Wohnungstüre: telegram[Michael]: Wohnungstür wurde geschlossen ! 2025-09-08 17:11:34.535 - info: javascript.0 (1141) script.js.common.Anwesendheitscheck.Marvin_PC_AN_AUS_Wlan: telegram['Michael']: Marvin Pc wurde angemacht (Wlan) 2025-09-08 17:11:35.288 - info: javascript.0 (1141) script.js.common.Anwesendheitscheck.Marvin_I_Phone_Anwesend_JA_NEIN: telegram[Michael]: Marvin IPhone ist im Wlan 2025-09-08 17:30:00.047 - info: host.raspberrypi instance system.adapter.ical.0 in version "1.16.2" started with pid 14347 2025-09-08 17:30:02.903 - info: ical.0 (14347) starting. Version 1.16.2 in /opt/iobroker/node_modules/iobroker.ical, node: v22.19.0, js-controller: 7.0.7 2025-09-08 17:30:03.818 - info: ical.0 (14347) processing URL: Müllkalender https://calendar.google.com/calendar/ical/8n95sqg3r88betcpncgkhe3m8c%40group.calendar.google.com/private-32cc3a968fd521a665efcc600d6ce4d4/basic.ics 2025-09-08 17:30:09.127 - info: ical.0 (14347) Terminated (NO_ERROR): Without reason 2025-09-08 17:30:09.681 - info: host.raspberrypi instance system.adapter.ical.0 having pid 14347 terminated with code 0 (NO_ERROR)

@martinp sagte in Neustart iobroker nach node js update:

die apt update und full-upgrade Prozedur muss man ja eh regelmäßig durchführen, und da würde ich gerne bei bleiben als zentrales tool für das Aktuell halten, und auch node js darüber aktuell halten...

Das ist genau richtig.

@azrael42 wenn der i5 -8500T "schon da" ist, würde ich den auch benutzen..

Wenn es aber um eine Kaufentscheidung geht, und man sich anschaut, was die Aufbereiter z. B. für einen "Refurbished" Lenovo Thinkcentre M720Q mit diesem Prozessor haben wollen, würde ich eher zum AMD-Neusystem greifen ...

Wenn man das Ding natürlich für deutlich unter 100 € bekommen kann, würde ich auch zuschlagen ... Günstigstes Angebot ist 179 € ... das finde ich vergleichsweise teuer

https://www.refurbed.de/p/lenovo-thinkcentre-m920q-tiny/61595/?offer=1185438

@thomas-braun said in WLan Einrichten unter Debian 13?:

per Network-Manager dürfte das am besten zu bewerkstelligen sein

Danke für die Rückmeldung.

@thomas-braun Ja genau. Dann mache ich mal ein eigenen Thread auf. Danke.
Konnte es selber klären siehe Failed Services im LXC

@smartuser_1 sagte in Speicherplatz Influx:

Das ist alles oder fehlt noch was?

Schau ob noch Updates angezeigt werden. Neustart gemacht?

@wendy2702 Danke dir, ich hätte vermutlich "Y" gemacht, scheint nun wieder alles an zu laufen, sieht soweit ok aus.

@powertrain01

Dann kannst du auch gleich die anderen Kinken angehehn.
Stromversorgung, Zigbee-Gerät usw.

@norbert999

Also bei mir funktioniert das so:
Wenn das der mount ist
sudo mount -t cifs -o user="",pass="",sec=ntlmv2,noserverino,vers=3.1.1 //192.168.****/fritz.nas/rout_bak/RaspSys /media/nas

dann läuft die Wiederherstellung so:
sudo raspiBackup.sh -d /dev/sda /media/nas/broker/broker@debian12-tar-backup-****/

In der raspiBackupInstallUI sollten die erforderlichen Angaben gemacht werden. Aber da das backup läuft, sollte alles stimmen.

sda steht für ein usb-laufwerk, bei mir ein usb Adapter, in dem die sdhc Karte steckt.

das mal mit
sudo parted -l
testen. das Laufwerk mit Bezeichnung wird dann angezeigt.

Evtl. kannst du das für deine Konfiguration übertragen.

@homoran Mea Culpa - Zu heiß heute ...

@berggeist sagte in Raspi bootet nicht mit neuem Image,aber Home Assistant geht:

Das betrifft alle aktuellen Raspberry OS Betriebssysteme welche im Imager angeboten

Da hast du dann aber schon einiges durchprobiert.
32 bit / 64 Bit, jeweils mit und ohne Desktop, jeweils bookworm oder bullseye........

Bitte testweise mal eine ganz bestimmte Version (bookworm 64 lite) nehmen.

wenn das mit dem imager nicht klappt einmal mit balena etcher o.ä. testen

@berggeist sagte in Raspi bootet nicht mit neuem Image,aber Home Assistant geht:

Die rote LED leuchtet ständig

passt!

@berggeist sagte in Raspi bootet nicht mit neuem Image,aber Home Assistant geht:

die grüne LED blinkt nach ca. 30 Sekunden mit ca. 1 Herz

und vorher?

ansonsten Problem mit dem Bootloader/Kartenerkennung

@Daniel-5

Vielleicht hilft das https://homematic-forum.de/forum/viewtopic.php?f=69&t=85134&p=832348#p832632

@martinp

So wie ich es verstehe, macht needrestart ein sudo systemctl restart iobroker.service . Warum dann vorher stoppen.

Ich hatte noch keine Probleme mit needrestart.

Hallo nochmal.

Ich habe jetzt einen neuen Stick (Zigbee 3.0 USB Dongle Plus) den Zigbee Adapter V3.0.1 neu installiert und versuche nun meine Geräte neu anzulernen.

Leider kommt immer ein Herdsman Fehler.

zigbee.0 2025-06-25 11:06:24.603 warn ELEVATED:I02 (a0ca) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.602 warn ELEVATED:I02 (a0ca) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.601 warn ELEVATED:I01 (a0ca) message received '{"linkquality":171}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.598 warn ELEVATED:I02 (a0c2) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.597 warn ELEVATED:I02 (a0c2) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.596 warn ELEVATED:I01 (a0c2) message received '{"linkquality":168}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.592 warn ELEVATED:I02 (a0c0) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.592 warn ELEVATED:I02 (a0c0) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.592 warn ELEVATED:I01 (a0c0) message received '{"linkquality":168}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.591 warn ELEVATED:I02 (a0b3) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.590 warn ELEVATED:I02 (a0b3) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.589 warn ELEVATED:I01 (a0b3) message received '{"linkquality":168}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.587 warn ELEVATED:I01 (a0ca) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":171,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":97,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:24.578 warn ELEVATED:I01 (a0c2) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":15},"linkquality":168,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":96,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:24.576 warn ELEVATED:I01 (a0c0) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":168,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":95,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:24.565 warn ELEVATED:I01 (a0b3) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":2869},"linkquality":168,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":94,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.592 warn ELEVATED:I02 (661d) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.592 warn ELEVATED:I02 (661d) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.591 warn ELEVATED:I01 (661d) message received '{"linkquality":174}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.578 warn ELEVATED:I02 (6611) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.576 warn ELEVATED:I02 (6611) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.575 warn ELEVATED:I01 (6611) message received '{"linkquality":171}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.574 warn ELEVATED:I02 (660e) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.573 warn ELEVATED:I02 (660e) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.573 warn ELEVATED:I01 (660e) message received '{"linkquality":171}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.566 warn ELEVATED:I01 (661d) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":174,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":93,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.553 warn ELEVATED:I01 (6611) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":15},"linkquality":171,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":92,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.551 warn ELEVATED:I01 (660e) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":171,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":91,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.393 warn ELEVATED:I02 (6568) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.392 warn ELEVATED:I02 (6568) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.391 warn ELEVATED:I01 (6568) message received '{"linkquality":174}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.385 warn ELEVATED:I01 (6568) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":2869},"linkquality":174,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":88,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

Irgendwo steckt wohl noch was fest. Gibt es eine Möglichkeit Zigbee komplett mit allem zu entfernen und neu zu beginnen?

Failed to open the network: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms at Object.start (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:47:23) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:263:41 at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/queue.js:29:26) at Znp.requestZdo (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:257:27) at func (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:322:32) at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/queue.js:29:26) at ZStackAdapter.sendZdoInternal (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:341:60) at ZStackAdapter.sendZdo (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:263:27) at ZStackAdapter.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:176:24) at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:249:32)

Mfg
Tom

@thomas-braun
da ich noch einen zweiten Conbee II habe, konnte ich den ausprobieren. Das hat sofort und ohne weitere Anpassungen funktioniert (Sensoren haben gemeldet).
Der Fehler mit dem Dateisystem wird trotzdem angezeigt, auch nach reboot.
Somit muß ich annehmen, dass nicht der Conbee II die Ursache ist und ein Firmware-Update nichts bringt (in der Annahme, dass die Firmware auf dem Stick liegt).

Ich hebe jetzt bei der Fehlernachricht vom 17.06.25 auf "Bestätigen und Schließen" geklickt. Mal sehen, ob der Fehler wieder kommt.

@syntetic

Wie gesagt, schau in deinem DHCP-Server nach.

Oder schau mir

dig hostname

nach wie die Auflösung läuft.

@zimbl
geht eigentlich ganz einfach!

Dann wollen wir es diesmal ganz richtig machen, falls da schon was im Argen liegt.
Sehen wir uns erstmal die vorhandene Basis an

iob diag in der Langfassung bitte

@postworld Vielleicht hast Du mal in der Vergangenheit auf "Alle Skripte exportieren" geklickt. Dann hast Du mit viel Glück das Gesuchte auf der Festplatte im Downloads-Ordner.

Ich klicke da regelmäßig drauf, so habe ich auch einen rudimentären Verlauf / Vorgängerversionen der Skripte.