Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Homekit Adapter lässt sich nicht installieren

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Homekit Adapter lässt sich nicht installieren

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Maddog-1 last edited by

      @maddog-1

      Container ist doch kein Ding...
      Wobei ich eh nicht überzeugt bin, dass du da wirklich ein Buster laufen hast, denn eigentlich läuft da ein nodejs@20 nicht mehr drauf.

      Was haste denn da wirklich am Start?

      iob diag
      

      sagt dir das.

      1 Reply Last reply Reply Quote 1
      • M
        Maddog-1 last edited by

        Skript v.2024-05-22
        
        *** BASE SYSTEM ***
           Static hostname: pIOBroker
                 Icon name: computer-container
                   Chassis: container
            Virtualization: lxc
          Operating System: Debian GNU/Linux 10 (buster)
                    Kernel: Linux 6.8.8-3-pve
              Architecture: x86-64
        
        model name      : Intel(R) Celeron(R) N5095 @ 2.00GHz
        Docker          : false
        Virtualization  : lxc
        Kernel          : x86_64
        Userland        : 64 bit
        
        Systemuptime and Load:
         13:20:54 up  1:16,  1 user,  load average: 0.42, 0.57, 0.39
        CPU threads: 2
        
        
        *** Time and Time Zones ***
                       Local time: Fri 2024-07-19 13:20:54 UTC
                   Universal time: Fri 2024-07-19 13:20:54 UTC
                         RTC time: n/a
                        Time zone: Etc/UTC (UTC, +0000)
        System clock synchronized: yes
                      NTP service: inactive
                  RTC in local TZ: no
        
        *** Users and Groups ***
        User that called 'iob diag':
        manuel
        HOME=/home/manuel
        GROUPS=manuel sudo
        
        User that is running 'js-controller':
        iobroker
        HOME=/home/iobroker
        GROUPS=iobroker tty dialout audio video plugdev
        
        *** Display-Server-Setup ***
        Display-Server: false
        Desktop: 
        Terminal: 
        Boot Target:    graphical.target
        
        *** MEMORY ***
                      total        used        free      shared  buff/cache   available
        Mem:           4.1G        1.5G        1.7G        8.0M        902M        2.6G
        Swap:          4.1G          0B        4.1G
        Total:         8.2G        1.5G        5.8G
        
        Active iob-Instances:   26
        
                 4096 M total memory
                 1524 M used memory
                 1419 M active memory
                  813 M inactive memory
                 1668 M free memory
                    0 M buffer memory
                  902 M swap cache
                 4096 M total swap
                    0 M used swap
                 4096 M free swap
        
        *** top - Table Of Processes  ***
        top - 13:20:55 up  1:16,  1 user,  load average: 0.42, 0.57, 0.39
        Tasks:  52 total,   1 running,  51 sleeping,   0 stopped,   0 zombie
        %Cpu(s):  3.1 us,  3.1 sy,  0.0 ni, 93.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
        MiB Mem :   4096.0 total,   1668.5 free,   1525.0 used,    902.5 buff/cache
        MiB Swap:   4096.0 total,   4096.0 free,      0.0 used.   2562.9 avail Mem 
        
        *** FAILED SERVICES ***
        
          UNIT                          LOAD   ACTIVE SUB    DESCRIPTION                     
        * run-rpc_pipefs.mount          loaded failed failed RPC Pipe File System            
        * sys-kernel-config.mount       loaded failed failed Kernel Configuration File System
        * systemd-journald-audit.socket loaded failed failed Journal Audit Socket            
        
        LOAD   = Reflects whether the unit definition was properly loaded.
        ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
        SUB    = The low-level unit activation state, values depend on unit type.
        
        3 loaded units listed. Pass --all to see loaded but inactive units, too.
        To show all installed unit files use 'systemctl list-unit-files'.
        
        *** FILESYSTEM ***
        Filesystem                       Type      Size  Used Avail Use% Mounted on
        /dev/mapper/pve-vm--101--disk--0 ext4       32G  5.1G   25G  18% /
        none                             tmpfs     492K  4.0K  488K   1% /dev
        udev                             devtmpfs  7.7G     0  7.7G   0% /dev/tty
        tmpfs                            tmpfs     7.8G     0  7.8G   0% /dev/shm
        tmpfs                            tmpfs     7.8G  8.1M  7.7G   1% /run
        tmpfs                            tmpfs     5.0M     0  5.0M   0% /run/lock
        
        Messages concerning ext4 filesystem in dmesg:
        dmesg: read kernel buffer failed: Operation not permitted
        
        Show mounted filesystems:
        TARGET                                SOURCE                           FSTYPE     OPTIONS
        /                                     /dev/mapper/pve-vm--101--disk--0 ext4       rw,relatime,stripe=16
        |-/run                                tmpfs                            tmpfs      rw,nosuid,nodev,mode=755,uid=100000,gid=100000,inode64
        | `-/run/lock                         tmpfs                            tmpfs      rw,nosuid,nodev,noexec,relatime,size=5120k,uid=100000,gid=100000,inode64
        |-/dev                                none                             tmpfs      rw,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64
        | |-/dev/shm                          tmpfs                            tmpfs      rw,nosuid,nodev,uid=100000,gid=100000,inode64
        | |-/dev/mqueue                       mqueue                           mqueue     rw,relatime
        | |-/dev/ttyUSB0                      udev[/ttyUSB0]                   devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/.lxc/proc                    proc                             proc       rw,relatime
        | |-/dev/.lxc/sys                     sys                              sysfs      rw,relatime
        | |-/dev/full                         udev[/full]                      devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/null                         udev[/null]                      devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/random                       udev[/random]                    devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/tty                          udev[/tty]                       devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/urandom                      udev[/urandom]                   devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/zero                         udev[/zero]                      devtmpfs   rw,nosuid,relatime,size=8043388k,nr_inodes=2010847,mode=755,inode64
        | |-/dev/pts                          devpts                           devpts     rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
        | |-/dev/ptmx                         devpts[/ptmx]                    devpts     rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
        | |-/dev/console                      devpts[/0]                       devpts     rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
        | |-/dev/tty1                         devpts[/1]                       devpts     rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
        | `-/dev/tty2                         devpts[/2]                       devpts     rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
        |-/proc                               proc                             proc       rw,nosuid,nodev,noexec,relatime
        | |-/proc/sys                         proc[/sys]                       proc       ro,relatime
        | | |-/proc/sys/net                   proc[/sys/net]                   proc       rw,nosuid,nodev,noexec,relatime
        | | `-/proc/sys/kernel/random/boot_id none[/.lxc-boot-id]              tmpfs      ro,nosuid,nodev,noexec,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64
        | |-/proc/sysrq-trigger               proc[/sysrq-trigger]             proc       ro,relatime
        | |-/proc/cpuinfo                     lxcfs[/proc/cpuinfo]             fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | |-/proc/diskstats                   lxcfs[/proc/diskstats]           fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | |-/proc/loadavg                     lxcfs[/proc/loadavg]             fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | |-/proc/meminfo                     lxcfs[/proc/meminfo]             fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | |-/proc/slabinfo                    lxcfs[/proc/slabinfo]            fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | |-/proc/stat                        lxcfs[/proc/stat]                fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | |-/proc/swaps                       lxcfs[/proc/swaps]               fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        | `-/proc/uptime                      lxcfs[/proc/uptime]              fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        `-/sys                                sysfs                            sysfs      ro,nosuid,nodev,noexec,relatime
          |-/sys/fs/fuse/connections          fusectl                          fusectl    rw,nosuid,nodev,noexec,relatime
          |-/sys/devices/virtual/net          sysfs[/devices/virtual/net]      sysfs      rw,nosuid,nodev,noexec,relatime
          |-/sys/fs/cgroup                    none                             cgroup2    rw,nosuid,nodev,noexec,relatime
          `-/sys/devices/system/cpu           lxcfs[/sys/devices/system/cpu]   fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        
        Files in neuralgic directories:
        
        /var:
        419M    /var/
        235M    /var/cache
        231M    /var/cache/apt
        181M    /var/lib
        169M    /var/cache/apt/archives
        
        Hint: You are currently not seeing messages from other users and the system.
              Users in the 'systemd-journal' group can see all messages. Pass -q to
              turn off this notice.
        No journal files were opened due to insufficient permissions.
        
        /opt/iobroker/backups:
        34M     /opt/iobroker/backups/
        
        /opt/iobroker/iobroker-data:
        705M    /opt/iobroker/iobroker-data/
        568M    /opt/iobroker/iobroker-data/files
        149M    /opt/iobroker/iobroker-data/files/vis-2
        138M    /opt/iobroker/iobroker-data/files/javascript.admin
        118M    /opt/iobroker/iobroker-data/files/javascript.admin/static
        
        The five largest files in iobroker-data are:
        33M     /opt/iobroker/iobroker-data/files/meteoalarm.admin/geocodes.json
        27M     /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map
        24M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
        24M     /opt/iobroker/iobroker-data/files/eventlist/static/js/main.bf7d9efc.js.map
        24M     /opt/iobroker/iobroker-data/files/eventlist.admin/static/js/main.bf7d9efc.js.map
        
        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-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_22559e53cd9ded11af12dca5a7669f5d-if00-port0
        
        HINT:
        Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:
        /dev/ttyUSB0
        
        
        
        *** NodeJS-Installation ***
        
        /usr/bin/nodejs         v20.15.1
        /usr/bin/node           v20.15.1
        /usr/bin/npm            10.7.0
        /usr/bin/npx            10.7.0
        /usr/bin/corepack       0.28.1
        
        
        nodejs:
          Installed: 20.15.1-1nodesource1
          Candidate: 20.15.1-1nodesource1
          Version table:
         *** 20.15.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
                100 /var/lib/dpkg/status
             20.15.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.14.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.13.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.13.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.12.2-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.12.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.12.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.11.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.11.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.10.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.9.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.8.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.8.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.7.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.6.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.6.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.5.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.5.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.4.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.3.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.3.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.2.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.1.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.0.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             10.24.0~dfsg-1~deb10u4 500
                500 http://security.debian.org buster/updates/main amd64 Packages
             10.24.0~dfsg-1~deb10u1 500
                500 http://ftp.debian.org/debian buster/main amd64 Packages
        
        Temp directories causing npm8 problem: 0
        No problems detected
        
        Errors in npm tree:
        
        *** ioBroker-Installation ***
        
        ioBroker Status
        iobroker is running on this host.
        
        
        Objects type: jsonl
        States  type: jsonl
        
        Core adapters versions
        js-controller:  5.0.19
        admin:          6.17.14
        javascript:     8.3.1
        
        nodejs modules from github:     2
        +-- iobroker.gotify@0.2.0 (git+ssh://git@github.com/ThomasPohl/ioBroker.gotify.git#c20ff9a8867b6b452a30b947c005fd7b6f42b41d)
        | +-- syno@3.0.0 (git+ssh://git@github.com/MeisterTR/syno.git#0104a973d33fe332aa6b1ab5be7fe8c57d3c68b0)
        
        Adapter State
        + system.adapter.admin.0                  : admin                 : pIOBroker                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.alexa2.0                 : alexa2                : pIOBroker                                -  enabled
        + system.adapter.backitup.0               : backitup              : pIOBroker                                -  enabled
          system.adapter.daswetter.0              : daswetter             : pIOBroker                                -  enabled
          system.adapter.discovery.0              : discovery             : pIOBroker                                - disabled
          system.adapter.dwd.0                    : dwd                   : pIOBroker                                -  enabled
        + system.adapter.eventlist.0              : eventlist             : pIOBroker                                -  enabled
        + system.adapter.firetv.0                 : firetv                : pIOBroker                                -  enabled
        + system.adapter.fritzbox.0               : fritzbox              : pIOBroker                                -  enabled
        + system.adapter.gotify.0                 : gotify                : pIOBroker                                -  enabled
        + system.adapter.hm-rega.0                : hm-rega               : pIOBroker                                -  enabled
        + system.adapter.hm-rpc.0                 : hm-rpc                : pIOBroker                                -  enabled, port: 0
        + system.adapter.hm-rpc.1                 : hm-rpc                : pIOBroker                                -  enabled, port: 0
          system.adapter.ical.0                   : ical                  : pIOBroker                                -  enabled
          system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: pIOBroker                                -  enabled
          system.adapter.icons-fatcow-hosting.0   : icons-fatcow-hosting  : pIOBroker                                -  enabled
          system.adapter.icons-icons8.0           : icons-icons8          : pIOBroker                                - disabled
          system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : pIOBroker                                - disabled
        + system.adapter.javascript.0             : javascript            : pIOBroker                                -  enabled
          system.adapter.meteoalarm.0             : meteoalarm            : pIOBroker                                -  enabled
        + system.adapter.node-red.0               : node-red              : pIOBroker                                -  enabled, port: 1880, bind: 0.0.0.0
        + system.adapter.pi-hole.0                : pi-hole               : pIOBroker                                -  enabled
        + system.adapter.ping.0                   : ping                  : pIOBroker                                -  enabled
        + system.adapter.proxmox.0                : proxmox               : pIOBroker                                -  enabled, port: 8006
        + system.adapter.signal-cmb.0             : signal-cmb            : pIOBroker                                -  enabled
        + system.adapter.synology.0               : synology              : pIOBroker                                -  enabled, port: 5000
        + system.adapter.synology.1               : synology              : pIOBroker                                -  enabled, port: 5000
        + system.adapter.tankerkoenig.0           : tankerkoenig          : pIOBroker                                -  enabled
        + system.adapter.telegram.0               : telegram              : pIOBroker                                -  enabled, port: 8443, bind: 0.0.0.0
          system.adapter.tr-064.0                 : tr-064                : pIOBroker                                - disabled
        + system.adapter.trashschedule.0          : trashschedule         : pIOBroker                                -  enabled
        + system.adapter.vis-2.0                  : vis-2                 : pIOBroker                                -  enabled
          system.adapter.vis-fancyswitch.0        : vis-fancyswitch       : pIOBroker                                - disabled
          system.adapter.vis-icontwo.0            : vis-icontwo           : pIOBroker                                -  enabled
        + system.adapter.vis-inventwo.0           : vis-inventwo          : pIOBroker                                -  enabled
          system.adapter.vis-material-advanced.0  : vis-material-advanced : pIOBroker                                - disabled
          system.adapter.vis-timeandweather.0     : vis-timeandweather    : pIOBroker                                - disabled
          system.adapter.vis-weather.0            : vis-weather           : pIOBroker                                - disabled
          system.adapter.vis.0                    : vis                   : pIOBroker                                -  enabled
        + system.adapter.web.0                    : web                   : pIOBroker                                -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        + system.adapter.zigbee.0                 : zigbee                : pIOBroker                                -  enabled, port: /dev/ttyUSB0
        
        + instance is alive
        
        Enabled adapters with bindings
        + system.adapter.admin.0                  : admin                 : pIOBroker                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.hm-rpc.0                 : hm-rpc                : pIOBroker                                -  enabled, port: 0
        + system.adapter.hm-rpc.1                 : hm-rpc                : pIOBroker                                -  enabled, port: 0
        + system.adapter.node-red.0               : node-red              : pIOBroker                                -  enabled, port: 1880, bind: 0.0.0.0
        + system.adapter.proxmox.0                : proxmox               : pIOBroker                                -  enabled, port: 8006
        + system.adapter.synology.0               : synology              : pIOBroker                                -  enabled, port: 5000
        + system.adapter.synology.1               : synology              : pIOBroker                                -  enabled, port: 5000
        + system.adapter.telegram.0               : telegram              : pIOBroker                                -  enabled, port: 8443, bind: 0.0.0.0
        + system.adapter.web.0                    : web                   : pIOBroker                                -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        + system.adapter.zigbee.0                 : zigbee                : pIOBroker                                -  enabled, port: /dev/ttyUSB0
        
        ioBroker-Repositories
        stable        : http://download.iobroker.net/sources-dist.json
        beta          : http://download.iobroker.net/sources-dist-latest.json
        
        Active repo(s): stable
        
        Installed ioBroker-Instances
        Used repository: stable
        Adapter    "admin"        : 6.17.14  , installed 6.17.14
        Adapter    "alexa2"       : 3.26.5   , installed 3.26.5
        Adapter    "backitup"     : 2.11.0   , installed 2.11.0
        Adapter    "coronavirus-statistics": 0.9.0, installed 0.9.0
        Adapter    "daswetter"    : 3.1.15   , installed 3.1.15
        Adapter    "deconz"       : 1.4.1    , installed 1.4.1
        Adapter    "device-reminder": 3.1.2  , installed 3.1.2
        Adapter    "discovery"    : 4.5.0    , installed 4.5.0
        Adapter    "dwd"          : 2.8.5    , installed 2.8.5
        Adapter    "eventlist"    : 2.0.1    , installed 2.0.1
        Adapter    "firetv"       : 2.1.0    , installed 2.1.0
        Adapter    "fritzbox"     : 0.6.0    , installed 0.6.0
        Adapter    "hm-rega"      : 4.0.0    , installed 4.0.0
        Adapter    "hm-rpc"       : 1.17.0   , installed 1.17.0
        Adapter    "ical"         : 1.15.0   , installed 1.15.0
        Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
        Adapter    "icons-fatcow-hosting": 0.1.0, installed 0.1.0
        Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
        Adapter    "icons-mfd-svg": 1.2.0    , installed 1.2.0
        Adapter    "javascript"   : 8.3.1    , installed 8.3.1
        Controller "js-controller": 5.0.19   , installed 5.0.19
        Adapter    "meteoalarm"   : 3.0.2    , installed 3.0.2
        Adapter    "node-red"     : 5.2.1    , installed 5.2.1
        Adapter    "pi-hole"      : 1.3.6    , installed 1.3.6
        Adapter    "ping"         : 1.6.2    , installed 1.6.2
        Adapter    "proxmox"      : 2.3.0    , installed 2.3.0
        Adapter    "signal-cmb"   : 0.3.0    , installed 0.3.0
        Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
        Adapter    "socketio"     : 6.7.0    , installed 6.7.0
        Adapter    "synology"     : 3.1.0    , installed 3.1.0
        Adapter    "tankerkoenig" : 3.4.0    , installed 3.4.0
        Adapter    "telegram"     : 3.3.2    , installed 3.3.2
        Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
        Adapter    "trashschedule": 3.3.0    , installed 3.3.0
        Adapter    "tuya"         : 3.15.0   , installed 3.15.0
        Adapter    "upnp"         : 1.0.21   , installed 1.0.21
        Adapter    "vis"          : 1.5.6    , installed 1.5.6
        Adapter    "vis-2"        : 2.9.32   , installed 2.9.32
        Adapter    "vis-fancyswitch": 1.1.0  , installed 1.1.0
        Adapter    "vis-icontwo"  : 1.5.0    , installed 1.5.0
        Adapter    "vis-inventwo" : 3.3.4    , installed 3.3.4
        Adapter    "vis-material-advanced": 1.7.4, installed 1.7.4
        Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
        Adapter    "vis-weather"  : 2.5.9    , installed 2.5.9
        Adapter    "web"          : 6.2.5    , installed 6.2.5
        Adapter    "ws"           : 2.6.1    , installed 2.6.1
        Adapter    "zigbee"       : 1.10.3   , installed 1.10.3
        Adapter    "zigbee2mqtt"  : 2.13.6   , installed 2.13.6
        
        Objects and States
        Please stand by - This may take a while
        Objects:        8340
        States:         7148
        
        *** OS-Repositories and Updates ***
        Hit:1 http://security.debian.org buster/updates InRelease
        Hit:2 http://ftp.debian.org/debian buster InRelease
        Hit:3 http://ftp.debian.org/debian buster-updates InRelease
        Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
        Reading package lists...
        Pending Updates: 0
        
        *** Listening Ports ***
        Active Internet connections (only servers)
        Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
        tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      105        351606     93/systemd-resolved 
        tcp        0      0 192.168.1.126:2010      0.0.0.0:*               LISTEN      1000       398547     5104/io.hm-rpc.1    
        tcp        0      0 192.168.1.126:2001      0.0.0.0:*               LISTEN      1000       398483     5089/io.hm-rpc.0    
        tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          351918     279/master          
        tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1000       396467     4898/iobroker.js-co 
        tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1000       394973     4898/iobroker.js-co 
        tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      105        351600     93/systemd-resolved 
        tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          345978     1/init              
        tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      1000       396717     4973/node-red       
        tcp6       0      0 :::8081                 :::*                    LISTEN      1000       396593     4916/io.admin.0     
        tcp6       0      0 :::8082                 :::*                    LISTEN      1000       401823     5307/io.web.0       
        tcp6       0      0 ::1:25                  :::*                    LISTEN      0          351919     279/master          
        tcp6       0      0 :::5355                 :::*                    LISTEN      105        351603     93/systemd-resolved 
        tcp6       0      0 :::22                   :::*                    LISTEN      0          350584     1/init              
        tcp6       0      0 :::111                  :::*                    LISTEN      0          345980     1/init              
        tcp6       0      0 :::80                   :::*                    LISTEN      1000       396720     4973/node-red       
        udp        0      0 0.0.0.0:5355            0.0.0.0:*                           105        351599     93/systemd-resolved 
        udp        0      0 127.0.0.53:53           0.0.0.0:*                           105        351605     93/systemd-resolved 
        udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          345979     1/init              
        udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1000       396721     4973/node-red       
        udp6       0      0 :::5355                 :::*                                105        351602     93/systemd-resolved 
        udp6       0      0 :::111                  :::*                                0          345981     1/init              
        
        *** Log File - Last 25 Lines ***
        
        
        2024-07-19 13:13:05.365  - info: fritzbox.0 (5059) data from 192.168.1.1: 19.07.24 15:13:05;CALL;1;11;913872;6929;SIP1;
        
        2024-07-19 13:13:09.324  - info: fritzbox.0 (5059) data from 192.168.1.1: 19.07.24 15:13:09;CONNECT;1;11;6929;
        
        2024-07-19 13:15:00.021  - info: host.pIOBroker instance system.adapter.dwd.0 started with pid 8529
        2024-07-19 13:15:01.020  - info: dwd.0 (8529) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v20.15.1, js-controller: 5.0.19
        2024-07-19 13:15:02.450  - info: dwd.0 (8529) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2024-07-19 13:15:02.964  - info: host.pIOBroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2024-07-19 13:15:04.067  - info: host.pIOBroker instance system.adapter.daswetter.0 started with pid 8547
        2024-07-19 13:15:04.888  - info: daswetter.0 (8547) starting. Version 3.1.15 in /opt/iobroker/node_modules/iobroker.daswetter, node: v20.15.1, js-controller: 5.0.19
        2024-07-19 13:15:07.049  - info: daswetter.0 (8547) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
        2024-07-19 13:15:07.556  - info: daswetter.0 (8547) cleaned everything up...
        2024-07-19 13:15:07.565  - info: host.pIOBroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2024-07-19 13:16:42.242  - info: fritzbox.0 (5059) data from 192.168.1.1: 19.07.24 15:16:42;DISCONNECT;1;213;
        
        2024-07-19 13:20:00.012  - info: host.pIOBroker instance system.adapter.dwd.0 started with pid 8675
        2024-07-19 13:20:00.885  - info: dwd.0 (8675) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v20.15.1, js-controller: 5.0.19
        2024-07-19 13:20:02.041  - info: dwd.0 (8675) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2024-07-19 13:20:02.556  - info: host.pIOBroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2024-07-19 13:20:04.027  - info: host.pIOBroker instance system.adapter.meteoalarm.0 started with pid 8693
        2024-07-19 13:20:05.927  - info: meteoalarm.0 (8693) starting. Version 3.0.2 in /opt/iobroker/node_modules/iobroker.meteoalarm, node: v20.15.1, js-controller: 5.0.19
        2024-07-19 13:20:07.845  - info: meteoalarm.0 (8693) 15.1: Updated Weather Alarms for Kreis Kronach -> 0 alarm(s) found
        2024-07-19 13:20:07.845  - info: meteoalarm.0 (8693) Terminated (ADAPTER_REQUESTED_TERMINATION): All data processed. Adapter stopped until next scheduled process.
        2024-07-19 13:20:08.376  - info: host.pIOBroker instance system.adapter.meteoalarm.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        
        
        Homoran Thomas Braun 2 Replies Last reply Reply Quote 0
        • Homoran
          Homoran Global Moderator Administrators @Maddog-1 last edited by Homoran

          @maddog-1 sagte in Homekit Adapter lässt sich nicht installieren:

          Operating System: Debian GNU/Linux 10 (buster)

          also doch.
          dann frag ich mich auch wo da nodejs v20 herkommt

          @maddog-1 sagte in Homekit Adapter lässt sich nicht installieren:

          Pending Updates: 0

          aber nur, weil keine mehr angeboten werden

          M 1 Reply Last reply Reply Quote 0
          • M
            Maddog-1 @Homoran last edited by

            @homoran
            hatte vorhin das iob Nodejs-Update gemacht, ich war der aus dem anderen Beitrag mit dem Problem das ich als Root user das Update nicht machen konnte

            Homoran 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @Maddog-1 last edited by

              @maddog-1 aber wie auch @Thomas-Braun schrieb sollte es für Buster gar nicht mehr gebaut werden.

              🤔

              M 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Maddog-1 last edited by Thomas Braun

                @maddog-1

                Deine Systemzeit ist falsch.
                Setz das auf die richtige Zeitzone.

                Der user 'manuel' fehlt in der Gruppe 'iobroker' (und ggfls. noch weiteren).

                Boot Target: graphical.target

                Sollte auf multi-user.target gesetzt werden.

                @Homoran

                dann frag ich mich auch wo da nodejs v20 herkommt

                Gut möglich, dass nur ein Raspberry 'Buster' davon betroffen ist. Die waren damals auch noch weiter von der Debian-Basis weg als heute.

                Aber nichts destotrotz ist Buster einfach 'end-of-life' und muss durch ein noch lebendes Release ersetzt werden.

                M 1 Reply Last reply Reply Quote 1
                • M
                  Maddog-1 @Homoran last edited by

                  @homoran
                  da bin ich überfragt, hatte nur den Befehl ausgeführt

                  iob nodejs-update
                  
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Maddog-1 last edited by

                    @maddog-1 sagte in Homekit Adapter lässt sich nicht installieren:

                    da bin ich überfragt, hatte nur den Befehl ausgeführt

                    Das geht im Moment noch, in einer kommenden Version wird das auf keinem Buster-basierendem System mehr möglich sein.

                    1 Reply Last reply Reply Quote 0
                    • M
                      Maddog-1 @Thomas Braun last edited by

                      @thomas-braun
                      gibt es da noch einen anderen befehl für die Zeitzone?

                      dpkg-reconfigure tzdata
                      

                      der den ich gerade über google gefunden habe funktioniert nicht

                      das mit dem user in den gruppen und multi user Target muss ich auch erstmal googeln, da hab ich keinen plan hab vorhin nur nach deinem anderen Beitrag den User angelegt

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        Maddog-1 @Maddog-1 last edited by

                        ok das mit der Zeitzone hat sich erledigt, hatte das Sudo vergessen, bin ja jetzt kein root mehr

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Maddog-1 last edited by

                          @maddog-1

                          Zeitzone

                          sudo timedatectl set-timezone Europe/Berlin
                          

                          Über tzdata geht's aber auch.

                          User Gruppen:

                          sudo usermod -aG adm,dialout,sudo,audio,video,plugdev,users,iobroker DEIN_USERNAME
                          exit
                          

                          Boot Target:

                          sudo systemctl set-default multi-user.target
                          
                          M 1 Reply Last reply Reply Quote 0
                          • M
                            Maddog-1 @Thomas Braun last edited by

                            @thomas-braun said in Homekit Adapter lässt sich nicht installieren:

                            sudo systemctl set-default multi-user.target

                            super, Dankeschön, hat alles funktioniert

                            zum thema Update,
                            kann man das 1 zu 1 von hier übernehmen
                            https://forum.iobroker.net/topic/47213/upgrade-von-debian-10-buster-auf-11-bullseye
                            oder gibts ne andere vorgehensweise für nen Proxmox container
                            oder eben ganz neu aufsetzten

                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Maddog-1 last edited by

                              @maddog-1

                              Container sind Wegwerfartikel. Das ist wohl am einfachsten und schnellsten, da einen aktuellen Container drüberzustülpen als zwei Dist-Upgrades zu fahren, bis du dann auf Debian 12 Bookworm bist.

                              M 1 Reply Last reply Reply Quote 0
                              • M
                                Maddog-1 @Thomas Braun last edited by

                                @thomas-braun
                                ok dann werde ich mich mal wenn ich frei hab dran setzen

                                Danke für die Hilfe

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                874
                                Online

                                31.9k
                                Users

                                80.1k
                                Topics

                                1.3m
                                Posts

                                4
                                20
                                839
                                Loading More Posts
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes
                                Reply
                                • Reply as topic
                                Log in to reply
                                Community
                                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                The ioBroker Community 2014-2023
                                logo