IOB keine Objekte für KNX
-
ich bin nur laienhafter Nutzer von IOB
und habe ca 2 Jahre eine Raspi 3 betrieben mit dem ich KNX geräte Shellys und sonoffsteckdosen
visualisiert habe. Leide bin ich ein bischen schlampig und hab es mit den Updates der Instanzen nicht so genau
genommen habe. Ein funktionierens Gesamtubdate war kaum möglich.
Jetzt habe ich mir einen Raspi 5 zugelegt in die erforderlichen Instanzen installiert die auch "grün" gekennzeichnit sind.
Leider kann ich dür die KNX Geräte nicht die Objektliste mit Daten sehen.
Habe u.a. nachfolgende Version installiert:
admin V7.1.5
Node 20.18.1
NPM 10.8.2
KNX läuft unter ETS 5
die Instanz KNX läuft auch
leider keine Objektlist
Wer kann mir helfen? -
@civitas2021 sagte in IOB keine Objekte für KNX:
Wer kann mir helfen?
Möglicherweise die komplette Ausgabe von
iob diag.für den Raspi im Moment bitte diese drei Befehle ausführen:
curl https://raw.githubusercontent.com/Grothesk242/ioBroker/refs/heads/Raspbian/diag.sh > iob_diag.sh chmod 744 iob_diag.sh ./iob_diag.sh -
@homoran habe die drei Befehle im Raspi ausgeführt , sind durchgelauf
nach Aufruf IOB der Objektliste KNX kein Erfolg
was kann ich noch tun -
@civitas2021 sagte in IOB keine Objekte für KNX:
was kann ich noch tun
die Ausgabe zeigen!
die ändert ja auch nichts -
@homoran
iStatic hostname: raspberry
Icon name: computer
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.6.62+rpt-rpi-2712
Architecture: arm64Installation: native
Kernel: aarch64
Userland: 64 bit
Timezone: Europe/Berlin (CET, +0100)
User-ID: 1000
Display-Server: false
Boot Target: graphical.targetPending OS-Updates: 91
Pending iob updates: 6Nodejs-Installation:
/usr/bin/nodejs v20.18.1
/usr/bin/node v20.18.1
/usr/bin/npm 10.8.2
/usr/bin/npx 10.8.2
/usr/bin/corepack 0.29.4Recommended versions are nodejs 20.18.1 and npm 10.8.2
nodeJS installation is correctMEMORY:
total used free shared buff/cache available
Mem: 4.2G 1.3G 2.1G 29M 993M 3.0G
Swap: 536M 0B 536M
Total: 4.8G 1.3G 2.6GActive iob-Instances: 13
Upgrade policy: noneioBroker Core: js-controller 7.0.3
admin 7.1.5ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonlStatus admin and web instance:
- system.adapter.admin.0 : admin : raspberry - enabled, port: 8081, bind: 0.0.0.0, run as: admin
- system.adapter.web.0 : web : raspberry - enabled, port: 8082, bind: 0.0.0.0, run as: admin
Objects: 695
States: 540Size of iob-Database:
16M /opt/iobroker/iobroker-data/objects.jsonl
344K /opt/iobroker/iobroker-data/states.jsonl
st diese Ausgabe ausreichend? -
@civitas2021 das ist leider nicht die Langfassung von iob diag
-
@homoran
ist das jetzt die erforderliche Ausgabe ?** BASE SYSTEM *** Static hostname: raspberry Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.62+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 13:43:40 up 1:21, 4 users, load average: 0.00, 0.00, 0.00 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Mon 2025-01-13 13:43:40 CET Universal time: Mon 2025-01-13 12:43:40 UTC RTC time: Mon 2025-01-13 12:43:40 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 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 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: 4.2G 1.3G 2.1G 29M 997M 3.0G Swap: 536M 0B 536M Total: 4.8G 1.3G 2.6G Active iob-Instances: 13 4045 M total memory 1193 M used memory 1301 M active memory 515 M inactive memory 1993 M free memory 86 M buffer memory 864 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 13:43:41 up 1:21, 4 users, load average: 0.00, 0.00, 0.00 Tasks: 211 total, 1 running, 210 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 50.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 4045.0 total, 1991.9 free, 1194.6 used, 951.4 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 2850.4 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 2.0G 0 2.0G 0% /dev tmpfs tmpfs 405M 6.2M 399M 2% /run /dev/mmcblk0p2 ext4 57G 8.2G 46G 16% / tmpfs tmpfs 2.0G 528K 2.0G 1% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 67M 444M 14% /boot/firmware tmpfs tmpfs 405M 192K 405M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon Jan 13 12:22:04 2025] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave smsc95xx.macaddr=2C:CF:67:98:7F:11 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=a4ac4bbd-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Mon Jan 13 12:22:06 2025] EXT4-fs (mmcblk0p2): mounted filesystem a36be96c-66be-4487-a7a6-0481bca99d89 ro with ordered data mode. Quota mode: none. [Mon Jan 13 12:22:08 2025] EXT4-fs (mmcblk0p2): re-mounted a36be96c-66be-4487-a7a6-0481bca99d89 r/w. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/run/user/1000/doc portal fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.3G /var/ 408M /var/cache 401M /var/cache/apt 287M /var/cache/apt/archives 207M /var/lib Archived and active journals take up 161.1M in the file system. /opt/iobroker/backups: 39M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 794M /opt/iobroker/iobroker-data/ 737M /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 16M /opt/iobroker/iobroker-data/objects.jsonl 12M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.js 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map 8.6M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/310.89a60ae1.chunk.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': No Devices found 'by-id' *** NodeJS-Installation *** /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 20.18.1-1nodesource1 Candidate: 20.18.1-1nodesource1 Version table: *** 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 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: raspberry raspberry (version: 7.0.3, hostname: raspberry , alive, uptime: 4873) Core adapters versions js-controller: 7.0.3 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberry - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : raspberry - enabled system.adapter.cloud.0 : cloud : raspberry - disabled + system.adapter.discovery.0 : discovery : raspberry - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberry - enabled + system.adapter.history.0 : history : raspberry - enabled + system.adapter.javascript.0 : javascript : raspberry - enabled + system.adapter.knx.0 : knx : raspberry - enabled, bind: 192.168.178.38 + system.adapter.mqtt.0 : mqtt : raspberry - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberry - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberry - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.systeminfo.0 : systeminfo : raspberry - enabled system.adapter.vis.0 : vis : raspberry - enabled + system.adapter.web.0 : web : raspberry - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberry - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : raspberry - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberry - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberry - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberry - 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.1.5 [Updatable] Adapter "backitup" : 3.0.31 , installed 3.0.25 [Updatable] Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 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.3 [Updatable] Adapter "knx" : 2.0.28 , installed 2.0.28 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "mqtt-client" : 2.1.0 , installed 2.1.0 Adapter "shelly" : 8.5.1 , installed 8.2.1 [Updatable] Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.6.1 [Updatable] Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "systeminfo" : 1.2.0 , installed 1.2.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.5.11 [Updatable] Objects and States Please stand by - This may take a while Objects: 695 States: 540 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 91 *** 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 5962 757/sshd: /usr/sbin tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 10995 2350/io.mqtt.0 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 13380 2335/io.sonoff.0 tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 12791 2178/io.shelly.0 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 3917 742/cupsd tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 6654 743/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 6659 743/iobroker.js-con tcp6 0 0 ::1:631 :::* LISTEN 0 3916 742/cupsd tcp6 0 0 :::22 :::* LISTEN 0 5964 757/sshd: /usr/sbin tcp6 0 0 :::8082 :::* LISTEN 1001 13439 2399/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 8939 1949/io.admin.0 udp 0 0 192.168.178.38:51105 0.0.0.0:* 1001 11076 2163/io.knx.0 udp 0 0 192.168.178.38:55203 0.0.0.0:* 1001 10859 2163/io.knx.0 udp 0 0 192.168.178.38:42926 0.0.0.0:* 1001 12917 2163/io.knx.0 udp 0 0 192.168.178.38:49101 0.0.0.0:* 1001 14471 2163/io.knx.0 udp 0 0 192.168.178.38:47064 0.0.0.0:* 1001 12931 2163/io.knx.0 udp 0 0 192.168.178.38:41100 0.0.0.0:* 1001 18683 2163/io.knx.0 udp 0 0 192.168.178.38:37104 0.0.0.0:* 1001 12922 2163/io.knx.0 udp 0 0 192.168.178.38:45379 0.0.0.0:* 1001 14447 2163/io.knx.0 udp 0 0 192.168.178.38:43379 0.0.0.0:* 1001 12920 2163/io.knx.0 udp 0 0 192.168.178.38:56105 0.0.0.0:* 1001 22011 2163/io.knx.0 udp 0 0 192.168.178.38:52033 0.0.0.0:* 1001 14442 2163/io.knx.0 udp 0 0 0.0.0.0:41803 0.0.0.0:* 104 3738 578/avahi-daemon: r udp 0 0 192.168.178.38:41942 0.0.0.0:* 1001 12940 2163/io.knx.0 udp 0 0 192.168.178.38:46100 0.0.0.0:* 1001 12932 2163/io.knx.0 udp 0 0 192.168.178.38:48222 0.0.0.0:* 1001 12925 2163/io.knx.0 udp 0 0 192.168.178.38:50293 0.0.0.0:* 1001 12912 2163/io.knx.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 3736 578/avahi-daemon: r udp 0 0 192.168.178.38:44266 0.0.0.0:* 1001 11118 2163/io.knx.0 udp 0 0 192.168.178.38:42459 0.0.0.0:* 1001 22002 2163/io.knx.0 udp 0 0 192.168.178.38:44575 0.0.0.0:* 1001 18676 2163/io.knx.0 udp 0 0 192.168.178.38:46641 0.0.0.0:* 1001 11136 2163/io.knx.0 udp 0 0 192.168.178.38:46716 0.0.0.0:* 1001 14468 2163/io.knx.0 udp 0 0 192.168.178.38:59256 0.0.0.0:* 1001 12929 2163/io.knx.0 udp6 0 0 fe80::10c3:5902:40a:546 :::* 0 7978 700/NetworkManager udp6 0 0 :::55850 :::* 104 3739 578/avahi-daemon: r udp6 0 0 :::5353 :::* 104 3737 578/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-01-13 12:23:31.529 - info: sonoff.0 (2335) Starting MQTT authenticated server on port 1883 2025-01-13 12:23:31.981 - info: sonoff.0 (2335) Client [Sonoffsteckdose_KZ] connected with secret 1736767411979_3676 2025-01-13 12:23:34.815 - info: host.raspberry instance system.adapter.mqtt.0 in version "6.1.2" started with pid 2350 2025-01-13 12:23:35.093 - info: sonoff.0 (2335) Client [Sonoff-Britge] connected with secret 1736767415093_8657 2025-01-13 12:23:35.455 - info: mqtt.0 (2350) starting. Version 6.1.2 in /opt/iobroker/node_modules/iobroker.mqtt, node: v20.18.1, js-controller: 7.0.3 2025-01-13 12:23:35.469 - error: mqtt.0 (2350) Cannot configure secure web server, because no certificates found: , , 2025-01-13 12:23:35.471 - warn: mqtt.0 (2350) No ioBroker changes will be published to the clients. Set the "publish" option in the adapter settings to subscribe for relevant changes. 2025-01-13 12:23:35.537 - info: mqtt.0 (2350) Starting MQTT (Secure) authenticated server on 0.0.0.0:1886 2025-01-13 12:23:38.792 - info: host.raspberry instance system.adapter.discovery.0 in version "5.0.0" started with pid 2365 2025-01-13 12:23:39.434 - info: discovery.0 (2365) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.18.1, js-controller: 7.0.3 2025-01-13 12:23:43.240 - info: host.raspberry instance system.adapter.ecovacs-deebot.0 in version "1.4.15" started with pid 2380 2025-01-13 12:23:43.909 - info: ecovacs-deebot.0 (2380) starting. Version 1.4.15 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v20.18.1, js-controller: 7.0.3 2025-01-13 12:23:44.675 - info: ecovacs-deebot.0 (2380) Successfully connected to Ecovacs server. Found 1 device(s) ... 2025-01-13 12:23:44.675 - info: ecovacs-deebot.0 (2380) Using Device[0]: {"did":"f09385d3-5ade-49ea-9b94-d5b52f73a642","name":"E02P12796B09HCA40171","class":"yna5xi","resource":"EBKr","company":"eco-ng","bindTs":1723809229162,"service":{"jmq":"jmq-ngiot-eu.dc.ww.ecouser.net","mqs":"api-ngiot.dc-eu.ww.ecouser.net"},"deviceName":"DEEBOT OZMO 950 Series","icon":"https://portal-ww.ecouser.net/api/pim/file/get/606278df4a84d700082b39f1","ota":true,"UILogicId":"DX_9G","materialNo":"110-1820-0101","pid":"5c19a91ca1e6ee000178224a","product_category":"DEEBOT","model":"DX9G","updateInfo":{"needUpdate":false,"changeLog":""},"nick":"Robert","homeId":"66a74b2e13b75cee89827150","homeSort":1,"status":1,"offmap":true,"otaUpgrade":{},"deviceNumber":0} 2025-01-13 12:23:44.992 - info: ecovacs-deebot.0 (2380) Instance for 'Robert' successfully initialized 2025-01-13 12:23:44.994 - info: ecovacs-deebot.0 (2380) Library version: 0.9.6-beta.3 2025-01-13 12:23:44.994 - info: ecovacs-deebot.0 (2380) Product name: DEEBOT OZMO 950 Series 2025-01-13 12:23:46.911 - info: host.raspberry instance system.adapter.web.0 in version "6.2.5" started with pid 2399 2025-01-13 12:23:47.636 - info: web.0 (2399) starting. Version 6.2.5 in /opt/iobroker/node_modules/iobroker.web, node: v20.18.1, js-controller: 7.0.3 2025-01-13 12:23:47.874 - info: web.0 (2399) socket.io server listening on port 8082 2025-01-13 12:23:47.877 - info: web.0 (2399) http server listening on port 8082 2025-01-13 12:24:00.585 - warn: ecovacs-deebot.0 (2380) Received error message: Request failed with status code 502 for command getAdvancedMode 2025-01-13 12:24:51.506 - info: admin.0 (1949) ==> Connected system.user.admin from ::ffff:192.168.178.23 2025-01-13 12:25:52.959 - info: admin.0 (1949) <== Disconnect system.user.admin from ::ffff:192.168.178.23 admin 2025-01-13 12:25:53.274 - info: admin.0 (1949) failed connection to socket.io from ::ffff:192.168.178.23: Passport was not initialized============ Mark until here for C&P =============
iob diag has finished.
-
@civitas2021 sagte in IOB keine Objekte für KNX:
load average: 0.00, 0.00, 0.00
läuft da überhaupt irgendetwas?
@civitas2021 sagte in IOB keine Objekte für KNX:
Used repository: stable
da ist noch viel veraltet!
bitte updatenAuch das Betriebssystem
@civitas2021 sagte in IOB keine Objekte für KNX:
Pending Updates: 91
Das ganze sieht nicht nach einer neuen sauberen Installation aus.
und bezüglich KNX:
@civitas2021 sagte in IOB keine Objekte für KNX:system.adapter.knx.0 : knx : raspberry - enabled, bind: 192.168.178.38
Wer ist das?
-
Hast du dein KNX Projekt übertragen?
-
Die KNX Anlage mit Geräte (Anzahl 12) bestehend aus Aktoren und Eingabegeräte
z.B. Glastaster und Thermostaten funktioniert separat und wird über eine Schnittstelle (Raspi 192.168.178.22:3671)
mittel IOB abgefragt. Die Instanz KNX weist eine lizensierte ETS 5 aus. Die Physikalische Adresse der <Schnittstelle
0.0.0
192.168.178.38 ist der neue Raspi 5
Beim alten Raspi 3b sind alle Objekte (Daten Temperaturanzeigen Schaltzustände etc ) angezeiget worden.
Das mit dem updaten werden ich ausführen -
@frankthegreat
wie ist das gemeint?
z.Z. betreibe ich zwei Raspe 3 und Raspi 5 (neu aufgesetzt)
Die Varinate 3b läft auch mit den KNX Meldungen ohne mögliche Erweiterung übergangsweise.
Bei dem Raspi 5 habe ich eine aktuelle Instanz KNX installiert die auch in Funktion (grün)
dargestellt ist. Nur das die Objekte nicht angezeigt werden, obwohl ich die Daten der Schnittstelle
für das KNX Sytem wie beim alten Raspi 3 eingetragen habe. Prinzipiell frage ich übergangsweise
von zwei Raspi die Daten zum KNX ab. Villeicht ist das das Problem? -
Beim KNX Adapter muss dein KNX Projekt aus der ETS eingelesen werden.
Dann erscheinen auch im Objektbaum die Datenpunkte. -
@frankthegreat
vielen Dank
habe aus der Vergangenheit vergessen das man das KNX Objekt auch hochladen muss
Das war der richte Hinweis
