NEWS
admin startet nach Backup nicht mehr
Installation
34
Beiträge
4
Kommentatoren
774
Aufrufe
3
Watching
-
@thomas-braun sagte in admin startet nach Backup nicht mehr:
Da geht dir der Speicher aus.
dachte ich auch!
Aber bei@ljsven sagte in admin startet nach Backup nicht mehr:
Mem: 8.2G 4.3G 1.5G 426M 3.1G 3.9G
und 0 Swap wohl eher ein anderes Problem.
RAM-Hardware?@homoran sagte in admin startet nach Backup nicht mehr:
und 0 Swap wohl eher ein anderes Problem.
RAM-Hardware?Auf dem Heap von nodejs, nicht im RAM.
-
@thomas-braun sagte in admin startet nach Backup nicht mehr:
Biste mit dem Backup von Steinzeit-Versionen auf das neue System gegangen?
Vorsteinzeit auf Zukunft ;-) Wie ich aber vorhin geschrieben habe - das Problem hatte ich schon auf früheren Updates mit dem Raspberry.
@ljsven sagte in admin startet nach Backup nicht mehr:
Vorsteinzeit auf Zukunft
Das funktioniert nicht (zuverlässig).
Man fährt auf dem Alt-System die Versionen (soweit es noch geht) an den aktuellen Stand ran, zieht davon ein Backup und zieht damit um.Das sind dann die Folgen vom den 'Never tatsch a running süstäm'-Schwachsinn.
-
@ljsven sagte in admin startet nach Backup nicht mehr:
Vorsteinzeit auf Zukunft
Das funktioniert nicht (zuverlässig).
Man fährt auf dem Alt-System die Versionen (soweit es noch geht) an den aktuellen Stand ran, zieht davon ein Backup und zieht damit um.Das sind dann die Folgen vom den 'Never tatsch a running süstäm'-Schwachsinn.
@thomas-braun sagte in admin startet nach Backup nicht mehr:
@ljsven sagte in admin startet nach Backup nicht mehr:
Vorsteinzeit auf Zukunft
Das funktioniert nicht (zuverlässig).
Man fährt auf dem Alt-System die Versionen (soweit es noch geht) an den aktuellen Stand ran, zieht davon ein Backup und zieht damit um.Das sind dann die Folgen vom den 'Never tatsch a running süstäm'-Schwachsinn.
Was würdest du mir vorschlagen?
Macht es Sinn, die Kiste neu aufzusetzen, als Slave ins Multihost einsetzten und Adapter für Adapter rüber holen? Bekomme ich ihn anschließend als Master hin?
-
@thomas-braun sagte in admin startet nach Backup nicht mehr:
@ljsven sagte in admin startet nach Backup nicht mehr:
Vorsteinzeit auf Zukunft
Das funktioniert nicht (zuverlässig).
Man fährt auf dem Alt-System die Versionen (soweit es noch geht) an den aktuellen Stand ran, zieht davon ein Backup und zieht damit um.Das sind dann die Folgen vom den 'Never tatsch a running süstäm'-Schwachsinn.
Was würdest du mir vorschlagen?
Macht es Sinn, die Kiste neu aufzusetzen, als Slave ins Multihost einsetzten und Adapter für Adapter rüber holen? Bekomme ich ihn anschließend als Master hin?
Das 'Backup' stammt von dem Raspberry?
-
Das 'Backup' stammt von dem Raspberry?
-
@thomas-braun Ja genau!
Dann mach es wie oben beschrieben...
-
@thomas-braun sagte in admin startet nach Backup nicht mehr:
Biste mit dem Backup von Steinzeit-Versionen auf das neue System gegangen?
Vorsteinzeit auf Zukunft ;-) Wie ich aber vorhin geschrieben habe - das Problem hatte ich schon auf früheren Updates mit dem Raspberry.
@Thomas-Braun
das hatte er ja auch nicht geschafft@ljsven sagte in admin startet nach Backup nicht mehr:
das Problem hatte ich schon auf früheren Updates mit dem Raspberry.
leider ohne weiter Informationen was genau.
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@Thomas-Braun
das hatte er ja auch nicht geschafft@ljsven sagte in admin startet nach Backup nicht mehr:
das Problem hatte ich schon auf früheren Updates mit dem Raspberry.
leider ohne weiter Informationen was genau.
@homoran Bei mir ist das System in die Knie gegangen wo ich js (wenn ich richtig liege) von 5.0.11 auf 5.0.19 updaten sollte. Danach hat der admin immer Probleme gemacht. Daraufhin wurde mir gesagt (auch hier im Forum) - neue Version,
mehr Ressourcen.Ich glaube mittlerweile, dass das Problem woanders liegt. Vielleicht in meiner config - Daher
frage ich mich, wie ich da rauskomme, ohne bei A anzufangen. -
@Thomas-Braun
das hatte er ja auch nicht geschafft@ljsven sagte in admin startet nach Backup nicht mehr:
das Problem hatte ich schon auf früheren Updates mit dem Raspberry.
leider ohne weiter Informationen was genau.
@homoran sagte in admin startet nach Backup nicht mehr:
das hatte er ja auch nicht geschafft
Dann muss man sich das halt mal anschauen. Das Ignorieren von Updates (das ist nämlich der eigentliche Grund für das pseudoschlaue NTARS-"Konzept") bringt dir halt nix.
-
@homoran Bei mir ist das System in die Knie gegangen wo ich js (wenn ich richtig liege) von 5.0.11 auf 5.0.19 updaten sollte. Danach hat der admin immer Probleme gemacht. Daraufhin wurde mir gesagt (auch hier im Forum) - neue Version,
mehr Ressourcen.Ich glaube mittlerweile, dass das Problem woanders liegt. Vielleicht in meiner config - Daher
frage ich mich, wie ich da rauskomme, ohne bei A anzufangen.@ljsven sagte in admin startet nach Backup nicht mehr:
Bei mir ist das System in die Knie gegangen wo ich js (wenn ich richtig liege) von 5.0.11 auf 5.0.19 updaten sollte.
Gib mal
iob diagvon dem Raspberry...
-
@homoran Bei mir ist das System in die Knie gegangen wo ich js (wenn ich richtig liege) von 5.0.11 auf 5.0.19 updaten sollte. Danach hat der admin immer Probleme gemacht. Daraufhin wurde mir gesagt (auch hier im Forum) - neue Version,
mehr Ressourcen.Ich glaube mittlerweile, dass das Problem woanders liegt. Vielleicht in meiner config - Daher
frage ich mich, wie ich da rauskomme, ohne bei A anzufangen.@ljsven Hast du das alte System noch?
Dann mach da mal einiob diag -
========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: tinkerboard Icon name: computer Kernel: Linux 6.6.63-current-rockchip Architecture: arm OS is similar to: model name : ARMv7 Processor rev 1 (v7l) Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit Systemuptime and Load: 21:46:11 up 14 days, 7:16, 2 users, load average: 0.52, 0.25, 0.20 CPU threads: 4 *** LIFE CYCLE STATUS *** Unknown release codenamed 'bookworm'. Please check yourself if the Operating System is actively maintained. *** TIME AND TIMEZONES *** Local time: Wed 2025-11-05 21:46:12 CET Universal time: Wed 2025-11-05 20:46:12 UTC RTC time: Wed 2025-11-05 20:46:12 Time zone: Europe/Berlin (CET, +0100) 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 tty disk dialout sudo audio video plugdev games users input netdev bluetooth systemd-journal iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker 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 System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 2.1G 1.3G 610M 3.8M 240M 791M Swap: 1.1G 309M 741M Total: 3.2G 1.6G 1.4G Active iob-Instances: 24 2004 M total memory 1249 M used memory 669 M active memory 522 M inactive memory 583 M free memory 38 M buffer memory 190 M swap cache 1002 M total swap 295 M used swap 706 M free swap *** top - Table Of Processes *** top - 21:46:12 up 14 days, 7:16, 2 users, load average: 0.52, 0.25, 0.20 Tasks: 167 total, 1 running, 166 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 20.0 sy, 0.0 ni, 80.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 2005.0 total, 581.8 free, 1251.1 used, 229.3 buff/cache MiB Swap: 1002.5 total, 707.0 free, 295.5 used. 753.9 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 991M 0 991M 0% /dev tmpfs tmpfs 201M 4.4M 197M 3% /run /dev/mmcblk0p1 ext4 117G 7.7G 108G 7% / tmpfs tmpfs 1003M 0 1003M 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 1003M 0 1003M 0% /tmp /dev/zram1 ext4 47M 29M 15M 67% /var/log tmpfs tmpfs 201M 0 201M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Oct 22 15:29:30 2025] Kernel command line: earlyprintk root=UUID=0025963e-ae6c-4147-9295-c418a82cbe11 rootwait rootfstype=ext4 splash=verbose console=ttyS2,115200n8 console=tty1 consoleblank=0 loglevel=1 ubootpart=ae152935-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u coherent_pool=2M cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [Wed Oct 22 15:29:36 2025] EXT4-fs (mmcblk0p1): mounted filesystem 0025963e-ae6c-4147-9295-c418a82cbe11 ro with writeback data mode. Quota mode: none. [Wed Oct 22 15:29:38 2025] EXT4-fs (mmcblk0p1): re-mounted 0025963e-ae6c-4147-9295-c418a82cbe11 r/w. Quota mode: none. [Wed Oct 22 15:29:40 2025] EXT4-fs (zram1): mounted filesystem 9b2531c2-609f-4cee-9205-a0e69feabee0 r/w without journal. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p1 ext4 rw,noatime,errors=remount-ro,commit=600 |-/var/log.hdd /dev/mmcblk0p1[/var/log] ext4 rw,noatime,errors=remount-ro,commit=600 `-/var/log /dev/zram1 ext4 rw,nosuid,nodev,noexec,relatime,discard Files in neuralgic directories: /var: 434M /var/ 217M /var/cache 212M /var/cache/apt 141M /var/cache/apt/archives 138M /var/lib Archived and active journals take up 21.9M in the file system. /opt/iobroker/backups: 2.0G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 992M /opt/iobroker/iobroker-data/ 853M /opt/iobroker/iobroker-data/files 441M /opt/iobroker/iobroker-data/files/javascript.admin 409M /opt/iobroker/iobroker-data/files/javascript.admin/static 408M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 28M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.ce422ec2.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.1e6546bb.js.map 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_DE1964189-if00 *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyACM0 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 v18.20.6 /usr/bin/node v18.20.6 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 18.20.6-1nodesource1 Candidate: 18.20.6-1nodesource1 Version table: *** 18.20.6-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.20.5-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.4-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.3-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main armhf Packages 18.19.0+dfsg-6~deb12u1 500 500 http://security.debian.org bookworm-security/main armhf Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 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 Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: ██████ █████ ███ ██ ██████ ███████ ███████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ███████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ v18.20.6 is end-of-life. There are high chances of being vulnerable. Please upgrade it. *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberrypi raspberrypi (version: 6.0.9, hostname: raspberrypi , alive, uptime: 4073374) tinkerboard tinkerboard (version: 5.0.11, hostname: tinkerboard , alive, uptime: 1233824) Core adapters versions js-controller: 5.0.11 admin: 7.0.22 javascript: 8.7.6 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : tinkerboard - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : tinkerboard - enabled system.adapter.backitup.0 : backitup : tinkerboard - enabled system.adapter.daswetter.0 : daswetter : raspberrypi - enabled system.adapter.discovery.0 : discovery : tinkerboard - disabled system.adapter.email.0 : email : raspberrypi - disabled system.adapter.flot.0 : flot : tinkerboard - disabled system.adapter.fritzdect.0 : fritzdect : raspberrypi - disabled + system.adapter.geofency.0 : geofency : raspberrypi - enabled, port: 7999, bind: 0.0.0.0 + system.adapter.history.0 : history : tinkerboard - enabled system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.icons-icons8.0 : icons-icons8 : raspberrypi - disabled system.adapter.icons-material-png.0 : icons-material-png : tinkerboard - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : tinkerboard - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : tinkerboard - disabled system.adapter.info.0 : info : tinkerboard - disabled + system.adapter.iot.0 : iot : tinkerboard - enabled + system.adapter.javascript.0 : javascript : tinkerboard - enabled + system.adapter.linkeddevices.0 : linkeddevices : tinkerboard - enabled + system.adapter.mihome.0 : mihome : tinkerboard - enabled, port: 9898, bind: 0.0.0.0 system.adapter.modbus.0 : modbus : tinkerboard - disabled + system.adapter.mqtt.0 : mqtt : tinkerboard - enabled, port: 1886, bind: 0.0.0.0 system.adapter.radar2.0 : radar2 : tinkerboard - disabled system.adapter.rpi2.0 : rpi2 : raspberrypi - disabled + system.adapter.scenes.0 : scenes : tinkerboard - enabled + system.adapter.shelly.0 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : tinkerboard - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.smartmeter.3 : smartmeter : raspberrypi - enabled + system.adapter.smartmeter.4 : smartmeter : raspberrypi - enabled + system.adapter.socketio.0 : socketio : tinkerboard - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : tinkerboard - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sql.0 : sql : tinkerboard - enabled, port: 3306 + system.adapter.telegram.0 : telegram : tinkerboard - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : raspberrypi - enabled system.adapter.tinker.0 : tinker : tinkerboard - disabled system.adapter.tr-064.0 : tr-064 : tinkerboard - disabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled system.adapter.tuya.0 : tuya : raspberrypi - disabled system.adapter.vis-history.0 : vis-history : tinkerboard - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : tinkerboard - disabled system.adapter.vis-icontwo.0 : vis-icontwo : tinkerboard - disabled system.adapter.vis-metro.0 : vis-metro : tinkerboard - disabled system.adapter.vis-rgraph.0 : vis-rgraph : tinkerboard - disabled system.adapter.vis.0 : vis : tinkerboard - disabled + system.adapter.web.0 : web : tinkerboard - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : tinkerboard - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : tinkerboard - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.geofency.0 : geofency : raspberrypi - enabled, port: 7999, bind: 0.0.0.0 + system.adapter.mihome.0 : mihome : tinkerboard - enabled, port: 9898, bind: 0.0.0.0 + system.adapter.mqtt.0 : mqtt : tinkerboard - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : tinkerboard - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : tinkerboard - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : tinkerboard - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sql.0 : sql : tinkerboard - enabled, port: 3306 + system.adapter.telegram.0 : telegram : tinkerboard - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : tinkerboard - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : tinkerboard - enabled, port: /dev/ttyACM0 ioBroker-Repositories Stable (default): http://download.iobroker.net/sources-dist.json Beta (latest) : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) Installed ioBroker-Adapters Used repository: Stable (default) Adapter "admin" : 7.7.19 , installed 7.0.22 [Updatable] Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "backitup" : 3.3.10 , installed 3.0.16 [Updatable] Adapter "discovery" : 5.0.0 , installed 4.5.0 [Updatable] Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "ical" : 1.17.0 , installed 1.15.0 [Updatable] Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 5.0.7 , installed 3.3.0 [Updatable] Adapter "javascript" : 8.9.2 , installed 8.7.6 [Updatable] Controller "js-controller": 7.0.7 , installed 5.0.11 [Updatable] Adapter "lgtv11" : 1.0.5 , installed 1.0.5 Adapter "linkeddevices": 1.5.5 , installed 1.5.5 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "modbus" : 6.3.2 , installed 6.2.3 [Updatable] Adapter "mqtt" : 6.1.4 , installed 5.2.0 [Updatable] Adapter "radar2" : 2.4.0 , installed 2.2.0 [Updatable] Adapter "scenes" : 3.2.3 , installed 3.2.1 [Updatable] Adapter "shelly" : 10.4.0 , installed 7.0.0 [Updatable] Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.0.3 [Updatable] Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "telegram" : 4.1.0 , installed 3.9.0 [Updatable] Adapter "tinker" : 1.3.9 , installed 1.3.2 [Updatable] Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-icontwo" : 1.18.0 , installed 1.5.0 [Updatable] Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "web" : 7.0.8 , installed 6.2.5 [Updatable] Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.1.5 , installed 1.0.3 [Updatable] Adapter "zigbee" : 3.1.5 , installed 1.10.3 [Updatable] Objects and States Please stand by - This may take a while Objects: 11911 States: 6830 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://deb.debian.org/debian bookworm-backports InRelease Hit:5 http://armbian.hosthatch.com/apt bookworm InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 127 *** 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:9001 0.0.0.0:* LISTEN 1001 28316 1845/iobroker.js-co tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 28336 1845/iobroker.js-co tcp 0 0 0.0.0.0:1888 0.0.0.0:* LISTEN 1001 29796 2029/io.shelly.1 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 28485 1999/io.mqtt.0 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 29601 2044/io.sonoff.0 tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 997 7549 557/systemd-resolve tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 997 7535 557/systemd-resolve tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 997 7547 557/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 8521 1055/sshd: /usr/sbi tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 7107 1/init tcp6 0 0 :::8084 :::* LISTEN 1001 29878 2114/io.socketio.0 tcp6 0 0 :::8087 :::* LISTEN 1001 29687 2092/io.simple-api. tcp6 0 0 :::8081 :::* LISTEN 1001 27606 1871/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 28587 2107/io.web.0 tcp6 0 0 :::1884 :::* LISTEN 1001 30808 1905/io.javascript. tcp6 0 0 :::5355 :::* LISTEN 997 7543 557/systemd-resolve tcp6 0 0 :::22 :::* LISTEN 0 8523 1055/sshd: /usr/sbi tcp6 0 0 :::111 :::* LISTEN 0 348 1/init udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 28519 2010/io.shelly.0 udp 0 0 127.0.0.54:53 0.0.0.0:* 997 7548 557/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 997 7546 557/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 7108 1/init udp 0 0 0.0.0.0:9898 0.0.0.0:* 1001 12474601 1984/io.mihome.0 udp 0 0 0.0.0.0:5355 0.0.0.0:* 997 7534 557/systemd-resolve udp 0 0 127.0.0.1:323 0.0.0.0:* 0 7861 1009/chronyd udp6 0 0 fe80::4baa:4d74:411:546 :::* 0 8782 813/NetworkManager udp6 0 0 :::111 :::* 0 7109 1/init udp6 0 0 :::5355 :::* 997 7542 557/systemd-resolve udp6 0 0 ::1:323 :::* 0 7862 1009/chronyd *** Log File - Last 25 Lines *** 2025-11-05 20:43:17.645 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:25.017 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:31.848 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:38.905 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:45.851 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:53.540 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:00.549 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:07.403 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:14.309 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:21.231 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:28.136 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:35.050 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:41.970 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:48.885 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:55.830 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:02.753 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:09.648 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:16.617 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:23.998 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:30.928 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:37.839 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:44.734 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:51.680 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:58.555 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:46:05.663 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running============ Mark until here for C&P =============
-
========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: tinkerboard Icon name: computer Kernel: Linux 6.6.63-current-rockchip Architecture: arm OS is similar to: model name : ARMv7 Processor rev 1 (v7l) Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit Systemuptime and Load: 21:46:11 up 14 days, 7:16, 2 users, load average: 0.52, 0.25, 0.20 CPU threads: 4 *** LIFE CYCLE STATUS *** Unknown release codenamed 'bookworm'. Please check yourself if the Operating System is actively maintained. *** TIME AND TIMEZONES *** Local time: Wed 2025-11-05 21:46:12 CET Universal time: Wed 2025-11-05 20:46:12 UTC RTC time: Wed 2025-11-05 20:46:12 Time zone: Europe/Berlin (CET, +0100) 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 tty disk dialout sudo audio video plugdev games users input netdev bluetooth systemd-journal iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker 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 System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 2.1G 1.3G 610M 3.8M 240M 791M Swap: 1.1G 309M 741M Total: 3.2G 1.6G 1.4G Active iob-Instances: 24 2004 M total memory 1249 M used memory 669 M active memory 522 M inactive memory 583 M free memory 38 M buffer memory 190 M swap cache 1002 M total swap 295 M used swap 706 M free swap *** top - Table Of Processes *** top - 21:46:12 up 14 days, 7:16, 2 users, load average: 0.52, 0.25, 0.20 Tasks: 167 total, 1 running, 166 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 20.0 sy, 0.0 ni, 80.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 2005.0 total, 581.8 free, 1251.1 used, 229.3 buff/cache MiB Swap: 1002.5 total, 707.0 free, 295.5 used. 753.9 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 991M 0 991M 0% /dev tmpfs tmpfs 201M 4.4M 197M 3% /run /dev/mmcblk0p1 ext4 117G 7.7G 108G 7% / tmpfs tmpfs 1003M 0 1003M 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 1003M 0 1003M 0% /tmp /dev/zram1 ext4 47M 29M 15M 67% /var/log tmpfs tmpfs 201M 0 201M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Oct 22 15:29:30 2025] Kernel command line: earlyprintk root=UUID=0025963e-ae6c-4147-9295-c418a82cbe11 rootwait rootfstype=ext4 splash=verbose console=ttyS2,115200n8 console=tty1 consoleblank=0 loglevel=1 ubootpart=ae152935-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u coherent_pool=2M cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [Wed Oct 22 15:29:36 2025] EXT4-fs (mmcblk0p1): mounted filesystem 0025963e-ae6c-4147-9295-c418a82cbe11 ro with writeback data mode. Quota mode: none. [Wed Oct 22 15:29:38 2025] EXT4-fs (mmcblk0p1): re-mounted 0025963e-ae6c-4147-9295-c418a82cbe11 r/w. Quota mode: none. [Wed Oct 22 15:29:40 2025] EXT4-fs (zram1): mounted filesystem 9b2531c2-609f-4cee-9205-a0e69feabee0 r/w without journal. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p1 ext4 rw,noatime,errors=remount-ro,commit=600 |-/var/log.hdd /dev/mmcblk0p1[/var/log] ext4 rw,noatime,errors=remount-ro,commit=600 `-/var/log /dev/zram1 ext4 rw,nosuid,nodev,noexec,relatime,discard Files in neuralgic directories: /var: 434M /var/ 217M /var/cache 212M /var/cache/apt 141M /var/cache/apt/archives 138M /var/lib Archived and active journals take up 21.9M in the file system. /opt/iobroker/backups: 2.0G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 992M /opt/iobroker/iobroker-data/ 853M /opt/iobroker/iobroker-data/files 441M /opt/iobroker/iobroker-data/files/javascript.admin 409M /opt/iobroker/iobroker-data/files/javascript.admin/static 408M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 28M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.ce422ec2.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.1e6546bb.js.map 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_DE1964189-if00 *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyACM0 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 v18.20.6 /usr/bin/node v18.20.6 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 18.20.6-1nodesource1 Candidate: 18.20.6-1nodesource1 Version table: *** 18.20.6-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.20.5-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.4-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.3-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main armhf Packages 18.19.0+dfsg-6~deb12u1 500 500 http://security.debian.org bookworm-security/main armhf Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 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 Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: ██████ █████ ███ ██ ██████ ███████ ███████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ███████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ v18.20.6 is end-of-life. There are high chances of being vulnerable. Please upgrade it. *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberrypi raspberrypi (version: 6.0.9, hostname: raspberrypi , alive, uptime: 4073374) tinkerboard tinkerboard (version: 5.0.11, hostname: tinkerboard , alive, uptime: 1233824) Core adapters versions js-controller: 5.0.11 admin: 7.0.22 javascript: 8.7.6 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : tinkerboard - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : tinkerboard - enabled system.adapter.backitup.0 : backitup : tinkerboard - enabled system.adapter.daswetter.0 : daswetter : raspberrypi - enabled system.adapter.discovery.0 : discovery : tinkerboard - disabled system.adapter.email.0 : email : raspberrypi - disabled system.adapter.flot.0 : flot : tinkerboard - disabled system.adapter.fritzdect.0 : fritzdect : raspberrypi - disabled + system.adapter.geofency.0 : geofency : raspberrypi - enabled, port: 7999, bind: 0.0.0.0 + system.adapter.history.0 : history : tinkerboard - enabled system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.icons-icons8.0 : icons-icons8 : raspberrypi - disabled system.adapter.icons-material-png.0 : icons-material-png : tinkerboard - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : tinkerboard - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : tinkerboard - disabled system.adapter.info.0 : info : tinkerboard - disabled + system.adapter.iot.0 : iot : tinkerboard - enabled + system.adapter.javascript.0 : javascript : tinkerboard - enabled + system.adapter.linkeddevices.0 : linkeddevices : tinkerboard - enabled + system.adapter.mihome.0 : mihome : tinkerboard - enabled, port: 9898, bind: 0.0.0.0 system.adapter.modbus.0 : modbus : tinkerboard - disabled + system.adapter.mqtt.0 : mqtt : tinkerboard - enabled, port: 1886, bind: 0.0.0.0 system.adapter.radar2.0 : radar2 : tinkerboard - disabled system.adapter.rpi2.0 : rpi2 : raspberrypi - disabled + system.adapter.scenes.0 : scenes : tinkerboard - enabled + system.adapter.shelly.0 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : tinkerboard - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.smartmeter.3 : smartmeter : raspberrypi - enabled + system.adapter.smartmeter.4 : smartmeter : raspberrypi - enabled + system.adapter.socketio.0 : socketio : tinkerboard - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : tinkerboard - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sql.0 : sql : tinkerboard - enabled, port: 3306 + system.adapter.telegram.0 : telegram : tinkerboard - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : raspberrypi - enabled system.adapter.tinker.0 : tinker : tinkerboard - disabled system.adapter.tr-064.0 : tr-064 : tinkerboard - disabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled system.adapter.tuya.0 : tuya : raspberrypi - disabled system.adapter.vis-history.0 : vis-history : tinkerboard - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : tinkerboard - disabled system.adapter.vis-icontwo.0 : vis-icontwo : tinkerboard - disabled system.adapter.vis-metro.0 : vis-metro : tinkerboard - disabled system.adapter.vis-rgraph.0 : vis-rgraph : tinkerboard - disabled system.adapter.vis.0 : vis : tinkerboard - disabled + system.adapter.web.0 : web : tinkerboard - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : tinkerboard - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : tinkerboard - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.geofency.0 : geofency : raspberrypi - enabled, port: 7999, bind: 0.0.0.0 + system.adapter.mihome.0 : mihome : tinkerboard - enabled, port: 9898, bind: 0.0.0.0 + system.adapter.mqtt.0 : mqtt : tinkerboard - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : tinkerboard - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : tinkerboard - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : tinkerboard - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : tinkerboard - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sql.0 : sql : tinkerboard - enabled, port: 3306 + system.adapter.telegram.0 : telegram : tinkerboard - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : tinkerboard - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : tinkerboard - enabled, port: /dev/ttyACM0 ioBroker-Repositories Stable (default): http://download.iobroker.net/sources-dist.json Beta (latest) : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) Installed ioBroker-Adapters Used repository: Stable (default) Adapter "admin" : 7.7.19 , installed 7.0.22 [Updatable] Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "backitup" : 3.3.10 , installed 3.0.16 [Updatable] Adapter "discovery" : 5.0.0 , installed 4.5.0 [Updatable] Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "ical" : 1.17.0 , installed 1.15.0 [Updatable] Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 5.0.7 , installed 3.3.0 [Updatable] Adapter "javascript" : 8.9.2 , installed 8.7.6 [Updatable] Controller "js-controller": 7.0.7 , installed 5.0.11 [Updatable] Adapter "lgtv11" : 1.0.5 , installed 1.0.5 Adapter "linkeddevices": 1.5.5 , installed 1.5.5 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "modbus" : 6.3.2 , installed 6.2.3 [Updatable] Adapter "mqtt" : 6.1.4 , installed 5.2.0 [Updatable] Adapter "radar2" : 2.4.0 , installed 2.2.0 [Updatable] Adapter "scenes" : 3.2.3 , installed 3.2.1 [Updatable] Adapter "shelly" : 10.4.0 , installed 7.0.0 [Updatable] Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.0.3 [Updatable] Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "telegram" : 4.1.0 , installed 3.9.0 [Updatable] Adapter "tinker" : 1.3.9 , installed 1.3.2 [Updatable] Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-icontwo" : 1.18.0 , installed 1.5.0 [Updatable] Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "web" : 7.0.8 , installed 6.2.5 [Updatable] Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.1.5 , installed 1.0.3 [Updatable] Adapter "zigbee" : 3.1.5 , installed 1.10.3 [Updatable] Objects and States Please stand by - This may take a while Objects: 11911 States: 6830 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://deb.debian.org/debian bookworm-backports InRelease Hit:5 http://armbian.hosthatch.com/apt bookworm InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 127 *** 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:9001 0.0.0.0:* LISTEN 1001 28316 1845/iobroker.js-co tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 28336 1845/iobroker.js-co tcp 0 0 0.0.0.0:1888 0.0.0.0:* LISTEN 1001 29796 2029/io.shelly.1 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 28485 1999/io.mqtt.0 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 29601 2044/io.sonoff.0 tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 997 7549 557/systemd-resolve tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 997 7535 557/systemd-resolve tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 997 7547 557/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 8521 1055/sshd: /usr/sbi tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 7107 1/init tcp6 0 0 :::8084 :::* LISTEN 1001 29878 2114/io.socketio.0 tcp6 0 0 :::8087 :::* LISTEN 1001 29687 2092/io.simple-api. tcp6 0 0 :::8081 :::* LISTEN 1001 27606 1871/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 28587 2107/io.web.0 tcp6 0 0 :::1884 :::* LISTEN 1001 30808 1905/io.javascript. tcp6 0 0 :::5355 :::* LISTEN 997 7543 557/systemd-resolve tcp6 0 0 :::22 :::* LISTEN 0 8523 1055/sshd: /usr/sbi tcp6 0 0 :::111 :::* LISTEN 0 348 1/init udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 28519 2010/io.shelly.0 udp 0 0 127.0.0.54:53 0.0.0.0:* 997 7548 557/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 997 7546 557/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 7108 1/init udp 0 0 0.0.0.0:9898 0.0.0.0:* 1001 12474601 1984/io.mihome.0 udp 0 0 0.0.0.0:5355 0.0.0.0:* 997 7534 557/systemd-resolve udp 0 0 127.0.0.1:323 0.0.0.0:* 0 7861 1009/chronyd udp6 0 0 fe80::4baa:4d74:411:546 :::* 0 8782 813/NetworkManager udp6 0 0 :::111 :::* 0 7109 1/init udp6 0 0 :::5355 :::* 997 7542 557/systemd-resolve udp6 0 0 ::1:323 :::* 0 7862 1009/chronyd *** Log File - Last 25 Lines *** 2025-11-05 20:43:17.645 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:25.017 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:31.848 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:38.905 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:45.851 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:43:53.540 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:00.549 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:07.403 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:14.309 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:21.231 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:28.136 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:35.050 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:41.970 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:48.885 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:44:55.830 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:02.753 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:09.648 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:16.617 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:23.998 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:30.928 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:37.839 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:44.734 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:51.680 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:45:58.555 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2025-11-05 20:46:05.663 - warn: telegram.0 (10536) polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running============ Mark until here for C&P =============
Das ist doch kein Raspberry?
-
Das ist doch kein Raspberry?
-
@thomas-braun Tinkerboard - dachte es wäre „ähnlich“
Ähnlich... Du pappst auf einen Baby-Benz einen AMG-Aufkleber, weil die Karre ja auch ähnlich ist?
Nein, Armbian ist kein RaspberryOS. Das unterscheidet sich an wesentlichen Stellen.Da läuft ja auch noch ein js-controller 5
Controller "js-controller": 7.0.7 , installed 5.0.11 [Updatable]
Keine Ahnung was ich dir zu dem versumpften System raten soll...
-
Ich nutze den iobroker gefühlt seit 10‘Jahren - da ist die Struktur gewachsen und ich hatte einfach nicht mehr die Zeit alles neu zu machen.
Wäre es sinnvoll ohne Backup zu arbeiten und die Adapter etc. über Multihost rüber zu holen?
@ljsven sagte in admin startet nach Backup nicht mehr:
Ich nutze den iobroker gefühlt seit 10‘Jahren - da ist die Struktur gewachsen und ich hatte einfach nicht mehr die Zeit alles neu zu machen.
Wäre es sinnvoll ohne Backup zu arbeiten und die Adapter etc. über Multihost rüber zu holen?
Auch da müsstest du das neue System mit der alten ioBroker Version aufsetzen. Wenn dir das gelingt kannst auch gleich das Backup einspielen ...
Aber je nachdem was du hast könntest du vieles einfach von Hand umziehen.
Datenpunkte kann man exportieren und importieren, Skripte ebenfalls. Bei der VIS müsste halt alles andere vorbereitet sein, also alle notwendigen Datenpunkte wieder vorhanden sowie alle Bilder und Grafiken.
Und selbst da kannst du auch Widgets exportieren und importieren.Und dann setz doch dein neues System gleich mit Proxmox auf. Dein neues System ist dann virtuell - da kann man dann die ganze VM sichern oder Snapshots machen (so etwas wie Spielstand speichern/laden), das nimmt auch den Schrecken wenn mal ein größeres Upgrade nicht klappt.
Support us
667
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge