Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Installation
  5. Keine Updates trotz Exit Code 0

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    15
    1
    654

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    632

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    1.9k

Keine Updates trotz Exit Code 0

Geplant Angeheftet Gesperrt Verschoben Installation
24 Beiträge 3 Kommentatoren 173 Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • M Mark

    @Thomas-Braun
    so, neues Image drauf, IO-Broker installiert und versucht das Backup wegen meinen Adaptern zurückzuspielen.
    Shelly und Skript sind aktuell,
    S7 geht nicht, renault findet er gar nicht, vis funktioniert auch nicht.

    Aber ich glaube das Hauptproblem ist folgendes:

    	iobroker npm-install: npm error code 1npm error path /opt/iobroker/node_modules/node-snap7npm error command failednpm error command sh -c prebuild-install || node-gyp rebuildnpm error (node:4373) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error Traceback (most recent call last):npm error File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 42, in <module>npm error import gyp # noqa: E402npm error ^^^^^^^^^^npm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 9, in <module>npm error import gyp.inputnpm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 19, in <module>npm error from distutils.version import StrictVersionnpm error ModuleNotFoundError: No module named 'distutils'npm error gyp ERR! configure error npm error gyp ERR! stack Error: `gyp` failed with exit code: 1npm error gyp ERR! stack at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:259:16)npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)npm error gyp ERR! System Linux 6.12.47+rpt-rpi-v8npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/node-snap7npm error gyp ERR! node -v v22.21.0npm error gyp ERR! node-gyp -v v8.4.1npm error gyp ERR! not oknpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-12-31T11_06_51_368Z-debug-0.loghost.raspberrypi Cannot install iobroker.s7@1.5.0: 1
    

    iob diag Ergibt folgende Ausgabe:

    
    ```bash
    Script v.2025-08-09
    
    *** BASE SYSTEM ***
    Operating System: Debian GNU/Linux 13 (trixie)
     Static hostname: raspberrypi
           Icon name: computer
              Kernel: Linux 6.12.47+rpt-rpi-v8
        Architecture: arm64
    OS is similar to:
    
    Model           : Raspberry Pi 4 Model B Rev 1.1
    Docker          : false
    Virtualization  : none
    Kernel          : aarch64
    Userland        : 64 bit
    
    Systemuptime and Load:
     12:13:12 up 17 min,  1 user,  load average: 0.44, 0.91, 0.97
    CPU threads: 4
    
    
    *** LIFE CYCLE STATUS ***
    Operating System is the current Debian stable version codenamed 'trixie'!
    
    *** RASPBERRY THROTTLING ***
    Current issues:
    No throttling issues detected.
    
    Previously detected issues:
    No throttling issues detected.
    
    *** TIME AND TIMEZONES ***
                   Local time: Wed 2025-12-31 12:13:12 CET
               Universal time: Wed 2025-12-31 11:13:12 UTC
                     RTC time: n/a
                    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':
    mark
    HOME=/home/mark
    GROUPS=mark adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input iobroker
    
    User that is running 'js-controller':
    iobroker
    HOME=/home/iobroker
    SUDO_HOME=/home/mark
    GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
    
    *** DISPLAY-SERVER SETUP ***
    Display-Server:         false
    Unit display-manager.service could not be found.
    Display-Manager:
    Desktop:
    Session:                tty
    
    *** MEMORY ***
                   total        used        free      shared  buff/cache   available
    Mem:            4.0G        1.2G        2.0G         12M        861M        2.8G
    Swap:           2.1G          0B        2.1G
    Total:          6.1G        1.2G        4.2G
    
    Active iob-Instances:   10
    
             3796 M total memory
             1143 M used memory
             1106 M active memory
              495 M inactive memory
             1930 M free memory
               98 M buffer memory
              723 M swap cache
             2047 M total swap
                0 M used swap
             2047 M free swap
    
    *** top - Table Of Processes  ***
    top - 12:13:12 up 17 min,  1 user,  load average: 0.49, 0.91, 0.97
    Tasks: 185 total,   1 running, 184 sleeping,   0 stopped,   0 zombie
    %Cpu(s):  0.0 us,  2.1 sy,  0.0 ni, 97.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
    MiB Mem :   3796.7 total,   1928.8 free,   1144.7 used,    822.5 buff/cache
    MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   2652.0 avail Mem
    
    *** FAILED SERVICES ***
    
      UNIT LOAD ACTIVE SUB DESCRIPTION
    
    0 loaded units listed.
    
    
    *** DMESG CRITICAL ERRORS ***
    No critical errors detected
    
    *** FILESYSTEM ***
    Filesystem     Type      Size  Used Avail Use% Mounted on
    udev           devtmpfs  1.6G     0  1.6G   0% /dev
    tmpfs          tmpfs     760M  9.4M  751M   2% /run
    /dev/mmcblk0p2 ext4      117G  6.4G  106G   6% /
    tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
    tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
    tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
    tmpfs          tmpfs     1.9G  2.8M  1.9G   1% /tmp
    /dev/mmcblk0p1 vfat      510M   74M  437M  15% /boot/firmware
    tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
    tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyS0.service
    tmpfs          tmpfs     380M  8.0K  380M   1% /run/user/1000
    
    Messages concerning ext4 filesystem in dmesg:
    [Wed Dec 31 11:55:26 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=DC:A6:32:3A:14:63 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=4c646aa6-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
    [Wed Dec 31 11:55:30 2025] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
    [Wed Dec 31 11:55:30 2025] EXT4-fs (mmcblk0p2): mounted filesystem 21724cc6-e5a3-48a1-8643-7917dba3a9fb ro with ordered data mode. Quota mode: none.
    [Wed Dec 31 11:55:33 2025] EXT4-fs (mmcblk0p2): re-mounted 21724cc6-e5a3-48a1-8643-7917dba3a9fb r/w.
    
    Show mounted filesystems:
    TARGET           SOURCE         FSTYPE OPTIONS
    /                /dev/mmcblk0p2 ext4   rw,noatime
    `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
    
    Files in neuralgic directories:
    
    /var:
    2.4G    /var/
    231M    /var/cache
    225M    /var/cache/apt
    177M    /var/lib
    145M    /var/lib/apt
    
    Archived and active journals take up 8M in the file system.
    
    /opt/iobroker/backups:
    152M    /opt/iobroker/backups/
    
    /opt/iobroker/iobroker-data:
    248M    /opt/iobroker/iobroker-data/
    226M    /opt/iobroker/iobroker-data/files
    47M     /opt/iobroker/iobroker-data/files/admin.admin
    46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets
    46M     /opt/iobroker/iobroker-data/files/admin.admin/custom
    
    The five largest files in iobroker-data are:
    24M     /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map
    19M     /opt/iobroker/iobroker-data/objects.jsonl
    9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json
    9.3M    /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js
    8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-C_W7K-9p.js
    
    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-1a86_USB2.0-Ser_-if00-port0
    /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_B002A4TN-if00-port0
    /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0033-if00-port0
    /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0058-if00-port0
    /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0068-if00-port0
    
    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.0-1nodesource1
      Version table:
     *** 22.21.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
            100 /var/lib/dpkg/status
         22.20.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.19.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.18.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.17.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.17.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.16.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.15.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.15.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.14.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.13.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.13.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.12.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.11.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.10.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.9.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.8.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.7.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.6.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.5.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.5.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.4.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.4.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.3.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.2.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.1.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         22.0.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
         20.19.2+dfsg-1 500
            500 http://deb.debian.org/debian trixie/main arm64 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:
    raspberrypi         raspberrypi (version: 7.0.7, hostname: raspberrypi   , alive, uptime: 664)
    
    Core adapters versions
    js-controller:  7.0.7
    admin:          7.7.19
    javascript:     9.0.11
    
    nodejs modules from github:     0
    
    Adapter State
    + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
    + system.adapter.backitup.0               : backitup              : raspberrypi                              -  enabled
      system.adapter.discovery.0              : discovery             : raspberrypi                              - disabled
      system.adapter.fritzdect.0              : fritzdect             : raspberrypi                              - disabled
      system.adapter.icons-icons8.0           : icons-icons8          : raspberrypi                              - disabled
    + system.adapter.javascript.0             : javascript            : raspberrypi                              -  enabled
    + system.adapter.modbus.0                 : modbus                : raspberrypi                              -  enabled
    + system.adapter.modbus.1                 : modbus                : raspberrypi                              -  enabled
    + system.adapter.oekofen-json.0           : oekofen-json          : raspberrypi                              -  enabled
      system.adapter.renault.0                : renault               : raspberrypi                              -  enabled
      system.adapter.roborock.0               : roborock              : raspberrypi                              - disabled
      system.adapter.rpi2.0                   : rpi2                  : raspberrypi                              - disabled
      system.adapter.s7.0                     : s7                    : raspberrypi                              - disabled
      system.adapter.s7.1                     : s7                    : raspberrypi                              - disabled
      system.adapter.s7.2                     : s7                    : raspberrypi                              - disabled
      system.adapter.shelly.0                 : shelly                : raspberrypi                              - disabled, port: 1883, bind: 192.168.188.149
    + system.adapter.smartmeter.0             : smartmeter            : raspberrypi                              -  enabled
    + system.adapter.smartmeter.1             : smartmeter            : raspberrypi                              -  enabled
    + system.adapter.smartmeter.2             : smartmeter            : raspberrypi                              -  enabled
      system.adapter.sql.0                    : sql                   : raspberrypi                              - disabled, port: 3306
      system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : raspberrypi                              - disabled
      system.adapter.vis-icontwo.0            : vis-icontwo           : raspberrypi                              - disabled
      system.adapter.vis.0                    : vis                   : raspberrypi                              -  enabled
      system.adapter.web.0                    : web                   : raspberrypi                              - disabled, port: 8082, bind: 0.0.0.0, run as: admin
    
    + instance is alive
    
    Enabled adapters with bindings
    + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
    
    ioBroker-Repositories
    ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
    │ (index) │ name     │ url                                                     │ auto upgrade │
    ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
    │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
    │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
    └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
    
    Active repo(s): stable
    Upgrade policy: none
    
    Installed ioBroker-Adapters
    Used repository: stable
    Adapter    "admin"        : 7.7.19   , installed 7.7.19
    Adapter    "backitup"     : 3.3.10   , installed 3.3.10
    Adapter    "discovery"    : 5.0.0    , installed 5.0.0
    Adapter    "fritzdect"    : 2.6.2    , installed 2.6.2
    Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
    Adapter    "javascript"   : 9.0.11   , installed 9.0.11
    Controller "js-controller": 7.0.7    , installed 7.0.7
    Adapter    "modbus"       : 6.3.2    , installed 6.3.2
    Adapter    "oekofen-json" : 2.0.0    , installed 2.0.0
    Adapter    "roborock"     : 0.6.18   , installed 0.6.18
    Adapter    "shelly"       : 10.4.1   , installed 10.4.1
    Adapter    "smartmeter"   : 3.4.0    , installed 3.4.0
    Adapter    "socketio"     : 6.7.1    , installed 7.0.8
    Adapter    "sql"          : 3.0.1    , installed 3.0.1
    Adapter    "vis"          : 1.5.6    , installed 1.5.6
    Adapter    "vis-hqwidgets": 1.5.1    , installed 1.5.1
    Adapter    "vis-icontwo"  : 1.18.0   , installed 1.18.0
    Adapter    "web"          : 7.0.8    , installed 7.0.8
    Adapter    "ws"           : 2.6.2    , installed 3.0.19
    
    Objects and States
    Please stand by - This may take a while
    Objects:        14741
    States:         12445
    
    *** OS-Repositories and Updates ***
    W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
    Hit:1 http://deb.debian.org/debian trixie InRelease
    Hit:2 http://deb.debian.org/debian trixie-updates InRelease
    Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
    Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
    Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
    Reading package lists...
    W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
    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:22              0.0.0.0:*               LISTEN      0          8508       1074/sshd: /usr/sbi
    tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          5092       1/init
    tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       17085      3085/iobroker.js-co
    tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       17080      3085/iobroker.js-co
    tcp6       0      0 :::22                   :::*                    LISTEN      0          8510       1074/sshd: /usr/sbi
    tcp6       0      0 :::111                  :::*                    LISTEN      0          159        1/init
    tcp6       0      0 :::8081                 :::*                    LISTEN      1001       14279      3110/io.admin.0
    udp        0      0 0.0.0.0:5353            0.0.0.0:*                           101        7456       655/avahi-daemon: r
    udp        0      0 0.0.0.0:34437           0.0.0.0:*                           101        7458       655/avahi-daemon: r
    udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          1799       1/init
    udp6       0      0 fe80::dea6:32ff:fe3:546 :::*                                0          8565       691/NetworkManager
    udp6       0      0 :::43813                :::*                                101        7459       655/avahi-daemon: r
    udp6       0      0 :::5353                 :::*                                101        7457       655/avahi-daemon: r
    udp6       0      0 :::111                  :::*                                0          5093       1/init
    
    *** Log File - Last 25 Lines ***
    
    2025-12-31 12:08:00.457  - info: modbus.1 (3233) Disconnected from slave
    2025-12-31 12:09:02.487  - warn: smartmeter.0 (3292) No or too long answer from Serial Device after last request.
    2025-12-31 12:09:04.536  - warn: smartmeter.1 (3325) No or too long answer from Serial Device after last request.
    2025-12-31 12:09:07.868  - warn: smartmeter.2 (3337) No or too long answer from Serial Device after last request.
    2025-12-31 12:09:28.150  - info: modbus.1 (3233) Connected to slave
    2025-12-31 12:09:33.151  - warn: modbus.1 (3233) Error: undefined
    2025-12-31 12:09:33.152  - error: modbus.1 (3233) Request timed out.
    2025-12-31 12:09:33.153  - warn: modbus.1 (3233) [DevID_2] Poll error count: 5 code: {"err":"timeout","timeout":5000}
    2025-12-31 12:09:34.152  - info: modbus.1 (3233) Disconnected from slave
    2025-12-31 12:11:01.846  - info: modbus.1 (3233) Connected to slave
    2025-12-31 12:11:06.849  - warn: modbus.1 (3233) Error: undefined
    2025-12-31 12:11:06.849  - error: modbus.1 (3233) Request timed out.
    2025-12-31 12:11:06.850  - warn: modbus.1 (3233) [DevID_2] Poll error count: 6 code: {"err":"timeout","timeout":5000}
    2025-12-31 12:11:07.672  - warn: smartmeter.0 (3292) No or too long answer from Serial Device after last request.
    2025-12-31 12:11:07.850  - info: modbus.1 (3233) Disconnected from slave
    2025-12-31 12:11:09.718  - warn: smartmeter.1 (3325) No or too long answer from Serial Device after last request.
    2025-12-31 12:11:13.047  - warn: smartmeter.2 (3337) No or too long answer from Serial Device after last request.
    2025-12-31 12:12:35.542  - info: modbus.1 (3233) Connected to slave
    2025-12-31 12:12:40.545  - warn: modbus.1 (3233) Error: undefined
    2025-12-31 12:12:40.546  - error: modbus.1 (3233) Request timed out.
    2025-12-31 12:12:40.547  - warn: modbus.1 (3233) [DevID_2] Poll error count: 7 code: {"err":"timeout","timeout":5000}
    2025-12-31 12:12:41.546  - info: modbus.1 (3233) Disconnected from slave
    2025-12-31 12:13:12.855  - warn: smartmeter.0 (3292) No or too long answer from Serial Device after last request.
    2025-12-31 12:13:14.906  - warn: smartmeter.1 (3325) No or too long answer from Serial Device after last request.
    2025-12-31 12:13:18.230  - warn: smartmeter.2 (3337) No or too long answer from Serial Device after last request.
    
    

    ============ Mark until here for C&P =============

    
    sudo apt update
    sudo apt upgrade wurde gemacht und läuft
    iob fix wurde auch ausgeführt und läuft fehlerfrei durch
    HomoranH Nicht stören
    HomoranH Nicht stören
    Homoran
    Global Moderator Administrators
    schrieb am zuletzt editiert von
    #10

    @Mark sagte in Keine Updates trotz Exit Code 0:

    neues Image drauf

    heisst was genau?

    kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

    M 1 Antwort Letzte Antwort
    0
    • HomoranH Homoran

      @Mark sagte in Keine Updates trotz Exit Code 0:

      neues Image drauf

      heisst was genau?

      M Offline
      M Offline
      Mark
      schrieb am zuletzt editiert von
      #11

      @Homoran
      hab mit dem Pi-Imager eine neue SD-Karte mit Trixi erstellt.
      Danach mit SSH eingeloggt und IOB installiert.
      Updates, gestartet und dann versucht das Backup einzuspielen

      HomoranH 1 Antwort Letzte Antwort
      0
      • M Mark

        @Homoran
        hab mit dem Pi-Imager eine neue SD-Karte mit Trixi erstellt.
        Danach mit SSH eingeloggt und IOB installiert.
        Updates, gestartet und dann versucht das Backup einzuspielen

        HomoranH Nicht stören
        HomoranH Nicht stören
        Homoran
        Global Moderator Administrators
        schrieb am zuletzt editiert von
        #12

        @Mark sagte in Keine Updates trotz Exit Code 0:

        Danach mit SSH eingeloggt und IOB installiert.

        und da war diag sauber?

        kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

        M 1 Antwort Letzte Antwort
        0
        • HomoranH Homoran

          @Mark sagte in Keine Updates trotz Exit Code 0:

          Danach mit SSH eingeloggt und IOB installiert.

          und da war diag sauber?

          M Offline
          M Offline
          Mark
          schrieb am zuletzt editiert von
          #13

          @Homoran
          ich kenne mich leider zu wenig aus um das wirklich beurteilen zu können.
          Hab das diag aber oben gepostet und würde als Laie sagen, ja, ist sauber

          HomoranH 1 Antwort Letzte Antwort
          0
          • M Mark

            @Homoran
            ich kenne mich leider zu wenig aus um das wirklich beurteilen zu können.
            Hab das diag aber oben gepostet und würde als Laie sagen, ja, ist sauber

            HomoranH Nicht stören
            HomoranH Nicht stören
            Homoran
            Global Moderator Administrators
            schrieb am zuletzt editiert von
            #14

            @Mark sagte in Keine Updates trotz Exit Code 0:

            Hab das diag aber oben geposte

            war das von vor dem Restore?

            kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

            M 1 Antwort Letzte Antwort
            0
            • HomoranH Homoran

              @Mark sagte in Keine Updates trotz Exit Code 0:

              Hab das diag aber oben geposte

              war das von vor dem Restore?

              M Offline
              M Offline
              Mark
              schrieb am zuletzt editiert von
              #15

              @Homoran
              nein, jetzt aktuell

              HomoranH 1 Antwort Letzte Antwort
              0
              • M Mark

                @Homoran
                nein, jetzt aktuell

                HomoranH Nicht stören
                HomoranH Nicht stören
                Homoran
                Global Moderator Administrators
                schrieb am zuletzt editiert von
                #16

                @Mark aber es geht auch darum wann es zu den Problemen kommt.

                @Mark sagte in Keine Updates trotz Exit Code 0:

                das Hauptproblem

                wo kommt denn das log her?
                ...und von wann?

                kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                M 1 Antwort Letzte Antwort
                0
                • HomoranH Homoran

                  @Mark aber es geht auch darum wann es zu den Problemen kommt.

                  @Mark sagte in Keine Updates trotz Exit Code 0:

                  das Hauptproblem

                  wo kommt denn das log her?
                  ...und von wann?

                  M Offline
                  M Offline
                  Mark
                  schrieb am zuletzt editiert von
                  #17

                  @Homoran
                  ist auch aktuell.
                  Die Fehler entstehen, weil die Adapter nicht richtig funktionieren. (Smartmeter und Modbus). Sind aber die gleichen einstellungen wie am alten System und da hat es funktioniert. Hab die Adapter jetzt gestoppt.

                  Im protokoll kommt aber immer wieder:

                  	iobroker npm-install: npm error code 1npm error path /opt/iobroker/node_modules/node-snap7npm error command failednpm error command sh -c prebuild-install || node-gyp rebuildnpm error (node:8282) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error Traceback (most recent call last):npm error File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 42, in <module>npm error import gyp # noqa: E402npm error ^^^^^^^^^^npm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 9, in <module>npm error import gyp.inputnpm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 19, in <module>npm error from distutils.version import StrictVersionnpm error ModuleNotFoundError: No module named 'distutils'npm error gyp ERR! configure error npm error gyp ERR! stack Error: `gyp` failed with exit code: 1npm error gyp ERR! stack at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:259:16)npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)npm error gyp ERR! System Linux 6.12.47+rpt-rpi-v8npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/node-snap7npm error gyp ERR! node -v v22.21.0npm error gyp ERR! node-gyp -v v8.4.1npm error gyp ERR! not oknpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-12-31T11_31_33_580Z-debug-0.log
                  
                  HomoranH 2 Antworten Letzte Antwort
                  0
                  • M Mark

                    @Homoran
                    ist auch aktuell.
                    Die Fehler entstehen, weil die Adapter nicht richtig funktionieren. (Smartmeter und Modbus). Sind aber die gleichen einstellungen wie am alten System und da hat es funktioniert. Hab die Adapter jetzt gestoppt.

                    Im protokoll kommt aber immer wieder:

                    	iobroker npm-install: npm error code 1npm error path /opt/iobroker/node_modules/node-snap7npm error command failednpm error command sh -c prebuild-install || node-gyp rebuildnpm error (node:8282) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error Traceback (most recent call last):npm error File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 42, in <module>npm error import gyp # noqa: E402npm error ^^^^^^^^^^npm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 9, in <module>npm error import gyp.inputnpm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 19, in <module>npm error from distutils.version import StrictVersionnpm error ModuleNotFoundError: No module named 'distutils'npm error gyp ERR! configure error npm error gyp ERR! stack Error: `gyp` failed with exit code: 1npm error gyp ERR! stack at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:259:16)npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)npm error gyp ERR! System Linux 6.12.47+rpt-rpi-v8npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/node-snap7npm error gyp ERR! node -v v22.21.0npm error gyp ERR! node-gyp -v v8.4.1npm error gyp ERR! not oknpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-12-31T11_31_33_580Z-debug-0.log
                    
                    HomoranH Nicht stören
                    HomoranH Nicht stören
                    Homoran
                    Global Moderator Administrators
                    schrieb am zuletzt editiert von
                    #18

                    @Mark sagte in Keine Updates trotz Exit Code 0:

                    Im protokoll kommt aber immer wieder:

                    in welchem Protokoll?

                    Das iobroker Protokoll ist gänzlich anders formatiert

                    kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                    M 1 Antwort Letzte Antwort
                    0
                    • M Mark

                      @Homoran
                      ist auch aktuell.
                      Die Fehler entstehen, weil die Adapter nicht richtig funktionieren. (Smartmeter und Modbus). Sind aber die gleichen einstellungen wie am alten System und da hat es funktioniert. Hab die Adapter jetzt gestoppt.

                      Im protokoll kommt aber immer wieder:

                      	iobroker npm-install: npm error code 1npm error path /opt/iobroker/node_modules/node-snap7npm error command failednpm error command sh -c prebuild-install || node-gyp rebuildnpm error (node:8282) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error Traceback (most recent call last):npm error File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 42, in <module>npm error import gyp # noqa: E402npm error ^^^^^^^^^^npm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 9, in <module>npm error import gyp.inputnpm error File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 19, in <module>npm error from distutils.version import StrictVersionnpm error ModuleNotFoundError: No module named 'distutils'npm error gyp ERR! configure error npm error gyp ERR! stack Error: `gyp` failed with exit code: 1npm error gyp ERR! stack at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:259:16)npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)npm error gyp ERR! System Linux 6.12.47+rpt-rpi-v8npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/node-snap7npm error gyp ERR! node -v v22.21.0npm error gyp ERR! node-gyp -v v8.4.1npm error gyp ERR! not oknpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-12-31T11_31_33_580Z-debug-0.log
                      
                      HomoranH Nicht stören
                      HomoranH Nicht stören
                      Homoran
                      Global Moderator Administrators
                      schrieb am zuletzt editiert von
                      #19

                      @Mark sagte in Keine Updates trotz Exit Code 0:

                      Die Fehler entstehen, weil die Adapter nicht richtig funktionieren

                      eher anders rum:
                      wegen Fehlern laufen die Adapter nicht.

                      um das herauszufinden muss man aber auch wissen wann was wie genau zu welchen exakten Meldungen führt.

                      Wie lwnge hast du nach dem Restore gewartet?
                      Der Bau der Adapter fängt dann erst an und sollte nicht gestört werden

                      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                      1 Antwort Letzte Antwort
                      0
                      • HomoranH Homoran

                        @Mark sagte in Keine Updates trotz Exit Code 0:

                        Im protokoll kommt aber immer wieder:

                        in welchem Protokoll?

                        Das iobroker Protokoll ist gänzlich anders formatiert

                        M Offline
                        M Offline
                        Mark
                        schrieb am zuletzt editiert von
                        #20

                        @Homoran
                        sorry, ich hab nur die Fehlermeldung rauskopiert. Hier mal der heutige Log:

                        iobroker.current.htm

                        Ist also vom ersten starten bis jetzt

                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • M Mark

                          @Homoran
                          sorry, ich hab nur die Fehlermeldung rauskopiert. Hier mal der heutige Log:

                          iobroker.current.htm

                          Ist also vom ersten starten bis jetzt

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #21

                          @Mark

                          Aber ich glaube das Hauptproblem ist folgendes:

                          Installier python3-setuptools nach.

                          sudo apt install python3-setuptools
                          

                          Linux-Werkzeugkasten:
                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                          NodeJS Fixer Skript:
                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                          M 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @Mark

                            Aber ich glaube das Hauptproblem ist folgendes:

                            Installier python3-setuptools nach.

                            sudo apt install python3-setuptools
                            
                            M Offline
                            M Offline
                            Mark
                            schrieb am zuletzt editiert von
                            #22

                            @Thomas-Braun
                            hab ich gemacht.

                            host.raspberrypi
                            	2025-12-31 14:03:00.697	info	iobroker exit 25
                            host.raspberrypi
                            	2025-12-31 14:02:59.649	error	iobroker host.raspberrypi Cannot install iobroker.rpi2@2.4.0: 1
                            host.raspberrypi
                            	2025-12-31 14:02:59.645	error	iobroker npm error code 1npm error path /opt/iobroker/node_modules/opengpionpm error command failednpm error command sh -c node-gyp rebuildnpm error make: Entering directory '/opt/iobroker/node_modules/opengpio/build'npm error CXX(target) Release/obj.target/opengpio/cpp/opengpio.onpm error make: Leaving directory '/opt/iobroker/node_modules/opengpio/build'npm error (node:10247) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioInput(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:14:17: error: expected primary-expression before ‘line’npm error 14 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:19:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 19 | line.request({resourceName, gpiod::line_request::DIRECTION_INPUT, 0});npm error | ^~~~npm error | gpiod::linenpm error In file included from /usr/include/gpiodcxx/chip.hpp:21,npm error from /usr/include/gpiod.hpp:27,npm error from ../cpp/opengpio.cpp:3:npm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:19:58: error: ‘DIRECTION_INPUT’ is not a member of ‘gpiod::line_request’npm error 19 | line.request({resourceName, gpiod::line_request::DIRECTION_INPUT, 0});npm error | ^~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:28:62: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:30:22: error: ‘line’ is not capturednpm error 30 | bool value = line.get_value();npm error | ^~~~npm error ../cpp/opengpio.cpp:28:66: note: the lambda has no capture-defaultnpm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:28:62: note: ‘<typeprefixerror>line’ declared herenpm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:34:52: error: ‘line’ is not capturednpm error 34 | { line.release(); });npm error | ^~~~npm error ../cpp/opengpio.cpp:33:67: note: the lambda has no capture-defaultnpm error 33 | Napi::Function cleanup = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:28:62: note: ‘<typeprefixerror>line’ declared herenpm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioOutput(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:49:17: error: expected primary-expression before ‘line’npm error 49 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:54:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 54 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:54:58: error: ‘DIRECTION_OUTPUT’ is not a member of ‘gpiod::line_request’npm error 54 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:63:62: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:66:9: error: ‘line’ is not capturednpm error 66 | line.set_value(value); });npm error | ^~~~npm error ../cpp/opengpio.cpp:63:66: note: the lambda has no capture-defaultnpm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:63:62: note: ‘<typeprefixerror>line’ declared herenpm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:69:52: error: ‘line’ is not capturednpm error 69 | { line.release(); });npm error | ^~~~npm error ../cpp/opengpio.cpp:68:67: note: the lambda has no capture-defaultnpm error 68 | Napi::Function cleanup = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:63:62: note: ‘<typeprefixerror>line’ declared herenpm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: At global scope:npm error ../cpp/opengpio.cpp:81:12: error: ‘line’ in namespace ‘gpiod’ does not name a typenpm error 81 | gpiod::line line;npm error | ^~~~npm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioWatch(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:92:17: error: expected primary-expression before ‘line’npm error 92 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:100:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 100 | line.request({resourceName, gpiod::line_request::EVENT_BOTH_EDGES, 0}, 0);npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:100:58: error: ‘EVENT_BOTH_EDGES’ is not a member of ‘gpiod::line_request’npm error 100 | line.request({resourceName, gpiod::line_request::EVENT_BOTH_EDGES, 0}, 0);npm error | ^~~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:109:62: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:111:22: error: ‘line’ is not capturednpm error 111 | bool value = line.get_value();npm error | ^~~~npm error ../cpp/opengpio.cpp:109:66: note: the lambda has no capture-defaultnpm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:109:62: note: ‘<typeprefixerror>line’ declared herenpm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioWatch(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:115:11: error: ‘struct WatchContext’ has no member named ‘line’npm error 115 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:127:25: error: expected primary-expression before ‘line’npm error 127 | gpiod::line line = data->line;npm error | ^~~~npm error ../cpp/opengpio.cpp:131:33: error: ‘line’ is not capturednpm error 131 | bool hasEvent = line.event_wait(chrono::milliseconds(1));npm error | ^~~~npm error ../cpp/opengpio.cpp:124:10: note: the lambda has no capture-defaultnpm error 124 | [](uv_work_t *req)npm error | ^npm error ../cpp/opengpio.cpp:109:62: note: ‘<typeprefixerror>line’ declared herenpm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp:134:28: error: ‘line_event’ is not a member of ‘gpiod’; did you mean ‘info_event’?npm error 134 | gpiod::line_event event = line.event_read();npm error | ^~~~~~~~~~npm error | info_eventnpm error ../cpp/opengpio.cpp:135:34: error: ‘event’ was not declared in this scope; did you mean ‘servent’?npm error 135 | bool value = event.event_type == gpiod::line_event::RISING_EDGE ? true : false;npm error | ^~~~~npm error | serventnpm error ../cpp/opengpio.cpp:135:61: error: ‘gpiod::line_event’ has not been declarednpm error 135 | bool value = event.event_type == gpiod::line_event::RISING_EDGE ? true : false;npm error | ^~~~~~~~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:147:19: error: ‘struct WatchContext’ has no member named ‘line’npm error 147 | data->line.release();npm error | ^~~~npm error ../cpp/opengpio.cpp: At global scope:npm error ../cpp/opengpio.cpp:168:12: error: ‘line’ in namespace ‘gpiod’ does not name a typenpm error 168 | gpiod::line line;npm error | ^~~~npm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioPwm(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:196:17: error: expected primary-expression before ‘line’npm error 196 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:201:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 201 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:201:58: error: ‘DIRECTION_OUTPUT’ is not a member of ‘gpiod::line_request’npm error 201 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:213:11: error: ‘struct PwmContext’ has no member named ‘line’npm error 213 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp:213:18: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 213 | data->line = line;npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:224:25: error: expected primary-expression before ‘line’npm error 224 | gpiod::line line = data->line;npm error | ^~~~npm error ../cpp/opengpio.cpp:264:17: error: ‘line’ is not capturednpm error 264 | line.set_value(true);npm error | ^~~~npm error ../cpp/opengpio.cpp:221:10: note: the lambda has no capture-defaultnpm error 221 | [](uv_work_t *req)npm error | ^npm error ../cpp/opengpio.cpp:213:18: note: ‘<typeprefixerror>line’ declared herenpm error 213 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp:278:17: error: ‘line’ is not capturednpm error 278 | line.set_value(false);npm error | ^~~~npm error ../cpp/opengpio.cpp:221:10: note: the lambda has no capture-defaultnpm error 221 | [](uv_work_t *req)npm error | ^npm error ../cpp/opengpio.cpp:213:18: note: ‘<typeprefixerror>line’ declared herenpm error 213 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:327:25: error: expected primary-expression before ‘line’npm error 327 | gpiod::line line = data->line;npm error | ^~~~npm error ../cpp/opengpio.cpp:328:13: error: ‘line’ is not capturednpm error 328 | line.release();npm error | ^~~~npm error ../cpp/opengpio.cpp:324:10: note: the lambda has no capture-defaultnpm error 324 | [](uv_work_t *req, int status)npm error | ^npm error ../cpp/opengpio.cpp:213:18: note: ‘<typeprefixerror>line’ declared herenpm error 213 | data->line = line;npm error | ^~~~npm error make: *** [opengpio.target.mk:108: Release/obj.target/opengpio/cpp/opengpio.o] Error 1npm error gyp ERR! build error npm error gyp ERR! stack Error: `make` failed with exit code: 2npm error gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)npm error gyp ERR! System Linux 6.12.47+rpt-rpi-v8npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/opengpionpm error gyp ERR! node -v v22.21.0npm error gyp ERR! node-gyp -v v8.4.1npm error gyp ERR! not oknpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-12-31T13_02_43_012Z-debug-0.log
                            host.raspberrypi
                            	2025-12-31 14:02:42.780	info	iobroker Installing iobroker.rpi2@2.4.0... (System call)
                            host.raspberrypi
                            	2025-12-31 14:02:42.778	info	iobroker NPM version: 10.9.4
                            host.raspberrypi
                            	2025-12-31 14:02:39.067	info	iobroker add rpi2 --host raspberrypi
                            host.raspberrypi
                            	2025-12-31 14:02:14.259	info	iobroker exit 25
                            host.raspberrypi
                            	2025-12-31 14:02:13.187	error	iobroker host.raspberrypi Cannot install iobroker.rpi2@2.4.0: 1
                            
                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • M Mark

                              @Thomas-Braun
                              hab ich gemacht.

                              host.raspberrypi
                              	2025-12-31 14:03:00.697	info	iobroker exit 25
                              host.raspberrypi
                              	2025-12-31 14:02:59.649	error	iobroker host.raspberrypi Cannot install iobroker.rpi2@2.4.0: 1
                              host.raspberrypi
                              	2025-12-31 14:02:59.645	error	iobroker npm error code 1npm error path /opt/iobroker/node_modules/opengpionpm error command failednpm error command sh -c node-gyp rebuildnpm error make: Entering directory '/opt/iobroker/node_modules/opengpio/build'npm error CXX(target) Release/obj.target/opengpio/cpp/opengpio.onpm error make: Leaving directory '/opt/iobroker/node_modules/opengpio/build'npm error (node:10247) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioInput(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:14:17: error: expected primary-expression before ‘line’npm error 14 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:19:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 19 | line.request({resourceName, gpiod::line_request::DIRECTION_INPUT, 0});npm error | ^~~~npm error | gpiod::linenpm error In file included from /usr/include/gpiodcxx/chip.hpp:21,npm error from /usr/include/gpiod.hpp:27,npm error from ../cpp/opengpio.cpp:3:npm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:19:58: error: ‘DIRECTION_INPUT’ is not a member of ‘gpiod::line_request’npm error 19 | line.request({resourceName, gpiod::line_request::DIRECTION_INPUT, 0});npm error | ^~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:28:62: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:30:22: error: ‘line’ is not capturednpm error 30 | bool value = line.get_value();npm error | ^~~~npm error ../cpp/opengpio.cpp:28:66: note: the lambda has no capture-defaultnpm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:28:62: note: ‘<typeprefixerror>line’ declared herenpm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:34:52: error: ‘line’ is not capturednpm error 34 | { line.release(); });npm error | ^~~~npm error ../cpp/opengpio.cpp:33:67: note: the lambda has no capture-defaultnpm error 33 | Napi::Function cleanup = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:28:62: note: ‘<typeprefixerror>line’ declared herenpm error 28 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioOutput(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:49:17: error: expected primary-expression before ‘line’npm error 49 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:54:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 54 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:54:58: error: ‘DIRECTION_OUTPUT’ is not a member of ‘gpiod::line_request’npm error 54 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:63:62: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:66:9: error: ‘line’ is not capturednpm error 66 | line.set_value(value); });npm error | ^~~~npm error ../cpp/opengpio.cpp:63:66: note: the lambda has no capture-defaultnpm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:63:62: note: ‘<typeprefixerror>line’ declared herenpm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:69:52: error: ‘line’ is not capturednpm error 69 | { line.release(); });npm error | ^~~~npm error ../cpp/opengpio.cpp:68:67: note: the lambda has no capture-defaultnpm error 68 | Napi::Function cleanup = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:63:62: note: ‘<typeprefixerror>line’ declared herenpm error 63 | Napi::Function setter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: At global scope:npm error ../cpp/opengpio.cpp:81:12: error: ‘line’ in namespace ‘gpiod’ does not name a typenpm error 81 | gpiod::line line;npm error | ^~~~npm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioWatch(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:92:17: error: expected primary-expression before ‘line’npm error 92 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:100:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 100 | line.request({resourceName, gpiod::line_request::EVENT_BOTH_EDGES, 0}, 0);npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:100:58: error: ‘EVENT_BOTH_EDGES’ is not a member of ‘gpiod::line_request’npm error 100 | line.request({resourceName, gpiod::line_request::EVENT_BOTH_EDGES, 0}, 0);npm error | ^~~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:109:62: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:111:22: error: ‘line’ is not capturednpm error 111 | bool value = line.get_value();npm error | ^~~~npm error ../cpp/opengpio.cpp:109:66: note: the lambda has no capture-defaultnpm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^npm error ../cpp/opengpio.cpp:109:62: note: ‘<typeprefixerror>line’ declared herenpm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioWatch(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:115:11: error: ‘struct WatchContext’ has no member named ‘line’npm error 115 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:127:25: error: expected primary-expression before ‘line’npm error 127 | gpiod::line line = data->line;npm error | ^~~~npm error ../cpp/opengpio.cpp:131:33: error: ‘line’ is not capturednpm error 131 | bool hasEvent = line.event_wait(chrono::milliseconds(1));npm error | ^~~~npm error ../cpp/opengpio.cpp:124:10: note: the lambda has no capture-defaultnpm error 124 | [](uv_work_t *req)npm error | ^npm error ../cpp/opengpio.cpp:109:62: note: ‘<typeprefixerror>line’ declared herenpm error 109 | Napi::Function getter = Napi::Function::New(info.Env(), [line](const Napi::CallbackInfo &info)npm error | ^~~~npm error ../cpp/opengpio.cpp:134:28: error: ‘line_event’ is not a member of ‘gpiod’; did you mean ‘info_event’?npm error 134 | gpiod::line_event event = line.event_read();npm error | ^~~~~~~~~~npm error | info_eventnpm error ../cpp/opengpio.cpp:135:34: error: ‘event’ was not declared in this scope; did you mean ‘servent’?npm error 135 | bool value = event.event_type == gpiod::line_event::RISING_EDGE ? true : false;npm error | ^~~~~npm error | serventnpm error ../cpp/opengpio.cpp:135:61: error: ‘gpiod::line_event’ has not been declarednpm error 135 | bool value = event.event_type == gpiod::line_event::RISING_EDGE ? true : false;npm error | ^~~~~~~~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:147:19: error: ‘struct WatchContext’ has no member named ‘line’npm error 147 | data->line.release();npm error | ^~~~npm error ../cpp/opengpio.cpp: At global scope:npm error ../cpp/opengpio.cpp:168:12: error: ‘line’ in namespace ‘gpiod’ does not name a typenpm error 168 | gpiod::line line;npm error | ^~~~npm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In function ‘Napi::Array GpioPwm(const Napi::CallbackInfo&)’:npm error ../cpp/opengpio.cpp:196:17: error: expected primary-expression before ‘line’npm error 196 | gpiod::line line = chip.get_line(lineNumber);npm error | ^~~~npm error ../cpp/opengpio.cpp:201:9: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 201 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp:201:58: error: ‘DIRECTION_OUTPUT’ is not a member of ‘gpiod::line_request’npm error 201 | line.request({resourceName, gpiod::line_request::DIRECTION_OUTPUT, 0}, 1);npm error | ^~~~~~~~~~~~~~~~npm error ../cpp/opengpio.cpp:213:11: error: ‘struct PwmContext’ has no member named ‘line’npm error 213 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp:213:18: error: ‘line’ was not declared in this scope; did you mean ‘gpiod::line’?npm error 213 | data->line = line;npm error | ^~~~npm error | gpiod::linenpm error /usr/include/gpiodcxx/line.hpp:24:11: note: ‘gpiod::line’ declared herenpm error 24 | namespace line {npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:224:25: error: expected primary-expression before ‘line’npm error 224 | gpiod::line line = data->line;npm error | ^~~~npm error ../cpp/opengpio.cpp:264:17: error: ‘line’ is not capturednpm error 264 | line.set_value(true);npm error | ^~~~npm error ../cpp/opengpio.cpp:221:10: note: the lambda has no capture-defaultnpm error 221 | [](uv_work_t *req)npm error | ^npm error ../cpp/opengpio.cpp:213:18: note: ‘<typeprefixerror>line’ declared herenpm error 213 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp:278:17: error: ‘line’ is not capturednpm error 278 | line.set_value(false);npm error | ^~~~npm error ../cpp/opengpio.cpp:221:10: note: the lambda has no capture-defaultnpm error 221 | [](uv_work_t *req)npm error | ^npm error ../cpp/opengpio.cpp:213:18: note: ‘<typeprefixerror>line’ declared herenpm error 213 | data->line = line;npm error | ^~~~npm error ../cpp/opengpio.cpp: In lambda function:npm error ../cpp/opengpio.cpp:327:25: error: expected primary-expression before ‘line’npm error 327 | gpiod::line line = data->line;npm error | ^~~~npm error ../cpp/opengpio.cpp:328:13: error: ‘line’ is not capturednpm error 328 | line.release();npm error | ^~~~npm error ../cpp/opengpio.cpp:324:10: note: the lambda has no capture-defaultnpm error 324 | [](uv_work_t *req, int status)npm error | ^npm error ../cpp/opengpio.cpp:213:18: note: ‘<typeprefixerror>line’ declared herenpm error 213 | data->line = line;npm error | ^~~~npm error make: *** [opengpio.target.mk:108: Release/obj.target/opengpio/cpp/opengpio.o] Error 1npm error gyp ERR! build error npm error gyp ERR! stack Error: `make` failed with exit code: 2npm error gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)npm error gyp ERR! System Linux 6.12.47+rpt-rpi-v8npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/opengpionpm error gyp ERR! node -v v22.21.0npm error gyp ERR! node-gyp -v v8.4.1npm error gyp ERR! not oknpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-12-31T13_02_43_012Z-debug-0.log
                              host.raspberrypi
                              	2025-12-31 14:02:42.780	info	iobroker Installing iobroker.rpi2@2.4.0... (System call)
                              host.raspberrypi
                              	2025-12-31 14:02:42.778	info	iobroker NPM version: 10.9.4
                              host.raspberrypi
                              	2025-12-31 14:02:39.067	info	iobroker add rpi2 --host raspberrypi
                              host.raspberrypi
                              	2025-12-31 14:02:14.259	info	iobroker exit 25
                              host.raspberrypi
                              	2025-12-31 14:02:13.187	error	iobroker host.raspberrypi Cannot install iobroker.rpi2@2.4.0: 1
                              
                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #23

                              @Mark sagte in Keine Updates trotz Exit Code 0:

                              iobroker.rpi2@2.4.0

                              Zu alt. Da muss eine Version 3 (z. Zt. noch Beta) installiert werden.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              1 Antwort Letzte Antwort
                              0
                              • M Offline
                                M Offline
                                Mark
                                schrieb am zuletzt editiert von
                                #24

                                Danke. Hab den Adapter gelöscht (hab ihn sowieso nicht mehr benutzt)
                                Der Rest läuft jetzt.

                                1 Antwort Letzte Antwort
                                0
                                Antworten
                                • In einem neuen Thema antworten
                                Anmelden zum Antworten
                                • Älteste zuerst
                                • Neuste zuerst
                                • Meiste Stimmen


                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                938

                                Online

                                32.6k

                                Benutzer

                                81.9k

                                Themen

                                1.3m

                                Beiträge
                                Community
                                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                ioBroker Community 2014-2025
                                logo
                                • Anmelden

                                • Du hast noch kein Konto? Registrieren

                                • Anmelden oder registrieren, um zu suchen
                                • Erster Beitrag
                                  Letzter Beitrag
                                0
                                • Home
                                • Aktuell
                                • Tags
                                • Ungelesen 0
                                • Kategorien
                                • Unreplied
                                • Beliebt
                                • GitHub
                                • Docu
                                • Hilfe