Um das hier zu updaten: Das Problem ist durch umstellen auf den Entwicklerzweig gelöst - die dort vorhandene Version des Adminadapters startet und ist auch wieder erreichbar
B
Latest posts made by BlindyBlinds
-
RE: ioBroker admin nicht mehr erreichbarposted in Error/Bug
-
RE: ioBroker admin nicht mehr erreichbarposted in Error/Bug
Hm, ich bin natürlich etwas paranoid, aber mein iobroker läuft in der Tat als User "iobroker"
Ausgabe ist
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: fujiki Icon name: computer-desktop Chassis: desktop Operating System: Ubuntu 22.04.4 LTS Kernel: Linux 5.15.0-101-generic Architecture: x86-64 Hardware Vendor: FUJITSU Hardware Model: FUTRO S740 model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz Docker : false Virtualization : none Kernel : x86_64 Userland : amd64 Systemuptime and Load: 17:28:16 up 3 min, 3 users, load average: 0.28, 0.24, 0.10 CPU threads: 4 *** Time and Time Zones *** Local time: Fri 2024-03-29 17:28:16 CET Universal time: Fri 2024-03-29 16:28:16 UTC RTC time: Fri 2024-03-29 16:28:16 Time zone: Europe/Amsterdam (CET, +0100) System clock synchronized: yes NTP service: n/a RTC in local TZ: no *** User and Groups *** iobroker /home/iobroker iobroker tty dialout sudo audio video *** X-Server-Setup *** X-Server: false Desktop: Terminal: Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 3.7G 649M 2.3G 5.0M 692M 2.8G Swap: 16G 0B 16G Total: 20G 649M 18G 3681 M total memory 649 M used memory 196 M active memory 893 M inactive memory 2339 M free memory 47 M buffer memory 644 M swap cache 16383 M total swap 0 M used swap 16383 M free swap *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 369M 1.7M 367M 1% /run /dev/sda2 ext4 49G 25G 23G 53% / tmpfs tmpfs 1.8G 736K 1.8G 1% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda1 vfat 1.1G 6.1M 1.1G 1% /boot/efi tmpfs tmpfs 369M 4.0K 369M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: [Fri Mar 29 17:24:29 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Fri Mar 29 17:24:31 2024] EXT4-fs (sda2): re-mounted. Opts: (null). Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,relatime |-/snap/core20/2182 /dev/loop2 squashfs ro,nodev,relatime,errors=continue |-/snap/core20/2105 /dev/loop3 squashfs ro,nodev,relatime,errors=continue |-/snap/core18/2812 /dev/loop1 squashfs ro,nodev,relatime,errors=continue |-/snap/core18/2796 /dev/loop0 squashfs ro,nodev,relatime,errors=continue |-/snap/core22/1033 /dev/loop4 squashfs ro,nodev,relatime,errors=continue |-/snap/core22/1122 /dev/loop5 squashfs ro,nodev,relatime,errors=continue |-/snap/docker/2915 /dev/loop7 squashfs ro,nodev,relatime,errors=continue |-/snap/docker/2904 /dev/loop6 squashfs ro,nodev,relatime,errors=continue |-/snap/lxd/27948 /dev/loop9 squashfs ro,nodev,relatime,errors=continue |-/snap/lxd/27428 /dev/loop8 squashfs ro,nodev,relatime,errors=continue |-/snap/snapd/20671 /dev/loop10 squashfs ro,nodev,relatime,errors=continue |-/snap/snapd/21184 /dev/loop11 squashfs ro,nodev,relatime,errors=continue `-/boot/efi /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 3.6G /var/ 2.1G /var/lib 1.5G /var/lib/snapd 901M /var/lib/snapd/snaps 899M /var/log 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 184.0M in the file system. /opt/iobroker/backups: 27M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 179M /opt/iobroker/iobroker-data/ 133M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 38M /opt/iobroker/iobroker-data/files/javascript.admin/static 37M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map 9.0M /opt/iobroker/iobroker-data/objects.jsonl 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.d0c8b930.chunk.js.map 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.20.0 /usr/bin/node v18.20.0 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 nodejs: Installed: 18.20.0-1nodesource1 Candidate: 18.20.0-1nodesource1 Version table: *** 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.9~dfsg-1ubuntu3.4 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 12.22.9~dfsg-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : fujiki - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : fujiki - enabled + system.adapter.discovery.0 : discovery : fujiki - enabled + system.adapter.iqontrol.0 : iqontrol : fujiki - enabled + system.adapter.mediola-gateway.0 : mediola-gateway : fujiki - enabled + system.adapter.simple-api.0 : simple-api : fujiki - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : fujiki - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : fujiki - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.simple-api.0 : simple-api : fujiki - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : fujiki - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "iqontrol" : 2.3.0 , installed 2.3.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mediola-gateway": 1.1.0 , installed 1.1.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "web" : 6.2.3 , installed 6.2.3 Adapter "ws" : 2.5.11 , installed 2.5.11 Objects and States Please stand by - This may take a while Objects: 278 States: 181 *** OS-Repositories and Updates *** Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:6 https://deb.torproject.org/torproject.org jammy 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:53 0.0.0.0:* LISTEN 997 21470 778/pihole-FTL tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 23309 785/sshd: /usr/sbin tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 19309 1/init tcp 0 0 0.0.0.0:90 0.0.0.0:* LISTEN 0 25376 843/lighttpd tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 997 21476 778/pihole-FTL tcp 0 0 0.0.0.0:51821 0.0.0.0:* LISTEN 0 27074 1444/docker-proxy tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1004 25994 699/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1004 26002 699/iobroker.js-con tcp 0 0 0.0.0.0:5240 0.0.0.0:* LISTEN 0 25336 837/nginx: master p tcp 0 0 0.0.0.0:5239 0.0.0.0:* LISTEN 998 25891 709/python3 tcp6 0 0 :::53 :::* LISTEN 997 21472 778/pihole-FTL tcp6 0 0 :::22 :::* LISTEN 0 23311 785/sshd: /usr/sbin tcp6 0 0 :::111 :::* LISTEN 0 484 1/init tcp6 0 0 :::90 :::* LISTEN 0 25375 843/lighttpd tcp6 0 0 :::51821 :::* LISTEN 0 27077 1450/docker-proxy tcp6 0 0 :::5239 :::* LISTEN 998 25897 709/python3 tcp6 0 0 ::1:4711 :::* LISTEN 997 21477 778/pihole-FTL tcp6 0 0 :::8087 :::* LISTEN 1004 29784 1675/io.simple-api. tcp6 0 0 :::8082 :::* LISTEN 1004 28355 1656/io.web.0 udp 0 0 0.0.0.0:57540 0.0.0.0:* 1004 26567 1690/io.mediola-gat udp 0 0 0.0.0.0:51820 0.0.0.0:* 0 26402 1464/docker-proxy udp 0 0 0.0.0.0:1902 0.0.0.0:* 1004 26566 1690/io.mediola-gat udp 0 0 0.0.0.0:53 0.0.0.0:* 997 21469 778/pihole-FTL udp 0 0 192.168.0.97:68 0.0.0.0:* 101 24518 678/systemd-network udp 0 0 0.0.0.0:111 0.0.0.0:* 0 19310 1/init udp 0 0 172.17.0.1:123 0.0.0.0:* 115 29647 804/ntpd udp 0 0 192.168.0.97:123 0.0.0.0:* 0 25298 804/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 0 25296 804/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 0 25292 804/ntpd udp6 1280 0 fe80::4e52:62ff:feb:546 :::* 101 24513 678/systemd-network udp6 0 0 :::51820 :::* 0 27080 1472/docker-proxy udp6 0 0 :::53 :::* 997 21471 778/pihole-FTL udp6 0 0 :::111 :::* 0 18378 1/init udp6 0 0 fe80::c02b:eff:fe0f:123 :::* 115 29691 804/ntpd udp6 0 0 fe80::42:36ff:fed7::123 :::* 115 29689 804/ntpd udp6 0 0 fe80::4e52:62ff:feb:123 :::* 0 25304 804/ntpd udp6 0 0 fdba:fa8:c75f:0:4e5:123 :::* 0 25302 804/ntpd udp6 0 0 ::1:123 :::* 0 25300 804/ntpd udp6 0 0 :::123 :::* 0 25289 804/ntpd *** Log File - Last 25 Lines *** 2024-03-29 17:28:46.292 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-29 17:28:46.292 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1364:14) 2024-03-29 17:28:46.292 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) 2024-03-29 17:28:46.292 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1203:32) 2024-03-29 17:28:46.293 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1019:12) 2024-03-29 17:28:46.293 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) 2024-03-29 17:28:46.293 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:28:49 2024-03-29 17:28:46.293 - error: host.fujiki Caught by controller[0]: Node.js v18.20.0 2024-03-29 17:28:46.293 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-03-29 17:28:46.293 - info: host.fujiki Restart adapter system.adapter.admin.0 because enabled 2024-03-29 17:29:16.319 - info: host.fujiki instance system.adapter.admin.0 started with pid 3110 2024-03-29 17:29:17.223 - error: host.fujiki Caught by controller[0]: /opt/iobroker/node_modules/iobroker.admin/main.js:43 2024-03-29 17:29:17.223 - error: host.fujiki Caught by controller[0]: class Admin extends utils.Adapter { 2024-03-29 17:29:17.224 - error: host.fujiki Caught by controller[0]: ^ 2024-03-29 17:29:17.224 - error: host.fujiki Caught by controller[0]: TypeError: Class extends value #<Object> is not a constructor or null 2024-03-29 17:29:17.224 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-29 17:29:17.224 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1364:14) 2024-03-29 17:29:17.224 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) 2024-03-29 17:29:17.224 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1203:32) 2024-03-29 17:29:17.225 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1019:12) 2024-03-29 17:29:17.226 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) 2024-03-29 17:29:17.227 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:28:49 2024-03-29 17:29:17.227 - error: host.fujiki Caught by controller[0]: Node.js v18.20.0 2024-03-29 17:29:17.227 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-03-29 17:29:17.227 - info: host.fujiki Restart adapter system.adapter.admin.0 because enabled============ Mark until here for C&P =============
System ist frisch durchgestartet und alle Module auf dem neuesten Stand. Schon verrückt worüber sich das admin-Modul beschwert, das noch funktionierende mediola-Modul extended auch den utils.Adapter
Installation hatte ich damals nach der Anleitung unter https://iobroker.readthedocs.io/de/latest/getting-started/installation.html ausgeführt.
@iotowago wie sieht es bei dir aus?
Frohe Ostern wünsche ich schon mal!
-
RE: ioBroker admin nicht mehr erreichbarposted in Error/Bug
UTC ist ja richtig. Rest ist korrigiert, das mit nodejs sah schon vielversprechend aus. Hat auch etwas gebraucht
Ergebnis ist aber noch
2024-03-24 19:01:03.281 - error: host.fujiki Caught by controller[0]: /opt/iobroker/node_modules/iobroker.admin/main.js:43 2024-03-24 19:01:03.282 - error: host.fujiki Caught by controller[0]: class Admin extends utils.Adapter { 2024-03-24 19:01:03.282 - error: host.fujiki Caught by controller[0]: ^ 2024-03-24 19:01:03.282 - error: host.fujiki Caught by controller[0]: TypeError: Class extends value #<Object> is not a constructor or null 2024-03-24 19:01:03.282 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-24 19:01:03.282 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1356:14) 2024-03-24 19:01:03.282 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1414:10) 2024-03-24 19:01:03.283 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1197:32) 2024-03-24 19:01:03.283 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1013:12) 2024-03-24 19:01:03.283 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) 2024-03-24 19:01:03.283 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:28:49 2024-03-24 19:01:03.283 - error: host.fujiki Caught by controller[0]: Node.js v18.19.1 2024-03-24 19:01:03.283 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED)Ich überleg mal wie die timezone einen TypeError auslöst, aber so weit bin ich noch nicht
-
RE: ioBroker admin nicht mehr erreichbarposted in Error/Bug
@homoran said in ioBroker admin nicht mehr erreichbar:
@blindyblinds sagte in ioBroker admin nicht mehr erreichbar:
/home/iUser
dein user ist nicht in der Gruppe iobroker
wie hast du iobroker installiert?Keine Sorge, der User ist drin
-
RE: ioBroker admin nicht mehr erreichbarposted in Error/Bug
@haselchen Super, das ging schnell mit der Antwort
2024-03-24 17:12:44.389 - info: host.fujiki Restart adapter system.adapter.admin.0 because enabled 2024-03-24 17:13:14.455 - info: host.fujiki instance system.adapter.admin.0 started with pid 8171 2024-03-24 17:13:15.329 - error: host.fujiki Caught by controller[0]: /opt/iobroker/node_modules/iobroker.admin/main.js:43 2024-03-24 17:13:15.330 - error: host.fujiki Caught by controller[0]: class Admin extends utils.Adapter { 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: ^ 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: TypeError: Class extends value #<Object> is not a constructor or null 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) 2024-03-24 17:13:15.331 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 2024-03-24 17:13:15.332 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:23:47 2024-03-24 17:13:15.332 - error: host.fujiki Caught by controller[0]: Node.js v18.17.1 2024-03-24 17:13:15.332 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED)Ergebnis leider gleich (Zeit ist in UTC, also -1 )
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: fujiki Icon name: computer-desktop Chassis: desktop Operating System: Ubuntu 22.04.4 LTS Kernel: Linux 5.15.0-101-generic Architecture: x86-64 Hardware Vendor: FUJITSU Hardware Model: FUTRO S740 model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz Docker : false Virtualization : none Kernel : x86_64 Userland : amd64 Systemuptime and Load: 17:16:28 up 1:54, 2 users, load average: 0.66, 0.41, 0.32 CPU threads: 4 *** Time and Time Zones *** Local time: Sun 2024-03-24 17:16:29 UTC Universal time: Sun 2024-03-24 17:16:29 UTC RTC time: Sun 2024-03-24 17:16:29 Time zone: Etc/UTC (UTC, +0000) System clock synchronized: yes NTP service: n/a RTC in local TZ: no *** User and Groups *** iUser /home/iUser iUser adm cdrom sudo dip plugdev lxd *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.7G 1.1G 899M 5.0M 1.7G 2.3G Swap: 16G 0B 16G Total: 20G 1.1G 17G 3681 M total memory 1103 M used memory 530 M active memory 1905 M inactive memory 899 M free memory 111 M buffer memory 1566 M swap cache 16383 M total swap 0 M used swap 16383 M free swap *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 369M 1.7M 367M 1% /run /dev/sda2 ext4 49G 24G 23G 52% / tmpfs tmpfs 1.8G 736K 1.8G 1% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda1 vfat 1.1G 6.1M 1.1G 1% /boot/efi tmpfs tmpfs 369M 4.0K 369M 1% /run/user/1000 /dev/mapper/cryptdisk ext4 153G 82G 64G 56% /mnt/cdisk Messages concerning ext4 filesystem in dmesg: [Sun Mar 24 15:21:39 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Sun Mar 24 15:21:42 2024] EXT4-fs (sda2): re-mounted. Opts: (null). Quota mode: none. [Sun Mar 24 15:25:13 2024] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,relatime |-/snap/core20/2182 /dev/loop2 squashfs ro,nodev,relatime,errors=continue |-/snap/core20/2105 /dev/loop3 squashfs ro,nodev,relatime,errors=continue |-/snap/core18/2812 /dev/loop1 squashfs ro,nodev,relatime,errors=continue |-/snap/core18/2796 /dev/loop0 squashfs ro,nodev,relatime,errors=continue |-/snap/core22/1033 /dev/loop4 squashfs ro,nodev,relatime,errors=continue |-/snap/core22/1122 /dev/loop5 squashfs ro,nodev,relatime,errors=continue |-/snap/docker/2915 /dev/loop7 squashfs ro,nodev,relatime,errors=continue |-/snap/docker/2904 /dev/loop6 squashfs ro,nodev,relatime,errors=continue |-/snap/lxd/27037 /dev/loop8 squashfs ro,nodev,relatime,errors=continue |-/snap/snapd/20671 /dev/loop10 squashfs ro,nodev,relatime,errors=continue |-/snap/lxd/27428 /dev/loop9 squashfs ro,nodev,relatime,errors=continue |-/snap/snapd/21184 /dev/loop11 squashfs ro,nodev,relatime,errors=continue |-/boot/efi /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro `-/mnt/cdisk /dev/mapper/cryptdisk ext4 rw,relatime Files in neuralgic directories: /var: 3.3G /var/ 2.1G /var/lib 1.5G /var/lib/snapd 901M /var/lib/snapd/snaps 751M /var/log Archived and active journals take up 744.0M in the file system. /opt/iobroker/backups: 35M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 175M /opt/iobroker/iobroker-data/ 132M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 38M /opt/iobroker/iobroker-data/files/javascript.admin/static 37M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.d0c8b930.chunk.js.map 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 6.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/344.2eef1017.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x jammy/main amd64 Packages 100 /var/lib/dpkg/status 12.22.9~dfsg-1ubuntu3.4 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 12.22.9~dfsg-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 1 Adapter State system.adapter.admin.0 : admin : fujiki - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : fujiki - enabled + system.adapter.discovery.0 : discovery : fujiki - enabled + system.adapter.iqontrol.0 : iqontrol : fujiki - enabled + system.adapter.mediola-gateway.0 : mediola-gateway : fujiki - enabled + system.adapter.simple-api.0 : simple-api : fujiki - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : fujiki - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : fujiki - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.simple-api.0 : simple-api : fujiki - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : fujiki - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.10.11 , installed 2.8.1 [Updatable] Adapter "discovery" : 4.4.0 , installed 3.1.0 [Updatable] Adapter "iqontrol" : 2.3.0 , installed 2.3.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mediola-gateway": 1.1.0 , installed 1.0.1 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.5.5 [Updatable] Adapter "web" : 6.2.3 , installed 6.1.2 [Updatable] Adapter "ws" : 2.5.10 , installed 2.5.5 [Updatable] Objects and States Please stand by - This may take a while Objects: 274 States: 179 *** OS-Repositories and Updates *** Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease Hit:5 https://deb.nodesource.com/node_18.x jammy InRelease Hit:6 https://deb.torproject.org/torproject.org jammy 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:5239 0.0.0.0:* LISTEN 998 25851 716/python3 tcp 0 0 0.0.0.0:5240 0.0.0.0:* LISTEN 0 22398 840/nginx: master p tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN 1001 28491 2125/java tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 997 25793 782/pihole-FTL tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 997 25787 782/pihole-FTL tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 25720 793/sshd: /usr/sbin tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1004 73258 7728/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1004 73265 7728/iobroker.js-co tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 21391 1/init tcp 0 0 0.0.0.0:90 0.0.0.0:* LISTEN 0 22437 847/lighttpd tcp 0 0 0.0.0.0:51821 0.0.0.0:* LISTEN 0 29046 1409/docker-proxy tcp6 0 0 :::7654 :::* LISTEN 1001 29678 2125/java tcp6 0 0 ::1:4711 :::* LISTEN 997 25794 782/pihole-FTL tcp6 0 0 :::5239 :::* LISTEN 998 25857 716/python3 tcp6 0 0 :::8087 :::* LISTEN 1004 69595 7804/io.simple-api. tcp6 0 0 :::8082 :::* LISTEN 1004 70561 7788/io.web.0 tcp6 0 0 127.0.0.1:7659 :::* LISTEN 1001 30284 2125/java tcp6 0 0 127.0.0.1:7658 :::* LISTEN 1001 28672 2125/java tcp6 0 0 127.0.0.1:7660 :::* LISTEN 1001 32769 2125/java tcp6 0 0 172.17.0.1:7652 :::* LISTEN 1001 30217 2125/java tcp6 0 0 :::4445 :::* LISTEN 1001 31799 2125/java tcp6 0 0 :::4444 :::* LISTEN 1001 30882 2125/java tcp6 0 0 127.0.0.1:6668 :::* LISTEN 1001 30880 2125/java tcp6 0 0 :::53 :::* LISTEN 997 25789 782/pihole-FTL tcp6 0 0 :::22 :::* LISTEN 0 25722 793/sshd: /usr/sbin tcp6 0 0 :::111 :::* LISTEN 0 384 1/init tcp6 0 0 :::90 :::* LISTEN 0 22436 847/lighttpd tcp6 0 0 ::1:7657 :::* LISTEN 1001 30830 2125/java tcp6 0 0 192.168.0.97:7657 :::* LISTEN 1001 30831 2125/java tcp6 0 0 192.168.0.97:7652 :::* LISTEN 1001 30218 2125/java tcp6 0 0 fdba:fa8:c75f:0:4e:7652 :::* LISTEN 1001 30219 2125/java tcp6 0 0 :::25418 :::* LISTEN 1001 28593 2125/java tcp6 0 0 :::51821 :::* LISTEN 0 27516 1415/docker-proxy udp 0 0 0.0.0.0:1902 0.0.0.0:* 1004 73390 7819/io.mediola-gat udp 0 0 0.0.0.0:53 0.0.0.0:* 997 25786 782/pihole-FTL udp 0 0 192.168.0.97:68 0.0.0.0:* 101 20116 685/systemd-network udp 0 0 0.0.0.0:111 0.0.0.0:* 0 21392 1/init udp 0 0 172.17.0.1:123 0.0.0.0:* 115 27643 802/ntpd udp 0 0 192.168.0.97:123 0.0.0.0:* 0 20290 802/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 0 20288 802/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 0 20284 802/ntpd udp 0 0 0.0.0.0:39319 0.0.0.0:* 1004 73391 7819/io.mediola-gat udp 0 0 0.0.0.0:51820 0.0.0.0:* 0 29055 1428/docker-proxy udp6 0 0 :::1900 :::* 1001 30225 2125/java udp6 0 0 :::1900 :::* 1001 30222 2125/java udp6 0 0 :::1900 :::* 1001 30750 2125/java udp6 0 0 :::53 :::* 997 25788 782/pihole-FTL udp6 0 0 :::111 :::* 0 21393 1/init udp6 0 0 fe80::f4d6:b7ff:fec:123 :::* 115 29698 802/ntpd udp6 0 0 fe80::42:93ff:fee6::123 :::* 115 27648 802/ntpd udp6 0 0 fe80::4e52:62ff:feb:123 :::* 0 20296 802/ntpd udp6 0 0 fdba:fa8:c75f:0:4e5:123 :::* 0 20294 802/ntpd udp6 0 0 ::1:123 :::* 0 20292 802/ntpd udp6 0 0 :::123 :::* 0 20281 802/ntpd udp6 1280 0 fe80::4e52:62ff:feb:546 :::* 101 20139 685/systemd-network udp6 0 0 :::51820 :::* 0 29057 1434/docker-proxy udp6 0 0 :::25417 :::* 1001 30234 2125/java udp6 0 0 fdba:fa8:c75f:0:4e:7653 :::* 1001 30230 2125/java udp6 0 0 192.168.0.97:7653 :::* 1001 30229 2125/java udp6 0 0 172.17.0.1:7653 :::* 1001 30228 2125/java *** Log File - Last 25 Lines *** 2024-03-24 17:16:21.045 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-24 17:16:21.045 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) 2024-03-24 17:16:21.046 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) 2024-03-24 17:16:21.046 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) 2024-03-24 17:16:21.046 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) 2024-03-24 17:16:21.046 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 2024-03-24 17:16:21.046 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:23:47 2024-03-24 17:16:21.046 - error: host.fujiki Caught by controller[0]: Node.js v18.17.1 2024-03-24 17:16:21.046 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-03-24 17:16:21.046 - info: host.fujiki Restart adapter system.adapter.admin.0 because enabled 2024-03-24 17:16:51.111 - info: host.fujiki instance system.adapter.admin.0 started with pid 8571 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: /opt/iobroker/node_modules/iobroker.admin/main.js:43 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: class Admin extends utils.Adapter { 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: ^ 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: TypeError: Class extends value #<Object> is not a constructor or null 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) 2024-03-24 17:16:52.022 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) 2024-03-24 17:16:52.023 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) 2024-03-24 17:16:52.023 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 2024-03-24 17:16:52.023 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:23:47 2024-03-24 17:16:52.023 - error: host.fujiki Caught by controller[0]: Node.js v18.17.1 2024-03-24 17:16:52.023 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-03-24 17:16:52.023 - info: host.fujiki Restart adapter system.adapter.admin.0 because enabled============ Mark until here for C&P =============
-
ioBroker admin nicht mehr erreichbarposted in Error/Bug
Da war ich wohl etwas optimistisch, als ich das admin-Modul heute, nach 5 Monaten oder so, in der Weboberfläche auf den neuesten Stand bringen wollte.
Seite dem ist die admin Weboberfläche nicht mehr erreichbar. ioBroker an sich funktioniert wunderbar, und die Steuerung via iqontrol geht auch.Jedenfalls; admin ist noch da:
iobroker list instances system.adapter.admin.0 : admin : fujiki - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : fujiki - enabled + system.adapter.discovery.0 : discovery : fujiki - enabled + system.adapter.iqontrol.0 : iqontrol : fujiki - enabled + system.adapter.mediola-gateway.0 : mediola-gateway : fujiki - enabled + system.adapter.simple-api.0 : simple-api : fujiki - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : fujiki - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is aliveEr meckert aber bezüglich eines Javascriptproblems hier nach einem iobroker start:
2024-03-24 17:00:50.641 - info: host.fujiki iobroker.js-controller version 5.0.19 js-controller starting 2024-03-24 17:00:50.645 - info: host.fujiki Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-03-24 17:00:50.645 - info: host.fujiki hostname: fujiki, node: v18.17.1 2024-03-24 17:00:50.646 - info: host.fujiki ip addresses: 192.168.0.97 fdba:fa8:c75f:0:4e32:62ef:feb9:5bc2 fe80::4e52:62ef:feb9:5bc2 172.17.0.1 fe80::42:93ff:ffe6:b28e fe80::f4d6:b7ff:fecf:433b 2024-03-24 17:00:51.185 - info: host.fujiki connected to Objects and States 2024-03-24 17:00:51.209 - info: host.fujiki added notifications configuration of host 2024-03-24 17:00:51.541 - info: host.fujiki 7 instances found 2024-03-24 17:00:51.558 - info: host.fujiki starting 7 instances 2024-03-24 17:00:51.600 - info: host.fujiki instance system.adapter.admin.0 started with pid 7746 2024-03-24 17:00:52.476 - error: host.fujiki Caught by controller[0]: /opt/iobroker/node_modules/iobroker.admin/main.js:43 2024-03-24 17:00:52.477 - error: host.fujiki Caught by controller[0]: class Admin extends utils.Adapter { 2024-03-24 17:00:52.477 - error: host.fujiki Caught by controller[0]: ^ 2024-03-24 17:00:52.477 - error: host.fujiki Caught by controller[0]: TypeError: Class extends value #<Object> is not a constructor or null 2024-03-24 17:00:52.478 - error: host.fujiki Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:43:27) 2024-03-24 17:00:52.478 - error: host.fujiki Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) 2024-03-24 17:00:52.478 - error: host.fujiki Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) 2024-03-24 17:00:52.478 - error: host.fujiki Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) 2024-03-24 17:00:52.478 - error: host.fujiki Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) 2024-03-24 17:00:52.478 - error: host.fujiki Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 2024-03-24 17:00:52.479 - error: host.fujiki Caught by controller[0]: at node:internal/main/run_main_module:23:47 2024-03-24 17:00:52.479 - error: host.fujiki Caught by controller[0]: Node.js v18.17.1 2024-03-24 17:00:52.479 - error: host.fujiki instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED)Ist das sonst wem untergekommen heute?
-
RE: [Neuer Adapter] mediola-gatewayposted in Tester
@oelison Danke für die prompte Antwort! In dem Configtool (ich hoffe wirr meinen die gleiche App
) bekomme ich leider auch nicht mehr Meldungen angezeigt, es scheint ihn nicht zu rühren was die Handyapp ausführen kann
-
RE: [Neuer Adapter] mediola-gatewayposted in Tester
Guten Abend,
tolles Teil dieser Adapter, Installation und Erkennung des Gateway hat direkt funktioniert. Hat hier schon jemand mit einem Mediola V5-Gateway und den Nobily-Rollos gehabt? Ich hab hier wie in der Anleitung beschrieben die Instanz auf DEBUG gesetzt, bekomme aber keinen Identifier im Log angezeigt. Sieht nur etwa so aus:
0 0 Log-Größe: 665.4 KB 1 PID Zeit debug Nachricht mediola-gateway.0 313602 2023-09-20 19:35:17.567 debug state mediola-gateway.0.sysvars.idFF changed: 0 (ack = true) mediola-gateway.0 313602 2023-09-20 19:35:17.517 debug {"type":"EVENT","adr":"FF","state":"0"} mediola-gateway.0 313602 2023-09-20 19:35:17.517 debug mediola device found data: {XC_SUC}[{"type":"EVENT","adr":"FF","state":"0"}] mediola-gateway.0 313602 2023-09-20 19:35:17.516 debug {XC_SUC}[{"type":"EVENT","adr":"FF","state":"0"}] mediola-gateway.0 313602 2023-09-20 19:35:17.489 debug Source: onReady mediola-gateway.0 313602 2023-09-20 19:35:17.472 debug validMediola: true sysvarInti: false timerRead: false mediola-gateway.0 313602 2023-09-20 19:35:17.471 info Mediola connected with ip:192.168.0.219 and mac:40-66-7a-00-32-71 mediola-gateway.0 313602 2023-09-20 19:35:17.471 debug mediola-gateway.0 313602 2023-09-20 19:35:17.471 debug NAME:AIO GATEWAY V5 mediola-gateway.0 313602 2023-09-20 19:35:17.471 debug MAC:40-66-7a-00-32-71 mediola-gateway.0 313602 2023-09-20 19:35:17.470 debug DNS:192.168.0.1 mediola-gateway.0 313602 2023-09-20 19:35:17.470 debug GW:192.168.0.1 mediola-gateway.0 313602 2023-09-20 19:35:17.470 debug SN:255.255.255.0 mediola-gateway.0 313602 2023-09-20 19:35:17.470 debug IP:192.168.0.219 mediola-gateway.0 313602 2023-09-20 19:35:17.470 debug VID:FFFF mediola-gateway.0 313602 2023-09-20 19:35:17.469 debug VER:1.0.31 mediola-gateway.0 313602 2023-09-20 19:35:17.469 debug HWV:E1 mediola-gateway.0 313602 2023-09-20 19:35:17.469 debug DHCP:TRUE mediola-gateway.0 313602 2023-09-20 19:35:17.468 debug out RECEIVED: 192.168.0.219:1901 - DHCP:TRUEHWV:E1VER:1.0.31VID:FFFFIP:192.168.0.219SN:255.255.255.0GW:192.168.0.1DNS:192.168.0.1MAC:40-66-7a-00-32-71NAME:AIO GATEWAY V5|end mediola-gateway.0 313602 2023-09-20 19:35:17.412 debug UDP socket listening on 0.0.0.0:1902 mediola-gateway.0 313602 2023-09-20 19:35:17.407 info auto detection: true mediola-gateway.0 313602 2023-09-20 19:35:17.382 info starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.mediola-gateway, node: v18.17.1, js-controller: 4.0.24 mediola-gateway.0 313602 2023-09-20 19:35:17.331 debug States connected to redis: 127.0.0.1:9000 mediola-gateway.0 313602 2023-09-20 19:35:17.326 debug States create User PubSub Client mediola-gateway.0 313602 2023-09-20 19:35:17.325 debug States create System PubSub Client mediola-gateway.0 313602 2023-09-20 19:35:17.321 debug Redis States: Use Redis connection: 127.0.0.1:9000 mediola-gateway.0 313602 2023-09-20 19:35:17.309 debug Objects connected to redis: 127.0.0.1:9001 mediola-gateway.0 313602 2023-09-20 19:35:17.305 debug Objects client initialize lua scripts mediola-gateway.0 313602 2023-09-20 19:35:17.296 debug Objects create User PubSub Client mediola-gateway.0 313602 2023-09-20 19:35:17.295 debug Objects create System PubSub Client mediola-gateway.0 313602 2023-09-20 19:35:17.294 debug Objects client ready ... initialize now mediola-gateway.0 313602 2023-09-20 19:35:17.273 debug Redis Objects: Use Redis connection: 127.0.0.1:9001Das XC_SUC wird gemeldet wenn ich via IOS und der Iqontrol-App eine Jalousie ansteuere.
Via tcpdump habe ich mir die gültigen Steuerbefehle manuell rausgesucht, ein STOP ist etwa
GET /cmd?XC_FNC=SendSC&type=DY&data=53E6760555&at=fdf26619fad78c2100884f709a8127e7&_=1695237633896 - von dort komme ich aber nicht weiter mit der Integration.
