YAKAH startet nicht nach js-controller upgrade auf 5.x.x
-
Und jetzt bringst du den ganzen ioBroker auf Stand...
-
@thomas-braun Damit meinst du Adapter updaten? YAKAH ist allerdings bereits neuste Version.
-
Schätze dann wird da wohl der Maintainer des Adapters was dazu sagen müssen.
-
Die ganzen Adapter-Updates die da in der Pipeline hängen. Und/oder schalt das beta-Repo aus.
-
Warum hast du 3 Yahka Instanzen, wusste garnicht, dass das geht..?
Wie hast du avahi konfiguriert? -
@thomas-braun
Getan. Leider ohne Änderung. Es betrifft wie gesagt nur die Instanz 0. Die beiden anderen Instanzen laufen. Auf meiner Hauptinstallation mit folgendem Setup laufen alle 3 Instanzen:YAHKA 1.0.3
Node.js 18.16.0
NPM 9.5.1
js-controller 4.0.24Hier nochmals das Log der Diagnose nach dem Adapterupdate:
Skript v.2023-10-10 *** BASE SYSTEM *** cat: /sys/devices/virtual/dmi/id/sys_vendor: No such file or directory Hardware Vendor : Kernel : x86_64 Userland : amd64 Docker : v9.1.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 09:21:30 up 1 day, 23:50, 0 user, load average: 1.60, 2.08, 2.08 CPU threads: 4 *** Time and Time Zones *** Mon Jan 29 08:21:30 UTC 2024 Mon Jan 29 09:21:30 CET 2024 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 16G 7.5G 317M 488M 9.9G 9.1G Swap: 32G 98M 32G Total: 49G 7.6G 32G 15856 M total memory 7133 M used memory 2215 M active memory 11436 M inactive memory 302 M free memory 1216 M buffer memory 8253 M swap cache 31016 M total swap 93 M used swap 30922 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on overlay overlay 374G 39G 335G 11% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev1 ext4 374G 39G 335G 11% /opt/iobroker tmpfs tmpfs 7.8G 0 7.8G 0% /proc/asound tmpfs tmpfs 7.8G 0 7.8G 0% /proc/acpi tmpfs tmpfs 7.8G 0 7.8G 0% /proc/scsi tmpfs tmpfs 7.8G 0 7.8G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS /opt/iobroker /dev/mapper/cachedev1[/Public/Docker/iobroker-test2] ext4 rw,relatime,noacl,stripe=128,data=ordered,data_err=abort,jqfmt=vfsv1,usrjquota=aquota.user /etc/resolv.conf /dev/mapper/cachedev1[/Public/Docker/container-station-data/lib/docker/containers/ae55d44f77a0fe709d40ccfd0f4e93bc0c129e9d83a542d767a1f71bffe9e096/resolv.conf] ext4 rw,relatime,noacl,stripe=128,data=ordered,data_err=abort,jqfmt=vfsv1,usrjquota=aquota.user /etc/hostname /dev/mapper/cachedev1[/Public/Docker/container-station-data/lib/docker/containers/ae55d44f77a0fe709d40ccfd0f4e93bc0c129e9d83a542d767a1f71bffe9e096/hostname] ext4 rw,relatime,noacl,stripe=128,data=ordered,data_err=abort,jqfmt=vfsv1,usrjquota=aquota.user /etc/hosts /dev/mapper/cachedev1[/Public/Docker/container-station-data/lib/docker/containers/ae55d44f77a0fe709d40ccfd0f4e93bc0c129e9d83a542d767a1f71bffe9e096/hosts] ext4 rw,relatime,noacl,stripe=128,data=ordered,data_err=abort,jqfmt=vfsv1,usrjquota=aquota.user Files in neuralgic directories: /var: 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 87M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 215M /opt/iobroker/iobroker-data/ 172M /opt/iobroker/iobroker-data/files 55M /opt/iobroker/iobroker-data/files/javascript.admin 43M /opt/iobroker/iobroker-data/files/iot.admin 42M /opt/iobroker/iobroker-data/files/iot.admin/static/js The five largest files in iobroker-data are: 42M /opt/iobroker/iobroker-data/objects.jsonl 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map 8.5M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js 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.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages *** 18.19.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main 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.17 admin: 6.13.15 javascript: 7.5.1 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : NAS - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.alexa2.0 : alexa2 : NAS - disabled + system.adapter.backitup.0 : backitup : NAS - enabled system.adapter.boschindego.0 : boschindego : NAS - disabled system.adapter.cloud.0 : cloud : NAS - disabled system.adapter.discovery.0 : discovery : NAS - disabled system.adapter.doorbird.0 : doorbird : NAS - disabled system.adapter.homeconnect.0 : homeconnect : NAS - disabled system.adapter.iot.0 : iot : NAS - disabled system.adapter.javascript.0 : javascript : NAS - disabled system.adapter.mihome-cloud.1 : mihome-cloud : NAS - disabled system.adapter.onkyo.0 : onkyo : NAS - disabled system.adapter.openknx.0 : openknx : NAS - disabled system.adapter.sma-em.0 : sma-em : NAS - disabled system.adapter.telegram.0 : telegram : NAS - disabled, port: 8443, bind: 0.0.0.0 system.adapter.terminal.0 : terminal : NAS - disabled, port: 8088, bind: 0.0.0.0, run as: admin system.adapter.tr-064.0 : tr-064 : NAS - disabled system.adapter.vaillant.0 : vaillant : NAS - disabled system.adapter.vis.0 : vis : NAS - disabled system.adapter.vw-connect.0 : vw-connect : NAS - disabled system.adapter.web.0 : web : NAS - disabled, port: 8090, bind: 0.0.0.0, run as: admin system.adapter.yahka.0 : yahka : NAS - enabled + system.adapter.yahka.1 : yahka : NAS - enabled + system.adapter.yahka.2 : yahka : NAS - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : NAS - enabled, port: 8081, bind: 0.0.0.0 (SSL), 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.12.0 , installed 6.13.15 Adapter "alexa2" : 3.26.4 , installed 3.26.4 Adapter "backitup" : 2.9.8 , installed 2.10.6 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "doorbird" : 1.3.0 , installed 1.3.0 Adapter "homeconnect" : 1.3.0 , installed 1.3.0 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "javascript" : 7.1.6 , installed 7.5.1 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "mihome-cloud" : 0.1.0 , installed 0.1.1 Adapter "onkyo" : 2.1.2 , installed 2.1.2 Adapter "openknx" : 0.6.3 , installed 0.7.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "sma-em" : 1.0.0 , installed 1.0.0 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "telegram" : 3.0.1 , installed 3.0.1 Adapter "terminal" : 1.0.0 , installed 1.0.0 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "vaillant" : 0.1.2 , installed 0.2.1 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "vw-connect" : 0.0.67 , installed 0.0.67 Adapter "web" : 6.1.10 , installed 6.2.3 Adapter "ws" : 2.5.8 , installed 2.5.10 Adapter "yahka" : 1.0.3 , installed 1.0.3 Objects and States Please stand by - This may take a while Objects: 4382 States: 3403 *** 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_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 38475089 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 38477790 - tcp 0 0 127.0.0.11:40349 0.0.0.0:* LISTEN 0 38446094 - tcp6 0 0 :::42505 :::* LISTEN 1000 38899787 - tcp6 0 0 :::35019 :::* LISTEN 1000 38899839 - tcp6 0 0 :::8081 :::* LISTEN 1000 38813362 - udp 0 0 127.0.0.11:45393 0.0.0.0:* 0 38446093 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 1000 38899840 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 1000 38899788 - *** Log File - Last 25 Lines *** 2024-01-29 09:20:48.490 - info: yahka.0 (1911) cleaning up ... 2024-01-29 09:20:48.490 - info: yahka.0 (1911) cleaned up ... 2024-01-29 09:20:48.491 - info: yahka.0 (1911) terminating 2024-01-29 09:20:48.492 - warn: yahka.0 (1911) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-01-29 09:20:48.993 - info: yahka.0 (1911) terminating 2024-01-29 09:20:49.067 - error: host.NAS Caught by controller[0]: [Yahka-0 DAC7] The selected advertiser, "avahi", isn't available on this platform. Reverting to "bonjour-hap" 2024-01-29 09:20:49.068 - error: host.NAS Caught by controller[1]: [Yahka-0 DAC7@Küche Temperatur@Temperatur@Target Temperature] characteristic was supplied illegal value: number 7 exceeded minimum of 10 2024-01-29 09:20:49.068 - error: host.NAS Caught by controller[2]: [Yahka-0 DAC7@Flur Temperatur@Temperatur@Current Temperature] characteristic value expected valid finite number and received "undefined" (undefined) 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[3]: [Yahka-0 DAC7@Treppe Spots@Dimmer@Brightness] characteristic value expected valid finite number and received "undefined" (undefined) 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[4]: [Yahka-0 DAC7@Bad Eltern LED@LED Controller@Brightness] characteristic value expected valid finite number and received "undefined" (undefined) 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[5]: [Yahka-0 DAC7@Szene Kochen@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[6]: [Yahka-0 DAC7@Szene Kochen@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[7]: [Yahka-0 DAC7@Szene TV@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[8]: [Yahka-0 DAC7@Szene TV@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.069 - error: host.NAS Caught by controller[9]: [Yahka-0 DAC7@Szene Gute Nacht@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.070 - error: host.NAS Caught by controller[10]: [Yahka-0 DAC7@Szene Gute Nacht@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.070 - error: host.NAS Caught by controller[11]: [Yahka-0 DAC7@Szene Guten Morgen@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.070 - error: host.NAS Caught by controller[12]: [Yahka-0 DAC7@Szene Guten Morgen@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.070 - error: host.NAS Caught by controller[13]: [Yahka-0 DAC7@Szene Ankommen@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.070 - error: host.NAS Caught by controller[14]: [Yahka-0 DAC7@Szene Ankommen@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.070 - error: host.NAS Caught by controller[15]: [Yahka-0 DAC7@Szene Weihnachten@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.071 - error: host.NAS Caught by controller[16]: [Yahka-0 DAC7@Szene Weihnachten@Szene@On] characteristic value expected boolean and received undefined 2024-01-29 09:20:49.071 - error: host.NAS instance system.adapter.yahka.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-01-29 09:20:49.071 - info: host.NAS Restart adapter system.adapter.yahka.0 because enabled 2024-01-29 09:20:49.071 - warn: host.NAS Do not restart adapter system.adapter.yahka.0 because restart loop detected -
@ilovegym
Wenn du in der Adapteransicht im ioBroker im Adapter auf + drückst, kannst du weitere Instanzen hinzufügen. Da ich mit YAHKA meine knx Geräte integriere habe ich mehr als 150 Geräte und muss diese daher aufteilen. -
@Thomas-Braun Noch eine Idee? Danke im Voraus.
-
Wie sieht denn das log vom Adapter jetzt aus?
-
@wendy2702
Nach wie vor:yahka.0
2024-02-03 17:28:15.978 error Error The pattern "[object Object]" is not a valid ID patternyahka.0
2024-02-03 17:28:15.977 error ReplyError: Error The pattern "[object Object]" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)yahka.0
2024-02-03 17:28:15.976 error unhandled promise rejection: Error The pattern "[object Object]" is not a valid ID patternyahka.0
2024-02-03 17:28:15.975 error 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(). -
@lehmann-maker laut log sieht es für mich so aus als wenn du in Instanz 0 etwas konfiguriert hast was der JS Controller jetzt als falsch interpretiert.
Weiß nicht wieviel Geräte da drin sind sonst würde ich mal eins nach dem anderen löschen und schauen ob der Adapter startet.
