@homoran Ich habe schon den Proxmox server und auch den IOB neugestartet.
Die Fehler kommen immer wieder.
Was soll ich tun um die doppelten PIDs zu killen?
M
Best posts made by matrose65
-
RE: Adapter werden neu gestartetposted in Error/Bug
Latest posts made by matrose65
-
RE: Fehler: cannot call visUtilsposted in Error/Bug
Hallo da bin ich wieder. Etwas später aber das mit dem arbeiten hält eben auf.
Dier Fehler ist immer noch da, auch nach "iob upload all"
Er kommt aber den ganzen Tag nicht, erst wenn ich mich anmelde.
@ sigi234 was soll F12 anzeigen? Da bin ich überfragt
-
RE: Fehler: cannot call visUtilsposted in Error/Bug
Habe ich gerade gemacht. Melde mich gleich wieder
-
RE: Fehler: cannot call visUtilsposted in Error/Bug
Hallo
War kurz mal im Urlaub, aber es gab ja auch keine Antworten. Schade.
So jetzt ist alles aktuell, also Debian13 Trixie, aber der Fehler ist immer noch da.
Kann mir niemand helfen?
-
RE: Fehler: cannot call visUtilsposted in Error/Bug
Hast ja recht und ich habe darauf auch schon darauf gewartet. Mach ich gleich. Proxmox ist schon auf Trixie
Aber das hat sicher nichts mit dem Fehler zu tun
-
Fehler: cannot call visUtilsposted in Error/Bug
- Adaptername: host.iobroker
- Link zu Adapterrepository: www.github.com...
- Adapterversion:
- js-controller Version: 7.0.7
- Admin Version: 7.7.2
- Hardwaresystem: NUC / Proxmox
- Arbeitsspeicher: 12GB
- Festplattenart: SSD,
- Betriebssystem: Linux
- Nodejs-Version: 22.19.0
- NPM-Version: 10.9.3
- Installationsart: Skript
- Image, Docker genutzt:
- Ort, Name der Imagedatei:
Ich habe in unregelmäsigen Abständen fogenden Fehler:
host.iobroker 2025-09-27 11:21:31.169 error cannot call visUtils: vis.0 is not an object of type "meta"
Eigentlich funktioniert alles, aber es stört mich schon.
Habe auch schon das Forum durchsucht, aber nichts richtiges gefundenHier noch die Ausgabe von IOB Diag:
========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 6.14.11-2-pve Architecture: x86-64 OS is similar to: model name : Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 11:26:41 up 5 days, 18:33, 2 users, load average: 0.26, 0.29, 0.36 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** TIME AND TIMEZONES *** Local time: Sat 2025-09-27 11:26:41 CEST Universal time: Sat 2025-09-27 09:26:41 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': uwe HOME=/home/uwe GROUPS=uwe sudo users iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 12G 2.0G 10G 114K 752M 10G Swap: 536M 0B 536M Total: 13G 2.0G 10G Active iob-Instances: 23 12288 M total memory 1925 M used memory 2019 M active memory 517 M inactive memory 9644 M free memory 0 M buffer memory 717 M swap cache 512 M total swap 0 M used swap 512 M free swap *** top - Table Of Processes *** top - 11:26:41 up 5 days, 18:33, 2 users, load average: 0.26, 0.29, 0.36 Tasks: 47 total, 1 running, 46 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 12288.0 total, 9643.1 free, 1927.1 used, 717.9 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 10360.9 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--100--disk--0 ext4 32G 5.2G 25G 18% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 16G 0 16G 0% /dev/tty tmpfs tmpfs 16G 0 16G 0% /dev/shm tmpfs tmpfs 6.3G 108K 6.3G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--100--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 657M /var/ 384M /var/cache 381M /var/cache/apt 305M /var/cache/apt/archives 147M /var/lib Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 31.1M in the file system. /opt/iobroker/backups: 124M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 611M /opt/iobroker/iobroker-data/ 389M /opt/iobroker/iobroker-data/files 175M /opt/iobroker/iobroker-data/backup-objects 99M /opt/iobroker/iobroker-data/files/vis-2 57M /opt/iobroker/iobroker-data/files/vis-2/widgets The five largest files in iobroker-data are: 29M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 24M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.c9369f6c.js.map 19M /opt/iobroker/iobroker-data/states.jsonl 9.8M /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json 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' *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp 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 amd64 Packages 100 /var/lib/dpkg/status 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://security.debian.org bookworm-security/main amd64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main amd64 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: iobroker iobroker (version: 7.0.7, hostname: iobroker , alive, uptime: 267173) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 8.9.2 nodejs modules from github: 3 +-- iobroker.brightsky@0.2.4 (git+ssh://git@github.com/ticaki/ioBroker.brightsky.git#0dffc96a42cbb1a5d3b601099814c5e07ae7d084) +-- iobroker.netatmo-crawler@1.0.0 (git+ssh://git@github.com/Bart1909/ioBroker.netatmo-crawler.git#18110bf428b3021c9d8e6f23a3546218b7b75a69) +-- iobroker.pirate-weather@0.4.1 (git+ssh://git@github.com/ticaki/ioBroker.pirate-weather.git#b56ebc883330b000a928285d446764661fde97ed) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.ankersolix2.0 : ankersolix2 : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.brightsky.0 : brightsky : iobroker - enabled system.adapter.daswetter.0 : daswetter : iobroker - enabled system.adapter.dwd.0 : dwd : iobroker - enabled + system.adapter.fullybrowser.0 : fullybrowser : iobroker - enabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 system.adapter.ical.0 : ical : iobroker - enabled system.adapter.ical.1 : ical : iobroker - enabled system.adapter.ical.2 : ical : iobroker - enabled system.adapter.ical.3 : ical : iobroker - enabled system.adapter.icons-material-png.0 : icons-material-png : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.netatmo-crawler.0 : netatmo-crawler : iobroker - enabled + system.adapter.pirate-weather.0 : pirate-weather : iobroker - enabled + system.adapter.proxmox.0 : proxmox : iobroker - enabled system.adapter.roborock.0 : roborock : iobroker - disabled + system.adapter.scenes.0 : scenes : iobroker - enabled + system.adapter.shelly.1 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.2 : shelly : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sonos.0 : sonos : iobroker - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled + system.adapter.tr-064.0 : tr-064 : iobroker - enabled + system.adapter.tuya.0 : tuya : iobroker - enabled + system.adapter.unifi.0 : unifi : iobroker - enabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : iobroker - disabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : iobroker - disabled system.adapter.vis-2-widgets-inventwo.0 : vis-2-widgets-inventwo: iobroker - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: iobroker - disabled + system.adapter.vis-2.0 : vis-2 : iobroker - enabled system.adapter.vis-icontwo.0 : vis-icontwo : iobroker - disabled + system.adapter.vis-inventwo.0 : vis-inventwo : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : iobroker - enabled + system.adapter.zigbee.0 : zigbee : iobroker - enabled, port: tcp://192.168.1.21:6638 + 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.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.shelly.1 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.2 : shelly : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : iobroker - enabled, port: tcp://192.168.1.21:6638 ioBroker-Repositories ┌─────────┬──────────┬──────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼──────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://iobroker.live/repo/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://iobroker.live/repo/sources-dist-latest.json' │ false │ └─────────┴──────────┴──────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.7.2 , installed 7.7.2 Adapter "ankersolix2" : 2.3.0 , installed 2.3.0 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "brightsky" : 0.2.4 , installed 0.2.4 Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "energiefluss-erweitert": 0.7.7, installed 0.7.8 Adapter "fullybrowser" : 3.1.2 , installed 3.1.2 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "ical" : 1.16.2 , installed 1.16.2 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "netatmo-crawler": 1.0.0 , installed 1.0.0 Adapter "pirate-weather": 0.4.1 , installed 0.4.1 Adapter "proxmox" : 2.4.0 , installed 2.4.0 Adapter "reolink" : 1.2.3 , installed 1.2.3 Adapter "roborock" : 0.6.18 , installed 0.6.18 Adapter "scenes" : 3.2.3 , installed 3.2.3 Adapter "shelly" : 10.2.0 , installed 10.2.0 Adapter "socketio" : 6.7.1 , installed 7.0.8 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.4 , installed 2.13.4 Adapter "vis-2-widgets-energy": 1.0.2, installed 1.0.2 Adapter "vis-2-widgets-gauges": 2.0.1, installed 2.0.1 Adapter "vis-2-widgets-inventwo": 0.2.2, installed 0.2.2 Adapter "vis-2-widgets-material": 1.4.10, installed 1.4.10 Adapter "vis-2-widgets-weather-and-heating": 1.1.3, installed 1.1.3 Adapter "vis-icontwo" : 1.18.0 , installed 1.18.0 Adapter "vis-inventwo" : 3.3.5 , installed 3.3.5 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "worx" : 3.2.7 , installed 3.2.7 Adapter "ws" : 2.6.2 , installed 3.0.19 Adapter "zigbee" : 3.0.5 , installed 3.0.5 Objects and States Please stand by - This may take a while Objects: 9527 States: 8047 *** 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 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending Updates: 65 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 14068 317/master tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 4401886 9314/iobroker.js-co tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 4401881 9314/iobroker.js-co tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 11102 1/init tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 4403095 9739/io.shelly.1 tcp 0 0 192.168.1.16:2001 0.0.0.0:* LISTEN 1001 4405382 9628/io.hm-rpc.0 tcp6 0 0 ::1:25 :::* LISTEN 0 14069 317/master tcp6 0 0 :::8081 :::* LISTEN 1001 4402043 9424/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 4405908 9989/io.web.0 tcp6 0 0 :::111 :::* LISTEN 0 11104 1/init tcp6 0 0 :::22 :::* LISTEN 0 13019 1/init tcp6 0 0 :::3010 :::* LISTEN 1001 4403914 9576/io.fullybrowse tcp6 0 0 :::3500 :::* LISTEN 1001 4404868 9791/io.sonos.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 4405919 10004/io.wled.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 4404849 9765/io.shelly.2 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 4405727 9881/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 4405728 9881/io.tuya.0 udp 0 0 0.0.0.0:111 0.0.0.0:* 0 11103 1/init udp6 0 0 :::111 :::* 0 11105 1/init *** Log File - Last 25 Lines *** 2025-09-27 11:00:21.636 - info: netatmo-crawler.0 (19387) Getting data for stationid:70:ee:50:2e:9d:b8 2025-09-27 11:00:26.404 - info: netatmo-crawler.0 (19387) Getting data for stationid:70:ee:50:7f:c8:b6 2025-09-27 11:00:33.693 - info: netatmo-crawler.0 (19387) Terminated (NO_ERROR): Everything done. Going to terminate till next schedule 2025-09-27 11:00:34.203 - info: host.iobroker instance system.adapter.netatmo-crawler.0 having pid 19387 terminated with code 0 (NO_ERROR) 2025-09-27 11:03:08.144 - info: fullybrowser.0 (9576) 🗸 192.168.1.144: Command screenOff successfully set to true 2025-09-27 11:05:20.538 - info: fullybrowser.0 (9576) 🗸 192.168.1.144: Command screenOn successfully set to true 2025-09-27 11:07:08.670 - info: zigbee.0 (9925) Device '0x14b457fffe732925' announced itself 2025-09-27 11:09:53.106 - info: fullybrowser.0 (9576) 🗸 192.168.1.144: Command screenOff successfully set to true 2025-09-27 11:09:58.009 - info: host.iobroker instance system.adapter.daswetter.0 in version "3.2.3" started with pid 19402 2025-09-27 11:09:58.689 - info: daswetter.0 (19402) starting. Version 3.2.3 in /opt/iobroker/node_modules/iobroker.daswetter, node: v22.19.0, js-controller: 7.0.7 2025-09-27 11:10:00.345 - info: daswetter.0 (19402) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment 2025-09-27 11:10:00.849 - info: daswetter.0 (19402) cleaned everything up... 2025-09-27 11:10:00.858 - info: host.iobroker instance system.adapter.daswetter.0 having pid 19402 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-09-27 11:12:28.362 - info: fullybrowser.0 (9576) 🗸 192.168.1.144: Command screenOn successfully set to true 2025-09-27 11:14:06.015 - info: host.iobroker instance system.adapter.dwd.0 in version "2.8.5" started with pid 19417 2025-09-27 11:14:06.728 - info: dwd.0 (19417) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v22.19.0, js-controller: 7.0.7 2025-09-27 11:14:07.077 - info: dwd.0 (19417) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-09-27 11:14:07.589 - info: host.iobroker instance system.adapter.dwd.0 having pid 19417 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-09-27 11:15:37.732 - info: fullybrowser.0 (9576) 🗸 192.168.1.144: Command screenOn successfully set to true 2025-09-27 11:16:19.852 - info: admin.0 (9424) ==> Connected system.user.admin from ::ffff:192.168.1.121 2025-09-27 11:16:19.853 - info: admin.0 (9424) <== Disconnect system.user.admin from ::ffff:192.168.1.121 admin 2025-09-27 11:16:21.846 - info: admin.0 (9424) ==> Connected system.user.admin from ::ffff:192.168.1.121 2025-09-27 11:20:04.920 - info: fullybrowser.0 (9576) 🗸 192.168.1.144: Command screenOff successfully set to true 2025-09-27 11:21:31.169 - error: host.iobroker cannot call visUtils: vis.0 is not an object of type "meta" 2025-09-27 11:26:17.110 - info: web.0 (9989) <== Disconnect system.user.admin from ::ffff:192.168.1.144============ Mark until here for C&P =============
iob diag has finished.
-
RE: Adapter Worx Landroid v3.x.xposted in Entwicklung
Ich wurde auch gesperrt. Dann habe ich den Adapter gestoppt und über das Wochenende die App nicht aufgerufen.
Am Montag ist der Lemmi nach Zeitplan gefahren.
Nachmittags wollte ich nur schauen, ob er auch am Nachmittag seine Runden gedreht hat.
Bin in die App gekommen, alles wurde angezeigt. Ein Aufruf der Aktivitäten und schon wieder gesperrt.
Jetzt weiß ich nicht was er macht, da der Garten 15km weg ist. Das ist ganz großer Mist -
RE: Neuer Adapter für Roborock-Staubsaugerposted in ioBroker Allgemein
Hallo
Ich habe einen Roborock Q7 Max. Das System ist auf dem neusten Stand.
Und der Staubsauer kann auch über meine Vis gesteuert werden.aber:
Ich habe das Problem wie es hier und in Github beschrieben ist.
Mit der Version 0.6.18 bekomme ich im Log alle 3h den Fehler:2025-03-05 07:59:55.564 - error: roborock.0 (32234) Failed to get home details: Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running at healthCheck (node:dgram:929:11) at Socket.bind (node:dgram:249:3) at /opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:213:11 at new Promise () at localConnector.getLocalDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:185:10) at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:197:56) at async /opt/iobroker/node_modules/iobroker.roborock/main.js:77:4Wenn ich dann wie hier angegeben die Version 0.6.19 herunterlade und installiere funktioniert erstmal alles,
aber nach kurzer Zeit oder wenn ich links in der Leiste den Tab aufrufe stürzt, der Adapter mit Fehlern ab.
Schon beim Aufruf des Tab wird die Karte nicht angezeigt und auch der Name des Sauger´s fehlt2025-03-02 20:36:58.794 - info: roborock.0 (25004) Starting adapter finished. Let's go!!!!!!! 2025-03-02 20:37:04.008 - error: roborock.0 (25004) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-03-02 20:37:04.008 - error: roborock.0 (25004) unhandled promise rejection: Cannot read properties of undefined (reading 'productId') 2025-03-02 20:37:04.009 - error: roborock.0 (25004) TypeError: Cannot read properties of undefined (reading 'productId') at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43) at requests_handler.sendRequest (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:712:17) at async requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:559:17) 2025-03-02 20:37:04.009 - error: roborock.0 (25004) Cannot read properties of undefined (reading 'productId') 2025-03-02 20:37:04.011 - info: roborock.0 (25004) terminating 2025-03-02 20:37:04.011 - warn: roborock.0 (25004) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-03-02 20:37:04.012 - error: roborock.0 (25004) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-03-02 20:37:04.013 - error: roborock.0 (25004) unhandled promise rejection: Cannot read properties of undefined (reading 'productId') 2025-03-02 20:37:04.013 - error: roborock.0 (25004) TypeError: Cannot read properties of undefined (reading 'productId') at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43) at requests_handler.sendRequest (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:712:17) at async requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:562:26) 2025-03-02 20:37:04.013 - error: roborock.0 (25004) Cannot read properties of undefined (reading 'productId') 2025-03-02 20:37:04.013 - error: roborock.0 (25004) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-03-02 20:37:04.013 - error: roborock.0 (25004) unhandled promise rejection: Cannot read properties of undefined (reading 'productId') 2025-03-02 20:37:04.013 - error: roborock.0 (25004) TypeError: Cannot read properties of undefined (reading 'productId') at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43) at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:601:18) 2025-03-02 20:37:04.013 - error: roborock.0 (25004) Cannot read properties of undefined (reading 'productId') 2025-03-02 20:37:04.512 - info: roborock.0 (25004) terminating 2025-03-02 20:37:04.537 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-03-02 20:37:04.537 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled 2025-03-02 20:37:17.463 - info: host.iobroker "system.adapter.roborock.0" disabled 2025-03-02 20:37:35.764 - error: roborock.0 (25051) adapter disabled 2025-03-02 20:37:35.848 - warn: roborock.0 (25051) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason 2025-03-02 20:37:36.373 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND) 2025-03-02 20:37:36.373 - info: host.iobroker Do not restart adapter system.adapter.roborock.0 because disabled or deleted -
RE: IOBroker stürzt ab und alle Adapter starten neuposted in Error/Bug
Hallo zusammen
Am Freitag habe ich es nicht mehr ausgehalten mit den ganzen Abstürzen. Ich hatte noch einen W-Lan ZigBee Stick und habe jetzt den IoBroker als Container installiert. (Danke an alle, die diese super Anleitungen schreiben)
Habe Freitag angefangen und den Samstag Mittag war alles neu und zwar ohne ein Backup.
Seitdem läuft der IOB ohne Abstürze.Danke an alle die hier geholfen haben
-
RE: IOBroker stürzt ab und alle Adapter starten neuposted in Error/Bug
Ja habe ich gestern gemacht, auch kein erfolg
-
RE: IOBroker stürzt ab und alle Adapter starten neuposted in Error/Bug
@chaot
Danke ich bin für jede Idee offen. Ich kann das alles auch noch verkleinern.
IOB verbraucht aktuell 2,59Gb und Rasp 1,0 GbWas mir noch aufgefallen ist, als ich vorhin das Log für heute aufgerufen habe wurde der Bildschirm gleich grau und wieder wurden die Adapter neu gestartet
