[geklärt] History Adapter viele Fehlermeldungen
-
@david-g said in History Adapter viele Fehlermeldungen:
EDIT
Ist dein System aktuell?Ja über den Terminal konnte ich den raspberry erreichen. Dort habe ich auch mal einen update gemacht. Daher kommt es nicht. Habe jetzt die history Instanz ausgeschalten.
Jetzt sieht das "System" ruhiger aus.
Kann man die Kategorie noch ändern?2025-02-22 12:36:24.681 - [33mwarn[39m: tuya.0 (32571) bfab36eff4be49952162kd: Error on Reconnect (7): connect EHOSTUNREACH 192.168.178.132:6668 2025-02-22 12:45:00.048 - [32minfo[39m: javascript.0 (32228) script.js.Skript_Shelly_Verbrauch: Shelly Verbrauch: Verbrauchswerte aktualisiert: 1 | Reboots korrigiert: 0 | Unveränderte Werte: 6 2025-02-22 12:45:57.647 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] reconnected. Old secret 1740224139338_5931. New secret 1740224757647_9213 2025-02-22 12:45:57.658 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.L1L2L3" 2025-02-22 12:45:57.668 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.NotAus" 2025-02-22 12:45:57.674 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.WaitSekunden" 2025-02-22 12:45:57.682 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.MaxPower" 2025-02-22 12:45:57.858 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:45:57.867 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:45:57.875 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:45:57.883 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:46:07.360 - [33mwarn[39m: mqtt.0 (32415) Client [SOYO_3b2107] Message 611 deleted after 11 retries 2025-02-22 12:46:12.474 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] reconnected. Old secret 1740224757647_9213. New secret 1740224772473_4009 2025-02-22 12:46:12.484 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.L1L2L3" 2025-02-22 12:46:12.564 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.NotAus" 2025-02-22 12:46:12.575 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.WaitSekunden" 2025-02-22 12:46:12.582 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.MaxPower" 2025-02-22 12:46:12.685 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:46:12.764 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:46:12.776 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:46:12.782 - [32minfo[39m: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe -
@david-g said in History Adapter viele Fehlermeldungen:
hilft evtl
Hab ich versucht. Dann kommt folgendes:
*** iob diag is starting up, please wait ***
iob diag needs to be updated. Please execute 'iobroker fix' first. -
@peter-c sagte in History Adapter viele Fehlermeldungen:
Hab ich versucht. Dann kommt folgendes:
Dann ist dein System nicht auf Stand.
-
@thomas-braun said in History Adapter viele Fehlermeldungen:
Dann ist dein System nicht auf Stand.
Hier die Diagnose
========== Start marking the full check here =========== ```bash Script v.2025-02-02 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Raspbian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 OS is similar to: debian Model : Raspberry Pi 4 Model B Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : 32 bit Systemuptime and Load: 12:59:07 up 1:14, 2 users, load average: 0.65, 0.68, 8.43 CPU threads: 4 *** LIFE CYCLE STATUS *** Unknown release codenamed 'bullseye'. Please check yourself if the Operating System is actively maintained. *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: ~ Under-voltage has occurred *** TIME AND TIMEZONES *** Local time: Sat 2025-02-22 12:59:07 CET Universal time: Sat 2025-02-22 11:59:07 UTC RTC time: n/a 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': pt HOME=/home/pt GROUPS=pt adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi 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 Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 942M 2.5G 0.0K 374M 2.8G Swap: 99M 28M 71M Total: 3.9G 970M 2.5G Active iob-Instances: 20 3794 M total memory 942 M used memory 980 M active memory 208 M inactive memory 2477 M free memory 48 M buffer memory 326 M swap cache 99 M total swap 28 M used swap 71 M free swap *** top - Table Of Processes *** top - 12:59:08 up 1:14, 2 users, load average: 0.65, 0.68, 8.43 Tasks: 186 total, 1 running, 185 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 4.2 sy, 0.0 ni, 95.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3794.3 total, 2476.6 free, 942.6 used, 375.1 buff/cache MiB Swap: 100.0 total, 71.5 free, 28.5 used. 2776.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 /dev/root ext4 29G 13G 16G 45% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 1.2M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 51M 205M 20% /boot tmpfs tmpfs 380M 20K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Feb 22 11:45:01 2025] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.7G /var/ 969M /var/log 961M /var/log/journal/061ea1674ff8454f9e4d5c7dfa8e6e06 961M /var/log/journal 458M /var/cache Archived and active journals take up 960.2M in the file system. /opt/iobroker/backups: 83M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 3.8G /opt/iobroker/iobroker-data/ 2.9G /opt/iobroker/iobroker-data/history 927M /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.js.map 13M /opt/iobroker/iobroker-data/objects.jsonl 9.3M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** NodeJS-Installation *** /usr/bin/nodejs v20.18.3 /usr/bin/node v20.18.3 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.30.0 nodejs: Installed: 20.18.3-1nodesource1 Candidate: 20.18.3-1nodesource1 Version table: *** 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages 12.22.12~dfsg-1~deb11u5 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 7.0.6, hostname: iobroker , alive, uptime: 1610) Core adapters versions js-controller: 7.0.6 admin: 7.4.10 javascript: 8.8.3 nodejs modules from github: 1 `-- tibber-api@5.1.9 (git+ssh://git@github.com/bisand/tibber-api.git#c288a93c2f4d4989dc8214f9e3549477fd1b5acd) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled system.adapter.bmw.0 : bmw : iobroker - disabled system.adapter.cloud.0 : cloud : iobroker - disabled + system.adapter.device-reminder.0 : device-reminder : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.energiefluss.0 : energiefluss : iobroker - enabled system.adapter.flot.0 : flot : iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled system.adapter.history.0 : history : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.meross.0 : meross : iobroker - enabled + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 192.168.178.94 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.ping.0 : ping : iobroker - enabled system.adapter.pushover.0 : pushover : iobroker - disabled + system.adapter.pvforecast.0 : pvforecast : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : iobroker - disabled + system.adapter.tibberlink.0 : tibberlink : iobroker - enabled + system.adapter.tuya.0 : tuya : iobroker - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : iobroker - enabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : iobroker - disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 192.168.178.94 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - 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 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Instances Used repository: stable Adapter "admin" : 7.4.10 , installed 7.4.10 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "backitup" : 3.0.31 , installed 3.0.31 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "email" : 1.3.1 , installed 1.3.1 Adapter "energiefluss" : 3.6.2 , installed 3.6.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fritzdect" : 2.5.11 , installed 2.5.11 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "node-red" : 5.2.1 , installed 5.2.1 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "pushover" : 4.1.0 , installed 4.1.0 Adapter "pvforecast" : 4.1.0 , installed 4.1.0 Adapter "shelly" : 8.5.1 , installed 8.5.1 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tibberlink" : 4.2.3 , installed 4.2.3 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 4957 States: 4074 *** OS-Repositories and Updates *** Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Hit:3 https://deb.nodesource.com/node_20.x nodistro 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:22 0.0.0.0:* LISTEN 0 1909 561/sshd: /usr/sbin tcp 0 0 192.168.178.94:1883 0.0.0.0:* LISTEN 1001 89012 32415/io.mqtt.0 tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 86010 32217/node-red tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 89868 32385/io.shelly.0 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 87431 32050/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 85718 32050/iobroker.js-c tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 15383 532/cupsd tcp6 0 0 :::22 :::* LISTEN 0 15079 561/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 87566 32168/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 92298 32644/io.web.0 tcp6 0 0 ::1:631 :::* LISTEN 0 15382 532/cupsd udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 92237 32571/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 92238 32571/io.tuya.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 1823 398/avahi-daemon: r udp 0 0 0.0.0.0:52477 0.0.0.0:* 108 1825 398/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14048 476/dhcpcd udp6 0 0 :::47601 :::* 108 1826 398/avahi-daemon: r udp6 0 0 :::546 :::* 0 14060 476/dhcpcd udp6 0 0 :::5353 :::* 108 1824 398/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-02-22 12:54:58.082 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:54:58.088 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:54:58.095 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:54:58.105 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:55:11.466 - warn: mqtt.0 (32415) Client [SOYO_3b2107] Message 519 deleted after 11 retries 2025-02-22 12:55:12.580 - info: mqtt.0 (32415) Client [SOYO_3b2107] reconnected. Old secret 1740225297871_6311. New secret 1740225312579_2546 2025-02-22 12:55:12.596 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.L1L2L3" 2025-02-22 12:55:12.609 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.NotAus" 2025-02-22 12:55:12.620 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.WaitSekunden" 2025-02-22 12:55:12.637 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.MaxPower" 2025-02-22 12:55:12.796 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:55:12.810 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:55:12.820 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:55:12.838 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:59:57.435 - info: mqtt.0 (32415) Client [SOYO_3b2107] connection closed: Error: read ECONNRESET 2025-02-22 12:59:57.908 - info: mqtt.0 (32415) Client [SOYO_3b2107] connected with secret 1740225597907_7518 2025-02-22 12:59:57.918 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.L1L2L3" 2025-02-22 12:59:57.927 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.NotAus" 2025-02-22 12:59:57.933 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.WaitSekunden" 2025-02-22 12:59:57.941 - info: mqtt.0 (32415) Client [SOYO_3b2107] subscribes on "mqtt.0.Soyosource.SOYO_3b2107.MaxPower" 2025-02-22 12:59:58.118 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:59:58.128 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:59:58.133 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 12:59:58.142 - info: mqtt.0 (32415) Client [SOYO_3b2107] publishOnSubscribe 2025-02-22 13:00:00.096 - info: javascript.0 (32228) script.js.Skript_Shelly_Verbrauch: Shelly Verbrauch: Verbrauchswerte aktualisiert: 1 | Reboots korrigiert: 0 | Unveränderte Werte: 6============ Mark until here for C&P =============
-
@peter-c sagte in History Adapter viele Fehlermeldungen:
bullseye
Aktuell ist Bookworm.
Installier es neu, diesmal in der 64Bit-Lite-Version.
ioBroker-Backup einspielen, fertig. -
@thomas-braun said in History Adapter viele Fehlermeldungen:
Aktuell ist Bookworm.
Installier es neu, diesmal in der 64Bit-Lite-Version.wie installiere ich bookworm?
-
-
Das ganze System neu aufsetzen?
-
Ja natürlich. Komplett von Grund auf NEU.
-
@thomas-braun said in History Adapter viele Fehlermeldungen:
Komplett von Grund auf NEU.
Ohne nach der Ursache zu suchen?
-
Was willst du auf dem toten Pferd denn noch suchen?
Du musst die Kiste eh neuaufsetzen, Fehler hin oder her. -
@thomas-braun said in History Adapter viele Fehlermeldungen:
toten Pferd
Sorry das ich das nachfrage. Warum ist meine Installation auf einmal ein totes Pferd?
-
Weil Debian 11 'Bullseye' im Upstream das EndOfLife erreicht hat.
Weil du da im Userland 32Bit fährst.
Weil du da so einen Quark wie CUPS aktiv hast.
Weil du da komische Fehlerbilder hast. -
@thomas-braun sagte in History Adapter viele Fehlermeldungen:
Weil du da so einen Quark wie CUPS aktiv hast
Warum Quark.
Hab es auch auf einem anderen iobroker System und finde ess sehr praktisch. -
@thomas-braun said in History Adapter viele Fehlermeldungen:
Weil du da so einen Quark wie CUPS aktiv hast.
Ich nutze keine Printfunktion über den IOB
-
@peter-c sagte in History Adapter viele Fehlermeldungen:
Under-voltage has occurred
da reicht wohl das Netzteil nicht.
wo liegen deine History Daten?
@peter-c sagte in History Adapter viele Fehlermeldungen:
/ /dev/mmcblk0p2 ext4 rw,noatime
-
@homoran said in History Adapter viele Fehlermeldungen:
wo liegen deine History Daten?
so weit ich weiß auf der SD Karte.
Das Netzteil hatte ich nicht geändert.
-
@peter-c sagte in History Adapter viele Fehlermeldungen:
Das Netzteil hatte ich nicht geändert.
dann ist es wohl von Anfang an zu schwach gewesen
-
@homoran said in History Adapter viele Fehlermeldungen:
Anfang an zu schwach gewesen
Kann es sein, dass eine Netzunterbrechnung den Eintrag auslöst?
Das ist vorgekommen.
Soll ich den History adapter neu aufsetzen oder wirklich das System komplett neu aufsetzen?
-
@peter-c sagte in History Adapter viele Fehlermeldungen:
das System komplett neu aufsetzen?
alles andere ergibt keinen Sinn!
Nimm eine neue Karte, darauf bookworm lite 64bit, dann iob installieren und neuestes Backup zurückspielen.
fertig!
