Reanimation meines Adapter aus 2021 NodeDMX
-
und es wäre toll wenn das jemand nach Entwicklung verschieben könnte, kann ich wohl nicht mehr ändern
-
@boardy sagte in Reanimation meines Adapter aus 2021 NodeDMX:
Node.js v20.19.2
JS Controller 7.0.6
npm version
{
'iobroker.nodedmx': '1.0.0',
npm: '11.5.2',
node: '22.16.0',Das passt nicht. Schau dir die Ausgabe von
iob diagin ganzen Länge an.
-
Danke, das hing total. nun hab ich auch die Edit Funktion wieder gefunden...
-
Nein. Drück mal F5.
-
========== Start marking the full check here =========== ```bash Script v.2025-03-08 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64 bit Docker : v10.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 19:17:19 up 48 days, 1:36, 0 user, load average: 0.95, 0.68, 0.64 CPU threads: 4 *** LIFE CYCLE STATUS *** Unknown release codenamed ''. Please check yourself if the Operating System is actively maintained. *** TIME AND TIMEZONES *** Sat Aug 2 17:17:19 UTC 2025 Sat Aug 2 19:17:19 CEST 2025 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/opt/iobroker GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 20G 4.1G 641M 179M 16G 16G Swap: 14G 1.6G 13G Total: 35G 5.7G 13G Active iob-Instances: 11 19852 M total memory 3937 M used memory 4700 M active memory 12991 M inactive memory 611 M free memory 39 M buffer memory 15777 M swap cache 13959 M total swap 1529 M used swap 12430 M free swap *** top - Table Of Processes *** top - 19:17:19 up 48 days, 1:36, 0 user, load average: 0.95, 0.68, 0.64 Tasks: 21 total, 1 running, 20 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 : 19852.1 total, 609.7 free, 3939.8 used, 15817.6 buff/cache MiB Swap: 13959.9 total, 12430.5 free, 1529.4 used. 15912.3 avail Mem *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cachedev_0 btrfs 11T 6.8T 3.8T 65% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 9.7G 0 9.7G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 btrfs 11T 6.8T 3.8T 65% /opt/iobroker /dev/mapper/cachedev_0 btrfs 11T 6.8T 3.8T 65% /etc/hosts tmpfs tmpfs 9.7G 0 9.7G 0% /proc/acpi tmpfs tmpfs 9.7G 0 9.7G 0% /proc/scsi tmpfs tmpfs 9.7G 0 9.7G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: [Sun Jun 15 17:41:18 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sun Jun 15 17:41:18 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Sun Jun 15 17:41:18 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sun Jun 15 17:41:18 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Sun Jun 15 17:41:23 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sun Jun 15 17:41:23 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Sun Jun 15 17:41:24 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sun Jun 15 17:41:24 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Sun Jun 15 17:41:41 2025] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [Sun Jun 15 17:42:13 2025] EXT4-fs (usb1p1): mounted filesystem with ordered data mode. Opts: nodelalloc,synoacl [Fri Aug 1 03:05:53 2025] EXT4-fs (usb1p1): re-mounted. Opts: (null) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/cachedev_0[/@syno/@docker/btrfs/subvolumes/3799a5dd43b68f19315050342b27f2f9ee939bab98a7cdb41b090ae20d826196] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=4364,subvol=/@syno/@docker/btrfs/subvolumes/3799a5dd43b68f19315050342b27f2f9ee939bab98a7cdb41b090ae20d826196 |-/opt/iobroker /dev/mapper/cachedev_0[/@syno/docker/iobroker8_data] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=260,subvol=/@syno/docker |-/etc/resolv.conf /dev/mapper/cachedev_0[/@syno/@docker/containers/aeb2c0fdc0000ff82542d72499d1b8d29d1e6939a1cca42657100aba3f4b0faf/resolv.conf] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno |-/etc/hostname /dev/mapper/cachedev_0[/@syno/@docker/containers/aeb2c0fdc0000ff82542d72499d1b8d29d1e6939a1cca42657100aba3f4b0faf/hostname] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno `-/etc/hosts /dev/mapper/cachedev_0[/@syno/@docker/containers/aeb2c0fdc0000ff82542d72499d1b8d29d1e6939a1cca42657100aba3f4b0faf/hosts] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno Files in neuralgic directories: /var: 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg/info /opt/iobroker/backups: 64M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 271M /opt/iobroker/iobroker-data/ 156M /opt/iobroker/iobroker-data/files 51M /opt/iobroker/iobroker-data/backup-objects 47M /opt/iobroker/iobroker-data/node-red 47M /opt/iobroker/iobroker-data/files/admin.admin The five largest files in iobroker-data are: 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 14M /opt/iobroker/iobroker-data/objects.jsonl 9.3M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js 9.2M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' 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 v20.19.2 /usr/bin/node v20.19.2 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.31.0 nodejs: Installed: 20.19.2-1nodesource1 Candidate: 20.19.4-1nodesource1 Version table: 20.19.4-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages *** 20.19.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 7.0.6, hostname: iobroker , alive, uptime: 4149538) Core adapters versions js-controller: 7.0.6 admin: 7.6.17 javascript: "javascript" not found nodejs modules from github: 1 +-- iobroker.nodedmx@1.0.0 (git+ssh://git@github.com/Bordman-ger/ioBroker.nodedmx.git#e93516c9c88702035b09e4579a0018e8e3404107) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker - enabled system.adapter.discovery.0 : discovery : iobroker - disabled system.adapter.email.0 : email : iobroker - disabled + system.adapter.ham.0 : ham : iobroker - enabled system.adapter.info.0 : info : iobroker - disabled + system.adapter.mielecloudservice.0 : mielecloudservice : iobroker - enabled + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.modbus.1 : modbus : iobroker - enabled system.adapter.mystrom.0 : mystrom : iobroker - disabled + system.adapter.netatmo.0 : netatmo : iobroker - enabled + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.11.16 system.adapter.nodedmx.0 : nodedmx : iobroker - disabled system.adapter.pvforecast.0 : pvforecast : iobroker - disabled system.adapter.solarwetter.0 : solarwetter : iobroker - disabled + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled + system.adapter.unifi.0 : unifi : iobroker - enabled system.adapter.weatherunderground.0 : weatherunderground : iobroker - disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.11.16 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'boardy' │ 'https://github.com/Bordman-ger/ioBroker.nanodmx.git' │ false │ │ 1 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 2 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.6.17 , installed 7.6.17 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "ham" : 5.3.1 , installed 5.3.1 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "mielecloudservice": 6.5.10, installed 6.5.10 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "netatmo" : 3.1.0 , installed 3.1.0 Adapter "node-red" : 5.2.1 , installed 5.2.1 Adapter "pvforecast" : 4.1.0 , installed 4.1.0 Adapter "solarwetter" : 1.2.0 , installed 1.2.0 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "weatherunderground": 3.7.0, installed 3.7.0 Objects and States Please stand by - This may take a while Objects: 4617 States: 3800 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 16 *** 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.11:39958 0.0.0.0:* LISTEN 0 1038654 - tcp 0 0 192.168.11.16:1880 0.0.0.0:* LISTEN 1000 335272651 - tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 1041696 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 1041691 - tcp6 0 0 :::80 :::* LISTEN 1000 335408995 - tcp6 0 0 :::8081 :::* LISTEN 1000 1043588 - tcp6 0 0 :::8000 :::* LISTEN 1000 1047588 - udp 0 0 127.0.0.11:34334 0.0.0.0:* 0 1038653 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 335408997 - *** Log File - Last 25 Lines *** 2025-08-02 14:18:50.381 - error: host.iobroker Caught by controller[0]: Node.js v20.19.2 2025-08-02 14:18:50.381 - error: host.iobroker instance system.adapter.nodedmx.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2025-08-02 14:18:50.381 - info: host.iobroker Do not restart adapter system.adapter.nodedmx.0 because disabled or deleted 2025-08-02 15:03:42.501 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 15:03:52.806 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 2025-08-02 15:04:37.307 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 15:04:38.881 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2025-08-02 15:06:08.197 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 2025-08-02 16:03:46.887 - warn: mielecloudservice.0 (397) An error (#1) occurred (TypeError: terminated: read ETIMEDOUT). Handling it in 1.963 seconds to give it a chance to solve itself. 2025-08-02 16:03:48.851 - info: mielecloudservice.0 (397) SSE is trying to reconnect but it seems this won't work. So trying myself by closing and reinitializing. 2025-08-02 16:08:57.821 - info: mielecloudservice.0 (397) Watchdog detected ping failure. Last ping occurred over a minute ago. Trying to handle. 2025-08-02 16:08:57.887 - info: mielecloudservice.0 (397) Server Sent Events-Connection has been established @Miele-API. 2025-08-02 17:19:39.761 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 admin 2025-08-02 17:30:20.975 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 17:30:21.706 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 admin 2025-08-02 17:30:22.905 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 17:30:23.011 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 admin 2025-08-02 17:30:24.363 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 17:36:44.404 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 admin 2025-08-02 18:38:31.836 - info: admin.0 (162) Adapter rating updated 2025-08-02 19:06:22.147 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.52 admin 2025-08-02 19:11:26.440 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 19:11:26.443 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 admin 2025-08-02 19:11:29.612 - info: admin.0 (162) ==> Connected system.user.admin from ::ffff:192.168.13.50 2025-08-02 19:12:16.527 - info: admin.0 (162) <== Disconnect system.user.admin from ::ffff:192.168.13.50 admin ============ Mark until here for C&P ============= -
Das ist nicht vollständig.
-
nun ist es vollständig, sorry hatte dich falsch verstanden
-
Mit Docker kenn ich mich nicht aus. Muss dir wer anders helfen.
-
Ich denke nicht, dass es am Docker liegt, damit hatte ich nie Probleme... letztlich ist da nur der USB Port ein Problem, hab ich aber im Griff... aber die Adapter Fehler sind doch eher was Adapterspezifisches? ich kann die Fehlermeldung nicht deuten....
-
Nicht das ich das genau erklären kann aber du darfst nicht
module.exportsundexportin der selben datei haben.Ich mache mir dafür immer eine
.d.tsdatei um da die Exports bekannt zu machen. Wobei ich da immer nur die Adapterklasse drin habe.Am besten über discord oder telegram im starter fragen. Links dazu findest du auf http://iobroker.dev
