UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[fiddle]

@oliverio du warst aber schnell :)
Gesucht hatte ich nach gyp Errors auch schon, aber die Posts / Umstände klangen beim "anlesen" alle anders, oder wahren diverse Jahre alt... Beim Überfliegen des von dir verlinkten Threads stach mir irgendwo "Radar2" ins Auge - den habe ich hier deaktiviert auch rumoxidieren. Kann ich ja mal rauswerfen. Aber "eigentlich" dürfte das ja nicht stören... eigentlich.

iob diag:

Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Ubuntu 22.04.5 LTS
 Static hostname: iob
       Icon name: computer-vm
         Chassis: vm
  Virtualization: kvm
          Kernel: Linux 5.15.0-160-generic
    Architecture: x86-64
 Hardware Vendor: QEMU
  Hardware Model: Standard PC _i440FX + PIIX, 1996_
OS is similar to: debian

model name      : Common KVM processor
Docker          : false
Virtualization  : kvm
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 20:11:38 up 4 days, 21:17,  2 users,  load average: 0.03, 0.02, 0.00
CPU threads: 8


*** LIFE CYCLE STATUS ***
Operating System codenamed 'jammy' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time!

*** TIME AND TIMEZONES ***
               Local time: Wed 2025-10-29 20:11:39 CET
           Universal time: Wed 2025-10-29 19:11:39 UTC
                 RTC time: Wed 2025-10-29 19:11:39
                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':
broki
HOME=/home/broki
GROUPS=broki adm cdrom sudo dip plugdev lxd iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
Unit display-manager.service could not be found.
Display-Manager: 
Desktop: 
Session:                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:            3.8G        2.2G        690M        1.0M        951M        1.4G
Swap:           4.1G        115M        4.0G
Total:          7.9G        2.3G        4.7G

Active iob-Instances:   17

         3815 M total memory
         2173 M used memory
          907 M active memory
         1920 M inactive memory
          690 M free memory
          133 M buffer memory
          817 M swap cache
         4095 M total swap
          115 M used swap
         3980 M free swap

*** top - Table Of Processes  ***
top - 20:11:39 up 4 days, 21:17,  2 users,  load average: 0.03, 0.02, 0.00
Tasks: 158 total,   1 running, 157 sleeping,   0 stopped,   0 zombie
%Cpu(s):  3.1 us,  1.5 sy,  0.0 ni, 92.3 id,  0.0 wa,  0.0 hi,  3.1 si,  0.0 st
MiB Mem :   3815.3 total,    690.4 free,   2173.0 used,    951.9 buff/cache
MiB Swap:   4096.0 total,   3980.3 free,    115.7 used.   1383.5 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
tmpfs          tmpfs  382M  1.2M  381M   1% /run
/dev/sda2      ext4    17G   15G  1.5G  91% /
tmpfs          tmpfs  1.9G     0  1.9G   0% /dev/shm
tmpfs          tmpfs  5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs  382M  4.0K  382M   1% /run/user/1001

Messages concerning ext4 filesystem in dmesg:
[Fri Oct 24 23:54:24 2025] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[Fri Oct 24 23:54:25 2025] EXT4-fs (sda2): re-mounted. Opts: (null). Quota mode: none.

Show mounted filesystems:
TARGET              SOURCE     FSTYPE   OPTIONS
/                   /dev/sda2  ext4     rw,relatime
|-/snap/core/17212  /dev/loop0 squashfs ro,nodev,relatime,errors=continue
|-/snap/core/17247  /dev/loop1 squashfs ro,nodev,relatime,errors=continue
|-/snap/core20/2599 /dev/loop2 squashfs ro,nodev,relatime,errors=continue
|-/snap/core20/2669 /dev/loop3 squashfs ro,nodev,relatime,errors=continue
|-/snap/lxd/29619   /dev/loop4 squashfs ro,nodev,relatime,errors=continue
`-/snap/lxd/32662   /dev/loop5 squashfs ro,nodev,relatime,errors=continue

Files in neuralgic directories:

/var:
1.4G    /var/
1.1G    /var/lib
741M    /var/lib/snapd
520M    /var/lib/snapd/snaps
264M    /var/lib/apt/lists

Archived and active journals take up 72.0M in the file system.

/opt/iobroker/backups:
111M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
1.3G    /opt/iobroker/iobroker-data/
984M    /opt/iobroker/iobroker-data/history
127M    /opt/iobroker/iobroker-data/files
116M    /opt/iobroker/iobroker-data/backup-objects
47M     /opt/iobroker/iobroker-data/files/admin.admin

The five largest files in iobroker-data are:
21M     /opt/iobroker/iobroker-data/objects.jsonl
9.0M    /opt/iobroker/iobroker-data/states.jsonl
8.6M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js
6.2M    /opt/iobroker/iobroker-data/objects.json.migrated
6.2M    /opt/iobroker/iobroker-data/objects.json.bak.migrated

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

/dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00

*** ZigBee Settings ***

HINT:
Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:
/dev/ttyACM0
Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v22.21.0
/usr/bin/node           v22.21.0
/usr/bin/npm            10.9.4
/usr/bin/npx            10.9.4
/usr/bin/corepack       0.34.0

nodejs:
  Installed: 22.21.0-1nodesource1
  Candidate: 22.21.1-1nodesource1
  Version table:
     22.21.1-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
 *** 22.21.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     22.20.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.19.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.18.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.17.1-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.17.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.16.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.15.1-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.15.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.14.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.13.1-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.13.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.12.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.11.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.10.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.9.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.8.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.7.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.6.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.5.1-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.5.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.4.1-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.4.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.3.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.2.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.1.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.0.0-1nodesource1 600
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     12.22.9~dfsg-1ubuntu3.6 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 deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


 █████  ██      ██           ██████   ██████   ██████  ██████         ██
██   ██ ██      ██          ██       ██    ██ ██    ██ ██   ██     ██  ██
███████ ██      ██          ██   ███ ██    ██ ██    ██ ██   ██         ██
██   ██ ██      ██          ██    ██ ██    ██ ██    ██ ██   ██     ██  ██
██   ██ ███████ ███████      ██████   ██████   ██████  ██████         ██



*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
iob                 iob (version: 7.0.7, hostname: iob           , alive, uptime: 422223)

Core adapters versions
js-controller:  7.0.7
admin:          7.7.2
javascript:     8.9.2

nodejs modules from github:     1
+-- iobroker.sourceanalytix@0.4.12 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.sourceanalytix.git#2eeddf574c25d28a4d21719e2fc606f00408418e)

Adapter State
+ system.adapter.admin.0                  : admin                 : iob                                      -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.backitup.0               : backitup              : iob                                      -  enabled
  system.adapter.daswetter.0              : daswetter             : iob                                      -  enabled
  system.adapter.discovery.0              : discovery             : iob                                      - disabled
  system.adapter.flot.0                   : flot                  : iob                                      -  enabled
+ system.adapter.followthesun.0           : followthesun          : iob                                      -  enabled
+ system.adapter.frigate.0                : frigate               : iob                                      -  enabled
+ system.adapter.history.0                : history               : iob                                      -  enabled
+ system.adapter.hm-rpc.0                 : hm-rpc                : iob                                      -  enabled, port: 0
  system.adapter.ical.0                   : ical                  : iob                                      -  enabled
+ system.adapter.javascript.0             : javascript            : iob                                      -  enabled
  system.adapter.mqtt.0                   : mqtt                  : iob                                      - disabled, port: 1885, bind: 0.0.0.0
+ system.adapter.node-red.0               : node-red              : iob                                      -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.node-red.1               : node-red              : iob                                      -  enabled, port: 1881, bind: 0.0.0.0
+ system.adapter.pi-hole2.0               : pi-hole2              : iob                                      -  enabled, port: 80
  system.adapter.radar2.0                 : radar2                : iob                                      - disabled
  system.adapter.rickshaw.0               : rickshaw              : iob                                      - disabled
+ system.adapter.sonoff.0                 : sonoff                : iob                                      -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.sourceanalytix.0         : sourceanalytix        : iob                                      -  enabled
+ system.adapter.tr-064.0                 : tr-064                : iob                                      -  enabled
+ system.adapter.trashschedule.0          : trashschedule         : iob                                      -  enabled
+ system.adapter.web.0                    : web                   : iob                                      -  enabled, port: 8082, bind: 10.0.10.102, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : iob                                      -  enabled, port: /dev/ttyACM0

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : iob                                      -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.hm-rpc.0                 : hm-rpc                : iob                                      -  enabled, port: 0
+ system.adapter.node-red.0               : node-red              : iob                                      -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.node-red.1               : node-red              : iob                                      -  enabled, port: 1881, bind: 0.0.0.0
+ system.adapter.pi-hole2.0               : pi-hole2              : iob                                      -  enabled, port: 80
+ system.adapter.sonoff.0                 : sonoff                : iob                                      -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : iob                                      -  enabled, port: 8082, bind: 10.0.10.102, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : iob                                      -  enabled, port: /dev/ttyACM0

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-Adapters
Used repository: stable
Adapter    "admin"        : 7.7.2    , installed 7.7.2
Adapter    "backitup"     : 3.3.5    , installed 3.3.5
Adapter    "daswetter"    : 3.2.3    , installed 3.2.3
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "followthesun" : 0.5.2    , installed 0.5.2
Adapter    "frigate"      : 1.3.2    , installed 1.3.2
Adapter    "history"      : 3.0.1    , installed 3.0.1
Adapter    "hm-rpc"       : 2.0.2    , installed 2.0.2
Adapter    "ical"         : 1.17.0   , installed 1.17.0
Adapter    "javascript"   : 8.9.2    , installed 8.9.2
Controller "js-controller": 7.0.7    , installed 7.0.7
Adapter    "mqtt"         : 6.1.4    , installed 6.1.4
Adapter    "node-red"     : 5.2.1    , installed 5.2.1
Adapter    "pi-hole2"     : 1.1.1    , installed 1.1.1
Adapter    "radar2"       : 2.4.0    , installed 2.4.0
Adapter    "rickshaw"     : 1.0.0    , installed 1.0.0
Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
Adapter    "socketio"     : 6.7.1    , installed 6.7.1
Adapter    "sonoff"       : 3.2.1    , installed 3.2.1
Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
Adapter    "trashschedule": 3.3.0    , installed 3.3.0
Adapter    "web"          : 7.0.8    , installed 7.0.8
Adapter    "ws"           : 2.6.2    , installed 2.6.2
Adapter    "zigbee"       : 3.1.5    , installed 3.1.5

Objects and States
Please stand by - This may take a while
Objects:        6950
States:         6263

*** OS-Repositories and Updates ***
Hit:1 https://apt.debmatic.de/debmatic stable InRelease
Hit:2 https://deb.nodesource.com/node_22.x nodistro InRelease
Hit:3 http://de.archive.ubuntu.com/ubuntu jammy InRelease
Hit:4 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:5 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:6 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists...
Pending Updates: 1

*** 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 10.0.10.102:8082        0.0.0.0:*               LISTEN      1002       24487      1683/io.web.0       
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1002       23866      691/iobroker.js-con 
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1002       24778      691/iobroker.js-con 
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      0          23638      907/lighttpd        
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          1265       1/init              
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          22713      763/sshd: /usr/sbin 
tcp        0      0 0.0.0.0:8200            0.0.0.0:*               LISTEN      0          23624      907/lighttpd        
tcp        0      0 0.0.0.0:2001            0.0.0.0:*               LISTEN      0          23634      907/lighttpd        
tcp        0      0 0.0.0.0:2000            0.0.0.0:*               LISTEN      0          23636      907/lighttpd        
tcp        0      0 0.0.0.0:2010            0.0.0.0:*               LISTEN      0          23630      907/lighttpd        
tcp        0      0 0.0.0.0:1999            0.0.0.0:*               LISTEN      0          23628      907/lighttpd        
tcp        0      0 0.0.0.0:8183            0.0.0.0:*               LISTEN      0          25976      1436/ReGaHss.normal 
tcp        0      0 0.0.0.0:8181            0.0.0.0:*               LISTEN      0          23626      907/lighttpd        
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      1002       25142      1636/io.sonoff.0    
tcp        0      0 0.0.0.0:1881            0.0.0.0:*               LISTEN      1002       196967     28439/node-red      
tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      1002       24405      1505/node-red       
tcp        0      0 127.0.0.1:30080         0.0.0.0:*               LISTEN      0          24755      1085/lighttpd       
tcp        0      0 0.0.0.0:32001           0.0.0.0:*               LISTEN      0          25707      1128/rfd            
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      101        22540      670/systemd-resolve 
tcp        0      0 0.0.0.0:31999           0.0.0.0:*               LISTEN      0          25002      1436/ReGaHss.normal 
tcp        0      0 0.0.0.0:9292            0.0.0.0:*               LISTEN      0          23632      907/lighttpd        
tcp        0      0 127.0.0.1:2002          0.0.0.0:*               LISTEN      1002       23410      1567/io.hm-rpc.0    
tcp6       0      0 :::39292                :::*                    LISTEN      0          24186      1186/java           
tcp6       0      0 :::80                   :::*                    LISTEN      0          23623      907/lighttpd        
tcp6       0      0 :::111                  :::*                    LISTEN      0          1268       1/init              
tcp6       0      0 :::22                   :::*                    LISTEN      0          22724      763/sshd: /usr/sbin 
tcp6       0      0 :::8200                 :::*                    LISTEN      0          23625      907/lighttpd        
tcp6       0      0 :::2001                 :::*                    LISTEN      0          23635      907/lighttpd        
tcp6       0      0 :::2000                 :::*                    LISTEN      0          23637      907/lighttpd        
tcp6       0      0 :::2010                 :::*                    LISTEN      0          23631      907/lighttpd        
tcp6       0      0 :::1999                 :::*                    LISTEN      0          23629      907/lighttpd        
tcp6       0      0 :::8181                 :::*                    LISTEN      0          23627      907/lighttpd        
tcp6       0      0 :::8081                 :::*                    LISTEN      1002       24899      1188/io.admin.0     
tcp6       0      0 :::1884                 :::*                    LISTEN      1002       27172      2374/io.frigate.0   
tcp6       0      0 :::9292                 :::*                    LISTEN      0          23633      907/lighttpd        
udp        0      0 0.0.0.0:47981           0.0.0.0:*                           111        1885       682/avahi-daemon: r 
udp        0      0 10.0.10.102:5353        0.0.0.0:*                           1002       239680     35132/io.tr-064.0   
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           111        1883       682/avahi-daemon: r 
udp        0      0 0.0.0.0:60829           0.0.0.0:*                           0          25708      1128/rfd            
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           0          22361      1057/ssdpd          
udp        0      0 127.0.0.1:1998          0.0.0.0:*                           0          25977      1436/ReGaHss.normal 
udp        0      0 127.0.0.1:8182          0.0.0.0:*                           0          24770      1105/hss_led        
udp        0      0 127.0.0.53:53           0.0.0.0:*                           101        22539      670/systemd-resolve 
udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          15877      1/init              
udp        0      0 0.0.0.0:43439           0.0.0.0:*                           0          23747      1054/eq3configd     
udp6       0      0 :::5353                 :::*                                111        1884       682/avahi-daemon: r 
udp6       0      0 :::56577                :::*                                111        1886       682/avahi-daemon: r 
udp6       0      0 :::111                  :::*                                0          15880      1/init              
udp6       0      0 :::41359                :::*                                0          24863      1186/java           

*** Log File - Last 25 Lines ***

2025-10-29 20:00:00.031  - info: host.iob instance system.adapter.ical.0 in version "1.17.0" started with pid 34649
2025-10-29 20:00:00.050  - warn: node-red.0 (1505) Read-only state "zigbee.0.a4c1387580dcecda.link_quality" has been written without ack-flag with value "0"
2025-10-29 20:00:01.921  - info: ical.0 (34649) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.ical, node: v22.21.0, js-controller: 7.0.7
2025-10-29 20:00:02.150  - info: ical.0 (34649) processing URL: ###anonymisiert-weil-verrät-meine-Adresse ;-)###
2025-10-29 20:00:05.012  - info: host.iob instance system.adapter.daswetter.0 in version "3.2.3" started with pid 34667
2025-10-29 20:00:07.234  - info: ical.0 (34649) Terminated (NO_ERROR): Without reason
2025-10-29 20:00:07.758  - info: host.iob instance system.adapter.ical.0 having pid 34649 terminated with code 0 (NO_ERROR)
2025-10-29 20:00:14.380  - info: host.iob instance system.adapter.daswetter.0 having pid 34667 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-10-29 20:00:17.247  - warn: zigbee.0 (1605) DeviceAvailability:ELEVATED: Non-pingable device 0xd0cf5efffe18d918 TRADFRI remote control was last seen '34868.928' seconds ago.
2025-10-29 20:00:17.252  - warn: zigbee.0 (1605) DeviceAvailability:ELEVATED: Non-pingable device 0xccccccfffe2a7209 TRADFRI on/off switch was last seen over 25 hrs ago - setting it offline.
2025-10-29 20:01:47.283  - error: zigbee.0 (1605) Send command to 0x84182600000d877e failed with no error code (Timeout - 58801 - 3 - 34 - 6 - 11 after 10000ms)
2025-10-29 20:01:50.174  - error: zigbee.0 (1605) Send command to 0x7cb03eaa00ac3a41 failed with no error code (Timeout - 27412 - 3 - 38 - 6 - 11 after 10000ms)
2025-10-29 20:02:10.304  - error: zigbee.0 (1605) Send command to 0x7cb03eaa00b1b3a0 failed with no error code (Timeout - 12284 - 3 - 39 - 6 - 11 after 10000ms)
2025-10-29 20:05:17.247  - warn: zigbee.0 (1605) DeviceAvailability:ELEVATED: Non-pingable device 0xd0cf5efffe18d918 TRADFRI remote control was last seen '35168.928' seconds ago.
2025-10-29 20:05:17.253  - warn: zigbee.0 (1605) DeviceAvailability:ELEVATED: Non-pingable device 0xccccccfffe2a7209 TRADFRI on/off switch was last seen over 25 hrs ago - setting it offline.
2025-10-29 20:10:00.039  - warn: node-red.0 (1505) Read-only state "zigbee.0.a4c1387580dcecda.link_quality" has been written without ack-flag with value "0"
2025-10-29 20:10:17.247  - warn: zigbee.0 (1605) DeviceAvailability:ELEVATED: Non-pingable device 0xd0cf5efffe18d918 TRADFRI remote control was last seen '35468.928' seconds ago.
2025-10-29 20:10:17.254  - warn: zigbee.0 (1605) DeviceAvailability:ELEVATED: Non-pingable device 0xccccccfffe2a7209 TRADFRI on/off switch was last seen over 25 hrs ago - setting it offline.
2025-10-29 20:10:23.348  - error: zigbee.0 (1605) Send command to 0x84182600000c7090 failed with no error code (Timeout - 3151 - 3 - 146 - 6 - 11 after 10000ms)
2025-10-29 20:12:01.669  - info: host.iob stopInstance system.adapter.tr-064.0 (force=false, process=true)
2025-10-29 20:12:01.715  - info: host.iob stopInstance system.adapter.tr-064.0 send kill signal
2025-10-29 20:12:02.233  - info: host.iob instance system.adapter.tr-064.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-10-29 20:12:05.511  - info: host.iob instance system.adapter.tr-064.0 in version "4.3.0" started with pid 35132

[Thomas Braun]

@fiddle sagte in gyp Error bei Adapter-Installationen:

Operating System codenamed 'jammy' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time!

Bring das zunächst mal auf einen aktuelleren Stand.

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'

Mach das. Mehr RAM würde ich der VM auch zuteilen.
Deine root-Partition läuft dir voll. Räum da auf oder vergrößere die.

Stell das um:

USB-Devices by-id:

USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

/dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00

*** ZigBee Settings ***

HINT:

Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:

/dev/ttyACM0

[Thomas Braun]

@fiddle

apt policy bluetooth bluez libbluetooth-dev libudev-dev

sagt?

[fiddle]

@thomas-braun release upgrade mache ich, aber nicht sofort. Rest schaue ich mir auch an. Aber läuft ja so... RAM noch nie ausgereizt, Platz auf / habe ich im im Blick, und der Zigbee Stick läuft seit Jahren an dem USB Port und wird nicht umgesteckt. Also das dürfte es doch weit überwiegend bis alles nicht sein warum das gyp muckt... oder wo ist da der Zusammenhang?

apt policy bluetooth bluez libbluetooth-dev libudev-dev....ist ein Intel NUC, wüsste gar nicht was ich da mit Bluetooth will/mache!?

bluetooth:
  Installed: (none)
  Candidate: 5.64-0ubuntu1.4
  Version table:
     5.64-0ubuntu1.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
     5.64-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
bluez:
  Installed: (none)
  Candidate: 5.64-0ubuntu1.4
  Version table:
     5.64-0ubuntu1.4 500
        500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://de.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     5.64-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
libbluetooth-dev:
  Installed: (none)
  Candidate: 5.64-0ubuntu1.4
  Version table:
     5.64-0ubuntu1.4 500
        500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://de.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     5.64-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
libudev-dev:
  Installed: 249.11-0ubuntu3.16
  Candidate: 249.11-0ubuntu3.17
  Version table:
     249.11-0ubuntu3.17 500 (phased 0%)
        500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 *** 249.11-0ubuntu3.16 500
        500 http://de.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     249.11-0ubuntu3 500
        500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

[Thomas Braun]

@fiddle sagte in gyp Error bei Adapter-Installationen:

oder wo ist da der Zusammenhang?

Der Zusammenhang ist: Das sind alles Dinge, die du für ein stabiles System angehen musst.
Das fällt dir früher oder später in der ein oder anderen Form auf die Füße.

wüsste gar nicht was ich da mit Bluetooth will/mache!?

Du nicht, aber ein Adapter will da @stoprocent/noble@1.19.1 installieren. Die genannten Pakete sind aber Voraussetzung für ein erfolgreiches build.

[Thomas Braun]

@fiddle

Hab es jetzt bei mir nachstellen können. Die Meldungen dürften vom radar2-Adapter stammen. Der baut wohl mit aktuellem nodejs nicht mehr (bzw. ein paar der Dependencies). Schmeiß den raus, wenn du den eh nicht verwendest.

Build hier bei mir:

echad@chet:/opt/iobroker $ iob add radar2 --debug
NPM version: 11.6.2
Installing iobroker.radar2@2.4.0... (System call)
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated gauge@2.7.4: This package is no longer supported.

> raw-socket@1.8.1 install
> node-gyp rebuild

gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2
gyp info using node@25.1.0 | linux | arm64
(node:96855) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
gyp info find Python using Python version 3.13.5 found at "/usr/bin/python3"
gyp http GET https://nodejs.org/download/release/v25.1.0/node-v25.1.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v25.1.0/node-v25.1.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v25.1.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v25.1.0/SHASUMS256.txt
gyp ERR! Completion callback never invoked! 
gyp ERR! System Linux 6.12.47+rpt-rpi-v8
gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/raw-socket
gyp ERR! node -v v25.1.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

> usocket@0.3.0 install
> node-gyp rebuild

gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2
gyp info using node@25.1.0 | linux | arm64
(node:96869) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
gyp info find Python using Python version 3.13.5 found at "/usr/bin/python3"
gyp ERR! Completion callback never invoked! 
gyp ERR! System Linux 6.12.47+rpt-rpi-v8
gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/usocket
gyp ERR! node -v v25.1.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

added 14 packages, and removed 1 package in 23s

250 packages are looking for funding
  run `npm fund` for details
host.chet install adapter radar2
upload [8] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/index.html index.html text/html
upload [7] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/index_m.html index_m.html text/html
upload [6] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/network_test.js network_test.js application/javascript
upload [5] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/node_ble_test.js node_ble_test.js application/javascript
upload [4] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/radar2.png radar2.png image/png
upload [3] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/tools.js tools.js application/javascript
upload [2] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/vendors.json vendors.json application/json
upload [1] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/words.js words.js application/javascript
upload [0] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/words.json words.json application/json
host.chet object system.adapter.radar2 created/updated
Updating objects from io-package.json for adapter "radar2" with version "2.4.0"
host.chet create instance radar2
host.chet object system.adapter.radar2.0.alive created
host.chet object system.adapter.radar2.0.connected created
host.chet object system.adapter.radar2.0.compactMode created
host.chet object system.adapter.radar2.0.cpu created
host.chet object system.adapter.radar2.0.cputime created
host.chet object system.adapter.radar2.0.memHeapUsed created
host.chet object system.adapter.radar2.0.memHeapTotal created
host.chet object system.adapter.radar2.0.memRss created
host.chet object system.adapter.radar2.0.uptime created
host.chet object system.adapter.radar2.0.inputCount created
host.chet object system.adapter.radar2.0.outputCount created
host.chet object system.adapter.radar2.0.eventLoopLag created
host.chet object system.adapter.radar2.0.sigKill created
host.chet object system.adapter.radar2.0.logLevel created
host.chet object radar2.0.info created
host.chet object radar2.0.info.connection created
host.chet Set default value of radar2.0.info.connection: false
host.chet object system.adapter.radar2.0 created
echad@chet:/opt/iobroker $ npm ls @stoprocent/noble
iobroker.inst@3.0.0 /opt/iobroker
├─┬ iobroker.ble@0.14.1
│ └── @stoprocent/noble@1.19.1
└─┬ iobroker.radar2@2.4.0
  └── @stoprocent/noble@1.19.1 deduped

echad@chet:/opt/iobroker $

[crunchip]

@thomas-braun die Meldungen hab ich auch und schon ewig, trotzdem funktioniert der Adapter und auch iobroker

[Thomas Braun]

@crunchip

Hier wird der auch installiert und auf den ersten Blick funktioniert der auch.
Trotz der build errors.

Ich wollte auch primär schauen, ob der radar2 auch
@stoprocent/noble reinholt. Tut er:

iobroker.inst@3.0.0 /opt/iobroker
├─┬ iobroker.ble@0.14.1
│ └── @stoprocent/noble@1.19.1
└─┬ iobroker.radar2@2.4.0
  └── @stoprocent/noble@1.19.1 deduped

Aber damit der sauber baut müssen die obigen Pakete für bluetooth installiert sein.

[fiddle]

Danke für eure Befassung.
Habe nun alle meine Todos abgearbeitet. Hat natürlich ein-zwei Dinge "zerlegt", sodass ich erstmal ein paar Umwege in völlig unbekannte Gefilde "moderner" python-Pfad-Irrgärten und wieder heraus finden muste... NETARUS, ich sag's ja....

Verwirrend (für Leute wie mich, oder auch nur mich): Wenn man Adapter XY installiert, warum wird dann (a) Radar2 neu gebaut (wo doch schon ewig installiert, seinerzeit vermutlich ohne diese Fehler), und (b) werden die Fehler die DADURCH entstehen im Log des "neuen" Adapater-Installations-Vorgangs ausgegeben, und das (c) ohne jeden (für Laien...) erkennbaren Hinweis, dass das eben von einem ganz anderen Adapter (Namens...Radar2) stammt.

Hatte Radar2 mal rausgeworfen. Nachdem ich jetzt auch die genannten Bluetooth-Pakete installiert habe, habe ich dann Radar2 nochmal neu installiert. Scheint aber noch nicht sauber zu sein.

$ iobroker add radar2 auto --host iob --debug

NPM version: 10.9.4Installing iobroker.radar2@2.4.0... (System call)

npm warn deprecated npmlog@4.1.2: This package is no longer supported.

npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.

npm warn deprecated gauge@2.7.4: This package is no longer supported.

> @stoprocent/noble@1.19.1 install> node-gyp-build

gyp info using node@22.21.1 | linux | x64

(node:3655) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.(Use `node --trace-deprecation ...` to show where the warning was created)

gyp info find Python using Python version 3.12.3 found at "/usr/bin/python3"

gyp http GET https://nodejs.org/download/release/v22.21.1/node-v22.21.1-headers.tar.gz

gyp http 200 https://nodejs.org/download/release/v22.21.1/node-v22.21.1-headers.tar.gz

gyp http GET https://nodejs.org/download/release/v22.21.1/SHASUMS256.txt

gyp http 200 https://nodejs.org/download/release/v22.21.1/SHASUMS256.txt

gyp ERR! System Linux 6.8.0-87-genericgyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/@stoprocent/noblegyp ERR! node -v v22.21.1gyp ERR! node-gyp -v v7.1.2gyp ERR! Node-gyp failed to build your package.gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

gyp info using node-gyp@7.1.2gyp info using node@22.21.1 | linux | x64

(node:3670) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.(Use `node --trace-deprecation ...` to show where the warning was created)

gyp info find Python using Python version 3.12.3 found at "/usr/bin/python3"

gyp ERR! UNCAUGHT EXCEPTION

gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#<Object>'gyp ERR! stack at createConfigFile (/opt/iobroker/node_modules/node-gyp/lib/configure.js:117:21)gyp ERR! stack at /opt/iobroker/node_modules/node-gyp/lib/configure.js:84:9gyp ERR! stack at FSReqCallback.oncomplete (node:fs:187:23)

gyp ERR! System Linux 6.8.0-87-genericgyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/raw-socketgyp ERR! node -v v22.21.1gyp ERR! node-gyp -v v7.1.2gyp ERR! Node-gyp failed to build your package.gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

> usb@2.16.0 install> node-gyp-build

(node:3702) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.(Use `node --trace-deprecation ...` to show where the warning was created)

gyp ERR! UNCAUGHT EXCEPTION gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#<Object>'gyp ERR! stack at createConfigFile (/opt/iobroker/node_modules/node-gyp/lib/configure.js:117:21)gyp ERR! stack at /opt/iobroker/node_modules/node-gyp/lib/configure.js:84:9gyp ERR! stack at FSReqCallback.oncomplete (node:fs:187:23)gyp ERR! System Linux 6.8.0-87-genericgyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/usocketgyp ERR! node -v v22.21.1gyp ERR! node-gyp -v v7.1.2

gyp ERR! Node-gyp failed to build your package.gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

added 42 packages in 16s

185 packages are looking for funding run `npm fund` for details

host.iob install adapter radar2

upload [8] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/index.html index.html text/html

upload [7] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/index_m.html index_m.html text/html

upload [6] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/network_test.js network_test.js application/javascript

upload [5] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/node_ble_test.js node_ble_test.js application/javascript

upload [4] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/radar2.png radar2.png image/png

upload [2] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/vendors.json vendors.json application/json

upload [1] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/words.js words.js application/javascript

upload [0] radar2.admin /opt/iobroker/node_modules/iobroker.radar2/admin/words.json words.json application/json

host.iob object system.adapter.radar2 created/updated

host.iob create instance radar2

host.iob object system.adapter.radar2.0.alive created

host.iob object system.adapter.radar2.0.connected created

host.iob object system.adapter.radar2.0.cpu created

host.iob object system.adapter.radar2.0.outputCount created

host.iob object radar2.0.info.connection created

host.iob Set default value of radar2.0.info.connection: false

host.iob object system.adapter.radar2.0 created

Process exited with code 0

[Thomas Braun]

@fiddle sagte in gyp Error bei Adapter-Installationen:

Wenn man Adapter XY installiert, warum wird dann (a) Radar2 neu gebaut (wo doch schon ewig installiert, seinerzeit vermutlich ohne diese Fehler), und (b) werden die Fehler die DADURCH entstehen im Log des "neuen" Adapater-Installations-Vorgangs ausgegeben, und das (c) ohne jeden (für Laien...) erkennbaren Hinweis, dass das eben von einem ganz anderen Adapter (Namens...Radar2) stammt.

Weil gyp immer auch abgebrochene Kompilierversuche wieder aufnimmt.

radar2 sollte jetzt aber funktionierend installiert sein.

[OliverIO]

@fiddle sagte in gyp Error bei Adapter-Installationen:

ohne jeden (für Laien...) erkennbaren Hinweis, dass das eben von einem ganz anderen Adapter (Namens...Radar2) stammt

das meiste der Ausgabe stammt direkt vom npm Befehl.
Da kann man nicht so viel daran machen.
Problem von node ist auch der hierarische Aufbau der Abhängigkeiten

• Adapter benötigt 5 weitere Pakete
• jedes dieser Pakete benötigt wieder weitere 5 Pakete
• jedes dieser Pakete benötigt wiederum jeweils 2 Pakete
• und eines davon bringt native Code in C mit und muss deshalb kompiliert werden.

Da ist es manchmal nicht so einfach das Problem tatsächlich zuzuordnen,
Wobei, glaube ich, das Hauptproblem des nicht aktuellen Betriebssystem war.
Sonst hätte das kompillieren auch geklappt.

[fiddle]

@oliverio sagte in gyp Error bei Adapter-Installationen:

Wobei, glaube ich, das Hauptproblem des nicht aktuellen Betriebssystem war.

Aber das habe ich doch nun gestern alles behoben.
Und dennoch ist das Log der erneuten Radar2 Installation voll mit gyp ERR. Also was auch immer er da noch bauen will klappt doch offenbar noch nicht. Ich brauche zwar den radar2 nicht, mache das also nur als Test...aber die Fehler wäre ich schon gern wieder los. Sieht jedenfalls nicht besser aus als vor den Updates des OS.

Kann man das mit dem Abarbeiten ggf früherer teil-gescheiterter Installationen nicht unterbinden? Installiere nur den Adapter den der User will. Wenn bei anderen was war, dan ignoriere das. Wenn der User den "problematischen" Adapter fixen will, kümmere dich dann um die Fehler. Aber nicht bei jedem weiteren.

[Thomas Braun]

@fiddle

npm geht immer über den gesamten tree. Da kannste nix ausschließen, weil npm immer versucht das ganze konsistent zu halten. Wenn es dich stört, schmeiß den radar2 halt raus.
Die Installation läuft ja trotzdem durch:

Process exited with code 0

Edit: Und warum läuft das (zumindest bei mir) durch?
Weil die beiden Module, die bei mir nicht gebaut werden können, nur eine SubDependency eines optionalen Moduls (hier: net-ping) sind:

  "optionalDependencies": {
    "@stoprocent/noble": "1.19.1",
    "net-ping": "^1.2.4"

Und net-ping scheint mir nicht mehr gepflegt zu werden:
https://github.com/nospaceships/node-net-ping/blob/master/README.md
Kann also gut sein, dass es mit aktuellen Setups nicht mehr baut.